Util-Linux package development
 help / color / mirror / Atom feed
From: Isaac Dunham <ibid.ag@gmail.com>
To: util-linux@vger.kernel.org
Subject: Trying to avoid incompatability on a mount enhancement
Date: Sat, 14 Mar 2015 22:02:50 +0000	[thread overview]
Message-ID: <20150314220249.GC1808@Sparta> (raw)

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.
This could be done by calling mkdir -p, or by calling mkdir() from mount.
The point is to allow one to mount /dev, /sys and all their subsystems
in one pass by using 
mount -T /etc/vfstab -a -d
or something like that where /etc/vfstab contains (for example):
===
# Kernel filesystems to mount for bringing up the system
proc	/proc	proc	noexec,nodev,nosuid	0 0
sysfs	/sys	sysfs	noexec,nodev,nosuid	0 0
devfs	/dev	devtmpfs defaults		0 0
devshm	/dev/shm tmpfs	nodev,nosuid		0 0
devpts	/dev/pts devpts	noexec,nodev,nosuid	0 0
===

I'm thinking that the option should be ignored with -o bind,
because that may take a file or a directory.

Do you have any comments about the concept?

As far as I can see, -d, -m, and -p are all available (at least in
the version of util-linux mount that ships in Jessie).
Are there any plans to use any of these options?

Also, is there any interest in seeing this in util-linux mount?
(I'd assume some of the corresponding code would be added to libmount,
but I haven't really looked at util-linux code before--just Busybox and
Toybox mount(8) implementations.)

Thanks,
Isaac Dunham



             reply	other threads:[~2015-03-14 22:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-14 22:02 Isaac Dunham [this message]
2015-03-16 10:22 ` Trying to avoid incompatability on a mount enhancement Karel Zak
2015-03-16 17:19   ` Isaac Dunham
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=20150314220249.GC1808@Sparta \
    --to=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