CALL FOR TESTING: NanoBSD Packages
-
As we get closer to release for 1.2.3, we need to test NanoBSD packages as much as possible. I have a Google Docs spreadsheet available with the list of packages that are currently available on NanoBSD. This list may shrink or grow as packages are added or removed due to testing results.
The spreadsheet is here:
http://spreadsheets.google.com/ccc?key=0AojFUXcbH0ROdFdHTTlKNWNSMG5rRjQwZE1fYVgySGc&hl=enIt would help to get all of these results compiled in a central place. Some packages may just need minor fixes, and others may need excluded entirely. The main thing is that they all need to be tried. Not just installed, but tested. Some of these packages depend on certain environments (Like OpenBGP) or certain hardware (Like NUT), so if you have access to a means for testing a package, try it out and add some notes to the spreadsheet and this thread.
Be sure to install, change settings, try to run the package, and report any errors you encounter (either on screen, in system logs, etc). The most common errors will probably be referencing a "read only filesystem" which indicates that the package needs some code added to properly switch to and from read/write and read only modes for the CF.
If you encounter an error with a package, it may also help to try the same package on a full install if you have one handy, to be sure the error is actually from NanoBSD and not a problem with the package itself.
-
Lots of views, no replies. ;D
I have fixed a LOT of packages today, the number of packages that do not work on NanoBSD is now in the single digits.
The following packages need testing, but appear to work:
AutoConfigBackup
LCDproc
Open-VM-Tools
Proxy Server with mod_security
nut -
Hi, Jimp. I replied in the hardware thread (since I had mentioned a few days ago trying to switch from full/HD to nano/CF). I do not see havp on your spreadsheet at all. It should be useable (I would think), since it can be set to use the ramdisk filesystem it creates. Unfortunately, I do not know where to get the package from (it does not show up in the list on the dashboard for a nanobsd install.)
-
Squid, Squidguard, HAVP, and some others have already been flagged as not being "nano-safe" for one reason or another.
I would like to get squid and squidguard working, and perhaps HAVP if I can, but it will take a lot more testing.
The problem with nano is that generally there is not enough RAM to handle all of these things, plus you would need to have a squid cache size of 0 since there is nowhere to write the cache.
-
Well, my interest (and what I was doing before), was running havp as a transparent proxy, without any squid involvement. I get that /var and /var/log use some RAM. One can always tweak the settings for havp to not scan above a certain size (I think it already defaults to 5MB or so?) I'd be happy to help test this out - if all else fails, I'd be willing to run a totally unsupported havp package, since I don't really want to switch back to HD :(
-
I may see what I can do about opening those up tomorrow. I'll have to try them from a personal test package repo first before unleashing them on the world. :)
-
HAVP may take more work than I thought, but I'll have to look at it again when I'm feeling a little better.
Squid and Squidguard were fairly easy to fix, and have been re-enabled for use on nanobsd, with a couple caveats:
1. Use HDD cache=0 on squid, unless you have some kind of external storage for the cache.
2. Be careful what you enable in squidGuard, as blacklists will likely use a lot of space in /var and there is not much to spare. -
Anyone else have any testing input? Anyone? Good news? Bad news? Indifferent news? Any feedback is better than none.
Thanks!
-
Anyone else have any testing input? Anyone? Good news? Bad news? Indifferent news? Any feedback is better than none.
I was finally able to install avahi. It interacted badly with mDNSResponder on the Macs on my network, causing them to think that there were other other hosts with the same name as themselves. This led to an endless loop of automatic self-renaming which stopped only when I uninstalled the package. I don't know enough about avahi to be able to tell why this happened. I was hoping to use the package to work around the lack of OpenVPN bridging support in pfSense. I wanted it to pass mDNS packets between the OpenVPN subnet and the LAN, but there seems to be no way of configuring it to do that.
-
That would be Avahi itself and not NanoBSD specific. Start a new thread for that. (NB - I use it to join two remote LANs via OpenVPN and it works well.)
-
Anyone else have any testing input? Anyone? Good news? Bad news? Indifferent news? Any feedback is better than none.
Thanks!
I do, if it helps ;)
LCDproc: installs okay, but haven't been able to get output on the (picolcd) display, keep getting the standard output the manufacturer put in.
Log errors:
Nov 17 20:03:50 php: lcdproc: The chosen lcdproc driver is not a valid choice
Nov 17 20:03:57 php: lcdproc: Stopping service: no com port selected
Nov 17 20:04:00 php: lcdproc: The chosen lcdproc driver is not a valid choice
Nov 17 20:04:03 php: lcdproc: Stopping service: no com port selectedAlready posted that in a topic of mine, also in the picolcd topic and I tried contacting ermal since he/she said there would be a working version published soon. He posted that in January, no response from PM.
Tested on pfSense-1.2.3-2g-20091105-2039-nanobsd.
-
That sounds more like it is missing a driver than something nanobsd-specific. I'd wait to hear back from ermal or someone else working on the lcdproc package.
-
If the driver is missing, how can I check if it is that?
(Note, have some basic commandline skills, if necessary.)Already done that, ermal has been online here couple of times since I've send the message, no response, don't even know if it arrived.
Don't think there is anyone (else) working on the package… -
I'm not familiar with the lcdproc package, so I can't say for certain.
-
'kay.
Any idea who can help and actually replies to private messages?
Already tried (besides ermal) a (different) admin, to ask who is working on the package, but also no answer back. -
Most people on this forum prefer to keep things in the public forums, and are turned off by PMs.
You might try the support mailing list, or IRC.
-
Not getting any response there either, that's why I tried PM's.
Uhm, support mailing list?
edit: found it -
These 2 not very big packages, but packages nonetheless work fine:
- iperf
- blinkled
Fit123 doesn't work though (seems to expect a RW filesystem):
- installs correctly, but switching any of the features on/off have no effect
- themes work fine
- error when selecting DDNS tab in Fit123: Warning: fopen(/usr/local/pkg/Fit123/ddns/ddns.php): failed to open stream: Read-only file system in /usr/local/pkg/fit123.inc on line 164
Hardware: 2 carped ALIX 2D3's / pfSense 1.2.3 RC3 and 4GB CF cards.
-
Hello all
i use the 1.2. 1G images for testing.
Now i see that the full versions and the 4G versions are still beeing updated, but the 1G version is still from 14 Nov
both the update and the new to install versions.Are the 1 GB version obsolete?
regards,
Johan -
Sylhouette,
That is unrelated to this topic, please start a new thread for a different question.
