mdev help

Chey chey.smith at gmail.com
Wed Aug 16 12:14:16 UTC 2006


On 8/15/06, Rob Landley <rob at landley.net> wrote:
> On Monday 14 August 2006 2:30 pm, Chey wrote:
> > During the boot process I use mdev to populate /dev which is a ramfs.
> > Everything seems to work fine with the exception of /dev/tty which
> > seems to be in invalid device file. I determine it to be an invalid
> > device file like so:
> >
> > @foobar:/# stty -F /dev/tty
> > stty: /dev/tty: No such device or address
> >
> > Is this a bug or does this have something to do with my kernel?
>
> Well, mdev is getting its values out of sysfs, ala:
>
> cat /sys/class/tty/tty/dev
> 5:0
>
> Could you cat the appropriate /sys/class/tty/tty/dev file and do an ls -l of
> your /dev/tty and tell us what you get?  (If that looks ok, then yes it's
> probably an issue with your kernel .config or some such.)

Here is the output:

@foobar:/# cat /sys/class/tty/tty/dev
5:0
@foobar:/# ls -l /dev/tty*
crw-rw----    1 0        0          5,   0 Aug 16 12:19 /dev/tty
crw-rw----    1 0        0          4,  64 Aug 16 12:19 /dev/ttyS0
crw-rw----    1 0        0          4,  65 Aug 16 12:19 /dev/ttyS1
crw-rw----    1 0        0          4,  66 Aug 16 12:19 /dev/ttyS2
crw-rw----    1 0        0          4,  67 Aug 16 12:19 /dev/ttyS3

One thing I would like to mention is that if I static my nodes in the
root file system I don't have this problem.

Chey

>
> Rob
> --
> Never bet against the cheap plastic solution.
>



More information about the busybox mailing list