Hello, Am Dienstag, 2. April 2013 schrieb Cristian Rodríguez:
El 02/04/13 16:09, Christian Boltz escribió:
Nice[tm]. What's the reason for this? (I assume "let's break some initscripts from stone age" was not the reason - I seriously hope Lennart is not evil enough for that ;-)
Early boot scripts were a distribution specific extension of sysvinit, hence everybody does it differently.
To be more specific than Frederic, systemd no longer includes any distribution-specific code, all distributions targets (in our case TARGET_SUSE) are gone.
That still sums up to "let's break some initscripts from stone age". Seems like I have to add "on multiple distributions, so that everybody gets hurt". Again: Is there a (technical) reason to remove the distro-specific code? I start to think Lennart reads too many BOfH stories... :-(
At the moment you'll break lots of packages and, more important, break lots of basic features like RAID and LVM.
RAID and LVM already have systemd support upstream, to make it work, last time I checked it required dracut.
... and dracut is not working on openSUSE yet if I understan the other mails correctly. In other words: At the moment, RAID and LVM will _not_ work without the boot.* initscripts.
=== boot.loadmodules ===
Already sent a patch to replace it.
http://lists.opensuse.org/opensuse-kernel/2013-03/msg00016.html
Not merged yet :-( another reason to use dracut.
Reading the mails in opensuse-kernel, the migration will depend on the mkinitrd package. If we switch to dracut, you should also add it to another package that is actually installed ;-) (for example dracut or kernel-*)
=== boot.local === Package: file /etc/init.d/boot.local is not owned by any package # but should continue to work ;-) Could replace that by a generator, or just call it "local.service".. ;)
As long as it works, I don't really care about the method ;-) BTW: There might be more boot.* initscripts - my mail only listed those installed on my system. ARCHIVES.gz will probably give you a longer list. [...]
Note that I didn't write anything about "remove the initscript" - for AppArmor, I'd like to keep it for backwards compability with older openSUSE releases. Other maintainers might or might not have similar wishes.
BTW: is ExecStatus supported in the meantime?
selinux and smack LSMs have native support merged in systemd (by the authors, Redhat and people from Intel respectively) kinda telling that apparmor doesn't...:-|
You most probably know that most of the AppArmor development is done by Ubuntu developers nowadays. [1] Yes, that's the distribution with upstart. Not too surprising that they don't care about systemd, right? That said: writing an apparmor.service file shouldn't be too hard, but at the moment I don't really have time to do it. BTW: do the RPM macros for migration to *.service also work with boot.* initscripts? I had a look at /usr/sbin/systemd-sysv-convert, and I somehow doubt. It seems to check /etc/rc.d/rc*.d/ only, but not /etc/rc.d/boot.d/... Talking about /usr/sbin/systemd-sysv-convert - even --help is buggy: cat << EOF Save and Restore SusV Service Runlevel Information ^ ;-) Regards, Christian Boltz [1] I'm also doing some work upstream, but that's mostly updating profiles and sometimes fixing some scripts. I also take part in discussions about future development, but you don't want me to write C code ;-) [2] [2] if I ever write or edit C code, I strongly recommend to confine it with AppArmor *g* -- what does "> /dev/null" mean? and how do i reverse it? would "< /dev/null" be right? [aus comp.unix.shell] -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org