Lino Commando: Difference between revisions

[unchecked revision]

← Older edit

Content deleted Content added

VisualWikitext

Revision as of 19:13, 19 February 2012 view source osdev>Bellezzasolo m Text UI category ← Older edit		Latest revision as of 17:09, 7 November 2021 view source osdev>Killaship m Added my name on the botton
(10 intermediate revisions by 9 users not shown)
Line 1: He's been impressed by the "naked beauty" of DOS/Unix times. The first thing he wants to be achieved is a blinking cursor after a ">" symbol so that he can type commands. No matter if there's no way to start 2 programs at the same time: he just needs a text editor and a FAT12 driver. Maybe you prefer a [[What order should I make things in\|different approach]]. == Reaching Lino's level == === A first shell === # Your first goal is an improved keyboard handler. Everything will start there. Make sure you leave room for a keyboard map (for instance easily compilable apart and loaded as a module by [[GRUB]] so that beta-testers can load their own map). # Don't echo characters right from the start and keep track on what's on screen. Commands histories, completions and working character erasure will be a must. # just put a few "built-in" commands from the start, but keep your mind open to "how will further shell extension add commands ?" ... scanning a table rather than a switch statement ? you're the one who knows. === Starting programs. === # Decide what programs will look like. The easiest model is to give them one data+code segment and let them run there. # Your programs will have to come from somewhere. Lino had used one GRUB module as a '[[initrd\|ramdisk]]' where programs were stored (he didn't tell whether using FAT or something even more simple for the internals). What is certain is that program see them as "real" files. # Provide your programs a simple API: open/close/read/write to files, read/write to the console, exit are enough at the start. Prevent your programs from writing directly to video memory. Line 19: Once this is done ask yourself how you'll start other programs from one program. This means implementing the [[System calls\|system(8) call]]. == Going further than Lino == Well, in many aspects, Lino's OS looks like first steps of most ~~unix~~Unix clones. Because of the simple "start at offset 0 in CS/DS" approach, whether multiple programs share the same address space or not is not much complicated, but Lino still has to write [[Multitasking Systems\|multitasking ~~systems~~]] support, which will require him a more sophisticated way of [[Memory ~~Management~~management\|allocating and freeing memory]] == Lino's bookshelf == Line 33 ⟶ 34: == People and OSes related to Lino Commando == * Inflater: ''"That's me alright :) I just don't have fully working FAT12 driver for my real mode 16-bit Borland Pascal OS :D)"'' * Piranha: ''"Me too. Who ~~need~~needs graphics at this stage! Just making the internals work right is hard enough!"'' * Troy: ''"Text mode calls to me like bananas call to monkeys. Except with me there's no flinging of poo."'' * iMate900: ''Lino, here I come kicking ~~meself~~myself with SauOS!!!! Oh, and I'm not even finished with my ATA driver :)'' * KotuxGuy: ''Yeah, this is most likely me too ;) I don't have any filesystem support though'' * bellezzasolo: ''This is always the best way to start. Nice if it's a PMode shell though ;)'' * LifeDJIK: ''Yes! That's definitely me! But I don't have FAT12 driver... I have FAT32 driver!'' * Moondeck: ''Graphics? VGA? Who needs that crap, I use serial!'' * Superleaf1995: ''Like me :D, I'm just doing with LeafOS, Why use graphics when you have a fancy text?'' * ''Killaship: Probably me (Minus the FAT-anything drivers), I just think text mode looks nice!'' * ''Insert your name here'' [[Category:Text UI]] [[Category:Developer Archetype]]