They can defund the CIA or particular CIA programs if they want
Oh joy - so they will have to turn back to their old ways of raising funds like selling weapons to terrorists (North and Hezbolla) or drug running. Any solution is going to require extra funding for incarceration of those that choose to continue to act against the state - the sort of thing that used to be called treason before it got more narrowly defined. As an example there is an astonishing amount of effort being put in by these spooks to support a regime (Saudi Arabia) that is both putting money into ISIS/daash and running a deliberate campaign to drive US based oil producers out of business by artificially lowering the oil price. That (the pro-Arab factions) and the the infighting (with pro-Israel factions) of the spooks are examples of spooks having their own policies that are opposed to national policies.
Torturing people is something you'd think is unforgivable but the only one jailed for anything related to that was the whistleblower who refused to torture anyone. So unforgivable has had the bar shifted to somewhere around the ninth circle of Hell, and this thing that should not be forgiven already has been.
It appears sometimes some of them pretend so hard that physical assaults happen. Like it or not, there's a lot of racism about whether a few kids somewhere are "pretending" or not.
That's close to the universal reaction to questions by email. If I have to ask salesfolk multiple questions by email it's always one per email or any later questions are ignored.
Yes, the failed NCOs and Officers who found that either a lack of ability or discipline meant they had hit their peak rank so their best bet was being bullies in private enterprise. They are so full of wind that it's hard to stand up to them but 99% of it is just wind. They give the rest a bad name. See the story of Enron as to how a few of them taken seriously can make a workplace incredibly toxic - the sort of shit the military at least tries not to let happen, but once they are loose and everyone is scared of them anything goes.
So true - I used to struggle to ride a bike up a hill near my house and then coast down the hill at what I thought was high speed. Twenty years later the town where I grew up was flooded and the top of that hill was a full three feet under water - not much of a hill really. "Miles" when you are small is typically one or two since everything is so big. Anyway, the point that we have a lot of scared parents around is valid and such a "free-range" upbringing in cities is something more likely from recent migrants than the mainstream.
True, but people actually did read manuals and do training courses a few years ago, while now users are expected to dive in at the deep end and bother hardware support folks if they want to have two MS Excel spreadsheets on their screen at the same time (or similar trivialities). There does appear to be something more concrete than "kids these days", especially since older users new to office computing are as bad or worse.
Fair enough, but going around "correcting" people with a concept that relies on negative mass looks like the sort of certainty that reduces with increased understanding of a topic. Also, if space isn't curved then where are we getting all that background heat from? There's a vast amount of it, 3K just about everywhere needs a bit of warming up, and if it's not being bounced back at us then where is it coming from?
Because you seem to be massively underestimating the amount of "little devices with a CPU" in existance which couldn't even run a fragment of busybox
I merely underestimated the devices you could think of (before your goalpost shift my words were "just about every little device with a CPU you can think of") based on what appeared to me a naive view in your rebuttal above. If you wish to be truthful you have to admit that there are a very large number of commercial devices with busybox on them. It doesn't have to be everything with a CPU to be enough to make my point of there being a lot of GPL stuff out there in commercial use does it?
You said it didn't get used commercially, I gave a couple of real examples where it is being used commercially. Surely that's enough to avoid snide crap about anecdotes and goalpost shifting insults such as 'you seem to be massively underestimating the amount of "little devices with a CPU" in existance'? If it isn't, well that's just showing you have a barrow to push and an any means to an ends attitude doesn't it?
Good question, but a better one is why doesn't the bug turn up when systemd is not the thing calling the shots but it turned up every time when it was systemd in control. A lack of effective logging makes that a difficult thing to answer, so my approach is I'll try again when the project is mature enough that something could be done to debug it such as the stepping through stages of init that is in the system it desires to replace. On CentOS6 it would be trivial to step through and see where it halts - Fedora with systemd, well such a feature is not required because systemd was apparently perfect upon conception.
XP Mode was developed 7+ years ago under Balmer... MS today is clearly a different company...
Actually that's my theory as to why every second version of an MS operating system is fucked up in some way - learning curve after they've gotten rid of the staff who got the last one right. MS should have a lot of 60 year old project leads and 40 year old developers at the "foreman" level by now, but they don't so there's a lot of wheel re-invention going on by people out of their depth.
The smoking gun was a few posts above: hangs on init repeatedly - remove device, doesn't hang - insert device after systemd has pissed off out of the way and lo, and behold, udev and the kernel get their shit together and use the device with no problems. I think it's just a little bit disgusting that you are ignoring that for the purpose of evangelism and treating me like an idiot that can't see what you are doing.
And why did you complain on systemd not displaying something if the problem is completely unrelated to systemd
Well I don't know do I? The system fails to initialise when the init system has the floor and there is no output - kernel panics often at least get to put something on the screen and no output plus no log is a bit of a clue that it's yet another systemd hang, just like the no output and no logs other people have when systemd halts. Maybe it isn't - in which case I can cross it off the growing list, but it's just the latest thing that happens to be as recent as this week. I haven't given up, I run fedora on my home system despite various hassles (eg. see systemd and ZFS startup problems for an example) but I'm not impressed. It's the early days of pulseaudio and networkmanager all over again from when they were rushed out before they were ready. That can be swallowed up to a point, but the insistence that the old thing is rubbish and the new unfinished thing is perfect so don't dare question it is grating.
An unknown device on USB should not being a "parallel" init system to a halt, the relevant process should just fail gracefully and the next thing should get going. However a house of cards instead of branching events is going to be fragile by design isn't it? One little bit missing and it's all over. It's looks like a bit more effort to make it as parallel as it pretends is in order.
SAP systems are not protected from cyber threats by traditional security approaches
That implies that there is some sort of protection while leaving out the word "traditional" implies the more correct situation where they are not protected at all. That not necessarily a bad thing so long as the practice is to secure their stuff with third party approaches afterwards (eg. need to get on a secured VPN before you can communicate with the software).
Considering the state of "XP mode" now I can't see any MS support of such an idea as being any better than the kludge of using Virtualbox today. Something library based along the lines of WINE to run the old stuff is also possible but I really don't think they'll get any commercial payoff so I cannot see them bothering. So IMHO the "future plan" is to ignore the problem and expect anyone with the problem to sort it out themselves.
Considering some stuff in use where I work which will not even run in Win8 yet I suppose it's a matter of only patching up to two or three years behind the current date. Yes that is stupid but that's the speed (or lack thereof) of development with some software.
He was interested in imaging the Calcium, it should be obvious that the other elements I mentioned would be a bit harder, but it may not to some readers or may be seen as an opening for nitpickers to prove some sort of point. By that point in time I think Tungsten and other relatively large atoms could be resolved so that's what I meant by "unlike larger atoms"
Yes, in the 1990s I listened to a presentation by someone imaging material in the roots of teeth which contained mostly Ca, H and O and he complained that unlike larger atoms the Ca could not be imaged directly with a TEM so he digitally generated defocused images for a range of possible structures to see what would match the images from the real sample with as close a focus as he could get. Interesting stuff.
how can you be certain that systemd is the fundamental cause of your problem ?
You are correct - systemd's lack of output and logging at that came to the rescue so it is absolved of blame! It's not that I hate it. It's just that I would prefer it to be beyond alpha quality before I use it.
Did you a least report the problem
I've seen how people who report systemd problems are treated so no, I'd rather avoid it than get into a shouting match with someone who perceives wishes that they get what they deserve someday as death threats. It's easier to decide not to use that bit of cheap hardware and move on - or install CentOS6 for a more stable environment that was tested a bit instead of rushed out by sheer force of ego.
Actually I think this "friday night fight" thing has been set up so that entitled little weenies can write about how their penis makes them better at IT than women. I chose to do something different with my penis other than being good at IT. While the "feminism is threatening my job and stopping me getting laid" rant may make you feel better it has very little relation to reality. IT an industry where the women were kicked out as soon as there was seen to be money in it, and now I see more women even in the mining industry than IT. Your rants about feminism are kicking the cat instead of addressing those who actually have some power to change things, I can see that with only an outsiders glimpse of the issue and I suggest you at least get up to speed with the average high school student on the issue.
Here it is from 1995 http://www.spacebanter.com/archive/index.php?t-24091.html
Microwave ovens are detectable at distances of many kilometers by
radio telescopes. They are not really a problem for SETI since thier
emission is very broadband by our standards. Our detection systems do
not see them. However, back in 1995 at the Parkes observatory, we
noticed broadband interference on our spectrum displays. Again, I
emphsize this was not detected by the search system. The interference
seemed to occur most often at breakfast and dinner times. There was a
microwave oven on site (since very little radio astronomy is done at
those frequencies). We made a cup of tea in the microwave and sure
enough, it produced the same pattern of broad interference. So, the
broad interference at ~2400 MHz was indeed emission from microwave
ovens at distances greater than 5 km. And it was coming in the
sidelobes.
It's also an ilustration of how usage of the spectrum has increased in
recent years. At Parkes in 95 and Green Bank in 96-98, we were able
to observe much of the spectrum that now has to be filtered to protect
the receiver.
The recent articles mentioned microwave ovens as an illustration of
how widespread radio emitters are in society. Your example of
wireless networks is another good one. Although all radio emitting
devices have specific frequency assignments, and limits on their out
of band emissions, radio telescopeshttp://www.independent.co.uk/news/science/seti-the-hunt-for-et-1793984.html
are very, very sensitive and can
often pick up those out of band emissions.
Since nothing related was logged or echoed to the screen (there was a PulseAudio message but that's all) all I know is it hung until I came back and rebooted it, then hung again a second time. The third time I pulled the dongle until it had got as far as X then plugged the dongle back in. Fine since then on that Fedora desktop. So I very much doubt it's udev alone since it's worked the couple of times since so long as I plug it in after it's made it to the X runlevel (or whatever it's called in systemd). That's just the latest of a list of things that have convinced me systemd just is not ready to be shipped in distros yet despite whatever is decided with Redhat and Gnome office politics.
Seriously? It fails on so many of those points - "simple parts connected by clean interfaces" and "Design for visibility to make inspection and debugging easier" for a start. It's introducing MS style voodoo debugging where you just have to keep unplugging things until the machine boots because nothing on the screen is going to tell you anything.
Slashdot Mirror
Oh joy - so they will have to turn back to their old ways of raising funds like selling weapons to terrorists (North and Hezbolla) or drug running.
Any solution is going to require extra funding for incarceration of those that choose to continue to act against the state - the sort of thing that used to be called treason before it got more narrowly defined.
As an example there is an astonishing amount of effort being put in by these spooks to support a regime (Saudi Arabia) that is both putting money into ISIS/daash and running a deliberate campaign to drive US based oil producers out of business by artificially lowering the oil price. That (the pro-Arab factions) and the the infighting (with pro-Israel factions) of the spooks are examples of spooks having their own policies that are opposed to national policies.
Torturing people is something you'd think is unforgivable but the only one jailed for anything related to that was the whistleblower who refused to torture anyone. So unforgivable has had the bar shifted to somewhere around the ninth circle of Hell, and this thing that should not be forgiven already has been.
It appears sometimes some of them pretend so hard that physical assaults happen.
Like it or not, there's a lot of racism about whether a few kids somewhere are "pretending" or not.
That's close to the universal reaction to questions by email.
If I have to ask salesfolk multiple questions by email it's always one per email or any later questions are ignored.
Yes, the failed NCOs and Officers who found that either a lack of ability or discipline meant they had hit their peak rank so their best bet was being bullies in private enterprise. They are so full of wind that it's hard to stand up to them but 99% of it is just wind. They give the rest a bad name. See the story of Enron as to how a few of them taken seriously can make a workplace incredibly toxic - the sort of shit the military at least tries not to let happen, but once they are loose and everyone is scared of them anything goes.
So true - I used to struggle to ride a bike up a hill near my house and then coast down the hill at what I thought was high speed. Twenty years later the town where I grew up was flooded and the top of that hill was a full three feet under water - not much of a hill really. "Miles" when you are small is typically one or two since everything is so big.
Anyway, the point that we have a lot of scared parents around is valid and such a "free-range" upbringing in cities is something more likely from recent migrants than the mainstream.
True, but people actually did read manuals and do training courses a few years ago, while now users are expected to dive in at the deep end and bother hardware support folks if they want to have two MS Excel spreadsheets on their screen at the same time (or similar trivialities).
There does appear to be something more concrete than "kids these days", especially since older users new to office computing are as bad or worse.
Fair enough, but going around "correcting" people with a concept that relies on negative mass looks like the sort of certainty that reduces with increased understanding of a topic.
Also, if space isn't curved then where are we getting all that background heat from? There's a vast amount of it, 3K just about everywhere needs a bit of warming up, and if it's not being bounced back at us then where is it coming from?
I merely underestimated the devices you could think of (before your goalpost shift my words were "just about every little device with a CPU you can think of") based on what appeared to me a naive view in your rebuttal above. If you wish to be truthful you have to admit that there are a very large number of commercial devices with busybox on them. It doesn't have to be everything with a CPU to be enough to make my point of there being a lot of GPL stuff out there in commercial use does it?
You said it didn't get used commercially, I gave a couple of real examples where it is being used commercially. Surely that's enough to avoid snide crap about anecdotes and goalpost shifting insults such as 'you seem to be massively underestimating the amount of "little devices with a CPU" in existance'? If it isn't, well that's just showing you have a barrow to push and an any means to an ends attitude doesn't it?
Good question, but a better one is why doesn't the bug turn up when systemd is not the thing calling the shots but it turned up every time when it was systemd in control.
A lack of effective logging makes that a difficult thing to answer, so my approach is I'll try again when the project is mature enough that something could be done to debug it such as the stepping through stages of init that is in the system it desires to replace.
On CentOS6 it would be trivial to step through and see where it halts - Fedora with systemd, well such a feature is not required because systemd was apparently perfect upon conception.
Actually that's my theory as to why every second version of an MS operating system is fucked up in some way - learning curve after they've gotten rid of the staff who got the last one right.
MS should have a lot of 60 year old project leads and 40 year old developers at the "foreman" level by now, but they don't so there's a lot of wheel re-invention going on by people out of their depth.
The smoking gun was a few posts above: hangs on init repeatedly - remove device, doesn't hang - insert device after systemd has pissed off out of the way and lo, and behold, udev and the kernel get their shit together and use the device with no problems.
I think it's just a little bit disgusting that you are ignoring that for the purpose of evangelism and treating me like an idiot that can't see what you are doing.
Well I don't know do I? The system fails to initialise when the init system has the floor and there is no output - kernel panics often at least get to put something on the screen and no output plus no log is a bit of a clue that it's yet another systemd hang, just like the no output and no logs other people have when systemd halts.
Maybe it isn't - in which case I can cross it off the growing list, but it's just the latest thing that happens to be as recent as this week.
I haven't given up, I run fedora on my home system despite various hassles (eg. see systemd and ZFS startup problems for an example) but I'm not impressed. It's the early days of pulseaudio and networkmanager all over again from when they were rushed out before they were ready. That can be swallowed up to a point, but the insistence that the old thing is rubbish and the new unfinished thing is perfect so don't dare question it is grating.
An unknown device on USB should not being a "parallel" init system to a halt, the relevant process should just fail gracefully and the next thing should get going. However a house of cards instead of branching events is going to be fragile by design isn't it? One little bit missing and it's all over. It's looks like a bit more effort to make it as parallel as it pretends is in order.
That implies that there is some sort of protection while leaving out the word "traditional" implies the more correct situation where they are not protected at all.
That not necessarily a bad thing so long as the practice is to secure their stuff with third party approaches afterwards (eg. need to get on a secured VPN before you can communicate with the software).
Considering the state of "XP mode" now I can't see any MS support of such an idea as being any better than the kludge of using Virtualbox today. Something library based along the lines of WINE to run the old stuff is also possible but I really don't think they'll get any commercial payoff so I cannot see them bothering.
So IMHO the "future plan" is to ignore the problem and expect anyone with the problem to sort it out themselves.
Considering some stuff in use where I work which will not even run in Win8 yet I suppose it's a matter of only patching up to two or three years behind the current date. Yes that is stupid but that's the speed (or lack thereof) of development with some software.
He was interested in imaging the Calcium, it should be obvious that the other elements I mentioned would be a bit harder, but it may not to some readers or may be seen as an opening for nitpickers to prove some sort of point. By that point in time I think Tungsten and other relatively large atoms could be resolved so that's what I meant by "unlike larger atoms"
Yes, in the 1990s I listened to a presentation by someone imaging material in the roots of teeth which contained mostly Ca, H and O and he complained that unlike larger atoms the Ca could not be imaged directly with a TEM so he digitally generated defocused images for a range of possible structures to see what would match the images from the real sample with as close a focus as he could get.
Interesting stuff.
So examples are worthless now are they? Sorry about being "reality based".
You are correct - systemd's lack of output and logging at that came to the rescue so it is absolved of blame!
It's not that I hate it. It's just that I would prefer it to be beyond alpha quality before I use it.
I've seen how people who report systemd problems are treated so no, I'd rather avoid it than get into a shouting match with someone who perceives wishes that they get what they deserve someday as death threats. It's easier to decide not to use that bit of cheap hardware and move on - or install CentOS6 for a more stable environment that was tested a bit instead of rushed out by sheer force of ego.
Actually I think this "friday night fight" thing has been set up so that entitled little weenies can write about how their penis makes them better at IT than women. I chose to do something different with my penis other than being good at IT.
While the "feminism is threatening my job and stopping me getting laid" rant may make you feel better it has very little relation to reality. IT an industry where the women were kicked out as soon as there was seen to be money in it, and now I see more women even in the mining industry than IT. Your rants about feminism are kicking the cat instead of addressing those who actually have some power to change things, I can see that with only an outsiders glimpse of the issue and I suggest you at least get up to speed with the average high school student on the issue.
http://www.spacebanter.com/archive/index.php?t-24091.html
Since nothing related was logged or echoed to the screen (there was a PulseAudio message but that's all) all I know is it hung until I came back and rebooted it, then hung again a second time. The third time I pulled the dongle until it had got as far as X then plugged the dongle back in. Fine since then on that Fedora desktop.
So I very much doubt it's udev alone since it's worked the couple of times since so long as I plug it in after it's made it to the X runlevel (or whatever it's called in systemd).
That's just the latest of a list of things that have convinced me systemd just is not ready to be shipped in distros yet despite whatever is decided with Redhat and Gnome office politics.
This has zero to do with feminism apart from your attempted use as a blunt instrument to bash it.
Seriously? It fails on so many of those points - "simple parts connected by clean interfaces" and "Design for visibility to make inspection and debugging easier" for a start.
It's introducing MS style voodoo debugging where you just have to keep unplugging things until the machine boots because nothing on the screen is going to tell you anything.