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

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

Stef Epardaud, on 09/12/2007 08:02 AM said:
>
> Hello,
> I am not subscribed to this list, so please CC me on replies.
> I have just suffered from a filesystem crash on my laptop. It's an x86
> running linux 2.6.22 from Ubutu latest gutsy.
>

(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.)

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.

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.
 At any rate, this list is not the place to air your problems with the
Gutsy Gibbon.

	HTH,
	Mike

-- 
Michael B. Trausch               Internet Mail & Jabber: mike@trausch.us
Phone:  (404) 592-5746 x1                         http://www.trausch.us/
Mobile: (678) 522-7934             VoIP: 6453@sip.trausch.us, 861384@fwd
Pidgin 2.1.1 and plugins for Ubuntu Feisty! http://www.trausch.us/pidgin


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  parent reply	other threads:[~2007-09-12 13:53 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 ` Michael B. Trausch [this message]
2007-09-12 14:12   ` [OT] Ubuntu GG 2.6.22 (Was: Re: Filesystem silent crash with EXT3) Stef Epardaud
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=46E7EF35.5000002@trausch.us \
    --to=mike@trausch.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stef@epardaud.net \
    /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