Re: what's next for the linux kernel?
From: Luke Kenneth Casson Leighton (lkcl_at_lkcl.net)
Date: 10/06/05
- Previous message: Robert Derr: "Re: 2.6.13.3 Memory leak, names_cache"
- In reply to: Michael Concannon: "Re: what's next for the linux kernel?"
- Next in thread: Michael Concannon: "Re: what's next for the linux kernel?"
- Reply: Michael Concannon: "Re: what's next for the linux kernel?"
- Reply: Howard Chu: "Re: what's next for the linux kernel?"
- Reply: Helge Hafting: "Re: what's next for the linux kernel?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 6 Oct 2005 22:20:01 +0100 To: Michael Concannon <mike@concannon.net>
On Thu, Oct 06, 2005 at 04:13:15PM -0400, Michael Concannon wrote:
> 1. It _is_ a file: registry.dat
> 2. It is a binary file at that...
> 3. That file has become a dumping ground for everything that every app
> thinks is "important" and of course every app writer thinks everything
> they write is the most important thing ever - I am sure a have never
> done such a thing :-)
s/"that file"/"openldap" and substitute "every app writer"
for "every major free software developer we respect greatly which
can store its data and/or configuration details in an LDAP database"
and your evident distaste for "that file" looks a little like religious
zealotry.
i say that with the greatest respect.
especially when "that file" is actually a database, just like
Berkeley DB (and we all know and _love_ Berkeley DB).
and especially in light it being possible to do a "decent" job, and
make "that file" available via a POSIX filesystem interface.
l.
> I guess you could argue that #3 is the fault of the app writers and not
> the architecture,
yes. i would say it's more to do with the dumb-ass nature of the app
writers, yes. typicall dumb-ass windows app writers give a *** about
security and care greatly about making money hand-over-fist.
whereas on linux it's far less likely for an app writer to
be able to get away with a) making money b) friggin up security. the
distros wouldn't allow an app writer to get away with either.
l.
-
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/
- Previous message: Robert Derr: "Re: 2.6.13.3 Memory leak, names_cache"
- In reply to: Michael Concannon: "Re: what's next for the linux kernel?"
- Next in thread: Michael Concannon: "Re: what's next for the linux kernel?"
- Reply: Michael Concannon: "Re: what's next for the linux kernel?"
- Reply: Howard Chu: "Re: what's next for the linux kernel?"
- Reply: Helge Hafting: "Re: what's next for the linux kernel?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]