Date: Tue, 6 Feb 2001 02:24:05 -0800 From: "David O'Brien" <obrien@FreeBSD.org> To: Warner Losh <imp@harmony.village.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/sysinstall Makefile Message-ID: <20010206022405.J33865@dragon.nuxi.com> In-Reply-To: <200101192016.f0JKGms55718@harmony.village.org>; from imp@harmony.village.org on Fri, Jan 19, 2001 at 01:16:48PM -0700 References: <200101191301.PAQ80768@burka.carrier.kiev.ua> <200101192016.f0JKGms55718@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 19, 2001 at 01:16:48PM -0700, Warner Losh wrote:
> In message <200101191301.PAQ80768@burka.carrier.kiev.ua> Valentin Nechayev writes:
> : sysinstall is extremely valuable to fix system in cases when it is damaged.
> : I think it can live in /stand, or /sbin, or in another place, but this
> : place must be on root partition. Can you move it to /sbin and build statically?
>
> The problem with this is that / is getting very full and many older
> systems that have been upgraded tend to have problems fitting all the
> stuff on them. sysinstall isn't required to boot the system, so it
> shouldn't be in /. Even though it is a useful repair tool, its use as
> a repair tool happens rarely enough that burning space for it on /
> isn't worth it, imho.
So you don't mind me moving fdisk & disklable out of /sbin?
IMHO, fdisk & disklabel are not usable for most. And don't bring up your
WIP on fdisk & disklabel until they are committed.
Putting sysinstall in /usr/sbin is just *wrong* as its our best disk
admin tool.
--
-- David (obrien@FreeBSD.org)
GNU is Not Unix / Linux Is Not UniX
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010206022405.J33865>