DOCSLIB.ORG

IBM AIX Enhancements and Modernization

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IBM AIX Enhancements and Modernization Front cover IBM AIX Enhancements and Modernization Navdeep Dhaliwal Ahmed Mashhour Armin Röll Liviu Rosca Redbooks IBM Redbooks IBM AIX Enhancements and Modernization January 2020 SG24-8453-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xv. First Edition (January 2020) This edition applies to AIX Version 7.2 Standard Edition (product number 5765-G98), AIX Version 7.2 Enterprise Edition (product number 5765-CD3), IBM PowerVM Version 3.1 Enterprise Edition (product number 5765-VE3), IBM PowerVC Version 1.4.3 Standard Edition (product number 5765-VCS), and IBM servers that are based on POWER9 processor-based technology. © Copyright International Business Machines Corporation 2020. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures . vii Tables . ix Examples . xi Notices . .xv Trademarks . xvi Preface . xvii Authors. xvii Now you can become a published author, too! . xviii Comments welcome. xviii Stay connected to IBM Redbooks . xix Chapter 1. General enhancements . 1 1.1 Live Update function . 2 1.1.1 Live Update concepts and procedure . 2 1.1.2 Live Update modes . 4 1.1.3 Live Update management types . 4 1.1.4 Live Update methods . 4 1.1.5 AIX Live Update integration with Power Enterprise Pools . 7 1.1.6 Live Update CPU resource reduction . 11 1.1.7 Live Update across frames . 15 1.1.8 Automount File System support with Live Update . 19 1.1.9 Kerberos authentication support in Live Update . 19 1.2 Server Flash Caching . 20 1.2.1 Flash caching concepts . 20 1.2.2 Implementation modes . 21 1.3 Multipath I/O . 23 1.3.1 AIX Path Control Module . 23 1.3.2 Subsystem Device Path Control Module. 29 1.4 iSCSI software initiator . 30 1.4.1 iSCSI overview . 30 1.4.2 Configuring the initiator . 30 1.5 Network Installation Manager . 34 1.5.1 Object classes. 34 1.5.2 HTTP service . 35 1.5.3 Live Update. 36 1.5.4 The nimadm support for MultiBOS environments . 42 1.6 Logical Volume Manager . 42 1.6.1 LVM mirroring to IBM FlashSystem for enhanced performance . 42 1.6.2 LVM reclamation support . 44 1.7 JFS2 . 45 1.7.1 JFS2 defragger . 45 1.7.2 Reclaiming JFS2 space . 46 1.8 Multiple alternative disk clones . 47 1.8.1 Cloning concepts . 47 1.9 Active Memory Expansion. 53 © Copyright IBM Corp. 2020. All rights reserved. iii 1.10 The nmon tool and current processor frequency reporting . 54 1.11 Globalization . 57 1.11.1 Unicode support . 57 1.11.2 Common Locale Data Repository updates . 59 1.11.3 International Components for Unicode for C. 60 1.12 AIX Toolbox for Linux Applications . 60 Chapter 2. Security enhancements . 63 2.1 AIX Trusted Execution . 64 2.2 AIX Secure boot . 68 2.2.1 PowerVM Secure Boot . 68 2.2.2 AIX Secure boot implementation . 69 2.2.3 AIX Secure boot policies and controls . 70 2.3 AIX trusted installation and update . 71 2.3.1 Digital signature and package signing . 72 2.3.2 AIX package signing and digital signature catalog definition . 73 2.3.3 AIX digital signature catalog signing process . 78 2.3.4 Signature validation during AIX installation and update process . 79 2.3.5 AIX trusted installation and update controls . 79 2.4 Multifactor authentication . 83 2.4.1 Authentication factors . 83 2.4.2 Authentication methods . 84 2.4.3 In-band MFA . 84 2.4.4 Out-of-band MFA . 85 2.4.5 Authentication on AIX systems by using RSA SecureID. 85 2.5 Cryptographic libraries . 87 2.5.1 OpenSSL . 87 2.5.2 CryptoLite for C library . 87 2.6 Address.
Load more

