Customizable - Revision history

72.84.95.92: That's not a single command, it's a bunch of commands strung together

2007-09-14T22:18:44Z

That's not a single command, it's a bunch of commands strung together

Heidi: more smoothing

2007-02-27T05:00:21Z

more smoothing

Heidi at 15:07, 18 January 2007

2007-01-18T15:07:27Z

Heidi: format

2007-01-18T14:58:50Z

format

Heidi: rewrite for style and flow

2007-01-18T14:38:29Z

rewrite for style and flow

Jimbo at 23:41, 12 September 2004

2004-09-12T23:41:22Z

Dave at 21:35, 28 August 2004

2004-08-28T21:35:59Z

New page

[[Category:Why FreeBSD?]]

@@ Line 3: / Line 3: @@
 For example, any webmaster will need a webserver but choosing which one depends on the needs. Some may need compatibility with older plug-ins from the [[Apache]] 1.x family while others will want the greater security and speed of the [[Apache]] 2.x family. Still others may need the highest speed and efficiency (but without CGI capability) found in the [[thttpd]] family. With FreeBSD it's easy, normal and even expected to pick and choose or even switch, with minimal pain, heartache or downtime.
-Likewise, this holds true for FTP, DNS, mail, ssh, X-Window components and almost anything else. Even those services which do have a default system installation (such as [[sendmail]] for mail services) are designed to be easily swapped out with any other service the system administrator may choose. For example [[sendmail]] can be replaced by [[qmail]] with a single command:
+Likewise, this holds true for FTP, DNS, mail, ssh, X-Window components and almost anything else. Even those services which do have a default system installation (such as [[sendmail]] for mail services) are designed to be easily swapped out with any other service the system administrator may choose. For example [[sendmail]] can easily be replaced by [[qmail]]:
   cd /usr/ports/mail/qmail && make install && make disable-sendmail && make install-qmail clean

@@ Line 1: / Line 1: @@
-The base installation of FreeBSD is meant to be lean and mean. It only contains the services absolutely necessary to operate the machine. Instead, FreeBSD sysadmins are encouraged to install their own services, whether from the [[ports tree]] or elsewhere, choosing for themselves which software packages suit their needs.
+The base installation of FreeBSD is meant to be lean and mean. It only contains the services absolutely necessary to operate the machine. Then, FreeBSD sysadmins are encouraged to install their own services, whether from the [[ports tree]] or elsewhere, choosing for themselves which software packages suit their needs.
-For example, any webmaster will need a webserver, but depending on the needs, a particular kind of webserver may be more or less appropriate. Some may need compatibility with older plug-ins of the [[Apache]] 1.x family, while others will want the greater security and speed of the [[Apache]] 2.x family. Still others may need the highest speed and efficiency (but with no CGI capability) found in the [[thttpd]] family. With FreeBSD it is easy, normal and even expected to pick and choose or even switch with minimal pain and heartache (or downtime).
+For example, any webmaster will need a webserver but choosing which one depends on the needs. Some may need compatibility with older plug-ins from the [[Apache]] 1.x family while others will want the greater security and speed of the [[Apache]] 2.x family. Still others may need the highest speed and efficiency (but without CGI capability) found in the [[thttpd]] family. With FreeBSD it's easy, normal and even expected to pick and choose or even switch, with minimal pain, heartache or downtime.
-This also holds true for FTP, DNS, mail, ssh, X-Window components and almost anything else. Even those services which do have a default system installation (such as [[sendmail]] for mail services) are specifically designed to be simply and easily swapped out with any other service the system administrator may choose. For example [[sendmail]] can be replaced by [[qmail]] with a single command:
+Likewise, this holds true for FTP, DNS, mail, ssh, X-Window components and almost anything else. Even those services which do have a default system installation (such as [[sendmail]] for mail services) are designed to be easily swapped out with any other service the system administrator may choose. For example [[sendmail]] can be replaced by [[qmail]] with a single command:
   cd /usr/ports/mail/qmail && make install && make disable-sendmail && make install-qmail clean
@@ Line 9: / Line 9: @@
 '''Please be aware though''', one must ''configure'' qmail after doing that so please don't be rash and blindly replace sendmail after reading this without being ready to learn a new system.
