Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror

Comment: Re: systemd sux (Score 1) 368

by Eunuchswear (#49556533) Attached to: Debian 8 Jessie Released

First, most modern Linux systems come without an inetd or xinetd, because they have no services which aren't supplied by long-running daemons.

Please name a modern Linux system that comes without [x]inetd.

Second, inetd won't listen on things it doesn't need to listen on, let alone xinetd.

Neither will systemd. As I said above on my system with no xxx.socket units systemd is not listening on any socket.

Comment: Re:Too much noise over SystemD (Score 1) 368

by Eunuchswear (#49556369) Attached to: Debian 8 Jessie Released

would be easy to replicate and should be reported as a major bug

The devs don't care. These issues have been reported.

No they haven't. There is no bug report for any of these ficticious problems.

Like the binary log corruption bug. After over 1 year of sitting, the bug got closed with a "working as intended" and dev border-lining lambasting the submitter. I can understand that a file can get corrupted because of faulty hardware or an FS bug, whatever. What I don't understand is how someone designs something as critical as a log to be non-atomic and easily get corrupted from an unexpected shutdown because it's designed that way.
 

What bug is that exactly? The bug where if the journal is closed incorrectly a new one will be opened to avoid losing messages?

Comment: Re:Too much noise over SystemD (Score 1) 368

by Eunuchswear (#49554457) Attached to: Debian 8 Jessie Released

I dont understand why in earth you are both posting as ACs in such an important matter.

Because they are lying.

systemd has bugs and implementation decisions that some people don't like, but, wierdly, there is a strange subculture of trolls who like to complain about systemd "throwing away output and exit statuses", behaviour which, if true, would be easy to replicate and should be reported as a major bug.

But no non-AC has ever been able to replicate the problem, and no bug report about this behaviour has ever been made.

Comment: Re:Debian Systemd SJWs (Score 1) 368

by Eunuchswear (#49554423) Attached to: Debian 8 Jessie Released

I consider a great majority of women as 'peculiar', twisted, crazy, psychotic and have their own agendas which reflects their particular form of insanity and unreasonableness. Blame it on their hormones or upbringing or whatever. I just don't care anymore.
There is a women against feminism group I heard

But are they more or less reasonable than wierd kiddy-fiddlers who claim that SJW's and "transgenders" are the only thing stopping them marrying "young girls".

Comment: Re:Debian Systemd SJWs (Score 0) 368

by Eunuchswear (#49554417) Attached to: Debian 8 Jessie Released

Fuck these people. SJW pieces of shit.
(Same type people banned marrying young girls everywhere, also look at planet.debian.org during the systemd debate: transgender this, women that, bla bla bla. fucking pieces of shit ruin everything good)

Since many places let you marry girls as young as 15 years old (E.G. Mexico) just how young do you like them?

As long as you're into post-puberty you could try Yemen. Watch out for the drones.

Comment: Re:systemd sux (Score 1) 368

by Eunuchswear (#49554011) Attached to: Debian 8 Jessie Released

You mean untested, unaudited code that is forced into production environments? Code that has full network access as root?

So, what systemd things have access to the network?

#netstat -naput | grep systemd
udp 0 0 0.0.0.0:54562 0.0.0.0:* 24001/systemd-times
# ps -fp 24001
UID PID PPID C STIME TTY TIME CMD
systemd+ 24001 1 0 Apr09 ? 00:00:00 /lib/systemd/systemd-timesyncd

Not running as root, running as user "systemd-timesyncd"

 

Harrison's Postulate: For every action, there is an equal and opposite criticism.

Working...