
> Name me an OS doesn't have to be configured.PC-BSD can
> save you a lot of install time.
But... setting font paths??? I'll quote from www.pcbsd.org
"PC-BSD has as its goals to be an easy to install and use desktop OS"
Routine work that must be done, strictly following some manual, when installing the system - this totally contradicts their philosophy. An easy-to-install OS has as its key features that it "just works". This is just brain-dead. On the other hand I hardly think that this is the intended final state of that OS. It would be just too geeky to be real.
- Morin

1st of all PC-BSD is still in BETA, so it must be used with this in mind.
2nd of all your exboss is soooo wrong to fire you for another employees fault (or carelessness) knowing that the swich was for evaluation.
I wish PC-BSD and its team the best, and am looking forward to use it as my Primary OS when it reaches the stable release.
I second vondur's statement, this is a variation of a troll post I have seen before. Also the story is so rediculous that I'm surprised anyone believed it:
- People don't get fired because one computer dies no matter what is lost, using any OS there is always a chance that a few of the computers will experince software or hardware failures that will cause data to be lost.
- Important projects in any professional work environment will have backup copies on a server or external drive. I mean hey, even I keep copies of my important work on USB Jumpdrives and CDs, stupid and/or lazy only sound like good excuses for not having backups when you're the one justifying it to yourself before something really bad happens.
- If the boss approved it then why did this person get fired for the failure of one computer?
- Being very close to a promotion for recommending PC-BSD, yeah right.
- Going from on the edge of a promotion to fired that fast over the failure of one computer, roflmao.
I like the idea. I had been waiting for something like PC-BSD for years.
However the project is very young.
Here is what I need before PC-BSD can become a real alternative:
1)Easily setting up an ADSL connection
2)Having sound: I have a SoundBlaster Live! 24 bits (in linux you need kernel 2.6.12 for full support)
3)The HD geometry issue needs to be solved. This is possibly the most important and difficult issue.
4)I want to read my PC-BSD partition from linux and the other way around.
someones ignorance is showing again....
so are we talking about ADSL or PPOE? either one isnt hard unless you have chosen some crazy isp....
Can you describe the geometry issue you seem to have?
no reason bsd cannot read a linux partition and anyway how hard is it to have a sperate partition in a common format to share stuff?
well did you even decide what YOU was talking about... ADSL or PPPOE ? which is it...
yes, thanks for pointing out those fine examples of what might go wrong in debian, i dont know how I lived without that sage advice that if you mix stuff in debian you might break something....I cant wait to run out and spread that breaking news... And that coming from someone who claims that CNR doesnt run into dependency issues... Considering we was talking about the advantages/disadvantages of CNR and you was claiming that CNR is perfect you sure proved your point.....
Oh and thanks for pointing out that linspire relases a new version every few months... of course only you would consider a bug fix a "new" distro release....
so what is ADSL and what what is the opposite of it and what is the difference? run and google and copy and paste
PC-BSD messed over my 12 linux box but a bunch of clever tricks saved the partitions at a linuxmafia.com installfest, thanks daniel, and then Ubuntu managed to put toghether a new menu.list for grub [and we even downloaded kppp for ubuntu so it CAN work from my place - major hint to gnome bigots - get a better dialer!]. The problem comes from bsd style slices not getting along with others or others not getting along well with slices might represent the problems more accurately since grub was made with bsd in mind. In fact, I wouldn't even have tried PC-BSD at all if it didn't claim to make the partitioning easier than prior attempts. I probably won't try another BSD along with my linuxes until one of them adopts ext3 or similar filesystem as this was not the first time I had this drive won't work in that box problem with a BSD.
Please take this into account when commenting about PC-BSD... If things were done using the command line it's because PC-BSD is not ready. Why dont people get this?
Of course all the command line options will remain there but if the goal of the project is simplicity, things arenīt obviously ready... why do people play dumb just to downplay other people's projects? Makes me sick. Religion is a kind of mind corruption...
PC-BSD while still in beta stage is very stable, has the easiest installs and packaging system (pbi). Windows partition is mounted by default no configuration required (not that it's difficult but saves time) unlike linux, installing linux binary package enables to use linux apps on PC-BSD, while still retaining the ability to install ports FreeBSD style. PC-BSD to me is "FreeBSD made easy".
This is an old Slashdot troll for sure.
Quoting Wikipedia:
We Tried Working With... is a cut and paste troll made infamous by anti-slash.org. The troll starts out by telling a story of an employer who evaluates <insert new item here> based on an employee recommendation. The troll then goes into how great <insert new item here> is, but then goes into how the new thing destroyed their company project - which leads to the dismissal of the employee who suggested the evaluation.
http://en.wikipedia.org/wiki/BSD_is_dying
(at the bottom)
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last
http://www.samag.com/documents/s=1148/sam0107a/0107a.htm
in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin
http://www.amdest.com/stars/Kreskin.html
to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and
its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dbblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
No comment seems to be on how the guide is but instead this turns into a flamefest. Can we stick on topic and give our opinions on the guide?
As for my opinion, I think the guide does a very good job of making it easy for a determined newbie to get PC-BSD up and running successfully. The scripts are helpful. Just download and run them and things get installed with ease. Good job. I for one, am awaiting part 3 eagerly.