How about the LPARNAME in /proc/sysinfo. Ron Sent via BlackBerry by AT&T
-----Original Message----- From: "Alan Schilla (OET)" <alan.schi...@state.mn.us> Date: Fri, 8 May 2009 08:10:06 To: LINUX-390@VM.MARIST.EDU<LINUX-390@VM.MARIST.EDU> Subject: Re: DR and Linux native lpar I have been giving this some thought lately too. I have been planning to extract the cpu serial number from /proc/cpuinfo. This should tell me whether or not I am on my normal production hardware. The problem I have with this is remembering that I need to change the script when we move zVM or Linux to a different system or replace hardware. That's the scary part. I am looking for something system wide yet better controllable that cpuid. Al Schilla Systems Programmer Enterprise Technology Services Office of Enterprise Technologies phone: 651-201-1216 email: alan.schi...@state.mn.us -----Original Message----- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Scott Rohling Sent: Thursday, May 07, 2009 2:07 PM To: LINUX-390@vm.marist.edu Subject: Re: DR and Linux native lpar Sure .. the trick is knowing when to use the DR version in your Linux scripts. Not sure /proc/cpuinfo would help.. maybe passing a parm at boot and looking at /proc/cmdline ? After determining which version/CPU/whatever you are on - your scripts can hit the appropriate network config files and change them if they are not correct for 'where' you are. Not sure if this is what you wanted though? Scott On Thu, May 7, 2009 at 12:29 PM, Michael Wickman <mwick...@waddell.com>wrote: > We are in the design phase of building our own disaster recovery site. > DASD will be mirrored or flashed. We don't have VM, so have SUSE > release 9 native lpar. Is it possible to have some logic in the IPL > startup to specify those unique things like IP address or a separate > script we can invoke when the DR site version is used. > > Thanks. > > Mike Wickman > > > > > > <font size="1"> > <div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in > 0in 1.0pt 0in'> > </div> > "This email is intended to be reviewed by only the intended recipient > and may contain information that is privileged and/or confidential. > If you are not the intended recipient, you are hereby notified that > any review, use, dissemination, disclosure or copying of this email > and its attachments, if any, is strictly prohibited. If you have > received this email in error, please immediately notify the sender by > return email and delete this email from your system." > </font> > > ---------------------------------------------------------------------- > 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 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 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
