Re: Making a partition larger without affecting my OS.

Hello, Eli.

On Tue, Mar 17, 2026 at 15:42:55 -0400, Eli Schwartz wrote:
> On 3/14/26 10:06 AM, Dale wrote:
> > Howdy,

> > As some know, on my old and new rig, I compile my updates in a chroot
> > environment.  Then I copy the binaries over and use the -k option on my
> > running OS.  That way I don't have a crash when one program is updated
> > and another it depends on is not yet updated. Anyway, my chroot is
> > getting squeezed a little.  I need to expand it another 30GBs or so so
> > that I don't get not enough space errors. It's only the largest packages
> > right now but the next larger ones are growing and will start having
> > issues as well.  I have a m.2 stick for my OS.  It's a 1TB stick.  I
> > have plenty of space unused. I did the OS first and then did a partition
> > for the chroot thingy. The partition named build-part is the chroot. 
> > The parts above it are the OS.  This is the current layout.

> Nobody mentions the elephant in the room! Why have separate partitions?

There are good reasons, and I'm not telling you anything new.  ;-)

I have a separate /boot partition, since this needs to be an ancient MS
filesystem which I don't want my sole partition to be.

I have a separate /home partition, so that in the event of my system
breaking, I can use a backup system, still keeping the same /home.

I have a separate /var/db/repos/gentoo partition with lots of inodes, to
contain lots of small ebuild files.

> I have a build chroot too -- it is on the main FS. It works totally fine
> and can grow larger automatically.

Yes, that is one of the advantages of having a single partition.  As
always in GNU/Linux, one has the choice and must make a choice.  Our
choices are different.

> -- 
> Eli Schwartz

-- 
Alan Mackenzie (Nuremberg, Germany).