I have installed Gnu Guix as the base operating system on one of my machines. It will likely become my web server eventually. 

(I have another machine running Void Linux within which I’ve installed the Guix System (because its proprietary hardware prevented a base install of Guix’s Libre kernel). This will probably become my mail server. Or vice versa.)

After some searching, I’ve decided to ultimately go with Guix on all my network nodes, for various reasons to include pure open-source ethics, everything-but-the-kitchen-sink Gnu libraries, adaptability of pure GNU/Linux for fledgling development considerations, and a general long-term work-in-progress computer science study project. I would recommend everyone in the LUG to take a stab at it, so we can all go lassie go.

However:

On the machine mentioned first above (the Guix base install, not the Guix System install), I did not encrypt the partitions with any LUKS/LVM upon initial install config, thinking I’d fix it later as needed be. Well, now, it needs be, because of the size limitations of the Linux root / boot partition on a 60 GB solid state drive (SDA). There is a 3 or 4 GB swap part on sda which is in use.

There is also a several TB SATA drive in the machine, formatted as ext4, that can be mounted (SDB). There is an 8 Gb swap part on sdb which does not appear to be in use. 

But now I need that sdb for the whole OS.

Here’s the nut: In the past I’ve been easily able to expand the size of root partitions using various appropriate utilities designed for just such a task. I did this with my Pinephone running Mobian with its microSD ROM, and a SSD Fedora server most recently, but those all had LVM encryption from setup/install. But again, I didn’t encrypt anything during the original install in this case, and I can’t find any instructions to do what I need to do with the Guix machine which don’t assume existing LVM.

I’d rather not do a full reinstall, that seems like a baby out with the bath water solution, but I will if I have to. 

Q: What might be best practice for encrypting existing unencrypted devices and partitions that already exist (assuming there is), so I may proceed with mapping those for my root expansion? There is also a sandbox/VM approach, but that’s not where I was headed with this.

I realize, if I’m the incumbent GUIX expert, then I’m the one who should decipher the Guix documentation on this. But, on the other hand, it really may be a more general question best addressed beneath the OS, so I wanted to ask here before I ask Guix forums.

~~~

Braswell 

Sent fast from my moon unit

I have installed Gnu Guix as the base operating system on one of my machines. It will likely become my web server eventually. 

(I have another machine running Void Linux within which I’ve installed the Guix System (because its proprietary hardware prevented a base install of Guix’s Libre kernel). This will probably become my mail server. Or vice versa.)

After some searching, I’ve decided to ultimately go with Guix on all my network nodes, for various reasons to include pure open-source ethics, everything-but-the-kitchen-sink Gnu libraries, adaptability of pure GNU/Linux for fledgling development considerations, and a general long-term work-in-progress computer science study project. I would recommend everyone in the LUG to take a stab at it, so we can all go lassie go.

However:

On the machine mentioned first above (the Guix base install, not the Guix System install), I did not encrypt the partitions with any LUKS/LVM upon initial install config, thinking I’d fix it later as needed be. Well, now, it needs be, because of the size limitations of the Linux root / boot partition on a 60 GB solid state drive (SDA). There is a 3 or 4 GB swap part on sda which is in use.

There is also a several TB SATA drive in the machine, formatted as ext4, that can be mounted (SDB). There is an 8 Gb swap part on sdb which does not appear to be in use. 

But now I need that sdb for the whole OS.

Here’s the nut: In the past I’ve been easily able to expand the size of root partitions using various appropriate utilities designed for just such a task. I did this with my Pinephone running Mobian with its microSD ROM, and a SSD Fedora server most recently, but those all had LVM encryption from setup/install. But again, I didn’t encrypt anything during the original install in this case, and I can’t find any instructions to do what I need to do with the Guix machine which don’t assume existing LVM.

I’d rather not do a full reinstall, that seems like a baby out with the bath water solution, but I will if I have to. 

Q: What might be best practice for encrypting existing unencrypted devices and partitions that already exist (assuming there is), so I may proceed with mapping those for my root expansion? There is also a sandbox/VM approach, but that’s not where I was headed with this.

I realize, if I’m the incumbent GUIX expert, then I’m the one who should decipher the Guix documentation on this. But, on the other hand, it really may be a more general question best addressed beneath the OS, so I wanted to ask here before I ask Guix forums.

~~~

Braswell 

Sent fast from my moon unit

You have your hands full ;-)
This site has a good summary of

LUKS ---> LVM

LVM ---> LUKS

with its plus and minus that may help in your situation.

-=terry=-
On Sun, 2024-03-17 at 17:54 -0700, Other One wrote:
Quoted reply (55 lines) --------------------------------------------------------------------
Cochise Linux Users Group Mailing List - cochiselinux@freelists.org
For more information: https://cochiselinuxusergroup.org/
Mailing List Archive: https://www.freelists.org/archive/cochiselinux
To unsubscribe: //www.freelists.org/list/cochiselinux