Date: Mon, 19 Jan 2004 11:17:59 -0500 From: Steve Ames <steve@energistic.com> To: Kirk Strauser <kirk@strauser.com> Cc: freebsd-current@freebsd.org Subject: Re: ATA still broken, but now differently Message-ID: <20040119161759.GB33923@energistic.com> In-Reply-To: <87isj8q8rt.fsf@strauser.com> References: <200401180957.i0I9vaxh077548@spider.deepcore.dk> <874qut9li1.fsf@strauser.com> <20040119120127.503502b0@it.buh.cameradicommercio.ro> <87isj8q8rt.fsf@strauser.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 19, 2004 at 09:04:54AM -0600, Kirk Strauser wrote: > At 2004-01-19T10:01:27Z, Ion-Mihai Tetcu <itetcu@apropo.ro> writes: > > >> Out of curiosity, how do I do that when the verbose boot log exceeds the > >> length of the message buffer? Below are the entire contents of > >> dmesg.boot. > > > /var/log/messages ? > > Nope. Seems as though syslog only records the contents of the kernel > message buffer; its entries appear to be identical to /var/run/dmesg.boot. Add to your kernel: # Size of the kernel message buffer. Should be N * pagesize. options MSGBUF_SIZE=122880 -Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040119161759.GB33923>