DOCSLIB.ORG

Yocto Project E Como Usá-Lo Em Seu Próximo Projeto

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Yocto Project E Como Usá-Lo Em Seu Próximo Projeto padtec.com Introdução ao Yocto Project e como usá-lo em seu próximo projeto João Freitas [email protected] padtec.com [email protected] http://www.github.com/joaohf padtec.com Linux Embarcado Aplicação Aplicação • Fim específico • Conjunto reduzido • Autonomia Biblioteca Biblioteca Biblioteca Toolchain Biblioteca C Linux Kernel Hardware Padtec S/A © 2014 Todos os Direitos Reservados 4 Imagem do Sistema Bootloader • Tamanho reduzido Linux Kernel • Particionamento rootfs1 rootfs2 data Padtec S/A © 2014 Todos os Direitos Reservados 5 Sistema com Linux Embarcado Opções para construção: • Distribuição pronta • Gerar uma distribuição manualmente • Usar um sistema de build Padtec S/A © 2014 Todos os Direitos Reservados 6 Sistema com Linux Embarcado ● Usar uma distribuição pronta – Red Hat – Ubuntu – Suse – Archlinux – Slackware – Debian – Android, Emdebian, Tizen Padtec S/A © 2014 Todos os Direitos Reservados Sistema com Linux Embarcado ● Gerar uma distribuição manualmente – Controle Total – Flexibilidade – Trabalhoso – Reprodutibilidade ● Linux From Scratch: vale a experiência! – http://www.linuxfromscratch.org/ Padtec S/A © 2014 Todos os Direitos Reservados Sistema com Linux Embarcado ● Ferramenta de Build – Automatização do processo de geração – Conjunto de pacotes validados – Frameworks para extensão e desenvolvimento ● Buildroot, PTXdist, LTIB, BaseRock, OpenEmbedded, Poky Padtec S/A © 2014 Todos os Direitos Reservados Yocto Project Unidade SI de medição, igual a 10^24 http://www.yoctoproject.org Padtec S/A © 2014 Todos os Direitos Reservados O que é? ● Projeto Open Source ● Build System para Linux OS ● Coleção de projetos, métodos e ferramentas – Fácil customização – Um lugar para a Indústria publicar BSPs ● Fundado em 2010 ● Gerenciado por membros da Linux Foundation ● Cadência de releases: 6 meses Padtec S/A © 2014 Todos os Direitos Reservados O que é? ● “The Yocto Project is not an Embedded Linux Distribution – It creates a custom one for You!” ● “The Yocto Project is not Single Open Source Project – It is an Ecosystem” ● “The Yocto Project combines the convenience of a ready-to-run Linux Distribuition with the flexibility of a custom Linux operation system stack” ● “... to bring some order to the chaos of embedded Linux development” Padtec S/A © 2014 Todos os Direitos Reservados Quem faz? ● Comunidade de usuários ● Organizações – Desenvolvedores individuais – Embeded Hardware – Semicondutores – OS Vendors ● Linux Foundation Padtec S/A © 2014 Todos os Direitos Reservados Quem faz? ● Adivisory Board – LSI, Freescale, Wind River, OpenEmbedded – TI, Intel, LTSI, Juniper Networks, AMD – Mentor Graphics, LG, Dell, Broadcom, – Renesas, OS Systems, MontaVista, Huawei, – Enea Padtec S/A © 2014 Todos os Direitos Reservados Quem faz? ● Participantes ● Membros ● Colaboradores Padtec S/A © 2014 Todos os Direitos Reservados Quem usa? ● Distros Comerciais – Wind River Linux Carrier Grade Profile 5 – Wind River Linux 6 – Enea Linux 4.0 – MontaVista Linux Carrier Grade Edition 7 – Mentor Embedded Linux ● Distros – Angstron (http://www.angstrom-distribution.org) – Shr (http://shr-project.org) Padtec S/A © 2014 Todos os Direitos Reservados Quem usa? ● BSP (Board Support Package) – Intel – Freescale – Texas Instruments – Renesas – AMD Padtec S/A © 2014 Todos os Direitos Reservados O que eu preciso para usar? Para começar... ● PC padrão ● 50Gb de disco ● Um distro recente (debian, ubuntu, fedora, opensuse, centos) ● Pacotes de desenvolvimento (gcc,make,git) ● Uma release do Yocto Project ● http://www.yoctoproject.org/docs/1.7/yocto-project-qs/yocto-project-qs.ht ml Padtec S/A © 2014 Todos os Direitos Reservados O que eu preciso para usar? ● Se quiser brincar profissionalmente: – Processador Xeon, 16Gb RAM, 1Tb Disco, controlador RAID com cache alto ● Em casa: i5 terceira geração com 16Gb RAM e 1Tb HD 7200 SATA ● Um bom processador e disco com controladora rápida vai fazer a diferença. Padtec S/A © 2014 Todos os Direitos Reservados Como funciona? ● Build System: – Poky reference system ● Bitbake: build engine ● OpenEmbedded Core: receitas e classes bases – http://www.openembedded.org ● Core BSPs e layers Padtec S/A © 2014 Todos os Direitos Reservados Como funciona? ● Ferramentas de desenvolvimento – Application Development Toolkit – Hob – Toaster ● Eclise IDE Plugin: integração entre ADT e Eclipse ● AutoBuilder: build tests e QA ● cross-prelink, pseudo, swabber Padtec S/A © 2014 Todos os Direitos Reservados Como funciona? ● Tarefa (task): etapas executadas pelo build engine ● Receita (recipe): conjunto de tarefas necessárias para compilar determinado software (.bb, .bbappend) ● Classes (classes): herança e encapsulamento da lógica para a execução de tarefas comuns (.bbclass) Padtec S/A © 2014 Todos os Direitos Reservados Como funciona? ● Configuração (conf): arquivos com definições globais (.conf) ● Pacote (package): resultado do processamento da receita de um componente de software ● Camada (layer): conjunto de receitas, classes, arquivos de configuração que podem ser agregados ao sistema de build para estendê-lo ou modificar comportamentos Padtec S/A © 2014 Todos os Direitos Reservados Como funciona? ● Composição de layers Padtec S/A © 2014 Todos os Direitos Reservados Como funciona? ● Layers são blocos de construção Padtec S/A © 2014 Todos os Direitos Reservados Como funciona? ● Layer é o modo de extender o build system – Adicionar, remover, modificar ● Classes, receitas, configurações – São adicionadas no sistema Padtec S/A © 2014 Todos os Direitos Reservados Como funciona? ● Agrupe as layers por funcionalidade, exemplo: – Toolchains – BSP/Machine – Áreas funcionais (database, networking, languages) – Especificidades do projeto ● Pilhas de software de terceiros ● Componente usados em outros projetos ● Configurações Padtec S/A © 2014 Todos os Direitos Reservados Como funciona? ● Máquina (machine): plataforma de hardware alvo da distribuição. Implementado através de uma layer BSP ● Imagem (image): imagem final do rootfs do sistema gerado ● Distribuição (distro): regras e políticas de geração da imagem do sistema Padtec S/A © 2014 Todos os Direitos Reservados Como funciona? Padtec S/A © 2014 Todos os Direitos Reservados Tem interface gráfica? ● Bitbake: linha de comando $ bitbake <receita> $ bitbake <receita> -c <task> $ bitbake <receita> -k $ bitbake -s Padtec S/A © 2014 Todos os Direitos Reservados Tem interface gráfica? ● HOB Padtec S/A © 2014 Todos os Direitos Reservados Tem interface gráfica? ● Toaster Padtec S/A © 2014 Todos os Direitos Reservados Distro YP X Distro customizada por mim? ● Distribuição Pronta, vantagens Framework de Simplicidade de uso desenvolvimento Pronto e funcional Facilidade na Base de usuários instalação (pacotes) Suporte comercial Padtec S/A © 2014 Todos os Direitos Reservados Distro YP X Distro customizada por mim? ● Distribuição Pronta, desvantagens Tempo de boot Falta de pode ser alto flexibilidade Requisitos de licença Pode não estar otimizada Experiência Requer tempo Para adaptação e customização Padtec S/A © 2014 Todos os Direitos Reservados O que o Yocto Project permite configurar numa distribuição? ● Versão dos componentes de sw ● Subsistemas – Systemv, systemd ● Features adicionais: alsa, wayland, x11, usb, pci ● Toolchain – Interna ou externa ● Versão de Linux Kernel Padtec S/A © 2014 Todos os Direitos Reservados Há alguma restrição de licença nas distribuições geradas? ● Não há restrição de licenças ● Há preocupação do YP em gerar distros legais – Opções para não permitir determinada licença – Manifesto de licenças – Exportação de código fonte, scripts, patches ● https://www.yoctoproject.org/blogs/davest/2012/binaries-considered-dang erous Padtec S/A © 2014 Todos os Direitos Reservados Caso: 1 distro 4 plataforma ● Plataformas: – 2 EVKs (ppc e x86-64) – plataforma alvo do produto – máquina virtual para integração ● Solução YP: – Distro e Linux Kernel comum – A mesma SDK – MACHINE=<plataforma alvo> Padtec S/A © 2014 Todos os Direitos Reservados Caso: Fabricante sumiu, cadê o BSP? ● BSP antigo (2002) – Fabricante não oferecia suporte ($$$) ● Necessidade de evolução kernel e userland ● Plataforma não otimizada ● Solução YP: – Redução do footprint – Toolchain otimizado – Bugfixes gerais e críticos solucionados – Controle de todos os componentes do produto Padtec S/A © 2014 Todos os Direitos Reservados Caso: Toolchains ● Geração de SDKs – Podem ser instaladas em qualquer workstation linux ● Mesma versão de GCC ● Target para diferentes plataformas Padtec S/A © 2014 Todos os Direitos Reservados Qual o resultado da construção? ● Imagem: ext2, ext3, cpio, directdisk, jffs2, ubi, cramfw, brtfs, live ● Linux kernel image (bz2, uImage) ● Pacotes (rpm, ipk, deb, tar) ● Manifesto das licenças de softwares usadas ● Histórico de build (buildhistory) ● Código fonte de todos os softwares usados ● Scripts de build e patches aplicados Padtec S/A © 2014 Todos os Direitos Reservados Quais plataformas são suportadas? ● Arquiteturas: ARM, PPC, MIPS, x86 e x86-64 ● Machines: qemuarm, qemumips64, qemumips, qemuppc, qemux86, qemux86-64 ● Vendor BSPs: – TI, FSF, Intel, AMD, LSI http://git.yoctoproject. org/ Padtec S/A © 2014 Todos os Direitos Reservados Quais softwares podem rodar nestas distribuições? Servidores web? Banco de dados? Controladores de hardware? ● Qualquer sw pode ser buildado e adicionado na imagem final ● Alguns sw são mais complicados de empacotar – Requerem buildtools exóticos ou scripts que não seguem padrões ● Como regra geral: qualquer artefato que o bitbake consiga empacotar, pode ser usado ● Qualquer
Load more

