Thanks for the info. I'm going to discuss this further with management. >>> On Fri, Aug 15, 2008 at 11:01 AM, in message <[EMAIL PROTECTED]>, Mark Post <[EMAIL PROTECTED]> wrote: >>>> On 8/15/2008 at 7:29 AM, in message <[EMAIL PROTECTED]>, > Ryan McCain <[EMAIL PROTECTED]> wrote: > -snip- >> It has at least one advantage for us. We are given very limited space to >> allocate for each guest. This method allows for the rapid installation of >> either single application/patch or mass deployment/upgrade via ZLM without >> having to guesstimate ahead of time that /opt will be 1.1 gig, /tmp will be >> 500 meg, etc. Using my example, if we need to grow /opt to 1.5 gig, we > would >> then have to shuffle sizes of other filesystems around. Would you agree or > >> am I missing something? > > That's not an advantage, it's a workaround for bad management decisions. > Coming to Novell from a company where our z/VM systems were overly resource > constrained, I completely understand your situation. The best you can do is > "do what you have to do" and document for management the potential risks and > business impact of their decision to not provide the necessary hardware > resources to do things the "right" way (understanding there is debate about > what "right" is). Then, if Murphy strikes, and people are asking why you did > things that way, you have covered yourself and your team as much as you can. > > If I were put (back) in your position, I wouild try to do some research > ahead of time to figure out what set of standardized system templates I might > be creating, and adjust the file system layout I favor to support those. > Just about everyone I've spoken to has done just that, whether / is on an LV > or not, and gotten those templates approved by security, etc. You don't want > every system you create to be a "one off" situation. That won't be to your > advantage in any way. In general, you shouldn't be having to install lots of > new packages, just maintenance, for the life of a particular guest. If you > are, then something in your ogranizational or development processes are > broken. > > > Mark Post > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
