If you enjoy learning, you'll enjoy FreeBSD.But that extra bit makes it also an extra bit more fun, otherwise I would have considered Linux (and FreeBSD) as a waste of time

If you enjoy learning, you'll enjoy FreeBSD.But that extra bit makes it also an extra bit more fun, otherwise I would have considered Linux (and FreeBSD) as a waste of time
Nothing to add to that really. It was my experience with FreeBSD that gave me the opportunity to go the full UNIX/UNIX-like route. Everything I learned on FreeBSD was easily transferred to Linux and Solaris. In essence they all use the same type of applications anyway, Apache, BIND, Exim, you name it. And because you are forced to configure everything with FreeBSD I was forced to figure out how exactly things worked. That knowledge helped me immensely.If you enjoy learning, you'll enjoy FreeBSD.![]()
Nothing to add to that really. It was my experience with FreeBSD that gave me the opportunity to go the full UNIX/UNIX-like route. Everything I learned on FreeBSD was easily transferred to Linux and Solaris. In essence they all use the same type of applications anyway, Apache, BIND, Exim, you name it. And because you are forced to configure everything with FreeBSD I was forced to figure out how exactly things worked. That knowledge helped me immensely.
Speaking for myself, I started using FreeBSD because there was a CD included in a system administration book I bought some years ago on a whim as it looked interesting at the time. I installed it on a spare disk and went from there.How did you guys learn Unix?
And because few people do gaming on FreeBSD, few people improve the gaming experience on FreeBSD (drivers for cutting-edge video cards, Steam, that kind of things). This is also a reason why FreeBSD isn't popular for that.One thing I never see people mention. FreeBSD is a professional operating system for professional environments so you're far less likely to see it used for gaming, or as much for the desktop, and that's what young people are most likely to use it for.
FreeBSD is a professional operating system for professional environments so you're far less likely to see it used for gaming, or as much for the desktop
make buildworld
running in background, obviously... How did you guys learn Unix?
My current version (Eclipse 4.3.2 "Kepler") works well, except for this bug, but I rarely move the tabs so it's not a great problem. I use the same version at work under Windows 7 (it's a daily suffering...java/eclipse on FreeBSD has been a hobby of mine for some time. You must let me know how that's going for you, Dies_Irae .
How did you guys learn Unix?
I can't say that I've had any issue compiling Firefox in recent memory; just out of curiosity, would you care to post your /etc/make.conf and also note any non-default build options you selected?That's a funny thing, because a lot of ports I try to compile fail. A simple package like Links can be compiled, but something like Firefox is destined to fail.
Your /etc/make.conf is a config file that is used by make when compiling; it is really important understand what each configuration variable does. A good guide to get you started is this BSD Now tutorial for a new install - http://www.bsdnow.tv/tutorials/the-desktop You should still take the time to read over the manpage, too - make.conf(5)I haven't even heard of that file so I guess it is still in the default state. I don't know what kind of options I had chosen. How can I start over new with building, so I can try if even the defaults do not work?
vi /etc/make.conf
.CC=clang
CXX=clang++
CPUTYPE?=native
CPP=clang-cpp
WRKDIRPREFIX=/tmp
MAKE_JOBS_UNSAFE=yes
WITH_PKGNG=yes
DISABLE_VULNERABILITIES=yes
DISABLE_VULNERABILITIES=yes
If you're building a desktop by using ports, sooner or later (at least in my experience) you're going to need to tweak /etc/make.conf. As an example, I needed to setin order to build /www/chromium. If you need to set a variable like that, you will usually find out from the output at the point of failure. Try building /www/firefox again and post the output.Code:DISABLE_VULNERABILITIES=yes
DISABLE_VULNERABILITIES=yes
Sorry, I should have mentioned that. I normally just comment it out after compiling www/chromium, I was just trying to give a real use case example of when you would need to tweak your /etc/make.conf to build a common desktop application.Just a nitpick. Addingto your /etc/make.conf file is generally bad practice IMHO. You would effectively be disabling vulnerability checks on all ports being installed or updated after setting that. Adding that flag directly to make(1) when compiling the specific port affected you wanted to override is a better choice. There are multiple ways to accomplish that. You can of course comment it out after compiling the port, however, if you forget...Code:DISABLE_VULNERABILITIES=yes
# DISABLE_VULNERABILITIES=yes
A lot? Except for the occasional hiccup during an upgrade, I've not had that happen in years; including Firefox.a lot of ports I try to compile fail.