Originally posted by cjcox
View Post
Announcement
Collapse
No announcement yet.
Systemd Continued Commanding Linux Systems In 2015
Collapse
X
-
Originally posted by SystemCrasher View PostLogs to computers are what flight recorders to aircraft. Logs are not meant to be edited. If event takes place and logged, it is logged. Editing it is wrong and only gives room to h4x0rz to hide traces of break-in. Generations of h4x0rz were learning to clean up logs. Let's make it a bit less convenient...
@Nille_kungen: this is a technical forum. If someone publicly states technically inaccurate criticism of the other peoples work, he should expect be called out for that.
- Likes 2
Comment
-
Originally posted by pal666 View Postimbeciles do not see themselves as imbeciles, who would've thought
People that doesn't like systemd mustn't be stupid nor incompetent.
I can't understand why this hate against people that doesn't like systemd.
Comment
-
Originally posted by Candy View PostCalling people imbeciles and uneducated clearly shows your social soft skills.
Comment
-
Originally posted by SystemCrasher View PostAnd somehow, I'm yet to see any reasonable objections against systemd. So far I've seen shitload of personal preferences and ignorance.
Comment
-
Originally posted by pal666 View Postyou broke your system with you crooked hands, it is not systemd's fault. on the other hand pre-systemd systems _always_ hang during shutdown on non-trivial setups
Comment
-
Originally posted by Candy View Post... or you could simply use your favourite editor and load the logs ... just because something is new, doesn't make it worth while ... my complaints about journald isn't just because it's hard to use (for me it is), but also because of the huge binary blobs it's creating. Simply accept the fact that there are things in a persons life, that the person refuses to adopt or learn. As for distros adopting systemd. I read that lines (above) with an sarcastic smily in my face. Been following too many political conversations on several mailing lists and the way udev has been dealt with inside systemd. Over long or short every competitor software has gotten it's feet cut by this. But please don't get me started here.
i really don't give a fuck about political reasons you mention, FOSS is always about choice. if you don't like something, use/create something else and then you end up on one of two points of the stick. you either make good stuff (or better then previous alternatives) and people adopt it or your work gets lost and forgotten. problem with second is that people instead of being self critical, they resort to complaining. if you look at systemd, you can clearly see which end of the stick it got and if you look how interest in other init systems is vanishing same thing is obvious. i personally would never go back to upstart or god forbid sysv.
then there is also another POV when one project is successful enough, can other contributors keep up and does extra work needed to support them even pay off? project with too many directions is just as flawed as project with too few contributors.
same thing about cutting off directions happened to gtk. and if i look at it now, it was for god damn better. although, to be truthful they had a major fuckup on how they conveyed that fact. if they didn't suck at communications as they do, whole thing would face off much less resistance.
... but, why in the world you ever go as ineffective as loading log in text editor? the only thing i could imagine being even more ineffective is probably someone loading those logs in libreoffice, printing them to pdf and then inspecting in adobe acrobat
- Likes 1
Comment
Comment