Subject: Bug#4458: diald install bug

From: [email-masked] (Joe Reinhardt)
Date: 09 Sep 1996 13:02:48 -0500

Package: diald
Version: 0.14-4

This is what happened when I tried to upgrade to the new diald.  I _do_
have a slip device in my kernel.     I _didn't_ press return at the
first prompt below, I didn't have a chance to before the script continued.

============

Do you want to install the files fetched [y]: 
Installing files...
(Reading database ... 21460 files and directories currently installed.)
Preparing to replace diald 0.14-3 (using .../net/diald_0.14-4.deb) ...

                        -*- ATTENTION -*-

Your kernel does not seem to have SLIP devices.

diald must be able to set up a SLIP device to do its work, even
if you only plan to use PPP connections.

If you know your kernel has SLIP devices, then this is a bug.
Please report it.

If you know your kernel has SLIP devices you can override my judgment
by entering <y> or <Y> below. The installation of diald will then
proceed as if nothing had happened.

Proceed with the installation? [n] Can't open upgrade: No such file or directory
Can't open 0.14-3: No such file or directory
Aborting installation.
dpkg: error processing debian/unstable/binary-i386/net/diald_0.14-4.deb (--install):
 subprocess pre-installation script returned error exit status 1

Please check the script /etc/init.d/diald. This is configured
for a modem on /dev/ttyS0 and it should be changed to match your
set up.

IMPORTANT
Users have reported that using the diald/pppd combination on
/dev/cua? devices causes problems. Use a /dev/ttyS? for diald.
Let me repeat this: the man page shows several examples with /dev/cua1.
THESE WILL NOT WORK (pppd willcomplain about the device being busy).
Use /dev/ttyS? devices instead.
Look into the doc directory (debian.device) for a possible explanation.

Also read the diald(8) man page and edit the configuration file
/etc/diald.options according to your system setup.

Work is in progress on an auto-configuration script.

Press <Return> to continue ... 

============

---

From: Giuseppe Vacanti <[email-masked]>
Date: Mon, 16 Sep 1996 21:07:15 +0200

This was fixed in revision 5, available in Incoming on master.

Thanks,

Giuseppe