On 10/10/07, James Carlson <[EMAIL PROTECTED]> wrote: > Robin du writes: > > On 10/10/07, Darren J Moffat <[EMAIL PROTECTED]> wrote: > > > When you build the kernel (or any of ON for that matter) you always only > > > build x86 or sparc since there is no cross compilation support. The > > > makefiles are setup to only build the binaries relevant for each > > > architecture. > > > > My steps as follows: > > > > 1) #cd $(SRC)/uts > > 2) dmake all > > 3) make install > > 4) Install -G kernel.robin -k i86pc > > 5) extract kernel image and update another menu.lst entry. > > > > It will take a long time even I change only one line of the source. > > I can't bear with it. Can this be improved? > > It depends on which line you're changing and what the effects of that > change are. > > Assuming it's just one of the drivers or kernel modules, you can > always go down into one of the $SRC/uts/intel/* subdirectories and do > a "dmake" there. That can then be manually copied to the system being > tested -- then a "bootadm update-archive" and "uadmin 2 0", and you're > good to go. > > Make sure it's a system you don't much care about. The first few > times you try this, you'll probably turn the machine into a warm > brick and need to reinstall it. > > > > If you really only want to build and install the kernel then run "make > > > install" in $SRC/uts and if you really know what you are doing you can > > > use Install(1) (from SUNWonbld) to install just a kernel - but note this > > > is very fragile and may cause panic's depending on what you change. It > > > is recommended to build the whole ON tree and use bfu unless you are > > > 100% certain your changes are kernel only. > > > > Hmm..., I thought Cap-Eye-Install is safer than BFU, because it > > doesn't overwrite the current kernel image. Why BFU is recommended? > > any known issue about Cap-Eye-Install? > > NO! > > Cap-Eye Install overwrites *only* the kernel. It doesn't touch the > user space bits. This makes it *much* more dangerous than BFU, > because there are shared private interfaces between kernel and user > space in ON, particularly with libc.
Yes, Cap-Eye install only works if the change is for kernel only. If you are not clear whether your modification is for kernel only, you may run into a weird problem. > > BFU is the supported way to replace the ON bits. It generally > includes corrections for changes that have occurred in packaging. > However, it only updates ON -- which is a small part of OpenSolaris. > Err..., BFU is dangerous, too. When change the code, developer can't make sure if it will cause kernel panic. While BFU overwrite the existing kernel image, so this is quite possible you will have no way to boot your system anymore. -Aubrey _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
