From: wkt@tuhs.org (Warren Toomey)
Subject: [Unix-jun72] Import V1 filesystem trees into svn?
Date: Tue, 6 May 2008 16:53:29 +1000 [thread overview]
Message-ID: <20080506065329.GA32717@minnie.tuhs.org> (raw)
In-Reply-To: <20080506025744.GA22678@minnie.tuhs.org>
On Tue, May 06, 2008 at 12:57:44PM +1000, Warren Toomey wrote:
> Perhaps we do the same as we have done with patches:
>
> fs/root == original files as per s2 tape
> fs/usr == original files as per s2 tape
> fs/newfiles == new files to add to images
> fs/buildroot == modified root (not in svn)
> fs/buildusr == modified usr (not in svn)
> tools/xxx == script to build root and usr
I've imported fs/root and fs/usr into the svn repository with the files from
the s2 tape, and fs/new has Tim's etc/init so far. I haven't written any
scripts to make filesystem images yet.
Rather than use the file owner/permissions on the fs/ files, I'll modify
mkfs.c to read a table a la the rawperms table in tools/mktape.py, so that
the exact owner/perms get put into the V1 filesystem images.
Cheers,
Warren
next prev parent reply other threads:[~2008-05-06 6:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 2:38 Warren Toomey
2008-05-06 2:48 ` Tim Newsham
2008-05-06 2:57 ` Warren Toomey
2008-05-06 6:53 ` Warren Toomey [this message]
2008-05-06 9:35 ` [Unix-jun72] mkfs.c modified to set correct file owner/perms Warren Toomey
2008-05-06 3:05 ` [Unix-jun72] Import V1 filesystem trees into svn? Brad Parker
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=20080506065329.GA32717@minnie.tuhs.org \
--to=wkt@tuhs.org \
/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).