<div dir="auto">David Spencer (aka idlemoor & 55020) created a SlackBuild a few years ago (geez, 6.5 years ago) to build kernels, calling his project dusk (Dave's Unofficial Slackbuilt Kernels). It was envisioned to be set up in a cron job and for it to automatically build new kernels point releases as they were released by <a href="http://kernel.org">kernel.org</a>, but the script can be ran by itself too.<div dir="auto"><br></div><div dir="auto">The script might be of interest to some.<br><div dir="auto"><br></div><div dir="auto"><a href="https://gitlab.com/idlemoor/dusk">https://gitlab.com/idlemoor/dusk</a><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 7, 2023, 10:10 PM David Chmelik <<a href="mailto:davidnchmelik@gmail.com" target="_blank" rel="noreferrer">davidnchmelik@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I like the idea because sometime after/in Linux kernel v2, documentation <br>
on how to build a kernel disappeared from the main site or from The <br>
Linux Documentation Project (TLDP) and/or was outdated. For a while <br>
there was no documentation or only informal/partial documentation, not <br>
always very good. Sometime by v4 there was documentation elsewhere but <br>
I don't know that it's official... I don't recall if there is any <br>
official documentation anymore or if it's back in TLDP, so I'd just like <br>
to see how it's done again. In the days of v2 I build kernels maybe <br>
200+ times trying to get a Matrox display/video card to work with dual <br>
monitors (as separate terminals) to no avail. I'd just like to see how <br>
it's done again and if we can be assured the SlackBuild does it right, <br>
that'd be something nice to see...<br>
<br>
On 6/7/23 6:48 PM, Julian Grinblat wrote:<br>
> I was wondering if a slackbuild for packaging the linux kernel is <br>
> something that would be accepted into SlackBuilds, or if people would <br>
> be interested in it to begin with.<br>
> I put together a small script for building and packaging the kernel <br>
> for personal use, here: <br>
> <a href="https://github.com/perrin4869/linux-kernel-slackbuild" rel="noreferrer noreferrer noreferrer" target="_blank">https://github.com/perrin4869/linux-kernel-slackbuild</a> <br>
> <<a href="https://github.com/perrin4869/linux-kernel-slackbuild" rel="noreferrer noreferrer noreferrer" target="_blank">https://github.com/perrin4869/linux-kernel-slackbuild</a>><br>
> The goal is to be able to install and remove and test kernels easily. <br>
> The repo follows the SlackBuild.org guidelines for the most part.<br>
> If this would be acceptable, is there anything that should be fixed?<br>
<br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org" rel="noreferrer noreferrer" target="_blank">SlackBuilds-users@slackbuilds.org</a><br>
<a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="https://slackbuilds.org/faq/" rel="noreferrer noreferrer noreferrer" target="_blank">https://slackbuilds.org/faq/</a><br>
<br>
</blockquote></div>