From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} dvdrip permissions error, alternative?
Date: Fri, 13 Oct 2006 07:52:57 -0700 [thread overview]
Message-ID: <49bf44f10610130752m52d4c2b4qb38428348c1f5e81@mail.gmail.com> (raw)
In-Reply-To: <20061013091453.709ef975@hactar.digimed.co.uk>
> > I'm tweaking that script you wrote. Here's what I have:
> >
> > #!/bin/bash
> >
> > echo Enter DVD filename:
> > read FILENAME
> > mount /dev/cdrom
> > TITLE=$(vobcopy -I 2>&1 | awk '/DVD-name:/ {print $3}')
> > vobcopy -m || exit
> > mkisofs -dvd-video -V $TITLE -o $FILENAME $TITLE || exit
> > rm -rf $TITLE
> > umount /dev/cdrom
> >
> > Can you tell me what purpose the "|| exit" portions serve?
>
> '||' is a logical or. When used to chain commands, as in "cmd1 || cmd2"
> it means run cmd1, if that fails run cmd2 (if the first command succeeds
> and returns true, the OR will alsays be true so there's no need to run
> cmd2). All is does here is exit the script if vobcopy or mkisofs return
> an error, because there'd be no point in continuing.
Got it.
> > Also, how
> > can I run the script by typing /path/to/getdvd? I've tried:
> >
> > chmod +x getdvd
>
> That should work, assuming you're i the same directory at getdvd. I keep
> my scripts in ~/bin, with the x bits set, and have ~/bin in $PATH, so I
> don't need to give the path to run them.
Here's what I get:
grant@system5 ~ $ ls -l
-rwxrwxrwx 1 grant grant 386 Oct 12 22:24 getdvd
grant@system5 ~ $ getdvd
-bash: getdvd: command not found
I like the sound of your ~/bin setup. How can I add that to my PATH
permanently? Is it 'export PATH=~/bin' ?
- Grant
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-13 14:57 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 16:57 [gentoo-user] {OT} dvdrip permissions error, alternative? Grant
2006-10-05 17:09 ` Hemmann, Volker Armin
2006-10-05 17:12 ` Meino Christian Cramer
2006-10-05 18:39 ` Mike Williams
2006-10-06 16:59 ` Grant
2006-10-06 17:27 ` Neil Bothwick
2006-10-06 17:50 ` Grant
2006-10-06 18:03 ` Neil Bothwick
2006-10-06 18:34 ` Grant
2006-10-07 8:52 ` Nick Rout
2006-10-07 19:16 ` Boyd Stephen Smith Jr.
2006-10-07 20:43 ` Grant
2006-10-08 5:45 ` Nick Rout
2006-10-06 22:36 ` Boyd Stephen Smith Jr.
2006-10-07 16:56 ` Neil Bothwick
2006-10-07 17:22 ` [gentoo-user] [Even more OT]: " Remy Blank
2006-10-07 17:47 ` darren kirby
2006-10-07 18:43 ` [gentoo-user] " Remy Blank
2006-10-07 18:03 ` [gentoo-user] " Uwe Thiem
2006-10-08 7:56 ` Nick Rout
2006-10-08 17:59 ` Grant
2006-10-09 1:40 ` Nick Rout
2006-10-09 2:01 ` Grant
2006-10-09 9:02 ` Neil Bothwick
2006-10-09 14:55 ` Grant
2006-10-09 15:16 ` Neil Bothwick
2006-10-09 16:42 ` Grant
2006-10-09 18:07 ` Neil Bothwick
2006-10-10 0:08 ` Grant
2006-10-10 7:43 ` Neil Bothwick
2006-10-10 8:28 ` Neil Bothwick
2006-10-10 15:59 ` Grant
2006-10-10 20:53 ` Neil Bothwick
2006-10-11 15:24 ` Grant
2006-10-11 18:12 ` Neil Bothwick
2006-10-12 10:08 ` Paul Stear
2006-10-12 14:26 ` Grant
2006-10-12 17:38 ` Neil Bothwick
2006-10-13 5:55 ` Grant
2006-10-13 8:14 ` Neil Bothwick
2006-10-13 14:52 ` Grant [this message]
2006-10-13 15:03 ` Neil Bothwick
2006-10-13 16:07 ` Grant
2006-10-14 3:39 ` Grant
2006-10-13 8:23 ` Bo Ørsted Andresen
2006-10-13 9:51 ` go moko
2006-10-09 10:50 ` Neil Bothwick
2006-10-06 22:31 ` Boyd Stephen Smith Jr.
2006-10-07 1:54 ` Grant
2006-10-07 4:21 ` Boyd Stephen Smith Jr.
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=49bf44f10610130752m52d4c2b4qb38428348c1f5e81@mail.gmail.com \
--to=emailgrant@gmail.com \
--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