Talk:Convert your PPC LinkStation into a full-blown Debian system

From NAS-Central Buffalo - The Linkstation Wiki
Jump to: navigation, search

Why fix_ext2_magic? Is it really necessary?

buffalo invented a way to secure the first partition of the hdd /dev/hda1 by changing the magic_number in the ext_filesystem to something unnatural (all linkstations and i think all terastations, kuroboxes do not have this problem of course). in reality the magic_number is a completely normal one, but because of this change you cannot mount the partition on a desktop. the fix_ext2_magic-app fixes this and afterwards you can mount the partition as normal. In fact i did yesterday after i deleted some stuff as root which made my LS unbootable. before running fix_ext2_magic there was no chance to mount it, afterwards it was working as normal. so the answer is: yes, it is necessary.Mindbender 03:16, 11 July 2006 (EDT)

Jumper setting

"make sure to return the hard drive jumper to cable select"

is it true that LS1 uses cable select as default? LS2 is using master setting ...--Hanfbauer 09:39, 28 July 2006 (EDT)

Step 13. Now With Example

For example, download
to your Windows/Linux machine, unzip it and then unzip the image.dat from it.
You will be prompted for a password...use the password from
and you will get a tmpimage.tgz.
Untar this tarball to /dev/hdx1 and you should be fine.

(Yes, indeed. Thank you, Mindbender!)

The reason for mounting partition 1 and using fix_ext2_magic is unclear. This article would be better split into 2 articles. One describing the LS-HG partition layout; the partition magic number problem and fix_ext2_magic; how to resize those partitions (and why you would want to do that).

This article then then focus on copying Openlink/Freelink to partition 1 and post install configuration.

I recently installed Freelink to my LS-HG and found problems with this article (apart from the partitioning thing mentioned above).

  1. The description of what to extract from the LS-HG Freelink distro is wrong.
  2. Freelink has no tmp-kun user configured