From: Bruce Ferrell <bferrell@baywinds.org>
To: linux-kernel@vger.kernel.org
Subject: Re: A SuSE riddle
Date: Mon, 05 Jan 2009 14:08:07 -0800 [thread overview]
Message-ID: <496284C7.20803@baywinds.org> (raw)
In-Reply-To: <20090105194624.GJ6165@tatooine.rebelbase.local>
markus reichelt wrote:
> * Bruce Ferrell <bferrell@baywinds.org> wrote:
>
>> markus reichelt wrote:
>>> Hi,
>>>
>>> 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
>>>
>>> The usual tools fail.
>>>
>>> Downloaded from
>>> http://ftp.uni-bayreuth.de/linux/opensuse/distribution/11.1/repo/oss/suse/i586/
>>>
>>>
>>> And why not provide a .CAB for it? Seems to work better anyway.
>>>
>> 1.) Try kernel-source-2.6.27.7-9.1.src.rpm instead
>
> Oh well, SuSE. Placing their eggs in different places...
Not exactly. i586.rpm is for 586 and up code just as i386.rpm is for
386 and up. src.rpm is for source code. you asked for the
kernel-source... source code so it fits the rpm scheme of things.
And the folks here are right. This belongs on the Suse lists.
My apologies all
>> 2.) Because CAB files are for windows silly trid :)
>
> A .CAB wouldn't need a .src.CAB, a .CAB would just frakking work :)
>
next prev parent reply other threads:[~2009-01-05 22:17 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 [this message]
2009-01-05 20:05 ` Martin Tessun
2009-01-05 20:55 ` Andi Kleen
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=496284C7.20803@baywinds.org \
--to=bferrell@baywinds.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