From: Lynn Kerby <lfk@kerbit.net>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] host-skas3a-RH8.patch
Date: Thu, 4 Sep 2003 15:05:52 -0700 [thread overview]
Message-ID: <20030904220551.GC2192@haman.kerbit.net> (raw)
In-Reply-To: <200309041536.h84Fa3f8013683@uml.karaya.com>; from jdike@addtoit.com on Thu, Sep 04, 2003 at 08:36:03 -0700
On 2003.09.04 08:36 Jeff Dike wrote:
>There have been a number of requests for skas patches for RH kernels. Since
>I did skas3 for RH8 a while ago, I have that lying around, and got around
>to releasing it.
>
>It's basically the same as the current skas3 patch, except for a fix which
>allows a !CONFIG_PROC_MM kernel to build, hence the 'a' in the name.
>
>Get it at the usual place.
>
> Jeff
Thanks Jeff.
Have you looked into making the patch apply to 2.4.20 or later kernels from RH?
It seems that the copy_segments() function is deprecated in the newer kernels
and I'm not quite adventurous enough to try eliminating the copy_segments()/
mm_copy_segments() portions of the skas3 patch. It looks like the Alan Cox
patches for 2.4.20-22 also include the elimination of copy_segments.
Is everyone that is running current stable kernels on the host just using the
base code?
--
Lynn Kerby <mailto:lfk@kerbit.net>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2003-09-04 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 15:36 [uml-devel] host-skas3a-RH8.patch Jeff Dike
2003-09-04 22:05 ` Lynn Kerby [this message]
2003-09-05 20:12 ` Jeff Dike
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=20030904220551.GC2192@haman.kerbit.net \
--to=lfk@kerbit.net \
--cc=user-mode-linux-devel@lists.sourceforge.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