DOCSLIB.ORG

The Buildroot User Manual I

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

The Buildroot user manual i The Buildroot user manual The Buildroot user manual ii Contents I Getting started 1 1 About Buildroot 2 2 System requirements 3 2.1 Mandatory packages.................................................3 2.2 Optional packages...................................................4 3 Getting Buildroot 5 4 Buildroot quick start 6 5 Community resources 8 II User guide 9 6 Buildroot configuration 10 6.1 Cross-compilation toolchain............................................. 10 6.1.1 Internal toolchain backend.......................................... 11 6.1.2 External toolchain backend.......................................... 11 6.1.3 Build an external toolchain with Buildroot.................................. 12 6.1.3.1 External toolchain wrapper.................................... 13 6.2 /dev management................................................... 13 6.3 init system....................................................... 14 7 Configuration of other components 16 8 General Buildroot usage 17 8.1 make tips....................................................... 17 8.2 Understanding when a full rebuild is necessary................................... 19 8.3 Understanding how to rebuild packages....................................... 20 8.4 Offline builds..................................................... 20 The Buildroot user manual iii 8.5 Building out-of-tree.................................................. 20 8.6 Environment variables................................................ 21 8.7 Dealing efficiently with filesystem images...................................... 22 8.8 Details about packages................................................ 22 8.9 Graphing the dependencies between packages.................................... 23 8.10 Graphing the build duration.............................................. 24 8.11 Graphing the filesystem size contribution of packages................................ 24 8.12 Top-level parallel build................................................ 25 8.13 Integration with Eclipse................................................ 26 8.14 Advanced usage.................................................... 26 8.14.1 Using the generated toolchain outside Buildroot............................... 26 8.14.2 Using gdb in Buildroot........................................... 26 8.14.3 Using ccache in Buildroot......................................... 27 8.14.4 Location of downloaded packages...................................... 28 8.14.5 Package-specific make targets........................................ 28 8.14.6 Using Buildroot during development..................................... 29 9 Project-specific customization 31 9.1 Recommended directory structure.......................................... 31 9.1.1 Implementing layered customizations.................................... 32 9.2 Keeping customizations outside of Buildroot..................................... 33 9.2.1 Layout of a br2-external tree......................................... 34 9.2.1.1 The external.desc file.................................... 34 9.2.1.2 The Config.in and external.mk files........................... 35 9.2.1.3 The configs/ directory..................................... 35 9.2.1.4 The provides/ directory.................................... 35 9.2.1.5 Free-form content......................................... 36 9.2.1.6 Additional Linux kernel extensions................................ 36 9.2.1.7 Example layout.......................................... 36 9.3 Storing the Buildroot configuration.......................................... 39 9.4 Storing the configuration of other components.................................... 40 9.5 Customizing the generated target filesystem..................................... 40 9.5.1 Setting file permissions and ownership and adding custom devices nodes................. 42 9.6 Adding custom user accounts............................................. 42 9.7 Customization after the images have been created.................................. 42 9.8 Adding project-specific patches............................................ 43 9.9 Adding project-specific packages........................................... 43 9.10 Quick guide to storing your project-specific customizations............................. 44 The Buildroot user manual iv 10 Using SELinux in Buildroot 46 10.1 Enabling SELinux support.............................................. 46 10.2 SELinux policy tweaking............................................... 46 11 Frequently Asked Questions & Troubleshooting 48 11.1 The boot hangs after Starting network. ....................................... 48 11.2 Why is there no compiler on the target?....................................... 48 11.3 Why are there no development files on the target?.................................. 49 11.4 Why is there no documentation on the target?.................................... 49 11.5 Why are some packages not visible in the Buildroot config menu?......................... 49 11.6 Why not use the target directory as a chroot directory?............................... 49 11.7 Why doesn’t Buildroot generate binary packages (.deb, .ipkg. )?......................... 49 11.8 How to speed-up the build process?......................................... 50 12 Known issues 52 13 Legal notice and licensing 53 13.1 Complying with open source licenses........................................ 53 13.2 Complying with the Buildroot license........................................ 54 13.2.1 Patches to packages.............................................. 54 14 Beyond Buildroot 55 14.1 Boot the generated images.............................................. 55 14.1.1 NFS boot................................................... 55 14.1.2 Live CD.................................................... 55 14.2 Chroot......................................................... 56 III Developer guide 57 15 How Buildroot works 58 16 Coding style 59 16.1 Config.in file................................................... 59 16.2 The .mk file...................................................... 59 16.3 The documentation.................................................. 61 16.4 Support scripts.................................................... 61 17 Adding support for a particular board 62 The Buildroot user manual v 18 Adding new packages to Buildroot 63 18.1 Package directory................................................... 63 18.2 Config files...................................................... 63 18.2.1 Config.in file............................................... 63 18.2.2 Config.in.host file........................................... 64 18.2.3 Choosing depends on or select .................................... 65 18.2.4 Dependencies on target and toolchain options................................ 66 18.2.5 Dependencies on a Linux kernel built by buildroot............................. 68 18.2.6 Dependencies on udev /dev management.................................. 68 18.2.7 Dependencies on features provided by virtual packages........................... 69 18.3 The .mk file...................................................... 69 18.4 The .hash file.................................................... 69 18.5 Infrastructure for packages with specific build systems............................... 71 18.5.1 generic-package tutorial........................................ 71 18.5.2 generic-package reference....................................... 73 18.6 Infrastructure for autotools-based packages..................................... 78 18.6.1 autotools-package tutorial...................................... 78 18.6.2 autotools-package reference..................................... 79 18.7 Infrastructure for CMake-based packages...................................... 80 18.7.1 cmake-package tutorial.......................................... 80 18.7.2 cmake-package reference........................................ 81 18.8 Infrastructure for Python packages.......................................... 82 18.8.1 python-package tutorial......................................... 82 18.8.2 python-package reference........................................ 83 18.8.3 Generating a python-package from a PyPI repository......................... 84 18.8.4 python-package CFFI backend..................................... 84 18.9 Infrastructure for LuaRocks-based packages..................................... 85 18.9.1 luarocks-package tutorial....................................... 85 18.9.2 luarocks-package reference...................................... 86 18.10Infrastructure for Perl/CPAN packages........................................ 86 18.10.1 perl-package tutorial.......................................... 86 18.10.2 perl-package reference......................................... 87 18.11Infrastructure for virtual packages.......................................... 88 18.11.1 virtual-package tutorial........................................ 88 18.11.2 Virtual package’s Config.in file..................................... 88 18.11.3 Virtual package’s .mk file.......................................... 89 18.11.4 Provider’s Config.in file......................................... 89 18.11.5 Provider’s .mk file.............................................. 89 18.11.6 Notes on depending on a virtual package.................................. 89 The Buildroot user manual vi 18.11.7 Notes on depending on a specific provider.................................. 90 18.12Infrastructure for packages using kconfig for configuration
Recommended publications
  • Alpine Linux: Minimalistická Distribuce Nejen Na Server

    Alpine Linux: Minimalistická Distribuce Nejen Na Server

    Alpine Linux: minimalistická distribuce nejen na server Petr Krčmář 5. března 2017 Uvedené dílo (s výjimkou obrázků) podléhá licenci Creative Commons Uveďte autora 3.0 Česko. Petr Krčmář (Root.cz, vpsFree.cz) Alpine Linux: minimalistická distribuce nejen na server 5. března 2017 1 / 19 Petr Krčmář (Root.cz, vpsFree.cz) Alpine Linux: minimalistická distribuce nejen na server 5. března 2017 2 / 19 Prezentace už teď na webu https://www.petrkrcmar.cz Petr Krčmář (Root.cz, vpsFree.cz) Alpine Linux: minimalistická distribuce nejen na server 5. března 2017 3 / 19 Historie Alpine první verze 2006 původně jako fork LEAF (Linux Embedded Appliance Framework) to je zase fork LRP (Linux Router Project) = disketové distribuce vývojáři ale chtěli jít za hranici disket zůstala jednoduchost a přehlednost umožnilo to nasazení mimo jednoduché firewally dnes plnohodnotná distribuce stále umí běžet z RAM nezávislá, nekomerční Petr Krčmář (Root.cz, vpsFree.cz) Alpine Linux: minimalistická distribuce nejen na server 5. března 2017 4 / 19 K čemu se hodí? velká plnohodnotná distribuce embedded zařízení (síťové prvky) firewally routery ústředny VoIP servery a kontejnery ale i na desktop (Xfce, Gnome) Petr Krčmář (Root.cz, vpsFree.cz) Alpine Linux: minimalistická distribuce nejen na server 5. března 2017 5 / 19 Motto Small. Simple. Secure. Petr Krčmář (Root.cz, vpsFree.cz) Alpine Linux: minimalistická distribuce nejen na server 5. března 2017 6 / 19 Small. instalace v kontejneru jen 8 MB, 260 souborů 16 balíčků, jen 6 z jiných projektů instalace do virtuálu 53 MB, 1222 souborů 26 balíčků plná instalace na železo 302 MB, 4686 souborů 27 balíčků hodně jaderných modulů Petr Krčmář (Root.cz, vpsFree.cz) Alpine Linux: minimalistická distribuce nejen na server 5.
  • Debian Developer's Reference Version 12.0, Released on 2021-09-01

    Debian Developer's Reference Version 12.0, Released on 2021-09-01

    Debian Developer’s Reference Release 12.0 Developer’s Reference Team 2021-09-01 CONTENTS 1 Scope of This Document 3 2 Applying to Become a Member5 2.1 Getting started..............................................5 2.2 Debian mentors and sponsors......................................6 2.3 Registering as a Debian member.....................................6 3 Debian Developer's Duties 9 3.1 Package Maintainer's Duties.......................................9 3.1.1 Work towards the next stable release............................9 3.1.2 Maintain packages in stable .................................9 3.1.3 Manage release-critical bugs.................................. 10 3.1.4 Coordination with upstream developers............................ 10 3.2 Administrative Duties.......................................... 10 3.2.1 Maintaining your Debian information............................. 11 3.2.2 Maintaining your public key.................................. 11 3.2.3 Voting.............................................. 11 3.2.4 Going on vacation gracefully.................................. 12 3.2.5 Retiring............................................. 12 3.2.6 Returning after retirement................................... 13 4 Resources for Debian Members 15 4.1 Mailing lists............................................... 15 4.1.1 Basic rules for use....................................... 15 4.1.2 Core development mailing lists................................. 15 4.1.3 Special lists........................................... 16 4.1.4 Requesting new
  • Glibc and System Calls Documentation Release 1.0

    Glibc and System Calls Documentation Release 1.0

    Glibc and System Calls Documentation Release 1.0 Rishi Agrawal <[email protected]> Dec 28, 2017 Contents 1 Introduction 1 1.1 Acknowledgements...........................................1 2 Basics of a Linux System 3 2.1 Introduction...............................................3 2.2 Programs and Compilation........................................3 2.3 Libraries.................................................7 2.4 System Calls...............................................7 2.5 Kernel.................................................. 10 2.6 Conclusion................................................ 10 2.7 References................................................ 11 3 Working with glibc 13 3.1 Introduction............................................... 13 3.2 Why this chapter............................................. 13 3.3 What is glibc .............................................. 13 3.4 Download and extract glibc ...................................... 14 3.5 Walkthrough glibc ........................................... 14 3.6 Reading some functions of glibc ................................... 17 3.7 Compiling and installing glibc .................................... 18 3.8 Using new glibc ............................................ 21 3.9 Conclusion................................................ 23 4 System Calls On x86_64 from User Space 25 4.1 Setting Up Arguements......................................... 25 4.2 Calling the System Call......................................... 27 4.3 Retrieving the Return Value......................................
  • Preview Objective-C Tutorial (PDF Version)

    Preview Objective-C Tutorial (PDF Version)

    Objective-C Objective-C About the Tutorial Objective-C is a general-purpose, object-oriented programming language that adds Smalltalk-style messaging to the C programming language. This is the main programming language used by Apple for the OS X and iOS operating systems and their respective APIs, Cocoa and Cocoa Touch. This reference will take you through simple and practical approach while learning Objective-C Programming language. Audience This reference has been prepared for the beginners to help them understand basic to advanced concepts related to Objective-C Programming languages. Prerequisites Before you start doing practice with various types of examples given in this reference, I'm making an assumption that you are already aware about what is a computer program, and what is a computer programming language? Copyright & Disclaimer © Copyright 2015 by Tutorials Point (I) Pvt. Ltd. All the content and graphics published in this e-book are the property of Tutorials Point (I) Pvt. Ltd. The user of this e-book can retain a copy for future reference but commercial use of this data is not allowed. Distribution or republishing any content or a part of the content of this e-book in any manner is also not allowed without written consent of the publisher. We strive to update the contents of our website and tutorials as timely and as precisely as possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt. Ltd. provides no guarantee regarding the accuracy, timeliness or completeness of our website or its contents including this tutorial. If you discover any errors on our website or in this tutorial, please notify us at [email protected] ii Objective-C Table of Contents About the Tutorial ..................................................................................................................................
  • Meeting Agenda 4:30 – 6:00 PM, Wednesday, Nov 2Nd, 2016 Lyons Town Hall

    Meeting Agenda 4:30 – 6:00 PM, Wednesday, Nov 2Nd, 2016 Lyons Town Hall

    Meeting Agenda 4:30 – 6:00 PM, Wednesday, Nov 2nd, 2016 Lyons Town Hall I. Roll Call, Agenda, Minutes • Amendments to Agenda • Approve Minutes from Oct 19th • UEB Officers and Member Lead Areas • Upcoming Meetings - Nov 12, 2016 9 AM or 1 PM - Lyons Boards and Commissions Training - Lyons ​ ​ ​ Nov 9. 8 AM - Northern Water Fall Water Users Meeting - Longmont, Best Western 1850 Industrial Cir. Dec 2nd - CAMU Fall Meeting - Fairfield & Woods in Denver, CO II. Audience Business III. Liaison Updates • Board of Trustees Update - MEAN meeting Report • Staff, Engineering Update - Honeywell Savings Gaurantee IV. Continued Business ● Town Utility Account tracking V. New Business ● Water/Wastewater Rate and CIP Study Presentation RG & Assoc. VI. Parking Lot • 2017 Utility FUnd Budget, Pipe Water rates for 2017 Budget, • Reserve/Rate Stabilization Funds • Wastewater Pretreatment Policy • LRAP INF 2.2.1 • Municipal Code Corrections UEB Meeting Minutes, 19 Oct 2016 Meeting Time and Location: Began at 4:30 at Town Hall. ​ Attendance:, Aaron Caplan, Lee Hall, Coco Gordon, John Cowdry, Chuck Keim, Dan Reitz, Jay Stott ​ Staff: Kyle Miller Liaisons: Guests: ​ ​ Amendments to Agenda: Welcomed Jay Stott as the newest member of the UEB. ​ Previous Minutes: . Reviewed and modified Oct 5th Minutes under Water Wastewater CIP to add “Areas ​ where there is no looping of the water mains need looping. It was emphasized to try and coordinate getting water, and wastewater done first in areas that need paving.” Aaron had not followed up with Parks and ​ Rec to find out if they were budgeting for water usage. He would do so. Then approved minutes.
  • What Are the Problems with Embedded Linux?

    What Are the Problems with Embedded Linux?

    What Are the Problems with Embedded Linux? Every Operating System Has Benefits and Drawbacks Linux is ubiquitous. It runs most internet servers, is inside Android* smartphones, and is used on millions of embedded systems that, in the past, ran Real-Time Operating Systems (RTOSes). Linux can (and should) be used were possible for embedded projects, but while it gives you extreme choice, it also presents the risk of extreme complexity. What, then, are the trade-offs between embedded Linux and an RTOS? In this article, we cover some key considerations when evaluating Linux for a new development: ■ Design your system architecture first ■ What is Linux? ■ Linux vs. RTOSes ■ Free software is about liberty—not price ■ How much does Embedded Linux cost? ■ Why pay for Embedded Linux? ■ Should you buy Embedded Linux or roll-your-own (RYO)? ■ To fork or not to fork? ■ Software patching ■ Open source licensing ■ Making an informed decision The important thing is not whether Linux or an RTOS is “the best,” but whether either operating system—or both together—makes the most technical and financial sense for your project. We hope this article helps you make an informed decision. Design Your System Architecture First It is important to design your system architecture first—before choosing either Linux or an RTOS—because both choices can limit architectural freedom. You may discover that aspects of your design require neither Linux nor an RTOS, making your design a strong candidate for a heterogeneous approach that includes one or more bare-metal environments (with possibly a Linux and/or RTOS environment as well).
  • Create an Email with Subject Title “Embedded Software Engineer”, Email a Copy of Your Resume to Jessica@Princetechnology.Com

    Create an Email with Subject Title “Embedded Software Engineer”, Email a Copy of Your Resume to [email protected]

    To Apply for This Position: Create an email with subject title “Embedded Software Engineer”, email a copy of your resume to [email protected] Location Address: ALLEN PARK, MI,48101 Position Description: TITLE: Embedded Software Engineer ‐ Hypervisor OS technologies This position is responsible to develop QNX and Android operating system images for Ford infotainment products. This includes creating and integrating code for: bootloader, kernel, drivers, type 1 hypervisor, and build environment. Skills Required: • Lead the design, bring‐up and support of QNX and Android operating system images • Create virt‐io drivers for QNX or Android guest operating systems • Participate in root cause analysis of hardware quality problems and software defects • Participate in system design, documentation, and testing to deliver a best‐in‐class infotainment system Experience Required: • 5+ years operating system experience involving Linux or QNX • 5+ years C/C++ software development experience on embedded, mobile, or consumer electronic platforms Experience Preferred: • Experience with Type 1 hypervisors • Experience creating virt‐io drivers • Mastery of C/C++ language, GNU tool chain, and Unix (QNX, Linux, or equivalent) • Experience with embedded build systems including QNX system builder, buildroot, yocto, or equivalent • Knowledge of in‐vehicle signaling and communication mechanisms such as CAN • Proficiency with revision control including Git, Subversion, or equivalent • Multi‐site software project team experience Education Required: • Bachelor's degree in Computer Engineering, Electrical Engineering, Computer Science, or related Education Preferred: • Master's degree in Computer Engineering, Electrical Engineering or Computer Science Additional Information: Web Based Assessment not required for this position. Visa Sponsorship and Domestic Relocation is available for this position.
  • Also Includes Slides and Contents From

    Also Includes Slides and Contents From

    The Compilation Toolchain Cross-Compilation for Embedded Systems Prof. Andrea Marongiu ([email protected]) Toolchain The toolchain is a set of development tools used in association with source code or binaries generated from the source code • Enables development in a programming language (e.g., C/C++) • It is used for a lot of operations such as a) Compilation b) Preparing Libraries Most common toolchain is the c) Reading a binary file (or part of it) GNU toolchain which is part of d) Debugging the GNU project • Normally it contains a) Compiler : Generate object files from source code files b) Linker: Link object files together to build a binary file c) Library Archiver: To group a set of object files into a library file d) Debugger: To debug the binary file while running e) And other tools The GNU Toolchain GNU (GNU’s Not Unix) The GNU toolchain has played a vital role in the development of the Linux kernel, BSD, and software for embedded systems. The GNU project produced a set of programming tools. Parts of the toolchain we will use are: -gcc: (GNU Compiler Collection): suite of compilers for many programming languages -binutils: Suite of tools including linker (ld), assembler (gas) -gdb: Code debugging tool -libc: Subset of standard C library (assuming a C compiler). -bash: free Unix shell (Bourne-again shell). Default shell on GNU/Linux systems and Mac OSX. Also ported to Microsoft Windows. -make: automation tool for compilation and build Program development tools The process of converting source code to an executable binary image requires several steps, each with its own tool.
  • Beginning Portable Shell Scripting from Novice to Professional

    Beginning Portable Shell Scripting from Novice to Professional

    Beginning Portable Shell Scripting From Novice to Professional Peter Seebach 10436fmfinal 1 10/23/08 10:40:24 PM Beginning Portable Shell Scripting: From Novice to Professional Copyright © 2008 by Peter Seebach All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN-13 (pbk): 978-1-4302-1043-6 ISBN-10 (pbk): 1-4302-1043-5 ISBN-13 (electronic): 978-1-4302-1044-3 ISBN-10 (electronic): 1-4302-1044-3 Printed and bound in the United States of America 9 8 7 6 5 4 3 2 1 Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, we use the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. Lead Editor: Frank Pohlmann Technical Reviewer: Gary V. Vaughan Editorial Board: Clay Andres, Steve Anglin, Ewan Buckingham, Tony Campbell, Gary Cornell, Jonathan Gennick, Michelle Lowman, Matthew Moodie, Jeffrey Pepper, Frank Pohlmann, Ben Renow-Clarke, Dominic Shakeshaft, Matt Wade, Tom Welsh Project Manager: Richard Dal Porto Copy Editor: Kim Benbow Associate Production Director: Kari Brooks-Copony Production Editor: Katie Stence Compositor: Linda Weidemann, Wolf Creek Press Proofreader: Dan Shaw Indexer: Broccoli Information Management Cover Designer: Kurt Krames Manufacturing Director: Tom Debolski Distributed to the book trade worldwide by Springer-Verlag New York, Inc., 233 Spring Street, 6th Floor, New York, NY 10013.
  • FPGA BASED RECONFIGURABLE BODY AREA NETWORK USING Nios II and Uclinux

    FPGA BASED RECONFIGURABLE BODY AREA NETWORK USING Nios II and Uclinux

    FPGA BASED RECONFIGURABLE BODY AREA NETWORK USING Nios II AND uClinux A Thesis Submitted to the College of Graduate Studies and Research in Partial Fulfillment of the Requirements for the Degree of Master of Science in the Department of Electrical and Computer Engineering University of Saskatchewan by Anthony Voykin Saskatoon, Saskatchewan, Canada c Copyright Anthony Voykin, April 2013. All rights reserved. Permission to Use In presenting this thesis in partial fulfillment of the requirements for a Postgraduate degree from the University of Saskatchewan, it is agreed that the Libraries of this University may make it freely available for inspection. Permission for copying of this thesis in any manner, in whole or in part, for scholarly purposes may be granted by the professors who supervised this thesis work or, in their absence, by the Head of the Department of Electrical and Computer Engineering or the Dean of the College of Graduate Studies and Research at the University of Saskatchewan. Any copying, publication, or use of this thesis, or parts thereof, for financial gain without the written permission of the author is strictly prohibited. Proper recognition shall be given to the author and to the University of Saskatchewan in any scholarly use which may be made of any material in this thesis. Request for permission to copy or to make any other use of material in this thesis in whole or in part should be addressed to: Head of the Department of Electrical and Computer Engineering 57 Campus Drive University of Saskatchewan Saskatoon, Saskatchewan, Canada S7N 5A9 i Acknowledgments I would like to thank my advisors Professor Ron Bolton and Professor Francis Bui for providing me with guidance and support necessary to complete my thesis work.
  • Embedded Linux Systems with the Yocto Project™

    Embedded Linux Systems with the Yocto Project™

    OPEN SOURCE SOFTWARE DEVELOPMENT SERIES Embedded Linux Systems with the Yocto Project" FREE SAMPLE CHAPTER SHARE WITH OTHERS �f, � � � � Embedded Linux Systems with the Yocto ProjectTM This page intentionally left blank Embedded Linux Systems with the Yocto ProjectTM Rudolf J. Streif Boston • Columbus • Indianapolis • New York • San Francisco • Amsterdam • Cape Town Dubai • London • Madrid • Milan • Munich • Paris • Montreal • Toronto • Delhi • Mexico City São Paulo • Sidney • Hong Kong • Seoul • Singapore • Taipei • Tokyo Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. The author and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. For information about buying this title in bulk quantities, or for special sales opportunities (which may include electronic versions; custom cover designs; and content particular to your business, training goals, marketing focus, or branding interests), please contact our corporate sales depart- ment at [email protected] or (800) 382-3419. For government sales inquiries, please contact [email protected]. For questions about sales outside the U.S., please contact [email protected]. Visit us on the Web: informit.com Cataloging-in-Publication Data is on file with the Library of Congress.
  • Cp 99, Other Filing/Pleading, 11/12/2014

    Cp 99, Other Filing/Pleading, 11/12/2014

    BINGHAM Catherine Wang Brett P. Ferenchak catherine. wang@ bingham. com [email protected] November 11, 2014 Via Overnight Courier and E-Mail Oregon Public Utility Commission Attn: Filing Center 550 Capitol Street, N.E. Suite 215 Salem, OR 97301-2551 [email protected] Re: Business Telecom, LLC d/b/a EarthLink Business I Notification of Conversion and Associated Name Change Dear Sir or Madam: Business Telecom, LLC d/b/a EarthLink Business I (formerly known as Business Telecom, Inc. d/b/a EarthLink Business III) (the "Company") hereby notifies the Commission (1) that the Company converted from a North Carolina corporation to a North Carolina limited liability company' and (2) of the associated name change to "Business Telecom, LLC d/b/a EarthLink Business 1." The Company requests that the Commission update its records, including the Company's Certificate,2 to reflect the conversion and associate name change and, to the extent necessary, approve these changes. Attached hereto are the Company's conversion documents and updated authorization to transact business in Oregon and trade name registration. Beijing Boston Frankfurt Hartford Hong Kong London los Angeles New York Orange County San Francisco Santa Monica Silicon Valley Tokyo Washington The conversion of the Company to a limited liability company was merely a change in its corporate form -the conversion was accomplished through the filing of Articles of Bingham McCutchen LLP Conversion in North Carolina and did not entail any merger or other transactions interrupting 2020 K Street NW Washington, DC the existence of the Company. 20006-1806 2 The Company is authorized to provide interexchange telecommunications services pursuant to Order No.