Date: Tue, 09 Mar 2004 19:47:57 -0800 From: underway@comcast.net (Gary W. Swearingen) To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: freebsd-questions@freebsd.org Subject: Re: network type console and /etc/ttys Message-ID: <8h3c8hgy6q.c8h@mail.comcast.net> In-Reply-To: <20040309231919.GA3671@happy-idiot-talk.infracaninophile.co.uk> (Matthew Seaman's message of "Tue, 9 Mar 2004 23:19:20 %2B0000") References: <gjsmgjgi9u.mgj@mail.comcast.net> <20040308214054.GD8114@happy-idiot-talk.infracaninophile.co.uk> <xt7jxthlco.jxt@mail.comcast.net> <20040309231919.GA3671@happy-idiot-talk.infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Seaman <m.seaman@infracaninophile.co.uk> writes: > ... It's pretty pointless having a remote console if you > can't type 'boot' into it. And it's hard to have the network > interface configured and up, with network comms programs running when > the system is sitting at the boot-loader prompt. Hmmmm. I was thinking that the serial port only got into the picture after the kernel was loaded and / was mounted so /etc/ttys could be read to configure the console, but you remind me that it comes into play during a mid-phase of the boot loading. So what I'm looking for would require a considerable change to the boot loader. I wonder if it has to fit into a few (up to about 15, IIRC) boot records, or if it could use some code under /boot/? Oh well, you've convinced me that Ethernet consoles can't be easily supported (though it still seems useful enough that someone would have done it by now). Thanks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8h3c8hgy6q.c8h>