Mailinglist Archive: opensuse (2425 mails)

[klcroxen@xxxxxxxxxxxxxxx (klcroxen@xxxxxxxxxxxxxxx)]

Part of the problem would appear to be a 
significant space crunch. 6.3/6.4 have 
*minimum* installs running well over 600
Megs. To squeeze 6.4 into the space you
evidently have available (and still have
room for actual apps) would require
some really ruthless package pruning
in the initial install phase. Plain
upgrade just won't do it.

Plus moving from the 2.0.x to the 2.2.x
kernels is/was frequently a dicey and
frustrating process via upgrade. So for
both those reasons you'd be better off
with backing up and installing cleanly.
(A good 2 Gig drive added prior to the
"installing cleanly" part certainly 
wouldn't hurt either...)

--Kevin

On Thu, 22 Jun 2000, Mike Kenzie wrote:

> 
> I'm trying to upgrade my old machine from 5.2 to 6.3.
> 
> I just put the CDrom back in and added a second HD.
> 
> When I tried to do the ugrade from .79 yast
>  it said the CD was from another yast and to boot from the
> boot disk.
>  I did that then setup the swap partitions.
> 
> It searched the disk and then started the update.
> 
> it ends with a red screen and a  error message on VT3
> 
> Error Open Output File, detail: 0 File systemCmd.cc
> line 530 YAST Return Code 256 (errno = 4)
> 
> I had a similar error on another old machine yesterday.
> Both machines have small drives.
> 
> Machine 1 hda is 202 meg, hdb 420 meg 8 meg RAM, 486-33
> 
> Machine 2 hda is 202 meg, 12 meg RAM, 486-66
> 
> 
> -- 
> 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/
> 


-- 
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/