Date: Fri, 25 Jan 2002 00:28:12 +0100 From: Brad Knowles <brad.knowles@skynet.be> To: swear@blarg.net (Gary W. Swearingen), 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: <p0510123eb87647ccfeaf@[10.0.1.3]> In-Reply-To: <pbhepb8srq.epb@localhost.localdomain> References: <20020123114658.A514@lpt.ens.fr> <20020123124025.A60889@HAL9000.wox.org> <3C4F5BEE.294FDCF5@mindspring.com> <20020123223104.SM01952@there> <p0510122eb875d9456cf4@[10.0.1.3]> <pbhepb8srq.epb@localhost.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:15 AM -0800 2002/01/24, Gary W. Swearingen wrote: > 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. Granted, you can do this. But this is not standard behaviour, and unless you carry this modification with you to all affected machines you ever administer, you could easily silently lose disk space that no one ever manages to figure out where it's gone. Even if you do so, you've now got a crutch that won't exist on other systems, and you're more likely to trip yourself up when you do the symlink part and you forget the rest. This is kind of like alias'ing rm to be something less dangerous for root, and then seriously injuring yourself on an unpatched system. IMO, you're better off leaving /tmp alone, and more carefully monitoring the disk space on the root filesystem instead. If all your own tools always use /usr/tmp or /var/tmp (or whatever), then you should only be left with the standard tools which might scribble all over /tmp, and they should be easier to catch. Alternatively, if you want a separate /tmp filesystem (so that /tmp is writable during the early stages of boot, but is not dangerous to the root filesystem once you're in multi-user mode), you could go so far as to make it an mfs, and it would be wicked fast. -- Brad Knowles, <brad.knowles@skynet.be> H4sICIFgXzsCA2RtYS1zaWcAPVHLbsMwDDvXX0H0kkvbfxiwVw8FCmzAzqqj1F4dy7CdBfn7 Kc6wmyGRFEnvvxiWQoCvqI7RSWTcfGXQNqCUAnfIU+AT8OZ/GCNjRVlH0bKpguJkxiITZqes MxwpSucyDJzXxQEUe/ihgXqJXUXwD9ajB6NHonLmNrUSK9nacHQnH097szO74xFXqtlbT3il wMsBz5cnfCR5cEmci0Rj9u/jqBbPeES1I4PeFBXPUIT1XDSOuutFXylzrQvGyboWstCoQZyP dxX4dLx0eauFe1x9puhoi0Ao1omEJo+BZ6XLVNaVpWiKekxN0VK2VMpmAy+Bk7ZV4SO+p1L/ uErNRS/qH2iFU+iNOtbcmVt9N16lfF7tLv9FXNj8AiyNcOi1AQAA 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?p0510123eb87647ccfeaf>