public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.17:Increase number of anonymous filesystems beyond 256?
Date: 18 Jan 2002 11:40:12 -0800	[thread overview]
Message-ID: <a29tms$s9v$1@cesium.transmeta.com> (raw)
In-Reply-To: <mailman.1011275640.16596.linux-kernel2news@redhat.com> <200201171855.g0HIt1314492@devserv.devel.redhat.com> <200201181212.g0ICCGq14563@bliss.uni-koblenz.de>

Followup to:  <200201181212.g0ICCGq14563@bliss.uni-koblenz.de>
By author:    Rainer Krienke <krienke@uni-koblenz.de>
In newsgroup: linux.dev.kernel
> 
> Now think of a setup where no user directory mounts are configured but the 
> whole directory of a NFS server with many users is exported. Of course this 
> makes things easyer for the NFS-system since only one mount is needed but on 
> the client you need to create link trees or something similar so the user 
> still can access his home under /home/<user> and not something like 
> /home/server1/<user>. Moreover even if you create link trees when you issue 
> commands like pwd you see the real path (eg /server1/<user>) instead of the 
> logical (/home/<user>). Such paths are soon written into scripts etc, so that 
> if the user is moved sometime later  things will be broken. 
> You simply loose a layer of abstraction if you do not mount the users dir 
> directly. The only other solution I know of would be amd. Amd automatically 
> places a link. But since we come from the sun world, we simply uses suns 
> automounter and there were no problems up to now. 
> 

This can easily be resolved with vfsbinds.  Even Sun has a specific
syntax in their automounter to deal with this
(server:common_root:tail).  If I ever do another autofs v3 release I
will probably try to incorporate that via vfsbinds.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  reply	other threads:[~2002-01-18 19:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1011275640.16596.linux-kernel2news@redhat.com>
2002-01-17 18:55 ` 2.4.17:Increase number of anonymous filesystems beyond 256? Pete Zaitcev
2002-01-18 12:12   ` Rainer Krienke
2002-01-18 19:40     ` H. Peter Anvin [this message]
2002-01-20 10:33       ` Rainer krienke
2002-01-20 10:37         ` H. Peter Anvin
2002-01-18 20:33     ` Horst von Brand
2002-01-19 22:07       ` H. Peter Anvin
2002-01-21 22:54     ` Pete Zaitcev
2002-01-18 12:26   ` Trond Myklebust
2002-01-21 12:40   ` Rainer Krienke
2002-01-22 10:25   ` Rainer Krienke
2002-01-22 10:40     ` Trond Myklebust
2002-01-22 13:08       ` Rainer Krienke
2002-01-22 13:28         ` Trond Myklebust
2002-01-22 15:23           ` Rainer Krienke
2002-01-22 15:40             ` Trond Myklebust
2002-01-22 17:45             ` Pete Zaitcev
2002-01-24  8:58               ` Rainer Krienke
2002-01-24 17:16                 ` Pete Zaitcev
2002-01-24 17:29                   ` Richard Gooch
2002-01-25  7:28                   ` Rainer Krienke
2002-01-25 17:41                     ` Pete Zaitcev
2002-01-25 18:34                       ` Richard Gooch
2002-01-25 18:42                         ` Pete Zaitcev
2002-01-22 19:45           ` Pete Zaitcev
     [not found] <200201171351.g0HDpdK05456@bliss.uni-koblenz.de.suse.lists.linux.kernel>
2002-01-17 17:49 ` Andi Kleen
2002-01-17 13:51 Rainer Krienke

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='a29tms$s9v$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --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