[UNIX-like] CWCOS

ANNOUNCEMENTS:
STUPID INSTALLER
install pkg to /disk and install cwcos from there -_-/>

Spoiler

— May 25, 2014 —
New installer coming soon as part of package when ccx (ComputerCraft X) is working!
Okay, people. Here it comes. You won. I code a GUI. It's in progress.

CWCOS, the OS that stands for somethingicantremember OS where the name is only really mentioned in the installer and in the package manager. I have tried to make a UNIX-like environment, even with init!
Screens:

Spoiler

Yes, it says booting FOREVER (not really, just until it scrolls off the screen) I'm just too lazy to clear and re-draw :P/>
I'm also too lazy to create my own shell so I use a slightly modified CraftOS shell. (I at least tried here, but failed. Feel free to post your various bashes on package.)

Downloads:

Spoiler

First, install package (pkg):

pastebin run JFDE9wiv

then

/usr/bin/pkg install cwcos
or
/disk/usr/bin/pkg install cwcos
if you're so cool you installed it to /disk

An installer floppy creator (think Linux installer CD) coming soon sporting a complete CWCOS system to run the installer! (sadly, no installing to floppy from floppy overwriting the installer :P/>)

package:

Spoiler

package is the default package manager in CWCOS. To submit a package, follow the instructions in README.md in the https://github.com/C...ree/packagerepo GitHub repo and branch.

APIs:

Spoiler

Anything started from init has the kernel API:

Spoiler

kernel.shutdown()

Shuts down the computer WITHOUT executing the rest of init

kernel.reboot()

Reboots the computer WITHOUT executing the rest of init

and everything ever has the init API:

Spoiler

init.postmessage<level>(from, message)

Posts message of level Info, Warn, or Error in the following format:

[from] message

init.ok() and init.fail()

Shows [ OK ] or [ FAIL ] aligned to the right on the previous line

init.termClear()

Handy tool for clearing the terminal and putting the cursor at (1, 1)

init.termReset()

Sets the text color to blue (why would you need this?)

same with ACPI:

Spoiler

acpi.shutdown()

Safely shuts down with init and the kernel knowing

acpi.reboot()

Safely reboots with init and the kernel knowing

This /might/ not be what I think it is. But. I was gonna start a GUI or something to contribute to the OS, and the files can't be cloned 'cause they have no command endings.

What I mean by that:

Spoiler

herp.txt –#This will get downloaded.
derp –#This will not, it has no command ending.

Agoldfish, on 25 May 2014 - 12:42 AM said:

This /might/ not be what I think it is. But. I was gonna start a GUI or something to contribute to the OS, and the files can't be cloned 'cause they have no command endings.

What I mean by that:

Spoiler

herp.txt –#This will get downloaded.
derp –#This will not, it has no command ending.

What are you wanting to clone? I did all git work on the GitHub interface on Chrome OS, so something might be wonky with cloning as I didn't do so.

CodingWithClass, on 25 May 2014 - 12:48 AM said:

Agoldfish, on 25 May 2014 - 12:42 AM said:

This /might/ not be what I think it is. But. I was gonna start a GUI or something to contribute to the OS, and the files can't be cloned 'cause they have no command endings.

What I mean by that:

Spoiler

herp.txt –#This will get downloaded.
derp –#This will not, it has no command ending.

What are you wanting to clone? I did all git work on the GitHub interface on Chrome OS, so something might be wonky with cloning as I didn't do so.

Using Git Bash, cloning is putting it in your local file system so you can push and stuff without going on GitHub.
EDIT: I didn't realize there were branches. -_-/>

Agoldfish, on 25 May 2014 - 12:50 AM said:

CodingWithClass, on 25 May 2014 - 12:48 AM said:

Agoldfish, on 25 May 2014 - 12:42 AM said:

This /might/ not be what I think it is. But. I was gonna start a GUI or something to contribute to the OS, and the files can't be cloned 'cause they have no command endings.

What I mean by that:

Spoiler

herp.txt –#This will get downloaded.
derp –#This will not, it has no command ending.

What are you wanting to clone? I did all git work on the GitHub interface on Chrome OS, so something might be wonky with cloning as I didn't do so.

Using Git Bash, cloning is putting it in your local file system so you can push and stuff without going on GitHub.
EDIT: I didn't realize there were branches. -_-/>

Yeah, I'm familiar with git command line, but yeah there are many branches: one for each package made by me for it and packagerepo which is the repository (just click the plus by to create a file and paste the installer contents there
EDIT - Scratch that - I forgot how PRs worked. Just https://docs.google....m?usp=send_form