Re: Application tools
Post, Mark K [EMAIL PROTECTED] wrote: I'm curious (truly) as to why you would be installing Jetty instead of Tomcat or something along those lines. What advantages does Jetty have? Mark Post Mark... This is a little dated, but was covered on the peanut gallery: http://developers.slashdot.org/developers/02/08/19/2042235.shtml?tid=108 -- 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: VM to Linux
On Tuesday, 03/16/2004 at 08:27 GMT, Crispin Hugo [EMAIL PROTECTED] wrote: I know that I should not use REXEC etc but it's the only way I know to run a shell in Linux that needs parameters passed to it from our VM system. Well, let's not throw the baby out with the bath water, eh? Feel free to use REXEC where the network is secure from unauthorized prying eyes, such as when using a virtual network. All of the concerns about the r commands are based on the use of networks that can be monitored by anyone with port access, and where that monitoring cannot be detected. My question is REXEC worked fine till we move Linux to the DMZ of our filewall. It sits for 5 minutes before timing out with unable to open port 512 etc. In /VAR/LOG/MESSAGES I get message like connect b.macro4.intranet.com that's all. I find I have to have the IP address of the VM system in /etc/hosts to make REXEC work. When its in DMZ I have put IP address of DMZ interface. Does it have to have a name with it and must the name be correct or just the IP address. Can I do it with out using /etc/hosts ? I can't speak to the etc/hosts aspect, but realize also that *two* connections are active when using rexec: 1. The client connects to the server's port 512 2. The server connects back to an ephemeral port number on the client. The port number is given to the server using the connection established in step 1. This connection carries stderr output. A firewall is likely to block rexecd from connecting back to the the rexec client, unless the firewall is performing stateful inspection of the traffic and opening ports as needed. FTP has the same issue, but passive ftp provides the fix. There is no equivalent for rexec. Alan Altmark Sr. Software Engineer IBM z/VM Development -- 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: Format disk and mount FS : lost space
We have formated a mini disk of 285 Cylinders with : dasdfmt -b 4096 -n 0104 dev2:/mnt# less /proc/dasd/devices 0104(ECKD) at ( 94: 16) is dasde : active at blocksize: 4096, 51300 blocks, 200 MB Going over the numbers, the overhead from dasdfmt is startling. At 849,960 bytes a cylinder, your 285 cyls should yield 242,238,600 bytes. Yet formatted at 12 4k blocks per track, you only get 4096 * 51300 = 210,124,800. Right there, that's 13.26% out the window immediately. The CDL, partition, filesystem/journal overhead is really quite tiny in comparison. The larger the number of cyls for the device, the worse the ratio gets :(. From Neale Ferguson's SCSI on Linux for zSeries presentation, it looks like he doesn't have to worry about this :). ~ Daniel --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you. -- 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: Format disk and mount FS : lost space
I know this has been discussed, but what was the final outcome. Should we use EXT2 or EXT3 block size 1024 or 4096 for space allocation on zlinux I am getting ready to start a POC on a z-800 IFL and it looks like I am throwing DASD at the LINUX images. We are also looking at LVM as a way to get larger File system space and share those volumes across several Linux ID's under z/VM, as opposed to NFS Any suggestions Larry Davis -Original Message- From: Daniel Jarboe [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 17, 2004 09:40 AM To: [EMAIL PROTECTED] Subject: Re: Format disk and mount FS : lost space We have formated a mini disk of 285 Cylinders with : dasdfmt -b 4096 -n 0104 dev2:/mnt# less /proc/dasd/devices 0104(ECKD) at ( 94: 16) is dasde : active at blocksize: 4096, 51300 blocks, 200 MB Going over the numbers, the overhead from dasdfmt is startling. At 849,960 bytes a cylinder, your 285 cyls should yield 242,238,600 bytes. Yet formatted at 12 4k blocks per track, you only get 4096 * 51300 = 210,124,800. Right there, that's 13.26% out the window immediately. The CDL, partition, filesystem/journal overhead is really quite tiny in comparison. The larger the number of cyls for the device, the worse the ratio gets :(. From Neale Ferguson's SCSI on Linux for zSeries presentation, it looks like he doesn't have to worry about this :). ~ Daniel --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you. -- 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: Format disk and mount FS : lost space
On Wed, 2004-03-17 at 08:54, Davis, Larry wrote: I know this has been discussed, but what was the final outcome. Should we use EXT2 or EXT3 block size 1024 or 4096 for space allocation on zlinux Depends. 1K blocks will be slower but less wasteful of space if you have lots of files smaller than 4K. I am getting ready to start a POC on a z-800 IFL and it looks like I am throwing DASD at the LINUX images. Does your z800 have the right microcode and the right FICON to do zSCSI? We are also looking at LVM as a way to get larger File system space and share those volumes across several Linux ID's under z/VM, as opposed to NFS Any suggestions LVM works fine. It's not especially fast, but it does the trick well enough. Still, in the long haul, for a zBox needing big DASD, consider SCSI. 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: /var/www
On Wed, Mar 17, 2004 at 12:31:07AM -0500, Post, Mark K wrote: The proper directory to look in would be defined in your httpd.conf file as the DocumentRoot. These days, Apache tends to get shipped with files like these in the DocumentRoot: index.html.en index.html.it index.html.se But no just plain index.html file. I would imagine which one gets displayed would depend on the value of the locale environment variable when Apache gets started. Close. Actually, the file displayed is based on the language sent by the client's browser. -Jere Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Fulton, Aaron Sent: Tuesday, March 16, 2004 5:15 PM To: [EMAIL PROTECTED] Subject: /var/www I can't seem to find the file that contains the initial web page when I start httpd and enter my IP address into my web browser's address bar. I've looked through all of the /var/www subdirectories to no avail. Regardless to what I change all I get is the default test page. Where else should I look? -- 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 ---end quoted text--- -- - | Jere Julian, RHCE, CCNA Cisco Systems, Inc. ITD - IBM Sustaining | | mailto:[EMAIL PROTECTED] 7025 Kit Creek Rd, RTP, NC 27709 | - -- 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 pgp0.pgp Description: PGP signature
Re: Format disk and mount FS : lost space
I have all the pieces for FCP other than an ESS 2105 box configured for SCSI disk we also have a Storagetek V2X2 box, but it has no FICON at this point. We are also going to evaluate an EMC DMX box for doing file sharing between z/OS and Solaris/Linux platforms. At this point I will place a caveat in our POC to discuss future enhancements, such as FCP and SCSI drives. A new and changing world ahead us. Thanks Larry -Original Message- From: Adam Thornton [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 17, 2004 10:19 AM To: [EMAIL PROTECTED] Subject: Re: Format disk and mount FS : lost space On Wed, 2004-03-17 at 08:54, Davis, Larry wrote: I know this has been discussed, but what was the final outcome. Should we use EXT2 or EXT3 block size 1024 or 4096 for space allocation on zlinux Depends. 1K blocks will be slower but less wasteful of space if you have lots of files smaller than 4K. I am getting ready to start a POC on a z-800 IFL and it looks like I am throwing DASD at the LINUX images. Does your z800 have the right microcode and the right FICON to do zSCSI? We are also looking at LVM as a way to get larger File system space and share those volumes across several Linux ID's under z/VM, as opposed to NFS Any suggestions LVM works fine. It's not especially fast, but it does the trick well enough. Still, in the long haul, for a zBox needing big DASD, consider SCSI. 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
Let Linux use Cyl 0?
Should I be letting Linux instances, under z/VM, utilize Cylinder 0? Currently I allocate Cylinder 0 to $ALLOC$ and the rest of the volume to the Linux image. I CPFMTXA cylinder 0 in VM and give it a VOLSER. Then, I access the devices under Linux and dasdfmt them, and partition them using fdasd. Until I get FCP and an ESS setup to allocate larger volumes, I will be using LVM for the larger file systems. I am planning to take full volumes of 3390-3 DASD and create Logical volume groups from them. I can split the devices between 4 FICON channels and 2 Controllers. Any recommendations? TIA,\|/ (. .) ooO-(_)-Ooo Larry Davis, 6-2380 -- 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: Format disk and mount FS : lost space
Adam wrote: Depends. 1K blocks will be slower but less wasteful of space if you have lots of files smaller than 4K. For SCSI devices, I would agree with you. For eckd devices, the overhead on 1K blocks is tremendous so what you make up from small files is lost to eckd overhead. Also, for eckd devices, the transfer overhead of moving 1k blocks is greater than the moving 4k blocks. I would suggest that, as long as you have eckd devices, 4k is better than 1k formatted devices. = Jim Sibley RHCT, Implementor of Linux on zSeries Computer are useless.They can only give answers. Pablo Picasso __ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com -- 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: Let Linux use Cyl 0?
I do not think you should let anything other than VM itself use cyl 0. As this is where VM keeps Vol id, disk map info, etc. $ALLOC$ is what is some times called a place holder. The userid $ALLOC$ doesn't actually do anything with it other than mark it or inform others that this cylinder is occupied. I also set up a $EOV$ on each volume on the last cylinder to help with keeping track of gaps that DISKMAP will show. Steve Gentry Davis, Larry [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 03/17/2004 11:50 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Let Linux use Cyl 0? Should I be letting Linux instances, under z/VM, utilize Cylinder 0? Currently I allocate Cylinder 0 to $ALLOC$ and the rest of the volume to the Linux image. I CPFMTXA cylinder 0 in VM and give it a VOLSER. Then, I access the devices under Linux and dasdfmt them, and partition them using fdasd. Until I get FCP and an ESS setup to allocate larger volumes, I will be using LVM for the larger file systems. I am planning to take full volumes of 3390-3 DASD and create Logical volume groups from them. I can split the devices between 4 FICON channels and 2 Controllers. Any recommendations? TIA,\|/ (. .) ooO-(_)-Ooo Larry Davis, 6-2380 -- 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
full /var after online updates
after applying online updates to a new install of sles8, my /var went from 50% to 98% used. can someone tell me where this usage is and can it be cleaned up? -- 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: full /var after online updates
I would look in /var/lib/YaST2/you/i386/update/SuSE-SLES/8/rpm/ Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scorch Burnet Sent: Wednesday, March 17, 2004 1:20 PM To: [EMAIL PROTECTED] Subject: full /var after online updates after applying online updates to a new install of sles8, my /var went from 50% to 98% used. can someone tell me where this usage is and can it be cleaned up? -- 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
dasd_diag_mod missing in SLES8 64bit
I recently completed an install of SLES8 64 bit and I was disappointed to find that the recent SUSE kernel rpms do not include dasd_diag_mod.o. The last s390x kernel rpm to include it was k_deflt-2.4.19-71, although it is still present in 31 bit SLES8. I'm sure that it's removal was probably the result of a problem and not an oversight, but does anyone know what those problems might have been and when (if?) the module will return? Michael Lambert -- 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: full /var after online updates
You might also have a look at /var/adm/backup/rpmdb -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Post, Mark K Sent: Wednesday, March 17, 2004 1:24 PM To: [EMAIL PROTECTED] Subject: Re: [LINUX-390] full /var after online updates I would look in /var/lib/YaST2/you/i386/update/SuSE-SLES/8/rpm/ Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scorch Burnet Sent: Wednesday, March 17, 2004 1:20 PM To: [EMAIL PROTECTED] Subject: full /var after online updates after applying online updates to a new install of sles8, my /var went from 50% to 98% used. can someone tell me where this usage is and can it be cleaned up? -- 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 == If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ == -- 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: full /var after online updates
thanks Mark and Ken lots of resources used here, can these be cleaned up or is it necessary to keep these files around? Post, Mark K wrote: I would look in /var/lib/YaST2/you/i386/update/SuSE-SLES/8/rpm/ Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scorch Burnet Sent: Wednesday, March 17, 2004 1:20 PM To: [EMAIL PROTECTED] Subject: full /var after online updates after applying online updates to a new install of sles8, my /var went from 50% to 98% used. can someone tell me where this usage is and can it be cleaned up? -- 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
VDISK for /tmp
/tmp is supposedly a throw away file system, can Linux set this up in a memory file system like it does /proc and could/should I use VDisk for /tmp also? TIA,\|/ (. .) ooO-(_)-Ooo Larry Davis, 6-2380 -- 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 for /tmp
You can do that. We're experimenting with using T-disk (real disk) for /tmp. Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light. - Alexander Pope It did not last; the Devil howling 'Ho! Let Einstein Be!' restored the status quo.- John Collings Squire God Rolled his dice, to Einstein's great dismay: 'Let Feynman Be!' and all was clear as day. - Jagdish Mehra Gordon W. Wolfe, Ph. D. VM Technical Services, The Boeing Company -- From: Davis, Larry Reply To: Linux on 390 Port Sent: Wednesday, March 17, 2004 10:27 AM To: [EMAIL PROTECTED] Subject: VDISK for /tmp /tmp is supposedly a throw away file system, can Linux set this up in a memory file system like it does /proc and could/should I use VDisk for /tmp also? TIA,\|/ (. .) ooO-(_)-Ooo Larry Davis, 6-2380 -- 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: full /var after online updates
or /var/lib/rpm Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light. - Alexander Pope It did not last; the Devil howling 'Ho! Let Einstein Be!' restored the status quo.- John Collings Squire God Rolled his dice, to Einstein's great dismay: 'Let Feynman Be!' and all was clear as day. - Jagdish Mehra Gordon W. Wolfe, Ph. D. VM Technical Services, The Boeing Company -- From: Post, Mark K Reply To: Linux on 390 Port Sent: Wednesday, March 17, 2004 10:24 AM To: [EMAIL PROTECTED] Subject: Re: full /var after online updates I would look in /var/lib/YaST2/you/i386/update/SuSE-SLES/8/rpm/ Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scorch Burnet Sent: Wednesday, March 17, 2004 1:20 PM To: [EMAIL PROTECTED] Subject: full /var after online updates after applying online updates to a new install of sles8, my /var went from 50% to 98% used. can someone tell me where this usage is and can it be cleaned up? -- 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: Let Linux use Cyl 0?
I depends on how you've got it set up and what controls you have in place. If you're using VM as a hypervisor for Linux, VM has to be able to know what the volser of the DASD is. If your linux instances have root authority not controlled by you and they take it in mind to do a dasdfmt on a full-pack disk, including cylinder 0, and change the volser in doing so, then the next time VM is IPLed, that pack might not be found and the linux instance won't come up because the directory won't match the volser. Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light. - Alexander Pope It did not last; the Devil howling 'Ho! Let Einstein Be!' restored the status quo.- John Collings Squire God Rolled his dice, to Einstein's great dismay: 'Let Feynman Be!' and all was clear as day. - Jagdish Mehra Gordon W. Wolfe, Ph. D. VM Technical Services, The Boeing Company -- From: Steve Gentry Reply To: Linux on 390 Port Sent: Wednesday, March 17, 2004 10:13 AM To: [EMAIL PROTECTED] Subject: Re: Let Linux use Cyl 0? I do not think you should let anything other than VM itself use cyl 0. As this is where VM keeps Vol id, disk map info, etc. $ALLOC$ is what is some times called a place holder. The userid $ALLOC$ doesn't actually do anything with it other than mark it or inform others that this cylinder is occupied. I also set up a $EOV$ on each volume on the last cylinder to help with keeping track of gaps that DISKMAP will show. Steve Gentry Davis, Larry [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 03/17/2004 11:50 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Let Linux use Cyl 0? Should I be letting Linux instances, under z/VM, utilize Cylinder 0? Currently I allocate Cylinder 0 to $ALLOC$ and the rest of the volume to the Linux image. I CPFMTXA cylinder 0 in VM and give it a VOLSER. Then, I access the devices under Linux and dasdfmt them, and partition them using fdasd. Until I get FCP and an ESS setup to allocate larger volumes, I will be using LVM for the larger file systems. I am planning to take full volumes of 3390-3 DASD and create Logical volume groups from them. I can split the devices between 4 FICON channels and 2 Controllers. Any recommendations? TIA,\|/ (. .) ooO-(_)-Ooo Larry Davis, 6-2380 -- 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: full /var after online updates
I would not erase the rpm database backups. If you don't think you'll be needing to re-install any of those RPMs again, then you can delete the files from the YOU directories. If you decide you want to re-install them again, YOU will re-download them again using wget, just as it did the first time. Another option would be to copy them off to another system (if you have one), in case you want to update more than one system off the now-local copies of the packages. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scorch Burnet Sent: Wednesday, March 17, 2004 1:46 PM To: [EMAIL PROTECTED] Subject: Re: full /var after online updates thanks Mark and Ken lots of resources used here, can these be cleaned up or is it necessary to keep these files around? Post, Mark K wrote: I would look in /var/lib/YaST2/you/i386/update/SuSE-SLES/8/rpm/ Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scorch Burnet Sent: Wednesday, March 17, 2004 1:20 PM To: [EMAIL PROTECTED] Subject: full /var after online updates after applying online updates to a new install of sles8, my /var went from 50% to 98% used. can someone tell me where this usage is and can it be cleaned up? -- 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: Let Linux use Cyl 0?
On Wednesday, 03/17/2004 at 11:50 EST, Davis, Larry [EMAIL PROTECTED] wrote: Should I be letting Linux instances, under z/VM, utilize Cylinder 0? I would recommend never allowing any guest to write on cyl 0. If the guest writes a label that matches the label of any of your CP_OWNED packs, you could be in for a big surprise the next time you IPL. The one exception is if the persons doing the labelling are following the same procedures you do for choosing volume labels. Problems can be reduced by having hourly/daily checks of the volume labels to ensure no overlap. You have to actually read the volser; you can't use QUERY DASD or QUERY rdev because CP caches the volser when the device comes online. USER volumes are easily dealt with by simply ATTACHing to SYSTEM in AUTOLOG1 rather than having them in the USER_VOLUME list. But, then, I'm a Security Weasel, so I'm more paranoid than most... Alan Altmark Sr. Software Engineer IBM z/VM Development -- 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: Let Linux use Cyl 0?
Well, technically VM only cares if the volumes are attached to SYSTEM (uservol include in SYSTEM CONFIG). If you use DEDICATE to assign them to Linux guests, then VM shouldn't much care, unless one of your Linuxes decides to label them something like 440W01 or something then watch out for fun at next IPL time. Not that I would ever do it that way - I didn't even give cyl 0 to MVS when we ran that as guests. I would think the only reason you'd want to do it is if you have to at times run in an LPAR without VM. Marcy Cortes Wells Fargo Services Co -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Wolfe, Gordon W Sent: Wednesday, March 17, 2004 10:49 AM To: [EMAIL PROTECTED] Subject: Re: [LINUX-390] Let Linux use Cyl 0? I depends on how you've got it set up and what controls you have in place. If you're using VM as a hypervisor for Linux, VM has to be able to know what the volser of the DASD is. If your linux instances have root authority not controlled by you and they take it in mind to do a dasdfmt on a full-pack disk, including cylinder 0, and change the volser in doing so, then the next time VM is IPLed, that pack might not be found and the linux instance won't come up because the directory won't match the volser. Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light. - Alexander Pope It did not last; the Devil howling 'Ho! Let Einstein Be!' restored the status quo.- John Collings Squire God Rolled his dice, to Einstein's great dismay: 'Let Feynman Be!' and all was clear as day. - Jagdish Mehra Gordon W. Wolfe, Ph. D. VM Technical Services, The Boeing Company -- From: Steve Gentry Reply To: Linux on 390 Port Sent: Wednesday, March 17, 2004 10:13 AM To: [EMAIL PROTECTED] Subject: Re: Let Linux use Cyl 0? I do not think you should let anything other than VM itself use cyl 0. As this is where VM keeps Vol id, disk map info, etc. $ALLOC$ is what is some times called a place holder. The userid $ALLOC$ doesn't actually do anything with it other than mark it or inform others that this cylinder is occupied. I also set up a $EOV$ on each volume on the last cylinder to help with keeping track of gaps that DISKMAP will show. Steve Gentry Davis, Larry [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 03/17/2004 11:50 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Let Linux use Cyl 0? Should I be letting Linux instances, under z/VM, utilize Cylinder 0? Currently I allocate Cylinder 0 to $ALLOC$ and the rest of the volume to the Linux image. I CPFMTXA cylinder 0 in VM and give it a VOLSER. Then, I access the devices under Linux and dasdfmt them, and partition them using fdasd. Until I get FCP and an ESS setup to allocate larger volumes, I will be using LVM for the larger file systems. I am planning to take full volumes of 3390-3 DASD and create Logical volume groups from them. I can split the devices between 4 FICON channels and 2 Controllers. Any recommendations? TIA,\|/ (. .) ooO-(_)-Ooo Larry Davis, 6-2380 -- 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 for /tmp
On Wed, 2004-03-17 at 12:27, Davis, Larry wrote: /tmp is supposedly a throw away file system, can Linux set this up in a memory file system like it does /proc and could/should I use VDisk for /tmp also? Not quite like /proc. You could use VDISK, although you'd have to format and mount it as the system came up. You could also use an EW DCSS, if you wanted. I just leave mine as regular DASD, though. Although I have done it LVM-multipathed before, for speed. 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: WebLogic 7.0 SP5 (Platform) for Linux for S/390 and zSeries is Now GA
Hi, Has anyone else installed this product, and if so, did it run OK? One of our developers said he installed this today, and they said it used a huge amount of our VM cpu. I need to check with the developer to see which version he installed, but the development team is now concerned that z/VM is not the place to run linux. If they were just running the server side of the product, and they only have 2 or 3 clients connecting, then I would think the CPU usage should have been low. Any tunning hints? Thanks, Ken Vance Amadeus -- 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: WebLogic 7.0 SP5 (Platform) for Linux for S/390 a nd zSeries is Now GA
Where are they getting the high CPU numbers from ? Anything from inside the instance is a lie. They'd have to be on VM and looking at rtm or esamon or something to see real numbers. Marcy Cortes -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ken Vance Sent: Wednesday, March 17, 2004 12:16 PM To: [EMAIL PROTECTED] Subject: Re: [LINUX-390] WebLogic 7.0 SP5 (Platform) for Linux for S/390 and zSeries is Now GA Hi, Has anyone else installed this product, and if so, did it run OK? One of our developers said he installed this today, and they said it used a huge amount of our VM cpu. I need to check with the developer to see which version he installed, but the development team is now concerned that z/VM is not the place to run linux. If they were just running the server side of the product, and they only have 2 or 3 clients connecting, then I would think the CPU usage should have been low. Any tunning hints? Thanks, Ken Vance Amadeus -- 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
More on: Let Linux use Cyl 0?
Let's suppose I was stupid enough in the beginning to just ATTACH a pack to the VM guest, install Linux and dasdfmt the entire pack. Then, I didn't use the -label on dasdfmt and ended up with a funky VOLSER like: q 127 DASD 0127 ATTACHED TO DARWIN 0200 R/W LNX1 x Ready; T=0.01/0.01 14:18:41 Can I still use ICKDSF: CPFORMAT LABEL UNIT(127) NVFY VOLID(LNX200) to recify it without harming the contents of the IPL volume? Dave -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Alan Altmark Sent: Wednesday, March 17, 2004 1:30 PM To: [EMAIL PROTECTED] Subject: Re: Let Linux use Cyl 0? On Wednesday, 03/17/2004 at 11:50 EST, Davis, Larry [EMAIL PROTECTED] wrote: Should I be letting Linux instances, under z/VM, utilize Cylinder 0? I would recommend never allowing any guest to write on cyl 0. If the guest writes a label that matches the label of any of your CP_OWNED packs, you could be in for a big surprise the next time you IPL. The one exception is if the persons doing the labelling are following the same procedures you do for choosing volume labels. ... Alan Altmark Sr. Software Engineer IBM z/VM Development -- 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
Problems with CUPS/SAMBA config (print drivers)
I am following Michael MacIsaac's Print Serving Solutions Using Samba CUPs presentation and have some config problems that I don't understand: 1. I ran the cupsaddsmb command and I see that it created InfoPrint_1125.PPD, which looks right for my Infoprint 1125 printer. Not sure why we're using W32X86 (how does that relate?) Problem:When I go to add the printer to my W2K client (and download the driver)... I get The server on which the 'Infoprint_1125' printer resides does not have the correct printer driver installed, if you want to install the driver on your local computer, click OK Then OK Then Type the file where the file is located and it's looking for an .INF file...not a *.PPD ??? When I added the CUPS printer with the lpadmin command I did not know which *.ppd.gz to use, so I just picked the Infoprint_12-gimp-print.ppd.gz maybe that is related to my problem? Any help would be appreciated. I am at Samba samba-2.2.8a-108 on SLES8 SP3 2. Also the UPLOAD procedure did not work for me..that is why I used cupsaddsmb. On the foid where is reads There should be no driver that was true...but the New Driver button was grayed out and unselectable. TIA, Dave Myers Denver Solutions Group Senior Systems Engineer Office Phone: (303) 996-7112 Cellular Phone: (303) 619-0782 Home Office: (303) 948-0027 Fax: (303) 706.1713 e-mail: [EMAIL PROTECTED] -- 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: SLES8 trap signal shutdown
For those of us playing along at home and trying to get this work, is there a short list of mistakes one might make (or contraindications one might overlook) in this context? Q SIGNALS on my VM system confirms that my Linux image is waiting for a shutdown signal. The first time I edited /etc/inittab to add this, I reversed two letters in ctrlaltdel and got an error message when I next did an init 6, so I know I'm in the right file, and since the error message went away, I presume I'm spelling it correctly now. :-) But when I actually do the SIGNAL SHUTDOWN USER WITHIN 90, it just waits 90 seconds and then logs itself off, without doing the /sbin/shutdown -h now specified. I know it didn't do the shutdown because when it comes back up, it takes forever doing the fsck For what do I look next? Thanks, Nick Rich Smrcina wrote: In /etc/inittab: # what to do when CTRL-ALT-DEL is pressed ca::ctrlaltdel:/sbin/shutdown -h now On Tue, 2004-02-24 at 08:48, Eric Sammons wrote: What should the ctrlaltdel line look like? If it is required... Thanks! Eric Sammons -- Rich Smrcina Sr. Systems Engineer DSG eServer Linux Solutions Milwaukee, WI rsmrcina at wi.rr.com rsmrcina at dsgroup.com -- 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: Let Linux use Cyl 0?
There is another consideration that makes allocating of Linux volume to a full-pack mini or letting it use cylinder zero very undesirable. If you regularly run FDR backups from MVS to dump the shared DASD volumes to tape, as part of your backup procedures, your backup will fail for full-pack Linux volumes. FDR chokes on the corrupted VTOC data that it sees in cylinder zero. There is a work-around for that problem that I don't think is worth dwelling on, but if someone needs that solution I'd be happy to post it. Simon Kharnas Technical Support Consultant TIAA/CREF -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Marcy Cortes Sent: Wednesday, March 17, 2004 2:38 PM To: [EMAIL PROTECTED] Subject: Re: Let Linux use Cyl 0? Well, technically VM only cares if the volumes are attached to SYSTEM (uservol include in SYSTEM CONFIG). If you use DEDICATE to assign them to Linux guests, then VM shouldn't much care, unless one of your Linuxes decides to label them something like 440W01 or something then watch out for fun at next IPL time. Not that I would ever do it that way - I didn't even give cyl 0 to MVS when we ran that as guests. I would think the only reason you'd want to do it is if you have to at times run in an LPAR without VM. Marcy Cortes Wells Fargo Services Co -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Wolfe, Gordon W Sent: Wednesday, March 17, 2004 10:49 AM To: [EMAIL PROTECTED] Subject: Re: [LINUX-390] Let Linux use Cyl 0? I depends on how you've got it set up and what controls you have in place. If you're using VM as a hypervisor for Linux, VM has to be able to know what the volser of the DASD is. If your linux instances have root authority not controlled by you and they take it in mind to do a dasdfmt on a full-pack disk, including cylinder 0, and change the volser in doing so, then the next time VM is IPLed, that pack might not be found and the linux instance won't come up because the directory won't match the volser. Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light. - Alexander Pope It did not last; the Devil howling 'Ho! Let Einstein Be!' restored the status quo.- John Collings Squire God Rolled his dice, to Einstein's great dismay: 'Let Feynman Be!' and all was clear as day. - Jagdish Mehra Gordon W. Wolfe, Ph. D. VM Technical Services, The Boeing Company -- From: Steve Gentry Reply To: Linux on 390 Port Sent: Wednesday, March 17, 2004 10:13 AM To: [EMAIL PROTECTED] Subject: Re: Let Linux use Cyl 0? I do not think you should let anything other than VM itself use cyl 0. As this is where VM keeps Vol id, disk map info, etc. $ALLOC$ is what is some times called a place holder. The userid $ALLOC$ doesn't actually do anything with it other than mark it or inform others that this cylinder is occupied. I also set up a $EOV$ on each volume on the last cylinder to help with keeping track of gaps that DISKMAP will show. Steve Gentry Davis, Larry [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 03/17/2004 11:50 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Let Linux use Cyl 0? Should I be letting Linux instances, under z/VM, utilize Cylinder 0? Currently I allocate Cylinder 0 to $ALLOC$ and the rest of the volume to the Linux image. I CPFMTXA cylinder 0 in VM and give it a VOLSER. Then, I access the devices under Linux and dasdfmt them, and partition them using fdasd. Until I get FCP and an ESS setup to allocate larger volumes, I will be using LVM for the larger file systems. I am planning to take full volumes of 3390-3 DASD and create Logical volume groups from them. I can split the devices between 4 FICON channels and 2 Controllers. Any recommendations? TIA,\|/ (. .) ooO-(_)-Ooo Larry Davis, 6-2380 -- 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
Re: Problems with CUPS/SAMBA config (print drivers)
Hi Dave, 1. I ran the cupsaddsmb command and I see that it created InfoPrint_1125.PPD, which looks right for my Infoprint 1125 printer. What's in /var/lib/samba/drivers/, /var/lib/samba/drivers/W32X86/, and /var/lib/samba/drivers/W32X86/2 or /var/lib/samba/drivers/W32X86/3? Not sure why we're using W32X86 (how does that relate?) Drivers for windows 95 and higher clients on x86. Problem:When I go to add the printer to my W2K client (and download the driver)... I get The server on which the 'Infoprint_1125' printer resides does not have the correct printer driver installed, if you want to install the driver on your local computer, click OK Then OK Here you should click No or Cancel or whatever the other option is, not OK. Clicking OK would try to install the driver locally instead of on the server. Then Type the file where the file is located and it's looking for an .INF file...not a *.PPD ??? .inf is to install the windows client driver locally. When I added the CUPS printer with the lpadmin command I did not know which *.ppd.gz to use, so I just picked the Infoprint_12-gimp-print.ppd.gz maybe that is related to my problem? You probably don't want to use the gimp drivers, but whatever you select there will not affect your windows clients which would be printing in RAW. This might affect things like the banner/cover page though, and print jobs initiated from linux. 2. Also the UPLOAD procedure did not work for me..that is why I used cupsaddsmb. On the foid where is reads There should be no driver that was true...but the New Driver button was grayed out and unselectable. Is the user you are connecting to samba with configured as a printer admin in /etc/samba/smb.conf? TIA, Good luck, ~ Daniel --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you. -- 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: More on: Let Linux use Cyl 0?
On Wed, 2004-03-17 at 21:18, David Booher wrote: Can I still use ICKDSF: CPFORMAT LABEL UNIT(127) NVFY VOLID(LNX200) to recify it without harming the contents of the IPL volume? Nope. Linux also sticks the volser in the DCB's that it puts on disk. You better use Linux' fdasd to change the volser if this would ever happen to you. You could even run the ramdisk system to do that. But from what you show it would seem that you don't have a CDL format disk but a LDL (where Linux uses LNX1 rather than VOL1 as key in R3). If that's the case then fdasd will complain in that style, and I think you would be better of copying the data (file level) to a new disk. Rob PS I think you can even do this being less stupid. From what I recall fdasd was overwriting the volser with its own 0X even when you set one with dasdfmt. -- 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: SLES8 trap signal shutdown
After changing /etc/inittab, mine wouldn't work the first time either. After the reboot it seemed to be OK. Rich Smrcina - Original Message - From: Nick Laflamme [EMAIL PROTECTED] Date: Wednesday, March 17, 2004 4:04 pm Subject: Re: SLES8 trap signal shutdown For those of us playing along at home and trying to get this work, is there a short list of mistakes one might make (or contraindications one might overlook) in this context? Q SIGNALS on my VM system confirms that my Linux image is waiting for a shutdown signal. The first time I edited /etc/inittab to add this, I reversed two lettersin ctrlaltdel and got an error message when I next did an init 6, so I know I'm in the right file, and since the error message went away, I presume I'm spelling it correctly now. :-) But when I actually do the SIGNAL SHUTDOWN USER WITHIN 90, it justwaits 90 seconds and then logs itself off, without doing the /sbin/shutdown -h now specified. I know it didn't do the shutdown because when it comes back up, it takes forever doing the fsck For what do I look next? Thanks, Nick Rich Smrcina wrote: In /etc/inittab: # what to do when CTRL-ALT-DEL is pressed ca::ctrlaltdel:/sbin/shutdown -h now On Tue, 2004-02-24 at 08:48, Eric Sammons wrote: What should the ctrlaltdel line look like? If it is required... Thanks! Eric Sammons -- Rich Smrcina Sr. Systems Engineer DSG eServer Linux Solutions Milwaukee, WI rsmrcina at wi.rr.com rsmrcina at dsgroup.com --- --- 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 for /tmp
The following technique seems to work for us, with SLES8. - In /etc/fstab: /dev/dasdb1 /tmp ext2 defaults 0 0 - In boot.local: # Create and mount the disk space used for /tmp mke2fs /dev/dasdb1 mount /dev/dasdb1 /tmp chmod o=t /tmp chmod a+rwx /tmp - Be sure that you have FBA support in your system. If not do this once: insmod dasd_fba_mod mkinitrd zipl Hope this helps! -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Davis, Larry Sent: Wednesday, March 17, 2004 1:28 PM To: [EMAIL PROTECTED] Subject: VDISK for /tmp /tmp is supposedly a throw away file system, can Linux set this up in a memory file system like it does /proc and could/should I use VDisk for /tmp also? TIA,\|/ (. .) ooO-(_)-Ooo Larry Davis, 6-2380 -- 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: SLES8 trap signal shutdown
You need to do telinit q to force rereading of inittab. My inittab has a slightly different line: ca:12345:ctrlaltdel:/sbin/shutdown -y -g0 I've tested this extensively, and it works for me. You should get messages on the console when the signal is received, even if the script isn't triggered. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Rich Smrcina Sent: Wednesday, March 17, 2004 4:21 PM To: [EMAIL PROTECTED] Subject: Re: [LINUX-390] SLES8 trap signal shutdown After changing /etc/inittab, mine wouldn't work the first time either. After the reboot it seemed to be OK. Rich Smrcina - Original Message - From: Nick Laflamme [EMAIL PROTECTED] Date: Wednesday, March 17, 2004 4:04 pm Subject: Re: SLES8 trap signal shutdown For those of us playing along at home and trying to get this work, is there a short list of mistakes one might make (or contraindications one might overlook) in this context? Q SIGNALS on my VM system confirms that my Linux image is waiting for a shutdown signal. The first time I edited /etc/inittab to add this, I reversed two lettersin ctrlaltdel and got an error message when I next did an init 6, so I know I'm in the right file, and since the error message went away, I presume I'm spelling it correctly now. :-) But when I actually do the SIGNAL SHUTDOWN USER WITHIN 90, it justwaits 90 seconds and then logs itself off, without doing the /sbin/shutdown -h now specified. I know it didn't do the shutdown because when it comes back up, it takes forever doing the fsck For what do I look next? Thanks, Nick Rich Smrcina wrote: In /etc/inittab: # what to do when CTRL-ALT-DEL is pressed ca::ctrlaltdel:/sbin/shutdown -h now On Tue, 2004-02-24 at 08:48, Eric Sammons wrote: What should the ctrlaltdel line look like? If it is required... Thanks! Eric Sammons -- Rich Smrcina Sr. Systems Engineer DSG eServer Linux Solutions Milwaukee, WI rsmrcina at wi.rr.com rsmrcina at dsgroup.com --- --- 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 == If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ == -- 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: SLES8 trap signal shutdown
On Wed, 2004-03-17 at 22:04, Nick Laflamme wrote: The first time I edited /etc/inittab to add this, I reversed two letters in ctrlaltdel and got an error message when I next did an init 6, so I know I'm in the right file, and since the error message went away, I presume I'm spelling it correctly now. :-) The init 6 takes another part of the inittab. Yours now it looks like this? ca::ctrlaltdel:/sbin/shutdown -r -t 4 now I would have thought I had -h in, but this seems to work... -- 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: SLES8 trap signal shutdown
In order to ask /sbin/init to re-read /etc/inittab, you can issue the command: kill -1 1 The -1 argument sends a kill signal which causes the process to reload its config. The 1 is the process id. init always has process id 1, as it is the first process loaded by the kernel. You don't really have to reboot. -- Thomas Cameron, RHCE, CNE, MCSE, MCT Assistant Vice President Linux Design and Engineering Bank of America (972) 997-9641 The opinions expressed in this message are mine alone and do not necessarily reflect the opinions of my employer, Bank of America. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Rich Smrcina Sent: Wednesday, March 17, 2004 3:21 PM To: [EMAIL PROTECTED] Subject: Re: SLES8 trap signal shutdown After changing /etc/inittab, mine wouldn't work the first time either. After the reboot it seemed to be OK. Rich Smrcina - Original Message - From: Nick Laflamme [EMAIL PROTECTED] Date: Wednesday, March 17, 2004 4:04 pm Subject: Re: SLES8 trap signal shutdown For those of us playing along at home and trying to get this work, is there a short list of mistakes one might make (or contraindications one might overlook) in this context? Q SIGNALS on my VM system confirms that my Linux image is waiting for a shutdown signal. The first time I edited /etc/inittab to add this, I reversed two lettersin ctrlaltdel and got an error message when I next did an init 6, so I know I'm in the right file, and since the error message went away, I presume I'm spelling it correctly now. :-) But when I actually do the SIGNAL SHUTDOWN USER WITHIN 90, it justwaits 90 seconds and then logs itself off, without doing the /sbin/shutdown -h now specified. I know it didn't do the shutdown because when it comes back up, it takes forever doing the fsck For what do I look next? Thanks, Nick Rich Smrcina wrote: In /etc/inittab: # what to do when CTRL-ALT-DEL is pressed ca::ctrlaltdel:/sbin/shutdown -h now On Tue, 2004-02-24 at 08:48, Eric Sammons wrote: What should the ctrlaltdel line look like? If it is required... Thanks! Eric Sammons -- Rich Smrcina Sr. Systems Engineer DSG eServer Linux Solutions Milwaukee, WI rsmrcina at wi.rr.com rsmrcina at dsgroup.com --- --- 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 for /tmp
On Wed, 2004-03-17 at 22:23, Scully, William P wrote: The following technique seems to work for us, with SLES8. - In /etc/fstab: /dev/dasdb1 /tmp ext2 defaults 0 0 - In boot.local: # Create and mount the disk space used for /tmp mke2fs /dev/dasdb1 mount /dev/dasdb1 /tmp chmod o=t /tmp chmod a+rwx /tmp So apparently you can get away with /tmp come in that late (or maybe things are writing on your root device until your mount the device). But this does not mean it is always wise to do. I don't know enough about Linux to tell whether it is important to have high bandwidth to /tmp. My systems seem to have the ssh-* subdirectories with the sockets to my ssh-agent forwarding (these live in inode cache anyway afaik) and some stuff that YaST left there, and I think also rpm builds go there. You would need to define the VDISK for peak requirements in /tmp. If Linux is continuously writing things into /tmp and deleting them, over time you will touch all pages in your VDISK and make it very unpleasant for CP to back that up with paging space. I even think an EW DCSS may not be the best thing to do (for the same reasons) because pages are copied back and forth between DCSS and Linux main memory you are wasting z/VM real memory. Let me phrase it differently: when you use VDISK for swap then some process data is active either in main memory or on VDISK, but not both. When you hold real data in VDISK, much of it will be active both on VIDSK and in page cache. This doubles your memory requirements for it. How about using ramfs for it? Is that going to hurt you? mount -t ramfs ramfs /tmp I believe that ramfs could even be swapped by Linux (to VDISK), but thinking about that makes my head hurt... 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
Re: SLES8 trap signal shutdown
On Wed, 2004-03-17 at 22:31, Cameron, Thomas wrote: In order to ask /sbin/init to re-read /etc/inittab, you can issue the command: kill -1 1 Great! Until Rich mentioned it, I never had realized init would need to re-read the /etc/inittab to make this work... 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
Re: Let Linux use Cyl 0?
If you're using CDL formatted volumes, this should not be the case. If you are, and it is happening anyway, you should report a problem to IBM and FDR. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Kharnas, Simon Sent: Wednesday, March 17, 2004 4:12 PM To: [EMAIL PROTECTED] Subject: Re: Let Linux use Cyl 0? There is another consideration that makes allocating of Linux volume to a full-pack mini or letting it use cylinder zero very undesirable. If you regularly run FDR backups from MVS to dump the shared DASD volumes to tape, as part of your backup procedures, your backup will fail for full-pack Linux volumes. FDR chokes on the corrupted VTOC data that it sees in cylinder zero. There is a work-around for that problem that I don't think is worth dwelling on, but if someone needs that solution I'd be happy to post it. Simon Kharnas Technical Support Consultant TIAA/CREF -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Marcy Cortes Sent: Wednesday, March 17, 2004 2:38 PM To: [EMAIL PROTECTED] Subject: Re: Let Linux use Cyl 0? Well, technically VM only cares if the volumes are attached to SYSTEM (uservol include in SYSTEM CONFIG). If you use DEDICATE to assign them to Linux guests, then VM shouldn't much care, unless one of your Linuxes decides to label them something like 440W01 or something then watch out for fun at next IPL time. Not that I would ever do it that way - I didn't even give cyl 0 to MVS when we ran that as guests. I would think the only reason you'd want to do it is if you have to at times run in an LPAR without VM. Marcy Cortes Wells Fargo Services Co -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Wolfe, Gordon W Sent: Wednesday, March 17, 2004 10:49 AM To: [EMAIL PROTECTED] Subject: Re: [LINUX-390] Let Linux use Cyl 0? I depends on how you've got it set up and what controls you have in place. If you're using VM as a hypervisor for Linux, VM has to be able to know what the volser of the DASD is. If your linux instances have root authority not controlled by you and they take it in mind to do a dasdfmt on a full-pack disk, including cylinder 0, and change the volser in doing so, then the next time VM is IPLed, that pack might not be found and the linux instance won't come up because the directory won't match the volser. Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light. - Alexander Pope It did not last; the Devil howling 'Ho! Let Einstein Be!' restored the status quo.- John Collings Squire God Rolled his dice, to Einstein's great dismay: 'Let Feynman Be!' and all was clear as day. - Jagdish Mehra Gordon W. Wolfe, Ph. D. VM Technical Services, The Boeing Company -- From: Steve Gentry Reply To: Linux on 390 Port Sent: Wednesday, March 17, 2004 10:13 AM To: [EMAIL PROTECTED] Subject: Re: Let Linux use Cyl 0? I do not think you should let anything other than VM itself use cyl 0. As this is where VM keeps Vol id, disk map info, etc. $ALLOC$ is what is some times called a place holder. The userid $ALLOC$ doesn't actually do anything with it other than mark it or inform others that this cylinder is occupied. I also set up a $EOV$ on each volume on the last cylinder to help with keeping track of gaps that DISKMAP will show. Steve Gentry Davis, Larry [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 03/17/2004 11:50 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Let Linux use Cyl 0? Should I be letting Linux instances, under z/VM, utilize Cylinder 0? Currently I allocate Cylinder 0 to $ALLOC$ and the rest of the volume to the Linux image. I CPFMTXA cylinder 0 in VM and give it a VOLSER. Then, I access the devices under Linux and dasdfmt them, and partition them using fdasd. Until I get FCP and an ESS setup to allocate larger volumes, I will be using LVM for the larger file systems. I am planning to take full volumes of 3390-3 DASD and create Logical volume groups from them. I can split the devices between 4 FICON channels and 2 Controllers. Any recommendations? TIA,\|/ (. .) ooO-(_)-Ooo Larry Davis, 6-2380 -- 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
Re: VDISK for /tmp
First, a small correction. The proc file system is not a memory file system in any way. It is an abstraction of kernel control blocks, presented as a file system to userland. Second, if you just want to make sure /tmp is empty after every reboot, put an entry in one of the startup scripts to clean it out. I can't see much benefit to trying to put it into a VDISK or TDISK. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Davis, Larry Sent: Wednesday, March 17, 2004 1:28 PM To: [EMAIL PROTECTED] Subject: VDISK for /tmp /tmp is supposedly a throw away file system, can Linux set this up in a memory file system like it does /proc and could/should I use VDisk for /tmp also? TIA,\|/ (. .) ooO-(_)-Ooo Larry Davis, 6-2380 -- 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
New Presentation on the Web Site
I've added a new presentation to the web site from SHARE 102. Harold Pritchett has contributed his Configuring BIND session. For those that don't know, BIND (Berkeley InterNet Daemon) is the software that provides DNS services for most of the Internet. The presentation is located at http://linuxvm.org/Present/ as usual. 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
