public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Josh Boyer <jwboyer@gmail.com>,
	Randy Dunlap <rdunlap@xenotime.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.2-rc1
Date: Tue, 22 Nov 2011 18:05:20 +0000	[thread overview]
Message-ID: <20111122180520.2c0c3e0f@pyx> (raw)
In-Reply-To: <4ECAFDAD.5040801@panasas.com>

> My god that totally-brain-dead Fedora Kernel rpm generation.

It's designed to produce kernel packages for distribution. It is indeed
useless for much else.

> 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

That's what the upstream make rpm tries to achieve. If it's not working
right on Fedora then we should fix it to work around any Fedora brokenness

> 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)

Fedora is now getting so weird and dependant on magic initrds it's become
pretty unusable for kernel development work nowdays IMHO because it's
undebuggable.

However "make rpm" from the Linus tree is meant to be as far as possible
generic.

Alan

  parent reply	other threads:[~2011-11-22 18:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08  2:10 Linux 3.2-rc1 Linus Torvalds
2011-11-08  3:12 ` Al Viro
2011-11-08  4:26   ` Linus Torvalds
2011-11-08 10:52     ` Geert Uytterhoeven
2011-11-08  6:50 ` Nicholas A. Bellinger
2011-11-08 13:43 ` Udo Steinberg
2011-11-08 14:47   ` Ming Lei
2011-11-08 22:10     ` Rafael J. Wysocki
2011-11-08 14:53 ` Alessandro Suardi
2011-11-08 20:13   ` Linus Torvalds
2011-11-08 20:15     ` Matthew Garrett
2011-11-08 20:44     ` Linus Torvalds
2011-11-08 14:55 ` Nick Bowler
2011-11-08 20:23   ` Linus Torvalds
2011-11-09  7:40     ` Takashi Iwai
2011-11-09 12:03       ` Wu Fengguang
2011-11-10 11:57       ` Wu Fengguang
2011-11-08 19:06 ` Thomas Bächler
2011-11-08 23:00 ` Steven Rostedt
2011-11-08 23:53   ` Linus Torvalds
2011-11-09  8:09   ` Borislav Petkov
2011-11-09 13:11   ` Valdis.Kletnieks
2011-11-09 14:20 ` Paul Rolland
2011-11-09 23:23   ` Linus Torvalds
2011-11-09 17:18 ` Randy Dunlap
2011-11-09 17:28   ` Josh Boyer
2011-11-22  1:41     ` Boaz Harrosh
2011-11-22 16:10       ` Josh Boyer
2011-11-22 18:05       ` Alan Cox [this message]
2011-11-22 18:29         ` Boaz Harrosh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111122180520.2c0c3e0f@pyx \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=bharrosh@panasas.com \
    --cc=jwboyer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox