Age | Commit message (Collapse) | Author | Files |
|
* this avoids "/init: source: 64: Can't open /initrd.d/0*" for initramfs
images built without the bootldr-buster module.
|
|
initramfs-module-bootmenu.
* That's because otherwise it's half-solution - after kexec, there won't be
delay, and rootfs won't be detected.
* Again, people who don't need and don't want delay, should pass rootdelay=0.
|
|
|
|
|
|
output device.
* This is to workaround bogus console= passed in by bootldr.
|
|
console issue.
* The main trouble is the bogus console=ttySA0 passed by bootldr
It appears that kernel doesn't have protection against only invalid
consoles being passed on the command line, which means that the
kernel is deaf and dumb when booted by bootldr.
|
|
stupidity.
|
|
* Extend plugin protocol: plugins matching pattern '0*' are early-init,
executed ASAP after boot, before kernel command and block devices are scanned.
And thus, they can affect parsing of kernel command line (by overriding $CMDLINE)
or detection of block devices (e.g. by loading additional modules).
|
|
delay still.
* So people who don't bother to set correct rootdelay still have good chance
for there SD/CF cards detected.
* To disable the feature, explicit rootdelay=0 should be passed on kernel
command line.
|
|
|
|
param.
|
|
shell" option.
|
|
* FSTYPE useful for FSes not automatically recognized by mount (e.g. jffs2).
|
|
|
|
* Be sure to pass original command line contents to new kernel.
* Add protection against infinite recursive kexecing.
|
|
* Instead of switch_root'ing to it, which was the only working mode previously.
So, now, if there's /boot/zImage in rootfs, it will be kexec'ed too. Otherwise,
switch_root will happen.
* Caveat: there should be initramfs for new (kexec'ed to) kernel too, too handle
its loading of rootfs as selected by interactive bootloader. This can be very
same kernel as for bootloader, with bundled initramfs-bootmenu-image (which
has special check - if root is explicitly specified on command line, then skip
interactive selection); or, as a kind of optimization, that could be initramfs-image
(no interactive part). Finally, initramfs (any of there two or other) can be
a standalone file in rootfs, /boot/initramfs.bin.
|
|
* This is likely not enough to make jffs2 boot work.
|
|
consistency.
* Checks that version of the boot kernel matches that of modules installed in
rootfs.
* A step towards providing manageable upgrade path for kernels outside rootfs.
|
|
|
|
NFS root.
|
|
buggy klibc's fstype.
|
|
initramfs-uniboot.
* For now, supports booting from ext2/ext3 partitions and from ext2/ext3 loopback
images placed on vfat partition.
|
|
|
|
* Use -q for modprobe, and as that apparently doesn't help bitbake's modprobe,
redirect output to /dev/null.
|
|
nodes.
|
|
|
|
|
|
|
|
|
|
kernel does.
|
|
* Design principles:
* This initramfs just mounts roots and runs init on it, nothing else.
* Whenever possible, existing kernel parameters are used. When extended
boot methods are provided, new parameters mimick/adhere to existing
conventions.
* System is modular/pluggable - each mount method is in own module with
more or less well defined interface, it's possible to construct complete
system with any combination of modules.
* Modules includes: initramfs-module-loop, initramfs-module-nfs, to boot
from loop devices (including recursive loops) and NFS, correspondingly.
|
|
* Untested.
|
|
* Need too add parsing of kernel cmdline instead of hardcoded params.
|