https://wiki.archlinux.org/api.php?action=feedcontributions&user=Brazier89&feedformat=atomArchWiki - User contributions [en]2024-03-29T11:31:16ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=List_of_Applications/Games/Emulators&diff=253768List of Applications/Games/Emulators2013-04-11T18:12:41Z<p>Brazier89: /* Consoles */</p>
<hr />
<div><noinclude><br />
[[Category:Gaming]]<br />
[[Category:Emulators]]<br />
[[it:List of Applications/Games/Emulators]]<br />
[[ja:List of Applications/Games/Emulators]]<br />
{{Games navigation}}<br />
</noinclude><br />
=== Emulators ===<br />
An emulator is a program which serves to replicate the functions of another platform or system so as to allow applications and games to be run in environments they were not programmed for. While emulators themselves are not games in a strict sense, they provide users with the ability to play games and therefore have been included in this article.<br />
<br />
{{Note|1=For possibly more up to date selection of emulators, try checking the [https://aur.archlinux.org/packages.php?O=0&K=&do_Search=Go&detail=1&L=0&C=5&SeB=nd&SB=n&SO=a&PP=25 AUR 'emulators' category]}}<br />
<br />
{{Warning|Owning an emulator itself is not illegal, but downloading/sharing copyrighted ROMs and using emulator to run them without the copyright holder's permission is ILLEGAL. Arch Linux etc. is not responsible if you get in trouble.}}<br />
<br />
==== Consoles ====<br />
{{Wikipedia|List of video game console emulators}}<br />
<br />
* {{App|Gens2|An emulator for Sega Genesis, Sega CD and 32X that is written in assembly language and no longer actively developed.<br />
:* activate OpenGL, set video resolution per custom to 1024x600 for streched full-screen or 800x600 for non-streched;<br />
:* use "Normal" renderer, I couldn't find a visible advantage with the other ones<br />
|http://www.gens.me/|{{AUR|gens}}}}<br />
* {{App|Gens-GS|Gens2, rewritten in C++, combining features from various Gens forks.|http://segaretro.org/Gens/GS|{{AUR|gens-gs}}}}<br />
<br />
* {{App|epsxe|An emulator for the PlayStation video game console for x86-based PC hardware.|http://www.epsxe.com/|{{AUR|epsxe}}}}<br />
* {{App|pSX|A not plugin-based PlayStation emulator with fairly high compatibility.|http://psxemulator.gazaxian.com/|{{AUR|psx}}}}<br />
* {{App|PCSXR|A PlayStation emulator; Debian fork of the abandoned original PCSX|http://pcsxr.codeplex.com/|{{Pkg|pcsxr}}}}<br />
<br />
* {{App|PCSX2|A PlayStation 2 emulator. It is still being maintained and developed.|http://www.pcsx2.net/|{{Pkg|pcsx2}}}}<br />
<br />
* {{App|FCEUX|An NTSC and PAL 8 bit Nintendo/Famicom emulator that is an evolution of the original FCE Ultra emulator. It is accurate, compatible and actively maintained.|http://fceux.com/|{{Pkg|fceux}}}}<br />
<br />
* {{App|higan|A multisystem emulator focusing on accuracy, supporting SNES, NES, GB, GBC, GBA.|http://byuu.org/higan/|{{AUR|higan-gtk}} {{AUR|higan-qt}}}}<br />
<br />
* {{App|ZSNES|A highly compatible Super Nintendo emulator.<br />
|http://www.zsnes.com/|{{Pkg|zsnes}}}}<br />
<br />
* {{App|[[Visual Boy Advance]]|A Game Boy emulator with Game Boy Advance, Game Boy Color, and Super Game Boy support.<br />
|http://vba.ngemu.com/|{{Pkg|visualboyadvance}} and {{AUR|vbaexpress}} (graphical frontend)}}<br />
<br />
* {{App|Mupen64Plus|A highly compatible Nintendo 64 emulator with plugin system.<br />
|http://code.google.com/p/mupen64plus/|{{Pkg|mupen64plus}} and {{AUR|m64py}} (graphical frontend)}}<br />
<br />
* {{App|DeSmuME|A Linux Nintendo DS emulator.|http://desmume.org/|{{Pkg|desmume}}}}<br />
* {{App|snes-9x|A portable, freeware Super Nintendo Entertainment System (SNES) emulator.|http://www.snes9x.com/|{{Pkg|snes9x}}}}<br />
* {{App|Dolphin|A very nice GameCube and Wii emulator.|http://dolphin-emu.org/|{{Pkg|dolphin-emu}}}}<br />
* {{App|fakenes|An NES (Nintendo Famicom) emulator.|http://kaede.strangesoft.net/kadence/|{{AUR|fakenes}}}}<br />
* {{App|gngeo|A command-line NeoGeo emulator.|http://gngeo.googlecode.com|{{AUR|gngeo}}}}<br />
* {{App|mednafen|A command line driven multi system emulator|http://mednafen.sourceforge.net/|{{Pkg|mednafen}}}}<br />
<br />
==== Other ====<br />
* {{App|MAME|A Multiple Arcade Machine Emulator.|http://mamedev.org/|{{Pkg|sdlmame}}}}<br />
* {{App|ScummVM|A virtual machine for old school adventures.|http://www.scummvm.org/|{{Pkg|scummvm}}}}<br />
* {{App|DOSBox|An open-source DOS emulator which primarily focuses on running DOS Games.|http://www.dosbox.com/|{{Pkg|dosbox}}}}<br />
* {{App|[[RetroArch]]|A frontend to libretro (emulation library, using modified versions of existing emulators as plugins).|http://github.com/Themaister/RetroArch|{{Aur|retroarch-git}}}}<br />
* {{App|X Neko Project II|PC-9801 emulator|http://www.asahi-net.or.jp/~aw9k-nnk/np2/|{{AUR|xnp2}}}}</div>Brazier89https://wiki.archlinux.org/index.php?title=Internet_sharing&diff=251036Internet sharing2013-03-17T17:52:49Z<p>Brazier89: /* Configuration */</p>
<hr />
<div>[[Category:Networking]]<br />
[[cs:Internet Share]]<br />
[[es:Conexion a Internet compartida]]<br />
[[fr:Partage de connexion]]<br />
[[it:Internet Share]]<br />
[[ru:Internet Share]]<br />
This article explains how to share the internet connection from one machine to other(s).<br />
<br />
==Requirements==<br />
* The machine acting as server should have an additional network device<br />
* That network device should be connected to the machines that are going to receive internet access. They can be one or more machines. To be able to share internet to several machies a [[Wikipedia:Network switch|switch]] is required. If you are sharing to only one machine, a [[Wikipedia:Ethernet crossover cable|crossover cable]] is sufficient<br />
{{Note|If one of the two computers has a gigabit ethernet card, a crossover cable is not necessary and a regular ethernet cable should be enough}}<br />
<br />
==Configuration==<br />
Using [[Udev#Setting static device names]], name the network device connected to the other computer(s) as '''''net0''''' and the network device connected to the internet as '''''internet0'''''.<br />
===Static IP address===<br />
Assign an static IPv4 address to the interface connected to the other machines. The first 3 bytes of this address cannot be exactly the same as those of another interface.<br />
{{bc|<br />
# ip link set up dev net0<br />
# ip addr add 139.96.30.100/24 dev net0 # arbitrary address<br />
}}<br />
To have your static ip assigned at boot, you can use [[netcfg]].<br />
<br />
===Enable packet forwarding===<br />
Enter this command to temporaly enable packet forwarding:<br />
{{bc|<nowiki>sysctl net.ipv4.ip_forward=1</nowiki>}}<br />
Edit {{ic|/etc/sysctl.conf}} and add this line, which will make the previous change persistent after a reboot.<br />
{{bc|<nowiki>net.ipv4.ip_forward=1</nowiki>}}<br />
If you are using ipv6, use these lines:<br />
{{bc|<nowiki><br />
net.ipv6.conf.default.forwarding=1<br />
net.ipv6.conf.all.forwarding=1<br />
</nowiki>}}<br />
===Enable NAT===<br />
[[pacman|Install]] the package {{Pkg|iptables}} from the [[Official Repositories|official repositories]].<br />
Use iptables to enable NAT:{{bc|<nowiki><br />
# iptables -t nat -A POSTROUTING -o internet0 -j MASQUERADE<br />
# iptables-save > /etc/iptables/iptables.rules<br />
# systemctl start iptables<br />
</nowiki>}}{{Note| Of course, this also works with a mobile broadband connection (usually called ppp0 on PC1)}}<br />
You can set {{ic|iptables.service}} to [[Daemon|auto start a boot]].<br />
<br />
Read the [[iptables]] article for more information.<br />
<br />
===Assigning ip addresses to the client pc(s)===<br />
If you are planning to regularly have several machines using the internet shared by this machine, then is a good idea to install a [[Wikipedia:dhcp|dhcp server]].<br />
<br />
You can read the [[dhcpd]] wiki article, to add a dhcp server. Then, install the [[dhcpcd]] client on every client pc.<br />
<br />
If you are not planing to use this setup regularly, you can manually add an ip to each client instead.<br />
====Manually adding an ip====<br />
<br />
Instead of using dhcp, on each client pc, add an ip address and the default route:<br />
{{bc|<nowiki><br />
ip addr add 139.96.30.120/24 dev eth0<br />
ip link set up dev eth0<br />
ip route add default via 139.96.30.100 dev eth0<br />
</nowiki>}}<br />
Add a nameserver:<br />
{{bc|<nowiki><br />
echo "nameserver <nameserver ip>" >> /etc/resolv.conf<br />
</nowiki>}}<br />
<br />
You can figure out the address of the nameserver by looking into the {{ic|/etc/resolv.conf}} of the server, if its Internet connection is already established. If you don't have a nameserver, you can use [https://code.google.com/speed/public-dns/ Google Public DNS] which is relatively fast. Its addresses are '''8.8.8.8''' and '''8.8.4.4'''.<br />
<br />
That's it. The client PC should now have Internet.<br />
<br />
== Troubleshooting ==<br />
<br />
If you are able to connect the two PCs but cannot send data (for example, if the client PC makes a DHCP request to the server PC, the server PC receives the request and offers an IP to the client, but the client does not accept it, timing out instead), check that you don't have other [[Iptables]] rules [https://bbs.archlinux.org/viewtopic.php?pid=1093208 interfering].<br />
<br />
==See also==<br />
*[[Sharing ppp connection with wlan interface]]<br />
*[[Simple stateful firewall]]<br />
*[[Router]]<br />
*[[USB 3G Modem]]</div>Brazier89https://wiki.archlinux.org/index.php?title=Internet_sharing&diff=251034Internet sharing2013-03-17T17:51:00Z<p>Brazier89: /* Requirements */</p>
<hr />
<div>[[Category:Networking]]<br />
[[cs:Internet Share]]<br />
[[es:Conexion a Internet compartida]]<br />
[[fr:Partage de connexion]]<br />
[[it:Internet Share]]<br />
[[ru:Internet Share]]<br />
This article explains how to share the internet connection from one machine to other(s).<br />
<br />
==Requirements==<br />
* The machine acting as server should have an additional network device<br />
* That network device should be connected to the machines that are going to receive internet access. They can be one or more machines. To be able to share internet to several machies a [[Wikipedia:Network switch|switch]] is required. If you are sharing to only one machine, a [[Wikipedia:Ethernet crossover cable|crossover cable]] is sufficient<br />
{{Note|If one of the two computers has a gigabit ethernet card, a crossover cable is not necessary and a regular ethernet cable should be enough}}<br />
<br />
==Configuration==<br />
Using [[Udev#Setting static device names]], name the network device connected the other computer(s) as '''''net0''''' and the network device connected to the internet as '''''internet0'''''.<br />
===Static IP address===<br />
Assign an static IPv4 address to the interface connected to the other machines. The first 3 bytes of this address cannot be exactly the same as those of another interface.<br />
{{bc|<br />
# ip link set up dev net0<br />
# ip addr add 139.96.30.100/24 dev net0 # arbitrary address<br />
}}<br />
To have your static ip assigned at boot, you can use [[netcfg]].<br />
<br />
===Enable packet forwarding===<br />
Enter this command to temporaly enable packet forwarding:<br />
{{bc|<nowiki>sysctl net.ipv4.ip_forward=1</nowiki>}}<br />
Edit {{ic|/etc/sysctl.conf}} and add this line, which will make the previous change persistent after a reboot.<br />
{{bc|<nowiki>net.ipv4.ip_forward=1</nowiki>}}<br />
If you are using ipv6, use these lines:<br />
{{bc|<nowiki><br />
net.ipv6.conf.default.forwarding=1<br />
net.ipv6.conf.all.forwarding=1<br />
</nowiki>}}<br />
===Enable NAT===<br />
[[pacman|Install]] the package {{Pkg|iptables}} from the [[Official Repositories|official repositories]].<br />
Use iptables to enable NAT:{{bc|<nowiki><br />
# iptables -t nat -A POSTROUTING -o internet0 -j MASQUERADE<br />
# iptables-save > /etc/iptables/iptables.rules<br />
# systemctl start iptables<br />
</nowiki>}}{{Note| Of course, this also works with a mobile broadband connection (usually called ppp0 on PC1)}}<br />
You can set {{ic|iptables.service}} to [[Daemon|auto start a boot]].<br />
<br />
Read the [[iptables]] article for more information.<br />
<br />
===Assigning ip addresses to the client pc(s)===<br />
If you are planning to regularly have several machines using the internet shared by this machine, then is a good idea to install a [[Wikipedia:dhcp|dhcp server]].<br />
<br />
You can read the [[dhcpd]] wiki article, to add a dhcp server. Then, install the [[dhcpcd]] client on every client pc.<br />
<br />
If you are not planing to use this setup regularly, you can manually add an ip to each client instead.<br />
====Manually adding an ip====<br />
<br />
Instead of using dhcp, on each client pc, add an ip address and the default route:<br />
{{bc|<nowiki><br />
ip addr add 139.96.30.120/24 dev eth0<br />
ip link set up dev eth0<br />
ip route add default via 139.96.30.100 dev eth0<br />
</nowiki>}}<br />
Add a nameserver:<br />
{{bc|<nowiki><br />
echo "nameserver <nameserver ip>" >> /etc/resolv.conf<br />
</nowiki>}}<br />
<br />
You can figure out the address of the nameserver by looking into the {{ic|/etc/resolv.conf}} of the server, if its Internet connection is already established. If you don't have a nameserver, you can use [https://code.google.com/speed/public-dns/ Google Public DNS] which is relatively fast. Its addresses are '''8.8.8.8''' and '''8.8.4.4'''.<br />
<br />
That's it. The client PC should now have Internet.<br />
<br />
== Troubleshooting ==<br />
<br />
If you are able to connect the two PCs but cannot send data (for example, if the client PC makes a DHCP request to the server PC, the server PC receives the request and offers an IP to the client, but the client does not accept it, timing out instead), check that you don't have other [[Iptables]] rules [https://bbs.archlinux.org/viewtopic.php?pid=1093208 interfering].<br />
<br />
==See also==<br />
*[[Sharing ppp connection with wlan interface]]<br />
*[[Simple stateful firewall]]<br />
*[[Router]]<br />
*[[USB 3G Modem]]</div>Brazier89https://wiki.archlinux.org/index.php?title=Archiso&diff=233046Archiso2012-11-01T16:31:49Z<p>Brazier89: /* Build the ISO */</p>
<hr />
<div>[[Category:Live Arch systems]]<br />
[[el:Archiso]]<br />
[[fr:Archiso]]<br />
[[it:Archiso]]<br />
[[nl:Archiso]]<br />
[[ru:Archiso]]<br />
[[uk:Archiso]]<br />
'''Archiso''' is a small set of bash scripts that is capable of building fully functional Arch Linux based live CD and USB images. It is a very generic tool, so it could potentially be used to generate anything from rescue systems, install disks, to special interest live CD/DVD/USB systems, and who knows what else. Simply put, if it involves Arch on a shiny coaster, it can do it.<br />
The heart and soul of Archiso is mkarchiso. All of its options are documented in its usage output, so its direct usage won't be covered here. Instead, this wiki article will act as a guide for rolling your own live mediums in no time!<br />
<br />
== Setup ==<br />
<br />
Before we begin, we need to grab the archiso scripts which carry out the beef of the work for us.<br />
<br />
# pacman -S archiso<br />
<br />
{{Note|1=Alternatively, the GIT version can be built and installed [https://aur.archlinux.org/packages.php?ID=25996 from the AUR].}}<br />
<br />
Create a directory to work within, this is where all the modifications to the live image will take place: ~/archlive should do fine.<br />
$ mkdir ~/archlive<br />
<br />
The archiso scripts that were installed to the host system earlier now need to be copied over into the newly created directory you will be working within.<br />
Archiso comes with two "profiles": releng, and baseline.<br />
If you wish to create a fully customised live version of Arch Linux, pre-installed with all your favourite programs and configurations, use "releng".<br />
If you just want to create the most basic live media, with no pre-installed packages and minimalistic configurations, then use "baseline".<br />
<br />
So, depending on your needs, execute the following, replacing 'PROFILE' with either '''releng''' or '''baseline'''.<br />
# cp -r /usr/share/archiso/configs/'''PROFILE'''/ ~USER/archlive<br />
<br />
If you are using the 'releng' profile to make a fully customised image, then you can proceed onto [[Archiso#Configure_our_live_medium]].<br />
<br />
If you are using the 'baseline' profile to create a bare bones, installation image, then you won't be needing to do any customisations and can proceed onto [[Archiso#Build_the_ISO]]<br />
<br />
== Setup (manual way) ==<br />
{{Note|If you have already completed Setup the 'automatic' way, using the steps above, then you do not need to read this section.}}<br />
<br />
Setup a base filesystem<br />
# mkarchiso init<br />
<br />
Install other packages (optional)<br />
# mkarchiso -p "pkg1 pkg2 pkg3 ... pkgN" install<br />
<br />
At this point, customize anything that you want in root-image, then exit when done.<br />
<br />
# mkarchiso -r "bash" run<br />
<br />
Setup initramfs image.<br />
Copy needed hooks to root-image<br />
<br />
# cp /usr/lib/initcpio/hooks/archiso work/root-image/usr/lib/initcpio/hooks<br />
# cp /usr/lib/initcpio/install/archiso work/root-image/usr/lib/initcpio/install<br />
<br />
Create a config for mkinitcpio '''work/root-image/etc/mkinitcpio-archiso.conf'''<br />
HOOKS="base udev archiso pata scsi sata usb fw filesystems usbinput"<br />
COMPRESSION="xz"<br />
<br />
Create a folder named as your PC's architecture, and generate the initramfs image:<br />
# mkdir work/root-image/boot/i686<br />
# mkarchiso -r "mkinitcpio -c /etc/mkinitcpio-archiso.conf -k /boot/vmlinuz-linux -g /boot/i686/archiso.img" run<br />
<br />
Move kernel/initramfs to boot/<br />
# mkdir -p work/iso/arch/boot/i686<br />
# mv work/root-image/boot/vmlinuz-linux work/iso/arch/boot/i686/vmlinuz<br />
# mv work/root-image/boot/i686/archiso.img work/iso/arch/boot/i686/archiso.img<br />
<br />
Setup syslinux<br />
<br />
Create a directory for it.<br />
# mkdir -p work/iso/arch/boot/syslinux<br />
<br />
Create a '''work/iso/arch/boot/syslinux/syslinux.cfg''' file.<br />
<br />
{{bc|1=<br />
DEFAULT menu.c32<br />
PROMPT 0<br />
MENU TITLE Arch Linux<br />
TIMEOUT 300<br />
<br />
LABEL arch<br />
MENU LABEL Arch Linux<br />
LINUX /arch/boot/i686/vmlinuz<br />
INITRD /arch/boot/i686/archiso.img<br />
APPEND archisolabel=MY_ARCH<br />
<br />
ONTIMEOUT arch<br />
}}<br />
<br />
Copy menu.c32 needed by previous config.<br />
# cp work/root-image/usr/lib/syslinux/menu.c32 work/iso/arch/boot/syslinux/<br />
<br />
Setup isolinux (optional, only needed for booteable iso)<br />
<br />
# mkdir work/iso/isolinux<br />
# cp work/root-image/usr/lib/syslinux/isolinux.bin work/iso/isolinux/<br />
# cp work/root-image/usr/lib/syslinux/isohdpfx.bin work/iso/isolinux/<br />
<br />
Create a '''work/iso/isolinux/isolinux.cfg'''<br />
{{bc|<br />
DEFAULT loadconfig<br />
<br />
LABEL loadconfig<br />
CONFIG /arch/boot/syslinux/syslinux.cfg<br />
APPEND /arch/boot/syslinux/<br />
}}<br />
<br />
Create an '''work/iso/arch/aitab''' file.<br />
# <img> <mnt> <arch> <sfs_comp> <fs_type> <fs_size><br />
root-image / i686 xz ext4 50%<br />
<br />
Build all filesystem images specified in aitab (.fs .fs.sfs .sfs)<br />
# mkarchiso prepare<br />
<br />
Generate an ISO 9660 with "El Torito" boot image (optional)<br />
# mkarchiso -L "MY_ARCH" iso "my-arch.iso"<br />
<br />
== Configure our live medium ==<br />
<br />
This section details configuring the image you will be creating, allowing you to define the packages and configurations you want your live image to contain.<br />
<br />
Change into the directory we created earlier (~/archlive/releng/ if you have been following this guide), you will see a number of files and directories; we are only concerned with a few of these, mainly: <br />
packages.* - this is where you list, line by line, the packages you want to have installed, and<br />
the root-image directory - this directory acts as an overlay and it is where you make all the customisations.<br />
<br />
=== Installing packages ===<br />
<br />
You will want to create a list of packages you want installed on your live CD system. A file full of package names, one-per-line, is the format for this. This is '''''great''''' for special interest live CDs, just specify packages you want and bake the image.<br />
Edit the packages.i686, or packages.x86_64 file depending on whether you are create a 32bit, or 64bit image, respectively.<br />
<br />
{{Tip|You can also create a '''[[custom local repository]]''' for the purpose of preparing custom packages or packages from [[AUR]]/[[ABS]]. Just add your local repository at the first position (for top priority) of your build machine's '''pacman.conf''' and you are good to go!}}<br />
<br />
=== Adding a user ===<br />
<br />
There are two methods to creating a user: either by adding the relevant useradd command to rc.local, or by copying over (and modifying) /etc/shadow, /etc/passwd, and /etc/group.<br />
The latter method shall be discussed here.<br />
<br />
Copy your /etc/shadow, /etc/passwd, and /etc/group from your '''host''' system to the /etc/ directory '''where you now working''' (which should be ~/archlive/releng/root-image/etc)<br />
e.g.<br />
# cp /etc/{shadow,passwd,group} ~/archlive/releng/root-image/etc/<br />
<br />
{{Warning|The shadow file will contain your encrypted password. I recommend before you copy the shadow file over, you change the password of your host user to that which you want your live user to have, copy the shadow file over, and then change back your password.}}<br />
<br />
=== Adding files to image ===<br />
<br />
{{Note|You must be root to do this, do not change the ownership of any of the files you copy over, '''everything''' within the root-image directory must be root owned. Proper ownerships will be sorted out shortly.}}<br />
<br />
The root-image directory acts as an overlay, think of it as root directory '/' on your current system, so any files you place within this directory will be copied over on boot-up.<br />
<br />
So if you have a set of iptables scripts on your current system you want to be used on you live image, copy them over as such:<br />
# cp -r /etc/iptables ~/archlive/releng/root-image/etc<br />
<br />
Placing files in the users home directory is a little different. Do not place them within root-image/home, but instead create a skel directory within root-image/ and place them there. We will then add the relevant commands to the rc.local we are going to create to copy them over on boot and sort out the permissions.<br />
<br />
First, create the skel directory; making sure you are within ~/archlive/releng/root-image/etc directory (if this is where you are working from):<br />
# cd ~/archlive/releng/root-image/etc && mkdir skel<br />
<br />
Now copy the 'home' files to the skel directory, again doing everything as root!<br />
e.g for .bashrc. <br />
# cp ~/.bashrc ~/archlive/releng/root-image/etc/skel/<br />
<br />
Inside the root-image/etc/ directory, create the rc.local file, and '''make sure''' you make it executable:<br />
<br />
# cd ~/archlive/releng/root-image/etc && touch rc.local && chmod +x rc.local<br />
<br />
Now add the all of following to rc.local, replacing 'youruser' with the user you specified earlier.<br />
# Create the user directory for live session<br />
if [ ! -d /home/'''youruser''' ]; then<br />
mkdir /home/'''youruser''' && chown '''youruser''' /home/'''youruser'''<br />
fi<br />
# Copy files over to home<br />
su -c "cp -r /etc/skel/.[a-zA-Z0-9]* /home/'''youruser'''/" '''youruser'''<br />
<br />
=== aitab ===<br />
<br />
The default file should work fine, so you should not need to touch it.<br />
<br />
The aitab file holds information about the filesystems images that must be created by mkarchiso and mounted at initramfs stage from the archiso hook.<br />
It consists of some fields which define the behaviour of images.<br />
<br />
# <img> <mnt> <arch> <sfs_comp> <fs_type> <fs_size><br />
<br />
; <img>: Image name without extension (.fs .fs.sfs .sfs).<br />
; <mnt>: Mount point.<br />
; <arch>: Architecture { i686 | x86_64 | any }.<br />
; <sfs_comp>: SquashFS compression type { gzip | lzo | xz }.<br />
; <fs_type>: Set the filesystem type of the image { ext4 | ext3 | ext2 | xfs }. A special value of "none" denotes no usage of a filesystem. In that case all files are pushed directly to SquashFS filesystem.<br />
; <fs_size>: An absolute value of file system image size in MiB (example: 100, 1000, 4096, etc) A relative value of file system free space [in percent] {1%..99%} (example 50%, 10%, 7%). This is an estimation, and calculated in a simple way. Space used + 10% (estimated for metadata overhead) + desired %<br />
<br />
{{Note|Some combinations are invalid. Example both sfs_comp and fs_type are set to none}}<br />
<br />
=== Boot Loader ===<br />
The default file should work fine, so you should not need to touch it.<br />
<br />
Due to the modular nature of isolinux, you are able to use lots of addons since all *.c32 files are copied and available to you. Take a look at the [http://syslinux.zytor.com/wiki/index.php/SYSLINUX official syslinux site] and the [http://projects.archlinux.org/archiso.git/tree/configs/syslinux-iso/boot-files archiso git repo]. Using said addons, it is possible to make visually attractive and complex menus. See [http://syslinux.zytor.com/wiki/index.php/Comboot/menu.c32 here].<br />
<br />
=== Finishing the root-image ===<br />
Some tips that will not be covered in this article because there are other articles on this wiki that already do, but please feel free to add them here.<br />
*Configure an ''inittab'' to start into X at boot time<br />
*Configure the ''hosts'' file<br />
*Configure ''rc.conf'' (no fancy modules required here)<br />
*Configure ''sudoers''<br />
*Configure ''rc.local''<br />
*Put additional artworks onto the medium <br />
*Put arbitrary binary stuff into opt/<br />
<br />
== Build the ISO ==<br />
<br />
Now you are ready to turn your files into the .iso which you can then burn to CD or USB:<br />
Inside the directory you are working with, either ~/archlive/releng, or ~/archlive/baseline, execute:<br />
<br />
# ./build.sh -v build single<br />
<br />
The script will now download and install the packages you specified to work/*/root-image, create the kernel and init images, apply your customizations and finally build the iso into out/.<br />
<br />
== Using the ISO ==<br />
=== CD ===<br />
Just burn the iso to a cd. You can follow [[CD Burning]] as you wish.<br />
=== USB ===<br />
You can now dd the iso file onto a USB using dd, an example of which:<br />
# dd if=~/archlive/releng/out/*.iso of=/dev/sdx<br />
You will have to adjust accordingly, and make sure you choose the right output file! A simple mistake here will destory data on your harddisk.<br />
=== grub4dos ===<br />
Grub4dos is a utility that can be used to create multiboot usbs, able to boot multiple linux distros from the same usb stick.<br />
<br />
To boot the generated system on a usb with grub4dos already installed, loop mount the ISO and copy the entire {{ic|/arch}} directory to the '''root of the usb'''.<br />
Then edit the {{ic|menu.lst}} file from the grub4dos (it must be on the usb root) and add this lines:<br />
{{bc|<nowiki><br />
title Archlinux x86_64<br />
kernel /arch/boot/x86_64/vmlinuz archisolabel=<your usb label><br />
initrd /arch/boot/x86_64/archiso.img<br />
</nowiki>}}<br />
Change the {{ic|x86_64}} part as necessary and put your '''real''' usb label there.<br />
== See also ==<br />
*[http://projects.archlinux.org/?p=archiso.git;a=summary Archiso project page]<br />
*[[Archiso_as_pxe_server|Archiso as pxe server]]<br />
*[https://kroweer.wordpress.com/2011/09/07/creating-a-custom-arch-linux-live-usb Step-by-step tutorial on using ArchISO]<br />
*[http://didjix.blogspot.com/ A live DJ distribution powered by ArchLinux and built with Archiso]</div>Brazier89https://wiki.archlinux.org/index.php?title=Archiso&diff=233036Archiso2012-11-01T16:23:07Z<p>Brazier89: /* Setup */</p>
<hr />
<div>[[Category:Live Arch systems]]<br />
[[el:Archiso]]<br />
[[fr:Archiso]]<br />
[[it:Archiso]]<br />
[[nl:Archiso]]<br />
[[ru:Archiso]]<br />
[[uk:Archiso]]<br />
'''Archiso''' is a small set of bash scripts that is capable of building fully functional Arch Linux based live CD and USB images. It is a very generic tool, so it could potentially be used to generate anything from rescue systems, install disks, to special interest live CD/DVD/USB systems, and who knows what else. Simply put, if it involves Arch on a shiny coaster, it can do it.<br />
The heart and soul of Archiso is mkarchiso. All of its options are documented in its usage output, so its direct usage won't be covered here. Instead, this wiki article will act as a guide for rolling your own live mediums in no time!<br />
<br />
== Setup ==<br />
<br />
Before we begin, we need to grab the archiso scripts which carry out the beef of the work for us.<br />
<br />
# pacman -S archiso<br />
<br />
{{Note|1=Alternatively, the GIT version can be built and installed [https://aur.archlinux.org/packages.php?ID=25996 from the AUR].}}<br />
<br />
Create a directory to work within, this is where all the modifications to the live image will take place: ~/archlive should do fine.<br />
$ mkdir ~/archlive<br />
<br />
The archiso scripts that were installed to the host system earlier now need to be copied over into the newly created directory you will be working within.<br />
Archiso comes with two "profiles": releng, and baseline.<br />
If you wish to create a fully customised live version of Arch Linux, pre-installed with all your favourite programs and configurations, use "releng".<br />
If you just want to create the most basic live media, with no pre-installed packages and minimalistic configurations, then use "baseline".<br />
<br />
So, depending on your needs, execute the following, replacing 'PROFILE' with either '''releng''' or '''baseline'''.<br />
# cp -r /usr/share/archiso/configs/'''PROFILE'''/ ~USER/archlive<br />
<br />
If you are using the 'releng' profile to make a fully customised image, then you can proceed onto [[Archiso#Configure_our_live_medium]].<br />
<br />
If you are using the 'baseline' profile to create a bare bones, installation image, then you won't be needing to do any customisations and can proceed onto [[Archiso#Build_the_ISO]]<br />
<br />
== Setup (manual way) ==<br />
{{Note|If you have already completed Setup the 'automatic' way, using the steps above, then you do not need to read this section.}}<br />
<br />
Setup a base filesystem<br />
# mkarchiso init<br />
<br />
Install other packages (optional)<br />
# mkarchiso -p "pkg1 pkg2 pkg3 ... pkgN" install<br />
<br />
At this point, customize anything that you want in root-image, then exit when done.<br />
<br />
# mkarchiso -r "bash" run<br />
<br />
Setup initramfs image.<br />
Copy needed hooks to root-image<br />
<br />
# cp /usr/lib/initcpio/hooks/archiso work/root-image/usr/lib/initcpio/hooks<br />
# cp /usr/lib/initcpio/install/archiso work/root-image/usr/lib/initcpio/install<br />
<br />
Create a config for mkinitcpio '''work/root-image/etc/mkinitcpio-archiso.conf'''<br />
HOOKS="base udev archiso pata scsi sata usb fw filesystems usbinput"<br />
COMPRESSION="xz"<br />
<br />
Create a folder named as your PC's architecture, and generate the initramfs image:<br />
# mkdir work/root-image/boot/i686<br />
# mkarchiso -r "mkinitcpio -c /etc/mkinitcpio-archiso.conf -k /boot/vmlinuz-linux -g /boot/i686/archiso.img" run<br />
<br />
Move kernel/initramfs to boot/<br />
# mkdir -p work/iso/arch/boot/i686<br />
# mv work/root-image/boot/vmlinuz-linux work/iso/arch/boot/i686/vmlinuz<br />
# mv work/root-image/boot/i686/archiso.img work/iso/arch/boot/i686/archiso.img<br />
<br />
Setup syslinux<br />
<br />
Create a directory for it.<br />
# mkdir -p work/iso/arch/boot/syslinux<br />
<br />
Create a '''work/iso/arch/boot/syslinux/syslinux.cfg''' file.<br />
<br />
{{bc|1=<br />
DEFAULT menu.c32<br />
PROMPT 0<br />
MENU TITLE Arch Linux<br />
TIMEOUT 300<br />
<br />
LABEL arch<br />
MENU LABEL Arch Linux<br />
LINUX /arch/boot/i686/vmlinuz<br />
INITRD /arch/boot/i686/archiso.img<br />
APPEND archisolabel=MY_ARCH<br />
<br />
ONTIMEOUT arch<br />
}}<br />
<br />
Copy menu.c32 needed by previous config.<br />
# cp work/root-image/usr/lib/syslinux/menu.c32 work/iso/arch/boot/syslinux/<br />
<br />
Setup isolinux (optional, only needed for booteable iso)<br />
<br />
# mkdir work/iso/isolinux<br />
# cp work/root-image/usr/lib/syslinux/isolinux.bin work/iso/isolinux/<br />
# cp work/root-image/usr/lib/syslinux/isohdpfx.bin work/iso/isolinux/<br />
<br />
Create a '''work/iso/isolinux/isolinux.cfg'''<br />
{{bc|<br />
DEFAULT loadconfig<br />
<br />
LABEL loadconfig<br />
CONFIG /arch/boot/syslinux/syslinux.cfg<br />
APPEND /arch/boot/syslinux/<br />
}}<br />
<br />
Create an '''work/iso/arch/aitab''' file.<br />
# <img> <mnt> <arch> <sfs_comp> <fs_type> <fs_size><br />
root-image / i686 xz ext4 50%<br />
<br />
Build all filesystem images specified in aitab (.fs .fs.sfs .sfs)<br />
# mkarchiso prepare<br />
<br />
Generate an ISO 9660 with "El Torito" boot image (optional)<br />
# mkarchiso -L "MY_ARCH" iso "my-arch.iso"<br />
<br />
== Configure our live medium ==<br />
<br />
This section details configuring the image you will be creating, allowing you to define the packages and configurations you want your live image to contain.<br />
<br />
Change into the directory we created earlier (~/archlive/releng/ if you have been following this guide), you will see a number of files and directories; we are only concerned with a few of these, mainly: <br />
packages.* - this is where you list, line by line, the packages you want to have installed, and<br />
the root-image directory - this directory acts as an overlay and it is where you make all the customisations.<br />
<br />
=== Installing packages ===<br />
<br />
You will want to create a list of packages you want installed on your live CD system. A file full of package names, one-per-line, is the format for this. This is '''''great''''' for special interest live CDs, just specify packages you want and bake the image.<br />
Edit the packages.i686, or packages.x86_64 file depending on whether you are create a 32bit, or 64bit image, respectively.<br />
<br />
{{Tip|You can also create a '''[[custom local repository]]''' for the purpose of preparing custom packages or packages from [[AUR]]/[[ABS]]. Just add your local repository at the first position (for top priority) of your build machine's '''pacman.conf''' and you are good to go!}}<br />
<br />
=== Adding a user ===<br />
<br />
There are two methods to creating a user: either by adding the relevant useradd command to rc.local, or by copying over (and modifying) /etc/shadow, /etc/passwd, and /etc/group.<br />
The latter method shall be discussed here.<br />
<br />
Copy your /etc/shadow, /etc/passwd, and /etc/group from your '''host''' system to the /etc/ directory '''where you now working''' (which should be ~/archlive/releng/root-image/etc)<br />
e.g.<br />
# cp /etc/{shadow,passwd,group} ~/archlive/releng/root-image/etc/<br />
<br />
{{Warning|The shadow file will contain your encrypted password. I recommend before you copy the shadow file over, you change the password of your host user to that which you want your live user to have, copy the shadow file over, and then change back your password.}}<br />
<br />
=== Adding files to image ===<br />
<br />
{{Note|You must be root to do this, do not change the ownership of any of the files you copy over, '''everything''' within the root-image directory must be root owned. Proper ownerships will be sorted out shortly.}}<br />
<br />
The root-image directory acts as an overlay, think of it as root directory '/' on your current system, so any files you place within this directory will be copied over on boot-up.<br />
<br />
So if you have a set of iptables scripts on your current system you want to be used on you live image, copy them over as such:<br />
# cp -r /etc/iptables ~/archlive/releng/root-image/etc<br />
<br />
Placing files in the users home directory is a little different. Do not place them within root-image/home, but instead create a skel directory within root-image/ and place them there. We will then add the relevant commands to the rc.local we are going to create to copy them over on boot and sort out the permissions.<br />
<br />
First, create the skel directory; making sure you are within ~/archlive/releng/root-image/etc directory (if this is where you are working from):<br />
# cd ~/archlive/releng/root-image/etc && mkdir skel<br />
<br />
Now copy the 'home' files to the skel directory, again doing everything as root!<br />
e.g for .bashrc. <br />
# cp ~/.bashrc ~/archlive/releng/root-image/etc/skel/<br />
<br />
Inside the root-image/etc/ directory, create the rc.local file, and '''make sure''' you make it executable:<br />
<br />
# cd ~/archlive/releng/root-image/etc && touch rc.local && chmod +x rc.local<br />
<br />
Now add the all of following to rc.local, replacing 'youruser' with the user you specified earlier.<br />
# Create the user directory for live session<br />
if [ ! -d /home/'''youruser''' ]; then<br />
mkdir /home/'''youruser''' && chown '''youruser''' /home/'''youruser'''<br />
fi<br />
# Copy files over to home<br />
su -c "cp -r /etc/skel/.[a-zA-Z0-9]* /home/'''youruser'''/" '''youruser'''<br />
<br />
=== aitab ===<br />
<br />
The default file should work fine, so you should not need to touch it.<br />
<br />
The aitab file holds information about the filesystems images that must be created by mkarchiso and mounted at initramfs stage from the archiso hook.<br />
It consists of some fields which define the behaviour of images.<br />
<br />
# <img> <mnt> <arch> <sfs_comp> <fs_type> <fs_size><br />
<br />
; <img>: Image name without extension (.fs .fs.sfs .sfs).<br />
; <mnt>: Mount point.<br />
; <arch>: Architecture { i686 | x86_64 | any }.<br />
; <sfs_comp>: SquashFS compression type { gzip | lzo | xz }.<br />
; <fs_type>: Set the filesystem type of the image { ext4 | ext3 | ext2 | xfs }. A special value of "none" denotes no usage of a filesystem. In that case all files are pushed directly to SquashFS filesystem.<br />
; <fs_size>: An absolute value of file system image size in MiB (example: 100, 1000, 4096, etc) A relative value of file system free space [in percent] {1%..99%} (example 50%, 10%, 7%). This is an estimation, and calculated in a simple way. Space used + 10% (estimated for metadata overhead) + desired %<br />
<br />
{{Note|Some combinations are invalid. Example both sfs_comp and fs_type are set to none}}<br />
<br />
=== Boot Loader ===<br />
The default file should work fine, so you should not need to touch it.<br />
<br />
Due to the modular nature of isolinux, you are able to use lots of addons since all *.c32 files are copied and available to you. Take a look at the [http://syslinux.zytor.com/wiki/index.php/SYSLINUX official syslinux site] and the [http://projects.archlinux.org/archiso.git/tree/configs/syslinux-iso/boot-files archiso git repo]. Using said addons, it is possible to make visually attractive and complex menus. See [http://syslinux.zytor.com/wiki/index.php/Comboot/menu.c32 here].<br />
<br />
=== Finishing the root-image ===<br />
Some tips that will not be covered in this article because there are other articles on this wiki that already do, but please feel free to add them here.<br />
*Configure an ''inittab'' to start into X at boot time<br />
*Configure the ''hosts'' file<br />
*Configure ''rc.conf'' (no fancy modules required here)<br />
*Configure ''sudoers''<br />
*Configure ''rc.local''<br />
*Put additional artworks onto the medium <br />
*Put arbitrary binary stuff into opt/<br />
<br />
== Build the ISO ==<br />
<br />
Now you are ready to turn your files into the .iso which you can then burn to CD or USB:<br />
Inside the directory you are working with, either ~/archlive/releng, or ~/archlive/baseline, execute:<br />
<br />
# ./build.sh -v build single netinstall<br />
<br />
You can replace 'netinstall' with 'core' if you wish; however, doing so will cache all of the packages pacman downloads into the iso file, which will vastly increase it's size.<br />
<br />
The script will now download and install the packages you specified to work/*/root-image, create the kernel and init images, apply your customizations and finally build the iso into out/.<br />
== Using the ISO ==<br />
=== CD ===<br />
Just burn the iso to a cd. You can follow [[CD Burning]] as you wish.<br />
=== USB ===<br />
You can now dd the iso file onto a USB using dd, an example of which:<br />
# dd if=~/archlive/releng/out/*.iso of=/dev/sdx<br />
You will have to adjust accordingly, and make sure you choose the right output file! A simple mistake here will destory data on your harddisk.<br />
=== grub4dos ===<br />
Grub4dos is a utility that can be used to create multiboot usbs, able to boot multiple linux distros from the same usb stick.<br />
<br />
To boot the generated system on a usb with grub4dos already installed, loop mount the ISO and copy the entire {{ic|/arch}} directory to the '''root of the usb'''.<br />
Then edit the {{ic|menu.lst}} file from the grub4dos (it must be on the usb root) and add this lines:<br />
{{bc|<nowiki><br />
title Archlinux x86_64<br />
kernel /arch/boot/x86_64/vmlinuz archisolabel=<your usb label><br />
initrd /arch/boot/x86_64/archiso.img<br />
</nowiki>}}<br />
Change the {{ic|x86_64}} part as necessary and put your '''real''' usb label there.<br />
== See also ==<br />
*[http://projects.archlinux.org/?p=archiso.git;a=summary Archiso project page]<br />
*[[Archiso_as_pxe_server|Archiso as pxe server]]<br />
*[https://kroweer.wordpress.com/2011/09/07/creating-a-custom-arch-linux-live-usb Step-by-step tutorial on using ArchISO]<br />
*[http://didjix.blogspot.com/ A live DJ distribution powered by ArchLinux and built with Archiso]</div>Brazier89https://wiki.archlinux.org/index.php?title=Minecraft&diff=229151Minecraft2012-10-17T02:38:59Z<p>Brazier89: /* Minecraft Server */</p>
<hr />
<div>Minecraft is a commercial game very popular with geeks. It's a game about blocks. You can build a computer out of the game thanks to logical switches. There is a parallel world. Zombies, pigs, spiders, sheeps, wolves that you can tame, etc...<br />
This wiki page is here to help you install the game :)<br />
<br />
==Installation==<br />
{{AUR|minecraft}} is available in the [[AUR]]. This package includes the official game plus a script for launching it.<br />
<br />
==Setting Up Java==<br />
Minecraft should work out-of-the-box with a couple of the various Java JREs.<br />
<br />
===OpenJDK6===<br />
Minecraft should 'just work' with OpenJDK6. Install it from community: <br />
# pacman -S openjdk6<br />
<br />
===OpenJDK7===<br />
OpenJDK7 works with Minecraft too:<br />
# pacman -S openjdk7<br />
If Minecraft has issues (sticky keys, stuck on pause menu, etc.), you can force it to use the newest version of LWJGL:<br />
<br />
*Download LWJGL 2.8.4 from [http://sourceforge.net/projects/java-game-lib/files/Official%20Releases/LWJGL%202.8.4/lwjgl-2.8.4.zip/download here]<br />
*Replace the following files in .minecraft/bin/ with the corresponding versions in lwjgl-2.8.4/jar<br />
<br />
jinput.jar<br />
lwjgl.jar<br />
lwjgl_util.jar <br />
*Replace the following files in .minecraft/bin/natives/ with lwjgl-2.8.4/natives/linux<br />
libjinput-linux.so<br />
libjinput-linux64.so<br />
liblwjgl.so<br />
liblwjgl64.so<br />
libopenal.so<br />
libopenal64.so<br />
<br />
==Running Minecraft==<br />
<br />
If you installed Minecraft from the AUR, you can use the included script:<br />
$ minecraft<br />
<br />
Otherwise, you will need to manually launch Minecraft:<br />
$ java -jar $HOME/.minecraft/minecraft.jar<br />
<br />
To allocate more RAM to the game, include Xms and Xmx arguments:<br />
$ java -jar -Xms1024M -Xmx2048M $HOME/.minecraft/minecraft.jar<br />
<br />
You can change these depending on the amount of RAM that you have. The Xms argument specifies the minimum amount of RAM to allocate to the program, and the Xmx argument specifies the maximum amount.<br />
<br />
==Extras==<br />
There are several [http://www.minecraftwiki.net/wiki/Programs_and_editors programs and editors] which can make your Minecraft experience a little easier to navigate. The most common of these programs are map generators. Using one of these programs will allow you to load up a Minecraft world file and render it as a 2D image, providing you with a top-down map of the world.<br />
===Minutor===<br />
Minutor is described as a minimalistic map generator for Minecraft. Don't let this mislead you, it generates maps of existing worlds, not the other way around. You are provided with a simple GTK based interface for viewing your world. Several rendering modes are available, as well as custom coloring modes and the ability to slice through z-levels. {{aur|minutor}} is available in the [[AUR]].<br />
<br />
==Minecraft Server==<br />
You can also run a dedicated Minecraft server:<br />
* Follow the steps above to install [[Java]]<br />
* [http://www.minecraft.net/download.jsp Download] the multiplayer server from the Minecraft site<br />
* Run the server:<br />
$ java -Xmx2048M -Xms2048M -jar minecraft_server.jar nogui<br />
(You can sub the -Xmx and -Xms values for the amount of memory you want your server to use. A good rule of thumb is one GB per ten users.)<br />
* To configure the server, take a look at this [http://www.minecraftwiki.net/wiki/Server.properties wiki page].<br />
===Extras===<br />
* Establishing a Minecraft-specific user is recommended for security. By running Minecraft under an unprivileged user account, anyone who successfully exploits your Minecraft server will only get access to that user account, and not yours.<br />
* To leave the server running unattended, look into [[tmux]] or [[screen]].<br />
* You may wish to modify your server, to provide additional features:<br />
** [http://www.minecraftwiki.net/wiki/Programs_and_editors#Server_Wrappers Server Wrappers] are one way to add administrative capabilities.<br />
** [http://bukkit.org/ Bukkit] is a powerful modding API, with a wide variety of plugins available.<br />
*** If installing the Dynmap plugin, you will need to install fontconfig and libcups to get it to work.<br />
* You might even set up a cron job with a [http://www.minecraftwiki.net/wiki/Programs_and_editors#Mappers mapper] to generate periodic maps of your world.<br />
* ...or you could use [[rsync]] to perform routine backups.<br />
<br />
==Useful links==<br />
* Main site : http://www.minecraft.net/<br />
* Community links: http://www.minecraft.net/community<br />
* Crafting recipies : http://www.minecraftwiki.net/wiki/Crafting<br />
* Data values (useful in multiplayer mode) : http://www.minecraftwiki.net/wiki/Data_values<br />
* Reddit community : http://www.reddit.com/r/minecraft<br />
<br />
[[Category:Gaming]]</div>Brazier89https://wiki.archlinux.org/index.php?title=Archiso&diff=218525Archiso2012-08-18T21:41:32Z<p>Brazier89: /* Setup */</p>
<hr />
<div>[[Category:Live Arch systems]]<br />
[[el:Archiso]]<br />
[[fr:Archiso]]<br />
[[it:Archiso]]<br />
[[nl:Archiso]]<br />
[[ru:Archiso]]<br />
[[uk:Archiso]]<br />
'''Archiso''' is a small set of bash scripts that is capable of building fully functional Arch Linux based live CD and USB images. It is a very generic tool, so it could potentially be used to generate anything from rescue systems, install disks, to special interest live CD/DVD/USB systems, and who knows what else. Simply put, if it involves Arch on a shiny coaster, it can do it.<br />
The heart and soul of Archiso is mkarchiso. All of its options are documented in its usage output, so its direct usage won't be covered here. Instead, this wiki article will act as a guide for rolling your own live mediums in no time!<br />
<br />
<br />
== Setup ==<br />
<br />
Before we begin, we need to grab the archiso scripts which carry out the beef of the work for us. You can get archiso from Git (recommended) or from [https://aur.archlinux.org/packages.php?ID=25996 aur]. We also need a few packages which archiso relies on; the following commands take care of this for us:<br />
<br />
# pacman -S make patch git libisoburn squashfs-tools dosfstools rsync lynx patch --needed<br />
# git clone git://projects.archlinux.org/archiso.git<br />
# make -C archiso install<br />
<br />
Create a directory to work within, this is where all the modifications to the live image will take place: ~/archlive should do fine.<br />
$ mkdir ~/archlive<br />
<br />
The archiso scripts that were installed to the host system earlier now need to be copied over into the newly created directory you will be working within.<br />
Archiso comes with two "profiles": releng, and baseline.<br />
If you wish to create a fully customised live version of Arch Linux, pre-installed with all your favourite programs and configurations, use "releng".<br />
If you just want to create the most basic live media, with no pre-installed packages and minimalistic configurations, then use "baseline".<br />
<br />
So, depending on your needs, execute the following, replacing 'PROFILE' with either '''releng''' or '''baseline'''.<br />
# cp -r /usr/share/archiso/configs/'''PROFILE'''/ ~/archlive<br />
<br />
If you are using the 'releng' profile to make a fully customised image, then you can proceed onto [[Archiso#Configure_our_live_medium]].<br />
<br />
If you are using the 'baseline' profile to create a bare bones, installation image, then you won't be needing to do any customisations and can proceed onto [[Archiso#Build_the_ISO]]<br />
<br />
== Setup (manual way) ==<br />
{{Note|If you have already completed Setup the 'automatic' way, using the steps above, then you do not need to read this section.}}<br />
<br />
Setup a base filesystem<br />
# mkarchiso init<br />
<br />
Install other packages (optional)<br />
# mkarchiso -p "pkg1 pkg2 pkg3 ... pkgN" install<br />
<br />
At this point, customize anything that you want in root-image, then exit when done.<br />
<br />
# mkarchiso -r "bash" run<br />
<br />
Setup initramfs image.<br />
Copy needed hooks to root-image<br />
<br />
# cp /usr/lib/initcpio/hooks/archiso work/root-image/usr/lib/initcpio/hooks<br />
# cp /usr/lib/initcpio/install/archiso work/root-image/usr/lib/initcpio/install<br />
<br />
Create a config for mkinitcpio '''work/root-image/etc/mkinitcpio-archiso.conf'''<br />
HOOKS="base udev archiso pata scsi sata usb fw filesystems usbinput"<br />
COMPRESSION="xz"<br />
<br />
Create a folder named as your PC's architecture, and generate the initramfs image:<br />
# mkdir work/root-image/boot/i686<br />
# mkarchiso -r "mkinitcpio -c /etc/mkinitcpio-archiso.conf -k /boot/vmlinuz-linux -g /boot/i686/archiso.img" run<br />
<br />
Move kernel/initramfs to boot/<br />
# mkdir -p work/iso/arch/boot/i686<br />
# mv work/root-image/boot/vmlinuz-linux work/iso/arch/boot/i686/vmlinuz<br />
# mv work/root-image/boot/i686/archiso.img work/iso/arch/boot/i686/archiso.img<br />
<br />
Setup syslinux<br />
<br />
Create a directory for it.<br />
# mkdir -p work/iso/arch/boot/syslinux<br />
<br />
Create a '''work/iso/arch/boot/syslinux/syslinux.cfg''' file.<br />
<br />
{{bc|1=<br />
DEFAULT menu.c32<br />
PROMPT 0<br />
MENU TITLE Arch Linux<br />
TIMEOUT 300<br />
<br />
LABEL arch<br />
MENU LABEL Arch Linux<br />
LINUX /arch/boot/i686/vmlinuz<br />
INITRD /arch/boot/i686/archiso.img<br />
APPEND archisolabel=MY_ARCH<br />
<br />
ONTIMEOUT arch<br />
}}<br />
<br />
Copy menu.c32 needed by previous config.<br />
# cp work/root-image/usr/lib/syslinux/menu.c32 work/iso/arch/boot/syslinux/<br />
<br />
Setup isolinux (optional, only needed for booteable iso)<br />
<br />
# mkdir work/iso/isolinux<br />
# cp work/root-image/usr/lib/syslinux/isolinux.bin work/iso/isolinux/<br />
# cp work/root-image/usr/lib/syslinux/isohdpfx.bin work/iso/isolinux/<br />
<br />
Create a '''work/iso/isolinux/isolinux.cfg'''<br />
{{bc|<br />
DEFAULT loadconfig<br />
<br />
LABEL loadconfig<br />
CONFIG /arch/boot/syslinux/syslinux.cfg<br />
APPEND /arch/boot/syslinux/<br />
}}<br />
<br />
Create an '''work/iso/arch/aitab''' file.<br />
# <img> <mnt> <arch> <sfs_comp> <fs_type> <fs_size><br />
root-image / i686 xz ext4 50%<br />
<br />
Build all filesystem images specified in aitab (.fs .fs.sfs .sfs)<br />
# mkarchiso prepare<br />
<br />
Generate an ISO 9660 with "El Torito" boot image (optional)<br />
# mkarchiso -L "MY_ARCH" iso "my-arch.iso"<br />
<br />
== Configure our live medium ==<br />
<br />
This section details configuring the image you will be creating, allowing you to define the packages and configurations you want your live image to contain.<br />
<br />
Change into the directory we created earlier (~/archlive/releng/ if you have been following this guide), you will see a number of files and directories; we are only concerned with a few of these, mainly: <br />
packages.* - this is where you list, line by line, the packages you want to have installed, and<br />
the root-image directory - this directory acts as an overlay and it is where you make all the customisations.<br />
<br />
=== Installing packages ===<br />
<br />
You will want to create a list of packages you want installed on your live CD system. A file full of package names, one-per-line, is the format for this. This is '''''great''''' for special interest live CDs, just specify packages you want and bake the image.<br />
Edit the packages.i686, or packages.x86_64 file depending on whether you are create a 32bit, or 64bit image, respectively.<br />
<br />
{{Tip|You can also create a '''[[custom local repository]]''' for the purpose of preparing custom packages or packages from [[AUR]]/[[ABS]]. Just add your local repository at the first position (for top priority) of your build machine's '''pacman.conf''' and you are good to go!}}<br />
<br />
=== Adding a user ===<br />
<br />
There are two methods to creating a user: either by adding the relevant useradd command to rc.local, or by copying over (and modifying) /etc/shadow, /etc/passwd, and /etc/group.<br />
The latter method shall be discussed here.<br />
<br />
Copy your /etc/shadow, /etc/passwd, and /etc/group from your '''host''' system to the /etc/ directory '''where you now working''' (which should be ~/archlive/releng/root-image/etc)<br />
e.g.<br />
# cp /etc/{shadow,passwd,group} ~/archlive/releng/root-image/etc/<br />
<br />
{{Warning|The shadow file will contain your encrypted password. I recommend before you copy the shadow file over, you change the password of your host user to that which you want your live user to have, copy the shadow file over, and then change back your password.}}<br />
<br />
=== Adding files to image ===<br />
<br />
{{Note|You must be root to do this, do not change the ownership of any of the files you copy over, '''everything''' within the root-image directory must be root owned. Proper ownerships will be sorted out shortly.}}<br />
<br />
The root-image directory acts as an overlay, think of it as root directory '/' on your current system, so any files you place within this directory will be copied over on boot-up.<br />
<br />
So if you have a set of iptables scripts on your current system you want to be used on you live image, copy them over as such:<br />
# cp -r /etc/iptables ~/archlive/releng/root-image/etc<br />
<br />
Placing files in the users home directory is a little different. Do not place them within root-image/home, but instead create a skel directory within root-image/ and place them there. We will then add the relevant commands to the rc.local we are going to create to copy them over on boot and sort out the permissions.<br />
<br />
First, create the skel directory; making sure you are within ~/archlive/releng/root-image/etc directory (if this is where you are working from):<br />
# cd ~/archlive/releng/root-image/etc && mkdir skel<br />
<br />
Now copy the 'home' files to the skel directory, again doing everything as root!<br />
e.g for .bashrc. <br />
# cp ~/.bashrc ~/archlive/releng/root-image/etc/skel/<br />
<br />
<br />
Inside the root-image/etc/ directory, create the rc.local file, and '''make sure''' you make it executable:<br />
<br />
# cd ~/archlive/releng/root-image/etc && touch rc.local && chmod +x rc.local<br />
<br />
Now add the all of following to rc.local, replacing 'youruser' with the user you specified earlier.<br />
# Create the user directory for live session<br />
if [ ! -d /home/'''youruser''' ]; then<br />
mkdir /home/'''youruser''' && chown '''youruser''' /home/'''youruser'''<br />
fi<br />
# Copy files over to home<br />
su -c "cp -r /etc/skel/.[a-zA-Z0-9]* /home/'''youruser'''/" '''youruser'''<br />
<br />
=== aitab ===<br />
<br />
The default file should work fine, so you should not need to touch it.<br />
<br />
The aitab file holds information about the filesystems images that must be created by mkarchiso and mounted at initramfs stage from the archiso hook.<br />
It consists of some fields which define the behaviour of images.<br />
<br />
# <img> <mnt> <arch> <sfs_comp> <fs_type> <fs_size><br />
<br />
; <img>: Image name without extension (.fs .fs.sfs .sfs).<br />
; <mnt>: Mount point.<br />
; <arch>: Architecture { i686 | x86_64 | any }.<br />
; <sfs_comp>: SquashFS compression type { gzip | lzo | xz }. A special value of "none" denotes no usage of SquashFS.<br />
; <fs_type>: Set the filesystem type of the image { ext4 | ext3 | ext2 | xfs }. A special value of "none" denotes no usage of a filesystem. In that case all files are pushed directly to SquashFS filesystem.<br />
; <fs_size>: An absolute value of file system image size in MiB (example: 100, 1000, 4096, etc) A relative value of file system free space [in percent] {1%..99%} (example 50%, 10%, 7%). This is an estimation, and calculated in a simple way. Space used + 10% (estimated for metadata overhead) + desired %<br />
<br />
{{Note|Some combinations are invalid. Example both sfs_comp and fs_type are set to none}}<br />
<br />
=== Boot Loader ===<br />
The default file should work fine, so you should not need to touch it.<br />
<br />
Due to the modular nature of isolinux, you are able to use lots of addons since all *.c32 files are copied and available to you. Take a look at the [http://syslinux.zytor.com/wiki/index.php/SYSLINUX official syslinux site] and the [http://projects.archlinux.org/archiso.git/tree/configs/syslinux-iso/boot-files archiso git repo]. Using said addons, it is possible to make visually attractive and complex menus. See [http://syslinux.zytor.com/wiki/index.php/Comboot/menu.c32 here].<br />
<br />
=== Finishing the root-image ===<br />
Some tips that will not be covered in this article because there are other articles on this wiki that already do, but please feel free to add them here.<br />
*Configure an ''inittab'' to start into X at boot time<br />
*Configure the ''hosts'' file<br />
*Configure ''rc.conf'' (no fancy modules required here)<br />
*Configure ''sudoers''<br />
*Configure ''rc.local''<br />
*Put additional artworks onto the medium <br />
*Put arbitrary binary stuff into opt/<br />
<br />
== Build the ISO ==<br />
<br />
Now you are ready to turn your files into the .iso which you can then burn to CD or USB:<br />
Inside the directory you are working with, either ~/archlive/releng, or ~/archlive/baseline, execute:<br />
<br />
# ./build.sh -v build single netinstall<br />
<br />
You can replace 'netinstall' with 'core' if you wish; however, doing so will cache all of the packages pacman downloads into the iso file, which will vastly inrease it's size.<br />
<br />
The script will now download and install the packages you specified to work/*/root-image, create the kernel and init images, apply your customizations and finally build the iso into out/.<br />
<br />
You can now dd the iso file onto a USB using dd, an example of which:<br />
# dd if=~/archlive/releng/out/*.iso of=/dev/sdx<br />
You will have to adjust accordingly, and make sure you choose the right output file! A simple mistake here will destory data on your harddisk.<br />
<br />
== See also ==<br />
*[http://projects.archlinux.org/?p=archiso.git;a=summary Archiso project page]<br />
*[[Archiso_as_pxe_server|Archiso as pxe server]]<br />
*[https://kroweer.wordpress.com/2011/09/07/creating-a-custom-arch-linux-live-usb Step-by-step tutorial on using ArchISO]<br />
*[http://didjix.blogspot.com/ A live DJ distribution powered by ArchLinux and built with Archiso]</div>Brazier89https://wiki.archlinux.org/index.php?title=Archiso&diff=215681Archiso2012-07-30T17:19:00Z<p>Brazier89: /* Setup */</p>
<hr />
<div>[[Category:Live Arch systems]]<br />
[[el:Archiso]]<br />
[[fr:Archiso]]<br />
[[it:Archiso]]<br />
[[nl:Archiso]]<br />
[[ru:Archiso]]<br />
[[uk:Archiso]]<br />
'''Archiso''' is a small set of bash scripts that is capable of building fully functional Arch Linux based live CD and USB images. It is a very generic tool, so it could potentially be used to generate anything from rescue systems, install disks, to special interest live CD/DVD/USB systems, and who knows what else. Simply put, if it involves Arch on a shiny coaster, it can do it.<br />
The heart and soul of Archiso is mkarchiso. All of its options are documented in its usage output, so its direct usage won't be covered here. Instead, this wiki article will act as a guide for rolling your own live mediums in no time!<br />
<br />
<br />
== Setup ==<br />
<br />
Before we begin, we need to grab the archiso scripts which carry out the beef of the work for us. You can get archiso from Git (recommended) or from [https://aur.archlinux.org/packages.php?ID=25996 aur]. We also need a few packages which archiso relies on; the following commands take care of this for us:<br />
<br />
# pacman -S make patch git libisoburn squashfs-tools dosfstools rsync lynx patch --needed<br />
# git clone git://projects.archlinux.org/archiso.git<br />
# make -C archiso/archiso install<br />
<br />
Create a directory to work within, this is where all the modifications to the live image will take place: ~/archlive should do fine.<br />
$ mkdir ~/archlive<br />
<br />
The archiso scripts that were installed to the host system earlier now need to be copied over into the newly created directory you will be working within.<br />
Archiso comes with two "profiles": releng, and baseline.<br />
If you wish to create a fully customised live version of Arch Linux, pre-installed with all your favourite programs and configurations, use "releng".<br />
If you just want to create the most basic live media, with no pre-installed packages and minimalistic configurations, then use "baseline".<br />
<br />
So, depending on your needs, execute the following, replacing 'PROFILE' with either '''releng''' or '''baseline'''.<br />
# cp -r /usr/share/archiso/configs/'''PROFILE'''/ ~/archlive<br />
<br />
If you are using the 'releng' profile to make a fully customised image, then you can proceed onto [[Archiso#Configure_our_live_medium]].<br />
<br />
If you are using the 'baseline' profile to create a bare bones, installation image, then you won't be needing to do any customisations and can proceed onto [[Archiso#Build_the_ISO]]<br />
<br />
== Setup (manual way) ==<br />
{{Note|If you have already completed Setup the 'automatic' way, using the steps above, then you do not need to read this section.}}<br />
<br />
Setup a base filesystem<br />
# mkarchiso init<br />
<br />
Install other packages (optional)<br />
# mkarchiso -p "pkg1 pkg2 pkg3 ... pkgN" install<br />
<br />
At this point, customize anything that you want in root-image, then exit when done.<br />
<br />
# mkarchiso -r "bash" run<br />
<br />
Setup initramfs image.<br />
Copy needed hooks to root-image<br />
<br />
# cp /usr/lib/initcpio/hooks/archiso work/root-image/usr/lib/initcpio/hooks<br />
# cp /usr/lib/initcpio/install/archiso work/root-image/usr/lib/initcpio/install<br />
<br />
Create a config for mkinitcpio '''work/root-image/etc/mkinitcpio-archiso.conf'''<br />
HOOKS="base udev archiso pata scsi sata usb fw filesystems usbinput"<br />
COMPRESSION="xz"<br />
<br />
Create a folder named as your PC's architecture, and generate the initramfs image:<br />
# mkdir work/root-image/boot/i686<br />
# mkarchiso -r "mkinitcpio -c /etc/mkinitcpio-archiso.conf -k /boot/vmlinuz-linux -g /boot/i686/archiso.img" run<br />
<br />
Move kernel/initramfs to boot/<br />
# mkdir -p work/iso/arch/boot/i686<br />
# mv work/root-image/boot/vmlinuz-linux work/iso/arch/boot/i686/vmlinuz<br />
# mv work/root-image/boot/i686/archiso.img work/iso/arch/boot/i686/archiso.img<br />
<br />
Setup syslinux<br />
<br />
Create a directory for it.<br />
# mkdir -p work/iso/arch/boot/syslinux<br />
<br />
Create a '''work/iso/arch/boot/syslinux/syslinux.cfg''' file.<br />
<br />
{{bc|1=<br />
DEFAULT menu.c32<br />
PROMPT 0<br />
MENU TITLE Arch Linux<br />
TIMEOUT 300<br />
<br />
LABEL arch<br />
MENU LABEL Arch Linux<br />
LINUX /arch/boot/i686/vmlinuz<br />
INITRD /arch/boot/i686/archiso.img<br />
APPEND archisolabel=MY_ARCH<br />
<br />
ONTIMEOUT arch<br />
}}<br />
<br />
Copy menu.c32 needed by previous config.<br />
# cp work/root-image/usr/lib/syslinux/menu.c32 work/iso/arch/boot/syslinux/<br />
<br />
Setup isolinux (optional, only needed for booteable iso)<br />
<br />
# mkdir work/iso/isolinux<br />
# cp work/root-image/usr/lib/syslinux/isolinux.bin work/iso/isolinux/<br />
# cp work/root-image/usr/lib/syslinux/isohdpfx.bin work/iso/isolinux/<br />
<br />
Create a '''work/iso/isolinux/isolinux.cfg'''<br />
{{bc|<br />
DEFAULT loadconfig<br />
<br />
LABEL loadconfig<br />
CONFIG /arch/boot/syslinux/syslinux.cfg<br />
APPEND /arch/boot/syslinux/<br />
}}<br />
<br />
Create an '''work/iso/arch/aitab''' file.<br />
# <img> <mnt> <arch> <sfs_comp> <fs_type> <fs_size><br />
root-image / i686 xz ext4 50%<br />
<br />
Build all filesystem images specified in aitab (.fs .fs.sfs .sfs)<br />
# mkarchiso prepare<br />
<br />
Generate an ISO 9660 with "El Torito" boot image (optional)<br />
# mkarchiso -L "MY_ARCH" iso "my-arch.iso"<br />
<br />
== Configure our live medium ==<br />
<br />
This section details configuring the image you will be creating, allowing you to define the packages and configurations you want your live image to contain.<br />
<br />
Change into the directory we created earlier (~/archlive/releng/ if you have been following this guide), you will see a number of files and directories; we are only concerned with a few of these, mainly: <br />
packages.* - this is where you list, line by line, the packages you want to have installed, and<br />
the root-image directory - this directory acts as an overlay and it is where you make all the customisations.<br />
<br />
=== Installing packages ===<br />
<br />
You will want to create a list of packages you want installed on your live CD system. A file full of package names, one-per-line, is the format for this. This is '''''great''''' for special interest live CDs, just specify packages you want and bake the image.<br />
Edit the packages.i686, or packages.x86_64 file depending on whether you are create a 32bit, or 64bit image, respectively.<br />
<br />
{{Tip|You can also create a '''[[custom local repository]]''' for the purpose of preparing custom packages or packages from [[AUR]]/[[ABS]]. Just add your local repository at the first position (for top priority) of your build machine's '''pacman.conf''' and you are good to go!}}<br />
<br />
=== Adding a user ===<br />
<br />
There are two methods to creating a user: either by adding the relevant useradd command to rc.local, or by copying over (and modifying) /etc/shadow, /etc/passwd, and /etc/group.<br />
The latter method shall be discussed here.<br />
<br />
Copy your /etc/shadow, /etc/passwd, and /etc/group from your '''host''' system to the /etc/ directory '''where you now working''' (which should be ~/archlive/releng/root-image/etc)<br />
e.g.<br />
# cp /etc/{shadow,passwd,group} ~/archlive/releng/root-image/etc/<br />
<br />
{{Warning|The shadow file will contain your encrypted password. I recommend before you copy the shadow file over, you change the password of your host user to that which you want your live user to have, copy the shadow file over, and then change back your password.}}<br />
<br />
=== Adding files to image ===<br />
<br />
{{Note|You must be root to do this, do not change the ownership of any of the files you copy over, '''everything''' within the root-image directory must be root owned. Proper ownerships will be sorted out shortly.}}<br />
<br />
The root-image directory acts as an overlay, think of it as root directory '/' on your current system, so any files you place within this directory will be copied over on boot-up.<br />
<br />
So if you have a set of iptables scripts on your current system you want to be used on you live image, copy them over as such:<br />
# cp -r /etc/iptables ~/archlive/releng/root-image/etc<br />
<br />
Placing files in the users home directory is a little different. Do not place them within root-image/home, but instead create a skel directory within root-image/ and place them there. We will then add the relevant commands to the rc.local we are going to create to copy them over on boot and sort out the permissions.<br />
<br />
First, create the skel directory; making sure you are within ~/archlive/releng/root-image/etc directory (if this is where you are working from):<br />
# cd ~/archlive/releng/root-image/etc && mkdir skel<br />
<br />
Now copy the 'home' files to the skel directory, again doing everything as root!<br />
e.g for .bashrc. <br />
# cp ~/.bashrc ~/archlive/releng/root-image/etc/skel/<br />
<br />
<br />
Inside the root-image/etc/ directory, create the rc.local file, and '''make sure''' you make it executable:<br />
<br />
# cd ~/archlive/releng/root-image/etc && touch rc.local && chmod +x rc.local<br />
<br />
Now add the all of following to rc.local, replacing 'youruser' with the user you specified earlier.<br />
# Create the user directory for live session<br />
if [ ! -d /home/'''youruser''' ]; then<br />
mkdir /home/'''youruser''' && chown '''youruser''' /home/'''youruser'''<br />
fi<br />
# Copy files over to home<br />
su -c "cp -r /etc/skel/.[a-zA-Z0-9]* /home/'''youruser'''/" '''youruser'''<br />
<br />
=== aitab ===<br />
<br />
The default file should work fine, so you should not need to touch it.<br />
<br />
The aitab file holds information about the filesystems images that must be created by mkarchiso and mounted at initramfs stage from the archiso hook.<br />
It consists of some fields which define the behaviour of images.<br />
<br />
# <img> <mnt> <arch> <sfs_comp> <fs_type> <fs_size><br />
<br />
; <img>: Image name without extension (.fs .fs.sfs .sfs).<br />
; <mnt>: Mount point.<br />
; <arch>: Architecture { i686 | x86_64 | any }.<br />
; <sfs_comp>: SquashFS compression type { gzip | lzo | xz }. A special value of "none" denotes no usage of SquashFS.<br />
; <fs_type>: Set the filesystem type of the image { ext4 | ext3 | ext2 | xfs }. A special value of "none" denotes no usage of a filesystem. In that case all files are pushed directly to SquashFS filesystem.<br />
; <fs_size>: An absolute value of file system image size in MiB (example: 100, 1000, 4096, etc) A relative value of file system free space [in percent] {1%..99%} (example 50%, 10%, 7%). This is an estimation, and calculated in a simple way. Space used + 10% (estimated for metadata overhead) + desired %<br />
<br />
{{Note|Some combinations are invalid. Example both sfs_comp and fs_type are set to none}}<br />
<br />
=== Boot Loader ===<br />
The default file should work fine, so you should not need to touch it.<br />
<br />
Due to the modular nature of isolinux, you are able to use lots of addons since all *.c32 files are copied and available to you. Take a look at the [http://syslinux.zytor.com/wiki/index.php/SYSLINUX official syslinux site] and the [http://projects.archlinux.org/archiso.git/tree/configs/syslinux-iso/boot-files archiso git repo]. Using said addons, it is possible to make visually attractive and complex menus. See [http://syslinux.zytor.com/wiki/index.php/Comboot/menu.c32 here].<br />
<br />
=== Finishing the root-image ===<br />
Some tips that will not be covered in this article because there are other articles on this wiki that already do, but please feel free to add them here.<br />
*Configure an ''inittab'' to start into X at boot time<br />
*Configure the ''hosts'' file<br />
*Configure ''rc.conf'' (no fancy modules required here)<br />
*Configure ''sudoers''<br />
*Configure ''rc.local''<br />
*Put additional artworks onto the medium <br />
*Put arbitrary binary stuff into opt/<br />
<br />
== Build the ISO ==<br />
<br />
Now you are ready to turn your files into the .iso which you can then burn to CD or USB:<br />
Inside the directory you are working with, either ~/archlive/releng, or ~/archlive/baseline, execute:<br />
<br />
# ./build.sh -v build single netinstall<br />
<br />
You can replace 'netinstall' with 'core' if you wish; however, doing so will cache all of the packages pacman downloads into the iso file, which will vastly inrease it's size.<br />
<br />
The script will now download and install the packages you specified to work/*/root-image, create the kernel and init images, apply your customizations and finally build the iso into out/.<br />
<br />
You can now dd the iso file onto a USB using dd, an example of which:<br />
# dd if=~/archlive/releng/out/*.iso of=/dev/sdx<br />
You will have to adjust accordingly, and make sure you choose the right output file! A simple mistake here will destory data on your harddisk.<br />
<br />
== See also ==<br />
*[http://projects.archlinux.org/?p=archiso.git;a=summary Archiso project page]<br />
*[[Archiso_as_pxe_server|Archiso as pxe server]]<br />
*[https://kroweer.wordpress.com/2011/09/07/creating-a-custom-arch-linux-live-usb Step-by-step tutorial on using ArchISO]<br />
*[http://didjix.blogspot.com/ A live DJ distribution powered by ArchLinux and built with Archiso]</div>Brazier89