Well I figured it out in case anyone cares. The /etc/grub.conf wasn't being copied to the /boot/grub/grub.conf file. Not really sure why, but we have a password on grub so that might possibly be it. I didn't create this kickstart, so I'm not sure what post install junk is happening that might limit this also.

This makes me want to get an RP3 just to run this and try it out.

I first heard about tmux here at ML. I've gotten to where I like it better than screen most of the time.

You all know what sh-bang really is....

Youtube Video

@travisdh1 said in Introducing Gnome Maps:

@scottalanmiller said in Introducing Gnome Maps:

@travisdh1 said in Introducing Gnome Maps:

@coliver said in Introducing Gnome Maps:

@StrongBad said in Introducing Gnome Maps:

@travisdh1 I agree, not very impressed that Mint included this but did not test it or respond to people with issues. Better to not have it in there.

Do you have the Cinnamon or Mate Desktop? It would make sense that you couldn't run a Gnome application without running in a Gnome environment. Although I could be mistaken.

Just because you run a different GUI doesn't mean you can't run apps meant for a different one. KDE and GNOME apps normally run just fine in the other type of desktop assuming all dependencies are met.

Cinnamon is Gnome 3, though.

Hrm, just gets worse and worse.

Yeah, I'd expect @StrongBad to have good luck here. I see the same thing, doesn't run.

Could it be going into the nonfree repository and getting a separate license agreement to accept? Canonical made Ubuntu a household name by including other things like this. Anyone else remember having to mess with codecs?

@Kelly said:

@PSX_Defector said:

@Kelly said:

I've also been looking at PowerBroker Identity Services from BeyondTrust. It is where Likewise ended up after a series of acquisitions. It looks like I'm going to have to be building a virtual network and trying some of this.

I've used this in multiple companies, from an airline in America to an oil exploration company.

Works like a champ, it's built on Winbind, but now has actual support versus calling RedHat and hoping for the best.

Did you use PBIS Open or the paid version? The paid version is significantly more than I can afford at about $1,600 per server instance.

This was back in the Likewise days. So free.99.

For those who were still having problems getting Mattermost running on CentOS 7, I was also having the same problems and couldn't get beyond the postgres install. I found another guide and with a few tweaks, I was able to get this running.

https://www.howtoforge.com/tutorial/install-mattermost-with-postgresql-and-nginx-on-centos7/

The change that was required from this guide was in the "Download and Extract Mattermost"

Instead of...
[root@mattermost ~]# wget -q "https://github.com/mattermost/platform/releases/download/v2.0.0/mattermost.tar.gz" -O mattermost.tar.gz

Use this...
wget https://releases.mattermost.com/3.3.0/mattermost-team-3.3.0-linux-amd64.tar.gz

Then in the next block, instead of...
tar -xvzf mattermost.tar.gz

Use this...
tar -xvzf mattermost-team-3.3.0-linux-amd64.tar.gz

After that, follow the guide to the letter and it will get you to this...
0_1473265786807_upload-d89fe07b-7d71-4d39-8dd7-e00395f6aa84

@aaronxiang @wirestyle22 @scottalanmiller

Some other pluses for this are easy setup for HBAC, Sudo and sudo command priveleges (host based and user based), SELinux user maps, and easier password policy management.

The "working data" that I mentioned that scrolls by quickly before our summary chart appears from this example looks like the below output. Generally we can ignore this, but it can be useful should there be an error to see where something has gone wrong.

$ yum update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirrors.lga7.us.voxel.net * epel: mirror.cs.princeton.edu * extras: mirror.lug.udel.edu * updates: mirror.trouble-free.net Resolving Dependencies --> Running transaction check ---> Package NetworkManager.x86_64 1:1.0.0-16.git20150121.b4ea599c.el7_1 will be updated ---> Package NetworkManager.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-adsl.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-adsl.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-bluetooth.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-bluetooth.x86_64 1:1.0.6-29.el7_2 will be an update --> Processing Dependency: libbluetooth.so.3()(64bit) for package: 1:NetworkManager-bluetooth-1.0.6-29.el7_2.x86_64 ---> Package NetworkManager-glib.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-glib.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-libnm.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-libnm.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-team.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-team.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-tui.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-tui.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-wifi.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-wifi.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-wwan.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-wwan.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package avahi.x86_64 0:0.6.31-14.el7 will be updated ---> Package avahi.x86_64 0:0.6.31-15.el7 will be updated ---> Package avahi.x86_64 0:0.6.31-15.el7_2.1 will be an update ---> Package avahi-autoipd.x86_64 0:0.6.31-15.el7 will be updated ---> Package avahi-autoipd.x86_64 0:0.6.31-15.el7_2.1 will be an update ---> Package avahi-libs.x86_64 0:0.6.31-15.el7 will be updated ---> Package avahi-libs.x86_64 0:0.6.31-15.el7_2.1 will be an update ---> Package bind-libs.x86_64 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-libs.x86_64 32:9.9.4-29.el7_2.3 will be an update ---> Package bind-libs-lite.x86_64 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-libs-lite.x86_64 32:9.9.4-29.el7_2.3 will be an update ---> Package bind-license.noarch 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-license.noarch 32:9.9.4-29.el7_2.3 will be an update ---> Package bind-utils.x86_64 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-utils.x86_64 32:9.9.4-29.el7_2.3 will be an update ---> Package ca-certificates.noarch 0:2015.2.4-71.el7 will be updated ---> Package ca-certificates.noarch 0:2015.2.6-70.1.el7_2 will be an update ---> Package coreutils.x86_64 0:8.22-12.el7_1.2 will be updated ---> Package coreutils.x86_64 0:8.22-15.el7 will be updated ---> Package coreutils.x86_64 0:8.22-15.el7_2.1 will be an update ---> Package cronie.x86_64 0:1.4.11-13.el7 will be updated ---> Package cronie.x86_64 0:1.4.11-14.el7 will be updated ---> Package cronie.x86_64 0:1.4.11-14.el7_2.1 will be an update ---> Package cronie-anacron.x86_64 0:1.4.11-14.el7 will be updated ---> Package cronie-anacron.x86_64 0:1.4.11-14.el7_2.1 will be an update ---> Package cyrus-sasl-lib.x86_64 0:2.1.26-19.2.el7 will be updated ---> Package cyrus-sasl-lib.x86_64 0:2.1.26-20.el7_2 will be an update ---> Package device-mapper.x86_64 7:1.02.107-5.el7 will be updated ---> Package device-mapper.x86_64 7:1.02.107-5.el7_2.1 will be an update ---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7 will be updated ---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7_2.1 will be an update ---> Package filebeat.x86_64 0:1.1.0-1 will be updated ---> Package filebeat.x86_64 0:1.2.1-1 will be an update ---> Package glibc.x86_64 0:2.17-106.el7_2.1 will be updated ---> Package glibc.x86_64 0:2.17-106.el7_2.4 will be an update ---> Package glibc-common.x86_64 0:2.17-106.el7_2.1 will be updated ---> Package glibc-common.x86_64 0:2.17-106.el7_2.4 will be an update ---> Package htop.x86_64 0:1.0.3-3.el7 will be updated ---> Package htop.x86_64 0:2.0.1-1.el7 will be an update ---> Package initscripts.x86_64 0:9.49.24-1.el7 will be updated ---> Package initscripts.x86_64 0:9.49.30-1.el7 will be updated ---> Package initscripts.x86_64 0:9.49.30-1.el7_2.2 will be an update ---> Package kernel.x86_64 0:3.10.0-327.13.1.el7 will be installed ---> Package kernel-tools.x86_64 0:3.10.0-327.4.5.el7 will be updated ---> Package kernel-tools.x86_64 0:3.10.0-327.13.1.el7 will be an update ---> Package kernel-tools-libs.x86_64 0:3.10.0-327.4.5.el7 will be updated ---> Package kernel-tools-libs.x86_64 0:3.10.0-327.13.1.el7 will be an update ---> Package kexec-tools.x86_64 0:2.0.7-19.el7_1.2 will be updated ---> Package kexec-tools.x86_64 0:2.0.7-38.el7 will be updated ---> Package kexec-tools.x86_64 0:2.0.7-38.el7_2.1 will be an update ---> Package kpartx.x86_64 0:0.4.9-85.el7 will be updated ---> Package kpartx.x86_64 0:0.4.9-85.el7_2.1 will be an update ---> Package krb5-libs.x86_64 0:1.13.2-10.el7 will be updated ---> Package krb5-libs.x86_64 0:1.13.2-12.el7_2 will be an update ---> Package libblkid.x86_64 0:2.23.2-26.el7 will be updated ---> Package libblkid.x86_64 0:2.23.2-26.el7_2.2 will be an update ---> Package libgudev1.x86_64 0:219-19.el7 will be updated ---> Package libgudev1.x86_64 0:219-19.el7_2.7 will be an update ---> Package libmount.x86_64 0:2.23.2-26.el7 will be updated ---> Package libmount.x86_64 0:2.23.2-26.el7_2.2 will be an update ---> Package libssh2.x86_64 0:1.4.3-10.el7 will be updated ---> Package libssh2.x86_64 0:1.4.3-10.el7_2.1 will be an update ---> Package libteam.x86_64 0:1.17-5.el7 will be updated ---> Package libteam.x86_64 0:1.17-6.el7_2 will be an update ---> Package libuuid.x86_64 0:2.23.2-26.el7 will be updated ---> Package libuuid.x86_64 0:2.23.2-26.el7_2.2 will be an update ---> Package mariadb-libs.x86_64 1:5.5.44-2.el7.centos will be updated ---> Package mariadb-libs.x86_64 1:5.5.47-1.el7_2 will be an update ---> Package nss-util.x86_64 0:3.19.1-4.el7_1 will be updated ---> Package nss-util.x86_64 0:3.19.1-9.el7_2 will be an update ---> Package numactl-libs.x86_64 0:2.0.9-5.el7_1 will be updated ---> Package numactl-libs.x86_64 0:2.0.9-6.el7_2 will be an update ---> Package openldap.x86_64 0:2.4.40-8.el7 will be updated ---> Package openldap.x86_64 0:2.4.40-9.el7_2 will be an update ---> Package openssh.x86_64 0:6.6.1p1-23.el7_2 will be updated ---> Package openssh.x86_64 0:6.6.1p1-25.el7_2 will be an update ---> Package openssh-clients.x86_64 0:6.6.1p1-23.el7_2 will be updated ---> Package openssh-clients.x86_64 0:6.6.1p1-25.el7_2 will be an update ---> Package openssh-server.x86_64 0:6.6.1p1-12.el7_1 will be updated ---> Package openssh-server.x86_64 0:6.6.1p1-25.el7_2 will be an update ---> Package openssl.x86_64 1:1.0.1e-51.el7_2.2 will be updated ---> Package openssl.x86_64 1:1.0.1e-51.el7_2.4 will be an update ---> Package openssl-libs.x86_64 1:1.0.1e-51.el7_2.2 will be updated ---> Package openssl-libs.x86_64 1:1.0.1e-51.el7_2.4 will be an update ---> Package polkit.x86_64 0:0.112-5.el7 will be updated ---> Package polkit.x86_64 0:0.112-6.el7_2 will be an update ---> Package procps-ng.x86_64 0:3.3.10-3.el7 will be updated ---> Package procps-ng.x86_64 0:3.3.10-5.el7_2 will be an update ---> Package python-boto.noarch 0:2.38.0-2.el7 will be obsoleted ---> Package python-perf.x86_64 0:3.10.0-327.4.5.el7 will be updated ---> Package python-perf.x86_64 0:3.10.0-327.13.1.el7 will be an update ---> Package python-pyudev.noarch 0:0.15-7.el7 will be updated ---> Package python-pyudev.noarch 0:0.15-7.el7_2.1 will be an update ---> Package python2-boto.noarch 0:2.39.0-1.el7 will be obsoleting ---> Package screen.x86_64 0:4.1.0-0.19.20120314git3c2946.el7 will be updated ---> Package screen.x86_64 0:4.1.0-0.23.20120314git3c2946.el7_2 will be an update ---> Package selinux-policy.noarch 0:3.13.1-60.el7 will be updated ---> Package selinux-policy.noarch 0:3.13.1-60.el7_2.3 will be an update ---> Package selinux-policy-targeted.noarch 0:3.13.1-23.el7_1.21 will be updated ---> Package selinux-policy-targeted.noarch 0:3.13.1-60.el7_2.3 will be an update ---> Package sudo.x86_64 0:1.8.6p7-16.el7 will be updated ---> Package sudo.x86_64 0:1.8.6p7-17.el7_2 will be an update ---> Package systemd.x86_64 0:208-20.el7_1.6 will be updated ---> Package systemd.x86_64 0:219-19.el7 will be updated ---> Package systemd.x86_64 0:219-19.el7_2.7 will be an update ---> Package systemd-libs.x86_64 0:219-19.el7 will be updated ---> Package systemd-libs.x86_64 0:219-19.el7_2.7 will be an update ---> Package systemd-python.x86_64 0:219-19.el7 will be updated ---> Package systemd-python.x86_64 0:219-19.el7_2.7 will be an update ---> Package systemd-sysv.x86_64 0:219-19.el7 will be updated ---> Package systemd-sysv.x86_64 0:219-19.el7_2.7 will be an update ---> Package teamd.x86_64 0:1.17-5.el7 will be updated ---> Package teamd.x86_64 0:1.17-6.el7_2 will be an update ---> Package topbeat.x86_64 0:1.1.0-1 will be updated ---> Package topbeat.x86_64 0:1.2.1-1 will be an update ---> Package tuned.noarch 0:2.4.1-1.el7 will be updated ---> Package tuned.noarch 0:2.5.1-4.el7_2.1 will be updated ---> Package tuned.noarch 0:2.5.1-4.el7_2.3 will be an update ---> Package tzdata.noarch 0:2015g-1.el7 will be updated ---> Package tzdata.noarch 0:2016c-1.el7 will be an update ---> Package util-linux.x86_64 0:2.23.2-26.el7 will be updated ---> Package util-linux.x86_64 0:2.23.2-26.el7_2.2 will be an update --> Running transaction check ---> Package bluez-libs.x86_64 0:5.23-4.el7 will be installed --> Finished Dependency Resolution --> Running transaction check ---> Package kernel.x86_64 0:3.10.0-229.7.2.el7 will be erased ---> Package kernel.x86_64 0:3.10.0-229.11.1.el7 will be erased --> Finished Dependency Resolution Dependencies Resolved

@travisdh1 said:

@johnhooks The difference is 6 compared to a half dozen (at least in this case.)

I used to know a reason why you would use less or more in certain cases, but it's been so long that I no longer remember what caused a difference.

I know of no case where you use more. I always used it because I learned it first, but less is the only one you would actually want to use.

I use it very little but have the odd task that I use it for. It's difficult to pop into a one liner so I try to use other tools when possible.

That's a good question... when does chrooting make more sense than containers today?

Storage is one. Lots of people use chroot jails for storage purposes. Containers are heavier than chrooting which has effectively no impact on any resources.

@dafyre said:

@johnhooks said:

@scottalanmiller said:

@johnhooks said:

@dafyre said:

Why are there two NFS servers to start with? (Just curious)

They're only 20-24 drives each. About 50TB per server. All of the engineer's home folders are on them so one isn't enough.

At some point down the road we are going to implement a clustered storage but we just don't have the time right now because of time constraints for this project.

Gluster could be done in an hour. I have how tos posted for both NFS Home Automounting and Gluster 🙂

Ha yes anywhere else it would take no time at all. We have so much red tape to jump through it's ridiculous.

Start setting up and testing a Gluster Cluster (see what I did there?)... and maybe by the time you get it set up and tested, you'll be done playing jump rope with the red tape.

The other issue is the NFS servers we have right now are applicances (was done before I got here I've only been here less than a month). We can install certain things, but too much and we might lose "support."

We have to have these inspectors come in and approve stuff if any changes are made to this network. It's ridiculous.

@scottalanmiller said:

@johnhooks said:

How secure is running a DE in the Dom0 though?

Are they running it there?

Ya.

Dom0 is sort of a system domain separate from the default domains and any other domains you create. The desktop manager runs in this domain. Your login credentials reside there. Much like a super domain, Dom0 is more trusted than any other domain.

It provides just two functions: It runs the window manager and the desktop manager.

Do they support booting from UEFI yet?