NSLU2-Linux
view · edit · print · history

Unslung.SuggestedChangesToTheReadme History

Hide minor edits - Show changes to markup

November 23, 2008, at 11:52 AM by rwhitby --
Deleted line 0:

domcnamon

November 17, 2008, at 11:25 PM by darersitcna -- darersitcna
Added line 1:

domcnamon

December 22, 2007, at 02:58 AM by Dave Lane --
Changed line 24 from:

Ironically I cannot find a copy of the readme in either of the suggested locations; slug-firmware.net has a lot of binaries and source files listed but no obvious readme files, and although my /opt/doc directory contains both the readme and notes files, neither contain any information. (Unslung V2.3R63-uNSLUng-6.8-beta) If this is me being silly, please ignore this comment...

to:

<suggestion here>

Changed line 34 from:

<suggestion here>

to:

It would be good if there were a list of available commands and switches, with explainations and examples, etc.

Added line 37:
Changed lines 40-41 from:

It would be good if there were a list of available commands and switches, with explainations and examples, etc.

to:

Readme Preinstall-4), Line 114 says the flash drive has to be at least 256MB in size if used to install packages, /wiki/WhichUSBPortforUnslung6 says "2# The root device must be 512MB or larger in size." None of them say how big it has to be without installing packages or whether unslung can be installed without installing packages (for the people not understanding the need for packages)

Deleted line 43:
Deleted lines 45-50:

Readme Preinstall-4), Line 114 says the flash drive has to be at least 256MB in size if used to install packages, /wiki/WhichUSBPortforUnslung6 says "2# The root device must be 512MB or larger in size." None of them say how big it has to be without installing packages or whether unslung can be installed without installing packages (for the people not understanding the need for packages) INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

December 22, 2007, at 02:33 AM by Dave Lane --
Changed line 24 from:

Ironically I cannot find a copy of the readme in either of the suggested locations; slug-firmware.net has a lot of binaries and source files listed but no obvious readme files, and although my /opt/doc directory contains both the readme and notes files, neither contain any information. If this is me being silly, please ignore this comment...

to:

Ironically I cannot find a copy of the readme in either of the suggested locations; slug-firmware.net has a lot of binaries and source files listed but no obvious readme files, and although my /opt/doc directory contains both the readme and notes files, neither contain any information. (Unslung V2.3R63-uNSLUng-6.8-beta) If this is me being silly, please ignore this comment...

December 22, 2007, at 02:31 AM by Dave Lane --
Changed line 24 from:

<suggestion here>

to:

Ironically I cannot find a copy of the readme in either of the suggested locations; slug-firmware.net has a lot of binaries and source files listed but no obvious readme files, and although my /opt/doc directory contains both the readme and notes files, neither contain any information. If this is me being silly, please ignore this comment...

Deleted line 31:
Changed lines 34-35 from:

Readme Preinstall-4), Line 114 says the flash drive has to be at least 256MB in size if used to install packages, /wiki/WhichUSBPortforUnslung6 says "2# The root device must be 512MB or larger in size." None of them say how big it has to be without installing packages or whether unslung can be installed without installing packages (for the people not understanding the need for packages)

to:

<suggestion here>

Changed lines 39-44 from:

In step 4 it says "If the disk has not been previously formatted on the NSLU2, then now is

          the time to do that."

It would be worthwhile being explicit about how to do that rather than assuming the user will know to use the web interface rather than that inviting telnet session...

to:

It would be good if there were a list of available commands and switches, with explainations and examples, etc.

Added line 42:
Changed lines 45-56 from:

> First-time unslingers should NOT use -nopw

In the UNSLINGING DETAILS section of the README, it says "NOTE: There are two root passwords." and "Later in the process you can change both of them."

I decided to run /sbin/unsling with -nopw. I was happy with the default in /usr/local/passwd AND I KNEW that the external disk's password would be different. But the README line above led me to think it could be changed easily, and that the process would not let me reboot without knowing the appropriate password(s).

Of course, after rebooting with the external unslung disk attached, I couldn't telnet. http://www.nslu2-linux.org/wiki/FAQ/CantTelnetToMyNewlyUnslungNSLU2 is useless at this point. Eventually, I solved the problem by unslinging again WITHOUT -nopw.

I accept that using -nopw as a first-timer was a bit silly, but I thought the README would indicate AT THE APPROPRIATE TIME how to change the external disk's password. It doesn't. The 5.5 README had text at just the right point, but that text isn't present anymore. (5.5's UNSLINGING DETAILS section basically says "after unslinging, don't logout until you're sure you have got YOUR root password on the external disk", and references the CantTelnetToMyNewlyUnslungNSLU2 page.)

I think the README should 1) say first-timers have no reason AT ALL to use -nopw, and 2) reuse the dropped text from the 5.5 README.

to:

Readme Preinstall-4), Line 114 says the flash drive has to be at least 256MB in size if used to install packages, /wiki/WhichUSBPortforUnslung6 says "2# The root device must be 512MB or larger in size." None of them say how big it has to be without installing packages or whether unslung can be installed without installing packages (for the people not understanding the need for packages)

Added lines 51-76:

In step 4 it says "If the disk has not been previously formatted on the NSLU2, then now is

          the time to do that."

It would be worthwhile being explicit about how to do that rather than assuming the user will know to use the web interface rather than that inviting telnet session...

INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

> First-time unslingers should NOT use -nopw

In the UNSLINGING DETAILS section of the README, it says "NOTE: There are two root passwords." and "Later in the process you can change both of them."

I decided to run /sbin/unsling with -nopw. I was happy with the default in /usr/local/passwd AND I KNEW that the external disk's password would be different. But the README line above led me to think it could be changed easily, and that the process would not let me reboot without knowing the appropriate password(s).

Of course, after rebooting with the external unslung disk attached, I couldn't telnet. http://www.nslu2-linux.org/wiki/FAQ/CantTelnetToMyNewlyUnslungNSLU2 is useless at this point. Eventually, I solved the problem by unslinging again WITHOUT -nopw.

I accept that using -nopw as a first-timer was a bit silly, but I thought the README would indicate AT THE APPROPRIATE TIME how to change the external disk's password. It doesn't. The 5.5 README had text at just the right point, but that text isn't present anymore. (5.5's UNSLINGING DETAILS section basically says "after unslinging, don't logout until you're sure you have got YOUR root password on the external disk", and references the CantTelnetToMyNewlyUnslungNSLU2 page.)

I think the README should 1) say first-timers have no reason AT ALL to use -nopw, and 2) reuse the dropped text from the 5.5 README.

INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

July 14, 2007, at 01:15 PM by Dave Lane -- Ensure web page refresh to check if you are unslung
Added lines 85-90:

Suggestion:

>In the README, when checking if you are unslung

It may sound obvious, but when checking whether you are unslung, you may have to manually refresh the web GUI - just returning to the homepage won't necessarily work. Using IE, a simple F5 should suffice. The most reliable test is logging in via the telnet session. Enable telnet as before, and then use the password entered during the unsling process to login.

July 07, 2007, at 11:15 PM by lImbus --
Changed line 35 from:

Readme PreInstall?-4), Line 114 says the flash drive has to be at least 256MB in size if used to install packages, /wiki/WhichUSBPortforUnslung6 says "2# The root device must be 512MB or larger in size."

to:

Readme Preinstall-4), Line 114 says the flash drive has to be at least 256MB in size if used to install packages, /wiki/WhichUSBPortforUnslung6 says "2# The root device must be 512MB or larger in size."

July 07, 2007, at 11:15 PM by lImbus -- needed root drive size
Added line 32:
Added lines 35-40:

Readme PreInstall?-4), Line 114 says the flash drive has to be at least 256MB in size if used to install packages, /wiki/WhichUSBPortforUnslung6 says "2# The root device must be 512MB or larger in size." None of them say how big it has to be without installing packages or whether unslung can be installed without installing packages (for the people not understanding the need for packages) INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

November 11, 2006, at 04:39 PM by Troll -- Full of obsolete information
Changed line 19 from:

<suggestion here>

to:

If someone can find the time to remove all obsolete information that no longer applies, then the documents will make some sense again. At the moment things are quite unusable.

September 09, 2006, at 03:48 PM by Steve G -- Undid vandalism AGAIN
Changed lines 1-4 from:

Thanks you for this site. Your creativity inspires me on feats and adventures. I love you for it. Let's be friends. And here my site http://order-generic-viagra.34www.com

All the whole

to:

Suggested Changes to the README

This article pertains to:

  • Unslung 6.8

The README file (/opt/doc/README on an Unslung system) is incorporated into the Monotone repository, and should be used as a starting point for suggested changes. A copy can also be found at http://www.slug-firmware.net/

The NOTES file (/opt/doc/NOTES on an Unslung system) is considered to be initial "usage" notes for the Unslung firmware - "doco on the go." Please suggest changes for that documentation here as well.


Note: Thanks to those who have suggested changes to date -- your feedback is appreciated. The latest README has been updated with the suggestions that were previously added here.

All documents can be improved, and this page is a great place to help us make sure that the first experience new users have with Unslung is as positive as it can be. Your suggestions are needed - please add your suggested changes and corrections to this page. Thanks!


Please add new suggestions below this line, prefixed by a > so we can easily spot new suggestions and answer them, but before the next separation (----) so that what is being worked on will not be confused with new issues. Also state whether the suggested change is to NOTES or to README as shown below. Thank you for your suggestions.

>README - suggested change

Suggestion:

<suggestion here> INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

<suggestion here> INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

<suggestion here> INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

In step 4 it says "If the disk has not been previously formatted on the NSLU2, then now is

          the time to do that."

It would be worthwhile being explicit about how to do that rather than assuming the user will know to use the web interface rather than that inviting telnet session...

INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

> First-time unslingers should NOT use -nopw

In the UNSLINGING DETAILS section of the README, it says "NOTE: There are two root passwords." and "Later in the process you can change both of them."

I decided to run /sbin/unsling with -nopw. I was happy with the default in /usr/local/passwd AND I KNEW that the external disk's password would be different. But the README line above led me to think it could be changed easily, and that the process would not let me reboot without knowing the appropriate password(s).

Of course, after rebooting with the external unslung disk attached, I couldn't telnet. http://www.nslu2-linux.org/wiki/FAQ/CantTelnetToMyNewlyUnslungNSLU2 is useless at this point. Eventually, I solved the problem by unslinging again WITHOUT -nopw.

I accept that using -nopw as a first-timer was a bit silly, but I thought the README would indicate AT THE APPROPRIATE TIME how to change the external disk's password. It doesn't. The 5.5 README had text at just the right point, but that text isn't present anymore. (5.5's UNSLINGING DETAILS section basically says "after unslinging, don't logout until you're sure you have got YOUR root password on the external disk", and references the CantTelnetToMyNewlyUnslungNSLU2 page.)

I think the README should 1) say first-timers have no reason AT ALL to use -nopw, and 2) reuse the dropped text from the 5.5 README.

INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

> In the README, /unslung and /opt warning unclear

For seasoned Unslung users the following warning (preinstallation step 3) might be meaningful

  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 all previous Unslung versions :-)

I believe it's rather cryptic. I would suggest it be a longer phrase like

  Before unsling, the root of the harddisk contains a directory per user (and the "public" one).
  After unslinging, it also contains a copy of all the files/directories of the root file system
  (like bin, proc, sbin). Thirdly, it will contain the /opt and /unslung directory. Those will
  be used to install packages respectively diversion scripts (the two reasons why you would want
  Unslung). The unsling script will not touch the 1st and 3rd category files (user directories and
  /opt plus /unslung) but it will touch the 2nd (root file system files). So make sure your file
  modifications are in category 1 or 3, but not in 2 if you ever plan to re-unsling.

>NOTES - Suggested change

NSLU2 Users: Please do not modify information below this line, as it contains information for review by NSLU2 developers.


We have tried to make the README cover the most prevalent issues - emphasizing certain things so that newbies can follow the directions and have a usable Unslung NSLU2. We still expect you to be able to read documentation AND be familiar enough with the Linksys basic functionality to be running an Unslung NSLU2 without problems. Thank you for your suggestions to help make NSLU2-Linux documentation better.

September 09, 2006, at 02:46 PM by ment --
Changed lines 1-83 from:

Suggested Changes to the README

This article pertains to:

  • Unslung 6.8

The README file (/opt/doc/README on an Unslung system) is incorporated into the Monotone repository, and should be used as a starting point for suggested changes. A copy can also be found at http://www.slug-firmware.net/

The NOTES file (/opt/doc/NOTES on an Unslung system) is considered to be initial "usage" notes for the Unslung firmware - "doco on the go." Please suggest changes for that documentation here as well.


Note: Thanks to those who have suggested changes to date -- your feedback is appreciated. The latest README has been updated with the suggestions that were previously added here.

All documents can be improved, and this page is a great place to help us make sure that the first experience new users have with Unslung is as positive as it can be. Your suggestions are needed - please add your suggested changes and corrections to this page. Thanks!


Please add new suggestions below this line, prefixed by a > so we can easily spot new suggestions and answer them, but before the next separation (----) so that what is being worked on will not be confused with new issues. Also state whether the suggested change is to NOTES or to README as shown below. Thank you for your suggestions.

>README - suggested change

Suggestion:

<suggestion here> INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

<suggestion here> INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

<suggestion here> INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

In step 4 it says "If the disk has not been previously formatted on the NSLU2, then now is

          the time to do that."

It would be worthwhile being explicit about how to do that rather than assuming the user will know to use the web interface rather than that inviting telnet session...

INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

> First-time unslingers should NOT use -nopw

In the UNSLINGING DETAILS section of the README, it says "NOTE: There are two root passwords." and "Later in the process you can change both of them."

I decided to run /sbin/unsling with -nopw. I was happy with the default in /usr/local/passwd AND I KNEW that the external disk's password would be different. But the README line above led me to think it could be changed easily, and that the process would not let me reboot without knowing the appropriate password(s).

Of course, after rebooting with the external unslung disk attached, I couldn't telnet. http://www.nslu2-linux.org/wiki/FAQ/CantTelnetToMyNewlyUnslungNSLU2 is useless at this point. Eventually, I solved the problem by unslinging again WITHOUT -nopw.

I accept that using -nopw as a first-timer was a bit silly, but I thought the README would indicate AT THE APPROPRIATE TIME how to change the external disk's password. It doesn't. The 5.5 README had text at just the right point, but that text isn't present anymore. (5.5's UNSLINGING DETAILS section basically says "after unslinging, don't logout until you're sure you have got YOUR root password on the external disk", and references the CantTelnetToMyNewlyUnslungNSLU2 page.)

