Posts by Sven Coenye 250 publicly visible posts • joined 29 Mar 2008
Logitech and others use 5V 100mA rated switches at 3.3V. The corresponding lower operating current allows oxidation to build up, leading to more bounces. Eventually, things get so bad the firmware is no longer able to detect a single click.
So, if you do feel adventurous: the switches have a cover that can be removed with some fiddling (keep tabs on the "button" - it is not attached to anything.) A couple of light passes with very fine sandpaper over the contact area will remove the oxidation and the buttons will work as normal again.
And in spirit of TFA: Asus RoG mice have replaceable switches and come with a spare pair (and other assorted wear parts.)
it would have to be one level downstream from the ISP router as e.g. Comcast will lobotomize a customer owned router. But that then brings the entire configuration issue back as now you potentially get to deal with dueling Wifi and DHCP services. If something like this comes to be, my bet is it will be the ISP's game.You know, for a monthly fee...
He may have gotten his comeuppance for that one. Slick 50 was snake-oil of the worst kind. Not only did it not work as advertised - it did damage. (The magic ingredient was Teflon powder. The manufacturer claimed it would coat the cylinders and reduce friction, but Teflon doesn't work that way. All the particles did was gum up the oil passages.)
Die?
https://www.cnbc.com/2022/11/22/envoy-air-says-pilot-who-was-reported-incapacitated-during-flight-has-died.html
https://www.cbsnews.com/news/american-airlines-pilot-dies-william-mike-grubbs/
https://www.cnn.com/2015/10/05/us/american-airlines-pilot-death/index.html
(Or, maybe stay away from American Airlines altogether??)
From the patch linked to in the article:
+ /*
+ * Modern (>=Nehalem) Intel systems use ACPI via intel_idle,
+ * not this code. Assume that any Intel systems using this
+ * are ancient and may need the dummy wait. This also assumes
+ * that the motivating chipset issue was Intel-only.
+ */
So Intel claims the problem was theirs, even though it was only detected on AMD + Via ?? And it makes no sense for that to be a typo, as there would be no need to leave it in place for Intel CPUs if the issue was AMD-only.
2000's and the argument is not about application dependencies. The RPM3 to RPM4 transition caused serious pain with Mandrake when RPM4 packages started making their way into the (official) "pressure cooker" repository. An RPM3 base OS would recognize the application upgrade but was unable to handle the RPM4 package. Pretty soon, the result was an irreparable mess.
I held an H-1B visa through the mid-90s. The B does make a lot of difference. It did not have the "no displacement" clause attached. The main requirements were that the position needed at least a BA and wages had to be at or above "market rates" (only INS had no statistics on that - that is where the gaming started. By the time it was time for me to renew, that piece had been delegated to the Dept of Labor and they got lost in their own paperwork.) The rules have changed significantly since those days. The program has become unrecognizable and is now mostly a money printing machine for the Feds.
Indeed. We did roughly the same thing. We had a Motorola Surfboard for ~10 years before that. The upgrade only happened because the Surfboard finally was unable to keep up with the base package's speed.
(OTOH, at least one large cableco will lobotomize your equipment so you may not quite get the features you expected.)
Someone lost track while writing TFA? The lead paragraph mentions a coal plant. I read that as a coal fired power plant, not the mine it turns into at the end. The former would make some sense as things like the hook-up to the grid are already in place, May even be able to reuse some of the turbine bits.
Bwahaha! That's a good one!
If you can draw a line on a map and one side has Comcast and the other side has Verizon, that is not what I call competition.
(And Verizon [and it's successor, FairPoint/Consolidated] used to sell 16 Mb/s packages in areas where they could only deliver 1.5 Mb/s off-peak. On if one complained, they would push a 20Mb/s package which the local exchange could not support. I have to consider myself lucky to be on the Comcast side of the map :-( )
Next up ... "we have found that 1% of our customers are responsible for 99% of ink consumption. Going forward, in order to protect the interests of all customers, full page color prints are no longer included in the monthly allotment and will be billed at the low price of $4.99/page"
Samsung punted the home entertainment operation in 2019. Even with that, they acknowledged the problem almost immediately and do fix it for free (postage included) even out of warranty. Some should take that as an example. But samsungcloudsolutions.net is going on the NXDOMAIN list forever regardless. :-(
Yes, let's adopt Poettering's shutdown strategy: change the event sequence in udev to suit systemd without giving a thought to anyone else. This had the lovely side effect of breaking shutdown completely if a LUKS partition was in use on SysV init.
(As in - upgrade from Debian Jessie to Stretch and find you can't shut down anymore. Lovely. I've used Debian since the 2.x days, but that was the last straw. Swicthed to Devuan and have not had a reason to look back. And Beowulf runs fine on a Raspberry Pi too.)
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2023
