From: Jeff Dike <jdike@addtoit.com>
To: jeremie le-hen <le-hen_j@epita.fr>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] UML + skas
Date: Mon, 05 Jan 2004 21:58:34 -0500 [thread overview]
Message-ID: <200401060258.i062wYFI023092@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Tue, 30 Dec 2003 19:33:31 +0100." <20031230183331.GB2845@carpediem.epita.fr>
le-hen_j@epita.fr said:
> But it think it would not be very difficult to make some #define
> protection around theses structures to prevent from changing the
> destination of `/usr/src/linux/' to a source without the SKAS patch
> applied.
Maybe, but skas4 doesn't have this problem, and /usr/include/asm should
point to the distro kernel headers, not whatever you have sitting in
/usr/src/linux (and if the distro put a kernel tree there, you should be
building stuff somewhere else).
Of course, this is wrong if there are distros shipping a kernel tree with
the skas patch in it (which maybe SuSE is). In this case, some sort of
protection would be the right thing for skas3.
Jeff
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-01-06 2:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 18:33 [uml-devel] UML + skas jeremie le-hen
2003-12-30 19:08 ` BlaisorBlade
2004-01-06 2:58 ` Jeff Dike [this message]
2004-01-06 4:33 ` attriel
2004-01-06 20:42 ` jeremie le-hen
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=200401060258.i062wYFI023092@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=le-hen_j@epita.fr \
--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