I'm thinking of separating /usr onto its own partition so that I can have it mounted read-only except while updating it. I'd prefer not to have to make an init thingy, not having needed one up to now. Besides, some machines have things like early-ucode or amd-uc.
I've found a few guides on the Web, but I'm still confused. Is there a simple guide to doing this? I know of at least one subscriber here who's done it. :)
If something you need for booting with separate /usr is missing that would be a FSH bug and is probably worth reporting unless you're doing something truly arcane with your system.
Hello list,
I'm thinking of separating /usr onto its own partition so that I can have it mounted read-only except while updating it. I'd prefer not to have to make an init thingy, not having needed one up to now. Besides, some machines have things like early-ucode or amd-uc.
I've found a few guides on the Web, but I'm still confused. Is there a simple guide to doing this? I know of at least one subscriber here who's done it. :)
You may can do it the way you are wanting to but for how long is the question. Odds are high that at some point, you will have a system that won't boot because something that's needed isn't there....
I'm thinking of separating /usr onto its own partition so that I can
have it mounted read-only except while updating it. I'd prefer not to
have to make an init thingy, not having needed one up to now. Besides,
some machines have things like early-ucode or amd-uc.
On Wed, 14 Sep 2022 16:50:45 +0100, Peter Humphrey wrote:
I'm thinking of separating /usr onto its own partition so that I can
have it mounted read-only except while updating it. I'd prefer not to
have to make an init thingy, not having needed one up to now. Besides,
some machines have things like early-ucode or amd-uc.
Most of this has already been answered, except for your final point. You
can load more than one initrd at boot, so you can still apply microcode updates. For example, with systemd-boot
title Desktop
version 5.15.59-gentoo
linux /vmlinuz-5.15.59-gentoo
options root=LABEL=blah blah
initrd /amd-uc.img
initrd /initramfs-5.15.59-gentoo.img
I use dracut to create the initrd, which is so straighforward even Dale
can't break it ;-)
On Wednesday, 14 September 2022 23:09:59 BST Neil Bothwick wrote:
On Wed, 14 Sep 2022 16:50:45 +0100, Peter Humphrey wrote::)
I'm thinking of separating /usr onto its own partition so that I canMost of this has already been answered, except for your final point. You
have it mounted read-only except while updating it. I'd prefer not to
have to make an init thingy, not having needed one up to now. Besides,
some machines have things like early-ucode or amd-uc.
can load more than one initrd at boot, so you can still apply microcode
updates. For example, with systemd-boot
title Desktop
version 5.15.59-gentoo
linux /vmlinuz-5.15.59-gentoo
options root=LABEL=blah blah
initrd /amd-uc.img
initrd /initramfs-5.15.59-gentoo.img
I use dracut to create the initrd, which is so straighforward even Dale
can't break it ;-)
That seems to be the way to go then - even dinosaurs die out in the end. Perhaps Dale will show us the command he referred to.
Thank you all for your help.
... I then build the init thingy. This is Neil's command that he posted. From my understanding, the kernel symlink needs to point to the correct kernel version.
dracut --kver=$(cat include/config/kernel.release)
On Thursday, 15 September 2022 11:00:25 BST Dale wrote:
... I then build the init thingy. This is Neil's command that he posted.That's the bit I was hoping for. Thanks Dale.
From my understanding, the kernel symlink needs to point to the correct
kernel version.
dracut --kver=$(cat include/config/kernel.release)
I don't use grub-2; the very thought of it makes me shudder. I could contemplate grub-1, but it can't handle EFI.
I switched to grub2 a while back. I've thought of using something else
but I don't have efi and most of the others are targeted at efi. If I
build a new rig, I'll likely use something else. I'll likely poke Neil until he reveals what he uses or something. ROFL
Note also that the "init thingy" is nothing more than a little
filesystem which contains everything you'd need to make sure was on
your root partition if you were attempting to boot without one.
Building one yourself is generally pretty trivial if you don't like
what dracut/genkernel produce. Utilities, kernel modules, and a script
to set up your main system and switch to it.
On Wednesday, 14 September 2022 23:09:59 BST Neil Bothwick wrote:
On Wed, 14 Sep 2022 16:50:45 +0100, Peter Humphrey wrote:
I'm thinking of separating /usr onto its own partition so that I can
have it mounted read-only except while updating it. I'd prefer not to have to make an init thingy, not having needed one up to now. Besides, some machines have things like early-ucode or amd-uc.
Most of this has already been answered, except for your final point. You can load more than one initrd at boot, so you can still apply microcode updates. For example, with systemd-boot
title Desktop
version 5.15.59-gentoo
linux /vmlinuz-5.15.59-gentoo
options root=LABEL=blah blah
initrd /amd-uc.img
initrd /initramfs-5.15.59-gentoo.img
I use dracut to create the initrd, which is so straighforward even Dale can't break it ;-):
:)
That seems to be the way to go then - even dinosaurs die out in the end. Perhaps Dale will show us the command he referred to.
On the ones you want to omit, is there supposed to be a space in there? Should it be like this instead:
omit_dracutmodules+="bluetoothd"
omit_dracutmodules+="systemd-cryptsetup"
omit_dracutmodules+="cryptsetup"
It may not matter but then again, it just might. Worth a try I'd guess.
:-) :-)
P. S. Finally, someone broke it. ROFLMBO
On Thursday, 15 September 2022 09:57:44 BST I wrote:
On Wednesday, 14 September 2022 23:09:59 BST Neil Bothwick wrote:Well, it's taken a few hours, but I have it working. Just a few wrinkles to clear up:
On Wed, 14 Sep 2022 16:50:45 +0100, Peter Humphrey wrote::
I'm thinking of separating /usr onto its own partition so that I canMost of this has already been answered, except for your final point. You >>> can load more than one initrd at boot, so you can still apply microcode
have it mounted read-only except while updating it. I'd prefer not to
have to make an init thingy, not having needed one up to now. Besides, >>>> some machines have things like early-ucode or amd-uc.
updates. For example, with systemd-boot
title Desktop
version 5.15.59-gentoo
linux /vmlinuz-5.15.59-gentoo
options root=LABEL=blah blah
initrd /amd-uc.img
initrd /initramfs-5.15.59-gentoo.img
I use dracut to create the initrd, which is so straighforward even Dale
can't break it ;-)
:)
That seems to be the way to go then - even dinosaurs die out in the end.
Perhaps Dale will show us the command he referred to.
1. dracut: 90crypt: Could not find any command of '/lib/systemd/systemd- cryptsetup cryptsetup'!
...and similar for bluetooth.
What do I have to include in /etc/dracut.conf.d/mine.conf to silence these? I already omit the relevant modules:
$ grep -e crypt -e blue /etc/dracut.conf.d/mine.conf
omit_dracutmodules+=" bluetoothd "
omit_dracutmodules+=" systemd-cryptsetup "
omit_dracutmodules+=" cryptsetup "
2. dracut: No KEYMAP configured.
$ grep i18n /etc/dracut.conf.d/mine.conf i18n_vars="/etc/conf.d/keymaps:KEYMAP /etc/conf.d/keymaps:WINDOWKEYS / etc/conf.d/consolefont:FONT"
Notice that only KEYMAP is complained about. The FONT in consolefont points to
/usr as well as KEYMAP.
1. dracut: 90crypt: Could not find any command of '/lib/systemd/systemd- cryptsetup cryptsetup'!
...and similar for bluetooth.
What do I have to include in /etc/dracut.conf.d/mine.conf to silence these? I already omit the relevant modules:
$ grep -e crypt -e blue /etc/dracut.conf.d/mine.conf
omit_dracutmodules+=" bluetoothd "
omit_dracutmodules+=" systemd-cryptsetup "
omit_dracutmodules+=" cryptsetup "
systemd-cryptsetup is called by the crypt module
There is also a bluetooth module.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 302 |
Nodes: | 16 (2 / 14) |
Uptime: | 100:52:32 |
Calls: | 6,767 |
Calls today: | 5 |
Files: | 12,295 |
Messages: | 5,376,432 |
Posted today: | 1 |