public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: igueths@attbi.com
To: speakup@braille.uwo.ca
Subject: Re: upgrade problems
Date: Wed, 14 Aug 2002 19:24:52 +0000	[thread overview]
Message-ID: <20020814192452.OPFF19356.rwcrmhc51.attbi.com@rwcrwbc58> (raw)

Hi Kenny and all. The command I used to so-called fully 
upgrade the packages I had installed was apt --dselect-
upgrade. It downloaded 82.2 mb of data before dpkg 
proceeded to configure the packages. I will try apt-get -
-fix-broken --show-upgraded --dist-upgrade and see what 
happens next time my box is up. Thanks for all the 
replies (I'll let everyone know if I am successfull, I 
hope I am). 
> Hi.  I don't have any problems using modprobe with Woody.  
> You should probably let dpkg and apt manage your package data base
> instead of trying to do things manually.
> Someone suggested a list of commands to try first in another message try
> running them and see what you get.
> 
>           Kenny
> 
> 
> On Wed, Aug 14, 2002 at 02:01:49PM +0000, igueths@attbi.com wrote:
> > Hi. Ok well at least now I know that people are using 
> > Woody without the problems I have mentioned (I guess 
> > that this is a good sign for the most part). Also, I 
> > noticed that Woody has installed modutils 2.4.15, and 
> > have since not been able to load my modules manually via 
> > modprobe (don't like modules.conf too much). Can 
> > modprobe still be run manually to load modules? Or is it 
> > absolutely necessary that I create files for my various 
> > devices via /etc/modutils? I personally don't really 
> > like this method due to the fact that I have always been 
> > able to script-load my modules and I prefer it that way. 
> > I am beginning to think that I for some reason did not 
> > do a full upgrade. Isn't the package index located 
> > somewhere in /var/state/apt? Bc I was going to remove 
> > the current index and rebuild it possibly based on Cd 
> > images. And thanks for all the replies, they have been 
> > very helpfull. 
> > > Hi.  I haven't had any of the problems you are having with upgrading to 
> Woody.
> > > Everything is working fine.
> > > 
> > >           Kenny
> > > 	  On Tue, Aug 13, 2002 at 05:06:42PM +0000, igueths@attbi.com wrote:
> > > > 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!
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


             reply	other threads:[~ UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 igueths [this message]
 ` Cheryl Homiak
  -- strict thread matches above, loose matches on Subject: below --
 igueths
 ` Kenny Hitt
   ` Steve Holmes
 igueths
 ` Kenny Hitt
   ` Cheryl Homiak
 ` Scott Howell
 ` Steve Holmes

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=20020814192452.OPFF19356.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).