-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mic J wrote: > what about making an NFS export, then the underlying file system wouldnt > matter? > > What about using sshfs?
First, remember I was talking about two partitions on the same machine, so nothing like NFS (which requires processes on sender and receiver) can possibly work (else I understand nothing about NFS, which I suppose isn't completely impossible). I'd never heard of sshfs before, so I had to go investigate it. Seems like a really neat idea, but (I *think*, and this time, I really might be wrong) that it's much like NFS in needing processes on sener and receiver, which again, in the same machine, can't work. My problem is that the FreeBSD side of this match is a RAID1 mirror, using FreeBSD's twa driver. So far, I can't find that driver for OpenBSD, but I'm still looking (it's the AMCC 3Ware 9650-4 Raid controller). This means I CAN'T even see the FreeBSD partitions from OpenBSD, it needs to be FreeBSD looking into OpenBSD. I've a couple of WD640 drives on my RAID1, so it's got about 600G of storage. I have 500G dedicated to FreeBSD, and as soon as I find the OpenBSD driver for this controller, OpenBSD gets that remaining 100G. At the moment, OpenBSD has a 80 WD junk drive I found laying around (EIDE), so all of my experimentation HAS TO BE FreeBSD's attempting to mount the OpenBSD's partitions. I know I could use something like FAT32, but I'm really unhappy (philosophically) to use anything like FAT-n. If I find any other sort of OpenBSD filesystem, that FreeBSD can mount, I'm off to the races, but it has to work without needing OpenBSD to actually be active. Look, I think I've really bothered this list more than can reasonably allowed by now, if I don't see a solution, I'm going to see if maybe I can let this die. I've found a way to move the data I need, by transiting a 2nd machine. Slow it may be, but I'm getting embarrassed already at bothering you folks too much. > > > mic Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn59YcACgkQz62J6PPcoOm2UQCdH65zVbnilQRmZw8vzX1IkVP1 +uUAoIxMhJxJDKTfQL+3e7VxTsoIMN3c =D0iO -----END PGP SIGNATURE-----
