Projects on the Move
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Arxiv:Cs/0107036V2 [Cs.SC] 31 Jul 2001
TEXmacs interfaces to Maxima, MuPAD and REDUCE A. G. Grozin Budker Institute of Nuclear Physics, Novosibirsk 630090, Russia [email protected] Abstract GNU TEXmacs is a free wysiwyg word processor providing an excellent typesetting quality of texts and formulae. It can also be used as an interface to Computer Algebra Systems (CASs). In the present work, interfaces to three general-purpose CASs have been implemented. 1 TEXmacs GNU TEXmacs [1] is a free (GPL) word processor which typesets texts and mathematical formulae with very high quality (like LAT X), • E emphasizes the logical structure of a document rather than its appearance (like • LATEX), is easy to use and intuitive (like typical wysiwyg word processors), • arXiv:cs/0107036v2 [cs.SC] 31 Jul 2001 can be extended by a powerful programming language (like Emacs), • can include PostScript figures (as well as other figures which can be converted • to PostScript), can export LAT X, and import LAT X and html, • E E supports a number of languages based on Latin and Cyrillic alphabets. • It uses TEX fonts both on screen and when printing documents. Therefore, it is truly wysiwyg, with equally good quality of on-screen and printed documents (in contrast to LyX which uses X fonts on screen and calls LATEX for printing). There is a similar commercial program called Scientific Workplace (for Windows). TEXmacs can also be used as an interface to any CAS which can generate LATEX output. It renders LATEX formulae on the fly, producing CAS output with highest 1 typesetting quality (better than, e.g., Mathematica, which uses fixed-width fonts for formula output). -
Building a Reliable Storage Stack
Building a Reliable Storage Stack Ph.D. Thesis David Cornelis van Moolenbroek Vrije Universiteit Amsterdam, 2016 This work was supported by the European Research Council Advanced Grant 227874. This work was carried out in the ASCI graduate school. ASCI dissertation series number 355. Copyright © 2016 by David Cornelis van Moolenbroek. ISBN 978-94-028-0240-5 Cover design by Eva Dienske. Printed by Ipskamp Printing. VRIJE UNIVERSITEIT Building a Reliable Storage Stack ACADEMISCH PROEFSCHRIFT ter verkrijging van de graad Doctor aan de Vrije Universiteit Amsterdam, op gezag van de rector magnificus prof.dr. V. Subramaniam, in het openbaar te verdedigen ten overstaan van de promotiecommissie van de Faculteit der Exacte Wetenschappen op maandag 12 september 2016 om 11.45 uur in de aula van de universiteit, De Boelelaan 1105 door David Cornelis van Moolenbroek geboren te Amsterdam promotor: prof.dr. A.S. Tanenbaum To my parents Acknowledgments This book marks the end of both a professional and a personal journey–one that has been long but rewarding. There are several people whom I would like to thank for accompanying and helping me along the way. First and foremost, I would like to thank my promotor, Andy Tanenbaum. While I was finishing up my master project under his supervision, he casually asked me “Would you like to be my Ph.D student?” during one of our meetings. I did not have to think long about the answer. Right from the start, he warned me that I would now have to conduct original research myself; only much later did I understand the full weight of this statement. -
AMNESIA 33: How TCP/IP Stacks Breed Critical Vulnerabilities in Iot
AMNESIA:33 | RESEARCH REPORT How TCP/IP Stacks Breed Critical Vulnerabilities in IoT, OT and IT Devices Published by Forescout Research Labs Written by Daniel dos Santos, Stanislav Dashevskyi, Jos Wetzels and Amine Amri RESEARCH REPORT | AMNESIA:33 Contents 1. Executive summary 4 2. About Project Memoria 5 3. AMNESIA:33 – a security analysis of open source TCP/IP stacks 7 3.1. Why focus on open source TCP/IP stacks? 7 3.2. Which open source stacks, exactly? 7 3.3. 33 new findings 9 4. A comparison with similar studies 14 4.1. Which components are typically flawed? 16 4.2. What are the most common vulnerability types? 17 4.3. Common anti-patterns 22 4.4. What about exploitability? 29 4.5. What is the actual danger? 32 5. Estimating the reach of AMNESIA:33 34 5.1. Where you can see AMNESIA:33 – the modern supply chain 34 5.2. The challenge – identifying and patching affected devices 36 5.3. Facing the challenge – estimating numbers 37 5.3.1. How many vendors 39 5.3.2. What device types 39 5.3.3. How many device units 40 6. An attack scenario 41 6.1. Other possible attack scenarios 44 7. Effective IoT risk mitigation 45 8. Conclusion 46 FORESCOUT RESEARCH LABS RESEARCH REPORT | AMNESIA:33 A note on vulnerability disclosure We would like to thank the CERT Coordination Center, the ICS-CERT, the German Federal Office for Information Security (BSI) and the JPCERT Coordination Center for their help in coordinating the disclosure of the AMNESIA:33 vulnerabilities. -
Free Software Philosophy, History and Practice
Introduction (and some quick reminders) History and philosophy Legal aspects Free Software Philosophy, history and practice Luca Saiu [email protected] http://ageinghacker.net GNU Project Screencast version Paris, October 2014 Luca Saiu <[email protected]> Free Software — Philosophy, history and practice Introduction (and some quick reminders) History and philosophy Legal aspects Introducing myself I’m a computer scientist living and working somewhere around Paris... ...and a GNU maintainer. I’m also an associate member of the Free Software Foundation, a fellow of the Free Software Foundation Europe and an April adherent. So I’m not an impartial observer. Luca Saiu <[email protected]> Free Software — Philosophy, history and practice Introduction (and some quick reminders) History and philosophy Legal aspects Contents 1 Introduction (and some quick reminders) 2 History and philosophy The hacker community The GNU Project and the Free Software movement Linux and the Open Source movement 3 Legal aspects Copyright Free Software licenses Luca Saiu <[email protected]> Free Software — Philosophy, history and practice Introduction (and some quick reminders) History and philosophy Legal aspects Reminders about software — source code vs. machine code Source code vs. machine code Quick demo Luca Saiu <[email protected]> Free Software — Philosophy, history and practice Programs are linked to libraries static libraries shared libraries Libraries (or programs) request services to the kernel Programs invoke with other programs Programs communicate with other programs... ...on the same machine ...over the network We’re gonna see that this has legal implications. Introduction (and some quick reminders) History and philosophy Legal aspects Reminders about software — linking In practice, programs don’t exist in isolation. -
El Manual De GNU TEXMACS
El manual de GNU TEXMACS Índice 1. Iniciar . 9 1.1. Convenciones para este manual . 9 1.2. Congurar TEXMACS . 9 1.3. Crear, guardar y cargar documentos . 10 1.4. Imprimir documentos . 10 2. Escribir documentos sencillos . 11 2.1. Generalidades para teclear de texto . 11 2.2. Tecleando texto estructurado . 11 2.3. Etiquetas basadas en contenido . 12 2.4. Listas . 12 2.5. Entornos . 13 2.6. Aspectos de presentación . 14 2.7. El sistema de selección de fuentes . 14 2.8. Dominando el teclado . 15 2.8.1. Reglas generales de prejos . 15 2.8.2. Algunos atajos de teclado fundamentales . 15 2.8.3. Atajos de teclado para el modo texto . 16 2.8.4. Comandos híbridos y simulación LATEX . 16 2.8.5. Objetos dinámicos . 16 2.8.6. Personalización del teclado . 17 3. Fórmulas matemáticas . 19 3.1. Principales constructos matemáticos . 19 3.2. Tecleando símbolos matemáticos . 20 3.3. Tecleando operadores grandes . 20 3.4. Teclear delimitadores grandes . 21 3.5. Acentos matemáticos anchos . 22 4. Material tabular . 23 4.1. Creando tablas . 23 4.2. El modo para dar formato . 23 4.3. Especicando el alineamiento de la celda y la tabla . 24 4.4. Especicando el tamaño de la celda y la tabla . 24 4.5. Bordes, acolchado y color de fondo . 25 4.6. Características avanzadas de la tabla . 25 5. Links and automatically generated content . 27 5.1. Creating labels, links and references . 27 5.2. Inserting images . 27 5.3. Generating a table of contents . 28 5.4. -
Software Livre Para Engenharia
SSOOFFTTWWAARREE LLIIVVRREE PPAARRAA EENNGENHGENHAARRIAIA AdAdiillssoonn JJ.. ddee AsAsssiiss [email protected] I Semana Acadêmica da UFU 28 de maio de 2004 Universidade Federal de Uberlândia Faculdade de Engenharia Química Núcleo de Modelagem, Controle e Otimização de Processos TERMINTERMINOOLLOOGGIAIA Software em Domínio Público Software em domínio público é software sem copyright. Alguns tipos de cópia, ou versões modificadas, podem não ser livres porque o autor permite que restrições adicionais sejam impostas na redistribuição do original ou de trabalhos derivados. Software Semi-livre Software semi-livre é software que não é livre, mas é concedida a permissão para que indivíduos o usem, copiem, distribuam e modifiquem, incluindo a distribuição de versões modificadas, desde que o façam sem o propósito de auferir lucros. Exemplos de software semi-livre são as primeiras versões do Internet Explorer da Microsoft, algumas versões dos browsers da Netscape, e o StarOffice. Softw are liv re p ara engenha ria I Sem ana Acadêm ica da UFU TERMINTERMINOOLLOOGGIAIA Freeware O termo freeware não possui uma definição amplamente aceita mas é usado com programas que permitem a redistribuição mas não a modificação, e seu código fonte não é disponibilizado. Estes programas não são software livre. Shareware Shareware é o software disponibilizado com a permissão para que seja redistribuído, mas a sua utilização implica no pagamento pela sua licença. Geralmente, o código fonte não é disponibilizado e portanto modificações são impossíveis. Softw are liv re p ara engenha ria I Sem ana Acadêm ica da UFU TERMINTERMINOOLLOOGGIAIA Software Proprietário Software proprietário é aquele cuja cópia, redistribuição ou modificação são em alguma medida proibidos pelo seu proprietário. -
Conservative Conversion Between and Texmacs
Conservative conversion between A L TEX and TEXMACS by Joris van der Hoevena, François Poulainb LIX, CNRS École polytechnique 91128 Palaiseau Cedex France a. Email: [email protected] b. Email: [email protected] April 15, 2014 Abstract Back and forth converters between two document formats are said to be conservative if the following holds: given a source document D, its conversion D0, a locally modied version M 0 of D0 and the back con- version M of M 0, the document M is a locally modied version of D. We will describe mechanisms for the implementation of such converters, A with the L TEX and TEXMACS formats as our guiding example. Keywords: Conservative document conversion, LATEX conversion, TEXMACS, mathematical editing A.M.S. subject classication: 68U15, 68U35, 68N99 1 Introduction The TEXMACS project [7, 10] aims at creating a free scientic oce suite with an integrated structured mathematical text editor [8], tools for graphical drawings and presentations, a spreadsheed, interfaces to various computer algebra sys- tems, and so on. Although TEXMACS aims at a typesetting quality which is at least as good as TEX and LATEX [14, 15], the system is not based on these latter systems. In particular, a new incremental typesetting engine was implemented from scratch, which allows documents to be edited in a wysiwyg and thereby more user friendly manner. This design choice made it also possible or at least easier to use TEXMACS as an interface for external systems, or as an editor for technical drawings. However, unlike existing graphical front-ends for LATEX such as LyX [2] or Scientific Workplace [23], native compatibility with LATEX is not ensured. -
The Flask Security Architecture: System Support for Diverse Security Policies
The Flask Security Architecture: System Support for Diverse Security Policies Ray Spencer Secure Computing Corporation Stephen Smalley, Peter Loscocco National Security Agency Mike Hibler, David Andersen, Jay Lepreau University of Utah http://www.cs.utah.edu/flux/flask/ Abstract and even many types of policies [1, 43, 48]. To be gen- erally acceptable, any computer security solution must Operating systems must be flexible in their support be flexible enough to support this wide range of security for security policies, providing sufficient mechanisms for policies. Even in the distributed environments of today, supporting the wide variety of real-world security poli- this policy flexibility must be supported by the security cies. Such flexibility requires controlling the propaga- mechanisms of the operating system [32]. tion of access rights, enforcing fine-grained access rights and supporting the revocation of previously granted ac- Supporting policy flexibility in the operating system is cess rights. Previous systems are lacking in at least one a hard problem that goes beyond just supporting multi- of these areas. In this paper we present an operating ple policies. The system must be capable of supporting system security architecture that solves these problems. fine-grained access controls on low-level objects used to Control over propagation is provided by ensuring that perform higher-level functions controlled by the secu- the security policy is consulted for every security deci- rity policy. Additionally, the system must ensure that sion. This control is achieved without significant perfor- the propagation of access rights is in accordance with mance degradation through the use of a security decision the security policy. -
Reactos-Devtutorial.Pdf
Developer Tutorials Developer Tutorials Next Developer Tutorials Table of Contents I. Newbie Developer 1. Introduction to ReactOS development 2. Where to get the latest ReactOS source, compilation tools and how to compile the source 3. Testing your compiled ReactOS code 4. Where to go from here (newbie developer) II. Centralized Source Code Repository 5. Introducing CVS 6. Downloading and configuring your CVS client 7. Checking out a new tree 8. Updating your tree with the latest code 9. Applying for write access 10. Submitting your code with CVS 11. Submitting a patch to the project III. Advanced Developer 12. CD Packaging Guide 13. ReactOS Architecture Whitepaper 14. ReactOS WINE Developer Guide IV. Bochs testing 15. Introducing Bochs 16. Downloading and Using Bochs with ReactOS 17. The compile, test and debug cycle under Bochs V. VMware Testing 18. Introducing VMware List of Tables 7.1. Modules http://reactos.com/rosdocs/tutorials/bk02.html (1 of 2) [3/18/2003 12:16:53 PM] Developer Tutorials Prev Up Next Chapter 8. Where to go from here Home Part I. Newbie Developer (newbie user) http://reactos.com/rosdocs/tutorials/bk02.html (2 of 2) [3/18/2003 12:16:53 PM] Part I. Newbie Developer Part I. Newbie Developer Prev Developer Tutorials Next Newbie Developer Table of Contents 1. Introduction to ReactOS development 2. Where to get the latest ReactOS source, compilation tools and how to compile the source 3. Testing your compiled ReactOS code 4. Where to go from here (newbie developer) Prev Up Next Developer Tutorials Home Chapter 1. Introduction to ReactOS development http://reactos.com/rosdocs/tutorials/bk02pt01.html [3/18/2003 12:16:54 PM] Chapter 1. -
AV Linux the Distro of Choice for Media Creators
DISTROHOPPER DISTROHOPPER Our pick of the latest releases will whet your appetite for new Linux distributions. ReactOS Like Windows, but open. K, this isn’t Linux – it’s not even based on Unix – but it is a free Ooperating system that you can try out. ReactOS is a clone of the Windows NT kernel used in Windows XP, and some of the API. This means that in theory, you should be able to use ReactOS just like a Windows system: install the same drivers, run the same software, etc. However, in practice, the implementation is not complete enough to allow you to do this. You can run the simple tools that come with the OS, but not much else. Wine offers a much better chance of being able to run Windows software without a full Windows install. Even though Wine and ReactOS share code, Wine has a much Don’t tell Linus we said this, but some games just don’t look right when running on Linux. better success rate. This is a shame, because if the team had Just because a project isn’t mainstream, Minesweeper, the game that killed millions of been able to create a fully working system that doesn’t mean it’s not interesting. man-hours worth of office-worker time in by the time Microsoft stopped support for Booting up ReactOS feels like taking a trip the last years of the previous millennium. Windows XP, they may have found many back in time – its visual style probably has Perhaps it’s not the best reason to get a new new users. -
Translate's Localization Guide
Translate’s Localization Guide Release 0.9.0 Translate Jun 26, 2020 Contents 1 Localisation Guide 1 2 Glossary 191 3 Language Information 195 i ii CHAPTER 1 Localisation Guide The general aim of this document is not to replace other well written works but to draw them together. So for instance the section on projects contains information that should help you get started and point you to the documents that are often hard to find. The section of translation should provide a general enough overview of common mistakes and pitfalls. We have found the localisation community very fragmented and hope that through this document we can bring people together and unify information that is out there but in many many different places. The one section that we feel is unique is the guide to developers – they make assumptions about localisation without fully understanding the implications, we complain but honestly there is not one place that can help give a developer and overview of what is needed from them, we hope that the developer section goes a long way to solving that issue. 1.1 Purpose The purpose of this document is to provide one reference for localisers. You will find lots of information on localising and packaging on the web but not a single resource that can guide you. Most of the information is also domain specific ie it addresses KDE, Mozilla, etc. We hope that this is more general. This document also goes beyond the technical aspects of localisation which seems to be the domain of other lo- calisation documents. -
Referência Debian I
Referência Debian i Referência Debian Osamu Aoki Referência Debian ii Copyright © 2013-2021 Osamu Aoki Esta Referência Debian (versão 2.85) (2021-09-17 09:11:56 UTC) pretende fornecer uma visão geral do sistema Debian como um guia do utilizador pós-instalação. Cobre muitos aspetos da administração do sistema através de exemplos shell-command para não programadores. Referência Debian iii COLLABORATORS TITLE : Referência Debian ACTION NAME DATE SIGNATURE WRITTEN BY Osamu Aoki 17 de setembro de 2021 REVISION HISTORY NUMBER DATE DESCRIPTION NAME Referência Debian iv Conteúdo 1 Manuais de GNU/Linux 1 1.1 Básico da consola ................................................... 1 1.1.1 A linha de comandos da shell ........................................ 1 1.1.2 The shell prompt under GUI ......................................... 2 1.1.3 A conta root .................................................. 2 1.1.4 A linha de comandos shell do root ...................................... 3 1.1.5 GUI de ferramentas de administração do sistema .............................. 3 1.1.6 Consolas virtuais ............................................... 3 1.1.7 Como abandonar a linha de comandos .................................... 3 1.1.8 Como desligar o sistema ........................................... 4 1.1.9 Recuperar uma consola sã .......................................... 4 1.1.10 Sugestões de pacotes adicionais para o novato ................................ 4 1.1.11 Uma conta de utilizador extra ........................................ 5 1.1.12 Configuração