Re: [Trisquel-users] Large Volume FOSS Backup Options
Heh, wild.
Re: [Trisquel-users] Can't update after installing apt-transport-tor
Thanks for clarifying that for me ;)
Re: [Trisquel-users] LIbreboot grub asks for LUKS password twice
Of course it would be easier if I just installed GRUB on disk with the Trisquel installation (I have done some changes to grub that way before on other computers), but I feel redundant to do so and think it will slow down a bit the boot process. Plus all the documentation on the libreboot page points to using the ROM GRUB.
Re: [Trisquel-users] LIbreboot grub asks for LUKS password twice
Thanks for your help. According to the Parabola link I provided above is goes like this: "By default, you will have to enter your LUKS passphrase twice; once in GRUB, and once when booting the kernel. GRUB unlocks the encrypted partition and then loads the kernel, but the kernel is not aware of the fact that it is being loaded from an encrypted volume. Therefore, you will be asked to enter your passphrase a second time. A workaround is to put a key file inside initramfs, with instructions for the kernel to use it when booting. This is safe, because /boot/ is encrypted (otherwise, putting a key file inside initramfs would be a bad idea).". That's what they say. Hence me thinking that it is indeed the same password (as in it is one only password and not two separate passwords that just happen to be the same). I tried following their procedure but they make use of a command "mkinitcpio" and it's configuration file. However I can't get it to work in Trisquel 8. Parabola's way of installing in Libreboot systems is slightly different so I am unsure how to adjust it to our own. I have tried reading other pages online about using a key file to unlock partitions but there is much information I don't understand.
Re: [Trisquel-users] Hello everyone! I have a question about this part of Trisquel GNU/Linux
> I wanted to know if plans to dropping 32-bit support and only 64 > will be the future for Trisquel 9 Etiona? Trisquel 9 will be based on Ubuntu 18.04. Since 18.04 has 32-bit support I do not think it will be a problem for Trisquel 9. Trisquel 9 will also add support for some non-x68 architectures. Do you know when Ubuntu is planning to drop 32-bit support? There is a 32-bit ISO for the 19.04 prerelease,[1] so it seems that they have not done so yet. If they drop 32-bit support before 20.04 then this will become an issue with Trisquel 10. If 20.04 does have 32-bit support then it won't become an issue until Trisquel 11. [1] http://cdimage.ubuntu.com/netboot/disco/ signature.asc Description: PGP signature
Re: [Trisquel-users] LIbreboot grub asks for LUKS password twice
On 14/01/19 13:46, Ignacio Agulló wrote: > So, definitely it is not the same password twice, but two passwords > that happen to be the same. Well, I have my doubts after checking up that the ID volume supplied is the same one the two times. Could it be that the ID and password are for the LUKS and the same password be entered twice, the first one to mount the boot logical volume inside, and the second one to mount the root logical volume inside? -- Ignacio Agulló · agu...@ati.es 0xC6AB2D51.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: [Trisquel-users] Large Volume FOSS Backup Options
16 TB hard dries have also been announced: https://soylentnews.org/article.pl?sid=19/01/10/176=rss
[Trisquel-users] Hello everyone! I have a question about this part of Trisquel GNU/Linux
Recently I've been seeing that some GNU/Linux distributions have been dropping 32-bit support out of their plans. This including Ubuntu and Arch (although, for the latter, there is arch32 which fixes that and the libre-projects known as Parabola GNU/Linux and Hyperbola have 32-bit versions as well) However, as the Trisquel project changed bases from Debian to Ubuntu 16.04. I wanted to know if plans to dropping 32-bit support and only 64 will be the future for Trisquel 9 Etiona? As upstream Ubuntu and its derivatives have all dropped support for this architecture, which I see a big shame. Have a good day, cheers! - Symphony
Re: [Trisquel-users] Large Volume FOSS Backup Options
... Interesting. BackInTime's automatic backup is not buggy... Not sure I want to swap to that particular problem. I need hourly automatic backups, per day. Once the day passes, BackInTime determines if any of the backups were worth keeping ... Anyway, I did some research just now and it seems that 12 TB Hard Disks exist! Not cheap, but since I use my backups for professional purposes, I might need to invest in that.
Re: [Trisquel-users] Can't seem to make bootable install USB
Let's try in the terminal? type sudo -s then cat /directory/trisquelmini.iso > /dev/sdb When "/dev/sdb" is your pen drive, be sure about this. Only work if you use "sudo -s".
Re: [Trisquel-users] LIbreboot grub asks for LUKS password twice
On 14/01/19 02:44 wrote: > I'm not sure that's the case... I mean, it only asked for one password > during the Trisquel 8 installation process, the Full Disk Encryption > password. Maybe it is the case of being necessary to unlock both boot > and swap? > However according to the Parabola guide, it is possible to automate > that process, and I am trying to do that. However it doesn't seem to > work for Trisquel, and that's what I need some help with. I attach a > picture of the second time the system asks for the password. It goes like this: -Libreboot asks you for the password for the /boot logical volume, mounts it and starts the boot process. -The boot process asks you for the password for the / (root) logical volume, mounts it and starts the system. As for why does Libreboot set two separated logical volumes instead of one in order to get full disk encryption, I can only guess that it is so because it builds on the more common [non-full] disk encryption procedure, that encrypts everything except for the /boot logical volume so the BIOS can read it. Rather than creating a new procedure that encrypted the entire filesystem in a single logical volume, they take the already existing procedure and add a second encryption for the /boot logical volume. What I can tell you is that you get some error messages that shouldn't be there. Everything goes right until "Begin: Mounting root file system...". But then, you get these unexpected messages: - Start quote - Volume group "grubcrypt" not found Cannot process volume group grubcrypt lvmetad is not active yet, using direct activation during sysinit Volume group "grubcrypt" not found Cannot process volume group grubcrypt - End quote - After that, I am surprised to see that the start process continues without hindrance. You get the prompt for the root logical-volume password, "Please unlock disk sdb_crypt", mine is different: "Unlocking the disk ... (sdb1_crypt) Enter passphrase". We are using different Libreboot versions, yours probably newer than mine. So, definitely it is not the same password twice, but two passwords that happen to be the same. But when it comes to your real question, how to avoid being requested two passwords, I'm sorry that I don't know about the file option. I never bothered me to introduce two passwords at each start. -- Ignacio Agulló · agu...@ati.es 0xC6AB2D51.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
