Scott Long has announced the release of FreeBSD 5.2.1. This point release contains security and bug fixes, as well as improvements to the ATA/IDE and SATA handling. A list of mirror sites is here.
FreeBSD 5.2.1 Released
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
I can’t wait for 5.3 ULE!!!
Good to see, but I’m still waiting for the 5.x -STABLE release 8)
The releases are already “stable”. But till 5.3 is out the releases are “new technology” releases. And “not recommended” to use for production.. but I’m running two production servers with 5.1
Will do a make world when 5.3 is out.
@LoCal
The releases are already “stable”.
Yes, but not officially “-STABLE” according to the FreeBSD folks 8)
So does the iso come with KDE 3.2 and GNOME 2.4.2? I hope so.
Great work! Luv FreeBSD!
No, it comes with what it was in 5.2 – 3.2 and 2.4.1. It is a “point” release, to fix bugs. It actually fixes also kdeadmin bug, which Eugenia encountered.
http://freebsd.kde.org/
i tested it on 5.2 and current, and they are pretty ok
I wish if all major Hardware & Software Companies can start active native support for FreeBSD !!!!!!. Then it will be the show of the Enterprise Systems.
So I just moved a week ago one server from RedHat to FreeBSD 5.2.1 RC2. I am a totally newbie with FreeBSD.
How can I upgrade my RC2 server without a keyboard and monitor. (That’s one reason why I like FreeBSD; install the OS without a monitor and keyboard with a null modemcable)
Use the normal routine:
cd /usr/src
make buildworld && make buildkernel
make installkernel
(reboot)
cd /usr/src
make installworld
mergemaster -i
AVL left out a few things such as updating your source code and booting in single user mode when you reboot.
Really as a bare minimum you should read:
1. Using CVSup
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.htm…
2. Make World
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld…
I’ve just tried Fedora test1 and it’s UGLY. Not UI-wise of course, but the configuration, never detected an old SB128, the bottom panel kept freezing totally, the kernel didn’t boot after recompiling etc etc. FreeBSD relies more heavily on command line, but it’s so straightforward… You always know where the stuff that you need is, and the documentation is there. AND the bootloader actually works, because Fedora rendered my XP install unbootable with grub due to BIOS started seeing that HD drive in CHS mode instead of LBA mode. All in all, Go FreeBSD!
This is what I was waiting for! I should try ASAP.
My precious~~~ !!
Keep up the good work FreeBSD team!
1) get cvsup as package or port
2) make a file like:
*default host=cvsup.se.freebsd.org
*default base=/usr
*default prefix=/usr
*default release=cvs
*default delete use-rel-suffix
*default compress
doc-all tag=.
ports-all tag=.
src-all tag=RELENG_5_2
3) run cvsup <the file>
And now a question, should the release tag be RELENG_5_2_1 now or will I get that one automatically? I think I have got 5.2.1-RC1 already or something.
And also, does it matters if I use . as ports tag? That’s current actually, or?
Thank you, FreeBSD people are very nice 😉
The handbook is really good stuf!
The -RELEASE tag for 5.2.1 is RELENG_5_2_1_RELEASE. To follow
security advisories and other critical fixes for 5.2.1 the
corresponding tag is always RELENG_5_2, see:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/
cvs-tags.html
—
-jg.
I still don’t see support for my GigaRAID ITE8212 SATA Controller.
Eugenia, can we please get rid of the canned BSD trolls? This is simply someone copying and pasting the same old tired monologue that ruins every Slashdot thread on BSD.
I fully welcome any real discussion on the pros and cons of BSD vs Linux, but this is not that. Others: please don’t even dignify the trolls with a response. Ignore them, or it will get worse.
I know that this is not a FreeBSD help forum but I tried looking for answers but I have not found any for my question: when adding a rule for tun0, ipfw says that the interface or host can’t be found? But it is there, after I make my dsl connection.
If anyone can direct me to any docs, I would really appreciate it. Thanks.
See these tutorials for IPFW, they are pretty good.
BSD Firewalls: IPFW
http://www.onlamp.com/pub/a/bsd/2001/04/25/FreeBSD_Basics.html
BSD Firewalls: IPFW Rulesets
http://www.onlamp.com/pub/a/bsd/2001/05/09/FreeBSD_Basics.html
Also related:
TCP Protocol Layers Explained
http://www.onlamp.com/pub/a/bsd/2001/03/14/FreeBSD_Basics.html
Capturing TCP Packets
http://www.onlamp.com/pub/a/bsd/2001/03/21/FreeBSD_Basics.html
Thanks for the links. I will read them
All the *BSDs are entirely different operating systems and kernels so I find it redic to expect be binary compat with each other…
But they do tend to be very source compat with each other…
I’m upgrading now .. but compiling, well, everything takes almost a decade on my toshiba laptop. By the time the upgrade’s done 5.3 will be released
.
However, long live gcc optimizations
. They make life on a slow laptop so much easier (once you get the thing to compile 
).
if you don’t have monitor or keyboard access, you need to use the serial console. then do what everyone else suggested.
Actually, you don’t need to drop to single user to do the install… it is just suggested that you do… but works fine as long as nothing calls what is being upgraded…
Still compiling
.
Man I need more ram .. compiling like mad and running openoffice on 64mb ram isn’t probably the best of ideas.
I’m debating on if I should do a clean install of 5.2.1 or just updating the sources and building it.
I guess the question really depends on whether or not I want to reinstall everything else as well. I guess I wouldn’t mind if I did. It would probably clean out all the cruft left behind from installing ports and deinstalling ports.
I’d have to save everything from my home directory to my OpenBSD box, but that’s not big deal. hmmm, although all the ISO’s I have would take awhile to move over.
Anyway, so what do you think? Clean install or not? By the way, I’m upgrading from 5.1 Release.
Why don’t do a binary upgrade?
.
I guess because I just wanted to make sure everything is nice and clean and to make sure that all the old cruft that gets left behind is gone. I’m downloading the mini-iso as I type this so I guess that’s the route I’m gonna go.
It’s no big deal for me really. I’ve installed FreeBSD enough times to breeze by it in just a few minutes. That’s the thing that I love about the FreeBSD installer. It’s simple and gets you installed quickly.
Just do a cvsup =]
From what I remember, it takes a little under 3 hours to recompile the kernel and world on a duron@1300MHz…
From 5.1 to 5.2.1 I’d recommend binary upgrade, and if you don’t mind doing a full reinstall I’d think that’s best in this case. Quite a few changes with a lot of impact. /libexec to name one.
(I wish OSNews had a preview option for comments)
@V. Velox
Yeah, usually I do CVSup but since this machine is an AMD K6-2 400 with a slow Western Digital drive (building world is more IO intensive than it is CPU intensive – you should see how building world flies when you got /usr/obj on a separate SCSI drive on a separate controller) it’s gonna take awhile to rebuild. It will be much faster to reinstall.
Although, backing up my stuff will take awhile too but not nearly as long as it takes to rebuild. If I had a faster machine, I’d definately would rebuild.
@Ricin
That’s exactly one of the concerns that I had. Alot of people don’t realize that with the development branch it’s sometimes better to reinstall due to the changes that have occured. When there’s alot of changes in the system, such as you mentioned /libexec, it’s better to reinstall.
Another example is that FreBSD now uses Perl 5.8.x rather than version 5.6.x and I build world I would still have that older version of Perl rather than the installer installing the latest supported version of Perl. Actually, I don’t think it would really matter much but it’s just an example of things that get left behind. Sure I can easily just update Perl, but that too will take awhile.
So my point is, I agree with you Ricin.
Where did it go? It seems to have disappeared without a trace? Or did my install not copy/build/.. it for some odd reason?
The pkgdb is part of portupgrade, so do you have portupgrade installed?
Isn’t that part of portupgrade or am I mistaken? Let’s check…
> pkg_info portupgrade-20040208
Information for portupgrade-20040208:
Comment:
FreeBSD ports/packages administration and management tool suite
Description:
Portupgrade is a tool to upgrade installed packages via ports or
packages. You can upgrade installed packages without having to
reinstall depending or dependent packages. It can automatically trace
dependency chains up and down upgrading packages recursively.
This package also includes the following utilities:
portinstall: Helps you install new ports in a handy way.
portcvsweb: Instantly lets you browse change history via CVSweb.
portversion: Replaces pkg_version(1) and helps you upgrade packages
with portupgrade(1). (runs much faster)
portsclean: Cleans ports workdir’s, unreferenced distfiles,
old and orphan shared libraries, and stale packages.
portsdb: Creates binary database from the ports INDEX.
ports_glob: Expands ports globs.
pkg_deinstall: Wraps pkg_delete(1) and provides additional features.
pkg_fetch: Fetches packages from a remote site.
pkg_glob: Expands package globs.
pkg_which: Checks which package a file came from quickly.
pkgdb: Manages and searches the package database.
Author: Akinori MUSHA <[email protected]>
Yep, it’s part of portupgrade.
What’s the difference between /usr/ports/INDEX and /usr/ports/INDEX-5 ? Which one ‘portsdb -U’ updates? (I think that if you ‘make index’ in /usr/ports it rebuilds INDEX-5, is this correct?)
Whoopsie. I knew I forgot something :o)
I certainly hope that this one is more stable than the last release. 5.2 was the most dissapointing release since 5.0 as so many basic things were broken. 5.2 was a truely horrible release, and I hope to high heaven that the FreeBSD folks have gotten themselves back on track producing quality code.