--TdDkFkGUMNACHLaO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jun 23, 2006 at 09:54:05PM +1000, Daniel Carosone wrote:
> On Fri, Jun 23, 2006 at 09:47:13PM +1000, Daniel Carosone wrote:
> > cgd on vnd works
>=20
> but you wanted to know about vnd on cgd - this certainly also works.

and finally I get what you were concerned about: will this work
directly with vnd on the cgd device raw, without a filesystem in
between?  no. vnd will need a filesystem to hold the file, cgd or not.

However, you could use a pretty light-weight and simple filesystem in
the cgd, especially given you're going to be read-only. I suggest
cd9660 with the single vnd file inside.

Of course, you wanted all of this to start with a file on the client,
and you're still going to need that for the cgd, which means another
vnd.

So you'll wind up with:

 - makefs -t ffs
 - vndcompress
 - makefs -t cd9660
 - dd same file size
 - vnconfig
 - cgdconfig
 - dd cd9660 image into cgd

and on the client machine,
ffs-on-compressedvnd-on-cd9660-on-cgd-on-vnd.  Which will work, but
will probably also drive you batty.  What you really want is a
compressed filesystem you can mount from the cgd directly.  I don't
have any good suggestions for that, sorry.

What are you storing in here? Can you really not do the decompression
in userland, even counting tricks like gzexe?

--
Dan.



--TdDkFkGUMNACHLaO
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (NetBSD)

iD8DBQFEm9unEAVxvV4N66cRAhPvAKDi6Cry7WPv+Izb0cCLl6sLcozhSwCgvLBD
+LNpedeaOs+mBMI19CMbIoE=
=BnVp
-----END PGP SIGNATURE-----

--TdDkFkGUMNACHLaO--