forget the dot in front of the filename. otherwise no files will be extracted.Querying installed packagesIf you want to know if a package is installed use:yum list "*http*"It will list the Installed Packages and also the Available Packages. Yum list only search for the packages name. Yum search searches also in the description of the package.Installing RPMsyum localinstall xxx.rpm works just like rpm -ivh xxx.rpm but will also solve the dependencies if necessary.Creating RPMsyum install rpm-build make -ymkdir -p /usr/src/lutieri/{BUILD,RPMS,SOURCES,SPECS,SRPMS,tmp}cd /usr/src/lutieri/mkdir samplecd sample/touch first_file second_file keys config_filecd ..tar -cf sample.tar.gz sample/mv sample.tar.gz SOURCES/create a spec file in SPECS: run vim foo.spec -> vim will load a template for you :-Drpmbuild -v -bb SPECS/sample.specORrpmbuild -v -bb --sign SPECS/sample.specthe former example works if you have the rpmmacros set correctly. then the package will be built and signed.Instead of creating all those directories, create the .spec file and run with rpmbuild. it will create all the directory structure in ~/rpmbuild/. then move the .spec to ~/rpmbuild/SPECS and the tar to ~/rpmbuild/SOURCES and run rpmbuild again against the .spec.OR Install rpmdevtools and run rpmdev-setuptree. This will also create the folder structure in the home directoryin the SPEC file , under the sessino %files you should specify every file that this package is responsible for.%files%defattr(-,root,root,-)%dir /root/package%attr(755,root,root) /root/package/script.shInstead of use cp to copy files to a specific location, use install -DSigning a packagegpg-agent --daemongpg2 --gen-keysgpg2 --list-keysgpg2 --export -a lutieri2 > RPM-GPG-KEY-lutieri2su -rpm --import /home/lutieri/RPM-GPG-KEY-lutieri2exitvim ~/.rpmmacros%_signature gpg%_gpg_name lutieri2rpm --addsign rpmbuild/RPMS/i386/lutieri-1.1-0.i386.rpmrpm --resign rpmbuild/RPMS/i386/lutieri-1.1-0.i386.rpmrpm --checksig rpmbuild/RPMS/i386/lutieri-1.1-0.i386.rpmRun man rpm and search for macro.. this will show you what goes inside the .rpmmacros files.all the keys imported into RPM DB are considered packages. take a look:rpm -q gpg-pubkey --qf "%{name} - %{version} - %{release} -> %{summary}\n"gpg-pubkey - c105b9de - 4e0fd3a3 -> gpg(CentOS-6 Key (CentOS 6 Official Signing Key) )gpg-pubkey - 8cee003f - 4f03b71a -> gpg(lutieri )gpg-pubkey - cf7fe955 - 4f03bacf -> gpg(lutieri2 )rpm -qa gpg-pub*gpg-pubkey-cf7fe955-4f03bacfgpg-pubkey-8cee003f-4f03b71agpg-pubkey-c105b9de-4e0fd3a3thus, to remove lutieri2 key. issue:rpm -e gpg-pubkey-cf7fe955-4f03bacfCreate a repository:yum install -y createrepomkdir /opt/myrepomv *.rpm /opt/myrepocreaterepo /opt/myrepovim /etc/yum.repos.d/lutieri.repo[lutieri]Baseurl=file:///opt/myreponame=lutierirepoenabled=1man yum.conf shows you the options that goes in the .repo files.If later on you add new RPMs to the directory run the following to update de metadata:createrepo -update /opt/myrepo --------------------------------------------------Networkon ifcfg-* files, the option NM_CONTROLLED="NO" will not allow network manager to manage this interface Bonding:vim /etc/modprobe.d/bonding.confalias bond0 bondingTo find out what options are necessary in the master interface do the follwingfind /usr/share/doc/kernel-doc* -iname "bond*"less /usr/share/doc/kernel-doc-2.6.32/Documentation/networking/bonding.txtmiimon is required as well as mode. Mode 1=rr, 2=active/passive 3=broadcastMaster:vim /etc/sysconfig/network-scripts/ifcfg-bond0TYPE=EthernetDEVICE=bond0BOOTPROTO=noneIPADDR=1.1.1.1NETMASK=255.255.255.0USERCTL=yesIPV6INIT=noONBOOT=yesBONDING_OPTS="miimon=100 mode=0"Slaves:vim /etc/sysconfig/network-scripts/ifcfg-eth0TYPE=EthernetDEVICE=eth1BOOTPROTO=noneONBOOT=yesMASTER=bond0SLAVE=yesIf you wanna see if the options in BONDING_OPTS were applied, take a look in[root@zeus ~]# cat /sys/class/net/bond0/bonding/miimon100[root@zeus ~]# cat /sys/class/net/bond0/bonding/modebalance-rr 0--------------------------------------------------File Systemspalimpsest it's a graphic utility to manage disks. TIP:fdisk -cul /dev/?d?it lists all disk devices.LUKS - Linux Unified Key Setupmake sure you have the partition unmountFormat the partition to be encrypted:cryptsetup luksFormat /dev/sdb1Open the FS and give it a name:cryptsetup luksOpen /dev/sdb1 hiddenDataFormat it to use:mkfs.ext4 /dev/mapper/hiddenDataUse it:mkdir /mnt/hiddenDatamount /dev/mapper/hiddenData /mnt/hiddenDatatouch /mnt/hiddenData/file1Lock it after use:umount /mnt/hiddenDatacryptsetup luksClose /dev/mapper/hiddenDataMake it the mounting persistent after reboot:vim /etc/crypttabhiddenData /dev/sda2 nonenone means you will have to type the password during boot. any other value is interpreted