Re: linking fs code problems in trunk

Hi,
   I am attaching a new patch, which:
  - Add the files fs/Module.cc,h similar to esi/Module.cc
  - Build a new library libfs.a
  - The fs/aufs/StoreFSaufs.cc, fs/diskd/StoreFSdiskd.cc and
fs/ufs/StoreFSufs.cc now contain just fake pointers
  - The FS::Init() method used to build ufs, aufs and diskd filesystems.
  - The FS::Init method called in main.cc before the code which reads
the config files. The FS::clean() currently does not used.
  - I left the old way initiating the coss filesystem. I did not want to
touch it, because currently does not used. I think the correct way, is
to (a) remove the StoreFScoss::GetInstance method, (b) declare the
StoreFScoss::stats as static and (c) merge the StoreFScoss::stat()
method with the static StoreFScoss::Stats()

Regards,
     Christos

Alex Rousskov wrote:
> On 03/29/2009 08:22 PM, Alex Rousskov wrote:
>>>...................
>> Can you move FsReg.cc to fs/Regs.cc?
>
> I am guessing you cannot move it "as is" because the code will be thrown
> away by the linker. If you are adding the Regs file, it would be nice to
> convert this to direct initialization and place into fs directory,
> similar to how esi/Module.cc does it. Perhaps the result should be
> called fs/Modules.cc then.
>
> ACLs should probably do the same, but it is more work because there are
> so many of them. Let's try not to take shortcuts where the proper
> implementation is simple though.
>
>
> Thank you,
>
> Alex.
>