lkml.org 
[lkml]   [2006]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] s390: Hypervisor File System
On Wed, 3 May 2006 14:51:53 +0200, Michael Holzheu wrote:
> Jörn Engel <joern@wohnheim.fh-wedel.de> wrote on 05/03/2006 02:33:39 PM:
>
> > Applications will depend on some arcane detail of your format. They
> > will depend on exactly five spaces in "foo bar". It does not even
> > matter if you documented "any amount of whitespace". The application
> > knows that it was five spaces and doesn't care. And once you change
> > it, the blame will be on you, because you broke existing userspace.
>
> Again, logically there is no difference between the two solutions. It does
> not matter, if you have one file with:
>
> <cpu>
> <0>
> <onlinetime = 4711>
> <\0>
> <\cpu>

Userspace can make your life hell by depending on indentation via 4
spaces. The problem is that you don't necessarily know that it does
until you managed to change indentation.

In a filesystem tree, it is fairly hard to make assumptions that are
later broken. It is by no means impossible, agreed. But the
"indentation" doesn't exist anymore. A file is part of a subdirectory
or it isn't. Opening tags without matching closing tags don't exist
either. List goes on.

In the end, both formats can get abused in ways you'd never foresee.
But the directory tree considerably raises the barrier.

Jörn

--
He who knows that enough is enough will always have enough.
-- Lao Tsu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-05-03 15:03    [W:0.184 / U:0.056 seconds]
©2003-2011 Jasper Spaans. Advertise on this site