Question re: Linux SLES9
I have a problem with network communication. SLES9 for S/390 (64-bit) in an LPAR (no VM) using a shared IFL I have one other LPAR running SLES9 64-bit I ran uname -a which shows: Linux techlnux 2.6.5-7.201-s390x #1 SMP Thu Aug 25 06:20:45 UTC 2005 s390x s390x s390x GNU/Linux I ran netstat -rn and it returned nothing only the column headings. I tried to ping the IP address of my system and it responded. I also successfully pinged the gateway IP 10.128.24.1. But I could not ping 10.128.26.1 or any other address. I ran route add default gw 10.128.24.1 which re-established connectivity with the outside world. Just like I never lost communications. I searched the log files looking for a message but I didn't see anything. Does anyone have a suggestion where I might find a message showing why connectivity was suddenly dropped? -- 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: PHP issue;
SuSE's response was to wait for the developer in-charge of PHP to incorporate a release of PHP that supports 64bit systems. Meanwhile I continue to sit idle. Would it be a bad thing to download and install the PHP source myself? I don't feel very comfortable with this but right now I don't see any other choice. Does anyone else have a suggestion? Thanks, Doug -Original Message- From: Clark, Douglas Sent: Thursday, July 14, 2005 3:30 PM To: 'LINUX-390@VM.MARIST.EDU' Cc: Clark, Douglas Subject: RE: PHP issue; Any experts The version of PHP I am running on the mainframe is 4.3.4 which is what came from SuSE. The release notes from PHP version 4.3.5 states a number of fixes were applied to correct 64bit issues and I hope by upgrading to a later version I will correct my problem. I have a maintenance contract with SuSE/Novell (I get to download the patches) but not a support contract. Does downloading the latest source code and installing it violate the maintenance contract? Will I get patches for versions of PHP that I am no longer running? I have always relied on the download and what is supplied directly from SuSE in the past so this is new ground for me. TIA Doug -Original Message- From: Clark, Douglas Sent: Wednesday, July 13, 2005 8:27 PM To: LINUX-390@VM.MARIST.EDU Cc: Clark, Douglas Subject:PHP issue; Any experts I have run into a problem running PHP code using preg_match_all. I'm racking my brain trying to figure out a solution. Maybe someone else knows the answer? I have two boxes that I'm working on, and I've moved some PHP code from one box using PHP version 4.2.2 (Intel running Red Hat) to another using PHP version 4.3.4 (z890 running SuSE S390x). -- 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: PHP issue; Any experts
The version of PHP I am running on the mainframe is 4.3.4 which is what came from SuSE. The release notes from PHP version 4.3.5 states a number of fixes were applied to correct 64bit issues and I hope by upgrading to a later version I will correct my problem. I have a maintenance contract with SuSE/Novell (I get to download the patches) but not a support contract. Does downloading the latest source code and installing it violate the maintenance contract? Will I get patches for versions of PHP that I am no longer running? I have always relied on the download and what is supplied directly from SuSE in the past so this is new ground for me. TIA Doug -Original Message- From: Clark, Douglas Sent: Wednesday, July 13, 2005 8:27 PM To: LINUX-390@VM.MARIST.EDU Cc: Clark, Douglas Subject: PHP issue; Any experts I have run into a problem running PHP code using preg_match_all. I'm racking my brain trying to figure out a solution. Maybe someone else knows the answer? I have two boxes that I'm working on, and I've moved some PHP code from one box using PHP version 4.2.2 (Intel running Red Hat) to another using PHP version 4.3.4 (z890 running SuSE S390x). -- 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
PHP issue; Any experts
I have run into a problem running PHP code using preg_match_all.
I'm racking my brain trying to figure out a solution. Maybe someone
else knows the answer?
I have two boxes that I'm working on, and I've moved some PHP code from
one box using PHP version 4.2.2 (Intel running Red Hat) to another using PHP
version 4.3.4 (z890 running SuSE S390x). The code is as follows:
?php
$lc = A-Za-z_'0-9\x80-\xFF\-;
$filteredText = First Next Last;
if(preg_match_all('/([-+~]?)(([' . $lc . ']+)(\*?)|[^]*)/',
$filteredText,$m,PREG_SET_ORDER))
{
foreach($m as $terms)
{
print(terms[1-3] = [${terms[1]}, ${terms[2]},
{terms[3]}]br/);
}
}
else
print(Error: no match or nothing in filteredText.);
?
On the 4.2.2 box the output is:
terms[1-3] = [, First, First]
terms[1-3] = [, Next, Next]
terms[1-3] = [, Last, Last]
On the 4.3.4 box the output is:
terms[1-3] = [Next, Last, ]
terms[1-3] = [, , ]
terms[1-3] = [Next, Last, ]
terms[1-3] = [Next, Last, ]
terms[1-3] = [, , ]
For additional information, I have the server info. listed below.
PHP 4.2.2 box:
-Linux 7njvv01a.bco-home.com 2.4.20-6 #1 Thu Feb 27 10:06:59 EST 2003
i686
-Configure Command:
'./configure'
'--host=i386-redhat-linux'
'--build=i386-redhat-linux'
'--target=i386-redhat-linux-gnu'
'--program-prefix='
'--prefix=/usr'
'--exec-prefix=/usr'
'--bindir=/usr/bin'
'--sbindir=/usr/sbin'
'--sysconfdir=/etc'
'--datadir=/usr/share'
'--includedir=/usr/include'
'--libdir=/usr/lib'
'--libexecdir=/usr/libexec'
'--localstatedir=/var'
'--sharedstatedir=/usr/com'
'--mandir=/usr/share/man'
'--infodir=/usr/share/info'
'--cache-file=../config.cache'
'--with-config-file-path=/etc'
'--with-config-file-scan-dir=/etc/php.d'
'--enable-force-cgi-redirect'
'--disable-debug'
'--enable-pic'
'--disable-rpath'
'--enable-inline-optimization'
'--with-bz2'
'--with-db3'
'--with-curl'
'--with-dom=/usr'
'--with-exec-dir=/usr/bin'
'--with-freetype-dir=/usr'
'--with-png-dir=/usr'
'--with-gd'
'--enable-gd-native-ttf'
'--with-ttf'
'--with-gdbm'
'--with-gettext'
'--with-ncurses'
'--with-gmp'
'--with-iconv'
'--with-jpeg-dir=/usr'
'--with-openssl'
'--with-png'
'--with-pspell'
'--with-regex=system'
'--with-xml'
'--with-expat-dir=/usr'
'--with-zlib'
'--with-layout=GNU'
'--enable-bcmath'
'--enable-exif'
'--enable-ftp'
'--enable-magic-quotes'
'--enable-safe-mode'
'--enable-sockets'
'--enable-sysvsem'
'--enable-sysvshm'
'--enable-discard-path'
'--enable-track-vars'
'--enable-trans-sid'
'--enable-yp'
'--enable-wddx'
'--without-oci8'
'--with-pear=/usr/share/pear'
'--with-imap=shared'
'--with-imap-ssl'
'--with-kerberos=/usr/kerberos'
'--with-ldap=shared'
'--with-mysql=shared,/usr'
'--with-pgsql=shared'
'--with-snmp=shared,/usr'
'--with-snmp=shared'
'--enable-ucd-snmp-hack'
'--with-unixODBC=shared'
'--enable-memory-limit'
'--enable-bcmath'
'--enable-shmop'
'--enable-versioning'
'--enable-calendar'
'--enable-dbx'
'--enable-dio'
'--enable-mcal'
'--with-apxs2=/usr/sbin/apxs'
PHP 4.3.4 box:
-Linux techlnux 2.6.5-7.155.29-s390x #1 SMP Thu Jun 2 12:07:05 UTC 2005
s390x
s390x s390x GNU/Linux
-Configure Command:
'./configure'
'--prefix=/usr'
'--datadir=/usr/share/php'
'--mandir=/usr/share/man'
'--bindir=/usr/bin'
'--libdir=/usr/share'
'--includedir=/usr/include'
'--sysconfdir=/etc'
'--with-_lib=lib64'
'--with-config-file-path=/etc'
'--with-exec-dir=/usr/lib64/php/bin'
'--disable-debug'
'--enable-inline-optimization'
'--enable-memory-limit'
'--enable-magic-quotes'
'--enable-safe-mode'
'--enable-sigchild'
'--disable-ctype'
'--disable-session'
'--without-mysql'
'--disable-cli'
'--without-pear'
'--with-openssl'
'--with-apxs2=/usr/sbin/apxs2-prefork'
's390x-suse-linux'
The 4.2.2 box is actually the one that is giving me the correct data
back. Is there something that I have to change in the configuration
that relates to preg_match_all?
Any help would be greatly appreciated.
Thanks for any and all comments/suggestions.
--
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
LPAR only Linux
We are upgrading our system to a z890 (and getting a new HMC) which is now installed and running on the old hardware a z800. I see a new feature (Integrated Ascii Console) and I have been searching for a redpaper or existing e-mail archives from this list on how to cofigure so I can use this console to work with Linux instead of the horrible existing HMC single line mode interface. Can someone point me to documentation or some instructions about how to get this interface to work. Now when I click on the icon on the HMC I just gat a blank window with no text and I cannont type anything into it. TIA -- by the time I get any responses (and assuming things go well) I will be running Linux on a 890 box - still without VM. The IBM rep here just told me that VM to manage Linux only (running on our single IFL) is reasonable. Can someone confirm that. We are (like most companies) trying to keep costs down and avoid being outsourced. Doug -- 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: MediaWiki; search problems
I sent a post about a problem searching from within a wiki I am running under my Linux system. I have not seen the post (not unusual) but no one has responded (which is unusual) and I just wanted to confirm if the post made it to the list and no one has posted regarding this issue. Or if our e-mail gestapo blocked the post from even being sent. If someone could just post and let me know that this made it, I would be very thankful. -Original Message- From: Clark, Douglas Sent: Monday, June 27, 2005 6:07 PM To: 'Linux on 390 Port' Subject: MediaWiki; search problems I am hosting a wiki from Mediawiki on my Linux system (LPAR mode no VM; running 64 bit Enterprise Server at 2.6.5-7.151-s390x) that our developers are using to document their work. This database is also on my linux server in mysql. The wiki was ported from a Red Hat linux system also running mysql. I copied the data fine (using a mysql utility) using FTP I copied it to my Linux server and restored the data fine. The wiki can see all the information just fine and they have been making updates and all is working great. The problem the users are having is that it seems that the search option on the wiki is not working. When the search function is attempted on the linux running Red Hat on an PC it works fine. Has anyone else ran into this problem? I hope I supplied all the necessary information, if not let me know and I will try to get it to you. Doug -- 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
MediaWiki; search problems
I am hosting a wiki from Mediawiki on my Linux system (LPAR mode no VM; running 64 bit Enterprise Server at 2.6.5-7.151-s390x) that our developers are using to document their work. This database is also on my linux server in mysql. The wiki was ported from a Red Hat linux system also running mysql. I copied the data fine (using a mysql utility) using FTP I copied it to my Linux server and restored the data fine. The wiki can see all the information just fine and they have been making updates and all is working great. The problem the users are having is that it seems that the search option on the wiki is not working. When the search function is attempted on the linux running Red Hat on an PC it works fine. Has anyone else ran into this problem? I hope I supplied all the necessary information, if not let me know and I will try to get it to you. Doug -- 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: NFS question
When I start mvsnfs, there are no filesystems exported to be mounted I copied the following text from my system log file, but I can't see any error messages detailing what problem I am having. GFSA348I (MVSNFS ) OS/390 NETWORK FILE SYSTEM SERVER (HDZ11TS) STARTED. GFSA554I (MVSNFS ) REGISTER FOR PORT 2049 PROGRAM 13 - VERSION 2 - FAILED. -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 8:02 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question When I did it years ago, it seemed pretty straightforward. I wouldn't think it would have gotten more complicated with z/OS, but I could be wrong. What exactly are the symptoms you're seeing? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, May 09, 2005 6:06 PM To: LINUX-390@VM.MARIST.EDU Subject: NFS question I want to setup under Linux the ability to mount an hfs filesystem exported by our zOS 1.4 system but I cannot get the configuration correct for zOS. I have tried diligently to follow the configuration process found in the z/OS V1R2. Network File Systems Customization and Operations manual (pub no. SC26-7417-02) but without any luck. I believe I have NFS installed correctly (including support for UNICODE) but I can't seem to get the EXPORT process to make a filesystem available. Can someone point me in the right direction? Thanks, Doug -- 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: NFS question
If it is on by default, but I did not start PORTMAP. I just configured NFS based on the z/OS Network File System Customization and Operation manual. Is there a better manual to reference the installation of NFS? Also, can someone point me to where I can see syslogd? I don't know if there is any information there but I can't say I have ever looked at it. -Original Message- From: Michael Morgan [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 10:10 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question The message indicating that port 2049 was not registered is an error. Do you have the PORTMAP address space started? ..thanks [EMAIL PROTECTED] wrote: When I start mvsnfs, there are no filesystems exported to be mounted I copied the following text from my system log file, but I can't see any error messages detailing what problem I am having. GFSA348I (MVSNFS ) OS/390 NETWORK FILE SYSTEM SERVER (HDZ11TS) STARTED. GFSA554I (MVSNFS ) REGISTER FOR PORT 2049 PROGRAM 13 - VERSION 2 - FAILED. -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 8:02 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question When I did it years ago, it seemed pretty straightforward. I wouldn't think it would have gotten more complicated with z/OS, but I could be wrong. What exactly are the symptoms you're seeing? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, May 09, 2005 6:06 PM To: LINUX-390@VM.MARIST.EDU Subject: NFS question I want to setup under Linux the ability to mount an hfs filesystem exported by our zOS 1.4 system but I cannot get the configuration correct for zOS. I have tried diligently to follow the configuration process found in the z/OS V1R2. Network File Systems Customization and Operations manual (pub no. SC26-7417-02) but without any luck. I believe I have NFS installed correctly (including support for UNICODE) but I can't seem to get the EXPORT process to make a filesystem available. Can someone point me in the right direction? Thanks, Doug -- 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 -- 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: NFS question
As you expected, portmapper failed. I am off to read TCP/IP for MVS: Customization and Administration Guide to see what I need to do to configure and start portmap. There is a reference to configuring the Domain Name Server and starting NAMESRV right after the information about portmap. Should I get that started too? *** EZA4329E orpcinfo: can't contact portmapper: EZA4339E RPC: Remote system error - EDC8128I Connection refused. -Original Message- From: Michael Morgan [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 10:48 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question That's a good manual. In the beginning of chapter 5, it says to start portmap. What does the command: rpcinfo -p mvs_system show, where mvs_system is your mvs host name? [EMAIL PROTECTED] wrote: If it is on by default, but I did not start PORTMAP. I just configured NFS based on the z/OS Network File System Customization and Operation manual. Is there a better manual to reference the installation of NFS? Also, can someone point me to where I can see syslogd? I don't know if there is any information there but I can't say I have ever looked at it. -Original Message- From: Michael Morgan [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 10:10 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question The message indicating that port 2049 was not registered is an error. Do you have the PORTMAP address space started? ..thanks [EMAIL PROTECTED] wrote: When I start mvsnfs, there are no filesystems exported to be mounted I copied the following text from my system log file, but I can't see any error messages detailing what problem I am having. GFSA348I (MVSNFS ) OS/390 NETWORK FILE SYSTEM SERVER (HDZ11TS) STARTED. GFSA554I (MVSNFS ) REGISTER FOR PORT 2049 PROGRAM 13 - VERSION 2 - FAILED. -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 10, 2005 8:02 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: NFS question When I did it years ago, it seemed pretty straightforward. I wouldn't think it would have gotten more complicated with z/OS, but I could be wrong. What exactly are the symptoms you're seeing? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, May 09, 2005 6:06 PM To: LINUX-390@VM.MARIST.EDU Subject: NFS question I want to setup under Linux the ability to mount an hfs filesystem exported by our zOS 1.4 system but I cannot get the configuration correct for zOS. I have tried diligently to follow the configuration process found in the z/OS V1R2. Network File Systems Customization and Operations manual (pub no. SC26-7417-02) but without any luck. I believe I have NFS installed correctly (including support for UNICODE) but I can't seem to get the EXPORT process to make a filesystem available. Can someone point me in the right direction? Thanks, Doug -- 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 -- 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
NFS question
I want to setup under Linux the ability to mount an hfs filesystem exported by our zOS 1.4 system but I cannot get the configuration correct for zOS. I have tried diligently to follow the configuration process found in the z/OS V1R2. Network File Systems Customization and Operations manual (pub no. SC26-7417-02) but without any luck. I believe I have NFS installed correctly (including support for UNICODE) but I can't seem to get the EXPORT process to make a filesystem available. Can someone point me in the right direction? Thanks, Doug -- 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: Hipersockets and DB/2
When DB/2 starts it (via smoke and mirrors) communicates with TCP/IP and issues a gethostid() request. In the tcpip(profile) configuration I did not have a primaryinterface parameter set and therefore the system defaulted to the first interface found in the Home stanza which was my hipersocket definition. My fix was to assign primaryinterface lcs0 sans quotes which points to my OSA and the external world and to change the order of the hosts to have the primary adapter first. Everything is fine now. -Original Message- From: Gianfranco Ciotti [mailto:[EMAIL PROTECTED] Sent: Thursday, April 14, 2005 12:05 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Hipersockets and DB/2 I'm not very exert, but error seems that z/OS tries to resolve the host name of 192.168.1.68 machine but faild. What do you mean for refuses remote connections? Can you ping, if echo replay is enabled, z/OS machine from zlinux using ip address? Thursday 14 April 2005 06:14, You wrote: After, I configured hipersockets for Linux; my DB/2 (under z/OS v1r4) systems now fails refuses remote connections. Here is the log from DB/2 on the mainframe (running in an LPAR no VM). Everything else works fine. I know that this is not a Linux question exactly, but I want hipersockets and so it becomes my issue to resolve. Does anyone have an idea where I should look or where a more appropriate forum would be to ask this question? 20.51.26 STC05183 DSNL512I @ DSNLILNR TCP/IP 766 766 GETHOSTBYADDR(192.168.1.68) FAILED WITH 766RETURN CODE=1 AND REASON CODE= 20.54.40 STC05183 DSNL512I @ DSNLILNR TCP/IP 767 767 GETHOSTBYADDR(192.168.1.68) FAILED WITH 767RETURN CODE=1 AND REASON CODE= 20.57.54 STC05183 DSNL512I @ DSNLILNR TCP/IP 768 Thanks, Doug -- 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
Hipersockets and DB/2
After, I configured hipersockets for Linux; my DB/2 (under z/OS v1r4) systems now fails refuses remote connections. Here is the log from DB/2 on the mainframe (running in an LPAR no VM). Everything else works fine. I know that this is not a Linux question exactly, but I want hipersockets and so it becomes my issue to resolve. Does anyone have an idea where I should look or where a more appropriate forum would be to ask this question? 20.51.26 STC05183 DSNL512I @ DSNLILNR TCP/IP 766 766 GETHOSTBYADDR(192.168.1.68) FAILED WITH 766RETURN CODE=1 AND REASON CODE= 20.54.40 STC05183 DSNL512I @ DSNLILNR TCP/IP 767 767 GETHOSTBYADDR(192.168.1.68) FAILED WITH 767RETURN CODE=1 AND REASON CODE= 20.57.54 STC05183 DSNL512I @ DSNLILNR TCP/IP 768 Thanks, Doug -- 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: Problems with SUSE LINUX install
I had a similar problem (even to the point of hanging initrd 62% every time) and I found that one of the ISO images I used was bad. Have you verified that what you are using is good? -Original Message- From: George Dranes [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 06, 2005 7:31 AM To: LINUX-390@VM.MARIST.EDU Subject: Problems with SUSE LINUX install I'm attempting to install SUSE LINUX Enterprise Server 9 (64 bit) for IBM zSeries on an LPAR. I've assigned 512MB to the partition along with a 3390 mod3 as a swap partition. I'm trying to install from an FTP server on which I've set up an installroot directory with core9 and sles9 directories under it as per Novell's online documentation. I am able to connect to the VNCSERVER and am using YAST to install. I get to the Finishing Basic Installation creating initrd 62% complete screen and it just appears to hang and installation never completes. I was hoping someone out there has run into a similar issue with SUSE LINUX. Any help would be appreciated. Thanks. University Information Management Systems George Dranes Manager-Technical Services [EMAIL PROTECTED] Morgan Hall 121 1 University Circle Macomb, IL 61455-1390 tel: 309-298-1097 X261 fax: 309-298-1451 -- 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: zLinux 31 to 64 bit
Showing my ignorance, but the logic I use is that 31bit apps can run in either a 31 bit OS or a 64 bit OS. Unless the application is doing something specific and detecting that it has reached the 31 bit line, do you really have to worry? -Original Message- From: Cortes, Marcy D. [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 30, 2005 9:33 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: zLinux 31 to 64 bit We will move the sles 7 to sles 9's very soon. I don't see a need to convert the 31bit to 64 bit unless they are storage constrained. Seems like if there weren't it would probably just be adding overhead; let's let one of the performance experts weigh in on that. Some of our app developers may want to move from sles 8 to sles 9 for later levels of things like compilers, autoconf, tomcat, etc. They will probably just want another server and migrate off the old one themselves. I don't forsee upgrading many of the sles 8 to sles 9.As new ones come on, we'll look at if they can run on 9 then put them there. Just need more time to do all this! If I had unlimited resources and time, they might all get upgraded to 9. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: Wednesday, March 30, 2005 9:22 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] zLinux 31 to 64 bit Well, I've read the manual, and basically, the only question that I asked that it answered was that to use 64 bit Sles9, you have to do a new install. But considering the lack of response from others, it kind of leads me to believe that anyone that is going to Sles9 and has earlier releases of Suse, are not migrating their applications to the next release. No matter what, I'll convert the Sles7 images to Sles9. The question is why or why not would someone convert Sles8 images to Sles9 and whether to convert Sles9 31 bit to Sles9 64 bit. So, is it a given that everyone should do the conversion? Or that you shouldn't do the conversion? That is given, that is it not a problem from the application side to do the conversion? Tom Duerbusch THD Consulting [EMAIL PROTECTED] 03/29/05 12:28 PM Some answers to your questions are in a Linux 2.4 to 2.6 Transition Guide PDF mentioned in today's posting by Jim Sibley: Linux on zSeries page http://www-1.ibm.com/servers/eserver/zseries/os/linux/index.html There are more and more links to whitepapers, tips and hints, redbooks (and of course, marketing stuff). An interesting white paper is available there dated this month (March,2005): Linux 2.4 to 2.6 Transition Guide. Jim Sibley -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: Tuesday, March 29, 2005 1:25 PM To: LINUX-390@VM.MARIST.EDU Subject: zLinux 31 to 64 bit Soon, we will have a z/890 and I need to make, at least, some of my Linux images, 64 bit. At that point, we will be on z/VM 5.1. 1. At this point, I don't really have a problem with just reinstalling Sles9 in order to get 64 bit. However, is there a way to migrate or toggle 64 bit mode in a Sles9 image installed on a 31 bit system? 2. I have some Sles7 and Sles8 images that I was thinking of reinstalling as Sles9 images. They don't need 64 bit capabilities. Is there a reason to install Sles9 as 31 bit when you have a 64 bit environment? Is there a performance hit on 64 bit vs 31 bit? Can you install a 31 bit Suse9 when in a 64 bit environment? 3. Sles9 seems to take more resources with the default install then Sles8 and Sles7. A Sles9 31 bit image would use swap space when booting with 32MBs, vs Sles7 and Sles8 never used swap during boot even in a 24MB machine. Others have indicated that Sles9 seems to take more CPU when idling. It seems to me that there are more services running by default in Sles9 that need to be looked at and/or shutdown. Getting off of Sles7 is a given. Too old and I don't want to have the administraction overhead of supporting every Suse versionG. But what are others feeling of having mixed release levels of Suse, given an environment where you don't have to. i.e. it is easy to migrate Sles8 to Sles9? 1. Why bother? 2. Yea, I'll get to it later? 3. Bite the bullet and stop supporting mixed environments? 4. Wish we could do it? 5. Don't, stop! The additional resources is a concern? 6. I don't like change? (hey, I still have my VM/ESA 370 mode packs spinning...don't ask) 7. We migrate when we need to. 8. The release dies when the application dies (or a new release needs to be
Re: How to determine if you are running on 31 or 64 bit system
If you are running 31 Bit the output from uname -m would be s390 (without the x) -Original Message- From: Michael MacIsaac [mailto:[EMAIL PROTECTED] Sent: Thursday, March 24, 2005 11:05 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: How to determine if you are running on 31 or 64 bit system Is there a simple way to determine if you are running on a 64-bit system? # uname -m s390x Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061 -- 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: New Shark
Here are the steps I used to clone the root filesystem to a new volume Shutdown Linux Performed a complete full volume backup of original dasd Restored disk units to new drive assignments Started Linux Logged and became root Execute cd /sys/devices/css0 sans quotes Ran echo 1 `find | grep 2505 | grep online` sans double quotes Ran cat /proc/dasd/devices sans quotes which returned the following: 10.0.1242(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 601020 blocks, 2347 MB 20.0.150e(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 1803060 blocks, 7043 MB 30.0.1611(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 601020 blocks, 2347 MB 40.0.113e(ECKD) at ( 94:12) is dasdd : active at blocksize: 4096, 601020 blocks, 2347 MB 50.0.2505(ECKD) at ( 94:16) is dasde : active at blocksize: 4096, 1803060 blocks, 7043 MB where dasde is the new device on disk unit address 2505 on line 5 Ran dasdfmt -b 4096 -v -f /dev/dasde sans quotes to prepare the disk to receive the data. Ran fdasd /dev/dasde sans quotes and made 3 partitions, for /, /boot, and swap Ran mke2fs -b 4096 /dev/dasde1 sans quotes for the /boot partition making it an ext2 filesystem Ran mke2fs -j -b 4096 /dev/dasde2 sans quotes for the / partition making it a journal ext3 filesystem Used /mntboot as a temporary mount point and mounted the DASD volume on it using mount /dev/dasde1 /mntboot sans quotes Used /mnt as a temporary mount point and mounted the DASD volume on it using mount /dev/dasde2 /mnt sans quotes Typed cd / sans quotes and hit enter Ran tar -clpSf - . | (cd /mnt ; tar -xpSf - ) sans quotes to copy the current root file system to the new volume Type cd /boot sans quotes and hit enter Ran tar -clpSf - . | (cd /mntboot ; tar -xpSf - ) to copy the boot information Typed cd / sans quotes and hit enter Ran umount mntboot to remove mntboot Ran chroot /mnt sans quotes Ran mount /mnt/boot /dev/dasde1 sans quotes to put Reviewed /etc/zipl.conf, to verify any device number changes. The file is contained below. Edited line 12 to include new dasd. 1 # Modified by YaST2. Last modification on Thu Dec 23 18:03:55 2004 2 3 4 5 [defaultboot] 6 default = ipl 7 8 [ipl] 9 target = /boot/zipl 10 image = /boot/image 11 ramdisk = /boot/initrd 12 parameters = dasd=2242,2505,2611,213e root=/dev/dasdb2 selinux=0 TERM=dumb elevator=cfq 13 14 [dumpdasd] 15 target = /boot/zipl 16 dumpto = /dev/dasd?? 17 18 [dumptape] 19 target = /boot/zipl 20 dumpto = /dev/rtibm0 Ran mkinitrd Ran zipl Ran exit to leave the chroot environment Ran umount /mnt/boot and umount /mnt to free the new file system. Rebooted system. -- 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
Migration to new disk devices
The output from running a mkinitrd command contained the following message Make sure to add 'dasd=dasd-range' to the kernel command line Can someone enlighten me where I need to add the line to my kernel command line I am running SuSE Linux 2.6.5-7.145-s390x in a LPAR without VM TIA Doug -- 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 Shark
I am running Linux 64Bit SLES9 (2.6.5-7.145-s390x #1) in 2 LPARs (no VM) using a shared IFL Output of uname -a Linux techlnux 2.6.5-7.145-s390x #1 SMP Thu Jan 27 09:19:29 UTC 2005 s390x s390x s390x GNU/Linux We are installing a new Shark 800 as a replacement for an existing shark f20. All of the original disk units were configured with unit address of 1xxx and the new Shark 800 is configured with unit address of 2xxx so they can co-exist. I have two 3390 mod 9 drives and 6 3390 mod 3 drives split between the two systems. I use dfdss to do full backups and restores but with the different drive units what do I need to change to make the restore work on the new units? Doug -- 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: New Shark
Great, My plan is to shutdown the existing system and do a complete volume backup and then restart the existing system. As the current system is coming up I plan to restore the disks to the new disk units. Then I am going to mount the new units and issue a chroot and then run yast to activate the proper drive units. Then run mkinitrd and zipl and exit from the chroot. I will then shut down the linux system, modify my HMC and try to bring up the old system on the new dasd. If anyone sees a problem with this please let me know. Doug -Original Message- From: Andrew N Wilt [mailto:[EMAIL PROTECTED] Sent: Monday, March 14, 2005 11:48 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: New Shark I don't believe that you will need to do anything differently to make the restore work on the new drives. As long as they are attached to the z/OS system and varied online, we can restore to them. Thanks, Andrew Wilt IBM DFSMSdss development Tucson, Arizona Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 03/14/2005 12:22:00 PM: I am running Linux 64Bit SLES9 (2.6.5-7.145-s390x #1) in 2 LPARs (no VM) using a shared IFL Output of uname -a Linux techlnux 2.6.5-7.145-s390x #1 SMP Thu Jan 27 09:19:29 UTC 2005 s390x s390x s390x GNU/Linux We are installing a new Shark 800 as a replacement for an existing shark f20. All of the original disk units were configured with unit address of 1xxx and the new Shark 800 is configured with unit address of 2xxx so they can co-exist. I have two 3390 mod 9 drives and 6 3390 mod 3 drives split between the two systems. I use dfdss to do full backups and restores but with the different drive units what do I need to change to make the restore work on the new units? Doug -- 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
Online Update via yast
Running SLES9 for S/390 (64-bit) in an LPAR (no VM) using a shared IFL (I have one other LPAR running SLES9 64-bit) I have never gotten the online update to work. Am I missing something? Our shop has a tight restriction for internet access but I can successfully ping www.suse.de www.suse.de Can someone who has gotten this to work please send me some instructions please. Here is the message I receive: Warning Cannot fetch remote server list. Only user-defined patch sources will be available. Possible solution: Check network connection. URL: http://www.suse.de/cgi-bin/suseservers.cgi http://www.suse.de/cgi-bin/suseservers.cgi Connect failed [Details ][Retry][Ignore][Abort Update] Thanks for your help -- 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: even more sles9 install weirdness
Verify the checksum of your iso files and make sure they are good.
I have included a cat mkinstallroot make sure that the location from where
you mount and copy the CDs is accessible to the script. I used
/ISO_Images_Dir only as an example directory location. Yours will be
different.
Doug
# cat mkinstallroot
#--
# Battling with the linux configuration I ended up writing a
# script (that also copies the CDs' contents) to be
# sure of the steps. It would be nice if SuSE picked
# it up. Hope it helps:
#
# Written by:
# -Mike MacIsaac, IBM [EMAIL PROTECTED] (845) 433-7061
#
# F0r 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
#
#--
#
function mountCopy
# arg 1: the ISO image to mount
# arg 2: the directory to copy to
{
mount -o loop,ro $1 tmpCD
cd tmpCD
cp -a * ../installroot/$2
cd ..
umount tmpCD
}
# main()
# make the directory structure
mkdir installroot tmpCD
cd installroot/
mkdir sles9 core9 yast
cd sles9
mkdir CD1
cd ../core9/
mkdir CD1 CD2 CD3 CD4 CD5
cd ../..
# mount and copy the 6 CDs
mountCopy /ISO_Images_Dir/SLES-9-s390-RC5a-CD1.iso sles9/CD1/
mountCopy /ISO_Images_Dir/SLES-9-s390-RC5-CD2.iso core9/CD1/
mountCopy /ISO_Images_Dir/SLES-9-s390-RC5-CD3.iso core9/CD2/
mountCopy /ISO_Images_Dir/SLES-9-s390-RC5-CD4.iso core9/CD3/
mountCopy /ISO_Images_Dir/SLES-9-s390-RC5-CD5.iso core9/CD4/
mountCopy /ISO_Images_Dir/SLES-9-s390-RC5-CD6.iso core9/CD5/
rmdir tmpCD/
# make symbolic links
cd installroot
ln -s sles9/CD1/boot boot
ln -s sles9/CD1/content content
ln -s sles9/CD1/control.xml control.xml
ln -s sles9/CD1/media.1 media.1
echo -e /sles9/CD1 /sles9/CD1\n/core9/CD1 /core9/CD1 yast/instorder
echo -e /sles9/CD1 /sles9/CD1\n/core9/CD1 /core9/CD1 yast/order
-Original Message-
From: Mark D Pace [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 20, 2005 12:46 PM
To: LINUX-390@VM.MARIST.EDU
Subject: even more sles9 install weirdness
Thanks to all that have blazed the trail of sles9 before me.
I have followed this thread pretty close and have used the installroot
procedure to create an installroot for my CDs. I can start the install, get
into yast, setup the DASD, and then I change my software to Minimal install.
But when the install starts it asks me to mount CD1. OK, just
repeats the request for CD1. Anything else and the install ends. Has
anyone run into this before? Maybe I screwed up the ISO part.
Mark D Pace
Senior Systems Engineer
Mainline Information Systems
1700 Summit Lake Drive
Tallahassee, FL. 32317
Office: 850.219.5184
Fax: 888.221.9862
http://www.mainline.com
This e-mail and files transmitted with it are confidential, and are intended
solely for the use of the individual or entity to whom this e-mail is
addressed. If you are not the intended recipient, or the employee or agent
responsible to deliver it to the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this communication is
strictly prohibited. If you are not one of the named
recipient(s) or otherwise have reason to believe that you received this
message in error, please immediately notify sender by e-mail, and destroy
the original 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: Suse 9.0 CD Validation
Here is the specific files I have stored on my system. SLES-9-s390x-RC5-CD6.iso 64 Bit version; Size = 664,592,384 I ran md5sum SLES-9-s390x-RC5-CD6.iso which yielded: 74301159228f91a4da4a2bb78cb607aa *SLES-9-s390x-RC5-CD6.iso SLES-9-s390-RC5-CD6.iso 32 Bit version; Size = 664,590,336 I ran md5sum SLES-9-s390-RC5-CD6.iso which yielded: 11bb0fcd7e82a07b7ab2878708478768 *SLES-9-s390-RC5-CD6.iso Here are the values from Novell site: 64 Bit Filename MD5 Checksum Value Approx. File Size SLES-9-s390x-RC5a-CD1.iso b45dd5dbb47fad87f58fb1b658dbc7f8 311.9 MB SLES-9-s390x-RC5-CD2.iso 04e7b9d8629e1d973230be67b22dc9b7 576.8 MB SLES-9-s390x-RC5-CD3.iso 1a5b5f0d15b4e182d2b23da478725933 445.0 MB SLES-9-s390x-RC5-CD4.iso cee521cbd1ac6c2e3980da99bd4b652e 485.8 MB SLES-9-s390x-RC5-CD5.iso 7fd515da7f5cdc2bd916ee432da30fd4 642.5 MB SLES-9-s390x-RC5-CD6.iso 74301159228f91a4da4a2bb78cb607aa 633.8 MB 31 Bit Filename MD5 Checksum Value Approx. File Size SLES-9-s390-RC5a-CD1.iso 4f5ca784a148ac0431ee18cd9c7840ce 305.6 MB SLES-9-s390-RC5-CD2.isob7f95b81510dfd527579b184baee5d30 516.6 MB SLES-9-s390-RC5-CD3.iso21d3e2eb32aa83bb0ddad1f08526d37f 417.5 MB SLES-9-s390-RC5-CD4.iso849936436e1fdd351df6403dbf5d7e2d 475.2 MB SLES-9-s390-RC5-CD5.iso7655c5871fae2915efe9644d211041e4 648.5 MB SLES-9-s390-RC5-CD6.iso11bb0fcd7e82a07b7ab2878708478768 633.8 MB -Original Message- From: Tom Duerbusch [mailto:[EMAIL PROTECTED] Sent: Thursday, January 13, 2005 2:46 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Suse 9.0 CD Validation You had me going there for a moment. This is s390, not i386 G Tom Duerbusch THD Consulting Post, Mark K wrote: 679772160 SLES-9-i386-RC5-CD6.iso Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: Thursday, January 13, 2005 5:05 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Suse 9.0 CD Validation Thanks Yep, that is where I got the iso images from. BTW, I noticed you didn't say what size your CD6 was. Do you have one available to quickly check its size? I've ordered the CDs. I should get the CDs well before I get the mainframe disk drives back to try NFS. I'll do the md5sum tomorrow when I get back in. Tom Duerbusch THD Consulting -- 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
Samba 3.0
Running Samba 3.0 , under Linux SLES9 64 bit on a 2066-0A2 (no VM) I have 160+ printers to setup. Many of them are the same type of printer HPLaserJet 4si, HPLaserJet 5, etc. and distributed to over 150 drops/locations through-out our campus. During the process of setting up these printers using Point-and-Print I have scripted several steps to save time. But I have not been able to script the command(s) used to associate a printer with its print driver. I have researched the rundll32 printui command and all of my attempts to execute it and associate a printer with a particular print driver fails. I know that the command has to be passed onto Linux and run, and I was thinking I could execute that command directly in Linux. Does anyone have any experience in this area? -- 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
Samba Configuration Issue
First, I changed the subject. I just didn't think this topic fit the subject description line. Your problem looks like an error with authorization. Sorry that I can't find a link, but Mike MacIsaac wrote a Redbook on this topic titled Printing with Linux on zSeries using CUPS and Samba and should answer your questions. Does anyone have a link to this for document? Doug -Original Message- From: Jose Raul Baron Rodriguez [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 12, 2005 10:45 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES install on z/VM 5.1 I chose the SAMBA installation method and didn't have any problem. I installed SLES 8 under z/VM 4.4. Saludos, Jose Raul Baron Dpto. Sistemas CALCULO S.A. Tel. 91 330 86 44 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
May get VM to manage Linux! Need cost information
Will someone on this list please give me a ballpark cost for VM in an IFL to manage Linux for our system. Our information is that the price for VM is different if it is just run in an IFL and only manage Linux. My manager needs it for a budget meeting he was told about for the first time when they called to tell him he was late for the meeting. I will talk to my sales rep about taking vacation at the most inopportune time. grin Doug -- 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
FW: May get VM to manage Linux! Need cost information
Sorry if I sent this before. I received a command from the list server saying I did something wrong. I am sure I did but it baffles me what. Anyway, please forgive my duplication. Will someone on this list please give me a ballpark cost for VM in an IFL to manage Linux for our system. Our information is that the price for VM is different if it is just run in an IFL and only manage Linux. My manager needs it for a budget meeting he was told about for the first time when they called to tell him he was late for the meeting. I will talk to my sales rep about taking vacation at the most inopportune time. grin Doug -- 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: Suse 9.0 installation
I know that this is late in the game, but the mkinstallroot script (supplied by Mark Post I believe) that was posted here worked great for me. If you are going to install SLES9 it would be worth the effort to search the archives, and implement. -Original Message- From: Dave Jones [mailto:[EMAIL PROTECTED] Sent: Saturday, January 08, 2005 8:04 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Suse 9.0 installation I can add my experiences trying to install SLES9 on a z/VM 5.1 system...and none of them are good. My installation server is an Intel box, running SuSE SLES9. The Intel box has a great deal of disk storage available, so I just put the 6 .iso files onto the server. I just do a simple mount -o loop -t iso9660 to make the cd images available. So far, so good. After booting the initial SLES9 install VM kernel and ram disk, in a 512M virtual machine and getting the networking setup and working (eth0 on a QDIO gLAN) without too much difficulty, I choose SSH and FTP for performing the basic installation, and I specify location of the install media as /CD1 (where I have mounted the CD1.iso file). I then log on, using SSH and start yast. After successfully creating the dasd partitions and making the mount points, yast reports the following error: Cannot read package data from installation media. Media error? On the Intel SLES9 server, I can navigate and view the files on /CD1, and they all appear OK. Anybody got a clue as to what's wrong? TIA. DJ Herczeg, Zoltan wrote: I can feel your pain. I ordered the SuSE sles9 evaluation and installed it via ftp from my windows desktop using war ftp server. It took me days just to get the ftp server set up properly for the initial install. Now after redoing things so many times and working with SuSE support on why my nic cards don't activate when linux boots a month has gone by and I have nothing to show for it. I am running MP3000, lpar with the nics on the MP3000. Zoltan -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: Wednesday, January 05, 2005 12:26 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Suse 9.0 installation -- 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 -- Dave Jones Houston, TX 281.578.7544 (speaking for myself only) -- 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: Suse 9.0 installation
Fair enough, -- Sorry Mike! Still, the script works great for this purpose. -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Monday, January 10, 2005 10:31 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Suse 9.0 installation No, that was Mike MacIsaac, not me. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, January 10, 2005 1:05 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Suse 9.0 installation I know that this is late in the game, but the mkinstallroot script (supplied by Mark Post I believe) that was posted here worked great for me. If you are going to install SLES9 it would be worth the effort to search the archives, and implement. -Original Message- From: Dave Jones [mailto:[EMAIL PROTECTED] Sent: Saturday, January 08, 2005 8:04 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Suse 9.0 installation I can add my experiences trying to install SLES9 on a z/VM 5.1 system...and none of them are good. My installation server is an Intel box, running SuSE SLES9. The Intel box has a great deal of disk storage available, so I just put the 6 .iso files onto the server. I just do a simple mount -o loop -t iso9660 to make the cd images available. So far, so good. After booting the initial SLES9 install VM kernel and ram disk, in a 512M virtual machine and getting the networking setup and working (eth0 on a QDIO gLAN) without too much difficulty, I choose SSH and FTP for performing the basic installation, and I specify location of the install media as /CD1 (where I have mounted the CD1.iso file). I then log on, using SSH and start yast. After successfully creating the dasd partitions and making the mount points, yast reports the following error: Cannot read package data from installation media. Media error? On the Intel SLES9 server, I can navigate and view the files on /CD1, and they all appear OK. Anybody got a clue as to what's wrong? TIA. DJ Herczeg, Zoltan wrote: I can feel your pain. I ordered the SuSE sles9 evaluation and installed it via ftp from my windows desktop using war ftp server. It took me days just to get the ftp server set up properly for the initial install. Now after redoing things so many times and working with SuSE support on why my nic cards don't activate when linux boots a month has gone by and I have nothing to show for it. I am running MP3000, lpar with the nics on the MP3000. Zoltan -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: Wednesday, January 05, 2005 12:26 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Suse 9.0 installation -- 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 -- Dave Jones Houston, TX 281.578.7544 (speaking for myself only) -- 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: Suse 9.0 installation
I installed x86 Linux on an Intel PC (with 20 Gb hard drive and 512 meg of memory) which we have plenty of machines to pick from. I configured vsftp for anonymous ftp. Using that machine as my source, I was successfully able to install SuSE 9.0 on my mainframe. On the pc I could mount the ISO images, run md5sum, etc. and connect to my mainframe using ssh without a problem. That solved my disk space issue because I too had to work with a limited amount of 3390-3 available to me. -Original Message- From: Tom Duerbusch [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 05, 2005 8:34 AM To: LINUX-390@VM.MARIST.EDU Subject: Suse 9.0 installation This is a very narrow focus questiondon't want to get on any other topics. Has anyone, installed Suse 9.0, from the evaluation CDs, via Windows SMB? My responses noted. 1. What hardware platform? ( VM) 2. What IP method (IUCV) 3. What PC operating system used (Windows 2000) 4. How did you do the MD5SUM function under Windows? (didn't) Over the last 2 months, I've tried installing Suse 9.0, under VM, with SMB using an IUCV connection and kept hitting a wall. Logs sent to Suse showed that they did something wrong. (Like they didn't bother to test the installation using real CDs.) We are about ready to throw in the towel on Suse 9.0 as not being ready for prime time and stay on Suse 8.0 (despite some venders telling us that they perfer Suse 9.0). Thanks Tom Duerbusch THD Consulting -- 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: Moving root to a new volume
For us non-VM aware users, can I assume that the command CP LINK causes the new root disk to be available -- aka online, to the original or (old/source) system? -Original Message- From: Tom Shilson [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 28, 2004 8:34 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Moving root to a new volume Here is a list of the steps I did to move my root disk. YMMV. Good Luck. Shut down my target system From a second system, CP LINK to the old root system and the new root disk dasdfmt -b 4096 -v -f /dev/dasdd [This prepares the disk to receive the data. ] fdasd -a -b 4096 /dev/dasdd mke2fs -j -b 4096 /dev/dasdd1 mount old root system as /oldroot mount new disk as /mnt cp --preserve=all --recursive /oldroot/* /mnt/ [There are two dashses before preserve and recursive] cd /mnt/etc Create the zipl.ths.conf file below. cd /mnt/sbin ./zipl -c /mnt/etc/zipl.ths.conf [You want to execute the copy of zipl on the target system] cd / [You need to get out of /mnt so you can umount it.] umount /mnt umount /oldroot CP DET the two minidisks Modify the directory of the targe system to swap the addresses of the old and new root disks. Boot the target system newroot/etc/zipl.ths.conf: # Generated by YaST2 [defaultboot] default=ipl [ipl] target=/mnt/boot/zipl image=/mnt/boot/kernel/image ramdisk=/mnt/boot/initrd parameters=dasd=201-20F root=/dev/dasda1 newroot/etc/fstab: /dev/dasda1 / ext3defaults 1 1 /dev/dasdc1 /homeext3defaults 1 2 /dev/dasdb1 /usr ext3defaults 1 2 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /procproc defaults 0 0 tom - - - - - - - - - - - - Toto, I have a feeling we're not in the mainframe world any more. _/) Tom Shilson ~GEDW VM System Services Aloha Tel: 651-733-7591 tshilson at mmm dot com Fax: 651-736-7689 Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 12/28/2004 08:42:49 AM: Hi all, When I initially installed my Linux Instances, I used MOD-3's. I would now like to move them to MOD-9's because my boss wants to reconfigure all the DASD to MOD-9's. How can I accomplish moving root to a new volume and get it to IPL off that new volume? Thanks Gene -- 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
Question re: Linux SLES9
SLES9 for S/390 (64-bit) in an LPAR (no VM) using a shared IFL (I have one other LPAR running SLES9 31-bit) I have looked and I have not seen any documentation that shows how to add a dasd unit via command line under SLES9. Under SLES8 I used to execute echo add device range= /proc/dasd/devices And then I would execute the following to view the changes: cat /proc/dasd/devices But that does not seem to work any more. -- 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: Question re: Linux SLES9
Is there another way besides using the yast interface? -Original Message- From: Ranga Nathan [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 29, 2004 2:24 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Question re: Linux SLES9 If the dasd address was genned for the LPAR, then it should be visible in yast under system (or hardware) -- DASD. You can then activate it, format and mount. __ Ranga Nathan / CSG Systems Programmer - Specialist; Technical Services; BAX Global Inc. Irvine-California Tel: 714-442-7591 Fax: 714-442-2840 [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 12/29/2004 02:09 PM Please respond to Linux on 390 Port To: LINUX-390@VM.MARIST.EDU cc: Subject:Question re: Linux SLES9 SLES9 for S/390 (64-bit) in an LPAR (no VM) using a shared IFL (I have one other LPAR running SLES9 31-bit) I have looked and I have not seen any documentation that shows how to add a dasd unit via command line under SLES9. Under SLES8 I used to execute echo add device range= /proc/dasd/devices And then I would execute the following to view the changes: cat /proc/dasd/devices But that does not seem to work any more. -- 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
OSA GigaBit Ethernet Adapter
SLES9 for S/390 (31-bit) in an LPAR (no VM) using a shared IFL Six months ago we installed a new mainframe (2066 - 0A2) and it has two Gigabit OSA adapters that were not setup. In January, we will start trying to share them between the LPARS. Do these adapters require a special ethernet cable? TIA Doug -- 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: OSA GigaBit Ethernet Adapter
Thanks, My co-worker was already on top of it and had the PDF downloaded and printed. Our IBM rep said that the cable had to be ordered separately. Seems like they are following the PC model with some parts sold separately / batteries not included mantra. -Original Message- From: Doug Fairobent [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 9:40 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: OSA GigaBit Ethernet Adapter Doug, I suggest you examine Appendix A in the Open Systems Adapter-Express Customer Guide and Reference (SA22-7476-03). - doug [EMAIL PROTECTED] Sent by: Linux on 390 Port To [EMAIL PROTECTED] LINUX-390@VM.MARIST.EDU IST.EDU cc Subject 12/21/2004 12:26 OSA GigaBit Ethernet Adapter PM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU SLES9 for S/390 (31-bit) in an LPAR (no VM) using a shared IFL Six months ago we installed a new mainframe (2066 - 0A2) and it has two Gigabit OSA adapters that were not setup. In January, we will start trying to share them between the LPARS. Do these adapters require a special ethernet cable? TIA Doug -- 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 CONFIDENTIALITY NOTICE: This message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. -- 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: SSH via putty to RH AS 3.0
Running SLES9 for S/390 (31-bit) in an LPAR (no VM) using a shared IFL We would like to move the Windows/2000 DB2/UDB (version 7.2 fix pack 10) inquiry database to a OS-390 Linux DB2/UDB database and wonder if anyone has had a similar experience and would share with us the pros and cons. Also, if it makes a difference, we are using Data Replication (DPropR) running the apply that will update the Linux database all changes that are captured on our master system an AIX RS/6000 running DB2/UDB. This master DB2 is also running version 7.2 fix pack 10. TIA Doug -- 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
Original sent out with wrong subject; DB2 for Linux question
-Original Message- From: Clark, Douglas Sent: Friday, December 17, 2004 11:57 AM To: 'Linux on 390 Port' Subject: RE: SSH via putty to RH AS 3.0 Running SLES9 for S/390 (31-bit) in an LPAR (no VM) using a shared IFL We would like to move the Windows/2000 DB2/UDB (version 7.2 fix pack 10) inquiry database to a OS-390 Linux DB2/UDB database and wonder if anyone has had a similar experience and would share with us the pros and cons. Also, if it makes a difference, we are using Data Replication (DPropR) running the apply that will update the Linux database all changes that are captured on our master system an AIX RS/6000 running DB2/UDB. This master DB2 is also running version 7.2 fix pack 10. TIA Doug -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: LVM woes in SLES 9
Using SLES9 when you are done setting up the logical volumes, you must issue a mk_initrd and zipl commands. If you don't the disks do not survive a restart. -Original Message- From: Ranga Nathan [mailto:[EMAIL PROTECTED] Sent: Friday, December 10, 2004 10:30 PM To: [EMAIL PROTECTED] Subject: LVM woes in SLES 9 I tried to do LVM via Yast many times but have not been successful. After reboot the volume group and logical volumes disappeared. Thanks to VM I re-cloned the guest and have recreated the vol group, this time from command line. But with a POR coming up on Sunday, I am in a dilemma. If I reboot the Linux guest, I will lose the volume group. Before that I need to do whatever to make it stick. Going back, I found some references to mkinitrd, zipl.conf and parmfile changes. Nowhere else on the net do I see any mention of this for other distros. Also I expected YaST to handle any SLES specific quirks. According to the documentation I have come across on the 'net, (here is one for example: http://www-106.ibm.com/developerworks/library/l-lvm2.html) there is no mention of any such special procedures except adding a vgscan -a y in the starting script before file systems are mounted and vgscan -a n at shutdown. Does anyone have a checklist of things to make the vol group persistent across reboot for SLES 9? Thanks a bunch. __ Ranga Nathan / CSG Systems Programmer - Specialist; Technical Services; BAX Global Inc. Irvine-California Tel: 714-442-7591 Fax: 714-442-2840 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: LVM question
I went through the yast panels and added the unit 113e; created the volume group usrdata; added the physical volume (/dev/dasdd1) to the volume group usrdata; and added the logical volume /dev/usrdata/srv. Output from pvscan, vgscan, and lvscan shows: techlnux:~ # pvscan PV /dev/dasdd1 VG usrdata lvm2 [2.29 GB / 1.80 GB free] PV /dev/dasdc1 VG systemlvm2 [2.29 GB / 0free] PV /dev/dasda1 VG systemlvm2 [2.29 GB / 68.00 MB free] Total: 3 [6.87 GB] / in use: 3 [6.87 GB] / in no VG: 0 [0 ] techlnux:~ # vgscan Reading all physical volumes. This may take a while... Found volume group usrdata using metadata type lvm2 Found volume group system using metadata type lvm2 techlnux:~ # lvscan ACTIVE'/dev/usrdata/srv' [500.00 MB] next free (default) ACTIVE'/dev/system/var' [3.30 GB] next free (default) ACTIVE'/dev/system/home' [512.00 MB] next free (default) Output from vgdisplay shows: techlnux:~ # vgdisplay --- Volume group --- VG Name usrdata System ID Formatlvm2 Metadata Areas1 Metadata Sequence No 2 VG Access read/write VG Status resizable MAX LV255 Cur LV1 Open LV 1 Max PV255 Cur PV1 Act PV1 VG Size 2.29 GB PE Size 4.00 MB Total PE 586 Alloc PE / Size 125 / 500.00 MB Free PE / Size 461 / 1.80 GB VG UUID F4TBxx-SrI3-70gb-RSaE-hWCX-MHHY-BUEHgP --- Volume group --- VG Name system System ID Formatlvm2 Metadata Areas2 Metadata Sequence No 10 VG Access read/write VG Status resizable MAX LV255 Cur LV3 Open LV 3 Max PV255 Cur PV2 Act PV2 VG Size 4.58 GB PE Size 4.00 MB Total PE 1172 Alloc PE / Size 1155 / 4.51 GB Free PE / Size 17 / 68.00 MB VG UUID udixdw-j6fY-Sgqn-vo9w-VgL4-w6gq-Xy72m3 Output from ls -l /dev/usrdata shows: techlnux:~ # ls -l /dev/usrdata total 88 dr-x-- 2 root root 4096 Dec 8 09:07 . drwxr-xr-x 14 root root 81920 Dec 8 09:07 .. lrwxrwxrwx 1 root root23 Dec 8 09:07 srv - /dev/mapper/usrdata-srv Output from ls -l /dev/mapper shows: techlnux:~ # ls -l /dev/mapper total 88 drwxr-xr-x 2 root root 4096 Dec 8 09:07 . drwxr-xr-x 14 root root 81920 Dec 8 09:07 .. lrwxrwxrwx 1 root root 16 Dec 7 16:56 control - ../device-mapper brw--- 1 root root 253, 2 Nov 4 13:03 system-home brw--- 1 root root 253, 1 Nov 4 13:03 system-opt brw--- 1 root root 253, 0 Nov 4 13:03 system-var brw--- 1 root root 253, 3 Dec 8 09:07 usrdata-srv Is there some magic now that I need to perform to make this permanent? What should be my next step? -Original Message- From: Mark Post [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 07, 2004 6:01 PM To: [EMAIL PROTECTED] Subject: Re: LVM question Ok, this looks like a difference between LVM and the LVM2 that comes with 2.6. I guess vgdisplay and ls -l /dev/usrdata might tell us something. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Tuesday, December 07, 2004 8:06 PM To: [EMAIL PROTECTED] Subject: Re: LVM question I crossed up too many systems trying to get this to work and I had to restore from backups. I then ran pvscan sans quotes techlnux:/proc # pvscan PV /dev/dasdc1 VG system lvm2 [2.29 GB / 0free] PV /dev/dasda1 VG system lvm2 [2.29 GB / 68.00 MB free] Total: 2 [4.58 GB] / in use: 2 [4.58 GB] / in no VG: 0 [0 ] When I ran cat /proc/lvm/global sans quotes I received: No such file or directory 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
LVM question
SLES9 for S/390 (31-bit) in an LPAR (no VM) using a shared IFL I must be missing something -- but things may be different under SLES9 Currently I have /srv filesytem under root. I would like to /srv under LVM. I keep getting an error during the IPL stating /sbin/fsck.reiserfs /srv failed open the device /dev/usrdata/srv? What am I missing. I have successfully created the new volume group, added the physical dasd volume to the group. Created the logical volume group. Ran fsck.reiserfs mounted the device updated fstab and ran zipl. There must be something else but I don't see it. Thanks -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: LVM question
I crossed up too many systems trying to get this to work and I had to restore from backups. I then ran pvscan sans quotes techlnux:/proc # pvscan PV /dev/dasdc1 VG system lvm2 [2.29 GB / 0free] PV /dev/dasda1 VG system lvm2 [2.29 GB / 68.00 MB free] Total: 2 [4.58 GB] / in use: 2 [4.58 GB] / in no VG: 0 [0 ] When I ran cat /proc/lvm/global sans quotes I received: No such file or directory -Original Message- From: Mark Post [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 07, 2004 4:47 PM To: [EMAIL PROTECTED] Subject: Re: LVM question What does the output of cat /proc/lvm/global show you? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Tuesday, December 07, 2004 7:20 PM To: [EMAIL PROTECTED] Subject: LVM question SLES9 for S/390 (31-bit) in an LPAR (no VM) using a shared IFL I must be missing something -- but things may be different under SLES9 Currently I have /srv filesytem under root. I would like to /srv under LVM. I keep getting an error during the IPL stating /sbin/fsck.reiserfs /srv failed open the device /dev/usrdata/srv? What am I missing. I have successfully created the new volume group, added the physical dasd volume to the group. Created the logical volume group. Ran fsck.reiserfs mounted the device updated fstab and ran zipl. There must be something else but I don't see it. Thanks -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: LVM question
I had to restore back to a state previous to the creation of usrdata. I have LVM with system VG and so I captured it. I get the same error when I tried to add a logical volume to system also. techlnux:~ # vgdisplay --- Volume group --- VG Name system System ID Formatlvm2 Metadata Areas2 Metadata Sequence No 10 VG Access read/write VG Status resizable MAX LV255 Cur LV3 Open LV 3 Max PV255 Cur PV2 Act PV2 VG Size 4.58 GB PE Size 4.00 MB Total PE 1172 Alloc PE / Size 1155 / 4.51 GB Free PE / Size 17 / 68.00 MB VG UUID udixdw-j6fY-Sgqn-vo9w-VgL4-w6gq-Xy72m3 techlnux:~ # ls -l /dev/system total 88 dr-x-- 2 root root 4096 Dec 7 16:56 . drwxr-xr-x 13 root root 81920 Dec 7 16:57 .. lrwxrwxrwx 1 root root23 Dec 7 16:56 home - /dev/mapper/system-home lrwxrwxrwx 1 root root22 Dec 7 16:56 opt - /dev/mapper/system-opt lrwxrwxrwx 1 root root22 Dec 7 16:56 var - /dev/mapper/system-var techlnux:~ # ls -l /dev/usrdata -Original Message- From: Mark Post [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 07, 2004 6:01 PM To: [EMAIL PROTECTED] Subject: Re: LVM question Ok, this looks like a difference between LVM and the LVM2 that comes with 2.6. I guess vgdisplay and ls -l /dev/usrdata might tell us something. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Tuesday, December 07, 2004 8:06 PM To: [EMAIL PROTECTED] Subject: Re: LVM question I crossed up too many systems trying to get this to work and I had to restore from backups. I then ran pvscan sans quotes techlnux:/proc # pvscan PV /dev/dasdc1 VG system lvm2 [2.29 GB / 0free] PV /dev/dasda1 VG system lvm2 [2.29 GB / 68.00 MB free] Total: 2 [4.58 GB] / in use: 2 [4.58 GB] / in no VG: 0 [0 ] When I ran cat /proc/lvm/global sans quotes I received: No such file or directory 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: SLES9 Install hang
I had problems with the SLES9 hanging during the install too. I believe that I had a bad CD image that I downloaded. Try downloading the image again and verify downloaded ISO images using MD5SUM. To check the MD5SUM of the filename.iso you would type the following in a terminal: md5sum filename.iso sans quotes. I believe novell gives you the following: FilenameMD5 Checksum Value Approx. File Size SLES-9-s390x-RC5-CD2.iso04e7b9d8629e1d973230be67b22dc9b7 576.8 MB (64 bit) SLES-9-s390-RC5-CD2.iso b7f95b81510dfd527579b184baee5d30 516.6 MB (31 bit) Hope this helps. -Original Message- From: Tom Duerbusch [mailto:[EMAIL PROTECTED] Sent: Monday, December 06, 2004 9:48 AM To: [EMAIL PROTECTED] Subject: SLES9 Install hang I went back thru the archives a couple months, and didn't see any discussion of this one... I'm trying to install the current SLES9 evaluation CDs. Once we get our support keys, I assume that this evaluation distribution can be upgraded, via YOU, to a current, production distribution. Wellwe hang... The first hang, I was able to get around. When you are first asked to select/activate/format dasd, just select and activate them. If you format them, you will hang when doing the package selection. Wait for the partitioner step, and format them there. But the second hang, I can't seem to get around... After CD1 has been loaded, it asks for CD2. I insert CD2 and click OK. Nothing. I can use Windows explorer to see that CD2 looks like a normal Suse CD (as least looks like all the others). I have 256 MBs virtual defined, using SMB for the install, with an IUCV network connection. I've tried the abort installation button, but it presses, and nothing happens. Are there any known problems with the evaluation CDs that would make them, rather unusable? Thanks Tom Duerbusch THD Consulting -- 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: SLES9 Install hang
When I successfully installed, the ISO images I used matched what Novell provided. I did run the MD5 checksum program under Linux on a PC. I don't know if that might make a difference vs. Win2K. -Original Message- From: Ledbetter, Scott E [mailto:[EMAIL PROTECTED] Sent: Monday, December 06, 2004 3:49 PM To: [EMAIL PROTECTED] Subject: Re: SLES9 Install hang Now I'm wondering about my SLES9 images. I downloaded all 6 CDs for both 31 and 64 bit versions from the Novell website to my Win2K PC. Not a single one matches the MD5 checksum on the Novell Download webpage. This seems so unlikely that I actually went and found another copy of md5sum. Same problem. I downloaded new copies to a different PC, and came up with the same MD5 values. Are the MD5 values on the SuSE page bad? I'm glad someone brought this up before I actually attempted to install. Scott Ledbetter StorageTek -- 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
Question re: Linux SLES9
Running: SLES9 for S/390 (31-bit) in two LPARs (no VM) Output from uname: -s, --kernel-nameLinux -r, --kernel-release 2.6.5-7.97-s390 -v, --kernel-version #1 SMP Fri Jul 2 14:21:59 UTC 2004 -m, --machines390 -p, --processor s390 -i, --hardware-platform s390 -o, --operating-system GNU/Linux --versionuname (coreutils) 5.2.1 Written by David MacKenzie. I have three other LPARs running OS/390 R2.10 (production, development, tech support) where 2 CHPIDs are used in production to access the 3490-A20 tape drives, 1 CHIP each assigned for development and tech support to access the tape drives. I used the Load from CD option off the HMC to install Linux and I have never accessed the four 3490 tape drives in our environment. My co-worker tells me that he can pull one of the two CHPIDs from the production system and assign it to Linux. First, after the new I/O configuration takes place, and the Linux LPAR is restarted (we have a machine power-on reset scheduled in early January) will Linux automatically detect the tape drive and load the necessary drivers? What steps do I need to take to access the tape drives for products like Amanda, or Bacula, etc.? We also have a VTS and an ATL that is being shared by the three LPARs and various UNIX and Windows servers. Would it be a better use of my time to use the VTS or the ATL instead of the stand alone 3490 tape drives? Just trying to understand this stuff a little better. Doug -- 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
SLES9 31 bit upgrade to 64 bit
SLES9 for S/390 (31-bit) in an LPAR (no VM) using a shared IFL (I have one other LPAR running SLES9 31-bit) I would like to upgrade my existing 31-bit system to 64-bit. When I tried running upgrade mode, there were hundreds of conflicts and I was not sure how to resolve them. That seemed logical to me (31-bit vs. 64-bit issues) but should I delete the dependencies, ignore them, or what? Any suggestions on an approach would be much appreciated. Doug -- 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: Installation of SLES9 hangs on 'creating initrd'
Because I could not get past the initrd hanging indefinitely problem, I went back and pulled down new set of ISO files and tried again. Now I get past the initrd (at least it doesn't hang) and I continue to the second phase (running YaST2.sshinstall) -- that all seems to run well but when I try to restart Linux, the system hangs trying to start slpd. Currently, I am installing the default rpms but I have pulled the slp - server package. My vote is SLES9 for MVS needs to try again. To me the install is trying to do to much for me. Is there a way to say thanks, but let me have complete control over the installation. I will update the list if the bypass of slpd allows me to bring up the system. -Original Message- From: Michael MacIsaac [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 02, 2004 5:08 AM To: [EMAIL PROTECTED] Subject: Re: Installation of SLES9 hangs on 'creating initrd' Doug, After using these scripts my installation continues to hang on 'creating initrd' at 62%. Did I do something wrong? Hmm, if you got past the copying of the RPMs from the install tree to your new system, then I would guess the problem with creating the RAMdisk is not related to the install tree. How large of a virtual machine do you have? 256M or better for install - smaller than that may be an issue. Another thought is what type of network connection are you using? Most people are not running into this problem, so somehow your install might be adding different modules to the RAMdisk, which might be causing the problem. Also, what hardware are you using? Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061 -- 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: Installation of SLES9 hangs on 'creating initrd'
SLES9 for S/390 (31-bit) in an LPAR (no VM) using a shared IFL (I have one other LPAR running SLES8) Running a 2066-0A2 soon to upgrade to a 2066-002 on a temporary basis with 512M of memory. Using option 2 OSA Ethernet -Original Message- From: Michael MacIsaac [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 02, 2004 5:08 AM To: [EMAIL PROTECTED] Subject: Re: Installation of SLES9 hangs on 'creating initrd' Doug, After using these scripts my installation continues to hang on 'creating initrd' at 62%. Did I do something wrong? Hmm, if you got past the copying of the RPMs from the install tree to your new system, then I would guess the problem with creating the RAMdisk is not related to the install tree. How large of a virtual machine do you have? 256M or better for install - smaller than that may be an issue. Another thought is what type of network connection are you using? Most people are not running into this problem, so somehow your install might be adding different modules to the RAMdisk, which might be causing the problem. Also, what hardware are you using? Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061 -- 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: Installation of SLES9 hangs on 'creating initrd'
-Original Message- From: Michael MacIsaac [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 02, 2004 10:28 AM To: [EMAIL PROTECTED] Subject: Re: Installation of SLES9 hangs on 'creating initrd' Doug, Using option 2 OSA Ethernet What type of OSA card is it (OSA express Fast Ethernet)? Is the OSA defined as type OSD or type OSE? If it is type OSD which is more common for recent OSA cards, did you try using option 3? Actually the question may be moot, because you probably cannot use the qdio driver (for type=OSD OSAs) with a type=OSE CHPID (which uses the lcs.o driver). If this is the case, there may be a bug in installation process. Has anyone else installed SLES-9 successfully with option 2 and a type=OSE OSA CHPID? Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061 -- 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: Installation of SLES9 hangs on 'creating initrd'
The card is defined as type OSA-E according to the documentation available to me. -Original Message- From: Michael MacIsaac [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 02, 2004 10:28 AM To: [EMAIL PROTECTED] Subject: Re: Installation of SLES9 hangs on 'creating initrd' Doug, Using option 2 OSA Ethernet What type of OSA card is it (OSA express Fast Ethernet)? Is the OSA defined as type OSD or type OSE? If it is type OSD which is more common for recent OSA cards, did you try using option 3? Actually the question may be moot, because you probably cannot use the qdio driver (for type=OSD OSAs) with a type=OSE CHPID (which uses the lcs.o driver). If this is the case, there may be a bug in installation process. Has anyone else installed SLES-9 successfully with option 2 and a type=OSE OSA CHPID? Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061 -- 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
Installation of SLES9 hangs on 'creating initrd'
I searched the archives regarding subject of hangs on 'creating initrd'
and I did not find a resolution.
I took the script that Mike MacIsaac wrote and modified it to use the -e
parameter as noted in the e-mail thread. I have included my version of the
mkinstallroot script as well as the order and instorder files.
After using these scripts my installation continues to hang on 'creating
initrd' at 62%. Did I do something wrong?
Doug Clark
mkinstallroot:
# cat mkinstallroot
#--
##
# Written by:
# -Mike MacIsaac, IBM [EMAIL PROTECTED]
#
# F0r 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
#
#--
#
function mountCopy
# arg 1: the ISO image to mount
# arg 2: the directory to copy to
{
mount -o loop,ro $1 tmpCD
cd tmpCD
cp -a * ../installroot/$2
cd ..
umount tmpCD
}
# main()
# make the directory structure
mkdir installroot tmpCD
cd installroot/
mkdir sles9 core9 yast
cd sles9
mkdir CD1
cd ../core9/
mkdir CD1 CD2 CD3 CD4 CD5
cd ../..
# mount and copy the 6 CDs
mountCopy /var/ISO_Images/SLES-9-s390-RC5a-CD1.iso sles9/CD1/
mountCopy /var/ISO_Images/SLES-9-s390-RC5-CD2.iso core9/CD1/
mountCopy /var/ISO_Images/SLES-9-s390-RC5-CD3.iso core9/CD2/
mountCopy /var/ISO_Images/SLES-9-s390-RC5-CD4.iso core9/CD3/
mountCopy /var/ISO_Images/SLES-9-s390-RC5-CD5.iso core9/CD4/
mountCopy /var/ISO_Images/SLES-9-s390-RC5-CD6.iso core9/CD5/
rmdir tmpCD/
# make symbolic links
cd installroot
ln -s sles9/CD1/boot boot
ln -s sles9/CD1/content content
ln -s sles9/CD1/control.xml control.xml
ln -s sles9/CD1/media.1 media.1
echo -e /sles9/CD1 /sles9/CD1\n/core9/CD1 /core9/CD1 yast/instorder
echo -e /sles9/CD1 /sles9/CD1\n/core9/CD1 /core9/CD1 yast/order
--
instorder:
/sles9/CD1 /sles9/CD1
/core9/CD1 /core9/CD1
--
order:
/sles9/CD1 /sles9/CD1
/core9/CD1 /core9/CD1
--
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
SuSE 8 upgrade to SuSE 9
I upgraded to SuSE 8 shortly after installing version 7 and I was told that I had to do a new install to version 8. I don't care if that was/is true, but can someone tell me if there is an upgrade migration path from version 8 to version 9 and how effective is it? Doug -- 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
Bash script question
I have cut some lines of code out of a bash script I am trying to execute. snip T2=NONE T1=$_PAGESIZE if [ $T2 = $T1 ]; then snip I ran this using the -x option at the start of the script for debugging and it produced the following results. + T2=NONE + T1=NONE + '[' NONE = $'NONE\r' ']' Will someone please help me understand why the \r was appended to the if clause? And how can I change this code to make this a valid compare. If needed, I will be happy to provide more information. TIA Doug -- 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: Bash script question
The variable is valued using the following statement read _PRINTQ _PRTENBL _PRTURI _PRTDESC _BLDING _LOCDESC _PPDLOC _PAGESIZE The \r is not apart of the file being read. The file read has 8 fields and PAGESIZE is the last one. It seems to be that \r is a part of the carriage return / line-feed. As a work around, I appended another field to each record and I don't see the \r when I debug the script. It is now working as expected. Does this make sense? Also, if I simply echo $_PAGESIZE is does not display the \r -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Thursday, July 15, 2004 10:14 To: [EMAIL PROTECTED] Subject: Re: Bash script question It's not that \r was appended to the if clause, it is that the value of the _PAGESIZE variable is: 'NONE\r' as opposed to this: NONE\r How that variable gets that value assigned to it is unknown, since you don't show that section of the code. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, July 15, 2004 12:59 PM To: [EMAIL PROTECTED] Subject: Bash script question I have cut some lines of code out of a bash script I am trying to execute. snip T2=NONE T1=$_PAGESIZE if [ $T2 = $T1 ]; then snip I ran this using the -x option at the start of the script for debugging and it produced the following results. + T2=NONE + T1=NONE + '[' NONE = $'NONE\r' ']' Will someone please help me understand why the \r was appended to the if clause? And how can I change this code to make this a valid compare. If needed, I will be happy to provide more information. TIA Doug -- 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: Bash script question
It was originally created on a windows system. -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Thursday, July 15, 2004 11:00 To: [EMAIL PROTECTED] Subject: Re: Bash script question Tell me, was the file being read created on a Windows system, or a Linux/UNIX system? (I'm guessing Windows.) Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, July 15, 2004 1:50 PM To: [EMAIL PROTECTED] Subject: Re: Bash script question The variable is valued using the following statement read _PRINTQ _PRTENBL _PRTURI _PRTDESC _BLDING _LOCDESC _PPDLOC _PAGESIZE The \r is not apart of the file being read. The file read has 8 fields and PAGESIZE is the last one. It seems to be that \r is a part of the carriage return / line-feed. As a work around, I appended another field to each record and I don't see the \r when I debug the script. It is now working as expected. Does this make sense? Also, if I simply echo $_PAGESIZE is does not display the \r -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Thursday, July 15, 2004 10:14 To: [EMAIL PROTECTED] Subject: Re: Bash script question It's not that \r was appended to the if clause, it is that the value of the _PAGESIZE variable is: 'NONE\r' as opposed to this: NONE\r How that variable gets that value assigned to it is unknown, since you don't show that section of the code. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, July 15, 2004 12:59 PM To: [EMAIL PROTECTED] Subject: Bash script question I have cut some lines of code out of a bash script I am trying to execute. snip T2=NONE T1=$_PAGESIZE if [ $T2 = $T1 ]; then snip I ran this using the -x option at the start of the script for debugging and it produced the following results. + T2=NONE + T1=NONE + '[' NONE = $'NONE\r' ']' Will someone please help me understand why the \r was appended to the if clause? And how can I change this code to make this a valid compare. If needed, I will be happy to provide more information. TIA Doug -- 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 -- 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
Question using LVM; trying to extend current LVM managed volume g roup
I have an existing Linux system (non-VM) running SuSE Enterprise Server 8 in an LPAR using an IFL. My root file system and swap space are on unit 150e. I am using LVM to manage two other units 1611, and 1242 and I have /home, /var/and /opt filesystems mounted on volume group system in my /etc/fstab snip /dev/system/home/home reiserfs defaults 1 2 /dev/system/opt /optreiserfs defaults 1 2 /dev/system/var /varreiserfs defaults 1 2 snip I am trying to extend the logical volumes assigned to /var, /home/ and /opt to get more space I was assigned a drive unit by my storage administrator, and I made sure the unit was varied offline on all LPARs I use the 'echo add device range=113e /proc/dasd/device' command to assign another unit to my system The cat /proc/dasd/devices shows the unit available. I ran dasdfmt, dasdfmt, and mkreiserfs, to prepare the new drive I ran pvcreate /dev/dasdd1 sans quotes to create physical volume to LVM I ran vgextend -v system /dev/dasdd1 sans quotes to get the disk defined to LVM I ran lvextend /dev/system/opt +200 sans quotes to extend the file system (also ran it for /var and /home) I ran resize_reiserfs -f /dev/system/opt to resize the filesystem (also ran it for /var and /home) When I ran df -k everything looks great until I cycle Linux, Then I receive the following message on the HMC and I cannot continue Scanning for LVM volume groups... lvm-mp: allocating 42 lowmem entries at 01316000 LVM version 1.0.5+(mp-v6c)(22/07/2002) module loaded vgscan -- reading all physical volumes (this may take a while...) vgscan -- ERROR vg_read_with_pv_and_lv(): current PV can't get data of volume group system from physical volume(s) Unable to find swap-space signature vgscan -- /etc/lvmtab and /etc/lvmtab.d successfully created vgscan -- WARNING: This is program does not do a VGDA backup of your volume group Activating LVM volume groups... vgchange -- no volume groups found ..done Activating swap-devices in /etc/fstab... ..failed Checking file systems... fsck 1.28 (31-Aug-2002) /dev/dasda1: clean, 82746/840320 files, 395657/1679988 blocks fsck failed. Please repair manually and reboot. The root file system is currently mounted read-only. To remount it read-write do: bash# mount -n -o remount,rw / Attention: Only CONTROL-D will reboot the system in this maintenance mode. shutdown or reboot will not work. Give root password to login: I read and searched through documents, redpapers, and e-mails I could find dealing with LVM, but I can't the step I am missing. My attempts to run 'fsck' manually have not been successful. What I end up doing is doing a full image restore from backups I took before I tried to expand the filesystem and trying something else. Can someone point me in the right direction, or identify the step that I am missing. TIA -- 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: Question using LVM; trying to extend current LVM managed volu me g roup
That was it. I was really doing two steps. First, I was adding a new disk to the Linux system, which I failed to do properly. And two, I was extending an existing LVM managed filesystems which worked fine. I kind of feel like I asked tech support for help and the came by and plugged in my computer and said try it now! Thanks, -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Thursday, June 17, 2004 15:45 To: [EMAIL PROTECTED] Subject: Re: Question using LVM; trying to extend current LVM managed volu me g roup You didn't indicate that you updated your dasd= parameter in your parmfile and re-ran zipl. Take a look at this: http://linuxvm.org/info/howtos/mkinitrd-notes.html Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, June 17, 2004 6:19 PM To: [EMAIL PROTECTED] Subject: Question using LVM; trying to extend current LVM managed volume g roup I have an existing Linux system (non-VM) running SuSE Enterprise Server 8 in an LPAR using an IFL. My root file system and swap space are on unit 150e. I am using LVM to manage two other units 1611, and 1242 and I have /home, /var/and /opt filesystems mounted on volume group system in my /etc/fstab snip /dev/system/home/home reiserfs defaults 1 2 /dev/system/opt /optreiserfs defaults 1 2 /dev/system/var /varreiserfs defaults 1 2 snip I am trying to extend the logical volumes assigned to /var, /home/ and /opt to get more space I was assigned a drive unit by my storage administrator, and I made sure the unit was varied offline on all LPARs I use the 'echo add device range=113e /proc/dasd/device' command to assign another unit to my system The cat /proc/dasd/devices shows the unit available. I ran dasdfmt, dasdfmt, and mkreiserfs, to prepare the new drive I ran pvcreate /dev/dasdd1 sans quotes to create physical volume to LVM I ran vgextend -v system /dev/dasdd1 sans quotes to get the disk defined to LVM I ran lvextend /dev/system/opt +200 sans quotes to extend the file system (also ran it for /var and /home) I ran resize_reiserfs -f /dev/system/opt to resize the filesystem (also ran it for /var and /home) When I ran df -k everything looks great until I cycle Linux, Then I receive the following message on the HMC and I cannot continue Scanning for LVM volume groups... lvm-mp: allocating 42 lowmem entries at 01316000 LVM version 1.0.5+(mp-v6c)(22/07/2002) module loaded vgscan -- reading all physical volumes (this may take a while...) vgscan -- ERROR vg_read_with_pv_and_lv(): current PV can't get data of volume group system from physical volume(s) Unable to find swap-space signature vgscan -- /etc/lvmtab and /etc/lvmtab.d successfully created vgscan -- WARNING: This is program does not do a VGDA backup of your volume group Activating LVM volume groups... vgchange -- no volume groups found ..done Activating swap-devices in /etc/fstab... ..failed Checking file systems... fsck 1.28 (31-Aug-2002) /dev/dasda1: clean, 82746/840320 files, 395657/1679988 blocks fsck failed. Please repair manually and reboot. The root file system is currently mounted read-only. To remount it read-write do: bash# mount -n -o remount,rw / Attention: Only CONTROL-D will reboot the system in this maintenance mode. shutdown or reboot will not work. Give root password to login: I read and searched through documents, redpapers, and e-mails I could find dealing with LVM, but I can't the step I am missing. My attempts to run 'fsck' manually have not been successful. What I end up doing is doing a full image restore from backups I took before I tried to expand the filesystem and trying something else. Can someone point me in the right direction, or identify the step that I am missing. TIA -- 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: MQ on Linux - multiple ports for multiple receive channels?
I am still learning about Linux so I don't know for sure, but your Linux environment should have a unique IP Address. If that is the case, then you can use port 1414. For example, IP ADDRESS/port of 192.168.12.24 1414 should work where you substitute your actual IP address for 192.168.12.24. Otherwise, it is also common in MQSeries to have different ports (1414, 1415, 1416, etc.) when multiple queue managers are running on the same machine with the same IP Address. Just make sure that your connection definitions (i.e. Channels) on the distributed machines use the correct port number. Doug Clark -Original Message- From: Ranga Nathan [mailto:[EMAIL PROTECTED] Sent: Friday, April 30, 2004 06:18 To: [EMAIL PROTECTED] Subject: MQ on Linux - multiple ports for multiple receive channels? Anyone running MQ server on Linux LPAR / VM? From all I see, multiple MQ receive channels in our Linux LPAR requires different (listening) ports but our mainframe experts say that on the mainframe all receive channels are multiplexed through one port. MQ's default port is 1414. Oh, also can you recommend any open source or otherwise (if proprietary anything that is not bloat-ware) monitor for MQ so we can check the pulse and do some health check? I was thinking of rolling an Nagios plug-in using the nrpep client/server architecture. Thanks. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
