DOCSLIB.ORG

Opensolaris Virtualization Technologies

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

OpenSolaris Virtualization Technologies Daniel Price Staff Engineer Solaris Kernel Technology Agenda • Virtualization Overview • Zones • BrandZ • Xen • Q&A The Need for Virtualization • Driven by the need to consolidate multiple hosts and services on a single machine • Leads to... > Increased hardware utilization (currently average data center utilization is below 15%) > Greater flexibility in resource allocation > Reduce power requirements > Minimize management costs > Lower the cost of ownership Types of Virtualization Hard Partitions Virtual Machines OS Virtualization Resource Mgmt. App OS Server Multiple OS's Single OS Trend to flexibility Trend to isolation Dynamic System Logical Domains Solaris Containers Solaris Resource Domains Xen (Zones + SRM) Manager (SRM) BrandZ CrossBow Solaris Zones • Basic concept: isolated execution environment within a Solaris instance • Virtualizes OS layer: file system, devices, network, processes • Provides: > Privacy: can't see outside zone > Security: can't affect activity outside zone > Failure isolation: application failure in one zone doesn't affect others • Lightweight, granular, efficient • No porting for most apps; ABI/APIs are the same Typical Uses for Zones • Consolidating data center workloads such as multiple databases. • Deploying multiple-tier application stacks • Hosting untrusted or hostile applications or those that require global resources like IP port space • Deploying Internet facing services • Software development Zones Block Diagram global zone (v880-room2-rack5-1; 129.76.1.12) dns1 zone (dnsserver1) web1 zone (foo.org) web2 zone (bar.net) mail zone (mailserver) zone root: /zone/dns1 zone root: /zone/web1 zone root: /zone/web2 zone root: /zone/mail1 login services login services login services login services (SSH sshd) (SSH sshd) (SSH sshd, telnetd) (SSH sshd) t n network services network services network services network services n e io t (named) (Apache, Tomcat) (IWS) (sendmail, IMAP) m a n c o li r i p core services core services core services core services v p n (inetd) A (inetd) (inetd) (inetd) E 1 2 3 : : : s s s s 0 0 0 1 2 3 : : : :1 n n n n e e e r r r r 0 0 0 1 o o o o s s s s l m 10 30 m 60 m c e e e e m c c c u u u u r a / z h / z h c / z h c / z c c o u f t t r i a l zoneadmd zoneadmd zoneadmd zoneadmd V P pool1 (4 CPU), FSS pool2 (4 CPU) zone management (zonecfg(1M), zoneadm(1M), zlogin(1), ...) core services remote admin/monitoring platform administration (inetd, rpcbind, sshd, ...) (SNMP, SunMC, WBEM) (syseventd, devfsadm, ifconfig, metadb,...) storage complex network device network device network device (hme0) (ce0) (ce1) Zones Security • Each zone has a security boundary around it • Runs with a subset of privileges(5) • A compromised zone is unable to escalate its privileges • Important name spaces are isolated • BSM auditing can be configured globally or on a per-zone basis • Processes running in a zone are unable to affect activity in other zones Zones Processes • Certain system calls are not permitted or have restricted scope inside a zone • From the global zone, all processes can be seen, but control is privileged • From within a zone, only processes in the same zone can be seen or affected • The /proc file system has been virtualized to only show processes in the same zone Zones Networking • Single TCP/IP stack for the system. > Shields non-global zones from configuration details > Prevents per-zone control (routing, tuning) • Each zone can be assigned any number of IPv4 and IPv6 addresses, and each has its own port space • Applications can bind to INADDR_ANY and will only get packets addressed to that zone • Zones cannot send packets with addresses other than those it has been assigned Zones Observability • From the global zone, process tools like prstat(1M), ps(1), and truss(1) can be used to observe processes in other zones • DTrace can be used from the global zone and supports a “zonename” variable as well as psinfo_t's pr_zoneid field for use with the proc provider, e.g. global# dtrace -n 'io:::start{@[zonename] = count()}' • A subset of the DTrace functionality (non-kernel probes) is available from within non-global zones Zones Configuration & Installation • zonecfg(1M) is used to configure a zone by specifying resources (file-systems, network interfaces, etc) and properties (zone name, file- system directory path, etc) • zoneadm(1M) is used to administer zones (boot, install, etc) • Each Zone is assigned its own file system, constructed by copying packaged files from the global zone. Zones Status • Initially supported in Solaris 10 • Available today through OpenSolaris > Integration with ZFS, faster provisioning with ZFS > Configurable privileges on a per non-global zone basis > Cloning for rapid provisioning > Zone migration, both local (enables zones to be moved and renamed) and remote (using a new attach/detach facility) • Future: > Enhancements to resource management and greater zones/rm integration > Enhanced management, Integration with Live Upgrade BrandZ: Branded Zones • Extends Zones model to support “non-native” zones on a Solaris system > Only supports user-space environments > If you need a different kernel, see Xen • Each distinct zone type is called a Brand • Possible uses: > A Linux zone > A Solaris GNU zone (Nexenta/ShilliX/BeleniX) > Support for Solaris N-1 on Solaris N > A MacOS X zone BrandZ: Brand Implementation • A Brand is composed of the following items: > Required: > An XML brand configuration file and an XML brand platform definition file > Scripts used to install a branded a zone > Optional: > Kernel brand support module > Scripts that can be invoked at zone boot and shutdown > Linker libraries that can be used to help debug branded applications > Userland brand support library > Any other native programs, libraries, or kernel modules needed to support execution of the branded zone BrandZ User-space Infrastructure • Zone utilities call per-brand scripts > At zone installation, zone boot, zone shutdown > Allows brand to customize software installed, execution environment, etc. • Debugging support libraries recognize branded processes and core files > Brand-specific library plugins aid with: > Application and library segment mappings > Address and symbol mappings > Enables tools like mdb, ptools, and the DTrace pid provider, to work without modification BrandZ Kernel Infrastructure • BrandZ adds interposition points to the Solaris kernel: > syscall path, process loading, fork, exit, etc. • Control is transferred to the brand kernel support module. • Allows a brand to replace or modify basic Solaris behaviors. • These interposition points are only applied to branded process. • Fundamentally different brands may require new interposition points The lx Brand • Implements Solaris Containers for Linux Applications • Enables Linux Binaries to run unmodified on Solaris • Creates a zone for Linux application execution > Zone is populated only with Linux software > At boot, it runs the Linux init(1M), configuration scripts, and applications > It all runs on a Solaris kernel. • There is no Linux software delivered with BrandZ > This is not a Linux distro and we do not include our own special Linux software, we install and run standard Linux distributions BrandZ Use Cases • As a transition tool, reducing the Linux “barrier to exit” > Customer would like to move to Solaris, but has legacy Linux applications • Best of both worlds > Users familiar with Linux environment > Administrators want Solaris' enterprise-class features: resource management, fault management, DTrace • Developer/ISV workload > Solaris has strong development tools, let Linux developers leverage them. > We want Solaris to be a better Linux development platform than Linux. BrandZ Status • Available in OpenSolaris now • Will be in Solaris 10 update 4 • Zones running a Red Hat Enterprise Linux 3.x or CentOS 3.5 operating environment > Support for Linux 2.4.21 system call interface > Basic /proc and /dev support • DTrace support for Linux applications > Linux syscall provider and PID provider • Rapid deployment and teardown of Linux zones. Perfect for building 'throwaway' zones for development/QA Hypervisors 101 ● The “Virtual Machine” abstraction ● Virtualizes hardware – memory, CPU, I/O devices ● May emulate real devices ● For x86/x64 multiple choices ● Xen, VMware, Parallels ● MSFT now: Virtual Server, future: Viridian Solaris Containers and Hypervision ● Containers (zones) • Scalable, fast, virtual platform, platform agnostic • Emphasis on sharing, simpler admin • Improved fault isolation over “single system.” • Alternate brands ● Hardware Virtualization • Emphasis on separation • Fault isolation, (Xen: SPOFs remain) • Live Migration • Foreign OSes Para vs Full Virtualization ● Full virtualization ● Runs binary image of “metal” OS ● Must emulate real i/o devices ● Can be slow, needs help from hardware ● May use trap and emulate or rewriting ● Para-virtualization ● Runs OS ported to virtual machine arch ● Uses “virtual” device drivers ● More efficient since it is hypervisor aware Xen • Open source hypervisor technology developed at the University of Cambridge > http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ • OpenSolaris on Xen community > http://www.opensolaris.org/os/community/xen • 2006: HW Virtualization Everywhere > x64 CPU capabilities (VT-x, AMDV) > Workload consolidation Xen Design Principles and Goals ● Existing applications run unmodified ● Support for multi-process, multi-application application environments ● Permit complex server configurations
Recommended publications
  • Solaris Und Opensolaris Eine Sinnvolle Alternative?

    Solaris Und Opensolaris Eine Sinnvolle Alternative?

    Solaris und OpenSolaris Eine sinnvolle Alternative? Wolfgang Stief best Systeme GmbH MUCOSUG, GUUG e. V. [email protected] 2009-11-23 Agenda OpenSolaris, Solaris Express, Solaris Community Edition Das „Open“ in OpenSolaris Community, Lizenzen, Projects Features Container/Zones, ZFS, DTrace, Crossbow ... Und warum dann nicht gleich Linux? Solaris und OpenSolaris – eine sinnvolle Alternative? pg 2 OpenSolaris? Enterprise PowerNetwork ManagementVirtualization Installation Open Containers Storage CIFS Security Network- DTraceNetwork Based ZFS Auto- Packaging Predictive Magic Self Healing Hardware Time Optimizaton Slider Solaris und OpenSolaris – eine sinnvolle Alternative? pg 3 OpenSolaris Binary Distribution http://www.opensolaris.com stabiler, getester Code Support möglich erscheint ca. 2x jährlich, x86 und SPARC aktuelle Pakete (GNOME etc.), Installer neues Paketformat, Repositories ähnlich Debian aktuell (noch) 2009.06 Solaris und OpenSolaris – eine sinnvolle Alternative? pg 4 OpenSolaris Source Code http://www.opensolaris.org ab Juni 2005: zunächst DTrace, dann sukzessive weitere Teile aktive Community Source Browser OpenGrok http://src.opensolaris.org/ Features werden in „Projects“ entwickelt Community Release 2-wöchentlich (b127) „BFU“ nach Bedarf (blindingly fast upgrade) Solaris und OpenSolaris – eine sinnvolle Alternative? pg 5 OpenSolaris Community Launch am 14. Juni 2005 mehrere Distributionen aus der Community Schillix, Belenix, Nexenta, Milax, StormOS, OSUNIX Stand Frühjahr 2009 (ca. 3½ Jahre): → 116.000 registrierte Mitglieder
  • BIONIX – a Solaris Based Platform for Computational Biology Abhishek Pratap1 Prateek Singh2

    BIONIX – a Solaris Based Platform for Computational Biology Abhishek Pratap1 Prateek Singh2

    BIONIX – a Solaris based Platform for Computational Biology Abhishek Pratap1 Prateek Singh2 1 VIT University, Vellore, TN 632014 India [email protected] 2 VIT University, Vellore, TN 632014 India [email protected] Keywords: Live CD, operating system, Integrated Workbench, Software. Bionix is an integrated software workbench, developed for bioinformaticians and computational biologists. Bioinx is a remastered version of Belenix with open source based bioinformatics applications being integrated with the kernel. The fact that distinguishes Bionix from other open source software’s is the performance based on the most advanced operating system technology, Solaris platform with feature like ZFS(128 bit File System), DTrace (Dynamic Tracing Framework), Zones (Multiple application can run in isolation), SMF (Service Management Framework for handling dependencies). There has been significant reduction in the boot time and memory requirements with on the fly compression techniques being used. It is independent of host operating system. It may provide an ad-hoc solution where no Solaris is installed and has the capability of forming a virtual cluster lab in minutes with auto network detection. The entire Emboss package has been remodeled with graphical user interface and onscreen help options, the NCBI toolkit with all flavors of blast and utilities like entrez search and sequin where a biologist can search or submit a sequence without going to web interface, molecular visualization tools like RasMol and Garlic; and a Perl module, bioperl for application development. The work on parallel computing with Bionix is in progress. The entire project has been coordinated with Asia Pacific Science and Technology Center, Sun Microsystems, Singapore.
  • Oracle VM Virtualbox Container Domains for SPARC Or X86

    Oracle VM Virtualbox Container Domains for SPARC Or X86

    1 <Insert Picture Here> Virtualisierung mit Oracle VirtualBox und Oracle Solaris Containern Detlef Drewanz Principal Sales Consultant SAFE HARBOR STATEMENT The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. In addition, the following is intended to provide information for Oracle and Sun as we continue to combine the operations worldwide. Each country will complete its integration in accordance with local laws and requirements. In the EU and other non-EU countries with similar requirements, the combinations of local Oracle and Sun entities as well as other relevant changes during the transition phase will be conducted in accordance with and subject to the information and consultation requirements of applicable local laws, EU Directives and their implementation in the individual members states. Sun customers and partners should continue to engage with their Sun contacts for assistance for Sun products and their Oracle contacts for Oracle products. 3 So .... Server-Virtualization is just reducing the number of boxes ? • Physical systems • Virtual Machines Virtualizationplattform Virtualizationplattform 4 Virtualization Use Workloads and Deployment Platforms
  • ISSN: 1804-0527 (Online) 1804-0519 (Print) Vol.8 (2), PP. 63-69 Introduction During the Latest Years, a Lot of Projects Have Be

    ISSN: 1804-0527 (Online) 1804-0519 (Print) Vol.8 (2), PP. 63-69 Introduction During the Latest Years, a Lot of Projects Have Be

    Perspectives of Innovations, Economics & Business, Volume 8, Issue 2, 201 1 EVALUATION OF PERFORMANCE OF SOLARIS TRUSTED EXTENSIONS USING CONTAINERS TECHNOLOGY EVALUATION OF PERFORMANCE OF GENTI DACI SOLARIS TRUSTED EXTENSIONS USING CONTAINERS TECHNOLOGY Faculty of Information Technology Polytechnic University of Tirana, Albania UDC: 004.45 Key words: Solaris Containers. Abstract: Server and system administrators have been concerned about the techniques on how to better utilize their computing resources. Today, there are developed many technologies for this purpose, which consists of running multiple applications and also multiple operating systems on the same hardware, like VMWARE, Linux-VServer, VirtualBox, Xen, etc. These systems try to solve the problem of resource allocation from two main aspects: running multiple operating system instances and virtualizing the operating system environment. Our study presents an evaluation of scalability and performance of an operating system virtualization technology known as Solaris Containers, with the main objective on measuring the influence of a security technology known as Solaris Trusted Extensions. Solaris. We will study its advantages and disadvantages and also the overhead that it introduces to the scalability of the system’s main advantages. ISSN: 1804 -0527 (online) 1804 -0519 (print) Vol.8 (2), PP. 63 -69 Introduction administration because there are no multiple operating system instances in a system. During the latest years, a lot of projects have been looking on virtualizing operating system Operating systems environments, such as FreeBSD Jail, Linux- VServer, Virtuozzo etc. This virtualization technique is based in using only one underlying Solaris/OpenSolaris are Operating Systems operating system kernel. Using this paradigm the performing as the main building blocks of computer user has the possibility to run multiple applications systems; they provide the interface between user in isolation from each other.
  • The Server Virtualization Landscape, Circa 2007

    The Server Virtualization Landscape, Circa 2007

    ghaff@ illuminata.com Copyright © 2007 Illuminata, Inc. single user license Gordon R Haff Illuminata, Inc. TM The Server Virtualization Bazaar, Circa 2007 Inspired by both industry hype and legitimate customer excitement, many Research Note companies seem to have taken to using the “virtualization” moniker more as the hip phrase of the moment than as something that’s supposed to convey actual meaning. Think of it as “eCommerce” or “Internet-enabled” for the Noughts. The din is loud. It doesn’t help matters that virtualization, in the broad sense of “remapping physical resources to more useful logical ones,” spans a huge swath of Gordon Haff technologies—including some that are so baked-in that most people don’t even 27 July 2007 think of them as virtualization any longer. Personally licensed to Gordon R Haff of Illuminata, Inc. for your personal education and individual work functions. Providing its contents to external parties, including by quotation, violates our copyright and is expressly forbidden. However, one particular group of approaches is capturing an outsized share of the limelight today. That would, of course, be what’s commonly referred to as “server virtualization.” Although server virtualization is in the minds of many inextricably tied to the name of one company—VMware—there are many companies in this space. Their offerings include not only products that let multiple virtual machines (VMs) coexist on a single physical server, but also related approaches such as operating system (OS) virtualization or containers. In the pages that follow, I offer a guide to today’s server virtualization bazaar— which at first glance can perhaps seem just a dreadfully confusing jumble.
  • Asesor Profesional: - Carrera: Licenciatura En Informática

    Asesor Profesional: - Carrera: Licenciatura En Informática

    Título: Redes inalámbricas ad-hoc autoconfigurables. Caso de estudio e implementación Autores: Marcos Mazzini Director: Ing. Luis Marrone Codirector: Lic. Paula Venosa Asesor profesional: - Carrera: Licenciatura en Informática Cualquier computadora portátil medianamente moderna ya cuenta con una placa de red inalámbrica y soporte para redes ad-hoc o sea que cada placa de red puede reenviar datos a cualquier otra que esté a su alcance sin necesidad de un nodo centralizado, pero esta configuración no viene por defecto en los distintos sistemas operativos y en general se requiere instalar y configurar software adicional para que la comunicación sea simple para el usuario no experto. Con la idea de facilitar el aprovechamiento del hardware con el que cuentan estas computadoras, se investigaron las tecnologías existentes que permiten configurar las placas de red en modo ad-hoc, asignar direcciones IP en forma descentralizada, resolver nombres de forma descentralizada y anunciar servicios de cada computadora en un entorno de red. Con esta información se derivó una versión Live CD de Linux con aplicaciones para redes preconfiguradas, soporte para placas de red Wi-Fi y modo ad-hoc preconfigurado de modo que si dos o más notebooks bootean este sistema puedan intercambiar archivos, compartir información, chatear y visualizar remotamente los escritorios y utilizar aplicaciones de red entre ellas sin ninguna necesidad de configurar, instalar o modificar los sistemas existentes y sin necesidad de conectarse a un Access Point. Wi-Fi Ad-Hoc LiveCD Linux Cigarra Conectar Igualdad Se verificó que las tecnologías analizadas son Debian Live Zeroconf Avahi mDNS Link Local IP compatibles y que resuelven la funcionalidad esperada.
  • Virtual Containers: Asset Management Best Practices and Licensing Considerations

    Virtual Containers: Asset Management Best Practices and Licensing Considerations

    Virtual Containers: Asset Management Best Practices and Licensing Considerations Virtual containers have seen tremendous adoption and growth within all industries. However, in terms of IT asset management, cont- ainers are not being managed and are an unknown area of risk for many of our clients. Because it is a newer technology, there is very little information about managing containers and how to address the emerging SAM & ITAM challenges they bring. Due to this lack of public information, Anglepoint has published this whitepaper on navigating the world of containers, with an empha- sis on asset management and licensing. We will cover everything from the history of containers, to what containers are, the benefits of containers, asset management best practices, and some publisher-specific licensing considerations. A BRIEF HISTORY OF VIRTUAL CONTAINERS The first proper containers came from the Linux world as LXC (LinuX Containers) in 2008. However, it wasn’t until 2013 that containers entered the IT public consciousness, when Docker came onto the scene with Enterprise usage in mind. Even then, though, it was more of an enthusiast’s technology. In 2015, Google released and open sourced Kubernetes which manages and ‘orchestrates’ containers. However, it wasn’t until 2017 that Docker and Kubernetes had matured enough to be considered for production use within corporate environments. 2017 also saw VMware, Microsoft, and Amazon beginning to support and offer solutions for Kubernetes and Docker on their top-tier cloud infrastructure. WHAT IS A CONTAINER? Often, people conflate the term ‘container’ with multiple technologies that make up the container ecosystem. Let’s look at what a modern container is at the most fundamental level.
  • Adventures with Illumos

    Adventures with Illumos

    > Adventures with illumos Peter Tribble Theoretical Astrophysicist Sysadmin (DBA) Technology Tinkerer > Introduction ● Long-time systems administrator ● Many years pointing out bugs in Solaris ● Invited onto beta programs ● Then the OpenSolaris project ● Voted onto OpenSolaris Governing Board ● Along came Oracle... ● illumos emerged from the ashes > key strengths ● ZFS – reliable and easy to manage ● Dtrace – extreme observability ● Zones – lightweight virtualization ● Standards – pretty strict ● Compatibility – decades of heritage ● “Solarishness” > Distributions ● Solaris 11 (OpenSolaris based) ● OpenIndiana – OpenSolaris ● OmniOS – server focus ● SmartOS – Joyent's cloud ● Delphix/Nexenta/+ – storage focus ● Tribblix – one of the small fry ● Quite a few others > Solaris 11 ● IPS packaging ● SPARC and x86 – No 32-bit x86 – No older SPARC (eg Vxxx or SunBlades) ● Unique/key features – Kernel Zones – Encrypted ZFS – VM2 > OpenIndiana ● Direct continuation of OpenSolaris – Warts and all ● IPS packaging ● X86 only (32 and 64 bit) ● General purpose ● JDS desktop ● Generally rather stale > OmniOS ● X86 only ● IPS packaging ● Server focus ● Supported commercial offering ● Stable components can be out of date > XStreamOS ● Modern variant of OpenIndiana ● X86 only ● IPS packaging ● Modern lightweight desktop options ● Extra applications – LibreOffice > SmartOS ● Hypervisor, not general purpose ● 64-bit x86 only ● Basis of Joyent cloud ● No inbuilt packaging, pkgsrc for applications ● Added extra features – KVM guests – Lots of zone features –
  • Containerisation Gareth Roy Gridpp 32, Pitlochry �1 Intermodal Containers

    Containerisation Gareth Roy Gridpp 32, Pitlochry 1 Intermodal Containers

    Containerisation Gareth Roy GridPP 32, Pitlochry "1 Intermodal Containers Developed by Malcolm P. McLean & Keith W. Tantlinger. Reaction to slow loading times produced by using “break bulk cargo.” Apparatus for shipping freight (1958): “In 1956, loose cargo cost $5.86 per ton US 2853968 A - Malcolm P McLean to load. Using an ISO shipping container, the cost was reduced to only .16 cents per ton.” IMPERIAL METRIC Length 19’ 10.5” 6.058 m Width 8’ 0” 2.438 m Height 8’ 6” 2.591 m Empty Weight 4,850 lb 2,200 kg Max Weight 66,139 lb 30,400 kg "2 Mærsk Mc-Kinney Møller (18270 TEU) Linux Containers Form of OS Level Virtualisation. Kernel hosts multiple separated user-land instances (Virtual Environment/Engine). Application Low overheads, elastic, multi-tennant. VE Storage can be Copy-on-Write or use UnionFS OS Examples: chroot (1982) Solaris Containers (2005) Physical Hardware FreeBSD Jails (1988) AIX WPARS (2007) Virtuozzo (2001) LXC (2008) OpenVZ (2005) "3 VM’s vs Containers Application Application Application Application Guest OS Guest OS VE VE Virtual HW Virtual HW OS Hypervisor / OS Physical Hardware Physical Hardware Virtual Machine Linux Container "4 VM’s vs Containers (Arguments) Pros: Pros: OS Independent Lightweight / Dense Secure / Isolated Fast Instantiation Flexible Elastic Resource Live Migration Low Memory Consumption Mature Ecosystem Native Performance Cons: Cons: Full System Image Restricted / Linux Only Slow Startup/Shutdown/Build Shared Kernel Memory Consumption Overhead Security Model Opaque to System Young Ecosystem Virtual Machine Linux Container "5 Containers in More Detail Running Application Application Application Instanced Namespace Virtual Environment Virtual Environment Resource Control Group Container CGROUP Container CGROUP Kernel Namespace Layer PID MNT IPC NET UTS USER* Linux Kernel > 2.6.23 OS Physical Hardware "6 Namespaces Application A Namespace wraps a global resource and presents an isolated instance to running process.
  • Guía De Instalación Y Uso De Belenix

    Guía De Instalación Y Uso De Belenix

    Guía de instalación y uso de Belenix Notas de uso BeleniX se inicia desde un CD y es bastante fácil de entender. No obstante, algunas notas ayudan a utilizarlo: 1. Al arrancarlo, se solicita realizar dos acciones: seleccionar la distribución del teclado, y si se prefiere el modo de línea de comandos o la GUI de XWindows. 2. Tras el arranque, es posible alternar entre el modo de línea de comandos y la GUI. El comando "startgui" inicia los servicios de Xserver y abre el escritorio de Xfce. El comando "stopgui" detiene los servicios de Xserver y vuelve al modo de línea de comandos. 3. BeleniX solicita un nombre de usuario y contraseña en el inicio de sesión de la línea de comandos. De forma predeterminada, el nombre de usuario es "root" y la contraseña "belenix". En el escritorio de la GUI todavía no se solicita ningún nombre de usuario ni contraseña. 4. Al iniciar el escritorio de la GUI por primera vez, aparece en pantalla el mensaje de seguimiento "Call Stack of Bad Caller". Este mensaje no genera ningún error; se trata de un problema conocido del controlador de apertura que utiliza una API de núcleo obsoleta. 5. BeleniX montará automáticamente las particiones reconocidas del disco duro en /mnt. La primera partición FAT se montará en /mnt/fat0, y así sucesivamente. De modo similar, los segmentos UFS se montarán en /mnt/solaris0..n. Es una función de recuperación. 6. Asimismo, BeleniX intentará utilizar un segmento de intercambio en el disco duro si ya hay una partición de Solaris con el intercambio configurado.
  • Container Technologies

    Container Technologies

    Zagreb, NKOSL, FER Container technologies Marko Golec · Juraj Vijtiuk · Jakov Petrina April 11, 2020 About us ◦ Embedded Linux development and integration ◦ Delivering solutions based on Linux, OpenWrt and Yocto • Focused on software in network edge and CPEs ◦ Continuous participation in Open Source projects ◦ www.sartura.hr Introduction to GNU/Linux ◦ Linux = operating system kernel ◦ GNU/Linux distribution = kernel + userspace (Ubuntu, Arch Linux, Gentoo, Debian, OpenWrt, Mint, …) ◦ Userspace = set of libraries + system software Linux kernel ◦ Operating systems have two spaces of operation: • Kernel space – protected memory space and full access to the device’s hardware • Userspace – space in which all other application run • Has limited access to hardware resources • Accesses hardware resources via kernel • Userspace applications invoke kernel services with system calls User applications E.g. bash, LibreOffice, GIMP, Blender, Mozilla Firefox, etc. System daemons: Windowing system: User mode Low-level system systemd, runit, logind, X11, Wayland, Other libraries: GTK+, Qt, EFL, SDL, SFML, Graphics: Mesa, AMD components networkd, PulseAudio, SurfaceFlinger FLTK, GNUstep, etc. Catalyst, … … (Android) C standard library Up to 2000 subroutines depending on C library (glibc, musl, uClibc, bionic) ( open() , exec() , sbrk() , socket() , fopen() , calloc() , …) About 380 system calls ( stat , splice , dup , read , open , ioctl , write , mmap , close , exit , etc.) Process scheduling Memory management IPC subsystem Virtual files subsystem Network subsystem Kernel mode Linux Kernel subsystem subsystem Other components: ALSA, DRI, evdev, LVM, device mapper, Linux Network Scheduler, Netfilter Linux Security Modules: SELinux, TOMOYO, AppArmor, Smack Hardware (CPU, main memory, data storage devices, etc.) TABLE 1 Layers within Linux Virtualization Virtualization Concepts Two virtualization concepts: ◦ Hardware virtualization (full/para virtualization) • Emulation of complete hardware (virtual machines - VMs) • VirtualBox, QEMU, etc.
  • The Open Pitt What's Cooking in Linux and Open Source in Western Pennsylvania Issue 25 June 2006

    The Open Pitt What's Cooking in Linux and Open Source in Western Pennsylvania Issue 25 June 2006

    The Open Pitt What's cooking in Linux and Open Source in Western Pennsylvania Issue 25 June 2006 www.wplug.org From the Editors: The Long Haul As The Open Pitt begins its third year Today, estimates of market share for Call for Speakers: of publication, it seems appropriate to Mozilla and Firefox combined range Ohio LinuxFest be a bit retrospective. You may have from 9% to 12%, depending on which heard the proverb: all it takes are source you consult. The fourth annual Ohio LinuxFest years and years of hard work to be- Are you seeing a pattern here? will again be held in Columbus, Ohio, and presenters are needed come an overnight success. It's pretty Those endeavors which achieve great well-suited to Open Source and Free to deliver talks about Free and success do so largely through the Open Source Software topics. Software as sayings go. years, if not decades, of effort put for- The event will take place on After all, the “upstart” Linux kernel ward by the people involved. As any September 30, 2006, and propos- has been in public development for 15 parent knows, the work doesn't end at als should be submitted by July 10 years. And the GNU project, whose childbirth—that's just the beginning of using the on-line form available tools are included in each distribution a twenty-year project. from <http://www.ohiolinux.org/ of Linux, was formed 24 years ago. So let's take a look at some re- speak.html>. The original release of BSD, the fore- cently-born projects.