On 9/29/06, Romanowski, John (OFT) <[EMAIL PROTECTED]> wrote:
To get the parameters for self-configuring I was thinking of having the rescue system read them from a CMS file using Rick Troth's CMSFS utility functions. The dead server's unique CMS parm file could be created by hand in advance, or populated once or periodically by some type of export process from the live server. For an IP address I'm thinking the rescue system can just use the dead server's 'admin lan' address probably similar function to your 'service' lan.
Sure. You can get the userid somewhere out of /proc and use that to pick up the file from a common R/O disk. But then you would probably also use this for normal configuration and not just rescue? If it's only used at startup you would still be pretty save in trying to update the files. And it's not even wrong to put the right parameters there just before you do the rescue IPL.
Instead of basing the rescue system on the starter system I'd like to just copy and convert an existing "full-fledged" server; and make it maintainable by Yast Online Update. That way I could easily add and maintain any packages I need for our environment, like the TSM restore client. When I boot the rescue system off R/W disk I can update it; when I boot it off R/O disk it assumes its rescue role.
I'm not sure it's that easy because with the way SuSE boots your normal system, the initrd role is already taken. So I think you would need to create something that merges the initrd (with the drivers) and the root file system. But your skills in that area or probably better than mine. Rob -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.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
