I've already done that, and at the time the hook is executed i'm
printing the contents of /etc/passwd (inside the initrd) and it prints
the entries just fine.
Could it be the lack of dbus? Maybe it tries to gather more
information from the user other than /etc/passwd?
- Thijs
2016-12-23 17:14
On Fri, Dec 23, 2016 at 04:43:32PM +0100, Thijs Cramer wrote:
> In that case, is there any guide on what's required to get it working?
>
> My current scripting only adds the binary (and library dependancies)
> and adds the systemd-network and resolve users to /etc/passwd.
> When it starts it
Am 23.12.2016 um 16:43 schrieb Thijs Cramer:
In that case, is there any guide on what's required to get it working?
My current scripting only adds the binary (and library dependancies)
and adds the systemd-network and resolve users to /etc/passwd.
When it starts it says: "Cannot resolve user
My own hand made (bash) scripting. I'm trying to build an mkinitcpio
hook for systemd for ArchLinux.
Also dracut is not used in this case.
I've already found out that dracut supports systemd-networkd, and have
already copied some of the scripts they use.
- Thijs
2016-12-23 16:45 GMT+01:00
In that case, is there any guide on what's required to get it working?
My current scripting only adds the binary (and library dependancies)
and adds the systemd-network and resolve users to /etc/passwd.
When it starts it says: "Cannot resolve user name systemd-network: No
such file or directory".
On Fri, Dec 23, 2016 at 5:14 PM, Thijs Cramer
wrote:
> Hi all,
>
> Are there any plans to support systemd-networkd inside initrd?
>
It's already supported. (It's also what networkd was created for.)
--
Mantas Mikulėnas
Hi all,
Are there any plans to support systemd-networkd inside initrd?
Thanks in advance!
- Thijs
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hi ALL,
I was looking into Journal remote and It looks like journal remote will
only write the remote log which it receives to Journal file. Is there any
reason why journal remote is supporting other destination option like
syslog or console?. Can I submit a patch for syslog destination support?