On Wednesday 04 June 2003 01:42 pm, Buchan Milne wrote: > Jason Straight wrote: > > Ok, now that I've taken time to collect myself and calm the fsck down. > > > > Why is ifplugd default? > > > > If it's for laptop users who switch network locations: > > > > 1. Why build the distro for laptops when more use it on desktops? > > Let's drop SCSI support while we're at it? What about firewire (I mean, > how many desktops ship with firewire ports compared to laptops) and > support for LCD panels?
I'm not saying drop it - but why (by default) configure mdk install for laptops? If that's the case why not have APM configured to suspend after 10 mins of inactivity? Or configure the system to only flush buffers to HD every 2 hrs to save battery? I use a laptop - I don't use ifplugd. > > 2. Who ever switches network cables and needs to have it reconfigured for > > them? > > Users (ie not admins). > > > I mean how often does someone really travel to another location with > > another network and not reboot and restart? > > Every time they us a cross-over cable to transfer something. That happens more often than using mdk on desktops? > Do you really think I want to tell our director over an international > cellphone call how to restart the network and/or configure routes to > transfer files to a windows machine which has now auto-configured itself? ifplugd is only going to restart ethX with the config in the ifup script, so it's going to come back up the same way anyway - so if it's DHCP it's not that hard to have him run dhclient to renew. > > 3. Most people who roam around and hotplug network would be on > > wireless, which > > > takes care of that in it's own configuration (pcmcia), not ifplugd. > > For PCMCIA users, it is not too much of a problem, if you're prepared to > tell them to pop the card every time they plug into a different network > (ie cross-over cable), but for on-board ethernet cards that's not possible. > > > I just don't understand who would want ifplugd? It's a dangerous thing > > that > > > caused problems on machines that I would never have put a utility like > > that > > > on, but I didn't know and didn't have any warning. > > It's not dangerous, it only highilghted the dangers you had in your > network (ifdown eth0 && ifup eth0 would have killed your network in the > same way ...). Yeah, but I would have done that manually and would expect it - I didn't expect 3 machines to die when I restarted the switch and not come back up with the routes and arp config the way I left them. Automation like that is anal. I have problems with XP disabling the wireless clients sometimes because of the hotplug detect network connection it has. I wish it would just leave them alone - if I configure something my way I don't expect some program to go and take the liberty of changing it for what it thinks I want. > Buchan -- Jason Straight [EMAIL PROTECTED] icq: 1796276 pgp: http://www.JeetKuneDoMaster.net/~jason/pubkey.asc
