Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. =================================================================== RCS file: /ftp/cvs/cvsroot/htdocs/docs/current/index.html,v rcsdiff: /ftp/cvs/cvsroot/htdocs/docs/current/index.html,v: warning: Unknown phrases like `commitid ...;' are present. retrieving revision 1.23 retrieving revision 1.24 diff -u -p -r1.23 -r1.24 --- htdocs/docs/current/index.html 2010/01/06 16:54:41 1.23 +++ htdocs/docs/current/index.html 2010/10/05 16:08:30 1.24 @@ -111,8 +111,8 @@ eliminated. Things you need to remember (top) -
People using NetBSD-current are strongly encouraged to subscribe to the current-users @@ -120,7 +120,7 @@ eliminated. mailing list is also of interest.
When upgrading to a more recent version of -current you should always install and boot a new kernel before installing any @@ -130,7 +130,7 @@ eliminated. Kernel FAQ.
When compiling a -current kernel, always remember to include the COMPAT_<lastrelease> option (e.g., COMPAT_16). As current @@ -165,15 +165,15 @@ by date and platform.
-
binary/sets
directory,
+binary/sets
directory,
and mget *.tgz
files
into your favorite local administrative directory
(for example, $HOME/current
);
when limited by disk space and/or time,
only kern-GENERIC, etc, base, and comp (if you want a compiler) are
essential.GENERIC
),
+GENERIC
),
copy it into /
(root) directory.
$ su
@@ -189,14 +189,14 @@ copy it into /
support.
The following items are typical files that possibly need to be updated:
-Usually a machine specific bootloader passes several parameters to a loaded kernel. If some new parameters have been added or @@ -204,7 +204,7 @@ might mention possible quirks on daily c you might also have to install new bootloader files for a new kernel to handle new features. A method to update bootloader files is quite machine dependent, - so check boot(8) and installboot(8) man pages for details.
+ so check boot(8) and installboot(8) man pages for details.On i386 and amd64, if you are using FFSv1 for root file system
on wd0a
(i.e. first ATA drive), typical commands to update
bootloaders are:
@@ -228,7 +228,7 @@ might mention possible quirks on daily c
/usr/mdec/boot
is secondary loader and it's file system
independenet.
If you forget your root file system type (FFSv1 or FFSv2), - you can check it by dumpfs(8) command: + you can check it by dumpfs(8) command:
# dumpfs /dev/rwd0a | head -3 @@ -238,8 +238,8 @@ might mention possible quirks on daily c #
A new framework “kernel modules” has been introduced +
A new framework “kernel modules” has been introduced
after netbsd-5 was branched, and GENERIC
kernel on i386
port has been switched to using the kernel module files since November 2008.
The kernel module files will be loaded dynamically by the kernel
@@ -296,18 +296,18 @@ might mention possible quirks on daily c
# shutdown -r now
GENERIC
kernel mentioned above,
you might also have to restore old kernel module files.
base
,
+base
,
and any other desirable feature sets
except etc
:
@@ -318,16 +318,16 @@ and any other desirable feature sets # ...Don't forget to specify
"p"
option (preserve permissions)
-on tar(1) command otherwise setuid'ed commands (like su(1))
+on tar(1) command otherwise setuid'ed commands (like su(1))
won't work.
Warning: Extracting etc.tgz
on
the installed system will overwrite your local settings.
/etc
-as last step: postinstall(8) will first check and fix most things that
-can be automated, and etcupdate(8) in the second step will ask on what
+/etc
+as last step: postinstall(8) will first check and fix most things that
+can be automated, and etcupdate(8) in the second step will ask on what
to merge:
# /usr/sbin/postinstall -s ~/etc.tgz check @@ -390,18 +390,18 @@ section in the-
- Read the src/UPDATING +
+
- Read the src/UPDATING file from the release you're trying to build.
-- Read the current-users +
- Read the current-users archive for hints.
-- Update again. You may have caught the repository in the middle of +
- Update again. You may have caught the repository in the middle of a commit to several related files, or the problem might have already been fixed.
-- If all else fails, send email to current-users explaining the +
- If all else fails, send email to current-users explaining the problem. Include the date, time, and method you used to get your -current sources, as well as any local changes you've made. Then put in a short script that includes the error messages @@ -421,14 +421,14 @@ by CVS
section in the NetBSD Guide. -+ -+@@ -438,17 +438,17 @@ See for a description of the branches in the CVS repository.-+--
- +
+
- Do not use the cvs '-z' flag. The data stream gets out of sync, leading to corruption on the client, or causing the client to hang completely. The additional load is also hard on the cvs server.
-- If you want to check out a certain branch of the tree, you may +
- If you want to check out a certain branch of the tree, you may want to take caution not to overwrite any existing directories by creating a new directory for this branch: @@ -460,14 +460,14 @@ $ mv src ../NewName $ cd .. $ rmdir NewName-temp
-- +
- You will have to use objdirs in order for cvs updates to work correctly. If you happen to get errors from cvs saying things like:
-cvs [update aborted]: could not chdir to gnu/usr.bin/gdb/gdb: Not a directoryyou should do amake cleandir
and try again. Make sure to runmake obj
after the cvs update.- +
You can put switches for specific commands in a .cvsrc in your home @@ -548,16 +548,16 @@ $ cvs -d /misc/cvsrep checkout netbsd command:
$ cvs tag successful-build-build date
-+--
- If the NetBSD customised version of CVS, which recognises +
@@ -663,7 +663,7 @@ base=/usr prefix=/usr backup use-rel-suf as such the number of concurrent rsync users is restricted. If you still want to try rsync, the command to retrieve the repository is: -+
- If the NetBSD customised version of CVS, which recognises $NetBSD$ markers in files, is not used, the NetBSD revision number of the file is available for reference purposes when build problems occur.
-- The sup/import/merge sequence described above is quite +
- The sup/import/merge sequence described above is quite easily automatable. The following Perl script automates this process.
-#!/usr/pkg/bin/perl @@ -605,7 +605,7 @@ close TAG; be fairly straightforward to write a shell script to perform the same task.- Techniques for tracking current with CVS have been discuss several +
- Techniques for tracking current with CVS have been discuss several times on the NetBSD current-users mailing list. For alternative techniques try searching the NetBSD mailing lists.
rsync -v -a 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!
- cvsup