From: Dave Eckhardt <davide+p9@cs.cmu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Removal of .i files from sources?
Date: Tue, 4 Dec 2007 12:45:23 -0500 [thread overview]
Message-ID: <14045.1196790323@lunacy.ugrad.cs.cmu.edu> (raw)
In-Reply-To: <20071203222511.GA1228@hermes.my.domain>
> I need to build a cpu kernel from sources. Therefore I have been
> following the tip of the day recipie from the wiki. Assembling the
> sd*.n files fails due to the corresponding .i files already exist.
> In my current setup I cannot delete those nor touch them or change
> permissions.
It sounds like it's time for my occasional commercial for divergefs,
a file system which lets you layer arbitrary changes on top of a
read-only file system (it even handles deletions).
If you say
% divergefs -p /some/dir /sys/src
you can build whatever you want. And you can resume your work the
next day with the same command.
Dave Eckhardt
next prev parent reply other threads:[~2007-12-04 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 22:25 Christian Kellermann
2007-12-04 9:22 ` Robert Raschke
[not found] ` <adc391e1dfd3d40c6439b19c65d02dff@tombob.com>
2007-12-04 9:43 ` Christian Kellermann
2007-12-04 17:45 ` Dave Eckhardt [this message]
2007-12-05 8:08 ` Christian Kellermann
2007-12-05 13:56 ` David Leimbach
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=14045.1196790323@lunacy.ugrad.cs.cmu.edu \
--to=davide+p9@cs.cmu.edu \
--cc=9fans@cse.psu.edu \
/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).