From owner-freebsd-questions@FreeBSD.ORG Sat Mar 11 14:30:04 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 450EB16A4C7 for ; Sat, 11 Mar 2006 14:30:04 +0000 (GMT) (envelope-from vaaf@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACA5343D45 for ; Sat, 11 Mar 2006 14:30:03 +0000 (GMT) (envelope-from vaaf@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IVY009KEWA2JTC0@osl1smout1.broadpark.no> for freebsd-questions@freebsd.org; Sat, 11 Mar 2006 15:30:02 +0100 (CET) Received: from urban.broadpark.no ([213.187.181.70]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IVY001K8WA1SCA0@osl1sminn1.broadpark.no> for freebsd-questions@freebsd.org; Sat, 11 Mar 2006 15:30:01 +0100 (CET) Date: Sat, 11 Mar 2006 15:30:05 +0100 From: Vaaf In-reply-to: <20060307131714.GI53121@pcwin002.win.tue.nl> To: Stijn Hoop Message-id: <7.0.1.0.2.20060311152610.0200afb0@broadpark.no> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT References: <7.0.1.0.2.20060221103409.021a8808@broadpark.no> <200602210922.38445.duncan.fbsd@gmail.com> <7.0.1.0.2.20060228121217.022172c0@broadpark.no> <200602281021.20107.duncan.fbsd@gmail.com> <7.0.1.0.2.20060303115508.022b1de0@broadpark.no> <20060303110514.GW11960@pcwin002.win.tue.nl> <7.0.1.0.2.20060304174442.022ad158@broadpark.no> <20060304210846.GB46967@pcwin002.win.tue.nl> <7.0.1.0.2.20060306172439.0225beb0@broadpark.no> <20060307131714.GI53121@pcwin002.win.tue.nl> Cc: freebsd-questions@freebsd.org Subject: Re: Haven't been able to make world in about a year X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Mar 2006 14:30:04 -0000 At 14:17 07.03.2006, Stijn Hoop wrote: >On Mon, Mar 06, 2006 at 05:29:36PM +0100, Kristian Vaaf wrote: > > At 22:08 04.03.2006, Stijn Hoop wrote: > > >On Sat, Mar 04, 2006 at 05:45:29PM +0100, Kristian Vaaf wrote: > > >> At 12:05 03.03.2006, Stijn Hoop wrote: > > >> > On Fri, Mar 03, 2006 at 11:58:37AM +0100, Kristian Vaaf wrote: > > >> > > I run the script to save time. > > >> > > Basically I'd run the exact same chain of commands otherwise. > > >> > > > >> > You're missing the point: you'd run the exact same chain of commands > > >> > > > >> > --> _if everything goes according to plan_ <-- > > >> > > > >> > What this list has been telling you is that it sometimes doesn't work > > >> > like anyone expects to, and you need to make an informed > decision about > > >> > the next command to enter instead of having the script proceed. > > >> > > >> Whether I have my commands in my script or in my head doesn't > > >> make any difference. Yes I do read UPDATING and if I notice any > > >> changes they will be applied respectively. > > > > > >The moment one step does NOT work in the command sequence, you need to > > >alter your next move. No script can be prepared for all the things > > >that can happen. Which is why everyone is recommending you NOT to run > > >things in a script. > > > > I understand what you mean. > >No you apparently do not. > > > What I'm saying is, I do not expect a script to be prepared. > >Good. > > > I am the one reading UPDATING and modifying the script if there > is a change. > > Manually. Whether I write the sequence in the command line or into > > a script that I execute doesn't make no difference! > >It doesn't, but you're missing the point again. > >Let's say for the sake of argument that your computer's internal clock >broke down. FreeBSD will keep the time just fine so long as your >machine has power, so you don't notice anything. > >Now you run your script. > >It will go through the stages of building world, building kernel, >installing the kernel, and then rebooting. > >At this point your computer loses power for a few seconds and *presto* >your clock is set to 1970. > >Now, your script proceeds after the reboot with the new kernel. >Because your clock is WAY off, 'make installworld' will complain (well >it could work, but let's assume it doesn't). > >Your script however, doesn't see this. > >It therefore proceeds with mergemaster, and rebooting again. > >Now you're running a new kernel with older binaries, that may or may >not work. > >If this had happened to me [1], I would have stopped at the point where >'make installworld' throws an error, and wondered what went wrong. I could >backout my kernel install, reboot into my working configuration, and figure >things out before it all got out of hand (edited configuration files etc). > >And this is just ONE example of a admittedly minor thing that can go >wrong. > >This is why you should not automate the installation yourself. > > > What do you mean, mailing list in the loop? > >I mean that you should keep CC'ing questions@FreeBSD.org so that other >who wonder why automating this is not a good idea can search the >archives to find out my answer to you. > > > Hartelijk dank, Stijn! > >Geen probleem. > >--Stijn > >-- > > Thus again, we have succesfully proven that I cannot read minds. >It doesn't help. Almost all you ever get is "This mind intentionally left >blank." > -- Steve VanDevender, alt.sysadmin.recovery > Interesting statement. I'd say that, however, is kinda like the chance of getting shot by African guerilla when you live on the North Pole. Ain't gonna happen :) So, to everyone who has tried helping me: I guess there is no solution to this? FreeBSD will NOT successfully make my world no matter what I do. I've tried all the sequences. Please stop flaming me for using the wrong sequence. I've used ALL sequences. So I know that's not the problem. But then, what can it be? Is it time for the list to admit "there's nothing we can do"? All the best, Vaaf