Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Oil changes, safety recalls, and software updates

daemonology.net

Post reply on HN
Print view View original

41–50 of 61 posts

Re: Oil changes, safety recalls, and software updates

#41

Post by jacquesm »

TeMPOraL wrote: post #37
jacquesm wrote: post #26

The biggest change will not come from getting users to upgrade, it will come from producing higher quality software in the first place.

Sure, but if we're in dreamland, then I think the second biggest factor will be making security upgrades invisible to users. If you could ensure that you can upgrade any part of your OS/application while it's running, without ever requiring a reboot, then the problem disappears as you can simply stop asking people when they want a security patch. In terms of safety, not much good comes from asking people. (That, or l…

That's fine, but it would require companies to abide by the rule of security updates being just that, security updates and not ways to push their corporate agenda after the fact, accidentally bricking your computer (or maliciously), installing spyware, adware or or other junk.

Re: Oil changes, safety recalls, and software updates

#42

Post by alkonaut »

woliveirajr wrote: post #32
alkonaut wrote: post #14

Earlier quoted context omitted.

You must have missed that he drives 2000 not 20000 km per year. He says he changes oil around every year, so every 2000km (1200 miles). If he changed every 6 months, he'd be changing every 1000km. That's insane! I don't even refuel every 1000km! Example oil change schedule for a modern car (Taken from Audi Q7 '09 service manual): 8.000km, 25.000km, 40.000km, 55.000km... So ~15.000km between changes - or 7.5 years if…

Refuel every 1000km... I envy you. Could you share some details, as it made me curious ?

Audi A6 diesel (yes very much a dirty VW/Audi diesel-gate diesel, although supposedly "fixed" now). It does 40-45 mpg US (5.5-6L/100km) and the tank is just bottomless (17 gallons/65L or something?)

> I envy you.

Still envy me when I say a full tank is $100? :)

Re: Oil changes, safety recalls, and software updates

#43

Post by bluGill »

x0x0 wrote: post #2

I'll admit to putting off applying security patches because my laptop is a giant repository of state and it's a pita to bring it all back up again. I have to remember how to start postgres, the erb command to make rails work, figure out how my upgrade to bash subtly broke virtualenvwrapper, make sure I didn't accidentally leave anything open in vim in some random window or go through the whining about vim swap files,…

Most people in this situation are forced to reboot at some point because of critical failure (power, or something physically break). Thereafter they carefully reboot on a regular schedule to just ensure everything will come up after the unplanned emergency reboot.

Re: Oil changes, safety recalls, and software updates

#44

Post by mcculley »

King-Aaron wrote: post #5

While I totally agree with most of the article, it made me grind my teeth at the frequency the author changes the oil in their car... That poor valvetrain will be full of gummy carbon deposits. RIP whoever buys the car second-hand.

This is one of the most common mesofacts I run across. It's a typical example of something that has changed, but was drilled into people's brains as important a long time ago.

Re: Oil changes, safety recalls, and software updates

#45

Post by JoeAltmaier »

miahi wrote: post #7
King-Aaron wrote: post #5

While I totally agree with most of the article, it made me grind my teeth at the frequency the author changes the oil in their car... That poor valvetrain will be full of gummy carbon deposits. RIP whoever buys the car second-hand.

I always wondered how this oil-change scam still continues in the US. Modern cars with synthetic oils don't need an oil change every 3-4 months or 3000 miles. I always changed the oil according to the (European or Japanese) manufacturer's schedule (once a year / every 10-15000km) and had no issues with the cars (even >10 years old cars).

My Subaru Forester gets an effective oil change every 2500 miles. It burns a quart of synthetic in that time. Too little to get the recall work done (faulty rings). But at least the car gets a gradual oil change over the year!

Re: Oil changes, safety recalls, and software updates

#46

Post by jstanley »

King-Aaron wrote: post #5

While I totally agree with most of the article, it made me grind my teeth at the frequency the author changes the oil in their car... That poor valvetrain will be full of gummy carbon deposits. RIP whoever buys the car second-hand.

Almost no car dies because the engine is worn out due to infrequent oil changes, unless the owner just doesn't change the oil at all.

Cars usually get scrapped for some problem that is uneconomical to fix due to the age of the car, long before the engine is worn out.

Re: Oil changes, safety recalls, and software updates

#47

Post by JoeAltmaier »

jstanley wrote: post #46
King-Aaron wrote: post #5

While I totally agree with most of the article, it made me grind my teeth at the frequency the author changes the oil in their car... That poor valvetrain will be full of gummy carbon deposits. RIP whoever buys the car second-hand.

Almost no car dies because the engine is worn out due to infrequent oil changes, unless the owner just doesn't change the oil at all. Cars usually get scrapped for some problem that is uneconomical to fix due to the age of the car, long before the engine is worn out.

Anecdotally, my Camry had 3 engines before it was involved in an accident well north of 200,000 miles.

Re: Oil changes, safety recalls, and software updates

#48

Post by StavrosK »

jacquesm wrote: post #25
StavrosK wrote: post #18

Earlier quoted context omitted.

Do this, and you'll thank me: https://www.stavros.io/posts/provisioning-your-computer-one-...

Was that blog post meant to end like that? It looks as if a lot is missing. The last lines for me read: "The main script First, let’s start with the main Ansible script: ~~~yaml This playbook is meant to provision a new computer. Run with: ansible-playbook -i , provision.yml"

Oops, no, I recently migrated to a static site generator and some posts broke. I'll fix it now, thanks Jacques.

EDIT: Phew, fixed, good catch, thanks. There was a triple dash in the article, which Lektor interpreted as the end of the post :/

Re: Oil changes, safety recalls, and software updates

#49

Post by StavrosK »

z29LiTp5qUC30n wrote: post #28
StavrosK wrote: post #18

Earlier quoted context omitted.

Do this, and you'll thank me: https://www.stavros.io/posts/provisioning-your-computer-one-...

Or better yet https://nixos.org/ Make state something exactly defined.

That's good, but you need to move to a whole new OS :(

Re: Oil changes, safety recalls, and software updates

#50

Post by jacquesm »

StavrosK wrote: post #48
jacquesm wrote: post #25

Earlier quoted context omitted.

Was that blog post meant to end like that? It looks as if a lot is missing. The last lines for me read: "The main script First, let’s start with the main Ansible script: ~~~yaml This playbook is meant to provision a new computer. Run with: ansible-playbook -i , provision.yml"

Oops, no, I recently migrated to a static site generator and some posts broke. I'll fix it now, thanks Jacques. EDIT: Phew, fixed, good catch, thanks. There was a triple dash in the article, which Lektor interpreted as the end of the post :/

Hehe, one of those painless migrations ;)

At least you found the cause.

Post reply on HN