Sarge 2.6.8 kernel suitable for NFS?

From the discussion regarding whether to stick with 2.6.8 in sarge , one gets the impression that there are NFS problems in the sarge 2.6.8 kernel. Are these severe enough to not recommend this kernel for NFS server and/or client use

kernel-patch-powerpc-2.6.8_2.6.8-16_powerpc.changes ACCEPTED

Accepted: kernel-build-2.6.8-power3-smp_2.6.8-16_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-power3-smp_2.6.8-16_powerpc.deb kernel-build-2.6.8-power3_2.6.8-16_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-power3_2.6.8-16_powerpc.deb ke

Bug#308639: marked as done (kernel-build vs. kernel-headers splitted broken, headers unuseable)

Your message dated Thu, 19 May 2005 23:32:38 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#308639: fixed in kernel-patch-powerpc-2.6.8 2.6.8-16 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 t

Processing of kernel-patch-powerpc-2.6.8_2.6.8-16_powerpc.changes

kernel-patch-powerpc-2.6.8_2.6.8-16_powerpc.changes uploaded successfully to localhost along with the files: kernel-patch-powerpc-2.6.8_2.6.8-16.dsc kernel-patch-powerpc-2.6.8_2.6.8-16.tar.gz kernel-headers-2.6.8_2.6.8-16_powerpc.deb kernel-image-2.6.8-power3_2.6.8-16_powerpc.deb kernel-

Bug#309841: kernel-headers-2.6.11-1-k7 symlinks

On Thu, 19 May 2005, Signey John wrote: Package: kernel-headers-2.6.11-1-k7 Version: 2.6.11-3 no files, all symlinks... This is not a bug. This package contains only flavour (k7) specific header files, creating a bunch of symlinks to the flavour-independent header files which come from the kernel-

Bug#80878: eSecure Online Pharmacies

Top 10 popular pharmacy drugs http://usyt.6lrhs7ozlyoeap6.luxfcadh.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#309841: kernel-headers-2.6.11-1-k7 symlinks

Package: kernel-headers-2.6.11-1-k7 Version: 2.6.11-3 no files, all symlinks... Signey John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Status of kernel-patches in sarge

I'm performing an ongoing activity to check the applicability of current kernel-patches against sarge kernel-sources for 2.4.27 and 2.6.8. An almost complete summary is available at http://people.debian.org/~frankie/kernel-patches-checks.txt As you can see, there are a few patches which cannot

Processed: Re: Bug#304483: mkinitrd does not create "mdadm -A" record for /boot partition on raid1 when initrd.img is built

Processing commands for [EMAIL PROTECTED]: > reassign 304483 madadm Bug#304483: mkinitrd does not create "mdadm -A" record for /boot partition on raid1 when initrd.img is built Warning: Unknown package 'madadm' Bug reassigned from package `initrd-tools' to `madadm'. > stop Stopping processing he

RFC: New uniform packaging scheme

Hello, As you might know, we are planning a transition to the common kernel source, which is expected to build all the kernel-related packages, eliminating the problems with arches getting out of sync, etc. A significant progress have been made in creating this source package, the pilot version w

Bug#295657: EXT3 on RAID problems in all 2.6-smp

> can you try to reproduce it with more recent 2.6.11 from unstable? i'm running 2.6.11-1-686-smp since yesterday and so far so good. i'll try to do some heavy loads later on this/next week and let you know the results. cheers, jeroen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subj

Bug#304483: mkinitrd does not create "mdadm -A" record for /boot partition on raid1 when initrd.img is built

reassign 304483 madadm stop On Thu, 19 May 2005, rds wrote: > I can't try this right now but I doubt this would help. The reason is that > when > the system boots initrd would not know how to assemble /dev/md1 because > .../initrimg/script does not contain "mdadm -A" record for /dev/md1. This i

Bug#309611: marked as done (initrd-tools: raidtools2 has been removed)

Your message dated Thu, 19 May 2005 17:16:04 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#309611: initrd-tools: raidtools2 has been removed 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

