Re: Cloning & SSH keys

[RPN01]

Only if your post-cloning process does not include generating new RSA keys.
It's all in how you set up your cloning process, and the planning you've put
into it.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 7/16/12 10:03 AM, "Lee Stewart"  wrote:

> I'd never thought about it before, but a customer pointed out that when
> you clone a system, each Linux clone has the same Host RSA key
> fingerprint as it's master.   I can't think of anything that would cause
> a problem with.  On the other hand, if they wanted to regenerate the
> keys, does it take more than erasing the current keys and restarting sshd?
>
> Any thoughts?
> Lee
> --

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: LGR & IPL CMS

[RPN01]

The coolest thing here is that we have Linux images running that have been
up much longer than the z/VM systems they are running on. We're rolling new
hardware underneath some more this weekend... Without taking them down.

Thanks to everyone at IBM that has made this possible, and to everyone
involved with VM since back in the 60's. It's still a wonderful system.

-- 
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 6/14/12 8:18 AM, "Scott Rohling"  wrote:

> Yep - it was one of the more memorable moments in my working with VM almost
> 30 years...  feels a little magical when you get it to work :)Only way
> I could tell on the Linux guest was 'vmcp q user' ..
> 
> Glad you got a chance to see it yourself!
> 
> Scott Rohling
> 
> On Thu, Jun 14, 2012 at 6:08 AM, Mark Pace  wrote:
> 
>> Detaching all the minidisks was the answer to my problem.
>> 
>> I must say it is pretty amazing the 1st time that LGR works.  You know that
>> it should work, but actually seeing it happen the 1st time is pretty cool.
>> 
>> On Wed, Jun 13, 2012 at 2:23 PM, Robert J Brenneman >> wrote:
>> 
>>> I relocate my Linux systems and I IPL CMS by default so I can use
>>> SWAPGEN too - what is the actual error message you're getting when you
>>> attempt to relocate ?
>>> 
>>> --
>>> Jay Brenneman
>>> 
>>> --
>>> For LINUX-390 subscribe / signoff / archive access instructions,
>>> send email to lists...@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/
>>> 
>> 
>> 
>> 
>> --
>> The postings on this site are my own and don¹t necessarily represent
>> Mainline¹s positions or opinions
>> 
>> Mark D Pace
>> Senior Systems Engineer
>> Mainline Information Systems
>> 
>> --
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@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 lists...@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 lists...@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/

Re: LGR & IPL CMS

[RPN01]

Go ahead and IPL CMS the way you always have, but once you're in Linux, use
vmcp to drop the CMS disks, so that LGR will work when needed.
Alternatively, just use "FOR guest CMD DET 190", etc. just before you
migrate the guest (this is what I do). Either way works, and allows you to
do the migration without any problems.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 6/13/12 12:59 PM, "Mark Pace"  wrote:

> Currently all of my linux guests IPL CMS to create VDISK swap disks and
> signatures.  For a linux to work with LGR it must IPL from a device or NSS
> so no CMS if I want to LGR.  I've been doing it this way for so long I'm
> unsure of how I would create the swap signature in my VDISKs without IPLing
> CMS first.
>
> Suggestions would greatly be appreciated.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: RES: Emergency

[RPN01]

I'm assuming that the disks that were scratched were the ones on the "old"
side of the migration, and without useful backups, I'd have to say that
you're probably out of luck at this point. I would have thought that there'd
have been several points in this process where the system pointed out to the
Systems Programmer that he was aiming the gun directly at his foot, long
before he pulled the trigger. ("This device is mounted, do you really want
to do this?" type messages...) Then again, I can also see how I could
"trick" the system into doing it, via some ill-advised MW links, so

You needed to check your backups before you ever mounted the first disk to
begin the migration. Always have a verified plan for failure before
beginning any potentially dangerous project.

At this point, recreate the system on the new disks and see what people can
recover / recreate their files and work, and hope for the best. Fire the
people who told you they were backing up your system. Learn from the
experience to always test your backups and recovery procedures periodically.

Sadly, all the cards were stacked against you.

Having said all this, I managed to write over our zOS DB2 data this last
summer during a disk migration. (But the zLinux data was all safe and
protected... :) You really have to check what you're about to do several
times before actually doing it, and even then, crossing your fingers doesn't
hurt.

-- 
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 3/19/12 3:26 PM, "Helio Mario Neves Pimentel de Oliveira"
 wrote:

> Yes 7 disks.
> I don´t how far the formatting exec went, before the machine hanging.
> 
> Sadly to say, but my reality is that the back-up (which was made in a
> separate x86 machine) was neglected by the people in charge.
> All this happened during the storage migration SHARK to DS8000.
> 
> Yes we built a second Linux. But the LVM / partition were not recognized.
> Only the disk not managed by the LVM could be mounted.
> 
> Helio Mario
> 
> -Mensagem original-
> De: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] Em nome de RPN01
> Enviada em: segunda-feira, 19 de março de 2012 16:40
> Para: LINUX-390@VM.MARIST.EDU
> Assunto: Re: Emergency
> 
> So, you have seven disks involved. Which disk(s) were formatted?
> 
> Key question: Do you have any sort of backups of the disks, and at what
> level? (File level or device level) How old are they?
> 
> How active were (i.e. How much updating was there on) the disks?
> 
> Do you have a second Linux image on which you could mount the disks and
> assess the damage?

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: Emergency

[RPN01]

So, you have seven disks involved. Which disk(s) were formatted?

Key question: Do you have any sort of backups of the disks, and at what
level? (File level or device level) How old are they?

How active were (i.e. How much updating was there on) the disks?

Do you have a second Linux image on which you could mount the disks and
assess the damage?

-- 
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 3/19/12 2:14 PM, "Helio Mario Neves Pimentel de Oliveira"
 wrote:

> Hi Mark and all listers,
> 
> We are in a great trouble.
> A guy of our tech team inadvertently submitted a job to 'format' the disk.
> So, there was a SUBSTANTIAL & CRITIC DATA LOSS.
> 
> Scenario:
> z10
> Suse 10 SP4
> 1 disk for the OS
> 2 LVMs with 3 disks each
> Address 0.0.E000 a 0.0.E006
> 
> What was submitted via YAST:
> - activate DASD
> - format DASD
> 
> During this process this LPAR (named LINUX2) stopped / hanged.
> No more jobs were processed in this machine.
> 
> Is there a way to rebuilt the "file system"?
> We´ve been searching for some utility to recover.
> 
> Do you have any suggestion / experience on such problem?
> 
> Thanks in advance ... and my great hopes of someone blessed to have a path
> to our salvation ...
> 
> Helio Mario - Brasil
> 
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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/

Re: Are your Linux instances healthy?

[RPN01]

It called out three exceptions, two of which that I thought were a bit odd,
all rated medium.

The first is that it found no driver for device 0.0.0009. Since my console,
though disconnected, is working just fine, I have to assume that there is
some driver active to it, so I'm not sure what the complaint is. Output is
here:

css_ccw_no_driver .. syspzl01.mayo.edu
EXCEPTION-MED

 >EXCEPTION css_ccw_no_driver.no_driver(medium)

  SUMMARY
One  or  more  I/O  devices  are not associated with a device
driver: 0.0.0009

  EXPLANATION
One or more I/O devices cannot be used properly because  they
not associated

with a device driver.

Possible  reasons  for this problem are that the required de-
vice driver module

has been unloaded, that an existing association  between  the
device and the

device  driver  has  been  removed, or that the device is not
supported.

The following I/O devices are not associated  with  a  device
driver:

BUS ID   DevType   CU Type
0.0.0009 /00   3215/00

I'm sure that any of the suggested solutions would cause problems with the
system.

The second is that my eth0 doesn't have the expected number of buffers. I
could buy that, but the thing it's comparing to is "n/a", so I'm not sure
where it is getting its information. Output follows:

 >EXCEPTION net_qeth_buffercount.inefficient_buffercount(medium)

  SUMMARY
These  network  interfaces do not have the expected number of
buffers: eth0

  EXPLANATION
The number of buffers of one or more network  interfaces  di-
verts  from  the  specified rule. The most suitable number of
buffers for a particular interface depends on  the  available
memory. To allow for memory constraints, many Linux distribu-
tions use a small number of buffers by default. On Linux  in-
stances with ample memory and a high traffic volume, this can
lead to performance  degradation,  as  incoming  packets  are
dropped and have to be resent by the originator.

For  the current main memory, 1.96 GB, interfaces should have
64 buffers.

The following interfaces have a different number of buffers:

NetworkCurrent  Recommended
Interface  Buffer Count Buffer Count
eth0   n/a  64

I'm fairly sure I have buffers, since I'm signed in to the system via ssh
over eth0. In fact, following the path given in the command output, I was
able to cat out the buffer_count "file" and the value is 16. This would be a
much more useful value than "n/a", above. This is the default value given by
the system, as we haven't made any effort to change it.

The third exception is about having ttys defined, without having programs
running to talk to them. I buy this one. I'm not sure why the zLinux images
define tty devices, when there are no interfaces for these to talk to. They
just waste memory and never get used, as far as I know.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 3/16/12 6:43 AM, "Hendrik Brueckner" 
wrote:

> Today the first release of the Linux Health Checker 1.0 is made available - an
> exciting new tool.
>
> The Linux Health Checker (lnxhc) identifies potential weaknesses in the Linux
> configuration before they impact your system's availability or cause outages.
>
> To try it out, visit:
>
> http://lnxhc.sourceforge.net/
>
> With it comes a Health Checker User's Guide. It explains the new framework,
> how to install the tool and get started, how to run the health checks.
>
>
> Get your Linux instances healthy with the Linux Health Checker!
> --
> Hendrik Brueckner
> brueck...@linux.vnet.ibm.com  | IBM Deutschland Research & Development
> GmbH
> Linux on System z Development | Schoenaicher Str. 220, 71032 Boeblingen
>
>
> IBM Deutschland Research & Development GmbH
> Vorsitzender des Aufsichtsrats: Martina Koederitz
> Geschaeftsfuehrung: Dirk Wittkopp
> Sitz der Gesellschaft: Boeblingen
> Registergericht: Amtsgericht Stuttgart, HRB 243294
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wl

Re: RedHat or Suse?

[RPN01]

We recently completed moving from SuSE to RedHat on the mainframe, to bring
the environment in-line with our Intel environment. This gave us one vendor
to deal with, and one common interface. (And, one common set of problems.)

We don't have to train people to do things one way with some systems, and a
different way with others. Maintenance was a nightmare because it was so
different between the two environments. Setting up new systems was
different. It was really like supporting two different operating systems.

Consolidating to a single distribution across all platforms saved us huge
amounts of time in terms of training and debugging.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 2/27/12 8:25 AM, "Dazzo, Matt"  wrote:

> We have zvm with Redhat 5.6 in a test environment only. Redhat was originally
> selected as we have some Redhat intel servers in production and the thinking
> was keep it Redhat should we ever migrate from Intel over to zvm/linux. Not
> sure that will ever happen but we are confident that another application will
> come up in the future and it will go on zvm/Linux.
>
> Sorry for the long intro but wanted to describe the environment a little.
> Basically what flavor is better on zvm? Redhat or Suse? Maybe a better
> question is what are the differences? Any opinions or info is appreciated.
>
> Thanks Matt
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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/

Re: LVM mount points

[RPN01]

The naming is not an issue if your recovery system has been built with a
different naming "standard" in place that doesn't match the clones.

Having the root filesystem as an LVM makes life much simpler should a time
come when you need to extend its size. LVM has given us some flexibility
here that I wouldn't want to give up, and handling all our filesystems the
same way has its benefits.

Also, in future releases of RedHat, I expect to see LVM become more of a
standard, as the requirement that the boot partition not be managed by LVM
is removed.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 2/23/12 3:29 PM, "David Boyes"  wrote:


> This is what we recommend as well. Note also here that / is NOT a LVM.
>
> If/when something chokes, it's a lot easier to fix stuff if you don't need to
> get LVM working for the root first, especially if you clone systems from a
> template and all the LVM groups have the same names in all the machines.
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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/

Re: LVM mount points

[RPN01]

We set our systems up as follows:

ts00086@rpndvm01 ~ $ df -h
FilesystemSize  Used Avail Use% Mounted on
/dev/mapper/vg_system-lv_root
  3.9G  3.6G  178M  96% /
/dev/mapper/vg_system-lv_var
  3.0G  748M  2.1G  27% /var
/dev/mapper/vg_local-lv_opt
  3.9G  577M  3.2G  16% /opt
/dev/mapper/vg_local-lv_home
  992M   34M  908M   4% /home
/dev/mapper/vg_system-lv_tmp
  3.1G  250M  2.7G   9% /tmp
/dev/sda1 122M   19M   97M  17% /boot
tmpfs 502M  260M  242M  52% /dev/shm
/dev/mapper/vg_app-lv_oracle
   12G   11G  903M  93% /u01/app/oracle
rchnas05n1.mayo.edu:/vol/vol2/unixhomes-5gb/86/ts00086
  1.7T   25G  1.7T   2% /home/auto/ts00086

All our users are on independent NAS automounted home directories. Major
common software, like Tivoli or WebSphere is installed in /opt. For user
applications, we add a mountpoint of /apps. Other major players, such as
Oracle, get their own filesystems, as needed. Not seen here is a logical
volume for swap, which backs a vdisk for swap.

We use the same general model on Intel as well.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 2/23/12 9:43 AM, "Mark Workman"  wrote:

> What are recommended LVM mount points for a Linux guest?  I currently use
> /opt for my WebSphere installations, but occasionally fill up /.
>
> Thanks,
>
> Mark Workman
> Shelter Insurance Companies
> 573.214.4672
> mwork...@shelterinsurance.com

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: Missing DASD after reboot

[RPN01]

Edit modprobe.conf, mkinitrd, zipl. That's the pattern I use. It needs to be
available when the driver gets loaded, which, I think, is before the real
filesystem is available (which makes sense).

We have a script that re-reruns mkinitrd for each of the initrds that exist
on /boot, so everything gets updated for each of the options in the zipl
menu.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 2/7/12 2:02 PM, "Emmett O'Grady"  wrote:

> Do you need to run 'mkinitrd' with the new modprobe info.
>
>
>
>
>
> nix.rob...@mayo.edu
>
> Subject
> Re: Missing DASD after reboot
>
> I don't know if this is a problem with SuSE, but in RedHat, I usually do
> this to myself by not remembering to put a disk into modprobe.conf.
>
> If the disk is offline during the boot, chances are that it has nothing to
> do with udev, and much more to do with the dasd driver not seeing the
> device
> because it hasn't been told to scan that address.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: Missing DASD after reboot

[RPN01]

I don't know if this is a problem with SuSE, but in RedHat, I usually do
this to myself by not remembering to put a disk into modprobe.conf.

If the disk is offline during the boot, chances are that it has nothing to
do with udev, and much more to do with the dasd driver not seeing the device
because it hasn't been told to scan that address.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 2/7/12 1:21 PM, "Mark Post"  wrote:

 On 2/7/2012 at 01:27 PM, "van Sleeuwen, Berry" 
> wrote:
>>>  After reboot all DASD is online except 213.
>
> I have no idea what might be causing this, but perhaps this might stop the
> problem.  If you want to try to document the problem and open a service
> request about it, backup the contents of /etc/udev/rules.d/ first.
>
> 1. Reboot the system.  At this point, 0.0.0213 should be offline.
> 2. Try running "dasd_configure 0.0.0213 1" to see if it gets an error
> 2a. If it does, run lsdasd to see if it was brought online or not
> 2b. If it wasn't brought online, then use chccwdev -e 0.0.0213
> 3. Run "dasd_configure 0.0.0213 0" to vary it offline and delete the udev
> rules for it.
> 4. Run "dasd_configure 0.0.0213 1" to vary it back online and create new udev
> rules.
> 5. Reboot and see if 0.0.0213 comes online with all the rest of the volumes.
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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/

Re: Scientific Linux

[RPN01]

Are you thinking of the Gentoo Linux distribution? A lovely environment that
takes days to build given the proper circumstances and mindset

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 1/27/12 2:04 PM, "John Campbell"  wrote:

>
> Yeah, you can do it.  Maybe you'd be best looking (memory failure,
> distro name not handy!!!) at the distro that downloads source packages
> and compiles them as you build up the system (dammit, I can't believe
> the hole in my memory).
>
> (sighs)
>
> I can't trust my memory because it isn't accurate:  I recall looking a
> lot younger 30 years ago.
>
> -soup

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: mvsdasd

[RPN01]

Is there a reason that zOS NFS won't work? Then you'd have direct access to
the file, without copying via FTP or to z/VM, via a documented, supported
and auditable interface to zOS that is also documented and supported by
zLinux in the standard distribution. No odd files to build. No security or
audit holes to document. The glossy sheet is at
http://www-03.ibm.com/systems/z/os/zos/nfs/index.html

This is an interface that I'd easily be able to "sell" at my site. The
pieces are already all in place, as they're part of the standard operating
systems. There's network time involved, but there would be with any of the
solutions. There's no additional disk space involved as there would be with
an FTP store and forward type solution.

I think NFS would be a much cleaner solution to your problem than mvsdasd.
And, it has the advantage of being understandable by the person(s) who come
along after you who might have to support it or make changes to it.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 11/9/11 8:59 AM, "Agblad Tore"  wrote:

