Yearly FreeBSD Foundation Fundraising Campaign Is On
An anonymous reader writes "The FreeBSD Foundation's annual year-end fundraising drive is currently running. Their goal this year is US$ 1M, and they're currently at US$ 427K. In 2013, the efforts that were funded were from the last drive were: Native iSCSI kernel stack, Updated Intel graphics chipset support, Integration of Newcons, UTF-8 console support, Superpages for ARM architecture, and Layer 2 networking updates. Also various conferences and summit sponsorships, as well as hardware purchases for the Project. The Foundation is a US 501(c)3 non-profit, so your donations (if in the US) are tax-deductible. Some of the larger 2013 (corporate?) sponsors so far are NetApp, LineRate, WhatsApp, and Tarsnap."
I need to start my fundraising to make an open source clone of OS/2 Warp :)
As I recall, FreeBSD provided some of the key underpinnings to Mac OS X and iOS. Surely Apple can spare some of its $90B back to the effort. $1M is a rounding error compared to $90B...
Program Intellivision!
FreeBSD probably isn't useful to you every day. Maybe some of your net traffic will go through a FreeBSD box, but that box could be replaced by just about anything really. However, I'm not trying to say that FreeBSD is useless or irrelevant - what I want to say is that FreeBSD has some excellent out-of-band uses.
I think people should consider the value of the educational, developmental, experimental and competitive opportunities that FreeBSD provides. We need projects and communities which have low hanging fruit for beginners and we need projects that are ready to give different approaches to problems a go - so that the rest of us on whatever OS can learn from it regardless of the success of the implementation.
The same goes for my favourite alternative OS - Haiku which also contains some bits and pieces from FreeBSD for networking/wireless IIRC. (BTW, it has package management now and a lot of improvements to the native browser, and more.)
Someone could make a fortune with something like this!
FreeBSD isnt for the desktop. Next time you need a quick-deploy firewall with advanced features in a virtual environment, and you stumble across pfSense or m0n0wall, remember to thank FreeBSD for making such a stable system.
My experience with it has been limited to a few appliances (freenas, pfsense, etc), but I've generally found it to be way more stable and better performing than linux alternatives (openfiler, untangle). Im sure there are a myriad of technical and non-technical reasons for that, but either way, I hope the FreeBSD folks keep it up.
Many people mistakenly think that freedom is all roses and rainbows. It's not. Freedom can be cruel. Freedom can feel unjust. Freedom can be ugly. Freedom can make you want to cry. But if you truly stand for freedom, then you will accept this. In fact, you won't just accept it, but you will embrace it.
Apple's behavior very clearly shows where true freedom lies when it comes to open source software licensing. It is not in the GPL. Contrary to the claims of its advocates, the GPL does not encourage freedom. It clearly does the opposite; it puts some very dictatorial restrictions upon how the software may be used, modified and redistributed. That is not freedom in any sense of the word.
The BSD license is clearly much the opposite. It is about true freedom. It is about allowing people the freedom to not contribute back changes. This may not be the kind of freedom that makes everybody happy, but freedom isn't about happiness. Freedom is about the ability to act independently, as one wishes, without undue interference or restrictions.
Anyone who truly loves freedom won't have a problem with Apple, or anyone else, benefiting from the generosity of the FreeBSD developers. In fact, they'll be happy that the FreeBSD developers have put out such amazing software with so few restrictions on how it may be used, modified and distributed. They'll be happy that a company like Apple is able to use that software as they see fit, in a way that maximizes Apple's freedom.
Freedom is about minimizing restrictions, as the BSD license shows. Freedom is absolutely not about applying restrictions, like the GPL family of licenses attempts to do.
Which side of your ass are you talking out of?
The GPL in no way restricts how you USE software. I can write viruses through GCC, if I want to. Another appl€ apologist. Keep buying your shiny things every year. Corpse Jobs needs the money.
Check out PC-BSD sometime. http://www.pcbsd.org/
Life was hell, then I discovered Linux...
you make a stupid statement. follow it up with examples of how you haven't used it on the desktop. and then declare your lack of experience.
whaddyuadick?
On the contrary, the GPL does impose restrictions upon how GPL'ed software is used. Remember, "use" also includes the incorporation of unmodified GPL'ed source code into another library or application. It is not permissible to statically link such GPL'ed code into a non-GPL'ed, closed source product that is then distributed. That's a big part of the reason why the LGPL had to be created, for crying out loud! And enough with the "Apple apologist" crap. The GP explicitly mentioned that this extends well beyond Apple. The comment clearly says "Anyone who truly loves freedom won't have a problem with Apple, or anyone else, benefiting from the generosity of the FreeBSD developers."
My (Free)BSD desktop works very well, and it doesn't constantly guess incorrectly about what I want it to do.
"fucktard"? Really? Is that you again Linus?
Forget about the parent A.C. He's swallowed the Kool-Aid, poor devil...
Linus is pretty good at only calling people names when they deserve it, not just to troll.
I can't say that I'm terribly impressed with the pledge interface. You end up with a "transaction completed" page that doesn't detail the transaction nor does it refer you back to the original URL.
When I clicked "back" I hit an autoforward URL, so I'm hoping it was at least smart enough to put in a transaction ID and not attempt the transaction multiple times.
No, he's not. Apologist.
Wut? I used to use FreeBSD as desktop OS before switching to OSX.
It's not only a server system. Works perfectly fine as productive desktop system.
Works fine for me on chips supported by dri. The dri2 support is being nailed down now and once that's in it'll work fine on the same bleeding edge Intel hardware Linux does.
I'm the wifi guy. The WiFi is now up to date on Intel and Atheros 11n. I'd like some help with broadcom. I'll do the Intel and Atheros 11ac stuff early next year.
I'm currently evaluating power management. FreeBSD and xorg on my ivybridge lenovo x230 draw 9w when idle. We are ok at using the deep sleep states per core and package but there's room for improvement.
I'm making the turbo boost stuff work out of the box. Powerd is .. Dumb. Modern CPUs are fine at running at the highest clock rate but spending time in c3 and lower. So I'll fix powers to do that on these chips.
I'm using an x230 in vesa mode but it works fine if you use the new DRI and xorg code. I do day to day hacking on the lenovo t400, mostly due to the cardbus slot I still use.
The only thing missing is hotplug express card.
So.. It's not perfect. 10.0 will not be laptop great. I expect 10.1 with updated dri2 and xorg along with Intel WiFi fixes and my power management stuff to be great.
There.
http://www.gnu.org/distros/common-distros.html#BSD
I'm not a power user but Linux for me is so absolutely stable that it is hard to believe that anyone finds its stability less than perfect. I will say that I want FreeBSD to do well as having strong alternatives is important for all of us. I have used various BSD distros and will say that short of stuffing a grenade in the PC case it is pretty much a rock solid, leave me running forever type of OS.
Yup. If you want to use BSD on desktop, PC-BSD is your ticket. Setting up a desktop on vanilla FreeBSD is not impossible either, but it's a pain in the ass. Just note that PC-BSD recently dropped 32-bit support (P4, early Atom, Core 1 Duo...).
FreeBSD is used by very important software projects such as Apple stuff, Juniper routers and Sony PlayStation 4. Can't those companies really whip a dime or two to the project? One would think that keeping the base OS flourishing would be a good business case for them.
http://www.gnu.org/fun/fun.html#Guidelines
So what exactly is the status of IPv6 support on pFsense?
Look up http://www.osfree.org/ Such a project is already under development.
Couldn't Haiku be forked @ the point they diverged? As for OS/2 Warp, I like the osFree model of taking a microkernel - the L4 - and then putting different 'personalities' on it. It was a bit like IBM's late Workplace OS, or OS/2-PPC, which got aborted since it was based on Mach 3, which compared to L4 was horribly slow.
Total non-sequitur. Apple does contribute to FreeBSD, both in terms of employing some FreeBSD devs, as well as donating certain software to be merged upstream w/ the project. LLVM/Clang being one major example.
Apple is stripping out GPL3 based components, due to certain clauses in the license that make it pretty hostile to business - like the one granting patent rights to everybody in case a certain component uses a certain patent which the contributor holds. But FreeBSD is doing the same - LLVM/Clang has been deprecated in v10, and I believe Samba too might not be included due to its going GPL3 as well.
How hard is a "pkg_add -r xorg gnome2" to execute?
Hmm? Is it really that simple? Recently I tried setting up an FreeBSD+XFCE combination and I humbly went through all the steps in the handbook regarding setting up and configuring X.org, installing and configuring the font packages and installing the ugly XDM, and finally installing XFCE.
I'd have to disagree. I'm using FreeBSD on my laptop right now. I think it makes a great desktop. Linux supports more hardware. But if (and it's a big IF) your hardware is supported by FreeBSD, then you're better off running it.
At my last company we developed an online ordering system for restaurants in the mid 2000's and deployed on FreeBSD over Linux using Pair Networks as our server & colo provider. When younger developers who only knew of Linux asked why my response was, "I don't want to waist time with the systems end of things. BSD will sit there and do it's job." Granted a lot of the backend was also written in Perl.
Once the software was written there wasn't a lot of maintenance, especially once we replaced MySQL with PostgreSQL. We'd have to power down one of the cluster to replace a harddrive, or rather Pair handled that, now and then. Maybe have a hardware failure, but we didn't have any problems stemming from the server OS in six years of operation.
Compare that to the point of sale we wrote which was powered on Linux. There was a number of times that changes to the Linux kernel borked something. Unfortunately touchscreen support & BSD was sorely lacking at the time. It got to the point where I considered hiring someone to write a driver.
"The problem with socialism is eventually you run out of other people's money" - Thatcher.
Compare that to the point of sale we wrote which was powered on Linux. There was a number of times that changes to the Linux kernel borked something.
Considering Linus' stance on breaking userland, and the fact that you wrote the software that was borked in-house, I'm going to ask for a [citation] on this, because it just sounds strange. And, if we're trading anectodes: FreeBSD did a hard lockup on me while attempting to play a .wma file. Impressive.
Note you can turn an existing FreeBSD install into PC-BSD too. Basically a case of switching pkgng to their repository, installing a metapackage and running a few bootstrap commands.
Stability comes in many forms, not simply up time.
For example, Linux has a long, long history of badly managed architectural transitions:
a.out to ELF
libc to glibc
virtual memory manager musical chairs
filesystem flavor of the month
32bit to 64bit
package manager du jour
sound
MAKEDEV/devfs/udev.
Stack on top of that the variety of distributions, with their own often wildly different ideas about where things should live and how they should be managed, frequently causes stability issues by introducing human error points. Many of those ideas are also inherently bad and affect stability, such as RedHat and friends throwing everything and the kitchen sink into /usr. -Yes, some packages can be retargeted...but not many, and doing so breaks convention (albeit a bad one) causing the same sort of management stability issues that multiple distros cause just on the local level.
All of that ends up being a make-work program for Linux System Administrators...honestly at leat 50% of your daily job only exists because of the instability of the Linux ecosystem.
Linux (all distros, all of it) is a Configuration Manager's worst nightmare.
My
AGPL covers usage. The others - GPL, LGPL - do not.
I would say GhostBSD is much better