From: "Paul Leung" <dragonpath@hotmail.com>
To: ggibson@blank.jbstamping.com, rhdb@sources.redhat.com
Subject: Re: RHDB 2.1 ISO not working
Date: Fri, 10 Jan 2003 06:19:00 -0000 [thread overview]
Message-ID: <F44JuwKm0n3fG5tBEIe0002b80d@hotmail.com> (raw)
That's very interesting. How do you think mounting it manually is different
than having it set as auto in fstab? How does it help?
>From: "George T. Gibson" <ggibson@blank.jbstamping.com>
>To: rhdb@sources.redhat.com
>Subject: Re: RHDB 2.1 ISO not working
>Date: 09 Jan 2003 08:58:36 -0500
>MIME-Version: 1.0
>Received: from sources.redhat.com ([209.249.29.67]) by
>mc4-f19.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Thu, 9 Jan
>2003 05:58:47 -0800
>Received: (qmail 11085 invoked by alias); 9 Jan 2003 13:58:42 -0000
>Received: (qmail 11003 invoked from network); 9 Jan 2003 13:58:37 -0000
>Received: from unknown (HELO blank.jbstamping.com) (207.166.197.106) by
>209.249.29.67 with SMTP; 9 Jan 2003 13:58:37 -0000
>Received: from localhost (localhost.localdomain [127.0.0.1])by
>blank.jbstamping.com (8.12.5/8.12.5) with ESMTP id h09Dwaxp026729for
><rhdb@sources.redhat.com>; Thu, 9 Jan 2003 08:58:37 -0500
>Mailing-List: contact rhdb-help@sources.redhat.com; run by ezmlm
>Precedence: bulk
>List-Unsubscribe:
><mailto:rhdb-unsubscribe-dragonpath=hotmail.com@sources.redhat.com>
>List-Subscribe: <mailto:rhdb-subscribe@sources.redhat.com>
>List-Post: <mailto:rhdb@sources.redhat.com>
>List-Help: <mailto:rhdb-help@sources.redhat.com>,
><http://sources.redhat.com/lists.html#faqs>
>Sender: rhdb-owner@sources.redhat.com
>Delivered-To: mailing list rhdb@sources.redhat.com
>Organization: J.B. Stamping, Inc.
>Message-Id: <1042120716.26674.6.camel@blank.jbstamping.com>
>Return-Path: rhdb-return-42-dragonpath=hotmail.com@sources.redhat.com
>X-OriginalArrivalTime: 09 Jan 2003 13:58:47.0718 (UTC)
>FILETIME=[3B219460:01C2B7E7]
>
>Downloaded and had a little trouble myself but did get it to work.
>
>I have my cdrom mounting "auto" in fstab. When I used 'mount
>/mnt/cdrom' at the command line and tried to run the script I got error
>messages about permissions on the bash script.
>
>When I mounted using 'mount -t iso9660 -o ro /dev/cdrom/ /mnt/cdrom' it
>worked fine.
>
>Hope it helps.
>
>--
>J.B. Stamping, Inc.
>George Gibson
>7413 Associate Ave.
>Cleveland, OH 44144
>216.631.0013 216.631.1327 fax
>gtgibson@jbstamping.com
_________________________________________________________________
The new MSN 8 is here: Try it free* for 2 months
http://join.msn.com/?page=dept/dialup
next reply other threads:[~2003-01-10 6:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 6:19 Paul Leung [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-12 5:48 Paul Leung
2003-01-12 17:40 ` Fernando Nasser
2003-01-13 16:49 ` Patrick Macdonald
2003-01-10 5:43 Paul Leung
2003-01-10 15:24 ` Andrew Overholt
2003-01-09 21:55 Fred New
2003-01-09 13:58 George T. Gibson
2003-01-09 4:33 Paul Leung
2003-01-09 18:19 ` Deepak Bhole
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=F44JuwKm0n3fG5tBEIe0002b80d@hotmail.com \
--to=dragonpath@hotmail.com \
--cc=ggibson@blank.jbstamping.com \
--cc=rhdb@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).