I had a similar problem on my home server recently. Don't bother with the uninstall-rebuild-reinstall trick, you'll only get the exact same problem with another package/port. And then another, etc. I hope for your sake that someone else knows of an easier fix, but what I ended up doing was to...
The port www/nspluginwrapper requires Linux, no matter which one. Binary packages really shouldn't be built against -f10 any more, but if they still are you can either build them yourself from ports or wait until the packages get updated.
Does that file exist? If so, does the user running sysguardd have sufficient permissions? Is it normal that the filename is enclosed in both single and double quotes (in other words: does sysguardd try to open a file /usr/local/etc/ksysguarddrc or a file "/usr/local/etc/ksysguarddrc")?
First this: Topics about unsupported FreeBSD versions.
FreeBSD 8.1 has reached End-Of-Life over two years ago. It is no longer supported, there will be very few (if any) people who still use it and it hasn't had any security updates in years either. It might be possible to install ImageMagick...
If you have these working, I'd encourage you to create ports for them. See the Porter's Handbook and feel free to ask questions either here or on the freebsd-ports@ mailing list.
Speaking of which, feel free to share your experiences and any sources you find helpful. I'm soon going to have to make that transition too (in other words I'm currently still using /etc/rc.conf) so pointers are always welcome.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.