Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Oct 1997 14:41:04 -0700
From:      Christopher Allen <gmfangs@asmrb.org>
To:        nik@iii.co.uk
Cc:        freebsd-doc@freebsd.org, John Polstra <jdp@polstra.com>
Subject:   Re: Problem with make install in modula-3-lib-3.6
Message-ID:  <v03110703b07ab7b21c36@dynamic-addr-115.consensus.com>
In-Reply-To: <19971026112422.00542@iii.co.uk>
References:  <v03110700b0780cf82dc1@lr8e1-port6.zocalo.net>; from Christopher Allen on Sat, Oct 25, 1997 at 02:26:20PM -0700 <v0311071eb076ebcb87cc@dynamic-addr-115.consensus.com>; <v0311070bb07693f4dfc8@dynamic-addr-115.consensus.com> <199710241919.MAA16170@austin.polstra.com> <v0311071eb076ebcb87cc@dynamic-addr-115.consensus.com> <19971025113557.59209@iii.co.uk> <v03110700b0780cf82dc1@lr8e1-port6.zocalo.net>

next in thread | previous in thread | raw e-mail | index | archive | help
At 4:24 AM -0700 10/26/97, nik@iii.co.uk wrote:
>On Sat, Oct 25, 1997 at 02:26:20PM -0700, Christopher Allen wrote:
>> At 3:35 AM -0700 10/25/97, nik@iii.co.uk wrote:
>> >For the next time, you might want to take a look at
>> >
>> >    http://www.freebsd.org/tutorials/upgrade/upgrade.html
>> >
>> >which is a tutorial I wrote that goes through all the steps necessary
>> >to do a successful 'make world'.
>>
>> There was some useful info in the tuturial, but the tutoral didn't seem to
>> be up to date, nor did it seem to have me as an appropriate audience. My
>> goal was just to go from a freshly installed 2.2.2 CD-ROM to a stable more
>> current version, which I think is narrower than the broader goals of your
>> tutorial which I think was more for upgrading 2.1 to any particular version.
>
>The specific aim is for it to take someone who has version 'n' of FreeBSD
>installed, and the source code for version 'n+x' in /usr/src, and how to
>use that source code to upgrade their system.
>

I think there should be a document that gets a relative novice from the
CD-ROM distribution to a net-distributed distribution. It is 80% similar to
your document, but your document has to do so much more as someone could be
upgrading from any version.

At 4:24 AM -0700 10/26/97, nik@iii.co.uk wrote:
>It doesn't really care what method you're using to get the latest source
>code, whether it's CTM, CVS, copying-from-a-CD-you've-just-bought or some
>other distribution method.

I just think a quick link should be there in your tutorial. Your tutorial
is in an entirely different section then the handbook, and is fairly close
to the top, thus I found it first. You have to read the handbook to find
the updating source code stuff.

At 4:24 AM -0700 10/26/97, nik@iii.co.uk wrote:
>On Sat, Oct 25, 1997 at 02:26:20PM -0700, Christopher Allen wrote:
>> Thus I also used other advice.
>>
>> Here are some notes should you wish to revise your tutorial:
>>
>> * I did my upgrade without going to single user as my machine was at a
>> remote location. I probably should have at least temporarily disabled
>> login, but I didn't need to do that as I knew that I was the only user. If
>> I had been local, I would have been glad to do single user, but it was nice
>> to find out others had done it in multi.
>
>A couple of other people have also mentioned that. I was always under the
>impression that you needed to go single user to update any system files
>that were in use at the time.
>
>Certainly when I first wrote the tutorial that was the case. I'll confirm
>that it's not *absolutely* necessary and then update the tutorial.
>
>Either way, it's generally a good idea (certainly if the machine can take
>some downtime, and you have access to the console).

Agreed, it is generally a good idea if you can, but it is useful to know
that you can do it without with a little more risk.

Also, for some people, a modem attached to serial port could serve this
purpose as well, but I don't know how to set that up as the console for
single user (another tutorial?)

At 4:24 AM -0700 10/26/97, nik@iii.co.uk wrote:
>On Sat, Oct 25, 1997 at 02:26:20PM -0700, Christopher Allen wrote:
>> * The tutorial didn't point me to CVS and CTM, so I flailed a bit trying to
>> ftp down source that I didn't need to do.
>
>It's not really meant to. There are sections in the handbook that deal
>with those, see http://www.freebsd.org/handbook/handbook228.html#483 for
>more details.

Agreed, I just think the pointer should be there as it is not obvious.

At 4:24 AM -0700 10/26/97, nik@iii.co.uk wrote:
>On Sat, Oct 25, 1997 at 02:26:20PM -0700, Christopher Allen wrote:
>> * There is a file that has to be pkg_add'ed that is not obvious to get CVS
>> installed (and probably fixes some other minor things). From my notes:
>>
>> At 5:38 PM -0700 10/22/97, John Polstra wrote:
>> >OK, it's not supposed to matter whether they're executable or not.
>> >Your problem is that you need to upgrade your <bsd.port.mk> file.
>> >Satoshi has made this very easy to do.  Just go to:
>> >
>> >    http://www.freebsd.org/ports/
>> >
>> >and grab the "2.2.2 to 2.2-stable upgrade kit" that's described
>> >there.  That will fix the problem.
>>
>> At 9:51 PM -0700 10/22/97, John Polstra wrote:
>> >> So I've put the upgrade kit in the /usr/ports/distfiles directory
>> >> (btw, this was not obvious to me as a new user of FreeBSD) and did a
>> >> pkg_add.
>> >
>> >Actually, it doesn't belong in the distfiles directory.  Just put it
>> >anywhere, say "~/222upgrade-97.07.21.tgz".  Then do this:
>> >
>> >    pkg_add ~/222upgrade-97.07.21.tgz
>
>That sort of information really needs to go in another document (that
>should be referenced from my tutorial and from the URL quoted above),
>called something like "Issues you will encounter when moving between
>different versions".

