From: <nsl...@li...> - 2004-11-26 10:35:42
|
This BitKeeper patch contains the following changesets: rwhitby@home.(none)|ChangeSet|20041126103504|62420 # ID: ke...@ze...|ChangeSet|20030602211901|40961|4f9b117aa66a8ba3 # User: rwhitby # Host: home.(none) # Root: /home/openembedded/packages # Patch vers: 1.3 # Patch type: REGULAR == ChangeSet == ke...@ze...|ChangeSet|20030602211901|40961|4f9b117aa66a8ba3 rwhitby@home.(none)|ChangeSet|20041125131602|62385 D 1.2680 04/11/26 21:05:04+10:30 rwhitby@home.(none) +5 -0 B ke...@ze...|ChangeSet|20030602211901|40961|4f9b117aa66a8ba3 C c Enabled mounting of external drives earlier in the Unslung boot process, so that the rc, rc.sysinit, and rc.1 scripts can be diverted by external diversion scripts on an attached drive. K 62420 P ChangeSet ------------------------------------------------ 0a0 > rwhitby@home.(none)|nslu2-binary-only/nslu2-unslung-ramdisk_2.3r25.oe|20040922145912|65262|a312506088a502b8 rwhitby@home.(none)|nslu2-binary-only/unslung-standard-rootfs_2.3r25.oe|20041126102611|01656 > rwhitby@home.(none)|nslu2-binary-only/unslung-ramdisk-2.3r25/README|20041106113831|05575|970ad49f851aaaf4 rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/README|20041126103218|15104 > rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/rc-diversion.patch|20041121102533|33550|34ef73b318bcf2b rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/rc-diversion.patch|20041126092230|55954 > rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/rc.1-diversion.patch|20041121102533|34770|6565bae973912a88 rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/rc.1-diversion.patch|20041126071756|12326 > rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/rc.sysinit-diversion.patch|20041121102533|49725|9f5e7c53b6b81877 rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/rc.sysinit-diversion.patch|20041126090336|05913 == nslu2-binary-only/unslung-standard-rootfs_2.3r25.oe == rwhitby@home.(none)|nslu2-binary-only/nslu2-unslung-ramdisk_2.3r25.oe|20040922145912|65262|a312506088a502b8 rwhitby@home.(none)|nslu2-binary-only/unslung-standard-rootfs_2.3r25.oe|20041125131111|01654 D 1.61 04/11/26 20:56:11+10:30 rwhitby@home.(none) +2 -2 B ke...@ze...|ChangeSet|20030602211901|40961|4f9b117aa66a8ba3 C c Bumped the version. K 1656 O -rw-rw-r-- P nslu2-binary-only/unslung-standard-rootfs_2.3r25.oe ------------------------------------------------ D3 1 I3 1 PR = "r27" D5 1 I5 1 UNSLUNG_VERSION = "3.8-alpha" == nslu2-binary-only/unslung-rootfs-2.3r25/README == rwhitby@home.(none)|nslu2-binary-only/unslung-ramdisk-2.3r25/README|20041106113831|05575|970ad49f851aaaf4 rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/README|20041125130233|13786 D 1.11 04/11/26 20:47:38+10:30 rwhitby@home.(none) +121 -96 B ke...@ze...|ChangeSet|20030602211901|40961|4f9b117aa66a8ba3 c First draft of the README for Unslung 3.x firmware. K 63956 O -rw-rw-r-- P nslu2-binary-only/unslung-rootfs-2.3r25/README ------------------------------------------------ D1 1 I1 1 UNSLUNG-3.x family release README D3 3 I5 4 Unslung is a replacement firmware image for the Linksys NSLU2 which is designed to allow you to make changes to the root filesystem (including the installation of downloadable packages) while still providing all the standard product functionality. D11 1 I11 1 The changes in the UNSLUNG 3.x firmware from the standard Linksys D23 10 I32 17 1) It is strongly recommended that you test telnet Redboot access first. See http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot \ 2) Because you can now make changes to the root filesystem in the internal flash storage, you no longer need to have an external disk to use the Unslung firmware (except if you want to install more than what can fit in the meagre spare space in the internal flash storage). \ 3) If you do want to use an external disk as the target for package installation, then it is absolutely required that the disk is (or has previously been) formatted by the NSLU2. It is possible to upgrade from Unslung 1.x or Unslung 2.x to Unslung 3.x without reformatting your disk. The unsling script will not touch anything in /unslung or /opt on your disk, so make sure all your file modifications are in those directories, as you were warned in the README file in Unslung 1.x and Unslung 2.x :-) D37 1 I37 20 \ 2) If you are installing Unslung 3.x onto an NSLU2 unit which has the standard Linksys firmware or Unslung versions 1.x or 2.x installed, then just flash unslung-standard-3.x.img as you normally would flash new firmware (using the web interface Upgrade Firmware page). However, you must ensure that you have confirmed access to one of the upgrade methods described in step 3 below so that you will be able to upgrade your firmware in the future, as the standard web interface is not operational in Unslung 3.x or later. \ 3) If you are installing Unslung 3.x onto an NSLU2 unit which already has Unslung version 3.x installed, then you cannot use the normal web interface to flash a new version. Because Unslung 3.x runs directly from the internal flash, then it is not possible to flash new firmware while Unslung is running. In this case, you must use an alternate method to flash the new firmware. Instructions for how to do this can be found at: \ http://www.nslu2-linux.org/wiki/HowTo/InstallUnslungFirmware \ I38 1 \ D44 1 I44 7 0) Note that this only has to be done when you update the firmware, and because Unslung 3.x now runs completely from the internal flash memory, it is no longer necessary to "unsling" to an external disk unless you wish to store downloadable packages on that disk - which you will probably want to do, because the internal flash memory only has enough spare room to one or two very small packages. \ I45 1 \ D51 2 I52 4 interface at this point (as no disks are attached, the default username and password is the only way to access the Management web pages). \ I53 1 \ D58 3 I60 9 \ 4) In the telnet session, run "/sbin/unsling". Note that starting with Unslung 3.x, the external disk is no longer used for the root filesystem, so only a few documentation files will be copied to the "conf" partition (not the "data" partition). Once you "unsling" to an external disk on a particular port (Disk 1 or Disk 2), it is important that you keep that disk continually plugged into that same port whenever the NSLU2 is turned on. \ I63 1 \ D66 2 I67 1 Congratulations, you're now Unslung! D69 1 I69 1 Make sure you add an entry to the "The Unslung 3.x" table in the Yahoo D73 3 I75 22 normally (apart from not being able to upgrade your firmware in the future using the web interface). But to customize things, you'll be downloading packages and adding stuff to the /unslung directory on the external disk (or even in the internal flash memory) using diversion scripts. \ If you "unsling" an external disk, then downloaded packages will be installed onto that external disk. The number of packages that you can install is only limited by the size of the "conf" partition on the external disk. \ If you are experienced with the Linux operating system, then you can also make changes directly to the root filesystem, and these changes are persistent across reboots. \ You are advised to use diversion scripts (see below) on an external disk to modify the behaviour of the NSLU2 rather than editing system files directly (as this will allow you to upgrade the Unslung firmware in the future without having to make all your changes again). \ If you do need to edit system files directly, then you can use the "resling" script to save and load your modified system files. D79 3 I81 4 Diversion scripts go into /unslung (which is normally a symbolic link to the unslung directory on the conf partition of an external disk). You can divert as many or as few scripts as you like. Simply add the name of the standard rc script into /unslung and it will be run. D106 8 I113 3 1) Run "ipkg update" on the NSLU2. 2) Run "ipkg list" to see the available packages. 3) Run "ipkg install <package-name>" to install them. D117 44 I160 16 1) The unsling firmware and associated scripts will never touch any files under /unslung or /opt, so please store all your additional files there. \ 2) The diversion of startup scripts is done at the lowest granularity, so you can, for instance, just divert the rc.xinetd script if you want, and leave all the others unchanged. \ 3) The diversion mechanism allows you to add to, or replace, the Linksys script functionality. \ 4) Note that telnet is not enabled by default - there is an openssh package available to replace telnet access with secure shell access. The rationale behind not enabling it by default is to ensure that an NSLU2 with Unslung firmware has the same network footprint as the standard firmware. D162 1 I162 1 5) This simple diversion script will enable telnet on boot D164 2 I165 3 [ Store the following in /unslung/rc.xinetd ] \ #!/bin/sh D171 10 I180 3 6) The Unslung firmware will automatically execute any scripts which are in /opt/etc/init.d - and this is where any packages put their startup scripts so that they execute on each boot. rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/README|20041126101738|63956 D 1.12 04/11/26 21:02:18+10:30 rwhitby@home.(none) +6 -0 B ke...@ze...|ChangeSet|20030602211901|40961|4f9b117aa66a8ba3 C c Added the ChangeLog for 3.8 K 15104 O -rw-rw-r-- P nslu2-binary-only/unslung-rootfs-2.3r25/README ------------------------------------------------ I298 6 \ 3.8: \ Enabled mounting of external drives earlier in the boot process, so that the rc, rc.sysinit, and rc.1 scripts can be diverted by external diversion scripts on an attached drive. == nslu2-binary-only/unslung-rootfs-2.3r25/rc-diversion.patch == rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/rc-diversion.patch|20041121102533|33550|34ef73b318bcf2b rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/rc-diversion.patch|20041125130233|50025 D 1.3 04/11/26 17:48:23+10:30 rwhitby@home.(none) +7 -6 B ke...@ze...|ChangeSet|20030602211901|40961|4f9b117aa66a8ba3 c Mount disks early, and create a symlink pseudo-mountpoint. K 61069 O -rw-rw-r-- P nslu2-binary-only/unslung-rootfs-2.3r25/rc-diversion.patch ------------------------------------------------ D1 1 I1 1 --- nslu2-linksys-ramdisk-2.3r25/etc/rc~ 2004-07-27 23:37:55.000000000 -0400 D3 1 I3 1 @@ -1,4 +1,23 @@ I12 1 + # Wait for the USB disks to be recognised. D17 2 I18 2 + /bin/mount -t ext3 /dev/sda2 /share/hdd/conf + /bin/rm -rf /mnt/sda2 ; /bin/ln -s /share/hdd/conf /mnt/sda2 D22 2 I23 2 + /bin/mount -t ext3 /dev/sdb2 /share/flash/conf + /bin/rm -rf /mnt/sdb2 ; /bin/ln -s /share/flash/conf /mnt/sdb2 rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/rc-diversion.patch|20041126071823|61069 D 1.4 04/11/26 19:52:30+10:30 rwhitby@home.(none) +3 -5 B ke...@ze...|ChangeSet|20030602211901|40961|4f9b117aa66a8ba3 C c Made the sleep 5 unconditional - we are sleeping to allow the /proc/*_conn files to be created, so it's no good testing for them before the sleep. K 55954 O -rw-rw-r-- P nslu2-binary-only/unslung-rootfs-2.3r25/rc-diversion.patch ------------------------------------------------ D3 1 I3 1 @@ -1,4 +1,21 @@ D12 4 I15 2 +# Wait for the USB disks to be recognised. +sleep 5 == nslu2-binary-only/unslung-rootfs-2.3r25/rc.1-diversion.patch == rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/rc.1-diversion.patch|20041121102533|34770|6565bae973912a88 rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/rc.1-diversion.patch|20041125130233|02579 D 1.3 04/11/26 17:47:56+10:30 rwhitby@home.(none) +10 -2 B ke...@ze...|ChangeSet|20030602211901|40961|4f9b117aa66a8ba3 C c Unmount disks just before rc.bootbin is run. K 12326 O -rw-rw-r-- P nslu2-binary-only/unslung-rootfs-2.3r25/rc.1-diversion.patch ------------------------------------------------ D1 1 I1 1 --- nslu2-linksys-ramdisk-2.3r25/etc/rc.d/rc.1~ 2004-07-27 23:37:55.000000000 -0400 D3 1 I3 1 @@ -1,5 +1,17 @@ I8 8 + +if ( [ -f /proc/hd_conn ] ) ; then + /bin/umount /dev/sda2 +fi + +if ( [ -f /proc/hd2_conn ] ) ; then + /bin/umount /dev/sdb2 +fi == nslu2-binary-only/unslung-rootfs-2.3r25/rc.sysinit-diversion.patch == rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/rc.sysinit-diversion.patch|20041121102533|49725|9f5e7c53b6b81877 rwhitby@home.(none)|nslu2-binary-only/unslung-rootfs-2.3r25/rc.sysinit-diversion.patch|20041125130233|03715 D 1.3 04/11/26 19:33:36+10:30 rwhitby@home.(none) +3 -3 B ke...@ze...|ChangeSet|20030602211901|40961|4f9b117aa66a8ba3 C c Fixed the diversion script check. K 5913 O -rw-rw-r-- P nslu2-binary-only/unslung-rootfs-2.3r25/rc.sysinit-diversion.patch ------------------------------------------------ D11 3 I13 3 +if ( [ -f /mnt/sda2/unslung/rc.sysinit ] && . /mnt/sda2/unslung/rc.sysinit ) ; then return 0 ; fi +if ( [ -f /mnt/sdb2/unslung/rc.sysinit ] && . /mnt/sdb2/unslung/rc.sysinit ) ; then return 0 ; fi +if ( [ -f /unslung/rc.sysinit ] && . /unslung/rc.sysinit ) ; then return 0 ; fi # Patch checksum=bf079b10 |