Mailinglist Archive: opensuse (3261 mails)

["Konstantin (Kastus) Shchuka" <kastus@xxxxxxxxx>]

On Sat, Mar 31, 2001 at 08:06:58PM +0200, filip wrote:
> Hi,
> 
> That's why a /home independant partition is appreciated !
> Let us remember that SuSE 7.1 distribution must work with the 2.2.18 and 2.4 
> kernel. As SuSE had to include 2.4 ( already promised in 7.0) , I think it 
> was a rush at that time to put everything together.
> Anyway, mostly, 7.1 works fine and I didn't experiment a major problem the 
> first time upgrading from 7.0 to 7.1.
> As home users we always want the latest and the best !!!! So my approach was 
> to test 2.4 in the beginning, with unsatisfied results. Then 2.4.2 from 
> kernel.org was released and decided to go for it. etc...... Finaly, I removed 
> 2.2.18 and only have 2.4.2 
> I still consider 7.0 and 7.1 as a "kernel" transition. We should help SuSE by 

The biggest transition is not kernel, but libc, which is finally 2.2 now.

-Kastus

> giving them all bad or good feedback so they can make a rock solid distro.
> Still speaking as home user, "the harder way we learn, the better we 
> understand". But there should be a limit!!!!
> Have fun with 7.1
> Filip.
> 
> 
> 
> Le Samedi 31 Mars 2001 09:39, vous avez ?crit :
> > I learned the hard way that the best way to upgrade is clean install.
> >
> > I tried to upgrade 7.0 to 7.1. The net result is X server which does not
> > start, yast2 does not start, a lot of packages missing files.
> > Finally, after a lost day of work I did a clean install.
> > My /home was on a separate partition, and I saved my /etc from 7.0
> > before doing clean install.
> >
> > It looks like we are back to Slackware circa 1995 when a new realease
> > of distribution meant a clean install. RPM and YaST supposed
> > upgradeability of the system. But now the difference even between
> > the releases within one major version number appear to be too big.
> >
> >
> > -Kastus
> >
> > On Sat, Mar 31, 2001 at 01:54:41AM -0500, Rick Green wrote:
> > > I'm in the process of doing an upgrade from 6.4 to 7.1.  yast2 presented
> > > me with three packages which had *lower* version numbers on the 7.1
> > > distribution, than I had loaded from the 6.4 distribution.  I told it to
> > > go ahead and replace the packages anyway, figuring that you must know
> > > something I don't know.
> > >   In other upgrades, I've encountered some packages which were 'split'
> > > into two or more new packages.  Since I just told it to replace existing
> > > packages, and then add the minimum of new packages to resolve
> > > dependencies, will I have a complete system?  Is there some list
> > > somewhere of 'split' packages, so I will know which packages I have to
> > > install to get back the full functionality I had?
> > >   How about 'renamed' packages?  Are there any packages which contain the
> > > same programs, but which go by different names between 6.4 and 7.1?  Will
> > > I have to manually uninstall the old and install the new ones?
> > >
> > > --
> > > Rick Green
> > >
> > > "I have the heart of a little child, and the brain of a genius.
> > >    ... and I keep them in a jar under my bed"
> > >
> > >
> > > --
> > > 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/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/faq