On Sat, 2020-02-15 at 22:23 -0500, David wrote:
I am not the sharpest tool in the shed, but I resolved my Rawhide update problem
all on my own.

The trick was to first run "dnf install redhat-rpm-config"

I think that is all there was too it.

I installed a lot of packages manually, but I do not think that was necessary.

My Rawhide install now has about seventy fc33 packages.       And lots of the
anaconda packages seemed to clear out.

Everything installed !!

I am too scared to reboot.    But probably will anyways.

I am curious now whether my system will say I am on Fedora 33, if
it reboots successfully ??

David Locklear
Fedora Rawhide Novice Level 0.0.0.2
Arcola, Texas USA

David,

If you want a simple way to see exactly what kernel you're running, type:

uname -a

If you want to know the familiar name of the OS you are running, type:

cat /etc/fedora-release

If you REALLY want to get fancy, edit your /etc/bashrc file using vim or equivalent editor. Look for the following three lines about 52 lines into the file:

# Turn on checkwinsize
    shopt -s checkwinsize
    [ "$PS1" = "\\s-\\v\\\$ " ] && PS1="[\u@\h \W]\\$ "

Replace the third line with this:

    [ "$PS1" = "\\s-\\v\\\$ " ] && PS1="\n\\033[1;31m`cat /etc/redhat-release`\n\\033[1;34m`date +%A` - `date +%B` `date +%d`, `date +%Y`  \\033[0;32m\t `date +%Z`\n\033[0;36m[\u@\h:\l] \\033[1;33m\w\\033[0;37m\n\\$ "

(Make sure you use back ticks rather than single quotes.) This will give you a complex colorful multi-line xterm prompt that will dress up your terminal sessions.

If you like running Rawhide simply because it has a cool name, you should probably have heeded your mother's warning not to run with scissors. I've been using Fedora since its initial release, and Red Hat Linux before that. I remember the wreckage in the early days when I (ignorantly) tried installing every (!) package in what was then Rawhide. Talk about your major train wreck. I eventually learned to install development versions of Fedora (starting with the Beta release) only in a VM so any serious oops wouldn't destroy my day-to-day working files in /home.

It's up to you, of course. Just a bit of no-cost advise from a long-time user to a new guy.

--Doc Savage
Fairview Heights, IL