Re: Lingo 3G (text Clustering)/Network Workbench: A Workbench for Network Scientists
Klein, Robert (NIH/CIT) [C] wrote:
One of our potential customers would like to be able to use an open source
program called Lingo 3G and another program called Network Workbench. We are
not able to compile Lingo3G for zLinux (Red Hat) because the source requires
some x86 libraries. This is the 2nd time we have run into this problem making
an open source program available on zLinux. (1) (mainly for IBM/Red Hat)
What, if any, plans are there for dealing with the problem of making open
source programs that require x86 libraries able to run on zLinux. The
inability to compile various open source software for the zLinux platform
greatly restricts the customer base we can tap for our zLinux platform. (2)
Does anyone know of any comparable alternative to Lingo 3G?
x86 libraries are made from source built for Intellish systems. There is
little prospect of using x86 libraries on Zeds.
What I would expect of an open source project is the source code so that
I can build any needed libraries myself.
Your gripe, }The inability to compile various open source software for
the zLinux platform greatly restricts the customer base we can tap for
our zLinux platform, is unreasonable. Requirements for building any
open source project for zLinux should be the same as for Linux IA32,
AMD-64, Power, Sparc, Sparc64 (can I ignore MIPS*). The needed compilers
and third-party libraries for your architecture, and the source code and
the documentation.
Third-party libraries not shipped by your vendor may be problematic as a
lot of OSS developers won't have access to zHardware. Helping them out
with that, and/or with setting up their own virtual Z using Hercules and
Fedora (CentOS5 if/when it becomes available), or an evaluation copy o
SLE{S,D} (which they can run past the evaluation period, just without
updates) or RHEL (I don't know the rules about evaluation licences
there), then those might become available too.
Oh, IBM may (it used to) have Zhardware available free of charge to
developers for some purposes.
--
Cheers
John
-- spambait
1...@coco.merseine.nu z1...@coco.merseine.nu
-- 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SHMALL and SHMMAX
Deric Abel wrote: -- Shared Memory Limits max number of segments = 4096 max seg size (kbytes) = 18014398509481983 max total shared memory (kbytes) = 4611686018427386880 min seg size (bytes) = 1 I don't know about you, but that total shared memory can't be good to have that large of a number. Is this a bug (or a feature ;) )? Feature, it seems. See https://bugzilla.novell.com/show_bug.cgi?id=146656 (requires a Novell user ID to access). Regards, Peter Oberparleiter -- 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: Lingo 3G (text Clustering)/Network Workbench: A Workbench for Network Scientists
Oh, IBM may (it used to) have Zhardware available free of charge to developers for some purposes. Older hardware. With the minimum z10 requirement for newer versions of VM and Linux, there hasn't been much discussion about upgrading same.
Re: Moving a Samba directory
When you cycle the samba server, all connection to the shares will be broken but the clients reconnect when they see this happen. At least for windows clients, this should be transparent unless someone tries to access your server in the exact time you are restarting it. Before you restart your server, you can issue a SMBSTATUS command to see if there are any open files or not. You will see client connections to shares but you want to watch out for open files. If you recycle the server while files are open, those application with open files will get upset. You can minimize your samba outage to seconds by using the RSYNC command I pointed out in an earlier post just before you shutdown your samba server and immediately after you shutdown the server and before you start it again in its new home. Depending on the size of your file system, this could be just seconds. I am not sure how much shorter you can make this outage. Aria -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Tom Duerbusch Sent: Wednesday, September 09, 2009 4:39 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Moving a Samba directory Like I said, I knew the answer to this one (i.e. shutdown Samba), but I hoping for a quick and dirty way, of doing the conversion with Samba still up. Well, once this is done, I can then add disks to the LVM on the fly. Just hate to have to do the scheduling of downtime (users and servers) when I know no one is going to be active anyway, just their shares are in use. Right? When I cycle the server, the users have to reaccess their shares? It's the servers that are accessing the Samba shares, then also have to be cycledand those users have to be notified... Thanks Tom Duerbusch THD Consulting Justin Payne jpa...@redhat.com 9/9/2009 2:41 PM If you do not stop the samba service you run a risk of files being accessed during the move, and this could lead to corruption of the new files. As recommended before, you should be able to copy the bulk of the data without shutting down the service. With the bulk of the data mirrored on the new LVM, the second rsync will be quite quick at syncing only the changes so downtime will be minimal. It would be best to plan a brief outage of the samba service to complete the task you have outlined. Justin Payne On 09/09/2009 12:53 PM, Tom Duerbusch wrote: I think I know the answer to this one, but then, I don't know how much I don't knowG. I have a Samba server that runs 24X7. It is rarely used at night, but still has Windows shares active. The /home directory is located off the / directory (dasda1). It needs more space. I've created a LVM with a directory name of /home2. I plan on copying the /home directory to /home2, rename /home to /homeold, and rename /home2 to /home. Simple. What is Samba going to think about this? Do I need to cycle Samba, and have all the currently connected users, reconnect? Or as long as Samba isn't trying to access a file during this period of time, would it care? Part of this is trying to decide how much notification I have to give the end users, and there are a couple servers that also have Samba shares. I don't know how to reconnect them, other than cycling those servers, which, then requires additional notification. On my test system, I moved the Samba /home directory to a LVM setup. No problem. But I didn't have any currently accessed shares at that time (poor test plan). Thanks for any input and direction. Tom Duerbusch THD Consulting - - 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: Moving a Samba directory
Thanks Aria SMBSTATUS is a good thing to know. I'm not worried about syncing files using RSYNC as the only time this Samba server is updated is during 1st shiftwell, so far. I will be doing the expansion during the 3td shift. Tom Duerbusch THD Consulting Aria Bamdad a...@bsc.gwu.edu 9/11/2009 8:12 AM When you cycle the samba server, all connection to the shares will be broken but the clients reconnect when they see this happen. At least for windows clients, this should be transparent unless someone tries to access your server in the exact time you are restarting it. Before you restart your server, you can issue a SMBSTATUS command to see if there are any open files or not. You will see client connections to shares but you want to watch out for open files. If you recycle the server while files are open, those application with open files will get upset. You can minimize your samba outage to seconds by using the RSYNC command I pointed out in an earlier post just before you shutdown your samba server and immediately after you shutdown the server and before you start it again in its new home. Depending on the size of your file system, this could be just seconds. I am not sure how much shorter you can make this outage. Aria -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Tom Duerbusch Sent: Wednesday, September 09, 2009 4:39 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Moving a Samba directory Like I said, I knew the answer to this one (i.e. shutdown Samba), but I hoping for a quick and dirty way, of doing the conversion with Samba still up. Well, once this is done, I can then add disks to the LVM on the fly. Just hate to have to do the scheduling of downtime (users and servers) when I know no one is going to be active anyway, just their shares are in use. Right? When I cycle the server, the users have to reaccess their shares? It's the servers that are accessing the Samba shares, then also have to be cycledand those users have to be notified... Thanks Tom Duerbusch THD Consulting Justin Payne jpa...@redhat.com 9/9/2009 2:41 PM If you do not stop the samba service you run a risk of files being accessed during the move, and this could lead to corruption of the new files. As recommended before, you should be able to copy the bulk of the data without shutting down the service. With the bulk of the data mirrored on the new LVM, the second rsync will be quite quick at syncing only the changes so downtime will be minimal. It would be best to plan a brief outage of the samba service to complete the task you have outlined. Justin Payne On 09/09/2009 12:53 PM, Tom Duerbusch wrote: I think I know the answer to this one, but then, I don't know how much I don't knowG. I have a Samba server that runs 24X7. It is rarely used at night, but still has Windows shares active. The /home directory is located off the / directory (dasda1). It needs more space. I've created a LVM with a directory name of /home2. I plan on copying the /home directory to /home2, rename /home to /homeold, and rename /home2 to /home. Simple. What is Samba going to think about this? Do I need to cycle Samba, and have all the currently connected users, reconnect? Or as long as Samba isn't trying to access a file during this period of time, would it care? Part of this is trying to decide how much notification I have to give the end users, and there are a couple servers that also have Samba shares. I don't know how to reconnect them, other than cycling those servers, which, then requires additional notification. On my test system, I moved the Samba /home directory to a LVM setup. No problem. But I didn't have any currently accessed shares at that time (poor test plan). Thanks for any input and direction. Tom Duerbusch THD Consulting - - 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
Re: Moving a Samba directory
Thanks Mark I can slip this thru and cycle the Samba server, during a known time period where no one is actively accessing Samba files. Thanks Tom Duerbusch THD Consulting Mark Post mp...@novell.com 9/9/2009 6:14 PM On 9/9/2009 at 4:38 PM, Tom Duerbusch duerbus...@stlouiscity.com wrote: -snip- Right? When I cycle the server, the users have to reaccess their shares? I doubt it. The Windows clients won't know that Samba has been cycled, so they will just try to re-establish the connection the next time the user tries to use it. It will likely be fairly transparent to them. 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 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: Dasd_diag_mod question
Following is the method I used to switch a swap from FBA to DIAG. I did not wish to use the third party SWAPGEN EXEC. 1) update /etc/init.d/boot.swap remove mkswap command shutdown 2) update PROFILE EXEC (swaps are formatted here) change format 162 h to format 162 h (blksize 512 boot system 3) YaST DASD : Deactivate the 162 device set Diag On for the 162 device Activate the 162 device Set MODULE=dasd_fba_mod instead of MODULE=dasd_diag_mod in /etc/sysconfig/hardware/hwcfg-dasd-bus-ccw-0.0.0162 leave as is DASD_USE_DIAG=1 mkswap /dev/dasdd1 swapon -a lsdasd (swap device 162 should show as DIAG now, not FBA) cd /boot mkinitrd zipl -V update /etc/init.d/boot.swap add mkswap command shutdown boot system again --- On Wed, 7/29/09, Mrohs, Ray ray.mr...@usdoj.gov wrote: From: Mrohs, Ray ray.mr...@usdoj.gov Subject: Dasd_diag_mod question To: LINUX-390@VM.MARIST.EDU Date: Wednesday, July 29, 2009, 2:04 PM Hi All, We are running SLES10 SP2, and I am trying to switch our vdisk swap from fba to diag. So far I: 1) run SWAPGEN EXEC with the reuse option (vdisks are defined in the CP directory) 2) included dasd_diag_mod in the kernel configuration and ran mkinitrd (verified with lsmod) 3) set the yast DASD option to use diag for the vdisk devices (verified in /etc/sysconfig/hardware/*) 4) included the devices in fstab as swap 5) reboot /etc/fstab: /dev/dasdf1 none swap sw 0 0 /dev/dasdg1 none swap sw 0 0 /dev/dasdh1 none swap sw 0 0 Swapon -s: Filename Type Size Used Priority /dev/dasdf1 partition 123948 0 -1 /dev/dasdg1 partition 247912 0 -2 /dev/dasdh1 partition 371872 0 -3 But the disks still show up like this: 0.0.0105(FBA ) at ( 94: 20) is dasdf : active at blocksize 512, 25 blocks, 122 MB 0.0.0106(FBA ) at ( 94: 24) is dasdg : active at blocksize 512, 50 blocks, 244 MB 0.0.0107(FBA ) at ( 94: 28) is dasdh : active at blocksize 512, 75 blocks, 366 MB How can I figure out what's missing? Any help is appreciated. Ray Mrohs US DOJ -- 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: Dasd_diag_mod question
On 9/11/2009 at 11:20 AM, Larry Uher larry...@yahoo.com wrote: Following is the method I used to switch a swap from FBA to DIAG. I did not wish to use the third party SWAPGEN EXEC. Any particular reason? I recommend it to all my z/VM customers. 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
Re: Dasd_diag_mod question
I guess my question would be why is a complex EXEC needed to do a normal system administration task? A second question is why didn't Novell provide a straightforward method for doing this and document it in a manual (without using a complex 3rd party EXEC) ? --- On Fri, 9/11/09, Mark Post mp...@novell.com wrote: From: Mark Post mp...@novell.com Subject: Re: Dasd_diag_mod question To: LINUX-390@VM.MARIST.EDU Date: Friday, September 11, 2009, 3:33 PM On 9/11/2009 at 11:20 AM, Larry Uher larry...@yahoo.com wrote: Following is the method I used to switch a swap from FBA to DIAG. I did not wish to use the third party SWAPGEN EXEC. Any particular reason? I recommend it to all my z/VM customers. 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 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: Dasd_diag_mod question
On 9/11/2009 at 11:36 AM, Larry Uher larry...@yahoo.com wrote: I guess my question would be why is a complex EXEC needed to do a normal system administration task? It's not all that complex, just a lot of parameter parsing and error checking surrounding a couple of lines of code that actually do the work. The reason why it's useful is so that people using VDISKs don't need to have their Linux admins make any changes to the Linux system itself, and so it doesn't appear to be different from midrange Linux systems. Eliminating these platform specific differences helps ease acceptance of the platform. It's also good system management practice in that you're not modifying distribution-provided scripts that will get over-written at some point by maintenance or an upgrade. Saves time, less hassle in the long run. A second question is why didn't Novell provide a straightforward method for doing this and document it in a manual (without using a complex 3rd party EXEC) ? When SWAPGEN was written, the Linux distribution providers had much bigger fish to fry. After it was written, there wasn't a need for them to do anything, since a solution already existed. Limited resources, re-inventing wheels, etc., etc. And, given the growth and evolution of the platform, there are still far bigger fish that need frying, perhaps more than before. 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
Re: Dasd_diag_mod question
I don't consider it complex; it's very useful. Thanks to SineNomine. Patrick Carroll | Enterprise Technical Architect L.L.Bean, Inc.® | Double L St. | Freeport ME 04033 http://www.llbean.com | pcarr...@llbean.com | 207.552.2426 CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s). Any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Larry Uher Sent: Friday, September 11, 2009 11:37 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Dasd_diag_mod question I guess my question would be why is a complex EXEC needed to do a normal system administration task? A second question is why didn't Novell provide a straightforward method for doing this and document it in a manual (without using a complex 3rd party EXEC) ? --- On Fri, 9/11/09, Mark Post mp...@novell.com wrote: From: Mark Post mp...@novell.com Subject: Re: Dasd_diag_mod question To: LINUX-390@VM.MARIST.EDU Date: Friday, September 11, 2009, 3:33 PM On 9/11/2009 at 11:20 AM, Larry Uher larry...@yahoo.com wrote: Following is the method I used to switch a swap from FBA to DIAG. I did not wish to use the third party SWAPGEN EXEC. Any particular reason? I recommend it to all my z/VM customers. 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 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: Dasd_diag_mod question
And if you put it in your PROFILE EXEC then as soon as the guest is autologged the disk is created and the system can then be booted by the PROFILE EXEC. On 9/11/09 11:52 AM, Mark Post mp...@novell.com wrote: On 9/11/2009 at 11:36 AM, Larry Uher larry...@yahoo.com wrote: It's not all that complex, just a lot of parameter parsing and error checking surrounding a couple of lines of code that actually do the work. The reason why it's useful is so that people using VDISKs don't need to have their Linux admins make any changes to the Linux system itself, and so it doesn't appear to be different from midrange Linux systems. Eliminating these platform specific differences helps ease acceptance of the platform. It's also good system management practice in that you're not modifying distribution-provided scripts that will get over-written at some point by maintenance or an upgrade. Saves time, less hassle in the long run. -- 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: Dasd_diag_mod question
On Sep 11, 2009, at 10:36 AM, Larry Uher wrote: I guess my question would be why is a complex EXEC needed to do a normal system administration task? A second question is why didn't Novell provide a straightforward method for doing this and document it in a manual (without using a complex 3rd party EXEC) ? Complex? After the description and the license and update comment blocks, it's about 240 lines. Of those, about 120 are the various ways the program can exit (with descriptive text) and the help message. That leaves about 120 lines of actual code, and those lines are not dense (e.g. one line per pipe stage). That handles both the raw FBA and the DIAG device cases. It's not a normal system administration task on any other Linux architecture. It's really quite unusual for your swap device to be destroyed and recreated every time you power on the machine. In the normal case the swap signature sits there between power cycles. That's why Dave and I wrote the thing in the first place--Linux does not generally consider needing to format the swap device as part of its normal bootup routine and rather than mess with system startup scripts and their ordering, we thought it was a lot easier to just take care of it in CMS before handing control to Linux, so that the swap device was pre-prepared like it expected. And that, by the way, is the reason Novell doesn't do it: it's not a task that's necessary on other architectures, and Novell, not surprisingly, likes to keep as much the same between platforms as possible. Adam -- 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: Dasd_diag_mod question
My complaint with SWAPGEN going back to when it was first announced was
that it needs to know the number of blocks to format. This means that
if the size or number of the vdisk(s) changes in the directory, the VM
admin also has to go to the target machine's 191 disk and update the
PROFILE EXEC so the right number of blocks get formatted on the right
devices. Having to change things in multiple places seemed like
something to be avoided.
So I wrote a Linux init script that does the whole thing internally
within the guest. It finds all of the FBA disks, formats them, and runs
mkswap. It also enables them in increasing priority order, so they get
used before the default DASD swap partition, and it handles the diag
module and enabling access via diag. We use this on about 100 guests,
and it works very well. My only complaint with it is that it treats all
FBA disks as swap disks, which might be a problem if we had any real FBA
disks, but since we're entirely on 3390's and the odd FCP device, it's a
non issue. It also generates one bogus error message that I never got
around to suppressing.
This version is for Red Hat (RHEL5), but it shouldn't be hard to
customize for Suse.
#!/bin/bash
# $Id: vdswap,v 1.7 2007/11/06 20:44:38 root Exp $
#
# vdswapThis shell script does the following:
# 1) Looks in sysfs for any FBA disks
# 2) If they are not already enabled for swap, it formats
# them, and enables them for swap with a higher
priority
# than the default disk swap space
#
# Should run after filesystems are mounted, before starting required
daemons
# that might need to be configured
#
# chkconfig: 2345 01 99
# Description: Formats and enables vdisk swap spaces
#
prog=`basename $0`
start() {
SYSDEV=/sys/bus/ccw/drivers/dasd-fba
echo Enabling vdisk swap spaces
modprobe -q dasd_diag_mod
if ls $SYSDEV | grep -q 0.0 ; then
PRIO=1
for A in $SYSDEV/0.0.*
do
DEVICE=`ls $A/block* | grep dasd | head -n 1`
if lsmod | grep -q dasd_diag_mod ; then
echo 0 $A/online
echo 1 $A/use_diag
echo 1 $A/online
sleep 1
fi
DEVBASE=${DEVICE:0:${#DEVICE}-1}
if ! swapon -s | grep -q $DEVBASE ; then
parted -s /dev/$DEVBASE mkpartfs primary swap 1
mkswap /dev/$DEVICE
swapon -p $PRIO /dev/$DEVICE
let PRIO=$PRIO+1
fi
done
fi
touch /var/lock/subsys/vdswap
}
stop() {
echo -n $Shutting down $prog:
rm -f /var/lock/subsys/vdswap
return 0
}
# See how we were called.
case $1 in
start)
start
;;
stop)
stop
;;
status)
status vdswap
RETVAL=0
;;
restart|reload)
stop
start
RETVAL=$?
;;
condrestart)
RETVAL=0
;;
*)
echo $Usage: $0 {start|stop|restart|condrestart|status}
exit 1
esac
exit $RETVAL
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Adam Thornton
Sent: Friday, September 11, 2009 12:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Dasd_diag_mod question
On Sep 11, 2009, at 10:36 AM, Larry Uher wrote:
I guess my question would be why is a complex EXEC needed to do a
normal system administration task? A second question is why didn't
Novell provide a straightforward method for doing this and document it
in a manual (without using a complex 3rd party EXEC) ?
Complex?
After the description and the license and update comment blocks, it's
about 240 lines. Of those, about 120 are the various ways the program
can exit (with descriptive text) and the help message. That leaves
about 120 lines of actual code, and those lines are not dense (e.g.
one line per pipe stage). That handles both the raw FBA and the DIAG
device cases.
It's not a normal system administration task on any other Linux
architecture. It's really quite unusual for your swap device to be
destroyed and recreated every time you power on the machine. In the
normal case the swap signature sits there between power cycles.
That's why Dave and I wrote the thing in the first place--Linux does
not generally consider needing to format the swap device as part of
its normal bootup routine and rather than mess with system startup
scripts and their ordering, we thought it was a lot easier to just
take care of it in CMS before handing control to Linux, so that the
swap device was pre-prepared like it expected.
And that, by the way, is the reason Novell doesn't do it: it's not a
task that's necessary on other architectures, and Novell, not
surprisingly, likes to keep as much the same between platforms as
Re: Dasd_diag_mod question
On Sep 11, 2009, at 12:02 PM, Hall, Ken (GTS) wrote: My complaint with SWAPGEN going back to when it was first announced was that it needs to know the number of blocks to format. This means that if the size or number of the vdisk(s) changes in the directory, the VM admin also has to go to the target machine's 191 disk and update the PROFILE EXEC so the right number of blocks get formatted on the right devices. Having to change things in multiple places seemed like something to be avoided. Hm. Did you ever send us a requirement for that? If so, I apologize for having missed it. Since we already look for the number of blocks in the reuse code, I think it should be pretty straightforward to do that check and then use the number of blocks detected if the user doesn't specify. Adam -- 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: Dasd_diag_mod question
Changing the size isn't an issue for me; I size memory so that we *barely* swap
anyway. I've never has to change the size of a vdisk.
Spelling courtesy of Blackberry
- Original Message -
From: Linux on 390 Port LINUX-390@VM.MARIST.EDU
To: LINUX-390@VM.MARIST.EDU LINUX-390@VM.MARIST.EDU
Sent: Fri Sep 11 13:02:54 2009
Subject: Re: Dasd_diag_mod question
My complaint with SWAPGEN going back to when it was first announced was
that it needs to know the number of blocks to format. This means that
if the size or number of the vdisk(s) changes in the directory, the VM
admin also has to go to the target machine's 191 disk and update the
PROFILE EXEC so the right number of blocks get formatted on the right
devices. Having to change things in multiple places seemed like
something to be avoided.
So I wrote a Linux init script that does the whole thing internally
within the guest. It finds all of the FBA disks, formats them, and runs
mkswap. It also enables them in increasing priority order, so they get
used before the default DASD swap partition, and it handles the diag
module and enabling access via diag. We use this on about 100 guests,
and it works very well. My only complaint with it is that it treats all
FBA disks as swap disks, which might be a problem if we had any real FBA
disks, but since we're entirely on 3390's and the odd FCP device, it's a
non issue. It also generates one bogus error message that I never got
around to suppressing.
This version is for Red Hat (RHEL5), but it shouldn't be hard to
customize for Suse.
#!/bin/bash
# $Id: vdswap,v 1.7 2007/11/06 20:44:38 root Exp $
#
# vdswapThis shell script does the following:
# 1) Looks in sysfs for any FBA disks
# 2) If they are not already enabled for swap, it formats
# them, and enables them for swap with a higher
priority
# than the default disk swap space
#
# Should run after filesystems are mounted, before starting required
daemons
# that might need to be configured
#
# chkconfig: 2345 01 99
# Description: Formats and enables vdisk swap spaces
#
prog=`basename $0`
start() {
SYSDEV=/sys/bus/ccw/drivers/dasd-fba
echo Enabling vdisk swap spaces
modprobe -q dasd_diag_mod
if ls $SYSDEV | grep -q 0.0 ; then
PRIO=1
for A in $SYSDEV/0.0.*
do
DEVICE=`ls $A/block* | grep dasd | head -n 1`
if lsmod | grep -q dasd_diag_mod ; then
echo 0 $A/online
echo 1 $A/use_diag
echo 1 $A/online
sleep 1
fi
DEVBASE=${DEVICE:0:${#DEVICE}-1}
if ! swapon -s | grep -q $DEVBASE ; then
parted -s /dev/$DEVBASE mkpartfs primary swap 1
mkswap /dev/$DEVICE
swapon -p $PRIO /dev/$DEVICE
let PRIO=$PRIO+1
fi
done
fi
touch /var/lock/subsys/vdswap
}
stop() {
echo -n $Shutting down $prog:
rm -f /var/lock/subsys/vdswap
return 0
}
# See how we were called.
case $1 in
start)
start
;;
stop)
stop
;;
status)
status vdswap
RETVAL=0
;;
restart|reload)
stop
start
RETVAL=$?
;;
condrestart)
RETVAL=0
;;
*)
echo $Usage: $0 {start|stop|restart|condrestart|status}
exit 1
esac
exit $RETVAL
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Adam Thornton
Sent: Friday, September 11, 2009 12:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Dasd_diag_mod question
On Sep 11, 2009, at 10:36 AM, Larry Uher wrote:
I guess my question would be why is a complex EXEC needed to do a
normal system administration task? A second question is why didn't
Novell provide a straightforward method for doing this and document it
in a manual (without using a complex 3rd party EXEC) ?
Complex?
After the description and the license and update comment blocks, it's
about 240 lines. Of those, about 120 are the various ways the program
can exit (with descriptive text) and the help message. That leaves
about 120 lines of actual code, and those lines are not dense (e.g.
one line per pipe stage). That handles both the raw FBA and the DIAG
device cases.
It's not a normal system administration task on any other Linux
architecture. It's really quite unusual for your swap device to be
destroyed and recreated every time you power on the machine. In the
normal case the swap signature sits there between power cycles.
That's why Dave and I wrote the thing in the first place--Linux does
not generally consider needing to format the swap device as part of
its normal bootup routine and rather than mess with system startup
scripts and
Re: Dasd_diag_mod question
Didn't seem worth it. The scheme we use works fine, and didn't require us to change PROFILE EXEC on 50-odd servers. The package containing the script was rolled out with a scheduled update on the Linux side. The directory changes could be scripted through VMSecure. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Adam Thornton Sent: Friday, September 11, 2009 1:09 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Dasd_diag_mod question On Sep 11, 2009, at 12:02 PM, Hall, Ken (GTS) wrote: My complaint with SWAPGEN going back to when it was first announced was that it needs to know the number of blocks to format. This means that if the size or number of the vdisk(s) changes in the directory, the VM admin also has to go to the target machine's 191 disk and update the PROFILE EXEC so the right number of blocks get formatted on the right devices. Having to change things in multiple places seemed like something to be avoided. Hm. Did you ever send us a requirement for that? If so, I apologize for having missed it. Since we already look for the number of blocks in the reuse code, I think it should be pretty straightforward to do that check and then use the number of blocks detected if the user doesn't specify. Adam -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to Merrill Lynch are references to any company in the Merrill Lynch Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Dasd_diag_mod question
We use two vdisks, plus one DASD swap. If the guest overflows the first vdisk,
it's time to watch it. If it overflows the second, it's time to increase the
memory.
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Pat
Carroll
Sent: Friday, September 11, 2009 1:14 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Dasd_diag_mod question
Changing the size isn't an issue for me; I size memory so that we *barely* swap
anyway. I've never has to change the size of a vdisk.
Spelling courtesy of Blackberry
- Original Message -
From: Linux on 390 Port LINUX-390@VM.MARIST.EDU
To: LINUX-390@VM.MARIST.EDU LINUX-390@VM.MARIST.EDU
Sent: Fri Sep 11 13:02:54 2009
Subject: Re: Dasd_diag_mod question
My complaint with SWAPGEN going back to when it was first announced was
that it needs to know the number of blocks to format. This means that
if the size or number of the vdisk(s) changes in the directory, the VM
admin also has to go to the target machine's 191 disk and update the
PROFILE EXEC so the right number of blocks get formatted on the right
devices. Having to change things in multiple places seemed like
something to be avoided.
So I wrote a Linux init script that does the whole thing internally
within the guest. It finds all of the FBA disks, formats them, and runs
mkswap. It also enables them in increasing priority order, so they get
used before the default DASD swap partition, and it handles the diag
module and enabling access via diag. We use this on about 100 guests,
and it works very well. My only complaint with it is that it treats all
FBA disks as swap disks, which might be a problem if we had any real FBA
disks, but since we're entirely on 3390's and the odd FCP device, it's a
non issue. It also generates one bogus error message that I never got
around to suppressing.
This version is for Red Hat (RHEL5), but it shouldn't be hard to
customize for Suse.
#!/bin/bash
# $Id: vdswap,v 1.7 2007/11/06 20:44:38 root Exp $
#
# vdswapThis shell script does the following:
# 1) Looks in sysfs for any FBA disks
# 2) If they are not already enabled for swap, it formats
# them, and enables them for swap with a higher
priority
# than the default disk swap space
#
# Should run after filesystems are mounted, before starting required
daemons
# that might need to be configured
#
# chkconfig: 2345 01 99
# Description: Formats and enables vdisk swap spaces
#
prog=`basename $0`
start() {
SYSDEV=/sys/bus/ccw/drivers/dasd-fba
echo Enabling vdisk swap spaces
modprobe -q dasd_diag_mod
if ls $SYSDEV | grep -q 0.0 ; then
PRIO=1
for A in $SYSDEV/0.0.*
do
DEVICE=`ls $A/block* | grep dasd | head -n 1`
if lsmod | grep -q dasd_diag_mod ; then
echo 0 $A/online
echo 1 $A/use_diag
echo 1 $A/online
sleep 1
fi
DEVBASE=${DEVICE:0:${#DEVICE}-1}
if ! swapon -s | grep -q $DEVBASE ; then
parted -s /dev/$DEVBASE mkpartfs primary swap 1
mkswap /dev/$DEVICE
swapon -p $PRIO /dev/$DEVICE
let PRIO=$PRIO+1
fi
done
fi
touch /var/lock/subsys/vdswap
}
stop() {
echo -n $Shutting down $prog:
rm -f /var/lock/subsys/vdswap
return 0
}
# See how we were called.
case $1 in
start)
start
;;
stop)
stop
;;
status)
status vdswap
RETVAL=0
;;
restart|reload)
stop
start
RETVAL=$?
;;
condrestart)
RETVAL=0
;;
*)
echo $Usage: $0 {start|stop|restart|condrestart|status}
exit 1
esac
exit $RETVAL
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Adam Thornton
Sent: Friday, September 11, 2009 12:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Dasd_diag_mod question
On Sep 11, 2009, at 10:36 AM, Larry Uher wrote:
I guess my question would be why is a complex EXEC needed to do a
normal system administration task? A second question is why didn't
Novell provide a straightforward method for doing this and document it
in a manual (without using a complex 3rd party EXEC) ?
Complex?
After the description and the license and update comment blocks, it's
about 240 lines. Of those, about 120 are the various ways the program
can exit (with descriptive text) and the help message. That leaves
about 120 lines of actual code, and those lines are not dense (e.g.
one line per pipe stage). That handles both the raw FBA and the DIAG
device cases.
It's not a normal system administration task on any other Linux
architecture. It's
Re: Dasd_diag_mod question
On Fri, Sep 11, 2009 at 5:36 PM, Larry Uher larry...@yahoo.com wrote: I guess my question would be why is a complex EXEC needed to do a normal system administration task? A second question is why didn't Novell provide a straightforward method for doing this and document it in a manual (without using a complex 3rd party EXEC) ? There will be plenty of us reminding you on this post when you found something happened to the order of your disks in the virtual machine configuration and the mkswap wiped out your root file system or some other relevant data... 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
Re: Dasd_diag_mod question
There will be plenty of us reminding you on this post when you found something happened to the order of your disks in the virtual machine configuration and the mkswap wiped out your root file system or some other relevant data... That shouldn't happen if you are using udev to address them Pieter Harder 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
Re: Dasd_diag_mod question
So, for those of you playing along at home: I'll eventually release a new VMARC, but I need to find and update the help file sources first, and I need to do the whole thing under update control and build the package, and in the meantime: I'm using the 0803 SWAPGEN as my starting point. Lines 243-244 read: parse var msg . . . . . newblks . if blks newblks then signal WrongBlks/* Mismatch, error */ Between these two lines, stick: if blks = '' then blks = newblks (that's two single quotes, not one double quote) And there you go: if you use REUSE (as you would if the VDISK is specified in your directory entry) then you no longer need to specify the number of blocks. Adam -- 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: Dasd_diag_mod question
I guess my question would be why is a complex EXEC needed to do a normal system administration task? It's a multi-step process whether you do it at the hypervisor level or inside the Linux guest, so you're going to need some kind of scripting either way. The basic Unix philosophy is write tools that do one thing well, then use scripting to sequence the execution of the one-thing tools to accomplish bigger tasks. You could write a custom tool that did it all -- but you'd be duplicating a lot of work and you'd have to maintain it over time. Big PITA. I happen to be of the school that it's easier and simpler for this kind of preparation work to be done at the hypervisor level, and let the guest OS concentrate on identifying stuff it can use and managing the process of devices coming and going in a rational way. In this case, also, having swap is kind of necessary to getting Linux to run decently, and it's hard to do Linux stuff without a running Linux system, so creating SWAPGEN was a way to do the deed before you had a running Linux system to do it with. A second question is why didn't Novell provide a straightforward method for doing this and document it in a manual (without using a complex 3rd party EXEC) ? It sounds like the issue is more that it's a 3rd party tool than that it's done the way it's done. If either of the distributors wants to include SWAPGEN, we're open to discussing the idea. No one has asked. It would be nice if the documentation included the way to set up DIAG disk I/O, though. -- db David Boyes Sine Nomine Associates -- 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: Dasd_diag_mod question
When SWAPGEN was written, the Linux distribution providers had much bigger fish to fry. When SWAPGEN was written, there WEREN'T any distribution providers for 390 (other than Marist, who definitely had other things to do). 8-) As you say, though, ain't broke, don't fix it. -- db -- 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: Dasd_diag_mod question
On Sep 11, 2009, at 12:59 PM, David Boyes wrote: It sounds like the issue is more that it's a 3rd party tool than that it's done the way it's done. If either of the distributors wants to include SWAPGEN, we're open to discussing the idea. No one has asked. They don't even need to ask, actually. It's under the Artistic License, which is OSI-approved. Just saying. Adam -- 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: Dasd_diag_mod question
My complaint with SWAPGEN going back to when it was first announced was that it needs to know the number of blocks to format. Actually, it needs to know how many blocks to define if you don't want to code it in the directory entry -- it always formats everything. If you put the VDISK in the CP directory entry and use the REUSE option, SWAPGEN will simply format what's there and write the signature on the disk. -- 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: Dasd_diag_mod question
On Sep 11, 2009, at 1:15 PM, David Boyes wrote: My complaint with SWAPGEN going back to when it was first announced was that it needs to know the number of blocks to format. Actually, it needs to know how many blocks to define if you don't want to code it in the directory entry -- it always formats everything. If you put the VDISK in the CP directory entry and use the REUSE option, SWAPGEN will simply format what's there and write the signature on the disk. Well, NOW it will, with the change I just posted. Adam -- 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: Dasd_diag_mod question
I prefer running SWAPGEN under CMS before starting Linux. If my primary background were Linux, I might feel differently. Adam's fix to pick up the disk size from the directory certainly makes things easier. Dennis O'Brien My computer beat me at chess, but it was no match for me in kickboxing. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of David Boyes Sent: Friday, September 11, 2009 10:59 To: LINUX-390@VM.MARIST.EDU Subject: Re: Dasd_diag_mod question I guess my question would be why is a complex EXEC needed to do a normal system administration task? It's a multi-step process whether you do it at the hypervisor level or inside the Linux guest, so you're going to need some kind of scripting either way. The basic Unix philosophy is write tools that do one thing well, then use scripting to sequence the execution of the one-thing tools to accomplish bigger tasks. You could write a custom tool that did it all -- but you'd be duplicating a lot of work and you'd have to maintain it over time. Big PITA. I happen to be of the school that it's easier and simpler for this kind of preparation work to be done at the hypervisor level, and let the guest OS concentrate on identifying stuff it can use and managing the process of devices coming and going in a rational way. In this case, also, having swap is kind of necessary to getting Linux to run decently, and it's hard to do Linux stuff without a running Linux system, so creating SWAPGEN was a way to do the deed before you had a running Linux system to do it with. A second question is why didn't Novell provide a straightforward method for doing this and document it in a manual (without using a complex 3rd party EXEC) ? It sounds like the issue is more that it's a 3rd party tool than that it's done the way it's done. If either of the distributors wants to include SWAPGEN, we're open to discussing the idea. No one has asked. It would be nice if the documentation included the way to set up DIAG disk I/O, though. -- db David Boyes Sine Nomine Associates -- 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: Dasd_diag_mod question
It's a religious debate at this point. We had our reasons for doing it the way we did at the time. YMMV. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of O'Brien, Dennis L Sent: Friday, September 11, 2009 2:52 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Dasd_diag_mod question I prefer running SWAPGEN under CMS before starting Linux. If my primary background were Linux, I might feel differently. Adam's fix to pick up the disk size from the directory certainly makes things easier. Dennis O'Brien My computer beat me at chess, but it was no match for me in kickboxing. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of David Boyes Sent: Friday, September 11, 2009 10:59 To: LINUX-390@VM.MARIST.EDU Subject: Re: Dasd_diag_mod question I guess my question would be why is a complex EXEC needed to do a normal system administration task? It's a multi-step process whether you do it at the hypervisor level or inside the Linux guest, so you're going to need some kind of scripting either way. The basic Unix philosophy is write tools that do one thing well, then use scripting to sequence the execution of the one-thing tools to accomplish bigger tasks. You could write a custom tool that did it all -- but you'd be duplicating a lot of work and you'd have to maintain it over time. Big PITA. I happen to be of the school that it's easier and simpler for this kind of preparation work to be done at the hypervisor level, and let the guest OS concentrate on identifying stuff it can use and managing the process of devices coming and going in a rational way. In this case, also, having swap is kind of necessary to getting Linux to run decently, and it's hard to do Linux stuff without a running Linux system, so creating SWAPGEN was a way to do the deed before you had a running Linux system to do it with. A second question is why didn't Novell provide a straightforward method for doing this and document it in a manual (without using a complex 3rd party EXEC) ? It sounds like the issue is more that it's a 3rd party tool than that it's done the way it's done. If either of the distributors wants to include SWAPGEN, we're open to discussing the idea. No one has asked. It would be nice if the documentation included the way to set up DIAG disk I/O, though. -- db David Boyes Sine Nomine Associates -- 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 -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to Merrill Lynch are references to any company in the Merrill Lynch Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Dasd_diag_mod question
If you put the VDISK in the CP directory entry and use the REUSE option, SWAPGEN will simply format what's there and write the signature on the disk. Well, NOW it will, with the change I just posted. Hmph. I'd fixed that while back, but guess I didn't commit the fix to the main repository. My bad, me. -- db -- 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
