Forthcoming 0.1.0 release

Forthcoming 0.1.0 release

[Riley Williams]

Hi all.

I've just tweaked the TODO document to state what I see as the steps
needed for various kernel releases, including the 0.1.0 release we're
proposing for 1st May. Can you all have a look at it, and let me know
what you think please?

Best wishes from Riley.

Re: Forthcoming 0.1.0 release

[Harry Kalogirou]

Την Τρι, 23-04-2002 στις 20:58, ο/η Riley Williams έγραψε:
> Hi all.
> 
> I've just tweaked the TODO document to state what I see as the steps
> needed for various kernel releases, including the 0.1.0 release we're
> proposing for 1st May. Can you all have a look at it, and let me know
> what you think please?
> 

I think it's ok.

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: Forthcoming 0.1.0 release

[erich alfred heine]

Hey all,
I dont know if this has been brought up yet, but on the sourceforge page,
in the news; index section (http://elks.sourceforge.net/news/) there are
articles stating that elks 0.1.0 and 0.1.1 are out and released. This
doesnt seem to jibe well with a planned release of 0.1.0 for 5-1.

And unrelated to all of this, has anyone made an OS builder for elks yet.
Im not sure exactly what to call my idea but here it is:

A program that guides you thru kernel compilation, then asks you which
tools you would like, and what size disk you will be using, then creates
the image for the disk.  I ask this because one of the biggest uses I see
for ELKS is booting old machines as terminals and (not so) embedded
microcontoller purposes over serial ports, or on that old 286 with custom
hardware etc. Only certain tools would be needed and usefull depending on
what you are doing.

And couple of quick question from my personal experiences:
Is there any way to tell what capacity of disk your fdd likes? Im booting
from a 1.44 MB floppy, but I really dont know if my disk drive is 720K and
playing nicely or what. All that extra disk space would be NICE (i could
even use my laptop as laptop and take it places, and make people look at
me funny!)

2. Maybe im mistaken, but i thought bcc was a K&R compiler, so why the big
push to ansi'fy it? (besides the fact that ansi C makes debugging a little
bit easier?)

Erich Heine
PS sorry about the long and not very well composed mail, ive been writing
it for a few hours, every time i have to wait for the computer im on to do
work.  (I should make an elks gis system, the network of roads that im
computing now would takes 8 hours on a P4 1.5 GHz, think, I could tie up
286s for the next several years!)

On Tue, 23 Apr 2002, Riley Williams wrote:

> Hi all.
>
> I've just tweaked the TODO document to state what I see as the steps
> needed for various kernel releases, including the 0.1.0 release we're
> proposing for 1st May. Can you all have a look at it, and let me know
> what you think please?
>
> Best wishes from Riley.
>
> -
> 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: Forthcoming 0.1.0 release

[Riley Williams]

Hi Erich.

> I dont know if this has been brought up yet, but on the sourceforge
> page, in the news; index section (http://elks.sourceforge.net/news/)
> there are articles stating that elks 0.1.0 and 0.1.1 are out and
> released. This doesnt seem to jibe well with a planned release of
> 0.1.0 for 5-1.

Those are due to a misunderstanding regarding a proposed release of
0.1.0 on 1st April, and will be vanishing when I update the website
next week.

> And unrelated to all of this, has anyone made an OS builder for elks
> yet. Im not sure exactly what to call my idea but here it is:
> 
> A program that guides you thru kernel compilation, then asks you
> which tools you would like, and what size disk you will be using,
> then creates the image for the disk.  I ask this because one of the
> biggest uses I see for ELKS is booting old machines as terminals and
> (not so) embedded microcontoller purposes over serial ports, or on
> that old 286 with custom hardware etc. Only certain tools would be
> needed and usefull depending on what you are doing.

That's something I can't comment on, other than to point out that ALL of
the existing tools will fit on a single 1.44M floppy alongside the boot
kernel image.

> And couple of quick question from my personal experiences: Is there
> any way to tell what capacity of disk your fdd likes? Im booting
> from a 1.44 MB floppy, but I really dont know if my disk drive is
> 720K and playing nicely or what. All that extra disk space would be
> NICE (i could even use my laptop as laptop and take it places, and
> make people look at me funny!)

The basic way to determine what capacity floppy drive you have is to
start with the highest capacity disk you can find and see if the drive
can read it, and step down a size until you find one it can. That one is
the maximum your drive can handle.

> 2. Maybe im mistaken, but i thought bcc was a K&R compiler, so why
> the big push to ansi'fy it? (besides the fact that ansi C makes
> debugging a little bit easier?)

It's basically so we can run one of the GPL'd `lint` tools across
the source and ensure that all function calls match the function
definitions.

We've already found one such bug - the function chq_addch was in two
cases being called with a missing parameter - and there's almost
certainly several more...

> Erich Heine

> PS sorry about the long and not very well composed mail, ive been
> writing it for a few hours, every time i have to wait for the
> computer im on to do work.  (I should make an elks gis system, the
> network of roads that im computing now would takes 8 hours on a P4
> 1.5 GHz, think, I could tie up 286s for the next several years!)

LOL !!!

Best wishes from Riley.

Re: Forthcoming 0.1.0 release

[Blaz Antonic]

> And couple of quick question from my personal experiences:
> Is there any way to tell what capacity of disk your fdd likes? Im booting
> from a 1.44 MB floppy, but I really dont know if my disk drive is 720K and
> playing nicely or what. All that extra disk space would be NICE (i could
> even use my laptop as laptop and take it places, and make people look at
> me funny!)

I'm not sure what exactly you want to know; if your system boots from
1.44 formatted floppy that means you have a drive that supports (at
least) 1.44 MB media. 720 KB has only 9 sectors per track whereas 1.44
MB medium has 18 sectors per track - if your drive was 720 KB and your
boot floppy was 1.44 MB it wouldn't be able to read track 0, let alone
all other tracks (and therefore wouldn't be able to boot).

Probe code should be able to determine size of the medium currently
inserted in your drive (so if your drive supports 1.44 MB media and you
put 720 KB floppy in it it should work just fine, same goes for 2.88 MB
drives and media of smaller formats). 

IMO, that is.

Blaz Antonic