http://www-128.ibm.com/developerworks/linux/linux390/april2004_technical.html
Software requirements
If you are using Linux as a VM-guest, z/VM Version 4 Release 4
or higher is required
On Tuesday, 06/21/2005 at 03:58 ZE2, Thomas Broman
[EMAIL PROTECTED]
Has anyone tried adding FCP tapes to linux. I was able to add FCP dasd
to Suse v8 and I'm in the process of adding them to Suse v9, but I'm
getting nothing but error messages when I try to add an FCP tape device
to either system. I suspect, but I'm not sure, that I've probably got a
problem
I was thinking that putting /tmp on a vdisk like we do with swap would be
better than lvm or a separate minidisk. What are the advantages of having /tmp
on real dasd?
/Tom Kern
--- Post, Mark K [EMAIL PROTECTED] wrote:
I build all my systems with /tmp separate from /. That goes for Linux/390
No zVM spoken here. We are only LPAR at this junction and zVM is is our
2006 budget (training, sys. prog., the entire 9 yards).
Regards,
[EMAIL PROTECTED]
NCCI
Boca Raton, Florida
561.893.2415
greetings / avec mes meilleures salutations / Cordialmente
mit freundlichen Grüßen / Med vänlig
Except that some piece of assinine software we had for HPUX installed it's
license key in /tmp. I wanted to reboot and not guarantee the contents of
that company.
-Original Message-
From: Post, Mark K [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 21, 2005 11:34 PM
To:
Hi All,
We are in the midst of installing a VM guested SuSE SLES9 on our z800 system
and are having trouble getting SWAT to work. We can map drives to our
network so we know that Samba is running. We've set a LISTEN directive to
port 901 and verified that there is a swat901/tcp entry in the
What do you mean by verified that there is a swat? Did you try 'netstat
-l' to make sure that swat is listening? Did you bounce inetd/xinetd
(KILL -HUP)? Is inetd/xinetd even running?
Campbell, Breck wrote:
Hi All,
We are in the midst of installing a VM guested SuSE SLES9 on our z800 system
Breck,
If I remember right, when I did some testing with sles9 SAMBA,
I found that SWAT is listening on the loopback port 127.0.0.1 by default.
Regards,
John
--
For LINUX-390 subscribe / signoff / archive access
Breck,
I believe SWAT is normally invoked via xinetd. First you have to modify
the swat inetd config file:
# cat /etc/xinetd.d/swat
# SWAT is the Samba Web Administration Tool.
service swat
{
socket_type = stream
protocol= tcp
wait= no
And how does one change it to listen on the network interface port?
[EMAIL PROTECTED] 06/22/05 02:39PM
Breck,
If I remember right, when I did some testing with sles9 SAMBA,
I found that SWAT is listening on the loopback port 127.0.0.1 by default.
Regards,
John
Greetings all,
We've just done an install of a golden image of SLES9 almost completely
by the From LPAR to Virtual Servers in Two Days book. The only
difference is, in our case, we included the C/C++ compiler and tools
packages in the install. Of course, this installed a lot of RPMs, some
of
Greetings;
I started to upgrade Debian and everything was going along fine
when it tried to install and activate Appletalk or some such thing
and couldn't do it. So, it just quit!
Seems to be an , shall we say inconvenient thing to do! That
doesn't sound like a terminal error to me!
But the
I will be out of the office starting 06/22/2005 and will not return until
06/28/2005.
I will be out of the office on vacation June 23 - 27. I will have no email
access. Please contact my backup Rey Armijo for assistance while I am gone
13 matches
Mail list logo
