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.

Fonts should never come as an .exe - if they do run away.

They come as native font files, you then install them based on the OS, either Mac or Windows does this easily

thanks, fixed.

Very nice.

@LAH3385 said:

@scottalanmiller said:

@LAH3385 said:

Let's not get too technical.. My real question is the ability to expand/shrink on the fly/VM stay online. I know for a fact that Gen1 cannot do that.. thus the question about conversion.

But do you have teh space for two copies during the operation? That's a key piece of why it is important.

Good question... we are 60% of the disk at the moment... so that would be no. The space inside VM it self is 50% full.. Say 2TB disk space on hypervisor. the VM is uing 1.2TB. But the OS/Files is using only 600GB out of 1.2TB.
If the cloning means 100% identical then I will not have enough space. But if there is a way to shrink while cloning then it is a viable option.

This also means you're using thick provisioning.

Perhaps you can copy the current VM disk to another VM disk, but one that is thin provisioned. Then it will only take up 600 GB on the disk, leaving you with 2 GB free space until you delete the old VM disk.

@coliver said:

@scottalanmiller said:

@coliver said:

We've been expansionist for a long time. The war of 1812 was the result in part of US Expansion.

Are you sure? The Second War of Independence was a defensive war. We had the population being taken for slaves, that wasn't going to stand (strangely.)

I always thought that was small part of it. The bigger parts, from my reading, was the US expansion westward, which resulted in fighting from British supported Native American tribes, and the trade embargoes setup by the British Empire on US interests in Europe.

Hard to say 201 years later, but that always seems to have been a very minor factor.

@Dashrender said:

@scottalanmiller said:

@Dashrender said:

Though MS I'm sure has been gun shy to include these types of services for fear of being called a monopoly like in the 90's.

Quality does not get them in trouble for anti-trust.

No, including options so no other options are needed does - i.e. IE. How does including a PDF reader not make them act just like they were when IE was bundled in (oh I mean like now :P) Notice how they aren't gunshy anymore... they now have a built in PDF reader.

The bit we were discussing was the need for one to be locked down while the other does not.

@BBigford It does everything automatically, via GPO, not really one at a time. LAPS prevents each local admin from having the same password. Obviously, if you want everything to be the same then you wouldn't want to use it.

EDIT: You can still use the bat file (mentioned above) if you want to create a specific user with a specific password and assign it to the local admins group. Keep in mind that it is plain text, as was the method you were previously using.

@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.

With all of the tack on options.. E3 really is where MS wants everyone. ug!

@scottalanmiller
None of that was covered, though. No amount of Windows, AD or SMB covers that. Only NTFS ACLs provide that. You can do with with actual NTFS or you can do it with Linux VFS and an NTFS ACL layer. Either way, works the same. But the only device that can give you ACLs is the device providing SMB. So the Synology NAS in the example.

Understood! Thank you sir.

Finally decided what to use. Going to have my dad setup Flickr albums for his project.

Latency ranges from <1ms to 4ms, each way.

Most of this "wrong usage" of my e-mail comes into play with my Clutter (a feature which I like) and Junk folders.

Just a quick (even quicker) look through them to make sure nothing important filtered in.

@scottalanmiller said:

@s.hackleman said:

I played with x10 equipment back in the day and it worked for me. I haven't used the cameras, but you can setup a motion sensor outside that turns on a light inside, and even turn on a few a few seconds appart like someone is moving through the house. It was reliable, affordable, and kinda fun to setup.

How very "Home Alone" of you 🙂

We had all of our network gear in our College apartment on a trigger with a switch at everyones desk. That way we could reboot the 802.11b router every 2 hours with out standing up. 😉

@Jason said:

@axigen said:

@Jason said:

Comodo provides them

Hi @Jason. Thanks for your note. I do not seem to see how I can get one for free. I am browsing their site and see that in the Free SSL section they only appear to provide 90 days 'free' for SSL certificates, no mention of S/MIME anywhere...

https://secure.instantssl.com/products/frontpage?area=SecureEmailCertificate&currency=USD&region=North+America&country=US

Really curious about how you found that 😉 on their website.

@travisdh1 said:

@dafyre said:

Assembly programs give me nightmares, lol.

I had an assembly language class in college. While I don't really enjoy it, I very much appreciate someone who does. Just... not.... this. It's a itty bitty little package of evil.

This isn't meant to be offensive, but I've never met anyone who liked Assembly who was not at least border-line autistic. I think it's because it takes a certain type of mind or memory in order to deal with in an extended way and enjoy it. I can deal with it, but I don't really enjoy it. For smaller programs I'd rather use C and strip everything down... still won't be as small, but certainly better than any extra high level language.

@mlnews said:

And this is the current site for the project...

https://github.com/Pash-Project/Pash

I love it when people port garbage to other platforms

It's all racked, I hear. Can't wait till we get it all fired up!

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