> Ok, since I think I was the one starting this I think a clarification about
> the reason is in place :)
> The 'problem': We need to read huge amount of data using a program on zLinux,
> but it needs access to the files.
> We could use ftp, but due to the
> huge amount of data, most of the costsaving is eaten up by ftp-cpucycles in
> z/OS :(
> And it takes time.
>
> If we could access the actual disks or files directly from zLinux it would
> really cut the cost here.
>
> In that case it is some dedicated volumes, scheduled and documented z/OS jobs.
>
> And about the mvsdasd program, it works like this:
> At the outpointed dasd volume it search for a file with a specified name, it
> must be there and it is a z/OS std seq file.
> It is created in z/OS and protected by RACF/ACF2.
> That file should contain names of files on that volume that mvsdasd is allowed
> to read.
>
> I think this makes it secure and auditable enough.
>
> But I haven't had the spare time to have this one working yet.
> For the moment we test to copy files from z/OS to z/VM CMS-files (tracable and
> auditable) and then read it from zLinux.
>
> /Tore

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: mvsdasd

[RPN01]

Since you got no replies, I took a quick look at the site. Since it creates
a read-only mount, I don't see how you're going to hurt anything, so that
would eliminate any of the "scary" portion, in terms of Sysplex membership
concerns.

Security concerns should be controlled from a z/VM standpoint, in that if
you don't want the Linux image to see it, don't give it a link to the disk.
If you're worried about a rogue z/VM administrator, he's got CMS, which
could do far more damage than a Linux image.

The mvsdasd driver doesn't support pdse or vsam, so it can't see most of
what z/OS does these days. I'm not too sure how useful it would be, other
than to get a view into flat files for the exchange of information meant
specifically for z/OS to Linux communications. On this point, it could be
fairly handy, but most sites will already have ftp or nfs traffic in place
to do this. Giving access to an entire disk to access a single text file
doesn't seem practical, and doesn't account for the fact that files'
locations aren't fixed in z/OS, so a great deal of legwork would be involved
just in locating the file and setting up the transaction, where FTP could be
far more simple and straight forward.

The driver itself makes a number of assumptions about the way z/OS sites "do
business" that smack of 1980's thinking. The z/OS world generally doesn't
work this way any more at the majority of sites, which leaves this
technology in the dust. In today's world, you never specify the volume where
a file will be created. The system takes care of this, based on standards
set up by the administrators.

It certainly wouldn't work here at all. I wouldn't even be able to get the
"security file" on a volume here, as its name doesn't fit into the file
naming standard here. The high-level-qualifier doesn't match anything used
here, and so could never be created. They've written this for their own
site, without any thought about what might be required anywhere else.

It's a product that solved problems 30 years ago. It just got written far
too late.

Hope this helps.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."


On 11/6/11 2:19 PM, "Richard Gasiorowski"  wrote:

> Going to ask again since the first message was so popular I received no
> responses.  has anyone used this driver from mvsdasd.org? Interested in
> any experience comments and gotcha's. Seems scary to open up z/VM access
> to z/OS DASD which is a member of a sysplex.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: Accessing Old Linux System After DASD Move

[RPN01]

Install a new Linux image (not actually that hard), and then mount the old
volumes and extract the necessary data you're looking for. Z/OS won't
understand the data at all.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 11/3/11 12:47 PM, "Craig Pace"  wrote:

> List,
>
> I have been doing some reading, scanning and searching and have come to
> many different answers and was wondering if someone might have some
> suggestions on this item.  We have an old Linux environment.  I am not
> sure how old it is; however, I know it is between 2 & 3 years at least.
> The system (Linux on System z - LPAR Mode) was not active and had the DASD
> (ECKD format) moved from one storage sub-system to another with now
> different UCBs.  I have been asked to look into bring up this system.  Is
> there any "easy" way to access the data to update the required
> configuration to now point to the correct UCB addresses?  At this point,
> we only have z/OS LPARs running in the environment with no other Linux.  I
> was hoping that I might be able to do something with USS; however, he does
> not know about the "formatted" filesystems that was built by Linux-390.
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: Odd swap space behavior

[RPN01]

You might also consider using a real disk to back the v-disk for the peak
period swap, so that it doesn't add additional memory pressure to the
underlying z/VM system.


On 11/2/11 10:29 AM, "Richard Troth"  wrote:

> You might consider a manual 'swapoff' (then 'swapon') of one large
> swap volume after that crunch time.  In any case, this is one where
> you should reconsider how much VDISK to use.  Obviously, there's a lot
> happening when it gets that end-of-month workload, so remember to
> include CPU and other I/O when you profile this server.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: Odd swap space behavior

[RPN01]

That's what you want when you're using "spindles", but on z, you're usually
talking about v-disks, which are really virtual disks in memory. When
they're not in use, they take up no space at all, but when you start using
them, they start to occupy real memory and become a burden. So you set
priorities on the swap spaces so that they each get used one at a time in
turn.

Ideally, you don't want to use them at all; they're a safeguard to keep the
image from coming down. When they are used, they're an indication that you
need more memory allocated to the image, and they give you a buffer to get
to the moment when you can safely cycle the image to add that memory. Having
four swap spaces allocated seems like a bit of overkill to me. It should be
sufficient to have one to be the buffer, and a second larger one to be the
trigger to increase the size of the image.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 11/2/11 8:25 AM, "Richard Higson"  wrote:

> On Wed, Nov 02, 2011 at 07:37:17AM -0400, Bauer, Bobby (NIH/CIT) [E] wrote:

> haven't done Linux on Z for a while, but I have always used the same
> "Priority" for the swapdisks
> so that linux could spread out the IO to several disks (preferably on separate
> spindles).
> This works well on x86 (real & VMware) and P-Series
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: VDISK Swap

[RPN01]

I think that "Gck!" means that strings that aren't meant to be
interpreted as variables should always be quoted so that they don't get
interpreted as variables.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 11/1/11 10:24 AM, "Dean, David (I/S)"  wrote:

> Thank you, I will. I will also assume Gaaack! means you are really impressed
> with my work.
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: VDISK Swap

[RPN01]

Do you IPL Linux directly in the virtual machine, or do you IPL CMS first?
SWAPGEN is a CMS exec which defines the Swap space using CMS commands,
before you IPL Linux from within CMS. IPLing CMS first gives you a chance do
preface the Linux IPL with some intelligence, such as defining the vDisk
swap space and checking to be sure that the Linux guest isn't running on any
other z/VM system first, before IPLing it where you are. It can also do some
accounting or anything else you'd like in CMS before starting the Linux
system.

If you IPL Linux directly, then you need to add the mkswap to your start-up
there, so that it can happen each time as the system comes up, without the
need for CMS and its tools. Either way will work equally well.
--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 10/5/11 2:31 PM, "Dean, David (I/S)"  wrote:

> No, the only place I have them defined is in the USER DIR.  Where do I put
> swapgen exec.
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark
> Post
> Sent: Wednesday, October 05, 2011 3:15 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: VDISK Swap
>
 On 10/5/2011 at 03:04 PM, "Dean, David (I/S)"  wrote:
>> Why do my swap disks go away when the zvm is ipl'ed?  They are defined in the
>> USER DIRECTORY, they are then created on each Linux box as swap drives
>> through partitioning, and exist in the fstab as swap disks.  After a recent
>> IPL, I had to re partition each drive...
>
> Do your guests IPL CMS and run SWAPGEN EXEC before Linux gets IPLed?
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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/
> -
> Please see the following link for the BlueCross BlueShield of Tennessee E-mail
> disclaimer:  http://www.bcbst.com/email_disclaimer.shtm
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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/

Re: VDISK Swap

[RPN01]

After the hasty replies, I suppose one should ask, how do you have your swap
disks defined in your CP Directory? Depending on your definition, you could
actually have a real concern, aside from the two comments already given.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 10/5/11 2:14 PM, "Mark Post"  wrote:

 On 10/5/2011 at 03:04 PM, "Dean, David (I/S)"  wrote:
>> Why do my swap disks go away when the zvm is ipl'ed?  They are defined in the
>> USER DIRECTORY, they are then created on each Linux box as swap drives
>> through partitioning, and exist in the fstab as swap disks.  After a recent
>> IPL, I had to re partition each drive...
>
> Do your guests IPL CMS and run SWAPGEN EXEC before Linux gets IPLed?
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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/

Moving to new DASD and LVM...

[RPN01]

Just from the ³interesting uses of LVM² department...

We¹d been asked to move from one set of DASD to another once too often, and
one of the guys here came up with a slick script based on our filesystem
layout that has made life much simpler that I thought folks might be
interested in hearing about.

We place everything, including the root filesystem, in LVM, the only
exception being the /boot directory. There¹s been a lot of criticism of this
in the past, but in this one case, it¹s been a life saver. What it is
allowing us to do is attach a new set of DASD matching the old set, unmount
/boot and dd it to the new DASD then remount it, then create new pv volumes
matching the old ones, add them into the existing volume groups, and use
pvmove to move the running system to the new DASD without having to stop the
system in any way. Once the move is done, the old DASD can be reduced and
removed from the volume group, and then removed from the running Linux
image. Afterward, running mkinitrd and zipl cleans up the system and makes
it ready for its future reboot.

This method removed the need to schedule downtime with the Linux image¹s
users, removed the need for a reboot and any downtime during the process,
and works cleanly and efficiently. Once the disks are allocated via DirMaint
using a rexx exec which reads the directory entry and allocates matching
minidisks within the new allocation area, the entire process is handled via
a single Perl script within the Linux image itself. Afterward, DirMaint is
used to free the old disks.

Just another example of the versatility of LVM...

-- 
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Oracle 11G on zLinux

[RPN01]

We¹re in the process of doing an Oracle 11g install for proof of concept,
and we¹ve run into the 4gig memory issue. We gave the machine 4g of memory,
but it came up with an actual value of 3.9255gig and failed. Why is 4gig not
4gig? And, how much memory actually has to be allocated to install? Does
that amount really have to be left in the image moving forward? How are
other sites configuring Oracle on zLinux?

-- 
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: Linux backups and restores to/from tape

[RPN01]

It's not free, but we use Veritas NetBackup for all our Linux, Unix and even
Windows systems for file-level backups. It works just as well for zLinux as
it does for Linux on Intel.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 7/8/11 10:23 AM, "Frederick, Michael"  wrote:

> Hi all,
>
> A question came up about getting an older version of a file on a Linux disk,
> which I was able to do by restoring the DASD that held the file in question to
> a temporary disk and then they could do whatever they liked with the file,
> easy enough.  It got me to thinking about, what would happen if this were to
> take place on an LVM?  Having a dasd-level backup is likely to be of limited
> use in this case, because you'd more than likely have to restore the entire
> LVM to a separate set of disks just to get at that one file.
>
> So does anyone know of a solution (free being better) that would do a
> file-level backup for zLinux to a tape?  Or has anyone dealt with this problem
> before and had some other way around it?
>
> Thanks in advance,
>
> Mike Frederick
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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/

[no subject]

[RPN01]

Spam


On 7/8/11 2:47 AM, "Rob JACKSON"  wrote:

> I invite you to visit my first site! It¹s important for me!..
> http://www.soleholiday.com/sites.friend.php?zyqCID=16iw4
>  
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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/

Re: vdisk

[RPN01]

Very true, and swapgen is what we use here. I didn't want to muddy the water
he was looking through though with additional tools, until he understood
what he had at the moment.

If you don't understand where you are, it isn't really important that you
might want to be 10 feet over there.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 4/20/11 10:42 AM, "David Boyes"  wrote:

>> Since it's a fresh disk every time, you'd have to do the mkswap every
>> time
>> you log in, so my guess is that's why you'd need the mkswap and
>> subsequent
>> swapon in the boot.local. The vdisk wouldn't be formatted when you get
>> it at
>> each fresh logon.
>
> I'll point out that running SWAPGEN before Linux IPL is intended to solve this
> problem. IPL CMS in the Linux guest at boot, and run SWAPGEN in the PROFILE
> EXEC. The swap disk is formatted and marked as a swap disk, and Linux "just
> works" from release to release, without having to do local mods inside the
> Linux system.
>
> --d b
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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/

Re: vdisk

[RPN01]

Since it's a fresh disk every time, you'd have to do the mkswap every time
you log in, so my guess is that's why you'd need the mkswap and subsequent
swapon in the boot.local. The vdisk wouldn't be formatted when you get it at
each fresh logon.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 4/20/11 9:06 AM, "Dean, David (I/S)"  wrote:

> Ok, we have it working.  Defined it in User Directory, formatted it for swap,
> added it to fstab, and added it to boot.local -> mkswap and swapon.
>
> Why did I have to add it boot.local?  why does it not act like a normal DASD
> drive and come on at boot?
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: Where is kernel loaded in memory?

[RPN01]

Could you set up a cron job / set of cron jobs to go out and wake things up
in the morning before things actually start to get busy? Take the edge off
starting things up?

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 3/17/11 2:04 PM, "Mark Wheeler"  wrote:

> Yes to both.
>
> The fundamental problem is one of expectations. One of z/VM's strengths is
> that it virtualizes storage. While that means storage can be overcommitted, it
> also means that unused storage gets paged out. Alas, some of that storage
> needs to get paged back in when the server awakens. Unfortunately, the
> customer expects that to occur instantaneously. Most customers of nearly all
> servers! If all servers get assigned RESERVEd pages, people will likely be
> more unhappy than they are now.
>
> I suspect SET RESERVE will cause some interesting side effects. Just
> speculating, but I think it may force these guests to look like polling
> guests, in that pages will only be paged out during emergency scan, e.g
> probably not the pages you want. Hence, as Rob van der Heij has recommended,
> you may need to beef up your XSTOR.
>
> Mark Wheeler
> UnitedHealth Group
>
>
>
>
>> Date: Thu, 17 Mar 2011 11:38:52 -0700
>> From: dkreu...@vm-resources.com
>> Subject: Re: Where is kernel loaded in memory?
>> To: LINUX-390@VM.MARIST.EDU
>>
>> Have you considered SET RESERVE for this guest? What about expanded
>> storage tweaks/increase?
>> David
>>
>>
>>  Original Message 
>> Subject: Re: Where is kernel loaded in memory?
>> From: Mark Wheeler 
>> Date: Thu, March 17, 2011 2:11 pm
>> To: LINUX-390@VM.MARIST.EDU
>>
>> MQ Broker.
>>
>>
>>> Date: Thu, 17 Mar 2011 12:22:35 -0500
>>> From: marcy.d.cor...@wellsfargo.com
>>> Subject: Re: Where is kernel loaded in memory?
>>> To: LINUX-390@VM.MARIST.EDU
>>>
>>> Mark, is this WAS? Is it possible it involves the heap? (BTDT :)
>>>
>>>
>>> Marcy
>>
>> --
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@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 lists...@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 lists...@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 lists...@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/

Re: Where is kernel loaded in memory?

[RPN01]

An obvious question that no one has bothered to ask as yet:

What is the problem you're trying to solve with this? Or, why do you want to
know where the kernel loads, and what will you gain from it?

Too many times, users or other people (programmers, other sysadmins, ...)
come to us with a solution in need of a piece or part, and we never hear the
larger question or problem, to which there may be a much simpler answer.

The query may be a simple one, the need may be educational. Or it may be a
cog in a larger, complex solution to a problem that some, or many of us have
already solved in some other way which does not involve walking through the
kernel's memory.

It's just a thought, but Mark -- What's your original problem or task?

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 3/17/11 5:59 AM, "Richard Troth"  wrote:

> Originally, the kernel loaded at "real" addr 64k.  That is the default for
> Linux on most platforms.  But you could change that, and for 1M alignment,
> some do so on S/390.
>
> Going with mapped memory, it sounds like absolute zero is the virtual pref
> for kernel space.   Cool.  Easily handled in all virt mem platforms.
>
> -- R; <><

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: WAS for zLinux download

[RPN01]

It's actually a Java package, isn't it? So isn't it write once, debug
everywhere?

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 12/8/10 7:15 AM, "Sergey Korzhevsky"  wrote:

> Hi All,
>
>   Can you, please, point me to the page, where i can download Websphere AS
> 7.0 for zLinux? I found it just for Intel Linux/Windows. It was here :
> http://www.ibm.com/developerworks/downloads/ws/was/
>
> Thank you.
>
>
> WBR, Sergey
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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/

Re: Support thru IBM?

[RPN01]

I use the z/VM tree, and specify in the beginning of the problem description
that it is a RedHat Linux problem, and that we get out service from IBM, but
that there is no option for it in the IBMLink tree. It gets to the right
person somehow.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 10/26/10 2:08 PM, "Harder, Pieter"  wrote:

> Yes, you can (at least for Suse I have done so). You illogically have to
> follow the z/OS tree and Linux is linked in as a z/OS subproduct.
>
> 
> Van: Linux on 390 Port [linux-...@vm.marist.edu] namens Bauer, Bobby (NIH/CIT)
> [E] [baue...@mail.nih.gov]
> Verzonden: dinsdag 26 oktober 2010 20:43
> Aan: LINUX-390@VM.MARIST.EDU
> Onderwerp: Re: Support thru IBM?
>
> We've been told you can't use IBMLINK to open a problem.
>
> Bobby Bauer
> Center for Information Technology
> National Institutes of Health
> Bethesda, MD 20892-5628
> 301-594-7474
>
>
>
> -Original Message-
> From: RPN01 [mailto:nix.rob...@mayo.edu]
> Sent: Tuesday, October 26, 2010 12:00 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Support thru IBM?
>
> The short answer is "Yes".
>
> We do it both ways.
>
> --
> Robert P. Nix  Mayo Foundation.~.
> RO-OC-1-18 200 First Street SW/V\
> 507-284-0844   Rochester, MN 55905   /( )\
> -^^-^^
> "In theory, theory and practice are the same, but
>  in practice, theory and practice are different."
>
>
>
> On 10/26/10 7:27 AM, "Bauer, Bobby (NIH/CIT) [E]" 
> wrote:
>
>> To those who have Redhat support through IBM, are you able to enter a problem
>> using IBMLINK or do you have to call?
>>
>> Thanks
>> Bobby Bauer
>> Center for Information Technology
>> National Institutes of Health
>> Bethesda, MD 20892-5628
>> 301-594-7474
>>
>> --
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@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 lists...@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 lists...@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/
>
> Brabant Water N.V.
> Postbus 1068
> 5200 BC  's-Hertogenbosch
> http://www.brabantwater.nl
> Handelsregister: 16005077
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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/

Re: Support thru IBM?

[RPN01]

The short answer is "Yes".

We do it both ways.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 10/26/10 7:27 AM, "Bauer, Bobby (NIH/CIT) [E]" 
wrote:

> To those who have Redhat support through IBM, are you able to enter a problem
> using IBMLINK or do you have to call?
>
> Thanks
> Bobby Bauer
> Center for Information Technology
> National Institutes of Health
> Bethesda, MD 20892-5628
> 301-594-7474
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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/

Re: Fedora 14 images

[RPN01]

Is there a Fedora 14 ISO image for "real" mainframes? I.E. Those of us poor
people who can't afford Hercules and have to get real zSeries boxes to play
with?

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 9/30/10 11:08 AM, "Robin Atwood"  wrote:

> On Thursday 30 September 2010, Phil Knirsch wrote:
>> On 09/30/2010 04:48 PM, Robin Atwood wrote:
>>> Karsten -
>>> I downloaded the installation images and booted using Hercules 3.07 (from
>>> SVN) and everything went well until anaconda crapped out during
>>> "Examining storage" (or a similar message). I had allocated four empty
>>> 3390-9's which ought to be enough. I can post the logs here or is it
>>> best to pursue this somewhere else?
>>>
>>> Cheers
>>> -Robin
>>
>> Hi Robin.
>>
>> Were those completely fresh DASDs? If so, then anaconda should have
>> asked you if it should initialize them (via dasdfmt). If that happened
>> then you most likely got hit by the bug i described in point 10:
>>
>> 10) After a while if you do this the 1st time you will be asked to
>> confirm to low level format the
>>  drive. Do this as this has to happen for a first time image. If you
>> reuse an old image you
>>  won't be bothered with this anymore.
>>  We've had some cases where with a completely fresh image even
>> partition would traceback. In that
>>  case simply restart the install from step 7) onwards and it should
>> work.
>
> They were formatted with the dasdinit "-linux" parameter so dasdfmt should not
> be necessary. or will that confuse it?
>
> -Robin
> --
> --
> Robin Atwood.
>
> "Ship me somewheres east of Suez, where the best is like the worst,
>  Where there ain't no Ten Commandments an' a man can raise a thirst"
>  from "Mandalay" by Rudyard Kipling
> --
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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/

Re: managing rhel disk space

[RPN01]

In your case it might require a time machine, but we've used LVM for this
type of thing. You put the amount of space there you need, rather than way
over-allocating space. Then in situations like this, you add the needed
space, and create the mount points they need. Also, down the road, when they
discover that they really should have asked for double that amount, you just
add the space to the volume group, give it to the logical volume, and extend
the filesystem. It really works as advertised.

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 9/13/10 2:10 PM, "Donald Russell"  wrote:

> I have a RHEL 5.5 system running on zVM 5.4...
>
> I've recently received a request to add two more file systems of 1 GB and
> 2GB and mount them at /var/something-something and /opt/something-something
>
> There is already enough free space in those directories to accommodate their
> request, so I just created the directories for them.
>
> However, they're insisting they be separate file systems so they can't
> accidentally exceed the expected max usage.
>
> So, my question is... do I have to attach new minidisks or LUNs(?) of the
> appropriate sizes or can quotas set a cap on the amount of space a directory
> can use? I know I can set individual user quotas, but I've a feeling there's
> more than one user of this space.
>
> What do other people do in these situations? Adding MDISKs or LUNs sounds
> extreme to me...
>
> I was looking at the mkfs command, but that seems to require
> unused/allocated part of an existing partition all non-cms disk space
> that's attached to the VM id is allocated to Linux. Can I reduce the size of
> a logical volume, then create a new filesystem from that freed space?
>
> Thanks
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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/

Debian install...

[RPN01]

Anyone done a Debian install on z/VM?

I’m attempting to install Lenny, and I get to the DASD partitioning. I set
up my disks the way I want them, tell it to begin writing, and get the
following:

┌──┤ [!!] Partition disks ├──
 │  ERROR!!!  │
 │ VTOC: seeking on device failed -- vtoc_write_label │
 │ Could not write VTOC labels.   │
 ││
 │ │
 ││
 └─

The install won’t go any further from there.

I know the disks are writable within the virtual machine; I was able to use
cpfmtxa on them, and Debian was able to format them. I’ve tried just about
every combination of formatting and not formatting, partitioning and not
partitioning that I can think of. We have 50 RedHat and SuSE images running,
so it’s not that we don’t know what we’re doing in general. There must be a
way to make this work, or they wouldn’t have released it. Does anyone have a
clue as to how to do it correctly?


--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: IT staff integration?

[RPN01]

We did this here; I moved from the mainframe team into the Unix team, after
starting to work more and more with Linux on z/VM, and one of the Linux
people began doing more with z/VM once I got there, so we merged the two.