Bug#295657: EXT3 on RAID problems in all 2.6-smp

severity 295657 important stop On Thu, 19 May 2005, Erik Forsberg wrote: > On Wed, 2005-05-18 at 22:44 +0200, maximilian attems wrote: > > can you try to reproduce it with more recent 2.6.11 from unstable? > > In my case, the machine in question is unfortunately running as a > medium-sized mails

kernel-patch-powerpc-2.6.8_2.6.8-16_powerpc.changes REJECTED

Rejected: Unknown distribution `UNRELEASED'. === If you don't understand why your files were rejected, or if the override file requires editing, reply to this email. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Bug#295657: EXT3 on RAID problems in all 2.6-smp

Processing commands for [EMAIL PROTECTED]: > severity 295657 important Bug#295657: EXT3 on RAID problems in all 2.6-smp Severity set to `important'. > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs da

Re: Kernel Modules for PE2850 in default i386 2.6 kernel builds.

On Thursday 19 May 2005 16:37, Satadru Pramanik wrote: > I am setting up a Dell PowerEdge 2850 with Debian/Sarge and noticed > that I can install with a sarge installation cd > using kernel 2.4.x, but I can not install with the debian 2.6.x > kernels, nor update to a debian 2.6.x kernel that wi

Processing of kernel-patch-powerpc-2.6.8_2.6.8-16_powerpc.changes

kernel-patch-powerpc-2.6.8_2.6.8-16_powerpc.changes uploaded successfully to localhost along with the files: kernel-patch-powerpc-2.6.8_2.6.8-16.dsc kernel-patch-powerpc-2.6.8_2.6.8-16.tar.gz kernel-headers-2.6.8_2.6.8-16_powerpc.deb kernel-image-2.6.8-power3_2.6.8-16_powerpc.deb kernel-

Bug#290708: initrd-tools: dm-crypt devices initialized with wrong arguments for cryptsetup

On Tue, May 17, 2005 at 19:35:22 +0200, maximilian attems wrote: > On Tue, 17 May 2005, Tino Keitel wrote: > > > On Sat, May 14, 2005 at 18:23:27 +0200, maximilian attems wrote: > > > hello tino, > > > > > > thanks for your patch, > > > i had a look at it, but got mad with all the > > > "x$foo" =

Kernel Modules for PE2850 in default i386 2.6 kernel builds.

I am setting up a Dell PowerEdge 2850 with Debian/Sarge and noticed that I can install with a sarge installation cd using kernel 2.4.x, but I can not install with the debian 2.6.x kernels, nor update to a debian 2.6.x kernel that will support the built in scsi hardware. The problem lies in the

Bug#303501: CAN-2005-0750: Bluetooth root exploit due to boundary checking

Hi, It seems that this is fixed in the current kernel (just uploaded) The patch submitted by this bug seems to be applied already. Probably forgotten to add to the changelog entry ? Regards, Matthijs Mohlmann signature.asc Description: OpenPGP digital signature

Bug#304483: mkinitrd does not create "mdadm -A" record for /boot partition on raid1 when initrd.img is built

> Quick question: why not add an auto=md clause to /etc/mdadm/mdadm.conf? > That way you have the option of *not* assembling some md drives if necessary. I can't try this right now but I doubt this would help. The reason is that when the system boots initrd would not know how to assemble /dev/md1

kernel-source-2.6.8_2.6.8-16_i386.changes ACCEPTED

Accepted: kernel-doc-2.6.8_2.6.8-16_all.deb to pool/main/k/kernel-source-2.6.8/kernel-doc-2.6.8_2.6.8-16_all.deb kernel-patch-debian-2.6.8_2.6.8-16_all.deb to pool/main/k/kernel-source-2.6.8/kernel-patch-debian-2.6.8_2.6.8-16_all.deb kernel-source-2.6.8_2.6.8-16.diff.gz to pool/main/k/kernel

