[Buildroot] mdev.conf missing during kernel boot-up process?

Arun Reddy reddyac at gmail.com
Wed Jun 11 18:00:54 UTC 2008

Thank you both for the responses. I thought mdev.conf was required to set
device node permissions properly, but this doesn't look like it's the case.
I went ahead and removed support for mdev.conf in BusyBox but haven't
recompiled yet. From the output posted above it looks like my real problem
is then with the line:

/bin/hostname: invalid option -- F.

I am looking into that now to see how I can fix it.

On Wed, Jun 11, 2008 at 10:29 AM, Bernhard Fischer <rep.dot.nop at gmail.com>

> On Wed, Jun 11, 2008 at 09:18:45AM -0700, Arun Reddy wrote:
> >I just finished a MIPS build and I seem to have a near-successful boot-up
> in
> >QEMU going. After mounting the root (ext2 filesystem) as ready only, the
> >boot up halts saying that it
> >
> >cannot create directory '/dev/pts': File exists
> >/bin/sh: /proc/sys/kernel/hotplug: No such file or directory
> >mdev: /etc/mdev.conf: No such file or directory
> >mdev: /etc/mdev.conf: No such file or directory
> >mdev: /etc/mdev.conf: No such file or directory
> >mdev: mknod loop2: Read-only file system
> >/bin/hostname: invalid option -- F
> >Try '/bin/hostname --help' for more information.
> >
> >I checked my BusyBox settings and mdev.conf support is enabled. It seems
> to
> >me that mdev.conf should be automatically generated for me, but after
> No, it should not. You should only turn on something that you really
> need. If you don't need an mdev.conf then you should turn support for
> the config-parsing off. If, OTOH, you _know_ that you need a specific
> mdev.conf, then you're supposed to use your .conf that you wrote and
> that does what it is supposed to do.
> mdev works fine without conf support.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20080611/7279f9a6/attachment-0002.html>

More information about the buildroot mailing list