Many users and developers of BSD-based operating systems have a different position on licensing. The main difference is the belief that the copyleft licences, particularly the GNU General Public License (GPL), are undesirably complicated and/or restrictive. The GPL requires any derivative work that is released to be released according to the GPL while the BSD licence does not. Essentially, the BSD license’s only requirement is to acknowledge the original authors, and poses no restrictions on how the source code may be used. As a result, BSD code can be used in proprietary software that only acknowledges the authors. For instance, the IP stack in Microsoft Windows and Mac OS X are derived from BSD-licensed software.

Supporters of the BSD licence argue that it is more free than the GPL because it grants the right to do anything with the source code, second only to software in the public domain. This includes incorporating the BSD-licensed code in proprietary products. The approach has led to BSD code being used in common, widely used commercial software. In response, GPL supporters claim that the freedom of others to make non-free software from free software is an unjust form of power rather than a necessary freedom. However, some developers might want to include GPLed software in their products and can’t do it, simply because the GPL is incompatible with the licences of other software they include in their product, even if everything is open source.

Code licensed under a permissive free software licence, such as the BSD licence, can be incorporated into copylefted (e.g. GPL’d) projects. Such code is thus “GPL-compatible”. There is no need to secure the consent of the original authors. In contrast, code under the GPL cannot be relicensed under the BSD licence without securing the consent of all copyright holders. Thus the two licences are compatible, but the combination as a whole must be distributed under the terms of the GPL, not the permissive licence.

Existing free software BSDs tend to avoid including software licenced under the GPL in the core operating system, or the ”base system”, except as a last resort when alternatives are non-existent or vastly less capable, such as with GCC. (Indeed however, note that as of mid 2010 Apple for example are moving from GCC to the upcoming LLVM compiler, perhaps primarily for this reason.) The OpenBSD project has acted to remove GPL-licensed tools in favor of BSD-licensed alternatives, some newly written and some adapted from older code.

Adapted from the Wikipedia article Free software licence, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki

No related posts.

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.

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.

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 — 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.

Other operating systems ported to the PA-RISC architecture include Linux, OpenBSD, NetBSD and NEXTSTEP.

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.

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.

Adapted from the Wikipedia article PA-RISC, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki

No related posts.

CVS uses a client–server architecture: a server stores the current version(s) of a project and its history, and clients connect to the server in order to “check out” a complete copy of the project, work on this copy and then later “check in” their changes. Typically, the client and server connect over a LAN or over the Internet, but client and server may both run on the same machine if CVS has the task of keeping track of the version history of a project with only local developers. The server software normally runs on Unix (although at least the CVSNT server also supports various flavors of Microsoft Windows), while CVS clients may run on any major operating-system platform.

Several developers may work on the same project concurrently, each one editing files within their own “working copy” of the project, and sending (or ”checking in”) their modifications to the server. To avoid the possibility of people stepping on each others’ toes, the server will only accept changes made to the most recent version of a file. Developers are therefore expected to keep their working copy up-to-date by incorporating other people’s changes on a regular basis. This task is mostly handled automatically by the CVS client, requiring manual intervention only when an edit conflict arises between a checked-in modification and the yet-unchecked local version of a file.

If the check in operation succeeds, then the version numbers of all files involved automatically increment, and the CVS-server writes a user-supplied description line, the date and the author’s name to its log files. CVS can also run external, user-specified log processing scripts following each commit. These scripts are installed by an entry in CVS’s loginfo file, which can trigger email notification or convert the log data into a Web-based format.

Clients can also compare versions, request a complete history of changes, or check out a historical snapshot of the project as of a given date or as of a revision number.

Anonymous CVS

Many open-source projects allow “anonymous read access”, a feature pioneered by OpenBSD. This means that clients may check out and compare versions with either a blank or simple published password (e.g., “anoncvs”); only the check-in of changes requires a personal account and password in these scenarios.

Clients can also use the “update” command in order to bring their local copies up-to-date with the newest version on the server. This eliminates the need for repeated downloading of the whole project..

CVS can also maintain different “branches” of a project. For instance, a released version of the software project may form one branch, used for bug fixes, while a version under current development, with major changes and new features, can form a separate branch.

CVS uses delta compression for efficient storage of different versions of the same file. The implementation favors files with many lines (usually text files) – in extreme cases the system may store individual copies of each version rather than deltas.

Adapted from the Wikipedia article Concurrent Versions System, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki

No related posts.

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’s PhD advisor was Bob Fabry.

As a UC Berkeley graduate student, Joy worked for Fabry’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.

Some of his most notable contributions were the vi editor, NFS, and csh. Joy’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.

Eric Schmidt, CEO of Novell at the time, continued the mythopoesis during an interview in PBS’s documentary Nerds 2.0.1, inflating Bill Joy’s accomplishments as having personally rewritten the BSD kernel in a weekend.

Adapted from the Wikipedia article Bill Joy, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki

No related posts.

*M. Elizabeth Cannon (1984, 1991), B.Sc. and Ph.D. Former Dean and first female president of the U of C.

*Theo de Raadt (1992), B.Sc. Founder and leader of the OpenBSD and OpenSSH projects, degree in Computer Science.

*Mitchell C. Gallivan (1989), Master of Kinesiology M.K. Sports announcer for the Canadian Football League.

*James Gosling (1977), B.Sc. Inventor of the Java programming language, holds a Computer Science degree.

*Douglas R. Hamilton (1991), Ph.D. NASA flight surgeon and biomedical engineer.

*The Rt. Hon. Stephen Harper (1991), MA, B.A. Prime Minister of Canada and leader of the Conservative Party, holds degrees in Economics.

*Harold Kvisle (1981), MBA. President & CEO of TransCanada Corporation.

