All of lore.kernel.org
 help / color / mirror / Atom feed
From: "La Monte H.P. Yarroll" <piggy@timesys.com>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: timesysgpl-developers@lists.sourceforge.net
Subject: [uml-devel] ANNOUNCE: SKAS patch for SuSE 8.2 (linux-2.4.20.SuSE) available
Date: Mon, 15 Dec 2003 07:50:29 -0500	[thread overview]
Message-ID: <3FDDAE15.6020409@timesys.com> (raw)

I have put a revised version of skas-2.4.21.patch.bz2 on the TimeSysGPL 
site at SourceForge:

https://sourceforge.net/tracker/index.php?func=detail&aid=860308&group_id=89531&atid=590444

This was built against  kernel-source-2.4.20.SuSE-100.i586.rpm.

The .config I used for my kernel is here:

https://sourceforge.net/tracker/index.php?func=detail&aid=860309&group_id=89531&atid=590444

Why a SuSE-specific version of the patch?  The kernel for SuSE 8.2 
already includes an earlier version of the SKAS patch, so the patch from 
Jeff does not apply cleanly.

Warning: even with this patch I have trouble using gdb.  It fails to 
identify the threads as they are created and frequently jumps from 
function to function with no discernable rationale--not unlike an 
undecected source/object mismatch.




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

                 reply	other threads:[~2003-12-15 12:50 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=3FDDAE15.6020409@timesys.com \
    --to=piggy@timesys.com \
    --cc=timesysgpl-developers@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.