On 29/09/2007, J Duff <jduff at getgreenbytes.com> wrote: > I'm modifying OpenSolaris for use on a field system. Initially I need to > modify only the kernel. I plan to pick a stable version of OpenSolaris, apply > my kernel changes, build, and then perform a Cap-Eye Install. This will > become the image for my field machine. Since I haven't BFU-ed, I can continue > to install packages on the field machine if necessary. ?All is good. > > At some point in the future, I may need to modify OpenSolaris user space > utilities and libs. I believe this will require a BFU in order to "install" > my user space changes. Once I BFU, I will no longer be able to install > packages. This means that my field system will be frozen at this point in > time, and I will not be able to add packages to the field machines. Is this > correct? >
It doesn't exactly destroy the ability to install packages. It's just that your machine is now in an unknown state since packages no longer necessarily "line up" with what is actually installed. It can cause bizarre results if you attempt to use the package manager to upgrade or remove any existing packages. > Is there some way to modify OpenSolaris user space utilities and libs without > destroying the ability of the machine to install additional packages? > You can't retain the integrity of the packaging system and BFU at the same time. You should still have the ability to install packages after a BFU, but upgrading or removing existing ones can lead to your system being in a "brickified" state. -- Shawn Walker, Software and Systems Analyst binarycrusader at gmail.com - http://binarycrusader.blogspot.com/ "Beware of bugs in the above code; I have only proved it correct, not tried it. " --Donald Knuth
