Solved ClonOS - FreeBSD based distro for virtual hosting platform

[Ole]

This is not a "distro". It's FreeBSD with packages pre-installed.

Ok, this is not a "distro" if it is very important for you But with current FreeBSD you won’t be able to run bhyve+Kali/Parrot linux (see: https://lists.freebsd.org/pipermail/freebsd-virtualization/2019-July/007604.html ), p9fs ( https://reviews.freebsd.org/D10335 ), Xorg in jail ( kmem patch https://www.leidinger.net/blog/2007/04/07/a-desktop-environment-in-a-jail/ + https://svnweb.freebsd.org/base?view=revision&revision=r261326 ) and bhyve live migration. When all these patches will be included in FreeBSD kernel/userland, then I agree that the ClonOS = FreeBSD + pre-installed packages. But at the moment this is not so.

 

[drhowarddrfine]

Yes. It's important to YOU to get the terminology correct and not sprinkle it with Linux terms.
You are using FreeBSD and installing additional packages.

 

[Ole]

Yes. It's important to YOU to get the terminology correct and not sprinkle it with Linux terms.
You are using FreeBSD and installing additional packages.

As for ME, I and people of my generation used this word long before Linux and imply what is described here: https://en.wikipedia.org/wiki/Software_distribution
If for the new generation this word means Linux - well, I will take note of this, thanks you.

 

[Sevendogsbsd]

No worries Ole, the problem is the Linux community, or Linux users do not understand what FreeBSD is or how it is structured, came about, etc. They use some terms interchangeably and incorrectly, and assume certain things that may be true in Linux but are not at all true in FreeBSD.

Just trying to make sure folks understand this, that's all. We get a lot of new users coming off Linux that keep trying to do things in FreeBSD the same way they did them in Linux and it typically doesn't work or is not a best practice.

 

[shkhln]

There are so many issues with this software and you decided to discuss the term "distribution"? Did anybody actually look at the code?

 

[Ole]

Did anybody actually look at the code?

As you can see, someone looked and wrote this comment. In fact, we need to move towards AMQP (for example, beanstalkd ). But everything rests on free time. WIP.

 

[shkhln]

Relying on someone else to fix security issues in your code is not good enough. WIP is not an excuse either.

 

[Ole]

Can I ask a moderator to close this topic? This community is not able to speak on the topic.

 

[mark_j]

Ok, this is not a "distro" if it is very important for you But with current FreeBSD you won’t be able to run bhyve+Kali/Parrot linux (see: https://lists.freebsd.org/pipermail/freebsd-virtualization/2019-July/007604.html ), p9fs ( https://reviews.freebsd.org/D10335 ), Xorg in jail ( kmem patch https://www.leidinger.net/blog/2007/04/07/a-desktop-environment-in-a-jail/ + https://svnweb.freebsd.org/base?view=revision&revision=r261326 ) and bhyve live migration. When all these patches will be included in FreeBSD kernel/userland, then I agree that the ClonOS = FreeBSD + pre-installed packages. But at the moment this is not so.

It is hard to use a term not already engulfed by Linux.
Maybe try: ClonOS is a FreeBSD remodel?
Or just call it ClonOS - FreeBSD-based if you must define it as using FreeBSD?

Not as catchy as a FreeBSD distro, though, I grant you.
Well done on your work, anyway.

 

[Crivens]

Can I ask a moderator to close this topic? This community is not able to speak on the topic.

Yes you can. You take the report button and explain why and how your thread went off the rails. We take a look and decide. Right now I let this open for another few hours for all participants to level out.

 

[shkhln]

What is the topic then? Apparently, there is even an automated exploit for that thing: https://github.com/Andhrimnirr/ClonOS-WEB-control-panel-multi-vulnerability.