Changes between Version 19 and Version 20 of WikiStart

Timestamp:

Jan 24, 2010, 9:56:22 PM (15 years ago)

Author:

huub

Comment:

--

WikiStart

@@ -125 +125 @@
  }}}
 
+ B.3. Set your favorite root password to be used in the image 
+
+ Note: you can skip this step if you are satisfied with the default password set in step A.4 above.
+
+ {{{ 
+ $ 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.
+
+ B.4 Apply kernel patch for USB-LAN adapter
+
+ For use of a Davicom DM9601 USB network controler you have to patch usbdevs and the if_udav driver:
+ {{{
+ cd /usr/src/sys/dev/usb/
+ patch < /root/nanobsd/misc/patches/usbdevs.patch
+ patch < /root/nanobsd/misc/patches/if_udav.c.patch
+ }}}
+
+ B.5. Build nanobsd (make sure to prepare some coffee;-) )
+ {{{ 
+ $ sh /usr/src/tools/tools/nanobsd/nanobsd.sh -c /root/nanobsd/cfg/nanobsd.wleiden 
+ }}}
+ Note 1: Take a coffee of go for a hike, this normally takes 2 - 8 hours depending on the machine configuration
+
+ Note 2: even this little script got flags, check the output of {{{sh /usr/src/tools/tools/nanobsd/nanobsd.sh -h}}}
+ {{{
+-b suppress builds (both kernel and world)
+-k suppress buildkernel
+-w suppress buildworld
+-c specify config file
+...
+ }}}
+
+
+== C. Fetch proxy configuration onto image, write to CF disk or remotely update ==
+
+C.1. Fetch configuration
+
+ {{{ 
+ $ /root/nanobsd/tools/config-image.sh 
+ }}}
+
+The script is connecting to the [http://svn.wirelessleiden.nl/svn/node-config/genesis/nodes/ Wireless Leiden 'genesis' database]. Pick your situation!
+
+You can inspect the image bij mounting as memory disk:
+{{{
+mdconfig -a -t vnode -f /usr/obj/nanobsd.wleiden/_.disk.full
+mount /dev/md0s1a /mnt
+ls /mnt
+umount /mnt
+mount /dev/md0s3 /mnt
+ls /mnt
+umount /mnt
+mdconfig -d -u 0
+}}}
+
+
+C.2. Write the correct image to CF
+----
+    ''NOTE:'' '''''_.disk.full''''' is required for '''new CF cards''' as it contains two base systems and one configuration. [[BR]]
+              '''''_.disk.image''''' on the other hand can be used to update an '''existing CF card''' 
+----
+
+    a. '''New image''': Put full image on compact flash disk (attach a card reader/writer with a CF disk of minimum 1 GB)
+    {{{
+    $ dd bs=64k if=/usr/obj/nanobsd.wleiden/_.disk.full of=/dev/da0
+    }}} 
+    (assuming {{{/dev/da0}}} is your compact flash entry; this takes about 15 minutes; 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)
+    {{{
+    $ dd bs=64k if=/usr/obj/nanobsd.wleiden/_.disk.image of=/dev/da0s2
+    }}}
+
+    a. '''Existing image remote update''' (slice 2) (network connection to machine 172.x.y.z required)
+
+    For remotely updating an existing configuration use:
+    {{{
+    dd if=/usr/obj/nanobsd.wleiden/_.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.
+ 
+== D. Check the cf card and apply last minute changes ==
+
+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.
+{{{
+mount /dev/da0s1a /mnt
+ls /mnt
+umount /mnt
+}}}
+and the configuration partition:
+{{{
+mount /dev/da0s3 /mnt
+ls /mnt
+}}}
+
+If you can not mount the partitions, take a fresh cf card and start again with writing the image.
+
+
+ == E. All done! Load the machine ==
+ Place the new CF disk in the machine and boot it up (existing nodes: just reboot), you should be good to go! Especially first time booting can take a long time, depending also on hardware. In a Soekris4521 this takes about ten minutes. You can follow the boot process using e.g. minicom or tip, via a serial connection (communication parameters: 9600 8N1).
+
+  Note 1. For subsequent nodes you can skip the build and go directly for step C, or take a look at development if you have to rebuild the image (after small changes).
+
+  Note 2. Check your bios version in case of booting problems (note: default communication setting for alix is 38400 8N1, bios should be 0.99h) 
+ 
+== F. Applying Updates ==
+ For small changes there is a shortcut in the build (to save you some coffee ;-)). Pick the situation applicable
+ 1. First lets pump it's source to the latest version 
+ {{{
+ $ svn up /root/nanobsd
+ }}}
+ 2. Set your favorite root password to be used in the image 
+ {{{ 
+ $ 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.
+ 3. Next step depends on the kind of changes:
+    a. Only changes in kernel options - `kernel.wleiden` altered - ETA 0:45
+    {{{
+    $ sh /usr/src/tools/tools/nanobsd/nanobsd.sh -w -c /root/nanobsd/cfg/nanobsd.wleiden
+    }}}
+    a. Only changes in world options - `CONF_{BUILD,COMMON,INSTALL}` in  `nanobsd.wleiden` altered - ETA 2:00 - 6:00
+    {{{
+    $ sh /usr/src/tools/tools/nanobsd/nanobsd.sh -k -c /root/nanobsd/cfg/nanobsd.wleiden
+    }}}
+    a. _NO_ changes in build options - any other file altered - ETA 0:10
+    {{{
+    $ sh /usr/src/tools/tools/nanobsd/nanobsd.sh -b -c /root/nanobsd/cfg/nanobsd.wleiden
+    }}} 
+
+= G, Development =
+
+== Handy tools ==
+Some handy tools are available in the /tools directory, such as
+ * /tools/wl-version : to get information on the configuration that is running
+ * /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'''!)