noying Linus
>with real no-changing -rc's. How many more, enough or not, remains to be
> seen but certainly more.
One way to handle the transition into bug-fix only would be to turn
the tree over to the $stability crew at that moment. They would have
the job of nursing it to stabili
ve been multiple comments that a fix for the problem is
forthcoming. Is there some reason you have to keep talking about it?
John alvord
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
f the other qualities in trivial areas.
>
>I guess what I'm trying to say is that "Life With Unix" should be required
>reading for anyone who goes near a Unix (or Linux) system.
David N. Smith, an IBM researcher, wrote that we should preserve the
past for the criticism o
d, hardware or software,
data being held or transformed can change. Old lesson but a good one
to know.
john alvord
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
The
granularity was 1 millsecond. Over time, all timer values from 0 to
roughly 10 minutes had been used. That resulted in 60,000 permanent
storage fragments laying about... a significant fragmentation problem.
The end was a forced recycle every month or so.
john alvord
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
e REALLY wants to continue and wait for a response.
Following is the model code...
John Alvord
=
_ECHO=@
all: t0 t1 t2 t3 t4 t5 t6
# prompt for input, must be in a separate rule to unbuffer terminal
# output.
t0:
$(_ECHO)echo Enter Y or N: \\c
# capture a line of ter
egal
action.
Why are we distributing such severely broken software? Heck, we seem
reluctant to include reiserfs, a pretty high quality, supported file
system. And we continue to distribute this !@#$%... There must be some
strange agenda going on to limit the use of Linux.
john alvord
-
To unsubs
e details of the kernel C
environment. In particular I do not know that all static variables are
initialized to 0 in the kernel startup. I have not read setup.S."
john alvord
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
s with
obj-$(CONFIG_WD80x3) += wd.o
ifneq (,$(findstring 8390.o,obj-$(CONFIG_WD80x3))
obj-$(CONFIG_WD80x3) += 8390.o
endif
Which is wordy but accomplishes the objective of avoiding duplicates.
john alvord
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Mon, 16 Oct 2000 14:45:03 +0200 (CEST), Igmar Palsenberg
<[EMAIL PROTECTED]> wrote:
>
>> >I presume your driver doesn't mind if this image is unavailable.
>> >If not, you'll need to provide a open source image to use in place
>> >of your proprietary one.
>>
>> Linus, please confirm.
>>
>> F
On Wed, 11 Oct 2000 02:06:52 +0200 (MET DST), Roman Zippel
<[EMAIL PROTECTED]> wrote:
>Hi,
>
>On Wed, 11 Oct 2000, Alan Cox wrote:
>
>> > http://www.osopinion.com/Opinions/MontyManley/MontyManley15.html
>> >
>> > good article, several unfortunate truths within.
>>
>> Really, must be a wrong URL
rest.
Clearly, the same idea has been rediscovered over and over again. The
VM/CMS case would be a good example of prior art, since it had
thousands of licenses and hundreds of thousands of end users in the
early 1980s.
john alvord
-
To unsubscribe from this list: send the line "unsubs
On Wed, 20 Sep 2000 22:37:29 -0700, "Lyle Coder" <[EMAIL PROTECTED]>
wrote:
>Hi
>The real issue is that if you use MMX or FP state, the kernel _must_ save
>and restore the original state other wise user programs will see corruption.
>We all know this too well since redhat's 6.1 (I think) kernel h
fit well with people who
>used their brains. I see it is as alive and well here as on the
>streets of East LA.
>
>{O.O}
How can anyone judge that a debugger was used in development of a
patch, along with system understanding, Linux knowledge, etc? The
changed code stands along with no provenance. If it reflects a shallow
understanding, it will be rejected. If it is a deep elegant fix, that
will stand on its merits.
john alvord
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
14 matches
Mail list logo
