> > a version number of the config file would also be nice then there is less
> magic
> >
> > struct sheepdog_config {
> > + uint16_t configversion; <- what do you think
> > uint64_t ctime;
> > uint64_t space;
> > uint16_t flags;
> > uint8_t copies;
> > uint8_t store[STORE_LEN];
>
> Sounds like a good plan, but preferably the version number should be
> after the old config data, so that the lack of it can be used to signal
> that it is a "version 0" format.
>
We need to clean up the config file once because it has changed. I think config
version in first place is better style - but I'm not the expert here.
--
sheepdog mailing list
[email protected]
http://lists.wpkg.org/mailman/listinfo/sheepdog
