[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#242614: marked as done (kppp: Customizable Device List)

Your message dated Sat, 3 Mar 2007 00:27:23 +0100
with message-id <20070302232722.GA11628@pryan.sytes.net>
and subject line kppp: Customizable Device List
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: kppp
Version: 4:3.1.5-1
Severity: wishlist


Yo kppp Maintainer.

I use a System with IRDA, Bluetooth and an Lucent Winmodem (Linmodem)
Those serial Devices are called

/dev/ircomm0
/dev/rfcomm0
/dev/LTmodem

and are not included in kppp's device list.
The easy solution is just to add a softlink from /dev/modem to the wanted device.
But as I use all three connections quite often, I get a bit annoyed to change that symlink every time I want to use 
another device.

As I read, the device list displayed by kppp is hardcoded in the headers depending on the os kppp is compiled on.

Would it be possible for further releases to add a user expandable device list that would be saved in kppprc?

-Benoit-


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.5
Locale: LANG=de_CH, LC_CTYPE=de_CH

Versions of packages kppp depends on:
ii  kdelibs4                    4:3.1.5-1    KDE core libraries
ii  libart-2.0-2                2.3.16-3     Library of functions for 2D graphi
ii  libaudio2                   1.6c-3       The Network Audio System (NAS). (s
ii  libc6                       2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  libfam0c102                 2.7.0-5      client library to control the FAM 
ii  libfontconfig1              2.2.2-1      generic font configuration library
ii  libfreetype6                2.1.7-2      FreeType 2 font engine, shared lib
ii  libgcc1                     1:3.3.3-5    GCC support library
ii  libpng12-0                  1.2.5.0-5    PNG library - runtime
ii  libqt3c102-mt               3:3.2.3-2    Qt GUI Library (Threaded runtime v
ii  libstdc++5                  1:3.3.3-5    The GNU Standard C++ Library v3
ii  libxcursor1                 1.0.2-5      X Cursor management library
ii  libxft2                     2.1.2-6      FreeType-based font drawing librar
ii  libxrender1                 0.8.3-7      X Rendering Extension client libra
ii  xlibmesa3-gl [libgl1]       4.2.1-12.1   Mesa 3D graphics library [XFree86]
ii  xlibs                       4.3.0-7      X Window System client libraries m
ii  zlib1g                      1:1.2.1-5    compression library - runtime

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Wed, Apr 07, 2004 at 07:54:31PM +0200, Benoit Panizzon wrote:
> Package: kppp
> Version: 4:3.1.5-1
> Severity: wishlist
> 
> 
> Yo kppp Maintainer.
> 
> I use a System with IRDA, Bluetooth and an Lucent Winmodem (Linmodem)
> Those serial Devices are called
> 
> /dev/ircomm0
> /dev/rfcomm0
> /dev/LTmodem
> 
> and are not included in kppp's device list.
> The easy solution is just to add a softlink from /dev/modem to the wanted device.
> But as I use all three connections quite often, I get a bit annoyed to change that symlink every time I want to use 
> another device.
> 
> As I read, the device list displayed by kppp is hardcoded in the headers depending on the os kppp is compiled on.
> 
> Would it be possible for further releases to add a user expandable device list that would be saved in kppprc?
> 



Fixed by upstream some time ago. Closing bug.

Ana

--- End Message ---
Reply to: