Does synchronisation use rsync or is it a from-scratch implementation?
Not sure, but I don't think so. It works a little different from simple folder syncronisation tools.
First it compares the two folders and then display display the differences using kdiff (or similarities, depending on the filters). There are various ways and options for filtering this, but when satisfied, one use the filtered output to synchronise the folders.
So it gives one a very good overview of what is going to be synchronized, and what exactly you want to synchronise at all. So folder synchronisation for the control freak.
Different strokes.... I think KDE has a brilliant UI that supports my workflow wonderfully. I find it much better than Mac OSX and MS Windows in almost every aspect. Haven't used Gnome since the early 2.0 days, but I never liked how it worked or how it looked, and I found KDE programs superior for my use: K3b, Krusader, Kmail, Amarok, Kontakt, Digikam, Gwenview, KTorrent, Konsole are IMHO superior what else I have seen on Linux.
Never had KDE Plasma crash on me, even with extreme loads.
Krusader is a KDE favourite of mine. Very underrated. It is twin panel, tabbed file-manager, with masking filters (e.g. select only "*.otd" files), the ability to unpack archives, and has superb "synchronise folders" feature. It's mass rename feature is very good too.
I look forward to the GPG backend to Kwallet. I was never quite sure how safe the encryptet wallet was, but with GnuPG I know what I get.
Ctrl-Click to launch URL's directly from Konsole looks nice too. It is a "right mousebutton" context menu at the moment, but clicking underlined URL's just seems right.
Great for "journalctl" with the "-x" switch that enables the catalogue db's, so that error messages in the log file are displayed together with full explanations and URL's pointing to support and documentation etc.
I have no problem with people having different preferences. In fact my main problem with systemd haters are exactly that they continually slander open source developers like Poettering just for making a init system that they evidently doesn't use or have any real knowledge about.
Content free statements like "Unix philosophy means..." doesn't convince either. grep, sed, cp, diff etc. are all useful tools, but I have absolutely no problem with Linux users that doesn't know anything about them, but just uses a GUI like Gnome for everything.
Make it easy for people to use Linux I say, and with systemd it will actually become feasible to write a proper GUI program for showing log files that can do sorting and filtering and what not, due to the fact that the journal is structured. Not only that, it will function across all systemd distros without a tons of distro specific code.
> since it is systemd based and therefore shows the direction that most Linux distribution are heading
We would be happy if you'd stop spreading such unproven bs!
Red Hat, Fedora, CentOS, SUSE, OpenSUSE, Arch Linux, Mageia, Sabayon Linux all enables systemd as default. There are probably many more, and certainly many more to come in the future. Besides that, distros like Gentoo and Debian have systemd as an option. Hey, even a slacker is working on systemd support on Slackware.
All desktop environments like Gnome, KDE, LXDE are integrating systemd like crazy because it saves them from a lot of OS specific code. At present you can either use systemd in order to hibernate/sleep, or rely on the unmaintained abandonware like ConsoleKit.
No one has bothered updating ConsoleKit for the last 1½ year, so it may contain huge security holes, who knows? Who cares?
> How does the newbie know what to grep for without knowing what is written in the log?
"journalctl -b -1 -p err" seems to be exactly what newbie knows out of his mind. Pathetic loser!
Ah, the ad hominem attacks begin. As said earlier, you systemd haters just seem unable to have a technical argument. I understand why you hide as an AC.
Sure, no UI is intuitive (excepting the nipple), you still have to learn something if you want use the CLI to inspect the log file. It is just that very basic 'journalctl' knowledge gives the newbie an easy and consistent way to obtain useful information.
Just one man page to look at, instead of several (and the man page for grep is pretty intimidating for a newbie too). No need to learn piping to combine 'tac' and 'grep'. No need for grep Kung Fu just to show what went wrong since last boot.
Just the fact that systemd has indexed all entries in the log file (journal) makes it a breeze to use for both newbies and experienced SA's since it allows for e.g. autocompletion of all services that has ever written in the journal.
I don't think making syslog only register error levels above "Error" is a solution. After all, seeing that a service is starting correctly can be very useful debugging information too.
I don't share your view, that only people mastering awk, sed and grep should be allowed to use Linux, and while I love the power of e.g. GNU tools, I don't think they should be mandatory to learn just to perform basic system maintenance.
As a newbie desktop user coming from Windows, there are so many new concepts to learn, adding for them incomprehensible CLI magic doesn't help their transition at all.
I still remember how hard it was to learn all those things when I was a Linux newbie.
If you admin Linux machines, then I find it amazing that you haven't heard of systemd. The majority of Linux distributions are changing to it. There is a very vocal minority who rants against this development, they apparently have cushy jobs where they never need to learn anything new.
Systemd is the most significant change in Linux for a decade at least, since it changes and unifies many core aspects on how Linux works.
But even if you too find systemd foreign to the knowledge to have accumulated, try to give it a serious chance by eg. getting F20 and walk through "The systemd for Administrators Blog Series" at http://www.freedesktop.org/wiki/Software/systemd/
The new RHEL 7 will be pure systemd, so will the upcoming SUSE and CentOS etc, so not having thorough knowledge on how it works will seriously impede future job opportunities for Linux SA's that don't posses systemd skills.
The AC brigade is out in force tonight I see. Anyway.
Your example shows exactly what is wrong: 1. What error? How does the newbie know what to grep for without knowing what is written in the log? A 'grep "some error"' will of course miss both "Error" and "", but also miss errors indicated with "Failure" or "Warning". 2. The newbie can be swamped with error messages since your simplistic grep (without -i switch and path, and no pager too) just dump every "some error" logged the last couple of months unto the terminal. The journalctl example just showed errors generated since previous boot, something that is much harder to do with grep only.
The journalctl example shows how simple it is to filter the log so that only essential information is shown.
I read his comment just fine, my comment about CPU, as you would have understood if you had read carefully what I wrote, was a general observation that systemd-journald is a really fast lightweight daemon that doesn't consume much memory, or _even_ CPU time. (BTW, I can't fathom any scenario where a daemon does so much RW that it causes a system slowdown, without that daemon sucking up CPU time.)
The OP may have experienced slowdown problems after his upgrade, but systemd-journald in it self wasn't the cause of it. Yes, I can imagine problems upgrading from eg. F17 to F19 without modifying the config files, since the systemd journal wasn't persistent in early Fedora versions, and running both systemd-journald and syslog may double the amount of disk writes.
Just go for it. Fedora 20 is worth investing some time in, since it is systemd based and therefore shows the direction that most Linux distribution are heading. All the knowledge you gain about systemd and its tools like "journalctl" can be directly used in future Linux distro's like RHEL, CentOS, SUSE, etc.
So instead of wasting time getting to know a particular distros home made tools for eg. managing daemons, you can learn a set of standard tools that can be deployed exactly the same way across many different Linux distributions.
I think any System Admin out there should seriously start to learn systemd, even if their present production servers doesn't support it yet, because some day they will.
You are trying to be sarcastic but that doesn't help one bit. Some people don't seem to like systemd, and that is ok with me, but what I find hilarious about the systemd haters are that they can't seem to argue their case in any coherent technical way, they always seem to use ad hominem attacks combined with a considerable dose of paranoid conspiracy speculation. I think your problem is that you actually doesn't have any real knowledge or experience with systemd, that way you are bound to loose any technical argument.
The plain fact is that I am right and you are wrong. It is hard for newbies that they have learn several different programs and the concept of piping just to view logs. Getting to know 'grep' is only part of their problems, they also need to know what to grep for. grepping for "error" doesn't help if the crucial message is "critical failure".
With systemd a single line can tell them about all the errors that has happened since they booted the system, and the output is even nicely color coded. It is simple to perform log filtering on a systemd box, that would otherwise requires pretty advanced grep, sed/awk skills.
I think there was a systemd bug that caused syslog to freak out. But besides that, systemd-journald is lightening fast and lightweight on a proper systemd distro like Fedora. It on takes 300 K memory (+3 Megabyte shared mem) on my desktop system. I haven't seen it even suck up 1% CPU time ever.
systemd often keeps logfiles around for longer than many syslog implementations that uses a simple cron/time based logrotate. Since the journal is indexed size isn't really a issue. You can tweak the maximum size etc., but it unless you are starved for space, a couple of hundred megabytes for many months of log files aren't bad.
Also, systemd-journald logs much more that any sysvinit/syslog implementation is capable of, especially stuff that happens early in the boot process.
All in all I find that "systemd-journald" is extremely fast and resource lightweight, and I just love how well designed and documented the systemd tools are.
I really like Fedora. Been using it since Fedora Core 1 (and Red Hat before that). It has been rock solid for me all these years, and it just keeps on improving.
The new "systemd" internal plumbing system is a joy to use. "journalctl" is the finest new system tool I have seen for many years; it is really fast, and its superb autocompletion reduces typing to a minimum.
"$ journalctl -F _SYSTEMD_UNIT" instantly show all systemd services that has ever written to the log file.
"$ journalctl -b -1 -p err" filters the log file, so that only errors are shown (-p err) from the previous boot (-b -1, current boot is just "-b" etc.).
A tremendous help for newbies who now doesn't need to learn 'cat', 'grep', 'less' and piping in order to do basic log file inspection.
Besides improving my systemd skills, the next spare time project I will try on Fedora 20 is lightweight containers. They seems like a useful addition to full blown virtual guests.
The way this is set up, it relies at its foundation on a purely subjective concept - what is "quality" literature? I consider myself well read, and empathetic. But my favorite literature, which meets my personal criteria for quality, was written by authors like William S. Burroughs, Mickey Spillane and Louis-Ferdinand Céline. Not exactly a collection of empaths or good citizens by standard definitions.
Quality literature is what influential readers reach a inter-subjective conclusion about. So it isn't a law of nature, nor are there objective ways to deduce whether a work is quality literature or not. Still, assuming that not every piece of literature is of quality, and one cannot ever hope to read even a fraction of the books ever written, one has to rely on the taste of other influential readers and writers to shift through the masses of books. The system actually work in its own peculiar way.
All 3 authors you mention are widely regarded as good writers that produced some quality literature.
Notice that the empathy developing ability of reading quality literature, isn't about being nice, or reading nice works by nice authors (Celine as a person was an arrogant anti-semtic asshole by all accounts).
Empathy isn't about feeling sorry for someone, but to understand their situation as they themselves see it. So literature allows the impossible, namely to "see" into a foreign mind and see how it operates, to follow its logic or lack thereof. Literature trains the mind in the reading of other minds, and to see things from their perspective, even if you disagree strongly with it.
Fiction is of course fiction, and the mind William S. Burroughs conjure in "Junkie" is just a fictional construction despite its semi-biographical nature. Still, after reading it you may think that you actually better understand the mind of a unredeemed drug addict, something you may never have experienced in your real life.
Oh, so now the bar for doing evil is set at "being allowed to voluntarily add a photo to your google product reviews."
If that is your definition of evil then I wonder; do you have any words left for describing what was going on in the Auschwitz-Birkenau, Majdanek and Treblinka death camps.
The whole point of pressing "+1" is that other people can see your vote. It is like writing a product review on Amazon; doesn't make much sense if your default setting for writing reviews or pressing "+1" is "that no one can see what you do".
But google makes it very easy to turn it off if you want (superb user panel IMHO).
So the only news is that you now can allow your photo etc. to show up on the "endorsement" like a product, or a political cause. You actually have to write a review first using your google account for this ever to happen, even if you have "Shared Endorsements" activated.
Not something for me, but I am sure that there are some who get a kick out of seeing their own face and review among google search results.
Well, I just looked at my google+ account: "Shared Endorsement" is "off" on my account, even though I accepted the new ToS. The ToS I received stated it was something I could enable if I wished. Doesn't seem evil to me.
As I read the ToS, this is an opt in. So if you for some reason want to show your google+ friends, followers, or the world that you "+1" something, your can turn this feature on.
Why would MS have any interest in a dual booting phone? I find it more likely that MS is begging HTC to still make Windows phones and are trying to make this more attractive by suspending demand for the mandatory 17 Windows buttons or whatever they usually demand to certify the hardware. That way HTC can use exactly the same hardware for both their Android and Windows version, thereby reducing their development costs.
MS probably have to sweetening the deal by making their OS free for HTC to use too.
It is difficult to understand why any phone company would still want to make windows phones now that MS now are competing directly against them with their own large ex-Nokia production line. Yes, for sure, MS is no longer a software only company.
Nokia already sold their Windows phones with a hefty loss, so now MS either have to raise prices as to not out-compete other Windows phone makers (not going to happen), or compete for market share by dumping prices, thereby out-competing other Windows phone makers like HTC, or dump prices and compensate anyone desperate enough to still make Windows phones.
Many critiques of the war crimes tribunals after WWII, including the chief prosecutor who was a judge but never had a law degree, claim the prosecutions were ex post facto law (law after the fact) and the trials constituted a victors justice.
I'm not saying they didn't deserve what they got, but lets not pretend it was all on the up and up when comparing it to other things we find horrible too.
What absolute rubbish to dump on Slashdot. I think the only one seriously criticizing the allied criminal tribunals for being "victors justice" was from people sympathetic to the nazi cause, often perpetrators of the worst kind. Unlike you, I have actually seen a lot of archival material from eg. the British "War Crimes Group (NW Europe)". And I can assure you, that unless the evidence against the German perpetrators could hold up in a normal criminal court, they didn't prosecute.
The sad fact is, that the vast majority of nazi war criminals never was prosecuted. It wasn't enough to be an officer in a unit whose whole purpose was mass slaughter of civilians like the SS Police battalions, and the officer's unit a proven record of murdering tens of thousands civilians in a 6 month period. If it couldn't be proved by witness account that the officer personally had shot specific victims, he wouldn't be persecuted.
The nazi mass murderers below the absolute top ranks, usually never got prosecuted, and those few that was, often got mild sentences, and by mass pardons, usually was released after a few years.
Nokia could have had excellent success with an Android phone. Unlike the many upcoming phone makers you see today, Nokia had a huge market share with lots of loyal costumers who always chose Nokia phones when they needed a replacement phone. Nokia was a premium brand among consumers.
By not making a Android phone, all their loyal costumers were forced to go elsewhere. For years, 9 out of 10 Nokia costumers have chosen another brand of smartphone when they needed a new phone. If Nokia could have kept most of those costumers with a Android phone, they would be dominating the market this day, and they would have kept the up coming competitors down, in stead of just handing over the smartphone market to them without a fight.
Go on then. Tell us who else is going to put up the money for more than a few comsats and why they will do it. We're listening. Surely you've got some kind of obvious answer since you are calling another a liar - let's see it.
I called the OP a liar because he lied about Neil deGrasse Tyson. He never claimed "only the government can do Space", in fact, if you and the OP actually Read The F*ne Article about him, you will see that he is an favour of commercial space activity, and in fact thought it scandalous that NASA had delayed such a development for years, hinting that the Space Shuttle program was part of the reason.
For scientists, like Tyson, it makes no sense that NASA should spend their budget on making rockets for commercial satellite delivery, let the private sector do that, and let NASA concentrate on new research and space exploration.
What Tyson also said was, that he didn't think the private sector would do trailblazing space feats, it is way too expensive to do space exploration compared to the economic gains that there simply isn't a business case.
Well, Nokia certainly isn't the first "partner" company Microsoft rapes and plunders. Their usual tactic with small companies was getting a good inside look at the technology while dangling a sack of cash in front of the owners, and then steal the technology and hire all the key workers, leaving the "partner" company as a gutted empty husk.
This time MS at least paid some token money for what they got.
It is hard to imagine that others smartphone makers will continue to make Windows phone after this.
Slashdot Mirror
Does synchronisation use rsync or is it a from-scratch implementation?
Not sure, but I don't think so. It works a little different from simple folder syncronisation tools.
First it compares the two folders and then display display the differences using kdiff (or similarities, depending on the filters). There are various ways and options for filtering this, but when satisfied, one use the filtered output to synchronise the folders.
So it gives one a very good overview of what is going to be synchronized, and what exactly you want to synchronise at all. So folder synchronisation for the control freak.
Different strokes....
I think KDE has a brilliant UI that supports my workflow wonderfully. I find it much better than Mac OSX and MS Windows in almost every aspect. Haven't used Gnome since the early 2.0 days, but I never liked how it worked or how it looked, and I found KDE programs superior for my use: K3b, Krusader, Kmail, Amarok, Kontakt, Digikam, Gwenview, KTorrent, Konsole are IMHO superior what else I have seen on Linux.
Never had KDE Plasma crash on me, even with extreme loads.
Krusader is a KDE favourite of mine. Very underrated. It is twin panel, tabbed file-manager, with masking filters (e.g. select only "*.otd" files), the ability to unpack archives, and has superb "synchronise folders" feature. It's mass rename feature is very good too.
I look forward to the GPG backend to Kwallet. I was never quite sure how safe the encryptet wallet was, but with GnuPG I know what I get.
Ctrl-Click to launch URL's directly from Konsole looks nice too. It is a "right mousebutton" context menu at the moment, but clicking underlined URL's just seems right.
Great for "journalctl" with the "-x" switch that enables the catalogue db's, so that error messages in the log file are displayed together with full explanations and URL's pointing to support and documentation etc.
Citation needed.
I assume you mean about RHEL using systemd.
The RHEL 7 beta is out, and it uses systemd:
https://access.redhat.com/site/discussions/644203
Fedora is an excellent platform for learning systemd, but a beta evaluation of RHEL 7 can be had here:
https://access.redhat.com/site/products/Red_Hat_Enterprise_Linux/Get-Beta
I have no problem with people having different preferences. In fact my main problem with systemd haters are exactly that they continually slander open source developers like Poettering just for making a init system that they evidently doesn't use or have any real knowledge about.
Content free statements like "Unix philosophy means ..." doesn't convince either. grep, sed, cp, diff etc. are all useful tools, but I have absolutely no problem with Linux users that doesn't know anything about them, but just uses a GUI like Gnome for everything.
Make it easy for people to use Linux I say, and with systemd it will actually become feasible to write a proper GUI program for showing log files that can do sorting and filtering and what not, due to the fact that the journal is structured. Not only that, it will function across all systemd distros without a tons of distro specific code.
> since it is systemd based and therefore shows the direction that most Linux distribution are heading
We would be happy if you'd stop spreading such unproven bs!
Red Hat, Fedora, CentOS, SUSE, OpenSUSE, Arch Linux, Mageia, Sabayon Linux all enables systemd as default. There are probably many more, and certainly many more to come in the future. Besides that, distros like Gentoo and Debian have systemd as an option. Hey, even a slacker is working on systemd support on Slackware.
All desktop environments like Gnome, KDE, LXDE are integrating systemd like crazy because it saves them from a lot of OS specific code. At present you can either use systemd in order to hibernate/sleep, or rely on the unmaintained abandonware like ConsoleKit.
No one has bothered updating ConsoleKit for the last 1½ year, so it may contain huge security holes, who knows? Who cares?
> How does the newbie know what to grep for without knowing what is written in the log?
"journalctl -b -1 -p err" seems to be exactly what newbie knows out of his mind. Pathetic loser!
Ah, the ad hominem attacks begin. As said earlier, you systemd haters just seem unable to have a technical argument. I understand why you hide as an AC.
Sure, no UI is intuitive (excepting the nipple), you still have to learn something if you want use the CLI to inspect the log file. It is just that very basic 'journalctl' knowledge gives the newbie an easy and consistent way to obtain useful information.
Just one man page to look at, instead of several (and the man page for grep is pretty intimidating for a newbie too). No need to learn piping to combine 'tac' and 'grep'. No need for grep Kung Fu just to show what went wrong since last boot.
Just the fact that systemd has indexed all entries in the log file (journal) makes it a breeze to use for both newbies and experienced SA's since it allows for e.g. autocompletion of all services that has ever written in the journal.
I don't think making syslog only register error levels above "Error" is a solution. After all, seeing that a service is starting correctly can be very useful debugging information too.
I don't share your view, that only people mastering awk, sed and grep should be allowed to use Linux, and while I love the power of e.g. GNU tools, I don't think they should be mandatory to learn just to perform basic system maintenance.
As a newbie desktop user coming from Windows, there are so many new concepts to learn, adding for them incomprehensible CLI magic doesn't help their transition at all.
I still remember how hard it was to learn all those things when I was a Linux newbie.
If you admin Linux machines, then I find it amazing that you haven't heard of systemd. The majority of Linux distributions are changing to it. There is a very vocal minority who rants against this development, they apparently have cushy jobs where they never need to learn anything new.
Systemd is the most significant change in Linux for a decade at least, since it changes and unifies many core aspects on how Linux works.
But even if you too find systemd foreign to the knowledge to have accumulated, try to give it a serious chance by eg. getting F20 and walk through "The systemd for Administrators Blog Series" at http://www.freedesktop.org/wiki/Software/systemd/
The new RHEL 7 will be pure systemd, so will the upcoming SUSE and CentOS etc, so not having thorough knowledge on how it works will seriously impede future job opportunities for Linux SA's that don't posses systemd skills.
> journalctl -b -1 -p err
is of course straight forward compared to
grep "some error" log
The AC brigade is out in force tonight I see. Anyway.
Your example shows exactly what is wrong:
1. What error? How does the newbie know what to grep for without knowing what is written in the log? A 'grep "some error"' will of course miss both "Error" and "", but also miss errors indicated with "Failure" or "Warning".
2. The newbie can be swamped with error messages since your simplistic grep (without -i switch and path, and no pager too) just dump every "some error" logged the last couple of months unto the terminal. The journalctl example just showed errors generated since previous boot, something that is much harder to do with grep only.
The journalctl example shows how simple it is to filter the log so that only essential information is shown.
I really recommend you try to actually learn systemd. Get F20 and hack away.
This is a good starting point:
http://www.freedesktop.org/wiki/Software/systemd/
You can still use all the grep, sed, awk Kung Fu you know with journalctl, it just makes it so much easier.
I read his comment just fine, my comment about CPU, as you would have understood if you had read carefully what I wrote, was a general observation that systemd-journald is a really fast lightweight daemon that doesn't consume much memory, or _even_ CPU time. (BTW, I can't fathom any scenario where a daemon does so much RW that it causes a system slowdown, without that daemon sucking up CPU time.)
The OP may have experienced slowdown problems after his upgrade, but systemd-journald in it self wasn't the cause of it. Yes, I can imagine problems upgrading from eg. F17 to F19 without modifying the config files, since the systemd journal wasn't persistent in early Fedora versions, and running both systemd-journald and syslog may double the amount of disk writes.
Just go for it. Fedora 20 is worth investing some time in, since it is systemd based and therefore shows the direction that most Linux distribution are heading. All the knowledge you gain about systemd and its tools like "journalctl" can be directly used in future Linux distro's like RHEL, CentOS, SUSE, etc.
So instead of wasting time getting to know a particular distros home made tools for eg. managing daemons, you can learn a set of standard tools that can be deployed exactly the same way across many different Linux distributions.
I think any System Admin out there should seriously start to learn systemd, even if their present production servers doesn't support it yet, because some day they will.
You are trying to be sarcastic but that doesn't help one bit. Some people don't seem to like systemd, and that is ok with me, but what I find hilarious about the systemd haters are that they can't seem to argue their case in any coherent technical way, they always seem to use ad hominem attacks combined with a considerable dose of paranoid conspiracy speculation. I think your problem is that you actually doesn't have any real knowledge or experience with systemd, that way you are bound to loose any technical argument.
The plain fact is that I am right and you are wrong. It is hard for newbies that they have learn several different programs and the concept of piping just to view logs. Getting to know 'grep' is only part of their problems, they also need to know what to grep for. grepping for "error" doesn't help if the crucial message is "critical failure".
With systemd a single line can tell them about all the errors that has happened since they booted the system, and the output is even nicely color coded.
It is simple to perform log filtering on a systemd box, that would otherwise requires pretty advanced grep, sed/awk skills.
I think there was a systemd bug that caused syslog to freak out. But besides that, systemd-journald is lightening fast and lightweight on a proper systemd distro like Fedora. It on takes 300 K memory (+3 Megabyte shared mem) on my desktop system. I haven't seen it even suck up 1% CPU time ever.
systemd often keeps logfiles around for longer than many syslog implementations that uses a simple cron/time based logrotate. Since the journal is indexed size isn't really a issue.
You can tweak the maximum size etc., but it unless you are starved for space, a couple of hundred megabytes for many months of log files aren't bad.
Also, systemd-journald logs much more that any sysvinit/syslog implementation is capable of, especially stuff that happens early in the boot process.
All in all I find that "systemd-journald" is extremely fast and resource lightweight, and I just love how well designed and documented the systemd tools are.
KDE Plasma Workspaces 4.11 and systemd, yes!
I really like Fedora. Been using it since Fedora Core 1 (and Red Hat before that). It has been rock solid for me all these years, and it just keeps on improving.
The new "systemd" internal plumbing system is a joy to use. "journalctl" is the finest new system tool I have seen for many years; it is really fast, and its superb autocompletion reduces typing to a minimum.
"$ journalctl -F _SYSTEMD_UNIT" instantly show all systemd services that has ever written to the log file.
"$ journalctl -b -1 -p err" filters the log file, so that only errors are shown (-p err) from the previous boot (-b -1, current boot is just "-b" etc.).
A tremendous help for newbies who now doesn't need to learn 'cat', 'grep', 'less' and piping in order to do basic log file inspection.
Besides improving my systemd skills, the next spare time project I will try on Fedora 20 is lightweight containers. They seems like a useful addition to full blown virtual guests.
The way this is set up, it relies at its foundation on a purely subjective concept - what is "quality" literature? I consider myself well read, and empathetic. But my favorite literature, which meets my personal criteria for quality, was written by authors like William S. Burroughs, Mickey Spillane and Louis-Ferdinand Céline. Not exactly a collection of empaths or good citizens by standard definitions.
Quality literature is what influential readers reach a inter-subjective conclusion about. So it isn't a law of nature, nor are there objective ways to deduce whether a work is quality literature or not. Still, assuming that not every piece of literature is of quality, and one cannot ever hope to read even a fraction of the books ever written, one has to rely on the taste of other influential readers and writers to shift through the masses of books. The system actually work in its own peculiar way.
All 3 authors you mention are widely regarded as good writers that produced some quality literature.
Notice that the empathy developing ability of reading quality literature, isn't about being nice, or reading nice works by nice authors (Celine as a person was an arrogant anti-semtic asshole by all accounts).
Empathy isn't about feeling sorry for someone, but to understand their situation as they themselves see it. So literature allows the impossible, namely to "see" into a foreign mind and see how it operates, to follow its logic or lack thereof. Literature trains the mind in the reading of other minds, and to see things from their perspective, even if you disagree strongly with it.
Fiction is of course fiction, and the mind William S. Burroughs conjure in "Junkie" is just a fictional construction despite its semi-biographical nature. Still, after reading it you may think that you actually better understand the mind of a unredeemed drug addict, something you may never have experienced in your real life.
google: do evil
Oh, so now the bar for doing evil is set at "being allowed to voluntarily add a photo to your google product reviews."
If that is your definition of evil then I wonder; do you have any words left for describing what was going on in the Auschwitz-Birkenau, Majdanek and Treblinka death camps.
The whole point of pressing "+1" is that other people can see your vote. It is like writing a product review on Amazon; doesn't make much sense if your default setting for writing reviews or pressing "+1" is "that no one can see what you do".
But google makes it very easy to turn it off if you want (superb user panel IMHO).
So the only news is that you now can allow your photo etc. to show up on the "endorsement" like a product, or a political cause. You actually have to write a review first using your google account for this ever to happen, even if you have "Shared Endorsements" activated.
Not something for me, but I am sure that there are some who get a kick out of seeing their own face and review among google search results.
Well, I just looked at my google+ account: "Shared Endorsement" is "off" on my account, even though I accepted the new ToS. The ToS I received stated it was something I could enable if I wished.
Doesn't seem evil to me.
As I read the ToS, this is an opt in. So if you for some reason want to show your google+ friends, followers, or the world that you "+1" something, your can turn this feature on.
Why would MS have any interest in a dual booting phone? I find it more likely that MS is begging HTC to still make Windows phones and are trying to make this more attractive by suspending demand for the mandatory 17 Windows buttons or whatever they usually demand to certify the hardware.
That way HTC can use exactly the same hardware for both their Android and Windows version, thereby reducing their development costs.
MS probably have to sweetening the deal by making their OS free for HTC to use too.
It is difficult to understand why any phone company would still want to make windows phones now that MS now are competing directly against them with their own large ex-Nokia production line. Yes, for sure, MS is no longer a software only company.
Nokia already sold their Windows phones with a hefty loss, so now MS either have to raise prices as to not out-compete other Windows phone makers (not going to happen), or compete for market share by dumping prices, thereby out-competing other Windows phone makers like HTC, or dump prices and compensate anyone desperate enough to still make Windows phones.
Many critiques of the war crimes tribunals after WWII, including the chief prosecutor who was a judge but never had a law degree, claim the prosecutions were ex post facto law (law after the fact) and the trials constituted a victors justice.
I'm not saying they didn't deserve what they got, but lets not pretend it was all on the up and up when comparing it to other things we find horrible too.
What absolute rubbish to dump on Slashdot. I think the only one seriously criticizing the allied criminal tribunals for being "victors justice" was from people sympathetic to the nazi cause, often perpetrators of the worst kind. Unlike you, I have actually seen a lot of archival material from eg. the British "War Crimes Group (NW Europe)". And I can assure you, that unless the evidence against the German perpetrators could hold up in a normal criminal court, they didn't prosecute.
The sad fact is, that the vast majority of nazi war criminals never was prosecuted. It wasn't enough to be an officer in a unit whose whole purpose was mass slaughter of civilians like the SS Police battalions, and the officer's unit a proven record of murdering tens of thousands civilians in a 6 month period. If it couldn't be proved by witness account that the officer personally had shot specific victims, he wouldn't be persecuted.
The nazi mass murderers below the absolute top ranks, usually never got prosecuted, and those few that was, often got mild sentences, and by mass pardons, usually was released after a few years.
Nokia could have had excellent success with an Android phone. Unlike the many upcoming phone makers you see today, Nokia had a huge market share with lots of loyal costumers who always chose Nokia phones when they needed a replacement phone. Nokia was a premium brand among consumers.
By not making a Android phone, all their loyal costumers were forced to go elsewhere. For years, 9 out of 10 Nokia costumers have chosen another brand of smartphone when they needed a new phone.
If Nokia could have kept most of those costumers with a Android phone, they would be dominating the market this day, and they would have kept the up coming competitors down, in stead of just handing over the smartphone market to them without a fight.
Go on then. Tell us who else is going to put up the money for more than a few comsats and why they will do it. We're listening. Surely you've got some kind of obvious answer since you are calling another a liar - let's see it.
I called the OP a liar because he lied about Neil deGrasse Tyson. He never claimed "only the government can do Space", in fact, if you and the OP actually Read The F*ne Article about him, you will see that he is an favour of commercial space activity, and in fact thought it scandalous that NASA had delayed such a development for years, hinting that the Space Shuttle program was part of the reason.
For scientists, like Tyson, it makes no sense that NASA should spend their budget on making rockets for commercial satellite delivery, let the private sector do that, and let NASA concentrate on new research and space exploration.
What Tyson also said was, that he didn't think the private sector would do trailblazing space feats, it is way too expensive to do space exploration compared to the economic gains that there simply isn't a business case.
Well, Nokia certainly isn't the first "partner" company Microsoft rapes and plunders. Their usual tactic with small companies was getting a good inside look at the technology while dangling a sack of cash in front of the owners, and then steal the technology and hire all the key workers, leaving the "partner" company as a gutted empty husk.
This time MS at least paid some token money for what they got.
It is hard to imagine that others smartphone makers will continue to make Windows phone after this.