All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Kolbe <lukas@einfachkaffee.de>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: nested automounts: bind and nfs
Date: Thu, 11 Oct 2007 12:49:24 +0200	[thread overview]
Message-ID: <1192099764.18125.3.camel@localhost> (raw)
In-Reply-To: <1192092341.3114.38.camel@raven.themaw.net>


Hi Ian!


> Congratulations Lucas you've managed to create an autofs map that the
> current autofs4 kernel module can't handle, well done.

D'Oh!

> I'll try to explain, but I can't be sure I'll be very clear.

I'm so sorry, I didn't mean to :)

It's just that I came into this situation where we're having
historically a Sun-based server (and client) park and are slowly and
(luckily) only partially switching to linux where it makes sense. The
system as you can imagine has grown over time (e.g. the last twenty-some
years IIRC, the oldest configuration file I touched was from 1994 I
think), and I now have to make linux fit into that ... I never would
have thought that Unix is _that_ much different from Unix. 

> Now the problem.

I *think* I understand what you describe there. If I were more
knowledgeable about the internals of Linux and autofs I could be of more
help :(

> The patch below should apply ok to most kernels you're using as there
> haven't been changes in this area for quite a while. It would be good if
> you could test this out and see if you observe any other side effects.

Looks fairly simple - shall I test it even with your warning in the
other mail?

> Ian

I really appreciate what you're doing, Ian. This is tough stuff and to
me it looks very scary.

-- 
Lukas

  parent reply	other threads:[~2007-10-11 10:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01 14:08 nested automounts: bind and nfs Lukas Kolbe
2007-10-01 14:17 ` Lukas Kolbe
2007-10-02  4:53 ` Ian Kent
2007-10-02 10:25   ` Lukas Kolbe
     [not found]   ` <1191321007.27255.12.camel@localhost>
     [not found]     ` <1191332917.26331.171.camel@raven.themaw.net>
2007-10-02 14:40       ` Lukas Kolbe
2007-10-10 14:15       ` Lukas Kolbe
2007-10-10 14:34         ` Lukas Kolbe
2007-10-10 15:15         ` Ian Kent
2007-10-10 15:29           ` Lukas Kolbe
2007-10-10 16:47             ` Ian Kent
2007-10-10 17:02               ` Lukas Kolbe
2007-10-11  8:45                 ` Ian Kent
2007-10-11  9:11                   ` Ian Kent
2007-10-11 10:49                   ` Lukas Kolbe [this message]
2007-10-11 11:43                     ` Ian Kent
2007-10-11 13:43                       ` Success! (was: Re: nested automounts: bind and nfs) Lukas Kolbe
2007-10-11 14:36                         ` Ian Kent
2007-10-17 10:19                   ` nested automounts: bind and nfs Lukas Kolbe
2007-10-11  3:13         ` Ian Kent
2007-10-11  8:24           ` Lukas Kolbe
2007-10-02  5:03 ` Ian Kent
2007-11-08 16:44 ` Lukas Kolbe

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=1192099764.18125.3.camel@localhost \
    --to=lukas@einfachkaffee.de \
    --cc=autofs@linux.kernel.org \
    --cc=raven@themaw.net \
    /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.