Hi Lennart,
I remember having read some time ago that UKI could pose problems with
early-boot modules provided by vendors and so. But... let's give it a
try! Then, the process should be:
1. Install a version of shim signed with MS keys.
2. Generate the UKI
3. rename the UKI image to grubx64.e
Greetings,
> Sent: Friday, May 26, 2023 at 12:02 PM
> From: "daggs"
> To: "Lennart Poettering"
> Cc: [email protected]
> Subject: Re: [systemd-devel] udev rule, continue to next rule only if preb
> failed
>
> Greetings Lennart,
>
> > Sent: Friday, May 26, 2023 at 11:23 AM
> >
Lennart Poettering writes:
> It actually checks that first:
>
> https://github.com/systemd/systemd/blob/main/src/libsystemd/sd-journal/journal-file.c#L2201
That's what I'm saying: it should have noticed that FIRST and not gotten
to the monotonic time check, but it didn't.
Greetings Lennart,
> Sent: Friday, May 26, 2023 at 11:23 AM
> From: "Lennart Poettering"
> To: "daggs"
> Cc: [email protected]
> Subject: Re: [systemd-devel] udev rule, continue to next rule only if preb
> failed
>
> On Do, 25.05.23 20:25, daggs ([email protected]) wrote:
>
> > Gr
On Do, 25.05.23 14:32, Phillip Susi ([email protected]) wrote:
>
> Lennart Poettering writes:
>
> > We want that within each file all records are strictly ordered by all
> > clocks, so that we can find specific entries via bisection.
>
> Why *all* clocks? Even if you want to search on the monot
On Do, 25.05.23 20:25, daggs ([email protected]) wrote:
> Greetings,
>
> I'm trying to implement the following behavior:
> if a usb is added ot removed, run a script before all other existing rules
> but continue to existing iff the script failed
> I've added the following rule to /etc/udev/rules.d/5
