NSLU2-Linux
view · edit · print · history

Info.RamHackU2 History

Hide minor edits - Show changes to markup

February 07, 2006, at 08:15 PM by endecotp --
Changed lines 14-15 from:

particular, users of flash drives might like it's simplicity.

to:

particular, users of flash drives might like its simplicity.

October 17, 2004, at 05:04 PM by tman --
Changed line 17 from:
  • You can still use a single vfat partition (this means your usb disk is still easily windows interoperable).
to:
  • You can still use a single VFAT partition (this means your USB disk is still easily Windows interoperable).
Changed line 24 from:
  • No extra ram (only 7MB free after boot).
to:
  • No extra RAM (only 7MB free after boot).
Changed line 79 from:

Since the ufs flash drive is still formated as FAT, you can't

to:

Since the USB flash drive is still formated as VFAT, you can't

Changed line 95 from:

If you are using WinZip to untar and extract the files to the flash drive on a windows box (as I did) then you must set the option in winzip NOT to change the CRLF formatting:

to:

If you are using WinZip to untar and extract the files to the flash drive on a Windows box (as I did) then you must set the option in WinZip NOT to change the CRLF formatting:

October 17, 2004, at 01:10 PM by tman --
Changed line 1 from:

What is RamHackU2?

to:

What is RamHackU2?

Changed line 5 from:

What defines RamHackU2?

to:

What defines RamHackU2?

Changed line 11 from:

Why keep this approach around when there are more sophisticated firmwares available?

to:

Why keep this approach around when there are more sophisticated firmwares available?

Changed line 30 from:

I'll describe how to use one of them in a usb flash disk configuration:

to:

I'll describe how to use one of them in a usb flash disk configuration:

September 19, 2004, at 09:05 PM by mrthreeplates --
Changed lines 76-77 from:

You can do this easily with a simple script in your hacks/rc.d directory.

to:

You can do this easily with a simple script in your hacks/rc.d directory (not yet provided...).

September 19, 2004, at 09:03 PM by mrthreeplates --
Changed line 46 from:

Remove the flash drive first. See the FAQ for more info.

to:

Remove the flash drive first. See the http://www.nslu2-linux.org/wiki/Main/FAQ FAQ for more info.

September 19, 2004, at 04:32 AM by ka6sox --
Changed line 19 from:
  • No regular NSLU2 state is kept on the disk (e.g. no passwords, etc). This is really a side effect of Linksys's lack of support for USB flash drives on the NSLU2. See the http://www.nslu2-linux.org/wiki/Main/FAQ FAQ (why doesn't this link work???).
to:
  • No regular NSLU2 state is kept on the disk (e.g. no passwords, etc). This is really a side effect of Linksys's lack of support for USB flash drives on the NSLU2. See the http://www.nslu2-linux.org/wiki/Main/FAQ FAQ.
September 19, 2004, at 04:32 AM by ka6sox --
Changed line 19 from:
  • No regular NSLU2 state is kept on the disk (e.g. no passwords, etc). This is really a side effect of Linksys's lack of support for USB flash drives on the NSLU2. See the FAQ FAQ? (why doesn't this link work???).
to:
  • No regular NSLU2 state is kept on the disk (e.g. no passwords, etc). This is really a side effect of Linksys's lack of support for USB flash drives on the NSLU2. See the http://www.nslu2-linux.org/wiki/Main/FAQ FAQ (why doesn't this link work???).
September 19, 2004, at 04:30 AM by ka6sox --
Changed line 1 from:

What is RamHackU2?

to:

What is RamHackU2?

Changed line 5 from:

What defines RamHackU2?

to:

What defines RamHackU2?

September 18, 2004, at 09:05 PM by mrthreeplates --
Changed line 19 from:
  • No regular NSLU2 state is kept on the disk (e.g. no passwords, etc). This is really a side effect of Linksys's lack of support for USB flash drives on the NSLU2. See the FAQ.
to:
  • No regular NSLU2 state is kept on the disk (e.g. no passwords, etc). This is really a side effect of Linksys's lack of support for USB flash drives on the NSLU2. See the FAQ FAQ? (why doesn't this link work???).
Changed line 83 from:

If you intend to use the thttpd web server, see the HowTo Recipes section

to:

If you intend to use the thttpd web server, see the HomePage HowTo? Recipes section

Changed line 85 from:

to avoid the problem with the WatchDog? script. This will require some

to:

to avoid the problem with the WatchDog script. This will require some

Changed line 94 from:

If you are using WinZip? to untar and extract the files to the flash drive on a windows box (as I did) then you must set the option in winzip NOT to change the CRLF formatting:

to:

If you are using WinZip to untar and extract the files to the flash drive on a windows box (as I did) then you must set the option in winzip NOT to change the CRLF formatting:

September 18, 2004, at 08:57 PM by mrthreeplates --
Added line 76:

You can do this easily with a simple script in your hacks/rc.d directory.

Changed lines 83-88 from:

If you intend to use the thttpd web server, note that the WatchDog? script will be broken and you may want to fix it. See the following. This post also has info on how the second web server instance is set up. You should also carefully review your web server .conf script to make sure thttpd is setup the way you want. Do check out thttpd's man page.

http://groups.yahoo.com/group/nslu2-linux/message/1223
to:

If you intend to use the thttpd web server, see the HowTo Recipes section for instructions. You will want to copy and rename the thttpd binary to avoid the problem with the WatchDog? script. This will require some slight modifications to your startup scripts in your hacks/rc.d directory. You should also carefully review your web server .conf script to make sure thttpd is setup the way you want.

Deleted line 93:
Changed line 97 from:

uncheck: TAR file smart CR/LF conversion

to:

uncheck: TAR file smart CR/LF conversion

September 18, 2004, at 08:35 PM by MattMcN --
Added lines 92-97:

If you are using WinZip? to untar and extract the files to the flash drive on a windows box (as I did) then you must set the option in winzip NOT to change the CRLF formatting:

Options -> Configuration... -> Miscellaneous
uncheck: TAR file smart CR/LF conversion

September 17, 2004, at 06:44 AM by mrthreeplates --
Changed lines 17-18 from:
  • You can still use a single vfat partition (this means

your usb disk is still easily windows interoperable).

to:
  • You can still use a single vfat partition (this means your usb disk is still easily windows interoperable).
Changed lines 19-21 from:
  • No regular NSLU2 state is kept on the disk (e.g. no passwords, etc). This

is really a side effect of Linksys's lack of support for USB flash drives on the NSLU2. See the FAQ.

to:
  • No regular NSLU2 state is kept on the disk (e.g. no passwords, etc). This is really a side effect of Linksys's lack of support for USB flash drives on the NSLU2. See the FAQ.
September 17, 2004, at 06:44 AM by mrthreeplates --
Changed line 8 from:

run startup scripts to install your favorite hacks. This means it boots

to:

run startup script(s) to install your favorite hacks. This means it boots

Changed line 11 from:

Why keep it around when there are more sophisticated firmwares available?

to:

Why keep this approach around when there are more sophisticated firmwares available?

Changed lines 17-18 from:
  • You can still use a single vfat partition (usb disk is still easily windows interoperable).
to:
  • You can still use a single vfat partition (this means

your usb disk is still easily windows interoperable).

Changed lines 20-21 from:
  • No regular NSLU2 state is kept on the disk (e.g. no passwords, etc).
  • Minimal writes to the usb device (minimizing write wear).
to:
  • No regular NSLU2 state is kept on the disk (e.g. no passwords, etc). This

is really a side effect of Linksys's lack of support for USB flash drives on the NSLU2. See the FAQ.

  • Minimizes writes to the usb device (reducing write wear).
Changed line 45 from:

That's it. No other changes.

to:

That's it, no other changes.

Changed lines 47-48 from:

Note that flash drive users occasionally have problems upgrading firmware with the flash drive installed.

to:

Note: that flash drive users occasionally have problems upgrading firmware with the flash drive installed.

Changed lines 87-89 from:

has info on how the second web server instance is set up:

to:

has info on how the second web server instance is set up. You should also carefully review your web server .conf script to make sure thttpd is setup the way you want. Do check out thttpd's man page.

Changed line 94 from:
http://groups.yahoo.com/group/nslu2-linux/message/671
to:
http://groups.yahoo.com/group/nslu2-linux/message/671
September 17, 2004, at 06:38 AM by mrthreeplates --
Changed lines 28-29 from:

http://groups.yahoo.com/group/nslu2-linux/files/Custom%20Firmware/

to:
http://groups.yahoo.com/group/nslu2-linux/files/Custom%20Firmware/
Changed lines 44-48 from:

It order to have fun with your NSLU2, you will also need to create

to:

Note that flash drive users occasionally have problems upgrading firmware with the flash drive installed. Remove the flash drive first. See the FAQ for more info.

In order to have fun with your NSLU2, you will also need to create

Changed lines 50-51 from:

http://groups.yahoo.com/group/nslu2-linux/files/

to:
http://groups.yahoo.com/group/nslu2-linux/files/
Changed line 62 from:

http://groups.yahoo.com/group/nslu2-linux/message/484

to:
http://groups.yahoo.com/group/nslu2-linux/message/484
Changed line 65 from:

http://groups.yahoo.com/group/nslu2-linux/message/772

to:
http://groups.yahoo.com/group/nslu2-linux/message/772
Changed lines 68-69 from:

http://groups.yahoo.com/group/nslu2-linux/message/612

to:
http://groups.yahoo.com/group/nslu2-linux/message/612
http://groups.yahoo.com/group/nslu2-linux/message/631
Changed lines 75-76 from:

http://groups.yahoo.com/group/nslu2-linux/message/980

to:
http://groups.yahoo.com/group/nslu2-linux/message/980
Changed lines 85-86 from:

http://groups.yahoo.com/group/nslu2-linux/message/1223

to:
http://groups.yahoo.com/group/nslu2-linux/message/1223
Changed lines 88-89 from:

http://groups.yahoo.com/group/nslu2-linux/message/1385

to:
http://groups.yahoo.com/group/nslu2-linux/message/1385
http://groups.yahoo.com/group/nslu2-linux/message/671
September 17, 2004, at 06:31 AM by mrthreeplates --
Deleted line 23:
Changed lines 32-33 from:

NSLU2_V23R25_rc_flash.bin.gz

to:
  • NSLU2_V23R25_rc_flash.bin.gz
Changed lines 38-44 from:

F=/share/flash/data/hacks/rc.flash

if [ -f $F ] ; then

/bin/sh $F >$F.out 2>&1

fi

to:
F=/share/flash/data/hacks/rc.flash
if [ -f $F ] ; then
/bin/sh $F >$F.out 2>&1
fi
Changed lines 51-54 from:

hacks_romfs.tar

romfs.tar.gz

to:
  • hacks_romfs.tar
  • romfs.tar.gz
Deleted lines 69-73:

Since the ufs flash drive is still formated as FAT, you can't use any of the chmod, chown commands on files. This has implications as you have to be careful how you configure security for your web server and/or ftp server.

Changed lines 75-76 from:

If you intend to use the web server, note that the WatchDog? script will be broken and you may want to fix it. See:

to:

Since the ufs flash drive is still formated as FAT, you can't use any of the chmod, chown commands on files. This has implications as you have to be careful how you configure security (e.g. for your web server and/or ftp server).

If you intend to use the thttpd web server, note that the WatchDog? script will be broken and you may want to fix it. See the following. This post also has info on how the second web server instance is set up:

Added lines 86-88:

Additional info on configuring the ftpd server provided in romfs above:

http://groups.yahoo.com/group/nslu2-linux/message/1385

September 17, 2004, at 06:23 AM by mrthreeplates --
Changed line 1 from:

mrthreeplates' new project area ...

to:

What is RamHackU2?

Changed lines 3-12 from:

I'm proposing that we keep around the idea of booting with a simple diversion script in the stock ramdisk (i.e. the very first hacked f/w).

Booting from ramdisk has some advantages (mostly for flash drives):

    You can still use a single vfat partition (usb disk is still easily windows interoperable).
    Each boot is clean with no residue from prior boots (e.g. repeatible).
    No regular NSLU2 state is kept on the disk (e.g. no passwords, etc).
    Minimal writes to the usb device (minimizing write wear).
    Mods to stock firmware are trivial.
