[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[cobalt-developers] Re: OS Restore server?



Once upon a time, Lyle Scheer <lyle.scheer@xxxxxxx> said:
> Chris Adams wrote:
> > I set up a server here to be a RaQ OS restore server.  I can plug into a
> > hub and restore RaQ1, RaQ1->2, RaQ2, RaQ3, and RaQ4, all from the same
> > server (and I don't have to boot a CD, make sure I have the exact right
> > hardware and configuration, etc. - I put update PKGs on the server to be
> > loaded during restore).  It was easy to make MIPS and x86 RaQs restore
> > from the same server, because the MIPS RaQs mount "/nfsroot" and the x86
> > RaQs mount "/nfsroot-x86".
> >
> > Now we have a RaQ550 and I need to do an OS restore.  However, the
> > RaQ550 also mounts "/nfsroot-x86", but it doesn't look like the RaQ3/4
> > netboot filesystem will coexist with the RaQ550 netboot filesystem.  I
> > tried setting my DHCP server with 'option root-path "/nfsroot-x86-550";'
> > but the RaQ550 ignored it and mounted "/nfsroot-x86" anyway.
> >
> > Does anyone know of a way to make this coexist on a single server?  Does
> > Sun have different networks for restoring different RaQs?
> 
> The RaQ550 /nfsroot-x86 should also work with RaQ 3/4.

The new OSRCD doesn't work like the old OSRCDs (my setup is based off
the old OSRCDs).  The old OSRCDs (for example the RaQ1 CD and original
RaQ3 CD) would prompt for what you wanted to load ("RaQ1", "RaQ1->2
Destroy", "RaQ2", etc. for the MIPS, "RaQ3i", "RaQ4", etc. for the x86).
Adding a new build required putting the build tree in /nfsroot or
/nfsroot-x86 and adding the section to /test_dir/mfg/qube_config (and
optionally /test_dir/mfg/patches).  It looks like the new-style OSRCD
doesn't prompt; it just picks the first thing it finds in
/bto-sync/production or /bto-sync/experimental and loads it, without
giving you a choice.

However, I think I see how to modify os_restore_build to look at the
options and prompt, so I guess I'll try that.  I need to modify it
anyway, since it has no way to associate update packages with a
particular build (everything in /bto-sync/updates is listed as an
update).

-- 
Chris Adams <cmadams@xxxxxxxxxx>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.