NSLU2-Linux
view · edit · print · history

HowTo.IncreaseSpaceAvailableForPackages History

Hide minor edits - Show changes to markup

August 18, 2005, at 07:36 PM by repvik -- preformat link
Changed line 19 from:

One thing that had me going around in circles with successive reboots for hours with moving /opt onto the hard disk was that I had my SLUG in Maintenance Mode. Turns out that I had accidently re-booted it using http://slug_IP/Management/maintmode.cgi (or from the web page) early on in my hacking to getting 3.18(beta) working. In Maintenance mode the SLUG makes / (root) read-only from flash. Therefore, upon a reboot you lose the link onto the hard disk, no programs load, you have to re-download the programs that you wanted to run, etc., etc. So, after you have updated your firmware, make sure you take the SLUG out of Maintenance mode before you do any installs of extra programs.

to:

One thing that had me going around in circles with successive reboots for hours with moving /opt onto the hard disk was that I had my SLUG in Maintenance Mode. Turns out that I had accidently re-booted it using http://slug_IP/Management/maintmode.cgi (or from the web page) early on in my hacking to getting 3.18(beta) working. In Maintenance mode the SLUG makes / (root) read-only from flash. Therefore, upon a reboot you lose the link onto the hard disk, no programs load, you have to re-download the programs that you wanted to run, etc., etc. So, after you have updated your firmware, make sure you take the SLUG out of Maintenance mode before you do any installs of extra programs.

August 15, 2005, at 09:25 PM by blaster8 -- singover sounds nicer, but isn\'t the right name :)
Changed lines 1-2 from:

NOTE: If you are running Unslung 4.x or 5.x, the default location for packages is already in the data partition, and there is no need to do what is described below. If you are running a 3.x version and upgrade to 5.x, step (6) of the install README describes how to use the singover script to move your current packages to the new default location.

to:

NOTE: If you are running Unslung 4.x or 5.x, the default location for packages is already in the data partition, and there is no need to do what is described below. If you are running a 3.x version and upgrade to 5.x, step (6) of the install README describes how to use the slingover script to move your current packages to the new default location.

June 21, 2005, at 04:03 PM by JohnS -- Updated - does not apply to unslung 4.x or greater
Added lines 1-2:

NOTE: If you are running Unslung 4.x or 5.x, the default location for packages is already in the data partition, and there is no need to do what is described below. If you are running a 3.x version and upgrade to 5.x, step (6) of the install README describes how to use the singover script to move your current packages to the new default location.

May 06, 2005, at 01:10 AM by tman --
Changed lines 3-11 from:
 ls -l /opt   (make sure it's a symbolic link. If it isn't, stop and ask for help)
 rm /opt
 cp -rp /share/hdd/conf/opt /share/hdd/data
 ln -s /share/hdd/data/opt /opt

Thanks. Ok, ls -l /opt shows me that they are all real directories "d" in the 1st column. ls -l / also only has real dirs. That means my packages go on the flash disk at the moment, right? What do I do now? df tells me I have 500k free 5900K used on the flash. (running 3.17) Would it be possible just to copy /opt to data and then rm /opt and create a symlink?

to:
ls -l /opt (make sure it's a symbolic link. If it isn't, stop and ask for help)
rm /opt
cp -rp /share/hdd/conf/opt /share/hdd/data
ln -s /share/hdd/data/opt /opt

Thanks. Ok, ls -l /opt shows me that they are all real directories "d" in the 1st column. ls -l / also only has real dirs. That means my packages go on the flash disk at the moment, right? What do I do now? df tells me I have 500k free 5900K used on the flash. (running 3.17) Would it be possible just to copy /opt to data and then rm /opt and create a symlink?

Changed line 17 from:

One thing that had me going around in circles with successive reboots for hours with moving /opt onto the hard disk was that I had my SLUG in Maintenance Mode. Turns out that I had accidently re-booted it using http://<slug IP>/Management/maintmode.cgi (or from the web page) early on in my hacking to getting 3.18(beta) working. In Maintenance mode the SLUG makes / (root) read-only from flash. Therefore, upon a reboot you lose the link onto the hard disk, no programs load, you have to re-download the programs that you wanted to run, etc., etc. So, after you have updated your firmware, make sure you take the SLUG out of Maintenance mode before you do any installs of extra programs.

to:

