FreeBSD 5.0 RC3 Now Ready
Dan writes "Scott Long announces that FreeBSD 5.0 RC3 has been released and available at all mirrors sites. Release notes can be viewed here, you can download 5.0 RC3 from ftp.freebsd.org or from one of your favorite mirror sites. Many thanks to the FreeBSD Release Engineering team for their work efforts!"
So it can't be completely dead!
first post
*BSD is dead.
FreeBSD 5.0 RC3 Now Dying
talk about beating a dead horse.
Who cares if it says it's not dead yet? We have a quota to meet!
I've used Linux for a while now, and wonder how it compares to the *BSDs.
So... how does it compare? More / less reliable? Easier to use? Etc?
Ok, so I need a new trolling gimmick. Any ideas? It should still revolve around subway, but I need a fresh outlook, fresh like the subway subs, if you will.
...saying *BSD is dead is dead.
What is this "BSD is dead"-stuff ? :>
A joke ?
Finally.
Now I don't have to copy my clients Adaptec DirectCD's to the network on a Windows machine before I can use them.
Why people mail me $3 CDRW's instead of $0.03 CDR's I'll never know.
In Soviet Russia, BSD is alive.
Karma: The shiznight, mostly because I am the Drizzle.
Yay! Finally! FreeBSD rules!
Are we sure this isn't just one of those after death body twitches? Sure, the person may be dead but they're still moving!
Jokes aside, I need to give FreeBSD another shot. I liked it when I used it, I just didn't have the time to play around with it.
I've just changed my Desktop OS from Mandrake to FreeBSD - I'd been running FreeBSD as my server OS for a few years now and have always been impressed by its stability (NEVER had a crash) and ease of configuration. I was unsure about it as a desktop system since in that I want something that just works without any fuss, and Mandrake seemed to do the job. After 4 hours I had FreeBSD running kde with kdm, my mail/news/browsers, sound etc. all set up and working without any touble at all. All I have left is to get my scroll mouse working and I have everything I need, and I am confident I will have much less problems then with Mandrake (a fair few crashes and awkward to troubleshoot).
I would now recommend FreeBSD as the unix of choice for any purpose, it may not have a fancy graphical install program, but you will really appreciate this simplicity when you come to make changes/ do something a little out of the ordinary.
My OS catagories -
Windows XX - For the clueless masses, and often a neccassary evil (esp. games)
Linux Mandrake - Good when it is good (i.e. installs without a problem and no strange configurations), but a hog to troubleshoot.
FreeBSD - The king of server OS's, and by the look of things a great Desktop system.
There's still a few gotchas in this one. Wait for the Release if you need stability.
Barring any nasty bugs, 5.0-Release may show up this week.
"You've got an invalid haircut" -Warren Zevon - Life'll Kill Ya
is it better as desktop os???
if(bsd > linux){ cout why; }
stop supporting microsoft with pirating their software!!!!!
Really looking to 5.0-RELEASE, which is getting quite close now. FreeBSD really is a nice OS> I'd really encourage all linux users to give it a try!
TODO: Something witty here...
Is that a Monty Python reference? "I feel happy! I feel happy -- PLONK"
The End of FreeBSD
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best.
Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It's when you get distracted by the politickers that they sideline you. The tireless work that you perform keeping the system clean and building is what provides the platform for the obsessives and the prima donnas to have their moments in the sun. In the end, we need you all; in order to go forwards we must first avoid going backwards.
To the paranoid conspiracy theorists - yes, I work for Apple too. No, my resignation wasn't on Steve's direct orders, or in any way related to work I'm doing, may do, may not do, or indeed what was in the tea I had at lunchtime today. It's about real problems that the project faces, real problems that the project has brought upon itself. You can't escape them by inventing excuses about outside influence, the problem stems from within.
To the politically obsessed - give it a break, if you can. No, the project isn't a lemonade stand anymore, but it's not a world-spanning corporate juggernaut either and some of the more grandiose visions going around are in need of a solid dose of reality. Keep it simple, stupid.
To the grandstanders, the prima donnas, and anyone that thinks that they can hold the project to ransom for their own agenda - give it a break, if you can. When the current core were elected, we took a conscious stand against vigorous sanctions, and some of you have exploited that. A new core is going to have to decide whether to repeat this mistake or get tough. I hope they learn from our errors.
I started work on FreeBSD because it was fun. If I'm going to continue, it has to be fun again. There are things I still feel obligated to do, and with any luck I'll find the time to meet those obligations.
However I don't feel an obligation to get involved in the political mess the project is in right now. I tried, I burnt out. I don't feel that my efforts were worthwhile. So I won't be standing for election, I won't be shouting from the sidelines, and I probably won't vote in the next round of ballots.
You could say I'm packing up my toys. I'm not going home just yet, but I'm not going to play unless you can work out how to make the project somewhere fun to be again.
= Mike
To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. -- Theodore Roosevelt
"Flogging a dead horse"?
I am a bit ashamed of it, but before getting up I actually masturbated thinking of Dr. Laura.
Debian is dead. It's not moving at all.
We are getting one release in 2 years.
FreeBSD has released 4.7 on October 10th, so they are moving very fast, in my opinion.
I have used FreeBSD in past and like it, but have usually chosen Red Hat because in my opinion it is a lot easier to install and get configured. Hopefully they have improved on this for 5.0. Has anyone who has tried the RC noticed any changes in this arena?
Since /. didn't announce it prematurely, it can't be for real.
_O_
.|< The named which can be named is not the true named
And this is great because it's a start on making binary formats less of an issue. Sure, there's always going to be those who want the fastest versions of, say, "rm", but for the rest of us, being able to compile something on one system and then just move it across anywhere will help tremendously.
Does anyone know if the OpenBSD and NetBSD projects are doing anything similar?
Racists should be sent back to where they came from
In other words, the project has matured and begun to turn into a real software engineering project.
Maybe there is still hope. Maybe BSD is not dying afterall, but just transforming into a more professional product.
Your reliable sources are not so reliable, it seems. FreeBSD is not dead and never was, because it has much which other Unixes/Linuxes don't offer.
I hope you know that Mac OS-X is based on a modified FreeBSD kernel. I like FreeBSD and I am using it as a desktop system. I don't need Linux, because it's emulated here ("emulation" means "emulation which works", not like Wine or stuff like that)
Unlike full releases, RCs seem to be immune to slashdotting! I'm currently pulling over 200K from a Canadian (eh!) FTP mirror site. The day of the last full release, you were lucky to pull over 5 K from ANYWHERE.
Prevent linux based DDOS's!
http://linux.denialofservice.org/
After all, you're an OS that runs on a computer. They have a patent for that you know!
If someone is able, please enlighten me...
I'm starting to become a little frustrated with having to download new ISOs every time an update comes around; examples readily springing to mind are deadRat and FreeBSD. I'm trying out all these things to obtain a better Unix/Linux Background.
I also use 2-3 distros that are a more piecemeal download structure: Gentoo, Debian & Slack. Slack, in particular, is what I'm most familiar with. When a change is made to the Slack9 (slack-current) layout I simply pull the CHANGES via rsync and then build my own isos: thus, I'm not overly wasting bandwidth.
Is there a similar process for other distros, notably Mandrake, SuSE, RHat & *BSD? Or do I have to roll my own for this stuff?
Curious,
-fester
-'fester
My prediction is one day off...
Can anyone recommend a display cleaner?
Wenn ist das Nunstueck git und Slotermeyer? Ja! Beiherhund das Oder die Flipperwaldt gersput.
Like I'm going to fall for this a second time.
You may not have understood the deep cosmological significance of "A Brief History of Rhyme", but there is not denying his crucial role in the establishment of gangsta cosmology. Truly a geniusly depraved English pervert, he will be missed.
N0 FP 4 J00. U R A L4M3R!!
Hi,
I can't boot my laptop with the RC2 and RC3 floppies, because it claims it cannot find said module.
The install hangs at this point.
(in a late stage of probing, after having found the network-card etc.)
4.7 runs OK.
Windows 2000 - from the guys who brought us edlin
(however one spells "fogey")
I can recall my days in college where I would always install the newest, latest and greatest stuff on my pc and then learn it and think I was cool... well, I don't know if I ever thought I was cool.
but nowadays I'm constantly just thinking "why should I upgrade? this stuff works just fine for me the way it is now!"
I think it is because I'm more business minded now and the "if it ain't broke, don't fix it" mentality has an effect on costs in that world.
after reading through what is new in FreeBSD 5, I see no reason for me to change. it looks like things that I don't have much need for in my world.
4.whatever works just dandy for me.
There are some odd things afoot now, in the Villa Straylight.
If you ARE NOT an expert, don't touch the "Custom installation"! People often cannot admit that they are newbies when configuring a system. Please choose "Standard" or at least read the FreeBSD Handbook. You NEED the FreeBSD Handbook, because it's a great document.
.
Use simple installation (default) and the installation is very easy. The installer mostly suggest correct settings and you don't need to do much except pressing
The installation of 5.0-RC2 is almost equal to 4.7-stable. In my opinion the installation phase is not meant to have a complete system after it finishes. It is only for having a basic environment for adapting everything. Almost everyone will want to recompile the kernel and install further software from the ports collection.
Without that competition, Unix would eventually stagnate. Or worse, innovation would be driven into the same kind of useless creeping featurism we've come to expect from the folks in Redmond.
...-.-
So does MySQL under 5.0-RC3 use native threading and are those threads efficient enough that large shops can move back from Linux to FreeBSD on their MySQL servers? We use FreeBSD almost exclusively except for on our multi-CPU SMP MySQL database servers where FreeBSD just couldn't deliver due to threading inefficiencies. We would LOVE to move back to FreeBSD since systems maintenance is very easy and it would also mean having a uniform OS on all our servers.
No open source project is dead as long as there is ONE hacker out there willing to hack on it. Everyone has been screaming FreeBSD is dead for a long time now and guess what? Here comes 5.0. The success of an open source project is not measure by it's use, but by whether or not someone is still willing to hack on it.
Comparison tests show that Ninnle Linux is more stable, more configurable, more user friendly than any of the other Linux distros, and definitely better than any of the BSDs. Try Ninnle today!
In Linux, KDE startup speeds have been improved recently with gcc 3.x, new ld.so in latest glibc, and the objprelink-stuff. How is FreeBSD doing here? Has similiar things been done to the FreeBSD compiler chain to speed up C++ linking times?
Wooo, imagine a Beowulf cluster of these things!
Unix does not prevent you from doing stupid things; that would also prevent you from doing clever things.
I always found Debian a bit obtuse, but mostly per the old, now-deprecated package manager it chose to dump you into on install.
/usr/bin ("and why do I have /usr/local/bin, and why is it empty?").
The distros that emphasize what you call 'simplicity' seem to work okay for users who expect a full XPerience, but to someone like myself, coming from small, customizable systems like DOS and AmigaOS, I couldn't wrap my head around 900 preinstalled entries in
What finally got me flying with *NIX was an install of OpenBSD; Slack, Gentoo or Sourcemage would probably have worked as well, if they'd existed in modern form at that time. [Of course, in retrospect, OpenBSD is still a bit crufty with BIND and Apache by default, but it was a good start, and I now know when to use each of Free, Net, and Open.]
I should also note I'm one of those weird ones who finds BSD kernel config files much more intelligible than (2.2's, admittedly) menuconfig... that's an even more subjective matter than arguing inits, but when you're a noob praying for hardware support, it makes or breaks you. [This was in the bad old days, when Debian's stable kernel hadn't heard of generic Tulip-based NICs, and FreeBSD hadn't either. I stuck with OS/2 for another dozen months, then put FreeBSD 3.5 on a 486 with a 14.4 modem (no LAN!), and evolved from there.
FreeBSD 5.0 is as important a milestone
as ever seen in the *NIX world. Many new
features and core technologies are
incorporated in this release.
The main problems with this release will be
caused by the "Chicken or Egg Conundrum",
in that the release will spur many new 5.0
users, whose input will come "after" the
pre-release testing process, finding bugs
that are not apparent in the release candidate
series due to limited testing on the incredibly
varied hardware and software systems found
in the "wild".
This is not a FreeBSD specific problem, this is
a reflection of the reality of a volunteer based
project with limited resources.
The incredible speed that FreeBSD developers,
contributers, and users update and solve
problems is amazing. Just check the mail
list archives for *many* examples of this!
IMHO many of the best and brightest minds in
the *NIX world have gravitated to the BSD's
stability and more structured development
model. For younger readers a "structured"
development model may seem to be a turn off,
but a few years of real world experience
will certainly temper this argument.
Thanks and Best Wishes to the BSD community,
and when the dust settles FreeBSD 5.X will
be the standard others are compared to.
Sig em Duke !
How about the low-latency (kernel preemption) patch that exists for Linux? How does FreeBSD compare with that? Already have good low latency?
... is driver support. I run my entire home network (12 hosts) on token-ring, but was forced to switch to redhat due to a buggy oltr (OC3140) driver. Beside this, FreeBSD never had another token-ring driver.
Even Linux has its own problems, not counting TX packets and lots of Soft errors on heavy traffic pausing sometimes for upto 10 sec. This is a bummer for online games.
It seems I'll be further forced to use Solaris x86 which naturally has drivers MADE by the madge/olicom people themselves. I dont yet know the quiality of their SNAT code, neet testing. Then again, I run a website on PHP/MYSQL on the same server (one ip ), and theres no PHP for Solaris. Adding GNU GCC and compiling PHP isnt a very tested solution and I'll have trouble there, but gotta try that before switching.
Would have been nice to have ONE real token-ring driver for FreeBSD. I miss its simplicity and standard on Linux, but am discovering so many new networking features on Linux its mind-boggling.
Hardware companies should release a standard driver code (based on XML) that can be translated to C for the platform and natively compiled. Token-ring equipment isnt bad for its price, but only the VERY proprietary OSes get drivers from hardware OEMs. Companies like SUN just sit back while the driver list grows (stability is also the manufacturers problem). *BSD and Linux have to rely on the developer community which is increasingly getting splintered between Linux distros and BSD flavors.
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
...mostly because the non-expert installation has been fairly broken at times, says the user who was allowed to choose both KDE and Gnome, and then noticed X was configured for neither. [Not that you shouldn't be able to install both KDE and Gnome, of course, but there's really no RHAT-like integration, and you just get left confused as to what packages actually got installed.]
I'd argue that users *should* be doing expert installations, and should expect to do at least 10 of them in the first year of learning. After that, there should be enough clue gained to produce the result desired.
--
Hopefully libh will lead to a less braindead installer sometime in the next 12-24 months.
Will there be a reasonable upgrade path from 4.X-STABLE to the 5.X STABLE branch, when it becomes available?
There was from 3.x->4.x, although it may have stretched some people's idea of reasonable. I pulled it off without problems on two boxes, although both were soon replaced with new hardware and fresh installs of 4.x.
http://www.mchawking.com/ M.C. Hawking for president!!.. :)
...there is no way in hell I'm installing 5.0 on anything important, even though it's going to be a "production" release. 4.8, 4.9 all the way baby.
Why you ask? There's far too much new code for 5.0 to be stable yet. I was using 5.0-CURRENT SMP in November and December of 2001, and was very impressed. Alas, it was running on an IBM DeathStar 75GXP, which died (lol--like the name suggests)...
I unsubscribed from the -current list a month or so later because Matt Dillon (the real one) was being his usual dickheaded self and causing a massive flamewar.
Anyway, I resusbscribed to -current in October cause I knew they had slipped the release date to somewhere around November, January, etc. and I wanted to find out how things were going (i.e. is this good enough that I should install it and have more fun with it). Ooh boy. Since I left, we've added GEOM, GDBE, a new init script system, IPFW2, UFS2, etc. vn has been replaced by md, devfs hasn't gotten any better, and as far as I can tell, they still have background fsck turned on by default, which tends to hose you when the least thing goes wrong with your fs (background fsck was FreeBSD's bitter parting shot to me when my GXP died -- it murdered my filesystem before I had a chance to save my valuable data -- admittedly this was a "for fun" desktop system, but that's typically considered Naughty). On -current today we have a couple people posting about panics. I enjoy the response in this one:
From: phk@freebsd.org (for those who don't know, Poul-Henning Kamp is one of the wisest, most respected, and ancient of all FreeBSD hackers)
Subject: Re: FreeBSD 5.0 RC3 now available
"Roderick van Domburg" writes:
I would like to point to a currently unresolved issue
[snip]
The thread is titled "panic: trap: fast data access mmu miss" and is about an error causing the sym SCSI controller to fail to mount root at best, and panic at worst.
Mr. Henning-Kamp's response:
Well, we all want our pet bug fixed before the release rolls, but at some point we simply have to call it quits and ship the release.
[snip]
In the meantime we _really_ have to ship 5.0-RELEASE, we keep slipping it.
Commentary: I agree, they really need to get 5.0 out the door, and I don't necessarily disagree with phk's opinion. But it does say massive Bad Things(tm) to me about the quality of this software that release engineering is leaving *known panics* in the software cause it is so late and over-schedule!!! Ah, and don't even get me started on not being able to install new boot blocks or run fdisk on a mounted filesystem, crashdumps overwriting people's disklabels, etc. etc.
Another one just came in: "PANIC in tcp_syncache.c sonewconn() line 562" about an easily-reproducible (from user mode) kernel panic. Come on people, this is worse than Windows NT ever was! (well, except the guy who could bluescreen it by printing tabs and backspaces).
So, no thanks to 5.x for me, for now.
Well since SCO thinks that Linux infinges on their patents and is wanting to charge every Linux user almost $100/CPU fee it's a good thing that FreeBSD is the highly refined, free unix that it is. :-)
(A die-hard FreeBSD user since 1996)
I don't understand why they modded you "funny"... you really have a point but... I guess it was not understood by them. xoxo's ***
Moderators: Don't agree? pray tell why.
(A die-hard BSD user since 1986)
...-.-
I've always had an interest in FreeBSD. But as trivial as this sounds, I'll never try it as long as they have that stupid L'il Devil logo.
As everyone's said, cvsup is rsync-based, if you want to build an upgrade.
However, when it comes to binary installs (and binary upgrades), not many people realize how painless it is to do an FTP install. I suggest looking into it; it's much less load on the servers vs. downloading ISOs, since you aren't pulling crap you don't need. You should never need to burn an ISO of FreeBSD unless you have 20 boxes to install (and don't want to run your own private net-install mirror, which is a better idea), or have absolutely zip for bandwidth.
I've net-installed OpenBSD over a 56k link- it's surprisingly unpainful, though you do need a proper LAN to do it- no PPP support on the install floppy, so you need another machine serving as NAT gateway.
I have a graphics card that uses the NVIDIA GeForce4 Ti 4400 chipset. I gather that XFree86 doesn't support it. There's an official NVIDIA driver for FreeBSD 4.7. Will it work with 5.0? I don't care about 3D graphics.
BSD licensing means releasing your sourcecode into slavery - does anyone think M$ gives a fuck about copyrights, even if they are only asked to >mention it? Like the BSD license asks to do?
The GPL, on the other hand, at least tries to protect the sourcecode it is applied to and has a strong (because large) community behind it.
Use whatever (free as in speech) OS you want, folks, but _please_ don't put your sourcecode under the BSD license!
"Karma: Bad (mostly affected by moderation done to your comments)" Mods@/. != geek?
-rwxr-xr-x 1 root root 50042807 Jan 28 2001 /bsd.el
It seems some people are confusing Stable and Release branches. 5.0 Release will not be a Stable branch according to Release Engineering. The stable branch will emerge around 5.1 or 5.2.
Just something to keep in mind.
Does this include floppy boot for network installs? ( or those with non booting CDROMS ).
1gb recommended? ack! blows the old mini installs.. quite a lot of wasted space just to run a simple smb server.
---- Booth was a patriot ----
Nope! Check this distro ...
http://www.lesbian.mine.nu/
Lesbian GNU/Linux provides more than a pure OS: it comes with more than 10000 packages, precompiled software bundled up in a nice format for easy installation on your machine.
It comes with a superior package management system called porn-get...
With Mandrake, you can use 'urpmi' to upgrade your system over the net. For example, if you want to upgrade your 9.0 system to Cooker (the 9.1 development version), just add it to your urpmi configuration withr /i586/
urpmi.addmedia --distrib Cooker ftp://somemirror.com/path/to/Mandrake-devel/cooke
Then, do
urpmi --media Cooker --auto-select
and you're done. Well, almost done. Urpmi won't update the kernel automatically, you'll need to do an 'urpmi kernel' to get the new kernel installed.
Hey kids, there's only 5 days left 'til Yak Shaving Day!
WOW! This sounds even better than Ninnle! I've always wanted to be a lesbian...if I could only get rid of this penis...men's bodies are soooo ugly! Where do you download it?
Now when'll linux die?
This thing was supposed to be dead already :-)
Most people on /. consider mac users idiots... that's fine with me - I don't really mind... I can compile my own apps, but have no desire to modify my kernel...
I have been looking longingly at the progress that FreeBSD has made in the past year - and hope that 5.0 becomes the basis for the next Darwin release...
This comment is purely (mac)userland-selfish.... but I think it refelcts nicely on the technology and abilities of the FreeBSD team...
Way to go!
He's one of the 25 active BSD users in the *ENTIRE UNIVERSE*.
Viva Linux!
The only thing preventing me from going back to freebsd as my primary *nix based OS is lack of support for my sound card, an SB Audigy Gamer. Does anyone know if/when they plan on supporting the Audigy?
is nvidia support already on rc3? :P
i think ill keep 4.7 and wait a little more...
screen01urt.jpg
theallseeingeye_1.png
screen01ut2k3.png
anyone know if freebsd's kernel has some equivalent to the linux preemptible kernel patch?
Here's a quicker way to upgrade from what other people are suggesting:
/stand/sysinstall as normal. In the options screen, change the release name as appropriate (like to 4.8-RELEASE, etc). Then do a ftp install for the base system, and configure->packages for other stuff. This only works for RELEASE, not -current or -stable.
Run
Simple.
A Government Is a Body of People, Usually Notably Ungoverned
I tried FreeBSD 4.7 for a while - still have it installed actually - and could not get around the problem of user-mountable removable media.
I suppose I could suid the relevant binaries (mount.iso9660 AFAIR), but is there a cleaner solution?
Thanks...
Michel
Fedora Project Contribut
I'm just going to pick on you because of the never crashed comment. I've had Linux, BSD, OSX, Solaris, SunOS, AIX, OS/2, Win2000, WinNT... all crash on me. The only OSes I've never seen crash are VMS and Z-OS. I use Windows 2000 all the time. It crashes; it crashes a lot less than Win95/98/ME but that's far short of never.
Now I have serious trouble believing you've never had a crash and your everyday workstation box.
I wouldn't be so sure. Somebody was speculating things like the patent on the SetUID bit; last I checked BSD had those too.
Hey I remember this program from the Compaq days. Two tips (assuming things haven't changed):
.pdf from them and well the shirt gets worn a lot more than the license plate gets used....
a) The servers were rather stripped so you weren't really showing off too much. You need to put some cool stuff on the servers which shows off what they can do. What is the person trying out True-64 going to see that's going to impressive them?
b) After the test drive you guys sent me a VMS license plate one day FEDEX. I appreciated it but a $3 gift that cost $18 to send.... Anyway go with a nice looking Polo shirt and cheaper shipping. IBM did that when I downloaded a
Just two friendly pieces of advice (not sure if they still apply or not).
says the user who was allowed to choose both KDE and Gnome, and then noticed X was configured for neither.
Why in the world should XFree86 be "configured" for a specific desktop? There is an option in the installer to choose a default desktop. Why didn't you choose one, instead of expecting FreeBSD to make the decision for you?
Contrary to most Linux distros, FreeBSD ships XFree86, KDE, GNOME, and every other package "as is" straight from their respective projects. The only changes made are platform specific. You don't get Bluecurve, because neither KDE or GNOME ship with Bluecurve.
A Government Is a Body of People, Usually Notably Ungoverned
Yes, but BSD's indemnified from any patent issues arising from SystemV as part of their settlement years ago.
*BSD's safe.
How far along has threading come on FreeBSD 5? MySQL suffers on FreeBSD due to this, and although I have heard promises of better things to come in 5, I haven't heard anything concrete.
Just the other day I wrote the simplest tool in Java and it crashed the VM. And since I'd settled on the Linux version of the JVM being the best choice, I couldn't exactly submit a bug to anyone.
Yes, but FreeBSD works.
Don't you even try to fuckin tell me Gentoo Genital-too runs properly. I have tried that piece of shit every release. If you think that shit is better than FreeBSD you are on crack. I'd rather run RedHat 7.1 than deal with that college kid brewed pile of batshit.
And BSD ports, well sheesh, Wally, I've never seen them not work for the shit I need. bash2, ncftp3, wget, portupgrade, cvsup [oh, CVSup, what a wonder FreeBSD inspired thing ], lsof, rsync, sudo, vim.
Funny, and XFree 4.2.1 works perfect in FBSD as I speak. What a fuckin ass. What, you want XFree CVS snapshots to run? Asswipe.
I personally have not seen a release version on a port not work in FreeBSD. You dumb ass.
We all already know that Slashdot will be switching to FreeBSD 5.0 as soon as it comes out, which was stated quite a while ago. I will definatly give it a shot, I dont like the way big linux distributions work, and Slackware isn't supported any more. Plus FreeBSD just has a awesome kernel, and the base system is BAD. Put that together with improved drivers, a great tcp/ip stack (hey they invented tcp/ip), and you've got a awesome OS.
You can call me partial, yeah, I have friends that use FreeBSD, but I really think this will be a big release for FreeBSD, and probably separate it from the whole "dead" BSD group.
"And we have seen and do testify that the Father sent the Son to be the Savior of the World"
1 John 4:14
Thanks :)
Michel
Fedora Project Contribut
Yay, they finally got 32bit cardbus support as well. Now i can get rid of that nasty netbsd off my laptop.