Re: Reading of release notes (was Re: Still on stretch, getting ready for bullseye)

piorunz wrote: ... > New install would change network interface name anyway. net.ifnames=0 works for me in that regards. songbird

Re: Re: Updating kernels impossible when /boot is getting full

> Large unneeded files can be deleted with "rm". This is what I ended up doing. The version 25 was in currently use and I rm'ed all the old version files. That worked, but I needed to do the same when version 31 appeared. Fortunately the new version will get into use so rm will work. Maybe

Re: Still on stretch, getting ready for bullseye

On 2021-08-18, mick crane wrote: >> >> Not sure I see how that analogy applies. >> >> If the 'water' is the knowledge of upgrading Debian releases as present >> in the official release notes, then the chemical analysis is the advice >> on upgrading from this list? In that case, it seems the

Re: Reading of release notes (was Re: Still on stretch, getting ready for bullseye)

On 20/08/2021 12:40, Greg Wooledge wrote: This line of thought probably comes from Windows, when any hardware change causes problems, drivers installation, it can refuse to boot, etc. Not a problem on Debian :) It can be. Any change to the hardware, or even the mobo firmware, can cause PCI

Re: Reading of release notes (was Re: Still on stretch, getting ready for bullseye)

On Fri, Aug 20, 2021 at 11:55:32AM +0100, piorunz wrote: > On 19/08/2021 13:21, songbird wrote: > > when i changed motherboards i figured it was worth a fresh > > install > > This line of thought probably comes from Windows, when any hardware > change causes problems, drivers installation, it can

Re: Reading of release notes (was Re: Still on stretch, getting ready for bullseye)

On 19/08/2021 13:21, songbird wrote: when i changed motherboards i figured it was worth a fresh install This line of thought probably comes from Windows, when any hardware change causes problems, drivers installation, it can refuse to boot, etc. Not a problem on Debian :) Motherboard or even

Re: Reading of release notes (was Re: Still on stretch, getting ready for bullseye)

songbird writes: > Anssi Saari wrote: > ... >> And yes, the working upgrades are the reason I've stuck with Debian >> since Hamm. My ever evolving desktop computer is on its second >> installation now since I reinstalled when I switched to 64-bits >> somewhere in the decade before last. >

Re: Still on stretch, getting ready for bullseye

On 2021-08-18, Tixy wrote: >> >> With a normal system, a shortened version of the upgrade procedure >> without the warnings and pre-checks and post-checks might be OK, >> but this is *Gene*. We know he does not have normal systems. >> >> He needs *all* of the warnings. >> > > I agree with all

Re: Reading of release notes (was Re: Still on stretch, getting ready for bullseye)

rhkra...@gmail.com wrote: ... > Aside: I have never (to the best of my recollection) done an upgrade from one > version to the next, I install the new version on a clean disk (or new > system) > -- the only time I could envision doing an upgrade would be if stable became > a > rolling

Re: Reading of release notes (was Re: Still on stretch, getting ready for bullseye)

Anssi Saari wrote: ... > And yes, the working upgrades are the reason I've stuck with Debian > since Hamm. My ever evolving desktop computer is on its second > installation now since I reinstalled when I switched to 64-bits > somewhere in the decade before last. when i changed motherboards i

Re: Still on stretch, getting ready for bullseye

On 2021-08-17 7:21 p.m., Brian wrote: > On Tue 17 Aug 2021 at 22:48:34 +, Andrew M.A. Cater wrote: > >> On Tue, Aug 17, 2021 at 11:05:44PM +0100, Brian wrote: >>> On Tue 17 Aug 2021 at 16:54:54 -0400, Gene Heskett wrote: >>> Where do I find the recipe to update stretch to buster? >>>

Re: Still on stretch, getting ready for bullseye

Hi On 2021-08-17 6:05 p.m., Brian wrote: > On Tue 17 Aug 2021 at 16:54:54 -0400, Gene Heskett wrote: > >> Where do I find the recipe to update stretch to buster? > > What, in this helpful thread, do you find difficult to understand? > > You have a collection of important machines in your

Re: Reading of release notes (was Re: Still on stretch, getting ready for bullseye)

On Wed, Aug 18, 2021 at 11:26:18AM -0500, David Wright wrote: > On Wed 18 Aug 2021 at 07:39:26 (-0400), The Wanderer wrote: > > On 2021-08-17 at 13:36, Brian wrote: > > > On Tue 17 Aug 2021 at 16:00:57 +, Andrew M.A. Cater wrote: > > > > >> Do the update to Buster - take it as slow as you

