From: Arjan van de Ven <arjan@infradead.org>
To: "pablo.ferlop@gmail.com" <pablo.ferlop@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: string to inode conversion
Date: Sun, 15 Jan 2006 20:24:14 +0100 [thread overview]
Message-ID: <1137353054.3230.8.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1137351430.11284.2.camel@localhost.localdomain>
On Sun, 2006-01-15 at 19:57 +0100, pablo.ferlop@gmail.com wrote:
> Hi
>
> I was wondering how I can get from a string with a path like "/home" or
> "/lib/libc-2.3.5.so" a struct inode.
which namespace do you want this in? The init one? or the one from the
user? (most traditional linux distributions only have one namespace, but
now that COW namespaces are merged I expect distros to start
experimenting with per user /tmp, or per-daemon data etc etc)
This is not a trivial thing... you need a "context" into which you can
ask that question (basically a process)
next prev parent reply other threads:[~2006-01-15 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 18:57 pablo.ferlop
2006-01-15 19:24 ` Arjan van de Ven [this message]
2006-01-15 19:49 ` pablo.ferlop
2006-01-15 20:27 ` Bob Copeland
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=1137353054.3230.8.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pablo.ferlop@gmail.com \
/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
all inboxes | Powered by JetHome®