You are not logged in.
Pages: 1
Topic closed
Having switched to systemd I now feel I might eventually get to like it, but I still have questions of more and less importance which I have not found answers to in the manuals or the Wiki. Instead of each of us spawning a new thread about generic systemd conundrums, might it be an idea to have a dedicated systemd thread? Sticky or not, something like 'The ATI Bar and Grill'?
Last edited by whaler (2012-09-30 13:56:08)
Offline
My vote is for no just due to the random nature of epic threads. Eventually the signal-to-noise ratio becomes so small as on topic discussion gets diluted out by bullshit; it is better to open a specific thread with a very focused scope in my opinion.
EDIT: Also, these types of threads are horrible those browsing looking for a specific answer. To my SNR argument, spending time wading through pages and pages of nonsense to find an answer is no way to research systemd.
Last edited by graysky (2012-09-30 14:10:10)
Offline
I second that "no" on the some grounds that searching that would be a nightmare. Also, systemd is still such touchy subject for many, that it would probably be best not to give anyone a platform for under bridge behavior.
Offline
Also, systemd is still such touchy subject for many, that it would probably be best not to give anyone a platform for under bridge behavior.
Agreed. Given the latest statistics, a third of Archer currently use Gnome. Perhaps the 3.6 push and its systemd requirement will help ease the transition to systemd.
...or away from gnome!
Offline
I am now an i3 and dwb user, and it really makes me cringe to think that I spent a couple months trying to get myself used to gnome-shell when there are such great alternatives available.
Offline
I would also vote no, and continue to have separate threads for specific systemd problems, but I really wish people would use descriptive titles, rather than "systemd issue" "another systemd problem" and so on. In addition to attracting people who might actually be able to solve the problem, coming up with a descriptive title helps the person with the problem focus his attention on what the problem may actually be.
Offline
Having switched to systemd I now feel I might eventually get to like it, but I still have questions of more and less importance which I have not found answers to in the manuals or the Wiki.
Have you seen Lennart Poetterings article series, to this day in fifteen parts "systemd for Administrators" from his blog?
Last edited by Odaer (2012-09-30 16:59:42)
Offline
For the reasons enumerated above, and for others, this won't happen.
I'm closing this to prevent yet another meta-discussion about systemd devolving in to flamebait, anecdote and blog-length posts about trial and redemption.
Offline
Pages: 1
Topic closed