Re: Still on stretch, getting ready for bullseye

of the recipe I need to follow. > > > > > > > > > > Cheers, Gene Heskett > > > > > > > > See, *this* is exactly what I tried to avoid -- giving someone > > > > an inferior version of the release notes, empowering their > > >

Re: Reading of release notes (was Re: Still on stretch, getting ready for bullseye)

ynaptic users will love that, as any use of its editor would have to be followed by a good nagging, in case they might hit Upgrade. . Any Release Day should cock the hammer worldwide on any system that includes any strings like *stable or testing in its sources.list, so that the next upgrade attempt will trigger a good nagging. The alternative for people who run rolling upgrades—let the world of big Upgrades pass you by, without getting concerned or bothered by it. Cheers, David.

Re: Reading of release notes (was Re: Still on stretch, getting ready for bullseye)

rhkra...@gmail.com writes: > But, if I did do an upgrade from one version to the next, it would not > surprise me if I forgot to read the upgrade notes. For me, the instructions for upgrading in the release notes are the only way I know how to find out how to upgrade Debian from one release to

Re: Reading of release notes (was Re: Still on stretch, getting ready for bullseye)

On Wednesday, August 18, 2021 07:39:26 AM The Wanderer wrote: > On 2021-08-17 at 13:36, Brian wrote: > > Of course! Do users not do this as a standard procedure? :) > > I don't - because I don't upgrade from one stable release to another; I > track testing, continuously, throughout the

Re: Still on stretch, getting ready for bullseye

gt; > > > See, *this* is exactly what I tried to avoid -- giving someone an > > > inferior version of the release notes, empowering their laziness, > > [...] > > > > Greg *was* trying to help Gene (and us) by getting him to read > documentation from the Debian project

Reading of release notes (was Re: Still on stretch, getting ready for bullseye)

On 2021-08-17 at 13:36, Brian wrote: > On Tue 17 Aug 2021 at 16:00:57 +, Andrew M.A. Cater wrote: >> Do the update to Buster - take it as slow as you need to. Bring it >> bang up to date. >> >> For the Buster to Bullseye - >> >> READ RELEASE NOTES :) > > Of course! Do users not do this as

Re: Still on stretch, getting ready for bullseye

On 2021-08-17 at 15:11, David Wright wrote: > On Tue 17 Aug 2021 at 10:07:18 (-0400), Gene Heskett wrote: >> On Tuesday 17 August 2021 09:08:43 Greg Wooledge wrote: > >>> On Tue, Aug 17, 2021 at 09:01:32AM -0400, Gene Heskett wrote: >>> You literally have the word "oldstable" in your

Re: Still on stretch, getting ready for bullseye

On 18/08/2021 07:57, to...@tuxteam.de wrote: On Wed, Aug 18, 2021 at 01:53:16AM +0100, piorunz wrote: Why are you repeating this? Because Andrew is a nice person. Which I do appreciate highly. Why shouldn't he? Why would you not want him to do? Please see my other reply: "> Amazing

Re: Still on stretch, getting ready for bullseye

On 2021-08-18 09:32, Tixy wrote: On Wed, 2021-08-18 at 09:06 +0100, mick crane wrote: On 2021-08-18 08:40, Tixy wrote: > I agree with all of the above, but as the saying goes: 'you can lead a > horse to water, but you can't make him drink'. You can't blame a horse for wanting to see the

Re: Still on stretch, getting ready for bullseye

On 18/08/2021 08:40, Tixy wrote: I agree with all of the above, but as the saying goes: 'you can lead a horse to water, but you can't make him drink'. Amazing analogy. Gene has been given plenty of water, but he keeps coming back for more while not taking even one sip yet. He failed to RTFM

Re: Still on stretch, getting ready for bullseye

On Tuesday 17 August 2021 18:48:34 Andrew M.A. Cater wrote: > On Tue, Aug 17, 2021 at 11:05:44PM +0100, Brian wrote: > > On Tue 17 Aug 2021 at 16:54:54 -0400, Gene Heskett wrote: > > > Where do I find the recipe to update stretch to buster? > > > > What, in this helpful thread, do you find

Re: Still on stretch, getting ready for bullseye

On Wed, 2021-08-18 at 09:06 +0100, mick crane wrote: > On 2021-08-18 08:40, Tixy wrote: > > > I agree with all of the above, but as the saying goes: 'you can lead a > > horse to water, but you can't make him drink'. > You can't blame a horse for wanting to see the chemical analysis of the >

Re: Still on stretch, getting ready for bullseye

