Contents. This guide is intended to introduce you to the very many ways in which Ubuntu may be installed to your machine depending on your specific use case. The official also covers a complete list of alternative installation methods for Ubuntu. Requirements Requirements are basic! Ubuntu has been designed keeping in mind most hardware that abounds, so it is highly likely that if your hardware is not too uncommon, Ubuntu will work on your machine right off the bat! Nonetheless, you should check if your hardware works with Ubuntu and meets the minimum system requirements.
The following pages are a comprehensive review of all Ubuntu supported hardware:.: Most laptops these days ship with an Intel or an AMD processor, which fall into the category x86/x8664. These are officially supported by Ubuntu. This page documents these as well as all other processor architectures supported by Ubuntu.: This page includes a comprehensive list of Ubuntu-certified machines, including most desktops/laptops from some of the biggest vendors.: This page includes the minimal system requirements a machine needs in order to run the graphical version of Ubuntu.
From the point of view of most modern machines, these are extremely basic. Standard installation If you want to install Ubuntu on your personal desktop/laptop either sharing the computer with Windows or as the only operating system, this is probably what you want to do, and it has never been easier! The standard Ubuntu desktop installation uses a, which is meant to help you through the installation process in a very small number of easy steps. To get the installer and to prepare Windows to share the computer with Linux, you will need to do the following:. The LiveCD (really a DVD) is a fully functional Ubuntu environment, and it allows you to get a taste of Ubuntu on your machine by using a session!
If you downloaded a DVD image (.iso file), you can burn it to a standard DVD (see and ). There are three things to do. (1) Back up Windows on a bootable USB drive. There are instructions on the Microsoft web site. This step is a good idea whether or not you install Ubuntu. (2) Disable Fast Startup. Windows 8.1 and presumably future versions have a feature called Fast Startup.
When it is enabled - and it is enabled by default - Windows shuts down in a hybrid state, somewhere between a full shutdown and a 'sleep' state. The dual boot manager which Ubuntu will install (called grub) does not presently (March 2015) know how to start Windows from this hybrid state. You must therefore disable Fast Startup if you ever want to use Windows again after installing Ubuntu. Just how to do that is best left to the documentation of your particular version of Windows. But do not fail to do it, or you will never boot Windows again.
(3) Change the boot order. Chances are that if you simply put the LiveDVD in the optical drive and turn on the computer, it will go straight to Windows and totally ignore the DVD.
That is because the computer came with the hard disk ahead of the DVD in the boot order. The boot order in machines made after about 2012 is set in something called the UEFI (Uniform Extensible Firmware Interface). You must edit the UEFI to change the boot order. Windows has a UEFI editor; how you get to it is different for Windows 8 and 8.1 and will probably be different again for 10. This editor is well hidden in 8.1, but can be reached by a series of steps beginning from PC Settings (the cogwheel) on the start page. From there go to 'Update and Recovery' then 'Recovery' then 'Advanced startup' then 'Restart now' then 'Troubleshoot' then 'Advanced options' and then 'UEFI Firmware settings'. Once you have reached this editor, use the right arrow key to move across to the 'Boot' tab and then follow instructions on the screen to move the optical drive to the top of the boot order.
It is also a good idea to enable booting from USB. On the Security tab it is possible to disable. It should not be necessary to do so, but if you have trouble getting the boot to start, come back and disable. (Do NOT be tempted to enable 'Legacy mode'. If you do, Windows won't work at all and Linux will work poorly.). The hard part is behind us. Turn off the computer.
Put the DVD in the optical drive and start the computer. After considerable whirring of the DVD, the opening screen appears and you have a choice of whether to try Ubuntu or proceed directly to installing it. It is probably a good idea to try it to check that the hardware, and in particular the modem, is supported.
When ready, click the button to install. You will need to answer a number of routine questions and then partition the hard disk. You have a choice of ways to do this, but unless you want to do something fancy and know very well what you are doing, the first option will be just fine.
Pharma guide 2014 free download pdf. Children: Usually 20-50 mg/kg once daily by IM inj., slow IV inj over at least 2-4 min, or IV infusion. Doses over 50 mg/kg to be given by slow IV infusion over at least 30 minutes. Severe infections, up to maximum 80 mg/kg daily.
Choose it and a screen opens with two bars of equal length, the one on the left representing the size of the Windows partition, and the one on the right, the size of the Linux partition. You adjust the allocation by dragging the inner edge of one of the bars. In deciding how to allocate the space, bear in mind that all Windows programs have to reside in the Windows partition and all Linux programs must reside in the Linux partition.
Windows programs cannot access files in the Linux partition, but Linux programs can to some extent access files in the Windows partition. For example, Writer installed in the Linux partition can edit files in the Windows partition. Once the disk is partitioned, the installation is soon finished. Remove the DVD, restart the computer, and you should be offered a choice between starting Windows or starting Ubuntu. Try one, then restart and try the other. Alternate Installation You may not wish to use the standard LiveCD for one of the following reasons:.
Your computer does not meet the hardware requirements, or the required drivers are missing from the standard LiveCD. The LiveCD is designed to support most standard hardware, but this won't cover every possible configuration. Or, you may simply prefer to install a more customized version of Ubuntu different from the standard install depending on your taste. Ubuntu has you covered in this regard, and towards this end you can use an Alternate Installation CD. Refer to the page for download locations. The Alternate CD allows more advanced installation options which are not available with the standard LiveCD. Installation without a CD The new generations of laptops and netbooks are increasingly shipping without CD drives.
To cater to this need, or if you do not wish to burn a CD to install Ubuntu, you are not left to trudge in the dark - Ubuntu can be installed without using a CD or CD-ROM drive!. A quick guide to installing from a USB memory stick.
Intended for less technically-inclined readers. Installing from a USB memory stick (full version). Similar to above but using. Overview: cloning and extraction, tools and a simple 'Do it yourself' extracting method. Installing from a PC which will not boot from a CD. Yes, it is possible to install Ubuntu from within Windows without using floppies, a CD, or any other removable media! This uses Wubi, and installs Ubuntu as a large file that may be uninstalled like any other program in Windows.
Installing without a CD drive over a network. Installing without a CD drive or network capabilities from a hard drive. Installing using a spare partition from an existing Linux system to house the Ubuntu CD image.
Installing using a physical disk to a Virtual Machine. A system for a USB pendrive - a good alternative to a persistent live system. Please refer also to the network installation guides below. Upgrading an installation If you are upgrading from a previous version of Ubuntu to a new version, please refer to the for upgrading instructions. Server and network installations Ubuntu can be installed over a network or the Internet. Booting the installer from a local server, using DHCP, TFTP, and PXE.
Another description of installing over the net, with no CD-ROM drive or a non-bootable SCSI CD-ROM drive. Booting using files saved to an existing partition and downloading the packages from the internet at installation time. Booting from a CD (could be TFTP or similar too) and installing the system over SSH. Installing on a NFS-server and using with diskless clients. Installing on an NFS-server with a local /boot (e.g.
Booting from for a silent media center PC). A quick guide for installing Hardy Ubuntu 12.04 on a dedicated server over ssh. Installing on a dedicated server over ssh (full version). Installing without a CD drive over a network. Installing on external or RAID hard disks Ubuntu can be installed on an external hard disk or RAID array. Booting Linux from a Firewire hard disk. Booting an Ubuntu system on a USB hard disk on computers which cannot boot from USB (using a boot CD).
Booting an Ubuntu system from a SD card on computers which cannot boot from SD. Installing Ubuntu or Kubuntu on a USB pendrive with persistent mode. Installing onto a Software RAID Array, with all partitions on RAID and LVM (including root and boot). Installing onto a BIOS RAID array. If you really want to keep XP and Ubuntu on separate hard drives. Install a Linux software RAID. Installing via a CD image loaded onto a hard drive.
LVM Installation Guides. Minimal installations If you have an older computer or a computer with a small amount of memory, see the guides below for help on installing Ubuntu. Install Ubuntu on older computers with low memory.
Making the desktop interface snappier on machines with low memory. From a minimal CD that downloads packages during install.
Other installation guides. Safely split your hard drive into smaller parts. Boot more than one operating system from a single hard drive. Install Ubuntu on the same hard drive as an existing Windows installation. Installing within Windows. Using Ubuntu with VMware and XEN.
Customize the Ubuntu Alternative Installer/Server installation CD. An explanation of the boot process and boot device issues.
How to install the Xen-optimized Ubuntu images on XenServer. Making a customized installation CD for unattended installations, with a web-served preseed file. Instructions on how to transfer data from common Windows applications to their Ubuntu equivalents. Guidance on switching from Windows to Ubuntu and getting used to the differences. See also.
January 05, 2015 topic: tagged:. In this post I give an overview of my evaluation of three different CPU profiling tools: gperftools, Valgrind and gprof. I evaluated the three tools on usage, functionality, accuracy and runtime overhead. The usage of the different profilers is demonstrated with the small demo program, available via my github repository.
The intent of cpuload.cpp is just to generate some CPU load - it does nothing useful. The bash scripts in the same repo (which are also listed below) show how to compile/link the cpuload.cpp appropriately and execute the resulting executable to get the CPU profiling data. Gprof The GNU profiler uses a hybrid approach of compiler assisted instrumentation and sampling. Instrumentation is used to gather function call information (e.g. To be able to generate call graphs and count the number of function calls). To gather profiling information at runtime, a sampling process is used. This means, that the program counter is probed at regular intervals by interrupting the program with operating system interrupts.
As sampling is a statistical process, the resulting profiling data is not exact but are rather a statistical approximation. Creating a CPU profile of your application with gprof requires the following steps:. compile and link the program with a compatible compiler and profiling enabled (e.g. execute your program to generate the profiling data file (default filename: gmon.out). run gprof to analyze the profiling data Let’s apply this to our demo application.
#!/bin/bash # build the program with profiling support (-gp) g -std =c11 -pg cpuload.cpp -o cpuload # run the program; generates the profiling data file (gmon.out)./cpuload # print the callgraph gprof cpuload The gprof output consists of two parts: the flat profile and the call graph. The flat profile reports the total execution time spent in each function and its percentage of the total running time. Function call counts are also reported. Output is sorted by percentage, with hot spots at the top of the list. Gprof’s call graph is a textual call graph representation which shows the caller and callees of each function. For detailed information on how to interpret the callgraph, take a look at the. You can also generate a graphical representation of the callgraph with - a tool to generate a graphical representation of the gprof callgraph)).
The overhead (mainly caused by instrumentation) can be quite high: estimated to 30-260%. Gprof does not support profiling multi-threaded applications and also cannot profile shared libraries. Even if there exist workarounds to get threading support, the fact that it cannot profile calls into shared libraries, makes it totally unsuitable for today’s real-world projects. Valgrind/callgrind is an instrumentation framework for building dynamic analysis tools. Valgrind is basically a virtual machine with just in time recompilation of x86 machine code to some simpler RISC-like intermediate code: UCode. It does not execute x86 machine code directly but it “simulates” the on the fly generated UCode.
There are various Valgrind based for debugging and profiling purposes. Depending on the chosen tool, the UCode is instrumented appropriately to record the data of interest. For performance profiling, we are interested in the tool callgrind: a profiling tool that records the function call history as a call-graph. For analyzing the collected profiling data, there is is the amazing visualization tool. It represents the collected data in a very nice way what tremendously helps to get an overview about whats going on.
Creating a CPU profile of your application with valgrind/callgrind is really simple and requires the following steps:. compile your program with debugging symbols enabled (to get a meaningful call-graph). execute your program with valgrind -tool=callgrind./yourprogram to generate the profiling data file. analyze your profiling data with e.g. KCachegrind Let’s apply this our demo application (profilevalgrind.sh). #!/bin/bash # build the program (no special flags are needed) g -std =c11 cpuload.cpp -o cpuload # run the program with callgrind; generates a file callgrind.out.12345 that can be viewed with kcachegrind valgrind -tool =callgrind./cpuload # open profile.callgrind with kcachegrind kcachegrind profile.callgrind In contrast to gprof, we don’t need to rebuild our application with any special compile flags. We can execute any executable as it is with valgrind.
Of course the executed program should contain debugging information to get an expressive call graph with human readable symbol names. Below you see a KCachegrind with the profiling data of our cpuload demo: A downside of Valgrind is the enormous slowdown of the profiled application (around a factor of 50x) what makes it impracticable to use for larger/longer running applications. The profiling result itself is not influenced by the measurement.
Gperftools from Google provides a set of tools aimed for analyzing and improving performance of multi-threaded applications. They offer a CPU profiler, a fast thread aware malloc implementation, a memory leak detector and a heap profiler. We focus on their sampling based CPU profiler.
Linux Tools - GProf Support Overview The Linux Tools GProf plugin aims to bring the profiling capabilities of GProf to Eclipse, in a manner that is easy to use for developers of any level of experience. Current Status The plugin can parse and display in eclipse gmon.out files generated by gprof intrumentation.
Plugin architecture was designed to be compatible with cross-devlopment tools (some additional work may be needed in this case). Future Plans. Support 'BSD' gmon files (see ). Enhance online documentation Help and screenshots Help and screenshots are available in the Try it out You can download the plugin from our, or check the project plugins out of Git directly from eclipse.org at git://git.eclipse.org/gitroot/linuxtools/org.eclipse.linuxtools.git.
Give More Feedback
I have a C code in a file test.c.I have to profile it using grof.I have used the following commands to do so. Gcc -p -o result test.c./result gprof result A section of the output looks as follows: `Flat profile: Each sample counts as 0.01 seconds.
No time accumulated% cumulative self self total time seconds seconds calls Ts/call Ts/call name` The problem is no matter what complex or easy program I use each sample count doesn't change from 0.01 seconds.Why is that and no time is being accumulated and displayed under the various coloumns.