From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] newbie question - keeping up to date
Date: Mon, 12 Jul 2004 20:30:40 -0600 [thread overview]
Message-ID: <68a46a69df8a1fbf2ed3c4f120cf5c5b@plan9.ucalgary.ca> (raw)
In-Reply-To: <Pine.BSI.4.58.0407121618140.14511@malasada.lava.net>
i forgot to mention -- you can just copy the kernel from /386. run
'9fat:' and see what's in /n/9fat (plan9.ini and a kernel are there)
and copy the same kernel from /386, it should have all updates.
as far as i can see on my system all kernels in /386 contain the
vmware graphics device so you ought to be safe :)
>> which conflicting files did you have when you pulled?
>
> it said that the /386/lib and /386/lib/acme files were locally
> built and that it wouldnt replace them. I manually deleted
> them and repeated the update. There were a few other files
> as well (some .8 files and one or two .c and .h files).
>
> Let me try again and rebuild a kernel this time.
>
next time do 'replica/pull -vs', which will overwrite conflicting
files with the ones from sources and save you the trouble of having to
delete them by hand. just make sure you don't overwrite important
configuration files like /rc/bin/{cpu,term}rc or /lib/ndb/local which
you may have modified for your system (until you've set up venti, or
fossil snapshots at the very least:)
next prev parent reply other threads:[~2004-07-13 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 2:01 Tim Newsham
2004-07-13 2:16 ` andrey mirtchovski
2004-07-13 2:20 ` Tim Newsham
2004-07-13 2:30 ` andrey mirtchovski [this message]
2004-07-13 5:11 ` Tim Newsham
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=68a46a69df8a1fbf2ed3c4f120cf5c5b@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).