he release notes, empowering their laziness, > [...] > > What's this new fashion around here? If you don't want to help > someone, that's your right. Greg *was* trying to help Gene (and us) by getting him to read documentation from the Debian project, rather than picking one of several di

Re: Still on stretch, getting ready for bullseye

On 2021-08-18 08:40, Tixy wrote: I agree with all of the above, but as the saying goes: 'you can lead a horse to water, but you can't make him drink'. You can't blame a horse for wanting to see the chemical analysis of the water and checking the vicinity for corpses. mick -- Key ID

Re: Still on stretch, getting ready for bullseye

On Tue, 2021-08-17 at 22:01 -0400, Greg Wooledge wrote: > On Tue, Aug 17, 2021 at 09:48:10PM -0400, Gene Heskett wrote: > > On Tuesday 17 August 2021 18:48:34 Andrew M.A. Cater wrote: > > > [an abridged version of the release notes] > > > Thank you Andy, thats more of the recipe I need to follow.

Re: Still on stretch, getting ready for bullseye

On Tue, Aug 17, 2021 at 10:01:32PM -0400, Greg Wooledge wrote: > On Tue, Aug 17, 2021 at 09:48:10PM -0400, Gene Heskett wrote: > > On Tuesday 17 August 2021 18:48:34 Andrew M.A. Cater wrote: > > > [an abridged version of the release notes] > > > Thank you Andy, thats more of the recipe I need to

Re: Still on stretch, getting ready for bullseye

On Wed, Aug 18, 2021 at 01:53:16AM +0100, piorunz wrote: > On 17/08/2021 23:48, Andrew M.A. Cater wrote: > >Gene, > > > >You have two upgrades to do. > > > >One from stretch -> buster. 9-10 That takes you from 2017 -> 2019. > > > >If you can reduce your /etc/apt/sources.list by commenting out

Re: Still on stretch, getting ready for bullseye

On Wed 18 Aug 2021 at 01:53:16 (+0100), piorunz wrote: > On 17/08/2021 23:48, Andrew M.A. Cater wrote: > > Gene, > > > > You have two upgrades to do. > > > > One from stretch -> buster. 9-10 That takes you from 2017 -> 2019. > > > > If you can reduce your /etc/apt/sources.list by commenting out

Re: Still on stretch, getting ready for bullseye

On Tue, Aug 17, 2021 at 09:48:10PM -0400, Gene Heskett wrote: > On Tuesday 17 August 2021 18:48:34 Andrew M.A. Cater wrote: > > [an abridged version of the release notes] > Thank you Andy, thats more of the recipe I need to follow. > > Cheers, Gene Heskett See, *this* is exactly what I tried to

Re: Still on stretch, getting ready for bullseye

Dan Ritter wrote: ... > Tell us more about what you're doing, but also remember that you > can't skip stable versions in an upgrade - you need to upgrade > from stretch to buster, then to bullseye. yes. plus it is good to get rid of cruft if you don't need it so i would back up the

Re: Still on stretch, getting ready for bullseye

On Tuesday 17 August 2021 18:48:34 Andrew M.A. Cater wrote: > On Tue, Aug 17, 2021 at 11:05:44PM +0100, Brian wrote: > > On Tue 17 Aug 2021 at 16:54:54 -0400, Gene Heskett wrote: > > > Where do I find the recipe to update stretch to buster? > > > > What, in this helpful thread, do you find

Re: Still on stretch, getting ready for bullseye

On Tue, Aug 17 2021 at 08:01:46 PM, Gene Heskett wrote: > On Tuesday 17 August 2021 16:57:44 Greg Wooledge wrote: > >> On Tue, Aug 17, 2021 at 04:54:54PM -0400, Gene Heskett wrote: >> > Where do I find the recipe to update stretch to buster? >> >> It's still at >>

Re: Still on stretch, getting ready for bullseye

On Tuesday 17 August 2021 17:45:49 piorunz wrote: > On 17/08/2021 21:57, Greg Wooledge wrote: > > On Tue, Aug 17, 2021 at 04:54:54PM -0400, Gene Heskett wrote: > >> Where do I find the recipe to update stretch to buster? > > > > It's still at > >

Re: Still on stretch, getting ready for bullseye

On 17/08/2021 23:48, Andrew M.A. Cater wrote: Gene, You have two upgrades to do. One from stretch -> buster. 9-10 That takes you from 2017 -> 2019. If you can reduce your /etc/apt/sources.list by commenting out third party repositories like Trinity, that will help. Why are you repeating

