Mailinglist Archive: opensuse (2234 mails)

< Previous Next >
[SLE] 6.2 install hosed
  • From: alex@xxxxxxxxxxxxxxxxxxxxxxx (Alex Angerhofer)
  • Date: Tue, 14 Sep 1999 04:55:56 -0400 (EDT)
  • Message-id: <199909140855.EAA03447@xxxxxxxxxxxxxxxxxxxxxxx>



Hi list,

here is my sad story of trying to upgrade my work box from 6.0 to 6.2.
There are a number of things that went wrong. While some of them
certainly go on my account, it also seems that YaST is not quite
sure about what it is doing.
First of all, the new sendmail.cf that YaST produced never cut meat.
My box was bounced off of e-mail for more than two days until I finally
realized that I had to substitute YaST's sendmail.cf with the old one
which was dumped to sendmail.cf.rmpnew. Please, note, that I had
net access during all that time and could freely ssh from and to my
machine.
The other big problem is that YaST doesn't install the new kernel image.
Whenever I reboot from HD I get the 2.0.36 kernel started which
lands me in the swamps. This happens even though I have now selected
and installed the new kernel image via YaST x number of times. Luckily
my tried and true boot floppy will get me into 2.2.10. I guess, I
will have to eventually make my own kernel and install that by hand.
By the way, trying to role my own kernel didn't work when I tried it
(didn't try hard enough probably and without the necessary tweaking).
make zImage or bzImage dumped a load of errors on me.
Okay, I got sendmail.cf back in order and went on with the install.
Saw that my old partitions didn't cut it for staroffice and decided
to divide the 7.8 GB /usr/local partition into two smaller pieces one of
which became /opt. Since I didn't want to do all the config files again,
I left the root partition alone and only partitioned the later ones.
Then went on with my install of staroffice. Well, I sort of thought that
killing /usr/local wouldn't go too well with the already installed
packages. In fact, SuSEconfig choked and I ended up with a login
prompt that wouldn't accept a user name :-(. Had to hard reboot and
replace the base package. From there I went on to hand-select further
packages for installation. Apparently, some of the earlier installed
packages are also hosed, since I can't get KDE to start up correctly.
Well, I guess, I will have to overwrite and reinstall all the packages,
just to be on the safe side :-(.
Still would be interested to hear if someone else had similar problems
with an upgrade that involved a partial repartitioning of their HD.
There is a further issue here that might cause problems. Would the fact that
I created the /opt as a new partition while it was still on the untouched
root directory tree cause problems? How would I get around these without
repartitioning the whole drive?

Best regards, Alex.


--
To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/


< Previous Next >
This Thread
  • No further messages