Re: [systemd-devel] Failed to mount early API filesystems, freezing execution

2018-10-30 Thread Jan Claeys
On Tue, 2018-10-30 at 16:14 +0100, Esben Stien wrote: > > Either way I think it would be best to ping your downstream distro > > about this. > > They don't have proper channels. I've written to the web forum, but > there's no reply. You got a reply there, although not the one you wanted. You co

Re: [systemd-devel] Mailing List List-Id Header

2018-10-30 Thread Reindl Harald
Am 30.10.18 um 16:17 schrieb Esben Stien: > Is there supposed to be a List-Id in the headers of email that comes from > this mailing list? > > I don't see any. Any other headers you use? List-Id: systemd Development Mailing List mostly you looked at one the famous "reply-all" instead "reply-l

Re: [systemd-devel] Failed to mount early API filesystems, freezing execution

2018-10-30 Thread Lennart Poettering
On Di, 30.10.18 16:14, Esben Stien (b...@esben-stien.name) wrote: > On 30.10.2018 15:17, Lennart Poettering wrote: > > > This suggests that the root partition you are trying to boot doesn't > > have properly set up /sys, /proc or /dev directories that we could > > mount stuff too, or your intird

Re: [systemd-devel] Mailing List List-Id Header

2018-10-30 Thread Paul Menzel
Dear Esben, On 10/30/18 16:17, Esben Stien wrote: > Is there supposed to be a List-Id in the headers of email that comes from > this mailing list? > > I don't see any. Any other headers you use? I see all the headers. For example, from your message (Ctrl + u in Thunderbird): ``` X-Mailman-Vers

[systemd-devel] Mailing List List-Id Header

2018-10-30 Thread Esben Stien
Is there supposed to be a List-Id in the headers of email that comes from this mailing list? I don't see any. Any other headers you use? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/s

Re: [systemd-devel] Failed to mount early API filesystems, freezing execution

2018-10-30 Thread Esben Stien
On 30.10.2018 15:17, Lennart Poettering wrote: This suggests that the root partition you are trying to boot doesn't have properly set up /sys, /proc or /dev directories that we could mount stuff too, or your intird set things up weirdly. Right, but why is it freezing, as opposed to giving me s

Re: [systemd-devel] Failed to mount early API filesystems, freezing execution

2018-10-30 Thread Lennart Poettering
On Di, 30.10.18 14:58, Esben Stien (b...@esben-stien.name) wrote: > > > I have an old Ubuntu 16.04 that I upgraded and during the upgrade, it had a > power failure. > > Now I only see this when I boot: > > failed to determine whether /sys is mount point > failed to mount early api filesystems,

[systemd-devel] Failed to mount early API filesystems, freezing execution

2018-10-30 Thread Esben Stien
I have an old Ubuntu 16.04 that I upgraded and during the upgrade, it had a power failure. Now I only see this when I boot: failed to determine whether /sys is mount point failed to mount early api filesystems, freezing execution Here's a photo of the screen: https://imgur.com/a/uPH7HTd I

Re: [systemd-devel] Launch at tty7

2018-10-30 Thread Lennart Poettering
On Di, 30.10.18 11:34, deepan muthusamy (deepan.m2...@gmail.com) wrote: > I have one doubt that, if I launch app1 under tty1 andapp2 at tty7. If I > add after dependency in app2 for app1( After=app1.service in app2.service). > will this dependency work? Why wouldn't it? > How to launch an applic