Consensus came down to what alan_at_nabeth has said
earlier.....Not to create fs, fsets, clusters etc. in
5.1 and expect to mount them with 4.0G.
Just incase to many applications get broken beyond
repair, then i will have the option of going back to
4.0g in a heartbeat.
Thanks once again goes to Alan_at_nabeth, Dr. Tom Blinn,
Jeffrey Hummel and Bryan Lavelle.
****************
As long as you don't do things from the V5.x system
that change
the V4.x file systems in a way incompatible with
V4.0x, you can
do what you want to do. You do need two system disks,
and you
must not try to share system files, but most
applications can
be shared provided you lay things out correctly.
However, it
is not trivially easy to get the applications to
install other
than where they think they should install, and in some
cases,
you need to run newer versions because the suppliers
say so.
*****************************
--- Tru64 User <tru64user_at_yahoo.com> wrote:
> Greetings,
> I would like to know if anyone has successfully been
> able to dual boot btwn 4.0g and 5.1.
> I am using advfs, and currently have 2 /root disks,
> and 2 /usr disks, both with 4.0g. I would like to
> upgrade one of these to 5.1, and have the ability to
> switch back to 4.0g incase too many applications get
> broken as a result of the upgrade, as has been the
> case in other upgrades (update install). I have
> other
> local disks as well in this system (1.5 TB hanging
> from a esa10000, hsz70 v7.3 controller), and all
> filesystems are advfs. Also system is highly NFS'ed
> to
> other boxes (tru64 4g and RedHat 6.0)
> Alan_at_nabeth had some words of caution back
> then...and
> i never tried/tested anything yet (No test resources
> for this scenario). His note is attached below.
> Would
> like to receive any additional words of caution and
> techniques to proceed if possible.
> All
>
>
>
>
> Keeping all of a system disk isolated to a single
> disk
> is pretty easy and offers a way to easily
> switch among
> versions on a given system. At one time I
> had
> disks
> for V1.3, V2.1, V3.0, V3.2, V3.2G and an
> assortment of
> V4 through V4.0D. This works best when the
> system
> disk is fairly isolated. NFS mounting from
> a
> stable
> server is the best way to get other file
> systems.
>
> If you do have other local file systems on
> different
> disks, some of the things you'll have to
> watch
> for:
>
> o The native version of AdvFS on V5 (AdvFS
> on
> disk format
> V4) isn't usable on V4 (AdvFS on disk
> format V3).
>
> o The AdvFS V3 support on Tru64 UNIX V5 may
> make subtle
> changes in the organization or usage of
> data. If you
> have a local file that needs to be usable
> by both,
> test it throughly.
>
> o UFS tends to be less touchy and generally
> fixable with
> fsck, but test it as well.
>
> V4 should be reasonably with the system
> firmware requirements
> of V5. Other hardware should be ok. The
> HSZ70 at V7.3 may
> not behave well on V5.
>
> =====
>
>
> __________________________________________________
> Do You Yahoo!?
> Great stuff seeking new owners in Yahoo! Auctions!
> http://auctions.yahoo.com
=====
__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions!
http://auctions.yahoo.com
Received on Fri Jan 25 2002 - 13:24:30 NZDT