How to Install and Configure Canon Pixma Ip3300 Printer for Color Printing on Ubuntu and Debian Linux
Total Page：16
File Type：pdf, Size：1020Kb
Load more
Recommended publications
-
Installation Iraf
INSTALLATION IRAF o IRAF: IMAGE REDUCTION AND ANALYSIS FACILITY (NOAO, TUCSON) SCISOFT (IRAF + DS9 + ...) MAC http://scisoftosx.dyndns.org/ LINUX http://www.eso.org/sci/software/scisoft/ P. OCVIRK - COURS DE REDUCTION DES DONNEES - M2 OBSERVATOIRE ASTRONOMIQUE DE STRASBOURG IRAF UBUNTU o DEPENDANCES o IRAF o CONFIG IRAF P. OCVIRK - COURS DE REDUCTION DES DONNEES - M2 OBSERVATOIRE ASTRONOMIQUE DE STRASBOURG INSTALLATION IRAF UBUNTU OCTOBRE 2012 Dependances (a installer avant iraf) o C’est peut-etre la premiere fois que vous devez installer des dependances. Vous aurez peut-etre l’impression de ne pas tout comprendre. Peu importe!! Le but c’est d’avoir iraf qui tourne! o Certaines sont deja presentes. Pour tester leur existence sur votre systeme: locate <ma dependance> o En general elles s’installent grace a apt-get: sudo apt-get install <ma dependance> o En cas de probleme avec une dependance, google est votre ami: faire une recherche “install SDL_image ubuntu” par exemple o Toutes les commandes de cette aide se lancent dans un terminal (ou xterm), la plupart (mais pas toutes!!) en mode super-user. Elles debutent alors par sudo (super-user do). P. OCVIRK - COURS DE REDUCTION DES DONNEES - M2 OBSERVATOIRE ASTRONOMIQUE DE STRASBOURG INSTALLATION IRAF UBUNTU OCTOBRE 2012 Dependances 1 o csh: sudo apt-get install csh o tcsh: sudo apt-get install tcsh o emacs (editeur de textes): sudo apt-get install emacs o SDL_image, SDL_ttf, libgfortran: deja installees? (me contacter si elles n’apparaissent pas avec un locate) P. OCVIRK - COURS DE REDUCTION DES DONNEES - M2 OBSERVATOIRE ASTRONOMIQUE DE STRASBOURG INSTALLATION IRAF UBUNTU OCTOBRE 2012 Dependances 2: le cas particuler de compat-libf2c-34. -
Cross-Compiling Linux Kernels on X86 64: a Tutorial on How to Get Started
Cross-compiling Linux Kernels on x86_64: A tutorial on How to Get Started Shuah Khan Senior Linux Kernel Developer – Open Source Group Samsung Research America (Silicon Valley) [email protected] Agenda ● Cross-compile value proposition ● Preparing the system for cross-compiler installation ● Cross-compiler installation steps ● Demo – install arm and arm64 ● Compiling on architectures ● Demo – compile arm and arm64 ● Automating cross-compile testing ● Upstream cross-compile testing activity ● References and Package repositories ● Q&A Cross-compile value proposition ● 30+ architectures supported (several sub-archs) ● Native compile testing requires wide range of test systems – not practical ● Ability to cross-compile non-natively on an widely available architecture helps detect compile errors ● Coupled with emulation environments (e.g: qemu) testing on non-native architectures becomes easier ● Setting up cross-compile environment is the first and necessary step arch/ alpha frv arc microblaze h8300 s390 um arm mips hexagon score x86_64 arm64 mn10300 unicore32 ia64 sh xtensa avr32 openrisc x86 m32r sparc blackfin parisc m68k tile c6x powerpc metag cris Cross-compiler packages ● Ubuntu arm packages (12.10 or later) – gcc-arm-linux-gnueabi – gcc-arm-linux-gnueabihf ● Ubuntu arm64 packages (13.04 or later) – use arm64 repo for older Ubuntu releases. – gcc-4.7-aarch64-linux-gnu ● Ubuntu keeps adding support for compilers. Search Ubuntu repository for packages. Cross-compiler packages ● Embedded Debian Project is a good resource for alpha, mips, -
27Th Large Installation System Administration Conference (LISA '13)
conference proceedings Proceedings of the 27th Large Installation System Administration Conference 27th Large Installation System Administration Conference (LISA ’13) Washington, D.C., USA November 3–8, 2013 Washington, D.C., USA November 3–8, 2013 Sponsored by In cooperation with LOPSA Thanks to Our LISA ’13 Sponsors Thanks to Our USENIX and LISA SIG Supporters Gold Sponsors USENIX Patrons Google InfoSys Microsoft Research NetApp VMware USENIX Benefactors Akamai EMC Hewlett-Packard Linux Journal Linux Pro Magazine Puppet Labs Silver Sponsors USENIX and LISA SIG Partners Cambridge Computer Google USENIX Partners Bronze Sponsors Meraki Nutanix Media Sponsors and Industry Partners ACM Queue IEEE Security & Privacy LXer ADMIN IEEE Software No Starch Press CiSE InfoSec News O’Reilly Media Computer IT/Dev Connections Open Source Data Center Conference Distributed Management Task Force IT Professional (OSDC) (DMTF) Linux Foundation Server Fault Free Software Magazine Linux Journal The Data Center Journal HPCwire Linux Pro Magazine Userfriendly.org IEEE Pervasive © 2013 by The USENIX Association All Rights Reserved This volume is published as a collective work. Rights to individual papers remain with the author or the author’s employer. Permission is granted for the noncommercial reproduction of the complete work for educational or research purposes. Permission is granted to print, primarily for one person’s exclusive use, a single copy of these Proceedings. USENIX acknowledges all trademarks herein. ISBN 978-1-931971-05-8 USENIX Association Proceedings of the 27th Large Installation System Administration Conference November 3–8, 2013 Washington, D.C. Conference Organizers Program Co-Chairs David Nalley, Apache Cloudstack Narayan Desai, Argonne National Laboratory Adele Shakal, Metacloud, Inc. -
Release Notes
LispWorks® Release Notes and Installation Guide Version 5.1 Copyright and Trademarks LispWorks Release Notes and Installation Guide Version 5.1 March 2008 Copyright © 2008 by LispWorks Ltd. All Rights Reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of LispWorks Ltd. The information in this publication is provided for information only, is subject to change without notice, and should not be construed as a commitment by LispWorks Ltd. LispWorks Ltd assumes no responsibility or liability for any errors or inaccuracies that may appear in this publication. The software described in this book is furnished under license and may only be used or copied in accordance with the terms of that license. LispWorks and KnowledgeWorks are registered trademarks of LispWorks Ltd. Adobe and PostScript are registered trademarks of Adobe Systems Incorporated. Other brand or product names are the registered trade- marks or trademarks of their respective holders. The code for walker.lisp and compute-combination-points is excerpted with permission from PCL, Copyright © 1985, 1986, 1987, 1988 Xerox Corporation. The XP Pretty Printer bears the following copyright notice, which applies to the parts of LispWorks derived therefrom: Copyright © 1989 by the Massachusetts Institute of Technology, Cambridge, Massachusetts. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, pro- vided that this copyright and permission notice appear in all copies and supporting documentation, and that the name of M.I.T. -
Building and Installing Software Packages for Linux Building and Installing Software Packages for Linux
Building and Installing Software Packages for Linux Building and Installing Software Packages for Linux Table of Contents Building and Installing Software Packages for Linux.....................................................................................1 Mendel Cooper −−− http://personal.riverusers.com/~thegrendel/...........................................................1 1.Introduction...........................................................................................................................................1 2.Unpacking the Files..............................................................................................................................1 3.Using Make...........................................................................................................................................1 4.Prepackaged Binaries............................................................................................................................1 5.Termcap and Terminfo Issues...............................................................................................................1 6.Backward Compatibility With a.out Binaries.......................................................................................1 7.Troubleshooting....................................................................................................................................2 8.Final Steps.............................................................................................................................................2 -
Reader Interface Guide for Alien RFID Readers
® ALIEN TECHNOLOGY READER INTERFACE GUIDE All Fixed Readers November 2019 ALR-F800 ALR-9900+ ALR-9680 ALR-9650 Legal Notices Copyright ©2019 Alien Technology, LLC. All rights reserved. Alien Technology, LLC has intellectual property rights relating to technology embodied in the products described in this document, including without limitation certain patents or patent pending applications in the U.S. or other countries. This document and the products to which it pertains are distributed under licenses restricting their use, copying, distribution and decompilation. No part of this product documentation may be reproduced in any form or by any means without the prior written consent of Alien Technology, LLC and its licensors, if any. Third party software is copyrighted and licensed from Licensors. Alien, Alien Technology, the Alien logo, Squiggle and other graphics, logos, and service names used in this document are trademarks of Alien Technology, LLC in the U.S. and other countries. All other trademarks are the property of their respective owners. U.S. Government approval required when exporting the product described in this documentation. Federal Acquisitions: Commercial Software -- Government Users Subject to Standard License Terms and Conditions. U.S. Government: If this Software is being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), then the Government's rights in the Software and accompanying documentation shall be only as set forth in this license; this is in accordance with 48 C.F.R. 227.7201 through 227.7202-4 (for Department of Defense (DoD) acquisitions) and with 48 C.F.R. -
Debian Quick Reference
Debian Quick Reference Osamu Aoki <[email protected]> Editor: David Sewell <[email protected]> ‘Authors’ on page 21 CVS, Sun, 13 Oct 2002 22:40:23 -0600 Abstract This Debian Quick Reference (http://qref.sourceforge.net/) is intended to provide a short introduction to the Debian system as a quick reference. This is an excerpt of Debian Refer- ence (http://qref.sourceforge.net/). Copyright Notice Copyright © 2001–2002 by Osamu Aoki <[email protected]>. This document may used under the terms of the GNU General Public License version 2 or higher. (http://www.gnu.org/copyleft/gpl.html) Permission is granted to make and distribute verbatim copies of this document provided the copy- right notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this document under the con- ditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this document into another language, under the above conditions for modified versions, except that this permission notice may be in- cluded in translations approved by the Free Software Foundation instead of in the original English. i Contents 1 Preface 1 1.1 Document conventions .................................... 1 1.2 Basics of the Debian distributions .............................. 1 2 Upgrading a distribution 3 2.1 Upgrade to “testing” ..................................... 3 2.1.1 Best upgrade practice using dselect ....................... 3 2.2 Woody configuration ..................................... 3 3 Debian package management 5 3.1 Introduction .......................................... 5 3.1.1 Main tools ...................................... -
Linux for Dummies 6Th Ed
01_579371 ffirs.qxd 12/27/04 7:54 PM Page i Linux® FOR DUMmIES‰ 6TH EDITION by Dee-Ann LeBlanc 01_579371 ffirs.qxd 12/27/04 7:54 PM Page iv 01_579371 ffirs.qxd 12/27/04 7:54 PM Page i Linux® FOR DUMmIES‰ 6TH EDITION by Dee-Ann LeBlanc 01_579371 ffirs.qxd 12/27/04 7:54 PM Page ii Linux® For Dummies®, 6th Edition Published by Wiley Publishing, Inc. 111 River Street Hoboken, NJ 07030-5774 Copyright © 2005 by Wiley Publishing, Inc., Indianapolis, Indiana Published by Wiley Publishing, Inc., Indianapolis, Indiana Published simultaneously in Canada No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permit- ted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permission should be addressed to the Legal Department, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, (317) 572-3447, fax (317) 572-4355, e-mail: brand [email protected]. Trademarks: Wiley, the Wiley Publishing logo, For Dummies, the Dummies Man logo, A Reference for the Rest of Us!, The Dummies Way, Dummies Daily, The Fun and Easy Way, Dummies.com, and related trade dress are trademarks or registered trademarks of John Wiley & Sons, Inc. -
The Non-Discrimination Principle in Open Source Licensing
GREENBAUM.37.4.4 (Do Not Delete) 4/3/2016 1:48 PM THE NON-DISCRIMINATION PRINCIPLE IN OPEN SOURCE LICENSING Eli Greenbaum† Open source communities have required licenses to satisfy requirements of non-discrimination. This principle of non-discrimination, however, has remained peripheral to the interpretation of open source licenses, with legal analysis concentrating on other aspects of open source regimes. This Article argues that non- discrimination, far from being marginal to open source, constitutes the central legal characteristic of the licensing model, and that an appreciation of the non- discrimination requirement is essential for understanding the economic incentives and effects of the open source license. This Article applies this understanding of the non-discrimination principle to interpret specific terms in free and open source licenses. In a number of instances, the interpretation consistent with the non- discrimination principle stands in contrast to generally accepted understandings of specific license provisions. TABLE OF CONTENTS INTRODUCTION .............................................................................................................. 1298 I. DEBIAN AND THE DEFINITIONS ............................................................................. 1302 A. History of the Non-Discrimination Principle .......................................... 1302 B. Interpretive Potential ................................................................................. 1306 C. In the Licenses ............................................................................................ -
Installing Using an RPM File
Installing using an RPM file If you have an rpm file for a package you wish to install, and if you cannot find a .deb debian package in any of the Ubuntu repositories or elsewhere, you can use the alien package converter application to install the .rpm file. Alien is a program that converts between the rpm, dpkg, stampede slp, and slackware tgz file formats. If you want to use a package from another distribution than the one you have installed on your system, you can use alien to convert it to your preferred package format and install it. Despite the large version number, alien is still (and will probably always be) rather experimental software. It has been used by many people for many years, but there are still many bugs and limitations. Alien should not be used to replace important system packages, like sysvinit, shared libraries, or other things that are essential for the functioning of your system. Many of these packages are set up differently by Debian and Red Hat, and packages from the different distributions cannot be used interchangably. In general, if you can’t uninstall the package without breaking your system, don’t try to replace it with an alien version. Instructions for Installing RPM Files Using Alien Installing Alien You can install alien itself from the Ubuntu Universe repository by adding the repository to your list of sources and doing: $sudo apt-get update $sudo apt-get install alien Installing the .rpm file To install the .rpm file, you first need to convert it to a .deb file which can be installed on Ubuntu. -
Master Your Package Management
TUTORIAL PACKAGE MANAGEMENT LINUX 101: MASTER YOUR TUTORIAL PACKAGE MANAGEMENT SYSTEM apt-get, dpkg, yum, zypper… There are many ways to install MIKE SAUNDERS packages on your Linux box. Here’s everything you need to know. ackage management systems are both loved WHY DO THIS? and hated in the Linux world. On the one hand, • Understand how they provide efficient ways to install and packages work and what P exactly they provide remove software, with everything neatly bundled up. • Learn vital admin skills (Contrast this to Windows, where a setup.exe typically to manage packages scatters all sorts of stuff all over your hard drive and outside of the GUI registry, and running the “uninstaller” doesn’t get rid of • Discover how packaging everything. You can even find third-party “uninstall” systems work across other distros tools designed to clean up this hideous mess.) On the other hand, package management systems often make it difficult to get the latest hot new applications. You have to find the right repository for your distribution, and make sure dependencies are satisfied (usually this is automatic, but not always), Here’s the metadata for the Debian Vim package, obtained and so forth. And if you’re completely new to Linux, with the dpkg -I command. Note the highlighted line, you might find all of the terminology here baffling. So showing dependencies. in this tutorial we’ll explore the two main packaging systems used in GNU/Linux distributions, and provide list GTK as a dependency in its metadata. Package some advanced tips and tricks for long-time Linuxers systems normally handle dependencies as well. -
Installing Ruby on Rails in Linux
Installing Ruby on Rails in Linux General rules Some general ideas apply throughout the installation. • Each Linux distribution has its own idiosyncrasies. The steps that work with Red Hat Linux don©t necessarily work the same way with SUSE Linux. The same is true for different versions of the same distribution. For example, what works well in Fedora Core 6 may not work exactly the same way in Fedora Core 5. Your best bet is to find your distribution©s most recent version. (I realize that installing the most recent version isn©t always practical. But sometimes, having the most recent version makes the difference between an effortless installation and a pain-in-the-neck installation.) • Some of the steps described in this document can be executed only with root privileges. The best way to get temporary root privileges is to issue a sudo command. For example, to search for all files ending in .rpm, and to do so as the big, powerful root user, open a terminal window and type sudo find / -name *.rpm -print After typing a sudo command, the system asks you for the root user©s password. For newly installed Linux systems, the root password is something that©s simple and well-documented. For example, the root password may be root, or there may be no root password (in which case, you press Enter when you©re prompted for the root password). On established Linux systems (systems that you use at work, for example) you must obtain the root password from your system administrator (after giving the administrator a pound of flesh).