The Linux Foundation Announces Project to Advance Real-Time Linux

Altera, ARM, Google, Intel, IBM, National Instruments, OSADL, Texas Instruments and Others to Advance Mainline Kernel Support of Real-Time Linux, Saving Millions in Research and Development

DUBLIN, IRELAND, Oct 05, 2015 (Marketwired via COMTEX) -- LinuxCon Europe and Embedded Linux Conference Europe -- The Linux Foundation, the nonprofit organization dedicated to accelerating the growth of Linux and collaborative development, today announced the new Real-Time Linux (RTL) Collaborative Project. RTL will bring together industry leaders and experts to advance and maximize technologies for the robotics, telecom, manufacturing, aviation and medical industries, among others.

The RTL kernel supports the largest range of architectures of any operating system and can leverage Linux device drivers, file systems and more from the mainline kernel. Real-time properties make it possible to control robots, data acquisition systems, manufacturing plants and other time-sensitive instruments and machines from RTL applications. It provides the critical infrastructure for some of the world's most complex computing systems.

Google is a founding Platinum member of this work. Gold members include National Instruments, OSADL and Texas Instruments; and silver members include Altera, ARM, Intel and IBM. RTL's Thomas Gleixner, who has been maintaining the RTL branch for more than a decade, will become a Linux Foundation Fellow to dedicate even more time to his work on RTL. He joins other Linux Foundation Fellows, including Linux kernel stable maintainer, Greg Kroah-Hartman, embedded Linux developer and Yocto Project maintainer, Richard Purdie, and Linux creator, Linus Torvalds. Gold member OSADL has been actively involved in supporting Gleixner's work.

"The work we've been doing on Real-Time Linux has been critical in advancing complex real-time computing systems. But technology is moving fast, and the RTL project, with support from across the industry, will allow us to sustain this work and successfully integrate with the mainline kernel for long-term support of these technologies," said Thomas Gleixner, Linux kernel developer and Linux Foundation Fellow.

"Code that is built and maintained collaboratively is better and less expensive than software that is not," said Jim Zemlin, executive director at The Linux Foundation. "By coming together to advance Real-Time Linux as a community, products and systems will be supported by the best developers in the world for years to come."

The RTL Collaborative Project will focus on pushing critical code upstream to be reviewed and eventually merged into the mainline Linux kernel where it will receive ongoing support. This will save the industry millions of dollars in research and development. It will also improve quality of the code through robust upstream kernel test infrastructure, since anything maintained in the mainline kernel is collectively supported by thousands of developers and hundreds of companies around the world. The Project will conduct a quarterly code plan review, meet face-to-face at least twice a year at Embedded Linux Conference and contribute to testing and documentation of the project.

For more information about the RTL Collaborative Project, please visit:https://www.linuxfoundation.org/collaborate/workgroups/real-time

Member Comments Altera

"Contributing upstream to the Linux kernel is a critical element of Altera's open source strategy," says Vicki Mitchell, Director of Software Engineering, Heterogeneous Programming Group. "Upstreaming Preempt RT into the mainline kernel provides significant benefits including support for a broader range of applications." Altera's contribution to kernel code ensures Linux developers can work on Altera's architectures, SoCFPGA and NiiosII. Altera's contributions don't stop there, however," said Mitchell. "The ability to collaborate with like-minded developers, customers and partners within the Linux community in a synergistic manner ensures the longevity of Linux and is paramount to Altera and its customers' success in the marketplace."

ARM "We see ARM technology being deployed in an increasing range of applications, such as networking infrastructure, where Linux is a core technology," said Charlene Marini, vice president, segment marketing, ARM. "The Real-Time Linux Collaborative Project will enable the ARM ecosystem to further optimize their products with increased confidence in the long-term support from upstream Linux kernel."

Intel "As a leading contributor to Linux, Intel is excited to be a part of the Real-Time Linux project and participate in the long-term success of the project. Linux's prevalence as an operating system for embedded platforms and new devices will help applications with real-time requirements, giving us confidence in its long-term support," said Mark Sharpness, director of Embedded Software, Open Source Technology Center at Intel Corporation.

National Instruments "By collaborating with The Linux Foundation through the Real-Time Linux Collaborative Project, we are able to make an informed investment to ensure the continued success of an open source project which will enhance future generations of our devices," said Omid Sojoodi, Vice President of R&D for Application and Embedded Software at National Instruments. "Having this patchset upstream will make Linux a first-class RTOS out of the box."

OSADL

"We've been supporting Real-Time Linux for a long time and look forward to transferring our funding activities to the newly founded Linux Foundation RTL project. In addition to funding Real-Time Linux, we will continue to help the industry deploy it in products through training, quality assurance, safety processes and legal support," said Carsten Emde, General Manager, OSADL.

