11.4 won't run on any of my hardware. I even opened a support ticket about it not that it will do any good.
I've also asked for a refund for our service contracts. Somehow I don't expect the money to come back. Our policy now is to dump Sun and move to FreeBSD. From a security point, I like different systems in a chain to be running different processors and SPARC had a nice spot in that. Right now I'm looking at putting FreeBSD on a QNAP rack mount thing. Its got dual power supply, dual 10 gig eth, Quad-Core 1.7 GHz ARM® Cortex-A15 CPU and 4 disk slots for about $1k. Intel is making me feel like this is a better and better solution every week. Intel has been doing odd things ever since they tried to improve the 4004. They were luckier with their early designs than groups like Motorola and Fairchild. Many of the early CPUs would have instructions that just didn't work right, it just happened that Intel lucked out and their defective instruction sets were ended up being Turing complete. Then they lucked out when IBM decided they wanted a cut down machine for their PC and picked the slowest of the 3 designs so it wouldn't compete with their system 36. They ended up using a design that had less memory and was slower than their computer typewriter system called Displaywriter. A friend of mine worked on the PC assembly line putting a flyer in each box that basically said "Thanks for buying this toy. There are great deals to trade it in to a real computer, call IBM today" I'm waiting for the Spectre/Meltdown write issues to go public. They are much harder to pull off since you need to get two cores to play unfriendly games as the same time. The basis of the trick is to get one of the early termination instructions to write a complete cache line and then have another core ask "Hey, are you done with the cache line yet? I need it" and the hardware dumps the stuff into ram. Not so good if that is the page table write permissions. -tim > On Aug 16, 2018, at 7:21 PM, nathan <[email protected]> wrote: > > Meh... sure there were some bad bits, but PCA made almost all of them go > away... > > Just the same, I wont miss Sol 10 patching either... > > ;) > > Solaris 11.4 for the win! > > Sent from my Samsung Galaxy smartphone. > > -------- Original message -------- > From: Chris Wells <[email protected]> > Date: 16/8/18 1:56 pm (GMT+10:00) > To: [email protected] > Subject: [msosug] Not super happy, but good riddance > > Solaris 10 reached Extended Support in Jan 31. We’ve just found that we can’t > download the 10_Recommended.zip file any longer. > > > > Since Oracle (and Sun for that matter) never kept historical versions of > 10_Recommended Patch Sets (Clusters), we basically can’t patch our boxes any > longer (unless you’ve happened to have kept an old version of > 10_Recommended.zip). > > > > However, I don’t think I’ll ever miss Sun patching, packaging. We just spent > a couple of months patching 5 M5ks. It’s not something I’d wish on my enemies. > > And for the patch script to take 2 hours to apply [hiding the zones first], > is plainly ridiculous. > > > > There were just too many hacks and issues: > > > > The awful N-to-M relationship between patches and packages, the fact that you > can have a partially applied “patch” > > Obsoleted patches introduced circular dependency logic; the complete mess > that was introduced with zones ; (I’ve seen patches that say you need to > apply them in the global zone, that wont apply due to them being under or > over release in the sparse zone) > > Issues with live upgrade packages (SUNWlu*) > > Issues with SUNWstosreg/ SUNWservicetagu packages > > Issues with sparse zones / full-root zones > > Patches that were installed without having back out data > > Patches which say that they can only be installed in the global zone, but you > can’t because the child zone is above rev, and can’t be backed out > > Corrupted /var/sadm/… > > Live upgrade doesn’t work with lofs filesystem > > liveupgrade doesn’t work with zones with zpools shared between zones > > …the list goes on and on. > > > > > > “zoneadm: zone XXXXXX : ERROR: attempt to downgrade package SUNWsomething, > the source had patch XXXXXX-NN but this system only has XXXXXX-MM…” > > “Fatal failure occurred - impossible to install any patches.” > > “SUNWlu-xxxxxxxxx: For patch 149646-02, required patch 147147-26 does not > exist.” > > “These packages installed on this system were not installed on the source > system:” > > “These packages installed on the source system are inconsistent with this > system:” > > > > > > #GoodRiddance > > > > *************************************************************** > This is a confidential message intended for the named recipient(s) only. The > contents herein are privileged to the sender and the use thereof is > restricted to the intended purpose. If you have received this e-mail in > error, please do not use, disclose, distribute, copy, print or relay on this > email. If receipt is in error, please advise the sender by reply email. Thank > you. > *************************************************************** > _______________________________________________ > msosug mailing list > [email protected] > http://mexico.purplecow.org/m/listinfo/msosug
_______________________________________________ msosug mailing list [email protected] http://mexico.purplecow.org/m/listinfo/msosug
