Bug#296958: Problem with creating device files.

[Kilian Krause]

--=-rd2uVuhD3GKnRIiQ0hqF
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi Tzafrir,

Am Donnerstag, den 31.03.2005, 07:07 +0200 schrieb Tzafrir Cohen:
> On Thu, Mar 31, 2005 at 12:04:32AM +0200, Kilian Krause wrote:
> > Hi,
> > > > The default kernel of Sarge uses nither. So it is relevant.=20
> > >=20
> > >   Yes, we need to create "usual" devices by default. If not, it won't
> > > work for a lot of users.
> >=20
> > yes, so we need a MAKEDEV bug to have /dev/zap* support in there..
> >=20
> > > >=20
> > > > So what group did we want to give them?
> > >=20
> > >   This is the same question I made when I asked about device
> > > permissions... so that need to be answered first.
> >=20
> > the zaptel devices are permissioned 0660 for root.audio following the
> > "sound" Section of the package itself.
>=20
> And those devices are related to "audio" becasue?

because zaptel is an "audio driver" to the debian archive (looking at
the Section). It therefore has audio devices which have a control
channel and interface with the PSTN. See them as a
"MoDem" (Modulator-Demodulator), like an ancient accoustic coupler or a
newer voice-modem-lookalike.

IMHO, if we consider them to be a digital modem/network entity rather
than a voice-modem, we should move zaptel to "comm" consistently
(meaning we need the overrides file adjusted). If we however look at
ISDN devices which we need for chan_capi, they're in the dialout group.
So there's good reason to tell zaptel (in the digital version) needs to
move over to comm.

As for overrides: there's 3 new ftpmasters now, so I'd say there's hope
if we're asking for the alteration, it'd be changed soon enough.

Santiago, any specific other reason you put it into sound in the first
place?

> If a console user gets permissions to write to audio devices, should
> that user get pemissions to write to zaptel devices?

Well, from a personal point, I'd prefer dialout here. But it'd need to
be consistently thought through.

> >=20
> > Asterisk has then to be adapted to be in groups "audio" *AND* "dialout"
> > to access aswell zaptel, oss, alsa and ISDN devices (like chan_capi or
> > chan_misdn).
>=20
> dialout is more related.
>=20
> Some relevant groups from my /etc/group:
>=20
>   dialout
>=20
>     My user is in that group for some reason, I can't recall why

doing PPP or direct ISDN/Modem dialling most probably. Could also mean
you've been using cu some time back then for a serial console.

> 	audio
>=20
> 	  All my local interactive users are there, along with Asterisk

Appropriate for those using asterisk as client with OSS/ALSA. There
apparently is cases where asterisk needs to be in that group for
interactive audio with the desktop.
=09
> 	dip

/dev/ppp which we'll not need - most probably. At least unless someone
comes up with a request for default ppp-dialin on Zaptel-devices. (Yes
it is possible with spandsp according to what i read)

> 	fax

uhm, are there devices which are fax-only in your filesys? I don't have
any device nodes with fax on my box.

> Anyway, I'd like to resolve this as soon as possible for Rapid, even if
> I have to patch MAKEDEV myself in the mean while.

We need this resolved to get the whole lot into Sarge, so belive me we
also need this urgently ;)


--=20
Best regards,
 Kilian

--=-rd2uVuhD3GKnRIiQ0hqF
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Dies ist ein digital signierter Nachrichtenteil

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

iD8DBQBCS6yavdkzt4X+wX8RAnssAJ0XSjxHPh+AR7KqpS0BA7RDCaz0aACggqrF
9ozn2VrEyKN3qZGXfE8D1O4=
=yBB7
-----END PGP SIGNATURE-----

--=-rd2uVuhD3GKnRIiQ0hqF--