tag:blogger.com,1999:blog-3458993853337115554.post5634369478468292410..comments2023-08-03T10:35:33.906-04:00Comments on Security, beer, theater and biking!: What are Solaris 10 Updates made of: Patches and scripts and packages, too.Valerie Fenwickhttp://www.blogger.com/profile/08527896668172818126noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-3458993853337115554.post-3726390300210070062007-12-19T11:05:32.000-05:002007-12-19T11:05:32.000-05:00Hi Mark-The release notes for every update should ...Hi Mark-<br>The release notes for every update should contain a list of all patches (including revs) included in that release. (that's why the release notes are so long! :-)<br>ValerieValeriehttp://blogs.sun.com/bubbvanoreply@blogger.comtag:blogger.com,1999:blog-3458993853337115554.post-16515648494246492002007-12-04T05:37:44.000-05:002007-12-04T05:37:44.000-05:00Valerie,Is there a resource that lists which patch...Valerie,<br>Is there a resource that lists which patches and revs are included in a Solaris Update?Mark Hodgesnoreply@blogger.comtag:blogger.com,1999:blog-3458993853337115554.post-11588693101631402282005-11-09T23:19:11.000-05:002005-11-09T23:19:11.000-05:00Hi,Why can't newboot be delivered by patches?T...Hi,<br><br><b>Why can't newboot be delivered by patches?</b><br><br>The quick answer is that it can, and will.<br><br>New packages are needed, and these will be delivered in a patch. It's not the normal way of doing things but this is exceptional circumstance.<br><br>Patching to newboot is not as trivial as you might think. Just getting it to work on a simple system isn't too hard, but we also need to make sure that customers using live upgrade can upgrade to newboot smoothly, which takes more effort.<br><br>Best Wishes,<br>~AlAlbert Whitehttp://blogs.sun.com/albertwnoreply@blogger.comtag:blogger.com,1999:blog-3458993853337115554.post-36558399370165875222005-10-31T10:01:57.000-05:002005-10-31T10:01:57.000-05:00Hi Mike -For your first question: most of our new ...Hi Mike -<br>For your first question: most of our new hardware support comes in the form of packages.<br>Patches can only patch existing software, so currently the only way to delivery new packages is through upgrade or fresh install. Since for the most part, new hardware is going to have those bits preinstalled, it's not an issue.<br>We are investigating new ways of delivering software and issues like yours are being kept in mind. I'm not sure what happened in your upgrade, as I've not heard of anything quite like that before.<br>As for NewBoot: NewBoot also comes with new packages. I will get clarification from the NewBoot team specificly.<br>Thanks,<br>ValerieValerie Bubbhttp://blogs.sun.com/bubbvanoreply@blogger.comtag:blogger.com,1999:blog-3458993853337115554.post-16885041023358308852005-10-28T14:05:44.000-04:002005-10-28T14:05:44.000-04:00I have a couple questions around this process. Pe...I have a couple questions around this process. Perhaps some of it lies more on the shoulders of the group that handles installation/upgrade tools...<br><b>Is there a simpler way to get support for updated hardware.</b><br>The most common reason that I choose the latest update over a fresh patch set is to get support for newer hardware. This is for a couple reasons: to support newer components in the same server (15k getting US-IV, then US-IV+ boards) or to update standard flash archives for deployment across all new or redeployed servers.<br>Unfortunately, the only supported way of getting this ON support seems to be to either install fresh or perform an upgrade. I have always been leary of upgrades and my most recent try explains why: I had the Sun SAN packages and relevant patches applied to a SUNWCall flar (misbuilt, long story). I wanted to get the SUNWCXall cluster on there so that I could reliably deploy it on everything from 220's - 25k's. However, on the first boot after the upgrade, sanity checks on files that were supposed to be patched indicated they were not the ones that were supposed to be there (checksums didn't match checksums from before upgrade). The patches were still installed and not superceded. Yikes. What else did it mess up?<br>I would feel a lot better about adding new hardware support to an OS if I could get a set of packages and patches that would add that support. This would help greatly in the promise of being able to easily upgrade high end servers like marketing says you can do.<br><b>Why can't newboot be delivered by patches?</b><br>I hear from many people that it is impossible to deliver newboot via anything other than a fresh install. I have a hard time believing that. It certainly could be a risky patch, but I haven't heard the argument for why it could not be delivered as the appropriate packages and/or patches. Grub can live in cylinder 0, just as the current boot code does. Any ramdisk boot images could be in a patch/package or generated from a script using the files on the system.<br>FWIW, way back when I had relatively little difficulty switching from LILO to GRUB with Linux. I installed the grub package, ran a few commands, and it worked better than its predecessor.<br>Thanks for any light you can shed,<br>MikeMike Gerdtsnoreply@blogger.com