The screams are still there. Ever tried to make the keyboard readable
by mortals again after X dies? You can spend half an hour chasing
symlinks to find out which physical device it really is, and then you
have to type the damned 200 char name out because you don't have a gui
at any point that you can cut and paste with. It drives me crackers.
> to use the new naming scheme, devfs does not!
In contrast, suns _scsi_ naming scheme makes some sense. But It don't
see it as any better than sda = id 0, sdb = id 1. sdaa = id 0 lun0,
etc. What's the fascination with humanly non-memorizable codes
(shudder) as device names?
OK, have them, but put in the symbolic links with human names.
> > /dev/sda, /dev/sda[1-15] is simple.
>
> Simple and IMNSHO totally inadequate as we grow into the so called
It only seems inadequate wrt multiple luns, and I suggest sdaa sdab etc
for that. I see no problem with sda being controller 0, id 0, ALWAYS.
There can't be more than 15 units on a controller, can there? So start
higher up for the second controller (shudder, again; hopefully I'll
never have two scsi controllers on a single machine).
> "enterprise computing" arena. Tell me without digging through
> /proc/scsi/scsi conslusively what /dev/sdc is? You can't unless you're
I can if we change it always to be id 2 on controller 0. That's a
trivial change that doesn't break anything. So where does your argument
go now?
> Now, tell me what /dev/dsk/c0t0d0s0 is -- easy controller 0 target 0
> device 0 slice 0. The only ambiguity is which controller is 0? That is
If that's important for you to know, so be it! I have the disks
tagged with little stickers telling me if they're sda or sdb, etc.
Why would I want to know unless I had physical contact with them?
I don't see how it helps you either, since you'd still have to trace the
wiring and examine the id's on the dipswitches.
> space, not mere gigabytes. We've got several hundred disks attached to
> our SUN servers to do this. Hmmmm. OK, let's extend /dev/sd? like the
> /dev/pty?? devices so now we have /dev/sd?? to handle that many drives.
This is a problem of scale. It shouldn't be inflicted on those without
problems of scale.
By all means fix the scsi names to be constant wrt device ids and luns, like
the ide stuff, but don't invent strings of digits as their names without
also providing a well thought out standard naming scheme that a human
can pronounce.
> Yeah, right! I hope that it's painfully obvious that /dev/sd? has to
> change at some point, the only question is when, and providing a migration
> path now is excellent timing.
> It may not be as "simple" as /dev/sda[1-15], but it also "screams"
> industry (SYSV) standard -- you know Solaris, HP-UX, IRIX, SCO, etc, etc.
Solaris = ugh in many respects like this. SCO ditto. These machines are not
people-friendly. If you want to make your machine easier for a machine to
administer, then don't be surprised when the human admins complain.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html