Re: Modem changes behavior after Sarge Update
On Tuesday 21 February 2006 22:37, John Hasler wrote:
> Hal Vaughan writes:
> > Does kill look for lock files and release devices?
>
> No. Kill just sends a signal (default SIGTERM). Minicom catches the
> signal, cleans up by closing files and restoring the terminal settings and
> then exits. Sounds like it restores the serial port settings as well. Try
> 'kill -9': that cannot be caught (it will leave the terminal in a strange
> state, though. Use 'reset' to fix it).
I used kill and kill -9. The latter also has that effect (of dropping the
DTR).
> > What does kill do that effects the DTR?
>
> Nothing.
>
> > first time I've ever seen an upgrade of Debian Stable hose a system!
>
> What did you change?
Aptitude log:
[UPGRADE] cupsys 1.1.23-10 -> 1.1.23-10sarge1
[UPGRADE] cupsys-bsd 1.1.23-10 -> 1.1.23-10sarge1
[UPGRADE] cupsys-client 1.1.23-10 -> 1.1.23-10sarge1
[UPGRADE] gnupg 1.4.1-1 -> 1.4.1-1sarge1
[UPGRADE] gzip 1.3.5-10 -> 1.3.5-10sarge1
[UPGRADE] kernel-image-2.6.8-2-386 2.6.8-16 -> 2.6.8-16sarge1
[UPGRADE] kernel-image-2.6.8-2-686 2.6.8-16 -> 2.6.8-16sarge1
[UPGRADE] libcupsimage2 1.1.23-10 -> 1.1.23-10sarge1
[UPGRADE] libcupsys2-gnutls10 1.1.23-10 -> 1.1.23-10sarge1
[UPGRADE] mdadm 1.9.0-4 -> 1.9.0-4sarge1
[UPGRADE] perl 5.8.4-8 -> 5.8.4-8sarge3
[UPGRADE] perl-base 5.8.4-8 -> 5.8.4-8sarge3
[UPGRADE] perl-doc 5.8.4-8 -> 5.8.4-8sarge3
[UPGRADE] perl-modules 5.8.4-8 -> 5.8.4-8sarge3
[UPGRADE] samba 3.0.14a-3 -> 3.0.14a-3sarge1
[UPGRADE] samba-common 3.0.14a-3 -> 3.0.14a-3sarge1
[UPGRADE] smbclient 3.0.14a-3 -> 3.0.14a-3sarge1
[UPGRADE] sudo 1.6.8p7-1.2 -> 1.6.8p7-1.3
[UPGRADE] xpdf-common 3.00-13 -> 3.00-13.5
[UPGRADE] xpdf-utils 3.00-13 -> 3.00-13.5
Also, if you check the original post (if you still have it), I had a LOT of
problems because it overwrote my /boot/grub/menu.lst file without warning.
In all other cases, I've seen apt or dpkg or whatever ask me to upgrade a
config file or to save my original config file. I can see the need for
editing or changing the menu.lst file when upgrading or adding a kernel, but
overwriting the file and not giving a choice to change or keep it is just
wrong.
I'll post that info separately, since I want to hear some feedback on that
before I submit it as a bug report.
Hal
Reply to: