Re: Shared filesystems with SuSE SLES 8
On Fri, 22 Oct 2004 10:39:54 -0700, Robert Gresky <[EMAIL PROTECTED]> wrote: > I am trying to implement shared filesystems, so that multiple guests can > share one /bin and /sbin for example. I am using the redbook > SG24-6824-00 (Large Scale Linux Deployment) as a guide, but with mixed > success. I have used techniques like that to build an army of penguins to do benchmarks and measure scalabilty. But I find that in real life the Linux guests end up being less identical, and I expect you will see that your time is more valuable than the disk space that you can save with this. Software management is painful when only part of the code is shared and some is not (I understand that Levanta have addressed some of these issues and actually got this to work well). But I reserve the right to change my mind when we include z/VM DCSS support (i.e. xip2) in the picture. In that case you not only save disk space, but also reduce the footprint of the virtual machine. And that is good. -- Rob van der Heij rvdheij @ gmail.com -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES9 installation problem - again
On Saturday, 10/23/2004 at 08:48ZE10, Vic Cross <[EMAIL PROTECTED]> wrote: > Back to the IOCDS then: since we are really trying to work in LCS mode, > is OSE the correct CHPID type? Should it be OSA? >From Gadi's original post: CHPID PATH=(CSS(0),02),SHARED,* PARTITION=((LINTST,PROD,TEST),(=)),TYPE=OSE,* PCHID=141 CNTLUNIT CUNUMBR=1200,PATH=((CSS(0),02)),UNIT=OSA IODEVICE ADDRESS=(1200,253),CUNUMBR=(1200),UNIT=OSA IODEVICE ADDRESS=(12FE,1),CUNUMBR=(1200),UNIT=OSAD CHPID type is correctly set to OSE, indicating non-QDIO mode. TYPE=OSA was used only on the original OSA and OSA-2. The UNIT=OSA and UNIT=OSAD are also correct. From the IOCP book: UNIT=device specifies the device type. You specify a maximum of 8 alphanumeric or special (#, @, or $) characters to define the device type (such as, 3390 or 3590). IOCP only checks the syntax for alphanumeric or special characters. IOCP does not validate the device value except for devices assigned to OSA, OSD, or OSE channel paths. For OSA, OSD, and OSE channel paths, IOCP expects devices with unit addresses in the range 00-FD to have a value of OSA and the device with unit address FE to have a value of OSAD. The non-OSAs, the value of UNIT is meaningless to Linux and VM. After all these years, MVS still uses the field to carry I/O config information. And since IOCP already knows what the correct values are, it could generate them. But, again, it really isn't for IOCP's benefit. To recall Gadi's problem: The LCS driver was hanging during load. Now that all the distractions are past, hopefully someone will have some helpful advice! Alan Altmark -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES9 installation problem - again
On 22/10/2004, at 11:48 pm, Alan Altmark wrote: David, the 1000base-T feature can operate in QDIO or non-QDIO mode. The Gigabit Ethernet feature operates only in QDIO mode. Okay then... (we're all learning on this one :) Back to the IOCDS then: since we are really trying to work in LCS mode, is OSE the correct CHPID type? Should it be OSA? Cheers, Vic Cross PS: On Gigabit/1000BaseT -- it's disappointing that the industry chooses to use the generic term "Gigabit Ethernet" to refer to a specific implementation of Ethernet that operates at gigabit speed. Sigh... No wonder everyone believes networking to be so confusing ;) -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Very good - get it!
I found this on Slashdot. "The Register is running a very interesting article about Microsoft and Linux security. From the article: 'until now there has been no systematic and detailed effort to address Microsoft's major security bullet points in report form. In a new analysis published here, however, Nicholas Petreley sets out to correct this deficit, considering the claims one at a time in detail, and providing assessments backed by hard data. Petreley concludes that Microsoft's efforts to dispel Linux "myths" are based largely on faulty reasoning and overly narrow statistical analysis.' The full report is available here in HTML form, and here in PDF. Although the article does make mention of OS X, it would have been nice if the 'other' OS had been included in the detailed analysis for comparison." Get the report at http://www.theregister.co.uk/2004/10/22/security_report_windows_vs_linux .pdf -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Looking for X-windows server for TurboLinux
I have been running TurboLinux 6.5 on our z800 processor for the last 5 months. However I cannot seem to find a good XMCP based server.The X-windows server that came with the distribution seemed to work for a while but was very limited. I need to know if there is anything compatible that has good features. Any suggestions? Thanks in advance. Greg -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Setting up VMNFS
Look for the file RPIUVMX XASSEMBL on VMRMAINT's 176 disk this is the RACROUTE interface routine used by TCP/IP services to validate user ID's and passwords also the documentation for setting up these interfaces is included in the documentation, but I am having a hard time finding the reference right now. Larry Davis -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Wolfe, Gordon W Sent: Friday, October 22, 2004 13:24 PM To: [EMAIL PROTECTED] Subject: Setting up VMNFS This is cross-posted to both the VM-ESA list and the Linux-390 list. Sorry for the duplications. I have a number of apache webservers on several Linux servers that need to use various pieces of data that is also in use by a number of VM webservers using VM:Webgateway. This data is updated every few months. Rather than go around and update all the various locations, it would be most convenient if I could update it in one location on VM and just have all the other systems be able to use it. It seems that NFS would be the best solution. I looked at cmsfs, but I also need the occasional read-write capability. So I'm trying to set up VMNFS for the first time. It's considerably different than NFS on Linux. I'm having all kinds of problems with "permission denied". I'll want to serve out both minidisks and SFS data. I'd like to use VM:Secure as the ESM, but I can live with just using the CP directory entries. Could someone who has VMNFS working and accessible from Linux send me: 1. A copy of their VMNFS CONFIG file 2. A copy of the relevant parts of the DCTPARMS file for VMNFS 3. The syntax of the mount command you use from linux. What do you do about hard-coding the passwords in the mount command? 4. Anything else you think I'm missing? So one elephant says to another, "You'll never believe what happened last night. I was trying on Groucho Marx's pajamas--and he shot me!" Gordon Wolfe, Ph.D. (425)865-5940 VM Technical Services, The Boeing Company -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: CAN-2004-0887
Check the code drop of 2004-10-21. I think it may be related to this. Neale -Original Message- Can't find any info on this but it is mentioned here: http://www.ussg.iu.edu/hypermail/linux/kernel/0410.2/2264.html -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
CAN-2004-0887
Can't find any info on this but it is mentioned here: http://www.ussg.iu.edu/hypermail/linux/kernel/0410.2/2264.html Greg -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
RACF LDAP Authentication using PAM - options and pitfalls?
As I understand things, you can use PAM authentication in a couple of ways. You can have the RACF LDAP directory server authenticate a user ID and password, but keep the user information local to the Linux (Name, home dir, default shell, GID, UID etc) or if you have a sufficiently robust backing database (TDBM vs SDBM) you can have the LDAP server supply everything that the user ID would normally pick up from the security information on the individual linux, obviating the need for user account information /etc/passwd. I understand also, that the UID/GID numerics typically used in z/OS (RACF) might not work with Linux out of the box, and that you would have to make some adjustments to linux in order to have everything be handled by RACF via LDAP. Is it true then, that if you let all user information be supplied by LDAP that anyone with a valid unix segment defined to the RACF user ID would then be able to logon to Linux? Is it better to just have RACF LDAP handle the authentication of the password and keep the authorized users in the local /etc/passwd file, thus preventing just anyone from doing this? What are people's experiences in implementing PAM authentication? Pitfalls? Pros/Cons? This and an antivirus solution are the next items on my list. Thanks all, and have a good weekend. -J -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Setting up VMNFS
CA has an info APAR that describes the process on enabling VMNFS through VM Secure I will try to find it. Larry Davis -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Wolfe, Gordon W Sent: Friday, October 22, 2004 13:24 PM To: [EMAIL PROTECTED] Subject: Setting up VMNFS This is cross-posted to both the VM-ESA list and the Linux-390 list. Sorry for the duplications. I have a number of apache webservers on several Linux servers that need to use various pieces of data that is also in use by a number of VM webservers using VM:Webgateway. This data is updated every few months. Rather than go around and update all the various locations, it would be most convenient if I could update it in one location on VM and just have all the other systems be able to use it. It seems that NFS would be the best solution. I looked at cmsfs, but I also need the occasional read-write capability. So I'm trying to set up VMNFS for the first time. It's considerably different than NFS on Linux. I'm having all kinds of problems with "permission denied". I'll want to serve out both minidisks and SFS data. I'd like to use VM:Secure as the ESM, but I can live with just using the CP directory entries. Could someone who has VMNFS working and accessible from Linux send me: 1. A copy of their VMNFS CONFIG file 2. A copy of the relevant parts of the DCTPARMS file for VMNFS 3. The syntax of the mount command you use from linux. What do you do about hard-coding the passwords in the mount command? 4. Anything else you think I'm missing? So one elephant says to another, "You'll never believe what happened last night. I was trying on Groucho Marx's pajamas--and he shot me!" Gordon Wolfe, Ph.D. (425)865-5940 VM Technical Services, The Boeing Company -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Setting up VMNFS
For VMNFS CONFIG, we appear to be using an ancient default version. Here is our DTCPARMS: .* Network File System (NFS) daemon :nick.nfs :type.class :name.Network File System daemon :command.VMNFS :runtime.C :diskwarn.YES :anonymous.YES :ESM_Enable.YES :ESM_Validate.VALIDATE :ESM_Racroute.RPIDUMY INIT Note that this uses VM:Secure for password validation. Here is the mount command: (beware line wrap!) /bin/mount -t nfs server:/../VMBFS:filepool:filespace/,RW,userid=user,password=password /mnt I do not have a good answer for hard coding the password. I'm just living with it for the moment. -Original Message- From: Wolfe, Gordon W [mailto:[EMAIL PROTECTED] Sent: October 22, 2004 13:24 To: [EMAIL PROTECTED] Subject: Setting up VMNFS This is cross-posted to both the VM-ESA list and the Linux-390 list. Sorry for the duplications. I have a number of apache webservers on several Linux servers that need to use various pieces of data that is also in use by a number of VM webservers using VM:Webgateway. This data is updated every few months. Rather than go around and update all the various locations, it would be most convenient if I could update it in one location on VM and just have all the other systems be able to use it. It seems that NFS would be the best solution. I looked at cmsfs, but I also need the occasional read-write capability. So I'm trying to set up VMNFS for the first time. It's considerably different than NFS on Linux. I'm having all kinds of problems with "permission denied". I'll want to serve out both minidisks and SFS data. I'd like to use VM:Secure as the ESM, but I can live with just using the CP directory entries. Could someone who has VMNFS working and accessible from Linux send me: 1. A copy of their VMNFS CONFIG file 2. A copy of the relevant parts of the DCTPARMS file for VMNFS 3. The syntax of the mount command you use from linux. What do you do about hard-coding the passwords in the mount command? 4. Anything else you think I'm missing? So one elephant says to another, "You'll never believe what happened last night. I was trying on Groucho Marx's pajamas--and he shot me!" Gordon Wolfe, Ph.D. (425)865-5940 VM Technical Services, The Boeing Company -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 __ The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon, this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error, please contact the sender and delete the material from any computer. The integrity and security of this message cannot be guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail, or for the consequences of any actions taken on the basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Shared filesystems with SuSE SLES 8
I am trying to implement shared filesystems, so that multiple guests can share one /bin and /sbin for example. I am using the redbook SG24-6824-00 (Large Scale Linux Deployment) as a guide, but with mixed success. Does anyone have any experience and suggestions that they can share with me on setting this up? Thanks, Robert Gresky -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Setting up VMNFS
This is cross-posted to both the VM-ESA list and the Linux-390 list. Sorry for the duplications. I have a number of apache webservers on several Linux servers that need to use various pieces of data that is also in use by a number of VM webservers using VM:Webgateway. This data is updated every few months. Rather than go around and update all the various locations, it would be most convenient if I could update it in one location on VM and just have all the other systems be able to use it. It seems that NFS would be the best solution. I looked at cmsfs, but I also need the occasional read-write capability. So I'm trying to set up VMNFS for the first time. It's considerably different than NFS on Linux. I'm having all kinds of problems with "permission denied". I'll want to serve out both minidisks and SFS data. I'd like to use VM:Secure as the ESM, but I can live with just using the CP directory entries. Could someone who has VMNFS working and accessible from Linux send me: 1. A copy of their VMNFS CONFIG file 2. A copy of the relevant parts of the DCTPARMS file for VMNFS 3. The syntax of the mount command you use from linux. What do you do about hard-coding the passwords in the mount command? 4. Anything else you think I'm missing? So one elephant says to another, "You'll never believe what happened last night. I was trying on Groucho Marx's pajamas--and he shot me!" Gordon Wolfe, Ph.D. (425)865-5940 VM Technical Services, The Boeing Company -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: 1000Base T widget
On Friday, 10/22/2004 at 10:23 AST, David Boyes <[EMAIL PROTECTED]> wrote: > Curious question, then: given all the hoopla IBM's been spouting about how > much better QDIO is, etc etc, why does this new device speak LCS? Restoring > SNA support, or ??? Because it is a 10/100/1000 card, providing an alternative to the old 10/100 FENET card. Alan Altmark Sr. Software Engineer IBM z/VM Development -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: 1000Base T widget
> IIRC, the OP said "OSA Express 1000Base-T" and the shown IOCP included CSS > specifications. That's a z890/z990. OK, ok. Got it. Adminstering coffee now. Curious question, then: given all the hoopla IBM's been spouting about how much better QDIO is, etc etc, why does this new device speak LCS? Restoring SNA support, or ??? -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES9 installation problem - again
On Friday, 10/22/2004 at 10:05 AST, David Boyes <[EMAIL PROTECTED]> wrote: > > David, the 1000base-T feature can operate in QDIO or non-QDIO mode. The > > Gigabit Ethernet feature operates only in QDIO mode. > > OK, you're the boss. Previous messages indicated we were talking about > the old OSA Express cards (which have the above restriction) not a 890/990. IIRC, the OP said "OSA Express 1000Base-T" and the shown IOCP included CSS specifications. That's a z890/z990. Alan Altmark Sr. Software Engineer IBM z/VM Development -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES9 installation problem - again
On Fri, Oct 22, 2004 at 09:48:52AM -0400, Alan Altmark wrote: > > David, the 1000base-T feature can operate in QDIO or non-QDIO mode. The > Gigabit Ethernet feature operates only in QDIO mode. OK, you're the boss. Previous messages indicated we were talking about the old OSA Express cards (which have the above restriction) not a 890/990. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES9 installation problem - again
On Friday, 10/22/2004 at 09:42 AST, David Boyes <[EMAIL PROTECTED]> wrote: > 1000baseT *is* gigabit Ethernet -- look it up. If you mean *100*baseT, > then you might be right, but if it can be configured as LCS, then it > is NOT a 1000baseT card. > > Again, if it is a 1000baseT card, then it MUST be QDIO. If you want to > use LCS, then you cannot use that card. David, the 1000base-T feature can operate in QDIO or non-QDIO mode. The Gigabit Ethernet feature operates only in QDIO mode. Alan Altmark Sr. Software Engineer IBM z/VM Development -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES9 installation problem - again
On Fri, Oct 22, 2004 at 09:47:25AM +0200, ?? ?? wrote: > It's not a gigE. It's a 1000base-T. It can be configured as non-qdio. > Any other thaughts? > Gadi 1000baseT *is* gigabit Ethernet -- look it up. If you mean *100*baseT, then you might be right, but if it can be configured as LCS, then it is NOT a 1000baseT card. Again, if it is a 1000baseT card, then it MUST be QDIO. If you want to use LCS, then you cannot use that card. -- db -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES9 installation problem - again
On Friday, 10/22/2004 at 08:17 EST, Don Sievert <[EMAIL PROTECTED]> wrote: > Ethernet is IEEE standard 802.3, regardless of copper or fiber media. Everyone is missing the point: In addition to the fibre Gigabit Ethernet we all know and love, the z890 and z990 have a copper 1000Base-T feature. While "1000Base-T Ethernet" and "Gigabit Ethernet" might appear on the surface to be the same, they are not. This is consistent with the industry terminology. Alan Altmark Sr. Software Engineer IBM z/VM Development -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES9 installation problem - again
Ethernet is IEEE standard 802.3, regardless of copper or fiber media. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Ronald Van Der Laan Sent: Friday, October 22, 2004 6:24 AM To: [EMAIL PROTECTED] Subject: Re: SLES9 installation problem - again Linux on 390 Port <[EMAIL PROTECTED]> wrote on 22-10-2004 13:12:33: > Linux on 390 Port <[EMAIL PROTECTED]> írta 2004.10.22 09:47:25 > idopontban: > > > It's not a gigE. It's a 1000base-T. It can be configured as non-qdio. > > 1000 Base-T is not Gigabit Ethernet??? > > 10 Base-T = Ethernet (eth) > 100 Base-T = Fast Ethernet (FEth) > 1000 Base-T = Gigabit Ethernet (GEth),..,gigE,... > 1000Base-T uses electrons through copper to connect to 10Base-T, 100Base-T or 1000Base-T GbE uses photons through fiber to connect to a 1Gbs LAN. Ronald van der Laan -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES9 installation problem - again
Linux on 390 Port <[EMAIL PROTECTED]> wrote on 22-10-2004 13:12:33: > Linux on 390 Port <[EMAIL PROTECTED]> írta 2004.10.22 09:47:25 > időpontban: > > > It's not a gigE. It's a 1000base-T. It can be configured as non-qdio. > > 1000 Base-T is not Gigabit Ethernet??? > > 10 Base-T = Ethernet (eth) > 100 Base-T = Fast Ethernet (FEth) > 1000 Base-T = Gigabit Ethernet (GEth),..,gigE,... > 1000Base-T uses electrons through copper to connect to 10Base-T, 100Base-T or 1000Base-T GbE uses photons through fiber to connect to a 1Gbs LAN. Ronald van der Laan -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES9 installation problem - again
Linux on 390 Port <[EMAIL PROTECTED]> írta 2004.10.22 09:47:25 időpontban: > It's not a gigE. It's a 1000base-T. It can be configured as non-qdio. 1000 Base-T is not Gigabit Ethernet??? 10 Base-T = Ethernet (eth) 100 Base-T = Fast Ethernet (FEth) 1000 Base-T = Gigabit Ethernet (GEth),..,gigE,... ??? -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
2004-10-21 Recommended Linux for zSeries code drop to developerWorks
Please see the "What's new" page at: http://www10.software.ibm.com/developerworks/opensource/linux390/whatsnew.shtml Change summary: > "April 2004 stream": - kernel 2.6.5: Recommended kernel patch with bug fixes Happy downloading! * end of message Mit freundlichem Gruß / Kind regards, Gerhard Hiller eServer Software Management, D4357 IBM Development Lab, Boeblingen/Germany Phone ext. +49-(0)7031 - 16 - 4388 Internet: [EMAIL PROTECTED] -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES9 installation problem - again
It's not a gigE. It's a 1000base-T. It can be configured as non-qdio. Any other thaughts? Gadi -Original Message- From: David Boyes [mailto:[EMAIL PROTECTED] Sent: × 21/10/2004 22:03 To: [EMAIL PROTECTED] Cc: Subject: RE: SLES9 installation problem - again > When I chose option 3 I was asked for 3 devices. The devices > I gave (1200-1202) were not acceptable. > I don't want to use QDIO at this time. Non-qdio should be > supported according to evrything I've read. Not on the gigE cards. You don't have a choice -- if it's really a gigE card, then you must define it as a QDIO device and use QDIO. That's been the situation since the gigE cards were released. If you were using this card with the LCS driver on SLES8, it's not a gigE card. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
