I have scratched the first CD in my set to the point where it is mostly
unuseable for installation. I downloaded an image that I am reasonable
certain would be a replacement for the one I ruined. When I try to
extract the image to copy the files and burn a new CD

In article <10n8qd231kbkg46@corp.supernews.com>,
Keith Krehbiel <redsilo@pldi.net> writes:

I have scratched the first CD in my set to the point where it is mostly
unuseable for installation. I downloaded an image that I am reasonable
certain would be a replacement for the one I ruined. When I try to
extract the image to copy the files and burn a new CD


Don't try it that way. Download the image file and burn it straight to
CD-R *AS AN IMAGE FILE* (that is, do *NOT* burn a CD with a single big
file). You can do this directly with cdrecord, or most GUI CD-R tools have
an option to burn a CD-R from an image file. If you need more help on
this, post with information on the CD-R software you're using.

Actually burning a single big file was about the only option I had not

icon but Disk Copy will open it and create an image. The problem is
that all the files and folders in the image are named to ISO standards
rather than something that Linux would understand.

Rod Smith wrote:
In article <10n8qd231kbkg46@corp.supernews.com>,
Keith Krehbiel <redsilo@pldi.net> writes:

I have scratched the first CD in my set to the point where it is mostly
unuseable for installation. I downloaded an image that I am reasonable
certain would be a replacement for the one I ruined. When I try to
extract the image to copy the files and burn a new CD

Don't try it that way. Download the image file and burn it straight to
CD-R *AS AN IMAGE FILE* (that is, do *NOT* burn a CD with a single big
file). You can do this directly with cdrecord, or most GUI CD-R tools have
an option to burn a CD-R from an image file. If you need more help on
this, post with information on the CD-R software you're using.

Actually burning a single big file was about the only option I had not
tried. The file I have downloaded has a garbage title and a generic
icon but Disk Copy will open it and create an image. The problem is
that all the files and folders in the image are named to ISO standards
rather than something that Linux would understand.

I tried just now to create an
image from the file with my burner software (Discribe) and it wouldn't
read the file. Thanks for your suggestion though.

The real filenames
are saved in each directory in a file called TABLE, something or
another.

Seems like there should be some way to reconstruct it.

In article <10nauqnmnkt6g35@corp.supernews.com>,
Keith Krehbiel <redsilo@pldi.net> writes:

Rod Smith wrote:

In article <10n8qd231kbkg46@corp.supernews.com>,
Keith Krehbiel <redsilo@pldi.net> writes:


I have scratched the first CD in my set to the point where it is mostly
unuseable for installation. I downloaded an image that I am reasonable
certain would be a replacement for the one I ruined. When I try to
extract the image to copy the files and burn a new CD

Don't try it that way. Download the image file and burn it straight to
CD-R *AS AN IMAGE FILE* (that is, do *NOT* burn a CD with a single big
file). You can do this directly with cdrecord, or most GUI CD-R tools have
an option to burn a CD-R from an image file. If you need more help on
this, post with information on the CD-R software you're using.


Actually burning a single big file was about the only option I had not
tried. The file I have downloaded has a garbage title and a generic
icon but Disk Copy will open it and create an image. The problem is
that all the files and folders in the image are named to ISO standards
rather than something that Linux would understand.


The CD-R image file is a complete ISO-9660 filesystem in a single file.
The Disk Copy tool just accesses that filesystem the way a Mac normally
does, except from the file rather than from an actual CD-ROM. The
filesystem image is almost certainly ISO-9660 with Rock Ridge extensions,
which means that it *DOES* have long filenames, but they're encoded via
Rock Ridge, which pre-X versions of MacOS can't understand. (Mac disc
images will be either HFS or ISO-9660 plus HFS, so Macs will see HFS long
filenames.) All of this is irrelevant once the CD-R is created correctly,
because what you should do is find a way to burn the image to disc
without adding it in a wrapper filesystem. That is, the usual way to
create a CD-R is to take files from a disk directory, wrap them in an
ISO-9660 filesystem (often plus other options), and write that created
filesystem to the CD-R. What you want to do is to write the file to disc
*WITHOUT* first wrapping it in an ISO-9660 filesystem, because the image
file *IS* an ISO-9660 filesystem.


I tried just now to create an
image from the file with my burner software (Discribe) and it wouldn't
read the file. Thanks for your suggestion though.


I'm afraid I'm not familiar with Discribe, so I can't tell you precisely
how to do what's needed with it, or even if it's possible -- it's
conceivable that Discribe is crippled and lacks the necessary option. Look
for something called "burn from image file," "create CD-R from ISO image,"
or something similar. You don't want to *CREATE* an image file -- you've
already got one. You want to COPY that existing image file to disc.