One thing that had me going around in circles with successive reboots for hours with moving /opt onto the hard disk was that I had my SLUG in Maintenance Mode. Turns out that I had accidently re-booted it using http://slug_IP/Management/maintmode.cgi (or from the web page) early on in my hacking to getting 3.18(beta) working. In Maintenance mode the SLUG makes / (root) read-only from flash. Therefore, upon a reboot you lose the link onto the hard disk, no programs load, you have to re-download the programs that you wanted to run, etc., etc. So, after you have updated your firmware, make sure you take the SLUG out of Maintenance mode before you do any installs of extra programs.

April 10, 2005, at 08:22 AM by Ed Royston --
Changed lines 13-17 from:

mt-daapd will fail in default installation during reboot because it needs to open the songs database located in /opt/var/mt-daapd as read/write, moving the songs database or disabling the rc.quota will fix that.

to:

mt-daapd will fail in default installation during reboot because it needs to open the songs database located in /opt/var/mt-daapd as read/write, moving the songs database or disabling the rc.quota will fix that.

10th April 2005 - More of a tip if anything...

One thing that had me going around in circles with successive reboots for hours with moving /opt onto the hard disk was that I had my SLUG in Maintenance Mode. Turns out that I had accidently re-booted it using http://<slug IP>/Management/maintmode.cgi (or from the web page) early on in my hacking to getting 3.18(beta) working. In Maintenance mode the SLUG makes / (root) read-only from flash. Therefore, upon a reboot you lose the link onto the hard disk, no programs load, you have to re-download the programs that you wanted to run, etc., etc. So, after you have updated your firmware, make sure you take the SLUG out of Maintenance mode before you do any installs of extra programs.

February 09, 2005, at 12:37 PM by Shorty --
Changed lines 10-13 from:

Would it be possible just to copy /opt to data and then rm /opt and create a symlink?

to:

Would it be possible just to copy /opt to data and then rm /opt and create a symlink?

NOTE: The rc.quota will make the data partition read only while it is calculating the disk usage of each user (this is stock linksys functionality). So any scripts/programs started in the boot process that needs write access to /opt can fail. mt-daapd will fail in default installation during reboot because it needs to open the songs database located in /opt/var/mt-daapd as read/write, moving the songs database or disabling the rc.quota will fix that.

February 02, 2005, at 01:40 PM by Oli --
Changed lines 9-10 from:

ls -l / also only has real dirs. That means my packages go on the flash disk at the moment, right? What do I do now? df tells me I have 500k free 5900K used on the flash. (running 3.17)

to:

ls -l / also only has real dirs. That means my packages go on the flash disk at the moment, right? What do I do now? df tells me I have 500k free 5900K used on the flash. (running 3.17) Would it be possible just to copy /opt to data and then rm /opt and create a symlink?

February 02, 2005, at 01:30 PM by Oli --
Added lines 7-9:

Thanks. Ok, ls -l /opt shows me that they are all real directories "d" in the 1st column. ls -l / also only has real dirs. That means my packages go on the flash disk at the moment, right? What do I do now? df tells me I have 500k free 5900K used on the flash. (running 3.17)

February 02, 2005, at 09:02 AM by paulhar --
Changed line 3 from:
 ls -l /opt   (make sure it's a symbolic link)
to:
 ls -l /opt   (make sure it's a symbolic link. If it isn't, stop and ask for help)
February 02, 2005, at 05:36 AM by rwhitby --
Changed lines 3-6 from:

Big thanks to Rod Whitby.

Great, thats exactly my problem but since I am a linux newbe I am not exactly sure how to do that. I guess if I screw up nothing will work. So the two lines to copy and create the symlink would be great. Thanks.

to:
 ls -l /opt   (make sure it's a symbolic link)
 rm /opt
 cp -rp /share/hdd/conf/opt /share/hdd/data
 ln -s /share/hdd/data/opt /opt
February 02, 2005, at 02:22 AM by Oli --
Changed lines 3-6 from:

Big thanks to Rod Whitby.

to:

Big thanks to Rod Whitby.

Great, thats exactly my problem but since I am a linux newbe I am not exactly sure how to do that. I guess if I screw up nothing will work. So the two lines to copy and create the symlink would be great. Thanks.

December 30, 2004, at 12:09 AM by Lex Delani --
Changed lines 1-3 from:
to:

Normally, the /opt where packages are normally installed, is symlinked into the /conf partition of the harddisk. This /conf part is usually small. One way to deal with the space problem is to copy the contents of /opt to a subdir of the data partition, then change the symlink to there, and presto! you can use as much space of your HD for packages as you like.

Big thanks to Rod Whitby.

view · edit · print · history · Last edited by repvik.
Based on work by blaster8, JohnS, tman, Ed Royston, Shorty, Oli, paulhar, and rwhitby.
Originally by Lex Delani.
Page last modified on August 18, 2005, at 07:36 PM