Remember - the point of a DBM is that it is much simpler than a full-blown oracle/mysql type DBMS. The best example of one is Berkely DB (aka, BDB). Please remember that when asking for features.

• I do not agree with the theory behind stored procedures, so I certainly will NOT implement them myself. However, I will gladly accept fully-tested patches for it.
• Logging of any kind requires additional files. DBM::Deep is supposed to be a single-file system.
• Systems tools for listing users/locks ... more specs, please?
• Backup of a single-file DBM is "cp".
• There is no server to startup or shutdown - that's the point of a DBM.
• Bulk-copy ... what are you looking for here?
• A security model can make sense. I'll gladly take a set of tests to write code against. (I'm willing to write the code here, unlike for stored procedures.)
• What are you referring to with runlevels?
• What kind of partitioning?
• There is almost no use of RAM, so no use of virtual memory. This goes along with the fact that there is no server. The DBM file is the shared point.
• Quotas make sense with a security model. However, how do you anticipate handling logging in?

In retrospect, it sounds like many of these features belong in Presto, not DBM::Deep. Does that ring closer to true for you?