Comment on Gokrazy – A Native Go UserlandparentComments−tyingq4yMaybe the easiest way to visualize it is that there is no filesystem at all. No shell, no "libc", no "ssh into the machine", no "cp", "mv" "ls", etc.They do provide a way to get one filesystem in place, but you can only interact with it using golang calls within your application.−hamburglar4y"no filesystem" does not fit into this list of things. There is definitely a filesystem. It has an optional sshd, and an optional shell that includes cp, mv, ls, etc, but there is always a filesystem.
Comments
Maybe the easiest way to visualize it is that there is no filesystem at all. No shell, no "libc", no "ssh into the machine", no "cp", "mv" "ls", etc.
They do provide a way to get one filesystem in place, but you can only interact with it using golang calls within your application.
"no filesystem" does not fit into this list of things. There is definitely a filesystem. It has an optional sshd, and an optional shell that includes cp, mv, ls, etc, but there is always a filesystem.