All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Goembel <phil-goembel@wi.rr.com>
To: Linux ELKS <Linux-8086@vger.kernel.org>
Subject: ELKS Development/FAQ Questions
Date: 30 Jul 2003 19:33:57 -0500	[thread overview]
Message-ID: <1059611636.15148.3084.camel@castle> (raw)
In-Reply-To: <BKEGKPICNAKILKJKMHCAKEHPFAAA.Riley@Williams.Name>

[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]

Ok. I'd like to help with the ELKS website, and with the 
documentation.

But my main interest is to help with development of the ELKS
code.

I have virtually no experience with the Linux development
environment, but I do have experience in cross-development
for embedded microprocessor systems (in DOS and Win32
environments)

I am trying to follow the FAQ in setting up the environment
so that I can compile the ELKS kernel, but have almost
immediately run into a problem.

The FAQ is telling me to install the Dev86 package in the
root (/) directory. I don't want to do this, and I see no 
reason that I should have to.

I would much rather do all of my cross development in
my home directory, with my standard user privileges, not
root privileges. I feel this would be much safer, especially
since I already have some tools installed that have the same
name as the Dev86 tools. I don't know where they came from,
and I'd rather not clobber them.

Is it possible to set up everything in ~/? If so, how
is it done? What reasons are there for me NOT to do it that 
way? If I can't set up everything in ~/, please explain why?

I will gladly update the ELKS FAQ with any answers you can 
give me.

Respectfully,
Phil

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-07-31  0:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 19:58 Web language codes Riley Williams
2003-07-31  0:33 ` Phil Goembel [this message]
2003-07-31  6:01   ` ELKS Development/FAQ Questions Riley Williams
2003-07-31  9:56     ` Raghavan
2003-07-31 21:30       ` Phil Goembel
2003-07-31 21:41         ` Paul Nasrat
2003-08-01 14:19       ` Phil Goembel
2003-08-01 14:05     ` Phil Goembel
2003-08-01 22:42       ` Riley Williams

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=1059611636.15148.3084.camel@castle \
    --to=phil-goembel@wi.rr.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 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.