Re: Still on stretch, getting ready for bullseye

On Tuesday 17 August 2021 16:57:44 Greg Wooledge wrote: > On Tue, Aug 17, 2021 at 04:54:54PM -0400, Gene Heskett wrote: > > Where do I find the recipe to update stretch to buster? > > It's still at > . Thats fine but its html in little

Re: Still on stretch, getting ready for bullseye

On Tue 17 Aug 2021 at 22:48:34 +, Andrew M.A. Cater wrote: > On Tue, Aug 17, 2021 at 11:05:44PM +0100, Brian wrote: > > On Tue 17 Aug 2021 at 16:54:54 -0400, Gene Heskett wrote: > > > > > Where do I find the recipe to update stretch to buster? > > > > What, in this helpful thread, do you

Re: Still on stretch, getting ready for bullseye

On Tue, Aug 17, 2021 at 11:05:44PM +0100, Brian wrote: > On Tue 17 Aug 2021 at 16:54:54 -0400, Gene Heskett wrote: > > > Where do I find the recipe to update stretch to buster? > > What, in this helpful thread, do you find difficult to understand? > > You have a collection of important machines

Re: Still on stretch, getting ready for bullseye

On Tue 17 Aug 2021 at 16:54:54 -0400, Gene Heskett wrote: > Where do I find the recipe to update stretch to buster? What, in this helpful thread, do you find difficult to understand? You have a collection of important machines in your charge. The complexity of managing them does not appear to

Re: Still on stretch, getting ready for bullseye

On 17/08/2021 21:57, Greg Wooledge wrote: On Tue, Aug 17, 2021 at 04:54:54PM -0400, Gene Heskett wrote: Where do I find the recipe to update stretch to buster? It's still at . Or to by more precise, that's what most important to

Re: Still on stretch, getting ready for bullseye

On Tue, Aug 17, 2021 at 04:54:54PM -0400, Gene Heskett wrote: > Where do I find the recipe to update stretch to buster? It's still at .

Re: Still on stretch, getting ready for bullseye

On Tuesday 17 August 2021 12:00:57 Andrew M.A. Cater wrote: > On Tue, Aug 17, 2021 at 07:24:45AM -0400, Gene Heskett wrote: > > Greetings all; > > > > I just installed another sata controller and 4 1 T-byte Samsung > > SSD's. > > > > The controller claims to be a 15 port port expander, but only 6

Re: Still on stretch, getting ready for bullseye

On Tue 17 Aug 2021 at 10:07:18 (-0400), Gene Heskett wrote: > [Subject: Re: Still on stretch, getting ready for bullseye] You have a habit of running systems about one release behind the current stable, so can you just check that you really mean to upgrade your machine to bullseye

Re: Still on stretch, getting ready for bullseye

On 8/17/21 4:24 AM, Gene Heskett wrote: Greetings all; I just installed another sata controller and 4 1 T-byte Samsung SSD's. The controller claims to be a 15 port port expander, but only 6 are bonded out, and collectively show up at ata7 in dmesg. They show up as /dev/sde/f/g/h but have not

Re: Still on stretch, getting ready for bullseye

On Tue 17 Aug 2021 at 13:42:25 -0400, Greg Wooledge wrote: > On Tue, Aug 17, 2021 at 06:36:15PM +0100, Brian wrote: > > Comment out *everything* in sources.list and then edit to have only > > > > deb http://deb.debian.org/debian/ stretch main contrib non-free > > > > Update and upgrade. > >

Re: Still on stretch, getting ready for bullseye

On Tue, Aug 17, 2021 at 06:36:15PM +0100, Brian wrote: > Comment out *everything* in sources.list and then edit to have only > > deb http://deb.debian.org/debian/ stretch main contrib non-free > > Update and upgrade. ... and then make all the changes necessary for stretch. > Chande stretch

Re: Still on stretch, getting ready for bullseye

On Tue 17 Aug 2021 at 16:00:57 +, Andrew M.A. Cater wrote: [...] > I think the others have mostly covered this but: But it bears repeating for the OP and others. Comment out *everything* in sources.list and then edit to have only deb http://deb.debian.org/debian/ stretch main contrib

Re: Still on stretch, getting ready for bullseye

On Tue, Aug 17, 2021 at 07:24:45AM -0400, Gene Heskett wrote: > Greetings all; > > I just installed another sata controller and 4 1 T-byte Samsung SSD's. > > The controller claims to be a 15 port port expander, but only 6 are > bonded out, and collectively show up at ata7 in dmesg. > > They

Re: Still on stretch, getting ready for bullseye

On Tuesday 17 August 2021 09:08:43 Greg Wooledge wrote: > On Tue, Aug 17, 2021 at 09:01:32AM -0400, Gene Heskett wrote: > > Tell me where to read about an insitu upgrade from stretch to > > buster, > > https://www.debian.org/releases/stable/amd64/release-notes/ > > > root@coyote:~$ apt update > >

Re: Still on stretch, getting ready for bullseye

On Tuesday 17 August 2021 09:01:32 Gene Heskett wrote: My mis-steak, its Tuesday not Monday. > On Tuesday 17 August 2021 08:05:27 Dan Ritter wrote: > > Gene Heskett wrote: > > > Greetings all; > > > > > > I just installed another sata controller and 4 1 T-byte Samsung > > > SSD's. > > > > > > The

Re: Still on stretch, getting ready for bullseye

On 2021-08-17 9:08 a.m., Greg Wooledge wrote: > On Tue, Aug 17, 2021 at 09:01:32AM -0400, Gene Heskett wrote: >> Tell me where to read about an insitu upgrade from stretch to buster, > > https://www.debian.org/releases/stable/amd64/release-notes/ > >> root@coyote:~$ apt update >> Hit:1

Re: Still on stretch, getting ready for bullseye

On Tue, Aug 17, 2021 at 09:08:43AM -0400, Greg Wooledge wrote: > On Tue, Aug 17, 2021 at 09:01:32AM -0400, Gene Heskett wrote: > > Tell me where to read about an insitu upgrade from stretch to buster, > > https://www.debian.org/releases/stable/amd64/release-notes/ Whoops. Google gave me the

Re: Still on stretch, getting ready for bullseye

On Tue, Aug 17, 2021 at 09:01:32AM -0400, Gene Heskett wrote: > Tell me where to read about an insitu upgrade from stretch to buster, https://www.debian.org/releases/stable/amd64/release-notes/ > root@coyote:~$ apt update > Hit:1 http://security.debian.org stretch/updates InRelease > Hit:2

Re: Still on stretch, getting ready for bullseye

On Tuesday 17 August 2021 08:05:27 Dan Ritter wrote: > Gene Heskett wrote: > > Greetings all; > > > > I just installed another sata controller and 4 1 T-byte Samsung > > SSD's. > > > > The controller claims to be a 15 port port expander, but only 6 are > > bonded out, and collectively show up at

Re: Still on stretch, getting ready for bullseye

Gene Heskett wrote: > Greetings all; > > I just installed another sata controller and 4 1 T-byte Samsung SSD's. > > The controller claims to be a 15 port port expander, but only 6 are > bonded out, and collectively show up at ata7 in dmesg. > > They show up as /dev/sde/f/g/h but have not

Still on stretch, getting ready for bullseye

Greetings all; I just installed another sata controller and 4 1 T-byte Samsung SSD's. The controller claims to be a 15 port port expander, but only 6 are bonded out, and collectively show up at ata7 in dmesg. They show up as /dev/sde/f/g/h but have not otherwise been touched. So I thought I'd

Re: Updating kernels impossible when /boot is getting full

On Sun 01 Aug 2021 at 21:55:15 (+0200), Kamil Jońca wrote: > David Christensen writes: > > [...] > > > > A 500 GB boot partition would be enough for several kernels, etc., on > > Debian 10 amd64. > > OP wrote about 500 _M_ bytes (0.5G), and I can confirm, this is rather > little, when trying

Re: Updating kernels impossible when /boot is getting full

On 8/1/21 12:55 PM, Kamil Jońca wrote: David Christensen writes: [...] A 500 GB boot partition would be enough for several kernels, etc., on Debian 10 amd64. OP wrote about 500 _M_ bytes (0.5G), Please see: > On 8/1/21 3:29 PM, David Christensen wrote: >> I see a typo in my post --

Re: Updating kernels impossible when /boot is getting full

David Christensen writes: [...] > > A 500 GB boot partition would be enough for several kernels, etc., on > Debian 10 amd64. OP wrote about 500 _M_ bytes (0.5G), and I can confirm, this is rather little, when trying updating kernels. KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html

Re: Updating kernels impossible when /boot is getting full

Sorry, Stefan.  This was supposed to go to the list. On 8/2/21 11:02 PM, Marc Shapiro wrote: On 8/1/21 9:33 PM, Stefan Monnier wrote: So really think hard before splitting off a filesystem outside of volume management. I believe it is more likely to cause problems than it is to avoid

Re: Updating kernels impossible when /boot is getting full

On 8/2/21 12:47 PM, Greg Wooledge wrote: On Mon, Aug 02, 2021 at 12:43:27PM -0700, David Christensen wrote: I'd rather not install dracut. Me too. So why not use lsinitramfs -l ? Why keep reinventing the wheel? unicorn:~$ lsinitramfs -l /boot/initrd.img-5.10.0-8-amd64 | head -12 drwxr-xr-x

Re: Updating kernels impossible when /boot is getting full

On Mon, Aug 02, 2021 at 12:43:27PM -0700, David Christensen wrote: > I'd rather not install dracut. Me too. So why not use lsinitramfs -l ? Why keep reinventing the wheel? unicorn:~$ lsinitramfs -l /boot/initrd.img-5.10.0-8-amd64 | head -12 drwxr-xr-x 2 root root0 Apr 25

Re: Updating kernels impossible when /boot is getting full

On 8/2/21 11:29 AM, Greg Wooledge wrote: On Mon, Aug 02, 2021 at 11:11:11AM -0700, David Christensen wrote: Please post your console session showing how you created initrd.img-5.10.0-8-amd64.txt.gz. I didn't. It was created automatically when I installed dracut-core. Prior to that, it was

Re: Updating kernels impossible when /boot is getting full

On Mon, Aug 02, 2021 at 11:11:11AM -0700, David Christensen wrote: > On 8/1/21 3:51 PM, Greg Wooledge wrote: > > On Sun, Aug 01, 2021 at 03:29:07PM -0700, David Christensen wrote: > > > 2021-08-01 13:52:37 root@dipsy ~ > > > > # gunzip -c /boot/initrd.img-4.19.0-17-amd64 | cpio -i -d -H newc > >

Re: Updating kernels impossible when /boot is getting full

On 8/1/21 3:51 PM, Greg Wooledge wrote: On Sun, Aug 01, 2021 at 03:29:07PM -0700, David Christensen wrote: 2021-08-01 13:52:37 root@dipsy ~ # gunzip -c /boot/initrd.img-4.19.0-17-amd64 | cpio -i -d -H newc --no-absolute-filenames 246741 blocks That may not extract the full content of the

Re: Updating kernels impossible when /boot is getting full

On Mon 02 Aug 2021 at 08:04:25 (+0300), Teemu Likonen wrote: > * 2021-08-01 16:00:24-0400, Greg Wooledge wrote: > > > Someone who knows what makes initrd images swell up, please step in > > and advise. And no, it's not "try using a different compression > > algorithm". It's something in the

Re: Updating kernels impossible when /boot is getting full

On Sun 01 Aug 2021 at 13:21:11 (+0300), Ilkka Huotari wrote: > Thanks. I should have said, that also apt-get autoremove fails: > > $ sudo apt-get autoremove > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > 0 upgraded, 0 newly installed, 0 to

Re: Updating kernels impossible when /boot is getting full

On 01/08/2021 23:51, Greg Wooledge wrote: > On Sun, Aug 01, 2021 at 03:29:07PM -0700, David Christensen wrote: >> 2021-08-01 13:52:37 root@dipsy ~ >> # file /boot/initrd.img-4.19.0-17-amd64 >> /boot/initrd.img-4.19.0-17-amd64: gzip compressed data, last modified: Sun >> Jul 25 19:43:38 2021, from

Re: Updating kernels impossible when /boot is getting full

> So really think hard before splitting off a filesystem outside of > volume management. I believe it is more likely to cause problems > than it is to avoid problems. All my machines have a separate /boot partition (and everything else in LVM). These are all "historical accidents", because at

Re: Updating kernels impossible when /boot is getting full

* 2021-08-01 16:00:24-0400, Greg Wooledge wrote: > Someone who knows what makes initrd images swell up, please step in > and advise. And no, it's not "try using a different compression > algorithm". It's something in the *content*. Initrd image is large when the pairing kernel is compiled with

Re: Updating kernels impossible when /boot is getting full

On Mon, 2 Aug 2021 at 08:33, Andy Smith wrote: > At this point there will probably be some people who consider > themselves veterans saying that one must absolutely split things off > because of various reasons like differing mount options being > desirable, ability to re-use contents of /home

Re: Updating kernels impossible when /boot is getting full

On Sun, Aug 01, 2021 at 03:29:07PM -0700, David Christensen wrote: > 2021-08-01 13:52:37 root@dipsy ~ > # file /boot/initrd.img-4.19.0-17-amd64 > /boot/initrd.img-4.19.0-17-amd64: gzip compressed data, last modified: Sun > Jul 25 19:43:38 2021, from Unix, original size 126331392 Your initrd

