Re: 4.1 make world and cvsup release field
In message <[EMAIL PROTECTED]> Christopher Stein writes: : Unfortunately, my system has no /usr/src/UPDATING. Then you need to get newer sources. /usr/src here is the conventional code for "the path to where you keep your sources." Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.1 make world and cvsup release field
On Mon, Sep 18, 2000 at 02:45:06PM -0400, Christopher Stein wrote: > On Mon, 18 Sep 2000, Kris Kennaway wrote: > > See the /usr/src/UPDATING file after updating your source and be sure to > > follow the directions precisely. > > Every message I see in the archives on these points is very simple: > "See /usr/src/UPDATING" It's more like, "See /usr/src/UPDATING after updating your source." > Unfortunately, my system has no /usr/src/UPDATING. If you had updated your source, you would have /usr/src/UPDATING. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.1 make world and cvsup release field
On Mon, 18 Sep 2000, Christopher Stein wrote: > Every message I see in the archives on these points is very simple: > > "See /usr/src/UPDATING" > > Unfortunately, my system has no /usr/src/UPDATING. Reread what I said: > See the /usr/src/UPDATING file after updating your source and be sure to > follow the directions precisely. ^^ > I have decided to go with a full net reinstall (rather than use cvsup) to > take me from 3.3 to 4.1. Cool. Probably easier all around. > I look forward to reading UPDATING when it lands on my system. Should make > great bedtime reading. :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.1 make world and cvsup release field
Every message I see in the archives on these points is very simple: "See /usr/src/UPDATING" Unfortunately, my system has no /usr/src/UPDATING. I have decided to go with a full net reinstall (rather than use cvsup) to take me from 3.3 to 4.1. I look forward to reading UPDATING when it lands on my system. Should make great bedtime reading. thanks -Chris On Mon, 18 Sep 2000, Kris Kennaway wrote: > On Mon, 18 Sep 2000, Christopher Stein wrote: > > > I would like to do this via cvsup and `make world'. > > My understanding is that `make world' is just buildworld followed > > by installworld, each a single monolithic step. Hhmm.. it seems > > to me that some build stages will not work without > > some other elements being installed. For example, my current modified > > 4.1 kernel will not build on a 3.3 system due to the old binutils (2.9.1 > > vs. 2.10). So how can a `make world' work in a monolithic build then > > install sequence? > > See the /usr/src/UPDATING file after updating your source and be sure to > follow the directions precisely. > > Kris > > -- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe <[EMAIL PROTECTED]> > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > -- -Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.1 make world and cvsup release field
On Mon, 18 Sep 2000, Christopher Stein wrote: > I would like to do this via cvsup and `make world'. > My understanding is that `make world' is just buildworld followed > by installworld, each a single monolithic step. Hhmm.. it seems > to me that some build stages will not work without > some other elements being installed. For example, my current modified > 4.1 kernel will not build on a 3.3 system due to the old binutils (2.9.1 > vs. 2.10). So how can a `make world' work in a monolithic build then > install sequence? See the /usr/src/UPDATING file after updating your source and be sure to follow the directions precisely. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.1 make world and cvsup release field
On Mon, 18 Sep 2000, Christopher Stein wrote: > > Hello, I don't wish to jump all the way forward to -CURRENT, but would > like to bring my 3.3 system up to 4.1 (would like to go beyond 4.0 > for kqueue() and fxp PEX support). > > How do I specify 4.1 in the release field of my supfile? > If you want 4.1-STABLE you need this: *default release=cvs tag=RELENG_4 On another note, this type of thing would better be suited for freebsd-questions. Peter Avalos TheShell.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
4.1 make world and cvsup release field
Hello, I don't wish to jump all the way forward to -CURRENT, but would like to bring my 3.3 system up to 4.1 (would like to go beyond 4.0 for kqueue() and fxp PEX support). I would like to do this via cvsup and `make world'. My understanding is that `make world' is just buildworld followed by installworld, each a single monolithic step. Hhmm.. it seems to me that some build stages will not work without some other elements being installed. For example, my current modified 4.1 kernel will not build on a 3.3 system due to the old binutils (2.9.1 vs. 2.10). So how can a `make world' work in a monolithic build then install sequence? How do I specify 4.1 in the release field of my supfile? (The man page isn't too enlightening. Says "The supfile is as described in sup(1)". `man sup` turns up nothing. An additional blurb on the release=releasename keyword talks about traditional sup and recommends using releasename=cvs.) thanks -Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
