On Sunday 12 January 2003 19:49, Charles A Edwards wrote: > On Sun, 12 Jan 2003 13:56:09 -0500 > > Mark Weaver <[EMAIL PROTECTED]> wrote: > > hey Harm! at least you got buttons to click on at that point! :) No > > buttons showed up on that panel during the intall, which necessitated > > me starting the install all over and choosing "all" in order to get it > > going. > > I think it important to note that anytime you test a Mandrake beta you > are in actuality testing 2 different works in progress. > > The first is DrakX which is the installation program itself and is > responsible for everything up until your system reboots you to your > newly installed toy. > This includes hardware detection, partitioning, pkg selection, buttons, > navigation, etc. etc, etc. > > The second process is, of course, the OS itself. > > This early in the beta devel stage varying hardware and varying configs > are going to produce an infestation of bugs. > This is by desire so that by the time the RCs arrive all that will > remain to be corrected are minor irritations. > > The more people and varied systems that can run and provide feedback, be > it through the lists or bugzilla, for the betas the more polished and > troublefree the next final will be. > BTW if it holds to the 6 mom timeline this will not be until April. > > That being said I also think that it is very important to note that a > beta OS release is not meant to be used as an upgrade for a currently > running stable OS. > > If you have an extra system, a spare hd, or even a gig or 2 of unused > space on your current drive then use it for a clean install of the beta. > > If this does not apply to you and you are determined to use the Beta as > an upgrade install. > Install it and then use rpmdrake or urpmi to go full cooker and at the > very least lurk on the cooker mailing list. > Do not try to run a miss-matched mix of pkgs, this invalidates any and > all bugs/problems you may/will encounter. > > > Charles
I disagree on that one. Upgrading has to be tested (the installation program itself) same as any clean install. Chances are indeed fairly high that problems, arising from package mis-matches could be mistaken for bugs. But that's not a real problem to find out. Whenever I think I found a bug I always try to redo it again to eliminate coincidence. Next I check if it isn't some stupid misconfiguration and only then do I submit a bug-report. Frankly I've never discovered a bug that hadn't allready been reported by somebody else. These double checks take time=:o) On top: Upgrading a working system makes it easier to compare and puts a heavier load on the OS i.e I use it straightaway for everything I did before. Overall the upgraded OS works very well up to now and I can't say I've stumbled over any real bugs yet. My log files are extremely boring at the moment=:o) Tomorrow I'll put a clean install next to it, I've just cleaned up a nice 8G partition for it. We'll see how that compares. Good luck, HarM
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
