Text 11897, 107 rader
Skriven 2008-11-11 01:17:56 av Maurice Kinal (1:261/38)
     Kommentar till en text av James Bradley
Ärende: here today ...
======================
Hey James!

> Woa... What a summer! I recall a few dropped threads, so...

It's been quiet.  A little too quiet?

> Using udev, it used the partition label for the directory name in
> /media the last few bouts I had with it.

I've managed to avoid that directory so far.  My neighbour Paul was looking to
do something simular with disk labelling.  I am not sure what that has to do
with udev though but I suppose it could.  Sounds more like a dbus/hal scheme to
me.

>  But, I'm too trying to move back to the (u)mount scheme.

I haven't stopped doing it that way, even for usb drives and/or usb flash
thingies.  I noticed lately that my 32-bit kernels have issues with my long
standing scheme with making flashdisks bootable the old fashioned lilo way. 
The 64-bit ones no problem so perhaps the new fangled stuff hasn't had a chance
to screw with x86_64.  I am glad I made the move when I did since I seemed to
have escaped much grief.  :-)

> struck me as slick, was with the optical media.

Right.  Are you using atapi/ide or usb/scsii types?  I've noticed a few sata
ones lately but have never run across any in the real world. Saw a couple usb
dvd ones (combo burner/rom) at the local dealers that look more attractive to
me than internal ones do.  At the moment the main box here has no optical
drives and would prefer any additional drives, especially dvd/cd, be
externalized.  I assume the usb dvd/cd drives would be scsii types ala usb
flashdisks as other usb drives.

> A quick question, if I might. I have the raid going in at sda1, and
> the spinning usb drive at sdb1, but sdc1 or sdd1 doesn't exist.
> man mknod tells me as much as info mknod or mknodat, or ... Am I
> chasing the right ghost here?

I am not sure what your question really is.  What are sdc and sdd? udev should
catch them and dynamically create the proper dev's ala mknod. Have a looksee in
dmesg and see if they show up there.  If the kernel doesn't see them then
manually creating them using mknod won't help. You should see something like
this in dmesg;

[   13.057505] scsi 0:0:0:0: Direct-Access     ATA      ST380815AS
4.AA PQ: 0 ANSI: 5
[   13.060266] sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors
(80026 MB)
[   13.062891] sd 0:0:0:0: [sda] Write Protect is off
[   13.065476] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   13.065496] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA [   13.068201] sd 0:0:0:0: [sda] 156301488
512-byte hardware sectors
(80026 MB)
[   13.070890] sd 0:0:0:0: [sda] Write Protect is off
[   13.073595] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   13.073615] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA [   13.076417]  sda: sda1 sda2 sda3 sda4
[   13.101481] sd 0:0:0:0: [sda] Attached SCSI disk

Man is the 2.6.27.5 kernel ever noisy!  I've never seen the numbering scheme in
square backets in earlier kernels.

> Next, I try to upgrade my kernel source tree.

As shown above, I just did that today.  Not sure I am happy with it yet but
everything seems to be working including (especially);

[   11.365766] matroxfb 0000:0b:00.0: PCI INT A -> GSI 20 (level, low)
-> IRQ 20
[   11.366035] matroxfb: Matrox G450 detected
[   11.368523] PInS memtype = 5
[   11.370441] matroxfb: MTRR's turned on
[   11.370706] matroxfb: 1024x768x24bpp (virtual: 1024x5461)
[   11.370950] matroxfb: framebuffer at 0xDC000000, mapped to
0xffffc20001080000, size 33554432
[   11.384921] Console: switching to colour frame buffer device 128x48
[   11.389726] fb0: MATROX frame buffer device
[   11.389911] matroxfb_crtc2: secondary head of fb0 was registered as fb1

as well as;

[   23.599248] Matrox MGA G200/G400/G450/G550 YUV Video interface v2.01
(c) Aaron Holtzman & A'rpi
[   23.601916] mga_vid: Found MGA G400/G450 at 0000:0b:00.0
[   23.604555] mga_vid: MMIO at 0xffffc20001010000 framebuffer: 0xDC000000
[   23.607144] mga_vid: OPTION word: 0x480A1560  mem: 0x05  SDRAM
[   23.609792] mga_vid: detected RAMSIZE is 32 MB
[   23.612430] mga_vid: 1 supported cards found
[   23.615153] mga_vid: using major: 83 (assigned or default!)

Gotta love it!!!

> I can speak to how well Ubuntu was dealing with udev. I had to first
> *create* /media before it worked at all, however. <L> I'm left with
> letting you smart guys figure it out, before I can step into that
> fray again.

AMEN!!!  I prefer the old fashioned way except when the kernel misses things
completely.  Mind you when that happens udev etc. won't help any. As for
/media, no such thing here and everything works great ... more or less.

Life is good,
Maurice

--- BBBS/LiI v4.01 Flag
 * Origin: Prism bbs (1:261/38)