-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ELKS v0.4.0 Pre-release version history and credits #873
Comments
This is obviously a huge work that has been done on ELKS for the PC/XT/AT platform. So many fixes & improvements ! That largely deserves the '0.4.0' version. |
Or the 1.0 :) |
This is big, @ghaerr!!
I’m vouching for 1.0 - this is just too big for a decimal-increment. Think about it - if all this is worth a decimal, what would it take to yank it up a whole number?
@ghaerr, your note keeping is impressive. Likewise for the contributions. Thank you.
Comments:
ARP: ARP wasn’t really working until you fixed it. So a reasonable entry would be
Fixed ARP, added ARP cache
clock:
added clock (or fixed?), elks now picks up time and date from the hardware at boot (and can set it).
Networking:
- File transfers both ways now supported.
- WD driver: It may be appropriate to be more specific than 'WD SMC', since there are many very different WD SMC cards out there. Suggest you mention WD8003 specifically.
NE2K: I think ‘rewritten’ is more appropriate than ‘fully working’.
Improved commands:
It may be worthwhile mentioning getty in this context, and that ELKS now works multiuser with 3 (probably 4) serial terminals.
Finally:
Possibly something about ’tested on’ or ‘works on’ - PCs running 8088, 8086, 80286, 80386 … and later
This should be a proud moment for all. Now ELKS is real - not just a half-stable playground for hackers (the original definition) and enthusiasts, but for users looking for a tool to make ’small’ hardware work big.
Unless someone else volunteers, I’ll do the Wikipedia update when the announcement is out.
Thanks again - to everyone and @ghjaerr in particular.
—Mellvik
… 19. nov. 2020 kl. 09:50 skrev toncho11 ***@***.***>:
Or the 1.0 :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#873 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA3WGODI72PJ5IBEYPJT32LSQTL5FANCNFSM4T2V2KCQ>.
|
Thanks for your comments, I've updated the release docs (above) from them.
Yes, there's a ton of stuff added, seemingly enough for a v1.0.0. However, there's still lots that doesn't work, and no need to rush. I plan on incrementing versions more quickly, and would like to continue to allow ELKS to be easier to use and evaluate. The Wiki page and website also need updating. The combination of that and more frequent versions will lead us to v1.0, just not yet :)
Thanks. I think it important to update the number of commits that have been made, and the kinds of things that have been added that make ELKS more useful on PC/XT/ATs, since that information is also quite out of date. Hopefully that will impart to readers the kind of activity ELKS has been seeing, and its usefulness. Thank you! |
OK for 0.4. I think for the bin images you should say: |
Yes, I agree that version numbers are also for marketing.
So here's a good point, and a problem. There currently isn't a good way to produce an ELKS image that will work on a variety of systems. In fact, ELKS was designed with a massive configuration system - the opposite of "it just works". The reasons for this are many, but with the far text kernel, it is now possible to create a larger kernel, which could possibly contain multiple network drivers, detection code, etc. So all that should be added, if the idea were truly to be able to run ELKS from a single distribution image/kernel. All this needs to be thought about more, and another reason we're not really ready for 1.0 - ELKS configuration vs works out-of-the-box design isn't ready for a lot of users yet. Thank you for your comments! |
Simply saying that it is currently configured with these settings is helpful. It hints why it might not work when people download it. |
When is it coming the new release :) ? |
Thanks, I have updated the release notes with a download section. |
@ghaerr From some comments on Youtube, people report that they can not attach the hdd to another computer to put an ELKS partition, so the sys tool comes handy! |
Following is a first-draft template of all that's happened since v0.3.0, along with the contributors. Please let me know what needs to be added, as the list is long and I'm sure something or someone has been forgotten! I plan to use this text as the v0.4.0 Final Release documentation.
ELKS v0.4.0 Downloads
Prebuilt disk images for floppy and hard disks are downloadable below from Github Assets for this release. These images can be used to boot from PC/XT/AT hardware, or an emulator, such as QEMU. The images are built with network support by default, using the NE2K network card, set for I/O address=0x300 and IRQ=12. See the Wiki HowTo for more information.
ELKS v0.4.0 Enhancements
Kernel
System Call Fixes: wait, rmdir, access, brk, link, stat, gettimeofday
Exec
Filesystems
Disk & I/O Subsystem
Console
Drivers
Networking
Networking Bug Fixes
Boot
New Commands
Improved Commands
C Library
Build
Compiler / Tools
Images
Documentation
The text was updated successfully, but these errors were encountered: