From: Andi Kleen <andi@firstfloor.org>
To: linux-kernel@vger.kernel.org
Subject: Re: A SuSE riddle
Date: Mon, 05 Jan 2009 21:55:05 +0100 [thread overview]
Message-ID: <874p0do4ly.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20090105185225.GH6165@tatooine.rebelbase.local> (markus reichelt's message of "Mon, 05 Jan 2009 19:52:25 +0100")
markus reichelt <ml@mareichelt.de> writes:
> this goes out to the SusE folks in here:
>
> What the heck is needed to get one's hands on the contents of
>
> kernel-source-2.6.27.7-9.1.i586.rpm
Since 11.0 SUSE uses LZMA enabled rpm, so you need rpm or rpm2cpio
versions that support that.
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2009-01-05 20:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 18:52 A SuSE riddle markus reichelt
2009-01-05 19:02 ` Bruce Ferrell
2009-01-05 19:46 ` markus reichelt
2009-01-05 19:49 ` Steven Noonan
2009-01-05 19:56 ` markus reichelt
2009-01-05 22:08 ` Bruce Ferrell
2009-01-05 20:05 ` Martin Tessun
2009-01-05 20:55 ` Andi Kleen [this message]
2009-01-06 1:46 ` Jiri Kosina
[not found] <fa.l0z6gwkTJUh2Q17O/6u2VzAQKlg@ifi.uio.no>
2009-01-05 19:41 ` Sitsofe Wheeler
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=874p0do4ly.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.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