I just used the YAST2 Online update tool to install the latest patches on
our instances running WAS. After the install I discovered Websphere
wouldn't start.
After some newsgroup searching I found that the problem was due to the fact
that localhost resolved to 127.0.0.1 instead of the external
in /etc/rc.config
#
# SuSEconfig can do some checks and modifications in /etc/hosts.
# If this is not wanted, set the following variable to 'no' (yes/no).
#
CHECK_ETC_HOSTS=no
WBR, Sergey
Marist EDU [EMAIL PROTECTED]
Sent by: Linux on 390 Port [EMAIL PROTECTED]
27.10.2003 15:36
I just used the YAST2 Online update tool to install the
latest patches on
our instances running WAS. After the install I discovered Websphere
wouldn't start.
After some newsgroup searching I found that the problem was
due to the fact
that localhost resolved to 127.0.0.1 instead of the
Hi,
We're installing a 3494 library with 3590-E1A drives on Sles8 on Z900
(VM) . We can see our drives with IBMtapeutil (display on tape drives work)
but we are unable to see the library plugged via ethernet (IP address is
set within ibmatl.conf). Doing an IBMtapeconfig command produce :
Everyone noticed that MS dropped support for Linux, BSD, Netware, and
Solaris from the new beta of what used to be the Connectix product,
right?
http://www.msfn.org/comments.php?id=5516catid=1
Adam
Adam,
From the link you provided I see that it is dropped from the Wizzard but
do you know if you can select other (see the screen shoot:
http://www.msfn.org/uploads/Screenshots/vpc2004_beta/os.png ) and still get
these supported?
-Dale
At 11:05 AM 2003_10_27, you wrote:
Everyone noticed that MS
Well we cycled VM for the cdt/cst time change and so far this morning all my
SLES8 guests run just fine. I'm not sure why my guests were dropping or why
an IPL fixed everything but we appear to be good to go. I will repost this
in the future if the problem recurs or if I find a possible cause of
This is exactly what we've been seeing. We have recommendations and trace requests
from IBM, we're just waiting for it to happen again. At the moment, all we know is
there are some odd things going
on in the qdio driver, but it often affects multiple Linux instances at the same time.
-Original Message-
From: Adam Thornton [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 10:06 AM
To: [EMAIL PROTECTED]
Subject: Connectix--now MS--Virtual PC drops guest OS support
Everyone noticed that MS dropped support for Linux, BSD, Netware, and
Solaris from the new
Any one have luck trying to use the llc_ui support on 2.4.19 kernel from the
patch-2.4.19-ac4
Seems like when I try to connect to a remote sap it causes the kernel to loop or when
i get a SABME from the other direction it cause the kernel to loop
Any thoughts?
On Mon, Oct 27, 2003 at 10:05:46AM -0600, Adam Thornton wrote:
Date: Mon, 27 Oct 2003 10:05:46 -0600
From: Adam Thornton [EMAIL PROTECTED]
Subject: Connectix--now MS--Virtual PC drops guest OS support
To: [EMAIL PROTECTED]
Everyone noticed that MS dropped support for Linux, BSD, Netware, and
On Mon, Oct 27, 2003 at 10:05:46AM -0600, Adam Thornton wrote:
Everyone noticed that MS dropped support for Linux, BSD, Netware, and
Solaris from the new beta of what used to be the Connectix product,
right?
http://www.msfn.org/comments.php?id=5516catid=1
The other thing that caught my eye
Hello. I'm having a problem getting connected to a linux image.
Everything seems to go ok during the boot and subsequent config. ok as
in no error messages. I'm running a z800, z/VM 4.3.0, OSA-Express Gig.
addresses E100 - E102. These addresses are attached the linux guest,
LNXRH01. When I
If so, what DB do you use?
Thanks much,
Leland
CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may
contain confidential and privileged information for the use of the
designated recipients named above. Any unauthorized review, use, disclosure
or distribution is prohibited.
The doc shows qeth0 (or 1 or 2, etc). I can try with eth0.
modprobe qeth returns nothing, no errors, no anything, just another
bash prompt.
However, I'm confused. IIRC, comments on this list indicate that the
qeth/qdio modules are not in RH. But when I enter qeth0 during the
config, RH doesn't
On Monday, 10/27/2003 at 02:56 CST, Adam Thornton
[EMAIL PROTECTED] wrote:
On Mon, 2003-10-27 at 14:50, Steve Gentry wrote:
qeth0,0xe100,0xe101,0xe102
Should be eth0, not qeth0, I think. But I'm not sure about that.
qeth0 is correct. For OSA, it is the *device* name, not the *interface*
On Mon, 27 Oct 2003, Steve Gentry wrote:
However, I'm confused. IIRC, comments on this list indicate that the
qeth/qdio modules are not in RH. But when I enter qeth0 during the
config, RH doesn't fuss.
Strange that it does not complain... By default the modules are not in
the installation
Hi All,
I have been ask a pretty cryptic question so here goes.
To start with I have No real idea what Forte is? Nor were my web searches
very enlightening.
I thought it was some type of development coding platform that appears to
have now been swallowed up in the Sun One Studio IDE.
I have heard
On Monday 27 October 2003 16:05, you wrote:
The doc shows qeth0 (or 1 or 2, etc). I can try with eth0.
modprobe qeth returns nothing, no errors, no anything, just another
bash prompt.
That's because the installation script is squelching all the error messages
you might see. Unfortunately,
19 matches
Mail list logo
