Re: [PATCH] hfsplus: add an option to force r/w mount

2005-04-20 Thread Colin Leroy
On 20 Apr 2005 at 22h04, Roman Zippel wrote: Hi, > > for some reason yet unknown, fsck.hfsplus doesn't correctly set the > > HFSPLUS_VOL_UNMNT flag here. > > If fsck doesn't mark it clean, there must be a reason By the way, the reason is that this stupid utility opens the device read-only

Re: [PATCH] hfsplus: add an option to force r/w mount

2005-04-20 Thread Colin Leroy
On 20 Apr 2005 at 22h04, Roman Zippel wrote: Hi, > Hi, > > On Wed, 20 Apr 2005, Colin Leroy wrote: > > > for some reason yet unknown, fsck.hfsplus doesn't correctly set the > > HFSPLUS_VOL_UNMNT flag here. > > If fsck doesn't mark it clean, there must be a reason and that also > means you

Re: [PATCH] hfsplus: add an option to force r/w mount

2005-04-20 Thread Roman Zippel
Hi, On Wed, 20 Apr 2005, Colin Leroy wrote: > for some reason yet unknown, fsck.hfsplus doesn't correctly set the > HFSPLUS_VOL_UNMNT flag here. If fsck doesn't mark it clean, there must be a reason and that also means you shouldn't mount it writable. bye, Roman - To unsubscribe from this

Re: [PATCH] hfsplus: add an option to force r/w mount

2005-04-20 Thread Roman Zippel
Hi, On Wed, 20 Apr 2005, Colin Leroy wrote: for some reason yet unknown, fsck.hfsplus doesn't correctly set the HFSPLUS_VOL_UNMNT flag here. If fsck doesn't mark it clean, there must be a reason and that also means you shouldn't mount it writable. bye, Roman - To unsubscribe from this

Re: [PATCH] hfsplus: add an option to force r/w mount

2005-04-20 Thread Colin Leroy
On 20 Apr 2005 at 22h04, Roman Zippel wrote: Hi, Hi, On Wed, 20 Apr 2005, Colin Leroy wrote: for some reason yet unknown, fsck.hfsplus doesn't correctly set the HFSPLUS_VOL_UNMNT flag here. If fsck doesn't mark it clean, there must be a reason and that also means you shouldn't

Re: [PATCH] hfsplus: add an option to force r/w mount

2005-04-20 Thread Colin Leroy
On 20 Apr 2005 at 22h04, Roman Zippel wrote: Hi, for some reason yet unknown, fsck.hfsplus doesn't correctly set the HFSPLUS_VOL_UNMNT flag here. If fsck doesn't mark it clean, there must be a reason By the way, the reason is that this stupid utility opens the device read-only (hence it