Date: Mon, 5 Oct 1998 18:31:43 +0200 From: Neil Blakey-Milner <nbm@rucus.ru.ac.za> To: "Larry S. Marso" <larry@marso.com>, freebsd-current@FreeBSD.ORG Subject: Re: odd /stand directory Message-ID: <19981005182753.A23877@rucus.ru.ac.za> In-Reply-To: <19981005100229.D815@marso.com>; from Larry S. Marso on Mon, Oct 05, 1998 at 10:02:29AM -0400 References: <19981005100229.D815@marso.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon 1998-10-05 (10:02), Larry S. Marso wrote: > This has happened on two machines. One an August 3.0-SNAP machine, another > a recent 3.0-elf compile. The /stand directory's contents morph into > machine-killing bloated garbage. For example: > > > ls -l /stand > -r-xr-xr-x 19 root bin 1232896 Aug 4 06:26 -sh > -r-xr-xr-x 19 root bin 1232896 Aug 4 06:26 bad144 > -rw-r--r-- 1 root wheel 1030 Aug 4 07:06 boot.help > -r-xr-xr-x 19 root bin 1232896 Aug 4 06:26 boot_crunch > -r-xr-xr-x 19 root bin 1232896 Aug 4 06:26 cpio *snip* > -r-xr-xr-x 19 root bin 1232896 Aug 4 06:26 mount_nfs > -r-xr-xr-x 19 root bin 1232896 Aug 4 06:26 newfs *snip* > -r-xr-xr-x 19 root bin 1232896 Aug 4 06:26 sysinstall > -r-xr-xr-x 19 root bin 1232896 Aug 4 06:26 zcat What specifically is wrong with this? Unless possibly a "ls -i" reveals that they're using different inodes, that looks about right, except maybe the size is a slight bit big, but I can only compare with a 2.2.6 and an old 3.0 (since I haven't updated /stand on either for ages, if ever), and it's only 200k more, which isn't that unthinkable considering the additions since then. Did you even upgrade /stand? Chances are you missed it, since it requires a make install in /usr/src/release/sysinstall (I know I almost never do it). Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981005182753.A23877>