From: Olaf Dietsche <olaf.dietsche@t-online.de>
To: miquels@cistron-office.nl (Miquel van Smoorenburg)
Cc: linux-kernel@vger.kernel.org
Subject: Re: About /etc/mtab and /proc/mounts
Date: Wed, 26 Feb 2003 12:00:43 +0100 [thread overview]
Message-ID: <87u1er71d0.fsf@goat.bogus.local> (raw)
In-Reply-To: <b3i4nv$sud$1@news.cistron.nl> (miquels@cistron-office.nl's message of "Wed, 26 Feb 2003 10:26:07 +0000 (UTC)")
miquels@cistron-office.nl (Miquel van Smoorenburg) writes:
> In article <3E5C8682.F5929A04@daimi.au.dk>,
> Kasper Dupont <kasperd@daimi.au.dk> wrote:
>>A simpler solution, that does not require changes to the kernel
>>would be to just move mtab to a more apropriate location. My
>>suggestion would be to change it from /etc/mtab to /mtab.d/mtab.
>>Then you could mount a tmpfs filesystem on /mtab.d. Or by making
>>/mtab.d a symlink, you can get the mtab file whereever you want,
>>including /etc.
>
> /dev/shm ? Supposed to be there on many systems anyway. Fix
> 'mount' and 'umount' so that if they see /etc/mtab is a symlink,
> they follow it and create the temp files etc in the destination
> directory of the link instead of in /etc. Then
> ln -sf /dev/shm/mtab /etc/mtab et voila
I thought, this is what /var is for. So, /var/run, /var/lib/misc or
/var/etc might be more appropriate?
OTOH, "ln -s /proc/mounts /etc/mtab" works just fine here.
Regards, Olaf.
next prev parent reply other threads:[~2003-02-26 10:50 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 11:21 About /etc/mtab and /proc/mounts DervishD
2003-02-26 9:18 ` Kasper Dupont
2003-02-26 10:26 ` Miquel van Smoorenburg
2003-02-26 11:00 ` Olaf Dietsche [this message]
2003-02-26 11:14 ` Måns Rullgård
2003-02-26 11:44 ` Kasper Dupont
2003-02-26 12:16 ` Olaf Dietsche
2003-02-26 12:34 ` Måns Rullgård
2003-02-26 13:39 ` Olaf Dietsche
2003-02-26 13:54 ` Måns Rullgård
2003-02-26 14:23 ` Olaf Dietsche
2003-02-27 4:14 ` Miles Bader
2003-02-27 6:40 ` Kasper Dupont
2003-02-27 7:03 ` Joseph Wenninger
2003-02-27 8:28 ` Kasper Dupont
2003-03-05 0:03 ` Jamie Lokier
2003-02-27 7:06 ` Miles Bader
2003-02-27 8:25 ` Kasper Dupont
2003-02-27 8:42 ` Miles Bader
2003-02-27 9:21 ` jw schultz
2003-02-27 9:49 ` Miles Bader
2003-02-27 23:33 ` Kasper Dupont
2003-02-27 12:48 ` Denis Vlasenko
2003-02-27 23:28 ` Kasper Dupont
2003-02-28 6:15 ` Denis Vlasenko
2003-03-02 13:04 ` DervishD
2003-03-02 14:16 ` Kasper Dupont
2003-03-03 1:04 ` jw schultz
2003-03-03 12:22 ` Kasper Dupont
2003-03-04 2:02 ` jw schultz
2003-03-05 12:57 ` Kasper Dupont
2003-03-06 1:18 ` jw schultz
2003-03-06 23:30 ` Kasper Dupont
2003-03-04 11:16 ` DervishD
2003-03-04 11:08 ` DervishD
2003-02-27 9:46 ` Kasper Dupont
2003-02-27 9:58 ` Miles Bader
2003-02-27 12:26 ` Gabriel Paubert
2003-02-27 7:07 ` Joseph Wenninger
2003-02-27 7:08 ` Dominik Kubla
2003-02-27 8:12 ` Kasper Dupont
2003-02-27 9:11 ` Dominik Kubla
2003-02-27 16:00 ` Horst von Brand
2003-02-27 16:31 ` Christoph Hellwig
2003-02-27 16:40 ` Dominik Kubla
2003-02-27 19:47 ` Kasper Dupont
2003-02-27 22:13 ` Valdis.Kletnieks
2003-02-27 22:31 ` Kasper Dupont
2003-02-27 23:54 ` Miquel van Smoorenburg
2003-02-28 1:37 ` Miles Bader
2003-03-02 12:53 ` DervishD
2003-03-02 14:00 ` Kasper Dupont
2003-03-04 11:02 ` DervishD
2003-03-04 12:09 ` Kasper Dupont
2003-03-04 14:53 ` DervishD
2003-03-02 12:51 ` DervishD
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=87u1er71d0.fsf@goat.bogus.local \
--to=olaf.dietsche@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron-office.nl \
/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