linux-kernel - Re: [Lf_driver_backport] scripts in compat tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAB=NE6X7ptSxB8aDW9boYqWDgTKpc8HuyJhN2UtHnW1CffVQbQ@mail.gmail.com>
Date:	Mon, 21 May 2012 06:40:05 -0700
From:	"Luis R. Rodriguez" <mcgrof@...jolero.org>
To:	Ozan Çağlayan <ozancag@...il.com>
Cc:	linux-kernel@...r.kernel.org, Andy Whitcroft <apw@...onical.com>,
	lf_driver_backport@...ts.linux-foundation.org,
	linux-wireless@...r.kernel.org, linux-bluetooth@...r.kernel.org
Subject: Re: [Lf_driver_backport] scripts in compat tree

On Mon, May 21, 2012 at 6:15 AM, Ozan Çağlayan <ozancag@...il.com> wrote:
>> Well kernel.org does not have already built kernels. Ubuntu's PPA
>> kernels *are* vanilla kernels, in fact that is why they were put up,
>> they are guaranteed to be built on vanilla kernels. We couldn't get a
>> more generic approach then. The only thing though is -- the PPA
>> kernels obviously have the kernels integrated on .debs. There are a
>> few options here:
>>
>>  1) If Ubuntu can dpkg -x the kernels for us onto tarballs that'd be swell
>>  2) We could write our own script to do this with C code that does
>> the dpkg -x for us
>>
>> There are ways to do 2) suggested in the thread above.
>
> ah you are right, we need to have built kernels in order to build the
> modules. Well then the 2nd solution seems reasonable if we can mimic
> dpkg -x. I googled a bit and people says that debs are generic .ar
> archives so it would be easy to take the tarball inside of them.
>
> If I succeed this can be used on any distro since that they are
> vanilla without any patches. But if the PPA disappears one day, we'll
> have to find another solution :)

Indeed :) the PPA must not seize to exist! Or something.

> BTW you also download the kernel images probably for booting into them
> to test the compat builds. Booting using those images on other
> distributions can be messy and unsuccessful as initramfs and booting
> mechanisms differ widely. I'll test those too.

Yeap... indeed. Mandrake for example loves to compress their modules.
compat-wireless handles the initramfs I think well, so *if* you do
want to address that, you could look at how we address initramfs
there, but I frankly don't think having this option available for all
distributions is a requirement. It'd be nice, but I think it'd be
nicer if ckmake itself could run for all options without root
privileges. So for example right now ckmake does require privileges to
install the debs, it'd be nicer if instead we just unload the kernels
to a $USER/ dir somewhere that ckmake has rights to under the user
calling it. In this case I'd be willing to remove the option to even
boot into these kernels.

 Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/