I think the README should 1) say first-timers have no reason AT ALL to use -nopw, and 2) reuse the dropped text from the 5.5 README.

INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

> In the README, /unslung and /opt warning unclear

For seasoned Unslung users the following warning (preinstallation step 3) might be meaningful

  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 all previous Unslung versions :-)

I believe it's rather cryptic. I would suggest it be a longer phrase like

  Before unsling, the root of the harddisk contains a directory per user (and the "public" one).
  After unslinging, it also contains a copy of all the files/directories of the root file system
  (like bin, proc, sbin). Thirdly, it will contain the /opt and /unslung directory. Those will
  be used to install packages respectively diversion scripts (the two reasons why you would want
  Unslung). The unsling script will not touch the 1st and 3rd category files (user directories and
  /opt plus /unslung) but it will touch the 2nd (root file system files). So make sure your file
  modifications are in category 1 or 3, but not in 2 if you ever plan to re-unsling.

>NOTES - Suggested change

NSLU2 Users: Please do not modify information below this line, as it contains information for review by NSLU2 developers.


We have tried to make the README cover the most prevalent issues - emphasizing certain things so that newbies can follow the directions and have a usable Unslung NSLU2. We still expect you to be able to read documentation AND be familiar enough with the Linksys basic functionality to be running an Unslung NSLU2 without problems. Thank you for your suggestions to help make NSLU2-Linux documentation better.

to:

Thanks you for this site. Your creativity inspires me on feats and adventures. I love you for it. Let's be friends. And here my site http://order-generic-viagra.34www.com

All the whole

September 08, 2006, at 07:51 PM by Steve G -- Undid vandalism
Changed lines 1-4 from:

hi all:) Its a nice site. And i looking for a friends. Visit my site http://comforter-cover.zfdfs.info

Love and music is my life ;) Good luck

to:

Suggested Changes to the README

This article pertains to:

  • Unslung 6.8

The README file (/opt/doc/README on an Unslung system) is incorporated into the Monotone repository, and should be used as a starting point for suggested changes. A copy can also be found at http://www.slug-firmware.net/

The NOTES file (/opt/doc/NOTES on an Unslung system) is considered to be initial "usage" notes for the Unslung firmware - "doco on the go." Please suggest changes for that documentation here as well.


Note: Thanks to those who have suggested changes to date -- your feedback is appreciated. The latest README has been updated with the suggestions that were previously added here.

All documents can be improved, and this page is a great place to help us make sure that the first experience new users have with Unslung is as positive as it can be. Your suggestions are needed - please add your suggested changes and corrections to this page. Thanks!


Please add new suggestions below this line, prefixed by a > so we can easily spot new suggestions and answer them, but before the next separation (----) so that what is being worked on will not be confused with new issues. Also state whether the suggested change is to NOTES or to README as shown below. Thank you for your suggestions.

>README - suggested change

Suggestion:

<suggestion here> INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

<suggestion here> INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

<suggestion here> INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

In step 4 it says "If the disk has not been previously formatted on the NSLU2, then now is

          the time to do that."

It would be worthwhile being explicit about how to do that rather than assuming the user will know to use the web interface rather than that inviting telnet session...

INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

> First-time unslingers should NOT use -nopw

In the UNSLINGING DETAILS section of the README, it says "NOTE: There are two root passwords." and "Later in the process you can change both of them."

I decided to run /sbin/unsling with -nopw. I was happy with the default in /usr/local/passwd AND I KNEW that the external disk's password would be different. But the README line above led me to think it could be changed easily, and that the process would not let me reboot without knowing the appropriate password(s).

Of course, after rebooting with the external unslung disk attached, I couldn't telnet. http://www.nslu2-linux.org/wiki/FAQ/CantTelnetToMyNewlyUnslungNSLU2 is useless at this point. Eventually, I solved the problem by unslinging again WITHOUT -nopw.

I accept that using -nopw as a first-timer was a bit silly, but I thought the README would indicate AT THE APPROPRIATE TIME how to change the external disk's password. It doesn't. The 5.5 README had text at just the right point, but that text isn't present anymore. (5.5's UNSLINGING DETAILS section basically says "after unslinging, don't logout until you're sure you have got YOUR root password on the external disk", and references the CantTelnetToMyNewlyUnslungNSLU2 page.)

I think the README should 1) say first-timers have no reason AT ALL to use -nopw, and 2) reuse the dropped text from the 5.5 README.

INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

> In the README, /unslung and /opt warning unclear

For seasoned Unslung users the following warning (preinstallation step 3) might be meaningful

  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 all previous Unslung versions :-)

I believe it's rather cryptic. I would suggest it be a longer phrase like

  Before unsling, the root of the harddisk contains a directory per user (and the "public" one).
  After unslinging, it also contains a copy of all the files/directories of the root file system
  (like bin, proc, sbin). Thirdly, it will contain the /opt and /unslung directory. Those will
  be used to install packages respectively diversion scripts (the two reasons why you would want
  Unslung). The unsling script will not touch the 1st and 3rd category files (user directories and
  /opt plus /unslung) but it will touch the 2nd (root file system files). So make sure your file
  modifications are in category 1 or 3, but not in 2 if you ever plan to re-unsling.

>NOTES - Suggested change

NSLU2 Users: Please do not modify information below this line, as it contains information for review by NSLU2 developers.


We have tried to make the README cover the most prevalent issues - emphasizing certain things so that newbies can follow the directions and have a usable Unslung NSLU2. We still expect you to be able to read documentation AND be familiar enough with the Linksys basic functionality to be running an Unslung NSLU2 without problems. Thank you for your suggestions to help make NSLU2-Linux documentation better.

September 08, 2006, at 07:11 AM by Rose --
Changed lines 1-83 from:

Suggested Changes to the README

This article pertains to:

  • Unslung 6.8

The README file (/opt/doc/README on an Unslung system) is incorporated into the Monotone repository, and should be used as a starting point for suggested changes. A copy can also be found at http://www.slug-firmware.net/

The NOTES file (/opt/doc/NOTES on an Unslung system) is considered to be initial "usage" notes for the Unslung firmware - "doco on the go." Please suggest changes for that documentation here as well.


Note: Thanks to those who have suggested changes to date -- your feedback is appreciated. The latest README has been updated with the suggestions that were previously added here.

All documents can be improved, and this page is a great place to help us make sure that the first experience new users have with Unslung is as positive as it can be. Your suggestions are needed - please add your suggested changes and corrections to this page. Thanks!


Please add new suggestions below this line, prefixed by a > so we can easily spot new suggestions and answer them, but before the next separation (----) so that what is being worked on will not be confused with new issues. Also state whether the suggested change is to NOTES or to README as shown below. Thank you for your suggestions.

>README - suggested change

Suggestion:

<suggestion here> INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

<suggestion here> INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

<suggestion here> INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

In step 4 it says "If the disk has not been previously formatted on the NSLU2, then now is

          the time to do that."

It would be worthwhile being explicit about how to do that rather than assuming the user will know to use the web interface rather than that inviting telnet session...

INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

> First-time unslingers should NOT use -nopw

In the UNSLINGING DETAILS section of the README, it says "NOTE: There are two root passwords." and "Later in the process you can change both of them."

I decided to run /sbin/unsling with -nopw. I was happy with the default in /usr/local/passwd AND I KNEW that the external disk's password would be different. But the README line above led me to think it could be changed easily, and that the process would not let me reboot without knowing the appropriate password(s).

Of course, after rebooting with the external unslung disk attached, I couldn't telnet. http://www.nslu2-linux.org/wiki/FAQ/CantTelnetToMyNewlyUnslungNSLU2 is useless at this point. Eventually, I solved the problem by unslinging again WITHOUT -nopw.

I accept that using -nopw as a first-timer was a bit silly, but I thought the README would indicate AT THE APPROPRIATE TIME how to change the external disk's password. It doesn't. The 5.5 README had text at just the right point, but that text isn't present anymore. (5.5's UNSLINGING DETAILS section basically says "after unslinging, don't logout until you're sure you have got YOUR root password on the external disk", and references the CantTelnetToMyNewlyUnslungNSLU2 page.)

I think the README should 1) say first-timers have no reason AT ALL to use -nopw, and 2) reuse the dropped text from the 5.5 README.

INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

> In the README, /unslung and /opt warning unclear

For seasoned Unslung users the following warning (preinstallation step 3) might be meaningful

  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 all previous Unslung versions :-)

I believe it's rather cryptic. I would suggest it be a longer phrase like

  Before unsling, the root of the harddisk contains a directory per user (and the "public" one).
  After unslinging, it also contains a copy of all the files/directories of the root file system
  (like bin, proc, sbin). Thirdly, it will contain the /opt and /unslung directory. Those will
  be used to install packages respectively diversion scripts (the two reasons why you would want
  Unslung). The unsling script will not touch the 1st and 3rd category files (user directories and
  /opt plus /unslung) but it will touch the 2nd (root file system files). So make sure your file
  modifications are in category 1 or 3, but not in 2 if you ever plan to re-unsling.

>NOTES - Suggested change

NSLU2 Users: Please do not modify information below this line, as it contains information for review by NSLU2 developers.


We have tried to make the README cover the most prevalent issues - emphasizing certain things so that newbies can follow the directions and have a usable Unslung NSLU2. We still expect you to be able to read documentation AND be familiar enough with the Linksys basic functionality to be running an Unslung NSLU2 without problems. Thank you for your suggestions to help make NSLU2-Linux documentation better.

to:

hi all:) Its a nice site. And i looking for a friends. Visit my site http://comforter-cover.zfdfs.info

Love and music is my life ;) Good luck

April 22, 2006, at 09:24 PM by mwester --
Changed lines 10-11 from:

Note: Thanks to those who have suggested changes to date -- your feedback is appreciated. The latest README has been updated with the suggestions that were previously added here.

to:

Note: Thanks to those who have suggested changes to date -- your feedback is appreciated. The latest README has been updated with the suggestions that were previously added here.

Changed lines 19-24 from:

In step 4 it says "If the disk has not been previously formatted on the NSLU2, then now is

          the time to do that."

It would be worthwhile being explicit about how to do that rather than assuming the user will know to use the web interface rather than that inviting telnet session...

to:

<suggestion here>

Changed lines 24-35 from:

> First-time unslingers should NOT use -nopw

In the UNSLINGING DETAILS section of the README, it says "NOTE: There are two root passwords." and "Later in the process you can change both of them."

I decided to run /sbin/unsling with -nopw. I was happy with the default in /usr/local/passwd AND I KNEW that the external disk's password would be different. But the README line above led me to think it could be changed easily, and that the process would not let me reboot without knowing the appropriate password(s).

Of course, after rebooting with the external unslung disk attached, I couldn't telnet. http://www.nslu2-linux.org/wiki/FAQ/CantTelnetToMyNewlyUnslungNSLU2 is useless at this point. Eventually, I solved the problem by unslinging again WITHOUT -nopw.

I accept that using -nopw as a first-timer was a bit silly, but I thought the README would indicate AT THE APPROPRIATE TIME how to change the external disk's password. It doesn't. The 5.5 README had text at just the right point, but that text isn't present anymore. (5.5's UNSLINGING DETAILS section basically says "after unslinging, don't logout until you're sure you have got YOUR root password on the external disk", and references the CantTelnetToMyNewlyUnslungNSLU2 page.)

I think the README should 1) say first-timers have no reason AT ALL to use -nopw, and 2) reuse the dropped text from the 5.5 README.

to:

<suggestion here>

Added lines 29-59:

<suggestion here> INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

In step 4 it says "If the disk has not been previously formatted on the NSLU2, then now is

          the time to do that."

It would be worthwhile being explicit about how to do that rather than assuming the user will know to use the web interface rather than that inviting telnet session...

INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

> First-time unslingers should NOT use -nopw

In the UNSLINGING DETAILS section of the README, it says "NOTE: There are two root passwords." and "Later in the process you can change both of them."

I decided to run /sbin/unsling with -nopw. I was happy with the default in /usr/local/passwd AND I KNEW that the external disk's password would be different. But the README line above led me to think it could be changed easily, and that the process would not let me reboot without knowing the appropriate password(s).

Of course, after rebooting with the external unslung disk attached, I couldn't telnet. http://www.nslu2-linux.org/wiki/FAQ/CantTelnetToMyNewlyUnslungNSLU2 is useless at this point. Eventually, I solved the problem by unslinging again WITHOUT -nopw.

I accept that using -nopw as a first-timer was a bit silly, but I thought the README would indicate AT THE APPROPRIATE TIME how to change the external disk's password. It doesn't. The 5.5 README had text at just the right point, but that text isn't present anymore. (5.5's UNSLINGING DETAILS section basically says "after unslinging, don't logout until you're sure you have got YOUR root password on the external disk", and references the CantTelnetToMyNewlyUnslungNSLU2 page.)

I think the README should 1) say first-timers have no reason AT ALL to use -nopw, and 2) reuse the dropped text from the 5.5 README.

INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

April 22, 2006, at 04:44 PM by AB -- First-time unslingers should NOT use -nopw
Changed lines 29-40 from:

...

to:

> First-time unslingers should NOT use -nopw

In the UNSLINGING DETAILS section of the README, it says "NOTE: There are two root passwords." and "Later in the process you can change both of them."

I decided to run /sbin/unsling with -nopw. I was happy with the default in /usr/local/passwd AND I KNEW that the external disk's password would be different. But the README line above led me to think it could be changed easily, and that the process would not let me reboot without knowing the appropriate password(s).

Of course, after rebooting with the external unslung disk attached, I couldn't telnet. http://www.nslu2-linux.org/wiki/FAQ/CantTelnetToMyNewlyUnslungNSLU2 is useless at this point. Eventually, I solved the problem by unslinging again WITHOUT -nopw.

I accept that using -nopw as a first-timer was a bit silly, but I thought the README would indicate AT THE APPROPRIATE TIME how to change the external disk's password. It doesn't. The 5.5 README had text at just the right point, but that text isn't present anymore. (5.5's UNSLINGING DETAILS section basically says "after unslinging, don't logout until you're sure you have got YOUR root password on the external disk", and references the CantTelnetToMyNewlyUnslungNSLU2 page.)

I think the README should 1) say first-timers have no reason AT ALL to use -nopw, and 2) reuse the dropped text from the 5.5 README.

April 22, 2006, at 03:13 AM by Peter Enzerink -- more explicit on drive formatting
Changed lines 19-24 from:

...

