Messages in this thread | | | Date | Thu, 27 Jul 2000 21:40:39 +0200 | From | Andries Brouwer <> | Subject | Re: multimounting cdroms ??? |
| |
On Thu, Jul 27, 2000 at 03:05:38PM -0400, Alexander Viro wrote:
> Wonderful. Could you add the following 4 options to mount(8): > -replace > -after > -before > -over > (syntax is completely up to you, but I would seriously recommend _not_ > using -o <foo> for that) and just pass them to the mount(2) in flags > (MNT_REPLACE, MNT_AFTER, MNT_BEFORE, MNT_OVER)? I'll add such flags and > restore the 2.2 behaviour for cases that existed in 2.2.
Done.
> Rules: > > none of these flags: same behaviour as in 2.2 > > MNT_REPLACE: remount, but new filesystem may be different from old. Atomic > (i.e. there is no interval when nothing is mounted at the mountpoint). If > new fs differs from the old one and old is busy - -EBUSY. > > MNT_AFTER, MNT_BEFORE: - as soon as we get unions these will add a > new member resp. in the end or beginning of the chain. Fail if there is a > stack on the mountpoint. > > MNT_OVER: if nothing mounted on a mountpoint - same as if none of these > flags had been set, if we have a union with more than one element - fail, > if we have a stack or plain mount - mount atop of it, forming a stack. > > If more than one of these bits is set - -EINVAL, they are obviously > mutually exclusive. > > Deal? BTW, while we are at it, could you add -bind (MNT_BIND) > option (can be combined with any of these)? -t bind syntax is a kludge and > I would be glad to get rid of it.
Deal.
Consider calling the constants MS_xxx for consistency with other constants. Consider putting them in <linux/mount_constants.h> since <linux/fs.h> contains such a lot of crap already.
Tell me the final names and values. (I expect to come with util-linux-2.10n soon.)
Andries
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |