Monday, June 21, 2010

why do we safely remove hardware

When you plug in a USB drive, you give your PC free reign to write and read data from it; some of which is cached.

Caching occurs by not writing information immediately to the USB device, and instead keeping it in your PC's memory (RAM). If you were to yank the USB drive out of your PC before this infromation is written, or while its being written, you'll end up with a corrupted file.

However, Windows automatically disables caching on USB devices, unless you specifically say that you want it enabled. For the most part you don't have to click the 'Safely Remove Hardware' button, if you aren't writting or reading anything from the device.

Its there simply as an extra level of security preventing you from destroying your own files.

Doing so causes the files to close "gracefully", preserving data, pointers and file size indicators. When writing to disk the computer doesn't always "flush" a buffer and only part of the data may have been written. Using the proper procedure will assure that the data and pointers are in good shape.

References:
http://wiki.answers.com/Q/Why_click_safely_remove_hardware_icon_on_USB_flash_drive

Sunday, June 20, 2010

Keyboad shortcuts

Ctrl-H: show hidden files
Ctrl-N: new window
Ctrl-Shift-N: create new folder
Alt-Home : jump to home folder
Alt-Enter : file / folder properties
Alt-F1 : launch application menu
Alt-F2 : launch "run application" dialogue
Ctrl-Alt - Right/Left arrow : move to the next virtual desktop
Ctrl-Alt-Shift - Right/Left arrow : take current window to the next virtual desktop
Ctrl-Alt-D: minimize all windows, and gives focus to the Desktop
Alt-Tab: switch between windows. When you use these shortcut keys, a list of windows that you can select is displayed. Release the keys to select a window.
Ctrl-Alt-Tab: switch the focus between the panels and the desktop. When you use these shortcut keys, a list of items that you can select is displayed. Release the keys to select an item.
CTRL + ALT + Enter: for toggling Full screen mode in rdesktop
ALT+ENTER: Show file properties without right-clicking the mouse



2.How to create a custom hotkey to launch whatever application you want in GNOME:
As an example, we will set a lock-screen shortcut.
Open "gconf-editor" as the user as you're logged in in GNOME (typing gconf-editor in the terminal or "Run Application").
Go to apps > metacity > keybinding_commands
Here we have a list of twelve slots for commands. Double click on e.g. "run_command_1"
In Key Value Type in the name of the application or command you want to launch (e.g. gnome-screensaver-command --lock).
Go to apps > metacity > global_keybindings
Double click on e.g. "run_command_1"
Change the key value to whatever key combination you like (e.g. L).Press "Ok".


3.How to create/change GNOME shortcuts:

Click on System > Preferences > Keyboard Shortcuts
Click the action in the list and press Enter.
Press the new key or key combination you want to assign to the action. (To clear a shortcut, press the Backspace key)

References:
http://www.linuxquestions.org/questions/linux-newbie-8/most-used-shortcuts-in-gnome-and-nautilus-640504/

Saturday, June 12, 2010

Linux installation methods

Adobe Reader 9 for Unix (Linux/Solaris-x86) can be installed using various different methods, depending on the distribution of the OS you are running.

There are 5 installer formats for Adobe Reader available via yum/apt-get OR via FTP from Adobe’s FTP server:
  1. BIN installer
  2. RPM installer
  3. DEB installer
  4. TARball installer
  5. PKG installer
Installation using yum and apt-get/aptitude is convenient and updates happen automagically so we recommend doing that. We’ve previously described how to install using yum and using apt-get.

Installer formats explained

Here’s a brief description and the merits/demerits of each installer format, to help you choose the format that best suits your needs/constraints:
  1. BIN installer: The BIN installer can be used to install Adobe Reader on any location that is writable by the current user.
    The advantages of using this installer are:
    • Smallest size. This installer has the smallest size amongst all installers for Adobe Reader on Unix platforms. (It is approximately 29% smaller than the second smallest installer.)
    • Install anywhere. This installer can be used to install Adobe Reader on any location that is writable by the user performing the installation.
    The BIN installers are available for both Linux and Solaris-x86 platforms.
  2. RPM installer: The RPM installer may be used to install Adobe Reader on RPM-based Linux distributions such as RedHat, Fedora, CentOS etc.
    The advantages of using this installer are:
    • Native installation. The package can be managed using RPM manager, which provides a one-stop place for managing all RPM-based packages.
    • Managing updates. RPM allows fully-automated, in-place upgrades of the package.
    • Package querying and verification.
    However, unlike the BIN installer, the RPM installer can only be installed by a privileged user. Once installed, it can used by any user on the system. The RPM installer can be used only on RPM-based Linux distributions.
  3. DEB installer: The DEB installer may be used to install Adobe Reader in Debian-based distributions such as Debian, Ubuntu, Linspire, KNOPPIX etc.
    It has exactly the same advantages and limitations as RPM installer. The DEB installer can only be used on Debian-based Linux distributions.
  4. TARball installer: The TARball installer is provided for legacy reasons.
    It has the following advantage:
    • Install anywhere. Just like the BIN installer, the TARball installer can be used to install Adobe Reader on any location that is writable by the user performing the installation.
    The TARball installer is available for both Linux and Solaris-x86 platforms.
  5. PKG installer: The PKG installer is native installer for Solaris and uses the ‘pkg’ installation mechanism, which is similar to RPM/DEB on Linux.
    It shares its advantages and shortcomings with the RPM and DEB installers. The PKG installer can be used only on Solaris-x86 platform.
Installation methods

Once you’ve chosen the installer format that suits your needs best, here’s how you can install Adobe Reader using it:
  1. Download the latest installer (9.1.1, at the time of writing this post) from here and save it to you HOME directory.
  2. Now, open a terminal (gnome-terminal / xterm / konsole /… ) and go to your home directory (which is where you downloaded the installer in step 1.)
BIN installer:
  • Now, mark the installer file as executable for the current user, that’s you:
    • On Linux:
    • On Solaris-x86:
  • Launch the installer:
    • On Linux:
    • On Solaris-x86:
  • Now follow the steps and answer the questions asked to complete the installation.
RPM installer:
  • Start the installation using the RPM installer (remember this would need to be done as root):
  • Alternatively, you can open the Desktop folder in nautilus installer and double-click the AdbeRdr9.1.1-1_i486linux_enu.rpm file to automatically start the installation. This method also requires you to be a privileged (or root) user.
DEB installer:
  • Start the installation using the DEB installer (remember this would need to be done as root):
  • Alternatively, you can open the Desktop folder in nautilus and double-click the AdbeRdr9.1.1-1_i386linux_enu.deb file to automatically start the installation. This method also requires you to be a privileged (or root) user.
TARball installer:
  • Extract the contents of the compressed tarball:
    • On Linux:
    • On Solaris-x86:
  • Launch the installation script:
  • Now follow the steps and answer the questions asked to complete the installation.
PKG installer:
  • Extract the contents of the compressed PKG installer:
We hope this will act as a definitive guide to install Adobe Reader using the various installer formats offered. In case you run into any issues related to Adobe Reader for Unix, please let us know at our forum.

References:
http://blogs.adobe.com/acroread/2009/05/installer_formats_for_adobe_re.html