[arch-releng] [RFC][PATCH] [configs/releng] Use systemd-networkd instead of dhcpcd

[Gerardo Exequiel Pozzi]

On 02/26/2014 04:22 AM, Thomas Bächler wrote:
> Am 26.02.2014 03:04, schrieb Gerardo Exequiel Pozzi:
>> The issue here is when booting via PXE... The initcpio hook, writes on
>> (append) etc/resolv.conf. Now, I think that I need to hack, and write to
>> /run/systemd/network/resolv.conf instead.
>>
>> * Under PXE scenario: systemd-networkd will not be used because
>> interface rename will fail (already UP from initramfs as eth) then
>> /run/systemd/network/resolv.conf is untouched from systemd-network.
>>
>> * Under non-PXE scenario: /run/systemd/network/resolv.conf will be
>> touched only by systemd-network.
>>
>> Also I think that can be a good idea for PXE scenario if-down-eth0, on
>> initramfs as last step, then in this case, rename does work and dhcpcd
>> is requested again but from systemd-networkd on real-root-fs.
> 
> Why don't we just copy all renaming and networkd-related stuff to
> initramfs and use it for initialization there, too?

Will be great, sure. But how to extract ROOTSERVER for later usage?
> 
> For that we'd probably have to switch initramfs to systemd entirely, but
> we should do that anyway.

Hehe. I tried this some times, but I fail. At least doing in a only
systemd-way (only using units, no shell scripts), for the most simple
boot scenario used by default and with fixed values.


> 
> 


-- 
Gerardo Exequiel Pozzi
\cos^2\alpha + \sin^2\alpha = 1

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 555 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/arch-releng/attachments/20140226/589bea2c/attachment.asc>