Re: [freebsd-stable] Re: BIND update?
> > On Thu, Jul 10, 2008 at 12:25:33PM +0200, Oliver Brandmueller wrote: > > OK, thanx for clarification. I totally overlooked the updated bind port; > > anyhow, I use base system bind and didn't plan to change that (although > > it might me a good idea, as this situation clearly shows). > > You can always use the WITH_REPLACE_BASE option in the port to > overwrite the base system named, or use the differences in the > extracted tarball of 9.5.0 vs 9.5.0-P1 to update the source of the > base one yourself. > Shouldn't you also add : NO_BIND= true# do not build BIND into /etc/make.conf if you do, so it doesn't get clobbered? Tuc/TBOH ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [freebsd-stable] Re: BIND update?
> > On Thu, Jul 10, 2008 at 10:03:24AM -0400, Tuc at T-B-O-H.NET wrote: > > > On Thu, Jul 10, 2008 at 12:25:33PM +0200, Oliver Brandmueller wrote: > > > > OK, thanx for clarification. I totally overlooked the updated bind > > > > port; > > > > anyhow, I use base system bind and didn't plan to change that (although > > > > it might me a good idea, as this situation clearly shows). > > > > > > You can always use the WITH_REPLACE_BASE option in the port to > > > overwrite the base system named, or use the differences in the > > > extracted tarball of 9.5.0 vs 9.5.0-P1 to update the source of the > > > base one yourself. > > > > > Shouldn't you also add : > > > > NO_BIND= true# do not build BIND > > > > into /etc/make.conf if you do, so it doesn't get clobbered? > > That would be WITHOUT_BIND=true in /etc/src.conf on RELENG_7 and later, > just for added clarification. > Thanks for the catch. I was looking at a 5.5 system I was doing that on. I haven't replaced base on my 7.0's, those were only changes to /etc/rc.conf for named_program="/usr/local/sbin/named". Tuc/TBOH ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: can I do 6.1-RELEASE to 6.2 via cvsup
> > Also, the list of things to do is a bit mis-ordered and truncated. The > official list is in /usr/src/UPDATING and reads: > > > make buildworld > make kernel KERNCONF=YOUR_KERNEL_HERE > [1] > [3] > mergemaster -p [5] > make installworld > make delete-old > ^ Where in /usr/src/UPDATING is that command. I can't see it. > > mergemaster [4] > Thanks, Tuc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: can I do 6.1-RELEASE to 6.2 via cvsup
> > --==_Exmh_1193178365_55823P > Content-Type: text/plain; charset=us-ascii > > > > > > > Also, the list of things to do is a bit mis-ordered and truncated. The > > > official list is in /usr/src/UPDATING and reads: > > > > > > > > > make buildworld > > > make kernel KERNCONF=YOUR_KERNEL_HERE > > > [1] > > > [3] > > > mergemaster -p [5] > > > make installworld > > > make delete-old > > > > > ^ Where in /usr/src/UPDATING is that command. I > > can't see it. > > > > > > mergemaster [4] > > > > > > > > > Thanks, Tuc > > > > Sorry. It is there on my 6-Stable system, but it looks like it is not in > 6.2-Release.It's been in HEAD for over 2 years. > > I am a bit confused,though. I see my 6.2-Stable has src/UPDATING,v > 1.416.2.35, but I can't find that version in CVS. I see only one commit, > 1.416, in RELENG_6 and I know that it has had more commits since then. > AH, no wonder why I don't see it... I'm on 5.5 still, and only have version 1.342.2.36 from 5/26/2006. Thanks, Tuc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: can I do 6.1-RELEASE to 6.2 via cvsup
> > > Also, the list of things to do is a bit mis-ordered and truncated. The > > > official list is in /usr/src/UPDATING and reads: > > > > > > > > > make buildworld > > > make kernel KERNCONF=YOUR_KERNEL_HERE > > > [1] > > > [3] > > > mergemaster -p [5] > > > make installworld > > > make delete-old > > > > > ^ Where in /usr/src/UPDATING is that command. I > > can't see it. > > > > > > mergemaster [4] > > > > > > > > > Thanks, Tuc > > > > Sorry. It is there on my 6-Stable system, but it looks like it is not in > 6.2-Release.It's been in HEAD for over 2 years. > > I am a bit confused,though. I see my 6.2-Stable has src/UPDATING,v > 1.416.2.35, but I can't find that version in CVS. I see only one commit, > 1.416, in RELENG_6 and I know that it has had more commits since then. > Um, I went to go check the file on a 7.0-BETA1 I just installed and and doing the ground up on.. And I just realized something... WHERE is the step to install the kernel?? I always thought it was : make buildworld make kernel KERNCONF=YOUR_KERNEL_HERE make installkernel KERNCONF=YOUR_KERNEL_HERE [1] [3] Tuc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-BETA1.5 Available...
> > On Thursday 25 October 2007, Ken Smith wrote: > > Sorry, I had a bit of a false start with 7.0-BETA1. I've got sets > > of build machines used for the Monthly Snapshots and procedures in > > place to try and minimize the mistakes I could make while doing > > those Snapshots (previously one set for HEAD, one set for > > RELENG_6). The set of machines I'll be using for the 7.0-RELEASE > > build are the ones that had previously been doing the HEAD > > snapshots and I missed doing one very important adjustment to the > > build routine while doing the BETA1 builds, which resulted in the > > builds being based on HEAD. I didn't notice during the tests I do > > before uploading it because the build procedure makes most things > > (e.g. uname) say what you told it to build, you need to look harder > > to discover that sort of mistake. So, 7.0-BETA1 actually should > > have been called something more like 8.0-SURPRISE... :-( > > > > Sorry for the screw-up. > > > > This change seems to break portupgrade. It complains that it cannot > parse the output of uname. I think it is not capable of handling the > 1.5 after the BETA. > I hadn't tried that... When you do build a new kernel, it goes back to BETA1 though. Tuc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: I can`t install BETA1.5 via ftp
> > I have some problems with installation of beta1.5 and beta1. That problems > are: > > 1) I try to install system via "passive ftp". So, when I use DHCP nrtwork > configuration anything works fine, but when I try to specify network > configuration > by hands (without using of DHCP) my system cant find any ftp mirror. > > 2) When you restart installation program, hav been formatted disks, and has > began > to copy "... base into /..." disk write error occur: " can`t write to diks... > if > full" > > 3) After all ports has been coppied, screen with message "LOCADET INDEX" > appear. After few minutes of this screen appear screen with information about > that " SIG -10 has been caught..." and all installation fail! > I didn't run into the first two of those myself. I installed with regular ftp, DHCP'd and also by hand, and I found the mirrors fine. Maybe your using a bad DNS server? For #2, you know you need to re-specify that volume is on what disk. Even though you label/format previously, it doesn't remember well between runs. As for #3, I tried to install Linux and got a SIG 11 the first time. I didn't try the second time. I ended up rebooting, but the system was installed fine. I think you need to solve the issues in the order you presented them. You can always ALT-F# over to the "#" prompt and check your networking, etc. Tuc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: date/time trouble - PST came too early
> > From: Vivek Khera <[EMAIL PROTECTED]> > > Date: Wed, 7 Nov 2007 15:09:35 -0500 > > Sender: [EMAIL PROTECTED] > > > > > > On Nov 5, 2007, at 8:58 PM, Chris H. wrote: > > > > > Ahh... I'm guessing that you missed the following post in this > > > thread titled > > > "date/time trouble - PST came too early [fixed]" posted 11-02. > > > > > > LI Xin offered the following solution, which solved my dilemma: > > > > No, I saw that... but like I said, most of us did this last year when > > the new DST rules went into effect. Did you not notice it last year? > > OK. This is twice you've said it and you are wrong. This is the FIRST > year of the new US DST dates. Last year DST ended on October as it has > for many years. > > From H.R. 6, Energy Policy Act of 2005, SEC. 110. DAYLIGHT SAVINGS: > "Effective Date- Subsection (a) shall take effect 1 year after the date > of enactment of this Act or March 1, 2007, whichever is later." > I think what he meant to say is that we all fixed it last year, even though it didn't go into effect until THIS year. I updated my systems as soon as the "zoneinfo" port was updated. Tuc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
