Re: help with dselect (on m68k)
OK, I've figured out (at least partially) what is going on. dselect is working just fine and so is everything else, except the actual CD. I gave up on dselect and rebooted, then mounted the debian CD and discovered that my system sees all the folders on it as just plain text files. That's why it can't find the directories when I direct it to them. This is probably my fault, though I'm not exactly sure why. I downloaded the cd image from the debian ftp site and made a CD. I was sure to make it 9660 format and can see all the files and folders on it with my Mac, I just can't get to them with the Linux box. Has anyone made a CD for 68K Mac from this image before? Is so, what is the secret. I tried making another disk at only 2x speed and that didn't work either. I know I have a complete valid CD image, I just can't copy it. David Kachel
Re: help with dselect (on m68k)
On Fri, 28 Jan 2000, David said: OK, I've figured out (at least partially) what is going on. dselect is working just fine and so is everything else, except the actual CD. I gave up on dselect and rebooted, then mounted the debian CD and discovered that my system sees all the folders on it as just plain text files. That's why it can't find the directories when I direct it to them. This is probably my fault, though I'm not exactly sure why. I downloaded the cd image from the debian ftp site and made a CD. I was sure to make it 9660 format and can see all the files and folders on it with my Mac, I just can't get to them with the Linux box. Has anyone made a CD for 68K Mac from this image before? Is so, what is the secret. I tried making another disk at only 2x speed and that didn't work either. I know I have a complete valid CD image, I just can't copy it. What command did you use to make the cd? You need to use a byte for byte duplicator in order to make the cd from the image. Did you use Linux to make the cd with dd if=[/file/cd/image] of=[/device/name/of/cdwriter] or did you use a mac utility? A byte for byte duplicator will put the filesystem on the cd for you as it is contained in the image. -ptw-
Re: help with dselect (on m68k)
OK, I've figured out (at least partially) what is going on. dselect is working just fine and so is everything else, except the actual CD. I gave up on dselect and rebooted, then mounted the debian CD and discovered that my system sees all the folders on it as just plain text files. That's why it can't find the directories when I direct it to them. This is probably my fault, though I'm not exactly sure why. I downloaded the cd image from the debian ftp site and made a CD. I was sure to make it 9660 format and can see all the files and folders on it with my Mac, I just can't get to them with the Linux box. Has anyone made a CD for 68K Mac from this image before? Is so, what is the secret. I tried making another disk at only 2x speed and that didn't work either. I know I have a complete valid CD image, I just can't copy it. What command did you use to make the cd? You need to use a byte for byte duplicator in order to make the cd from the image. Did you use Linux to make the cd with dd if=[/file/cd/image] of=[/device/name/of/cdwriter] or did you use a mac utility? A byte for byte duplicator will put the filesystem on the cd for you as it is contained in the image. I found the problem and made another CD last night (the third!). It works just fine. Now all I have to do is wrestle with dselect's intransigent march to the sea! Thanks. David Kachel
Re: help with dselect (on m68k)
Clyde was just trying to help you, you need to be more patient and read more carefully. On most install cds, the distribution path is: /debian/dists/stable If it is not there your on your own. I would suggest exploring the cd and writing down the path when you've found it, then go back to dselect. My expirience with dselect (on i386) tells me that the standard path to the distribution is usually mentioned in the dialog when you are asked for the path. If the suggested path is incorect, then you must look for it yourself. And yes, there ARE non-standard install cds out there. good luck, -ptw-
Re: help with dselect (on m68k)
Clyde was just trying to help you, you need to be more patient and read more carefully. You're right. It's been a very frustrating day all around. Sorry. It seems I do indeed also have an issue with mounting the CD. Dselect asks me for the name of a block device. Since I cannot find that term anywhere in any of the documentation, I'm stuck! What is a block device, and how do I get its name? (Should I name it Shirly, Bruce, Albatross?) David Kachel
Re: help with dselect (on m68k)
On Wed, 26 Jan 2000, dkphoto wrote:
It seems I do indeed also have an issue with mounting the CD. Dselect
asks me for the name of a block device. Since I cannot find that term
anywhere in any of the documentation, I'm stuck! What is a block device,
and how do I get its name? (Should I name it Shirly, Bruce, Albatross?)
amber{jgg}~#dmesg | grep -i cd
hdb: CD-ROM 36X/AKW, ATAPI CDROM drive
hdb: ATAPI 36X CD-ROM drive, 128kB Cache
Uniform CDROM driver Revision: 2.55
/dev/hdb is the block device name for the CD. It will be printed during
bootup, but you can review the boot messages with the 'dmesg' command. You
should edit /etc/fstab and put an entry like this:
/dev/hdb/cdromauto noauto,ro,defaults,user0 0
Depending on your m68k, your CD interface may be something entirely
different (scsi?) or it may need a special module.. Look at the boot
messages.
Jason
Re: help with dselect (on m68k)
David Kachel wrote: You're right. It's been a very frustrating day all around. Sorry. It seems I do indeed also have an issue with mounting the CD. Dselect asks me for the name of a block device. Since I cannot find that term anywhere in any of the documentation, I'm stuck! What is a block device, and how do I get its name? (Should I name it Shirly, Bruce, Albatross?) Block device names follow a simple naming convention under Linux. For example, the first disk on the first ide controller is always /dev/hda, the second is always /dev/hdb, etc. I believe, but am not sure, that the m68k achetecture uses scsi devices only. Scsi devices would be named /dev/sda, /dev/sdb, etc. On your system you would need to know how many scsi devices are installed on your scsi controller (I believe your machine is likely to only have one scsi controller, but I could be wrong.) Check the scsi id numbers on each of your scsi devices and determine where your cdrom fits in the order. (if you have three scsi devices with scsi id numbers 1, 3, and 6, and your cdrom has been assigned scsi id 6, then your cdrom is /dev/sdc). I hope that this helps somewhat. My help may be inacurate in some minor ways as I am not familiar with the m68k archetecture. You can feel free to flame me horribly if I've steered you wrong. I sugest that you visit http://www.linux-m68k.org , http://www.mac.linux-m68k for better information. Have fun! -ptw-
