FAQ Additional Questions
Hz4711 had this problem: the linkstation has a service called ls_servd(apservd) which is needed for the firmware updater. it did not start. over telnet he could delete /var/run/ls_servd-eth0.pid because it was pretty old (you can check this by doing a "ls -a" in /var/run)...
afterwards start apservd:
hopefully this happened only with an old openlink-version
I cannot connect to the Buffalo`s FTP-Server? Why?
Buffalo has changed the FTP-Server-Address....
IP: 22.214.171.124\\ Username: guest\\ Password: We1c0m3
or here is the link to go there directly over your browser:
/bin/more doesn't work. It says 'more: /dev/console: No such device'.
cd /dev\\ mknod tty0 c 4 0\\ mknod tty1 c 4 1\\ mknod tty2 c 4 2\\ mknod tty3 c 4 3\\ mknod tty4 c 4 4\\ mknod tty5 c 4 5\\ mknod tty6 c 4 6\\ mknod tty c 5 0
(by ramon. see http://linkstationwiki.org/forum/3_270_0.html)
(Can we add this back to the main FAQ?)
If you follow the FAQ to move /usr to say, /mnt/hda/moved_folder/usr and symbolic-link it back, some relative links won't work. For example, /usr/bin/wget has the symbolic link ../../bin/busybox, and that would get resolved to /mnt/hda/moved_folder/bin/busybox, which does not exist. Therefore, you can link all unmoved directory under root back to this /mnt/hda/moved_folder:
ln -s /bin /mnt/hda/moved_folder\\ ln -s /dev /mnt/hda/moved_folder\\ ln -s /etc /mnt/hda/moved_folder\\ ln -s /lib /mnt/hda/moved_folder\\ ln -s /lost+found /mnt/hda/moved_folder\\ ln -s /mnt /mnt/hda/moved_folder\\ ln -s /proc /mnt/hda/moved_folder\\ ln -s /root /mnt/hda/moved_folder\\ ln -s /sbin /mnt/hda/moved_folder\\ ln -s /sys /mnt/hda/moved_folder\\ ln -s /tmp /mnt/hda/moved_folder\\ ln -s /www /mnt/hda/moved_folder
A lot of commands stopped working. Busybox is overwritten after installing Development Tools.
This is very possible if you install some package which overwrites busybox through its symbolic links. For example, the Development Tools overwrites 'cmp' (through /usr/bin/cmp -> /bin/busybox) and this may ruin your busybox. One way to prevent this is add the k option (non-overwriting) for tar in install.sh.
If your busybox is overwritten, you might not even be able to boot. In that case, you'll have to rescue your busybox through other means, e.g. mount your HD under PC and use ext2_fix to write back the binary file.
I found busybox is easily overwritten, so I always keep another copy somewhere else and copy it back after any potential writing into /bin, /sbin, or /usr/bin.