public inbox for gentoo-mips@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: gentoo-mips@lists.gentoo.org
Subject: [gentoo-mips] 2.6.9-r4 marked unstable (~mips)
Date: Sat, 27 Nov 2004 07:45:36 -0500	[thread overview]
Message-ID: <41A876F0.8070803@gentoo.org> (raw)


For those users running unstable (ACCEPT_KEYWORDS="~mips"), I've marked 
mips-sources-2.6.9-r4 as unstable.  Those running Indy/Indigo2-class systems, 
be wary, as this specific kernel version didn't stay up too long for me on my 
Indy, but that was a bootcd kernel, and it probably had bugs.  If IP22 users 
get it to run for several days, then it's probably just my end.

IP32, IP30, and Cobalt users should have no problems running this kernel. 
IP30 (Octane) users need to include "ip30" in their USE flags in order for the 
ebuild to apply the Octane patch.  Cobalt users will need to include "cobalt" 
in their USE as well, but the Cobalt profiles should do this already.  When in 
doubt, check your `emerge info` output and see what USE flags are set.

This specific revision also includes several security fixes, including the new 
CAN-2004-0883 (smbfs bug) fix, and a fix for a mips-specific ptrace vuln.

Users running stable setups probably don't want to play with this kernel 
unless they know what they are doing.  </disclaimer>

Questions, comments, flames, and ice cubes welcome as replies to this message 
or on IRC in #gentoo-mips.


--Kumba

-- 
"Such is oft the course of deeds that move the wheels of the world: small 
hands do them because they must, while the eyes of the great are elsewhere." 
--Elrond

--
gentoo-mips@gentoo.org mailing list


                 reply	other threads:[~2004-11-27 12:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41A876F0.8070803@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=gentoo-mips@lists.gentoo.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