-This is all in stark contrast not only with Microsoft Windows, in which sysadmins and users alike are tightly bound to whatever Microsoft provided in the way of system services, but with many GNU/Linux flavours too. For example, veteran '''Red Hat Linux''' admins are familiar with the notion that Apache 1.x "goes with" Red Hat 7, whereas Apache 2.x "goes with" Red Hat 8 and it can be something of a dire mess to try changing from one to the other. What's more, upgrading a base Microsoft or Linux system is likely to willy-nilly change its services whether this is wanted or not. Meanwhile, upgrading the OS may make needed (perhaps mission-critical) services inoperable and comes with widely known risks, downtime and often, unhappiness.
+This is all in stark contrast not only with Microsoft Windows, in which sysadmins and users alike are tightly bound to whatever Microsoft provided in the way of system services, but with many GNU/Linux flavours too. For example, veteran '''Red Hat Linux''' admins are familiar with the notion that Apache 1.x "goes with" Red Hat 7, but Apache 2.x "goes with" Red Hat 8 and so on. It can be a rather daunting, canny mess to try changing from one to the other. What's more, upgrading a base Microsoft or Linux system is likely to blindly change a system's services like it or not and meanwhile, upgrading the OS can make needed (and maybe mission-critical) services inoperable and comes with widely known risks, downtime and often, unhappiness.
-FreeBSD mostly succeeds in drawing a much sharper line between the base system and optional services. It's easy to install whatever type of service wanted from whichever vendor or group chosen (open source or not).
+FreeBSD mostly succeeds in drawing a much sharper line between the base system and optional services. It's easy to install whatever type of service is wanted from whichever vendor or group chosen, open source or not.
-Moreover, FreeBSD is truly open and free. For highly specialized projects, the source code itself can be studied and modified. While this step is not taken by most FreeBSD users, it's a comfort.
+Moreover, FreeBSD is truly open and free. For highly specialized projects the source code itself can be studied and modified. While this step is not taken by most FreeBSD users, it's a comfort.
 [[Category:Why FreeBSD?]]

@@ Line 1: / Line 1: @@
 The base installation of FreeBSD is meant to be lean and mean. It only contains the services absolutely necessary to operate the machine. Instead, FreeBSD sysadmins are encouraged to install their own services, whether from the [[ports tree]] or elsewhere, choosing for themselves which software packages suit their needs.
-For example, any webmaster will need a webserver, but depending on the needs, a particular kind of webserver may be more or less appropriate. Some may need compatibility with older plug-ins of the [[Apache]] 1.x family, while others will want the greater security and speed of the [[Apache]] 2.x family. Still others yet may need the highest speed and efficiency (but with no CGI capability) found in the [[thttpd]] family. With FreeBSD it is easy, normal and even expected to pick and choose or even switch with minimal pain and heartache (or downtime).
+For example, any webmaster will need a webserver, but depending on the needs, a particular kind of webserver may be more or less appropriate. Some may need compatibility with older plug-ins of the [[Apache]] 1.x family, while others will want the greater security and speed of the [[Apache]] 2.x family. Still others may need the highest speed and efficiency (but with no CGI capability) found in the [[thttpd]] family. With FreeBSD it is easy, normal and even expected to pick and choose or even switch with minimal pain and heartache (or downtime).
 This also holds true for FTP, DNS, mail, ssh, X-Window components and almost anything else. Even those services which do have a default system installation (such as [[sendmail]] for mail services) are specifically designed to be simply and easily swapped out with any other service the system administrator may choose. For example [[sendmail]] can be replaced by [[qmail]] with a single command:

@@ Line 3: / Line 3: @@
 For example, any webmaster will need a webserver, but depending on the needs, a particular kind of webserver may be more or less appropriate. Some may need compatibility with older plug-ins of the [[Apache]] 1.x family, while others will want the greater security and speed of the [[Apache]] 2.x family. Still others yet may need the highest speed and efficiency (but with no CGI capability) found in the [[thttpd]] family. With FreeBSD it is easy, normal and even expected to pick and choose or even switch with minimal pain and heartache (or downtime).
