May 27, 2013 - So while Dennis Wilson contributed almost nothing to the Beach Boys'. Apart from a brief CD release in 1990, Pacific Ocean Blue remained. Jun 18, 2016 - 6/28/17 EDIT: On August 22nd, 1977, Dennis Wilson released his first solo album, entitled Pacific Ocean Blue. The first ever solo Beach Boys. Apr 28, 2011 - Dennis Wilson 'Pacific Ocean Blue' (1977) (News, Views and Music 97). At first Dennis was central to The Beach Boys by encouraging a. Apr 28, 2017 - Released in 1977, Pacific Ocean Blue was the debut album by Beach Boy Dennis Wilson (indeed his only album as the follow up Bambu was. Dennis wilson songs.

1. Get Into Pc - Download Free Your Desired App
2. Pokki - Download Free Desktop Apps And Games

This utility replaces the Desktop Themes component of Microsoft Plus. With this utility you can use the thousands of free desktop themes available on both. TechSpot Downloads is updated every day with dozens of apps, from productivity to security and gaming. Free Software Downloads Fast downloads for power users: No bundles, no malware, focus on quality. Software essentials for Windows, macOS and Android. TechSpot Downloads is updated every day with dozens of apps covering everything from. No more that old boring GRUB menu ####INSTALLATION Move the extracted file to /boot/grub/themes. Your Choice Download as. GFX Boot GRUB Themes.

GRUB2 (the GRand Unified Bootloader version 2) is a replacement for the original GRUB boot loader, which is now referred to as 'GRUB Legacy'. GRUB2 has an entirely separate code base from GRUB Legacy, and features a new shell-like syntax for advanced scripting capabilities.

For a shotgun approach, see GRUB2 Quick Start.

If migrating from GRUB Legacy to GRUB2, see GRUB2 Migration.

• 1Installation
• 2Configuration
• 3Installing the boot loader
  • 3.1BIOS with MBR
  • 3.2BIOS with GPT
  • 3.3UEFI with GPT
• 4Extended features
• 5Troubleshooting

Installation

The sys-boot/grub package is slotted. Both grub-0.97 (GRUB Legacy) and grub-2.02 may be installed at the same time; however, only one version at a time may be installed in the Master Boot Record (MBR) of a hard drive.

Prerequisites

To control which platforms GRUB2 will install for, set the GRUB_PLATFORMS variable in make.conf. The amd64 architecture includes a profile default which works for most systems.

The following platforms are supported depending on the target CPU:

The amd64 profiles enable support for (U)EFI functionality by default. When using a BIOS-based system, set GRUB_PLATFORMS variable to pc to avoid unneeded dependencies.

USE flags

Emerge

To install GRUB2 use the normal emerge syntax:

Additional software

Optionally, install the os-prober utility (provided through the sys-boot/os-prober package) to have GRUB2 probe for other operating systems when running the grub-mkconfig command. In most instances, this will enable GRUB2 to automatically detect other operating systems including Windows 7, 8.1, 10, other distributions of Linux, etc.

The GRUB2 (and optionally sys-boot/os-prober) installations do not automatically enable the boot loader. These only install the software on the operating system, but to install the boot loader to the system itself (so that it is used when booting the system), additional steps need to be taken, which are covered in the Configuration section.

Configuration

There are two important aspects to the configuration of GRUB2:

1. Installation of GRUB2 software as the boot loader of the system.
2. Configuration of the GRUB2 boot loader.

The installation of GRUB2 software is specific to the type of system, and is covered in Installing the boot loader. First we cover the configuration of the boot loader itself.

Main configuration file

