Kashmir running on Spacely.

After considerable work, Kashmir 'nee Corona is running on Spacely.

The rough outline of the steps I used:
1.) Install new yum from Corona. Configure repos for new yum.
2.) Remove the 2.4 kernels.
3.) Set exactarch=0?
4.) Upgraded by hand fedora-release
5.) Don't upgrade rpm  to 4.4!
6.) Remove nscd and nss_ldap-217-1
7.) Hand upgrade glibc (get both sparc64 and sparc versions)
8.) yum upgrade
9.) reboot (and cross fingers)


I took some detours in and amongst this, including a dead end down rpm-4.4
alley (hint: don't upgrade rpm by hand!) and backing out a botched rpm-4.4
install (including removing the old python directory to get yum working
again).  This issue was primarily nscd, nss_ldap-217, and glibc.  I had to
-Uvh both the sparc and sparc 64 glibc (and glibc-common ON A SINGLE
COMMAND LINE) to get yum to resolve all deps.  I think exactarch=0 had to
be set, as well; it worked when exactarch was 0, might work with
exactarch=1 but haven't tried it.  Having a remote serial console during
this certainly eased my nerves during the reboot, but I didn't have to
drop to singleuser or anything like that.

My install was pretty minimal, not any extra packages, and a lean Aurora
1.0 install at the base that I upgraded to 1.92, so there may be some real
kinks for a fully loaded 1.92 -> corona/kashmir.
-- 
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
1 PARI Drive
Rosman, NC  28772
(828)862-5554
www.pari.edu
_______________________________________________
Aurora-sparc-devel mailing list
[email protected]
http://lists.auroralinux.org/mailman/listinfo/aurora-sparc-devel
Aurora FAQ: http://www.ecs.soton.ac.uk/~mas01r/aurorafaq.html