From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: mkext vs. tar for custom install
Date: Wed, 20 Sep 1995 03:49:16 -0400 [thread overview]
Message-ID: <19950920074916.AIjNs0RyRHqRGrlOHM59CLeo4Xbe42i6n6U9sX8CJ-I@z> (raw)
>>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.
next reply other threads:[~1995-09-20 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-09-20 7:49 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-09-20 3:23 Steve
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=19950920074916.AIjNs0RyRHqRGrlOHM59CLeo4Xbe42i6n6U9sX8CJ-I@z \
--to=forsyth@plan9.cs.york.ac.uk \
/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;
as well as URLs for NNTP newsgroup(s).