Just a couple of problems I found after after an upgrade from 10.1RC3. 1. the kernel installed as the default boot kernel is not correct when the processor is a P3 1Ghz (245M ram) 2. Yast2-->Install sources - SUSE Linux 10.1 CD:///?devices=/dev/hdc is listed -four- times and the addon disk is listed twice. I thought this was reported as fixed. 3. The two YUM sources listed for YOU updates report: Signature Check Failed The file /repodata/repomd.xml is not digitally signed. This is for http://ftp-linux.cc.gatech.edu/pub/suse/suse/update/10.1/ and http://ftp.ale.org/pub/suse/update/10.1/ This is a big no-no and could be used against Novell as being a security hole. Other problems as they are found. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Fri, May 12, 2006 at 09:46:38AM -0400, Kenneth Schneider wrote:
Just a couple of problems I found after after an upgrade from 10.1RC3.
2. Yast2-->Install sources - SUSE Linux 10.1 CD:///?devices=/dev/hdc is listed -four- times and the addon disk is listed twice. I thought this was reported as fixed.
3. The two YUM sources listed for YOU updates report: Signature Check Failed The file /repodata/repomd.xml is not digitally signed.
This is for http://ftp-linux.cc.gatech.edu/pub/suse/suse/update/10.1/
Seems to have a .asc file however. And downloading it now works fine.
and http://ftp.ale.org/pub/suse/update/10.1/
This is a big no-no and could be used against Novell as being a security hole.
Other problems as they are found.
This is a problem of these mirrors and I cannot reproduce it anymore. Ciao, Marcus
On Fri, 12 May 2006, Kenneth Schneider wrote:
Just a couple of problems I found after after an upgrade from 10.1RC3.
You can probably stop right there. Upgrading from a release candidate is not a supported upgrade method. I upgraded from 10.0 and experienced none of the problems that you describe.
Other problems as they are found.
Why don't you create bugs instead?
--
Carpe diem - Seize the day.
Carp in denim - There's a fish in my pants!
Jon Nelson
On Fri, 2006-05-12 at 08:55 -0500, Jon Nelson wrote:
On Fri, 12 May 2006, Kenneth Schneider wrote:
Just a couple of problems I found after after an upgrade from 10.1RC3.
You can probably stop right there. Upgrading from a release candidate is not a supported upgrade method. I upgraded from 10.0 and experienced none of the problems that you describe.
Other problems as they are found.
Why don't you create bugs instead?
I wanted to report them here as well so others that have the same problems can see they are not alone. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On 5/12/06, Kenneth Schneider
On Fri, 2006-05-12 at 08:55 -0500, Jon Nelson wrote:
On Fri, 12 May 2006, Kenneth Schneider wrote:
Other problems as they are found.
Why don't you create bugs instead?
I wanted to report them here as well so others that have the same problems can see they are not alone.
And thanks for that! People scan these lists for this kind of first hand information, not Bugzilla. Please keep on reporting also the problems. I was looking for updating my 2 home computers to 10.1. The other is a pain to do as it only has floppies (laptop) and the other is P3... so I'm still waiting to see how this 10.1 goes. -- HG.
Kenneth Schneider
Just a couple of problems I found after after an upgrade from 10.1RC3.
1. the kernel installed as the default boot kernel is not correct when the processor is a P3 1Ghz (245M ram)
Please open a bugreport for this.
2. Yast2-->Install sources - SUSE Linux 10.1 CD:///?devices=/dev/hdc is listed -four- times and the addon disk is listed twice. I thought this was reported as fixed.
This might be a result of your update from RC3. I advise everybody updating from a previous 10.1 RC or Beta to remove all installation sources first...
3. The two YUM sources listed for YOU updates report: Signature Check Failed The file /repodata/repomd.xml is not digitally signed.
This is for http://ftp-linux.cc.gatech.edu/pub/suse/suse/update/10.1/ and http://ftp.ale.org/pub/suse/update/10.1/
This is a big no-no and could be used against Novell as being a security hole.
This is a result of your RC3 update, it will not happen if you do an update from 10.0 or if you remove all installation sources first...
Other problems as they are found.
Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Fri, 2006-05-12 at 16:02 +0200, Andreas Jaeger wrote:
Kenneth Schneider
writes: Just a couple of problems I found after after an upgrade from 10.1RC3.
1. the kernel installed as the default boot kernel is not correct when the processor is a P3 1Ghz (245M ram)
Please open a bugreport for this.
Will do.
2. Yast2-->Install sources - SUSE Linux 10.1 CD:///?devices=/dev/hdc is listed -four- times and the addon disk is listed twice. I thought this was reported as fixed.
This might be a result of your update from RC3. I advise everybody updating from a previous 10.1 RC or Beta to remove all installation sources first...
3. The two YUM sources listed for YOU updates report: Signature Check Failed The file /repodata/repomd.xml is not digitally signed.
This is for http://ftp-linux.cc.gatech.edu/pub/suse/suse/update/10.1/ and http://ftp.ale.org/pub/suse/update/10.1/
This is a big no-no and could be used against Novell as being a security hole.
This is a result of your RC3 update, it will not happen if you do an update from 10.0 or if you remove all installation sources first...
Other problems as they are found.
Andreas
Thanks for the response. The laptop I used is for testing purposes and has some files I need to backup before installing new. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Fri, 2006-05-12 at 16:02 +0200, Andreas Jaeger wrote:
Kenneth Schneider
writes: Just a couple of problems I found after after an upgrade from 10.1RC3.
1. the kernel installed as the default boot kernel is not correct when the processor is a P3 1Ghz (245M ram)
Please open a bugreport for this.
When going to http://en.opensuse.org/Submitting_Bug_Reports I get the following error: The Wiki functionality is currently unavailable. Please use the link above to download and begin using SUSE Linux 10.1! This is after I have logged in. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Fri, May 12, 2006 at 10:13:08AM -0400, Kenneth Schneider wrote:
When going to http://en.opensuse.org/Submitting_Bug_Reports I get the following error:
https://bugzilla.novell.com/index.cgi Also the question should have gobe to suse-linux-e mailinglist. This list is about the SUSE community. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau
On Fri, 2006-05-12 at 16:02 +0200, Andreas Jaeger wrote:
Kenneth Schneider
writes: Just a couple of problems I found after after an upgrade from 10.1RC3.
1. the kernel installed as the default boot kernel is not correct when the processor is a P3 1Ghz (245M ram)
Please open a bugreport for this.
Submitted as bug #175381. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Hi,
2. Yast2-->Install sources - SUSE Linux 10.1 CD:///?devices=/dev/hdc is listed -four- times and the addon disk is listed twice. I thought this was reported as fixed.
I had this too. But I installed a new version, no upgrade. In my old installation of suse 10.0 I made a dvd from the 10.1-cds including the 6th non-oss-cd. With this i did the installation. If the original dvd-image is released next week I will try to reinstall. Suse 10 is just for testing purposes used by me. Greetings, Alexander
participants (7)
-
Alexander Bruns
-
Andreas Jaeger
-
HG
-
houghi
-
Jon Nelson
-
Kenneth Schneider
-
Marcus Meissner