to:

A silly name for the first hacked firmwares that appeared for the NSLU2.

What defines RamHackU2?

It is a nearly 100% stock Linksys firmware, but with a few lines added to run startup scripts to install your favorite hacks. This means it boots from and retains the firmware's ramdisk.

Why keep it around when there are more sophisticated firmwares available?

Well, it does have some advantages that a few might find useful. In particular, users of flash drives might like it's simplicity.

Advantages:

  • You can still use a single vfat partition (usb disk is still easily windows interoperable).
  • Each boot is clean with no residue from prior boots (e.g. repeatible).
  • No regular NSLU2 state is kept on the disk (e.g. no passwords, etc).
  • Minimal writes to the usb device (minimizing write wear).
  • Mods to stock firmware are trivial (simplicity).
Changed lines 24-26 from:
    No extra ram.
    Hacks need to be installed every time at boot.
    ...
to:
  • No extra ram (only 7MB free after boot).
  • Hacks need to be installed every time at boot.

Two sample firmwares can be found at:

http://groups.yahoo.com/group/nslu2-linux/files/Custom%20Firmware/

I'll describe how to use one of them in a usb flash disk configuration:

NSLU2_V23R25_rc_flash.bin.gz

This firmware was constructed by taking the stock linksys firmware and (with the use of the slugtool) added 4 lines to the /etc/rc.d/rc.local.

F=/share/flash/data/hacks/rc.flash

if [ -f $F ] ; then

/bin/sh $F >$F.out 2>&1

fi

That's it. No other changes.

It order to have fun with your NSLU2, you will also need to create a rc.flash file. You can use and take a look at what I did. Go to:

http://groups.yahoo.com/group/nslu2-linux/files/

And download the following files:

hacks_romfs.tar

romfs.tar.gz

Extract and untar them both in the /share/flash/data directory of your flash drive.

See the following posts for more details:

Re: the firmware: http://groups.yahoo.com/group/nslu2-linux/message/484

Re: The hacks_romfs.tar http://groups.yahoo.com/group/nslu2-linux/message/772

Re: The romfs.tar.gz http://groups.yahoo.com/group/nslu2-linux/message/612

Finally, A few extra issues I've discovered along the way:

Since the ufs flash drive is still formated as FAT, you can't use any of the chmod, chown commands on files. This has implications as you have to be careful how you configure security for your web server and/or ftp server.

For further write wear minimization, try remounting your flash disk with noatime as described in:

http://groups.yahoo.com/group/nslu2-linux/message/980

If you intend to use the web server, note that the WatchDog? script will be broken and you may want to fix it. See:

http://groups.yahoo.com/group/nslu2-linux/message/1223

September 16, 2004, at 11:14 PM by rwhitby --
Changed lines 8-9 from:
    You can still use a single vfat partition (usb disk is still easily 

windows interoperable).

to:
    You can still use a single vfat partition (usb disk is still easily windows interoperable).
September 16, 2004, at 11:13 PM by rwhitby --
Changed lines 1-18 from:

mrthreeplates' new project area ...

to:

mrthreeplates' new project area ...

I'm proposing that we keep around the idea of booting with a simple diversion script in the stock ramdisk (i.e. the very first hacked f/w).

Booting from ramdisk has some advantages (mostly for flash drives):

    You can still use a single vfat partition (usb disk is still easily 

windows interoperable).

    Each boot is clean with no residue from prior boots (e.g. repeatible).
    No regular NSLU2 state is kept on the disk (e.g. no passwords, etc).
    Minimal writes to the usb device (minimizing write wear).
    Mods to stock firmware are trivial.

Of course, there are disadvantages:

    No extra ram.
    Hacks need to be installed every time at boot.
    ...
September 16, 2004, at 11:11 PM by rwhitby --
Changed line 1 from:

Describe HomePage here.

to:

mrthreeplates' new project area ...

view · edit · print · history · Last edited by endecotp.
Based on work by tman, mrthreeplates, ka6sox, MattMcN, and rwhitby.
Originally by rwhitby.
Page last modified on February 07, 2006, at 08:15 PM