Showing posts with label rsync reference. Show all posts
Showing posts with label rsync reference. Show all posts

Monday, 19 October 2015

Raspberry Pi Starter Guide


The Raspberry Pi is an amazing little computer that fits perfectly in the palm of your hand, yet it’s able to pack enough power to run a VPN, your home media center and a lot more. Before you can do anything good, however, you will need to configure the Raspberry Pi and install an operating system. Here’s a simple guide on how to do that.

A Raspberry Pi Defined

It’s a very capable mini computer that is small enough to fit in your pocket. For about $30-45, you will get a caseless computer with an HDMI and analog composite video output. You can add up to two different USB devices and connect it to the internet via ethernet. The Raspberry Pi is inexpensive and powerful thus allowing you to create a home media center, VPN server or internet radio on the cheap. That said, set up equipment and a lot of other parts are required to get it ready.

What You Will Need

The Raspberry Pi may be a small computer on its own, but you will still need a couple of other things to make it work.

A Raspberry Pi

m An HDMI, or a video-capable connecting to a monitor or a television.
In this guide we will be working with an HDMI capable and a monitor because a monitor offers built-in sound and a better resolution.

A 4GB SD card Class 4+ and a card reader
A majority of SD cards will work, but some SD cards are not compatible and will therefore cause some issues. .

A USB mouse and keyboard: Any standard USB mouse or keyboard will do the job. Wireless peripherals will also work, but you will have to unplug them and then plug them back in after the Raspberry Pi boots.

An ethernet cable: Any ethernet cable will do. You will only need this cable to connect to your network,thus gain internet access.

A quality, USB power supply that can be able to provide at least
700 milliAmps at 5V.



A 3.5mm audio cable:

You will only need this if you are using analog video and you want to connect your Raspberry Pi to external speakers or internal ones on your monitor or television.
You can find most of these items pretty much anywhere, i.e online shops, stores, e.t.c

How to Setup Your Raspberry Pi

You can use your Raspberry Pi for a couple of different things–some that may require special operating systems, but first off, it’s a good idea to understand the Pi by installing Raspbian, which is a Raspberry Pi-focused version of Linux.

1. Prepare Your SD Card

The first thing you need to do is to prepare your SD card for the Pi. This will involve formatting the SD card properly and putting Raspbian, which is the standard Raspberry Pi operating system, on it. The steps will vary depending on the operating system, but in this article, we are going to discuss how to setup the Pi on Windows.

2. Setup on Windows

1. Download the most recent version of Raspbian and then unzip the .img file inside. (It’s about 500MB thus it may take a some time to download.)

2. Download Win32 Disk Imager and then unzip the application (it’s a .exe file) inside.

3. Insert your microSD card into the Windows PC using a card reader.

4. Open the Win32 Disk Imager.exe, you just downloaded by double-clicking on it. If you’re running on Windows 7, 8 or 10 right click on the application and select “Run as Administrator” instead.

5. If the SD card is not automatically detected by the application, just click on the dropdown menu at the top right and choose it from the list.

6. In the img file section of your application, click on the little folder icon and then choose the Raspbian .img file that you just downloaded.

7. Click on the Write button and wait for the Win32 Disk Imager to do its thing. When it completes, you can now safely eject the SD card and insert it into your Raspberry Pi. You are ready to go!!

To Know More About Raspberry pi Reference Visit us…

Source : Click Here

Tuesday, 6 October 2015

Groovy Commands Reference

The groovy shell has a quite number of different commands, which provide rich access to the groovy shell’s environment.

Commands all have a shortcut (which is something like \h) and a name . The commands may also have some predefined system aliases. The users may also create their own aliases.



1.4.1. Recognized Commands

help

To display the list of commands or the help text for specific command.

The Groovy Command List

groovy:000> : i.e help

