David Both - David Both is a Linux and Open Source advocate who resides in Raleigh, North Carolina. He has been in the IT industry for over forty years and taught OS/2 for IBM where he worked for over 20 years. While at IBM, he wrote the first training course for the original IBM PC in 1981. He has taught RHCE classes for Red Hat and has worked at MCI Worldcom, Cisco, and the State of North Carolina. He has been working with Linux and Open Source Software for almost 20 years. David has written articles for.

1. Free Fedora 16 Download
2. Linux Mint 12

For ages I have used the 'unsupported' yum update method documented here: With the exception of the systemd debacle around about Fedora 16 or 17, this method has worked like a charm and kept systems on-line as much as possible. You do have to pay attention to dependencies and may have to resolve issues and restore packages, but it worked. I've had a few (virtual) machines that where upgraded using this method from Fedora 1 in a continuous chain to Fedora 23 (although systemd require some serious recovery efforts). For me this has been the best approach for remote systems (as in hours of driving time remote) where you simply can NOT have them off-line during the upgrade process. Fed-up, which was vastly superior to 'preupgrade: was worthless to me because it used anaconda and took the machine off-line during the upgrade and, if anything goes wrong, you could get screwed real fast with a remote machine. In addition to the straight forward manual 'dnf -releasver=' method documented in that URL, the URL above points out that they have created a (YES UNSUPPORTED) script to automate most of it.

That's the fedora-upgrade package. Yes it's 'unsupported' but it should be supported. The only failures I've run into it are dependency errors that should not be in the rpm repos to begin with. Things like circular dependencies and broken obsolete dependencies. If they actually supported the fedora-upgrade process, they would be force to fix those broken dependencies.

Fortunately, the problems been easy to work around and get a clean upgrade with virutally no downtime or loss of control of my remote servers. Just backup a database of your installed packages and delete any offending package (often rpmfusion) and then reinstall after the upgrade.

If there is any problem I have seen in recent years, it's that there hasn't been enough testing on old hardware. I suppose like many, I have a collection of computers of varying age, that I keep running 'just in case'.

Free Fedora 16 Download

Maybe it's a version of hoarding, but let me say this: my hoarding allowed me to be able to recover some files I had saved on some ZipDisks, using some old hardware that could still manage the connectors on my ZipDisk drive. I ended up skipping over Fedora 22, and waited for 23, since as far as I could tell, there wasn't any recognition or fix for issues with my Intel graphics chip.

Once you spend an entire weekend upgrading, only to have to downgrade to the prior version, you don't feel like going through that again any time soon, and this was with making backups (fortunately). I've had some catastrophic failures with these 'automatic' upgrades. It seems so cool, in that you don't have to load all the individual bits and pieces for your unique situation after upgrading, but when it doesn't work.ugh! And it is VERY time-consuming. My preferred way to upgrade is a backup, then doing a netinstall. For more discussion on open source and the role of the CIO in the enterprise, join us.

The opinions expressed on this website are those of each author, not of the author's employer or of Red Hat. Opensource.com aspires to publish all content under a but may not be able to do so in all cases. You are responsible for ensuring that you have the necessary permission to reuse any work on this site. Red Hat and the Shadowman logo are trademarks of Red Hat, Inc., registered in the United States and other countries.

Linux Mint 12

This manual explains how to boot the Fedora installation program, Anaconda, and how to install Fedora 26 on 32 and 64-bit AMD and Intel systems. It also covers advanced installation methods such as automated Kickstart installations, booting the installation from a network location, remote access to the installation system using VNC, and system upgrades from previous versions of Fedora. It also describes common post-installation tasks and explains how to troubleshoot common issues related to the installation.