DOCSLIB.ORG

2003-2004 (C) Montavista, Software, Inc. Copyright (C) 2006-2007

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

2003-2004 (c) MontaVista, Software, Inc. Copyright (C) 2006-2007 Sylvain Munaut <[email protected]> Copyright (C) 2006 Freescale - John Rigby (C) COPYRIGHT 2008 PANASONIC COMMUNICATIONS CO., LTD. ※ 本Fileは自動生成Fileであるため 直接編集しないこと" Copyright (C) 1992 David B. Gentzel Low-level SCSI driver for UltraStor 14F, 24F, and 34F by David B. Gentzel, Whitfield Software Services, Carnegie, PA ([email protected]) scatter/gather added by Scott Taylor ([email protected]) 24F and multiple command support by John F. Carr ([email protected]) John's work modified by Caleb Epstein ([email protected]) and Eric Youngdale ([email protected]). Thanks to UltraStor for providing the necessary documentation version of the code. Original copyright preserved below. Steve Whitehouse: Some bug fixes, cleaning up some code to make it compatible with my routing layer. Steve Whitehouse: Merging changes from Eduardo Serrat and Patrick Caulfield. Steve Whitehouse: Further bug fixes, checking module code still works with new routing layer. Steve Whitehouse: Additional set/get_sockopt() calls. Steve Whitehouse: Fixed TIOCINQ ioctl to be same as Eduardo's new code. Steve Whitehouse: recvmsg() changed to try and behave in a POSIX like way. Didn't manage it entirely, but its better. Steve Whitehouse: ditto for sendmsg(). Steve Whitehouse: A selection of bug fixes to various things. Steve Whitehouse: Added TIOCOUTQ ioctl. Steve Whitehouse: Fixes to username2sockaddr & sockaddr2username. Steve Whitehouse: Fixes to connect() error returns. Patrick Caulfield: Fixes to delayed acceptance logic. David S. Miller: New socket locking Steve Whitehouse: Socket list hashing/locking Arnaldo C. Melo: use capable, not suser Steve Whitehouse: Removed unused code. Fix to use sk->allocation when required. Patrick Caulfield: /proc/net/decnet now has object name/number Steve Whitehouse: Fixed local port allocation, hashed sk list Matthew Wilcox: Fixes for dn_ioctl() Steve Whitehouse: New connect/accept logic to allow timeouts and prepare for sendpage etc. Copyright (C) 2004 2005 2006 Michel Xhaard # # Copyright (C) 2005 2006 Laurent Pinchart && Michel Xhaard # # Copyright (C) 2005 2006 Laurent Pinchart && Michel Xhaard # Copyright (C) 2007 Tom Stöveken (minor modifications for uvc_streamer) # # Copyright (C) 2003 2004 Michel Xhaard [email protected] Add Pas106 Stefano Mozzi (C) 2004 Copyright 1994 David C. Davies and United States Government (as represented by the Director, National Security Agency). Copyright 1995 Digital Equipment Corporation. Copyright (C) 1997 Martin von Löwis, Régis Duchesne Copyright (c) 2002-2004 Anton Altaparmakov Copyright (C) 1997 Martin von Löwis, Régis Duchesne Copyright (c) 2002-2005 Anton Altaparmakov Copyright (C) Peter T. Breuer ([email protected]) 2003 additions: Copyright (C) 2003-2004, Paul Clements, SteelEye Technology, Inc. Copyright (C) 1992 Drew Eckhardt Generic hard disk header file by Drew Eckhardt Copyright (C) 1992, 1993 Drew Eckhardt low level scsi driver for ST01/ST02, Future Domain TMC-885, TMC-950 by Drew Eckhardt <[email protected]> if ((num = asc2num(c)) != 0xff) {/* 数字であるならば*/ PointedData[PDColumn++] += num ; sts = 0x14 ;/* 付属情報数字検索中 */ } break ; case 0x16: /* 付属情報終了 */ if (c == '/') //2つ目発見！ { sts = 0x11 ; /* 数字検索中 */ } break ; /* ASCIIキャラクタ */ Copyright (C) 1992 Drew Eckhardt Copyright (C) 1993, 1994, 1995, 1998, 1999 Eric Youngdale generic SCSI package header file by Initial versions: Drew Eckhardt Subsequent revisions: Eric Youngdale Copyright (C) 1992 Lawrence Foard Version 2 and 3 extensions to driver: Copyright (C) 1998 - 2005 Douglas Gilbert Copyright (C) 1995-06 ICP vortex, Achim Leubner See gdth.c for further informations and below for supported controller types (c) 1995 Alan Cox, <[email protected]> Linux Consultancy and Custom Driver Development (c) 1995 Alan Cox, <[email protected]> Linux Consultancy and Custom Driver Development Copyright (C) 1992, 1998 Linus Torvalds, Ingo Molnar SuperH version: Copyright (C) 1999 Niibe Yutaka Copyright (C) 2001 Daniel Barlow <dan AT telent.net> Some of this code is "inspired" by linux-wlan-ng-0.1.10, but nothing has been copied from it. linux-wlan-ng-0.1.10 is originally : Copyright (C) 1999 AbsoluteValue Systems, Inc. This file originally written by: Copyright (C) 2001 Jean Tourrilhes <jt AT hpl.hp.com> And is now maintained by: (C) Copyright David Gibson, IBM Corp. 2002-2003. Copyright (C) 2001 Ivan Martinez <[email protected]> Copyright (C) 2001 Frank Mori Hess <[email protected]> Copyright (c) 2004 Sascha Hauer <[email protected]> 2004 (c) MontaVista Software, Inc. Copyright 2008 Openmoko, Inc. Copyright 2008 Simtec Electronics Ben Dooks <[email protected]> kobject is Copyright (c) 2002-2003 Patrick Mochel configfs Copyright (C) 2005 Oracle. sysfs is Copyright (C) 2001, 2002, 2003 Patrick Mochel configfs Copyright (C) 2005 Oracle. Copyright (C) 2000-2003 David McCullough <[email protected]> Copyright (C) 2002 Greg Ungerer <[email protected]> Copyright (C) 2002 SnapGear, by Paul Dale <[email protected]> Copyright (C) 2000, 2001 Lineo, by David McCullough <[email protected]> Copyright (C) 2001-2004 by Thomas Winischhofer, Vienna, Austria and sis310_accel.h which is Copyright (C) 2001-2004 by Thomas Winischhofer, Vienna, Austria Copyright (C) 2005 2006 Laurent Pinchart && Michel Xhaard # Copyright (C) 2007 Tom Stöveken # # Copyright 2003-2005 Red Hat Inc Copyright 2003-2005 Jeff Garzik Copyright header from piix.c: Copyright (C) 1998-1999 Andrzej Krzysztofowicz, Author and Maintainer Copyright (C) 1998-2000 Andre Hedrick <[email protected]> Copyright (C) 2003 Red Hat Inc Copyright 2003-2005 Red Hat Inc Copyright 2003-2005 Jeff Garzik Copyright header from piix.c: Copyright (C) 1998-1999 Andrzej Krzysztofowicz, Author and Maintainer Copyright (C) 1998-2000 Andre Hedrick <[email protected]> Copyright (C) 2003 Red Hat Inc <[email protected]> Copyright Xavier Ducoin <[email protected]> Copyright 2002 by Thomas Winischhofer, Vienna, Austria and XGI310_accel.c which is Copyright 2002 by Thomas Winischhofer, Vienna, Austria Copyright Xavier Ducoin <[email protected]> Copyright 2002 by Thomas Winischhofer, Vienna, Austria and XGI310_accel.h which is Copyright 2002 by Thomas Winischhofer, Vienna, Austria ultrastor.c (C) 1991 David B. Gentzel Low-level scsi driver for UltraStor 14F by David B. Gentzel, Whitfield Software Services, Carnegie, PA ([email protected]) scatter/gather added by Scott Taylor ([email protected]) 24F support by John F. Carr ([email protected]) John's work modified by Caleb Epstein ([email protected]) and Eric Youngdale ([email protected]). Thanks to UltraStor for providing the necessary documentation Busybox port by Vladimir Oleynik (C) 2001-2005 <[email protected]> */ /* IPv6 support, many bug fixes by Denys Vlasenko (c) 2008 */ * Copyright (c) 1983,1991 The Regents of the University of California. * Copyright (C) 1991 Free Software Foundation, Inc. Copyright (C) 1991, 1992 Free Software Foundation, Inc. Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved. Copyright (C) 1992-1998 Free Software Foundation, Inc. Copyright (c) 1994 by P.J. Plauger. Consult your license regarding permissions and restrictions. V2.21:0576 Copyright (C) 1994 Free Software Foundation, Inc. Copyright (c) 1994-1998 by P.J. Plauger. Consult your license regarding permissions and restrictions. V2.21:0576 Copyright (c) 1995 by P.J. Plauger. Consult your license regarding permissions and restrictions. V2.21:0576 Copyright (C) 1995-1996 Gary Thomas ([email protected]) Copyright (C) 2001 IBM Copyright (C) 1997,1998 Jakub Jelinek ([email protected]) Copyright (C) 1997 David S. Miller ([email protected]) Copyright (c) 1996 by P.J. Plauger. Consult your license regarding permissions and restrictions. V2.21:0576 Copyright (c) 1996-1998 by P.J. Plauger. Consult your license regarding permissions and restrictions. V2.21:0576 Copyright (C) 1999, 2000, 2007, 2008, 2009, 2010 Free Software Foundation, Inc. Copyright (c) 2001 Dave Engebretsen Copyright (C) 2002 Anton Blanchard <[email protected]>, IBM Copyright (C) 2002, David McCullough <[email protected]> */ /* Copyright (C) 1997,1998,2005,2006 Free Software Foundation, Inc. Copyright (c) 2003 Dave Engebretsen Will Schmidt [email protected] SPLPAR updates, Copyright (c) 2003 Will Schmidt IBM Corporation. seq_file updates, Copyright (c) 2004 Will Schmidt IBM Corporation. Nathan Lynch [email protected] Added lparcfg_write, Copyright (C) 2004 Nathan Lynch IBM Corporation. Copyright (C) 2003, 2004 Free Software Foundation, Inc. written by Alexandre Oliva <[email protected]> Copyright (C) 2005 Jeff Dike <[email protected]> */ /* Much of this ripped from drivers/char/hw_random.c, see there for other * copyright. Copyright 2003 Free Software Foundation, Inc. Copyright 2003, 2004 Free Software Foundation, Inc. (c) 2000, 2001 Robert Baruch ([email protected]) (c) 2002 Andries Brouwer ([email protected]) Developed with the assistance of: (c) 2002 Alan Stern <[email protected]> (C) 2002 by gaoyonghong MODULE_AUTHOR ("gaoyonghong"); MODULE_DESCRIPTION ("Rsltek 8139D PCI Fast Ethernet Adapter driver"); MODULE_LICENSE("GPL"); Both are almost identical and seem to be Copyright (C) 1992 Linus Torvalds Adapted from arch/i386 by Gary Thomas Copyright (C) 1995-1996 Gary Thomas ([email protected]) Updated and modified by Cort Dougan <[email protected]> Copyright (C) 1996-2001 Cort Dougan Adapted for Power Macintosh by Paul Mackerras Copyright (C) 1996 Paul Mackerras ([email protected])
Recommended publications
  • Administració De Sistemes GNU Linux Mòdul4 Administració

    Administració De Sistemes GNU Linux Mòdul4 Administració

    Administració local Josep Jorba Esteve PID_00238577 GNUFDL • PID_00238577 Administració local Es garanteix el permís per a copiar, distribuir i modificar aquest document segons els termes de la GNU Free Documentation License, Version 1.3 o qualsevol altra de posterior publicada per la Free Software Foundation, sense seccions invariants ni textos de la oberta anterior o posterior. Podeu consultar els termes de la llicència a http://www.gnu.org/licenses/fdl-1.3.html. GNUFDL • PID_00238577 Administració local Índex Introducció.................................................................................................. 5 1. Eines bàsiques per a l'administrador........................................... 7 1.1. Eines gràfiques i línies de comandes .......................................... 8 1.2. Documents d'estàndards ............................................................. 10 1.3. Documentació del sistema en línia ............................................ 13 1.4. Eines de gestió de paquets .......................................................... 15 1.4.1. Paquets TGZ ................................................................... 16 1.4.2. Fedora/Red Hat: paquets RPM ....................................... 19 1.4.3. Debian: paquets DEB ..................................................... 24 1.4.4. Nous formats d'empaquetat: Snap i Flatpak .................. 28 1.5. Eines genèriques d'administració ................................................ 36 1.6. Altres eines .................................................................................
  • Storage Administration Guide Storage Administration Guide SUSE Linux Enterprise Server 12 SP4

    Storage Administration Guide Storage Administration Guide SUSE Linux Enterprise Server 12 SP4

    SUSE Linux Enterprise Server 12 SP4 Storage Administration Guide Storage Administration Guide SUSE Linux Enterprise Server 12 SP4 Provides information about how to manage storage devices on a SUSE Linux Enterprise Server. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xii 1 Available Documentation xii 2 Giving Feedback xiv 3 Documentation Conventions xiv 4 Product Life Cycle and Support xvi Support Statement for SUSE Linux Enterprise Server xvii • Technology Previews xviii I FILE SYSTEMS AND MOUNTING 1 1 Overview
  • Terra Incognita: Liberdade, Espoliação

    Terra Incognita: Liberdade, Espoliação

    INSTITUTO DE FILOSOFIA E CIÊNCIAS HUMANAS PROGRAMA DE PÓS-GRADUAÇÃO DOUTORADO EM SOCIOLOGIA Terra incognita: liberdade, espoliação. O software livre entre técnicas de apropriação e estratégias de liberdade FRANCISCO ANTUNES CAMINATI CAMPINAS 2013 ii iii iv v vi Dedico esse trabalho aos sonhos de liberdade do Cacique Apow'ẽ e de Richard M. Stallman. vii viii AGRADECIMENTOS: TODO MEU RESPEITO E GRATIDÃO: À FAPESP E AO POVO DO ESTADO DE SP, por apoiarem este trabalho de pesquisa durante 5 anos. AO IFCH E À UNICAMP, A TODOS OS PROFESSORES, FUNCIONÁRIOS E COLEGAS; E A TODA COMUNIDADE UNIVERSITÁRIA E DE BARÃO GERALDO, por proporcionarem um verdadeiro encontro com o mundo. AO PROFESSOR PEDRO PEIXOTO FERREIRA pelo apoio decisivo na reta final e na defesa. AO PROFESSOR LAYMERT GARCIA DOS SANTOS por incentivar meu trabalho desde o início e pelas experiências de pensamento e pelos experimentos de criação que realizamos juntos. AOS PROFESSORES: IMRE SIMON (in memoria) e MAURO W. B. ALMEIDA pela participação no exame de qualificação que marcou a passagem da pesquisa de Mestrado para Doutorado (2007); RICARDO ANTUNES e SÉRGIO AMADEU DA SILVEIRA por participarem do segundo exame (2011) que, anos depois, habilitou a realização da defesa. AOS PROFESSORES: SÉRGIO SILVA, NÁDIA FARAGE, VANESA LEA, RENATO ORTIZ, MARIA FILOMENA GREGORI, MARCELO RIDENTI, OSWALDO SEVÁ, OMAR RIBEIRO e JORGE TÁPIA. AOS COLEGAS E PARCEIROS DO GRUPO DE PESQUISA CTeMe; DA REDE LATA – LABORATÓRIO DE ANTROPOLOGIA, TERRITÓRIO E AMBIENTE; E DO LABORATÓRIO DE CARTOGRAFIA DO CERES. À RÁDIO MUDA E AO COLETIVO SARAVÁ.ORG – por proporcionarem, a partir da superação da especialização técnica e da propriedade sobre o saber, experiências de cruzamento de conhecimentos e de práticas voltados para a transformação social e invenção de novos mundos, que foram a escola política de mais de uma geração.
  • Open Source Software Notice

    Open Source Software Notice

    OPEN SOURCE SOFTWARE NOTICE DCS Touch Display Software V2.00.XXX Schüco International KG Karolinenstraße 1-15 33609 Bielefeld OPEN SOURCE SOFTWARE NOTICE Seite 1 von 32 10000507685_02_EN OPEN SOURCE SOFTWARE NOTICE This document contains information about open source software for this product. The rights granted under open source software licenses are granted by the respective right holders. In the event of conflicts between SCHÜCO’S license conditions and the applicable open source licenses, the open source license conditions take precedence over SCHÜCO’S license conditions with regard to the respective open source software. You are allowed to modify SCHÜCO’S proprietary programs and to conduct reverse engineering for the purpose of debugging such modifications, to the extent such programs are linked to libraries licensed under the GNU Lesser General Public License. You are not allowed to distribute information resulting from such reverse engineering or to distribute the modified proprietary programs. The rightholders of the open source software require to refer to the following disclaimer, which shall apply with regard to those rightholders: Warranty Disclaimer THE OPEN SOURCE SOFTWARE IN THIS PRODUCT IS DISTRIBUTED ON AN "AS IS" BASIS AND IN THE HOPE THAT IT WILL BE USEFUL, BUT WITHOUT ANY WARRANTY OF ANY KIND, WITHOUT EVEN THE IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SEE THE APPLICABLE LICENSES FOR MORE DETAILS. OPEN SOURCE SOFTWARE NOTICE Seite 2 von 32 10000507685_02_EN Copyright Notices and License Texts (please see the source code for all details) Software: iptables Copyright notice: Copyright (C) 1989, 1991 Free Software Foundation, Inc. Copyright Google, Inc.
  • Ivoyeur: Inotify

    Ivoyeur: Inotify

    COLUMNS iVoyeur inotify DAVE JOSEPHSEN Dave Josephsen is the he last time I changed jobs, the magnitude of the change didn’t really author of Building a sink in until the morning of my first day, when I took a different com- Monitoring Infrastructure bination of freeways to work. The difference was accentuated by the with Nagios (Prentice Hall T PTR, 2007) and is Senior fact that the new commute began the same as the old one, but on this morn- Systems Engineer at DBG, Inc., where he ing, at a particular interchange, I would zig where before I zagged. maintains a gaggle of geographically dispersed It was an unexpectedly emotional and profound metaphor for the change. My old place was server farms. He won LISA ‘04’s Best Paper off to the side, and down below, while my future was straight ahead, and literally under award for his co-authored work on spam construction. mitigation, and he donates his spare time to the SourceMage GNU Linux Project. The fact that it was under construction was poetic but not surprising. Most of the roads I [email protected] travel in the Dallas/Fort Worth area are under construction and have been for as long as anyone can remember. And I don’t mean a lane closed here or there. Our roads drift and wan- der like leaves in the water—here today and tomorrow over there. The exits and entrances, neither a part of this road or that, seem unable to anticipate the movements of their brethren, and are constantly forced to react.
  • USB Composite Gadget Using CONFIG-FS on Dra7xx Devices

    USB Composite Gadget Using CONFIG-FS on Dra7xx Devices

    Application Report SPRACB5–September 2017 USB Composite Gadget Using CONFIG-FS on DRA7xx Devices RaviB ABSTRACT This application note explains how to create a USB composite gadget, network control model (NCM) and abstract control model (ACM) from the user space using Linux® CONFIG-FS on the DRA7xx platform. Contents 1 Introduction ................................................................................................................... 2 2 USB Composite Gadget Using CONFIG-FS ............................................................................. 3 3 Creating Composite Gadget From User Space.......................................................................... 4 4 References ................................................................................................................... 8 List of Figures 1 Block Diagram of USB Composite Gadget............................................................................... 3 2 Selection of CONFIGFS Through menuconfig........................................................................... 4 3 Select USB Configuration Through menuconfig......................................................................... 4 4 Composite Gadget Configuration Items as Files and Directories ..................................................... 5 5 VID, PID, and Manufacturer String Configuration ....................................................................... 6 6 Kernel Logs Show Enumeration of USB Composite Gadget by Host ................................................ 6 7 Ping
  • Communicating Between the Kernel and User-Space in Linux Using Netlink Sockets

    Communicating Between the Kernel and User-Space in Linux Using Netlink Sockets

    SOFTWARE—PRACTICE AND EXPERIENCE Softw. Pract. Exper. 2010; 00:1–7 Prepared using speauth.cls [Version: 2002/09/23 v2.2] Communicating between the kernel and user-space in Linux using Netlink sockets Pablo Neira Ayuso∗,∗1, Rafael M. Gasca1 and Laurent Lefevre2 1 QUIVIR Research Group, Departament of Computer Languages and Systems, University of Seville, Spain. 2 RESO/LIP team, INRIA, University of Lyon, France. SUMMARY When developing Linux kernel features, it is a good practise to expose the necessary details to user-space to enable extensibility. This allows the development of new features and sophisticated configurations from user-space. Commonly, software developers have to face the task of looking for a good way to communicate between kernel and user-space in Linux. This tutorial introduces you to Netlink sockets, a flexible and extensible messaging system that provides communication between kernel and user-space. In this tutorial, we provide fundamental guidelines for practitioners who wish to develop Netlink-based interfaces. key words: kernel interfaces, netlink, linux 1. INTRODUCTION Portable open-source operating systems like Linux [1] provide a good environment to develop applications for the real-world since they can be used in very different platforms: from very small embedded devices, like smartphones and PDAs, to standalone computers and large scale clusters. Moreover, the availability of the source code also allows its study and modification, this renders Linux useful for both the industry and the academia. The core of Linux, like many modern operating systems, follows a monolithic † design for performance reasons. The main bricks that compose the operating system are implemented ∗Correspondence to: Pablo Neira Ayuso, ETS Ingenieria Informatica, Department of Computer Languages and Systems.
  • Linux Kernel and Driver Development Training Slides

    Linux Kernel and Driver Development Training Slides

    Linux Kernel and Driver Development Training Linux Kernel and Driver Development Training © Copyright 2004-2021, Bootlin. Creative Commons BY-SA 3.0 license. Latest update: October 9, 2021. Document updates and sources: https://bootlin.com/doc/training/linux-kernel Corrections, suggestions, contributions and translations are welcome! embedded Linux and kernel engineering Send them to [email protected] - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 1/470 Rights to copy © Copyright 2004-2021, Bootlin License: Creative Commons Attribution - Share Alike 3.0 https://creativecommons.org/licenses/by-sa/3.0/legalcode You are free: I to copy, distribute, display, and perform the work I to make derivative works I to make commercial use of the work Under the following conditions: I Attribution. You must give the original author credit. I Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. I For any reuse or distribution, you must make clear to others the license terms of this work. I Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. Document sources: https://github.com/bootlin/training-materials/ - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 2/470 Hyperlinks in the document There are many hyperlinks in the document I Regular hyperlinks: https://kernel.org/ I Kernel documentation links: dev-tools/kasan I Links to kernel source files and directories: drivers/input/ include/linux/fb.h I Links to the declarations, definitions and instances of kernel symbols (functions, types, data, structures): platform_get_irq() GFP_KERNEL struct file_operations - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 3/470 Company at a glance I Engineering company created in 2004, named ”Free Electrons” until Feb.
  • Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO

    Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO

    Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO..........................................................................................................................................1 Martin Hinner < [email protected]>, http://martin.hinner.info............................................................1 1. Introduction..........................................................................................................................................1 2. Volumes...............................................................................................................................................1 3. DOS FAT 12/16/32, VFAT.................................................................................................................2 4. High Performance FileSystem (HPFS)................................................................................................2 5. New Technology FileSystem (NTFS).................................................................................................2 6. Extended filesystems (Ext, Ext2, Ext3)...............................................................................................2 7. Macintosh Hierarchical Filesystem − HFS..........................................................................................3 8. ISO 9660 − CD−ROM filesystem.......................................................................................................3 9. Other filesystems.................................................................................................................................3
  • Monitoring File Events

    Monitoring File Events

    MONITORING FILE EVENTS Some applications need to be able to monitor files or directories in order to deter- mine whether events have occurred for the monitored objects. For example, a graphical file manager needs to be able to determine when files are added or removed from the directory that is currently being displayed, or a daemon may want to monitor its configuration file in order to know if the file has been changed. Starting with kernel 2.6.13, Linux provides the inotify mechanism, which allows an application to monitor file events. This chapter describes the use of inotify. The inotify mechanism replaces an older mechanism, dnotify, which provided a subset of the functionality of inotify. We describe dnotify briefly at the end of this chapter, focusing on why inotify is better. The inotify and dnotify mechanisms are Linux-specific. (A few other systems provide similar mechanisms. For example, the BSDs provide the kqueue API.) A few libraries provide an API that is more abstract and portable than inotify and dnotify. The use of these libraries may be preferable for some applications. Some of these libraries employ inotify or dnotify, on systems where they are available. Two such libraries are FAM (File Alteration Monitor, http:// oss.sgi.com/projects/fam/) and Gamin (http://www.gnome.org/~veillard/gamin/). 19.1 Overview The key steps in the use of the inotify API are as follows: 1. The application uses inotify_init() to create an inotify instance. This system call returns a file descriptor that is used to refer to the inotify instance in later operations.
  • Linux 2.5 Kernel Developers Summit

    Linux 2.5 Kernel Developers Summit

    conference reports This issue’s reports are on the Linux 2.5 Linux 2.5 Kernel Developers Linux development, but I certainly Kernel Developers Summit Summit thought that, in all of this time, someone would have brought this group together OUR THANKS TO THE SUMMARIZER: SAN JOSE, CALIFORNIA before. Rik Farrow, with thanks to La Monte MARCH 30-31, 2001 Yarroll and Chris Mason for sharing their Summarized by Rik Farrow Another difference appeared when the notes. first session started on Friday morning. The purpose of this workshop was to The conference room was set up with cir- provide a forum for discussion of cular tables, each with power strips for changes to be made in the 2.5 release of For additional information on the Linux laptops, and only a few attendees were Linux (a trademark of Linus Torvalds). I not using a laptop. USENIX had pro- 2.5 Kernel Developers Summit, see the assume that many people reading this vided Aeronet wireless setup via the following sites: will be familiar with Linux, and I will hotel’s T1 link, and people were busy <http://lwn.net/2001/features/KernelSummit/> attempt to explain things that might be typing and compiling. Chris Mason of unfamiliar to others. That said, the odd- <http://cgi.zdnet.com/slink?91362:12284618> OSDN noticed that Dave Miller had numbered releases, like 2.3 and now 2.5, <http://www.osdn.com/conferences/kernel/> written a utility to modulate the speed of are development releases where the the CPU fans based upon the tempera- intent is to try out new features or make ture reading from his motherboard.
  • Linux Kernel 8.1 Introduction

    Linux Kernel 8.1 Introduction

    Page 1 of 6 Linux Kernel 8.1 Introduction: The Linux kernel is a Unix-like operating system kernel used by a variety of operating systems based on it, which are usually in the form of Linux distributions. The Linux kernel is a prominent example of free and open source software. The Linux kernel is released under the GNU General Public License version 2 (GPLv2) (plus some firmware images with various non-free licenses), and is developed by contributors worldwide. Day-to-day development discussions take place on the Linux kernel mailing list. The Linux kernel was initially conceived and created in 1991 by Finnish computer science student Linus Torvalds. Linux rapidly accumulated developers and users who adapted code from other free software projects for use with the new operating system. The Linux kernel has received contributions from thousands of programmers. 8.2 History: History In April 1991, Linus Torvalds, a 21-year-old student at the University of Helsinki, Finland started working on some simple ideas for an operating system. He started with a task switcher in Intel 80386 assembly language and a terminal driver. On 25 August 1991, Torvalds posted the following to comp.os.minix, a newsgroup on Usenet: I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones. This has been brewing since April, and is starting to get ready. I'd like any feedback on things people like/dislike in minix, as my OS resembles it somewhat (same physical layout of the file-system (due to practical reasons) among other things).