Now (don't ask) the two of us have been moved to the Windows team, because,
obviously, Windows and Linux both run on Intel hardware. Go figure.

When life gives you lemons... Put them in vodka.
--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 9/3/10 10:38 AM, "John Campbell"  wrote:

> I think it would be hard to take a dyed-in-the-wool z/VM (or zOS)
> maven and turn them into a PenguinHead...  and taking a PenguinHead
> and expecting them to embrace z/VM as fanatically as they embrace
> Linux is likely to be as difficult.
>
> The philosophies of the environments are so different so there's going
> to be limited overlap and no one is likely to be able to quickly
> switch mental context between the two different OS architectures.
>
> I suspect my time as an AIX geek (AIX has VERY non-Unix internals and
> the fact that there's enough in a thin veneer to make it act vaguely
> like a Unix system from the POV of a SysAdmin strikes me as
> near-miraculous) helps me to handle some of the cross-over (and the
> IBM class in z/VM and Linux, I forget the Q number) between the needs
> of z/VM and zLinux.
>
> (chuckles)
>
> This goes beyond "z/VM is a hypervisor, and Linux is a guest, just
> like CMS, zOS and VSE".
>
> -soup

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@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/

Re: Problem with root

[RPN01]

What did the device look like when it was alright? Just a straight
filesystem in a partition, or a LVM volume group?

Did you check your CP Directory to be sure that nothing overlaid the disk?
Can you link and access it in CMS and see what the volume label is? This
might be a clue...

Can you dump the first few tracks of the disk to see the contents, and do
they look correct?

-- 
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 6/22/10 9:22 AM, "Victor Echavarry Diaz" 
wrote:

> When we re-ipl this server we receive the following message:
> 
> VFS: Cannot open root device "dasdb1" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> HCPGIR450W CP entered; disabled wait PSW 00020001 8000  006A1B82
> 
> Does anybody know how to solve this
> 
> Regards,
> 
> V�ctor Echavarry
> System Programmer
> Technology Systems & Operations Division
> EVERTEC
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> -
> 
> CONFIDENTIALITY NOTE: This email communication and its attachments
> contain information that are proprietary and confidential to
> EVERTEC, INC., its affiliates or its clients.  They may not be
> disclosed, distributed, used, copied or modified in any way without
> EVERTEC, Inc.’s authorization. If you are not the intended
> recipient of this email, you are not an authorized person.  Please
> delete it and notify the sender immediately. EVERTEC, Inc. and its
> affiliates do not assume any liability for damages resulting from
> emails that have been sent or altered without their consent.
> Moreover, EVERTEC, Inc. has taken precautions to safeguard its
> email communications, but cannot assure that such is the case and
> disclaim any responsibility attributable thereto.
> 
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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/

Re: Missing chccwdev

[RPN01]

If that's the case, then you should likely do a mkinitrd and zipl before you
bring the image down, as it may not come up correctly without the zipl being
run

--
Robert P. Nix  Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 6/22/10 7:24 AM, "Bauer, Bobby (NIH/CIT) [E]" 
wrote:

> That was it, thanks.
>
> Bobby Bauer
> Center for Information Technology
> National Institutes of Health
> Bethesda, MD 20892-5628
> 301-594-7474
>
>
>
> -Original Message-
> From: Rob van der Heij [mailto:rvdh...@gmail.com]
> Sent: Tuesday, June 22, 2010 7:54 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Missing chccwdev
>
> On Tue, Jun 22, 2010 at 1:50 PM, Bauer, Bobby (NIH/CIT) [E]
>  wrote:
>> I just built a new server and 'chccwdev' is missing. Not sure what I did
>> differently. Anybody tell me where to get this module. Probably I forgot to
>> install some package. I noticed it when I tried to setup swap devices.
>>
>
> It's part of the s390-tools package (at least on SLES). I would expect
> that missing zipl (also in the package) would prevent the installer
> from doing things right.
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@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 lists...@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 lists...@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/

Re: TSM memory requirements

[RPN01]

Most products stated requirements assume that they will be running on an
Intel box as the only "guest", and without any hypervisor support. The
likely need is for disk buffering; hopefully, the actual code doesn't need
12GB to run in.

In z/VM, you already have disk buffering at a minimum of two levels,
assuming IBM DASD: The DASD controller buffers disk access, and z/VM does
some buffering as well; depending on MDCache settings, it may be doing a
lot.

Linux on Z tuning principles are generally that you should allocate just
enough storage so that the virtual image just begins to page. At that point,
the program is running efficiently, and the disk caching is being handled
behind the curtain.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 6/2/10 10:04 AM, "Melancon, Ruddy"  wrote:

> We currently have a z10 with 2 IFL's driving one LPAR running zVM and Linux
> images.  The LPAR has 18GB of real storage and 6 GB of expanded storage
> assigned to it.
>
> We are wanting to run four images Linux with TSM as the application.  In the
> TSM literature it states that we should have 12GB of real storage for each
> image.  Is this virtual mamory or do we need 12 times 4 for 48 GB REAL memory
> to accomplish this scenerio?  Has anyone tried this before?
>
> Ruddy A. Melancon
> IT Systems Specialist, Senior
> Alabama Department of Transportation
> 334-353-6323
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: AUTO: Jon Nolting we be in Palisades, NY for meetings. I will have periodic access to email and VM. (returning 06/06/2010)

[RPN01]

You do realize that you're announcing that your house is empty and available
to rob... Right?

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 6/1/10 5:03 PM, "Jonathan R Nolting"  wrote:

> I am out of the office until 06/06/2010.
>
>
>
>
> Note: This is an automated response to your message  "?z/VM and z/OS
> sharing OSAs?" sent on 6/1/10 13:19:02.
>
> This is the only notification you will receive while this person is away.
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Monday for RHEL 5

[RPN01]

My best guess (having "tested" this theory several times personally) is that
you added several disks (maybe two?) to the system and added them into LVM
groups, but forgot to edit modprobe.conf and execute the mkinitrd and zipl
following the additions.

This is guaranteed to give varying weird results such as what you are now
seeing.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."


On 4/26/10 8:00 AM, "Frank M. Ramaekers"  wrote:

> There was a normal shutdown of RHEL 5 on Friday, but today:
>
>
>
> Waiting for driver initialization.
>
>
> Scanning and configuring dmraid supported devices
>
>
> Scanning logical volumes
>
>
>   Reading all physical volumes.  This may take a while...
>
>
>   Couldn't find device with uuid
> 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'.
>
>   Couldn't find device with uuid
> '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'.
>
>   Couldn't find device with uuid
> 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'.
>
>   Couldn't find device with uuid
> '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'.
>
>   Couldn't find device with uuid
> 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'.
>
>   Couldn't find device with uuid
> '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'.
>
>   Couldn't find device with uuid
> 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'.
>
>   Couldn't find device with uuid
> '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'.
>
>   Found volume group "VolGroup01" using metadata type lvm2
>
>
> Activating logical volumes
>
>
>   Couldn't find device with uuid
> 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'.
>
>   Couldn't find device with uuid
> '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'.
>
>   Couldn't find device with uuid
> 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'.
>
>   Couldn't find device with uuid
> '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'.
>
> Couldn't find device with uuid 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'.
>
>
> Couldn't find device with uuid '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'.
>
>
> Couldn't find device with uuid 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'.
>
>
> Couldn't find device with uuid '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'.
>
>
> Couldn't find device with uuid 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'.
>
>
> Couldn't find device with uuid '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'.
>
>
> Refusing activation of partial LV LogVol00. Use --partial to override.
>
>
> Couldn't find device with uuid 'ogvezr-vkSF-BPI5-mGBq-tKY5-1NOz-GOVHot'.
>
>
> Couldn't find device with uuid '5vu4wT-amMD-6LEm-Q59g-uAxb-POZu-VI5cN1'.
>
>
> 1 logical volume(s) in volume group "VolGroup01" now active
>
>
> eating root device.
>
>
> unting root filesystem.
>
>
> unt: could not find filesystem '/dev/root'
>
>
> tting up other filesystems.
>
>
> tting up new root fs
>
>
> tuproot: moving /dev failed: No such file or directory
>
>
>  fstab.sys, mounting internal defaults
>
>
> tuproot: error mounting /proc: No such file or directory
>
>
> tuproot: error mounting /sys: No such file or directory
>
>
> itching to new root and running init.
>
>
> mounting old /dev
>
>
> mounting old /proc
>
>
> mounting old /sys
>
>
> switchroot: mount failed: No such file or directory
>
>
> Kernel panic - not syncing: Attempted to kill init!
>
>
> HCPGIR450W CP entered; disabled wait PSW 00020001 8000 
> 0010C04A
>
>
>
> (Sorry, but my RHEL 5 is not supported...the THIRTY DAY trial ran out at
> the end of last month.)
>
>
>
>  Frank M. Ramaekers Jr.
>
>
>
> Systems Programmer
>
> MCP, MCP+I, MCSE & RHCE
>
> American Income Life Insurance Co.
>
> Phone: (254)761-6649
>
> 1200 Wooded Acres Dr.
>
> Fax: (254)741-5777
>
> Waco, Texas  76701
>
>
>
>
>
>
> _
>
> This message contains information which is privileged and confidential and is
> solely for the use of the
>
> intended recipient. If you are not the intended recipient, be aware that any
> review, disclosure,
>
> copying, distribution, or use of the contents of this message is strictly
> prohibited. If you have
>
> received this in error, please destroy it immediately and notify us at
> privacy...@ailife.com.
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: /var/lib/zypp/cache/ is on my nerves

[RPN01]

Before you get really fired up about all these paths, I'll give you a
command that I use to see if / where the space is being used:

du -cks * | sort -rn | head -11

Run this from any "root" that you feel is using space, and it will show you
the top 10 "offenders" in that root. So in your case, you might try:

cd /var/cache ; du -cks * | sort -rn | head -11

An easy way to keep this handy is to add to your .profile or .bashrc the
command:

Alias ducks=' du -cks * | sort -rn | head -11'

This would change the above to

cd /var/cache ; ducks

Hope this will help.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 4/23/10 12:47 PM, "Peter E. Abresch Jr.   - at Pepco"
 wrote:

> Thanks, I made the changes. I also notice the following in
> /var/cache/zmd/web/files/nu.novell.com/repo/$RCE:
>
> linuxd02:/var/cache/zmd/web/files/nu.novell.com/repo/$RCE # ls -l
> total 0
> drwxr-xr-x 3 root root 80 Apr 11 20:16 SLE10-SP1-Debuginfo-Updates
> drwxr-xr-x 3 root root 80 Apr 11 20:23 SLE10-SP2-Debuginfo-Updates
> drwxr-xr-x 3 root root 80 Apr 11 20:28 SLE10-SP3-Debuginfo-Online
> drwxr-xr-x 3 root root 80 Apr 11 20:28 SLE10-SP3-Debuginfo-Pool
> drwxr-xr-x 3 root root 80 Apr 11 20:27 SLE10-SP3-Debuginfo-Updates
> drwxr-xr-x 3 root root 80 Apr 11 20:08 SLES10-SP1-Online
> drwxr-xr-x 3 root root 80 Apr 11 20:11 SLES10-SP1-Updates
> drwxr-xr-x 3 root root 80 Apr 11 20:17 SLES10-SP2-Online
> drwxr-xr-x 3 root root 80 Apr 11 20:25 SLES10-SP2-Pool
> drwxr-xr-x 3 root root 80 Apr 11 20:18 SLES10-SP2-Updates
> drwxr-xr-x 3 root root 80 Mar  4 06:59 SLES10-SP3-Online
> drwxr-xr-x 3 root root 80 Apr 11 20:27 SLES10-SP3-Pool
> drwxr-xr-x 3 root root 80 Apr 11 20:25 SLES10-SP3-Updates
>
> Again, all these look like patches, I can I stop these and since we are
> SP3 everywhere, can I safely delete all the non-SP3 directories?
>
> Peter
>
>
>
> Mark Post 
> Sent by: Linux on 390 Port 
> 04/23/2010 12:18 PM
> Please respond to
> Linux on 390 Port 
>
>
> To
> LINUX-390@vm.marist.edu
> cc
>
> Subject
> Re: /var/lib/zypp/cache/ is on my nerves
>
>
>
>
>
>
 On 4/23/2010 at 12:06 PM, "Peter E. Abresch Jr.   - at Pepco"
>  wrote:
>> cache-max-size-hard-limit  | False  | If true, never allow
> the
>> cache to grow past the maximum size
>> cache-max-size-in-mb   | 300| The maximum size of
> the
>> cache (in mb)
>> max-cache-age  | 30 | The maximum number of
>> days to cache a file
>>
>> Is there any hope here?
>
> By changing these values you can limit how much space is taken up on your
> systems.  I'm not sure just how much you're going to be saving though.  On
> the system I checked, /var/lib/zypp/ is only taking up about 12MB. Another
> one is using 40MB.
>
> In any case, you can use "rug set-prefs" to change them, one preference at
> a time:
> rug set-prefs cache-max-size-hard-limit true
> rug set-prefs cache-max-size-in-mb 200
>
> and so on.
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>
>
> This Email message and any attachment may contain information that is
> proprietary, legally privileged, confidential and/or subject to copyright
> belonging to Pepco Holdings, Inc. or its affiliates ("PHI").  This Email is
> intended solely for the use of the person(s) to which it is addressed.  If
> you are not an intended recipient, or the employee or agent responsible for
> delivery of this Email to the intended recipient(s), you are hereby notified
> that any dissemination, distribution or copying of this Email is strictly
> prohibited.  If you have received this message in error, please immediately
> notify the sender and permanently delete this Email and any copies.  PHI
> policies expressly prohibit employees from making defamatory or offensive
> statements and infringing any copyright or any other legal right by Email
> communication.  PHI will not accept any liability in respect of such
> communications.
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: A Question on Sizing z/VM Linux Guests

[RPN01]

If you're using IBM style DASD as your disk storage, you'll want to size the
linux image's memory considerably smaller than what is suggested for an
Intel processor.

The first reason is that you have several levels of cache before the data
even gets to the linux image. These layers (controller, z/VM, mdcache) will
cut the time to retrieve the data, and caching it in linux as well really
won't make anything any faster.

The second reason is that larger images cause more paging on z/VM's part.
The Intel memory suggestion is based on real memory, always available. Since
this is virtual memory, your "in-memory cache" may actually be on disk
anyway, causing a paging read when it is needed. You can actually slow down
the response in an image by making its memory larger, because it will spend
much more time paging.

Finding the right size is a little more tricky. You want to start at some
reasonable value (1G, 2G...), and then cut the image's memory over time
until you notice it just begin to swap. Some people will allow it to do this
minimal swapping, while others will increase the image size enough so that
it doesn't swap at all. It just depends on which expert you choose to listen
to.

At this point, you'll have an image that supports the application running,
but doesn't have enough memory to devote a large amount to caching its disk,
which is exactly where you want to be. You may actually be surprised at how
little memory this really is.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 2/4/10 7:00 AM, "Carson, Brad"  wrote:

> We have a project that is being setup to run on RHEL under z/VM.  The sizing
> parameters for the guests (Oracle DB, and WebLogic) are being sent to us based
> on intel platform sizing.  How do some of you handle the sizing conversion
> from Intel to IFL's?  Are there some rules of thumb, we should know about?
>
> Our environment:
>
> IBM z10-BC (QA and Dev) and z10-EC (Prod) running z/VM 5.4 and RHEL 5.3.
>
>
> Thanks for any insight.
>
> /Brad (please ignore the company inserted HIPAA disclaimer)
>
> - This e-mail and any attachments may
> contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If
> you are not the intended recipient, any use or disclosure of this information
> is STRICTLY PROHIBITED; you are requested to delete this e-mail and any
> attachments, notify the sender immediately, and notify the LabCorp Privacy
> Officer at privacyoffi...@labcorp.com or call (877) 23-HIPAA.
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

RedHat 5.4 (and 5.2) installs fail before formatting DASD

[RPN01]

Trying to install a RedHat image by hand, and I get through the network
definitions, I skip the installation number, and get to the warning about
formatting the first disk and data loss. I tell it to go ahead and format,
and RedHat exits without doing anything.

Is there any way to get around this and go on with the install?

I¹ve tried both RHEL 5.4 and 5.2, with the same results. Open to any
suggestions.

(SLES was much simpler...)
-- 
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Backup procedure for Linux

[RPN01]

You may find your backups to be inconsistent or unstable this way, as Linux
buffers things in storage, so the disk image taken by the snapshot may not
be complete at the moment you flash.

Have you tried mounting and looking over the data on the backup disks as
yet?

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 12/17/09 12:50 PM, "Gary Detro"  wrote:

> The approach we have taken is to give the machine duplicate mdisk 150-155
> (base disk) and then B150-B155 (backup disks) and do a flashcopy of the base
> disks to the backup disks.  From another user running CMS programmable
> operator.   I do this without stopping the linux guest system and it has been
> recoverable each time we have tested.
>
>
> Thanks,
>
> Detro
>
>
>
>
>
>
>
>
> From: Stephen Frazier 
> To: LINUX-390@VM.MARIST.EDU
> Date: 12/17/2009 12:45 PM
> Subject: Re: Backup procedure for Linux
> Sent by: Linux on 390 Port 
>
>
>
>
> Romanowski, John (OFT) wrote:
>> > Are you asking how to make the script launch automatically when the
>> minidisk attach event occurs? or ??
>> >
>> >
> No, what I am asking is what should I put in the script to be able to
> back up everything needed to do a restore in another virtual machine.
>
> --
> Stephen Frazier
> Information Technology Unit
> Oklahoma Department of Corrections
> 3400 Martin Luther King
> Oklahoma City, Ok, 73111-4298
> Tel.: (405) 425-2549
> Fax: (405) 425-2554
> Pager: (405) 690-1828
> email:  stevef%doc.state.ok.us
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

<>

Re: Adding dasd to Red Hat, mkinitrd problem

[RPN01]

The command we use is the following, if you're remaking your current system:

mkinitrd -v -f initrd-$(uname -r).img $(uname -r)

Don't know if this will help

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 9/9/09 2:29 PM, "Sue Sivets"  wrote:

> I'm trying to add 2 new mini disks to Redhat 5.3, and I've now reached
> the point where I'm going nowhere fast. The dasd are online, and
> mounted, I've updated both fstab and modprobe.conf, and I've renamed the
> initrd img file according to the RedHat Installation Guide. When I try
> to run mkinitrd, I get an error message, and so far, I haven't been able
> to figure why it's complaining.The mkinitrd command I entered is:
>
>  mkinitrd -v /boot/initrd-2.6.18-128.el5.img  2.6.18-128.e15
>
> The message I get back is: No modules available for kernel
> "2.6.18-128.e15". I have no idea what modules it's looking for, or why
> it can't find them. This is a brand new install, and I'm pretty sure no
> one has logged on or tried to do anything yet.
>
> When I issue  uname -a to find out the kernel version, I get: Linux
> Red53.idp.com 2.6.18-128.el5 #1 SMP Wed Dec 17 11:45:02 EST 2008 s390x s3x
>
> Can anyone tell me what I'm missing, or not doing correctly?
> Are there other commands to find out what version the kernel is?
> If I just issue mkinitrd, like I do on Suse, I get the following:
> usage: mkinitrd [--version] [--help] [-v] [-f] [--preload ]
>[--force-ide-probe] [--force-scsi-probe | --omit-scsi-modules]
>[--image-version] [--force-raid-probe | --omit-raid-modules]
>[--with=] [--force-lvm-probe | --omit-lvm-modules]
>[--builtin=] [--net-dev=]
>[--without-usb] [--without-multipath] [--without-dmraid]
>[--fstab=] [--nocompress]  
>
>(ex: mkinitrd /boot/initrd-2.2.5-15.img 2.2.5-15)
>
> How do I get the new dasd added to this RedHat system?
>
> Thanks to anyone who can help.
>
> Sue Sivets
>
> --
>  Suzanne Sivets
>  Systems Programmer
>  Innovation Data Processing
>  275 Paterson Ave
>  Little Falls, NJ 07424-1658
>  973-890-7300
>  Fax 973-890-7147
>  ssiv...@fdrinnovation.com
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: How to tell how many linux running on z/VM?

[RPN01]

This will work if you've named all your images with the word "linux" in the
user ID, and have not done something like 'linuxmon' for a monitor, etc.

In the real world, "linux" uses up far too many characters to leave any hope
of having a descriptive name to identify the ownership or use of the image.
True, you can number the images, and allow for 1000 users (linux000 to
linux999), and more if you throw in some letters as well. But, when an
auditor asks what linux427 does, can you give him an immediate answer, or do
you need to go look it up? And more often, if you get a call in the middle
of the night that linux427 is unresponsive, is it a production, development,
or sandbox image, and do you want to have to get out of bed to find out?

Just thoughts. For the most part, your command will not work on the vast
majority of systems. Using it here, I have no linux images running, based on
the output of your command.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 8/13/09 6:32 AM, "Richard Heimo"  wrote:

> Hello
>
> Try from a guest:
>
> vmcp q n | tr ' ' '\n' | grep -i linux | wc -l
>
> Best regards
> Richard
>
> -Original Message-
> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of And Get
> Involved
> Sent: Wednesday, August 12, 2009 11:50 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: How to tell how many linux running on z/VM?
>
> I was asked to find out how many linux guests are running on our  z/VM?
> the cp commands:Q N is not very suitable for this question.
> What is the better way?
>
> This message is intended only for the addressee.  It may contain privileged or
> confidential information.  Any unauthorized disclosure is strictly prohibited.
> If you have received this message in error, please notify us immediately so
> that we may correct our internal records.  Please then delete the original
> email.  Thank you. (Sent by Webgate1)
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: OT (was Re: RHEL 5.4 Beta is out in the wild)

[RPN01]

Yup, beyond all doubt.

But "foo" was still the license plate on Smokey Stover's car and has nothing
to do with "fubar" or "foobar".

It may have been Pascal, but I had a textbook whose favorite variable names
were foo, bar and foobar.

-- 
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 7/2/09 11:14 AM, "Ed Long"  wrote:

> FOOBAR dates from WW2 where it was more commonly spelled FUBAR.
> The polite definition is fouled up beyond all recognition.
> Guess what the real definition is!
> 
> Edward Long
> 
> 
> --- On Thu, 7/2/09, RPN01  wrote:
> 
>> From: RPN01 
>> Subject: Re: OT (was Re: RHEL 5.4 Beta is out in the wild)
>> To: LINUX-390@VM.MARIST.EDU
>> Date: Thursday, July 2, 2009, 11:45 AM
>> Actually, "foo" is unrelated to
>> "fubar". Foo was the licence plate on Smokey
>> Stover's two wheeled car in the comic strips, dating back
>> to the 1920's or
>> 1930's. "Fubar" and "foobar" came into use later, as far as
>> I can tell, but
>> it's hard to trace things like that.
>> 
>> --
>> Robert P. Nix          Mayo
>> Foundation        .~.
>> RO-OE-5-55         
>>    200 First Street SW    /V\
>> 507-284-0844       
>>    Rochester, MN 55905   /(
>> )\
>> -             
>>                
>>           ^^-^^
>> "In theory, theory and practice are the same, but
>>  in practice, theory and practice are different."
>> 
>> 
>> 
>> 
>> On 7/2/09 8:20 AM, "Michael MacIsaac" 
>> wrote:
>> 
>>> Rob,
>>> 
>>>> Maybe you could get a position at the ITSO as an
>> editor and flag
>>>> the phrase "kill a daemon"
>>> 
>>> I recently got a variable named "foo" edited out by an
>> ITSO editor.
>>> Because everyone knows that foo is a variant of fubar
>> which is an acronym
>>> with a *bad word* in it - "foo" might offend a
>> reader.  The compromise was
>>> to name the variable "goo".
>>> 
>>> The next step may be to disallow all variables
>> starting with "f", and who
>>> knows, maybe "s" too, for good measure :))
>>> 
>>> "Mike MacIsaac"    (845)
>> 433-7061
>>> 
>>> 
>> --
>>> For LINUX-390 subscribe / signoff / archive access
>> instructions,
>>> send email to lists...@vm.marist.edu
>> 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 lists...@vm.marist.edu
>> 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: OT (was Re: RHEL 5.4 Beta is out in the wild)

