IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
This is a patch by Maxim Suhanov <suhanov/group-ib.ru>
aiming to provide integrity and authenticity check for
stage2 rootfs image when required:
- media bootloader passes sha256 hash of stage2 image;
- stage1 early userspace code (that is, propagator)
checks the candidate files against that during search;
- existing file with different checksum results in a warning
with a dialog to just say NO, continue searching for the
proper squashfs image and have a look at that weird one;
- existing file with correct checksum results in booting
as usual.
The check is triggered by "hash=..." kernel boot parameter.
See also http://www.forensicswiki.org/wiki/Forensic_Live_CD_issues
tools.c: In function 'splash_verbose':
tools.c:309:2: warning: implicit declaration of function 'spawn' [-Wimplicit-function-declaration]
stage1.c: In function 'spawn_splash':
stage1.c:165:2: warning: implicit declaration of function 'spawn' [-Wimplicit-function-declaration]
mkdir_dev() use for create subdir with mode 0755 in /dev directory
and return success if subdir already exist.
mkdirs_dev() used mkdir_dev() for create multiple subdirs.
The misoptimization of the final commit version resulted
in strlen operating on a 5 char too short string thus
delivering "device names" like "/de" and "/de1".
Thanks yet another late colleague :)
Essentially finished what gfd2a83d started; this is to avoid
"/bin/plymouth: No such file or directory" spam all over the place
when "splash" boot parameter is present but plymouth itself is absent.
Here's the culprit:
open("/lib/modules/3.4.7-std-def-alt1/modules.dep.bin", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/lib/modules/3.4.7-std-def-alt1/modules.dep.bin", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/lib/modules/3.4.7-std-def-alt1/modules.alias.bin", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
exit_group(1) = ?
+++ exited with 1 +++
[root@builder .in]# ls -l /lib/modules/3.4.7-std-def-alt1/modules.dep*
-rw-r--r-- 1 root root 370664 Jul 29 18:20 /lib/modules/3.4.7-std-def-alt1/modules.dep
Here's the typical result for mkimage:
ERROR: could not open directory /tmp/mkmodpack.sWzMWshm9Z/lib/modules/3.4.7-std-def-alt1: No such file or directory
FATAL: could not search modules: No such file or directory
mkmodpack: Failed to create modules dependencies.
The initial intention was that at least one second
should pass before retesting for the insmod result
*but* that appears to be both unneeded and boring;
let's skip even an extra second if there's no need.
It's pretty silly to wait for 10 seconds at once
while not having ensured that the module is being
loaded indeed...
Thanks rom_as@ for pointing this out.