public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Tessun <martin.tessun@die-tessuns.de>
To: linux-kernel@vger.kernel.org
Subject: Re: A SuSE riddle
Date: Mon, 05 Jan 2009 21:05:34 +0100	[thread overview]
Message-ID: <4962680E.1030306@die-tessuns.de> (raw)
In-Reply-To: <20090105185225.GH6165@tatooine.rebelbase.local>

markus reichelt schrieb:
> 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.
> 

I don't see your problem:

S | Name          | Typ   | Version      | Arch   | Repository
--+---------------+-------+--------------+--------+-----------------------
i | kernel-source | Paket | 2.6.27.7-9.1 | x86_64 | Haupt-Repository (OSS)
v | kernel-source | Paket | 2.6.27.7-9.1 | i586   | Haupt-Repository (OSS)

12 | repo_1                           | Haupt-Repository (OSS)
       | Ja        | Ja            | 99        | yast2  |
http://download.opensuse.org/distribution/11.1/repo/oss/       |


So there are the kenels for both Architectures available.

Regards,
Martin

BTW.: I think zypper *is* the standard-tool for SuSE-Updates and you
should go to the SuSE-Kernel-Mailing-List with that problem.

  parent reply	other threads:[~2009-01-05 20:14 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 [this message]
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=4962680E.1030306@die-tessuns.de \
    --to=martin.tessun@die-tessuns.de \
    --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