Tho I've been current cooker all along (and consequently already  
at 9.1 final), I did a fresh install today. Fortunately I saved 
copies of pertinent adsl/eth0 related configs and a backup of my 
/home/tom directory, among other stuff.

   All'n all I was pleasantly surprised with the fresh install 
(regular, or what use to be 'recommended'). Great job, better than 
ever. Everything worked, just a coupl'a niggles and a potential real 
pisser off'r.

o   I again had to 'urpme alsa-utils' to prevent aplay from suckin on 
the cpu (100%), and enable sound. Same thing happened after the 
recent 'upgrade' with 9.1 final CD's. Onboard AC97,  snd-via82xx     
: VIA Technologies|VT82C686 [Apollo Super AC97/Audio]. And I had to 
run 'aumix' to move the sliders off -0-.  Then Kmix was functional, 
sound was fully restored.

o   Tho eth0 worked, it spent _many_ seconds during boot being 
enabled, finally "claiming" an address after tryin it several times.  
This was soon fixed by moving in the saved copy  of 
/etc/sysconfig/network- scripts/ifcfg-eth0

    The only difference between the '9.1 fresh install' file and the 
saved ifcfg-eth0 file was one line.  BOOTPROTO=static  from the saved 
file works, eth0 is just a split second pause during bootup. 
BOOTPROTO=dhcp, from the 'fresh' install caused the long wait and 
search. Connection is adsl, dynamic IP, auto DNS. (dsl line -> ATU-R, 
'often referred to as a modem' -> pci NIC 'D-Link TX538')

o   Now for the pisser.  I had previously done an upgrade with the d/l 
9.1 CD's, mainly to look at the installer. Everything was fine, no 
problems. I like the new simplicity, look'n feel, and ease.  Very 
fortunately it's my habit to regularly backup my user dir (/tom) to a 
storage partition, which I did just before I began todays fresh 
install.

    During the install I was presented with the options to format 
partitions other than the preselected '/'. I also chose /boot, to 
clean out a bunch of obsolete kernels. I was careful to make sure 
that none of the (many) partitions including /home, were _not_ 
selected.

    Still, on first boot, my 'old' /home/tom was wiped out, replaced 
by the beginning default one. Easily fixed by overwriting with the 
saved /tom dir. Could'a been a disaster tho.
-- 
    Tom Brinkman                  Corpus Christi, Texas

Reply via email to