The Available commands:

 :help      (:h ) Will display this help message
  ?          (:? ) An alias to: ->help
  :exit      (:x ) Exiting the shell
  :quit      (:q ) An alias to: :exit
  import     (:i ) Importing a class into the namespace
  :display   (:d ) To display the current buffer
  :clear     (:c ) Clearing the buffer and resetting the prompt counter.
  :show      (:S ) Show’s variables, imports or classes
  :inspect   (:n ) Inspecting a variable or the last result with the GUI object browser
  :purge     (:p ) Purging variables, classes, imports or preferences
  :edit      (:e ) Editing the current buffer
  :load      (:l ) Loading a file or URL into the buffer
  .          (:. ) An alias to: ->load
  :save      (:s ) Saving the current buffer to a file
  :record    (:r ) Recording the current session to a file
  :history   (:H ) Displaying, managing and recalling edit-line history
  :alias     (:a ) Create an alias
  :set       (:= ) List or set preferences
  :register  (:rc) Registering a new command with the shell
  :doc       (:D ) This Opens a browser window displaying the specific doc for the argument

For help on a specific command just type:

    :help <command>

Help for a Command

While in the interactive groovy shell, you can ask for help for a specific command to get more details about it's function or syntax.

To Know More About Groovy language Reference Visit us..




Tuesday, 29 September 2015

GIT COMMANDS REFERENCE




A list of some basic Git commands that will get you going with Git.


Git task
Notes
Git commands
Telling Git who you are
Make sure you configure the author name and email address to be used with your commits.
Take Note that Git strips some characters (for example trailing periods) from user.name.
git config --global user.name "Ian Smonerl"
git config --global user.email ian@example.com
Creating a new local repository

git init
Checking out a repository
Create a working copy of the local repository:
git clone / path/to/repository
For a remote server, just use:
git clone username@host:/path/to/repository
Adding files
Adding one or a couple of files to staging (index):
git add <filename>

git add *
Committing
Commit changes to head :
git commit -m "The Commit message"
Committing any files that you've added with git add, and also commit any files you've changed since then:
git commit -a
Push
Send the changes to the master branch of your remote repository:
git push origin master
Status
Listing the files you have changed and those you still need to commit or add.
git status
Connecting to a remote repository
If you have not connected your local repository to the remote server, add the server so as to be able to push to it:
git remote add origin <server>
List all the currently configured remote repositories:
git remote -v
Branches
Creating a new branch and switch to it:
git checkout -b <branchname>
Switch from one branch to another:
git checkout <branchname>
Listing all the branches in your repository, and also tell you what branch you are currently in:
git branch
Deleting the feature branch:
git branch -d <branchname>
Pushing the branch to the remote repository, so other people can use it:
git push origin <branchname>
Pushing all branches to your remote repository:
git push --all origin
Deleting a branch on your remote repository:
git push origin :<branchname>
Update from your remote repository
Fetching and merging changes on the remote server to your working directory:
git pull
To merge different branches into your active branch:
git merge <branchname>
Viewing all the merge conflicts:
Viewing the conflicts against the base file:
Previewing changes, before merging:
git diff
git diff --base <filename>
git diff <sourcebranch> <targetbranch>
After you have manually resolved any kind of conflicts, you mark the changed file:
git add <filename>
Tags
You can use tagging to mark a significant changeset, e.g a release:
git tag 1.0.0 <commitID>
Commit Id is the leading characters of the changeset ID, up to 10, but they must be unique. Get the ID using:
git log
Pushing all tags to remote repository:
git push --tags origin
Undoing local changes
In case you end up messing up, you can replace the changes in your work tree with the last content in head:
Changes already added to the indexing, as well as new files, that will be kept.
git checkout -- <filename>
Instead, so as to drop all your local changes and commits, fetching the latest history from the server and point your local master branch at it, do this:
git fetch origin

git reset --hard origin/master
Search
Searching the working directory for foo():
git grep "foo()"

To Know more About This Content Git Command Reference Visit us..