linux-kernel - Re: Linux 3.2-rc1

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+5PVA7a2GgX_FVWTnQtV5VXK1x9UhqLHSzqZHaibcGH+8a+NA@mail.gmail.com>
Date:	Tue, 22 Nov 2011 11:10:00 -0500
From:	Josh Boyer <jwboyer@...il.com>
To:	Boaz Harrosh <bharrosh@...asas.com>
Cc:	Randy Dunlap <rdunlap@...otime.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 3.2-rc1

On Mon, Nov 21, 2011 at 8:41 PM, Boaz Harrosh <bharrosh@...asas.com> wrote:
> On 11/09/2011 09:28 AM, Josh Boyer wrote:
>>
>> Fedora uses those.  We also used the -gitX snapshot patches when they
>> were generated, but now we do that by hand (which we also did for the
>> -rcX patches while kernel.org was down.)
>>
>> josh
>
> My god that totally-brain-dead Fedora Kernel rpm generation.
>
> RANT a head should be skipped!!
>
> I wish there was a strait forward way to point to a Kernel
> git tree HEAD and say "make rpm", which is simply the tar
> of the "make modules_install" and the "make install" output
> + a simple script to manipulate grub.conf

I'm actually thinking about creating an exploded source Fedora git
tree.  I just haven't gotten around to it yet because it's not exactly
straight-forward.

> Not today's Fedora-Kernel git tree which is not a Linux
> git tree at all but those patches above + stable.
> Any simple tree moments needs to involve black patch magic
> and fear of hell. (Don't try this at home)

There's a wiki page on building your own Fedora kernel.  It's really
not that complicated.

> Actually the "grub-selector" should have been it's own
> rpm. And each Kernel can/should be it's own independent
> (none conflicting, right) package. I know, I know, it tries
> to be that, but it is not. For example I want a low-latency
> rt Kernel as a side choice for any Kernel, and so on...

Fedora has no interest in the kernels it isn't building, so we're not
really going to split things out separately like that because it
serves us no purpose.

> Throw away that monstrous  Fedora-Kernel-tree. There is
> only one Kernel tree it is called Linux. You can do your
> own back/forward port branches based on stable to your
> heart's content with out inventing a new totally different
> patches tree.

The git tree you're looking at is for the buildsystem to create RPMs.
That requires a spec file, tarballs, and patches.  It can't build from
exploded source (at least not easily), so you're comparing apples to
oranges somewhat.

Anyway, if/when I get an exploded source git tree created for Fedora,
I'll post about it to the Fedora kernel list.

josh
--
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/