Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Comment Re:So when are they making something we can AFFORD (Score 1) 321

What's the point of that? It's large, ugly as sin, and the concept only works assuming low use anyway. It's also not going to work as intended if you park it in a garage, inside parking spot, or in the shade.

I wonder if it's even practical in ideal conditions, because a car parked in the sun gets hot as hell, and batteries don't like that much.

It's much better to put those panels on your roof instead. That way you can go with cheaper and less efficient panels because there's less need to squeeze all the possible power in the small amount of room available, they'll be unobstructed as much as possible, collecting power at all times when there's any to collect, and it can be used for things besides the car.

Comment Re:wrong analogy (Score 1) 528

You are ignoring how other countries have benefitted from our pollution. China's economy would still be shit with 2 billion starving people instead of 1 billion.

And the glazier benefits from broken windows. That your actions had an effect that was positive for somebody doesn't mean you get out of paying damages. See the broken window fallacy.

Comment Re:This is what Climate Change is all about.... (Score 4, Interesting) 528

What's marxist about it? You break somebody's window, you have to pay them for the repairs. You poison somebody else's garden, you pay for having it replanted. This is pure capitalism and the very model libertarians propose.

Comment Re: why bother? (Score 1) 232

Hah, I knew it. You have no ability to hold a technical discussion.

If there's somebody not needed here, it's people who are ignorant and proud of it. If you actually want to contribute something useful, start coding. You discredit your own cause by posting this nonsense.

Comment Re: why bother? (Score 2) 232

You systemd haters are really hilarious.

Where else do you get to see somebody professing their love of the True Unix with Unix Philosophy, while repeatedly demonstrating ignorance of the very system they claim to love so much?

Allow me to impart a bit of education: some things have more than one manpage. For instance there's a manpage for both cron, and crontab, and Perl has a whole bunch of them. Any competent admin would know this and wouldn't be mystified by systemd having separate manpages for commandline tools and descriptions of unit files.

Comment Re: why bother? (Score 2) 232

Actually it is a step forward.

In sysv land, this is the difference between letting a service fork by itself and using start-stop-daemon. If you take the later approach, start-stop-daemon will perform the daemonization task on behalf of the service. In such a case if it ever prints on stderr, it will be lost in the void, since it's no longer connected to any terminal. systemd actually will ensure it goes into the log.

Comment Re: why bother? (Score 3, Informative) 232

Actually no, it hasn't. sysv init has long been a pile of hacks on top of a pile of hacks. Ever tried to write a sysv service? It's really wonderful when a service refuses to come up because the pid file was left around for whatever reason, and some other program happens to be running under that pid.

For instance, the stderr thing this guy is complaining about was long a "feature" of sysv systems, where stderr could actually disappear into the void. Systemd actually makes things much better by ensuring stderr always gets saved.

As to why change logging, under systemd you can trivially ask for the messages for a particular service, or the messages from last boot, without having to figure out what to grep for, or having to setup syslogd beforehand to sort out your messages into separate files.

Comment Re: why bother? (Score 1) 232

That's a stupid attitude to have in a field that moves as fast as computing. The internet didn't exist in anything resembling the current shape 30 years ago, just to give an example. You don't get to excuse ignorance of networking just because of that. I don't see how it's viable remaining a sysadmin without dealing with the fact that the hardware, software, and needs of the organization are constantly changing.

Nevertheless, all it takes is "ForwardToSyslog=yes" in journald.conf.

Comment Re: why bother? (Score 2) 232

No, it is not. The string "forking" isn't anywhere in the man page for systemd on Red Hat. Considering Poettering works for Red Hat, that is a pretty big omission if you're right that it is the solution, and it isn't considering I have that in the unit file.

That's because the systemd manpage is about the main application. You want the systemd.service manpage.

Comment Re: why bother? (Score 4, Informative) 232

What are you on about?

$ cat /usr/local/bin/
echo This is stdout
echo This is stderr 1>&2
$ cat /etc/systemd/system/errtest.service
Description=stderr test
$ sudo systemctl start errtest
$ journalctl -u errtest
-- Logs begin at Thu 2015-03-05 22:42:26 CET, end at Mon 2015-09-07 14:40:56 CEST. --
Sep 07 14:39:23 gadget systemd[1]: Started stderr test.
Sep 07 14:39:23 gadget systemd[1]: Starting stderr test...
Sep 07 14:39:23 gadget[8971]: This is stdout
Sep 07 14:39:23 gadget[8971]: This is stderr

There's your stdout and stderr.

All science is either physics or stamp collecting. -- Ernest Rutherford