Changes between Version 59 and Version 60 of FreeBSD10_Guide

Timestamp:

Aug 29, 2014, 8:39:08 AM (10 years ago)

Author:

huub

Comment:

--

FreeBSD10_Guide

@@ -177 +177 @@
  Note: you can skip this step if you are satisfied with the default password set in step A.3 above.
 
- {{{ 
- $ setenv CFG_ROOT_PASSWORD `dd if=/dev/random bs=10k count=10 |\
+build# setenv CFG_ROOT_PASSWORD `dd if=/dev/random bs=10k count=10 |\
    tr -cd '[a-zA-Z0-9]' | cut -c -15`
- $ echo $CFG_ROOT_PASSWORD
- }}} 
- If you like a simple password, substitute the {{{ `dd if=/dev/random bs=10k count=10 | tr -cd '[a-zA-Z0-9]' | cut -c -15` }}} with your password.
+build# echo $CFG_ROOT_PASSWORD
+
+If you like a simple password, substitute the {{{ `dd if=/dev/random bs=10k count=10 | tr -cd '[a-zA-Z0-9]' | cut -c -15` }}} with your password.
 
 === B.4  Build nanobsd (make sure to prepare some coffee;-) ; use screen) ===
- {{{ 
- $ sh /usr/src/tools/tools/nanobsd/nanobsd.sh -c $R/cfg/nanobsd.wleiden 
- }}}
+
+build# sh /usr/src/tools/tools/nanobsd/nanobsd.sh -c $R/cfg/nanobsd.wleiden 
+
  Note 1: Take a coffee of go for a hike, this normally takes 2 - 8 hours depending on the machine configuration. If you like to save some power use the script provided by Rick ([http://rickvanderzwet.nl/svn/personal/misc/power-saver]). This script is mainly used on a home server for building FreeBSD world and kernels. As soon it is done it can shutdown if not being used anymore. The system has Wake-On-Lan support and can thus be activated again from remote.
 
@@ -208 +207 @@
 
 === C.1. Fetch configuration ===
-
- {{{ 
+ 
  build# $R/tools/image config for <HybridNodename>
- }}}
 
 The script is connecting to the [http://svn.wirelessleiden.nl/svn/node-config/genesis/nodes/ Wireless Leiden 'genesis' database]. First make sure that the configuration file is up to date by clicking the 'update' button on [http://sunfire.wirelessleiden.nl/wleiden/config/ http://sunfire.wirelessleiden.nl/wleiden/config/] Pick your situation! Note: proxy configurations are [http://sunfire.wirelessleiden.nl/wleiden/config/ here].
 
 You can inspect the image bij mounting as memory disk:
-{{{
+
 build# mdconfig -a -t vnode -f /usr/obj/nanobsd.wleiden-hybrid/_.disk.full
 build# mount /dev/md0s1a /mnt
@@ -225 +222 @@
 build# umount /mnt
 build# mdconfig -d -u 0
-}}}
 
 Editing can also be done using the image script:
-{{{
+
 build# $R/tools/image edit
-}}}
+
 
 === C.2. Write the correct image to CF (media based on SLC and not MLC flash seem to perform much better)===
@@ -240 +236 @@
     a. '''New image''': Put full image on compact flash disk (attach a card reader/writer with a CF disk of minimum 1 GB)
     Use the script 
-    {{{
+    
     build# $R/tools/write-image.sh
-    }}}
+    
 or the command line:
-    {{{
+    
     build# dd bs=64k if=/usr/obj/nanobsd.wleiden-hybrid/_.disk.full of=/dev/da0
-    }}} 
+     
     (assuming {{{/dev/da0}}} is your compact flash entry; this takes about 15 minutes, check progress by typing Ctrl-T; you may wish to check afterwards with fdisk whether there 
     are three partitions on the disk, you can also mount /dev/da0s1a and /dev/da0s3 and check the configuration)
 
     a. '''Existing image''': Put partial image on slice (slice 2) (attach a card reader/writer with the CF disk containing the existing image)
-    {{{
+    
     build# dd bs=64k if=/usr/obj/nanobsd.wleiden-hybrid/_.disk.image of=/dev/da0s2
-    }}}
+    
 
     a. '''Existing image remote update''' (slice 2) (network connection to machine 172.x.y.z required)
@@ -259 +255 @@
     For remotely updating an existing configuration use:
     the image script
-    {{{
+    
     build# $R/tools/image deploy on <node> [and reboot]
-    }}}
+    
     or manually:
-    {{{
+    
     build# dd if=/usr/obj/nanobsd.wleiden-hybrid/_.disk.image bs=10k | ssh root@172.x.y.z /tools/updatep2
-    }}}
+    
   
    You may adjust the block size to make the transfer more efficient (additionally ssh -C is possible) and you can use Ctrl-T to check progress.
@@ -276 +272 @@
 
 While the cf card is still in your flash card reader you can check whether the image has been written correctly. Check whether you can mount the partitions, e.g.
-{{{
+
 build# mount /dev/da0s1a /mnt
 build# ls /mnt
 build# umount /mnt
-}}}
+
 and the configuration partition:
-{{{
+
 build# mount /dev/da0s3 /mnt
 build# ls /mnt
-}}}
+
 
 If you cannot mount the partitions, take a fresh cf card and start again with writing the image.