If Discribe is so crippled that it won't do what you need, you might look
into other software. I'm not familiar with MacOS options, so I can't point
you to specific products, but there's got to be something that'll do the
job. If you've already installed Linux and can access the file from Linux,
just use cdrecord to burn the image file to CD-R from Linux.


The real filenames
are saved in each directory in a file called TABLE, something or
another.


This is a common practice when using certain Unix/Linux CD-R creation
tools. Placing the long filenames in a special files enables users of OSs
that can't read them to figure out what's what. You can and should ignore
this detail, along with everything you see when accessing the file with
Disk Copy, because using Disk Copy as any part of this process is the
wrong approach -- or at the very least, it's the way-too-hard approach.


Seems like there should be some way to reconstruct it.


In theory, yes. Reconstruction is the wrong approach, though; it's like
trying to pick all the toppings off of a pizza to make a sandwich from
them, when a sandwich just like the one you want to make is sitting right
next to the pizza. Only multiply that by a thousandfold. ;-)

CD-R *AS AN IMAGE FILE* (that is, do *NOT* burn a CD with a single big
file). You can do this directly with cdrecord, or most GUI CD-R
tools have
an option to burn a CD-R from an image file.

I have, so far, not found a way to access disks other than the system
disk from inside linux. I am not sure if I have something wrong with
the system or if it is an operator malfunction.

At least this time I
have emacs and am learning to use it. Several of my attempts to install
omitted emacs and that was one of the reasons to reinstall: to get a
tool to examine a few things.

Discribe has an option to copy CD/DVD. I will try that next. It sounds
like what you were describing.

In article <10nskv5s3g7ps8b@corp.supernews.com>,
Keith Krehbiel <redsilo@pldi.net> writes:

I have, so far, not found a way to access disks other than the system
disk from inside linux. I am not sure if I have something wrong with
the system or if it is an operator malfunction.


You might try posting details of what you've tried and what error messages
you get under an appropriately-titled thread. My initial guess is that
you're trying to mount HFS+ partitions, and Linux lacks support for HFS+.
(So far; I believe it's being worked on, although I've not looked into
this recently.) It could also be that you're just trying the wrong
partition numbers.


At least this time I
have emacs and am learning to use it. Several of my attempts to install
omitted emacs and that was one of the reasons to reinstall: to get a
tool to examine a few things.


That's overkill. If you omit a package during the initial install, you can
simply install that package later. I went back and skimmed your earlier
posts, but didn't see mention of what Linux distribution you're using, so
I can't provide specific instructions. In any event, it's usually easier
to fix an existing Linux installation than to re-install it.


Discribe has an option to copy CD/DVD. I will try that next. It sounds
like what you were describing.


CD-R software "copy" options usually expect to copy from one physical
medium to another, rather than from an image file to CD-R. I'm not
familiar with Discribe specifically, though, so I can't promise that this
isn't where the image copy option is located.

Again you gave us very little information.
exactly what command did you run to try to mount the disks?
Exactly what is the content of the /etc/fstab file?

What happens when you try
mount -a
after you have logged on as root?
Give all output from that command.

What is the output when you type
df
see above.

What happens if you type
mount /mnt/cdrom
?
ditto

If that does not work, what happens when you type
mount /dev/hdc /mnt/cdrom

and then, if there is no error messages
ls /mnt/cdrom

