On Mon, Apr 16, 2012 at 05:45:33PM +0100, Andrew Benton wrote: > On Mon, 16 Apr 2012 17:01:10 +0100 > "Dr.-Ing. Edgar Alwers" <[email protected]> wrote: > > > Hallo, > > > > I am building udev BLFS § 12 Version 2012-04-15. My LFS System is 7.0 > > My original LFS udev was 173. If I build this one in BLFS, following the > > actual instructions, I get an error during the boot process: > > " /dev/pts does not exist" > > and I do not have xterm or consoles availaible. By the way, udev-173 is > > not anymore included in the list. > > > > So I took udev-174 and built following the book. "Make check" delivers some > > 140 errors, but the system boots now withouth problems. Is that OK ? Can I > > continue with udev-174 even if LFS was built with udev-173 ? > > If the system boot Ok then sure, why not? > > > May be a follow up problem is that, after building upower-0.9.14, the > > system crashes during the boot process, telling that /dev/sda1 has not been > > found. I do not know, if this could be related to a udev not working as it > > should ? > > The only way that I can think that installing a package would produce > a /dev/sda1 has not been found error would be if it modified the udev > rules so that /dev/sda1 was called something else or had the wrong > permissions so it couldn't be read. So check your udev rules, > /lib/udev/rules.d/* and /etc/udev/rules.d/* > > Andy
The big question is: did you reboot after installing 173, or did you install both udev and upower and then check to see if it rebooted ? I suspect the latter - if so, your udev does appear to be broken. But, udev uses the kernel names - did you also rebuild your kernel and change its config ? If so, go back to the old kernel. Also, what does your system use /dev/sda1 for ? If it's the root filesystem, that sounds like a kernel config problem. Or, is it your /boot partition, and the problem is actually in grub ? The reason I put in the paragraph "You should look at the LFS instructions for the version you used, to check that you are using the correct testfiles (for some versions, this was a separate tarball, extracted in the udev directory with --strip-components=1) and to compare the configure options you are about to use against those which you used to build the version you are running (sometimes, the options change)." was because in 7.0 I needed to rebuild udev for gnome, and the number of test failures scared me enough to look at how I had built udev in LFS-7.0, and what we did to test it. From memory, there were some configuration changes apart from the separate-testfile problem. FWIW, it looks as if the the kernel.org files have only been restored back to udev-174 following the break-in. The LFS book should have an md5sum for 173, google found tarballs at : http://www.mirrorservice.org/sites/ftp.kernel.org/pub/linux/utils/kernel/hotplug/%5Bpage=7%5D (Oddly, 173 is the last entry, so it seems mirrorservice has not yet resumed mirroring this part of kernel.org.), http://pkgs.fedoraproject.org/lookaside/pkgs/udev/ (you need to go down two levels - the second levels seem to be named for the git commits), and https://launchpad.net/udev/+download I haven't verified that any of these match the md5, but they are normally-reliable sources. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
