Changes between Version 138 and Version 139 of NanoBSD

Timestamp:

Mar 3, 2011, 1:21:58 PM (14 years ago)

Author:

huub

Comment:

--

NanoBSD

@@ -17 +17 @@
 ----
 WARN: Make sure ''/usr'' is '''at least 5GB''' in size building as building images require quite some space [[BR]]
-WARN: Make sure you install the '''i386''' release of FreeBSD also when your system does support amd64, as cross compiling can give some nasty surprises [[BR]]
+WARN: Make sure you install the 32bit '''i386''' release of FreeBSD also when your system does support amd64, as cross compiling can give some nasty surprises [[BR]]
 ----
 Get yourself a fresh i386 freebsd host with ports and subversion installed as follows:
@@ -203 +203 @@
 If the node has a /28 subnet that should be routable modify the /conf/base/etc/rc.conf file:
 {{{
-lvrouted_flags="-u -m 28 -s s00p3rs3kr3t"
+lvrouted_flags="...... -m 28 "
 }}}
 (for a /24 subnet use -m 24)
+
+  Note. For an 'iLeiden'-type node you have to add also the -z flag (pointing to iLeiden internet gateway ip-addresses, separated by comma's) here.
 
  == E. All done! Load the machine ==
@@ -242 +244 @@
     $ /root/nanobsd/tools/config-image.sh 
     }}}
- 4. Upgrading from 7.2 to 8.0 is tricky because the interface configuration statements have changed. You have to update the config file on slice 3 as well in this case.
+ 4. Upgrading from 7.2 to 8.2 is tricky because the interface configuration statements have changed. You have to update the config file on slice 3 as well in this case.
     Mount the image as memory disk:
     {{{
@@ -266 +268 @@
  There appears to be a bug in FreeBSD8.0 upgrade procedure. A work around for the partition switch problem in the upgrade procedure that works for Wireless Leiden:
   * reboot ( unclear why this is needed, but otherwise it doesnot work, i.e. no switch of the active partition)
-  * updatep2 (of p1)
+  * updatep2 (or p1)
   * log in, check whether fdisk has activated p2 (or p1).
   * If positive go to runlevel 6 (init 6), log out. 
   * After a couple of minutes you can log in, welcome on the new slice!
+
+ Note we have recently modified the /tools/update scripts to use gpart instead of fdisk and boot0cfg, see the /tools/updatep scripts for details. This solved the problem.
     
 
@@ -279 +283 @@
  * /tools/image-build.sh for building images (replaces long command lines and prevents unintentional, time-consuming rebuilds; do not forget to '''setenv the root password'''!) 
 
-== Light based packages suggestions ==
+== Light alternative packages now implemented ==
  * dnsmasq has been implemented instead of isc-dhcp30-server and bind
  * thttpd instead of apache
@@ -364 +368 @@
  * It seems tempting to follow {{{/usr/share/examples/cvsup/stable-supfile}}} instead of {{{/usr/share/examples/cvsup/standard-supfile}}} please __DO NOT__ unless your like big trouble as stable-supfile is the stable __DEVELOPMENT__ branch e.g. upcoming stable.
  * Default username/password = root/<blank>, so please do mind, _when no password is set ssh login is disabled_.
- * Always use `cu` or `putty` for serial communication minicom, screen, putty all issues of some kind. 
+ * Always use `cu` or `putty` for serial communication minicom, screen, putty all have issues of some kind. 
  * After writing an image to cf-card using a usb-card-reader/writer you may encounter a problem dd-ing another image. Rebooting will help. Alternatively you can apply a power-cycle tot het usb device:
   {{{