Date: Thu, 29 Dec 2005 19:12:49 +0100 From: =?ISO-8859-2?Q?K=F6vesd=E1n_G=E1bor?= <gabor.kovesdan@t-hosting.hu> To: pav@FreeBSD.org Cc: freebsd-www@FreeBSD.org Subject: Re: www/en/advocacy/myths.sgml is full of broken links Message-ID: <43B42721.7060400@t-hosting.hu> In-Reply-To: <1135871595.60574.15.camel@localhost> References: <43B3E51F.8040905@t-hosting.hu> <1135871595.60574.15.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------000900070508020908060209 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit Pav Lucistnik wrote: >Kövesdán Gábor pí¹e v èt 29. 12. 2005 v 14:31 +0100: > > >>Hello, >> >>I've started out to translate the FreeBSD webpage to Hungarian, and I've >>found a lot of dead links in myths.sgml. I've tried to find a new >>location for these documents but no success. If we remove all of those >>links from the part about clustering it will be almost empty, so I >>haven't send a PR. I wrote this to discuss what to do with that page. We >>may look for another good articles about clustering. I'd suggest mention >>CARP and place a link about CARP here, for example: >>http://pf4freebsd.love2party.net/carp.html. >>I hope You have another good ideas. >> >> > >All broken links have to be either fixed or removed. There's just no >point in keeping them. > >Regarding the clustering section, well, is Tom Rhodes' article still >coming "in late 2002"? > >a.out section is awfully irrelevant today. > >This page needs a good overhaul. If you can fill it with some fresh and >relevant content, it would be greatly appreciated. > > > Here is a patch attached: - Eliminate the deprecated a.out section - Remove the broken link to Jordan Hubbard's article - Remove broken links from clustering section and fill that in with new interesting links - Fix link to commercial support - Mention DragonflyBSD as a derivative project - Update the description about architecture ports - Mention MAC and GEOM Frameworks as great new features in the codebase - Remove the test about BSDi, since it doesn't exist any more - Remove the text about Tom Rhodes' future article :) - Mention freebsd-cluster@ instead - Fix a typo (no whitespace before SunOS) - Fix the current ports number and make the description about Linux compatibility more relevant - Mention 32-bit compatibility, too Please also take a look at www/91054, it should be committed, too. Regards, Gabor Kovesdan --------------000900070508020908060209 Content-Type: text/plain; name="myths.sgml.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="myths.sgml.diff" --- myths.sgml.orig Thu Dec 29 17:42:18 2005 +++ myths.sgml Thu Dec 29 18:52:03 2005 @@ -52,9 +52,6 @@ <li><a href="#applications">There are no applications for *BSD</a></li> - <li><a href="#aout">*BSD uses the a.out executable format, which is - outdated technology</a></li> - <li><a href="#beats">*BSD is better than (some other system)</a></li> <li><a href="#beaten">(some other system) is better than *BSD</a></li> @@ -133,9 +130,6 @@ never had to ask for them, they were freely given.</i></p></li> </ul> - <p>Also, see this article written by Jordan Hubbard in Performance - Computing, titled <a href="http://www.performance-computing.com/features/9810of1.shtml">What is FreeBSD?</a></p> - <hr noshade size="1"> <h3><a name="own-distro">You</a> cannot make your own distributions @@ -156,7 +150,8 @@ them proprietary that they can stay in business).</p> <p>The OpenBSD project started as a spinoff from the NetBSD project, and - has since evolved its own distinctive approach.</p> + has since evolved its own distinctive approach. Similarly DragonflyBSD + derives from FreeBSD 4.x.</p> <hr noshade size="1"> @@ -198,11 +193,22 @@ wcarchive.cdrom.com juggle thousands (literally, more than 10,000) simultaneous FTP connections without falling over.</p></li> - <li><p>Architecture ports: Ports of *BSD are under way or already exist - on many other architectures, including UltraSPARC, Alpha, and PowerPC. - NetBSD and OpenBSD both have more architecture ports than FreeBSD, which - is, at the time of writing, running on i386, Alpha and - UltraSPARC.</p></li> + <li><p>Architecture ports: FreeBSD supports seven main architectures + currently: alpha, amd64, i386, ia64, pc98, ppc and sparc64. + There are also ongoing works to port the project for further + architectures. See the <a href="../platforms/index.html"> + Supported Platforms</a> page for more information.</p></li> + + <li><p>MAC Framework: FreeBSD supports Mandatory Access Control, which + are normally possessed by trusted operating systems available for high + price. FreeBSD gives you advanced security for free! The + <a href="http://www.trustedbsd.org">TrustedBSD Project</a> + provides further trusted operating system extensions.</p></li> + + <li><p>GEOM classess: GEOM is a modular disk framework that lets + you concatenate, mirror, stripe, or encrypt disks. It is rich + in functionality and keep your data safe. + </ul> <hr noshade size="1"> @@ -217,9 +223,6 @@ sets. FreeBSD and NetBSD both integrate security fixes first discovered by the OpenBSD team.</p> - <p>This cooperation extends to the commercial company BSDi, who graciously - donated their DOS emulation layer to FreeBSD.</p> - <p>The FreeBSD and NetBSD projects separated more than five years ago. OpenBSD is the only new BSD project to split off in the last five years.</p> @@ -241,37 +244,43 @@ setting up a Cluster simple. The source code is freely available, and will run on FreeBSD without much problem.</li> - <li><a href="http://cubix.desy.de/General/bsd/bsd.html">http://cubix.desy.de/General/bsd/bsd.html</a></li>; - - <li><a href="http://acme.ecn.purdue.edu/">http://acme.ecn.purdue.edu/</a>; - Advanced Computer Matrix for Engineering (ACME) which runs the FreeBSD Operating System.</li> - - <li><a href="http://www.scl.ameslab.gov/workshops/Talks/Mikler/mikler.html">; - http://www.scl.ameslab.gov/workshops/Talks/Mikler/mikler.html</a></li>; - - <li><a href="http://www.scope.gmd.de/info/www6/technical/paper196/paper196.html">; - http://www.scope.gmd.de/info/www6/technical/paper196/paper196.html</a>NetBSD for Clusters!</li> - - <li><a href="http://www.ccrc.wustl.edu/~milind/MediaServers.html">; - http://www.ccrc.wustl.edu/~milind/MediaServers.html</a></li>; + <li><a href="http://www.scl.ameslab.gov/Projects/old/ClusterCookbook/">; + http://www.scl.ameslab.gov/Projects/ClusterCookbook/index.html</a></li>; - <li><a href="http://daily.daemonnews.org/view_story.php3?story_id=964">; - http://daily.daemonnews.org/view_story.php3?story_id=964</a>; - Daemon News Posting, quick talk about Clustering</li> + <li><a href="http://people.freebsd.org/~brooks/papers/bsdcon2003/fbsdcluster/">; + http://people.freebsd.org/~brooks/papers/bsdcon2003/fbsdcluster/</a>; + Brooks Davis's paper about the implementation of a FreeBSD cluster + with more than 300 CPU's</li> + + <li><a href="http://www.onlamp.com/pub/a/bsd/2004/07/01/freesbie.html/">; + http://www.onlamp.com/pub/a/bsd/2004/07/01/freesbie.html/</a>; + Building a Web Cluster with FreeSBIE (a FreeBSD derivative live-CD + system)</li> + + <li><a href="http://www.openbsd.org/faq/pf/carp.html">; + http://www.openbsd.org/faq/pf/carp.html</a>; + OpenBSD's Common Address Redundancy Protocol (CARP) lets you + build redundant clusters at the level of the firewall + + <li><a href=http://www.countersiege.com/doc/pfsync-carp">; + http://www.countersiege.com/doc/pfsync-carp</a>; + A good explanation of CARP + + <li><a href="http://pf4freebsd.love2party.net/carp.html">; + http://pf4freebsd.love2party.net/carp.html</a>; + OpenBSD's CARP ported to FreeBSD - <li><a href="http://www.scl.ameslab.gov/Projects/ClusterCookbook/index.html">; - http://www.scl.ameslab.gov/Projects/ClusterCookbook/index.html</a></li>; </ul> - <p>In addition to this, Tom Rhodes is currently writing an article designed to walk a user through setting up - a Parallel Computing environment using FreeBSD and other utilities. Keep an eye out for this article in late - 2002 early 2003.</p> + <p>Note, that <a href="mailto:freebsd-cluster@FreeBSD.org">freebsd-cluster</a> + mailing list is available for further discussion about clustering of + FreeBSD.</p> <hr noshade size="1"> <h3><a name="support">There's no commercial support for *BSD</a></h3> - <p><b>FreeBSD:</b> The <a href="http://www.FreeBSD.org/commercial/consulting.html">FreeBSD - Commercial Consulting Page</a> lists companies that offer commercial + <p><b>FreeBSD:</b> The <a href="../commercial/consult_bycat.html">FreeBSD + Commercial Vendors Page</a> lists companies that offer commercial support for FreeBSD.</p> <p>The <a href="http://www.freebsdmall.com">FreeBSD @@ -290,16 +299,17 @@ <h3><a name="applications">There</a> are no applications for *BSD</h3> <p>The free software community started running on predominantly BSD - systems(SunOS and similar). *BSD users can generally compile software + systems (SunOS and similar). *BSD users can generally compile software written for these systems without needing to make any changes.</p> <p>In addition, each *BSD project uses a ``ports'' system to make the building of ported software much easier.</p> - <p><b>FreeBSD:</b> There are currently more than 8,000 + <p><b>FreeBSD:</b> There are currently more than 13,000 applications ready to download and install in the FreeBSD ports - collection. On both the i386 and Alpha, the Linux emulation layer will - also run the vast majority of Linux applications.</p> + collection. On i386, amd64, ia64 and Alpha, the Linux emulation layer will + also run the vast majority of Linux applications. On the amd64 and ia64 + architectures there is a compatibility layer to run 32-bit binaries.</p> <p><b>NetBSD:</b> The Linux emulation layer will run the vast majority of i386 Linux applications, and the majority of SunOS4 applications can be @@ -325,17 +335,6 @@ on FreeBSD with Java support was the Linux version. Now you can also use a native FreeBSD version of Mozilla with a native Java plugin, all compiled conveniently from the ports!</p> - - <hr noshade size="1"> - - <h3><a name="aout">*BSD</a> uses the a.out executable format, which is - outdated technology</h3> - - <p><b>FreeBSD:</b> Quite a while ago (before 1998) FreeBSD used the a.out - format by default. There were no pressing reasons to switch earlier. In - particular, FreeBSD did not (and does not) have the problems building - shared libraries that spurred the Linux conversion from a.out to ELF. As - of FreeBSD version 3.0, FreeBSD uses the ELF executable format.</p> <hr noshade size="1"> --------------000900070508020908060209--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43B42721.7060400>