I volunteered to help someone with a project and I am struggling to come up with a solid policy on updates to NanoBSD.
Because it is an Read-Only disk arrangement normal updating procedures do not apply.
New images must be crafted for each update.
I recommended every 6 months and no more than yearly. They are leaning to yearly.
We have contingency plans for anything real foul comes along.
But I started to think -instead of a calendar date maybe we should just worry about tracking -RELEASE 's and do emergency build for anything tragic that needs patching. That is more or less the way I use it now. Sometimes I have skipped point releases though.
Thoughts?
NanoBSD will be the OS for an embedded commercial appliance.
Because it is an Read-Only disk arrangement normal updating procedures do not apply.
New images must be crafted for each update.
I recommended every 6 months and no more than yearly. They are leaning to yearly.
We have contingency plans for anything real foul comes along.
But I started to think -instead of a calendar date maybe we should just worry about tracking -RELEASE 's and do emergency build for anything tragic that needs patching. That is more or less the way I use it now. Sometimes I have skipped point releases though.
Thoughts?
NanoBSD will be the OS for an embedded commercial appliance.