Talk:FreeLink for the LinkStation PRO/LIVE - Revision history

PurgedReality at 17:50, 10 August 2010

PurgedReality — Tue, 10 Aug 2010 17:50:03 GMT

← Older revision		Revision as of 17:50, 10 August 2010
Line 6:		Line 6:

	This should enable proper fetching of packages and allow 'apt-get update' or rather 'aptitude update' to successfully complete		This should enable proper fetching of packages and allow 'apt-get update' or rather 'aptitude update' to successfully complete
-	and packages will install.	+	and packages will install. [[User:PurgedReality\|PurgedReality]] 17:50, 10 August 2010 (UTC)

	== Root Permission Bug ==		== Root Permission Bug ==

PurgedReality at 17:48, 10 August 2010

PurgedReality — Tue, 10 Aug 2010 17:48:49 GMT

← Older revision		Revision as of 17:48, 10 August 2010
Line 1:		Line 1:
		+	== Etch Repository Moved from Official Server to Archive Server. ==
		+	On May 22nd, 2010 the Debian Package Repository Maintainers moved the Etch Package Tree to the Archive Server. [http://www.debian.org/News/2010/20100522 News Article Here.] This is a showstopper for those new to linux/debian/apt as their sources are now invalid. 'apt-get update' will now continuously 404 and give 'No such file or directory' errors. Users will
		+	need to edit /etc/apt/sources.list and alter the deb source to...
		+
		+	<nowiki>deb http://archive.debian.org/debian/ etch main non-free contrib</nowiki>
		+
		+	This should enable proper fetching of packages and allow 'apt-get update' or rather 'aptitude update' to successfully complete
		+	and packages will install.
		+
		+	== Root Permission Bug ==
	In FreeLink_arm9-1.0rev2.zip, some of the permissions in /usr/bin are 766. This is how I fixed it:		In FreeLink_arm9-1.0rev2.zip, some of the permissions in /usr/bin are 766. This is how I fixed it:
	find /usr/bin -type f -perm -g+w,-o+w -exec chown root.root {} \;		find /usr/bin -type f -perm -g+w,-o+w -exec chown root.root {} \;

RobNC: added notes about pending forum information

RobNC — Mon, 01 Mar 2010 03:04:17 GMT

added notes about pending forum information

← Older revision		Revision as of 03:04, 1 March 2010
Line 23:		Line 23:

	Be warned!		Be warned!
		+
		+	UPDATE: from the serial console, it appears that the LS v2 doesn't boot from the HDD any longer, and in my case didn't even go into EVM. Waiting the result of this forum post [http://forum.buffalo.nas-central.org/viewtopic.php?f=39&t=21578&p=135774#p135774] to determine how to fix this situation when Buffalo 2.11 firmware was previously installed. --[[User:RobNC\|RobNC]] 03:04, 1 March 2010 (UTC)

Pjtait at 04:19, 6 June 2009

Pjtait — Sat, 06 Jun 2009 04:19:25 GMT

← Older revision		Revision as of 04:19, 6 June 2009
Line 18:		Line 18:

	Very great text, but I fear there are two things which could confuse beginners. Within the update the message "Configuration file `/etc/init.d/networking' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. ..." appear, one sentence about this would be nice. The other thing is the line "aptitude unhold udev", should the user enter this command or not? And one more, it seems to me that it is impossible to install WebMin when you follow this steps, because "Disk full" message. --[[User:Lastwebpage\|Lastwebpage]] 10:25, 23 December 2008 (UTC)		Very great text, but I fear there are two things which could confuse beginners. Within the update the message "Configuration file `/etc/init.d/networking' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. ..." appear, one sentence about this would be nice. The other thing is the line "aptitude unhold udev", should the user enter this command or not? And one more, it seems to me that it is impossible to install WebMin when you follow this steps, because "Disk full" message. --[[User:Lastwebpage\|Lastwebpage]] 10:25, 23 December 2008 (UTC)
		+
		+	== This procedure does not seem to work with an LS v2 that has previously been updated to the Buffalo 2.11 firmware ==
		+	The LS always goes into EM on the first reboot, requiring TFTP recovery.
		+
		+	Be warned!

Lastwebpage: /* Update of the Debian repository and packages */

Lastwebpage — Tue, 23 Dec 2008 10:25:40 GMT

Update of the Debian repository and packages

← Older revision		Revision as of 10:25, 23 December 2008
Line 17:		Line 17:
	== Update of the Debian repository and packages ==		== Update of the Debian repository and packages ==

-	Very great text, but I fear there are two things which could confuse beginners. Within the update the message "Configuration file `/etc/init.d/networking' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. ..." appear, one sentence about this would be nice. The other thing is the line "aptitude unhold udev", should the user enter this command or not?	+	Very great text, but I fear there are two things which could confuse beginners. Within the update the message "Configuration file `/etc/init.d/networking' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. ..." appear, one sentence about this would be nice. The other thing is the line "aptitude unhold udev", should the user enter this command or not? And one more, it seems to me that it is impossible to install WebMin when you follow this steps, because "Disk full" message. --[[User:Lastwebpage\|Lastwebpage]] 10:25, 23 December 2008 (UTC)

80.132.11.212: /* Update of the Debian repository and packages */ new section

80.132.11.212 — Sun, 21 Dec 2008 23:36:01 GMT

Update of the Debian repository and packages: new section

← Older revision		Revision as of 23:36, 21 December 2008
Line 14:		Line 14:

	In the end I used firmware 2.10 as my basis, exchanged the relevant packages with the ones from Freelink and got on with it. A few very sweaty moments with the device rebooting at least three times and flashing on all diodes resulted in a a successful install of Debian. Thanks! [[User:Refdoc\|Refdoc]] 08:09, 28 March 2008 (CDT)		In the end I used firmware 2.10 as my basis, exchanged the relevant packages with the ones from Freelink and got on with it. A few very sweaty moments with the device rebooting at least three times and flashing on all diodes resulted in a a successful install of Debian. Thanks! [[User:Refdoc\|Refdoc]] 08:09, 28 March 2008 (CDT)
		+
		+	== Update of the Debian repository and packages ==
		+
		+	Very great text, but I fear there are two things which could confuse beginners. Within the update the message "Configuration file `/etc/init.d/networking' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. ..." appear, one sentence about this would be nice. The other thing is the line "aptitude unhold udev", should the user enter this command or not?

Refdoc: Linkstation Live 500GB Gigabit version 2 confusion

Refdoc — Fri, 28 Mar 2008 13:09:34 GMT

Linkstation Live 500GB Gigabit version 2 confusion

← Older revision		Revision as of 13:09, 28 March 2008
Line 6:		Line 6:

	I should have the Linkstation Live Old hardware when comparing my device to the pictures on the site. Although, when I did the install of FreeLink, the instructions for the newer hardware worked better ("Installation on V2 (NEW hardware) LS LIVE (running 2.06 Buffalo firmware) using LSUpdater"). The instructions for the older (v1) Linkstation Live just caused the Linkstations firmware to corrupt. Before flashing, I had the firmware version 2.06 installed.		I should have the Linkstation Live Old hardware when comparing my device to the pictures on the site. Although, when I did the install of FreeLink, the instructions for the newer hardware worked better ("Installation on V2 (NEW hardware) LS LIVE (running 2.06 Buffalo firmware) using LSUpdater"). The instructions for the older (v1) Linkstation Live just caused the Linkstations firmware to corrupt. Before flashing, I had the firmware version 2.06 installed.
		+
		+	== Linkstation Live 500GB Gigabit version 2 confusion ==
		+
		+	Some confusion when I looked at my Linkstation up close before I went ahead with it.
		+
		+	Despite being a version 2 Linkstation Live the device had firmware 1.06 - and not 2.06 as expected. Or at least this is what it said on the status pages in the link station.
		+
		+	In the end I used firmware 2.10 as my basis, exchanged the relevant packages with the ones from Freelink and got on with it. A few very sweaty moments with the device rebooting at least three times and flashing on all diodes resulted in a a successful install of Debian. Thanks! [[User:Refdoc\|Refdoc]] 08:09, 28 March 2008 (CDT)

Rollot: Are differences between the V1 and V2 Linkstation Live stated correct?

Rollot — Tue, 22 Jan 2008 13:10:24 GMT

Are differences between the V1 and V2 Linkstation Live stated correct?

← Older revision		Revision as of 13:10, 22 January 2008
Line 2:		Line 2:
	find /usr/bin -type f -perm -g+w,-o+w -exec chown root.root {} \;		find /usr/bin -type f -perm -g+w,-o+w -exec chown root.root {} \;
	find /usr/bin -type f -perm -g+w,-o+w -exec chmod 555 {} \;		find /usr/bin -type f -perm -g+w,-o+w -exec chmod 555 {} \;
		+
		+	== Are differences between the V1 and V2 Linkstation Live stated correct? ==
		+
		+	I should have the Linkstation Live Old hardware when comparing my device to the pictures on the site. Although, when I did the install of FreeLink, the instructions for the newer hardware worked better ("Installation on V2 (NEW hardware) LS LIVE (running 2.06 Buffalo firmware) using LSUpdater"). The instructions for the older (v1) Linkstation Live just caused the Linkstations firmware to corrupt. Before flashing, I had the firmware version 2.06 installed.

Hsum: fix for permissions to execute some /usr/bin stuff as a non-root user

Hsum — Sun, 11 Nov 2007 08:47:56 GMT

fix for permissions to execute some /usr/bin stuff as a non-root user

New page

In FreeLink_arm9-1.0rev2.zip, some of the permissions in /usr/bin are 766. This is how I fixed it:
find /usr/bin -type f -perm -g+w,-o+w -exec chown root.root {} \;
find /usr/bin -type f -perm -g+w,-o+w -exec chmod 555 {} \;