From: "Jack McKinney" <jackmc-linux-lvm@lorentz.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LILO configuration for LVM "boot" filesystem
Date: Thu, 7 Jun 2001 11:32:07 -0500 [thread overview]
Message-ID: <20010607113207.A30712@stocks.pillory.com> (raw)
In-Reply-To: <20010607182636.H3232@jensbenecke.de>; from lvm@jensbenecke.de on Thu, Jun 07, 2001 at 06:26:36PM +0200
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
Big Brother tells me that Jens Benecke wrote:
> > 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.
Hmmm... I run Debian, and /var/tmp is certainly world-writable:
drwxrwxrwt 7 root root 2048 Jun 7 07:56 /var/tmp
It has been this way on every Debian system I have installed...
--
Whoever put the '.' next to the '/' Jack McKinney
on a keyboard obviously never used jackmc@lorentz.com
the -R option to /bin/chown http://www.lorentz.com
1024D/D68F2C07 4096g/38AEF076
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2001-06-07 16:32 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 [this message]
[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
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=20010607113207.A30712@stocks.pillory.com \
--to=jackmc-linux-lvm@lorentz.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