Re: [opensuse-factory] Factory updated on our server...
On Sun, Apr 30, 2006 at 08:12:51AM +0200, Andreas Jaeger wrote: > > Check the inst-source/content file whether it's correct as explained > in my message, I checked inst-source/content on mirrors.kernel.org and it looks good. Thank you for the hint. When I try network install from mirrors.kernel.org it fails with the message: No catalog found at 'http://204.152.19139/opensuse/distribution/SL-OSS-factory/inst-source' Does it mean that something is still out of sync on that mirror? Or network install from factory is not possible? Thanks, -Kastus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Factory updated on our server...
On Sat, Apr 29, 2006 at 11:05:19PM +0200, Andreas Jaeger wrote: > > Therefore I advise to check that factory is updated before using the > tree before installation. Please excuse me if it is an FAQ, but how do I verify that factory is updated? I was trying to run net install from factory which was failing with error 134 (but after download of a 70+MB root image which takes a while). Is there an easier method? Thanks, -Kastus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] network installation fails with 'install program exit code is 134'
Hi, I tried network installation on 2 different machines and both failed with mysterious message "install program exit code is 134" The hardware is IBM ThinkPad T30 and T21. I first tried with boot CD from 10.1RC2 and then with boot.iso from the factory. I tried mirrors ftp.gwdg.de and mirrors.kernel.org. The result is consistent--exit code 134. It downloads root file system (70MB), mounts it, kicks off yast, I confirm license, then select new installation or update (T31 is clean, T21 has 10.1beta2 installed) and moment later it blows with 134 error. VT3 shows this: starting setctsid `showconsole` inst_setup yast install program exit code is 134 Am I doing something obviously wrong here or is it a bug in root image? Shall I report it to bugzilla? Thanks, -Kastus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
