Same story, but wound up confused the first time through because I somehow landed myself an a.out kernel for an ELF distribution. Ah, well; EFNet #linux...
I do wonder what Slackware's biggest downfall is these days. IIRC, it was package management or the general lack thereof, previously. I've got a laptop with FreeBSD *ahem* PC-BSD on it that wants a different flavor of *NIX, I might try throwing it on there...
Except for the RRoD, YLoD, over a decade of unscrupulous bad/underspecified capacitor guffaws, the continuing lead-free solder fallout from RoHS, and electron migration slowly killing things like IC radio transceivers, I guess you're right!
1. Beamforming and spacial multiplexing. Read up on the differences between 802.11ac and 802.11a/b/g/n.
2. There's a sucker born every minute... no, that's not what I meant to say. I mean, this is Slashdot: We have LANs. We transfer data across out LANs. We would rather transfer data more quickly across our LANs (and associated WLANs) than we would like to so less quickly.
In other words, I don't want to plug my laptop into the network just to move some big files around and do a backup.
Who cares how fast the Internet connection is? We already know how to do arithmetic here. Next!
3. See #2. Seriously. It doesn't take lots of people; it just takes one person who has a lot of stuff to transfer locally to justify a better radio at the router end of things, and this applies to Grandma and her snapshots of her grandkids, too.
If all you want to do with a wireless router is access the Internet, you're in the wrong crowd.
And yet, solid-state electronics with no moving part fail fairly regularly.
You act as if you've never actually had your hands on any 20-year-old hardware: 20 years ago, computer stuff regularly broke within a couple of years: I know this because I was fixing them 20 years ago. That which is still left is simply at the other end of the MTBF scale.
I'm game, too: $17,000,000.00/yr seems like a good starting point to me as well, since that's certainly plenty for most of the most-exuberant lifestyles imaginable.
But won't we need a lot of torches to make this? And what about pitchforks?
Given the way that the Windows Store keeps shoving itself in my face (I've been dinking around with "insider" builds), it would surprise me none if MSFT were going to take the same route as GOOG and AAPL: Give away the OS, and make money on a percentage of the take selling applications.
Every time I look at running NTP on Android (because I'm a geek like that, and it annoys me that clock skew is a solved problem everywhere else), I find that it's never been implemented by anyone because "herrp, it's taken care of automatically! who cares?"
Kids, these days...
Sometime I'll have to hack up ntp to run on Android as a proof of concept and get the ball rolling myself, I guess.
Perhaps I was trying to steer your argument in favor of my own want for re-education programs.
Many drivers consistently don't know how to use shared turn lanes properly. They consistently misidentify passing zones (!) on rural 2-lane roads. They consistently don't know how to handle an intersection with (gasp) more than one dedicated left-turn lane.
Currently, the only reinforcement of correct behavior is negative: Car crashes and tickets for those who get it wrong. This is a problem.
Just have people take the same written test that new licensees have to take, every 5 years, with zero immediate penalty for not passing, and many opportunities to re-take. If drivers are as good they claim to be (I'm the best driver in the world, and so are you! Just ask one of us!), it'll be no big deal since they already know this stuff.
dd is sufficient. It doesn't have to be zeros -- it could be/dev/random or a long series of concatenated goatses: Once the bits are set into different byte patterns, nobody can tell what the previous bytes were anymore.
They used to be able to recover some data using a process called magnetic force microscopy, but those days are gone and the process was/is expensive enough that your financial data wasn't a cost-effective proposition.
One thing that none of these high-level software erasure techniques can do is deal with data that remains in reallocated sectors, and for that the (literal) shotgun approach is probably best. If your financial information is that important, there's probably not enough relative value in the old hardware anyway.
Shoot it, throw it in the dumpster, and forget about it.
It baffles me why we don't use hydrogen for balloons. It's vastly cheaper, lighter, and leaks more slowly.
The only downside is the danger of storing it in big tanks to fill the things. But surely we've reached the stage now where suitably accredited businesses are allowed to keep potentially hazardous materials on site? It happens in lots of other industries.
Otherwise, having the a vent above the filling station that goes outside should alleviate most any commercialized OMFG HYDROGEN BUILDUP NEXT TO THAT ARCING FLUORESCENT LAMP HRP DERP DERP worries -- as long as only people who deal with explosive gases for a living transport the bottles, even within the store itself.
If it can be recycled and sold for party balloons, it can also be recycled and used for another medical device/other important thing
Unless you want to tell how it is that "virgin" helium is somehow superior to "recycled" helium, despite both of them being noble gases no matter how many times you use them -- especially when we're running out of the former, and keep letting Little Johnny make chipmonk noises with the latter before releasing it into the atmosphere (or beyond?).
f you get an apple device repaired at a third party that is not an AASP and you then take it into apple and they see it has third party parts in it, they will refuse to even look at it. In most cases. Mostly for idevices, but can extend to computers.
Oh, my lord. Does anyone read the shit they post anymore?
During the service ordering process, you must notify Apple of any unauthorized modifications, or any repairs or replacements not performed by Apple or an Apple Authorized Service Provider ("AASP"), that have been made to your product. Apple will not be responsible for any damage to the product that occurs during the repair process that is a result of any unauthorized modifications or repairs or replacements not performed by Apple or an AASP.
So. You go modding a third eyeball into the back of your iWidget, and have it illuminated and software-controlled, because you're just cool like that.
Apple wants you to
A) Tell them about this. (Well, duh.) B) Accept the fact that IF, DURING THE REPAIR PROCESS, the third eyeball on your iWidget (iBall?) causes the device to be damaged, THEN: C) Apple will ask for more money, because them working around your mod is now above and above them working on the terms of the warranty (though it was still fine until it got damaged BECAUSE of the mod). D) You can either pay them more money, and get the warranty issue fixed (and presumably your iBall mod re-assembled) or they'll just send it back to you broken.
Nowhere in the verbiage quoted does it say the warranty is toast, or that they'll refuse to look at it. In fact, the default condition is to A) tell them about the iBall, and proceed to the undeclared step of E) have warranty repair completed.
None of this means that managers aren't assholes who don't understand their own corporate policy, but that's a social problem and not a legal one, and the remedy is also social: First you talk to his boss, then that boss's boss, and so on, politely, until you find someone that can actually understand their own written warranty statement.
Which I guess can be hard, since you, puto, apparently can't be bothered with even doing so yourself. I suggest you start.
(There's another one born every minute, it seems.)
I've been telling everyone (here, too) about the Warranty Act of 1975, every time the foolish notion of "voiding" a warranty comes up, for over a decade.
If you're just hearing about it now, you should look around more.
Slashdot Mirror
Same story, but wound up confused the first time through because I somehow landed myself an a.out kernel for an ELF distribution. Ah, well; EFNet #linux...
I do wonder what Slackware's biggest downfall is these days. IIRC, it was package management or the general lack thereof, previously. I've got a laptop with FreeBSD *ahem* PC-BSD on it that wants a different flavor of *NIX, I might try throwing it on there...
Except for the RRoD, YLoD, over a decade of unscrupulous bad/underspecified capacitor guffaws, the continuing lead-free solder fallout from RoHS, and electron migration slowly killing things like IC radio transceivers, I guess you're right!
This stuff will last FOREVER!
I don't know if I'd call him a well-respected computer security guru.
But he did write Spin-Rite and seems to have built a cult of followers based on that, so there is that I guess.
1. Beamforming and spacial multiplexing. Read up on the differences between 802.11ac and 802.11a/b/g/n.
2. There's a sucker born every minute... no, that's not what I meant to say. I mean, this is Slashdot: We have LANs. We transfer data across out LANs. We would rather transfer data more quickly across our LANs (and associated WLANs) than we would like to so less quickly.
In other words, I don't want to plug my laptop into the network just to move some big files around and do a backup.
Who cares how fast the Internet connection is? We already know how to do arithmetic here. Next!
3. See #2. Seriously. It doesn't take lots of people; it just takes one person who has a lot of stuff to transfer locally to justify a better radio at the router end of things, and this applies to Grandma and her snapshots of her grandkids, too.
If all you want to do with a wireless router is access the Internet, you're in the wrong crowd.
(Now get off my lawn!)
And yet, solid-state electronics with no moving part fail fairly regularly.
You act as if you've never actually had your hands on any 20-year-old hardware: 20 years ago, computer stuff regularly broke within a couple of years: I know this because I was fixing them 20 years ago. That which is still left is simply at the other end of the MTBF scale.
Meh. Shibby's Tomato USB for me, FTW.
DD-WRT always seemed ao disappointingly fragmented, though it does work with more hardware.
Is there money to be made there, or is it dwarfed by high-bandwidth prospects?
I'm game, too: $17,000,000.00/yr seems like a good starting point to me as well, since that's certainly plenty for most of the most-exuberant lifestyles imaginable.
But won't we need a lot of torches to make this? And what about pitchforks?
In this particular scenario: You're dead. You don't care.
Given the way that the Windows Store keeps shoving itself in my face (I've been dinking around with "insider" builds), it would surprise me none if MSFT were going to take the same route as GOOG and AAPL: Give away the OS, and make money on a percentage of the take selling applications.
Yep.
And as an IMAX competitor myself, this doesn't sound like a particularly bad value -- part of which includes the IMAX certification.
It's out of my budget, but meh: I've only got about $20k worth of AV gear in my tiny living room that seats 3.
A 90's analogy:
"I need to buy a faster modem."
A Slashdotter's pedantic rebuttal:
"But it's not fast! It's stationary!"
Followed by,
"How fast is stationary engine, then?"
[...]
Please, just just stop.
I don't know WTF, either.
Every time I look at running NTP on Android (because I'm a geek like that, and it annoys me that clock skew is a solved problem everywhere else), I find that it's never been implemented by anyone because "herrp, it's taken care of automatically! who cares?"
Kids, these days...
Sometime I'll have to hack up ntp to run on Android as a proof of concept and get the ball rolling myself, I guess.
Perhaps I was trying to steer your argument in favor of my own want for re-education programs.
Many drivers consistently don't know how to use shared turn lanes properly. They consistently misidentify passing zones (!) on rural 2-lane roads. They consistently don't know how to handle an intersection with (gasp) more than one dedicated left-turn lane.
Currently, the only reinforcement of correct behavior is negative: Car crashes and tickets for those who get it wrong. This is a problem.
Just have people take the same written test that new licensees have to take, every 5 years, with zero immediate penalty for not passing, and many opportunities to re-take. If drivers are as good they claim to be (I'm the best driver in the world, and so are you! Just ask one of us!), it'll be no big deal since they already know this stuff.
Right?
It sells.
Same as shiny screens on laptops, which all of them in the store have, and almost none of them do if bought from the usual sources online.
And yes, it's BS. Meh.
dd is sufficient. It doesn't have to be zeros -- it could be /dev/random or a long series of concatenated goatses: Once the bits are set into different byte patterns, nobody can tell what the previous bytes were anymore.
They used to be able to recover some data using a process called magnetic force microscopy, but those days are gone and the process was/is expensive enough that your financial data wasn't a cost-effective proposition.
One thing that none of these high-level software erasure techniques can do is deal with data that remains in reallocated sectors, and for that the (literal) shotgun approach is probably best. If your financial information is that important, there's probably not enough relative value in the old hardware anyway.
Shoot it, throw it in the dumpster, and forget about it.
The reaction is short-lived, but I don't want to see Little Johnny's pants on fire because of it.
Otherwise, having the a vent above the filling station that goes outside should alleviate most any commercialized OMFG HYDROGEN BUILDUP NEXT TO THAT ARCING FLUORESCENT LAMP HRP DERP DERP worries -- as long as only people who deal with explosive gases for a living transport the bottles, even within the store itself.
If it can be recycled and sold for party balloons, it can also be recycled and used for another medical device/other important thing
Unless you want to tell how it is that "virgin" helium is somehow superior to "recycled" helium, despite both of them being noble gases no matter how many times you use them -- especially when we're running out of the former, and keep letting Little Johnny make chipmonk noises with the latter before releasing it into the atmosphere (or beyond?).
Oh, my lord. Does anyone read the shit they post anymore?
During the service ordering process, you must notify Apple of any unauthorized modifications, or any repairs or replacements not performed by Apple or an Apple Authorized Service Provider ("AASP"), that have been made to your product. Apple will not be responsible for any damage to the product that occurs during the repair process that is a result of any unauthorized modifications or repairs or replacements not performed by Apple or an AASP.
So. You go modding a third eyeball into the back of your iWidget, and have it illuminated and software-controlled, because you're just cool like that.
Apple wants you to
A) Tell them about this. (Well, duh.)
B) Accept the fact that IF , DURING THE REPAIR PROCESS, the third eyeball on your iWidget (iBall?) causes the device to be damaged, THEN:
C) Apple will ask for more money, because them working around your mod is now above and above them working on the terms of the warranty (though it was still fine until it got damaged BECAUSE of the mod).
D) You can either pay them more money, and get the warranty issue fixed (and presumably your iBall mod re-assembled) or they'll just send it back to you broken.
Nowhere in the verbiage quoted does it say the warranty is toast, or that they'll refuse to look at it. In fact, the default condition is to A) tell them about the iBall, and proceed to the undeclared step of E) have warranty repair completed.
None of this means that managers aren't assholes who don't understand their own corporate policy, but that's a social problem and not a legal one, and the remedy is also social: First you talk to his boss, then that boss's boss, and so on, politely, until you find someone that can actually understand their own written warranty statement.
Which I guess can be hard, since you, puto, apparently can't be bothered with even doing so yourself. I suggest you start.
(There's another one born every minute, it seems.)
And what is there to stop from incrementing the ECU's oil change counter, while keeping the old oil and filter in the car and doing zero work?
Dear sir or ma'am,
I find your citation to be largely unsupportive of your claims.
Please resubmit with greater clarity.
Thanks you,
Er, no. It informs me of what it says.
What it says may be a damned lie, but that's still the information that I receive from such verbiage.
I've been telling everyone (here, too) about the Warranty Act of 1975, every time the foolish notion of "voiding" a warranty comes up, for over a decade.
If you're just hearing about it now, you should look around more.
Galaxy S5 is easy, too: Remove back panel (using thumbnail in the slot provided), lift battery out.
I am at a loss as to why they're not all so simple.
A screwdriver and a prybar and a heat gun. These devices are held together with adhesive and plastic clips, with an occasional screw.
Changing the battery on a Moto X tends to destroy the NFC antenna, no matter how careful you are.
And my 1st gen iPod Touch did not survive battery replacement surgery, back when that was still a current device.
Hell, further back, I had a Palm Zire 71 which was impossible to disassemble to get at the battery.
More to the point, there are only two things that end users will probably need to do at some point: Change SIM cards, and replace the battery.
It should not be any more difficult than replacing the batteries in a children's toy.