Re: dselect problem/compiling kernel
Thanks I have the packages installed:) I had forgotten a while back I was trying to figure out how to get kde off the extras cd and I was messing around with the access menu then and must have screwed it up so that I couldn't access the
binary cd.
Thanks,
Kent
David Stern wrote:
> On Tue, 09 Feb 1999 12:54:32 CST, KTB wrote:
> > David Stern wrote:
>
> > > It sounds like the most recent available version of packages are
> > > installed. Some questions to consider:
> > > o Did you successfully configure the method using the [A]ccess menu
> > > item?
> >
> > I haven't changed the access. When I selected "install" the cdrom takes off
> > just as it has before.
>
> Generally, the cdrom access method is straightforward, but make sure
> your cdrom is specified as a particular block device, and not as a
> symlink (/dev/cdrom can be a symlink to /dev/hdaX)
>
> > > o Did you successfully [U]pdate the available packages using the
> > > menu?
> >
> > No, if I'm reading you correctly that is what I'm trying to do. Usually when
> > I want something off the cd I go into dselect, do a search for whatever I'm
> > looking for, in this case kernel-packages, deselect displays the line where
> > the package is, I hit "shift +" and then select "install" and "config" This
> > time it didn't work.
>
> Unless your available packages have changed (unlikely on a cdrom), you
> don't ordinarily need to update the list. However, it is somewhat
> common for available package lists to become corrupt every once in a
> while, and the solution is to blow em away and start over. dpkg
> --clear-avail
>
> > > o What do the "ton of messages" that scroll by say? (when you quit
> > > dselect, hold the shift key and press the page-up key to scroll
> > > backwards)
> >
> > There were no messages scrolling by when I tried to install the packages in
> > question. In the past I had a lot of messages scrolling by when I installed
> > other packages. This was my first clue that the installation didn't happen.
>
> Maybe this was one of those dependency related issues, where certain
> packages have to be installed before others can be installed.
> Sometimes it helps to run though install a couple times, and configure
> at least once.
>
> If none of this helps, then more specific wording of messages during the attempted install phase would be helpful. Act like you're going to install, and after it does whatever it's doing, quit, then cut and paste the messages into a mail.
> --
> David
> dstern@u.washington.edu
Reply to: