Find the answer to your Linux question:
Results 1 to 2 of 2
I just installed Etch (testing) and then installed devfs by: # apt-get install devfsd At the end of the instal I got: No devfs on /dev, not starting I Then ...
  1. #1
    Just Joined!
    Join Date
    Dec 2005
    Posts
    2

    No devfs on /dev

    I just installed Etch (testing) and then installed devfs by:

    # apt-get install devfsd

    At the end of the instal I got:
    No devfs on /dev, not starting

    I Then added devfs=mount on the line directly after the kermel specification in the grub boot loader per the directions when installing devfsd.

    When I reboot I also get a "No devfs on /dev" message so devfs is not working.

    Any ideas of what I'm missing here?

  2. #2
    Just Joined!
    Join Date
    Aug 2006
    Posts
    4
    Quote Originally Posted by tomiro
    I just installed Etch (testing) and then installed devfs by:

    # apt-get install devfsd

    At the end of the instal I got:
    No devfs on /dev, not starting

    I Then added devfs=mount on the line directly after the kermel specification in the grub boot loader per the directions when installing devfsd.

    When I reboot I also get a "No devfs on /dev" message so devfs is not working.

    Any ideas of what I'm missing here?
    Unfortunately I cannot offer any advice but I am having similar issues. I am running Ubuntu 6.06 (based on Deb 3.1) on an Athlon XP PC w/ 512 MB RAM.

    I just made my first (multiple) attempts at compiling the 2.6.17 kernel which (finally) completed successfully. After getting it loaded and my boot file (menu.lst as I use grub) set up, I rebooted and, alas, got the same error message that you mentioned above. Its the first thing that shows up after the initial kernel selection information which ends with the word "boot" as found in menu.lst. The only other error message I get in the boot sequence is that there are no devices listed in /etc/default/udftools and that udftools cannot start.

    I tried adding devfs=mount between 'kernel' and 'initrd' in my menu.lst but that didn't help. I am also able to boot without using initrd as I compiled ext2 and 3 directly into the kernel, but this still doesn't solve my problem.

    I am able to use all my hardware, it seems. I have read up a bit on devfs only to really find that it seems to be loaded by udev to work with the initial ramdisk.

    Can anyone offer me any suggestions and/or point me in the right direction? Anyone with similar problems? There is surprisingly little information on this particular error out there in google's universe. Please help!

    Xenblend
    San Francisco Bay, CA

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •