*A* Version of ELKS

*A* Version of ELKS

[Raghavan]

Folks,

I have been unsuccesful 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 dont 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 ...

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.

Thanks for the Help.

Bye,
Raghavan V

Re: *A* Version of ELKS

[Riley Williams]

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

Re: *A* Version of ELKS

[Raghavan]

Riley ,

Thanks a Ton for the Information.
It has really got me going...

I had to fix a couple of make files in elkscmd to make em use the $(CFLAGS)
variable or else they would not find some include files (e.g. in.h)  under
linuxmt of the elks.

A few problems I am facing .....

(1) When I am compiling the elksnet , it is unable to link to the select
system call.
make[1]: Entering directory `/home/rags/ELKS/elksnet/ktcp'
bcc  -o ktcp ktcp.o slip.o ip.o icmp.o tcp.o tcp_cb.o tcp_output.o timer.o
tcpdev.o netconf.o vjhc.o
undefined symbol: _select

BTW, getting the 'screen' directory to compile might be just too much for me
2 handle. I felt that I don't need it. So I am NOT compiling it. Tricked the
Top level make file by renaming the Makefile in screen directory to
Makefile.bak.

(2) In the elkscmd compilation, I have a few more to go.


init.c
====
make[2]: Entering directory `/home/rags/ELKS/elkscmd/sys_utils'
bcc -0 -O -ansi  "-DELKS_VERSION=\"0.1.3-pre1\"" -s init.c -o init -H 2000
undefined symbol: _setsid

inet utils
=====
make[3]: Entering directory `/home/rags/ELKS/elkscmd/inet/nettools'
bcc -s netstat.o -o netstat
undefined symbol: _socket
undefined symbol: _connect
undefined symbol: _bind

This is coming up for all of em under inet.

I suspect the elkscmd compilations are unable to lookout for Network
Libraries manfactured in the elks ...
I tried some simple hacking ..copying the net.a as libnet.a and linking it
over ...Did not help...

Has anybody seen these ..?

I am not in a 'giving up' kinda state ..Getting a working elks kernel
certainly looks do-able now :-))


Bye,
Rags



----- Original Message -----
From: "Riley Williams" <Riley@Williams.Name>
To: "Raghavan" <raghavan.viswanathan@wipro.com>
Cc: <Linux-8086@vger.kernel.org>
Sent: Tuesday, July 15, 2003 1:34 PM
Subject: Re: *A* Version of ELKS


> 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
>
> -
> 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