If they aren't symptomatic they aren't contagious, period.

And carrying a flask of nitroglycerin with you is perfectly safe providing you handle it carefully. Sure thing.

Voters worry about irrelevant issues like

Or the NSA's mass surveillance, the TSA, the Patriot Act, DUI checkpoints, free speech zones, and the countless other things our government does that violates the constitution.

True on slasdhot. Not the case anywhere else as far as I can tell. If I asked 100 in a shopping center whether they are care about having their internet surfing monitored, text messages monitored, phone calls monitored - I would not find one person that cares. Try convincing a BFU to start using encryption in e-mail. Good l luck. All you get is a blank stare (or they report you to authorities). Do you think anybody stops and thinks about containers for bottles at airport security check? Nobody does. Claim "it's for the children" or "it helps to fight terrorism" and you get a free pass with anything. Absolutely anything. Gosh, don't you see that everywhere?

Systemd is modular: ...

Consisting of multiple binaries/libraries is not sufficient to call it modular. Not in my book anyway. What are the options to replace a specific "module" with a different implementation?

In discussions around the Web in the past few months, I've seen who run Linux on their laptops and maybe a VPS or home server.

- there is a link on words "an overwhelming level of support of systemd from Linux users" - and that prompted me to click on that link (in clear violation of /. codex) because I was hoping to see who are these people that overwhelmingly support systemd? (apart from Lennart himself, that is).

All I got was a blog by Paul Venezia claiming that there is "an overwhelming level of support of systemd from Linux users". The links proving that claim are suspiciously missing. The blog itself seem to be be more on the skeptical side too.

So unless I see an overwhelming level of support of systemd from someone that matters and someone who knows what he talks about, then I'm not inclined to take that statement at face value.

Bottom line, unless you have very poor impulse control, not having a credit card is a poor financial decision.

You are assuming that whole world is equally fucked up. (It is fucked up everywhere, but in different ways).

1)Debit cards don't build credit history. This makes it hard to get a car or house loan at good rates.

The rates here are in all time lows (we talk about 2-3% for a house loan). Even if they are not, the ability to pay debts is evaluated here based on other things - such as "are you employed?", "how high is your income?", "how high are your expenses?", "do you have family?", "do you have a guarantor?", "can you provide any collateral?"

2)Credit cards have 0% interest if you pay at the end of the month every month.

The "if" is what bothers me. The bank basically sits there and waits until you make a mistake or run (even temporarily) into troubles where you can't meet the obligations. Then it makes you pay through the nose.

What services does your daemon provide?

?? Does it matter? It answers queries received over the network.

Will it rebind to network interfaces if they change?

Hmm. Can you be more specific? I have problem coming up with scenario where replacing of NIC or changing of MAC/IP address could be handled transparently to the clients.

Does it need to write to disk?

Yes.

Does it need syslog to do logging output?

Does it matter? The typical configuration is to use direct logging to file. Without syslog. On Linux syslog may be used to log startup/shutdown of the daemon. Most likely using logger(1). On other platforms some native solution would be used.

If it crashes, should someone be notified? How? When? How often? Who?

If it crashes, people will notice because they don't get a service the daemon is providing. Immediately. They will notify the administrator and require the service to be restored. The administrator will capture the current logs and storage for investigation and restart the service. For HA systems, there will be failover system.

You start an executable ... What do I need to do to "support an init system"?

[Guessing] Tell it how to start an executable?

That is a solved problem and does not need a new solution of the size of systemd.

The problem with supporting multiple init systems is that each package that provides a daemon needs to support all of them.

The idea that "a daemon needs to support an init system" somehow does not make sense to me. But I'm ready to improve myself and learn. So, please, enlighten me:

Let's say I have a daemon that implements a network server. You start an executable, it reads a config file, opens a socket, listens for connections on some TCP port, reads a command from the socket, sends a reply. It can be shut down with a specific command received via socket connection or perhaps by sending a SIGTERM.

What do I need to do to "support an init system"?

... a bug in Microsoft's Windows operating system has allowed hackers located in Russia to spy on computers used by NATO, Ukraine, the European Union, and others

Did the bug somehow prevent NATO, Ukraine, EU and others from spying on Russia?

Yet it's the expensive name-brand boutique hotels that always charge for wi-fi.

Duh. They did not become name-brand by giving things away (such as cheap rooms or free wi-fi).