As long as it is referenced in your tutorial -- there are ALOT of people
starting with 2.2.2, as that is is most of the books now, and this problem
really through me for a loop.

At 4:24 AM -0700 10/26/97, nik@iii.co.uk wrote:
>No one (so far) has had the time to create and maintain such a document.
>If you'd like to start (and it's high time someone did), I'd suggest moving
>this over to the freebsd-doc mailing list.

I will do so starting now -- this message will go to the list.

At 4:24 AM -0700 10/26/97, nik@iii.co.uk wrote:
>On Sat, Oct 25, 1997 at 02:26:20PM -0700, Christopher Allen wrote:
>> Most of your tutorial sections 4 & 6 I didn't use -- no one else said that
>> I need to do anything but merge my /etc directory.
>
>Yes. But sections 4, 5 and 6 go through a known *safe* way to do this.
>
>The problem is that "merge in any changes to /etc" has become a bit of
>a shorthand on the mailing lists.
>
>For example, between versions 2.1 and 2.2 (or possibly between 2.2 and 2.2.2)
>files were *added* and *deleted* to /etc. It's not enough to simply do the
>equivalent of
>
>    for file in /etc; do
>        if exists /usr/src/etc/$file
>            /usr/src/etc/$file /etc/$file
>        fi
>    done
>
>Since this won't add files to /etc, nor will it remove them.
>
>Note that some files in /usr/src/etc (and subdirectories thereof)
>*cannot* simply be copied over. The "make distribution" step ensures that
>these files are converted to the right format.
>
>For example, /usr/src/etc/etc.i386 contains rc.i386, which should go into
>/etc, disktab, which should go into /etc, and MAKEDEV, which should go into
>/dev. If you just copy from /usr/src/etc to /etc you'll get a /etc/etc.i386
>directory, which is very wrong.

I didn't realize this, and they /etc.i386/ files were not properly moved in
my system.

Worse is the issue of removing files -- ouch, that is hard, as there are so
many files in /etc that are not put in by the 2.2-stable release, so it is
hard to tell which ones are "old" and should be removed, vs. added by
something else. Even your tutorial doesn't help much there. This section
really could use some help to make it easier.

At 4:24 AM -0700 10/26/97, nik@iii.co.uk wrote:
>On Sat, Oct 25, 1997 at 02:26:20PM -0700, Christopher Allen wrote:
>> At 9:51 PM -0700 10/22/97, John Polstra wrote:
>> >After you run cvsup to get your update, the updated sources will be
>> >in "/usr/src".  Next you have to rebuild the system.  The basic idea
>> >for doing that is:
>> >
>> >    cd /usr/src
>> >    make world
>> >
>> >and then go to bed and have a good night's sleep, because it will
>> >take a while (2 to 18 hours, depending on your system).
>
>Yep, that's basically correct, although it omits some non-essential stuff.
>
>> Although you referred people to the compiling the kernel section, it was
>> too complex, and the below worked easier for me.
>>
>> At 12:19 PM -0700 10/24/97, John Polstra wrote:
>> >To build yourself a new GENERIC kernel, do this:
>> >
>> >    cd /usr/src/sys/i386/conf
>> >    config GENERIC
>> >    cd ../../compile/GENERIC
>> >    make depend
>> >    make
>> >    make install
>> >
>> >and then reboot.
>
>If you haven't changed your kernel from the original GENERIC then that will
>also work. If you have done then you will need to go through the steps
>outlined in the tutorial to make sure that everything still works, and has
>the same syntax.

I do believe that the above at minimum should be in your tutorial, as the
build kernel stuff you refer to is more than what most new people need.

At 4:24 AM -0700 10/26/97, nik@iii.co.uk wrote:
>On Sat, Oct 25, 1997 at 02:26:20PM -0700, Christopher Allen wrote:
>> At 12:19 PM -0700 10/24/97, John Polstra wrote:
>> >You also should check your various files in "/etc" against the new
>> >ones in "/usr/src/etc", and merge in any changes or additions that
>> >have taken place between 2.2.2 and now.

At 4:24 AM -0700 10/26/97, nik@iii.co.uk wrote:
>I would strongly suggest you do steps 4, 5 and 6. If for no other reason,
>it means that if you do have a problem at some point in the future you
>*know* that you did the update a particular way, and you can tell anyone
>else who's trying to diagnose the problem. It's far simpler to say
>
>   "I followed the steps outlined at http://...."
>
>than it is to say
>
>   "I did this, then I did that, and then I did this as well..."
>
>More comments, particularly as a result of the above comments are always
>welcome. As are suggestions for re-wording, or new questions, or explanations
>of things that weren't clear.

I will do so.

-----------------------------------------------------------------------
.. Christopher Allen                          1563 Solano Ave., #353 ..
.. <gmfangs@asmrb.org>          ;->          Berkeley, CA 94707-2116 ..
..                                                     h510/528-9899 ..
.. <http://www.asmrb.org/~gmfangs/>;      f510/649-3301 o510/649-3300 ..





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v03110703b07ab7b21c36>