[gobolinux-users] Udev is being evil . . .

[Samuel A. Falvo II]

I needed to burn some CDs, and had to reboot into Slackware to do it,
since it has a 2.4-series kernel instead of a 2.6 (on my box).  I
type, as root, "reboot", and it immediately rebooted -- complete with
completely forgetting to unmount the live filesystems!

Mohjive (on IRC) reproduced this bug, and I think he said he had fixed
it.  So maybe it'll go into 014rc2.

Anyway, back on the topic of cdrecord issues, one of the things that
was recommended was upgrading to udev 110-r4.  I did this, and it
rendered the system all but inoperable in the process.  The following
errors are so numerous that I couldn't catch them all.  I'm talking
hundreds, if not thousands, of errors:

/BootScripts/Reboot: not found
/System/Settings/BootScripts/Reboot: Shutdown: not found

udevd[1035]: add_to_rules: invalid rule
'/System/Settings/udev/rules.d/10-udev.rules:...'

(where ... is any number you please)

udevd[1035]: add_to_rules: invalid SUBSYSTEMS operation

and last but FAR from least:

specified group 'console' unknown

Well, I reverted back to udev 095, and eliminated all the error
messages that I could see.  But my xterm program refuses to spawn a
shell!  The precise error I get is:

xterm: Error 32, errno 2: No such file or directory
Reason: get_pty: not enough ptys

Can anyone please help in this?  This is a substantial failure on the
part of Gobo 013, but good lord, I haven't the _foggiest_ clue where
to begin diagnosing this.  :(


Thanks!


-- 
Samuel A. Falvo II