<div dir="ltr">Re: The question regarding missing dependencies. <div> </div><div>You might try this:</div><div> </div>zcat /boot/initramfs-$(uname -r).img | grep -E "(depends|provides)" <div> </div><div>If you ran an update and dependencies were missing. Then </div><div> </div><div>update-initramfs -u </div><div> </div><div>wouldn't be of any help to you. </div><div> </div><div>I hadn't introduced myself. My background is in art and literature, I started working on the front end, and I started moving to the backend to troubleshoot problems with the web server. Learning NodeJs, Php and Bash, and I'm learning C++. In particular, I'm trying to get the Apache2 to serve. I have Ubuntu working on a Chromebook. </div><div> </div><div>Is it really that much more complicated to complete the boot process in chroot? I'll try the container solution. </div><div> </div><div>yours truly,</div><div>Benjamin Godfrey</div><div> </div></div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 26, 2023 at 5:00 AM <<a href="mailto:systemd-devel-request@lists.freedesktop.org" target="_blank">systemd-devel-request@lists.freedesktop.org</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send systemd-devel mailing list submissions to <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank">systemd-devel@lists.freedesktop.org</a> To subscribe or unsubscribe via the World Wide Web, visit <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a> or, via email, send a message with subject or body 'help' to <a href="mailto:systemd-devel-request@lists.freedesktop.org" target="_blank">systemd-devel-request@lists.freedesktop.org</a> You can reach the person managing the list at <a href="mailto:systemd-devel-owner@lists.freedesktop.org" target="_blank">systemd-devel-owner@lists.freedesktop.org</a> When replying, please edit your Subject line so it is more specific than "Re: Contents of systemd-devel digest..." Today's Topics: 1. Re: Failed to start up manager. Freezing execution. (Caeri Tech) 2. Completing the boot process for systemd inside the chroot (Benjamin Godfrey) 3. Re: Completing the boot process for systemd inside the chroot (Lennart Poettering) ---------------------------------------------------------------------- Message: 1 Date: Tue, 25 Apr 2023 09:18:35 -0400 From: Caeri Tech <<a href="mailto:caeritech@gmail.com" target="_blank">caeritech@gmail.com</a>> To: Lennart Poettering <<a href="mailto:lennart@poettering.net" target="_blank">lennart@poettering.net</a>> Cc: <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank">systemd-devel@lists.freedesktop.org</a> Subject: Re: [systemd-devel] Failed to start up manager. Freezing execution. Message-ID: <CAAuiGE=<a href="mailto:hGC%2Br3sYjkJBt7Vfin-s8B4kkUAsFhfCAGKmYdOYWbg@mail.gmail.com" target="_blank">hGC+r3sYjkJBt7Vfin-s8B4kkUAsFhfCAGKmYdOYWbg@mail.gmail.com</a>> Content-Type: text/plain; charset="utf-8" Interesting. If I downgrade systemd and systemd-libs from 253 to 252 it works as before. Is there perhaps a dependency that I'm now required to include in the initramfs config? On Tue., Apr. 25, 2023, 4:54 a.m. Lennart Poettering, < <a href="mailto:lennart@poettering.net" target="_blank">lennart@poettering.net</a>> wrote: > On Di, 25.04.23 01:43, Caeri Tech (<a href="mailto:caeritech@gmail.com" target="_blank">caeritech@gmail.com</a>) wrote: > > > *:: running cleanup hook [udev]* > > This ouput doesn't look as if systemd was actually involved? > > > But it still freezes execution. > > > > The rescue and emergency shells do not start if I activate the hook and > > again it freezes. The shells do start, however, when the hook is not > > activated. > > Anyway, without debug logs as suggested in my earlier mail this is > really hard to debug. Enable debug logging. > > Lennart > > -- > Lennart Poettering, Berlin > -------------- next part -------------- An HTML attachment was scrubbed... URL: <<a href="https://lists.freedesktop.org/archives/systemd-devel/attachments/20230425/9ba4216c/attachment-0001.htm" rel="noreferrer" target="_blank">https://lists.freedesktop.org/archives/systemd-devel/attachments/20230425/9ba4216c/attachment-0001.htm</a>> ------------------------------ Message: 2 Date: Tue, 25 Apr 2023 13:26:08 -0700 From: Benjamin Godfrey <<a href="mailto:mr.benjamingodfrey@gmail.com" target="_blank">mr.benjamingodfrey@gmail.com</a>> To: <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank">systemd-devel@lists.freedesktop.org</a> Subject: [systemd-devel] Completing the boot process for systemd inside the chroot Message-ID: <<a href="mailto:CAJxCLXpVJiCk9MbsjndjN_y0R9m8-4hAbW5XXK3fFXSUWF4TNQ@mail.gmail.com" target="_blank">CAJxCLXpVJiCk9MbsjndjN_y0R9m8-4hAbW5XXK3fFXSUWF4TNQ@mail.gmail.com</a>> Content-Type: text/plain; charset="utf-8" It seems I sent this to the wrong list. I hope this isn't off topic. Dear systemd mailing list, I am trying to finish the boot process for systemd inside the chroot. I have followed the instructions in the documentation, but I am still having some problems. The following is typical output: [...$ sudo systemctl start systemd-journald Running in chroot, ignoring request: start...] ### Showing that systemd is bailing out because of the chroot. [...$ ps --no-headers -o comm 1 init...] ### showing the Chromebook is using init at PID 1 [...$ file /sbin/init /sbin/init: symbolic link to /lib/systemd/systemd ...} ### showing that init and systemd are linked in the chroot. [...$ stat /sbin/init File: /sbin/init -> /lib/systemd/systemd ...] ### Showing that systemd is in use. {...$ ls /usr/lib/systemd } ### Shows the systemd files are loaded. [...$ systemctl is-active --quiet service System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down ...] *### Systemd not active in chroot* *I'm wondering if adding a line in the rc would help complete the boot process. * Can you please help me troubleshoot this issue? Thank you for your time. yours truly, Benjamin Godfrey -------------- next part -------------- An HTML attachment was scrubbed... URL: <<a href="https://lists.freedesktop.org/archives/systemd-devel/attachments/20230425/2dd09d88/attachment-0001.htm" rel="noreferrer" target="_blank">https://lists.freedesktop.org/archives/systemd-devel/attachments/20230425/2dd09d88/attachment-0001.htm</a>> ------------------------------ Message: 3 Date: Wed, 26 Apr 2023 10:33:44 +0200 From: Lennart Poettering <<a href="mailto:lennart@poettering.net" target="_blank">lennart@poettering.net</a>> To: Benjamin Godfrey <<a href="mailto:mr.benjamingodfrey@gmail.com" target="_blank">mr.benjamingodfrey@gmail.com</a>> Cc: <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank">systemd-devel@lists.freedesktop.org</a> Subject: Re: [systemd-devel] Completing the boot process for systemd inside the chroot Message-ID: <ZEjh6FduyO+JPRaf@gardel-login> Content-Type: text/plain; charset=us-ascii On Di, 25.04.23 13:26, Benjamin Godfrey (<a href="mailto:mr.benjamingodfrey@gmail.com" target="_blank">mr.benjamingodfrey@gmail.com</a>) wrote: > It seems I sent this to the wrong list. I hope this isn't off topic. > > Dear systemd mailing list, > > I am trying to finish the boot process for systemd inside the > chroot. systemd does not support booting in a classic chroot(). Use a container manager for that, for example "systemd-nspawn -D /some/directory -b" Lennart -- Lennart Poettering, Berlin ------------------------------ Subject: Digest Footer _______________________________________________ systemd-devel mailing list <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank">systemd-devel@lists.freedesktop.org</a> <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a> ------------------------------ End of systemd-devel Digest, Vol 156, Issue 26 ********************************************** </blockquote></div>