Lets make a killer backup tool

[viking60]

Yupp Rolf was joking, he is the guru so he knows this stuff best.
But I might point out that you need to install git from the repo. I might be stating the obvious, but it cannot hurt.....

Code: Select all

sudo apt-get install git

After that you can simply copy and paste the code in your ~/ et voila; berserk_stuff will be created - in other words, just follow the advice of the guru

[viking60]

I have even made a wiki now please do tell me if I have been lying to much
https://github.com/viking60/berserk_stuff/wiki/Backup

[rolf]

Well, I see the wiki and that is good.

I thought to add this to my local copy and, new to me, guessed to use one of your commands of your initial git post but something is wrong.

Code: Select all

[rolf@localhost ~]$ cd info/bjoernvold/git/
[rolf@localhost git]$ ls
berserk_stuff/
[rolf@localhost git]$ git remote add upstream https://github.com/viking60/berserk_stuff.git
fatal: Not a git repository (or any parent up to mount parent )
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[rolf@localhost git]$

I have not done any configuring or registering, just used your 'git clone' command to get berserk_stuff/.....

[viking60]

Hmm I take it the cloning went well. and then the upstream command does not work.... I am not sure that everybody can use the enter the upstream command but I thought so.
It looks like you are in the correct path when you enter the command. You could try sending a pull request (hit button on the project page).

[rolf]

I issue the command in the parent directory of berserk_stuff

Maybe the git commands are different on Mandrva 2011, in case you are in a different distro.

I also tried in berserk_stuff/ some commands, like git ls-tree and git seems a little less po'ed but not altogether happy:

Code: Select all

[rolf@localhost git]$ git ls-tree -d
fatal: Not a git repository (or any parent up to mount parent )
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[rolf@localhost git]$ cd berserk_stuff/
[rolf@localhost berserk_stuff (master)]$ git ls-tree -d
usage: git ls-tree [<options>] <tree-ish> [<path>...]

    -d                    only show trees
    -r                    recurse into subtrees
    -t                    show trees when recursing
    -z                    terminate entries with NUL byte
    -l, --long            include object size
    --name-only           list only filenames
    --name-status         list only filenames
    --full-name           use full path names
    --full-tree           list entire tree; not just current directory (implies --full-name)
    --abbrev[=<n>]        use <n> digits to display SHA-1s

[rolf@localhost berserk_stuff (master)]$

[viking60]

I am puzzled. I was going to suggest git fetch upstream but I managed to unwatch my project so now it is gone - I think. Going into fixing mode......
Fixed!
You have tried being in the berserk_stuff directory? And besides that I am drawing blanks right now...

[viking60]

OK here is my Mandriva entry:

Code: Select all

.:[ thomas@thomas-pc : 10:13:55 : ~/berserk_stuff ]:.
:( git remote add uppstream https://github.com/viking60/berserk_stuff.git
.:[ thomas@thomas-pc : 10:19:37 : ~/berserk_stuff ]:.
:) git fetch uppstream
From https://github.com/viking60/berserk_stuff
 * [new branch]      master     -> uppstream/master
.:[ thomas@thomas-pc : 10:19:56 : ~/berserk_stuff ]:.
:)


The ":)" are smileys I get similar errors like you if the

Code: Select all

git remote add uppstream https://github.com/viking60/berserk_stuff.git

is not ran first.
And I do it from within berserk_stuff.

In your case maybe this would help:

Code: Select all

git config --global branch.autosetupmerge true

http://nuclearsquid.com/writings/git-tr ... workflows/
You should also be able to do a

Code: Select all

gitk

in berserk_stuff and get a GUI overview of what is going on.

[viking60]

I have added the guided backup script (the fool prof one ) to the repo. It does the same as backup.sh but it prompts you for the paths and makes the first run easier.
After it is run you can edit viking.backup and ex.txt with whatever you want to backup and exclude.

[rolf]

I have not yet done any configuration steps and it appears my error came from not running commands in the "master" directory

Code: Select all