Re: Updated kernel-source 2.4.27 and 2.6.8 packages in unstable

Hi, I have taged, built and uploaded to unstable, kernel-source 2.6.8-16 and 2.4.27-10. Similarly for i386 kernel-images. I will upload powerpc once it finishes building. Can the relevant parties please kick of per-arch builds as they see fit? I have the sarge-security updates almost ready, but

Re: Updated kernel-source 2.4.27 and 2.6.8 packages in unstable

On Thu, May 19, 2005 at 08:12:20PM +0900, Horms wrote: > Hi, > > I have taged, built and uploaded to unstable, kernel-source 2.6.8-16 and > 2.4.27-10. Similarly for i386 kernel-images. I will upload powerpc > once it finishes building. Can the relevant parties please kick of > per-arch builds as

Re: Kernel Security Updates for Sarge

Hi, after some discusson, most of which can be found at http://lists.debian.org/debian-kernel/2005/05/msg00164.html I have prepared proposed security updates for Sarge, which Steve Langasek tells me he would really like to be available the day sarge is released. I have source, i386 and powerpc

Processing of kernel-image-2.6.8-i386_2.6.8-16_i386.changes

PGP/GnuPG signature check failed on kernel-image-2.6.8-i386_2.6.8-16_i386.changes gpg: Signature made Thu May 19 06:00:23 2005 EDT using DSA key ID 87B1CFB5 gpg: BAD signature from "Horms <[EMAIL PROTECTED]>" (Exit status 1) kernel-image-2.6.8-i386_2.6.8-16_i386.changes has bad PGP/GnuPG signature

Processing of kernel-source-2.6.8_2.6.8-16_i386.changes

kernel-source-2.6.8_2.6.8-16_i386.changes uploaded successfully to localhost along with the files: kernel-source-2.6.8_2.6.8-16.dsc kernel-source-2.6.8_2.6.8-16.diff.gz kernel-patch-debian-2.6.8_2.6.8-16_all.deb kernel-source-2.6.8_2.6.8-16_all.deb kernel-tree-2.6.8_2.6.8-16_all.deb ker

Bug#304548: marked as done (CAN-2005-1041: DoS vulnerability in fib_seq_start())

Your message dated Thu, 19 May 2005 07:17:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#304548: fixed in kernel-source-2.6.8 2.6.8-16 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

kernel-patch-powerpc-2.4.27_2.4.27-10_powerpc.changes ACCEPTED

Accepted: kernel-build-2.4.27-apus_2.4.27-10_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-apus_2.4.27-10_powerpc.deb kernel-build-2.4.27-nubus_2.4.27-10_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-nubus_2.4.27-10_powerpc.deb kernel

Bug#295725: marked as done (kernel-image-2.6.8-2-sparc64: sunmouse on Ultra 5 is not recognized under X)

Your message dated Thu, 19 May 2005 07:17:45 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#295725: fixed in kernel-source-2.6.8 2.6.8-16 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

kernel-image-2.4.27-i386_2.4.27-10_i386.changes ACCEPTED

Accepted: kernel-build-2.4.27-2_2.4.27-10_i386.deb to pool/main/k/kernel-image-2.4.27-i386/kernel-build-2.4.27-2_2.4.27-10_i386.deb kernel-headers-2.4.27-2-386_2.4.27-10_i386.deb to pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-386_2.4.27-10_i386.deb kernel-headers-2.4.27-2-58

Bug#272683: marked as done (libgnomevfs2-0: [sparc] file monitoring doesn't work)

Your message dated Thu, 19 May 2005 07:17:45 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#272683: fixed in kernel-source-2.6.8 2.6.8-16 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

Bug#300163: marked as done ([CAN-2004-1191]: Race condition could allow local users to read unauthorized memory from "foreign memory pages.")

Your message dated Thu, 19 May 2005 07:17:45 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#300163: fixed in kernel-source-2.6.8 2.6.8-16 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

Bug#303140: marked as done (CAN-2005-0937: DoS in futex handling)

Your message dated Thu, 19 May 2005 07:17:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#303140: fixed in kernel-source-2.6.8 2.6.8-16 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

Bug#301488: marked as done (kernel-source-2.6.8: fails to compile; undefined reference to `drm_free')

Your message dated Thu, 19 May 2005 07:17:45 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#301488: fixed in kernel-source-2.6.8 2.6.8-16 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

Bug#301528: marked as done (kernel-image-2.6.8-2-686: can't load radeon module (no 3d support))

Your message dated Thu, 19 May 2005 07:17:45 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#301488: fixed in kernel-source-2.6.8 2.6.8-16 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

Bug#307552: marked as done (CAN-2005-1369: DoS through user-writable sysfs nodes in it87 and via686a drivers)

Your message dated Thu, 19 May 2005 07:17:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#307552: fixed in kernel-source-2.6.8 2.6.8-16 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

Bug#308034: marked as done (Radeon module unable to load since last Sarge update)

Your message dated Thu, 19 May 2005 07:17:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#308034: fixed in kernel-source-2.6.8 2.6.8-16 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

Bug#308634: marked as done (kernel-source-2.6.8: A locally exploitable flaw to gain root.)

Your message dated Thu, 19 May 2005 07:17:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#308634: fixed in kernel-source-2.6.8 2.6.8-16 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

Bug#308724: marked as done (CAN-2005-1263: "ELF core dump privilege elevation")

Your message dated Thu, 19 May 2005 07:17:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#308634: fixed in kernel-source-2.6.8 2.6.8-16 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

Bug#308855: marked as done (Privilege escalation in ELF core dump (fs/binfmt_elf.c))

Your message dated Thu, 19 May 2005 07:17:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#308634: fixed in kernel-source-2.6.8 2.6.8-16 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

Bug#301799: marked as done (use 4 level digits for stable kernels)

Your message dated Thu, 19 May 2005 07:17:45 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#301799: fixed in kernel-source-2.6.8 2.6.8-16 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

Bug#303498: marked as done (CAN-2005-0749: Elf Binary Loading Local DoS)

Your message dated Thu, 19 May 2005 07:17:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#303498: fixed in kernel-source-2.6.8 2.6.8-16 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

Bug#308760: marked as done (CAN-2005-1263: Linux kernel ELF core dump privilege elevation)

Your message dated Thu, 19 May 2005 07:17:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#308634: fixed in kernel-source-2.6.8 2.6.8-16 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

Bug#309429: marked as done (kernel-source-2.6.8: Local privilege escalation in pktcdvd und raw ioctl handling)

Your message dated Thu, 19 May 2005 07:17:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#309429: fixed in kernel-source-2.6.8 2.6.8-16 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

Processing of kernel-patch-powerpc-2.4.27_2.4.27-10_powerpc.changes

kernel-patch-powerpc-2.4.27_2.4.27-10_powerpc.changes uploaded successfully to localhost along with the files: kernel-patch-powerpc-2.4.27_2.4.27-10.dsc kernel-patch-powerpc-2.4.27_2.4.27-10.tar.gz kernel-patch-2.4.27-apus_2.4.27-10_powerpc.deb kernel-headers-2.4.27-apus_2.4.27-10_powerpc.

Processing of kernel-image-2.4.27-i386_2.4.27-10_i386.changes

kernel-image-2.4.27-i386_2.4.27-10_i386.changes uploaded successfully to localhost along with the files: kernel-image-2.4.27-i386_2.4.27-10.dsc kernel-image-2.4.27-i386_2.4.27-10.tar.gz kernel-headers-2.4.27-2_2.4.27-10_i386.deb kernel-pcmcia-modules-2.4.27-2-586tsc_2.4.27-10_i386.deb ke

kernel-source-2.4.27_2.4.27-10_i386.changes ACCEPTED

