nmcli, nmtui, nm-tool all use small letters.
Slashdot videos: Now with more Slashdot!
Did you really just say that Oracle fixing "what" you told it do makes it better at SQL, because SQL is about the engine figuring out the "how"?
you only have to worry about family members..
Chrome itself isn't available in the repositories of Debian or Ubuntu. Chromium is. Mint may have it. The usual way is to get the deb file from Google, which adds a source entry for Google's repos.
Ah, but others endangered by your actions want it to.
How does using COW images save RAM? It's one of the arguments posted by GGP.
If that system takes over, what difference does autofilling an entry make? It only fills the field, and doesn't submit it. On the other hand, idiotic site's like Microsoft's will stop being an annoyance to users like me.
The linked changelog and description are for Firefox 28. For FF 30: http://www.mozilla.org/en-US/firefox/30.0/releasenotes/. Even accounting for FF's release schedule and for Slashdot delay, that's a bit much. Only important change for me as an end-user looks to be:
Ignore autocomplete="off" when offering to save passwords via the password manager (see 956906)
The first is Linus's reply in which the very first line is:
And by "their" you mean Kay Sievers.
As for Ingo, for all I know, he may have some beef with the systemd team.
Those interested may look at LWN's report for a saner, more balanced view: http://lwn.net/Articles/593676/
Torvalds is pissed off at Kay Sievers, not at systemd and not at the systemd team. He's fine with Greg Kroah-Hartman taking over that mess until Sievers can get his shit together. I went through the original bug report and the kernel mailing list discussion when it first caught the limelight, and I think you're seeing Sievers's actions (condemnable as they are) as representative of the whole systemd team. (They maybe, in which case you need to show more than one lone post as proof.)
Finding "systemctl -xb" you just realise that there actually is something neat about the system being able to understand it's own logs. Finding out that your system is failing to boot because of one directory permission (/var to the wrong user) and that it doesn't start a shell at all or anything you can debug with is just disappointing.
I guess you mean "journalctl -xb". Even so, I had an issue with a mount failing (not a critical one), and systemd dropped me into a what it called a root shell. (See #733232 for a similar situation). Of course, then the system was practically fully up, so the shell was fully functional. However, I refuse to believe that systemd can't start a shell to debug. It might not do so by default, but it can. See http://freedesktop.org/wiki/Software/systemd/Debugging/ (and https://fedoraproject.org/wiki/Systemd_early_debug_shell for what I presume is an older guide).
Ideone. Codepad. Any number of pastebins.
That image is practically unreadable. As pointed out later on, the 600x600 scaled version worked much better and scaling each QR pixel by 3 is the current idea.
Indeed. Note what Linus says further down the thread:
> Well, parsing kernel cmdline by systemd is a bad idea
No, we very much expose
are *supposed* to parse it, because it gives a unified way for people
to pass in various flags. The kernel doesn't complain about flags it
doesn't recognize, exactly because the kernel realizes that "hey,
maybe this flag is for something else".
And yes, that does include "quiet" and "debug". Parsing them and doing
something sane with them is not a bug, it's a feature.
And the thing is, this has never really been a problem in practice.
Because nobody minds if some kernel option like "debug" makes not only
the kernel enable debugging, but some system deamon log a bit more
It does become a problem when you have a system service developer who
thinks the universe revolves around him, and nobody else matters, and
people sending him bug-reports are annoyances that should be ignored
rather than acknowledged and fixed. At that point, it's a problem.
It looks like Greg has stepped in as a baby-sitter for Kay, and things
are going to be fixed. And I'd really like to avoid adding hacky code
to the kernel because of Kay's continued bad behavior, so I hope this
works. But it's really sad that things like this get elevated to this
kind of situation, and I personally find it annoying that it's always
the same f*cking primadonna involved.
One of the original suggestions was utilities parsing the kernel command line was a Bad Thing (TM).