From: "Doug Henderson" <djhender@telusplanet.net>
To: <9fans@cse.psu.edu>
Subject: [9fans] Installing the updates
Date: Mon, 31 Jul 2000 08:53:04 -0600 [thread overview]
Message-ID: <001c01bffaff$09b49fa0$0500a8c0@telusplanet.net> (raw)
In one of my porting project, <stdio.h> is included twice. This fails,
because, for instance, the way getchar is declared, first as an external
function, then as a macro. As a result, I added the usual protection code
(#ifndef <tag>; #define <tag>; <original body of header>; #endif) to
/sys/include/stdio.h, and others. I have also added some defines to allow
<event.h> and <mouse.h> to both be included without error/warning messages.
And I messed around with the ethernet driver code for my card (RealTeck
8029AS) trying to find out why it didn't work. Etc, etc.
I understand that wrap/inst will not overwrite my modified files, unless I
force it to do so. But I want to get a list of them, stash the source
changes to safety,
and overwrite all files with those from the release. Then, if still
necessary, I
will reapply the parts that actually fix a problem, instead of help diagnose
one. I want to have a clean updated system, with well known modifications.
Is there a wrap/inst expert out there that can provide some quick help.
How do I list the contents of a wrap archive?
How do I list the conflicts between a wrap archive and the current versions
(without actually installing anything)?
Thanks,
Doug
-- --
Doug Henderson, Calgary, Alberta, Canada
next reply other threads:[~2000-07-31 14:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <djhender@telusplanet.net>
2000-07-31 14:53 ` Doug Henderson [this message]
2000-07-31 17:38 ` Scott Schwartz
2000-07-31 20:10 ` Steve Simon
2000-07-31 15:15 rob pike
2000-08-01 8:53 ` Douglas A. Gwyn
2000-08-01 12:12 ` Howard Trickey
2000-08-02 9:11 ` Douglas A. Gwyn
2000-08-01 14:31 ` Ralph Corderoy
2000-08-01 16:03 ` Greg Hudson
2000-08-01 16:32 ` James A. Robinson
2000-08-01 17:05 ` James A. Robinson
2000-08-02 9:39 ` Douglas A. Gwyn
2000-08-02 9:11 ` Douglas A. Gwyn
2000-08-03 14:51 ` ozan s. yigit
2000-07-31 15:57 jmk
2000-07-31 17:09 Russ Cox
2000-08-01 5:42 Russ Cox
2000-08-01 6:04 Russ Cox
2000-08-01 12:55 rob pike
2000-08-02 9:39 ` Douglas A. Gwyn
2000-08-01 13:06 rob pike
2000-08-01 13:10 ` Lucio De Re
2000-08-01 13:35 rob pike
2000-08-01 18:34 ` Greg Hudson
2000-08-02 9:53 ` Douglas A. Gwyn
2000-08-01 16:26 rob pike
2000-08-02 21:49 ` Steve Simon
2000-08-01 16:27 rob pike
2000-08-02 10:53 ` Ralph Corderoy
2000-08-01 17:06 Russ Cox
2000-08-02 8:32 ` Bruce G. Stewart
2000-08-02 9:47 forsyth
2000-08-02 9:52 ` Boyd Roberts
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='001c01bffaff$09b49fa0$0500a8c0@telusplanet.net' \
--to=djhender@telusplanet.net \
--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).