Alvin Oga [EMAIL PROTECTED] writes:
http://linux.bkbits.net:8080/linux-2.4/diffs/mm/[EMAIL PROTECTED]
i see other code fragments that has a similar PAGE_ALIGN() problem
- sounds like the macro needs to be cleaned up ?
Sorry, this comment was a little too cryptic for me. Could you expand
Alvin Oga [EMAIL PROTECTED] writes:
http://linux.bkbits.net:8080/linux-2.4/diffs/mm/[EMAIL PROTECTED]
i see other code fragments that has a similar PAGE_ALIGN() problem
- sounds like the macro needs to be cleaned up ?
Sorry, this comment was a little too cryptic for me. Could you expand
On Thursday, 2003-12-04 at 01:46:43 +0100, Bernd Eckenfels wrote:
In article [EMAIL PROTECTED] you wrote:
Nah, just look at /proc/cpuinfo, /proc/pci (or use lspci), dmesg, etc
It's almost all there for you. Not like the old days...
lshw is fine for collecting the above information. If you
On Thursday, 2003-12-04 at 07:47:53 +0100, Matthias Faulstich wrote:
Having the kernel-souces, knowledge about make-kpkg and a propper
working .config for a previously kernel is one thing, but having a debian
patched kernel (or kernel-sources) is a second.
E.g. cramfs for initrd still
On Fri, Dec 05, 2003 at 08:08:46AM +0100, Lupe Christoph wrote:
BUT! Does anybody have a patch for the do_brk vuln on any kernel-source
package = 2.4.20 as they are currently in the archives? I would like to
build a new kernel with the vuln patched ASAP, rather than wait for the
upload to
Quoting Thomas Sjögren [EMAIL PROTECTED]:
On Fri, Dec 05, 2003 at 08:08:46AM +0100, Lupe Christoph wrote:
BUT! Does anybody have a patch for the do_brk vuln on any kernel-source
package = 2.4.20 as they are currently in the archives? I would like to
build a new kernel with the vuln patched
On Fri, 5 Dec 2003, Thomas [iso-8859-1] Sjögren wrote:
On Fri, Dec 05, 2003 at 08:08:46AM +0100, Lupe Christoph wrote:
BUT! Does anybody have a patch for the do_brk vuln on any kernel-source
package = 2.4.20 as they are currently in the archives? I would like to
build a new kernel with
On Thursday, 2003-12-04 at 07:47:53 +0100, Matthias Faulstich wrote:
Having the kernel-souces, knowledge about make-kpkg and a propper
working .config for a previously kernel is one thing, but having a debian
patched kernel (or kernel-sources) is a second.
E.g. cramfs for initrd still
On Thursday, 2003-12-04 at 01:46:43 +0100, Bernd Eckenfels wrote:
In article [EMAIL PROTECTED] you wrote:
Nah, just look at /proc/cpuinfo, /proc/pci (or use lspci), dmesg, etc
It's almost all there for you. Not like the old days...
lshw is fine for collecting the above information. If you
On Fri, Dec 05, 2003 at 08:08:46AM +0100, Lupe Christoph wrote:
BUT! Does anybody have a patch for the do_brk vuln on any kernel-source
package = 2.4.20 as they are currently in the archives? I would like to
build a new kernel with the vuln patched ASAP, rather than wait for the
upload to
Am Mittwoch, 3. Dezember 2003 21:26 schrieb Kjetil Kjernsmo :
On Wednesday 03 December 2003 20:57, Phillip Hofmeister wrote:
You may wish to look at the make-kpkg(kernel-package) package. It
takes your stock 2.4.23 source and makes it into a nice .deb file for
you.
Note: This option is
On Thu, Dec 04, 2003 at 07:47:53AM +0100, Matthias Faulstich wrote:
Having the kernel-souces, knowledge about make-kpkg and a propper
working .config for a previously kernel is one thing, but having a debian
patched kernel (or kernel-sources) is a second.
E.g. cramfs for initrd still
Am Mittwoch, 3. Dezember 2003 21:26 schrieb Kjetil Kjernsmo :
On Wednesday 03 December 2003 20:57, Phillip Hofmeister wrote:
You may wish to look at the make-kpkg(kernel-package) package. It
takes your stock 2.4.23 source and makes it into a nice .deb file for
you.
Note: This option is
On Thu, Dec 04, 2003 at 07:47:53AM +0100, Matthias Faulstich wrote:
Having the kernel-souces, knowledge about make-kpkg and a propper
working .config for a previously kernel is one thing, but having a debian
patched kernel (or kernel-sources) is a second.
E.g. cramfs for initrd still
Also,
You may wish to look at the make-kpkg(kernel-package) package. It
takes your stock 2.4.23 source and makes it into a nice .deb file for
you.
Note: This option is for those who have a working .config file.
Experience in making your own config make (config|menuconfig|xconfig) is
On Wednesday 03 December 2003 20:57, Phillip Hofmeister wrote:
You may wish to look at the make-kpkg(kernel-package) package. It
takes your stock 2.4.23 source and makes it into a nice .deb file for
you.
Note: This option is for those who have a working .config file.
Experience in making
At 21:26 03.12.2003 +0100, you wrote:
Experience in making your own config make (config|menuconfig|xconfig) is
recommended.
No experience without the first try. Take about two days for reading the
documentation and finding the brands on the chips your machine works with.
P.S.: Before rebooting
On Wed, Dec 03, 2003 at 10:43:44PM +0100, Marc F. Neininger wrote:
No experience without the first try. Take about two days for reading the
documentation and finding the brands on the chips your machine works with.
Nah, just look at /proc/cpuinfo, /proc/pci (or use lspci), dmesg, etc
It's
On Tue, 2 Dec 2003, Jan H. van Gils wrote:
After some research a found that kernel-image-2.4.18 is patched
regarding the security problem with the kernel.
I am wonder when kernel 2.4.23 wil be available as a packages for sarge ?
Nobody knows for sure, but the things which should happen, in
Also,
You may wish to look at the make-kpkg(kernel-package) package. It
takes your stock 2.4.23 source and makes it into a nice .deb file for
you.
Note: This option is for those who have a working .config file.
Experience in making your own config make (config|menuconfig|xconfig) is
At 21:26 03.12.2003 +0100, you wrote:
Experience in making your own config make (config|menuconfig|xconfig) is
recommended.
No experience without the first try. Take about two days for reading the
documentation and finding the brands on the chips your machine works with.
P.S.: Before
On Wed, Dec 03, 2003 at 10:43:44PM +0100, Marc F. Neininger wrote:
No experience without the first try. Take about two days for reading the
documentation and finding the brands on the chips your machine works with.
Nah, just look at /proc/cpuinfo, /proc/pci (or use lspci), dmesg, etc
It's
In article [EMAIL PROTECTED] you wrote:
Nah, just look at /proc/cpuinfo, /proc/pci (or use lspci), dmesg, etc
It's almost all there for you. Not like the old days...
lshw is fine for collecting the above information. If you need more
detection try discover (Progeny) or Kudzu (Redhat) both
Hi,
After some research a found that kernel-image-2.4.18 is patched
regarding the security problem with the kernel.
I am wonder when kernel 2.4.23 wil be available as a packages for sarge ?
Jan
--
With regards Jan H. van Gils
Internet web-page http://www.VGNet.NL/
Internet e-mail
24 matches
Mail list logo