Texas Instruments "Thomas Gleixner's work on Real-time Linux has been an integral part of our customers' development process, and with TI's commitment to RTL, we're thrilled to see what advancements will come now that he can dedicate more time to further improving and integrating it with the mainline kernel," Jon Humphreys, Linux Core Product Development Director, Texas Instruments.

About The Linux Foundation The Linux Foundation is a nonprofit consortium dedicated to fostering the growth of Linux and collaborative software development. Founded in 2000, the organization sponsors the work of Linux creator Linus Torvalds and promotes, protects and advances the Linux operating system and collaborative software development by marshaling the resources of its members and the open source community. The Linux Foundation provides a neutral forum for collaboration and education by hosting Collaborative Projects, Linux conferences, including LinuxCon, and generating original research and content that advances the understanding of Linux and collaborative software development. More information can be found at http://www.linuxfoundation.org.

The Linux Foundation and Linux Standard Base are trademarks of The Linux Foundation. Linux is a trademark of Linus Torvalds.

Media Contact
Jennifer Cloer
The Linux Foundation
503-867-2304
Jennifer@linuxfoundation.org

SOURCE: The Linux Foundation

Unix Timeline

1969	The Beginning	The history of UNIX starts back in 1969, when Ken Thompson, Dennis Ritchie and others started working on the "little-used PDP-7 in a corner" at Bell Labs and what was to become UNIX.
1971	First Edition	It had a assembler for a PDP-11/20, file system, fork(), roff and ed. It was used for text processing of patent documents.
1973	Fourth Edition	It was rewritten in C. This made it portable and changed the history of OS's.
1975	Sixth Edition	UNIX leaves home. Also widely known as Version 6, this is the first to be widely available out side of Bell Labs. The first BSD version (1.x) was derived from V6.
1979	Seventh Edition	It was a "improvement over all preceding and following Unices" [Bourne]. It had C, UUCP and the Bourne shell. It was ported to the VAX and the kernel was more than 40 Kilobytes (K).
1980	Xenix	Microsoft introduces Xenix. 32V and 4BSD introduced.
1982	System III	AT&T's UNIX System Group (USG) release System III, the first public release outside Bell Laboratories. SunOS 1.0 ships. HP-UX introduced. Ultrix-11 Introduced.
1983	System V	Computer Research Group (CRG), UNIX System Group (USG) and a third group merge to become UNIX System Development Lab. AT&T announces UNIX System V, the first supported release. Installed base 45,000.
1984	4.2BSD	University of California at Berkeley releases 4.2BSD, includes TCP/IP, new signals and much more. X/Open formed.
1984	SVR2	System V Release 2 introduced. At this time there are 100,000 UNIX installations around the world.
1986	4.3BSD	4.3BSD released, including internet name server. SVID introduced. NFS shipped. AIX announced. Installed base 250,000.
1987	SVR3	System V Release 3 including STREAMS, TLI, RFS. At this time there are 750,000 UNIX installations around the world. IRIX introduced.
1988		POSIX.1 published. Open Software Foundation (OSF) and UNIX International (UI) formed. Ultrix 4.2 ships.
1989		AT&T UNIX Software Operation formed in preparation for spinoff of USL. Motif 1.0 ships.
1989	SVR4	UNIX System V Release 4 ships, unifying System V, BSD and Xenix. Installed base 1.2 million.
1990	XPG3	X/Open launches XPG3 Brand. OSF/1 debuts. Plan 9 from Bell Labs ships.
1991		UNIX System Laboratories (USL) becomes a company - majority-owned by AT&T. Linus Torvalds commences Linux development. Solaris 1.0 debuts.
1992	SVR4.2	USL releases UNIX System V Release 4.2 (Destiny). October - XPG4 Brand launched by X/Open. December 22nd Novell announces intent to acquire USL. Solaris 2.0 ships.
1993	4.4BSD	4.4BSD the final release from Berkeley. June 16 Novell acquires USL
Late 1993	SVR4.2MP	Novell transfers rights to the "UNIX" trademark and the Single UNIX Specification to X/Open. COSE initiative delivers "Spec 1170" to X/Open for fasttrack. In December Novell ships SVR4.2MP , the final USL OEM release of System V
1994	Single UNIX Specification	BSD 4.4-Lite eliminated all code claimed to infringe on USL/Novell. As the new owner of the UNIX trademark, X/Open introduces the Single UNIX Specification (formerly Spec 1170), separating the UNIX trademark from any actual code stream.
1995	UNIX 95	X/Open introduces the UNIX 95 branding programme for implementations of the Single UNIX Specification. Novell sells UnixWare business line to SCO. Digital UNIX introduced. UnixWare 2.0 ships. OpenServer 5.0 debuts.
1996		The Open Group forms as a merger of OSF and X/Open.
1997	Single UNIX Specification, Version 2	The Open Group introduces Version 2 of the Single UNIX Specification, including support for realtime, threads and 64-bit and larger processors. The specification is made freely available on the web. IRIX 6.4, AIX 4.3 and HP-UX 11 ship.
1998	UNIX 98	The Open Group introduces the UNIX 98 family of brands, including Base, Workstation and Server. First UNIX 98 registered products shipped by Sun, IBM and NCR. The Open Source movement starts to take off with announcements from Netscape and IBM. UnixWare 7 and IRIX 6.5 ship.
1999	UNIX at 30	The UNIX system reaches its 30th anniversary. Linux 2.2 kernel released. The Open Group and the IEEE commence joint development of a revision to POSIX and the Single UNIX Specification. First LinuxWorld conferences. Dot com fever on the stock markets. Tru64 UNIX ships.
2001	Single UNIX Specification, Version 3	Version 3 of the Single UNIX Specification unites IEEE POSIX, The Open Group and the industry efforts. Linux 2.4 kernel released. IT stocks face a hard time at the markets. The value of procurements for the UNIX brand exceeds $25 billion. AIX 5L ships.
2003	ISO/IEC 9945:2003	The core volumes of Version 3 of the Single UNIX Specification are approved as an international standard. The "Westwood" test suite ship for the UNIX 03 brand. Solaris 9.0 E ships. Linux 2.6 kernel released.
2007		Apple Mac OS X certified to UNIX 03.
2008	ISO/IEC 9945:2008	Latest revision of the UNIX API set formally standardized at ISO/IEC, IEEE and The Open Group. Adds further APIs
2009	UNIX at 40	IDC on UNIX market -- says UNIX $69 billion in 2008, predicts UNIX $74 billion in 2013
2010	UNIX on the Desktop	Apple reports 50 million desktops and growing -- these are Certified UNIX systems.

