module-assistant support for zaptel

[Jose Carlos Garcia Sogo]

--=-8X8P9xgd9rxzf9rpGJiH
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

El dom, 27-03-2005 a las 23:06 +0200, Tzafrir Cohen escribi=C3=B3:

  Woops! Someone added an extra > in your reply and I though you were
quoting from here on.
=20
> > >  I have also changed and improved package descriptions (please review
> > > and comment) and I have added a README.Debian file telling about how =
to
> > > compile modules and use them with udev.
> >=20
> > Hmmm... Something the user has to do. Is there any way to do it for the
> > user?

  We could add that file ourselves but udev maintainer discourages it.
Anyway, if we agree on the permissions, we could bug udev so those get
included.

> >=20
> > For instance, quoting from README.Debian:
> >=20
> > | If you cannot access the zap/ctl device, check which user asterisk is=
=20
> > | running as and add these permissions to your permissions file
> > | (ie /etc/udev/permissions.d/50-udev.permissions):
> > | # zaptel devices -- if you want to run asterisk as a different user
> > | # (asterisk in this case, subtitute it for the appropiate one)
> > | zap/*:asterisk:asterisk:660
> >=20
> > So shouldn't the asterisk package include a file
> > /etc/udev/permissions.d/60-asterisk-udev.permissions which reads:
> >=20
> >   zap/*:asterisk:asterisk:660
> >=20
> > In thoe worst case the use will have to unload and load the zaptel
> > modules.

 Read above.

> >=20
> > In addition, hotplug does a good job at detecting the PCI cards. I
> > wouldn't think of automating the scan after installing zaptel. However
> > telling the user how to do that would help.=20
> >=20
> > Anything better than /etc/init.d/hotplug restart ?

  Well, I don't think you will need to do that. User should be wise
enough to install modules "after" shutting down the machine for
installing the card. If he doesn't do that, he should load the module
himself as for any other hardware. I think we shouldn't mess here, and
restarting hotplug sometimes hangs some computers (for example my laptop
after it having been suspended)

> >=20
> > Another common case to handle is installation of kernel 2.4 without ude=
v
> > and without devfs (the default of sarge). My current hack for them is t=
o
> > create the device files at asterisk install time if no udev/devfs is
> > detected.
> >=20
> > This won't help in a case where someone installed asterisk with kernel=20
> > 2.6/udev but later runs with kernel 2.4/no-udev. But it still handles
> > the common case and does practically no harm.

   Yes, we should keep creating devices by default, if no udev or devfs
is detected. But perhaps we can improve that script and create those
nodes in the real /dev that is kept around (at least udev does it), so
in case udev in deinstalled, user still have them created.

> >=20
> > >=20
> > >  Last, I have a comment to make on device ownership. When we create t=
hem
> > > by hand, when udev or devfs is not being used, we set the ownership f=
or
> > > them as root.dialout. At the same time, asterisk is being runned as
> > > asterisk.asterisk, and user asterisk is only added to audio group. He=
re
> > > there is a lack of coordination. Or we think that zaptel is going to =
be
> > > used only by asterisk, and we make devices as root.asterisk (which ha=
s
> > > the problem of failing if asterisk is not installed), or we add aster=
isk
> > > to dialout group, which has the problem of giving with thas asterisk
> > > power to lauch modem calls (using ppp, for example)
> >=20
> > Moreover. The x100p is practically a modem with the PCI ID of such.
> > Other TDM cards have the PCI IDs of some ISDN cards. Giving permissions
> > to dialout on them may actually cause confusion: it has the pci ids
> > of a modem, and the permissions of a modem, so it must be a modem :-) .

   And isn't dialout what modems have? Or are they owned by root.root
and it is ppp which access them? Not sure about this one.


> > However asterisk is not the only user of zaptel. What about yate? I
> > don't want the config files of Asterisk to mess with the installation o=
f
> > yate and vice-versa.

  Yes, Diana pointed us to that yet. Then we should think on a global
solution for the problem.

  Thanks,

--=20
Jose Carlos Garcia Sogo
   jsogo@debian.org

--=-8X8P9xgd9rxzf9rpGJiH
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
	digitalmente

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCRyqOS+BYJZB4jhERAm0PAJ4/v+1rKg3FM162/fhNwCJYjIj3YQCfUH7Q
WNHqGzo76uaQzOXV7i7WGOc=
=zxS3
-----END PGP SIGNATURE-----

--=-8X8P9xgd9rxzf9rpGJiH--