From: "Gregg C Levine" <obiwanthejediknight@worldnet.att.net>
To: sample junk <gumnam777@yahoo.com>, linux-8086@vger.kernel.org
Subject: Re: Help needed reg LDT
Date: Wed, 9 Apr 2003 22:06:14 -0400 [thread overview]
Message-ID: <000801c2ff05$c4bdfd20$51a3580c@who5> (raw)
In-Reply-To: 20030409162235.64286.qmail@web41807.mail.yahoo.com
Hello from Gregg C Levine
How about your choice of lists? This list is for the ELKS project. You want
the actual kernel list, or a Usenet Linux group. Try one of those.
Gregg C Levine obiwanthejediknight@att.net
<This signature will be replaced, pending an approval from the Jedi Council.
>
----- Original Message -----
From: "sample junk" <gumnam777@yahoo.com>
To: <linux-8086@vger.kernel.org>
Sent: Wednesday, April 09, 2003 12:22 PM
Subject: Help needed reg LDT
> Hi all,
> I am trying to implement per process LDT for
> linux-2.4.20 on IA-32. During booting the kernel
> does'nt get past the invocation of /sbin/init.
> I have made the following changes for my
> implementation
> 1) Have added segment descriptors for User code and
> data in the newly created segment in the function
> "copy_segments".
> 2)changed the __USER_CS and USER_DS to point into the
> new descriptors created above.
>
> Could anyone suggest where i had gone wrong??
>
> TIA
> gum
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
> http://platinum.yahoo.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2003-04-10 2:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 16:22 Help needed reg LDT sample junk
2003-04-10 2:06 ` Gregg C Levine [this message]
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='000801c2ff05$c4bdfd20$51a3580c@who5' \
--to=obiwanthejediknight@worldnet.att.net \
--cc=gumnam777@yahoo.com \
--cc=linux-8086@vger.kernel.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