On Sun, 5 Nov 2000, Barry K. Nathan wrote:
+CONFIG_INET_ECN
+ Explicit Congestion Notification (ECN) allows routers to notify
+ clients about network congestion, resulting in fewer dropped packets
+ and increased network performance. This option adds ECN support to the
+ Linux kernel,
On Mon, 6 Nov 2000, David Woodhouse wrote:
On Mon, 6 Nov 2000, Oliver Xymoron wrote:
If I understand you correctly:
process 1 process 2
...
Is there any reason we ever want to unblock process 1 before process 2
terminates?
No, and I don't think we do. That's
On Wed, 25 Oct 2000, Martin Mares wrote:
> Hello!
>
> > "The Linux 'original' IDE guy' Mark Lord showed Alan what was trying to
> > bang over everyone's head, without success.
> >
> > Here is his sample code for cs5530 chipset.
> >
> > Look at this and comment. I have part of the space setup
On Wed, 25 Oct 2000, Martin Mares wrote:
Hello!
"The Linux 'original' IDE guy' Mark Lord showed Alan what was trying to
bang over everyone's head, without success.
Here is his sample code for cs5530 chipset.
Look at this and comment. I have part of the space setup to complete
On Tue, 24 Oct 2000, Pavel Machek wrote:
> Hi!
>
> > > [EMAIL PROTECTED] said:
> > > > You can also pretty trivially keep track of an error term so that the
> > > > clock is right on average:
> > >
> > > True, but I don't want 'right on average'. I want 'not screwed with at all'.
> > >
On Tue, 24 Oct 2000, Pavel Machek wrote:
Hi!
[EMAIL PROTECTED] said:
You can also pretty trivially keep track of an error term so that the
clock is right on average:
True, but I don't want 'right on average'. I want 'not screwed with at all'.
Shifting the timer tick
On Mon, 23 Oct 2000, David Woodhouse wrote:
>
> [EMAIL PROTECTED] said:
> > You can also pretty trivially keep track of an error term so that the
> > clock is right on average:
>
> True, but I don't want 'right on average'. I want 'not screwed with at all'.
> Shifting the timer tick onto the
On Mon, 23 Oct 2000, David Woodhouse wrote:
> See arch/i386/kernel/time.c:
>
> /* This function must be called with interrupts disabled
> * It was inspired by Steve McCanne's microtime-i386 for BSD. -- jrs
> *
> * However, the pc-audio speaker driver changes the divisor so that
> * it
On Mon, 23 Oct 2000, David Woodhouse wrote:
See arch/i386/kernel/time.c:
/* This function must be called with interrupts disabled
* It was inspired by Steve McCanne's microtime-i386 for BSD. -- jrs
*
* However, the pc-audio speaker driver changes the divisor so that
* it gets
On Mon, 23 Oct 2000, David Woodhouse wrote:
[EMAIL PROTECTED] said:
You can also pretty trivially keep track of an error term so that the
clock is right on average:
True, but I don't want 'right on average'. I want 'not screwed with at all'.
Shifting the timer tick onto the RTC will
On Sat, 14 Oct 2000, Mike A. Harris wrote:
> The 2.4.0test9 Changes file mentions the following and I'd like
> to know if after installing updated packages, if I'll still be
> able to use a 2.2.x kernel ok, or if I'll have to resort to
> initscript trickery:
>
> Will the following work with
On Sat, 14 Oct 2000, Mike A. Harris wrote:
The 2.4.0test9 Changes file mentions the following and I'd like
to know if after installing updated packages, if I'll still be
able to use a 2.2.x kernel ok, or if I'll have to resort to
initscript trickery:
Will the following work with 2.2.17 as
On Wed, 11 Oct 2000, Kiril Vidimce wrote:
> My primary concern is whether a process can allocate more than 4 GB of
> memory, rather than just be able to use more than 4 GB of physical
> memory in the system.
Define allocate. There are tricks you can play, but userspace is still a
flat 32-bit
On Thu, 12 Oct 2000, Keith Owens wrote:
> If anything is going to detect the mismatch and complain, it has to be
> the boot loader, after uncompressing and before entering the kernel
> proper.
Perhaps we can add the processor type to linux_banner and print it from
setup.S.
--
"Love the
On Thu, 12 Oct 2000, Keith Owens wrote:
If anything is going to detect the mismatch and complain, it has to be
the boot loader, after uncompressing and before entering the kernel
proper.
Perhaps we can add the processor type to linux_banner and print it from
setup.S.
--
"Love the
On Wed, 11 Oct 2000, Kiril Vidimce wrote:
My primary concern is whether a process can allocate more than 4 GB of
memory, rather than just be able to use more than 4 GB of physical
memory in the system.
Define allocate. There are tricks you can play, but userspace is still a
flat 32-bit
On Wed, 11 Oct 2000, Keith Owens wrote:
> Yes. I am usually up to date on pre patches within a few hours of
> their release, but then I have to play catch up to get my own patches
> up to date. What I would like is the ability to see what is in the
> kernel CVS tree before the pre patch is
On Wed, 11 Oct 2000, Keith Owens wrote:
Yes. I am usually up to date on pre patches within a few hours of
their release, but then I have to play catch up to get my own patches
up to date. What I would like is the ability to see what is in the
kernel CVS tree before the pre patch is sent
On Mon, 25 Sep 2000, Oliver Xymoron wrote:
> On my /home partition, mkdir(2) is returning EIO on ext2fs for uid!=0.
> Creating files with touch still works though. Persists after reboot,
> forced e2fsck finds nothing wrong.
>
> About to try test9-pre6 but thought I'd mention it.
On Mon, 25 Sep 2000, Alan Cox wrote:
> > > > Stupidity has no limits...
> > >
> > > Unfortunately its frequently wired into the hardware to save a few cents on
> > > scatter gather logic.
> >
> > Since when hardware folks became exempt from the rule above? 128K is
> > almost tolerable, there
On my /home partition, mkdir(2) is returning EIO on ext2fs for uid!=0.
Creating files with touch still works though. Persists after reboot,
forced e2fsck finds nothing wrong.
About to try test9-pre6 but thought I'd mention it.
--
"Love the dolphins," she advised him. "Write by W.A.S.T.E.."
On my /home partition, mkdir(2) is returning EIO on ext2fs for uid!=0.
Creating files with touch still works though. Persists after reboot,
forced e2fsck finds nothing wrong.
About to try test9-pre6 but thought I'd mention it.
--
"Love the dolphins," she advised him. "Write by W.A.S.T.E.."
On Mon, 25 Sep 2000, Alan Cox wrote:
Stupidity has no limits...
Unfortunately its frequently wired into the hardware to save a few cents on
scatter gather logic.
Since when hardware folks became exempt from the rule above? 128K is
almost tolerable, there were requests for 64
On Mon, 25 Sep 2000, Oliver Xymoron wrote:
On my /home partition, mkdir(2) is returning EIO on ext2fs for uid!=0.
Creating files with touch still works though. Persists after reboot,
forced e2fsck finds nothing wrong.
About to try test9-pre6 but thought I'd mention it.
Figured it out. Ran
On Thu, 21 Sep 2000, Mao Yun wrote:
> Hi all,
> Is there any T/TCP patch for kernel 2.2.16? thanks.
Maybe, but you don't want it. T/TCP is inherently insecure.
--
"Love the dolphins," she advised him. "Write by W.A.S.T.E.."
-
To unsubscribe from this list: send the line "unsubscribe
On Fri, 22 Sep 2000, Keith Owens wrote:
> On Thu, 21 Sep 2000 18:54:33 -0400 (EDT),
> Byron Stanoszek <[EMAIL PROTECTED]> wrote:
> >On Fri, 22 Sep 2000, Keith Owens wrote:
> >> The idea is to write characters direct to the video screen during
> >> booting using a macro called VIDEO_CHAR.
> >
>
On Fri, 22 Sep 2000, Keith Owens wrote:
On Thu, 21 Sep 2000 18:54:33 -0400 (EDT),
Byron Stanoszek [EMAIL PROTECTED] wrote:
On Fri, 22 Sep 2000, Keith Owens wrote:
The idea is to write characters direct to the video screen during
booting using a macro called VIDEO_CHAR.
Why not just
On Thu, 21 Sep 2000, Mao Yun wrote:
Hi all,
Is there any T/TCP patch for kernel 2.2.16? thanks.
Maybe, but you don't want it. T/TCP is inherently insecure.
--
"Love the dolphins," she advised him. "Write by W.A.S.T.E.."
-
To unsubscribe from this list: send the line "unsubscribe
On Tue, 12 Sep 2000, Simon Huggins wrote:
> On Tue, Sep 12, 2000 at 01:41:45AM -0500, Oliver Xymoron wrote:
> > > > This is similar to my patch-names patch, which lets you add components
> > > > to uname too. IIRC, it was rejected because it made things eas
On Mon, 11 Sep 2000, Simon Huggins wrote:
> On Sat, Sep 09, 2000 at 11:59:41AM -0500, Oliver Xymoron wrote:
> > This is similar to my patch-names patch, which lets you add components
> > to uname too. IIRC, it was rejected because it made things easier.
>
> Erm? Not re
On Tue, 12 Sep 2000, Simon Huggins wrote:
On Tue, Sep 12, 2000 at 01:41:45AM -0500, Oliver Xymoron wrote:
This is similar to my patch-names patch, which lets you add components
to uname too. IIRC, it was rejected because it made things easier.
Erm? Not really. Not unless you want
[reposted for the benefit of anyone wondering what Linus was replying to]
On Sat, 9 Sep 2000, Oliver Xymoron wrote:
> On Sat, 9 Sep 2000, Linus Torvalds wrote:
>
> > I use revision control at work. We use CVS on steroids - CVS with a lo tof
> > the extensions availabl
On Sat, 9 Sep 2000, Daniel Phillips wrote:
> Simon Huggins wrote:
> > On Thu, Sep 07, 2000 at 08:46:56AM +1100, Keith Owens wrote:
> > ... and a few more times recent weeks ...
> >
> > >
> > > Why don't you look in linux/Documentation/Changes? That file exist
> > > precisely to stop repeated
On Sat, 9 Sep 2000, Daniel Phillips wrote:
Simon Huggins wrote:
On Thu, Sep 07, 2000 at 08:46:56AM +1100, Keith Owens wrote:
... and a few more times recent weeks ...
rant
Why don't you look in linux/Documentation/Changes? That file exist
precisely to stop repeated questions
[reposted for the benefit of anyone wondering what Linus was replying to]
On Sat, 9 Sep 2000, Oliver Xymoron wrote:
On Sat, 9 Sep 2000, Linus Torvalds wrote:
I use revision control at work. We use CVS on steroids - CVS with a lo tof
the extensions available, and with a "mad scien
On Wed, 6 Sep 2000, Linus Torvalds wrote:
> Apparently, if you follow the arguments, not having a kernel debugger
> leads to various maladies:
> - you crash when something goes wrong, and you fsck and it takes forever
>and you get frustrated.
> - people have given up on Linux kernel
On Thu, 31 Aug 2000, Alan Cox wrote:
> > /lib/modules//.config is a big step up from the current situation
> > and I'm grateful. But I do want /proc/config.gz in the kernel.
>
> So cat it with a magic lead in after the bzImage gzip block into the bzImage.
> If you dont even know what file you
On Thu, 31 Aug 2000, Alan Cox wrote:
/lib/modules/version/.config is a big step up from the current situation
and I'm grateful. But I do want /proc/config.gz in the kernel.
So cat it with a magic lead in after the bzImage gzip block into the bzImage.
If you dont even know what file you
101 - 138 of 138 matches
Mail list logo
