Packages update Request
-
I just forgot to tag the havp widget as not being for embedded, but I would like to see havp working on nanobsd if possible. I haven't had any more time to look at it.
-
bummer, i had high hopes :) Is there any way I can help with this? I work with software for a living, so I'm not out of my depth here…
-
I outlined what needs to happen a few posts back when I addressed a post toward dvserg. Basically any time that the package needs to write to the CF, it needs to first switch to read/write mode and then back to read only mode when complete. This would be for config changes, writing out an RC script, updating virus defs, etc.
Also, HDD scanning would have to be disabled, and only RAM disk scanning allowed, since there is no HDD. (Eventually I suppose support could be added to allow using external storage such as a USB HDD, but that is beyond the scope of what we're doing right now)
File activity in /tmp and /var need to be limited as well. You can write small files there all the time but nothing large, as it is also a RAM-based disk.
-
Okay, this sounds manageable, given that I am on a learning curve here (bsd pkg system). Would I take the HD version of the package and make those changes? If so, where would I get it?
-
It's not the bsd package system you'd be dealing with, but the pfSense package system.
You can checkout the pfSense packages repo from git if you want to look at the individual packages.
-
sorry for the confusion. i'm aware there is a difference - i was referring to the pkg_* system, which is specific to BSD, not (for example) linux. i will take a look…
-
Ah… well, the pfSense package stuff is mainly XML and PHP. In this case, all of the changes will probably be in the PHP code for the package.
-
I am not clear if there is a difference between the embedded versions and the full versions, in terms of: are there different actual packages, or does the package have to figure out the operating environment and act accordingly?
-
There is no difference in packages. If any platform-specific code is needed, you can check /etc/platform, if the file contains the text "nanobsd" then it's on nanobsd.
The functions to mount things read/write and read only are basically a no-op on full installs, so they can be inserted where needed and will only affect nanobsd.
-
cool thanks!
-
I split the package development questions off into its own thread:
http://forum.pfsense.org/index.php/topic,19986.0.html -
How possible update pfSense packages-7 tree ?
-
How possible update pfSense packages-7 tree ?
I think only GeekGod, cmb, and a few others have access to that. They have to manually place new files there. Do you have a file that needs updated or changed? You can probably open a redmine ticket to get it done and they'll pick it up.
-
Thanks
I see a way ::) -
dvserg: just email me with info on what needs to be updated. cmb at pfsense dot org
