Tian He wrote: > On Fri, Dec 4, 2009 at 1:23 PM, James Carlson <carlsonj at workingcode.com > <mailto:carlsonj at workingcode.com>> wrote: >> I'm baffled. You were asking about SUNWonbld and _building_ the >> software from source code. That has nothing to do with BEs. >> >> What are you doing? > I am building and installing ON from source code. > That description <http://defect.opensolaris.org/bz/show_bug.cgi?id=1156> > is found when I searched the error message. I couldn't see the > connection either.
But what does that have to do with using Install to copy in a new kernel? I'm really confused about what you're doing. Yes, that bug you point to does exist, but it's mostly relevant if you're upgrading your system using the "pkg" command. It's not related to using Install or to building the software from source or to the tool set used to build the software from source. For what it's worth, I definitely recommend using bfu rather than Install. The latter is a bit faster, but unless you're positive that you're modifying only kernel bits and that your new kernel _exactly_ matches the existing user space (including all the undocumented wonderfulness in libc.so.1), you'll end up in a world of hurt. Cap-eye "Install" is for kernel hackers. (For what it's worth, once you've got a system bfu'd to a particular set of consistent bits, you can use Install to try out modified kernel bits, assuming you don't affect the kernel/user boundary in your changes.) Also, it's very helpful to use "beadm create" to apply your changes to an alternate boot environment, so that if something goes wrong (as it often does when modifying the OS itself), you'll have a way to get back. But all of that assumes a lot about what you're trying to do and what experience you have in Solaris kernel work ... -- James Carlson 42.703N 71.076W <carlsonj at workingcode.com>
