Re: No such file or directory reported by df

On Thursday 20 November 2008, 01:08:30, T o n g wrote: > $ cat /proc/mounts > rootfs / rootfs rw 0 0 > none /sys sysfs rw,nosuid,nodev,noexec 0 0 > none /proc proc rw,nosuid,nodev,noexec 0 0 > udev /dev tmpfs rw,size=10240k,mode=755 0 0 > /dev/scd0 /live/image iso9660 ro,noatime 0 0 > /dev/loop0 /

"BOOT FAILED!" with a live-rw partition (ext2 and ext3 tested)

I get Remounting /dev/sdb2 ro on /cow failed and a prompt (initramfs) when trying to boot with "persistent" and a partition named "live-rw". cat /live.log gives mount: mounting /dev/sdb2 on /cow failed: Device or resource busy the list of mounts includes / /sys /proc /dev /live/image /filesys

problem with aufs

Hi, I try to make a CD with live-helper from Debian etch, with linux-image-2.6.26-1-486, aufs-modules-2.6.26-1-486 (unionfs not available for this kernel), and squashfs-modules-2.6.26-1.486 from lenny (while this kernel is running). In config/chroot LH_UNION_FILESYSTEM="aufs", LH_LINUX_FLAVOURS="4

Re: problem with aufs

On Thu, Nov 20, 2008 at 12:50:21PM +0100, Olaf Till wrote: > ... > For the case making a lenny CD should be a possible solution: I tried > this and got an error message "Unknown flavor lenny" (probably from > cdebootstrap). Sorry, it was actually: E: Unknown suite lenny -- To UNSUBSCRIBE, email

Bug#506321: live-initramfs: improve documentation for persistency feature

Package: live-initramfs Version: 1.139.1-4 Severity: wishlist The documentation regarding the persistency feature should be improved. The live-snapshot manpage is lacking some usage examples. I'd like to see stuff from http://live.debian.net/manual/html/persistence.html integrated within the off

RE: "BOOT FAILED!" with a live-rw partition (ext2 and ext3 tested)

This would be SWEET and I could see a PERFECT use for something like this. PXE boot a base 30MB Live image then as needed, download and add the different Live Systems you need/want to be mounted. This would save on network bandwidth as well as give some flexibility to clients with OLDER hardware

A central place for stacked filesystems

Hi, It seems that I can't access the stacked filesystems individually. I.e., the mount point of each individual stacked filesystems is not accessible for me. Is it just me or it is the "feature"? I hope, as we might have several stackable fs in /live, that the mount point for them is not from

Re: problem with aufs

Olaf Till wrote: > Sorry, it was actually: > E: Unknown suite lenny always use latest live-helper from sid, always use latest debootstrap from sid. both install just fine without any change on lenny and also etch. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email:

Re: A central place for stacked filesystems

T o n g wrote: > I hope, as we might have several stackable fs in /live, that the mount > point for them is not from root, but some central location, say under > /live/module, for example? /live/module (or /live/modules ?) sounds sane to me, go on. -- Address:Daniel Baumann, Burgunders

Re: "BOOT FAILED!" with a live-rw partition (ext2 and ext3 tested)

On Thu, Nov 20, 2008 at 12:23:31PM +0100, Hans Ekbrand wrote: > I get > > Remounting /dev/sdb2 ro on /cow failed > > and a prompt (initramfs) when trying to boot with "persistent" and a > partition named "live-rw". > > cat /live.log gives > > mount: mounting /dev/sdb2 on /cow failed: Device or

building lenny, how can I use live-initramfs from sid?

Lenny has live-initramfs 139-3, Sid has live-initramfs 139-4 1. Is it possible to build a lenny image, but with live-initramfs 139-4 from Sid? 2. If so, then how? I tried to manually install 139-4 in the chroot before rebuilding, to no avail. -- Hans Ekbrand (http://sociologi.cjb.net) <[EMAIL

Re: building lenny, how can I use live-initramfs from sid?

On Fri, Nov 21, 2008 at 12:25:18AM +0100, Hans Ekbrand wrote: > Lenny has live-initramfs 139-3, Sid has live-initramfs 139-4 > > 1. Is it possible to build a lenny image, but with live-initramfs > 139-4 from Sid? > > 2. If so, then how? > > I tried to manually install 139-4 in the chroot before

persistent partition live-rw is not cleanly unmounted during shutdown

Hi all, messages during shutdown prozess on a live system with persistent partition telling me that /live/cow is busy and e2fsck on a live-rw partition (on a usb harddisk) reports errors after shutdown is complete. I suppose it will not be remounted ro or something like that. I use the live-he

/etc/resolv.conf bug

Hi, There is a bug with /etc/resolv.conf. One should manually make the /etc/resolv.conf symbolic link to have dhclient working properly after a fresh build: ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf This is tested with Lenny gnome-desktop Regards, Olivier -- To UNSUBSCRIBE,