Difference between pages "ZFS Install Guide" and "Package:Irssi"

(Difference between pages)
(Genkernel)
 
 
Line 1: Line 1:
== Introduction ==
+
{{Ebuild
 +
|Summary=A modular textUI IRC client with IPv6 support.
 +
|CatPkg=net-irc/irssi
 +
|Maintainer=
 +
|Homepage=http://www.irssi.org/
 +
}}
  
This tutorial will show you how to install Funtoo on ZFS (rootfs). This tutorial is meant to be an "overlay" over the [[Funtoo_Linux_Installation|Regular Funtoo Installation]]. Follow the normal installation and only use this guide for steps 2, 3, and 8.
+
=== Description ===
 +
irssi is a small command line IRC client based on ncurses. It's a great thing to use when you SSH into a server, or just simply for your main IRC client.  
  
=== Introduction to ZFS ===
+
=== Installation ===
 +
The install of irssi is pretty straight forward. There are not many USE flags, but one that is worth looking at is the {{c|SSL}} flag. This enables you to use SSL when connecting to servers.
 +
{{console|body=
 +
###i## echo "net-irc/irssi ssl" >> /etc/portage/package.use
 +
###i## emerge irssi
 +
}}
 +
=== Using irssi ===
 +
Using irssi initially can be a little intimidating if you're not used to command line programs. To first start irssi, you just simply run:
 +
{{console|body=
 +
$ ##i##irssi
 +
}}
 +
There are flags you can pass to the command line while starting irssi, such as:
 +
{{console|body=
 +
$ ##i##irssi -n mynick -c irc.freenode.org
 +
}}
 +
This would connect you to Freenode with the nick 'mynick'. Or alternatively you can just run the {{c|irssi}} command and connect via SSL if you need to:
 +
{{file|body=
 +
/connect -ssl irc.freenode.org
 +
}}
 +
This will automatically connect you over port 6697.
  
Since ZFS is a new technology for Linux, it can be helpful to understand some of its benefits, particularly in comparison to BTRFS, another popular next-generation Linux filesystem:
+
When you have connected to the server of your choice, you can join a channel simply by:
 +
{{file|body=
 +
/j #funtoo
 +
}}
 +
If you want to leave any channel you've entered you can use the {{c|part}} command:
 +
{{file|body=
 +
/part #funtoo reasons...
 +
}}
 +
There are a few ways of navigating through your channels, you can use {{c|alt+<nowiki>{1-9}{q-p}</nowiki>}}, or alternatively you can use the {{c|window}} command that is in irssi:
 +
{{file|body=
 +
/window 1
 +
/window 2
 +
/window 3
 +
}}
 +
For as many channels you are apart of.
  
* On Linux, the ZFS code can be updated independently of the kernel to obtain the latest fixes. btrfs is exclusive to Linux and you need to build the latest kernel sources to get the latest fixes.
+
When you're ready to leave, you can simply type in:
 +
{{file|body=
 +
/exit
 +
}}
 +
Which will close out connections to the IRC networks you've joined, and take you back to your console window.
 +
=== Themes and scripts ===
 +
==== Scripts ====
 +
There are a few things you can do to make irssi look a little bit better and add some cool features. There are a few plugins that are pretty useful, such as {{c|fnotify.pl}} which is a script that utilizes {{f|libnotify}} to send you popup notifications for when your nick is pinged or you are sent a private message.  
  
