Date: 24 Jan 2002 11:15:37 -0800 From: swear@blarg.net (Gary W. Swearingen) To: Brad Knowles <brad.knowles@skynet.be> Cc: freebsd-chat@FreeBSD.ORG Subject: Re: Bad disk partitioning policies (was: "Re: FreeBSD Intaller (was "Re: ... RedHat ...")") Message-ID: <pbhepb8srq.epb@localhost.localdomain> In-Reply-To: <p0510122eb875d9456cf4@[10.0.1.3]> References: <20020123114658.A514@lpt.ens.fr> <20020123124025.A60889@HAL9000.wox.org> <3C4F5BEE.294FDCF5@mindspring.com> <20020123223104.SM01952@there> <p0510122eb875d9456cf4@[10.0.1.3]>
next in thread | previous in thread | raw e-mail | index | archive | help
Brad Knowles <brad.knowles@skynet.be> writes: > > When all's said and done, I symlink /tmp to > > /usr/tmp and /var to /usr/var. > > This has also been discussed previously. However, I believe > that there is much more agreement that symlinking /tmp to anywhere not > on the root filesystem is a really, really bad idea -- what happens > during boot if the system need to write something to /tmp, but /tmp is a > symlink to a filesystem that hasn't been mounted yet? Many (but not all) such problems can be handled by having /tmp symlink to a directory that exists whether or not a parent of that directory is mounted. Eg, /tmp -> /var/tmp and you make a /var/tmp directory when /var is unmounted. If anything shows up in the unmounted /var/tmp (which you could have a script check for just before next "mount -a"), you've discovered a bug, IMO. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?pbhepb8srq.epb>