Mailinglist Archive: opensuse-factory (551 mails)
| < Previous | Next > |
Re: [opensuse-factory] Systemd by default
- From: Kay Sievers <kay.sievers@xxxxxxx>
- Date: Sun, 29 May 2011 14:53:15 +0200
- Message-id: <1306673597.1337.18.camel@zag>
On Sun, 2011-05-29 at 13:40 +0200, Bruno Friedmann wrote:
Systemd only supports encrypted LUKS volumes out-of-the-box.
I personally never used LVM. The SUSE init scripts might need
integration to work properly with systemd. I can't really tell what's
needed here. I know Fedora needed some hacks to their init
scripts/service files to make stacked LVM/crypto configs work.
That should work already. We should cleanup all DM devices.
That sounds weird. I've never seen that. Maybe it's some init script
going crazy. If you use a recent systemd version and can provide some
output, please open a bug.
Yeah, many things need integration still.
It's a lot of work ahead. We really need to dedicate resources to it,
means people working full time on it, otherwise it would leave too many
things in unknown state. Also people finally need to make hard
decisions, I fear, otherwise we will run into a test matrix of
alternative options to support, which we can not really handle.
It works fine for me, but I use only a very tiny subset of the tings
that need to work in the distro. LVM, nfs, iscsi, unlocking of encrypted
SSL certificates, openvpn server, ..., all the 'non-laptop things' I
never used with systemd.
Some things are mentioned here, I need to update it the next days to
reflect the current state:
http://en.opensuse.org/openSUSE:Systemd_status
Kay
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
On 05/29/2011 09:55 AM, Tim wrote:
to my knowledge systemd supposed to be the default init daemon in 12.1.
Doesn't it make sense to activate it now (or as early as possible) to
get at least some feedback from the people running factory?
Tim I'm also in favor of that, but before becoming the default
systemd has to support fully lvm and encrypted volume group
Systemd only supports encrypted LUKS volumes out-of-the-box.
I personally never used LVM. The SUSE init scripts might need
integration to work properly with systemd. I can't really tell what's
needed here. I know Fedora needed some hacks to their init
scripts/service files to make stacked LVM/crypto configs work.
(particulary in shutdown process)
That should work already. We should cleanup all DM devices.
Having fsck forced at each reboot is a pain.
That sounds weird. I've never seen that. Maybe it's some init script
going crazy. If you use a recent systemd version and can provide some
output, please open a bug.
Then make sure yast systemlevel can work with systemd if it is present.
Yeah, many things need integration still.
I think Kay can comment on what is the actual status of
integration, and the specific help he needs
It's a lot of work ahead. We really need to dedicate resources to it,
means people working full time on it, otherwise it would leave too many
things in unknown state. Also people finally need to make hard
decisions, I fear, otherwise we will run into a test matrix of
alternative options to support, which we can not really handle.
It works fine for me, but I use only a very tiny subset of the tings
that need to work in the distro. LVM, nfs, iscsi, unlocking of encrypted
SSL certificates, openvpn server, ..., all the 'non-laptop things' I
never used with systemd.
Some things are mentioned here, I need to update it the next days to
reflect the current state:
http://en.opensuse.org/openSUSE:Systemd_status
Kay
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |