dusk-fun

Unnamed repository; edit this file 'description' to name the repository.
git clone git://git.alexwennerberg.com/dusk-fun
Log | Files | Refs | README

commit 453bd2cd6ff99c314cacef9c5ec87713879df61e
Author: alex wennerberg <alex@alexwennerberg.com>
Date:   Sat, 29 Apr 2023 13:48:03 -0400

Initial commit

Diffstat:
AREADME | 4++++
Ahello.c | 4++++
Aunix.fs | 32++++++++++++++++++++++++++++++++
3 files changed, 40 insertions(+), 0 deletions(-)

diff --git a/README b/README @@ -0,0 +1,4 @@ +Dusk OS ports + tools +===================== + +Experimenting with Dusk OS diff --git a/hello.c b/hello.c @@ -0,0 +1,4 @@ +int helloworld() { + printf("Hello, World!"); + return 0; +} diff --git a/unix.fs b/unix.fs @@ -0,0 +1,32 @@ +\ Getting started with Dusk OS coming from unix +\ +\ When I booted up Dusk OS, my first question was: how do I navigate the fileystem? How do I read/edit files? +\ Here's how to translate from unix to Dusk OS and get started. +\ You can use these words or just read them to understand + +\ Takes no args, operates on current directory +: ls curpath :listdir ; + +\ postfix: p" .." cd +: cd Path :chdir ; + +\ Reading files with ged. It's vi-like +\ We need to import the text editor +\ f<< text/ed.fs +\ f<< text/ged.fs +\ If you want this on boot, you can add those lines to init.fs +\ f" init.fs" vi +: vi edload ged ; +\ save with edsave + +\ q to quit. see doc/text/ged.txt for full docs + +\ Compile a C program using Dusk C from a unix environment + +\ put hello.c in fs +\ run make +\ import the following: +\ f<< comp/c/cc.fs +\ f<< comp/c/lib.fs +\ cc<< hello.c +\ helloworld -> should print "Hello, World!"