Keith Krehbiel <redsilo@pldi.net> writes:

]I am using Debian from a set of disks from Edmunds Enterprises of
]America. I am sure that I am not trying to access HFS+. It could very
]well be that I am trying to access the wrong partition numbers. I have
]had very limited success trying read the directory structure from within
]linux. I know that part of it is ignorance on my part. I have seen in
]threads that the error output can be directed to a file and the file
]then can be read and posted but I have not been able to complete the
]circle there. At this point I have not tried to install any sort of
]internet access onto linux. I figured to try to get the os working
]first. Maybe that is a mistake. Chalk it up to the simple mind.

]snip>That's overkill. If you omit a package during the initial install,
]you can
]simply install that package later. <clip
]I agree wholeheartedly that it is overkill. The reason I have found it
]necessary is that the only time I can access the installation library is
]from the initial installer and from the first boot following
]installation. In subsequent sessions I cannot access anything that is
]not on the boot partition and that includes the distribution CDs which I
]am relatively certain are not HFS+. The error I get at that point is
]that the file/directory I am trying to access does not exist. I have
]even tried to access another linux hard drive and that fails to work. Go
]figure. The first appears to be HFS or at least partially HFS and the
]remaining disks appear to be ISO9660, at least from MacOS.
]I tried the CD Copy function but, as you said, it expects a CD to be
]read and then written to a blank. I did, however, burn a disk with the
]image I had downloaded. I have not yet tried to read it from linux but
]the image opens from MacOS to look like the original disk that I had
]damaged. This is after opening the image. Opening the disk shows the
]image, not the directory structure as on the original.
]I tore down my system to move it out of the way after I installed the
]last time. Upon reassembling it in a different location I have not been
]able to boot again. This is a Mac problem not linux. I just have to
]remember which spell to cast to get it going again.
]Thank you for your help. I am sure that a lot of my trouble is caused
]by plain ignorance on my part.
]Keith

]Rod Smith wrote:
]> In article <10nskv5s3g7ps8b@corp.supernews.com>,
]> Keith Krehbiel <redsilo@pldi.net> writes:
]> ]>>I have, so far, not found a way to access disks other than the system
]>>disk from inside linux. I am not sure if I have something wrong with
]>>the system or if it is an operator malfunction.
]> ]> ]> You might try posting details of what you've tried and what error messages
]> you get under an appropriately-titled thread. My initial guess is that
]> you're trying to mount HFS+ partitions, and Linux lacks support for HFS+.
]> (So far; I believe it's being worked on, although I've not looked into
]> this recently.) It could also be that you're just trying the wrong
]> partition numbers.
]> ]> ]>>At least this time I
]>>have emacs and am learning to use it. Several of my attempts to install
]>>omitted emacs and that was one of the reasons to reinstall: to get a
]>>tool to examine a few things.
]> ]> ]> That's overkill. If you omit a package during the initial install, you can
]> simply install that package later. I went back and skimmed your earlier
]> posts, but didn't see mention of what Linux distribution you're using, so
]> I can't provide specific instructions. In any event, it's usually easier
]> to fix an existing Linux installation than to re-install it.
]> ]> ]>>Discribe has an option to copy CD/DVD. I will try that next. It sounds
]>>like what you were describing.
]> ]> ]> CD-R software "copy" options usually expect to copy from one physical
]> medium to another, rather than from an image file to CD-R. I'm not
]> familiar with Discribe specifically, though, so I can't promise that this
]> isn't where the image copy option is located.
]

+ Bill Unruh wrote:

+ > What happens when you try
+ > mount -a
+ > after you have logged on as root?
+ > Give all output from that command.
+
+ I have not tried that either. I hope you don't mean for me to type the
+ output verbatim. That is what it will require to give what you ask for
+ at this point.

On Mon, 01 Nov 2004 14:32:58 -0600,
Keith Krehbiel <redsilo@pldi.net>, in
10od7bstae95a4f@corp.supernews.com> wrote:

+ Bill Unruh wrote:


+ > What happens when you try
+ > mount -a
+ > after you have logged on as root?
+ > Give all output from that command.
+
+ I have not tried that either. I hope you don't mean for me to type the
+ output verbatim. That is what it will require to give what you ask for
+ at this point.


No, that's why G*d invented redirection...

# mount -a > ~/mount-output

Copy and paste (or otherwise insert) the contents of the file
mount-output.

You might follow up the "mount -a" with the output of "fdisk -l"
(so we can see your filesystems):

# fdisk -l >> ~/mount-output
^^append to an existing file, create if necessary

Simply trim the resulting file, stick it in a post, and send it on.

James
Believe it or not, I actually kinda understand output redirection. I

+ From the file I really have no place to paste. As things currently are
+ I am communicating from another computer running MacOS 9.1. One of the
+ several problems I am having is accessing disks/files/devices, etc. from
+ linux.

+ Not sure if I can make text go to MacOS, maybe that would work.

On Mon, 01 Nov 2004 22:55:01 -0600,
Keith Krehbiel <redsilo@pldi.net>, in
10oe4p5k802it79@corp.supernews.com> wrote:


+ From the file I really have no place to paste. As things currently are
+ I am communicating from another computer running MacOS 9.1. One of the
+ several problems I am having is accessing disks/files/devices, etc. from
+ linux.


Then the first thing you need to look at is the output of 'fdisk
-l'. It's been a *very*long*time* since I've looked at MacOS9.x, but I
think the odds are that you have an HFS filesystem. fdisk will give up
the pertinent information about the current partitions, and tell us
what it thinks your disk state is. So far as I know, if you have
HFS+, you're hosed.

If not, then it should be a matter of figuring out which device is the
correct partion for MacOS (more than a few kilobytes in size). Then:

mount -t hfs /dev/hfsfilesystem /somemounpoint

where "hfsfilesystem" is like "hda6" or "sda5", and "/somemountpoint"
is an arbritary empty directory. There may be a /mnt directory already
available. If not, make one. "mkdir /somemountpoint" for instance.


+ Not sure if I can make text go to MacOS, maybe that would work.


Fortunately, text is text, even if it looks a little odd due to the
niceties of the end-of-record delimiter.

James