DOCSLIB.ORG

Wenv Documentation Release 0.2.1

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Wenv Documentation Release 0.2.1 wenv Documentation Release 0.2.1 Sebastian M. Ernst Jul 10, 2020 Contents 1 Introduction 3 1.1 Synopsis.................................................3 1.2 Motivation................................................3 1.3 Implementation..............................................4 1.4 Use cases.................................................4 2 Installation 5 2.1 Getting Wine ...............................................5 2.2 Getting wenv ...............................................5 2.3 Possible problem: OSError: [WinError 6] Invalid handle ..............6 2.4 Installing wenv in development mode..................................6 3 Examples 7 4 Configuration 9 4.1 Configuration files............................................9 4.2 Configuration environment variables..................................9 4.3 Configurable parameters......................................... 10 5 Usage 13 5.1 Command: wenv init ........................................ 13 5.2 Command: wenv clean ........................................ 13 5.3 Command: wenv help ........................................ 13 5.4 Command: wenv python ....................................... 13 5.5 Command: wenv pip ......................................... 14 5.6 Command: wenv init_coverage ................................. 14 6 API: class Env 15 6.1 Constructor: Env(**kwargs) ..................................... 15 6.2 Method: ensure() ........................................... 15 6.3 Method: wine_47766_workaround() ............................... 15 6.4 Method: setup_wineprefix(overwrite = False) ..................... 16 6.5 Method: setup_pythonprefix(overwrite = False) .................... 16 6.6 Method: setup_pip() ........................................ 16 6.7 Method: install_package(name, update = False) .................... 16 6.8 Method: uninstall_package(name) ............................... 16 6.9 Method: list_packages() ..................................... 16 i 6.10 Method: shebang() .......................................... 16 6.11 Method: cli() ............................................. 16 6.12 Method: uninstall() ........................................ 16 6.13 Method: setup_coverage_activate() ............................. 17 7 Security 19 8 Bugs 21 8.1 How to bisect issues........................................... 21 9 FAQ 23 9.1 Why?................................................... 23 9.2 What are actual use cases for this project?................................ 23 9.3 How does it work?............................................ 23 9.4 Is it secure?................................................ 23 10 Indices and tables 25 Index 27 ii wenv Documentation, Release 0.2.1 Running Python on Wine. wenv is a Python package (currently in development status 4/beta). It allows to run Python on top of Wine on Linux, MacOS or BSD. It handles required plumbing related to making Python and a number of Python modules work on Wine. wenv creates isolated virtual environments which can be transparently used from a Unix command line and which seamlessly integrate into Unix Python virtual environments. Contents 1 wenv Documentation, Release 0.2.1 2 Contents CHAPTER 1 Introduction 1.1 Synopsis wenv is a Python package (currently in development status 4/beta). It allows to run Python on top of Wine on Linux, MacOS or BSD. It handles required plumbing related to making Python and a number of Python modules work on Wine. wenv creates isolated virtual environments which can be transparently used from a Unix command line and which seamlessly integrate into Unix Python virtual environments. 1.2 Motivation wenv was derived from the Python package zugbruecke. zugbruecke allows to call routines in Windows DLLs from Python code running on Unices / Unix-like systems such as Linux, MacOS or BSD. wenv’s code started out as infras- tructure for zugbruecke. Eventually, it became too complex on its own and - at the same time - began to enable new and interesting use cases beyond the scope of zugbruecke. Technically, the basic problem is how to install (and run) just any version or distribution of Python on Wine. The in- stallers of most Python distributions including Anaconda and even CPython itself tend to be broken on most versions of Wine (“garbage” in Wine jargon). For a while, ActiveState’s ActivePython was the only “easy” way of directly installing Python on Wine, but even this path was (and still is) extremely unreliable. The commonly recommended workaround is to install Python directly on Windows and copy the resulting installation directory tree over to Unix/Wine. First, this is not an option for everybody as it requires a Windows installation. Second, it is also notoriously unreliable. While researching options for developing zugbruecke, CPython’s embeddable package for Windows showed up on the radar. It is a simple ZIP-file without any installer. By merely unpacking it, one can run Python without an issue. With some manual tweaking and tuning of both the unpacked folder and Wine, it becomes possible to make pip work and install just about anything on top. wenv essentially takes care of the entire process automatically. 3 wenv Documentation, Release 0.2.1 1.3 Implementation wenv has two roles. First, it downloads, installs and configures both CPython and pip. The process is based on CPython’s embeddable package distribution for Windows. Second, wenv provides a thin launcher for staring Python (or just any Python application) on Wine. The installer and launcher themselves are also written in Python and run on any Unix-version of Python. The launcher sets the stage in Unix Python before using an exec syscall to replace itself with Windows Python. 1.4 Use cases • Running Python apps & scripts written for Windows on Unix. • Running critical portions of Python apps depending on Windows on Unix - while the remaining uncritical por- tions of those apps can directly run on Unix. Inter-process communication can bridge the gap. • Testing the Windows compatibility of Python apps directly on Unix. • Accessing proprietary DLLs through ctypes, cffi, swig, sip, f2py and friends. Also see the zugbruecke project. • Running a Windows version of Python as a Jupyter kernel next to a Unix version, see the wenv-kernel project. 4 Chapter 1. Introduction CHAPTER 2 Installation 2.1 Getting Wine For using wenv, you need to install Wine first. Depending on your platform, there are different ways of doing that. • Installation instructions for various Linux distributions • Installation instructions for Mac OS X • Installation instructions for FreeBSD Currently, Wine >= 4.x is supported (tested). If you are limited to an older version of Wine such as 2.x or 3.x, you have one option: Try to set the pythonversion configuration parameter to 3.5.4. 2.2 Getting wenv The latest stable release version can be installed with pip: pip install wenv If you are interested in testing the latest work from the development branch, you can try it like this: pip install git+https://github.com/pleiszenburg/wenv.git@develop After installing the package with pip, you must initialize the “Wine Python environment” by running wenv init. If you are relying on wenv, please notice that it uses semantic versioning. Breaking changes are indicated by increasing the first version number, the major version. Going for example from 0.0.x to 1.0.0 or going from 0.1.y to 1.0.0 therefore indicates a breaking change. 5 wenv Documentation, Release 0.2.1 2.3 Possible problem: OSError: [WinError 6] Invalid handle On older versions of Linux such as Ubuntu 14.04 alias Trusty Tahr (released 2014), you may observe errors when run- ning wenv python. Most commonly, they will present themselves as OSError: [WinError 6] Invalid handle: 'z:\\... triggered by calling os.listdir on a symbolic link (“symlink”) to a folder. A clean solution is to upgrade to a younger version of Linux. E.g. Ubuntu 16.04 alias Xenial Xerus (released 2016) is known to work. 2.4 Installing wenv in development mode If you are interested in contributing to wenv, you might want to install it in development mode. You can find the latest instructions on how to do this in the CONTRIBUTING file of this project on Github. 6 Chapter 2. Installation CHAPTER 3 Examples Fire up a shell and try the following: (env) user@comp:~> uname Linux (env) user@comp:~> python-m platform Linux (env) user@comp:~> wenv python-m platform Windows wenv pip works just like one would expect. Have a look at the output of wenv help for more commands and in- formation. For use as a shebang, wenv python has an alias: One can write #!/usr/bin/env _wenv_python at the top of scripts. wenv python can also be used as a Jupyter kernel, side-by-side with a Unix-version of Python. Have a look at the wenv-kernel project. 7 wenv Documentation, Release 0.2.1 8 Chapter 3. Examples CHAPTER 4 Configuration wenv can configure itself automatically or can be configured with files and environment variables manually. 4.1 Configuration files wenv uses JSON configuration files named .wenv.json. They are expected in the following locations (in that order): • The current working directory • A directory specified in the WENV environment variable • The user profile folder (~ / /home/{username}) • /etc There is one optional addition to the above rules: The path specified in the WENV environment variable can directly point to a configuration file. I.e. the WENV environment variable can also contain a path similar to /path/to/ some/file.json. Configuration options are being looked for location after location in the above listed places. If, after
Load more

Recommended publications
  • ECOGEO Workshop 2: Introduction to Env 'Omics
    ECOGEO Workshop 2: Introduction to Env ‘Omics Unix and Bioinformatics Ben Tully (USC); Ken Youens-Clark (UA) Unix Commands pwd rm grep tail install ls ‘>’ sed cut cd cat nano top mkdir ‘<’ history screen touch ‘|’ $PATH ssh cp sort less df mv uniq head rsync/scp Unix Command Line 1. Open Terminal window Unix Command Line 2. Open Chrome and navigate to Unix tutorial at Protocols.io 3. Group: ECOGEO 4. Protocol: ECOGEO Workshop 2: Unix Module ! This will allow you to copy, paste Unix scripts into terminal window ! ECOGEO Protocols.io for making copy, paste easier Unix Command Line $ ls ls - lists items in the current directory Many commands have additional options that can be set by a ‘-’ $ ls -a Unix Command Line $ ls -a lists all files/directories, including hidden files ‘.’ $ ls -l lists the long format File Permissions | # Link | User | Group | Size | Last modified $ ls -lt lists the long format, but ordered by date last modified Unix Command Line Unix Command Line $ cd ecogeo/ cd - change directory List the contents of the current directory Move into the directory called unix List contents $ pwd pwd - present working directory Unix Command Line /home/c-debi/ecogeo/unix When were we in the directory home? Or c-debi? Or ecogeo? $ cd / Navigates to root directory List contents of root directory This where everything is stored in the computer All the commands we are running live in /bin Unix Command Line / root bin sys home mnt usr c-debi BioinfPrograms cdebi Desktop Downloads ecogeo unix assembly annotation etc Typical Unix Layout Unix Command Line Change directory to home Change directory to c-debi Change directory to ecogeo Change directory to unix List contents Change directory to data Change directory to root Unix Command Line Change directory to unix/data in one step $ cd /home/c-debi/ecogeo/unix/data Tab can be used to auto complete names $ cd .
    [Show full text]
  • Spirent Testcenter Automation Validating the Environment and Configuring the System Variables – an Overview
    Spirent TestCenter Automation Validating the environment and configuring the system variables – an overview August 10 2016 SRE Chicago Vijay Muthucumarasamy Principle Field Service Engineer Spirent Communications PROPRIETARY AND CONFIDENTIAL 1 Agenda Spirent Automation and Supported Platforms Operating System and Validation Environment Set up and Verification • TCL • Python • Perl Lab Server HLTAPI Command Sequencer Q & A Spirent Communications PROPRIETARY AND CONFIDENTIAL 2 Supported OS and API 1. Multi-threaded 2. If you are using Avalanche on Spirent TestCenter, Windows 2008 server is not officially supported at this time. 3. Running as a 32-bit application 4. Requires LabServer 5. Requires openssh-client package **** PLEASE Check the release notes for updated information Spirent Communications PROPRIETARY AND CONFIDENTIAL 3 Spirent API Packages for Linux Environment Spirent Communications PROPRIETARY AND CONFIDENTIAL 4 Verify and Validate the OS & API Before install the STC installation packages • Verify the Operating System - Kernel - CPU - Memory - Validate the requirement : Check the Spirent TestCenter releases and verify Spirent requirements • Verify the API (TCL/Python/Perl) - Release version - Whether 32/64 bit platform - Whether need a Spirent Lab Server - Validate the requirement : Check the Spirent TestCenter releases and verify Spirent requirements Spirent Communications PROPRIETARY AND CONFIDENTIAL 5 Operating System and Validation Verify Kernel version • CentOS/RedHat/Ubuntu - cat /etc/issue - cat /etc/redhat-release
    [Show full text]
  • Pingdirectory Administration Guide Version
    Release 7.3.0.3 Server Administration Guide PingDirectory | Contents | ii Contents PingDirectory™ Product Documentation................................................ 20 Overview of the Server............................................................................. 20 Server Features.................................................................................................................................20 Administration Framework.................................................................................................................21 Server Tools Location....................................................................................................................... 22 Preparing Your Environment....................................................................22 Before You Begin.............................................................................................................................. 22 System requirements..............................................................................................................22 Installing Java......................................................................................................................... 23 Preparing the Operating System (Linux).......................................................................................... 24 Configuring the File Descriptor Limits.................................................................................... 24 File System Tuning.................................................................................................................25
    [Show full text]
  • Environment Variable and Set-UID Program Lab 1
    SEED Labs – Environment Variable and Set-UID Program Lab 1 Environment Variable and Set-UID Program Lab Copyright © 2006 - 2016 Wenliang Du, All rights reserved. Free to use for non-commercial educational purposes. Commercial uses of the materials are prohibited. The SEED project was funded by multiple grants from the US National Science Foundation. 1 Overview The learning objective of this lab is for students to understand how environment variables affect program and system behaviors. Environment variables are a set of dynamic named values that can affect the way running processes will behave on a computer. They are used by most operating systems, since they were introduced to Unix in 1979. Although environment variables affect program behaviors, how they achieve that is not well understood by many programmers. As a result, if a program uses environment variables, but the programmer does not know that they are used, the program may have vulnerabilities. In this lab, students will understand how environment variables work, how they are propagated from parent process to child, and how they affect system/program behaviors. We are particularly interested in how environment variables affect the behavior of Set-UID programs, which are usually privileged programs. This lab covers the following topics: • Environment variables • Set-UID programs • Securely invoke external programs • Capability leaking • Dynamic loader/linker Readings and videos. Detailed coverage of the Set-UID mechanism, environment variables, and their related security problems can be found in the following: • Chapters 1 and 2 of the SEED Book, Computer & Internet Security: A Hands-on Approach, 2nd Edition, by Wenliang Du.
    [Show full text]
  • 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.
    [Show full text]
  • Virtualfish Documentation
    virtualfish Documentation Release 1.0.7.dev0+g64f7675.d20200320 Adam Brenecki and contributors Mar 20, 2020 Contents 1 Contents 3 1.1 Installation and Setup..........................................3 1.2 Usage...................................................4 1.3 Plugins..................................................5 1.4 Extending Virtualfish...........................................8 1.5 Frequently Asked Questions.......................................9 1.6 See Also.................................................9 2 Contributors 11 i ii virtualfish Documentation, Release 1.0.7.dev0+g64f7675.d20200320 A Fish Shell wrapper for Ian Bicking’s virtualenv, somewhat loosely based on Doug Hellman’s virtualenvwrapper for Bourne-compatible shells. Contents 1 virtualfish Documentation, Release 1.0.7.dev0+g64f7675.d20200320 2 Contents CHAPTER 1 Contents 1.1 Installation and Setup 1.1.1 Installing 1. Make sure you’re running Fish 2.x. If you’re running an Ubuntu LTS release that has an older Fish version, install Fish 2.x via the fish-shell/release-2 PPA. 2. Install virtualfish by running pip install virtualfish. 3. Add the following to your ~/.config/fish/config.fish: eval (python-m virtualfish) If you want to use virtualfish with plugins, list the names of the plugins as arguments to the virtualfish loader: eval (python-m virtualfish compat_aliases) Note: If your config.fish modifies your $PATH, you should ensure that you load virtualfish after those modifications. 4. Customize your fish_prompt 1.1.2 Customizing Your fish_prompt virtualfish doesn’t
    [Show full text]
  • A Simple Implementation of Name Spaces for R
    A Simple Implementation of Name Spaces for R Luke Tierney Department of Statistics and Actuarial Science University of Iowa May 29, 2003 1 Introduction This document presents the implementation of name space support provided in R 1.7. Some minor changes in the current development verison have also been incorporated. A pdf version1 of this document is also available. Name spaces provide a means for packages to control the way global variables in their function defini- tions are resolved and to control which local definitions are to be available outside the package. Packages with name spaces export variables with certain values. A package with a name space can import variables exported by other packages with name spaces. Functions defined within a name space are defined in an en- vironment consisting of the internal name space frame, which is enclosed in a (set of) imported frames.2 All name spaces import the base name space. The base name space is a special name space that is enclosed by the global environment. For example, a function defined in a name space bar that imports foo will be defined in an environment that looks like this: --------------- | bar internals | --------------- | foo exports | --------------- | base exports | --------------- | .GlobalEnv | --------------- | package:pkg1 | --------------- ... --------------- | package:base | --------------- The variables in base appear twice: once as a statically determined import (static in the sense that its position in the environment is fixed) and once at the end of the dynamic global environment (where the search index of base varies as packages are attached and detached).3 1See URL morenames.pdf. 2The implementation fuses all explicit imports into a single frame.
    [Show full text]
  • CPSA+Maude+PDA + PVS
    CPSA+Maude+PDA + PVS Carolyn Talcott & Sam Owre SRI International with help from Shaddin, Dusko, and Matthias and others Protocol exchange, June 2005 Plan • Viewing CPSA skeletons • PVS formalization Maude Display skeletons • Execution of PDA Ground execution of scenarios and attacks Protocols Symbolic execution processes Skeletons Protocols using homomorphisms Processes and inference rules .... CPSA Define protocol PDA Create role Derive protocol Verification and properties Discover conditions ... Compose/Refine ... PVS Formal model Verify theorems Certify claims ... CSPA-Maude Viewing CPSA Skeletons • CPSA -> Maude -> JLambda • String -> Sexp -> Strand exp -> JLambda exp • Two tricks to printing: • ordering columns • spacing rows Sexpression external form (skeleton (identifiers (id original (sid resp 1))) (strands (strand (sid resp 1) (messages (sm - (conc (name A) (nonce Na))) ... ) )) (non (ltk (name B) (name S)) (ltk (name A) (name S))) (uniq (nonce Nb)) (order) (safe)) Converting to Strand Exp <Skeleton> := (skeleton <IdentifierSet> <StrandSet> <Non><Uniq> <EdgeSet> <Safe>) op sexp2skeleton : Sexp -> Skeleton . ceq sexp2skeleton( [a("skeleton") [a("identifiers") idsexpl] [a("strands") ssexpl] .... [a("safe") sasexpl]]) = cpsa-skel(ids,ss,non,uniq,es,safe) if ids := sexpl2ids(idsexpl) /\ ss := sexpl2strands(ssexpl) ... Ordering Columns • For each permutation of strands sum crossings of strands between source and target of each edge • Pick a permutation with the fewest crossings Spacing Rows: Setting up Constraints Assume a skeleton
    [Show full text]
  • BCP – SRTP Configuration and Troubleshooting Guidelines for Oracle Enterprise SBC
    BCP – SRTP Configuration and Troubleshooting Guidelines for Oracle Enterprise SBC Revision History Version Author Description of Changes Date Revision Completed 520-0043-00 Antonio Merenciano Initial Release Oct 21st,2010 520-0043-01 Anima Khindari Added ETC NIU support July 27th, 2011 information 520-0043-02 Bhaskar Reddy Gaddam Rebranded with latest release July 12th , 2018 information 520-0043-02 Priyesh Mehrotra Rebranded with latest release July 16th 2020 information.IPSec configuraton removed. Copyright © 2013, 2020, Oracle and/or its affiliates. All rights reserved.. Status of this memo Oracle SBC Best Current Practices are working documents of the Professional Services department of Oracle Corporation. Note that other groups may also distribute working documents as Best Current Practices. Best Current Practices are working documents valid until explicitly obsoleted, and may be updated, replaced or obsoleted by other documents at any time. It is recommended to use Best Current Practices as reference material as well as to cite them in other works in progress. Abstract The use of the RFC 2119 keywords is an attempt to assign the correct requirement levels ("MUST", "SHOULD", "MAY", etc.). This document defines a series of recommendations for Secure Real-time Transport Protocol (SRTP) configuration and troubleshooting on the Oracle SBC in a customer’s production network. They should be used when either (a) deploying a new SBC, or (b) updating an existing configuration made before Best Current Practices were in place. When in conflict with Customer requirements or desires, the Customer’s preference SHOULD take precedence. Applicability This document is applicable to Oracle Enterprise Session Border Controller Release S-Cz8.4.0 Best Current Practice SRTP Configuration and Troubleshooting Guidelines July 2020 Table of Contents 1 Introduction .....................................................................................................................................................
    [Show full text]
  • Gnu Coreutils Core GNU Utilities for Version 6.9, 22 March 2007
    gnu Coreutils Core GNU utilities for version 6.9, 22 March 2007 David MacKenzie et al. This manual documents version 6.9 of the gnu core utilities, including the standard pro- grams for text and file manipulation. Copyright c 1994, 1995, 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc. 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; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". Chapter 1: Introduction 1 1 Introduction This manual is a work in progress: many sections make no attempt to explain basic concepts in a way suitable for novices. Thus, if you are interested, please get involved in improving this manual. The entire gnu community will benefit. The gnu utilities documented here are mostly compatible with the POSIX standard. Please report bugs to [email protected]. Remember to include the version number, machine architecture, input files, and any other information needed to reproduce the bug: your input, what you expected, what you got, and why it is wrong. Diffs are welcome, but please include a description of the problem as well, since this is sometimes difficult to infer. See section \Bugs" in Using and Porting GNU CC. This manual was originally derived from the Unix man pages in the distributions, which were written by David MacKenzie and updated by Jim Meyering.
    [Show full text]
  • UNIX Reference Card Create a Directory Called Options: -I Interactive Mode
    File System Manipulation Move (Rename) Files and Directories mv present-filename new-filename to rename a file Create (or Make) a Directory mv source-filename destination-directory to move a file into another directory mkdir directory-name directory-name UNIX Reference Card create a directory called options: -i interactive mode. Must confirm file overwrites. Anatomy of a Unix Command Look at a File Copy Files more filename man display file contents, same navigation as cp source-filename destination-filename to copy a file into command-name -option(s) filename(s) or arguments head filename display first ten lines of a file another file tail filename display last ten lines of a file Example: wc -l sample cp source-filename destination-directory to copy a file into another directory : options options: The first word of the command line is usually the command name. This -# replace # with a number to specify how many lines to show is followed by the options, if any, then the filenames, directory name, or -i interactive mode. Must confirm overwrites. Note: this other arguments, if any, and then a RETURN. Options are usually pre- option is automatically used on all IT’s systems. -R recursive delete ceded by a dash and you may use more than one option per command. List Files and Directories The examples on this reference card use bold case for command names Remove (Delete) Files and Directories and options and italics for arguments and filenames. ls lists contents of current directory ls directory-name list contents of directory rm filename to remove a file rmdir directory-name to remove an Important Note about UNIX Commands empty directory : options options: -a list all files including files that start with “.” UNIX commands are case sensitive.
    [Show full text]
  • UNIX System Commands for Nuclear Magnetic Resonance(NMR)
    8/25/00 11:41 AM UNIX System Commands For Nuclear Magnetic Resonance(NMR) EMORY Dr. Shaoxiong Wu NMR Research Center at Emory 1996 /xiong/UNIX.doc September 25, 1996 Dr. Shaoxiong Wu The information in this document is based on my own experiences. It has been carefully checked. However, no responsibility is assumed if any one copied this document as their reference. UNIX Commands 10/05/96 12:50 PM Updated Commands for tape operation: Tape Utility %mt -f /dev/rst0 retention (rewind)* Tape Copy %tcopy /dev/rst0 /dev/rst1 rst0-source rst1 --target Tape Dump #/usr/etc/dump 0cdstfu 1000 700 18 /dev/rst0 /dev/sd3c (/dev/sd0a;/dev/sd0g) 150Mb tape This dump can be recovered by mini root!!!! #dump 0cdstfu 1000 425 9 /dev/rst0 /dev/rsd0a On Omega600 (60Mb tape) Recover some files from the dump tape #restore -i restore>ls List files on the tape restore>add file name restore>extract you may extract file into a temp.dir first Tape Backup #../tar cvf /dev/rst0 dir-to-be-backup #../tar tvf /dev/rst0 ---list file on the tape #../tar xvfp /dev/rst0 ./restoredir (current dir) DATA Compression and Tape Backup #tar cf directoryname.tar directoryname ------compress all files in the directoryname #rm -r directoryname #compress directoryname.tar -------a new file name will be -------.tar.Z #tar cvf /dev/rst0 -----tar.Z ------save the file on a tape *******Retrieve the files #tar xvf /dev/rst0 ------tar.Z #uncompress ------tar.Z -----a new file will appear -----.tar 1 /xiong/UNIX.doc September 25, 1996 Dr.
    [Show full text]