Bug#319583: pcmciautils packaging followup
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.
> 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.
How much of pcmcia-cs do we actually need with pcmciautils? As I
understand it, the mappings of device to driver have moved into the
kernel. Is it just /etc/pcmcia/config.opts (pcmciautils ships its own,
but we need to take care to make pcmcia-cs and pcmciautils coexist
here)?
> 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?
Cheers,
--
Colin Watson [cjwatson@debian.org]
Reply to: