FreeBSD 4.6

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.

Comments

Re:software for BSD

[Janon]

Much Free Software from linux compiles fine on BSD, if that isn't what you meen by being a programmer. Otherwise, you can mount your linux system under /usr/compat/linux, add linux_enable="YES" to /etc/rc.conf and run your linux binaries as they are.

Re:Great to hear it...

[cbcbcb]

If you use lilo you can use lilo -R to select which kernel to boot.

Re:Great!

[Leimy]

November 25th.

semi-polling mode

[sigxcpu]

AFAIK selected polling mode means that after an interupt the driver switches to poling mode to avoid the interrupt overhead.
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:semi-polling mode

[bluGill]

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:software for BSD

[elbuddha]

# cd /usr/ports/emulators/linux_base
# make install
# echo 'linux_enable="YES"' >> /etc/rc.conf

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 /etc/fstab.

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 /usr/compat/linux/

Really, its easy. The FreeBSD handbook does a good job of explaining.

Re:figures

[AilleCat]

Time to learn how to use cvsup

then cd /usr/src
make buildworld
make buildkernel
make installkernel
reboot
make installworld
mergemaster

then optional: reboot again

:)

Lilo...

[wowbagger]

If you use LILO, you can specify the kernel to reboot by:

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

[Anonymous Coward]

It will, however, run Linux software! Here's how:

# cd /usr/ports/emulators/linux_base
# make install
# echo 'linux_enable="YES"' >> /etc/rc.conf

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 /etc/fstab.

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 /usr/compat/linux/

Re:Linux for desktop, *BSD for servers?

[White Shadow]

Actually, I use FreeBSD for both desktop and server. I admit that I originally made this decision based on my familiarity with FreeBSD and I was a bit apprehensive, but I've found it to be just as good for everything I do. My original concern was hardware support (getting XFree86 4.x to work properly and firewire support), but it hasn't been a problem. Over the past couple weeks, I've successfully installed one of the 4.6 pre-releases on my laptop, including the firewire cd-rom drive and internal wireless card. Tangentially, I must say that networking with FreeBSD is incredibly easy, I was amazed at how little effort it took to get the wireless card up and running.

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?

[stripes]

However, since Linux got most of the hype, most *nix desktop stuff especially from commercial side like game companies is targeted for it. So it makes sense to use it on the desktop. Just keep your data on the servers ;)

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...)

More experienced administrators: do you support this kind of dualism?

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:warning: corrupt ISOs --[FIX]--

[sar]

I had the same problem, even burned 4 copies of disc1 from a couple different mirrors, and I saw a suggestion from a while back about how to fix it. The fix involved adding a line to /boot/loader.conf, which is kinda hard to do on a cd boot. So, I tried the next step, setting the variable at boot time, and it worked.

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 /boot/loader.conf and all will be well. This is just a workaround, I think its something to do w/ the ata driver and some cdroms, but I could be wrong. All I know is it works, and others have had success w/ that fix.

btw, do you have a AOpen 52x also?

Re:figures

[Anonymous Coward]

Well, it's trivial to upgrade to 4.6, once you have *any* bsd version installed. (Well, so long as you're in the same major version numbers, upgrades are simple.)
Just:

1. cvsup -h cvsupX.freebsd.org /usr/share/examples/cvsup/stabl e-supfile
   Where 'X' is one of the cvsup servers, like cvsup2.freebsd.org, cvsup3.freebsd.org, etc.
   
2. cd /usr/src/ && make buildworld
   
3. make installworld
4. mergemaster
   NOTE: READ what mergemaster has to say!!!
   
5. make buildkernel KERNCONF=YOUR_MACHINE && make installkernel KERNCONF=YOUR_MACHINE
   Where YOUR_MACHINE is your edited copy of /usr/src/sys/i386/conf/GENERIC. See /usr/src/sys/i386/conf/LINT for various options.

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?

[Bishop]

I have used FreeBSD, OpenBSD, and various Linux distros on i386 hardware. In my experience Linux and FreeBSD are excellent on the desktop, and FreeBSD and OpenBSD are excellent on servers.

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 /etc/rc.d/ is not the way to go. Use OpenBSD and you will understand. Gentoo is interesting. I just started useing it. It has promise, but it needs an easier install. It also needs a better default install. I like it and will continue to use it, but not on my servers. You really have to sit down and use FreeBSD or OpenBSD for a while before you will understand how lacking Linux distros are when it comes to servers.

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

[pancrace]

Coming in November. Look at the release schedule.

Re:Mach?

[Drishmung]

Did you find this link? It gives a good overview of what is going on from a Unix perspective. Some useful quotes:

Part of the history of Mac OS X goes back to Berkeley Software Distributions (BSD) UNIX of the early seventies. Specifically, it is based in part on BSD 4.4 Lite. On a system level, many of the design decisions are made to align with BSD-style UNIX systems. Many of the libraries are derived from NetBSD (http://www.netbsd.org/), while many of the utilities are from FreeBSD (http://www.freebsd.org/). For future development, Mac OS X has adopted FreeBSD as a reference code base for BSD technology. Work is ongoing to more closely synchronize all BSD tools and libraries with the FreeBSD-stable branch.

Although Mac OS X must credit BSD for most of the underlying levels of the operating system, Mac OS X also owes a major debt to Mach. The kernel is heavily influenced in its design philosophy by Carnegie Mellon's Mach project. The kernel is not a pure microkernel implementation though since the address space is shared with BSD processes.

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.