On Wed, Aug 06, 2008 at 11:44:22AM +1200, Jasper Bryant-Greene wrote:Sure. But that does not answer my question about what to do with options that can't be changed. Options can come from more than just /etc/fstab - they can come from the mount command line itself as entered by the admin. What do we do if an option is specified that we do not support in a remount? The problem is the way mount combines command line options with options in fstab. I'm not questioning what you did - I'm asking what the expected behaviour is supposed to be so we can make it behave the same way as all the other filesystems. Use the full device/directory syntax for the remount command and it will do just that. The command you issued was not a "pure" remount,rw, it was silently changed by mount.... Cheers, Dave. -- Dave Chinner david@fromorbit.com --
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| Adrian Bunk | [1/6] 2.6.21-rc2: known regressions |
| Paul Jackson | Re: cpuset-remove-sched-domain-hooks-from-cpusets |
git: | |
| Linus Torvalds | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Andrew Morton | Re: [BUG] New Kernel Bugs |
