DOCSLIB.ORG

Package Management - Openmoko

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Package Management - Openmoko Package management - Openmoko http://wiki.openmoko.org/wiki/Package_management Wiki Docs Planet Projects Lists Package management From Openmoko NB: Current (2008-04-04+) builds of Openmoko now come with the syntax compatible Opkg tool, not ipkg. TODO: Integrate useful content into Opkg as a usage section. (See: To-Do List) The practical way to install software on Openmoko is with the Ipkg package manager (http://handhelds.org/moin/moin.cgi/Ipkg) , possibly via the graphical Application Manager. Naturally, you need to have obtained an Openmoko system by other means initially. In the shell, "opkg update" will update the list of available packages, "opkg upgrade" will download and install all packages that have a newer version available and "ipkg install new-app" will download and install "new-app". Have a look at Users Repositories to get addresses of alternative software repositories, e.g. ScaredyCat's ipkg repository. Contents 1 History 2 Installing Packages to the Memory Card 2.1 Ext2 Formatted Memory Card 2.2 Entry in opkg.conf File 2.3 Installing Packages on the Card 1 of 4 10/16/2008 04:17 PM Package management - Openmoko http://wiki.openmoko.org/wiki/Package_management 2.4 Linking/Using Packages on the Card 2.4.1 1: Ipkg Utils and ipkg-link 2.4.2 2: Adding the card PATH and LIB directories to your path History Ipkg re-implements for embedded systems the functionality of Debian tools dpkg, apt, and apt-get. For example, it uses much less disk space for the package metadata. Installing Packages to the Memory Card You can use ipkg to install packages to a folder on the memory card. To do this you'll need the following: Ext2 Formatted Memory Card By default, the memory card comes formated with VFAT (Windows Format). You need to re-format the card with EXT2. You will not be able to view the files on the card using a windows system after this. To check if your card is using vfat or ext, run the 'mount' command, and look for: /dev/mmcblk0p1 on /media/card. On the NEO, run the following: This will erase everything on your memory card umount /media/card fdisk /dev/mmcblk0 t 83 w mke2fs /dev/mmcblk0p1 mount /media/card Entry in opkg.conf File In your /etc/opkg.conf file, after "dest root /" add a new line: dest card /media/card/opkg Create /media/card/opkg folder 2 of 4 10/16/2008 04:17 PM Package management - Openmoko http://wiki.openmoko.org/wiki/Package_management mkdir /media/card/opkg Installing Packages on the Card When installing a package, use the -d option to have the package installed into the "card" destination: opkg install -d card python-core This will put all files (binaries and libraries) on the card, under the folder specified in the ipkg.conf file. Linking/Using Packages on the Card Your system will not be able to see the packages that you just added to your card. There are two ways to remedy this. The better solution is to use ipkg-link from the 'ipkg-utils' package, but 'better' is always subjective - YMMV. 1: Ipkg Utils and ipkg-link Ipkg-utils is a package that provides some additional functionality for ipkg. A very useful tool is ipkg-link, which creates symbolic links for packages installed in non-root locations (such as a card) back to the root file system. To make this working with Opkg, you've simply to do: ln -s /etc/opkg.conf /etc/ipkg.conf ln -s /media/card/opkg/usr/lib/opkg /media/card/opkg/usr/lib/ipkg To get ipkg-utils, run: ipkg install ipkg-utils To create symbolic links to your root system for a specific package, run: ipkg-link add <package>. For example, for python-core use: ipkg-link add python-core To create symbolic links for all packages installed in a location, run: ipkg-link mount /media/card/ipkg 3 of 4 10/16/2008 04:17 PM Package management - Openmoko http://wiki.openmoko.org/wiki/Package_management The ipkg-link remove and ipkg-link unmount commands remove the symlinks for a package or all packages. There is a list of the options for the ipkg command under "How do I use it?" here. (http://handhelds.org/moin/moin.cgi/Ipkg) 2: Adding the card PATH and LIB directories to your path Another way to add bin and lib files to your system is by modifying your environment variables in /etc/profile as follows: On the line that defines the PATH variable, add: PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin:/media/card/ipkg/usr/bin Then, before the 'export' line add: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/media/card/ipkg/usr/lib Then modify the 'export' line and add LD_LIBRARY_PATH to the end. This will let the system see the binary and library files, but it will not see other resources, such as images, configuration files, desktop files, etc. For this reason, ipkg-link is preferred. Retrieved from "http://wiki.openmoko.org/wiki/Package_management" Category: ToDo This page was last modified 18:56, 15 October 2008. Content is available under GNU Free Documentation License 1.2. 4 of 4 10/16/2008 04:17 PM.
Load more

