Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Jul 2000 20:56:18 -0600
From:      Warner Losh <imp@village.org>
To:        "Andrey A. Chernov" <ache@nagual.pp.ru>
Cc:        "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com>, Marcel Moolenaar <marcel@cup.hp.com>, Will Andrews <andrews@technologist.com>, Marcel Moolenaar <marcel@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/etc Makefile src/include Makefile src/release Makefile src/release/picobsd/build Makefile.mfs src/release/picobsd/custom Makefile.mfs src/release/picobsd/dial Makefile.mfs src/release/picobsd/install Makefile.mfs 
Message-ID:  <200007250256.UAA85575@harmony.village.org>
In-Reply-To: Your message of "Tue, 25 Jul 2000 06:52:15 %2B0400." <20000725065215.A36350@nagual.pp.ru> 
References:  <20000725065215.A36350@nagual.pp.ru>  <20000725055124.A35927@nagual.pp.ru> <20000724085030.A28936@nagual.pp.ru> <25873.964459115@localhost> <20000725055124.A35927@nagual.pp.ru> <200007250228.UAA85362@harmony.village.org> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <20000725065215.A36350@nagual.pp.ru> "Andrey A. Chernov" writes:
: On Mon, Jul 24, 2000 at 08:28:15PM -0600, Warner Losh wrote:
: > But come to think of it, I'm not at all sure why we need to have mtree
: > follow symbolic links in the build process.  I thought I understood
: > that, but now cannot find the words to explain it and am in doubt of
: > my understanding of it.
: 
: It depends of the way disks set organized. If people have several disks
: with symlinks to /tmp, /var/mail etc., they need -L to set correct
: permissions, otherwise they are under security risk. But other people
: don't need this thing. The acceptable solution will be /etc/make.conf
: option defaulted to -L to minimize risk.

Let me understand.  If I have /tmp a symbolic link to /big/disk/tmp
and /var/tmp a symbolic link to /big/disk/var/tmp, then without -L my
/big/disk/tmp and /big/disk/var/tmp directories will not be touched by
the mtree and may retain bad permissions?  Is that correct?

If so, then an option in /etc/make.conf will be the best way to handle
this since that's relatively rare and people tend to setup those sorts
of systems correctly.  We'd need to document it, of course, but that
shouldn't be too hard.  And it would allow your changes back into the
tree as they are otherwise benign.

Warner


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?200007250256.UAA85575>