Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Should I stop using init s, boot -s, and my other standard procedures to change runlevels and perform standard system maintenance?

0
Posted

Should I stop using init s, boot -s, and my other standard procedures to change runlevels and perform standard system maintenance?

0

Emphatically, no! Your old favorite commands continue to work as they always have. There’s no need to change procedures. There’s no reason to retrain your fingers with a much longer-to-type command when init s works just fine. The init invocations will work just like they always have, where svcadm milestone won’t. For example, running svcadm milestone svc:/milestone/single-user:default won’t change the run-level of the system (as described by who -r). Running init s will. This is kool, more more more tips guys! Lots of new folks, lets help them all out with all the tips we can cough up.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123