You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: Installation » Default size of the /boot partition » 2016-12-16 13:48:54
alt-F2 #to get to a console with a command prompt umount <mountpoint> vgchange -a n <volume_group_name> cryptsetup luksClose label
The umount and vgchange are not strictly necessary as the volume group can be deleted from the installer (after deleting the logical volumes). And the partition being used as physical group can be set as unused.
Now for the cryptsetup luksClose command, it closes the encrypted volume but the installer does not seem aware of that, and keeps trying to use it as if it were open. Even if you go back to the main menu, and come back to the partitioning menu, you'll have an error message because the installer seems to assume that the encrypted volume should already be open.
#2 Re: Installation » Default size of the /boot partition » 2016-12-15 16:47:18
It's not clear to me what you're doing in the above. I don't use guided partitioning, but I thought it was not possible to change the settings that the partitioner uses.
250mb for /boot should be more than enough unless you're planning to do something unusual.
I had that funny problem with an Ubuntu once, the kernels had been accumulating in the /boot partition, until it got full during an update and I had to clean up the mess. If Debian (and now Devuan) remove old kernels, everything's fine.
About the encryption, it's just a limitation of the installer. Let's say you start by asking a guided installation of an encrypted root partition. You enter a passphrase, accept the changes. Then you change your mind, you want to redo the layout from scratch: it's impossible. The installer does not let you close the container. The partition is "blocked".This is also the case when you manually create and open an encrypted container. Once it's open, the only way you can change the partition is by rebooting and redoing the installation.
#3 Installation » Default size of the /boot partition » 2016-12-15 10:54:54
- Malinas
- Replies: 5
Hi everyone,
As I'm playing around with the beta2 installer, I'm once again reminded of some weaknesses of the installer. My typical setup is to have a /boot partition and an encrypted root partition. So the guided installation does that for me, but:
The /boot partition size is only 256MB. This could be a problem with kernels and associated files taking more and more space. Right now on another machine I have two kernels installed there, already taking up 64MB. If I ever have to resize the partition, it's going to be a pain (since the other partition is encrypted and can't be shrunk).
It is impossible to undo the setting up of the 2nd partition (usually /dev/sda2) as an encrypted partition. There's something amiss in the installer, it cannot properly let go of the encrypted partition. This means that in case I want to change the size of the /boot partition, I need to reboot (hopefully it's at the beginning of the installation process, so not much time wasted).
So, my question is not about how to solve the problem (I know how to do it in manual mode), but rather about other's experiences on the subject. Has anyone had problems in the past with the default size of the /boot partition? Does it need to be changed?
#4 Re: Forum Feedback » [SPLIT] URL post limitations » 2016-12-07 23:41:34
Please don't restrict the new users in any way, people coming here for help will be frustrated if they can't for instance post a link to an online dump of a log file. Others would game the system just to access these privileges (see for instance the bad example of stack overflow).
I think that measures should be taken at the source first, i.e. making the registration process a tad more difficult for bots.
#5 Re: Documentation » Moving /home to a separate partition after installation. » 2016-12-07 19:35:48
Hi edbarx,
Since you mention using a Live CD starting from step 7, why not do everything from the Live CD? I think it also makes it easier for the preparation of the partitions, since it's not possible to shrink some FS (ext4, for instance) online. And if during the reboot the /home does not mount correctly, it's still possible to log in as root and fix the /etc/fstab.
#6 Re: Forum Feedback » forgiveness regarding proofreading edits » 2016-12-07 19:10:55
It might cause confusion for someone replying immediately to your post, especially if they talk about something that you are about to edit. It's not going to be a problem at the moment, but once the forum reaches full speed, with flocks of users constantly using it, these editing "conflicts" will definitely happen.
My rule of thumb when using a forum: always Preview your post to proofread it, and if you're writing a reply, also check whether someone replied in the meantime.
As a side note, you're probably overdoing it if you think that all your posts need to be perfect 
Pages: 1
Board footer
