Subject: getty's Exec format error [was: Re: Tests of mdsetimage -s]
To: Hubert Feyrer <email@example.com>
From: Marcin Jessa <firstname.lastname@example.org>
Date: 04/02/2005 21:25:37
On Sat, 2 Apr 2005 20:55:58 +0200 (CEST)
Hubert Feyrer <email@example.com> wrote:
> > Any idea how the floppy ramdisk can generate all the dev files on the
> > fly ?
> Put (only) a MAKEDEV into dev/, and NetBSD's init(8) will DTRT.
> Just make sure everything needed by MAKEDEV is there (mknod, chown, chmod,
> chgrp, ...).
Everything worked fine now, the kernel boots, executes init and then /etc/rc
Seemed like I forgot one binary needed by MAKEDEV.
A part of dmesg:
root file system type: ffs
warning: no /dev/console
init: Creating mfs /dev (374 blocks, 896 inodes)
Now a new problem (as if I did not have enough of them before).
This is what happens when /etc/rc finished executing.
Apr 2 23:06:19 init: can't exec getty '/usr/libexec/getty' for port /dev/console: Exec format error
Apr 2 23:06:19 init: can't exec getty '/usr/libexec/getty' for port /dev/ttyE1: Exec format error
I can execute the getty binary directly in my build dir and then I get a login prompt and can login to my build computer just fine.
/etc/gettytab and image/etc/ttys are also in place.
I am so close to a login prompt I can allmost smell it... :)