Slashdot Mirror
Ask Slashdot: How Often Do You Update Your OS?
An anonymous reader writes: A couple friends of mine have been having a debate recently. One is constantly updating all of his operating systems (desktop, phone, and otherwise), often as soon as a new patch is available. He tries betas and nightlies. He has a different ROM on his phone every other week. The other friend is much more conservative with his updates. Once his systems are running smoothly, he wants to leave them alone for as long as possible. He'll do some serious security updates, but he's extremely wary of anything involving major UI changes or functionality differences. What's your preference? Are you constantly tweaking? Waiting for the early adopters to work out the kinks? How does your preference change between work machines and personal machines?
First I update the VMs, if they survive then I update the main box. I'm running CentOS BTW.
The simple truth is that interstellar distances will not fit into the human imagination
- Douglas Adams
In the immortal words of Weird Al:
"I've beta tested every operating system; gave props to some but others, I dissed 'em "
Yeah I tend to update and change my OS frequently on my personal systems. Work systems tend to be kept in known stable configurations.
Nothing to see here
Alvin Toffler thought human personalities could be split between those who welcome change and those who avoid it. First published in mid-20th century.
https://en.wikipedia.org/wiki/...
http://www.amazon.com/Future-S...
https://www.goodreads.com/book...
Whenever I have some of the most expensive and valuable resource to waste - my time. If it is up and working, security updates go in, after 2 to 3 weeks, other updates may go with them as well, but not necessary. I would rather be out on my bicycle or working on my photo collection ( sometimes I take 3-4k photos on a weekend) than doing updates. Keep in mind, the summary talks about upgrades - the new rom every week. Update is keeping the same version, upgrade is moving to another.
This is an issue that I think is handled beautifully by Ubuntu's release system. LTS releases come out on a relatively steady schedule, with bleeding-edge releases in between. I personally stick with LTS releases, which come out often enough to keep me up to date with features, etc., but without lots of things breaking all the time.
And, yes, I like Unity very much.
Let the suckers and adventurers be the beta testers.
Don't run the crap which is most likely to be causing you security problems in the first place -- I've never been impacted by a Flash zero day exploit because I don't run it.
Many years of being around computers has taught me that I have no intention of putting up with the drama of beta testing for companies who do a lousy job of QA.
I've seen WAY too many things which are broken on day 1, or even worse, which introduce new broken on day 1 that it takes some time to identify.
There isn't an OS vendor on the planet I'd accept a fresh release from and install on the first day.
If you do this stuff as a hobby, have fun with it. The rest of us don't have the time or the inclination to consider upgrading the OS to be a hobby.
Lost at C:>. Found at C.
Your friends show two distant points on the patching spectrum we have to make all the time.
Neither is right, nor wholly wrong. The first friend doesn't worry so much about stability, and for himself that's fine. He knows the choices he's making and he's really into that. Good for him. The second friend is more conservative and more in line with what the mainstream hopes for and expects. I'd like to know what they consider "serious security" updates, because it could be anywhere from reasonable security to complete insecurity. This is why most environments have tiers of patching and testing. We know we need to get security updates out as much as possible. Some people get more value out of being on the bleeding edge than having a stable install, others can't/won't have their work interrupted for any cost. This is also why this argument is silly to have between two people on which way is "better."
As for what I do? My home system gets updates as soon as I see they're available. I occasionally play with nightlies or betas, on a VM, to see if there are major interface tweaks, a new feature I want, or whatever else I'm interested in. I'd never suggest that for most of my friends or relatives.
Incidentally, that's pretty much how it goes at work. Most of the people I work with in IT, and a few select users are in the first group. Most people get security updates quickly, and well vetted other updates when they're more thoroughly tested.
Which is the one which comes pre-installed on most distros?
with the production releases and patches. I won't use betas or nightlies unless I'm trying to fix a specific bug.
I'm still using DOS on a P-II w/640k RAM. No problems so far.
It must have been something you assimilated. . . .
the Emacs vs VI war is over (Emacs won) ...
Yeah I'm thinking not. I've been a Unix sysadmin for over 15 years and I've never worked with a single person who uses Emacs.
Nothing to see here
Automotive control interfaces change all of the time.
Into about 1980 all American cars and trucks had, for many years, placed the headlights control on the dash at the left. Wiper blade control was usually on the lower left side of the dash near the knee bolster. They placed the turn signal on the left side of the column, placed the gearshift on the right side of the column, and placed the brights control on the floor, operated by the left foot. The radio was generally low on the right side. If a fancy car had an interior dome light with dimming capability it was usually placed on the left with the headlight control, and if there was cruise control, the function was integrated with the turn signal indicator stalk, with a slider on the side for set/coast and a button on the tip for on/off.
In the late seventies and eighties they started playing with multifunction stalks and all bets were off. Some cars integrated nearly every function into the stalk, and if the car had a floor shifter instead of a column shifter sometimes a second multifunction stalk was added to the right side. Floor controls were mostly eliminated and most low, hard to reach controls were relocated to stalks. Tilting telescoping steering columns added a third stalk on the lower-left of the column. When Mercedes Benz took over Chrysler they attempted to add a fourth stalk to the column, low on the right, for the cruise control. Steering wheels got controls on the front, then on the back. At one point early on there was a "rim blow" steering wheel where squeezing the wheel would activate the horn.
My point is that automotive controls are very much NOT standard. Even basic functions like gear selection could be pushbutton, could be a column stalk, could be a dash stalk, could be a floor stick, could be a dash-mounted knob, could be a center-console knob, and there are probably more variations yet. Drivers have to get used to each and every configuration.
Do not look into laser with remaining eye.
I'm on arch, so way too often if you ask me. To specifically answer the question: at least once a week, with probably a new kernel update every couple of weeks. I make sure I have LVM snapshots between each update procedure as at least 1/4 of the time something breaks. I really wish arch didn't use rolling updates, but the vast AUR repository unique to arch is more than worth it.
If it ain't broke, don't fix it.
What is the entire lab doing planning to run Win 10 Home? That's the only edition that forces mandatory updates. Pro lets you defer them; Enterprise lets you completely control the process
Say what? I work in a shop with extensive Solaris and Linux installation, and run several personal Linux boxes as well. They all have vi. None of them, as far as I know, and I checked several, have Emacs. This was not a conscious decision for any of them: it's just the way the hosts installed (although on my personal boxes, I would've installed vi had it not installed by itself). Who won the war?
Still running Windows for Workgroups 3.11....
MS word 2.0 works just fine!
Do not look at laser with remaining good eye.
The answer is simple: hipsters don't design car user interfaces, but they do "design" software user interfaces.
It may be difficult to believe these days, but for quite some time, from the mid-1980s to the mid-2000s, software UIs were quite consistent on each major platform. Almost all Windows apps looked the same on any given version of Windows. Almost all Mac apps looked the same on any given version of Mac OS. Even on X, where there was no standard toolkit, at least a Motif-like theme was offered by most toolkits. There was even superficial similarity across these very different platforms, where the UIs consisted of very similar components, even if the appearance differed.
The important thing to remember is that all of that software predated the influx of hipsters into the computing industry. The hipsters flooded in starting around 2005, which corresponds exactly to the decline in user interface consistency. After a few years of work, these hipsters left us with UI disasters like all of modern web design (especially Slashdot Beta), Chrome, Firefox 4 and later, GNOME 3, and Windows 8.
Hipsters care only about the appearance of the UI. The usability of the software is not a concern to them. The appearance is what they deem to look "good", of course. So if, as a user, you find that the software looks bad and is difficult to use, then the hipsters insist that you are wrong and they are right.
Gedit is the best example I've seen of how the hipster approach to "design" can totally destroy a software user interface. Gedit, which is nothing more than a simple Notepad-like text editor, went from having consistent, usable interface to having this terrible farce of a user interface. That's right, they managed to fuck up the user interface of a text editor that badly!
At least the auto industry, in general, has kept these hipsters away from the physical dashboard. Yes, they have screwed up some of the software for in-car screens, but at least that functionality is non-critical.
.
Version updates:
.
Security and other interim updates:
It's the extortion model of OS pricing.
"Lovely little computer you have here. Shame if it got broken in an update. Just buy a little insurance and you can avoid all that."
Some of us run it at home, but since most of the work is done on Linux anyway, the whole auto updates was the last straw. It's kind of fun watching the distributed computing model morph back into the server based model that existed when I first got into programming.
-- Tigger warning: This post may contain tiggers! --
Still running OSX 10.6.8 -- an OS version ca. July 2011
Isn't broken in the sense that anything about it significantly impedes what I use the computer for; anything that was really crappy -- like Safari -- has been replaced with something that worked better.
Ergo, no need to "fix" it.
I have more interesting things to do with my time than adopt change for the sake of change.
There's a great deal positive that can be said for a stable OS environment, not the least of which is that software which I develop for it will work for more people than software that utilizes functionality only available from a later version of the OS. Speaking for myself, I view a statement about any application of the general form "requires late version of/latest OS" as an abject failure of the developer to think of the users.
That's not to say that others aren't, or shouldn't be interested in the latest OS version-- it's just that I am not, and that addresses the question that was asked.
I've fallen off your lawn, and I can't get up.
Wish this got more time on slashdot.
The 60% of the geography of the United States that does not have high-speed internet, or has low-speed data with data caps and no other options, NEVER get to update operating systems.
While no one should think they are entitled to high-speed internet, the fact is that outside large cities u.s. connectivity is just about the worst on the planet.
Many in rural areas can't even update an OS to a new version since everyone changed updates to be online-based.
Back in the days of physical media, we would just order a new version of the OS on disk. This is why I left Windows after Win2000 and went to Macs - OS on DVD's for less than $20 shipped to your home. For a while, Mac was the only way if you could not download. Well, you know what happened after Snow Leopard - no more Mac media.
In our small town of 530, there are 5 people with WIndows 7, because it came on the cheap pc/laptop they bought. A few still use Vista, 3 of us also have Mac Snow Leopard, and the rest of us have WinXP.
None of us have the 'internet' to update anything, so we don't. Our pc's still work as good as they did when we got them though.
We all run Ad blockers to minimize the misuse of our connections.
When you have little internet connection and use little of the internet, you don't seem to ever get viruses and malware though. A great trade-off.
Server: Latest with 1 week after patches released unless security mandated. This way let's see what else breaks.
Laptop/Desktop: Latest Windows with the above caveat. Apple update to the latest, no need to wait, apple patches so rarely. No Linux desktop/laptop (Who does that anymore?)
Phone/Mobile: Latest, always. Chances are if it breaks it's because of some rare use case some idiot did doing something equally stupid.
Gaming Consoles: Latest, do it, patch everything ASAP, go beta here for nifty new features!
Wheel of Time: Book by Book and Sumview (summary review) Bigdady92 style: http://bigdady92.blogspot.com/
Automotive control interfaces change all of the time.
But in most cases, the automobile someone drivers does not.
And when someone does change car, maybe every 5-10 years, getting up to speed with the new controls takes them a few minutes.
This is because, fair as the examples you give of evolving car controls might be, ultimately you still turn the steering wheel to change direction (and you turn it anticlockwise to turn left). When you get a different car, you still have the same gas and brake pedals you used to. If you drive a manual then you still have the same clutch pedal and probably a near-identical gear stick arrangement. The range of external lights and when you use them hasn't changed a lot in decades. The internal and external environment-related controls are still roughly the same. The changes are mostly cosmetic, more akin to changing visual themes in software than changing actual functionality to something significantly different that the user must then learn before they can use the software effectively again.
If software only changed its UI significantly every 5-10 years, and you could choose when to switch, and when you did it would still basically work the same way but you might have to spend five minutes figuring out where the main functions were found in the new version, I don't think users would be nearly as frustrated by the changes as so many are today.
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
I run Gentoo on my primary machines. Any guesses?
You know what ... just say no.
Unless you enjoy doing that kind of support for free, tell them they're on their own.
My parents live quite far from me. I told them flat out I can't be support for their computer because I have no way to see it, and I don't know WTF they did to it.
But why people keep letting themselves get sucked into the black hole of supporting technology for friends and family I will never know. There's no limit to how much you can get dragged into that crap.
Lost at C:>. Found at C.
We travel a lot and rent a lot of cars. It can range from being mildly annoying to almost hazardous, getting to know the controls for a new vehicle, especially when other things like the seat and mirror positioning will also have to be set.
True, the pedals and steering wheel haven't moved, and the actual turn signal stalk's basic signal-left and signal-right functions are unchanged, but as I said, the gearshift selector and everything else is up for grabs.
Do not look into laser with remaining eye.
I re-image mine from an image I made, stored on a server in the middle of the house. Every time the machine boots, it re-images the OS image on the local hard drive, thoroughly destroying anything else that might have been on the disk. When an update to the main image is necessary, I make a new one.
I create those once about every six months, unless there's an emergency patch like Heartbleed. This works on all of the computers in my home. Wife and daughter go through the same process on their machines.
Boot to Ghost, install os, play, run, do whatever. In the event of a virus, it's short lived. When I attended Berkeley, this was the way they had set up their computer lab. I remember, at the time, being intrigued by the setup.
Now that I have myself, my wife, and a five year old all using machines around the house (nine distinct pc's), I have a practical use application for this.
Since I implemented this about five years ago, we have had virtually no problems with it. The drawback of course is that it's a lot easier to do if your machines, desktops, laptops, etc, all match. Learned that one the hard way, but good now.
My machine gets shut down about once a week. My daughter is always letting the battery burn down on her laptop, so she images more frequently than anyone else in the house. My wife is also at about once a week.
This signature has Super Cow Powers
DOS 6.2 was good. 6.22 wasn't exciting, so I stopped there. Has anything notable changed?
Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
It depends on whether a machine is one on which I do work for which I get paid, or not. My main workstation, which is the source of my income, warrants a very conservative update approach. I was very slow in leaving XP, and with a mature, stable Windows 7 environment, I'm in no hurry at all to adopt another version of Windows. Yeah, like everyone else I've seen the popups inviting me to upgrade to Windows 10. You first. I can't afford to be down while I figure out why things aren't working or figuring out where Microsoft hid certain buttons this time.
I will sometimes install a new version on a spare machine just to see where technology is heading, and acquaint myself with what I will eventually have to deal with, but that's a lower priority. I'm not really interested in spending half my life doing upgrades and figuring out what broke.
Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
Automotive control interfaces change all of the time.
Really? The "control interface" of my '81 Ford is the same as the day it was purchased.
Well, the auto makers have "fixed" that problem in their latest models. They now have those little "onboard computers" that constantly scan many of the controls and figure out how to map them to physical actions. This means that any "upgrade" to the software can change the functioning of all the controls. You can think you're just getting an upgrade to improve the mileage, but that upgrade can flip the meaning of the turn-signal controls.
Some of the latest models have wifi, so they can do upgrades while you're traveling. We'll probably soon be hearing of accidents caused by a sudden change in meaning of what the driver did with the controls. (Yes, they may say the upgrades won't happen while the car is moving. What that means is that if you stop at a stop sign or light, when you start moving again, the controls may have silently changed. And if you think they wouldn't do upgrades without your permission, you haven't been paying attention.)
If computer-industry history is any guide, it'll probably take decades for all this to settle down to an intuitive, reliable auto UI. And the security problems still won't be solved, so your car can be taken over at any moment by "hackers" - or the police - or your insurance company.
(I wish I were joking ... but I'll probably get a "funny" mod for this anyway. ;-)
Those who do study history are doomed to stand helplessly by while everyone else repeats it.
I also have a friend who upgrades everything all the time. "the new phone's amazing" either means that the "old phone sucks" -- which makes no sense since the old phone was "amazing" when it was new too -- or that the new marketing is amazing -- which makes sense because the old marketing was also amazing.
There are countly amazing things that can be added to anything. Some new features are just really impressive. But being impressive doesn't mean that it improves my life at all.
A frisbee that can be thrown over a half-mile is really cool (and called an aerobe, by the way, and I love them) but I don't have a park that large, nor would I enjoy playing catch with a friend that far away.
Similarly, most new OS features might be neat, but they don't actually change my life at all. Perhaps the best example I can give is with regard to office/productivity suites.
Between word, excel, wordperfect, lotus 123, and-if-you-thought-wordperfect-was-dating-myself wordstar, I've been writing essays and poems and business documents for close to thirty years. Before the computer "clipboard", before 3d text-art, before pivot tables, before ribbon bars, before toolbars, before menu bars, before arrow-keys, even before the mouse. In the end, the business documents that I produce today, to earn a living, aren't any more sophistimicated than the ones that I producted 25 years ago, early in my career. Believe it or not, youngin's, business invoices and quotes and proposals existing before XML. So none of these new features actually provide any additional benefit to my life. They only change the way I create the very same invoice -- whether for dot-matrix, inkjet, laser, PDF, or e-mail.
How many new OS features actually add to my life? The answer is: none. So I upgrade my OS when I upgrade my computer. When is that? When my computer is too old to play the almost-latest games -- because games are entertainment, and entertainment is my sole purpose in life.
The OS is very definitely secondary.
All that said, there have been OS upgrades that have improved my life. Win 95 let me switch between games and work faster, which meant that I could play more games. Vista let me have more pixels so I could work more at a time and keep the tv playing in the corner at the same time. Win 7 added nothing. Win 8 added nothing. Win 10 would let me work cross-device better, if my work were capable of being done anywhere but a desk, but it ain't.
This is aggressively missing the point. The original poster was discussing the fact that you can hop in any modern car and know with certainty how to actuate the left or right hand turn indicators. His/her point is valid and true, but instead of addressing it you are now on about hazard lights.
I drive a car with the automatic transmission gear selector on the column. I have inadvertently turned on the windshield wipers a couple of times in the pickup with a floor-stick because the wiper controls on the truck are where the gearshift is on the car.
Do not look into laser with remaining eye.
I don't update my OS, ever.
The overlords living at 1 Infinite Loop, Cupertino, CA 95014 are the ones updating the OS for me.
Get free satoshi (Bitcoin) and Dogecoins
the Emacs vs VI war is over (Emacs won)
Nope. B-)
When I got my first UNIX box, back in the '80s, it had two megabytes and did NOT have demand paging, which would have allowe a larger virtual image to run. That was too small to compile emacs. (The joke at the time was that the name was really an acronym for Eight Megabytes And Constantly Swapping. B-) )
So I learned VI. Then I used it VERY heavily for years, on the original conferencing system whose software was later ported to The Well. After that a number of editing idioms were "wired into" my hindbrain and I could do the things I wanted to do with text very efficiently with vi.
As machines improved I tried emacs several times. Each time I found that the stuff I depended on took about 1.5 to 3 times as many keystrokes. This was too much of a penalty to pay for the handful of features it offered.
At one point I considered going to it but running in a vi emulator mode and gradually migrating to native idioms. But I discovered that, kitchen sink that it was, it had TWO vi emulator modes, each with distinct deviations from vi (alias "bug sets"). With one vi emulator, even with substantial shortcomings, I might still have made the shift. With two there was no easy way to chose, so I didn't bother.
Now I'm using vim, which is close enough. One of my regular colleagues is an emaxian rather than a vithian and we get along just fine. B-)
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way