On Wed, Aug 11, 2004 at 12:04:30AM -0400, Andres Salomon wrote:
On Tue, 10 Aug 2004 13:19:22 -0700, Steve Langasek wrote:
The upgrade-only kernels would be intended solely as an intermediate step
during the upgrade process; users should be encouraged to install kernels
from the main archive
On Wed, Aug 11, 2004 at 05:41:18PM +0900, Horms wrote:
On Mon, Aug 02, 2004 at 02:32:59PM +0200, Sven Luther wrote:
On Sun, Aug 01, 2004 at 11:13:23AM +0900, Horms wrote:
On Sat, Jul 31, 2004 at 06:02:19PM +0200, Jens Schmalzing wrote:
Package: kernel-source-2.4.26
Version: 2.4.26-4
On Tue, Aug 03, 2004 at 02:16:52PM +0200, Norbert Tretkowski wrote:
Hi,
I just discovered that CAN-2004-0554 is still valid, at least for
kernel-image-2.4.26-1-686 2.4.26-4 from unstable. I tested it on
two machines, and both machines crashed when running crash.c.
Thanks, I will take
On Thu, Aug 05, 2004 at 02:10:14PM -0400, Kevin B. McCarty wrote:
Have you guys seen this advisory yet? It looks rather serious:
http://isec.pl/vulnerabilities/isec-0016-procleaks.txt
Apparently this is fixed in 2.4.27-rc5 (don't know about 2.6 series):
http://lwn.net/Articles/96485/
The
On Wed, Aug 04, 2004 at 05:36:03PM +0100, Martin Michlmayr wrote:
* Andres Salomon [EMAIL PROTECTED] [2004-08-02 02:25]:
the standard kernel, please don't butcher it just because you feel
like it.
There's nothing stopping us from removing Herbert's incomplete DM
patch and applying
* [EMAIL PROTECTED] [EMAIL PROTECTED] [2004-08-11 21:41]:
This is a preemptive patch to deal with upcoming changes to the PCI
IDE driver names exported via sysfs. This may appear as early as
2.6.9.
I've seen Adrian Bunk's patches removin the spaces, but do you know
the rationale for it?
--
On Wed, Aug 11, 2004 at 01:13:19PM +0100, Martin Michlmayr wrote:
* [EMAIL PROTECTED] [EMAIL PROTECTED] [2004-08-11 21:41]:
This is a preemptive patch to deal with upcoming changes to the PCI
IDE driver names exported via sysfs. This may appear as early as
2.6.9.
I've seen Adrian Bunk's
initrd-tools_0.1.73_i386.changes uploaded successfully to localhost
along with the files:
initrd-tools_0.1.73.dsc
initrd-tools_0.1.73.tar.gz
initrd-tools_0.1.73_all.deb
Greetings,
Your Debian queue daemon
Your message dated Wed, 11 Aug 2004 08:32:07 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#255390: fixed in initrd-tools 0.1.73
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Wed, 11 Aug 2004 08:32:07 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#265011: fixed in initrd-tools 0.1.73
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Accepted:
initrd-tools_0.1.73.dsc
to pool/main/i/initrd-tools/initrd-tools_0.1.73.dsc
initrd-tools_0.1.73.tar.gz
to pool/main/i/initrd-tools/initrd-tools_0.1.73.tar.gz
initrd-tools_0.1.73_all.deb
to pool/main/i/initrd-tools/initrd-tools_0.1.73_all.deb
Announcing to
Package: kernel-image-2.6.7-1-k7-smp
Version: 2.6.7-2
Severity: critical
Justification: breaks the whole system
Hardware Environment:
Motherboard: MSI K7D Master
CPU: 2x AMD Athlon MP 1800+
Disk ctrl:Adaptec 2410 SATA Raid
SCSI ctrl:Adaptec 2490UW
HD:s :4 Seagate
Processing commands for [EMAIL PROTECTED]:
reopen 262672
Bug#262672: cpio: modprobe.conf: No such file or directory
Bug reopened, originator not changed.
reassign 262672 initrd-tools
Bug#262672: cpio: modprobe.conf: No such file or directory
Bug reassigned from package `kernel-package' to
Herbert Xu [EMAIL PROTECTED] - Wed, Jun 09, 2004:
Excellent. Thanks for your work on this.
Patch still applies on current mkinitrd, and I'd appreciate if it could
be integrated, thanks for your work.
I've attached a small fix for the patch which miss a * in a regexp.
Regards,
--
Loïc
On Wed, 2004-08-11 at 18:17 +0900, Horms wrote:
On Wed, Aug 04, 2004 at 05:36:03PM +0100, Martin Michlmayr wrote:
* Andres Salomon [EMAIL PROTECTED] [2004-08-02 02:25]:
the standard kernel, please don't butcher it just because you feel
like it.
There's nothing stopping us from
Package: kernel-image-2.4.26-1-686
Version: 2.4.26-4
Severity: important
Sorry this isn't more specific, but the Sarge install was done more to see
if the tc1 netinst worked on this sometimes quirky laptop. After a little
magic with boot options, it did. Recently I came back to it, intending
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi list,
yesterday i encounterd several oopses with my server. the subject of
this mail is just plain saying that it is all 2.6.8-rc4's fault. the
reality however turned out to be much more complex and confusing so i
try to recapitulate in a
On Wed, Aug 11, 2004 at 10:33:36AM -0400, Andres Salomon wrote:
On Wed, 2004-08-11 at 18:17 +0900, Horms wrote:
On Wed, Aug 04, 2004 at 05:36:03PM +0100, Martin Michlmayr wrote:
* Andres Salomon [EMAIL PROTECTED] [2004-08-02 02:25]:
the standard kernel, please don't butcher it just
On Wed, Aug 11, 2004 at 03:05:25PM +0200, Norbert Tretkowski wrote:
* Horms wrote:
On Tue, Aug 03, 2004 at 02:16:52PM +0200, Norbert Tretkowski wrote:
I just discovered that CAN-2004-0554 is still valid, at least for
kernel-image-2.4.26-1-686 2.4.26-4 from unstable. I tested it on
two
Your message dated Wed, 11 Aug 2004 19:47:27 -0700
with message-id [EMAIL PROTECTED]
and subject line closing these bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility
Your message dated Wed, 11 Aug 2004 19:47:27 -0700
with message-id [EMAIL PROTECTED]
and subject line closing these bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility
21 matches
Mail list logo
