Is it possible to mount an ISO in NEXTSTEP 3.3?
I have the developer tools CD in ISO file format but I don't have a SCSI CD-ROM. I checked the "man" documentation for "mount" but it doesn't seem to have the ability to mount files, or if it does, it's not obvious.
Another option would be to mount it over the network somehow. I have Mac OS X and Raspberry Pi machines at my disposal if that's the way to do it.
Thanks!
I solved this problem in a convoluted, painful way:
1. Copied ISO file to flash drive
2. Booted Mac with Linux rescue CD
3. Mounted ISO like this: "mount -t ufs -o ufstype=nextstep-cd /dev/cdrom /nextcd"
4. Tarballed the resulting directory then gzipped it... big mistake by the way as you'll see in a second.
5. Copied the tar.gz file to my Mac server's ftp directory
6. FTP-ed to the NeXT
7. Gunzipped then untarred - this took almost half an hour! It turns out "turbo" isn't really all that fast. It would have been quicker to just use "tar" - the space saved from compressing the file wasn't worth the significant extra time required to uncompress it. It's amazing how far computers have come in 25 years...
8. Installed developer tools smoothly and without drama.
FYI, you can use NFS from a NeXT. I wrote a howto on using the NFS automounter (search the forums), but you can also use a static NFS mount (requires many of the same steps).
Funny, I found this when doing a web search for how to mount an ISO in NeXTSTEP. I tried your command but it didn't work; eventually I was able to get this working by mounting the ISO on my Mac, creating a tarball of the files on the disc, moving the tarball to the NeXT, and untarring that directly on the NeXT.
Quote from: eagle on May 23, 2022, 08:19:45 AMFunny, I found this when doing a web search for how to mount an ISO in NeXTSTEP. I tried your command but it didn't work; eventually I was able to get this working by mounting the ISO on my Mac, creating a tarball of the files on the disc, moving the tarball to the NeXT, and untarring that directly on the NeXT.
The command didn't work you say. How did you end up mounting it on the Mac then? I'm trying this now under macOS Sonoma. Many thanks.
bp
Have you taken a look at vmount?
https://ftp.nice.ch/pub/next/unix/disk/_vmount.0.6a.README.htmlQuotevmount is a utility that allows you to mount foreign filesystems in your
directory hierarchy. It uses the NFS-interface to the kernel to make the
files available and the Linux code for the low level filesystem access.
* What filesystems can currently be accessed?
=============================================
The filesystem sources are taken from the Linux 2.0.25 kernel, which supports
the following filesystems for disk devices:
ext the old Linux native filesystem
ext2 the new Linux native filesystem
xiafs another old Linux native filesystem
minix the minix filesystem (Linux floppies)
umsdos unix permissions on top of a FAT filesystem
msdos normal FAT filesystem
vfat FAT filesystem with long filenames (Win95, NT compatible)
iso9660 CDROM filesystem
xenix System V filesystem for XENIX (PC-Unix)
sysv SCO-Unix System V filesystem format
coherent System V filesystem for Coherent (PC-Unix)
hpfs the OS/2 filesystem (read only)
affs the Amiga Fast FileSystem
ufs should be standard berkeley "fast file system" format
ntfs NT-filesystem, read only (not part of the kernel but a
separate module written by Martin von Loewis)
I have tested (unarchiving, compiling):
ext2: read and write OK.
minix: read and write OK.
vfat: read and write OK.
ntfs: read only, seems to work OK although the implementation of the
"." and ".." directory entries is not completely correct (wrong
inode numbers in ls). Some directoryies generate endless loops
of warning or error messages. I had to modify the ntfs module
sources a bit to make things work, mostly removing #includes of
non-kernel headers and removing access restrictions.
iso9660: read only :-), multi session uses an ioctl() that is not
available on NEXTSTEP. However, it seems to work better than
NeXT's implementation with multi session disks. Sizing etc. is
much faster than on NeXT's iso9660 filesystem.
hpfs: I have not tested this myself, but Peter Eybert
<pjoe@charon.muc.de> has reported that it works for read only
access.
Quote from: blakespot on May 24, 2024, 10:17:20 AMThe command didn't work you say. How did you end up mounting it on the Mac then? I'm trying this now under macOS Sonoma. Many thanks.
Hey - I think I just double-clicked the ISO file and it mounted.
Having this exact problem with OS4.2 developer at the moment. Have the ISO on my IBM Thinkpad T43 but don't want to waste a CD burning it. NetBSD 8.3 does not allow mounting of OS4.2 image so I can copy the developer packages to the DOS partition.