public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stef Epardaud <stef@epardaud.net>
To: "Michael B. Trausch" <mike@trausch.us>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] Ubuntu GG 2.6.22 (Was: Re: Filesystem silent crash with EXT3)
Date: Wed, 12 Sep 2007 16:12:07 +0200	[thread overview]
Message-ID: <20070912141206.GA24461@inforealm.org> (raw)
In-Reply-To: <46E7EF35.5000002@trausch.us>

On Wed, Sep 12, 2007 at 09:52:53AM -0400, Michael B. Trausch wrote:
> (I am cc:ing the list so that this person does not get several multiple
> replies.  Also, I am making the assumption, Stef, that you are not
> running a vanilla kernel that you built yourself from the kernel sources
> and that you are running the Ubuntu stock kernel.)

You're right.

> Please go to #ubuntu+1 on irc.freenode.net for issues with your Ubuntu
> Gutsy Gibbon prerelease system.  For starters, the kernel that comes
> with Ubuntu is not the vanilla Linux kernel, it has patches and added
> and removed things to it---like nearly all distribution kernels.

Sorry, I did not realise there was a more appropriate place. It won't
happen again :)

> Secondly, the Gutsy Gibbon is not yet released for public consumption.
> It is in a prerelease state, and as such, if you're running it, and you
> encounter issues, please file bugs with Ubuntu
> (http://www.launchpad.net/), where they will be far more receptive to
> such information.  However, they will not directly support you---you
> chose to run a prerelease system; they'll tell you that if it breaks
> your system you get to keep all the pieces.  Once the Gibbon is
> released, though, you can use it with the backing of the regular Ubuntu
> community and it will be supported.
> That having been said, you may not want to run prerelease software that
> is known to be unstable if you don't have the time (or the ability) to
> troubleshoot and file a detailed bug report during the prerelease state.

It's not so much that I am complaining, I didn't ask anyone to help me
recover my data either. I just wanted to see if there was something I
could do to find an eventual problem, so that it could be fixed.

Thanks for your pointers though.
-- 
Stéphane Epardaud

  reply	other threads:[~2007-09-12 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 12:02 Filesystem silent crash with EXT3 Stef Epardaud
2007-09-12 13:03 ` Jan Kara
2007-09-12 13:52 ` [OT] Ubuntu GG 2.6.22 (Was: Re: Filesystem silent crash with EXT3) Michael B. Trausch
2007-09-12 14:12   ` Stef Epardaud [this message]
2007-09-12 13:53 ` Filesystem silent crash with EXT3 Krzysztof Halasa
2007-09-12 14:16   ` [Resolved: bad RAM] " Stef Epardaud
2007-09-13  9:15     ` Helge Hafting

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=20070912141206.GA24461@inforealm.org \
    --to=stef@epardaud.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@trausch.us \
    /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