Date: Thu, 6 Dec 2001 14:15:15 -0800 (PST) From: "f.johan.beisser" <jan@caustic.org> To: Michael Perrone <mperrone@jtbusa.com> Cc: <questions@FreeBSD.ORG> Subject: Re: the best source Message-ID: <20011206135311.N16958-100000@localhost> In-Reply-To: <4.2.0.58.20011206152321.00ad3350@mail.jtbusa.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 6 Dec 2001, Michael Perrone wrote: > Is there a single comprehensive and authoritative document or book on > converting > from BSDI to FreeBSD? If I migrate our mail and DNS services, I need to be > fairly sure of what I am doing, and would rather not have to read every > single man page, if much of it is identical. for the most part, your conversion will be painless. > The bells and whistles are not so important for our limited needs - just > understanding > what usr files and mail can be simply ported, and which config files in > /etc, for example need to be changed to reflect different path statements, > daemons, etc. since most files are pretty much converted directly, it's just a matter of knowing where things go, and making sure you've got equivelent copies. FreeBSD doesn't use /usr/contrib for 3rd party software. most third party software will be installed to /usr/local/. BSDi doesn't do init the same way.. at all. for one, freebsd's simplified the startup process from the original 4.4-BSD. the start scripts are still fairly dependant on one another (do an ls of rc.* in /etc/ on any fbsd box, and you'll see what i mean), but the configuration is much much easier. i like the more centralised control that rc.conf brings. BSDi's rc system reminds me of solaris or linux's use of complex run levels and interdependant rc scripts. 3rd party software in BSDi is generally started from rc.local. this is very standard BSD behaviour, since you don't replicate your rc.local files over several machines, or if you do, the various scripts fail. Net- and Open-BSD both use the same system.. FreeBSD changed this in favour of using startup scripts in /usr/local/etc/rc.d, one for each of the services used. don't want to run it? tun it off by moving the script from ending in .sh to something else. next reboot, it won't start up. there are many more effective differences between the two, most are in the kernel, buried well below where you would need to worry about them (specifically for mail and other generic services). FreeBSD does sport some of the most advanced networking and disk systems available on BSD, well ahead of where BSDi is. (i should by the way, state that BSDi is the company, they make BSD/OS, and are now owned by Wind River Systems.) > Is there a Lexicon of the differences > between FreeBSD and BSDI? not really. my best bit of advice to you is this: what you choose to do with the OS depends entirely on what you need out of it. BSD/OS does come with support, it is closed off source code. you can purchace source licenses for it (this is of course outdated knowledge on my part, i've not used BSD/OS in a very long time for anything other than high availibility servers, which we do binary patches on), at some expense. if you're already familiar with BSD/OS, there's no reason for you to have any real problems with FreeBSD, or any other BSD out there. -------/ f. johan beisser /--------------------------------------+ http://caustic.org/~jan jan@caustic.org "John Ashcroft is really just the reanimated corpse of J. Edgar Hoover." -- Tim Triche To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011206135311.N16958-100000>