[gentoo-user] cryptsetup close and device in use when it is not
Howdy, As some may recall, I use external drives as backups. They are encrypted and I use cryptsetup to open and close them. Open works fine but close gives me trouble at times. It doesn't always do this but it does it more often than not. It's getting annoying. Drive one. It's a 6TB drive and when it gave this error a few minutes ago, I restarted udev-trigger to correct it. When I try to close it, it says it is in use. But restarting udev-trigger reset it so I could close it. Drive two, when I tried to close it, it gives me this: root@fireball / # cryptsetup close 8tb Device 8tb is still in use. root@fireball / # mount | grep 8tb root@fireball / # As you can tell, it is not mounted. When I mount, I do it manually from a fstab entry. I just do mount /mnt/8tb and it mounts it. I use umount to unmount it. Old school but it works. Thing is, for some reason it shows it is in use even tho it is not mounted. Even restarting udev-trigger didn't work this time. I can't figure out what is doing it exactly and think it is something besides cryptsetup having a problem. I'm actually thinking udev for this reason. I do my backups while I'm updating the OS. When I do my updates, all my firefox profiles are closed and I'm not downloading new files. So that is when I do my backups. Last time it did this, I went to boot runlevel and restarted udev itself. That reset it so I could close the drive and cut it off. Thing is, I'd like a proper fix for this or a good sound way to reset it without having to do all that. Sometimes all I need is to logout and back in after updates. Restarting udev and such shouldn't be required. If it matters, both drives are in identical enclosures and use the same cable and power source. One is a SMR and the other a CMR. One is 6TB and one is 8TB. Both are encrypted the same way. Both use eSATA, not USB. I used USB before and it may have been the enclosure but it ruined drives. I could never depend on it so I switched to eSATA. So, anyone else run into this and have a solution for it? Do I have something set up wrong or is this a bug in some package somewhere? I've googled and seen where others have the problem but their solutions don't seem to work and most are very old posts. Need some ideas and thoughts here. Thanks. Dale :-) :-) P. S. I took some meds so I hope the above makes sense. The meds are working well right now but I need to close the drive so I can put it back in the safe. :/
Re: [gentoo-user] Re: Exact setting in grub to default to a kernel by name?
On Mon, Jun 14, 2021 at 12:20:44AM +0100, Neil Bothwick wrote
> On Sun, 13 Jun 2021 18:57:49 -0400, Walter Dnes wrote:
>
> /etc/default/grub is only used when you call grub-mkconfig.
>
> > 1) Is "insmod extfs3" necessary? I've built extfs3 into the kernels.
>
> If the kernel is on an ext3 filesystem, yes. This is GRUB's module, it
> uses it to read an ext3 filesystem in order to load the kernel.
Some confusion here. "fdisk -l" on my new machine gives...
Device StartEndSectors Size Type
/dev/sda12048 526335 524288 256M EFI System
/dev/sda2 526336 1886416303 1885889968 899.3G Linux filesystem
/dev/sda3 1886418352 1953523119 6710476832G Linux filesystem
The EFI Systen partition is fat32. The web examples I read show
"insmod " matching the filesystem of the linux system being
booted. But all entries in grub.cfg on my new machine are "insmod fat".
I wonder if the web documentation was referring to BIOS-booting machines.
grub.cfg would be sitting on an xfs or extfs3 or whatever file system,
and would need to read it off that filesystem.
I have a UEFI system which demands a fat32 boot partition. Since grub
and the kernels are sitting on a fat32 partition, my machine needs
"insmod fat".
Things that make you go h...
* you need to put "insmod fat" in grub.cfg to tell grub that the kernels
are sitting on a fat32 partition
* but grub has to first read grub.cfg on the fat32 partition before it
knows that it must read a fat32 partition
I wonder if this is due to the verbose automagic configuration. I
also noticed that all menuentries on my machine contain "insmod gzio
and "insmod part_gpt", so I'm including them here. Here is my proposed
grub.cfg. If anybody sees any problems, please let me know. Otherwise,
I'll try the following tomorrow on the new machine...
set timeout_style=menu
set timeout=15
insmod vga
set gfxpayload=640x480
insmod gzio
insmod part_gpt
insmod fat
set root='hd0,gpt1'
menuentry 'Linux Experimental' --class gnu-linux {
linux /vmlinuz-experimental root=/dev/sda2 ro noexec=on
net.ifnames=0 intel_pstate=disable ipv6.disable=1
}
menuentry 'Linux Experimental Recovery' --class gnu-linux {
linux /vmlinuz-experimental root=/dev/sda2 ro
}
menuentry 'Linux Production' --class gnu-linux {
linux /vmlinuz-production root=/dev/sda2 ro noexec=on net.ifnames=0
intel_pstate=disable ipv6.disable=1
}
menuentry 'Linux Production Recovery' --class gnu-linux {
linux /vmlinuz-production root=/dev/sda2 ro
}
--
Walter Dnes
I don't run "desktop environments"; I run useful applications
[gentoo-user] Re: Exact setting in grub to default to a kernel by name?
On 2021-06-13, Walter Dnes wrote:
> On Sun, Jun 13, 2021 at 05:38:53PM -, Grant Edwards wrote
>> On 2021-06-13, Walter Dnes wrote:
>>
>> > I'd be tempted to do a manual gub.cfg if I had documentation.
>>
>> I gave up on the grub2 auto-magical config system many years ago. My
>> grub.cfg is typically 10-20 lines long. The documentation is at
>>
>> https://www.gnu.org/software/grub/manual/grub/grub.html
>>
>> For manual confiuration: see section 6:
>>
>>
>> https://www.gnu.org/software/grub/manual/grub/html_node/Configuration.html#Configuration
>
> When experimenting with this, I'll backup grub.cfg. If things go
> awry, boot with the USB key I used for the install, and copy back the
> old known working grub.cfg. I've done a first crack at this. I assume
> that nothing in /etc/default/grub will have any effect. Questions...
>
> 1) Is "insmod extfs3" necessary? I've built extfs3 into the kernels.
I've never used it it, and my boot partitions are always ext3/4
> 2) I assume that the the first "menuentry" will be the default boot?
Unless you set the `default` variable to something other than 0
> 3) Is the default timeout still 5 seconds?
Dunny, I always set 'timeout=10'
> 3) I assume that 640x480 is supported on just about every monitor
>out there. I want as large text as possible. My eyes are
>getting old... just like me. Any obvious errors in the following
>grub.cfg?
>
>=
> menuentry 'Linux Experimental' --class gnu-linux {
> set gfxpayload=640x480
> insmod ext3fs
> set root='hd0,gpt1'
> linux /vmlinuz-experimental root=/dev/sda2 ro noexec=on
> net.ifnames=0 intel_pstate=disable ipv6.disable=1
> }
I don't know if you really need the gfxpayload or the insmod lines, I don't
recall ever needing those to boot kernels from ext3/4 partitions.
All my grub.cfg files looks like this:
timeout=10
root=hd0,1
default=0
menuentry 'vmlinuz-5.10.27-gentoo' {
linux /boot/vmlinuz-5.10.27-gentoo root=/dev/sda1
}
menuentry 'vmlinuz-5.4.97-gentoo' {
linux /boot/vmlinuz-5.4.97-gentoo root=/dev/sda1
}
> Something that occured to me. Can I move the duplicated lines to the
> top of the file and take them out of the menuentries? E.g.
Yes.
Re: [gentoo-user] Re: Exact setting in grub to default to a kernel by name?
On Sun, 13 Jun 2021 18:57:49 -0400, Walter Dnes wrote: > When experimenting with this, I'll backup grub.cfg. If things go > awry, boot with the USB key I used for the install, and copy back the > old known working grub.cfg. I've done a first crack at this. I assume > that nothing in /etc/default/grub will have any effect. Questions... /etc/default/grub is only used when you call grub-mkconfig. > 1) Is "insmod extfs3" necessary? I've built extfs3 into the kernels. If the kernel is on an ext3 filesystem, yes. This is GRUB's module, it uses it to read an ext3 filesystem in order to load the kernel. > 2) I assume that the the first "menuentry" will be the default boot? Yes, you'll see default=0 in the first part of grub.cfg. > 3) Is the default timeout still 5 seconds? Not sure on that one, but look at grub.cfg. > 3) I assume that 640x480 is supported on just about every monitor > out there. I want as large text as possible. My eyes are getting > old... just like me. My eyes are better than they were 40 years ago but don't ask about my hearing, or if you must, do it loudly... -- Neil Bothwick Documentation: (n.) a novel sold with software, designed to entertain the operator during episodes of bugs or glitches. pgp_fXOqbnpCs.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Re: Exact setting in grub to default to a kernel by name?
On Sun, Jun 13, 2021 at 05:38:53PM -, Grant Edwards wrote
> On 2021-06-13, Walter Dnes wrote:
>
> > I'd be tempted to do a manual gub.cfg if I had documentation.
>
> I gave up on the grub2 auto-magical config system many years ago. My
> grub.cfg is typically 10-20 lines long. The documentation is at
>
> https://www.gnu.org/software/grub/manual/grub/grub.html
>
> For manual confiuration: see section 6:
>
>
> https://www.gnu.org/software/grub/manual/grub/html_node/Configuration.html#Configuration
When experimenting with this, I'll backup grub.cfg. If things go
awry, boot with the USB key I used for the install, and copy back the
old known working grub.cfg. I've done a first crack at this. I assume
that nothing in /etc/default/grub will have any effect. Questions...
1) Is "insmod extfs3" necessary? I've built extfs3 into the kernels.
2) I assume that the the first "menuentry" will be the default boot?
3) Is the default timeout still 5 seconds?
3) I assume that 640x480 is supported on just about every monitor
out there. I want as large text as possible. My eyes are getting
old... just like me. Any obvious errors in the following grub.cfg?
=
menuentry 'Linux Experimental' --class gnu-linux {
set gfxpayload=640x480
insmod ext3fs
set root='hd0,gpt1'
linux /vmlinuz-experimental root=/dev/sda2 ro noexec=on
net.ifnames=0 intel_pstate=disable ipv6.disable=1
}
menuentry 'Linux Experimental Recovery' --class gnu-linux {
set gfxpayload=640x480
insmod ext3fs
set root='hd0,gpt1'
linux /vmlinuz-experimental root=/dev/sda2 ro
}
menuentry 'Linux Production' --class gnu-linux {
set gfxpayload=640x480
insmod ext3fs
set root='hd0,gpt1'
linux /vmlinuz-production root=/dev/sda2 ro noexec=on net.ifnames=0
intel_pstate=disable ipv6.disable=1
}
menuentry 'Linux Production Recovery' --class gnu-linux {
set gfxpayload=640x480
insmod ext3fs
set root='hd0,gpt1'
linux /vmlinuz-production root=/dev/sda2 ro
}
=
Something that occured to me. Can I move the duplicated lines to the
top of the file and take them out of the menuentries? E.g.
=
set gfxpayload=640x480
insmod ext3fs
set root='hd0,gpt1'
menuentry 'Linux Experimental' --class gnu-linux {
linux /vmlinuz-experimental root=/dev/sda2 ro noexec=on
net.ifnames=0 intel_pstate=disable ipv6.disable=1
}
menuentry 'Linux Experimental Recovery' --class gnu-linux {
linux /vmlinuz-experimental root=/dev/sda2 ro
}
menuentry 'Linux Production' --class gnu-linux {
linux /vmlinuz-production root=/dev/sda2 ro noexec=on net.ifnames=0
intel_pstate=disable ipv6.disable=1
}
menuentry 'Linux Production Recovery' --class gnu-linux {
linux /vmlinuz-production root=/dev/sda2 ro
}
=
--
Walter Dnes
I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] Exact setting in grub to default to a kernel by name?
On Sun, Jun 13, 2021 at 04:09:58PM -0400, Philip Webb wrote > > Or the OP could use Lilo, the simplest boot manager of all. On a UEFI-only desktop PC? -- Walter Dnes I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] Exact setting in grub to default to a kernel by name?
210613 Neil Bothwick wrote: > Isn't this a new laptop? If so, why torment yourself with GRUB when you > have UEFI available to you? The only real justification for using GRUB in > such a situation is that you are completely familiar with it and don't > want to learn something else. But if you have to learn something, you may > as well learn the 2/3 line configs of systemd-boot. > Note that systemd-boot doesn't require systemd, it's just the gummiboot > boot manager that was merged into systemd taken out again. Or you could > use rEFInd if you prefer a prettier boot menu. Or the OP could use Lilo, the simplest boot manager of all. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] Exact setting in grub to default to a kernel by name?
On Sunday, 13 June 2021 19:05:29 BST Neil Bothwick wrote: > On Sun, 13 Jun 2021 09:33:57 -0400, Walter Dnes wrote: > > On Sun, Jun 13, 2021 at 06:46:15AM +0200, Hund wrote > > > > > >Let me rephrase the question more generally... given a > > > >kernel "/boot/vmlinuz-fubar" how and where do I specify it by name as > > > >the default boot kernel? > > > > > > What about this? > > > > > > https://www.stephenrlang.com/2017/06/setting-default-kernel-in-grub2/ > > > > > Is /boot/grub/grub.cfg the file that actually controls bootup, and is > > > > all 154 lines of verbosity really necessary? For menu entries I see... > > Not necessary, but does no harm either. The first 90% of the file is > automated setup, which you can replace with hard coded entries or just > leave it to its own devices. The only part you need to think about is the > menuentry sections. > > > I'd be tempted to do a manual gub.cfg if I had documentation. > > GRUB has extensive documentation. it's not the best written but every > configuration option is described. > > Isn't this a new laptop? If so, why torment yourself with GRUB when you > have UEFI available to you? The only real justification for using GRUB in > such a situation is that you are completely familiar with it and don't > want to learn something else. But if you have to learn something, you may > as well learn the 2/3 line configs of systemd-boot. > > Note that systemd-boot doesn't require systemd, it's just the gummiboot > boot manager that was merged into systemd taken out again. Or you could > use rEFInd if you prefer a prettier boot menu. I do like rEFInd, feels AppleMac-like. :-) However, I have abandoned all boot managers these days on UEFI MoBos and just use the native UEFI firmware to boot with.[1] It's simpler, lighter and faster. However, I don't boot into different OS/kernels unless I have to and when I do I have to use the UEFI menu GUI to switch OS/kernels, so this won't suit all use cases. This approach requires to enable the 'EFI boot stub' option in the kernel, so that the UEFI firmware can recognise and load the kernel directly as an EFI executable.[2] Then it is a matter of using the efibootmgr on the CLI to set up my boot menu labels and OS/kernel order.[3] [1] https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/ Bootloader#Alternative_2:_efibootmgr [2] https://wiki.gentoo.org/wiki/EFI_Stub [3] https://wiki.gentoo.org/wiki/Efibootmgr signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Exact setting in grub to default to a kernel by name?
On Sun, 13 Jun 2021 09:33:57 -0400, Walter Dnes wrote: > On Sun, Jun 13, 2021 at 06:46:15AM +0200, Hund wrote > > >Let me rephrase the question more generally... given a > > >kernel "/boot/vmlinuz-fubar" how and where do I specify it by name as > > >the default boot kernel? > > > > What about this? > > > > https://www.stephenrlang.com/2017/06/setting-default-kernel-in-grub2/ > > > > Is /boot/grub/grub.cfg the file that actually controls bootup, and is > all 154 lines of verbosity really necessary? For menu entries I see... Not necessary, but does no harm either. The first 90% of the file is automated setup, which you can replace with hard coded entries or just leave it to its own devices. The only part you need to think about is the menuentry sections. > I'd be tempted to do a manual gub.cfg if I had documentation. GRUB has extensive documentation. it's not the best written but every configuration option is described. Isn't this a new laptop? If so, why torment yourself with GRUB when you have UEFI available to you? The only real justification for using GRUB in such a situation is that you are completely familiar with it and don't want to learn something else. But if you have to learn something, you may as well learn the 2/3 line configs of systemd-boot. Note that systemd-boot doesn't require systemd, it's just the gummiboot boot manager that was merged into systemd taken out again. Or you could use rEFInd if you prefer a prettier boot menu. -- Neil Bothwick Mouse: (n.) an input device used by management to force computer users to keep at least a part of their desks clean. pgpPxJzM0hjsF.pgp Description: OpenPGP digital signature
[gentoo-user] Re: Exact setting in grub to default to a kernel by name?
On 2021-06-13, Walter Dnes wrote: > I'd be tempted to do a manual gub.cfg if I had documentation. I gave up on the grub2 auto-magical config system many years ago. My grub.cfg is typically 10-20 lines long. The documentation is at https://www.gnu.org/software/grub/manual/grub/grub.html For manual confiuration: see section 6: https://www.gnu.org/software/grub/manual/grub/html_node/Configuration.html#Configuration
Re: [gentoo-user] Building package "dev-texlive/texlive-basic-2021" failed
On Sunday, 13 June 2021 18:10:46 BST Dr Rainer Woitok wrote: > Michael, > > On Sunday, 2021-06-13 16:16:37 +0100, you wrote: > > ... > > $ grep -i en_gb /usr/share/i18n/SUPPORTED > > en_GB.UTF-8 UTF-8 > > en_GB ISO-8859-1 > > Same here. It would/should be the same with mine. Have you made sure: en_GB.UTF-8 UTF-8 is in your /etc/locale.gen and have you run locale-gen thereafter? > > ... > > $ eselect locale list > > > > Available targets for the LANG variable: > > [1] C > > [2] C.utf8 > > [3] POSIX > > > > [snip ... ] > > > > [7] en_GB > > [8] en_GB.iso88591 > > [9] en_GB.utf8 > > [10] en_US > > [11] en_US.iso88591 > > [12] en_US.utf8 > > [13] en_GB.UTF-8 * > > [ ] (free form) > > Now it's becoming really mysterious, right from the local horse's mouth: > >$ eselect locale list >Available targets for the LANG variable: > [1] C > [2] C.utf8 > [3] POSIX > [4] en_GB.utf8 * > [ ] (free form) > > So allegedly my only "available target" for English is the not (or no > longer) working "en_GB.utf8". Being slightly flabbergasted would be a > huge understatement ... :-/ > > Sincerely, > Rainer Yes, this looks odd, but I have not worked out how locale is sourced in detail. Have you added: LANG="en_GB.UTF-8" in your /etc/env.d/02locale for a system wide setting? signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Building package "dev-texlive/texlive-basic-2021" failed
Michael, On Sunday, 2021-06-13 16:16:37 +0100, you wrote: > ... > $ grep -i en_gb /usr/share/i18n/SUPPORTED > en_GB.UTF-8 UTF-8 > en_GB ISO-8859-1 Same here. > ... > $ eselect locale list > Available targets for the LANG variable: > [1] C > [2] C.utf8 > [3] POSIX > [snip ... ] > [7] en_GB > [8] en_GB.iso88591 > [9] en_GB.utf8 > [10] en_US > [11] en_US.iso88591 > [12] en_US.utf8 > [13] en_GB.UTF-8 * > [ ] (free form) Now it's becoming really mysterious, right from the local horse's mouth: $ eselect locale list Available targets for the LANG variable: [1] C [2] C.utf8 [3] POSIX [4] en_GB.utf8 * [ ] (free form) So allegedly my only "available target" for English is the not (or no longer) working "en_GB.utf8". Being slightly flabbergasted would be a huge understatement ... :-/ Sincerely, Rainer
Re: [gentoo-user] Building package "dev-texlive/texlive-basic-2021" failed
On Sunday, 13 June 2021 15:11:18 BST Dr Rainer Woitok wrote: > All, > > On Sunday, 2021-06-13 15:39:46 +0200, I myself wrote: > > ... > > > > > > $ sudo locale > > > > LANG=en_GB.utf8 > > > > ... > > > > Erm, is there a difference between "*.utf8" and "*.UTF-8"? Does case > > matter? > > Apparently yes. At least for Perl or anything else used by Portage. > Running my package upgrade script again after setting > >$ export LANG=en_GB.UTF-8 > > just succeeded. "As soon as you're doing it right, it just works". :-) > But what exactly is the difference? > > Sincerely, > Rainer If you have a look at the comments in /etc/locale.gen it explains where to find suitable notation for locale name, charset, and it also provides a default list of supported combinations: /usr/share/i18n/SUPPORTED In there we find: $ grep -i en_gb /usr/share/i18n/SUPPORTED en_GB.UTF-8 UTF-8 en_GB ISO-8859-1 I recall in the past having had a similar problem and as you say, once you set it up correctly it just works. :-) I don't know what the difference is between lower/upper case notation for the charset, but having set it up in capitals seems to work here. Note, I don't have any lower case charset in / etc/locale.gen. $ eselect locale list Available targets for the LANG variable: [1] C [2] C.utf8 [3] POSIX [snip ... ] [7] en_GB [8] en_GB.iso88591 [9] en_GB.utf8 [10] en_US [11] en_US.iso88591 [12] en_US.utf8 [13] en_GB.UTF-8 * [ ] (free form) signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Building package "dev-texlive/texlive-basic-2021" failed
All, On Sunday, 2021-06-13 15:39:46 +0200, I myself wrote: > ... > > > $ sudo locale > > > LANG=en_GB.utf8 > > > ... > Erm, is there a difference between "*.utf8" and "*.UTF-8"? Does case > matter? Apparently yes. At least for Perl or anything else used by Portage. Running my package upgrade script again after setting $ export LANG=en_GB.UTF-8 just succeeded. "As soon as you're doing it right, it just works". :-) But what exactly is the difference? Sincerely, Rainer
Re: [gentoo-user] Building package "dev-texlive/texlive-basic-2021" failed
Michael, On Saturday, 2021-06-12 16:29:12 +0100, you wrote: > ... > > $ sudo locale > > LANG=en_GB.utf8 > > ... > I can't speak for your lua* packages, but as long as you have defined your > locale correctly in /etc/locale.gen your system should source what it needs > from there. Erm, is there a difference between "*.utf8" and "*.UTF-8"? Does case matter? The web page https://wiki.gentoo.org/wiki/UTF-8 provides a mix of both notations, but I get $ grep -v '^#' /etc/locale.gen en_GB.UTF-8 UTF-8 $ So do I have to adapt my definition of "LANG"? > Regarding perl complaining, there was a perl update recently (stable) so > running perl-cleaner is recommended and may fix at least your texlive-basic > issue. I installed Perl version 5.32.1 two weeks ago during my last routine up- grade, so this might be a reason as well. And running "perl-cleaner" returned this: $ perl-cleaner --all --pretend * Would try to remove the following perl-core packages from world file *emerge --deselect perl-core/File-Temp * Would try to update installed Perl virtuals *emerge -u1 virtual/perl-Carp virtual/perl-Compress-Raw-Zlib virtual/perl-CPAN-Meta virtual/perl-CPAN-Meta-YAML virtual/perl-Data-Dumper virtual/perl-Digest virtual/perl-Digest-MD5 virtual/perl-Digest-SHA virtual/perl-Encode virtual/perl-Exporter virtual/perl-ExtUtils-CBuilder virtual/perl-ExtUtils-Install virtual/perl-ExtUtils-MakeMaker virtual/perl-ExtUtils-Manifest virtual/perl-ExtUtils-ParseXS virtual/perl-File-Path virtual/perl-File-Spec virtual/perl-File-Temp virtual/perl-Getopt-Long virtual/perl-IO virtual/perl-JSON-PP virtual/perl-libnet virtual/perl-MIME-Base64 virtual/perl-Module-Metadata virtual/perl-parent virtual/perl-Parse-CPAN-Meta virtual/perl-Perl-OSType virtual/perl-Pod-Parser virtual/perl-podlators virtual/perl-Scalar-List-Utils virtual/perl-Storable virtual/perl-Sys-Syslog virtual/perl-Test-Harness virtual/perl-Test-Simple virtual/perl-Text-ParseWords virtual/perl-Time-Local virtual/perl-version virtual/perl-XSLoader * Locating packages for an update * Locating ebuilds linked against libperl * No package needs to be reinstalled. $ As far as I can see all these virtual packages are installed and updated to the most recent stable version. But nevertheless I will try that, too. By the way, "man perl-cleaner" starts with DESCRIPTION perl-cleaner -- Find & rebuild packages and Perl header files broken due to a perl upgrade Is this what they call "inspiring confidence"? :-) Is there a reason why "perl-cleaner" should be run manually rather than automatically after emerging any Perl component? Should I put it into my "edepclean" script which I normally run after a successful upgrade? Sincerely, Rainer
Re: [gentoo-user] Exact setting in grub to default to a kernel by name?
On Sun, Jun 13, 2021 at 06:46:15AM +0200, Hund wrote
> >Let me rephrase the question more generally... given a
> >kernel "/boot/vmlinuz-fubar" how and where do I specify it by name as
> >the default boot kernel?
>
> What about this?
>
> https://www.stephenrlang.com/2017/06/setting-default-kernel-in-grub2/
Is /boot/grub/grub.cfg the file that actually controls bootup, and is
all 154 lines of verbosity really necessary? For menu entries I see...
=
menuentry 'Gentoo GNU/Linux, with Linux production' --class blah blah
blah {
blah blah blah
set root='hd0,gpt1'
linux /vmlinuz-production root=/dev/sda2 ro noexec=on net.ifnames=0
intel_pstate=disable ipv6.disable=1
}
menuentry 'Gentoo GNU/Linux, with Linux production (recovery mode)'
--class blah blah blah {
blah blah blah
set root='hd0,gpt1'
linux /vmlinuz-production root=/dev/sda2 ro single
}
menuentry 'Gentoo GNU/Linux, with Linux experimental' --class blah blah
blah {
blah blah blah
set root='hd0,gpt1'
linux /vmlinuz-experimental root=/dev/sda2 ro noexec=on net.ifnames=0
intel_pstate=disable ipv6.disable=1
}
menuentry 'Gentoo GNU/Linux, with Linux experimental (recovery mode)'
--class blah blah blah {
blah blah blah
set root='hd0,gpt1'
linux /vmlinuz-experimental root=/dev/sda2 ro single
}
=
I'd be tempted to do a manual gub.cfg if I had documentation.
--
Walter Dnes
I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] Exact setting in grub to default to a kernel by name?
On Sun, 13 Jun 2021 09:21:36 +0100, Neil Bothwick wrote: > The default setting takes either the number of title of a kernel, so > default="experimental kernel" should do it. Forgot the obligatory RTFM reference :) https://www.gnu.org/software/grub/manual/grub/grub.html#default -- Neil Bothwick After all is said and done let there not be more said than done. pgpcGURGY0yxa.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Exact setting in grub to default to a kernel by name?
On Sun, 13 Jun 2021 00:07:27 -0400, Walter Dnes wrote: > I have multiple (would you believe 2?) kernels in /boot. > > [x8940][waltdnes][~] ll /boot/vm* > -rwxr-xr-x 1 root root 7046848 Jun 12 23:46 /boot/vmlinuz-experimental > -rwxr-xr-x 1 root root 6986624 Jun 12 16:55 /boot/vmlinuz-production > > The grub kernel listing at bootup is > > - production kernel > - production kernel recovery mode > - experimental kernel > - experimental kernel recovery mode > > The default is the first entry, i.e. "GRUB_DEFAULT=0" in > /etc/default/grub. I prefer going with "experimental". If I screw up > the config to the point where it can't boot, then I'll manually override > to "production". The simple way of getting the third entry as default > is "GRUB_DEFAULT=2" (remember to count from zero). > > This works for now. But what happens if/when I add more kernels for > whatever reason? Let me rephrase the question more generally... given a > kernel "/boot/vmlinuz-fubar" how and where do I specify it by name as > the default boot kernel? > The default setting takes either the number of title of a kernel, so default="experimental kernel" should do it. -- Neil Bothwick A Smith & Wesson beats Four Aces everytime. pgpyzmCiCiVrV.pgp Description: OpenPGP digital signature
