From: "Riley Williams" <Riley@Williams.Name>
To: Raghavan <raghavan.viswanathan@wipro.com>
Cc: Linux-8086@Vger.Kernel.Org
Subject: Re: *A* Version of ELKS
Date: Tue, 15 Jul 2003 09:04:49 +0100 [thread overview]
Message-ID: <BKEGKPICNAKILKJKMHCACEDCEOAA.Riley@Williams.Name> (raw)
In-Reply-To: <003a01c34a85$d0e1a360$8c06770a@wipro.com>
Hi.
> I have been unsuccessful in trying to build a ELKS 1.1 Images from
> Sources... I am finding it hard to debug it ... :-((
> I had no success with 1.0 sources either ...
>
> I am wondering , if somebody has like *A SET** of
> (a) Dev
> (b) elkscmd
> (c) elks
> (d) elksnet
>
> which can all compile (hopefully without too much of work) and
> generate a Working Image.
I do my compiling under Red Hat Linux 6.2 and dev86-0.15.0-2.i386.rpm
is installed here. I synchronise with the ELKS CVS archive, so I have
the ELKS kernel source as it exists in the current CVS tree here, and
likewise elkscmd and elksnet although I haven't looked at those two
recently. Certainly the ELKS kernel compiles without problems here.
I will add that the current elkscmd and elksnet sources require the
dev sources to be installed in a specific directory. I'm working on
relaxing this requirement, but that work is far from complete.
> I don't care if it Old or new ..all I need is a Working Image file
> 'generated' from **SOME** sources. That will enable me to start
> off on learning about this Cool thingie ...
If it's not fairly recent - ELKS 0.1.2 or 0.1.3-pre1 preferably - then
you'd be wasting your time as there were quite a lot of major changes
just prior to the 0.1.0 beta release.
> As a suggestion to the guy who is putting up the sources of ELKS
> on the Web server, I feel along with the sources of elks and elkscmd
> on the Download Page, it might be a good Idea to say which version
> of Dev sources were used to generate the Image ( putting the Dev tar
> ball along would be even better !!) This will give completeness to
> the Version controlling.
The primary sources are those in the CVS archive, so if you have that
set up, you will be able to keep track of what is happening. Download
and install cvs and some version of ssh, then choose where you want the
ELKS sources installed, and make that the current directory. When you
have done that, type the following commands from the bash prompt...
CVSROOT=:pserver:anonymous@cvs.elks.sf.net:/cvsroot/elks
CVS_RSH=`which ssh`
export CVSROOT CVS_RSH
cvs get elks elkscmd elksnet elksutils
...and you will have the latest set of ELKS sources.
Best wishes from Riley.
---
* Nothing as pretty as a smile, nothing as ugly as a frown.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.500 / Virus Database: 298 - Release Date: 10-Jul-2003
next prev parent reply other threads:[~2003-07-15 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 4:01 *A* Version of ELKS Raghavan
2003-07-15 8:04 ` Riley Williams [this message]
2003-07-16 8:47 ` Raghavan
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=BKEGKPICNAKILKJKMHCACEDCEOAA.Riley@Williams.Name \
--to=riley@williams.name \
--cc=Linux-8086@Vger.Kernel.Org \
--cc=raghavan.viswanathan@wipro.com \
/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