From: Edgar Toernig <froese@gmx.de>
To: Alexander Viro <viro@math.psu.edu>
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org
Subject: Re: symlink_prefix
Date: Thu, 07 Jun 2001 03:00:35 +0200 [thread overview]
Message-ID: <3B1ED233.CCF2942D@gmx.de> (raw)
In-Reply-To: <Pine.GSO.4.21.0106030703590.27673-100000@weyl.math.psu.edu>
Alexander Viro wrote:
> ...
> dir = open("/usr/local", O_DIRECTORY);
> /* error handling */
> new_mount(dir, MNT_SET, fs_fd); /* closes dir and fs_fd */
Do you really want to start using fds instead of strings for tree
modifying commands (link, unlink, symlink, rename, mount and umount)?
Even if it were possible in the new_mount case it wouldn't have the
atomic lookup+act nature of the old mount. And then, _I_ would
prefer a uniform interface for tree management commands - strings.
Ciao, ET.
next prev parent reply other threads:[~2001-06-07 1:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-03 10:53 symlink_prefix Andries.Brouwer
2001-06-03 11:25 ` symlink_prefix Alexander Viro
2001-06-04 11:53 ` symlink_prefix Remi Turk
2001-06-05 12:43 ` symlink_prefix Pavel Machek
2001-06-07 1:00 ` Edgar Toernig [this message]
2001-06-07 1:19 ` symlink_prefix Alexander Viro
2001-06-07 3:43 ` symlink_prefix Edgar Toernig
-- strict thread matches above, loose matches on Subject: below --
2001-06-04 12:28 symlink_prefix Hank Leininger
2001-06-05 2:31 ` symlink_prefix Ton Hospel
2001-06-03 17:37 symlink_prefix Andries.Brouwer
2001-06-03 16:36 symlink_prefix Andries.Brouwer
2001-06-03 17:19 ` symlink_prefix Alexander Viro
2001-06-04 22:05 ` symlink_prefix Albert D. Cahalan
2001-06-03 15:10 symlink_prefix Andries.Brouwer
2001-06-03 15:27 ` symlink_prefix Alexander Viro
2001-06-02 23:54 symlink_prefix Andries.Brouwer
2001-06-03 0:23 ` symlink_prefix Robert Love
2001-06-03 0:49 ` symlink_prefix Alexander Viro
2001-06-03 1:00 ` symlink_prefix Mitchell Blank Jr
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=3B1ED233.CCF2942D@gmx.de \
--to=froese@gmx.de \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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.