On Tue, Aug 17, 1999 at 02:44:03PM +0200, goswin.brederlow@student.uni-tuebingen.de wrote: > Michael Stone <mstone@debian.org> writes: > > How does putting /tmp on its own partition keep it from getting filled > > up? If anything, it will fill up faster if it has less than 100% of the > > available drive space assigned to it. This argument is a non-starter for > > the single-user desktop. > > 1. /tmp fragments a lot. Hmm. My system doesn't seem fragmented. This is a single-user box--there's not going to be a whole lot of activity in /tmp. I'm far more likely to fragment my home dir. > 2. If /tmp is full and is on / with /var, linux crashes. > 3. If /tmp is full, but a partition, nothing happens but a "filesystem > full" Whoopie, you saved people from filling up /tmp. Now all you've got to do is keep them from filling up / and /var. Remember, this is a single user box with someone running things as root while still learning what they're doing. How do we keep them from upgrading from potato to woody via apt-get (filling the small /var partition and possibly /usr) and saving a 100MB email to /root/mbox? > I think policy states that / and /usr should readonly mountable, so to > fullfill that policy /var, /tmp and /home must be partitions. The > suggestion should be made to have them on another partition. The > benefits and drawbacks should be explained in the online help. No policy can dictate that it's possible to do that. Whether the local admin chooses to is beyond the purview of policy. Tuning the default to the low end in no way impedes someone from setting up their own system in a different manner. Mike Stone
Attachment:
pgpXroomizXkz.pgp
Description: PGP signature