@PSX_Defector said:

But FreeBSD came out AFTER 4.1BSD, which is where the great schism started. Next started their work on Mach/Darwin a few years before FreeBSD came about. There is plenty borrowed from FreeBSD but it's still running kernels that are nothing like FreeBSD.

Yes, the ported the Mach kernel to the FreeBSD ecosystem. But the bulk of the code is from FreeBSD, not from Next/Mach. The OSX project started long after both FreeBSD and Next were established. That Next was older isn't really a big deal. OSX was much later. At the time, around 1999, they made a big deal that it was mostly FreeBSD with the Mach kernel swapped out for the old kernel.

Not totally unlike the Dragonfly project. Based on FreeBSD but taking the kernel in a different direction.

Here it is: Understanding the Tradeoffs in Latency and Throughput

I also tried to use the ccd with different segment, with config below:

server.conf
client-config-dir /etc/openvpn/ccd
route 10.8.2.0 255.255.255.0

/etc/openvpn/ccd/username1:
Code:
ifconfig-push 10.8.2.9 10.8.2.10

but still getting 10.8.0.x internal IP instead of 10.8.2.x.

Also put in IPtables:
iptables -A FORWARD -s 10.8.2.0/24 -j ACCEPT

@johnhooks said:

@scottalanmiller said:

@johnhooks said:

I knew the workstation version was, I just didn't understand why they have a "server" version.

Server and workstation are just different sets of packages. Not different products. Server is the actual proving ground, the workstation isn't really a big deal since no one actually uses CentOS or RHEL as a desktop, that would be pretty silly in general. Fedora Workstation is the product that is actually used as a workstation. It is Fedora Server that is the actual proving ground for CentOS and RHEL.

I actually did use CentOS 7 as a desktop for a while, just to try it. It wasn't bad. I don't use anything strange, and was able to compile everything else I needed. Their gnome theme is pretty nice.

Thing is, if you used CentOS 7 that means that it was pretty new. But CentOS 7 will be one painfully old desktop by the time that CentOS 8 is getting close. Fedora updates every six to eight months, so their desktops are always current. So you are never looking at something outdated. CentOS 7 will be many years out of date when it is time to replace it.

@scottalanmiller Ok, I think I got it. Per http://bugs.elastix.org/view.php?id=2549:

Starting with PHPMailer v5.2.7, the default HELO hostname is not set anymore to 'localhost' if not supplied on the Hello() function... This generates that the Elastix remotesmtp configuration checker ends up sending an empty HELO/EHLO command, which makes Gmail (and probably many other SMTP servers) really unhappy.

A possible solution would be to modify /var/www/html/modules/remote_smtp/libs/paloSantoEmailRelay.class.php on line 156:

if(!$smtp->Hello()){

change to:

if(!$smtp->Hello(getHostname())){

If you are using the Multi Tenant version the location is /usr/share/elastix/apps/remote_smtp/libs/paloSantoEmailRelay.class.php

Changed that and it worked. However, whenever I create a new organization and the email is sent to the "admin", I never receive anything... what could it be now? Any ideas? Thanks!

Yes, the number of people who are out there looking for "whatever is called Elastix" is way more than enough to keep the website and brand name around. Elastix has a huge presence in South America and in LATAM countries in general alone.

@matteo-nunziati said in Open Storage Operating Systems for SAM-SD:

what a mess...

Windows desktops are loaded with software that you are only limited as to how you can use it by EULA as well.

I doubt that they will be making any "visible" Linux products for some time, at the least.

@dafyre said:

Not yet... I still haven't even figured out what the default desktop is... (It feels like Gnome 3 to me).

Whta is the KDE Connect?

Here's what the notifications look like:

KDE Connect

@anonymous said:

Nice Guide. Can you please add a link to the Jumpbox guide, I missed it.....

http://mangolassi.it/topic/6143/linux-lab-project-building-a-linux-jump-box

I agree, this is a case where downloading the fully up to date version that CentOS provides is what makes sense. The overall version is 5. The .7 or .11 is just the patch level.

Decent guide for this from NIST:

http://csrc.nist.gov/publications/drafts/nistir-7966/nistir_7966_draft.pdf

@JaredBusch said in Linux Lab Project: Building a Linux Jump Box:

@scottalanmiller said in Linux Lab Project: Building a Linux Jump Box:

First you would create users and SSH keys and then deploy them to the other boxes that you wish to connect to. This is the core of what makes the Jump Box a Jump Box. This is standard SSH key setup, nothing unique to a Jump Box.

Did you ever make a good write up on creating users and SSH keys? If so, I cannot find it.

I mean, I know how to make and use keys in general. But detail here would be good.

Write up for creating the users on the jump box and getting their SSH keys. Write up for pushing users and keys to other systems that said jump box will be allowing access. Write up for control of said access. Bob and Jill have access to Jump Box. Bob has Access to servers 1 & 2. Jill has access to server 2 & 3.

I know that @scottalanmiller has mentioned in another thread that he has a script to push this all out (question 2). I can only assume that the script has some controls to tell you which server so shove the key and user logon to (question 3).

I thought that screen looked familiar, lol.

Only so shocking, Microsoft was making UNIX systems before they got into Windows. Xenix was the original Microsoft UNIX.