From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] dracut kernel hook appears to have issues
Date: Mon, 22 Mar 2021 04:51:29 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29672@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2857 bytes --]
New issue by CameronNemo on void-packages repository
https://github.com/void-linux/void-packages/issues/29672
Description:
### System
* xuname:
*output of ``xuname`` (part of xtools)*
* package: dracut-051_2
### Expected behavior
dracut kernel hook does not send a bunch of info on stderr
### Actual behavior
Seeing this on the output, even though dracut seems to make the initramfs alright:
```
Executing post-install kernel hook: 20-dracut ...
dracut-install: No SOURCE argument given
Usage: dracut-install -D DESTROOTDIR [-r SYSROOTDIR] [OPTION]... -a SOURCE...
or: dracut-install -D DESTROOTDIR [-r SYSROOTDIR] [OPTION]... SOURCE DEST
or: dracut-install -D DESTROOTDIR [-r SYSROOTDIR] [OPTION]... -m KERNELMODULE [KERNELMODULE …]
Install SOURCE (from rootfs or SYSROOTDIR) to DEST in DESTROOTDIR with all needed dependencies.
KERNELMODULE can have the format:
<absolute path> with a leading /
=<kernel subdir>[/<kernel subdir>…] like '=drivers/hid'
<module name>
-D --destrootdir Install all files to DESTROOTDIR as the root
-r --sysrootdir Install all files from SYSROOTDIR
-a --all Install all SOURCE arguments to DESTROOTDIR
-o --optional If SOURCE does not exist, do not fail
-d --dir SOURCE is a directory
-l --ldd Also install shebang executables and libraries
-L --logdir <DIR> Log files, which were installed from the host to <DIR>
-R --resolvelazy Only install shebang executables and libraries
for all SOURCE files
-H --hostonly Mark all SOURCE files as hostonly
-f --fips Also install all '.SOURCE.hmac' files
--module,-m Install kernel modules, instead of files
--kerneldir Specify the kernel module directory
--firmwaredirs Specify the firmware directory search path with : separation
--silent Don't display error messages for kernel module install
--modalias Only generate module list from /sys/devices modalias list
-o --optional If kernel module does not exist, do not fail
-p --mod-filter-path Filter kernel modules by path regexp
-P --mod-filter-nopath Exclude kernel modules by path regexp
-s --mod-filter-symbol Filter kernel modules by symbol regexp
-S --mod-filter-nosymbol Exclude kernel modules by symbol regexp
-N --mod-filter-noname Exclude kernel modules by name regexp
-v --verbose Show more output
--debug Show debug output
--version Show package version
-h --help Show this help
```
### Steps to reproduce the behavior
No idea really. Happens on some upgrades, but not others. Most recently `linux5.10 update 5.10.24_1 5.10.25_1 87MB`. Was wondering if anyone else has experienced this.
next reply other threads:[~2021-03-22 3:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 3:51 CameronNemo [this message]
2021-03-22 4:12 ` ericonr
2021-03-22 12:38 ` sgn
2021-03-22 12:50 ` sgn
2021-03-29 4:56 ` CameronNemo
2021-03-29 13:51 ` sgn
2021-04-07 21:14 ` rafaelgoncalves
2021-07-15 12:18 ` [ISSUE] [CLOSED] " ahesford
2021-07-15 12:18 ` ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29672@inbox.vuxu.org \
--to=cameronnemo@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).