Date: Sun, 28 Oct 2001 16:01:00 -0500 From: Jon Parise <jon@csh.rit.edu> To: Seth Kingsley <sethk@meowfishies.com> Cc: freebsd-hackers@freebsd.org Subject: Re: boot -v capture Message-ID: <20011028160100.A23305@csh.rit.edu> In-Reply-To: <20011028123934.C40700@fluff.meowfishies.com>; from sethk@meowfishies.com on Sun, Oct 28, 2001 at 12:39:34PM -0800 References: <20011028140808.C19580@csh.rit.edu> <20011028123934.C40700@fluff.meowfishies.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Jon Parise (jon@csh.rit.edu) . Information Technology (2001) http://www.csh.rit.edu/~jon/ : Computer Science House Member 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?20011028160100.A23305>