Comment 0 for bug 46994

Revision history for this message
In , Christian Knoke (chrisk-cknoke) wrote : setserial: package configure goes wrong

Package: setserial
Version: 2.17-40
Severity: important

-- System Information:
Debian Release: 3.1
Architecture: i386 (i586)
Kernel: Linux 2.6.8-2-386
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages setserial depends on:
ii debconf 1.4.30.13 Debian configuration management
sy
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries
an

-- debconf information:
  setserial/autosave: true
  setserial/rc-boot-file-removed:
  setserial/rc-boot-file-renamed:
* setserial/autosave-types: manual
  setserial/update-modules-failed:

I have standard pc ports which I wish to configure with different speeds.
I configure them with setserial and then use

 dpkg-reconfigure setserial

and choose 'autosave once'. But the config isn't saved as expected. The
files in /var/lib/setserial/ are not updated.

/etc/serial.conf does not exist at this time. I create it. After that, I do

 invoke-rc.d setserial restart

but the configuration isn't changed to that in serial.conf.

Rebooting sets the correct parameters.

The comment in /etc/init.d/setserial

# Note that this has been changed so that if /etc/serial.conf exists,
# this script does not configure the ports. It uses
# /var/lib/setserial/autoserial.conf # instead, which is handled by another
# init.d script. However, the script is still used for module loads and
# unloads, even if serial.conf exists.

is confusing at this point.

Maybe another script sets the configuration during boot? Or the comment is
wrong? autoserial.conf has still the old wrong parameters, so this can't be
the source.

Christian

--
Christian Knoke * * * http://cknoke.de
* * * * * * * * * Ceterum censeo Microsoft esse dividendum.