linux-um archives
 help / color / mirror / Atom feed
From: Piotr Neuman <sikkh@wp.pl>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Example databases to keep humfs metadata
Date: Thu, 8 Apr 2004 21:14:49 +0200	[thread overview]
Message-ID: <200404082114.49123.sikkh@wp.pl> (raw)

gdbm: http://www.gnu.org/software/gdbm/gdbm.html

Simple file database, using hashing. Should be relatively easy to include with 
UML sources. It's pretty standard in all Linux distributions.

qdbm: http://qdbm.sourceforge.net/

More up to date than gdbm. Also has B+tree algorithms, so it may be more 
apriopriate for filesystem data. Disadvantage is it's larger size but I 
believe it could be trimmed down for UML.

API similiarity between gdbm and qbdm should allow for easy transition if 
needed.

Berkeley DB: http://www.sleepycat.com/

Very powerfull (logging for example) but it's features are rather overkill. 
Advantage is that it's available on all major distributions (UML could link 
to it dynamically).

Those are just a few possibilities, I'm sure there are other options (like 
open source SQL databases ;).


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

                 reply	other threads:[~2004-04-08 19:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200404082114.49123.sikkh@wp.pl \
    --to=sikkh@wp.pl \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox