Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!psgrain!m2xenix!agora!rgrimes
From: rgrimes@agora.rain.com (Rodney Grimes)
Subject: Re: Install+patch: THANKS, comments, questions...
Message-ID: <C50I4w.LF3@agora.rain.com>
Organization: Open Communications Forum
References: <9309418.24038@mulga.cs.mu.OZ.AU>
Date: Mon, 5 Apr 1993 13:14:55 GMT
Lines: 103
summer@ee.mu.OZ.AU (Mark Summerfield) writes:
> [install/ patch success story]
>So, instead of reporting bugs/problems I'd like to THANK everyone who
>helped out. Those who did so directly know who they are, I assume, so I
>won't mention them here. Special thanks to Jordan and Rodney -- the patchkit
>does seem to work, for the most part, and installing the patches was really
>easy (not what I'd expected from some of the postings I'd read). The
>instructions seem clear and helpful to me.
Your welcome...
>I do have a few quick questions and comments:
>1) If there really are bugs in the source tree, why wasn't I hit by them?
> I notice Rodney has owned up to a few, so I just used "find" to
> make sure everything installed was new as of this morning, which it
> was (with explicable exceptions), so I assume the compile/install worked.
With a clean source tree the make depend is not really needed, the big
failures with the 0.2.2 patchkit where mostly make depend failures, I
believe a cd /usr/src; make clean; make; make install; runs all the
way through without failing, but am not sure my system is now to far
beyond that patchkit for me to test it out. But I do know that I
can cd /usr/src and do ALL of the possible targets, except lint, and
we don't have lint is the reason for that failure.
>2) If someone could point me to some good documentation on the date/time
> system I'd be grateful -- I still don't really understand how
> /etc/localtime and the kernel timezone interact to produce the correct
> time (so my clock's six hours off!). I also don't know how to make
> sure that local daylight saving periods are configured correctly.
> Is there an editor for those /usr/share/timezone/... files?
Don't know. I'm luck I am DST 8, same as Berkeley, never had to muck with
that on a unix box, and the only other thing I've worked on that uses
TimeZones is apollo, and there it is real easy...
>3) I'm not happy with the standard installation procedure for manual
> pages. The way I figure it, I have at least two copies of every man
> page -- the nroff one in the src tree, and the formated one. In some
> cases there is a third, because even after a "make clean" in /usr/src
> some of the c library pages remain in the /usr/obj tree (incidentally,
> is there a legitimate way of completely cleaning this tree?
> rm -r /usr/obj is tempting! :-) What I'd much rather do is put
> links to the src tree into /usr/share/man/man?, and let man format
> each page when and if I first read it. I can obviously do this
> myself, but it would be nice to have it as an option on the build
> procedure.
If you want to try and maintain both a source and binary system you need
2 copies, the third copy you mentioned as not being removed by a make clean
has been fixed in the next patchkit. A lot of work went into cleaning up
the build tree and makeing sure it all went. As I type this a 16 hour
long regression test sequence is running that does about 4 times as many
things to the source tree as buildworld.sh. I am really testing the
source tree out this time. Also there are lots of NEW sources in the
next patchkit, basically all the stuff that never made it over from
Net/2 is now there.
To clean you obj tree you can do this, but It fails on your version
of the code in 2 places, maybe 3:
cd /usr/obj; rm -r *; cd /usr/src; find . -name obj -exec rm {} \;
make obj; #That should remove all old obj dirs, and links, then
#recreate them I did something very similiar in the NEW buildworld.sh
Good Idea on the man page thing, If some one can implement it CLEANLY.
>4) Again on the subject of saving disk space, is it OK to delete all
> the *.pl* files once the patching process is complete, and I'm happy
> that everything has gone OK? Or are they used if I ever want to
> deinstall a patch?
DO NOT remove them at this time, there are needed to remove patches, and
(I know no one wants to here this) there is at least one of the patches
in patchkit0.2.2 that must be deinstalled to upgrade to the next patchkit.
I am working on some changes to a future version of the patchkit that
does away with all the .pl? files. If you are tight on disk space I
suggest that you compress them, then make sure you decompress them
before running patches.
>5) A quick tip for anybody planning on doing a custom installation as
> described in the FAQ: as a first-timer with disk partitioning and
> stuff, I found it really instructive to run a standard install,
> boot the fixit floppy, and examine my hard disk with disklabel,
> then take it from there. Also, I think a really big print entry
> about which partitions are used for swap, whole disk, and whole
> disk used by 386bsd is an absolute MUST for the new FAQ! :-)
Yes, I agree, I hope that the person doing the FAQ picks this one up.
>Again, thanks -- I'm really happy with my system so far. I hope I've
>been constructive here: that is certainly my intention!
Your welcome again :-) :-).. It really helps to read this kinda of stuff
now and again..
--
Rod Grimes rgrimes@agora.rain.com
Accurate Automation Company All opinions belong to me and my company!
Get your free copy of 386bsd from agate.berkeley.edu:/pub/386BSD via ftp!
An out of work contractor... You need unix work done.... Send me your project!