[Linux-NTFS-Dev] Re: [PATCH] NTFS: Add force_rw mount option

[Yura P. <cha...@tu...>]

On Fri, 2004-12-17 at 20:02 +0200, Yura Pakhuchiy wrote:
> On Fri, 2004-12-17 at 11:14 +0000, Anton Altaparmakov wrote:
> > > people too dumb to use this options it's their own problem, we warned
> > 
> > 99.9% of people are too dumb.  No warning is sufficient.  You can tell
> > them "using this will destroy your data" and five minutes later they
> > will come back and say "linux ntfs is shit - it just destroyed all my
> > data".  They don't care that it told them it would.  They only care that
> > they *could* do it, so they did and now they blame us for trashing the
> > data.  That's how the world works I am afraid...  This has been proven
> > to be correct over and over again.
> 
> Why you are care so much about those dumbs? Many people cries "linux
> sucks", "windows rulez", etc. Do we care about them? No. So why we
> should care about those who cries "linux-ntfs is shit"? As for me I only
> want good ntfs driver for linux and it's doesn't matter for me if some
> dumbs treat it bad. Clever people will look at driver themselves and
> will decide themselves.
> 
> Many open source developers add dangerous options to their projects and
> don't care about dumbs. People who really know what they are doing
> benefit from this options. We can do "rm -rf /", mount dirty ext2fs
> volume read-write and many other things. I love linux, because it's not
> prevent me from doing anything. OTOH windows that try prevent users from
> almost all (in some case permit them, after tons of the stupid
> questions). But current linux driver behave even worse, it's doesn't
> permit unclean read-write mount at all.
> 
> I propose only turned of by default option (ext2fs driver will mount
> dirty volume by default, without any extra flags) with very scary
> warning. This option will be documented deep in <kernel
> source/Documentation/filesystems/ntfs.txt>. I think most of dumbs
> install kernel from rpm and even don't know about existence of this
> file.
> 
> > > Our write support is very poor, but volume is always marked dirty (in
> > > unclean shutdown case) even we nothing changed on it. IMHO we need some
> > > mechanism to regulate it.
> > 
> > It is only set dirty when something broken is found.  If something is
> > broken we do not want to write to this volume as we could make the
> > damage worse.
> 
> I meant: I mounted volume read-write, nothing changed on it, than I had
> power failure, after reboot I can write anything to it, but it's
I meant: I can *not* write.
> consist, because I don't changed anything on it before power failure.
> 
> Best regards,
> 	Yura
>