For printer name try port1, port2 or port3, or parallel1, 2 or 3. raw1, 2 or
3 may work as well.
On Wednesday 06 November 2002 07:09 pm, Doug Clark wrote:
> Does anyone have experience with configuration of a printer connected to
> the network through HP JetDirect 500x devices? There are three D
You use different remote printer queue names to differentiate the ports.
The print server supports 3 basic names: 'raw', 'text', and 'auto' (raw
takes, well raw formatted output for the printer, text is for text files,
and auto automatically switches between text and raw as necesary). . You
indica
Does anyone have experience with configuration of a printer connected to the
network through HP JetDirect 500x devices? There are three DB25 ports
(parallel ports ) on the back of the JetDirect device and I need to be able
to specify which one of the three connected printer to use. I have the IP
On Wed, Nov 06, 2002 at 09:07:07PM -0500, David Boyes wrote:
> > Does Red Hat include the OCO modules for QDIO on an OSA? Thanks.
> > Kyle Stewart
> > The Kroger Co.
> No.
However, IBM does supply the modules built for RH, and they also have a
procedure for building a new initrd with those module
> Does Red Hat include the OCO modules for QDIO on an OSA? Thanks.
> Kyle Stewart
> The Kroger Co.
No.
-- db
Does Red Hat include the OCO modules for QDIO on an OSA? Thanks.
Kyle Stewart
The Kroger Co.
[EMAIL PROTECTED]
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@;VM.MARIST.EDU]On Behalf Of
Crowley, Glen L
Sent: Wednesday, November 06, 2002 12:38 PM
To: [EMAIL PROTECTED]
Subjec
I already did, and got the same error. Just FYI, it compiles just fine on
my Intel Linux system, also gcc 2.95.3, but with glibc 2.2.5.
Mark Post
-Original Message-
From: Jochen Röhrig [mailto:jr@;debian.org]
Sent: Wednesday, November 06, 2002 4:53 PM
To: [EMAIL PROTECTED]
Subject: Re: C
Mark Post wrote:
>I'm trying to compile gdb 5.2 [...]
Please don't; use gdb 5.2.1 instead (ideally with the developerWorks patch).
gdb 5.2 is known not to build out-of-the-box on s390.
Bye,
Ulrich
--
Dr. Ulrich Weigand
[EMAIL PROTECTED]
Robert,
/dev/dasda1 refers to the first partition on dev/dasda. You will need to 'fdasd'
and 'mke2fs' for /dev/dasda1 If this is a SuSE install, when you first logon you
should be presented with a screen that explains how to issue the insmod command and
how to format the dasd prior to begi
On Wed, Nov 06, 2002 at 04:15:52PM -0500, Post, Mark K wrote:
> I'm trying to compile gdb 5.2 with gcc 2.95.3, glibc 2.1.3, and I'm getting
> the following error:
There are known problems with compiling gdb 5.2 on Linux/390 which
should be fixed in gdb 5.2.1. Maybe hust give it a try ...
Jochen R
I'm trying to compile gdb 5.2 with gcc 2.95.3, glibc 2.1.3, and I'm getting
the following error:
gcc -c -g -O2-I. -I. -I./config -DHAVE_CONFIG_H -I./../include/opcode
-I./../readline/.. -I../bfd -I./../bfd -I./../include -I../intl -I./../intl
-DMI_OUT=1 -DUI_OUT=1 -Wimplicit -Wreturn-type -Wco
Thanks I thought I could change in one place in YaST, but it did not update
the conf file.
Larry
-Original Message-
From: Post, Mark K [mailto:mark.post@;eds.com]
Sent: Wednesday, November 06, 2002 15:31
To: [EMAIL PROTECTED]
Subject: Re: OSA express gb adapter
Larry,
Hopefully /etc/ch
Larry,
Hopefully /etc/chandev.conf
Mark Post
-Original Message-
From: Davis, Lawrence [mailto:DavisLA@;tvratings.com]
Sent: Wednesday, November 06, 2002 3:20 PM
To: [EMAIL PROTECTED]
Subject: Re: OSA express gb adapter
Where would I find the qeth parms below on a SuSE 2.4 Kernel Distri
Where would I find the qeth parms below on a SuSE 2.4 Kernel Distribution.
Larry
-Original Message-
From: Sanford H Gelbard [mailto:sgelbard@;CSC.COM]
Sent: Wednesday, November 06, 2002 10:42
To: [EMAIL PROTECTED]
Subject: Re: OSA express gb adapter
I specified the following to work onc
Thanks to those who replied to my message. Apparently, if you don't reply
with the portname in upper case the first time thru the questions, it does
not matter on the 2nd trip thru. If I enter the portname in upper case the
first time thru, all works ok.
Thanks
Glen
I have an LPAR that shares a
Hi,
The IDX TERMINATE with cause code 0x22 is probably the result of a
mismatch between your configured portname (OSA1) and the current
portname assigned by someone already using the adapter.
The portname IS case-sensitive, and since the configuration files on some
platforms will convert to upper
I specified the following to work once I migrated to driver 38 on my Z :
qeth parms noauto,0x350,0x351,0x352,portname:OSA350,eth0
I found my correct portname by using the HMC option Advanced facilities
"View Port Parameters"
SG
"Crowley,
Glen L"
We've tried compiling using this compiler but still received a number of
errors due to the new features of Fortran95 being utilized in the module.
Any other ideas???
-Original Message-
From: Alan Cox [mailto:alan@;lxorguk.ukuu.org.uk]
Sent: Tuesday, November 05, 2002 2:55 PM
To: [EMAIL PR
Robert,
If this is a 2.4 system, fdasd must be used to create at least one partition
on the target volumes before running mke2fs.
Mark Post
-Original Message-
From: Nix, Robert P. [mailto:Nix.Robert@;mayo.edu]
Sent: Wednesday, November 06, 2002 11:25 AM
To: [EMAIL PROTECTED]
Subject: SuS
Try the following when it asks for the device address:
noauto,qeth0,0xc40,0xc41,0xc42;add_parms,0x10,0xc40-0xc41,portname:OSA1
Also you may want to query the card thru the HMC to see what it thinks the
portname is.
James Johnson Email: [EMAIL PROTECTED]
Systems P
This should be dirt simple, and I've already done it several times, so I'm not really
understanding what I've done wrong here, but...
I wanted to build a new Linux/390 image. I created the new userid, loaded up the ram
image, went through defining the network and logged into root via telnet. I r
I have tried using the "Auto" detect feature, and got stung big
time... when the system goes down the machine that you used
"Auto" will grab the FIRST PORT AVAILABLE, so it can make your other
systems go bonkers with IP access since the device that they expect
to acquire is now taken !!
use
OSA1 is what is defined in the VTAM TRLE and caps does not make a
difference.
Glen
-Original Message-
From: Mark Kliner [mailto:MarkK@;VSP.com]
Sent: Wednesday, November 06, 2002 9:37 AM
To: [EMAIL PROTECTED]
Subject: Re: OSA express gb adapter
Is that indeed the same portname defined i
Upper and lower case gets the same result, also I have used specific device
addresses as well as auto.
Thanks
Glen
-Original Message-
From: Malcolm Beattie [mailto:mbeattie@;clueful.co.uk]
Sent: Wednesday, November 06, 2002 9:35 AM
To: [EMAIL PROTECTED]
Subject: Re: OSA express gb adapter
Crowley, Glen L writes:
> I have an LPAR that shares a gb ethernet osa express adapter with OS/390
> LPAR's. I am using SUSE distribution as it is the only one that I found
> that includes the OCO modules. I get the error that follows when setting up
> my network definition. I have on ocasion be
Is that indeed the same portname defined in the VTAM TRLE setup under
OS/390?
Does it need to be specified as upper-case?
Mark Kliner
Systems Programmer
Vision Service Plan
Rancho Cordova, CA
-Original Message-
From: Crowley, Glen L [mailto:GLCROWLEY@;arkbluecross.com]
Sent: Wednesday,
I have an LPAR that shares a gb ethernet osa express adapter with OS/390
LPAR's. I am using SUSE distribution as it is the only one that I found
that includes the OCO modules. I get the error that follows when setting up
my network definition. I have on ocasion be able to get this to work, but
9
Moloko:
What level of VM TCP/IP are you running? APAR PQ41584 addressed this
problem, but that was in TCP/IP FL 310 and FL 320 and is part of the
base of VM TCP/IP in z/VM V4.
Romney
On Wed, 6 Nov 2002 09:34:48 +0200 Moloko Monyepao said:
>I am running the following Redhat 7.2 kernel under VM 4.
On Wed, 2002-11-06 at 02:36, John Summerfield wrote:
> BTW IA32 has four protection levels enforced in hardware. I believe the
> problem is that Linux doesn't use them all.
x86 has 2 or 4 depending on where you look. Some of the levels really
exist as back compatibility segmentation stuff only. Mo
"Gowans, Chuck" <[EMAIL PROTECTED] wrote:
>
> Hello All,
>
> I need to port a Fortran module from a non-390 Linux platform to our
> Linux-On-390 platform. This module has been coded in Fortran95 using a
> number of the new functions/features available in Fortran95.
>
> I am aware of the g77 Fortra
30 matches
Mail list logo
