157 replies to this topic

[cyanisaac]

This OS is dead. No download is linked. Please lock this thread.

Edited by cyanisaac, 13 January 2016 - 01:38 AM.

[biggest yikes]

Looks nice, but if you're going to restrict access to "shell", then why not "rom/programs/shell", "./rom/programs/shell", "./shell", etc.?
Another bug, if you go into "edit" and exit "edit" the screen is no longer gray

Edited by Atenefyr, 02 May 2015 - 10:54 PM.

[cyanisaac]

 Atenefyr, on 02 May 2015 - 10:45 PM, said:

Looks nice, if you're going to restrict access to "shell", then why not "rom/programs/shell", "./rom/programs/shell", "./shell", etc.?

That's something that I put in the code when I first started working on it, to prevent people from using the CraftOS shell, but what the OS will do is make "shell" point to "/OTOS/core" which is the modified shell.

I'll get rid of that now, it will be available in the nightly version likely, well, tonight.

[biggest yikes]

 cyanisaac, on 02 May 2015 - 10:54 PM, said:

 Atenefyr, on 02 May 2015 - 10:45 PM, said:

Looks nice, if you're going to restrict access to "shell", then why not "rom/programs/shell", "./rom/programs/shell", "./shell", etc.?

That's something that I put in the code when I first started working on it, to prevent people from using the CraftOS shell, but what the OS will do is make "shell" point to "/OTOS/core" which is the modified shell.

I'll get rid of that now, it will be available in the nightly version likely, well, tonight.

Seemed to have edited my post too late, how about this?

 Atenefyr, on 02 May 2015 - 10:45 PM, said:

Another bug, if you go into "edit" and exit "edit" the screen is no longer gray

Another thing I'd like to see (so much feedback, I know) is a file to show the version of the OS, so people can track the version of the OS, and differentiate OTOS Nightly with OTOS Stable

Edited by Atenefyr, 02 May 2015 - 11:00 PM.

[Creator]

Can you post a list of available commands. Else, nice work.

[cyanisaac]

 Atenefyr, on 02 May 2015 - 10:56 PM, said:

 cyanisaac, on 02 May 2015 - 10:54 PM, said:

 Atenefyr, on 02 May 2015 - 10:45 PM, said:

Looks nice, if you're going to restrict access to "shell", then why not "rom/programs/shell", "./rom/programs/shell", "./shell", etc.?

That's something that I put in the code when I first started working on it, to prevent people from using the CraftOS shell, but what the OS will do is make "shell" point to "/OTOS/core" which is the modified shell.

I'll get rid of that now, it will be available in the nightly version likely, well, tonight.

Seemed to have edited my post too late, how about this?

 Atenefyr, on 02 May 2015 - 10:45 PM, said:

Another bug, if you go into "edit" and exit "edit" the screen is no longer gray

Another thing I'd like to see (so much feedback, I know) is a file to show the version of the OS, so people can track the version of the OS, and differentiate OTOS Nightly with OTOS Stable

Again I don't believe I need to block shell, since if you're trying to get to the CraftOS shell you probably know what you're doing.

The edit program will have this fix, again, I'll get it done and have it available tonight.

There is no stable version of the OS right now. there's live indev stuff, and then there's the nightly version linked here. The stable version will come when I have a lot more functionality.

[cyanisaac]

 Creator, on 02 May 2015 - 11:06 PM, said:

Can you post a list of available commands. Else, nice work.

Here you go: https://docs.google....dit?usp=sharing
sorry my os does so little right now xD I need to get to work...

[biggest yikes]

 cyanisaac, on 02 May 2015 - 11:06 PM, said:

There is no stable version of the OS right now. there's live indev stuff, and then there's the nightly version linked here. The stable version will come when I have a lot more functionality.

I know..
I'm saying, in the future, when stable is released, it'll be good to have a version file to easily identify stable vs. nightly

Edited by Atenefyr, 02 May 2015 - 11:25 PM.

[cyanisaac]

Alrighty, I'm making a program that will fix all of the issues with colors being off (i.e. the edit program). Although I will definitely implement something that will fix this in the background.

You'll be able to run a program that has color issues like this: "colorfix <whatever you would normally run in the shell>"

This will set the colors to defaults, run the program, pause for 2 seconds so you can see any messages the program gives you, and then will clear the screen and put you back with normal colors.

This will be pushed to the nightly builds soon, let me go ahead and do that. This change has been pushed to the nightly builds.

Edited by cyanisaac, 02 May 2015 - 11:52 PM.

[cyanisaac]

Alrighty, pushed out a set of changes to the nightly build.

This includes:

• removed restriction on shell
  
• made shell forward to the custom shell
  
• Added the "colorfix" program to fix color issues (would recommend using with edit).
  
• other improvements i forgot about

If any major issues pop up let me know and I will address them as soon as possible.

