Well, as long as you use a feature that is absent from another kernel, it will not work on that other kernel. A fallback can be implemented when the feature is a detail. In the case of systemd's pid 1, the cgroups are central to the design (so that daemons cannot escape management, not even by double-forking). The real solution for other operating systems that want systemd is to have their kernel catch up with Linux. As far as I understood, GNU Hurd's developer are actually considering the implementation of a cgroups-like feature so that systemd could work on top of it.
I'm not against using features that aren't available on other *nix systems in
general, just against unportable system components that can become
dependencies of programs.
- Re: [Trisquel-users] Could systemd be an inconvenient on p... marioxcc . MT
- Re: [Trisquel-users] Could systemd be an inconvenient... danigaritarojas
- Re: [Trisquel-users] Could systemd be an inconven... marioxcc . MT
- Re: [Trisquel-users] Could systemd be an inconvenient on p... csh
- [Trisquel-users] Re : Could systemd be an inconvenient on ... lcerf
- Re: [Trisquel-users] Could systemd be an inconvenient... danigaritarojas
- [Trisquel-users] Re : Could systemd be an inconve... lcerf
- Re: [Trisquel-users] Could systemd be an inconven... danigaritarojas
- [Trisquel-users] Re : Could systemd be an inc... lcerf
- Re: [Trisquel-users] Could systemd be an ... danigaritarojas
- Re: [Trisquel-users] Could systemd be an inconvenient on p... taiji_tao
- Re: [Trisquel-users] Could systemd be an inconvenient on p... taiji_tao
