Snap!nix Neo

Requests to the Community Collaborations
, , , ,
1

Hello. Would anyone be interested in remaking Snap!nix, this time with everything but the file system and TTY emulated? (I.E. A real kernel.)

Here's the link for the Snap! project. Snap!nix Neo

SMERGE

TODO:

  • File system
    • Reading Files
    • Writing Files
  • Terminal
  • Visual Mode
  • Multitasking
  • Multi-User
    • File ownership & permissions
  • POSIX Standard compliance! (To an acceptable degree.)
2

Yes, in fact I was looking back at it a few days ago.

3

Great!

4

I remember when the original snapnix was made

I think you should sharing across the cloud

and if you want to add it me and someone else made a cloud database library

5

Whoever implemented users, I have some changes I'd like to make.

  1. Passwords will be stored in /home/username/shadow, and will be stored as SHA-256 hashes.
  2. Login will be handled by /etc/login, to be called by /etc/init.
  3. A user's home directory is /home/username.
  4. Bash is only a shell. Nothing else.

However, let's focus on setting files first.

6

"Didn't you know NEO is famous for it's high defense?"

7

that was me, i will add those changes.
edit: what should i do with the users/add command?
edit 2: @bluebaritone21, the new get block can be used with the list blocks to write files.
Snap!nix Neo script pic

8

undertale refrence1?!?!?

9

Cool. I'll look into that.

Note: to prevent vandalizing, everyone (myself included) should get confirmation before pushing changes. (I.E: let's only have a few branches.)

10

ok, but

11

Create a new directory in /home.

I already have a get block that works like your new one. It's just hidden. (Also, don't store lists in files. directories are the only lists.)

12

i mean, it already exists, where do i put it now that /users is gone?

13

What do you mean?

14

where should it be in the filesystem?

15

You mean the executable? put it in /bin/addUser.

16

can i push changes?

17

Can I help?

18

Go ahead.

I'm working on the teletype, and I'll make a PR when I'm done.

19

Sure!

20

How's this for a hashing algorithm? (It's super insecure, but it's better than nothing.)
pic