Concept Installer Manual

[Erminia Scharnberg]

Id like to see the full How-To on how to use manual partitioning during Ubuntu installation. The existing guides (at least those I found here) cover only automatic part and leave untouched the manual part (or extremely short and contain no pictures).

As LiveWireBT noticed in comments, it is recommended to place root partition onto primary partition on MBR scheme disks. However, it belongs to personal taste. Sometimes it's even better to put /boot directory on primary and leave root on logical partition.

Optionally disable fast startup and probably disable hibernation, if it is activated and you intend to access the Windows partition with Ubuntu. Run powercfg.cpl and navigate to Power Options > System Settings through "Choose what the power button does".

Attention! No, you don't want to erase the entire disk and Windows along with it. Choose the Something else option if you see this screen. (Something else may be the most difficult option to understand, but considering existing bugs you know what you will get.)

I will not cover how to create mdadm arrays here. There are a lot of articles around the Internet. However, there is one major problem: Ubiquity installer doesn't account for the arrays created in the live session, so you'll probably get unbootable system after installation on such array.

Important: Install /boot onto one of partition outside the array because GRUB doesn't support mdadm. In my case, it's /dev/sda3. If you want more quick booting of your system, it should be placed at the beginning of the disk.

Now suppose that we are going to install Ubuntu 11.04 and at first of the installation process we will meet Allocate drive space screen (the most important step in the installation process). In Allocate drive space screen Select Something else to partition your disk drive manually.

These instructions assume you have a Linux virtual machine that you will communicate with from your local workstation. Rancher will be installed on the Linux machine. You will need to retrieve the IP address of that machine so that you can access Rancher from your local workstation. Rancher is designed to manage Kubernetes clusters remotely, so any Kubernetes cluster that Rancher manages in the future will also need to be able to reach this IP address.

We don't recommend installing Rancher locally because it creates a networking problem. Installing Rancher on localhost does not allow Rancher to communicate with downstream Kubernetes clusters, so on localhost you wouldn't be able to test Rancher's cluster provisioning or cluster management functionality.

Your Linux machine can be anywhere. It could be an Amazon EC2 instance, a Digital Ocean droplet, or an Azure virtual machine, to name a few examples. Other Rancher docs often use 'node' as a generic term for all of these. One possible way to deploy a Linux machine is by setting up an Amazon EC2 instance as shown in this tutorial.

In the kubeconfig file, you will need to change the value of the server field to :6443. The Kubernetes API server will be reached at port 6443, while the Rancher server will be reached at ports 80 and 443. This edit is needed so that when you run Helm or kubectl commands from your local workstation, you will be able to communicate with the Kubernetes cluster that Rancher will be installed on.

The final command to install Rancher is below. The command requires a domain name that forwards traffic to the Linux machine. For the sake of simplicity in this tutorial, you can use a fake domain name to create your proof-of-concept. An example of a fake domain name would be .sslip.io.

For Kubernetes v1.25 or later, set global.cattle.psp.enabled to false when using Rancher v2.7.2-v2.7.4. This is not necessary for Rancher v2.7.5 and above, but you can still manually set the option if you choose.

To make these instructions simple, we used a fake domain name and self-signed certificates to do this installation. Therefore, you will probably need to add a security exception to your web browser to see the Rancher UI. Note that for production installs, you would need a high-availability setup with a load balancer, a real domain name and real certificates.

Permission is granted to copy and distribute modified versions of thismanual under the conditions for verbatim copying, provided that theentire resulting derived work is distributed under the terms of apermission notice identical to this one.

Permission is granted to copy and distribute translations of this manualinto another language, under the above conditions for modified versions,except that this permission notice may be stated in a translationapproved by the R Core Team.

If you want the build to be usable by a group of users, set umaskbefore unpacking so that the files will be readable by the target group(e.g., umask 022 to be usable by all users). Keep thissetting of umask whilst building and installing.

If you use a fairly recent GNU version of tar and dothis as a root account (which on Windows includes accounts withadministrator privileges) you may see many warnings about changingownership. In which case you can use

