All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Mcdermott <smcdermott@questra.com>
To: nfs@lists.sourceforge.net
Subject: Re: (autofs) Re: Direct mounts on Linux
Date: Mon, 20 Jan 2003 23:03:18 -0500	[thread overview]
Message-ID: <20030121040318.GI10369@questra.com> (raw)
In-Reply-To: <p5wukzyx8m.fsf@lemming.engeast.baynetworks.com>

Paul Smith on Mon 20/01 22:53 -0500:
> Well, if you mount directly in / it can be a big problem, since
> commands like pwd etc. often use an algorithm that can hang if one of
> your direct mounts in / is unavailable.

mostly nowadays, `pwd' is a shell builtin that doesn't use the algorithm
you refer to, if I understand right (like /bin/pwd has to use, eg keep
going ..) instead keeping track internally.

but your point is a good one :)

(if only umount -f worked hehe see recent list archives)


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2003-01-21  4:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-20 18:02 Direct mounts on Linux Paul Smith
2003-01-20 21:41 ` Scott Mcdermott
2003-01-21  2:48   ` Paul Smith
2003-01-21  3:08     ` (autofs) " Scott Mcdermott
2003-01-21  3:53       ` Paul Smith
2003-01-21  4:03         ` Scott Mcdermott [this message]
2003-01-21  6:05           ` Paul Smith
2003-01-21  6:48             ` Scott Mcdermott
2003-01-21  7:05               ` Paul Smith
2003-01-21  7:23                 ` [OT] " Scott Mcdermott
2003-01-21  7:59                   ` Paul Smith
2003-01-21 22:59                 ` Ion Badulescu

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=20030121040318.GI10369@questra.com \
    --to=smcdermott@questra.com \
    --cc=nfs@lists.sourceforge.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.