Re: The IPsec kernel problem

2003-10-06 Thread martin f krafft
also sprach Andreas Schuldei <[EMAIL PROTECTED]> [2003.10.06.2211 +0200]: > > From glancing over the patch, it *also* replaces parts of the > > non IPsec i.e. standard IP stack. Maybe it provides the same > > functionality to the end user. It does *not* provide the same > > functionality to the dev

Re: The IPsec kernel problem

2003-10-06 Thread Tom Badran
On Monday 06 October 2003 21:11, Andreas Schuldei wrote: > kernel developers dont use the debian source package as a base > for their work. I have in the past for writing device drivers. Admittedly none are in the mainstream kernel (afaik) but that is not the point. Tom -- ^__^| T

Re: The IPsec kernel problem

2003-10-06 Thread Andreas Schuldei
* martin f krafft ([EMAIL PROTECTED]) [031006 21:57]: > > The IPSEC stack does nothing unless you specify policies through > > PFKEY or NETLINK. In other words, it is disabled by default. > > From glancing over the patch, it *also* replaces parts of the non > IPsec i.e. standard IP stack. Maybe i

Re: The IPsec kernel problem

2003-10-06 Thread martin f krafft
also sprach Herbert Xu <[EMAIL PROTECTED]> [2003.10.03.1016 +0200]: > > I cannot disable IPsec at runtime as I cannot replace the IP stack > > at runtime, and it modifies the IP stack. Moreover, you state the > > The IPSEC stack does nothing unless you specify policies through > PFKEY or NETLINK.

Re: The IPsec kernel problem

2003-10-03 Thread Herbert Xu
martin f krafft <[EMAIL PROTECTED]> wrote: > > * If it's a feature, can it be disabled/enabled at runtime? > >Sinec we're making generic kernels, this is a must. The presence >of the patch should not prevent me from doing something that I would >otherwise be able to do. > > I canno

Re: The IPsec kernel problem

2003-10-02 Thread martin f krafft
also sprach Herbert Xu <[EMAIL PROTECTED]> [2003.10.03.0121 +0200]: > I have given you the reason for this many times already. Please > reread the thread on debian-devel carefully. This one post did in fact slip my eyes. In it, you mention some checks when it comes to patch inclusion. I have a p

Re: Kernel problem

2002-09-04 Thread Herbert Xu
On Tue, Sep 03, 2002 at 07:40:23PM +0200, Michael Meskes wrote: > > The "error" message is: > > BIOS data check successful That message comes from LILO. It sounds as if you've got a boot loader problem that is triggered by the Debian kernels. See if you can get it to load by removing the initr

Re: Kernel problem

2002-09-03 Thread Michael Meskes
On Tue, Sep 03, 2002 at 08:11:41PM +1000, Herbert Xu wrote: > Which 2.4.19 kernel package did you install and what is the exact > error message? The "error" message is: BIOS data check successful Interestingly the very same message is printed my my manually installed 2.4.18 kernel, but not by th

Re: Kernel problem

2002-09-03 Thread Michael Meskes
On Tue, Sep 03, 2002 at 08:11:41PM +1000, Herbert Xu wrote: > Which 2.4.19 kernel package did you install and what is the exact > error message? 2.4.19-k7. As for the BIOS message, I will look it up when I get to the machine the next time. It may take a day or two though. Anyway, that message did

Re: Kernel problem

2002-09-03 Thread Herbert Xu
Michael Meskes <[EMAIL PROTECTED]> wrote: > makes it boot but later I get a lost interrupt on hda. Now I installed > 2.4.19 and do get that message about bios checksum or so. But after that > it stands still again. Which 2.4.19 kernel package did you install and what is the exact error message?

Kernel problem

2002-09-03 Thread Michael Meskes
Hi, I've been using self compiled kernels throughout the years and up to 2.4.18 never experienced a problem. But Now I tried switching to the debian kernel and cannot do that at all. When using 2.4.18 the first try ends before "Uncompressing ..." is written on the screen. A reset then makes it boo

Re: Pb: gdb cannot read core from 2.0.8 (is it a gdb or kernel problem)?

1996-08-10 Thread Ian Jackson
Yves Arrouye writes ("Re: Pb: gdb cannot read core from 2.0.8 (is it a gdb or kernel problem)?"): ... > But the message is really misleading... It would ne nice if Gdb checked > wether the prog arg was a core first, and in this case tell that's the > case and remind usage.

Re: Pb: gdb cannot read core from 2.0.8 (is it a gdb or kernel problem)?

1996-08-10 Thread Yves Arrouye
Miquel van Smoorenburg writes: > You (Yves Arrouye) wrote: > > GDB 4.15.1 (i486-linux), Copyright 1995 Free Software Foundation, Inc... > > > > "0¨´ > > @/core": not in executable format: File format not recognized > > > > So there's a problem there. Do you have an idea about who is fa

Re: Pb: gdb cannot read core from 2.0.8 (is it a gdb or kernel problem)?

1996-08-10 Thread Miquel van Smoorenburg
You (Yves Arrouye) wrote: > GDB 4.15.1 (i486-linux), Copyright 1995 Free Software Foundation, Inc... > > "0¨´ > @/core": not in executable format: File format not recognized > > So there's a problem there. Do you have an idea about who is faulty? Gdb? As I understand it, the way you call gdb

Pb: gdb cannot read core from 2.0.8 (is it a gdb or kernel problem)?

1996-08-09 Thread Yves Arrouye
marin157# file core core: ELF 32-bit LSB core file, Intel 80386, version 1, stripped marin158# gdb core GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warra