Re: Using dasd_configure in SLES11 SP2
On 2/13/2013 6:56 PM, Leland Lucius wrote:
On 2/13/2013 10:07 AM, Peter Oberparleiter wrote:
On 13.02.2013 00:38, Leland Lucius wrote:
Create the following file and remove all of your existing
51-dasd*.rules.
cat /etc/udev/rules.d/51-dasd.rules
# Rule to add all eckd devices
ACTION=="add", SUBSYSTEM=="ccw", DRIVER=="dasd-eckd", ATTR{online}="1"
Note that adding kernel/module parameter dasd=autodetect should achieve
the same result.
That's really weird. We always specify dasd=autodetect. I even just
double checked to make sure. All of the disks are certainly detected,
they just don't come up online.
But, you've got me curious, so I'm going to modify an initrd and see if
the devices are online prior to any initrd processing. Mayhap something
in boot is putting them offline before udev is getting his mitts on 'em.
Probably not, but I just HAVE to know. :-)
Definitely detected but offline no matter if I specify dasd=autodetect
or a device range like dasd=0.0.-0.0.. Even tried
dasd=0.0.-0.0.,autodetect for the heck of it.
I just added:
grep -ir '.*' /sys/bus/ccw/devices/*/online
as the second line of the "init" script in the initrd. The only device
at this point that shows as being online is the console device (0009).
/sys/bus/ccw/devices/0.0.0009/online:1
/sys/bus/ccw/devices/0.0.000c/online:0
/sys/bus/ccw/devices/0.0.000d/online:0
/sys/bus/ccw/devices/0.0.000e/online:0
/sys/bus/ccw/devices/0.0.0190/online:0<--- disk
/sys/bus/ccw/devices/0.0.0191/online:0<--- disk
/sys/bus/ccw/devices/0.0.019d/online:0<--- disk
/sys/bus/ccw/devices/0.0.019e/online:0<--- disk
/sys/bus/ccw/devices/0.0.0592/online:0<--- disk
/sys/bus/ccw/devices/0.0.1000/online:0<--- disk
/sys/bus/ccw/devices/0.0.3000/online:0
/sys/bus/ccw/devices/0.0.3001/online:0
/sys/bus/ccw/devices/0.0.3002/online:0
/sys/bus/ccw/devices/0.0.3200/online:0
/sys/bus/ccw/devices/0.0.3201/online:0
/sys/bus/ccw/devices/0.0.3202/online:0
/sys/bus/ccw/devices/0.0.4000/online:0< disk
Leland
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
Re: Using dasd_configure in SLES11 SP2
Hi Tomas,
Did you catch this line in my other reply?
# Set them to readonly if linked R/O
ACTION=="add", SUBSYSTEM=="ccw", DRIVER=="dasd-eckd", PROGRAM="/bin/sh -c
'/sbin/modprobe vmcp;/sbin/vmcp q v dasd|grep ${DEVPATH##*.}|grep -q R/O'",
ATTR{readonly}="1"
Again...make sure it's all on one line.
Leland
On 2/13/2013 1:31 AM, Pavelka, Tomas wrote:
> Will your solution preserve read only attributes? I.e. if you bring all dasd
> online with a single udev rule, will those linked as read only have the
> correct read only attributes so the kernel knows that it cannot write to them?
>
> Example of what I mean by correct read only attributes:
>
>> vmcp q v dasd
> DASD 0200 3390 VMBL1V R/W353 CYL ON DASD 8460 SUBCHANNEL = 0001
> DASD 0201 3390 VMBL1J R/O683 CYL ON DASD 845C SUBCHANNEL = 0002
>
>> lsdasd
> Bus-ID Status Name Device Type BlkSz Size Blocks
> ==
> 0.0.0200 active dasda 94:0ECKD 4096 248MB 63540
> 0.0.0201 active(ro) dasdb 94:4ECKD 4096 480MB 122940
>
> We have ran into the same problem you are describing and ended up making
> individual rules for each dasd (e.g.
> /etc/udev/rules.d/51-dasd-0.0.0200.rules) to preserve read only attributes.
> But we are new to SUSE and haven't experimented with a single rule for all
> dasd which is why I am curious.
>
> Tomas
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
Re: Using dasd_configure in SLES11 SP2
On 2/13/2013 10:07 AM, Peter Oberparleiter wrote:
On 13.02.2013 00:38, Leland Lucius wrote:
Create the following file and remove all of your existing 51-dasd*.rules.
cat /etc/udev/rules.d/51-dasd.rules
# Rule to add all eckd devices
ACTION=="add", SUBSYSTEM=="ccw", DRIVER=="dasd-eckd", ATTR{online}="1"
Note that adding kernel/module parameter dasd=autodetect should achieve
the same result.
That's really weird. We always specify dasd=autodetect. I even just
double checked to make sure. All of the disks are certainly detected,
they just don't come up online.
But, you've got me curious, so I'm going to modify an initrd and see if
the devices are online prior to any initrd processing. Mayhap something
in boot is putting them offline before udev is getting his mitts on 'em.
Probably not, but I just HAVE to know. :-)
Leland
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
Re: disable autocleanup of /tmp
isn't it part of /etc/cron.daily:suse.de-clean-tmp ? Gaylord (Dave) Toneff Strategic Outsourcing Delivery gton...@us.ibm.com Member, z/Linux Commercial Account Support Kaiser Permanente Account Home Office 661 338 0900 Cell 661 618 2825 From: Tobias Doerkes To: LINUX-390@vm.marist.edu, Date: 02/12/2013 01:20 AM Subject:Re: disable autocleanup of /tmp Sent by:Linux on 390 Port Hi, probably /etc/sysconfig/cron is what you are looking for: ## Path:System/Cron ## Description: days to keep old files in tmp-dirs, 0 to disable ## Type:integer ## Default: 0 ## Config: # # cron.daily can check for old files in tmp-dirs. It will delete all files # MAX_DAYS_IN_TMP or set to 0, this feature will be disabled. # MAX_DAYS_IN_TMP="3" But setting this to 0 will upset your lnxhc. Tobias. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IBM Resources for Developers?
We have an ISV enablement team through partnerworld as mentioned. Chiphopper as I understand it just helps to insure things will compile/will be pretty easy to port before investing to much time. http://www.ibm.com/partnerworld/wps/pub/systems/z/isvtap http://www.ibm.com/isv/go/chiphopper Hopefully the info at those links are helpful, Kurt Acker IBM Smarter Planet, Smarter Data Centers Virtualization and Enterprise System Management Technologies From: Michael Coffin To: LINUX-390@vm.marist.edu, Date: 02/13/2013 02:15 PM Subject: IBM Resources for Developers? Sent by: Linux on 390 Port Hi Folks, I have a vendor that has a product that runs on Linux, but only on Intel-chipped Linux hosts. They are interested in providing S390 binaries for Linux on zSeries customers. Does IBM provide any kind of assistance for vendors to do this, for example access to Linux on zSeries systems where they can install, compile, test and run their applications to produce an S390 distro? -Mike -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: A new open source systems management tool: Mz (longer version)
Peter, > Could you make the srpm available ? I'd like to have a look and test it locally. There is no srpm. As the code is in bash, the RPM includes all the code. However, it does not include the mz.spec file so I just uploaded that to sourceforge. "Mike MacIsaac" -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: A new open source systems management tool: Mz (longer version)
Hello, Could you make the srpm available ? I'd like to have a look and test it locally. Thanks, Peter Peter Linnell SUSE Linux Technical Specialist Tel: 1-415-308-3037 >>> Michael MacIsaac 2/13/2013 12:01 PM >>> Hello lists, Again, Mz is new experimental package that is a lightweight set of Linux bash scripts that provide both a CLI and a Web interface for systems management of z/VM and Linux. These scripts work well between LPARs and CECs. Again, a disclaimer: if you are expecting quality, well-tested bug-free code, then this package is not for you (you have been warned :)) If you're the experimental, "bleading-edge" type, you might want to try it out on a sandbox system. An RPM and a PDF are available at: http://sourceforge.net/projects/managing-z/ Each source file is *not* checked into svn/git as may be customary with sourceforge - too many things to worry about for now, but that will hopefully be coming.. A little background: (1) Two interns worked at IBM back in the summer of '08. They created a great Web front-end to a z/VM and Linux management interface. The problem was that the back-end data structure was simply not there. It became apparent that the data must come first - build the foundation before the facade. (2) One day I needed a chart to show the CEC - LPAR - z/VM - VirtualMachine - Linux hierarchy and started fiddling with boxes, lines and arrows. Not being a 'chart-meister', I thought how can to quickly draw a hierarchy and the Linux 'tree' command came to mind. So I created a hierarchy of Linux directories, ran "tree" and dropped the output in the chart and was about to delete the directory structure when an "aha moment" occured: Why can't the Linux file system be a database for the system z hierarchy of resources? (Neale Ferguson once called it something like "the /proc of System z resources") (3) Another influence was a comment Marcy Cortez made years ago - words the the effect of "I don't want a systems management solution that gives me islands of automation (one island per z/VM LPAR), each of which need care and feeding". (4) Many customers have asked for "no root SSH" support: If root is not permitted to SSH among systems, how does the systems management tool work? I could go on, but it is these and other "zCommunity" input/contributions/revelations from these lists, user group meetings and conferences that have driven the design of Mz. So what *is* Mz? To start with, it is a Linux RPM. A Linux system with the Mz RPM installed is considered to be an "Mz server". It requires extra privileges. Other Linux systems under the same z/VM can be managed by this server. These are considered "Mz clients", however, there is no special client code needed. The term for all Linux systems managed by Mz is nodes (clients + servers = nodes). The Secure Shell (SSH) is used for communication among Mz servers and clients and 'passwordless' SSHing is important. Except for sshd, Mz is effectively "agentless". Mz servers store data about all systems in a hierarchy of Linux directories and files. This enables fast access to data and leverages the rich set of tools that manipulate Linux file systems. There are three main branches of this "Mz tree": (1) Systems - the hierarchy of the System z resources: CECs, LPARs, z/VM systems, virtual machines and Linux systems (2) Appliances - imges of systems that have been 'captured' and can be 'deployed' to other z/VM LPARs (3) SSI clusters - for z/VM 6.2 and later, Single System Image clusters and members Multiple Mz servers can join together to form an Mz cluster. This enables cross-CEC and cross-LPAR systems management through SSH and TCP/IP (hopefully addressing Marcy's concern). All servers in the cluster synchronize with each other. When there are multiple Mz servers in the Mz cluster, each server?s system data is duplicated on each of the other servers but each Mz server "owns" the data on its LPAR. First, second and third level Linuxes are supported (though first and third have been only lightly tested). This project has been a group effort that's been percolating for years. It includes another excellent open-source tool, smaclient, written by Leland Lucius of Sine Nomine Associates. Other IBMers have contributed to the code, especially Christian Paro doing the initial capture and deploy work, and recently, Marian Gasparovic in the area of Web serving (and he has implemented some excellent ideas). While IBM OK'd the open-sourcing of this and the redistribution of smaclient, It is not an official IBM project. It's an experiment in utilizing input from the community and the proven success of the open source model. Nobody has their names in the code. While it could help IBM sales and services, it is really being made available for you the customer - to make it easier to manage your IT systems, and to make your organizations more successful and efficient. "Mike MacIsaac
Re: IBM Resources for Developers?
Partner World is the answer.Depending upon the amount of IBM hardware - or to some degree software - the ISV can move, the more help IBM can be at various costs including free.The Z solutions in Partnerworld are somewhat more complicated to navigate than the other platforms. Get to the right person, they can be great. Edward Long --- On Wed, 2/13/13, Michael Coffin wrote: From: Michael Coffin Subject: IBM Resources for Developers? To: LINUX-390@VM.MARIST.EDU Date: Wednesday, February 13, 2013, 2:01 PM Hi Folks, I have a vendor that has a product that runs on Linux, but only on Intel-chipped Linux hosts. They are interested in providing S390 binaries for Linux on zSeries customers. Does IBM provide any kind of assistance for vendors to do this, for example access to Linux on zSeries systems where they can install, compile, test and run their applications to produce an S390 distro? -Mike -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: IBM Resources for Developers?
>>> On 2/13/2013 at 02:01 PM, Michael Coffin wrote: > Hi Folks, > > I have a vendor that has a product that runs on Linux, but only on > Intel-chipped Linux hosts. They are interested in providing S390 binaries > for Linux on zSeries customers. Does IBM provide any kind of assistance for > vendors to do this, for example access to Linux on zSeries systems where > they can install, compile, test and run their applications to produce an > S390 distro? IBM's Community Development System for Linux has been around for a long, long time now. The IBM link to the page describing it seems to be broken (I've sent in a report for that). But, you might be able to contact the responsible person at linuxats at us.ibm.com. The previous and current maintainer are very friendly people that you probably already know. :) Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
A new open source systems management tool: Mz (longer version)
Hello lists, Again, Mz is new experimental package that is a lightweight set of Linux bash scripts that provide both a CLI and a Web interface for systems management of z/VM and Linux. These scripts work well between LPARs and CECs. Again, a disclaimer: if you are expecting quality, well-tested bug-free code, then this package is not for you (you have been warned :)) If you're the experimental, "bleading-edge" type, you might want to try it out on a sandbox system. An RPM and a PDF are available at: http://sourceforge.net/projects/managing-z/ Each source file is *not* checked into svn/git as may be customary with sourceforge - too many things to worry about for now, but that will hopefully be coming.. A little background: (1) Two interns worked at IBM back in the summer of '08. They created a great Web front-end to a z/VM and Linux management interface. The problem was that the back-end data structure was simply not there. It became apparent that the data must come first - build the foundation before the facade. (2) One day I needed a chart to show the CEC - LPAR - z/VM - VirtualMachine - Linux hierarchy and started fiddling with boxes, lines and arrows. Not being a 'chart-meister', I thought how can to quickly draw a hierarchy and the Linux 'tree' command came to mind. So I created a hierarchy of Linux directories, ran "tree" and dropped the output in the chart and was about to delete the directory structure when an "aha moment" occured: Why can't the Linux file system be a database for the system z hierarchy of resources? (Neale Ferguson once called it something like "the /proc of System z resources") (3) Another influence was a comment Marcy Cortez made years ago - words the the effect of "I don't want a systems management solution that gives me islands of automation (one island per z/VM LPAR), each of which need care and feeding". (4) Many customers have asked for "no root SSH" support: If root is not permitted to SSH among systems, how does the systems management tool work? I could go on, but it is these and other "zCommunity" input/contributions/revelations from these lists, user group meetings and conferences that have driven the design of Mz. So what *is* Mz? To start with, it is a Linux RPM. A Linux system with the Mz RPM installed is considered to be an "Mz server". It requires extra privileges. Other Linux systems under the same z/VM can be managed by this server. These are considered "Mz clients", however, there is no special client code needed. The term for all Linux systems managed by Mz is nodes (clients + servers = nodes). The Secure Shell (SSH) is used for communication among Mz servers and clients and 'passwordless' SSHing is important. Except for sshd, Mz is effectively "agentless". Mz servers store data about all systems in a hierarchy of Linux directories and files. This enables fast access to data and leverages the rich set of tools that manipulate Linux file systems. There are three main branches of this "Mz tree": (1) Systems - the hierarchy of the System z resources: CECs, LPARs, z/VM systems, virtual machines and Linux systems (2) Appliances - imges of systems that have been 'captured' and can be 'deployed' to other z/VM LPARs (3) SSI clusters - for z/VM 6.2 and later, Single System Image clusters and members Multiple Mz servers can join together to form an Mz cluster. This enables cross-CEC and cross-LPAR systems management through SSH and TCP/IP (hopefully addressing Marcy's concern). All servers in the cluster synchronize with each other. When there are multiple Mz servers in the Mz cluster, each server?s system data is duplicated on each of the other servers but each Mz server "owns" the data on its LPAR. First, second and third level Linuxes are supported (though first and third have been only lightly tested). This project has been a group effort that's been percolating for years. It includes another excellent open-source tool, smaclient, written by Leland Lucius of Sine Nomine Associates. Other IBMers have contributed to the code, especially Christian Paro doing the initial capture and deploy work, and recently, Marian Gasparovic in the area of Web serving (and he has implemented some excellent ideas). While IBM OK'd the open-sourcing of this and the redistribution of smaclient, It is not an official IBM project. It's an experiment in utilizing input from the community and the proven success of the open source model. Nobody has their names in the code. While it could help IBM sales and services, it is really being made available for you the customer - to make it easier to manage your IT systems, and to make your organizations more successful and efficient. "Mike MacIsaac" -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http:
A new open source systems management tool: Mz
Hello lists,
I am pleased to announce a new experimental package named "Mz" ("Managing
z") - a lightweight set of Linux bash scripts that provide both a command
line and a Web interface for systems management of z/VM and Linux. These
scripts work well between LPARs and CECs. An RPM and a PDF are available
under the Artistic License 2.0 at:
http://sourceforge.net/projects/managing-z/
If you are expecting quality, well-tested bug-free code, then this package
is not for you (you have been warned :)) If you're the experimental,
"bleading-edge" type, you might want to try it out on a sandbox system.
Here is a "quick start" on how to try it out:
-) Define a virtual machine with class BCDEG privileges and OPTION
LNKNOPAS.
-) Install a recent RHEL or SLES Linux.
-) Install the cmsfs RPM on SLES (on RHEL it's part of s390-tools).
-) Have access to co-req'd RPMs - 'openssh', 'rsync' and 's390-tools' are
easy, 'tree' is on another DVD on SLES (e.g. SLE-11-SP2-SDK).
-) Download the Mz rpm.
-) Install the pre-req RPMs
-) Install it (rpm -ivh mz-2-13.s390x.rpm)
-) Run 'mzmktree'
-) If that works, rum 'mzlstree -d'
-) look in the document /usr/local/share/mz/mz.pdf (also on the
sourceforge site) on how to set up Web access and much more
A longer post coming ...
"Mike MacIsaac"
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
Re: IBM Resources for Developers?
Hi Mike, IBM has a program called Chip Hopper designed for exactly this purpose. https://www-304.ibm.com/partnerworld/wps/servlet/ContentHandler/isv_com_dvm_techval_chiphopper /Nick Nick Sardino System z Software Client Leader IBM Corporation (347) 986-9280 sard...@us.ibm.com From: Michael Coffin To: LINUX-390@vm.marist.edu, Date: 02/13/2013 02:09 PM Subject:IBM Resources for Developers? Sent by:Linux on 390 Port Hi Folks, I have a vendor that has a product that runs on Linux, but only on Intel-chipped Linux hosts. They are interested in providing S390 binaries for Linux on zSeries customers. Does IBM provide any kind of assistance for vendors to do this, for example access to Linux on zSeries systems where they can install, compile, test and run their applications to produce an S390 distro? -Mike -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Using dasd_configure in SLES11 SP2
On Wed, Feb 13, 2013 at 12:49 PM, Mark Post wrote:
> >>> On 2/12/2013 at 06:38 PM, Leland Lucius wrote:
> > As a followup to a posting over on the IBM/VM mailing list about using
> > dasd_configure to bring a device online and create the necessary udev
> > rules, I wanted to contribute this as I think having a separate rule file
> > for every disk device attached to my guests is just wrong.
>
> I would disagree with the "wrong" bit. There are a number of reasons why
> you might want to do this. Keeping things fairly simple and therefore
> easier to understand is one of them.
Could just be my screwy grey matter (probably is ;-)), but I find the
static rule files more difficult to deal with (trust issues) and get much
more of a warm fuzzy knowing that if I add a disk to my Linux guests, it
will be there when I boot. I can only hope that it will be there with the
static rules.
> Trying to handle all the various attributes for all DASD from one file is
> not easy. Things like readonly, use_diag, eer_enabled, and so on.
>
Here's an addition to my previous post that updates the readonly attribute:
# Bring ECKD devices online
ACTION=="add", SUBSYSTEM=="ccw", DRIVER=="dasd-eckd", ATTR{online}="1"
# Set them to readonly if linked R/O
ACTION=="add", SUBSYSTEM=="ccw", DRIVER=="dasd-eckd", PROGRAM="/bin/sh -c
'/sbin/modprobe vmcp;/sbin/vmcp q v dasd|grep ${DEVPATH##*.}|grep -q R/O'",
ATTR{readonly}="1"
But I totally agree with you. Get anymore complicated and an external
script to (dynamically) handle all of the attributes would be the way to go.
>
> -snip-
> > All of our Linux disks are defined at address 1000 or greater. Anything
> > below that address is a CMS disk and is detached in the guests PROFILE
> > EXEC. So, Linux only sees the disks that we want him to see and
> everything
> > above 1000 SHOULD be seen without having to have another file to worry
> > whether it's there or not.
>
> That's fine in a well-controlled z/VM environment. I would definitely
> _not_ recommend this for anyone running any Linux in an LPAR. Too much
> potential for damage, and it will certainly slow down the boot process if
> all devices are visible to all LPARs as most sites have things defined
> these days.
>
Yepper, I thought about that last night and wished I'd put in a blurb about
z/VM only. That little udev rule would NOT be a good thing if running bare.
>
> -snip-
> > Yes, dasd_configure will still create additional rules files, but it
> won't
> > hurt.
>
> As will YaST, since it calls dasd_configure under the covers. So don't be
> surprised if they show up again even if don't use dasd_configure directly.
>
We're good to go there too as we never really use YaST and uninstall most
of the yast rpms (all of them that we can without breaking dependencies).
Leland
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
Re: IBM Resources for Developers?
Have you considered suggesting running z/Linux on an Intel machine under the Hercules-390 emulator? Many have done this successfully. I realize that final testing should likely be done on a real machine, but it would be "free" to do initial testing and adjusting under Hercules. IBM does have a center in Dallas to host various z-series operating systems under z/VM. Might try looking here: http://www-304.ibm.com/partnerworld/wps/pub/systems/technical/hardware/linuxdrive I know nothing more about this. I'm just a z/OS grunt. On Wed, Feb 13, 2013 at 1:01 PM, Michael Coffin wrote: > Hi Folks, > > I have a vendor that has a product that runs on Linux, but only on > Intel-chipped Linux hosts. They are interested in providing S390 binaries > for Linux on zSeries customers. Does IBM provide any kind of assistance > for > vendors to do this, for example access to Linux on zSeries systems where > they can install, compile, test and run their applications to produce an > S390 distro? > > -Mike > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! <>< John McKown -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
IBM Resources for Developers?
Hi Folks, I have a vendor that has a product that runs on Linux, but only on Intel-chipped Linux hosts. They are interested in providing S390 binaries for Linux on zSeries customers. Does IBM provide any kind of assistance for vendors to do this, for example access to Linux on zSeries systems where they can install, compile, test and run their applications to produce an S390 distro? -Mike -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Using dasd_configure in SLES11 SP2
>>> On 2/12/2013 at 06:38 PM, Leland Lucius wrote: > As a followup to a posting over on the IBM/VM mailing list about using > dasd_configure to bring a device online and create the necessary udev > rules, I wanted to contribute this as I think having a separate rule file > for every disk device attached to my guests is just wrong. I would disagree with the "wrong" bit. There are a number of reasons why you might want to do this. Keeping things fairly simple and therefore easier to understand is one of them. Trying to handle all the various attributes for all DASD from one file is not easy. Things like readonly, use_diag, eer_enabled, and so on. -snip- > All of our Linux disks are defined at address 1000 or greater. Anything > below that address is a CMS disk and is detached in the guests PROFILE > EXEC. So, Linux only sees the disks that we want him to see and everything > above 1000 SHOULD be seen without having to have another file to worry > whether it's there or not. That's fine in a well-controlled z/VM environment. I would definitely _not_ recommend this for anyone running any Linux in an LPAR. Too much potential for damage, and it will certainly slow down the boot process if all devices are visible to all LPARs as most sites have things defined these days. -snip- > Yes, dasd_configure will still create additional rules files, but it won't > hurt. As will YaST, since it calls dasd_configure under the covers. So don't be surprised if they show up again even if don't use dasd_configure directly. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Using dasd_configure in SLES11 SP2
On 13.02.2013 00:38, Leland Lucius wrote:
Create the following file and remove all of your existing 51-dasd*.rules.
cat /etc/udev/rules.d/51-dasd.rules
# Rule to add all eckd devices
ACTION=="add", SUBSYSTEM=="ccw", DRIVER=="dasd-eckd", ATTR{online}="1"
Note that adding kernel/module parameter dasd=autodetect should achieve
the same result.
Regards,
Peter Oberparleiter
--
Peter Oberparleiter
Linux on System z Development - IBM Germany
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
Re: Using dasd_configure in SLES11 SP2
On 2/13/2013 1:31 AM, Pavelka, Tomas wrote: Will your solution preserve read only attributes? I.e. if you bring all dasd online with a single udev rule, will those linked as read only have the correct read only attributes so the kernel knows that it cannot write to them? No, but it would be easy to add. Let me tinker a little for ya. Leland -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
