Freeing up space on hda1 - Revision history

Ramuk: /* FreeLink */

Ramuk — Tue, 31 Oct 2006 13:25:01 GMT

FreeLink

← Older revision		Revision as of 13:25, 31 October 2006
Line 80:		Line 80:

	You can move the <tt>/usr</tt> with the following commands:		You can move the <tt>/usr</tt> with the following commands:
-	cp -Rdp /usr ~~/mnt~~	+	DIR="$(mount \| grep hda3 \| awk '{print $3}')"
		+	cp -Rdp /usr ${DIR}
	rm -R /usr		rm -R /usr
-	ln -s ~~/mnt~~/usr /usr	+	ln -s ${DIR}/usr /usr

	=== /var ===		=== /var ===

84.44.133.54: /* Background */

84.44.133.54 — Tue, 31 Oct 2006 09:38:35 GMT

Background

← Older revision		Revision as of 09:38, 31 October 2006
Line 10:		Line 10:
	[[Upgrade (or replace) the existing LinkStation hard drive]]}}		[[Upgrade (or replace) the existing LinkStation hard drive]]}}
	If you are running out of hard drive space on '''<tt>hda1</tt>''' (the location of the OS, and the default location of installed programs), you can free up space by moving some of the files to '''<tt>hda3</tt>''' (the large partition containing the network shares). You can then create symbolic links in the original locations, and should in that way be able to access your files as if nothing happened (for the most part). You could well run into problems if you do this with '''[[OpenLink]]'''. There are known issues related to how '''[[w:BusyBox\|BusyBox]]''' uses symbolic links, and other issues might arise. Some issues are reported below. ''Proceed at your own risk.''		If you are running out of hard drive space on '''<tt>hda1</tt>''' (the location of the OS, and the default location of installed programs), you can free up space by moving some of the files to '''<tt>hda3</tt>''' (the large partition containing the network shares). You can then create symbolic links in the original locations, and should in that way be able to access your files as if nothing happened (for the most part). You could well run into problems if you do this with '''[[OpenLink]]'''. There are known issues related to how '''[[w:BusyBox\|BusyBox]]''' uses symbolic links, and other issues might arise. Some issues are reported below. ''Proceed at your own risk.''
