On Saturday, 23 January 1999 at 6:24:17 +0800, Peter Wemm wrote: > Greg Lehey wrote: >> On Friday, 22 January 1999 at 9:23:48 -0800, Jake wrote: >>> I can no longer bring up my vinum volume with the vinum read >>> command: >>> >>> vinum read /dev/wd0s1e /dev/wd2s1f >>> vinum read /dev/wd0s1e >>> vinum read /dev/wd2s1f >>> >>> all come back with >>> vinum: no drives >> >> Correct. As I explained in detail in my HEADS UP message a couple of >> days ago, you must now specify drives, not partitions. The correct >> command might be >> >> vinum read /dev/wd0 /dev/wd2 > > Does vinum scan the slices? What if there are two freebsd slices?
Currently it just scans the compatibility slice. I'll change that later. > From vinumhdr.h, it looks like it totally ignores slices. Well, that's not the place I'd look. > If somebody is working on a disk shared with something else (eg: > DOS/windoze), then perhaps the examples should be: vinum read > /dev/wd0s1 /dev/wd2s1 Interesting. Yes, I think this would work. The real problem here is that, as you know from private correspondence, I haven't found a good way to determine what partitions are on the system, so I go through with brute force and try to open each possible partition. This will change when I find a better way, but it shouldn't require incompatible changes to the command line syntax again. With any luck, I *will* be able to say `vinum start', and it will go out and find the partitions by itself. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
