... is the one *generating* the qid, surely? for instance, in the case of cdfs, the version number comes from the scsi(2...t have any necessary correspondence with qid.vers as found in the .... but by putting device-specific information in qid.vers, you run ... whether you're talking about versions, sizes, read/write offsets, or ... understand it you argue that qid.vers should change for each ...
... not responsible for checking the qid.version. the server (e.g.... devaoe or devfloppy) does the qid checking itself. i'm sorry?... is the one *generating* the qid, surely? for instance, in the ... have any necessary correspondence with qid.vers as found in the ... but by putting device-specific information in qid.vers, you run ...whether you're talking about versions, sizes, read/write offsets, or...
...i said that it was new behaviour. i did say that i thought...the abuse of wstat() to imply device i/o flushing. ☺ (just to remove... things around, by providing device-specificversioning behavior, you can end up... be fairly surprised if the version number changes every time it ... assumptions about ownership, dates or qid.vers are going to get burned by devices serving up physical media. try ...
...find any programs that use the qid.version for anything except to ...a file has changed if it qid.vers has changed. i gave one... it: say dossrv expected this behaviour. it would then do an occasional stat; if the qid.vers had changed, it would ... had been swapped because the version number had changed. i think ... devaoe or devfloppy) does the qid checking itself. the server checks ...
...find any programs that use the qid.version for anything except to infer...on it: say dossrv expected this behaviour. it would then do an occasional stat; if the qid.vers had changed, it would ... had been swapped because the version number had changed. as it ..., nor 9660srv do check the version number this way, as far as...a convenient place to store the version, rather than to deliberately make ...
..., if possible) to determine the version. the marvell and aoe driver ...something like cfs over such a device. turning things around, by providing device-specificversioning behavior, you can end up...to be fairly surprised if the version number changes every time it ... any programs that use the qid.version for anything except to ... the floppy driver use the qid.vers in this way on ...
... connections, if possible) to determine the version. the marvell and aoe driver consider ... software that uses the original notion of "version". for instance, i suppose it's not...run something like cfs over such a device. turning things around, by providing device-specificversioning behavior, you can end up with... to be fairly surprised if the version number changes every time it writes ...
... choose b), you need devsd to act like it does. i don't understand why qid.vers is involved. it's the read and writes that mustn't be misleading, so ...reasonably clear-cut, but devfloppy.c's could be better). that condition lasts until the device is reopened (or whatever is appropriate). it works for exported devices. i've probably just lost the plot, which i think is easy enough, both for...
>> the qid.vers does get exported. indeed it does. but if clients aren't expected to make use of it, why *is* it exported? i guess i'm arguing that the notions of device medium version (a.k.a. nchanges) and file version are two separate things, and it doesn't really make sense to present the former as the latter. why supress it?...
On 11/5/07, erik quanstrom <quanstro@quanstro.net> wrote: the qid.vers does get exported. indeed it does. but if clients aren't expected to make use of it, why *is* it exported? i guess i'm arguing that the notions of device medium version (a.k.a. nchanges) and file version are two separate things, and it doesn't really make sense to present the former as the latter....