to:

In step 4 it says "If the disk has not been previously formatted on the NSLU2, then now is

          the time to do that."

It would be worthwhile being explicit about how to do that rather than assuming the user will know to use the web interface rather than that inviting telnet session...

April 14, 2006, at 02:19 AM by mwester -- Updated for 6.8-beta release
Changed lines 3-9 from:
  • Unslung 6.x
  • Unslung 5.5

The README file (/opt/doc/README on an Unslung system) is incorporated into the Monotone repository, and should be used as a starting point for suggested changes. A copy can also be found at http://download.berlios.de/unslung/Unslung-5.5-beta-README.txt

The NOTES file (/opt/doc/NOTES on an Unslung system) is considered to be initial "usage" notes for the Unslung firmware - "doco on the go." Please suggest changes for that documentation here as well.

to:
  • Unslung 6.8

The README file (/opt/doc/README on an Unslung system) is incorporated into the Monotone repository, and should be used as a starting point for suggested changes. A copy can also be found at http://www.slug-firmware.net/

The NOTES file (/opt/doc/NOTES on an Unslung system) is considered to be initial "usage" notes for the Unslung firmware - "doco on the go." Please suggest changes for that documentation here as well.

Changed lines 10-12 from:

Note: Thanks to those who have suggested changes to date -- your feedback is appreciated. The latest README has been updated with the suggestions that were previously added here.

All documents can be improved, and this page is a great place to help us make sure that the first experience new users have with Unslung is as positive as it can be. Your suggestions are needed - please add your suggested changes and corrections to this page. Thanks!

to:

Note: Thanks to those who have suggested changes to date -- your feedback is appreciated. The latest README has been updated with the suggestions that were previously added here.

All documents can be improved, and this page is a great place to help us make sure that the first experience new users have with Unslung is as positive as it can be. Your suggestions are needed - please add your suggested changes and corrections to this page. Thanks!

Added line 16:
Changed lines 18-28 from:
to:

Suggestion:

... INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

... INSERT YOUR SUGGESTION HERE!

>README - suggested change

Suggestion:

Changed lines 52-57 from:

We have tried to make the README cover the most prevalent issues - emphasizing certain things so that newbies can follow the directions and have a usable Unslung NSLU2. We still expect you to be able to read documentation AND be familiar enough with the Linksys basic functionality to be running an Unslung NSLU2 without problems. Thank you for your suggestions to help make NSLU2-Linux documentation better.


I suggest to add a intermediate step between steps 5 and 6 to enfatize the need to change the /share/hdd/conf/passwd before reboot. Althoug it is written in the text, it is mentioned in a note on step 5 and it is easy to miss. Failing this step prevents you from telnet with a harddisk attached. In my case (no Linux knowledge), I solve it only by starting from scratch. If there is a workaround, it would be nice to add to the FAQ too.

to:

We have tried to make the README cover the most prevalent issues - emphasizing certain things so that newbies can follow the directions and have a usable Unslung NSLU2. We still expect you to be able to read documentation AND be familiar enough with the Linksys basic functionality to be running an Unslung NSLU2 without problems. Thank you for your suggestions to help make NSLU2-Linux documentation better.

April 04, 2006, at 05:56 PM by Mauro Vianna -- Readme suggestion
Added lines 45-47:

I suggest to add a intermediate step between steps 5 and 6 to enfatize the need to change the /share/hdd/conf/passwd before reboot. Althoug it is written in the text, it is mentioned in a note on step 5 and it is easy to miss. Failing this step prevents you from telnet with a harddisk attached. In my case (no Linux knowledge), I solve it only by starting from scratch. If there is a workaround, it would be nice to add to the FAQ too.

March 08, 2006, at 06:26 AM by mwester -- Reset page after updating the README
Added lines 1-5:

Suggested Changes to the README

This article pertains to:

  • Unslung 6.x
  • Unslung 5.5
March 08, 2006, at 06:24 AM by mwester -- Reset page after updating the README
Changed lines 1-4 from:

Latest README - This is incorporated into the Monotone repository, and should be used as a starting point for suggested changes.

Latest NOTES - This file is considered to be initial "usage" notes for the Unslung firmware - "doco on the go." Please suggest changes for that documentation here as well.

to:

The README file (/opt/doc/README on an Unslung system) is incorporated into the Monotone repository, and should be used as a starting point for suggested changes. A copy can also be found at http://download.berlios.de/unslung/Unslung-5.5-beta-README.txt

The NOTES file (/opt/doc/NOTES on an Unslung system) is considered to be initial "usage" notes for the Unslung firmware - "doco on the go." Please suggest changes for that documentation here as well.

Added lines 6-9:

Note: Thanks to those who have suggested changes to date -- your feedback is appreciated. The latest README has been updated with the suggestions that were previously added here.

All documents can be improved, and this page is a great place to help us make sure that the first experience new users have with Unslung is as positive as it can be. Your suggestions are needed - please add your suggested changes and corrections to this page. Thanks!


Changed lines 12-84 from:

>REAME

> there are number of references to 'external disk' that probably also refer to external flash card. If not, then it isn't clear. No 4 of the PRE-INSTALLATION CONSIDERATIONS says to format an external flash disk using the web interface, but there is no such facility (that I can find).

>README - Suggested change

<<< This section has been added to the README

> There have been a number of news group posts that seem to indicate that some new users are getting confused regarding instalation as follows (in the Unslining section):-

  1. Instruction 5 of the readme regarding password changing. Suggest moving the note from the top of the section regarding password changing to instruction 5 where it is needed. Changing the password using the command passwd and moving the changed password file to disk using cp /etc/passwd /share/hdd/conf/passwd or cp /etc/passwd /share/flash/conf/passwd are important steps for new installations otherwise impossible to telnet in after unslinging and re-booting. cp /etc/passwd /usr/local/passwd is an optional step and not necessarily recommended.
  2. Expand the last instruction 7 to emphasise the need to re-boot the slug at this point. A number of users seem to have missed this stage, many run ipkg update which then overfills their flash ram.

>>> End of section that has been added to the README

RobHam 03 June 2005 note - some of the above have been incorporated into 5.5

> Suggested changes to the unslung steps:

In step 5, change the comment:

***** Unsling will not change the password on your disk...

to:

***** Unsling will not change the password on your disk, so if you had previously changed the password on a disk, then your password will not be changed.

Then add the following comment:

***** It is recommended that you change the root password at this time, or you will not be able to login again with disks attached. Simply editing the /etc/passwd file is not enough to permanently change a password. See:
http://www.nslu2-linux.org/wiki/HowTo/ChangePasswordsFromTheCommandLine

In step 8, change the step from:

8) Wait for the NSLU2 to boot, telnet in, and confirm that the root filesystem is being loaded from the external disk.

to:

8) Wait for the NSLU2 to boot, enable telnet from the web management page, telnet in, and confirm that the root filesystem is being loaded from the external disk.
Note: The commands df and mount will be helpful in verifying your filesystem status. Look for the 'rootfs' line, and note the figure under the '1k-blocks' header. This number should match the number in the same column, for the line with '/share/hdd/data' under the 'Mounted on' column.

After the comment:

If you make no further changes, your NSLU2 will continue to operate normally. But to customize things, you'll be downloading packages and adding stuff to the /unslung directory using diversion scripts.

Add:

http://www.nslu2-linux.org/wiki/Unslung/Packages
http://www.nslu2-linux.org/wiki/Unslung/DiversionScripts

[ToddZ? 2005/06/07]

> Suggested change for unslung 5.5 password change. Don't point to the wiki as it's confusing, and will lock users (possibly) out of their new unslung systems. Instead, add:

If this is your first time unslinging to this disk, change the password for root by typing 'passwd' (without the quotes) at the command prompt. Type it the same way twice, as directed by the prompts. When you have changed it, the file /etc/passwd will contain the newly changed root password. As this only exists in the RAM disk in memory, unless you copy it to the hard disk, when you reboot, it will default back to the original password. To copy it, type the following commands:

cp /etc/passwd /share/hdd/conf/passwd cp /etc/passwd /share/hdd/data/usr/local/passwd

Also consider the implications contained in the news post message http://groups.yahoo.com/group/nslu2-general/message/1527

> Suggested addition to step 4 under FIRMWARE INSTALLATION DETAILS: Note: There exists a bug in Linksys R29 software (which Unslung 5.5 is based on) that causes Disk 2/Flash to show the following on the webpage:

  Disk 2/Flash:  	Ready, 0MB (0% Free)

Using df from a telnet session will show the correct disk usage.

> Suggested addition to the "postamble" of the 5.5 README: add location of NOTES file.

Read the NOTES file (in /share/hdd/data/opt/doc) to expand the capabilities of your Unslung NSLU2!

> Suggested addition to the "postamble" of the 5.5 README: add location of "The Unslung 5.x table".

Make sure you add an entry to the "The 5.x Unslung" table in the Yahoo group nslu2-linux ("Database" section).

> /unslung and /opt warning unclear

to:

>README - suggested change

> In the README, /unslung and /opt warning unclear

Changed lines 22-23 from:

I believe it's rather criptic. I would suggest it be a longer phrase like

to:

I believe it's rather cryptic. I would suggest it be a longer phrase like

Deleted line 31:
Added lines 36-37:

September 08, 2005, at 11:47 AM by Max Waterman -- and no flash format facility on web interface
Changed lines 10-11 from:

> there are number of references to 'external disk' that probably also refer to external flash card. If not, then it isn't clear.

to:

> there are number of references to 'external disk' that probably also refer to external flash card. If not, then it isn't clear. No 4 of the PRE-INSTALLATION CONSIDERATIONS says to format an external flash disk using the web interface, but there is no such facility (that I can find).

September 08, 2005, at 11:40 AM by Max Waterman -- external disk ==
Changed lines 8-9 from:

SUGGESTIONS GO HERE!!!!

to:

>REAME

> there are number of references to 'external disk' that probably also refer to external flash card. If not, then it isn't clear.

August 06, 2005, at 08:38 PM by blaster8 -- Usual speeling errors (joke)
Changed lines 16-17 from:
  1. Expand the last instruction 7 to emphesise the need to re-boot the slug at this point. A number of users seem to have missed this stage, many run ipkg update which then fills there flash ram.
to:
  1. Expand the last instruction 7 to emphasise the need to re-boot the slug at this point. A number of users seem to have missed this stage, many run ipkg update which then overfills their flash ram.
August 06, 2005, at 08:34 PM by blaster8 -- Changed BK reference
Changed lines 1-2 from:

Latest README - This is incorporated into the BK repository, and should be used as a starting point for suggested changes.

to:

Latest README - This is incorporated into the Monotone repository, and should be used as a starting point for suggested changes.

July 21, 2005, at 09:53 AM by diag71 --
Changed lines 35-40 from:

> Complete newbie feedback : This part of section 5) about changing the password needs to stand out more. I completely missed it. I think it is because the paragraph starts out exaclty the same as a paragraph on the previous page, and I probably skipped reading the whole paragraph. Perhaps you should make "Change your password" a seperate step between the current 5) and 6).

Otherwise, the Readme was excellent and very easy to follow.

to:
July 21, 2005, at 09:50 AM by diag71 --
Added lines 35-40:

> Complete newbie feedback : This part of section 5) about changing the password needs to stand out more. I completely missed it. I think it is because the paragraph starts out exaclty the same as a paragraph on the previous page, and I probably skipped reading the whole paragraph. Perhaps you should make "Change your password" a seperate step between the current 5) and 6).

Otherwise, the Readme was excellent and very easy to follow.

July 18, 2005, at 09:25 PM by MaartenPennings -- clarify /opt and /unslung warning
Added lines 76-94:

> /unslung and /opt warning unclear

For seasoned Unslung users the following warning (preinstallation step 3) might be meaningful

  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 all previous Unslung versions :-)

I believe it's rather criptic. I would suggest it be a longer phrase like

  Before unsling, the root of the harddisk contains a directory per user (and the "public" one).
  After unslinging, it also contains a copy of all the files/directories of the root file system
  (like bin, proc, sbin). Thirdly, it will contain the /opt and /unslung directory. Those will
  be used to install packages respectively diversion scripts (the two reasons why you would want
  Unslung). The unsling script will not touch the 1st and 3rd category files (user directories and
  /opt plus /unslung) but it will touch the 2nd (root file system files). So make sure your file
  modifications are in category 1 or 3, but not in 2 if you ever plan to re-unsling.
June 26, 2005, at 01:02 PM by MaarttenPennings -- explain where to find the NOTES file
Added lines 68-75:

> Suggested addition to the "postamble" of the 5.5 README: add location of NOTES file.

Read the NOTES file (in /share/hdd/data/opt/doc) to expand the capabilities of your Unslung NSLU2!

> Suggested addition to the "postamble" of the 5.5 README: add location of "The Unslung 5.x table".

Make sure you add an entry to the "The 5.x Unslung" table in the Yahoo group nslu2-linux ("Database" section).

June 21, 2005, at 05:52 PM by RobHam -- Link to news post added regarding implications of not changing password
Added lines 58-60:

Also consider the implications contained in the news post message http://groups.yahoo.com/group/nslu2-general/message/1527

June 20, 2005, at 10:28 PM by RobHam -- Changed request 1. slightly
Changed line 15 from:
  1. Instruction 5 of the readme regarding password changing. Suggest moving the note from the top of the section regarding password changing to instruction 5 where it is needed. Changing the password using the command passwd and moving the changed password file to disk using cp /etc/passwd /share/hdd/conf/passwd is an important step for new instalations otherwise impossible to telnet in after unslinging and re-booting. cp /etc/passwd /usr/local/passwd is an optional step.
to:
  1. Instruction 5 of the readme regarding password changing. Suggest moving the note from the top of the section regarding password changing to instruction 5 where it is needed. Changing the password using the command passwd and moving the changed password file to disk using cp /etc/passwd /share/hdd/conf/passwd or cp /etc/passwd /share/flash/conf/passwd are important steps for new installations otherwise impossible to telnet in after unslinging and re-booting. cp /etc/passwd /usr/local/passwd is an optional step and not necessarily recommended.
June 20, 2005, at 10:24 PM by RobHam --
Changed line 15 from:
  1. Instruction 5 of the readme regarding password changing. Suggest moving the note from the top of the section regarding password changing to instruction 5 where it is needed. Changing the password using the command passwd is optional however moving the password file to disk using cp /etc/passwd /share/hdd/conf/passwd and cp /etc/passwd /usr/local/passwd is an important step for new instalations (otherwise impossible to telnet in after unslinging and re-booting).
