FreeBSD 4.6 320
An Anonymous Coward writes "FreeBSD 4.6 is out! The announcement is out, and so are the release notes.
Have fun, and thanks to the FreeBSD team!" The announcement has all the mirror information, etc.
All seems condemned in the long run to approximate a state akin to Gaussian noise. -- James Martin
Re:software for BSD (Score:4, Informative)
Re:Great to hear it... (Score:2, Informative)
Re:Great! (Score:2, Informative)
semi-polling mode (Score:5, Informative)
Some of Donald Becker's linux driver have this feature.
This improves system stabillity and responsivenes under high nework loads, and avoides the so called 'livelock' where the system isn't hung but it is wasting so much time doing interupt handling that it can't do anything else.
This is a GOOD THING but it won't help much against DDOS
Re:software for BSD (Score:4, Informative)
# cd
# make install
# echo 'linux_enable="YES"' >>
Note that if you choose linux binary compatibility during installation, the above is done for you.
For some things (vmware) you may need to add linprocfs to
linux_base comes with rpm, et al. Rarely, you may need to copy some shared libraries from a linux box to the the appropriate directories under
Really, its easy. The FreeBSD handbook does a good job of explaining [freebsd.org].
Re:figures (Score:3, Informative)
then cd
make buildworld
make buildkernel
make installkernel
reboot
make installworld
mergemaster
then optional: reboot again
:)
Lilo... (Score:3, Informative)
lilo -R
reboot.
I have an "exp" config in my LILO, for experimental kernels before I move them off probation. So, when I have done my build and install, I just type
lilo -R exp && reboot
and there I go.
I don't know if Grub has anything similar.
Re:*BSD is dying (Score:2, Informative)
# cd
# make install
# echo 'linux_enable="YES"' >>
Note that if you choose linux binary compatibility during installation, the above is done for you.
For some things (vmware) you may need to add linprocfs to
linux_base comes with rpm, et al. Rarely, you may need to copy some shared libraries from a linux box to the the appropriate directories under
Re:Linux for desktop, *BSD for servers? (Score:3, Informative)
I think FreeBSD works fine on the desktop, but then again, I don't really play games. I use all the same software as linux folks such as galeon, gaim, enlightenment, kde, etc
Re:Linux for desktop, *BSD for servers? (Score:3, Informative)
I have about 15 years of experiance with BSD systems (I'm counting SunOS 3, SunOS 4, and AOS as BSD systems). That kind of made my shy away from Linux systems and their vaguely Sys5 flavor...but not forever. About a year ago I bought a machine to run Linux on. I used it as a desktop on and off for about 11 months, and then finally put FreeBSD on it. Now my only Linux is my TiVo (and...um...my emergency backup TiVo).
All of the desktop stuff I ever ran under Linux was already running on my older FreeBSD machines, and I never really liked the Linux package managment.
That's not to say Linux is crap, or FreeBSD is a better desktop machine...just that FreeBSD makes a fine desktop, and if you are talking about yourself, supporting one is easier then supporting both. I would say to everyone else out there that has only run BSD systems, give Linux a whirl sometime. The things I didn't like about it are definitly not the things I thought I would dislike. And to those of you that never gave BSD a shot? Go for it.
(besides if you want a real desktop Unix...we all know OSX is the way to go... plus, finally full hardware support for laptop Unix! and a sub-second unsusspend from sleep...)
I use to do Unix support for a University. We went from only having 68000 Suns to having SPARCs, DEC-MIPS, IBM RTs, and some other things while I was there (i.e. one of to four or five). Adding support for the second one is a giant pain...but if you do it right adding the next three isn't bad.
Re:Sun Java (Score:3, Informative)
- you need to build it yourself from src
- you need linux-jdk13 for that
- there's no hotspot
- the certification-process is a bit lengthy...
Combined, this means that for the foreseeable future, you can only get it by building it yourself and using a JIT like shujit or so.
And it's not blessed^H^H^H^H^H^H^Hcertified by SUN.
Re:Sun Java (Score:3, Informative)
Check http://www.freebsd.org/java/ for more info and http://www.freebsd.org/java/dists/13.html in particular for the latest release.
For some time, BSD folks were trying to stay away from non free software (JDK is released under Sun license), but finally gave up due to:
-lack of developers willing to develop a stable JVM from scratch compatible with latest Sun classes (Kaffe is not.)
- popularity of J2EE on the server side and growing number of people switching to Linux based systems just to be able to run Java.
Thanks ot Greg Lewis for doing mostly all the work and other people for spending cycles so we can all run Java on an awesome OS.
PPA, the girl next door.
Re:warning: corrupt ISOs --[FIX]-- (Score:2, Informative)
At the bootloader prompt (Hit enter to continue or any other key for prompt), type:
set hw.ata.atapi_dma=1
boot
and it should install fine. Also, once installed and booted to it, before you try to read from a cd, add the line without 'set' to the
btw, do you have a AOpen 52x also?
Re:figures (Score:1, Informative)
Just:
Where 'X' is one of the cvsup servers, like cvsup2.freebsd.org, cvsup3.freebsd.org, etc.
NOTE: READ what mergemaster has to say!!!
Where YOUR_MACHINE is your edited copy of
It's a snap to keep your bsd box updated. I even have a cron job to build it at 2 a.m. I then manually run mergemaster, and take the rest from there. It's that simple.
Re:Linux for desktop, *BSD for servers? (Score:5, Informative)
I find that the default install (without X) of both FreeBSD and OpenBSD has "everything I want in a server and nothing more." The ports system is there for the few extras you may want (like bash). Basically the defaults for the ports system and the install are sane. When I want a server I install *BSD get it running and forget about it. Usually I install OpenBSD as the install is easier, and it is slightly smaller.
No linux distro gives you this. I love Debian but it is suffereing from bloat. That and the default Debian install isen't good enough, because there isen't a true default. Something about giving the user choice. I don't need choice on my servers. I want an install that has been tested and works. Slackware dosen't have a ports/package system like FreeBSD. Again I want packages that has been tested and work. Slackware also has a hideous config. Editing all those files in
For the desktop I have been useing Debian. I don't care too much about the bloat on the desktop and 'apt-get install package-name' is great. When it came to a desktop shoot out between Debian and FreeBSD, Debian/Linux won becuase ALSA supports my Trident 4D-NX sound card better then FreeBSD. In my experience Linux often supports uncommon bits of hardware better then FreeBSD. There isen't a native Mozilla for OpenBSD, so I haven't really used OpenBSD on the desktop.
For firewalls I have not used FreeBSD, only OpenBSD. OpenBSD has one of the best packet filters out there. It is easy to configure, and works. FreeBSD has something very similar. Recently I have been useing Linux as a firewall due to some funky stuff you can do with equalcost routeing, QOS, and bandwidth shapeing. If you don't need these features then OpenBSD is best. Linux can do some packet bashing that rivals Cisco routers. Unfortunately these features are largely undocumented.
Lack of documentation is ofcourse the worst part of Linux. FreeBSD and OpenBSD have lots documentation that is kept up to date. Linux dosen't.
FreeBSD and OpenBSD are better then any Linux distrobution for servers. These *BSD systems are well thought out and mature products. OpenBSD has a slight edge due to its easier install. On the desktop I think it is a tie. FreeBSD is excellent, but lacks a few of the bells and wistles you will find on a Linux destop. In particular some hardware is better supported under Linux. On the other hand Linux distors suffer from bloat and are not as well thought out as FreeBSD. OpenBSD makes an excellent firewall. Linux makes a good hybrid firewall/router. If I had to choose just one I would install FreeBSD everywhere.
Re:I wonder what happened to FreeBSD 5.0 (Score:2, Informative)
Re:Mach? (Score:2, Informative)
The Mac OS X kernel (also known as XNU) is a monolithic kernel (unlike Mach, but like Linux and xBSD) with Mach and BSD sitting side-by-side.
Mach handles memory management, IPC and device drivers. BSD handles users and permissions, the network stack, the virtual file system and POSIX.
Once outside the kernel it's much more BSD like, with a large dollop of NeXT-isms thrown in. Most of the CLI and utilities are BSD like. Mac OS X tends to use OpenBSD for networking. (As an aside, Mac OS 8-9's OpenTransport is streams based, like Solaris. In fact, written by Mentat who wrote the NetWare and Solaris stacks too).
The chief gotcha may be that Mach handles I/O. The BSD /dev tree is there, but putting devices into the tree is done dynamically by Mach. In other words, you can't make use of any BSD device drivers.
Theo... (Score:1, Informative)
Thanks to all of your generalisation and mud-slinging, you come across as an arrogant bastard with no respect for anything besides your own self-righteous position as the creator of OpenBSD.
I find it hard to believe that you are the "real" Theo. But if you are: act your age. You aren't going to gain any potential advocates by insulting your critics and dismissing them as "fanboys" and "children". They may even have some valid arguments (unlike your leaky arguments, this [securityfocus.com] vulnerability you pointed out also applied to OpenBSD).
And you wonder why people are still critical of OpenBSD? With an attitude like yours, perhaps it's well deserved.
Re:semi-polling mode (Score:3, Informative)
It always has. However the catch is that when there is no data to read polling still uses resources. So if 99% of the time there is data to read you are better off polling for it. If most of the time there is no data you are better off with the interupt overhead.
I know one product that gets around this by having the interupt handler never exit until there is no data, so if you are streaming data in they stay in the interupt handler, often for as much as 20 seconds at a time. Of course this means you can't do any other processing on the system, but that is okay for their application. There are many other ways around this, but you have to know your application to try them.
Re:Use a real BSD (Score:3, Informative)
Okay, you just made yourself look like a complete jackass. Your whole point that "continued development on utterly useless platforms is what accounts for NetBSD's instability compared to OpenBSD and Linux." You identify Mac68k as a "useless platform." Why don't you check out http://www.linux-m68k.org/ and http://www.openbsd.org/mac68k.html
I actually have a Mac SE/30 running OpenBSD, which Theo saw at last year's DefCon. I have a few bitchy points to complain about OpenBSD, but most of what I said before was just flamebait so that some OpenBSD users could make some points, and here I get a bonus jackass such as yourself contributing to the mess.
Re:Use a real BSD (Score:2, Informative)
You misjudged NetBSD, it infact runs quite well on a 68040, we have NetBSD 1.5.2 currently on a Mac 68040-25 currently running a webserver, an eggdrop for a netbsd channel, and a few other things. the 68k port of netbsd is best optimized when installing software with a -mcpu=68040 in the gcc environment. Then again, expect an old 68k to be slower than your 1.2GHz AMD. And NetBSD has been stable in all the years I've been using it.
As for SMP, it is usually not needed in most cases. Also getting SMP to work full-time in OpenBSD and NetBSD is going to take ALOT of work since there is no user-level threading, NetBSD has already introduced kernel-level threading which is still pretty useless.
PS- nice to know someone else out there that uses those multiple platforms such as HP/UX, AIX, *BSD, Solaris/SunOS, OS/2, MacOS, Linux, SCO (I'm well known as "the OS whore"