public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Christian Könitzer" <chkab@gmx.ch>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Writing a bash script or thinking about it anyway.
Date: Tue, 22 Dec 2009 12:20:46 +0100	[thread overview]
Message-ID: <4B30AB8E.7000903@gmx.ch> (raw)
In-Reply-To: <6155bd0861f00c277e49c2b0b8028c17@localhost>

I agree with Jesús but recommend you to use rsync for backup purpose.
Simple google for rsync backup script.
And this link explains why:
http://www.sanitarium.net/golug/rsync_backups.html

There are a lot backup scripts using rsync out there and most of them 
are written in bash so it's anyway a good idea to learn a bit bash ;)


Am 22.12.2009 11:34, schrieb Jesús Guerrero:
> On Mon, 21 Dec 2009 21:22:05 -0600, Dale<rdalek1967@gmail.com>  wrote:
>    
>> Hi folks,
>>
>> Me again.  I'm thinking about writing a bash script that backs up my
>> /home directory.  I found a guide but before I read all that stuff and
>> muddy up the waters, is this thing current and will it work fine with
>> the bash Gentoo uses?  Links to a even better guide would be good too.
>> The guide I found is here:
>>
>> http://tldp.org/LDP/abs/html/
>>      
> The advanced bash scripting guide will be equally valid nowadays as it was
> when it was first written. A few minor edges have changed in bash in the
> latest times, but you are unlikely to get touched by these unless you are
> using some rare feature. After all, bash is compatible with the original
> bourne shell to a big extent, and that part of its behavior never changes.
>
> If you truly want to learn bash, I say go for it and come back when/if you
> have some problem.
>
>    



  reply	other threads:[~2009-12-22 11:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22  3:22 [gentoo-user] Writing a bash script or thinking about it anyway Dale
2009-12-22  3:53 ` Francisco Ares
2009-12-22  4:16   ` Dale
2009-12-22  4:32     ` Francisco Ares
2009-12-22  5:02 ` Neil Walker
2009-12-22  5:09   ` Dale
2009-12-23  1:45     ` Francisco Ares
2009-12-25 23:21       ` Dale
2009-12-22 10:34 ` Jesús Guerrero
2009-12-22 11:20   ` Christian Könitzer [this message]
2009-12-22 12:11     ` Jesús Guerrero
2009-12-22 14:21       ` Christian Könitzer
2009-12-22 14:51         ` Alan McKinnon
2009-12-22 15:36           ` Jesús Guerrero
2009-12-22 19:01             ` Stroller
2009-12-23  6:58               ` Dirk Heinrichs
2009-12-22 18:56   ` Stroller
2009-12-22 23:25   ` Willie Wong
2009-12-22 11:16 ` Stroller
2009-12-22 23:30   ` Willie Wong
2009-12-22 15:08 ` Ward Poelmans
2009-12-22 15:39   ` Neil Bothwick
2009-12-22 15:57     ` Ward Poelmans
2009-12-23  0:33 ` [gentoo-user] " »Q«
2009-12-25 23:19   ` Dale
2009-12-27 21:09     ` »Q«
2009-12-23 12:29 ` [gentoo-user] " Alex Schuster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B30AB8E.7000903@gmx.ch \
    --to=chkab@gmx.ch \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox