I never tried using the installation files ( iplable kernel, parms,
initrd) as a rescue system. I have not done enough installs to know
where and how to interfer with the coded install process to use it as a
rescue service. My own rescue system is a 500 cylinder write-able root
minidisk with a shared read-only /usr minidisk from our production
servers. I have seen references to ipling a NSS for the kernel and
possibly having a filesystem in a DCSS. That could make the footprint
for a rescue server much smaller.
But our designated file-level backup/restore utility is TSM and I let
my personal feelings get in the way and I just quickly have the
operators mount my tapes and use DDR.
/Tom Kern
--- James Melin <[EMAIL PROTECTED]> wrote:
> As far as having a working linux to use for restorations.... in the
> event
> of that hardware error making the disk un-IPLable....
>
> We put the 3 files needed to IPL from 'tape' out on a disk device
> that is
> allocated to all defined guests. It contains the install setup stuff.
> I can
> logon to a guest and type 'lin' and IPL the install system in fairly
> short
> order. I imagine that it wouldn't be hard to craft a bona-fide
> rescue
> system that would be generic enough for all guests, and small enough
> to not
> take up a huge amount of disk.
>
> I have never done this(our VM guy set it up with IBM when we got VM
> in
> here) , but I'm sure other people on the list could certainly point
> out
> what you would need to do to an install image to make it more of an
> IPL-able rescute system.
__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/
----------------------------------------------------------------------
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