History of the UNIX operating system

The first version of UNIX was created in 1969 by Kenneth Thompson and Dennis Ritchie, system engineers at AT&T's Bell Labs. It went through many revisions and gained in popularity until 1977, when it was first made commercially available by Interactive Systems Corporation.
At the same time a team from the University of California at Berkeley was working to improve UNIX. In 1977 it released the first Berkeley Software Distribution, which became known as BSD. Over time this won favour through innovations such as the C shell.
Meanwhile the AT&T version was developing in different ways. The 1978 release of Version 7 included the Bourne Shell for the first time. By 1983 commercial interest was growing and Sun Microsystems produced a UNIX workstation. System V appeared, directly descended from the original AT&T UNIX and the prototype of the more widely used variant today. Modern variants of UNIX


Since it began to escape from AT&T's Bell Laboratories in the early 1970's, the success of the UNIX operating system has led to many different versions: recipients of the (at that time free) UNIX system code all began developing their own different versions in their own, different, ways for use and sale. Universities, research institutes, government bodies and computer companies all began using the powerful UNIX system to develop many of the technologies which today are part of a UNIX system.
Computer aided design, manufacturing control  systems, laboratory simulations, even the Internet itself, all began life with and because of UNIX systems. Today, without UNIX systems, the Internet would come to a screeching halt. Most telephone calls could not be made, electronic commerce would grind to a halt and there would have never been "Jurassic Park"!
By the late 1970's, a ripple effect had come into play. By now the under- and post-graduate students whose lab work had pioneered these new applications of technology were attaining management and decision-making positions inside the computer system suppliers and among its customers. And they wanted to continue using UNIX systems.
Soon all the large vendors, and many smaller ones, were marketing their own, diverging, versions of the UNIX system optimized for their own computer architectures and boasting many different strengths and features. Customers found that, although UNIX systems were available everywhere, they seldom were able to interwork or co-exist without significant investment of time and effort to make them work effectively. The trade mark UNIX was ubiquitous, but it was applied to a multitude of different, incompatible products.
In the early 1980's, the market for UNIX systems had grown enough to be noticed  by industry analysts and researchers. Now the question was no longer "What is a UNIX system?" but "Is a UNIX system suitable for business and commerce?"
Throughout the early and mid-1980's, the debate about the strengths and weaknesses of UNIX systems raged, often fuelled by the utterances of the vendors themselves who sought to protect their profitable proprietary system sales by talking UNIX systems down. And, in an effort to further differentiate their competing UNIX system products, they kept developing and adding features of their own.
In 1984, another factor brought added attention to UNIX systems. A group of vendors concerned about the continuing encroachment into their markets and control of system interfaces by the larger companies, developed the concept of "open systems."
Open systems were those that would meet agreed specifications or standards. This resulted in the formation of X/Open Company Ltd whose remit was, and today in the guise of The Open Group remains, to define a comprehensive open systems environment. Open systems, they declared, would save on costs, attract a wider portfolio of applications and competition on equal terms. X/Open chose the UNIX system as the platform for the basis of open systems.
Although UNIX was still owned by AT&T, the company did little commercially with it until the mid-1980's. Then the spotlight of X/Open showed clearly that a single, standard version of the UNIX system would be in the wider interests of  the industry and its customers. The question now was, "which version?".
In a move intended to unify the market in 1987, AT&T announced a pact with Sun Microsystems, the leading proponent of the Berkeley derived strain of UNIX. However, the rest of the industry viewed the development with considerable concern. Believing that their own markets were under threat they clubbed together to develop their own "new" open systems operating system. Their new organization was called the Open Software Foundation (OSF). In response to this, the AT&T/Sun faction formed UNIX International.
The ensuing "UNIX wars" divided the system vendors between these two camps clustered around the two dominant UNIX system technologies: AT&T's System V and the OSF system called OSF/1. In the meantime, X/Open Company held the center ground. It continued the process of standardizing the APIs necessary for an open operating system specification.
In addition, it looked at areas of the system beyond the operating system level where a standard approach would add value for supplier and customer alike, developing or adopting specifications for languages, database connectivity, networking and mainframe interworking. The results of this work were published in successive X/Open Portability Guides.
XPG 4 was released in October 1992. During this time, X/Open had put in place a brand program based on vendor guarantees and supported by testing. Since the publication of XPG4, X/Open has continued to broaden the scope of open systems specifications in line with market requirements. As the benefits of the X/Open brand became known and understood, many large organizations began using X/Open as the basis for system design and procurement. By 1993, over $7 billion had been spent on X/Open branded systems. By the start of 1997 that figure has risen to over $23 billion. To date, procurements referencing the Single UNIX Specification amount to over $5.2 billion.
In early 1993, AT&T sold it UNIX System Laboratories to Novell which was looking for a heavyweight operating system to link to its NetWare product range. At the same time, the company recognized that vesting control of the definition (specification) and trademark with a vendor-neutral organization would further facilitate the value of UNIX as a foundation of open systems. So the constituent parts of the UNIX System (source code/technology and specification/trademark), previously owned by a single entity are now quite separate
In 1995 X/Open introduced the UNIX 95 brand for computer systems guaranteed to meet the Single UNIX Specification. The Single UNIX Specification brand program has now achieved critical mass: vendors whose products have met the demanding criteria now account for the majority of UNIX systems by value.
For over twenty years, since the inception of X/Open, UNIX had been closely linked with open systems. X/Open, now The Open Group, continues to develop and evolve the Single UNIX Specification and associated brand program on behalf of the IT community. The freeing of the specification of the interfaces from the technology is allowing many systems to support the UNIX philosophy of small, often simple tools , that can be combined in many ways to perform often complex tasks. The stability of the core interfaces preserves existing investment, and is allowing development of a rich set of software tools. The Open Source movement is building on this stable foundation and is creating a resurgence of enthusiasm for the UNIX philosophy. In many ways Open Source can be seen as the true delivery of Open Systems that will ensure it continues to go from strength to strength.

