[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6773AB0F-C197-4465-80D2-3F7DA28EF790@zytor.com>
Date: Thu, 07 Mar 2019 15:40:37 -0800
From: hpa@...or.com
To: Joel Fernandes <joel@...lfernandes.org>,
"Enrico Weigelt, metux IT consult" <lkml@...ux.net>
CC: Greg KH <gregkh@...uxfoundation.org>,
Daniel Colascione <dancol@...gle.com>,
Pavel Machek <pavel@....cz>,
linux-kernel <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>, ast@...nel.org,
atish patra <atishp04@...il.com>,
Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...hat.com>,
Jan Kara <jack@...e.cz>, Jonathan Corbet <corbet@....net>,
Karim Yaghmour <karim.yaghmour@...rsys.com>,
Kees Cook <keescook@...omium.org>, kernel-team@...roid.com,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
Manoj Rao <linux@...ojrajarao.com>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
Randy Dunlap <rdunlap@...radead.org>, rostedt@...dmis.org,
Thomas Gleixner <tglx@...utronix.de>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@...nel.org>,
yhs@...com
Subject: Re: [RFC] Provide in-kernel headers for making it easy to extend the kernel
On March 7, 2019 3:12:07 PM PST, Joel Fernandes <joel@...lfernandes.org> wrote:
>Enrico,
>
>On Thu, Mar 07, 2019 at 11:11:22PM +0100, Enrico Weigelt, metux IT
>consult wrote:
>> On 07.03.19 21:55, Greg KH wrote:
>>
>> > Ick, no, no more squashfs please, let's just kill that mess once
>and for
>> > all :)
>>
>> okay, then: s/squashfs/whatever_fs_image_or_archive_you_like/;
>>
>> > Again, putting this in a simple compressed tar image allows anyone
>to do
>> > whatever they need to with this. If they want a full filesystem,
>> > uncompress it and use it there. If they just want it in-memory
>where
>> > they can uncompress it and then discard it, that works too.
>>
>> And let me stress the point: doesn't need any kernel changes at all,
>> when it's just a file in the same place where the .ko's live.
>
>Yes, but you're missing the point that some people would also opt to
>build it
>into the kernel during their development/debugging (Config=y). For such
>folks, they don't want to update the FS with anything during debug runs
>either. Your "whole same place where the .ko lives" doesn't address
>Daniel's
>usecase. You may say "initrd", but this is a much cleaner solution to
>that
>IMO. There is no initrd needed and the path to the header files will be
>at a
>standard location that is already pre-decided by the kernel.
>
>As Greg said, you are welcome to keep it disabled for yourself if you
>don't
>want it. This doesn't affect anyone else who doesn't use it.
You do know that initrd can be built into the kernel, right?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Powered by blists - more mailing lists