On Wednesday 04 June 2003 11:38 am, Buchan Milne wrote: > Jason Straight wrote: > > Ok, I'm about ready to start kicking ass over this - ifplugd just totally > > farked up our network on a bunch of machines when I had to recycle > > power on > > > our switch - what mayhem. > > So your DHCP server can't handle multiple requests? If your network > can't handle DHCP, use static assignments.
Has nothing to do with DHCP, I don't use dhcp-client for servers, these are machines with static settings and some with special routes that get added with ip route, and proxy arp gets turned on. That stuff doesn't get restarted by ifplugd when it decides to restart my ethernet devs. > > What a gay idea to try to turn mandrake into XP > > All versions of windows after 2000 Pro do it, including all versions of > Windows 2000 server. Yeah, but that doesn't make it suck less. :) > > - and even worse why can't I > > just remove ifplugd package? I see there's a conditional in > > initscripts/network for ifplugd to have it check for it - why can't I > > just > > > remove with ifplugd without breaking dependancies? > > You can just run drakconnect and uncheck "network hotplugging". Thank you - I just rm'ed ifplugd - was fasts fix, since I didn't feel like bringing down a network of 4000 again to remove ifplug, I'll just wait till the next reboot. > > This really is a stupid setup, and what a pain in the ass it just caused. > > Paint that package brown and stick peanuts and corn to it, put it on > > contrib > > > or something don't make it a default install. > > So what about laptop users? Must they know about contrib before they can > get a semi-functional network setup? How does not having ifplug make may laptop not work? I've been running mandrake on my laptop for years without ifplug without a problem. I mostly use wireless though and hardly ever boot up with a working eth0 so I didn't notice this behaviour of ifplugd before. -- Jason Straight [EMAIL PROTECTED] icq: 1796276 pgp: http://www.JeetKuneDoMaster.net/~jason/pubkey.asc
