Date: Fri, 15 Dec 2000 14:38:44 GMT From: Andreas Haakh <Andreas@Haakh.de> To: Boris <koester@x-itec.de> Cc: Bert Driehuis <driehuis@playbeing.org>, freebsd-isdn@FreeBSD.ORG Subject: Re: GRRRRRRRRR COMPILER ERRORS Message-ID: <20001215.14384463@wilma.IbHaakh.de> In-Reply-To: <10066501434.20001215093233@x-itec.de> References: <Pine.BSI.4.21.0012150228470.2818-100000@c1111.nl.compuware.com> <10066501434.20001215093233@x-itec.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Bert, I don't know the steps you followed to upgrade your OS. Nevertheless=20= there is a file called UDATING in /usr/src containig lots of important=20= informations... I usually do the following steps (well, if the changes to /usr/src/sys=20= are minor, then I omit some of them) make -i update >Update.log 2>&1 & (bash-syntax) inspect Update.log, search for changes, errors etc. read /usr/src/UPDATING patch some files (some patches to i4b didn't make it into stable ;-) make buildworld >World.log 2>&1 & inspect World.log if there are any errors. Under some circumstances You = need to make clean before make buildworld. save /kernel.old to /kernel.something make kernel KERNEL=3DMYKERNEL (this builds AND installs =84MYKERNEL=93 a= s=20 kernel. You can also do this in two steps: make buildkernel=20 KERNEL=3DMYKERNEL and make installkernel KERNEL=3DMYKERNEL if the=20 buildprocess was fine.) mergemaster (to update /etc) make installworld reboot Andreas >>>>>>>>>>>>>>>>>> Urspr=FCngliche Nachricht <<<<<<<<<<<<<<<<<< Am 15.12.2000, 18:32:33, schrieb Boris <koester@x-itec.de> zum Thema Re[= 4]:=20 GRRRRRRRRR COMPILER ERRORS: > Hello Bert, > Thursday, December 14, 2000, 5:54:38 PM, you wrote: > BD> On Fri, 15 Dec 2000, Boris wrote: > BD> Maybe I'm old fashioned, but I never ever try to do two things at = the > BD> same time. If you're updating your kernel to an unreleased version= , you > BD> should expect breakage, so replacing the kernel with an untested o= ne is > BD> asking for trouble. > hm, ok. > BD> If your complaint boils down to "I expect CVSup to produce a perfe= ctly > BD> running system and I'm disappointed", then you are absolutely righ= t=20 (and > BD> also very unrealistic). The people that develop the updates to Fre= eBSD > BD> stable are most likely not ISDN users, and if you CVSup you run th= e=20 risk > Ahh, i have understand! ok no problem. I thought that a stable commit= > is tested first by quality-assurance people (?). Hm, however i like to= > see what=B4s going on with freebsd so i like to update the sources > nearly daily -) It is a motivation to me if i am developing my litte > progs. > BD> of encountering breakage. In the greater scheme of things, ISDN is= not=20 a > BD> central part of FreeBSD, because relatively few people have ISDN (= as > BD> much as FreeBSD is not the life focus of the ISDN4BSD developers -= - > Aaaah ok! > BD> First of all, you should consider getting a test system if you wan= t to > BD> run untested combinations of software. Blaming FreeBSD for the pro= blems > not FreeBSD, i4b -) I love FreeBSD > BD> you had because you inadvertantly blew away a working system is no= t the > BD> right thing to do. > *ggg yes this was my first complete failure on a production server > hihi. > BD> Second, not keeping a copy of a working kernel on your root partit= ion=20 is > BD> asking for trouble. > I had a working kernel, but the system was not working anymore after > build world. When the trouble begans, i had bsd 4.1.1, updated the > sources to the latest cvs, make world (works), i4b patch .. tried to > compile the kernel.. after the i4b patch.. BANG -) The old 4.1.1 > kernel was alyways available but i had no access to anything anymore > after rebooting. I=B4ve got access denied, the only thing i could do i= s > to log in, that=B4s all. > Ok i=B4m sorry for my reaction, it was my first real failure of a very= > important server and i have never expected this on a stable-branch. > Now i know what=B4s up and i had a chance to understand why sometimes= > something is wrong. I will try to get it up and running on my > developer server first, before updating a netserver and i have learned= > to write a backup-script with all neccessary content i need for the > next failure *gggg. Another person said to build a GENERIC kernel > FIRST, a very good idea. So i will make a GENERIC kernel first after > make world, then i try to get my configuration up and running. > Thanks to all the people for helping me! > -- > Best regards, > Boris mailto:koester@x-itec.de > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isdn" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001215.14384463>