Bug#506589: "No such file or directory" output in df
Package: live-initramfs Version: 1.139.1-4 Severity: minor > this could be a bug of live-initramfs, please file a bug > for it in the debian BTS. OK, here it goes: I have the "No such file or directory" output in df: $ df Filesystem 1K-blocks Used Available Use% Mounted on rootfs 194040 3284190756 2% / udev 1024096 10144 1% /dev /dev/scd0 325228325228 0 100% /live/image df: `/001-base.squashfs': No such file or directory df: `/002-vars.squashfs': No such file or directory tmpfs 194040 3284190756 2% /live/cow aufs194040 3284190756 2% / tmpfs 194040 0194040 0% /live tmpfs 194040 0194040 0% /lib/init/rw tmpfs 19404028194012 1% /dev/shm >> df: `/001-base.squashfs': No such file or directory df: >> `/002-vars.squashfs': No such file or directory > > look at /proc/mounts, df looks at /etc/mtab which is still misaligned > and manually crafted. Here is the /proc/mounts: $ 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 /001-base.squashfs squashfs ro,noatime 0 0 /dev/loop1 /002-vars.squashfs squashfs ro,noatime 0 0 . . . I use the nfsbooted package, which is the reason for the error, because "the mtab ... is misaligned since it refers to another "chroot"". Having remove the nfsbooted package, the error has gone. regards -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (300, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-grml (SMP w/1 CPU core; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#506591: A central place for stacked filesystems
Package: live-initramfs Version: 1.139.1-4 Severity: wishlist On Thu, 20 Nov 2008 18:07:48 +, T o n g wrote: 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. 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? On Thu, 20 Nov 2008 21:50:19 +0100, Daniel Baumann wrote: > /live/module (or /live/modules ?) sounds sane to me, go on. Both are fine, but let's use /live/module, as per the Perl Best Practices suggests, because normally it is going to be addressed individually, e.g., /live/module/so_and_so which sounds better than /live/modules/so_and_so regards -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (300, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-grml (SMP w/1 CPU core; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#506591: A central place for stacked filesystems
In summary, 1. create a central place for stacked filesystems, eg, /live/module 2. expose the mounted individual stacked filesystems; make them accessible -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#506591: A central place for stacked filesystems
On Mon, Nov 24, 2008 at 3:17 AM, Marco Amadori <[EMAIL PROTECTED]> wrote: > On Saturday 22 November 2008, 22:20:18, Tong Sun wrote: > >> It seems that I can't access the stacked filesystems individually. . . > > Try to boot with "showmounts" :-) Ah, thx, so the side-question is solved. > If I understood what you meant, this bug could be closed. but the main wish, ie, a central place for stacked filesystems, still holds. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Configurable persistent device names
Package: live-initramfs Severity: wishlist Hi, Currently live-initramfs will look for hard-coded partitions labeled "live-rw"/"home-rw", and files called "live-sn*"/"home-sn*" for persistent and snapshot partitions or files. This will cause problem when trying to run/test two or more live-initramfs based distros on the same machine. Different debian-live based distros need different persistent devices (partitions or files) and contents. Configurable persistent device names is the solution. Thanks -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (300, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.28-grml64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#536796: use swap files on boot up
Package: live-initramfs Severity: wishlist Hi, To many people, Debian-Live base distros are one-time-quick-fix things, but to me, it is a solution to use my Linux on boxes otherwise impossible. More often than not, I'm faced with boxes that have little ram, and impossible to have the luxury to create a swap partition. So swap files that can be picked on boot up is most valuable. Since nowadays Linux utilizes swap files as efficient as swap partition, using flexible swap files are more encouraged than the fixed swap partition. Use swap files on boot up is a small fix with huge advantages. Thanks -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (300, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.28-grml64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#544583: Need to control ramfs size
Package: live-initramfs Version: 1.157.2-1 Severity: minor Hi, I've bumped into "out of disk space" problem when using Debian Live. I am using the persistent root and a big swap partition, but mount tmp on ramfs -- in fstab: /dev/ram7 /var/tmpramfs defaults,rw,auto,dev0 0 /dev/ram/tmpramfs defaults,rw,auto,dev0 0 but it didn't go long before running into "out of disk space" problem. I hope that live-initramfs can control how big the /dev/ram device is (better be 1/8 of swap spaces for example). Thanks Tong Sun -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (300, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.28-grml64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages live-initramfs depends on: ii busybox 1:1.10.2-2 Tiny utilities for small and embed ii file 5.00-1 Determines file type using "magic" ii initramfs-tools 0.93.2 tools for generating an initramfs ii sudo 1.7.0-1Provide limited super user privile ii udev 0.141-1/dev/ and hotplug management daemo ii user-setup1.23 Set up initial user and password Versions of packages live-initramfs recommends: pn cryptsetup (no description available) ii eject 2.1.5+deb1+cvs20081104-5 ejects CDs and operates CD-Changer pn uuid-runtime (no description available) ii wget1.11.4-2 retrieves files from the web Versions of packages live-initramfs suggests: pn curlftpfs (no description available) pn genext2fs (no description available) pn httpfs2(no description available) pn loop-aes-utils (no description available) pn mtd-tools (no description available) ii squashfs-lzma-tools [squashfs 3.3-1 Tool to create and append to squas -- no debconf information -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#544583: Need to control ramfs size
On Tue, Sep 1, 2009 at 2:24 PM, Daniel Baumann wrote: > Tong Sun wrote: >> I've bumped into "out of disk space" problem when using Debian >> Live. I am using the persistent root and a big swap partition, >> but mount tmp on ramfs -- in fstab: > > i don't understand. if you use (root) persistency, you don't have a ram > disk at all, but all writes are dumped to the persistency partition. > > so how/why does ramfs matter? As shown in OP: /dev/ram7 /var/tmpramfs defaults,rw,auto,dev0 0 /dev/ram/tmpramfs defaults,rw,auto,dev0 0 I.e., I don't want all writes dumped to the persistency partition, so I excluded /tmp & /var/tmp by using ramfs. I hope that live-initramfs can have a boot parameter to control how big the /dev/ram device is. thanks -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