[Cloud Ninja]

So realistically all it is is a locked down shell? I honestly dont see the point in that. If i wanted LuaIDE (which is what seems to be the only change other than sandboxing it) id install it myself. I also reccomend changing the standard switch command from 'std' for social reasons, because you know other people are going to give you crap for it.

[biggest yikes]

 CloudNinja, on 03 May 2015 - 01:48 AM, said:

So realistically all it is is a locked down shell? I honestly dont see the point in that. If i wanted LuaIDE (which is what seems to be the only change other than sandboxing it) id install it myself. I also reccomend changing the standard switch command from 'std' for social reasons, because you know other people are going to give you crap for it.

Give him some slack, it's in development

[cyanisaac]

 CloudNinja, on 03 May 2015 - 01:48 AM, said:

So realistically all it is is a locked down shell? I honestly dont see the point in that. If i wanted LuaIDE (which is what seems to be the only change other than sandboxing it) id install it myself. I also reccomend changing the standard switch command from 'std' for social reasons, because you know other people are going to give you crap for it.

Actually if you read... It's not a locked down shell, and won't be. You can even terminate out of it if you want. The root shell is going to be deprecated so... social reasons? Whatever you were trying to convey, will not be an issue. LuaIDE is there for convience because I really like the editor and so I wanted to make it easy to install... But better stuff will be coming soon, I need to work on the shell redesign, that should be here sometime relatively soon.

[ProjectB]

Ok, so this is only a small feature request, but could you add the ability to press your up key to run the previously run command, it's really helpful in CraftOS. In case you don't know how to do it, read on.
First you need to make a table with the previously run commands:

commandsRun = {}

Last just make sure that the read function sees the table!

input = read(nil, commandsRun)

Then add it to the table, so it can be run in the future!

table.insert(table, string)

The reason I typed out a mini-tutorial is because I just couldn't find any information on the topic at all, so I thought I would let you know how to implement it.

[cyanisaac]

 ProjectB, on 03 May 2015 - 04:29 PM, said:

Ok, so this is only a small feature request, but could you add the ability to press your up key to run the previously run command, it's really helpful in CraftOS. In case you don't know how to do it, read on.
First you need to make a table with the previously run commands:

commandsRun = {}

Last just make sure that the read function sees the table!

input = read(nil, commandsRun)

Then add it to the table, so it can be run in the future!

table.insert(table, string)

The reason I typed out a mini-tutorial is because I just couldn't find any information on the topic at all, so I thought I would let you know how to implement it.

Thanks, I will implement that whenever I work on OTOS next (probably tomorrow)

[cyanisaac]

Okay so I am going to be focusing attention on this and will be changing some stuff about it.

I am stripping out the root shell functionality since everything is unlocked anyhow. I will also be adding a theming system into the shell so you can customize the colors. These will be the most notable changes that will come soon.

Less noticeable changes:

I'm going to switch from having a nightly system to a snapshot system. This is because it's slow and painful to update the nightly pastebin. Instead you will see an update every two weeks or so if I stay on schedule. Along with this change will come an updater that will check for new versions and notify you of any new versions.

The boot loader my OS uses will also be receiving an update that will improve stuffs that you don't care about :I

I will get my code on GitHub.

Anyways expect these changes over the next one to two weeks, and thanks for the support.

[biggest yikes]

shell.run("reboot")

Ahm, hello?

os.reboot()

When downloading LuaIDE, why not run it with colorfix automatically?
If luaide2 is the real LuaIDE file, then the file luaide would be:

shell.run("colorfix luaide2")

Edited by Atenefyr, 06 May 2015 - 01:15 AM.

[cyanisaac]

 Atenefyr, on 06 May 2015 - 01:12 AM, said:

shell.run("reboot")

Ahm, hello?

os.reboot()

When downloading LuaIDE, why not run it with colorfix automatically?
If luaide2 is the real LuaIDE file, then the file luaide would be:

shell.run("colorfix luaide2")

I will make note of this and implement it, but first I need to implement an improved updater so I can notify people when to update their snapshot versions.

[cyanisaac]

Alrighty so the first thing I've worked on is a bootloader (runs as the startup file). It's not very indepth but it does offer a bit more functionality than the previous one.

It will allow you to boot into CraftOS's shell in the event that you need to access that, for whatever reason. It will print out any errors that the shell runs into (hopefully). Along with these comes a handy third mode called Recovery that will allow you to repair the system, reset the computer etc.

This should be available in its entirety with the first snapshot-type update I'll push out hopefully this week. This will not be included in the last nightly update, which will simply add a notifier to the updater (so you know when the S1 update is available).

Edited by cyanisaac, 06 May 2015 - 07:13 PM.

[Creator]

You sound very professional: snapshot, nightly.

Can't you do everything in CraftOS that you would be able to do in Recovery?