lkml.org 
[lkml]   [1996]   [May]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: sysvinit-2.60
I think any SUCH problem - whether init or the kernel - is a kernel problem.
It is not a problem for developpers, but for users. The problem is the lack
of coordination between kernel programming and "other" programming. 'ps' me
if I am incorrect. Their should be more awareness on part of kernel hackers,
that ruining the "API" has unforeseen impacts. Kernel developpers should be
more nice to users, as in Linux 96 is Windows 2000.

Anyway, when are we coming up with a snappy "Linux 2000" before Bill
"The Monster" Gates puts his foot in the door?

I do not have any such problems, but sometimes my colleagues have:
"It worked yesterday now it is broken." If Linux wants to be mainstream,
it got to be less destructive. I have now converted an industrial group
with a $3M budget to linux and they would like to get something for
their money :-)) - obviously linux is MORE than just hacking away on
the kernel.

WE are taking linux very seriously - even if we had to pay for it -
"no, you said it, you pay, not me".

If we would like to be the elephant couldn't we just ring a bell
before the porcelain is broken to notify the clerk to clean up?

As in "kernel-space--user-space" interaction? Or as in API -
APIs are sacred, let people know about changes IMMEDIATLEY if
anything changes? I've written a device driver for a since
deceased co-processor board (it WAS fast in 1993) and I have
sevreral generations of patches to cope with API changes.

Arno


\
 
 \ /
  Last update: 2005-03-22 13:37    [W:0.041 / U:8.904 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site