centos tested
This commit is contained in:
parent
8b351731bd
commit
fa5a962552
33
docs/FAQ
Normal file
33
docs/FAQ
Normal file
@ -0,0 +1,33 @@
|
|||||||
|
BDisk Frequently Asked(/Unasked) Questions
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
0.) Why does it take so long to build?
|
||||||
|
1.) Why is the generated ISO file so big?
|
||||||
|
2.) How do I find the version/release/etc. number of an ISO?
|
||||||
|
|
||||||
|
|
||||||
|
=========================================================
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
0.) WHY DOES IT TAKE SO LONG TO BUILD?
|
||||||
|
A: This typically occurs when you're building from within a LiveCD/LiveUSB situation, in a VM/container/etc., or on a headless server.
|
||||||
|
If this is the case, you may run into what appears to be "stalling", especially while keys are generating for the chroots.
|
||||||
|
Thankfully, there is an easy fix. You can install the "haveged"(http://www.issihosts.com/haveged/) software and run it. This will
|
||||||
|
show an immediate and non-negligible improvement for the above contexts. If you have extra power to throw at it (or are using a dedicated build box)
|
||||||
|
as well, I recommend enabling I_AM_A_RACECAR in your build.conf. BDisk will then be more aggressive with its resource consumption.
|
||||||
|
|
||||||
|
|
||||||
|
1.) WHY IS THE GENERATED ISO FILE SO BIG?
|
||||||
|
A: You may have enabled a LOT of packages in extra/packages.(32|64|both). Or you're using the default set of packages, which tries to include a LOT
|
||||||
|
of different (and in some cases, redundant) packages for widespread utilization and usage. In addition, keep in mind that BDisk builds a single ISO
|
||||||
|
that can be used on both i686 architectures AND full x86_64 architectures ("AMD64" as you may sometimes see it referenced). Because it doesn't cheat
|
||||||
|
and just use a 64-bit kernel with a 32-bit userland, it needs two different squash images on each ISO- one for 32-bit userland and one for 64-bit
|
||||||
|
userland.
|
||||||
|
|
||||||
|
2.) HOW DO I FIND THE VERSION/RELEASE/ETC. NUMBER OF AN ISO?
|
||||||
|
A: This can be found in a multitude of places. The full-size ISO file (iso/<distname>-<git tag>-<git rev number>-(32|64|any).iso) should have the
|
||||||
|
version right in the file name. If you want more detailed information (or perhaps you renamed the file), you can mount the ISO as loopback in GNU/Linux,
|
||||||
|
*BSD, or Mac OS X and check /path/to/mounted/iso/VERSION_INTO.txt. Lastly, within the runtime itself (especially handy if booting via iPXE), you can
|
||||||
|
check /root/VERSION_INFO.txt within the running live environment.
|
@ -4,8 +4,7 @@ function centos_is_stupid {
|
|||||||
|
|
||||||
if [[ "${HOST_DIST}" == "CentOS" || "${HOST_DIST}" == "RHEL" ]];
|
if [[ "${HOST_DIST}" == "CentOS" || "${HOST_DIST}" == "RHEL" ]];
|
||||||
then
|
then
|
||||||
rpm -qa | egrep -q "^xorriso-[0-9]"
|
if [[ "$(rpm -qa | egrep -q '^xorriso-[0-9]')" != "0" ]];
|
||||||
if [[ "${?}" != "0" ]];
|
|
||||||
then
|
then
|
||||||
# Download/install the proper xorriso
|
# Download/install the proper xorriso
|
||||||
EL_VER="$(rpm -qa coreutils | sed -re 's/^coreutils-[0-9.-]*el([0-9])*.*$/\1/g')"
|
EL_VER="$(rpm -qa coreutils | sed -re 's/^coreutils-[0-9.-]*el([0-9])*.*$/\1/g')"
|
||||||
@ -17,7 +16,9 @@ function centos_is_stupid {
|
|||||||
XORRISO_RPM=$(curl -s http://pkgs.repoforge.org/xorriso/ | egrep "\"xorriso-[0-9.-]*el${EL_VER}.rf.x86_64.rpm\"" | sed -re "s/^.*\"(xorriso[0-9.-]*el${EL_VER}.rf.x86_64.rpm).*$/\1/g")
|
XORRISO_RPM=$(curl -s http://pkgs.repoforge.org/xorriso/ | egrep "\"xorriso-[0-9.-]*el${EL_VER}.rf.x86_64.rpm\"" | sed -re "s/^.*\"(xorriso[0-9.-]*el${EL_VER}.rf.x86_64.rpm).*$/\1/g")
|
||||||
echo "Since you're using either CentOS or RHEL, we need to install xorriso directly from an RPM. Please wait while we do this..."
|
echo "Since you're using either CentOS or RHEL, we need to install xorriso directly from an RPM. Please wait while we do this..."
|
||||||
curl -sLo /tmp/${XORRISO_RPM} http://pkgs.repoforge.org/xorriso/${XORRISO_RPM}
|
curl -sLo /tmp/${XORRISO_RPM} http://pkgs.repoforge.org/xorriso/${XORRISO_RPM}
|
||||||
|
set +e
|
||||||
yum -y install /tmp/${XORRISO_RPM} >> "${LOGFILE}.${FUNCNAME}" 2>&1
|
yum -y install /tmp/${XORRISO_RPM} >> "${LOGFILE}.${FUNCNAME}" 2>&1
|
||||||
|
set -e
|
||||||
echo "Done."
|
echo "Done."
|
||||||
echo
|
echo
|
||||||
fi
|
fi
|
||||||
@ -28,8 +29,7 @@ function centos_is_stupid {
|
|||||||
# UGH. And you know what? Fuck SUSE too.
|
# UGH. And you know what? Fuck SUSE too.
|
||||||
if [[ "${HOST_DIST}" == "openSUSE" || "${HOST_DIST}" == "SUSE" ]];
|
if [[ "${HOST_DIST}" == "openSUSE" || "${HOST_DIST}" == "SUSE" ]];
|
||||||
then
|
then
|
||||||
rpm -qa | egrep -q "^xorriso-[0-9]"
|
if [[ "$(rpm -qa | egrep -q '^xorriso-[0-9]')" != "0" ]];
|
||||||
if [[ "${?}" != "0" ]];
|
|
||||||
then
|
then
|
||||||
# Download/install the proper xorriso
|
# Download/install the proper xorriso
|
||||||
source /etc/os-release
|
source /etc/os-release
|
||||||
@ -64,6 +64,7 @@ function centos_is_stupid {
|
|||||||
echo "Please ensure you are connected to the Internet/have repositories configured correctly."
|
echo "Please ensure you are connected to the Internet/have repositories configured correctly."
|
||||||
exit 1
|
exit 1
|
||||||
fi
|
fi
|
||||||
|
set -e
|
||||||
fi
|
fi
|
||||||
|
|
||||||
zypper search binutils-devel | egrep -q '^[[:space:]]*|[[:space:]]*binutils-devel[[:space:]]*'
|
zypper search binutils-devel | egrep -q '^[[:space:]]*|[[:space:]]*binutils-devel[[:space:]]*'
|
||||||
|
@ -1,6 +1,7 @@
|
|||||||
binutils
|
binutils
|
||||||
binutils-devel
|
binutils-devel
|
||||||
curl
|
curl
|
||||||
|
dosfstools
|
||||||
gcc
|
gcc
|
||||||
git
|
git
|
||||||
libisofs
|
libisofs
|
||||||
|
@ -28,6 +28,7 @@ netctl
|
|||||||
networkmanager
|
networkmanager
|
||||||
openssh
|
openssh
|
||||||
openvpn
|
openvpn
|
||||||
|
prebootloader
|
||||||
pv
|
pv
|
||||||
rsync
|
rsync
|
||||||
sed
|
sed
|
||||||
|
Loading…
Reference in New Issue
Block a user