mdadm –examine /dev/sd* | grep -E “(^\/dev|UUID)”
mdadm –examine /dev/sd* | grep -E “(^\/dev|UUID)”
mdadm –create /dev/md1–metadata=0.9 –level=1 –raid-disks=2 missing /dev/sdb2
mount -t proc none /mnt/sysimage/proc
mount -o bind /dev /mnt/sysimage/dev
mount -t sysfs sys /mnt/sysimage/sys
where /mnt/sysimage/ location of chrooted sysimage
Get imap c-client: cd /usr/local wget ftp://ftp.cac.washington.edu/imap/c-client.tar.Z tar xvfz c-client.tar.Z cd imap-2007f
Compile imap c-client: make lr5 PASSWDTYPE=std SSLTYPE=unix.nopwd IP6=4 echo "set disable-plaintext nil" > /etc/c-client.cf mkdir /usr/local/imap-2007f mkdir /usr/local/imap-2007f/include/ mkdir /usr/local/imap-2007f/lib/ chmod -R 077 /usr/local/imap-2007f rm -rf /usr/local/imap-2007f/include/* rm -rf /usr/local/imap-2007f/lib/* cp imapd/imapd /usr/sbin/ cp c-client/*.h /usr/local/imap-2007f/include/ cp c-client/*.c /usr/local/imap-2007f/lib/ cp c-client/c-client.a /usr/local/imap-2007f/lib/libc-client.a
Configuring php custom settings: mkdir -p custom/ap2 cp configure/ap2/configure.php5 custom/ap2 edit your custom/ap2/configure.php5 --with-imap=/usr/local/imap-2007f \ --with-imap-ssl \
FCrDNS, or Forward Confirmed reverse DNS, is when an IP address has forward and reverse DNS entries that match each other. For FCrDNS verification, first a reverse DNS lookup is done to get a list of PTR. Then for each domain name mentioned in the PTR records, a regular DNS lookup is done to see if any of the A records match the original IP address. If there is a forward DNS lookup that confirms one of the names given by the reverse DNS lookup, then the FCrDNS check passes.
IP address 1.2.3.4 resolves to mail.domain.com.
Host name mail.domain.com resolves to IP addresses 1.2.3.4 and 5.6.7.8.
Thus, reverse DNS for IP address 1.2.3.4 is forward confirmed.
You can check it there: http://multirbl.valli.org/fcrdns-test/
lpstat -a
then you can found more information: lpoptions -d printer_name
nmap -p 515,9100 192.168.0.1-255 -oG – | grep open
then you can add your printer, if you are using KDE:
ALT+F2: kcmshell4 kcm_printer_manager
sed -r “s:\x1B\[[0-9;]*[mK]::g”‘
or with perl:
perl -pe ‘s/\x1b.*?[mGKH]//g’
ansible webservers -m yum -a "name=httpd state=installed"
cat /etc/issue
CentOS release 4.9 (Final)
Kernel \r on an \m
NOTICE: Support for CentOS 4 ends on Feb 29th, 2012
Don’t forget. 🙂
How to fix?
yum install python-simplejson
but not python-json
if you will install python-json you still get errors like:
“msg”: “Traceback (most recent call last):\n File \”/root/.ansible/tmp/ansible-1381145464.17-139681524282507/command\”, line 1137, in ?\n main()\n File \”/root/.ansible/tmp/ansible-1381145464.17-139681524282507/command\”, line 155, in main\n changed = True\n File \”/root/.ansible/tmp/ansible-1381145464.17-139681524282507/command\”, line 911, in exit_json\n print self.jsonify(kwargs)\n File \”/root/.ansible/tmp/ansible-1381145464.17-139681524282507/command\”, line 901, in jsonify\n return json.dumps(data)\nAttributeError: ‘module’ object has no attribute ‘dumps’\n”,
sfdisk -d /dev/sda > partitions.txt
1.BIOS(Basic Input/Output System)
2.MBR(Master Boot Record)
3.LILO or GRUB
LILO:-LInux LOader
GRUB:-GRand Unified Bootloader
4.Kernel
5.init
6.Run Levels
1.BIOS:
i.When we power on BIOS performs a Power-On Self-Test (POST) for all of the different hardware components in the system to make sure everything is working properly
ii.Also it checks for whether the computer is being started from an off position (cold boot) or from a restart (warm boot) is stored at this location.
iii.Retrieves information from CMOS (Complementary Metal-Oxide Semiconductor) a battery operated memory chip on the motherboard that stores time, date, and critical system information.
iv.Once BIOS sees everything is fine it will begin searching for an operating system Boot Sector on a valid master boot sector on all available drives like hard disks,CD-ROM drive etc.
v.Once BIOS finds a valid MBR it will give the instructions to boot and executes the first 512-byte boot sector that is the first sector (“Sector 0″) of a partitioned data storage device such as hard disk or CD-ROM etc .
2.MBR
i. Normally we use multi-level boot loader.Here MBR means I am referencing to DOS MBR.
ii.Afer BIOS executes a valid DOS MBR,the DOS MBR will search for a valid primary partition marked as bootable on the hard disk.
iii.If MBR finds a valid bootable primary partition then it executes the first 512-bytes of that partition which is second level MBR.
iv. In linux we have two types of the above mentioned second level MBR known as LILO and GRUB
3.LILO
i.LILO is a linux boot loader which is too big to fit into single sector of 512-bytes.
ii.So it is divided into two parts :an installer and a runtime module.
iii.The installer module places the runtime module on MBR.The runtime module has the info about all operating systems installed.
iv.When the runtime module is executed it selects the operating system to load and transfers the control to kernel.
v.LILO does not understand filesystems and boot images to be loaded and treats them as raw disk offsets
GRUB
i.GRUB MBR consists of 446 bytes of primary bootloader code and 64 bytes of the partition table.
ii.GRUB locates all the operating systems installed and gives a GUI to select the operating system need to be loaded.
iii.Once user selects the operating system GRUB will pass control to the karnel of that operating system.
4.Kernel
i.Once GRUB or LILO transfers the control to Kernel,the Kernels does the following tasks
5.Init
i.The kernel, once it is loaded, finds init in sbin(/sbin/init) and executes it.
ii.Hence the first process which is started in linux is init process.
iii.This init process reads /etc/inittab file and sets the path, starts swapping, checks the file systems, and so on.
iv.It runs all the boot scripts(/etc/rc.d/*,/etc/rc.boot/*)
v.starts the system on specified run level in the file /etc/inittab
6.Runlevel
i.There are 7 run levels in which the linux OS runs and different run levels serves for different purpose.The descriptions are
given below.
ii.We can set in which runlevel we want to run our operating system by defining it on /etc/inittab file.
Now as per our setting in /etc/inittab the Operating System the operating system boots up and finishes the bootup process.
Below are given some few important differences about LILO and GRUB
LILO | GRUB |
LILO has no interactive command interface | GRUB has interactive command interface |
LILO does not support booting from a network | GRUB does support booting from a network |
If you change your LILO config file, you have to rewrite the LILO stage one boot loader to the MBR | GRUB automatically detects any change in config file and auto loads the OS |
LILO supports only linux operating system | GRUB supports large number of OS |
"ayy
this will store the line in buffer a
"ap
this will put the contents of buffer a
at the cursor
There are many variations on this
"a5yy
this will store the 5 lines in buffer a
yy
will yank the current line without deleting it
dd
will delete the current line
p
will ‘put’ a line grabbed by either of the previous methods
OR just YP
or Yp
or yyp
Copy and paste 10 lines:
y10yp