Re: kudzu broken in Fedora 8 after updates?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 22 Mar 2008 at 19:39, Craig White wrote:

From:           	Craig White <craigwhite@xxxxxxxxxxx>
To:             	For users of Fedora <fedora-list@xxxxxxxxxx>
Date sent:      	Sat, 22 Mar 2008 19:39:53 -0700
Subject:        	Re: kudzu broken in Fedora 8 after updates?
Send reply to:  	For users of Fedora <fedora-list@xxxxxxxxxx>
	<mailto:fedora-list-
request@xxxxxxxxxx?subject=unsubscribe>
	<mailto:fedora-list-
request@xxxxxxxxxx?subject=subscribe>

> On Sun, 2008-03-23 at 12:27 +1000, Michael D. Setzer II wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > Systems are not finding the nic after clonng to an identical machine as they 
> > have with all version from Redhat 9 to Fedora 7. Now it is coming up with a 
> > message that eth0 doesn't appear to be present. Deleting the network setup 
> > in the gui, and then creating a new one using eth1 instead of eth0 that still 
> > shows up as an option then works.
> > 
> > In dmesg, found that kudzu has an error.
> > 
> > warning: process 'kudzu' used the deprecated sysctl system call with 1.23.
> > 
> > I've run it at the command prompt with kudzu -p and it produces output that 
> > shows the eth0, but the /etc/sysconfig/hwconf does not show those lines. 
> > 
> > I am going to reimage a machine, and see if redirecting the output of 
> > kudzu -p >/etc/sysconfig/hwconf 
> > and then rebooting will fix the problem, but even if it does, is this a problem 
> > that could effect other things if kudzu isn't working, and is there an 
> > alternative?
> ----
> seems to me that you know what you are doing but you have to be careful
> because it's possible that you have a HWADDR=something
> in /etc/sysconfig/network-scripts/ifcfg-eth0 in your image that you use
> to 'clone' and that of course would break things just like this.
> 
> Craig
> 
> -- 

Thanks for the reply. I am aware of the HWADDR issue, and in the past, it 
was just the process of unchecking the bind to  MAC Address, and that is 
done on the main machine.

I check the /etc/sysconfig/network and the networking directory, and don't 
see any HWADDR lines. 

Tried the kudzu -p >/etc/sysconfig/hwconf  but it just recreates it without the 
eth0 or any eth?. Even tried chmod 444 but it still changed the file on the 
next boot. So, either kudzu on boot is doing something different, or 
something is modifying it after kudzu???

Thanks again for the reply.

> fedora-list mailing list
> fedora-list@xxxxxxxxxx
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list


+----------------------------------------------------------+
  Michael D. Setzer II -  Computer Science Instructor      
  Guam Community College  Computer Center                  
  mailto:mikes@xxxxxxxxxxxxxxxx                            
  mailto:msetzerii@xxxxxxxxx
  http://www.guam.net/home/mikes
  Guam - Where America's Day Begins                        
+----------------------------------------------------------+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC@HOME CREDITS
SETI 4,990,334.110836 | EINSTEIN 1,485,279.534200 | ROSETTA 
441,980.400273


-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8 -- QDPGP 2.61c
Comment: http://community.wow.net/grt/qdpgp.html

iQA/AwUBR+VlsizGQcr/2AKZEQLwyQCg4mxBOLkugbE51rZdGkNDWT1FweIAmwcD
MAmdN5teiHWfoW59c7rx18H0
=P6SQ
-----END PGP SIGNATURE-----


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux