cvs commit: src/etc/mtree BSD.root.dist src/include paths.h src/rescue Makefile README src/rescue/librescue Makefile src/rescue/rescue Makefile

[David O'Brien]

On Mon, Jul 07, 2003 at 02:21:19PM -0400, John Baldwin wrote:
> 
> On 07-Jul-2003 David O'Brien wrote:
> > On Tue, Jul 01, 2003 at 03:25:26PM -0400, John Baldwin wrote:
> >> On 01-Jul-2003 David O'Brien wrote:
> >> > On Tue, Jul 01, 2003 at 02:28:05PM -0400, John Baldwin wrote:
> >> >> No.  sysinstall copies over /stand and then chroots into the new root
> >> >> for the actual install after it does the newfs.  If you don't copy /stand
> >> >> then installs will fail.  
> >> > 
> >> > Yes, we need a /stand during the install.  But not post install.
> >> 
> >> Maybe for your machines, not for some machines I work with that use custom
> >> install scripts. :)
> > 
> > Oh, for a local TWC'ism.  Stock FreeBSD should not be required to support
> > rare localisms.
> 
> David,
> 
> Whether you like it or not, having FreeBSD be friendly to being
> deployed as the OS in "smart devices" is good for FreeBSD's future,
> not bad.  I strongly do not wish to have to maintain a TWCBSD fork
> and strongly try to minimize the differences between what we use
> and what is stock.  I don't commit every hack we use, but I don't
> see a legitimate reason for blowing away /stand during installs.
> Go ahead and be pig-headed if you want though.  If the consensus
> is that /stand should go then I guess that will be Yet Another Local
> Patch.

If "/resuce" had been installed in "/stand" as would be the FreeBSD way
since 2.0; we wouldn't be having this discussion.  Yet another reason why
we should have gone with that location.

Why am I being pig-headed over something that one company needs, and not
another single FreeBSD using entity needs?  All binaries in /stand are in
/resuce and they are updated by 'make world'.

-- 
-- David  (obrien at FreeBSD.org)