From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Wed, 20 Sep 1995 03:49:16 -0400
From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: mkext vs. tar for custom install
Topicbox-Message-UUID: 25848fd2-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19950920074916.AIjNs0RyRHqRGrlOHM59CLeo4Xbe42i6n6U9sX8CJ-I@z>

>>Is the manpage out of date, or is build.c breaking the rules somehow?
{disk/kfscmd allow} puts disk/kfs into the same state as a full-blown file server
during its initial load (or `allow' at config level).  (the command is
issued by startkfs in build.)

disk/mkext -u will set owners, groups, and file times correctly to those
on the CDROM.  tar won't.  although it probably doesn't affect the distribution,
tar also has several other restrictions (eg, path name limits) that don't apply
to mkext.