-This also holds true for FTP, DNS, mail, ssh, X-Window components and almost anything else. Even those services which do have a default system installation (such as [[sendmail]] for mail services) are specifically designed to be simply and easily swapped out with any other service the system administrator may choose. For example [[sendmail]] can be replaced by [[qmail]] with a single command: '''cd /usr/ports/mail/qmail && make install && make disable-sendmail && make install-qmail clean''' (be aware though, one must ''configure'' qmail after doing that so please don't be rash and blindly replace sendmail after reading this without being ready to learn a new system.)
+This also holds true for FTP, DNS, mail, ssh, X-Window components and almost anything else. Even those services which do have a default system installation (such as [[sendmail]] for mail services) are specifically designed to be simply and easily swapped out with any other service the system administrator may choose. For example [[sendmail]] can be replaced by [[qmail]] with a single command:
 This is all in stark contrast not only with Microsoft Windows, in which sysadmins and users alike are tightly bound to whatever Microsoft provided in the way of system services, but with many GNU/Linux flavours too. For example, veteran '''Red Hat Linux''' admins are familiar with the notion that Apache 1.x "goes with" Red Hat 7, whereas Apache 2.x "goes with" Red Hat 8 and it can be something of a dire mess to try changing from one to the other. What's more, upgrading a base Microsoft or Linux system is likely to willy-nilly change its services whether this is wanted or not. Meanwhile, upgrading the OS may make needed (perhaps mission-critical) services inoperable and comes with widely known risks, downtime and often, unhappiness.

@@ Line 1: / Line 1: @@
-The base installation of FreeBSD is, very purposefully, lean and mean - it contains very few pre-installed services other than those absolutely necessary to operate the machine.  FreeBSD sysadmins are encouraged instead to install their own services, whether from the [[ports tree]] or elsewhere, choosing for themselves which software packages suit their needs best.
+The base installation of FreeBSD is meant to be lean and mean. It only contains the services absolutely necessary to operate the machine. Instead, FreeBSD sysadmins are encouraged to install their own services, whether from the [[ports tree]] or elsewhere, choosing for themselves which software packages suit their needs.
-For example, any given webmaster will of course need a webserver - but for different situations, different types of webserver are more or less appropriate.  Some may need the compatibility with older plug-ins of the [[Apache]] 1.x family, while others will want the greater security and speed of the [[Apache]] 2.x family, and others yet may need the ultimate speed and efficiency (at the sacrifice of CGI capability) of the [[thttpd]] family - and under FreeBSD, it is very easy and "normal" to use any or all of the above, or even switch between them with minimal pain and heartache.
+For example, any webmaster will need a webserver, but depending on the needs, a particular kind of webserver may be more or less appropriate. Some may need compatibility with older plug-ins of the [[Apache]] 1.x family, while others will want the greater security and speed of the [[Apache]] 2.x family. Still others yet may need the highest speed and efficiency (but with no CGI capability) found in the [[thttpd]] family. With FreeBSD it is easy, normal and even expected to pick and choose or even switch with minimal pain and heartache (or downtime).
-This is not just true of webservers, but also FTP, DNS, mail, ssh, X-Windows components, and just about anything else you care to name.  Even those services which do have a default system installation (such as [[sendmail]] for mail services) are specifically designed to be simply and easily replaced in a modular fashion with any alternate service that the system administrator may choose; for example you may replace [[sendmail]] with [[qmail]] with a single command: '''cd /usr/ports/mail/qmail && make install && make disable-sendmail && make install-qmail clean'''.  (Of course, you'd also need to ''configure'' qmail after doing that, so don't just blindly replace sendmail now after reading this line unless you're ready to learn a new system.)
+This also holds true for FTP, DNS, mail, ssh, X-Window components and almost anything else. Even those services which do have a default system installation (such as [[sendmail]] for mail services) are specifically designed to be simply and easily swapped out with any other service the system administrator may choose. For example [[sendmail]] can be replaced by [[qmail]] with a single command: '''cd /usr/ports/mail/qmail && make install && make disable-sendmail && make install-qmail clean''' (be aware though, one must ''configure'' qmail after doing that so please don't be rash and blindly replace sendmail after reading this without being ready to learn a new system.)
-This is in stark contrast not only to Microsoft Windows, in which you are generally bound with iron chain to whatever Microsoft provided you in the way of system services, but also to many GNU/Linux variants.  For example, veteran '''Red Hat Linux''' admins are very familiar with the idea that Apache 1.x "goes with" Red Hat 7, whereas Apache 2.x "goes with" Red Hat 8, and it can be something of a dire mess to try to change from one to the other - and upgrading your base system is likely to willy-nilly change your services whether you want it to or not.
+This is all in stark contrast not only with Microsoft Windows, in which sysadmins and users alike are tightly bound to whatever Microsoft provided in the way of system services, but with many GNU/Linux flavours too. For example, veteran '''Red Hat Linux''' admins are familiar with the notion that Apache 1.x "goes with" Red Hat 7, whereas Apache 2.x "goes with" Red Hat 8 and it can be something of a dire mess to try changing from one to the other. What's more, upgrading a base Microsoft or Linux system is likely to willy-nilly change its services whether this is wanted or not. Meanwhile, upgrading the OS may make needed (perhaps mission-critical) services inoperable and comes with widely known risks, downtime and often, unhappiness.
-FreeBSD tries, and in general succeeds pretty well, in drawing a more concrete line between the base system and optional services.  Not only is it easy to install whatever type of service you like from whichever vendor or group that you like, you don't have to sweat that upgrading your version of FreeBSD will suddenly make the service you depend on inoperable either.
+FreeBSD mostly succeeds in drawing a much sharper line between the base system and optional services. It's easy to install whatever type of service wanted from whichever vendor or group chosen (open source or not).
 [[Category:Why FreeBSD?]]

← Older revision		Revision as of 23:41, 12 September 2004
Line 1:		Line 1:
		+	The base installation of FreeBSD is, very purposefully, lean and mean - it contains very few pre-installed services other than those absolutely necessary to operate the machine. FreeBSD sysadmins are encouraged instead to install their own services, whether from the [[ports tree]] or elsewhere, choosing for themselves which software packages suit their needs best.

		+	For example, any given webmaster will of course need a webserver - but for different situations, different types of webserver are more or less appropriate. Some may need the compatibility with older plug-ins of the [[Apache]] 1.x family, while others will want the greater security and speed of the [[Apache]] 2.x family, and others yet may need the ultimate speed and efficiency (at the sacrifice of CGI capability) of the [[thttpd]] family - and under FreeBSD, it is very easy and "normal" to use any or all of the above, or even switch between them with minimal pain and heartache.
		+
		+	This is not just true of webservers, but also FTP, DNS, mail, ssh, X-Windows components, and just about anything else you care to name. Even those services which do have a default system installation (such as [[sendmail]] for mail services) are specifically designed to be simply and easily replaced in a modular fashion with any alternate service that the system administrator may choose; for example you may replace [[sendmail]] with [[qmail]] with a single command: '''cd /usr/ports/mail/qmail && make install && make disable-sendmail && make install-qmail clean'''. (Of course, you'd also need to ''configure'' qmail after doing that, so don't just blindly replace sendmail now after reading this line unless you're ready to learn a new system.)
		+
		+	This is in stark contrast not only to Microsoft Windows, in which you are generally bound with iron chain to whatever Microsoft provided you in the way of system services, but also to many GNU/Linux variants. For example, veteran '''Red Hat Linux''' admins are very familiar with the idea that Apache 1.x "goes with" Red Hat 7, whereas Apache 2.x "goes with" Red Hat 8, and it can be something of a dire mess to try to change from one to the other - and upgrading your base system is likely to willy-nilly change your services whether you want it to or not.
		+
		+	FreeBSD tries, and in general succeeds pretty well, in drawing a more concrete line between the base system and optional services. Not only is it easy to install whatever type of service you like from whichever vendor or group that you like, you don't have to sweat that upgrading your version of FreeBSD will suddenly make the service you depend on inoperable either.

	[[Category:Why FreeBSD?]]		[[Category:Why FreeBSD?]]