public inbox for ecos-cvs@sourceware.org
help / color / mirror / Atom feed
From: asl@sourceware.org
To: ecos-cvs@ecos.sourceware.org
Subject: ecos/packages/fs/ram/current ChangeLog cdl/ram ...
Date: Sun, 02 Oct 2005 14:03:00 -0000	[thread overview]
Message-ID: <20051002140314.21105.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/ecos
Module name:	ecos
Changes by:	asl@sourceware.org	2005-10-02 14:03:14

Modified files:
	packages/fs/ram/current: ChangeLog 
	packages/fs/ram/current/cdl: ramfs.cdl 
	packages/fs/ram/current/src: ramfs.c 
	packages/fs/ram/current/tests: ramfs2.c 

Log message:
	* src/ramfs.c: Implement holes in files when using BLOCK
	allocation method. This requires allowing lseek to go past the end
	of the file.
	
	* test/ramfs2.c: Extended the lseek test to now seek past the end
	of the file. With the BLOCK allocation method this will create a
	whole. With the SIMPLE allocation method is just allocates the
	memory and fills it with zero.
	
	* cdl/ramfs.cdl: Added in interface which both SIMPLE and BLOCK
	implement. This allows the inference engine to work out is should
	enable BLOCK if SIMPLE is disabled by the user.
	
	2005-10-01  Dan Jakubiec  <dan.jakubiec@systech.com>
	
	* src/ramfs.c: (ramfs_mount, ramfs_open, ramfs_mkdir) Changed the
	permissions for files and directories created on RAMFS file systems
	from 000 to 777. This helps ported applications which wrongly
	assume there is some security concept and check for the existence
	of certain file permissions.


             reply	other threads:[~2005-10-02 14:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-02 14:03 asl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-01  9:31 asl
2004-03-29 13:01 asl
2003-02-24 14:22 jlarmour

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=20051002140314.21105.qmail@sourceware.org \
    --to=asl@sourceware.org \
    --cc=ecos-cvs@ecos.sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).