[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-390
Subject:    Re: Slightly OT: LVMing root file system & other Linux on z best practices (or not so best).....
From:       Scott Rohling <scott.rohling () gmail ! com>
Date:       2015-05-04 17:58:22
Message-ID: CAApr904iVYp-LLyweJXnRfrNf5ke1PQ2a8YkWYKxknyQC6nptA () mail ! gmail ! com
[Download RAW message or body]

Linux 'is' Linux on any platform...  the underlying hardware and potential
for advantageous use/setup are not.    I think you 'do' want your Nix guys
to see this as 'any other platform' ---    When you're talking about
supporting a very large number of servers - that's a 'good thing'.    When
it comes to architecture and setup of Linux on these platforms ---  you
still want anything you do differently to be as easy to deal with as you
can (arch specific packages, etc) so those poor Nix support folks don't
have to be platform experts.    (All IMHO of course)..

Root on LVM never phased me...   With the proper recovery process (bootable
'maintenance' Linux w/o LVM and access to other guest disks)  this
shouldn't be a major deterrent...   you want such a thing anyway.

z/VM support access depends on your separation of duties and how you staff
things..   'vmcp' and most of the s390-tools utilities require root
access...   There is always a need for root access by 'someone'...  and as
others have said - sudo is the standard retort to root access.

Sharing/RO stuff can be implemented on any platform...   though the methods
may differ.

I tend to underplay the differences -- as I think most subscribers do ?

Scott Rohling



On Mon, May 4, 2015 at 10:20 AM, Jason Space <
Jason.Space@fiscal.treasury.gov> wrote:

> Gee Mark,
> Thanks for being a voice of reason, with you're non-inflammatory rhetoric
> and separation of duties.  :-)   (That was sarcasm, in case it didn't come
> across the line that way.)
> I think I understand what you're saying, in that being VM sys prog why
> should you care how the zLinux is setup?  It's just the change in culture
> from when z/VM group did the initial setup and configuration of zLinux.
>
> To everyone else.
> I've tried to avoid the statement that "..Linux is Linux is Linux"
> regardless of the platform, as I think that is some of what cause this
> change in who does what.  My perception is our *NIX group doesn't see
> benefit of Linux on z and what to treat it like all the other *NIX's they
> maintain.  As mentioned, to them it is just another platform...but to
> complete the statement..."that they really don't want to deal with."  That
> means competing ideas on how to best advance & leverage zLinux as a viable
> platform.
>
> Concerning the shared binaries, I've not really entertained the idea of a
> read-only root.  Mostly, I've been pushing for 3rd party "/opt/var/
> packages" such as DB2, InfoSphere, MQ. etc...
>
> Thanks everyone though for commenting.
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to LISTSERV@VM.MARIST.EDU with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to LISTSERV@VM.MARIST.EDU with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
[prev in list] [next in list] [prev in thread] [next in thread]