*Now* (was: Re:Well...not quite)
on
OpenBSD 3.1 Released
·
· Score: 5, Informative
Okay, now it's official. Here's the announcement:
To: announce@openbsd.org Subject: OpenBSD 3.1 Released! Date: Sun, 19 May 2002 15:03:44 -0600 From: "Todd C. Miller" <Todd.Miller@courtesan.com>
- OpenBSD 3.1 RELEASED -
May 19, 2002.
It is our pleasure to officially announce the release of OpenBSD 3.1. This year OpenBSD turns 7 years old. In celebration of this milestone, we invite you to enjoy our 11th release on CD-ROM (and 12th via FTP). We continue to celebrate OpenBSD's record of four years without a remote hole in the default install. Just like all of our previous releases, 3.1 provides significant improvements, including new features, in nearly all areas of the system:
- Improved hardware support (http://www.OpenBSD.org/plat.html)
o Much improved support for UltraSPARC hardware. More models are
supported and X11 works on all supported models.
o Improved 802.11b support, including a host-based access point
mode for Prism chipsets (i.e. wireless bridging). It is now
possible to completely configure a wireless interface using ifconfig.
o The hardware crypto drivers now work on all PCI platforms.
o Major macppc improvements including a brand new pmap module
that cut 'make build' time by over an hour.
o Tekram TRM-S1040 based PCI SCSI controllers are now supported.
o Creative SB Live! cards are now supported.
o HiFn 7811 is now supported by the hifn driver. A long-standing
bug causing PCI aborts has also been fixed in the hifn driver.
o Kernel support for Altivec on the macppc platform.
- Major improvements in the pf packet filter:
o Significant performance improvements due to additional optimizations
based on detailed benchmarks. Filter rule evaluation cost
(which occurs for every packet that isn't passed statefully)
is reduced by about 70%.
o Stateful filtering (including address translation and redirection)
for arbitrary IP protocols other than TCP, UDP and ICMP, for
instance GRE (used for IPsec/PPTP).
o Configurable memory limits (preventing memory exhaustion).
'pfctl -m' can set an upper bound on the number of simultaneous
states or fragments.
o authpf(8), an authenticating gateway user shell, modifies filter
rules when a user logs in, controlling network access at the user
level.
o New 'fastroute', 'route-to' and 'dup-to' options allow pf to
route packets independently of the system routing table. This
can be used to e.g., implement source-based routing or to
duplicate packets to an IDS or logging host.
o Parser improvements allow further reduction of rule set complexity
('no nat', rdr port ranges, and more).
o Rule labels simplify usage of counters for accounting ('pass in
from any to any port www label http_requests').
o The 'no-route' keyword in filter rules matches packets with non-
routable addresses. E.g., 'block in quick from no-route to any'
blocks packets from non-routable source addresses.
o tcpdump(8) expressions can filter pf logs on pf-specific fields.
E.g. 'tcpdump -i pflog0 action block' prints only blocked packets.
o Additional ioctls for adding and removing state entries (used by
proxies, authpf(8) and pfctl(8)).
o More fixes for potential signal handler races. Work is ongoing in
this area to fix the signal handlers in all programs, not just
privileged ones.
o sshd now supports a privilege separation mode where all incoming
network traffic takes place in an unprivileged process.
o A number of memory leaks that could lead to denial of service
attacks have been plugged.
o Several other security issues fixed throughout the system, many
of which were identified by members of the OpenBSD team themselves.
Please see http://www.OpenBSD.org/errata30.html for more details
on what was fixed.
- New subsystems included with 3.1
o A version of the venerable spell program is now included.
o Generic macros for manipulating splay trees and red-black trees.
o Support for extended attributes in the filesystem.
- Many other bugs fixed (http://www.OpenBSD.org/plus30.html)
- The "ports" tree is greatly improved (http://www.OpenBSD.org/ports.html)
o The 3.1 CD-ROMs ship with many more pre-built packages for the
common architectures. The FTP site contains hundreds more
packages (for the important architectures) which we could not
fit onto the CD-ROMs.
- Many subsystems improved and updated since the last release:
o A long-standing bug in the i386 MBR that caused a hang on boot
with some machines has been fixed.
o Better sizing of kernel buffers, based on amount physical memory.
o Other memory-related limits are tunable without recompiling a
lernel via config -e.
o Improved behavior of the virtual memory system in low-memory
situations.
o ALTQ is supported by more ethernet drivers and now works on
bridged interfaces.
o Loadable kernel modules are now supported on ELF platforms.
o The 2 gigabyte file size limit has been removed from mmap(2),
vnd(4), savecore(8), dump(8), restore(8), and rcp(1).
o XFree86 updated to 4.2.0.
o sendmail updated to 8.12.2.
o Latest KAME IPv6
o KTH Heimdal-0.4e
o OpenSSH 3.2
If you'd like to see a list of what has changed between OpenBSD 3.0 and 3.1, look at
http://www.OpenBSD.org/plus31.html
Even though the list is a summary of the most important changes made to OpenBSD, it still is a very very long list.
This is our twelfth OpenBSD release, and the eleventh release which is available on CD-ROM. Our releases have been spaced six months apart, and we plan to continue this timing.
- SECURITY AND ERRATA
We provide patches for known security threats and other important issues discovered after each CD release. As usual, between the creation of the OpenBSD 3.1 FTP/CD-ROM binaries and the actual 3.1 release date, our team found and fixed some new reliability problems (note: most are minor, and in subsystems that are not enabled by default). Our continued research into security means we will find new security problems and we always provide patches as soon as possible. Therefore, we advise regular visits to
http://www.OpenBSD.org/security.html and
http://www.OpenBSD.org/errata.html
Security patch announcements are sent to the security-announce@OpenBSD.org mailing list. For information on OpenBSD mailing lists, please see:
http://www.OpenBSD.org/mail.html
- CD-ROM SALES
OpenBSD 3.1 is also available on CD-ROM. The 3-CD set costs $40USD (EUR 45) and is available via mail order and from a number of contacts around the world. The set includes a colorful booklet which carefully explains the installation of OpenBSD. A new set of cute little stickers are also included (sorry, but our FTP mirror sites do not support STP, the Sticker Transfer Protocol). As an added bonus, the second CD contains an exclusive audio track by Ty Semaka, http://www.thedevils.com/.
Profits from CD sales are the primary income source for the OpenBSD project in essence selling these CD-ROM units ensures that OpenBSD will continue to make another release six months from now.
The OpenBSD 3.1 CD-ROMs are bootable on the following six platforms:
o i386
o alpha
o sparc
o sparc64 (UltraSPARC)
o macppc
o hp300*
* The m68k-based platforms, including hp300, are located on a fourth
CD that is not included in the official CD-ROM package. You can
download the ISO image for the fourth CD as described below.
(Other platforms must boot from floppy, network, or other method).
For more information on ordering CD-ROMs, see:
http://www.OpenBSD.org/orders.html
The above web page lists a number of places where OpenBSD CD-ROMs can be purchased from. For our default mail order, go directly to:
https://https.OpenBSD.org/cgi-bin/order
or, for European orders:
https://https.OpenBSD.org/cgi-bin/order.eu
All of our developers strongly urge you to buy a CD-ROM and support our future efforts. As well, donations to the project are highly appreciated, as described in more detail at:
http://www.OpenBSD.org/goals.html#funding
Due to space restrictions and our desire not to raise the cost of the CD-ROM, the Motorola 68k-based platforms are located on a fourth CD that is not included in the official CD-ROM package. An ISO image for this CD may be downloaded from:
ftp://ftp.openbsd.org/pub/OpenBSD-ISO/3.1-CD4.iso
This CD contains the amiga, hp300, mac68k and mvme68k install sets as well as the m68k packages. The CD is bootable on the hp300. Note that not all ftp mirrors will carry the CD image.
- T-SHIRT SALES
The project continues to expand its funding base by selling t-shirts and polo shirts. And our users like them too. We have a variety of shirts available, with the new and old designs, from our web ordering system at:
https://https.OpenBSD.org/cgi-bin/order
The new 3.1 t-shirt is not available at this time but will be available shortly.
- FTP INSTALLS -
If you choose not to buy an OpenBSD CD-ROM, OpenBSD can be easily installed via FTP. Typically you need a single small piece of boot media (e.g., a boot floppy) and then the rest of the files can be installed from a number of locations, including directly off the Internet. Follow this simple set of instructions to ensure that you find all of the documentation you will need while performing an install via FTP. With the CD-ROMs, the necessary documentation is easier to find.
1) Read either of the following two files for a list of ftp
mirrors which provide OpenBSD, then choose one near you:
2) Connect to that ftp mirror site and go into the directory
pub/OpenBSD/3.1/ which contains these files and directories.
This is a list of what you will see:
It is quite likely that you will want at LEAST the following
files which apply to all the architectures OpenBSD supports.
README - generic README
HARDWARE - list of hardware we support
PORTS - description of our "ports" tree
PACKAGES - description of pre-compiled packages
root.mail - a copy of root's mail at initial login.
(This is really worthwhile reading).
3) Read the README file. It is short, and a quick read will make
sure you understand what else you need to fetch.
4) Next, go into the directory that applies to your architecture,
for example, i386. This is a list of what you will see:
If you are new to OpenBSD, fetch _at least_ the file INSTALL.i386
and the appropriate floppy*.fs file. Consult the INSTALL.i386
file if you don't know which of the floppy images you need (or
simply fetch all of them).
5) If you are an expert, follow the instructions in the file called
README; otherwise, use the more complete instructions in the
file called INSTALL.i386. INSTALL.i386 may tell you that you
need to fetch other files.
6) Just in case, take a peek at:
http://www.OpenBSD.org/errata.html
This is the page where we talk about the mistakes we made while
creating the 3.1 release, or the significant bugs we fixed
post-release which we think our users should have fixes for.
Patches and workarounds are clearly described there.
Note: If you end up needing to write a raw floppy using Windows,
you can use "fdimage.exe" located in the pub/OpenBSD/3.1/tools
directory to do so.
- XFree86 FOR MOST ARCHITECTURES -
XFree86 has been integrated more closely into the system. This release contains XFree86 4.2.0. Most of our architectures ship with XFree86, including sparc, sparc64 and macppc. During installation, you can install XFree86 quite easily. Be sure to try out xdm(1) and see how we have customized it for OpenBSD.
On the i386 platform a few older X servers are included from XFree86 3.3.6. These can be used for cards that are not supported by XFree86 4.2.0 or where XFree86 4.2.0 support is buggy. Please read the /usr/X11R6/README file for post-installation information.
- PORTS TREE -
The OpenBSD ports tree contains automated instructions for building third party software. The software has been verified to build and run on the various OpenBSD architectures. The 3.1 ports collection, including many of the distribution files, is included on the 3-CD set. Please see PORTS file for more information.
Note: some of the most popular ports, e.g., the Apache web server and several X applications, come standard with OpenBSD. Also, many popular ports have been pre-compiled for those who do not desire to build their own binaries (see PACKAGES, below).
- BINARY PACKAGES WE PROVIDE -
A large number of binary packages are provided. Please see PACKAGES file (ftp://ftp.OpenBSD.org/pub/OpenBSD/PACKAGES) for more details.
- SYSTEM SOURCE CODE -
The CD-ROMs contain source code for all the subsystems explained above, and the README (ftp://ftp.OpenBSD.org/pub/OpenBSD/README) file explains how to deal with these source files. For those who are doing an FTP install, the source code for all four subsystems can be found in the pub/OpenBSD/3.1/ directory:
XF4.tar.gz ports.tar.gz src.tar.gz srcsys.tar.gz
- THANKS -
OpenBSD 3.1 includes artwork and CD artistic layout by Ty Semaka, who also is featured in an audio track on the OpenBSD 3.1 CD set. Ports tree and package building by Christian Weisgerber, David Lebel, Marc Espie, Peter Valchev and Miod Vallat. System builds by Theo de Raadt, Niklas Hallqvist, Todd Fries and Bob Beck. ISO-9660 filesystem layout by Theo de Raadt.
We would like to thank all of the people who sent in bug reports, bug fixes, donation cheques, and hardware that we use. We would also like to thank those who pre-ordered the 3.1 CD-ROM or bought our previous CD-ROMs. Those who did not support us financially have still helped us with our goal of improving the quality of the software.
Our developers are:
Aaron Campbell, Angelos D. Keromytis, Anil Madhavapeddy, Artur Grabowski,
Ben Lindstrom, Bob Beck, Brad Smith, Brandon Creighton, Brian Caswell,
Brian Somers, Bruno Rohee, Camiel Dobbelaar, Chris Cappuccio,
Christian Weisgerber, Constantine Sapuntzakis, Dale Rahn, Damien Miller,
Dan Harnett, Daniel Hartmeier, David B Terrell, David Lebel,
David Leonard, Dug Song, Eric Jackson, Federico G. Schwindt,
Grigoriy Orlov, Hakan Olsson, Hans Insulander, Heikki Korpela,
Horacio Menezo Ganau, Hugh Graham, Ian Darwin, Jakob Schlyter,
Jan-Uwe Finck, Jason Ish, Jason Peel, Jason Wright, Jean-Baptiste Marchand,
Jean-Jacques Bernard-Gundol, Jim Rees, Joshua Stein,
Jun-ichiro itojun Hagino, Kenjiro Cho, Kenneth R Westerback,
Kevin Lo, Kevin Steves, Kjell Wooding, Louis Bertrand, Marc Espie,
Marco S Hyman, Mark Grimes, Markus Friedl, Mats O Jansson, Matt Behrens,
Matt Smart, Matthew Jacob, Matthieu Herrb, Michael Shalayeff,
Michael T. Stolarchuk, Mike Frantzen, Mike Pechkin, Miod Vallat
Nathan Binkert, Nick Holland, Niels Provos, Niklas Hallqvist,
Oleg Safiullin, Paul Janzen, Peter Galbavy, Peter Stromberg,
Peter Valchev, Reinhard J. Sammer, Shell Hin-lik Hung, Steve Murphree,
Thierry Deval, Theo de Raadt, Thorsten Lockert, Tobias Weingartner,
Todd C. Miller, Todd T. Fries, Wim Vandeputte.
I wonder why there isn't any ISO images to download. I mean for someone who doesn't have credit card and live far away from North America, ISO images seems like the best alternative.
CD sales are a prime source of income for OpenBSD; you'll never see an official OpenBSD ISO image legally available for download.
Having said that, an ISO image really isn't necessary. You can download a floppy image and use that to do an install directly via FTP. Rather than ~600 Mbytes to transfer for an ISO, you'll only have to grab about 120 Mbytes for a full install.
Re:How fast a computer needed?
on
OpenBSD 3.1 Released
·
· Score: 5, Informative
Quoth baywuulf:
I have an old Pentium 166 w/ 64MB and S3 virge video card lying around which I might use to play around with this stuff. Assuming no X Windows, will this be adequate to run OpenBSD without swapping to the harddrive much?
OpenBSD will run just fine on this computer. monk.trumpetpower.com is running on basically that same platform, and it's never given me a hint of trouble. Not that it or my DSL would likely survive a slashdotting, but....
My laptop is a Pentium 120 with 72 Mbytes RAM. I run Konqueror and Netscape under Windowmaker on it all the time. Sure, it's not a blazing speed daemon, but it's quite useable. And it's great to take onsite--I've got Apache, a DHCP server, lots more running on a machine I can tuck under my arm. I can max out a 100 Mbit Ethernet link with Apache, which actually makes the laptop a bit more convenient in some cases than a CD for transfering files.
To: Ben Goren <ben@trumpetpower.com>
Cc: misc@openbsd.org
Subject: Re: Are we there yet?
Date: Sun, 19 May 2002 11:26:07 -0600
From: "Todd C. Miller" <Todd.Miller@courtesan.com>
In message <20020519101502.O11398@trumpetpower.com>
so spake Ben Goren (ben):
> So, are we there yet? Are we there yet? Huh? Huh? Are we there
> yet?
The files have been transferring to the main ftp mirror since last
night. Once that is done they will move to the secondary mirrors
and the email announcement will be sent out.
$1,800,000,000 / 12 = $150,000,000. The U.S. population is somewhere around 300,000,000. About half of all Americans have Internet access. 50% of 300,000,000 is 150,000,000. So, yes, $1/month/customer =~ $2B/year.
Having said that, no audio file has crossed my router that wasn't perfectly legitimate, and I don't mean ``well, I'm gonna buy the CD, anyway.'' The RIAA is scum and its executives should be thrown in jail as the corrupt rackettering thugs that they are, but I'm not willing to ``subsidize'' something that I'm not using.
And who's to say that this new scheme won't be just as bad as what we now have with the RIAA?
Go to concerts. Buy knick-knacks. Break copyright laws if you must, but accept the consequences--be willing to pay fines or go to jail over that downloaded MP3 or warezed Photoshop when you get caught. Lobby your lawmakers and educate your friends.
I'll pay for my own entertainment. Don't make me pay for your yours.
If someody were to develop some amazing new casette tape that didn't work on a subset of casette players, that would be okay. If that tape, instead, destroyed the player into which it was inserted by chewing up the playback heads, that would not be okay, even if it came with a label saying, ``Not for use on foo tape decks.''
uh, ok. $1 a piece for a.1 watt bulb. sounds great. Exactly how many would I have to gang to be able to read my newspaper?
Because, while that bulb only consumes 0.1 W, it gives off as much light as a much brighter incandescant bulb. I didn't see figures in the article, but one would figure that it's better than what you get with flourescent lights.
I've replaced many of the lights in my apartment with compact flourescents. Typically, a CF bulb that outputs as many lumens as a 100 W incandescant bulb will only require 20 - 30 W. Reading a newspaper with a 20 W incandescant isn't practical, but the 20 W CF is more than bright enough.
Why limit something like this to the developing world? If the developed world used low-power, high-efficiency lighting, we'd dramatically reduce the consumption of energy and non-renewable resources. If these lights are cheap enough for the poorest on the planet to consider using them, there's no doubt that they'd save the industrialized nations amazing amounts of money, as well.
Frankly, I suspect we'd do more for the developing world by adopting this sort of thing for ourselves--which is not to say, of course, that we shouldn't encourage them to skip our wasteful ways in favor of the right way to do things.
The USB daughterboard is easily identified and is clearly labeled with a "Warning: this card is not removable" marking. All you do is unscrew the screws holding the USB card to the back of the case, pry up the double-sided tape that's holding it down, and slide the USB card out the back of the satmodem case.
*waves hand* This is not the daughterboard you're looking for.
While this may be a valid argument, it does not provide a legislative alternative (something which many on Capitol Hill are scratching for).
Just because you've got an itch doesn't mean that you should scratch it.
There is no need for additional laws, and the idea of ``net cops'' is sheer lunacy compounded with totalitarinism. If a copyright owner doesn't like what somebody's doing with the copyrighted work, let that owner deal wiith it. The {RI,MP}AA can waste their own dollars chasing honest citizens who're acting in concert with the Constitution and ignoring unconsitutional laws.
If you really want to tell your representatives what law to pass, tell them to pass a law repealing the DMCA and the Bono act.
What happens on the file trading networks isn't a crime. What is a crime is that the Scottsdale Symphony can't afford to perform Maurice Ravel's Bolero (you know, the Bo Derek piece) because, thanks to Sonny Bono, it's back under copyright.
This isn't significantly different from the militarizaton of space. China has space launch capabilities, and it doesn't take more than simple collision to destroy a satellite. Yet I don't worry about China (or anybody else) knocking US (or anybody else's) satellites out of the sky.
Why? Because an attack on our satellites would be no different from, say, offshore planes or ships jamming radio signals, or, for that matter, a bunch of commandoes blowing up inland transmission towers. It's a potentially devastating move, but it's also unquestionably an attack on the US and an obvious precursor to invasion or nuclear attack.
A concerted attack on the Internet, and especially on Amereican military computers that are connected to the Internet, is every bit the act of war as are the other scenarios.
Folks, the Chinese are not stupid. For all the sabre-rattling Beijing might do (and let's not forget that Washington's swords are pretty noisy, themselves), they're not about to commit species suicide anytime soon. MAD aside, China is no match for the US militarily in an all-out war, and that's what we've promised if they invade Taiwan. They might not like it, but they know it.
Should the military take steps to protect themselves against such an attack? Of course. But the rest of us shouldn't worry about it any more than we worry about CNN going off the air due to military action.
If any of my browsers succumb to Ooqa Ooqa, I'll have the owner of that site prosecuted under the PATRIOT act.
Either the scumbag who tries to pull off these kinds of things goes to jail for terroristic computer hacking or the PATRIOT act gets struck down. Either way, I win.
*sigh* The lameness filter aparently doesn't belive in conciseness. Therefore, the quick brown fox jumps over the lazy dog and now is the time for all good people to come to the aid of their country.
If you were to invest $230/month at a 10% annual rate, compounded annually, from the time you were 20 to the time you were 65, you'd have two million dollars in the bank.
So, which would you rather have: AOL's ultimate media package, or multiple millions in the bank when you retired?
For what it's worth, when I first read that story (it could be Have Space Suit, Will Travel, but I'm not sure, either), my first reaction was something like, ``yeah, sure, like that'll happen any time soon.'' It must have been the early eighties. A big part of the thought was that telephones were nothing like CB or walkie-talkies, and the idea of having a handheld two-way radio with its own unique telephone number just didn't seem feasible.
Keep in mind that, at that time, wireless was broadcast-only and wired was point-to-point only...and that I probably wasn't yet a teenager.
Heinlein, especially in his early years, is full of technology that is commonplace today that was pie-in-the-sky when he wrote it. He just didn't always call it by the same names we do today.
I'd have to go digging for specific technologies in specific titles, but it's all good-to-great reading anyway.
Expect to find mobile phones, faxes, video phones, voice dictation, computers of various intelligences, maglev, flywheels for energy storage (we use 'em as a UPS in datacenters; he used 'em in spaceships), sophisticated chemical synthesis (Venusians making real maple syrup from a sample), all sorts of rocketry and space tech, and lots more.
Also good is Niven, though more of his things (such as matter transporters and indestructible ship hulls) are still in the distant future. Zahn likes to take some form of technology, such as $6M-Man-like soldiers (Cobra et al.) and see what it might do to people and society--you get a chapter or two of a space western and the rest of the book of social analysis and commentary.
Sounds like a fun project, if for no other reason than the reading list!
Slashdot Mirror
Okay, now it's official. Here's the announcement:
To: announce@openbsd.org
Subject: OpenBSD 3.1 Released!
Date: Sun, 19 May 2002 15:03:44 -0600
From: "Todd C. Miller" <Todd.Miller@courtesan.com>
- OpenBSD 3.1 RELEASED -
May 19, 2002.
It is our pleasure to officially announce the release of OpenBSD
3.1. This year OpenBSD turns 7 years old. In celebration of this
milestone, we invite you to enjoy our 11th release on CD-ROM (and
12th via FTP). We continue to celebrate OpenBSD's record of four
years without a remote hole in the default install. Just like all
of our previous releases, 3.1 provides significant improvements,
including new features, in nearly all areas of the system:
- Improved hardware support (http://www.OpenBSD.org/plat.html)
o Much improved support for UltraSPARC hardware. More models are
supported and X11 works on all supported models.
o Improved 802.11b support, including a host-based access point
mode for Prism chipsets (i.e. wireless bridging). It is now
possible to completely configure a wireless interface using ifconfig.
o The hardware crypto drivers now work on all PCI platforms.
o Major macppc improvements including a brand new pmap module
that cut 'make build' time by over an hour.
o Tekram TRM-S1040 based PCI SCSI controllers are now supported.
o Creative SB Live! cards are now supported.
o HiFn 7811 is now supported by the hifn driver. A long-standing
bug causing PCI aborts has also been fixed in the hifn driver.
o Kernel support for Altivec on the macppc platform.
- Major improvements in the pf packet filter:
o Significant performance improvements due to additional optimizations
based on detailed benchmarks. Filter rule evaluation cost
(which occurs for every packet that isn't passed statefully)
is reduced by about 70%.
o Stateful filtering (including address translation and redirection)
for arbitrary IP protocols other than TCP, UDP and ICMP, for
instance GRE (used for IPsec/PPTP).
o Configurable memory limits (preventing memory exhaustion).
'pfctl -m' can set an upper bound on the number of simultaneous
states or fragments.
o authpf(8), an authenticating gateway user shell, modifies filter
rules when a user logs in, controlling network access at the user
level.
o New 'fastroute', 'route-to' and 'dup-to' options allow pf to
route packets independently of the system routing table. This
can be used to e.g., implement source-based routing or to
duplicate packets to an IDS or logging host.
o Parser improvements allow further reduction of rule set complexity
('no nat', rdr port ranges, and more).
o Rule labels simplify usage of counters for accounting ('pass in
from any to any port www label http_requests').
o The 'no-route' keyword in filter rules matches packets with non-
routable addresses. E.g., 'block in quick from no-route to any'
blocks packets from non-routable source addresses.
o tcpdump(8) expressions can filter pf logs on pf-specific fields.
E.g. 'tcpdump -i pflog0 action block' prints only blocked packets.
o Additional ioctls for adding and removing state entries (used by
proxies, authpf(8) and pfctl(8)).
- Ever-improving security (http://www.OpenBSD.org/security.html)
o More fixes for potential signal handler races. Work is ongoing in
this area to fix the signal handlers in all programs, not just
privileged ones.
o sshd now supports a privilege separation mode where all incoming
network traffic takes place in an unprivileged process.
o A number of memory leaks that could lead to denial of service
attacks have been plugged.
o Several other security issues fixed throughout the system, many
of which were identified by members of the OpenBSD team themselves.
Please see http://www.OpenBSD.org/errata30.html for more details
on what was fixed.
- New subsystems included with 3.1
o A version of the venerable spell program is now included.
o Generic macros for manipulating splay trees and red-black trees.
o Support for extended attributes in the filesystem.
- Many other bugs fixed (http://www.OpenBSD.org/plus30.html)
- The "ports" tree is greatly improved (http://www.OpenBSD.org/ports.html)
o The 3.1 CD-ROMs ship with many more pre-built packages for the
common architectures. The FTP site contains hundreds more
packages (for the important architectures) which we could not
fit onto the CD-ROMs.
- Many subsystems improved and updated since the last release:
o A long-standing bug in the i386 MBR that caused a hang on boot
with some machines has been fixed.
o Better sizing of kernel buffers, based on amount physical memory.
o Other memory-related limits are tunable without recompiling a
lernel via config -e.
o Improved behavior of the virtual memory system in low-memory
situations.
o ALTQ is supported by more ethernet drivers and now works on
bridged interfaces.
o Loadable kernel modules are now supported on ELF platforms.
o The 2 gigabyte file size limit has been removed from mmap(2),
vnd(4), savecore(8), dump(8), restore(8), and rcp(1).
o XFree86 updated to 4.2.0.
o sendmail updated to 8.12.2.
o Latest KAME IPv6
o KTH Heimdal-0.4e
o OpenSSH 3.2
If you'd like to see a list of what has changed between OpenBSD 3.0
and 3.1, look at
http://www.OpenBSD.org/plus31.html
Even though the list is a summary of the most important changes
made to OpenBSD, it still is a very very long list.
This is our twelfth OpenBSD release, and the eleventh release which
is available on CD-ROM. Our releases have been spaced six months
apart, and we plan to continue this timing.
- SECURITY AND ERRATA
We provide patches for known security threats and other important
issues discovered after each CD release. As usual, between the
creation of the OpenBSD 3.1 FTP/CD-ROM binaries and the actual 3.1
release date, our team found and fixed some new reliability problems
(note: most are minor, and in subsystems that are not enabled by
default). Our continued research into security means we will find
new security problems and we always provide patches as soon as
possible. Therefore, we advise regular visits to
http://www.OpenBSD.org/security.html
and
http://www.OpenBSD.org/errata.html
Security patch announcements are sent to the security-announce@OpenBSD.org
mailing list. For information on OpenBSD mailing lists, please see:
http://www.OpenBSD.org/mail.html
- CD-ROM SALES
OpenBSD 3.1 is also available on CD-ROM. The 3-CD set costs $40USD
(EUR 45) and is available via mail order and from a number of
contacts around the world. The set includes a colorful booklet
which carefully explains the installation of OpenBSD. A new set
of cute little stickers are also included (sorry, but our FTP mirror
sites do not support STP, the Sticker Transfer Protocol). As an
added bonus, the second CD contains an exclusive audio track by Ty
Semaka, http://www.thedevils.com/.
Profits from CD sales are the primary income source for the OpenBSD
project in essence selling these CD-ROM units ensures that OpenBSD
will continue to make another release six months from now.
The OpenBSD 3.1 CD-ROMs are bootable on the following six platforms:
o i386
o alpha
o sparc
o sparc64 (UltraSPARC)
o macppc
o hp300*
* The m68k-based platforms, including hp300, are located on a fourth
CD that is not included in the official CD-ROM package. You can
download the ISO image for the fourth CD as described below.
(Other platforms must boot from floppy, network, or other method).
For more information on ordering CD-ROMs, see:
http://www.OpenBSD.org/orders.html
The above web page lists a number of places where OpenBSD CD-ROMs
can be purchased from. For our default mail order, go directly to:
https://https.OpenBSD.org/cgi-bin/order
or, for European orders:
https://https.OpenBSD.org/cgi-bin/order.eu
All of our developers strongly urge you to buy a CD-ROM and support
our future efforts. As well, donations to the project are highly
appreciated, as described in more detail at:
http://www.OpenBSD.org/goals.html#funding
Due to space restrictions and our desire not to raise the cost of
the CD-ROM, the Motorola 68k-based platforms are located on a
fourth CD that is not included in the official CD-ROM package.
An ISO image for this CD may be downloaded from:
ftp://ftp.openbsd.org/pub/OpenBSD-ISO/3.1-CD4.iso
This CD contains the amiga, hp300, mac68k and mvme68k install sets
as well as the m68k packages. The CD is bootable on the hp300.
Note that not all ftp mirrors will carry the CD image.
- T-SHIRT SALES
The project continues to expand its funding base by selling t-shirts
and polo shirts. And our users like them too. We have a variety
of shirts available, with the new and old designs, from our web
ordering system at:
https://https.OpenBSD.org/cgi-bin/order
The new 3.1 t-shirt is not available at this time but will be
available shortly.
- FTP INSTALLS -
If you choose not to buy an OpenBSD CD-ROM, OpenBSD can be easily
installed via FTP. Typically you need a single small piece of boot
media (e.g., a boot floppy) and then the rest of the files can be
installed from a number of locations, including directly off the
Internet. Follow this simple set of instructions to ensure that
you find all of the documentation you will need while performing
an install via FTP. With the CD-ROMs, the necessary documentation
is easier to find.
1) Read either of the following two files for a list of ftp
mirrors which provide OpenBSD, then choose one near you:
http://www.OpenBSD.org/ftp.html
ftp://ftp.OpenBSD.org/pub/OpenBSD/3.1/ftplist
2) Connect to that ftp mirror site and go into the directory
pub/OpenBSD/3.1/ which contains these files and directories.
This is a list of what you will see:
Changelogs/ alpha/ macppc/ sparc64/
HARDWARE amiga/ mvme68k/ src.tar.gz
PACKAGES ftplist packages/ srcsys.tar.gz
PORTS hp300/ ports.tar.gz tools/
README i386/ root.mail vax/
XF4.tar.gz mac68k/ sparc/
It is quite likely that you will want at LEAST the following
files which apply to all the architectures OpenBSD supports.
README - generic README
HARDWARE - list of hardware we support
PORTS - description of our "ports" tree
PACKAGES - description of pre-compiled packages
root.mail - a copy of root's mail at initial login.
(This is really worthwhile reading).
3) Read the README file. It is short, and a quick read will make
sure you understand what else you need to fetch.
4) Next, go into the directory that applies to your architecture,
for example, i386. This is a list of what you will see:
CKSUM INSTALL.os2br comp31.tgz man31.tgz
INSTALL.ata INSTALL.pt etc31.tgz misc31.tgz
INSTALL.chs MD5 floppy31.fs xbase31.tgz
INSTALL.dbr base31.tgz floppyB31.fs xfont31.tgz
INSTALL.i386 bsd floppyC31.fs xserv31.tgz
INSTALL.linux bsd.rd game31.tgz xshare31.tgz
INSTALL.mbr cdrom31.fs index.txt
If you are new to OpenBSD, fetch _at least_ the file INSTALL.i386
and the appropriate floppy*.fs file. Consult the INSTALL.i386
file if you don't know which of the floppy images you need (or
simply fetch all of them).
5) If you are an expert, follow the instructions in the file called
README; otherwise, use the more complete instructions in the
file called INSTALL.i386. INSTALL.i386 may tell you that you
need to fetch other files.
6) Just in case, take a peek at:
http://www.OpenBSD.org/errata.html
This is the page where we talk about the mistakes we made while
creating the 3.1 release, or the significant bugs we fixed
post-release which we think our users should have fixes for.
Patches and workarounds are clearly described there.
Note: If you end up needing to write a raw floppy using Windows,
you can use "fdimage.exe" located in the pub/OpenBSD/3.1/tools
directory to do so.
- XFree86 FOR MOST ARCHITECTURES -
XFree86 has been integrated more closely into the system. This
release contains XFree86 4.2.0. Most of our architectures ship
with XFree86, including sparc, sparc64 and macppc. During installation,
you can install XFree86 quite easily. Be sure to try out xdm(1)
and see how we have customized it for OpenBSD.
On the i386 platform a few older X servers are included from XFree86
3.3.6. These can be used for cards that are not supported by XFree86
4.2.0 or where XFree86 4.2.0 support is buggy. Please read the
/usr/X11R6/README file for post-installation information.
- PORTS TREE -
The OpenBSD ports tree contains automated instructions for building
third party software. The software has been verified to build and
run on the various OpenBSD architectures. The 3.1 ports collection,
including many of the distribution files, is included on the 3-CD
set. Please see PORTS file for more information.
Note: some of the most popular ports, e.g., the Apache web server
and several X applications, come standard with OpenBSD. Also, many
popular ports have been pre-compiled for those who do not desire
to build their own binaries (see PACKAGES, below).
- BINARY PACKAGES WE PROVIDE -
A large number of binary packages are provided. Please see PACKAGES
file (ftp://ftp.OpenBSD.org/pub/OpenBSD/PACKAGES) for more details.
- SYSTEM SOURCE CODE -
The CD-ROMs contain source code for all the subsystems explained
above, and the README (ftp://ftp.OpenBSD.org/pub/OpenBSD/README)
file explains how to deal with these source files. For those who
are doing an FTP install, the source code for all four subsystems
can be found in the pub/OpenBSD/3.1/ directory:
XF4.tar.gz ports.tar.gz src.tar.gz srcsys.tar.gz
- THANKS -
OpenBSD 3.1 includes artwork and CD artistic layout by Ty Semaka,
who also is featured in an audio track on the OpenBSD 3.1 CD set.
Ports tree and package building by Christian Weisgerber, David Lebel,
Marc Espie, Peter Valchev and Miod Vallat.
System builds by Theo de Raadt, Niklas Hallqvist, Todd Fries and Bob Beck.
ISO-9660 filesystem layout by Theo de Raadt.
We would like to thank all of the people who sent in bug reports, bug
fixes, donation cheques, and hardware that we use. We would also like
to thank those who pre-ordered the 3.1 CD-ROM or bought our previous
CD-ROMs. Those who did not support us financially have still helped
us with our goal of improving the quality of the software.
Our developers are:
Aaron Campbell, Angelos D. Keromytis, Anil Madhavapeddy, Artur Grabowski,
Ben Lindstrom, Bob Beck, Brad Smith, Brandon Creighton, Brian Caswell,
Brian Somers, Bruno Rohee, Camiel Dobbelaar, Chris Cappuccio,
Christian Weisgerber, Constantine Sapuntzakis, Dale Rahn, Damien Miller,
Dan Harnett, Daniel Hartmeier, David B Terrell, David Lebel,
David Leonard, Dug Song, Eric Jackson, Federico G. Schwindt,
Grigoriy Orlov, Hakan Olsson, Hans Insulander, Heikki Korpela,
Horacio Menezo Ganau, Hugh Graham, Ian Darwin, Jakob Schlyter,
Jan-Uwe Finck, Jason Ish, Jason Peel, Jason Wright, Jean-Baptiste Marchand,
Jean-Jacques Bernard-Gundol, Jim Rees, Joshua Stein,
Jun-ichiro itojun Hagino, Kenjiro Cho, Kenneth R Westerback,
Kevin Lo, Kevin Steves, Kjell Wooding, Louis Bertrand, Marc Espie,
Marco S Hyman, Mark Grimes, Markus Friedl, Mats O Jansson, Matt Behrens,
Matt Smart, Matthew Jacob, Matthieu Herrb, Michael Shalayeff,
Michael T. Stolarchuk, Mike Frantzen, Mike Pechkin, Miod Vallat
Nathan Binkert, Nick Holland, Niels Provos, Niklas Hallqvist,
Oleg Safiullin, Paul Janzen, Peter Galbavy, Peter Stromberg,
Peter Valchev, Reinhard J. Sammer, Shell Hin-lik Hung, Steve Murphree,
Thierry Deval, Theo de Raadt, Thorsten Lockert, Tobias Weingartner,
Todd C. Miller, Todd T. Fries, Wim Vandeputte.
Quoth SpikyTux:
CD sales are a prime source of income for OpenBSD; you'll never see an official OpenBSD ISO image legally available for download.
Having said that, an ISO image really isn't necessary. You can download a floppy image and use that to do an install directly via FTP. Rather than ~600 Mbytes to transfer for an ISO, you'll only have to grab about 120 Mbytes for a full install.
More details can be found here.
Quoth Sits:
If you like your uptime, have a look here.
b&
Quoth baywuulf:
OpenBSD will run just fine on this computer. monk.trumpetpower.com is running on basically that same platform, and it's never given me a hint of trouble. Not that it or my DSL would likely survive a slashdotting, but....
My laptop is a Pentium 120 with 72 Mbytes RAM. I run Konqueror and Netscape under Windowmaker on it all the time. Sure, it's not a blazing speed daemon, but it's quite useable. And it's great to take onsite--I've got Apache, a DHCP server, lots more running on a machine I can tuck under my arm. I can max out a 100 Mbit Ethernet link with Apache, which actually makes the laptop a bit more convenient in some cases than a CD for transfering files.
b&
3.1 still hasn't been officially announced:
So, check back soon.
b&
In that case, would you mind buying a nuclear power plant and a Space Shuttle?
b&
Your math is FUBAR.
$1,800,000,000 / 12 = $150,000,000. The U.S. population is somewhere around 300,000,000. About half of all Americans have Internet access. 50% of 300,000,000 is 150,000,000. So, yes, $1/month/customer =~ $2B/year.
Having said that, no audio file has crossed my router that wasn't perfectly legitimate, and I don't mean ``well, I'm gonna buy the CD, anyway.'' The RIAA is scum and its executives should be thrown in jail as the corrupt rackettering thugs that they are, but I'm not willing to ``subsidize'' something that I'm not using.
And who's to say that this new scheme won't be just as bad as what we now have with the RIAA?
Go to concerts. Buy knick-knacks. Break copyright laws if you must, but accept the consequences--be willing to pay fines or go to jail over that downloaded MP3 or warezed Photoshop when you get caught. Lobby your lawmakers and educate your friends.
I'll pay for my own entertainment. Don't make me pay for your yours.
b&
If someody were to develop some amazing new casette tape that didn't work on a subset of casette players, that would be okay. If that tape, instead, destroyed the player into which it was inserted by chewing up the playback heads, that would not be okay, even if it came with a label saying, ``Not for use on foo tape decks.''
Celine has done the latter.
b&
Because, while that bulb only consumes 0.1 W, it gives off as much light as a much brighter incandescant bulb. I didn't see figures in the article, but one would figure that it's better than what you get with flourescent lights.
I've replaced many of the lights in my apartment with compact flourescents. Typically, a CF bulb that outputs as many lumens as a 100 W incandescant bulb will only require 20 - 30 W. Reading a newspaper with a 20 W incandescant isn't practical, but the 20 W CF is more than bright enough.
b&
Why limit something like this to the developing world? If the developed world used low-power, high-efficiency lighting, we'd dramatically reduce the consumption of energy and non-renewable resources. If these lights are cheap enough for the poorest on the planet to consider using them, there's no doubt that they'd save the industrialized nations amazing amounts of money, as well.
Frankly, I suspect we'd do more for the developing world by adopting this sort of thing for ourselves--which is not to say, of course, that we shouldn't encourage them to skip our wasteful ways in favor of the right way to do things.
b&
Goodness gracious!
b&
*waves hand* This is not the daughterboard you're looking for.
b&
Just because you've got an itch doesn't mean that you should scratch it.
There is no need for additional laws, and the idea of ``net cops'' is sheer lunacy compounded with totalitarinism. If a copyright owner doesn't like what somebody's doing with the copyrighted work, let that owner deal wiith it. The {RI,MP}AA can waste their own dollars chasing honest citizens who're acting in concert with the Constitution and ignoring unconsitutional laws.
If you really want to tell your representatives what law to pass, tell them to pass a law repealing the DMCA and the Bono act.
What happens on the file trading networks isn't a crime. What is a crime is that the Scottsdale Symphony can't afford to perform Maurice Ravel's Bolero (you know, the Bo Derek piece) because, thanks to Sonny Bono, it's back under copyright.
b&
Unless you know something the rest of us don't, STL is the only option. 299,792,458 m/s isn't just a good idea, you know, it's the law.
Oh--you meant the Standard Template Library. Nevermind....
b&
The only truly appropriate custom ID for such a plate:
b&
``Lather. Rinse. Repeat.'' Are you sure you've got the right bottle?
b&
This isn't significantly different from the militarizaton of space. China has space launch capabilities, and it doesn't take more than simple collision to destroy a satellite. Yet I don't worry about China (or anybody else) knocking US (or anybody else's) satellites out of the sky.
Why? Because an attack on our satellites would be no different from, say, offshore planes or ships jamming radio signals, or, for that matter, a bunch of commandoes blowing up inland transmission towers. It's a potentially devastating move, but it's also unquestionably an attack on the US and an obvious precursor to invasion or nuclear attack.
A concerted attack on the Internet, and especially on Amereican military computers that are connected to the Internet, is every bit the act of war as are the other scenarios.
Folks, the Chinese are not stupid. For all the sabre-rattling Beijing might do (and let's not forget that Washington's swords are pretty noisy, themselves), they're not about to commit species suicide anytime soon. MAD aside, China is no match for the US militarily in an all-out war, and that's what we've promised if they invade Taiwan. They might not like it, but they know it.
Should the military take steps to protect themselves against such an attack? Of course. But the rest of us shouldn't worry about it any more than we worry about CNN going off the air due to military action.
b&
If any of my browsers succumb to Ooqa Ooqa, I'll have the owner of that site prosecuted under the PATRIOT act.
Either the scumbag who tries to pull off these kinds of things goes to jail for terroristic computer hacking or the PATRIOT act gets struck down. Either way, I win.
b&
I think, perhaps, you just did.
b&
*sigh* The lameness filter aparently doesn't belive in conciseness. Therefore, the quick brown fox jumps over the lazy dog and now is the time for all good people to come to the aid of their country.
All the best to both of you!
b&
If you were to invest $230/month at a 10% annual rate, compounded annually, from the time you were 20 to the time you were 65, you'd have two million dollars in the bank.
So, which would you rather have: AOL's ultimate media package, or multiple millions in the bank when you retired?
b&
...here.
b&
I must admit, I've never gotten into anime. Would those who have recommend this as a good place to start?
b&
For what it's worth, when I first read that story (it could be Have Space Suit, Will Travel, but I'm not sure, either), my first reaction was something like, ``yeah, sure, like that'll happen any time soon.'' It must have been the early eighties. A big part of the thought was that telephones were nothing like CB or walkie-talkies, and the idea of having a handheld two-way radio with its own unique telephone number just didn't seem feasible.
Keep in mind that, at that time, wireless was broadcast-only and wired was point-to-point only...and that I probably wasn't yet a teenager.
b&
Heinlein, especially in his early years, is full of technology that is commonplace today that was pie-in-the-sky when he wrote it. He just didn't always call it by the same names we do today.
I'd have to go digging for specific technologies in specific titles, but it's all good-to-great reading anyway.
Expect to find mobile phones, faxes, video phones, voice dictation, computers of various intelligences, maglev, flywheels for energy storage (we use 'em as a UPS in datacenters; he used 'em in spaceships), sophisticated chemical synthesis (Venusians making real maple syrup from a sample), all sorts of rocketry and space tech, and lots more.
Also good is Niven, though more of his things (such as matter transporters and indestructible ship hulls) are still in the distant future. Zahn likes to take some form of technology, such as $6M-Man-like soldiers (Cobra et al.) and see what it might do to people and society--you get a chapter or two of a space western and the rest of the book of social analysis and commentary.
Sounds like a fun project, if for no other reason than the reading list!
b&