Hi,
I didn't turn anything off in journald.conf, it is all the default
settings. I do get every boot log just fine for example within
emergency.target, also tried with multi-user.target just for the sake of
trying. I could pastebin them somewhere or at least try to if you want
to have a look,
On Mo, 29.04.19 11:06, Ellis ([email protected]) wrote:
> Hi,
> after some manual testing on my end, I can confirm two things:
>
> 1. systemd really takes care of /run as it should
> and 2. I still have no log prior to 'received sigterm from PID 1' when the
> real root is booted up.
>
> I intentio
Hi,
after some manual testing on my end, I can confirm two things:
1. systemd really takes care of /run as it should
and 2. I still have no log prior to 'received sigterm from PID 1' when
the real root is booted up.
I intentionally messed up my kernel cmdline giving it a wrong rootfs
partitio
On Mo, 29.04.19 07:12, Ellis ([email protected]) wrote:
> Hi,
> thank you once again. I guess I will have to find how to keep this directory
> as a whole as you said. Maybe I expected systemd to realize this on its own
> somehow, and it doesn't. Should a fstab entry be enough ? I'm guessing
> not.
On So, 28.04.19 13:42, Ellis ([email protected]) wrote:
> Hi,
> subject pretty much says it all. I am currently working on an embeded system
> and wish to use systemd in both the rootfs and the initramfs. These are both
> built via buildroot, making a full rootfs for one and a minimal rootfs for
>
Hi,
subject pretty much says it all. I am currently working on an embeded
system and wish to use systemd in both the rootfs and the initramfs.
These are both built via buildroot, making a full rootfs for one and a
minimal rootfs for the other. However the documentation on how to make a
proper
