Which is precisely where apple (usually) succeeds and others fail. Apple would NEVER have released a product in the same state Amazon released the Fire. Generally speaking (and there are most certainly exceptions,) Apple won't release a product until it's "done." Other tech companies really should learn from this example.
I'm often stunned by the crap that modern "consumers" are willing to accept.
Mock us if you want, non-believer, but your "photons" are a load of bunk. Darkons dominate the universe, and those things you call "light sources" are nothing more than darkon attractors. The math proves it.
Just use a bandsaw to cut off the spine and feed it through a normal scanner with a sheet feeder. Duh. Faster, cheaper, and better results along the spine.
I've heard of destroying CRTs for security purposes, but not for modern tubes and not for office systems. I believe that the practice originated in old-style CAD displays where burn in was extremely common.
I agree with you that it's extreme overkill, but it's not completely paranoid. Shooting them sounds like the worst possible way of destroying a display, though. Aren't there CRT recycling centers that would accomplish exactly the same thing?
Is there some good reason not to fry the bacon in itself?
Yes. Flavor. And to see if you can make your heart explode.
I used to make the eggs sunny-side-up and melt cheddar cheese over the top, but it ruined the "soupy mess" effect of the syrup, butter, and yolks. For some extra yolk in your soupy mess, go sunny side up instead of over-easy. It's really easy to completely solidify the yolks if you go over-easy, too, so I sometimes go sunny-side anyway. Oh yeah, and remember to get all of the solids out of your grease before cooking your eggs... crunchy carbon in the eggs just isn't tasty.
Warning: Only to be used sparingly. Excessive usage WILL kill you.
Two strips bacon, fried in butter (not margarine, sissy boy)
Two strips sausage, fried in bacon grease and butter from above
4 eggs over-easy, cooked in bacon grease, sausage fat, and butter from above. Yolks should be slightly runny.
Two waffles, buttered. Syrup to be applied in large quantities (see below)
Hash browns or grits
a biscuit, buttered
1 cup coffee
1 large glass orange juice
The excess melted butter, syrup, and egg yolks should be allowed to mingle. The resulting soupy mess should be eaten mixed with the hash browns. The biscuit can be used to mop up any remaining liquid.
This should not be eaten on a regular basis. I use it before a long day of hard outdoor work, like felling trees, hauling timber, pouring concrete, etc.. Anything where I expect to burn a huge number of calories.
Actually, the windows version is annoying, clunky, and makes my head hurt. I prefer the UNIX (and now Linux) versions because so much can be done from the command line when necessary. With Networker on UNIX, you can just use wrapper scripts around the basic commands if the GUI doesn't work for you. For large or complex recoveries, CLI is really the best way to go, anyway.
Sounds like a problem with your staging policy. Make sure the stage itself is enabled and make sure the destination pool is correct. Does manual staging work?
Slashdot isn't really a networker support forum... feel free to email me at skroz at skroz dot net, if you'd like.
I've been using Legato (now EMC) Networker at a number of different sites for over ten years now. It's easy, reliable, and supports a wide range of hardware. It scales well, but can get quite expensive when you start adding large autoloaders into the mix.
Their site should get you started. They'll set you up with a media kit and 45 day demo licenses if you request one.
Amavisd-new has had p0f support for detecting the OS of the sending mail server for quite some time. It detects the OS type of the incoming mail connection and adds a header indicating the results. You can then use SpamAssassin to detect the OS an add an appropriate point total. Since few "real" organizations use desktop OSs for mail relays, you can usually assume a high probability of spamminess from such.
Because there's no large group of people out there that actually believe Santa Claus exists
Oh yeah? Then who are all of those people I line up with every year to see him at the mall? HMM??? You've tried to put us down for years with all of your "facts" and "science," but we all know the truth.
Keep talking like that, mister, and you're going to find a lump of coal in your stocking this year...
I suspect that it was done intentionally. The batteries used will typically last only three years or so, rendering the device essentially useless after their expiration. It goes beyond planned obsolescence... it's forced obsolescence. Apple is perfectly happy to sell everyone a new iPod every three years.
The battery issue is the primary reason that I will not buy an iPod. Like you, I'm somewhat disgusted by the fact that the product is expected to end up in a landfill (battery and all) in a relatively short period of time. That, and I'm not too happy about shelling out $250+ for an item that I know will "break" soon after I buy it. I know we're heading towards a disposable society and all, but come one!
I still have a Panasonic boom box I bought in 1990. The speakers are just as loud as they were sixteen years ago, the radio still works, and the CD player still plays CDs. Sure, the dual-cassette player is broken, but who still uses tape, anyway? I've bought plenty of better players since, but that one is still works just fine in my workshop.
Show me an iPod that'll still function in 2022 (not to mention in extreme and changing winter/summer temperatures as well as surrounded by sawdust and metal shavings) and I'll buy one.
Sure, out in the middle of a cornfield in Kansas, you might not care about DGPS, but in that case you often have eight or ten satellites available and an accuracy of perhaps 15 feet. Not in the middle of the city.
Not true. In the middl of a cornfield in Knasas, where farm machinery is uften automated and steered via GPS, extreme precision is critical. Non only that, but your sample rate is often much higher than the.5 to 1 Hz seen in most consumer GPS units.
If your thresher (or whatever) is out in the field "threshing" you'll want to make sure that the individual rows it covers are even and as close together as possible. Too much overlap and you're wasting time and fuel. Without overlap you would miss "product."
At my company we've used a number of Dell PowerEdge Linux servers running Samba. All of the servers are then tied together using Samba's Dfs implementation to "stitch" individual components together for Windows clients and NFS/AutoFS/symlinks for Linux clients. This is all accomplished with some very simple perl and shell scripts.
This likely won't work in all environments, however. Our data is divided into thousands of discrete and manageable chunks stored in individual directories, so stitching it together via an automated process is relatively simple. Part of the job of the scripts mentioned above is to "rebalance" these chunks (move them from server to server) to prevent any one volume from becoming full. If your data "components" are large, or if your data is too active to move regularly, this won't work.
It's the poor man's cluster, and there are better solutions out there, but it works extremely well in our case.
Slashdot Mirror
Which is precisely where apple (usually) succeeds and others fail. Apple would NEVER have released a product in the same state Amazon released the Fire. Generally speaking (and there are most certainly exceptions,) Apple won't release a product until it's "done." Other tech companies really should learn from this example.
I'm often stunned by the crap that modern "consumers" are willing to accept.
Mock us if you want, non-believer, but your "photons" are a load of bunk. Darkons dominate the universe, and those things you call "light sources" are nothing more than darkon attractors. The math proves it.
Are you surprised? Most people think Arkham is a mental institution in a movie about a comic book.
Just use a bandsaw to cut off the spine and feed it through a normal scanner with a sheet feeder. Duh. Faster, cheaper, and better results along the spine.
Oh, you wanted to keep the books INTACT?
While I respect your modest proposal, I've always felt that human flesh to be a bit gamey. Even as a zombie I still prefer chicken.
Don't forget WLW, which operated at half a megawatt for quite some time (and even applied for a license to operate at a megawatt at one point.)
I used to pick up WLW on my home answering machine at a distance of about ten miles from the transmitter. Stupid faulty ground...
Sadly, I haven't seen any triffids today.
I've heard of destroying CRTs for security purposes, but not for modern tubes and not for office systems. I believe that the practice originated in old-style CAD displays where burn in was extremely common.
I agree with you that it's extreme overkill, but it's not completely paranoid. Shooting them sounds like the worst possible way of destroying a display, though. Aren't there CRT recycling centers that would accomplish exactly the same thing?
As Eric Cartman might say...
"You just got F'ed in the A."
Absolutely.
Yes. Flavor. And to see if you can make your heart explode.
I used to make the eggs sunny-side-up and melt cheddar cheese over the top, but it ruined the "soupy mess" effect of the syrup, butter, and yolks. For some extra yolk in your soupy mess, go sunny side up instead of over-easy. It's really easy to completely solidify the yolks if you go over-easy, too, so I sometimes go sunny-side anyway. Oh yeah, and remember to get all of the solids out of your grease before cooking your eggs... crunchy carbon in the eggs just isn't tasty.
The excess melted butter, syrup, and egg yolks should be allowed to mingle. The resulting soupy mess should be eaten mixed with the hash browns. The biscuit can be used to mop up any remaining liquid.
This should not be eaten on a regular basis. I use it before a long day of hard outdoor work, like felling trees, hauling timber, pouring concrete, etc.. Anything where I expect to burn a huge number of calories.
Actually, the windows version is annoying, clunky, and makes my head hurt. I prefer the UNIX (and now Linux) versions because so much can be done from the command line when necessary. With Networker on UNIX, you can just use wrapper scripts around the basic commands if the GUI doesn't work for you. For large or complex recoveries, CLI is really the best way to go, anyway.
Sounds like a problem with your staging policy. Make sure the stage itself is enabled and make sure the destination pool is correct. Does manual staging work?
Slashdot isn't really a networker support forum... feel free to email me at skroz at skroz dot net, if you'd like.
I've been using Legato (now EMC) Networker at a number of different sites for over ten years now. It's easy, reliable, and supports a wide range of hardware. It scales well, but can get quite expensive when you start adding large autoloaders into the mix.
Their site should get you started. They'll set you up with a media kit and 45 day demo licenses if you request one.
I've got it. Sorry, but I've decided to keep it.
Heh... yeah. It's been a long day.
Amavisd-new has had p0f support for detecting the OS of the sending mail server for quite some time. It detects the OS type of the incoming mail connection and adds a header indicating the results. You can then use SpamAssassin to detect the OS an add an appropriate point total. Since few "real" organizations use desktop OSs for mail relays, you can usually assume a high probability of spamminess from such.
I ask that you use the proper capitalization of American when slamming my nation's environmental record, sir.
Oh yeah? Then who are all of those people I line up with every year to see him at the mall? HMM??? You've tried to put us down for years with all of your "facts" and "science," but we all know the truth.
Keep talking like that, mister, and you're going to find a lump of coal in your stocking this year...
I suspect that it was done intentionally. The batteries used will typically last only three years or so, rendering the device essentially useless after their expiration. It goes beyond planned obsolescence... it's forced obsolescence. Apple is perfectly happy to sell everyone a new iPod every three years.
The battery issue is the primary reason that I will not buy an iPod. Like you, I'm somewhat disgusted by the fact that the product is expected to end up in a landfill (battery and all) in a relatively short period of time. That, and I'm not too happy about shelling out $250+ for an item that I know will "break" soon after I buy it. I know we're heading towards a disposable society and all, but come one!
I still have a Panasonic boom box I bought in 1990. The speakers are just as loud as they were sixteen years ago, the radio still works, and the CD player still plays CDs. Sure, the dual-cassette player is broken, but who still uses tape, anyway? I've bought plenty of better players since, but that one is still works just fine in my workshop.
Show me an iPod that'll still function in 2022 (not to mention in extreme and changing winter/summer temperatures as well as surrounded by sawdust and metal shavings) and I'll buy one.
Not true. In the middl of a cornfield in Knasas, where farm machinery is uften automated and steered via GPS, extreme precision is critical. Non only that, but your sample rate is often much higher than the
If your thresher (or whatever) is out in the field "threshing" you'll want to make sure that the individual rows it covers are even and as close together as possible. Too much overlap and you're wasting time and fuel. Without overlap you would miss "product."
But contrary to what you may believe, Slashdot ISN'T.
At my company we've used a number of Dell PowerEdge Linux servers running Samba. All of the servers are then tied together using Samba's Dfs implementation to "stitch" individual components together for Windows clients and NFS/AutoFS/symlinks for Linux clients. This is all accomplished with some very simple perl and shell scripts.
This likely won't work in all environments, however. Our data is divided into thousands of discrete and manageable chunks stored in individual directories, so stitching it together via an automated process is relatively simple. Part of the job of the scripts mentioned above is to "rebalance" these chunks (move them from server to server) to prevent any one volume from becoming full. If your data "components" are large, or if your data is too active to move regularly, this won't work.
It's the poor man's cluster, and there are better solutions out there, but it works extremely well in our case.
Too easy? Turn the difficulty slider up all the way. Your "death blossom" won't be so cool anymore.