From: Hendrik Visage <hvisage@envisage.co.za>
To: gentoo-dev@cvs.gentoo.org
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] MOSIX and kernel 2.4.6
Date: Sun Jul 22 18:01:02 2001 [thread overview]
Message-ID: <20010723020031.B27728@hvs.envisage.co.za> (raw)
In-Reply-To: <20010722151839.A15188@chronic.unixabuse.org>; from jb3insf@chronic.unixabuse.org on Sun, Jul 22, 2001 at 03:18:39PM -0700
On Sun, Jul 22, 2001 at 03:18:39PM -0700, jb3insf@chronic.unixabuse.org wrote:
> Hello,
> I today I tried to upgarde to kernel 2.4.6 from portage/sys-kernel/linux-sources. It stops immediatly saying it cannot get MOSIX-1.0.5.I am doing a fresh install with build.10_rc5.Is there a way to fix this?.
Fetch MOSIX-1.0.5 yourself.
But Caveat Emptor: -rc5's 2.4.6 is flaky as far as I can see.
Module support is broken based on some _mmx_* calls thats somehow
either not mangled, or mangled wrongly.
Advice:
Install build-rc5 with a 2.4.4 kernel (I think I did a 2.4.4-r something),
and after that (Except if you need it the extra extentions) fetch
linux-2.4.6 yourself & do a manual installation.
(That's what I did, and yes, it's not "ebuild"/portage safe, but it works :)
Hendrik
a.k.a. hevisko
> Thanks
> Jake
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
--
------------------------
Hendrik Visage
hvisage@envisage.co.za
next prev parent reply other threads:[~2001-07-23 0:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-22 16:14 [gentoo-dev] MOSIX and kernel 2.4.6 jb3insf
2001-07-22 18:01 ` Hendrik Visage [this message]
2001-07-22 23:01 ` Daniel Robbins
2001-07-23 1:02 ` Hendrik Visage
-- strict thread matches above, loose matches on Subject: below --
2001-07-23 7:07 Sean Mitchell
2001-07-23 7:28 ` Jerry A!
2001-07-23 7:34 ` Hendrik Visage
2001-07-23 7:35 Sean Mitchell
2001-07-23 8:03 ` Jerry A!
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=20010723020031.B27728@hvs.envisage.co.za \
--to=hvisage@envisage.co.za \
--cc=gentoo-dev@cvs.gentoo.org \
--cc=gentoo-dev@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