Re: m68k vs. d-i tc1 -- bummer, help needed

2004-06-02 Thread Stephen R Marenka
On Wed, Jun 02, 2004 at 11:04:05AM -0300, Joey Hess wrote: > Stephen R Marenka wrote: > > Well on my autobuilders buildd has sudo rights. I don't know if this is > > still policy everywhere or just a holdover. I can switch to a dd, mke2fs > > scheme, at least for the initrd's destined for 2.2 kerne

Re: m68k vs. d-i tc1 -- bummer, help needed

2004-06-02 Thread Joey Hess
Stephen R Marenka wrote: > Well on my autobuilders buildd has sudo rights. I don't know if this is > still policy everywhere or just a holdover. I can switch to a dd, mke2fs > scheme, at least for the initrd's destined for 2.2 kernels. I think we're > getting out-of-scope for a binNMU though. > >

Re: m68k vs. d-i tc1 -- bummer, help needed

2004-06-02 Thread Stephen R Marenka
On Wed, Jun 02, 2004 at 10:11:38AM -0300, Joey Hess wrote: > Stephen R Marenka wrote: > > If this was a normal package, I'd binNMU it to get the fixed images > > available for testing. Since I can't do that, I've put them at > > . > > > > mv cdrom2

Re: m68k vs. d-i tc1 -- bummer, help needed

2004-06-02 Thread Joey Hess
Stephen R Marenka wrote: > If this was a normal package, I'd binNMU it to get the fixed images > available for testing. Since I can't do that, I've put them at > . > > mv cdrom22-initrd-tc1-take2.gz cdrom22-initrd.gz > mv nativehd-initrd-tc1-take2.

Re: m68k vs. d-i tc1 -- bummer, help needed

2004-06-02 Thread Stephen R Marenka
If this was a normal package, I'd binNMU it to get the fixed images available for testing. Since I can't do that, I've put them at . mv cdrom22-initrd-tc1-take2.gz cdrom22-initrd.gz mv nativehd-initrd-tc1-take2.gz mac/nativehd-initrd.gz Thanks, S

Re: m68k vs. d-i tc1 -- bummer, help needed

2004-06-01 Thread Stephen R Marenka
On Tue, Jun 01, 2004 at 07:21:16PM +0100, Colin Watson wrote: > Do you have enough space and kernel support to use cramfs as a > workaround? 2.2 doesn't seem to have cramfs. It also doesn't have tmpfs, so we need to be able to write to the initrd (unless someone has a better idea). -- Stephen R

Re: m68k vs. d-i tc1 -- bummer, help needed

2004-06-01 Thread Colin Watson
On Tue, Jun 01, 2004 at 10:21:48AM -0500, Stephen R Marenka wrote: > I think this may be genext2fs bug #232023. > > Preliminary testing seems to support this. If I create a filesystem using > dd and ext2fs and copy a broken initrd to it via loopback: the new image > seems to be fine. > > Which