yitianlang said:
So Unix is so hard to use ?
Any operating system (or any software package) is hard to use if you don't read the manual before you've become familiar with it. Not to mention that 'hard to use' is a matter of opinion.
yitianlang said:
I found FreeBSD 9.0-RELEASE install 9.1-RELEASE's packages , and these packages would not work.
Well,
9.0 is different from
9.1, that should give something away as to a possible cause why things might not work as expected.
Even so there is an even bigger issue here (which most likely also explains your current issues): FreeBSD 9.0 is no longer supported, at all, as such using packages from a later version is also bound to cause errors because those packages, as you tend to call them, sort of expect to be used on a supported environment.
yitianlang said:
I just want to know when FreeBSD is installed as a server in
http://www.12345.com[just for example] .How can we update/upgrade it ?
By following
the manual. An important aspect to keep in mind is that FreeBSD is a two-folded experience. First there's the base system which is updated by using
freebsd-update and second there's the optional ports collection which can be updated using either the
portsnap or
svn command.
Keep in mind that the first thing to keeping a server safe is understanding how it works. And the first step to that, in my opinion that is, is by reading the manual. In this particular example the so called
FreeBSD handbook. I write from personal experience saying that this contains everything you're asking about right now.
yitianlang said:
I think if I compile packages from source, that will be boring for waitting too long and there are many errors in the end.
How do you do to upgrade/update it ?
Ask yourself this: if you compile from source and there are errors you'll know then and there that there were issues. Would you really be any safer if those issues simply stopped appearing even though you could have known the issues were still there?
It's a matter of choice. FreeBSD's "3rd party software" is build upon the ports collection. And the main approach there is compiling software yourself. Each to his own, but as to me I no longer would trust a package if I didn't know it cleanly compiled (by seeing this happening myself).
If your goal is not being delayed by compiling software then I can't help wonder; why pick an environment which main goal is aimed at providing just that?
No offense, but although FreeBSD also provides binary packages I can't help state my opinion that if you're aiming to install an operating system with extra's (such as a web server, SQL server, and so on..) you may have picked the wrong solution for the job.
Here's not saying that FreeBSD isn't up to the challenge but as you hinted at yourself earlier on in this message it could require a lot more in depth knowledge and not so much a "out of the box" working environment.
Just my 2 cents here mind you.
.
