Hotplugging with Udev, HAL, and D-Bus HOTHOT WIREDWIRED

Total Page:16

File Type:pdf, Size:1020Kb

Hotplugging with Udev, HAL, and D-Bus HOTHOT WIREDWIRED LINUXKNOW-HOW USER SchlagwortHotplugging sollte hier stehen Hotplugging with Udev, HAL, and D-Bus HOTHOT WIREDWIRED Hardware which just works is what every user wants. Current Linux distributions go a long way to fulfilling that dream. In this article, we will be investigating how the hotplug system works. BY OLIVER FROMMEL, MARCEL HILZINGER AND RENÉ REBE s it really that difficult? You only wanted Linux to launch the right manages the actions associated with a Iprogram when you attached your hotplug event. In this case, the agent new digital camera, but the operating manages the task of adding and register- which in turn start other agents. It is system has decided to sit this one out. ing the new device. common for multiple hotplug agents to This scenario is all too common, The steps the agent performs may work together. For example, when you although the situation has started to vary depending on your distribution and connect an external hard disk, first the improve. Linux should handle any kind the type of hardware you are installing. USB agent loads, then the SCSI agent of hardware correctly, but the ability to Since most hotplug-capable hardware loads to mount the individual partitions manage USB and Firewire devices attaches to a USB port, the USB agent is as SCSI devices with the help of the usb- plugged in or unplugged while the com- perhaps a good example. The USB agent storage module. If you attach a Bluetooth puter is running (known as hotplugging first checks if a driver is available for the dongle, the USB agent runs first, fol- [1]) has become increasingly important. new device (for example, isdn) and then lowed by a Bluetooth agent called blue- This article explains what a modern calls modprobe to load the module. If the tooth.agent. Linux system does with the devices you agent finds a script with the same name attach to it, and why not everything as the driver in the /etc/hotplug/usb/ Blacklisting Drivers works as planned. directory, the agent runs that script. The /etc/hotplug/blacklist file has a list The act of loading modules typically of modules that no agent is allowed to Agents at Work triggers a few more hotplug events, load. The list includes the modules that When you plug in a device that supports hotplugging, the kernel sends an event signal to the hot- plug system. The hotplug system uses Udev to create a device file for the device and then calls the Figure 1: After you modify the appropriate agent. An agent is a Udev configuration file, the script, typically stored below Gnome desktop icon has a Figure 2: The hal-device-manager with detailed information for the the /etc/hotplug/ directory, that more intuitive label. Prism2 WLAN adapter. 48 ISSUE 53 APRIL 2005 WWW.LINUX- MAGAZINE.COM Hotplugging KNOW-HOW the system loads via other services, as the global rules, you will need to assign This stops the Gnome desktop from dis- well as modules that prevent power a filename to ensure that this happens, playing the generic sda1 label; instead management. for example 10-local.rules. The following the label is a more intuitive mp3disk Linux typically requires a device file in entry is good for a no-name MP3 stick: (Figure 1). The lsusb tool, which lists the order to interact with a device. In a hot- attached USB devices, will help you find plug situation, that device file must be BUS="usb", SYSFS{idProduct}=U the USB IDs. If a device file exists, created on the fly when the new device "1000", SYSFS{idVendor}="10d6",U udevinfo -q path -n /dev/devicefile dis- is detected. As you learned in the pre- NAME="mp3disk" plays the path in the SysFS (see “Box2: ceding section, hotplug uses Udev to cre- Device files with Udev”), but it does not ate the device file prior to summoning give you the mount point /sys. You need the agent. the path as a parameter (-p), with this command to get SysFS information: Device Files as Needed Udev [1] is the designated successor to udevinfo -a -p /block/hda/hda1 static device files, and most current dis- ... tributions now use it. The purpose of SYSFS{idVendor}="10d6" Udev is to create device files based on ... rules specified in a Udev configuration file. For example, if you want to assign a This command helps you discover the device file other than sda1 to your MP3 device-specific values you need for spe- stick, you could specify this requirement cial configurations. There is a detailed in your own Udev rule. how-to for creating Udev files at [2]. The Udev rules are stored in /etc/udev/ Fedora site has a short overview of the rules.d. If you look in that directory, you Udev system [3]. will find a file that describes typical devices: in Ubuntu this is udev.rules, Your Own Usermaps whereas Fedora uses 50-udev.rules. Udev Figure 3: In Gnome 2.8, gnome-volume- A usermap file contains one or multiple reads the files in alphabetic order. If you properties specifies which application is run IDs that uniquely identify a hardware want to load your own Udev rule before for which hotplug event. component. When a device that matches Box 1: Hotplug on Suse Linux The Suse Linux approach to hotplugging also has them for hard disks, CD/DVD tion when you attach a memory stick, is different in parts, and the current ver- drives, and a variety of USB devices. but if you have disabled this feature, or if sion does not use the HAL architecture. After hwup has finished, the hotplug you simply close the window, it’s back to It distinguishes between (currently) agent launches. In the case of a USB My Computer. unknown and configured devices and event, the agent will be the USB agent; Suse Linux uses its own icons for the dri- uses the hwup, hwdown, hwstatus, and for network events, the agent will be the ves:/ URL. They are located below /usr/ hwscanqueue programs to support hot- network agent; and so on. If the hotplug share/hotplug/DesktopTemplates/. KDE plugging. Suse stores a configuration system fails to find a suitable agent, it adds the name to the ~/.kde/share/con- file in /etc/sysconfig/hardware for config- launches a generic agent to create the fig/kio_drivesrc file. You can edit the file ured devices. When the kernel registers required device files. In Suse Linux 9.2, to assign intuitive and unique names to a hotplug event, /sbin/hotplug loads the the agent also looks in /etc/sysconfig for your devices. For example, if you have appropriate kernel module. a configuration file for the service and two memory sticks, you can simply edit No HAL launches the appropriate service. the entries below [Used Names] to dis- After loading the kernel module, hwup Suse Linux has a simple approach to tinguish between them. checks if there is a configuration file for bug hunting that makes hotplug slightly To enable the device icons for the KDE the device below /etc/sysconfig/hard- more verbose. To enable this, set the desktop in Suse, you first need to install ware and, if so, loads the modules speci- variable HOTPLUG_DEBUG in the kdebase3-extra and kdemultimedia3- fied by the file. If hwup fails to locate a /etc/syconfig/hotplug to yes or even to extra packages. Take care if you have configuration file, it attempts to locate max. The latter setting tells the system Suse 9.2: the packages are only on the the required modules by reading the to log every single step. DVD version! After completing the *.usermap files in /etc/hotplug/, just as Desktop Icons on Suse Linux install, right click on the KDE desktop other distributions do. Suse Linux Version 9.1 or later does not and select Configure desktop… in the drop-down menu. In the Behavior win- In the future, Suse is looking to create a create desktop icons for drives. Instead, dow, select Device icons and then check file below /etc/sysconfig/hardware for users are expected to use the My Com- Enable icons on desktop. You can then every hardware component and to com- puter icon (just like in Windows) or to use the list to specify which device icons pletely do without usermap files. Com- access drives directly via the drives:/ you want to display on the desktop. paring the last two Suse versions shows URL. This solution can be a less than After installing kdebase3-extra and kde- that Suse is already heading in this perfect for USB memory sticks. By multimedia3-extra, the devices:/ URL will direction. Whereas 9.1 only creates con- default, Suse opens a Konqueror win- also work in Konqueror. figuration files for network devices, 9.2 dow with the content of the stick parti- WWW.LINUX- MAGAZINE.COM ISSUE 53 APRIL 2005 49 KNOW-HOW Hotplugging one of these entries is plugged into the prism2 0x0003 0x0846 0x4110 The script we want to run, prism2, system, the subsystem automatically 0x0000 0x0000 0x00 0x00 0x00 needs to be in the same directory, and runs the specified program, which can 0x00 0x00 0x00 0x0 we need to run chmod +x to make it be a script. executable. In our example, it runs the This allows you to enable a WLAN USB Most maps look like this and only use rc.wlan start script from the Prism2 adapter that your distribution does not the first four values. The first value spec- package, configures the wlan0 network properly configure.
Recommended publications
  • Enable USB Drivers on Linux
    Enable USB drivers on Linux INTHISDOCUMENT · Enable USB driver on system with USBFS support · Enable USB driver on system without USBFS support · Additional notes for FTDI/XTAG debug adapters The XMOS tools interface to development boards using USB debug adapters. USB driver support is provided natively on Linux, but in some cases, the driver must be enabled. The method required to enable the driver depends on the Linux distribution you are using and the kernel version. Linux distributions known to provide USBFS support include: · Ubuntu 9.04 or older · Ubuntu 9.10 with kernel 2.6.31-19-server · CentOS 4.8 and 5.4 · Generally, any distribution with kernel version < 2.6.32 Linux distributions known to not provide USBFS support include: · Ubuntu 10.04 · Generally, any distribution with kernel version >= 2.6.32 1 Enable USB driver on system with USBFS support If your distribution provides USBFS support, use the following command to enable the Linux driver: · mount -t usbfs none /proc/bus/usb -o devmode=0666 To automatically enable the driver on boot, add the following line to the file /etc/fstab: none /proc/bus/usb usbfs defaults,devmode=0666 0 0 Publication Date: 2012/10/30 Document Number: X2612A XMOS © 2012, All Rights Reserved Enable USB drivers on Linux 2/3 2 Enable USB driver on system without USBFS support If you distribution does not provide USBFS support, you must configure udev to recognise the device. To configure udev, follow these steps: 1. Create a file /etc/udev/rules.d/99-xmos.rules with the following contents: SUBSYSTEM!="usb|usb_device", GOTO="xmos_rules_end" ACTION!="add", GOTO="xmos_rules_end" # 20b1:f7d1 for xmos xtag2 ATTRS{idVendor}=="20b1", ATTRS{idProduct}=="f7d1", MODE="0666", SYMLINK+="xtag2-%n" # 0403:6010 for XC-1 with FTDI dual-uart chip ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", MODE="0666", SYMLINK+="xc1-%n" LABEL="xmos_rules_end" The ATTRS, MODE and SYMLINK stanzas must be all on one line, as each rule can only be on one line.
    [Show full text]
  • Flexible Lustre Management
    Flexible Lustre management Making less work for Admins ORNL is managed by UT-Battelle for the US Department of Energy How do we know Lustre condition today • Polling proc / sysfs files – The knocking on the door model – Parse stats, rpc info, etc for performance deviations. • Constant collection of debug logs – Heavy parsing for common problems. • The death of a node – Have to examine kdumps and /or lustre dump Origins of a new approach • Requirements for Linux kernel integration. – No more proc usage – Migration to sysfs and debugfs – Used to configure your file system. – Started in lustre 2.9 and still on going. • Two ways to configure your file system. – On MGS server run lctl conf_param … • Directly accessed proc seq_files. – On MSG server run lctl set_param –P • Originally used an upcall to lctl for configuration • Introduced in Lustre 2.4 but was broken until lustre 2.12 (LU-7004) – Configuring file system works transparently before and after sysfs migration. Changes introduced with sysfs / debugfs migration • sysfs has a one item per file rule. • Complex proc files moved to debugfs • Moving to debugfs introduced permission problems – Only debugging files should be their. – Both debugfs and procfs have scaling issues. • Moving to sysfs introduced the ability to send uevents – Item of most interest from LUG 2018 Linux Lustre client talk. – Both lctl conf_param and lctl set_param –P use this approach • lctl conf_param can set sysfs attributes without uevents. See class_modify_config() – We get life cycle events for free – udev is now involved. What do we get by using udev ? • Under the hood – uevents are collect by systemd and then processed by udev rules – /etc/udev/rules.d/99-lustre.rules – SUBSYSTEM=="lustre", ACTION=="change", ENV{PARAM}=="?*", RUN+="/usr/sbin/lctl set_param '$env{PARAM}=$env{SETTING}’” • You can create your own udev rule – http://reactivated.net/writing_udev_rules.html – /lib/udev/rules.d/* for examples – Add udev_log="debug” to /etc/udev.conf if you have problems • Using systemd for long task.
    [Show full text]
  • The Interplay of Compile-Time and Run-Time Options for Performance Prediction Luc Lesoil, Mathieu Acher, Xhevahire Tërnava, Arnaud Blouin, Jean-Marc Jézéquel
    The Interplay of Compile-time and Run-time Options for Performance Prediction Luc Lesoil, Mathieu Acher, Xhevahire Tërnava, Arnaud Blouin, Jean-Marc Jézéquel To cite this version: Luc Lesoil, Mathieu Acher, Xhevahire Tërnava, Arnaud Blouin, Jean-Marc Jézéquel. The Interplay of Compile-time and Run-time Options for Performance Prediction. SPLC 2021 - 25th ACM Inter- national Systems and Software Product Line Conference - Volume A, Sep 2021, Leicester, United Kingdom. pp.1-12, 10.1145/3461001.3471149. hal-03286127 HAL Id: hal-03286127 https://hal.archives-ouvertes.fr/hal-03286127 Submitted on 15 Jul 2021 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. The Interplay of Compile-time and Run-time Options for Performance Prediction Luc Lesoil, Mathieu Acher, Xhevahire Tërnava, Arnaud Blouin, Jean-Marc Jézéquel Univ Rennes, INSA Rennes, CNRS, Inria, IRISA Rennes, France [email protected] ABSTRACT Both compile-time and run-time options can be configured to reach Many software projects are configurable through compile-time op- specific functional and performance goals. tions (e.g., using ./configure) and also through run-time options (e.g., Existing studies consider either compile-time or run-time op- command-line parameters, fed to the software at execution time).
    [Show full text]
  • Mashup Architecture for Connecting Graphical Linux Applications Using a Software Bus Mohamed-Ikbel Boulabiar, Gilles Coppin, Franck Poirier
    Mashup Architecture for Connecting Graphical Linux Applications Using a Software Bus Mohamed-Ikbel Boulabiar, Gilles Coppin, Franck Poirier To cite this version: Mohamed-Ikbel Boulabiar, Gilles Coppin, Franck Poirier. Mashup Architecture for Connecting Graph- ical Linux Applications Using a Software Bus. Interacción’14, Sep 2014, Puerto de la Cruz. Tenerife, Spain. 10.1145/2662253.2662298. hal-01141934 HAL Id: hal-01141934 https://hal.archives-ouvertes.fr/hal-01141934 Submitted on 14 Apr 2015 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Mashup Architecture for Connecting Graphical Linux Applications Using a Software Bus Mohamed-Ikbel Gilles Coppin Franck Poirier Boulabiar Lab-STICC Lab-STICC Lab-STICC Telecom Bretagne, France University of Bretagne-Sud, Telecom Bretagne, France gilles.coppin France mohamed.boulabiar @telecom-bretagne.eu franck.poirier @telecom-bretagne.eu @univ-ubs.fr ABSTRACT functionalities and with different and redundant implemen- Although UNIX commands are simple, they can be com- tations that forced special users as designers to use a huge bined to accomplish complex tasks by piping the output of list of tools in order to accomplish a bigger task. In this one command, into another's input.
    [Show full text]
  • Modeling of Hardware and Software for Specifying Hardware Abstraction
    Modeling of Hardware and Software for specifying Hardware Abstraction Layers Yves Bernard, Cédric Gava, Cédrik Besseyre, Bertrand Crouzet, Laurent Marliere, Pierre Moreau, Samuel Rochet To cite this version: Yves Bernard, Cédric Gava, Cédrik Besseyre, Bertrand Crouzet, Laurent Marliere, et al.. Modeling of Hardware and Software for specifying Hardware Abstraction Layers. Embedded Real Time Software and Systems (ERTS2014), Feb 2014, Toulouse, France. hal-02272457 HAL Id: hal-02272457 https://hal.archives-ouvertes.fr/hal-02272457 Submitted on 27 Aug 2019 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Modeling of Hardware and Software for specifying Hardware Abstraction Layers Yves BERNARD1, Cédric GAVA2, Cédrik BESSEYRE1, Bertrand CROUZET1, Laurent MARLIERE1, Pierre MOREAU1, Samuel ROCHET2 (1) Airbus Operations SAS (2) Subcontractor for Airbus Operations SAS Abstract In this paper we describe a practical approach for modeling low level interfaces between software and hardware parts based on SysML operations. This method is intended to be applied for the development of drivers involved on what is classically called the “hardware abstraction layer” or the “basic software” which provide high level services for resources management on the top of a bare hardware platform.
    [Show full text]
  • ANDROID PRIVACY THROUGH ENCRYPTION by DANIEL
    ANDROID PRIVACY THROUGH ENCRYPTION by DANIEL DEFREEZ A THESIS Presented to the Department of Computer Science in partial fullfillment of the requirements for the degree of Master of Science in Mathematics and Computer Science Ashland, Oregon May 2012 ii APPROVAL PAGE “Android Privacy Through Encryption,” a thesis prepared by Daniel DeFreez in partial fulfillment of the requirements for the Master of Science in Mathematics and Computer Science. This project has been approved and accepted by: Dr. Lynn Ackler, Chair of the Examining Committee Date Pete Nordquist, Committee Member Date Hart Wilson, Committee Member Date Daniel DeFreez c 2012 iii ABSTRACT OF THESIS ANDROID PRIVACY THROUGH ENCRYPTION By Daniel DeFreez This thesis explores the field of Android forensics in relation to a person’s right to privacy. As the field of mobile forensics becomes increasingly sophisticated, it is clear that bypassing common privacy measures, such as disk encryption, will become routine. A new keying method for eCryptfs is proposed that could significantly mitigate memory attacks against encrypted file systems. It is shown how eCryptfs could be modified to implement this keying method on an Android device. iv ACKNOWLEDGMENTS I would like to thank Dr. Lynn Ackler for introducing me to the vast world of computer security and forensics, cultivating a healthy paranoia, and for being a truly excellent teacher. Dr. Dan Harvey, Pete Nordquist, and Hart Wilson provided helpful feedback during the preparation of this thesis, for which I thank them. I am deeply indebted to my friends and colleagues Brandon Kester, Andrew Krug, Adam Mashinchi, Jeff McJunkin, and Stephen Perkins, for their enthusiastic interest in the forensics and security fields, insightful comments, love of free software, and encouraging words.
    [Show full text]
  • Installing a Real-Time Linux Kernel for Dummies
    Real-Time Linux for Dummies Jeroen de Best, Roel Merry DCT 2008.103 Eindhoven University of Technology Department of Mechanical Engineering Control Systems Technology group P.O. Box 513, WH -1.126 5600 MB Eindhoven, the Netherlands Phone: +31 40 247 42 27 Fax: +31 40 246 14 18 Email: [email protected], [email protected] Website: http://www.dct.tue.nl Eindhoven, January 5, 2009 Contents 1 Introduction 1 2 Installing a Linux distribution 3 2.1 Ubuntu 7.10 . .3 2.2 Mandriva 2008 ONE . .6 2.3 Knoppix 3.9 . 10 3 Installing a real-time kernel 17 3.1 Automatic (Ubuntu only) . 17 3.1.1 CPU Scaling Settings . 17 3.2 Manually . 18 3.2.1 Startup/shutdown problems . 25 4 EtherCAT for Unix 31 4.1 Build Sources . 38 4.1.1 Alternative timer in the EtherCAT Target . 40 5 TUeDACs 43 5.1 Download software . 43 5.2 Configure and build software . 44 5.3 Test program . 45 6 Miscellaneous 47 6.1 Installing ps2 and ps4 printers . 47 6.1.1 In Ubuntu 7.10 . 47 6.1.2 In Mandriva 2008 ONE . 47 6.2 Configure the internet connection . 48 6.3 Installing Matlab2007b for Unix . 49 6.4 Installing JAVA . 50 6.5 Installing SmartSVN . 50 6.6 Ubuntu 7.10, Gutsy Gibbon freezes every 10 minutes for approximately 10 sec 51 6.7 Installing Syntek Semicon DC1125 Driver . 52 Bibliography 55 A Menu.lst HP desktop computer DCT lab WH -1.13 57 i ii CONTENTS Chapter 1 Introduction This document describes the steps needed in order to obtain a real-time operating system based on a Linux distribution.
    [Show full text]
  • Release Notes for X11R7.5 the X.Org Foundation 1
    Release Notes for X11R7.5 The X.Org Foundation 1 October 2009 These release notes contains information about features and their status in the X.Org Foundation X11R7.5 release. Table of Contents Introduction to the X11R7.5 Release.................................................................................3 Summary of new features in X11R7.5...............................................................................3 Overview of X11R7.5............................................................................................................4 Details of X11R7.5 components..........................................................................................5 Build changes and issues..................................................................................................10 Miscellaneous......................................................................................................................11 Deprecated components and removal plans.................................................................12 Attributions/Acknowledgements/Credits......................................................................13 Introduction to the X11R7.5 Release This release is the sixth modular release of the X Window System. The next full release will be X11R7.6 and is expected in 2010. Unlike X11R1 through X11R6.9, X11R7.x releases are not built from one monolithic source tree, but many individual modules. These modules are distributed as individ- ual source code releases, and each one is released when it is ready, instead
    [Show full text]
  • Thread Scheduling in Multi-Core Operating Systems Redha Gouicem
    Thread Scheduling in Multi-core Operating Systems Redha Gouicem To cite this version: Redha Gouicem. Thread Scheduling in Multi-core Operating Systems. Computer Science [cs]. Sor- bonne Université, 2020. English. tel-02977242 HAL Id: tel-02977242 https://hal.archives-ouvertes.fr/tel-02977242 Submitted on 24 Oct 2020 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Ph.D thesis in Computer Science Thread Scheduling in Multi-core Operating Systems How to Understand, Improve and Fix your Scheduler Redha GOUICEM Sorbonne Université Laboratoire d’Informatique de Paris 6 Inria Whisper Team PH.D.DEFENSE: 23 October 2020, Paris, France JURYMEMBERS: Mr. Pascal Felber, Full Professor, Université de Neuchâtel Reviewer Mr. Vivien Quéma, Full Professor, Grenoble INP (ENSIMAG) Reviewer Mr. Rachid Guerraoui, Full Professor, École Polytechnique Fédérale de Lausanne Examiner Ms. Karine Heydemann, Associate Professor, Sorbonne Université Examiner Mr. Etienne Rivière, Full Professor, University of Louvain Examiner Mr. Gilles Muller, Senior Research Scientist, Inria Advisor Mr. Julien Sopena, Associate Professor, Sorbonne Université Advisor ABSTRACT In this thesis, we address the problem of schedulers for multi-core architectures from several perspectives: design (simplicity and correct- ness), performance improvement and the development of application- specific schedulers.
    [Show full text]
  • Foot Prints Feel the Freedom of Fedora!
    The Fedora Project: Foot Prints Feel The Freedom of Fedora! RRaahhuull SSuunnddaarraamm SSuunnddaarraamm@@ffeeddoorraapprroojjeecctt..oorrgg FFrreeee ((aass iinn ssppeeeecchh aanndd bbeeeerr)) AAddvviiccee 101011:: KKeeeepp iitt iinntteerraaccttiivvee!! Credit: Based on previous Fedora presentations from Red Hat and various community members. Using the age old wisdom and Indian, Free software tradition of standing on the shoulders of giants. Who the heck is Rahul? ( my favorite part of this presentation) ✔ Self elected Fedora project monkey and noisemaker ✔ Fedora Project Board Member ✔ Fedora Ambassadors steering committee member. ✔ Fedora Ambassador for India.. ✔ Editor for Fedora weekly reports. ✔ Fedora Websites, Documentation and Bug Triaging projects volunteer and miscellaneous few grunt work. Agenda ● Red Hat Linux to Fedora & RHEL - Why? ● What is Fedora ? ● What is the Fedora Project ? ● Who is behind the Fedora Project ? ● Primary Principles. ● What are the Fedora projects? ● Features, Future – Fedora Core 5 ... The beginning: Red Hat Linux 1994-2003 ● Released about every 6 months ● More stable “ .2” releases about every 18 months ● Rapid innovation ● Problems with retail channel sales model ● Impossible to support long-term ● Community Participation: ● Upstream Projects ● Beta Team / Bug Reporting The big split: Fedora and RHEL Red Hat had two separate, irreconcilable goals: ● To innovate rapidly. To provide stability for the long-term ● Red Hat Enterprise Linux (RHEL) ● Stable and supported for 7 years plus. A platform for 3rd party standardization ● Free as in speech ● Fedora Project / Fedora Core ● Rapid releases of Fedora Core, every 6 months ● Space to innovate. Fedora Core in the tradition of Red Hat Linux (“ FC1 == RHL10” ) Free as in speech, free as in beer, free as in community support ● Built and sponsored by Red Hat ● ...with increased community contributions.
    [Show full text]
  • The Whole Disk
    COVER STORY DM-Crypt/ LUKS Workshop: Encrypting hard disks with DM-Crypt and LUKS THE WHOLE DISK Encrypting a home directory is easy. Encrypting your whole hard disk – including the root filesystem – takes a little more effort. BY MICHAEL NERB ncrypting individual filesystems means you’ll need to roll up your shirt is no big deal; in fact, some dis- sleeves for some hands-on configuration. Etributions allow you to encrypt In this workshop, we will start by in- directories as part of the installation rou- stalling a standard Linux system and tine. But encrypting the home directory then progress to encrypting the existing on your laptop is a job half done. Dis- filesystems one at a time. We will finish honest finders can still draw conclusions off by deleting the unprotected partition from log and configuration files. If you’re and using the space for other tasks, such serious about providing security through as swapping out the /home directory to encryption, you need to protect the an encrypted partition of its own. whole hard disk against spying – some- Our goal is to encrypt the entire hard thing that no distribution can do out of disk (with the exception of the partition the box. table in the Master Boot Record). Be- Things start to become more complex cause it isn’t possible to encrypt the boot if you need to protect the root filesystem. partition, we will move /boot to an exter- Neither Suse nor Debian Linux give nal medium – a USB stick, in this case. users a tool to help encrypt the root file- To boot from the stick, we will need to system during the install (or later).
    [Show full text]
  • Linux Enumeration of Nics Version 4.1
    Linux Enumeration of NICs Version 4.1 By Robert Hentosh <[email protected]>, Matt Domsch <[email protected]> and Narendra K <[email protected]> . September 2009 Abstract Linux naming of the hardware network interfaces may not align with BIOS and chassis labeling of the Ethernet ports. This is seen on Dell PowerEdge 1950, 1955, 2900, 2950 and newer servers when using a Linux 2.6 kernel-based product such as Red Hat Enterprise Linux 4, 5 and Novell/SuSE Linux Enterprise Server 9, 10 and 11. Solutions to align the Linux name with the expected name are presented. Introduction System administrators may expect the onboard network ports labeled Gb1, Gb2, etc... on a system to be assigned interface names eth0, eth1, etc... respectively. This would be one possible naming convention for network interfaces; however no industry standards currently exist to ensure such a convention. The method used in Linux to determine the number associated with a network port (i.e. eth0, eth1, eth2…) is complex and changed with the 2.6 and newer kernels. The naming disconnect can be observed at two different times: 1. Install Time - OS Installation when network booting (e.g. using a PXE installation procedure); 2. System Runtime – Following OS installation Dell engineers have developed workarounds for Red Hat Enterprise Linux 4 (RHEL4), 5 (RHEL5), and Novell/SuSE Linux Enterprise Server (SLES) 9, 10 and 11 for each of the above scenarios. While the naming disconnect directly affects Dell PowerEdge 1950, 1955, 2900, 2950 and newer servers running Linux 2.6 kernels (eg. RHEL4, RHEL5 , SLES9, SLES10 and SLES 11), this behavior is not unique to Dell systems.
    [Show full text]