2009/8/31 Bakul Shah <bakul+pl...@bitblocks.com>: > But this is nasty! > % cat ndb/dom/'' # same as ndbquery dom ''
No, the nasty part is really that the file should be called `.' and the filesystem reserves dot as the reference to the current directory. You could probably call the file `dot' or `root' (cat ndb/dom/dot or cat ndb/dom/root) as something that shouldn't ever conflict with anything else -- but the root of DNS is not an empty string. --dho > dom= ns=A.ROOT-SERVERS.NET ns=B.ROOT-SERVERS.NET ns=C.ROOT-SERVERS.NET > ns=D.ROOT-SERVERS.NET ns=E.ROOT-SERVERS.NET ns=F.ROOT-SERVERS.NET > ns=G.ROOT-SERVERS.NET ns=H.ROOT-SERVERS.NET ns=I.ROOT-SERVERS.NET > ns=J.ROOT-SERVERS.NET ns=K.ROOT-SERVERS.NET ns=L.ROOT-SERVERS.NET > ns=M.ROOT-SERVERS.NET > > And it is not clear how you would map > % ndbquery attr value rattr ... > > Another alternative is to map each tuple to a directory: > % ls ndb/dom/A.ROOT-SERVERS.NET # just show the attributes! > dom ip > > % grep '' ndb/dom/A.ROOT-SERVERS.NET/* > dom:A.ROOT-SERVERS.NET > ip:198.41.0.4 > > An intriguing idea that can point toward a synth fs interface > to a dbms or search results.... But I don't think this would > be a lightweight interface. > >
