Re: unhappy upgrade
On Monday 04 October 2021 07:55:25 pm David Wright wrote:
> On Mon 04 Oct 2021 at 15:25:23 (-0400), Roy J. Tellason, Sr. wrote:
> > On Sunday 03 October 2021 07:53:39 pm Greg Wooledge wrote:
> > > On Sun, Oct 03, 2021 at 04:48:38PM -0700, Patrick Bartek wrote:
> > > > On Sun, 3 Oct 2021 12:49:12 -0400 "Roy J. Tellason, Sr." wrote:
> > > > > I did do a download from their site. But it's not clear to me where
> > > > > I need to put it and how to tell the package management software
> > > > > about it.
> > > >
> > > > Did you download the .deb file of it? You can use dpkg to install, but
> > > > it won't automatically take care of dependencies. I use gdebi-core, a
> > > > command line utility, that will install the .deb file correctly and
> > > > install any dependencies. You must be root to install.
> > >
> > > You can also use this command to install a locally-downloaded .deb
> > > package and its dependencies:
> > >
> > > apt install ./filename.deb
> >
> > Okay, I was using a bunch of diferent apt-get commands to do the upgrade. This is part of why I'm getting confused, too many tools with very similar
> > names... :-)
> >
> > That *did* install it, and also gave me a really long list of stuff that it said wasn't needed any more, but which I didn't deal with at all. I assume that the next
> > time around the apt-get autoremove command will take care of that? It also downloaded one library to work with the package, no big deal there.
> >
> > I don't see virtualbox in my applications menu. Rebooting, I am seeing a *lot* of disk activity, don't know what it's doing there, during the boot process. After
> > it gets the whole way booted, everything is smaller on my screen! This is _not_ good for these 70-YO eyes,
> >
> > I had thought initially that the program had not been installed into my applications menu. But it turns out that they changed the name! Instead of being in there
> > under "virtualbox" it's now in there umder "Oracle VM Virtualbox", which is why I missed it.
> >
> > Tried it out, it runs. I'm not going to start it right now as I'm currently still running it on this laptop, and that would not go well. I guess I need to deal with
> > moving some files around, maybe do an rsync or something, and then shut this one down.
> >
> > Incidentally the issues with Konqueror and Okular seem to have gone away as well.
> >
> > Now the only thing I need to do is get things back to something like the sizes I had before so I can read 'em. Hell, I can't even read the clock in my taskbar!
> > Any thoughts as to how to do that?
>
> It would help people trying to follow what you are doing just to confirm at each stage which version you're now running.
> I /think/ you've got as far as stretch.
Yes, I wanted to get the issues that I was seeing resolved before I went ahead and proceeded with the rest of the upgrades. At this point I've copied things from the laptop (which got very flaky on me) back to the workstation and I am doing my mail there, like I used to. The font is too damn small, though.
> So the main things to confirm as working are the specific points mentioned in the respective Release Notes. In stretch that would
> be, for example, the 4.9 kernel is finding everything,
About the only issue that I've noticed after this stuff all getting fixed is that there's something up with the sound. Given the details of what advice I saw someone else getting, I have a few things to look at. The virtualbox OS complained about it too. :-)
> that X may be running as a user (rather than root) on the console it's started from,
I'm not sure I see the concern here.
> and that your ethernet or wireless connectivity is still good. (Changes were made to the kernel device naming.)
Ethernet is working fine here, as evidenced by the fact that I'm moving lots of data back and forth (32GB for this virtualbox stuff ferinstance) and that I'm doing my mail on this system now. If there had been any issues with that I sure would've been jumping all over it, as I tend to use networking rather heavily. And there is no wireless on this machine.
> Those are just a few I recall, but note they all relate to the OS rather than details in configuring third-party applications.
> Once that's done, time to read the next set of Release Notes. Note that even things like the best tool (apt-get or aptitude) to
> upgrade with may vary from release to release which, remember, are normally separated by a couple of years of tool development.
I saw a couple of references that stated that aptitude had been recommeded earlier but that apt was now a better choice.
So we'll see how it goes from here. My upgrade path for this step went like this:
apt-get autoremove
edit the sources.list file replacing jessie with stretch
apt-get update
apt-get upgrade
apt-get dist-upgrade
And then reboot, and see how well things work. Or maybe reboot a couple of times...
We'll see how it goes.
--
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space, a critter that can
be killed but can't be tamed. --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James
M Dakin
Reply to: