Your message dated Mon, 23 Nov 2009 11:45:44 +0100
with message-id <20091123104543.gv25...@baikonur.stro.at>
and subject line Re: Bug#557536: initramfs-tools: break=init doesn't work
has caused the Debian Bug report #557536,
regarding initramfs-tools: break=init doesn't work
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 ow...@bugs.debian.org
immediately.)
--
557536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.92o
Severity: normal
If I add "break=init" to the kernels boot parameters I expect init to run a
shell in the initrds environment instead of running the root partitions init.
But it seems initrds init ignores break=init.
digest of initrds init:
# don't leak too much of env - some init(8) don't clear it
# (keep init, rootmnt)
unset debug
unset MODPROBE_OPTIONS
unset DPKG_ARCH
unset ROOTFLAGS
unset ROOTFSTYPE
unset ROOTDELAY
unset ROOT
unset blacklist
unset break
unset noresume
unset panic
unset quiet
unset readonly
unset resume
unset resume_offset
# Chain to real filesystem
maybe_break init
exec run-init ${rootmnt} ${init} "$@" <${rootmnt}/dev/console
>${rootmnt}/dev/console
panic "Could not execute run-init."
The variable break is unset before maybe_break can read it.
-- Package-specific info:
-- /proc/cmdline
root=/dev/mapper/64GB-LENNYX64--ROOT selinux=0 acpi_sleep=s3_bios
no_console_suspend rootfstype=ext4
-- /proc/filesystems
ext4
fuseblk
ext2
reiserfs
-- lsmod
Module Size Used by
cbc 4192 0
aes_x86_64 9200 1
aes_generic 28096 1 aes_x86_64
ecb 3488 1
radeon 364960 1
drm 191024 2 radeon
i2c_core 26736 1 drm
binfmt_misc 9788 1
kvm_amd 40348 0
kvm 181736 1 kvm_amd
powernow_k8 13508 1
cpufreq_stats 5108 0
cpufreq_conservative 8576 0
cpufreq_userspace 3780 0
cpufreq_powersave 1920 0
nls_utf8 2192 3
cifs 227784 4
ipv6 312720 37
bridge 55984 0
stp 3028 1 bridge
llc 7616 2 bridge,stp
ecryptfs 97912 0
reiserfs 230168 1
ext2 68624 1
fuse 67248 1
dm_crypt 14376 0
loop 17148 0
it87 25256 0
hwmon_vid 3104 1 it87
msr 4056 0
snd_hda_codec_atihdmi 4400 1
usbhid 30912 0
hid 45680 1 usbhid
snd_hda_codec_realtek 272132 1
snd_seq_dummy 3412 0
snd_seq_oss 31584 0
snd_hda_intel 29112 1
snd_hda_codec 73760 3
snd_hda_codec_atihdmi,snd_hda_codec_realtek,snd_hda_intel
snd_seq_midi 7520 0
snd_rawmidi 25008 1 snd_seq_midi
snd_seq_midi_event 8736 2 snd_seq_oss,snd_seq_midi
snd_pcm_oss 40608 0
snd_mixer_oss 17360 1 snd_pcm_oss
snd_pcm 87800 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq 57968 6
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 23632 2 snd_pcm,snd_seq
snd_seq_device 8404 5
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
button 7152 0
snd 68616 13
snd_hda_codec_realtek,snd_seq_oss,snd_hda_intel,snd_hda_codec,snd_rawmidi,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq,snd_timer,snd_seq_device
soundcore 8784 1 snd
snd_page_alloc 10512 2 snd_hda_intel,snd_pcm
processor 42428 1 powernow_k8
evdev 11360 3
ext4 237640 4
mbcache 9476 2 ext2,ext4
jbd2 66272 1 ext4
crc16 2352 1 ext4
dm_mirror 15688 0
dm_region_hash 13520 1 dm_mirror
dm_log 11252 2 dm_mirror,dm_region_hash
dm_snapshot 25548 0
dm_mod 76632 24 dm_crypt,dm_mirror,dm_log,dm_snapshot
sd_mod 30920 8
ahci 40716 6
r8169 36036 0
mii 6112 1 r8169
libata 146944 1 ahci
ehci_hcd 37536 0
scsi_mod 170576 2 sd_mod,libata
ohci_hcd 24092 0
thermal 17472 0
fan 5736 0
thermal_sys 18256 3 processor,thermal,fan
-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
relative_links = yes
do_bootloader = yes
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
BOOT=local
DEVICE=eth0
NFSROOT=auto
-- /etc/crypttab
# <target name> <source device> <key file> <options>
-- System Information:
Debian Release: 5.0.3
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31.4 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages initramfs-tools depends on:
ii cpio 2.9-13 GNU cpio -- a program to manage ar
ii findutils 4.4.0-2 utilities for finding files--find,
ii klibc-utils 1.5.12-2 small utilities built with klibc f
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
ii udev 0.125-7+lenny3 /dev/ and hotplug management daemo
Versions of packages initramfs-tools recommends:
ii busybox 1:1.10.2-2 Tiny utilities for small and embed
initramfs-tools suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.93
On Sun, Nov 22, 2009 at 06:41:58PM +0100, Benjamin S. wrote:
> Package: initramfs-tools
> Version: 0.92o
> Severity: normal
>
>
> If I add "break=init" to the kernels boot parameters I expect init to run a
> shell in the initrds environment instead of running the root partitions init.
> But it seems initrds init ignores break=init.
please next time check if it isn't fixed in newer, thanks.
closing.
--- End Message ---
