Linux LVM users
 help / color / mirror / Atom feed
From: Steven Lembark <lembark@wrkhors.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LILO configuration for LVM "boot" filesystem
Date: Thu, 07 Jun 2001 16:20:56 -0500	[thread overview]
Message-ID: <3B1FF038.41D7D184@wrkhors.com> (raw)
In-Reply-To: 20010607182636.H3232@jensbenecke.de

> > > Use separate mount points for /var, /usr & /home.  This keeps root down
> > > to mainly /etc, /dev, /bin, /sbin and /lib -- none of which is all that
> > > enormous.  Short of writing the File From Hell to /tmp a 128MB root
> > > file system works well enough for me.  I do put /usr & /opt on LVM but
> > > only because all the tools needed to revive the system are in /bin,
> > > /sbin & /lvm on the root.
> >     After installation, do:
> > cd / ; mv tmp tmp.old ; ln -s /var/tmp .  reboot rm -rf /tmp.old
> >     Now you don't have to worry about root filling up at all...
> 
> er... I wouldn't do that (at least not on a Debian system).
> 
> Usually /var/tmp is _assumed_ to be only root-writeable, so all sorts of
> daemons and programs running as root put their stuff there. This could open
> a number of security holes, when /var/tmp doesn't get treated as carefully
> as /tmp.

then debian butchered the SVR4 file system layout.  whole idea 
of having /boot and /var was to make sure that diskless systems
that nfs-ed everything else could count on having local storage
in /var and a minimal amount of anything required in /boot.

just about everything else on the planet assumes that /var/tmp
is a replacement for /tmp and should 01777...

-- 
 Steven Lembark                                   2930 W. Palmer St.
                                                 Chicago, IL  60647
 lembark@wrkhors.com                                   800-762-1582

  parent reply	other threads:[~2001-06-07 21:20 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-04  8:07 [linux-lvm] LILO configuration for LVM "boot" filesystem Brian J. Murrell
2001-06-04 14:21 ` Ben Lutgens
2001-06-05  2:01   ` Brian J. Murrell
2001-06-05 11:56     ` Steven Lembark
2001-06-05 15:48       ` Jack McKinney
2001-06-05 18:32         ` Andreas Dilger
2001-06-06  4:07         ` Brian J. Murrell
2001-06-07 15:30           ` Steven Lembark
2001-06-07 15:43             ` Jack McKinney
     [not found]               ` <20010607182636.H3232@jensbenecke.de>
2001-06-07 16:32                 ` Jack McKinney
     [not found]                   ` <20010607191649.R3232@jensbenecke.de>
2001-06-07 19:18                     ` Jack McKinney
2001-06-07 16:39                 ` Mario 'BitKoenig' Holbe
2001-06-07 21:20                 ` Steven Lembark [this message]
2001-06-08  2:27                 ` Russell Coker
2001-06-07 21:18               ` Steven Lembark
2001-06-07 21:36                 ` Steve Wray
2001-06-07 21:37                   ` Steven Lembark
2001-06-07 21:52                     ` Steve Wray
2001-06-07 22:15                       ` Jack McKinney
2001-06-07 22:24                         ` Steve Wray
2001-06-07 22:27                           ` Steven Lembark
2001-06-07 22:23                       ` Steven Lembark
2001-06-08  2:28                         ` Russell Coker
2001-06-08  2:26                       ` Russell Coker
2001-06-07 22:29               ` Mark van Walraven
2001-06-07 22:38                 ` Steve Wray
2001-06-07 21:08             ` Michael Tokarev
     [not found]               ` <20010608153036.G21909@jensbenecke.de>
2001-06-11  0:04                 ` Mark van Walraven
2001-06-11  0:10                   ` Steven Lembark
2001-06-11  0:20                   ` Michael Tokarev
2001-06-11 11:39                     ` Russell Coker
2001-06-07 15:26         ` Steven Lembark
2001-06-05 18:00       ` Andreas Dilger
2001-06-04 17:56 ` Andreas Dilger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B1FF038.41D7D184@wrkhors.com \
    --to=lembark@wrkhors.com \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox