Language Selection

English French German Italian Portuguese Spanish

Fedora 12, upgrade or fresh-install?

Filed under
Linux

Constantine, Fedora 12 is going to be out soon. I am really excited and I bet every linuxer will be equally excited and looking forward to try it out. Most of the you will be in a dilemma, whether to do an upgrade or a fresh-install? what's best for my system? In this article I will give you some tips and methods which will help you answer such questions.

Don't you just love your system after an upgrade or a re-install? The whole looks and feel has changed, sometimes things that were not working on your previous installation start working , its amazing. Even though you might not agree with me but I believe that the decision that you take at this point, if right, makes you love your new system even more.

Here are some points that you should know before starting:




Flip a coin.

First I back up my important data and try the upgrade option. If for any reason things go tits up then I do a fresh-install and restore my backed up data.

Upgrade should be fine

pacman -Syu

Pacman wacka wacka

Anonymo wrote:
pacman -Syu

What is tis pacman stuff?

re: pacman

yeah, ain't that arch? fedora is yummy.

Full install gives all the goodies

I doubt an upgrade would allow you to change your /boot to Ext4, while a new install will allow you to run the /boot on Ext4 and install Grub2 or whatever so it can boot from Ext4 (something missing until this Oct '09 + distribution versions).

grub2

drewgonbite wrote:
I doubt an upgrade would allow you to change your /boot to Ext4, while a new install will allow you to run the /boot on Ext4 and install Grub2 or whatever so it can boot from Ext4 (something missing until this Oct '09 + distribution versions).

Oh crap another grub2 distro release? pffffffft

Not grub2

No, Fedora does not use grub2. It uses grub.

re: grub2

one reputable online site said openSUSE used grub2 too, but they didn't. I think folks are getting confused with all the big distro releases so close together.

Fresh install FTW

Real unix/Linux users keep /home on a separate partition and never format it, this way a fresh install is faster than an upgrade.

Just keep note of the config files you edited in the past - shoudn't be more than two or three these days, Linux doesn't need much tweaking anymore - and apply the same changes to the new installation, if still necessary.

Real unix/Linux users also use xfs and not ext4, because xfs is just as efficient but has the advantage of being a proven workhorse: It's been on high-end unix workstations for decades, working through entire projects (from CAD engineering to complex simulations) without a reboot.

wow.

wow, exclude people much? I use ext4, apparently I'm not a 'real unix/Linux user' now? last I checked, Linus uses ext4 too...

Re: wow.

It was more like banter actually, I do make the choices I expressed but far from me the intention of excluding anybody, let alone AdamW and Linus =:O

re: ext4

Is it just me or is ext4 slow? I know it must just be me cause wasn't speed one of its touted features? But every time I install on ext4, the system seems very slow. I tend to do better with ext3. Weird huh?

ext3 vs ext4

srlinuxx wrote:
Is it just me or is ext4 slow? I know it must just be me cause wasn't speed one of its touted features? But every time I install on ext4, the system seems very slow. I tend to do better with ext3. Weird huh?

Me too! Whats up with that??

ext4 performance

Phoronix comprehensive filesystems benchmark:
http://www.phoronix.com/scan.php?page=article&item=ext4_benchmarks&num=1

It shows that the perceived speed of each filesystem depends on what you do with your computer, because the top contenders - ext3/4 and xfs - are very close to each other, each excelling at different tasks.

I would add though that xfs has an online defrag utility that's far more full featured than e4defrag, so it remains to see how the comparison would look like after one year of usage and doing the correct maintenance to the fs.

Unix filesystem fragmentation is low but it does exist, and if you move around multimedia files day in and day out like in the typical home desktop usage, its effects can be noticed IMO.

BTRFS will catch up with and surpass xfs in speed AND features, with real online defragmentation too; ext4 is an incremental update that doesn't dramatically change the game.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Leftovers: BSD

Security Leftovers

  • Stop using SHA1 encryption: It’s now completely unsafe, Google proves
    Security researchers have achieved the first real-world collision attack against the SHA-1 hash function, producing two different PDF files with the same SHA-1 signature. This shows that the algorithm's use for security-sensitive functions should be discontinued as soon as possible. SHA-1 (Secure Hash Algorithm 1) dates back to 1995 and has been known to be vulnerable to theoretical attacks since 2005. The U.S. National Institute of Standards and Technology has banned the use of SHA-1 by U.S. federal agencies since 2010, and digital certificate authorities have not been allowed to issue SHA-1-signed certificates since Jan. 1, 2016, although some exemptions have been made. However, despite these efforts to phase out the use of SHA-1 in some areas, the algorithm is still fairly widely used to validate credit card transactions, electronic documents, email PGP/GPG signatures, open-source software repositories, backups and software updates.
  • on pgp
    First and foremost I have to pay respect to PGP, it was an important weapon in the first cryptowar. It has helped many whistleblowers and dissidents. It is software with quite interesting history, if all the cryptograms could tell... PGP is also deeply misunderstood, it is a highly successful political tool. It was essential in getting crypto out to the people. In my view PGP is not dead, it's just old and misunderstood and needs to be retired in honor. However the world has changed from the internet happy times of the '90s, from a passive adversary to many active ones - with cheap commercially available malware as turn-key-solutions, intrusive apps, malware, NSLs, gag orders, etc.
  • Cloudflare’s Cloudbleed is the worst privacy leak in recent Internet history
    Cloudflare revealed today that, for months, all of its protected websites were potentially leaking private information across the Internet. Specifically, Cloudflare’s reverse proxies were dumping uninitialized memory; that is to say, bleeding private data. The issue, termed Cloudbleed by some (but not its discoverer Tavis Ormandy of Google Project Zero), is the greatest privacy leak of 2017 and the year has just started. For months, since 2016-09-22 by their own admission, CloudFlare has been leaking private information through Cloudbleed. Basically, random data from random sites (again, it’s worth mentioning that every site that used CloudFlare in the last half year should be considered to having fallen victim to this) would be randomly distributed across the open Internet, and then indefinitely cached along the way.
  • Serious Cloudflare bug exposed a potpourri of secret customer data
    Cloudflare, a service that helps optimize the security and performance of more than 5.5 million websites, warned customers today that a recently fixed software bug exposed a range of sensitive information that could have included passwords and cookies and tokens used to authenticate users. A combination of factors made the bug particularly severe. First, the leakage may have been active since September 22, nearly five months before it was discovered, although the greatest period of impact was from February 13 and February 18. Second, some of the highly sensitive data that was leaked was cached by Google and other search engines. The result was that for the entire time the bug was active, hackers had the ability to access the data in real-time by making Web requests to affected websites and to access some of the leaked data later by crafting queries on search engines. "The bug was serious because the leaked memory could contain private information and because it had been cached by search engines," Cloudflare CTO John Graham-Cumming wrote in a blog post published Thursday. "We are disclosing this problem now as we are satisfied that search engine caches have now been cleared of sensitive information. We have also not discovered any evidence of malicious exploits of the bug or other reports of its existence."

Security Leftovers

  • Change all the passwords (again)
    Looks like it is time to change all the passwords again. There’s a tiny little flaw in a CDN used … everywhere, it seems.
  • Today's leading causes of DDoS attacks [Ed: The so-called 'Internet of things' (crappy devices with identical passwords) is a mess; programmers to blame, not Linux]
    Of the most recent mega 100Gbps attacks in the last quarter, most of them were directly attributed to the Mirai botnet. The Mirai botnet works by exploiting the weak security on many Internet of Things (IoT) devices. The program finds its victims by constantly scanning the internet for IoT devices, which use factory default or hard-coded usernames and passwords.
  • How to Set Up An SSL Certificate on Your Website [via "Steps To Secure Your Website With An SSL Certificate"]
  • SHA-1 is dead, long live SHA-1!
    Unless you’ve been living under a rock, you heard that some researchers managed to create a SHA-1 collision. The short story as to why this matters is the whole purpose of a hashing algorithm is to make it impossible to generate collisions on purpose. Unfortunately though impossible things are usually also impossible so in reality we just make sure it’s really really hard to generate a collision. Thanks to Moore’s Law, hard things don’t stay hard forever. This is why MD5 had to go live on a farm out in the country, and we’re not allowed to see it anymore … because it’s having too much fun. SHA-1 will get to join it soon.
  • SHA1 collision via ASCII art
    Happy SHA1 collision day everybody! If you extract the differences between the good.pdf and bad.pdf attached to the paper, you'll find it all comes down to a small ~128 byte chunk of random-looking binary data that varies between the files.
  • PayThink Knowledge is power in fighting new Android attack bot
    Android users and apps have become a major part of payments and financial services, carrying an increased risk for web crime. It is estimated that there are 107.7 million Android Smartphone users in the U.S. who have downloaded more than 65 million apps from the Google App Store, and each one of them represents a smorgasbord of opportunity for hackers to steal user credentials and other information.
  • Red Hat: 'use after free' vulnerability found in Linux kernel's DCCP protocol IPV6 implementation
    Red Hat Product Security has published details of an "important" security vulnerability in the Linux kernel. The IPv6 implementation of the DCCP protocol means that it is possible for a local, unprivileged user to alter kernel memory and escalate their privileges. Known as the "use-after-free" flaw, CVE-2017-6074 affects a number of Red Hat products including Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7 and Red Hat Openshift Online v2. Mitigating factors include the requirement for a potential attacker to have access to a local account on a machine, and for IPV6 to be enabled, but it is still something that will be of concern to Linux users. Describing the vulnerability, Red Hat says: "This flaw allows an attacker with an account on the local system to potentially elevate privileges. This class of flaw is commonly referred to as UAF (Use After Free.) Flaws of this nature are generally exploited by exercising a code path that accesses memory via a pointer that no longer references an in use allocation due to an earlier free() operation. In this specific issue, the flaw exists in the DCCP networking code and can be reached by a malicious actor with sufficient access to initiate a DCCP network connection on any local interface. Successful exploitation may result in crashing of the host kernel, potential execution of code in the context of the host kernel or other escalation of privilege by modifying kernel memory structures."

Android Leftovers