[RPN01]

Actually, "foo" is unrelated to "fubar". Foo was the licence plate on Smokey
Stover's two wheeled car in the comic strips, dating back to the 1920's or
1930's. "Fubar" and "foobar" came into use later, as far as I can tell, but
it's hard to trace things like that.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 7/2/09 8:20 AM, "Michael MacIsaac"  wrote:

> Rob,
>
>> Maybe you could get a position at the ITSO as an editor and flag
>> the phrase "kill a daemon"
>
> I recently got a variable named "foo" edited out by an ITSO editor.
> Because everyone knows that foo is a variant of fubar which is an acronym
> with a *bad word* in it - "foo" might offend a reader.  The compromise was
> to name the variable "goo".
>
> The next step may be to disallow all variables starting with "f", and who
> knows, maybe "s" too, for good measure :))
>
> "Mike MacIsaac"(845) 433-7061
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: To kick or to clone ... that is the question

[RPN01]

Another point is that cloning can take advantage of the IBM DASD Flashcopy,
which Kickstart cannot. In our cloning process, copying the volumes with DDR
takes roughly 8 seconds or so, for two 3390-27's. Kickstart can't copy the
data onto the DASD that fast, so I don't see how it could be quicker in any
sense.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 6/10/09 7:55 AM, "Scott Rohling"  wrote:

> Hi Doug --  Yep, we sure had some fun kicking Linux servers!
>
> Not sure how Linux not doing restarting itself is an IBM issue...  but that
> 'is' a nasty downside to kickstarting -- ending up at a 'You may safely
> reboot' screen doesn't help automation.
>
> And we should add that kickstarting is faster than cloning 'if' the DASD is
> already Linux formatted.. if not, the kickstart does the formatting, adding
> time to the install.
>
> Scot
>
> On Tue, Jun 9, 2009 at 11:39 PM, WILLIAM CARROLL  wrote:
>
>> Hi Scott,
>>
>> I'll jump on your bandwagon but then again you already know I perfer
>> Kickstarting over cloning
>> you should also mention that unless you have Flashcopy for your DASD
>> Kickstarting is actually faster than cloning.
>> unless your clone master is very small.
>>
>> as you recall ours was on a mod3 (lots of required garbage)  and cloning
>> that mod3 was slower than kickstarting
>> also after the kickstart was done the server was ready,  no additional
>> steps
>> to change IP's or anything.
>>
>> if only redhat would fix that re-ipl after the reboot.
>> they say it's an IBM issue not thiers
>>
>> Doug Carroll
>>
>>
>>
>> - Original Message -
>> From: "Scott Rohling" 
>> To: 
>> Sent: Wednesday, June 10, 2009 12:00 AM
>> Subject: To kick or to clone ... that is the question
>>
>>
>>  This is a blatant request for discussion about the pros and cons of using
>>> an
>>> automated installation (e.g. RH kickstart - Suse autoyast (though maybe
>>> this
>>> has changed - I'm not current on Suse) - vs cloning a system from a
>>> 'golden
>>> image'...   and I should say:   on zSeries.
>>>
>>> I'm a fan of kickstart - and I'll list my reasons in approximate order of
>>> importantance to me (most to least):
>>>
>>> - kickstart forces a scripted and recreatable installation.   You specify
>>> the rpm's and can do some limited scripting within the kickstart file
>>> itself
>>> to end up with (hopefully) a working Linux system that requires no manual
>>> tweaking (at least - if you do it 'right').  The alternative is a cloned
>>> system that the Linux SA's have been on, and perhaps several other teams -
>>> all performing manual tasks to end up with the final product - all sorts
>>> of
>>> shoeprints and no good detectives.  Whereas a kickstart config is
>>> self-documenting - a clone is not.   With good scripting and good use of
>>> rpm
>>> packaging for your 'local' or even 'vendor' products - you can end up with
>>> a
>>> very KISS config file that might even go multiplatform.  (e.g. arch=`uname
>>> -m` )
>>>
>>> - with a proper building of conf and parm files on z/VM - a guest can be
>>> kicked already configured with a working network -- no need for some
>>> outside
>>> scripting or manual config.
>>>
>>> - you can have different kickstart files for different server 'types'
>>> (web,
>>> app, db, etc) - these can even be built dynamically and requested via a
>>> URL
>>> to to the kickstart ( e.g.
>>> http://mykicker/kick.web&ip=xx.xx.xx.xx+etc+etc.)
>>>
>>> - The size of the DASD can be flexible..   cloning requires copying the
>>> same
>>> size DASD as the source..
>>>
>>> -  The latest fixes can be applied by keeping the repository the kickstart
>>> uses current - rather than updating a clone source.  (of course - testing
>>> is
>>> still required and would require kickstarting a guest to truly do any
>>> testing - a good thing imo)
>>>
>>> -  It encourages packing by rpm rather than manual 'tarball' methods..
>>> this
>>> is in line with a 'recreatable' install.   Yes, you can still do 'tar'
>>> commands in the kickstart file itself..  but specifying an rpm package is
>>> oh
>>> so much easier.
>>>
>>> -  Servers start 'clean' - ie no old log files from the clone source and
>>> no
>>> need to try and script a 'cleanup'
>>>
>>> -  No worrying about whether a clone source is 'up' when a new server is
>>> clone and possibly clone a live system
>>>
>>>
>>> There are downsides..  but I'll leave those to the rest of you to expound
>>> on, since I'm taking a position of 'kickstart good, Jane'
>>>
>>> Thanks and hope this is valuable to some ..
>>>
>>> Scott
>>>
>>> --
>>> For LINUX-390 subscribe / signoff / archive access instructions,
>>> send email to lists...@vm.m

Re: vswitch for everyone

[RPN01]

None of the z/Linux guests run in anything more than a class G user on z/VM,
so they really don't have any "magic" facilities within z/VM via the root
userid. For the images that the end user has root access, if they want to
mess around and screw up their virtual machine, isn't that their right? And
a simple logout / login will reset anything they've done, because DirMaint
is a CMS facility, and CMS isn't running there for them to invoke any
commands. 

In addition, the users with root access are from an Intel background, and
would have to find and implement the z/VM additions before they could even
begin to touch their environment. While it could happen, it isn't likely.

-- 
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 4/21/09 6:10 PM, "Rob van der Heij"  wrote:

> On Wed, Apr 22, 2009 at 12:09 AM, Patrick Spinler
>  wrote:
> 
>>> Your scope should probably include the users of your applications that
>>> run on Linux, not just the few people who have legal permission to
>>> logon to a VM userid.
>> 
>> Err, why?  We already have a heterogeneous Unix LDAP solution that
>> serves our virtual linux, distributed linux, solaris, and AIX systems.
>> Note that our Z hosted linux guests are only about 1/4 of the total
>> number of these.   Why in the world would we want to segregate our
>> z/Linux security to a completely separate security system than all the
>> rest of our unix and linux?
> 
> Ok, I see where this went wrong... You can certainly use those central
> solutions to manage application access for Linux on z/VM.
> 
> What I meant to say is that z/VM security is not just for the users
> with legal access. Someone with root access on your Linux server could
> also do things on z/VM that you don't want. z/VM is your virtual
> "raised floor" and when you allow more folks access to the computer
> room, you may need to tighten some of the rules and procedures you
> follow.
> 
> -Rob
> 
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: vswitch for everyone

[RPN01]

The problem is that not everyone wants to purchase an external security
manager simply to get this feature. We have no need for an ESM, as, if one
of our four users get out of line, we can just walk over to their cube and
whack them with a board. I'm not buying an ESM to un-secure a single entity
in an already closed box. That makes no sense at all.

No humans use the box directly, and we grant the vSwitch to just short of
every virtual machine that uses the box. To have to go through the grant
process, no matter if it is in the CP directory, in System Config, or in
Autolog1, for every new machine that gets created, and to open the door for
human error by forgetting to grant this resource, which needs to be
available for everyone on the system, seems at best to be an oversight on
IBM's part.

ESMs are not the solution to this problem. Sorry.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 4/17/09 12:20 AM, "Alan Altmark"  wrote:

> On Thursday, 04/16/2009 at 04:15 EDT, Marcy Cortes
>  wrote:
>
>> Apparently its *someone*'s requirement, but I agree, and optional open
>> Vswitch would be handy indeed.
>
> I should probably get the requirement answered "Available".  As Rob
> mentioned, your ESM is capable of doing this. With RACF, RALTER VMLAN
> SYSTEM.VSWITCH1 UACC(READ).
>
> I have no plan (or much willingness) to spend money to duplicate in CP
> what can be done with an ESM.
>
> Alan Altmark
> z/VM Development
> IBM Endicott
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: vswitch for everyone

[RPN01]

That would be my desire as well, but IBM says it is what it is for security
reasons.

Evidently, a rogue Linux guest could appear on your system, connect to the
vSwitch and reek havoc on your network. Nobody's ever told me where this
rogue image is supposed to come from, and in our case, there are only four
"people" users allowed on either of our systems.

Having an open vSwitch would be handy, or just a way to grant * or grant
all. The way it is now is such a pain.


--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 4/15/09 3:26 AM, "Andrew Avramenko"  wrote:

> Colleagues,
>
>
> Does anybody know is it possible to create vswitch which will be
> unaware to access permissions, so every guest can connect to it and I
> don't need to run modify vswitch grant access every time?
>
> Thank You in advance.
>
>
>
>
> --
> With best regards,
> Andrew
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

IBM License Metric Tool - Administration Server requirements...

[RPN01]

Is anyone running the IBM License Metric Tool ­ Administration Server on
zLinux? We were asked to create an image for this, but in looking at the
requirements, it lists ³one dedicated processor².

If you¹re running this on z, what are your experiences? And does it, indeed,
require a whole processor? I¹m hoping that it¹s just a CYA type statement,
as I don¹t have a complete processor to spare simply for license management.

If we don¹t give it its own dedicated processor, how badly will its
performance suffer? How badly will the other virtual images it competes with
suffer?

-- 
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Posting etiquette

[RPN01]

The problem I have with job postings is that receiving them here is a
violation of company policy. Management takes it as doing a job search on
company time.

If there are too many, then I'll have to leave the list, or lose my job and
generate the need to see the listings.

I'd prefer to not see postings containing job listings. I like the list, use
the list, and would like to stay subscribed. I like my job, need my job, and
would like to stay employed.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 3/14/09 10:59 PM, "Douglas M. Wooster"  wrote:

> As one of those recently laid off, I wholeheartedly agree. :)
>
> Douglas
>
> On Fri March 13 2009, Schneck.Glenn <"Schneck.Glenn"
> > wrote:
>> Mark,
>>
>> I have seen job postings on other lists and personally don't see an
>> issue with them.  In this economic climate and the potential of
>> each of us being laid off any avenue for employment is appreciated,
>> IMHO.
>>
>> Glenn
>>
>> Glenn A. Schneck
>> AVP, Managed Services, Transaction Services
>> SunTrust Banks, Inc.
>> 407-762-3514 (office)
>> 407-625-2596 (cell)
>> glenn.schn...@suntrust.com
>> Live Solid. Bank Solid.
>>
>>
>>
>> -Original Message-
>> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf
>> Of Mark Barajas
>> Sent: Friday, March 13, 2009 1:09 PM
>> To: LINUX-390@VM.MARIST.EDU
>> Subject: Re: Posting etiquette
>>
>> Ladies and Gentlemen,
>>
>>
>>
>> I have a question about etiquette of postings into this email list.
>> I've been monitoring and most of the postings are about asking and
>> sharing of technical issues encountered during day to day
>> activities and once in a while about events to benefit everyone.
>> Even once or twice I have seen several of the members posting
>> having to move on.  On the last one; I would like to know what
>> would be or if it would be possible for posting for employment
>> opportunities.  If this is not the right spot to find folks with
>> this groups skill sets ... would someone be able to direct me to
>> where I might be able to post and find folks?
>>
>>
>>
>> PS This is my first post to the email list and hope that I'm not
>> breaking too many rules.
>>
>>
>>
>> Thanks
>>
>>
>>
>> Mark Barajas
>> Data Center Technologies
>> Accenture - Infrastructure Consulting & Enterprise Architecture
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: starting 'at the begining' to install linux on z/os

[RPN01]

Linux does not install on z/OS. No other operating system does.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 3/13/09 10:06 AM, "Gear, Steven"  wrote:

>
>  Hello,
>
>   I am at the beginning of installing Linux on z/os. I thinking just in an
> Lpar or two for now, z/vm later. This is an R&D project just to get it up and
> running. I have a Z9 and a copy of SUSE. Now what? What would be the best
> redbook or manual?
>
> Thanks,
>   steve
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: How to determine which lpar a linux guest is hosted on ?

[RPN01]

To get at the original question, try "vmcp q userid" and look in the third
token in the response. This should tell you which system you're on. Or are
you really looking for the LPAR name?


--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."





On 2/19/09 1:14 PM, "Scott Rohling"  wrote:

> Do a HELP CPQUERY LPARS ..   there are a few conditions for this command to
> work -- one is dynamic i/o turned on.
>
> Scott
>
> On Thu, Feb 19, 2009 at 12:04 PM, Bernie Wu  wrote:
>
>> Hi Richard,
>> When I try "vmcp q lpars" this is what I get :
>> No LPAR data is available
>>
>> Is this indicative of a zVM install problem ?
>>
>> Bernie Wu
>>
>> -Original Message-
>> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
>> Richard Gasiorowski
>> Sent: Thursday, February 19, 2009 10:27 AM
>> To: LINUX-390@VM.MARIST.EDU
>> Subject: Re: How to determine which lpar a linux guest is hosted on ?
>>
>> you can use vmcp q lpars if you have the correct authorization for CP
>> queries
>>
>> 'Where ever you go - There you are!! '
>> Richard (Gaz) Gasiorowski
>> System z - Linux Product Manager
>> Portfolio Platform Services
>> CSC
>> 3170 Fairview Park Dr., Falls Church, VA 22042
>> 845-773-9243 Work|845-392-7889 Cell|rgasi...@csc.com|www.csc.com
>>
>>
>>
>>
>> This is a PRIVATE message. If you are not the intended recipient, please
>> delete without copying and kindly advise us by e-mail of the mistake in
>> delivery.
>> NOTE: Regardless of content, this e-mail shall not operate to bind CSC to
>> any order or other contract unless pursuant to explicit written agreement
>> or government initiative expressly permitting the use of e-mail for such
>> purpose.
>>
>>
>>
>> Stewart Thomas J 
>> Sent by: Linux on 390 Port 
>> 02/19/2009 10:12 AM
>> Please respond to
>> Linux on 390 Port 
>>
>>
>> To
>> LINUX-390@VM.MARIST.EDU
>> cc
>>
>> Subject
>> Re: How to determine which lpar a linux guest is hosted on ?
>>
>>
>>
>>
>>
>>
>> On my RHEL4 system, I use cat /proc/sysinfo and it indicates the LPAR name
>> and guest name.
>>
>>
>>
>> -Original Message-
>> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
>> Bernie Wu
>> Sent: Thursday, February 19, 2009 9:09 AM
>> To: LINUX-390@VM.MARIST.EDU
>> Subject: How to determine which lpar a linux guest is hosted on ?
>>
>> Hi Listers,
>> We have 2 LPARS, each hosting VM, which in turn hosts several linux
>> guests.
>> From a Linux guest, how do I determine which LPAR the guest is on ?
>>
>> TIA
>> Bernie Wu
>>
>> 
>> The information contained in this e-mail message is intended only for the
>> personal and confidential use of the recipient(s) named above. This
>> message may be an attorney-client communication and/or work product and as
>> such is privileged and confidential. If the reader of this message is not
>> the intended recipient or an agent responsible for delivering it to the
>> intended recipient, you are hereby notified that you have received this
>> document in error and that any review, dissemination, distribution, or
>> copying of this message is strictly prohibited. If you have received this
>> communication in error, please notify us immediately by e-mail, and delete
>> the original message.
>>
>> --
>> For LINUX-390 subscribe / signoff / archive access instructions, send
>> email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or
>> visit
>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>>
>> The information contained in this e-mail message is intended only for the
>> personal and confidential use of the recipient(s) named above. This message
>> may be an attorney-client communication and/or work product and as such is
>> privileged and confidential. If the reader of this message is not the
>> intended recipient or an agent responsible for delivering it to the intended
>> recipient, you are hereby notified that you have received this document in
>> error and that any review, dissemination, distribution, or copying of this
>> message is strictly prohibited. If you have received this communication in
>> error, please 

Newer versions of Java for SuSE SLES 9

[RPN01]

I have a customer asking for a more recent version of Java than 1.4.2.
They¹re running on SuSE SLES 9 at the moment. Is there somewhere I could
find an install of Java 1.5.09 or higher, that we could put into a separate
path, and not disturb the Java that came with the distribution?

-- 
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: System Mail consolidation

[RPN01]

In the root userid, you can add a .forward file, pointing to where you'd
like the e-mail messages to flow. This will forward everything to a central
e-mail address.

You can use syslog to route the console messages to a central syslog sink to
collect all the other messages to one location.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 1/15/09 4:29 AM, "Ceruti, Gerard G" 
wrote:

> Hi All
>
> Does anyone collect the System emails generated by Linux images in a
> central location, currently I invoke the "mail" command on each image
> but  I would like to look in one location,
> This location could be a pc or a System z Linux image. Any ideas.
>
> Regards
> Gerard Ceruti
> may the 'z' be with you
>
>
> __
> ___
>
> Standard Bank email Disclaimer and confidentiality note
>
> This e-mail, its attachments and any rights attaching hereto are, unless the
> content clearly indicates otherwise, the property of
> Standard Bank Group Limited and its subsidiaries. It is confidential, private
> and intended for only the addressee.
>
> Should you not be the addressee and receive this e-mail by mistake, kindly
> notify the sender, and delete this e-mail immediately.
> Do not disclose or use it in any way. Views and opinions expressed in this
> e-mail are those of the sender unless clearly stated as
> those of Standard Bank Group.
>
> Standard Bank Group accepts no liability for any loss or damages howsoever
> incurred, or suffered, resulting, or arising,
> from the use of this email or its attachments.
>
> Standard Bank Group does not warrant the integrity of this e-mail nor that it
> is free of errors, viruses, interception or interference.
>
> Licensed divisions of the Standard Bank Group are authorised financial
> services providers in terms of the Financial Advisory and
> Intermediary Services Act, No 37 of 2002 (FAIS).
>
> For information about the Standard Bank Group visit our website
> http://www.standardbank.com
> __
> __
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Boot after cloning: SLES10

[RPN01]

The best place to "fix" this is in the system you're using as a source for
the clone. What good is cloning, if, after every clone, you have to go in
and make hand modifications?

Change your source system to use by-path. Then you won't have a problem with
any of the clones. And, since you're just cloning, and can't get through the
second boot, scratch this clone and recreate it with the corrected source.

It's not worth fighting, when you need to fix the source system anyway.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 12/8/08 4:17 PM, "Tom Duerbusch" <[EMAIL PROTECTED]> wrote:

> I hit the same problem as others (reference back in November), but I knew that
> a solution already exists..
>
> OK, so where is it?  As in on your website?
>
> Tom Duerbusch
> THD Consulting
>
> "You need to boot a rescue system with the disks for the problem system
> attached and change /etc/fstab to by-path. We wrote a script to do this for
> you -- check sinenomine.net for a copy."
>
> --
> 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

Re: programming question: OPEN options

[RPN01]

It really depends on if the logging program keeps the file open on a file
handle, or opens and closes the log file as it has things to add. If you mv
the log within the same filesystem, many times the logging program will just
continue to log to the original file in its new location.

Basically, you'll get varying results doing things like this, so everyone's
mileage will vary.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 11/6/08 7:24 PM, "John Summerfield" <[EMAIL PROTECTED]>
wrote:

> John McKown wrote:
>> I was just having a discussion here. We had a Tomcat log file exhaust all
>> the space on a filesystem. An Oracle person said that they often
>> "truncate" Oracle logs, while Oracle is still running by doing something
>> like:
>>
>> cp oracle.log /some/other/filesystem
>
> That copies the oracle log, it does not change it.
>
>> tail -20 /some/other/filesystem/oracle.log oracle.log
>
> That prints the last 20 records of each.
>
> Possibly, someone meant
> tail -20 /some/other/filesystem/oracle.log >oracle.log
>
> I wouldn't think that would do anything but corrupt the log, but I don't
>   have a log file I care to try it on.
>
> At the very least, there's a race condition, and anything logged between
> the completion of the mv command and the tail command working (if indeed
> it does, and that I doubt) is lost. And you know what Murphy said!
>
>
>>
>> He indicated that this causes the file to shrink in size and Oracle then
>> continues logging after the 20 records copied.
>>
>> I'm thinking that this is dependant on Oracle, or whatever application,
>> using the O_APPEND option on the fopen() call. If the program doesn't use
>> O_APPEND, then the space is not released and the program continues writing
>> at the end and the file continues to increase in size.
>>
>> Am I understanding this correctly?
>
> What might work, if tomcat is written for it to work, is something like
> this:
> mv tomcat.log tomcat.log.0
> service tomcat reload
>
> There's no file locking, so the mv renames the file while it's being
> written. I would not move it to another filesystem at this point, harm
> will ensue.
>
> Ordinarily, the service command runs the named script from /etc/init.d
> and the reload argument sends a SIGHUP signal to the application, and by
> convention, the application rereads its configuration and closes/opens
> its logs. Whether this works with tomcat is something you need to
> explore in its documentation.
>
> You have an application, logrotate, that can (and should) do this. It is
> configurable as to how many logs are kept and whether they are
> compressed. From its man page:
> LOGROTATE(8) System Administrator's Manual
> LOGROTATE(8)
>
> NAME
> logrotate - rotates, compresses, and mails system logs
>
> SYNOPSIS
> logrotate [-dv] [-f|--force] [-s|--state file] config_file+
>
> DESCRIPTION
> logrotate  is  designed  to  ease  administration of systems
> that generate large numbers of log files.  It allows automatic
> rotation, compression, removal, and mailing of log files.  Each
> log file may be handled daily, weekly, monthly, or when  it
> grows too large.
>
>
>
>>
>> --
>> Q: What do theoretical physicists drink beer from?
>> A: Ein Stein.
>>
>> Maranatha!
>> John McKown
>>
>> --
>> 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
>>
>
>
> --
>
> Cheers
> John
>
> -- spambait
> [EMAIL PROTECTED]  [EMAIL PROTECTED]
> -- Advice
> http://webfoot.com/advice/email.top.php
> http://www.catb.org/~esr/faqs/smart-questions.html
> http://support.microsoft.com/kb/555375
>
> You cannot reply off-list:-)
>
> --
> 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

Re: Lx86

[RPN01]

I think the problems are the vended products for which you cannot obtain
source, and for which the vendor is unable or unwilling to create zSeries
binaries.

An Intel binary executor on p Series makes sense for this; you can move the
product and run it, with very little hassle. This would be a fine solution
for z Series as well, if it were available, but I don't see it happening.

We've "lost" several internal customers because they were running a vended
product that could not be converted to z. We catch them again with Blades
and VMWare and standalone systems, but they aren't a good fit for z no
matter how hard you push.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 10/19/08 9:19 AM, "John Summerfield" <[EMAIL PROTECTED]>
wrote:


> Originally, you asked about a solution to a problem.
>
> What problem are you trying to solve?
>
> If you have a bunch of Intellish servers running Linux, the usual way to
> transfer the workload is to create a Linux server on a zSeries (virtual)
> machine. It would run a Linux kernel compiled for zSeries, apache built
> for zSeries, DB2, Oracle, etc built for zSeries, Java built for zSeries.
>
> One does _not_ transfer the Intellish binaries, one creates a system
> with equivalent zSeries binaries.
>
> One _can_ transfer files and even filesystems, Linux uses the same
> encoding on all platforms and filesystems code is written to not care
> about endianness.
>
> I am _not_ sure about floating point numbers.
>
> If you have your own programs written for Linux on intellish hardware,
> and the code follows sensible rules (eg no assembly code, no referencing
>   ints as a sequence of chars setc), odds are good it will port with
> minimal fuss and bother.
>
> I repeat, what problem are you trying to solve?
>
>
> --
>
> Cheers
> John
>
> -- spambait
> [EMAIL PROTECTED]  [EMAIL PROTECTED]
> -- Advice
> http://webfoot.com/advice/email.top.php
> http://www.catb.org/~esr/faqs/smart-questions.html
> http://support.microsoft.com/kb/555375
>
> You cannot reply off-list:-)
>
> --
> 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

