Date: Mon, 29 Oct 2001 01:33:30 +0100 From: Bernd Walter <ticso@cicely8.cicely.de> To: Jon Parise <jon@csh.rit.edu> Cc: Seth Kingsley <sethk@meowfishies.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: boot -v capture Message-ID: <20011029013329.D49388@cicely8.cicely.de> In-Reply-To: <20011028160100.A23305@csh.rit.edu> References: <20011028140808.C19580@csh.rit.edu> <20011028123934.C40700@fluff.meowfishies.com> <20011028160100.A23305@csh.rit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 28, 2001 at 04:01:00PM -0500, Jon Parise wrote: > On Sun, Oct 28, 2001 at 12:39:34PM -0800, Seth Kingsley wrote: > > > > Can anyone suggest a means by which to capture the 'boot -v' > > > output without using a serial console? > > > > dmesg(8), so long as it doesn't overrun the buffer. > > > > -current is also writing boot messages to syslog presumably with the > > facility of kern.*. > > Ah, I should have been more specific. > > The machine is unable to boot, so I need to the 'boot -v' output > to diagnose that problem first. It's a chicken-and-egg scenario. If you have an IR interface which you can set to IRDA1 FreeBSD will see it a normal seriel interface. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011029013329.D49388>