[arch-projects] [mkinitcpio] [RFC] initrd: systemd-{networkd, resolved}

Timofey Titovets nefelim4ag at gmail.com
Tue Aug 26 18:28:26 EDT 2014

I resend mail from systemd-devel, because i think it make sense in 
mkinitcpio, i think it can be added by systemd hook. I can try write a 
patch, but before, i want to know opinions of arch developers.

---------- Forwarded message ----------
From: Lennart Poettering <lennart at poettering.net>
Date: 2014-08-26 3:57 GMT+03:00
Subject: Re: [systemd-devel] [RFC] initrd: systemd-{networkd,resolved}
To: Timofey Titovets <nefelim4ag at gmail.com>
Копия: systemd-devel at lists.freedesktop.org

On Sat, 23.08.14 23:26, Timofey Titovets (nefelim4ag at gmail.com) wrote:

> Good time of day list, i just want to hear your opinions - pro and con
> Pre story:
> Before i install bunch of systemd-{networkd,resolved} and
> wpa_supplicant (for connecting to HotSpots)
> After i spend some time to think about network handling by networkd
> and resolved, about some cases and i have idea, what if try to
> implement early network connection in initrd?
> Pro:
> spherical cow - If mount rootfs fail to boot, or mount, we have
> network access to restore system.
> If system headless we can get remote access as case above and i think it cool.
> It useful for nfs mount.
> Yes, this implies what we use systemd, as init in boot process.
> What i miss? This is good idea or i must burn him in hell.

One of the reasons systemd-networkd exists is to make it useful for
running in the initrd, so that we can boot from networked volumes.  It
should actually pretty much work already, even though it cannot
deserialize its state after the initrd transition.


Lennart Poettering, Red Hat

Have a nice day,

More information about the arch-projects mailing list