Re: Lx86

[RPN01]

I fail to see what z/OS has to do with any of the discussion at all. I
thought we were comparing to zLinux and the z/VM environment. zLinux is much
closer to Linux than AIX is... Because it IS Linux. It can run bare bones,
or using z/VM as a hipervisor, and z/OS doesn't have to be present at all.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 10/18/08 6:24 PM, "John McKown" <[EMAIL PROTECTED]> wrote:

>
> From what I understand of how IBM divisons work, this is considered
> normal. The System p people will attempt to take business from the System
> z people and vice versa. It is not one big happy family. I will grant that
> perhaps the p people would be more likely to go after HP or Intel markets,
> but that is because that AIX is closer to Linux or HP-UX, than z/OS, so it
> is an easier sale. But the p people will compete with the z people over a
> possible Linux account.

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

Re: Lx86

[RPN01]

Not every site will have the environment, structure, or support personnel to
install and maintain a z Series system and keep up with its needs. In order
to cover as many markets as possible, I think it is wise of IBM to supply
the alternative structure in the p Series machines. This covers the market
from two angles, and either way the customer goes, IBM still gets the money,
so it's a win for them.

They are still THINKing...

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 10/18/08 7:07 AM, "Richard Gasiorowski" <[EMAIL PROTECTED]> wrote:

> I must be missing something.  My original question was does IBM have an
> LX86 product for zLinux. The answer is no.  So are you other vendors
> saying you have something that works or not.  I am not talking windows
> servers-  Linux servers.  Personally I am surprsied that IBM presents
> zLinux as a platform to migrate many small linux x86 servers.  It also
> states that the system p competes with the Unix large Suns and HP. Then
> turns around and makes a product for the system p to address a need which
> zlinux could use.  Very strategic and logical thinking.  No wonder they no
> longer use THINK as their motto.

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

Re: Lx86

[RPN01]

I thought that graphics, in general, was not a good use of the System Z
resources?.? Aren't you looking at putting a high CPU load task onto the
mainframe server, rather than farming it out to the desktop, where it
belongs?

Now, maybe Windows servers would be a different idea altogether...

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 10/16/08 9:18 AM, "Rich Smrcina" <[EMAIL PROTECTED]> wrote:

> Richard Gasiorowski wrote:
>> Question for someone @ IBM.  Lx86 is a feature provided for on the p
>> series whihc allows Linux binaries to execute on the p system without a
>> recompile.
>> Since IBM professes a philosophy of providing like platform capabilities.
>> the question is
>>
>> When can we expect this features functions available on the system z?  I
>> would definitely sign up for alpha or beta testing of this.
>
> Watch this space...
>
> In Q1 2009 Mantissa will deliver a system that permits unaltered Windows
> operating systems to run under z/VM. Using a desktop appliance running RDC,
> users will be able to connect to their virtual Windows images running in the
> VM environment. Goodbye desktop hardware, remote maintenance, high power
> consumption, machine order lead time.
>
> --
>
> Rich Smrcina
> VM Assist, Inc.
> Phone: 414-491-6001
> Ans Service:  360-715-2467
> rich.smrcina at vmassist.com
> http://www.linkedin.com/in/richsmrcina
>
> Catch the WAVV!  http://www.wavv.org
> WAVV 2009 - Orlando, FL - May 15-19, 2009
>
> --
> 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

Re: Buggered up zipl.conf file

[RPN01]

Boot up your install system, and define the network. Get things up to the
point that ssh is started. Then log in via ssh, mount your real Linux
system's filesystem and once everything is in place beneath this mount
point, do a chroot to the mountpoint. Then edit your zipl.conf file, and
re-run mkinitrd and zipl. Shutdown and try to boot again.

My assumption here is that this is your first linux image. If you have
others, you could attach the necessary disks to a running image, mount them
and chroot to there.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 8/29/08 1:51 PM, "Rakoczy, Dave" <[EMAIL PROTECTED]> wrote:

>
> All,
>
> Being a zLinux Newbie I'm following Chapter 7. (installing and
> configuring SLES10) in the  'z/VM and Linux on IBM System z The
> Virtualization Cookbook'
>
> Step 7.5.13 identifies modifications to make to the zipl.conf file.
>
> Well... Here's where the problem lies... I fat fingered the parameter
> line and went ahead and executed the zipl command.  Now when I try to
> IPL I get the following message.
>
> Waiting for device /dev/dasd1 to appear:
> ..not found
>  -- exiting to /bin/sh
>
> $
>
>
> The device I should be looking for is /dev/dasda1not
> /dev/dasd1.
>
> Can anyone offer any insight on how I can save this install without
> starting all over again?
>
> This is just a sandbox system I'm playing with for the time being, I was
> hoping this was going to become my "Gold" system eventually.
>
> Thanks in advance for any assistance.
>
> And yes... I do have a backup of the zipl.conf file, I just have no idea
> on how to restore it and re-run the zipl command without the actual
> system.
>
> David Rakoczy
> Operating Systems Programmer
> Thermo Fisher Scientific
>
> "He who laughs last probably made a backup."
>
>
>
> --
> 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

Re: Linux version

[RPN01]

Unfortunately, as has been mentioned, there's no way to know with any
certainty just how to identify what distribution you're on. Just where would
uname get the information, when we can't agree on where to find it by hand?

It's certainly not the kernel's job to know what distribution it came with.
You could put the burdon on the distribution creator by adding some feature
to uname, and then hoping that the various distributions would buy into the
change and comply with whatever means you used to identify the distribution
and version... But I wouldn't count on it. The various distributions can't
even agree on a filename format that would lend itself to easy use.

SuSE supplies a command "SPident" which returns the "found" and "expected"
versions of the distribution, though I've never been able to get it to
respond with what I expected. The system I'm looking at right now "expects"
SLES-9-s390x-SP4, but "finds" SLES-9-s390x-SP1 + "online updates". On one of
my SLES 10 images, I get SLE-10-s390x-SP1 + "online updates", so the output
doesn't conform from release to release either. We went from "SLES" to
"SLE". The SPident command is notably absent from my RedHat systems.

So in summary, there seems to be no simple way, either manual or automated,
of knowing what distribution you're on, without prior knowledge of what
distribution you're on.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 8/20/08 2:01 AM, "Mark Perry" <[EMAIL PROTECTED]> wrote:


>
> Thought
> wouldn't it be nice if another option were added to the uname command
> that listed Distributor info?
>
> It could at a minimum do the functional equivalent of "cat
> /etc/distro-info" and each distributor could set a softlink to their own
> existing files, or patches could be applied to uname to supply the info
> "inline".
>
> Then customers could do something like uname -V or uname -D and have a
> consistent method of obtaining distributor information.
>
> mark

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

Re: Finally getting into zFCP...

[RPN01]

Actually, I just found a reference saying that the second and fourth fields
are obsolete anyway, so it may not matter what is coded there.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 8/18/08 10:37 AM, "Spann, Elizebeth (Betsie)" <[EMAIL PROTECTED]> wrote:

> I have coded both 0x01 and 0x00 on different servers.  If you code 0x00, that
> is host0 on the lszfcp display.
> Betsie
>
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01
> Sent: Monday, August 18, 2008 8:17 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Finally getting into zFCP...
>
> I read somewhere that the second column cannot be equal to zero. Is this not
> true?

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

Re: Finally getting into zFCP...

[RPN01]

I read somewhere that the second column cannot be equal to zero. Is this not
true?

-- 
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 8/13/08 4:01 PM, "Spann, Elizebeth (Betsie)" <[EMAIL PROTECTED]> wrote:

> Robert,
> Here's a sample /etc/zfcp.conf file
> 
> 0.0.0315 0x00 0x5006048ad5f09e01 0x00 0x0010
> 0.0.0315 0x00 0x5006048ad5f09e01 0x01 0x0011
> 0.0.0315 0x00 0x5006048ad5f09e01 0x02 0x0012
> 0.0.0315 0x00 0x5006048ad5f09e01 0x03 0x0013
> 0.0.0315 0x00 0x5006048ad5f09e01 0x04 0x0014
> 0.0.0315 0x00 0x5006048ad5f09e01 0x05 0x0025
> 0.0.0325 0x01 0x5006048ad5f09e0e 0x00 0x0010
> 0.0.0325 0x01 0x5006048ad5f09e0e 0x01 0x0011
> 0.0.0325 0x01 0x5006048ad5f09e0e 0x02 0x0012
> 0.0.0325 0x01 0x5006048ad5f09e0e 0x03 0x0013
> 0.0.0325 0x01 0x5006048ad5f09e0e 0x04 0x0014
> 0.0.0325 0x01 0x5006048ad5f09e0e 0x05 0x0025
> 
> There are 6 LUN's on two paths. The first field is the zfcp subchannel  (we
> code 300-31F on first chpid, 320-32F on second chpid, for example).
> Second field is 0x00 for first adapter, 0x01 for second adapter, 0x02 for
> third adapter, etc.
> The third field identifies the WWPN of the SCSI adapter (two in this example).
> Fourth field is the LUN sequence (0 thru 5 for six LUN's).
> Fifth is the LUN ID that I got from the SCSI vendor SE.
> 
> Betsie
>  
> 
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01
> Sent: Wednesday, August 13, 2008 1:48 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Finally getting into zFCP...
> 
> We¹re finally getting back around to ³playing² with zFCP, and I¹ve run into a
> possible bug
> 
> We¹re able to get things up and running by hand, and we¹re now trying to set
> things up to happen during the boot of the system. Everything points back
> around to a file called /etc/zfcp.conf, but there¹s very little on what¹s
> really required in the file (i.e. What the five fields really mean / where to
> go to get the information to fill them out). I think we¹ve figured them out,
> but it would have been more reassuring to have found some detailed
> documentation. Or maybe even a man page?
> 
> Also, there¹s a script called /sbin/zfcpconf.sh, that appears to be entirely
> wrong. It lops the 0x off the front of the device address, and uses it in the
> /sys directory path, but fails to add the ³0.0.² to the front of it.
> Could it have ever worked? I¹m not sure I see how... Adding in the ³0.0.² into
> the paths used in the script seems to make it work correctly.
> 
> The second question is, does this script actually get envoked during the boot?
> Or do we have to slip it in somewhere in the /etc/init.d path?

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

Finally getting into zFCP...

[RPN01]

We¹re finally getting back around to ³playing² with zFCP, and I¹ve run into
a possible bug

We¹re able to get things up and running by hand, and we¹re now trying to set
things up to happen during the boot of the system. Everything points back
around to a file called /etc/zfcp.conf, but there¹s very little on what¹s
really required in the file (i.e. What the five fields really mean / where
to go to get the information to fill them out). I think we¹ve figured them
out, but it would have been more reassuring to have found some detailed
documentation. Or maybe even a man page?

Also, there¹s a script called /sbin/zfcpconf.sh, that appears to be entirely
wrong. It lops the 0x off the front of the device address, and uses it in
the /sys directory path, but fails to add the ³0.0.² to the front of it.
Could it have ever worked? I¹m not sure I see how... Adding in the ³0.0.²
into the paths used in the script seems to make it work correctly.

The second question is, does this script actually get envoked during the
boot? Or do we have to slip it in somewhere in the /etc/init.d path?

-- 
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



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

Re: 3270 console confusion

[RPN01]

The positive part of adding the extra complexity comes when you want / need
to expand one of your logical volumes. This can be done via LVM fairly
easily, and in some cases, without even taking the filesystem offline. A
real, physical minidisk can't do this at all; you need to create an entirely
new disk, and copy the data from the old one to the new one. Then, you have
to replace the old one with the new one, possibly requiring the guest to be
brought down.

The other bad thing about avoiding LVM is that you are then limited by the
size of your largest physical disk. If all you have are 3390 mod 27's, then
you avoid your users when they need more than 22gig in a filesystem. We have
several filesystems on 3390 DASD that are half a terrabyte or larger, and
would not be possible without LVM.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 8/13/08 11:06 AM, "Rob van der Heij" <[EMAIL PROTECTED]> wrote:

> On Wed, Aug 13, 2008 at 5:50 PM, RPN01 <[EMAIL PROTECTED]> wrote:
>
>> Current standard here is to have /boot as a physical volume, root, var, tmp
>> and some swap (yes, we're moving to v-disk swap) in LVM vg_system on one
>> 3390 mod 9 and /home and /opt in LVM vg_local on a second 3390 mod 9. There
>> are pluses and minuses to having root in the LVM, but nothing tips the
>> scales greatly either way...
>
> I think that standard was inspired by experience on platforms where
> folks have just a single big disk rather than the option to create
> block devices as they like them. I understand the motivation to
> separate things in different disks, but to first bundle block devices
> in an LVM VG and then create LVs out of that, is a bit odd. It creates
> two additional layers of storage management that have a negative
> impact on performance and probably complicate things a lot.
>
> I strongly believe in separating application and operating system. And
> there's good reasons to have some things like /var and /tmp in
> separate file systems. But you can do with mini disks. Using the
> "first-aid" system approach, enlarging file systems on mini disk is
> not harder than with LVs
>
> Rob
>
> --
> 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

Re: 3270 console confusion

[RPN01]

Actually, you can get the VG configuration from the first few tracks of
cylinder zero of any of the physical volumes in the VG. You just need
something willing to dump it off so you can interpret it.

--
Bob Nix


On 8/13/08 11:01 AM, "Mark Post" <[EMAIL PROTECTED]> wrote:

>>>> On 8/13/2008 at  8:50 AM, in message <[EMAIL PROTECTED]>,
> RPN01 <[EMAIL PROTECTED]> wrote:
>> Current standard here is to have /boot as a physical volume, root, var, tmp
>> and some swap (yes, we're moving to v-disk swap) in LVM vg_system on one
>> 3390 mod 9 and /home and /opt in LVM vg_local on a second 3390 mod 9. There
>> are pluses and minuses to having root in the LVM, but nothing tips the
>> scales greatly either way...
>
> Just last week I was working with a customer on a problem with his Intel/AMD
> system.  He had / on an LV.  We couldn't get the VG to build.  We couldn't get
> to the LVM data in /etc/ because we couldn't get the VG to build.  I.e., there
> was no way to fix the problem.  He wound up restoring from backup.  Is that
> enough of a minus?
>
>
> 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

Re: 3270 console confusion

[RPN01]

Current standard here is to have /boot as a physical volume, root, var, tmp
and some swap (yes, we're moving to v-disk swap) in LVM vg_system on one
3390 mod 9 and /home and /opt in LVM vg_local on a second 3390 mod 9. There
are pluses and minuses to having root in the LVM, but nothing tips the
scales greatly either way...

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 8/13/08 10:33 AM, "Mark Post" <[EMAIL PROTECTED]> wrote:

>>>> On 8/13/2008 at  5:44 AM, in message <[EMAIL PROTECTED]>,
> RPN01 <[EMAIL PROTECTED]> wrote:
>> Our problem with this scenario comes from cloning and LVM: If the penguin is
>> a clone, its LVM volume groups are likely to have the same names as the
>> rescue penguin, in which case, you likely won't get them mounted properly.
>
> If you don't have your root file system on an LV, this is going to be
> irrelevant 99.9% of the time.  I've helped a few people that ran into this
> problem, but they were doing other things that didn't involve a non-networked
> system.
>
>
> 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

Re: 3270 console confusion

[RPN01]

Our problem with this scenario comes from cloning and LVM: If the penguin is
a clone, its LVM volume groups are likely to have the same names as the
rescue penguin, in which case, you likely won't get them mounted properly.
The only alternative would be to have a specifically designated "rescue"
system with strange (based on current practice) LVM and logical volume names
sitting idly by to serve this purpose, which we haven't taken time to do as
yet.

On the flip side, we've only ended up in the described situation once or
twice since we started, so it really hasn't come up as a huge issue as yet.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 8/12/08 6:03 PM, "Rob van der Heij" <[EMAIL PROTECTED]> wrote:

> On Tue, Aug 12, 2008 at 9:18 PM, RPN01 <[EMAIL PROTECTED]> wrote:
>
>> The linemode console is much more versatile, and the only time you'll
>> actually sit at it is when you're in trouble; at any other time, you'll just
>> walk away from it and use a ssh or telnet (not advised) connection.
>>
>> Learn a bit of sed or ed, and forget about the 3270.
>
> I second that. Even more flexible is to simply have a working trusted
> Linux server reach out and link the disks of the dead penguin, use all
> your favorite tools to repair things, release them again, and start
> the server. With some standardization in how you number the disks, you
> can write yourself a nifty bash script that does the hard things under
> the covers.
>
> -Rob
>
> --
> 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

Re: 3270 console confusion

[RPN01]

As near as I can tell, the problems created by a 3270 console outweigh the
benefits. Sure, you have a nifty 3270 interface that acts like z/VM and
z/OS, but you can't run the image disconnected, you can't spool the messages
from the console, and you have to sit there and clear the screen when it
fills.

The linemode console is much more versatile, and the only time you'll
actually sit at it is when you're in trouble; at any other time, you'll just
walk away from it and use a ssh or telnet (not advised) connection.

Learn a bit of sed or ed, and forget about the 3270.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 8/8/08 1:42 AM, "Robin Atwood" <[EMAIL PROTECTED]> wrote:

> I have found various threads about using NED on a 3270 console to zLinux and I
> thought this was a good idea. I read the 3270 HOWTO on linuxvm.org but it
> seemed no longer relevant to recent kernels; I am running 2.6.26. I have no
> tub3270 module so there is nothing under /proc/tty/drivers and so
> config3270.sh just exits. I had a read of the device drivers manual but am
> not sure what I need.
>
> I have a 3270 defined at 001f which gives me:
>
> # ll /sys/bus/ccw/drivers/3270
> total 0
> lrwxrwxrwx 1 root root0 Aug  8 13:37
> 0.0.001f -> ../../../../devices/css0/0.0./0.0.001f
> --w--- 1 root root 4096 Aug  8 13:37 bind
> --w--- 1 root root 4096 Aug  8 13:21 uevent
> --w--- 1 root root 4096 Aug  8 13:37 unbind
>
> but there are no tty devices. What do I do next?
>
> TIA
> -Robin
> --
> --
> Robin Atwood.
>
> "Ship me somewheres east of Suez, where the best is like the worst,
>  Where there ain't no Ten Commandments an' a man can raise a thirst"
>  from "Mandalay" by Rudyard Kipling
> --
>
> --
> 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

Re: vi alternative?

[RPN01]

Check your settings in putty; It prefers version 1 of the protocol, but most
systems now use version 2. In the list of setup pages, the setting appears
in one of the last ones. Don't even set it to dynamically go between 2 and
1; it'll still pick 1 every time and fail. Set it to 2.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 8/5/08 12:27 PM, "Stahr, Lea" <[EMAIL PROTECTED]> wrote:

> I have installed the SuSE 10 SP1 under my zVM 5.2. I chose to do the SSH
> install and it worked OK. When I tried to use PUTTY to access the
> system, it presented the LOGON and PASSWORD prompts but I always receive
> an ACCESS DENIED reply. I can SSH in from a SuSE 8 guest OK using the
> same userid and password.
>
> Is there a newer version of putty that I need?
>
> Lea Stahr
> zVM, Linux and zLinux Administrator
> Navistar, Inc.
> 630-753-5445
> [EMAIL PROTECTED]
>
> CONFIDENTIALITY NOTICE:  This e-mail, and any attachments
> and/or documents linked to this email, are intended for the
> addressee and may contain information that is privileged,
> confidential, proprietary, or otherwise protected by law.  Any
> dissemination, distribution, or copying is prohibited.  This
> notice serves as a confidentiality marking for the purpose of
> any confidentiality or nondisclosure agreement.  If you have
> received this communication in error, please contact the
> original sender.
>
> --
> 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

Re: vi alternative?

[RPN01]

When you get down to just 3270 access, the sed command is your friend. Do it
once to the terminal, if the file isn't too big, and check your results,
then use > to put the results into a new file, rename the old, rename the
new, and then start the cycle over again...

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 8/4/08 5:41 PM, "Ryan McCain" <[EMAIL PROTECTED]> wrote:

> I was just in text editor hell.  Network access was down to to our Linux guest
> so I loaded  up x3270 and was able to get to the host.  I needed to make a
> simple edit to a text file when I realized vi doesn't work. DOH!
>
> Is there an alternative to vi?  I was having to echo text into files, grep -v,
> etc. etc.
>
> Thanks..
>
> --
> 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

Re: VDISK-SWAP-SWAPGEN ???

[RPN01]

Make sure that, once you have manually gotten everything to work, you run
mkinird and zipl to create the new initrd image containing the parameters to
load the diag and fba drivers. This should make the next boot a bit...
Smoother.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."





On 7/31/08 4:44 PM, "Huegel, Thomas" <[EMAIL PROTECTED]> wrote:

> Thanks Adam.. That makes total sense.
> BTW as I was messing around I see I do have dasd_diag_mod, so I guess I could
> use the 'perfered' DIAG format in SWAPGEN and then swap to dasdb1 ..
>
> This LINUX stuff is going to make the rest of my hair turn grey..
>
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Adam Thornton
> Sent: Thursday, July 31, 2008 4:30 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: VDISK-SWAP-SWAPGEN ???
>
>
> On Jul 31, 2008, at 3:59 PM, Huegel, Thomas wrote:
>
>> Yes I have dasd_fba_mod loaded, I don't know about dasd_diag_mod..
>>
>> Here are some more messages...
>>
>> swapon -a
>> Unable to find swap-space signature
>> swapon: /dev/dasdb1: Invalid argument
>> linmstr:~ # Jul 31 15:54:23 linmstr kernel: Unable to find swap-
>> space signature
>> swapon /dev/dasdb
>> swapon /dev/dasdb
>> Adding 49992k swap on /dev/dasdb.  Priority:-1 extents:1
>> Jul 31 15:55:19 linmstr kernel: Adding 49992k swap on /dev/dasdb.
>> Priority:-1 extents:1
>
> Hmmm, OK.
>
> So the swapspace signature IS on /dev/dasdb, and it swapped on OK.
>
> So I think what's going on is that, for some reason, it's initially
> trying to swap on before dasd_fba_mod is loaded.
>
> So you probably need to build the ramdisk again with dasd_fba_mod in
> it, or you can just do a late-in-the-boot-process swapon -a once the
> device driver is loaded.
>
> Adam
>
> --
> 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

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

Re: VDISK-SWAP-SWAPGEN ???

[RPN01]

The copy I have was updated on 4/16/08. It doesn't appear to have been
drastic changes, though.


On 7/31/08 1:41 PM, "Huegel, Thomas" <[EMAIL PROTECTED]> wrote:

> I sort of understand what you are saying here, but I had to forward it to our
> LINUX guy and haven't heard back from him..
>
> Has SWAPGEN ben updated recently? .. the version I have was from about MARCH
> of this year.
>
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> RPN01
> Sent: Thursday, July 31, 2008 12:24 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: VDISK-SWAP-SWAPGEN ???
>
>
> From one of my systems, here's the contents of /proc/dasd/devices:
>
> iwydzl03:/home/rpn01 # cat /proc/dasd/devices
> 0.0.0391(ECKD) at ( 94: 0) is dasda   : active at blocksize: 4096,
> 22500 blocks, 87 MB
> 0.0.0392(ECKD) at ( 94: 4) is dasdb   : active at blocksize: 4096,
> 1802880 blocks, 7042 MB
> 0.0.0393(ECKD) at ( 94: 8) is dasdc   : active at blocksize: 4096,
> 1802880 blocks, 7042 MB
> 0.0.0394(ECKD) at ( 94:12) is dasdd   : active at blocksize: 4096,
> 1802880 blocks, 7042 MB
> 0.0.0395(ECKD) at ( 94:16) is dasde   : active at blocksize: 4096,
> 5896620 blocks, 23033 MB
> 0.0.0396(ECKD) at ( 94:20) is dasdf   : active at blocksize: 4096,
> 5896620 blocks, 23033 MB
> 0.0.0397(ECKD) at ( 94:24) is dasdg   : active at blocksize: 4096,
> 5896620 blocks, 23033 MB
> 0.0.0398(ECKD) at ( 94:28) is dasdh   : active at blocksize: 4096,
> 5896620 blocks, 23033 MB
> 0.0.0399(ECKD) at ( 94:32) is dasdi   : active at blocksize: 4096,
> 5896620 blocks, 23033 MB
> 0.0.039a(ECKD) at ( 94:36) is dasdj   : active at blocksize: 4096,
> 1440000 blocks, 5625 MB
> 0.0.07ff(FBA ) at ( 94:40) is dasdk   : active at blocksize: 512,
> 2097152 blocks, 1024 MB
> iwydzl03:/home/rpn01 #
>
> The last entry (0.0.7ff) ends up being /dev/dasdk. Using udev, entries for
> each disk are made in the path /dev/disk/by-path directory such as follows:
>
> iwydzl03:/dev/disk/by-path # ls
> .   ccw-0.0.0395ccw-0.0.0396ccw-0.0.0397ccw-0.0.0398
> ccw-0.0.0399ccw-0.0.039a   ccw-0.0.07ff
> ..  ccw-0.0.0395p1  ccw-0.0.0396p1  ccw-0.0.0397p1  ccw-0.0.0398p1
> ccw-0.0.0399p1  ccw-0.0.039a1  ccw-0.0.07ff1
> iwydzl03:/dev/disk/by-path #
>
> (Sorry for the formatting, or lack thereof) The entry I'm interested in for
> swap is ccw-0.0.07ff1 (the first partition of ccw device 07ff). This is used
> in fstab, as so:
>
> /dev/vg_system/lv_var /var reiserfs   acl,user_xattr
> 1 2
> /dev/disk/by-path/ccw-0.0.07ff1 swapswapdefaults,pri=100  0 0
> /dev/vg_system/lv_swap swap swap   defaults,pri=50
> 0 0
> devpts   /dev/pts devpts mode=0620,gid=5   0
> 0
>
> This allows me to access the swap without having to know what /dev/dasd?
> Device it is, or be worried about it changing positions in the list.
> Swapgen, used in a CMS profile which starts the boot process, makes sure
> that the swap space is formatted.
>
> --
> Robert P. Nix  Mayo Foundation.~.
> RO-OE-5-55 200 First Street SW/V\
> 507-284-0844   Rochester, MN 55905   /( )\
> -^^-^^
> "In theory, theory and practice are the same, but
>  in practice, theory and practice are different."
>
>
>
>
> On 7/31/08 11:51 AM, "Huegel, Thomas" <[EMAIL PROTECTED]> wrote:
>
>> Tried changing to /dev/dasdb1   ...
>> Still getting these messages..
>>
>> FBA SWAP DISK DEFINED AT VIRTUAL ADDRESS 151 (12498 4K PAGES OF SWAP SPACE)
>>
>>
>> ACTIVATING SWAP-DEVICES IN /ETC/FSTAB..."""
>>  [1A..FAILED
>>
>> ACTIVATING REMAINING SWAP-DEVICES IN /ETC/FSTAB..."""
>>  [1A..FAILED
>>
>> and no swap space gets defined.
>>
>>
>>
>> -Original Message-
>> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
>> Adam Thornton
>> Sent: Thursday, July 31, 2008 11:02 AM
>> To: LINUX-390@VM.MARIST.EDU
>> Subject: Re: VDISK-SWAP-SWAPGEN ???
>>
>>
>> On Jul 31, 2008, at 10:48 AM, Huegel, Thomas wrote:
>>
>>> /dev/dasdb  swapswapsw  0   0
>>> /dev/dasda1  /ext3
>>> acl,user_xattr1 1
>>> devpts   /dev/pts devpts
>>> mode=0620,gid=5   0 0
>>> proc /procproc
>>> defaults  0 0
>>> sysfs

Re: VDISK-SWAP-SWAPGEN ???

[RPN01]

>From one of my systems, here's the contents of /proc/dasd/devices:

iwydzl03:/home/rpn01 # cat /proc/dasd/devices
0.0.0391(ECKD) at ( 94: 0) is dasda   : active at blocksize: 4096,
22500 blocks, 87 MB
0.0.0392(ECKD) at ( 94: 4) is dasdb   : active at blocksize: 4096,
1802880 blocks, 7042 MB
0.0.0393(ECKD) at ( 94: 8) is dasdc   : active at blocksize: 4096,
1802880 blocks, 7042 MB
0.0.0394(ECKD) at ( 94:12) is dasdd   : active at blocksize: 4096,
1802880 blocks, 7042 MB
0.0.0395(ECKD) at ( 94:16) is dasde   : active at blocksize: 4096,
5896620 blocks, 23033 MB
0.0.0396(ECKD) at ( 94:20) is dasdf   : active at blocksize: 4096,
5896620 blocks, 23033 MB
0.0.0397(ECKD) at ( 94:24) is dasdg   : active at blocksize: 4096,
5896620 blocks, 23033 MB
0.0.0398(ECKD) at ( 94:28) is dasdh   : active at blocksize: 4096,
5896620 blocks, 23033 MB
0.0.0399(ECKD) at ( 94:32) is dasdi   : active at blocksize: 4096,
5896620 blocks, 23033 MB
0.0.039a(ECKD) at ( 94:36) is dasdj   : active at blocksize: 4096,
144 blocks, 5625 MB
0.0.07ff(FBA ) at ( 94:40) is dasdk   : active at blocksize: 512,
2097152 blocks, 1024 MB
iwydzl03:/home/rpn01 #

The last entry (0.0.7ff) ends up being /dev/dasdk. Using udev, entries for
each disk are made in the path /dev/disk/by-path directory such as follows:

iwydzl03:/dev/disk/by-path # ls
.   ccw-0.0.0395ccw-0.0.0396ccw-0.0.0397ccw-0.0.0398
ccw-0.0.0399ccw-0.0.039a   ccw-0.0.07ff
..  ccw-0.0.0395p1  ccw-0.0.0396p1  ccw-0.0.0397p1  ccw-0.0.0398p1
ccw-0.0.0399p1  ccw-0.0.039a1  ccw-0.0.07ff1
iwydzl03:/dev/disk/by-path #

(Sorry for the formatting, or lack thereof) The entry I'm interested in for
swap is ccw-0.0.07ff1 (the first partition of ccw device 07ff). This is used
in fstab, as so:

/dev/vg_system/lv_var /var reiserfs   acl,user_xattr
1 2
/dev/disk/by-path/ccw-0.0.07ff1 swapswapdefaults,pri=100  0 0
/dev/vg_system/lv_swap swap swap   defaults,pri=50
0 0
devpts   /dev/pts devpts mode=0620,gid=5   0
0

This allows me to access the swap without having to know what /dev/dasd?
Device it is, or be worried about it changing positions in the list.
Swapgen, used in a CMS profile which starts the boot process, makes sure
that the swap space is formatted.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 7/31/08 11:51 AM, "Huegel, Thomas" <[EMAIL PROTECTED]> wrote:

> Tried changing to /dev/dasdb1   ...
> Still getting these messages..
>
> FBA SWAP DISK DEFINED AT VIRTUAL ADDRESS 151 (12498 4K PAGES OF SWAP SPACE)
>
>
> ACTIVATING SWAP-DEVICES IN /ETC/FSTAB..."""
>  [1A..FAILED
>
> ACTIVATING REMAINING SWAP-DEVICES IN /ETC/FSTAB..."""
>  [1A..FAILED
>
> and no swap space gets defined.
>
>
>
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Adam Thornton
> Sent: Thursday, July 31, 2008 11:02 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: VDISK-SWAP-SWAPGEN ???
>
>
> On Jul 31, 2008, at 10:48 AM, Huegel, Thomas wrote:
>
>> /dev/dasdb  swapswapsw  0   0
>> /dev/dasda1  /ext3
>> acl,user_xattr1 1
>> devpts   /dev/pts devpts
>> mode=0620,gid=5   0 0
>> proc /procproc
>> defaults  0 0
>> sysfs/sys sysfs
>> noauto0 0
>
> If you didn't run SWAPGEN in FBA mode, you want to swap to /dev/dasdb1.
>
> Adam
>
> --
> 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

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

Re: VDISK-SWAP-SWAPGEN ???

[RPN01]

Does the swap disk appear as /dev/dasdb? (cat /proc/dasd/devices)



On 7/31/08 10:48 AM, "Huegel, Thomas" <[EMAIL PROTECTED]> wrote:

> /dev/dasdb  swapswapsw  0   0
> /dev/dasda1  /ext3   acl,user_xattr1 1
> devpts   /dev/pts devpts mode=0620,gid=5   0 0
> proc /procproc   defaults  0 0
> sysfs/sys sysfs  noauto0 0
>
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> RPN01
> Sent: Thursday, July 31, 2008 10:30 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: VDISK-SWAP-SWAPGEN ???
>
>
> What does fstab look like?
>
> --
> Robert P. Nix  Mayo Foundation.~.
> RO-OE-5-55 200 First Street SW/V\
> 507-284-0844   Rochester, MN 55905   /( )\
> -^^-^^
> "In theory, theory and practice are the same, but
>  in practice, theory and practice are different."
>
>
>
>
> On 7/31/08 10:23 AM, "Huegel, Thomas" <[EMAIL PROTECTED]> wrote:
>
>> I'm the VM guy not the LINUX guy, so be gentle.
>>
>> I am trying to use VDISK for swap space for the first time and it doesn't
>> seem
>> to work.
>> These are the messages I get.
>>
>>
>> From SWAPGEN
>>  FBA SWAP DISK DEFINED AT VIRTUAL ADDRESS 151 (12498 4K PAGES OF SWAP SPACE)
>>
>> During the LINUX boot:
>>
>>  ACTIVATING SWAP-DEVICES IN /ETC/FSTAB..."""
>>  [1A..FAILED
>>  CHECKING ROOT FILE SYSTEM..."""FSCK 1.38 (30-JUN-2005)"""[/SBIN/FSCK.EXT3
>> (1)
>> --
>>
>> When LINUX finishes there is no active swap disk.
>>
>> Once LINUX is booted I can do swapon -a and it starts up.
>>
>>
>> Any ideas?
>>
>> Thanks
>> Tom
>>
>> --
>> 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
>
> --
> 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

Re: VDISK-SWAP-SWAPGEN ???

[RPN01]

What does fstab look like?

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 7/31/08 10:23 AM, "Huegel, Thomas" <[EMAIL PROTECTED]> wrote:

> I'm the VM guy not the LINUX guy, so be gentle.
>
> I am trying to use VDISK for swap space for the first time and it doesn't seem
> to work.
> These are the messages I get.
>
>
> From SWAPGEN
>  FBA SWAP DISK DEFINED AT VIRTUAL ADDRESS 151 (12498 4K PAGES OF SWAP SPACE)
>
> During the LINUX boot:
>
>  ACTIVATING SWAP-DEVICES IN /ETC/FSTAB..."""
>  [1A..FAILED
>  CHECKING ROOT FILE SYSTEM..."""FSCK 1.38 (30-JUN-2005)"""[/SBIN/FSCK.EXT3 (1)
> --
>
> When LINUX finishes there is no active swap disk.
>
> Once LINUX is booted I can do swapon -a and it starts up.
>
>
> Any ideas?
>
> Thanks
> Tom
>
> --
> 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

Re: Cloning of SLES10 image and logon IDs

[RPN01]

I would guess that, for a system to be useful, /etc/passwd and shadow would
change over time to include other userids for whatever task or application
is taking place there. That would preclude copying and old copy over the
current one producing any useful results.

The approach we've used is to connect pam on each image to an LDAP server
which maintains the accounts. Each server has an associated netgroup, and
users of that server have that netgroup included in their LDAP profiles,
allowing them to log into the server.

Doing maintenance by writing over the /, /usr, or /boot directories is a
"Very Bad Idea" . Even if you only do /boot, there are kernel changes which
necessitate changes to the programs that interface to the kernel function.
Maintenance is an all-inclusive thing, where changes are made in /etc,
/boot, /usr/bin, /usr/share and many other locations, all at once. These
things, most times, need to be in sync in order for the system to run
correctly. 

I've not seen a way to correctly propagate all the necessary pieces of a
maintenance run, other than using YaST itself. Down other paths lie
insanity. There are system management and provisioning products that claim
to be able to do it... Look at them closely and make them prove that they
work before you commit your systems to them.

-- 
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 7/22/08 10:35 AM, "Whiteman, Mark" <[EMAIL PROTECTED]> wrote:

> I guess my point is, if I deploy from a "gold"  image, I'll probably
> want to change passwords on the various clones.  If I put patches/fixes
> onto my "gold" image and want to redeploy it, I'll go back to the
> original passwords.  So, when I redploy, could I simply take a backup of
> the /etc/passwd, group, shadow and copy them back over the original
> members that existed on the "gold" image ?
> 
> 
> 
> Mark W.
> 
> . 
> 
> The only place Linux stores "local" user information is in /etc/passwd,
> /etc/shadow, and /etc/group.  Without special schemes to get around it,
> /etc lives in your root file system.  So, any method you come up with to
> copy one system to another will automatically bring with it the same
> userids and passwords.
> 
> 
> 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

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

Re: z/Linux cloning

[RPN01]

We have a cloning process that is down to a single zVM command to create a
new image, and we can create new images in about 8 minutes time from zVM
command to being able to log into the new image. The master images occupy
disk space, but are not running at any time. Since the disk copies are done
from zVM via Flashcopy, the cloning process is independent of filesystem
choice and works with LVM managed disks. As far as I know, we're the only
ones using the process at the moment. If there's an interest, I can share it
with you.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 7/18/08 10:36 AM, "Quay, Jonathan (IHG)" <[EMAIL PROTECTED]> wrote:

> What's the current "best practices" cloning solution for z/Linux under
> z/VM?  We've used the one found in "Running z/VM to Host Linux -
> Installation and Customization" class documentation (the CLONER and
> CLONEDDR virtual machines).  Is there one that's newer, better or better
> supported?  We have multiple CECs, z/Linux lpars, and both Suse and
> Redhat, if that makes a difference.  We don't anticipate creating
> hundreds of clones, maybe 20 or so in the first wave.
>
>
>
>
> --
> 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

Re: LVM problem. Lost VG info

[RPN01]

Also note that the information necessary to recreate the LVM environment
should be stored in the first few blocks of any of the PV devices (I think
there's actually about five copies there.) Use your favorite tool to read
the physical device, and you should be able to extract the information you
need to re-build the environment.

Sorry if the other message was a false start, but you didn't say if you
could actually see the physical devices, and it was the first thought that
came to me

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 6/17/08 8:03 AM, "CHAPLIN, JAMES (CTR)"
<[EMAIL PROTECTED]> wrote:

> Did you try a vgscan?
>
> James Chaplin
> Systems Programmer, MVS, zVM & zLinux
> Base Technologies, Inc
> (703) 921-6220
>
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> Walters, Gene P
> Sent: Tuesday, June 17, 2008 8:58 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: LVM problem. Lost VG info
>
> I'm already having a bad day.  I took one of our Linux Instances down to
> add more disk space to it.  Everything went fine.  I used Yast2 to add
> the new volumes to the VG.  Now when I IPL, it cant find the volume
> group.
>
> I ran a PVSCAN, and it shows all my physical volumes are associated to
> an unknown VG.  I've looked at several commands, but I guess I just
> don't understand.  Hopefully my data is not lost.  Is there a way to
> rebuild the VG?
>
> --
> 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

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

Re: LVM problem. Lost VG info

[RPN01]

After adding the new DASD, did you run mkinitrd and zipl, to fold them into
the boot configuration? I think that on RedHat, you also have to add them to
the parm line in the zipl.conf file

This is the last step in adding DASD, and the one that I've forgotten way
too many times. Given that it has to happen, my question is why YaST doesn't
perform the mkinitrd and zipl commands itself as part of the process. I know
that you can attach DASD temporarily, but it would seem simple enough to do
the commands again when you take DASD out of the configuration as well
It's just way too easy to forget to do.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 6/17/08 7:58 AM, "Walters, Gene P" <[EMAIL PROTECTED]> wrote:

> I'm already having a bad day.  I took one of our Linux Instances down to
> add more disk space to it.  Everything went fine.  I used Yast2 to add
> the new volumes to the VG.  Now when I IPL, it cant find the volume
> group.
>
> I ran a PVSCAN, and it shows all my physical volumes are associated to
> an unknown VG.  I've looked at several commands, but I guess I just
> don't understand.  Hopefully my data is not lost.  Is there a way to
> rebuild the VG?
>
> --
> 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

Re: SLES 10 SP1 and SP2 install defaults of disk by device-ID

[RPN01]

The problem with this in a z/VM world is that many disks are not complete
DASD's, so this value is not unique; possibly not even unique within a
single Linux image. This scheme trips us up in two ways:

The first is that, while all our DASD are 3390 mod 27 devices, we tend to
build out Linux images using two mod 9 virtual devices. In roughly half the
builds, these two minidisks are on the same physical device, and can cause a
conflict because the UID is not unique.

The second is that we clone Linux images by copying the minidisks to new
extents, which are likely not on the same physical device as the original.
At that point, the mounts fail because the UID cannot be located.

At least for the z/VM environment, the /dev/disk/by-path is a better choice
for building mounts in fstab. The virtual CUU of the minidisk will
definitely be unique within a single virtual machine, and, unless you savor
insanity, cloning images will keep the minidisks at the same virtual CUU as
the master image used.

The choice to use UID in the physical Intel world may be good... But for a
virtual world, zSeries or Intel, it would seem, to me, to be a very poor
choice as a default.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 6/10/08 4:37 PM, "Alan Altmark" <[EMAIL PROTECTED]> wrote:
>
> The UID is indeed unique to the device.  It consists of manufacturer's
> name, plant of manufacture, and a serial number.  That allows you to
> identify a volume, independent of how you access it (UAs, device numbers,
> chpids, etc.).

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

Re: Sles9 to 10 upgrades and disk naming

[RPN01]

I've noticed that the naming of the devices is very inconsistent. Just
within SuSE SLES 9, I see /dev/disk/by-path/ccw-0.0.07ffp1 and
/dev/disk/by-path/ccw-0.0.07ff1. And as noted, this is different from SLES
10 which had /dev/disk/by-path/ccw-0.0.07ff-part1.

Isn't the point of this to have predictable names for the devices? But if
you can't predict what the predictable name will be, how is it any better
than /dev/dasda and /dev/dasdb?


On 5/27/08 2:13 PM, "Mark Post" <[EMAIL PROTECTED]> wrote:

 On Thu, May 22, 2008 at 10:14 PM, in message
> <[EMAIL PROTECTED]>, Marcy
> Cortes <[EMAIL PROTECTED]> wrote:
>> We use /dev/disk/by-path
>>
>> names to label all of our disks on sles9 rather than the /dev/dasda.. In
>> zipl.conf for the root= as well as in /etc/fstab.
>>
>> Now.. Sles10 has decided that instead of
>> /dev/disk/by-path/ccw-0.0.0100p1
>> It will call the disk
>> /dev/disk/by-path/ccw-0.0.0100-part1
>>
>> So the upgrade process doesn't work.
>> Is there a better way other than reverting back to /dev/dasda.. And then
>> changing it backup again when we're doing upgrading?
>
> What exactly happens during the upgrade?  I haven't tried this myself, so I
> don't know.
>
>
> 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

Re: Query CPU usage.

[RPN01]

Tivoli will also report that the LPAR is running at 100% for z/VM and for CF
LPARs. Obviously, there's something that is "misinformed". Ignore these
numbers for everything that is not a z/OS LPAR, and they are quite useless.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 5/12/08 3:07 PM, "Fargusson.Alan" <[EMAIL PROTECTED]> wrote:

> I don't know how they determine that the LPAR is running at 100% CPU.  It may
> be completely inaccurate, so I want to check from VM.
>
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Barton Robinson
> Sent: Monday, May 12, 2008 2:00 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Query CPU usage.
>
>
> So you use the z/OS performance monitor for monitoring the LPAR, it will say
> your IFL is
> running at 100%.  This would be useless information, and less than accurate.

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

Re: Cloned system mounts file systems read-only

[RPN01]

I don't think he was running in z/VM though...

The two things I see as possible problems are that you didn't run mkinitrd
before running zipl. The mkinitrd needs to know about the disks as well,
based on your current chroot'ed paths. This is my absolute favorite mistake,
and I've recovered from it dozens (and dozens) of times I do not learn
quickly.

The second, and it may have just been missed, would be that, once you've
mkinitrd && zipl'ed, you didn't mention getting out of the chroot
environment, unmounting the paths and taking the devices offline again to
Linux. Just jerking them out from beneath the system may have left them in
an undesired state.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 4/18/08 8:47 AM, "Scott Rohling" <[EMAIL PROTECTED]> wrote:

> You're not showing how you either ATTACHed or LINKed to the 186/187 --   you
> need to DETACH them.  (vmcp det 186-187).   Just putting them offline with
> chccwdev doesn't do it..  (unless your 'logout' is a LOGOFF -- if so, then
> I'm stumped)
>
> Hope that helps - Scott
>
> On Fri, Apr 18, 2008 at 7:15 AM, Herczeg, Zoltan <[EMAIL PROTECTED]>
> wrote:
>
>> Hi. From information I have gathered from this list I tried to clone a
>> sles 9 system (lpar no VM). When I log in to the system and try to
>> update a file I get a message that it is read-only. When I booted this
>> system I see messages
>>
>> VFS: Mounted root (reiserfs filesystem) readonly
>> Trying to move old root to /initrd . . . failed
>> Unmounting old root
>>
>> Here are the steps I followed
>>
>> Shut down source linux system which uses dasd 43e and 43f
>> Use VSE to fastcopy full volumes to another two dasd addresses 186 and
>> 187 (3390-3)
>> IPL source linux system
>> chccwdev -e 0.0.0186and chccwdev -e 0.0.0187
>> lsdasd command to see that 186 is dasdc and 187 is dasdd
>> mount /dev/dasdc1 /mnt
>> chroot /mnt
>> edit /etc/zipl.conf   changing the parmfile dasd addresses from 43e and
>> 43f to 186 and 187
>> ed /etc/hosts
>> rename /etc/sysconfig/hardware hwcfg-dasd-bus-ccw-0.0.043e  to .0186
>> and .043f to .0187
>> zipl
>> exit out of chroot
>> unmount /mnt
>> chccwdev -d 0.0.0186  and 0187
>> logout
>>
>> If anyone can point out my fatal readonly flaw I would appreciate it.
>> Thanks in advance from a very green newbie!
>>
>> Zoltan
>>
>> --
>> 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

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

Re: recover root password

[RPN01]

This is one of the problems I've had learning Linux: There are Linux
defaults, and then there are different defaults created by the various
distributions, and it's hard to tell which are which. Linux is a single
operating system that never acts the same from machine to machine (much like
Windows, but for different reasons).

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 4/15/08 4:20 PM, "John Summerfield" <[EMAIL PROTECTED]>
wrote:

> RPN01 wrote:
>> By default, sudo expects root's password.
>
> That is not what the man page says, It _is_ the way SUSE configures it.
> --
>
> Cheers
> John
>

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

Re: recover root password

[RPN01]

By default, sudo expects root's password. But, it can be easily configured
to expect the user to enter his own password instead. It's a one line
change.

RedHat and SuSE expect administrators to use the root account because "It's
always been done that way." But, when you have more than one administrator,
and especially if you have more than a hand-full, like six to fifteen, then
doing so gives you no accountability for what has been done to your systems.

Anyone sticking to the "I have to have root!" model of system administration
is leaving themselves open to a huge awakening as Sarbanes-Oxley and other
regulations overtake us. While we aren't required by law to conform to
Sarbanes-Oxley, we've chosen to bring ourselves as close as we possibly can.
One of the requirements is that what is done to your systems is done with
accountability. To be completely compliant, everything done by / with root
will need to be logged, showing what was done, and by whom. Can you do that
now, with two or more people logging into root? Can you do it with even one
person logging into root? Not on any distribution I know today. So you
aren't compliant, and will be pinged on your audit, and if you're required
to be S-O compliant, you're leaving your company open to legal action.

Just because it's the way RedHat or SuSE does it doesn't make it the
standard. You need it for the installation, which may be why both RedHat and
SuSE are set up that way. It doesn't mean you have to stay that way once the
system is up and running. You change other things on the system after the
install, so I don't see the reasoning of holding up the standard that "It
comes that way, so it should stay that way." That doesn't make any sense.

I stand by my statement: Get out of root as soon as you possibly can after
the install, and stay out of root as much as you possibly can. Complain to
vendors when they force you to use root to install their products. Complain
to vendors that force you to run their product as root. These are practices
that shortly will not be acceptable. And the time shortens every time some
retailer loses thousands of credit card records. We didn't lose that
information, but we're the ones that it is easiest to go to and say "You've
got to improve security! You have to have accountability!" So we're the ones
that will ultimately pay the price. I predict that this will be one of the
costs in the short term.

Anyone willing to bet a coke on it?

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



On 4/14/08 5:34 PM, "John Summerfield" <[EMAIL PROTECTED]>
wrote:

> RPN01 wrote:
>> Would it be the wrong time to suggest that, once you have the system
>> installed, up and running, nobody should ever log in as root, except in dire
>> or unavoidable circumstances.
>>
>> Once you have the system, give your system administration group sudo all
>> privs. Then just don't log into root at all. This gives you accountability
>
> Red Hat expects administrators to know and use root's password. That's
> what su does.
>
> SUSE expects administrators to know and use root's password. It
> configures sudo to work that way.
>
> Until the vendors change their approach, administrators are going to be
> working that way.
>
> The only Linux distribution that expects administrators to use their own
> password is Ubuntu, and while it's based off Debian that is available
> for IBM mainframes, Ubuntu isn't yet.
>
>
>
> One can also login as root without password if ssh is so configured.
>
>
>
> --
>
> Cheers
> John
>
> -- spambait
> [EMAIL PROTECTED]  [EMAIL PROTECTED]
> -- Advice
> http://webfoot.com/advice/email.top.php
> http://www.catb.org/~esr/faqs/smart-questions.html
> http://support.microsoft.com/kb/555375
>
> You cannot reply off-list:-)
>
> --
> 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

Re: recover root password

[RPN01]

Would it be the wrong time to suggest that, once you have the system
installed, up and running, nobody should ever log in as root, except in dire
or unavoidable circumstances.

Once you have the system, give your system administration group sudo all
privs. Then just don't log into root at all. This gives you accountability
for what is being done to your system; You can't tell who logged in as root
(ok, you can tell what IP address they were from, but that person can say
"Hey! Somebody else used my jack..."), but you can tell who is using sudo.

Dire circumstances? Like when you need to log into a semi-brain dead system
from the console. Or your normal authorization system (like LDAP) has given
up the ghost. Unavoidable circumstances? Like when you need to install a
product and it checks that you logged in as root; not that you are root now,
but that you actually logged in to the root account. If you're the vendor,
then shame on you! It shouldn't matter how I got to be root, and you
shouldn't care either, just to install your program.

In any case, don't log into root, and you avoid this type of problem. At
best, someone will lock themselves out, which might actually be a good
thing, given some people. And if you change root's password and forget, you
have several semi-root people to call upon to easily fix your mistake.

Of course, that doesn't mean that you don't need to change root's password
from time to time; you still need to maintain the security and integrity of
your system

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 4/14/08 10:42 AM, "David K. Kelly" <[EMAIL PROTECTED]> wrote:

> Miguel,
>
> For things like this VM is the Bomb!  Just make the root drive from the
> locked server
> available for a different  Lunix guest, (making sure the one with the
> locked out root
> account is down) and boot the 2nd guest. Then mount the new disk as /mnt
> and cd /mnt/etc
> Then edit the /mnt/etc/shadow file and remove the password from the root
> account.
> Then undo all the previous steps and boot.  Fixed.   (this is kind of a
> quick and
> dirty explanation, I can do better if you'd like)
>
> David K.
>
>
>
>
>
>  Marcy Cortes
>  <[EMAIL PROTECTED]
>  ellsfargo.com> To
>  Sent by: Linux on LINUX-390@VM.MARIST.EDU
>  390 Port   cc
>  <[EMAIL PROTECTED]
>  IST.EDU>  Subject
>Re: recover root password
>
>  04/14/2008 11:30
>  AM
>
>
>  Please respond to
>  Linux on 390 Port
>  <[EMAIL PROTECTED]
>  IST.EDU>
>
>
>
>
>
>
>
> Does anyone have full sudo?
> Then you could just
>   sudo su -
>   passwd
>
> And change it.
>
> Marcy Cortes
>
> "This message may contain confidential and/or privileged information. If
> you are not the addressee or authorized to receive this for the
> addressee, you must not use, copy, disclose, or take any action based on
> this message or any information herein. If you have received this
> message in error, please advise the sender immediately by reply e-mail
> and delete this message. Thank you for your cooperation."
>
>
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> Miguel Roman
> Sent: Monday, April 14, 2008 8:03 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: [LINUX-390] recover root password
>
> Hello,
>
> We are running Suse Linux 9.3 (64 bit) under z/VM 5.1. One of the
> administrators changed the root password and forgot the password. Does
> anyone know how to recover the root password? Thanks.
>
> Miguel A Roman.
>
>
>
>
> --
> 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
>
> --
> 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 ins

What distribution and why?

[RPN01]

We¹re looking at the costs and effort of converting our installation from
SuSE SLES to RedHat RHEL on the zSeries, and I¹m wondering what others are
running, and why they chose the particular distribution. All comments are
welcome, on or off list; I just want to be sure we¹re not backing ourselves
into the room¹s other corner

I know this has been discussed before, but times change, and maybe a
headcount is in order again.

-- 
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."



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

Re: What is a good generic disk layout?

[RPN01]

We're using the following layout:

Allocate the following disks to the Linux guest:

* 124 cylinders minimum as device num 391, used as /boot
* 10016 cylinders minimum as device num 392, used as vg_system.
* 10016 cylinders minimum as device num 393, used as vg_local
* ?? cylinders as device numbers 394+, used as vg_app, vg_db, etc.
as required by app

During the Linux install, allocate the disk as follows:

* /dev/dasda1 (391) as /boot
* /dev/dasdb1 (392) as LVM vg_system
  o / - 2.0 gb
  o /var - 2.5 gb
  o /tmp - 500 mb
  o swap - 1 gb
* /dev/dasdc1 (393) as LVM vg_local
  o /home - 2 gb
  o /opt - 5.4 gb

This provides us with a minimal /boot outside of LVM, isolates /var and /tmp
from the root file system, and places /home and /opt on its own disk.

This leaves us with a disk usage after install somewhat like the following:

[EMAIL PROTECTED]:~> df
Filesystem   1K-blocks  Used Available Use% Mounted on
/dev/mapper/vg_system-lv_root
   2890692   2074908668944  76% /
udev509860   104509756   1% /dev
/dev/dasda1  87076 16544 66040  21% /boot
/dev/mapper/vg_local-lv_home
   2064208 95864   1863488   5% /home
/dev/mapper/vg_local-lv_opt
   4954828595096   4108036  13% /opt
/dev/mapper/vg_system-lv_tmp
495944110616359728  24% /tmp
/dev/mapper/vg_system-lv_var
   2580272216860   2232340   9% /var
[EMAIL PROTECTED]:~>

Hope this helps...

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 4/8/08 10:31 AM, "Adam Thornton" <[EMAIL PROTECTED]> wrote:

> On Apr 8, 2008, at 9:45 AM, Romanowski, John (OFT) wrote:
>
>> can't you make partition1 dasda1 /boot and partition2 dasda2 the PV
>> for
>> LVM?
>
> Sub-partitioning DASD on zSeries is really not a very good idea.
>
> If you're running under VM, you've already GOT virtualized disk.
>
> Make /dev/dasda a small /boot parition (so, only give it 80 cylinders
> or something) and make /dev/dasdb a bigger volume which you can make
> into an LVM PV if you want to.
>
> Adam

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

Re: DASD error on zlinux ipl

[RPN01]

At first blush, it appears that you added volumes to VolGroup00, but failed
to run mkinitrd and zipl afterward. This is my favorite (or at least most
common) error.

If it comes up far enough, log into root and check /proc/dasd/devices to see
if you have what you expected to have. You may need to re-activate them and
run mkinitrd and zipl to get them permanently into the fold, then boot once
more.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 3/30/08 7:08 PM, "Ian S. Worthington" <[EMAIL PROTECTED]> wrote:

> Restarting my zlinux system today I got the following which seems to
> suggest some problem on 120.  I'm assuming this is a red herring as it
> also appears in my last good console (underneath)?
>
> VolGroup00 should contain 122 as well I suspect, as it was extended to use
> this volume, though there's nothing on it as the fs is ext2 and couldn't be
> extended
> online and I have no other way of booting.  Could it be this its not
> finding, or has got corrupted?
>
> Any help/advice on how to disentangle this most welcome.
>
> Ian
> ..
>
> 18:39:00 Loading dasd_mod.ko module
> 18:39:01 Loading dasd_eckd_mod.ko module
> 18:39:01 HHCCP048I 0120:CCW=2742 0FBDFFB8=>1D00 0800
>   
> 18:39:01 HHCCP075I 0120:Stat=0E40 Count=0040
> 18:39:01 HHCCP076I 0120:Sense=8000 000B0804  
>  
> 18:39:01 HHCCP077I 0120:Sense=CMDREJ
> 18:39:01 dasd_erp(3990):  0.0.0120: EXAMINE 24: Command Reject detected
> - fatal error
> 18:39:01 dasd(eckd): I/O status report for device 0.0.0120:
> 18:39:01 dasd(eckd): in req: 0fbdfee0 CS: 0x40 DS: 0x0E
> 18:39:01 dasd(eckd): device 0.0.0120: Failing CCW: 0fbdffb8
> 18:39:01 dasd(eckd): Sense(hex)  0- 7: 80 00 00 00 00 0b 08 04
> 18:39:01 dasd(eckd): Sense(hex)  8-15: 00 00 00 00 00 00 00 00
> 18:39:01 dasd(eckd): Sense(hex) 16-23: 00 00 00 00 00 00 00 00
> 18:39:01 dasd(eckd): Sense(hex) 24-31: 00 00 00 80 00 00 0b 08
> 18:39:01 dasd(eckd): 24 Byte: 0 MSG 4, no MSGb to SYSOP
> 18:39:01 dasd(eckd): Related CP in req: 0fbdfee0
> 18:39:01 dasd(eckd): CCW 0fbdffb0: 2742 0FBDFFB8 DAT:
> 1d00 0800  000
> 18:39:01 0       
> 18:39:01 dasd(eckd): 0.0.0120: PSF-SSC on storage subsystem
> HRC.ZZ0001.0120 retur
> 18:39:01 ned rc=-5
> 18:39:01 dasd(eckd): 0.0.0120: 3390/0A(CU:3990/01) Cyl:3339 Head:15
> Sec:224
> 18:39:01 Using cfq io scheduler
> 18:39:01 dasd(eckd): 0.0.0120: (4kB blks): 2404080kB at 48kB/trk
> compatible disk layout
> 18:39:01  dasda:VOL1/  0X0120: dasda1 dasda2
> 18:39:01 dasd(eckd): 0.0.0121: 3390/0A(CU:3990/01) Cyl:3339 Head:15
> Sec:224
> 18:39:01 dasd(eckd): 0.0.0121: (4kB blks): 2404080kB at 48kB/trk
> compatible disk layout
> 18:39:01  dasdb:VOL1/  0X0121: dasdb1
> 18:39:02 Loading dasd_fba_mod.ko module
> 18:39:02 Loading dm-mirror.ko module
> 18:39:02 Loading dm-zero.ko module
> 18:39:02 Loading dm-snapshot.ko module
> 18:39:04 Making device-mapper control node
> 18:39:04 Scanning logical volumes
> 18:39:04   Reading all physical volumes.  This may take a while...
> 18:39:05   Couldn't find device with uuid
> 'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'.
> 18:39:05   Couldn't find all physical volumes for volume group
> VolGroup00.
> 18:39:05   Couldn't find device with uuid
> 'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'.
> 18:39:05   Couldn't find all physical volumes for volume group
> VolGroup00.
> 18:39:05   Couldn't find device with uuid
> 'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'.
> 18:39:05   Couldn't find all physical volumes for volume group
> VolGroup00.
> 18:39:05   Couldn't find device with uuid
> 'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'.
> 18:39:05   Couldn't find all physical volumes for volume group
> VolGroup00.
> 18:39:05   Volume group "VolGroup00" not found
> 18:39:05 ERROR: /bin/lvm exited abnormally  (pid 188)
> 18:39:05 Activating logical volumes
> 18:39:07   Couldn't find device with uuid
> 'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'.
> 18:39:07   Couldn't find all physical volumes for volume group
> VolGroup00.
> 18:39:07   Couldn't find device with uuid
> 'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'.
> 18:39:07   Couldn't find all physical volumes for volume group
> VolGroup00.
> 18:39:07   Couldn't find device with uuid
> 'Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd'.
> 18:39:07   Couldn't find all physical volumes for volume group
> VolGroup00.
> 18:39:08 Kernel panic - not syncing: Attempted to kill init
> 18:39:08 CPU: SIGP Stop (05) CPU0001, PARM : CC 0
> 18:39:08 CPU: SIGP Store status (0E) CPU0001, PARM 00D0C000:
> CC 2
> 18:39:08 CPU: SIGP Store status (0E) CPU0001, PARM 00D0C000:
>

Re: curiousity question: Linux usage: many or few

[RPN01]

I'll start with the second part first, and even with a rant, at that: VMWare
doesn't work for Linux. If you put a Linux system on a heavily used VMWare
box, VMWare can't complete the Linux I/O quickly enough, Linux detects the
timeout, and places the filesystem in a read-only state. There is no
solution if you want to stay within your standard Linux distribution. VMWare
does have a disk driver that is supposed to work, but the only change is
that they greatly increased the disk I/O timeout, and installing it means
headaches when you later want to apply maintenance to your Linux system.

Then to the actual question: The appliance mode works well, if you never
plan to upgrade it, or it is a stand-alone application unto itself, with
little outside information applied or kept. When the time comes to upgrade,
you have to figure out what to take from the old system, and what you don't
want to take for fear of overwriting something new and important in the new
system.

And now, the "it depends" part: One server, one function is much more a
political battle than a technical one. On Windows, where there is no concept
of a "User", and therefore no concept of security, you're forced into the
one server, one function mode of implementation, in order to keep prying
eyes out of each other's applications and data. But on Linux, whatever
platform you're on, this isn't the case.

You can easily implement multiple user groups and applications on a single
Linux image and still isolate one from another. The problem comes when those
groups find out that they're sharing the system, and don't feel that you've
applied the correct priority, and security to their project. Most things are
implemented in separate Linux systems because it is politically easier to
explain the application's level of isolation if you can draw a line around
the application and say "This is your box". When there are other things
within the line, people get nervous, especially the ones used to Windows.

The downside of this in a virtual environment is that you are repeatedly
implementing the same operating system code in memory for each unique image,
when in fact, this code could have been shared by several individual
applications, were they to share a single Linux image. It would be more
efficient to place several applications within a single Linux image, within
reason, to exploit the shared copy of the operating system.

The downside of this in a physical hardware environment is that you
proliferate systems in your racks to the point of environmental collapse.
This is where we are at this point; There is no space to install a new
server in the computer room. If there were space, there isn't enough
electric capacity entering the room to support the new hardware. Were there
power, there isn't enough cooling in order to keep everything chilled given
the additional heat load of the new system. Yes, you can exceed the capacity
of the electric company to bring power into your computer room; come have a
peek, and welcome to my world...

Having said that, all our Linux images, virtual and hardware-based, are
single tasked. It is a Windows world, after all, and how do you fight the
logic of the largest operating system company in the world

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 3/26/08 11:42 AM, "McKown, John" <[EMAIL PROTECTED]> wrote:

> I'm wondering about this. I'm a z/OS person with some Linux knowledge.
> But we don't run Linux on z around here. In the Windows world, the
> mantra is generally "One server, one function". On z/OS it is the
> opposite of "one server, lots of functions". How does Linux, in general,
> stack up on this scale? It is better to have multiple guests, each doing
> a specific job. Or is it better to have multiple functions in a single
> guest? Yeah, I know, "it depends!". I am fairly sure that if a Linux
> system is very busy, that it would be better for it to be "stand alone".
> But is the same true of low activity functions? No, I don't have any
> examples of a "low activity function", maybe simple email.
>
> Just curious.
>
> Also, what do ya'll think of VMWare's "appliance" philosophy? I.e.
> instead of having a generalized Linux (or other) system which can do
> many things, each "appliance" does one thing and is specialized to do
> that only. When you want to upgrade, you replace the entire appliance,
> OS and application, as a single "black box".

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

Re: Betr.: how can I mount /tmp as a tmpfs in SLES9?

[RPN01]

Not a performance issue, but several products place files in /tmp that they
expect to live across boots. In one case, I know of one that stores all its
configuration data there. This is in spite of the fact that everything
documents /tmp as being volatile. So, depending on your application mix, a
truly temporary /tmp could get you (or at least someone you know) in
trouble.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 3/17/08 4:16 PM, "Pieter Harder" <[EMAIL PROTECTED]> wrote:

> My first thought would be that it isn't a great idea to mount /tmp in Linux
> memory as that adds to the working set of the machine. If you want memory I
> would make it a z/VM Vdisk and put /tmp there and let CP handle the memory
> requirement. But I may be totally off base here. Anybody have numbers about
> this? Velocity guys?
>
>
> Best regards,
> Pieter Harder

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

Re: Cloning SLES10 & udev

[RPN01]

The problem lies in SLES 10 SP 1, which introduced the fstab mount by
obscure id "feature". While noble and in the right direction, much like my
arrows at the archery range, they missed the mark.

The change was made so that when new devices are added, fstab can find the
correct devices even if their order has changed and there's a new /dev/dasda
that wasn't what it was before. In order to keep the spirit of the change,
but avoid the cloning error, what you need to do is change the fstab entry
from using /dev/disk/by-id to using /dev/disk/by-path. Within the by-path
directory, all your minidisks (the actual thing indicative of what you're
really trying to mount. Assuming partition one on the minidisk at address
391, the entry you want to use would be:

/dev/disk/by-path/ccw-0.0.0391-part1

This doesn't have the downside of the magic number based on the physical
device the minidisk resides on, while still not depending on the order in
which the disks are presented to the Linux system.

If you make this change to fstab in your clone master, it should clone
correctly. When you create new masters, I think you can make this change as
you define the disks, via the fstab options button.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."





On 3/14/08 12:57 PM, "Lee Stewart" <[EMAIL PROTECTED]> wrote:

> Hi all,
>
> While I've installed and played with a number of SLES10 images, today I
> tried to clone one...
>
> When I tried to boot it, I got:
> Starting udevd
> Creating devices
> Loading dasd_mod
> Loading dasd_eckd_mod
> Activating DASDs: 0.0.0200:0dasd(eckd): 0.0.0200: 3390/0A(CU:3990/01)
> Cyl:3338 H
> ead:15 Sec:224
> dasd(eckd): 0.0.0200: (4kB blks): 2403360kB at 48kB/trk compatible disk
> layout
>   dasda:VOL1/  0X0200: dasda1
>   : done
> Loading jbd
> Loading ext3
> Waiting for device /dev/disk/by-id/ccw-HTC.1400043418.7608.10-part1
> to appear: ..not found -- exiting to /bin/sh
> $
>
>
> And of course the clone's DASD don't have the same id's as the master's.
>
> This image (I don't recall doing anything special/different during the
> install) has udev on and all the mounts (/etc/fstab) and zipl.conf all
> are referencing "by-id".
>
> The other SLES10 systems also have udev on but the mounts and zipl
> reference the devices by the device name (i.e., /dev/dasda1).
>
> I went back to the master, used Yast/Partitioner and changed it to mount
> by device name, checked /etc/fstap, manually updated /etc/zipl.conf and
> reran zipl.  Then recloned and all worked normally...
>
> The question is...   Why this time did SLES10 default to "by id"
> everywhere?   Was it something I inadvertently did?   Or??
>
> Any thoughts?
> Thanks,
> Lee
> --
>
> Lee Stewart, Senior SE

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

Re: Is it possible to do an initial SLES9 install on a partially-LVM root?

[RPN01]

One disk or twenty, LVM for all or just a few filesystems, it should still
work. So you still have some problem in your definitions that hasn't been
revealed here yet.

Since you're running into the problem during the install, there aren't a lot
of files you could post here for review. But could you walk through, in
detail, what you are doing during the install, from the point of formatting
the DASD through to the error? What options are you selecting on which
panels, and what steps you go through to define each physical volume, volume
group and logical volume? Perhaps, given this information, others here can
spot the problem, or test your config on their own systems and find the
mis-step.

If you can, take "pictures" of the major windows involved in the process.
I'm not sure that the group here will allow posting them, but you could, at
the very least, create a Flickr account and post them there, and then supply
the URL to get to them here.

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 3/14/08 8:15 AM, "Collinson.Shannon" <[EMAIL PROTECTED]>
wrote:

> We don't have mod54's yet--this is just a mod9, and we'll have static
> PAV aliases defined for the mod54s--but I assume the same logic applies.
> Does this mean that I can't use LVM for the four mountpoints (/usr,
> /var, /opt and /home) at all until we have PAV set up?  I could define
> minidisks on different volumes, but at the moment we're
> storage-crunched--I've only got 3 mod9s to work with.  If I stick with
> the current plan (/ on a separate disk, the other 4 on LVM), I'd have at
> least two filesystems overlapping--3 volumes but 5 mountpoints.  I don't
> have a problem with the I/O requests waiting in that case, but it
> appears that the SLES9 install is trying to mount the LVM filesystems at
> once, since otherwise I would have thought I'd just have a "slow
> install", not get the "file descriptor 3 left open" error.  Everything
> worked fine when I was installing all of root on a single minidisk...
>
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> Bruce Hayden
> Sent: Friday, March 14, 2008 9:01 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Is it possible to do an initial SLES9 install on a
> partially-LVM root?
>
> You need to remember that you can't start more than 1 I/O to an
> address (real or virtual!) at a time.  This is a hardware restriction.
>  This is why PAV was invented - so that the PAV alias addresses can be
> used to start parallel I/Os to the same base volume.  So - if you
> don't have PAV, then it will not help to split up your mod 54 into
> minidisks.  Linux may try to start more than 1 I/O at a time (since it
> can start one to each virtual address) but  z/VM will only execute
> them one at a time and the other I/O requests will wait.
>
> If you had HyperPAV, then splitting up the mod 54 into minidisks
> works, because then z/VM will use the PAV pool for that device to do
> I/Os to that device in parallel.  If you have static PAV, the same
> thing also works, but the alias addresses have to be set up in
> advance.  If you had SLES 10, then instead, I'd recommend that you
> define virtual PAV aliases to the guest with 1 minidisk and use
> multipath on Linux for overlapped I/O.  But - this is not supported on
> SLES 9.
>
>
>
> LEGAL DISCLAIMER
> The information transmitted is intended solely for the individual or entity to
> which it is addressed and may contain confidential and/or privileged material.
> Any review, retransmission, dissemination or other use of or taking action in
> reliance upon this information by persons or entities other than the intended
> recipient is prohibited. If you have received this email in error please
> contact the sender and delete the material from any computer.
>
> SunTrust and Seeing beyond money are federally registered service marks of
> SunTrust Banks, Inc.
> [ST:XCL]
>
>
>
>
>
> --
> 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

Re: Is it possible to do an initial SLES9 install on a partially-LVM root?

[RPN01]

Hi Mark;

You suggest FCP for larger disk allocations, and we've looked at that here,
but we've back-burnered it for two reasons.

The first is mirroring. With our mainframe DASD, we get mirroring for free
(meaning that it requires no software or CPU time or additional I/Os within
our Linux guests). If we start using FCP, suddenly we have to do our own
mirroring in Linux, which means double the I/O, more CPU, and additional
software in the install to support it. Also, current Linux mirroring does
not keep duplicate copies of the mirroring index, meaning that if you lose
the master of the mirror set which contains the index, once it's back up
your only choice is to re-mirror the entire disk, or set of disks. We've had
to do this in our Intel Linux environment; it took several days for it to
catch up.

The second is multipathing. Again, using DASD, this is entirely free, and
handled at the controller level. Doing so with FCP requires additional
software in Linux to set up the redundant paths, and this translates into
more CPU expended to provide the feature.

These two bottlenecks have kept us from trying to exploit FCP. We mirror and
multipath everything, in all environments (mainframe, Intel Linux, Solaris,
AIX...), so it isn't just a special project consideration; it's a
requirement for installing a system here. (We're a medical facility; we like
things to survive, be it patients or computers. :-)

--
Robert P. Nix  Mayo Foundation.~.
RO-OE-5-55 200 First Street SW/V\
507-284-0844   Rochester, MN 55905   /( )\
-^^-^^
"In theory, theory and practice are the same, but
 in practice, theory and practice are different."




On 3/13/08 5:01 PM, "Mark Post" <[EMAIL PROTECTED]> wrote:

> To be able to use striping, you need more than one virtual disk/minidisk.
> Mod-54s sounds like you're planning on a lot of data.  SCSI over FCP should be
> considered at that point.

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