. i am very pro-austerity and pro-EU/EUROzone, i hope that in the next weeks our current goverment will loose the support so our previous goverment can take control again, continue repaying the loans and you know... do what it must be done. Keep in mind: Greece is a poor state with rich citizens!
So pay your fucking taxes already. There is no way the rest of us are going to subsidize you at the rate of 36 billion euros a year.
(Actually, now we've got you to pay off all the debt you owed to our private banks we're going to throw you to the wolves any day now).
No. systemd read the/proc/cmdline file, a linux interface available to all user-level programs. It also wrote to the system log, a linux interface available to all user level programs running as root. Systemd included no code in the kernel
He would've accepted such changes had the team submitted their work in a way that wasn't broken as it was.
As the systemd team didn't ask for any code to be included in the kernel (then) there was no question of Linus accepting it or not. He claimed he would refuse any code submissions from Kay, who hadn't made any submissions for over a year.
Not only is your interpretation of Linus's feelings absurd:
"When it comes to systemd, you may expect me to have lots of colourful opinions, and I just don't," Torvalds told iTWire in an interview. "I don't personally mind systemd, and in fact my main desktop and laptop both run it.
No, that doesn't really count, as it's outside the scope of the current start-up management. It's not something that could be done with start-up management alone today.
Now of course, if we're allowed to fix the infrastructure, with hindsight there's a lot of things we could/should/would have done differently.
But that's what systemd is about. You can criticise the way they do it, but they are at least trying to fix these problems, rather than denying they exist or throwing up their hands and saying "you can't get there from here".
(By the way, in what way is sd_notify "outside the scope of current start-up management"? systemd is "current start-up management" for lots of us).
Problem is that UNIX services doesn't actually tell you when they're ready to "provide", the init system is based on the notion of having told something to start, not actually having it available.
[...]
Fun fact, systemd doesn't address this either. Well, there are some kluges in the form of initd like behaviour, but by and large its still the old "spawn off a process and cross your fingers"-approach to service provisioning and dependency resolution. Only a lot more complicated for not much improvement.
sd_notify.
At least the systemd people know there is a problem, sysvinit has been burying their heads in the sand for how many years about this?
(The discussion about this on the Devuan mailing list was funny -- people desperately trying to find some way of avoiding saying good things about systemd).
I don't have any real experience or hard data with [ the open source AMD and Nouveau ] drivers, because I've been fearful that working with these open source/reverse engineered drivers would have pissed off each vendor's closed source teams so much that they wouldn't help.
The program may work well for years if you are lucky enough that the data of the dead object (stored on the stack) is not overwritten by something else.
FreeBSD nukes the stack when a stack frame is deallocated? I think not.
And even if they managed both of those, why would Snowden's files include information on human resources? Why would a contractor even have access to that information? Everything that's been leaked has been about technical SIGINT capabilities.
Actually the lesson from systemd is that dependencies have been screwed since the beginning and only "work" by accident.
What systemd is doing is forcing people to deal with the whole "when is a service started" problem that everyone has been sweeping under the carpet. The same problem was also visible in parallel sysvinit (Debian) and Upstart, but to a lesser extent.
I would hardly call Devuan a "failure". They're currently in Alpha, and I'm running it on a system now.
I still don't know what devuan are trying to do. Make a version of Debian Jessie that doesn't use systemd? But Jessie can already be run without systemd. Make a system without libsystemd0? Why?
Slashdot Mirror
. i am very pro-austerity and pro-EU/EUROzone, i hope that in the next weeks our current goverment will loose the support so our previous goverment can take control again, continue repaying the loans and you know... do what it must be done. Keep in mind: Greece is a poor state with rich citizens!
So pay your fucking taxes already. There is no way the rest of us are going to subsidize you at the rate of 36 billion euros a year.
(Actually, now we've got you to pay off all the debt you owed to our private banks we're going to throw you to the wolves any day now).
He's answered that question multiple times. Why bother asking it again? Just because you don't like the answer?
Small parts of systemd have Linux components.
No. Systemd has no kernel code, it uses standard Linux interfaces, open to all. Even if kdbus goes in it will not be reserved to systemd.
Overall, systemd is an extra-kernel computer system management system.
True even without the "overall"
Poettering+team once tried to submit some changes to Linux that broke Linux and Torvalds chewed them out for this.
No. systemd read the /proc/cmdline file, a linux interface available to all user-level programs. It also wrote to the system log, a linux interface available to all user level programs running as root. Systemd included no code in the kernel
He would've accepted such changes had the team submitted their work in a way that wasn't broken as it was.
As the systemd team didn't ask for any code to be included in the kernel (then) there was no question of Linus accepting it or not. He claimed he would refuse any code submissions from Kay, who hadn't made any submissions for over a year.
Isn't SystemD a component of the kernel
No.
Next question?
Not only is your interpretation of Linus's feelings absurd:
-- Linus Torvalds
But your claims of systemd developers "butthurt" are also ridiculous:
-- From the link you posted.
What insurance?
One thing is protesting, and a very different one is actively preventing people from going about their business.
But what if the business you are interfering with is illegal?
Protesters have also blocked access to train stations in Merseille and Aix.
Merseille? Where that?
For example, the Birmingham school district was taken over Islamic extremists
Are you an American?
Yup, 'cos Jesus was real big on killing people and not notably hard on rich people or capitalists.
Connecticut woman arrested after sexual attack on dog results in death
Colorado police issue warrant on Beth Chapman, wife of Dog the Bounty Hunter
Pennsylvania couple accused of having sex with their dog
'Dog the Bounty Hunter's' Lyssa Chapman's book reveals horrific childhood
Great site. News for Nerds indeed.
With current start-up management I meant "as it's defined by history and hence the system we've got to work with".
Ah, by "current" you mean "historical". :-)
Luckily for us software isn't carved in stone.
sd_notify.
No, that doesn't really count, as it's outside the scope of the current start-up management. It's not something that could be done with start-up management alone today.
Now of course, if we're allowed to fix the infrastructure, with hindsight there's a lot of things we could/should/would have done differently.
But that's what systemd is about. You can criticise the way they do it, but they are at least trying to fix these problems, rather than denying they exist or throwing up their hands and saying "you can't get there from here".
(By the way, in what way is sd_notify "outside the scope of current start-up management"? systemd is "current start-up management" for lots of us).
Problem is that UNIX services doesn't actually tell you when they're ready to "provide", the init system is based on the notion of having told something to start, not actually having it available.
[...]
Fun fact, systemd doesn't address this either. Well, there are some kluges in the form of initd like behaviour, but by and large its still the old "spawn off a process and cross your fingers"-approach to service provisioning and dependency resolution. Only a lot more complicated for not much improvement.
sd_notify.
At least the systemd people know there is a problem, sysvinit has been burying their heads in the sand for how many years about this?
(The discussion about this on the Devuan mailing list was funny -- people desperately trying to find some way of avoiding saying good things about systemd).
I don't have any real experience or hard data with [ the open source AMD and Nouveau ] drivers, because I've been fearful that working with these open source/reverse engineered drivers would have pissed off each vendor's closed source teams so much that they wouldn't help.
Which is just fucking great.
Read the message you are replying to:
The program may work well for years if you are lucky enough that the data of the dead object (stored on the stack) is not overwritten by something else.
FreeBSD nukes the stack when a stack frame is deallocated? I think not.
It also appears that the company's drives were enterprise Samsung PROs.
Yeah, right, "enterprise" disks with SATA interfaces. Buy crap, get crap.
Wow, you systemd fanbois are all so rude.
Aw, diddums.
Various(*) anonymous trolls repeatedly lying is not rude?
(* Actually I suspect there is only one troll, he's getting boringly repetitive).
Well spotted:
And even if they managed both of those, why would Snowden's files include information on human resources? Why would a contractor even have access to that information? Everything that's been leaked has been about technical SIGINT capabilities.
This is the reason not to believe the story.
It's using twitters little known CEEFAX gateway.
Actually the lesson from systemd is that dependencies have been screwed since the beginning and only "work" by accident.
What systemd is doing is forcing people to deal with the whole "when is a service started" problem that everyone has been sweeping under the carpet. The same problem was also visible in parallel sysvinit (Debian) and Upstart, but to a lesser extent.
No it is not. It's not the service itself that starts required services, it is systemd that does it.
GigaplexNZ was suggesting that every service start out by starting all the dependencies it requires.
Duh, typo, terminal, not kernel.
I would hardly call Devuan a "failure". They're currently in Alpha, and I'm running it on a system now.
I still don't know what devuan are trying to do. Make a version of Debian Jessie that doesn't use systemd? But Jessie can already be run without systemd. Make a system without libsystemd0? Why?