DOCSLIB.ORG

A Complete Bibliography of Publications in Software—Practice and Experience

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Complete Bibliography of Publications in Software—Practice and Experience A Complete Bibliography of Publications in Software|Practice and Experience Nelson H. F. Beebe University of Utah Department of Mathematics, 110 LCB 155 S 1400 E RM 233 Salt Lake City, UT 84112-0090 USA Tel: +1 801 581 5254 FAX: +1 801 581 4148 E-mail: [email protected], [email protected], [email protected] (Internet) WWW URL: http://www.math.utah.edu/~beebe/ 23 July 2021 Version 3.26 Title word cross-reference [Bar82a, Bar82c, Bar84b]. < [SMGMOFM07a, SMGMOFM07b]. > [SMGMOFM07a, SMGMOFM07b]. 2 [MST13, MDB19]. 3 [DS09]. 4 [MSR+07]. \ 0 [GW96]. 1 [GW96]. $1.50 [Bar78d]. $11 [PK04]. TM [MZB00, Win02]. 8 [DB21b]. k [Bar84a]. $12.00 [Rob72]. $13 [Bar84a]. [AW93, Mer93]. κ [MG94]. µ $13.00 [Rob72]. $18.50 [Jon74]. $185 [BS90c, BDS+92, SMNB21]. N [Bar79b]. $19.30 [Lan74a]. $19.50 [Dav78]. [MS98, Coh98, KST94, YAVHC21]. P 3 $25.00 [Pet77, And78]. 3 [BE02, FMA02]. [DC03]. PM [CLD+17]. q [GSR17]. τ $31-25 [Pet77]. $31.35 [Bri82]. 32 [VED06]. 2:5 [TSZ14, UDS+07]. $35.00 [Inc86]. $39.50 [Sim83]. 5 [CPMAH+20]. $58.50 [Wal81a]. $6.95 -ary [MS98]. -bit [AM10, SF85, VED06]. [Tho74]. 64 [AM10, VED06]. 68 -gram [Coh98, KST94, YAVHC21]. -grams [Ear76, Hol77]. $68.25 [Pit82]. $7.00 [GSR17]. -level [FM77]. -queens [Plu74]. [Bar72a]. $7.50 [Bar78d]. $7.95 -R [Ear76, Hol77]. -shortest-paths [MG94]. [Bar76a, Lav77]. $78.50 [Sim83]. 8 -System [BS90c]. [Plu74, SF85]. $8.95 [Bar82a, Bar82c, Bar84b]. $9.75 . [Bis81b]. .NET [Coo04, Han04]. [Bar77e, Mul76]. $9.80 [Atk79a]. $9.95 1 2 0 [Bar81, Edw98a, Edw98b, Gru83, Llo82, 2 [Bar74a, Bar74b, Bar80b, Bud85, Cor88b, Val77a, Val78, Wal83b]. 0-12-380230-X Dun75, Fos86, Gut87, Hop80b, MS74a, [Dea86]. 0-13-751975-3 [Edw98a, Edw98b]. OSW92, Pro92, Rai81, Tag88, Ter86, 0-201-03822-6 [Llo82]. 0-201-08571-2 UGBW91, Val76b, Wal83b, Woo86, Hun72, [Wal83b]. 0-201-13787-9 [Gru83]. Mee87, Ano87a, Bow88, Bar78b]. 2-75 0-387-10256-6 [Cav83a]. 0-387-9642 [Lav78]. 2.0 [Hsu12]. 2.0-based [Hsu12]. [Mee87]. 0-471-19161-2 [Cor99a, Cor99b]. 2.25 [Atk83, Cou84b]. 2.50 0-471-87834-0 [Ano87a]. 0-471-88311-5 [Bar73d, Bar75c, Jac71]. 2.55 [Bar73b]. 2.6 [Ano88c]. 0-471-89052-9 [Ree84b]. [TCM07]. 2.65 [Bul72a]. 2.95 0-471-91128-3 [Ano88a]. 0-471-91754-0 [Cou84a, Tho77]. 20 [Liv75]. 20.00 [CO88]. 0-521-21965-5 [Bar81]. [Gar86, Wil87]. 2010 [Obe11]. 2011 0-521-30689-2 [Lon88]. 0-521-31423-2 [BN13, PL14]. 205 [LS84]. 22.50 [Rob82a]. [Lon88]. 0-632-01309-5 [Rop88a]. 25 [Val77b]. 25p [Bar73a]. 2900 0-632-01609-4 [Bow88]. 0-7204-0437-1 [EP79, Iza80]. 2D [BBGP01]. 2nd [Val78]. 0-7204-2802-5 [Val77a]. [Bar75a, Bul72a, Cou84a, Llo82, McD71]. 0-7458-0092-0 [Mar88]. 0-7458-0110-2 [Vel88]. 0-85012-612-6 [Rop88b]. 3 [Bar72c, Edw98a, Edw98b, Hun72, Oes71]. 0-85312-846-4 [Sto88]. 0.90 [Bar75a]. 3-540-10256-6 [Cav83a]. 3.10 [Bar71]. 3.15 [McD71]. 3.30 [Bar76e]. 3.50 1 [BH87, Col72b, Hus86, Les72, Pal74, [Bar78c, Bis79a, Nic72, Wis74]. 3.75 SHR80, Val78, Yuv77a, Wis74, Nic72]. [Bar76d, Hut74, Mil72]. 3.95 [Han78b]. 30 1-85058-035-9 [Ano88b]. 1-like [EBD+74]. [XZ01, XZ03]. 30.00 [Bar83a]. 315 1.50 [Bar72b]. 1.60 [Eve73]. 1.65 [Bar74c]. [Pra96a, Pra96b]. 32.10 [Ano88c]. 336 1.75 [Wel72]. 1.9 [Kur78]. 1.90 [Bar74f]. [Fen94a]. 360 [Haz74, RS76, Haz72, Lar71]. 10.50 [Rob82b]. 10.75 [Ree82, Wal83c]. 370 [BB75]. 39.95/$32.08 10/LSD [Les72]. 103 [Whi87]. 10646 [Cor99a, Cor99b]. 3D [Wu01]. 10th [WCK11]. 11' [MTT83, Woo71, XAN07]. [Hay80, BLLP04, DM84, GKM90, HGWBS75, Mat80]. 11-11 [BLLP04]. 11.20 4 [Lar75a]. 4.00 [Bar74d, Han78a, Rog74]. [Val80]. 11.70 [Bar79a]. 11.80 [Bry77]. 4.20 [Bar75f]. 4.25 [Eme84]. 4.40 [Haz72]. 11.95 [Jac84]. 12 [CST75]. 122 [SFS97c]. 4.50 [Haz71, HW77, Rop88b]. 4.80 [Rog71]. 13.50 [Rop88a]. 13.95 [CO88, Wil84b]. 130 4.85 [Bul73]. 4.95 [Atk79b, Col77b, Ree76]. [Hal82]. 14 [Val79]. 14.00 [Bra80]. 14.20 40 [Bar76b, Bul72b, Rog73, Wil74a]. 450 [Wal84b]. 14.95 [Bra75]. 15 [KP94]. 15.00 [Bis86]. [For72, Roh77a]. 15.50 [Ree84b]. 15.95 [Cam85]. 16.50 [Vel88]. 18.50 5 [Bar77c, Bar81, LG73, Val77a]. 5-50 [Mar88, Sha83]. 19 [KRK21]. 19.50 [Bar77c]. 5.00 [Wic72a]. 5.25 [Dea86, Sto88, Wal86b]. 190 [Her84]. 1900 [Ano73a, Lan75, Ros74]. 5.50 [Far74, NY78, REC75, WQ72]. 1969 [Bar73e, Bar78b, Wan82]. 5.75 [Rob72]. 1971 [Bar73e]. 1973 [Val77a]. [Han72, Mer74]. 5.90 [Ken77]. 5.95 1975 [Val78]. 1980 [Bis81a]. 1982 [Bar80d, Edm82]. 50 [Bar77c]. 56th [Bar83a, Bar83a]. 1998 [Wri98]. 1A [Wit83]. [Bar82a, Bar82c, Bar84b]. 5G [BSDF20]. 1D [MV95]. 1D-FFT [MV95]. 6 [Lar71, Llo82]. 6.00 [Bar75b, Ree73]. 6.25 3 [Bar73c, Bar75d]. 6.50 [Bar75e, Hop74]. Wil72, Wil87, Bar77d, BLC19, Han77a]. 6.75 [Sha72, Wil72]. 6.95 [Bis84]. 60 Academics [Ano71e]. accelerated [HSW75, Hut76, Wic72b, WJ76, Wil76]. [NPHJ18]. Accelerating [TT82]. 6000 [Bak72, Rob79, Yuv77a, Yuv77c]. Acceptance [Mat83b, WWB03]. Access 6000-Series [Bak72]. 6000/7000 [BMY03, Coh73, CFL84, Cow87, Day83, [Has77, Rob79, Yuv77a]. 653 [DKM11]. 68 DPS03, Hun81, LN71, PSR83, Poo71b, Ree71, [DV85, FM78, IR80, Inc81, PH86, ST79, Sil81, SY79, SY86, SL87, Sti79, Tag88, TB72, She75, Woo72, Woo84, Wyv77, Bar74e, Wil73, WMG94, WP96, BSC+05, CKL+02, Bra80]. 68-R [Bar75a, FM78]. 68K [Poh81]. Gay80, HNW+01, HLW08, KKN04, MLC02, NH03, WJC+14, KT01b, SROAdM+08]. 7 [HCD84, WK06a, Bar76b]. 7.00 Access-control [Sil81]. Accessed [Bar82b, Lar75a, Ree75]. 7.30 [Flo74]. 7.35 [SW87, HJC00]. Accesses [Har92, PF97]. [Woo74]. 7.50 [Bis79b]. 7.60 [Ald72]. 7.80 Accessing [Ker80]. accident [JH03]. [Bar76c]. 7.85 [Bar77b]. 7.95 [Ano88b]. Accommodating [Not90]. Accounting 7000 [Rob79]. 70's [Spo71]. 750 [HJ88b]. [CW82b, Sre76]. accounts [BLNU15]. 77 [HWS+88, Lar81, Edm86, RB82]. Acculock [XXZ13]. accumulator [CRT80]. accuracy [PKvdWB17]. Accurate 8 [Ell72, Har71b, KL21]. 8.00 [Oli83, Bin06, Spi04, WC08, XXZ13, YMH16]. [Ear77, Hop73]. 8.20 [Bux78]. 8.25 ACET [LPF+11]. Achieve [Nee77c]. [Edm86, How76]. 8.50 [Dav74, Han77a]. achieved [BLC19]. Achieving 8.75 [Flo79]. 8.80 [Bar77d]. 8.95 [Cou85a]. [CW97, WW09, WC08]. ACID [FZ98]. Ackermann [Wic77]. Acknowledgements 9 [Gru83]. 9.45 [Bar80e, Val76a, Wal82]. [Ano17m]. Acos [SH17]. Acquiring 9.70 [Edw77]. 9.80/$16.60 [Lav77]. 9.95 [Ard87, Ano80b, Jos79, Jos80]. Acquisition [Ano88a, Cou85b]. 90 [SM90]. [Har80a, SDF+21, WPL+21]. acronyms [CK15]. across = [Edw77]. [DGRB15, DW91, ZWML14]. action [ST12]. Actions [M¨os88, Set84, TE90, FZS+17, AAOP [JZ10]. ABACUS [JT00]. OMM15, ZRX+99]. activation [SSO13]. Abbreviations [New86, MT84a]. ABCD activator [SSO13]. Active [AN88, Car98, [KAS+16]. Abecedarian [Bar76d]. Ability CC97, Cho96, MK96, RMC97, TS02]. [YH97]. Ablego [ZA07]. Abmash ActiveX [Lev01]. activities [SJK+21]. [OMM15]. Abnormal [BMZ92, XLZ+20]. Activity [FM78, HLR+03, CmJHL18, Abowd [Wri98]. Abstract HLR20, SH17, aSZP+16]. ACTUS [AD87, BCHR81, CFL84, Die97, ELRV93, [PCM83]. acyclic [LSZ16]. Ada Fle82, FH82a, Gri80, GH84, HOS85, Ian90, [BK86, FIL86, GWA91, WL81a, AB88, Jal87, Lar90, NPW72, Pow87, AG06, CFC15, Ard87, Bar80a, BAP87, Bri84, Bru84, BK87, MGG+09]. Abstraction DHGR92, FFW96, Gau95, Geh85, Hol83, [BR95, Fel81, GR79, LHC97, Sal79a, SL78, Ibs84, IM93, Jac85, KO86, LMSP92, LvLS84, CLSE05, WZLN08]. Abstractions Lun89, LF90, PCBE96, RA87, REMC81, [Kat83a, KS87, Mor80, AYdS+06, CPD13, SB93, vK87, Wal83c, Wal84b]. Ada-based SM01, VGF21]. Academic [LvLS84]. Adam [LvLS84]. ADAMS [Bar75f, Bux78, Dav78, Dea86, Hop74, Inc86, [DFOT10]. Adaptability Jon74, Rob72, Sha72, SFB13, Whi87, Wic72a, [JZ10, Han77b, KKLL99]. Adaptable 4 [Ell79a, VAP+17, WN88, BHR15, BS89]. aerial [SGA21]. Aesthetic [Blo93]. Adaptation [AE06b, AE06a, PA91, CLC09, Aesthetics [CP96]. Aesthetics-based CRGIP15, GBE+09, GDH13, HK06b, [CP96]. affecting [MCLL21]. affective IHS+14, KY05, NS01b, PDBG10]. [ZZC+17]. After [Nee75]. AG [Car97]. Adapters [HL94]. Adapting [LLS06, Again [Hut78, Sal79b]. against MNW14, SSCdA+03, HIR06, MA20a]. [AGG06, Mid86]. Agent adaption [Wal81a]. Adaptive [BDMP17, BHR+02, BPR01, BMM19, [AS97b, HMS+95, LH82, LDI98, LXY+11, CCP06, CNAM+10, DO99, DS09, GHM+06, NZH20, SXWL17, TP03, VBH+98, VC90, GCK+02, HL02a, KT01a, LM02, MAJ15, AF99, AE06b, AE06a, dODP21, BDA20, Pei02, TKT+07]. agent-based BFNP08, CPCL10, FFF+13, GLT08, [BMM19, MAJ15, TKT+07]. HKC+12, HML04, LKC12, Mos06, NB19, Agent-oriented [BDMP17]. Agents PRA+06, PCML09, PDPM+16, SIC+20, [GdLC04, Lib97b, BLE+08, CCP06, FZ12, ST12, SLRS06, SJP+09, SM15, Sta07, HBM06, KY05, MKC11, PL08]. aggregate VGF21, YFC06, ZXT+17, ZCN06]. [Mid79]. Aggregating [dSRdSS+21]. adaptivity [MK03]. ADARC [JZLP20]. aggregation Ada(R) [GC84]. Added [Bro80]. [FO10, FKL+13, FSC08, WMSY12]. Agile Addendum [Sau88]. Adding [DPAG11, GEI+11, GH11, Han11, [CD94, JGT95, Ron99, Ste92, Str83a, ZM95, dSdMSNO+11, BBS11, FSR11, ABL08, KGL06, MSB18]. Addison MdCGdC+17, GH09]. Aglets [OT02]. [Bar76e, Bis79b, Cam85, Cou85a, Ear77, agreement [ASP+19, BS19, DTB12]. Gru83, Jac84, Llo82, Wal83b, Wil84b]. agreement-aware [BS19]. Ahab [VSID17]. Addison-Wesley ahead [DSD+19, HKM+09, PES+20]. [Bar76e, Bis79b, Cam85, Cou85a, Ear77, ahead-of-time [HKM+09]. Aho [NK07]. Gru83, Llo82, Wal83b, Wil84b]. Address Aid [BCL+94, CT90, CP76, Gri80, Gri82, [HEV+98, Wil79, CRT80, GNSP12, LGZ+08]. RR85, Bud85]. AIDA [CC87]. aided Addresses [Bel74, HP87]. Addressing [CGK89, FR78, KCS+20, LPT82, SM15]. [FS11, Har92, vK87, DFRR15, FS13, JK14]. Aids [CL83, Fox78, Sco77b, Val76a]. AIMS Addyman [Bis79a]. ADIC [BRMO97]. [YSM95]. Air [DP85, MPN+95]. aircraft adjusting [BG93, WZH01]. [CGH+15, MdCGdC+17]. airplane [LLK04]. Administration airplane-landing [LLK04]. Ajalon [BR97, Bur98, CWD08, Ped86, FSS99]. [PWI+21]. Ajanta [KT01a]. ALADIN Administrator [Gen81]. Administrators [FHS92]. ALCHEMIST [LTV96]. [GST92]. admission [MNH04]. Adoption Alchemy [GZX+21]. Alcock [Ree78]. [KHGSS12]. ADT [CS91a]. Adtpp ALEPH [Gru79]. Alex [Haz72]. Algebra [NSM16]. Advanced [MV86, HBC15]. Algebraic [DB21b, FL75b, BB10, HAM18, MMM18, [IR80, vHLB+88, HM12, NSM16]. ALGOL RMSMML+11, Sav04, For72]. [Bar74e, Woo74, Bra80, Cor82, AvdSGS80, advancements [JC19]. Advances BW71, BCP71, Bro74, Ear76, HSW75, [Jon74, Wil72]. Advantages Hud72, Kaw79, Mid79, PH86, She75, VV84, [DRG11, HKW77]. adversary [McI99]. WJ76, Woo72, AM78, DV85, FM78, Hol77, advertisement [HLH15].
Load more

