Re:Oil changes, safety recalls, and software updates
by StavrosK on Wednesday June 14, 2017 @06:53AM
(#14551838)
Do this, and you'll thank me:
https://www.stavros.io/posts/provisioning-your-computer-one-...
Re:Oil changes, safety recalls, and software updates
by jacquesm on Wednesday June 14, 2017 @07:53AM
(#14552048)
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"
Re:Oil changes, safety recalls, and software updates
by StavrosK on Wednesday June 14, 2017 @11:10AM
(#14553299)
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
by jacquesm on Wednesday June 14, 2017 @11:40AM
(#14553518)
Hehe, one of those painless migrations ;)
At least you found the cause.
Re:Oil changes, safety recalls, and software updates
by StavrosK on Wednesday June 14, 2017 @01:26PM
(#14554316)
Ugh, tell me about it, it took days :( Thanks again!
Re:Oil changes, safety recalls, and software updates
by z29LiTp5qUC30n on Wednesday June 14, 2017 @08:34AM
(#14552231)
Or better yet
https://nixos.org/
Make state something exactly defined.
Re:Oil changes, safety recalls, and software updates
by StavrosK on Wednesday June 14, 2017 @11:14AM
(#14553327)
That's good, but you need to move to a whole new OS :(
Re:Oil changes, safety recalls, and software updates
by bluGill on Wednesday June 14, 2017 @10:36AM
(#14553019)
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
by aargh_aargh on Wednesday June 14, 2017 @05:18AM
(#14551521)
Solution for you: more frequent updates. Breaks less stuff at a time.
Re:Oil changes, safety recalls, and software updates
by rwallace on Wednesday June 14, 2017 @11:59AM
(#14553638)
But breaks stuff more often. Why would that be a net win? Probably a net loss because you incur the mental overhead of putting down whatever actual problems you are trying to solve and getting into a frame of mind to try to fix your computer, more frequently.
Re:Oil changes, safety recalls, and software updates
by aargh_aargh on Thursday June 15, 2017 @02:22PM
(#14562970)
Let's sum up the available options:
1) update rarely, fix a lot of breakage at a time
2) update daily, run into each breakage as soon as it happens and fix it
3) never update, no need to fix anything
Re:Oil changes, safety recalls, and software updates
by AnimalMuppet on Thursday June 15, 2017 @03:01PM
(#14563376)
The problem with #3 is that, while there are no updates to break things, there are also no updates to fix things, so whatever is broken will stay broken.
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, and dump/restore all the state spread through 20+ browser windows, probably 30+ bash instances, and a couple repls. etc. It's really fucking annoying.
Another thing that ate 3 hours of my life recently: post reboot, zoom.us, which previously worked flawlessly, no longer works. I of course discover this as a meeting is starting.