Jonathan Brandmeyer wrote:
> /dev/mapper is empty except for control
Does running "vgscan" and/or "vgchange -ay" from the initramfs shell create
any nodes in /dev/mapper?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Jonathan Brandmeyer wrote:
> So, what do I need to edit to fix this? Alternatively,
> what command should I try to run after modprobing in
> ide-disk and ide-generic?
The problem is that ide-disk and ide-generic are not loaded when dm-mod is
loaded so when it performs its initial device scan it s
maximilian attems wrote:
> please retest with latest initramfs-tools in unstable
And when doing so, please take note of merged bugs 332824, 337497 and 342925
(i.e. make sure that ide-disk and possibly ide-generic are added to
/dev/mapper/control before generating the new initramfs image).
It seem
This problem is not limited to sparc64, I've encountered it on i386 after
upgrading from initramfs-tools 0.41 to 0.44 (when using a kernel compiled with
modular ide).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: initramfs-tools
Severity: important
The latest version of initramfs-tools (0.44) calls update-initramfs in
postinst to regenerate the latest initramfs on upgrades (see initramfs-tools
changelog, version 0.40ubuntu6).
This can be potentially very dangerous if the newer initramfs-tools for
tags 339091 - moreinfo
stop
maximilian attems ([EMAIL PROTECTED]) wrote:
> can you please confirem that your manpage was written under "PUBLIC
> DOMAIN" license as the initramfs-tools package?
I hope this is sufficient:
I, the creator of this work, hereby release it into the public domain. This
Package: initramfs-tools
Severity: minor
Currently, initramfs-tools relies upon usr/initramfs_list in 2.6 kernels
to create the /dev and /root directories. The attached patch will make
sure that they are created along with the console and null device nodes.
This has two advantages:
1) If usr
y kernels
(see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339374).
Regards,
David Härdeman
[EMAIL PROTECTED]
--- ketchup.orig2005-11-17 22:35:02.0 +0100
+++ ketchup 2005-11-17 22:37:14.0 +0100
@@ -671,6 +671,9 @@
# Process args
+if not os.path.exists(options["
Package: ketchup
Severity: wishlist
If ketchup is run with the -d command, it would be nice if it created
the target directory (if it doesn't exist) instead of crashing:
([EMAIL PROTECTED]:~/kernel)$ ketchup -G -a /home/david/kernel/tarballs -d
./linux-2.6.14.2 2.6.14.2
Traceback (most recen
Package: ketchup
Severity: normal
Ketchup fails to download recent 2.6.x.y kernels:
([EMAIL PROTECTED]:~/kernel)$ mkdir linux-2.6.14.2
([EMAIL PROTECTED]:~/kernel)$ ketchup -G -a /home/david/kernel/tarballs -d
./linux-2.6.14.2 2.6.14.2
None -> 2.6.14.2
Unpacking linux-2.6.14.tar.bz2
rmdir: linu
Package: initramfs-tools
Severity: important
With the recent udev version (0.074-3), /sbin/udevsynthesize tries to
run /lib/udev/udevsynthesize if the kernel is a recent version. This
fails as /lib/udev/* is not copied to the initramfs image meaning that
the boot fails.
Re,
David
--
To UNS
This was discussed on debian-devel [1]. As long as the debian kernel is
shipped with CONFIG_LEGACY_PTYS enabled I'd say that the current
behaviour is correct.
The proper fix would be to:
a) change the default kernel config; or
b) change the udev rules
not to do any special changes to initramf
Russel Coker wrote:
The initramfs generated on a LVM IDE system does not create /dev/hda* device
nodes, so vgchange doesn't discover any LVM devices and therefore the
machine can't boot.
That is weird, I have root-on-lvm-on-hda and the devices are created
+ the system boots just fine for me.
Package: initramfs-tools
Severity: minor
Tags: patch
Currently /usr/share/initramfs-tools/init kills udev after init-premount
scripts have executed. However, more devices might become available as a
result of running the local scripts.
I therefore suggest to kill udev as late as possible (rig
Package: initramfs-tools
Severity: minor
Tags: patch
This patch adds a separate function to load a filesystem driver which
first checks if it is already compiled into the kernel which should
remove some superflous modprobe error messages if it is.
Re,
David
Index: initramfs-tools-0.38/scripts
quot; ]; then
panic "Frobnication executable not found"
fi
if [ ! -e "/dev/mapper/frobb" ]; then
panic "Frobnication device not found"
fi
log_begin_msg "Starting frobnication"
/sbin/frobnicate "/dev/mapper/frobb" || panic "Frobnication failed"
log_end_msg
exit 0
.fi
.RE
.SH AUTHOR
The initramfs-tools are written by Jeff Bailey <[EMAIL PROTECTED]>.
.PP
This manual was written by David Härdeman <[EMAIL PROTECTED]>.
Package: initramfs-tools
Severity: wishlist
Currently /usr/share/initramfs-tools/scripts/local checks for the
presence of the root device node after local-top has been run but before
local-premount has been run an panics if it can't find it:
# Get the root filesystem type
if [ ! -e "${ROOT}"
Package: initramfs-tools
Severity: wishlist
Currently the last line in
/usr/share/initramfs-tools/scripts/local-top/lvm only activates the
volume group which seems to contain the root fs.
In order to support features such as root-auto-probing (bug #337682) and
cryptoroot-over-lvm, it would b
this patch
applied and verified that it does indeed fix the problem and it seems to
have no side effects.
I hope that a fixed version can be included in sarge as soon as possible
since this could potentially be a security issue (e.g. if the account
has been disabled, access would still be gra
I am still seeing this problem in the version of courier included in
sarge. Courier seems to happily ignore the result of the pam check and
continue anyway (when using the pam_tally module).
I would suggest that this warrants the security tag and a security
update as it allows a user to try to
On Wed, Feb 09, 2005 at 07:22:31PM +0100, Michael Meskes wrote:
On Fri, Aug 20, 2004 at 10:28:12PM +0200, David Härdeman wrote:
I can still see this behavious (5 years later), with a recent (2.6.8.1)
kernel and hardware watchdog (i8xx-tco).
Do you still see the bug? Do you have any time to debug
601 - 621 of 621 matches
Mail list logo