*Robert Thirsk (1976), B.Sc. Canadian Space Agency astronaut and NASA capsule communicator for the International Space Station program. Holds a Mechanical Engineering degree.

*D. George Wyse (1974), MD, FRCPC, Ph.D, Professor Emeritus in the Faculty of Medicine’s Department of Pharmacology and Therapeutics, University of Calgary, is a member of the Libin Cardiovascular Institute of Alberta. His research changed the way cardiac arrhythmia is treated globally.

Adapted from the Wikipedia article University of Calgary, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki

No related posts.

*Wi-Fi Protected Access (WPA and WPA2) used to secure Wi-Fi wireless networks

*Microsoft Windows Data Protection API (DPAPI)

*OpenDocument encryption used in OpenOffice.org

*[http://www.zetetic.net/software/sqlcipher SQLCipher], an encrypted variant of SQLite

*WinZip’s AES Encryption scheme.

*JBoss Seam Framework JpaIdentityStore.generatePasswordHash (as of 2.1.2)

*Grub 2, for password hashing.

Disk encryption software

*FileVault (Mac OS X) from Apple Computer

*FreeOTFE (Windows and Pocket PC PDAs); also supports mounting Linux (e.g. LUKS) volumes under Windows

*LUKS (Linux Unified Key Setup) (Linux)

*TrueCrypt (Windows, Linux, and Mac OS X)

*[http://netbsd.org/guide/en/chap-cgd.html Cryptographic disk] (NetBSD)

*GEOM ELI module for FreeBSD

*softraid crypto for OpenBSD

*EncFS (Linux) since v1.5.0

== External links

*[http://www.rsa.com/rsalabs/node.asp?id=2127 RSA PKCS #5] – RSA Laboratories PKCS #5 v2.0 – Multiple Formats, and test vectors.

*RFC 2898

Implementations

*[http://code.google.com/p/as3-pbkdf2/ ActionScript 3.0 implementation]

*[http://msdn.microsoft.com/en-us/library/system.security.cryptography.rfc2898derivebytes.aspx .NET's built-in function]

*[http://msdn.microsoft.com/en-us/magazine/cc163913.aspx C# implementation]

*[http://anandam.name/pbkdf2 JavaScript implementation (slow)] [http://code.google.com/p/crypto-js/ JavaScript implementation (fast)]

*[http://www.dlitz.net/software/python-pbkdf2 Python implementation]

*[http://github.com/emerose/pbkdf2-ruby/tree/master Ruby implementation]

*[http://www.openbsd.org/cgi-bin/cvsweb/src/sbin/bioctl/pbkdf2.c?rev=HEAD&content-type=text%2Fplain C implementation]

Category:Password authentication

Category:Cryptography standards

Adapted from the Wikipedia article PBKDF2, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki

No related posts.

* 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, SPARCstation 2, and SPARCstation IPX computer motherboard.

* 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).

* QEMU emulating Sun-4 architecture (sun4m) virtual network interface.

* GXemul with le(4) emulating ARM, MIPS, M88K, PowerPC, and SuperH CPU. One example architecture is DECstation 5000 (3max).

Adapted from the Wikipedia article AMD Lance Am7990, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki

No related posts.

Eläkeläiset (Finnish for “pensioners”) are a Finnish humppa band founded in 1993. They specialise in humppa and jenkka music and have been successful in Germany, Finland and elsewhere.

Current members of the band are Onni Waris (keyboard, vocals), Petteri Halonen (keyboard, guitar, vocals), Lassi Kinnunen (accordion, vocals), Martti Waris (bass, vocals) and Kristian Voutilainen (drums, vocals). Ilmari Koivuluhta (sound technique, logistics) and Pekka Jokinen (graphics, merchandise) complete the “humppa family”. According to the band’s statements, they play between 80 and 100 concerts per year, of which only 20 in Finland and 40 to 50 in Germany, due to their popularity there. Rarely performing in big venues, they have visited several big international music festivals, and surprisingly to many, even large heavy metal festivals e.g. Wacken Open Air and Tuska Open Air. They travel mostly on a private lorry and no bus.

Eläkeläiset mainly play cover versions of famous pop and rock hits in a fast humppa or slow jenkka style (both sound somewhat similar to polka music the way “Weird Al” Yankovic plays it) with Finnish lyrics — the original songs are barely recognizable. They also publish bootleg recordings of their own concerts.

Eläkeläiset are very popular among some OpenBSD developers and frequently played at their hackathons, where they claim they are “thwarting evil with humppa and math.”

Eläkeläiset was one of the nominees to represent Finland in Eurovision Song Contest 2010.

Adapted from the Wikipedia article Eläkeläiset, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki

No related posts.

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 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.

Macintosh OS

From the 1984 Super Bowl advertisement and “Test Drive a Macintosh” 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.

Microsoft Windows

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].

NetBSD

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 “powered by” logo with a license permitting use on any product running NetBSD.

OpenBSD

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’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 “Free, Functional & Secure”, “Secure by default”, and “Power. Security. Flexibility.” Each OpenBSD release features an original song and a variety of artwork.

OS/2

OS/2 is the only operating system which saw the creation of a semi-formal advocates organization. Named ”Team OS/2”, 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.

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 “new IBM” – a few employees who took “empowerment” seriously, able to coordinate their efforts through participation in TEAMOS2 FORUM, an internal IBM discussion group) – and passionate supporters outside IBM who adopted the ideas and modeled the behaviors of those who were early activists within IBM.

Adapted from the Wikipedia article Operating system advocacy, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki

No related posts.

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.

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 “web-based” 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.

Adapted from the Wikipedia article OpenVPN, under the G. N. U. Free Documentation License. Please also see http://en.wikipedia.org/wiki

No related posts.