Alan,
2009.06 vanilla clients will be checking for:
http://opensolaris.org/os/project/indiana/resources/packagemanager/startpagebase/startpagebase-<locale>.tar.gz
Where locale is their current locale, if this fails then it tries the
root locale and then C locale. For example:
http://opensolaris.org/os/project/indiana/resources/packagemanager/startpagebase/startpagebase-en-US.tar.gz
http://opensolaris.org/os/project/indiana/resources/packagemanager/startpagebase/startpagebase-en.tar.gz
http://opensolaris.org/os/project/indiana/resources/packagemanager/startpagebase/startpagebase-C.tar.gz
We need all these navigations to fail, if they do not and any goes to a
real page then the script downloads that page and we are in trouble.
2006.09 machines which have updated from the release repo and current
builds all point to:
http://dlc.sun.com/osol/packagemanager/downloads/200906/
And attempts to download from here fail as expected, until we do
actually put up a tar ball update that we want clients to download.
Hope that clears things up, if not let me know.
Thanks,
JR
Alan Burlison wrote:
jmr wrote:
So if
http://opensolaris.org/os/project/indiana/resources/packagemanager/startpagebase/
is redirected to
http://dlc.sun.com/osol/packagemanager/downloads/200906/ and
attempting to navigate to
http://opensolaris.org/os/project/indiana/resources/packagemanager/startpagebase/startpagebase-C.tar.gz
results in a failure we should be fine and the update_refresh.sh
script will behave as expected.
Are you asking for:
http://opensolaris.org/os/project/indiana/resources/packagemanager/startpagebase/
redirects to
http://dlc.sun.com/osol/packagemanager/downloads/200906/
or are you asking for
http://opensolaris.org/os/project/indiana/resources/packagemanager/startpagebase/startpagebase-C.tar.gz
redirects to
http://dlc.sun.com/osol/packagemanager/downloads/200906/startpagebase-C.tar.gz
because the two are not equivalent.
And just to confirm I have it 100% straight: I think what you are
saying is that you've fixed this in the source so in future the pkgmgr
will go straight to the DLC instead of redirecting via OSO, and you
just need the redirect in place until all the clients have been
updated. Is that correct? If not we have a problem, as the redirects
are a site transition mechanism, not a permanent one.
Thanks,
_______________________________________________
website-discuss mailing list
[email protected]
