Project

General

Profile

Actions

Todo #107

closed

NanoBSD - Update Packages to work properly with 1.2.3-RC2 NanoBSD

Added by Christian Bendl over 14 years ago. Updated over 14 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
10/02/2009
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

Some (most likely 8/10) packages need writing access to their config files...
this leads to warning messages.. and in most cases to make packages useless.

Actions #1

Updated by Scott Ullrich over 14 years ago

8/10? Come on. If you are going to file a bug report please at least list the packages that have issues!

Actions #2

Updated by Chris Buechler over 14 years ago

What we need is someone to go through and try them all and see specifically which ones work and which don't. And ideally send patches to fix, but just having some testing help would be good.

Actions #3

Updated by Christian Bendl over 14 years ago

ATM I'am in no condition to test all of them on my working router :)

in a few weeks i planned on setting up some kind of freenas (its a shame project is abandoned),
until then i might be able to setup another nano bsd pfsense on that hw.. and test some packages.

sry for the inconvenient bug report ;)

Actions #4

Updated by Joachim Fritschi over 14 years ago

FreeSwitch Installation fails on my nanobsd 1.2.3-RC3 built on Sun Oct 4 02:37:42 UTC 2009. The memory backed /var partition is to small to download the package. The Package itself is ~53M and the partition only 58M.

dmesg

pid 655 (php), uid 0 inumber 4031 on /var: filesystem full

df -h

/dev/md1              58M     58M   -4.3M   108%    /var

After that the package appears in all the menus but the package seems broken. The installer itself reports no errors and in the logs i only have the filesystem full error.
When trying to restart the service i get no errors, but nothing happens.
Maybe it would be nice if the size of the memory backed partitions could be set from the gui.

Actions #5

Updated by Jim Pingle over 14 years ago

I have a Google Docs spreadsheet that I have started, listing packages for NanoBSD and testing results, error messages, etc.

If any of the other devs want access, let me know.

So far, out of 43 relevant packages, 21 I haven't tested yet, 2 are known to fail badly, and 20 install cleanly. Of the ones that install, only one of those installed but didn't work (TFTP). A few packages have been fixed already during the testing (Thanks mcrane!) but there are still plenty more to test.

Seems to be a good percentage of working packages, actually. Even if the other 21 fail, that is still ~50% not 8/10.

Actions #6

Updated by Jim Pingle over 14 years ago

Here is a link to that spreadsheet of NanoBSD packages mentioned in the previous update:

http://spreadsheets.google.com/ccc?key=0AojFUXcbH0ROdFdHTTlKNWNSMG5rRjQwZE1fYVgySGc&hl=en

Should be viewable by all. If you want write access, let me know.

Actions #7

Updated by Jim Pingle over 14 years ago

I worked a bit on packages today and fixed quite a few to work on NanoBSD. There are still several with issues that will need attention from their respective maintainers.

Current totals:
Packages available for NanoBSD: 43
Install Correctly: 42
Working Properly: 30
Need more Testing: 5
Not working: 8

Details are available in the spreadsheet linked in my last update.

Actions #8

Updated by Jim Pingle over 14 years ago

It's now up to 39 working packages out of 42 available to install. And two of those don't work on full installs either.

I disabled FreeSWITCH from NanoBSD, according to the maintainer (mcrane) he said it needs constant write access so it won't be available for NanoBSD.

On the upside, I was able to make Squid and SquidGuard work, though you probably want HDD cache = 0 on squid, and to be careful what you enable on squidguard. I didn't fully test the blacklist features, but ACLs/Destinations work. Logging options for both should be monitored closely, it would be all too easy to fill up nano's 40MB /var if you're not careful. As long as you're aware of the limitations, it works.

Actions #9

Updated by Chris Buechler over 14 years ago

  • Status changed from New to Resolved

these are all fixed (that we're aware of), if there are remaining issues, specific individual tickets can be opened.

Actions

Also available in: Atom PDF