I love multibos. It's great! It's an excellent way to roll through TL updates, and test all sorts of stuff.
The only thing I don't like about it is you can't really leave your server in your multibos shell. You can, but it can break things later on.
For example, let's say you have server_a, and it's at 6.1.4.4 and it's very critical, and you want to bring it up to 6.1.4.6. You can use multibos to bring it up to that level of 6.1.4.6, and keep the old 6.1.4.4 in the old multibos shell in case you need to roll back. However, if you leave your system in the new one, and you go to do a nimadm operation down the road - you won't be able to because your LV's will be named bos_hd5 etc.
So now what I do is this:
1. Upgrade server to new level using multibos.
2. Test and let sit for a week.
3. multibos -R (remove our old instance)
4. multibos -sX (create duplicate instance)
5. Change bootlist and boot into new instance.
6. multibos -R
Before I would just let the server sit there with the old instance until the NEXT update, that way the option of always going back is there.. but it's easy to forget your LV's are not named correctly when you're trying to do other things :).
Thanks to Andrew Wojnarek