Linux Open Source BSD
Training Support & Administration
Frequently Asked Questions about Binary Updates for NetBSD0.1 Why charge?
0.2 How do I set it up?
0.3 Why NetBSD?
0.4 What about kernel updates?
0.5 Can this be automated?
0.6 How long does it take you to build a binary update?
0.7 Do I need to apply (use) the binary updates in order?
0.8 Do I need to use each binary update?
0.9 What can I use the downloadable Binary Updates database for?
0.10 Why is this like BSD/OS mods?
0.11 What about later configurations (configuring after software changes)?
0.12 Do these security updates upgrade the software completely?
0.13 Can anyone join the Binary Updates announcements mailing list?
0.14 How soon are Binary Updates available?
0.15 What about the other BSDs?
0.1 Why charge?
Yes, this is supporting open source software. We charge to help pay for hosting and bandwidth. And this service costs money to help cover the man-hours used in building and providing the updates.
In addition, we are dedicating 5-percent of the income to donate for The NetBSD Project.
Nothing really needs to be setup. Each binary update is a standalone shell script that can be ran via sh. (You don't need perl.) It does log to /var/log/binary-updates.
0.3 Why NetBSD?
NetBSD is known for its technological advantages, great security history, and ongoing stability. It has proven to be an easy-to-administer operating system and has a friendly community.
We can not easily automatically provide kernel updates for customized kernel configurations. But when applicable, we will provide kernels using standard GENERIC configuration. (Ask us for customized solutions.)
In addition, we have provided source diffs for patching the kernel source.
Yes. Fetch the Binary Updates database file. See if you need a new update. Fetch it. And run it.
Depending on the availability of source and amount of files to update, this can take an entire day of manually patching files, building and testing.
It is not required. But some files may end up taking advantage of earlier fixes. Also, some fixes may just replace previous Binary Update files.
You only need to update what you use, but it is a good idea to update all. For example, even if you don't use lpd and lpr under NetBSD 1.5.2, it is still a good idea to have secure binaries for them.
You can automatically fetch it each day and then email a diff against your earlier copy to let you know about new updates. It can also be parsed to create the download URL for automatic download.
BSD/OS mods are perl scripts that are used to update BSD/OS systems (between releases). These mods are used for important security issues and for general operating system improvements. The script backs up files before replacing.
Some software may need further configurations. We will announce this as applicable. Also, some software may need to be restarted as applicable, like sshd when it is updated.
Generally, the updates do not upgrade the software completely like a complete CVS update may do. Instead of upgrading software to add new features (while fixing bugs), the code is usually just modified for the individual security issues. So, usually, version numbers don't change.
Yes. Please contact us to join.
Often, we can have a Binary Update available before an official NetBSD Security Advisory is announced due to earlier announcements on various forums. Sometimes, security issues are not disclosed except when official announcement is released -- so our Binary Updates will be delayed accordingly.
We may be offering this for OpenBSD and FreeBSD too. It depends on our customer's needs. Let us know, if this is something you can use.
|Home | About | Services | Training | Hosting | Contact|