linux-kernel - Re: Thinking outside the box on file systems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <1187202192.30730.25.camel@wombat.dlib.indiana.edu>
Date:	Wed, 15 Aug 2007 14:23:12 -0400
From:	Brian Wheeler <bdwheele@...iana.edu>
To:	mperkel@...oo.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Thinking outside the box on file systems

HI

While I find your ideas intriguing, I'd like to offer a friendly
suggestion:  You're never going to convince anyone on LKML unless you do
the following things:
	* Describe your idea in detail, including algorithms, pseudo code,
pictures, or whatever.  Vague hand-wavey stuff won't do it.
	* Don't accuse others of being close minded (i.e. "not thinking outside
the box").  Explain why their assertions may not be correct according to
your proposal.
	* Accept that others have far more experience, no matter how
experienced you are.
	* Remember that the current assumptions can't just break when the idea
is implemented:  backwards compatibility is important.

Also, be prepared to have your idea shot down.  Very few ideas make it
into the kernel, and those only get there after months of hashing out
the details.

Brian

--- Kyle Moffett <mrmacman_g4@....com> wrote:

> On Aug 15, 2007, at 13:19:16, Marc Perkel wrote:
> > One of the problems with the Unix/Linux world is
> that your minds  
> > are locked into this one model. In order to do it
> right it requires  
> > the mental discipline to break out of that.
> 
> The major thing that you are missing is that this
> "one model" has  
> been very heavily tested over the years.  People
> understand it, know  
> how to use it and write software for it, and grok
> its limitations.   
> There's also a vast amount of *existing* code that
> you can't just  
> "deprecate" overnight; the world just doesn't work
> that way.  The  
> real way to get there (IE: a new model) from here
> (IE: the old model)  
> is the way all Linux development is done with a lot
> of sensible easy- 
> to-understand changes and refactorings.
> 
> With that said, if you actually want to sit down and
> start writing  
> *code* for your model, go ahead.  If it turns out to
> be better than  
> our existing model then I owe you a bottle of your
> favorite beverage.
> 
> Cheers,
> Kyle Moffett
> 


When one thinks outside the box one has to think about
evolving beyond what you are used to. When I moved
beyond DOS I have to give up the idea of 8.3 file
names. The idea here is to come up with a model that
can emulate the existing system for backwards
compatibility.

The concept behind my model is to create a new layer
where you can do ANYTHING with file names and
permissions and create models that emulate Linux, DOS,
Windows, Mac, or anything else you can dream of. Then
you can create a Linux/Windows/Mac template to emulate
what you are used to.


Marc Perkel
Junk Email Filter dot com
http://www.junkemailfilter.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/