Date: 17 Jul 1998 16:54:53 +0200 From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) To: CyberPsychotic <fygrave@krsu.edu.kg> Cc: ben@rosengart.com, Alfred Perlstein <bright@hotjobs.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. Message-ID: <rx4n2a87cjm.fsf@oslo.geco-prakla.slb.com> In-Reply-To: CyberPsychotic's message of Fri, 17 Jul 1998 19:54:10 %2B0300 (EET DST) References: <Pine.LNX.3.95.980717194951.17417S-100000@unslaved.freenet.bishkek.su>
next in thread | previous in thread | raw e-mail | index | archive | help
CyberPsychotic <fygrave@krsu.edu.kg> writes: > > > so binaries, right? > > And documentation, yes. Changed to /etc are made in /usr/src/etc and > > have to be brought over by hand. > Ah, I see. So things are more wide than in linux. in linux the most thing > i do is upgrade kernel, and binaries, if i feel they produce bugs working > with new kernel (but usually they don't) under BSD things are more > dependent uppon each other. hmm.,.. thanks anyway, I guess now i see the > whole picture. I don't think things are "more dependent upon eachother"in FreeBSD than in Linux. If you feel like, you can rebuild exactly the binaries you want manually, e.g. for ls(1): # cd /usr/src/bin/ls # make ; make install But since FreeBSD, unlike Linux, is one large, integrated, centrally controlled project, we have a consistent source tree and tools to rebuild the entire tree in just a few commands. If you are jumping a large gap (e.g. 2.2.1 to 2.2.7) you should at the very least rebuild most of man section 8 (init(8), fsck(8), mount(8) etc), anything that access kernel structures, such as ps(1) and top(1) (which is now part of the base system rather than a port), config(8), and the LKMs. Don't expect everything to work just peachy unless you rebuild everything, though. > yep.:) I just found out that i lack this binary, so I have to download by > hand cvsup archives (together with modula libs.,. hmm, why would it want > modula anyway?) You don't. Just look for a package named "cvsup-bin" and install that. > > Then you run cvsup with one of the files in /usr/share/examples/cvsup/, > > for you it would be stable-supfile. > and this file tells cvsup what to download, right? Yes. It's not very difficult to read, once you understand that everything that is on a "*default" line can also be put on a collection line. For instance, instead of: *default tag=RELENG_2_2 src-all ports-all tag=. you can drop the *default line and just use src-all tag=RELENG_2_2 ports-all tag=. > > You might want to copy it and tweak > > it first. > > Cvsup knows how to work with proxies; I've never had to do it, but take > > a look at the man page for the appropriate arguments. > yeah. I guess I won't have problems tuning it here. John Polstra (IIRC) has written an excellent CVSup FAQ, though the URL escapes me at the moment. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?rx4n2a87cjm.fsf>