public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: RFC - named loop devices...
Date: Fri, 24 May 2002 16:40:33 -0700	[thread overview]
Message-ID: <20020524164033.B9600@pegasys.ws> (raw)
In-Reply-To: <20020521015517.609d5516.spyro@armlinux.org> <200205211409.g4LE9HY31513@Port.imtp.ilyichevsk.odessa.ua> <20020523180105.141af04b.spyro@armlinux.org> <20020523180453.E29960@flint.arm.linux.org.uk>

On Thu, May 23, 2002 at 06:04:53PM +0100, Russell King wrote:
> On Thu, May 23, 2002 at 06:01:05PM +0100, Ian Molton wrote:
> > On Tue, 21 May 2002 17:11:34 -0200
> > Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua> wrote:
> > 
> > > > I was wondering if a solution to this would be to introduce 'named'
> > > > loopback devices.
> > 
> > > Have no time to think about this now, but will test any patches -
> > > I want /etc/mtab -> /proc/mounts to become standard practice
> > 
> > me too. :-)
> 
> /proc/mounts and /etc/mtab contain different information.  /etc/mtab can
> contain what ever information a user space app needs.  /proc/mount can't.
> See the following as a perfect example, specifically the automount and
> NFS entries.
> 
> Also, remember that mount uses /etc/mtab to perform synchronisation
> between two concurrent mount requests for the same device/resource.
> 
[snip]

It is clear to me that what really needs to happen is to
retire /etc/mtab.  It seems to be the last file in /etc that
needs to be written.  Mount, df and others need to look
elsewhere and we might need a syscall (if it doesn't exist)
to support umount and root pivoting when not even proc is
mounted.  It might be a pain to coordinate but should be
worth it.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

      reply	other threads:[~2002-05-24 23:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21  0:55 RFC - named loop devices Ian Molton
2002-05-21  6:05 ` Frank Schaefer
2002-05-21 19:11 ` Denis Vlasenko
2002-05-23 17:01   ` Ian Molton
2002-05-23 17:04     ` Russell King
2002-05-24 23:40       ` jw schultz [this message]

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=20020524164033.B9600@pegasys.ws \
    --to=jw@pegasys.ws \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox