Processed: reassign 309405 to kernel

2005-05-17 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.14 > # bug in the kernel smbfs driver > reassign 309405 kernel Bug#309405: mount.cifs: poor performance and high CPU load with large files (500MB+) compared to mount.smbfs Bug reassigned

it`s julie here

2005-05-17 Thread Julie Burton
My name is Julie :) Most of the time I like to do something I've never done before.. so I decided to have my first website featuring me (pics and videos). My girlfriends want to join me to on my website. -) Verify your age and connect to my webcam today -) Come I want to share my life experie

Bug#309551: 2.6.x kernel won't boot on an Itanium machine

2005-05-17 Thread Peter Hessler
On Wed, 18 May 2005 01:52:26 +0200 maximilian attems <[EMAIL PROTECTED]> wrote: : On Tue, 17 May 2005, Peter Hessler wrote: : : > Package: kernel-image-2.6.11-1-mckinley : > Version: 2.6.11-1 : : i'm not aware of aboves kernel package? but.. http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=kern

Bug#309551: 2.6.x kernel won't boot on an Itanium machine

2005-05-17 Thread maximilian attems
On Tue, 17 May 2005, Peter Hessler wrote: > Package: kernel-image-2.6.11-1-mckinley > Version: 2.6.11-1 i'm not aware of aboves kernel package? but.. > I have a Dell PowerEdge 3250, that won't boot any of the 2.6 kernels I > throw at it (not even from the install CD). In the best instance > (

Bug#309551: 2.6.x kernel won't boot on an Itanium machine

2005-05-17 Thread Peter Hessler
Package: kernel-image-2.6.11-1-mckinley Version: 2.6.11-1 I have a Dell PowerEdge 3250, that won't boot any of the 2.6 kernels I throw at it (not even from the install CD). In the best instance (pasted below), it will attempt to mount root on VFS, then pause and reboot. So far, any 2.4 kernel tha

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

2005-05-17 Thread maximilian attems
On Tue, 17 May 2005, Wesley W. Terpstra wrote: > On Tue, May 17, 2005 at 07:35:22PM +0200, maximilian attems wrote: > > i don't know how it would reach sarge. > > as it seems we are doing one last initrd-tools round. > > Errr. > cryptsetup is not even supposed to be in sarge. > I asked it for it

Re: Bug#291375: marked as done (initrd-tools for Debian are one big mess)

2005-05-17 Thread Erik van Konijnenburg
On Tue, May 17, 2005 at 10:47:17PM +0200, maximilian attems wrote: > afaik the strong point is that initramfs uses klibc and non glibc, > it should be smaller compared to current initrd image, plus it > doesn't need shell script magic as it's an cpio archive. Yep, my own experiments show a factor

Re: Bug#291375: marked as done (initrd-tools for Debian are one big mess)

2005-05-17 Thread maximilian attems
On Tue, 17 May 2005, Erik van Konijnenburg wrote: > > Hi, > > In the closing message for this bug, you note: > > On Tue, May 17, 2005 at 08:33:16AM -0700, Debian Bug Tracking System wrote: > > anyway postsarge it will be replaced by an initramfs implementation, > > so you won't have to rant on

Re: Bug#291375: marked as done (initrd-tools for Debian are one big mess)

2005-05-17 Thread Erik van Konijnenburg
Hi, In the closing message for this bug, you note: On Tue, May 17, 2005 at 08:33:16AM -0700, Debian Bug Tracking System wrote: > anyway postsarge it will be replaced by an initramfs implementation, > so you won't have to rant on initrd-tools anymore. I didn't see that mentioned before on debian

Bug#296464: initrd-tools: Patch to correct mkinitrd and cryptsetup using key

2005-05-17 Thread Leonardo Serra
Package: initrd-tools Version: 0.1.79 Followup-For: Bug #296464 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm using cryptsetup to crypt my swap with random key. I had the same problem, then I make a patch to /usr/sbin/mkinitrd. The realy problem is when cryptsetup asks the password for a

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

2005-05-17 Thread Wesley W. Terpstra
On Tue, May 17, 2005 at 07:35:22PM +0200, maximilian attems wrote: > i don't know how it would reach sarge. > as it seems we are doing one last initrd-tools round. Errr. cryptsetup is not even supposed to be in sarge. I asked it for it to be pulled (and it was)... yet it seems it's back. -- Wesl

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

2005-05-17 Thread maximilian attems
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" = "xtrue" and reworked it a bit. > > Yeah, I also don't like this, I just followe

Bug#251156: initrd-tools: getting /dev2/root2 in /proc/mounts

2005-05-17 Thread maximilian attems
On Sun, 01 May 2005, Stepan Koltsov wrote: > Thanks for you reply. np, thanks for your quick reply. :) > Error still persist with current initrd-tools. I. e. there is record > about /dev2/root2 in /proc/mounts, but there is no /dev2. > > Here it is requested info: > > # cat /proc/mounts > roo

Bug#266609: marked as done (initrd lacks support for root device on SATA)

2005-05-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 May 2005 17:32:25 +0200 with message-id <[EMAIL PROTECTED]> and subject line (fwd) Re: initrd-tools: doesn't probe sata devices 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 cas

Bug#272143: marked as done (failed to mount root device on sil 3112 sataraid controller)

2005-05-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 May 2005 17:32:58 +0200 with message-id <[EMAIL PROTECTED]> and subject line (fwd) Re: initrd-tools: doesn't probe sata devices 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 cas

Bug#256113: marked as done (initrd-tools: doesn't probe sata devices (or at least not sata_sis) correctly)

2005-05-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 May 2005 17:30:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line initrd-tools: doesn't probe sata devices 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 no

Bug#291375: marked as done (initrd-tools for Debian are one big mess)

2005-05-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 May 2005 17:22:32 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#291375: initrd-tools for Debian are one big mess 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 c

Bug#298311: marked as done (new ldd breaks initrd-tools on amd64)

2005-05-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 May 2005 17:15:37 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#298311: new ldd breaks initrd-tools on amd64 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#294396: kernel-kbuild-2.6-3 - does not support kernel images without symbol versions

2005-05-17 Thread Steve Langasek
severity 294396 important thanks AIUI, this is in fact a bug that's shared between kernel-kbuild-2.6-3 and kernel-image-2.6.8-s390; kernel-kbuild-2.6-3 is not in itself unusable, it's just not usable with the official Debian kernel packages on s390 due to a choice in how those packages are built.

Processed: Re: kernel-kbuild-2.6-3 - does not support kernel images without symbol versions

2005-05-17 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 294396 important Bug#294396: kernel-kbuild-2.6-3 - does not support kernel images without symbol versions Severity set to `important'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system a

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

2005-05-17 Thread Tino Keitel
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" = "xtrue" and reworked it a bit. Yeah, I also don't like this, I just followed the coding style in the cryptsetup initscript. > > On

Processed: tagging 309429

2005-05-17 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.8.14 > tags 309429 sarge-ignore Bug#309429: kernel-source-2.6.8: Local privilege escalation in pktcdvd und raw ioctl handling There were no tags set. Tags added: sarge-ignore > End of mess

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

2005-05-17 Thread Moritz Muehlenhoff
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 is passed unchecked. Both issues have been fixed in 2.6.11.10. 2.4 does not seem to be affected. At least one