Understand how servers work and you will know.

Ever wondered how important Google's servers are to the world? Understand how servers work and you will know.  Rate this news:  (1 Votes)

Tuesday, February 18, 2014:  It is safe to say that the world right now is running on a bunch of servers. Whether it be Google, Microsoft or any other big technology firm. A click of a mouse results into a request sent to a server, which in turn results in information being sent across to you. So, as developers and programmers, it is important to learn about servers, their role in computing and how to work with them. Here are resources that will help you do so. Cheers! 1. Microsoft Exchange Server 2013 Pocket Consultant: Databases, Services, & Management Portable and precise, this pocket-sized guide delivers ready answers for managing databases and services in Exchange Server 2013. Zero in on core tasks through quick-reference tables, instructions, and lists. You'll get the focused information you need to save time and get the job done-whether at your desk or in the field. 2. Nginx HTTP Server, 2nd Edition Nginx is a lightweight HTTP server designed for high-traffic websites, with network scalability as the primary objective. With the advent of high speed Internet access, short loading times and fast transfer rates have become a necessity. This free, open source solution will either come as a full replacement of other software such as Apache, or stand in front of your existing infrastructure to improve its overall speed. Nginx HTTP Server, 2nd Edition provides a detailed guide to setting up Nginx in different ways that correspond to actual production situations: as a standalone server, as a reverse proxy, interacting with applications via FastCGI and more. In addition, the complete directive reference will be your best friend at all stages of the configuration and maintenance processes. 3. Introducing Windows Server 2012 R2 Get a head start evaluating Windows Server 2012 R2 - with technical insights from a Microsoft MVP and members of the Windows Server product team. Based on final Windows Server 2012 R2 release-to-manufacturing (RTM) software, this guide introduces new features and capabilities, with scenario-based advice on how the platform can meet the needs of your business. Get the high-level overview you need to begin preparing your deployment now. 4. Microsoft Exchange Server 2013 Inside Out: Mailbox and High Availability With a focus on mailbox and high availability features, this book delivers the ultimate, in-depth reference to IT professionals planning and managing an Exchange Server 2013 deployment. Guided by Tony Redmond, a Microsoft MVP and award-winning author, you will: Understand major changes to Exchange Server architecture; Get inside insights for planning your upgrade or deployment; Examine the new web-based Exchange admin center (EAC); Take a deep dive into configuring mailboxes, distribution groups, and contacts; planning and managing the Managed Store; database availability groups; mailbox replication service; compliance, data leakage, and data loss prevention; site mailboxes; modern public folders. 5. Microsoft Exchange Server 2013 Inside Out: Connectivity, Clients, and UM With a focus on connectivity, clients, and unified messaging, this book delivers the ultimate, in-depth reference to IT professionals planning and managing an Exchange Server 2013 deployment. Guided by Paul Robichaux, a Microsoft MVP and popular author, you will: Understand how Exchange Server 2013 works with previous versions; Gain expert insights into supporting clients, mobile devices, and UM; Take a deep dive into front-end servers; certificate and namespace management; transport rules; load balancing; client management, including Microsoft Outlook, Outlook Web App (OWA), and POP3/IMAP4; mobile devices; anti-malware and anti-spam features; Unified Messaging; Microsoft Lync; Office 365; Exchange Online. 6. Intel Trusted Execution Technology for Server Platforms Intel Trusted Execution Technology (Intel TXT) is a new security technology that started appearing on Intel server platforms in 2010. This book explains Intel Trusted Execution Technology for Servers, its purpose, application, advantages, and limitations. This book guides the server administrator / datacenter manager in enabling the technology as well as establishing a launch control policy that he can use to customize the server's boot process to fit the datacenter's requirements. This book explains how the OS (typically a Virtual Machine Monitor or Hypervisor) and supporting software can build on the secure facilities afforded by Intel TXT to provide additional security features and functions. It provides examples how the datacenter can create and use trusted pools. 7. Oracle WebLogic Server 12c Advanced Administration Cookbook Oracle WebLogic Server 12c Advanced Administration Cookbook guides you through 70 recipes covering from the basics of WebLogic 12c installation, and passing through JDBC, JMS, cluster configuration and tuning. The book covers the day-by-day tasks of a WebLogic Administrator, enhanced with a lot of tips to build a WebLogic production environment focused on stability, high availability and performance. The best place to start with any book is at the beginning so the first thing that is covered is the basics. This quick refresher should get you back up to speed with WebLogic server and get you in the right frame of mind to get stuck into the more complex techniques. 8. Microsoft Exchange Server 2013 PowerShell Cookbook, 2nd Edition Microsoft Exchange Server 2013 is a complex messaging system. Windows PowerShell 3 can be used in conjunction with Exchange Server 2013 to automate and manage routine and complex tasks to save time, money, and eliminate errors. Microsoft Exchange Server 2013 PowerShell Cookbook: Second Edition offers more than 120 recipes and solutions to everyday problems and tasks encountered in the management and administration of Exchange Server. If you want to write scripts that help you create mailboxes, monitor server resources, and generate detailed reports, then this Cookbook is for you. This practical guide to Powershell and Exchange Server 2013 will help you automate and manage time-consuming and reoccurring tasks quickly and efficiently. Starting by going through key PowerShell concepts and the Exchange Management Shell, this book will get you automating tasks that used to take hours in no time. 9. Implementing Citrix XenServer Quickstarter Virtualization is the present and the future of the technological world and to keep up with the latest trends is critical for all of us. With cloud technology gaining popularity day by day it is important to get familiar with the basics and move quickly to a practical implementation. Citrix is one of the leading virtualization and cloud technology vendors and the number one choice of experts around the globe. Implementing Citrix XenServer Quick Starter is a practical, hands-on guide which will walk you through a series of steps from the initial installation of Citrix XenServer to more advanced topics and enables you to readily build your own virtual environments. 10. Getting Started with Oracle Tuxedo The client server or Tuxedo has existed for the past few decades and it is expanding every day! Today, Service Oriented Architecture (SOA) or Service Component Architecture (SCA) are considered to be the new approaches to build client server architecture, Tuxedo adopts this concept and can be extended very easily. Getting Started with Oracle Tuxedo shows how to develop distributed systems using Tuxedo and extend that to SOA or even a Cloud environment. 11. PostgreSQL Server Programming Learn how to work with PostgreSQL as if you spent the last decade working on it. PostgreSQL is capable of providing you with all of the options that you have in your favourite development language and then extending that right on to the database server. With this knowledge in hand, you will be able to respond to the current demand for advanced PostgreSQL skills in a lucrative and booming market. PostgreSQL Server Programming will show you that PostgreSQL is so much more than a database server. In fact, it could even be seen as an application development framework, with the added bonuses of transaction support, massive data storage, journaling, recovery and a host of other features that the PostgreSQL engine provides. 12. Learning SQL Server Reporting Services 2012 In the present day information-centric world we live in, the success of an enterprise depends enormously on how its information is generated, handled, and disseminated. With ample screenshots and over 65 hands-on exercises, this book will guide you effortlessly through creating cutting edge reports using SQL Server Reporting Services 2012, native and fully integrated with SharePoint Server 2010 including new features like Power View and Data Alerts. Learning SQL Server Reporting Services 2012 will get you started right from installation and then move on to configuration of SQL Server Reporting Services 2012. 13. JBoss AS 7 Development JBoss Application Server meets high standards of reliability, efficiency, and robustness, and is used to build powerful and secure Java EE applications. It supports the most important areas of Java Enterprise programming including EJB 3.1, Contexts and Dependency Injection, JAX-WS and JAX-RS web services, the security framework, and more. Getting started with JBoss application server development can be challenging; however, with the right approach and guidance, you can easily master it and this book promises that. 14. Windows Server 2012 Automation with PowerShell Cookbook Automating server tasks allows administrators to repeatedly perform the same, or similar, tasks over and over again. With PowerShell scripts, you can automate server tasks and reduce manual input, allowing you to focus on more important tasks. Windows Server 2012 Automation with PowerShell Cookbook will show several ways for a Windows administrator to automate and streamline his/her job. Learn how to automate server tasks to ease your day-to-day operations, generate performance and configuration reports, and troubleshoot and resolve critical problems. 15. CentOS 6 Linux Server Cookbook CentOS is a community-based enterprise class operating system and this book will provide a series of practical solutions that will not only show you how to install and maintain CentOS as a server, but to explore this well-known Linux distribution with the intention of tackling many common issues by providing some tricks of the trade in order to simplify the task of building a server. CentOS 6 Linux Server Cookbook is a practical guide to installation, configuration, administration, and maintenance. This is a one-stop-shop to all things CentOS, so regardless as to whether you need a mail server, web server, database server, domain server or a file sharing platform, this book provides a comprehensive series of starting points that will give you direct access to the inner workings of this open source, community-based enterprise server. 16. Developing Business Intelligence Apps for SharePoint Create dynamic business intelligence (BI) solutions for SharePoint faster and with more capabilities than previously possible. With this book, you'll learn the entire process - from high-level concepts to development and deployment - for building data-rich BI applications with Visual Studio LightSwitch, SQL Server 2012, and a host of related Microsoft technologies. You'll learn practical techniques and patterns necessary to use all of these technologies together as you build an example application through the course of the book, step by step. Discover how to solve real problems, using BI solutions that will evolve to meet future needs. 17. Exam Ref 70-331: Core Solutions of Microsoft SharePoint Server 2013 Prepare for Exam 70-331 - and help demonstrate your real-world mastery of Microsoft SharePoint Server 2013 core solutions. Designed for experienced IT professionals ready to advance their status, Exam Ref focuses on the critical-thinking and decision-making acumen needed for success at the MCSE level. 18. 70-411 Administering Windows Server 2012 This 70-411 Administering Windows Server 2012 textbook covers the second of three exams required for Microsoft Certified Solutions Associate (MCSA): Windows Server 2012 certification. This course will help validate the skills and knowledge necessary to administer a Windows Server 2012 Infrastructure in an enterprise environment. The three MCSA exams collectively validate the skills and knowledge necessary for implementing, managing, maintaining, and provisioning services and infrastructure in a Windows Server 2012 environment. This Microsoft Official Academic Course is mapped to the 70-411 Administering Windows Server 2012 exam objectives. This textbook focuses on real skills for real jobs and prepares students to prove mastery of core services such as user and group management, network access, and data security.