Re: Updating kernels impossible when /boot is getting full

Hello, OP: You are pretty safe deleting (rm) vmlinuz* and initrd* things from /boot that are related to any kernels you aren't actually booted into at the time. That can give you back enough space to let apt finish what it wants to do. Just remember to do: # update-initramfs -u -k all

Re: Updating kernels impossible when /boot is getting full

On 8/1/21 1:00 PM, Greg Wooledge wrote: On Sun, Aug 01, 2021 at 12:45:27PM -0700, David Christensen wrote: On 7/31/21 9:20 PM, Ilkka Huotari wrote: -rw-r--r-- 1 root root 153M heinä 10 14:22 initrd.img-5.11.0-22-generic -rw-r--r-- 1 root root 151M heinä 23 13:13

Re: Updating kernels impossible when /boot is getting full

Am Sonntag, 1. August 2021, 22:00:24 CEST schrieb Greg Wooledge: Try to uninstall old kernels with aptitude purge ~n5.10.0-7-* for uninstalling all related packages with "5.10.0-7-" in its name. Do it with all unneeded kernels. It will also uninstall headers and modules for that

Re: Updating kernels impossible when /boot is getting full

On Sun, Aug 01, 2021 at 12:45:27PM -0700, David Christensen wrote: > On 7/31/21 9:20 PM, Ilkka Huotari wrote: > > -rw-r--r-- 1 root root 153M heinä 10 14:22 initrd.img-5.11.0-22-generic > > -rw-r--r-- 1 root root 151M heinä 23 13:13 initrd.img-5.11.0-25-generic > A 500 GB boot partition would

Re: Updating kernels impossible when /boot is getting full

On 7/31/21 9:20 PM, Ilkka Huotari wrote: Hi, I'm using Ubuntu 21. My /boot partition size is 500M and it's getting full: /dev/sda1 446M 352M 61M 86% /boot What's taking space are mainly these: -rw-r--r-- 1 root root 153M heinä 10 14:22 initrd.img-5.11.0-22-generic -rw-r

Re: Updating kernels impossible when /boot is getting full

Ilkka Huotari [2021-08-01 07:20:20] wrote: > I'm using Ubuntu 21. My /boot partition size is 500M and it's getting full: Notice that this is a Debian mailing-list, so questions about Ubuntu are not really "on topic". AFAIK Ubuntu handles the initrd files and kernels slightly dif

Re: Updating kernels impossible when /boot is getting full

On Sunday 01 August 2021 06:57:54 Paul Duncan wrote: > Hmmm... Thats a little annoying. > > Maybe try removing the -22 image manually, like this: > > apt-get remove linux-image-5.11.0-22 > > See if that works. If it doesn't, I'm not sure what else to try - > other than a re-install - at which I

Re: Updating kernels impossible when /boot is getting full

On 01/08/2021 13:34, didier gaumet wrote: > Hello, > > Disclaimer: I have never tested what is following. > > Perhaps another way of keeping two kernels without increasing the size oft > the /boot partition would be to decrease the size of the initrd files: by > default they are built with

Re: Updating kernels impossible when /boot is getting full

Paul Duncan wrote: ... > Hmmm... Thats a little annoying. > > Maybe try removing the -22 image manually, like this: > > apt-get remove linux-image-5.11.0-22 if that is the kernel that is being run then you risk putting your system into a completely unbootable state (if the upgrade failed that

Re: Re: Updating kernels impossible when /boot is getting full

Hello, Disclaimer: I have never tested what is following. Perhaps another way of keeping two kernels without increasing the size oft the /boot partition would be to decrease the size of the initrd files: by default they are built with allmost all possible modules, but they can be built with

Re: Re: Updating kernels impossible when /boot is getting full

Hmmm... Thats a little annoying. Maybe try removing the -22 image manually, like this: apt-get remove linux-image-5.11.0-22 See if that works. If it doesn't, I'm not sure what else to try - other than a re-install - at which I would make /boot a little bigger :-) I'm sure others more

Re: Updating kernels impossible when /boot is getting full

On 2021-08-01 at 06:21, Ilkka Huotari wrote: > Hi Paul, > > Thanks. I should have said, that also apt-get autoremove fails: > > $ sudo apt-get autoremove > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > 0 upgraded, 0 newly installed, 0 to

Re: Re: Updating kernels impossible when /boot is getting full