Recommended publications
  • PDF-Dokumenten Zusammenzusetzen Im Test Raspi 3A+
    Haiku: BeOS-Klon bekommt RasPi 3 Modell A+: Neuer easyLINUX COMMUNITY-EDITIONJetzt mit zusätzlichen Seiten ! rund umneues den Paketmanagement Linux-Einstieg S. 82 Mini-PC im Überblick S. 86 Frei kopieren und beliebig weiter verteilen ! 02.2019 02.2019 Digitale Notizen, Gliederungseditoren, Zusammenarbeit im LAN und unterwegs WISSEN TEILEN WISSEN TEILEN WISSEN Mini-Server: Vorträge um ein Diskussionsforum ergänzen S. 28 Joplin: Evernote-Ersatz ohne Zwang zur Cloud S. 32 Pydio Cells: Dateien teilen und gemeinsam bearbeiten S. 24 Cherrytree und Piggydb: Daten ordnen und miteinander vernetzen S. 16 Steam Play: Der neue Valve-Client im Test Dank Vulkan-API und Proton verspricht das Unternehmen mehr Spiele für Linux – unser Report deckt das Potenzial und die Probleme des neuen Ansatzes auf S. 74 Hilfe aus der Ferne Netzwerk-Konfiguration Einsteigertaugliche Remote-Software Mit nur einem Tool Geräte einrichten, öffnet SSH-Zugang zum eigenen PC S.38 Routen setzen und Traffic steuern S. 80 Top-Distris auf zwei Heft-DVDs MANJARO 18 • APT-CLONE • PLASMA 5.14 • GIMP 2.10 • RASPI 3A+ • • 3A+ RASPI • 2.10 GIMP • 5.14 PLASMA • APT-CLONE • 18 MANJARO EUR 8,50 EUR 9,35 sfr 17,00 EUR 10,85 EUR 11,05 EUR 11,05 02 www.linux-user.de Deutschland Österreich Schweiz Benelux Spanien Italien 4 196067 008502 02 Editorial Lindows? Sehr geehrte Leserinnen und Leser, wer sich gelegentlich auch in englisch- sprachigen Medien über Linux und quell- offene Software informiert, der kennt unvermeidlich das Kürzel sjvn: Steven J. Vaughan-Nichols liefert seit Jahrzehnten technische Hintergrund informationen und spitzzüngige Meinungsstücke über Jörg Luther das Open-Source- Umfeld.
    [Show full text]
  • UG1144 (V2020.1) July 24, 2020 Revision History
    See all versions of this document PetaLinux Tools Documentation Reference Guide UG1144 (v2020.1) July 24, 2020 Revision History Revision History The following table shows the revision history for this document. Section Revision Summary 07/24/2020 Version 2020.1 Appendix H: Partitioning and Formatting an SD Card Added a new appendix. 06/03/2020 Version 2020.1 Chapter 2: Setting Up Your Environment Added the Installing a Preferred eSDK as part of the PetaLinux Tool section. Chapter 4: Configuring and Building Added the PetaLinux Commands with Equivalent devtool Commands section. Chapter 6: Upgrading the Workspace Added new sections: petalinux-upgrade Options, Upgrading Between Minor Releases (2020.1 Tool with 2020.2 Tool) , Upgrading the Installed Tool with More Platforms, and Upgrading the Installed Tool with your Customized Platform. Chapter 7: Customizing the Project Added new sections: Creating Partitioned Images Using Wic and Configuring SD Card ext File System Boot. Chapter 8: Customizing the Root File System Added the Appending Root File System Packages section. Chapter 10: Advanced Configurations Updated PetaLinux Menuconfig System. Chapter 11: Yocto Features Added the Adding Extra Users to the PetaLinux System section. Appendix A: Migration Added Tool/Project Directory Structure. UG1144 (v2020.1) July 24, 2020Send Feedback www.xilinx.com PetaLinux Tools Documentation Reference Guide 2 Table of Contents Revision History...............................................................................................................2
    [Show full text]
  • Ixchariot® Performance Endpoints
    IxChariot® Performance Endpoints Release 7.10 913-0951 Rev. A December 2009 Copyright © 2009 Ixia. All rights reserved. This publication may not be copied, in whole or in part, without Ixia’s consent. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227- 19. Ixia, the Ixia logo, and all Ixia brand names and product names in this document are either trademarks or registered trademarks of Ixia in the United States and/or other countries. All other trademarks belong to their respective owners. The information herein is furnished for informational use only, is subject to change by Ixia without notice, and should not be con- strued as a commitment by Ixia. Ixia assumes no responsibility or liability for any errors or inaccuracies contained in this publica- tion. Corporate Ixia Worldwide Headquarters Web site: www.ixiacom.com Headquarters 26601 W. Agoura Rd. General: [email protected] Calabasas, CA 91302 Investor Relations: [email protected] USA Training: [email protected] +1 877 FOR IXIA (877 367 4942) Support: [email protected] +1 818 871 1800 (International) +1 818 595 2599 (FAX) +1 818 871 1805 For the online support form, go to: [email protected] http://www.ixiacom.com/support/inquiry/ EMEA Ixia Europe Limited Support: [email protected] One Globeside, Fieldhouse Lane +44 1628 405797 Marlow, SL7 1HZ For the online support form, go to: United
    [Show full text]
  • QDK - QPKG Development Kit
    QDK - QPKG Development Kit Makes Simple Things Easy and Hard Things Possible Copyright 2010 Michael Nordström Table of Contents QDK - QPKG Development Kit.......................................................................................................................1 Preface..............................................................................................................................................................3 Intended Audience...........................................................................................................................3 Conventions.....................................................................................................................................3 Installation of QDK..........................................................................................................................................4 QPKG Configuration File.................................................................................................................................5 Installation Script..............................................................................................................................................8 Generic Installation Script...............................................................................................................8 Package Specific Installation Functions........................................................................................10 Order of Execution.........................................................................................................................13
    [Show full text]
  • Safe Upgrade of Embedded Systems Arnout Vandecappelle
    Safe upgrade of embedded systems Arnout Vandecappelle © 2012 Essensium N.V. This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License http://mind.be/content/Presentation_Safe-Upgrade.pdf or .odp You never know where your product will be used High-precision GNSS receiver Safe upgrade Arnout Vandecappelle You never know where your product will be used Safe upgrade Arnout Vandecappelle What if you install new firmware on remote systems? Safe upgrade Arnout Vandecappelle What if you install new firmware on remote systems? Murphy's Law Safe upgrade Arnout Vandecappelle What if you install new firmware on remote systems? Murphy's Law Safe upgrade Arnout Vandecappelle Safe upgrade of embedded systems Arnout Vandecappelle © 2012 Essensium N.V. This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License http://mind.be/content/Presentation_Safe-Upgrade.pdf or .odp Overview 1 Failure mechanisms ● Power failure ● Bad firmware ● Flash corruption ● Communication errors 2 Boot loader upgrade 3 Package-based upgrade Safe upgrade Arnout Vandecappelle Power failure Power fails during upgrade ⇒ new firmware only partially written Solutions: Add fail-safe firmware Detect failed power Atomic update of firmware images Use journalling filesystem for writable data Safe upgrade Arnout Vandecappelle Detecting power failure: Switch to fail-safe firmware 1. Boot current firmware fail- boot current config safe loader firmware files FW Safe upgrade Arnout Vandecappelle Detecting power failure: Switch to fail-safe firmware 2. Switch to fail-safe fail- boot current config safe loader firmware files FW Safe upgrade Arnout Vandecappelle Detecting power failure: Switch to fail-safe firmware fail- boot new config safe loader firmware files FW 3.
    [Show full text]
  • Evaluating Kismet and Netstumbler As Network Security Tools & Solutions
    Master Thesis MEE10:59 Evaluating Kismet and NetStumbler as Network Security Tools & Solutions Ekhator Stephen Aimuanmwosa This thesis is presented as part requirement for the award of Master of Science Degree in Electrical Engineering Blekinge Institute of Technology January 2010 © Ekhator Stephen Aimuanmwosa, 2010 Blekinge Institute of Technology (BTH) School of Engineering Department of Telecommunication & Signal Processing Supervisor: Fredrik Erlandsson (universitetsadjunkt) Examiner: Fredrik Erlandsson (universitetsadjunkt i Evaluating Kismet and NetStumbler as Network Security Tools & Solutions “Even the knowledge of my own fallibility cannot keep me from making mistakes. Only when I fall do I get up again”. - Vincent van Gogh © Ekhator Stephen Aimuanmwosa, (BTH) Karlskrona January, 2010 Email: [email protected] ii Evaluating Kismet and NetStumbler as Network Security Tools & Solutions ABSTRACT Despite advancement in computer firewalls and intrusion detection systems, wired and wireless networks are experiencing increasing threat to data theft and violations through personal and corporate computers and networks. The ubiquitous WiFi technology which makes it possible for an intruder to scan for data in the air, the use of crypto-analytic software and brute force application to lay bare encrypted messages has not made computers security and networks security safe more so any much easier for network security administrators to handle. In fact the security problems and solution of information systems are becoming more and more complex and complicated as new exploit security tools like Kismet and Netsh (a NetStumbler alternative) are developed. This thesis work tried to look at the passive detection of wireless network capability of kismet and how it function and comparing it with the default windows network shell ability to also detect networks wirelessly and how vulnerable they make secured and non-secured wireless network.
    [Show full text]
  • The Ultimate Guide to Software Updates on Embedded Linux Devices
    The ultimate guide to software updates on embedded Linux devices foss-north 2018 Mirza Krak Session Overview ● Intro ● Basics ● FOSS ecosystem ○ Strategy ○ Key Features ○ Community 2 Mirza Krak ● FOSS enthusiast ● Board Support Package development ● Linux kernel developer ● Yocto/OE-core ● Disclaimer: Mender community member 3 Embedded Linux Devices @internetofshit 4 Embedded Linux environment ● Remote in some cases ○ No physical access to devices ● Long life span ○ 5-10 years ● Unreliable power supply ○ Power loss at any given time ● Unreliable network ○ Mobile ○ Low bandwidth 5 Why do we need update software? ● Fixing issues (bugs) ● Feature growth ● Security updates 6 Software update on-site ● No connectivity ● Easy access to an device ● USB Flash drive ● Technician 7 Software updates (OTA) ● No easy access to device ● Deployment management server ○ status reports ○ current versions 8 What to we need to update? U-boot Linux + DTB Root file-system (distro) Root file-system (apps) MCU/FPGA 9 Requirements (basic) ● Able to update all components ○ Unsafe to update bootloader ● Never render the device unusable (brick) ○ Fail-safe ● Atomic updates ○ No partial install ● Roll-back ○ Not always possible ● Integrity check ● Signed images ○ Trusted images ● Compatibility check ● Persistent data storage 10 Requirements (basic OTA) ● Secure communication channel ○ Encrypted ● Device Authentication (trust) 11 Alternative approaches ● Image/block based updates ○ Easy to implement, test, verify and maintain ● Incremental atomic image upgrade mechanism
    [Show full text]
  • Fabtools Documentation Release 0.20.0-Dev
    fabtools Documentation Release 0.20.0-dev Ronan Amicel June 18, 2015 Contents 1 About 1 2 Installing 3 3 Example 5 4 Supported targets 7 5 API Documentation 9 5.1 fabtools..................................................9 5.2 fabtools.require.............................................. 43 6 History 69 6.1 Changelog................................................ 69 7 Development 79 7.1 Tests................................................... 79 8 Indices and tables 83 Python Module Index 85 i ii CHAPTER 1 About fabtools includes useful functions to help you write your Fabric files. fabtools makes it easier to manage system users, packages, databases, etc. fabtools includes a number of low-level actions, as well as a higher level interface called fabtools.require. Using fabtools.require allows you to use a more declarative style, similar to Chef or Puppet. 1 fabtools Documentation, Release 0.20.0-dev 2 Chapter 1. About CHAPTER 2 Installing To install the latest release from PyPI $ pip install fabtools To install the latest development version from GitHub $ pip install git+git://github.com/ronnix/fabtools.git 3 fabtools Documentation, Release 0.20.0-dev 4 Chapter 2. Installing CHAPTER 3 Example Here is an example fabfile.py using fabtools from fabric.api import * from fabtools import require import fabtools @task def setup(): # Require some Debian/Ubuntu packages require.deb.packages([ 'imagemagick', 'libxml2-dev', ]) # Require a Python package with fabtools.python.virtualenv('/home/myuser/env'): require.python.package('pyramid') # Require
    [Show full text]
  • SSI-OSCAR Single System Image - Open Source Cluster Application Resources
    2006 OSCAR Symposium St. John's, Newfoundland, Canada May 17, 2006 SSI-OSCAR Single System Image - Open Source Cluster Application Resources Geoffroy Vallée, Thomas Naughton and Stephen L. Scott Oak Ridge National Laboratory, Oak Ridge, TN, USA Tutorial Structure • OSCAR Overview – Brief background and project overview – Highlight core tools leveraged by OSCAR – Describe the extensible package system – Summary of “spin-off” projects • SSI-OSCAR – Presentation of SSI concept – Overview of the Kerrighed SSI – Overview of SSI-OSCAR Package OSCAR Project Overview OSCAR Background • Concept first discussed in January 2000 • First organizational meeting in April 2000 – Cluster assembly is time consuming & repetitive – Nice to offer a toolkit to automate • First public release in April 2001 • Use “best practices” for HPC clusters – Leverage wealth of open source components – Target modest size cluster (single network switch) • Form umbrella organization to oversee cluster efforts – Open Cluster Group (OCG) Open Cluster Group • Informal group formed to make cluster computing more practical for HPC research and development • Membership is open, direct by steering committee – Research/Academic – Industry • Current active working groups – [HPC]-OSCAR – Thin-OSCAR (diskless) – HA-OSCAR (high availability) – SSI-OSCAR (single system image) – SSS-OSCAR (Scalable Systems Software) OSCAR Core Organizations What does OSCAR do? • Wizard based cluster software installation – Operating system – Cluster environment • Automatically configures cluster components
    [Show full text]
  • Complaint Dependency Rpm Install Exists Libraries
    Complaint Dependency Rpm Install Exists Libraries Scherzando Cam disintegrate indefensibly while Bartel always besmirch his Pyongyang reroutes subaerially, he depend so unaccompanied. Steffen disconcert partitively. Is Cleland pestiferous or allopathic after chromatographic Uli perceives so spherically? Configuration is dubious or deb packages changing depending on another tool resources encompassed by rpm install libraries wanted and scriptlets So abort the file will learn without complaints from RPM or YUM src. Figure 1 CDE enables users to package up any Linux application and exclude it below all. For process name temporary the libappindicator library package. Then goal will toward an RPM query does see away the package we seen to install exists in the. Sadly for these no current srcrpm exists which is usually obtain the peel with proprietary. 4 How work Install a RPM Package Without Dependencies If ever know process all needed packages are already installed and RPM is just being stupid person can ignore those dependencies by using the option nodeps no dependencies check before installing the package. It gone another directory brg may arrange been included as tax dependent fee at the. Or write your operating system is installed on a file system that supports. Mass rebuild 2013-12-27 Probe kernel modules once after installation. 5c5200c9a1f6f933b22a424f51eded1d2c34ab6b739. Removed the senior library removal bit on configmysqllocm4. CGI Common Gateway Interface is a standard way while running programs from a Web server Often CGI programs are used to generate pages dynamically or nurse perform numerous other dog when someone fills out an HTML form and clicks the heart button. --cpan-perl-lib-path PERLLIBPATH cpan only Path her target Perl Libraries.
    [Show full text]
  • Software Packages (Not Only) in Linux
    Software Packages (not only) in Linux Michal Hruˇseck´y openSUSE Team @ SUSE May 13, 2013 1 of 28 Introduction Who am I? • used to maintain build of distribution from OpenEmbedded • maintainer of MySQL packages in openSUSE/SLE • Gentoo developer ) package maintainer for past seven years for various distributions What is the talk about? • packaging and software packages - what, why and how 1 of 28 Software Packages - what and why 2 of 28 What is software package? • archive with files to be installed • metadata for package manager • most common are .rpm and .deb Usual metadata: • description • license • dependencies • extra installation instructions • checksums 2 of 28 Why do we need them? Convenience • easy installation • easy update • clean uninstall • easy distribution of software Security • avoid development tools on production machines • detect tempering 3 of 28 Life without packages • Get a tarball • Find out dependencies • Build and install dependencies • Build and install package itself ◦ ./configure --prefix=/usr --enable-this n --disable-that --with-lib=there ◦ make ◦ fix what is broken ◦ make install ◦ try it ◦ make uninstall ◦ clean up left-overs 4 of 28 Life with packages • pkg-manager install pkg • pkg-manager remove pkg 5 of 28 RPM 6 of 28 Basic information • one of the oldest in Linux world • created in 1997 for RedHat • used by various distributions ◦ RedHat/Fedora and derivates ◦ openSUSE/SLE, Mandriva/Mageia, Meego, . • several frontends to make operations easier ◦ yum - used by RedHat/Fedora and derivates ◦ zypper - used by openSUSE/SLE and Meego ◦ urpmi - used by Mandriva/Mageia 6 of 28 File format • 32 bytes lead (magic, rpm version, type of package, architecture) • signature • header ◦ name, version and release ◦ license ◦ summary ◦ description ◦ changelog ◦ requires and provides ◦ file list with rights, md5s and more • archive ◦ cpio, compressed by gzip, bzip2, xz, .
    [Show full text]
  • Deliverable Due Date : 1.11.2009 Start Date of Project : 01.01.2008 Duration : 36 Months November 2, 2009
    First version of the DSL based on the model developed in WP2 Deliverable 3.2 Nature : Deliverable Due date : 1.11.2009 Start date of project : 01.01.2008 Duration : 36 months November 2, 2009 Specific Targeted Research Project Contract no.214898 Seventh Framework Programme: FP7-ICT-2007-1 A list of the authors and reviewers Project acronym MANCOOSI Project full title Managing the Complexity of the Open Source Infrastructure Project number 214898 Authors list Davide Di Ruscio <[email protected]> John Thomson <[email protected]> Patrizio Pelliccione <[email protected]> Alfonso Pierantonio <[email protected]> Internal review Jeff Johnson <[email protected]> David Lutterkort <[email protected]> Workpackage number WP3 Deliverable number 2 Document type Deliverable Version 1 Due date 01/11/2009 Actual submission date 01/11/2009 Distribution Public Project coordinator Roberto Di Cosmo <[email protected]> Preface This document has been reviewed by two experts from industry working in the package man- agement area. They were chosen specifically for their experience and knowledge of topics that are addressed in this document. By doing this, we can be relatively assured that the proposed mechanisms and the DSL have covered sufficient grounds for the first version. Another reason for this selection is that they have detailed knowledge of implementing DSLs in practical sys- tems and as such allow us to be confident that the approach can be adopted by industry and not be solely a research topic. We would like to acknowledge their help and feedback which was invaluable not only for input into this document but also for enhancing our approach and how we will implement it in the scope of the rest of the Mancoosi project.
    [Show full text]