Date: Tue, 15 Aug 2000 14:55:40 -0700 From: Gary Kline <kline@thought.org> To: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com> Cc: Gary Kline <kline@thought.org>, Antonio Bemfica <antonio@axolotl.ic.gc.ca>, freebsd-stable@FreeBSD.ORG Subject: Re: /stand/sysinstall cannot find any disks ? Message-ID: <20000815145540.A93616@tao.thought.org> In-Reply-To: <43777.966375330@localhost>; from jkh@zippy.osd.bsdi.com on Tue, Aug 15, 2000 at 02:35:30PM -0700 References: <20000815104433.B91711@tao.thought.org> <43777.966375330@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 15, 2000 at 02:35:30PM -0700, Jordan K. Hubbard wrote: > > Exactly! So since the automated build|install procedures > > do not target a new /stand/sysinstall, it should be part of > > whatever cheat-sheet of instructions you write down and type > > out to follow during your next up-rev. > > Or, far better, it should be reinvented as a proper mechanism which is > more conducive to updating. Everything about sysinstall and /stand > right now basically sucks and needs to be shot rather than > documented. :) > In some ways it makes sense to have a standalone tree off root, but reinvesting these things ought to be up there in your prio queue;) What about moving the sysinstall utility to somewhere logical in the hierarchy: say, /usr/sbin? gary -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000815145540.A93616>