The grub-mkconfig script is used to generate a grub configuration. It uses the scripts under /etc/grub.d/* together with the /etc/default/grub configuration file to generate the final /boot/grub/grub.cfg - the only configuration file used by GRUB2 itself.

GRUB2 does not require the administrator to manually maintain a boot option configuration (as is the case with boot loaders such as GRUB Legacy and LILO). Instead it can generate its configuration file (/boot/grub/grub.cfg) using the grub-mkconfig command. This utility will use the scripts in /etc/grub.d/ and the settings in /etc/default/grub.

After modifying one or more settings, run the grub-mkconfig utility with the -o option pointing to the output file located at /boot/grub/grub.cfg (this is GRUB2's default output location):

Each time the grub-mkconfig utility is called a new configuration will be generated.

Setting configuration parameters

The following variables in /etc/default/grub are the most common ones to set to control how GRUB2 will function:

For a more complete list, please refer to the configuration variables sub-page and as the info page of grub-mkconfig.

After modifying the parameters, regenerate the GRUB2 configuration file with grub-mkconfig.

Enabling or disabling configuration scripts

The directory /etc/grub.d/ contains the scripts that grub-mkconfig uses to generate a grub.cfg file. By default the contents of this directory should be similar to the following:

GRUB2 will use all installed scripts that are marked as executable (which by default, they all are). To disable any of the scripts simply remove the executable bit from the script's file permissions using the chmod command. In the following example every script but 00_header and 10_linux are disabled:

After modifying the scripts (or removing the executable bit), regenerate the GRUB2 configuration file using grub-mkconfig.

Get Into Pc - Download Free Your Desired App

Manipulating configuration scripts

Some features or GRUB2 functionalities are only possible to be exploited by modifying the configuration scripts. For instance, to support dual-booting with FreeBSD, the following manipulation needs to be done.

Change the /etc/grub.d/40_custom script to:

/dev/sda1 or (hd0,1) is the partition in which FreeBSD resides. If the normal UFS install was used for the FreeBSD partition then /dev/sda1 is a container (something like a logical partition). It consists of the swap and root partition. Verify the 40_custom script is executable by running ls -la /etc/grub.d/40_custom. If the executable bit is not set then set it using the chmod u+x 40_custom command.

Next install GRUB2 using the grub-install command and update GRUB2's configuration file:

Installing the boot loader

Installing GRUB2 as the system's boot loader depends on how the system is meant to boot (through BIOS or UEFI) and how the disk on which the boot loader should be installed is partitioned (using MBR or GPT partition layout).

This article covers the following situations:

Select the installation instructions appropriate for the system.

BIOS with MBR

Pokki - Download Free Desktop Apps And Games

Make sure that the /boot location is available - if this uses a separate partition, make sure that it is mounted:

Run the grub-install command to copy the relevant files to /boot/grub. On the PC platform, this also installs a boot image to the Master Boot Record (MBR) or a partition's boot sector. If all goes well, after running grub-install an output such as the one below is to be expected:

grub-install accepts a --target option to set the CPU architecture and system platform. If unspecified, grub-install will attempt to guess the proper values; on an amd64/x86 system it will use i386-pc by default. grub-install also accepts a --boot-directory option to tell the GRUB2 installer which directory to look for GRUB2's boot files. This defaults to the current /boot but is useful when trying to move a root partition.

Partitioning for BIOS with MBR

Be sure to leave enough free space before the first partition. Starting the first partition at sector 2048 leaves at least 1 MiB of disk space for the master boot record. It is recommended (but not mandatory) to create an additional partition for GRUB called the BIOS boot partition. This partition just needs to be defined, but not formatted. It is only needed if the system is later migrated to the GPT partition layout. When sticking with MBR, this is not needed.

If the Gentoo installation instructions were followed, this BIOS boot partition will already be available.

BIOS with GPT

If a /boot partition is needed, start by mounting the /boot partition:

If all goes well, after running the grub-install command an output such as the one below is to be expected:

grub-install accepts a --target option to set the CPU architecture and system platform. If unspecified, grub-install will attempt to guess the correct values; on an amd64/x86 system it will use i386-pc by default. grub-install also accepts a --boot-directory option to tell the GRUB2 installer which directory to look in for GRUB2's boot files. This defaults to the current /boot but is useful when trying to move a root partition.

Partitioning for BIOS with GPT

When a GPT partition table is present on the system, a small BIOS boot partition with type EF02 (which is different from the EFI System Partition (ESP) which has type EF00) will need to be available. 1 MiB will be enough to work, but 2-4 MiB is a safer option. This BIOS boot partition will hold the stage 2 of the bootloader. BIOS boot partitions do not need to be formatted with a filesystem; the grub-install command will overwrite any existing filesystem with one of its own.

To set a partition as a BIOS partition use the command-line tool parted (sys-block/parted) by typing (change 1 to the number of the partition to mark as a BIOS boot partition!):

With sys-apps/gptfdisk's cgdisk utility, this is accomplished by setting the partition type to 0xEF02 and giving it a label of gptbios.

An EFI System Partition is not required, but it would be sensible to make sure that the BIOS boot partition is large enough to be converted to one, should the system motherboard later be upgraded to an UEFI board.

The following is the output of pressing the p key using the gdisk utility on a GPT-partitioned disk with both a BIOS boot [0xEF02] partition and an EFI [0xEF00] partition:

Using the same setup, the parted utility gives output with slightly different syntax:

Creating partitions in gdisk is straightforward for users familiar with the fdisk partitioning utility. After starting gdisk, type n (for new) in the main menu, provide beginning and end sectors (if needed), and set the partition type to EF00 for an EFI system partition.

Users who have followed the Gentoo installation instructions will already have the proper partitioning layout set up.

UEFI with GPT

Make sure that the /boot location is available - if this uses a separate partition, make sure that it is mounted:

Run the grub-install command to copy the relevant files to /boot/grub. This should install GRUB2 in /boot/grub, copy the core image to /boot/efi/EFI/gentoo/grubx64.efi, and call efibootmgr to add a boot entry.

The above command assumes the vfat EFI System Partition (ESP) is mounted at /boot/efi. If the ESP is mounted directly at /boot, use --efi-directory=/boot.

grub-install also accepts a --target option to set the CPU architecture and system platform. If unspecified, grub-install will attempt to guess the proper values; on an AMD64 UEFI-booted system it will use x86_64-efi by default. grub-install also accepts a --boot-directory option to tell the GRUB2 installer which directory to look for GRUB2's boot files. This defaults to /boot but is useful when trying to move a root partition.

Partitioning for UEFI with GPT

For UEFI GPT boot using GRUB2, the system must have a dedicated EFI partition containing a FAT filesystem.

The EFI partition can replace having a /boot partition on /dev/sda1 by having a /boot/efi partition on /dev/sda1. This is to say a successful UEFI boot scenario using GRUB2 can operate with two partitions total (three total if a swap partition is needed): a root partition and an EFI partition. Using this configuration, the /bootfolder will be located in the root /partition (at /boot) and the EFI partition will mount in the boot folder (at /boot/efi). For further clarification, see the example /etc/fstab file below.

Generating a 100MB partition for /boot/efi should provide plenty of space for holding multiple

• .efi files (multiple entries will most likely not be needed; most systems will only use one).

Create the partition using the partitioning tool of choice. The gdisk (sys-apps/gptfdisk) and parted (sys-block/parted) tools fit nicely for this purpose. When using the gdisk utility, be sure to use type EF00.

Proceed to create a FAT filesystem on the EFI system partition using mkfs.fat and add it to /etc/fstab by following the example below: