+++ This bug was initially created as a clone of Bug #1260788 +++ Description of problem: I am trying to add a file to my initramfs but it is not gettting created. Version-Release number of selected component (if applicable): 041-14.fc22 How reproducible: I created a test file called test to include in the / directory of the initramfs but it does not get added. Steps to Reproduce: 1. Create a test file called test with test in the body 2. Ran "dracut --force --include test /" 3. No file is created. Actual results: lsinitrd|grep test Arguments: --force --include 'test' '/' Expected results: lsinitrd|grep test Arguments: --force --include 'test' '/' /test Additional info: I tried to define the destination completely (including the filename) and it only create an empty test directory with no file in it. Here is the command I ran for that: dracut --force --include test /test --- Additional comment from Harald Hoyer on 2015-09-08 04:36:30 EDT --- # echo test > test # ls -l test -rwxrwxr-x 1 harald harald 5 8. Sep 10:34 test # dracut -f --include $(pwd)/test /test test.img # lsinitrd test.img /test test # lsinitrd test.img |fgrep test Image: test.img: 12M Arguments: -f --include '/home/harald/test' '/test' -rwxrwxr-x 1 root root 5 Sep 8 10:34 test Works for me with the full path. --- Additional comment from Mikhail Campos on 2016-06-28 10:59:07 EDT --- I can confirm the bug against fc23. It seems to work under the normal, user but only when full path is used. Moreover, it's broken when running under the root (even with full path): 1. su - 2. ls -la mycfg.conf -rw-r--r-- 1 root root 27 Jun 28 16:47 mycfg.conf 3. dracut --include $(pwd)/mycfg.cfg /etc/myconf.conf -f myinitrd.img 4. lsinitrd myinitrd.img | grep myconf Arguments: -f --include '/tmp/mycfg.cfg' '/etc/myconf.conf' drwxr-xr-x 2 root root 0 Jun 28 17:33 etc/myconf.conf It creates file of zero size, but the target one was not empty. Moreover, we have misleading information about --include option using man: "...--include can only be specified once." and later in the man: "--include <SOURCE> <TARGET> ... This parameter can be specified multiple times." Moreover, consequent invocation of dracut --include deletes previous added information (not sure whether it's supposed to be or not). Version-Release number of selected component (if applicable): 043-60.git20150811.fc23
Actually, skip the note about the 'root' cause incorrect file names were used on test steps (mycfg.conf != mycfg.cfg). But it would be better if some warning was printed on attempt to include a non-existing file.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.