I am interested in this too. I have seen both LED bulbs and strips die, both with the same failure mode - a low-intensity flicker. In the former case I'm almost certain it's the ballast (cheap chinese capacitors), but I have no idea how the strip that takes 12V would fail assuming it's not being over-driven.
The diode junctions should last for many thousands of hours if driven with the correct current.
Funnily enough I think flying cars could be a better target for automation than those disastrous ground-based driverless cars.
The problem space is much more defined in the air than on the ground and, given that it's difficult for a human to look in all directions at once or judge distances of rapidly approaching objects, should probably be mandatory.
A while ago someone here compared Systemd to the MCP in the disney film Tron. Having re-watched that movie recently I have to admit they were right on the money.
Guess what doesn't happen on my server? Yes, random hardware appearing and disappearing while it sits there for years running one app.
Really? You don't change disks in your server or plug in USB keyboards? That must be nice for you, but there are cases where the state of a server will definitely change. Think hot-swappable CPUs, RAM, USB-controlled UPS's.
Look, I think systemd is a terrible kludge and the wrong solution to the issue but I do not think assuming a constant-state computer is a realistic or particularly useful design objective.
Well okay, but patches are available for the major Linux distributions. One apt-get and it's fixed.
From Apple? Nothing. You need to download the source for bash, download a patch, compile it yourself (after making sure you have a fully functional XCode) and manually copy it over the existing binary.
I'm not sure that's the kind of Thinking Different they were talking about.
Standard LAMP server for my environment monitoring, shared Calendar (davical, sync'd to Android gadgets, desktops, etc), data storage, web applications, email (getmail, postfix, dovecot, roundcube), etc.
Backup server (in another room from the first server), switched on by WoL each day, slurps data from server with rsync w/archival backup, waits a few minutes then shuts down.
10/100/1000 Mbps switch ADSL modem 802.11n Access Point
That's about it from the top of my head. The server is over 12 years old and still going strong. And it draws about 50 watts. The backup server is a much more modern machine, but its power draw is negligible since it's only on for about 20 minutes per day.
What you say may well be correct, but not necessarily relevant. You always have a choice to turn off your phone, or at least turn off GPS and other location services.
These insidious "connected" vehicles will not give a choice. Want to travel by car? Get tracked or get out.
The star in question is Barnard's Star, a red dwarf.
Pulsar PSR B1257+12 was credited in the summary as an example at the start of the modern explosion in discovering extrasolar planets, not the one that was mistakenly thought to have planets.
Don't forget the awesome single-player three-monitor gameplay experience that was present in early versions of Doom 1. Sure you needed three computers to do it, but AFAIK no other PC game could do that.
Why do these successful companies allow themselves to be bought up by behemoths who almost never improve upon them? Is it just so the current owners can retire?
Especially Microsoft, whose modus operandi has been shown again and again to be embrace, extend, extinguish.
We could somewhat control the effects of global warming with a large array of satellites that unfolded large solar panels like big umbrellas to divert sunlight otherwise destined for Earth, controlled to keep the Earth within a desired temperature range.
I'm not saying it's practical at all, but it is within our means.
I guess to test it you would do just what you described, but with an added control - three points chosen randomly (on a map, preferably by a computer RNG). After enough repetitions you could build up a confidence interval to determine whether you could reject the null hypothesis (that the spots marked by dowsing lead to no more water than the random ones).
Slashdot Mirror
I am interested in this too. I have seen both LED bulbs and strips die, both with the same failure mode - a low-intensity flicker. In the former case I'm almost certain it's the ballast (cheap chinese capacitors), but I have no idea how the strip that takes 12V would fail assuming it's not being over-driven.
The diode junctions should last for many thousands of hours if driven with the correct current.
Funnily enough I think flying cars could be a better target for automation than those disastrous ground-based driverless cars.
The problem space is much more defined in the air than on the ground and, given that it's difficult for a human to look in all directions at once or judge distances of rapidly approaching objects, should probably be mandatory.
Please don't confuse disruptive innovations with forward-thinking ones.
For the record, I agree with you. I was more criticizing the mindset that said a Linux server could be considered static between boots.
Linux still has a long way to go in terms of hot-plugging (USB graphics cards, additional monitors, NICs), but systemd is not the solution.
It's buried there in the word "unreasonable".
A while ago someone here compared Systemd to the MCP in the disney film Tron. Having re-watched that movie recently I have to admit they were right on the money.
The resemblance is very disturbing.
Guess what doesn't happen on my server? Yes, random hardware appearing and disappearing while it sits there for years running one app.
Really? You don't change disks in your server or plug in USB keyboards? That must be nice for you, but there are cases where the state of a server will definitely change. Think hot-swappable CPUs, RAM, USB-controlled UPS's.
Look, I think systemd is a terrible kludge and the wrong solution to the issue but I do not think assuming a constant-state computer is a realistic or particularly useful design objective.
Yes, and so what? Why is this a problem?
Sorry is that meant to be an apostrophe or a comma?
It's not very helpful focusing on the fact he was looking at an iPad. It could have just as easily been a cell phone or a magazine.
You mean those same collection agencies whose bread and butter comes from finance companies? One of those collection agencies?
A dead-man's kill switch. Nice, in a morbid do-not-want kind of a way.
Remote kill switches should be illegal.
Well okay, but patches are available for the major Linux distributions. One apt-get and it's fixed.
From Apple? Nothing. You need to download the source for bash, download a patch, compile it yourself (after making sure you have a fully functional XCode) and manually copy it over the existing binary.
I'm not sure that's the kind of Thinking Different they were talking about.
And still posters on /. try to justify these abominations. When will you people get it into your thick heads?
Remote kill switches are a BAD THING.
It's times like this that I'm glad that I use Debian exclusively for headless servers that never see a GUI.
Standard LAMP server for my environment monitoring, shared Calendar (davical, sync'd to Android gadgets, desktops, etc), data storage, web applications, email (getmail, postfix, dovecot, roundcube), etc.
Backup server (in another room from the first server), switched on by WoL each day, slurps data from server with rsync w/archival backup, waits a few minutes then shuts down.
10/100/1000 Mbps switch
ADSL modem
802.11n Access Point
That's about it from the top of my head. The server is over 12 years old and still going strong. And it draws about 50 watts. The backup server is a much more modern machine, but its power draw is negligible since it's only on for about 20 minutes per day.
What you say may well be correct, but not necessarily relevant. You always have a choice to turn off your phone, or at least turn off GPS and other location services.
These insidious "connected" vehicles will not give a choice. Want to travel by car? Get tracked or get out.
No thanks.
With respect, that's a very selfish position and an incredibly naive justification (that you'd probably find a second way to cure cancer).
Not all of us come with a price.
The star in question is Barnard's Star, a red dwarf.
Pulsar PSR B1257+12 was credited in the summary as an example at the start of the modern explosion in discovering extrasolar planets, not the one that was mistakenly thought to have planets.
So with the slow yet inevitable leakage of helium, what will be the estimated lifetime of these drives?
Planned obsolescence, anyone?
Don't forget the awesome single-player three-monitor gameplay experience that was present in early versions of Doom 1. Sure you needed three computers to do it, but AFAIK no other PC game could do that.
Why do these successful companies allow themselves to be bought up by behemoths who almost never improve upon them? Is it just so the current owners can retire?
Especially Microsoft, whose modus operandi has been shown again and again to be embrace, extend, extinguish.
We could somewhat control the effects of global warming with a large array of satellites that unfolded large solar panels like big umbrellas to divert sunlight otherwise destined for Earth, controlled to keep the Earth within a desired temperature range.
I'm not saying it's practical at all, but it is within our means.
It's where all your stuff is.
I guess to test it you would do just what you described, but with an added control - three points chosen randomly (on a map, preferably by a computer RNG). After enough repetitions you could build up a confidence interval to determine whether you could reject the null hypothesis (that the spots marked by dowsing lead to no more water than the random ones).