Initialized the drive, reinstalled Trisquel...
- Login o registrati per inviare commenti
- but there's no way to increase the / partition to anything more than 25GB... OK, whatever, I'll be looking for huge directories and moving them to /home and putting in a symlink. It would be nice to be able to increase / allocation easily, but that apparently isn't in The Plan. I was able to install Guix using apt, but this time, when I went to do a "guix pull" nothing happened after "updating Guix channel from Git depository at ...savannah.org" ... Tried it three times this afternoon, once it sat for an hour and a half doing nothing. Tried it again and still nothing, did d C-z, a ps -a, and a kill -9 to kill the process, just to be sure -did that each time, btw. So is Guix just dead?
More - the latest emacs that apt installs is 27.1 which is way, way outdated, so there's no way to get 30.1 unless I either compile from source, guix pull decides to work, or I dump trisquel and use Debian 12 instead...
There are easier ways, using either Flatpak or AppImage, as prospero and I have recently explained to beardystarstuff:
guix pull has now decided to work. Oddly enough the AllTrails app on my phone shot craps too, so maybe there's something weird with some parts of the internet today. Still took the walk... and the temp wasn't "78 degrees", it was a lot closer to 90.
no way to increase the / partition to anything more than 25GB.
Because /home is on an XFS filesystem, isn't it? XFS cannot be shrunk. With a backup (for instance on an external drive) of the user data, you may want to boot a live system, delete the partition for /home and extend the root partition. Either you decide to have it take up the whole space or not.
In the first case, the home directories will be on the root partition. Still using the live system, you can copy them from the backup. In the second case, you can recreate a partition for /home, maybe choosing ext4, which can be shrunk and copy there the home directories. In both cases, you need to modify /etc/fstab (that of the installed system and not of the live system): in the first case, just delete the line related to /home; in the second case, modify it to properly identify the new partition (you can use UUID but also classical devices such as /dev/sda3), its type (possibly ext4 instead of xfs) and the mount options (writing "defaults" should be fine).
Nope, both / and /home are ext4, according to /etc/fstab on the installed system.
Maybe /home is too full to have its partition shrunk then? The df command can tell.
I am a translator!
> when I went to do a "guix pull" nothing happened after "updating Guix channel from Git depository at ...savannah.org"
Try guix pull --url=https://codeberg.org/guix/guix
See https://guix.gnu.org/fr/blog/2025/migrating-to-codeberg/. I have not fully understood yet which file to update so that you don't need to manually add this option at every guix pull.
> but there's no way to increase the / partition to anything more than 25GB
As Magic Banana asked, what does "df -h " say? And "lsblk --fs". My previous suggestion was, on a fresh install (so, before installing guix), to move the /home logical volume (if you use LVM) to the volume used for /, delete the volume for home, enlarge the volume for / to take the whole space, and remove the /home line /etc/fstab.
I use guix on Trisquel but only for a few packages, darktable and torbrowser, ungoogled-chromium on aramo only (it is in ecne repository). I only use ungoogled-chromium if something I need to use seems not to work on abrowser (rarely, but it happens).
I'm just not going to use guix, I'll build stuff from source, this is just too much trouble. and getting rid of all of the files in guix is a huge pain, you can't do it using rm * "argument list is too long".
The find command has a (dangerous) option, -delete. It will allow you to avoid the shell's globing at the origin of the too-long argument list. See https://www.baeldung.com/linux/find-delete-files-directories for instance.
If you seriously intend for people to use this software, you just might think of making it easier to use instead of doing dumb stuff like making root size 25GB, when you know that people will use guix on it - and how big guix is. That's just lousy engineering. And instead of going through all of the hassle to remove those files, I'm just going to reintialize the disk and stert over. The icing on the cake is that gnu.org is unavailable and has been for two days.
If you seriously intend for people to use this software, you just might think of making it easier to use instead of doing dumb stuff like making root size 25GB, when you know that people will use guix on it - and how big guix is.
I very much doubt Guix on Trisquel is popular. Guix definitely is for advanced users, whereas Trisquel targets a large audience.
If you seriously intend for people to use this software, you just might think of making it easier to use instead of doing dumb stuff like making root size 25GB, when you know that people will use guix on it - and how big guix is. That's just lousy engineering. And instead of going through all of the hassle to remove those files, I'm just going to reintialize the disk and stert over. The icing on the cake is that gnu.org is unavailable and has been for two days.
If you seriously intend for people to use this software, you just might think of making it easier to use instead of doing dumb stuff like making root size 25GB, when you know that people will use guix on it - and how big guix is. That's just lousy engineering. And instead of going through all of the hassle to remove those files, I'm just going to reintialize the disk and stert over. The icing on the cake is that gnu.org is unavailable and has been for two days.
If you seriously intend for people to use this software, you just might think of making it easier to use instead of doing dumb stuff like making root size 25GB, when you know that people will use guix on it - and how big guix is. That's just lousy engineering. And instead of going through all of the hassle to remove those files, I'm just going to reintialize the disk and stert over. The icing on the cake is that gnu.org is unavailable and has been for two days.
If you seriously intend for people to use this software, you just might think of making it easier to use instead of doing dumb stuff like making root size 25GB, when you know that people will use guix on it - and how big guix is. That's just lousy engineering. And instead of going through all of the hassle to remove those files, I'm just going to reintialize the disk and stert over. The icing on the cake is that gnu.org is unavailable and has been for two days.
If you seriously intend for people to use this software, you just might think of making it easier to use instead of doing dumb stuff like making root size 25GB, when you know that people will use guix on it - and how big guix is. That's just lousy engineering. And instead of going through all of the hassle to remove those files, I'm just going to reintialize the disk and stert over. The icing on the cake is that gnu.org is unavailable and has been for two days.
If you seriously intend for people to use this software, you just might think of making it easier to use instead of doing dumb stuff like making root size 25GB, when you know that people will use guix on it - and how big guix is. That's just lousy engineering. And instead of going through all of the hassle to remove those files, I'm just going to reintialize the disk and stert over. The icing on the cake is that gnu.org is unavailable and has been for two days.
If you seriously intend for people to use this software, you just might think of making it easier to use instead of doing dumb stuff like making root size 25GB, when you know that people will use guix on it - and how big guix is. That's just lousy engineering. And instead of going through all of the hassle to remove those files, I'm just going to reintialize the disk and stert over. The icing on the cake is that gnu.org is unavailable and has been for two days.
If you seriously intend for people to use this software, you just might think of making it easier to use instead of doing dumb stuff like making root size 25GB, when you know that people will use guix on it - and how big guix is. That's just lousy engineering. And instead of going through all of the hassle to remove those files, I'm just going to reintialize the disk and stert over. The icing on the cake is that gnu.org is unavailable and has been for two days.
If you seriously intend for people to use this software, you just might think of making it easier to use instead of doing dumb stuff like making root size 25GB, when you know that people will use guix on it - and how big guix is. That's just lousy engineering. And instead of going through all of the hassle to remove those files, I'm just going to reintialize the disk and stert over. The icing on the cake is that gnu.org is unavailable and has been for two days.
If you seriously intend for people to use this software, you just might think of making it easier to use instead of doing dumb stuff like making root size 25GB, when you know that people will use guix on it - and how big guix is. That's just lousy engineering. And instead of going through all of the hassle to remove those files, I'm just going to reintialize the disk and stert over. The icing on the cake is that gnu.org is unavailable and has been for two days.