On 11-Jan-01 Ben Smithurst wrote:
> Crist J. Clark wrote:
>
>> On Thu, Jan 11, 2001 at 11:52:43AM -0800, John Baldwin wrote:
>>
>>> Erm, many things live in both /stand and other places:
>>>
>>>> ll /stand/ | wc -l
>>> 35
>>>> ll /stand/rm /bin/rm
>>> -r-xr-xr-x 2 root wheel 255736 Jan 9 08:17 /bin/rm
>>> -r-xr-xr-x 31 root wheel 1729520 Jul 28 07:32 /stand/rm
>>
>> I am not clear what you are saying here. Only sysinstall lives in
>> /stand,
>
> yeah, but it can be used as many things. If invoked as "rm" sysinstall
> behaves just like the real rm, it happens to be one big binary.
>
>> Well, /stand/rm is not _really_ rm at all, but I get the point. I
>> guess the only question is whether to put it in /sbin or /usr/sbin. I
>> think /sbin makes sense (so it is bootable), but it is 1.6MB of
>> /-bloat... But from another thread about making 250MB the default /
>> size, I guess few care too much about that anymore.
>
> I'd prefer it in /usr/sbin, some of my root partitions are only 32MB,
> and that's not big enough at the moment. If your /usr is hosed to
> the extent you can't mount it you've probably got more problems than
> sysinstall will help you with. But that's just my opinion.
Erm, sysinstall can be used as a replacement for fdisk and disklabel, both of
which are in /sbin. In fact, in 4.2 the only tool you can realistically use to
splat a virgin disklabel onto a slice w/o weird hoop jumping that isn't
documented _is_ sysinstall. disklabel should have that fixed by 4.3, however.
However, 800k is big for /sbin:
> ll /sbin/ | sort -n -k 5
...
-r-xr-sr-x 2 root tty 299956 Jan 9 08:25 restore
-r-xr-sr-x 2 root tty 299956 Jan 9 08:25 rrestore
-r-xr-xr-x 1 root wheel 424448 Jan 9 08:24 ipfstat
-r-xr-xr-x 1 root wheel 484912 Jan 9 08:24 fsdb
-r-xr-xr-x 1 root wheel 513748 Jan 9 08:25 vinum
--
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message