On Mon, Nov 21, 2005 at 12:58:48PM +0000, Colin Watson wrote: > On Wed, Nov 09, 2005 at 08:12:36PM +0100, Mattia Dongili wrote: > > I didn't find time enough to do much work on pcmciautils :/ > > > > Anyway I'd still like to help and I plan to look into the package > > further in the next days. > > Since we're about to switch to 2.6.15 as the default kernel in Ubuntu, > we needed pcmciautils, so I did a very quick packaging job on it, which > I'd like to move into Debian as long as I'm not stepping on anyone > else's toes: > > http://archive.ubuntu.com/ubuntu/pool/universe/p/pcmciautils/ > > (may have moved to > http://archive.ubuntu.com/ubuntu/pool/main/p/pcmciautils/ by the time > you read this) > > However, I've done no real work on transitioning from pcmcia-cs; I > simply left pcmcia-cs there and made sure that both pcmcia-cs and > pcmciautils could be installed at the same time (which I think is a very > good property to have anyway). Further work on this would be useful. I'd > be happy to co-maintain this with a team.
Be careful, if pcmcia-cs is purged after installing pcmciautils you lose
/etc/pcmcia/config.opts :)
> > The first thing coming to my mind is having a pcmcia-common that does
> > all the configuration stuff, and puts kernel-version-aware
> > init/udev/hotplug(?) scripts around,
>
> I didn't bother with the hotplug scripts, since pcmciautils can only
> easily be configured for one of udev or hotplug, and hotplug is going
> away anyway. As far as I know there's no need for the udev scripts to be
> kernel-version-aware because if your kernel is too old you simply won't
> get the uevent.
Yes, sorry for being unclear, I though only of the init-script being
kernel-version aware so that it can be included into pcmcia-common.
I don't know if it make sense but:
- the user might want to not start pcmcia at boot (so no udev
rules but an init-script is necessary)
- there's an easy way to load/unload pcmcia modules
(eg: to have some powersaving or workaround common suspend
(S3/S4) issues)
- you have a single init-script that runs happily if you want to
boot an older kernel.
- put more than just one file into pcmcia-common :)
I was also thinking about the upgrade path from sarge to etch where a
kernel upgrade+reboot is already necesary because of udev.
Now what happens? The careful user upgrades the kernel as a first step
to something >2.6.13-rc1 and surprise! cardmgr doesn't work anymore
and the network card used to download new packages doesn't come up
(easily).
Correct? If so I'm probably being a little catastrophic but it might be
worth to explore the eventuality.
> > http://lists.infradead.org/pipermail/linux-pcmcia/2005-October/002820.html
>
> I can't help thinking that the init script proposed there shouldn't be
> an init script at all. Wouldn't it be better to write udev rules for
> this?
Well, you already have udev rules, but quoting a comment within the
script: "if you have a socket controller where the module cannot be
loaded automatically by hotplug,...".
There's still something obscure to me in that paragraph but I assume it
can be true in some cases. :)
(I hope -again- to be able to spend more time here in the next days, but
I can understand if you don't believe me anymore)
--
mattia
:wq!
signature.asc
Description: Digital signature
