On Sun 01 Mar 2020 at 18:11:07 (+0100), Mikhail Morfikov wrote:
> On 01/03/2020 17:15, mick crane wrote:
> > On 2020-02-29 18:17, Mikhail Morfikov wrote
> >
> >> vmlinuz -> boot/vmlinuz-5.4.0-4-amd64
> >> lrwxrwxrwx 1 root root 24 2020-02-24 00:37:53
> >> vmlinuz.old ->
Mikhail Morfikov wrote:
...
> Also, I'm trying to configure refind EFI boot manager, and basically I do=
> n't
> want to change its config file with each kernel update (the numbers in th=
> e file
> names change).
that's exactly what i've been doing. they work fine no
matter where they end up
Brian composed on 2020-03-01 16:10 (UTC):
> On Sun 01 Mar 2020 at 08:41:09 -0500, Felix Miata wrote:
>> Grub does not like symlinks to un-versioned kernel and initrd in /boot/.
> I am probably missing your point but I have just booted successfully
> with:
> root='hd1,msdos5'
> linux
On 01/03/2020 17:15, mick crane wrote:
> On 2020-02-29 18:17, Mikhail Morfikov wrote
>
>> vmlinuz -> boot/vmlinuz-5.4.0-4-amd64
>> lrwxrwxrwx 1 root root 24 2020-02-24 00:37:53
>> vmlinuz.old -> boot/vmlinuz-5.5.4-amd64
>>
>
> .old is pointing to a newer kernel ?
>
> mick
>
On 01/03/2020 16:53, David Wright wrote:
> I've read here that Grub can decrypt LUKS, but currently only v1,
> at least in buster, so no help to you.
Actually grub supports LUKSv2[1], but I haven't tried it yet.
[1]:
On 3/1/20, Brian wrote:
> On Sun 01 Mar 2020 at 08:41:09 -0500, Felix Miata wrote:
>
>>
>> Grub does not like symlinks to un-versioned kernel and initrd in /boot/.
>
> I am probably missing your point but I have just booted successfully
> with:
>
> root='hd1,msdos5'
> linux /vmlinuz.old
On 2020-02-29 18:17, Mikhail Morfikov wrote
vmlinuz -> boot/vmlinuz-5.4.0-4-amd64
lrwxrwxrwx 1 root root 24 2020-02-24 00:37:53
vmlinuz.old -> boot/vmlinuz-5.5.4-amd64
.old is pointing to a newer kernel ?
mick
--
Key ID4BFEBB31
On Sun 01 Mar 2020 at 08:41:09 -0500, Felix Miata wrote:
> Brian composed on 2020-03-01 13:26 (UTC):
>
> > On Sat 29 Feb 2020 at 19:15:12 -0600, David Wright wrote:
>
> >> On Sat 29 Feb 2020 at 19:17:39 (+0100), Mikhail Morfikov wrote:
>
> >>> # ls -al /
> >>> ...
> >>> lrwxrwxrwx 1
On Sun 01 Mar 2020 at 15:09:34 (+0100), Mikhail Morfikov wrote:
> On 01/03/2020 02:15, David Wright wrote:
> > They're a convenience. If you want them kept in /boot, then edit
> > /etc/kernel-img.conf and linux-update-symlinks will recreate them
> > there when the kernel is updated. Ditto if you
On 01/03/2020 02:15, David Wright wrote:
> They're a convenience. If you want them kept in /boot, then edit
> /etc/kernel-img.conf and linux-update-symlinks will recreate them
> there when the kernel is updated. Ditto if you want them removed.
I didn't know there's even such an option. But yes,
Brian composed on 2020-03-01 13:26 (UTC):
> On Sat 29 Feb 2020 at 19:15:12 -0600, David Wright wrote:
>> On Sat 29 Feb 2020 at 19:17:39 (+0100), Mikhail Morfikov wrote:
>>> # ls -al /
>>> ...
>>> lrwxrwxrwx 1 root root 29 2020-02-14 17:22:18 initrd.img ->
>>>
On Sat 29 Feb 2020 at 19:15:12 -0600, David Wright wrote:
> On Sat 29 Feb 2020 at 19:17:39 (+0100), Mikhail Morfikov wrote:
> > I have an encrypted (LUKSv2) LVM setup with a separate unencrypted /boot/
> > partition. When I install a new kenrel in the system, the following
> > symlinks are
> >
On Sat 29 Feb 2020 at 19:17:39 (+0100), Mikhail Morfikov wrote:
> I have an encrypted (LUKSv2) LVM setup with a separate unencrypted /boot/
> partition. When I install a new kenrel in the system, the following symlinks
> are
> created in the root directory (/):
>
> # ls -al /
> ...
>
I have an encrypted (LUKSv2) LVM setup with a separate unencrypted /boot/
partition. When I install a new kenrel in the system, the following symlinks are
created in the root directory (/):
# ls -al /
...
lrwxrwxrwx 1 root root 29 2020-02-14 17:22:18
14 matches
Mail list logo
