DOCSLIB.ORG

Basic Operations

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Basic operations Action Arch Red Hat/Fedora Debian/Ubuntu SLES/openSUSE Gentoo zypper install or emerge [- Install a package(s) by name pacman -S dnf install apt install zypper in a] zypper remove or Remove a package(s) by name pacman -Rs dnf remove apt remove emerge -vc zypper rm Search for package(s) by searching the expression in name, description, short zypper search or description. What exact fields are being pacman -Ss dnf search apt search emerge -S zypper se [-s] searched by default varies in each tool. Mostly options bring tools on par. Upgrade Packages - Install packages which have apt update and zypper update or emerge - pacman -Syu dnf upgrade an older version already installed then apt upgrade zypper up uDN @world Upgrade Packages - Another form of the update command, which can perform more complex updates -- like distribution upgrades. When the apt update and dnf distro- emerge - usual update command will omit package pacman -Syu then apt dist- zypper dup sync uDN @world updates, which include changes in upgrade dependencies, this command can perform those updates. Clean up all local caches. Options might limit pacman -Sc dnf clean apt autoclean eclean what is actually cleaned. autoclean removes or pacman - zypper clean all or apt clean distfiles only unneeded, obsolete information. Scc pacman - Remove dependencies that are no longer Qdtq | dnf emerge -- needed, because e.g. the package which apt autoremove zypper rm -u pacman -Rs autoremove depclean needed the dependencies was removed. - 1 pacman -Qmq dnf Remove packages no longer included in any aptitude purge | pacman - repoquery -- repositories. '~o' Rs - extras pacman -D Mark a package previously installed as a dnf mark apt-mark emerge -- -- dependency as explicitly required. install manual select asexplicit dnf install Install package(s) as dependency / without pacman -S and then dnf apt-mark auto emerge -1 marking as explicitly required. --asdeps mark remove apt install -- download-only Only downloads the given package(s) without (into the package zypper -- emerge -- pacman -Sw dnf download unpacking or installing them cache) or apt download-only fetchonly download (bypass the package cache) Start a shell to enter multiple commands in one apt-config zypper shell session shell read read see Show a log of actions taken by the software read /var/log/ /var/log/pa dnf history /var/log/zypp/hi /var/log/p management. dpkg.log cman.log story ortage Get a dump of the whole system information - Prints, Saves or similar the current state of the see see package management system. Preferred output apt-cache emerge -- /var/lib/pa /var/lib/rpm is text or XML. (Note: Why either-or here? No stats info cman/local /Packages tool offers the option to choose the output format.) apt install e-mail delivery of package changes apt- listchanges 2 Querying specific packages Action Arch Red Hat/Fedora Debian/Ubuntu SLES/openSUSE Gentoo Show all or most information about a pacman - apt show or emerge -S, package. The tools' verbosity for the Si or zypper info or dnf list or dnf info apt-cache emerge -pv or default command vary. But with options, pacman - zypper if policy eix the tools are on par with each other. Qi Display local package information: Name, pacman - rpm -qi / dnf info dpkg -s or zypper info or rpm emerge -pv or version, description, etc. Qi installed aptitude show -qi emerge -S emerge -pv apt-cache Display remote package information: pacman - and emerge -S dnf info show or zypper info Name, version, description, etc. Si or equery aptitude show meta pacman - equery files Display files provided by local package rpm -ql dpkg -L rpm -Ql Ql or qlist dnf repoquery -l or pacman - Display files provided by a remote package repoquery -l (from apt-file list pfl Fl package yum-utils) rpm -qf (installed only) or equery pacman - dnf provides (everything) dpkg -S or Query the package which provides FILE zypper search -f belongs or Qo or repoquery -f (from dlocate qfile package yum-utils) pacman - List the files that the package holds. Again, Ql or equery files this functionality can be mimicked by dnf repoquery -l dpkg-query -L rpm -ql pacman - or qlist other more complex commands. Fl Displays packages which provide the given pacman -F dnf provides apt-file zypper what- equery exp. aka reverse provides. Mainly a search provides or zypper belongs (only shortcut to search a specific field. Other wp installed packages) 3 tools might offer this functionality through or pfl the search command. Search all packages to find the one which equery apt-file holds the specified file. auto-apt is using pacman -F dnf provides zypper search -f belongs or search this functionality. qfile pacman - apt-get rpm -q -- equery Show the changelog of a package rpm -q --changelog Qc changelog changelog changes -f 4 Querying package lists Action Arch Red Hat/Fedora Debian/Ubuntu SLES/openSUSE Gentoo Search for package(s) by searching the expression in name, description, short description. pacman zypper search or What exact fields are being dnf search apt search emerge -S or eix -Ss zypper se -s searched by default varies in each tool. Mostly options bring tools on par. Lists packages which have an update available. Note: Some dnf list apt-get upgrade zypper list-updates pacman provide special commands to limit updates or dnf (press n to only see the or zypper patch-check emerge -uDNp @world -Qu the output to certain installation check-update list) (just for patches) sources, others use options. Display a list of all packages in all installation sources that are apt-cache handled by the packages dumpavail or apt- pacman dnf list portageq management. Some tools provide cache dump (Cache zypper packages -Sl available all_best_visible / options or additional commands only) or apt-cache to limit the output to a specific pkgnames installation source. Generates a list of installed pacman dnf list dpkg --list | zypper search -- qlist -IC packages -Q installed grep ^i installed-only List packages that are installed pacman zypper se -si | grep but are not available in any dnf list extras deborphan eix-test-obsolete -Qm 'System Packages' installation source (anymore). List packages that were recently dnf list recent aptitude search eix-diff 5 added to one of the installation '~N' or aptitude sources, i.e. which are new to it. forget-new List installed local packages along pacman zypper search -s or rpm -qa dpkg -l qlist -ICv with version -Q rpm -qa aptitude search Search locally installed package pacman rpm -qa '~i(~n $name|~d eix -S -I for names or descriptions -Qs '*<str>*' $description)' List packages not required by any pacman dnf leaves deborphan -anp1 emerge -pc other package -Qt emerge -pvO List packages installed explicitly pacman dnf history apt-mark @selected or eix -- (not as dependencies) -Qe userinstalled showmanual selected List packages installed pacman apt-mark showauto automatically (as dependencies)}} -Qd 6 Querying package dependencies Action Arch Red Hat/Fedora Debian/Ubuntu SLES/openSUSE Gentoo dnf repoquery --alldeps Display packages which require X apt-cache rdepends or pacman - --whatrequires or zypper search emerge - to be installed, aka show reverse aptitude search Sii repoquery -- --requires pvc dependencies. ~D$pattern whatrequires Display packages which conflict with given expression (often dnf repoquery -- aptitude search package). Search can be used as conflicts '~C$pattern' well to mimic this function. pacman - List all packages which are required Si or dnf repoquery -- apt-cache depends or zypper info for the given package, aka show emerge -ep pacman - requires or repoquery -R apt-cache show --requires dependencies. Qi equery List what the current package zypper info dnf provides dpkg -s or aptitude show files or provides --provides qlist aptitude search List all packages that require a dnf repoquery --alldeps ~D{depends,recommends, zypper search equery particular package --whatrequires suggests}:$pattern or --requires depends -a aptitude why Display all packages that the dnf list obsoletes apt-cache show specified packages obsoletes. Generates an output suitable for processing with dotty for the given apt-cache dotty package(s). 7 Installation sources management Action Arch Red Hat/Fedora Debian/Ubuntu SLES/openSUSE Gentoo edit edit edit edit /etc/zypp/ Installation sources layman or eselect /etc/pacman.c /etc/yum.repos.d /etc/apt/sources. repos.d/$ management repository onf /${REPO}.repo list {REPO}.repo Add an installation source to the system. Some tools provide additional commands for certain sources, others allow all types of source URI for the add edit /etc/ zypper command. Again others, like apt /etc/pacman.c yum.repos.d/ apt-cdrom add layman or overlays service-add and dnf force editing a sources onf *.repo list. apt-cdrom is a special command, which offers special options design for CDs/DVDs as source. Refresh the information about pacman -Sy dnf clean zypper the specified installation (always upgrade expire-cache and emerge --sync or apt-get update refresh or source(s) or all installation the whole system then dnf check- layman -S zypper ref sources. afterwards) update Prints a list of all installation cat cat zypper layman -l or eselect sources including important /etc/pacman.d /etc/yum.repos.d apt-cache policy service-list repository list information like URI, alias etc. /mirrorlist /* List all packages from a certain paclist eix --in-overlay repo <repo> Disable an installation source dnf -- emerge for an operation disablerepo= package::repo-to-use Download packages
Recommended publications
  • Debian GNU/Linux 4.0 (“Etch”) (Mips )

    Debian GNU/Linux 4.0 (“Etch”) (Mips )

    Debian GNU/Linux 4.0 (“etch”) JJー スノー( (Mips 用) Josip Rodin, Bob Hilliard, Adam Di Carlo, Anne Bezemer, Rob Bradford, Frans Pop (現在.AS&*), Andreas Barth (現在.AS&*), Javier Fernández-Sanguino Peña (現在.AS&*), Steve Langasek (現在.AS&*) <[email protected]> $Id: release-notes.en.sgml,v 1.312 2007-08-16 22:24:38 jseidel Exp $ i 目目目 hhh 1 //はじじじめAA+++ 1 1.1 この£書+¯するバグR報告する ...........................1 1.2 アップグレー)についての報告をする .........................2 1.3 この£書.ソース .....................................2 2 Debian GNU/Linux 4.0 ...最最最新新新情ss報報報 3 2.1 Mips +¯する最新情報 .................................4 2.2 ディストリビューション.最新情報 ..........................4 2.2.1 パッケージ管理 ..................................5 2.2.2 debian-volatile がGwサービス+ .......................6 2.3 システム.改, ......................................6 2.4 カー-K¯c.®要*¼f点 ..............................7 2.4.1 カーネルパッケージングにおける¼f ....................8 2.4.2 新しい initrd 生成Fーティリティ .......................8 2.4.3 #¿* /dev 管理(/ードウェア検õ .....................8 3 イイインSンスススト((ーーーKKルシシシススステ&&@@@ 11 3.1 インストールシステム.最新情報 ........................... 11 3.1.1 ®要*¼f点 ................................... 11 3.1.2 r#インストーK ................................ 13 3.2 ®気コンテスト ...................................... 14 4 )))MMM...JJJJJJーーースススかかからIIアアアッ##77プグググレLLーーー)))すすするKK 15 4.1 アップグレー).準& .................................. 15 4.1.1 あらゆる'ータD設¡s報Rバックアップする ............... 15 目 h ii 4.1.2 _M+Fーザ+通知する ............................ 16 4.1.3 復!.準& .................................... 16 4.1.4 アップグレー)用.!Q*環@.準& .................... 17 4.1.5 2.2 系カー-K/サポー(されなくなりました ................ 17 4.2 システム.x態Rチェックする ............................. 17 4.2.1 パッケージマネージャU.? ?.アクションRGx ........... 17 4.2.2 APT . pin 機能R\Iにする .......................... 18 4.2.3 パッケージ.x態Rチェックする ....................... 18 4.2.4 "Gw*ソース(バックポー( ........................ 19 4.3 パッケージ.>ークR±ù[')す .........................
  • Embedded Linux Systems with the Yocto Project™

    Embedded Linux Systems with the Yocto Project™

    OPEN SOURCE SOFTWARE DEVELOPMENT SERIES Embedded Linux Systems with the Yocto Project" FREE SAMPLE CHAPTER SHARE WITH OTHERS �f, � � � � Embedded Linux Systems with the Yocto ProjectTM This page intentionally left blank Embedded Linux Systems with the Yocto ProjectTM Rudolf J. Streif Boston • Columbus • Indianapolis • New York • San Francisco • Amsterdam • Cape Town Dubai • London • Madrid • Milan • Munich • Paris • Montreal • Toronto • Delhi • Mexico City São Paulo • Sidney • Hong Kong • Seoul • Singapore • Taipei • Tokyo Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. The author and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. For information about buying this title in bulk quantities, or for special sales opportunities (which may include electronic versions; custom cover designs; and content particular to your business, training goals, marketing focus, or branding interests), please contact our corporate sales depart- ment at [email protected] or (800) 382-3419. For government sales inquiries, please contact [email protected]. For questions about sales outside the U.S., please contact [email protected]. Visit us on the Web: informit.com Cataloging-in-Publication Data is on file with the Library of Congress.
  • Lmod Or How to Protect Your Sanity from Dependency Hell

    Lmod Or How to Protect Your Sanity from Dependency Hell

    Lmod or how to protect your sanity from dependency hell Steffen Müthing Interdisciplinary Center for Scientific Computing Heidelberg University Dune User Meeting Aachen September 26, 2013 1 Steffen Müthing | Lmod or how to protect your sanity from dependency hell ⇒ Have to keep around multiple versions of MPI, BLAS, ParMetis, ALUGrid, UGGrid, . The Issue • DUNE has a number of non-packaged dependencies • Some of those contain libraries that are bound to a compiler / MPI version • You have to support multiple compilers / MPIs • Library developer (we try to be good about this...) • Clusters with different compiler / MPI combinations • Easily switch between release / debug version of MPI (only with dynamic linking) • Use GCC in general, but switch to clang during the “fix compilation errors” stage 2 Steffen Müthing | Lmod or how to protect your sanity from dependency hell The Issue • DUNE has a number of non-packaged dependencies • Some of those contain libraries that are bound to a compiler / MPI version • You have to support multiple compilers / MPIs • Library developer (we try to be good about this...) • Clusters with different compiler / MPI combinations • Easily switch between release / debug version of MPI (only with dynamic linking) • Use GCC in general, but switch to clang during the “fix compilation errors” stage ⇒ Have to keep around multiple versions of MPI, BLAS, ParMetis, ALUGrid, UGGrid, . 2 Steffen Müthing | Lmod or how to protect your sanity from dependency hell Problems • Do I already have ALUGrid for MPICH? • If yes, where on earth did I put it? • Did I really build it with the correct dependencies? • Why does my build fail? Do all the libraries in my nice --with= actually work together? 3 Steffen Müthing | Lmod or how to protect your sanity from dependency hell • Look around for something that’s already there • Distribution package managers (APT, rpm, Portage, MacPorts, homebrew,.
  • Windows Subsystem for Linux

    Windows Subsystem for Linux

    LINUX 101 ... FOR .NET DEVS Oliver Sturm • @olivers • [email protected] OLIVER STURM Training Director at DevExpress Consultant, trainer, author, software architect and developer for over 25 years Contact: [email protected] Linux 101 2 / 37 AGENDA That Linux Thing Getting Started with Linux Shells, Command Lines and Commands File Systems and Permissions Users and Processes Editing and Configuring Packages Creating a .NET Core App Setting Up a Runtime Environment Linux 101 3 / 37 ON DAY 1... From: Linus Benedict Torvalds Date: August 25 1991 Subject: What would you like to see most in minix? Hello everybody out there using minix - I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones. PS. It is NOT protable (uses 386 task switching etc), and it probably never will support anything other than AT-harddisks, as that's all I have :-(. Full thread: http://osturm.me/torvalds-linux-announcement Linux 101 4 / 37 ON DAY 1... From: Linus Benedict Torvalds Date: August 25 1991 Subject: What would you like to see most in minix? Hello everybody out there using minix - Y THE AY I'm Bdoin g a ( Wfree) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones. Linus doesn't mention it, but his new OS was going to be PS. called It Freaxis NO Tat p thisrota bpoint.le (uses 386 task switching etc), and it probably never will support anything other than AT-harddisks, as that's all I have :-(.
  • With Yocto/Openembedded

    With Yocto/Openembedded

    PORTING NEW CODE TO RISC-V WITH YOCTO/OPENEMBEDDED Martin Maas ([email protected]) 1st RISC-V Workshop, January 15, 2015 Monterey, CA WHY WE NEED A LINUX DISTRIBUTION • To build an application for RISC-V, you need to: – Download and build the RISC-V toolchain + Linux – Download, patch and build application + dependencies – Create an image and run it in QEMU or on hardware • Problems with this approach: – Error-prone: Easy to corrupt FS or get a step wrong – Reproducibility: Others can’t easily reuse your work – Rigidity: If a dependency changes, need to do it all over • We need a Linux distribution! – Automatic build process with dependency tracking – Ability to distribute binary packages and SDKs 2 RISCV-POKY: A PORT OF THE YOCTO PROJECT • We ported the Yocto Project – Official Linux Foundation Workgroup, supported by a large number of industry partners – Part I: Collection of hundreds of recipes (scripts that describe how to build packages for different platforms), shared with OpenEmbedded project – Part II: Bitbake, a parallel build system that takes recipes and fetches, patches, cross-compiles and produces packages (RPM/DEB), images, SDKs, etc. • Focus on build process and customizability 3 GETTING STARTED WITH RISCV-POKY • Let’s build a full Linux system including the GCC toolchain, Linux, QEMU + a large set of packages (including bash, ssh, python, perl, apt, wget,…) • Step I: Clone riscv-poky: git clone [email protected]:ucb-bar/riscv-poky.git • Step II: Set up the build system: source oe-init-build-env • Step III: Build an image (may
  • ROOT Package Management: “Lazy Install” Approach

    ROOT Package Management: “Lazy Install” Approach

    ROOT package management: “lazy install” approach Oksana Shadura ROOT Monday meeting Outline ● How we can improve artifact management (“lazy-install”) system for ROOT ● How to organise dependency management for ROOT ● Improvements to ROOT CMake build system ● Use cases for installing artifacts in the same ROOT session Goals ● Familiarize ROOT team with our planned work ● Explain key misunderstandings ● Give a technical overview of root-get ● Explain how root-get and cmake can work in synergy Non Goals We are not planning to replace CMake No change to the default build system of ROOT No duplication of functionality We are planning to “fill empty holes” for CMake General overview Manifest - why we need it? ● Easy to write ● Easy to parse, while CMakeLists.txt is impossible to parse ● Collect information from ROOT’s dependencies + from “builtin dependencies” + OS dependencies + external packages to be plugged in ROOT (to be resolved after using DAG) ● It can be easily exported back as a CMakeLists.txt ● It can have extra data elements [not only what is in CMakeLists.txt, but store extra info] ○ Dependencies description (github links, semantic versioning) ■ url: "ssh://[email protected]/Greeter.git", ■ versions: Version(1,0,0)..<Version(2,0,0) Manifest is a “dump” of status of build system (BS), where root-get is just a helper for BS Manifest - Sample Usage scenarios and benefits of manifest files: LLVM/Clang LLVM use CMake as a LLVMBuild utility that organize LLVM in a hierarchy of manifest files of components to be used by build system llvm-build, that is responsible for loading, verifying, and manipulating the project's component data.
  • Praise for the Official Ubuntu Book

    Praise for the Official Ubuntu Book

    Praise for The Official Ubuntu Book “The Official Ubuntu Book is a great way to get you started with Ubuntu, giving you enough information to be productive without overloading you.” —John Stevenson, DZone Book Reviewer “OUB is one of the best books I’ve seen for beginners.” —Bill Blinn, TechByter Worldwide “This book is the perfect companion for users new to Linux and Ubuntu. It covers the basics in a concise and well-organized manner. General use is covered separately from troubleshooting and error-handling, making the book well-suited both for the beginner as well as the user that needs extended help.” —Thomas Petrucha, Austria Ubuntu User Group “I have recommended this book to several users who I instruct regularly on the use of Ubuntu. All of them have been satisfied with their purchase and have even been able to use it to help them in their journey along the way.” —Chris Crisafulli, Ubuntu LoCo Council, Florida Local Community Team “This text demystifies a very powerful Linux operating system . in just a few weeks of having it, I’ve used it as a quick reference a half dozen times, which saved me the time I would have spent scouring the Ubuntu forums online.” —Darren Frey, Member, Houston Local User Group This page intentionally left blank The Official Ubuntu Book Sixth Edition This page intentionally left blank The Official Ubuntu Book Sixth Edition Benjamin Mako Hill Matthew Helmke Amber Graner Corey Burger With Jonathan Jesse, Kyle Rankin, and Jono Bacon Upper Saddle River, NJ • Boston • Indianapolis • San Francisco New York • Toronto • Montreal • London • Munich • Paris • Madrid Capetown • Sydney • Tokyo • Singapore • Mexico City Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks.
  • Ubuntu Server Guide Basic Installation Preparing to Install

    Ubuntu Server Guide Basic Installation Preparing to Install

    Ubuntu Server Guide Welcome to the Ubuntu Server Guide! This site includes information on using Ubuntu Server for the latest LTS release, Ubuntu 20.04 LTS (Focal Fossa). For an offline version as well as versions for previous releases see below. Improving the Documentation If you find any errors or have suggestions for improvements to pages, please use the link at thebottomof each topic titled: “Help improve this document in the forum.” This link will take you to the Server Discourse forum for the specific page you are viewing. There you can share your comments or let us know aboutbugs with any page. PDFs and Previous Releases Below are links to the previous Ubuntu Server release server guides as well as an offline copy of the current version of this site: Ubuntu 20.04 LTS (Focal Fossa): PDF Ubuntu 18.04 LTS (Bionic Beaver): Web and PDF Ubuntu 16.04 LTS (Xenial Xerus): Web and PDF Support There are a couple of different ways that the Ubuntu Server edition is supported: commercial support and community support. The main commercial support (and development funding) is available from Canonical, Ltd. They supply reasonably- priced support contracts on a per desktop or per-server basis. For more information see the Ubuntu Advantage page. Community support is also provided by dedicated individuals and companies that wish to make Ubuntu the best distribution possible. Support is provided through multiple mailing lists, IRC channels, forums, blogs, wikis, etc. The large amount of information available can be overwhelming, but a good search engine query can usually provide an answer to your questions.
  • 07 07 Unixintropart2 Lucio Week 3

    07 07 Unixintropart2 Lucio Week 3

    Unix Basics Command line tools Daniel Lucio Overview • Where to use it? • Command syntax • What are commands? • Where to get help? • Standard streams(stdin, stdout, stderr) • Pipelines (Power of combining commands) • Redirection • More Information Introduction to Unix Where to use it? • Login to a Unix system like ’kraken’ or any other NICS/ UT/XSEDE resource. • Download and boot from a Linux LiveCD either from a CD/DVD or USB drive. • http://www.puppylinux.com/ • http://www.knopper.net/knoppix/index-en.html • http://www.ubuntu.com/ Introduction to Unix Where to use it? • Install Cygwin: a collection of tools which provide a Linux look and feel environment for Windows. • http://cygwin.com/index.html • https://newton.utk.edu/bin/view/Main/Workshop0InstallingCygwin • Online terminal emulator • http://bellard.org/jslinux/ • http://cb.vu/ • http://simpleshell.com/ Introduction to Unix Command syntax $ command [<options>] [<file> | <argument> ...] Example: cp [-R [-H | -L | -P]] [-fi | -n] [-apvX] source_file target_file Introduction to Unix What are commands? • An executable program (date) • A command built into the shell itself (cd) • A shell program/function • An alias Introduction to Unix Bash commands (Linux) alias! crontab! false! if! mknod! ram! strace! unshar! apropos! csplit! fdformat! ifconfig! more! rcp! su! until! apt-get! cut! fdisk! ifdown! mount! read! sudo! uptime! aptitude! date! fg! ifup! mtools! readarray! sum! useradd! aspell! dc! fgrep! import! mtr! readonly! suspend! userdel! awk! dd! file! install! mv! reboot! symlink!
  • Working with Ubuntu Linux

    Working with Ubuntu Linux

    Working with Ubuntu Linux Track 2 Workshop June 2010 Pago Pago, American Samoa Assumptions You are comfortable with the following: • Core Linux concepts - Shells - Permissions - Graphical user interface (GUI) vs. command line interface (CLI) • Working on the Linux command line • Editing files in Linux (using vi, nano or other text editors) • Basics of networking Is this correct? Goal Present the “Ubuntu philosophy” and differences from other Linux distributions. Including: • Naming conventions • Release conventions (Server, Desktop and LTS) • Other flavors • The Debian way • Packaging system (how software is installed) • Meta-packages • Keeping up-to-date • Stopping and starting services Ubuntu Timeline The Debian Way Ubuntu is built from Debian repositories and uses the Debian package management system. • Debian is a very cautious and strict Linux distribution: • Minimal new versions • Extremely well-tested • No closed source software • Beta version of Debian as stable as release quality for most Linux distributions. • New versions are not released until they are ready. • Latest versions of software often not available in main branch as they are not considered stable or safe enough. • There are pluses and minuses to this approach. The Ubuntu Take on the Debian Way Potentially heretical slide … • Use the Debian software repository concept to classify software. • Use the Debian package management system. • Be more open – Ubuntu allows closed source software and drivers. • Ubuntu pushes releases out fast, but supports releases for 2 to 5 years (Unlike Fedora Core’s 18 months). • Ubuntu aiming at both the desktop and server markets. • The “Ubuntu Project” is supported by Mark Shuttleworth. • Make maintaining a current system very easy to completely automatic (much like Windows).
  • MX-19.2 Users Manual

    MX-19.2 Users Manual

    MX-19.2 Users Manual v. 20200801 manual AT mxlinux DOT org Ctrl-F = Search this Manual Ctrl+Home = Return to top Table of Contents 1 Introduction...................................................................................................................................4 1.1 About MX Linux................................................................................................................4 1.2 About this Manual..............................................................................................................4 1.3 System requirements..........................................................................................................5 1.4 Support and EOL................................................................................................................6 1.5 Bugs, issues and requests...................................................................................................6 1.6 Migration............................................................................................................................7 1.7 Our positions......................................................................................................................8 1.8 Notes for Translators.............................................................................................................8 2 Installation...................................................................................................................................10 2.1 Introduction......................................................................................................................10
  • Meeting the Yocto Project

    Meeting the Yocto Project

    Meeting the Yocto Project In this chapter, we will be introduced to the Yocto Project. The main concepts of the project, which are constantly used throughout the book, are discussed here. We will discuss the Yocto Project history, OpenEmbedded, Poky, BitBake, and Metadata in brief, so fasten your seat belt and welcome aboard! What is the Yocto Project? The Yocto Project is a "The Yocto Project provides open source, high-quality infrastructure and tools to help developers create their own custom Linux distributions for any hardware architecture, across multiple market segments. The Yocto Project is intended to provide a helpful starting point for developers." The Yocto Project is an open source collaboration project that provides templates, tools, and methods to help us create custom Linux-based systems for embedded products regardless of the hardware architecture. Being managed by a Linux Foundation fellow, the project remains independent of its member organizations that participate in various ways and provide resources to the project. It was founded in 2010 as a collaboration of many hardware manufacturers, open source operating systems, vendors, and electronics companies in an effort to reduce their work duplication, providing resources and information catering to both new and experienced users. Among these resources is OpenEmbedded-Core, the core system component, provided by the OpenEmbedded project. Meeting the Yocto Project The Yocto Project is, therefore, a community open source project that aggregates several companies, communities, projects, and tools, gathering people with the same purpose to build a Linux-based embedded product; all these components are in the same boat, being driven by its community needs to work together.