Accepted: kernel-doc-2.4.27_2.4.27-10_all.deb to pool/main/k/kernel-source-2.4.27/kernel-doc-2.4.27_2.4.27-10_all.deb kernel-patch-debian-2.4.27_2.4.27-10_all.deb to pool/main/k/kernel-source-2.4.27/kernel-patch-debian-2.4.27_2.4.27-10_all.deb kernel-source-2.4.27_2.4.27-10.diff.gz to pool/

Bug#305655: marked as done (CAN-2004-0790: TCP connection DoS through ICMP_QUENCH messages)

Your message dated Thu, 19 May 2005 06:47:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#305655: fixed in kernel-source-2.4.27 2.4.27-10 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 ca

Bug#302864: marked as done (CAN-2005-0815: Multiple security problems in ISO9660 and Rockridge Code)

Your message dated Thu, 19 May 2005 06:47:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#302864: fixed in kernel-source-2.4.27 2.4.27-10 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 ca

Bug#302704: marked as done (CAN-2005-0750: Possible local root exploit through insufficient range checking in af_bluetooth)

Your message dated Thu, 19 May 2005 06:47:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#302704: fixed in kernel-source-2.4.27 2.4.27-10 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 ca

Bug#302705: marked as done (CAN-2005-0749: Potential DOS in elf_load_library())

Your message dated Thu, 19 May 2005 06:47:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#302705: fixed in kernel-source-2.4.27 2.4.27-10 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 ca

Bug#308757: marked as done (CAN-2005-1263: Linux kernel ELF core dump privilege elevation)

Your message dated Thu, 19 May 2005 06:47:46 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#308757: fixed in kernel-source-2.4.27 2.4.27-10 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 ca

Processing of kernel-source-2.4.27_2.4.27-10_i386.changes

kernel-source-2.4.27_2.4.27-10_i386.changes uploaded successfully to localhost along with the files: kernel-source-2.4.27_2.4.27-10.dsc kernel-source-2.4.27_2.4.27-10.diff.gz kernel-patch-debian-2.4.27_2.4.27-10_all.deb kernel-doc-2.4.27_2.4.27-10_all.deb kernel-source-2.4.27_2.4.27-10_al

Re: General Protection Faults in nfsd (Sarge kernel)

On Tue, May 10, 2005 at 07:46:16PM +0900, Horms wrote: > Are you able to test this against the 2.6.11 kernels that are in unstable? Sorry for the late reply. We just had another GPF, this time the logs showed four of them in a row. I show the relevant parts of the log below. The processes affec

Bug#295657: EXT3 on RAID problems in all 2.6-smp

On Wed, 2005-05-18 at 22:44 +0200, maximilian attems wrote: > can you try to reproduce it with more recent 2.6.11 from unstable? In my case, the machine in question is unfortunately running as a medium-sized mailserver. It's a rather bad idea to use it for file system trashing tests. I will recei

Bug#309429: kernel-source-2.6.8: Local privilege escalation in pktcdvd und raw ioctl handling

tag 309429 +pending thanks On Tue, May 17, 2005 at 09:06:16AM +0200, Moritz Muehlenhoff wrote: > Package: kernel-source-2.6.8 > Severity: grave > Justification: user security hole > > > Two new local privilege escalations have been found in the 2.6 kernels; > input to the pktcdvd and raw ioctls

Bug#309611: initrd-tools: raidtools2 has been removed

yes. Can anyone kind tell me that why mdadm takes the raidtools' place? Thx. Stanley On 5/18/05, Domenico Andreoli <[EMAIL PROTECTED]> wrote: > Package: initrd-tools > Version: 0.1.79 > > if package mdadm is not installed, mkinitrd looks for /sbin/raidstart. > /sbin/raidstart was provided by p

Processed: Re: Bug#309429: kernel-source-2.6.8: Local privilege escalation in pktcdvd und raw ioctl handling

Processing commands for [EMAIL PROTECTED]: > tag 309429 +pending Bug#309429: kernel-source-2.6.8: Local privilege escalation in pktcdvd und raw ioctl handling Tags were: sarge-ignore Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tra