From: Karel Zak <kzak@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: util-linux-ng@vger.kernel.org
Subject: Re: fsck files w/relative paths
Date: Fri, 25 Jan 2013 16:17:36 +0100 [thread overview]
Message-ID: <20130125151736.GP27413@x2.net.home> (raw)
In-Reply-To: <201301201827.23141.vapier@gentoo.org>
On Sun, Jan 20, 2013 at 06:27:22PM -0500, Mike Frysinger wrote:
> we could tweak parse_argv() so that it checks for argv[0] == '.' in addition
> to argv[0] == '/'. but that wouldn't fix other relative paths like:
> $ fsck images/foo
> $ fsck foo
Hmm... maybe add a hint to the fsck man page is the best solution :-)
> should we treat all non-options as devices ? would that break anything ?
I don't think it's a good idea.
All unknown stuff is by default interpreted as filesystem specific options
(options for fsck.<type>) and it's pretty common that people don't use
"--" separator between fsck and fsck.<type> options.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2013-01-25 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 23:27 fsck files w/relative paths Mike Frysinger
2013-01-25 15:17 ` Karel Zak [this message]
2013-01-25 17:02 ` Mike Frysinger
2013-01-25 17:36 ` Karel Zak
2013-01-25 19:55 ` Mike Frysinger
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=20130125151736.GP27413@x2.net.home \
--to=kzak@redhat.com \
--cc=util-linux-ng@vger.kernel.org \
--cc=vapier@gentoo.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