From: Paul Moore <paul@paul-moore.com>
To: Anurag Aggarwal <anurag19aggarwal@gmail.com>
Cc: Linux-audit@redhat.com, audit@vger.kernel.org
Subject: Re: Help with setting up Auditd kernel repository
Date: Mon, 20 Mar 2023 11:50:23 -0400 [thread overview]
Message-ID: <CAHC9VhSBbvE0GuLbrWmCgQyJc0KY_-MYrXYG08SjMp_7QYJnpg@mail.gmail.com> (raw)
In-Reply-To: <CAPoNrturZV58xESCvCOg5PQbHkf0reJvAbbLJ6-fJa003xxnjw@mail.gmail.com>
On Mon, Mar 20, 2023 at 11:09 AM Anurag Aggarwal
<anurag19aggarwal@gmail.com> wrote:
> >
> > Can you be more specific about the exact repository? There is a
> > repository which contains the development code for the Linux Kernel's
> > audit subsystem, and there is a second repository which contains
> > Steve's audit userspace code (which contains auditd as a component).
> > There is no combined "auditd-kernel" repository.
>
> Yes Paul, the repository that I am talking about is:
> https://github.com/linux-audit/audit-kernel
[NOTE: The upstream Linux Kernel discussion has moved to
audit@vger.kernel.org, CC'd on this email]
Thanks for the clarification.
If you aren't already aware of the Kernel Newbies site, it's a good
resource for getting familiar with the Linux Kernel. There are a
couple of pages which I believe might be helpful here, the first is
the guide on building the Linux Kernel:
* https://kernelnewbies.org/KernelBuild
... the second page is a general landing page which has links to other
kernel related guides and resources:
* https://kernelnewbies.org/KernelHacking
These info on these pages should help you get started but if you have
any additional questions let us know.
--
paul-moore.com
parent reply other threads:[~2023-03-20 16:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAPoNrturZV58xESCvCOg5PQbHkf0reJvAbbLJ6-fJa003xxnjw@mail.gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHC9VhSBbvE0GuLbrWmCgQyJc0KY_-MYrXYG08SjMp_7QYJnpg@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=Linux-audit@redhat.com \
--cc=anurag19aggarwal@gmail.com \
--cc=audit@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).