mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: markus reichelt <ml@mareichelt.de>
To: linux-kernel@vger.kernel.org
Subject: Re: A SuSE riddle
Date: Mon, 05 Jan 2009 20:56:13 +0100	[thread overview]
Message-ID: <20090105195613.GL6165@tatooine.rebelbase.local> (raw)
In-Reply-To: <f488382f0901051149r1d164f23uf7d876fa6c7017a2@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 975 bytes --]

* Steven Noonan <steven@uplinklabs.net> wrote:

> On Mon, Jan 5, 2009 at 11:46 AM, markus reichelt <ml@mareichelt.de>
> >> wrote: 2.) Because CAB files are for windows silly trid :)
> >
> > A .CAB wouldn't need a .src.CAB, a .CAB would just frakking work
> > :)
> >
> 
> I don't think .CAB has ever been a standard distribution system for
> any Linux, BSD, or UNIX operating system. I can understand the need
> for a .tar.gz or .tar.bz2, but .cab?

Sarcasm. Sorry, collateral damage.


> And you can grab such .tar.{gz,bz2} files from here:
> http://www.kernel.org/pub/linux/kernel/v2.6/

No, SuSE once again broke with their patched kernel a tool, and we
are trying to get our hands on the borked patched sources so we can
diff the borked kernel to the working vanilla kernel in order to help
the sorry SuSE user left hanging midair by SuSE folks.

I signed the petition "Meteor Strikes To SuSE FIRST!" - Did you? ;-)

-- 
left blank, right bald

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2009-01-05 19:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 18:52 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 [this message]
2009-01-05 22:08     ` Bruce Ferrell
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=20090105195613.GL6165@tatooine.rebelbase.local \
    --to=ml@mareichelt.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

all inboxes | Powered by JetHome®