Re: Introduction and proposal:

Re: Introduction and proposal:

[Al Yazdi]

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

>
> I have recently joined this list, and would like to
introduce myself:
> Hi im Erich.
>
Hi Herich and Welcome

>
> One of the things Ive thought would be neat, is a guide to
the source code
> of ELKS, like a programmers manual. Is this something
that is needed? Or
> would my time be better spent working on other documentation?
>

Of course ; and I think all kind of doc. could be usefull.
I'propose myself to help you in this *hard* work.

I can translate too in Frensh some English papers.

Him
Bye

______________________________________________________
Envoyez des messages musicaux sur le portable de vos amis
http://mobile.lycos.fr/mobile/local/sms_musicaux/

______________________________________________________
Boîte aux lettres - Caramail - http://www.caramail.com

Re: Swap support

[Harry Kalogirou]

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

Την Δευ, 22-04-2002 στις 21:18, ο/η Riley Williams έγραψε:
> Would you mind if I tweaked the config system to allow this to be
> configured therein, making the entire configuration dependent on the
> CONFIG_EXPERIMENTAL config variable?

Yes make it dependent on CONFIG_EXPERIMENTAL, as for the configuration
of the swap partition leave it as it is now, since it is only for
developers at the moment...

> Also, does it use any particular format for the swap partition? I'm
> presuming from the above that it operates at partition level rather
> than at device level, so doesn't require a separate hard drive for
> swap usage.

There is no need to format the block device(partition) to be used...


Harry



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

Introduction and proposal:

[erich alfred heine]

Hello all,

I have recently joined this list, and would like to introduce myself:
Hi im Erich.

Anyway, Ive been playing with ELKS on my 286 laptop for a couple of weeks
now, and i think its way cool. Especially since the hard disk has long
since been kaput.

Ive read a couple emails about the documentation for this project, and I
concur that it does need improvement.  I would like to help out with
documenting this project, while I learn enough about the OS to maybe start
helping with code.

One of the things Ive thought would be neat, is a guide to the source code
of ELKS, like a programmers manual.  Is this something that is needed? Or
would my time be better spent working on other documentation?

Another of the projects related to ELKS that ive been considering, is a
good vt100 emulator, and/or a serial library that would make ELKS good for
controlling devices over a serial line, but I wont be able to consider
working on that till the end of the summer at the earliest.

Anyway, thats all from me, I just figured I would consult you all about
the documentation thing.

Erich Heine

Re: Introduction and proposal:

[Riley Williams]

Hi Erich.

> Anyway, Ive been playing with ELKS on my 286 laptop for a couple of
> weeks now, and i think its way cool. Especially since the hard disk
> has long since been kaput.

It's good to see others are interested. Welcome aboard.

> I've read a couple emails about the documentation for this project,
> and I concur that it does need improvement. I would like to help out
> with documenting this project, while I learn enough about the OS to
> maybe start helping with code.

You're certainly welcome to do that.

> One of the things I've thought would be neat, is a guide to the
> source code of ELKS, like a programmers manual. Is this something
> that is needed? Or would my time be better spent working on other
> documentation?

To be honest, the ELKS documentation in general falls into one or more
of the following categories:

 1. Hopelessly out of date.

 2. Abysmal English. Apparently, the non-English versions are far
    easier to follow than the English ones. (I can't confirm this
    as the only three languages I speak with anything approaching
    fluency are English and American).

 3. Ambiguous phraseology, largely as a result of (1) above.

Anything you can do to help with ANY of the ELKS documentation that
currently exists, or to create QUALITY new documentation, would be
appreciated by far more than just me.

> Another of the projects related to ELKS that I've been considering,
> is a good vt100 emulator, and/or a serial library that would make
> ELKS good for controlling devices over a serial line, but I won't be
> able to consider working on that till the end of the summer at the
> earliest.

I started on a VT100 emulator a while back, but got little further than
documenting some of the control sequences used. ELKS itself uses VT52
sequences for video control, so the emulator would basically consist of
a tool that receives VT100 sequences and generates the equivalent VT52
sequence. If you're interested, I have a genuine VT100 manual that lists
all the codes supported by the hardware in question.

As regards the serial library, ELKS already supports SLIP links, and I
understand that requires the kernel to provide pretty much complete
serial support, so that is probably an unnecessary project.

> Anyway, thats all from me, I just figured I would consult you all
> about the documentation thing.

The basic instruction there has to be "Go ahead".

Best wishes from Riley.

Re: Introduction and proposal:

[Harry Kalogirou]

Την Δευ, 22-04-2002 στις 23:58, ο/η Riley Williams έγραψε:
> Hi Erich.
> 
> 
> As regards the serial library, ELKS already supports SLIP links, and I
> understand that requires the kernel to provide pretty much complete
> serial support, so that is probably an unnecessary project.
> 

Actualy the serial driver needs some work. Flow control is the priority
one and modem control lines is priority two...

Harry



-
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

Re: Introduction and proposal:

[Riley Williams]

Hi Harry.

>> As regards the serial library, ELKS already supports SLIP links, and
>> I understand that requires the kernel to provide pretty much
>> complete serial support, so that is probably an unnecessary project.

> Actualy the serial driver needs some work. Flow control is the
> priority one and modem control lines is priority two...

Surely that's back to front? The primary flow control is via the CTS
and RTS modem control lines, so flow control can't be fully implemented
before the modem control lines have been implemented.

Best wishes from Riley.

Re: Introduction and proposal:

[Harry Kalogirou]

Την Δευ, 22-04-2002 στις 23:19, ο/η erich alfred heine έγραψε:
> Hello all,
> 
> I have recently joined this list, and would like to introduce myself:
> Hi im Erich.
> 

Nice to meet you!

The only thing I know is that we need documentators badly!!

Harry




-
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