to:
  1. Instruction 5 of the readme regarding password changing. Suggest moving the note from the top of the section regarding password changing to instruction 5 where it is needed. Changing the password using the command passwd and moving the changed password file to disk using cp /etc/passwd /share/hdd/conf/passwd is an important step for new instalations otherwise impossible to telnet in after unslinging and re-booting. cp /etc/passwd /usr/local/passwd is an optional step.
Added line 21:

note - some of the above have been incorporated into 5.5

June 20, 2005, at 09:54 PM by gsherwood -- Added note about Disk 2 showing 0% Free
Added lines 57-63:

> Suggested addition to step 4 under FIRMWARE INSTALLATION DETAILS: Note: There exists a bug in Linksys R29 software (which Unslung 5.5 is based on) that causes Disk 2/Flash to show the following on the webpage:

  Disk 2/Flash:  	Ready, 0MB (0% Free)

Using df from a telnet session will show the correct disk usage.

June 20, 2005, at 05:02 AM by tsailer -- suggested unslung 5.5 passwd file directions
Added lines 49-56:

> Suggested change for unslung 5.5 password change. Don't point to the wiki as it's confusing, and will lock users (possibly) out of their new unslung systems. Instead, add:

If this is your first time unslinging to this disk, change the password for root by typing 'passwd' (without the quotes) at the command prompt. Type it the same way twice, as directed by the prompts. When you have changed it, the file /etc/passwd will contain the newly changed root password. As this only exists in the RAM disk in memory, unless you copy it to the hard disk, when you reboot, it will default back to the original password. To copy it, type the following commands:

cp /etc/passwd /share/hdd/conf/passwd cp /etc/passwd /share/hdd/data/usr/local/passwd

June 17, 2005, at 04:42 PM by ToddZ -- added suggestions as posted in yahoo groups
Added lines 22-48:

> Suggested changes to the unslung steps:

In step 5, change the comment:

***** Unsling will not change the password on your disk...

to:

***** Unsling will not change the password on your disk, so if you had previously changed the password on a disk, then your password will not be changed.

Then add the following comment:

***** It is recommended that you change the root password at this time, or you will not be able to login again with disks attached. Simply editing the /etc/passwd file is not enough to permanently change a password. See:
http://www.nslu2-linux.org/wiki/HowTo/ChangePasswordsFromTheCommandLine

In step 8, change the step from:

8) Wait for the NSLU2 to boot, telnet in, and confirm that the root filesystem is being loaded from the external disk.

to:

8) Wait for the NSLU2 to boot, enable telnet from the web management page, telnet in, and confirm that the root filesystem is being loaded from the external disk.
Note: The commands df and mount will be helpful in verifying your filesystem status. Look for the 'rootfs' line, and note the figure under the '1k-blocks' header. This number should match the number in the same column, for the line with '/share/hdd/data' under the 'Mounted on' column.

After the comment:

If you make no further changes, your NSLU2 will continue to operate normally. But to customize things, you'll be downloading packages and adding stuff to the /unslung directory using diversion scripts.

Add:

http://www.nslu2-linux.org/wiki/Unslung/Packages
http://www.nslu2-linux.org/wiki/Unslung/DiversionScripts

[ToddZ? 2005/06/07]

June 11, 2005, at 12:33 PM by rwhitby --
Added line 13:
Added line 17:
June 11, 2005, at 12:32 PM by rwhitby --
Changed lines 1-4 from:

Latest README - This is incorporated into the BK repository, and should be used as a starting point for suggested changes.

Latest NOTES - This file is considered to be initial "usage" notes for the Unslung firmware - "doco on the go." Please suggest changes for that documentation here as well.

to:

Latest README - This is incorporated into the BK repository, and should be used as a starting point for suggested changes.

Latest NOTES - This file is considered to be initial "usage" notes for the Unslung firmware - "doco on the go." Please suggest changes for that documentation here as well.

Added line 12:

<<< This section has been added to the README

Changed lines 16-17 from:
to:

>>> End of section that has been added to the README

Deleted lines 18-19:
June 03, 2005, at 10:46 AM by RobHam -- Somenotes added regarding some possible sections that need a little more clarification
Added lines 11-18:

> There have been a number of news group posts that seem to indicate that some new users are getting confused regarding instalation as follows (in the Unslining section):-

  1. Instruction 5 of the readme regarding password changing. Suggest moving the note from the top of the section regarding password changing to instruction 5 where it is needed. Changing the password using the command passwd is optional however moving the password file to disk using cp /etc/passwd /share/hdd/conf/passwd and cp /etc/passwd /usr/local/passwd is an important step for new instalations (otherwise impossible to telnet in after unslinging and re-booting).
  2. Expand the last instruction 7 to emphesise the need to re-boot the slug at this point. A number of users seem to have missed this stage, many run ipkg update which then fills there flash ram.

RobHam 03 June 2005

May 10, 2005, at 06:37 AM by ByronT -- Synching Suggested Changes to Latest README
Deleted lines 11-14:

Added by kai on 2005 April the 17th

1. If using the /data partition as / with Unslung4 - what if previously the /conf partition has been used ... how will installed packages and modified config files / scripts move to the new / location? Sorry, I didn't investigate. As I didn't have much on my slug, I simply installed the few packages from scratch...

Changed lines 13-28 from:

README - Typographical error: Added by Graeme Robinson April 24 2005

TYPOGRAPHICAL ERROR in unslung 3.18 beta README:

At PRE-INSTALLATION CONSIDERATIONS 1)

There is a bad link to the RecoverFromBadFlash? howto:

http://www.nslu2-linux.org/wiwki/HowTo/RecoverFromABadFlash

i.e. directory specified 'wiwki' should be 'wiki'


to:
Changed lines 16-17 from:

We have tried to make the README cover the most prevalent issues - emphasizing certain things so that newbies can follow the directions and have a usable Unslung NSLU2. We still expect you to be able to read documentation AND be familiar enough with the Linksys basic functionality to be running an Unslung NSLU2 without problems. Thank you for your suggestions to hPuppyWithoutFlashOrHddelp make NSLU2-Linux documentation better.

to:

We have tried to make the README cover the most prevalent issues - emphasizing certain things so that newbies can follow the directions and have a usable Unslung NSLU2. We still expect you to be able to read documentation AND be familiar enough with the Linksys basic functionality to be running an Unslung NSLU2 without problems. Thank you for your suggestions to help make NSLU2-Linux documentation better.

April 23, 2005, at 11:42 PM by Graeme Robinson -- readme typographical error
Deleted line 16:
Added lines 18-32:

README - Typographical error: Added by Graeme Robinson April 24 2005

TYPOGRAPHICAL ERROR in unslung 3.18 beta README:

At PRE-INSTALLATION CONSIDERATIONS 1)

There is a bad link to the RecoverFromBadFlash? howto:

http://www.nslu2-linux.org/wiwki/HowTo/RecoverFromABadFlash

i.e. directory specified 'wiwki' should be 'wiki'


Changed lines 35-36 from:

We have tried to make the README cover the most prevalent issues - emphasizing certain things so that newbies can follow the directions and have a usable Unslung NSLU2. We still expect you to be able to read documentation AND be familiar enough with the Linksys basic functionality to be running an Unslung NSLU2 without problems. Thank you for your suggestions to help make NSLU2-Linux documentation better.

to:

We have tried to make the README cover the most prevalent issues - emphasizing certain things so that newbies can follow the directions and have a usable Unslung NSLU2. We still expect you to be able to read documentation AND be familiar enough with the Linksys basic functionality to be running an Unslung NSLU2 without problems. Thank you for your suggestions to hPuppyWithoutFlashOrHddelp make NSLU2-Linux documentation better.

April 21, 2005, at 11:46 AM by kai -- clarification on the left over comment
Changed lines 14-15 from:

1. What if previously the conf partition has been used ... how will installed packages and modified config files / scripts move to the new / location? As I didn't have much on my slug, I simply installed the few packages from scratch...

to:

1. If using the /data partition as / with Unslung4 - what if previously the /conf partition has been used ... how will installed packages and modified config files / scripts move to the new / location? Sorry, I didn't investigate. As I didn't have much on my slug, I simply installed the few packages from scratch...

April 20, 2005, at 12:51 PM by rwhitby --
Deleted lines 11-12:

April 20, 2005, at 12:51 PM by rwhitby --
Changed lines 9-13 from:

> README - Suggested change to the Unslinging details:

"Unslinging" is the process of configuring your NSLU. Basically it's a script (stored in /sbin/unsling) which configures the target location of the software your gonna install. You have two options.

to:

>README - Suggested change

Changed lines 12-61 from:

1. Install the software on the external harddisk.

2. Install the software on the internal flash memory.

To run the unsling-script you have to be logged in as root (with a telnet session).

NOTE: There are two root-passwords. One is saved in a internal file called /usr/local/passwd (we know this one. It's "uNSLUng" and used when you boot without a attached harddisk) the other is stored in a external file called /share/hdd/conf/passwd (we don't know this one. It's used when you boot with a external harddisk attached). Later in the process you can change both of them. That means: Everytime you boot WITHOUT a attached harddisk you gain root-access with the "uNSLUng" password. If you boot with an attached harddisk, you'll don't have access until you change the file /share/hdd/conf/passwd.

Ad 1.)

  • Boot WITHOUT harddisk.
  • Enable telnet. (http://192.168.1.77/Management/telnet.cgi" - press enable button)
  • Login with telnet 192.168.1.77 login:root passwd: uNSLUng
  • Attach the harddisk - wait.
  • type "/sbin/unsling"

Now: Change your root-password:

  • type "passwd", enter and re-enter your new root-passwd.
  • type "cp /etc/passwd /share/hdd/conf/passwd"
  • type "ln -sf /share/hdd/conf/passwd /etc/passwd"
  • Reboot with harddisk, enable telnet via web-interface and you can login with your new password.
  • NOTE: When booting without harddisk, your root-password is still "uNSLUng"

COMMENT: I wrote this after my first Unslinging 3 days ago. I did NOT test it. It needs a REVIEW !!

Added by jncharli on 2005 March the 30th

I tried this procedure, and it doesn't work. I found another procedure that I documented in HowTo.ChangePasswordsFromTheCommandLine

Added by landge -- 03/30-2005

Why not? Your documentation is part of my suggestion!

Mail me if you want: tilsch at online.no

> README - URL typo for pre-installation considerations section

Added by thodson 2005-03-31

In section 1) of the above, talking about the Redboot loader, there is a link to the page dealing with recovering from a bad flash. The word 'wiki' in the URL is spelt as 'wiwki'. Presumably it should be:

http://www.nslu2-linux.org/wiki/HowTo/RecoverFromABadFlash


to:

Added by kai on 2005 April the 17th

1. What if previously the conf partition has been used ... how will installed packages and modified config files / scripts move to the new / location? As I didn't have much on my slug, I simply installed the few packages from scratch...

Deleted lines 19-23:

>README - Suggested change

Focusing on "FIRMWARE INSTALLATION DETAILS" first: I just flashed Unslung 4.x, but it goes for 3.x too: During flashing, at least Firefox will hog 100% CPU (don't know about IE or others) - the flashing may take a long time, longer than 5 mins as reported by the web interface. You are adviced not to have other activities going on at the client while flashing - in my case, the virus-scanner timed out during scanning of an incoming mail and screamed bloody murder. Other than that, this section is still valid [ bob_tm-sick ]

Deleted lines 24-63:

Added by jncharli on 2005 March the 29th

My remark concerns UNSLUNG-3.x Family Release README INSTALLATION on section FIRMWARE INSTALLATION DETAILS

Before

2) If you are installing UNSLUNG 3.x onto an NSLU2 unit with Linksys standard firmware *or* UNSLUNG 1.x or 2.x, go to step 2-a. If you are installing

     Unslung 3.x onto an NSLU2 unit with version 3.x already installed, go to step 2-b.

2-a) Flash unslung-standard-3.x.bin as you normally would flash new firmware (using the web interface "Upgrade Firmware" page).

2-b) You must put the NSLU2 into maintenance mode before you can use... (to be continued)

After

2) Run the Web interface using admin as username, and admin as password. None of the users you have previously defined will run as I guess they are all stored in the passwd file that is on the disk you just disconnected.

2-a) If you are installing Unslung 3.x onto an NSLU2 unit with Linksys standard firmware *or* UNSLUNG 1.x or 2.x, flash unslung-standard-3.x.bin as you normally would flash new firmware (using the web interface "Upgrade Firmware" page).

2-b) If you are installing Unslung 3.x onto an NSLU2 unit with version 3.x already installed, you must put the NSLU2 into maintenance mode before you can use... (unchanged)


> I would add HowTo.IncreaseSpaceAvailableForPackages to the base set of instructions, since the size of the CONF partition isn't controlled by the user through the Linksys GUI.


Added by kai on 2005 April the 17th

Based on unslung-4.14-alpha ... here are things that IMHO would be great to be included in the unslung-4 README:

1. I mistakenly tried to flash several times using a broken download file (4mb). Maybe a check on exact size of the published beta file and/or MD5? checksum would be a nice to have in the readme.

2. I was flashing with unslung-3 only once ever; and then moved to unslung-4. People like me might need to be pointed to ReSling in order to not lose changes that were done in the jffs. and what if previously the conf partition has been used ... how will installed packages and modified config files / scripts move to the new / location? As I didn't have much on my slug, I simply installed the few packages from scratch...

3. I based my unsling process roughly on the unslung-3 README and did "/sbin/unsling hdd-data" - however, the quota check was still running, hence I had pages of error messages. Maybe before unslinging the user needs to check that the data partition is (rw) - only in case one wants to unsling to the data partition, of cause.

April 20, 2005, at 10:28 AM by tman --
Changed lines 1-6 from:

Latest README at http://nslu2-linux.bkbits.net:8080/openembedded/hist/packages/nslu2-binary-only/unslung-rootfs-2.3r25/README This is incorporated into the BK repository, and should be used as a starting point for suggested changes.

Latest NOTES at http://nslu2-linux.bkbits.net:8080/openembedded/hist/packages/nslu2-binary-only/unslung-rootfs-2.3r25/NOTES This file is considered to be initial "usage" notes for the Unslung firmware - "doco on the go." Please suggest changes for that documentation here as well.

to:

Latest README - This is incorporated into the BK repository, and should be used as a starting point for suggested changes.

Latest NOTES - This file is considered to be initial "usage" notes for the Unslung firmware - "doco on the go." Please suggest changes for that documentation here as well.

Deleted lines 64-68:
Deleted line 76:
Deleted line 78:
Changed line 116 from:

