From: Isaac Dunham <ibid.ag@gmail.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: Trying to avoid incompatability on a mount enhancement
Date: Mon, 16 Mar 2015 17:19:59 +0000 [thread overview]
Message-ID: <20150316171958.GA13750@newbook> (raw)
In-Reply-To: <20150316102233.GA28925@ws.net.home>
On Mon, Mar 16, 2015 at 11:22:33AM +0100, Karel Zak wrote:
> On Sat, Mar 14, 2015 at 10:02:50PM +0000, Isaac Dunham wrote:
> > Hello,
> > I've been thinking about adding a feature to Busybox mount, but I'd
> > like to check on options that are already claimed in util-linux so I
> > don't cause a major incompatability.
> >
> > The feature I'm thinking about is roughly analogous to "mkdir -p" or
> > "cpio -d":
> > it creates the mountpoints if needed.
>
> man mount:
>
> x-mount.mkdir[=mode]
>
> Allow to make a target directory (mountpoint). The
> optional argument mode specifies the filesystem access mode
> used for mkdir(2) in octal notation. The default mode is
> 0755. This functionality is supported only for root users.
>
>
> ... so:
>
> mount /dev/sda1 /mnt/foo -o x-mount.mkdir
>
Thank you for responding.
I read about that some time after I sent the email; now comes the question
of whether Busybox will accept it.
I've already gotten a comment to the effect that x-mount.mkdir is "ugly"
(no clarifications provided), and that it's lacking the ability to set
owner/group for the mountpoint.
(The individual who opposes this is arguing in favor of adding a similar
but more expanded capability to mdev, the Busybox hotplugger.)
Thanks,
Isaac Dunham
next prev parent reply other threads:[~2015-03-16 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 22:02 Trying to avoid incompatability on a mount enhancement Isaac Dunham
2015-03-16 10:22 ` Karel Zak
2015-03-16 17:19 ` Isaac Dunham [this message]
2015-03-16 20:23 ` Karel Zak
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=20150316171958.GA13750@newbook \
--to=ibid.ag@gmail.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.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 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.