From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] lscp: support opening mounted filesystem by directory pathname
Date: Wed, 02 Mar 2011 20:23:45 +0900 (JST) [thread overview]
Message-ID: <20110302.202345.74569955.ryusuke@osrg.net> (raw)
In-Reply-To: <201103021113.32637.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hi,
On Wed, 2 Mar 2011 11:13:32 +0100, dexen deVries wrote:
> The patch I've submited may be a wrong solution; perhaps instead the algorithm
> of nilfs_find_fs() (around lib/nilfs.c:179,211) should be improved.
>
> Regards,
Well, allowing directory pathname for nilfs commands seems a good idea
to me. Why not apply it to other commands except nilfs_cleanerd ?
I think you can simply the callsite of nilfs_open() just like follows:
char *dev = NULL, *dir = NULL;
...
stat(pathname, &statbuf);
if (S_ISDIR(statbuf.st_mode))
dir = pathname;
else
dev = pathname;
nilfs = nilfs_open(dev, dir, NILFS_OPEN_RDONLY);
...
Thanks,
Ryusuke Konishi
> --
> dexen deVries
>
> [[[↓][→]]]
>
> > how does a C compiler get to be that big? what is all that code doing?
>
> iterators, string objects, and a full set of C macros that ensure
> boundary conditions and improve interfaces.
>
> ron minnich, in response to Charles Forsyth
>
> http://9fans.net/archive/2011/02/90
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-02 11:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 10:13 [PATCH] lscp: support opening mounted filesystem by directory pathname dexen deVries
[not found] ` <201103021113.32637.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-03-02 11:23 ` Ryusuke Konishi [this message]
[not found] ` <20110302.202345.74569955.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-03-02 12:43 ` dexen deVries
[not found] ` <201103021343.54036.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-03-02 14:21 ` Ryusuke Konishi
[not found] ` <20110302.232110.169818198.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-03-03 12:47 ` [PATCH 1/8] " dexen deVries
[not found] ` <1299156472-4707-1-git-send-email-dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-03-03 12:47 ` [PATCH 2/8] chcp: " dexen deVries
2011-03-03 12:47 ` [PATCH 3/8] dumpseg: " dexen deVries
2011-03-03 12:47 ` [PATCH 4/8] lssu: " dexen deVries
2011-03-03 12:47 ` [PATCH 5/8] mkcp: " dexen deVries
2011-03-03 12:47 ` [PATCH 6/8] rmcp: " dexen deVries
2011-03-03 12:47 ` [PATCH 7/8] bin/*: update inline help to indicate possibility of accessing filesystem by mountpoint pathname dexen deVries
2011-03-03 12:47 ` [PATCH 8/8] update manpages to indicate open-by-mountpoint dexen deVries
2011-03-03 16:15 ` [PATCH 1/8] lscp: support opening mounted filesystem by directory pathname Ryusuke Konishi
[not found] ` <20110304.011511.83301246.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-03-03 16:23 ` dexen deVries
[not found] ` <201103031723.22583.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-03-03 17:16 ` Ryusuke Konishi
[not found] ` <20110304.021603.234305303.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-03-03 18:31 ` dexen deVries
[not found] ` <201103031931.32310.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-03-04 10:26 ` Ryusuke Konishi
[not found] ` <20110304.192609.247659638.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-03-04 11:21 ` Ryusuke Konishi
-- strict thread matches above, loose matches on Subject: below --
2011-03-02 9:56 [PATCH] " dexen deVries
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=20110302.202345.74569955.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).