Introducing Routing and Switching in the Enterprise (Version 4.0) DRSEnt Practice Final

CCNA Discovery: Introducing Routing and Switching in the Enterprise (Version 4.0)

DRSEnt Practice Final 

1. Refer to the exhibit. If router RTA fails, which statement is true?       

Hosts A and B can reach each other, but cannot reach hosts C and D or the server.

2. Refer to the exhibit. A network administrator must manually summarize all IP addresses on the POP router for the ISP. Which one is the correct summary address?

          192.168.0.0/22

3. Which three IP addresses are valid host addresses in the 10.200.0.0/20 network? (Choose three.)

          10.200.11.69

          10.200.0.255

          10.200.15.240

4. What are two characteristics of an extended ACL? (Choose two.)

          IP is used to specify all TCP/IP protocols including TCP, UDP, ICMP and routing protocols.

          Traffic can be filtered on source and destination address, protocol, and specific port number.

5. Which two criteria are used by STP to select a root bridge? (Choose two.)

          bridge priority

          base MAC address

6. If a modem is being used to connect to an ISP, which WAN connection type is being used?

          circuit switched

7. Assuming VLSM is not being used, what impact will adding the command ip route 172.16.64.0 255.255.240.0 serial0/0 have on a router that is already operational in a network?

         All packets with a destination address between 172.16.64.1 and 172.16.79.254 will be forwarded out serial0/0.

