From: igueths@attbi.com
To: speakup@braille.uwo.ca
Subject: upgrade problems
Date: Tue, 13 Aug 2002 17:06:42 +0000 [thread overview]
Message-ID: <20020813170643.GLZK19356.rwcrmhc51.attbi.com@rwcrwbc58> (raw)
Hi all. I upgraded to Woody about three days ago, and
have since been experiencing many problems. In my
opinion, the thing's not even close to being ready for
stable distribution (unlike potato). Is anyone currently
experiencing problems with modutils, where modprobe
says "invalid line 81 in modules.conf?" Considering the
fact that nothing has been changed in modules.conf for a
considerably long time, because I have always been
loading my modules manually via scripts. Also has anyone
experienced a status 10 in fetchmail because connection
to localhost failed? The most probable cause for this is
an early termination by exim (This was in my syslog
output). Another thing that has been happening to me is
that whenever I download a file in Lynx, and go back to
the previous page, Dectalk seases responding to
keystrokes. This means that possibly setserial is
attempting to change port configuration and preventing
data from being passed to the serial device (the Dectalk
express). Also at boot time, when I am trying to review
the screen with the 5 and 6 keys on the numpad, they
don't work when the hd is being probed for example. They
only work starting at the login prompt. To fix this
problem, I am going to get the keymap that I was using
in potato and revert back to it. In terms of the
problems with the packages, I am going to replace the
Woody version with the potato version of setserial, and
possibly getting the latest version of Exim. Or if that
doesn't work, I'm going to use the Potato version. And
in terms of modutils, its going to have to get scrapped
for the earlier version as well. So far, I know of one
person who has or is experiencing the problems mentioned
above. Is there anyone else? I am considering submitting
a series of bug reports when this whole thing gets
resolved (if nobody else has done so already). Thanks in
advance for any input!
next reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
igueths [this message]
` Kenny Hitt
` Cheryl Homiak
` Scott Howell
` Steve Holmes
igueths
` Kenny Hitt
` Steve Holmes
igueths
` Cheryl Homiak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020813170643.GLZK19356.rwcrmhc51.attbi.com@rwcrwbc58 \
--to=igueths@attbi.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).