Re: MPIO digital audio player support for Debian

2003-04-27 Thread Matthew Palmer
On Sun, 27 Apr 2003, Sebastien Phelep wrote: > I already tried to package it, and it's quite ok for libraries and utilities > packages (they still need a little more work to reach Debian Standards > perfection's level), but I however encounter difficulties having the kernel > source package ope

Re: Mannaging non well-known port in inetd.conf/services

2003-04-27 Thread Emmanuel Lacour
On Sun, Apr 27, 2003 at 03:31:32PM +0200, Matthias Urlichs wrote: > Hi, > > On Sun, 27 Apr 2003 08:26:48 +, Emmanuel Lacour wrote: > > And I've got another question. Is there a way of handling "listen ports > > conflicts" in debian. > > Of course there is. It's called "register your port wit

Re: Mannaging non well-known port in inetd.conf/services

2003-04-27 Thread Matthias Urlichs
Hi, On Sun, 27 Apr 2003 08:26:48 +, Emmanuel Lacour wrote: > And I've got another question. Is there a way of handling "listen ports > conflicts" in debian. Of course there is. It's called "register your port with the maintainer of the /etc/services file". -- Matthias

MPIO digital audio player support for Debian

2003-04-27 Thread Sebastien Phelep
Hello, I own a MPIO digital audio player, and would like to create packages for the MPIO Project (http://mpio.sourceforge.net/) utilities so that the required software, libraries and kernel driver module may be managed natively within Debian. Its packaging is very similar to lm-sensors : The M

Re: Mannaging non well-known port in inetd.conf/services

2003-04-27 Thread Emmanuel Lacour
On Sun, Apr 27, 2003 at 09:37:27AM +1000, Matthew Palmer wrote: > On Sat, 26 Apr 2003, Emmanuel Lacour wrote: > > > No real problem for daemon mode, but what to do with inetd mode, as > > defaults ports are 1 and 10001. Could I do directly: > > update-inetd --add '1 stream tcp nowait...' o