<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
><channel><title>Computer Operating Systems &#187; Netbsd</title> <atom:link href="http://www.morphosppc.com/topic/netbsd/feed" rel="self" type="application/rss+xml" /><link>http://www.morphosppc.com</link> <description>All about Computer Operating Systems</description> <lastBuildDate>Sun, 28 Aug 2011 09:20:48 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.1</generator> <item><title>MIT License &#8211; Comparison to other licenses</title><link>http://www.morphosppc.com/article/mit-license-comparison-to-other-licenses</link> <comments>http://www.morphosppc.com/article/mit-license-comparison-to-other-licenses#comments</comments> <pubDate>Sun, 28 Aug 2011 00:21:04 +0000</pubDate> <dc:creator></dc:creator> <category><![CDATA[FreeBSD]]></category> <category><![CDATA[Bsd License]]></category> <category><![CDATA[End user]]></category> <category><![CDATA[Isc license]]></category> <category><![CDATA[Mit license]]></category> <category><![CDATA[Mit license - comparison to other licenses]]></category> <category><![CDATA[Netbsd]]></category> <category><![CDATA[University of illinois/ncsa open source license]]></category> <category><![CDATA[Xfree86]]></category><guid
isPermaLink="false">http://www.morphosppc.com/article/mit-license-comparison-to-other-licenses</guid> <description><![CDATA[The MIT License is similar to the 3-clause &#8220;modified&#8221; BSD license, except that the BSD license contains a notice prohibiting the use of the name of the copyright holder in promotion. This is sometimes present in versions of the MIT License, as noted above. The original BSD license also includes a clause requiring all advertising [...]No related posts.]]></description> <content:encoded><![CDATA[<div
class="ad" style="float:left; padding:0 15px 15px 15px"><script type="text/javascript"><!--
google_ad_client = "pub-0091919875977192";
/* 336x280, skapad 2011-04-06 */
google_ad_slot = "0402496911";
google_ad_width = 336;
google_ad_height = 280;
//-->
</script><script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div><p>The MIT License is similar to the 3-clause &#8220;modified&#8221; BSD license, except that the BSD license contains a notice prohibiting the use of the name of the copyright holder in promotion. This is sometimes present in versions of the MIT License, as noted above.</p><p>The original BSD license also includes a clause requiring all advertising of the software to display a notice crediting its authors. This &#8220;advertising clause&#8221; (since disavowed by UC Berkeley) is present in the modified MIT License used by XFree86.</p><p>The MIT License states more explicitly the rights given to the end-user, including the right to use, copy, modify, merge, publish, distribute, sublicense, and/or sell the software.</p><p>A 2-clause BSD-style license used by FreeBSD (and preferred for NetBSD) is essentially identical to the MIT License, as it contains neither an advertising clause, nor a prohibition on promotional use of the copyright holder&#8217;s name.</p><p>Also similar in terms is the ISC license, which has a simpler language.</p><p>The University of Illinois/NCSA Open Source License combines text from both the MIT and BSD licenses; the license grant and disclaimer are taken from the MIT License.</p><p>Adapted from the Wikipedia article MIT License, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki</p><p>No related posts.</p>]]></content:encoded> <wfw:commentRss>http://www.morphosppc.com/article/mit-license-comparison-to-other-licenses/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>PA-RISC &#8211; History</title><link>http://www.morphosppc.com/article/pa-risc-history</link> <comments>http://www.morphosppc.com/article/pa-risc-history#comments</comments> <pubDate>Sat, 27 Aug 2011 17:21:03 +0000</pubDate> <dc:creator></dc:creator> <category><![CDATA[OpenBSD]]></category> <category><![CDATA[Complex Instruction Set Computer]]></category> <category><![CDATA[Cpu Cache]]></category> <category><![CDATA[Fused multiply-add]]></category> <category><![CDATA[Hp 3000]]></category> <category><![CDATA[Hp 9000]]></category> <category><![CDATA[Hp focus]]></category> <category><![CDATA[Hp Ux]]></category> <category><![CDATA[I286]]></category> <category><![CDATA[Ibm pc compatible]]></category> <category><![CDATA[Intel]]></category> <category><![CDATA[Linux]]></category> <category><![CDATA[Minicomputer]]></category> <category><![CDATA[Motorola 68000]]></category> <category><![CDATA[Mpe/ix]]></category> <category><![CDATA[Multimedia acceleration extensions]]></category> <category><![CDATA[Netbsd]]></category> <category><![CDATA[Nextstep]]></category> <category><![CDATA[Pa-8000]]></category> <category><![CDATA[Pa-risc]]></category> <category><![CDATA[Pa-risc - history]]></category> <category><![CDATA[Silicon on sapphire]]></category> <category><![CDATA[Simd]]></category> <category><![CDATA[Steve muchnick]]></category> <category><![CDATA[Transistor-transistor logic]]></category> <category><![CDATA[Unix]]></category> <category><![CDATA[Workstation]]></category><guid
isPermaLink="false">http://www.morphosppc.com/article/pa-risc-history</guid> <description><![CDATA[In the late 1980s HP was building four series of computers, all based on CISC CPUs. One line was the IBM PC compatible Intel i286 based Vectra Series started 1986. All others were non-Intel systems. One of them was the HP Series 300 of Motorola 68000-based workstations, another Series 200 line of technical workstations based [...]No related posts.]]></description> <content:encoded><![CDATA[<div
class="ad" style="float:left; padding:0 15px 15px 15px"><script type="text/javascript"><!--
google_ad_client = "pub-0091919875977192";
/* 336x280, skapad 2011-04-06 */
google_ad_slot = "0402496911";
google_ad_width = 336;
google_ad_height = 280;
//-->
</script><script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div><p>In the late 1980s HP was building four series of computers, all based on CISC CPUs. One line was the IBM PC compatible Intel i286 based Vectra Series started 1986. All others were non-Intel systems. One of them was the HP Series 300 of Motorola 68000-based workstations, another Series 200 line of technical workstations based on a custom silicon on sapphire (SOS) chip design, the SOS based 16-bit HP 3000 classic series and finally the HP 9000 Series 500 minicomputers, based on their own (16 and 32-bit) FOCUS microprocessor. HP planned to use PA-RISC to move all of their non-PC compatible machines to a single RISC CPU family.</p><p>Precision Architecture was introduced in 1986. It had thirty-two 32-bit integer registers and sixteen 64-bit floating-point registers. The number of floating-point registers was doubled in the 1.1 version to 32 once it became apparent that 16 were inadequate and restricted performance. The architects included Allen Baum, Hans Jeans, Michael J. Mahon, Ruby Bei-Loh Lee, Russel Kao, Steve Muchnick, Terrence C. Miller and William S. Worley.</p><p>The first implementation was the TS1 a central processing unit built from discrete transistor-transistor logic (TTL) devices. Later implementations were multi-chip VLSI designs fabricated in NMOS processes (NS1 and NS2) and CMOS (CS1 and PCX). They were first used in a new series of HP 3000 machines in the late 1980s &mdash; the 930 and 950, commonly known at the time as Spectrum systems, the name given to them in the development labs. These machines ran MPE/iX. The HP 9000 machines were soon upgraded with the PA-RISC processor as well, running the HP-UX version of UNIX.</p><p>Other operating systems ported to the PA-RISC architecture include Linux, OpenBSD, NetBSD and NEXTSTEP.</p><p>An interesting aspect of the PA-RISC line is that most of its generations have no Level 2 cache. Instead large Level 1 caches are used, formerly as separate chips connected by a bus, and now integrated on-chip. Only the PA-7100LC and PA-7300LC had L2 caches. Another innovation of the PA-RISC was the addition of vectorized instructions (SIMD) in the form of MAX which were first introduced on the PA-7100LC.</p><p>The ISA was extended in 1996 to 64-bits, with this revision named PA-RISC 2.0. PA-RISC 2.0 also added fused multiply-add instructions, which helps certain floating-point intensive algorithms, and the MAX-2 SIMD extension, which provides instructions for accelerating multimedia applications. The first PA-RISC 2.0 implementation was the PA-8000, which was introduced in January 1996.</p><p>Adapted from the Wikipedia article PA-RISC, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki</p><p>No related posts.</p>]]></content:encoded> <wfw:commentRss>http://www.morphosppc.com/article/pa-risc-history/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Bill Joy &#8211; Early career</title><link>http://www.morphosppc.com/article/bill-joy-early-career</link> <comments>http://www.morphosppc.com/article/bill-joy-early-career#comments</comments> <pubDate>Fri, 26 Aug 2011 14:21:43 +0000</pubDate> <dc:creator></dc:creator> <category><![CDATA[OpenBSD]]></category> <category><![CDATA[Apple inc.]]></category> <category><![CDATA[Berkeley Software Distribution]]></category> <category><![CDATA[Bill joy]]></category> <category><![CDATA[Bill joy - early career]]></category> <category><![CDATA[Bob fabry]]></category> <category><![CDATA[C Shell]]></category> <category><![CDATA[Csrg]]></category> <category><![CDATA[Detroit]]></category> <category><![CDATA[Electrical Engineering]]></category> <category><![CDATA[Electrical engineering and computer science]]></category> <category><![CDATA[Eric schmidt]]></category> <category><![CDATA[FreeBSD]]></category> <category><![CDATA[Mac Os X]]></category> <category><![CDATA[Michigan]]></category> <category><![CDATA[Mythopoeia]]></category> <category><![CDATA[Nerds 2.0.1]]></category> <category><![CDATA[Netbsd]]></category> <category><![CDATA[Network file system]]></category> <category><![CDATA[Novell]]></category> <category><![CDATA[Phd]]></category> <category><![CDATA[Public broadcasting service]]></category> <category><![CDATA[Uc berkeley]]></category> <category><![CDATA[University of michigan]]></category> <category><![CDATA[Unix]]></category> <category><![CDATA[Vi]]></category><guid
isPermaLink="false">http://www.morphosppc.com/article/bill-joy-early-career</guid> <description><![CDATA[After growing up in suburban Detroit, Michigan, Joy received his B.S. in Electrical Engineering from the University of Michigan and his M.S. in EECS from UC Berkeley in 1979. Joy&#8217;s PhD advisor was Bob Fabry. As a UC Berkeley graduate student, Joy worked for Fabry&#8217;s Computer Systems Research Group CSRG in managing the BSD support [...]No related posts.]]></description> <content:encoded><![CDATA[<div
class="ad" style="float:left; padding:0 15px 15px 15px"><script type="text/javascript"><!--
google_ad_client = "pub-0091919875977192";
/* 336x280, skapad 2011-04-06 */
google_ad_slot = "0402496911";
google_ad_width = 336;
google_ad_height = 280;
//-->
</script><script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div><p>After growing up in suburban Detroit, Michigan, Joy received his B.S. in Electrical Engineering from the University of Michigan and his M.S. in EECS from UC Berkeley in 1979. Joy&#8217;s PhD advisor was Bob Fabry.</p><p>As a UC Berkeley graduate student, Joy worked for Fabry&#8217;s Computer Systems Research Group CSRG in managing the BSD support and rollout where many claim he was largely responsible for managing the authorship of BSD UNIX, from which sprang many modern forms of UNIX, including FreeBSD, NetBSD, and OpenBSD. Apple Inc. has based much of the Mac OS X kernel and OS Services on the BSD technology.</p><p>Some of his most notable contributions were the vi editor, NFS, and csh. Joy&#8217;s prowess as a computer programmer is legendary, with an oft-told anecdote that he wrote the vi editor in a weekend. Joy denies this assertion.</p><p>Eric Schmidt, CEO of Novell at the time, continued the mythopoesis during an interview in PBS&#8217;s documentary Nerds 2.0.1, inflating Bill Joy&#8217;s accomplishments as having personally rewritten the BSD kernel in a weekend.</p><p>Adapted from the Wikipedia article Bill Joy, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki</p><p>No related posts.</p>]]></content:encoded> <wfw:commentRss>http://www.morphosppc.com/article/bill-joy-early-career/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>AMD Lance Am7990 &#8211; Uses</title><link>http://www.morphosppc.com/article/amd-lance-am7990-uses</link> <comments>http://www.morphosppc.com/article/amd-lance-am7990-uses#comments</comments> <pubDate>Thu, 25 Aug 2011 15:21:03 +0000</pubDate> <dc:creator></dc:creator> <category><![CDATA[OpenBSD]]></category> <category><![CDATA[Alpha axp]]></category> <category><![CDATA[Amd lance am7990]]></category> <category><![CDATA[Amd lance am7990 - uses]]></category> <category><![CDATA[Amiga zorro ii]]></category> <category><![CDATA[Arm architecture]]></category> <category><![CDATA[Dec 3000 axp]]></category> <category><![CDATA[Decstation]]></category> <category><![CDATA[Device Driver]]></category> <category><![CDATA[FreeBSD]]></category> <category><![CDATA[Gxemul]]></category> <category><![CDATA[Industry Standard Architecture]]></category> <category><![CDATA[Microvax]]></category> <category><![CDATA[Mips architecture]]></category> <category><![CDATA[Motherboard]]></category> <category><![CDATA[Motorola 88000]]></category> <category><![CDATA[Netbsd]]></category> <category><![CDATA[Network card]]></category> <category><![CDATA[Operating System]]></category> <category><![CDATA[Personal Computer]]></category> <category><![CDATA[Powerpc]]></category> <category><![CDATA[Q-bus]]></category> <category><![CDATA[Qemu]]></category> <category><![CDATA[Sparcstation]]></category> <category><![CDATA[Sparcstation 1]]></category> <category><![CDATA[Sparcstation 2]]></category> <category><![CDATA[Sun Microsystems]]></category> <category><![CDATA[Sun-3]]></category> <category><![CDATA[Sun-4]]></category> <category><![CDATA[Superh]]></category> <category><![CDATA[Unix]]></category> <category><![CDATA[X86]]></category><guid
isPermaLink="false">http://www.morphosppc.com/article/amd-lance-am7990-uses</guid> <description><![CDATA[* Amiga 2065 the first Ethernet controller for Amiga computer family. Uses the Zorro-II bus interface and equipped with the NMOS Am7990 chip. * MicroVAX Q-Bus Ethernet controllers (like the DELQA). * DECstation 2100/3100 MIPS architecture motherboard Ethernet. * DEC 3000 AXP 64-bit Alpha AXP architecture motherboard. * Sun Microsystems Sun Hydra 3/80, SPARCstation 1, [...]No related posts.]]></description> <content:encoded><![CDATA[<div
class="ad" style="float:left; padding:0 15px 15px 15px"><script type="text/javascript"><!--
google_ad_client = "pub-0091919875977192";
/* 336x280, skapad 2011-04-06 */
google_ad_slot = "0402496911";
google_ad_width = 336;
google_ad_height = 280;
//-->
</script><script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div><p>* Amiga 2065 the first Ethernet controller for Amiga computer family. Uses the Zorro-II bus interface and equipped with the NMOS Am7990 chip.</p><p>* MicroVAX Q-Bus Ethernet controllers (like the DELQA).</p><p>* DECstation 2100/3100 MIPS architecture motherboard Ethernet.</p><p>* DEC 3000 AXP 64-bit Alpha AXP architecture motherboard.</p><p>* Sun Microsystems Sun Hydra 3/80, SPARCstation 1, SPARCstation 2, and SPARCstation IPX computer motherboard.</p><p>* Various x86-Personal computer ISA network interface cards (some called NE1500 and NE2100 ). Under Unix operating systems like FreeBSD/NetBSD/OpenBSD/Linux the device driver is usually called le(4).</p><p>* QEMU emulating Sun-4 architecture (sun4m) virtual network interface.</p><p>* GXemul with le(4) emulating ARM, MIPS, M88K, PowerPC, and SuperH CPU. One example architecture is DECstation 5000 (3max).</p><p>Adapted from the Wikipedia article AMD Lance Am7990, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki</p><p>No related posts.</p>]]></content:encoded> <wfw:commentRss>http://www.morphosppc.com/article/amd-lance-am7990-uses/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Multipurpose Transaction Protocol &#8211; Compatibility</title><link>http://www.morphosppc.com/article/multipurpose-transaction-protocol-compatibility</link> <comments>http://www.morphosppc.com/article/multipurpose-transaction-protocol-compatibility#comments</comments> <pubDate>Tue, 23 Aug 2011 04:21:15 +0000</pubDate> <dc:creator></dc:creator> <category><![CDATA[FreeBSD]]></category> <category><![CDATA[Aix]]></category> <category><![CDATA[Algorithms]]></category> <category><![CDATA[Hp Ux]]></category> <category><![CDATA[Ibm power]]></category> <category><![CDATA[Internet Protocol]]></category> <category><![CDATA[Irix]]></category> <category><![CDATA[Linux]]></category> <category><![CDATA[Mac Os X]]></category> <category><![CDATA[Microsoft Windows]]></category> <category><![CDATA[Mips architecture]]></category> <category><![CDATA[Multipurpose transaction protocol]]></category> <category><![CDATA[Multipurpose transaction protocol - compatibility]]></category> <category><![CDATA[Netbsd]]></category> <category><![CDATA[Pa-risc family]]></category> <category><![CDATA[Port number]]></category> <category><![CDATA[Powerpc]]></category> <category><![CDATA[Solaris]]></category> <category><![CDATA[Sparc]]></category> <category><![CDATA[X86 Architecture]]></category><guid
isPermaLink="false">http://www.morphosppc.com/article/multipurpose-transaction-protocol-compatibility</guid> <description><![CDATA[Because MTP/IP uses proprietary algorithms, compatible software must be installed on both ends of a communication path. Use of the UDP packet format permits compatibility with standard Internet Protocol (IP) network hardware and software. MTP/IP applications may use any available UDP port number. MTP and the applications which use it have been implemented for several [...]No related posts.]]></description> <content:encoded><![CDATA[<div
class="ad" style="float:left; padding:0 15px 15px 15px"><script type="text/javascript"><!--
google_ad_client = "pub-0091919875977192";
/* 336x280, skapad 2011-04-06 */
google_ad_slot = "0402496911";
google_ad_width = 336;
google_ad_height = 280;
//-->
</script><script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div><p>Because MTP/IP uses proprietary algorithms, compatible software must be installed on both ends of a communication path. Use of the UDP packet format permits compatibility with standard Internet Protocol (IP) network hardware and software. MTP/IP applications may use any available UDP port number.</p><p>MTP and the applications which use it have been implemented for several operating systems, including versions of Microsoft Windows, Mac OS X, Linux, NetBSD, FreeBSD, Solaris, IRIX, HP-UX, and AIX. Hardware platforms include variations of x86, PowerPC, UltraSPARC, MIPS64, PA-RISC and POWER.</p><p>Adapted from the Wikipedia article Multipurpose Transaction Protocol, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki</p><p>No related posts.</p>]]></content:encoded> <wfw:commentRss>http://www.morphosppc.com/article/multipurpose-transaction-protocol-compatibility/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Operating system advocacy &#8211; Advocacy and specific operating systems</title><link>http://www.morphosppc.com/article/operating-system-advocacy-advocacy-and-specific-operating-systems</link> <comments>http://www.morphosppc.com/article/operating-system-advocacy-advocacy-and-specific-operating-systems#comments</comments> <pubDate>Sun, 21 Aug 2011 21:20:56 +0000</pubDate> <dc:creator></dc:creator> <category><![CDATA[OpenBSD]]></category> <category><![CDATA[1984]]></category> <category><![CDATA[Apple Computer]]></category> <category><![CDATA[Apple switch ad campaign]]></category> <category><![CDATA[Big Brother]]></category> <category><![CDATA[Compuserve]]></category> <category><![CDATA[Fidonet]]></category> <category><![CDATA[Flaming]]></category> <category><![CDATA[FreeBSD]]></category> <category><![CDATA[Get a mac]]></category> <category><![CDATA[Grassroots]]></category> <category><![CDATA[Hip]]></category> <category><![CDATA[Ibm]]></category> <category><![CDATA[Ibm vnet]]></category> <category><![CDATA[Linux]]></category> <category><![CDATA[Linux Distribution]]></category> <category><![CDATA[Logo]]></category> <category><![CDATA[Macintosh]]></category> <category><![CDATA[Mailing list]]></category> <category><![CDATA[Microsoft]]></category> <category><![CDATA[Microsoft Windows]]></category> <category><![CDATA[Neowin.net]]></category> <category><![CDATA[Netbsd]]></category> <category><![CDATA[Operating system advocacy]]></category> <category><![CDATA[Operating system advocacy - advocacy and specific operating systems]]></category> <category><![CDATA[Os/2]]></category> <category><![CDATA[Plush toy]]></category> <category><![CDATA[Poster]]></category> <category><![CDATA[Prodigy]]></category> <category><![CDATA[Seul]]></category> <category><![CDATA[T Shirt]]></category> <category><![CDATA[Team os/2]]></category> <category><![CDATA[Website]]></category><guid
isPermaLink="false">http://www.morphosppc.com/article/operating-system-advocacy-advocacy-and-specific-operating-systems</guid> <description><![CDATA[FreeBSD FreeBSD is served by a mailing list specifically for advocacy discussion. Advocacy-related materials and links are provided on the FreeBSD website, including a page of logos. Linux As there are a large number of Linux distributions, there are many organizations involved in Linux advocacy, including companies directly involved in the development of distributions as [...]No related posts.]]></description> <content:encoded><![CDATA[<div
class="ad" style="float:left; padding:0 15px 15px 15px"><script type="text/javascript"><!--
google_ad_client = "pub-0091919875977192";
/* 336x280, skapad 2011-04-06 */
google_ad_slot = "0402496911";
google_ad_width = 336;
google_ad_height = 280;
//-->
</script><script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div><h3>FreeBSD</h3><p> FreeBSD is served by a mailing list specifically for advocacy discussion. Advocacy-related materials and links are provided on the FreeBSD website, including a page of logos.</p><h3>Linux</h3><p> As there are a large number of Linux distributions, there are many organizations involved in Linux advocacy, including companies directly involved in the development of distributions as well as purely advocacy-based groups, such as SEUL. Promotion takes on a wide variety of forms from plush toys to t-shirts and posters, and even to more unorthodox forms, such as body paints and video games.</p><h3>Macintosh OS</h3><p> From the 1984 Super Bowl advertisement and &#8220;Test Drive a Macintosh&#8221; to the Apple Switch and Get a Mac advertising campaigns, Apple Computer has a long history of advocating its platform through innovative techniques in traditional media. This also covers advocacy of the Macintosh hardware, peripherals and even lifestyle choices, with both fans and the company projecting a hip and trendy image while negatively portraying Microsoft Windows, IBM or other competitors as anything from awkward and dated to a totalitarian Big Brother figure.</p><h3>Microsoft Windows</h3><p> Neowin.net is a recent attempt in Windows and Microsoft advocacy, concentrating a community of fans of Microsoft products. The site also wrote editorials opposing Windows bashing in the media. Microsoft has also attempted to boost popularity of Windows 7 with a widely ridiculed Launch Party program [http://www.youtube.com/watch?v=1cX4t5-YpHQ].</p><h3>NetBSD</h3><p> Like FreeBSD, the NetBSD Foundation hosts a mailing list especially for advocacy. This mailing list is automatically archived and made accessible online. They also provide some official advocacy material, such as posters and flyers and an official &#8220;powered by&#8221; logo with a license permitting use on any product running NetBSD.</p><h3>OpenBSD</h3><p> Like FreeBSD and NetBSD, the OpenBSD project provides a mailing list specifically intended for advocacy, advocacy@openbsd.org. It was created on July 21, 1998 for discussion of user groups, stickers, shirts and the promotion of OpenBSD&#8217;s image and also to host all flame-worthy discussions. As a part of its advocacy, the project also maintains a list of consulting firms and individual consultants around the world on its website and has produced a number of slogans, including &#8220;Free, Functional &amp; Secure&#8221;, &#8220;Secure by default&#8221;, and &#8220;Power. Security. Flexibility.&#8221; Each OpenBSD release features an original song and a variety of artwork.</p><h3>OS/2</h3><p> OS/2 is the only operating system which saw the creation of a semi-formal advocates organization. Named &#8221;Team OS/2&#8221;, it was a grassroots organization conceived by an IBM employee and initially joined by other IBMers which quickly spread outside IBM. Whether IBM employees or not, Team OS/2 members initially volunteered their time and passion without official sanction from or connection to IBM. Members would promote OS/2 at trade shows, conferences, fairs, and in stores, participate in operating system discussions on CompuServe, Prodigy, Fidonet and Usenet, throw parties, help users install OS/2, contact media figures to explain OS/2 and generate interest, and in general exercise creativity and initiative in helping popularize OS/2.</p><p>The industry dynamics that gave rise to such passionate advocacy were multi-faceted. Perhaps the leading cause was antipathy for the idea that Microsoft could and would establish a monopoly for Windows and DOS, widely deemed as far inferior to OS/2. Additionally, many users feared that IBM, who had proven eminently capable of developing a superior PC operating system, knew very little about consumer marketing in the high-tech marketplace or establishing even a superior product as a standard in the cut-throat, get-there-first-at-any-cost arena dominated by Microsoft. Finally, the mere fact that so many copies of Windows were shipping to users (whom OS/2 advocates viewed as uncritical and uninformed), coupled with the fact that so many in the industry had so much riding on the success of OS/2, created conditions ripe for so many trying to take matters into their own hands. The only spark that was needed for this combustible situation to ignite was an example of evangelism provided by the &#8220;new IBM&#8221; &#8211; a few employees who took &#8220;empowerment&#8221; seriously, able to coordinate their efforts through participation in TEAMOS2 FORUM, an internal IBM discussion group) &#8211; and passionate supporters outside IBM who adopted the ideas and modeled the behaviors of those who were early activists within IBM.</p><p>Adapted from the Wikipedia article Operating system advocacy, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki</p><p>No related posts.</p>]]></content:encoded> <wfw:commentRss>http://www.morphosppc.com/article/operating-system-advocacy-advocacy-and-specific-operating-systems/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>OpenVPN &#8211; Introduction</title><link>http://www.morphosppc.com/article/openvpn-introduction</link> <comments>http://www.morphosppc.com/article/openvpn-introduction#comments</comments> <pubDate>Sun, 21 Aug 2011 12:21:46 +0000</pubDate> <dc:creator></dc:creator> <category><![CDATA[OpenBSD]]></category> <category><![CDATA[Authentication]]></category> <category><![CDATA[Binary file]]></category> <category><![CDATA[Certificate authority]]></category> <category><![CDATA[Client]]></category> <category><![CDATA[Configuration File]]></category> <category><![CDATA[Digital Signature]]></category> <category><![CDATA[FreeBSD]]></category> <category><![CDATA[Ipsec]]></category> <category><![CDATA[Library]]></category> <category><![CDATA[Linux]]></category> <category><![CDATA[Mac Os X]]></category> <category><![CDATA[Netbsd]]></category> <category><![CDATA[Openssl]]></category> <category><![CDATA[Openvpn]]></category> <category><![CDATA[Openvpn - introduction]]></category> <category><![CDATA[Password]]></category> <category><![CDATA[Peer-to-peer]]></category> <category><![CDATA[Pre-shared key]]></category> <category><![CDATA[Protocol]]></category> <category><![CDATA[Public key certificate]]></category> <category><![CDATA[QNX]]></category> <category><![CDATA[Server]]></category> <category><![CDATA[Solaris]]></category> <category><![CDATA[Transport layer security]]></category> <category><![CDATA[User]]></category> <category><![CDATA[Windows 2000]]></category> <category><![CDATA[Windows vista]]></category> <category><![CDATA[Windows Xp]]></category><guid
isPermaLink="false">http://www.morphosppc.com/article/openvpn-introduction</guid> <description><![CDATA[OpenVPN allows peers to authenticate each other using a pre-shared secret key, certificates, or username/password. When used in a multiclient-server configuration, it allows the server to release an authentication certificate for every client, using signature and Certificate authority. It uses the OpenSSL encryption library extensively, as well as the SSLv3/TLSv1 protocol, and contains many security [...]No related posts.]]></description> <content:encoded><![CDATA[<div
class="ad" style="float:left; padding:0 15px 15px 15px"><script type="text/javascript"><!--
google_ad_client = "pub-0091919875977192";
/* 336x280, skapad 2011-04-06 */
google_ad_slot = "0402496911";
google_ad_width = 336;
google_ad_height = 280;
//-->
</script><script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div><p>OpenVPN allows peers to authenticate each other using a pre-shared secret key, certificates, or username/password. When used in a multiclient-server configuration, it allows the server to release an authentication certificate for every client, using signature and Certificate authority. It uses the OpenSSL encryption library extensively, as well as the SSLv3/TLSv1 protocol, and contains many security and control features.</p><p>It is available on Solaris, Linux, OpenBSD, FreeBSD, NetBSD, QNX, Mac OS X, and Windows 2000/XP/Vista. Although Windows, Windows Mobile, Android, iPhone, etc. include built-in support for VPNs, they do not include OpenVPN. It must be installed as a separate program and configured by editing text files manually, rather than through the normal GUI. It is not a &#8220;web-based&#8221; VPN, meaning that it is not shown as a web page such as Citrix or TS Web access. OpenVPN is not compatible with IPsec or any other VPN package. The entire package consists of one binary for both client and server connections, an optional configuration file, and one or more key files depending on the authentication method used. It is sometimes used by computer gamers as a way of accessing LAN games over the internet.</p><p>Adapted from the Wikipedia article OpenVPN, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki</p><p>No related posts.</p>]]></content:encoded> <wfw:commentRss>http://www.morphosppc.com/article/openvpn-introduction/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>XORP &#8211; Introduction</title><link>http://www.morphosppc.com/article/xorp-introduction</link> <comments>http://www.morphosppc.com/article/xorp-introduction#comments</comments> <pubDate>Sun, 21 Aug 2011 04:21:29 +0000</pubDate> <dc:creator></dc:creator> <category><![CDATA[OpenBSD]]></category> <category><![CDATA[Atanu ghosh]]></category> <category><![CDATA[Berkeley]]></category> <category><![CDATA[C]]></category> <category><![CDATA[California]]></category> <category><![CDATA[Dragonflybsd]]></category> <category><![CDATA[FreeBSD]]></category> <category><![CDATA[Intel]]></category> <category><![CDATA[International computer science institute]]></category> <category><![CDATA[Internet Protocol]]></category> <category><![CDATA[Linux]]></category> <category><![CDATA[Mac Os X]]></category> <category><![CDATA[Mark handley]]></category> <category><![CDATA[Microsoft]]></category> <category><![CDATA[National science foundation]]></category> <category><![CDATA[Netbsd]]></category> <category><![CDATA[Open Source]]></category> <category><![CDATA[Quagga]]></category> <category><![CDATA[Routing]]></category> <category><![CDATA[University college london]]></category> <category><![CDATA[Vyatta]]></category> <category><![CDATA[Windows Server 2003]]></category> <category><![CDATA[Xorp]]></category> <category><![CDATA[Xorp - introduction]]></category><guid
isPermaLink="false">http://www.morphosppc.com/article/xorp-introduction</guid> <description><![CDATA[XORP, or eXtensible Open Router Platform, is an open source Internet Protocol routing software suite. It is designed from principles of software modularity and extensibility and aims at exhibiting stability and providing feature requirements for production use while also supporting networking research. The development project was founded by Mark Handley in 2000. Receiving funding from [...]No related posts.]]></description> <content:encoded><![CDATA[<div
class="ad" style="float:left; padding:0 15px 15px 15px"><script type="text/javascript"><!--
google_ad_client = "pub-0091919875977192";
/* 336x280, skapad 2011-04-06 */
google_ad_slot = "0402496911";
google_ad_width = 336;
google_ad_height = 280;
//-->
</script><script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div><p>XORP, or eXtensible Open Router Platform, is an open source Internet Protocol routing software suite.</p><p>It is designed from principles of software modularity and extensibility and aims at exhibiting stability and providing feature requirements for production use while also supporting networking research. The development project was founded by Mark Handley in 2000. Receiving funding from Intel, Microsoft, and the National Science Foundation, it released its first production software in July 2004. The project was then run by Atanu Ghosh of the International Computer Science Institute, in Berkeley, California.</p><p>In July 2008, the International Computer Science Institute transferred the XORP technology to a new entity, XORP Inc., a commercial startup founded by the leaders of the opensource project team and backed by Onset Ventures and Highland Capital Partners. In February 2010, XORP Inc. was wound up, a victim of the recession. However the open source project continues, with the servers now based at University College London.</p><p>The XORP codebase consists of around 670,000 lines of C++ and is developed primarily on FreeBSD, but fully supported on Linux, OpenBSD, DragonFlyBSD, NetBSD, Mac OS X. A port running on Windows Server 2003 only supports IPv4. XORP is available for download as a Live CD or as source code via the project&#8217;s homepage.</p><p>The software suite was selected commercially as the routing platform for the Vyatta line of products in its early releases, but later has been replaced with quagga.</p><p>Adapted from the Wikipedia article XORP, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki</p><p>No related posts.</p>]]></content:encoded> <wfw:commentRss>http://www.morphosppc.com/article/xorp-introduction/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Bluetooth &#8211; Computer requirements</title><link>http://www.morphosppc.com/article/bluetooth-computer-requirements</link> <comments>http://www.morphosppc.com/article/bluetooth-computer-requirements#comments</comments> <pubDate>Sat, 20 Aug 2011 16:20:23 +0000</pubDate> <dc:creator></dc:creator> <category><![CDATA[OpenBSD]]></category> <category><![CDATA[Apple inc.]]></category> <category><![CDATA[Bluetooth]]></category> <category><![CDATA[Bluetooth - computer requirements]]></category> <category><![CDATA[Bluetooth stack]]></category> <category><![CDATA[Bluez]]></category> <category><![CDATA[Computer Keyboard]]></category> <category><![CDATA[Desktop Computer]]></category> <category><![CDATA[Dongle]]></category> <category><![CDATA[FreeBSD]]></category> <category><![CDATA[Infrared data association]]></category> <category><![CDATA[Laptop]]></category> <category><![CDATA[Linux]]></category> <category><![CDATA[Mac os x v10.2]]></category> <category><![CDATA[Microsoft]]></category> <category><![CDATA[Mobile Phone]]></category> <category><![CDATA[Mouse]]></category> <category><![CDATA[Netbsd]]></category> <category><![CDATA[Nokia]]></category> <category><![CDATA[Personal Computer]]></category> <category><![CDATA[Qualcomm]]></category> <category><![CDATA[Usb]]></category> <category><![CDATA[Windows xp service pack 2]]></category><guid
isPermaLink="false">http://www.morphosppc.com/article/bluetooth-computer-requirements</guid> <description><![CDATA[A personal computer that does not have embedded Bluetooth can be used with a Bluetooth adapter or &#8220;dongle&#8221; that will enable the PC to communicate with other Bluetooth devices (such as mobile phones, mice and keyboards). While some desktop computers and most recent laptops come with a built-in Bluetooth radio, others will require an external [...]No related posts.]]></description> <content:encoded><![CDATA[<div
class="ad" style="float:left; padding:0 15px 15px 15px"><script type="text/javascript"><!--
google_ad_client = "pub-0091919875977192";
/* 336x280, skapad 2011-04-06 */
google_ad_slot = "0402496911";
google_ad_width = 336;
google_ad_height = 280;
//-->
</script><script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div><p> A personal computer that does not have embedded Bluetooth can be used with a Bluetooth adapter or &#8220;dongle&#8221; that will enable the PC to communicate with other Bluetooth devices (such as mobile phones, mice and keyboards). While some desktop computers and most recent laptops come with a built-in Bluetooth radio, others will require an external one in the form of a dongle.</p><p>Unlike its predecessor, IrDA, which requires a separate adapter for each device, Bluetooth allows multiple devices to communicate with a computer over a single adapter.</p><h3> Operating system support</h3><p> Apple has supported Bluetooth since Mac OS X v10.2 which was released in 2002.</p><p>For Microsoft platforms, Windows XP Service Pack 2 and SP3</p><p>releases have native support for Bluetooth 1.1, 2.0 and 2.0+EDR.</p><p>Previous versions required users to install their Bluetooth adapter&#8217;s own drivers, which were not directly supported by Microsoft.</p><p>Microsoft&#8217;s own Bluetooth dongles (packaged with their Bluetooth computer devices) have no external drivers and thus require at least Windows XP Service Pack 2. Windows Vista RTM/SP1 with the Feature Pack for Wireless or Windows Vista SP2 support Bluetooth 2.1+EDR. Windows 7 supports Bluetooth 2.1+EDR and Extended Inquiry Response (EIR).</p><p>The Windows XP and Windows Vista/Windows 7 Bluetooth stacks support the following Bluetooth profiles natively: PAN, SPP, DUN, HID, HCRP. The Windows XP stack can be replaced by a third party stack which may support more profiles or newer versions of Bluetooth. The Windows Vista/Windows 7 Bluetooth stack supports vendor-supplied additional profiles without requiring the Microsoft stack to be replaced.</p><p>Linux has two popular Bluetooth stacks, BlueZ and Affix. The BlueZ stack is included with most Linux kernels and was originally developed by Qualcomm. The Affix stack was developed by Nokia.</p><p>FreeBSD features Bluetooth support since its 5.0 release.</p><p>NetBSD features Bluetooth support since its 4.0 release. Its Bluetooth stack has been ported to OpenBSD as well.</p><p>Adapted from the Wikipedia article Bluetooth, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki</p><p>No related posts.</p>]]></content:encoded> <wfw:commentRss>http://www.morphosppc.com/article/bluetooth-computer-requirements/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Snack Sound Toolkit &#8211; Introduction</title><link>http://www.morphosppc.com/article/snack-sound-toolkit-introduction</link> <comments>http://www.morphosppc.com/article/snack-sound-toolkit-introduction#comments</comments> <pubDate>Fri, 19 Aug 2011 06:20:41 +0000</pubDate> <dc:creator></dc:creator> <category><![CDATA[FreeBSD]]></category> <category><![CDATA[Audio filter]]></category> <category><![CDATA[Hp Ux]]></category> <category><![CDATA[Irix]]></category> <category><![CDATA[Linux]]></category> <category><![CDATA[Mac Os X]]></category> <category><![CDATA[Microsoft Windows]]></category> <category><![CDATA[Netbsd]]></category> <category><![CDATA[Pitch tracking]]></category> <category><![CDATA[Python]]></category> <category><![CDATA[Royal institute of technology]]></category> <category><![CDATA[Ruby]]></category> <category><![CDATA[Snack sound toolkit]]></category> <category><![CDATA[Snack sound toolkit - introduction]]></category> <category><![CDATA[Solaris]]></category> <category><![CDATA[Sound pressure]]></category> <category><![CDATA[Spectral analysis]]></category> <category><![CDATA[Spectrogram]]></category> <category><![CDATA[Tcl]]></category><guid
isPermaLink="false">http://www.morphosppc.com/article/snack-sound-toolkit-introduction</guid> <description><![CDATA[Snack Sound Toolkit is a cross-platform library written by K&#229;re Sj&#246;lander of the Swedish Royal Technical University (KTH) with bindings for the scripting languages Tcl, Python, and Ruby. It provides audio I/O, audio analysis and processing functions, such as spectral analysis, pitch tracking, and filtering, and related graphics functions such as display of the sound [...]No related posts.]]></description> <content:encoded><![CDATA[<div
class="ad" style="float:left; padding:0 15px 15px 15px"><script type="text/javascript"><!--
google_ad_client = "pub-0091919875977192";
/* 336x280, skapad 2011-04-06 */
google_ad_slot = "0402496911";
google_ad_width = 336;
google_ad_height = 280;
//-->
</script><script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div><p>Snack Sound Toolkit is a cross-platform library written by K&aring;re Sj&ouml;lander of the Swedish Royal Technical University (KTH) with bindings for the scripting languages Tcl, Python, and Ruby. It provides audio I/O, audio analysis and processing functions, such as spectral analysis, pitch tracking, and filtering, and related graphics functions such as display of the sound pressure waveform and spectrogram.</p><p>It is available on Microsoft Windows , Linux, Mac OS X, Solaris, HP-UX, FreeBSD, NetBSD, and IRIX.</p><p>Adapted from the Wikipedia article Snack Sound Toolkit, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki</p><p>No related posts.</p>]]></content:encoded> <wfw:commentRss>http://www.morphosppc.com/article/snack-sound-toolkit-introduction/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Database Caching 42/179 queries in 3.276 seconds using disk: basic
Object Caching 3030/3275 objects using disk: basic
Content Delivery Network via Amazon Web Services: CloudFront: d3j1u3j0l3helq.cloudfront.net

Served from: www.morphosppc.com @ 2012-02-06 10:04:47 -->
