Generalised Interfacing with Microprocessor System Hardware Monitors

Total Page:16

File Type:pdf, Size:1020Kb

Generalised Interfacing with Microprocessor System Hardware Monitors Proceedings of the 2007 IEEE International Conference on TuesE04 Networking, Sensing and Control, London, UK, 15-17 April 2007 Generalised Interfacing with Microprocessor System Hardware Monitors Constantine A. Murenin Department of Computer Science, East Carolina University, Greenville, NC, USA Faculty of Computing Sciences and Engineering, De Montfort University, Leicester, UK comes very handy, such that administrators can be sure that Abstract their systems are running in accordance with manufacturers’ specifications and guidelines. In this paper, we will discuss the possibilities, Vast majority of motherboards in use today already functionalities and limitations of Microprocessor System integrate chips that allow temperature, voltage and fan speed Hardware Monitors. We will provide a comparison survey monitoring, and many newer motherboards have the of their main functions, depict some weaknesses and give an circuitry for supplying fans with user-specified voltage so overview of what possibilities they provide for the end-user. that the user can control fan speed entirely from software. We will also discuss OpenBSD’s sysctl Hardware However, hardware manufacturers do not always provide Sensors framework, and describe our recent contributions to any end-user utilities to do the aforementioned monitoring the addressing scheme and underpinnings of the framework. and controlling, and when it comes to open-source software, the community is expected to come up with a software 1. Background solution on their own. This works well as long as chip manufacturers release appropriate register documentation for Power consumption of personal computers grows every their hardware. In the presence of such documentation, year along with their computational capabilities. Recently qualified software developers can write drivers for the produced microprocessors consume at times hundreds watts operating system of their choice, and these drivers are of power, and thus require massive cooling resources. Most usually shortly integrated into the official distribution of the often than not, fans are used as a low-cost solution that operating system for which they were written. provides adequate cooling in low- and medium-cost personal computers, whilst water-cooling is used in high-end systems. 2. Hardware review However, fans have several problems associated with them, such as noise when run at full speed and, once again, they Hardware monitors usually come either in a distinct chip themselves consume more electricity. package or a as a part of a Super I/O solution. Sensor Processor manufacturers have come to realise that power readings and fan-controlling capabilities may be accessed consumption of modern processors is a major drawback through different busses, mostly I2C or SMBus, ISA or LPC, from creating high-end personal systems with acceptable or PCI. power-drawn, so several power-saving technologies were I2C and SMBus are two-wire busses, which are deployed, such as deactivating some microprocessor units or essentially compatible with each other. I2C is an acronym for modules whilst the processor is in the idle loop. The Inter Integrated Circuit, a bus developed by Philips adoption of these features means that fans may be turned off Semiconductor with version 1.0 published in 1992 [1], while the overall system activity is low, and turned to full whilst SMBus is an acronym for System Management Bus, a speed when the system performs some processor-intensive bus defined by Intel in 1995. task. LPC stands for Low Pin Count Interface Specification, It is in the interest of the user to be able to control the which is a bus authored by Intel that is hardware and speed at which fans are running in order to utilise the software compatible with the existing ISA devices and power-saving features of the processor and minimise the applications. [2] overall noise of the system. Practically, this may be proven Popular hardware monitoring chips often feature both I2C extremely useful in situations where one is running an and ISA bus access, for example National Semiconductor OpenBSD-based firewall or fileserver system in the home LM78 [3] or Winbond W83627HF [4]. In such case, setting, where the overall processor activity of the server is accessing sensors over ISA bus is preferred over I2C, with going to be very minimal, whereas the noise of the system is ISA being the faster of the two. From the practical of a major concern due to the desired 24hr operation of the standpoint, however, unless special care is taken, two server within the living room area. Desktop usage of instances of the same device may be attached to the system hardware monitoring and controlling software is also of at once — one on I2C, the other one on ISA. Whilst this value, since the amount of processor idling time prevails in usually does not create any resource conflicts, most desktop applications and minimised noise is of implementations might detach the instance of the driver from particular value. In the server arena, the monitoring part the I2C bus in favour of ISA bus access to avoid any user confusion of two distinct devices being attached with Public domain. identical sensor readings. (In fact, this is what OpenBSD’s 1-4244-1076-2/07/$25.00 ©2007 IEEE 901 lm(4) driver does — when the hardware monitoring chip is monitoring chips inside their motherboard, and utilise their detected on the ISA bus, it is automatically attached on ISA voltage sensor inputs in such a way as to provide the and detached from the I2C bus.) maximum flexibility in monitoring, say, dual power-supplies It is not less common to find hardware monitors that only that provide uninterrupted power to the motherboard. have I2C interface — this is usually the case with simple However, when one thinks more about this situation, one chips that only have one or two temperature sensors. On the realises that most power supplies in the desktop market other hand, Super I/O chipsets usually offer ISA/LPC today are standard ATX power supplies, which have the very interface as they already use ISA/LPC for the purpose of same connectors from motherboard to motherboard. They connecting serial, parallel, infrared and PS/2 ports. also come in standard voltage configurations, for example, Hardware monitors that are accessible through PCI they all have a +3.3V lead, +5V regular lead, +5V lead for interface are usually enclosed in South Bridges, such as VIA ‘stand-by’ use, several +12V leads etc. [6] I.e. the hardware VT82C686A “Super South” South Bridge. At this time, only monitoring chip manufacturer should already have a pretty VIA is known to have produced this kind of “Super South” good idea of where their Super I/O chips will be used in the South Bridge with system-wide hardware monitoring vast majority of cases. capabilities. Nevertheless, because chip manufacturers still provide only recommendations of which voltages should be 2.1. Hardware documentation connected to which voltage sensor inputs, we have a problem to tackle. The problem cannot be seen until you In order to write an effective driver for a hardware realise how voltage sensors in the monitoring chip work. monitoring chip, or any chip for that matter, the Voltage sensors work as follows: each sensor has a limit manufacturer of the chip has to release appropriate of the maximum voltage that it can detect and the maximum documentation that would summarise main functions of the voltage it can withstand. Most older chips have the chip and provide some insightful information on how the maximum voltage detection level at around 4.0 volts, whilst chip can be talked-to to perform desired operations. many newer chips have it at around 2.0 volts. This maximum Unfortunately, in recent years in the computer industry it voltage detection level will only decrease over time, as the became very difficult to acquire appropriate documentation semiconductor industry manufactures integrated circuits that is required for programming the chips. According to using a smaller and smaller chip manufacturing process year Theo de Raadt, the founder and main software-architect of after year, which in turn makes chips consume less the OpenBSD project, it is the large American companies electricity, and moreover makes it impossible to transfer which usually resist from giving away their documentation high voltage over such small electrical parts inside the chip. that is required for programming the chips. [5] Datasheet Therefore, before the voltage can be connected to the unavailability is a major obstacle for open-source software, monitoring chip, it must be downscaled to no more than the because it means that driver developers have to reverse- specified maximum detection level. This is done with the engineer the devices and their interfaces in order to create help of resistors. working drivers. After the voltage is transformed to the appropriate scale Fortunately, most popular hardware monitoring chip and is connected to the sensor, the sensor usually has 8-bit, manufacturers do provide the datasheets for programming sometimes 10-bit, scale under which it can report the voltage their hardware. However, in the next subsection, we will it senses. discuss some problems that driver developers may have to In other words, the detected value from the sensor is face when interpreting provided documentation. usually stored in one byte, and assumptions are made on 2.2. Datasheet shortcomings which resistors were used in order to bring the voltage to the desired level. The resistor factors can be thought of as the In this section, we will provide a brief survey of common conversion table, and because the chip manufacturer, problems that may be encountered by driver developers in essentially, does not require the motherboard manufacturer writing drivers for most popular hardware monitoring chips. to connect specific leads from the power supply to specific Some problems mentioned in this section can equally apply sensor inputs of the monitoring chip using specific to the end user as well, for example, what expectations resistors — there is no guarantee that the value we think is should the user have for hardware monitors in general? +12V is indeed connected to the +12V line of the power supply.
Recommended publications
  • Advanced Openbsd Hardening
    Advanced Hardening WrongunWrongun && DCDC JuneJune 20052005 ssh://root:[email protected] Lab Challenge JoinJoin thethe wifiwifi netnet andand sshssh intointo thethe boxbox usingusing thethe accountaccount specifiedspecified inin thethe footerfooter TryTry toto pwnpwn thethe boxbox byby addingadding anan accountaccount forfor yourselfyourself oror backdooringbackdooring sshdsshd ssh://root:[email protected] “Only one remote hole in the default install, in more than 8 years! “ ssh://root:[email protected] So OpenBSD is uber secure, right? Actually,Actually, nono …… TheThe defaultdefault installinstall hashas nothingnothing enabledenabled (except(except ssh)ssh) ““NoNo wonderwonder itit ’’ss secure,secure, itit ’’ss poweredpowered off!off! ”” SourceSource --onlyonly patchingpatching strategystrategy makesmakes itit difficultdifficult toto rollroll outout fixesfixes toto platformsplatforms w/ow/o compilerscompilers (i.e.(i.e. disklessdiskless firewalls,firewalls, etc.)etc.) ssh://root:[email protected] Brief History of OpenBSD Vulnerabilities 30 March 05: Bugs in the cp(4) stack can lead to memory exhaustion or processing of TCP segments with invalid SACK optio ns and cause a system crash. 14 Dec 04: On systems running sakmpd(8) it is possible for a local user to cause kernel memory corruption and system panic by setti ng psec(4) credentials on a socket 20 Sept 04: radius authentication, as implemented by ogin_radius(8) , was not checking the shared secret used for replies sent by the radius server. This could allow an attacker to spoof
    [Show full text]
  • OPENBSD HARDWARE SENSORS FRAMEWORK a Unified and Ready-To-Use System for Hassle-Ee Hardware Monitoring
    OPENBSD HARDWARE SENSORS FRAMEWORK A unified and ready-to-use system for hassle-ee hardware monitoring. Constantine A. Murenin and Raouf Boutaba University of Waterloo AsiaBSDCon 2009 — 12–15 March 2009 — Tokyo, Japan Abstract In this paper, we will discuss the origin, history, design guidelines, API and the device drivers of the hardware sensors framework available in OpenBSD. The framework spans multiple utilities in the base system and the ports tree, is utilised by over 70 drivers, and is considered to be a distinctive and ready-to-use feature that sets OpenBSD apart from many other operating systems, and in its root is inseparable from the OpenBSD experience. 1. Introduction Another trend that has been particularly common in the recent years is the availability of defined inter- We will start by investigating into the matter of what faces for software-based temperature readout from hardware monitoring sensors represent, how common individual components of personal computers, such as is it for them to appear in the general-purpose com- the CPU, or the add-on cards, such as those imple- puter hardware that has been available on the market menting the 802.11 wireless functionality or 10 Giga- in the last decade or so, and what benefits can we gain bit Ethernet. Popular examples include recent Intel by having a unified, simple and straightforward inter- Xeon and Core series of processors (as well as budget face for getting the data out of these sensors. models that are marketed under different brands) Although it may come as a surprise to some users, the [admtemp.4] [cpu.4]; all AMD64 processors from majority of personal computers that have been avail- AMD (Families 0Fh, 10h, 11h) [kate.4] [km.4]; Intel able on the market in the last decade have an inte- WiFi Link 4965/5100/5300 wireless network devices grated hardware monitoring circuitry whose main [iwn.4].
    [Show full text]
  • Cryptanalysis of the Random Number Generator of the Windows Operating System
    Cryptanalysis of the Random Number Generator of the Windows Operating System Leo Dorrendorf School of Engineering and Computer Science The Hebrew University of Jerusalem 91904 Jerusalem, Israel [email protected] Zvi Gutterman Benny Pinkas¤ School of Engineering and Computer Science Department of Computer Science The Hebrew University of Jerusalem University of Haifa 91904 Jerusalem, Israel 31905 Haifa, Israel [email protected] [email protected] November 4, 2007 Abstract The pseudo-random number generator (PRNG) used by the Windows operating system is the most commonly used PRNG. The pseudo-randomness of the output of this generator is crucial for the security of almost any application running in Windows. Nevertheless, its exact algorithm was never published. We examined the binary code of a distribution of Windows 2000, which is still the second most popular operating system after Windows XP. (This investigation was done without any help from Microsoft.) We reconstructed, for the ¯rst time, the algorithm used by the pseudo- random number generator (namely, the function CryptGenRandom). We analyzed the security of the algorithm and found a non-trivial attack: given the internal state of the generator, the previous state can be computed in O(223) work (this is an attack on the forward-security of the generator, an O(1) attack on backward security is trivial). The attack on forward-security demonstrates that the design of the generator is flawed, since it is well known how to prevent such attacks. We also analyzed the way in which the generator is run by the operating system, and found that it ampli¯es the e®ect of the attacks: The generator is run in user mode rather than in kernel mode, and therefore it is easy to access its state even without administrator privileges.
    [Show full text]
  • History of the Openbsd Hardware Sensors Framework
    History of the OpenBSD Hardware Sensors Framework Constantine A. Murenin University of Waterloo AsiaBSDCon 2009 — 12/15 March 2009 — Tokyo, Japan Outline • Introduction • Framework API and utilities • Drivers • I²C Bus Scan • Conclusion What is a sensor? • Any device with a sensor-like data: • temperature • voltage • fan speed • … • logical drive status • time offset Are these common at all? • many Super I/O chips have integrated hardware monitors • Intel Core and AMD K8 / K10 have integrated thermal sensors • IPMI in servers / ACPI in laptops • SCSI enclosures • 10GbE and 802.11 Why sensors framework? • Monitoring environmental values can predict, detect, troubleshoot system failure. (Voltage, temperature, fan, logical drive status.) • Unified interface, no configuration required, works out-of-the-box. • Sensors are fun! Uber cool drivers • sdtemp(4) — SO-DIMM temperature sensors • km(4) — AMD Family 10h processors (Phenom, Opteron Barcelona) and Family 11h (Turion X2 Ultra et al) neither of these two are in Linux yet! http://theos.com/deraadt/jc-42.4-pic1.jpg http://theos.com/deraadt/jc-42.4-pic2.jpg Design decisions • Keep it simple, secure and usable • Make it work by default • Overengineering is useless — many devices have incomplete specifications • No buttons™ How voltage sensors work? • Most chips have sensors from 0 to 4 V • Excess voltage removed by resistors • Resistor “recommendations” How voltage sensors read? function maths result original readin’ 0xcb 203 sensor voltage 203 * 16 mV 3.24 V scale for +5 V 3.24 V * 1.68 5.44 V scale for +12 V 3.24 V * 3.80 12.31 V Resistor recommendations • Ignored by some motherboard designers • Not given in documentation for some chips • Results: • voltage “doesn’t scale” • do the best with what you have Framework API /sys/sys/sensors.h • struct sensor / struct sensordev, transport over sysctl(3) • sensor description, e.g.
    [Show full text]
  • BSD Projects IV – BSD Certification • Main Features • Community • Future Directions a (Very) Brief History of BSD
    BSD Overview Jim Brown May 24, 2012 BSD Overview - 5/24/2012 - Jim Brown, ISD BSD Overview I – A Brief History of BSD III – Cool Hot Stuff • ATT UCB Partnership • Batteries Included • ATT(USL) Lawsuit • ZFS , Hammer • BSD Family Tree • pf Firewall, pfSense • BSD License • Capsicum • Virtualization Topics • Jails, Xen, etc. • Desktop PC-BSD II – The Core BSD Projects IV – BSD Certification • Main Features • Community • Future Directions A (Very) Brief History of BSD 1971 – ATT cheaply licenses Unix source code to many organizations, including UCB as educational material 1975 – Ken Thompson takes a sabbatical from ATT, brings the latest Unix source on tape to UCB his alma mater to run on a PDP 11 which UCB provided. (Industry/academic partnerships were much more common back then.) Computer Science students (notably Bill Joy and Chuck Haley) at UCB begin to make numerous improvements to Unix and make them available on tape as the “Berkeley Software Distribution” - BSD A (Very) Brief History of BSD Some notable CSRG • 1980 – Computer Science Research Group members (CSRG) forms at UCB with DARPA funding to make many more improvements to Unix - job control, autoreboot, fast filesystem, gigabit address space, Lisp, IPC, sockets, TCP/IP stack + applications, r* utils, machine independence, rewriting almost all ATT code with UCB/CSRG code, including many ports • 1991 – The Networking Release 2 tape is released on the Internet via anon FTP. A 386 port quickly follows by Bill and Lynne Jolitz. The NetBSD group is formed- the first Open Source community entirely on the Internet • 1992 – A commercial version, BSDI (sold for $995, 1-800-ITS-UNIX) draws the ire of USL/ATT.
    [Show full text]
  • IOMMU-Resistant DMA Attacks
    IOMMU-resistant DMA attacks Gil Kupfer Technion - Computer Science Department - M.Sc. Thesis MSC-2018-21 - 2018 Technion - Computer Science Department - M.Sc. Thesis MSC-2018-21 - 2018 IOMMU-resistant DMA attacks Research Thesis Submitted in partial fulfillment of the requirements for the degree of Master of Science in Computer Science Gil Kupfer Submitted to the Senate of the Technion | Israel Institute of Technology Sivan 5778 Haifa May 2018 Technion - Computer Science Department - M.Sc. Thesis MSC-2018-21 - 2018 Technion - Computer Science Department - M.Sc. Thesis MSC-2018-21 - 2018 This research was carried out under the supervision of Prof. Dan Tsafrir and Dr. Nadav Amit, in the Faculty of Computer Science. Acknowledgements who passed ,ז"ל This work is dedicated to my grandfather, Tuvia Kupfer away during the writing of this work. I would like to thank my wife, Odeya, for helping and supporting when needed. Also, I would like to thank all the friends who have been there. Finally, thanks to my advisors, Prof. Dan Tsafrir and Dr. Nadav Amit, for their help and guidance along the way. The generous financial help of the Technion is gratefully acknowledged. Technion - Computer Science Department - M.Sc. Thesis MSC-2018-21 - 2018 Technion - Computer Science Department - M.Sc. Thesis MSC-2018-21 - 2018 Contents List of Figures Abstract 1 Abbreviations and Notations3 1 Introduction5 2 Background9 2.1 DMA Attacks.................................9 2.1.1 Classic DMA Attacks........................9 2.1.2 IOMMU Protection......................... 10 2.1.3 Circumventing the IOMMU..................... 11 2.2 FireWire.................................... 12 3 Attack Mechanics 15 3.1 Sub-Page Granularity Vulnerability....................
    [Show full text]
  • Mengenal Sistim Operasi *BSD
    Mengenal Sistim Operasi *BSD Ada banyak sekali tulisan-tulisan yang membahas tentang BSD, baik tulisan mengenai sejarah, system administrasi, sampai penggunaan BSD kepada end-user sebagai desktop. Tulisan ini memperkenalkan BSD sebagai alternatif lain dari Linux untuk memenuhi kebutuhan akan UNIX-like operating system di Indonesia. Dalam tulisan ini pula, dibahas mengenai beberapa hal yang membedakan antara Linux dan BSD, namun tidak memutuskan mana yang paling baik, karena untuk menentukan mana operating system yang paling baik digunakan adalah Anda sendiri. Daftar Isi 1. Sejarah 2. Distribusi Varian BSD 3. Model Pengembangan 4. Integrasi System 5. Software-software di BSD 6. System Administrasi 7. File System 8. Lain-lain 9. Kesimpulan Sejarah Hampir semua orang telah mendengar Linux saat ini. Namun apa itu BSD? BSD adalah singkatan dari Berkeley Software Distribution. BSD pertama kali dibangun dan dikembangkan oleh Computer System Research Group (CSRG) di University of California at Berkeley (UCB), BSD pertama kali keluar pada akhir 1977 sebagai paket tambahan dan patch dari AT&T UNIX version 6, yang mana waktu itu beroperasi pada mesin PDP-11 minicomputer. BSD pada akhirnya banyak memberikan kontribusi berharga pada pengembangan UNIX secara umum. Ada banyak fitur yang pertama kali diperkenalkan oleh BSD dan beberapa diadopsi dari AT&T dan vendor-vendor lainnya. BSD dibuat, dikembangkan, dan digunakan secara BEBAS sebagai perlawanan terhadap lisensi UNIX yang dimiliki oleh AT&T dan oleh karena itu BSD mempunyai lisensi tersendiri yang memungkinkan setiap orang bebas melakukan pengembangan, dan menggunakan source code BSD. Pada tahun 1993, 4.4BSD dirilis sebagai sebuah Operating System yang utuh. Untuk sejarah lengkap BSD di CSRG, mulai sejarah dari jaman kuda, motivasi orang-orang yang pertama kali mengerjakannya, sampai perseteruan lisensi dan hak cipta dengan AT&T, saya mereferensikan Anda untuk membaca tulisan yang dibuat oleh Kirk McKusick, “Twenty Years of Berkeley Unix“.
    [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]
  • Open Source Software Notice
    OPEN SOURCE SOFTWARE NOTICE This product incorporates various open source software packages that are distributed under license terms as described further below. 1. Linux Kernel, GNU C library and Toolchain, Busybox, dsnmasq, ethtool, iproute, iptables, sftpd, smcroute, mtdutils, gdb, uboot, cgi-c, jQuery Library, bootloader are licensed under the GNU General Public License, V2.0, which may be viewed at http://www.gnu.org/licenses/gpl-2.0.html. Copies of the source code for the above may be obtained at the following URLs: https://www.kernel.org https://gcc.gnu.org/ http://www.busybox.net/ http://www.thekelleys.org.uk/dnsmasq/doc.html https://www.kernel.org/pub/software/network/ethtool/) http://developer.osdl.org/dev/iproute2 (now- http://www.linuxfoundation.org/) http://www.cschill.de/smcroute/ http://git.infradead.org/mtd-utils.git http://www.gnu.org/software/gdb/ http://www.denx.de/wiki/U-Boot/SourceCode http://sourceforge.net/projects/cgi-c/ http://jquery.com/ Wolfgang Denk, DENX Software Engineering, [email protected]. Copies of the modified source code for BusyBox, cgi-c, boot loader, and Linux may be requested in writing by contacting: ViaSat, Inc., attn: General Counsel / Source Code Request, 6155 El Camino Real, Carlsbad CA 92009 USA. Your request should clearly identify the product and open source software component(s) to which your request relates. Your request must be sent within three (3) years of the date you received the Viasat product that included the binary that is the subject of your request. 2. OpenNTPD This is a summary of the licences for the files that make up Portable OpenNTPD.
    [Show full text]
  • The Design of the Openbsd Cryptographic Framework
    The Design of the OpenBSD Cryptographic Framework Angelos D. Keromytis Jason L. Wright Theo de Raadt Columbia University OpenBSD Project OpenBSD Project [email protected] [email protected] [email protected] Abstract the design of these systems is intended to impede sim- ple, brute-force, computational attacks. This complexity drives the belief that strong security is fundamentally in- Cryptographic transformations are a fundamental build- imical to good performance. ing block in many security applications and protocols. To improve performance, several vendors market hard- This belief has led to the common predilection to avoid ware accelerator cards. However, until now no operating cryptography in favor of performance [22]. However, system provided a mechanism that allowed both uniform the foundation for this belief is often software imple- and efficient use of this new type of resource. mentation [8] of algorithms intended for efficient hard- ware implementation. To address this issue, vendors We present the OpenBSD Cryptographic Framework have been marketing hardware cryptographic acceler- (OCF), a service virtualization layer implemented in- ators that implement several cryptographic algorithms side the kernel, that provides uniform access to accel- used by security protocols and applications. However, erator functionality by hiding card-specific details be- modern operating systems lack the necessary support hind a carefully-designed API. We evaluate the impact to provide efficient access to such functionality to ap- of the OCF in a variety of benchmarks, measuring over- plications and the operating system itself through a all system performance, application throughput and la- uniform API that abstracts away device details. As tency, and aggregate throughput when multiple applica- a result, accelerators are often used directly through tions make use of it.
    [Show full text]
  • Open Source Software: a History David Bretthauer University of Connecticut, [email protected]
    University of Connecticut OpenCommons@UConn Published Works UConn Library 12-26-2001 Open Source Software: A History David Bretthauer University of Connecticut, [email protected] Follow this and additional works at: https://opencommons.uconn.edu/libr_pubs Part of the OS and Networks Commons Recommended Citation Bretthauer, David, "Open Source Software: A History" (2001). Published Works. 7. https://opencommons.uconn.edu/libr_pubs/7 Open Source Software: A History —page 1 Open Source Software: A History by David Bretthauer Network Services Librarian, University of Connecticut Open Source Software: A History —page 2 Abstract: In the 30 years from 1970 -2000, open source software began as an assumption without a name or a clear alternative. It has evolved into a s ophisticated movement which has produced some of the most stable and widely used software packages ever produced. This paper traces the evolution of three operating systems: GNU, BSD, and Linux, as well as the communities which have evolved with these syst ems and some of the commonly -used software packages developed using the open source model. It also discusses some of the major figures in open source software, and defines both “free software” and “open source software.” Open Source Software: A History —page 1 Since 1998, the open source softw are movement has become a revolution in software development. However, the “revolution” in this rapidly changing field can actually trace its roots back at least 30 years. Open source software represents a different model of software distribution that wi th which many are familiar. Typically in the PC era, computer software has been sold only as a finished product, otherwise called a “pre - compiled binary” which is installed on a user’s computer by copying files to appropriate directories or folders.
    [Show full text]
  • Raspberrypiでnetbsdを使ってみる
    セキュリティキャンプ2016 SecCamp2016 ドキュメント file:///usr/local/Github/NetBSD/Guide/_build/singleh... RaspberryPIでNetBSDを使ってみる 特徴 NetBSDをRaspberryPIで利用するために、ディスクイメージを用意しました。 Xが動いて、ご家庭のテレビでmikutterが動きます。 うまく動いたら、動いた記念写真をツイートだ! fossil(http://www.fossil-scm.org/)も入れてあります。家庭内Webサーバとかチケットシステムとかwikiサーバになるんでないかい。 準備するもの RaspberryPI本体 HDMI入力のあるテレビ/ディスプレイ USBキーボード USBマウス 有線ネットワーク 起動ディスクの作成 ディスクイメージのダウンロード earmv6hf # ftp http://cdn.netbsd.org/pub/NetBSD/misc/jun/raspberry-pi/ 2016-07-29-earmv6hf/2016-07-29-netbsd-raspi-earmv6hf.img.gz 2GB以上のSDカードを準備します。 ダウンロードしたディスクイメージを、SDカード上で展開します。 disklabel sd0 ..... 必ずインストールするSDカードか確認してください。 gunzip < 2016-07-29-netbsd-raspi-earmv6hf.img.gz.gz|dd of=/dev/rsd0d bs=1m Cubieboard2,BananaPI用イメージ Cubieboard2,BananaPI用のイメージが、 http://cdn.netbsd.org/pub/NetBSD/misc/jun/allwinner/ 以下にあります。 同じ手 順で起動できます。 ODROID-C1用イメージ ODROID-C1用のイメージが、 http://cdn.netbsd.org/pub/NetBSD/misc/jun/odroid_c1/ 以下にあります。 同じ手順で起動で きます。 RaspberryPIの起動 1. HDMIケーブル/USBキーボード/USBマウス/有線ネットワークをRPIにさします。 2. 電源を入れてRPIを起動します。 3. 少し待つと、HDMIからNetBSDの起動メッセージが表示されます。 4. メモリカードの容量にあわせたサイズまでルートパーティションを自動調整します。(現在、RPI2では自動調整プログラムの起動が失 敗します) 5. 容量調整後に再起動します。再起動した後は、起動プロセスが最後まで進み、ログインできる状態になります。 6. 起動しない場合、まず基板上のLEDを確認してください。 赤いランプのみ点灯している場合 OSを正しく読み込めていません。 少なくともMSDOS領域に各種ファームウェアファイルが見えていることを確認する。 SDカードの接触不良の可能性があるので、SDカードを挿しなおしてみる。 ファームウェアが古いため起動しない 緑のランプも点灯している場合 OSは起動しているのに画面をHDMIに表示できていません。 HDMIケーブルを差した状態で電源ケーブルを抜き差しして、HDMIディスプレイに何か表示するか確認する。 HDMIケーブル自体の接触不良。ケーブルを何度か差し直してください。 電源アダプタ容量には、少なくとも800mA程度の容量を持つアダプタを使ってみてください。スマートフォン用のアダプタなら まず大丈夫です。起動途中で画面が一瞬消えたり、負荷をかけるといきなり再起動したりする場合は、電源やUSBケーブルを気
    [Show full text]