if you read the article, the ban on these words is not a "DEP policy" but "But four former DEP employees from offices around the state say the order was well known and distributed verbally statewide.". Makes it look like someone has an agenda
Climate Change IS NOT political, its verifiable fact. The political bit of it is spoken by politicians, bloggers, fossil fuel proponents etc who have no climate science training or expertise i.e. those that make up stuff to suit their personal/political opinion that is not backed up by verifiable facts. Scientists get dragged onto TV panels/interviews etc to dispel the nonsense of non-scientific personal/political opinions (and is not the scientists being political)
Possibly linked to the utilities opposition to solar in Florida seeing how the fossil industry seems to be linked very closely to the politicians- here's a comment from them "The utilities have said that solar is not as effective in Florida because the state’s cloud cover makes solar panels inefficient." http://www.tampabay.com/news/b...
"Really, really stupid idea, taking the heat away for a tiny bit of thermoelectric power." - well, this will then be a chance for Firestone to make that point if its truely a stupid idea, could be a PR win for Firestone (or some other tyre manufacturer)
the first tech preview was very flakey, the Vivaldi_TP2_1.0.94.2.x86_64.rpm is a lot better and more stable, just downloading the 3rd one now vivaldi-preview-1.0.118.19-1.x86_64.rpm
" Obviously nobody with the least bit of clue would expect logs to be cleanly written on failing disks, hence this is not even a subject for discussion" exactly so if rsyslog logs are corrupted its expected but if journald logs are corrupted, its the fault of systemd, great logic
" Failing disks or filesystems are detected rightfully by the kernel, nothing else has any business doing so" so what else does?
""Different from systemd "logging", rsyslog will not make the log problem worse by using a binary format " - it doesn;t make any difference what format the logs are written in, if the location of the log file data is trashed, then its totally or partially unreadable in any format.
" and for remote logging will transfer the messages off-site." and if the system fails before rsyslog is actually running or the network is not yet loaded? rsyslog is loaded quite late in the boot process as opposed to journald
the only dependencies are systemd, journald and udev. all others are configurable for use. if a developer makes changes to his/her app to depend on systemd in any way, its their development choice and their efforts.
well as you seem so negative about systemd. why not create and publish a report comparing all the features of systemd and various other init systems as you see them and what your solution is to counter all the systemd features and stand up and present it to Red Hat et al and make your case? Get some of the anti-systemd supporters to help. so far all i've seen from the anti's is personal opinions of systemd and personal attacks on the developers, nothing really technically decisive only misinformed comments touted as "information"
"The carrot is making things as easy as possible for the people who write init scripts in distros" - nothing wrong with that.
"The stick are the emotional posts that the author spreads throughout the internet " - can you link to those, all i've seen is him answer the stupid trolls misinformed understanding of how systemd works? i can't see pointing out the obvious as a "stick", must make the rest of the distro decision makers a bunch of wimps.
"It is also my understanding that SystemD is taking the approach of wrapping up quite a number of those software pieces into one tool/process." - wrong, all the other processes are optional. Unfortunately the collective software project is also called "systemd" so people get confused that when other processes are mentioned and think that the systemd executable does it all.
"No, it's crashy bug-riddled garbage that hasn't finished alpha testing, but is being pushed out as a defacto standard to replace things that actually work. THAT is why the community is so divided over it." you obviously don't know what you are talking about apart from propagating shit
its not thrown away, its still there is you want it. if you can't manage it yourself, move to Slackware or Gentoo, thats the beauty of the linux ecosystem.
if a disk is corrupting sectors where the logs (or anything) are being written, nothing will stop the corruption, not even syslog or rsyslog. "systemd apparently does not even try to." -eh?
Slashdot Mirror
Genetics? more like skin color or language or location or a combination of all three, how many white races are there?
if you read the article, the ban on these words is not a "DEP policy" but "But four former DEP employees from offices around the state say the order was well known and distributed verbally statewide.". Makes it look like someone has an agenda
Climate Change IS NOT political, its verifiable fact. The political bit of it is spoken by politicians, bloggers, fossil fuel proponents etc who have no climate science training or expertise i.e. those that make up stuff to suit their personal/political opinion that is not backed up by verifiable facts. Scientists get dragged onto TV panels/interviews etc to dispel the nonsense of non-scientific personal/political opinions (and is not the scientists being political)
stating verifiable facts is not politics, its more anti-politics as it undermines the politicians fabrications
Possibly linked to the utilities opposition to solar in Florida seeing how the fossil industry seems to be linked very closely to the politicians- here's a comment from them "The utilities have said that solar is not as effective in Florida because the state’s cloud cover makes solar panels inefficient." http://www.tampabay.com/news/b...
true but electric cars don't have an ICE
"Really, really stupid idea, taking the heat away for a tiny bit of thermoelectric power." - well, this will then be a chance for Firestone to make that point if its truely a stupid idea, could be a PR win for Firestone (or some other tyre manufacturer)
the first tech preview was very flakey, the Vivaldi_TP2_1.0.94.2.x86_64.rpm is a lot better and more stable, just downloading the 3rd one now vivaldi-preview-1.0.118.19-1.x86_64.rpm
" Obviously nobody with the least bit of clue would expect logs to be cleanly written on failing disks, hence this is not even a subject for discussion" exactly so if rsyslog logs are corrupted its expected but if journald logs are corrupted, its the fault of systemd, great logic
" Failing disks or filesystems are detected rightfully by the kernel, nothing else has any business doing so" so what else does?
""Different from systemd "logging", rsyslog will not make the log problem worse by using a binary format " - it doesn;t make any difference what format the logs are written in, if the location of the log file data is trashed, then its totally or partially unreadable in any format.
" and for remote logging will transfer the messages off-site." and if the system fails before rsyslog is actually running or the network is not yet loaded? rsyslog is loaded quite late in the boot process as opposed to journald
"Systemd causes log corruption where sane alternatives do not have such issues." - just why do you propagate this shit?
the only dependencies are systemd, journald and udev. all others are configurable for use. if a developer makes changes to his/her app to depend on systemd in any way, its their development choice and their efforts.
anti-systemd attacks have no merit, they are just a list of vitriolic personal attacks on the developers and lies about what systemd does or can do.
If systemd had no merit, it would not be adopted by so many distros
well as you seem so negative about systemd. why not create and publish a report comparing all the features of systemd and various other init systems as you see them and what your solution is to counter all the systemd features and stand up and present it to Red Hat et al and make your case? Get some of the anti-systemd supporters to help. so far all i've seen from the anti's is personal opinions of systemd and personal attacks on the developers, nothing really technically decisive only misinformed comments touted as "information"
i can also make up stuff thats not supported by evidence
i can google and i do in order to sort out the shit posted about systemd. if you really had information, you'd have posted it
ok, if you've lost your sense of humour try this instead http://www.skeptic.com/reading...
"The carrot is making things as easy as possible for the people who write init scripts in distros" - nothing wrong with that.
"The stick are the emotional posts that the author spreads throughout the internet " - can you link to those, all i've seen is him answer the stupid trolls misinformed understanding of how systemd works? i can't see pointing out the obvious as a "stick", must make the rest of the distro decision makers a bunch of wimps.
You are blaming the wrong person, if something like Gimp decided to interface with systemd, its the Gimp developers.
"All subprocesses running as root " - bollox, do some research instead of spreading crap
"It is also my understanding that SystemD is taking the approach of wrapping up quite a number of those software pieces into one tool/process." - wrong, all the other processes are optional. Unfortunately the collective software project is also called "systemd" so people get confused that when other processes are mentioned and think that the systemd executable does it all.
"No, it's crashy bug-riddled garbage that hasn't finished alpha testing, but is being pushed out as a defacto standard to replace things that actually work. THAT is why the community is so divided over it." you obviously don't know what you are talking about apart from propagating shit
its not thrown away, its still there is you want it. if you can't manage it yourself, move to Slackware or Gentoo, thats the beauty of the linux ecosystem.
why not go back to life before "init" if you are against progress?
want to link to them so we can see their reasons?
if a disk is corrupting sectors where the logs (or anything) are being written, nothing will stop the corruption, not even syslog or rsyslog. "systemd apparently does not even try to." -eh?