Cristian RodrC-guez wrote:
No, it is not just kernel modules.. in current incarnations with systemd/dracut the initrd is also used for clean shutdown, not just for system startup.
dracut wouldn't be needed for an initrd that has only kernel modules would it? What's on initrd that systemd would need that isn't on the hard disk?
Er... wait a sec, you mean initrd isn't deallocated after boot? ?
Do you mean to say that the large initrd's that people are complaining about stay around in memory AFTER boot just so systemd can use it to shut down? I fully agree that small initrds are desirable and I would also prefer if it does not contain parts which are not really needed. But on the other hand for "modern PCs" I would think it is not really an issue. Even if the initrd is kept during the uptime, in case the memory would be needed it would be paged out, I assume without noticable impact on
On Fri, 28 Jun 2013 01:35:10 -0700 Linda Walsh wrote: the performance.
If the systemd project recommends getting rid of initd for efficiency & speed, I'm sure it wouldn't be too difficult for us to do so. In my understanding there are significantly different use cases, especially small/mobile/embedded devices vs. "PCs". For the first it is known quite precisely in advance which HW can be included and therefore it is "easier" to build a monolythic kernel - and my interpretation of the systemd configuration without initrd aims at these.
For the latter there is a huge range of possible configurations, and therefore it is "reasonable" to use the initrd. Kind regards, Dieter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org