Recommended publications
  • Openmoko Is Dead. Long Live Openphoenux!
    Openmoko is dead. Long live OpenPhoenux! Nikolaus Schaller, Lukas Märdian LinuxTag, Berlin, May 26th, 2012 Agenda Part one: some history Part two: a long way home Part three: rising from the ashes Part four: flying higher Part five: use it as daily phone – software Q&A Nikolaus Schaller, Lukas Märdian OpenPhoenux | GTA04 May 26th 2012 LinuxTag 2012 wiki.openmoko.org | www.gta04.org 2 Some history – Past iterations • FIC GTA01 – Neo 1973 – Roughly 3.000 units sold – Production discontinued • Openmoko GTA02 – Neo Freerunner – Roughly 15.000 units sold – Hardware revision v7 – Production discontinued Nikolaus Schaller, Lukas Märdian OpenPhoenux | GTA04 May 26th 2012 LinuxTag 2012 wiki.openmoko.org | www.gta04.org 3 Some history – The End (of part I) • FIC and Openmoko got out • Strong community continues development • Golden Delicious taking the lead – Excellent support for existing devices – Shipping spare parts and add-ons – Tuned GTA02v7++ • Deep sleep fix (aka bug #1024) -> Improved standby time • Bass rework -> Improved sound quality Nikolaus Schaller, Lukas Märdian OpenPhoenux | GTA04 May 26th 2012 LinuxTag 2012 wiki.openmoko.org | www.gta04.org 4 Agenda Part one: some history Part two: a long way home Part three: rising from the ashes Part four: flying higher Part five: use it as daily phone – software Q&A Nikolaus Schaller, Lukas Märdian OpenPhoenux | GTA04 May 26th 2012 LinuxTag 2012 wiki.openmoko.org | www.gta04.org 5 A long way home How do we get to a new open mobile phone? – open kernel for big ${BRAND} – reverse eng. – order from some ${MANUFACTURER} – hope for openness – DIY, “Use the source, Luke!” Nikolaus Schaller, Lukas Märdian OpenPhoenux | GTA04 May 26th 2012 LinuxTag 2012 wiki.openmoko.org | www.gta04.org 6 Using the source: Beagleboard Beagleboard – Full Linux support – Open schematics – Open layout – Expansion connectors – Lots of documentation – Components available Nikolaus Schaller, Lukas Märdian OpenPhoenux | GTA04 May 26th 2012 LinuxTag 2012 wiki.openmoko.org | www.gta04.org 7 In theory it could fit (Aug.
    [Show full text]
  • Reached Milestones and Ongoing Development on Replicant
    Reached milestones and ongoing development on Replicant Paul Kocialkowski [email protected] Sunday February 1st, 2015 Replicant “Replicant is a fully free Android distribution running on several devices, a free software mobile operating system putting the emphasis on freedom and privacy/security” ● Pragmatic way for software freedom on mobile devices ● Started in mid-2010: Openmoko FreeRunner and HTC Dream ● Fully free version of Android ● Ethical project that respects users ● Functional and usable daily ● Privacy enhancements (…) Replicant development Technical grounds: ● AOSP base at first ● CyanogenMod for more devices Implications of a fully free system: ● Remove or replace proprietary parts: executables, libraries, firmwares ● Get rid of malicious features tracking, statistics, etc Additional work: ● Adapt the system for the lack of proprietary components: graphics acceleration, firmwares loading ● "Branding”, look and feel ● Maintenance, security updates Replacing non-free software Have as many features available as possible! Reverse engineering: ● Long list of proprietary parts: graphics, audio, camera, sensors, RIL, hardware video decoding, etc ● Documentation is seldom available: [Chip maker] is not in a position to provide details of the formula we addressed with [OEM] phone team. ● Reverse engineering: logs, tracing, strings, decompiling, kernel driver, maths, frustration ● Understanding what's going on ● Writing free software replacements Hard tasks that Repicant doesn't deal with: ● Graphics acceleration, firmwares, modem system Replacing non-free software Free software replacements written for Replicant: ● RIL: Samsung-RIL, libsamsung-ipc: 30000 lines, 9 devices ● Camera: 5500-10000 lines, 2 devices ● Audio: 4500 lines, 3 devices ● Sensors: 3000-4000 lines, 8 devices Cooperation with other communities: ● SHR/FSO for libsamsung-ipc ● CyanogenMod/Teamhacksung for camera, audio ● Integration of work from Replicant (e.g.
    [Show full text]
  • Beyond.Pdf (Slides)
    Beyond Traditional Mobile Linux by Carsten “Stskeeps” Munk, Mer project architect http://www.merproject.org Mobile Linux up to 2011 ● Moblin, MeeGo, Maemo, LiMo, OpenEmbedded (Yocto, WebOS), OpenWRT, etc.. ● OpenMoko-centric (QtMoko, FSO/SHR, etc.) ● Android (Replicant, Ophone, Baidu Yi, B2G, etc.) ● Familiar, Access Linux Platform, Ubuntu Mobile/MID, Mobilinux ● ... and many many more What do most of them have in common? ● Many of them are now dead or zombie projects. ● Many were centric around specific vendors or specific devices. ● Many of them were wasted effort for the Mobile Linux community. Mobile Linux in 2012 ● OpenWRT, OpenEmbedded (Yocto) ● Android & Boot2Gecko ● Tizen, Mer, WebOS, Linaro efforts ● Intentionally not mentioning single- hardware/vendor OS'es, UI projects or open hardware ● Linux in general in all sorts of consumer devices ● Why not Fedora, Debian, Ubuntu, Slackware, etc..? The world around us If we were to interpret the world around us through what we see in popular Linux distributions and attitudes There's just one problem about that.. This is not how real life looks like anymore. ● But but but, what about KDE, GNOME, all our projects centered around the PC as the primary form of computer usage? ● We're experiencing the beginnings of a paradigm shift in how people use computers. “the notion of a major change in a certain thought-pattern — a radical change in personal beliefs, complex systems or organizations, replacing the former way of thinking or organizing with a radically different way of thinking or organizing” But.. ● A lot of open source projects are built around this old paradigm – centered around the PC.
    [Show full text]
  • EFL a UI Toolkit Designed for the Embedded World
    EFL A UI Toolkit Designed for the Embedded World stosb.com/talks Tom Hacohen [email protected] Samsung Open Source Group @TomHacohen Where We Come From The Enlightenment project is old (1996) - predating GNOME, KDE, etc. Initially a window manager - split to a set of libraries EFL as we know it dates back to at least 2000 Targeted the embedded world since the beginning Where We Come From (image circa 2001) General Information Used in many places, and supported by big industry players Focus on embedded devices A mix of LGPL 2.1 and BSD Three months release cycle Ever improving CI and static analysis (coverity) API/ABI checks before every release Zero compiler warnings with -Wall -Wextra Development Statistics Latest version (1.18.0): 105 unique contributors 3,364 commits Overall: 587 unique contributors 50,000 commits What Does the EFL Provide? What Does the EFL Provide? General Purpose Library Stringshares for reducing memory footprint In-line lists/arrays for reducing memory usage and fragmentation Copy-on-write support for C structures and unions Magic checks for structures Many others - list, hash, rb-tree and more What Does the EFL Provide? Binary Serialization Library Serialize, de-serialize C structures and unions Decompile to text, and re-compile from text Reduces memory usage (mmap) Faster to load Supports compression and signing What Does the EFL Provide? Mainloop and General-Glue Library Animators - Timers that tick at most on every frame Easy support for thread-workers Execute, monitor and pipe input/output of executables Integrates with other main loop implementations Networking, IPC, HTTP and etc.
    [Show full text]
  • Openmoko Free Your Phone
    Openmoko Free Your Phone Shakthi Kannan August 2008 Creative Commons Attribution-Share Alike 3.0 License Version 1.3 This talk will not be possible without ● FIC, Taiwan ● Openmoko Inc ● Free Software community ● Ole Tange (Openmoko presentation) ● Mukt.in ● Qvantel ● Myself chocolate sugar pistachios butter Chocolate eggs salt and water Pistachio Cake Chocolate Chip Cupcakes butter sugar flour eggs vanilla extract chocolate chips baking powder cocoa powder evaporated milk double nutella cupcakes whole wheat flour cocoa powder baking soda salt butter sugar eggs buttermilk milk vinegar coffee vanilla extract beatty's chocolate cake butter flour sugar cocoa powder baking soda baking powder salt buttermilk vegetable oil eggs vanilla extract brewed hot coffee chocolate egg yolk chocolate mocha trifle brownies whipped cream sugar chocolate pudding coffee granules almonds chocolate cake with hot chocolate fudge sugar flour hershey's coca baking soda eggs milk butter vanilla extract water Ingredients Crispy Layer (top) http://wiki.openmoko.org/wiki/Neo_FreeRunner_GTA02_Hardware Crispy Layer (back) http://wiki.openmoko.org/wiki/Neo_FreeRunner_GTA02_Hardware Black Current http://wiki.openmoko.org/wiki/Neo1973_as_radio_replacement Toppings http://wiki.openmoko.org/wiki/Getting_Started_with_your_Neo_FreeRunner Chocolate Fudge http://wiki.openmoko.org/wiki/Neo_FreeRunner_GTA02_Hardware Choco Chips Component Name Openness CPU Samsung S3C2442 Docs available after free registration NAND Samsung Standard NAND command-set GSM modem TI Calypso Speaks standard
    [Show full text]
  • Master Thesis “ the Geosharing Project: an Openmoko Geoposition
    Master Thesis \ The GeoSharing project: An Openmoko geoposition sharing system " June 2011 This document was presented to the Louvain School of Engineering in Partial Fulfilment of the Requirements for the Degree of MASTER IN COMPUTER ENGINEERING Supervisor: Pr. Marc Lobelle Authors: Lamouline Laurent Nuttin Vincent Universit´ecatholique de Louvain \ In theory, there is no difference between theory and practice; In practice, there is. " { Chuck Reid Nous remercions chaleureusement le Professeur Marc Lobelle, notre promoteur ainsi que S´ebastienComb´efiset Xavier Carpent pour leur guidance ´eclair´ee. Abstract Geo-positioning systems provide a way to locate objects or persons on Earth. Geo- positioning systems can be used in the scope of social networks allowing users to share their location at any time with their friends. They can also be used by rescue or military units. Because the GeoSharing project aims to provide a wireless real-time location system that can be deployed everywhere, independently of infrastructure and because nodes are susceptible to be in constant movement, the challenging part of this project is to maintain a consistent network topology in order to be able to reach each node at any time to share geographical positions. In order to fit more critical application fields, the system must also be secured. The first version of GeoSharing is released for Openmoko Neo FreeRunner devices. It provides a secured way to share geographical positions over a wireless network. The network topology management is assured by a Linux dæmon implementing the Optimized Link State Routing (OLSR) protocol which is suitable for Mobile Ad Hoc NETwork (MANET).
    [Show full text]
  • Open Mobile API: Accessing the UICC on Android Devices
    Technical Report Open Mobile API: Accessing the UICC on Android Devices Michael Roland Michael Hölzl University of Applied Sciences Upper Austria Johannes Kepler University Linz Josef Ressel Center u’smile Institute of Networks and Security [email protected] [email protected] Abstract This report gives an overview of secure element integration into Android devices. It focuses on the Open Mobile API as an open interface to access secure elements from Android applications. The overall architecture of the Open Mobile API is described and current Android devices are ana- lyzed with regard to the availability of this API. Moreover, this report summa- rizes our efforts of reverse engineering the stock ROM of a Samsung Galaxy S3 in order to analyze the integration of the Open Mobile API and the in- terface that is used to perform APDU-based communication with the UICC (Universal Integrated Circuit Card). It further provides a detailed explanation on how to integrate this functionality into CyanogenMod (an after-market firmware for Android devices). This work has been carried out within the scope of “u’smile”, the Josef Ressel Center for User-Friendly Secure Mobile Environments, funded by the Chris- tian Doppler Gesellschaft, A1 Telekom Austria AG, Drei-Banken-EDV GmbH, LG Nexera Business Solutions AG, NXP Semiconductors Austria GmbH, and Österreichische Staatsdruckerei GmbH in cooperation with the Institute of Net- works and Security at the Johannes Kepler University Linz. Moreover, this work has been carried out in close cooperation with the project “High Speed RFID” within the EU programme “Regionale Wettbewerbsfähigkeit OÖ 2007–2013 (Regio 13)” funded by the European Regional Development Fund (ERDF) and the Province of Upper Austria (Land Oberösterreich).
    [Show full text]
  • Digital Devices and the Information on Them
    Devices as Witnesses Greg Kelley, EnCE, DFCP Vestige Digital Investigations NALS of Northeast Ohio About Me • B.S. in Computer Engineering from CWRU • Computer forensics since 2001 • Examined thousands of computers for hundreds of matters • Testified in State and Federal Cases for plaintiff, prosecution and defense 800.314.4357 | www.VestigeLtd.com | Responsiveness, Speed & Availability Reliability Knowledge | Copyright ©2016 Vestige Ltd Digital Evidence 800.314.4357 | www.VestigeLtd.com | Responsiveness, Speed & Availability Reliability Knowledge | Copyright ©2016 Vestige Ltd More Digital Evidence! 800.314.4357 | www.VestigeLtd.com | Responsiveness, Speed & Availability Reliability Knowledge | Copyright ©2016 Vestige Ltd What to do? • It is quite daunting • You don’t know what you don’t know • Lack of resources 800.314.4357 | www.VestigeLtd.com | Responsiveness, Speed & Availability Reliability Knowledge | Copyright ©2016 Vestige Ltd Witnesses • Understand that digital devices are witnesses • Won’t lie • See things you may not realize • Can be misinterpreted 800.314.4357 | www.VestigeLtd.com | Responsiveness, Speed & Availability Reliability Knowledge | Copyright ©2016 Vestige Ltd What you can expect from Computers • Content • Keyword search for content/communication • ALL correspondence • Hidden information • Deleted information • Orphaned information • Encrypted information 800.314.4357 | www.VestigeLtd.com | Responsiveness, Speed & Availability Reliability Knowledge | Copyright ©2016 Vestige Ltd • Correspondence • Memos
    [Show full text]
  • The Most Common Mobile Operating Systems Are: Android from Google Inc. (Open Source, Apache) Blackberry OS from RIM
    The most common mobile operating systems are: Android from Google Inc. (open source, Apache) BlackBerry OS from RIM (closed source, proprietary) iOS from Apple Inc. (closed source, proprietary) Symbian OS from the Symbian Foundation (open public license) Windows Phone from Microsoft (closed source, proprietary) webOS from HP (certain parts open sourced) Android from Google Inc. (open source, Apache) Android was developed by a small startup company that was purchased by Google Inc. Released on November 5th 2007 Android is an open source, Linux-derived OS backed by Google, along with major hardware and software developers (such as Intel, HTC, ARM, Samsung, Motorola and eBay, to name a few) Android releases prior to 2.0 (1.0, 1.5, 1.6) were used exclusively on mobile phones. Android 3.0 was a tablet-oriented release and does not officially run on mobile phones. Android releases are nicknamed after sweets or dessert items like Cupcake (1.5), Frozen Yogurt (2.2), Honeycomb (3.0) and Ice Cream Sandwich (4.0). Most major mobile service providers carry an Android device. 1. What is Android? Android is a software platform and an operating system for mobile devices, The first device running Android is T-Mobile G1 officially released on October 22nd 2008. 2. I want to develop for Android. What are the basics I need to know? Android requires knowledge of Java programming language although it allows other programming languages (C C++for example) to be compiled in the native code. This however is not officially supported by Google. You can download SDK and get all the relevant info at http://code.google.com/android/index.html Make sure to checkout Android Developers forum for more tips at http://androidforums.com/a/ and/or share your experience with us.
    [Show full text]
  • CA OPS/MVS Event Management and Automation Administration Guide
    CA OPS/MVS® Event Management and Automation Administration Guide Release 12.1 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT.
    [Show full text]
  • Smartphone Operating Systems Feature Comparison
    Computer Applications Mobile Operating Systems (MOS) Prof: Muhammad Moazam Ali Group Name: Twinkle 2 By: Hassam Rasheed (Leader) BAT11327 Daniyal Ali BAT11362 Junaid Siddique BAT11318 Umair Tariq BAT11315 Mobile Operating System A mobile operating system, also known as a mobile OS, a mobile platform, or a handheld operating system, is the operating system that controls a mobile device or information appliance—similar in principle to an operating system such as Windows, Mac OS, or Linux that controls a desktop computer or laptop. However, they are currently somewhat simpler, and deal more with the wireless versions of broadband and local connectivity, mobile multimedia formats, and different input methods. Typical examples of devices running a mobile operating system are Smartphone, personal digital assistants (PDAs), tablet computers and information appliances, or what are sometimes referred to as smart devices, which may also include embedded systems, or other mobile devices and wireless devices. Today's mobile devices are multi-functional devices capable of hosting a broad range of applications for both business and consumer use. PDAs and the ever-growing category of smart phones allow people to access the Internet for e-mail, instant messaging, text messaging and Web browsing, as well as work documents, contact lists and more. Mobile devices are often seen as an extension to your own PC. Work done on the road or away from the office can be synchronized with your PC to reflect changes and new information. History The increasing importance of mobile devices has triggered intense competition among technology giants, like Google, Microsoft, Apple, and Nokia in a bid to capture the bigger market share pre-emptively.
    [Show full text]
  • Oracle Goldengate Performance Best Practices
    Oracle GoldenGate Performance Best Practices ORACLE WHITE PAPER | M A Y 2 0 1 7 Table of Contents Table of Contents 2 Introduction 4 Oracle Software 5 Database Configuration 5 Configuring the Source Database 5 Configuring the Target Database 8 Oracle GoldenGate Configuration 9 Extract Configuration 9 Data Pump Configuration 9 Replicat Configuration 13 Configure the GoldenGate Heartbeat Table 14 Database File System (DBFS) Configuration 16 Data Gathering for Oracle GoldenGate Performance 16 Oracle GoldenGate Performance Tuning Methodology 17 Conclusion 26 Appendix A – Oracle GoldenGate Performance Information Gathering 27 Oracle GoldenGate Latency 27 Determining Latency for Integrated Extract 27 Determining Latency for Integrated Replicat 27 Oracle GoldenGate Report Files and Error Logs 28 Automatic Workload Repository and Active Session History 28 CPU Data 29 2 | ORACLE GOLDENGATE PERFORMANCE BEST PRACTICES I/O Data 29 Oracle Streams Performance Advisor (Integrated Extract and Integrated Replicat) 30 Integrated Capture and Integrated Replicat Healthcheck 33 Appendix B – Considerations for Non-Integrated GoldenGate Replicat Processes 34 Use of BATCHSQL 34 Dividing Workload Between Multiple Replicats 35 Appendix C – Displaying Real-time SPADV Statistics 40 3 | ORACLE GOLDENGATE PERFORMANCE BEST PRACTICES Introduction The strategic integration of Oracle Exadata Database Machine and Oracle Maximum Availability Architecture (MAA) best practices (Exadata MAA) provides the best and most comprehensive Oracle Database availability solution. Oracle GoldenGate is a key component of MAA, providing a logical replication solution for fast platform migration and a near zero downtime solution for application and database upgrades. It complements the rest of Oracle’s MAA solution that tolerates failures and enables online maintenance and rolling upgrade through Oracle Real Application Clusters (Oracle RAC), Oracle Automatic Storage Management (Oracle ASM), and Oracle Active Data Guard.
    [Show full text]