<div dir="ltr">If you're starting from scratch, I can't speak highly enough about configuration management tools like Chef, Puppet, Ansible, cfengine, etc. The time spent getting up to speed will pay itself back many times over. Reinstalls become a non event. Finding out "what changed" isn't an issue. You can spin up new boxes, even if there are customizations to each one.<div>
<br></div><div>As an aside, you don't need to start from scratch to make use of config management. If you can just start off managing your motd and ntpd on existing boxes, you'll soon start finding reasons to bring stuff under config management rather than one offs.</div>
<div><br></div><div><a href="http://ertw.com/chef-walberg-winnipegrb/">http://ertw.com/chef-walberg-winnipegrb/</a> is a presentation I gave at WinnipegRB about some of the work I was doing with Chef at the time. While the demo is obviously missing there are some code snippets at the end that show what you can do with the tools.<br>
<div><br></div><div><div>Sean<br><div><br></div></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 26, 2014 at 4:00 PM, Trevor Cordes <span dir="ltr"><<a href="mailto:trevor@tecnopolis.ca" target="_blank">trevor@tecnopolis.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 2014-08-26 Gilbert E. Detillieux wrote:<br>
> > <a href="http://archive09.linux.com/feature/123800" target="_blank">http://archive09.linux.com/feature/123800</a><br>
><br>
> Good luck with that... :)<br>
<br>
</div>Oops, doh! Turns out F20 (actually as of F17?) the DVD install method<br>
no longer contains an "upgrade" option. As in anaconda can't do it<br>
anymore. That removes the "offline" option which makes changing arches<br>
easier/possible.<br>
<br>
Instead they want one to use fedup, which, from what I can tell,<br>
appears to be nothing more than a glorified "yum upgrade". It strikes<br>
me as odd, as fedup provides a new specialized initrd but then says it<br>
boots into your system "mostly" as normal so it can mount all your<br>
disks, etc. Then does the upgrade while the system is all running. Uh,<br>
ok.<br>
<br>
Anyhow, I see ZERO instructions on google on tricking fedup to switch<br>
32->64, and the few people who have asked have gotten a firm "NO, DON'T<br>
BE INSANE" response. I'm not sure I want to be the very first to try!<br>
<br>
(One would think you could possibly install a 64 kernel on my F19<br>
system with 32b userland, boot into that, trick fedup or yum into<br>
thinking it's 64-bit, etc. But perhaps that would break badly as<br>
whilst yum is running it'll pull the rug out on libraries, programs,<br>
etc, by changing them to 64 on the fly. Who knows, maybe it would<br>
work, maybe it would blow up badly.)<br>
<div class=""><br>
> I'm with you on that one! I've always found that to be the biggest<br>
> pain about complete reinstalls. (You think you've got a complete set<br>
> of config files for all your customisations, only to find that you've<br>
<br>
</div>Sigh, it looks like I may be forced into a wipe/reinstall. I've made<br>
dd image backups of my drives so I may still give yum or fedup a stab.<br>
Nothing to lose, really.<br>
<br>
I'm always shocked yum upgrade works at all, even when arch remains the<br>
same, so perhaps if it can survive the carpet-yanking there, it can<br>
survive it when going 64. Who knows.<br>
<br>
Thanks for the help.<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
Roundtable mailing list<br>
<a href="mailto:Roundtable@muug.mb.ca">Roundtable@muug.mb.ca</a><br>
<a href="http://www.muug.mb.ca/mailman/listinfo/roundtable" target="_blank">http://www.muug.mb.ca/mailman/listinfo/roundtable</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Sean Walberg <<a href="mailto:sean@ertw.com" target="_blank">sean@ertw.com</a>> <a href="http://ertw.com/" target="_blank">http://ertw.com/</a>
</div>