public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: alf@i100.no
To: development@lists.ipfire.org
Subject: Re: [PATCH] dracut: Update to 056
Date: Sat, 05 Mar 2022 23:13:51 +0100	[thread overview]
Message-ID: <a995c5d5ab5e42b8a6060b37fc221465@i100.no> (raw)

[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]

Hi

Regarding the new modules that have been added to dracut after v38, and 
the possible
systemd dependencies, I wonder a bit about this line in the Makefile of 
dracut in ipfire

https://github.com/ipfire/ipfire-2.x/blob/master/lfs/dracut#L79
rm -rf 
/usr/lib/dracut/modules.d/*{biosdevname,bootchart,dash,fips*,modsign,busybox,convertfs,network,ifcfg,url-lib,gensplash,cms,plymouth,btrfs,crypt*,dm,dmraid,dmsquash-live,livenet,lvm,multipath,qemu*,cifs,dasd*,fcoe*,iscsi,nbd,nfs,resume,ssh-client,zfcp*,systemd*,znet,securityfs,masterkey,selinux,usrmount,uefi-lib}

I am assuming that is removing dracut modules that one for certain do 
not need.
I guess some of the new modules introduced between v38 and v56(current) 
of dracut
should also be but on that "rm" list ?
I.e some new dracut modules depends on systemd, and some are for s390, 
for example.


I was playing a bit with grep'ing the module-setup.sh files of dracut, 
to find modules
that depends on systemd for example.
I.e. some way of finding the modules that "at least" should be put on 
the "rm" list.
I'm unsure if you have any semi automatic way of doing that, or are 
fully manually needing
to review the modules.

 From what I can see, dracut should fully support being used without 
systemd, since the modules
are signalling dependencies on systemd.
But modules that are only for s390 for example, needs to be detected 
manually I think.


The dracut.conf file also has the possibility to omit modules, by the
omit_dracutmodules variable, but that does not seem to be used currently 
by ipfire.

Regards
Alf

             reply	other threads:[~2022-03-05 22:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-05 22:13 alf [this message]
2022-03-05 23:12 ` alf
  -- strict thread matches above, loose matches on Subject: below --
2022-03-05  9:00 alf
2022-03-05  7:49 alf
2022-03-03 21:22 Peter Müller
2022-03-04 11:18 ` Michael Tremer

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=a995c5d5ab5e42b8a6060b37fc221465@i100.no \
    --to=alf@i100.no \
    --cc=development@lists.ipfire.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