Hm, I think the reason ISPs charge for extra addresses is not so much the (perceived) scarcity of IPv4 addresses, but rather the desire to divide the market up into different segments ("home users", "business users", etc.), and charge an extra premium for those not fitting in the first category.
If you know how to do the legwork, it's not all that hard to justify allocation of more IP addresses...
I disagree, unless you want netbsd on a CPU that is not supported by 1.4.x , the reason 1.5 is not a complete os yet. It still has
quite a few bugs to work out . I would only recomend useing 1.5beta2 if you dont have to worry about loseing any important
things on your harddrive.
Oh, I'll have to disagree here; NetBSD 1.5 (even in the beta2 incarnation) is most definately a complete OS, and unless you start using the more experimental bits (unfortunately LFS still falls into that category), the risk of data loss due to file system corruption is miniscule and comparable to the risk of running NetBSD 1.4.3 or any of the other BSDs.
Perhaps a word or two about the difference between NetBSD 1.4.3 and NetBSD 1.5 is in order. The former (1.4.3) is first and foremost a bugfix release. Please note that the code branch was created quite a while ago, and even though some features have been imported from the main development branch, far from all features have received this treatment. NetBSD/i386 and sparc still use a.out as object format in 1.4.3.
On the other hand NetBSD 1.5 includes all the new features developed since the NetBSD 1.4 release was created, about May 1999. As with almost any piece of software, bugs are bound to exist, and there are obviously higher risk of finding bugs in the first version of a major release number (as with NetBSD 1.5), so if you wanted to be super-conservative you'd hold on until 1.5.1 was released. In NetBSD 1.5 the i386 and sparc ports have been converted to using the ELF object format.
In fact, the "beta" designation in NetBSD's releases really means "we think this is ready to ship, please test for any remaining minor glitches, so that we may fix those before the release goes out the door."
(I'd still recommend to upgrade to the release version once it becomes available if you decide to test any of the beta versions.)
One of the biggest differences (to a sysadmin) is that BSD and Linux use different init scripts. In BSD, your init script is this
one big monstrous file. In Linux, your init scripts are SysV-style, in which you have seven directories (/etc/rc[0-6].d) which
contain symlinks to files in a master directory (/etc/init.d).
While this is true of NetBSD 1.4.3, the upcoming NetBSD 1.5 release will contain an/etc/rc.d directory with smallish startup scripts where the order is dynamically determined at runtime based on "provide / require" statements in the scripts, and the startup of services are controlled by system-supplied defaults in/etc/defaults/rc.conf and system-specific settings in/etc/rc.conf. This mechanism makes it easier to "drop in" new startup scripts, and thus builds on the good features of the SysV startup system.
However, NetBSD 1.5 does not introduce the SysV runlevels -- this is IMHO a good thing, since the above mechanism allows for more flexibility. Your opinion may differ, of course.
Slashdot Mirror
If you know how to do the legwork, it's not all that hard to justify allocation of more IP addresses...
Oh, I'll have to disagree here; NetBSD 1.5 (even in the beta2 incarnation) is most definately a complete OS, and unless you start using the more experimental bits (unfortunately LFS still falls into that category), the risk of data loss due to file system corruption is miniscule and comparable to the risk of running NetBSD 1.4.3 or any of the other BSDs.
Perhaps a word or two about the difference between NetBSD 1.4.3 and NetBSD 1.5 is in order. The former (1.4.3) is first and foremost a bugfix release. Please note that the code branch was created quite a while ago, and even though some features have been imported from the main development branch, far from all features have received this treatment. NetBSD/i386 and sparc still use a.out as object format in 1.4.3.
On the other hand NetBSD 1.5 includes all the new features developed since the NetBSD 1.4 release was created, about May 1999. As with almost any piece of software, bugs are bound to exist, and there are obviously higher risk of finding bugs in the first version of a major release number (as with NetBSD 1.5), so if you wanted to be super-conservative you'd hold on until 1.5.1 was released. In NetBSD 1.5 the i386 and sparc ports have been converted to using the ELF object format.
In fact, the "beta" designation in NetBSD's releases really means "we think this is ready to ship, please test for any remaining minor glitches, so that we may fix those before the release goes out the door." (I'd still recommend to upgrade to the release version once it becomes available if you decide to test any of the beta versions.)
While this is true of NetBSD 1.4.3, the upcoming NetBSD 1.5 release will contain an /etc/rc.d directory with smallish startup scripts where the order is dynamically determined at runtime based on "provide / require" statements in the scripts, and the startup of services are controlled by system-supplied defaults in /etc/defaults/rc.conf and system-specific settings in /etc/rc.conf. This mechanism makes it easier to "drop in" new startup scripts, and thus builds on the good features of the SysV startup system.
However, NetBSD 1.5 does not introduce the SysV runlevels -- this is IMHO a good thing, since the above mechanism allows for more flexibility. Your opinion may differ, of course.