F7T1 install experience

[Jonathan Berry]

Hi all,
I gave installing F7T1 x86_64 a try last night.  First thoughts...
whew, that was messy...

First hitch I encountered was a problem reading from the DVD in my IDE
DVD burner.  I believe this issue has been noted.  I have a Gigabyte
socket 939 motherboard with the nForce4 chipset.  I had to load the
pata_amd module to get it to see the DVD.  At little guess-work made
this minor.

Setup and install went pretty well.  Installed to a single partition
with Ext3 filesystem (no LVM or anything).  Since I'm multi-booting
with WinXP and FC6 I wanted to install grub to the boot sector of the
partition I was installing to (sda7).  When it came time to install
grub at the end, Anaconda blew up with a Python backtrace.  Bugziila:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=227782

I rebooted to see what damage had been done.  I tried to chainload to
(hd0,6) to see if grub had been installed and it had not.  So I booted
directly with some manual grub commands.  Thankfully I am fairly
familiar with grub.  F7T1 booted to a TUI (no graphical at this point)
where I could setup things like the network, firewall/SELinux, etc.  I
looked around a little then went on past it.  It booted to a console,
so I logged in as root.  I did a "grub-install /dev/sda7" which seemed
to work.  Testing with a reboot (later) confirmed it did.

Wanting to get X up and running, I tried system-config-display, which
I quickly found was not installed.  I'm not sure if that is normal, I
decided not to customize anything in the install.  Installed it with
yum, ran "system-config-display --reconfig" and X was up and running
(nvidia card, using nv drivers).  I do not know if X was configured
prior to this or not.  I assumed that since it did not start that it
was not.  However, I found inittab set to default to runlevel 3, so
that is the main reason X did not start.  Why it was set to 3, I do
not know.

That's everything for the install.  I am having some issues on startup
(some SELinux problems, it seems) and I am not sure the RPM database
is currently healthy.  These could be a result of the not *quite*
finished install.  I need to investigate that further.  Other than
that, things do not seem to badly broken.

Jonathan