WHITE RUSSIAN RC3
-----------------

  This is the third release candidate for whiterussian. For those of
  you not familiar with OpenWrt, whiterussian is the codename for the
  stable release that's replacing the old experimental releases.

What the heck are all these files?
  If you've been using OpenWrt you'll probably already know this, but
  for the benefit of those using OpenWrt for the first time:

  Squashfs files:
    The firmwares with "squashfs" in the filename use a combination of
    a readonly squashfs partition and a writable jffs2 partition. This
    gives you a /rom with all the files that shipped with the firmware
    and a writable root containing symlinks to /rom. This is considered
    the standard install.

    NOTE: The initial install will take a few minutes to boot --
    this is completely normal. During the initial bootup the jffs2
    partition and several symlinks are created.

  Jffs2 files:
    The firmwares with "jffs2" in the name are jffs2 only; all of the
    files are fully writable. The "4M" and "8M" in the filenames is a
    reference to the flash block size; most 4M flash chips use a block
    size of 64k while most 8M chips tend to use a 128k block size --
    there are some exceptions. The jffs2 partition needs to be formatted
    for the correct block size and hence the two versions.

    The jffs2 versions are for experienced users only -- these firmwares
    only have minimal support for failsafe mode.

    NOTE: With the jffs2 versions you'll get a "disk full" error message
    attempting to modify anything during the initial bootup; this is a
    side effect of the initial setup and will go away after a reboot. If
    you see this message, please reboot. Once again, this means reboot
    -- we're sick of answering this question.

  Which version should I use?
    The squashfs versions give you slightly more jffs2 space and are
    capable of booting even when the jffs2 filesystem is broken or
    corrupted.

    Unless you specifically require the jffs2 version, use the squashfs
    version. If you later decide you needed the jffs2 version you can
    easily convert on the fly -- just replace all the symlinks pointing
    to /rom with actual files, run "jffs2root --move" and reboot.

    TRX extension:
      These are the firmware in raw format, suitable for writing directly
      to the flash or for vendors that don't require a BIN file.

    BIN extension:
      Same as above but with a vendor specific header.

Upgrading from a previous openwrt install
  Backup /etc changes and package list:
    Before you consider to update please make a backup of your /etc 
    directory and make a package list with ipkg list_installed > ipkg.txt.
    If you reflash with mtd, you will have backups of all important data.
    NVRAM is not touched by an update.
  
  Backing up the old firmware:
    To backup the existing openwrt install, use the command:
      dd if=/dev/mtdblock/1ro of=/tmp/firmware.trx
    This will produce a file containing the trx of the current firmware
    (kernel and squashfs filesystems) followed by a dump of the jffs2
    partition (including all installed packages) following the trx data
    -- basically everything except the bootloader and NVRAM.

    To restore from such a file you'll need to use OpenWrt's mtd command:
      mtd -e linux -r write firmware.trx linux
    Other methods of reflashing are likely to stop at the end of the trx
    data, before restoring the jffs2 data.

  Squashfs:
    In most cases, reflashing will not erase the jffs2 filesystem. The
    chances of jffs2 being corrupted or erased will depend on the sizes
    of the old and new firmware. If the new firmware is much larger then
    the jffs2 partition gets smaller and the existing data gets truncated.
    The NVRAM configuration will not be touched.

    If you're upgrading remotely, you may wish to set no_root_swap=1 in
    NVRAM. This will prevent the system from attempting to boot off the
    jffs2 partition. After the system boots you can unset this variable
    and manually fix the jffs2 partition, or simply run firstboot.

  Jffs2:
    Reflashing WILL erase the filesystem; nvram configuration will not
    be touched. Please backup any changes you've made to the filesystem
    before reflashing.

  Reflashing:
    To reflash from openwrt you will need a TRX file, generally the
    "openwrt-brcm-2.4-squashfs.trx" file. Copy or wget this file into
    /tmp/ and run the following command to reflash --
      mtd -r write openwrt-brcm-2.4-squashfs.trx linux
    After the command finishes, the router will automatically restart.
    If you switch between squashfs and jffs2 based openwrt installations
    please use mtd -e linux -r write openwrt-brcm-2.4-squashfs.trx linux,
    so that the flash is erased before writing.