DOCSLIB.ORG

Opensuse Slides

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Opensuse Slides Richard Brown MicroOS Desktop MicroOS Release Engineer The Road to Daily Driving [email protected] aka We Need YOUR HELP sysrich on Freenode.net @sysrich About Me ● ~15 years with openSUSE & other FOSS communities ● >7 years with SUSE ● Future !echnologies Team Member ● openSUSE MicroOS & $ubic Go To This Talk Too What’s the point of this talk? ● %ario has pro&en the MicroOS Des'top can be a “%aily Driver) *or him ● +e need to ma'e it a “Dai"y Driver) for e&eryone more people ● +e need your help to ma'e this happen What is MicroOS? Why is MicroOS? ● ,omputer-s are not just laptops/ des'tops/ and ser&ers any more. ● 0eople don-t e&en use laptops/ desktops and ser&ers the same way any more. IP Webcam Do you have an IP Webcam or similar IoT Device? Ever updated it? IP Webcam There are millions of these devices ● 78% of total detected malware activity is due to IoT botnets (2018) ● Failed update → Many, many unhappy customers O2 UK Network Outage 2019 ● Reliable Updates ● Automatic Recovery ● Outage can be very expensive ● Repair can be very time consuming The New World #oT "loud Single-purpose devices More Hardware is always are increasingly prolific just a Credit Card away eg! Raspberry Pis irtualisation "ontainers More Services = More VMs, Limits incompatibilities, not more physical isolates service problems hardware Regular Linux Isn’t Good Enough ● 1egular Distros are a"l like Swiss Army $nives ● 3ots o* Ser&ices & Features – 4ncreased chance of incompatibilities between ser&ices – 2 prob"em with service 2 can impact B, ,, D, etc MicroOS openSUSE MicroOS is a predictable & immutab"e. It cannot be altered during runtime. MicroOS is reliable with automated updates and automated reco&er from *au"ty updates. MicroOS is sma"l with only what is needed to run it-s “one job). Applications/Services are e7pected to be ,ontainerised or Sandbo7ed. MicroOS Architecture openSUSE MicroOS is a rolling release based on openSUSE Tumbleweed. MicroOS is who""y bui"t/ de&eloped, and tested as part o* the Tumbleweed re"ease process. Any test failure detected be*ore the release o* either Tumbleweed & MicroOS can pre&ent the release o* both distributions. What is the MicroOS Desktop? MicroOS Des'top is MicroOS where the )one job) is running as a %es'top. MicroOS Des'top provides only a minimal base system with a %es'top Environment and Basic Con*iguration Tools O839. 2"l Applications/ Browsers/ etc are provided by Flat0a's from FlatHub. Who is the MicroOS Desktop For? 4t is not for e&eryone. 9our Tumbleweed & Leap Des'tops are Safe :) 4t should be per*ect for lazy de&elopers/ who no longer want to mess around with their des'top and just )get stuff done)/ especially i* they de&elop around containers. 4t should also appeal to the same audience now more used to an iOS, Chromebook or Android?"i'e experience where the OS is static, automated & reliable and the Apps are the main thing the user cares about. MicroOS Desktop Goals MicroOS Des'top shou"d be reliable, predictable & immutable, .ust li'e regu"ar MicroOS. MicroOS Des'top shou"d be less customisable than regular openSUSE Tumb"eweed/Leap. MicroOS Des'top shou"d be sma""/ but not at the e7pense o* functiona"ity. Printing/ Gaming/ Media Production and much more should a"l wor'. MicroOS Des'top shou"d just wor' (out o* the bo7). MicroOS Desktop Status MicroOS Des'top shou"d be reliable, predictable & immutable, .ust li'e regu"ar MicroOS. MicroOS Des'top shou"d be less customisable than regular openSUSE Tumb"eweed/Leap. MicroOS Des'top shou"d be sma""/ but not at the e7pense o* functiona"ity. Printing/ Gaming/ Mu"ti#edia are a"l va"id use cases. MicroOS Des'top shou"d just wor' (out o* the bo7). Current Team Fabian Vogt – $%E B *&[email protected] Dario Fagio""i – @8OME – d*agiol"[email protected] ● Richard Brown– 1elEng B [email protected] Open Roles ● 233 OF !:E# ;< – @8OME/ KDE, RelEng al" need more help – openC2 Test writers needed – U46UD po"ish reEuired – #ar'eting & 2d&ocacy desperately wanted – Other %E’sF – 4* you have other ideas/ we want your he"p tooG Top Issues Generally ● 4mperfect “out of the bo7” e7perience – !oo much con*iguration reEuired/ eg adding *"athub config to *"atpa'/ no de*au"t *"atpa' apps ● No U4 *or Transactional?Updates – 0ac'age$it 4ntegration or a"ternati&e notification widget wou"d be rea""y nice ● 0ol$it Ru"es – ,urrent"y too many root password prompts/ such as *or shutdown ● No V#62pp"iance Images Top Issues in KDE ● %isco&er is unstable/ related to 0ackageKit?=ypper not being a&ailableF Top Issues in GNOME ● adwaita?icon?theme missing Hgood Ifirst time- contribution< ● 10#s stil" shown in gnome?software ● system mounts showing in nautilus ● Dock not popu"ated with 'ey tools Heg. gnome? software< Sway? ● @8O#E and $DE ma'e sense *or the IiOS/ 2ndroid/ ,hromeboo'-?li'e use?case ● (Some) De&e"opers may pre*er an e&en more trimmed down/ Window?manager? only experience. ● Should the MicroOS Des'top ha&e an openSUSEway *"a&our alsoF Just One Desktop? ● For the iOS/Android/Chromebook?"i'e users the choice of ($%E or @8OME) is a scary one ● MicroOS Des'top @8OME current"y has most active users & contributors ● Should we .ust *ocus on thatF ● 4* you strongly *ee" (8o) – then ,O8!RIBUTE ;< Key Packages ● patterns-microos in deve";'ubic – ,ontains the #icroOS Des'top Patterns ● https;66github.com/yast/s'e"cd-contro"?#icroOS – %e*ines system ro"es ● openSUSE?#icroOS in de&e";'ubic:images – %e*ines app"iance6OE#6se"*?insta""ing dis' images Contributing ● opensuse?'[email protected] – #ailing "ist ● K'ubic on irc.freenode.net – 41, ● openSUSE:Factory & de&el;'ubic on bui"d.opensuse.org – 5ui"d Service .
Load more

Recommended publications
  • Mysql and Linux/Unix Abstract
    MySQL and Linux/Unix Abstract This is the MySQL Linux extract from the MySQL 5.6 Reference Manual. For legal information, see the Legal Notices. For help with using MySQL, please visit the MySQL Forums, where you can discuss your issues with other MySQL users. Document generated on: 2021-09-23 (revision: 70881) Table of Contents Preface and Legal Notices ............................................................................................................ v 1 Installing MySQL on Unix/Linux Using Generic Binaries ............................................................... 1 2 Installing MySQL on Linux ......................................................................................................... 5 2.1 Installing MySQL on Linux Using the MySQL Yum Repository ........................................... 6 2.2 Replacing a Third-Party Distribution of MySQL Using the MySQL Yum Repository .............. 9 2.3 Installing MySQL on Linux Using the MySQL APT Repository ......................................... 11 2.4 Installing MySQL on Linux Using the MySQL SLES Repository ....................................... 11 2.5 Installing MySQL on Linux Using RPM Packages from Oracle ......................................... 12 2.6 Installing MySQL on Linux Using Debian Packages from Oracle ...................................... 15 2.7 Installing MySQL on Linux from the Native Software Repositories .................................... 16 2.8 Deploying MySQL on Linux with Docker .......................................................................
    [Show full text]
  • Red Hat Developer Toolset 9 User Guide
    Red Hat Developer Toolset 9 User Guide Installing and Using Red Hat Developer Toolset Last Updated: 2020-08-07 Red Hat Developer Toolset 9 User Guide Installing and Using Red Hat Developer Toolset Zuzana Zoubková Red Hat Customer Content Services Olga Tikhomirova Red Hat Customer Content Services [email protected] Supriya Takkhi Red Hat Customer Content Services Jaromír Hradílek Red Hat Customer Content Services Matt Newsome Red Hat Software Engineering Robert Krátký Red Hat Customer Content Services Vladimír Slávik Red Hat Customer Content Services Legal Notice Copyright © 2020 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp.
    [Show full text]
  • Chapter 7 Package Management
    Chapter 7 Package Management CERTIFICATION OBJECTIVES 7.01 The Red Hat Package Manager ✓ Two-Minute Drill 7.02 More RPM Commands Q&A Self Test 7.03 Dependencies and the yum Command 7.04 More Package Management Tools fter installation is complete, systems are secured, filesystems are configured, and other initial setup tasks are completed, you still have work to do. Almost certainly before your system is in the state you desire, you will be required to install or remove packages. To make sure the right updates are installed, you need to know how to get a system working with ARed Hat Subscription Management (RHSM) or the repository associated with a rebuild distribution. To accomplish these tasks, you need to understand how to use the rpm and yum commands in detail. Although these are “just” two commands, they are rich in detail. Entire books have been dedicated to the rpm command, such as the Red Hat RPM Guide by Eric 344 Chapter 7 Package Management Foster-Johnson. For many, that degree of in-depth knowledge of the rpm command is no longer necessary, given the capabilities of the yum command and the additional package management tools provided in RHEL 7. CERTIFICATION OBJECTIVE 7.01 The Red Hat Package Manager One of the major duties of a system administrator is software management. New applications are installed. Services are updated. Kernels are patched. Without the right tools, it can be difficult to figure out what software is on a system, what is the latest update, and what applications depend on other software.
    [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]
  • Install Gnome Software Center Arch
    Install gnome software center arch Upstream URL: License(s): GPL2. Maintainers: Jan Steffens. Package Size: MB. Installed Size: Installed Size​: ​ MB. gnome-software will be available as a preview in It can install, remove applications on systems with PackageKit. It can install updates on Gnome software will not start / Applications & Desktop. A quick video on Gnome Software Center in Arch Linux. Gnome unstable repository. There is a component called Polkit that is used by many applications to request root permissions to do things (it can do so because it's a. GNOME Software on #archlinux with native PackageKit backend, and this is a gui for installing software, ala ubuntu software manager, but distro This is some kind of Ubuntu Software Centre, with comments and all that. Need help installing Gnome Software Center for Arch Linux? Here are some instructions: Click DOWNLOAD HERE in the menu. Download the file. Make the file. I had to install it with along with packagekit. This is what's missing to make Antergos *the* beginner-friendly Arch-based distro, or general So, it is not a bad idea for the “Gnome Software Center” to include by default. GNOME software software center graphic that we will find the default in future releases of Fedora in addition to being installed in Arch Linux Please help me to install GNOME Software on. GNOME Software Will Work On Arch Linux With PackageKit the Alpm/Pacman back-end for using this GNOME application to install and. From: Sriram Ramkrishna ; To: desktop-devel-list devel-list gnome org>; Subject: gnome- software/packagekit.
    [Show full text]
  • Opensuse Leap 15.3 Start-Up Start-Up Opensuse Leap 15.3
    openSUSE Leap 15.3 Start-Up Start-Up openSUSE Leap 15.3 Publication Date: June 22, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About this guide xi 1 Available documentation xi 2 Improving the documentation xii 3 Documentation conventions xiii 4 Source code xiv 5 Acknowledgments xiv I INSTALLATION 1 1 Installation Quick Start 2 1.1 Welcome to openSUSE Leap 2 Minimum system requirements 2 • Installing openSUSE Leap 2 2 Boot parameters 17 2.1 Using the default boot parameters 17 2.2 PC (AMD64/Intel 64/Arm AArch64) 17 The boot screen on machines equipped with traditional
    [Show full text]
  • Linux Package Management
    Welcome A Basic Overview and Introduction to Linux Package Management By Stan Reichardt [email protected] October 2009 Disclaimer ● ...like a locomotive ● Many (similar but different) ● Fast moving ● Complex parts ● Another one coming any minute ● I have ridden locomotives ● I am NOT a locomotive engineer 2 Begin The Train Wreck 3 Definitions ● A file archiver is a computer program that combines a number of files together into one archive file, or a series of archive files, for easier transportation or storage. ● Metadata is data (or information) about other data (or information). 4 File Archivers Front Ends Base Package Tool CLI GUI tar .tar, tar tar file roller .tar.gz, .tgz, .tar.Z, .taz, .tar.bz2,.tbz2, .tbz, .tb2, .tar.lzma,.tlz, .tar.xz, .txz, .tz zip .zip zip zip file roller gzip gzip gunzip gunzip ● Archive file http://en.wikipedia.org/wiki/Archive_file ● Comparison of file archivers http://en.wikipedia.org/wiki/Comparison_of_file_archivers 5 tar ● These files end with .tar suffix. ● Compressed tar files end with “.t” variations: .tar.gz, .tgz, .tar.Z, .taz, .tar.bz2, .tbz2, .tbz, .tb2, .tar.lzma, .tlz, .tar.xz, .txz, .tz ● Originally intended for transferring files to and from tape, it is still used on disk-based storage to combine files before they are compressed. ● tar (file format) http://en.wikipedia.org/wiki/.tar 6 tarball ● A tar file or compressed tar file is commonly referred to as a tarball. ● The "tarball" format combines tar archives with a file-based compression scheme (usually gzip). ● Commonly used for source and binary distribution on Unix-like platforms, widely available elsewhere.
    [Show full text]
  • RPM Packages
    RPM Packaging Guide Adam Miller, Maxim Svistunov, Marie Doleželová, et al. Table of Contents Introduction. 1 PDF Version . 1 Document Conventions. 1 Contributing to this guide . 2 Prerequisites . 3 Why Package Software with RPM?. 4 Your First RPM Package . 5 Preparing Software for Packaging . 7 What is Source Code? . 7 How Programs Are Made . 8 Natively Compiled Code . 8 Interpreted Code . 8 Building Software from Source . 9 Natively Compiled Code . 9 Interpreted Code . 10 Patching Software . 12 Installing Arbitrary Artifacts. 14 Using the install command . 14 Using the make install command . 15 Preparing Source Code for Packaging. 16 Putting Source Code into Tarball . 16 bello . 17 pello . 17 cello. 18 Packaging Software . 20 RPM Packages . 20 What is an RPM? . 20 RPM Packaging Tools . 20 RPM Packaging Workspace . 21 What is a SPEC File? . 21 BuildRoots . 23 RPM Macros . 24 Working with SPEC files. 25 Building RPMS . 44 Source RPMs . 45 Binary RPMS . 45 Checking RPMs For Sanity . 47 Checking the bello SPEC File. 47 Checking the bello Binary RPM . 48 Checking the pello SPEC File. 48 Checking the pello Binary RPM . 49 Checking the cello SPEC File . 50 Checking the cello Binary RPM . 51 Advanced Topics. 52 Signing Packages . 52 Adding a Signature to a Package . 52 Replacing a Package Signature. 53 Build-time Signing. 54 Mock . 55 Version Control Systems. 59 tito . ..
    [Show full text]
  • Package Management Yum and Rpm
    Package Management yum and rpm Presented by Prabin Kumar Datta 4th Year 8th Semester, IT, GCECT Copyright (C) 2011 prabindatta GNU General Public License http://www.gnu.org/licenses/ PackageKit PackageKit, the default package manager front-end on Fedora PackageKit Front-ends: There are three front-ends for PackageKit: gnome-packagekit to be used in the GNOME desktop. kpackagekit to be used in the KDE desktop. pkcon to be used on the command line. PackageKit Back-ends There are number of back-ends for PackageKit. Few of them are: YUM Opkg Simple Package Manager Advanced Packaging Tool Yellowdog Updater Modified Yellowdog Updater Modified (YUM) is an open- source command-line package-management utility for RPM-compatible Linux operating systems Yum is System administration commands (usually only for root) RPM Package Manager RPM stand for Redhat Package Manager. Features of RPM include: RPM packages can be cryptographically verified with GPG and MD5 Original source archive(s) (e.g. .tar.gz, .tar.bz2) are included in SRPMs, making verification easier PatchRPMs, the RPM equivalent of a patch file, can incrementally update RPM-installed software Automatic build-time dependency evaluation. Few Commands Install packages: # rpm -ivh <package_name> The above command has inability to resolve dependencies. # yum install <package_name> The yum application can call upon several repositories for dependency resolution. Few Commands Install packages: (continue) # yum localinstall <rpmfile> This command will install the local rpm file and also search for
    [Show full text]
  • Ubuntu 20.04 Essentials Ubuntu 20.04 Essentials ISBN-13: 978-1-951442-05-7 © 2020 Neil Smyth / Payload Media, Inc
    Contents 1. 1. Introduction 1. 1.1 Superuser Conventions 2. 1.2 Opening a Terminal Window 3. 1.3 Editing Files 4. 1.4 Feedback 5. 1.5 Errata 2. 2. A Brief History of Linux 1. 2.1 What exactly is Linux? 2. 2.2 UNIX Origins 3. 2.3 Who Created Linux? 4. 2.4 The History of Ubuntu 5. 2.5 What does the word “Ubuntu” Mean? 6. 2.6 Summary 3. 3. Installing Ubuntu on a Clean Disk Drive 1. 3.1 Ubuntu Installation Options 2. 3.2 Server vs. Desktop Editions 3. 3.3 Obtaining the Ubuntu Installation Media 4. 3.4 Writing the ISO Installation Image to a USB Drive 1. 3.4.1 Linux 2. 3.4.2 macOS 3. 3.4.3 Windows 5. 3.5 Booting from the Ubuntu USB Image 6. 3.6 Installing Ubuntu 7. 3.7 Accessing the Ubuntu Desktop 8. 3.8 Installing Updates 9. 3.9 Displaying Boot Messages 10. 3.10 Summary 4. 4. Installing Ubuntu with the Network Installer 1. 4.1 Network Installer Advantages 2. 4.2 Obtaining the Network Installer Image 3. 4.3 Booting from the Installer Image 4. 4.4 Performing the Installation 5. 4.5 Disk Partitioning 6. 4.6 Software Collection Selection 7. 4.7 Installing Software Collections After System Setup 8. 4.8 Summary 5. 5. Dual Booting Ubuntu with Windows 1. 5.1 Beginning the Ubuntu Installation 2. 5.2 Booting Ubuntu for the First Time 3. 5.3 Changing the Default Boot Option 4. 5.4 Accessing the Windows Partition from the Command-line 5.
    [Show full text]
  • Red Hat Enterprise Linux 8 Using the Desktop Environment in RHEL 8
    Red Hat Enterprise Linux 8 Using the desktop environment in RHEL 8 Configuring and customizing the GNOME 3 desktop environment on RHEL 8 Last Updated: 2021-09-10 Red Hat Enterprise Linux 8 Using the desktop environment in RHEL 8 Configuring and customizing the GNOME 3 desktop environment on RHEL 8 Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent.
    [Show full text]
  • Practical Linux Forensics by Bruce Nikkel! As a Prepublication Title, This Book May Be Incom- Plete and Some Chapters May Not Have Been Proofread
    P R A C T I C A L LINUX FORENSICS A GUIDE FOR DIGITAL INVESTIGATORS BRUCE NIKKEL EARLY ACCESS NO STARCH PRESS EARLY ACCESS PROGRAM: FEEDBACK WELCOME! Welcome to the Early Access edition of the as yet unpublished Practical Linux Forensics by Bruce Nikkel! As a prepublication title, this book may be incom- plete and some chapters may not have been proofread. Our goal is always to make the best books possible, and we look forward to hearing your thoughts. If you have any comments or questions, email us at [email protected]. If you have specific feedback for us, please include the page number, book title, and edition date in your note, and we’ll be sure to review it. We appreciate your help and support! We’ll email you as new chapters become available. In the meantime, enjoy! PR CA T IC A L L INU X FOR E N SI C S BRUCE N IK KE L Early Access edition, 6/18/21 Copyright © 2021 by Bruce Nikkel. ISBN-13: 978-1-7185-0196-6 (print) ISBN-13: 978-1-7185-0197-3 (ebook) Publisher: William Pollock Production Manager: Rachel Monaghan Production Editor: Miles Bond Developmental Editor: Jill Franklin Cover Illustrator: James L. Barry Technical Reviewer: Don Frick Copyeditor: George Hale No Starch Press and the No Starch Press logo are registered trademarks of No Starch Press, Inc. Other product and company names mentioned herein may be the trademarks of their respective owners. Rather than use a trademark symbol with every occurrence of a trade- marked name, we are using the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark.
    [Show full text]