Re: Installs of Multiple Servers
Gerhard Sittig wrote: > > on the server and any other machine: > - mount /usr/src (ro?) and /usr/obj (not at the server, of > course:) > - make installworld > - mergemaster [ -s -v ] > - build kernel > - install kernel > - reboot > The only step I would add to this is if you use different sendmail.cf on different machines, ie the mail server vs. the reset. Put SENDMAIL_CF=mailserver.cf or client.cf in the machines /etc/make.conf and on the mail server do: - mount /usr/src (ro?) and /usr/obj (not at the server, of course:) + cd /usr/src/sendmail ; make - make installworld - mergemaster [ -s -v ] - build kernel - install kernel - reboot And on one of the other machines also do a + cd /usr/src/sendmail ; make so that each machine will install the proper sendmail.cf. The other option is on the build server to do cd /usr/src/sendmail make SENDMAIL_CF=mailserver.cf make SENDMAIL_CF=client.cf Of course you would name mailserver.cf and client.cf to match your .mc files that you have customized. Jim -- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." -- Charles Spickman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
[Conspectus] -stable, week ending 5th June 2000
[ Posting on behalf of Salvo Bartolotta, who did all the hard work. See http://www.FreeBSD.org/conspectus/index.html for more information. To contribute, contact [EMAIL PROTECTED] -- N ] FreeBSD-stable Conspectus, week ending 5th June 2000 Dates # Posts Subject May 31 - June 01 33.5 Release date May 30 - May 30 1Announce: -stable commit lists June 01 - June 01 1HEADS UP: Data corruption bug in Vinum found and fixed June 01 - June 01 2smbfs for FreeBSD 3.4 June 03 - June 05 5PCCARD support June 04 - June 05 23dfx driver June 02 - June 04 53.4-STABLE -> 4.0-RELEASE upgrade: unable to mount root partition June 02 - June 02 2Reboots on Alpha System running 4.0 Stable June 05 - June 05 1Spontaneous reboot with STABLE SMP kernel May 30 - June 01 18GENERIC 4.0 kernel compile fails on in_cksum.c May 30 - June 05 3Make world fails on latest 2.2.8... June 05- June 05 1FATAL FS Mount bug in -STABLE and -RELEASE May 31 - May 31 1FinallyA solution, It would appear May 30 - May 31 6-jn and -STABLE world May 29 - May 30 94.0-stable, OpenSSH v1 & v2 --- May 31 - June 01 (3 posts): 3.5 Release date On May 31, 2000, [Jordan K. Hubbard] announced to the -stable community a possible date for the release of FreeBSD-3.5: June 20. On the same day, [James Housley] reminded the -stable forum that CTM did not still work as it should: I have a PR that I think should be resolved before the release: http:// www.FreeBSD.org/cgi/query-pr.cgi?pr=18058 Description: src/usr.sbin/ctm/ctm/ctm_input.c limits files to 10Meg (10485760). cvs-cur.6200xEmpty.gz has a file, src/sys/dev/isp/asm_pci.h,v that is greather than 11Meg, actually 11913588 bytes. [Vivek Khera], replying to Jordan's letter, remarked: I was just investigating the NIS server on 3.4-STABLE, and noticed that the docs claim that TCP wrappers are not compiled in by default since they are not shipped with FreeBSD... However, that is no longer the case. Can we get this security updgrade included in the next release? All that seems to be necessary is to define YP_WRAPPER in the Makefile and link to the libwrap that is part of the system now. --- May 30 - May 30 (1 posts): Announce: -stable commit lists On May 30, 2000, [David Miller] made this proclamation: I've setup freebsd-stable-3 and freebsd-stable-4 majordomo lists at sparks.net. These use procmail to filter the RELENG_[3|4] messages out of cvs-all, so one can easily tell which commits affect them. Anyone could use procmail to filter the list himself, but I thought this was more convenient, especially for those not set up with procmail. To subscribe, send an email to freebsd-stable-[3|4][EMAIL PROTECTED] Digest versions are setup as well. --- June 01 - June 01 (1 posts): HEADS UP: Data corruption bug in Vinum found and fixed On June 1, 2000, [Greg Lehey] promulgated the following important result: I've just discovered (and fixed) a serious data corruption bug in Vinum. Under certain circumstances, serious data corruption can result: 1. You are using RAID-4 or RAID-5 plexes. 2. One of these plexes (not the first plex in the system, whether a RAID-[45] plex or not) develops parity problems. 3. You correct these errors with the 'rebuildparity' command. Under these circumstances, the corrected blocks will probably be written to the wrong subdisk. The original parity errors will remain. The fix is in 4-STABLE and 5-CURRENT (revisions 1.22.2.1 and 1.29, respectively). I don't think that 3-STABLE currently supports the rebuildparity command, but I shall check and MFC if necessary. --- June 01 - June 01 (2 posts): smbfs for FreeBSD 3.4 On June 1, 2000, [Boris Popov] broadcast some good news: Native smbfs for FreeBSD now supports version 3.4 of this OS (it may also run on 3.2 or 3.3, but definitely 'll crash on 3.1). Please note, that FreeBSD 3.4 doesn't contain src/sys/crypto directory which is required if you want to use encrypted passwords. You have to pull this directory from either FreeBSD
Odd crash
>Jun 16 01:10:03 binary /kernel: microuptime() went backwards (23115.1781232 -> >23115,1486749) >Jun 16 01:10:03 binary /kernel: microuptime() went backwards (23115.1781232 -> >23115,1487088) And so on; it caused the system not to respond at all over the network (not sure about the console, I was just getting console output from a colo). Any ideas as to what would cause this? binary% uname -a FreeBSD binary.databits.net 4.0-STABLE FreeBSD 4.0-STABLE #0: Mon Jun 12 12:56:57 EDT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/BINARY i386 binary% Thanks! [ please cc: me, as I am not on this list ] -- Pete Fritchman <[EMAIL PROTECTED]> Databits Network Services, Inc http://www.databits.net finger: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
ATA DMA Problem
I've discovered an interesting problem as follows: Jun 17 05:16:59 cwsys /kernel: ad2: HARD READ ERROR blk# 4999424ata1-master: WAR NING: WAIT_READY active=ATA_ACTIVE_ATA Jun 17 05:16:59 cwsys /kernel: ad2: DMA problem fallback to PIO mode Jun 17 05:16:59 cwsys last message repeated 15 times The IDE devices attached to the system are: Jun 17 07:06:31 cwsys /kernel: ata0: at 0x1f0 irq 14 on atapci0 Jun 17 07:06:31 cwsys /kernel: ata1: at 0x170 irq 15 on atapci0 Jun 17 07:06:32 cwsys /kernel: ad0: 2014MB [4092/16/63] at ata0-m aster using WDMA2 Jun 17 07:06:32 cwsys /kernel: ad2: 2441MB [4960/16/63] at ata1-m aster using WDMA2 At first glance it looks like a bad block on disk. However, the errors only occur when running: dd if=/dev/ad0 of=/dev/null bs=1024k After running the Western Digital wddiag scan three times, without indication of error, and running: dd if=/dev/ad0 of=/dev/null (notice no bs=1024k) ... also without error. ... and running the dd with bs=1024k a number of times subsequent to this, the above error can be repeated 100% of the time when dd is run with bs=1024k specified. (Just a hunch but bs=64k would probably not cause the error -- will have to test that theory out). Otherwise the system and disk have been running nicely, so this is not a major issue. It is an interesting problem of which I don't have too much data collected and therefore feel awkward submitting a PR regarding this. I suspect one of the following: 1. Possible heat problem, bs=1024k probably drives the disk harder than the default bs=512. Interestingly, 3.4 didn't experience this problem. Maybe 4.0's new ATA driver is more efficient, driving the disk harder and causing the disk's controller board to run a little hotter than it did under 3.4. (most) 2. Possible disk/controller/DMA timing issue, e.g. hardware problem excluding HDA failure. 3. Possible FreeBSD ATA/DMA driver bug. (least) I'm running 4.0S as of May 27. Any comments would be welcome. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: [EMAIL PROTECTED] Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
xmms & jumpy sound [solved!]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 For those of you out there like me, who had sound jump all over the place whenever you turned on the mixer in xmms, 1.2.0 fixes that somehow. We now have a mixer again! (I tried w/ esound & oss output, both worked) Cheers :) Matt Heckaman [EMAIL PROTECTED] http://www.lucida.qc.ca -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (FreeBSD) Comment: http://www.lucida.qc.ca/pgp iD8DBQE5S/m8dMMtMcA1U5ARAgO+AKDV5kpbeoYf76BfC6exqLPE4rMxIwCeJZZL 5IXRzaeGxboLTlBJ6wECXVw= =5ioU -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: kerneld for FreeBSD
"Daniel C. Sobral" <[EMAIL PROTECTED]> writes: > R Joseph Wright wrote: > > > > Since when? Any that I've ever needed had to be compiled into the > > kernel. > > Since when is a tough question, but since 4.0, I think, for NICs, and > certainly at least 3.x, maybe even 2.x, for fs. cvs log ifconfig.c says revision 1.44 which is after RELENG_3_4_0_RELEASE ... RELENG_4_0_0_RELEASE: 1.51 ... RELENG_3_4_0_RELEASE: 1.38.2.2 ... revision 1.44 date: 1999/09/20 07:58:08; author: msmith; state: Exp; lines: +45 -1 If we don't appear to have a module loaded supporting the interface we're about to operate on, try to load one. Don't complain if the load fails, and always press on regardless (there may not be a module suitable or required). With the renaming of the PCI ethernet driver modules and the addition of appropriate miibus dependancies on those modules that need it, it is now no longer necessary to compile many ethernet drivers into the kernel; they will be loaded on demand the first time they are ifconfig'ed. Inspiration from: mount cvs log mount_ufs.c says revision 1.2 which is before ALPHA_2_0 ! so, from the beginning. ... ALPHA_2_0: 1.4.0.2 bsd_44_lite: 1.1.1.1 ... revision 1.2 date: 1994/09/22 02:07:33; author: wollman; state: Exp; lines: +16 -1 Use getvfs* functions to map between VFS types and names. Automatically load UFS if it is not present but is loadable. (This won't happen now, but could happen if we fix NFS diskless support.) Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "no-spam." pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "no-spam." to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Woah, what happened to the snaps?
Anyone know what's happened to the 4.x-stable snapshots? The last one on releng4.FreeBSD.org is dated June 8th, which is 9 days ago. :( -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
