Re: lx-390] RPM question
On Thu, 15 Mar 2007, Spann, Elizebeth (Betsie) wrote:
Is there a way to determine if both 31 bit and 64 bit versions of a
package are installed? RPM returns only one line.
For example,
[EMAIL PROTECTED] kernel]# rpm -qa | grep xorg-x11-depre
xorg-x11-deprecated-libs-6.8.2-1.EL.13.37.5
but the distribution lists
xorg-x11-deprecated-libs-6.8.2-1.EL.13.37.5.s390
xorg-x11-deprecated-libs-6.8.2-1.EL.13.37.5.s390x
sorry about the delay in responding
try: rpm -q --q '%{name}-%{version}-%{release}.%{arch}' \
xorg-x11-deprecated-libs
and you should get the same result, if both are installed.
'arch' and 'epoch' are 'silent' in the customary RPM -q query
option by design, as they are to some degree 'latecomer'
features; as such there is a large universe of scripting which
would get VERY confused by a format change there.
See generally the long time RPM site, relocated to:
http://www.oldrpm.org/
in light of recent changes in the hosting arrangements for the
RPM site.
-- Russ Herrold
--
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: getgroups for root
Arthur Ecock wrote: On Mar 20, 2007, at 2:22 PM, Rodriguez, Oscar wrote: I second that MQ should be run as mqm. Yes, I certainly agree. In this case, it's actually a WAS jmsserver instance that is trying to start the queue manager. Using sudo, we can get everything to start correctly, but there's still some confusion. If root is a member of multiple groups, and you issue an "id" command from an rc script during boot, shouldn't you see root's entire group membership? Why? root's not logged in. HOME isn't set either. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Please do not reply off-list -- 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
Fw: sles9 s390x install root
Here's the y2log when I tried with local directory. Yast appears to
complain of a number of missing files/locations. Anyone else see these
errors and are yet still able to install new packages?
2007-03-27 12:20:58 <1> zzlnx015(15461) [packagemanager]
InstSrcManager.cc(enableDefaultSources):915 Going to enable all default
InstSrc'es...
2007-03-27 12:20:58 <1> zzlnx015(15461) [packagemanager]
InstSrc.cc(enableSource):178 Enable InstSrc
InstSrc(<-1)(InstSrcDescr(<-2)(UnitedLinux:SUSE SLES-9- from
dir:///opt/sles9xsp3root/(/))|(NULL))
2007-03-27 12:20:58 <1> zzlnx015(15461) [Timecount++]
Timecount.cc(start):78 START Timecount(InstSrc::enableSource)
2007-03-27 12:20:58 <1> zzlnx015(15461) [packagemanager]
InstSrcDataUL.cc(tryGetData):299
InstSrcDataUL::tryGetData(/suse/setup/descr)
2007-03-27 12:20:58 <3> zzlnx015(15461) [packagemanager]
InstSrcDataUL.cc(initDataCache):572 Cannot access descr dir on media:
/opt/sles9xsp3root/suse/setup/descr{does not exist}
2007-03-27 12:20:58 <1> zzlnx015(15461) [packagemanager]
InstSrcDataUL.cc(tryGetData):329 (F)No cache. Use media
dir(dir:///opt/sles9xsp3root/ attached; localRoot "/opt/sles9xsp3root")
2007-03-27 12:20:58 <1> zzlnx015(15461) [packagemanager]
InstSrcData.cc(InstSrcData):56 New InstSrcData InstSrcData(<-0)((withdrawn
sel:0 pkg:0 you:0)
2007-03-27 12:20:58 <2> zzlnx015(15461) [mediaaccess]
MediaHandler.cc(provideFile):242 provideFile(/suse/setup/descr/packages):
ERROR(Media:file not found)
2007-03-27 12:20:58 <3> zzlnx015(15461) [packagemanager]
ULPackagesParser.cc(fromMediaDir):768 Media can't provide
'/suse/setup/descr/packages' : ERROR(Media:file not found)
2007-03-27 12:20:58 <2> zzlnx015(15461) [mediaaccess]
MediaHandler.cc(provideFile):242
provideFile(/suse/setup/descr/selections): ERROR(Media:file not found)
2007-03-27 12:20:58 <2> zzlnx015(15461) [mediaaccess]
MediaHandler.cc(dirInfo):365 dirInfo(/suse/setup/descr): ERROR(Media:not a
directory)
2007-03-27 12:20:58 <3> zzlnx015(15461) [packagemanager]
ULSelectionParser.cc(fromMediaDir):356 dirInfo failed for
'/suse/setup/descr' ERROR(Media:not a directory)
2007-03-27 12:20:58 <3> zzlnx015(15461) [packagemanager]
InstSrcDataUL.cc(tryGetData):371 tryGetData failed pkg: ERROR(Media:file
not found)
2007-03-27 12:20:58 <3> zzlnx015(15461) [packagemanager]
InstSrcDataUL.cc(tryGetData):372 tryGetData failed sel: ERROR(Media:not a
directory)
2007-03-27 12:20:58 <1> zzlnx015(15461) [packagemanager]
InstSrcData.cc(InstSrcData):69 Delete InstSrcData
InstSrcData(<-0)((withdrawn sel:0 pkg:0 you:0)
2007-03-27 12:20:58 <3> zzlnx015(15461) [packagemanager]
InstSrc.cc(enableSource):244 No InstSrcData type UnitedLinux found on
media dir:///opt/sles9xsp3root
Cheers
- Tex
Brendan Kelly
Certified Senior IT
Specialist - z/OS & Linux
Open Source Community of
Practice Co-Leader
IBM Global Technology
Services
348 Edward St, Brisbane, QLD
4000
+61-7-3213-2133
+61-419-394-143
[EMAIL PROTECTED]
- Forwarded by Brendan Kelly/Australia/IBM on 27/03/07 01:34 PM -
Brendan
Kelly/Australia/I
BM To
LINUX-390@VM.MARIST.EDU
26/03/07 09:13 PM cc
Subject
Re: Fw: sles9 s390x install root
(Document link: Brendan Kelly)
Still no luck - see below.
> I don't think the media are necessarily bad. I think the symbolic link
> you
> said you needed to add is causing the problem. On the git390 system, I
> compared the output you sent me to the directory structure on the NFS
> server used to build git390. The main differences I see (other than you
> not included the SRPM CDs) are this:
> 1. You have a sles9xsp3root/sp3-9/CD1/s390x/ and
> sles9xsp3root/sp3-9/CD2/s390x directory trees, which do not exist on "my"
> known working NFS server.
> 2. You have the symbolic link sles9xsp3root/suse -> core9/CD1/suse/
I removed all the ISOs and the old sles9xsp3root and started from scratch,
cut new ISOs downloaded to zLinux instance and ran vanilla mksles9root.sh
(sans my symlink). I then removed and readded the installation source in
yast. All I see now is currently installed software :-(
> I also noticed some "invalid userid or password" log entries when you
were
> trying to use your FTP source.
I have also tried NFS, HTTP and Local Directory - all with the same
results.
> The error you saw about 'SUSE LINUX Products GmbH != SuSE Linux AG' is
> because YOU is finding the wrong string in the media.3/media file it is
> looking at. You should have two of them with the following contents:
> core9/CD3/media.3/media:SuSE Linux AG
> core9/C
Re: getgroups for root
On Mar 20, 2007, at 2:22 PM, Rodriguez, Oscar wrote: I second that MQ should be run as mqm. Yes, I certainly agree. In this case, it's actually a WAS jmsserver instance that is trying to start the queue manager. Using sudo, we can get everything to start correctly, but there's still some confusion. If root is a member of multiple groups, and you issue an "id" command from an rc script during boot, shouldn't you see root's entire group membership? If I issue "id" from the 3215 console, I only see 1 group (root). If I issue "sudo id" from the 3215 console, I see the entire group membership for root. From a ssh session, "id" and "sudo id" both return then entire list (as expected). I've tried this without using mingetty. Same result. Very odd. Cheers, Arty -- 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: Pros/Cons of FCP connection DASD
On Mon, 26 Mar 2007 16:37:39 -0800 barton <[EMAIL PROTECTED]> wrote: > I don't understand - where would an installation with many linux servers get > SCSI I/O > information that identifies a device response time and shows delays > associated with that > I/O? I/O statistics are "nice", but how are they helpful? They tell you when you've got too much traffic on one bus, when your disk latency is becoming a problem and what volumes are affect and the like. Alan -- 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: Pros/Cons of FCP connection DASD
I don't understand - where would an installation with many linux servers get SCSI I/O information that identifies a device response time and shows delays associated with that I/O? I/O statistics are "nice", but how are they helpful? Ingo Adlung wrote: That's somewhat outdated information at least for SLES 9 & 10. We have Linux I/O statistics for FCP/SCSI and shortly we'll have FCP adapter I/O statistics, too. It is true that ECKD attached disks provide QoS features like end-to-end data protection and is the dominant I/O attachment for Linux. It is also true that customers would usually observe higher throughput with FCP attached storage. More performance related data to disk I/O is available at http://www-128.ibm.com/developerworks/linux/linux390/perf/index.html and more specific information for related to the DS8000 at http://www-128.ibm.com/developerworks/linux/linux390/perf/tuning_res_dasd_ds8000.html Best regards Ingo Linux on 390 Port wrote on 26.03.2007 22:38:21: When performance is bad, do you want to know why? Until we know how to show when the SAN is impacting your application and how - do you want to trust your production to something where performance is not manageable? For example, an ibm controller was benchmarked first as eckd, then as scsi. on eckd, we get cache stats - could show the dasd fast write filled up, and could show response time. for scsi, all we could show was thruput was degraded. we can't even measure silly response time numbers on scsi. Lionel B. Dyck wrote: I've heard several good reasons to have my zlinux images use dasd that is on the fibre connected san and a few for using the old tried and true dasd. What I'd like to find out is what is true and what isn't - basically what is considered the best practice for zlinux dasd. Thus - what do y'all think? Thanks in advance. Lionel B. Dyck, Consultant/Specialist zLinux Platform -- 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 begin:vcard note:If you can't measure it, I'm just not interested version:2.1 end:vcard
Re: Pros/Cons of FCP connection DASD
> Even this info. is dated. There are considerable differences > between the FCP firmware for Ficon Express 2 on Trex, and the > firmware for Ficon Express 2 on Danu. To translate: Trex = z990 and Danu = z9 EC Jim -- 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: Pros/Cons of FCP connection DASD
Linux on 390 Port wrote on 03/26/2007 04:52:17 PM: > That's somewhat outdated information at least for SLES 9 & 10. > We have Linux I/O statistics for FCP/SCSI and shortly we'll have > FCP adapter I/O statistics, too. > > It is true that ECKD attached disks provide QoS features like > end-to-end data protection and is the dominant I/O attachment > for Linux. It is also true that customers would usually observe > higher throughput with FCP attached storage. > > More performance related data to disk I/O is available at > > http://www-128.ibm.com/developerworks/linux/linux390/perf/index.html > > and more specific information for related to the DS8000 at > > http://www-128.ibm. > com/developerworks/linux/linux390/perf/tuning_res_dasd_ds8000.html Even this info. is dated. There are considerable differences between the FCP firmware for Ficon Express 2 on Trex, and the firmware for Ficon Express 2 on Danu. > Best regards > Ingo > > > Linux on 390 Port wrote on 26.03.2007 22:38:21: > > > When performance is bad, do you want to know why? Until we know how > > to show when the SAN > > is impacting your application and how - do you want to trust your > > production to something > > where performance is not manageable? > > For example, an ibm controller was benchmarked first as eckd, then > > as scsi. on eckd, we > > get cache stats - could show the dasd fast write filled up, and > > could show response time. > > for scsi, all we could show was thruput was degraded. we can't > > even measure silly > > response time numbers on scsi. > > > > > > Lionel B. Dyck wrote: > > > > > I've heard several good reasons to have my zlinux images use dasd that > is > > > on the fibre connected san and a few for using the old tried and true > > > dasd. What I'd like to find out is what is true and what isn't - > basically > > > what is considered the best practice for zlinux dasd. > > > > > > Thus - what do y'all think? > > > > > > Thanks in advance. > > > > > > Lionel B. Dyck, Consultant/Specialist zLinux Platform > > > Client and Platform Engineering Services (CAPES) > > > KP-IT Enterprise Engineering, Manager Toni Nicotera > > > 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] > > > AIM: lbdyck | Yahoo IM: lbdyck > > > Kaiser Service Credo: "Our cause is health. Our passion is service. > We?re > > > here to make lives better.? > > > > > > ?Never attribute to malice what can be caused by miscommunication.? > > > > > > NOTICE TO RECIPIENT: If you are not the intended recipient of this > e-mail, > > > you are prohibited from sharing, copying, or otherwise using or > disclosing > > > its contents. If you have received this e-mail in error, please notify > the > > > sender immediately by reply e-mail and permanently delete this e-mail > and > > > any attachments without reading, forwarding or saving them. Thank you. > > > > > > -- > > 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 > > [attachment "barton.vcf" deleted by Ingo Adlung/Germany/IBM] Ray Higgs System z FCP Development Bld. 706, B24 2455 South Road Poughkeepsie, NY 12601 (845) 435-8666, T/L 295-8666 [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: Pros/Cons of FCP connection DASD
That's somewhat outdated information at least for SLES 9 & 10. We have Linux I/O statistics for FCP/SCSI and shortly we'll have FCP adapter I/O statistics, too. It is true that ECKD attached disks provide QoS features like end-to-end data protection and is the dominant I/O attachment for Linux. It is also true that customers would usually observe higher throughput with FCP attached storage. More performance related data to disk I/O is available at http://www-128.ibm.com/developerworks/linux/linux390/perf/index.html and more specific information for related to the DS8000 at http://www-128.ibm.com/developerworks/linux/linux390/perf/tuning_res_dasd_ds8000.html Best regards Ingo Linux on 390 Port wrote on 26.03.2007 22:38:21: > When performance is bad, do you want to know why? Until we know how > to show when the SAN > is impacting your application and how - do you want to trust your > production to something > where performance is not manageable? > For example, an ibm controller was benchmarked first as eckd, then > as scsi. on eckd, we > get cache stats - could show the dasd fast write filled up, and > could show response time. > for scsi, all we could show was thruput was degraded. we can't > even measure silly > response time numbers on scsi. > > > Lionel B. Dyck wrote: > > > I've heard several good reasons to have my zlinux images use dasd that is > > on the fibre connected san and a few for using the old tried and true > > dasd. What I'd like to find out is what is true and what isn't - basically > > what is considered the best practice for zlinux dasd. > > > > Thus - what do y'all think? > > > > Thanks in advance. > > > > Lionel B. Dyck, Consultant/Specialist zLinux Platform > > Client and Platform Engineering Services (CAPES) > > KP-IT Enterprise Engineering, Manager Toni Nicotera > > 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] > > AIM: lbdyck | Yahoo IM: lbdyck > > Kaiser Service Credo: "Our cause is health. Our passion is service. We’re > > here to make lives better.” > > > > “Never attribute to malice what can be caused by miscommunication.” > > > > NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, > > you are prohibited from sharing, copying, or otherwise using or disclosing > > its contents. If you have received this e-mail in error, please notify the > > sender immediately by reply e-mail and permanently delete this e-mail and > > any attachments without reading, forwarding or saving them. Thank you. > > > -- > 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 > [attachment "barton.vcf" deleted by Ingo Adlung/Germany/IBM]
Re: Pros/Cons of FCP connection DASD
When performance is bad, do you want to know why? Until we know how to show when the SAN is impacting your application and how - do you want to trust your production to something where performance is not manageable? For example, an ibm controller was benchmarked first as eckd, then as scsi. on eckd, we get cache stats - could show the dasd fast write filled up, and could show response time. for scsi, all we could show was thruput was degraded. we can't even measure silly response time numbers on scsi. Lionel B. Dyck wrote: I've heard several good reasons to have my zlinux images use dasd that is on the fibre connected san and a few for using the old tried and true dasd. What I'd like to find out is what is true and what isn't - basically what is considered the best practice for zlinux dasd. Thus - what do y'all think? Thanks in advance. Lionel B. Dyck, Consultant/Specialist zLinux Platform Client and Platform Engineering Services (CAPES) KP-IT Enterprise Engineering, Manager Toni Nicotera 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: "Our cause is health. Our passion is service. We’re here to make lives better.” “Never attribute to malice what can be caused by miscommunication.” NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. -- 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 begin:vcard note:If you can't measure it, I'm just not interested version:2.1 end:vcard
Re: Pros/Cons of FCP connection DASD
Depending on the size of your shop, but money is a consideration in smaller shops. i.e. You already have ficon attached dasd with twin ficon cards. Now you need another pair of FCP cards (at how much per card), and FCP attached dasd (lparing your current DS6800 orr DS8000, or a separate dasd subsystem) and, what do you get? Slightly better performance (is the performance increase worth the cost?). Another set of underutilized channels (depending on the size of your shop and requirements) DASD that can't be universally used (some OS and older releases may not support FCP attached dasd) What else can you do with the money? Then, the other things that have already been mentioned, like lack of good performance monitors and detail compared to standard dasd subsystems. I assume that the SANs have their version of flashcopy and mirroring. In other words, if you need the performance, go for it. If you don't need the performance, then I'm not sure I would step up to it. In my setup, two years ago, we upgraded to an IBM z/890 with IBM DS6800. LPARing the DS6800 to a FCP side was a possibility. I rejected it due to the cost and little perceived benefit. Today, I would make the same decision here. However, at the next processor/dasd upgrade point, I would revisit the decision. But my gut feeling of our performance needs in the next two years, would steer me away from adding FCP, at this time. But, if the Open Systems group, wanted to replace their current SANs and I was offered additional disk space on it, I would consider adding the FCP ability instead of an upgrade to the DS6800. Just depends on how the cost numbers work out. End of ramble... The cost of supporting two different DASD subsystems (ficon and fcp) is a cost that has to be considered vs the cost of supporting a single, slightly lower performance ficon DASD Subsystem. Tom Duerbusch THD Consulting >>> "Lionel B. Dyck" <[EMAIL PROTECTED]> 3/26/2007 11:09 AM >>> I've heard several good reasons to have my zlinux images use dasd that is on the fibre connected san and a few for using the old tried and true dasd. What I'd like to find out is what is true and what isn't - basically what is considered the best practice for zlinux dasd. Thus - what do y'all think? Thanks in advance. Lionel B. Dyck, Consultant/Specialist zLinux Platform Client and Platform Engineering Services (CAPES) KP-IT Enterprise Engineering, Manager Toni Nicotera 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: "Our cause is health. Our passion is service. We*re here to make lives better.* *Never attribute to malice what can be caused by miscommunication.* NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. -- 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: Pros/Cons of FCP connection DASD
-Lionel B. Dyck wrote: - >I've heard several good reasons to have my zlinux images use dasd >that is on the fibre connected san and a few for using the old >tried and true dasd. What I'd like to find out is what is true and >what isn't - basically what is considered the best practice for >zlinux dasd. We have migrated a significant portion of our Linux disk space to FCP connections, and have been very pleased with the performance and with the ease of setting up very large file systems. I would note a few cautions: 1.We found that setting up FCP disk for the first time had a fairly formidable learning curve. The mail I see on this list suggests that our experience is not unusual. 2.We still have disks we have left on ECKD devices because our current hot site contract does not include FCP disk for the mainframe. Make sure your disaster recovery process can supply FCP disks, or that you can convert back to ECKD at the recovery site in an acceptable amount of time. 3.We have never tried to use an FCP disk as a boot device. I gather that the internals of the FCP boot process are considerably different than the internals of the traditonal mainframe boot process. I don't know how diffictult it is to set up the newboot process. -- 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: Pros/Cons of FCP connection DASD
>>> On Mon, Mar 26, 2007 at 12:09 PM, in message <[EMAIL PROTECTED]>, "Lionel B. Dyck" <[EMAIL PROTECTED]> wrote: > I've heard several good reasons to have my zlinux images use dasd that is > on the fibre connected san and a few for using the old tried and true > dasd. What I'd like to find out is what is true and what isn't - basically > what is considered the best practice for zlinux dasd. Lionel, this is really too broad of a question to answer well. At a very high level, SCSI disks are great for large volumes, a little harder to set up, give better performance (when things are working right), but the instrumentation for performance monitoring is nowhere near that for ECKD (when things aren't working right). Mark Post -- 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: Pros/Cons of FCP connection DASD
The biggest point in favor of the 3390 style DASD is that the 3990 (emulated) takes care of the mirroring and multipathing for me, where the FCP SAN disk is not mirrored or multipathed unless I do it myself in Linux. You may gain some file transfer speed, but you pay for it in CPU. -- .~.Robert P. Nix Mayo Foundation /V\RO-OC-1-13200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/26/07 11:09 AM, "Lionel B. Dyck" <[EMAIL PROTECTED]> wrote: > I've heard several good reasons to have my zlinux images use dasd that is > on the fibre connected san and a few for using the old tried and true > dasd. What I'd like to find out is what is true and what isn't - basically > what is considered the best practice for zlinux dasd. > > Thus - what do y'all think? > > Thanks in advance. -- 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: Pros/Cons of FCP connection DASD
Linux on 390 Port wrote on 03/26/2007 12:09:58 PM: > I've heard several good reasons to have my zlinux images use dasd that is > on the fibre connected san and a few for using the old tried and true > dasd. What I'd like to find out is what is true and what isn't - basically > what is considered the best practice for zlinux dasd. > > Thus - what do y'all think? > > Thanks in advance. > > Lionel B. Dyck, Consultant/Specialist zLinux Platform > Client and Platform Engineering Services (CAPES) > KP-IT Enterprise Engineering, Manager Toni Nicotera > 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] > AIM: lbdyck | Yahoo IM: lbdyck > Kaiser Service Credo: "Our cause is health. Our passion is service. We?re > here to make lives better.? > > ?Never attribute to malice what can be caused by miscommunication.? > > NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, > you are prohibited from sharing, copying, or otherwise using or disclosing > its contents. If you have received this e-mail in error, please notify the > sender immediately by reply e-mail and permanently delete this e-mail and > any attachments without reading, forwarding or saving them. Thank you. Lionel, There is some comparision info. here: http://www.linuxvm.org/Present/SHARE108/S9259cb.pdf Thanks, Ray Higgs System z FCP Development Bld. 706, B24 2455 South Road Poughkeepsie, NY 12601 (845) 435-8666, T/L 295-8666 [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: Pros/Cons of FCP connection DASD
In my view it depends on what you need: - a few very large disks, go for FCP FCP luns can't be suballocated (as far as I know), so wanting a lot of small ones won't give you any fun with the storage admin. - lots of small disks, go for old style ECKD LVMing lots of ECKD disks to get a large allocation is cumbersome. But it is no pain to get a lot of them. That's what the S390 boys have been doing for ages. Best regards, Pieter Harder [EMAIL PROTECTED] tel +31-73-6837133 / +31-6-47272537 >>> "Lionel B. Dyck" <[EMAIL PROTECTED]> 03/26/07 6:09 >>> I've heard several good reasons to have my zlinux images use dasd that is on the fibre connected san and a few for using the old tried and true dasd. What I'd like to find out is what is true and what isn't - basically what is considered the best practice for zlinux dasd. Thus - what do y'all think? Thanks in advance. Lionel B. Dyck, Consultant/Specialist zLinux Platform Client and Platform Engineering Services (CAPES) KP-IT Enterprise Engineering, Manager Toni Nicotera 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: "Our cause is health. Our passion is service. We’re here to make lives better.” “Never attribute to malice what can be caused by miscommunication.” NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. Brabant Water N.V. Postbus 1068 5200 BC 's-Hertogenbosch http://www.brabantwater.nl Handelsregister: 16005077 -- 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
Pros/Cons of FCP connection DASD
I've heard several good reasons to have my zlinux images use dasd that is on the fibre connected san and a few for using the old tried and true dasd. What I'd like to find out is what is true and what isn't - basically what is considered the best practice for zlinux dasd. Thus - what do y'all think? Thanks in advance. Lionel B. Dyck, Consultant/Specialist zLinux Platform Client and Platform Engineering Services (CAPES) KP-IT Enterprise Engineering, Manager Toni Nicotera 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: "Our cause is health. Our passion is service. We’re here to make lives better.” “Never attribute to malice what can be caused by miscommunication.” NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you.
Re: Surprise, Microsoft Listed as Most Secure OS
Depending on hardware the emulator, z/VSE will run there just fine. Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 3/23/2007 11:37 AM >>> Mark, Yes, but your laptop CAN run z/OS, z/VM and z/LinuxDon't know about z/VSE or z/TPF Glenn -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Friday, March 23, 2007 2:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Surprise, Microsoft Listed as Most Secure OS >>> On Fri, Mar 23, 2007 at 2:10 PM, in message <[EMAIL PROTECTED]>, "Chase, John" <[EMAIL PROTECTED]> wrote: >> - Original Message- >> From: Linux on 390 Port On Behalf Of Schneck.Glenn >> >> Wonder where z/Linux, z/VM and z/OS ranked. > > Oh, they aren't "widely- used operating systems". :- | By most criteria that people would employ, they truly aren't. Just because we know how great they can be doesn't mean there's an awful lot of them out there, compared to others. From our perspective the fact that there _has_ to be so many of them in the first place is part of the problem, but that doesn't change the facts. And besides, I would hate having to lug around a z9 BC when I go to conferences. My laptop running SLED10 is quite heavy enough. Which means that the skew in absolute numbers won't ever go away, regardless of the OSes involved. Mark Post -- 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 LEGAL DISCLAIMER The information transmitted is intended solely for the individual 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 action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. SunTrust and Seeing beyond money are federally registered service marks of SunTrust Banks, Inc. [ST:XCL] -- 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: Fw: sles9 s390x install root
>>> On Mon, Mar 26, 2007 at 7:13 AM, in message <[EMAIL PROTECTED]>, Brendan Kelly <[EMAIL PROTECTED]> wrote: > Still no luck - see below. > -snip- > I removed all the ISOs and the old sles9xsp3root and started from scratch, > cut new ISOs downloaded to zLinux instance and ran vanilla mksles9root.sh > (sans my symlink). I then removed and readded the installation source in > yast. All I see now is currently installed software :- ( I'm curious. What happens if you do a "yast -i packagename" from the command line, where packagename is something you don't already have installed? Mark Post -- 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: Fw: sles9 s390x install root
Still no luck - see below. > I don't think the media are necessarily bad. I think the symbolic link > you > said you needed to add is causing the problem. On the git390 system, I > compared the output you sent me to the directory structure on the NFS > server used to build git390. The main differences I see (other than you > not included the SRPM CDs) are this: > 1. You have a sles9xsp3root/sp3-9/CD1/s390x/ and > sles9xsp3root/sp3-9/CD2/s390x directory trees, which do not exist on "my" > known working NFS server. > 2. You have the symbolic link sles9xsp3root/suse -> core9/CD1/suse/ I removed all the ISOs and the old sles9xsp3root and started from scratch, cut new ISOs downloaded to zLinux instance and ran vanilla mksles9root.sh (sans my symlink). I then removed and readded the installation source in yast. All I see now is currently installed software :-( > I also noticed some "invalid userid or password" log entries when you were > trying to use your FTP source. I have also tried NFS, HTTP and Local Directory - all with the same results. > The error you saw about 'SUSE LINUX Products GmbH != SuSE Linux AG' is > because YOU is finding the wrong string in the media.3/media file it is > looking at. You should have two of them with the following contents: > core9/CD3/media.3/media:SuSE Linux AG > core9/CD3/media.3/media:20040702201752 > sp3-9/CD3/media.3/media:SUSE LINUX Products GmbH > sp3-9/CD3/media.3/media:20051214003614 > > Check yours to make sure they match that. They do. > I would do an "rm -rf" on sles9xsp3root/sp3-9/CD1/s390x and > sles9xsp3root/sp3-9/CD2/s390x just out of general principles. I would > also > remove the sles9xsp3root/suse symbolic link. It may also be worthwhile > deleting and re-adding your repository as an installation source. There > are some directories that get built down in > /var/adm/YaST/InstSrcManager/IS_CACHE_0x00something that should may need > be > cleaned up, but I'm not at all sure about that. > > To see if the CDs are bad, checking the md5 checksums as Mike indicated > would be a good idea: > for file in `find . -type f -name MD5SUMS` > do dir=`dirname $file` >pushd $dir >md5sum -c MD5SUMS >popd > done I used this (with a little mod to only show exceptions) - no invalid checksums. > Mark Post > > -- > 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
