Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Re: Jerri (Score 3, Informative) 523

See what happened in Paris and Denmark. People from Europe travel to Syria and Iraq to fight with ISIS, get training and AK47s, and then come back to Europe to kill the infidels.

Omar El-Hussein, the Copenhagen shooter, never went to Syria nor Iraq, never received any terrorist training, and didn't use an AK47, nor is there any evidence he ever communicated with terrorist organisations.

He did use a C7 rifle stolen from a member of the Danish national guard, but apparently had no weapons training. He did spend a couple of years in the Middle East years ago, but his radicalization appears to have happened primarily while he was incarcerated in Denmark.

Comment: Re:Can they do it with corporate code? (Score 1) 220

by Kiwikwi (#48930925) Attached to: Anonymous No More: Your Coding Style Can Give You Away

Can they do it with corporate code where there are naming and style standards in abundance, and code reviews to ensure those guidelines are followed?

Presumably, yes. Style guides are 95% formatting, and if one RTFA (I know, I know), they look only at the structure of the parsed AST, not variable names, comments and whitespace. From the article:

Accuracy rates weren’t statistically different when using an off-the-shelf C++ code obfuscators. Since these tools generally work by refactoring names and removing spaces and comments, the syntactic feature set wasn’t changed so author identification at similar rates was still possible.

Since they look at code structure, they've even found identifying patterns that survive compilation and end up in the binary.

This is one of the coolest data mining results I've seen in quite a while.

Comment: Re:Well... (Score 3, Informative) 181

by Kiwikwi (#48849921) Attached to: NSA Hack of N. Korea Convinced Obama NK Was Behind Sony Hack

How would the West feel about the release of a popular film in which the assassination of a living head of state is planned? How would your government behave toward you if YOU wrote a book / published a film / performed a play about this?

In 2006, Death of a President portrayed the assasination of George W. Bush. I don't remember hearing about it at the time, and even searching the website of Fox News doesn't turn up much controversy.

In 2008, AFR came out, in which Anders Fogh Rasmussen, the then-Prime Minister of Denmark (and later Secretary-General of NATO) was murdered (and also, incidentally, portrayed as a closeted homosexual, in line with long-standing rumours). It genereted minor controversy, was well-received by critics, and a failure at the box office. I found it forgettable (I literally don't remember any of it).

Of course, both films were small, independent films, and both can legitimately claim to use the controversial plot for a higher purpose. The Interview... not so much.

Comment: Re:"We listen to users" (Score 1) 551

by Kiwikwi (#48835677) Attached to: Systemd's Lennart Poettering: 'We Do Listen To Users'

In addition to which, you replace it with something that requires more typing, and does not give any feedback. service nfs restart stopping nfsd starting nfsd etc.

systemctl restart nfs

Here you go; put this in your .bashrc:

service() { systemctl $2 $1; }

And the entire concept of *BINARY* logfiles,

Install a syslog daemon and put this in your /etc/systemd/journald.conf?

[Journal] ForwardToSyslog=yes

Or just install syslog-ng 3.6.1+, which requires no additional journald configuration?

xml configuration files [are] insanely stupid when X won't run, or isn't installed (like on a server).

Where does systemd use XML configuration files? (And what does XML and X have to do with eachother?)

And telling me that oh, it boots up *so* much faster means something *only* if I'm on a laptop.

Or a virtual machine, or a container...

Comment: Re:The very first thing out of his mouth (Score 1) 551

by Kiwikwi (#48835287) Attached to: Systemd's Lennart Poettering: 'We Do Listen To Users'

The very first thing out of his mouth is a straw man.

Basically, his arguments are :
* systemd haters have no clue about UNIX
* RedHat took a long time to notice my genius
* Gentoo users are old-farts that don't like beautifully written shiny new stuff
* Debian users are even older assholes
* You can use Gnome without systemd, but it won't work
* I listen to users, but they're all idiots

I take it that the irony of accusing Lennart of strawman arguments and then posting this is lost on you.

Comment: Re:When I see that [literaly] textbook mistake.... (Score 1) 329

by Kiwikwi (#48832201) Attached to: Steam For Linux Bug Wipes Out All of a User's Files

if [ ! -z "$STEAMROOT" ] then...

! -z is the same as -n; though personally, I find it more readable to elide the "-z" and "-n" test operators entirely:

if [ ! "$STEAMROOT" ]; then echo "BAD BAD BAD"; exit 1; fi


if [ "$STEAMROOT" ]; then rm stuff; fi

(And yes, this still works if $STEAMROOT starts with a dash.)

Comment: Re:um, no (Score 2) 216

by Kiwikwi (#48302969) Attached to: Scotland Builds Power Farms of the Future Under the Sea


Solar is the real eye opener and should serve as a lesson on blindly trusting hype and "What seems obvious." Solar panels are terrible for the environment,

It's always important to remember that there's no such thing as free energy. That said, the linked graph doesn't say anything about solar being "terrible for the environment", only that other sources of electricity consumes* very little silver compared to solar (as Scientific American also notes in the graph). Importantly, it does not show how that use compares to e.g. worldwide silver use.

* "consumes"? "wastes"? "produces as a byproduct"? Pretty sure that oil energy (or biomass!) doesn't consume uranium, even if drilling for oil produces it as a byproduct. Not sure what exactly is being graphed here, honestly. Unfortunately, the cited report is paywalled.

Anyway, if you look at the other report cited by Scientific American as the graph source, in figure 4 on page 19, it shows the global material requirements (in giga-grams, that is, kilotons) under various energy mix scenarios. Neither silver or tin use even registers on the graph in the so-called "non-fossil" scenario (mix of solar, wind and hydro - and no nuclear). In other words, in the "non-fossil" scenario, silver and tin usage for power is less than 1 kiloton a year. Worldwide silver use in 2013 was 34 kt.

As a bonus, silver recycles better than aluminum, with energy savings of 96% (table 4.4).

Comment: Re:Fedora fork too (Score 1) 555

by Kiwikwi (#48199021) Attached to: Debian's Systemd Adoption Inspires Threat of Fork

It seems whenever people want to show how simple a SysV init script can be, they pull out examples that don't do half of what the (still much shorter) SystemD unit file does.

In this example from Slackware:

- 'sendmail' is a globally reserved name for a binary; only the system-wide sendmail daemon may use it.
- you cannot query the service status.
- there's no automatic preprocesing of sendmail config files (rehashing etc.)
- there's no dependency information

And that's just what's missing compared to the Fedora SysV init script.

The Fedora SystemD unit file adds at least the following features:

- the ability to reliably stop or restart the service
- automatic restart if the service dies

Comment: Re:2,266,800 (Score 4, Informative) 407

by Kiwikwi (#48168677) Attached to: As Prison Population Sinks, Jails Are a Steal

1.6M? The U.S. prison population is 2,266,800 according to Wikipedia. It's been over 2M for years, and was 2,418,352 in 2008.

In the U.S., the word "prison" is more specific than you think. Look at the third figure from the top at your own link.

In 2010, the U.S. prison population was ~1,518,000 (state and federal prisons). The U.S. jail population was ~749,000. The sum of those is 2,267,000; then comes another ~90,000 in juvenile detention (see the table below the figure). Add all these (and a bunch of smaller numbers, such as holding facilities for immigrants, and military facilities), you get the number of incarcerated people, which is the number you mention.

But yes, AFAIK the U.S. still incarcerates more people than any other country in the world, both as a fraction of the population, and in absolute numbers. There's a long way down to the next on the list.

Comment: Re:Charging amperage (Score 2) 395

Enh, seems to be only off by a factor 10, though IANAEE (I am not an electrical engineer). Forgive me if I'm missing a factor 1.44 or something, below.

Obviously you don't charge an electric car battery at 12 V. What the individual cells do is irrelevant, since they charge in parallel; the bottle neck is the cable attached to the car (and cooling, but hey, we're assuming magic new wonder battery tech, so I'll conveniently ignore that issue).

The highest power available using standard CEE (IEC 60309) plugs and mainline voltage is 3 x 125A x 230V, or about 86 kW. This is not normal in a home, obviously, but you can easily get a couple of these in commercial installations.

Ignoring losses (I know, I know), 86 kW means one hour to fully charge a Tesla Model S with the big 85 kWh battery pack, but that's also a big battery pack.

Charging the 48 kWh battery of the upcoming Model E to 70 % will take: 70% x 48 kWh / 86 kW = 23 minutes.

Now, I would've thought 3 x 125 A x 230V was about the limit, simple due to the weight (those cables are very heavy!). But apparently, Tesla Superchargers go beyond this, to more than 120 kW (340 A x 360 V), with possible plans for 135 kW or even 150 kW. (I guess if the cable is short enough, and you increase voltage beyond mains voltage...) This gives you 70% x 48 kWh charging times in as little as 17 minutes (120 kW) or even 13 minutes (150 kW). Still a far cry from 2 minutes, but then the 17 minute figure is using current mass-market technology.

Comment: Re:The water wars are coming (Score 5, Insightful) 151

by Kiwikwi (#48037819) Attached to: Aral Sea Basin Almost Completely Dry

Yup, this is what you get when a short-sighted totalitarian government messes with the water cycle to enable farming in a desert, consequences be damned.

Come to think of it, California is what you get when a short-sighted democratic government messes with the water cycle to enable farming in a desert, consequences be damned.

Let's face it, environmental concerns wasn't really on any government's radar until the 70s. (And a lot of countries still try to ignore them...)

Comment: Re:~/.cshrc (Score 3, Interesting) 208

by Kiwikwi (#48012793) Attached to: Apple Yet To Push Patch For "Shellshock" Bug

It really has nothing to do with the default shell. It won't matter what shell is the default when your CGI script starts with #!/bin/bash.

No, no, no, no... People really don't get the scope of this.

It doesn't matter what the default user shell is, or what language a CGI script is written in. Bash is the most common system shell, which means it's invoked all the time when other programs run commands.

Obviously, I can't know this, but OP is probably not using csh as his system shell, because that's not POSIX compliant and would cause major breakage.

If /bin/sh is Bash, you're vulnerable, no matter what shell you're using yourself, or what language your CGI script is written in.

Also, CGI scripts is only the most obvious attack vector; others that have been identified so far are the CUPS printing daemon, the ISC DHCP client and locked down SSH shells like those commonly used to host Git repositories. But there are without doubt many more. The only safe thing to do is to upgrade or remove Bash from your system immediately.

Comment: Re:"could be worse than Heartbleed" (Score 1) 318

by Kiwikwi (#48001199) Attached to: Flurry of Scans Hint That Bash Vulnerability Could Already Be In the Wild

No, it is any CGI program that sets an environment variable to unchecked user input and then invokes a shell or calls any other program that invokes a shell.

Got that?

No, it's not the CGI program that sets the HTTP_USER_AGENT environment variable, and this is not a vulnerability in the CGI program nor the CGI protocol. The fault lies 100% with Bash, which executes arbitrary shell code from arbitrary environment variables.

Due to lack of disk space, this fortune database has been discontinued.