From: Karel Zak <kzak@redhat.com>
To: Isaac Dunham <ibid.ag@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: Trying to avoid incompatability on a mount enhancement
Date: Mon, 16 Mar 2015 21:23:43 +0100 [thread overview]
Message-ID: <20150316202343.GO28925@ws.net.home> (raw)
In-Reply-To: <20150316171958.GA13750@newbook>
On Mon, Mar 16, 2015 at 05:19:59PM +0000, Isaac Dunham wrote:
> On Mon, Mar 16, 2015 at 11:22:33AM +0100, Karel Zak wrote:
> > 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"
Well, x-* prefixes are generic solution for userspace mount options,
we already use it for more things (for example systemd).
> (no clarifications provided), and that it's lacking the ability to set
> owner/group for the mountpoint.
Good point, it would be possible to extend it for example to
x-mount.mkdir[=mode:user:group]
where :user and :group are optional and may be specified by UID/GID
or by username/groupname.
> (The individual who opposes this is arguing in favor of adding a similar
> but more expanded capability to mdev, the Busybox hotplugger.)
I have no clue about busybox hotplugger, for standard udev we
usually don't want to do things like "mount" in udev context.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2015-03-16 20:23 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
2015-03-16 20:23 ` Karel Zak [this message]
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=20150316202343.GO28925@ws.net.home \
--to=kzak@redhat.com \
--cc=ibid.ag@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox