22.01.2004 21:10:11 Wolfe, Gordon W wrote:
Things that we or our users are finding essential, but which do not in
fact
exist in the marketplace yet are:
Virus-checking software for your Samba and e-mail Linux servers
Web single-signon software
Tivoli Access Manager (WebSeal, etc)?
Alex deVries wrote:
How about just using scp? It's much simpler.
e.g. on your ia32 Linux system, run:
scp file-to-transfer root@ip-address-of-instance:/tmp
Maybe I trimmed my earlier note too much, but the context is the SuSE
installation process. I have no idea how I'd try to convince the
23.01.2004 14:47:05 Nick Laflamme wrote:
Maybe I trimmed my earlier note too much, but the context is the SuSE
installation process. I have no idea how I'd try to convince the SLES
I think, you can't.
install process to use scp, and I doubt the scp daemon, if there is one,
is running on the
The OSA-2 must be defined as shared in HCD (iocds) and OSASF needs to
be run to setup the OAT for each LPAR that will access the OSA. You
will need to define the IP addresses and the device addresses for each
LPAR. You can use the same device addresses in each LPAR.
Be sure and define all of the
I use vsftpd all the time for installs/updates without any problem.
Neale
Hi,
Thanks for the responses. The problem with the SuSE 8 install turned out
to be a CD mount issue. The installation CD was mounted on a UNIX system,
but I believe it was not mounted with the correct options. The Unix
support person here talked to SuSE, and they had them remount the CD so
Our current NT SNA print servers are entering their end-of-life
cycle. These servers handle our current IMS/CICS SNA requirements out to
the field. If anyone has successfully done this port/migration I'd
appreciate hearing from them concerning the challenges of doing so. Thanks
in
One thing to check is if these printers also support LPR. If they do,
than the project would involve changing the SNA definitions to LPR
definitions. That might seem pretty simplistic and I'm sure there would
be more challenges (report formatting, spacing, etc), but in a nutshell
that's what
My Slackware system runs Proftpd, and has served up both RHEL and SLES
installs for my z/VM guests.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Nick Laflamme
Sent: Friday, January 23, 2004 7:47 AM
To: [EMAIL PROTECTED]
Subject: Re: SLES
Ferguson, Neale wrote:
I use vsftpd all the time for installs/updates without any problem.
Cool, we have a winner.
The firewall guy and I did a trace; the SLES installation process wasn't
recognizing responses it was getting from the BSD ftpd I was running.
Maybe if I'd looked longer and
to ease your migration (SNA-Print to IP-Printers or IP-Printservers) you
should use z/OS Infoprint Server (or OS/390 Infoprint Server). Using
this aproach there is no need to change any application or transaction
for a new (non-SNA) printer infrastructure - means use your IP-Printers
for any
Tom Butler wrote:
Our current NT SNA print servers are entering their end-of-life
cycle. These servers handle our current IMS/CICS SNA requirements out to
the field. If anyone has successfully done this port/migration I'd
appreciate hearing from them concerning the challenges of
Hi folks,
I've been running into a problem every so often that I can't track down and
thought I'd just throw it out here to see if I get any bites.
I have 2 Gbit OSAs that I share among my guests and use VIPA to provide
failover in case one goes down. So, every guest has an eth0, eth1, and an
Well don't have an answer for you but have seen an other weird linux osa
situation.
Client presents me with a linux image with two osa cards at eth0 and eth1.
eth0 172.27.194.153
eth1 172.27.94.153
eth1:1 172.27.88.51
eth1:2 172.27.88.52
eth1:3 172.27.8853
Eth1:3 are according to client VIPA's.
Hmm. I see the problem at the workstation. Poke around for a bit and
notice that eth1 is not aliased in
modules.conf. Add an alias to modules.conf for eth1 and the
problem goes
away. Cannot be recreated.
... so it' s fixed ... no ... we remove the update to modules.conf and
cannot
Hi all
I want to use an userall aliases only for a special user . Meanwhile I
want only this user can use this aliase to send e-mail for all and
nobody can use this aliase for some reasons. What must i do ?
-- sophia
__
Inflex - installed on mailserver for
16 matches
Mail list logo
