linux-um archives
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] A quick humfs HOWTO
Date: Mon, 12 Apr 2004 11:06:15 -0400	[thread overview]
Message-ID: <7424.1081782375@marajade.sandelman.ottawa.on.ca> (raw)
In-Reply-To: Message from Henrik Nordstrom <uml@henrik.marasystems.com>  of "Thu, 08 Apr 2004 10:43:47 +0200." <Pine.LNX.4.44.0404081039320.7910-100000@filer.marasystems.com>

-----BEGIN PGP SIGNED MESSAGE-----


>>>>> "Henrik" == Henrik Nordstrom <uml@henrik.marasystems.com> writes:
    >> In the meanwhile I'm thinking about this system and it seems that
    >> this will eat lots of inodes because every file will be present
    >> twice in the [host] filesystem with the metadata version using
    >> only a few bytes.

    Henrik> Indeed, so the host better use a filesystem which can handle
    Henrik> this efficiently such as reiserfs if you plan on very large
    Henrik> filesystems.

  That's a good idea. So, let's make sure that we can put the file
system data in one place, and the metadata in a different place.

- --
]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBQHqwYoqHRg3pndX9AQE97wP/YDhKSNJQiN5dgm1UckIB69RlvNbf3SFC
notLIbqcPFVvGjyXwZgvoMMAfYnQ7ND/tnbH4IOEGjiUSMXCvK3vHMRB8uYZQltA
jAO8e0+Lt668ysS3BRpX0KdZ8EMCV45NBd2PY8h4IvE9WIfa6tmOSwGgnYtEX5N9
ZPSkuMzGm+g=
=3Grd
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2004-04-12 22:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08  2:07 [uml-devel] A quick humfs HOWTO Jeff Dike
2004-04-08  6:25 ` Nuno Silva
2004-04-08  8:43   ` Henrik Nordstrom
2004-04-09 18:49     ` BlaisorBlade
2004-04-12 15:06     ` Michael Richardson [this message]
2004-04-13  6:51       ` Henrik Nordstrom
2004-04-12 15:05   ` Michael Richardson
2004-04-08  7:58 ` [uml-devel] Re: [uml-user] " Rus Foster
2004-04-08 11:23   ` Jeff Dike
2004-04-08  8:35 ` [uml-devel] " Henrik Nordstrom
2004-04-08 11:34   ` Jeff Dike
2004-04-08 12:09     ` Henrik Nordstrom
2004-04-08  9:54 ` Nick Craig-Wood
2004-04-08 10:07   ` Henrik Nordstrom
2004-04-08 11:41     ` Jeff Dike
2004-04-08 10:26   ` stian
2004-04-08 11:41   ` Jeff Dike
2004-04-08 12:52   ` Jeff Dike
2004-04-08 12:03 ` [uml-devel] " Gerd Knorr
2004-04-08 12:49   ` Jeff Dike
2004-04-08 13:01     ` Gerd Knorr
2004-04-08 13:49   ` Robin Green
2004-04-12 15:11   ` Michael Richardson

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=7424.1081782375@marajade.sandelman.ottawa.on.ca \
    --to=mcr@sandelman.ottawa.on.ca \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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