On Mon, 11 Dec 2000, James Simmons wrote:
> > > When built into the Kernel, by only pressing the
> > > PrintScreen/SysRq the current application is terminated (tested
> > > on a console and GNU screen). Is this just me or I should
> > > expect it?
Well this should happen even when sysrq is NOT
On Mon, 11 Dec 2000, James Simmons wrote:
When built into the Kernel, by only pressing the
PrintScreen/SysRq the current application is terminated (tested
on a console and GNU screen). Is this just me or I should
expect it?
Well this should happen even when sysrq is NOT compiled
Anyone know how to properly filter packet floods using iptables w/ nat?
>From my point of view 2.4.x:ish connection tracking seems to be quite
a bit more vulnerable to packet flooding than the 2.2.x:ish
IP Masquerading used to be (when using default configuration that is).
First we try to make
Anyone know how to properly filter packet floods using iptables w/ nat?
From my point of view 2.4.x:ish connection tracking seems to be quite
a bit more vulnerable to packet flooding than the 2.2.x:ish
IP Masquerading used to be (when using default configuration that is).
First we try to make
On Fri, 24 Nov 2000, Andre Hedrick wrote:
> Anyone having DMA errors that are dmaproc: error 14, there is not a clean
> workaround yet. Also the Intel erratas state that only a bus reset will
> clear the hang, but the details are loose.
We talking about errors like the following one? :
Nov 18
On Thu, 23 Nov 2000, Charles Cazabon wrote:
> [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > Thats because too many things get put on a line then.
> > > And because we do [] [] not [][] ?
> >
> > In the good old times we had foo bar for a total of 8*(8+1) = 72
> > positions. Now we
6 matches
Mail list logo
