Re: PCMCIA network configuration

2004-04-04 Thread Per Olofsson
On Sun, Apr 04, 2004 at 15:39 -0400, Joey Hess wrote: > If the installer has the change the default, then the default is wrong > and should be fixed IMHO. Anyway, we have no mechanism for preseeding > the database at that point. Right. So I could either bug the hotplug maintainer to make this the

Re: PCMCIA network configuration

2004-04-04 Thread Joey Hess
Per Olofsson wrote: > I filed a bug report against hotplug and it has been closed now by a > new upload. The solution implemented was a low-priority debconf > question which asked whether to not use the logical hotplug interface, > and the default is false, i.e. use a logical interface. So what do

Re: PCMCIA network configuration

2004-04-04 Thread Per Olofsson
On Tue, Mar 30, 2004 at 21:59 +0200, pelle wrote: > Now that the hotplug init script is linked as S40hotplug, I don't see > the big problem in reverting hotplug to the old behaviour of just > doing ifup on the interface without the "=hotplug". I filed a bug report against hotplug and it has been c

Re: PCMCIA network configuration

2004-03-30 Thread Per Olofsson
On Mon, Mar 29, 2004 at 17:08 -0500, Joey Hess wrote: > I went back and looked at the thread starting at > http://lists.debian.org/debian-devel/2003/debian-devel-200302/thrd4.html, > and it seems that this behavior was added to give more control to work > around various bad interactions involving h

Re: PCMCIA network configuration

2004-03-29 Thread Joey Hess
Per Olofsson wrote: > The real problem is the installed system. cardmgr doesn't bring up > Cardbus network interfaces, and neither does > /etc/init.d/networking. hotplug used to bring up these interfaces but > does not do that anymore by default. That seems serously brain-dead. Why should this not

Re: PCMCIA network configuration

2004-03-29 Thread Per Olofsson
On Mon, Mar 29, 2004 at 21:19 +0200, pelle wrote: > Ideally the network script should only do this if it is invoked from > withing debian-installer. Perhaps put a special network script in the > udeb, or add the code with some kind of check so that it is not > activated on a real Debian system. Sho

Re: PCMCIA network configuration

2004-03-29 Thread Per Olofsson
On Mon, Mar 29, 2004 at 12:42 -0500, Joey Hess wrote: > I don't think getting really accurate card names is all that important, > very few people will have two pcmcia network cards. So calling it > "PCMCIA network card N" is probably fine, or whatever it does now. Yeah, that was merely a side thin

Re: PCMCIA network configuration

2004-03-29 Thread Joey Hess
Per Olofsson wrote: > Now, how to implement this? What first comes to mind is to add a > special field to /etc/network/devnames and use that file, since netcfg > already reads it. One could also add cardctl to pcmcia-cs-udeb and use > it to get the card name. The problem is that card names might co

Re: PCMCIA network configuration

2004-03-29 Thread Per Olofsson
On Sun, Mar 28, 2004 at 20:27 -0500, Joey Hess wrote: > Per Olofsson wrote: > > (Please CC me on replies.) > > 1. Change /etc/pcmcia/network{,.opts} to somehow tell netcfg that a > >particular interface is a PCMCIA network card and then modify > >netcfg so that it doesn't add the auto opti

Re: PCMCIA network configuration

2004-03-28 Thread Joey Hess
Per Olofsson wrote: > (Please CC me on replies.) > > Currently, netcfg adds the "auto" option on all interface definitions > it generates. However, during the boot process cardmgr is started > after networking, so the interfaces are ifup'd before they are known > by the kernel. FWIW, this is bug

PCMCIA network configuration

2004-03-28 Thread Per Olofsson
(Please CC me on replies.) Currently, netcfg adds the "auto" option on all interface definitions it generates. However, during the boot process cardmgr is started after networking, so the interfaces are ifup'd before they are known by the kernel. Unfortunately, ifup does not check whether the inte