Hi,

i wrote:
> > it is quite some hurdle that some of the tests need to be run as
> > superuser.

Glenn Washburn wrote:
> Yes, not ideal. I have spent an embarrassing amount of time developing
> scripts that do away with with root requirement, and it works. The way
> they are able to run the root required tests as an unprivileged user is
> by compiling a user mode linux kernel and running the tests in the UML
> process. Would you be interested in trying out these scripts?

Yes, if you can describe the necessary activities for a dummy who sends
a mail twice because a completely unrelated mail caused protests by
the mail provider.
(I stopped myself from sending a third mail with an apology.)


> > I wonder what happened to the fixes for the file leaks of
> > grub_cmd_cryptomount which we discussed in
> >   https://lists.gnu.org/archive/html/grub-devel/2024-09/msg00222.html

> I meant to send a v2, but hadn't gotten around to it. It is now sent and
> now that the security patches are out, hopefully Daniel will be able to
> get to them soon.

I will try to remember what we discussed and how these topics reflect
in patch v2.


(I will also have to revisit my patch from last summer which was meant
to make error messages visible in the tests.
When testing it, i ran into the grub_cmd_cryptomount leaks.

The patch is archived as
  [PATCH 0/2] grub-fstest: Show error message if command causes grub_errno
  https://lists.gnu.org/archive/html/grub-devel/2024-06/msg00197.html
of which the first motivating paragraph of the cover letter was eaten by
git send-email and later added by
  https://lists.gnu.org/archive/html/grub-devel/2024-06/msg00201.html

Especially i will have to compare it with your recent patch set
  [PATCH v6 0/6] More ls improvements
  https://lists.gnu.org/archive/html/grub-devel/2025-03/msg00012.html
and check whether our patch sets overlap.
)


Have a nice day :)

Thomas


_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

Reply via email to