Bug#497561: marked as done (live-initramfs: mount-call in scripts/init-bottom/udev has wrong syntax)
Your message dated Thu, 26 Feb 2009 11:08:01 +0100
with message-id <49A66A01.3030300@debian.org>
and subject line Re: live-initramfs: mount-call in scripts/init-bottom/udev has wrong syntax
has caused the Debian Bug report #497561,
regarding live-initramfs: mount-call in scripts/init-bottom/udev has wrong syntax
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
497561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497561
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: live-initramfs: mount-call in scripts/init-bottom/udev has wrong syntax
- From: Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
- Date: Tue, 02 Sep 2008 18:38:41 +0200
- Message-id: <20080902163841.19200.43511.reportbug@z6.physik.fu-berlin.de>
Package: live-initramfs
Severity: important
Tags: patch
The udev-script in scripts/init-bottom/ on the ramdisk created for live-initramfs seems to
use an deprecated syntax for the mount-call:
mount -n -o move /dev $rootmnt/dev
This will cause the booting live system to abort with a kernel-panic (mount complaining
with "You must specify the filesystem-type").
Unpacking the ramdisk, replacing the above line with:
mount --move /dev $rootmnt/dev
fixed it and the live-system will boot properly.
The initrd I used was created by "make-fai-nfsroot" in the fai-server-package, but the fai-maintainers
told me this would rather be a bug in "live-initramfs", so I post it here.
Regards,
Adrian
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages live-initramfs depends on:
ii busybox 1:1.10.2-1 Tiny utilities for small and embed
ii file 4.25-1 Determines file type using "magic"
ii initramfs-tools 0.92f tools for generating an initramfs
ii sudo 1.6.9p17-1 Provide limited super user privile
ii udev 0.125-5 /dev/ and hotplug management daemo
pn user-setup <none> (no description available)
Versions of packages live-initramfs recommends:
ii eject 2.1.5+deb1-1 ejects CDs and operates CD-Changer
pn uuid-runtime <none> (no description available)
ii wget 1.11.4-1 retrieves files from the web
Versions of packages live-initramfs suggests:
pn curlftpfs <none> (no description available)
pn genext2fs <none> (no description available)
pn httpfs2 <none> (no description available)
pn loop-aes-utils <none> (no description available)
pn mtd-tools <none> (no description available)
pn squashfs-tools <none> (no description available)
--- End Message ---
--- Begin Message ---
Hi,
to summarise:
* live-initramfs never had any scripts in init-bottom.
* the scripts/live script uses correct mount options for the included
mount program inside the initramfs.
* i cannot reproduce any panic with live images.
* i cannot reporoduce any "You must specify the filesystem-type"
message at boot time.
therefore, I'm closing this bug. feel free to reopen if you have
evidence for the bug with current systems.
also, if there is no standard way of generating an image where it
happens (e.g. when not using live-helper), consider providing a test
image so that a particular image can be debugged.
Regards,
Daniel
--
Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email: daniel.baumann@panthera-systems.net
Internet: http://people.panthera-systems.net/~daniel-baumann/
--- End Message ---
Reply to: