2012/9/28 Cristian Rodríguez
El 28/09/12 09:03, Andrea Turrini escribió:
2012/9/28 Cristian Rodríguez
: El 28/09/12 05:13, eddie escribió:
Is chkconfig now obselete?
Yes.
Just two questions: 1) Where is this documented? I have not seen it in the oS 12.2 release notes.
You can find a systemd chapter in the "current" documentation.
No reference to chkconfig (a "grep chkconfig /usr/share/doc/manual/opensuse-manuals_en/cha.systemd.html" returns nothing; a grep for chkconfig in /usr/share/doc/manual/opensuse-manuals_en/ matches only cha.apache2.html, cha.nfs.html, and cha.tuning.kexec.html). So, again, where is the fact "chkconfig is now obsolete" documented? This time please give me the file available on my disk I can install from oS dvd containing the paragraph talking about "chkconfig is now obsolete", not just a generic reference to the systemd documentation that does not even mention the word "chkconfig".
2) How can I enable a systemd service only in runlevel 3 and not in runlevel 5?
Runlevels exists as a compatibility "thin layer" on systemd, there are no native runlevels anymore.
can you give an example of a service you want to disable in runlevel 5 but have it working in runlevel 3 ? as well the rationale for such thing ?
This is exactly the answer I expected from you. I repeat the part of my mail you removed in your reply: On 09/28/2012 02:03 PM, Andrea Turrini wrote:
In particular, for the second question, please give a concrete answer to the question such as a list of commands to obtain the wanted result (list of commands that should be included in the release notes).
So, again, how can I concretely enable a service in runlevel 3 and not in runlevel 5 using systemd service files and terminal commands? I do not want to give you a concrete example and a rationale since as you (read: systemd supporters) say that systemd is a fully compatible replacement of sysV-init and that init files should be removed and replaced by service files, the proposed problem has to have a solution that works for every possible service you are or you are not aware of, as happens with init files. And possibly a solution that has the same complexity as using chkconfig or a couple of clicks in yast. Or do you want that I use only services approved by systemd or with a rationale acknowledged by systemd's supporters?
If I try by using "yast2 runlevel", expert mode,
Yast runlevel editor has not been updated to work with systemd yet.
And where is this now broken behavior documented in the release-notes/documentation of oS 12.2? According to the chapter of oS 12.2 documentation you referred, I expect that by using yast runlevel in expert mode I can change as *I want* and as the interface allows me the services in each runlevel, as it worked for a long time. Best, Andrea -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org