Hisham Muhammad wrote: > On 9/18/07, Isaac Dupree <[EMAIL PROTECTED]> wrote: >> Hisham Muhammad wrote: >>> Did it appear in /Programs/Udev/Settings, in >>> /Programs/Udev/115.x/Resources/Defaults/Settings or both? >> Both. >> >>>> Probably is a Compile problem, somehow... >>> Yes, I'm suspecting somewhere down the line Compile is not respecting >>> the "-e" flag. Does the oldest, original version of Udev 115 in >>> /Programs still have 50-udev-default.rules in its >>> Resources/Defaults/Settings? Does the problem go away if it is >>> removed? >> Yes, good point, I did make a "115" version originally, which has >> 50-udev-default.rules in Defaults ... but removing that >> 50-udev-default.rules (and /P/Udev/Settings/that, simultaneously) didn't >> fix the problem. > > Ok, I double-checked things here and I think I messed it up. > 50-udev-default.rules comes from the udev tarball. But it shouldn't > reference the console group.
You are right... I had been checking in the file to see if it referenced the console group, and it did several times, but one of the clean-ups must have succeeded in making it revert to the udev tarball's version. Unrelated, I noticed an early log-message saying that /System/Kernel/Devices/shm doesn't exist, so it can't be mounted. I guess this is caused by the `mount -a ..` that was moved to before starting Udev. But when the system is finished booting, /System/Kernel/Devices/shm does exist and is a mountpoint, so maybe this is not exactly a problem? Isaac _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
