Sorry, it was Hercules
Then you actually don't want to run KDE or Gnome
it will be very slow ;)
Cordialement / Vriendelijke Groeten / Best Regards / Med Vänliga Hälsningar
Tore Agblad
Volvo Information Technology
Infrastructure Mainframe Design Development
SE-405 08, Gothenburg
Actually, you don't want KDE or Gnome running in z.
That will be expensive. Depends on how you bill you CPU cycles :)
Cordialement / Vriendelijke Groeten / Best Regards / Med Vänliga Hälsningar
Tore Agblad
Volvo Information Technology
Infrastructure Mainframe Design Development
Mark,
Thanks, I think it is important to have as much as possible ported packages
to s390x even they are not supported by Novell and might be delived on an as
is base. I know from my work that we are always confronted with applications
that exists out in the Internet and suddently we have to
Dave,
you can try to setup a qeth device manually at your HMC console using
these steps:
1. Check with lscss, if the subchannel triplet (0.0., 0.0.xxxy,
0.0.xxxz) of your OSA-device is available.
2. Define the ccwgroup device with:
echo 0.0.,0.0.xxxy,0.0.xxxz
On Wed, Jul 22, 2009 at 10:19 AM, Ursula Braunubr...@linux.vnet.ibm.com wrote:
4. Activate the network interface:
ifconfig eth0 ip.ad.dr.es netmask aa.bb.cc.dd
Don't forget the default route if your PC is not on the same subnet as
the Linux guest (in most real world situations it is not)
On 7/22/09 5:05 AM, Agblad Tore tore.agb...@volvo.com wrote:
Actually, you don't want KDE or Gnome running in z.
That will be expensive. Depends on how you bill you CPU cycles :)
Like I said: you REALLY don't want to do this. You can, but it's just a
waste.
Here's what we do:
Currently, we have a DB2 Connect Server (Application Server Edition v9.5)
running on one of our SLES guests which we use as a gateway to each DB2
instance that we want to allow remote access to. If this is what you're
interested in, I recommend reading this:
Zach and Mark, thanks very much for your input.
Plenty to think about
Regards
Paul
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Zach Pratt
Sent: 22 July 2009 14:56
To: LINUX-390@VM.MARIST.EDU
Subject: Re: WMB and DB2 Connect on z/Linux
Hi All
We are in a similar situation as David, we were defining a new OSA with
layer2 support for CCL and have clobbered the network definitions for
normal access.
When I try ifup or ifdown the interfaces I get a message Network
interface is managed from NetworkManager etc etc as I am unable to
You might try: /etc/init.d/NetworkManager stop -- I'm surprised it's
running on the z -- that's usually something I use on my laptop to manage
switching between ethernet/wireless/etc.
Scott
On Wed, Jul 22, 2009 at 7:03 AM, Ceruti, Gerard G
gerard.cer...@standardbank.co.za wrote:
Hi
Hi Scott
Found it as well, it looks like we have messed up config files , will look
further tomorrow.
Regards
Gerard Ceruti
may the 'z' be with you
SharePoint (internal)
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Scott
Rohling
Sent: 22
Thanks Ursula,
I managed to get one of the connections back up and working.
The echo in step 2 failed with a message -bash: echo: write error: Invalid
argument. But I went ahead with step 3, echo 1 ... /online, and then step 4,
ifconfig eth0, and then added the default route as suggested
Ursula,
The config files you pointed out exist for both OSA ports. But I am not sure
what should be in them. Besides the ip address and netmask. I have pasted the
files for one of the OSA interfaces below. Sorry for my ignorance, but what am
I looking for? What should be in the config
On 7/22/2009 at 11:48 AM, David Stuart david.stu...@ventura.org wrote:
-snip-
Not being all that familiar with linux, or having the time to work with it
and really learn it, I have a tendency to use Yast(2). However, I apparently
shouldn't use Network Manager...
Absolutely. As it is
On 7/22/2009 at 12:22 PM, David Stuart david.stu...@ventura.org wrote:
Ursula,
The config files you pointed out exist for both OSA ports. But I am not
sure what should be in them. Besides the ip address and netmask. I have
pasted the files for one of the OSA interfaces below. Sorry
Hi Mark,
Yes, I did. After the problem originally occurred. Both OSA interfaces were
'dead'.
And I tried again after I reviewed the interface files after going through
Ursula's procedures. After reboot, both were 'dead' again. I had to go
through Ursula's procedures again to get it
On 7/22/2009 at 10:41 AM, Ceruti, Gerard G
gerard.cer...@standardbank.co.za
wrote:
Hi Scott
Found it as well, it looks like we have messed up config files , will look
further tomorrow.
I don't think your config files will be affected. After all, the main thing
Network Manager does is
On 7/22/2009 at 12:44 PM, David Stuart david.stu...@ventura.org wrote:
Hi Mark,
Yes, I did. After the problem originally occurred. Both OSA interfaces
were 'dead'.
Have you gone back into YaST to switch from Network Manager to traditional
mode?
Mark Post
Mark,
How do you switch back from Network Manager?
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
david.stu...@ventura.org
Mark Post mp...@novell.com 7/22/2009 9:54 AM
On 7/22/2009 at 10:41 AM, Ceruti, Gerard G
Mark,
I think so. Now when I go in to Yast, Network Devices, Network Card, it shows
Traditional Method with ifup as the management selection.
If I look at the interfaces through there, they look correct. However, I can
only seem to get one interface active at any given time. And it's not
On 7/22/2009 at 12:57 PM, David Stuart david.stu...@ventura.org wrote:
Mark,
How do you switch back from Network Manager?
YaST - Network Devices
The very first screen that comes up should be:
Network Setup Method
(x ) User Controlled with NetworkManager
( ) Traditional Method with ifup
21 matches
Mail list logo