3. I based my unsling process roughly on the unslung-3 README and did "/sbin/unsling hdd-data" - however, the quota check was still running, hence I had pages of error messages. Maybe before unslinging the user needs to check that the data partition is (rw) - only in case one wants to unsling to the data partition, of cause.

to:

3. I based my unsling process roughly on the unslung-3 README and did "/sbin/unsling hdd-data" - however, the quota check was still running, hence I had pages of error messages. Maybe before unslinging the user needs to check that the data partition is (rw) - only in case one wants to unsling to the data partition, of cause.

April 20, 2005, at 09:54 AM by rwhitby --
Changed lines 1-4 from:

Latest README at http://www.toddcomp.com/NSLU2/README.txt This is incorporated into the BK repository, and should be used as a starting point for suggested changes.

Latest NOTES at http://www.toddcomp.com/NSLU2/NOTES.txt This file is considered to be initial "usage" notes for the Unslung firmware - "doco on the go." Please suggest changes for that documentation here as well.

to:

Latest README at http://nslu2-linux.bkbits.net:8080/openembedded/hist/packages/nslu2-binary-only/unslung-rootfs-2.3r25/README This is incorporated into the BK repository, and should be used as a starting point for suggested changes.

Latest NOTES at http://nslu2-linux.bkbits.net:8080/openembedded/hist/packages/nslu2-binary-only/unslung-rootfs-2.3r25/NOTES This file is considered to be initial "usage" notes for the Unslung firmware - "doco on the go." Please suggest changes for that documentation here as well.

April 17, 2005, at 07:18 PM by kaste -- some thoughts on unslung 4 alpha
Added lines 112-123:

Added by kai on 2005 April the 17th

Based on unslung-4.14-alpha ... here are things that IMHO would be great to be included in the unslung-4 README:

1. I mistakenly tried to flash several times using a broken download file (4mb). Maybe a check on exact size of the published beta file and/or MD5? checksum would be a nice to have in the readme.

2. I was flashing with unslung-3 only once ever; and then moved to unslung-4. People like me might need to be pointed to ReSling in order to not lose changes that were done in the jffs. and what if previously the conf partition has been used ... how will installed packages and modified config files / scripts move to the new / location? As I didn't have much on my slug, I simply installed the few packages from scratch...

3. I based my unsling process roughly on the unslung-3 README and did "/sbin/unsling hdd-data" - however, the quota check was still running, hence I had pages of error messages. Maybe before unslinging the user needs to check that the data partition is (rw) - only in case one wants to unsling to the data partition, of cause.

April 10, 2005, at 05:26 AM by tman --
Changed line 95 from:
     2-a) Flash unslung-standard-3.x.bin as you normally would flash new firmware (using the web interface "Upgrade Firmware" page).
to:

2-a) Flash unslung-standard-3.x.bin as you normally would flash new firmware (using the web interface "Upgrade Firmware" page).

Changed line 97 from:
     2-b) You must put the NSLU2 into maintenance mode before you can use... (to be continued)
to:

2-b) You must put the NSLU2 into maintenance mode before you can use... (to be continued)

Changed line 103 from:
   None of the users you have previously defined will run as I guess they are all stored in the passwd file that is on the disk you just disconnected.
to:

None of the users you have previously defined will run as I guess they are all stored in the passwd file that is on the disk you just disconnected.

Changed line 105 from:
     2-a) If you are installing UNSLUNG 3.x onto an NSLU2 unit with Linksys standard firmware *or* UNSLUNG 1.x or 2.x, flash unslung-standard-3.x.bin as you normally would flash new firmware (using the web interface "Upgrade Firmware" page).
to:

2-a) If you are installing Unslung 3.x onto an NSLU2 unit with Linksys standard firmware *or* UNSLUNG 1.x or 2.x, flash unslung-standard-3.x.bin as you normally would flash new firmware (using the web interface "Upgrade Firmware" page).

Changed line 107 from:
     2-b) If you are installing Unslung 3.x onto an NSLU2 unit with version 3.x already installed, you must put the NSLU2 into maintenance mode before you can use... (unchanged)
to:

2-b) If you are installing Unslung 3.x onto an NSLU2 unit with version 3.x already installed, you must put the NSLU2 into maintenance mode before you can use... (unchanged)

Changed line 111 from:

> I would add http://www.nslu2-linux.org/wiki/HowTo/IncreaseSpaceAvailableForPackages to the base set of instructions, sine the size of the CONF partition isn't controlled by the user through the Linksys GUI.

to:

> I would add HowTo.IncreaseSpaceAvailableForPackages to the base set of instructions, since the size of the CONF partition isn't controlled by the user through the Linksys GUI.

April 09, 2005, at 01:28 PM by barrym --
Added lines 108-111:

> I would add http://www.nslu2-linux.org/wiki/HowTo/IncreaseSpaceAvailableForPackages to the base set of instructions, sine the size of the CONF partition isn't controlled by the user through the Linksys GUI.

March 31, 2005, at 06:38 AM by thodson --
Added line 56:
Added line 58:
March 31, 2005, at 06:38 AM by thodson --
Added line 38:
Added lines 55-57:

> README - URL typo for pre-installation considerations section Added by thodson 2005-03-31 In section 1) of the above, talking about the Redboot loader, there is a link to the page dealing with recovering from a bad flash. The word 'wiki' in the URL is spelt as 'wiwki'. Presumably it should be:

Added line 59:

http://www.nslu2-linux.org/wiki/HowTo/RecoverFromABadFlash

March 30, 2005, at 03:36 PM by landge --
Added lines 48-55:

Added by landge -- 03/30-2005

Why not? Your documentation is part of my suggestion!

Mail me if you want: tilsch at online.no

March 29, 2005, at 10:24 PM by jncharli --
Changed line 46 from:

I found another procedure that I documented in HowTo.ChangePasswordsFromTheCommandLine

to:

I found another procedure that I documented in HowTo.ChangePasswordsFromTheCommandLine

March 29, 2005, at 10:23 PM by jncharli --
Added lines 42-47:

Added by jncharli on 2005 March the 30th

I tried this procedure, and it doesn't work. I found another procedure that I documented in HowTo.ChangePasswordsFromTheCommandLine

Changed lines 87-88 from:

2) Run the Web interface using admin as username, and admin as password.

   None of the users you have previously defined will run. I guess they are all stored in the passwd file that is on the disk you just disconnected.
to:

2) Run the Web interface using admin as username, and admin as password.

   None of the users you have previously defined will run as I guess they are all stored in the passwd file that is on the disk you just disconnected.
March 29, 2005, at 07:53 PM by jncharli --
Deleted lines 86-99:

Added by jncharli on 2005 March the 29th

My remark concerns UNSLUNG-3.x Family Release README INSTALLATION on section UNSLINGING DETAILS

Before Enable telnet by going to "http://192.168.1.77/Management/telnet.cgi", and press the enable button.

After Enable telnet by going to "http://192.168.1.77/Management/telnet.cgi" (username = admin, password = admin), and press the enable button.

March 29, 2005, at 07:51 PM by jncharli --
Changed line 67 from:

My remark concerns UNLUNG-3.x Family Release README INSTALLATION on section FIRMWARE INSTALLATION DETAILS

to:

My remark concerns UNSLUNG-3.x Family Release README INSTALLATION on section FIRMWARE INSTALLATION DETAILS

Changed lines 86-100 from:
     2-b) If you are installing Unslung 3.x onto an NSLU2 unit with version 3.x already installed, you must put the NSLU2 into maintenance mode before you can use... (unchanged)
to:
     2-b) If you are installing Unslung 3.x onto an NSLU2 unit with version 3.x already installed, you must put the NSLU2 into maintenance mode before you can use... (unchanged)

Added by jncharli on 2005 March the 29th

My remark concerns UNSLUNG-3.x Family Release README INSTALLATION on section UNSLINGING DETAILS

Before Enable telnet by going to "http://192.168.1.77/Management/telnet.cgi", and press the enable button.

After Enable telnet by going to "http://192.168.1.77/Management/telnet.cgi" (username = admin, password = admin), and press the enable button.

March 29, 2005, at 07:37 PM by jncharli --
Deleted line 69:
 2-a) Flash unslung-standard-3.x.bin as you normally would flash new firmware (using the web interface "Upgrade Firmware" page).
Changed lines 71-76 from:
 2-b) You must put the NSLU2 into maintenance mode before you can use... (to be continued)
to:

2) If you are installing UNSLUNG 3.x onto an NSLU2 unit with Linksys standard firmware *or* UNSLUNG 1.x or 2.x, go to step 2-a. If you are installing

     Unslung 3.x onto an NSLU2 unit with version 3.x already installed, go to step 2-b.

     2-a) Flash unslung-standard-3.x.bin as you normally would flash new firmware (using the web interface "Upgrade Firmware" page).

     2-b) You must put the NSLU2 into maintenance mode before you can use... (to be continued)
Deleted lines 79-81:
 2-a) Run the Web interface using admin as username, and admin as password.
      None of the users you have previously defined will run.
      I guess they are all stored in the passwd file that is on the disk you just disconnected.
Changed lines 81-84 from:
 2-b) Flash unslung-standard-3.x.bin as you normally would flash new firmware (using the web interface "Upgrade Firmware" page).
to:

2) Run the Web interface using admin as username, and admin as password.

   None of the users you have previously defined will run. I guess they are all stored in the passwd file that is on the disk you just disconnected.

     2-a) If you are installing UNSLUNG 3.x onto an NSLU2 unit with Linksys standard firmware *or* UNSLUNG 1.x or 2.x, flash unslung-standard-3.x.bin as you normally would flash new firmware (using the web interface "Upgrade Firmware" page).
Changed line 86 from:
 2-c) You must put the NSLU2 into maintenance mode before you can use... (unmodified)
to:
     2-b) If you are installing Unslung 3.x onto an NSLU2 unit with version 3.x already installed, you must put the NSLU2 into maintenance mode before you can use... (unchanged)
March 29, 2005, at 07:16 PM by jncharli --
Changed line 65 from:

"italics" Added by jncharli on 2005 March the 29th "italics"

to:

Added by jncharli on 2005 March the 29th

Changed line 67 from:

My remark concerns "bold" UNLUNG-3.x Family Release README INSTALLATION "bold" on section "bold" FIRMWARE INSTALLATION DETAILS "bold"

to:

My remark concerns UNLUNG-3.x Family Release README INSTALLATION on section FIRMWARE INSTALLATION DETAILS

Changed line 69 from:

"italics" Before "italics"

to:

Before

Changed lines 74-75 from:

"italics" after "italics"

to:

After

Changed lines 82-86 from:
 2-c) You must put the NSLU2 into maintenance mode before you can use... (unmodified)
to:
 2-c) You must put the NSLU2 into maintenance mode before you can use... (unmodified)
March 29, 2005, at 07:12 PM by jncharli --
Changed lines 59-85 from:

We have tried to make the README cover the most prevalent issues - emphasizing certain things so that newbies can follow the directions and have a usable Unslung NSLU2. We still expect you to be able to read documentation AND be familiar enough with the Linksys basic functionality to be running an Unslung NSLU2 without problems. Thank you for your suggestions to help make NSLU2-Linux documentation better.

to:

We have tried to make the README cover the most prevalent issues - emphasizing certain things so that newbies can follow the directions and have a usable Unslung NSLU2. We still expect you to be able to read documentation AND be familiar enough with the Linksys basic functionality to be running an Unslung NSLU2 without problems. Thank you for your suggestions to help make NSLU2-Linux documentation better.


"italics" Added by jncharli on 2005 March the 29th "italics"

My remark concerns "bold" UNLUNG-3.x Family Release README INSTALLATION "bold" on section "bold" FIRMWARE INSTALLATION DETAILS "bold"

"italics" Before "italics"

 2-a) Flash unslung-standard-3.x.bin as you normally would flash new firmware (using the web interface "Upgrade Firmware" page).

 2-b) You must put the NSLU2 into maintenance mode before you can use... (to be continued)

"italics" after "italics"

 2-a) Run the Web interface using admin as username, and admin as password.
      None of the users you have previously defined will run.
      I guess they are all stored in the passwd file that is on the disk you just disconnected.

 2-b) Flash unslung-standard-3.x.bin as you normally would flash new firmware (using the web interface "Upgrade Firmware" page).

 2-c) You must put the NSLU2 into maintenance mode before you can use... (unmodified)
March 23, 2005, at 11:22 AM by landge --
Added lines 9-47:

> README - Suggested change to the Unslinging details:

"Unslinging" is the process of configuring your NSLU. Basically it's a script (stored in /sbin/unsling) which configures the target location of the software your gonna install. You have two options.

1. Install the software on the external harddisk.

2. Install the software on the internal flash memory.

To run the unsling-script you have to be logged in as root (with a telnet session).

