/proc/version usually has pertinent information across most systems.

Edit: I looked closer. It's just the OS name (RHEL/Ubuntu) and kernel version. Never mind.

@ntozier said in HPE Sells OpenStack and Cloud Foundry Business to Suse:

HP seems to be selling off a lot of stuff recently...

Definitely trimming the fat if nothing else.

@NerdyDad said in Suse Enterprise Linux for the Raspberry Pi:

I'm seeing it as a good entry level device to finally learn Linux Server administration at an affordable device. Granted the hardware isn't something that you're normally going to normally see in an enterprise environment, it would give me nearly identical experience managing a linux server in an enterprise environment.

The hardware doesn't matter at all. Like SAM suggested, go for a VM. There's no difference.

There are actually pitfalls in using a Pi, for example there isn't any RTC (realtime clock and battery). This can give you very weird results during reboots because next to no application expects a filetime to go backwards, which can happen without a working clock (depends on timing, network availability during reboot, working fake-hwclock package etc).

@dafyre said in OpenSuse Leap 42.2 Hits Beta:

I played with the first OpenSuse Leap release. It was pretty cool. My only OpenSuse server at the moment is a web server and it runs Tumbleweed.

Yup, I worked with it too, it's a great product.

@KOOLER "do guy" = "do gui" LOL

@momurda said in Building a Basic DRBD Cluster on OpenSuse 12.2:

What is the purpose of 'zypper -remove patterns-openSUSE-minimal_base'
I know what it does, but is it necessary? Does this minimal_base package prevent you from installing certain packages at a later date? Or you just making things nice n neat?

It's been quite some time, but if I remember correctly it interfered with some packages that we needed as the "minimal" blocked adding a bunch of stuff.

@DustinB3403 said in Linux: Checking Filesystem Usage with df:

Will there be a topic on "managing inode in linux"

Yes, but it is going to go into an "Advanced Topics" section. Just as LVM and MD will have high level "normal" admin sections and eventually delve much deeper in advanced sections. I want to cover everything in a "normal admin" capacity like you would learn from the RHCE up front. Then go back and cover the nitty gritty details that other admin books don't. So it will basically take two passes but the hope is that the first pass will take you from "starting point" to "competent Linux Admin" then the second part will go where normal admin guides don't tread.

It doesn't update as "new" when I just update the list. Only if I comment on the thread.

I don't know why others don't follow with this. I'm sure there are reasons I can't see, but it just seems easier with a rolling release like Arch or Tumbleweed.

They can still snapshot at a point in time to create the LTS release. Maybe it's more work on their part since with a rolling release there can be so many packages that change rather quickly?

I know it's almost enough of a pain to do the upgrade from release to release sometimes to make me consider just wiping and starting over (I usually do that with my laptop and Fedora since home is on a separate drive).

It is not uncommon to only have servers approved to access the storage listed. So many shops will go in and add a server one by one to enable access. If your servers almost never change, this works pretty well and is extremely secure. You can do this in the firewall too, for even more security. But if you are using DevOps and creating and destroying VMs regularly you will want to automate this in some fashion.