Age | Commit message (Collapse) | Author |
|
seems lots of people fancy it so lets add it.
Signed-off-by: maximilian attems <maks@debian.org>
|
|
fixes unionfs-fuse to service requests made by non-root users.
[ merge from 0.92bubuntu31, this does not interfer with UMASK setting of
created initramfs, but only concerns / of initramfs -maks ]
Signed-off-by: maximilian attems <maks@debian.org>
|
|
no point in spamming that for quiet boot.
Signed-off-by: maximilian attems <maks@debian.org>
|
|
if tsort is available, use it instead of custom sorting code
if a pre-cached order file is available, use that instead
[ move cache_run_scripts from scripts/functions to hook-scripts
as only used on mkinitramfs build and not on boot ]
Signed-off-by: maximilian attems <maks@debian.org>
|
|
it is no longer used on boot, saves initramfs space and thus speed.
Signed-off-by: maximilian attems <maks@debian.org>
|
|
partialy revert "nuke thermal hooks",
this is needed for broken hardware.
no point in us loading them, as udev will do it anyway and
should soon run earlier.
This reverts commit c5e39cd1cb1dc9f6a18de07e137ef47ecc8f8cc6.
|
|
fixed the commandline argument to select the compressor.
also your test with "command" needed to be negated otherwise the
fallback to gzip would take place everytime.
--
frohe ostern
Bert Schulze
[ nuked trailing whitespace, and add comment for usage() ]
Signed-off-by: maximilian attems <maks@debian.org>
|
|
forgot to add here on compress commit.
|
|
this version uses /etc/initramfs-tools/initramfs.conf to determine
the compression method, checks kernel and userspace support with
fallback to gzip. Since LZO didnt work for me at all with 2.6.33
I left that out for now.
(closes: #533903)
[ minor changes in mkinitramfs code ]
Signed-off-by: maximilian attems <maks@debian.org>
|
|
allows wider usage.
(closes: #487409)
Reported-by: Christoph Anton Mitterer <calestyo@scientia.net>
Signed-off-by: maximilian attems <maks@debian.org>
|
|
[ merge from 0.92bubuntu1 ]
Reported-by: Ben Hutchings <ben@decadent.org.uk>
Signed-off-by: maximilian attems <maks@debian.org>
|
|
do not trust mount as this is not the thing we look at on boot.
(closes: #519800)
as bonus run blkid if fstype has no idea.
Reported-by: Martin Michlmayr <tbm@cyrius.com>
Signed-off-by: maximilian attems <maks@debian.org>
|
|
they cause cpio to explode (LP: #540686).
[ merge from 0.92bubuntu70 ]
(closes: #575157)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
Allows to redirect the console early.
[ merge from 0.92bubuntu71 ]
Signed-off-by: maximilian attems <maks@debian.org>
|
|
[ merge from 0.92bubuntu71 ]
Signed-off-by: maximilian attems <maks@debian.org>
|
|
Reported-by: Loïc Grenié <loic.grenie@gmail.com>
Signed-off-by: maximilian attems <maks@debian.org>
|
|
I thought I'd experiment a bit with MODULES=DEP, but it seems this will
not work. The atiixp module is properly installed into the initrd (I'm
not sure how), but it doesn't end up in /conf/modules. Instead, the
/conf/modules ends up as:
radeonfb
fbcon
vesafb
pci:v00001002d00004376sv00001462sd00000131bc01sc01i8a
ide-gd
ATIIXP_IDE
pci:v00001002d00004376sv00001462sd00000131bc01sc01i8a
unix
Of these, the ide-gd and ATIIXP_IDE modules come from walking
/sys/devices/pci0000\:00/0000\:00\:14.1/ide0/0.0/. However, the module
is called atiixp, not ATIIXP_IDE. The ATIIXP_IDE comes directly from
sysfs, though:
readlink -f /sys/devices/pci0000\:00/0000\:00\:14.1/driver
/sys/bus/pci/drivers/ATIIXP_IDE
Using driver/module instead of just driver is more robust:
$ readlink -f /sys/devices/pci0000\:00/0000\:00\:14.1/driver/module
/sys/module/atiixp
This would also fix the ide-gd module, which really seems to be called
ide-gd_mod:
$ readlink -f /sys/devices/pci0000\:00/0000\:00\:14.1/ide0/0.0/driver
/sys/bus/ide/drivers/ide-gd
$ readlink -f
/sys/devices/pci0000\:00/0000\:00\:14.1/ide0/0.0/driver/module
/sys/module/ide_gd_mod
$ sudo modprobe ide-gd
FATAL: Module ide_gd not found.
$ sudo modprobe ide-gd_mod
(closes: #567189)
Reported-by: Matthijs Kooijman <matthijs@stdin.nl>
[ checked that this already works in Lenny ]
Signed-off-by: maximilian attems <maks@debian.org>
|
|
sloppy coding without coffee
|
|
check for /etc/elilo.conf
(closes: #534201)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
UMASK variable was supported for some time, but nobody knew about it.
(closes: #536195)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
Here is a bug description and a patch. Please consider it.
The patch solves a an LTSP client problem that arises when
the clients are connected to Cisco switches that have
spanning-tree calculations enabled.
Also related to:
http://git.debian.org/?p=kernel/initramfs-tools.git;a=commitdiff;h=9c3ec61b1a5e2feaa8d9c6de737eaa00eb446a9c
And
http://git.debian.org/?p=kernel/initramfs-tools.git;a=commitdiff;h=115134f07a0dd042355a2a6fb5a5ca987b000f5d
Here in an extensive explaination:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/181258
Also in the following:
I can report the same problem. A number of diskless clients go
flawlessly through a PXE boot, then the net interface is brought down
when the Linux kernel boots and suddenly, dhcp does not work anymore.
Background research on the network: The clients are connected to Cisco
switches. The configuration of the switches makes them run spanning-tree
calculations. This usually takes some seconds but for large networks it
can take up to 30 40 seconds.
The network port on the switch is turned on, when this calculation has
been finished. This is primarily a security measure.
See also: http://networkers-online.com/blog/2008/08/what-is-bpdu-filter/
If this security measure is turned off, the client boots without
problems. :)
To debug the problem, the following boot line was used:
kernel amd64/vmlinuz
append ro initrd=amd64/initrd.img nbdport=2000 debug=100 break=1
ip=dhcp
In my case, this causes a timeout as can be seen on the attached
screenshots. The kernel loads the NIC module e1000e and reports the type
of NIC et.c. The kernel time reported is 5.927 .
The debug shows the following:
configure_networking
[ -n eth0 ]
[-e /tmp/net-eth0.conf ]
ipconfig -t 60 eth0
At about 6.4 in kernel time, the NIC module reports further about it's
IRQ configuration.
Two seconds (2 sec) later at about 8.56 the NIC module reports that the
Link is up at 100 Mbps full duplex.
Some milliseconds later it signals ADDRCONF(NETDEV_CHANGE): eth0: link
becomes ready .
At this point in time, ipconfig is just waiting for an answer to the
DHCP-discover that really was choked by the switch.
Now this is an obvious flaw in the script. It would be much more
reasonable to try repeatedly with increasing timouts. This would also
be much more efficent.
may I suggest the following timeouts:
4
8
16
30
60
The sum of this timeout is about 120 seconds.
I did some testing with exponential timeout with 1 2 4 8 16 30 ...
and it solved the problem, but it seems that ipconfig runs once
additionally after it has actually done the job.
I am running tests now with an exponent of n/1.5 instead of n.
That would give a sequence of (ca)
2 3 4 6 9 16 25 36 64 100
Attached are a jpeg screenshot of the boot sequence and of
course the patch. The patch is relative to the present git
snapshot.
--
Kindest Regards, Anna Jonna Ármannsdóttir, %& A: Because people read from top to bottom.
Unix System Aministration, Computing Services, %& Q: Why is top posting bad?
University of Iceland.
Signed-off-by: maximilian attems <maks@debian.org>
|
|
this is untested. (closes: #415474, #433708)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
If people have both lilo and grub installed they need
to figured out on their own, what they want.
The mbr detection is error prone and a nice hack,
but has survived it's time now that grub.cfg would need
to be parsed in a different way.
warn people that they should act.
(closes: #574553)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
newest debhelper makefile is short and quick.
inspiration from /usr/share/doc/debhelper/examples/rules.tiny.
also drop useless pre-build rule, which seems to stem from old bzr.
it was an vcs that didn't keep the permissions.
Signed-off-by: maximilian attems <maks@debian.org>
|
|
When searching for the root block device, there may be multiple device
mapper indirections.
Fixes MODULES=dep if crypto-root fs has snapshot.
(closes: 573761)
Signed-off-by: Nikolaus Schulz <microschulz@web.de>
Signed-off-by: maximilian attems <maks@debian.org>
|
|
none of the other listed persons are active currently.
|
|
|
|
It doesn't boot with MODULES=dep because mmc_block is missing.
(closes: #548711)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
The attached patch fixes the problem for me (udev no longer ships vol_id
since 146-1).
(closes: #525606)
[ Fix not hardcoding blkid path ]
Signed-off-by: maximilian attems <maks@debian.org>
|
|
we don't need to any more. TODO: lilo might still want .bak's.
[ merge 0.92bubuntu9 + fix manpage
note: indeed the precaution seems no longer needed these days,
but is potentially harmful when /boot space is small. ]
Signed-off-by: maximilian attems <maks@debian.org>
|
|
init: thus drop depmod call.
Don't quote modules.*map, so we actually expand it.
(closes: #465760, #562561)
[ merge from 0.92bubuntu57 and 0.92bubuntu58 ]
Signed-off-by: maximilian attems <maks@debian.org>
|
|
falling back to a tmpfs if not supported by the kernel.
[ merge of 0.92bubuntu61 ]
Signed-off-by: maximilian attems <maks@debian.org>
|
|
as bonus rename confusing function.
(closes: #559535)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
as bonus also simplify the noresume case, just unset it in that case.
this should fix #572858 and friends,
looks broken to me in Lenny too.
Signed-off-by: maximilian attems <maks@debian.org>
|
|
enhances 673abb77821433a67add61ac79d739c6cee9eee0,
to allow scripts to make use of the variable.
Reported-by: Vagrant Cascadian <vagrant@freegeek.org>
Signed-off-by: maximilian attems <maks@debian.org>
|
|
49337bd looks bogus. It adds the test "[
command ... ]" but I think that should be just "command ..."
Reporte-by: Ben Hutchings <ben@decadent.org.uk>
Signed-off-by: maximilian attems <maks@debian.org>
|
|
This removes the need to maintain an explicit list, which always has
some drivers missing.
fixes #553024 partly.
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Signed-off-by: maximilian attems <maks@debian.org>
|
|
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Signed-off-by: maximilian attems <maks@debian.org>
|
|
updated patch against current master, using only shell, and with a cleaner
method to convert BOOTF to a typical mac address.
(closes: #567540)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
as udev will start earlier, care to blacklist before it loads.
Signed-off-by: maximilian attems <maks@debian.org>
|
|
I have attached a patch that makes the keymap hook consider
/etc/console-setup/cached.kmap.gz.
I have also added gunzip to the initramfs because otherwise loadkeys complained
that it was missing and failed to load the keymap.
(closes: #565416)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
Sometimes one misses the error message printed by the panic helper function,
for example when attaching a serial console after the fact, or if kernel
messages resulting from udev activity obscure or scroll it away.
Please consider adding some facility like the attached patch.
Thanks,
Feri.
(closes: #569033)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
USB storage device is not recognized at boot after kernel upgrade
to 2.6.30.
It seems that the usb-storage module has been split into several mini
modules, which are not copied to the initramfs image.
In my case usb-storage.ko is copied but ums-cypress.ko is not copied.
I've attached a patch against hook-functions that fixes this, by using
copy_modules_dir to copy all the modules in kernel/drivers/usb/storage,
instead of just usb-storage.
I've set the severity to important because my USB storage device also
happens to be the boot device...
Cheers,
Avi
(closes: #543568)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
Fix a2127d33 for systems without /proc/modules because the check has
the wrong logic order. (closes: #570678)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
do not add packaging garbage
(closes: #506533)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
|
|
if blkid is on initramfs use it.
Thanks to Joey Hess <joeyh@debian.org> for calling syntax.
Signed-off-by: maximilian attems <maks@debian.org>
|
|
Since fstype does not support btrfs (#548047),
and since udev 150, vol_id no longer exists,
get_fstype sets FSTYPE to "unknown", and
then the root filesystem is mounted using
"mount -t unknown /dev/hda2 /root".
Of course, that fails, and with a really unhelpful error message
("mount: device doesnot exist")
Why not just skip the -t parameter if FSTYPE=unknown?
Mounting the root fs was going to fail, so letting
mount autodetect the fs type can't be worse.
Attached patch does that and got my root on btrfs working.
Workaround: boot with rootfstype=btrfs
Signed-off-by: maximilian attems <maks@debian.org>
|
|
Signed-off-by: maximilian attems <maks@debian.org>
|
|
got report of a box with missing ldd.
as the errors get seded away the user is left with no idea of the failure.
Signed-off-by: maximilian attems <maks@debian.org>
|