8. What is the term for the value 2172416 that is highlighted in the output of the show ip eigrp topology command?
   
   
   

          reported distance of the feasible successor

9. While using the Class A addressing scheme, a network administrator decides to use the 255.255.254.0 subnet mask in the network configuration. How many host addresses can be created for each subnetwork in this addressing scheme?

           510

10. What are two features of a standard IP ACL? (Choose two.)

It permits or denies access based on the entire protocol.

It filters the packet based on the source IP address only.

11. Refer to the exhibit. A router has learned the six routes that are shown in the exhibit. Which two routes will be installed in the routing table? (Choose two.)
    
    
    
    2

6

12. Refer to the exhibit. The network administrator enters the command that is shown in the exhibit and then issues the show ip route command. The route added by the network administrator is missing from the routing table. What is the reason for this?
    
    
    

This static route is providing a backup to the existing route to 192.168.1.0 /24.

13. Refer to the exhibit. How many routers have established OSPF adjacencies with R1?
    
    
    

         2

14. Refer to the exhibit. R1 and R2 are connected to each other through their serial0/0/0 interfaces, but are unable to establish OSPF adjacency. What are two reasons for this? (Choose two.)
    
    
    

The Hello and Dead timers of the routers do not match.

The serial interfaces of the two routers are in different subnets.

