Bug#382394: XFS corruption

2006-08-10 Thread Giuseppe Sacco
Bastian Blank wrote: On Thu, Aug 10, 2006 at 06:58:23PM +0200, Giuseppe Sacco wrote: Today I got a file system crash that completely screwed up my laptop. It happened during an upgrade of unstable after 10 days from the previous upgrade. Probably one of the file system went full and the file sy

initramfs-tools 0.73c MIGRATED to testing

2006-08-10 Thread Debian testing watch
FYI: The status of the initramfs-tools source package in Debian's testing distribution has changed. Previous version: 0.69b Current version: 0.73c -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information.

Bug#382394: marked as done (XFS corruption)

2006-08-10 Thread Debian Bug Tracking System
Your message dated Thu, 10 Aug 2006 20:47:08 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#382394: XFS corruption 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 respons

Re: Bug#382368: please enable sysrq keys

2006-08-10 Thread Martin Michlmayr
* Thiemo Seufer <[EMAIL PROTECTED]> [2006-08-10 18:05]: > > * martin f krafft <[EMAIL PROTECTED]> [2006-08-10 16:06]: > > > This is obviously to aid development but should not add to the > > > kernel size or affect the user: please enable the use of the sysrq > > > key during d-i. > > 2.6.17 has th

Bug#382394: XFS corruption

2006-08-10 Thread Giuseppe Sacco
Package: linux-image-2.6.17-1-powerpc Version: 2.6.17-5 Severity: important Today I got a file system crash that completely screwed up my laptop. It happened during an upgrade of unstable after 10 days from the previous upgrade. Probably one of the file system went full and the file system cra

Re: Etch timeline is unrealistic because non-free firmware is NOT being dealt with

2006-08-10 Thread Thomas Bushnell BSG
Russ Allbery <[EMAIL PROTECTED]> writes: > Please don't lose track of the fact that there's nothing inherently wrong > with a sourceless binary if that's all the source anyone *has*. I think in most of the cases under consideration, we have firmware which a hardware manufacturer wrote and then

Re: Etch timeline is unrealistic because non-free firmware is NOT being dealt with

2006-08-10 Thread Sven Luther
On Thu, Aug 10, 2006 at 06:14:08PM +0200, Goswin von Brederlow wrote: > Sven Luther <[EMAIL PROTECTED]> writes: > >> Where people buy their hardware or how free their hardware is has > >> little to do with Debian main. It is a problem for the linux upostream > >> authors to support the hardware wit

Re: Etch timeline is unrealistic because non-free firmware is NOT being dealt with

2006-08-10 Thread Goswin von Brederlow
Sven Luther <[EMAIL PROTECTED]> writes: > On Thu, Aug 10, 2006 at 04:32:52PM +0200, Goswin von Brederlow wrote: >> Sven Luther <[EMAIL PROTECTED]> writes: >> >> > I am not familiar enough with how library are run, but there is some very >> > different way in which libraries called by programs wor

Re: Etch timeline is unrealistic because non-free firmware is NOT being dealt with

2006-08-10 Thread Sven Luther
On Thu, Aug 10, 2006 at 04:50:29PM +0200, Goswin von Brederlow wrote: > Sven Luther <[EMAIL PROTECTED]> writes: > > > On Thu, Aug 10, 2006 at 03:51:31PM +0200, Goswin von Brederlow wrote: > >> Sven Luther <[EMAIL PROTECTED]> writes: > >> Which would be a task for the debian-cd team. Has anyone tal

Re: Etch timeline is unrealistic because non-free firmware is NOT being dealt with

2006-08-10 Thread Russ Allbery
Nathanael Nerode <[EMAIL PROTECTED]> writes: > The point of my initial message was not to argue: it was that the etch > timeline is unrealistic, because I see no progress on removing the > substantial number of sourceless binaries from the Linux kernel source > package, and it's *after* the kernel

Re: Etch timeline is unrealistic because non-free firmware is NOT being dealt with

2006-08-10 Thread Sven Luther
On Thu, Aug 10, 2006 at 04:32:52PM +0200, Goswin von Brederlow wrote: > Sven Luther <[EMAIL PROTECTED]> writes: > > > On Mon, Aug 07, 2006 at 02:48:08PM +0200, Goswin von Brederlow wrote: > >> Sven Luther <[EMAIL PROTECTED]> writes: > >> And even for an aggregation of works the DFSG holds and you

Processed: Re: Bug#382280: does not configure encrypted swap during initramfs, thus prevents resume

2006-08-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 382280 cryptsetup Bug#382280: does not configure encrypted swap during initramfs, thus prevents resume Bug reassigned from package `cryptsetup initramfs-tools' to `cryptsetup'. > thanks Stopping processing here. Please contact me if you need

