GenLink for ARM9 - Revision history

Speeddymon: /* Install Modified Initrd/Kernel */

Speeddymon — Tue, 22 Mar 2011 20:29:08 GMT

Install Modified Initrd/Kernel

← Older revision		Revision as of 20:29, 22 March 2011
Line 36:		Line 36:
	=== Install Modified Initrd/Kernel ===		=== Install Modified Initrd/Kernel ===

-	To boot another firmware, you need a modified Initrd. One initrd that will work is [http://forum.nas-central.org/viewtopic.php?f=19&t=1771 lb_worm's 'Modified Initrd']. Alternatively, you may install the [http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/Genlink/boot(sda1)/GenLink-bootSDA1_arm9-20080910.tar.bz2 Genlink tarball], which you only have to unpack over '''/dev/sda1''' in order to have a custom initrd, a modified stock kernel with NFS and usb-printer support pre-configured to boot an alternative distribution. '''''Note:''''' Unpacking the Genlink tarball will overwrite your existing '''initrd.buffalo''' (initrd) and '''uImage.buffalo''' (kernel) files. It is ''highly'' recommended that you save backups of the stock initrd and kernel in case the modified initrd or GenLink kernel fail to boot.	+	To boot another firmware, you need a modified Initrd. One initrd that will work is [http://forum.buffalo.nas-central.org/viewtopic.php?f=19&t=1771 lb_worm's 'Modified Initrd']. Alternatively, you may install the [http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/Genlink/boot(sda1)/GenLink-bootSDA1_arm9-20080910.tar.bz2 Genlink tarball], which you only have to unpack over '''/dev/sda1''' in order to have a custom initrd, a modified stock kernel with NFS and usb-printer support pre-configured to boot an alternative distribution. '''''Note:''''' Unpacking the Genlink tarball will overwrite your existing '''initrd.buffalo''' (initrd) and '''uImage.buffalo''' (kernel) files. It is ''highly'' recommended that you save backups of the stock initrd and kernel in case the modified initrd or GenLink kernel fail to boot.

	Of course, if your box was already setup to boot an alternative firmware, you won't need to replace the stock kernel and initrd. This is most likely the case if the contents of your '''/dev/sda1''' looks similar to:		Of course, if your box was already setup to boot an alternative firmware, you won't need to replace the stock kernel and initrd. This is most likely the case if the contents of your '''/dev/sda1''' looks similar to:

Zoolook: adapted portage BINHOST wiki link

Zoolook — Tue, 11 Jan 2011 13:54:59 GMT

adapted portage BINHOST wiki link

← Older revision		Revision as of 13:54, 11 January 2011
Line 306:		Line 306:
	amule (daemon & webui only)		amule (daemon & webui only)
	sys-apps/ksysguard (not kde-base/ksysguard, see [[KDE_ksysguardd_on_the_Linkstation\| KDE ksysguardd daemon only on the Linkstation]])		sys-apps/ksysguard (not kde-base/ksysguard, see [[KDE_ksysguardd_on_the_Linkstation\| KDE ksysguardd daemon only on the Linkstation]])
-	and the list may continue, please check the contents of the [http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/Genlink/Binaries/ remote binpkg directory] (''BINHOST'', in terms of [http://gentoo-wiki.com/TIP_Using_PORTAGE_BINHOST Using PORTAGE BINHOST])	+	and the list may continue, please check the contents of the [http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/Genlink/Binaries/ remote binpkg directory] (''BINHOST'', in terms of [http://en.gentoo-wiki.com/wiki/TIP_Using_PORTAGE_BINHOST Using PORTAGE BINHOST])

	=== Monitoring Hard Drive Temperature ===		=== Monitoring Hard Drive Temperature ===

Smiley: -d marvell for monitoring hdd temperature

Smiley — Thu, 13 Aug 2009 22:10:52 GMT

-d marvell for monitoring hdd temperature

← Older revision		Revision as of 22:10, 13 August 2009
Line 307:		Line 307:
	sys-apps/ksysguard (not kde-base/ksysguard, see [[KDE_ksysguardd_on_the_Linkstation\| KDE ksysguardd daemon only on the Linkstation]])		sys-apps/ksysguard (not kde-base/ksysguard, see [[KDE_ksysguardd_on_the_Linkstation\| KDE ksysguardd daemon only on the Linkstation]])
	and the list may continue, please check the contents of the [http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/Genlink/Binaries/ remote binpkg directory] (''BINHOST'', in terms of [http://gentoo-wiki.com/TIP_Using_PORTAGE_BINHOST Using PORTAGE BINHOST])		and the list may continue, please check the contents of the [http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/Genlink/Binaries/ remote binpkg directory] (''BINHOST'', in terms of [http://gentoo-wiki.com/TIP_Using_PORTAGE_BINHOST Using PORTAGE BINHOST])
		+
		+	=== Monitoring Hard Drive Temperature ===
		+
		+	If your LS-GL/LS-CL contains a SATA hard drive that supports [[S.M.A.R.T. hard drive monitoring\| S.M.A.R.T]], you may want to emerge sys-apps/smartmontools. '''Note:''' in order for '''smartctl''' to recognize a drive attached to the Marvell SATA controller in NAS, you '''need''' to pass it the '''-d marvell''' option. For example, if you want to see the SMART attributes and values for /dev/sda, you would run:
		+	smartctl -a -d marvell /dev/sda
		+	One (rather important) SMART attribute you may want to keep an eye on is the one for hard drive temperature. On many drives, the value of attribute 194 is the temperature of the drive in Celsius degrees. If you prefer Fahrenheit, you can convert to Fahrenheit degrees using the formula: '''F = (C * 9)/5 + 32'''.

	=== Important Security Note for NFS Users ===		=== Important Security Note for NFS Users ===

Smiley: warning about insecure /etc/exports

Smiley — Wed, 12 Aug 2009 13:38:34 GMT

warning about insecure /etc/exports

← Older revision		Revision as of 13:38, 12 August 2009
Line 307:		Line 307:
	sys-apps/ksysguard (not kde-base/ksysguard, see [[KDE_ksysguardd_on_the_Linkstation\| KDE ksysguardd daemon only on the Linkstation]])		sys-apps/ksysguard (not kde-base/ksysguard, see [[KDE_ksysguardd_on_the_Linkstation\| KDE ksysguardd daemon only on the Linkstation]])
	and the list may continue, please check the contents of the [http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/Genlink/Binaries/ remote binpkg directory] (''BINHOST'', in terms of [http://gentoo-wiki.com/TIP_Using_PORTAGE_BINHOST Using PORTAGE BINHOST])		and the list may continue, please check the contents of the [http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/Genlink/Binaries/ remote binpkg directory] (''BINHOST'', in terms of [http://gentoo-wiki.com/TIP_Using_PORTAGE_BINHOST Using PORTAGE BINHOST])
		+
		+	=== Important Security Note for NFS Users ===
		+
		+	The [http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/Genlink/Rootfs/GenLink-stage3.1_arm9-1.1_rc3-20080923.tar.bz2 the stage 3 tarball from above] contains an '''/etc/exports''' file with insecure defaults. If you're going to merge net-fs/nfs-utils, '''make sure''' to delete, edit, or otherwise fix '''/etc/exports''' before you start your NFS server.

	=== Create whatis Database ===		=== Create whatis Database ===

Smiley: typo, elaboration

Smiley — Tue, 11 Aug 2009 20:18:35 GMT

typo, elaboration

← Older revision		Revision as of 20:18, 11 August 2009
Line 308:		Line 308:
	and the list may continue, please check the contents of the [http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/Genlink/Binaries/ remote binpkg directory] (''BINHOST'', in terms of [http://gentoo-wiki.com/TIP_Using_PORTAGE_BINHOST Using PORTAGE BINHOST])		and the list may continue, please check the contents of the [http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/Genlink/Binaries/ remote binpkg directory] (''BINHOST'', in terms of [http://gentoo-wiki.com/TIP_Using_PORTAGE_BINHOST Using PORTAGE BINHOST])

-	=== Create whatis ~~database~~ ===	+	=== Create whatis Database ===

-	The '''whatis''' and '''apropos''' commands provide a useful, searchable index to the pages on your system. However, to use them, you must first generate an index of the man pages on your system:	+	The '''whatis''' and '''apropos''' commands provide a useful, searchable index to the '''man''' pages on your system. However, to use them, you must first generate an index of the man pages on your system:
	makewhatis -w		makewhatis -w
		+	Now, typing '''whatis ''keyword''''' or '''apropos ''keyword''''' should return a list of matching man pages.

	=== Start & configure automatic start for cron and logger ===		=== Start & configure automatic start for cron and logger ===

Smiley: seed whatis database with man pages

Smiley — Tue, 11 Aug 2009 20:16:36 GMT

seed whatis database with man pages

← Older revision		Revision as of 20:16, 11 August 2009
Line 307:		Line 307:
	sys-apps/ksysguard (not kde-base/ksysguard, see [[KDE_ksysguardd_on_the_Linkstation\| KDE ksysguardd daemon only on the Linkstation]])		sys-apps/ksysguard (not kde-base/ksysguard, see [[KDE_ksysguardd_on_the_Linkstation\| KDE ksysguardd daemon only on the Linkstation]])
	and the list may continue, please check the contents of the [http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/Genlink/Binaries/ remote binpkg directory] (''BINHOST'', in terms of [http://gentoo-wiki.com/TIP_Using_PORTAGE_BINHOST Using PORTAGE BINHOST])		and the list may continue, please check the contents of the [http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/Genlink/Binaries/ remote binpkg directory] (''BINHOST'', in terms of [http://gentoo-wiki.com/TIP_Using_PORTAGE_BINHOST Using PORTAGE BINHOST])
		+
		+	=== Create whatis database ===
		+
		+	The '''whatis''' and '''apropos''' commands provide a useful, searchable index to the pages on your system. However, to use them, you must first generate an index of the man pages on your system:
		+	makewhatis -w

	=== Start & configure automatic start for cron and logger ===		=== Start & configure automatic start for cron and logger ===

Smiley: replace estimated compile time with actual observed compile time

Smiley — Tue, 11 Aug 2009 19:44:18 GMT

replace estimated compile time with actual observed compile time

← Older revision		Revision as of 19:44, 11 August 2009
Line 203:		Line 203:
	emerge --getbinpkgonly --usepkgonly --update system		emerge --getbinpkgonly --usepkgonly --update system

-	If you're lucky enough to be able to do a binary-only install, this should take maybe 5 to 10 minutes. If you're using a combination of prebuilt and source packages, it will take ~~close to 9~~ hours. If you're building from source only, it will take even longer. Go play with the kids. Say hi to your wife. Go for a bicycle ride.	+	If you're lucky enough to be able to do a binary-only install, this should take maybe 5 to 10 minutes. If you're using a combination of prebuilt and source packages, it will take 5 or 6 hours. If you're building from source only, it will take even longer. Go play with the kids. Say hi to your wife. Go for a bicycle ride.

	After merging the system packages, '''''timezone-data''''' will have been installed. Now, you can set your timezone by		After merging the system packages, '''''timezone-data''''' will have been installed. Now, you can set your timezone by

Smiley: mask gcc-2.4.2-r1

Smiley — Tue, 11 Aug 2009 14:10:03 GMT

mask gcc-2.4.2-r1

← Older revision		Revision as of 14:10, 11 August 2009
Line 188:		Line 188:
	If you're using the [http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/Genlink/Rootfs/GenLink-stage3.1_arm9-1.1_rc3-20080923.tar.bz2\|20080923 stage 3 tarball] listed above, you'll have to '''''downgrade''''' portage to version 2.1.6.13 before you'll be able to emerge updated packages. The version of portage in the tarball (version 2.2_pre-something) doesn't support EAPI 2, but version 2.1.6.13 does. As many of the packages in the current portage tree are only offered under EAPI 2, you first need to emerge portage 2.1.6.13 from source. Fortunately, this is quick and easy:		If you're using the [http://buffalo.nas-central.org/download/LSPro_ARM9/Distributions/Genlink/Rootfs/GenLink-stage3.1_arm9-1.1_rc3-20080923.tar.bz2\|20080923 stage 3 tarball] listed above, you'll have to '''''downgrade''''' portage to version 2.1.6.13 before you'll be able to emerge updated packages. The version of portage in the tarball (version 2.2_pre-something) doesn't support EAPI 2, but version 2.1.6.13 does. As many of the packages in the current portage tree are only offered under EAPI 2, you first need to emerge portage 2.1.6.13 from source. Fortunately, this is quick and easy:
	emerge --oneshot portage		emerge --oneshot portage
-	Due to a problem with the way portage 2.1.6.13 handles dependencies, additional workarounds may be necessary. For example, I had to mask sys-fs/e2fsprogs-1.41.8:	+	Due to a problem with the way portage 2.1.6.13 handles dependencies, additional workarounds may be necessary. For example, I had to mask sys-fs/e2fsprogs-1.41.8 (which depends on a masked package) and sys-devel/gcc-4.2.4-r1 (which segfaults during compilation):
	echo =sys-fs/e2fsprogs-1.41.8 >> /etc/portage/package.mask/common		echo =sys-fs/e2fsprogs-1.41.8 >> /etc/portage/package.mask/common
		+	echo =sys-devel/gcc-4.2.4-r1 >> /etc/portage/package.mask/common
	Check the output from '''emerge''' to see if it complains about anything else in the portage tree. (It likes to do that.) While this step may require some patience (and coffee), resolving these dependencies generally isn't too hard.		Check the output from '''emerge''' to see if it complains about anything else in the portage tree. (It likes to do that.) While this step may require some patience (and coffee), resolving these dependencies generally isn't too hard.

Smiley: check date/time after reboot, too

Smiley — Tue, 11 Aug 2009 14:02:30 GMT

check date/time after reboot, too

← Older revision		Revision as of 14:02, 11 August 2009
Line 162:		Line 162:
	<br>		<br>

-	=== ~~Set Root Password~~ ===	+	=== Confirm System Date/Time ===
		+	The ''first thing'' you should do after logging into GenLink is confirm that, after rebooting, the system still has the correct date and time, as described above. If the time or date shown is incorrect, set it to the current date and time.

-	The ''~~first~~ thing'' you should do after logging into GenLink is set a password for root:	+	=== Set Root Password ===
		+	The ''second thing'' you should do after logging into GenLink is set a password for root:
	passwd		passwd
	As always, make sure to use a password that can be remembered reliably, but is hard to guess.		As always, make sure to use a password that can be remembered reliably, but is hard to guess.

Smiley: setting system date

Smiley — Tue, 11 Aug 2009 13:57:37 GMT

setting system date

← Older revision		Revision as of 13:57, 11 August 2009
Line 26:		Line 26:
	java -jar acp_commander.jar -t <linkstation-ip> -o		java -jar acp_commander.jar -t <linkstation-ip> -o

		+	=== Correcting System Date/Time ===
		+	Before installing any files, it is a good idea to make sure that the system date and time are correct. If you don't do this, the files you install will be dated in the past or future, which can cause confusion later on. To check the system date and time, run:
		+	date
		+	If the date or time is incorrect, you can set the correct time with a command like:
		+	date -s "Aug 11 16:12:34 2009"
		+	Then, (try to) synchronize the hardware clock with the newly set system clock:
		+	hwclock --systohc

	=== Install Modified Initrd/Kernel ===		=== Install Modified Initrd/Kernel ===