public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Which process context does /sbin/hotplug run in?
Date: Sun, 14 May 2006 20:08:39 -0400	[thread overview]
Message-ID: <200605142008.39420.rob@landley.net> (raw)
In-Reply-To: <F68E5CEA-AB95-4E1C-9923-0882394AE16E@mac.com>

On Saturday 13 May 2006 3:24 am, Kyle Moffett wrote:
> /
>    /var
>      /var/sub
>      /var/sub2
>        /var/sub2/sub
>        /var/sub2/sub2
>
> The recursion ends there.  Basically with the first bind mount you
> attach the same instance of tmpfs to /tmp and /var, then you move the
> tmpfs from /tmp to the "/sub2" directory in the "/var" tmpfs
> _mountpoint_.  It's kind of confusing behavior; but the directory
> tree and the mount tree are basically kind of separate entities in a
> sense.

I can CD into them endlessly, and both "ls -lR" and "find ." report cycles in 
the tree, which surprised me that they had a specific error message for that, 
actually.  Good enough for me. :)

And I'm not _complaining_ about it.  Just fiddling around with fun stuff.  If 
I get really bored I'll figure a way to split the tree so there are two 
completely unconnected mount trees in different processes.  (Get a private 
namespace that's chrooted into something that somebody else does a umount -l 
on from their space.  Or without using umount -l, just have two processes 
chroot into other mount points which should theoretically garbage collect the 
old root if no processes still references it, which presumably means one of 
the processes is init...)

Don't mind me, I do this for fun.

Rob
-- 
Never bet against the cheap plastic solution.

  reply	other threads:[~2006-05-15  0:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-12 18:20 Which process context does /sbin/hotplug run in? Rob Landley
2006-05-13  7:24 ` Kyle Moffett
2006-05-15  0:08   ` Rob Landley [this message]
2006-05-15  4:17     ` Kyle Moffett
2006-05-15  4:28       ` Joshua Hudson
2006-05-15 19:59       ` Rob Landley
2006-05-15 22:22         ` Kyle Moffett

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=200605142008.39420.rob@landley.net \
    --to=rob@landley.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.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