WARNING. HEAV:Y SARCASM AHEAD. It's late, and these are things that bit me
and generally annoyed the crap out of me when I ws getting 7.1 up and
running. These things are *not* the fault of the SGI dudes! It's the kernel
interface from hell... yes, it's (shield your kid's eyes, folks, you don't
want them to see this) DEVFS.
On Sun, Jun 24, 2001 at 09:01:33PM -0700, Dusan wrote:
>i recently tried xfs rh7.1 installer, and it seem to me that there are two
>problems
>first during boot there's attempt to do fstab entry for cdrom /hdc
>and the file already exists.
If it's what I think it is, this is some RedHat drain-bamage, hiding in the
"kudzu" hardware registry startup ... just put your cdrom mount points into
/etc/fstab yourself, like:
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0
/dev/cdrom1 /mnt/cdrom1 iso9660 noauto,owner,ro 0 0
and don't worry about it, the error is harmless. It's a *devfs* thing.
But you do need some devfsd magic ... aaah, devfs, you either hate it or you
hate it.
# Manage CD burners too :
#REGISTER ^cdroms/cdrom. EXECUTE /bin/ln -sf $devname .
^^^ comment this one out
vvv and add these (only use cdrom1 if you got it)
# ...and /dev/cdrom
# In case no cdrom modules loaded, point link over to /dev/cdroms/cdrom?
LOOKUP cdrom EXECUTE /bin/ln -sf cdroms/cdrom0 cdrom
LOOKUP cdrom1 EXECUTE /bin/ln -sf cdroms/cdrom1 cdrom1
# Similarly, if the module loaded, create the /dev/cdrom link
REGISTER cdroms/cdrom0 EXECUTE /bin/ln -sf cdroms/cdrom0 cdrom
REGISTER cdroms/cdrom1 EXECUTE /bin/ln -sf cdroms/cdrom1 cdrom1
>second no matter what, it looks to me that sound doesn't work for anybody
>but root
Dunno if this is your problem, but ...
More RH weirdness ... put the line "options sound dmabuf=1" in
/etc/modules.conf, just like that, spaces, not tabs. to force loading of
sound modules at boot. Yup. It's a MAGIC MODULE OPTION! Don't get too close
to it; it sucks harder than most small black holes.
>there's another problem with keyboard lockups after exit from xsessions
>and troubles accessing serial devices.
Keyboard lockups? You got a USB keyboard?
Devices... like serial ports... well, you gotta set perms on these
things.... devfs will do its best to save them across boots in /dev-state
unless it gets alzheimers, in which case ....
set 'em to 664 or 660 and make yourself a member of the group holding the
device; or set 'em to 666 if nobody else uses the box and it's preferebly
not on a network...
note also that if your cdrom drivers are modules (i've got scsi, so mine
are), then they can get unloaded. and i don't care what devfsd is *supposed*
to do, be prepared for an open to fail with ENODEV or ENOENT while the
driver gets loaded again. this happens regularly to me and i haven't got it
tracked down yet. ive been thinking about rewriting devfsd in python so its
comprehensible.
OK, thanks for listening. I feel *MUCH* better. Hope this rant helps you out.
--
Alan Eldridge
"Smart Tags? We don't need no steenking Smart Tags!"
|