LPI Linux LPIC1

Total Page:16

File Type:pdf, Size:1020Kb

LPI Linux LPIC1 LPI Linux LPIC1 Module 2 Module Contents • 1 Evans Ikua Lead Editor Kenya [email protected] • 2 Chris Brown Content Author UK [email protected] • 3 Mark Clarke Content Author RSA [email protected] • 4 Brian Ssennoga Content Author Uganda [email protected] • 5 Trust Zifa Material co-editor Zimbabwe [email protected] • 6 John Matogo Material co-editor Kenya john [email protected] • 7 Ken Mutua Material co-editor Kenya [email protected] • 8 Bernard Owuor Material co-editor Kenya [email protected] • 9 Sisay Adugna Material co-editor Ethiopia [email protected] • 10 Balthas Seibold Senior Project • Manager - GIZ • Germany [email protected] • 11 Petra Hagemann Project Manager - GIZ Germany [email protected] • 12 George Nyambuya Africa Coordinator - • ict@innovation • RSA [email protected] • 13 David Paulus Intern - GIZ Germany [email protected] Module Contents • Design hard disk layout • Install a boot manager • Manage shared libraries • Use Debian package management • Use RPM and YUM package management Design hard disk layout Linux creates filesystems on block devices. A device whose data can only be accessed sequentially, such as keyboards and mice are character devices but devices such as hard-disks, that can have their data accessed randomly are call block devices. Each type of device has different functionality to cater for the differences in data access methods. The Linux kernel's device-mapper framework allows for the creation of virtual block devices on which filesystems can be created. The advantage of virtual block devices is that Linux can provide functionality such as encrypted drives and raid devices without the need for specialist hardware. Virtual block devices allow for the creation of LVM (Logical Volume Manager) drives. Design hard disk layout Common Partition Schemes 1. Small systems – Boot partition - 50-100MB usually on the 1st partition to ensure all kernels are below the 1024 cylinder limit for older kernel BIOS. – Swap partition - Swap space allocation depends on he amount of physcial ram available. There is much debate about the optimal size of the partition for swap space, especially as the amount of physical memory available in most systems is increasing, but a general rule of thumb is to use twice the amount of ram available but a maximum of around 1 G is recommended. Design hard disk layout Common Partition Schemes – / The root filesystem partition contains the rest of the Linux operating system and should usually be allocated the remaining disk space. Most distributions today will install the root partition on an logical partition to allow for the possibility of creating more than 4 partitions in future should this be necessary. Design hard disk layout Common Partition Schemes 2. Larger systems – Boot partition - 100MB-250MB In more modern computers, that do not have the 1024 cylinder limit, you may want to allocate more space to the boot to accommodate additional kernels. Keeping the /boot separate may be necessary especially if the remaining filesystems are loaded on virtual block devices which the boot loader cannot access natively, for example they root filesystem is on a software raid5 block device. Design hard disk layout Common Partition Schemes –Swap partition - as above –/home - The /home directory is where all user data and documents are kept. A separate partition means that it will be easier to backup data and protects the kernel and other core system files from running out of disk space due to users storing too much data in their home directories. – /usr - The user directory contains is user application. Usually the /usr directory does not grow that much in size and is fairly static. Design hard disk layout Common Partition Schemes –/var - The /var directory contains system log files. Logs files, especially if not maintained properly, can rapidly fill up disk space. By placing the /var directory on a different drive the rest of the system is protected from running out of disk space. –/tmp - The /tmp directory is used to house all temporary files. The directory should be cleaned upon reboot or when users log out but often files are left behind. Over time this can cause the system to run out of disk space. Placing /tmp in its own directory protects the rest of the system form this. Design hard disk layout How to Partition Using fdisk The fdisk command takes the block device you wish to partition as a parameter. For example to partition the master drive on the primary connector for a SATA drive the command would be: fdisk /dev/sda The fdisk utility provides you with a command prompt to create and delete partitions on block devices. Pressing “m” at the prompt will provide you with a list of possible actions to perform on the Design hard disk layout How to Partition Using fdisk Command action options: • a toggle a bootable flag • b edit bsd disklabel • c toggle the dos compatibility flag • d delete a partition • l list known partition types • m print this menu • n add a new partition • o create a new empty DOS partition table Design hard disk layout How to Partition Using fdisk • p print the partition table • q quit without saving changes • s create a new empty Sun disklabel • t change a partition's system id • u change display/entry units • v verify the partition table • w write table to disk and exit • x extra functionality (experts only) Design hard disk layout Filesystem types in Linux A filesystem is a way of storing data in a computer- accessible form on the hard disk. Different filesystems have different algorithms and structures to determine where the data and indexing information, needed by the computer to find data, will be stored. Meta-data relating to the organisation of the filesystem is stored in areas of the disk called superblocks. Superblocks contain critical information for the computer to find files and data on disk. Design hard disk layout Filesystem types in Linux Some popular Linux filesystems include: • ext2 – the oldest and most well supported filesystem on Linux machines. • ext3 - an extension of the ext2 filesystem which adds journaling support • ext4 – an extension of the ext3 filesystem, supporting bigger volumes, more subfolders handled (up to 32000), extents and pre-allocation handling, etc. • reiserfs - an enhanced journaling filesystem written by Hans Reiser Design hard disk layout Managing Swap space Swap space does not contain a file system but is accessed in raw mode by the Linux kernel. By passing a filesystem has some speed advantages which is crucial for swap space. After creating the disk partition to be used as swap space , you will need to activate it. For example: swapon /dev/sda2 During system insallation this will be done automatically for you. Information on the swap partition can be displayed with swapon. swapon -s Design hard disk layout Install a boot manager A boot loader is installed in the MBR. When a system starts, it loads what is in the MBR to RAM. Under Linux there are two main boot loaders: • Lilo: LInux LOader. • Grub: GRand Unified Boot Loader. A boot loader allows you to select the image that you would like to boot from. A system can contain multiple images (operating systems). Design hard disk layout Install a boot manager Grub can be installed, either by editing the grub configuration file located at /boot/grub/grub.conf or /boot/grub/menu.lst and running grub-install or by invoking the grub shell. When referring to hard disks and partition grub uses the convention (hdx) for hard disks, irrespective of whether they are PATA or SATA disks, and (fdx) for floppy disks, where x refers to the disk number as seen by the BIOS. When a reference to a partition is need the conventions (hdx,n) or (fdx,n) is used, where n is the partition numbered from 0. Design hard disk layout Install a boot manager default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title Linux (2.4.18-14) root (hd0,0) kernel /vmlinuz-2.4.18-14 ro root=/dev/hda5 initrd /initrd-2.4.18-14.img Design hard disk layout Install a boot manager default image that will boot by default (the first entry is 0) timeout prompt timeout in seconds title name of the image root where the 2nd stage bootloader and kernel are e.g (hd0,0) is /dev/hda1 kernel path for the kernel starting from the previous root e.g /vmlinuz ro read-only root the filesystem root initrd path to the initial root disk Design hard disk layout Install a boot manager To install the first stage MBR loader on /dev/hda with grub- install you would run the command grubinstall (hd0) Alternatively grub can be installed through the grub shell but still requires the grub.conf/menu.lst file. The grub shell can be entered by typing grub. To install the boot loader you need to run the following commands in the shell: root (hd0,0) setup (hd0) Managing Shared Libraries Manage shared libraries A library is a set of functions that programs can use to implement their functionalities. When building (linking) a program, those libraries can be statically or dynamically linked to an executable. Static link means that the final program will contain the library function within its file (lib.a). Dynamic link means that the needed libraries are loaded into RAM when the program executes (lib.so). Managing Shared Libraries Manage shared libraries In order to find libraries, required by an application at runtime, Linux needs to know where to find them. By default Linux looks in the following trusted locations for library files: • /lib: - Used mainly by /bin programs.
Recommended publications
  • Mel Mcweeney – Curriculum Vitae Education
    Mel McWeeney – Curriculum Vitae Last updated: 13 Jul 2009 Address: 136 Teffia Park, Longford. Tel: (043) 3347697 SMS: 085 1371515 Updated CV@: http://geocities.com/mmcweeney/ Skype: [email protected] Ekiga: [email protected] eMail (Preferred Contact): [email protected] Drivers License: Irish, Full clean. Objective: To relocate to where I can work within my interests and specialities, exploit my talents and grow my career. Education, Qualifications and Training Awarding body Date Course and Qualification Russian & Slavonic Dept.Trinity College. May 2009 B1: Common European Framework of Reference for Languages(*) Dundalk Institute of Technology 1987 - 1989 National Certificate in Computing (Pass with Merit) Thomond College of Education, Limerick 1985 - 1986 Metal & Engineering Technology (Teacher training). Santa Cruz Organisation (Unix vendor) May 1996 SCO Advanced Certified Engineer, (Unix). Subjects: System Admin., TCP/IP. UUCP, Shell Programming Dell 1993 – 1998 Contemporary technology: PC, Servers, OS, others. Irish Blood Transfusion Service 2000 – 2006 GAMP (Good Automated Manufacturing Processes) VMWare (Virtualisation Vendor) Jul 2008 Employee course: Vсenter Server 3: ESX Server 3.5, vCentre 2.5 (*) http://www.coe.int/ Level B1: Can understand the main points of clear standard input on familiar matters regularly encountered in work, school, leisure, etc. Can deal with most situations likely to arise whilst travelling in an area where the language is spoken. Can produce simple connected text on topics which are familiar or of personal interest. Can describe experiences and events, dreams, hopes & ambitions and briefly give reasons and explanations for opinions and plans. Active Projects Name Nature / Goal Status Linux from Scratch Manually build a functional GNU/Linux OS from sources Preliminary build platform complete.
    [Show full text]
  • Universidad De San Carlos De Guatemala Facultad De Ingeniería Escuela De Ingeniería En Ciencias Y Sistemas
    Universidad de San Carlos de Guatemala Facultad de Ingeniería Escuela de Ingeniería en Ciencias y Sistemas HERRAMIENTA PARA AUTOMATIZAR LA CREACIÓN DE LIVE CDS PERSONALIZADOS Sergio Arnaldo Méndez Aguilar Asesorado por el Ing. Edgar René Ornelis Hoíl Guatemala, octubre de 2009 UNIVERSIDAD DE SAN CARLOS DE GUATEMALA FACULTAD DE INGENIERÍA HERRAMIENTA PARA AUTOMATIZAR LA CREACIÓN DE LIVE CDS PERSONALIZADOS TRABAJO DE GRADUACIÓN PRESENTADO A JUNTA DIRECTIVA DE LA FACULTAD DE INGENIERÍA POR: SERGIO ARNALDO MÉNDEZ AGUILAR ASESORADO POR EL ING. EDGAR RENÉ ORNELIS HOÍL AL CONFERÍRSELE EL TÍTULO DE INGENIERO EN CIENCIAS Y SISTEMAS GUATEMALA, OCTUBRE DE 2009 UNIVERSIDAD DE SAN CARLOS DE GUATEMALA FACULTAD DE INGENIERÍA NÓMINA DE JUNTA DIRECTIVA DECANO Ing. Murphy Olympo Paiz Recinos VOCAL I Inga. Glenda Patricia García Soria VOCAL II Inga. Alba Maritza Guerrero de López VOCAL III Ing. Miguel Ángel Dávila Calderón VOCAL IV Br. José Milton De León Bran VOCAL V Br. Isaac Sultán Mejía SECRETARIA Inga. Marcia Ivónne Véliz Vargas TRIBUNAL QUE PRACTICÓ EL EXAMEN GENERAL PRIVADO DECANO Ing. Murphy Olympo Paiz Recinos EXAMINADOR Ing. Victor Hugo de León Barrios EXAMINADOR Ing. Juan Alvaro Díaz Ardavín EXAMINADOR Ing. Pedro Pablo Hernández Ramírez SECRETARIA Inga. Marcia Ivónne Véliz Vargas ACTO QUE DEDICO A: Dios en primer lugar, por haberme permitido conocerlo en esta universidad y darme una nueva oportunidad, para empezar a cambiar mi vida en mi actuar y en mi forma de pensar. Mis padres y a mi hermana, que me brindaron todo el apoyo posible de acuerdo a sus capacidades, ya que ellos trabajaron muy duro para poder brindarme la oportunidad de lograr finalizar mis estudios universitarios.
    [Show full text]
  • Linux: Come E Perchх
    ÄÒÙÜ Ô ©2007 mcz 12 luglio 2008 ½º I 1. Indice II ½º Á ¾º ¿º ÈÖÞÓÒ ½ º È ÄÒÙÜ ¿ º ÔÔÖÓÓÒÑÒØÓ º ÖÒÞ ×Ó×ØÒÞÐ ÏÒÓÛ× ¾½ º ÄÒÙÜ ÕÙÐ ×ØÖÙÞÓÒ ¾ º ÄÒÙÜ ÀÖÛÖ ×ÙÔÔ ÓÖØØÓ ¾ º È Ð ÖÒÞ ØÖ ÖÓ ÓØ Ù×Ö ¿½ ½¼º ÄÒÙÜ × Ò×ØÐÐ ¿¿ ½½º ÓÑ × Ò×ØÐÐÒÓ ÔÖÓÖÑÑ ¿ ½¾º ÒÓÒ ØÖÓÚÓ ÒÐ ×ØÓ ÐÐ ×ØÖÙÞÓÒ ¿ ½¿º Ó׳ ÙÒÓ ¿ ½º ÓÑ × Ð ××ØÑ ½º ÓÑ Ð ½º Ð× Ñ ½º Ð Ñ ØÐ ¿ ½º ÐÓ ½º ÓÑ × Ò×ØÐÐ Ð ×ØÑÔÒØ ¾¼º ÓÑ ÐØØÖ¸ Ø×Ø ÐÖ III Indice ¾½º ÓÑ ÚÖ Ð ØÐÚ×ÓÒ ¿ 21.1. Televisioneanalogica . 63 21.2. Televisione digitale (terrestre o satellitare) . ....... 64 ¾¾º ÐÑØ ¾¿º Ä 23.1. Fotoritocco ............................. 67 23.2. Grafica3D.............................. 67 23.3. Disegnovettoriale-CAD . 69 23.4.Filtricoloreecalibrazionecolori . .. 69 ¾º ×ÖÚ Ð ½ 24.1.Vari.................................. 72 24.2. Navigazionedirectoriesefiles . 73 24.3. CopiaCD .............................. 74 24.4. Editaretesto............................. 74 24.5.RPM ................................. 75 ¾º ×ÑÔ Ô ´ËÐе 25.1.Montareundiscoounapenna . 77 25.2. Trovareunfilenelsistema . 79 25.3.Vedereilcontenutodiunfile . 79 25.4.Alias ................................. 80 ¾º × ÚÓÐ×× ÔÖÓÖÑÑÖ ½ ¾º ÖÓÛ×Ö¸ ÑÐ ººº ¿ ¾º ÖÛÐРгÒØÚÖÙ× Ð ÑØØÑÓ ¾º ÄÒÙÜ ½ ¿¼º ÓÑ ØÖÓÚÖ ÙØÓ ÖÖÑÒØ ¿ ¿½º Ð Ø×ØÙÐ Ô Ö Ð ×ØÓÔ ÄÒÙÜ ¿¾º ´ÃµÍÙÒØÙ¸ ÙÒ ×ØÖÙÞÓÒ ÑÓÐØÓ ÑØ ¿¿º ËÙÜ ÙÒ³ÓØØÑ ×ØÖÙÞÓÒ ÄÒÙÜ ½¼½ ¿º Á Ó Ò ÄÒÙÜ ½¼ ¿º ÃÓÒÕÙÖÓÖ¸ ÕÙ×ØÓ ½¼ ¿º ÃÓÒÕÙÖÓÖ¸ Ñ ØÒØÓ Ô Ö ½½¿ 36.1.Unaprimaocchiata . .114 36.2.ImenudiKonqueror . .115 36.3.Configurazione . .116 IV Indice 36.4.Alcuniesempidiviste . 116 36.5.Iservizidimenu(ServiceMenu) . 119 ¿º ÃÓÒÕÙÖÓÖ Ø ½¾¿ ¿º à ÙÒ ÖÖÒØ ½¾ ¿º à ÙÒ ÐÙ×ÓÒ ½¿½ ¼º ÓÒÖÓÒØÓ Ò×ØÐÐÞÓÒ ÏÒÓÛ×È ÃÍÙÒØÙ º½¼ ½¿¿ 40.1.
    [Show full text]
  • Noprianto Instalasi Pprogramrogram
    UTAMA Noprianto Instalasi PProgramrogram eiring dengan semakin banyaknya Linux digunakan, teknologi Syang memudahkan instalasi program di Linux ddii LLinuxinux pun bertambah. Kita akan membahasnya di tulisan ini. Suatu sistem yang solid adalah impian contoh, di sistem berbasis RPM, kita me- sendiri-sendiri. Selain karena alasan tidak semua pengguna komputer. Baik pengguna ngenal program yang dipaketkan sebagai ingin adanya redundansi yang tidak diper- komputer di server besar sampai perangkat fi le dengan ekstensi rpm yang dapat diin- lukan, juga karena kemungkinan terjadinya genggam. Permasalahannya adalah sistem stal. Atau, di sistem berbasis DPKG, kita inkompatibilitas versi pustaka. operasi yang telah terinstal tidak dapat mengenal program yang dipaketkan sebagai Oleh karena itu, sebuah paket barangkali memenuhi kebutuhan semua pengguna. fi le dengan ekstensi .deb. Dan masih banyak akan membutuhkan paket lainnya. Dan, pa- Baik saat pertama penggunaan ataupun di lagi. ket tersebut juga mungkin dibutuhkan oleh waktu yang akan datang. Oleh karena itu, Khususnya di Linux, masalah instalasi paket lainnya. Beberapa package manage- sistem operasi modern mengizinkan insta- program menjadi sangat istimewa karena ment modern sudah mengatasi masalah lasi aplikasi tambahan, baik yang berjalan adanya keinginan untuk mengumpulkan dependency ini, namun sempat menjadi isu sepenuhnya di user space ataupun yang me- semua pustaka di satu atau beberapa tem- yang sangat rumit di beberapa waktu yang nyentuh kernel space. pat yang disepakati bersama. Demikian lalu ataupun di beberapa sistem saat ini. Instalasi program dapat dilakukan juga dengan lokasi executable program. Di Kebutuhan akan versi pustaka yang ber- dengan berbagai cara. Di sistem operasi Linux, kita tidak disarankan untuk menggu- beda-beda juga bisa menjadi masalah besar.
    [Show full text]
  • Come Installare Software
    http://www.conoscerelinux.it Corso base di Gnu/Linux ± Installare software Prima di iniziare... Prima di partire ad installare un determinato software sotto la nostra distro Gnu/Linux, cerchiamo di vedere se vi è già suddetto software ªpacchettizzatoº per la nostra distro in modo da poterci evitare tante piccole scocciature. Ossia cerca il suddetto software attraverso il gestore di pacchetti della propria distro, come ad esempio: ✔ aptitude per Debian, Ubuntu (evoluzione di apt); ✔ swaret per Slackware; ✔ emerge per Gentoo; ✔ yum per Fedora e Red Hat; ✔ yast per Suse; Ora non staremo a descrivere ogni gestore di pacchetti, poiché vi basta una piccola ricerca sul web per imparare ad utilizzare queste utility in pochi istanti, sia con, sia senza interfacce grafiche. Come installare software Se non avete trovato il software da voi desiderato, già pacchettizzato per la vostra distro, vi toccherà installarvelo da codice sorgente, e questo varie volte può demoralizzare varie persone, soprattutto quelle che si sono avvicinate a Linux da poco. Per installare il software che vi interessa innanzitutto dovrete scaricare i file sorgenti, che generalmente sono compressi (*.zip, *.rar, *.tar, *.tar.bz2, *.tar.gz, *.ace, ecc...), scaricati i file andranno scompattati (decompressi) in una directory. Ora vi dovrete spostare nella directory dove avete scompattato il file e dare il comando ªlsº. Nel 99% dei casi all©interno della directory c©è un file che si chiama README o INSTALL (scritti in maiuscolo) i quali contengono la spiegazione di ciò che il programma fa e le istruzioni per installare il suddetto programma. Nel caso non vi siano i sopracitati file, la procedura generale da avviare è: ./configure che crea il il cosiddetto makefile il quale passa al comando make tutti i parametri e le librerie necessarie per eseguire la compilazione del programma.
    [Show full text]
  • Linuxday 2004 Openlug
    Installare programmi con Linux A cura di isazi <[email protected]> Indice: di cosa parleremo oggi ? Pacchetti o Sorgenti ? Installazione di software pacchettizzato .rpm .deb .tgz Installazione di software non pacchettizzato ./configure && make && make install Creiamo i nostri pacchetti checkinstall Pag. 2 Pacchetti o Sorgenti ? Nella maggior parte dei casi, durante l'installazione di una distribuzione linux ci viene chiesto (più o meno nello specifico) quali pacchetti software o quali tipologie di questi vogliamo installare Se successivamente vogliamo installare altri programmi non dobbiamo ripetere l'intero processo di installazione, ci basterà infatti scegliere tra una di queste due opzioni: Installare software pacchettizzato per la nostra distribuzione, fornito sui cd di installazione o reperito in altro modo (es. internet) Prendere i sorgenti del pacchetto che ci interessa e “compilarcelo” a partire da questi Pag. 3 Pacchetti o Sorgenti ? (2) La scelta sarà naturalmente dettata da pochi (e personali) fattori: La nostra esperienza con linux La disponibilità o meno di un pacchetto precompilato Nostre necessità particolari Di solito installare un pacchetto è sicuramente più semplice e porta via meno tempo; inoltre il pacchetto è sicuramente stato testato da altri e possiamo considerarlo “affidabile” Tuttavia compilare i sorgenti ci permette notevoli personalizzazioni e la possibilità di incrementare le prestazioni del software che andremo ad eseguire Pag. 4 Installazione di software pacchettizzato: RPM Cominciamo con l'installazione e la gestione di pacchetti RPM (RedHat Package Manager) I pacchetti RPM sono stati inizialmente introdotti da Red Hat, e sono oggi utilizzati oltre che su RedHat e Fedora dalle loro derivazioni e da distribuzioni terze (SuSE o Mandrake ad esempio) che hanno scelto di non sviluppare un proprio sistema di pacchettizzazione Informazioni precise su questo formato possono essere reperite su http://www.rpm.org Pag.
    [Show full text]
  • Antes De Empezar
    Antes de empezar... ● Láminas (y quizás video) en bureado.com ● Aplicaciones->Accesorios->Terminal – sudo aptitude update – sudo aptitude install gems – gems-client 10.2.205.219 ● Aplicaciones->Accesorios->Terminal – sudo aptitude install dpkg-dev devscripts Taller de empaquetamiento de software bajo el sistema APT José Miguel Parrella Romero (bureado) Debian Developer Problemática ● La mayoría del software libre crece de forma orgánica, generando un problema de acceso ● ca 1993 se empezó a atender el problema de la distribución de software libre al público ● En 1998, Debian libera APT: Advanced Packaging Tool como propuesta – Facilitar la distribución de software libre – Hacer elegante y escalable la distribución – Hoy en día, el sistema de paquetes más usado Otros sistemas de paquetes ● Derivados de APT ● Sistemas agnósticos (ipkg/opkg, Fink) postmodernos ● RPM y frontends – PackageKit contemporáneos – Conary usados en Red Hat, – Smart SuSe y derivados – ZeroInstall ● Paquetes basados – CoApp en fuentes como – Ponga su nombre Arch (pacman) y aquí... también Slackware (swaret) Objetivos funcionales ● Ubicar un pedazo de software en cualquier parte del mundo, en demanda – If you can't apt-get it, it isn't useful or doesn't exist ● Encargarse de conseguir y preparar todas las dependencias para el software ● Instalar el software para su uso inmediato ● Preconfigurar el software, opcionalmente de acuerdo a instrucciones del usuario ● Gestionar actualizaciones y remociones Componentes de APT Paquete Repo fuente ● Paquetes binarios físicos (.deb) ● Build Paquetes fuentes daemon físicos (.dsc, .tar.gz) Listas de paquetes ● Listas de paquetes (Release y Packages[.*]) ● Repositorios (HTTP, Developers FTP, SSH...) Paquetes binarios Escenarios (objetivos) ● Reconstruir un paquete de software existente con nuevas opciones y/o cambios ● Crear un paquete de software para una nueva aplicación ● Discusión sobre otros escenarios (si el tiempo lo permite) – Aplicaciones Web – Módulos de lenguajes (Perl, Python...) ● Buenos ciudadanos en Debian (y Ubuntu) Buscando las fuentes..
    [Show full text]
  • GNU MANUALINUX 6.8 This (Manual) Is Free and Is Realized Also with Collaboration of Others Passionated (THANKS !!!)
    Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation. A copy of the license is included in the section entitled "GNU Free Documentation License". Copyright (c) 2001-2008 Cristiano Macaluso (aka Panther) E' garantito il permesso di copiare, distribuire e/o modificare questo documento seguendo i termini della Licenza per Documentazione Libera GNU, Versione 1.2 o ogni versione successiva pubblicata dalla Free Software Foundation. Una copia della licenza è acclusa in fondo al documento nella sezione intitolata "GNU Free Documentation License". GNU MANUALINUX 6.8 This (Manual) is free and is realized also with collaboration of others passionated (THANKS !!!). Last update on October 6 2008 version: 6.8 Manualinux Homepage: http://www.manualinux.com http://www.manualinux.it http://www.manualinux.eu http://www.manualinux.in http://www.manualinux.cn http://www.manualinux.org http://www.manualinux.net http://www.manualinux.tk DO YOU WANT TO MODIFY OR INSERT OTHER ARTICLES ? WRITE ME ! EMAIL: [email protected] (Cristiano Macaluso). NEWS OF THE VERSION 6.8 Modified 38b)INSTALL SLAX ON HARD-DISK AND ON USB STICK Modified 3c)CREATE AND BURN CD AND DVD MENU' Page a)COMMANDS 2 b)UTILITY 2 c)PROGRAMS 3 d)KERNEL 4 e)NETWORKING 4 f)OTHER 5 GNU Free Documentation License 151 DO YOU WANT ADD / MODIFY OTHER ARGUMENTS ??? WRITE ME !!! 1 COMMANDS Page 1a)COMMON COMMANDS TO MOVE FIRST STEPS ON LINUX 5 2a)DIFFERENT COMMANDS
    [Show full text]
  • Twórca Data Pierwszego Wydania Poprzednik Wersja Stabilna Cena W
    Data Wersja Cena w Twórca pierwszego Poprzednik Preferowana licencja² Przeznaczenie stabilna USD wydania Arch stacje robocze, Judd Vinet 11 marca 2002 CRUX 2009.08 darmowy GPL Linux uŜytkownicy domowi Robert Red Hat stacje robocze, Aurox listopad 2002 12.0 darmowy GPL Główczyński Linux uŜytkownicy domowi Debian 5.0 serwery, stacje robocze, Debian sierpień 1993 SLS darmowy kaŜda zgodna z WDdWO Project (lenny ) uŜytkownicy domowi Red Hat serwery, stacje robocze, Fedora Fedora 5 listopada 2003 12 darmowy GPL Linux uŜytkownicy domowi Klaus stacje robocze, Knoppix 19 stycznia 2003 Debian 5.3.1 darmowy GPL Knopper uŜytkownicy domowi Canonical bazujący 10.04 serwery, stacje robocze, Ubuntu październik 2004 darmowy GPL Ltd naDebianie LTS uŜytkownicy domowi Gentoo serwery, stacje robocze, Gentoo Foundation, marzec 2002 Enoch 10.1 darmowy GPL uŜytkownicy domowi Inc GPL, Free stacje robocze, Linspire Linspire Inc. marzec 2002 Lindows 6.0 płatny software, Oprogramowanie uŜytkownicy domowi własnościowe darmowy / Mandriva Red Hat płatny – stacje robocze, Mandriva lipiec 1998 2010.0 GPL Linux Linux wersja uŜytkownicy domowi rozszerzona Warren bazuje darmowy serwery, stacje robocze, MEPIS wrzesień 2003 7.0 GPL Woodford naDebianie (download) uŜytkownicy domowi PLD Dewe loperzy Red Hat 2.0 serwery, stacje robocze, 1998 darmowy dowolna Linux PLD Linux Linux (AC ) uŜytkownicy domowi Slackware Patrick darmowy serwery, stacje robocze, lipiec 1993 SLS 12.1 GPL Linux Volkerding (download) uŜytkownicy domowi serwery, stacje robocze, openSUSE Novell marzec 1994
    [Show full text]
  • Linux Record Audio from Console / Terminal with Rec, Arecord and Ffmpeg
    Walking in Light with Christ - Faith, Computing, Diary Articles & tips and tricks on GNU/Linux, FreeBSD, Windows, mobile phone articles, religious related texts http://www.pc-freak.net/blog Linux record audio from console / terminal with rec, arecord and ffmpeg Author : admin Recording from microphone input on Linux is possible, through multiple programs. 1. Recording microphone input using SoX's rec The classical old-school way is through a little proggie called sox. Back in the day I remember we recorded with sox with a friend from the school years necroleak - mirror of his website is on kenamick.pc- freak.net, trying to make save vox for one of his Tracked Songs. The experiments was not very succesful as both the PC microphone was low quality one, as well as the the state of recording microphone sound streams on Linux was terrible, but at least I learned about sox. sox is not so popular and mainstream as it used to be back in the day but for anyone willing to investigate into the roots of GNU / Linux sound capturing make sure you have installed sox, alsa-utils and lame package. The package is available across virtually all main stream Linux distributions, depending on the distro to INSTALL sox do: apt-get install --yes sox alsa-utils lame .... (On Debian, Ubuntu, Arch, Xubuntu ... ) yum -y install sox alsa-utils lame .... (on Fedora, CentOS, RHEL ...) slapt-get install sox ; swaret install sox alsa-utils lame 1 / 3 Walking in Light with Christ - Faith, Computing, Diary Articles & tips and tricks on GNU/Linux, FreeBSD, Windows, mobile phone articles, religious related texts http://www.pc-freak.net/blog ....
    [Show full text]
  • Vademecum Linux 3.0 Beta
    LINUX VADEMECUM Versione 3.0 beta CHE COSA CI TROVO DENTRO? LE RISPOSTE a COSA VUOI FARE OGGI? ovvero come cambiare sistema operativo DOVE VUOI ANDARE OGGI? ovvero come procurarsi un sistema operativo Linux QUALE VUOI OGGI? ovvero come scegliere una distribuzione Linux COSA VUOI CREARE OGGI? ovvero come scegliere i programmi Linux COME VUOI USARLO OGGI? ovvero come funziona il vostro sistema operativo Linux CHI PUO' AIUTARMI OGGI? ovvero dove trovare aiuto e supporto CHE COSA VUOL DIRE QUESTO OGGI? ovvero un breve glossario con i termini Linux più comuni Licenza: CC Attribuzione - Non commerciale - Condividi allo stesso modo 3.0 Unported Vademecum Linux 3.0 beta COSA VUOI FARE OGGI? ovvero come cambiare sistema operativo olti di voi hanno imparato ad usare un computer in un certo modo, sono abituati a trovare gli strumenti che usate Mquotidianamente sempre allo stesso posto. Ora vi siete decisi. Volete cambiare sistema operativo. Per tanti motivi. Questi possono essere l'esigenza di avere maggiore libertà, maggiore privacy, maggiore sicurezza, maggiore stabilità, maggiore qualità degli applicativi, minor costo. Una buona notizia, Linux si basa su standard, standard che sono alla base del sistema operativo che voi state utilizzando adesso. Alcune parole chiave sono diverse, alcune procedure sono diverse, ma i concetti sottostanti sono uguali. Tenete presente che Linux non è un INFO: Linux, con la funzione multiboot, può sostituto o un clone di altri sistemi convivere nello stesso computer insieme altri sistemi operativi, anche nello stesso disco operativi, ha una sua personalità e rigido, ma in partizioni diverse. caratteristiche specifiche che lo differenziano.
    [Show full text]
  • Snap – System Snapshotter
    Snap – System Snapshotter Masters Project Paper Mohammed Morsi Syracuse University, 1 / 2008 Table of Contents I. System Overview....................................................................................................................................3 1 Project Description.............................................................................................................................3 2. Background.......................................................................................................................................4 3. Target Users.......................................................................................................................................5 4. Requirements.....................................................................................................................................7 II. System Layout.......................................................................................................................................8 1. Primary Interface...............................................................................................................................8 2. Exceptions and Errors.......................................................................................................................9 3. Configuration System......................................................................................................................10 4. Callback system...............................................................................................................................12
    [Show full text]