This doesn't address the topic of 3270 linux console limitations but,

Has anyone implemented Rob van der Heij's idea about a read-only-dasd
rescue system that run's from ramdisk?  I don't want to reinvent the
wheel if someone's documented how they did it.

I want to build one that automatically self-configures itself with the
dead server's hostname, IP addrs, LDAP config, and its Tivoli Storage
Manager client configuration.
  It would have the same 3270 console limitations, but if the network's
up I'd have ssh access to a working system that could access all the
disk, dasd or scsi, of the dead system and be much more useful than
IPL-ing the Suse installation system (aka rescue system) from my reader.




--------------------------------------------------------
This e-mail, including any attachments, may be confidential, privileged or 
otherwise legally protected. It is intended only for the addressee. If you 
received this e-mail in error or from someone who was not authorized to send it 
to you, do not disseminate, copy or otherwise use this e-mail or its 
attachments.  Please notify the sender immediately by reply e-mail and delete 
the e-mail from your system.


-----Original Message-----

From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Rob van der Heij
Sent: Thursday, September 28, 2006 4:53 PM
To: [email protected]
Subject: Re: zLinux User Passwords on console

<snip>

How 'bout :   XAUTOLOG deadone STORAGE 512M IPL 200
Where the R/O disk 200 has a rescue system that will run from ramdisk,
uses your central LDAP to authenticate (or has the well known root
password) and tries to mount the file system as /sysimage or what have
you. It should probably come up only with an IP address in your
service network, not at the live (outside) network, but that's up to
you. Bonus points if you make the rescue system in an NSS with a cool
name.

Obviously you could also let PROP do the autolog or use a web site to
trigger it.

Rob

----------------------------------------------------------------------
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

Reply via email to