Re: Etch timeline is unrealistic because non-free firmware is NOT being dealt with

2006-08-10 Thread Goswin von Brederlow
Sven Luther <[EMAIL PROTECTED]> writes: > On Thu, Aug 10, 2006 at 03:51:31PM +0200, Goswin von Brederlow wrote: >> Sven Luther <[EMAIL PROTECTED]> writes: >> Which would be a task for the debian-cd team. Has anyone talk to them >> about it? > > Currently there is no infrastructure to build non-fre

Bug#382280: does not configure encrypted swap during initramfs, thus prevents resume

2006-08-10 Thread martin f krafft
reassign 382280 cryptsetup thanks also sprach maximilian attems <[EMAIL PROTECTED]> [2006.08.10.1358 +0100]: > > cryptsetup only sets up root in the initramfs. If swap is encrypted, > > it should probably also set that up, or else resume from disk will > > not work. > > cryptswap is not the gener

Re: Etch timeline is unrealistic because non-free firmware is NOT being dealt with

2006-08-10 Thread Goswin von Brederlow
Sven Luther <[EMAIL PROTECTED]> writes: > On Mon, Aug 07, 2006 at 02:48:08PM +0200, Goswin von Brederlow wrote: >> Sven Luther <[EMAIL PROTECTED]> writes: >> And even for an aggregation of works the DFSG holds and you are still >> in trouble. > > Sure, the DFSG says that we need the source code fo

Re: Etch timeline is unrealistic because non-free firmware is NOT being dealt with

2006-08-10 Thread Sven Luther
On Thu, Aug 10, 2006 at 03:51:31PM +0200, Goswin von Brederlow wrote: > Sven Luther <[EMAIL PROTECTED]> writes: > > > > 1) it is lot of work, and we (the kernel team) don't realy have the > > ressources > > for it. > > Then stop doing 0 day uploads and fix the kernel. No matter how long > it

Re: Etch timeline is unrealistic because non-free firmware is NOT being dealt with

2006-08-10 Thread Goswin von Brederlow
Sven Luther <[EMAIL PROTECTED]> writes: > On Tue, Aug 08, 2006 at 08:12:48PM -0400, Jim Crilly wrote: >> On 08/08/06 04:49:33PM -0700, Thomas Bushnell BSG wrote: >> > Sven Luther <[EMAIL PROTECTED]> writes: >> > >> > > Well, it reads to me that we won't screw our users without second >> > > thoug

Bug#382280: does not configure encrypted swap during initramfs, thus prevents resume

2006-08-10 Thread maximilian attems
On Wed, 09 Aug 2006, martin f krafft wrote: > cryptsetup only sets up root in the initramfs. If swap is encrypted, > it should probably also set that up, or else resume from disk will > not work. cryptswap is not the generic initramfs-tools business. > On my system, initramfs tells me that the

Bug#382339: Dell Latitude D420 does not resume from suspend-to-RAM

2006-08-10 Thread Steinar H. Gunderson
Package: linux-image-2.6.17-1-686 Version: 2.6.17-5 Severity: normal Tags: patch Dell Latitude D420 does not resume properly from suspend-to-RAM -- this works with 2.6.16 and current git head (around 2.6.18-rc4 somewhere), but not with 2.6.17. The included patch was applied around 2.6.18-rc1, and

Re: Etch timeline is unrealistic because non-free firmware is NOT being dealt with

2006-08-10 Thread Thiemo Seufer
Nathanael Nerode wrote: [snip] > http://wiki.debian.org/KernelFirmwareLicensing is grossly out-of-date, but I > will integrate the relevant information from that in the process. KernelFirmwareLicensing is supposed to track information about mis-licensed firmware. IIRC you mentioned to have found a

Modules & 2.6.16

2006-08-10 Thread Erik Svensson
I need to prevent a module from loading at boot (ehci-hcd) in order toget my scanner to work. I have put it in /etc/hotplug/blacklist.d and it has worked fine until i updated to kernel 2.6.16 (debian testing standard kernel), after that the module is loaded evey time I boot. How can I stop it from

Re: Etch timeline is unrealistic because non-free firmware is NOT being dealt with

2006-08-10 Thread Sven Luther
On Sat, Aug 05, 2006 at 11:29:44PM -0400, Nathanael Nerode wrote: > I apologize for responding to Marco's post; in retrospect he was clearly > trolling and I should not have responded to him. > > The point of my initial message was not to argue: it was that the etch > timeline is unrealistic, beca

Bug#382303: please add timezone option to vfat mounts

2006-08-10 Thread Blars Blarson
Package: mount,kernel Severity: wishlist When mouting the sd card from my gps, the file timestamps are 8 hours off. It appears that the gps records the time stamps in GMT, and linux vfat uses the local time zone for timestamps. Please add support for using alternate timezones on vfat filesystems