Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c > #23144

image as an FS: HOWTO?

From Ivan Shmakov <oneingray@gmail.com>
Newsgroups comp.lang.c
Subject image as an FS: HOWTO?
Date 2012-07-07 17:53 +0700
Organization Aioe.org NNTP Server
Message-ID <86629z971t.fsf@gray.siamics.net> (permalink)

Show all headers | View raw


	Suppose that I need to develop a "few files only" application
	(so to make it convenient to pass around for the users of the
	systems lacking decent package management) based on an existing
	"way too many files to install manually" one (written in C.)

	My idea is that the files would be: the immutable data file, the
	mutable data file, and the executable binary; though I'm not yet
	sure if I'd need to keep all the working data in a single file.

	Then, the immutable data file could be pretty much any kind of
	an archive, as long as it supports quick name-to-file lookup (so
	Tar won't fit, but ISO-9660 or even Zip probably will.)

	Do I understand it correctly that for such a scheme to work, I
	need to "shadow" all the common filesystem functions, either
	stream-based, such as fopen (), or filehandle-based, such as
	open (), to access the "image" instead (should the filename in
	question begin with a specific prefix)?

	(ISTR that AVFS [1] does something similar.)

[1] http://avf.sourceforge.net/

	I guess that I won't be able to run a binary contained within
	such an "image" on the common systems of today?

	TIA.

-- 
FSF associate member #7257

Back to comp.lang.c | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

image as an FS: HOWTO? Ivan Shmakov <oneingray@gmail.com> - 2012-07-07 17:53 +0700
  Re: image as an FS: HOWTO? Malcolm McLean <malcolm.mclean5@btinternet.com> - 2012-07-07 04:34 -0700
  Re: image as an FS: HOWTO? Nobody <nobody@nowhere.com> - 2012-07-08 03:42 +0100
  Re: image as an FS: HOWTO? Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-07-10 21:20 +0000

csiph-web