All, Please ignore my previous post. The last rootf I built didn't have the correct nodes installed $ cd ~/rootfs $ sudo mknod -m 666 dev/null c 1 3 $ sudo mknod -m 600 dev/console c 5 1
Added the following command rebuilt the ram file system and all is well again. Thanks. On Sunday, 10 December 2017 20:37:30 UTC, onio wrote: > > I am learning Embedded Linux using the book titled "Mastering Embedded > Linux Programming" by Chris Simmonds on page 131 of the second edition. He > speak about adding the following lines to an "inittab" file in /etc when > building a ram file system. > >> There is a version of getty in BusyBox. You launch it from inittab using >>> the keyword >> >> respawn, which restarts getty when a login shell is terminated, so >>> inittab should read >> >> like this: >> >> > ::sysinit:/etc/init.d/rcS > ::respawn:/sbin/getty 115200 console > > My problem is when I do this I can't seem to log in I get re-occurring > message > getty: can't open '/dev/null': No such file or directory > > Any insight would be appreciated. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/205f88cf-96ef-45a3-965a-4e017a1c04f6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
