[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

debian live under an alternate kernel (was binary.iso in Lenny)



On Thu, Sep 13, 2007 at 02:29:22AM +0200, Jean-Louis Lou?r wrote:
> On Tue, Sep 11, 2007 at 11:00:25AM -0500, Mr Alk3 wrote:
> > http://wiki.debian.org/DebianLive/FAQ#head-6c3c3a58f555bc62cc5cc65cdcdd2dd51361a07f
> > That should do it.
> > -Alk3
> > > > > I made a linux-image-2.6.21.deb from Unstable source with make-kpkg.
> > > > > I put this package in ./debian-live/config/chroot_local-packages/
> > > > > I put this line in ./debian-live/config/chroot :
> > > > > LH_LINUX_PACKAGES="none"
> > > > > In ./debian-live/config/bootstrap, I have LH_DISTRIBUTION="etch"
> [...]
> > > Let's go a litle bit further on. I made a kernel with the command :
> > > # make-kpkg kernel_image --append_to_version -majilux --initrd
> > > Then I have a live-cd that can boot nicely after the splash screen,
> > > but... after a few stuffs (recognition of hard disk, usb...), I get the
> > > message "can't access tty; job control turned off" and a minimal shell.
> > > Then I replaced the line in debian-live/config/common :
> > > LH_INITRAMFS="live-initramfs"
> > >
> > > At the boot of this cd, I get the lines :
> > > Begin: mounting root file system
> > > /init: .: 150: can't open /scripts/live
> > > kernel panic :-(
> 
> Ok, I added the packet 'live-initramfs_1.95.2-1~bpo.1_all.deb' in
> debian-live/config/chroot_local-packages/
> with the same parameters as above.
> 
> At boot, the system stops after "Begin: Mounting root file system". 
> But I get a Busybox shell instead of a Kernel panic.

http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-September/002114.html

If you get a kernel panic, I'm saying it might be a unionfs (?)
problem with 2.6.2[12] so use 2.6.18 (with sid) or even aufs which
hasn't given me this problem.  That means setting
LIVE_LINUX_PACKAGES=none and including the kernel and
{squash,union/au}fs modules.

As discussed, the LINUX_FLAVOUR has to match the filename of the
kernel otherwise you get the vmlinuz-* message.

Justin



Reply to: