@ryanov said:

Part of this is not correct. RHEL releases as often as not do not directly correspond to a specific Fedora release. I stumbled upon this myself when I tried to use Fedora packages in RHEL for some things (using packages for the same release of Fedora that the RHEL release was based on). Neither RHEL6 nor 7 was based on a single Fedora release:

https://access.redhat.com/articles/3078

True, they are starting to base it less closely now that Fedora has some additional testing that RHEL doesn't want to role in. SystemD is part of what caused this to change in RHEL 6. It's basically the same, still. Even if they based off of Fedora initially, it eventually skews as Fedora stops getting updates many, many years before RHEL does.

@bsouder said:

Pluralsight:
($50 monthly subscription - can turn off at any time - unlimited training for that month.)
http://www.pluralsight.com/search/?searchTerm=Linux

Linux Foundation:
(Online Classrooms)
http://training.linuxfoundation.org/linux-courses

Learnable:
Not sure how good this one is. I was going to check out some of their topics.
https://learnable.com/courses/a-beginner-s-guide-to-production-linux-49#overview

bsouder thank you for providing links on the educational part. I really need all I can get. I really do appreciate that!

@Rob-Dunn said:

@thanksaj

Yeah, all my experience has been with Windows DHCP, and you're right, configuring the DNS suffix and other options are easy as pie. On the pfSense/Linux side it's a bit...different...!

I don't have much experience with pfsense. I've played with it a little but never actually set it up and used it. YMMV

@coliver said:

"They don't have a very good business model what are you going to do when they fold?" Aggravating to say the least.

Since it's FOSS you can manage the project yourself, but every time a closed source company goes out of business, that code vanishes into thin air forever, leaving people behind. That's another thing people don't seem understand. Just because you paid for something, doesn't mean they'll support you when they fold, but if a FOSS company folds, at least you have the ability to fork the project and keep it going, especially from other users.

For example if Microsoft goes belly up Windows will die out, but if Linus Torvalds dies or Richard Stallman or anyone else like that, people will still crank out code for Linux, GNU projects, etc.

Did C support or implementation suddenly drop off after Dennis Ritchie died? Compare that to, say... ColdFusion or some other god awful garbage, those creators still curse the Earth and their products are dying.

@scottalanmiller said:

I don't know the spoon reference.

The Matrix...really?!

@scottalanmiller said:

@Dashrender said:

@scottalanmiller said:

Only as long as it takes you to get a new phone, which while possible expensive, really shouldn't be that long.

In theory. But when you are traveling, away from home or don't live near a big city that can be quite a challenge. When you are without a phone AND your are then cut off from your computer even hours can be pretty dramatic. It makes losing your phone go from an inconvenience (one form of communication down) to a big thing (all communication down.)

Granted.

That looks like an interesting tool, I need to check into that.

@coliver said:

Hasn't Linux always been able to do something like VSS?
Always? No. Before VSS? Yes. VSS is heavily based on Linux LVM. You have long (but not always) been able to take snapshots of the filesystem.

@MattSpeller said:

@scottalanmiller For sure, but I thought there was one to be integrated by MS... shrug

I think so, but sadly they aren't leading even in their own space here.

@Reid-Cooper wonderful

I had read about this a or another system in the last few months. it is an awesome downsizing of the technology.

It's always best practice to disable root login over SSH, especially from the Internet; use su or sudo for root access. Another good practice is to disable password-based authentication; only use keys with a passphrase. The setup you're doing here is useful for allowing scripted/automated connections between machines (e.g. for backups, scheduled tasks, etc) but they should be accounts with limited access, not root. You should be creating layers that make it difficult for someone to gain access to your systems; root keys with no passphrase means you're solely relying on that one strong password (which is one keylogger away from being defeated.)

@Rob-Dunn Yup, I hope it helps!

Linux and FreeBSD Map

The third one is "running Crouton in a window inside ChromeOS"

Also, when I update to 14.10, $4!+ goes haywire...