Hi, Eric, I have to admit that I am a little bit paranoid. It _could_ be a problem if some other components in Bering-uClibc expect ifupdown to do this kind of checks internally.
In the ifupdown used in Bering-uClibc 1.0.x, there are several functions and variables to ensure we're not downing an interface that's not up, or uping one that's not down. Do you think it is ok to remove all these checking routines and other code segments in busybox to read (or update) /var/run/ifstate? If this the case, then we can expect a somewhat smaller busybox. Best regards, Jonathan On Fri, Oct 08, 2004 at 06:04:46PM +0200, Eric Spakman wrote: > Jonathan, > > I don't fully understand why this is a problem. I agree with you that > the error handling could be better but the interface is already > brought up and configured. By doing an "ifup lo" or "ifup eth0" you > try to enable an already enabled interface. > > Doing an "ifdown lo" and "ifup lo" is the correct way to bring the > interface down and up. > > Eric > > > Hi, Luis, > > > > Unfortunately, other interfaces also have the same problem. > > I took "lo" as an example just because /etc/network/interfaces > > contains "lo" by default. I do agree with you that basic > > ifupdown functions work. > > > > Best regards, > > > > Jonathan > > > > On Fri, Oct 08, 2004 at 08:42:51AM +0100, Luis.F.Correia wrote: > > > Hi! > > > > > > > -----Original Message----- > > > > From: Jonathan Chang [mailto:[EMAIL PROTECTED] > > > > Sent: Friday, October 08, 2004 3:44 AM > > > > To: [EMAIL PROTECTED] > > > > Subject: [leaf-devel] ifupdown problem in Bering-uClibc V2.2.0 > > > > > > > > Hi, list, > > > > > > > > To reproduce this problem: > > > > > > > > firewall# ifup lo > > > > RTNETLINK answers: File exists > > > > And /var/run/ifstate now has only one entry > > > > lo=lo > > > > > > > > On Debian platform or Bering-uClibc 1.0.x, it will response: > > > > ifup: interface lo already configured > > > > Also, /etc/network/ifstate is left unchanged. > > > > lo=lo > > > > eth1=eth1 > > > > eth0=eth0 > > > > > > > > It seems this problem occurs after switching to busybox's ifupdown. > > > > Any idea? > > > > > > > > > > busybox functions are minimalistic, and support only what is asked. > > > > > > if you type 'ifup eth0' and 'ifup eth1', each command will give > > > out proper output, right? then all is ok. > > > > > > If you're asking something about 'lo' you will get a response about > > > 'lo', not any other devices... > > > > > > (but I might be wrong) > > > > > > Luis Correia > > > Bering uClibc Team Member > > > > > > PGP Fingerprint: BC44 D7DA 5A17 F92A CA21 9ABE DFF0 3540 2322 21F6 > > > Key Server: http://pgp.mit.edu > > > > > > > Best regards, > > > > > > > > Jonathan > > ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
