From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Kernel 2.6.22-rc3 safe to migrate to?
Date: Sat, 2 Jun 2007 18:27:05 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0706021826470.4161@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.0.99.0706022253130.16496@sheep.housecafe.de>
Jun 2 18:23:23 p34 upsd[2225]: Can't connect to UPS [belkin]
(newhidups-auto): No such file or directory
Jun 2 18:24:23 p34 upsmon[2228]: Poll UPS [belkin@localhost] failed -
Driver not connected
Hmm, something changes with USB in 2.6.22-rc3 form 2.6.21..
On Sat, 2 Jun 2007, Christian Kujau wrote:
> On Sat, 2 Jun 2007, Justin Piszcz wrote:
>> Wondering as their were a lot of XFS related issues early on in
>> development..? The 2.6.22-rc3 kernel has the core 2 duo coretemp patch by
>> ruik which I want be running as long as 2.6.22-rc3 does not have any severe
>> XFS issues?
>
> Tracking -rc and running 2.6.22-rc3 for a couple of days now, no problems
> with xfs since this infamous 2.6.17 thingy[0]. But that's pretty useless
> information I guess, since your setup will be different from mine. Did you
> have anything "special" in mind when asking this?
>
> C.
>
> [0] http://oss.sgi.com/projects/xfs/faq.html#dir2
> --
> BOFH excuse #339:
>
> manager in the cable duct
>
>
next prev parent reply other threads:[~2007-06-02 22:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 21:24 Justin Piszcz
2007-06-02 21:59 ` Christian Kujau
2007-06-02 22:09 ` Justin Piszcz
2007-06-02 22:27 ` Justin Piszcz [this message]
2007-06-02 22:54 ` Jeremy Fitzhardinge
2007-06-02 22:55 ` Justin Piszcz
2007-06-03 0:25 ` Christian Kujau
2007-06-03 0:27 ` Justin Piszcz
2007-06-03 6:30 ` Jeremy Fitzhardinge
[not found] ` <6bffcb0e0706030059o3e53e647uf3ae1aa3f16609d8@mail.gmail.com>
2007-06-03 8:02 ` Jeremy Fitzhardinge
2007-06-03 8:41 ` Justin Piszcz
[not found] <fa.eE9c0s9eXX/aO2N8hiu3e2Yehz8@ifi.uio.no>
[not found] ` <fa.hq4JzIoUe01l8ywIZPkqjocRBmc@ifi.uio.no>
[not found] ` <fa.3aN+T/xQVA3sf9DdMPLOfUVmYA0@ifi.uio.no>
[not found] ` <fa.mJ71j4nyi6ALIkQjLcpIJtTbVVI@ifi.uio.no>
[not found] ` <fa.vxJKq726YMWJY2i/waKQsNec3aU@ifi.uio.no>
2007-06-03 6:23 ` Robert Hancock
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=Pine.LNX.4.64.0706021826470.4161@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=xfs@oss.sgi.com \
/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®