[rolf@localhost git]$ cd berserk_stuff/
[rolf@localhost berserk_stuff (master)]$ git remote add uppstream https://github.com/viking60/berserk_stuff.git
[rolf@localhost berserk_stuff (master)]$ git fetch uppstream
remote: Counting objects: 18, done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 12 (delta 2), reused 12 (delta 2)
Unpacking objects: 100% (12/12), done.
From https://github.com/viking60/berserk_stuff
 * [new branch]      master     -> uppstream/master
[rolf@localhost berserk_stuff (master)]$ ls
backup/  README*
[rolf@localhost berserk_stuff (master)]$ ls -R
.:
backup/  README*

./backup:
backup.sh*  ex.txt*  viking.backup*
[rolf@localhost berserk_stuff (master)]$

Thanks for all your work on this

[dedanna1029]

In that usage, "configure" is the first step of building the binary from the source and I was just alluding to that process.

So, to understand you correctly, as regular user, it is as you have here. Then, once done, in this case, it's already "there", and ready to use?

Sorry on the joke - that shows how little I know about git or the commands for it (I wasn't kidding, hence why I'm trying to understand it now), so it blew right over my head.

[rolf]

So, to understand you correctly, as regular user, it is as you have here. Then, once done, in this case, it's already "there", and ready to use?

Right. There are several issues. One, git is a way of distributing stuff. To get the stuff, first, as Viking60 pointed out, you have to have git installed on your system. Then, you can use git as a downloader, to download from the repository to your machine. Like other downloaders, you have to have write permissions in the directory where you run the command. In that case, run as regular user in one of your directories under /home will do it. Many of us have data partitions where we have write permission as regular user, that's how we set it up.

What Viking put in his git repository is berserk_stuff/ with files and directories under that. Running the git command he gave will download that directory recursively, like rsync, like making a local mirror of the repo. Getting source code to compile is like that. Once it's on your machine, you can do whatever you want. Viking is talking about other functions of git as a developer tool, such as uploading changes to his stuff or new stuff. That's something new to me but I know that is how software development is done, even kernel development. There are other "distributed version control system"s and I'm not up-to-date on which one Linus is using atm. In that usage, there is another permissions issue as only authorized contributors will be able to upload to the git repository.

The next hurdle for us was running the commands to, essentially, add Viking's git repository as a source for git to fetch changes:

Code: Select all

[rolf@localhost berserk_stuff (master)]$ git remote add uppstream https://github.com/viking60/berserk_stuff.git

As we discovered, this has to be run in the top level directory of the local repository. I see git has control over the shell to change the prompt when I am inside the repository, [rolf@localhost berserk_stuff (master)]$, kinda cool.

[viking60]

I have not yet done any configuration steps and it appears my error came from not running commands in the "master" directory

Code: Select all

[rolf@localhost git]$ cd berserk_stuff/
[rolf@localhost berserk_stuff (master)]$ git remote add uppstream https://github.com/viking60/berserk_stuff.git
[rolf@localhost berserk_stuff (master)]$ git fetch uppstream
remote: Counting objects: 18, done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 12 (delta 2), reused 12 (delta 2)
Unpacking objects: 100% (12/12), done.
From https://github.com/viking60/berserk_stuff
 * [new branch]      master     -> uppstream/master
[rolf@localhost berserk_stuff (master)]$ ls
backup/  README*
[rolf@localhost berserk_stuff (master)]$ ls -R
.:
backup/  README*

./backup:
backup.sh*  ex.txt*  viking.backup*
[rolf@localhost berserk_stuff (master)]$

Thanks for all your work on this

That is great feeling I am sure! I am still learning myself (come to think of it - who isn't) Now we have this repo to play with.

@dedanna
git is a magician that interacts with the "sky" (github.com) all you have to do on your end is to install it.
..and then you can test it by typing

Code: Select all

git config --global core.editor "nano -w"

This makes nano the default editor for git, and if you do not get any error messages git works!
Now you are ready to enter the clone command:

Code: Select all

git clone https://github.com/viking60/berserk_stuff.git

PS And Rolf has added a post above and that does explain things way better - as usual
And Linus is using Git; he made Git....