Recommended publications
  • IBM Power® Systems for SAS® Empowers Advanced Analytics Harry Seifert, Laurent Montaron, IBM Corporation
    Paper 4695-2020 IBM Power® Systems for SAS® Empowers Advanced Analytics Harry Seifert, Laurent Montaron, IBM Corporation ABSTRACT For over 40+ years of partnership between IBM and SAS®, clients have been benefiting from the added value brought by IBM’s infrastructure platforms to deploy SAS analytics, and now SAS Viya’s evolution of modern analytics. IBM Power® Systems and IBM Storage empower SAS environments with infrastructure that does not make tradeoffs among performance, cost, and reliability. The unified solution stack, comprising server, storage, and services, reduces the compute time, controls costs, and maximizes resilience of SAS environment with ultra-high bandwidth and highest availability. INTRODUCTION We will explore how to deploy SAS on IBM Power Systems platforms and unleash the full potential of the infrastructure, to reduce deployment risk, maximize flexibility and accelerate insights. We will start by reviewing IBM and SAS’s technology relationship and the current state of SAS products on IBM Power Systems. Then we will look at some of the infrastructure options to deploy SAS 9.4 on IBM Power Systems and IBM Storage, while maximizing resiliency & throughput by leveraging best practices. Next, we will look at SAS Viya, which introduces changes to the underlying infrastructure requirements while remaining able to be deployed alongside a traditional SAS 9.4 operation. We’ll explore the various deployment modes available. Finally, we’ll look at tuning practices and reference materials available for a deeper dive in deploying SAS on IBM platforms. SAS: 40 YEARS OF PARTNERSHIP WITH IBM IBM and SAS have been partners since the founding of SAS.
    [Show full text]
  • POWER® Processor-Based Systems
    IBM® Power® Systems RAS Introduction to IBM® Power® Reliability, Availability, and Serviceability for POWER9® processor-based systems using IBM PowerVM™ With Updates covering the latest 4+ Socket Power10 processor-based systems IBM Systems Group Daniel Henderson, Irving Baysah Trademarks, Copyrights, Notices and Acknowledgements Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: Active AIX® POWER® POWER Power Power Systems Memory™ Hypervisor™ Systems™ Software™ Power® POWER POWER7 POWER8™ POWER® PowerLinux™ 7® +™ POWER® PowerHA® POWER6 ® PowerVM System System PowerVC™ POWER Power Architecture™ ® x® z® Hypervisor™ Additional Trademarks may be identified in the body of this document. Other company, product, or service names may be trademarks or service marks of others. Notices The last page of this document contains copyright information, important notices, and other information. Acknowledgements While this whitepaper has two principal authors/editors it is the culmination of the work of a number of different subject matter experts within IBM who contributed ideas, detailed technical information, and the occasional photograph and section of description.
    [Show full text]
  • This Document Serves As a Summary of the UC Berkeley Script Encoding Initiative's Recent Activities. Proposals Recently Submit
    L2/11‐049 TO: Unicode Technical Committee FROM: Deborah Anderson, Project Leader, Script Encoding Initiative, UC Berkeley DATE: 3 February 2011 RE: Liaison Report from UC Berkeley (Script Encoding Initiative) This document serves as a summary of the UC Berkeley Script Encoding Initiative’s recent activities. Proposals recently submitted to the UTC that have involved SEI assistance include: Afaka (Everson) [preliminary] Elbasan (Everson and Elsie) Khojki (Pandey) Khudawadi (Pandey) Linear A (Everson and Younger) [revised] Nabataean (Everson) Woleai (Everson) [preliminary] Webdings/Wingdings Ongoing work continues on the following: Anatolian Hieroglyphs (Everson) Balti (Pandey) Dhives Akuru (Pandey) Gangga Malayu (Pandey) Gondi (Pandey) Hungarian Kpelle (Everson and Riley) Landa (Pandey) Loma (Everson) Mahajani (Pandey) Maithili (Pandey) Manichaean (Everson and Durkin‐Meisterernst) Mende (Everson) Modi (Pandey) Nepali script (Pandey) Old Albanian alphabets Pahawh Hmong (Everson) Pau Cin Hau Alphabet and Pau Cin Hau Logographs (Pandey) Rañjana (Everson) Siyaq (and related symbols) (Pandey) Soyombo (Pandey) Tani Lipi (Pandey) Tolong Siki (Pandey) Warang Citi (Everson) Xawtaa Dorboljin (Mongolian Horizontal Square script) (Pandey) Zou (Pandey) Proposals for unencoded Greek papyrological signs, as well as for various Byzantine Greek and Sumero‐Akkadian characters are being discussed. A proposal for the Palaeohispanic script is also underway. Deborah Anderson is encouraging additional participation from Egyptologists for future work on Ptolemaic signs. She has received funding from the National Endowment for the Humanities and support from Google to cover work through 2011. .
    [Show full text]
  • IBM AIX Version 6.1 Differences Guide
    Front cover IBM AIX Version 6.1 Differences Guide AIX - The industrial strength UNIX operating system AIX Version 6.1 enhancements explained An expert’s guide to the new release Roman Aleksic Ismael "Numi" Castillo Rosa Fernandez Armin Röll Nobuhiko Watanabe ibm.com/redbooks International Technical Support Organization IBM AIX Version 6.1 Differences Guide March 2008 SG24-7559-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xvii. First Edition (March 2008) This edition applies to AIX Version 6.1, program number 5765-G62. © Copyright International Business Machines Corporation 2007, 2008. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures . xi Tables . xiii Notices . xvii Trademarks . xviii Preface . xix The team that wrote this book . xix Become a published author . xxi Comments welcome. xxi Chapter 1. Application development and system debug. 1 1.1 Transport independent RPC library. 2 1.2 AIX tracing facilities review . 3 1.3 POSIX threads tracing. 5 1.3.1 POSIX tracing overview . 6 1.3.2 Trace event definition . 8 1.3.3 Trace stream definition . 13 1.3.4 AIX implementation overview . 20 1.4 ProbeVue . 21 1.4.1 ProbeVue terminology. 23 1.4.2 Vue programming language . 24 1.4.3 The probevue command . 25 1.4.4 The probevctrl command . 25 1.4.5 Vue: an overview. 25 1.4.6 ProbeVue dynamic tracing example . 31 Chapter 2. File systems and storage. 35 2.1 Disabling JFS2 logging .
    [Show full text]
  • Raiffeisenbank Speeds Data Warehouse, Cuts Costs with Red Hat Enterprise Linux
    CUSTOMER CASE STUDY RAIFFEISENBANK SPEEDS DATA WAREHOUSE, CUTS COSTS WITH RED HAT ENTERPRISE LINUX Raiffeisenbank, a banking institution that provides a wide range of services to private and corporate clients in the Czech Republic, needed to replace the aging hardware and IBM AIX operating system that supported its data warehouse. By migrating to Red Hat Enterprise Linux running on cost-effective Hitachi servers with Intel processors, the bank has tripled system performance speed and maintained stability — while cutting total cost SOFTWARE AND of ownership (TCO) by 50%. SERVICES Red Hat® Enterprise Linux® HARDWARE Hitachi Unified Compute Platform for Oracle Database Hitachi Compute Blade 2500 Prague, Czech Republic FINANCIAL SERVICES (CB 2500) Hitachi Virtual Storage HEADQUARTERS 3,000 EMPLOYEES Platform G600 (VSP G600) 120 BRANCHES PARTNER “There are many benefits to using Red Hat MHM computer a.s. and Oracle solutions together, and also BENEFITS from moving from IBM to Intel. We feel • Achieved three times faster a combination of Red Hat and Oracle on system performance an Intel platform is a preferred solution • Anticipates 50% decrease for any company.” in total cost of ownership over five years JIŘÍ KOUTNÍK HEAD OF SYSTEM ADMINISTRATION, • Gained greater flexibility by RAIFFEISENBANK eliminating vendor lock-in facebook.com/redhatinc @redhatnews linkedin.com/company/red-hat redhat.com AGING UNIX SYSTEM TOO SLOW FOR MODERN BUSINESS Raiffeisenbank a.s. provides a wide range of banking services to private and corporate clients in the Czech Republic at more than 120 branches and business client centers. The bank offers corpo- rate and personal finance products and services related to savings, insurance, and leasing, including specialized mortgage centers and business advisors.
    [Show full text]
  • GSI Local Guide
    UNIX Primer GSI Local Guide GSI Computing Center Version 2.0 This is draft version !!! Preface: More than one year ago, we published our ®rst version of the Unix primer, which has been used in the meantime by many people at GSI and even in the outside HEP community. Nowadays, as more and more physicists have access to a Unix computer either via a X-terminal or use their own workstation, and as the installed computing power has increased by a large factor, we have revised the ®rst version of our Unix primer. We tried to re¯ect the changes in the installedhardware, like the installationof the 11 machine AIX cluster, and the installationof new software products, as the batch system for job submission, new backup and restore products and the graphics system IDL. Almost all chapters have been revised, and some have undergone substantial changes like the introduction, the section about experimental data and tape handling and the chapter about the editors, where more editors are described in detail. Although many topics are still missing or could be improved, we decided to publishthe second edition of the Unix primer now in order to give a guide to the rapidly increasing Unix user community at GSI. As for the ®rst edition, many people again have contributed to this document: Wolfgang Ahner, Eliete Bertulani, Michael Dahlinger, Matthias Feyerabend, Ingo Giese, Horst GÈoringer, Eva Hocks, Peter Malzacher, Udo Meyer, Kerstin Schiebel, Kay Winkler and Heiko Weber. Preface for Version 1.0: In early summer 1991 the GSI Computing Center started a Unix Pilot Project investigating the hardware and software possibilities of centrally operated unix workstation systems.
    [Show full text]
  • Programming the Cell Broadband Engine Examples and Best Practices
    Front cover Draft Document for Review February 15, 2008 4:59 pm SG24-7575-00 Programming the Cell Broadband Engine Examples and Best Practices Practical code development and porting examples included Make the most of SDK 3.0 debug and performance tools Understand and apply different programming models and strategies Abraham Arevalo Ricardo M. Matinata Maharaja Pandian Eitan Peri Kurtis Ruby Francois Thomas Chris Almond ibm.com/redbooks Draft Document for Review February 15, 2008 4:59 pm 7575edno.fm International Technical Support Organization Programming the Cell Broadband Engine: Examples and Best Practices December 2007 SG24-7575-00 7575edno.fm Draft Document for Review February 15, 2008 4:59 pm Note: Before using this information and the product it supports, read the information in “Notices” on page xvii. First Edition (December 2007) This edition applies to Version 3.0 of the IBM Cell Broadband Engine SDK, and the IBM BladeCenter QS-21 platform. © Copyright International Business Machines Corporation 2007. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Draft Document for Review February 15, 2008 4:59 pm 7575TOC.fm Contents Preface . xi The team that wrote this book . xi Acknowledgements . xiii Become a published author . xiv Comments welcome. xv Notices . xvii Trademarks . xviii Part 1. Introduction to the Cell Broadband Engine . 1 Chapter 1. Cell Broadband Engine Overview . 3 1.1 Motivation . 4 1.2 Scaling the three performance-limiting walls. 6 1.2.1 Scaling the power-limitation wall . 6 1.2.2 Scaling the memory-limitation wall .
    [Show full text]
  • A Cadem Ic C a Le Ndar 2 0
    calcover08-09_final.qxp 4/25/2008 9:45 AM Page 1 a . c g u i s s i n p . n i w w w NORTH BAY, ONTARIO, CANADA : t e n r e t NOR n i • T H a B . c A Y , g u ON T AR i s s i n p I O , CANA r @ n i a r t D A i s g r e : l i a m - e Ac ad emic C a len da r 2008 – 200 Liaison Office, 100 College Drive, Box 5002, North Bay, ON P1B 8L7 9 tel: (705) 474-3450, ext. 4517 • fax: (705) 495-1772 • tty: (705) 474-8797 • e-mail: [email protected] • internet: www.nipissingu.ca A CADEM I C CALEN D A R 2 0 0 8 – 2 0 0 9 Table of Contents DIRECTORY FOR INQUIRIES . .1 EXTENSION (IN-SERVICE) EDUCATION . .281 DEGREES AND MAJORS AT A GLANCE . .2 Advanced Bachelors Degree in Education Degree Program . .285 ACADEMIC YEAR 2008–2009 . .4 Advanced Bachelors Degree in Educational INTRODUCING NIPISSING UNIVERSITY . .10 Leadership Program . .286 GRADUATION . .19 Teacher of the Deaf and Hard of CHARGES AND FEES . .20 Hearing Program . .287 FINANCIAL AID, SCHOLARSHIPS, BURSARIES Professional Development for Teachers . .287 AND AWARDS . .28 NIPISSING UNIVERSITY STUDENT POLICIES . .309 ADMISSIONS . .33 ADMINISTRATION AND FACULTY . .321 Undergraduate Program Admissions . .33 INDEX . .335 Professional Program Admissions – Education . .44 Graduate Program Admissions . .50 FACULTY OF ARTS AND SCIENCE / FACULTY OF APPLIED AND PROFESSIONAL STUDIES . .53 Registration Procedures and Regulations . .53 Academic Regulations and Information . .54 Degree Requirements and Academic Standing .
    [Show full text]
  • ONIX for Books Codelists Issue 40
    ONIX for Books Codelists Issue 40 23 January 2018 DOI: 10.4400/akjh All ONIX standards and documentation – including this document – are copyright materials, made available free of charge for general use. A full license agreement (DOI: 10.4400/nwgj) that governs their use is available on the EDItEUR website. All ONIX users should note that this is the fourth issue of the ONIX codelists that does not include support for codelists used only with ONIX version 2.1. Of course, ONIX 2.1 remains fully usable, using Issue 36 of the codelists or earlier. Issue 36 continues to be available via the archive section of the EDItEUR website (http://www.editeur.org/15/Archived-Previous-Releases). These codelists are also available within a multilingual online browser at https://ns.editeur.org/onix. Codelists are revised quarterly. Go to latest Issue Layout of codelists This document contains ONIX for Books codelists Issue 40, intended primarily for use with ONIX 3.0. The codelists are arranged in a single table for reference and printing. They may also be used as controlled vocabularies, independent of ONIX. This document does not differentiate explicitly between codelists for ONIX 3.0 and those that are used with earlier releases, but lists used only with earlier releases have been removed. For details of which code list to use with which data element in each version of ONIX, please consult the main Specification for the appropriate release. Occasionally, a handful of codes within a particular list are defined as either deprecated, or not valid for use in a particular version of ONIX or with a particular data element.
    [Show full text]
  • UTC L2/16‐037 FROM: Deborah Anderson, Ken Whistler
    TO: UTC L2/16‐037 FROM: Deborah Anderson, Ken Whistler, Rick McGowan, Roozbeh Pournader, Andrew Glass, and Laurentiu Iancu SUBJECT: Recommendations to UTC #146 January 2016 on Script Proposals DATE: 22 January 2016 The recommendations below are based on documents available to the members of this group at the time they met, January 19, 2016. EUROPE 1. Latin Document: L2/15‐327 Proposal to add Medievalist punctuation characters – Everson Discussion: We reviewed this document, which requested 21 characters. Many of the proposed characters require more detailed analysis, specifically providing examples that show contrasts in manuscripts, in old transcriptions, and how the marks are represented in text today. Specific comments raised in the discussion: • §1 Introduction. In the list of the proposed characters on pages 1 and 2, include dotted guide‐ lines, which show the placement of the characters in relation to the baseline, mid‐line, and top line, and solid lines separating individual table cells. • §2.2.3. Punctus versus. The text suggests that two glyphs for the same character are being proposed: PUNCTUS VERSUS MARK and LOW PUNCTUS VERSUS MARK. • §2.4 Distinctiones. “Note too that ჻ is the Georgian paragraph separator; no ‘generic’ punctuation mark for that has been encoded.” Is this a request to unify the Latin ჻ with U+10FB Georgian Paragraph Separator? If so, it can be added to ScriptExtensions.txt. • §4 Linebreaking. The assignment of SY as the LB property for DOTTED SOLIDUS should be reviewed by the UTC, since the SY class currently has only one member and it would be prudent to be cautious about adding another member to SY.
    [Show full text]
  • Realizacija Datotečnog Sustava Na SSD Pogonu
    Realizacija datotečnog sustava na SSD pogonu Večenaj, Matija Undergraduate thesis / Završni rad 2019 Degree Grantor / Ustanova koja je dodijelila akademski / stručni stupanj: University of Zagreb, Faculty of Organization and Informatics / Sveučilište u Zagrebu, Fakultet organizacije i informatike Permanent link / Trajna poveznica: https://urn.nsk.hr/urn:nbn:hr:211:426744 Rights / Prava: Attribution-ShareAlike 3.0 Unported Download date / Datum preuzimanja: 2021-09-28 Repository / Repozitorij: Faculty of Organization and Informatics - Digital Repository SVEUČILIŠTE U ZAGREBU FAKULTET ORGANIZACIJE I INFORMATIKE V A R A Ž D I N Matija Večenaj REALIZACIJA DATOTEČNOG SUSTAVA NA SSD POGONU ZAVRŠNI RAD Varaždin, 2019. SVEUČILIŠTE U ZAGREBU FAKULTET ORGANIZACIJE I INFORMATIKE V A R A Ž D I N Matija Večenaj Matični broj: 44855/16-R Studij: Informacijski sustavi REALIZACIJA DATOTEČNOG SUSTAVA NA SSD POGONU ZAVRŠNI RAD Mentor: Izv. Prof. Dr. Sc. Igor Balaban Varaždin, kolovoz 2019. Matija Večenaj Izjava o izvornosti Izjavljujem da je moj završni rad izvorni rezultat mojeg rada te da se u izradi istoga nisam koristio drugim izvorima osim onima koji su u njemu navedeni. Za izradu rada su korištene etički prikladne i prihvatljive metode i tehnike rada. Autor potvrdio prihvaćanjem odredbi u sustavu FOI-radovi _______________________________________________________________________ i Sažetak Tema ovog rada jest datotečni sustav i njegova realizacija na SSD pogonu. Najprije se u razradi obrazložava uloga flash memorije bez koje SSD pogon ne bi bilo moguće realizirati. Nakon toga, slijede općenite informacije o SSD pogonu kao što je povijest razvoja, karakteristike, usporedba sa starijim tehnologijama i podjela istih s obzirom na sučelja. Objasnit će se i arhitektura SSD-a, s posebnim naglaskom na kontroler i memoriju.
    [Show full text]
  • Script Encoding, Part 2
    Script Encoding, Part 2 Working with the user community Debbie Anderson, SEI, UC Berkeley Internationalization and Unicode Conference 40 2 November 2016 Script Encoding Initiative, UC Berkeley • Started 2002 • Helped get over 70 scripts into Unicode • 100+ scripts remain to be encoded A few words about scripts... • Can carry significant emotional feeling • Ol Chiki • Even if the “user” can’t read the script , script can be a symbol of identity & pride • Can make one community different from another • But a new script can delay its use on devices Bamum Who make up the “user community”? • Anyone with an interest in the script: • linguists, native users, liturgical script users, librarians, historians, script enthusiasts... • May not be able to actively read and write the script • To assist on Unicode proposals, should have very good working knowledge of script Steps to Encoding a Script Steps to Encoding a Script: Identify script as eligible Factors: • Users (beyond creator and few others) • Printed materials in script • Taught today (esp. new script) • Script relatively stable • Not unifiable with another encoded script Identify script as eligible Steps to Encoding a Script: Identify script as eligible Lakhum Mossang - Tangsa Identify script as eligible Shuishu Steps to Encoding a Script: Collect materials Kpelle Collect materials Khitan Large Script Identify script as eligible Steps to Encoding a Script: Write proposal l Write proposal Collect materials Identify script as eligible Steps to Encoding a Script: Get Experts / User Community
    [Show full text]