Find command and logical operators

Understanding find command operators

WARNING! The '-or', '-and', and '-not' operator are not available on all versions of find. Usually GNU find supports all options. Refer your local find command man page for more information.

How do I ignore hidden .dot files while searching for files?

find /path/to/dest -type d \( ! -name tmp \) -print

find /path/to/dest -type d \( ! -name tmp \) -o \( ! -name cache \) -print

find /path/to/dest -type d \( ! -name tmp \) -o \( ! -name cache -prune \) -print

find /  \( ! -name tmp \) -o \( ! -name root -prune \)  -name "*.pl" -print

SESSION MANAGEMENT

tmux new -s session_name

creates a new tmux session named session_name

tmux attach -t session_name

attaches to an existing tmux session named session_name

tmux switch -t session_name

switches to an existing session named session_name

tmux list-sessions

lists existing tmux sessions

tmux detach (prefix + d)

detach the currently attached session

WINDOWS

tmux new-window (prefix + c)

create a new window

tmux select-window -t :0-9 (prefix + 0-9)

move to the window based on index

tmux rename-window (prefix + ,)

rename the current window

PANES

tmux split-window (prefix + ")

splits the window into two vertical panes

tmux split-window -h (prefix + %)

splits the window into two horizontal panes

tmux swap-pane -[UDLR] (prefix + { or })

swaps pane with another in the specified direction

tmux select-pane -[UDLR]

selects the next pane in the specified direction

tmux select-pane -t :.+

selects the next pane in numerical order

HELPFUL TMUX COMMANDS

tmux list-keys

lists out every bound key and the tmux command it runs

tmux list-commands

lists out every tmux command and its arguments

tmux info

lists out every session, window, pane, its pid, etc.

tmux source-file ~/.tmux.conf

reloads the current tmux configuration (based on a default tmux config)

MUST-HAVES

# remap prefix to Control + a
set -g prefix C-a
unbind C-b
bind C-a send-prefix

# force a reload of the config file
unbind r
bind r source-file ~/.tmux.conf

# quick pane cycling
unbind ^A
bind ^A select-pane -t :.+

WORKFLOW

Identify & Locate Your Windows Live Mail Store Folder

1. Open Windows Live Mail, Select Tools | Options from Windows Live Mail toolbar. This will display following Options box:
   
   
   
2. From the Options box go to the Advanced Tab then click the Maintenance button as shown below:
   
   
   
   
3. From the Maintenance box, Click the Store Folder button as shown below:
   
   
   
4. Now this will display the following box having store folder location as shown below:
   
   

Introduction

fdisk

[root@racnode1 ~]# fdisk /dev/hdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.


The number of cylinders for this disk is set to 4865.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-4865, default 1): 1
Last cylinder or +size or +sizeM or +sizeK (1-4865, default 4865): 4865

Command (m for help): t
Partition number (1-4): 1
Hex code (type L to list codes): 83

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.

Create ext3 File System

[root@racnode1 ~]# mkfs.ext3 -b 4096 /dev/hdb1
mke2fs 1.27 (8-Mar-2002)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
4889248 inodes, 9769520 blocks
488476 blocks (5.00%) reserved for the super user
First data block=0
299 block groups
32768 blocks per group, 32768 fragments per group
16352 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624

Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.

Mounting the File System

You will first need to create the /db directory before mouting the disk! (e.g. mkdir /db)

LABEL=/                 /                       ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /proc                   proc    defaults        0 0
none                    /dev/shm                tmpfs   defaults        0 0
/dev/hdb1               /db                     ext3    defaults        1 1
/dev/hda2               swap                    swap    defaults        0 0
/dev/cdrom              /mnt/cdrom              iso9660 noauto,owner,kudzu,ro 0 0
/dev/fd0                /mnt/floppy             auto    noauto,owner,kudzu 0 0

[root@racnode1 ~]# mount /db

[root@racnode1 ~]# df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/hda3             37191660  11016692  24285724  32% /
/dev/hda1               101089     12130     83740  13% /boot
none                    515524         0    515524   0% /dev/shm
/dev/hdb1             38464340     32828  36477608   1% /db

If dma is enabled on a controller that is not well supported, these errors can appear. ( I had it on a VIA KT266a with kernel 2.2. Upgrading to kernel 2.4 fixed it beautifully.

If you are sure that the IDE controller is supported, the drive is on its way out. You can run fsck with the badblock option turned on to mark these blocks as bad... As a rule, once these errors start, we throw the disk away(This is a high availability production environment).

If you dont mind that the disk can crash in the near future, make a backup and continue using it, it might work for a long time to come.

If the disk is under guarantee... take it back, it is not worth risking data loss if the drive can be replaced for free.

This is how you hunt for and fix badblocks.

# e2fsck -c /dev/hda1

Make sure that you have a backup, badblock scans can destroy data running with certain switches.

# man badblocks && man e2fsck (And read them carefully)

To turn of dma per drive

# hdparm -d0 /dev/hd[a-d]

To list dma settings

# hdparm -d /dev/hd[a-d]

To turn dma on

# hdparm -d1 /dev/hd[a-d]

Where hd[a-d] is hda, hdb, hdc, hdd.