On Fri, Aug 24, 2018 at 10:10 AM, David Howells <dhowells@xxxxxxxxxx> wrote: > Andy Lutomirski <luto@xxxxxxxxxxxxxx> wrote: > >> Hmm. Is it that case in the current patchset that you can do CMD_CREATE and >> reconfigure the result and some *other* existing mount will change? If so, >> that’s rather unfriendly to users. > > The default behaviour has to be the same as mount(2). > Why? Obviously mount(2) needs to keep working the way it does now. Most likely mount(8) also needs to retain its current behavior. But I don't see why the new API needs be bug-compatible with mount(2). --Andy
