Diff for /wikisrc/tracking_current.mdwn between versions 1.1 and 1.2

version 1.1, 2013/05/11 09:10:12 version 1.2, 2013/05/11 09:15:13
Line 32  after it's written, more bugs can be fou Line 32  after it's written, more bugs can be fou
    list. The [source-changes](http://netbsd.org/mailinglists/#source-changes)     list. The [source-changes](http://netbsd.org/mailinglists/#source-changes)
    mailing list is also of interest.     mailing list is also of interest.
   
 # XXX  
  * When upgrading to a more recent version of -current you should   * When upgrading to a more recent version of -current you should
     *always* install and boot a new kernel before installing any new     *always* install and boot a new kernel before installing any new libs (unless 
     libs ([[http://netbsd.org/docs/current/index.html#star|*]]). In general the best approach is to try the new     you are certain there have been no new system calls added, but do it anyway; 
     kernel before anything else, and if you hit any problems see the     it's safer).In general the best approach is to try the new kernel before 
     entry in the [[http://netbsd.org/docs/kernel/#problems_compiling_a_current_kernel|Kernel FAQ]].     anything else, and if you hit any problems see the entry in the
      [Kernel FAQ](http://netbsd.org/docs/kernel/#problems_compiling_a_current_kernel).
   
  * When compiling a -current kernel, always remember to include the   * When compiling a -current kernel, always remember to include the
    `COMPAT_<lastrelease>` option (e.g., `COMPAT_16`). As current diverges from     `COMPAT_<lastrelease>` option (e.g., `COMPAT_16`). As current diverges from
Line 46  after it's written, more bugs can be fou Line 46  after it's written, more bugs can be fou
    compatibility code for the time between booting the new kernel and finishing     compatibility code for the time between booting the new kernel and finishing
    your build via `build.sh`     your build via `build.sh`
   
 # XXX  
 \*: Unless you are certain there have been no new system calls added,  
 but do it anyway; it's safer.  
   
 ## Updating an existing system from a current snapshot  ## Updating an existing system from a current snapshot
   
 *Please remember to check  *Please remember to check
Line 226  the [[NetBSD Guide|guide/index]]. Line 222  the [[NetBSD Guide|guide/index]].
   
 ## Updating the configuration and startup files  ## Updating the configuration and startup files
   
 # XXX  See the
 See the [[http://netbsd.org/docs/guide/en/chap-updating.html#updating-etcupdate|More details about the updating of configuration and startup files]] section in the [[http://netbsd.org/docs/guide/en/|NetBSD Guide]].  [[More details about the updating of configuration and startup files|guide/updating]]
   section in the [[NetBSD Guide|guide/index]].
   
 ## What if I get an error?  ## What if I get an error?
   
Line 370  command: Line 367  command:
     $ cvs tag successful-build-BUILD date      $ cvs tag successful-build-BUILD date
   
 ### Notes  ### Notes
    * If the NetBSD customised version of CVS, which recognises *\$NetBSD\$*
  * If the NetBSD customised version of CVS, which recognises `$NetBSD$`  
    markers in files, is not used, the NetBSD revision number of the file is      markers in files, is not used, the NetBSD revision number of the file is 
    available for reference purposes when build problems occur.     available for reference purposes when build problems occur.
  * The sup/import/merge sequence described above is quite easily   * The sup/import/merge sequence described above is quite easily

Removed from v.1.1  
changed lines
  Added in v.1.2


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb