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
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 a
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 wit
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 us
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
conso
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-ma
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
mysq
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
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 an
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 FO
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
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
def
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 s
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
T
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:[
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
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/
The output from running a mkinitrd command contained the following message
Make sure to add 'dasd=' 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
--
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 th
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
Was there a change in the sdb.suse.de download site for updates that I
missed? I can't seem to get access to download updates that I had last
week.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to
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
Can someone
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
#
I don't remember. The dates on the file show 11/04/2004.
-Original Message-
From: Tom Duerbusch [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 13, 2005 7:54 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Suse 9.0 CD Validation
So when did you download your s390 version?
I just download
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 ra
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 inf
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 t
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 sho
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
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 P
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:
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
im
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
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=" >>
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.M
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
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?
-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 1
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,
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]
Subje
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
>
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
Format
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]
>
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 o
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, Decembe
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
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-pl
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 logic
Yes - always hangs in the same place (31 bit or 64 bit) -- I bypassed by
proactively selecting which packages to use at install time and kept the slp
server from being installed. Everything came up (31 bit mode) just fine. I
will try the 64 bit mode next week.
-Original Message-
From:
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
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,
> Usi
-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)? I
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
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
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
--
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?
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
I have cut some lines of code out of a bash script I am trying to execute.
T2="NONE"
T1=$_PAGESIZE
if [ "$T2" = "$T1" ]; then
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 so
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 comput
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/fs
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.
Othe
61 matches
Mail list logo
