Eunuchswear - Slashdot User

Comment Re:Choose init during installation? (Score 2) 442

by Eunuchswear on Sunday April 26, 2015 @04:50AM (#49553997) Attached to: Debian 8 Jessie Released

Just did an install in a vm. No. There is no option to choose an init system. systemd is default. If you want to use sysvinit, you have to do it via a pre-install script which basically means, netinstall.

Why just netinstall? The instructions I've seen on the web say: https://wiki.debian.org/systemd#Installing_without_systemd

If not using a preseed file, this can be added to the boot arguments instead by hitting TAB at the boot menu on the desired entry and appending the above preseed line at the end of the boot command.

That doesn't work?

Comment Re:Debian Systemd SJWs (Score 1) 442

by Eunuchswear on Sunday April 26, 2015 @04:42AM (#49553987) Attached to: Debian 8 Jessie Released

1 vote decided for the systemd takeover in debian.
There was a split 4-4 vote in the debian technical comittie.
Which was then tie-broken by the chair who just happened to be a rabid force-it-down-your-throght supporter.

No, that's not what happened. The vote was: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727708#6729

4x D U O V F (bdale, russ, keith, don)
F U D O V (steve)
U D O F V (colin)
F V O U D (ian)
U F D O V (andi)

So 4 people wanted systemd, or upstart, or openrc, or even sysvinit but lets stop the boring wrangling,
3 people wanted upstart, or systemd, or openrc, or sysvinit
and one wanted sysvinit, or basicly anything but systemd.

There was no 4-4 split.

As for your insane frothing about SJW's, fuck off you paedophile moron.

Comment Re:Systemd wins nothing (Score 1) 442

by Eunuchswear on Sunday April 26, 2015 @04:32AM (#49553959) Attached to: Debian 8 Jessie Released

Of course you could just read the summary and realize that a Debian can be "a distro that doesn't use systemd".

Comment Re:Finally, one init again (Score 1) 494

by Eunuchswear on Saturday April 25, 2015 @07:56AM (#49550189) Attached to: Ubuntu 15.04 Released, First Version To Feature systemd

You'd think half Slashdot was born before 1960 and learned some traditional UNIX before there even was a Linux, the way they carry on whenever anything changes

I was born before 1960 and started to use Unix around SVR3.0 before there even was a Linux.

I quite like systemd.

Comment Re:Some truths (Score 1) 494

by Eunuchswear on Saturday April 25, 2015 @07:49AM (#49550183) Attached to: Ubuntu 15.04 Released, First Version To Feature systemd

Not portable? Who even cares when systemd doesn't even run on linux in most cases. Think phone tablet embedded non glibc. The biggest use case for linux already excludes systemd.

My phone runs systemd fine.

But then my phone runs Linux, not Android.

Comment Re: systemd rules!!! (Score 1) 494

by Eunuchswear on Saturday April 25, 2015 @07:36AM (#49550169) Attached to: Ubuntu 15.04 Released, First Version To Feature systemd

you have to do a "systemctl reload" after stopping the service and before restarting it.

Sorry, I mean "systemctl daemon-reload" of course.

Comment Re:systemd, eh? (Score 1) 494

by Eunuchswear on Saturday April 25, 2015 @07:11AM (#49550103) Attached to: Ubuntu 15.04 Released, First Version To Feature systemd

I'm completely stumped, so I welcome any suggestions at this point.

I suppose you've checked out https://wiki.archlinux.org/index.php/Power_management

Comment Re:systemd, eh? (Score 1) 494

by Eunuchswear on Saturday April 25, 2015 @07:07AM (#49550087) Attached to: Ubuntu 15.04 Released, First Version To Feature systemd

Also the sleep key works fine

By which you mean? What happens when you press the sleep key?

Comment Re:Cannot reproduce your test case (Score 1) 494

by Eunuchswear on Saturday April 25, 2015 @06:25AM (#49550039) Attached to: Ubuntu 15.04 Released, First Version To Feature systemd

That's not what I see on RHEL7

But it is exactly what I see on CentOS 7. How odd.

Type=oneshot

Where is this documented? I didn't see it in the man page for systemd, systemd.unit, systemctl, etc. or any other commands listed in the "SEE ALSO" sections of those commands.

man systemd.service

In man systemd I see:

The following unit types are available:

1. Service units, which start and control daemons and the processes
they consist of. For details see systemd.service(5).

[...]

SEE ALSO
The systemd Homepage[9], systemd-system.conf(5), locale.conf(5),
systemctl(1), journalctl(1), systemd-notify(1), daemon(7), sd-
daemon(3), systemd.unit(5), systemd.special(5), pkg-config(1), kernel-
command-line(7), bootup(7), systemd.directives(7)

And in systemd.directives there is:

Type=
systemd.mount(5), systemd.service(5)

Comment Re:systemd rules!!! (Score 1) 494

by Eunuchswear on Saturday April 25, 2015 @06:13AM (#49550013) Attached to: Ubuntu 15.04 Released, First Version To Feature systemd

"shit" does happen. What is interesting about the whole systemd thing is that there are a class of people, all posting AC, why lie about what happens.

I'd love to know why. I can understand that people don't like some software, but why would they flat out lie about what that software does?

How do I know these claims are lies? Because they are all posted AC, because nobody has ever claimed to have reported these defective behaviours as bugs, because I can't reproduce them even when using exactly the same environments and commands as the claimant.

Comment Re: systemd rules!!! (Score 1) 494

by Eunuchswear on Saturday April 25, 2015 @06:06AM (#49549993) Attached to: Ubuntu 15.04 Released, First Version To Feature systemd

I did try it, and reproduced the his results on Fedora 21.

That's very interesting, you're the first non-ac to report this.

Care to show me exactly what you did?

If you took the recipe given by the ac:

It is trivial to reproduce this serious problem with systemd. Pick any script in /usr/lib/systemd/*.service:

# append --broken to ExecStart line vi /usr/lib/systemd/system/named.service systemctl stop named systemctl start named

Then maybe you missed the fact that systemd doesn't re-read unit files for existing services, you have to do a "systemctl reload" after stopping the service and before restarting it. (You should have got a message warning you of this, but many people seem to misunderstand the message).