From: DervishD <lkml@dervishd.net>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOM & [OT] util-linux-2.12e
Date: Mon, 20 Sep 2004 13:06:31 +0200 [thread overview]
Message-ID: <20040920110631.GJ5482@DervishD> (raw)
In-Reply-To: <UTC200409192205.i8JM52C25370.aeb@smtp.cwi.nl>
Hi Andries :)
* Andries.Brouwer@cwi.nl <Andries.Brouwer@cwi.nl> dixit:
> If we would put the mount options in /proc/mounts, and introduced
> a comment convention (say, the part starting with \: is ignored by
> the kernel but can be used by programs reading /proc/mounts),
> then /etc/mtab can die. Comments? Better solutions?
If you add a comment convention to /proc/mounts so you can use it
as a substitute for /etc/mtab, you will probably break the apps that
use /etc/mtab. I was wondering, then... does the kernel *read*
/proc/mounts contents? If the answer is no, then you can add all
syntactic noise you want to /proc/mounts, exporting options needed
for userspace programs, with no problem. You can make /proc/mounts to
look like /etc/mtab. That will solve most of the problems.
If the kernel needs to read /proc/mounts, then you have a
problem: you will need /etc/mtab as long as you have to use loop
devices, user mounts, etc.
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/
next prev parent reply other threads:[~2004-09-20 11:04 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 22:05 OOM & [OT] util-linux-2.12e Andries.Brouwer
2004-09-20 9:46 ` Olaf Hering
2004-09-20 10:12 ` Andreas Schwab
2004-09-20 10:54 ` DervishD
2004-09-20 11:43 ` Andreas Schwab
2004-09-20 11:51 ` Paulo Marques
2004-09-20 12:11 ` DervishD
2004-09-20 12:14 ` Andreas Schwab
2004-09-20 12:00 ` DervishD
2004-09-20 10:23 ` Roman Zippel
2004-09-20 10:56 ` Olaf Hering
2004-09-20 11:16 ` Roman Zippel
2004-09-20 11:26 ` Olaf Hering
2004-09-20 11:38 ` Roman Zippel
2004-09-20 11:50 ` Olaf Hering
2004-09-20 12:02 ` Roman Zippel
2004-09-20 12:07 ` Olaf Hering
2004-09-20 12:14 ` Roman Zippel
2004-09-20 12:19 ` Olaf Hering
2004-09-20 12:34 ` Roman Zippel
2004-09-20 12:38 ` Olaf Hering
2004-09-20 12:51 ` Andreas Schwab
2004-09-20 12:54 ` Olaf Hering
2004-09-20 13:19 ` CaT
2004-09-20 13:33 ` Andreas Schwab
2004-09-20 13:15 ` CaT
2004-09-20 10:59 ` DervishD
2004-09-20 13:24 ` Helge Hafting
2004-09-20 13:21 ` Olaf Hering
2004-09-20 13:32 ` Helge Hafting
2004-09-20 14:12 ` Herbert Poetzl
2004-09-21 7:20 ` Helge Hafting
2004-09-21 9:18 ` Herbert Poetzl
2004-09-20 15:24 ` Tonnerre
2004-09-20 11:11 ` David Gómez
2004-09-20 11:06 ` DervishD [this message]
2004-09-20 11:38 ` Xavier Bestel
2004-09-20 11:59 ` DervishD
2004-09-20 12:32 ` Xavier Bestel
2004-09-20 14:16 ` Herbert Poetzl
2004-09-21 16:45 ` Jari Ruusu
2004-09-21 21:26 ` Andries Brouwer
2004-09-22 17:05 ` Jari Ruusu
2004-09-22 18:39 ` Andries Brouwer
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=20040920110631.GJ5482@DervishD \
--to=lkml@dervishd.net \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.