[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a874c3bd-94b4-2e22-2263-7a2eacbfdb17@riseup.net>
Date: Thu, 14 Nov 2019 16:43:00 +0000
From: Patrick Schleizer <adrelanos@...eup.net>
To: lkrg-users@...ts.openwall.com
Subject: Re: module loading / systemd bug report / suggestion /
my Debian packaging rationale
To your last e-mail in this thread: awesome!
Debian packaging status update:
The /debian folder is ready. I've successfully created a deb package on
my local machine. Managed figuring out using DKMS.
The source code for that can be found here:
https://github.com/Whonix/lkrg
Instructions how to build the deb package from source code will come
soonish. (Standard Debian methods / commands would do but this isn't
trivial to research.) Binary packages will come soonish too.
Also started describing the Debian packaging for of LKRG here:
https://www.whonix.org/wiki/Linux_Kernel_Runtime_Guard_LKRG
As for the default loglevel:
I don't see why the loglevel should be set through either /etc/sysctl.d
and/or a systemd unit file to loglevel 3 when running "make install" or
when using the Debian package. In case of the Debian package, that
"seems" like me downstream making that decision.
Since you're upstream, it's perfectly fine to decide "default loglevel
3" in the source code? Then users could lower it using sysctl easily.
then there wouldn't be need for the systemd unit file to set it to
loglevel 3. (As the LKRG progresses, you might want to change the
default hardcoded in the source code, which is fine too.)
(I don't argue against user's possibility to change loglevels through
sysctl / /etc/sysctl.d. That's a great feature.)
Kind regards,
Patrick
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
