Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

Mnemo H3 (2.1.2) (Horde 3 branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Mnemo H3 (2.1.2) (Horde 3 branch)
# 1  
Old 01-10-2008
Mnemo H3 (2.1.2) (Horde 3 branch)
Mnemo Note Manager is the Horde notes/memos application. It providesWeb-based notes and freeform text in a way similar to the PalmOS Noteapplication and shared notepads. It requires the Horde ApplicationFramework and a SQL database for backend storage.License: The Apache LicenseChanges:
A privilege escalation in the Horde API has been fixed. A missing ownership validation on share changes has been fixed. Finnish, Japanese, Portuguese, Simplified Chinese, Spanish, and Traditional Chinese translations have been updated. Small bugfixes and improvements have been made.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT BSD

mknf

MKNF(8) 						      System Manager's Manual							   MKNF(8)

NAME

       mknf, rmnf - create and delete notesfiles

SYNOPSIS

       mknf [ -aon ] topic [ ... ]

       rmnf [ -f ] topic [ ... ]

DESCRIPTION

       Mknf and rmnf create and delete notesfiles respectively.  The same parameters apply for each: the `topic' is the name that the notesfile is
       known by.

       As mknf processes its arguments, creating new notesfiles, the name of each new notesfile is echoed to the terminal.  The new notesfiles are
       closed and the notesfile owner is made the sole director.  He customarily turns control over to the user requesting the notesfile by making
       that person a director.

       The -aon options apply to mknf only.  They signify that the notesfiles created are to permit anonymous notes, be  open,	and  be  networked
       respectively.

       If  the	file  `/usr/spool/notes/.utilities/access-template' is present, it contains a list of access-rights which are added to the created
       notesfile.  The file contains lines of access-rights similar to those used in the nfaccess(8) command.  In environments with  dynamic  cre-
       ation of notesfiles, such as on USENET nodes, one or more users can automatically be made directors of all new notesfiles.  If appropriate,
       they can be removed from the access list of newly created notesfiles as needed.

       Rmnf asks for verification of each notesfile before deleting it.  The notesfile is deleted if the response line	begins	with  a  `y'.	If
       invoked with the -f option, rmnf does not ask for verification before deleting the notesfiles.

       Only the notesfile owner is allowed to run mknf and rmnf.

BUGS

       Rmnf doesn't understand about absolute pathnames for notesfiles.  It refuses to remove notesfiles specified by absolute pathnames.

       Any user should be allowed to create private notesfiles in directories where he has permission.

FILES

       /usr/spool/notes/.utilities	       where these programs live.
       /usr/spool/notes/.utilities/access-template
					       Default access-list.
       /usr/spool/notes 		       Default notesfile directory.

SEE ALSO

       nfaccess(8), nfxmit(8), notes(1),
       The Notesfile Reference Manual

AUTHORS

       Ray Essick (uiucdcs!essick, essick%uiuc@csnet-relay.arpa)
       Department of Computer Science
       University of Illinois at Urbana-Champaign
       Urbana, IL

       Rob Kolstad (kolstad@convex.UUCP)
       CONVEX Computer Corporation
       Richardson, TX

							      University of Illinois							   MKNF(8)