and perhaps also include the option --no-same-permissions.(These options can also be set in the TAR_OPTIONS environmentvariable: if more than one option is included they should be separatedby spaces.)

The tarballs are available from DownloadR-patched.tar.gz or R-devel.tar.gz (or the .tar.bz2versions) and unpack as described in the previous section. They arebuilt in exactly the same way as distributions of R releases.

The Subversion repository does not contain the current sources for therecommended packages, which can be obtained by rsync ordownloaded from CRAN. To use rsync to install theappropriate sources for the recommended packages, run./tools/rsync-recommended from the top-level directory of theR sources.

In addition, binary distributions are available for some common Linuxdistributions (see the FAQ for current details) and formacOS. These are installed in platform-specific ways, so for the restof this chapter we consider only building from the sources.

First review the essential and useful tools and libraries inEssential and useful other programs under a Unix-alike, and installthose youwant or need. Ensure that either the environment variable TMPDIRis either unset (and /tmp exists and can be written in andscripts can be executed from) or points to the absolute path to a validtemporary directory (one from which execution of scripts is allowed)which does not contain spaces.

Choose a directory to install the R tree (R is not just a binary, buthas additional data sets, help files, font metrics etc). Let us callthis place R_HOME. Untar the source code. This should createdirectories src, doc, and several more under a top-leveldirectory: change to that top-level directory (At this point NorthAmerican readers should consult Setting paper size.) Issue thefollowing commands:

Failures are not necessarily problems as they might be caused by missingfunctionality, but you should look carefully at any reporteddiscrepancies. (Some non-fatal errors are expected in locales that donot support Latin-1, in particular in true C locales andnon-UTF-8 non-Western-European locales.) A failure intests/ok-errors.R may indicate inadequate resource limits(see Running R).

see Testing an Installationfor the possibilities of doing this in parallel. Note that these checksare only run completely if the recommended packages are installed. Ifyou have a local CRAN mirror, these checks can be speeded up by eithersetting environment variable R_CRAN_WEB to its URL, or having afile .R/repositories specifying it (see ?setRepositories).

If the configure and make commands executesuccessfully, a shell-script front-end called R will be createdand copied to R_HOME/bin. You can link or copy this scriptto a place where users can invoke it, for example to/usr/local/bin/R. You could also copy the man page R.1 toa place where your man reader finds it, such as/usr/local/man/man1. If you want to install the complete Rtree to, e.g., /usr/local/lib/R, see Installation. Note:you do not need to install R: you can run it from where it wasbuilt.

and so on, as described further below. This has the advantage of alwayskeeping your source tree clean and is particularly recommended when youwork with a version of R from Subversion. (You may needGNU make to allow this, and you will need no spacesin the path to the build directory. It is unlikely to work if thesource directory has previously been used for a build.)

There are many settings which can be customized when building R andmost are described in the file config.site in the top-levelsource directory. This can be edited, but for an installation usingBUILDDIR it is better to put the changed settings in anewly-created file config.site in the build directory.

Note: if you already have R installed, check that where you installedR replaces or comes earlier in your path than the previousinstallation. Some systems are set up to have /usr/bin (thestandard place for a system installation) ahead of /usr/local/bin(the default place for installation of R) in their default path, andsome do not have /usr/local/bin on the default path.

If you need to disable the server and want HTML help, there is theoption to build HTML pages when packages are installed(including those installed with R). This is enabled by theconfigure option --enable-prebuilt-html. WhetherR CMD INSTALL (and hence install.packages) pre-buildsHTML pages is determined by looking at the R installation and isreported by R CMD INSTALL --help: it can be overridden byspecifying one of the INSTALL options --html or--no-html.

The server is disabled by setting the environment variableR_DISABLE_HTTPD to a non-empty value, either before R isstarted or within the R session before HTML help (includinghelp.start) is used. It is also possible that system securitymeasures will prevent the server from being started, for example if theloopback interface has been disabled. See?tools::startDynamicHelp for more details.

3a8082e126