What happened between 7 an XP was Intel giving MicroSoft a kick by donating a bunch of code to Linux that massively improved the boot times leaving MS to suddenly be far behind in that department.
It's not he first time I've seen Intel do this and Microsoft reacts the same way every time and suspect that's Intel's new way of dealing with MicroSoft: Anytime they want MS to do something they give the code to Linux that does what they want in Linux.
And yes I have used a cheap dual drive NAS while it was rebuilding the array. It was slower but still functional.
Hot swap cases make drive management much easier. Drive 3 of 5 needs replacing? Forget tracing cables back to the motherboard just pop out drive 3 in the array and replace it. This also means I can get someone else to do it even if it means walking them through it over the phone.
These things need to be dead easy since I have been going out of my way to tell all of my non techie friends that USB drives do not count as backups.
I highly suggest an Ergotron monitor stand. They are easy to set to the exact height you need the monitor to be at and, thanks to it's internal pulley system, after 3 years mine still holds solid as opposed to the cheaper (or even some of the more expensive) ones that have a tendency to slowly sink.
I prefer mesh chairs to anything else because they don't hold the heat against my back or seat and at work. In my office I have a standard chair with the usual fake leather and I find I lean forward on hot days to avoid back sweat and I know that's not good for my posture.
I also suggest not bothering with ergonomic keyboards and instead go with something like the HP washable. It's solidly built and every once and awhile I go give it a solid washing. Hygiene is important too and keyboards tend to be bacteria central.
Yes but that doesn't mean you have to suffer. Just because you are at work does not mean the employer must pay for everything. and I can't imagine an employer that would mind an employee bringing things to work that make them work more efficiently. I'm not saying go all out but forking out $20 - $30 for a monitor riser stand so at least the worst of the neck strain isn't an issue will at least make life easier.
The proper way to deal with these things is to deal with the seller first and I tried to do that but anyways from the response I got was that I didn't have a case under any condition.
Many people accept returns but only for defective products. If I ordered size large and was sent size small or I got something damaged I would expect a repair or refund and the law would pretty much back me up on that.
It is not a reasonable policy. Imagine if you went to rent a car and was handed the keys on the first day tried to drive the car out of the lot only to discover it doesn't start. Then imagine being told that sorry we rented you the car for a week but never said it would drive. I was sold a subscription I had no possible way to access and no way to know that before paying for it. I got no communication at all from the guy who sold it to me and asked for a refund after two days of not even a single word from the guy.
If Amazon sold me a Halloween costume that wasn't fit for purpose (wrong size, damaged goods etc) I would demand my money back I could understand why they wouldn't return the goods if there were no defects but afik even Amazon isn't evil enough to stick anyone with defective goods based on policy.
Essentially I got sold a product that didn't exist, had I used my credit card my bank would have pulled the money and I would have gotten a refund.
There are some easy ways to screw a customer that gets around the TOS. What happened to me was that I was charged for a 1 month subscription to a website that ended up requiring non functional software to access the site. Ended up being told that I was out of luck because that kind of transaction is non refundable.
Thankfully there wasn't much money at stake but I sharply cut back my Paypal usage after that.
And abstinence provides better protection than condoms.
Yet, abstinence probably leads to much more serious things than possibility of some minor STD, including depression, anti-social behavior and stress. It's good to let go every once in a while.
Of course, there is a good middle ground too. Serious STD's like HIV/AIDS generally do not spread orally. If you're on the receiving end of a blowjob, you have almost 0% change of catching HIV. Even with prostitutes. I learned this thing and have had sex with many ladyboys and never had any STD. Of course, while having intercourse it's a good idea to use condom, but as a receiving end of a blowjob, you cannot get AIDS.
You think that's bad? Just go into your local Walmart with a pen and paper and start writing prices down and time how long it takes them to stick security on you. I have just discovered that Tesco has the same policy.
No My answer is for the BIOS makers to do the right thing and quite frankly, the current situation is hardly Microsoft's "A" game when an estimated 70% of windows problems are due to driver crashes. The only reason MicroSoft allows this to continue is because it works against their competitors and if they gave a flying crap about their own customers they would have demanded hardware makers all conform to a set of standards that MicroSoft can write drivers for a long time ago.
Oh, and if your favored platform has so many fiddly tweaks they they have generated a cottage industry of tool makers (PowerTweak etc) you don't get to call out the competition for "esoteric workarounds"
The monthly rate more than covers that cost of installation and maintenance of those lines. The technology advance is quite honestly not expensive even at $60 per port on ADSL2+ equipment (slightly high) they can expect to make that money back long before the next technology rollout. And quite frankly, they haven't had to worry about changing the actual cable (and no, it shouldn't involve tearing out streets at this point because most of that is in conduit) until recently with the moves to fiber.
To be clear: I don't mind being charged a monthly rate. What I object to is being charged $15/ GB for over b/w fees.
That is exactly my point. The entire cost of running an ISP is the costs associated with the "last mile" and they are using that to overcharge. I would be much more understanding if the limitations I faced were due to the copper rather than artificial charges from the ISP side.
Not really, In places where the b/w costs are competitive (server hosting) I don't pay much more than that. ISPs only get to charge more because there are fewer options, on the other hand, last time I was in a telco building pretty much everyone was using ATM switching equipment and that will drive the costs up.
Don't be stupid. If they had done that we would all be blasting Linux for making things unstable. The setting that used the power regression was that due to stability issues Linux now by default leaves the power state setting where the BIOS left it with a switch to enable it if you feel brave. This all means that if you have a non buggy chipset Linux will use the power save setting as before. This is the smart play because if the BIOS hasn't set it than it hasn't been tested by the manufacturer.
Phoronix is trolling, if they have a laptop where the setting works fine they need to be complaining to the Laptop manufacturer and have them correct their BIOS to take full support of the chipset.
On a properly deployed system you should expect config problems for the first couple of days after you deploy something and someone does something you didn't expect even if the same config worked in testing and after that the bugs get into the "one off" variety. In either case you want to find out what went wrong.
It's not the "load a VM to get the service working again" that I object to. I object to the idea that you can just reload a VM and never debug.
Better idea: bring in backup server/VM or whatever then figure out what went wrong on the original. If it happened once than it will happen again given the same config. You might have some bad hardware, or you could have a bug that only happens under select conditions.
Case in point: the sasl software most people use with Postfix has a memory leak when the wrong password is entered (yes they know, no they don't actually care) Some would say a memory leak isn't a problem because it would take thousands of bad password attempts to take down the software right? But what happens when some bot sends several thousand requests in an attempt to guess system passwords? 4 GB of ram later the process goes dead. Reloading the VM? good thing but you still have an exploitable glitch that can be used to take down the mail service and unless someone goes through the logs and discovers what exactly happened you will just end up with the same problem on the next bot scan.
You have the time between when a service starts misbehaving until it's detected and then reported to someone who can start a new VM, That time gap is something the customer will notice Fixing it right the first time prevents more outages and the customer will care about that. A VM/Backup server/ whatever may help with shortening the outage but it will not reduce the time spent debugging.
I think you have missed the entire point. You still need people who know what they are doing to make the scripts and setup in the first place.
What DevOps fixes are places where any problem gets passed off on someone else. Software is too slow? Software devs blame the database people who blame the systems people who blame the networking people (if they can) and as a result pretty much any problem is fixed with hardware upgrades and when that becomes impossible you end up with a badly running system but either way the whole thing costs more than it ever should have.
Case in point: At a company I previously worked at they were building some some bingo software for another customer that required a front end server and a dedicated database server (with hot failover). That's three top of the line servers for 300 concurrent users. Software devs blamed the hardware and when that failed they blamed Java.
Sorry but no. What you are suggesting is a more modern "reboot the server and see if that fixes it" and it solves nothing. Somewhere the bug is lurking and waiting to rear it's ugly head again. It could happen in a week or it could happen tomorrow but it's very likely it will happen.
And how do you know the new VM won't have the same problem? If you never know what went wrong and fix the actual problem you will just end up restarting VMs constantly.
Slashdot Mirror
What happened between 7 an XP was Intel giving MicroSoft a kick by donating a bunch of code to Linux that massively improved the boot times leaving MS to suddenly be far behind in that department.
It's not he first time I've seen Intel do this and Microsoft reacts the same way every time and suspect that's Intel's new way of dealing with MicroSoft: Anytime they want MS to do something they give the code to Linux that does what they want in Linux.
Don't know how that first "And" got there even though I went out of my way to proofread that.
And yes I have used a cheap dual drive NAS while it was rebuilding the array. It was slower but still functional.
Hot swap cases make drive management much easier. Drive 3 of 5 needs replacing? Forget tracing cables back to the motherboard just pop out drive 3 in the array and replace it. This also means I can get someone else to do it even if it means walking them through it over the phone.
These things need to be dead easy since I have been going out of my way to tell all of my non techie friends that USB drives do not count as backups.
Most plans if this kind can be covered by the saying "Anything is easy if you don't know what you are talking about."
You don't have a hot plug enclosure in there and much all of these will hot plug drives.
I highly suggest an Ergotron monitor stand. They are easy to set to the exact height you need the monitor to be at and, thanks to it's internal pulley system, after 3 years mine still holds solid as opposed to the cheaper (or even some of the more expensive) ones that have a tendency to slowly sink.
I prefer mesh chairs to anything else because they don't hold the heat against my back or seat and at work. In my office I have a standard chair with the usual fake leather and I find I lean forward on hot days to avoid back sweat and I know that's not good for my posture.
I also suggest not bothering with ergonomic keyboards and instead go with something like the HP washable. It's solidly built and every once and awhile I go give it a solid washing. Hygiene is important too and keyboards tend to be bacteria central.
Yes but that doesn't mean you have to suffer. Just because you are at work does not mean the employer must pay for everything. and I can't imagine an employer that would mind an employee bringing things to work that make them work more efficiently. I'm not saying go all out but forking out $20 - $30 for a monitor riser stand so at least the worst of the neck strain isn't an issue will at least make life easier.
The proper way to deal with these things is to deal with the seller first and I tried to do that but anyways from the response I got was that I didn't have a case under any condition.
Many people accept returns but only for defective products. If I ordered size large and was sent size small or I got something damaged I would expect a repair or refund and the law would pretty much back me up on that.
It is not a reasonable policy. Imagine if you went to rent a car and was handed the keys on the first day tried to drive the car out of the lot only to discover it doesn't start. Then imagine being told that sorry we rented you the car for a week but never said it would drive. I was sold a subscription I had no possible way to access and no way to know that before paying for it. I got no communication at all from the guy who sold it to me and asked for a refund after two days of not even a single word from the guy.
If Amazon sold me a Halloween costume that wasn't fit for purpose (wrong size, damaged goods etc) I would demand my money back I could understand why they wouldn't return the goods if there were no defects but afik even Amazon isn't evil enough to stick anyone with defective goods based on policy.
Essentially I got sold a product that didn't exist, had I used my credit card my bank would have pulled the money and I would have gotten a refund.
#4 is why I have an account dedicated to PayPal that I only transfer money into when I make a purchase.
There are some easy ways to screw a customer that gets around the TOS. What happened to me was that I was charged for a 1 month subscription to a website that ended up requiring non functional software to access the site. Ended up being told that I was out of luck because that kind of transaction is non refundable.
Thankfully there wasn't much money at stake but I sharply cut back my Paypal usage after that.
NoScript blocks more malware than either.
And abstinence provides better protection than condoms.
Yet, abstinence probably leads to much more serious things than possibility of some minor STD, including depression, anti-social behavior and stress. It's good to let go every once in a while.
Of course, there is a good middle ground too. Serious STD's like HIV/AIDS generally do not spread orally. If you're on the receiving end of a blowjob, you have almost 0% change of catching HIV. Even with prostitutes. I learned this thing and have had sex with many ladyboys and never had any STD. Of course, while having intercourse it's a good idea to use condom, but as a receiving end of a blowjob, you cannot get AIDS.
This is dangerously wrong. The CDC reports that the risk is lower but still a risk with known infections.
I imagine it's some rule to keep antihistamines from being turned into street drugs that ended up far too restrictive than what it was designed for.
You think that's bad? Just go into your local Walmart with a pen and paper and start writing prices down and time how long it takes them to stick security on you. I have just discovered that Tesco has the same policy.
No My answer is for the BIOS makers to do the right thing and quite frankly, the current situation is hardly Microsoft's "A" game when an estimated 70% of windows problems are due to driver crashes. The only reason MicroSoft allows this to continue is because it works against their competitors and if they gave a flying crap about their own customers they would have demanded hardware makers all conform to a set of standards that MicroSoft can write drivers for a long time ago.
Oh, and if your favored platform has so many fiddly tweaks they they have generated a cottage industry of tool makers (PowerTweak etc) you don't get to call out the competition for "esoteric workarounds"
The monthly rate more than covers that cost of installation and maintenance of those lines. The technology advance is quite honestly not expensive even at $60 per port on ADSL2+ equipment (slightly high) they can expect to make that money back long before the next technology rollout. And quite frankly, they haven't had to worry about changing the actual cable (and no, it shouldn't involve tearing out streets at this point because most of that is in conduit) until recently with the moves to fiber.
To be clear: I don't mind being charged a monthly rate. What I object to is being charged $15/ GB for over b/w fees.
That is exactly my point. The entire cost of running an ISP is the costs associated with the "last mile" and they are using that to overcharge. I would be much more understanding if the limitations I faced were due to the copper rather than artificial charges from the ISP side.
Not really, In places where the b/w costs are competitive (server hosting) I don't pay much more than that. ISPs only get to charge more because there are fewer options, on the other hand, last time I was in a telco building pretty much everyone was using ATM switching equipment and that will drive the costs up.
Don't be stupid. If they had done that we would all be blasting Linux for making things unstable. The setting that used the power regression was that due to stability issues Linux now by default leaves the power state setting where the BIOS left it with a switch to enable it if you feel brave. This all means that if you have a non buggy chipset Linux will use the power save setting as before. This is the smart play because if the BIOS hasn't set it than it hasn't been tested by the manufacturer.
Phoronix is trolling, if they have a laptop where the setting works fine they need to be complaining to the Laptop manufacturer and have them correct their BIOS to take full support of the chipset.
On a properly deployed system you should expect config problems for the first couple of days after you deploy something and someone does something you didn't expect even if the same config worked in testing and after that the bugs get into the "one off" variety. In either case you want to find out what went wrong.
It's not the "load a VM to get the service working again" that I object to. I object to the idea that you can just reload a VM and never debug.
Better idea: bring in backup server/VM or whatever then figure out what went wrong on the original. If it happened once than it will happen again given the same config. You might have some bad hardware, or you could have a bug that only happens under select conditions.
Case in point: the sasl software most people use with Postfix has a memory leak when the wrong password is entered (yes they know, no they don't actually care) Some would say a memory leak isn't a problem because it would take thousands of bad password attempts to take down the software right? But what happens when some bot sends several thousand requests in an attempt to guess system passwords? 4 GB of ram later the process goes dead. Reloading the VM? good thing but you still have an exploitable glitch that can be used to take down the mail service and unless someone goes through the logs and discovers what exactly happened you will just end up with the same problem on the next bot scan.
You have the time between when a service starts misbehaving until it's detected and then reported to someone who can start a new VM, That time gap is something the customer will notice Fixing it right the first time prevents more outages and the customer will care about that. A VM/Backup server/ whatever may help with shortening the outage but it will not reduce the time spent debugging.
I think you have missed the entire point. You still need people who know what they are doing to make the scripts and setup in the first place.
What DevOps fixes are places where any problem gets passed off on someone else. Software is too slow? Software devs blame the database people who blame the systems people who blame the networking people (if they can) and as a result pretty much any problem is fixed with hardware upgrades and when that becomes impossible you end up with a badly running system but either way the whole thing costs more than it ever should have.
Case in point: At a company I previously worked at they were building some some bingo software for another customer that required a front end server and a dedicated database server (with hot failover). That's three top of the line servers for 300 concurrent users. Software devs blamed the hardware and when that failed they blamed Java.
Sorry but no. What you are suggesting is a more modern "reboot the server and see if that fixes it" and it solves nothing. Somewhere the bug is lurking and waiting to rear it's ugly head again. It could happen in a week or it could happen tomorrow but it's very likely it will happen.
And how do you know the new VM won't have the same problem? If you never know what went wrong and fix the actual problem you will just end up restarting VMs constantly.