Hi Paul, Thanks. I should have said, that also apt-get autoremove fails: $ sudo apt-get autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed.

Re: Updating kernels impossible when /boot is getting full

using Ubuntu 21. My /boot partition size is 500M and it's getting full: > > /dev/sda1 446M 352M 61M 86% /boot > > What's taking space are mainly these: > > -rw-r--r-- 1 root root 153M heinä 10 14:22 initrd.img-5.11.0-22-generic > -rw-r--r-- 1 root root 151M hein

Updating kernels impossible when /boot is getting full

Hi, I'm using Ubuntu 21. My /boot partition size is 500M and it's getting full: /dev/sda1 446M 352M 61M 86% /boot What's taking space are mainly these: -rw-r--r-- 1 root root 153M heinä 10 14:22 initrd.img-5.11.0-22-generic -rw-r--r-- 1 root root 151M heinä 23 13:13

getting apt-cacher-ng to pass auth through

Hi, I would like to use apt-cacher-ng to cache the updates from enterprise.proxmox.com. One thing about this repo is that they have two different kinds, the http one and the https one, the http one is non-enterprise and open to all, but the https one is closed and needs a subscription with a

Re: PC fan getting very loud

Alexander V. Makartsev wrote: Thank you Alexander V. Makartsev > You can monitor and log temperatures and other characteristics with > 'psensor'. > TCase of i5-4570T is only 66.35°C and that means CPU will have to keep > the temperature at that point or lower. > I'd expect an idle temperature

Re: PC fan getting very loud because of CPU load

Celejar wrote: > https://old.reddit.com/r/uBlockOrigin/comments/mu2qcm/indefinitely_increasing_blocked_elements/ > > I'm not sure that I would interpret this sort of thing as the website > putting up an aggressive fight or deliberately trying to burn out > anyone's computer, but it is an

Re: PC fan getting very loud because of CPU load

On Sat, 8 May 2021 17:18:35 -0400 Dan Ritter wrote: > Bret Busby wrote: > > > > I think this goes to the issue of client side processing, as opposed to > > server side processing ( I believe, and, argue, that all processing involved > > with web sites, should be server side, if the web sites

Re: PC fan getting very loud

On Sun, 2021-05-09 at 12:13 +0200, Thomas Schmitt wrote: > Hi, > > Alexander V. Makartsev wrote: > > > Put this mini-PC under any, not just Firefox, multi-threaded workload > > > and you will have the same outcome. > > deloptes wrote: > > What would be a good test to find out if this theory is

Re: PC fan getting very loud

Hi, Alexander V. Makartsev wrote: > > Put this mini-PC under any, not just Firefox, multi-threaded workload > > and you will have the same outcome. deloptes wrote: > What would be a good test to find out if this theory is true? Did you already compare the Firefoxes about the number of threads

Re: PC fan getting very loud

On 09.05.2021 12:49, deloptes wrote: Alexander V. Makartsev wrote: On 09.05.2021 02:30, deloptes wrote: Charles Curley wrote: Fujitsu ESPRIMO Q520 when opening some sh*tty web sitesin firefox the fan gets extremly noisy. I have a similar problem with some of my older laptops. I have

Re: PC fan getting very loud

Alexander V. Makartsev wrote: > On 09.05.2021 02:30, deloptes wrote: >> Charles Curley wrote: >> Fujitsu ESPRIMO Q520 when opening some sh*tty web sitesin firefox the fan gets extremly noisy. >>> I have a similar problem with some of my older laptops. I have switched >>> to Vivaldi

Re: PC fan getting very loud because of CPU load

Bret Busby wrote: > I think this goes to an issue, over which, I tend to get into heated > arguments, including with my wife, who is a software developer, who > develops web sites that I believe to be responsible. > > In the original post, from memory, was stated that it happened with some > web

Re: PC fan getting very loud

On 09.05.2021 02:30, deloptes wrote: Charles Curley wrote: Fujitsu ESPRIMO Q520 when opening some sh*tty web sitesin firefox the fan gets extremly noisy. I have a similar problem with some of my older laptops. I have switched to Vivaldi (based on chromium), and that has reduced the problem

Re: PC fan getting very loud because of CPU load

deloptes [2021-05-08 21:33:47] wrote: > Dan Ritter wrote: >> It is also the case that fans are cheap. Replacing one for >> $10-20 is generally good for another 5-10 years. > But the question is why it runs > 100% - the fan is not that important in > the case. It could be replaced with not so loud

<    1   2   3   4   5   6   7   8   9   10   >