Last weekend I ran "pkg image-update" and updated the system to build 128, downloaded the tip of the ONNV source tree using Mercurial, ran nightly to build and Install to install. This time it works!
I wonder when "pkg image-update" is executed, how can we specify which build we want to update to. I read the manual and info, which don't seem to give me the answer. Is it something we have no control over? Tian On Sat, Dec 5, 2009 at 5:22 PM, Tian He <hnhetian at gmail.com> wrote: > thanks a lot! > > tian > > > On Fri, Dec 4, 2009 at 11:55 PM, Jonathan Adams <jonathan.adams at > sun.com>wrote: > >> On Fri, Dec 04, 2009 at 03:55:25PM -0800, Tian He wrote: >> > > 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 >> > > >> > >> > I wonder how I can be absolutely sure of this. Is that something that >> comes >> > with years of experience? Is there a recommended path to reach that >> level? >> >> As a rule of thumb, I always BFU to (usually) the closest daily build >> before using Install. Being inside the Sun firewall, I have the advantage >> of access to nightly builds generated by the ON gate staff, though. >> >> If I were doing a project outside SWAN, I'd use BFU the first time, >> and then if my changes were kernel-only, Install to test intermediate >> builds. After syncing up with the gate, I'd run a non-incremental >> nightly(1), >> BFU the results, then Install from there. >> >> If your changes cross the U-K boundry, you typically know it; the above >> is mostly to save you from unexpected dependencies from *other* putbacks. >> >> Cheers, >> - jonathan >> >> > > > -- > One way leads to another > -- One way leads to another -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/on-discuss/attachments/20091207/b063d6b5/attachment.html>
