> 2) make makedev produce more of these files (but probably most users
>don't need them, at least not on desktop PCs which have seldomly
>two mouses or keyboards)
That's probably the right solution. Device nodes hardly take any
resources anyway.
Cheers,
Peter (p2).
signature.asc
Descri
On Sun, Sep 11, 2005 at 01:05:36PM +0200, Frank Lichtenheld wrote:
> 2) make makedev produce more of these files (but probably most users
>don't need them, at least not on desktop PCs which have seldomly
>two mouses or keyboards)
That's the right choice. Lot's of laptops have additional e
On Sep 11, Frank Lichtenheld <[EMAIL PROTECTED]> wrote:
> 1) generate more device files in the postinst of the package with
>mknod (which is a policy violation IIRC)
Right.
> 2) make makedev produce more of these files (but probably most users
>don't need them,
the event device files
(/dev/input/event*) to monitor attached input devices. The problem
now is that makedev only generates four of these event device files
(event0 to event3). On my fully standard Powerbook with an attached
USB mouse I have already _six_ of these those, if I would plug in
e.g. a
Martin -
>I'm packaging a kernel driver for the Gravis Ultrasound sound card.
>It requires some special device files to be created (in addition to
>those normally used by the OSS driver) in order for all of its
>features to work. My question is, how should I create the device
Hi all:
I'm packaging a kernel driver for the Gravis Ultrasound sound card. It
requires some special device files to be created (in addition to those
normally used by the OSS driver) in order for all of its features to work. My
question is, how should I create the device files?
By now
Package: base
Version: 0.93.6
The base package creates a group `audio' with GID 29 in /etc/group,
yet the following audio-related device files are set to be owned by
group 55, which is unmentioned in /etc/group :
/dev/mixer
/dev/midi00
/dev/sequencer
/dev/dsp
/dev/audio
/dev/sndstat
/dev/m
7 matches
Mail list logo
