Open Stock Firmware LS-XHL - Revision history

Kenatonline: /* Important */

Kenatonline — Tue, 31 Jan 2012 12:41:52 GMT

Important

← Older revision		Revision as of 12:41, 31 January 2012
Line 10:		Line 10:
	* You have to get access to the LS via acp_commander in interactive mode.		* You have to get access to the LS via acp_commander in interactive mode.
	* You will have to use some Unix commands to copy files and to set file mode bits.		* You will have to use some Unix commands to copy files and to set file mode bits.
		+
		+	There is a guide for the VL which will work for the XHL as well.<br>
		+	http://buffalo.nas-central.org/wiki/Open_Stock_Firmware_LS-VL

	=Why a new page for the XHL?=		=Why a new page for the XHL?=

Kenatonline: /* How will it work? */

Kenatonline — Wed, 28 Dec 2011 08:23:03 GMT

How will it work?

← Older revision		Revision as of 08:23, 28 December 2011
Line 130:		Line 130:
	'''Update 16.03.2010''': Updated open_firmware.sh to handle RAID systems in emergency.sh also.		'''Update 16.03.2010''': Updated open_firmware.sh to handle RAID systems in emergency.sh also.

-	For emergency purposes, I added the call to a script into a script started at bootup of the box. It is called in step 4 of the rcS via a standard Buffalo mechanism (/etc/~~init~~.d/extensions.d). The advantage of this is, that you can put a script onto the "share" share and simply reboot the box to have the possibility to execute commands as the superuser.	+	For emergency purposes, I added the call to a script into a script started at bootup of the box. It is called in step 4 of the rcS via a standard Buffalo mechanism (/etc/rc.d/extensions.d). The advantage of this is, that you can put a script onto the "share" share and simply reboot the box to have the possibility to execute commands as the superuser.

	The script to place on the share "share" is named "emergency.sh".		The script to place on the share "share" is named "emergency.sh".

Noble: /* The step by step guide */

Noble — Tue, 26 Apr 2011 18:11:16 GMT

The step by step guide

← Older revision		Revision as of 18:11, 26 April 2011
Line 156:		Line 156:
	==The step by step guide==		==The step by step guide==

-	Download the firmware zip from Buffalo. Then determine the password which has to be used to unpack the hddrootfs.img.	+	Download the firmware zip from Buffalo. Then determine the password which has to be used to unpack the hddrootfs.img. A list of possible passwords can be found at [[Create_a_custom_firmware_image#Collected_passwords]].

	Edit open_firmware.sh and replace the value of the PASSWORD variable with the matching password. Take care to use a Unix-aware editor.		Edit open_firmware.sh and replace the value of the PASSWORD variable with the matching password. Take care to use a Unix-aware editor.

Kenatonline: /* How to convert the data partition from XFS to EXT3? */

Kenatonline — Sat, 05 Feb 2011 06:50:25 GMT

How to convert the data partition from XFS to EXT3?

← Older revision		Revision as of 06:50, 5 February 2011
Line 261:		Line 261:
	to:		to:
	USERLAND_FS=ext3		USERLAND_FS=ext3
		+	To prevent error messages when putting the settings back, also delete the line containing "NAS_FEATURE_VERSION".

	Now one can format the data partition (/dev/disk1_6 aka. /mnt/disk1), but do not forget to save the data before, because you will loose everything on this partition.		Now one can format the data partition (/dev/disk1_6 aka. /mnt/disk1), but do not forget to save the data before, because you will loose everything on this partition.

Soepy: Undo revision 29971 by Soepy (Talk)

Soepy — Wed, 25 Aug 2010 12:53:47 GMT

Undo revision 29971 by Soepy (Talk)

← Older revision		Revision as of 12:53, 25 August 2010
Line 60:		Line 60:
	Use the password:		Use the password:
	aAhvlM1Yp7_2VSm6BhgkmTOrCN1JyE0C5Q6cB3oBB		aAhvlM1Yp7_2VSm6BhgkmTOrCN1JyE0C5Q6cB3oBB
-	~~Version 1.34 uses the following password:~~
-	~~1NIf_2yUOlRDpYZUVNqboRpMBoZwT4PzoUvOPUp6l~~
	Now you can copy the extracted executables to your XHL share.		Now you can copy the extracted executables to your XHL share.

Soepy: /* How to get the executables from release 1.10 if you already upgraded to 1.20? */

Soepy — Wed, 25 Aug 2010 12:41:42 GMT

How to get the executables from release 1.10 if you already upgraded to 1.20?

← Older revision		Revision as of 12:41, 25 August 2010
Line 60:		Line 60:
	Use the password:		Use the password:
	aAhvlM1Yp7_2VSm6BhgkmTOrCN1JyE0C5Q6cB3oBB		aAhvlM1Yp7_2VSm6BhgkmTOrCN1JyE0C5Q6cB3oBB
		+	Version 1.34 uses the following password:
		+	1NIf_2yUOlRDpYZUVNqboRpMBoZwT4PzoUvOPUp6l
	Now you can copy the extracted executables to your XHL share.		Now you can copy the extracted executables to your XHL share.

Mattaw at 19:57, 17 July 2010

Mattaw — Sat, 17 Jul 2010 19:57:05 GMT

← Older revision		Revision as of 19:57, 17 July 2010
Line 148:		Line 148:
	==Bells and Whistles==		==Bells and Whistles==

-	'''Each''' .tar file and '''each''' .key file can get included into the patched firmware. Just put the files in the same directory as the firmware zip and the open_firmware.sh script.	+	'''Each''' .tar file and '''each''' .key file can get included into the patched firmware. Just put the files in the same directory as the firmware zip and the open_firmware.sh script. For root access in firmware 1.33 you must add at least one root key to get access (ssh-keygen as root and copy the .ssh/id_rsa.pub file to the script directory as id_rsa.pub.key).

	The *.tar can contain anything you like to have within the firmware. The file will be unpacked in the virtual root directory of the hddrootfs. So if you want to have an additional file ending in "/usr/sbin" of the firmware, you have to put it into "usr/sbin/" within the tar file.		The *.tar can contain anything you like to have within the firmware. The file will be unpacked in the virtual root directory of the hddrootfs. So if you want to have an additional file ending in "/usr/sbin" of the firmware, you have to put it into "usr/sbin/" within the tar file.

Kenatonline: /* How to get telnet working in 1.24 or any other LS-XHL or LS-CHLv2 version */

Kenatonline — Sat, 22 May 2010 10:39:13 GMT

How to get telnet working in 1.24 or any other LS-XHL or LS-CHLv2 version

← Older revision		Revision as of 10:39, 22 May 2010
Line 115:		Line 115:

	Due to the circumstance that buffalo changed a third time the way to "open" a firmware, I decided to make a guide which will help others to open ''any'' firmware version.		Due to the circumstance that buffalo changed a third time the way to "open" a firmware, I decided to make a guide which will help others to open ''any'' firmware version.
		+
		+	'''Update 22.05.2010''': I verified that the guide below works for 1.26 also. The Buffalo LS-XHL 1.26 firmware is a "multi-box" firmware. It covers the XHL, CHL, SL, WXL and WSXL in one firmware.

	==How will it work?==		==How will it work?==

Kenatonline: /* How will it work? */

Kenatonline — Tue, 16 Mar 2010 16:59:40 GMT

How will it work?

← Older revision		Revision as of 16:59, 16 March 2010
Line 137:		Line 137:

	One to enable the ssh daemon. Of course you can call this script as well on the box directly when logged in as superuser. http://downloads.buffalo.nas-central.org/Users/kenatonline/OpenFirmware/enablesshd.sh		One to enable the ssh daemon. Of course you can call this script as well on the box directly when logged in as superuser. http://downloads.buffalo.nas-central.org/Users/kenatonline/OpenFirmware/enablesshd.sh
		+
		+	'''Update 16.03.2010''': Updated enablessh.sh to handle RAID systems also.

	Just copy one of this scripts to the share "share" and rename them to "emergency.sh". Take care that you set the execution bit of the script for superuser at least!		Just copy one of this scripts to the share "share" and rename them to "emergency.sh". Take care that you set the execution bit of the script for superuser at least!

Kenatonline: /* How will it work? */

Kenatonline — Tue, 16 Mar 2010 16:00:07 GMT

How will it work?

← Older revision		Revision as of 16:00, 16 March 2010
Line 125:		Line 125:

	'''Update 15.03.2010''': Updated open_firmware.sh due to problem to switch to superuser (su returned permission denied).		'''Update 15.03.2010''': Updated open_firmware.sh due to problem to switch to superuser (su returned permission denied).
		+
		+	'''Update 16.03.2010''': Updated open_firmware.sh to handle RAID systems in emergency.sh also.

	For emergency purposes, I added the call to a script into a script started at bootup of the box. It is called in step 4 of the rcS via a standard Buffalo mechanism (/etc/init.d/extensions.d). The advantage of this is, that you can put a script onto the "share" share and simply reboot the box to have the possibility to execute commands as the superuser.		For emergency purposes, I added the call to a script into a script started at bootup of the box. It is called in step 4 of the rcS via a standard Buffalo mechanism (/etc/init.d/extensions.d). The advantage of this is, that you can put a script onto the "share" share and simply reboot the box to have the possibility to execute commands as the superuser.