On 2013-08-31 7:32 AM, Alon Bar-Lev <alo...@gentoo.org> wrote:
If this is not mainline, and it is not trivial gentoo kernels
maintainer patch, and you must have this as static, you can just put
the patch within/etc/portage/patches/sys-kernel/gentoo-sources/, so
it will patch your kernel every time you emerge new one.
Interesting, but this would require manually updating the patch every
time, right?
Or could the 'patch' be configured to automatically pull the right
version (compatible with the kernel being installed) every time? That
would not be such a bad thing... but if not... well...
Computers excel at automating things. People excel at breaking things,
and I'd like this to be automated as much as possible.
That said, I've never applied patches in this manner, so, is there an up
to date how-to on how to do this? It might be something I can get
comfortable with unless/until an automated process is implemented.
On 2013-08-31 8:19 AM, Joerg Schilling wrote:
> So there seems to be no real need to create a static linux kernel
> with ZFS inside.
<sigh>
There is for those who *do not want modules enabled on their servers*.
Why is it so hard for some people to just not get that their way is not
the only way.
Again, Joerg... please *stop arguing* about this point, it has *nothing*
to do with the thread.
On 2013-08-31 2:44 PM, Mark David Dumlao <madum...@gmail.com> wrote:
You must have missed the point that this is for *servers*, that
most people *disable modules* on. I*know* that it is available as a
module.
Ok, I was just asking. But as for what "most people" do on their
servers, speak for yourself.
Ok, I left out two words: '... I know ... ' - and the fact is, most
everyone I know (over a dozen) who runs linux servers (not just gentoo)
runs them with modules disabled, and I've seen countless others say the
same thing over the years...
The fact is, *many* people do this, and if it trivial to implement it in
gentoo (which appears it is), then why not do so?
