Re: Lenny-LiveCD boot error (/bin/sh: can't access tty ...)

2008-02-12 Thread Jordi Pujol
El Tuesday 12 February 2008 18:58:19 Sebastian Holler va escriure:
 I tried to build a Lenny image on my own with live-helper1.0~a37~20071120:

 lh_config \
 --distribution lenny --packages-list 'kde-core' --architecture i386 \
 --language de --bootloader syslinux --bootstrap debootstrap \
 --apt-secure disabled --union-filesystem aufs \
 --linux-packages 'linux-image-2.6 aufs-modules-2.6 squashfs-modules-2.6' \
 --initramfs 'live-initramfs'
 lh_clean
 lh_build

 The boot procedure of the final Live-CD breaks and opens a BusyBox.
 The live.log contains the following:

 mount: Mounting /dev/hda2 on /live/image failed: No such device
 stdin: error 0
 debug: Can not mount backdev /dev/loop0 (Image =
 /live/image/live/filesystem.squashfs) on croot/imagename
 //filesystem.squashfs
 mount: Mounting /dev/loop on //filesystem.squashfs failed: Invalid
 argument. ...

 The mount-command inside the busybox shows, that /dev/hdc is mounted on
 /live/image (and not /dev/hda2). Therefore in /live/image/live I can see
 the file filesystem.squashfs.

 Using mksquashfs with -no-lzma option (by editing
 /usr/bin/lh_binary_rootfs) didn't solve this problem. (There are no
 problems with building Etch images.)

 Can anyone help me?

 Sebastian H.

--- live-initramfs-1.110.7/scripts/live2007-11-18 15:10:11.0 +0100
+++ live-initramfs-jp/scripts/live2008-02-10 19:33:10.0 +0100

Can be because fstype does not detect the filesystem type of squashfs 3.3 
files.

I propose the following patch for live-initramfs, where the filesystem type, 
if not detected, is assumed from the file extension.

@@ -962,9 +840,23 @@
panic Unknown file system type on ${backdev} 
(${image})
fi

+   if [ -z ${fstype} ]
+   then
+   fstype=${imagename#*.}
+   log_warning_msg Unknown file system type on 
${backdev} (${image}) Assuming ${fstype}
+   fi
+
mkdir -p ${croot}/${imagename}
 
 ___
 debian-live-devel mailing list
 debian-live-devel@lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel



___
debian-live-devel mailing list
debian-live-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel


Re: lh_build on lenny and squashfs-tools

2008-02-12 Thread maybeway36
On Feb 12, 2008 11:38 AM, Philippe Lhardy [EMAIL PROTECTED] wrote:
 Hi,

 live builds on lenny are broken due to latest squashfs-tools v 3.3.
 they generate 3.1 squash version, where squashfs kernel module can't
 support.
 using squashfs-tool 1:2.2r2-9 proove to make it work, but it is not easy to
 set it up for lh_build usage
  since it is upgraded to 1:3.3-3 automatically.

 1) i put squashfs-tools_3.2r2-9_i386.deb in local packages
 config/chroot_local-packages/squashfs-tools_3.2r2-9_i386.deb

 2) I believe this one should fix :

 creating config/chroot_local-includes/etc/apt/preferences :
 Package: squashfs-tools
 Pin: version 1:3.2r2-*
 Pin-Priority: 1001

 to maintain it even if an upgrade is coming.


 but i didn't manage to do a clean build since i have other problem with
 apt-proxy getting stuck.

 ___
 debian-live-devel mailing list
 debian-live-devel@lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel


http://dennou-h.gfd-dennou.org/debian/pool/main/s/squashfs/squashfs-tools_3.2r2-9_i386.deb
I found it. And sorry about the Fwd: I did earlier, you can just ignore that.

___
debian-live-devel mailing list
debian-live-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel


Re: Lenny-LiveCD boot error (/bin/sh: can't access tty ...)

2008-02-12 Thread Jordi Pujol
 Can be because fstype does not detect the filesystem type of squashfs 3.3
 files.

 I propose the following patch for live-initramfs, where the filesystem
 type, if not detected, is assumed from the file extension.

this patch works well with kernel 2.6.24,
but this patch does not solve the problem in testing,
the squashfs version is 3.2 for the kernel in testing 

apt-cache policy  squashfs-modules-2.6.22-3-686
squashfs-modules-2.6.22-3-686:
 2.6.22+3.2r2-9 0
990 http://ftp.debian.org testing/main Packages

and squashfs-tools is only available in version 3.3 in any of testing or 
unstable,

apt-cache policy  squashfs-tools
squashfs-tools:
 1:3.3-3 0
990 http://ftp.debian.org testing/main Packages
  9 http://ftp.debian.org unstable/main Packages

Is that the available packages do not allow to do a correct install in 
testing ?

The only way is using the packages for kernel 2.6.24 in unstable ?

___
debian-live-devel mailing list
debian-live-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel


Lenny-LiveCD boot error (/bin/sh: can't access tty ...)

2008-02-12 Thread Sebastian Holler
I tried to build a Lenny image on my own with live-helper1.0~a37~20071120:

lh_config \
--distribution lenny --packages-list 'kde-core' --architecture i386 \
--language de --bootloader syslinux --bootstrap debootstrap \
--apt-secure disabled --union-filesystem aufs \
--linux-packages 'linux-image-2.6 aufs-modules-2.6 squashfs-modules-2.6' \
--initramfs 'live-initramfs'
lh_clean
lh_build

The boot procedure of the final Live-CD breaks and opens a BusyBox.
The live.log contains the following:

mount: Mounting /dev/hda2 on /live/image failed: No such device
stdin: error 0
debug: Can not mount backdev /dev/loop0 (Image = 
/live/image/live/filesystem.squashfs) on croot/imagename 
//filesystem.squashfs
mount: Mounting /dev/loop on //filesystem.squashfs failed: Invalid argument.
...

The mount-command inside the busybox shows, that /dev/hdc is mounted on 
/live/image (and not /dev/hda2). Therefore in /live/image/live I can see 
the file filesystem.squashfs.

Using mksquashfs with -no-lzma option (by editing 
/usr/bin/lh_binary_rootfs) didn't solve this problem. (There are no 
problems with building Etch images.)

Can anyone help me?

Sebastian H.

___
debian-live-devel mailing list
debian-live-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel


lh_build on lenny and squashfs-tools

2008-02-12 Thread Philippe Lhardy
Hi,

live builds on lenny are broken due to latest squashfs-tools v 3.3.
they generate 3.1 squash version, where squashfs kernel module can't
support.
using squashfs-tool 1:2.2r2-9 proove to make it work, but it is not easy to
set it up for lh_build usage
since it is upgraded to 1:3.3-3 automatically.

1) i put squashfs-tools_3.2r2-9_i386.deb in local packages
config/chroot_local-packages/squashfs-tools_3.2r2-9_i386.deb

2) I believe this one should fix :

creating config/chroot_local-includes/etc/apt/preferences :
Package: squashfs-tools
Pin: version 1:3.2r2-*
Pin-Priority: 1001

to maintain it even if an upgrade is coming.


but i didn't manage to do a clean build since i have other problem with
apt-proxy getting stuck.
___
debian-live-devel mailing list
debian-live-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel

Fwd: lh_build on lenny and squashfs-tools

2008-02-12 Thread maybeway36
Any idea where I can find 3.2r2? It's gone from ftp.debian.org.

___
debian-live-devel mailing list
debian-live-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel