[lkml]   [2004]   [Jan]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [autofs] [RFC] Towards a Modern Autofs
(sorry for the resend, forgot to CC the lists)

On Tue, Jan 06, 2004 at 02:06:34PM -0800, H. Peter Anvin wrote:
> > Can you maybe share some details? I think this deign moves MORE state to
> > userspace (expiry aside). The "state" in kernel is really mostly sent back
> > to userspace. No more passing pipes into the kernel (state) or tracking the
> > pgid of the daemon (state).
> If you want to fire up a new daemon, all that state that was supposed to
> be kept in userspace has to be reconstructed. That means the kernel has
> to have all that information; this would include stuff like what kind of
> umount policy you want for each key entry (the current daemon doesn't do
> that because it doesn't have the proper state.)

I'm not really sure what you're saying., here. I'm sorry. Not trying to be
thick, just not understanding.

What umount policy? What state is supposed to be kept in userspace that isn't?

> > The daemon as it stands does NOT handle namespaces, does NOT handle expiry
> > well, and is a pretty sad copy of an old design.
> First of all, I'll be blunt: namespaces currently provide zero benefit
> in Linux, and virtually noone uses them. I have discussed this with
> Linus in the past, and neither one of us see namespaces as being worth

Let's get rid of them, then. Make life that much easier.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:59    [W:0.106 / U:0.612 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site