-
-	Note that <tt>/dev/hda3</tt> is mounted on either <tt>/mnt</tt> or <tt>/mnt/hda</tt>, depending on the type of LinkStation you have (the instructions below refer to the former. If <tt>/mnt/hda</tt> exists on your LinkStation, you will need to modify the commands accordingly.

	==OpenLink==		==OpenLink==

84.44.133.54: /* /home */

84.44.133.54 — Tue, 31 Oct 2006 09:37:20 GMT

/home

← Older revision		Revision as of 09:37, 31 October 2006
Line 73:		Line 73:
	=== /home ===		=== /home ===
	Moving the <tt>/home</tt> directory should be safe, but it will not save you much space unless you are going to store a lot of data in the home directory of users. This can be done as follows:		Moving the <tt>/home</tt> directory should be safe, but it will not save you much space unless you are going to store a lot of data in the home directory of users. This can be done as follows:
-	cp -Rdp /home ~~/mnt~~	+	DIR="$(mount \| grep hda3 \| awk '{print $3}')"
		+	cp -Rdp /home ${DIR}
	rm -R /home		rm -R /home
-	ln -s ~~/mnt~~/home /home	+	ln -s ${DIR}/home /home
-		+

	=== /usr ===		=== /usr ===

84.44.133.54: /* Alternative method */

84.44.133.54 — Tue, 31 Oct 2006 09:36:39 GMT

Alternative method

← Older revision		Revision as of 09:36, 31 October 2006
Line 57:		Line 57:

	DIR="$(mount \| grep hda3 \| awk '{print $3}')"		DIR="$(mount \| grep hda3 \| awk '{print $3}')"
-	ln -s /bin ~~${DIR}~~/moved_folder	+	ln -s /bin /mnt/hda/moved_folder
-	ln -s /~~dev ${DIR}~~/moved_folder	+	ln -s /mnt/hda/moved_folder
-	ln -s /etc ~~${DIR}~~/moved_folder	+	ln -s /etc /mnt/hda/moved_folder
-	ln -s /lib ~~${DIR}~~/moved_folder	+	ln -s /lib /mnt/hda/moved_folder
-	ln -s /lost+found ~~${DIR}~~/moved_folder	+	ln -s /lost+found /mnt/hda/moved_folder
-	ln -s /mnt ~~${DIR}~~/moved_folder	+	ln -s /mnt /mnt/hda/moved_folder
-	ln -s /proc ~~${DIR}~~/moved_folder	+	ln -s /proc /mnt/hda/moved_folder
-	ln -s /root ~~${DIR}~~/moved_folder	+	ln -s /root /mnt/hda/moved_folder
-	ln -s /sbin ~~${DIR}~~/moved_folder	+	ln -s /sbin /mnt/hda/moved_folder
-	ln -s /sys ~~${DIR}~~/moved_folder	+	ln -s /sys /mnt/hda/moved_folder
-	ln -s /tmp ~~${DIR}~~/moved_folder	+	ln -s /tmp /mnt/hda/moved_folder
-	ln -s /www ~~${DIR}~~/moved_folder	+	ln -s /www /mnt/hda/moved_folder

	==FreeLink==		==FreeLink==

84.44.133.54: /* /var */

84.44.133.54 — Tue, 31 Oct 2006 09:35:07 GMT

/var

← Older revision		Revision as of 09:35, 31 October 2006
Line 92:		Line 92:

	If you choose to do so, these are the commands needed to move <tt>/var</tt>:		If you choose to do so, these are the commands needed to move <tt>/var</tt>:
-	cp -Rdp /var ~~/mnt~~	+	DIR="$(mount \| grep hda3 \| awk '{print $3}')"
		+	cp -Rdp /var ${DIR}
	rm -R /var		rm -R /var
-	ln -s ~~/mnt~~/var /var	+	ln -s ${DIR}/var /var

	You could also choose to move only <tt>/var/lib</tt> and <tt>/var/cache</tt>. You would of course need to modify the commands accordingly.		You could also choose to move only <tt>/var/lib</tt> and <tt>/var/cache</tt>. You would of course need to modify the commands accordingly.

84.44.133.54: /* Alternative method */

84.44.133.54 — Tue, 31 Oct 2006 09:34:00 GMT

Alternative method

← Older revision		Revision as of 09:34, 31 October 2006
Line 56:		Line 56:
	If you follow the FAQ to move /usr to say, <tt>/mnt/hda/moved_folder/usr</tt> and symbolic-link it back, some relative links won't work. For example, <tt>/usr/bin/wget</tt> has the symbolic link <tt>../../bin/busybox</tt>, and that would get resolved to <tt>/mnt/hda/moved_folder/bin/busybox</tt>, which does not exist. Therefore, you can link all unmoved directory under root back to this <tt>/mnt/hda/moved_folder</tt>:		If you follow the FAQ to move /usr to say, <tt>/mnt/hda/moved_folder/usr</tt> and symbolic-link it back, some relative links won't work. For example, <tt>/usr/bin/wget</tt> has the symbolic link <tt>../../bin/busybox</tt>, and that would get resolved to <tt>/mnt/hda/moved_folder/bin/busybox</tt>, which does not exist. Therefore, you can link all unmoved directory under root back to this <tt>/mnt/hda/moved_folder</tt>:

-	ln -s /bin ~~/mnt/hda~~/moved_folder	+	DIR="$(mount \| grep hda3 \| awk '{print $3}')"
-	ln -s /dev ~~/mnt/hda~~/moved_folder	+	ln -s /bin ${DIR}/moved_folder
-	ln -s /etc ~~/mnt/hda~~/moved_folder	+	ln -s /dev ${DIR}/moved_folder
-	ln -s /lib ~~/mnt/hda~~/moved_folder	+	ln -s /etc ${DIR}/moved_folder
-	ln -s /lost+found ~~/mnt/hda~~/moved_folder	+	ln -s /lib ${DIR}/moved_folder
-	ln -s /mnt ~~/mnt/hda~~/moved_folder	+	ln -s /lost+found ${DIR}/moved_folder
-	ln -s /proc ~~/mnt/hda~~/moved_folder	+	ln -s /mnt ${DIR}/moved_folder
-	ln -s /root ~~/mnt/hda~~/moved_folder	+	ln -s /proc ${DIR}/moved_folder
-	ln -s /sbin ~~/mnt/hda~~/moved_folder	+	ln -s /root ${DIR}/moved_folder
-	ln -s /sys ~~/mnt/hda~~/moved_folder	+	ln -s /sbin ${DIR}/moved_folder
-	ln -s /tmp ~~/mnt/hda~~/moved_folder	+	ln -s /sys ${DIR}/moved_folder
-	ln -s /www ~~/mnt/hda~~/moved_folder	+	ln -s /tmp ${DIR}/moved_folder
		+	ln -s /www ${DIR}/moved_folder

	==FreeLink==		==FreeLink==

84.44.133.54: /* /home */

84.44.133.54 — Tue, 31 Oct 2006 09:32:40 GMT

/home

← Older revision		Revision as of 09:32, 31 October 2006
Line 16:		Line 16:
	=== /home ===		=== /home ===
	Moving the <tt>/home</tt> directory should be safe, but it will not save you much space unless you are going to store a lot of data in the home directory of users. This can be done as follows:		Moving the <tt>/home</tt> directory should be safe, but it will not save you much space unless you are going to store a lot of data in the home directory of users. This can be done as follows:
-	DIR="/$(mount \| awk '{print $3}')"	+	DIR="$(mount \| grep hda3 \| awk '{print $3}')"
-	cp -Rdp /home ~~/mnt~~${DIR}	+	cp -Rdp /home ${DIR}
	rm -R /home		rm -R /home
-	ln -s ~~/mnt~~${DIR}/home /home	+	ln -s ${DIR}/home /home

	=== /usr/local ===		=== /usr/local ===

84.44.133.54: /* /usr/local */

84.44.133.54 — Tue, 31 Oct 2006 09:30:42 GMT

/usr/local

← Older revision		Revision as of 09:30, 31 October 2006
Line 23:		Line 23:
	=== /usr/local ===		=== /usr/local ===
	Moving the <tt>/usr/local</tt> directory should also be safe. This directory contains additionally installed software, and moving it should not disrupt any mission critical applications. This can be done as follows:		Moving the <tt>/usr/local</tt> directory should also be safe. This directory contains additionally installed software, and moving it should not disrupt any mission critical applications. This can be done as follows:
-	mkdir ~~/mnt~~/usr	+	DIR="$(mount \| grep hda3 \| awk '{print $3}')"
-	cp -Rdp /usr/local ~~/mnt~~/usr	+	mkdir ${DIR}/usr
		+	cp -Rdp /usr/local ${DIR}/usr
	rm -R /usr/local		rm -R /usr/local
-	ln -s ~~/mnt~~/usr/local /usr/local	+	ln -s ${DIR}/usr/local /usr/local

	=== /usr - Fixing the busybox symlinks ===		=== /usr - Fixing the busybox symlinks ===

84.44.133.54: /* /home */

84.44.133.54 — Tue, 31 Oct 2006 09:28:10 GMT

/home

← Older revision		Revision as of 09:28, 31 October 2006
Line 16:		Line 16:
	=== /home ===		=== /home ===
	Moving the <tt>/home</tt> directory should be safe, but it will not save you much space unless you are going to store a lot of data in the home directory of users. This can be done as follows:		Moving the <tt>/home</tt> directory should be safe, but it will not save you much space unless you are going to store a lot of data in the home directory of users. This can be done as follows:
-	cp -Rdp /home /mnt	+	DIR="/$(mount \| awk '{print $3}')"
		+	cp -Rdp /home /mnt${DIR}
	rm -R /home		rm -R /home
-	ln -s /mnt/home /home	+	ln -s /mnt${DIR}/home /home

	=== /usr/local ===		=== /usr/local ===

84.44.133.54: /* Background */

84.44.133.54 — Tue, 31 Oct 2006 09:25:18 GMT

Background

← Older revision		Revision as of 09:25, 31 October 2006
Line 11:		Line 11:
	If you are running out of hard drive space on '''<tt>hda1</tt>''' (the location of the OS, and the default location of installed programs), you can free up space by moving some of the files to '''<tt>hda3</tt>''' (the large partition containing the network shares). You can then create symbolic links in the original locations, and should in that way be able to access your files as if nothing happened (for the most part). You could well run into problems if you do this with '''[[OpenLink]]'''. There are known issues related to how '''[[w:BusyBox\|BusyBox]]''' uses symbolic links, and other issues might arise. Some issues are reported below. ''Proceed at your own risk.''		If you are running out of hard drive space on '''<tt>hda1</tt>''' (the location of the OS, and the default location of installed programs), you can free up space by moving some of the files to '''<tt>hda3</tt>''' (the large partition containing the network shares). You can then create symbolic links in the original locations, and should in that way be able to access your files as if nothing happened (for the most part). You could well run into problems if you do this with '''[[OpenLink]]'''. There are known issues related to how '''[[w:BusyBox\|BusyBox]]''' uses symbolic links, and other issues might arise. Some issues are reported below. ''Proceed at your own risk.''

-	~~*~~Note that <tt>/dev/hda3</tt> is mounted on either <tt>/mnt</tt> or <tt>/mnt/hda</tt>, depending on the type of LinkStation you have (the instructions below refer to the former. If <tt>/mnt/hda</tt> exists on your LinkStation, you will need to modify the commands accordingly.~~*~~	+	Note that <tt>/dev/hda3</tt> is mounted on either <tt>/mnt</tt> or <tt>/mnt/hda</tt>, depending on the type of LinkStation you have (the instructions below refer to the former. If <tt>/mnt/hda</tt> exists on your LinkStation, you will need to modify the commands accordingly.

	==OpenLink==		==OpenLink==