Linux Kernel 2.6 Installation on Buffalo Linkstation/KuroBox/HG/HS/Terastation | hvkls.dyndns.org

| | Search · Suche | Version: Wed, 12 Nov 2008 06:34:42 CET

Policy Regeln | Search Suche

The webinstaller is the recommended installation method, and 'nice' to the server. If you want to install the kernel manually, please use the 'dry run' mode to download the components!

• USE AT YOUR OWN RISK

• Deutschsprachige Hilfe auf Anfrage

  Es wäre leider zu zeitaufwendig für mich, eine deutschsprachige Version dieses Dokuments zu pflegen. Falls Sie nach Durchsicht des englischsprachigen Teils deutschsprachige Hilfe benötigen sollten, schreiben Sie mir bitte unter Angabe Ihrer korrekten Antwortadresse, Ihres Linkstation- oder Terastation-Modells und des Firmwaretyps.

• Overview

  The webinstaller is a mature, 'smart', automatic retrieval and installation procedure. It can install or just download my (André's) version of the Linux 2.6.* bootloader, kernel (or variant), modules, and headers onto your PPC based Linkstation, Linkstation HG, Linkstation HS, Kuro Box, Kuro HG, or Terastation (experimental) for you, in an easy-to-use and noninvasive way.

  The webinstaller comes as a single command with a user-friendly design: Download it, unpack it, run it, reboot into the new kernel of your choice. No firmware flashing required, your original kernel will be preserved. You can choose which kernel you would like to boot into any time.

  Screen Shots

  
  The webinstaller, on a 'dry run' for (the obsolete) variant-rtc

  
  The webinstaller, user contributed screen shot

  The total amount of data transferred varies, but is typically around 10 to 20 MB, which would take up to two hours on a 56K V.90 modem line. The modules packages is currently about five times, the (optional) headers package eight times the size of the kernel package. Be patient!

  Details

  The webinstaller can upgrade itself if necessary, identify your system, download files accordingly, resume interrupted downloads, check the file integrity, and install the downloaded files for you, into a temporary location if you insist. It can also adjust the system configuration, if necessary and not conflicting with your own modifications.

  Whenever it runs into trouble, the webinstaller quits and suggests a solution. The solution is usually you re-run the webinstaller, so it can make use of the latest version of a specific component. This may happen several times to you, and is a feature.

  If the webinstaller shouldn't know of your Operating System, it would fall back to a 'dry run' automatically.

• Different systems, different needs

  The webinstaller supports a variety of systems and configurations. Check them one-by-one; they are listed in alphabetical order here. If a condition doesn't apply, jump to the next. More than one of the following conditions may apply. Everyone must complete the final step, as it downloads and installs the webinstaller itself. One time pays for all here: Once installed, the webinstaller can do all the checking and downloading itself.

  Prerequisites (first-time installation only)

  • Anyone whose /etc/fstab use internal /dev/sd* partitions, Gentoo users

    In order to check your setup, run:

    grep -E "^/.* / " /etc/fstab | grep -q "/dev/hda1" || echo "fstab WARNING"

    If you don't see a warning, you are good. If you do, you must take post-installation action.

  • Linkstation HS users; also anyone experiencing five-minute-reboot cycles

    touch /boot/variant-notmp
wget http://hvkls.dyndns.org/downloads/latest-upgradehelper.tar.gz
tar -C / -xvzf latest-upgradehelper.tar.gz
/etc/init.d/avr_evtd start

  • OpenLink users (only; including OpenLink on Linkstation HS and Terastation without Debian users):

    wget http://hvkls.dyndns.org/downloads/latest-openlinkhelper.tar.gz
tar -C / -xvzf latest-openlinkhelper.tar.gz
chmod 1777 /tmp

  • Terastation users (only):

    Experimental Tera Setup

  • UBoot users (only; see Advanced Usage: Variants for an explanation)

    mkdir /boot 2>/dev/null
touch /boot/variant-uboot

  Anyone (all users must complete this final step, once):

  wget http://hvkls.dyndns.org/downloads/latest-webinstaller.tar.gz
tar -C / -xvzf latest-webinstaller.tar.gz

  Once you've completed these initial steps (one time pays for all), the webinstaller is ready to go, whenever you want to upgrade your kernel package.

• Usage

  Basic Usage

  The webinstaller comes as a single command with two names, explained below.

  Non-developers (95% of all users) will and should choose the 'real' installation right away. You would most likely not benefit from a 'dry run'. The built-in validation routines are designed to prevent the installation of invalid components anyway. Your own modifications to the configuration files are respected.

  The 'dry run' mode is practically obsolete. Remember, I told you!

  'Real' Installation

  /usr/local/sbin/webinstaller-kernelinst.sh

  'Real', 'easy', 'automatic', 'recommended', 'save-your-time-and-my-bandwidth' installation into /. The installer will replace existing files on your running system without notification when expanding the downloaded files, which sounds scarier than it is. Problematic downloads are moved to /tmp/ for further inspection.

  'Dry Run'

  /usr/local/sbin/webinstaller-kernelinst-dryrun.sh

  The 'dry run' won't tell you 'if the kernel would work' or the like! If you don't plan to interfere with the webinstaller, which is strongly recommended, skip this step.

  The 'dry run' is for expert evaluation only, and safe to use. It will not only download, but also install everything into /tmp/kernel-inst/, so you can take your time to investigate what would be done, and make backups if necessary; or save the downloaded components to a different place. Problematic downloads are moved to /tmp/ for further inspection.

  Advanced Usage: Variants

  Users can, optionally, instruct the webinstaller to install kernel variants with U-Boot support. For maximum compatibility, you could override the webinstaller's very reliable automatic detection, and force the selection of either the LS1/Kuro or the HG/KuroHG/HS/Tera flavor. The same goes for the latest (default) or legacy kernel package. A separate NFS optimized legacy kernel is also available.

  Terastation users need to choose the tera flavor.

  If you need the kernel headers, which 95% of all users won't, please refer to headers.

• Post-Installation

  rm -r /boot/variant-notmp /kernel-inst 2>/dev/null

  Set up avr_evtd, as described in README-upgradehelper. Your modifications will 'survive' future upgrades.

  If you got the mentioned fstab warning, your system failed the test for the standard IDE driver setup. By editing /etc/fstab or /etc/default/boot_new.sh_local, this can be addressed in a very flexible manner.

  Important! Changing your /etc/fstab to inadequate values would prevent your system from booting and might force you to reflash the firmware.

  Example /etc/fstab (do not copy it blindly):

  'Incorrect':

  /dev/sda1 / ext3 defaults,nodiratime,noatime 0 0
/dev/sda2 swap swap sw,pri=1 0 0
/dev/sda3 /mnt ext3 defaults,nodiratime,noatime 0 0

  'Correct' (standard setup):

  /dev/hda1 / ext3 defaults,nodiratime,noatime 0 0
/dev/hda2 swap swap sw,pri=1 0 0
/dev/hda3 /mnt ext3 defaults,nodiratime,noatime 0 0

• Troubleshooting

  If you should run into an error, the script will help you.

  Wait for the webinstaller to either complete or fail. It will tell you unambiguously if an error occurs. Restarting the webinstaller because it seems to take too long, is just a waste of time, it's not hung. It doesn't make sense to run more than one instance of the webinstaller at the same time, either.

  Kernel modules consume a lot of disk space. Any modules from previous installations would have to be removed manually. Always keep the 2.4* and the 2.6* modules with the highest version number to be on the safe side.
  rm -r /lib/modules/2.6.old.versions-only

• Linkstations, Linkstation HGs, Linkstation HSs, Kuro Boxes, and Kuro HGs with Debian and Buffalo style init, or Gentoo startup sequence, are supported out-of-the-box. If the webinstaller can neither find /etc/rcS.d/, /etc/rc.d/rcS.d/, nor /etc/gentoo-release, it will assume you're on a system with non-SysV or Gentoo startup method, and switch to a 'dry run' automatically. The kernel and modules will work for you in this case regardless, but you'll have to install them and a suitable bootloading mechanism manually (loader*.o is provided). Take a look at /tmp/kernel-inst/boot/ when the script has finished to learn more.
  If you don't know what the heck I'm talking about, don't worry, you should be fine.
• If you decide against automatic installation, you must check README-upgradehelper for specific additional installation requirements. Please use the 'dry run' mode to download the files to ease the load on the server!
• Additional documentation is available in the Downloads section.

http://hvkls.dyndns.org/downloads/documentation/README-webinstaller.html