From: Paolo Giarrusso <blaisorblade@yahoo.it>
To: "Carl Radford (DC0854-IT)" <CRADFORD@bordersgroupinc.com>,
Laurent@lvivier.info, for@gmx.de, Jeff Dike <jdike@addtoit.com>,
UML-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] Another cause for UML
Date: Thu, 22 Jun 2006 01:16:49 +0200 (CEST) [thread overview]
Message-ID: <20060621231649.25378.qmail@web25225.mail.ukl.yahoo.com> (raw)
In-Reply-To: <CA52872BEA6FD41182A50008C724B23003F2FFD2@corp01uk.bordersgroupinc.com>
"Carl Radford (DC0854-IT)" <CRADFORD@bordersgroupinc.com> ha scritto:
> Any chance I can interest the UML developers
I've included some more address (including Jeff, UML 1st author and
maintainer).
> in fixing UML to
> support openMosix (for the purposes of debugging) ?
> I applied the openMosix patch to a stock kernel (2.6.16) and then
> tried to build a um kernel (yes I should know better :>),
> but there are (obviously) inconsistencies between the would-be-used
> include/arch-i386 header files and the actually-used
> include/um header files (seem to be mostly ptrace/regs stuff).
> For
> someone who knows their way around UML, it should
> be quite trivial to sort the compilation issues (yes I'm
> simplifying, but I'm trying to get you on my side).
> I am not trying to recruit you, from there on it would be up to the
> openMosix development team not to break it again, unless
> you wanted to contribute, of course...... :>).
> Being able to debug the kernel this way would be of great benefit
> to openMosix development and earn UML yet another gold star.
Having helped NTFS (and probably FUSE) to get going is one of the UML
merits, but we likely should advertise this (we know this indirectly,
by having seen those projects' authors using UML for debug).
Start posting some of these errors and we'll look at how trivial it
is (unless the compiler is flooding you). If they look trivial to us
we may try it...
But my 1st question is: does OpenMosix currently support anything
else than x86? If not a little compatibility layer may be needed and
this may hinder significantly the porting - however they'll have to
fix this anyway to support x86_64 at the very least.
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next parent reply other threads:[~2006-06-21 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA52872BEA6FD41182A50008C724B23003F2FFD2@corp01uk.bordersgroupinc.com>
2006-06-21 23:16 ` Paolo Giarrusso [this message]
2006-06-22 21:30 ` [uml-devel] Another cause for UML Jeff Dike
2006-06-23 7:43 Carl Radford (DC0854-IT)
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=20060621231649.25378.qmail@web25225.mail.ukl.yahoo.com \
--to=blaisorblade@yahoo.it \
--cc=CRADFORD@bordersgroupinc.com \
--cc=Laurent@lvivier.info \
--cc=for@gmx.de \
--cc=jdike@addtoit.com \
--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