From ArchWiki

This page is still work in progress

"Hello World"

Hi everyone out there! If you managed to stumble across this page, it's alright, you can pop in. I might have some useful stuff for you!

Post Installation Tips

I usually have a few tips to make sure that I have a good system running that I like, and to get a few annoying things out of the way. So i'll share them with you!

Setting up Pacman

Now, one of the things I like to do is to get all of my most useful repositories onto my /etc/pacman.conf file. So I ALWAYS edit the file, and add some in. If you have a laptop spare, or a windows partition, i would suggest looking at this page for a list of good repositories. I usually add [archlinuxfr] for yaourt, [xyne-any] for powerpill, and [arch-games] for, you know, games.

You should also use the time the installer gives you to config your system to set the Architecture line to get the proper packages for your system, and make sure nothing bad happens.

Installing GRUB2/BURG after installation

Well, basically, I don't like GRUB Legacy because, well, it just looks really old. GRUB2 looks really clean and new-ish! So I'll help you out a little bit with some mix of ArchWiki content that can be found at the GRUB2 page on the wiki. Basically, if you've set up your network before installing (if you're on ethernet or wireless lan) and used DHCP don't worry about the aif-partial-network bit. If you didn't use dhcpcd, I would suggest following the GRUB2 page. Chroot like the page says:

# mount -o bind /dev /mnt/dev
# chroot /mnt bash

then use:

# dhcpcd (interface)

to get your network back. If you used wpa_supplicant, don't use it again! You don't need to. Then, just use pacman -Sy grub2 and you'll have GRUB2!

REMEMBER THIS STEP! (you don't have to, I edited the command to make the root my partition when i forgot to, but lets make it easy) Make a config file for grub:

# grub-mkconfig -o /boot/grub/grub.cfg

and then install grub using:

# grub-install /dev/(partition) --no-floppy

if you want to install to the MBR, use /dev/sda or /dev/sda1. A JFS partition will give you grief, and give you a code in the format (hdx,y) which is USEFUL! If you want to install to a JFS partition, just do:

# grub-setup '(hdx,y)' --skip-fs-probe --force --no-floppy

and it'll be all good. This can be used to install any package onto your system before you boot in, and you can edit all of your configs once you've chrooted

Compiling Kernels

Some arch linux users (like how I was) might still be unaware on how to compile kernels, so I might as well help you out! It's a very useful thing to know, because then you can modify your own kernel to be as big, or small, or feature rich, or feature stripped, as you want! I know there's already pages on this wiki to help you, but I managed to get it done a little bit differently.

Getting your sources

First, you need your kernel source. Mainly this means that this page will be your best friend, but there are three ways to get your source:

Download in a tarball

Using the "Full Source" links means that you can download it as a tarball to your system, unpack it into a folder, and that's your source done! (I'll assume you know how to unpack files either graphically or from the command line)

Git Repository!

For this, you'll need to make sure that git is installed. If you're not sure, can't hurt to run:

# pacman -S git

Then you need to get the source down from the git server to yours. It's best to use the git server if you're using the mainline or nightly server, so you always get the latest one. You need to click "gitweb" and you'll be taken to a different page with three links that'll look like:

git:// http://" " https://" "

Copy one of them, and then paste it after the command:

$ git clone

Note: to paste in terminals, it's normally "Ctrl+Shift+V" You can also add a directory option for it, so if i wanted to take the source and put it into a folder called "linux-nightly", i'd run:

$ git clone git:// linux-nightly

Leaving the directory out means the files will be put in a directory with the name of the .git file it points to (so without the linux-nightly bit at the end, it'd go into a folder called linux-next)

Seems longer, but it means that to update all you need to do is cd to the linux-nightly directory in a terminal, and run:

$ git pull

If you've ever used git or subversion (svn) before, you'll know how cool this is!