[Novalug] Device naming.

[Alan Grimes]

> In fact, one of the many reasons to the unified "every read/write device
> is an sd* device" (and sr for read-only/optical) model was so one can
> use the modprobe facilities to blacklist, scsi_hostadapter re-order,
> etc... one ATA device without affecting the rest of the entire ATA
> subsystem.

In the good old days, if I put a drive on a specific port of a specific
controller, I _KNEW_ what it would appear as in the OS.

The standard assignment of interrupts and port numbers to the primary
and secondary IDE controllers has not changed since the early 90s,
indeed it is one of the most stable corners of the PC architecture.

>> what was  previously HDA/(hd0) is now SDB/(hd1). Yeah, I could throw
>> two map commands into grub, but I'd rather not.
>> As for Peter's suggestion about udev, I would argue violently with the 
>> word "clearly". Between HAL, UDEV, SYSFS, DEVFS, KUDZU et al (some of 
>> these are obsolete), it's almost impossible to tell what is going on 
>> anymore.

> The idea is that you don't have to.  I've yet to have an issue myself in
> many, many years.  But if you want to know, then writing udev rules is
> very easy.

=\
There are a hundred things in linux that I simply can't be bothered
with, that's one of them. =|

I don't work for my computer, I demand that it work for me!

>> Yeah, I know there are Too Many Devices, but how about dividing the 
>> space into Important Devices That Most People Have and bless thoss names 
>> and number assignments Forever, and Weird Stuff That We Support So We 
>> Can Claim We Can Run Anything and Everything and let THAT stuff be 
>> assigned dynamically?
>> Make the Commonplace Easy, and the Random/Weird/Obscure stuff Hard.

> I think always having the first disk as "sda" and the first optical as
> "sr0" actually simplifies things.  That's exactly what the new solutions
> do.  The installers and distros these days are pretty good.

You dumb ****, you think you know anything whatsoever about what LINUX
will assign your optical drive?!?!??!

>From the dmesg. (Obviously a noob would be sent to an asylum after
trying to figure out where his phantom scsi hardware is...)

#####
scsi 2:0:1:0: CD-ROM            TSSTcorp CDDVDW SH-S202G  SB00 PQ: 0 ANSI: 5
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
scsi 2:0:1:0: Attached scsi generic sg2 type 5
#####

So I guess I'll map the only optical drive in my system to sg2 and patch
my fstab accordingly...

When I came downstairs Saturday morning, my keyboard couldn't type
letters... The machine was still listening to SSH, but I couldn't fix
it; had to reboot. I was a bit dumbfounded when the kernel panicked
because it couldn't find the root partition. I had forgotten that the
root partition was configured in grub.conf... Understandable because I
hadn't touched the damn file since July 26, 2008; nearly two years ago!! =|

ARGH. LINUX SUCKS!!!


-- 
DO NOT USE OBAMACARE.
DO NOT BUY OBAMACARE.
Powers are not rights.