Recommended publications
  • Ebook - Informations About Operating Systems Version: August 15, 2006 | Download
    eBook - Informations about Operating Systems Version: August 15, 2006 | Download: www.operating-system.org AIX Internet: AIX AmigaOS Internet: AmigaOS AtheOS Internet: AtheOS BeIA Internet: BeIA BeOS Internet: BeOS BSDi Internet: BSDi CP/M Internet: CP/M Darwin Internet: Darwin EPOC Internet: EPOC FreeBSD Internet: FreeBSD HP-UX Internet: HP-UX Hurd Internet: Hurd Inferno Internet: Inferno IRIX Internet: IRIX JavaOS Internet: JavaOS LFS Internet: LFS Linspire Internet: Linspire Linux Internet: Linux MacOS Internet: MacOS Minix Internet: Minix MorphOS Internet: MorphOS MS-DOS Internet: MS-DOS MVS Internet: MVS NetBSD Internet: NetBSD NetWare Internet: NetWare Newdeal Internet: Newdeal NEXTSTEP Internet: NEXTSTEP OpenBSD Internet: OpenBSD OS/2 Internet: OS/2 Further operating systems Internet: Further operating systems PalmOS Internet: PalmOS Plan9 Internet: Plan9 QNX Internet: QNX RiscOS Internet: RiscOS Solaris Internet: Solaris SuSE Linux Internet: SuSE Linux Unicos Internet: Unicos Unix Internet: Unix Unixware Internet: Unixware Windows 2000 Internet: Windows 2000 Windows 3.11 Internet: Windows 3.11 Windows 95 Internet: Windows 95 Windows 98 Internet: Windows 98 Windows CE Internet: Windows CE Windows Family Internet: Windows Family Windows ME Internet: Windows ME Seite 1 von 138 eBook - Informations about Operating Systems Version: August 15, 2006 | Download: www.operating-system.org Windows NT 3.1 Internet: Windows NT 3.1 Windows NT 4.0 Internet: Windows NT 4.0 Windows Server 2003 Internet: Windows Server 2003 Windows Vista Internet: Windows Vista Windows XP Internet: Windows XP Apple - Company Internet: Apple - Company AT&T - Company Internet: AT&T - Company Be Inc. - Company Internet: Be Inc. - Company BSD Family Internet: BSD Family Cray Inc.
    [Show full text]
  • The Blit: a Multiplexed Graphics Terminal
    The Blit: A Multiplexed Graphics Terminal Rob Pike Bell Laboratories Murray Hill, New Jersey 07974 ABSTRACT The Blit is a programmable bitmap graphics terminal designed specifically to run with the Unix operating system. The software in the terminal provides an asynchronous multi-window environment, and thereby exploits the multiprogramming capabilities of the Unix system which have been largely under-utilized because of the restrictions of conventional terminals. This paper discusses the design motivation of the Blit, gives an overview of the user interface, mentions some of the novel uses of multiprogramming made possible by the Blit, and describes the implementation of the multiplexing facilities on the host and in the terminal. Because most of the functionality is provided by the ter- minal, the discussion focuses on the structure of the terminal’s software. Sometime in 1983 The Blit: A Multiplexed Graphics Terminal Rob Pike Bell Laboratories Murray Hill, New Jersey 07974 Introduction The Blit* is a graphics terminal characterized more by the software it runs than the hardware itself. The hardware is simple and inexpensive (Figure 1): 256K bytes of memory dual-ported between an 800×1024×1 bit display and a Motorola MC68000 microprocessor, with 24K of ROM, an RS-232 interface, a mouse and a keyboard. Unlike many graphics terminals, it has no special-purpose graphics hardware; instead, the microprocessor executes all graphical operations in software. The reasons for and conse- quences of this design are discussed elsewhere.5 The microprocessor may be loaded from the host with custom applications software, but the terminal is rarely used this way.
    [Show full text]
  • Research Purpose Operating Systems – a Wide Survey
    GESJ: Computer Science and Telecommunications 2010|No.3(26) ISSN 1512-1232 RESEARCH PURPOSE OPERATING SYSTEMS – A WIDE SURVEY Pinaki Chakraborty School of Computer and Systems Sciences, Jawaharlal Nehru University, New Delhi – 110067, India. E-mail: [email protected] Abstract Operating systems constitute a class of vital software. A plethora of operating systems, of different types and developed by different manufacturers over the years, are available now. This paper concentrates on research purpose operating systems because many of them have high technological significance and they have been vividly documented in the research literature. Thirty-four academic and research purpose operating systems have been briefly reviewed in this paper. It was observed that the microkernel based architecture is being used widely to design research purpose operating systems. It was also noticed that object oriented operating systems are emerging as a promising option. Hence, the paper concludes by suggesting a study of the scope of microkernel based object oriented operating systems. Keywords: Operating system, research purpose operating system, object oriented operating system, microkernel 1. Introduction An operating system is a software that manages all the resources of a computer, both hardware and software, and provides an environment in which a user can execute programs in a convenient and efficient manner [1]. However, the principles and concepts used in the operating systems were not standardized in a day. In fact, operating systems have been evolving through the years [2]. There were no operating systems in the early computers. In those systems, every program required full hardware specification to execute correctly and perform each trivial task, and its own drivers for peripheral devices like card readers and line printers.
    [Show full text]
  • The Symbian OS Architecture Sourcebook
    The Symbian OS Architecture Sourcebook The Symbian OS Architecture Sourcebook Design and Evolution of a Mobile Phone OS By Ben Morris Reviewed by Chris Davies, Warren Day, Martin de Jode, Roy Hayun, Simon Higginson, Mark Jacobs, Andrew Langstaff, David Mery, Matthew O’Donnell, Kal Patel, Dominic Pinkman, Alan Robinson, Matthew Reynolds, Mark Shackman, Jo Stichbury, Jan van Bergen Symbian Press Head of Symbian Press Freddie Gjertsen Managing Editor Satu McNabb Copyright 2007 Symbian Software, Ltd John Wiley & Sons, Ltd The Atrium, Southern Gate, Chichester, West Sussex PO19 8SQ, England Telephone (+44) 1243 779777 Email (for orders and customer service enquiries): [email protected] Visit our Home Page on www.wileyeurope.com or www.wiley.com All Rights Reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except under the terms of the Copyright, Designs and Patents Act 1988 or under the terms of a licence issued by the Copyright Licensing Agency Ltd, 90 Tottenham Court Road, London W1T 4LP, UK, without the permission in writing of the Publisher. Requests to the Publisher should be addressed to the Permissions Department, John Wiley & Sons Ltd, The Atrium, Southern Gate, Chichester, West Sussex PO19 8SQ, England, or emailed to [email protected], or faxed to (+44) 1243 770620. Designations used by companies to distinguish their products are often claimed as trademarks. All brand names and product names used in this book are trade names, service marks, trademarks or registered trademarks of their respective owners.
    [Show full text]
  • Sealing OS Processes to Improve Dependability and Security
    Sealing OS Processes to Improve Dependability and Safety Galen Hunt, Mark Aiken, Manuel Fähndrich, Chris Hawblitzel, Orion Hodson, James Larus, Steven Levi, Bjarne Steensgaard, David Tarditi, and Ted Wobber Microsoft Research One Microsoft Way Redmond, WA 98052 USA [email protected] ABSTRACT General Terms In most modern operating systems, a process is a Design, Reliability, Experimentation. hardware-protected abstraction for isolating code and data. This protection, however, is selective. Many common Keywords mechanisms—dynamic code loading, run-time code Open process architecture, sealed process architecture, sealed generation, shared memory, and intrusive system APIs— kernel, software isolated process (SIP). make the barrier between processes very permeable. This paper argues that this traditional open process architecture 1. INTRODUCTION exacerbates the dependability and security weaknesses of Processes debuted, circa 1965, as a recognized operating modern systems. system abstraction in Multics [48]. Multics pioneered As a remedy, this paper proposes a sealed process many attributes of modern processes: OS-supported architecture, which prohibits dynamic code loading, self- dynamic code loading, run-time code generation, cross- modifying code, shared memory, and limits the scope of process shared memory, and an intrusive kernel API that the process API. This paper describes the implementation permitted one process to modify directly the state of of the sealed process architecture in the Singularity another process. operating system,
    [Show full text]
  • Study on Operating Systems for Small Devices for Mobile Payments Application 17 Th July, 2009
    Study on Operating Systems for Small Devices for Mobile Payments Application 17 th July, 2009 Project Report On Study on Operating Systems for Small Devices for Mobile Payments Application Submitted by: V V Aishwarya B.E IV/IV (01-07-862) Department of Computer Science and Engineering (CSE) University College of Engineering (Autonomous) Osmania University , Hyderabad- 500004 To Summer Internship Project under the Guidance of Dr. V N Sastry Associate Professor Institute for Development and Research in Banking Technology (IDRBT) (Established by Reserve Bank of India) Road No. 1, Castle Hills, Masab Tank, Hyderabad – 500 057. July 2009 CSE,UCE,OU 1 IDRBT Study on Operating Systems for Small Devices for Mobile Payments Application 17 th July, 2009 CERTIFICATE This is to certify that this project on “ Study on Operating Systems for Small Devices for Mobile Payments Application ” submitted by Ms. V V Aishwarya , 01-07-862 of B.E. IV/IV, CSE, University College of Engineering, Osmania University, is a record of Bonafide work done by her under my guidance during the Summer Internship Programme from 21 st May, 2009 to 17 th July, 2009. Ms. V V Aishwarya has completed the work assigned to her within the limited period of learning and execution. She has successfully completed the project to my satisfaction and it has been observed that the goals set upon at the outset of this endeavor have been worked upon to the best of the student’s abilities and resources. During this period I have observed her to be very sincere, hardworking and coping up with new challenges.
    [Show full text]
  • CS 162 Operating Systems and Systems Programming Lecture 3
    CS 162 Operating Systems and Systems Programming Answer: Decompose hard problem into simpler ones. Instead of dealing with Professor: Anthony Joseph everything going on at once, separate into logical abstractions that we can deal Spring 2004 with one at a time. Lecture 3: 3.2 Processes Concurrency: Processes, Threads, and Address Spaces The notion of a “process” is a central concept for Operating Systems. 3.0 Main point: What are processes? Process: Operating system abstraction to represent what is needed to run a single How are they related to threads and address spaces? program (this is the traditional UNIX definition) Formally, a process is a sequential stream of execution in its own address space. 3.1 Concurrency 3.1.1 Definitions: 3.2.1 Two parts to a (traditional Unix) process: Uniprogramming: one process at a time (e.g., MS/DOS, early Macintosh) 1. Sequential program execution: the code in the process is executed as a single, sequential stream of execution (no concurrency inside a process). This Easier for operating system builder: get rid of problem of concurrency by defining is known as a thread of control. it away. For personal computers, idea was: one user does only one thing at a 2. State Information: everything specific to a particular execution of a program: time. Encapsulates protection: address space • CPU registers Harder for user: can’t work while waiting for printer • Main memory (contents of address space) • I/O state (in UNIX this is represented by file descriptors) Multiprogramming: more than one process at a time (UNIX, OS/2, Windows NT).
    [Show full text]
  • The Niagara Framework
    The Niagara Framework Control System Interoperability with Seamless Intranet/Internet Enterprise Connectivity © Copyright 1998 Tridium, Inc., All Rights Reserved Tridium, Inc. 3951 Westerre Parkway Suite 350 Richmond, Virginia 23233 (804) 747-4771 http://www.tridium.com Ernie Allen, Technical Services Manager John Bishop, Regional Manager Copyright Notice: The software described herein is furnished under a license agreement and may be used only in accordance with the terms of the agreement. © Copyright 1998 Tridium, Inc. All rights reserved. This document may not, in whole or in part, be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine-readable form without prior written consent from Tridium, Inc., 3951 Westerre Parkway, Suite 350, Richmond, Virginia 23233. The confidential information contained in this document is provided solely for use by Tridium employees, licensees, and system owners; and is not to be released to, or reproduced for, anyone else; neither is it to be used for reproduction of this Control System or any of its components. All rights to revise designs described herein are reserved. While every effort has been made to assure the accuracy of this document, Tridium shall not be held responsible for damages, including consequential damages, arising from the application of the information given herein. The information in this document is subject to change without notice. The release described in this document may be protected by one of more U.S. patents, foreign patents, or pending applications. Trademark Notices: Microsoft and Windows are registered trademarks, and Windows 95, Windows NT, and Internet Explorer are trademarks of Microsoft Corporation. Java and other Java-based names are trademarks of Sun Microsystems Inc.
    [Show full text]
  • Acme: a User Interface for Programmers Rob Pike AT&T Bell Laboratories Murray Hill, New Jersey 07974
    Acme: A User Interface for Programmers Rob Pike AT&T Bell Laboratories Murray Hill, New Jersey 07974 ABSTRACT A hybrid of window system, shell, and editor, Acme gives text-oriented applications a clean, expressive, and consistent style of interaction. Traditional window systems support inter- active client programs and offer libraries of pre-defined operations such as pop-up menus and buttons to promote a consistent user interface among the clients. Acme instead provides its clients with a fixed user interface and simple conventions to encourage its uniform use. Clients access the facilities of Acme through a file system interface; Acme is in part a file server that exports device-like files that may be manipulated to access and control the contents of its win- dows. Written in a concurrent programming language, Acme is structured as a set of communi- cating processes that neatly subdivide the various aspects of its tasks: display management, input, file server, and so on. Acme attaches distinct functions to the three mouse buttons: the left selects text; the mid- dle executes textual commands; and the right combines context search and file opening functions to integrate the various applications and files in the system. Acme works well enough to have developed a community that uses it exclusively. Although Acme discourages the traditional style of interaction based on typescript windows— teletypes—its users find Acme’s other services render typescripts obsolete. History and motivation The usual typescript style of interaction with Unix and its relatives is an old one. The typescript—an inter- mingling of textual commands and their output—originates with the scrolls of paper on teletypes.
    [Show full text]
  • Micropython Documentation Release 1.10 Damien P. George, Paul
    MicroPython Documentation Release 1.10 Damien P. George, Paul Sokolovsky, and contributors Jan 25, 2019 CONTENTS 1 MicroPython libraries 1 1.1 Python standard libraries and micro-libraries..............................2 1.1.1 Builtin functions and exceptions................................2 1.1.2 array – arrays of numeric data................................5 1.1.3 cmath – mathematical functions for complex numbers....................5 1.1.4 gc – control the garbage collector...............................6 1.1.5 math – mathematical functions................................7 1.1.6 sys – system specific functions................................9 1.1.7 ubinascii – binary/ASCII conversions........................... 11 1.1.8 ucollections – collection and container types...................... 11 1.1.9 uerrno – system error codes................................. 12 1.1.10 uhashlib – hashing algorithms............................... 13 1.1.11 uheapq – heap queue algorithm................................ 14 1.1.12 uio – input/output streams................................... 14 1.1.13 ujson – JSON encoding and decoding............................ 16 1.1.14 uos – basic “operating system” services............................ 16 1.1.15 ure – simple regular expressions............................... 20 1.1.16 uselect – wait for events on a set of streams........................ 22 1.1.17 usocket – socket module................................... 23 1.1.18 ussl – SSL/TLS module................................... 28 1.1.19 ustruct – pack and unpack
    [Show full text]
  • Sealing OS Processes to Improve Dependability and Security
    MSR-TR-2006-51 This is a draft paper that is under submission. Please contact Galen Hunt for citation information. Sealing OS Processes to Improve Dependability and Security Galen Hunt, Mark Aiken, Paul Barham, Manuel Fähndrich, Chris Hawblitzel, Orion Hodson, James Larus, Steven Levi, Nick Murphy, Bjarne Steensgaard, David Tarditi, Ted Wobber, Brian Zill Microsoft Research Abstract On most modern operating systems, a process is a hardware-protected abstraction for executing potentially mutable code and data. Common features of processes include: dynamic code loading, dynamic code generation, access to cross-process shared memory, and a universal API. This paper argues that many of the dependability and security weaknesses of modern systems are exacerbated by this open process architecture. Moreover, this architecture impairs the ability of tools to analyze code statically, to improve its performance or dependability. By contrast, a sealed process architecture prohibits dynamic code loading, prohibits self-modifying code, prohibits shared memory, and replaces a universal API with a process-limited API. This paper describes an implementation of a sealed process architecture in the Singularity operating system, discusses its merits, and evaluates its impact. Among the benefits are: improved static program analysis, strong security guarantees, elimination of OS redundancies found in language runtimes such as the JVM and CLR, and better software engineering. 1. Introduction 1.1. Disadvantages of Open Processes The process, as a recognized operating system Although common, open processes are not “free.” abstraction, debuted in Multics [52] in the 1960s. This architecture has negative consequences for Multics processes included support for dynamic code dependability, correctness, security, and performance.
    [Show full text]
  • Lecture 24: Javaos Key Concepts Java Application on a Host OS Java
    Lecture 24: JavaOS Key concepts ■ Java - an object oriented language (a safer/simpler) modification of C++; ■ JavaOS adheres to the following design goals: ■ Java program is usually interpreted - translated and executed at the ◆ ease the development same time; ◆ portability of the OS ■ Java is usually translated into bytecode; a computer capable of ◆ ease of configuration executing bytecode is called Java-machine; there are no physical ■ JavaOS was designed to run software written in Java Java-machine. The Java machine is usually emulated (like programming language on a variety of platforms from Nachos emulates MIPS architecture) on some other platform. The embedded platforms to network computers program capable of executing Java bytecodes is called Java ◆ embedded system - a computer that facilitates the Virtual Machine (JVM). Thus to make a Java program execute on work of the machine whose purpose is not related to any platform - only JVM has to be designed to execute on this information processing. Example: household platform appliances - microwave, industrial robots ■ Java Development Toolkit (JDK) - a collection of Java classes to ◆ network computer (NC or thin clients) - a computer designed to run only several applications loaded over be used by Java programmers - they declare system functions the network - computers designed to run web- (threading, process creation I/O), windowing functions, graphics, browsers only networking, etc. 1 ■ JavaOS implements JVM and JDK in a portable way 2 Java Java application applicat on a host ion
    [Show full text]