Earlier quoted context omitted.
barco really just means "hay barrack" in my native language ¯\_(ツ)_/¯
It means 'watercraft' or 'sea worthy ship' in Spanish, too. :) In what language does it mean 'hay barrack'?
Indeed the wiki yields no matches
Barco: Linux Containers from Scratch in C
21–30 of 75 posts
Re: Barco: Linux Containers from Scratch in C
#22Earlier quoted context omitted.
I still think it is tangential. The author stated that they wrote this project to learn. The readme says that it is not intended for production use and that there is no networking set up in the containers. With that context, I doubt that name collisions outside of the containers space are top of mind.
barco really just means "hay barrack" in my native language ¯\_(ツ)_/¯
'Boat' in mine
Re: Barco: Linux Containers from Scratch in C
#23Earlier quoted context omitted.
GP was asking if it could cause an issue for the OP, not complaining about an annoyance. It's something that the OP may want to address.
I still think it is tangential. The author stated that they wrote this project to learn. The readme says that it is not intended for production use and that there is no networking set up in the containers. With that context, I doubt that name collisions outside of the containers space are top of mind.
If it was my project, I would want to know about a possible name collision. Saying it once seems fine.
Re: Barco: Linux Containers from Scratch in C
#24Earlier quoted context omitted.
I still think it is tangential. The author stated that they wrote this project to learn. The readme says that it is not intended for production use and that there is no networking set up in the containers. With that context, I doubt that name collisions outside of the containers space are top of mind.
barco really just means "hay barrack" in my native language ¯\_(ツ)_/¯
Venetian: https://vec.m.wikipedia.org/wiki/Barco
Re: Barco: Linux Containers from Scratch in C
#25Question: for sandboxing untrusted code, should I invest time in learning more linux container stuff or switch to learning WASI? I am inclined towards WASI myself.
Re: Barco: Linux Containers from Scratch in C
#26[flagged]
Why would there be any conflict? They're in completely different domains so there is no potential for confusion. Why would copyright be relevant in any way? Do you even know what copyright is?
Re: Barco: Linux Containers from Scratch in C
#27barco is a project I worked on to learn more about Linux containers and the Linux kernel, based on other guides on the internet.
How did you come up with the name "Barco"?
Re: Barco: Linux Containers from Scratch in C
#28Question: for sandboxing untrusted code, should I invest time in learning more linux container stuff or switch to learning WASI? I am inclined towards WASI myself.
I have more faith in WASI. Linux containers is inherently in a whack-a-mole position where they're trying to retrofit security onto something that was never built for it, which very rarely works.