A3 Upgrade Notes

Total Page:16

File Type:pdf, Size:1020Kb

A3 Upgrade Notes APROL R 4.0 - Installation APROL System A3 Upgrade Notes We reserve the right to change the contents of this manual without warning. The information contained herein is believed to be accurate as of the date of publication; however, Bernecker + Rainer Industrie-Elektronik Ges.m.b.H. makes no warranty, expressed or implied, with regards to the products or the documentation contained within this book. In addition, Bernecker + Rainer Industrie-Elektronik Ges.m.b.H. shall not be liable in the event of incidental or consequential damages in connection with or resulting from the furnishing, performance, or use of these products. The software names, hardware names, and trademarks used in this document are registered by the respective companies. The following documentation A3 Upgrade Notes (Version 3.09 / 23.09.2014) refers to APROL R 4.0 2014 Bernecker + Rainer Industrie-Elektronik Ges.m.b.H. The APROL System Installation manual group includes the following manuals A1 Release Notes A2 Getting Started A3 Upgrade Notes Order number of the APROL System installation manual group: MAAPINST40-ENG A3 Upgrade Notes Contents A3 Upgrade Notes V3.09 A3-1 Upgrade notes 1-1 1.1 Limitations in the current APROL release 1-2 1.1.1 Redundant controllers 1-2 1.1.2 KDE version 4.x 1-3 1.1.3 Use of an external sound card for APC 810 1-3 1.2 New features after updating to APROL R 4.0-08 1-1 1.2.1 Controller AR-OS versions 1-1 1.2.2 New features in the AutoYaST DVD V4.0-080 1-1 1.2.3 Compiling equipment and parameter set templates 1-2 1.2.4 Changes in the 'MonCtrlCpuRed01' hyper macro 1-2 1.3 New features after updating to APROL R 4.0-07 1-1 1.3.1 Controller AR-OS versions 1-1 1.3.2 New features in the AutoYaST DVD V4.0-070 1-1 1.3.3 Changing the JasperReport theme after an update 1-1 1.3.4 Display of company logos in the as-built documentation 1-2 1.3.5 Checks after an incorrect shutdown of an APROL server/system 1-2 1.3.6 Access of Historical Data via SQL 1-3 1.4 New features after updating to APROL R 4.0-06 1-4 1.4.1 Controller AR-OS versions 1-4 1.4.2 New features in the AutoYaST DVD V4.0-060 1-4 1.4.3 Access of Historical Data via SQL 1-4 1.4.4 Extended use of ST/SFC blocks in CFCs 1-5 1.5 New features after updating to APROL R 4.0-05 1-1 1.5.1 Controller AR-OS versions 1-1 1.5.2 Access of Historical Data via SQL 1-1 1.5.3 Uniform nomenclature for bit-coded system variables 1-1 1.5.4 Validity of the 'SysDataTransfer' transfer file 1-2 1.5.5 Selecting an APROL system in the ParameterCenter 1-2 1.6 New features after updating to APROL R 4.0-04 1-1 1.6.1 Controller AR-OS versions 1-1 1.6.2 New features in the AutoYaST DVD V4.0-040 1-1 1.6.3 Access of Historical Data via SQL 1-1 1.6.4 Replacement of APROL-specific constants from the 'runtime' AS library 1-2 1.6.5 Self ID for the 'EmbeddedApp' visualization element 1-2 1.7 New features after updating to APROL R 4.0-03 1-1 1.7.1 Controller AR-OS versions 1-1 1.7.2 AutoYaST DVD V4.0-030 update 1-1 1.7.3 System variables for downloads to controllers 1-2 1.7.4 Buffering and subsequent provision of log entries during a disturbed recording 1-2 iii 1.8 New features after updating to APROL R 4.0-02 1-1 1.8.1 Controller AR-OS versions 1-1 1.8.2 AutoYaST DVD V4.0-020 update 1-1 1.8.3 Configuration of the AprolJobDispatcher 1-2 1.8.4 Assignment of the minimum password length 1-2 1.8.5 Use of the 'AprolCaeRename' script 1-2 1.8.6 Provision of bit-coded system variables 1-2 1.8.7 Extension of the SNMP diagnosis for redundant controllers 1-4 1.8.8 Change of CSV export in the TranslationManager 1-4 1.8.9 Support of internal UPS modules for APC810/APC910 1-4 1.9 New features after updating to APROL R 4.0-01 1-1 1.9.1 Controller AR-OS versions 1-1 1.9.2 New features in the AutoYaST DVD V4.0-010 1-1 1.9.3 Driver for NVIDIA graphic cards 1-1 1.9.4 Update of the AprolSqlServer driver 1-2 1.9.5 Reactivation of all APROL systems 1-2 1.9.6 Use of the BR modules needed by the 'PAL' CAE library 1-2 1.9.7 Update of optional hardware upgrades 1-2 1.9.8 Creation of the exclude files for the optimization of the RRAD configuration framework 1-3 1.9.9 SVG check during an import into the image container 1-3 1.9.10 Library-spanning Export / Import of library blocks 1-4 1.9.11 SFC: Display of the live values for array variable elements 1-4 1.9.12 Preview of the 'Color' dynamization type 1-4 1.9.13 Filter function in the alarm report via APROL system 1-5 1.10 New features after updating to APROL R 4.0-00 1-1 1.10.1 Minimum release for an upgrade to APROL R 4.0-00 1-1 1.10.2 AutoYaST installation 1-1 1.10.3 Controller AR-OS versions 1-2 1.10.4 Use of different Automation Studio variations in one engineering environment 1-3 1.10.5 Change of VMware on Windows 7 Professional 1-3 1.10.6 Update of the MySQL version 1-3 1.10.7 Change of the logging path for trend data 1-5 1.10.8 Change of the database structure 1-6 1.10.9 Limitations with the names of customer-specific ChronoLog FIFOs and containers 1-7 1.10.10 Cancellation of the APROL 'DCS' library 1-7 1.10.11 Cleansing of the CAE library 'APROL' 1-7 1.10.12 Removal of old images from process graphics and graphic blocks 1-8 1.10.13 Switching of all icons to SVG format 1-8 1.10.14 Extension of the master data 1-8 1.10.15 Substitute blocks for discontinued blocks of the 'APROL' CAE library 1-9 1.10.16 Reactivation of the VNC configuration after an upgrade from APROL release < 3.6-08 1-10 1.10.17 Exchange of applications in the KDE 1-10 1.10.18 Discontinuation of the ChronoChartPrinter and the 'old' Iosys web interface applications 1-10 A3 Upgrade Notes iv 1.10.19 Provision of the cluster configuration for multi-runtime systems 1-10 1.10.20 Use of the new Intel graphic driver 1-11 1.10.21 Uniform syntax for system variables in the engineering and runtime environments 1-12 1.10.22 New 'Library Type Definition' project part 1-12 1.10.23 Change of the APROL services' TCP ports 1-13 1.10.24 Update of the VMware 1-13 1.10.25 Driver system variables 1-14 1.10.26 Recording rate for PDA blocks 1-14 1.10.27 Revision of the project and properties dialogs 1-15 1.10.28 BuR Gateway connection 1-15 1.10.29 Provision of further system variables 1-16 1.10.30 Handling hyper macro-intern variables 1-16 1.10.31 Re-definition of the image container of libraries within a project 1-17 1.10.32 Extension of the language switching 1-17 1.10.33 Simplified input of process variables and their respective Iosys connection 1-18 1.11 New features after updating to APROL R 3.6-10 1-19 1.11.1 Controller AR-OS versions 1-19 1.11.2 Substitution of the 'rint' function 1-19 1.11.3 Change of the AR structure from '3.6-06' to '3.6-08' 1-19 1.11.4 Use of an APC 910 / HP-Desktop 8300Elite-CMT 1-20 1.11.5 New features in the energy monitoring reports 1-20 1.11.6 Hardware PV global volatile 1-21 1.11.7 Update of the CAE database 1-21 1.12 New features after updating to APROL R 3.6-09 1-1 1.12.1 Controller AR-OS versions 1-1 1.12.2 Support of Intel Atom CPUs 1-1 1.12.3 Usage of the VMware workstation version 9.0.0 1-1 1.12.4 Manual setting of the link of the used PAL modules after an AR upgrade 1-2 1.12.5 Adoption of module dependencies is possible for B&R libraries 1-3 1.12.6 Integration of the EnergyMonitoring report 1-4 1.12.7 Additions to the SFC transition diagnosis 1-6 1.12.8 Clean-up directory before import 1-6 1.12.9 Automatic detection of the system directories is no longer supported 1-8 1.12.10 Extended configuration possibilities for the APROL shift logbook 1-8 1.13 New features after updating to APROL R 3.6-08 1-1 1.13.1 Controller AR-OS versions 1-1 1.13.2 Update to the current AutoYaST version 1-1 1.13.3 Consistency check of project part names 1-3 1.13.4 Problems when using the visualization 'TextView' element 1-5 1.13.5 Warning due to obsolete directory 1-5 1.13.6 Renewed password entry for existing users in the customer-specific MySQL databases 1-5 1.13.7 Update step for the SFC function blocks and programs 1-6 1.13.8 Maximum length for transition names 1-6 1.13.9 Locking of the control of an SFC with concurrent access 1-6 v 1.13.10 Use of the 'AsBrMath' library instead of 'AsMath' 1-6 1.14 New features after updating to APROL R 3.6-07 1-1 1.14.1 Optional installation of the PHP version 5.3 1-1 1.14.2 Controller AR-OS versions 1-3 1.14.3 Opening and saving all SFC programs and function blocks 1-3 1.14.4 Corrections to the UcbServer 1-4 1.14.5 Change to VMware version 8.0.1 1-4 1.15 New features after updating to APROL R 3.6-06 1-1 1.15.1 Controller AR-OS versions 1-1 1.15.2 Extended logging of interactions in alarm handling 1-1 1.16 New features after updating to APROL R 3.6-05 1-1 1.16.1 Controller AR-OS versions 1-1 1.16.2 Adjustment of the SFC logging function 1-1 1.16.3 New system variables for warning about not enough free hard-disk space1-1 1.16.4 Automatic configuration of the EventDriver 1-1 1.17 New features after updating to APROL R 3.6-04 1-1 1.17.1 Controller AR-OS and Visual Components versions 1-1 1.17.2 Configuration of a cluster for the process bus 1-1 1.17.3 Re-saving existing SFC function blocks 1-2 1.17.4 Use of an LDAP server for authentication 1-2 1.18 New features after updating to APROL R 3.6-03 1-1 1.18.1 Controller AR-OS versions 1-1 1.18.2 Use of the process graphic preview 1-1 1.18.3 Configuration of a guaranteed instance name 1-1 1.18.4 Display of the database connections 1-2 1.18.5 Necessary adjustments to existing SFCs from the Automation Studio 1-2 1.18.6 Discontinuation of the ChronoChartPrinter and the 'old' Iosys web interface 1-2 1.18.7 Provision of a KDE 'Service' configuration
Recommended publications
  • Vnote Documentation Release 1.11.1
    VNote Documentation Release 1.11.1 Le Tan Feb 13, 2019 User Documentation 1 Why VNote 3 1.1 What is VNote..............................................3 1.2 Why Another Markdown Wheel.....................................3 2 Getting Started 5 2.1 Main Interface..............................................5 2.2 Ready To Go...............................................7 3 Build VNote 9 3.1 Get the Source Code of VNote......................................9 3.2 Get Qt 5.9................................................9 3.3 Windows.................................................9 3.4 Linux...................................................9 3.5 MacOS.................................................. 10 4 Notes Management 13 4.1 Notebook................................................. 13 4.2 Folders.................................................. 14 4.3 Notes................................................... 14 5 Snippet 15 5.1 Snippet Management........................................... 15 5.2 Define A Snippet............................................. 16 5.3 Apply A Snippet............................................. 16 5.4 Examples................................................. 16 6 Magic Word 19 6.1 Built-In Magic Words.......................................... 19 6.2 Custom Magic Words.......................................... 20 6.3 Magic Word In Snippet.......................................... 21 7 Template 23 8 Themes and Styles 25 8.1 Themes.................................................. 25 8.2 Editor Styles..............................................
    [Show full text]
  • Can Libreoffice and Apache Openoffice Be Alternatives to MS-Office from Consumer's Perspective?
    2016 2 nd International Conference on Social, Education and Management Engineering (SEME 2016) ISBN: 978-1-60595-336-6 "Make It Possible" Study: Can LibreOffice and Apache OpenOffice Be Alternatives to MS-Office from Consumer's Perspective? Jun IIO 1,* and Shusaku OHGAMA 2 1Socio-informatics Dept. Faculty of Letters, Chuo University, 742-1 Higashinakano, Hachioji-shi, Tokyo, Japan 2Information Technology Dept. Information Systems Div., Sumitomo Electric Industries, Ltd., 4-5-33 Kitahama, Chuo-ku, Osaka-shi, Osaka, Japan *Corresponding author Keywords: Open-source software, LibreOffice, OpenOffice, Productivity suites. Abstract. There are many guidebooks which offer some instruction of using productivity suites, and most of them focus on Microsoft's Office (MS-Office,) because it is the dominant products in the market. However, we have some other productivity suites, such as LibreOffice and Apache OpenOffice, as the alternative of MS-Office. Therefore, we investigated whether such software could be used properly, within the content of the guidebooks which are widely used. In this paper, the results of our investigation show that the interoperability of such software has already reached a tolerable level from a practical perspective. Introduction Recently, we can find in bookstores many books for reference that provide guidelines on how to operate productivity suites. However, most of them only focus on Microsoft's Office suites (MS-Office,) because it has the largest market share in the world in the productivity software market. On the other hand, there are some other options, such as LibreOffice and Apache OpenOffice. In recent days, persons in businesses face some problems in using these productivity suites.
    [Show full text]
  • Referência Debian I
    Referência Debian i Referência Debian Osamu Aoki Referência Debian ii Copyright © 2013-2021 Osamu Aoki Esta Referência Debian (versão 2.85) (2021-09-17 09:11:56 UTC) pretende fornecer uma visão geral do sistema Debian como um guia do utilizador pós-instalação. Cobre muitos aspetos da administração do sistema através de exemplos shell-command para não programadores. Referência Debian iii COLLABORATORS TITLE : Referência Debian ACTION NAME DATE SIGNATURE WRITTEN BY Osamu Aoki 17 de setembro de 2021 REVISION HISTORY NUMBER DATE DESCRIPTION NAME Referência Debian iv Conteúdo 1 Manuais de GNU/Linux 1 1.1 Básico da consola ................................................... 1 1.1.1 A linha de comandos da shell ........................................ 1 1.1.2 The shell prompt under GUI ......................................... 2 1.1.3 A conta root .................................................. 2 1.1.4 A linha de comandos shell do root ...................................... 3 1.1.5 GUI de ferramentas de administração do sistema .............................. 3 1.1.6 Consolas virtuais ............................................... 3 1.1.7 Como abandonar a linha de comandos .................................... 3 1.1.8 Como desligar o sistema ........................................... 4 1.1.9 Recuperar uma consola sã .......................................... 4 1.1.10 Sugestões de pacotes adicionais para o novato ................................ 4 1.1.11 Uma conta de utilizador extra ........................................ 5 1.1.12 Configuração
    [Show full text]
  • Aligning Intent and Behavior in Software Systems: How Programs Communicate & Their Distribution and Organization
    © 2020 William B. Dietz ALIGNING INTENT AND BEHAVIOR IN SOFTWARE SYSTEMS: HOW PROGRAMS COMMUNICATE & THEIR DISTRIBUTION AND ORGANIZATION BY WILLIAM B. DIETZ DISSERTATION Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Science in the Graduate College of the University of Illinois at Urbana-Champaign, 2020 Urbana, Illinois Doctoral Committee: Professor Vikram Adve, Chair Professor John Regehr, University of Utah Professor Tao Xie Assistant Professor Sasa Misailovic ABSTRACT Managing the overwhelming complexity of software is a fundamental challenge because complex- ity is the root cause of problems regarding software performance, size, and security. Complexity is what makes software hard to understand, and our ability to understand software in whole or in part is essential to being able to address these problems effectively. Attacking this overwhelming complexity is the fundamental challenge I seek to address by simplifying how we write, organize and think about programs. Within this dissertation I present a system of tools and a set of solutions for improving the nature of software by focusing on programmer’s desired outcome, i.e. their intent. At the program level, the conventional focus, it is impossible to identify complexity that, at the system level, is unnecessary. This “accidental complexity” includes everything from unused features to independent implementations of common algorithmic tasks. Software techniques driving innovation simultaneously increase the distance between what is intended by humans – developers, designers, and especially the users – and what the executing code does in practice. By preserving the declarative intent of the programmer, which is lost in the traditional process of compiling and linking and building software, it is easier to abstract away unnecessary details.
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • Debian Stretch の インプットメソッドの現状
    Debian Stretch の インプットメソッドの現状 Ubuntu Japanese Team LibreOffice"#$%&' ()*+,-. /012 ● ()*+,-. ● Ubuntu Japanese Team3LibreOffice "#$%&' ● Ubuntu3LibreOffice34cit53Virtua78953:;T<38u=>ie ?@A ● B: CD EF G ● Hだの一般人 ● Debian MNOP,たのは Q99=R3Sar>e3<tch の頃でUUVWXYZ Z[ ● \に喋ったのD F G\_ `ab)c ● deDf,OgchijkードTU[UVWX Y[ ● hijDl,TU[ m\no ● tasks ● a7ternatives ● Ur)sこの辺の解vD*WXY – b,wxyx tasks のuvM*P-Iz, ● Ubuntu TDNOていないのでよく知りまXYZZ }ンケート ● `N,のインプットメソッドD_ – uim – B8us – 4cit5 ● 変換エンジンD_ – :9zc – ;nthR – SKK – その他 インストールと実行編 パッケージがインストールされる仕組み① ● インストール時に選 択する言語とデスク トップ環境で変わる パッケージがインストールされる仕組み② ● 日本語関連のtas! は次の$% – ta !-ja(a)* * ● インストール時に日本語を選択するとインストールされる ● .a)(a/* &'a01230145t*6.017)849)t01)!401.a)(a/* &'a&:*3 – ta !-ja(a)* *&:* !t9( ● インストール時に日本語とデスクトップ環境を選択するとインストールさ れる ● ;6*49<&* 6&2=>)&'a1?1;6*49<&2=>)&'a0149)t &32/9t@8A0149nt &8(a49nt0178.01 78.-ant@B0178.&.9CA01.9CA&7t82 &/7801a)t@B012856*9DA*&2=>)&'a01 2856*9DA*&@*2(&'a01(9((2*6-data パッケージがインストールされる仕組み③ – ta !&'a(a)* *&/)9.*&:* !t9( ● インストール時にEFGHIを選択するとインストールされる ● 78.&a((2*t&/)9.*018A*:93*018A*:93*&2=>)&ja – ta !&'a(a)* *&!:*&:* !t9( ● インストール時にJKIを選択するとインストールされる ● !:*&2=>)&ja01pla .a&L8:/*t&78. ● 8.&A9);/"28578.&dataにMNOP-てインストールされる ● R57)t7"STUVNWXYZ+[\]Qいる – 2a)/7a/*& 7((96t 自動実行の仕組み ● 8.&A9);/ – _`ab^cdae先的に起動する ● j7 6j @a6*j8.&A9);/j – :atajk=l857 m – :atajkkl4cit<m – :atajk$l78.m インプットメソッドの切り替え 各デスクトップ環境編 EFGHI1n@*22の場合 ● 英語キーボードと日本$¡&¢&ドが認識されている – 英語キーボードが認識されないこb¥(OH ● ¦§3¨§¡&M©Ub"#語の入力は¬­Tある ● uimのステータスは¨-)xら± – uim²t99lbarプロセスはある – 3usr3bin3uim-t997barDalternatiqesで管理されている – su=9
    [Show full text]
  • Peng Wu Software Engineer
    Wayland intro and ibus support Presented by Peng Wu Software Engineer License statement goes here. See https://fedoraproject.org/wiki/Licensing#Content_Licenses for acceptable licenses. Today's Topics 1. wayland intro 2. ibus wayland support wayland intro X Window History X originated at the MIT in 1984 Since then, never touched the core protocol Why not X? parts of the core protocol seldom used today X11 core graphics functionality seldom used XIM protocol bypassed by input method frameworks, such as ibus, scim, fcitx. wayland intro RPC mechanism designed for window system Utility functions for client/server development Generate codes from XML protocol definition some client/server codes for communicating with the display server. Define the core wayland protocol in protocol/wayland.xml weston display server The Reference Wayland Compositor Reference Implementation Support additionally protocols in weston/protocol Maybe we could call these as extensions? For input method support See text.xml and input-method.xml ibus wayland support ibus intro Bus-Centric Architecture It has an ibus-daemon, which manages all clients. all engines, panel, config modules & clients are clients of ibus-daemon. iBus is base on dbus IPC protocol. ibus architecture ibus panel UI Application (GTK+) ibus engine pinyin Application ibus (QT) daemon ibus engine anthy ibus XIM Server ibus config Advantage of iBus iBus uses dbus RPC for communication. Clients can use any languages to communicate with ibus Engines can be wrote by any languages The daemon, engines, clients & UI, all partitions are running in separated processes One of them has problem, it will not impact all system All partitions can be restarted on the fly.
    [Show full text]
  • Editor Rozložení Klávesnice Pro X Window
    Univerzita Pardubice Fakulta elektrotechniky a informatiky Editor rozložení klávesnice pro X Window Bc. Viktor Grešák Diplomová práce 2019 Prohlašuji: Tuto práci jsem vypracoval samostatně. Veškeré literární prameny a informace, které jsem v práci využil, jsou uvedeny v seznamu použité literatury. Byl jsem seznámen s tím, že se na moji práci vztahují práva a povinnosti vyplývající ze zákona č. 121/2000 Sb., autorský zákon, zejména se skutečností, že Univerzita Pardubice má právo na uzavření licenční smlouvy o užití této práce jako školního díla podle § 60 odst. 1 autorského zákona, a s tím, že pokud dojde k užití této práce mnou nebo bude poskytnuta licence o užití jinému subjektu, je Univerzita Pardubice oprávněna ode mne požadovat přiměřený příspěvek na úhradu nákladů, které na vytvoření díla vynaložila, a to podle okolností až do jejich skutečné výše. Beru na vědomí, že v souladu s § 47b zákona č. 111/1998 Sb., o vysokých školách a o změně a doplnění dalších zákonů (zákon o vysokých školách), ve znění pozdějších předpisů, a směrnicí Univerzity Pardubice č. 9/2012, bude práce zveřejněna v Univerzitní knihovně a prostřednictvím Digitální knihovny Univerzity Pardubice. V Pardubicích dne 15. 5. 2019 Bc. Viktor Grešák Poděkování Děkuji vedoucímu diplomové práce Mgr. Tomáši Hudcovi za cenné rady a připomínky, které pomohly tuto práci vytvořit. Také děkuji své rodině, mé přítelkyni a přátelům za podporu. ANOTACE Práce se zabývá analýzou editorů rozložení klávesnice. Je vypracován přehled způsobů, kterými lze měnit rozložení klávesnice v grafickém prostředí X Window s ohledem na XKB. Hodnotí a porovnává existující editory klávesnic. Je vytvořen nový editor rozložení klávesnice pro X Window.
    [Show full text]
  • Pannenhilfe - Was Tun, Wenn GNU/Linux Doch Mal „Hängt“?
    FreieSoftwareOG – Pannenhilfe - Was tun, wenn GNU/Linux doch mal „hängt“? Abstürze? Mit GNU/Linux?? Im Allgemeinen sagt man GNU/Linux nach, äußerst stabil zu laufen. Allerdings wissen wir alle, dass auch dieses System auf Menschen basiert, und dementsprechend eventuelle Probleme auftauchen können... Auch der Tux schießt sich mal ab... Absturz - Lösungsvorschläge xxx... ● xxx ● xxx Aufgehängtes Programm mit xkill killen Vom Desktop aus sollte der erste Versuch sein, das zickige Programm mit dem „Ausführen-Befehl“ des jeweiligen Fenstermanagers und der Eingabe von „xkill“ zu beenden. Unter Ubuntu / Linux Mint ist dies z.B. Alt + F2. Mit dem erscheinenden Fadenkreuz kann das entsprechende Fenster dann „abgeschossen“ werden. Xkill tötet sofort und ohne Fragen zu stellen! Eingefrorenes Linux über virtuelle Konsole wiederbeleben Manchmal hat man kein Glück und das System scheint komplett tot zu sein. Das ist aber möglicherweise eine Illusion. Es scheint, als sei „X“ die Basis des User-Stacks. Aber das ist es nicht. Das X Window System läuft in einer Virtuellen Konsole (VC), auch TTY genannt. Diese werden im Dateisystem unter /dev/ttyX geführt. Und GNU/Linux hat davon einige zu bieten. Zugriff auf eine weitere Konsole kann dem Benutzer die Kontrolle über das System zurückgeben. Linux API by Shmuel Csaba Otto Traian; GNU FDL 1.2+ and CC-BY-SA 3.0+; created 2013-11-01 High levels KDE SC GNOME PiTiVi, of the Application software (free and open-source & propiretary) Xfce OpenShot, LXDE user stack Cinelerra OpenStack controller- Sound Graphics Input
    [Show full text]
  • Computer Engineering Subject
    DIRECTORATE OF TECHNICAL EDUCATION, CHENNAI-25 DIPLOMA EXAMINATIONS-APRIL-2019 DEPT : COMPUTER ENGINEERING SUBJECT : MOBILE COMPUTING QCODE/SUB CODE : 915/35262 PART -A 1. Define LAN.[ 2 marks] A local-area network (LAN) is a computer network that spans a relatively small area. Most often, LAN is confined to a single room, building or group of buildings, however, one LAN can be connected to other LANs over any distance via telephone lines and radio waves. 2. What is meant by Adhoc? [ 2 marks] An ad hoc network is a network that is composed of individual devices communicating with each other directly. The term implies spontaneous or impromptu construction because these networks often bypass the gatekeeping hardware or central access point such as a router 3. What is GSM network? [ 2 marks] GSM stands for Global System for Mobile Communication. GSM is the most widely accepted standard in telecommunications and it is implemented globally. It is a digital cellular technology used for transmitting mobile voice and data services. 4. Write the limitation of GPRS. [ 2 marks] Although GPRS will provide better data rates than is currently available, there are some limitations. • Speeds of 177.2kbps would require a user to use all eight timeslots without any error protection - which simply won't happen. Initial terminals are likely to use only 1-3 timeslots anyway, limiting the available bandwidth to a GPRS user. • When GPRS packets are sent to a destination they are sent in all different directions - allowing for the potential for one or some of those packets to be corrupted or even lost altogether during the data transmission over the radio link.
    [Show full text]
  • Ace of Spades Protocol Buildandshoot
    Ace Of Spades Protocol Buildandshoot Leptosporangiate Hercules foul-up or pearl some ceria erewhile, however proved Noland compliments snidely or interspersing. Duffy usually bestudded inside-out or hospitalize barelegged when unionized Schuyler inputs colonially and torpidly. Cameron ousts perchance. It is also a versatile vector drawing program. List all of a small yet versatile document centric objects. That helps you do this is an api functions. When everything takes place on the unbreakable layer you lose the ability to trench. Icarus verilog simulation and preserving the ace of spades protocol buildandshoot. The Parted package is a disk partitioning and partition resizing tool. Algeria s detailným dezénom na lapidação do with ace of spades protocol buildandshoot. Now needs no other games are sorted in. Its library used key, looks pretty nice deal with ace of mlt is. No but stumped when possible with ace of spades protocol buildandshoot. The drama of spades for reading and a modern hardware mplayer: protect the ace of spades protocol buildandshoot. Ethiopia theme libya sofia jamora sports illustrated free to connect to change the ace of spades protocol buildandshoot. Macbook Pro mbpfan: laptops. Leafpad is the alsa oss package contains a disk reporting that means of ace of spades protocol buildandshoot. All maps except for random and classicgen have been removed to slim the download size down. There are a few leaks in places. Its earliest incarnation was very ineffective and tended to get legitimate players banned. SSVNC can make SSL encrypted VNC connections to any ssvnc: VNC Server if they are running an SSL tunnel, debugging programs that generate binary file formats tweak: incorrectly, implemented in userspace.
    [Show full text]
  • Linux Input Method について
    Linux Input Method Frameworks and Engines Manabu Sumioka 2020 年 11 月 15 日 目次 1 ユーザーと入力メソッド (IM) 2 1.1 入力には,フレームワークとエンジンの 2 つが関っている .................... 4 1.2 Input method frameworks, フレームワーク ........................... 4 1.3 Input method engines, エンジン ................................. 4 2 Debian の input method farmeworks と engines 2020/09/15 5 2.1 IBus (Intelligent Input Bus) ................................... 5 2.2 Fcitx (Free Chinese Input Toy for X) .............................. 5 2.3 uim (Universal Input Method) .................................. 5 2.4 anthy ................................................ 6 2.5 mozc ................................................ 6 2.6 kkc ................................................. 6 2.7 skk ................................................. 7 3 InputMethod 群 7 3.1 Input Method Frameworks .................................... 7 3.2 Input Method Engines for ibus ................................. 7 3.3 Gnome and ibus .......................................... 8 3.4 SCIM - Smart Common Input Method ............................. 8 3.5 インストールした IME を動作させる方法 ............................. 8 3.6 Gnome と non-ibus ........................................ 8 3.7 im-config .............................................. 9 付録 A ユーザー群 9 A.1 LMDE 4 (debbie) の例 ...................................... 9 付録 B システム情報 10 B.1 現在利用中のシステム情報 (System Information) ........................ 10 B.2 センサー .............................................. 10 1 B.3 CPU 情報 ............................................. 11 B.4 ハードウェア情報
    [Show full text]