This installs zsh and sets it as default for root and the arch user.
grml-zsh-config is installed as a userfriendly default configuration.
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
* add the network daemon to rc.conf
* configure dhcpd to background immediatly so we don't timeout if network is not up yet
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
* We use a rc.conf file loser to the upstream default.
* Use the recommend config files to setup hostname, locale, timezone and console
EDIT (Gerardo): Add empty FONT= and use ln -f for localtime
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
Download and add the current installation guide as plain text.
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
This was made originally using directly pacman-key file,
convert it in a patch form, to be more easy to track it.
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
Simplify build process, using the same method like in shutdown hook by mkinitcpio
we still need a custom shutdown script for archiso,
since "twisted" structure of block devices.
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
Although everything should be fine now (due to the /lib -> /usr/lib symlink),
adjust everything to the proper path.
Edited (Gerardo): Also rename function name and image name to be consisten.
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
Adding branding here is not worth the effort. We should keep the archiso environment as vanilla as possible.
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
The old autologin method doesn't work anymore with recent login from util-linux.
Utilize agetty -a instead.
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
This will allow users to install packages within the live environment.
We use the haveged daemon to increase entropy from CPU timings.
See http://www.issihosts.com/haveged/ for details.
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
This ensures we do not pick up any testing or third party repos from the host.
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
* Download and add package signatures to the repository database
* Support any number of configured package caches
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
UTC is a more reasonable default than Canada/Pacific
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
Makes an efiboot.img (FAT16) for "El Torito" (additional).
Under an EFI-system, implies that this .ISO works only if is used
as "CD-ROM/DVD-ROM" not in ISO-HYBRID-MBR mode.
If you want, an EFI-ready USB-key, just unpack this "<ISO>/EFI/efiboot.img" (FAT16) to
"<USB-key-FAT-formatted>/EFI" then copy "<ISO>/arch" and setup the filesystem label.
An aditional EFI shell is provided with an startup script for automatic booting
until EFI_STUB supports "linux.conf" to pass boot parms to kernel.
Anyway I think that is a good idea to keep this shell, so can customize boot parms,
or for doing other tasks on systems without an EFI-shell.
RFCv1: Initial efiboot.img build with vmlinuz.efi (Linux with EFI_STUB enabled)
and archiso.img (initramfs).
RFCv2: Use an startup.nsh with EFI-Shell 2.0 (generated from build.sh) for automatic boot.
RFCv3: Use and older EFI-Shell 1.0 instead of 2.0, since not all UEFI-systems
are compatible with 2.3+ specs.
RFCv4: The script "startup.nsh" improved by Keshav P R, using a for-loop
(see notes below from original commit), now that has more than 1-line,
I moved it to an independent file and is parsed by build.sh.
----
About startup.nsh:
Author: Keshav P R <the.ridikulus.rat@gmail.com>
Date: Thu Apr 5 10:33:20 2012 +0530
[configs/releng] Search in all existing UEFI FS mountpoints for archiso efistub kernel file
There is no guarantee that the efistub kernel will always be in fs0:
(similar to the case inside linux OS where the sda, sdb confusion exists,
hence the need for UUIDs), especially when USB (instead os CD/ISO) is
used for booting.
Hence loop through all possible fs mountpoints (in UEFI) in startup.nsh
and try to launch the first mountpoint that contains the archiso files.
Cd's into the fs%m:\EFI\archiso directory also may remove future issues
with efistub's linux.conf where the efistub might have problems
identifying the directory from which the kernel was launched.
Also add an helpful echo message showing the user the UEFI PATH to the
archiso kernel file being launched by startup.nsh .
Hopefully this should work in both CD and USB. Tested in Tianocore
UDK/EDK2 DuetPkg X64 UEFI 2.3.1 firmware with EdkShellBinPkg's Shell.
----
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
* For installed packages on live-enviroment use mkarchiso pkglist command.
* For packages in [core] repo in core.iso, make a list of them during repo generation.
It uses the same format like done by pkglist command: <repo>/<package>-<version>
(anyway repo is always core in this case).
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
This command makes a list of installed packages on root-image,
on <ISO>/$archisobasedir/pkglist.$arch.txt with the format
<repo>/<package>-<version>
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