* ZFS is supported on multiple platforms. The platforms with the best support are Solaris, FreeBSD and Linux. Other platforms with varying degrees of support are NetBSD, Mac OS X and Windows. btrfs is exclusive to Linux.
+
{{file|name=fnotify.pl|lang=perl|desc=fnotify.pl|body=
 +
# todo: grap topic changes
  
* ZFS has the Adaptive Replacement Cache replacement algorithm while btrfs uses the Linux kernel's Last Recently Used replacement algorithm. The former often has an overwhelmingly superior hit rate, which means fewer disk accesses.
+
use strict;
 +
use vars qw($VERSION %IRSSI);
  
* ZFS has the ZFS Intent Log and SLOG devices, which accelerates small synchronous write performance.
+
use Irssi;
 +
$VERSION = '0.0.3';
 +
%IRSSI = (
 +
authors    => 'Thorsten Leemhuis',
 +
contact    => 'fedora@leemhuis.info',
 +
name        => 'fnotify',
 +
description => 'Write a notification to a file that shows who is talking to you in which channel.',
 +
url        => 'http://www.leemhuis.info/files/fnotify/',
 +
license    => 'GNU General Public License',
 +
changed    => '$Date: 2007-01-13 12:00:00 +0100 (Sat, 13 Jan 2007) $'
 +
);
  
* ZFS handles internal fragmentation gracefully, such that you can fill it until 100%. Internal fragmentation in btrfs can make btrfs think it is full at 10%. Btrfs has no automatic rebalancing code, so it requires a manual rebalance to correct it.
+
#--------------------------------------------------------------------
 +
# In parts based on knotify.pl 0.1.1 by Hugo Haas
 +
# http://larve.net/people/hugo/2005/01/knotify.pl
 +
# which is based on osd.pl 0.3.3 by Jeroen Coekaerts, Koenraad Heijlen
 +
# http://www.irssi.org/scripts/scripts/osd.pl
 +
#
 +
# Other parts based on notify.pl from Luke Macken
 +
# http://fedora.feedjack.org/user/918/
 +
#
 +
#--------------------------------------------------------------------
  
* ZFS has raidz, which is like RAID 5/6 (or a hypothetical RAID 7 that supports 3 parity disks), except it does not suffer from the RAID write hole issue thanks to its use of CoW and a variable stripe size. btrfs gained integrated RAID 5/6 functionality in Linux 3.9. However, its implementation uses a stripe cache that can only partially mitigate the effect of the RAID write hole.
+
#--------------------------------------------------------------------
 +
# Private message parsing
 +
#--------------------------------------------------------------------
  
* ZFS send/receive implementation supports incremental update when doing backups. btrfs' send/receive implementation requires sending the entire snapshot.
+
sub priv_msg {
 
+
my ($server,$msg,$nick,$address,$target) = @_;
* ZFS supports data deduplication, which is a memory hog and only works well for specialized workloads. btrfs has no equivalent.
+
filewrite($nick." " .$msg );
 
+
* ZFS datasets have a hierarchical namespace while btrfs subvolumes have a flat namespace.
+
 
+
* ZFS has the ability to create virtual block devices called zvols in its namespace. btrfs has no equivalent and must rely on the loop device for this functionality, which is cumbersome.
+
 
+
The only area where btrfs is ahead of ZFS is in the area of small file
+
efficiency. btrfs supports a feature called block suballocation, which
+
enables it to store small files far more efficiently than ZFS. It is
+
possible to use another filesystem (e.g. reiserfs) on top of a ZFS zvol
+
to obtain similar benefits (with arguably better data integrity) when
+
dealing with many small files (e.g. the portage tree).
+
 
+
For a quick tour of ZFS and have a big picture of its common operations you can consult the page [[ZFS Fun]].
+
 
+
=== Disclaimers ===
+
 
+
{{fancywarning|This guide is a work in progress. Expect some quirks.}}
+
{{fancyimportant|'''Since ZFS was really designed for 64 bit systems, we are only recommending and supporting 64 bit platforms and installations. We will not be supporting 32 bit platforms'''!}}
+
 
+
== Video Tutorial ==
+
 
+
As a companion to the installation instructions below, a YouTube video tutorial is now available:
+
 
+
{{#widget:YouTube|id=SWyThdxNoP8|width=640|height=360}}
+
 
+
== Downloading the ISO (With ZFS) ==
+
In order for us to install Funtoo on ZFS, you will need an environment that already provides the ZFS tools. Therefore we will download a customized version of System Rescue CD with ZFS included.
+
 
+
<pre>
+
Name: sysresccd-4.0.1_zfs_0.6.2.iso  (545 MB)
+
Release Date: 2014-02-25
+
md5sum 01f4e6929247d54db77ab7be4d156d85
+
</pre>
+
 
+
 
+
'''[http://ftp.osuosl.org/pub/funtoo/distfiles/sysresccd/ Download System Rescue CD with ZFS]'''<br />
+
 
+
== Creating a bootable USB from ISO (From a Linux Environment) ==
+
After you download the iso, you can do the following steps to create a bootable USB:
+
 
+
<console>
+
Make a temporary directory
+
# ##i##mkdir /tmp/loop
+
 
+
Mount the iso
+
# ##i##mount -o ro,loop /root/sysresccd-4.0.1_zfs_0.6.2.iso /tmp/loop
+
 
+
Run the usb installer
+
# ##i##/tmp/loop/usb_inst.sh
+
</console>
+
 
+
That should be all you need to do to get your flash drive working.
+
 
+
== Booting the ISO ==
+
 
+
{{fancywarning|'''When booting into the ISO, Make sure that you select the "Alternate 64 bit kernel (altker64)". The ZFS modules have been built specifically for this kernel rather than the standard kernel. If you select a different kernel, you will get a fail to load module stack error message.'''}}
+
 
+
== Creating partitions ==
+
There are two ways to partition your disk: You can use your entire drive and let ZFS automatically partition it for you, or you can do it manually.
+
 
+
We will be showing you how to partition it '''manually''' because if you partition it manually you get to create your own layout, you get to have your own separate /boot partition (Which is nice since not every bootloader supports booting from ZFS pools), and you get to boot into RAID10, RAID5 (RAIDZ) pools and any other layouts due to you having a separate /boot partition.
+
 
+
==== gdisk (GPT Style) ====
+
 
+
'''A Fresh Start''':
+
 
+
First lets make sure that the disk is completely wiped from any previous disk labels and partitions.
+
We will also assume that <tt>/dev/sda</tt> is the target drive.<br />
+
 
+
<console>
+
# ##i##sgdisk -Z /dev/sda
+
</console>
+
 
+
{{fancywarning|This is a destructive operation and the program will not ask you for confirmation! Make sure you really don't want anything on this disk.}}
+
 
+
Now that we have a clean drive, we will create the new layout.
+
 
+
First open up the application:
+
 
+
<console>
+
# ##i##gdisk /dev/sda
+
</console>
+
 
+
'''Create Partition 1''' (boot):
+
<console>
+
Command: ##i##n ↵
+
Partition Number: ##i##↵
+
First sector: ##i##↵
+
Last sector: ##i##+250M ↵
+
Hex Code: ##i##↵
+
</console>
+
 
+
'''Create Partition 2''' (BIOS Boot Partition):
+
<console>Command: ##i##n ↵
+
Partition Number: ##i##↵
+
First sector: ##i##↵
+
Last sector: ##i##+32M ↵
+
Hex Code: ##i##EF02 ↵
+
</console>
+
 
+
'''Create Partition 3''' (ZFS):
+
<console>Command: ##i##n ↵
+
Partition Number: ##i##↵
+
First sector: ##i##↵
+
Last sector: ##i##↵
+
Hex Code: ##i##bf00 ↵
+
 
+
Command: ##i##p ↵
+
 
+
Number  Start (sector)    End (sector)  Size      Code  Name
+
  1            2048          514047  250.0 MiB  8300  Linux filesystem
+
  2          514048          579583  32.0 MiB    EF02  BIOS boot partition
+
  3          579584      1953525134  931.2 GiB  BF00  Solaris root
+
 
+
Command: ##i##w ↵
+
</console>
+
 
+
 
+
=== Format your /boot partition ===
+
 
+
<console>
+
# ##i##mkfs.ext2 -m 1 /dev/sda1
+
</console>
+
 
+
=== Encryption (Optional) ===
+
If you want encryption, then create your encrypted vault(s) now by doing the following:
+
 
+
<console>
+
# ##i##cryptsetup luksFormat /dev/sda3
+
# ##i##cryptsetup luksOpen /dev/sda3 vault_1
+
</console>
+
 
+
{{fancywarning|On some machines, a combination of ZFS and LUKS has caused instability and system crashes.}}
+
 
+
=== Create the zpool ===
+
We will first create the pool. The pool will be named `tank` and the disk will be aligned to 4096 (using ashift=12)
+
<console># ##i##zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo tank /dev/sda3</console>
+
 
+
{{fancyimportant|If you are using encrypted root, change '''/dev/sda3 to /dev/mapper/vault_1'''.}}
+
 
+
{{fancynote| If you have a previous pool that you would like to import, you can do a: '''zpool import -f -R /mnt/funtoo <pool_name>'''.}}
+
 
+
=== Create the zfs datasets ===
+
We will now create some datasets. For this installation, we will create a small but future proof amount of datasets. We will have a dataset for the OS (/), and your swap. We will also show you how to create some optional datasets: <tt>/home</tt>, <tt>/var</tt>, <tt>/usr/src</tt>, and <tt>/usr/portage</tt>.
+
 
+
<console>
+
Create some empty containers for organization purposes, and make the dataset that will hold /
+
# ##i##zfs create -p tank/funtoo
+
# ##i##zfs create -o mountpoint=/ tank/funtoo/root
+
 
+
Optional, but recommended datasets: /home
+
# ##i##zfs create -o mountpoint=/home tank/funtoo/home
+
 
+
Optional datasets: /usr/src, /usr/portage/{distfiles,packages}
+
# ##i##zfs create -o mountpoint=/usr/src tank/funtoo/src
+
# ##i##zfs create -o mountpoint=/usr/portage -o compression=off tank/funtoo/portage
+
# ##i##zfs create -o mountpoint=/usr/portage/distfiles tank/funtoo/portage/distfiles
+
# ##i##zfs create -o mountpoint=/usr/portage/packages tank/funtoo/portage/packages
+
</console>
+
 
+
=== Create your swap zvol ===
+
For modern machines that have greater than 4 GB of RAM, A swap size of 2G should be enough. However if your machine doesn't have a lot of RAM, the rule of thumb is either 2x the RAM or RAM + 1 GB.
+
 
+
For this tutorial we will assume that it is a newer machine and make a 2 GB swap.
+
 
+
<console>
+
# ##i##zfs create -o sync=always -o primarycache=metadata -o secondarycache=none -o volblocksize=4K -V 2G tank/swap
+
</console>
+
 
+
=== Format your swap zvol ===
+
<console>
+
# ##i##mkswap -f /dev/zvol/tank/swap
+
# ##i##swapon /dev/zvol/tank/swap
+
</console>
+
 
+
Now we will continue to install funtoo.
+
 
+
== Installing Funtoo ==
+
 
+
=== Pre-Chroot ===
+
 
+
<console>
+
Go into the directory that you will chroot into
+
# ##i##cd /mnt/funtoo
+
 
+
Make a boot folder and mount your boot drive
+
# ##i##mkdir boot
+
# ##i##mount /dev/sda1 boot
+
</console>
+
 
+
[[Funtoo_Linux_Installation|Now download and extract the Funtoo stage3 ...]]
+
 
+
Once you've extracted the stage3, do a few more preparations and chroot into your new funtoo environment:
+
 
+
<console>
+
Bind the kernel related directories
+
# ##i##mount -t proc none proc
+
# ##i##mount --rbind /dev dev
+
# ##i##mount --rbind /sys sys
+
 
+
Copy network settings
+
# ##i##cp -f /etc/resolv.conf etc
+
 
+
Make the zfs folder in 'etc' and copy your zpool.cache
+
# ##i##mkdir etc/zfs
+
# ##i##cp /etc/zfs/zpool.cache etc/zfs
+
 
+
Chroot into Funtoo
+
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l
+
</console>
+
 
+
=== In Chroot ===
+
 
+
<console>
+
Create a symbolic link to your mountpoints
+
# ##i##ln -sf /proc/mounts /etc/mtab
+
 
+
Sync your tree
+
# ##i##emerge --sync
+
</console>
+
 
+
=== Add filesystems to /etc/fstab ===
+
 
+
Before we continue to compile and or install our kernel in the next step, we will edit the <tt>/etc/fstab</tt> file because if we decide to install our kernel through portage, portage will need to know where our <tt>/boot</tt> is, so that it can place the files in there.
+
 
+
Edit <tt>/etc/fstab</tt>:
+
 
+
<pre>
+
# <fs>                  <mountpoint>    <type>          <opts>          <dump/pass>
+
 
+
/dev/sda1              /boot          ext2            defaults        0 2
+
/dev/zvol/tank/swap    none            swap            sw              0 0
+
</pre>
+
 
+
== Kernel Configuration ==
+
To speed up this step, you can install a pre-configured/compiled kernel called '''bliss-kernel'''. This kernel already has the correct configurations for ZFS and a variety of other scenarios. It's a vanilla kernel from kernel.org without any external patches.
+
 
+
To install {{Package|sys-kernel/bliss-kernel}} type the following:
+
 
+
<console>
+
# ##i##emerge bliss-kernel
+
</console>
+
 
+
Now make sure that your <tt>/usr/src/linux symlink</tt> is pointing to this kernel by typing the following:
+
 
+
<console>
+
# ##i##eselect kernel list
+
Available kernel symlink targets:
+
[1]  linux-3.12.13-KS.02 *
+
</console>
+
 
+
You should see a star next to the version you installed. In this case it was 3.12.13-KS.02. If it's not set, you can type '''eselect kernel set #'''.
+
 
+
== Installing the ZFS userspace tools and kernel modules ==
+
Emerge {{Package|sys-fs/zfs}}. This package will bring in {{Package|sys-kernel/spl}}, and {{Package|sys-fs/zfs-kmod}} as its dependencies:
+
 
+
<console>
+
# ##i##emerge zfs
+
</console>
+
 
+
Check to make sure that the zfs tools are working. The <code>zpool.cache</code> file that you copied before should be displayed.
+
 
+
<console>
+
# ##i##zpool status
+
# ##i##zfs list
+
</console>
+
 
+
If everything worked, continue.
+
 
+
== Create the initramfs ==
+
There are two ways to do this, you can use "genkernel" or "bliss-initramfs". Both will be shown.
+
 
+
=== genkernel ===
+
Install genkernel and run it:
+
<console>
+
# ##i##emerge genkernel
+
 
+
You only need to add --luks if you used encryption
+
# ##i##genkernel --zfs --luks initramfs
+
</console>
+
 
+
=== Bliss Initramfs Creator ===
+
If you are encrypting your drives, then add the "luks" use flag to your package.use before emerging:
+
 
+
<console>
+
# ##i##echo "sys-kernel/bliss-initramfs luks" >> /etc/portage/package.use
+
</console>
+
 
+
Now install the program and run it:
+
<console>
+
# ##i##emerge bliss-initramfs
+
 
+
You can either run it without any parameters to get an interactive menu
+
or you can pass the parameters directly. 1 = zfs, 6 = encrypted zfs, and the kernel name.
+
# ##i##bliss-initramfs 1 3.12.13-KS.02
+
</console>
+
 
+
=== Moving into the correct location ===
+
Place the file that was generated by the above applications into either your /boot folder (If you are using boot-update) or into your /boot/kernels/3.12.13-KS.02 folder (If you are using bliss-boot). For bliss-boot, the file needs to be called 'initrd' rather than 'initrd-3.12.13-KS.02'.
+
 
+
==== boot-update ====
+
<console>
+
# ##i##mv initrd-3.12.13-KS.02 /boot
+
</console>
+
 
+
==== bliss-boot ====
+
<console>
+
# ##i##mv initrd-3.12.13-KS.02 /boot/kernels/3.12.13-KS.02/initrd
+
</console>
+
 
+
== Installing & Configuring the Bootloader ==
+
 
+
=== GRUB 2 (Optional if you are using another bootloader) ===
+
<console>
+
# ##i##emerge grub
+
</console>
+
 
+
You can check that grub is version 2.00 by typing the following command:
+
 
+
<console>
+
# ##i##grub-install --version
+
grub-install (GRUB) 2.00
+
</console>
+
 
+
Now install grub to the drive itself (not a partition):
+
<console>
+
# ##i##grub-install /dev/sda
+
</console>
+
 
+
You should receive the following message:
+
 
+
<console>
+
Installation finished. No error reported.
+
</console>
+
 
+
You should now see some a grub directory with some files inside your /boot folder:
+
 
+
<console>
+
# ##i##ls -l /boot/grub
+
total 2520
+
-rw-r--r-- 1 root root    1024 Jan  4 16:09 grubenv
+
drwxr-xr-x 2 root root    8192 Jan 12 14:29 i386-pc
+
drwxr-xr-x 2 root root    4096 Jan 12 14:28 locale
+
-rw-r--r-- 1 root root 2555597 Feb  4 11:50 unifont.pf2
+
</console>
+
 
+
=== Extlinux (Optional if you are using another bootloader) ===
+
To install extlinux, you can follow the guide here: [[Extlinux|Link to Extlinux Guide]].
+
 
+
=== LILO (Optional if you are using another bootloader) ===
+
To install lilo you can type the following:
+
 
+
<console>
+
# ##i##emerge lilo
+
</console>
+
 
+
=== boot-update ===
+
boot-update comes as a dependency of grub2, so if you already installed grub, it's already on your system!
+
 
+
==== Genkernel ====
+
If your using genkernel you must add 'real_root=ZFS=<root>' and 'dozfs' to your params.
+
Example entry for <tt>/etc/boot.conf</tt>:
+
 
+
<pre>
+
"Funtoo ZFS" {
+
        kernel vmlinuz[-v]
+
        initrd initramfs-genkernel-x86_64[-v]
+
        params real_root=ZFS=tank/funtoo/root
+
        params += dozfs=force
+
        # Also add 'params += crypt_root=/dev/sda3' if you used encryption
+
        # Adjust the above setting to your system if needed
+
 
+
        # You should also add 'root=none' to your params (not 'params +=') if you plan to use it along with boot-update
+
        # If root variable will not be set, boot-update will fail to generate boot.conf
+
        # This is right for <=sys-boot/boot-update-1.6.11 on 16.08.2014 date
+
 
}
 
}
</pre>
 
  
==== Bliss Initramfs Creator ====
+
#--------------------------------------------------------------------
If you used Bliss Initramfs Creator then all you need to do is add 'root=<root>' to your params.
+
# Printing hilight's
Example entry for <tt>/etc/boot.conf</tt>:
+
#--------------------------------------------------------------------
  
<pre>
+
sub hilight {
"Funtoo ZFS" {
+
    my ($dest, $text, $stripped) = @_;
        kernel vmlinuz[-v]
+
    if ($dest->{level} & MSGLEVEL_HILIGHT) {
        initrd initrd[-v]
+
filewrite($dest->{target}. " " .$stripped );
        params root=tank/funtoo/root quiet
+
    }
        # If you have an encrypted device with a regular passphrase,
+
        # you can add the following line
+
        params += enc_root=/dev/sda3 enc_type=pass
+
 
}
 
}
</pre>
 
  
After editing /etc/boot.conf, you just need to run boot-update to update grub.cfg
+
#--------------------------------------------------------------------
 +
# The actual printing
 +
#--------------------------------------------------------------------
  
<console>
+
sub filewrite {
###i## boot-update
+
my ($text) = @_;
</console>
+
# FIXME: there is probably a better way to get the irssi-dir...
 
+
        open(FILE,">>$ENV{HOME}/.irssi/fnotify");
=== bliss-boot ===
+
print FILE $text . "\n";
This is a new program that is designed to generate a simple, human-readable/editable, configuration file for a variety of bootloaders. It currently supports grub2, extlinux, and lilo.
+
        close (FILE);
 
+
You can install it via the following command:
+
<console>
+
# ##i##emerge bliss-boot
+
</console>
+
 
+
==== Bootloader Configuration ====
+
In order to generate our bootloader configuration file, we will first configure bliss-boot so that it knows what we want. The 'bliss-boot' configuration file is located in '''/etc/bliss-boot/conf.py'''. Open that file and make sure that the following variables are set appropriately:
+
 
+
<pre>
+
# This should be set to the bootloader you installed earlier: (grub2, extlinux, and lilo are the available options)
+
bootloader = "grub2"
+
 
+
# This should be set to the kernel you installed earlier
+
default = "3.12.13-KS.02"  
+
</pre>
+
 
+
Scroll all the way down until you find 'kernels'. You will need to add the kernels and the options
+
you want for these kernels here. Below are a few configuration options depending if you are using
+
'''bliss-initramfs''' or '''genkernel'''.
+
 
+
===== Genkernel =====
+
 
+
<pre>
+
kernel = {
+
    '3.12.13-KS.02' : 'real_root=ZFS=tank/funtoo/root dozfs=force quiet',
+
 
}
 
}
</pre>
 
 
'''If you are using encryption you can add the crypt_root option:'''
 
 
<pre>
 
kernel = {
 
    '3.12.13-KS.02' : 'real_root=ZFS=tank/funtoo/root dozfs=force crypt_root=/dev/sda3 quiet',
 
}
 
</pre>
 
 
===== Bliss Initramfs Creator =====
 
<pre>
 
kernel = {
 
    '3.12.13-KS.02' : 'root=tank/funtoo/root quiet',
 
}
 
</pre>
 
 
'''If you are using encryption then you would let the initramfs know:'''
 
 
#"What type of encryption authentication you want to use? ('''enc_type=''')
 
::* pass = will ask for passphrase directly
 
::* key = a plain unencrypted key file
 
::* key_gpg = an encrypted key file
 
#"Where is the encrypted drive?" ('''enc_root=''')
 
#"Where is the root pool after it has been decrypted?" ('''root=''')
 
 
<pre>
 
kernel = {
 
    '3.12.13-KS.02' : 'root=tank/funtoo/root enc_root=/dev/sda3 enc_type=pass quiet',
 
}
 
</pre>
 
 
==== Generate the configuration ====
 
Now that we have configure our '''/etc/bliss-boot/conf.py''' file, we can generate our config. Simply run the following command:
 
 
<console>
 
# ##i##bliss-boot
 
</console>
 
 
This will generate a configuration file for the bootloader you specified previously in your current directory. You can check your config file before hand to make sure it doesn't have any errors. Simply open either: grub.cfg, extlinux.conf, or lilo.conf.
 
 
Once you have checked it for errors, place this file in the correct directory:
 
 
* grub2 = /boot/grub/
 
* extlinux = /boot/extlinux/
 
* lilo = /etc/lilo.conf
 
 
=== LILO (Optional if you are using another bootloader) ===
 
Now that bliss-boot generated the lilo.conf file, move that config file to its appropriate location
 
and install lilo to the MBR:
 
 
<console>
 
# ##i##mv lilo.conf /etc
 
# ##i##lilo
 
 
You should see the following:
 
 
Warning: LBA32 addressing assumed
 
Added Funtoo + *
 
One warning was issued
 
</console>
 
 
== Final configuration ==
 
=== Add the zfs tools to openrc ===
 
<console># ##i##rc-update add zfs boot</console>
 
 
=== Clean up and reboot ===
 
We are almost done, we are just going to clean up, '''set our root password''', and unmount whatever we mounted and get out.
 
 
<console>
 
Delete the stage3 tarball that you downloaded earlier so it doesn't take up space.
 
# ##i##cd /
 
# ##i##rm stage3-latest.tar.xz
 
 
Set your root password
 
# ##i##passwd
 
>> Enter your password, you won't see what you are writing (for security reasons), but it is there!
 
 
Get out of the chroot environment
 
# ##i##exit
 
 
Unmount all the kernel filesystem stuff and boot (if you have a separate /boot)
 
# ##i##umount -l proc dev sys boot
 
 
Turn off the swap
 
# ##i##swapoff /dev/zvol/tank/swap
 
 
Export the zpool
 
# ##i##cd /
 
# ##i##zpool export tank
 
 
Reboot
 
# ##i##reboot
 
</console>
 
 
{{fancyimportant|'''Don't forget to set your root password as stated above before exiting chroot and rebooting. If you don't set the root password, you won't be able to log into your new system.'''}}
 
 
and that should be enough to get your system to boot on ZFS.
 
 
== After reboot ==
 
 
=== Forgot to reset password? ===
 
==== System Rescue CD ====
 
If you aren't using bliss-initramfs, then you can reboot back into your sysresccd and reset through there by mounting your drive, chrooting, and then typing passwd.
 
 
Example:
 
<console>
 
# ##i##zpool import -f -R /mnt/funtoo tank
 
# ##i##chroot /mnt/funtoo bash -l
 
# ##i##passwd
 
# ##i##exit
 
# ##i##zpool export -f tank
 
# ##i##reboot
 
</console>
 
 
==== Using bliss-initramfs ====
 
If you forgot to reset your password and are using '''bliss-initramfs''', you can add the '''su''' option to your bootloader parameters and the initramfs will throw you into the rootfs of your drive. In there you can run 'passwd' and then type 'exit'. Once you type 'exit', the initramfs will continue to boot your system as normal.
 
 
=== Create initial ZFS Snapshot ===
 
Continue to set up anything you need in terms of /etc configurations. Once you have everything the way you like it, take a snapshot of your system. You will be using this snapshot to revert back to this state if anything ever happens to your system down the road. The snapshots are cheap, and almost instant.
 
 
To take the snapshot of your system, type the following:
 
<console># ##i##zfs snapshot -r tank@install</console>
 
 
To see if your snapshot was taken, type:
 
<console># ##i##zfs list -t snapshot</console>
 
 
If your machine ever fails and you need to get back to this state, just type (This will only revert your / dataset while keeping the rest of your data intact):
 
<console># ##i##zfs rollback tank/funtoo/root@install</console>
 
 
{{fancyimportant|'''For a detailed overview, presentation of ZFS' capabilities, as well as usage examples, please refer to the [[ZFS_Fun|ZFS Fun]] page.'''}}
 
 
== Troubleshooting ==
 
 
=== Starting from scratch ===
 
If your installation has gotten screwed up for whatever reason and you need a fresh restart, you can do the following from sysresccd to start fresh:
 
  
<console>
+
Irssi::signal_add_last("message private", "priv_msg");
Destroy the pool and any snapshots and datasets it has
+
Irssi::signal_add_last("print text", "hilight");
# ##i##zpool destroy -R -f tank
+
  
This deletes the files from /dev/sda1 so that even after we zap, recreating the drive in the exact sector
+
#- end
position and size will not give us access to the old files in this partition.
+
}}
# ##i##mkfs.ext2 /dev/sda1
+
Another very useful script is for colored nicks, to better tell people apart. Which can be found at [http://scripts.irssi.org irssi scripts] called {{f|nickcolor.pl}}. 
# ##i##sgdisk -Z /dev/sda
+
</console>
+
  
Now start the guide again :).
+
When you have the scripts you would like you would put them into {{f|~/.irssi/scripts}} and set a link to {{f|~/.irssi/scripts/autorun}}.
 +
{{console|body=
 +
$ ##i##wget -O ~/.irssi/scripts/nickcolor.pl http://scripts.irssi.org/scripts/nickcolor.pl
 +
$ ##i##cd ~/.irssi/scripts/autorun
 +
$ ##i##ln -s ~/.irssi/scripts/nickcolor.pl .
 +
$ ##i##ln -s ~/.irssi/scripts/fnotify.pl .
 +
}}
 +
You can do this for as many scripts as you've chosen to use. They will automatically load when you start irssi. You can also manually load scripts:
 +
{{file|body=
 +
/load ~/.irssi/scripts/fnotify.pl
 +
Irssi: Loaded script fnotify
 +
}}
 +
Whichever works best for you is what you should do.
 +
==== Themes ====
 +
You can choose from many themes on the [http://irssi.org/themes irssi themes] page if you don't like the default look of it. Once you've chosen the them you like, you can simply put it in your {{f|~/.irssi/}} directory and when you run just run:
 +
{{file|body=
 +
/set theme mycooltheme
 +
}}
 +
And there you have it, the theme you have chosen is now there.
 +
=== Conclusion ===
 +
irssi is a great IRC client, and really helpful if you spend a lot of time in a terminal emulator or on a server.  
  
[[Category:HOWTO]]
+
== External Resources ==
[[Category:Filesystems]]
+
[http://www.irssi.org/documentation Further documentation]
[[Category:Featured]]
+
[[Category:Install]]
+
  
__NOTITLE__
+
{{EbuildFooter}}
 +
[[Category:IRC]]

Revision as of 07:49, January 22, 2015

net-irc/irssi


Source Repository:Repository:Gentoo Portage Tree

http://www.irssi.org/

Summary: A modular textUI IRC client with IPv6 support.

Use Flags

proxy
Adds support for a loadable IRC proxy module

News

Drobbins

IP Space Migration Continues

All Funtoo user containers in the 8.28 IP space will be moving into our new IP space (172.97) over the next few days. If you have DNS set up -- be sure to watch your container and update to the new IP! container.host.funtoo.org DNS will be updated after the move.
2015-08-27 by Drobbins
Drobbins

Funtoo Hosting IP Move

Funtoo user containers with IPs in the 72.18.x.x range will be gradually migrating to new IP addresses this week. If you have DNS entries for your containers, please be aware that your DNS will need to be updated.
2015-08-11 by Drobbins
Drobbins

New ARM Stages

New ARM Stages, built with a new toolchain, are now hitting mirrors. Existing ARM users should re-install using these stages (dated Aug 3, 2015 or later,) rather than upgrade using emerge.
2015-08-06 by Drobbins
More...

Irssi

Tip

We welcome improvements to this page. To edit this page, Create a Funtoo account. Then log in and then click here to edit this page. See our editing guidelines to becoming a wiki-editing pro.


Description

irssi is a small command line IRC client based on ncurses. It's a great thing to use when you SSH into a server, or just simply for your main IRC client.

Installation

The install of irssi is pretty straight forward. There are not many USE flags, but one that is worth looking at is the SSL flag. This enables you to use SSL when connecting to servers.

# echo "net-irc/irssi ssl" >> /etc/portage/package.use
# emerge irssi

Using irssi

Using irssi initially can be a little intimidating if you're not used to command line programs. To first start irssi, you just simply run:

$ irssi

There are flags you can pass to the command line while starting irssi, such as:

$ irssi -n mynick -c irc.freenode.org

This would connect you to Freenode with the nick 'mynick'. Or alternatively you can just run the irssi command and connect via SSL if you need to:

/connect -ssl irc.freenode.org

This will automatically connect you over port 6697.

When you have connected to the server of your choice, you can join a channel simply by:

/j #funtoo

If you want to leave any channel you've entered you can use the part command:

/part #funtoo reasons...

There are a few ways of navigating through your channels, you can use alt+{1-9}{q-p}, or alternatively you can use the window command that is in irssi:

/window 1
/window 2
/window 3

For as many channels you are apart of.

When you're ready to leave, you can simply type in:

/exit

Which will close out connections to the IRC networks you've joined, and take you back to your console window.

Themes and scripts

Scripts

There are a few things you can do to make irssi look a little bit better and add some cool features. There are a few plugins that are pretty useful, such as fnotify.pl which is a script that utilizes libnotify to send you popup notifications for when your nick is pinged or you are sent a private message.

fnotify.pl (perl source code) - fnotify.pl
# todo: grap topic changes
 
use strict;
use vars qw($VERSION %IRSSI);
 
use Irssi;
$VERSION = '0.0.3';
%IRSSI = (
	authors     => 'Thorsten Leemhuis',
	contact     => 'fedora@leemhuis.info',
	name        => 'fnotify',
	description => 'Write a notification to a file that shows who is talking to you in which channel.',
	url         => 'http://www.leemhuis.info/files/fnotify/',
	license     => 'GNU General Public License',
	changed     => '$Date: 2007-01-13 12:00:00 +0100 (Sat, 13 Jan 2007) $'
);
 
#--------------------------------------------------------------------
# In parts based on knotify.pl 0.1.1 by Hugo Haas
# http://larve.net/people/hugo/2005/01/knotify.pl
# which is based on osd.pl 0.3.3 by Jeroen Coekaerts, Koenraad Heijlen
# http://www.irssi.org/scripts/scripts/osd.pl
#
# Other parts based on notify.pl from Luke Macken
# http://fedora.feedjack.org/user/918/
#
#--------------------------------------------------------------------
 
#--------------------------------------------------------------------
# Private message parsing
#--------------------------------------------------------------------
 
sub priv_msg {
	my ($server,$msg,$nick,$address,$target) = @_;
	filewrite($nick." " .$msg );
}
 
#--------------------------------------------------------------------
# Printing hilight's
#--------------------------------------------------------------------
 
sub hilight {
    my ($dest, $text, $stripped) = @_;
    if ($dest->{level} & MSGLEVEL_HILIGHT) {
	filewrite($dest->{target}. " " .$stripped );
    }
}
 
#--------------------------------------------------------------------
# The actual printing
#--------------------------------------------------------------------
 
sub filewrite {
	my ($text) = @_;
	# FIXME: there is probably a better way to get the irssi-dir...
        open(FILE,">>$ENV{HOME}/.irssi/fnotify");
	print FILE $text . "\n";
        close (FILE);
}
 
Irssi::signal_add_last("message private", "priv_msg");
Irssi::signal_add_last("print text", "hilight");
 
#- end

Another very useful script is for colored nicks, to better tell people apart. Which can be found at irssi scripts called nickcolor.pl.

When you have the scripts you would like you would put them into ~/.irssi/scripts and set a link to ~/.irssi/scripts/autorun.

$ wget -O ~/.irssi/scripts/nickcolor.pl http://scripts.irssi.org/scripts/nickcolor.pl
$ cd ~/.irssi/scripts/autorun
$ ln -s ~/.irssi/scripts/nickcolor.pl .
$ ln -s ~/.irssi/scripts/fnotify.pl .

You can do this for as many scripts as you've chosen to use. They will automatically load when you start irssi. You can also manually load scripts:

/load ~/.irssi/scripts/fnotify.pl
Irssi: Loaded script fnotify

Whichever works best for you is what you should do.

Themes

You can choose from many themes on the irssi themes page if you don't like the default look of it. Once you've chosen the them you like, you can simply put it in your ~/.irssi/ directory and when you run just run:

/set theme mycooltheme

And there you have it, the theme you have chosen is now there.

Conclusion

irssi is a great IRC client, and really helpful if you spend a lot of time in a terminal emulator or on a server.

External Resources

Further documentation