[lug] YAST=EVIL

George Sexton gsexton at mhsoftware.com
Fri Feb 27 15:20:43 MST 2004


I upgraded three other machines and didn't hit this problem either. I
don't know what it was, but I am absolutely certain that it worked, I
upgraded, it didn't work, I re-defined the interfaces, and it started
working again.



-----Original Message-----
From: lug-bounces at lug.boulder.co.us
[mailto:lug-bounces at lug.boulder.co.us] On Behalf Of Ferdinand Schmid
Sent: Friday, February 27, 2004 1:06 PM
To: Boulder \(Colorado\) Linux Users Group -- General Mailing List
Cc: support at suse.com
Subject: Re: [lug] YAST=EVIL


First my apologies - this is a very tardy reply to your BLUG posting,
but...

In four years of using SuSE and YAST I have not seen such behavior yet
- not
on laptops and not on servers and desktops.  I would really inspect your
system more closely to see what else may have gone wrong with this
update -
and how the ifcfg-ethxx configs got broken.  In fact I don't see why a
kernel
upgrade would even touch those.  

You may also want to look at fou4s form Markus Gaugusch for automated
updates
- it has some nice features.

Ferdinand

--On Thursday, February 19, 2004 12:47:22 PM -0700 George Sexton
<gsexton at mhsoftware.com> wrote:

> I just spent a few hours troubleshooting a SuSE 9.0 server
> installation.
> 
> Everything was fine until the security update was applied last night
> and the machine rebooted.
> 
> All of a sudden, the NICs stopped working. The initialization script
> just failed for eth0 and eth1.
> 
> I tried putting a hand-compiled kernel on thinking that something in
> the new kernel was keeping things from working. It still didn't work.
> 
> At this point, in desparation I tried SuSE support. Their solution was
> to roll back to the stock kernel level. 
> 
> While on hold (15 minutes) waiting to receive this gem, it occurred to
> me to delete the configurations for the interfaces, re-boot the
> machine, and re-define the interfaces. Lo, and Behold! It worked.
> 
> I guess the next logical step for the future of YAST is to have it
> leave parts of bad configurations behind, and then not-recreate them
> when the interfaces are re-added. Once they do this, we will have
> complete parity with Windows. The solution when things don't work
> will be to re-install the OS.
> 
> ARRRGGGGG....
> 
> George Sexton
> MH Software, Inc.
> Voice: 303 438 9585
> http://www.mhsoftware.com 
>  
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug



--
Ferdinand Schmid
Architectural Energy Corporation
Celebrating over 20 Years of Improving Building Energy Performance
http://www.archenergy.com

_______________________________________________
Web Page:  http://lug.boulder.co.us
Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
Join us on IRC: lug.boulder.co.us port=6667 channel=#colug




More information about the LUG mailing list