Date: Thu, 25 Jul 1996 11:54:34 +1000 (EST) From: "Daniel O'Callaghan" <danny@panda.hilink.com.au> To: Hans Zuidam <hans@brandinnovators.com> Cc: freebsd-hackers@freebsd.org Subject: Re: catching /etc/rc output Message-ID: <Pine.BSF.3.91.960725112216.1006D-100000@panda.hilink.com.au> In-Reply-To: <199607241503.RAA01095@truk.brandinnovators.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 24 Jul 1996, Hans Zuidam wrote: > Is there a convenient way to direct all output from the /etc/rc scripts > to both the console and a file other than rewriting them? Scrollback > is not always sufficient especially after lengthy fsck output. How about starting by building a statically linked version of tee(1). Pop it into /bin and wedge it into /etc/rc where appropriate. Trouble is that you don't have anywhere to write the file unless you (a) brute-force fsck of / and write on that, or (b) have a special partition wd0h, 1MB in size, which you mount for the purposes of catching fsck output, then umount when finished. Thus wd0h is almost guaranteed to be clean and writable. I've given myself a project of making it straightforward to get a two-stage boot process so a machine which is administered remotely can come half-way up enough to be telnetted to. Danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960725112216.1006D-100000>