In message <[EMAIL PROTECTED]>,
"Stevenson, Charles" <[EMAIL PROTECTED]> writes
&PARTFILES& on UV is purely decorative. (Someone _please_ correct me if
that isn't true!)
&PARTFILES& was vital on PI, but maintained on UV solely for backward
compatibility in case guys like us ported some user-grown PI critter
that relied on it.
Ummm...
Sounds like the type 27 file is as vital on UV, as &PARTFILES& was on PI
- ie not at all!
Perhaps a UV example would help.
FSR is distributed, type27, with 5 partfiles.
The 5 parts are each dynamic hashed, type30.
The 4096 byte OS file called "FSR" is filled with x00 and xFF bytes,
scattered with some pointers to the partfiles.
LIST.DF FSR
Part file "/u1/SIMS5/FSR_p5", Part number = 5.
Part file "/u1/SIMS5/FSR_p2", Part number = 2.
Part file "/u1/SIMS5/FSR_p3", Part number = 3.
Part file "/u1/SIMS5/FSR_p4", Part number = 4.
Part file "/u1/SIMS5/FSR_p1", Part number = 1.
CT VOC FSR
FSR
0001 F (dist file)
0002 FSR
0003 /software/SIMS5/DICTS/D_FSR
Ohhhhhhhhhhhhhhh That is NOT what I expected to see!
On PI (and I'm SURE it was the same on UV) I would have expected to see
0001 F
0002 FSR_p1 vm FSR_p2 vm FSR_p3 vm FSR_p4 vm FSR_p5
0003 /software/SIMS5/DICTS/D_FSR
actually, I am sure it was the same on UV - I had a program writing
these things directly into the VOC, and it worked fine.
Well interesting ... maybe we're both right ... or maybe it works the PI
way in PI-flavour accounts (I haven't knowingly used anything else).
Cheers,
Wol
--
Anthony W. Youngman <[EMAIL PROTECTED]>
'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the
thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man
lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998
Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open Source Pick
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
