> > I would like to add that perhaps using tmpfs instead of ramfs would be
> > a nice touch.
I've written some code that allows using an initial tmpfs which gets it's
contents from a tar file (optionally compressed). See
http://www.escape.de/users/outback/linux/patch-2.4.17-inittar.gz (should also
work for 2.4.18) and (for later kernels):
[hpa, on tmpfs mounted over initramfs:]
> Baloney. You can't swap out what is actively in use, and something
> that's overmounted is actively used. You're supposed to clean up the
> contents before overmounting. I discussed with viro a scheme (using
> two ramfs's) which made that close to automatic, but I think he
> thought it was needless complexity.
But you don't have to swap anything. As I understand, the current concept is:
- a very minimalistic initial fs that doesn't anything meaningful except
allowing the creation of directories (mount points).
- one or more other fs's on top of this, either overmounted or mounted on a
For example, my patch for 2.4.19-preX just does a
sys_mount("tmpfs", "/root", "tmpfs", ...);
Later, the tar image is extracted into this tmpfs. There's no need to swap or
unmount any filesystems. If you want to mount another filesystem as root and
throw away the tmpfs, just use chroot(8) and pivot_root(8).
Correct me if I'm wrong.
ps: please answer with cc: to my address, since I'm not subscribed to this
mailinglist and may take longer to search the archives for answers.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/