Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
http://ffp.inreto.de/ffp/0.7/
Although still working fine, the programs in the 0.5 version are a little dated by now. The next version 0.7 has lots of updates, built with a new toolchain (gcc 4.5 and current uClibc). Unfortunately, not all programs compiled for 0.5 will work on 0.7 and may need to be recompiled.
0.7 is available in two variants: The "oarm" variant should work on the same devices as 0.5. It's made for the "old ABI" (Application Binary Interface, see wikipedia for details). More recent devices usually employ the new "Embedded ABI (EABI)". Use the "arm" variant on those.
Overall, 0.7 works mostly the same way as 0.5. A noteable change is funpkg. It was a shell script in 0.5, and is now a C program. And there's a new script called "slacker" that can download and install packages from the Internet (try "slacker -Ui").
Have fun!
Offline
Whoow!! Very good idea to refresh ffp 0.5
The toolchain was becoming old, and was sometimes running into problems when trying to build recent sources from the Internet.
I just tried ffp 0.7 on my DNS-313, (I did a backup of my previous ffp folder, then deleted it, before installing 0.7)
First step for me was to replace /mnt/HD_a2 references by /mnt/HD_a4, in funplug script (on DNS-313, sda2 is formated in NTFS, and can't be use for ffp).
The installation runs perfectly, and after a few minutes, I was able to telnet my device.
First impressions:
- Native ffp applications runs without any problem. I re-enabled ssh and lighttpd immediately.
- the slacker command is so great! Very practical to install and upgrade package, in a "menuconfig" way.
I just got a problem with the "new" funpkg command. I was not able to reinstall my old 0.5 packages:
sh-4.1# funpkg -i unrar-4.1.3-1.tgz Skipping unrar-4.1.3-1.tgz: Invalid package filename
What is bad about the filename?
Nevertheless, the binary file still work:
sh-4.1# mkdir temp sh-4.1# tar xzf unrar-4.1.3-1.tgz -C temp/ sh-4.1# temp/ffp/bin/unrar --help UNRAR 4.10 beta 3 freeware Copyright (c) 1993-2011 Alexander Roshal ...
Maybe I don't use funpkg correctly? Or maybe it is only compatible with 0.7 packages?
Thank you very much :-)
Offline
Electrocut wrote:
I just got a problem with the "new" funpkg command. I was not able to reinstall my old 0.5 packages:
Code:
sh-4.1# funpkg -i unrar-4.1.3-1.tgz Skipping unrar-4.1.3-1.tgz: Invalid package filenameWhat is bad about the filename?
0.7 is available in the "arm" and "oarm" variants. I changed the package naming to include the variant. Package names must now look like NAME-VERSION-VARIANT-REVISION. funpkg doesn't check the variant field, but insists that it exists in the name.
So, if you want to install a 0.5 package, you need to rename it. Just insert -oarm-.
Offline
Thank you, I will try!
Will you provide building scripts for ffp packages, like the previous ones available on svn://inreto.de/svn/dns323/funplug/trunk ?
(for the moment, the previous scripts doesn't work anymore since I haven't distcc)
Offline
Electrocut wrote:
Will you provide building scripts for ffp packages, like the previous ones available on svn://inreto.de/svn/dns323/funplug/trunk ?
Yes, sure.
Available at http://ffp.inreto.de/ffp/0.7/src/ or via rsync:
rsync -avP --delete ffp.inreto.de::ffp/0.7/src .
Last edited by fonz (2012-01-25 22:52:34)
Offline
Thank you for the update! ffp 0.7 is a treat but I'll have to move back to my trusted 0.5. I rely on Transmission and it does not work with 0.7 yet. Transmission throws this error:
transmission-daemon: can't load library 'libssl.so.0.9.8'
libssl is 1.0.0 in 0.7 and I haven't had the time to setup my own build environment.
Thanks again for providing these types of updates since there are so many people that rely on them.
Jon
Offline
I run fun_plug 0.5 off of a mirror created with mdadm-2.6.7-1 on a DNS323. When I updated to fun_plug 0.7 some commands, like ls & rm won't work on the mirrored filesystem. I get errors like "Value too large for defined data type". I can traverse the directory structure and run programs from it, but I can't do directory listings or remove files on it.
Offline
The "oarm" variant should work on the same devices as 0.5. It's made for the "old ABI" (Application Binary Interface, see wikipedia for details).
Can you post the link to wiki the refers to ffp 0.7
Thanks for doing this!
Offline
bound4h wrote:
Can you post the link to wiki the refers to ffp 0.7
No sure what you mean. Maybe http://dns323.kood.org/howto:ffp#version_0.7
Offline
That's it, I just missed it. Thank you
Offline
I removed /ffp (0.5) version and did a clean install of ffp 0.7 on a dns-323 FW1.10, using oarm version. Observations:
ffp
+ All went well! Only had to recreate /ffp/home/root, enable sshd starter, disable telnet starter --> OK. Disk are going to sleep as expected.
+ 'top' throws "Unknown HZ value! (0) Assume 100." at start, but works ok. In ffp 0.5 it didn't throw the error
+ 'vi' doesn't use full terminal windows (I use putty), but only 80x25. Resize of terminal does not help. In ffp 0.5 the whole terminal was used, resize did work. vim on the other hand, works ok
+ 'uptime' still prints nonsense, but did this under ffp 0.5 also, and in my understanding is a bug of the dns-323 firmware, not ffp
packages
+ I've installed "squeezecenter-funplug" via slacker (which is great, by the way), then removed it via slacker. I leaves a /ffp/start/ffp-admin.sh, which is not working ("/ffp/sbin/httpd: Not executable"). What is ffp-admin, by the way? I tries to expose a web interface at port 90?
+ What is squeezecenter-funplug anyway? The squeezecenter server is in package "logitech media server" (the new name of the slimserver/squeezebox server). Maybe ad a pointer to the logitech media server in the package description of squeezecenter-funplug?
+ package "logitech media server": slimserver.pl throws
The following CPAN modules were found but cannot work with Logitech Media Server: Image::Scale: Can't load '/mnt/HD_a2/ffp/lib/logitechmediaserver-7.7.1/CPAN/arch/5.14/arm-linux-thread-multi-64int/auto/Image/Scale/Scale.so' for module Image::Scale: File not found at /ffp/lib/perl5/5.14.2/arm-linux-thread-multi-64int/DynaLoader.pm line 190. at (eval 101) line 2 Compilation failed in require at (eval 101) line 2. BEGIN failed--compilation aborted at (eval 101) line 2. To fix this problem you have several options: 1. Install the latest version of the module(s) using CPAN: sudo cpan Some::Module 2. Update the module's package using apt-get, yum, etc. 3. Run the .tar.gz version of Logitech Media Server which includes all required CPAN modules.
Not sure if it is really a problem with Scale.so. In your logitechmediaserver-standalone funplug (http://ffp.inreto.de/dns323/squeezecenter-funplug/) - which is working - is the same Scale.so.
cleanup.pl seems to work, but throws at start
Can't locate Wx.pm in @INC (@INC contains: CPAN CPAN /ffp/lib/perl5/site_perl/5.14.2/arm-linux-thread-multi-64int /ffp/lib/perl5/site_perl/5.14.2 /ffp/lib/perl5/vendor_perl/5.14.2/arm-linux-thread-multi-64int /ffp/lib/perl5/vendor_perl/5.14.2 /ffp/lib/perl5/5.14.2/arm-linux-thread-multi-64int /ffp/lib/perl5/5.14.2 .) at ./cleanup.pl line 21.
I've installed perl-modules-5.14.2-oarm-1.txz with no change...
Keep up the great work with ffp!!!
Loose gravel
Offline
Awesome work on ffp-0.7, fonz!
I'm in the process of building several packages for arm already, oarm is to follow.
Looking at /ffp/etc/funpkg, it looks to me as if the new tool slacker is extensible by adding additional repositories to the "sites" file.
Can you explain the format a bit and what one needs to do in order to make it work?
Also, I've never set up an rsync server before. Is there a tutorial somewhere so I can make my packages available via rsync as well (and possible integrate them into slacker?)
EDIT: After looking at slacker (which is just a simple shell-script!) I figured out that a repository can be hosted via FTP, HTTP or rsync. So no need for an additional rsync server.
I added my own package repository to the sites file and it works like a charm. This will simplify things a lot!
Last edited by KyleK (2012-01-30 15:58:46)
Offline
KyleK wrote:
I added my own package repository to the sites file and it works like a charm. This will simplify things a lot!
Glad you like it. The script isn't complicated. You only need to remember to always update the CHECKSUMS.md5 file when you add, remove or update a package.
When you're ready to share your packages, feel free to add your site to the wiki:
http://dns323.kood.org/howto:ffp#slacker_sites
Offline
Done
I have a question: With funplug-0.5, I used to see when the HDDs wake up/go to standby by typing "dmesg" on the shell. That is not the case anymore.
It is not shown in /var/log/user.log either.
Is it because of changes in ffp-0.7, or some misconfiguration of mine?
Offline
KyleK wrote:
That is not the case anymore.
Maybe your drives don't sleep anymore? I have no idea how ffp (or anything else) could (intentionally or acidentally) suppress kernel messages in dmesg.
Offline
I'm using ffp 0,7 here, and disks go to sleep as expected...
Plug off your ethernet cable. If disks go to sleep then, something "external" is keeping your disks up (repeated access to filesystem, etc). If not, start top. look for running processes. Post list of processes here.
Btw. I've upgraded to Fw 1.10. After boot the upnp Server was scanning the whole filesystem and every media file (which took ages) causing my disks to stay awake.
Offline
Yes, disks do go to sleep, I even confirmed that before writing the above question.
The problem I see is that the message that the disks have gone to standby doesn't show up in the logs anymore.
I went back and booted with ffp-0.5 to then compare the dmesg output with that of ffp-0.7.
I discovered that dmesg outputs only a fraction of the boot information when compared to ffp-0.5.
It seems the dmesg output is truncated, and stuck after boot (no new messages appear).
Offline
Thanks for releasing 0.7. It's working quite well for me with 1 exception: the DBD cnid scheme in Netatalk is broken. Any time cnid_dbd is invoked, it segfaults. The easiest way to demonstrate the problem is to run the following:
dbd -d .
in a directory that is an AFP share. I am able to use the TDB scheme, so I have something working for now, but I pretty sure DBD is a better long term option. Is anyone else seeing this? Am I missing some obvious fix to the problem?
Update: The problem was that DB5 was built with --enable-smallbuild, which means it didn't include all the functionality that Netatalk depends on. When I rebuilt DB5 without it, everything started working properly.
Last edited by woogie (2012-02-05 14:57:33)
Offline
@fonz: Looking at your build script for gettext, you delete the folder /ffp/share/gettext prior to packaging. Unfortunately, this causes autopoint to fail when building other packages (util-linux for example), because autopoint apparently has a dependency on /ffp/share/gettext/archive.git.tar.gz.
Offline
KyleK wrote:
Yes, disks do go to sleep, I even confirmed that before writing the above question.
The problem I see is that the message that the disks have gone to standby doesn't show up in the logs anymore.
I went back and booted with ffp-0.5 to then compare the dmesg output with that of ffp-0.7.
I discovered that dmesg outputs only a fraction of the boot information when compared to ffp-0.5.
It seems the dmesg output is truncated, and stuck after boot (no new messages appear).
I discovered that when I use 'dmesg --raw', I do get ouput (including the status messages from the NAS regarding disks awake/standby). But when I just type 'dmesg', nothing appears.
Offline
I did some more investigation into my 'dmesg' issue and compiled util-linux 2.18 for arm.
And behold, now dmesg works again! I couldn't find anything revealing in the util-linux changelogs, so this is still a mystery.
fonz, any reason why your script uses v2.18 for oarm, but 2.20 for arm?
Offline
There is a bug in the rsync package. The example .conf file specifies the pid file as /ffp/var/run/rsyncd.pid, while the start script insists it should be /var/run/rsyncd.pid
Offline
Is there also any new ffpbuildenv or should packages just be build with the old 0.5 ffpbuildenv?
Is there install procedure the same as for 0.5? Or where is it documented otherwise?
Is there any explanation what the difference between arm and oarm is, and what my device is?
/edit:
I found a script that figured out that my nas is capable of both, earm and oarm.
Which one is the one to prefer? Which should I use?
/edit:
So got deeper in this and got sucessfully an 0.7 installed.
I recognized so far that there is sth called makepkg to create pakackages for fun_plug 0.7.
Is there any documentation of this?
Any tutorials?
Last edited by pizzard (2012-02-26 22:15:35)
Offline