Would I did was mount it r/w from 3270 mount -n -o remount, rw/
Then manually started inetd (./Inetd start) to start telnet up and telneted in to use VI. -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Brian France Sent: Thursday, May 06, 2004 3:15 PM To: [EMAIL PROTECTED] Subject: how to "vi" to regain a bad image... People, In playing around today with MDISKS, sharing between linux instances, adding dasd to instances, I made a boo boo. I accidentally did a #cp logoff and not a disc. So, I booted the instance but it comes back in a safe mode due to me in the process of adding dasd to it, saying it can't mount the "new" dasd cause it might have a bad superblock. It tells me to repair it manually and reboot. So I figure since I can log in as root, and change over to r/w mode, I'll just undo my changes, and start over. Well, vi, 3270, it's not pretty. SO, before I up and nuke this instance and start over, it made me curious if I was missing some way to repair it. I figure sometime in the future I will probably need it to fix a production instance. Is there another way to edit, remove my changes, and reboot the instance? THANX!!!!! Brian W. France Systems Engineer I Pennsylvania State University Administrative Information Services - Infrastructure/Sysarc Rm 25 Shields Bldg., University Park, Pa. 16802 814-863-4739 [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 ---------------------------------------------------------------------- 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
