On Wed, Jan 05, 2022 at 05:36:56PM -0800, Adam Williamson wrote:
> So, my question is...do other Rawhide users have this problem, or is my
> system an outlier for some reason? I have not been able to figure out
> *what* created the problematic directories on my system. An earlier
> systemd rc may have created /boot/efi/(machine_id) if
> /boot/efi/loader/entries existed, but I don't know what might have
> created /boot/efi/loader/entries . I'm pretty sure I didn't do it
> myself, though.

  My rawhide system seem to have both and boot even other kernel:

tree /boot/efi
/boot/efi
├── 6a1b72cbb94d4c95a4ac9df2d581e371
│   ├── 0-rescue
│   │   ├── initrd
│   │   └── linux
│   ├── 4.16.0-0.rc5.git2.1.fc29.x86_64
│   ├── 4.16.0-0.rc6.git2.1.fc29.x86_64
│   ├── 4.16.0-0.rc7.git1.1.fc29.x86_64
│   └── 5.16.0-0.rc5.20211216git2b14864acbaa.37.fc36.x86_64
│       ├── initrd
│       └── linux
├── EFI
│   ├── BOOT
│   │   ├── BOOTX64.EFI
│   │   └── fbx64.efi
│   └── fedora
│       ├── BOOTX64.CSV
│       ├── grub.cfg
│       ├── grub.cfg.rpmsave
│       ├── grubenv.rpmsave
│       ├── grubx64.efi
│       ├── mmx64.efi
│       ├── shim.efi
│       └── shimx64.efi
└── loader
    └── entries
            └──
            
6a1b72cbb94d4c95a4ac9df2d581e371-5.16.0-0.rc5.20211216git2b14864acbaa.37.fc36.x86_64.conf

# uname -r
5.16.0-0.rc4.20211207gitcd8c917a56f2.30.fc36.x86_64


-- 
Tomasz Torcz                                                       72->|   80->|
to...@pipebreaker.pl                                               72->|   80->|
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to