2013. június 11. 20:35 napon Cristian Rodríguez <crrodriguez@opensuse.org> írta:
Linda is once again talking non-sense and driving to conclusions based on that non-sense.
All that she made is a big argument from ignorance, "I do not know how things work,therefore.."
Same thing on kernel,
What ? if the kernel fails to do something it is not a systemd problem!
Amazingly enough, I have heard knowledgeable people making this argument too "systemd is a problem because it makes the kernel crash".. oh well..*facepalm*
Christian, I don't understand your argument. Linda says that: QUOTE: I mean I go into level 'S;, and I can go to the boot.d directory and run the scripts by hand, or semi-automated: (in boot.d or rcX.d): for i in S*;do ./"$i" start & read -p "next? [y]/n" -t 4 -n 1 ans [[ $ans == n ]] && break done --- can pause it at any time, or lean on CR to go full bore... As soon as a script fails I can redo it with bash -x SCRIPT... and see exactly what failed. QUOTE END The first question is if this is really doable with sysV. She also says that this type or equivalent booting/debugging is not available with systemd. The second question is if this is true. Which statement of Linda is not true? I am really curious since I never did booting like this in sysV. And I don't know systemd. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org