Install Debian Lenny on Stock Kurobox - Revision history

Lsuser1985: Add category `Lenny`.

Lsuser1985 — Fri, 18 Jan 2013 15:55:00 GMT

Add category `Lenny`.

← Older revision		Revision as of 15:55, 18 January 2013
Line 245:		Line 245:

	Feedback and discussion is welcomed via [http://forum.buffalo.nas-central.org/viewtopic.php?f=41&t=22002 http://forum.buffalo.nas-central.org/viewtopic.php?f=41&t=22002]		Feedback and discussion is welcomed via [http://forum.buffalo.nas-central.org/viewtopic.php?f=41&t=22002 http://forum.buffalo.nas-central.org/viewtopic.php?f=41&t=22002]
		+
		+	[[Category:Debian]]
		+	[[Category:Lenny]]

Asc: /* Partition the Hard Drive */

Asc — Tue, 14 Dec 2010 23:57:55 GMT

Partition the Hard Drive

← Older revision		Revision as of 23:57, 14 December 2010
Line 60:		Line 60:
	/dev/hda1 Bootable Type 83(Linux) 2GB for Sarge		/dev/hda1 Bootable Type 83(Linux) 2GB for Sarge
	/dev/hda2 Type 82(LinuxSwap) 256MB		/dev/hda2 Type 82(LinuxSwap) 256MB
-	/dev/~~hda1~~ Type 83(Linux) 4GB for Lenny	+	/dev/hda3 Type 83(Linux) 4GB for Lenny
-	/dev/~~hda3~~ Type 83(Linux) the rest of the Disk	+	/dev/hda4 Type 83(Linux) the rest of the Disk

	* Clear existing partitions:		* Clear existing partitions:

Asc: /* Configure and Reboot */

Asc — Tue, 14 Dec 2010 23:40:00 GMT

Configure and Reboot

← Older revision		Revision as of 23:40, 14 December 2010
Line 141:		Line 141:
	** Lenny		** Lenny
	vi /mnt/hda3/etc/hostname		vi /mnt/hda3/etc/hostname
		+
		+	* Configure DNS servers:
		+	** Sarge
		+	vi /mnt/hda1/etc/resolv.conf
		+	** Lenny
		+	vi /mnt/hda3/etc/resolv.conf

	* Finally, to boot into Debian Lenny 5.05, type:		* Finally, to boot into Debian Lenny 5.05, type:

Nicholas.robinson: /* Introduction */

Nicholas.robinson — Thu, 07 Oct 2010 18:41:59 GMT

Introduction

← Older revision		Revision as of 18:41, 7 October 2010
Line 19:		Line 19:

	# Initial Configuration		# Initial Configuration
		+	# Optional Configuration
	# Install Services		# Install Services

Nicholas.robinson: /* Optional Configuration */

Nicholas.robinson — Tue, 28 Sep 2010 18:48:23 GMT

Optional Configuration

← Older revision		Revision as of 18:48, 28 September 2010
Line 188:		Line 188:
	To force the system to always boot Lenny with the updated kernel:		To force the system to always boot Lenny with the updated kernel:

-	# Boot into Sarge	+	* Boot into Sarge and login as root
-	# Create a rebooter script	+	* Create a rebooter script:
		+	nano /etc/init.d/kernel_check.sh
		+	* Add the following content ('''replacing 2.4.17_mvl21''' with '''your stock firmware revision''' ['''uname -r''']):
		+	#!/bin/sh
		+	# Check Kernel Version
		+	KERNEL=`uname -r`
		+	echo "Detected Kernel: $KERNEL"
		+	if [ $KERNEL = '2.4.17_mvl21' ]; then
		+	echo 'Rebooting...'
		+	/sbin/reboot
		+	fi
		+	* Save the script
		+	<ctrl>+o, <ctrl>+x
		+	* Make the script executable:
		+	chmod +x /etc/init.d/kernel_check.sh
		+	* Register an @reboot crontab process:
		+	crontab -e <enter>
		+	@reboot /bin/sh /etc/init.d/kernel_check.sh > /root/log.txt 2>&1
		+	<ctrl>+o, <ctr>+x

		+	Now, whenever the system boots into Sarge it will detect the stock firmware and force a reboot into Lenny with the updated firmware. This behavior will allow you to reboot the server remotely with confidence that it will return running Lenny. It also simplifies the boot procedure to a single button push.

		+	'''Note''': There are definitely much more elegant ways of achieving this behavior, this only serves as a simple example.

	==== Install Services ====		==== Install Services ====

Nicholas.robinson at 18:33, 28 September 2010

Nicholas.robinson — Tue, 28 Sep 2010 18:33:28 GMT

← Older revision		Revision as of 18:33, 28 September 2010
Line 181:		Line 181:
	* Upgrade installed packages:		* Upgrade installed packages:
	apt-get dist-upgrade		apt-get dist-upgrade
		+
		+	==== Optional Configuration ====
		+
		+	By default the dual-boot installation will cycle between Sarge with stock kernel and Lenny with updated kernel after each reboot. Whilst this provides a safety net in the event that the Lenny installation fails to boot (i.e. reboot in Sarge, mount the Lenny filesystem and fix the problem), this behavior may be undesirable if you operate always-on services purely within Lenny.
		+
		+	To force the system to always boot Lenny with the updated kernel:
		+
		+	# Boot into Sarge
		+	# Create a rebooter script
		+
		+

	==== Install Services ====		==== Install Services ====

Nicholas.robinson: /* Limitations */

Nicholas.robinson — Tue, 28 Sep 2010 18:18:11 GMT

Limitations

← Older revision		Revision as of 18:18, 28 September 2010
Line 190:		Line 190:

	Ideally the auxiliary Sarge installation should not be necessary, however much work is required to facilitate this. Please let me know if you have such a solution.		Ideally the auxiliary Sarge installation should not be necessary, however much work is required to facilitate this. Please let me know if you have such a solution.
-
-	~~In the meantime, the current limitations exist and require solutions:~~
-	~~# Shutdown does not work correctly: After issuing a ''shutdown now'' command the system does not halt. This should be simple to fix~~
-	~~# Reboot does not work correctly: After issuing a ''reboot'' command the system reboots in Sarge 3.1 running the stock 2.4.17 kernel.~~

	Please let me know or amend this article if you discover solutions or further limitations.		Please let me know or amend this article if you discover solutions or further limitations.

Nicholas.robinson: /* Change Log */

Nicholas.robinson — Tue, 28 Sep 2010 18:15:39 GMT

Change Log

← Older revision		Revision as of 18:15, 28 September 2010
Line 200:		Line 200:
	'''28/09/2010'''		'''28/09/2010'''

-	The shutdown and reboot limitations have now been resolved by means of a crontab @reboot script (detailed above). This script has not been incorporated into the repository images as it removes the built-in safety net that dual booting provides. (i.e. without the script if Lenny fails to boot you can reboot in Sarge mount the Lenny filesystem and fix the problem, with the script if Lenny fails to boot you will need to force EM mode or remove the hard drive to rectify).	+	The shutdown and reboot limitations have now been resolved by means of a crontab @reboot script (detailed above). This script has not been incorporated into the repository images as it removes the built-in safety net that dual booting provides. (i.e. without the script if Lenny fails to boot you can reboot in Sarge, mount the Lenny filesystem and fix the problem; with the script if Lenny fails to boot you will need to force EM mode or remove the hard drive to rectify the problem).

	'''23/07/2010'''		'''23/07/2010'''

Nicholas.robinson: /* Change Log */

Nicholas.robinson — Tue, 28 Sep 2010 18:14:40 GMT

Change Log

← Older revision		Revision as of 18:14, 28 September 2010
Line 198:		Line 198:

	== Change Log ==		== Change Log ==
		+	'''28/09/2010'''
		+
		+	The shutdown and reboot limitations have now been resolved by means of a crontab @reboot script (detailed above). This script has not been incorporated into the repository images as it removes the built-in safety net that dual booting provides. (i.e. without the script if Lenny fails to boot you can reboot in Sarge mount the Lenny filesystem and fix the problem, with the script if Lenny fails to boot you will need to force EM mode or remove the hard drive to rectify).

	'''23/07/2010'''		'''23/07/2010'''

Nicholas.robinson: /* Limitations */

Nicholas.robinson — Wed, 11 Aug 2010 18:27:44 GMT

Limitations

← Older revision		Revision as of 18:27, 11 August 2010
Line 193:		Line 193:
	In the meantime, the current limitations exist and require solutions:		In the meantime, the current limitations exist and require solutions:
	# Shutdown does not work correctly: After issuing a ''shutdown now'' command the system does not halt. This should be simple to fix		# Shutdown does not work correctly: After issuing a ''shutdown now'' command the system does not halt. This should be simple to fix
-	# Reboot does not work correctly: After issuing a ''reboot'' command the system reboots in Sarge 2.1 running the stock 2.4.17 kernel.	+	# Reboot does not work correctly: After issuing a ''reboot'' command the system reboots in Sarge 3.1 running the stock 2.4.17 kernel.

	Please let me know or amend this article if you discover solutions or further limitations.		Please let me know or amend this article if you discover solutions or further limitations.