15. Refer to the exhibit. The network administrator has configured R1, R2, and R3 to use RIPv2, and the network is fully converged. The hosts on the internal network are able to access R2, but they are unable to access the Internet. 
    
    
    

Configure a default route on R2 and propagate it via RIPv2 to routers R1 and R3.

16. Once the root bridge has been determined, which two items are assigned to every other switch before STP converges a switched network? (Choose two.)

root port

designated port

17. An organization is planning to expand by adding five new branches. After the expansion, it will require secured, full-time, and simultaneous connectivity for its new branch offices with the central office. There is only one port available on the central office router. Which WAN technology can be used in this situation?

Frame Relay

18. Where are EIGRP successor routes stored?

in the routing table and the topology table

19. Refer to the exhibit. None of the hosts in network A are able to access the Internet. How can this problem be resolved?
    
    
    

Configure the access list for the correct network.

20. Which command should a network administrator issue to disable default summarization in an EIGRP network?

Router(config-router)# no auto-summary

21. Refer to the exhibit. What is the purpose of assigning the IP address 192.168.30.1 to an access layer switch?
    
    
    

to allow remote management of the switch

23. Refer to the exhibit. Both routers are configured to use the EIGRP routing protocol. The network administrator wants to enable manual summarization by issuing the displayed command. 
    
    
    
    
    in interface mode on the S0/0/0 interface of R2
24. Refer to the exhibit. What are two possible procedures that would ensure that R1 would always be the DR for OSPF area 0? (Choose two.)
    
    
    

Set the router ID of R1 to the highest IP address in the network.

Set the OSPF priority to 255 on the R1 FastEthernet0/0 interface

25. What is the difference between the passive and active route status as displayed in an EIGRP topology table?

Routes that are active are being recalculated by DUAL.

26. Refer to the exhibit. Which two facts can be determined from the output? (Choose two.)
    

    

    
    

The router ID of R2 is 192.168.100.65.

R2 has established adjacencies with three routers.

27. Refer to the exhibit. Both switches have been configured with static VLANs. Host A and host C belong to one VLAN and host B and D belong to another VLAN. However, the hosts within the same VLAN are unable to communicate with each other.
    
    Which troubleshooting approach should be followed to resolve this problem?
    

    

    
    

Ensure that the ports connecting the two switches are configured as trunk ports.

28. Refer to the exhibit. The network administrator has just configured a default route on the HQ router. What two statements describe what must happen so that all routers in the OSPF network have a route to the Internet? (Choose two.)
    

    

    
    

