Diff for /wikisrc/Attic/tracking_current.mdwn between versions 1.2 and 1.3

version 1.2, 2013/05/11 09:15:13 version 1.3, 2019/05/03 10:12:56
Line 40  after it's written, more bugs can be fou Line 40  after it's written, more bugs can be fou
    [Kernel FAQ](http://netbsd.org/docs/kernel/#problems_compiling_a_current_kernel).     [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_80`). As current diverges from
    the last s"table release, compatibility code will be added, but it will only     the last stable release, compatibility code will be added, but it will only
    be enabled if this option is present. At a bare minimum, you will need this     be enabled if this option is present. At a bare minimum, you will need this
    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`
Line 119  corresponding releases found in by date  Line 119  corresponding releases found in by date 
   
      2. kernel modules       2. kernel modules
   
         A new framework *kernel modules* has been introduced after netbsd-5 was           A new framework *kernel modules* was been introduced after netbsd-5 was 
         branched, and `GENERIC` kernel on i386 port has been switched to using           branched.
         the kernel module files since November 2008. The kernel module files           The kernel module files 
         will be loaded dynamically by the kernel to support various kernel           will be loaded dynamically by the kernel to support various kernel 
         options (including file systems) on demand, rather than linking all           options (including file systems) on demand, rather than linking all 
         necessary (but possibly unused) object files into the kernel binary.           necessary (but possibly unused) object files into the kernel binary. 
Line 148  corresponding releases found in by date  Line 148  corresponding releases found in by date 
         module files to a modular'ized kernel (and you can't rename directories           module files to a modular'ized kernel (and you can't rename directories 
         without a working kernel).          without a working kernel).
   
         **Warning**: The infrastructure of kernel module files mentioned here is   
         still under discussion on -current development. It could be changed at   
         some point before the next 6.0 release and in that case the description   
         in this section will be obsolete. Again, check   
         [src/UPDATING](http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/UPDATING)   
         and  
         [currenet-users mailing list](http://mail-index.netbsd.org/current-users/)  
         for updated information.  
   
         There is  
         [a possible alternative structure for kernel modules](http://mail-index.netbsd.org/current-users/2009/05/10/msg009372.html)  
         which was proposed on May 2009, but we have not got any conclusion yet.   
         This would be because most -current users build their own custom kernels   
         from sources, but kernel modules might be rather useful for users who   
         don't want to bother to compile their own kernels from sources to just   
         try to use optinal functions. Anyway, any feedback about this brandnew   
         kernel modules is quite appreciated.  
   
  4. Reboot machine with the new kernel:   4. Reboot machine with the new kernel:
   
         # shutdown -r now          # shutdown -r now
   
  5. Make sure the new kernel boots and works properly. If your new kernel has   5. Make sure the new kernel boots and works properly. If your new kernel has
     any trouble, you can recover it by loading the renamed old one. If you are       any trouble, you can recover it by loading the renamed old one. If you are 
     using modular'ized GENERIC kernel mentioned above, you might also have to       using a modularised GENERIC kernel as mentioned above, you might also have to 
     restore old kernel module files.      restore old kernel module files.
   
  6. Extract the matching base, and any other desirable feature sets **except    6. Extract the matching base, and any other desirable feature sets **except 
Line 259  section in the [[NetBSD Guide|guide/inde Line 241  section in the [[NetBSD Guide|guide/inde
   
 ### To check out the sources from a certain branch  ### To check out the sources from a certain branch
   
     $ cvs checkout -rnetbsd-5-0 src      $ cvs checkout -rnetbsd-8-0 src
   
 See   See 
 [src/doc/BRANCHES](http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/doc/BRANCHES)   [src/doc/BRANCHES](http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/doc/BRANCHES) 
Line 293  for a description of the branches in the Line 275  for a description of the branches in the
  * You can put switches for specific commands in a `.cvsrc` in your home    * You can put switches for specific commands in a `.cvsrc` in your home 
    directory, and they will be automatically used. A sample `.cvsrc` would be:     directory, and they will be automatically used. A sample `.cvsrc` would be:
   
        update -dP      cvs -q
          checkout -P      checkout -P
          diff -u      update -dP
       diff -upN
       rdiff -u
       release -d
   
 ## Importing and merging sources.  ## Importing and merging sources.
   
Line 448  The methods to retrieve the whole reposi Line 433  The methods to retrieve the whole reposi
                   
    After that, run `sup /path/to/supfile anoncvs` to retrieve the files.     After that, run `sup /path/to/supfile anoncvs` to retrieve the files.
   
    Some example sup files are available in `/usr/share/examples/supfiles`. Also,      Some example sup files are available in `/usr/share/examples/supfiles`.
    check our  
    [list of SUP mirrors](http://netbsd.org/mirrors/#sup) to find the server   
    closest to you!  
   
  * **rsync**   * **rsync**
   
Line 462  The methods to retrieve the whole reposi Line 444  The methods to retrieve the whole reposi
        $ rsync -v -a --delete --exclude '#cvs.lock' rsync://anoncvs.NetBSD.org/cvsroot/src .         $ rsync -v -a --delete --exclude '#cvs.lock' rsync://anoncvs.NetBSD.org/cvsroot/src .
   
    Please see our [list of rsync mirrors](http://netbsd.org/mirrors/#rsync)!     Please see our [list of rsync mirrors](http://netbsd.org/mirrors/#rsync)!
   
  * **cvsup**  
   
  * CVSup is not currently available for all NetBSD architectures, since the M3   
    compiler has not been ported. On i386, you can mirror the repository from   
    cvsup.de.NetBSD.org with the `devel/cvsup` package and the following config   
    file:  
   
        *default host=cvsup.de.NetBSD.org  
        *default base=/usr  
        *default prefix=/local/NetBSD-cvs  
        *default release=cvs  
        *default delete use-rel-suffix  
        *default compress  
   
        netbsd  
   
    Please see our [list of CVSup mirrors](http://netbsd.org/mirrors/#cvsup)!  

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


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