IEEE SOFTWARE Mavnune 2000 N7~N-7~~Qinniffinnn a 7Nnn IFFF the Netbsd Operating System Proprietary Unix-Like Although Several Problems Were Evi- Systems

Total Page:16

File Type:pdf, Size:1020Kb

IEEE SOFTWARE Mavnune 2000 N7~N-7~~Qinniffinnn a 7Nnn IFFF the Netbsd Operating System Proprietary Unix-Like Although Several Problems Were Evi- Systems ..................mm .. .........e........ I Computer Science Classes In 1993, the Jesus M. ConxirlmBarahona, Pedro delaeHeras-Quiibs,Jose Centeno&mhIez, authors began us- Vicente Matdhn-Oliverr, and Francisco 1. Ballesteros, ihg]tian CU~OSUniverszty, S~UWZ ing 386BSD to uring 1991 and 1992, the landscape of libre software, and of teach computer science classes at software development in general, was ready for a change. In two Madrid’s Carlos different communities, two very exciting events were taking III University, in place: 386BSD, a libre derivative of the BSD code, was born, and Spain. Seven years Linus Torvalds distributed the first versions of the Linux kernel. Soon after, later, NetBSD and D GNU/Linux are the software community had two libre operating systems at its disposal (for the operating sys- some basic references to online information on libre products and distribu- tems of choice for tion, see the “Online Resources” and “Terminology” sidebars). several of the Uni- versity’s computer In late 1992 at Carlos I11 University, we both GNU/Linux and 386BSD were reason- science teaching were introducing new computer science ably stable platforms. laboratories. studies and planning a distributed systems course. We were looking for a software History of the Unix Lab platform suitable for practical lectures on After a testing period, we established a sta- distributed systems (our practical lectures ble environment that several students helped take place in a computer lab and usually in- us maintain and improve. When the semester volve a programming exercise). Unfortu- started, a small group of around 20 students nately, we couldn’t afford workstations- used 3 86BSD to learn to build client-server we could only share a PC laboratory run- applications. The experiment was a success. ning MS-DOS, used to teach other The students, using the environment, were computer science subjects. Therefore, we productive and fulfilled the goal we had set: were pleased to discover that 386BSD could to build simple RPC-based applications. run on those PCs and already had the com- 386BSD exposed them to a system similar to plete environment we needed for the practi- Unix workstations but at a fraction of the cal lectures. We decided to give the new, ex- cost and with many new features-such as citing libre operating systems a chance- access to source code. 76 IEEE SOFTWARE MavNune 2000 n7~n-7~~qinniffinnn a 7nnn IFFF The NetBSD operating system proprietary Unix-like Although several problems were evi- systems. dent-the lack of a GUI and several com- The new environ- mon applications, difficulties with main- ment was much more tenance, and trouble with some of the hard- user-friendly. We in- ware devices-we decided to continue using stalled XFree86 in systems based on libre software. After con- every computer, with a sidering GNU/Linux, we selected NetBSD, a GUI that provided a successor of 386BSD, as the new operating faster learning curve system for several reasons: for students. We also installed new applica- tions, many of them with a GUI. Familiarity: Our background was mainly in BSD-derived systems, such as SunOS. The switch to GNU/Linux Quality: BSD’s networking code was said In 1997, the department decided to renew to be better, especially regarding NFS. and expand the Unix Lab. Because of the so- Availability of bibliographies: books cial pressure for moving toward GNU/Linux, about BSD and its networking code were we decided to install it instead of NetBSD in widely known.1J the new hardware. Among the many distri- butions of GNULinux, we considered Red- We didn’t consider any proprietary sys- Hat, Slackware, and others, but we chose tems, in part because of budget constraints, Debian because of but also because it was obvious to us at the time that NetBSD, and perhaps GNU/Linux, I its development model, which was based were technically the best available Unix-like on hundreds of developers spread around systems for PCs. the world; We compiled most of the applications I the number of included applications- from source code, because NetBSD lacked a around 1,000 at the time; collection of binary packages. Therefore, a I the development team’s spirit, open to lot of source code was always around, and external suggestions and fully commit- interested students could look at the code ted to libre software; and that experienced programmers had writ- H advanced package management tools, ten-an activity uncommon in Spain (and in which simplified large-scale upgrades. many other parts of the world) at that time. In 1994, our department allocated funds The new Unix Lab required no funding for buying new PCs and developing the for buying software, letting us allocate addi- Unix Lab. Thus, we introduced our first li- tional funds to improved networking hard- bre software laboratory. We devoted the ware and multimedia equipment. This let next two years to improving the Unix Lab- students use MBone applications for estab- further integrating it with classroom work lishing, for instance, video conferences. and lectures and polishing the user interface. The switch to GNULinux has proven Although GNU/Linux was quickly becom- beneficial for students, because it is more ex- ing a viable alternative, we were still com- tensively used in Spain than NetBSD and is mitted to BSD derivatives and, in particular, much easier to obtain. Currently, the lab runs to NetBSD. However, students started ask- Debian 2.1 (which includes almost 2,000 ing for GNU/Linux, and colleagues in the packages), with an improved GUI based on Computer Science Department pressured us Gnome. More and more teachers (in com- to switch so they could run Linux-only ap- puter science departments and elsewhere) are plications. Looking back, it is astounding using or planning to use GNU/Linux for their that we had almost no pressure to switch to practical assignments, and we are sharing our May/June 2000 IEEE SOFTWARE 77 Jesus M. Gonxalez Barahona teaches at the King Juan Carlos University, Mostoles, Spain. He ioined the Computer Science Department of the Carlos 111 University, Leganes, in 1992, where he worked until September 1999. His current research interests are they gained immense learning value by being distributed systems, multicasl protocols, and fault-tolerant systems. He is also interested in the technical and teaching implications of libre software. He received his PhD in telecommunication able to inspect the internals of the software engineering from Universidad Politecnica of Madrid. He is a member of the IEEE Computer So- and system. ciety and of AT1 (Association of Computing Technicians). Contact him al Similarly, all the teaching materials (in- [email protected] or [email protected]. cluding the software) are available to stu- dents and colleagues at other universities Pedro de-las-HerasQuiros teaches at the King Juan Carlos University, Mostoles, Spain. He worked at the Computer Science Department of Carlos 111 University, Leganes, until without restrictions. We can thus easily share Oclober 1999. His research interests include distributed systems, fault tolerance, and large- our teaching tools and techniques with col- scale network protocols and applications. He is also interested in the impad of libre software leagues. Another advantage is that libre soft- in the software industry and academic circles. He earned an MS in computer science from the Universidad Politecnica of Madrid and expects to receive a PhD in computer science during ware ensures “brand-neutral” teaching-any 2000 from the same University. He is a member of the IEEE, ACM, and ATI. Contact him at reseller can provide the software because no [email protected]. one owns it. This way, the University doesn’t endorse any particular brand or company. Jose Centeno-GonzAlexteaches at the King Juon Carlos University, Mostoles, Spain. Also, source code availability for computer He ioined the Computer Science Departmenl of Carlos 111 University, Leganes, in 1993, where he worked until September 1999. His research interests include distributed-systems program- science students is extremely important so ming, and protocols for distributed systems. He is also interested in the impact of libre soft- they can learn how other programmers solve ware on computer science teaching and industry. He graduated from Universidad Politecnica of common problems. Because of the availability Madrid with an MS in electrical engineering and expects to receive a PhD in computer science from the same university this year. Contact him a1 [email protected]. of source code, we were able to customize and adapt the software to our environment. This included porting rare applications to the operating system we were using. Vicente Matellan Olivera teaches at the King Juan Carlos University, Mostoles, Another positive side effect is extremely Spain. He ioined the Computer Science Department of Carlos 111 University, Leganes, in 1993, where he worked until September 1999. He is interested in muhiagent and distributed systems low software costs. Funding for software and has worked on applying these topics in robotics. He received his PhD in computer science laboratories is limited, and with libre soft- from the Universidad Politecnica of Madrid. He is a member of the IAS (Intelligent Autonomous ware, the only significant costs are hard- Systems) and All (Association of Computer Science Graduates). Contact him at vmoQgsyc. escet.uric.es. ware and maintenance. In addition, the libre software develop- ment model ensures that if a product has a Francisco 1. Ballesteros does research on distributed and adaptable operating strong enough user base, it will maintain systems and teaches operating systems and advanced programming courses at the King Juan high quality standards. Among libre soft- Carlos University, Mostoles, Spain. He received his PhD in computer science from Universidad ware programs, there is a range of technical Politecnica of Madrid.
Recommended publications
  • Openbsd and Soekris
    OpenBSD and Soekris UUASC meeting June 3, 2004 Presented by Arild Jensen Outline ● What is OpenBSD and where do I get it? ● Built-in security features ● Maintaining an OpenBSD system ● The PF packet filter Outline (cont'd) ● What is Soekris and where do I get it? ● Different models and accessories ● Getting OpenBSD onto a Soekris box ● Maintaining a Soekris/OpenBSD solution What is OpenBSD? History BSD Net/2 (4.3BSD Lite) NetBSD 0.8 386BSD 0.0 NetBSD 0.9 386BSD 0.1 4.4BSD Lite 1 NetBSD 1.0 386BSD 1.0 NetBSD 1.1 OpenBSD FreeBSD What is OpenBSD? From the creators: “...freely available, multi- platform 4.4BSD-based UNIX-like OS.” Emphasis on: ● Portability ● Standardization ● Correctness ● Proactive Security ● Integrated Cryptography ...and where do I get it? www.openbsd.org CD sales only No .iso downloads $40 Portability ● i386 ● MVME68k ● Sparc ● MVME88k ● Sparc64 ● AMD64 ● HP300 ● CATS (ARM) ● Mac68k ● MacPPC ● HPPA Standardization The Story of CARP ● Firewall failover desired ● IEEE VRRP (Virtual router redundancy protocol) ● Cisco patents involved, HSRP protocol ● Cisco and Alcatel dispute ● Birth of CARP (Common address redundancy protocol ● Early implementation included in OpenBSD 3.5 Correctness The Audit Process ● 6-12 member security team ● Continuous audit of code multiple times by different people ● Security holes and common errors ● Result: Newly discovered bugs often already fixed in OpenBSD Pro-active Security Source Code Run Time ● ProPolice ● Privilege Separation – Buffer overflow – Avoid running as root protection – Dual-process setup – Similar to Stackguard – Daemons being ● W^X converted – Write xor Execute ● Chroot – Fine-grained memory – Apache /var/www permission layout – BIND /var/named – Only on some architectures Cryptography ● Based outside of U.S.
    [Show full text]
  • Absolute BSD—The Ultimate Guide to Freebsd Table of Contents Absolute BSD—The Ultimate Guide to Freebsd
    Absolute BSD—The Ultimate Guide to FreeBSD Table of Contents Absolute BSD—The Ultimate Guide to FreeBSD............................................................................1 Dedication..........................................................................................................................................3 Foreword............................................................................................................................................4 Introduction........................................................................................................................................5 What Is FreeBSD?...................................................................................................................5 How Did FreeBSD Get Here?..................................................................................................5 The BSD License: BSD Goes Public.......................................................................................6 The Birth of Modern FreeBSD.................................................................................................6 FreeBSD Development............................................................................................................7 Committers.........................................................................................................................7 Contributors........................................................................................................................8 Users..................................................................................................................................8
    [Show full text]
  • A Brief Technical Introduction
    Mac OS X A Brief Technical Introduction Leon Towns-von Stauber, Occam's Razor LISA Hit the Ground Running, December 2005 http://www.occam.com/osx/ X Contents Opening Remarks..............................3 What is Mac OS X?.............................5 A New Kind of UNIX.........................12 A Diferent Kind of UNIX..................15 Resources........................................39 X Opening Remarks 3 This is a technical introduction to Mac OS X, mainly targeted to experienced UNIX users for whom OS X is at least relatively new This presentation covers primarily Mac OS X 10.4.3 (Darwin 8.3), aka Tiger X Legal Notices 4 This presentation Copyright © 2003-2005 Leon Towns-von Stauber. All rights reserved. Trademark notices Apple®, Mac®, Macintosh®, Mac OS®, Finder™, Quartz™, Cocoa®, Carbon®, AppleScript®, Bonjour™, Panther™, Tiger™, and other terms are trademarks of Apple Computer. See <http://www.apple.com/legal/ appletmlist.html>. NeXT®, NeXTstep®, OpenStep®, and NetInfo® are trademarks of NeXT Software. See <http://www.apple.com/legal/nexttmlist.html>. Other trademarks are the property of their respective owners. X What Is It? 5 Answers Ancestry Operating System Products The Structure of Mac OS X X What Is It? Answers 6 It's an elephant I mean, it's like the elephant in the Chinese/Indian parable of the blind men, perceived as diferent things depending on the approach X What Is It? Answers 7 Inheritor of the Mac OS legacy Evolved GUI, Carbon (from Mac Toolbox), AppleScript, QuickTime, etc. The latest version of NeXTstep Mach, Quartz (from Display PostScript), Cocoa (from OpenStep), NetInfo, apps (Mail, Terminal, TextEdit, Preview, Interface Builder, Project Builder, etc.), bundles, faxing from Print panel, NetBoot, etc.
    [Show full text]
  • Mac OS X Intro for UNIX Users
    Mac OS X An Introduction for UNIX Users Leon Towns-von Stauber, Occam's Razor Seattle BSD Users Group, October 2004 http://www.occam.com/osx/ X Contents Opening Remarks.............................3 Where Did Mac OS X Come From?.....5 What is Mac OS X?..........................13 A New Kind of UNIX........................25 A Different Kind of UNIX.................28 Why Use Mac OS X?.........................60 Resources.......................................63 Closing Remarks.............................67 X Opening Remarks 3 This is a technical introduction to Mac OS X, mainly targeted to experienced UNIX users for whom OS X is at least relatively new Some emphasis on comparisons with FreeBSD I'm assuming basic familiarity with operating system design Where I'm coming from: UNIX user and some-time admin since 1990 Full-time UNIX admin since 1995 NeXTstep user and admin since 1991 This presentation covers primarily Mac OS X 10.3.5 (Darwin 7.5) X Legal Notices 4 This presentation Copyright © 2003-2004 Leon Towns-von Stauber. All rights reserved. Trademark notices Apple®, Mac®, Macintosh®, Mac OS®, Aqua®, Finder™, Quartz™, Cocoa®, Carbon®, AppleScript®, Rendezvous™, Panther™, and other terms are trademarks of Apple Computer. See <http:// www.apple.com/legal/appletmlist.html>. NeXT®, NeXTstep®, OpenStep®, and NetInfo® are trademarks of NeXT Software. See <http://www.apple.com/legal/nexttmlist.html>. PowerPC™ is a trademark of International Business Machines. Java™ is a trademark of Sun Microsystems. Other trademarks are the property of their
    [Show full text]
  • Openafs: BSD Clients 2009
    OpenAFS: BSD Clients 2009 Matt Benjamin <[email protected]> OpenAFS: BSD Clients 2009 Who am I? ● OpenAFS developer interested in various new-code development topics ● for the last while, “portmaster” for BSD clients except DARWIN/MacOS X ● involves evolving the ports, interfacing withusers and port maintainers in the BSD communities OpenAFS: BSD Clients 2009 Former Maintainers ● Tom Maher, MIT ● Jim Rees, University of Michigan (former Gatekeeper and Elder) ● Garret Wollman, MIT OpenAFS: BSD Clients 2009 Other Active ● Ben Kaduk (FreeBSD) ● Tony Jago (FreeBSD) ● Jamie Fournier (NetBSD) OpenAFS: BSD Clients 2009 Historical Remarks ● AFS originated in a BSD 4.2 environment ● extend UFS with coherence across a group of machines ● Terminology in common with BSD, SunOS, etc, e.g., vnodes ● Followed SunOS and Ultrix to Solaris and Digital Unix in Transarc period ● 386BSD released at 4.3 level in the Transarc period, some client development never publically released (or independent of Transarc) OpenAFS: BSD Clients 2009 BSD Clients Today ● Descendents of 386BSD distribution and successors, not including DARWIN/MacOS X ● DARWIN separately maintained, though of course there are similarities OpenAFS: BSD Clients 2009 Today ● FreeBSD ● OpenBSD Soon ● NetBSD ● OpenBSD Not yet supported (as a client): ● Dragonfly BSD OpenAFS: BSD Clients 2009 BSD Port History I ● First 386BSD port probably that of John Kohl (MIT), for NetBSD ● First to appear in OpenAFS is FreeBSD, by Tom Maher ● Next to appear in OpenAFS is OpenBSD, by Jim Rees ● Significant evolution
    [Show full text]
  • History of Unix.Pdf
    History of Unix In order to define UNIX, it helps to look at its history. In 1969, Ken Thompson, Dennis Ritchie and others started work on what was to become UNIX on a "little-used PDP-7 in a corner" at AT&T Bell Labs. For ten years, the development of UNIX proceeded at AT&T in numbered versions. V4 (1974) was re-written in C -- a major milestone for the operating system's portability among different systems. V6 (1975) was the first to become available outside Bell Labs -- it became the basis of the first version of UNIX developed at the University of California Berkeley. Bell Labs continued work on UNIX into the 1980s, culminating in the release of System V (as in "five," not the letter) in 1983 and System V, Release 4 (abbreviated SVR4) in 1989. Meanwhile, programmers at the University of California hacked mightily on the source code AT&T had released, leading to many a master thesis. The Berkeley Standard Distribution (BSD) became a second major variant of "UNIX." It was widely deployed in both university and corporate computing environments starting with the release of BSD 4.2 in 1984. Some of its features were incorporated into SVR4. As the 1990s opened, AT&T's source code licensing had created a flourishing market for hundreds of UNIX variants by different manufacturers. AT&T sold its UNIX business to Novell in 1993, and Novell sold it to the Santa Cruz Operation two years later. In the meantime, the UNIX trademark had been passed to the X/Open consortium, which eventually merged to form The Open Group.1 While the stewardship of UNIX was passing from entity to entity, several long- running development efforts started bearing fruit.
    [Show full text]
  • UNIX History Page 1 Tuesday, December 10, 2002 7:02 PM
    UNIX History Page 1 Tuesday, December 10, 2002 7:02 PM CHAPTER 1 UNIX Evolution and Standardization This chapter introduces UNIX from a historical perspective, showing how the various UNIX versions have evolved over the years since the very first implementation in 1969 to the present day. The chapter also traces the history of the different attempts at standardization that have produced widely adopted standards such as POSIX and the Single UNIX Specification. The material presented here is not intended to document all of the UNIX variants, but rather describes the early UNIX implementations along with those companies and bodies that have had a major impact on the direction and evolution of UNIX. A Brief Walk through Time There are numerous events in the computer industry that have occurred since UNIX started life as a small project in Bell Labs in 1969. UNIX history has been largely influenced by Bell Labs’ Research Editions of UNIX, AT&T’s System V UNIX, Berkeley’s Software Distribution (BSD), and Sun Microsystems’ SunOS and Solaris operating systems. The following list shows the major events that have happened throughout the history of UNIX. Later sections describe some of these events in more detail. 1 UNIX History Page 2 Tuesday, December 10, 2002 7:02 PM 2 UNIX Filesystems—Evolution, Design, and Implementation 1969. Development on UNIX starts in AT&T’s Bell Labs. 1971. 1st Edition UNIX is released. 1973. 4th Edition UNIX is released. This is the first version of UNIX that had the kernel written in C. 1974. Ken Thompson and Dennis Ritchie publish their classic paper, “The UNIX Timesharing System” [RITC74].
    [Show full text]
  • BSD Intro Lecture
    Short history • Based on: http://www.levenez.com/unix/ • 1978 – BSD (Barkeley software distribution) Based on unix system developed by Bell. • 1991 – 386BSD – BSD port to Intel (Based on 4.3BSD). • 1991 – Linux based on Minix. • 1993 – FreeBSD and NetBSD Based on 386BSD. • 1995 - OpenBSD splits from NetBSD. • 2001 – Apple’s Darwin, based on FreeBSD. • Latest releases: 5.3, 4.11. • The most popular of the *BSDs. • Historically aimed for maximum. performance on X86. Now supports most of the popular hardware platforms. • Biggest installations: Yahoo servers, ftp.cdrom.com, www.netcraft.com. • “Of course it runs NetBSD” • Last version: NetBSD 2.0. • Aims for supporting as many architectures possible. • Portable design. • 40 supported architectures. • www.openbsd.org • Current version: OpenBSD 3.6. • “Try to be the #1 most secure operating system“. • “Secure by default”. • Based on Canada – is not restricted by US export laws. • developer.apple.com/darwin/projects/darwin/ • The operating system behind Apple’s MAC OS X. • Based on FreeBSD. • Apple’s cool GUI, on top of a reliable Open source unix. • Runs on PowerPC based Macintosh. • Version for X86 is also available. Licensing Issues • Linux – GPL Must publish your source code if your code is based on a GPLd software. • *BSD - BSD license. • Do what ever you want, just give us credit. • Poul Henning Kamp - Beerware license Do what ever you want, just buy me beer when we meet. FreeBSD – The people behind • FreeBSD Core Team – The board of directors. • FreeBSD Committers – The programmers. • Release Engineering Teams • Documentation engineering team • Port management team. • Donations Team. FreeBSD – The people behind cont’ • Technical Review Board.
    [Show full text]
  • Limits and the Practical Usability of Bsds, a Big Data Prospective
    Limits and the Practical Usability of BSDs, a Big Data Prospective Predrag Punosevacˇ [email protected] The Auton Lab Carnegie Mellon University June 11, 2016 1 / 22 Thanks Thanks to organizers for this great meeting and for giving me the op- portunity to speak. note 1 of slide 1 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ❖ General Limitations ❖ Scientific Computing ❖ Continuation ❖ misc issues ❖ NetBSD ❖ OpenBSD ❖ pf.conf and pfctl ❖ OpenBSD cons ❖ FreeBSD ❖ TrueOS ❖ TurnKey Appliance ❖ FreeNAS ❖ pfSense ❖ DragonFly BSD ❖ HAMMER ❖ Dark Clouds ❖ References 2 / 22 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ● What is the Auton Lab? ❖ General Limitations ❖ Scientific Computing ❖ Continuation ❖ misc issues ❖ NetBSD ❖ OpenBSD ❖ pf.conf and pfctl ❖ OpenBSD cons ❖ FreeBSD ❖ TrueOS ❖ TurnKey Appliance ❖ FreeNAS ❖ pfSense ❖ DragonFly BSD ❖ HAMMER ❖ Dark Clouds ❖ References 2 / 22 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ● What is the Auton Lab? ❖ General Limitations ❖ Scientific ● Why don’t we just use SCS computing facilities? Computing ❖ Continuation ❖ misc issues ❖ NetBSD ❖ OpenBSD ❖ pf.conf and pfctl ❖ OpenBSD cons ❖ FreeBSD ❖ TrueOS ❖ TurnKey Appliance ❖ FreeNAS ❖ pfSense ❖ DragonFly BSD ❖ HAMMER ❖ Dark Clouds ❖ References 2 / 22 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ● What is the Auton Lab? ❖ General Limitations ❖ Scientific ● Why don’t we just use SCS computing facilities? Computing ❖ Continuation ❖ misc issues ● How did
    [Show full text]
  • BSD Based Systems
    Pregled BSD sistema I projekata Glavne BSD grane FreeBSD Homepage: http://www.freebsd.org/ FreeBSD je Unix-like slobodni operativni sistem koji vodi poreklo iz AT&T UNIX-a preko Berkeley Software Distribution (BSD) grane kroz 386BSD i 4.4BSD. Radi na procesorima kompatibilnim sa Intel x86 familijom procesora, kao I na DEC Alpha, UltraSPARC procesorima od Sun Microsystems, Itanium (IA-64), AMD64 i PowerPC procesorima. Radi I na PC-98 arhitekturi. Podrska za ARM i MIPS arhitekture je trenutno u razvoju. Početkom 1993. godine Jordan K. Hubbard, Rod Grimes i Nate Williams su pokrenuli projekat čiji je cilj bio rešavanje problema koji su postojali u principima razvoja Jolitzovog 386BSD-a. Posle konsultovanja sa tadašnjim korisnicima sistema, uspostavljeni su principi i smišljeno je ime - FreeBSD. Pre nego što je konkretan razvoj i počeo, Jordan Hubbard je predložio je firmi Walnut Creek CDROM (danas BSDi) da pripreme distribuiranje FreeBSD-a na CD-ROM-ovima. Walnut Creek CDROM su prihvatili ideju, ali i obezbedili (tada potpuno nepoznatom) projektu mašinu na kojoj će biti razvijan i brzu Internet konekciju. Bez ove pomoći teško da bi FreeBSD bio razvijen u ovolikoj meri i ovolikom brzinom kao što jeste. Prva distribucija FreeBSD-a na CD-ROM-ovima (i naravno na netu) bila je FreeBSD 1.0, objavljena u decembru 1993. godine. Bila je zasnovana na Berkeley-evoj 4.3BSD-Lite ("Net/2") traci, a naravno sadržala je i komponente 386BSD-a i mnoge programe Free Software Foundation (fondacija besplatnog- slobodnog softvera). Nakon što je Novell otkupio UNIX od AT&T-a, Berkeley je morao da prizna da Net/2 traka sadrži velike delove UNIX koda.
    [Show full text]
  • Operating Systems. Lecture 2
    Operating systems. Lecture 2 Michał Goliński 2018-10-09 Introduction Recall • Basic definitions – Operating system – Virtual memory – Types of OS kernels • Booting process – BIOS, MBR – UEFI Questions? Plan for today • History of Unix-like systems • Introduction to Linux • Introduction to bash • Getting help in bash • Managing files in bash History History of Unix-like systems • 1960s – Multics (MIT, AT&T Bell Labs, General Electric) • 1960s/1970s – UNIX (Ken Thompson, Dennis Ritchie) 1 PDP-7 History of UNIX-like systems • 1970s, 1980s – popularization, standardization and commerciallization of UNIX • 1983 – the GNU Project is stared 2 • 1988 – the first version of the POSIX standard History of Unix-like systems • 1991 – the first version of a Unix clone – Linux (Linux is not Unix) • 1992 – the license is fixed as GPLv2 • 1996 – version 2.0, supporting many processors • 2003 – version 2.6, new scheduler, much better with multiprocessor machines, preemptive kernel, rewriting code to not depend on the so- called Big Kernel Lock • if the version scheme had not been changed, the current kernel (4.18) would be 2.6.78 Genealogy 1969 Unnamed PDP-7 operating system 1969 Open source 1971 to 1973 Unix 1971 to 1973 Version 1 to 4 Mixed/shared source 1974 to 1975 Unix 1974 to 1975 Version 5 to 6 PWB/Unix Closed source 1978 1978 BSD 1.0 to 2.0 Unix 1979 Version 7 1979 Unix/32V 1980 1980 BSD 3.0 to 4.1 1981 Xenix System III 1981 1.0 to 2.3 1982 1982 Xenix 3.0 1983 BSD 4.2 SunOS 1983 1 to 1.1 System V R1 to R2 1984 SCO Xenix 1984 Unix 1985 Version 8
    [Show full text]
  • Characterizing the Evolution of Operating Systems
    Copyright Warning & Restrictions The copyright law of the United States (Title 17, United States Code) governs the making of photocopies or other reproductions of copyrighted material. Under certain conditions specified in the law, libraries and archives are authorized to furnish a photocopy or other reproduction. One of these specified conditions is that the photocopy or reproduction is not to be “used for any purpose other than private study, scholarship, or research.” If a, user makes a request for, or later uses, a photocopy or reproduction for purposes in excess of “fair use” that user may be liable for copyright infringement, This institution reserves the right to refuse to accept a copying order if, in its judgment, fulfillment of the order would involve violation of copyright law. Please Note: The author retains the copyright while the New Jersey Institute of Technology reserves the right to distribute this thesis or dissertation Printing note: If you do not wish to print this page, then select “Pages from: first page # to: last page #” on the print dialog screen The Van Houten library has removed some of the personal information and all signatures from the approval page and biographical sketches of theses and dissertations in order to protect the identity of NJIT graduates and faculty. ABSTRACT CHARACTERIZING THE EVOLUTION OF OPERATING SYSTEMS By Yi Peng Examining the development and trends in software engineering technology is a huge undertaking. It is constantly evolving and affected by a large number of factors, which are themselves driven by a wide range of sub-factors. This dissertation is part of a long term project intended to analyze software engineering technology trends and how they evolve.
    [Show full text]