Date: Tue, 16 Mar 1999 17:47:10 +1030 From: Greg Lehey <grog@lemis.com> To: Roelof Osinga <roelof@eboa.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Have crashed, won't travel Message-ID: <19990316174710.H429@lemis.com> In-Reply-To: <36DE0352.E99BCB70@eboa.com>; from Roelof Osinga on Thu, Mar 04, 1999 at 04:51:46AM %2B0100 References: <36DCB59E.F16D5539@eboa.com> <19990303195632.B441@lemis.com> <36DDBFEB.86D89D20@eboa.com> <19990304095813.I441@lemis.com> <36DDEFFD.A4DB4978@eboa.com> <19990304130126.B441@lemis.com> <36DE0352.E99BCB70@eboa.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 4 March 1999 at 4:51:46 +0100, Roelof Osinga wrote: > Greg Lehey wrote: >>> However I am quite new to FreeBSD, maybe these (boot) messages get stored >>> and kept for a few revisions like the maillog? >> >> They're in /var/log/messages, and also (just the boot messages) in >> /var/run/dmesg.boot. You can also display the contents of the message >> buffer with dmesg, but after the machine's been up for a while it gets >> overwritten with other messages. > > So I noticed. The top is either all gibberish or some fancy ANSI codes > that are totally wasted on my telnets <g>. E.g. > > "\^[[17;1H\^[[m\^[[19;1H\^[[m\^[[20;1H\^[[m\^[[21;1H\^[[m\^[[17;" > > etc., for about 10K. This junk is the record of what you entered to the visual UserConfig. The gibberish are control codes for the terminal emulation. >> The kind of damage done to a file system is usually in the structure >> rather than in the individual files. A make world wouldn't do much to >> help there. In general, if it complains about problems, but still >> comes up, it has solved those problems. > > Well, I can't recollect having ever experienced file corruption with an > unix system but I do have experienced them with other OSs. Also I have > lost whole filesystems due to superblock problems. Granted, this was > with Microsoft Xenix, but ... Well, XENIX had a pretty typical old-style file system layout. ufs is better, and doesn't get so corrupted. >> You might find it interesting to try. It won't solve the (possible) >> problem at hand. > > It came up in single user mode. So I could easily recheck the filesystems. > It didn't find any problems, so I guess it's probably Ok. You can assume that's OK. It isn't always, but I've seen very very few instances of file system damage which wasn't detected by fsck. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990316174710.H429>