Re: systemd landed
- From: Colin Walters <walters verbum org>
- To: Giovanni Campagna <scampa giovanni gmail com>
- Cc: ostree-list gnome org
- Subject: Re: systemd landed
- Date: Thu, 13 Sep 2012 20:09:53 -0400
On Fri, 2012-09-14 at 00:50 +0200, Giovanni Campagna wrote:
> I tested this, but did not go very far.
> First of all, I had my /etc/fstab from the distro copied to /etc for
> /home and /boot, but systemd doesn't like remounting / on ostree, so
> it would jump to emergency mode straight away.
Yeah, systemd vs the ostree mount setup is a tricky integration issue.
It needs a good amount of thought as to how things should work.
At the moment, systemd also fails to remount / read-only at reboot time.
> To make things extra
> fun, -.mount is before systemd-journald.service, so nothing was logged
> (syslogd has no .service file, so it's not even started),
Right =/ I had a similar thing where I was trying to debug why
something was failing, but it turns out "journalctl" just outputs
nothing at all if you didn't build with XZ. Painful.
Anyways I was thinking we might as well go journal-only, but I don't
have a strong opinion.
> and
> emergency.service would just loop because there is no /sbin/sushell.
> In Fedora /sbin/sushell is provided by initscripts, so maybe we still
> need a gnome-initscripts module?
It looks like there should be a fallback though.
Hmm.... booting with systemd.unit=emergency.target does nothing, but
booting with systemd.unit=multi-user.target works? I'll debug this
later.
> Once passed that, I reached a black gdm screen.
https://bugzilla.gnome.org/show_bug.cgi?id=630485
Basically we need to make /var/lib/gdm. It used to be done in the
ginitscripts hack.
> This actually brings a more general problem: where do we report
> "integration" problems for ostree, such as missing packages or
> dependency issues? Is it right to reuse the ostree product?
Seems fine to me. I expect the two things to co-evolve.
> Should we ship a preset file, and have a trigger that does "systemctl preset"?
> It depends on the ability to do systemctl outside of systemd, though.
This is already fixed by:
http://git.gnome.org/browse/gnome-ostree/commit/?id=94cc016c2b81b7d2eadce64fa24f46c2ab359568
> Maybe it's time to enable gnome-initial-setup, so that we can actually test it?
Yeah, that'd be a good idea.
> If one wants, he can still setup the uid and home directory to share
> with the host system. Btw, I believe on the majority of Fedora
> installations out there it doesn't work out of the box because /home
> is on a separate partition which is not mounted automatically at
> startup.
Maybe this is something "ostree admin" should do? When you're doing a
deployment for the first time from a running system, copy things over
from the host?
Or it could be an ostree admin clone-host-config command or something.
This hasn't affected me since I think the Fedora default partitioning
scheme is total crack, and I use one big /. But we should clearly
figure out how to accomodate the Fedora defaults.
> systemd-tmpfiles?
Well, in this case it isn't a temporary directory. I think it should be
valid for the administrator to configure GDM defaults there.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]