The gateway of last resort must be set on each OSPF router.

HQ must be configured with the default-information originate command.

29. Refer to the exhibit. What can be determined from the output of the show ip nat translation command?
    

    

    
    

NAT overload is enabled on router R1.

30. Refer to the exhibit. The RIPv2 routing protocol has been enabled with default options on all routers in the network. A user at IP address 192.168.3.20 attempts to connect to a server at IP address 192.168.3.88 but is unsuccessful. What could be done to correct this situation?
    

    

    
    

Turn off automatic summarization on all routers in the network.

31. Refer to the exhibit. Workstation H1 is unable to reach the Internet. A network technician issues a ping command to troubleshoot the problem. Based on the results of the commands that are shown, what could be the cause of the problem?
    

    

    
    

The default gateway on H1 is incorrect.

32. Refer to the exhibit. Host H2 and host H3 are able to ping the default gateway but cannot ping host H1. Host H1 cannot ping either the default gateway, host H2, or host H3. The network technician issues the show interfaces command on switch S1 and notes that all unused switch ports are administratively down and ports Fa0/1, Fa0/3, and Fa0/4 are up with their line protocol up. However, S1 port Fa0/2 is shown as down with the line protocol down error (disabled). What is a possible cause for the inability of H1 to communicate with the network?
    

    

    
    

Port security on switch S1 port Fa0/2 is misconfigured.

33. Which software is typically used on a remote PC to access the enterprise through the Internet via a secure tunnel?

VPN client

34. Refer to the exhibit. Which two statements are correct about the VTP configuration on S2? (Choose two.)
    

    

    
    

The default mode is used.

S2 would not update a new client mode switch whose VTP revision number is 3.

35. Refer to the exhibit. How will the access control list impact the operation of the network?
    

    

    
    

Users on the 192.168.32.0/27 network will be able to telnet into RTA.

36. Refer to the exhibit. What are two consequences of issuing the displayed commands? (Choose two.)
    

    

    
    

The routing update information is protected against being falsified.

The key is encrypted with the MD5 hashing algorithm.

37. An administrator wants to configure a new Cisco Catalyst 2960 switch in order to manage the switch remotely. After configuring the vty lines to allow login, which set of commands should the administrator enter?

Switch(config)# interface vlan 1
Switch(config-if)# ip address 192.168.1.5 255.255.255.0
Switch(config-if)# no shutdown
Switch(config-if)# exit
Switch(config)# ip default-gateway 192.168.1.1

38. Refer to the exhibit. EIGRP has been configured on all routers in the network. Based on the provided output, which route or routes will be installed in the R1 routing table for the 172.30.1.0/24 network?
    

    

    
    

            EIGRP will install the route via the 10.1.45.0/24 network.

 

Hierarchical Design Model – Core – distribution – access layer

A hierarchical network design includes the following three layers:

• The backbone (core) layer that provides optimal transport between sites
• The distribution layer that provides policy-based connectivity
• The local-access layer that provides workgroup/user access to the network

Function of the Core Layer

The core layer is a high-speed switching backbone and should be designed to switch packets as fast as possible. This layer of the network should not perform any packet manipulation, such as access lists and filtering, that would slow down the switching of packets.

Function of the Distribution Layer

The distribution layer of the network is the demarcation point between the access and core layers and helps to define and differentiate the core. The purpose of this layer is to provide boundary definition and is the place at which packet manipulation can take place. In the campus environment, the distribution layer can include several functions, such as the following:

• Address or area aggregation
• Departmental or workgroup access
• Broadcast/multicast domain definition
• Virtual LAN (VLAN) routing
• Any media transitions that need to occur
• Security

In the non-campus environment, the distribution layer can be a redistribution point between routing domains or the demarcation between static and dynamic routing protocols. It can also be the point at which remote sites access the corporate network. The distribution layer can be summarized as the layer that provides policy-based connectivity.

Function of the Access Layer

The access layer is the point at which local end users are allowed into the network. This layer may also use access lists or filters to further optimize the needs of a particular set of users. In the campus environment, access-layer functions can include the following:

• Shared bandwidth
• Switched bandwidth
• MAC layer filtering
• Microsegmentation

In the non-campus environment, the access layer can give remote sites access to the corporate network via some wide-area technology, such as Frame Relay, ISDN, or leased lines.
It is sometimes mistakenly thought that the three layers (core, distribution, and access) must exist in clear and distinct physical entities, but this does not have to be the case. The layers are defined to aid successful network design and to represent functionality that must exist in a network. The instantiation of each layer can be in distinct routers or switches, can be represented by a physical media, can be combined in a single device, or can be omitted altogether. The way the layers are implemented depends on the needs of the network being designed. Note, however, that for a network to function optimally, hierarchy must be maintained.