Re: [OpenIndiana-discuss] updates and reboots
On Mon, 5 Feb 2024 19:08:26 +0100, Andreas Wacknitz via openindiana-discuss wrote: > Am 04.02.24 um 23:20 schrieb Goetz T. Fischer: >> On Sun, 4 Feb 2024 09:37:26 +0100, Andreas Wacknitz via openindiana-discuss >> wrote: >>> You can only update individual packages when you uninstall both, >>> userland-incorporation and entire. >> i did so and got the exact same reply as before. and using install instead >> fails with tons of >> consolidation/osnet/osnet-incorporation errors. > You are unlucky that we had changes in illumos-gate recently that also > needed changes in oi-userland. > This is rare but can happen. So, in this case you'll need a full update. openssl seems to be one of those. thanks for the info! ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
Am 04.02.24 um 23:20 schrieb Goetz T. Fischer: On Sun, 4 Feb 2024 09:37:26 +0100, Andreas Wacknitz via openindiana-discuss wrote: You can only update individual packages when you uninstall both, userland-incorporation and entire. i did so and got the exact same reply as before. and using install instead fails with tons of consolidation/osnet/osnet-incorporation errors. You are unlucky that we had changes in illumos-gate recently that also needed changes in oi-userland. This is rare but can happen. So, in this case you'll need a full update. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Sun, 4 Feb 2024 09:37:26 +0100, Andreas Wacknitz via openindiana-discuss wrote: > You can only update individual packages when you uninstall both, > userland-incorporation and entire. i did so and got the exact same reply as before. and using install instead fails with tons of consolidation/osnet/osnet-incorporation errors. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
Am 04.02.24 um 03:21 schrieb Goetz T. Fischer: well it might not be so good after all. for example just updating openssl: root@openindiana:~# pkg list library/security/openssl-31 NAME (PUBLISHER) VERSIONIFO library/security/openssl-31 3.1.4-2023.0.0.1 i-- root@openindiana:~# pkg update -nv library/security/openssl-31 No updates available for this image. looks fine. however, if i just use "pkg update -nv" i see: library/security/openssl-31 3.1.4-2023.0.0.1 -> 3.1.5-2024.0.0.0 so there is an update after all. apparently updating single packages doesn't work this way. Yes, this is by design. The metapackage userland-incorporation defines a baseline and thus fixes all package versions of packages coming from oi-userland. userland-incorporation will be updated automatically whenever an oi-userland jenkins job finishes successfully. You can only update individual packages when you uninstall both, userland-incorporation and entire. But that comes at additional costs as there are no guarantees that a newer version of a packages works with other packages. This is, by the way, usually a duty of a package maintainer. If a package maintainer updates a package he/she needs to check whether other packages need to be rebuild or even updated, too. This is a situation where problems can be introduced easily because some dependencies and changes are obvious and others are hiddenm especially the dependencies from illumos-gateway. Andreas On Mon, 8 Jan 2024 12:31:04 +0100, Goetz T. Fischer wrote: fair, that's good enough for me. much thanks for all the great info !! On Mon, 8 Jan 2024 12:22:20 +0100, Marcel Telka wrote: Sure. It should somehow (and usually) work, modulo the userland-incorporation warning in my previous mail. So it is discouraged. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
well it might not be so good after all. for example just updating openssl: root@openindiana:~# pkg list library/security/openssl-31 NAME (PUBLISHER) VERSIONIFO library/security/openssl-31 3.1.4-2023.0.0.1 i-- root@openindiana:~# pkg update -nv library/security/openssl-31 No updates available for this image. looks fine. however, if i just use "pkg update -nv" i see: library/security/openssl-31 3.1.4-2023.0.0.1 -> 3.1.5-2024.0.0.0 so there is an update after all. apparently updating single packages doesn't work this way. On Mon, 8 Jan 2024 12:31:04 +0100, Goetz T. Fischer wrote: > fair, that's good enough for me. much thanks for all the great info !! > > On Mon, 8 Jan 2024 12:22:20 +0100, Marcel Telka wrote: >> Sure. It should somehow (and usually) work, modulo the >> userland-incorporation warning in my previous mail. So it is >> discouraged. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
fair, that's good enough for me. much thanks for all the great info !! On Mon, 8 Jan 2024 12:22:20 +0100, Marcel Telka wrote: > Sure. It should somehow (and usually) work, modulo the > userland-incorporation warning in my previous mail. So it is > discouraged. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, Jan 08, 2024 at 12:13:48PM +0100, Goetz T. Fischer wrote: > sure, that's fine. if the package i selected for an update does require a > reboot then so be it. the idea > is just to avoid reboots for things i don't necessarily need to be up to date. > how much that would reduce reboots ... not sure, but maybe it would save some. Sure. It should somehow (and usually) work, modulo the userland-incorporation warning in my previous mail. So it is discouraged. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
sure, that's fine. if the package i selected for an update does require a reboot then so be it. the idea is just to avoid reboots for things i don't necessarily need to be up to date. how much that would reduce reboots ... not sure, but maybe it would save some. On Mon, 8 Jan 2024 12:05:46 +0100, Marcel Telka wrote: > For the ssh case (package network/ssh) you also need to account that the > package depends on system/library and this means... see my other mail. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, Jan 08, 2024 at 11:52:25AM +0100, Goetz T. Fischer wrote: > no sorry, i wasn't clear. not one isolated package of course but whatever > "pkg update some_great_app" > triggers. No, you were clear. My "ssh only and nothing else" as an example was confusing. I meant ssh (and all tightly related pkgs that are needed to run ssh), as opposite to the full "pkg update" case. So my previous reply applies exactly to your case. For the ssh case (package network/ssh) you also need to account that the package depends on system/library and this means... see my other mail. In short if your system is older than 2023-12-22 then you cannot have latest network/ssh package. > the idea is to limit the updates to what i deem sensitive and whatever else > those updates drag in with > them is fine. reboots included because it would likely not be as often as > doing a full "pkg update" > everytime. > > On Mon, 8 Jan 2024 11:40:59 +0100, Marcel Telka wrote: > > e.g. update ssh only and nothing else -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
no sorry, i wasn't clear. not one isolated package of course but whatever "pkg update some_great_app" triggers. the idea is to limit the updates to what i deem sensitive and whatever else those updates drag in with them is fine. reboots included because it would likely not be as often as doing a full "pkg update" everytime. On Mon, 8 Jan 2024 11:40:59 +0100, Marcel Telka wrote: > e.g. update ssh only and nothing else ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, Jan 08, 2024 at 10:59:05AM +0100, Goetz T. Fischer wrote: > On Mon, 8 Jan 2024 10:49:37 +0100, Marcel Telka wrote: > > On Mon, Jan 08, 2024 at 10:27:32AM +0100, Goetz T. Fischer wrote: > >> which would mean pretty much every update needs a reboot. > > > > If you need to be always up-to-date. All the time and with all packages > > available then yes, you need to reboot once a day. > > hmm okay, i don't need that. if i would only use "pkg update" for specific > packages like for example > ssh, would pkg then fetch everything else that's required? yes, but ... see below > and would that way work permanently? Not sure what you mean by that. > or would i cripple the system after a while if i only update like that? Officially, there are incorporations to make sure your system is in known (and theoretically well tested) state. Mainly userland-incorporation. The userland-incorporation prevents you from most upgrades (or possibly downgrades) as you painted above. So if you want to do something like that (e.g. update ssh only and nothing else) then you need to deal with the userland-incorporation constraints somehow (for example by uninstalling the incorporation). But once you do that you could shot yourself in a foot if you really do not know what you are doing. So it is basically not recommended for general use. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, 8 Jan 2024 10:49:37 +0100, Marcel Telka wrote: > On Mon, Jan 08, 2024 at 10:27:32AM +0100, Goetz T. Fischer wrote: >> which would mean pretty much every update needs a reboot. > > If you need to be always up-to-date. All the time and with all packages > available then yes, you need to reboot once a day. hmm okay, i don't need that. if i would only use "pkg update" for specific packages like for example ssh, would pkg then fetch everything else that's required? and would that way work permanently? or would i cripple the system after a while if i only update like that? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, Jan 08, 2024 at 10:48:30AM +0100, Goetz T. Fischer wrote: > well, looking at their release notes > https://raw.githubusercontent.com/omniosorg/omnios-build/r151046/doc/ReleaseNotes.md > 1 reboot per month on average. that i can do with indiana as well. If you really need very long uptimes with being always up-to-date (reasonably, so without up-to-date illumos-gate bits) then you'll probably need to create your own fork of OpenIndiana (or OmnioOS, or whatever). Similarly as I do for our internal enterprise purposes. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, Jan 08, 2024 at 10:27:32AM +0100, Goetz T. Fischer wrote: > On Mon, 8 Jan 2024 10:03:47 +0100, Marcel Telka wrote: > > OTOH, system/library in OI (and also the rest of "kernel" - the > > illumos-gate) is rebuild once a day and almost all pacakges depends on > > them (either directly or indirectly). > > which would mean pretty much every update needs a reboot. If you need to be always up-to-date. All the time and with all packages available then yes, you need to reboot once a day. > how about --no-backup-be and/or --deny-new-be ? i can't try it right now > because i just updated my > system. That's orthogonal to the problem/question we are talking about here. In short, if you specify --deny-new-be you won't be able to upgrade any package that require reboot. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
well, looking at their release notes https://raw.githubusercontent.com/omniosorg/omnios-build/r151046/doc/ReleaseNotes.md 1 reboot per month on average. that i can do with indiana as well. On Mon, 8 Jan 2024 01:23:28 -0800, Joshua M. Clulow via openindiana-discuss wrote: > If you're looking for a server-centric distribution that produces > critical bug and security updates without the constant churn, you > should probably look at OmniOS LTS instead of OpenIndiana. The OmniOS > folks have a sharp focus on minimising disruption for server > operators, which is pretty different from how OpenIndiana is > maintained. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, 8 Jan 2024 10:03:47 +0100, Marcel Telka wrote: > OTOH, system/library in OI (and also the rest of "kernel" - the > illumos-gate) is rebuild once a day and almost all pacakges depends on > them (either directly or indirectly). which would mean pretty much every update needs a reboot. how about --no-backup-be and/or --deny-new-be ? i can't try it right now because i just updated my system. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, 8 Jan 2024 at 00:54, Goetz T. Fischer wrote: > i'm aware of the disadvantages but i'd like to have the choice to do so > anyway if/when i see fit. If you're looking for a server-centric distribution that produces critical bug and security updates without the constant churn, you should probably look at OmniOS LTS instead of OpenIndiana. The OmniOS folks have a sharp focus on minimising disruption for server operators, which is pretty different from how OpenIndiana is maintained. Cheers. -- Joshua M. Clulow http://blog.sysmgr.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, Jan 08, 2024 at 08:56:30AM +0100, Goetz T. Fischer wrote: > of course but that raises the question why new libs would require a reboot. > the worst that could happen New libs does not require reboot on their own. The problem is with system/library only (and few other similar). The system/library package itself contains only few files that requires reboot (libc only). So with some effort we probably could make system/library usually upgradable without reboot (when libc is unchanged) but I think the bigger problem is that system/library depends on SUNWcs and SUNWcs contains 48 files that require reboot on update. And similar cascading dependencies makes the picture even more complex. > is that programs which depend on that lib would crash if they're restarted. > but if they're also updated, > then the next time they're restarted or just started it'll be fine. > let's say there's a new openssl so i simply copy the new one over the old > one, restart ssh and i'm good. > > similarly i can for example update rhel for months without a reboot and that > works. and i don't mean > live kernel patching. basically i only have to reboot for kernel stuff. but > for everything else i just > don't see a reason for all these reboots. To compare with rhel you should consider system/library similarly to their kernel-* packages. The main difference is that rhel's kernel packages are rebuild rarely AND almost no other package depends directly on them. OTOH, system/library in OI (and also the rest of "kernel" - the illumos-gate) is rebuild once a day and almost all pacakges depends on them (either directly or indirectly). So the current result is that if you want to stay up-to-date you need to reboot often. This is the fee we need to pay with the current way how OI Hipster is developed and built. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
i'm aware of the disadvantages but i'd like to have the choice to do so anyway if/when i see fit. On Mon, 8 Jan 2024 10:22:43 +0200, Toomas Soome via openindiana-discuss wrote: > reboot is needed to verify your setup is still working as supposed after an > update. You can have > different kind of potential issues; if file is overwritten, then your > currently running app will most > likely crash, if the file is replaced, then running apps will continue to use > old content till the > apps are restarted and you can have mixture of old and new setup, which can > give interesting results > sometimes (you think your system has security patch installed, but actually > old code is running and > you are still vulnerable for example). > > Of course, the context can be different, getting your vi or gnu tar updated > most likely will not > affect your system, but there are different scenarios. > > Having BE concept actually does imply that you get used to have those BE’s > created, so that you can > actually rely on actually having the option to roll back in case of failure > from update, or recovery > from other kind of corruption. And yes, the cost of having those BE’s is > needing to actually create > those BE’s and leave old one functional. > > I have seen plenty of cases where people have done those “small changes” on > live systems over long > period of time and ending up unbootable or broken systems once they actually > reboot the system. > Therefore I really encourage to have habit to reboot the system, to make sure > that everything is still > behaving as you do expect to. > ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
> On 8. Jan 2024, at 09:56, Goetz T. Fischer wrote: > > of course but that raises the question why new libs would require a reboot. > the worst that could happen > is that programs which depend on that lib would crash if they're restarted. > but if they're also updated, > then the next time they're restarted or just started it'll be fine. > let's say there's a new openssl so i simply copy the new one over the old > one, restart ssh and i'm good. > > similarly i can for example update rhel for months without a reboot and that > works. and i don't mean > live kernel patching. basically i only have to reboot for kernel stuff. but > for everything else i just > don't see a reason for all these reboots. reboot is needed to verify your setup is still working as supposed after an update. You can have different kind of potential issues; if file is overwritten, then your currently running app will most likely crash, if the file is replaced, then running apps will continue to use old content till the apps are restarted and you can have mixture of old and new setup, which can give interesting results sometimes (you think your system has security patch installed, but actually old code is running and you are still vulnerable for example). Of course, the context can be different, getting your vi or gnu tar updated most likely will not affect your system, but there are different scenarios. Having BE concept actually does imply that you get used to have those BE’s created, so that you can actually rely on actually having the option to roll back in case of failure from update, or recovery from other kind of corruption. And yes, the cost of having those BE’s is needing to actually create those BE’s and leave old one functional. I have seen plenty of cases where people have done those “small changes” on live systems over long period of time and ending up unbootable or broken systems once they actually reboot the system. Therefore I really encourage to have habit to reboot the system, to make sure that everything is still behaving as you do expect to. rgds, toomas > > On Mon, 8 Jan 2024 08:10:51 +0100, Marcel Telka wrote: >> many newly built packages will require something from new >> illumos-gate (typically system/library[*]) > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
of course but that raises the question why new libs would require a reboot. the worst that could happen is that programs which depend on that lib would crash if they're restarted. but if they're also updated, then the next time they're restarted or just started it'll be fine. let's say there's a new openssl so i simply copy the new one over the old one, restart ssh and i'm good. similarly i can for example update rhel for months without a reboot and that works. and i don't mean live kernel patching. basically i only have to reboot for kernel stuff. but for everything else i just don't see a reason for all these reboots. On Mon, 8 Jan 2024 08:10:51 +0100, Marcel Telka wrote: > many newly built packages will require something from new > illumos-gate (typically system/library[*]) ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
On Mon, Jan 08, 2024 at 06:21:31AM +0100, Andreas Wacknitz via openindiana-discuss wrote: > "pfexec pkg freeze osnet-incorporation" does mostly what you want. > It prohibits the update of packages that come from illumos-gate. > There are only few other packages (eg. NVIDIA drivers) from OI userland > that need a reboot. The only problem with this approach is that it will shortly prevent most updates since many newly built packages will require something from new illumos-gate (typically system/library[*]), but since you stay frozen at the older illumos-gate you won't be able to update affected packages. The above depends on frequency of the build server updates to new illumos-gate bits and reboots, which is currently often (roughly once a week, I think). [*] Currently ca 2000 packages out of 5200 require system/library and another ca 300 comes from illumos-gate (so you explicitly opted to not update them by frozing osnet-incorporation even they do not depend on system/library). So you have left only 2900 packages (or very likely even less because system/library is not the only package that comes from illumos-gate and is required by other packages) that you can safely update with frozen osnet-incorporation. Ca 1100 of them are Perl packages (library/perl-5/*) and ca 1300 are Python packages (library/python/*). So at the end of the day you can update only less than 500 non Perl, non Python packages when you run with frozen osnet-incorporation. This includes ca 60 packages with fonts, for example. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | +---+ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
Am 08.01.24 um 04:07 schrieb Goetz T. Fischer: hi, a general question: i did a "pkg update" on the 2nd and another one just now. so just a few days later but again a new be was created and i had to reboot. of course i understand that for certain things a reboot is necessary but is there a way to somewhat filter the things that don't need a reboot ? for a desktop system that doesn't matter but i can't reboot a server once a week or maybe even more often. especially if i have several zones and/or vms. in other words, what's the "officially" recommended way of updating a server? thanks in advance for any info -- R-A-C Götz T. Fischer CertIT +49(0)7225/98 98 79 g.fisc...@r-a-c.de r-a-c.de ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss "pfexec pkg freeze osnet-incorporation" does mostly what you want. It prohibits the update of packages that come from illumos-gate. There are only few other packages (eg. NVIDIA drivers) from OI userland that need a reboot. Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] updates and reboots
> On Jan 7, 2024, at 22:07, Goetz T. Fischer wrote: > > hi, > > a general question: > > i did a "pkg update" on the 2nd and another one just now. so just a few days > later but again a new be > was created and i had to reboot. of course i understand that for certain > things a reboot is necessary > but is there a way to somewhat filter the things that don't need a reboot ? > for a desktop system that doesn't matter but i can't reboot a server once a > week or maybe even more > often. especially if i have several zones and/or vms. in other words, what's > the "officially" > recommended way of updating a server? > > thanks in advance for any info While OI doesn't support hot kernel patching AFAIK (like some Linux, or like Solaris occasionally did), not all updates create a new BE (unless one requested a backup BE). What can be changed safely without a new BE or reboot, and what can't, is subtle. It's quite possible that some individual package updates (and thus the most extreme requirement of a group of them) might be able to be redone so they don't require a new BE or reboot; but getting that reliably right isn't easy. I don't know offhand what happens if you install an update that creates a new BE, and without rebooting, install another. I would hope the newest BE created would include all the updates (so maybe you could delete the intermediate one to save space). How long you wait with the reboot is up to you. But some inconsistencies may exist, if for instance there are administrator-editable configuration files both in the running BE and in the new one, and you make changes, they probably won't get into the new BE. So you don't want to wait too long, and with multiple administrators, you want to make sure they're careful about that and know that there's a pending reboot to a new BE, and to defer configuration changes as much as possible. And of course some configuration changes add to the risk of boot problems. If you need nonstop uptime, you need a cluster or the like, so you can update one at a time. And you need very strict configuration control, and probably a test system where all changes are tried first (isolated network, obviously dummy data, to avoid nasty confusion). At least with BE's rather than old style patching, you can do the somewhat slow update anytime (give or take that it has some slight performance impact while running), do the relatively quick reboot at a time more convenient to the customers, and have an easy recover plan (switch back to the old BE) if something goes wrong. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