NOTE: There are two root-passwords. One is saved in a internal file called /usr/local/passwd (we know this one. It's "uNSLUng" and used when you boot without a attached harddisk) the other is stored in a external file called /share/hdd/conf/passwd (we don't know this one. It's used when you boot with a external harddisk attached). Later in the process you can change both of them. That means: Everytime you boot WITHOUT a attached harddisk you gain root-access with the "uNSLUng" password. If you boot with an attached harddisk, you'll don't have access until you change the file /share/hdd/conf/passwd.

Ad 1.)

  • Boot WITHOUT harddisk.
  • Enable telnet. (http://192.168.1.77/Management/telnet.cgi" - press enable button)
  • Login with telnet 192.168.1.77 login:root passwd: uNSLUng
  • Attach the harddisk - wait.
  • type "/sbin/unsling"

Now: Change your root-password:

  • type "passwd", enter and re-enter your new root-passwd.
  • type "cp /etc/passwd /share/hdd/conf/passwd"
  • type "ln -sf /share/hdd/conf/passwd /etc/passwd"
  • Reboot with harddisk, enable telnet via web-interface and you can login with your new password.
  • NOTE: When booting without harddisk, your root-password is still "uNSLUng"

COMMENT: I wrote this after my first Unslinging 3 days ago. I did NOT test it. It needs a REVIEW !!


March 05, 2005, at 08:32 PM by bobtm --
Added lines 14-16:

Focusing on "FIRMWARE INSTALLATION DETAILS" first: I just flashed Unslung 4.x, but it goes for 3.x too: During flashing, at least Firefox will hog 100% CPU (don't know about IE or others) - the flashing may take a long time, longer than 5 mins as reported by the web interface. You are adviced not to have other activities going on at the client while flashing - in my case, the virus-scanner timed out during scanning of an incoming mail and screamed bloody murder. Other than that, this section is still valid [ bob_tm-sick ]

February 18, 2005, at 12:26 PM by rwhitby --
Changed line 1 from:

Latest README at http://www.toddcomp.com/NSLU2/README.txt This is incorporated into the BK report, and should be used as a starting point for suggested changes.

to:

Latest README at http://www.toddcomp.com/NSLU2/README.txt This is incorporated into the BK repository, and should be used as a starting point for suggested changes.

February 18, 2005, at 03:14 AM by ByronT --
Changed lines 17-32 from:

> I'm a newbie. I found the part about the root password extremely confusing. I think you need to say something about changing the root password more explicitly. I unslung to my flash drive, then plugged in my hard drive, and was baffled to discover later that I could no longer log in as root (I had not changed the root password). I really thought I had destroyed the device, but managed to use the reset buttons a couple of times before I realized that the original root password from the original firmware was on my harddrive). I think part of the confusion derives from statements like "Starting with UNSLUNG 3.x, the external disk is no longer used for the root filesystem" - which are not helpful to newbies who are trying to follow the README exactly as written.

[ByronT? - response] We have addressed this issue in many places. The README plainly states:

"***** Unsling will not change the password on your disk, so if you had previously changed the password on a disk, then your password will not be changed. Also note that simply editing the /etc/passwd file is not enough to permanently change a password. See:"
http://www.nslu2-linux.org/wiki/HowTo/ChangePasswordsFromTheCommandLine

If you read the README completely, you can't miss that. We have tried to make the README cover the most prevalent issues - emphasizing certain things so that newbies can follow the directions and have a usable Unslung NSLU2. We still expect you to be able to read documentation AND be familiar enough with the Linksys basic functionality to be running an Unslung NSLU2 without problems. However, we cannot read the documentation for you, nor make you understand it. That is not to say that the documentation is perfect, nor that it couldn't use improvement.

ChrisParker? - I recently flashed my NSLU with unslung 3.18. I read the entire README through (like a good user) and then read it again, and started the procedure. When I got to actually flashing the thing, The first time there seemed to be some sort of error. I know you can't accomodate for every error, but it was an error that left me wondering if I had flashed or not. You might want to put in the README that the top light flashes green and red while the flash is happening, and that you SHOULD get a Javascript message that says the flash went ok after about 5 minutes. The first time I got neither of these and (after waiting 10 minutes) had concluded the flash never happend.

[ByronT? - Response] Not a bad idea! Will be implemented. Thank you!


to:

We have tried to make the README cover the most prevalent issues - emphasizing certain things so that newbies can follow the directions and have a usable Unslung NSLU2. We still expect you to be able to read documentation AND be familiar enough with the Linksys basic functionality to be running an Unslung NSLU2 without problems. Thank you for your suggestions to help make NSLU2-Linux documentation better.

February 17, 2005, at 06:03 PM by ByronT --
Added lines 8-9:

SUGGESTIONS GO HERE!!!!

Added lines 27-30:

ChrisParker? - I recently flashed my NSLU with unslung 3.18. I read the entire README through (like a good user) and then read it again, and started the procedure. When I got to actually flashing the thing, The first time there seemed to be some sort of error. I know you can't accomodate for every error, but it was an error that left me wondering if I had flashed or not. You might want to put in the README that the top light flashes green and red while the flash is happening, and that you SHOULD get a Javascript message that says the flash went ok after about 5 minutes. The first time I got neither of these and (after waiting 10 minutes) had concluded the flash never happend.

[ByronT? - Response] Not a bad idea! Will be implemented. Thank you!

Changed line 32 from:

I recently flashed my NSLU with unslung 3.18. I read the entire README through (like a good user) and then read it again, and started the procedure. When I got to actually flashing the thing, The first time there seemed to be some sort of error. I know you can't accomodate for every error, but it was an error that left me wondering if I had flashed or not. You might want to put in the README that the top light flashes green and red while the flash is happening, and that you SHOULD get a Javascript message that says the flash went ok after about 5 minutes. The first time I got neither of these and (after waiting 10 minutes) had concluded the flash never happend.

to:
February 17, 2005, at 05:57 PM by Chris Parker --
Added lines 24-26:

I recently flashed my NSLU with unslung 3.18. I read the entire README through (like a good user) and then read it again, and started the procedure. When I got to actually flashing the thing, The first time there seemed to be some sort of error. I know you can't accomodate for every error, but it was an error that left me wondering if I had flashed or not. You might want to put in the README that the top light flashes green and red while the flash is happening, and that you SHOULD get a Javascript message that says the flash went ok after about 5 minutes. The first time I got neither of these and (after waiting 10 minutes) had concluded the flash never happend.

February 09, 2005, at 09:53 PM by ByronT --
Deleted lines 23-36:

>> - If you run out of room on the "conf" partition, you can always put >> symlinks across to the "data" partition. From a prompt: > >Wouldn't it be better to do: > mkdir -p /share/hdd/data/unslung > cp -R /share/hdd/conf/unslung/* /share/hdd/data/unslung && ln -s >/share/hdd/data/unslung /unslung && rm -rf /share/hdd/conf/unslung > >(i.e. with the &&'s and using cp rather than mv) > >That way if the cp fails for some reason (out of disk space) then nothing will >break. Also if any cron jobs or other stuff runs that uses the unslung it won't >break either.

[ByronT? - response] Agreed. Next revision - this will be updated.

February 07, 2005, at 06:59 PM by ByronT --
Changed line 1 from:

ByronT? reworded the README at http://www.toddcomp.com/NSLU2/README.txt. This is being incorporated into the BK repo. Please use this as a starting point for any other suggested changes.

to:

Latest README at http://www.toddcomp.com/NSLU2/README.txt This is incorporated into the BK report, and should be used as a starting point for suggested changes.

Changed line 3 from:

Note: The README cannot be all things to all people (though I swear we've tried!). The idea is that the README should serve as "installation documentation on the go" - meaning that it gives you something to print out and use for installing Unslung firmware and that's it. We have emphasized certain things that have been missed and caused some users problems.

to:

Latest NOTES at http://www.toddcomp.com/NSLU2/NOTES.txt This file is considered to be initial "usage" notes for the Unslung firmware - "doco on the go." Please suggest changes for that documentation here as well.

Deleted lines 4-5:

For general usage notes, the NOTES.txt file [http://www.toddcomp.com/NSLU2/NOTES.txt] is included for basic information as well as usage notes. In no way is the NOTES.txt supposed to replace or cover the breadth or depth of information that can be found in this wiki. NOTES.txt will be updated as needed *BUT* the wiki should serve you as your FIRST source of information.

Changed line 6 from:

Please add new suggestions below this line, prefixed by a > so we can easily spot new suggestions and answer them, but before the next separation (----) so that what is being worked on will not be confused with new issues.

to:

Please add new suggestions below this line, prefixed by a > so we can easily spot new suggestions and answer them, but before the next separation (----) so that what is being worked on will not be confused with new issues. Also state whether the suggested change is to NOTES or to README as shown below. Thank you for your suggestions.

Changed line 8 from:

> I'm a newbie. I found the part about the root password extremely confusing. I think you need to say something about changing the root password more explicitly. I unslung to my flash drive, then plugged in my hard drive, and was baffled to discover later that I could no longer log in as root (I had not changed the root password). I really thought I had destroyed the device, but managed to use the reset buttons a couple of times before I realized that the original root password from the original firmware was on my harddrive). I think part of the confusion derives from statements like "Starting with UNSLUNG 3.x, the external disk is no longer used for the root filesystem" - which are not helpful to newbies who are trying to follow the README exactly as written.

to:

>NOTES - Suggested change

Added line 10:

>README - Suggested change

Added lines 15-17:

> I'm a newbie. I found the part about the root password extremely confusing. I think you need to say something about changing the root password more explicitly. I unslung to my flash drive, then plugged in my hard drive, and was baffled to discover later that I could no longer log in as root (I had not changed the root password). I really thought I had destroyed the device, but managed to use the reset buttons a couple of times before I realized that the original root password from the original firmware was on my harddrive). I think part of the confusion derives from statements like "Starting with UNSLUNG 3.x, the external disk is no longer used for the root filesystem" - which are not helpful to newbies who are trying to follow the README exactly as written.

[ByronT? - response] We have addressed this issue in many places. The README plainly states:

Changed line 19 from:

> Could we move the "upgrade" considerations and instructions into a section by >itself. My reasoning: ideally we want everyone's slug to be configured the same >(so - no /unslung directory, for example), so more depth could be given to >exactly how to turn an existing older slug into what a newbie would have. Also >Mixing old + new instructions just confuses newbies who never had the things >before (e.g. PRE-CONSIDERATIONS #2 and #3 contain info that isn't useful to >newbies, the FIRMWARE section starts splitting up with a 2a and 2b, making >reading harder than it otherwise would be, etc.)

to:
"***** Unsling will not change the password on your disk, so if you had previously changed the password on a disk, then your password will not be changed. Also note that simply editing the /etc/passwd file is not enough to permanently change a password. See:"
Changed lines 21-23 from:

[ByronT? - response] Not a bad idea, however, my idea of the README (and devs are welcome to correct me) is for installation doco on the go. Meaning that either upgraders or newbies can print out README and get their NSLU2 unslung without having to go anywhere else UNLESS a problem arises. When that happens, then the reader goes to wiki.

to:
http://www.nslu2-linux.org/wiki/HowTo/ChangePasswordsFromTheCommandLine

If you read the README completely, you can't miss that. We have tried to make the README cover the most prevalent issues - emphasizing certain things so that newbies can follow the directions and have a usable Unslung NSLU2. We still expect you to be able to read documentation AND be familiar enough with the Linksys basic functionality to be running an Unslung NSLU2 without problems. However, we cannot read the documentation for you, nor make you understand it. That is not to say that the documentation is perfect, nor that it couldn't use improvement.

Changed lines 36-46 from:

[ByronT? - response] No idea on this one. Waiting for a dev to weigh in on the issue.


I have added my specific replies to below issues in double brackets

> efore the diversion script is called. This allows you to use the variables and functions defined by the factory script.

A list of the "factory" scripts that can be diverted would be useful... e.g.

  /unslung/rc.local  (this does x)
  /rc.xinetd  (this does y)
to:

[ByronT? - response] Agreed. Next revision - this will be updated.

Deleted lines 37-38:

[rwhitby: agreed]
ByronT: unfinished business? DANG! Issue here is that factory scripts should be wiki based... Let's leave README for documentation on the go - something to print out and use for installation and running. If more is wanted to be done to the slug, then consult wiki NOT README.

January 31, 2005, at 11:06 PM by ByronT --
Changed line 5 from:

For general usage notes, the NOTES.txt file [http://www.toddcomp.com/NSLU2/NOTES.txt] is included for basic information as well as notes. In no way is the NOTES.txt supposed to replace or cover the breadth or depth of information that can be found in this wiki. NOTES.txt will be updated as needed *BUT* the wiki should serve you as your FIRST source of information.

to:

For general usage notes, the NOTES.txt file [http://www.toddcomp.com/NSLU2/NOTES.txt] is included for basic information as well as usage notes. In no way is the NOTES.txt supposed to replace or cover the breadth or depth of information that can be found in this wiki. NOTES.txt will be updated as needed *BUT* the wiki should serve you as your FIRST source of information.

January 31, 2005, at 11:05 PM by ByronT --
Changed line 3 from:

Note: The README cannot be all things to all people (though I swear we've tried!). The idea is that the README should serve as "installation documentation on the go" - meaning that it gives you something to print out and use for installing Unslung firmware and that's it.

to:

Note: The README cannot be all things to all people (though I swear we've tried!). The idea is that the README should serve as "installation documentation on the go" - meaning that it gives you something to print out and use for installing Unslung firmware and that's it. We have emphasized certain things that have been missed and caused some users problems.

Changed line 5 from:

We have emphasized certain things that have caused some users problems. For general usage notes, the NOTES.txt file [http://www.toddcomp.com/NSLU2/NOTES.txt] is included for basic information as well as notes. In no way is the NOTES.txt supposed to replace or cover the breadth or depth of information that can be found in this wiki. NOTES.txt will be updated as needed *BUT* the wiki should serve you as your FIRST source of information.

to:

For general usage notes, the NOTES.txt file [http://www.toddcomp.com/NSLU2/NOTES.txt] is included for basic information as well as notes. In no way is the NOTES.txt supposed to replace or cover the breadth or depth of information that can be found in this wiki. NOTES.txt will be updated as needed *BUT* the wiki should serve you as your FIRST source of information.

January 31, 2005, at 10:40 PM by ByronT --
Changed line 1 from:

ByronT? reworded the README at http://www.toddcomp.com/NSLU2/Unslung-3.1x-README.txt. This is being incorporated into the BK repo. Please use this as a starting point for any other suggested changes.

to:

ByronT? reworded the README at http://www.toddcomp.com/NSLU2/README.txt. This is being incorporated into the BK repo. Please use this as a starting point for any other suggested changes.

Changed line 3 from:

Note: The README cannot be all things to all people (though I swear we've tried!). The idea is that the README should serve as "documentation on the go" - meaning that it gives you something to print out and use for installing Unslung firmware and some basic usage notes. We have emphasized certain things that have caused some users problems. Other issues are left to be worked out here on the Wiki. PLEASE, PLEASE use the wiki if at all possible - certain items (such as passwd/telnet issues) are EASILY found by searching/using the wiki.

to:

Note: The README cannot be all things to all people (though I swear we've tried!). The idea is that the README should serve as "installation documentation on the go" - meaning that it gives you something to print out and use for installing Unslung firmware and that's it.

Added lines 5-6:

We have emphasized certain things that have caused some users problems. For general usage notes, the NOTES.txt file [http://www.toddcomp.com/NSLU2/NOTES.txt] is included for basic information as well as notes. In no way is the NOTES.txt supposed to replace or cover the breadth or depth of information that can be found in this wiki. NOTES.txt will be updated as needed *BUT* the wiki should serve you as your FIRST source of information.

Changed lines 19-28 from:

[ByronT? - response] Not a bad idea, however, my idea of the README (and devs are welcome to correct me) is for doco on the go. Meaning that either upgraders or newbies can print out README and get their NSLU2 unslung without having to go anywhere else UNLESS a problem arises. When that happens, then the reader goes to wiki.

>> ***** Unsling will not change the password on your disk, so if you had >> previously changed the password on a disk, then your password will >> not be changed. Also note that simply editing the /etc/passwd file >> is not enough to permanently change a password. See > >Is this still true? I don't remember mv'ing and ln'ing my passwd file after >unslinging. I remember just running passwd and that being it? Or have I a bad >memory ;)

[ByronT? - response] If you changed your passwd earlier - the correct way, then it is saved on the hd and *stuck*.

to:

[ByronT? - response] Not a bad idea, however, my idea of the README (and devs are welcome to correct me) is for installation doco on the go. Meaning that either upgraders or newbies can print out README and get their NSLU2 unslung without having to go anywhere else UNLESS a problem arises. When that happens, then the reader goes to wiki.

Deleted lines 32-48:

> Consider moving the DIVERSIONSCRIPTS out completely and just having a pointer to the wiki; it's probably not needed here. Also - the references to /unslung should be only mentioned in an "advanced" context / heading of it's own - we generally want all users to use the /share/hdd/conf/unslung directory instead to reduce the risk of broken scripts. I realise there is a warning here but it's the first thing mentioned and the example also uses /unslung so people will just copy that...

[ByronT? - response] This goes back to the issue at top. README is more than just installation. I would prefer it stay that way - but I won't force my decision on everyone else. (I maintain a few wiki pages that mirror README information as well).

> A short section on what directories will be automatically regenerated at reboot time would be useful. e.g. if I create a file in /tmp, will it stick? How about changes in /etc? Or new links in /bin? If they do stick - will they stick through a firmware upgrade? if not - then a section on backing up and restoring before firmware upgrading would be great too.

[ByronT? - response] "short section on..." <- Good idea for "documentation", but I don't think we want this in-depth type information in README - use the wiki, wiki!!!. However, there is already some information about using the "resling" script to save filesystem changes through f/w upgrades (with really only /opt and /unslung staying untouched). As for backing up and restoring CONFIGURATION, that has now been added to the Preinstallation Considerations #5 of README.

> In PRE-INSTALLATION CONSIDERATIONS #5, should the backup operation be done with disks connected or with disks disconnected? It's a bit ambiguous, given how much emphasis has been given to removing any attached disks.

[ByronT? - response] Devs? Oh puhlease. Does it say remove disks? Do we really have to teach logical decision making via the README?

> In FIRMWARE INSTALLATION DETAILS #2, it might be worth mentioning that that user/password will revert to admin/admin without disks attached.

[ByronT? - response] What? When? Where?

January 31, 2005, at 08:26 PM by ByronT --
Added lines 3-4:

Note: The README cannot be all things to all people (though I swear we've tried!). The idea is that the README should serve as "documentation on the go" - meaning that it gives you something to print out and use for installing Unslung firmware and some basic usage notes. We have emphasized certain things that have caused some users problems. Other issues are left to be worked out here on the Wiki. PLEASE, PLEASE use the wiki if at all possible - certain items (such as passwd/telnet issues) are EASILY found by searching/using the wiki.

Deleted lines 27-32:

>> guessed!) In general, ipkg packages are commonly availabe software packages > >A smelling mistooke. "availabe" -> "available". Might be worth running spell on >the rest too just in case.

[ByronT? - response] Yes, I spent almost three days working on README. I'm taking a break and will get around to fixing my spelling mistakes and omissions (I've already noticed one or two ;) ).

Deleted lines 49-55:

> The address about Redboot in PRE-INSTALLATION CONSIDERATIONS #1 is misspelled: http://www.nslu2-linux.org/wiwki/HowTo/RecoverFromABadFlash should be http://www.nslu2-linux.org/wiki/HowTo/RecoverFromABadFlash

[ByronT? - repsonse] Yes, a spelling error. I'll go find my hari kari sword.

Deleted lines 57-59:

> In FIRMWARE INSTALLATION DETAILS #4, it is not entirely clear whether I need to do the unslinging (#5) if I am upgrading from a previous version of unslung (e.g. 1.11). What exactly does "first installation" mean? Does it refer to first installation of 3.x or the first installation of any unslung?

[ByronT? - response] Researching. After any f/w upgrade, an unslinging should always be performed. Will update README - next revision - due Sunday/Monday 1/30 or 1/31...

January 30, 2005, at 05:49 PM by thomas144 --
Added lines 6-7:

> I'm a newbie. I found the part about the root password extremely confusing. I think you need to say something about changing the root password more explicitly. I unslung to my flash drive, then plugged in my hard drive, and was baffled to discover later that I could no longer log in as root (I had not changed the root password). I really thought I had destroyed the device, but managed to use the reset buttons a couple of times before I realized that the original root password from the original firmware was on my harddrive). I think part of the confusion derives from statements like "Starting with UNSLUNG 3.x, the external disk is no longer used for the root filesystem" - which are not helpful to newbies who are trying to follow the README exactly as written.

January 29, 2005, at 06:39 PM by ByronT --
Added lines 6-10:

NSLU2 Users: Please do not modify information below this line, as it contains information for review by NSLU2 developers.

Added lines 13-14:

[ByronT? - response] Not a bad idea, however, my idea of the README (and devs are welcome to correct me) is for doco on the go. Meaning that either upgraders or newbies can print out README and get their NSLU2 unslung without having to go anywhere else UNLESS a problem arises. When that happens, then the reader goes to wiki.

Added lines 22-23:

[ByronT? - response] If you changed your passwd earlier - the correct way, then it is saved on the hd and *stuck*.

Added lines 28-29:

[ByronT? - response] Yes, I spent almost three days working on README. I'm taking a break and will get around to fixing my spelling mistakes and omissions (I've already noticed one or two ;) ).

Added lines 41-42:

[ByronT? - response] No idea on this one. Waiting for a dev to weigh in on the issue.

Changed line 45 from:

> I've read through the rest of it and nothing else jumps out; you can archive off the rest of the suggestions I made below (as uSURPER). Thanks :) Paul

to:

[ByronT? - response] This goes back to the issue at top. README is more than just installation. I would prefer it stay that way - but I won't force my decision on everyone else. (I maintain a few wiki pages that mirror README information as well).

Changed line 50 from:

ByronT? - "short section on..." <- Good idea for "documentation", but I don't think we want this in-depth type information in README - use the wiki, wiki!!!. However, there is already some information about using the "resling" script to save filesystem changes through f/w upgrades (with really only /opt and /unslung staying untouched). As for backing up and restoring CONFIGURATION, that has now been added to the Preinstallation Considerations #5 of README.

to:

[ByronT? - response] "short section on..." <- Good idea for "documentation", but I don't think we want this in-depth type information in README - use the wiki, wiki!!!. However, there is already some information about using the "resling" script to save filesystem changes through f/w upgrades (with really only /opt and /unslung staying untouched). As for backing up and restoring CONFIGURATION, that has now been added to the Preinstallation Considerations #5 of README.

Added lines 57-58:

[ByronT? - repsonse] Yes, a spelling error. I'll go find my hari kari sword.

Added lines 61-62:

[ByronT? - response] Devs? Oh puhlease. Does it say remove disks? Do we really have to teach logical decision making via the README?

Added lines 65-66:

[ByronT? - response] What? When? Where?

Changed lines 69-76 from:

NSLU2 Users: Please do not modify information below this line, as it contains information for review by NSLU2 developers.

UPDATE

Previous Suggestions - Waiting to depracate after review.

to:

[ByronT? - response] Researching. After any f/w upgrade, an unslinging should always be performed. Will update README - next revision - due Sunday/Monday 1/30 or 1/31...

Deleted lines 73-126:

> 1) It is strongly recommended that you test telnet RedBoot access first. See http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot

Why is this? An explanation of _why_ it's strongly recommended might be nice *especially* since it's pretty difficult to do in a "normal" environment (relies on timing, all the scripts are Linux based and most people use Windows, etc).

[rwhitby: agreed]
ByronT: done? Explanation added and link to page that gives further information as to why this is strongly recommended.

This can be done in Windows. If you are connected to the network or directly to the NSLU. You have to telnet at command prompt first and immediate reboot/start the NSLU. The telnet command will stay active for a short period and you can connect if you time it correctly.

> 4) Verify your NSLU2 is working normally again at this point - in the web interface. In particular, you should ensure that all your disks are still recognized as they were before you updated the firmware.

... "updated the firmare and that any shares and data you previously had stored are available. If not, do not continue."

[rwhitby: agreed]
ByronT: done? Two locations where the user needs to verify disk/users/groups/shares functionality. Both places update.

> 5) Shutdown the NSLU2 and unplug *ALL* attached disks.

- You must NOT have any disk plugged into the NSLU2 when you reboot to perform the next part of installation - the "Unslinging".

This should be moved to point 1 of the uNSLUng portion - if you aren't unslunging then you don't need to do this, you stop at point 4.

[rwhitby: agreed]
ByronT: done? I think we all realize that unplugging disks for upgrades/prior to unslinging cannot be emphasized enough. So an outlet for those who are not unslinging has been added - RETAINING the emphasis on unplugged disks.

> permanently change a password. See the NSLU2 wiki for more details.

Which part of the wiki? Where? A hyperlink would be great here.

[rwhitby: agreed]
ByronT: done? Section edited, clarified, and link provided.

> 5) Reboot.

Move this to point 6 and add the following for point 5) 5) Create an unslung directory for storing any packages you may decide to download as follows: mkdir /share/hdd/conf/unslung && ln -s /share/hdd/conf/unslung /unslung

[rwhitby: agreed]
ByronT: done? This was addressed in a reworking of the entire diversion script section. As I understand it, /unslung DOES NOT always have to be a symlink in order that "Pluggable Personalities" can be used as well as diversion scripts working without any drives plugged in.

> And if you run out of room on the "conf" partition, you can always put symlinks across to the "data" partition too.

How, where? i.e. can we have an example like mkdir /share/hdd/data/unslung && mv /unslung/* /share/hdd/data/unslung && rm -rf /unslung && ln -s /share/hdd/data/unslung /unslung (or something better).

[rwhitby: agreed]
ByronT: done? Ditto above. Reworked.

Or -- why not just do this in #5 above and avoid using /conf at all if it's going to potentially be a problem that users will see?

[cause it's not usually a problem, and we don't want to mess with the user's data partition]

Deleted lines 81-112:

> 0) Note that you must have network connectivity to the package

Can we have the lists (throughout) starting at 1 please.

[rwhitby: agreed]
ByronT: done? Easiest fix of all.

> 0) Note that you must have network connectivity to the package repository at http://ipkg.nslu2-linux.org before proceeding. You must also confirm that your DNS server address is set in the web interface, or the NSLU2 will not be able to find the site.

How about 0) You need to have network connectivity to the package repositry at http://ipky.nslu2-linux.org before proceeding. A simple way of testing this is to: ping ipkg.nslu2-linux.org. If this doesn't work please check your NSLU2 has the correct DNS setting in the web interface.

[rwhitby: agreed]
ByronT: done? Reworked. Links provided.

> 1) Run "ipkg update" on the NSLU2.

1) Run "ipkg update" on the NSLU2. This updates the list of available "ipkg" packages.

[rwhitby: agreed]
ByronT: done? Reworded and clarified.

> 5) This simple diversion script will enable telnet on boot > > [ Store the following in /unslung/rc.xinetd ]

[ Save the following as a script called /unslung/rc.xinetd and reboot your NSLU2]

[rwhitby: agreed]
ByronT: done? Addressed as part of Diversion Script reworking.

January 29, 2005, at 02:46 PM by MattMcNeill --
Added lines 46-47:

> In FIRMWARE INSTALLATION DETAILS #2, it might be worth mentioning that that user/password will revert to admin/admin without disks attached.

January 29, 2005, at 02:44 PM by MattMcNeill --
Added lines 46-47:

> In FIRMWARE INSTALLATION DETAILS #4, it is not entirely clear whether I need to do the unslinging (#5) if I am upgrading from a previous version of unslung (e.g. 1.11). What exactly does "first installation" mean? Does it refer to first installation of 3.x or the first installation of any unslung?

January 29, 2005, at 02:29 PM by MattMcNeill --
Deleted line 39:
Deleted line 40:
Deleted line 41:
Changed line 44 from:
to:

> In PRE-INSTALLATION CONSIDERATIONS #5, should the backup operation be done with disks connected or with disks disconnected? It's a bit ambiguous, given how much emphasis has been given to removing any attached disks.

January 29, 2005, at 02:17 PM by MattMcNeill --
Added lines 39-48:

> The address about Redboot in PRE-INSTALLATION CONSIDERATIONS #1 is misspelled:

http://www.nslu2-linux.org/wiwki/HowTo/RecoverFromABadFlash

should be

http://www.nslu2-linux.org/wiki/HowTo/RecoverFromABadFlash

January 29, 2005, at 09:43 AM by paulhar --
Added lines 6-32:

> Could we move the "upgrade" considerations and instructions into a section by >itself. My reasoning: ideally we want everyone's slug to be configured the same >(so - no /unslung directory, for example), so more depth could be given to >exactly how to turn an existing older slug into what a newbie would have. Also >Mixing old + new instructions just confuses newbies who never had the things >before (e.g. PRE-CONSIDERATIONS #2 and #3 contain info that isn't useful to >newbies, the FIRMWARE section starts splitting up with a 2a and 2b, making >reading harder than it otherwise would be, etc.)

>> ***** Unsling will not change the password on your disk, so if you had >> previously changed the password on a disk, then your password will >> not be changed. Also note that simply editing the /etc/passwd file >> is not enough to permanently change a password. See > >Is this still true? I don't remember mv'ing and ln'ing my passwd file after >unslinging. I remember just running passwd and that being it? Or have I a bad >memory ;)

>> guessed!) In general, ipkg packages are commonly availabe software packages > >A smelling mistooke. "availabe" -> "available". Might be worth running spell on >the rest too just in case.

>> - If you run out of room on the "conf" partition, you can always put >> symlinks across to the "data" partition. From a prompt: > >Wouldn't it be better to do: > mkdir -p /share/hdd/data/unslung > cp -R /share/hdd/conf/unslung/* /share/hdd/data/unslung && ln -s >/share/hdd/data/unslung /unslung && rm -rf /share/hdd/conf/unslung > >(i.e. with the &&'s and using cp rather than mv) > >That way if the cp fails for some reason (out of disk space) then nothing will >break. Also if any cron jobs or other stuff runs that uses the unslung it won't >break either.

> Consider moving the DIVERSIONSCRIPTS out completely and just having a pointer to the wiki; it's probably not needed here. Also - the references to /unslung should be only mentioned in an "advanced" context / heading of it's own - we generally want all users to use the /share/hdd/conf/unslung directory instead to reduce the risk of broken scripts. I realise there is a warning here but it's the first thing mentioned and the example also uses /unslung so people will just copy that...

> I've read through the rest of it and nothing else jumps out; you can archive off the rest of the suggestions I made below (as uSURPER). Thanks :) Paul

January 29, 2005, at 08:16 AM by ByronT --
Changed line 1 from:

ByronT? reworded the README at http://www.toddcomp.com/NSLU2/Unslung-3.17-README.txt. This has been incorporated into the BK repo. Please use this as a starting point for any other suggested changes.

to:

ByronT? reworded the README at http://www.toddcomp.com/NSLU2/Unslung-3.1x-README.txt. This is being incorporated into the BK repo. Please use this as a starting point for any other suggested changes.

Changed line 16 from:

UPDATE

to:

UPDATE

Changed line 18 from:

New README for review at http://www.toddcomp.com/NSLU2/Unslung-3.1x-README.txt.

to:

Previous Suggestions - Waiting to depracate after review.

January 29, 2005, at 07:56 AM by ByronT --
Changed line 18 from:

New README for review at http://www.toddcomp.com/NSLU2/Unslung-3.1x-README.txt. That file is the "all-in-one" file. For separated documentation, please review http://www.toddcomp.com/NSLU2/Unslung-3.1x-beta-README.txt [Installation] and http://www.toddcomp.com/NSLU2/Unslung-3.1x-beta-Notes.txt [Usage Notes]

to:

New README for review at http://www.toddcomp.com/NSLU2/Unslung-3.1x-README.txt.

January 27, 2005, at 06:28 PM by ByronT --
Added lines 10-11:

ByronT? - "short section on..." <- Good idea for "documentation", but I don't think we want this in-depth type information in README - use the wiki, wiki!!!. However, there is already some information about using the "resling" script to save filesystem changes through f/w upgrades (with really only /opt and /unslung staying untouched). As for backing up and restoring CONFIGURATION, that has now been added to the Preinstallation Considerations #5 of README.

Added line 92:
January 27, 2005, at 06:14 PM by ByronT --
Added lines 18-19:

Changed line 27 from:

[rwhitby: agreed]

to:

[rwhitby: agreed]\\

Changed line 36 from:

[rwhitby: agreed]

to:

[rwhitby: agreed]\\

Changed line 45 from:

[rwhitby: agreed]

to:

[rwhitby: agreed]\\

Changed line 52 from:

[rwhitby: agreed]

to:

[rwhitby: agreed]\\

Changed line 60 from:

[rwhitby: agreed]

to:

[rwhitby: agreed]\\

Changed line 69 from:

[rwhitby: agreed]

to:

[rwhitby: agreed]\\

Changed line 82 from:

[rwhitby: agreed]

to:

[rwhitby: agreed]\\

Changed line 89 from:

[rwhitby: agreed]

to:

[rwhitby: agreed]\\

Changed line 97 from:

[rwhitby: agreed]

to:

[rwhitby: agreed]\\

Changed line 104 from:

[rwhitby: agreed]

to:

[rwhitby: agreed]\\

Changed line 113 from:

[rwhitby: agreed]

to:

[rwhitby: agreed]\\

January 27, 2005, at 06:10 PM by ByronT --
Added lines 12-20:

NSLU2 Users: Please do not modify information below this line, as it contains information for review by NSLU2 developers.

UPDATE

New README for review at http://www.toddcomp.com/NSLU2/Unslung-3.1x-README.txt. That file is the "all-in-one" file. For separated documentation, please review http://www.toddcomp.com/NSLU2/Unslung-3.1x-beta-README.txt [Installation] and http://www.toddcomp.com/NSLU2/Unslung-3.1x-beta-Notes.txt [Usage Notes]

I have added my specific replies to below issues in double brackets

Added line 26:

ByronT: done? Explanation added and link to page that gives further information as to why this is strongly recommended.

Added line 35:

ByronT: done? Two locations where the user needs to verify disk/users/groups/shares functionality. Both places update.

Added line 44:

ByronT: done? I think we all realize that unplugging disks for upgrades/prior to unslinging cannot be emphasized enough. So an outlet for those who are not unslinging has been added - RETAINING the emphasis on unplugged disks.

Added line 51:

ByronT: done? Section edited, clarified, and link provided.

Added lines 59-60:

ByronT: done? This was addressed in a reworking of the entire diversion script section. As I understand it, /unslung DOES NOT always have to be a symlink in order that "Pluggable Personalities" can be used as well as diversion scripts working without any drives plugged in.

Added line 68:

ByronT: done? Ditto above. Reworked.

Added line 81:

ByronT: unfinished business? DANG! Issue here is that factory scripts should be wiki based... Let's leave README for documentation on the go - something to print out and use for installation and running. If more is wanted to be done to the slug, then consult wiki NOT README.

Added line 88:

ByronT: done? Easiest fix of all.

Added line 96:

ByronT: done? Reworked. Links provided.

Added line 103:

ByronT: done? Reworded and clarified.

Added line 112:

ByronT: done? Addressed as part of Diversion Script reworking.

January 26, 2005, at 10:34 PM by ByronT --
Changed line 28 from:
	- You must NOT have any disk plugged into the NSLU2 when you reboot to perform the next part of installation - the "Unslinging".
to:

- You must NOT have any disk plugged into the NSLU2 when you reboot to perform the next part of installation - the "Unslinging".

January 26, 2005, at 10:32 PM by ByronT --
Changed line 4 from:

Please add new suggestions below this line, prefixed by a > so we can easily spot new suggestions and answer them.

to:

Please add new suggestions below this line, prefixed by a > so we can easily spot new suggestions and answer them, but before the next separation (----) so that what is being worked on will not be confused with new issues.

Added line 10:

January 26, 2005, at 10:16 PM by davlan --
Added lines 17-18:

This can be done in Windows. If you are connected to the network or directly to the NSLU. You have to telnet at command prompt first and immediate reboot/start the NSLU. The telnet command will stay active for a short period and you can connect if you time it correctly.

January 26, 2005, at 12:12 PM by paulhar --
Changed lines 1-8 from:
to:

ByronT? reworded the README at http://www.toddcomp.com/NSLU2/Unslung-3.17-README.txt. This has been incorporated into the BK repo. Please use this as a starting point for any other suggested changes.


Please add new suggestions below this line, prefixed by a > so we can easily spot new suggestions and answer them.

> A short section on what directories will be automatically regenerated at reboot time would be useful. e.g. if I create a file in /tmp, will it stick? How about changes in /etc? Or new links in /bin? If they do stick - will they stick through a firmware upgrade? if not - then a section on backing up and restoring before firmware upgrading would be great too.

Deleted line 9:

ByronT? reworded the README at http://www.toddcomp.com/NSLU2/Unslung-3.17-README.txt. This has been incorporated into the BK repo. Please use this as a starting point for any other suggested changes.

January 14, 2005, at 02:34 AM by tman --
Changed lines 5-6 from:

> 1) It is strongly recommended that you test telnet Redboot access

   first.  See http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot
to:

> 1) It is strongly recommended that you test telnet RedBoot access first. See http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot

Changed lines 11-13 from:

> 4) Verify your NSLU2 is working normally again at this point - in the

   web interface.  In  particular, you should ensure that all your disks are
   still recognized as they were before you updated the firmware.
to:

> 4) Verify your NSLU2 is working normally again at this point - in the web interface. In particular, you should ensure that all your disks are still recognized as they were before you updated the firmware.

Changed lines 19-20 from:
	- You must NOT have any disk plugged into the NSLU2 when you reboot
          to perform the next part of installation - the "Unslinging".
to:
	- You must NOT have any disk plugged into the NSLU2 when you reboot to perform the next part of installation - the "Unslinging".
Changed lines 52-53 from:

/unslung/rc.local (this does x)

        /rc.xinetd (this does y)
to:
  /unslung/rc.local  (this does x)
  /rc.xinetd  (this does y)
Changed lines 63-66 from:

> 0) Note that you must have network connectivity to the package

   repository at http://ipkg.nslu2-linux.org before proceeding.
   You must also confirm that your DNS server address is set in the
   web interface, or the NSLU2 will not be able to find the site.
to:

> 0) Note that you must have network connectivity to the package repository at http://ipkg.nslu2-linux.org before proceeding. You must also confirm that your DNS server address is set in the web interface, or the NSLU2 will not be able to find the site.

Changed lines 66-67 from:

0) You need to have network connectivity to the package repositry at http://ipky.nslu2-linux.org before proceeding. A simple way of testing this is to:

 ping ipkg.nslu2-linux.org. If this doesn't work please check your NSLU2 has the correct DNS setting in the web interface.
to:

0) You need to have network connectivity to the package repositry at http://ipky.nslu2-linux.org before proceeding. A simple way of testing this is to: ping ipkg.nslu2-linux.org. If this doesn't work please check your NSLU2 has the correct DNS setting in the web interface.

January 13, 2005, at 09:03 PM by rwhitby --
Added lines 10-11:

[rwhitby: agreed]

Added lines 18-19:

[rwhitby: agreed]

Added lines 27-28:

[rwhitby: agreed]

Added lines 33-34:

[rwhitby: agreed]

Added lines 40-41:

[rwhitby: agreed]

Added lines 47-48:

[rwhitby: agreed]

Added lines 51-52:

[cause it's not usually a problem, and we don't want to mess with the user's data partition]

Added lines 59-60:

[rwhitby: agreed]

Added lines 65-66:

[rwhitby: agreed]

Added lines 76-77:

[rwhitby: agreed]

Changed lines 80-82 from:

1) Run "ipkg update" on the NSLU2. This updates "ipkg" to the current version.

to:

1) Run "ipkg update" on the NSLU2. This updates the list of available "ipkg" packages.

[rwhitby: agreed]

Added line 90:

[rwhitby: agreed]

January 13, 2005, at 03:21 PM by uSURPER --
Added lines 5-67:

> 1) It is strongly recommended that you test telnet Redboot access

   first.  See http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot

Why is this? An explanation of _why_ it's strongly recommended might be nice *especially* since it's pretty difficult to do in a "normal" environment (relies on timing, all the scripts are Linux based and most people use Windows, etc).

> 4) Verify your NSLU2 is working normally again at this point - in the

   web interface.  In  particular, you should ensure that all your disks are
   still recognized as they were before you updated the firmware.

... "updated the firmare and that any shares and data you previously had stored are available. If not, do not continue."

> 5) Shutdown the NSLU2 and unplug *ALL* attached disks.

	- You must NOT have any disk plugged into the NSLU2 when you reboot
          to perform the next part of installation - the "Unslinging".

This should be moved to point 1 of the uNSLUng portion - if you aren't unslunging then you don't need to do this, you stop at point 4.

> permanently change a password. See the NSLU2 wiki for more details.

Which part of the wiki? Where? A hyperlink would be great here.

> 5) Reboot.

Move this to point 6 and add the following for point 5) 5) Create an unslung directory for storing any packages you may decide to download as follows: mkdir /share/hdd/conf/unslung && ln -s /share/hdd/conf/unslung /unslung

> And if you run out of room on the "conf" partition, you can always put symlinks across to the "data" partition too.

How, where? i.e. can we have an example like mkdir /share/hdd/data/unslung && mv /unslung/* /share/hdd/data/unslung && rm -rf /unslung && ln -s /share/hdd/data/unslung /unslung (or something better).

Or -- why not just do this in #5 above and avoid using /conf at all if it's going to potentially be a problem that users will see?

> efore the diversion script is called. This allows you to use the variables and functions defined by the factory script.

A list of the "factory" scripts that can be diverted would be useful... e.g. /unslung/rc.local (this does x)

        /rc.xinetd (this does y)

> 0) Note that you must have network connectivity to the package

Can we have the lists (throughout) starting at 1 please.

> 0) Note that you must have network connectivity to the package

   repository at http://ipkg.nslu2-linux.org before proceeding.
   You must also confirm that your DNS server address is set in the
   web interface, or the NSLU2 will not be able to find the site.

How about 0) You need to have network connectivity to the package repositry at http://ipky.nslu2-linux.org before proceeding. A simple way of testing this is to:

 ping ipkg.nslu2-linux.org. If this doesn't work please check your NSLU2 has the correct DNS setting in the web interface.

> 1) Run "ipkg update" on the NSLU2.

1) Run "ipkg update" on the NSLU2. This updates "ipkg" to the current version.

> 5) This simple diversion script will enable telnet on boot > > [ Store the following in /unslung/rc.xinetd ]

[ Save the following as a script called /unslung/rc.xinetd and reboot your NSLU2]

January 04, 2005, at 08:01 AM by rwhitby --
Changed line 3 from:

For nslu2-linux developer review: http://www.toddcomp.com/NSLU2/Unslung-3.17-README.txt.

to:

ByronT? reworded the README at http://www.toddcomp.com/NSLU2/Unslung-3.17-README.txt. This has been incorporated into the BK repo. Please use this as a starting point for any other suggested changes.

Deleted lines 4-10:
Notes: First edit; I have primarily focused on emphasizing steps/actions and differentiating them from notes accompanying those steps. In the interest of creating a README that is geared more toward a new user, I have changed some steps to explicity state the action needed to be taken. Example, in the existing README, "make sure you unplug all disks before the next step" was changed to read "Shutdown your NSLU2 and unplug *ALL* attached disks." I have already noticed several formatting and/or consistency issues in that uploaded version, and am working on my next revision of the README.

Please send any comments, suggestions to byrontodd at gmail dot com.

Thanking *all* the developers for their time and dedication to making a good product even better.

ByronT?

January 04, 2005, at 06:12 AM by ByronT --
Changed lines 1-11 from:

Please add suggested changes here. The changes only.

to:

Describe SuggestedChangesToTheReadme here.

For nslu2-linux developer review: http://www.toddcomp.com/NSLU2/Unslung-3.17-README.txt.

Notes: First edit; I have primarily focused on emphasizing steps/actions and differentiating them from notes accompanying those steps. In the interest of creating a README that is geared more toward a new user, I have changed some steps to explicity state the action needed to be taken. Example, in the existing README, "make sure you unplug all disks before the next step" was changed to read "Shutdown your NSLU2 and unplug *ALL* attached disks." I have already noticed several formatting and/or consistency issues in that uploaded version, and am working on my next revision of the README.

Please send any comments, suggestions to byrontodd at gmail dot com.

Thanking *all* the developers for their time and dedication to making a good product even better.

ByronT?

January 04, 2005, at 03:45 AM by dyoung --
Changed line 1 from:
to:

Please add suggested changes here. The changes only.

January 04, 2005, at 03:33 AM by dyoung --
Changed line 1 from:
to: