LATEX Installation Guide
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Command Line Interface Specification Windows
Command Line Interface Specification Windows Online Backup Client version 4.3.x 1. Introduction The CloudBackup Command Line Interface (CLI for short) makes it possible to access the CloudBackup Client software from the command line. The following actions are implemented: backup, delete, dir en restore. These actions are described in more detail in the following paragraphs. For all actions applies that a successful action is indicated by means of exit code 0. In all other cases a status code of 1 will be used. 2. Configuration The command line client needs a configuration file. This configuration file may have the same layout as the configuration file for the full CloudBackup client. This configuration file is expected to reside in one of the following folders: CLI installation location or the settings folder in the CLI installation location. The name of the configuration file must be: Settings.xml. Example: if the CLI is installed in C:\Windows\MyBackup\, the configuration file may be in one of the two following locations: C:\Windows\MyBackup\Settings.xml C:\Windows\MyBackup\Settings\Settings.xml If both are present, the first form has precedence. Also the customer needs to edit the CloudBackup.Console.exe.config file which is located in the program file directory and edit the following line: 1 <add key="SettingsFolder" value="%settingsfilelocation%" /> After making these changes the customer can use the CLI instruction to make backups and restore data. 2.1 Configuration Error Handling If an error is found in the configuration file, the command line client will issue an error message describing which value or setting or option is causing the error and terminate with an exit value of 1. -
Attacker Antics Illustrations of Ingenuity
ATTACKER ANTICS ILLUSTRATIONS OF INGENUITY Bart Inglot and Vincent Wong FIRST CONFERENCE 2018 2 Bart Inglot ◆ Principal Consultant at Mandiant ◆ Incident Responder ◆ Rock Climber ◆ Globetrotter ▶ From Poland but live in Singapore ▶ Spent 1 year in Brazil and 8 years in the UK ▶ Learning French… poor effort! ◆ Twitter: @bartinglot ©2018 FireEye | Private & Confidential 3 Vincent Wong ◆ Principal Consultant at Mandiant ◆ Incident Responder ◆ Baby Sitter ◆ 3 years in Singapore ◆ Grew up in Australia ©2018 FireEye | Private & Confidential 4 Disclosure Statement “ Case studies and examples are drawn from our experiences and activities working for a variety of customers, and do not represent our work for any one customer or set of customers. In many cases, facts have been changed to obscure the identity of our customers and individuals associated with our customers. ” ©2018 FireEye | Private & Confidential 5 Today’s Tales 1. AV Server Gone Bad 2. Stealing Secrets From An Air-Gapped Network 3. A Backdoor That Uses DNS for C2 4. Hidden Comment That Can Haunt You 5. A Little Known Persistence Technique 6. Securing Corporate Email is Tricky 7. Hiding in Plain Sight 8. Rewriting Import Table 9. Dastardly Diabolical Evil (aka DDE) ©2018 FireEye | Private & Confidential 6 AV SERVER GONE BAD Cobalt Strike, PowerShell & McAfee ePO (1/9) 7 AV Server Gone Bad – Background ◆ Attackers used Cobalt Strike (along with other malware) ◆ Easily recognisable IOCs when recorded by Windows Event Logs ▶ Random service name – also seen with Metasploit ▶ Base64-encoded script, “%COMSPEC%” and “powershell.exe” ▶ Decoding the script yields additional PowerShell script with a base64-encoded GZIP stream that in turn contained a base64-encoded Cobalt Strike “Beacon” payload. -
Powershell Integration with Vmware View 5.0
PowerShell Integration with VMware® View™ 5.0 TECHNICAL WHITE PAPER PowerShell Integration with VMware View 5.0 Table of Contents Introduction . 3 VMware View. 3 Windows PowerShell . 3 Architecture . 4 Cmdlet dll. 4 Communication with Broker . 4 VMware View PowerCLI Integration . 5 VMware View PowerCLI Prerequisites . 5 Using VMware View PowerCLI . 5 VMware View PowerCLI cmdlets . 6 vSphere PowerCLI Integration . 7 Examples of VMware View PowerCLI and VMware vSphere PowerCLI Integration . 7 Passing VMs from Get-VM to VMware View PowerCLI cmdlets . 7 Registering a vCenter Server . .. 7 Using Other VMware vSphere Objects . 7 Advanced Usage . 7 Integrating VMware View PowerCLI into Your Own Scripts . 8 Scheduling PowerShell Scripts . 8 Workflow with VMware View PowerCLI and VMware vSphere PowerCLI . 9 Sample Scripts . 10 Add or Remove Datastores in Automatic Pools . 10 Add or Remove Virtual Machines . 11 Inventory Path Manipulation . 15 Poll Pool Usage . 16 Basic Troubleshooting . 18 About the Authors . 18 TECHNICAL WHITE PAPER / 2 PowerShell Integration with VMware View 5.0 Introduction VMware View VMware® View™ is a best-in-class enterprise desktop virtualization platform. VMware View separates the personal desktop environment from the physical system by moving desktops to a datacenter, where users can access them using a client-server computing model. VMware View delivers a rich set of features required for any enterprise deployment by providing a robust platform for hosting virtual desktops from VMware vSphere™. Windows PowerShell Windows PowerShell is Microsoft’s command line shell and scripting language. PowerShell is built on the Microsoft .NET Framework and helps in system administration. By providing full access to COM (Component Object Model) and WMI (Windows Management Instrumentation), PowerShell enables administrators to perform administrative tasks on both local and remote Windows systems. -
Linux-PATH.Pdf
http://www.linfo.org/path_env_var.html PATH Definition PATH is an environmental variable in Linux and other Unix-like operating systems that tells the shell which directories to search for executable files (i.e., ready-to-run programs ) in response to commands issued by a user. It increases both the convenience and the safety of such operating systems and is widely considered to be the single most important environmental variable. Environmental variables are a class of variables (i.e., items whose values can be changed) that tell the shell how to behave as the user works at the command line (i.e., in a text-only mode) or with shell scripts (i.e., short programs written in a shell programming language). A shell is a program that provides the traditional, text-only user interface for Unix-like operating systems; its primary function is to read commands that are typed in at the command line and then execute (i.e., run) them. PATH (which is written with all upper case letters) should not be confused with the term path (lower case letters). The latter is a file's or directory's address on a filesystem (i.e., the hierarchy of directories and files that is used to organize information stored on a computer ). A relative path is an address relative to the current directory (i.e., the directory in which a user is currently working). An absolute path (also called a full path ) is an address relative to the root directory (i.e., the directory at the very top of the filesystem and which contains all other directories and files). -
Travels in TEX Land: Choosing a TEX Environment for Windows
The PracTEX Journal TPJ 2005 No 02, 2005-04-15 Rev. 2005-04-17 Travels in TEX Land: Choosing a TEX Environment for Windows David Walden The author of this column wanders through world of TEX, as a non-expert, reporting what he observes and learns, which hopefully will be interesting to other non-expert users of TEX. 1 Introduction This column recounts my experiences looking at and thinking about different ways TEX is set up for users to go through the document-composition to type- setting cycle (input and edit, compile, and view or print). First, I’ll describe my own experience randomly trying various TEX environments. I suspect that some other users have had a similar introduction to TEX; and perhaps other users have just used the environment that was available at their workplace or school. Then I’ll consider some categories for thinking about options in TEX setups. Last, I’ll suggest some follow-on steps. Since I use Microsoft Windows as my computer operating system, this note focuses on environments that are available for Windows.1 2 My random path to choosing a TEX environment 2 I started using TEX in the late 1990s. 1But see my offer in Section 4. 2 While I started using TEX, I switched from TEX to using LATEX as soon as I discovered LATEX existed. Since both TEX and LATEX are operated in the same way, I’ll mostly refer to TEX in this note, since that is the more basic system. c 2005 David C. Walden I don’t quite remember my first setup for trying TEX. -
Producing Beautiful Documents with TEX and LATEX an Extremely Brief Introduction
Producing Beautiful Documents With TEX and LATEX An Extremely Brief Introduction Lawrence Hubert University of Illinois Producing Beautiful Documents With TEX and LATEX – p. 1/37 What is TEX and LATEX? TEX is a very mathematically savvy typesetting engine produced in the 1980’s by Donald Knuth from Stanford. It is open-source (which means it is free, and freely available); implemented for every conceivable operating system; it is currently in Version 3.141592, so it is, in effect, now “fixed” forever. Extra Credit: can you tell why it is essentially “fixed”? And what will be the version number when Knuth dies? Producing Beautiful Documents With TEX and LATEX – p. 2/37 LATEX is a set of macros sitting on top of TEX that makes our task easier. It was produced by Leslie Lamport in the middle 1980’s; it is also open-source and delivered conjointly with any TEX system. The current version is LATEX2e and is under constant development and extension. TEX and LATEX work together, with LATEX helping produce what is called the document mark-up, and TEX then being called upon to do the actual typesetting. Producing Beautiful Documents With TEX and LATEX – p. 3/37 Features and Advantages Why you should use TEX and LATEX— In contrast to word-processing methods such as Word, you do not worry about the visual formatting of your document. You are concerned only about the content. In other words, you separate content from layout. The file you produce is ascii, the simplest you can have with no special symbols; it includes general commands for what you wish to do in the document. -
Miktex Manual Revision 2.0 (Miktex 2.0) December 2000
MiKTEX Manual Revision 2.0 (MiKTEX 2.0) December 2000 Christian Schenk <[email protected]> Copyright c 2000 Christian Schenk Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual 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 manual into another lan- guage, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Chapter 1: What is MiKTEX? 1 1 What is MiKTEX? 1.1 MiKTEX Features MiKTEX is a TEX distribution for Windows (95/98/NT/2000). Its main features include: • Native Windows implementation with support for long file names. • On-the-fly generation of missing fonts. • TDS (TEX directory structure) compliant. • Open Source. • Advanced TEX compiler features: -TEX can insert source file information (aka source specials) into the DVI file. This feature improves Editor/Previewer interaction. -TEX is able to read compressed (gzipped) input files. - The input encoding can be changed via TCX tables. • Previewer features: - Supports graphics (PostScript, BMP, WMF, TPIC, . .) - Supports colored text (through color specials) - Supports PostScript fonts - Supports TrueType fonts - Understands HyperTEX(html:) specials - Understands source (src:) specials - Customizable magnifying glasses • MiKTEX is network friendly: - integrates into a heterogeneous TEX environment - supports UNC file names - supports multiple TEXMF directory trees - uses a file name database for efficient file access - Setup Wizard can be run unattended The MiKTEX distribution consists of the following components: • TEX: The traditional TEX compiler. -
Tugboat, Volume 33 (2012), No. 1 53 TEX on Windows: Miktex Or TEX Live? Joseph Wright on Windows, There Are Two Actively-Develop
TUGboat, Volume 33 (2012), No. 1 53 TEX on Windows: MiKTEX or TEX Live? A reminder that MiKTEX and TEX Live are not the only choices. W32TEX (Kakuto, 2012) is popular Joseph Wright in the far east. As well as being a TEX system in On Windows, there are two actively-developed free its own right, it is the source of the Windows binar- TEX systems with similar coverage: MiKTEX (Schenk, ies for TEX Live, and TEX Live acquires more CJK 2011) and TEX Live (TEX Users Group, 2011). The support from it every year. For users focussed on good news is that there is a lot of similarity between ConTEXt, ConTEXt standalone (Pragma ADE, 2012) the two systems, so for most users both systems is probably the best way to go (it uses the W32TEX are equally usable, and (LA)TEX documents are port- binaries on Windows). There are also the commer- able between them. However, there are differences cial options, for example BaKoMa TEX (BaKoMa and depending on what you need these might be Soft., 2011) or PCTEX (Personal TEX, Inc., 2011). important. However, for most users it comes down to a choice between the ‘big two’. • The default settings install everything for TEX Live, but only a minimal set of packages for References MiKT X. MiKT X will then install extra pack- E E BaKoMa Soft. “BaKoMa T X 9.77”. ages ‘on the fly’, while T X Live does not (there E E http://www.bakoma-tex.com/, 2011. is a package to do that in TEX Live, but it is aimed at GNU/Linux users). -
Installation
APPENDIX A Installation In case you do not already have a LATEX installation, in Sections A.1 and A.2, we describe how to install LATEX on your computer, a PC or a Mac. The installation is much easier if you obtain TEX Live 2007 (or later) from the TEX Users Group, TUG (see Section E.2). It contains both the TEX implementations we discuss. No installation is given for UNIX computers. The attraction of UNIX to its users is the incredibly large number of options, from the UNIX dialect, to the shell, the editor, and so on. A typical UNIX user downloads the code and compiles the system. This is obviously beyond the scope of this book. Nevertheless, TEX Live 2007 (or later) from the TEX Users Group supplies the compiled (binaries) of LATEX for a number of UNIX variants. First read Chapter 1, so that in this Appendix you recognize the terminology we introduce there. I will assume that you become sufficiently familiar with your LATEX distribution to be able to perform the editing cycle with the sample documents. 490 Appendix A Installation A.1 LATEX on a PC On a PC, most mathematicians use MiKTeX and the editor WinEdt. So it seems appro- priate that we start there. A.1.1 Installing MiKTeX If you made a donation to MiKTeX or if you have the TEX Live 2007 (or later) from the TEX Users Group, then you have a CD or DVD with the MiKTeX installer. Installation then is in one step and very fast. In case you do not have this CD or DVD, we show how to install from the Internet. -
Path Howto Path Howto
PATH HOWTO PATH HOWTO Table of Contents PATH HOWTO..................................................................................................................................................1 Esa Turtiainen etu@dna.fi.......................................................................................................................1 1. Introduction..........................................................................................................................................1 2. Copyright.............................................................................................................................................1 3. General.................................................................................................................................................1 4. Init........................................................................................................................................................1 5. Login....................................................................................................................................................1 6. Shells....................................................................................................................................................1 7. Changing user ID.................................................................................................................................1 8. Network servers...................................................................................................................................1 -
PDF: Itransi-Miktex.Pdf
ITRANS53 Installation Notes with MiKTEX 2.9 John Washburn 20130701 MiKTEX is a distribution of LATEX for win32. It can be downloaded from http://miktex.org/2.9/setup. 1. Install the latest version of MiKTEX As of this writing the latest version of MiKTEX is 2.9. The default location into which MiKTEX is installed is: C:\Program Files\MiKTeX 2.9. If this is not the location to which you have installed MiKTEX then note the installation directory for use by the steps below. 2. Install all the font packages available through MiKTEX (a) Start ! MiKTEX ! MiKTEX Maintenance ! MiKTEX Maintenance Settings. (b) Select the Packages tab from the MiKTEX Options dialog box. (c) Check the checkbox: Fonts, until the box has a simple check with no background color. A simple check indicates all MiKTEX options within that category will be selected. Installing all the fonts will cause the outline font packages: indic-type1 and devangari, to be installed. 3. Download itrans53-win32.zip from http://www.aczoom.com/files/itrans/53/itrans53-win32.zip 4. Extract the contents of itrans53-win32.zip to some temporary location such as: c:\temp\itrans53 5. Create a file named install.bat file within the temporary location: c:\temp\itrans53 The contents of the install.bat batch file are listed below. If the installa- tion of MiKTEX was not to the directory: C:\Program Files\MiKTeX 2.9, then change the value of MiktexRoot to reflect the actual location of the MiKTEX installation. 6. Open an MS-DOS command window which is running as administator. -
LATEX3 News Issue 12, January 2020
LATEX3 News Issue 12, January 2020 Contents more stable: squeezing out more experimental ideas, refining ones we have and making it a serious option for Introduction 1 core LATEX programming. New features in expl3 1 As a result of these activities, the LATEX3 A new argument specifier: e-type . 1 programming layer will be available as part of the New functions . 1 kernel of LATEX 2" from 2020-02-02 onwards, i.e., can String conversion moves to expl3 . 1 be used without explicitly loading expl3. See LATEX Case changing of text . 2 News 31 [2] for more details on this. Notable fixes and changes 2 New features in expl3 File name parsing . 2 A new argument specifier: e-type Message formatting . 2 During 2018, the team worked with the TEX Live, Key inheritance . 2 X TE EX and (u)pTEX developers to add the \expanded Floating point juxtaposition . 2 primitive to pdfTEX, X TE EX and (u)pTEX. This Changing box dimensions . 2 primitive was originally suggested for pdfTEX v1.50 More functions moved to stable . 2 (never released), and was present in LuaTEX from the Deprecations . 2 start of that project. Adding lets us create a new argument Internal improvements 2 \expanded specifier: -type expansion. This is almost the same as Cross-module functions . 2 e -type, but is itself expandable. (It also doesn't need The backend . 2 x doubled # tokens.) That's incredibly useful for creating Better support for (u)pTEX 2 function-like macros: you can ensure that everything is expanded in an argument before you go near it, with Options 3 not an \expandafter in sight.