From owner-freebsd-stable Sun Nov 11 2:42:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by hub.freebsd.org (Postfix) with SMTP id 1D52737B417 for ; Sun, 11 Nov 2001 02:42:45 -0800 (PST) Received: (qmail 72129 invoked from network); 11 Nov 2001 10:42:17 -0000 Received: from 213-84-202-101.adsl.xs4all.nl (HELO jak.nl) (213.84.202.101) by jak.nl with SMTP; 11 Nov 2001 10:42:17 -0000 Message-ID: <3BEE56A2.2000305@jak.nl> Date: Sun, 11 Nov 2001 11:44:50 +0100 From: Arjan Knepper Organization: JAK++ Software Development B.V. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Tor.Egge@cvsup.no.freebsd.org Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FBSD4.4-STABLE SMP broken! References: <20011110172005.J999-100000@klima.physik.uni-mainz.de> <20011111003641B.tegge@cvsup.no.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear Tor, Do you think this is related to the problems below with a dual PIII-933 Mhz Dell PowerEdge 2550 (serverworks chipset)? panic: rslock: cpu: 1, addr:0xc0307228, lock: 0x01000001 mp_lock = 01000002; cpuid =1; lapic.id = 00000000 boot() called on cpu#1 Thanks Arjan Tor.Egge@cvsup.no.freebsd.org wrote: >>I did a cvsupdate today, the target machine was running >>stable for the last four days. >> >>After the update and make world today, the system run a few minutes and then >>get stuck ... no keyboard input, nothing, no network response. >> > >Sleeping while holding a simplelock can be fatal on an SMP machine. >If the other CPU tries to obtain the simplelock then you get a hang. >If the same CPU tries to obtain the simplelock then you get a panic. > >One example is vinvalbuf() holding the vnode interlock while calling >vm_object_page_remove() (which might block), cf. PR 26224. > >For 4.4-STABLE, it might make sense to just define some simplelock >operations to nops also under SMP. All relevant code is already >serialized by mp_lock and further lock pushdown is unlikely to occur >on that branch. The only effect of these simplelock operations under >4.4-STABLE SMP is a hang or panic when the locking protocol is >violated. > >The enclosed patch will break 3rd party device drivers that use fast >interrupts and simple_lock() to serialize access to shared resources. >I don't know about any such device drivers. > >You'll need to add > > options SIMPLELOCK_NULL > >to the relevant kernel config file and recompile the kernel for the >patch to have any effect. > >- Tor Egge > > >------------------------------------------------------------------------ > >Index: sys/conf/options >=================================================================== >RCS file: /home/ncvs/src/sys/conf/options,v >retrieving revision 1.191.2.37 >diff -u -r1.191.2.37 options >--- sys/conf/options 3 Nov 2001 01:41:07 -0000 1.191.2.37 >+++ sys/conf/options 10 Nov 2001 23:29:19 -0000 >@@ -361,7 +363,8 @@ > INVARIANT_SUPPORT opt_global.h > INVARIANTS opt_global.h > SIMPLELOCK_DEBUG opt_global.h >+SIMPLELOCK_NULL opt_global.h > VFS_BIO_DEBUG opt_global.h > > # These are VM related options > VM_KMEM_SIZE opt_vm.h >Index: sys/i386/include/lock.h >=================================================================== >RCS file: /home/ncvs/src/sys/i386/include/Attic/lock.h,v >retrieving revision 1.11.2.2 >diff -u -r1.11.2.2 lock.h >--- sys/i386/include/lock.h 30 Sep 2000 02:49:34 -0000 1.11.2.2 >+++ sys/i386/include/lock.h 10 Nov 2001 23:29:19 -0000 >@@ -170,6 +170,18 @@ > extern struct simplelock mcount_lock; > > #if !defined(SIMPLELOCK_DEBUG) && MAXCPU > 1 >+ >+#ifdef SIMPLELOCK_NULL >+ >+/* On SMP systems, mp_lock is used for the serialization */ >+ >+#define NULL_SIMPLELOCKS >+#define simple_lock_init(alp) >+#define simple_lock(alp) >+#define simple_lock_try(alp) (1) /* always succeeds */ >+#define simple_unlock(alp) >+ >+#else > /* > * This set of defines turns on the real functions in i386/isa/apic_ipl.s. > */ >@@ -177,6 +189,8 @@ > #define simple_lock(alp) s_lock(alp) > #define simple_lock_try(alp) s_lock_try(alp) > #define simple_unlock(alp) s_unlock(alp) >+ >+#endif > > #endif /* !SIMPLELOCK_DEBUG && MAXCPU > 1 */ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 3:12:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp4.cluster.oleane.net (smtp4.cluster.oleane.net [195.25.12.62]) by hub.freebsd.org (Postfix) with ESMTP id BA74637B419 for ; Sun, 11 Nov 2001 03:12:15 -0800 (PST) Received: from diabolic-cow.chatgris.net (d96df453.fsp.oleane.fr [217.109.244.83]) by smtp4.cluster.oleane.net with ESMTP id fABBCC416032 for ; Sun, 11 Nov 2001 12:12:13 +0100 (CET) Received: by diabolic-cow.chatgris.net (Postfix, from userid 1000) id E8FFC97; Sun, 11 Nov 2001 12:10:47 +0100 (CET) Date: Sun, 11 Nov 2001 12:10:47 +0100 From: =?iso-8859-1?Q?R=E9mi_Guyomarch?= To: freebsd-stable@FreeBSD.ORG Subject: Re: 4.4-RELEASE real time scheduling broke? Message-ID: <20011111121047.A357@diabolic-cow.chatgris.net> References: <20011110154957.V14356-100000@coredump.scriptkiddie.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20011110154957.V14356-100000@coredump.scriptkiddie.org>; from lamont@scriptkiddie.org on Sat, Nov 10, 2001 at 03:53:19PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Nov 10, 2001 at 03:53:19PM -0800, Lamont Granquist wrote: > > xmms has been popping a lot more under 4.4-RELEASE and i just noticed that > is not running with real-time priority anymore according to top, even > though it should be configured to do so. > > i've upgraded xmms recently though, so i'm not sure who to blame (and not > really familiar enough with real time scheduling to know what i need to do > to test it out...) System is fine, the xmms port is broken wrt real-time priority. -- Rémi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 3:21:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from newmail.spectraweb.ch (eagle.spectraweb.ch [194.158.230.44]) by hub.freebsd.org (Postfix) with ESMTP id 9582537B419 for ; Sun, 11 Nov 2001 03:21:33 -0800 (PST) Received: from [172.20.0.2] (194.230.203.76) by newmail.spectraweb.ch for ; 11 Nov 2001 12:21:32 +0100 Mime-Version: 1.0 X-Sender: bsiege@pop.spectraweb.ch Message-Id: In-Reply-To: <3BED3FC8.D3AEEEB2@herbelot.com> References: <006201c169d7$80752310$c80aa8c0@lfarr> <3BED3FC8.D3AEEEB2@herbelot.com> Date: Sun, 11 Nov 2001 12:16:57 +0100 To: freebsd-stable@FreeBSD.ORG From: Beat Siegenthaler Subject: KDE2 upgrade pains Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >attempts to upgrade KDE2 via source and portupgrade left >the machine with an unbuildable parts of KDE, due to incompatible >automake/autoconf versions Is there somebody who can solve this issue...??? Wanna back my KDE ;-))) -- Gruss, Sigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 3:55:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from herbelot.dyndns.org (d211.dhcp212-198-26.noos.fr [212.198.26.211]) by hub.freebsd.org (Postfix) with ESMTP id 85F5237B41C for ; Sun, 11 Nov 2001 03:55:31 -0800 (PST) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id NAA38130; Sun, 11 Nov 2001 13:23:50 +0100 (CET) (envelope-from thierry@herbelot.com) Message-ID: <3BEE672D.99CF92DC@herbelot.com> Date: Sun, 11 Nov 2001 12:55:25 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: Beat Siegenthaler Cc: freebsd-stable@FreeBSD.ORG Subject: Re: KDE2 upgrade pains References: <006201c169d7$80752310$c80aa8c0@lfarr> <3BED3FC8.D3AEEEB2@herbelot.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Beat Siegenthaler wrote: > > >attempts to upgrade KDE2 via source and portupgrade left > >the machine with an unbuildable parts of KDE, due to incompatible > >automake/autoconf versions > > Is there somebody who can solve this issue...??? Wanna back my KDE ;-))) my solution was a clean re-install with a -Stable snapshot and accompanying binary packages (but I've got a cable connection ...) and KDE 2.2.1 is a very good surprise -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 4:46:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by hub.freebsd.org (Postfix) with ESMTP id C704D37B425 for ; Sun, 11 Nov 2001 04:46:29 -0800 (PST) Received: from dragon.stack.nl (dragon.stack.nl [131.155.141.104]) by mailhost.stack.nl (Postfix) with ESMTP id 2DC4B3D828; Sun, 11 Nov 2001 13:46:28 +0100 (CET) Received: by dragon.stack.nl (Postfix, from userid 1600) id A4D3399C8; Sun, 11 Nov 2001 13:45:02 +0100 (CET) Date: Sun, 11 Nov 2001 13:45:02 +0100 From: Dean Strik To: Marcel Prisi Cc: stable@FreeBSD.ORG Subject: Re: What NIC to choose ? Message-ID: <20011111124502.GA10461@dragon.stack.nl> References: <019a01c16629$4b151650$8d01a8c0@gastroleader.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <019a01c16629$4b151650$8d01a8c0@gastroleader.com> User-Agent: Mutt/1.3.23.1i X-Editor: VIM Rulez! http://www.vim.org/ X-MUD: Outerspace - telnet://mud.stack.nl:3333 X-Really: Yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Marcel Prisi wrote: > Hi all ! > > After having loads of trouble with Intel Etherexpress, Netgear, and others > NIC, what card REALLY work on FreeBSD ? This is a rather late reply, but I'd like to share a bit about a problem we had with Intel EtherExpress Pro 100. We had a few connected to a Cisco Fasthub. We found that since bridging was enabled on one of these boxen, all computers with the intel cards completely 'netdied' after seemingly arbitrary periods (days). Computers with NICs from 3com or other manufacturers were not affected. Later problems also occurred in the same configuration (connected to a cisco hub). The bridging machine (FreeBSD) also is an IPv6 router, and IPv6 connections through the box went fine.. except to/from boxen with the Intel cards. All the boxen with these intel cards run FreeBSD-STABLE, so it's hard to say if this problem only occurs with FreeBSD. -- Dean C. Strik Eindhoven University of Technology dean@stack.nl | dean@ipnet6.org | http://www.ipnet6.org/ "This isn't right. This isn't even wrong." -- Wolfgang Pauli To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 6:37:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id 9F8E437B42A; Sun, 11 Nov 2001 06:37:30 -0800 (PST) Date: Sun, 11 Nov 2001 06:37:30 -0800 From: John De Boskey To: Stable List Subject: "disklabel -rw ar0 auto" breaks HPT raid0+1 Message-ID: <20011111063730.A3860@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I have an ABIT KT7A-RAID motherboard with the builtin HPT370 controller: atapci1: port 0xe800-0xe8ff,0xe400-0xe403,0 ar0: 190792MB [24322/255/63] subdisks: ad6: 95396MB [193821/16/63] at ata3-master UDMA100 ad5: 95396MB [193821/16/63] at ata2-slave UDMA100 ad4: 95396MB [193821/16/63] at ata2-master UDMA100 ad7: 95396MB [193821/16/63] at ata3-slave UDMA100 After setting up the raid (stripes are quick, mirror takes 4+ hours) and booting the machine I get the above. The disklabel command: disklabel -rw ar0 auto creates and writes a label. newfs -c 22 /dev/ar0c writes a filesystem on to the disk which can then be mounted and used. However, when the system is rebooted, the HPT controller says the stripe has been broken and needs to be re-synced. After re-syncing the array comes up fine and continues to work correctly across reboots with no problems. Having debugged this a few times, it appears that disklabel is writing data over the control information at the head of the disks. Looking at the ata-raid.c source code, it appears to be reserving 10 blocks. Am I stuck simply increasing this number until the problem goes away or is there any real information on the control structures being written out? I have only tested this on a -stable system, though from looking at the code -current will probably have the same issues. As a side note, it takes 4+ hours to 'sync' the 2 stripes into a mirror from the HPT bios. If we understand the control structures well enough, it would seem nice if we could have an ioctl interface to force the raid into normal mode from broken mode since there really isn't any data that needs to be sync'd yet... The motherboard has the latest bios installed. Comments? Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 8: 0:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (Postfix) with ESMTP id A880B37B41E for ; Sun, 11 Nov 2001 08:00:24 -0800 (PST) Received: from d1o982.telia.com (d1o982.telia.com [213.65.24.241]) by mailb.telia.com (8.11.6/8.11.6) with ESMTP id fABG0Je11610 for ; Sun, 11 Nov 2001 17:00:23 +0100 (CET) Received: from there (h247n2fls34o982.telia.com [213.67.61.247]) by d1o982.telia.com (8.10.2/8.10.1) with SMTP id fABG0Ib12090 for ; Sun, 11 Nov 2001 17:00:18 +0100 (CET) Message-Id: <200111111600.fABG0Ib12090@d1o982.telia.com> Content-Type: text/plain; charset="iso-8859-1" From: Vidor Demeter To: FreeBSD-STABLE@FreeBSD.ORG Subject: Power-off Date: Sun, 11 Nov 2001 17:00:16 +0100 X-Mailer: KMail [version 1.3] References: <20011109215521.A701@laptop.lambertfam.org> <20011109202433.A83759@hollin.btc.adaptec.com> <20011110010048.B1317@laptop.lambertfam.org> In-Reply-To: <20011110010048.B1317@laptop.lambertfam.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Is there any possibility to auto power-off the PC after a shutdown command? Just like in Linux or Win9x... Regards Vidor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 8: 9:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from D00015.dialonly.kemerovo.su (www2.svzserv.kemerovo.su [213.184.65.86]) by hub.freebsd.org (Postfix) with ESMTP id 438E837B41B; Sun, 11 Nov 2001 08:09:15 -0800 (PST) Received: (from eugen@localhost) by D00015.dialonly.kemerovo.su (8.11.6/8.11.4) id fABG8Hw02428; Sun, 11 Nov 2001 23:08:17 +0700 (KRAT) (envelope-from eugen) Date: Sun, 11 Nov 2001 23:08:17 +0700 From: Eugene Grosbein To: stable@freebsd.org Cc: hackers@freebsd.org Subject: kern.vm.kmem.size Message-ID: <20011111230817.A2325@grosbein.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! I'm trying to test and tune speed of freebsd's filesystem in many aspects. I run recent FreeBSD 4.4-STABLE with new dirprefs code, read tuning(7), newfs'd my FS, turned softupdates on, have UFS_DIRHASH kernel option. Also, I've read DIRHASH kernel code source. It seems that efficiency of DIRHASH greatly depends of kernel memory size (and some experiments approve this). loader(8) describes tunnable parameter kern.vm.kmem.size which overrides default size of kernel memory. Increasing this helps DIRHASH not to fall back to linear search. But how can I see exact amount of used kernel memory? Default 12M does not seem to be suitable for my tasks and I would like to increase this but cannot estimate right value. Perhaps, sysctl vm.zone might help but I do not know how to interpret its output. All that I need is a % of used kernel memory. Eugene Grosbein P.S. Please CC: me when replying. Thank you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 8:10:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.136.200]) by hub.freebsd.org (Postfix) with ESMTP id 3292837B41A for ; Sun, 11 Nov 2001 08:10:42 -0800 (PST) Received: from vpn64.ece.cmu.edu (VPN10.ECE.CMU.EDU [128.2.138.10]) (authenticated) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id fABGAcl01567; Sun, 11 Nov 2001 11:10:38 -0500 (EST) Date: Sun, 11 Nov 2001 11:10:35 -0500 From: "Brandon S. Allbery KF8NH" To: Vidor Demeter , FreeBSD-STABLE@FreeBSD.ORG Subject: Re: Power-off Message-ID: <6940000.1005495034@vpn64.ece.cmu.edu> In-Reply-To: <200111111600.fABG0Ib12090@d1o982.telia.com> References: <20011109215521.A701@laptop.lambertfam.org> <20011109202433.A83759@hollin.btc.adaptec.com> <20011110010048.B1317@laptop.lambertfam.org> <200111111600.fABG0Ib12090@d1o982.telia.com> X-Mailer: Mulberry/2.1.0 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday, November 11, 2001 17:00:16 +0100, Vidor Demeter wrote: +----- | Is there any possibility to auto power-off the PC after a | shutdown command? Just like in Linux or Win9x... +--->8 "shutdown -p now" works for me. -- brandon s. allbery [os/2][linux][solaris][freebsd] allbery@kf8nh.apk.net system administrator [JAPH][WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university [linux: proof of the million monkeys theory] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 8:12:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from phb.avic.dk (phb.avic.dk [212.54.72.25]) by hub.freebsd.org (Postfix) with SMTP id 997C837B41B for ; Sun, 11 Nov 2001 08:12:08 -0800 (PST) Received: from fallesen.dk (jf@dilbert.avic.dk [212.54.72.26]) by phb.avic.dk (8.11.6/8.11.6/PHB/15) with ESMTP id fABGC7D22039 for ; Sun, 11 Nov 2001 17:12:07 +0100 (CET) Message-ID: <3BEEA37B.79D2466F@fallesen.dk> Date: Sun, 11 Nov 2001 17:12:43 +0100 From: Jens Fallesen Organization: AVIC X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.3-STABLE i386) X-Accept-Language: da, en MIME-Version: 1.0 Cc: FreeBSD-STABLE@FreeBSD.ORG Subject: Re: Power-off References: <20011109215521.A701@laptop.lambertfam.org> <20011109202433.A83759@hollin.btc.adaptec.com> <20011110010048.B1317@laptop.lambertfam.org> <200111111600.fABG0Ib12090@d1o982.telia.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Vidor Demeter wrote: > Is there any possibility to auto power-off the PC after a > shutdown command? Just like in Linux or Win9x... Give the halt or shutdown command a -p and see what happens. Of course you must have power management enable in your kernel for this to work. Look for the apm0 device. -- Jens Fallesen O- Hedegaardsvej 41 st th, 2300 Copenhagen S, Denmark Phone: (+45) 32 86 18 99 * Fax: (+45) 32 86 17 99 CCIE #5470 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 8:44:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from johnson.mail.mindspring.net (johnson.mail.mindspring.net [207.69.200.177]) by hub.freebsd.org (Postfix) with ESMTP id BFBD737B419 for ; Sun, 11 Nov 2001 08:44:30 -0800 (PST) Received: from netcom1.netcom.com (pool0206.cvx4-bradley.dialup.earthlink.net [209.178.146.206]) by johnson.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id LAA20638; Sun, 11 Nov 2001 11:44:24 -0500 (EST) Received: by netcom1.netcom.com (Postfix, from userid 1000) id DA89B13414; Sun, 11 Nov 2001 08:44:21 -0800 (PST) From: Mike Harding To: sigi@spectraweb.ch Cc: freebsd-stable@FreeBSD.ORG In-reply-to: (message from Beat Siegenthaler on Sun, 11 Nov 2001 12:16:57 +0100) Subject: Re: KDE2 upgrade pains References: <006201c169d7$80752310$c80aa8c0@lfarr> <3BED3FC8.D3AEEEB2@herbelot.com> Message-Id: <20011111164421.DA89B13414@netcom1.netcom.com> Date: Sun, 11 Nov 2001 08:44:21 -0800 (PST) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Portupdgrade has 'issues' - do a make clean on kde, capture the output, delete the listed ports, slash and burn, build a new kde. I have spend more time trying to fix the occasional problem with portupgrade than saves. - Mike H. X-Sender: bsiege@pop.spectraweb.ch Date: Sun, 11 Nov 2001 12:16:57 +0100 From: Beat Siegenthaler Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.ORG >attempts to upgrade KDE2 via source and portupgrade left >the machine with an unbuildable parts of KDE, due to incompatible >automake/autoconf versions Is there somebody who can solve this issue...??? Wanna back my KDE ;-))) -- Gruss, Sigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 9:38:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from server.highperformance.net (ip30.gte4.rb1.bel.nwlink.com [209.20.215.30]) by hub.freebsd.org (Postfix) with ESMTP id 2F3A137B425 for ; Sun, 11 Nov 2001 09:38:14 -0800 (PST) Received: from localhost (jcw@localhost) by server.highperformance.net (8.11.6/8.11.3) with ESMTP id fABHc6i37287 for ; Sun, 11 Nov 2001 09:38:06 -0800 (PST) (envelope-from jcw@highperformance.net) Date: Sun, 11 Nov 2001 09:38:05 -0800 (PST) From: "Jason C. Wells" X-Sender: jcw@server.highperformance.net To: FreeBSD-stable Subject: config - unknown option "NFSKERB" Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The exports(5) page tells me that I must have the option "NFSKERB" compiled to use kerberos authentication for NFS. I get this error: # config SERVER SERVER:29: unknown option "NFSKERB" # LINT doesn't document this option. The #ifdefs do exist in sys/nfs. What can I do to get a NFSKERB kernel to compile? Thanks, Jason C. Wells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 11:31: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.noos.fr (verlaine.noos.net [212.198.2.73]) by hub.freebsd.org (Postfix) with ESMTP id 3309437B416 for ; Sun, 11 Nov 2001 11:31:06 -0800 (PST) Received: (qmail 8594663 invoked by uid 0); 11 Nov 2001 19:31:04 -0000 Received: from unknown (HELO gits.dyndns.org) ([212.198.229.145]) (envelope-sender ) by 212.198.2.73 (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 11 Nov 2001 19:31:04 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.6/8.11.6) id fABJV3j10940; Sun, 11 Nov 2001 20:31:03 +0100 (CET) (envelope-from root) Message-Id: <200111111931.fABJV3j10940@gits.dyndns.org> Subject: Re: "disklabel -rw ar0 auto" breaks HPT raid0+1 In-Reply-To: <20011111063730.A3860@FreeBSD.org> To: John De Boskey Date: Sun, 11 Nov 2001 20:31:03 +0100 (CET) Cc: Stable List Reply-To: clefevre@citeweb.net From: Cyrille Lefevre Organization: ACME X-Face: X-Mailer: ELM [version 2.4ME+ PL95a (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John De Boskey wrote: > Hi, > > I have an ABIT KT7A-RAID motherboard with the builtin > HPT370 controller: > > atapci1: port 0xe800-0xe8ff,0xe400-0xe403,0 > > ar0: 190792MB [24322/255/63] subdisks: > ad6: 95396MB [193821/16/63] at ata3-master UDMA100 > ad5: 95396MB [193821/16/63] at ata2-slave UDMA100 > ad4: 95396MB [193821/16/63] at ata2-master UDMA100 > ad7: 95396MB [193821/16/63] at ata3-slave UDMA100 > > > After setting up the raid (stripes are quick, mirror takes 4+ hours) > and booting the machine I get the above. > > The disklabel command: > > disklabel -rw ar0 auto > > creates and writes a label. > > newfs -c 22 /dev/ar0c > > writes a filesystem on to the disk which can then be mounted and used. > However, when the system is rebooted, the HPT controller says the stripe > has been broken and needs to be re-synced. After re-syncing the array comes > up fine and continues to work correctly across reboots with no problems. > > Having debugged this a few times, it appears that disklabel is writing > data over the control information at the head of the disks. Looking at the > ata-raid.c source code, it appears to be reserving 10 blocks. Am I stuck > simply increasing this number until the problem goes away or is there > any real information on the control structures being written out? as I understand it, you are partitionning your drive in "dangerously dedicated mode" which is the wrong way to go. to avoid this problem you have to partition your drive using fdisk and to create your BSD slices w/in MSDOS partitions. maybe I'm wrong, but I'm almost sure I'm not. Cyrille. -- Cyrille Lefevre mailto:clefevre@citeweb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 12:33:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from itouch.co.nz (itouch.co.nz [203.99.66.188]) by hub.freebsd.org (Postfix) with ESMTP id DEB9F37B418 for ; Sun, 11 Nov 2001 12:33:55 -0800 (PST) Received: from jonc.itouch ([192.168.2.21]) by itouch.co.nz with esmtp (Exim 3.33 #1) id 1631Ih-0006gH-00; Mon, 12 Nov 2001 09:33:55 +1300 Received: (from jonc@localhost) by jonc.itouch (8.11.6/8.11.6) id fABKXpr48206; Mon, 12 Nov 2001 09:33:51 +1300 (NZDT) (envelope-from jonc) Date: Mon, 12 Nov 2001 09:33:51 +1300 From: Jonathan Chen To: Matthew Dillon Cc: Galen Sampson , freebsd-stable@freebsd.org Subject: Re: KDE init [was RE: DCOP server problem...] Message-ID: <20011112093351.C47998@jonc.itouch> References: <20011109180124.31471.qmail@web14103.mail.yahoo.com> <200111100718.fAA7I9522856@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200111100718.fAA7I9522856@apollo.backplane.com>; from dillon@apollo.backplane.com on Fri, Nov 09, 2001 at 11:18:09PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Nov 09, 2001 at 11:18:09PM -0800, Matthew Dillon wrote: [...] > I'm having weird problems with kde2 as well.. it keeps screwing up > the fonts. It forgets about font families, changes my defaults, and > does all sorts of other nasty things. There's some wierd interaction with KDE's artsd daemon and the fonts. I've discovered that if artsd isn't running, I get all my fonts; but they go away when its active... -- Jonathan Chen Once is dumb luck. Twice is coincidence. Three times and Somebody Is Trying To Tell You Something. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 13:17:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1124E37B419; Sun, 11 Nov 2001 13:17:41 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fABLHaB47695; Sun, 11 Nov 2001 13:17:36 -0800 (PST) (envelope-from dillon) Date: Sun, 11 Nov 2001 13:17:36 -0800 (PST) From: Matthew Dillon Message-Id: <200111112117.fABLHaB47695@apollo.backplane.com> To: Cyrille Lefevre Cc: John De Boskey , Stable List Subject: Re: "disklabel -rw ar0 auto" breaks HPT raid0+1 References: <200111111931.fABJV3j10940@gits.dyndns.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG There is a section near the end of the 'disklabel' manual page that describes how to partition a disk with a real slice entry instead of dangerously dedicated mode. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 13:21:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id E4FEB37B405 for ; Sun, 11 Nov 2001 13:21:34 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fABLLWu47758; Sun, 11 Nov 2001 13:21:32 -0800 (PST) (envelope-from dillon) Date: Sun, 11 Nov 2001 13:21:32 -0800 (PST) From: Matthew Dillon Message-Id: <200111112121.fABLLWu47758@apollo.backplane.com> To: "Frank J. Eigler" Cc: "FreeBSD" Subject: Re: 4.4 - X windows starts for root only References: <001901c16a34$12e7f680$0101a8c0@e1> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Hi, : :I installed 4.4 but X windows can be started for root only. Try running 'xdm' as root, then login on the X logi nwindow as yourself. X is not installed suid for security reasons so it cannot be run directly from a user login. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 13:35:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 08D5237B405; Sun, 11 Nov 2001 13:35:09 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fABLYXK47890; Sun, 11 Nov 2001 13:34:33 -0800 (PST) (envelope-from dillon) Date: Sun, 11 Nov 2001 13:34:33 -0800 (PST) From: Matthew Dillon Message-Id: <200111112134.fABLYXK47890@apollo.backplane.com> To: Nate Williams Cc: stable@FreeBSD.ORG, jayanth@FreeBSD.ORG Subject: Re: TCP NewReno causing wild performance fluctuations References: <15340.20191.441648.662113@caddis.yogotech.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I think you should MFC this, Nate. -Matt Matthew Dillon :We've been using FreeBSD boxes as our reference ftp servers at work, and :because of the recent security issues, I've went through and updated a :number of our public boxes from 3.x -> 4.4. : :However, we're seeing significant variations in ftp throughput from :boxes that are directly connected on the lan segment. If I disable the :New Reno code, things go back to normal (ie; no fluctuations). : :I went through the logfiles, and it turns out there has been one fix to :the code that hasn't been merged into stable. : :Rev1.139 in tcp_input.c has not (yet) been merged into -stable. :... : :I hand-merged this change back onto my box, installed a new kernel, and :now in my *very* minor testing things appear to be more normal. My :question is should this fix be merged into stable, and would the lack of :this bugfix explain my performance results? : :Unfortunately, I don't haven't gotten any tcpdump outputs to analyze :what was going on, but I didn't want this bugfix to slip through the :cracks. : :Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 13:36: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9301337B419 for ; Sun, 11 Nov 2001 13:36:07 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fABLa5d47917; Sun, 11 Nov 2001 13:36:05 -0800 (PST) (envelope-from dillon) Date: Sun, 11 Nov 2001 13:36:05 -0800 (PST) From: Matthew Dillon Message-Id: <200111112136.fABLa5d47917@apollo.backplane.com> To: Vidor Demeter Cc: freebsd-stable@FreeBSD.ORG Subject: Re: DCOP server problem... References: <200111091204.fA9C4nb02201@d1o982.telia.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Hi, : :I have some problems when I try to start Xwindows as a user: :I get an error message as: "DCOP-server is not running" :After a few trying to start Xwindows it starts, baut when I close it :it shows some error messages. :If I start X as root everything is right! :Can somebody help me out ? :Best regards Vidor KDE is broken. It creates /tmp/.ICE-unix as the user logging into the X session. Then if you login as another user later on it tries to use the same directory and of course cannot do anything. rm -rf /tmp/.ICE-unix and try again. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 14:18: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.noos.fr (lafontaine.noos.net [212.198.2.72]) by hub.freebsd.org (Postfix) with ESMTP id 95DA037B419 for ; Sun, 11 Nov 2001 14:18:01 -0800 (PST) Received: (qmail 96645886 invoked by uid 0); 11 Nov 2001 22:18:00 -0000 Received: from unknown (HELO gits.dyndns.org) ([212.198.229.145]) (envelope-sender ) by 212.198.2.72 (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 11 Nov 2001 22:18:00 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.6/8.11.6) id fABMHw017887; Sun, 11 Nov 2001 23:17:58 +0100 (CET) (envelope-from root) Message-Id: <200111112217.fABMHw017887@gits.dyndns.org> Subject: Re: "disklabel -rw ar0 auto" breaks HPT raid0+1 In-Reply-To: <200111112117.fABLHaB47695@apollo.backplane.com> To: Matthew Dillon Date: Sun, 11 Nov 2001 23:17:58 +0100 (CET) Cc: John De Boskey , Stable List Reply-To: clefevre@citeweb.net From: Cyrille Lefevre Organization: ACME X-Face: X-Mailer: ELM [version 2.4ME+ PL95a (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: > There is a section near the end of the 'disklabel' manual page that > describes how to partition a disk with a real slice entry instead of > dangerously dedicated mode. are you talking about the "BUG" section ? it only say that disklabel doesn't clobber the partition table. the problem is that it overwrite the following 15 sectors w/ boot2 while the first 10 sectors are used by the RAID hardware... do you see the problem. using fdisk, disklabel writes it's boot informations starting at sector 64 since the first half cylinder is reserved by fdisk. so, it doesn't clobber anything. is this explanation more clear ? Cyrille. -- Cyrille Lefevre mailto:clefevre@citeweb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 14:52:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fep7.cogeco.net (smtp.cogeco.net [216.221.81.25]) by hub.freebsd.org (Postfix) with ESMTP id DAF2D37B41A for ; Sun, 11 Nov 2001 14:52:02 -0800 (PST) Received: from e1 (d150-160-195.home.cgocable.net [24.150.160.195]) by fep7.cogeco.net (Postfix) with SMTP id CB9C1291B5 for ; Sun, 11 Nov 2001 17:51:46 -0500 (EST) Message-ID: <002101c16b03$72146e20$0101a8c0@e1> Reply-To: "Frank J. Eigler" From: "Frank J. Eigler" To: "FreeBSD" Subject: Boot menu entries Date: Sun, 11 Nov 2001 17:51:48 -0500 Organization: Frank J. Eigler MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I haven't fixed it, but thanks for the replies to the start of X windows - root vs. other user question. I have another question. I have FreeBSD installed on a dual boot machine, and the boot menu is: F1: DOS F2: FreeBSD I would love to change the entries to something like: F1: Windows F2: UNIX Is there a file somewhere I can edit? Thanks, Frank -- Frank J. Eigler frank-eigler@usa.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 15:47:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id EF0A237B41C; Sun, 11 Nov 2001 15:47:36 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fABNlUS48412; Sun, 11 Nov 2001 15:47:30 -0800 (PST) (envelope-from dillon) Date: Sun, 11 Nov 2001 15:47:30 -0800 (PST) From: Matthew Dillon Message-Id: <200111112347.fABNlUS48412@apollo.backplane.com> To: Cyrille Lefevre Cc: John De Boskey , Stable List Subject: Re: "disklabel -rw ar0 auto" breaks HPT raid0+1 References: <200111112217.fABMHw017887@gits.dyndns.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :Matthew Dillon wrote: :> There is a section near the end of the 'disklabel' manual page that :> describes how to partition a disk with a real slice entry instead of :> dangerously dedicated mode. : :are you talking about the "BUG" section ? it only say that disklabel :doesn't clobber the partition table. the problem is that it overwrite :the following 15 sectors w/ boot2 while the first 10 sectors are used :by the RAID hardware... do you see the problem. using fdisk, disklabel :writes it's boot informations starting at sector 64 since the first :half cylinder is reserved by fdisk. so, it doesn't clobber anything. :is this explanation more clear ? : :Cyrille. :-- :Cyrille Lefevre mailto:clefevre@citeweb.net No, the EXAMPLES section. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 16:39:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 8503437B405 for ; Sun, 11 Nov 2001 16:39:12 -0800 (PST) Received: from cain.gsoft.com.au (root@localhost [127.0.0.1]) by cain.gsoft.com.au (8.11.6/8.11.6) with ESMTP id fAC0d0S45302; Mon, 12 Nov 2001 11:09:04 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <002101c16b03$72146e20$0101a8c0@e1> Date: Mon, 12 Nov 2001 11:08:58 +1030 (CST) From: "Daniel O'Connor" To: "Frank J. Eigler" Subject: RE: Boot menu entries Cc: FreeBSD Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 11-Nov-2001 Frank J. Eigler wrote: > I would love to change the entries to something like: > > F1: Windows > F2: UNIX > > Is there a file somewhere I can edit? You would need to edit the boot0 assembler and reinstall it.. ie /usr/src/sys/boot/i386/boot0/boot0.s Look at line 391. I have no idea if 'Windows' in there will fit or not though. Please don't complain to me if you manage to make your system unbootable after fiddling with this :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 16:55:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 12A7137B405; Sun, 11 Nov 2001 16:55:53 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fAC0vR803652; Sun, 11 Nov 2001 16:57:28 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200111120057.fAC0vR803652@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: clefevre@citeweb.net Cc: Matthew Dillon , John De Boskey , Stable List Subject: Re: "disklabel -rw ar0 auto" breaks HPT raid0+1 In-reply-to: Your message of "Sun, 11 Nov 2001 23:17:58 +0100." <200111112217.fABMHw017887@gits.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Nov 2001 16:57:27 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Matthew Dillon wrote: > > There is a section near the end of the 'disklabel' manual page that > > describes how to partition a disk with a real slice entry instead of > > dangerously dedicated mode. > > are you talking about the "BUG" section ? it only say that disklabel > doesn't clobber the partition table. the problem is that it overwrite > the following 15 sectors w/ boot2 while the first 10 sectors are used > by the RAID hardware... do you see the problem. using fdisk, disklabel > writes it's boot informations starting at sector 64 since the first > half cylinder is reserved by fdisk. so, it doesn't clobber anything. > is this explanation more clear ? The region owned by the firmware should *not* be visible to applications opening the device. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 17: 6:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.noos.fr (lafontaine.noos.net [212.198.2.72]) by hub.freebsd.org (Postfix) with ESMTP id D60A037B417 for ; Sun, 11 Nov 2001 17:06:21 -0800 (PST) Received: (qmail 96722400 invoked by uid 0); 12 Nov 2001 01:06:20 -0000 Received: from unknown (HELO gits.dyndns.org) ([212.198.229.145]) (envelope-sender ) by 212.198.2.72 (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 12 Nov 2001 01:06:20 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.6/8.11.6) id fAC16J324069; Mon, 12 Nov 2001 02:06:19 +0100 (CET) (envelope-from root) Message-Id: <200111120106.fAC16J324069@gits.dyndns.org> Subject: Re: "disklabel -rw ar0 auto" breaks HPT raid0+1 In-Reply-To: <200111112347.fABNlUS48412@apollo.backplane.com> To: Matthew Dillon Date: Mon, 12 Nov 2001 02:06:18 +0100 (CET) Cc: John De Boskey , Stable List Reply-To: clefevre@citeweb.net From: Cyrille Lefevre Organization: ACME X-Face: X-Mailer: ELM [version 2.4ME+ PL95a (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > : > :Matthew Dillon wrote: > :> There is a section near the end of the 'disklabel' manual page that > :> describes how to partition a disk with a real slice entry instead of > :> dangerously dedicated mode. > : > :are you talking about the "BUG" section ? it only say that disklabel > :doesn't clobber the partition table. the problem is that it overwrite > :the following 15 sectors w/ boot2 while the first 10 sectors are used > :by the RAID hardware... do you see the problem. using fdisk, disklabel > :writes it's boot informations starting at sector 64 since the first > :half cylinder is reserved by fdisk. so, it doesn't clobber anything. > :is this explanation more clear ? > > No, the EXAMPLES section. there is nothing in the "EXAMPLES" section which prevent to write the first 16 sectors if using the drive in `dangerously-dedicated' mode that is w/ no fdisk partition. Cyrille. -- Cyrille Lefevre mailto:clefevre@citeweb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 17:20: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3741737B405; Sun, 11 Nov 2001 17:20:05 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fAC1Jq448679; Sun, 11 Nov 2001 17:19:52 -0800 (PST) (envelope-from dillon) Date: Sun, 11 Nov 2001 17:19:52 -0800 (PST) From: Matthew Dillon Message-Id: <200111120119.fAC1Jq448679@apollo.backplane.com> To: Cyrille Lefevre Cc: John De Boskey , Stable List Subject: Re: "disklabel -rw ar0 auto" breaks HPT raid0+1 References: <200111120106.fAC16J324069@gits.dyndns.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :> :half cylinder is reserved by fdisk. so, it doesn't clobber anything. :> :is this explanation more clear ? :> :> No, the EXAMPLES section. : :there is nothing in the "EXAMPLES" section which prevent to write :the first 16 sectors if using the drive in `dangerously-dedicated' :mode that is w/ no fdisk partition. : :Cyrille. :-- :Cyrille Lefevre mailto:clefevre@citeweb.net The examples section, if you have a reasonably recent (4.3 or later I believe) system, shows you how to create a disklabel inside a slice (i.e. NOT dangerously dedicated), and shows you how to run fdisk to initialize a disk and then how to run disklabel to inintialize the slice. The sequence is something like: fdisk -BI da0 disklabel -w -r -B da0s1 auto disklabel -e da0s1 -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 17:29:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bsdone.bsdwins.com (www.bsdwins.com [192.58.184.33]) by hub.freebsd.org (Postfix) with ESMTP id C7E4437B419; Sun, 11 Nov 2001 17:29:34 -0800 (PST) Received: (from jwd@localhost) by bsdone.bsdwins.com (8.11.6/8.11.0) id fAC1TYO01027; Sun, 11 Nov 2001 20:29:34 -0500 (EST) (envelope-from jwd) Date: Sun, 11 Nov 2001 20:29:34 -0500 From: John De Boskey To: Mike Smith Cc: clefevre@citeweb.net, Matthew Dillon , Stable List Subject: Re: "disklabel -rw ar0 auto" breaks HPT raid0+1 Message-ID: <20011111202933.A940@bsdwins.com> References: <200111112217.fABMHw017887@gits.dyndns.org> <200111120057.fAC0vR803652@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200111120057.fAC0vR803652@mass.dis.org>; from msmith@FreeBSD.ORG on Sun, Nov 11, 2001 at 04:57:27PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Mike Smith's Original Message ----- > > Matthew Dillon wrote: > > > There is a section near the end of the 'disklabel' manual page that > > > describes how to partition a disk with a real slice entry instead of > > > dangerously dedicated mode. > > > > are you talking about the "BUG" section ? it only say that disklabel > > doesn't clobber the partition table. the problem is that it overwrite > > the following 15 sectors w/ boot2 while the first 10 sectors are used > > by the RAID hardware... do you see the problem. using fdisk, disklabel > > writes it's boot informations starting at sector 64 since the first > > half cylinder is reserved by fdisk. so, it doesn't clobber anything. > > is this explanation more clear ? > > The region owned by the firmware should *not* be visible to applications > opening the device. Thank you for stating the problem so succinctly. For the HPT controller, ata-raid.c reserves 10 blocks at the head of the physical raid and 10 blocks on all disks following the 1st. I want to put some trace code in to determine where disklabel is physically writing on the disk(s). I will also create a real slice entry tommorrow to determine if that avoids the problem. -John > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 18:57:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.noos.fr (aragon.noos.net [212.198.2.75]) by hub.freebsd.org (Postfix) with ESMTP id EC58B37B405 for ; Sun, 11 Nov 2001 18:57:26 -0800 (PST) Received: (qmail 52539866 invoked by uid 0); 12 Nov 2001 02:53:15 -0000 Received: from unknown (HELO gits.dyndns.org) ([212.198.229.145]) (envelope-sender ) by 212.198.2.75 (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 12 Nov 2001 02:53:15 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.6/8.11.6) id fAC2rEq28982; Mon, 12 Nov 2001 03:53:14 +0100 (CET) (envelope-from root) Message-Id: <200111120253.fAC2rEq28982@gits.dyndns.org> Subject: Re: "disklabel -rw ar0 auto" breaks HPT raid0+1 In-Reply-To: <200111120119.fAC1Jq448679@apollo.backplane.com> To: Matthew Dillon Date: Mon, 12 Nov 2001 03:53:14 +0100 (CET) Cc: John De Boskey , Stable List Reply-To: clefevre@citeweb.net From: Cyrille Lefevre Organization: ACME X-Face: X-Mailer: ELM [version 2.4ME+ PL95a (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :> :half cylinder is reserved by fdisk. so, it doesn't clobber anything. > :> :is this explanation more clear ? > :> > :> No, the EXAMPLES section. > : > :there is nothing in the "EXAMPLES" section which prevent to write > :the first 16 sectors if using the drive in `dangerously-dedicated' > :mode that is w/ no fdisk partition. > > The examples section, if you have a reasonably recent (4.3 or > later I believe) system, shows you how to create a disklabel -stable is enough :P > inside a slice (i.e. NOT dangerously dedicated), and shows you > how to run fdisk to initialize a disk and then how to run > disklabel to inintialize the slice. The sequence is something > like: > > fdisk -BI da0 > disklabel -w -r -B da0s1 auto > disklabel -e da0s1 so, we are "in accord" (don't know if this is really english speaking :) but the originator of this thread (John) don't talk about fdisk. so, I stated that he is trying to format his drives in `dangerously-dedicated' mode which conflict w/ the HTP hardware which lso need the first blocks of the drive. Cyrille. -- Cyrille Lefevre mailto:clefevre@citeweb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 20:10:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtpout.mac.com (smtpout.mac.com [204.179.120.89]) by hub.freebsd.org (Postfix) with ESMTP id 943C237B405 for ; Sun, 11 Nov 2001 20:10:38 -0800 (PST) Received: from smtp-relay02.mac.com (server-source-si02 [10.13.10.6]) by smtpout.mac.com (8.12.1/8.10.2/1.0) with ESMTP id fAC40ssD015217 for ; Sun, 11 Nov 2001 20:00:54 -0800 (PST) Received: from asmtp02.mac.com ([10.13.10.66]) by smtp-relay02.mac.com (Netscape Messaging Server 4.15 relay02 Jun 21 2001 23:53:48) with ESMTP id GMO69Q00.0VE for ; Sun, 11 Nov 2001 20:10:38 -0800 Received: from quinn ([24.91.220.49]) by asmtp02.mac.com (Netscape Messaging Server 4.15 asmtp02 Jun 21 2001 23:53:48) with ESMTP id GMO69P00.M0A for ; Sun, 11 Nov 2001 20:10:37 -0800 Date: Sun, 11 Nov 2001 23:10:35 -0500 Subject: Re: 4.4 - X windows starts for root only Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v472) From: Justin White To: freebsd-stable@freebsd.org Content-Transfer-Encoding: 7bit In-Reply-To: <001901c16a34$12e7f680$0101a8c0@e1> Message-Id: <38DD5232-D723-11D5-8F86-000393092F82@mac.com> X-Mailer: Apple Mail (2.472) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Saturday, November 10, 2001, at 05:07 , Frank J. Eigler wrote: > Hi, > > I installed 4.4 but X windows can be started for root only. > > Hardware: > Intel SE440BX2NAV motherboard > ATI Rage Fury 32MB 2x AGP video card > SoundBlaster CT5803 soundcard > Linksys EtherFast LNE100TX v4.1 (ADMtek AN985 10/100TX) NIC > 512 MB PC100 SDRAM > WD 20GB harddrive > > I'm new to FreeBSD, and need advice. Could anyone tell me where to start > fixing this? check out /usr/ports/x11/wrapper cat pkg_descr for a quick look at what it (and any port) does alternatively, use xdm/gdm/kdm and login through that as your normal user as has been said before -Justin White | just6979@yahoo.com | http://justinfinity.2y.net:8080/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 20:12: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shumai.marcuscom.com (rdu57-28-046.nc.rr.com [66.57.28.46]) by hub.freebsd.org (Postfix) with ESMTP id A83DF37B405 for ; Sun, 11 Nov 2001 20:12:01 -0800 (PST) Received: from localhost (marcus@localhost) by shumai.marcuscom.com (8.11.6/8.11.6) with ESMTP id fAC4C5X59419 for ; Sun, 11 Nov 2001 23:12:05 -0500 (EST) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: shumai.marcuscom.com: marcus owned process doing -bs Date: Sun, 11 Nov 2001 23:12:04 -0500 (EST) From: Joe Clarke To: freebsd-stable@freebsd.org Subject: Problem with Gnome apps crashing on -stable Message-ID: <20011111230137.V59304-100000@shumai.marcuscom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm seeing something strange with certain Gnome apps on -stable. At first it was just happening with nautilus, so I ignored it. Now, the same thing happens with balsa. I've been trying to track down the problem, but I need some help. When I open my home directory in nautilus (which has a lot of files), I noticed this on my console: sigreturn: eflags 0x10296 Then a core dump on signal 6. The eflags value is different each time. This message comes from machdep.c in the kernel. It seems to indicate that the user process is trying to set eflags and (eflags & PSL_VM) is not true. My first question is, what exactly is eflags? Is this caused by someone not saving context correctly? Now, when this happens, the SIGABRT is caused by uthread_kern.c which is evident in my .gnomerc-errors file: Fatal error 'Thread has returned from sigreturn or longjmp' at line ? in file /usr/src/lib/libc_r/uthread/uthread_kern.c (errno = ?) Abort trap - core dumped The relevant code from uthread_kern.c seems to be: /* * Ensure the process signal mask is set * correctly: */ _thread_run->ctx.uc.uc_sigmask = _process_sigmask; sigreturn(&_thread_run->ctx.uc); #endif break; } /* This point should not be reached. */ PANIC("Thread has returned from sigreturn or longjmp"); Line 607 was changed three weeks ago from: _thread_sys_sigreturn(&_thread_run->ctx.uc); to what you see above. I'm not sure this has any bearing on the problem, though. Balsa 1.2.3 has started doing the same thing at times. I have -stable cvsup'd and compiled from yesterday (11/10/2001), and all the latest components having anything to do with gnome. Like I said, I'd love to track this down, but I need some guidance as I'm not that familiar with kernel threading. Thanks. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 20:46:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.bmi.net (smtp.bmi.net [204.57.191.31]) by hub.freebsd.org (Postfix) with ESMTP id 0154537B405 for ; Sun, 11 Nov 2001 20:46:18 -0800 (PST) Received: from johncoop.MSHOME (drumheller-router.bmi.net [206.63.201.3] (may be forged)) by smtp.bmi.net (Pro-8.9.3/Pro-8.9.3) with ESMTP id DAA29767; Mon, 12 Nov 2001 03:52:19 -0800 Date: Sun, 11 Nov 2001 20:45:58 -0800 From: John Merryweather Cooper To: Joe Clarke Cc: freebsd-stable@freebsd.org Subject: Re: Problem with Gnome apps crashing on -stable Message-ID: <20011111204558.C717@johncoop.MSHOME> References: <20011111230137.V59304-100000@shumai.marcuscom.com> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: <20011111230137.V59304-100000@shumai.marcuscom.com>; from marcus@marcuscom.com on Sun, Nov 11, 2001 at 20:12:04 -0800 X-Mailer: Balsa 1.2.3 Lines: 83 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2001.11.11 20:12 Joe Clarke wrote: > I'm seeing something strange with certain Gnome apps on -stable. At > first > it was just happening with nautilus, so I ignored it. Now, the same > thing > happens with balsa. I've been trying to track down the problem, but I > need some help. When I open my home directory in nautilus (which has > a > lot of files), I noticed this on my console: > > sigreturn: eflags 0x10296 > > Then a core dump on signal 6. The eflags value is different each > time. > This message comes from machdep.c in the kernel. It seems to indicate > that the user process is trying to set eflags and (eflags & PSL_VM) is > not > true. My first question is, what exactly is eflags? Is this caused > by > someone not saving context correctly? > > Now, when this happens, the SIGABRT is caused by uthread_kern.c which > is > evident in my .gnomerc-errors file: > > Fatal error 'Thread has returned from sigreturn or longjmp' at line ? > in > file /usr/src/lib/libc_r/uthread/uthread_kern.c (errno = ?) > Abort trap - core dumped > > The relevant code from uthread_kern.c seems to be: > > /* > * Ensure the process signal mask is set > * correctly: > */ > _thread_run->ctx.uc.uc_sigmask = > _process_sigmask; > sigreturn(&_thread_run->ctx.uc); > #endif > break; > } > /* This point should not be reached. */ > PANIC("Thread has returned from sigreturn or longjmp"); > > Line 607 was changed three weeks ago from: > > _thread_sys_sigreturn(&_thread_run->ctx.uc); > > to what you see above. I'm not sure this has any bearing on the > problem, > though. Balsa 1.2.3 has started doing the same thing at times. I > have > -stable cvsup'd and compiled from yesterday (11/10/2001), and all the > latest components having anything to do with gnome. > > Like I said, I'd love to track this down, but I need some guidance as > I'm > not that familiar with kernel threading. Thanks. > > Joe > I've seen this too. I would add that I've even seen it happen spontaneously (while xscreensaver has the root window) with the result that the whole X window session comes crashing down. I'm also consistently seeing warning being issued concurrent with the eflags discussed above relating to calls to free() for blocks that are already freed. A wild guess is that something isn't quite right in ORBit/oaf? -- jmc || MacroHard -- \ || the perfection of form over | ----------------------------------|| substance, marketing over | Web: http://www.borgsdemons.com || performance, and greed over | || design . . . | =======================================================================/ Public Key: http://www.borgsdemons.com/Personal/pgpkey.asc | =======================================================================\ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 21: 1:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail45.sdc1.sfba.home.com (femail45.sdc1.sfba.home.com [24.254.60.39]) by hub.freebsd.org (Postfix) with ESMTP id E182537B405 for ; Sun, 11 Nov 2001 21:01:33 -0800 (PST) Received: from manhattan ([24.253.231.66]) by femail45.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20011112050133.HLMK4426.femail45.sdc1.sfba.home.com@manhattan> for ; Sun, 11 Nov 2001 21:01:33 -0800 From: "Jolly Roger" To: "'freebsd-mobile@FreeBSD.org'" Subject: Sony VAIO PCG-R505JSP & FreeBSD 4.4 CD Image Date: Sun, 11 Nov 2001 23:55:09 -0500 Message-ID: <001b01c16b36$3534e6f0$4100a8c0@compuspec.net> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <000601c1667c$f66fbb60$4100a8c0@compuspec.net> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I am trying to install FreeBSD from CD using the 4.4 CD Image. It boots OK and lets me into the HW Config screen. Here (I've tried several combinations) I disable all the SCSI stuff and all the Network Stuff. When I continue, the installation just hangs. I have tried the 4.3 CD and this gets past the point where the 4.4 CD Hangs, but when it tried to do the actual install it is unable to find the CD. With the 4.4 Install doing a boot -v, I get the output shown below. (Note: The output has been hand typed, not a cut & paste, so it could have a Typo...) ata0-master: success setting UDMA5 on Intel chip Creating DISK ad0 ad0: ATA-5 disk at ata0-master ad0: 28615MB (58605120 sectors), 58140 cyls, 16 heads, 63 S/T, 512 B/S ado: 16 secs/int, 1 depth queue, UDMA100 ado: piomode=4 dmamode=2 udmamode=5 cblid=1 ado: 28615MB [58140/16/63] at ata0-master UDMA100 Mounting root from ufs:/dev/md0c md0: invalid primary partition table: no magic start_init: trying /sbin/init start_init: trying /sbin/oinit start_init: trying /sbin/init.bak start_init: trying stand/sysinstall I would be grateful for any suggestions that I may try... Thanks, Roger. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 21:40:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 83BBD37B41B; Sun, 11 Nov 2001 21:40:03 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fAC5e2a30036; Sun, 11 Nov 2001 22:40:02 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fAC5e1778386; Sun, 11 Nov 2001 22:40:02 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200111120540.fAC5e1778386@harmony.village.org> To: mobile@freebsd.org Cc: stable@freebsd.org Subject: HEADS UP: MFC of latest pccard code Date: Sun, 11 Nov 2001 22:40:01 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just tried the latest -current pccard code on my CL-Pd6729, and it works great, even with the 3.3V card that I have, so I merged the latest kernel changes to -stable. o Fixes second socket of 6729 o Fixes hang on reboot on some cards o Expand working 3.3V card support from only 82365SL step DF to also include CL-PD6710, '22 and '29. o Lots of other stuff too. Pleae let me know if you have problems. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 21:52:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 9D5DC37B405 for ; Sun, 11 Nov 2001 21:52:21 -0800 (PST) Received: from cain.gsoft.com.au (root@localhost [127.0.0.1]) by cain.gsoft.com.au (8.11.6/8.11.6) with ESMTP id fAC5qBS49882; Mon, 12 Nov 2001 16:22:12 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200111071514.fA7FEFO27709@cwsys.cwsent.com> Date: Mon, 12 Nov 2001 16:22:10 +1030 (CST) From: "Daniel O'Connor" To: Cy Schubert - ITSD Open Systems Group Subject: Re: dhclient bug? Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 07-Nov-2001 Cy Schubert - ITSD Open Systems Group wrote: > You probably want to submit a PR to make sure that it's included in > FreeBSD. Otherwise everyone might assume that someone else will handle > it. Besides, the job isn't done until the paperwork is done. 'tis done.. http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/31835 --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 22:13: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 776BD37B416 for ; Sun, 11 Nov 2001 22:13:01 -0800 (PST) Received: (qmail 75058 invoked from network); 12 Nov 2001 06:13:00 -0000 Received: from unknown (HELO there) ([66.92.40.28]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 12 Nov 2001 06:13:00 -0000 Content-Type: text/plain; charset="us-ascii" From: Michael Collette To: Warner Losh Subject: Re: HEADS UP: MFC of latest pccard code Date: Sun, 11 Nov 2001 22:10:44 +0000 X-Mailer: KMail [version 1.3] Cc: FreeBSD MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20011112061301.776BD37B416@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Warner, Don't know if it's pccard related or not, but on a build of STABLE on Saturday my ipfw was all dinked up. I was seeing all kinds of nasty get socket errors whenever I tried to add a rule. This evening whe I cvsup'd I noticed some code changes coming in with sufixes of fw on them so I went and rebuilt world here. Seems that cleaned up all the errors, and ipfw is once again working for me on this laptop. I should note that there is still a nasty timing problem on boot up in relation to when pccard kicks in. It's the last darn thing to run, after pretty much all my networking daemons have already been asked to go. pccardd really needs to get going long before stuff like ipfw kicks in. At this point I simply have a shell script that I run following a boot up that forces a reload of all my ipfw rules. It works and all, but it is an awfully nasty hack around. Any chance a more elegant solution might be in the works sometime soon? Lastly, do any of the changes you've made here effect the Xircom PCMCIA cards? I've got a RealPort Cardbus Ethernet 10/100+Modem 56 over here I'd love to try out some time. Not a real big deal, as this Linksys card I've got now work terrific after all your hard work over there. Warner Losh wrote: > I just tried the latest -current pccard code on my CL-Pd6729, and it > works great, even with the 3.3V card that I have, so I merged the > latest kernel changes to -stable. > o Fixes second socket of 6729 > o Fixes hang on reboot on some cards > o Expand working 3.3V card support from only 82365SL step DF > to also include CL-PD6710, '22 and '29. > o Lots of other stuff too. > > Pleae let me know if you have problems. > > Warner Later on, -- "A short saying often contains much wisdom." -Sophocles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 22:19:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 6428937B416 for ; Sun, 11 Nov 2001 22:19:44 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fAC6Jha30119; Sun, 11 Nov 2001 23:19:43 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fAC6Jg778698; Sun, 11 Nov 2001 23:19:43 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200111120619.fAC6Jg778698@harmony.village.org> To: Michael Collette Subject: Re: HEADS UP: MFC of latest pccard code Cc: FreeBSD In-reply-to: Your message of "Sun, 11 Nov 2001 22:10:44 GMT." <200111120613.fAC6D1a30102@rover.village.org> References: <200111120613.fAC6D1a30102@rover.village.org> Date: Sun, 11 Nov 2001 23:19:42 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200111120613.fAC6D1a30102@rover.village.org> Michael Collette writes: : I should note that there is still a nasty timing problem on boot up in : relation to when pccard kicks in. It's the last darn thing to run, after : pretty much all my networking daemons have already been asked to go. pccardd : really needs to get going long before stuff like ipfw kicks in. : At this point I simply have a shell script that I run following a boot up : that forces a reload of all my ipfw rules. It works and all, but it is an : awfully nasty hack around. Any chance a more elegant solution might be in : the works sometime soon? Add -z to the pccardd_flags and this will be fixed. : Lastly, do any of the changes you've made here effect the Xircom PCMCIA : cards? I've got a RealPort Cardbus Ethernet 10/100+Modem 56 over here I'd : love to try out some time. Not a real big deal, as this Linksys card I've : got now work terrific after all your hard work over there. None of the changes I just merged will change that, I don't think. I do have some Xircom patches, but I've not committed them yet. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 22:29:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 9968F37B405 for ; Sun, 11 Nov 2001 22:29:32 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fAC6TVa30138; Sun, 11 Nov 2001 23:29:31 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fAC6TV778771; Sun, 11 Nov 2001 23:29:31 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200111120629.fAC6TV778771@harmony.village.org> To: Michael Collette Subject: Re: HEADS UP: MFC of latest pccard code Cc: FreeBSD In-reply-to: Your message of "Sun, 11 Nov 2001 22:10:44 GMT." <20011112061301.776BD37B416@hub.freebsd.org> References: <20011112061301.776BD37B416@hub.freebsd.org> Date: Sun, 11 Nov 2001 23:29:31 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011112061301.776BD37B416@hub.freebsd.org> Michael Collette writes: : Lastly, do any of the changes you've made here effect the Xircom PCMCIA : cards? I've got a RealPort Cardbus Ethernet 10/100+Modem 56 over here I'd : love to try out some time. Not a real big deal, as this Linksys card I've : got now work terrific after all your hard work over there. Actaully, I misread this the first time. Cardbus support in -stable may or may not happen, but it won't be soon. There's too much to do to get the issues with NEWCARD in -current fixed, which will be my focus for a while. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 23:53:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 28DD437B405 for ; Sun, 11 Nov 2001 23:53:41 -0800 (PST) Received: (qmail 96597 invoked from network); 12 Nov 2001 07:53:40 -0000 Received: from unknown (HELO there) ([66.92.40.28]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 12 Nov 2001 07:53:40 -0000 Content-Type: text/plain; charset="us-ascii" From: Michael Collette To: Warner Losh Subject: Re: HEADS UP: MFC of latest pccard code Date: Sun, 11 Nov 2001 23:51:24 +0000 X-Mailer: KMail [version 1.3] Cc: FreeBSD References: <200111120613.fAC6D1a30102@rover.village.org> <200111120619.fAC6Jg778698@harmony.village.org> In-Reply-To: <200111120619.fAC6Jg778698@harmony.village.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20011112075341.28DD437B405@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Warner, The -z flag worked exactly as advertised. Very cool! On Monday 12 November 2001 06:19 am, Warner Losh wrote: > In message <200111120613.fAC6D1a30102@rover.village.org> Michael Collette writes: > : I should note that there is still a nasty timing problem on boot up in > : relation to when pccard kicks in. It's the last darn thing to run, after > : pretty much all my networking daemons have already been asked to go. > : pccardd really needs to get going long before stuff like ipfw kicks in. > : At this point I simply have a shell script that I run following a boot > : up that forces a reload of all my ipfw rules. It works and all, but it > : is an awfully nasty hack around. Any chance a more elegant solution > : might be in the works sometime soon? > > Add -z to the pccardd_flags and this will be fixed. Later on, -- "A short saying often contains much wisdom." -Sophocles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 11 23:55:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id E74C237B405 for ; Sun, 11 Nov 2001 23:55:53 -0800 (PST) Received: (qmail 13184 invoked from network); 12 Nov 2001 07:55:53 -0000 Received: from unknown (HELO there) ([66.92.40.28]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 12 Nov 2001 07:55:53 -0000 Content-Type: text/plain; charset="us-ascii" From: Michael Collette To: Warner Losh Subject: Re: HEADS UP: MFC of latest pccard code Date: Sun, 11 Nov 2001 23:53:37 +0000 X-Mailer: KMail [version 1.3] Cc: FreeBSD References: <20011112061301.776BD37B416@hub.freebsd.org> <200111120629.fAC6TV778771@harmony.village.org> In-Reply-To: <200111120629.fAC6TV778771@harmony.village.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20011112075553.E74C237B405@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday 12 November 2001 06:29 am, Warner Losh wrote: > In message <20011112061301.776BD37B416@hub.freebsd.org> Michael Collette writes: > : Lastly, do any of the changes you've made here effect the Xircom PCMCIA > : cards? I've got a RealPort Cardbus Ethernet 10/100+Modem 56 over here > : I'd love to try out some time. Not a real big deal, as this Linksys card > : I've got now work terrific after all your hard work over there. > > Actaully, I misread this the first time. Cardbus support in -stable > may or may not happen, but it won't be soon. There's too much to do > to get the issues with NEWCARD in -current fixed, which will be my > focus for a while. > > Warner Oh well. The stuff that's in there now is working really sweet. Please let me know if that cardbus support ever does get in there and I'd be happy to run any kind of testing for it. Later on, -- "A short saying often contains much wisdom." -Sophocles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 6:27:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailout1.informatik.tu-muenchen.de (mailout1.informatik.tu-muenchen.de [131.159.254.5]) by hub.freebsd.org (Postfix) with ESMTP id 85C9B37B419 for ; Mon, 12 Nov 2001 06:27:28 -0800 (PST) Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by mailout1.informatik.tu-muenchen.de (Postfix) with ESMTP id 8F4147953 for ; Mon, 12 Nov 2001 15:27:27 +0100 (MET) Received: from atrbg11.informatik.tu-muenchen.de (atrbg11.informatik.tu-muenchen.de [131.159.24.91]) by tuminfo2.informatik.tu-muenchen.de (Postfix) with ESMTP id D658510AC1 for ; Mon, 12 Nov 2001 15:27:23 +0100 (MET) Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id 0D9E4136DB; Mon, 12 Nov 2001 15:27:26 +0100 (CET) Date: Mon, 12 Nov 2001 15:27:26 +0100 From: Daniel Lang To: freebsd-stable@freebsd.org Subject: dirpref benefit on virtual disks Message-ID: <20011112152726.A10505@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Geek: GCS/CC d-- s: a- C++$ UBS++++$ P+++$ L- E-(---) W+++(--) N++ o K w--- O? M? V? PS+(++) PE--(+) Y+ PGP+ t++ 5+++ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y+ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, as I understood, the new dirpref algorithm can improve performance a lot, but only applies to new created directories. To be able to use it, old existing directories would have to be created new. Now I have some huge filesystems on RAID partitions. To recreate all their directories involves some hassle, but I would think about doing it. But since these are no real but virtual disks, spread over a set of disks in a hardware raidbox, I'm not sure, if I would even benefit from the better algorithm. It sounded a bit like designed for filesystems on a (single?) disk? Could anyone clearify this, please? Also I would like to know, if there is a certain limit of free space, on the disk, so that the algorithm can actually use the better layout? The disks have some space left, in an absolute way, but not that much from a relative point of view (like 12GB left which is just 6% minfree not taken into account). Thanks for your answers. Best regards, Daniel -- IRCnet: Mr-Spock - Burn them to ashes, then burn the ashes. - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 6:32:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 1694C37B405 for ; Mon, 12 Nov 2001 06:32:22 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id JAA28267; Mon, 12 Nov 2001 09:32:12 -0500 (EST) (envelope-from mwlucas) Date: Mon, 12 Nov 2001 09:32:12 -0500 From: Michael Lucas To: Matthew Dillon Cc: Galen Sampson , freebsd-stable@FreeBSD.ORG Subject: Re: KDE init [was RE: DCOP server problem...] Message-ID: <20011112093211.A28224@blackhelicopters.org> References: <20011109180124.31471.qmail@web14103.mail.yahoo.com> <200111100718.fAA7I9522856@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200111100718.fAA7I9522856@apollo.backplane.com>; from dillon@apollo.backplane.com on Fri, Nov 09, 2001 at 11:18:09PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matt, Check out /usr/ports/sysutils/portupgrade. Automatic port & port dependency upgrading, fully recursive. Took me about thirty minutes to set up. My desktop is three years old and has been manually upgraded, patched, etc, repeatedly. And portupgrade upgraded every port to the latest version, cleaned up all sorts of old crap, etc. Highly recommended. Tutorial coming to onlamp.com RSN (I believe later this month). On Fri, Nov 09, 2001 at 11:18:09PM -0800, Matthew Dillon wrote: > > : > :Hello all, > : I have seen quite a few posts in here about problems with KDE. I personally > :still have the problem that KDE will show its splash screen, get to > :"initializing peripherals" and just sit there. I have noticed a few PR's, > :etc., and KDE's bug database had at least on message claiming this to be a > :problem with FreeBSD's threads. I have gone so far as to remove every port > :that KDE depends on (except X) and rebuilt through the ports, but I just > :haven't had any luck. I am running Xfree86 3.3.6 (built from ports) over a > :year ago, and KDE2 cvsuped many times, but the latest has been 7 days ago. Any > :known workarounds/fixes would be most appreciated. > : > :regards, > :Galen Sampson > > I'm having weird problems with kde2 as well.. it keeps screwing up > the fonts. It forgets about font families, changes my defaults, and > does all sorts of other nasty things. > > I noticed that when I did a 'make' in the port for kde2, that it didn't > bother updating older kde2-related libraries that were already installed > but out of date, so it was running the kde2 desktop binaries against > older shared libraries. It took a while to go through all the ports > and deinstall them and now I am rebuilding the whole thing from scratch > again. Maybe it will work better with all the shared libs synced up. > > I've actually noticed this with ports before... there needs to be a > make target to tell ports to upgrade everything that is out of date or > something like that. I dunno. > > -Matt > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 6:58: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from atos.sr.se (atos.sr.se [192.121.194.132]) by hub.freebsd.org (Postfix) with ESMTP id C76AA37B405 for ; Mon, 12 Nov 2001 06:58:03 -0800 (PST) Received: from honken.sr.se (honken.sr.se [134.25.128.27]) by atos.sr.se (8.11.6/8.11.6) with ESMTP id fACEvVs92358 for ; Mon, 12 Nov 2001 15:57:35 +0100 (CET) (envelope-from gunnar@pluto.sr.se) Received: from pluto.sr.se (pluto.SR.SE [134.25.193.91]) by honken.sr.se (8.9.3/8.9.3) with ESMTP id PAA45725 for ; Mon, 12 Nov 2001 15:57:31 +0100 (CET) (envelope-from gunnar@pluto.sr.se) Received: (from root@localhost) by pluto.sr.se (8.11.6/8.11.1) id fACEvVE34640 for freebsd-stable@freebsd.org; Mon, 12 Nov 2001 15:57:31 +0100 (CET) (envelope-from gunnar) Received: (from gunnar@localhost) by pluto.sr.se (8.11.6/8.11.1av) id fACEvTU34632 for freebsd-stable@freebsd.org; Mon, 12 Nov 2001 15:57:29 +0100 (CET) (envelope-from gunnar) Date: Mon, 12 Nov 2001 15:57:29 +0100 From: Gunnar Flygt To: FreeBSD Stable Subject: png-port-upgrade gave med defunct kde Message-ID: <20011112155729.A34537@sr.se> Reply-To: Gunnar Flygt Mail-Followup-To: Gunnar Flygt , FreeBSD Stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Not really a stable question, but since the experts are here. :) Upgraded png from 1.0.12 to 1.2.0 That was a catastrophy for kde! No more icons at all! Anyone else seen this? Fix? kde is 2.2.1 -- __o regards, Gunnar ---_ \<,_ email: flygt@sr.se ---- (_)/ (_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 7:14:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cx2037703-a.kenner1.la.home.com (cx2037703-a.kenner1.la.home.com [24.39.27.145]) by hub.freebsd.org (Postfix) with ESMTP id 75F3B37B41F; Mon, 12 Nov 2001 07:14:27 -0800 (PST) Received: (from conrads@localhost) by cx2037703-a.kenner1.la.home.com (8.11.6/8.11.6) id fACFED274510; Mon, 12 Nov 2001 09:14:13 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.1 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 12 Nov 2001 09:14:13 -0600 (CST) Organization: @Home Network From: Conrad Sabatier To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: unknown kernel error message Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG A friend of mine is getting these lately, every time he boots his 4.4-STABLE box (I just cvsupped him and built a new world and kernel last night to see if it would help; didn't): Nov 11 22:36:10 unixpros /kernel: arp: unknown hardware address format (0x0800) I have no idea where this might be coming from or why. But his NIC doesn't seem to be performing anywhere near up to par. From dmesg: txp0: <3Com 3cR990-TX-95 Etherlink with 3XP Processor> port 0xb400-0xb47f mem 0xf2800000-0xf283ffff irq 9 at device 12.0 on pci2 Any ideas would be greatly appreciated. Thanks. -- Conrad Sabatier "Power corrupts. Absolute power is kind of neat" -- John Lehman, Secretary of the Navy 1981-1987 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 7:54:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.michaelchaney.com (ns2.michaelchaney.com [207.65.84.67]) by hub.freebsd.org (Postfix) with ESMTP id CDD2437B405; Mon, 12 Nov 2001 07:54:21 -0800 (PST) Received: from adsl-66-136-97-81.dsl.hrlntx.swbell.net (negwo.eastcore.net) [66.136.97.81] by mail.michaelchaney.com with esmtp (Exim 3.22 #1 (Debian)) id 163JPg-000PNb-00; Mon, 12 Nov 2001 09:54:21 -0600 Received: (from rick@localhost) by negwo.eastcore.net (8.11.6/8.11.6) id fACFsHA38902; Mon, 12 Nov 2001 09:54:17 -0600 (CST) (envelope-from roundeye@roundeye.net) Date: Mon, 12 Nov 2001 09:54:17 -0600 From: Rick Bradley To: Conrad Sabatier Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: unknown kernel error message Message-ID: <20011112095417.F25208@negwo.eastcore.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from conrads@home.com on Mon, Nov 12, 2001 at 09:14:13AM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Conrad Sabatier (conrads@home.com) [011112 09:16]: > A friend of mine is getting these lately, every time he boots his > 4.4-STABLE box (I just cvsupped him and built a new world and kernel last > night to see if it would help; didn't): > > Nov 11 22:36:10 unixpros /kernel: arp: unknown hardware address format > (0x0800) I had this problem once when I had a Mandrake Linux system on my network. IIRC either Mandrake 7.2 is sometimes doing something weird when it constructs ARP packets. I upgraded the Mandrake machine to FreeBSD and the problem went away. Rick -- Mostly useless pseudo-random number: 882 (77 F) http://xns.org/=rick@eastcore.net CE7E0CBE7AB9F5EAF1E34943E8EB2BA10615B6E3 keyserver.pgp.com/pks/lookup?op=get&exact=on&search=roundeye%40roundeye.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 9:28:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from desws060.mediaways.net (smtp.compuserve.de [62.52.27.101]) by hub.freebsd.org (Postfix) with SMTP id 6040437B416 for ; Mon, 12 Nov 2001 09:28:49 -0800 (PST) Received: (qmail 14772 invoked by uid 4218); 12 Nov 2001 17:28:46 -0000 Received: from dtmd-d931a81f.pool.mediaways.net (HELO dunkelkammer.void) (217.49.168.31) by relay3b with SMTP; 12 Nov 2001 17:28:46 -0000 Received: by dunkelkammer.void (Postfix, from userid 910) id 5A17011898; Mon, 12 Nov 2001 18:00:34 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by dunkelkammer.void (Postfix) with ESMTP id 370F3F86E for ; Mon, 12 Nov 2001 18:00:34 +0100 (CET) Date: Mon, 12 Nov 2001 18:00:34 +0100 (CET) From: Stefan Walter X-X-Sender: stefan@dunkelkammer.void To: FreeBSD Stable Subject: Re: png-port-upgrade gave med defunct kde In-Reply-To: <20011112155729.A34537@sr.se> Message-ID: <20011112175742.U606-100000@dunkelkammer.void> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Am 12.11.01 ward von Gunnar Flygt das Folgende gesandt: > Not really a stable question, but since the experts are here. :) > > Upgraded png from 1.0.12 to 1.2.0 That was a catastrophy for kde! No > more icons at all! Anyone else seen this? Fix? kde is 2.2.1 I do not use KDE, but with me, removing, recompiling and reinstalling all ports/packages depending on (and including) libpng solved it. Stefan -- No reading beyond this point PGP key: http://homepages.compuserve.de/SWDunkelkammer/dunkelkammer.asc PGP key fingerprint: 6719 7C67 E188 4419 C7F6 786E 58C0 AEBF 5796 6947 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 9:39:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A7FBC37B417 for ; Mon, 12 Nov 2001 09:39:26 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fACHctx84446; Mon, 12 Nov 2001 09:38:55 -0800 (PST) (envelope-from dillon) Date: Mon, 12 Nov 2001 09:38:55 -0800 (PST) From: Matthew Dillon Message-Id: <200111121738.fACHctx84446@apollo.backplane.com> To: Michael Lucas Cc: Galen Sampson , freebsd-stable@FreeBSD.ORG Subject: Re: KDE init [was RE: DCOP server problem...] References: <20011109180124.31471.qmail@web14103.mail.yahoo.com> <200111100718.fAA7I9522856@apollo.backplane.com> <20011112093211.A28224@blackhelicopters.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :Matt, : :Check out /usr/ports/sysutils/portupgrade. Automatic port & port :dependency upgrading, fully recursive. : :Took me about thirty minutes to set up. My desktop is three years old :and has been manually upgraded, patched, etc, repeatedly. And :portupgrade upgraded every port to the latest version, cleaned up all :sorts of old crap, etc. Highly recommended. Yah, I'm playing with it now. After fixing up the database with pkgdb -F (scary!) I am now running portupgrade -a. It's happily churning away on the ports tree upgrade god knows what. Thanks! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 9:48:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 4CDB337B417 for ; Mon, 12 Nov 2001 09:48:23 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id MAA29326; Mon, 12 Nov 2001 12:48:20 -0500 (EST) (envelope-from mwlucas) Date: Mon, 12 Nov 2001 12:48:20 -0500 From: Michael Lucas To: Matthew Dillon Cc: Galen Sampson , freebsd-stable@FreeBSD.ORG Subject: Re: KDE init [was RE: DCOP server problem...] Message-ID: <20011112124820.A29306@blackhelicopters.org> References: <20011109180124.31471.qmail@web14103.mail.yahoo.com> <200111100718.fAA7I9522856@apollo.backplane.com> <20011112093211.A28224@blackhelicopters.org> <200111121738.fACHctx84446@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200111121738.fACHctx84446@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Nov 12, 2001 at 09:38:55AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Nov 12, 2001 at 09:38:55AM -0800, Matthew Dillon wrote: > Yah, I'm playing with it now. After fixing up the database with > pkgdb -F (scary!) I am now running portupgrade -a. It's happily > churning away on the ports tree upgrade god knows what. Thanks! General word to the public: The first time you use portupgrade, be prepared to have your computer spend a *long* time upgrading ports. I had 187 ports on my computer when I started it the first time. It took almost a day on a twin-CPU Pentium 1G system. Ouch. Of course, I had Mozilla, my wife's KDE, gnucash... most of the really nasty stuff in the Ports Collection, actually. Running those upgrades by hand would have taken a week, not to mention sorting out the dependencies. -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 9:49:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id A5DF537B419; Mon, 12 Nov 2001 09:49:25 -0800 (PST) Received: from caddis.yogotech.com (caddis.yogotech.com [206.127.123.130]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id KAA03943; Mon, 12 Nov 2001 10:49:23 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id fACHnNo62647; Mon, 12 Nov 2001 10:49:23 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15344.2979.298398.315095@caddis.yogotech.com> Date: Mon, 12 Nov 2001 10:49:23 -0700 To: Matthew Dillon Cc: Nate Williams , stable@FreeBSD.ORG, jayanth@FreeBSD.ORG Subject: Re: TCP NewReno causing wild performance fluctuations In-Reply-To: <200111112134.fABLYXK47890@apollo.backplane.com> References: <15340.20191.441648.662113@caddis.yogotech.com> <200111112134.fABLYXK47890@apollo.backplane.com> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I think you should MFC this, Nate. I too think it should be merged, but I wanted to get Jayanth's feedback first. Nate > > :We've been using FreeBSD boxes as our reference ftp servers at work, and > :because of the recent security issues, I've went through and updated a > :number of our public boxes from 3.x -> 4.4. > : > :However, we're seeing significant variations in ftp throughput from > :boxes that are directly connected on the lan segment. If I disable the > :New Reno code, things go back to normal (ie; no fluctuations). > : > :I went through the logfiles, and it turns out there has been one fix to > :the code that hasn't been merged into stable. > : > :Rev1.139 in tcp_input.c has not (yet) been merged into -stable. > :... > : > :I hand-merged this change back onto my box, installed a new kernel, and > :now in my *very* minor testing things appear to be more normal. My > :question is should this fix be merged into stable, and would the lack of > :this bugfix explain my performance results? > : > :Unfortunately, I don't haven't gotten any tcpdump outputs to analyze > :what was going on, but I didn't want this bugfix to slip through the > :cracks. > : > :Nate > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 10:25:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from clmboh1-smtp3.columbus.rr.com (clmboh1-smtp3.columbus.rr.com [65.24.0.112]) by hub.freebsd.org (Postfix) with ESMTP id E154437B417 for ; Mon, 12 Nov 2001 10:25:37 -0800 (PST) Received: from potentialtech.com (dhcp065-024-023-038.columbus.rr.com [65.24.23.38]) by clmboh1-smtp3.columbus.rr.com (8.11.2/8.11.2) with ESMTP id fACIHVT21940; Mon, 12 Nov 2001 13:17:31 -0500 (EST) Message-ID: <3BF013B8.8070009@potentialtech.com> Date: Mon, 12 Nov 2001 13:23:52 -0500 From: Bill Moran Organization: Potential Technology User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.3) Gecko/20010914 X-Accept-Language: en-us MIME-Version: 1.0 To: Daniel Lang Cc: freebsd-stable@FreeBSD.ORG Subject: Re: dirpref benefit on virtual disks References: <20011112152726.A10505@atrbg11.informatik.tu-muenchen.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [since I've yet to see any other replies] Daniel Lang wrote: > Hi, > > as I understood, the new dirpref algorithm can improve > performance a lot, but only applies to new created directories. > To be able to use it, old existing directories would have to > be created new. That's consistent with my understanding of it. > Now I have some huge filesystems on RAID partitions. To recreate > all their directories involves some hassle, but I would think > about doing it. But since these are no real but virtual disks, > spread over a set of disks in a hardware raidbox, I'm not sure, > if I would even benefit from the better algorithm. It sounded > a bit like designed for filesystems on a (single?) disk? My thought would be that, yes, it will improve performance. If you've got a typical 3 disk, RAID-5, a read of the directory still causes a seek on all three disks, and if there's continual seeking across the three disks, you'll see performance degredation. If dirpref can layout the directory info so that it's close together, seek time is reduces, whether on 3 disks or one. That being said, I don't _know_. It would be interesting to test it. Since you're already considering recreating directories, why not do a test to see if it's worth it? Just take a directory tree that's pretty complicated and that was created before you updated the dirpref code. Run a find operation of some sort that traverses the tree and time it. Then, back that tree up and recreate it, re-run the find and time it again and let everyone know if it's worth it. You only need do this with one section of a tree on the drive to determine how much difference it's going to make. > Also I would like to know, if there is a certain limit of free > space, on the disk, so that the algorithm can actually use > the better layout? The disks have some space left, in an > absolute way, but not that much from a relative point of view > (like 12GB left which is just 6% minfree not taken into account). Have a read of the original paper on FFS (which is in /usr/share/doc if you installed docs with FreeBSD) there is an explanation of why 8% is reserved on the drive - man tunefs comments about this as well. I would assume that the new dirpref code needs plenty of free space to use the optimal layout policy, but I don't know if the minimal free space is still 8% or not, and I don't know if anyone has even tested the new dirpref code to see if that number has changed. -- Bill Moran Potential Technology http://www.potentialtech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 11:12:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dell-serv-1.phoenixmedical.co.uk (dell-serv-1.phoenixmedical.co.uk [213.38.153.186]) by hub.freebsd.org (Postfix) with SMTP id 7C22C37B405 for ; Mon, 12 Nov 2001 11:12:40 -0800 (PST) Received: from no.name.available by dell-serv-1.phoenixmedical.co.uk via smtpd (for hub.FreeBSD.org [216.136.204.18]) with SMTP; 12 Nov 2001 18:56:48 UT Received: by dell-serv-1.phoenixmedical.co.uk with Internet Mail Service (5.5.2650.21) id ; Mon, 12 Nov 2001 17:20:50 -0000 Message-ID: <99A83EE8C34AD311809C009027936117144B60@dell-serv-1.phoenixmedical.co.uk> From: Tomas Palfi To: "'freebsd-stable@FreeBSD.ORG'" Subject: jdk1.2.2 Date: Mon, 12 Nov 2001 17:20:42 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG all, trying to build jdk1.2.2 for Freebsd from 'jdk1_2_2-src[1].tar.gz' using a patch set 'freebsd-jdk122-patches-10[1].tar.gz'. i have followed the instructions as in the INSTRUCTIONS file from the patches, and everything seemed to be ok. I followed the path one to build "a normal" JDK1.2.2 (not the one for testing and development) but when it came to 'build world' it started complaining about javac not found. I have appended some of the specific details on my system as to illustrate the environment. I have checked where the javac classes are in the file system, and would like to include the whole path but how would i do that?? I had initially unpacked the source in /usr/local/java (not in /usr/local/jdk1.2.2) and set up all the environmental settings accordingly as follows: setenv ALT_BOOTDIR /usr/local/java setenv ALT_MOTIF_DIR /usr/X11R6/share/doc/openmotif setenv OPENWINHOME /usr/X11R6 unsetenv CLASSPATH unsetenv JAVA_HOME unsetenv JAVA_COMPILER HAVE_DPS no HAVE_ODBC no my installation is without odbs and dps support as it is only attempt no1, (and i can do without print screen at present time). thank you -- Tomas Palfi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 11:53: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from marvin.nildram.co.uk (marvin.nildram.co.uk [195.112.4.71]) by hub.freebsd.org (Postfix) with SMTP id 53C2137B416 for ; Mon, 12 Nov 2001 11:52:57 -0800 (PST) Received: (qmail 2881 invoked from network); 12 Nov 2001 19:52:55 -0000 Received: from muttley.gotadsl.co.uk (HELO VicNBob) (213.208.123.26) by marvin.nildram.co.uk with SMTP; 12 Nov 2001 19:52:55 -0000 Date: Mon, 12 Nov 2001 19:52:55 -0000 To: Bill Moran , Daniel Lang Cc: freebsd-stable@FreeBSD.ORG From: Matthew Whelan Subject: Re: dirpref benefit on virtual disks X-Mailer: Opera 5.11 build 904 X-Priority: 3 (Normal) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: <20011112195257.53C2137B416@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 12/11/2001 18:23:52, Bill Moran wrote: >> Now I have some huge filesystems on RAID partitions. To recreate >> all their directories involves some hassle, but I would think >> about doing it. But since these are no real but virtual disks, >> spread over a set of disks in a hardware raidbox, I'm not sure, >> if I would even benefit from the better algorithm. It sounded >> a bit like designed for filesystems on a (single?) disk? > >My thought would be that, yes, it will improve performance. If >you've got a typical 3 disk, RAID-5, a read of the directory still >causes a seek on all three disks, and if there's continual seeking >across the three disks, you'll see performance degredation. If >dirpref can layout the directory info so that it's close together, >seek time is reduces, whether on 3 disks or one. There were some benchmarks posted to this list, which confirmed this. A speedup, and a very healthy one, but maybe not -quite- as much as on a single disk, ISTR maybe a 6x improvement on rm -rf /usr/ports where you'd get 10x on a single disk. Check the archives if you want better figures than my dim memory can provide. >> Also I would like to know, if there is a certain limit of free >> space, on the disk, so that the algorithm can actually use >> the better layout? The disks have some space left, in an >> absolute way, but not that much from a relative point of view >> (like 12GB left which is just 6% minfree not taken into account). > >Have a read of the original paper on FFS (which is in /usr/share/doc >if you installed docs with FreeBSD) there is an explanation of why >8% is reserved on the drive - man tunefs comments about this as well. >I would assume that the new dirpref code needs plenty of free space >to use the optimal layout policy, but I don't know if the minimal >free space is still 8% or not, and I don't know if anyone has even >tested the new dirpref code to see if that number has changed. I'd imagine a lot would depend on how fragmented your free space is, in particular, avg. fragment size vs. avg. directory size (as configured in sysctl). People have tried tar -c/rm -rf/tar -x cycles, with wildly varying improvements - from nearly no difference to nearly as good as newfs. Matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 11:53:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-168.zoominternet.net [24.154.28.168]) by hub.freebsd.org (Postfix) with ESMTP id 4EA4037B418 for ; Mon, 12 Nov 2001 11:53:06 -0800 (PST) Received: from topperwein.dyndns.org (topperwein.dyndns.org [192.168.168.10]) by topperwein.dyndns.org (8.11.6/8.11.6) with ESMTP id fACJqwF48989 for ; Mon, 12 Nov 2001 14:52:58 -0500 (EST) (envelope-from behanna@zbzoom.net) Date: Mon, 12 Nov 2001 14:52:53 -0500 (EST) From: Chris BeHanna Reply-To: Chris BeHanna To: FreeBSD-Stable Subject: Re: png-port-upgrade gave med defunct kde In-Reply-To: <20011112155729.A34537@sr.se> Message-ID: <20011112145211.K48843-100000@topperwein.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 12 Nov 2001, Gunnar Flygt wrote: > Not really a stable question, but since the experts are here. :) > > Upgraded png from 1.0.12 to 1.2.0 That was a catastrophy for kde! No more > icons at all! Anyone else seen this? Fix? kde is 2.2.1 The fix is to rebuild KDE against the new libpng.so.5. Your currently-installed version of KDE is looking for the old libpng.so.4 and, failing to find it, will not display PNG files. -- Chris BeHanna Software Engineer (Remove "bogus" before responding.) behanna@bogus.zbzoom.net I was raised by a pack of wild corn dogs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 11:59: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-80.dsl.lsan03.pacbell.net [63.207.60.80]) by hub.freebsd.org (Postfix) with ESMTP id B2F0537B418 for ; Mon, 12 Nov 2001 11:59:04 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 4180466D03; Mon, 12 Nov 2001 11:59:04 -0800 (PST) Date: Mon, 12 Nov 2001 11:59:04 -0800 From: Kris Kennaway To: Gunnar Flygt Cc: FreeBSD Stable Subject: Re: png-port-upgrade gave med defunct kde Message-ID: <20011112115903.D28444@xor.obsecurity.org> References: <20011112155729.A34537@sr.se> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="UPT3ojh+0CqEDtpF" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011112155729.A34537@sr.se>; from flygt@sr.se on Mon, Nov 12, 2001 at 03:57:29PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --UPT3ojh+0CqEDtpF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 12, 2001 at 03:57:29PM +0100, Gunnar Flygt wrote: > Not really a stable question, but since the experts are here. :) >=20 > Upgraded png from 1.0.12 to 1.2.0 That was a catastrophy for kde! No more > icons at all! Anyone else seen this? Fix? kde is 2.2.1 When you upgrade a package you must make sure to update the entire ports collection and recompile everything which depends on that package, otherwise you'll get bitten by changes like this which break backwards-compatibility. The portupgrade port is an easy way to do this, especially for a complicated package like KDE with dozens of sub-packages. Kris --UPT3ojh+0CqEDtpF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE78CoHWry0BWjoQKURAmcrAKCJdfpMSShS0cgn2mkPDNVBJiMQlgCbBZke FTNFj47rJEBcs1UVVd/bElo= =6TWi -----END PGP SIGNATURE----- --UPT3ojh+0CqEDtpF-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 12: 3:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from prg.traveller.cz (prg.traveller.cz [193.85.2.2]) by hub.freebsd.org (Postfix) with ESMTP id 9C0A137B405 for ; Mon, 12 Nov 2001 12:03:44 -0800 (PST) Received: from prg.traveller.cz (prg.traveller.cz [193.85.2.2]) by prg.traveller.cz (EUnet.1022902037-17/pukvis) with ESMTP id fACK3gq24839 for ; Mon, 12 Nov 2001 21:03:43 +0100 (CET) Date: Mon, 12 Nov 2001 21:03:42 +0100 (CET) From: Michal Mertl To: stable@freebsd.org Subject: re: dirpref benefit on virtual disk Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I tried to do some basic "real-world" benchmarks of dirpref on Adaptec 3210S RAID HW and it still makes huge difference. Go for it. -- Michal Mertl mime@traveller.cz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 13: 3:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from herbelot.dyndns.org (d211.dhcp212-198-26.noos.fr [212.198.26.211]) by hub.freebsd.org (Postfix) with ESMTP id AF6E937B405 for ; Mon, 12 Nov 2001 13:03:24 -0800 (PST) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id WAA40659; Mon, 12 Nov 2001 22:31:37 +0100 (CET) (envelope-from thierry@herbelot.com) Message-ID: <3BF038EA.B5586CD8@herbelot.com> Date: Mon, 12 Nov 2001 22:02:34 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Gunnar Flygt , FreeBSD Stable Subject: Re: png-port-upgrade gave med defunct kde References: <20011112155729.A34537@sr.se> <20011112115903.D28444@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > > Upgraded png from 1.0.12 to 1.2.0 That was a catastrophy for kde! No more > > icons at all! Anyone else seen this? Fix? kde is 2.2.1 I just killed my 4-Stable machine by portupgrad-ing it : the result was a total mess (anyway, a full reinstall was needed) this was the same libpng problem as Gunnar -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 13:31: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.wanadoo.nl (smtp1.wanadoo.nl [194.134.35.136]) by hub.freebsd.org (Postfix) with ESMTP id 8435137B41B for ; Mon, 12 Nov 2001 13:30:58 -0800 (PST) Received: from ams-gw.sohara.org (p1391.vcu.wanadoo.nl [194.134.170.116]) by smtp.wanadoo.nl (8.11.3/8.11.3) with SMTP id fACLUpV11989; Mon, 12 Nov 2001 22:30:52 +0100 (MET) Date: Mon, 12 Nov 2001 22:30:44 +0100 From: "Steve O'Hara-Smith" To: Michael Lucas Cc: freebsd-stable@FreeBSD.ORG Subject: Re: KDE init [was RE: DCOP server problem...] Message-Id: <20011112223044.0e15ec9b.steve@sohara.org> In-Reply-To: <20011112093211.A28224@blackhelicopters.org> References: <20011109180124.31471.qmail@web14103.mail.yahoo.com> <200111100718.fAA7I9522856@apollo.backplane.com> <20011112093211.A28224@blackhelicopters.org> X-Mailer: Sylpheed version 0.6.5 (GTK+ 1.2.10; i386--freebsd4.4) X-Face: %]+HVL}K`P8>+8ZcY-WGHP6j@&mxMo9JH6_WdgIgUGH)JX/usO0%jy7T~IVgqjumD^OBqX,Kv^-GM6mlw(fI^$"QRKyZ$?xx/ Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 12 Nov 2001 09:32:12 -0500 Michael Lucas wrote: > Matt, > > Check out /usr/ports/sysutils/portupgrade. Automatic port & port > dependency upgrading, fully recursive. Thanks for mentioning this, I installed portupgrade a long time ago and strangely never did portupgrade portupgrade. That tool has changed a lot since it first appeared. Anyone with an old version should definitely upgrade it (ruby too if it's as old as mine was). -- C:>WIN | Directable Mirrors The computer obeys and wins. |A Better Way To Focus The Sun You lose and Bill collects. | licenses available - see: | http://www.sohara.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 13:32:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from volatile.chemikals.org (ci391991-a.grnvle1.sc.home.com [24.37.154.83]) by hub.freebsd.org (Postfix) with ESMTP id D18D337B405 for ; Mon, 12 Nov 2001 13:32:41 -0800 (PST) Received: (from morganw@localhost) by volatile.chemikals.org (8.11.5/8.11.5) id fACLWNk39305; Mon, 12 Nov 2001 16:32:23 -0500 (EST) (envelope-from morganw) Date: Mon, 12 Nov 2001 16:32:23 -0500 (EST) From: Wesley Morgan To: Michael Lucas Cc: Matthew Dillon , Galen Sampson , Subject: Re: KDE init [was RE: DCOP server problem...] In-Reply-To: <20011112093211.A28224@blackhelicopters.org> Message-ID: <20011112163059.W39202-100000@volatile.chemikals.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The next time KDE screws up your fonts or starts acting screwy, go into /tmp and rm -rf all the old DCOP / KDE stuff. That usually fixes it for me (I used to use a mfs /tmp, but that seems to be broken in -current). On Mon, 12 Nov 2001, Michael Lucas wrote: > Matt, > > Check out /usr/ports/sysutils/portupgrade. Automatic port & port > dependency upgrading, fully recursive. > > Took me about thirty minutes to set up. My desktop is three years old > and has been manually upgraded, patched, etc, repeatedly. And > portupgrade upgraded every port to the latest version, cleaned up all > sorts of old crap, etc. Highly recommended. > > Tutorial coming to onlamp.com RSN (I believe later this month). > > On Fri, Nov 09, 2001 at 11:18:09PM -0800, Matthew Dillon wrote: > > > > : > > :Hello all, > > : I have seen quite a few posts in here about problems with KDE. I personally > > :still have the problem that KDE will show its splash screen, get to > > :"initializing peripherals" and just sit there. I have noticed a few PR's, > > :etc., and KDE's bug database had at least on message claiming this to be a > > :problem with FreeBSD's threads. I have gone so far as to remove every port > > :that KDE depends on (except X) and rebuilt through the ports, but I just > > :haven't had any luck. I am running Xfree86 3.3.6 (built from ports) over a > > :year ago, and KDE2 cvsuped many times, but the latest has been 7 days ago. Any > > :known workarounds/fixes would be most appreciated. > > : > > :regards, > > :Galen Sampson > > > > I'm having weird problems with kde2 as well.. it keeps screwing up > > the fonts. It forgets about font families, changes my defaults, and > > does all sorts of other nasty things. > > > > I noticed that when I did a 'make' in the port for kde2, that it didn't > > bother updating older kde2-related libraries that were already installed > > but out of date, so it was running the kde2 desktop binaries against > > older shared libraries. It took a while to go through all the ports > > and deinstall them and now I am rebuilding the whole thing from scratch > > again. Maybe it will work better with all the shared libs synced up. > > > > I've actually noticed this with ports before... there needs to be a > > make target to tell ports to upgrade everything that is out of date or > > something like that. I dunno. > > > > -Matt > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@chemikals.org _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 13:45:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id CDD8837B416 for ; Mon, 12 Nov 2001 13:45:39 -0800 (PST) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id fACLXQd31109; Mon, 12 Nov 2001 13:33:26 -0800 (PST) Message-Id: <200111122133.fACLXQd31109@ptavv.es.net> To: Thierry Herbelot Cc: Kris Kennaway , Gunnar Flygt , FreeBSD Stable Subject: Re: png-port-upgrade gave med defunct kde In-reply-to: Your message of "Mon, 12 Nov 2001 22:02:34 +0100." <3BF038EA.B5586CD8@herbelot.com> Date: Mon, 12 Nov 2001 13:33:26 -0800 From: "Kevin Oberman" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Date: Mon, 12 Nov 2001 22:02:34 +0100 > From: Thierry Herbelot > Sender: owner-freebsd-stable@FreeBSD.ORG > > > > > > > Upgraded png from 1.0.12 to 1.2.0 That was a catastrophy for kde! No more > > > icons at all! Anyone else seen this? Fix? kde is 2.2.1 > > I just killed my 4-Stable machine by portupgrad-ing it : the result was > a total mess (anyway, a full reinstall was needed) > > this was the same libpng problem as Gunnar I hit the same problem. The cause, in my case, was a change in the function of certain options on portupgrade. The -u flag will cause older versions of shared libraries to be de-installed. I think that it used to de-install old versions of the software. In any case, I did a "portupgrade -Rru libpng" and lost the version 4 sharable. (I recovered by getting the same sharable from another system.) By default, portupgrade does not delete older versions of sharable libraries. Seems odd that it was libpng and only libpng that seems to have bitten several people, though. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 13:49:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by hub.freebsd.org (Postfix) with ESMTP id 051F537B405 for ; Mon, 12 Nov 2001 13:49:14 -0800 (PST) Received: from lerami.lerctr.org (localhost [127.0.0.1]) by lerami.lerctr.org (8.12.1/8.12.1/20010730/$Revision: 1.25 $) with ESMTP id fACLmiGw013111; Mon, 12 Nov 2001 15:48:44 -0600 (CST) Received: (from ler@localhost) by lerami.lerctr.org (8.12.1/8.12.1/Submit) id fACLmixP013110; Mon, 12 Nov 2001 21:48:44 GMT Date: Mon, 12 Nov 2001 15:48:44 -0600 From: Larry Rosenman To: Kevin Oberman Cc: Thierry Herbelot , Kris Kennaway , Gunnar Flygt , FreeBSD Stable Subject: Re: png-port-upgrade gave med defunct kde Message-ID: <20011112154844.A13078@lerami.lerctr.org> References: <3BF038EA.B5586CD8@herbelot.com> <200111122133.fACLXQd31109@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200111122133.fACLXQd31109@ptavv.es.net> User-Agent: Mutt/1.3.23i X-Mailer: Mutt http://www.mutt.org/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Kevin Oberman [011112 15:46]: > > Date: Mon, 12 Nov 2001 22:02:34 +0100 > > From: Thierry Herbelot > > Sender: owner-freebsd-stable@FreeBSD.ORG > > > > > > > > > > Upgraded png from 1.0.12 to 1.2.0 That was a catastrophy for kde! No more > > > > icons at all! Anyone else seen this? Fix? kde is 2.2.1 > > > > I just killed my 4-Stable machine by portupgrad-ing it : the result was > > a total mess (anyway, a full reinstall was needed) > > > > this was the same libpng problem as Gunnar > > I hit the same problem. The cause, in my case, was a change in the > function of certain options on portupgrade. The -u flag will cause > older versions of shared libraries to be de-installed. I think that it > used to de-install old versions of the software. In any case, I did a > "portupgrade -Rru libpng" and lost the version 4 sharable. (I > recovered by getting the same sharable from another system.) > > By default, portupgrade does not delete older versions of sharable > libraries. > > Seems odd that it was libpng and only libpng that seems to have bitten > several people, though. I think some of the issue is that some of the Gnome ports don't declare ALL of their dependencies, so things break in wierd ways. > > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 14: 9:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rutger.owt.com (rutger.owt.com [204.118.6.16]) by hub.freebsd.org (Postfix) with ESMTP id D815437B405 for ; Mon, 12 Nov 2001 14:09:22 -0800 (PST) Received: from owt.com (owt-207-41-94-232.owt.com [207.41.94.232]) by rutger.owt.com (8.9.3/8.9.3) with ESMTP id LAA22831; Mon, 12 Nov 2001 11:26:42 -0800 Message-ID: <3BF02271.7070907@owt.com> Date: Mon, 12 Nov 2001 11:26:41 -0800 From: Kent Stewart User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Gunnar Flygt Cc: FreeBSD Stable Subject: Re: png-port-upgrade gave med defunct kde References: <20011112155729.A34537@sr.se> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Gunnar Flygt wrote: > Not really a stable question, but since the experts are here. :) > > Upgraded png from 1.0.12 to 1.2.0 That was a catastrophy for kde! No more > icons at all! Anyone else seen this? Fix? kde is 2.2.1 Anyone who has done this has seen it. There are times when you will believe that png is used by everything. Look at the port portupgrade. It is designed to handle situations like this. Kent > > -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://users.owt.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 14:10: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from moya.lambermont.dyndns.org (e165253.upc-e.chello.nl [213.93.165.253]) by hub.freebsd.org (Postfix) with ESMTP id 7F1F437B417 for ; Mon, 12 Nov 2001 14:09:56 -0800 (PST) Received: by moya.lambermont.dyndns.org (Postfix, from userid 1001) id CF13A36415; Mon, 12 Nov 2001 23:09:51 +0100 (CET) Date: Mon, 12 Nov 2001 23:09:51 +0100 To: Tomas Palfi Cc: freebsd-stable@FreeBSD.ORG Subject: Re: jdk1.2.2 Message-ID: <20011112230951.B24759@moya.lambermont.dyndns.org> References: <99A83EE8C34AD311809C009027936117144B60@dell-serv-1.phoenixmedical.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <99A83EE8C34AD311809C009027936117144B60@dell-serv-1.phoenixmedical.co.uk>; from tpalfi@phoenixmedical.co.uk on Mon, Nov 12, 2001 at 05:20:42PM -0000 From: hans@lambermont.dyndns.org (H) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Tomas Palfi wrote: > trying to build jdk1.2.2 for Freebsd from 'jdk1_2_2-src[1].tar.gz' using a > patch set 'freebsd-jdk122-patches-10[1].tar.gz'. i have followed the Are you building it from one of the java sdk trees in the ports collection ? (If not have a look at /usr/ports/java/jdk1* , a 'make install' as root in /usr/ports/java/jdk12-beta/ or in /usr/ports/java/jdk13/ should get you further.) -- Hans To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 14:42:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailc.telia.com (mailc.telia.com [194.22.190.4]) by hub.freebsd.org (Postfix) with ESMTP id DFFF037B416 for ; Mon, 12 Nov 2001 14:41:44 -0800 (PST) Received: from d1o907.telia.com (d1o907.telia.com [195.252.38.241]) by mailc.telia.com (8.11.6/8.11.6) with ESMTP id fACMfhu13426 for ; Mon, 12 Nov 2001 23:41:43 +0100 (CET) Received: from ludd.luth.se (h216n2fls21o907.telia.com [213.66.203.216]) by d1o907.telia.com (8.8.8/8.8.8) with ESMTP id XAA14018 for ; Mon, 12 Nov 2001 23:41:41 +0100 (CET) Message-ID: <3BF05067.3040902@ludd.luth.se> Date: Mon, 12 Nov 2001 23:42:47 +0100 From: Joachim =?ISO-8859-1?Q?Str=F6mbergson?= Organization: Acne User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.5) Gecko/20011104 X-Accept-Language: en-US MIME-Version: 1.0 To: stable Subject: Still FPE-problems with pgp5 on Athlon Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Aloha! A While ago I wrote about my problems getting pgp to work on Athlnon machines running 4.3-STABLE. Someone suggested then to upgrade to 4.4-STABLE. After trying out varoius things (and generally be busy with other things) I know selected one of the machines. I Moved it to 4.4-STABLE (without any problems) and the proceeded to install the pgp5 port in /usr/ports/security Unfortunately, I still receive a signal 8 (FPE exception) as soon as I try to do anything with pgp. Some command logs: js@marge.springfield.se:/usr/home/js>pgpk -l Type Bits KeyID Created Expires Algorithm Use sec+ 1024 0x1F339A35 2001-11-12 ---------- DSS Sign & Encrypt sub 4096 0xC7DB775C 2001-11-12 ---------- Diffie-Hellman uid Joachim Strombergson 1 matching key found Received signal 8. ^C Stopped at user request. It really hangs pretty bad. I need to do CTRL-Z and do a "kill -9" on the process. It doesen't matter if I run this as user or as root. How do I investigate this further? I will try to do some debugging and/or tracing, but any other ideas here? I have verified that the machine can run floating point code. Also, we have a bunch of these machines and all Athlon machines are having this problem. Any suggestions, directions or helt would be greatly appreciated. Here are the uname, make.conf, kernel configuration and dmesg information: uname: ------ js@marge.springfield.se:/usr/home/js>uname -a FreeBSD marge.springfield.se 4.4-STABLE FreeBSD 4.4-STABLE #0: Mon Nov 12 13:11:15 CET 2001 root@marge.springfield.se:/usr/obj/usr/src/sys/MARGE i386 make.conf: ---------- # $FreeBSD: src/etc/defaults/make.conf,v 1.97.2.45 2001/03/22 01:43:39 ps Exp $ # # NOTE: Please would any committer updating this file also update the # make.conf(5) manual page, if necessary, which is located in # src/share/man/man5/make.conf.5. # # This file, if present, will be read by make (see /usr/share/mk/sys.mk). # It allows you to override macro definitions to make without changing # your source tree, or anything the source tree installs. # # This file must be in valid Makefile syntax. # # You have to find the things you can put here in the Makefiles and # documentation of the source tree. # # # The CPUTYPE variable controls which processor should be targetted for # generated code. This controls processor-specific optimizations in # certain code (currently only OpenSSL) as well as modifying the value # of CFLAGS to contain the appropriate optimization directive to gcc. # The automatic setting of CFLAGS may be overridden using the # NO_CPU_CFLAGS variable below. # Currently the following CPU types are recognised: # Intel x86 architecture: # (AMD CPUs) k7 k6-2 k6 k5 # (Intel CPUs) p4 p3 p2 i686 i586/mmx i586 i486 i386 # Alpha/AXP architecture: ev6 pca56 ev56 ev5 ev45 ev4 # # If you experience any problems after setting this flag, please unset # it again before submitting a bug report or attempting to modify code. # It may be that certain types of software will become unstable after being # compiled with processor-specific (or higher - see below) optimization flags. # If in doubt, do not set CPUTYPE or CFLAGS to non-default values. # #CPUTYPE=k7 # #NO_CPU_CFLAGS= true # Don't add -march= to CFLAGS automatically #NO_CPU_COPTFLAGS=true # Don't add -march= to COPTFLAGS automatically # # CFLAGS controls the compiler settings used when compiling C code. # Note that optimization settings above -O (-O2, ...) are not recommended # or supported for compiling the world or the kernel - please revert any # nonstandard optimization settings to "-O" before submitting bug reports # to the developers. # Note also that at this time the -O2 setting is known to produce BROKEN # CODE on the Alpha platform. # CFLAGS= -O -pipe # # CXXFLAGS controls the compiler settings used when compiling C++ code. # Note that CXXFLAGS is initially set to the value of CFLAGS. If you wish # to add to CXXFLAGS value, "+=" must be used rather than "=". Using "=" # alone will remove the often needed contents of CFLAGS from CXXFLAGS. # CXXFLAGS+= -fmemoize-lookups -fsave-memoized # # BDECFLAGS are a set of gcc warning settings that Bruce Evans has suggested # for use in developing FreeBSD and testing changes. They can be used by # putting "CFLAGS+=${BDECFLAGS}" in /etc/make.conf. # BDECFLAGS= -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align \ -Wcast-qual -Wchar-subscripts -Wconversion -Winline \ -Wmissing-prototypes -Wnested-externs -Wpointer-arith \ -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings # # To compile just the kernel with special optimizations, you should use # this instead of CFLAGS (which is not applicable to kernel builds anyway). # There is very little to gain by using higher optimization levels, and doing # so can cause problems. # #COPTFLAGS= -O -pipe # # Compare before install #INSTALL=install -C # # To enable installing suidperl with the setuid bit turned on #ENABLE_SUIDPERL= true # # To build perl with thread support #PERL_THREADED= true # # To build ppp with normal permissions #PPP_NOSUID= true # # To enable installing ssh(1) with the setuid bit turned on #ENABLE_SUID_SSH= true # # To avoid building various parts of the base system: #NO_CVS= true # do not build CVS #NO_BIND= true # do not build BIND #NO_FORTRAN= true # do not build g77 and related libraries #NO_LPR= true # do not build lpr and related programs #NO_MAILWRAPPER=true # do not build the mailwrapper(8) MTA selector #NO_MODULES= true # do not build modules with the kernel #NO_OBJC= true # do not build Objective C support #NO_OPENSSH= true # do not build OpenSSH #NO_OPENSSL= true # do not build OpenSSL (implies NO_OPENSSH) #NO_SENDMAIL= true # do not build sendmail and related programs #NO_SHAREDOCS= true # do not build the 4.4BSD legacy docs #NO_TCSH= true # do not build and install /bin/csh (which is tcsh) #NO_X= true # do not compile in XWindows support (e.g. doscmd) #NOCRYPT= true # do not build any crypto code #NODESCRYPTLINKS=true # do not replace libcrypt -> libscrypt links #NOGAMES= true # do not build games (games/ subdir) #NOINFO= true # do not make or install info files #NOLIBC_R= true # do not build libc_r (re-entrant version of libc) #NOPERL= true # do not build perl. Disables OpenSSL optimizations #NOPROFILE= true # Avoid compiling profiled libraries #NOSECURE= true # do not build crypto code in secure/ subdir #NOSHARE= true # do not go into the share subdir #NOUUCP= true # do not build uucp related programs # # To build the OpenSSL manpages, uncomment the following. These are not # built by default because they clobber a number of system manpages with # manpages describing parts of the OpenSSL toolkit, including passwd(1), # err(3), md5(3), and others. # #WANT_OPENSSL_MANPAGES= true # # To build sys/modules when building the world (our old way of doing things) #MODULES_WITH_WORLD=true # do not build modules when building kernel # # # The following controls building optional IDEA code in libcrypto and # certain ports. Patents are involved - you must not use this unless # you either have a license or fall within patent 'fair use' # provisions. # # *** It is YOUR RESPONSIBILITY to determine if you can use this! *** # # IDEA is patented in the USA and many european countries - thought to # be OK to use for any non-commercial use. This is optional. #MAKE_IDEA= YES # IDEA (128 bit symmetric encryption) # # To avoid running MAKEDEV all on /dev during install: #NO_MAKEDEV= true # # If you do not want unformatted manual pages to be compressed # when they are installed: # #NOMANCOMPRESS= true # # # If you want the "compat" shared libraries installed as part of your normal # builds, uncomment these: # #COMPAT1X= yes #COMPAT20= yes #COMPAT21= yes #COMPAT22= yes #COMPAT3X= yes #COMPAT4X= yes # # # If you do not want additional documentation (some of which are # a few hundred KB's) for ports to be installed: # #NOPORTDOCS= true # # # Default format for system documentation, depends on your printer. # Set this to "ascii" for simple printers or screen # #PRINTERDEVICE= ps # # # How long to wait for a console keypress before booting the default kernel. # This value is approximately in milliseconds. Keypresses are accepted by the # BIOS before booting from disk, making it possible to give custom boot # parameters even when this is set to 0. # #BOOTWAIT=0 #BOOTWAIT=30000 # # By default, the system will always use the keyboard/video card as system # console. However, the boot blocks may be dynamically configured to use a # serial port in addition to or instead of the keyboard/video console. # # By default we use COM1 as our serial console port *if* we're going to use # a serial port as our console at all. Alter as necessary. # # COM1: = 0x3F8, COM2: = 0x2F8, COM3: = 0x3E8, COM4: = 0x2E8 # #BOOT_COMCONSOLE_PORT= 0x3F8 # # The default serial console speed is 9600. Set the speed to a larger value # for better interactive response. # #BOOT_COMCONSOLE_SPEED= 115200 # # By default the 'pxeboot' loader retrieves the kernel via NFS. Defining # this and recompiling /usr/src/sys/boot will cause it to retrieve the kernel # via TFTP. This allows pxeboot to load a custom BOOTP diskless kernel yet # still mount the server's '/' (i.e. rather then load the server's kernel). # #LOADER_TFTP_SUPPORT= YES # # By default, this points to /usr/X11R6 for XFree86 releases 3.0 or earlier. # If you have a XFree86 from before 3.0 that has the X distribution in # /usr/X386, you want to uncomment this. # #X11BASE= /usr/X386 # # # If you have Motif on your system, uncomment this. # #HAVE_MOTIF= yes #MOTIF_STATIC= yes # # If the default location of the Motif library (specified below) is NOT # appropriate for you, uncomment this and change it to the correct value. # If your motif is in ${X11BASE}/lib, you don't need to touch this line. # #MOTIFLIB= -L${X11BASE}/lib -lXm # # # If you're resident in the USA, this will help various ports to determine # whether or not they should attempt to comply with the various U.S. # export regulations on certain types of software which do not apply to # anyone else in the world. # #USA_RESIDENT= YES # # # Override "don't install a port that's already installed" behavior. # One might wish to do this for ports debugging or to unconditionally # reinstall a set of suspect/broken ports. # #FORCE_PKG_REGISTER= YES # # # If you're behind a firewall and need FTP or HTTP proxy services for # ports collection fetching to work, the following examples give the # necessary syntax. See the fetch(3) man page for details. # #FTP_PROXY= 10.0.0.1:21 #HTTP_PROXY= 10.0.0.1:80 # # # Port master sites. # # If you want your port fetches to go somewhere else than the default # (specified below) in case the distfile/patchfile was not found, # uncomment this and change it to a location nearest you. (Don't # remove the "/${DIST_SUBDIR}/" part.) # #MASTER_SITE_BACKUP?= \ # ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR}/ # # If you want your port fetches to check the above site first (before # the MASTER_SITES specified in the port Makefiles), uncomment the # line below. You can also change the right side to point to wherever # you want. # #MASTER_SITE_OVERRIDE?= ${MASTER_SITE_BACKUP} # # Some ports use a special variable to point to a collection of # mirrors of well-known software archives. If you have a mirror close # to you, uncomment any of the following lines and change it to that # address. (Don't remove the "/%SUBDIR%/" part.) # # Note: the right hand sides of the following lines are only for your # information. For a full list of default sites, take a look at # bsd.sites.mk. # #MASTER_SITE_XCONTRIB= ftp://ftp.x.org/contrib/%SUBDIR%/ #MASTER_SITE_XFREE= ftp://ftp.freesoftware.com/pub/XFree86/%SUBDIR%/source/ #MASTER_SITE_GNU= ftp://ftp.gnu.org/gnu/%SUBDIR%/ #MASTER_SITE_PERL_CPAN= ftp://ftp.digital.com/pub/plan/perl/CPAN/modules/by-module/%SUBDIR%/ #MASTER_SITE_TEX_CTAN= ftp://ftp.tex.ac.uk/tex-archive/%SUBDIR%/ #MASTER_SITE_SUNSITE= ftp://metalab.unc.edu/pub/Linux/%SUBDIR%/ #MASTER_SITE_RINGSERVER= ftp://ring.ocn.ad.jp/pub/%SUBDIR%/ #MASTER_SITE_KDE= ftp://ftp.kde.org/pub/kde/%SUBDIR%/ #MASTER_SITE_COMP_SOURCES= ftp://gatekeeper.dec.com/pub/usenet/comp.sources.%SUBDIR%/ #MASTER_SITE_GNOME= ftp://ftp.gnome.org/pub/GNOME/sources/%SUBDIR%/ #MASTER_SITE_AFTERSTEP= ftp://ftp.afterstep.org/%SUBDIR%/ #MASTER_SITE_WINDOWMAKER= ftp://ftp.windowmaker.org/pub/%SUBDIR%/ #MASTER_SITE_MOZILLA= ftp://ftp.yggdrasil.com/mirrors/site/ftp.mozilla.org/pub/%SUBDIR%/ #MASTER_SITE_XEMACS= ftp://ftp.sunsite.utk.edu/pub/xemacs/%SUBDIR%/ #MASTER_SITE_TCLTK= ftp://ftp.uu.net/languages/tcl/%SUBDIR%/ #MASTER_SITE_RUBY= ftp://ftp.fu-berlin.de/unix/languages/ruby/%SUBDIR%/ # # Also it is highly recommended that you configure MASTER_SORT_REGEX # to choose better mirror sites for you. List awk(1)-style regular # expressions separated by space so MASTER_SITES will be sorted in # that order. The following example is for Japanese users; change # "jp" part to your ccTLD ("de", "ru", "uk", etc.) or the domain names # of your nearest/upstream networks to meet your needs. # #MASTER_SORT_REGEX?= ^file: ^ftp://ftp\.FreeBSD\.org/pub/FreeBSD/ports/local-distfiles/ ://[^/]*\.jp/ ://[^/]*\.jp\. # # Kerberos IV # If you want KerberosIV (KTH eBones), define this: # #MAKE_KERBEROS4= yes # # # Kerberos 5 # If you want KerberosIV (KTH Heimdal), define this: # #MAKE_KERBEROS5= yes # # # Kerberos5 # If you want to install MIT Kerberos5 port somewhere other than /usr/local, # define this (this is also used to tell ssh1 that kerberos is needed): # #KRB5_HOME= /usr/local # # # CVSup update flags. Edit SUPFILE settings to reflect whichever distribution # file(s) you use on your site (see /usr/share/examples/cvsup/README for more # information on CVSup and these files). To use, do "make update" in /usr/src. # #SUP_UPDATE= yes # #SUP= /usr/local/bin/cvsup #SUPFLAGS= -g -L 2 #SUPHOST= cvsup.uk.FreeBSD.org #SUPFILE= /usr/share/examples/cvsup/stable-supfile #SUPFILE1= /usr/share/examples/cvsup/secure-supfile #PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile #DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile # # top(1) uses a hash table for the user names. The size of this hash # can be tuned to match the number of local users. The table size should # be a prime number approximately twice as large as the number of lines in # /etc/passwd. The default number is 20011. # #TOP_TABLE_SIZE= 101 # # Documentation # # The list of languages and encodings to build and install # #DOC_LANG= en_US.ISO_8859-1 ru_RU.KOI8-R # # # sendmail # # The following sets the default m4 configuration file to use at # install time. Use with caution as a make install will overwrite # any existing /etc/mail/sendmail.cf. Note that SENDMAIL_CF is now # deprecated. The value should be a fully qualified path name. # #SENDMAIL_MC=/etc/mail/myconfig.mc # # If you need to build additional .cf files during a make buildworld, # include the full paths to the .mc files in SENDMAIL_ADDITIONAL_MC. # #SENDMAIL_ADDITIONAL_MC=/etc/mail/foo.mc /etc/mail/bar.mc # # Setting the following variables modifes the build environment for # sendmail and its related utilities. For example, SASL support can be # added with settings such as: # # SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL # SENDMAIL_LDFLAGS=-L/usr/local/lib # SENDMAIL_LDADD=-lsasl # # Note: If you are using Cyrus SASL with other applications which require # access to the sasldb file, you should add '-D_FFR_UNSAFE_SASL' to # SENDMAIL_CFLAGS. Also, add the following to your sendmail.mc file: # # define(`confDONT_BLAME_SENDMAIL',`GroupReadableSASLFile') # #SENDMAIL_CFLAGS= #SENDMAIL_LDFLAGS= #SENDMAIL_LDADD= #SENDMAIL_DPADD= kernel configuration: --------------------- #======================================================================= # # MARGE # ----- # # Kernel configuration file for the Kwikemart server. # # # (c) 2001 InformAsic AB # # Revision history: # 2001-06-26: Initial revision. Removal of APM to fix the # microuptime creeps backwards problem. Also, # removal of unneeded devices (SCSI for example) # # #======================================================================= machine i386 cpu I686_CPU ident MARGE maxusers 32 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O device isa device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # SCSI Controllers device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices device amd # AMD 53C974 (Tekram DC-390(T)) device isp # Qlogic family device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets) options SYM_SETUP_LP_PROBE_MAP=0x40 # Allow ncr to attach legacy NCR devices when # both sym and ncr are configured device adv0 at isa? device adw device bt0 at isa? device aha0 at isa? device aic0 at isa? device ncv # NCR 53C500 device nsp # Workbit Ninja SCSI-3 device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # RAID controllers interfaced to the SCSI subsystem device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID device dpt # DPT Smartcache - See LINT for options! device mly # Mylex AcceleRAID/eXtremeRAID # RAID controllers device aac # Adaptec FSA RAID, Dell PERC2/PERC3 device ida # Compaq Smart RAID device amr # AMI MegaRAID device mlx # Mylex DAC960 family device twe # 3ware Escalade # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) #device apm0 at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support device card device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd0000 device pcic1 at isa? irq 0 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') device fxp # Intel EtherExpress PRO/100B (82557, 82558) device tx # SMC 9432TX (83c170 ``EPIC'') device vx # 3Com 3c590, 3c595 (``Vortex'') device wx # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device dc # DEC/Intel 21143 and various workalikes device pcn # AMD Am79C79x PCI 10/100 NICs device rl # RealTek 8129/8139 device sf # Adaptec AIC-6915 (``Starfire'') device sis # Silicon Integrated Systems SiS 900/SiS 7016 device ste # Sundance ST201 (D-Link DFE-550TX) device tl # Texas Instruments ThunderLAN device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 device ex device ep device fe0 at isa? port 0x300 # Xircom Ethernet device xe # PRISM I IEEE 802.11b wireless NIC. device awi # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attachment needed # and resources will always be dynamically assigned by the pccard code. device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those parameters here. device an # The probe order of these is presently determined by i386/isa/isa_compat.c. device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 device lnc0 at isa? port 0x280 irq 10 drq 0 device cs0 at isa? port 0x300 device sn0 at isa? port 0x300 irq 10 # Pseudo devices - the number indicates how many units to allocate. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" pseudo-device gif 4 # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device uscanner # Scanners # USB Ethernet, requires mii device aue # ADMtek USB ethernet device cue # CATC USB ethernet device kue # Kawasaki LSI USB ethernet # Sound For PnP/PCI sound cards device pcm #======================================================================= # EOF MARGE #======================================================================= dmesg output: -------------- Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.4-STABLE #0: Mon Nov 12 13:11:15 CET 2001 root@marge.springfield.se:/usr/obj/usr/src/sys/MARGE Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1200051335 Hz CPU: AMD Athlon(tm) Processor (1200.05-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc0440000<,AMIE,DSP,3DNow!> real memory = 536805376 (524224K bytes) config> di pcic0 config> di sn0 config> di lnc0 config> di ie0 config> di fe0 config> di ed0 config> di cs0 config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 517853184 (505716K bytes) Preloaded elf kernel "kernel" at 0xc04bd000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc04bd09c. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 9 entries at 0xc00fde50 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: at 0.0 irq 10 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: Logitech USB Receiver, rev 1.10/9.10, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. uhci1: port 0xd800-0xd81f irq 11 at device 7.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered fxp0: port 0xdc00-0xdc3f mem 0xda000000-0xda01ffff,0xda020000-0xda020fff irq 11 at device 8.0 on pci0 fxp0: Ethernet address 00:02:b3:33:c8:00 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: port 0xe000-0xe03f irq 12 at device 13.0 on pci0 pcib1: on motherboard pci2: on pcib1 orm0: -- Med vänlig hälsning, Cheers! Joachim Strömbergson ============================================================================ Joachim Strömbergson - ASIC designer, nice to *cute* animals. snail: phone: mail & web: Sävenäsgatan 5A +46 31 - 27 98 47 watchman@ludd.luth.se 416 72 Göteborg +46 733 75 97 02 www.ludd.luth.se/~watchman ============================================================================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 15: 4:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by hub.freebsd.org (Postfix) with ESMTP id 73E3937B417 for ; Mon, 12 Nov 2001 15:04:17 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtpzilla2.xs4all.nl (8.12.0/8.12.0) with ESMTP id fACN4Foo033739; Tue, 13 Nov 2001 00:04:15 +0100 (CET) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fACN4FY34425; Tue, 13 Nov 2001 00:04:15 +0100 (CET) (envelope-from wkb) Date: Tue, 13 Nov 2001 00:04:15 +0100 From: Wilko Bulte To: =?iso-8859-1?Q?Joachim_Str=F6mbergson?= Cc: stable Subject: Re: Still FPE-problems with pgp5 on Athlon Message-ID: <20011113000415.A34365@freebie.xs4all.nl> References: <3BF05067.3040902@ludd.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <3BF05067.3040902@ludd.luth.se>; from watchman@ludd.luth.se on Mon, Nov 12, 2001 at 11:42:47PM +0100 X-OS: FreeBSD 4.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Nov 12, 2001 at 11:42:47PM +0100, Joachim Strömbergson wrote: > to do anything with pgp. Some command logs: > > > > js@marge.springfield.se:/usr/home/js>pgpk -l > Type Bits KeyID Created Expires Algorithm Use > sec+ 1024 0x1F339A35 2001-11-12 ---------- DSS Sign & Encrypt > sub 4096 0xC7DB775C 2001-11-12 ---------- Diffie-Hellman > uid Joachim Strombergson > > 1 matching key found > > Received signal 8. > ^C > Stopped at user request. > > > It really hangs pretty bad. I need to do CTRL-Z and do a "kill -9" on the > process. > > It doesen't matter if I run this as user or as root. > > How do I investigate this further? I will try to do some debugging and/or > tracing, but any other ideas here? > > I have verified that the machine can run floating point code. Also, we > have a bunch of these machines and all Athlon machines are having this > problem. But not mine: wb ~: uname -a FreeBSD freebie.xs4all.nl 4.4-STABLE FreeBSD 4.4-STABLE #1: Mon Nov 5 20:08:48 CET 2001 root@freebie.xs4all.nl:/usr/src/sys/compile/FREEBIE i386 wb ~: pgpk -l Type Bits KeyID Created Expires Algorithm Use pub 1024 0x95B4F211 1999-03-12 ---------- DSS Sign & Encrypt sub 2048 0x3DBCD155 1999-03-12 ---------- Diffie-Hellman uid Nicholas Sayer pub 1024 0x95DB7985 1993-11-19 ---------- RSA Sign & Encrypt uid Nicholas Sayer 2 matching keys found wb ~: and freebie# dmesg Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.4-STABLE #1: Mon Nov 5 20:08:48 CET 2001 root@freebie.xs4all.nl:/usr/src/sys/compile/FREEBIE Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) Processor (700.03-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x621 Stepping = 1 Features=0x183f9ff AMD Features=0xc0400000 real memory = 268353536 (262064K bytes) avail memory = 257605632 (251568K bytes) Preloaded elf kernel "kernel" at 0xc0393000. etc. -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 15: 7:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-168.zoominternet.net [24.154.28.168]) by hub.freebsd.org (Postfix) with ESMTP id 1A5F437B416 for ; Mon, 12 Nov 2001 15:07:46 -0800 (PST) Received: from topperwein.dyndns.org (topperwein.dyndns.org [192.168.168.10]) by topperwein.dyndns.org (8.11.6/8.11.6) with ESMTP id fACN7iF49448 for ; Mon, 12 Nov 2001 18:07:44 -0500 (EST) (envelope-from behanna@zbzoom.net) Date: Mon, 12 Nov 2001 18:07:38 -0500 (EST) From: Chris BeHanna Reply-To: Chris BeHanna To: FreeBSD-Stable Subject: Re: Still FPE-problems with pgp5 on Athlon In-Reply-To: <3BF05067.3040902@ludd.luth.se> Message-ID: <20011112180507.Y49365-100000@topperwein.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 12 Nov 2001, Joachim Strömbergson wrote: > Aloha! > > A While ago I wrote about my problems getting pgp to work on Athlnon > machines running 4.3-STABLE. > > Someone suggested then to upgrade to 4.4-STABLE. After trying out varoius > things (and generally be busy with other things) I know selected one of > the machines. I Moved it to 4.4-STABLE (without any problems) and the > proceeded to install the pgp5 port in /usr/ports/security > > Unfortunately, I still receive a signal 8 (FPE exception) as soon as I try > to do anything with pgp. Some command logs: > > [...snip...] > > > kernel configuration: > --------------------- > > options MATH_EMULATE #Support for x87 emulation Remove this or comment it out. That's the only thing that leapt out at me. You certainly don't need it. -- Chris BeHanna Software Engineer (Remove "bogus" before responding.) behanna@bogus.zbzoom.net I was raised by a pack of wild corn dogs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 17:53:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.world-online.no (fe080.world-online.no [213.142.64.158]) by hub.freebsd.org (Postfix) with SMTP id 6A09D37B405 for ; Mon, 12 Nov 2001 17:53:24 -0800 (PST) Received: (qmail 4843 invoked by uid 0); 13 Nov 2001 01:53:23 -0000 Received: from 72.ppp1-3.td.tiscali.no (HELO odde) (213.142.72.72) by mail000.world-online.no with SMTP; 13 Nov 2001 01:53:23 -0000 Message-ID: <00ca01c16be5$95732a40$0400a8c0@odde> From: "Odd Egil H. Selnes" To: Subject: Date: Tue, 13 Nov 2001 02:50:33 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG auth 55c187a7 subscribe freebsd-stable odde@wayout.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 22:52:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id 53C4D37B417 for ; Mon, 12 Nov 2001 22:52:48 -0800 (PST) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id RAA66459; Tue, 13 Nov 2001 17:52:42 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id RAA29678; Tue, 13 Nov 2001 17:52:41 +1100 (EST) Message-Id: <200111130652.RAA29678@lightning.itga.com.au> From: Gregory Bond To: Pete French Cc: iberiozko@infodom.ru, stable@FreeBSD.ORG Subject: Re: Curious crash In-reply-to: Your message of Thu, 08 Nov 2001 12:28:12 -0000. Date: Tue, 13 Nov 2001 17:52:38 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Hello. > > Are you using screensaver? > > yes, graphical daemon. I have had private emails from several people who > have observed similar behaviour on Matrox cards actually Hmm, we have had the same experience with one of our servers - also running the daemon screen saver but with an old #9 video card (I think - remote possibility of a Matrox but unlikely). This is running something just a bit after 4.4-Release. No problem on any of the other FreeBSD machines. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 23:14:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from goku.branchmedia.com (goku.branchmedia.com [216.129.214.40]) by hub.freebsd.org (Postfix) with ESMTP id 8B4A137B405 for ; Mon, 12 Nov 2001 23:14:03 -0800 (PST) Received: from cr411661a (shadow.dreamlabs.com [216.129.214.38]) (authenticated) by goku.branchmedia.com (8.11.6/8.11.5) with ESMTP id fAD7E1X47785 for ; Tue, 13 Nov 2001 02:14:02 -0500 (EST) (envelope-from mitayai@dreamlabs.com) From: "Mit Rowe" To: Subject: kernel build problem Date: Tue, 13 Nov 2001 02:10:51 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm having a problem building today's stable kernel, around the linux_sysent part. i'm using the standard compile options (no overrides in /etc/make.conf) and my conf file is below. Any ideas? ###error### cc -nostdinc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qu al -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../inc lude -mpreferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qu al -fformat-extensions -ansi -c linux_sysent.c In file included from linux_sysent.c:14: linux_proto.h:57: syntax error before `linux_time_t' linux_proto.h:57: `linux_time_t' undeclared here (not in a function) linux_proto.h:57: syntax error before `)' linux_proto.h:57: `linux_time_t' undeclared here (not in a function) linux_proto.h:57: syntax error before `)' linux_proto.h:156: syntax error before `linux_handler_t' linux_proto.h:156: `linux_handler_t' undeclared here (not in a function) linux_proto.h:156: `linux_handler_t' undeclared here (not in a function) linux_proto.h:184: syntax error before `linux_dev_t' linux_proto.h:184: `linux_dev_t' undeclared here (not in a function) linux_proto.h:184: `linux_dev_t' undeclared here (not in a function) linux_proto.h:189: syntax error before `linux_osigaction_t' linux_proto.h:189: `linux_osigaction_t' undeclared here (not in a function) linux_proto.h:189: syntax error before `)' linux_proto.h:189: `linux_osigaction_t' undeclared here (not in a function) linux_proto.h:189: syntax error before `)' linux_proto.h:190: syntax error before `linux_osigaction_t' linux_proto.h:190: `linux_osigaction_t' undeclared here (not in a function) linux_proto.h:190: syntax error before `)' linux_proto.h:190: `linux_osigaction_t' undeclared here (not in a function) linux_proto.h:190: syntax error before `)' linux_proto.h:196: syntax error before `linux_osigset_t' linux_proto.h:196: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:196: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:200: syntax error before `linux_osigset_t' linux_proto.h:200: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:200: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:201: syntax error before `linux_osigset_t' linux_proto.h:201: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:201: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:204: syntax error before `linux_osigset_t' linux_proto.h:204: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:204: syntax error before `)' linux_proto.h:204: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:204: syntax error before `)' linux_proto.h:216: syntax error before `linux_gid_t' linux_proto.h:216: `linux_gid_t' undeclared here (not in a function) linux_proto.h:216: syntax error before `)' linux_proto.h:216: `linux_gid_t' undeclared here (not in a function) linux_proto.h:216: syntax error before `)' linux_proto.h:220: syntax error before `linux_gid_t' linux_proto.h:220: `linux_gid_t' undeclared here (not in a function) linux_proto.h:220: syntax error before `)' linux_proto.h:220: `linux_gid_t' undeclared here (not in a function) linux_proto.h:220: syntax error before `)' linux_proto.h:344: syntax error before `linux_osigset_t' linux_proto.h:344: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:344: syntax error before `)' linux_proto.h:344: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:344: syntax error before `)' linux_proto.h:345: syntax error before `linux_osigset_t' linux_proto.h:345: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:345: syntax error before `)' linux_proto.h:345: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:345: syntax error before `)' linux_proto.h:380: syntax error before `linux_uid_t' linux_proto.h:380: `linux_uid_t' undeclared here (not in a function) linux_proto.h:380: `linux_uid_t' undeclared here (not in a function) linux_proto.h:383: syntax error before `linux_gid_t' linux_proto.h:383: `linux_gid_t' undeclared here (not in a function) linux_proto.h:383: `linux_gid_t' undeclared here (not in a function) linux_proto.h:410: syntax error before `linux_pid_t' linux_proto.h:410: `linux_pid_t' undeclared here (not in a function) linux_proto.h:410: `linux_pid_t' undeclared here (not in a function) linux_proto.h:439: syntax error before `linux_uid_t' linux_proto.h:439: `linux_uid_t' undeclared here (not in a function) linux_proto.h:439: syntax error before `)' linux_proto.h:439: `linux_uid_t' undeclared here (not in a function) linux_proto.h:439: syntax error before `)' linux_proto.h:440: syntax error before `linux_uid_t' linux_proto.h:440: `linux_uid_t' undeclared here (not in a function) linux_proto.h:440: syntax error before `)' linux_proto.h:440: `linux_uid_t' undeclared here (not in a function) linux_proto.h:440: syntax error before `)' linux_proto.h:441: syntax error before `linux_uid_t' linux_proto.h:441: `linux_uid_t' undeclared here (not in a function) linux_proto.h:441: syntax error before `)' linux_proto.h:441: `linux_uid_t' undeclared here (not in a function) linux_proto.h:441: syntax error before `)' linux_proto.h:453: syntax error before `linux_gid_t' linux_proto.h:453: `linux_gid_t' undeclared here (not in a function) linux_proto.h:453: syntax error before `)' linux_proto.h:453: `linux_gid_t' undeclared here (not in a function) linux_proto.h:453: syntax error before `)' linux_proto.h:454: syntax error before `linux_gid_t' linux_proto.h:454: `linux_gid_t' undeclared here (not in a function) linux_proto.h:454: syntax error before `)' linux_proto.h:454: `linux_gid_t' undeclared here (not in a function) linux_proto.h:454: syntax error before `)' linux_proto.h:455: syntax error before `linux_gid_t' linux_proto.h:455: `linux_gid_t' undeclared here (not in a function) linux_proto.h:455: syntax error before `)' linux_proto.h:455: `linux_gid_t' undeclared here (not in a function) linux_proto.h:455: syntax error before `)' linux_proto.h:465: syntax error before `linux_sigaction_t' linux_proto.h:465: `linux_sigaction_t' undeclared here (not in a function) linux_proto.h:465: syntax error before `)' linux_proto.h:465: `linux_sigaction_t' undeclared here (not in a function) linux_proto.h:465: syntax error before `)' linux_proto.h:466: syntax error before `linux_sigaction_t' linux_proto.h:466: `linux_sigaction_t' undeclared here (not in a function) linux_proto.h:466: syntax error before `)' linux_proto.h:466: `linux_sigaction_t' undeclared here (not in a function) linux_proto.h:466: syntax error before `)' linux_proto.h:471: syntax error before `linux_sigset_t' linux_proto.h:471: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:471: syntax error before `)' linux_proto.h:471: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:471: syntax error before `)' linux_proto.h:472: syntax error before `linux_sigset_t' linux_proto.h:472: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:472: syntax error before `)' linux_proto.h:472: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:472: syntax error before `)' linux_proto.h:485: syntax error before `linux_sigset_t' linux_proto.h:485: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:485: syntax error before `)' linux_proto.h:485: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:485: syntax error before `)' linux_proto.h:516: syntax error before `*' linux_proto.h:516: syntax error before `linux_stack_t' linux_proto.h:516: syntax error before `linux_stack_t' linux_proto.h:517: syntax error before `linux_stack_t' linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) linux_proto.h:517: syntax error before `)' linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) linux_proto.h:517: syntax error before `)' linux_sysent.c:21: sizeof applied to an incomplete type linux_sysent.c:21: warning: built-in function `exit' used without declaration linux_sysent.c:21: warning: cast discards qualifiers from pointer target type *** Error code 1 Stop in /usr/src/sys/modules/linux. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/tenchi. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ###config file### machine i386 cpu I686_CPU ident tenchi maxusers 32 options INET #InterNETworking #options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem #options MD_ROOT #MD is a potential root device options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, NFS required #options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem #options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev device isa device pci device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? pseudo-device splash device sc0 at isa? flags 0x100 device npx0 at nexus? port IO_NPX irq 13 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device miibus # MII bus support device sis # Silicon Integrated Systems SiS 900/SiS 7016 device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" #pseudo-device gif # IPv6 and IPv4 tunneling #pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) pseudo-device bpf #Berkeley packet filter options INCLUDE_CONFIG_FILE # Include this file in kernel #pseudo-device stf #6to4 IPv6 over IPv4 encapsulation #options IPFIREWALL #firewall #options IPFIREWALL_VERBOSE #enable logging to syslogd(8) #options IPFIREWALL_FORWARD #enable transparent proxy support #options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity #options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default #options IPV6FIREWALL #firewall for IPv6 #options IPV6FIREWALL_VERBOSE #options IPV6FIREWALL_VERBOSE_LIMIT=100 #options IPV6FIREWALL_DEFAULT_TO_ACCEPT #options IPDIVERT #divert sockets #options IPSTEALTH #support for stealth forwarding options RANDOM_IP_ID #options DUMMYNET #options BRIDGE #options UFS_DIRHASH options QUOTA #enable disk quotas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 23:33: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from castle.dreaming.org (castle.dreaming.org [216.221.214.170]) by hub.freebsd.org (Postfix) with ESMTP id 2A16837B405 for ; Mon, 12 Nov 2001 23:32:56 -0800 (PST) Received: (from root@localhost) by castle.dreaming.org (8.11.6/8.11.6) id fAD7Wts26647 for stable@freebsd.org; Tue, 13 Nov 2001 02:32:55 -0500 (EST) (envelope-from mitayai@dreaming.org) Received: from cr411661a (shadow.dreamlabs.com [216.129.214.38]) (authenticated) by castle.dreaming.org (8.11.6/8.11.6av) with ESMTP id fAD7WrY26639 for ; Tue, 13 Nov 2001 02:32:53 -0500 (EST) (envelope-from mitayai@dreaming.org) From: "Mit Rowe" To: Subject: RE: kernel build problem Date: Tue, 13 Nov 2001 02:29:43 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hmm... is it using the /compat/linux stuff? I'm using the 6.1 stuff from /usr/ports/emulators/linux_base/. I'll upgrade to 62, and recompile, and if that doesn't work, i'll do up to 71 and try again. Regardless of what happens, i'll report back. I doubt it will hurt for me to be up-to-date anyway ;-) -Mit > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Mit Rowe > Sent: November 13, 2001 02:11 > To: stable@FreeBSD.ORG > Subject: kernel build problem > > > I'm having a problem building today's stable kernel, around the > linux_sysent > part. > > i'm using the standard compile options (no overrides in > /etc/make.conf) and > my conf file is below. > > Any ideas? > > ###error### > cc -nostdinc -O -pipe -D_KERNEL -Wall -Wredundant-decls > -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qu > al -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ > -I@/../inc > lude -mpreferred-stack-boundary=2 -Wall -Wredundant-decls > -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qu > al -fformat-extensions -ansi -c linux_sysent.c > In file included from linux_sysent.c:14: > linux_proto.h:57: syntax error before `linux_time_t' > linux_proto.h:57: `linux_time_t' undeclared here (not in a function) > linux_proto.h:57: syntax error before `)' > linux_proto.h:57: `linux_time_t' undeclared here (not in a function) > linux_proto.h:57: syntax error before `)' > linux_proto.h:156: syntax error before `linux_handler_t' > linux_proto.h:156: `linux_handler_t' undeclared here (not in a function) > linux_proto.h:156: `linux_handler_t' undeclared here (not in a function) > linux_proto.h:184: syntax error before `linux_dev_t' > linux_proto.h:184: `linux_dev_t' undeclared here (not in a function) > linux_proto.h:184: `linux_dev_t' undeclared here (not in a function) > linux_proto.h:189: syntax error before `linux_osigaction_t' > linux_proto.h:189: `linux_osigaction_t' undeclared here (not in a > function) > linux_proto.h:189: syntax error before `)' > linux_proto.h:189: `linux_osigaction_t' undeclared here (not in a > function) > linux_proto.h:189: syntax error before `)' > linux_proto.h:190: syntax error before `linux_osigaction_t' > linux_proto.h:190: `linux_osigaction_t' undeclared here (not in a > function) > linux_proto.h:190: syntax error before `)' > linux_proto.h:190: `linux_osigaction_t' undeclared here (not in a > function) > linux_proto.h:190: syntax error before `)' > linux_proto.h:196: syntax error before `linux_osigset_t' > linux_proto.h:196: `linux_osigset_t' undeclared here (not in a function) > linux_proto.h:196: `linux_osigset_t' undeclared here (not in a function) > linux_proto.h:200: syntax error before `linux_osigset_t' > linux_proto.h:200: `linux_osigset_t' undeclared here (not in a function) > linux_proto.h:200: `linux_osigset_t' undeclared here (not in a function) > linux_proto.h:201: syntax error before `linux_osigset_t' > linux_proto.h:201: `linux_osigset_t' undeclared here (not in a function) > linux_proto.h:201: `linux_osigset_t' undeclared here (not in a function) > linux_proto.h:204: syntax error before `linux_osigset_t' > linux_proto.h:204: `linux_osigset_t' undeclared here (not in a function) > linux_proto.h:204: syntax error before `)' > linux_proto.h:204: `linux_osigset_t' undeclared here (not in a function) > linux_proto.h:204: syntax error before `)' > linux_proto.h:216: syntax error before `linux_gid_t' > linux_proto.h:216: `linux_gid_t' undeclared here (not in a function) > linux_proto.h:216: syntax error before `)' > linux_proto.h:216: `linux_gid_t' undeclared here (not in a function) > linux_proto.h:216: syntax error before `)' > linux_proto.h:220: syntax error before `linux_gid_t' > linux_proto.h:220: `linux_gid_t' undeclared here (not in a function) > linux_proto.h:220: syntax error before `)' > linux_proto.h:220: `linux_gid_t' undeclared here (not in a function) > linux_proto.h:220: syntax error before `)' > linux_proto.h:344: syntax error before `linux_osigset_t' > linux_proto.h:344: `linux_osigset_t' undeclared here (not in a function) > linux_proto.h:344: syntax error before `)' > linux_proto.h:344: `linux_osigset_t' undeclared here (not in a function) > linux_proto.h:344: syntax error before `)' > linux_proto.h:345: syntax error before `linux_osigset_t' > linux_proto.h:345: `linux_osigset_t' undeclared here (not in a function) > linux_proto.h:345: syntax error before `)' > linux_proto.h:345: `linux_osigset_t' undeclared here (not in a function) > linux_proto.h:345: syntax error before `)' > linux_proto.h:380: syntax error before `linux_uid_t' > linux_proto.h:380: `linux_uid_t' undeclared here (not in a function) > linux_proto.h:380: `linux_uid_t' undeclared here (not in a function) > linux_proto.h:383: syntax error before `linux_gid_t' > linux_proto.h:383: `linux_gid_t' undeclared here (not in a function) > linux_proto.h:383: `linux_gid_t' undeclared here (not in a function) > linux_proto.h:410: syntax error before `linux_pid_t' > linux_proto.h:410: `linux_pid_t' undeclared here (not in a function) > linux_proto.h:410: `linux_pid_t' undeclared here (not in a function) > linux_proto.h:439: syntax error before `linux_uid_t' > linux_proto.h:439: `linux_uid_t' undeclared here (not in a function) > linux_proto.h:439: syntax error before `)' > linux_proto.h:439: `linux_uid_t' undeclared here (not in a function) > linux_proto.h:439: syntax error before `)' > linux_proto.h:440: syntax error before `linux_uid_t' > linux_proto.h:440: `linux_uid_t' undeclared here (not in a function) > linux_proto.h:440: syntax error before `)' > linux_proto.h:440: `linux_uid_t' undeclared here (not in a function) > linux_proto.h:440: syntax error before `)' > linux_proto.h:441: syntax error before `linux_uid_t' > linux_proto.h:441: `linux_uid_t' undeclared here (not in a function) > linux_proto.h:441: syntax error before `)' > linux_proto.h:441: `linux_uid_t' undeclared here (not in a function) > linux_proto.h:441: syntax error before `)' > linux_proto.h:453: syntax error before `linux_gid_t' > linux_proto.h:453: `linux_gid_t' undeclared here (not in a function) > linux_proto.h:453: syntax error before `)' > linux_proto.h:453: `linux_gid_t' undeclared here (not in a function) > linux_proto.h:453: syntax error before `)' > linux_proto.h:454: syntax error before `linux_gid_t' > linux_proto.h:454: `linux_gid_t' undeclared here (not in a function) > linux_proto.h:454: syntax error before `)' > linux_proto.h:454: `linux_gid_t' undeclared here (not in a function) > linux_proto.h:454: syntax error before `)' > linux_proto.h:455: syntax error before `linux_gid_t' > linux_proto.h:455: `linux_gid_t' undeclared here (not in a function) > linux_proto.h:455: syntax error before `)' > linux_proto.h:455: `linux_gid_t' undeclared here (not in a function) > linux_proto.h:455: syntax error before `)' > linux_proto.h:465: syntax error before `linux_sigaction_t' > linux_proto.h:465: `linux_sigaction_t' undeclared here (not in a function) > linux_proto.h:465: syntax error before `)' > linux_proto.h:465: `linux_sigaction_t' undeclared here (not in a function) > linux_proto.h:465: syntax error before `)' > linux_proto.h:466: syntax error before `linux_sigaction_t' > linux_proto.h:466: `linux_sigaction_t' undeclared here (not in a function) > linux_proto.h:466: syntax error before `)' > linux_proto.h:466: `linux_sigaction_t' undeclared here (not in a function) > linux_proto.h:466: syntax error before `)' > linux_proto.h:471: syntax error before `linux_sigset_t' > linux_proto.h:471: `linux_sigset_t' undeclared here (not in a function) > linux_proto.h:471: syntax error before `)' > linux_proto.h:471: `linux_sigset_t' undeclared here (not in a function) > linux_proto.h:471: syntax error before `)' > linux_proto.h:472: syntax error before `linux_sigset_t' > linux_proto.h:472: `linux_sigset_t' undeclared here (not in a function) > linux_proto.h:472: syntax error before `)' > linux_proto.h:472: `linux_sigset_t' undeclared here (not in a function) > linux_proto.h:472: syntax error before `)' > linux_proto.h:485: syntax error before `linux_sigset_t' > linux_proto.h:485: `linux_sigset_t' undeclared here (not in a function) > linux_proto.h:485: syntax error before `)' > linux_proto.h:485: `linux_sigset_t' undeclared here (not in a function) > linux_proto.h:485: syntax error before `)' > linux_proto.h:516: syntax error before `*' > linux_proto.h:516: syntax error before `linux_stack_t' > linux_proto.h:516: syntax error before `linux_stack_t' > linux_proto.h:517: syntax error before `linux_stack_t' > linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) > linux_proto.h:517: syntax error before `)' > linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) > linux_proto.h:517: syntax error before `)' > linux_sysent.c:21: sizeof applied to an incomplete type > linux_sysent.c:21: warning: built-in function `exit' used without > declaration > linux_sysent.c:21: warning: cast discards qualifiers from pointer target > type > *** Error code 1 > > Stop in /usr/src/sys/modules/linux. > *** Error code 1 > > Stop in /usr/src/sys/modules. > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/tenchi. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > ###config file### > > machine i386 > cpu I686_CPU > ident tenchi > maxusers 32 > options INET #InterNETworking > #options INET6 #IPv6 communications protocols > options FFS #Berkeley Fast Filesystem > options FFS_ROOT #FFS usable as root device > [keep this!] > options SOFTUPDATES #Enable FFS soft updates support > options MFS #Memory Filesystem > #options MD_ROOT #MD is a potential root device > options NFS #Network Filesystem > #options NFS_ROOT #NFS usable as root device, > NFS required > #options MSDOSFS #MSDOS Filesystem > options CD9660 #ISO 9660 Filesystem > #options CD9660_ROOT #CD-ROM usable as root, > CD9660 required > options PROCFS #Process filesystem > options COMPAT_43 #Compatible with BSD 4.3 > [KEEP THIS!] > options UCONSOLE #Allow users to grab the console > options USERCONFIG #boot -c editor > options VISUAL_USERCONFIG #visual boot -c editor > options KTRACE #ktrace(1) support > options SYSVSHM #SYSV-style shared memory > options SYSVMSG #SYSV-style message queues > options SYSVSEM #SYSV-style semaphores > options P1003_1B #Posix P1003_1B real-time extensions > options _KPOSIX_PRIORITY_SCHEDULING > options ICMP_BANDLIM #Rate limit bad replies > options KBD_INSTALL_CDEV # install a CDEV entry in /dev > device isa > device pci > device fdc0 at isa? port IO_FD1 irq 6 drq 2 > device fd0 at fdc0 drive 0 > device ata0 at isa? port IO_WD1 irq 14 > device ata1 at isa? port IO_WD2 irq 15 > device ata > device atadisk # ATA disk drives > device atapicd # ATAPI CDROM drives > options ATA_STATIC_ID #Static device numbering > device atkbdc0 at isa? port IO_KBD > device atkbd0 at atkbdc? irq 1 flags 0x1 > device psm0 at atkbdc? irq 12 > device vga0 at isa? > pseudo-device splash > device sc0 at isa? flags 0x100 > device npx0 at nexus? port IO_NPX irq 13 > device sio0 at isa? port IO_COM1 flags 0x10 irq 4 > device sio1 at isa? port IO_COM2 irq 3 > device miibus # MII bus support > device sis # Silicon Integrated > Systems SiS 900/SiS 7016 > device xl # 3Com 3c90x > (``Boomerang'', ``Cyclone'') > pseudo-device loop # Network loopback > pseudo-device ether # Ethernet support > pseudo-device tun # Packet tunnel. > pseudo-device pty # Pseudo-ttys (telnet etc) > pseudo-device md # Memory "disks" > #pseudo-device gif # IPv6 and IPv4 tunneling > #pseudo-device faith 1 # IPv6-to-IPv4 relaying > (translation) > pseudo-device bpf #Berkeley packet filter > options INCLUDE_CONFIG_FILE # Include this file in kernel > #pseudo-device stf #6to4 IPv6 over > IPv4 encapsulation > #options IPFIREWALL #firewall > #options IPFIREWALL_VERBOSE #enable logging to syslogd(8) > #options IPFIREWALL_FORWARD #enable transparent proxy support > #options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity > #options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default > #options IPV6FIREWALL #firewall for IPv6 > #options IPV6FIREWALL_VERBOSE > #options IPV6FIREWALL_VERBOSE_LIMIT=100 > #options IPV6FIREWALL_DEFAULT_TO_ACCEPT > #options IPDIVERT #divert sockets > #options IPSTEALTH #support for stealth forwarding > options RANDOM_IP_ID > #options DUMMYNET > #options BRIDGE > #options UFS_DIRHASH > options QUOTA #enable disk quotas > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 23:38: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by hub.freebsd.org (Postfix) with ESMTP id 2C12637B417 for ; Mon, 12 Nov 2001 23:37:59 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtpzilla2.xs4all.nl (8.12.0/8.12.0) with ESMTP id fAD7buhn085834; Tue, 13 Nov 2001 08:37:56 +0100 (CET) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fAD7bt435709; Tue, 13 Nov 2001 08:37:55 +0100 (CET) (envelope-from wkb) Date: Tue, 13 Nov 2001 08:37:55 +0100 From: Wilko Bulte To: Mit Rowe Cc: stable@FreeBSD.ORG Subject: Re: kernel build problem Message-ID: <20011113083755.B35646@freebie.xs4all.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mitayai@dreaming.org on Tue, Nov 13, 2001 at 02:29:43AM -0500 X-OS: FreeBSD 4.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Nov 13, 2001 at 02:29:43AM -0500, Mit Rowe wrote: Same problem here on an Alpha machine. > hmm... is it using the /compat/linux stuff? I'm using the 6.1 stuff from > /usr/ports/emulators/linux_base/. I'll upgrade to 62, and recompile, and if > that doesn't work, i'll do up to 71 and try again. > > Regardless of what happens, i'll report back. I doubt it will hurt for me to > be up-to-date anyway ;-) > > -Mit > > > > -----Original Message----- > > From: owner-freebsd-stable@FreeBSD.ORG > > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Mit Rowe > > Sent: November 13, 2001 02:11 > > To: stable@FreeBSD.ORG > > Subject: kernel build problem > > > > > > I'm having a problem building today's stable kernel, around the > > linux_sysent > > part. > > > > i'm using the standard compile options (no overrides in > > /etc/make.conf) and > > my conf file is below. > > -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 23:51:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from castle.dreaming.org (castle.dreaming.org [216.221.214.170]) by hub.freebsd.org (Postfix) with ESMTP id 7297F37B405 for ; Mon, 12 Nov 2001 23:51:43 -0800 (PST) Received: (from root@localhost) by castle.dreaming.org (8.11.6/8.11.6) id fAD7pgV27028; Tue, 13 Nov 2001 02:51:42 -0500 (EST) (envelope-from mitayai@dreaming.org) Received: from cr411661a (shadow.dreamlabs.com [216.129.214.38]) (authenticated) by castle.dreaming.org (8.11.6/8.11.6av) with ESMTP id fAD7peY27020; Tue, 13 Nov 2001 02:51:40 -0500 (EST) (envelope-from mitayai@dreaming.org) From: "Mit Rowe" To: "Mit Rowe" , Subject: RE: kernel build problem Date: Tue, 13 Nov 2001 02:48:30 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Nix that, the Makefile for the linux_base-62 port tried to build 61. On to 71... > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Mit Rowe > Sent: November 13, 2001 02:30 > To: stable@FreeBSD.ORG > Subject: RE: kernel build problem > > > hmm... is it using the /compat/linux stuff? I'm using the 6.1 stuff from > /usr/ports/emulators/linux_base/. I'll upgrade to 62, and > recompile, and if > that doesn't work, i'll do up to 71 and try again. > > Regardless of what happens, i'll report back. I doubt it will > hurt for me to > be up-to-date anyway ;-) > > -Mit > > > > -----Original Message----- > > From: owner-freebsd-stable@FreeBSD.ORG > > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Mit Rowe > > Sent: November 13, 2001 02:11 > > To: stable@FreeBSD.ORG > > Subject: kernel build problem > > > > > > I'm having a problem building today's stable kernel, around the > > linux_sysent > > part. > > > > i'm using the standard compile options (no overrides in > > /etc/make.conf) and > > my conf file is below. > > > > Any ideas? > > > > ###error### > > cc -nostdinc -O -pipe -D_KERNEL -Wall -Wredundant-decls > > -Wnested-externs > > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > > -Winline -Wcast-qu > > al -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ > > -I@/../inc > > lude -mpreferred-stack-boundary=2 -Wall -Wredundant-decls > > -Wnested-externs > > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > > -Winline -Wcast-qu > > al -fformat-extensions -ansi -c linux_sysent.c > > In file included from linux_sysent.c:14: > > linux_proto.h:57: syntax error before `linux_time_t' > > linux_proto.h:57: `linux_time_t' undeclared here (not in a function) > > linux_proto.h:57: syntax error before `)' > > linux_proto.h:57: `linux_time_t' undeclared here (not in a function) > > linux_proto.h:57: syntax error before `)' > > linux_proto.h:156: syntax error before `linux_handler_t' > > linux_proto.h:156: `linux_handler_t' undeclared here (not in a function) > > linux_proto.h:156: `linux_handler_t' undeclared here (not in a function) > > linux_proto.h:184: syntax error before `linux_dev_t' > > linux_proto.h:184: `linux_dev_t' undeclared here (not in a function) > > linux_proto.h:184: `linux_dev_t' undeclared here (not in a function) > > linux_proto.h:189: syntax error before `linux_osigaction_t' > > linux_proto.h:189: `linux_osigaction_t' undeclared here (not in a > > function) > > linux_proto.h:189: syntax error before `)' > > linux_proto.h:189: `linux_osigaction_t' undeclared here (not in a > > function) > > linux_proto.h:189: syntax error before `)' > > linux_proto.h:190: syntax error before `linux_osigaction_t' > > linux_proto.h:190: `linux_osigaction_t' undeclared here (not in a > > function) > > linux_proto.h:190: syntax error before `)' > > linux_proto.h:190: `linux_osigaction_t' undeclared here (not in a > > function) > > linux_proto.h:190: syntax error before `)' > > linux_proto.h:196: syntax error before `linux_osigset_t' > > linux_proto.h:196: `linux_osigset_t' undeclared here (not in a function) > > linux_proto.h:196: `linux_osigset_t' undeclared here (not in a function) > > linux_proto.h:200: syntax error before `linux_osigset_t' > > linux_proto.h:200: `linux_osigset_t' undeclared here (not in a function) > > linux_proto.h:200: `linux_osigset_t' undeclared here (not in a function) > > linux_proto.h:201: syntax error before `linux_osigset_t' > > linux_proto.h:201: `linux_osigset_t' undeclared here (not in a function) > > linux_proto.h:201: `linux_osigset_t' undeclared here (not in a function) > > linux_proto.h:204: syntax error before `linux_osigset_t' > > linux_proto.h:204: `linux_osigset_t' undeclared here (not in a function) > > linux_proto.h:204: syntax error before `)' > > linux_proto.h:204: `linux_osigset_t' undeclared here (not in a function) > > linux_proto.h:204: syntax error before `)' > > linux_proto.h:216: syntax error before `linux_gid_t' > > linux_proto.h:216: `linux_gid_t' undeclared here (not in a function) > > linux_proto.h:216: syntax error before `)' > > linux_proto.h:216: `linux_gid_t' undeclared here (not in a function) > > linux_proto.h:216: syntax error before `)' > > linux_proto.h:220: syntax error before `linux_gid_t' > > linux_proto.h:220: `linux_gid_t' undeclared here (not in a function) > > linux_proto.h:220: syntax error before `)' > > linux_proto.h:220: `linux_gid_t' undeclared here (not in a function) > > linux_proto.h:220: syntax error before `)' > > linux_proto.h:344: syntax error before `linux_osigset_t' > > linux_proto.h:344: `linux_osigset_t' undeclared here (not in a function) > > linux_proto.h:344: syntax error before `)' > > linux_proto.h:344: `linux_osigset_t' undeclared here (not in a function) > > linux_proto.h:344: syntax error before `)' > > linux_proto.h:345: syntax error before `linux_osigset_t' > > linux_proto.h:345: `linux_osigset_t' undeclared here (not in a function) > > linux_proto.h:345: syntax error before `)' > > linux_proto.h:345: `linux_osigset_t' undeclared here (not in a function) > > linux_proto.h:345: syntax error before `)' > > linux_proto.h:380: syntax error before `linux_uid_t' > > linux_proto.h:380: `linux_uid_t' undeclared here (not in a function) > > linux_proto.h:380: `linux_uid_t' undeclared here (not in a function) > > linux_proto.h:383: syntax error before `linux_gid_t' > > linux_proto.h:383: `linux_gid_t' undeclared here (not in a function) > > linux_proto.h:383: `linux_gid_t' undeclared here (not in a function) > > linux_proto.h:410: syntax error before `linux_pid_t' > > linux_proto.h:410: `linux_pid_t' undeclared here (not in a function) > > linux_proto.h:410: `linux_pid_t' undeclared here (not in a function) > > linux_proto.h:439: syntax error before `linux_uid_t' > > linux_proto.h:439: `linux_uid_t' undeclared here (not in a function) > > linux_proto.h:439: syntax error before `)' > > linux_proto.h:439: `linux_uid_t' undeclared here (not in a function) > > linux_proto.h:439: syntax error before `)' > > linux_proto.h:440: syntax error before `linux_uid_t' > > linux_proto.h:440: `linux_uid_t' undeclared here (not in a function) > > linux_proto.h:440: syntax error before `)' > > linux_proto.h:440: `linux_uid_t' undeclared here (not in a function) > > linux_proto.h:440: syntax error before `)' > > linux_proto.h:441: syntax error before `linux_uid_t' > > linux_proto.h:441: `linux_uid_t' undeclared here (not in a function) > > linux_proto.h:441: syntax error before `)' > > linux_proto.h:441: `linux_uid_t' undeclared here (not in a function) > > linux_proto.h:441: syntax error before `)' > > linux_proto.h:453: syntax error before `linux_gid_t' > > linux_proto.h:453: `linux_gid_t' undeclared here (not in a function) > > linux_proto.h:453: syntax error before `)' > > linux_proto.h:453: `linux_gid_t' undeclared here (not in a function) > > linux_proto.h:453: syntax error before `)' > > linux_proto.h:454: syntax error before `linux_gid_t' > > linux_proto.h:454: `linux_gid_t' undeclared here (not in a function) > > linux_proto.h:454: syntax error before `)' > > linux_proto.h:454: `linux_gid_t' undeclared here (not in a function) > > linux_proto.h:454: syntax error before `)' > > linux_proto.h:455: syntax error before `linux_gid_t' > > linux_proto.h:455: `linux_gid_t' undeclared here (not in a function) > > linux_proto.h:455: syntax error before `)' > > linux_proto.h:455: `linux_gid_t' undeclared here (not in a function) > > linux_proto.h:455: syntax error before `)' > > linux_proto.h:465: syntax error before `linux_sigaction_t' > > linux_proto.h:465: `linux_sigaction_t' undeclared here (not in > a function) > > linux_proto.h:465: syntax error before `)' > > linux_proto.h:465: `linux_sigaction_t' undeclared here (not in > a function) > > linux_proto.h:465: syntax error before `)' > > linux_proto.h:466: syntax error before `linux_sigaction_t' > > linux_proto.h:466: `linux_sigaction_t' undeclared here (not in > a function) > > linux_proto.h:466: syntax error before `)' > > linux_proto.h:466: `linux_sigaction_t' undeclared here (not in > a function) > > linux_proto.h:466: syntax error before `)' > > linux_proto.h:471: syntax error before `linux_sigset_t' > > linux_proto.h:471: `linux_sigset_t' undeclared here (not in a function) > > linux_proto.h:471: syntax error before `)' > > linux_proto.h:471: `linux_sigset_t' undeclared here (not in a function) > > linux_proto.h:471: syntax error before `)' > > linux_proto.h:472: syntax error before `linux_sigset_t' > > linux_proto.h:472: `linux_sigset_t' undeclared here (not in a function) > > linux_proto.h:472: syntax error before `)' > > linux_proto.h:472: `linux_sigset_t' undeclared here (not in a function) > > linux_proto.h:472: syntax error before `)' > > linux_proto.h:485: syntax error before `linux_sigset_t' > > linux_proto.h:485: `linux_sigset_t' undeclared here (not in a function) > > linux_proto.h:485: syntax error before `)' > > linux_proto.h:485: `linux_sigset_t' undeclared here (not in a function) > > linux_proto.h:485: syntax error before `)' > > linux_proto.h:516: syntax error before `*' > > linux_proto.h:516: syntax error before `linux_stack_t' > > linux_proto.h:516: syntax error before `linux_stack_t' > > linux_proto.h:517: syntax error before `linux_stack_t' > > linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) > > linux_proto.h:517: syntax error before `)' > > linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) > > linux_proto.h:517: syntax error before `)' > > linux_sysent.c:21: sizeof applied to an incomplete type > > linux_sysent.c:21: warning: built-in function `exit' used without > > declaration > > linux_sysent.c:21: warning: cast discards qualifiers from pointer target > > type > > *** Error code 1 > > > > Stop in /usr/src/sys/modules/linux. > > *** Error code 1 > > > > Stop in /usr/src/sys/modules. > > *** Error code 1 > > > > Stop in /usr/obj/usr/src/sys/tenchi. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > > > ###config file### > > > > machine i386 > > cpu I686_CPU > > ident tenchi > > maxusers 32 > > options INET #InterNETworking > > #options INET6 #IPv6 communications protocols > > options FFS #Berkeley Fast Filesystem > > options FFS_ROOT #FFS usable as root device > > [keep this!] > > options SOFTUPDATES #Enable FFS soft updates support > > options MFS #Memory Filesystem > > #options MD_ROOT #MD is a potential root device > > options NFS #Network Filesystem > > #options NFS_ROOT #NFS usable as root device, > > NFS required > > #options MSDOSFS #MSDOS Filesystem > > options CD9660 #ISO 9660 Filesystem > > #options CD9660_ROOT #CD-ROM usable as root, > > CD9660 required > > options PROCFS #Process filesystem > > options COMPAT_43 #Compatible with BSD 4.3 > > [KEEP THIS!] > > options UCONSOLE #Allow users to grab the console > > options USERCONFIG #boot -c editor > > options VISUAL_USERCONFIG #visual boot -c editor > > options KTRACE #ktrace(1) support > > options SYSVSHM #SYSV-style shared memory > > options SYSVMSG #SYSV-style message queues > > options SYSVSEM #SYSV-style semaphores > > options P1003_1B #Posix P1003_1B real-time extensions > > options _KPOSIX_PRIORITY_SCHEDULING > > options ICMP_BANDLIM #Rate limit bad replies > > options KBD_INSTALL_CDEV # install a CDEV entry in /dev > > device isa > > device pci > > device fdc0 at isa? port IO_FD1 irq 6 drq 2 > > device fd0 at fdc0 drive 0 > > device ata0 at isa? port IO_WD1 irq 14 > > device ata1 at isa? port IO_WD2 irq 15 > > device ata > > device atadisk # ATA disk drives > > device atapicd # ATAPI CDROM drives > > options ATA_STATIC_ID #Static device numbering > > device atkbdc0 at isa? port IO_KBD > > device atkbd0 at atkbdc? irq 1 flags 0x1 > > device psm0 at atkbdc? irq 12 > > device vga0 at isa? > > pseudo-device splash > > device sc0 at isa? flags 0x100 > > device npx0 at nexus? port IO_NPX irq 13 > > device sio0 at isa? port IO_COM1 flags 0x10 irq 4 > > device sio1 at isa? port IO_COM2 irq 3 > > device miibus # MII bus support > > device sis # Silicon Integrated > > Systems SiS 900/SiS 7016 > > device xl # 3Com 3c90x > > (``Boomerang'', ``Cyclone'') > > pseudo-device loop # Network loopback > > pseudo-device ether # Ethernet support > > pseudo-device tun # Packet tunnel. > > pseudo-device pty # Pseudo-ttys (telnet etc) > > pseudo-device md # Memory "disks" > > #pseudo-device gif # IPv6 and IPv4 tunneling > > #pseudo-device faith 1 # IPv6-to-IPv4 relaying > > (translation) > > pseudo-device bpf #Berkeley packet filter > > options INCLUDE_CONFIG_FILE # Include this file in kernel > > #pseudo-device stf #6to4 IPv6 over > > IPv4 encapsulation > > #options IPFIREWALL #firewall > > #options IPFIREWALL_VERBOSE #enable logging to syslogd(8) > > #options IPFIREWALL_FORWARD #enable transparent proxy support > > #options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity > > #options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default > > #options IPV6FIREWALL #firewall for IPv6 > > #options IPV6FIREWALL_VERBOSE > > #options IPV6FIREWALL_VERBOSE_LIMIT=100 > > #options IPV6FIREWALL_DEFAULT_TO_ACCEPT > > #options IPDIVERT #divert sockets > > #options IPSTEALTH #support for stealth forwarding > > options RANDOM_IP_ID > > #options DUMMYNET > > #options BRIDGE > > #options UFS_DIRHASH > > options QUOTA #enable disk quotas > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 12 23:53:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rutger.owt.com (rutger.owt.com [204.118.6.16]) by hub.freebsd.org (Postfix) with ESMTP id 93ED237B416 for ; Mon, 12 Nov 2001 23:53:11 -0800 (PST) Received: from owt.com (owt-207-41-94-232.owt.com [207.41.94.232]) by rutger.owt.com (8.9.3/8.9.3) with ESMTP id XAA09367; Mon, 12 Nov 2001 23:53:03 -0800 Message-ID: <3BF0D15E.7060105@owt.com> Date: Mon, 12 Nov 2001 23:53:02 -0800 From: Kent Stewart User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Wilko Bulte Cc: Mit Rowe , stable@FreeBSD.ORG Subject: Re: kernel build problem References: <20011113083755.B35646@freebie.xs4all.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wilko Bulte wrote: > On Tue, Nov 13, 2001 at 02:29:43AM -0500, Mit Rowe wrote: > > Same problem here on an Alpha machine. > This has been happening for about a week. A "config -r" seems cure it if you are doing a kernel build that way. A clean /usr/obj works for me with the buildkernel. Kent > >>hmm... is it using the /compat/linux stuff? I'm using the 6.1 stuff from >>/usr/ports/emulators/linux_base/. I'll upgrade to 62, and recompile, and if >>that doesn't work, i'll do up to 71 and try again. >> >>Regardless of what happens, i'll report back. I doubt it will hurt for me to >>be up-to-date anyway ;-) >> >>-Mit >> >> >> >>>-----Original Message----- >>>From: owner-freebsd-stable@FreeBSD.ORG >>>[mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Mit Rowe >>>Sent: November 13, 2001 02:11 >>>To: stable@FreeBSD.ORG >>>Subject: kernel build problem >>> >>> >>>I'm having a problem building today's stable kernel, around the >>>linux_sysent >>>part. >>> >>>i'm using the standard compile options (no overrides in >>>/etc/make.conf) and >>>my conf file is below. >>> >>> > -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://users.owt.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 0:27:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from castle.dreaming.org (castle.dreaming.org [216.221.214.170]) by hub.freebsd.org (Postfix) with ESMTP id D983937B419 for ; Tue, 13 Nov 2001 00:27:23 -0800 (PST) Received: (from root@localhost) by castle.dreaming.org (8.11.6/8.11.6) id fAD8RNe28240; Tue, 13 Nov 2001 03:27:23 -0500 (EST) (envelope-from mitayai@dreaming.org) Received: from cr411661a (shadow.dreamlabs.com [216.129.214.38]) (authenticated) by castle.dreaming.org (8.11.6/8.11.6av) with ESMTP id fAD8RLY28231; Tue, 13 Nov 2001 03:27:21 -0500 (EST) (envelope-from mitayai@dreaming.org) From: "Mit Rowe" To: "Kent Stewart" , "Wilko Bulte" Cc: Subject: RE: kernel build problem Date: Tue, 13 Nov 2001 03:24:12 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <3BF0D15E.7060105@owt.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG confirmed... that worked. I blew away my kernel build directory in /usr/obj/usr/src/sys and it build fine. Thanks! -Mit > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Kent Stewart > Sent: November 13, 2001 02:53 > To: Wilko Bulte > Cc: Mit Rowe; stable@FreeBSD.ORG > Subject: Re: kernel build problem > > > > > Wilko Bulte wrote: > > > On Tue, Nov 13, 2001 at 02:29:43AM -0500, Mit Rowe wrote: > > > > Same problem here on an Alpha machine. > > > > > This has been happening for about a week. A "config -r" seems cure it if > you are doing a kernel build that way. A clean /usr/obj works for me > with the buildkernel. > > Kent > > > > > >>hmm... is it using the /compat/linux stuff? I'm using the 6.1 stuff from > >>/usr/ports/emulators/linux_base/. I'll upgrade to 62, and > recompile, and if > >>that doesn't work, i'll do up to 71 and try again. > >> > >>Regardless of what happens, i'll report back. I doubt it will > hurt for me to > >>be up-to-date anyway ;-) > >> > >>-Mit > >> > >> > >> > >>>-----Original Message----- > >>>From: owner-freebsd-stable@FreeBSD.ORG > >>>[mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Mit Rowe > >>>Sent: November 13, 2001 02:11 > >>>To: stable@FreeBSD.ORG > >>>Subject: kernel build problem > >>> > >>> > >>>I'm having a problem building today's stable kernel, around the > >>>linux_sysent > >>>part. > >>> > >>>i'm using the standard compile options (no overrides in > >>>/etc/make.conf) and > >>>my conf file is below. > >>> > >>> > > > > > -- > Kent Stewart > Richland, WA > > mailto:kbstew99@hotmail.com > http://users.owt.com/kstewart/index.html > FreeBSD News http://daily.daemonnews.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 0:57:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gsaix2.cc.GaSoU.EDU (gsaix2.cc.GaSoU.edu [141.165.1.57]) by hub.freebsd.org (Postfix) with ESMTP id 94EC437B416 for ; Tue, 13 Nov 2001 00:57:22 -0800 (PST) Received: from localhost (gsi22419@localhost) by gsaix2.cc.GaSoU.EDU (8.9.2/8.9.2) with SMTP id DAA37478; Tue, 13 Nov 2001 03:56:44 -0500 Date: Tue, 13 Nov 2001 03:56:43 -0500 (EST) From: Scott Dodson To: Kent Stewart Cc: Wilko Bulte , Mit Rowe , stable@FreeBSD.ORG Subject: Re: kernel build problem In-Reply-To: <3BF0D15E.7060105@owt.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 12 Nov 2001, Kent Stewart wrote: > This has been happening for about a week. A "config -r" seems cure it if > you are doing a kernel build that way. A clean /usr/obj works for me > with the buildkernel. > > Kent Doesn't this break the order prescribed when updating via sources? buildworld, buildkernel, installkernel, installworld ? -- scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 1:19:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rutger.owt.com (rutger.owt.com [204.118.6.16]) by hub.freebsd.org (Postfix) with ESMTP id 8479437B416 for ; Tue, 13 Nov 2001 01:19:16 -0800 (PST) Received: from owt.com (owt-207-41-94-232.owt.com [207.41.94.232]) by rutger.owt.com (8.9.3/8.9.3) with ESMTP id BAA12475; Tue, 13 Nov 2001 01:19:07 -0800 Message-ID: <3BF0E58A.4060903@owt.com> Date: Tue, 13 Nov 2001 01:19:06 -0800 From: Kent Stewart User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Scott Dodson Cc: Wilko Bulte , Mit Rowe , stable@FreeBSD.ORG Subject: Re: kernel build problem References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Scott Dodson wrote: > On Mon, 12 Nov 2001, Kent Stewart wrote: > >>This has been happening for about a week. A "config -r" seems cure it if >>you are doing a kernel build that way. A clean /usr/obj works for me >>with the buildkernel. >> >>Kent >> > > Doesn't this break the order prescribed when updating via sources? > buildworld, buildkernel, installkernel, installworld ? That is only recommended if you have done a cvsup. A buildkernel works just fine. A config style build after that doesn't. Kent > > -- > scott > > > > > . > > -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://users.owt.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 1:50:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id D7A2A37B418 for ; Tue, 13 Nov 2001 01:50:40 -0800 (PST) Received: (from root@localhost) by plab.ku.dk (8.11.3/8.9.3) id fAD9odK83011 for freebsd-stable@freebsd.org.AVP; Tue, 13 Nov 2001 10:50:39 +0100 (CET) (envelope-from dmitry@karasik.eu.org) Received: from raven.plab.ku.dk (raven.plab.ku.dk [130.225.105.67]) by plab.ku.dk (8.11.3/8.9.3) with ESMTP id fAD9odJ83003 for ; Tue, 13 Nov 2001 10:50:39 +0100 (CET) (envelope-from dmitry@karasik.eu.org) Subject: Weird resolver behavior Content-Transfer-Encoding: 8bit To: freebsd-stable@freebsd.org From: Dmitry Karasik Keywords: 2001334874 Content-Type: text/plain; charset="koi8-r" Lines: 44 MIME-Version: 1.0 Date: 12 Nov 2001 11:26:36 +0100 X-Mailer: Mail::Mailer[v1.40] Net::SMTP[v2.17] Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello all I'm seeking advice on what might have happened and what can be done in the following situation. I noticed that 'ssh prima.eu.org' for me takes 0.2 sec, while 'ssh cvs.prima.eu.org' takes ~30 sec, while these two are the same machine. I suspected DNS misconfiguration, but didn't find any. Well at least I didn't touch anything for months there. Anyway, the tcpdump output to the closest resolver was: 17:10:10.601561 plab.ku.dk.2702 > danpost.uni-c.dk.domain: 40331+ AAAA? cvs.prima.eu.org. (34) 17:10:10.605903 danpost.uni-c.dk.domain > plab.ku.dk.2702: 56366 ServFail0/0/0 (48) and so on with typical retranmission timeouts: 2, 5, 6, 3 seconds etc. The AAAA intrigued me very much. I didn't find any mention to it in RFC1035, but well it might be pretty valid; I just don't know. Nevertheless, something is wrong, because /var/log/messages is thrashed by Nov 8 15:02:11 plab named[228]: sysquery: no addrs found for root NS (AUTH210.NS.UU.NET) Nov 8 15:02:11 plab named[228]: sysquery: no addrs found for root NS () Nov 8 15:02:11 plab named[228]: sysquery: no addrs found for root NS (AUTH210.NS.UU.NET) Nov 8 15:02:11 plab named[228]: sysquery: no addrs found for root NS () Nov 8 15:02:15 plab named[228]: sysquery: no addrs found for root NS (mail.ftf.net) Nov 8 15:02:15 plab named[228]: sysquery: no addrs found for root NS (hotel.ftf.net) and the like. Please help. System is FreeBSD-4.3-STABLE, named-8.2.3 -- Sincerely, Dmitry --- www.karasik.eu.org --- Life ain't fair, but the root password helps. - BOFH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 2:22:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.online.ie (mail.online.ie [213.159.130.68]) by hub.freebsd.org (Postfix) with ESMTP id 1232037B416 for ; Tue, 13 Nov 2001 02:22:10 -0800 (PST) Received: from liszt (unknown [193.120.4.195]); by mail.online.ie with ESMTP id 933907023; for ; Tue, 13 Nov 2001 10:22:08 +0000 (GMT) Message-ID: <000b01c16c2b$cdedecc0$7b00000a@TUADH.local> From: "Vincent D Murphy" To: Subject: 4.4-RELEASE CTM Date: Tue, 13 Nov 2001 10:13:13 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG i want to start using CTM to track 4.4-STABLE starting from a stock 4.4-RELEASE install. which delta files do i start with? i want to track the ports and all source, basically everything i need to 'make world'. (please CC me in any replies) thanks, -vincent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 2:59:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from thrush.ravenbrook.com (thrush.ravenbrook.com [193.112.141.249]) by hub.freebsd.org (Postfix) with ESMTP id 61DE737B416 for ; Tue, 13 Nov 2001 02:59:47 -0800 (PST) Received: from thrush.ravenbrook.com (localhost [127.0.0.1]) by thrush.ravenbrook.com (8.11.6/8.11.6) with ESMTP id fADAxNG20204; Tue, 13 Nov 2001 10:59:23 GMT (envelope-from nb@thrush.ravenbrook.com) From: Nick Barnes To: Dmitry Karasik Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Weird resolver behavior In-Reply-To: Message from Dmitry Karasik of "12 Nov 2001 11:26:36 +0100." Date: Tue, 13 Nov 2001 10:59:23 +0000 Message-ID: <20202.1005649163@thrush.ravenbrook.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG AAAA is an IPv6 address record; RFC1886. Nick B At 2001-11-12 10:26:36+0000, Dmitry Karasik writes: > > Hello all > > I'm seeking advice on what might have happened and what can be done in the > following situation. I noticed that 'ssh prima.eu.org' for me takes 0.2 > sec, while 'ssh cvs.prima.eu.org' takes ~30 sec, while these two are the same > machine. > > I suspected DNS misconfiguration, but didn't find any. Well at least > I didn't touch anything for months there. Anyway, the tcpdump output to the > closest resolver was: > > 17:10:10.601561 plab.ku.dk.2702 > danpost.uni-c.dk.domain: 40331+ AAAA? cvs.prima.eu.org. (34) > 17:10:10.605903 danpost.uni-c.dk.domain > plab.ku.dk.2702: 56366 ServFail0/0/0 (48) > > and so on with typical retranmission timeouts: 2, 5, 6, 3 seconds etc. > > The AAAA intrigued me very much. I didn't find any mention to it in > RFC1035, but well it might be pretty valid; I just don't know. > > Nevertheless, something is wrong, because /var/log/messages is thrashed by > > Nov 8 15:02:11 plab named[228]: sysquery: no addrs found for root NS (AUTH210.NS.UU.NET) > Nov 8 15:02:11 plab named[228]: sysquery: no addrs found for root NS () > Nov 8 15:02:11 plab named[228]: sysquery: no addrs found for root NS (AUTH210.NS.UU.NET) > Nov 8 15:02:11 plab named[228]: sysquery: no addrs found for root NS () > Nov 8 15:02:15 plab named[228]: sysquery: no addrs found for root NS (mail.ftf.net) > Nov 8 15:02:15 plab named[228]: sysquery: no addrs found for root NS (hotel.ftf.net) > > and the like. > > Please help. > > System is FreeBSD-4.3-STABLE, named-8.2.3 > > -- > Sincerely, > Dmitry > > --- www.karasik.eu.org --- > > Life ain't fair, but the root password helps. > - BOFH > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 3:11:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tenchi.dreamlabs.com (tenchi.dreamlabs.com [216.220.37.61]) by hub.freebsd.org (Postfix) with ESMTP id 379C337B405 for ; Tue, 13 Nov 2001 03:11:13 -0800 (PST) Received: (from root@localhost) by tenchi.dreamlabs.com (8.11.6/8.11.6) id fADBB6Q83916 for stable@freebsd.org; Tue, 13 Nov 2001 06:11:06 -0500 (EST) (envelope-from mitayai@dreamlabs.com) Received: from cr411661a (shadow.dreamlabs.com [216.129.214.38]) (authenticated) by tenchi.dreamlabs.com (8.11.6/8.11.6av) with ESMTP id fADBB3783906 for ; Tue, 13 Nov 2001 06:11:04 -0500 (EST) (envelope-from mitayai@dreamlabs.com) From: "Mit Rowe" To: Subject: ATA Hard Drives Date: Tue, 13 Nov 2001 06:07:54 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Quick Question... What is the largest/fastest ATA drives currently supported by -STABLE? -Mit ___________________________________________________________ Mit Rowe (Will Mitayai Keeso Rowe) Internet Services DreamLabs/Branch Media Inc. ph: 416.323.0840 ext. 262 260 Richmond St. East Suite 200 fax: 416.323.0894 Toronto, Ontario M5A 1P4 icq: 7161728 Canada mit@dreamlabs.com / mit@branchmedia.com ___________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 3:13: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id 76B9737B416 for ; Tue, 13 Nov 2001 03:13:03 -0800 (PST) Received: from colt.ncptiddische.net (ppp-166.wobline.de [212.68.69.174]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id fADBD0523300; Tue, 13 Nov 2001 12:13:00 +0100 Received: from jodie.ncptiddische.net (jodie.ncptiddische.net [192.168.0.2]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fADBDPV18321; Tue, 13 Nov 2001 12:13:25 +0100 (CET) (envelope-from nils@tisys.org) Received: from jodie.ncptiddische.net (jodie.ncptiddische.net [192.168.0.2]) by jodie.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fADBDZU57157; Tue, 13 Nov 2001 12:13:35 +0100 (CET) (envelope-from nils@tisys.org) Date: Tue, 13 Nov 2001 12:13:35 +0100 (CET) From: Nils Holland To: Vincent D Murphy Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 4.4-RELEASE CTM In-Reply-To: <000b01c16c2b$cdedecc0$7b00000a@TUADH.local> Message-ID: <20011113121201.D56922-100000@jodie.ncptiddische.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 13 Nov 2001, Vincent D Murphy wrote: > i want to start using CTM to track 4.4-STABLE starting from a stock > 4.4-RELEASE install. > > which delta files do i start with? i want to track the ports and all > source, basically everything i need to 'make world'. Well, I would probably only recommend CTM as a last resort. If possible, you should consider using CVSup. It's much more reliable and will probably save you quite a few headaches. And, oh: You don't really need "ports" to make world ;-) Greetings Nils Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 3:18:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailout2.informatik.tu-muenchen.de (mailout2.informatik.tu-muenchen.de [131.159.254.8]) by hub.freebsd.org (Postfix) with ESMTP id 3BB6637B416 for ; Tue, 13 Nov 2001 03:18:39 -0800 (PST) Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by mailout2.informatik.tu-muenchen.de (Postfix) with ESMTP id 07FB38123; Tue, 13 Nov 2001 12:18:38 +0100 (MET) Received: from atrbg11.informatik.tu-muenchen.de (atrbg11.informatik.tu-muenchen.de [131.159.24.91]) by tuminfo2.informatik.tu-muenchen.de (Postfix) with ESMTP id 4C3F010AC1; Tue, 13 Nov 2001 12:18:34 +0100 (MET) Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id 8EC44136E3; Tue, 13 Nov 2001 12:18:37 +0100 (CET) Date: Tue, 13 Nov 2001 12:18:37 +0100 From: Daniel Lang To: Bill Moran Cc: freebsd-stable@FreeBSD.ORG Subject: Re: dirpref benefit on virtual disks Message-ID: <20011113121837.A34946@atrbg11.informatik.tu-muenchen.de> References: <20011112152726.A10505@atrbg11.informatik.tu-muenchen.de> <3BF013B8.8070009@potentialtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BF013B8.8070009@potentialtech.com>; from wmoran@potentialtech.com on Mon, Nov 12, 2001 at 01:23:52PM -0500 X-Geek: GCS/CC d-- s: a- C++$ UBS++++$ P+++$ L- E-(---) W+++(--) N++ o K w--- O? M? V? PS+(++) PE--(+) Y+ PGP+ t++ 5+++ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y+ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Bill Moran wrote on Mon, Nov 12, 2001 at 01:23:52PM -0500: [..] > That being said, I don't _know_. It would be interesting to test > it. Since you're already considering recreating directories, why > not do a test to see if it's worth it? Just take a directory tree [..] I just did it. I've copied the FreeBSD mirror (which should be complicated enough) onto a free partition, and then ran a find on the original location and then on the new one. The find command was: find . -print > /dev/null the result seemed convincing old dirpref: 2.97s user 67.45s system 6% cpu 17:36.22 total new dirpref: 2.09s user 5.94s system 5% cpu 2:39.32 total But I cannot rule our side-effects. The system is not quiet, and the array with the old code is much more busy than the spare one, which is not busy at all. Anyway, I will recreate the tree on the busy array und do the test again. Thanks so far, Daniel -- IRCnet: Mr-Spock - Burn them to ashes, then burn the ashes. - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 3:21: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.online.ie (mail.online.ie [213.159.130.68]) by hub.freebsd.org (Postfix) with ESMTP id 1479E37B416 for ; Tue, 13 Nov 2001 03:21:06 -0800 (PST) Received: from liszt (unknown [193.120.4.195]); by mail.online.ie with ESMTP id B7D757032; Tue, 13 Nov 2001 11:21:04 +0000 (GMT) Message-ID: <000901c16c34$098a43c0$7b00000a@TUADH.local> From: "Vincent D Murphy" To: "Nils Holland" , References: <20011113121201.D56922-100000@jodie.ncptiddische.net> Subject: Re: 4.4-RELEASE CTM Date: Tue, 13 Nov 2001 11:12:09 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG nils holland wrote: > On Tue, 13 Nov 2001, Vincent D Murphy wrote: > > > i want to start using CTM to track 4.4-STABLE starting from a stock > > 4.4-RELEASE install. > > > > which delta files do i start with? i want to track the ports and all > > source, basically everything i need to 'make world'. > > Well, I would probably only recommend CTM as a last resort. If possible, > you should consider using CVSup. It's much more reliable and will probably > save you quite a few headaches. > > And, oh: You don't really need "ports" to make world ;-) i apologise for not mentioning that the 4.4-STABLE machine in question is offline from the Internet; hence my desire to use CTM. i want to get the deltas at work, burn them on to sneakernet media and update the offline machine at home. downloading *all* of the deltas looks like a lot of work/bandwidth, and so i would like to know a point corresponding to the 4.4-STABLE CDs from which i can download all subsequent deltas. thanks, -vincent PS do you care to elaborate on the 'headaches' CTM can potentially cause? that sounds scary. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 3:22:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sanctuary.magill.unisa.edu.au (sanctuary.magill.unisa.edu.au [130.220.227.239]) by hub.freebsd.org (Postfix) with ESMTP id 0A65837B417 for ; Tue, 13 Nov 2001 03:22:46 -0800 (PST) Received: from localhost (sayersjm@localhost) by sanctuary.magill.unisa.edu.au (8.11.6/8.11.4) with ESMTP id fADBMJk80195; Tue, 13 Nov 2001 21:52:20 +1030 (CST) (envelope-from Jarrod.Sayers@unisa.edu.au) Date: Tue, 13 Nov 2001 21:52:19 +1030 (CST) From: Jarrod Sayers X-X-Sender: sayersjm@sanctuary.magill.unisa.edu.au To: Mit Rowe Cc: stable@freebsd.org Subject: Re: ATA Hard Drives In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 13 Nov 2001, Mit Rowe wrote: > Date: Tue, 13 Nov 2001 06:07:54 -0500 > From: Mit Rowe > To: stable@freebsd.org > Subject: ATA Hard Drives > > Quick Question... > > What is the largest/fastest ATA drives currently supported by -STABLE? > > -Mit I don't know if a size limit is documented... In practice, we are running 3 Seagate 80GB's off a Promise ATA100 card on a 4.4-STABLE machine cvsupped a month or so ago I think. This machine is currently looking after cvsup.au.freebsd.org and has no dramas at all with the load. ad4: 76319MB [155061/16/63] at ata2-master UDMA100 ad5: 76319MB [155061/16/63] at ata2-slave UDMA100 ad6: 76319MB [155061/16/63] at ata3-master UDMA100 Jarrod Sayers Client Services Information Technology Services Unit University of South Australia, Magill Campus. Phone: +61 8 8302 4809 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 3:52:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scribble.fsn.hu (scribble.fsn.hu [193.224.40.95]) by hub.freebsd.org (Postfix) with SMTP id 7AAC737B416 for ; Tue, 13 Nov 2001 03:52:52 -0800 (PST) Received: (qmail 40592 invoked by uid 1000); 13 Nov 2001 11:52:51 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 13 Nov 2001 11:52:51 -0000 Date: Tue, 13 Nov 2001 12:52:51 +0100 (CET) From: Attila Nagy To: Mit Rowe Cc: stable@freebsd.org Subject: Re: ATA Hard Drives In-Reply-To: Message-ID: <20011113124823.X38684-100000@scribble.fsn.hu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, > What is the largest/fastest ATA drives currently supported by -STABLE? FreeBSD supports 48 bit addressing (introduced with ATA133 standard), so the limit is quite theoretical. BTW, the largest ATA drive I know of is the Maxtor 4G160J8 (160 GBs). Although this may be the largest it isn't the fastest, because it spins only with 5400 RPM. -------------------------------------------------------------------------- Attila Nagy e-mail: Attila.Nagy@fsn.hu Budapest Polytechnic (BMF.HU) @work: +361 210 1415 (194) H-1084 Budapest, Tavaszmezo u. 15-17. cell.: +3630 306 6758 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 4: 0:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gw.novag.spb.ru (ns.novag.spb.ru [195.5.156.77]) by hub.freebsd.org (Postfix) with ESMTP id A8E2837B405 for ; Tue, 13 Nov 2001 04:00:47 -0800 (PST) Received: from alf (alf.novag.spb.ru [195.5.158.20]) by gw.novag.spb.ru (8.11.6/8.11.6) with SMTP id fADC0ih08359 for ; Tue, 13 Nov 2001 15:00:45 +0300 (MSK) (envelope-from Sergey@Novag.spb.ru) Message-ID: <00be01c16c3a$d3c39dc0$149e05c3@alf> From: "Sergey Morozov" To: Subject: subscribe Date: Tue, 13 Nov 2001 15:00:44 +0300 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 4:27:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id 2BD6B37B418 for ; Tue, 13 Nov 2001 04:27:27 -0800 (PST) Received: from colt.ncptiddische.net (ppp-190.wobline.de [212.68.69.201]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id fADCRO530577; Tue, 13 Nov 2001 13:27:24 +0100 Received: from jodie.ncptiddische.net (jodie.ncptiddische.net [192.168.0.2]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fADCRnV18630; Tue, 13 Nov 2001 13:27:49 +0100 (CET) (envelope-from nils@tisys.org) Received: from jodie.ncptiddische.net (jodie.ncptiddische.net [192.168.0.2]) by jodie.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fADCS0U65218; Tue, 13 Nov 2001 13:28:00 +0100 (CET) (envelope-from nils@tisys.org) Date: Tue, 13 Nov 2001 13:28:00 +0100 (CET) From: Nils Holland To: Vincent D Murphy Cc: freebsd-stable@freebsd.org Subject: Re: 4.4-RELEASE CTM In-Reply-To: <000901c16c34$098a43c0$7b00000a@TUADH.local> Message-ID: <20011113132310.I65191-100000@jodie.ncptiddische.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 13 Nov 2001, Vincent D Murphy wrote: > i apologise for not mentioning that the 4.4-STABLE machine in question is > offline from the Internet; hence my desire to use CTM. > > i want to get the deltas at work, burn them on to sneakernet media and > update the offline machine at home. downloading *all* of the deltas looks > like a lot of work/bandwidth, and so i would like to know a point > corresponding to the 4.4-STABLE CDs from which i can download all subsequent > deltas. I'm pretty sure that if you ask this question on freebsd-questions@freebsd.org, someone will be able to help you. > PS do you care to elaborate on the 'headaches' CTM can potentially cause? > that sounds scary. :) Well, I have never used CTM, so what I have said is only based on what I have read and heart in the documentation and on mailing-lists. So, if you don't get a deifinite answer to yoru question on this list, try posting it to freebsd-questions@freebsd.org, as I'm sure someone there will have a few suggestions for you. Greetings Nils Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 6:46: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dell-serv-1.phoenixmedical.co.uk (dell-serv-1.phoenixmedical.co.uk [213.38.153.186]) by hub.freebsd.org (Postfix) with SMTP id 0DEC537B418 for ; Tue, 13 Nov 2001 06:46:04 -0800 (PST) Received: from no.name.available by dell-serv-1.phoenixmedical.co.uk via smtpd (for hub.FreeBSD.org [216.136.204.18]) with SMTP; 13 Nov 2001 14:30:10 UT Received: by dell-serv-1.phoenixmedical.co.uk with Internet Mail Service (5.5.2650.21) id ; Tue, 13 Nov 2001 13:46:54 -0000 Message-ID: <99A83EE8C34AD311809C009027936117144B62@dell-serv-1.phoenixmedical.co.uk> From: Tomas Palfi To: "'freebsd-stable@FreeBSD.ORG'" Subject: jdk1.2.2 Date: Tue, 13 Nov 2001 13:46:54 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG all, trying to 'gmake world' in order to build jdk1.2.2, I am getting this message: /usr/local/jdk1.2.2/bin/javac: not found gmake[3]: *** [.compile.classlist] Error 127 gmake[3]: Leaving directory `/usr/local/jdk1.2.2/build/freebsd/java/jvm' gmake[2]: *** [optimized] Error 2 gmake[2]: Leaving directory `/usr/local/jdk1.2.2/build/freebsd/java/jvm' gmake[1]: *** [all] Error 1 gmake[1]: Leaving directory `/usr/local/jdk1.2.2/build/freebsd/java' gmake: *** [all] Error 1 maranello# is the /usr/local/jdk1.2.2/bin/javac the directory i have unpacked the jdk source and if how come i haven't got any bin dirs there. the only selection of files i have there are: /usr/local/jdk1.2.2 maranello# ls LegalReadme.html build src OriginalCode.txt ext zipnote README.html jdk1_2_2-src.zip maranello# (am i supposed to install jdk1.2.2 for Solaris first and then set the directories) it's probably me, but i am lost now. thank you -- Tomas Palfi Group I.T. Department Phoenix Medical Supplies Ltd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 7:13:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 286AB37B405; Tue, 13 Nov 2001 07:13:34 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 13 Nov 2001 15:13:33 +0000 (GMT) Date: Tue, 13 Nov 2001 15:13:29 +0000 From: David Malone To: Eugene Grosbein Cc: stable@freebsd.org, hackers@freebsd.org Subject: Re: kern.vm.kmem.size Message-ID: <20011113151329.A44837@walton.maths.tcd.ie> References: <20011111230817.A2325@grosbein.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011111230817.A2325@grosbein.pp.ru>; from eugen@grosbein.pp.ru on Sun, Nov 11, 2001 at 11:08:17PM +0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Nov 11, 2001 at 11:08:17PM +0700, Eugene Grosbein wrote: > I'm trying to test and tune speed of freebsd's filesystem in many aspects. > I run recent FreeBSD 4.4-STABLE with new dirprefs code, read tuning(7), > newfs'd my FS, turned softupdates on, have UFS_DIRHASH kernel option. > Also, I've read DIRHASH kernel code source. It seems that efficiency of > DIRHASH greatly depends of kernel memory size (and some experiments > approve this). You should be able to control how much memory is used by dirhash with the vfs.ufs.dirhash_maxmem sysctl. By default it uses up to 2MB and it should be possible to raise it significantly, providing you have enough physical memory. (By default there is about 1GB of kernel address space, so you are unlikely to be running into this limit - I don't think changing kern.vm.kmem.size will help you). Remember - raising it will only help you if your working set of oversized directories is larger that what fits into the memory allocated for dirhash. I'd suggest that you watch how much memory dirhash is using "vmstat -m" and examinign the dirhash line. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 7:51:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from D00015.dialonly.kemerovo.su (www2.svzserv.kemerovo.su [213.184.65.86]) by hub.freebsd.org (Postfix) with ESMTP id 3FFD637B418; Tue, 13 Nov 2001 07:51:31 -0800 (PST) Received: (from eugen@localhost) by D00015.dialonly.kemerovo.su (8.11.6/8.11.4) id fADFlUT00911; Tue, 13 Nov 2001 22:47:30 +0700 (KRAT) (envelope-from eugen) Date: Tue, 13 Nov 2001 22:47:30 +0700 From: Eugene Grosbein To: David Malone Cc: stable@freebsd.org, hackers@freebsd.org Subject: Re: kern.vm.kmem.size Message-ID: <20011113224730.A864@grosbein.pp.ru> References: <20011111230817.A2325@grosbein.pp.ru> <20011113151329.A44837@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011113151329.A44837@walton.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Tue, Nov 13, 2001 at 03:13:29PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Nov 13, 2001 at 03:13:29PM +0000, David Malone wrote: > > I'm trying to test and tune speed of freebsd's filesystem in many aspects. > > I run recent FreeBSD 4.4-STABLE with new dirprefs code, read tuning(7), > > newfs'd my FS, turned softupdates on, have UFS_DIRHASH kernel option. > > Also, I've read DIRHASH kernel code source. It seems that efficiency of > > DIRHASH greatly depends of kernel memory size (and some experiments > > approve this). > > You should be able to control how much memory is used by dirhash > with the vfs.ufs.dirhash_maxmem sysctl. By default it uses up to > 2MB and it should be possible to raise it significantly, providing > you have enough physical memory. (By default there is about 1GB of > kernel address space, so you are unlikely to be running into this > limit - I don't think changing kern.vm.kmem.size will help you). Are you shure? From LINT: # Tune the kernel malloc area parameters. VM_KMEM_SIZE represents the # minimum, in bytes, and is typically (12*1024*1024) (12MB). # VM_KMEM_SIZE_MAX represents the maximum, typically 200 megabytes. # VM_KMEM_SIZE_SCALE can be set to adjust the auto-tuning factor, which # typically defaults to 4 (kernel malloc area size is physical memory # divided by the scale factor). # options VM_KMEM_SIZE="(10*1024*1024)" options VM_KMEM_SIZE_MAX="(100*1024*1024)" options VM_KMEM_SIZE_SCALE="4" It seems DIRHASH is limited with free space in the kernel malloc area. It even cannot utilize default 2M of vfs.ufs.dirhash_maxmem when I do not increase kern.vm.kmem.size. I think it's because of kernel malloc area exhaustion. However, when I increase kern.vm.kmem.size upto 64M and vfs.ufs.dirhash_maxmem upto 8M, it starts using more than 2M of dirhash memory and speed of my tests greatly improves. So, how can I estimate needed value of kern.vm.kmem.size? Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 8:19: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [129.83.20.90]) by hub.freebsd.org (Postfix) with ESMTP id B160A37B416 for ; Tue, 13 Nov 2001 08:19:00 -0800 (PST) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id fADGEv822747; Tue, 13 Nov 2001 11:14:57 -0500 (EST) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id fADGEvs26682; Tue, 13 Nov 2001 11:14:57 -0500 (EST) Received: from dhcp-105-164.mitre.org (128.29.105.164) by mailhub2.mitre.org with SMTP id 8343459; Tue, 13 Nov 2001 11:14:55 -0500 Message-ID: <3BF146FE.7C7AD7E5@mitre.org> Date: Tue, 13 Nov 2001 11:14:54 -0500 From: Jason Andresen Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Jan Schlesner Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 4.3 Release / XFree86 4.1 / KDE 2.1.1 References: <00b801c16945$00e2ad80$13fea8c0@drs> <20011110150303.B57051@physik.TU-Berlin.DE> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jan Schlesner wrote: > > On Fri, Nov 09, 2001 at 10:36:02AM -0700, Don Sutter wrote: > > /usr/X11R6/lib/libMesaGL.so: undefined reference to > > `pthread_getspecific' > > /usr/X11R6/lib/libMesaGL.so: undefined reference to > > `pthread_key_create' > > /usr/X11R6/lib/libMesaGL.so: undefined reference to > > `pthread_setspecific' > > I think, that you must install Mesa (/usr/ports/graphics/Mesa3). > I don't know, why it doesn't install Mesa automatically. Mesa is installed, the problem is that Mesa was compiled with pthreads support and whatever you're compiling doesn't set the flag correctly. I used to run into this ALL the time. The workaround is to go into the port itself and add -pthread to the link line. It should work after that. Generally this is something like: executable: $(OBJS) $(AND_STUFF) $(CLINK) You just need to change it to $(CLINK) -pthread -- \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org |\/ | | | / _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 9: 4:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from kirk.sector14.net (66-61-170-163.mtc2.cox.rr.com [66.61.170.163]) by hub.freebsd.org (Postfix) with ESMTP id 6936537B405 for ; Tue, 13 Nov 2001 09:04:54 -0800 (PST) Received: (from dgl@localhost) by kirk.sector14.net (8.11.3/8.11.3) id fADH4n590573 for freebsd-stable@freebsd.org; Tue, 13 Nov 2001 12:04:49 -0500 (EST) (envelope-from dgl) Date: Tue, 13 Nov 2001 12:03:55 -0500 From: Doug Lee To: freebsd-stable@freebsd.org Subject: ftpd/smbfs combo producing garbage files--anyone else seen this? Message-ID: <20011113120355.I87301@kirk.sector14.net> Mail-Followup-To: Doug Lee , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Bartimaeus Group Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I submitted a PR on this issue on 11/01/01, but the PR has not been modified since (I'm sure everyone is busy; this isn't a complaint so much as a curious question). This is the main content of the PR. Has anyone else seen this problem occur? >Synopsis: 2872-or-less-byte ftp binary transfer from smbfs share produces garbage >Release: FreeBSD 4.3-STABLE i386 >Environment: System: FreeBSD kirk.sector14.net 4.3-STABLE FreeBSD 4.3-STABLE #5: Mon May 28 01:57:16 EDT 2001 dgl@kirk.sector14.net:/usr/obj/usr/src/sys/CUSTOM i386 Using smbfs-1.4.1 Using standard ftpd; problem does not occur when using wu-ftpd-2.6.1. >Description: Trying to ftp a short file from a mounted smbfs share using binary mode will produce garbage in the garbage file instead of a copy of the file being transferred. The garbage varies from one attempt to the next. This occurs even when using "ftp localhost." It does not occur when transferring from a UFS mount or when transferring in ASCII mode, or when the file is larger than 2872 bytes. The problem does not occur when accessing the smbfs-mounted file by other means (e.g., ex/vi, cp, or even copying to a Windows box via a Samba share). tcpdump during the corrupted ftp shows that data moves correctly from smbfs-mounted machine to FreeBSD but is incorrect by the time it leaves FreeBSD (via ftpd) for its final destination. Reproduced on two machines running different 4.3-STABLE snapshots. Transfers using wu-ftpd-2.6.1 work properly. >How-To-Repeat: Mount a Windows share via smbfs, ftp localhost on the FreeBSD box, log in and change to binary mode, and get a file of2872 bytes or less from somewhere under the smbfs mount point. Compare original and transferred files. >Fix: Workaround: Copy the needed file via means other than ftp to a UFS mount before getting it with FTP, or use a different ftpd. -- Doug Lee dgl@visi.com http://www.visi.com/~dgl Bartimaeus Group doug@bartsite.com http://www.bartsite.com "It's not easy to be crafty and winsome at the same time, and few accomplish it after the age of six." --D. Sutton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 9:31:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 69C4D37B418 for ; Tue, 13 Nov 2001 09:31:34 -0800 (PST) Received: from mail2.uniserve.com ([204.244.156.10]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 163hPD-0004fZ-00; Tue, 13 Nov 2001 09:31:27 -0800 Date: Tue, 13 Nov 2001 09:31:27 -0800 (PST) From: Tom X-Sender: tom@athena.uniserve.ca To: Dmitry Karasik Cc: freebsd-stable@freebsd.org Subject: Re: Weird resolver behavior In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 12 Nov 2001, Dmitry Karasik wrote: ... > Nov 8 15:02:11 plab named[228]: sysquery: no addrs found for root NS (AUTH210.NS.UU.NET) > Nov 8 15:02:11 plab named[228]: sysquery: no addrs found for root NS () > Nov 8 15:02:11 plab named[228]: sysquery: no addrs found for root NS (AUTH210.NS.UU.NET) > Nov 8 15:02:11 plab named[228]: sysquery: no addrs found for root NS () > Nov 8 15:02:15 plab named[228]: sysquery: no addrs found for root NS (mail.ftf.net) > Nov 8 15:02:15 plab named[228]: sysquery: no addrs found for root NS (hotel.ftf.net) I think your root.cache file is old, or someone has damaged it by adding incorrect root servers. This file is included with BIND, or you can find a copy listing the current root servers someplace on internic.net Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 9:50:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from D00015.dialonly.kemerovo.su (www2.svzserv.kemerovo.su [213.184.65.86]) by hub.freebsd.org (Postfix) with ESMTP id 9715037B405 for ; Tue, 13 Nov 2001 09:50:09 -0800 (PST) Received: (from eugen@localhost) by D00015.dialonly.kemerovo.su (8.11.6/8.11.4) id fADHn7s03690 for stable@freebsd.org; Wed, 14 Nov 2001 00:49:07 +0700 (KRAT) (envelope-from eugen) Date: Wed, 14 Nov 2001 00:49:07 +0700 From: Eugene Grosbein To: stable@freebsd.org Subject: src/lib/libc/gen/initgroups.c: warn() breaks CVS protocol Message-ID: <20011114004907.D864@grosbein.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! I'm trying to setup local anonymous read-only CVS pserver for my mirror of FreeBSD CVS Repository. The Repo is owned by root. My system is 4.4-STABLE and I use stock cvs for 'cvs pserver -R'. I do not want cvs be allowed to write to the Repo or read /etc/master.passwd so I setup CVSROOT/passwd, CVSROOT/readers, CVSROOT/writers and I run cvspserver from inetd as non-root user 'anoncvs'. My CVSROOT/passwd file contains one line: anoncvs:hashed_password:anoncvs 'cvs login' works fine, but 'cvs checkout' does not. cvs(1) tries to call initgroups(3) and does not complain if it returns EPERM (see src/contrib/cvs/src/server.c, line 5286). But initgroups() uses warn(3) to note setgroups(2) failure. That breaks CVS protocol and client obtains this message: $ cvs checkout -r ppp_2_3_5 src/usr.sbin/pppd cvs [checkout aborted]: unrecognized auth response from my.anoncvs.host: cvs: setgroups: Operation not permitted I cannot run cvspserver as root because it does not use /etc/login.conf restrictions then. Using inetd is a perfect way to limit resource usage for cvs but this bug (or feature) of libc breaks protocol. So, the question is: will this be fixed? What if I just comment out that warn() in src/lib/libc/gen/initgroups.c? Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 10: 4: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from barbera.system.pl (barbera.system.pl [195.205.185.21]) by hub.freebsd.org (Postfix) with ESMTP id D292F37B405 for ; Tue, 13 Nov 2001 10:03:48 -0800 (PST) Received: (from saper@localhost) by barbera.system.pl (SYSTEM Internet) id fADI3df58297 for freebsd-stable@FreeBSD.org; Tue, 13 Nov 2001 19:03:39 +0100 (CET) Date: Tue, 13 Nov 2001 19:03:39 +0100 From: Marcin Cieslak To: freebsd-stable@FreeBSD.org Subject: Intel 82801AA (ICH) - unable to map IO port space on PCI? Message-ID: <20011113190339.A57871@barbera.system.pl> Mail-Followup-To: freebsd-stable@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG First time install on quite new HP Vectra machine, but I cannot get USB and embedded audio (AC'97) to work with very recent -STABLE. Fragment of dmesg output: isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1800-0x180f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: at device 31.2 on pci0 uhci0: Could not map ports device_probe_and_attach: uhci0 attach returned 6 ichsmb0: port 0x1810-0x181f irq 9 at device 31.3 on pci0 smbus0: on ichsmb0 smb0: on smbus0 pcm0: at device 31.5 on pci0 pcm0: unable to map IO port space device_probe_and_attach: pcm0 attach returned 6 I was supposing that the sound card is just not supported until I noticed similar message below the uhci0 entry. I get the same results without "device smbus/smb/ichsmb" entries - ichsmb0 gets unrecognized then, but sound and USB is still unusable. Output from pciconf -l: chip0@pci0:0:0: class=0x060000 card=0x11308086 chip=0x11308086 rev=0x02 hdr=0x00 pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x11318086 rev=0x02 hdr=0x01 pcib2@pci0:30:0: class=0x060400 card=0x00000000 chip=0x24188086 rev=0x02 hdr=0x01 isab0@pci0:31:0: class=0x060100 card=0x00000000 chip=0x24108086 rev=0x02 hdr=0x00 atapci0@pci0:31:1: class=0x010180 card=0x24118086 chip=0x24118086 rev=0x02 hdr=0x00 none0@pci0:31:2: class=0x0c0300 card=0x24128086 chip=0x24128086 rev=0x02 hdr=0x00 ichsmb0@pci0:31:3: class=0x0c0500 card=0x24138086 chip=0x24138086 rev=0x02 hdr=0x00 none1@pci0:31:5: class=0x040100 card=0x1249103c chip=0x24158086 rev=0x02 hdr=0x00 none2@pci2:0:0: class=0x030000 card=0x0541102b chip=0x0525102b rev=0x82 hdr=0x00 xl0@pci1:4:0: class=0x020000 card=0x1246103c chip=0x920010b7 rev=0x78 hdr=0x00 Kernel config enclosed below the sig. -- << Marcin Cieslak // saper@system.pl >> machine i386 cpu I586_CPU cpu I686_CPU ident ALT maxusers 64 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev device isa device pci device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices device amd # AMD 53C974 (Tekram DC-390(T)) device isp # Qlogic family device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets) options SYM_SETUP_LP_PROBE_MAP=0x40 # Allow ncr to attach legacy NCR devices when # both sym and ncr are configured device ncv # NCR 53C500 device nsp # Workbit Ninja SCSI-3 device stg # TMC 18C30/18C50 device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID device dpt # DPT Smartcache - See LINT for options! device mly # Mylex AcceleRAID/eXtremeRAID device aac # Adaptec FSA RAID, Dell PERC2/PERC3 device ida # Compaq Smart RAID device amr # AMI MegaRAID device mlx # Mylex DAC960 family device twe # 3ware Escalade device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? pseudo-device splash device sc0 at isa? flags 0x100 device npx0 at nexus? port IO_NPX irq 13 device apm0 at nexus? disable flags 0x20 # Advanced Power Management device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device device de # DEC/Intel DC21x4x (``Tulip'') device txp # 3Com 3cR990 (``Typhoon'') device vx # 3Com 3c590, 3c595 (``Vortex'') device miibus # MII bus support device dc # DEC/Intel 21143 and various workalikes device fxp # Intel EtherExpress PRO/100B (82557, 82558) device pcn # AMD Am79C97x PCI 10/100 NICs device rl # RealTek 8129/8139 device sf # Adaptec AIC-6915 (``Starfire'') device sis # Silicon Integrated Systems SiS 900/SiS 7016 device ste # Sundance ST201 (D-Link DFE-550TX) device tl # Texas Instruments ThunderLAN device tx # SMC EtherPower II (83c170 ``EPIC'') device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device wx # Intel Gigabit Ethernet Card (``Wiseman'') device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') device ex device ep device xe device awi device wi device an pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" pseudo-device gif # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) pseudo-device bpf #Berkeley packet filter device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device uscanner # Scanners device urio # Diamond Rio MP3 Player device aue # ADMtek USB ethernet device cue # CATC USB ethernet device kue # Kawasaki LSI USB ethernet device pcm device csa device sbc device smbus device smb device ichsmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 10: 4:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from D00015.dialonly.kemerovo.su (www2.svzserv.kemerovo.su [213.184.65.86]) by hub.freebsd.org (Postfix) with ESMTP id 238C137B418 for ; Tue, 13 Nov 2001 10:04:34 -0800 (PST) Received: (from eugen@localhost) by D00015.dialonly.kemerovo.su (8.11.6/8.11.4) id fADI3Nj03909; Wed, 14 Nov 2001 01:03:23 +0700 (KRAT) (envelope-from eugen) Date: Wed, 14 Nov 2001 01:03:23 +0700 From: Eugene Grosbein To: stable@FreeBSD.ORG Cc: fjoe@iclub.nsu.ru Subject: Re: src/lib/libc/gen/initgroups.c: warn() breaks CVS protocol Message-ID: <20011114010323.A3840@grosbein.pp.ru> References: <20011114004907.D864@grosbein.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011114004907.D864@grosbein.pp.ru>; from eugen@grosbein.pp.ru on Wed, Nov 14, 2001 at 12:49:07AM +0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Nov 14, 2001 at 12:49:07AM +0700, Eugene Grosbein wrote: > cvs(1) tries to call initgroups(3) and does not complain if it returns EPERM > (see src/contrib/cvs/src/server.c, line 5286). But initgroups() > uses warn(3) to note setgroups(2) failure. That breaks CVS protocol O, I see there is PR/15421 taking about this. Well, it was posted 1999, December and noted 2001, June, very funny. Deep silence since than, I see. How about commiting the patch from PR, somebody? Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 10:13:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from kirk.sector14.net (66-61-170-163.mtc2.cox.rr.com [66.61.170.163]) by hub.freebsd.org (Postfix) with ESMTP id C71E237B416 for ; Tue, 13 Nov 2001 10:13:39 -0800 (PST) Received: (from dgl@localhost) by kirk.sector14.net (8.11.3/8.11.3) id fADIDcY90966 for freebsd-stable@freebsd.org; Tue, 13 Nov 2001 13:13:38 -0500 (EST) (envelope-from dgl) Date: Tue, 13 Nov 2001 13:13:38 -0500 From: Doug Lee To: freebsd-stable@freebsd.org Subject: PCM or PCM and SBC for AWE64 sound card? Message-ID: <20011113131338.A90890@kirk.sector14.net> Mail-Followup-To: Doug Lee , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Bartimaeus Group Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [I sent this to freebsd-questions on 10/25/01 but heard nothing back. This problem predates the current issues with sound drivers I think. I'm hoping that submitting this here might help me find a solution, or become part of one. :-) ] Do I need to enable PCM and SBC or just PCM in my FreeBSD 4.3-STABLE (soon to be 4.4) kernel to support an AWE64 sound card? I've been using a kernel with both PCM and SBC enabled for a while, but I'm having problems recording (I'm told I can only record 8-bit samples by the apps I try with, but they then go ahead and record 16-bit samples and then tell me they're 8-bit samples, and unusable files result; sfmike from Speak Freely sends out garbage). Both devices are recognized at boot time: sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 pcm0: on sbc0 but I'm wondering if just PCM would be enough. What would I lose (or gain) by removing SBC support from my kernel? Please CC me directly. Thanks much. -- Doug Lee dgl@visi.com http://www.visi.com/~dgl Bartimaeus Group doug@bartsite.com http://www.bartsite.com "Determine that the thing can and shall be done, and then...find the way." - Abraham Lincoln To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 10:39:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 89DA237B418 for ; Tue, 13 Nov 2001 10:39:52 -0800 (PST) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id fADIdkd19632; Tue, 13 Nov 2001 10:39:46 -0800 (PST) Message-Id: <200111131839.fADIdkd19632@ptavv.es.net> To: Tom Cc: Dmitry Karasik , freebsd-stable@FreeBSD.ORG Subject: Re: Weird resolver behavior In-reply-to: Your message of "Tue, 13 Nov 2001 09:31:27 PST." Date: Tue, 13 Nov 2001 10:39:46 -0800 From: "Kevin Oberman" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Date: Tue, 13 Nov 2001 09:31:27 -0800 (PST) > From: Tom > Sender: owner-freebsd-stable@FreeBSD.ORG > > I think your root.cache file is old, or someone has damaged it by > adding incorrect root servers. This file is included with BIND, or you > can find a copy listing the current root servers someplace on internic.net Easiest way is "dig . ns @a.root-servers.net" You can pipe it into the appropriate zone file as specified in named.conf. dig formats the response so that it is the correct format with non-zonefile lines commented out. Current contents: > dig . ns @a.root-servers.net. ; <<>> DiG 8.3 <<>> . ns @a.root-servers.net. ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr aa rd; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 13 ;; QUERY SECTION: ;; ., type = NS, class = IN ;; ANSWER SECTION: . 6D IN NS L.ROOT-SERVERS.NET. . 6D IN NS M.ROOT-SERVERS.NET. . 6D IN NS I.ROOT-SERVERS.NET. . 6D IN NS E.ROOT-SERVERS.NET. . 6D IN NS D.ROOT-SERVERS.NET. . 6D IN NS A.ROOT-SERVERS.NET. . 6D IN NS H.ROOT-SERVERS.NET. . 6D IN NS C.ROOT-SERVERS.NET. . 6D IN NS G.ROOT-SERVERS.NET. . 6D IN NS F.ROOT-SERVERS.NET. . 6D IN NS B.ROOT-SERVERS.NET. . 6D IN NS J.ROOT-SERVERS.NET. . 6D IN NS K.ROOT-SERVERS.NET. ;; ADDITIONAL SECTION: L.ROOT-SERVERS.NET. 5w6d16h IN A 198.32.64.12 M.ROOT-SERVERS.NET. 5w6d16h IN A 202.12.27.33 I.ROOT-SERVERS.NET. 5w6d16h IN A 192.36.148.17 E.ROOT-SERVERS.NET. 5w6d16h IN A 192.203.230.10 D.ROOT-SERVERS.NET. 5w6d16h IN A 128.8.10.90 A.ROOT-SERVERS.NET. 5w6d16h IN A 198.41.0.4 H.ROOT-SERVERS.NET. 5w6d16h IN A 128.63.2.53 C.ROOT-SERVERS.NET. 5w6d16h IN A 192.33.4.12 G.ROOT-SERVERS.NET. 5w6d16h IN A 192.112.36.4 F.ROOT-SERVERS.NET. 5w6d16h IN A 192.5.5.241 B.ROOT-SERVERS.NET. 5w6d16h IN A 128.9.0.107 J.ROOT-SERVERS.NET. 5w6d16h IN A 198.41.0.10 K.ROOT-SERVERS.NET. 5w6d16h IN A 193.0.14.129 ;; Total query time: 5126 msec ;; FROM: puppeteer.es.net to SERVER: a.root-servers.net. 198.41.0.4 ;; WHEN: Tue Nov 13 10:34:39 2001 ;; MSG SIZE sent: 17 rcvd: 436 R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 12:15:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from midway.uchicago.edu (midway.uchicago.edu [128.135.12.12]) by hub.freebsd.org (Postfix) with ESMTP id 869AF37B417 for ; Tue, 13 Nov 2001 12:15:34 -0800 (PST) Received: from harper.uchicago.edu (daemon@harper.uchicago.edu [128.135.12.7]) by midway.uchicago.edu (8.11.6/8.11.6) with ESMTP id fADKEgn25415; Tue, 13 Nov 2001 14:14:42 -0600 (CST) Received: from localhost (dsyphers@localhost) by harper.uchicago.edu (8.11.6/8.11.6) with ESMTP id fADKEgL16245; Tue, 13 Nov 2001 14:14:42 -0600 (CST) X-Authentication-Warning: harper.uchicago.edu: dsyphers owned process doing -bs Date: Tue, 13 Nov 2001 14:14:42 -0600 (CST) From: David Syphers To: Vincent D Murphy Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 4.4-RELEASE CTM In-Reply-To: <000b01c16c2b$cdedecc0$7b00000a@TUADH.local> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You need to start with the huge XEmpty file. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ctm.html. -David On Tue, 13 Nov 2001, Vincent D Murphy wrote: > i want to start using CTM to track 4.4-STABLE starting from a stock > 4.4-RELEASE install. > > which delta files do i start with? i want to track the ports and all > source, basically everything i need to 'make world'. > > (please CC me in any replies) > > thanks, > -vincent > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 12:20:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from midway.uchicago.edu (midway.uchicago.edu [128.135.12.12]) by hub.freebsd.org (Postfix) with ESMTP id D4B9937B405 for ; Tue, 13 Nov 2001 12:20:31 -0800 (PST) Received: from harper.uchicago.edu (daemon@harper.uchicago.edu [128.135.12.7]) by midway.uchicago.edu (8.11.6/8.11.6) with ESMTP id fADKKVn01353; Tue, 13 Nov 2001 14:20:31 -0600 (CST) Received: from localhost (dsyphers@localhost) by harper.uchicago.edu (8.11.6/8.11.6) with ESMTP id fADKKV422504; Tue, 13 Nov 2001 14:20:31 -0600 (CST) X-Authentication-Warning: harper.uchicago.edu: dsyphers owned process doing -bs Date: Tue, 13 Nov 2001 14:20:31 -0600 (CST) From: David Syphers To: Vincent D Murphy Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 4.4-RELEASE CTM In-Reply-To: <000901c16c34$098a43c0$7b00000a@TUADH.local> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I never had any problems with CTM, and used it for years. It seems like a fine solution to me... -David On Tue, 13 Nov 2001, Vincent D Murphy wrote: > PS do you care to elaborate on the 'headaches' CTM can potentially cause? > that sounds scary. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 12:51:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.quantified.com (ns2.quantified.com [63.212.171.3]) by hub.freebsd.org (Postfix) with ESMTP id 85AF337B405 for ; Tue, 13 Nov 2001 12:51:50 -0800 (PST) Received: from danzig.sd.quantified.net (web.quantified.com [63.212.171.5]) by mail.quantified.com (8.11.3/8.11.3) with ESMTP id fADKph440989 for ; Tue, 13 Nov 2001 12:51:43 -0800 (PST) (envelope-from dsilver@quantified.com) Date: Tue, 13 Nov 2001 12:51:45 -0800 (PST) From: Doug Silver X-Sender: dsilver@danzig.sd.quantified.net To: freebsd-stable@FreeBSD.ORG Subject: Problems upgrading from 4.2 to 4.4S Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Filter-Version: 1.3 (mail.quantified.com) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have two 4.2 boxes, and one box did a buildworld/installworld properly, but my other machine keeps having problems during the buildworld stage, always at the same point: cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/strip -I/usr/src/gnu/usr.bin/binutils/strip/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/strip/../libbinutils -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/binutils -c /usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/binutils/is-strip.c cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/strip -I/usr/src/gnu/usr.bin/binutils/strip/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/strip/../libbinutils -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/binutils -static -o strip objcopy.o is-strip.o ../libbinutils/libbinutils.a ../libbfd/libbfd.a ../libiberty/libiberty.a ../libbinutils/libbinutils.a(bucomm.o): In function `make_tempname': bucomm.o(.text+0x357): warning: mktemp() possibly used unsafely; consider using mkstemp() cp strip maybe_stripped strip maybe_stripped ===> doc ===> libiberty ===> libbfd Segmentation fault - core dumped *** Error code 139 Stop in /usr/src/gnu/usr.bin/binutils. Here's /etc/make.conf: COPTFLAGS= -O -pipe USA_RESIDENT=YES NO_FORTRAN=true NO_LPR=true NOGAMES=true NOUUCP=true MAKE_IDEA=YES NO_MODULES=true I added the 'NO_MODULES' after I saw someone suggest it in the archive. I have the make log if that would help too. I just cvsup'd this morning, deleted /usr/obj, etc, but still can't figure out why it's getting stuck. Any suggestions? Thanks! -Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 12:55:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from 217-126-145-95.uc.nombres.ttd.es (217-126-145-95.uc.nombres.ttd.es [217.126.145.95]) by hub.freebsd.org (Postfix) with ESMTP id 4DCF937B417 for ; Tue, 13 Nov 2001 12:55:24 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by phoenix.ea4els.ampr.org (Postfix) with ESMTP id 617BD3D4E for ; Tue, 13 Nov 2001 21:55:21 +0100 (CET) Date: Tue, 13 Nov 2001 21:55:20 +0100 (CET) From: Simon J Mudd To: Subject: trouble compiling kernel with -stable? Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-2060712476-1718630794-1005684920=:18222" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---2060712476-1718630794-1005684920=:18222 Content-Type: TEXT/PLAIN; charset=US-ASCII I'm having trouble compiling a custom-defined -stable kernel, after having cvsuped today. make buildworld works fine. make buildkernel works fine with GENERIC My custon kernel last built on FreeBSD unicorn.ea4els.ampr.org 4.4-STABLE FreeBSD 4.4-STABLE #0: Wed Oct 24 09 root@unicorn.ea4els.ampr.org:/usr/obj/usr/src/sys/UNICORN i386 and has little changes from GENERIC except for several options which have been commented out. I've encluded it as an attachment with this message. The error I'm seeing when building the UNICORN kernel is the following: cc -nostdinc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpreferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -c linux_sysent.c In file included from linux_sysent.c:14: linux_proto.h:57: syntax error before `linux_time_t' linux_proto.h:57: `linux_time_t' undeclared here (not in a function) linux_proto.h:57: syntax error before `)' linux_proto.h:57: `linux_time_t' undeclared here (not in a function) linux_proto.h:57: syntax error before `)' linux_proto.h:156: syntax error before `linux_handler_t' linux_proto.h:156: `linux_handler_t' undeclared here (not in a function) linux_proto.h:156: `linux_handler_t' undeclared here (not in a function) linux_proto.h:184: syntax error before `linux_dev_t' linux_proto.h:184: `linux_dev_t' undeclared here (not in a function) linux_proto.h:184: `linux_dev_t' undeclared here (not in a function) linux_proto.h:189: syntax error before `linux_osigaction_t' linux_proto.h:189: `linux_osigaction_t' undeclared here (not in a function) linux_proto.h:189: syntax error before `)' linux_proto.h:189: `linux_osigaction_t' undeclared here (not in a function) linux_proto.h:189: syntax error before `)' linux_proto.h:190: syntax error before `linux_osigaction_t' linux_proto.h:190: `linux_osigaction_t' undeclared here (not in a function) linux_proto.h:190: syntax error before `)' linux_proto.h:190: `linux_osigaction_t' undeclared here (not in a function) linux_proto.h:190: syntax error before `)' linux_proto.h:196: syntax error before `linux_osigset_t' linux_proto.h:196: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:196: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:200: syntax error before `linux_osigset_t' linux_proto.h:200: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:200: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:201: syntax error before `linux_osigset_t' linux_proto.h:201: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:201: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:204: syntax error before `linux_osigset_t' linux_proto.h:204: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:204: syntax error before `)' linux_proto.h:204: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:204: syntax error before `)' linux_proto.h:216: syntax error before `linux_gid_t' linux_proto.h:216: `linux_gid_t' undeclared here (not in a function) linux_proto.h:216: syntax error before `)' linux_proto.h:216: `linux_gid_t' undeclared here (not in a function) linux_proto.h:216: syntax error before `)' linux_proto.h:220: syntax error before `linux_gid_t' linux_proto.h:220: `linux_gid_t' undeclared here (not in a function) linux_proto.h:220: syntax error before `)' linux_proto.h:220: `linux_gid_t' undeclared here (not in a function) linux_proto.h:220: syntax error before `)' linux_proto.h:344: syntax error before `linux_osigset_t' linux_proto.h:344: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:344: syntax error before `)' linux_proto.h:344: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:344: syntax error before `)' linux_proto.h:345: syntax error before `linux_osigset_t' linux_proto.h:345: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:345: syntax error before `)' linux_proto.h:345: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:345: syntax error before `)' linux_proto.h:380: syntax error before `linux_uid_t' linux_proto.h:380: `linux_uid_t' undeclared here (not in a function) linux_proto.h:380: `linux_uid_t' undeclared here (not in a function) linux_proto.h:383: syntax error before `linux_gid_t' linux_proto.h:383: `linux_gid_t' undeclared here (not in a function) linux_proto.h:383: `linux_gid_t' undeclared here (not in a function) linux_proto.h:410: syntax error before `linux_pid_t' linux_proto.h:410: `linux_pid_t' undeclared here (not in a function) linux_proto.h:410: `linux_pid_t' undeclared here (not in a function) linux_proto.h:439: syntax error before `linux_uid_t' linux_proto.h:439: `linux_uid_t' undeclared here (not in a function) linux_proto.h:439: syntax error before `)' linux_proto.h:439: `linux_uid_t' undeclared here (not in a function) linux_proto.h:439: syntax error before `)' linux_proto.h:440: syntax error before `linux_uid_t' linux_proto.h:440: `linux_uid_t' undeclared here (not in a function) linux_proto.h:440: syntax error before `)' linux_proto.h:440: `linux_uid_t' undeclared here (not in a function) linux_proto.h:440: syntax error before `)' linux_proto.h:441: syntax error before `linux_uid_t' linux_proto.h:441: `linux_uid_t' undeclared here (not in a function) linux_proto.h:441: syntax error before `)' linux_proto.h:441: `linux_uid_t' undeclared here (not in a function) linux_proto.h:441: syntax error before `)' linux_proto.h:453: syntax error before `linux_gid_t' linux_proto.h:453: `linux_gid_t' undeclared here (not in a function) linux_proto.h:453: syntax error before `)' linux_proto.h:453: `linux_gid_t' undeclared here (not in a function) linux_proto.h:453: syntax error before `)' linux_proto.h:454: syntax error before `linux_gid_t' linux_proto.h:454: `linux_gid_t' undeclared here (not in a function) linux_proto.h:454: syntax error before `)' linux_proto.h:454: `linux_gid_t' undeclared here (not in a function) linux_proto.h:454: syntax error before `)' linux_proto.h:455: syntax error before `linux_gid_t' linux_proto.h:455: `linux_gid_t' undeclared here (not in a function) linux_proto.h:455: syntax error before `)' linux_proto.h:455: `linux_gid_t' undeclared here (not in a function) linux_proto.h:455: syntax error before `)' linux_proto.h:465: syntax error before `linux_sigaction_t' linux_proto.h:465: `linux_sigaction_t' undeclared here (not in a function) linux_proto.h:465: syntax error before `)' linux_proto.h:465: `linux_sigaction_t' undeclared here (not in a function) linux_proto.h:465: syntax error before `)' linux_proto.h:466: syntax error before `linux_sigaction_t' linux_proto.h:466: `linux_sigaction_t' undeclared here (not in a function) linux_proto.h:466: syntax error before `)' linux_proto.h:466: `linux_sigaction_t' undeclared here (not in a function) linux_proto.h:466: syntax error before `)' linux_proto.h:471: syntax error before `linux_sigset_t' linux_proto.h:471: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:471: syntax error before `)' linux_proto.h:471: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:471: syntax error before `)' linux_proto.h:472: syntax error before `linux_sigset_t' linux_proto.h:472: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:472: syntax error before `)' linux_proto.h:472: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:472: syntax error before `)' linux_proto.h:485: syntax error before `linux_sigset_t' linux_proto.h:485: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:485: syntax error before `)' linux_proto.h:485: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:485: syntax error before `)' linux_proto.h:516: syntax error before `*' linux_proto.h:516: syntax error before `linux_stack_t' linux_proto.h:516: syntax error before `linux_stack_t' linux_proto.h:517: syntax error before `linux_stack_t' linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) linux_proto.h:517: syntax error before `)' linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) linux_proto.h:517: syntax error before `)' *** Error code 1 Stop in /usr/src/sys/modules/linux. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/UNICORN. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. unicorn# I've not noticed any messages on freebsd-stable which are related, so any pointers would much be appreciated. Simon -- Simon J Mudd, Tel: +34-91-408 4878, Mobile: +34-605-085 219 Madrid, Spain. email: sjmudd@pobox.com, Postfix RPM Packager ---2060712476-1718630794-1005684920=:18222 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=UNICORN Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=UNICORN Iw0KIyBVTklDT1JOIC0tIGNvbmZpZ3VyYXRpb24gZmlsZSBmb3IgRnJlZUJT RC9pMzg2IGZvciB1bmljb3JuLmVhNGVscy5hbXByLm9yZw0KIw0KIyBGb3Ig bW9yZSBpbmZvcm1hdGlvbiBvbiB0aGlzIGZpbGUsIHBsZWFzZSByZWFkIHRo ZSBoYW5kYm9vayBzZWN0aW9uIG9uDQojIEtlcm5lbCBDb25maWd1cmF0aW9u IEZpbGVzOg0KIw0KIyAgICBodHRwOi8vd3d3LkZyZWVCU0Qub3JnL2hhbmRi b29rL2tlcm5lbGNvbmZpZy1jb25maWcuaHRtbA0KIw0KIyBUaGUgaGFuZGJv b2sgaXMgYWxzbyBhdmFpbGFibGUgbG9jYWxseSBpbiAvdXNyL3NoYXJlL2Rv Yy9oYW5kYm9vaw0KIyBpZiB5b3UndmUgaW5zdGFsbGVkIHRoZSBkb2MgZGlz dHJpYnV0aW9uLCBvdGhlcndpc2UgYWx3YXlzIHNlZSB0aGUNCiMgRnJlZUJT RCBXb3JsZCBXaWRlIFdlYiBzZXJ2ZXIgKGh0dHA6Ly93d3cuRnJlZUJTRC5v cmcvKSBmb3IgdGhlDQojIGxhdGVzdCBpbmZvcm1hdGlvbi4NCiMNCiMgQW4g ZXhoYXVzdGl2ZSBsaXN0IG9mIG9wdGlvbnMgYW5kIG1vcmUgZGV0YWlsZWQg ZXhwbGFuYXRpb25zIG9mIHRoZQ0KIyBkZXZpY2UgbGluZXMgaXMgYWxzbyBw cmVzZW50IGluIHRoZSAuL0xJTlQgY29uZmlndXJhdGlvbiBmaWxlLiBJZiB5 b3UgYXJlDQojIGluIGRvdWJ0IGFzIHRvIHRoZSBwdXJwb3NlIG9yIG5lY2Vz c2l0eSBvZiBhIGxpbmUsIGNoZWNrIGZpcnN0IGluIExJTlQuDQojDQojICRG cmVlQlNEOiBzcmMvc3lzL2kzODYvY29uZi9HRU5FUklDLHYgMS4yNDYuMi4z NCAyMDAxLzA4LzEyIDEzOjEzOjQ2IGpvZXJnIEV4cCAkDQoNCm1hY2hpbmUJ CWkzODYNCiNjcHUJCUkzODZfQ1BVDQojY3B1CQlJNDg2X0NQVQ0KI2NwdQkJ STU4Nl9DUFUNCmNwdQkJSTY4Nl9DUFUNCmlkZW50CQlVTklDT1JODQptYXh1 c2VycwkzMg0KDQojbWFrZW9wdGlvbnMJREVCVUc9LWcJCSNCdWlsZCBrZXJu ZWwgd2l0aCBnZGIoMSkgZGVidWcgc3ltYm9scw0KDQpvcHRpb25zIAlNQVRI X0VNVUxBVEUJCSNTdXBwb3J0IGZvciB4ODcgZW11bGF0aW9uDQpvcHRpb25z IAlJTkVUCQkJI0ludGVyTkVUd29ya2luZw0Kb3B0aW9ucyAJSU5FVDYJCQkj SVB2NiBjb21tdW5pY2F0aW9ucyBwcm90b2NvbHMNCm9wdGlvbnMgCUZGUwkJ CSNCZXJrZWxleSBGYXN0IEZpbGVzeXN0ZW0NCm9wdGlvbnMgCUZGU19ST09U CQkjRkZTIHVzYWJsZSBhcyByb290IGRldmljZSBba2VlcCB0aGlzIV0NCm9w dGlvbnMgCVNPRlRVUERBVEVTCQkjRW5hYmxlIEZGUyBzb2Z0IHVwZGF0ZXMg c3VwcG9ydA0Kb3B0aW9ucyAJTUZTCQkJI01lbW9yeSBGaWxlc3lzdGVtDQpv cHRpb25zIAlNRF9ST09UCQkJI01EIGlzIGEgcG90ZW50aWFsIHJvb3QgZGV2 aWNlDQpvcHRpb25zIAlORlMJCQkjTmV0d29yayBGaWxlc3lzdGVtDQpvcHRp b25zIAlORlNfUk9PVAkJI05GUyB1c2FibGUgYXMgcm9vdCBkZXZpY2UsIE5G UyByZXF1aXJlZA0Kb3B0aW9ucyAJTVNET1NGUwkJCSNNU0RPUyBGaWxlc3lz dGVtDQpvcHRpb25zIAlDRDk2NjAJCQkjSVNPIDk2NjAgRmlsZXN5c3RlbQ0K b3B0aW9ucyAJQ0Q5NjYwX1JPT1QJCSNDRC1ST00gdXNhYmxlIGFzIHJvb3Qs IENEOTY2MCByZXF1aXJlZA0Kb3B0aW9ucyAJUFJPQ0ZTCQkJI1Byb2Nlc3Mg ZmlsZXN5c3RlbQ0Kb3B0aW9ucyAJQ09NUEFUXzQzCQkjQ29tcGF0aWJsZSB3 aXRoIEJTRCA0LjMgW0tFRVAgVEhJUyFdDQpvcHRpb25zIAlTQ1NJX0RFTEFZ PTUwMDAJCSNEZWxheSAoaW4gbXMpIGJlZm9yZSBwcm9iaW5nIFNDU0kNCm9w dGlvbnMgCVVDT05TT0xFCQkjQWxsb3cgdXNlcnMgdG8gZ3JhYiB0aGUgY29u c29sZQ0Kb3B0aW9ucyAJVVNFUkNPTkZJRwkJI2Jvb3QgLWMgZWRpdG9yDQpv cHRpb25zIAlWSVNVQUxfVVNFUkNPTkZJRwkjdmlzdWFsIGJvb3QgLWMgZWRp dG9yDQpvcHRpb25zIAlLVFJBQ0UJCQkja3RyYWNlKDEpIHN1cHBvcnQNCm9w dGlvbnMgCVNZU1ZTSE0JCQkjU1lTVi1zdHlsZSBzaGFyZWQgbWVtb3J5DQpv cHRpb25zIAlTWVNWTVNHCQkJI1NZU1Ytc3R5bGUgbWVzc2FnZSBxdWV1ZXMN Cm9wdGlvbnMgCVNZU1ZTRU0JCQkjU1lTVi1zdHlsZSBzZW1hcGhvcmVzDQpv cHRpb25zIAlQMTAwM18xQgkJI1Bvc2l4IFAxMDAzXzFCIHJlYWwtdGltZSBl eHRlbnNpb25zDQpvcHRpb25zIAlfS1BPU0lYX1BSSU9SSVRZX1NDSEVEVUxJ TkcNCm9wdGlvbnMJCUlDTVBfQkFORExJTQkJI1JhdGUgbGltaXQgYmFkIHJl cGxpZXMNCm9wdGlvbnMgCUtCRF9JTlNUQUxMX0NERVYJIyBpbnN0YWxsIGEg Q0RFViBlbnRyeSBpbiAvZGV2DQoNCiMgVG8gbWFrZSBhbiBTTVAga2VybmVs LCB0aGUgbmV4dCB0d28gYXJlIG5lZWRlZA0Kb3B0aW9ucyAJU01QCQkJIyBT eW1tZXRyaWMgTXVsdGlQcm9jZXNzb3IgS2VybmVsDQpvcHRpb25zIAlBUElD X0lPCQkJIyBTeW1tZXRyaWMgKEFQSUMpIEkvTw0KDQpkZXZpY2UJCWlzYQ0K ZGV2aWNlCQllaXNhDQpkZXZpY2UJCXBjaQ0KDQojIEZsb3BweSBkcml2ZXMN CmRldmljZQkJZmRjMAlhdCBpc2E/IHBvcnQgSU9fRkQxIGlycSA2IGRycSAy DQpkZXZpY2UJCWZkMAlhdCBmZGMwIGRyaXZlIDANCiNkZXZpY2UJCWZkMQlh dCBmZGMwIGRyaXZlIDENCiMNCiMgSWYgeW91IGhhdmUgYSBUb3NoaWJhIExp YnJldHRvIHdpdGggaXRzIFktRSBEYXRhIFBDTUNJQSBmbG9wcHksDQojIGRv bid0IHVzZSB0aGUgYWJvdmUgbGluZSBmb3IgZmRjMCBidXQgdGhlIGZvbGxv d2luZyBvbmU6DQojZGV2aWNlCQlmZGMwDQoNCiMgQVRBIGFuZCBBVEFQSSBk ZXZpY2VzDQojZGV2aWNlCQlhdGEwCWF0IGlzYT8gcG9ydCBJT19XRDEgaXJx IDE0DQojZGV2aWNlCQlhdGExCWF0IGlzYT8gcG9ydCBJT19XRDIgaXJxIDE1 DQojZGV2aWNlCQlhdGENCiNkZXZpY2UJCWF0YWRpc2sJCQkjIEFUQSBkaXNr IGRyaXZlcw0KI2RldmljZQkJYXRhcGljZAkJCSMgQVRBUEkgQ0RST00gZHJp dmVzDQojZGV2aWNlCQlhdGFwaWZkCQkJIyBBVEFQSSBmbG9wcHkgZHJpdmVz DQojZGV2aWNlCQlhdGFwaXN0CQkJIyBBVEFQSSB0YXBlIGRyaXZlcw0KI29w dGlvbnMgCUFUQV9TVEFUSUNfSUQJCSNTdGF0aWMgZGV2aWNlIG51bWJlcmlu Zw0KDQojIFNDU0kgQ29udHJvbGxlcnMNCiNkZXZpY2UJCWFoYgkJIyBFSVNB IEFIQTE3NDIgZmFtaWx5DQpkZXZpY2UJCWFoYwkJIyBBSEEyOTQwIGFuZCBv bmJvYXJkIEFJQzd4eHggZGV2aWNlcw0KI2RldmljZQkJYW1kCQkjIEFNRCA1 M0M5NzQgKFRla3JhbSBEQy0zOTAoVCkpDQojZGV2aWNlCQlpc3AJCSMgUWxv Z2ljIGZhbWlseQ0KI2RldmljZQkJbmNyCQkjIE5DUi9TeW1iaW9zIExvZ2lj DQojZGV2aWNlCQlzeW0JCSMgTkNSL1N5bWJpb3MgTG9naWMgKG5ld2VyIGNo aXBzZXRzKQ0KI29wdGlvbnMJU1lNX1NFVFVQX0xQX1BST0JFX01BUD0weDQw DQoJCQkJIyBBbGxvdyBuY3IgdG8gYXR0YWNoIGxlZ2FjeSBOQ1IgZGV2aWNl cyB3aGVuIA0KCQkJCSMgYm90aCBzeW0gYW5kIG5jciBhcmUgY29uZmlndXJl ZA0KDQojZGV2aWNlCQlhZHYwCWF0IGlzYT8NCiNkZXZpY2UJCWFkdw0KI2Rl dmljZQkJYnQwCWF0IGlzYT8NCiNkZXZpY2UJCWFoYTAJYXQgaXNhPw0KI2Rl dmljZQkJYWljMAlhdCBpc2E/DQoNCiNkZXZpY2UJCW5jdgkJIyBOQ1IgNTND NTAwDQojZGV2aWNlCQluc3AJCSMgV29ya2JpdCBOaW5qYSBTQ1NJLTMNCiNk ZXZpY2UJCXN0ZwkJIyBUTUMgMThDMzAvMThDNTANCg0KIyBTQ1NJIHBlcmlw aGVyYWxzDQpkZXZpY2UJCXNjYnVzCQkjIFNDU0kgYnVzIChyZXF1aXJlZCkN CmRldmljZQkJZGEJCSMgRGlyZWN0IEFjY2VzcyAoZGlza3MpDQpkZXZpY2UJ CXNhCQkjIFNlcXVlbnRpYWwgQWNjZXNzICh0YXBlIGV0YykNCmRldmljZQkJ Y2QJCSMgQ0QNCmRldmljZQkJcGFzcwkJIyBQYXNzdGhyb3VnaCBkZXZpY2Ug KGRpcmVjdCBTQ1NJIGFjY2VzcykNCg0KIyBSQUlEIGNvbnRyb2xsZXJzIGlu dGVyZmFjZWQgdG8gdGhlIFNDU0kgc3Vic3lzdGVtDQojZGV2aWNlCQlhc3IJ CSMgRFBUIFNtYXJ0UkFJRCBWLCBWSSBhbmQgQWRhcHRlYyBTQ1NJIFJBSUQN CiNkZXZpY2UJCWRwdAkJIyBEUFQgU21hcnRjYWNoZSAtIFNlZSBMSU5UIGZv ciBvcHRpb25zIQ0KI2RldmljZQkJbWx5CQkjIE15bGV4IEFjY2VsZVJBSUQv ZVh0cmVtZVJBSUQNCg0KIyBSQUlEIGNvbnRyb2xsZXJzDQojZGV2aWNlCQlh YWMJCSMgQWRhcHRlYyBGU0EgUkFJRCwgRGVsbCBQRVJDMi9QRVJDMw0KI2Rl dmljZQkJaWRhCQkjIENvbXBhcSBTbWFydCBSQUlEDQojZGV2aWNlCQlhbXIJ CSMgQU1JIE1lZ2FSQUlEDQojZGV2aWNlCQltbHgJCSMgTXlsZXggREFDOTYw IGZhbWlseQ0KI2RldmljZQkJdHdlCQkjIDN3YXJlIEVzY2FsYWRlDQoNCiMg YXRrYmRjMCBjb250cm9scyBib3RoIHRoZSBrZXlib2FyZCBhbmQgdGhlIFBT LzIgbW91c2UNCmRldmljZQkJYXRrYmRjMAlhdCBpc2E/IHBvcnQgSU9fS0JE DQpkZXZpY2UJCWF0a2JkMAlhdCBhdGtiZGM/IGlycSAxIGZsYWdzIDB4MQ0K ZGV2aWNlCQlwc20wCWF0IGF0a2JkYz8gaXJxIDEyDQoNCmRldmljZQkJdmdh MAlhdCBpc2E/DQoNCiMgc3BsYXNoIHNjcmVlbi9zY3JlZW4gc2F2ZXINCnBz ZXVkby1kZXZpY2UJc3BsYXNoDQoNCiMgc3lzY29ucyBpcyB0aGUgZGVmYXVs dCBjb25zb2xlIGRyaXZlciwgcmVzZW1ibGluZyBhbiBTQ08gY29uc29sZQ0K ZGV2aWNlCQlzYzAJYXQgaXNhPyBmbGFncyAweDEwMA0KDQojIEVuYWJsZSB0 aGlzIGFuZCBQQ1ZUX0ZSRUVCU0QgZm9yIHBjdnQgdnQyMjAgY29tcGF0aWJs ZSBjb25zb2xlIGRyaXZlcg0KI2RldmljZQkJdnQwCWF0IGlzYT8NCiNvcHRp b25zIAlYU0VSVkVSCQkJIyBzdXBwb3J0IGZvciBYIHNlcnZlciBvbiBhIHZ0 IGNvbnNvbGUNCiNvcHRpb25zIAlGQVRfQ1VSU09SCQkjIHN0YXJ0IHdpdGgg YmxvY2sgY3Vyc29yDQojIElmIHlvdSBoYXZlIGEgVGhpbmtQQUQsIHVuY29t bWVudCB0aGlzIGFsb25nIHdpdGggdGhlIHJlc3Qgb2YgdGhlIFBDVlQgbGlu ZXMNCiNvcHRpb25zIAlQQ1ZUX1NDQU5TRVQ9MgkJIyBJQk0ga2V5Ym9hcmRz IGFyZSBub24tc3RkDQoNCiMgRmxvYXRpbmcgcG9pbnQgc3VwcG9ydCAtIGRv IG5vdCBkaXNhYmxlLg0KZGV2aWNlCQlucHgwCWF0IG5leHVzPyBwb3J0IElP X05QWCBpcnEgMTMNCg0KIyBQb3dlciBtYW5hZ2VtZW50IHN1cHBvcnQgKHNl ZSBMSU5UIGZvciBtb3JlIG9wdGlvbnMpDQojZGV2aWNlCQlhcG0wICAgIGF0 IG5leHVzPyBkaXNhYmxlIGZsYWdzIDB4MjAgIyBBZHZhbmNlZCBQb3dlciBN YW5hZ2VtZW50DQoNCiMgUENDQVJEIChQQ01DSUEpIHN1cHBvcnQNCiNkZXZp Y2UJCWNhcmQNCiNkZXZpY2UJCXBjaWMwCWF0IGlzYT8gaXJxIDAgcG9ydCAw eDNlMCBpb21lbSAweGQwMDAwDQojZGV2aWNlCQlwY2ljMQlhdCBpc2E/IGly cSAwIHBvcnQgMHgzZTIgaW9tZW0gMHhkNDAwMCBkaXNhYmxlDQoNCiMgU2Vy aWFsIChDT00pIHBvcnRzDQpkZXZpY2UJCXNpbzAJYXQgaXNhPyBwb3J0IElP X0NPTTEgZmxhZ3MgMHgxMCBpcnEgNA0KZGV2aWNlCQlzaW8xCWF0IGlzYT8g cG9ydCBJT19DT00yIGlycSAzDQojZGV2aWNlCQlzaW8yCWF0IGlzYT8gZGlz YWJsZSBwb3J0IElPX0NPTTMgaXJxIDUNCiNkZXZpY2UJCXNpbzMJYXQgaXNh PyBkaXNhYmxlIHBvcnQgSU9fQ09NNCBpcnEgOQ0KDQojIFBhcmFsbGVsIHBv cnQNCmRldmljZQkJcHBjMAlhdCBpc2E/IGlycSA3DQpkZXZpY2UJCXBwYnVz CQkjIFBhcmFsbGVsIHBvcnQgYnVzIChyZXF1aXJlZCkNCmRldmljZQkJbHB0 CQkjIFByaW50ZXINCmRldmljZQkJcGxpcAkJIyBUQ1AvSVAgb3ZlciBwYXJh bGxlbA0KZGV2aWNlCQlwcGkJCSMgUGFyYWxsZWwgcG9ydCBpbnRlcmZhY2Ug ZGV2aWNlDQojZGV2aWNlCQl2cG8JCSMgUmVxdWlyZXMgc2NidXMgYW5kIGRh DQoNCg0KIyBQQ0kgRXRoZXJuZXQgTklDcy4NCiNkZXZpY2UJCWRlCQkjIERF Qy9JbnRlbCBEQzIxeDR4IChgYFR1bGlwJycpDQojZGV2aWNlCQl0eHAJCSMg M0NvbSAzY1I5OTAgKGBgVHlwaG9vbicnKQ0KI2RldmljZQkJdngJCSMgM0Nv bSAzYzU5MCwgM2M1OTUgKGBgVm9ydGV4JycpDQoNCiMgUENJIEV0aGVybmV0 IE5JQ3MgdGhhdCB1c2UgdGhlIGNvbW1vbiBNSUkgYnVzIGNvbnRyb2xsZXIg Y29kZS4NCiMgTk9URTogQmUgc3VyZSB0byBrZWVwIHRoZSAnZGV2aWNlIG1p aWJ1cycgbGluZSBpbiBvcmRlciB0byB1c2UgdGhlc2UgTklDcyENCmRldmlj ZQkJbWlpYnVzCQkjIE1JSSBidXMgc3VwcG9ydA0KI2RldmljZQkJZGMJCSMg REVDL0ludGVsIDIxMTQzIGFuZCB2YXJpb3VzIHdvcmthbGlrZXMNCiNkZXZp Y2UJCWZ4cAkJIyBJbnRlbCBFdGhlckV4cHJlc3MgUFJPLzEwMEIgKDgyNTU3 LCA4MjU1OCkNCiNkZXZpY2UJCXBjbgkJIyBBTUQgQW03OUM5N3ggUENJIDEw LzEwMCBOSUNzDQojZGV2aWNlCQlybAkJIyBSZWFsVGVrIDgxMjkvODEzOQ0K I2RldmljZQkJc2YJCSMgQWRhcHRlYyBBSUMtNjkxNSAoYGBTdGFyZmlyZScn KQ0KI2RldmljZQkJc2lzCQkjIFNpbGljb24gSW50ZWdyYXRlZCBTeXN0ZW1z IFNpUyA5MDAvU2lTIDcwMTYNCiNkZXZpY2UJCXN0ZQkJIyBTdW5kYW5jZSBT VDIwMSAoRC1MaW5rIERGRS01NTBUWCkNCiNkZXZpY2UJCXRsCQkjIFRleGFz IEluc3RydW1lbnRzIFRodW5kZXJMQU4NCiNkZXZpY2UJCXR4CQkjIFNNQyBF dGhlclBvd2VyIElJICg4M2MxNzAgYGBFUElDJycpDQojZGV2aWNlCQl2cgkJ IyBWSUEgUmhpbmUsIFJoaW5lIElJDQojZGV2aWNlCQl3YgkJIyBXaW5ib25k IFc4OUM4NDBGDQojZGV2aWNlCQl3eAkJIyBJbnRlbCBHaWdhYml0IEV0aGVy bmV0IENhcmQgKGBgV2lzZW1hbicnKQ0KI2RldmljZQkJeGwJCSMgM0NvbSAz YzkweCAoYGBCb29tZXJhbmcnJywgYGBDeWNsb25lJycpDQoNCiMgSVNBIEV0 aGVybmV0IE5JQ3MuDQojICdkZXZpY2UgZWQnIHJlcXVpcmVzICdkZXZpY2Ug bWlpYnVzJw0KZGV2aWNlCQllZDAJYXQgaXNhPyBwb3J0IDB4MzAwIGlycSA1 IGlvbWVtIDB4ZDgwMDANCiNkZXZpY2UJCWV4DQojZGV2aWNlCQllcA0KI2Rl dmljZQkJZmUwCWF0IGlzYT8gcG9ydCAweDMwMA0KIyBYaXJjb20gRXRoZXJu ZXQNCiNkZXZpY2UJCXhlDQojIFBSSVNNIEkgSUVFRSA4MDIuMTFiIHdpcmVs ZXNzIE5JQy4NCiNkZXZpY2UJCWF3aQ0KIyBXYXZlTEFOL0lFRUUgODAyLjEx IHdpcmVsZXNzIE5JQ3MuIE5vdGU6IHRoZSBXYXZlTEFOL0lFRUUgcmVhbGx5 DQojIGV4aXN0cyBvbmx5IGFzIGEgUENNQ0lBIGRldmljZSwgc28gdGhlcmUg aXMgbm8gSVNBIGF0dGFjaG1lbnQgbmVlZGVkDQojIGFuZCByZXNvdXJjZXMg d2lsbCBhbHdheXMgYmUgZHluYW1pY2FsbHkgYXNzaWduZWQgYnkgdGhlIHBj Y2FyZCBjb2RlLg0KI2RldmljZQkJd2kNCiMgQWlyb25ldCA0NTAwLzQ4MDAg ODAyLjExIHdpcmVsZXNzIE5JQ3MuIE5vdGU6IHRoZSBkZWNsYXJhdGlvbiBi ZWxvdyB3aWxsDQojIHdvcmsgZm9yIFBDTUNJQSBhbmQgUENJIGNhcmRzLCBh cyB3ZWxsIGFzIElTQSBjYXJkcyBzZXQgdG8gSVNBIFBuUA0KIyBtb2RlICh0 aGUgZmFjdG9yeSBkZWZhdWx0KS4gSWYgeW91IHNldCB0aGUgc3dpdGNoZXMg b24geW91ciBJU0ENCiMgY2FyZCBmb3IgYSBtYW51YWxseSBjaG9zZW4gSS9P IGFkZHJlc3MgYW5kIElSUSwgeW91IG11c3Qgc3BlY2lmeQ0KIyB0aG9zZSBw YXJhbWV0ZXJzIGhlcmUuDQojZGV2aWNlCQlhbg0KIyBUaGUgcHJvYmUgb3Jk ZXIgb2YgdGhlc2UgaXMgcHJlc2VudGx5IGRldGVybWluZWQgYnkgaTM4Ni9p c2EvaXNhX2NvbXBhdC5jLg0KI2RldmljZQkJaWUwCWF0IGlzYT8gcG9ydCAw eDMwMCBpcnEgMTAgaW9tZW0gMHhkMDAwMA0KI2RldmljZQkJbGUwCWF0IGlz YT8gcG9ydCAweDMwMCBpcnEgNSBpb21lbSAweGQwMDAwDQojZGV2aWNlCQls bmMwCWF0IGlzYT8gcG9ydCAweDI4MCBpcnEgMTAgZHJxIDANCiNkZXZpY2UJ CWNzMAlhdCBpc2E/IHBvcnQgMHgzMDANCiNkZXZpY2UJCXNuMAlhdCBpc2E/ IHBvcnQgMHgzMDAgaXJxIDEwDQoNCiMgUHNldWRvIGRldmljZXMgLSB0aGUg bnVtYmVyIGluZGljYXRlcyBob3cgbWFueSB1bml0cyB0byBhbGxvY2F0ZS4N CnBzZXVkby1kZXZpY2UJbG9vcAkxCSMgTmV0d29yayBsb29wYmFjaw0KcHNl dWRvLWRldmljZQlldGhlcgkJIyBFdGhlcm5ldCBzdXBwb3J0DQpwc2V1ZG8t ZGV2aWNlCXNsCTEJIyBLZXJuZWwgU0xJUA0KcHNldWRvLWRldmljZQlwcHAJ MQkjIEtlcm5lbCBQUFANCnBzZXVkby1kZXZpY2UJdHVuCTEJIyBQYWNrZXQg dHVubmVsLg0KcHNldWRvLWRldmljZQlwdHkJCSMgUHNldWRvLXR0eXMgKHRl bG5ldCBldGMpDQpwc2V1ZG8tZGV2aWNlCW1kCQkjIE1lbW9yeSAiZGlza3Mi DQpwc2V1ZG8tZGV2aWNlCWdpZgk0CSMgSVB2NiBhbmQgSVB2NCB0dW5uZWxp bmcNCnBzZXVkby1kZXZpY2UJZmFpdGgJMQkjIElQdjYtdG8tSVB2NCByZWxh eWluZyAodHJhbnNsYXRpb24pDQoNCiMgVGhlIGBicGYnIHBzZXVkby1kZXZp Y2UgZW5hYmxlcyB0aGUgQmVya2VsZXkgUGFja2V0IEZpbHRlci4NCiMgQmUg YXdhcmUgb2YgdGhlIGFkbWluaXN0cmF0aXZlIGNvbnNlcXVlbmNlcyBvZiBl bmFibGluZyB0aGlzIQ0KcHNldWRvLWRldmljZQlicGYJCSNCZXJrZWxleSBw YWNrZXQgZmlsdGVyDQoNCiMgVVNCIHN1cHBvcnQNCiNkZXZpY2UJCXVoY2kJ CSMgVUhDSSBQQ0ktPlVTQiBpbnRlcmZhY2UNCiNkZXZpY2UJCW9oY2kJCSMg T0hDSSBQQ0ktPlVTQiBpbnRlcmZhY2UNCiNkZXZpY2UJCXVzYgkJIyBVU0Ig QnVzIChyZXF1aXJlZCkNCiNkZXZpY2UJCXVnZW4JCSMgR2VuZXJpYw0KI2Rl dmljZQkJdWhpZAkJIyAiSHVtYW4gSW50ZXJmYWNlIERldmljZXMiDQojZGV2 aWNlCQl1a2JkCQkjIEtleWJvYXJkDQojZGV2aWNlCQl1bHB0CQkjIFByaW50 ZXINCiNkZXZpY2UJCXVtYXNzCQkjIERpc2tzL01hc3Mgc3RvcmFnZSAtIFJl cXVpcmVzIHNjYnVzIGFuZCBkYQ0KI2RldmljZQkJdW1zCQkjIE1vdXNlDQoj ZGV2aWNlCQl1c2Nhbm5lcgkjIFNjYW5uZXJzDQojIFVTQiBFdGhlcm5ldCwg cmVxdWlyZXMgbWlpDQojZGV2aWNlCQlhdWUJCSMgQURNdGVrIFVTQiBldGhl cm5ldA0KI2RldmljZQkJY3VlCQkjIENBVEMgVVNCIGV0aGVybmV0DQojZGV2 aWNlCQlrdWUJCSMgS2F3YXNha2kgTFNJIFVTQiBldGhlcm5ldA0KDQojIC0t LS0tLS0tLS0gT1RIRVIgU1RVRkYgQURERUQgRlJPTSBMSU5UIC0tLS0tLS0t LS0NCg0Kb3B0aW9ucyAgICAgICAgIFFVT1RBDQpvcHRpb25zICAgICAgICAg RVhUMkZTDQo= ---2060712476-1718630794-1005684920=:18222-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 12:59:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id A127C37B41A for ; Tue, 13 Nov 2001 12:59:18 -0800 (PST) Received: from horsey.gshapiro.net (gshapiro@localhost [IPv6:::1]) by horsey.gshapiro.net (8.12.2.Beta1/8.12.2.Beta1) with ESMTP id fADKxH6d071860 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 13 Nov 2001 12:59:17 -0800 (PST) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.12.2.Beta1/8.12.2.Beta1/Submit) id fADKxH6m071857; Tue, 13 Nov 2001 12:59:17 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15345.35237.56436.754175@horsey.gshapiro.net> Date: Tue, 13 Nov 2001 12:59:17 -0800 From: Gregory Neil Shapiro To: Simon J Mudd Cc: Subject: Re: trouble compiling kernel with -stable? In-Reply-To: References: X-Mailer: VM 6.96 under 21.5 (beta3) "asparagus" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG sjmudd> cc -nostdinc -O -pipe -D_KERNEL -Wall -Wredundant-decls sjmudd> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith sjmudd> -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- sjmudd> -I. -I@ -I@/../include -mpreferred-stack-boundary=2 -Wall sjmudd> -Wredundant-decls -Wnested-externs -Wstrict-prototypes sjmudd> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual sjmudd> -fformat-extensions -ansi -c linux_sysent.c sjmudd> In file included from linux_sysent.c:14: sjmudd> linux_proto.h:57: syntax error before `linux_time_t' ... I had this problem also until I did this: cd /usr/src/sys/modules/linux make cleandir Note that I build modules with world (MODULES_WITH_WORLD=yes) so you have to: rm -rf /usr/obj/usr/src/sys/UNICORN/modules/linux or something close to that. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 15:42:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gilmore.nas.nasa.gov (gilmore.nas.nasa.gov [129.99.32.17]) by hub.freebsd.org (Postfix) with ESMTP id 2C83837B417 for ; Tue, 13 Nov 2001 15:42:35 -0800 (PST) Received: from gilmore.nas.nasa.gov (IDENT:y1ut5t5ZqLobVlpkGRByRdNoN0N+wiCW@localhost.nas.nasa.gov [127.0.0.1]) by gilmore.nas.nasa.gov (8.11.4/8.11.4) with ESMTP id fADNgVd40197 for ; Tue, 13 Nov 2001 15:42:32 -0800 (PST) (envelope-from tweten@gilmore.nas.nasa.gov) Message-Id: <200111132342.fADNgVd40197@gilmore.nas.nasa.gov> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 Reply-To: tweten@nas.nasa.gov To: freebsd-stable@FreeBSD.ORG Subject: Re: -STABLE buildkernel broke! (linux module) From: Dave Tweten Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Nov 2001 15:42:30 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG My automatic Saturday morning script to rebuild from source failed this past Saturday morning while trying to build the kernel, as did many others'. My possible contribution to a fix is to place bounds upon the time when the bug was introduced. I run a completely vanilla sequence of cvs, make world, make kernel (and in parallel), make documentation. It is vanilla, that is, except for my custom kernel config. It worked the morning of November 3rd. It didn't work on the 10th. Except for the actual date, this past weekend's cvsup control file is typical: *default host=cvsup10.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs *default delete use-rel-suffix *default date=2001.11.10.08.00.00 *default tag=. doc-all *default tag=RELENG_4 src-all The automatic build process sets the date each time it is run. I haven't installed kernel or world since July 22, meaning that the tools used for make world and for make kernel were the same before and after the advent of the bug. So, it seems reasonable to me that it must have been introduced into STABLE after 8:00 GMT Saturday, November 3 and before 8:00 GMT Saturday, November 10. Since the first e-mail of the complaint tide (an e-mail from Greg Prosser ) was dated 6:02 GMT Saturday, November 10, my guess is that the bug was introduced late last week. Like everyone else's, my process gets through building world and fails while building kernel in the linux module: In file included from linux_sysent.c:14: linux_proto.h:57: syntax error before `linux_time_t' linux_proto.h:57: `linux_time_t' undeclared here (not in a function) I'd be happy to provide any additional help I can to anyone interested in fixing this problem (and who is empowered actually to fix it). -- M/S 258-5 | 1024-bit PGP fingerprint: | tweten@nas.nasa.gov NASA Ames Research Center | 41 B0 89 0A 8F 94 6C 59 | (650) 604-4416 Moffett Field, CA 94035-1000 | 7C 80 10 20 25 C7 2F E6 | FAX: (650) 604-4377 We each earn what freedom of speech we defend for those who most offend us. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 16:54:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id 950C037B418 for ; Tue, 13 Nov 2001 16:54:17 -0800 (PST) Received: from dialup-209.244.104.77.dial1.sanjose1.level3.net ([209.244.104.77] helo=blossom.cjclark.org) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 163oJk-000065-00; Tue, 13 Nov 2001 16:54:16 -0800 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.3) id fAE0rVl63476; Tue, 13 Nov 2001 16:53:31 -0800 (PST) (envelope-from cjc) Date: Tue, 13 Nov 2001 16:53:31 -0800 From: "Crist J. Clark" To: Dave Tweten Cc: freebsd-stable@FreeBSD.ORG Subject: Re: -STABLE buildkernel broke! (linux module) Message-ID: <20011113165331.G61915@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: <200111132342.fADNgVd40197@gilmore.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200111132342.fADNgVd40197@gilmore.nas.nasa.gov>; from tweten@nas.nasa.gov on Tue, Nov 13, 2001 at 03:42:30PM -0800 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Nov 13, 2001 at 03:42:30PM -0800, Dave Tweten wrote: > My automatic Saturday morning script to rebuild from source failed this past > Saturday morning while trying to build the kernel, as did many others'. My > possible contribution to a fix is to place bounds upon the time when the bug > was introduced. > > I run a completely vanilla sequence of cvs, make world, make kernel (and in > parallel), make documentation. It is vanilla, that is, except for my custom > kernel config. It worked the morning of November 3rd. It didn't work on the > 10th. Except for the actual date, this past weekend's cvsup control file is > typical: > > *default host=cvsup10.FreeBSD.org > *default base=/usr > *default prefix=/usr > *default release=cvs > *default delete use-rel-suffix > *default date=2001.11.10.08.00.00 > *default tag=. > doc-all > *default tag=RELENG_4 > src-all > > The automatic build process sets the date each time it is run. > > I haven't installed kernel or world since July 22, meaning that the tools used > for make world and for make kernel were the same before and after the advent > of the bug. So, it seems reasonable to me that it must have been introduced > into STABLE after 8:00 GMT Saturday, November 3 and before 8:00 GMT Saturday, > November 10. Since the first e-mail of the complaint tide (an e-mail from > Greg Prosser ) was dated 6:02 GMT Saturday, November 10, my > guess is that the bug was introduced late last week. > > Like everyone else's, my process gets through building world and fails while > building kernel in the linux module: > > In file included from linux_sysent.c:14: > linux_proto.h:57: syntax error before `linux_time_t' > linux_proto.h:57: `linux_time_t' undeclared here (not in a function) > > I'd be happy to provide any additional help I can to anyone interested in > fixing this problem (and who is empowered actually to fix it). The problem seems to be stale dependencies. Add, # rm -rf /usr/obj/usr/src/sys/YOURKERNEL Or better yet, # rm -rf /usr/obj/usr To your weekly script. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 17:48:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gilmore.nas.nasa.gov (gilmore.nas.nasa.gov [129.99.32.17]) by hub.freebsd.org (Postfix) with ESMTP id C9B9737B405 for ; Tue, 13 Nov 2001 17:48:28 -0800 (PST) Received: from gilmore.nas.nasa.gov (IDENT:941jFtbfMSufkOmUDDoED47yvyQdoiBZ@localhost.nas.nasa.gov [127.0.0.1]) by gilmore.nas.nasa.gov (8.11.4/8.11.4) with ESMTP id fAE1lsd40911; Tue, 13 Nov 2001 17:47:54 -0800 (PST) (envelope-from tweten@gilmore.nas.nasa.gov) Message-Id: <200111140147.fAE1lsd40911@gilmore.nas.nasa.gov> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: cjclark@alum.mit.edu Cc: freebsd-stable@FreeBSD.ORG Subject: Re: -STABLE buildkernel broke! (linux module) In-Reply-To: Message from "Crist J. Clark" of "Tue, 13 Nov 2001 16:53:31 PST." <20011113165331.G61915@blossom.cjclark.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Nov 2001 17:47:53 -0800 From: Dave Tweten Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG cristjc@earthlink.net said: >The problem seems to be stale dependencies. Add, > # rm -rf /usr/obj/usr/src/sys/YOURKERNEL >Or better yet, > # rm -rf /usr/obj/usr >To your weekly script. Since I mount a separate file system at /usr/obj, it would be an even faster band-aid to unmount that file system, newfs it, and re-mount it each week. In fact, that could be done in parallel with the cvsup step. But, wouldn't it be "better yet" to fix the problem so band-aids aren't necessary? One of my reasons for a weekly re-build is to help the community discover and fix bugs as they are introduced. It seems clear to me that this is a build bug. If my help could be useful, I'd be happy to help anyone who is both empowered to fix this bug and interested in fixing it. -- M/S 258-5 | 1024-bit PGP fingerprint: | tweten@nas.nasa.gov NASA Ames Research Center | 41 B0 89 0A 8F 94 6C 59 | (650) 604-4416 Moffett Field, CA 94035-1000 | 7C 80 10 20 25 C7 2F E6 | FAX: (650) 604-4377 We each earn what freedom of speech we defend for those who most offend us. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 19: 8:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 8031B37B416 for ; Tue, 13 Nov 2001 19:08:08 -0800 (PST) Received: from morpheus.kfu.com (morpheus.kfu.com [3ffe:1200:301b:1:2d0:b7ff:fe3f:bdd0]) by quack.kfu.com (8.11.6/8.11.6) with ESMTP id fAE37vl47439 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Tue, 13 Nov 2001 19:08:03 -0800 (PST) (envelope-from nsayer@medusa.kfu.com) Received: (from nsayer@localhost) by morpheus.kfu.com (8.11.6/8.11.6) id fAE37vb00593 for freebsd-stable@freebsd.org; Tue, 13 Nov 2001 19:07:57 -0800 (PST) (envelope-from nsayer) Message-Id: <200111140307.fAE37vb00593@morpheus.kfu.com> Content-Type: text/plain; charset="iso-8859-15" From: Nick Sayer To: freebsd-stable@freebsd.org Subject: Problems with Znyx multiport Ethernet card Date: Tue, 13 Nov 2001 19:07:57 -0800 X-Mailer: KMail [version 1.3] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just got a ZX346Q and can't get it to work under 4.4-RELEASE. It is 4x Intel 21143 (dc0) chips hiding behind a DEC 21152 PCI-PCI bridge (according to dmesg, anyway). It appears to me as if interrupts are not making it through. I never get a link and I get watchdog timeout errors. Has anyone gotten one of these (or a similar card) to work? I would give a dmesg, but I didn't save it, and had to pull the cards out, as it was a production machine. But I did see dc0-dc3 show up and could ifconfig them anyway I wanted but never saw any indication of a link or that it ever received any interrupts. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 19:18:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id BA7B237B405 for ; Tue, 13 Nov 2001 19:18:23 -0800 (PST) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id UAA15796; Tue, 13 Nov 2001 20:18:12 -0700 (MST) (envelope-from chad) Date: Tue, 13 Nov 2001 20:18:11 -0700 From: "Chad R. Larson" To: Dave Tweten Cc: cjclark@alum.mit.edu, freebsd-stable@FreeBSD.ORG Subject: Re: -STABLE buildkernel broke! (linux module) Message-ID: <20011113201811.A15736@freeway.dcfinc.com> References: <200111140147.fAE1lsd40911@gilmore.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200111140147.fAE1lsd40911@gilmore.nas.nasa.gov>; from tweten@nas.nasa.gov on Tue, Nov 13, 2001 at 05:47:53PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Nov 13, 2001 at 05:47:53PM -0800, Dave Tweten wrote: > cristjc@earthlink.net said: > >The problem seems to be stale dependencies. Add, > > # rm -rf /usr/obj/usr/src/sys/YOURKERNEL > >Or better yet, > > # rm -rf /usr/obj/usr > >To your weekly script. > Since I mount a separate file system at /usr/obj, it would be an even > faster band-aid to unmount that file system, newfs it, and re-mount it > each week. I do that. The seperate filesystem is also mounted async. Between those two tricks I save quite a lot of time on a build. > But, wouldn't it be "better yet" to fix the problem so band-aids > aren't necessary? One of my reasons for a weekly re-build is to help > the community discover and fix bugs as they are introduced. It seems > clear to me that this is a build bug. I also believe all this chicken waving about "rm -rf /usr/obj" should not be necessary if the build makefiles are glued together properly. What happens now is the moby top makefile descends into each subdirectory and does a "make clean". Usually that works, sometimes it doesn't. But if the general suggestion is to believe that some sections of the code are broken in regard to "make clean", and the fix is to rm /usr/obj, then perhaps the "make buildworld" target should just do that. It would be faster than the recursive cleans. Plus, it would be one step closer to the way Linux does stuff. (Sorry, couldn't help myself.) -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 19:57:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from valen.gwi.net (valen.gwi.net [207.5.128.33]) by hub.freebsd.org (Postfix) with ESMTP id 142D137B405 for ; Tue, 13 Nov 2001 19:57:56 -0800 (PST) Received: from ABERRATION (dieselgeek.outofspec.com [207.5.188.11]) by valen.gwi.net (8.11.6/8.11.6) with SMTP id fAE3vtB05470 for ; Tue, 13 Nov 2001 22:57:55 -0500 (EST) Message-ID: <00ba01c16cc0$8a1a8900$fa01a8c0@ABERRATION> Reply-To: "Predius" From: "Predius" To: References: <200111140307.fAE37vb00593@morpheus.kfu.com> Subject: Re: Problems with Znyx multiport Ethernet card Date: Tue, 13 Nov 2001 22:57:54 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've mucked with those under 4.1 and they are a little tricky. I believe if you force the media to either auto sense, or 100FDX they'll work. They like to mess with your head as they don't report the media correctly, once they get link, reguardless of speed or duplex they call it 100FDX. Joshua Coombs ----- Original Message ----- From: "Nick Sayer" To: Sent: Tuesday, November 13, 2001 10:07 PM Subject: Problems with Znyx multiport Ethernet card > I just got a ZX346Q and can't get it to work under 4.4-RELEASE. > > It is 4x Intel 21143 (dc0) chips hiding behind a DEC 21152 PCI-PCI bridge > (according to dmesg, anyway). It appears to me as if interrupts are not > making it through. I never get a link and I get watchdog timeout errors. Has > anyone gotten one of these (or a similar card) to work? > > I would give a dmesg, but I didn't save it, and had to pull the cards out, as > it was a production machine. But I did see dc0-dc3 show up and could ifconfig > them anyway I wanted but never saw any indication of a link or that it ever > received any interrupts. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 20: 5:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gaia.inet.co.th (gaia.inet.co.th [203.150.17.116]) by hub.freebsd.org (Postfix) with ESMTP id 601B237B418 for ; Tue, 13 Nov 2001 20:05:51 -0800 (PST) Received: (from anto@localhost) by gaia.inet.co.th (8.11.6/8.11.5) id fAE45Od16946; Wed, 14 Nov 2001 11:05:24 +0700 (ICT) (envelope-from anto) Message-Id: <200111140405.fAE45Od16946@gaia.inet.co.th> Content-Type: text/plain; charset="iso-8859-1" From: Anto Prijosoesilo To: Gunnar Flygt Subject: Re: png-port-upgrade gave med defunct kde Date: Wed, 14 Nov 2001 11:05:23 +0700 X-Mailer: KMail [version 1.3] Cc: FreeBSD Stable MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Upgraded png from 1.0.12 to 1.2.0 That was a catastrophy for kde! No more > icons at all! Anyone else seen this? Fix? kde is 2.2.1 Recompile qt. I had the same problem and that's the only port I recompiled to get my KDE back. I saved the +REQUIRED_BY file from /var/db/pkg/qt-2.3.1 before doing "make deinstall reinstall" and restored that file back after the reinstall. Cheers, Anto. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 20:10:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 9F76837B416 for ; Tue, 13 Nov 2001 20:10:31 -0800 (PST) Received: from dialup-209.244.104.77.dial1.sanjose1.level3.net ([209.244.104.77] helo=blossom.cjclark.org) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 163rNN-0006jZ-00; Tue, 13 Nov 2001 20:10:27 -0800 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.3) id fAE49Gs63945; Tue, 13 Nov 2001 20:09:16 -0800 (PST) (envelope-from cjc) Date: Tue, 13 Nov 2001 20:09:14 -0800 From: "Crist J. Clark" To: Dave Tweten Cc: freebsd-stable@FreeBSD.ORG Subject: Re: -STABLE buildkernel broke! (linux module) Message-ID: <20011113200914.J61915@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: <200111140147.fAE1lsd40911@gilmore.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200111140147.fAE1lsd40911@gilmore.nas.nasa.gov>; from tweten@nas.nasa.gov on Tue, Nov 13, 2001 at 05:47:53PM -0800 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Nov 13, 2001 at 05:47:53PM -0800, Dave Tweten wrote: > cristjc@earthlink.net said: > >The problem seems to be stale dependencies. Add, > > # rm -rf /usr/obj/usr/src/sys/YOURKERNEL > >Or better yet, > > # rm -rf /usr/obj/usr > >To your weekly script. > > Since I mount a separate file system at /usr/obj, it would be an even faster > band-aid to unmount that file system, newfs it, and re-mount it each week. In > fact, that could be done in parallel with the cvsup step. > > But, wouldn't it be "better yet" to fix the problem so band-aids aren't > necessary? One of my reasons for a weekly re-build is to help the community > discover and fix bugs as they are introduced. It seems clear to me that this > is a build bug. > > If my help could be useful, I'd be happy to help anyone who is both empowered > to fix this bug and interested in fixing it. If you still have your old build tree, figure out what dependencies are not being cleaned out before the new build is being started. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 20:30:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from alchemistry.net (alchemistry.net [66.114.66.158]) by hub.freebsd.org (Postfix) with ESMTP id 89F7C37B41B for ; Tue, 13 Nov 2001 20:30:29 -0800 (PST) Received: from amavis by alchemistry.net with scanned-ok (Exim 3.33 #1) id 163rgy-000IB9-00 for freebsd-stable@FreeBSD.ORG; Tue, 13 Nov 2001 23:30:28 -0500 Received: from [192.168.0.1] (helo=ilya) by alchemistry.net with smtp (TLSv1:RC4-MD5:128) (Exim 3.33 #1) id 163rgx-000IAo-00; Tue, 13 Nov 2001 23:30:27 -0500 Message-ID: <00f101c16cc5$5f979010$0100a8c0@ilya> From: "Ilya" To: , References: <20011112095417.F25208@negwo.eastcore.net> Subject: kernel compile error on latest cvsup of stable Date: Tue, 13 Nov 2001 23:32:30 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Virus-Scanned: by AMaViS snapshot-20010714 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just cvsuped 4.4 stable and kernel build fails with these: cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-pr ototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fforma t-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpre ferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-pr ototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fforma t-extensions -ansi -c linux_sysent.c In file included from linux_sysent.c:14: linux_proto.h:57: syntax error before `linux_time_t' linux_proto.h:57: `linux_time_t' undeclared here (not in a function) linux_proto.h:57: syntax error before `)' linux_proto.h:57: `linux_time_t' undeclared here (not in a function) linux_proto.h:57: syntax error before `)' linux_proto.h:156: syntax error before `linux_handler_t' linux_proto.h:156: `linux_handler_t' undeclared here (not in a function) linux_proto.h:156: `linux_handler_t' undeclared here (not in a function) linux_proto.h:184: syntax error before `linux_dev_t' linux_proto.h:184: `linux_dev_t' undeclared here (not in a function) linux_proto.h:184: `linux_dev_t' undeclared here (not in a function) linux_proto.h:189: syntax error before `linux_osigaction_t' linux_proto.h:189: `linux_osigaction_t' undeclared here (not in a function) linux_proto.h:189: syntax error before `)' linux_proto.h:189: `linux_osigaction_t' undeclared here (not in a function) linux_proto.h:189: syntax error before `)' linux_proto.h:190: syntax error before `linux_osigaction_t' linux_proto.h:190: `linux_osigaction_t' undeclared here (not in a function) linux_proto.h:190: syntax error before `)' linux_proto.h:190: `linux_osigaction_t' undeclared here (not in a function) linux_proto.h:190: syntax error before `)' linux_proto.h:196: syntax error before `linux_osigset_t' linux_proto.h:196: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:196: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:200: syntax error before `linux_osigset_t' linux_proto.h:200: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:200: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:201: syntax error before `linux_osigset_t' linux_proto.h:201: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:201: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:204: syntax error before `linux_osigset_t' linux_proto.h:204: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:204: syntax error before `)' linux_proto.h:204: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:204: syntax error before `)' linux_proto.h:216: syntax error before `linux_gid_t' linux_proto.h:216: `linux_gid_t' undeclared here (not in a function) linux_proto.h:216: syntax error before `)' linux_proto.h:216: `linux_gid_t' undeclared here (not in a function) linux_proto.h:216: syntax error before `)' linux_proto.h:220: syntax error before `linux_gid_t' linux_proto.h:220: `linux_gid_t' undeclared here (not in a function) linux_proto.h:220: syntax error before `)' linux_proto.h:220: `linux_gid_t' undeclared here (not in a function) linux_proto.h:220: syntax error before `)' linux_proto.h:344: syntax error before `linux_osigset_t' linux_proto.h:344: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:344: syntax error before `)' linux_proto.h:344: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:344: syntax error before `)' linux_proto.h:345: syntax error before `linux_osigset_t' linux_proto.h:345: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:345: syntax error before `)' linux_proto.h:345: `linux_osigset_t' undeclared here (not in a function) linux_proto.h:345: syntax error before `)' linux_proto.h:380: syntax error before `linux_uid_t' linux_proto.h:380: `linux_uid_t' undeclared here (not in a function) linux_proto.h:380: `linux_uid_t' undeclared here (not in a function) linux_proto.h:383: syntax error before `linux_gid_t' linux_proto.h:383: `linux_gid_t' undeclared here (not in a function) linux_proto.h:383: `linux_gid_t' undeclared here (not in a function) linux_proto.h:410: syntax error before `linux_pid_t' linux_proto.h:410: `linux_pid_t' undeclared here (not in a function) linux_proto.h:410: `linux_pid_t' undeclared here (not in a function) linux_proto.h:439: syntax error before `linux_uid_t' linux_proto.h:439: `linux_uid_t' undeclared here (not in a function) linux_proto.h:439: syntax error before `)' linux_proto.h:439: `linux_uid_t' undeclared here (not in a function) linux_proto.h:439: syntax error before `)' linux_proto.h:440: syntax error before `linux_uid_t' linux_proto.h:440: `linux_uid_t' undeclared here (not in a function) linux_proto.h:440: syntax error before `)' linux_proto.h:440: `linux_uid_t' undeclared here (not in a function) linux_proto.h:440: syntax error before `)' linux_proto.h:441: syntax error before `linux_uid_t' linux_proto.h:441: `linux_uid_t' undeclared here (not in a function) linux_proto.h:441: syntax error before `)' linux_proto.h:441: `linux_uid_t' undeclared here (not in a function) linux_proto.h:441: syntax error before `)' linux_proto.h:453: syntax error before `linux_gid_t' linux_proto.h:453: `linux_gid_t' undeclared here (not in a function) linux_proto.h:453: syntax error before `)' linux_proto.h:453: `linux_gid_t' undeclared here (not in a function) linux_proto.h:453: syntax error before `)' linux_proto.h:454: syntax error before `linux_gid_t' linux_proto.h:454: `linux_gid_t' undeclared here (not in a function) linux_proto.h:454: syntax error before `)' linux_proto.h:454: `linux_gid_t' undeclared here (not in a function) linux_proto.h:454: syntax error before `)' linux_proto.h:455: syntax error before `linux_gid_t' linux_proto.h:455: `linux_gid_t' undeclared here (not in a function) linux_proto.h:455: syntax error before `)' linux_proto.h:455: `linux_gid_t' undeclared here (not in a function) linux_proto.h:455: syntax error before `)' linux_proto.h:465: syntax error before `linux_sigaction_t' linux_proto.h:465: `linux_sigaction_t' undeclared here (not in a function) linux_proto.h:465: syntax error before `)' linux_proto.h:465: `linux_sigaction_t' undeclared here (not in a function) linux_proto.h:465: syntax error before `)' linux_proto.h:466: syntax error before `linux_sigaction_t' linux_proto.h:466: `linux_sigaction_t' undeclared here (not in a function) linux_proto.h:466: syntax error before `)' linux_proto.h:466: `linux_sigaction_t' undeclared here (not in a function) linux_proto.h:466: syntax error before `)' linux_proto.h:471: syntax error before `linux_sigset_t' linux_proto.h:471: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:471: syntax error before `)' linux_proto.h:471: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:471: syntax error before `)' linux_proto.h:472: syntax error before `linux_sigset_t' linux_proto.h:472: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:472: syntax error before `)' linux_proto.h:472: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:472: syntax error before `)' linux_proto.h:485: syntax error before `linux_sigset_t' linux_proto.h:485: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:485: syntax error before `)' linux_proto.h:485: `linux_sigset_t' undeclared here (not in a function) linux_proto.h:485: syntax error before `)' linux_proto.h:516: syntax error before `*' linux_proto.h:516: syntax error before `linux_stack_t' linux_proto.h:516: syntax error before `linux_stack_t' linux_proto.h:517: syntax error before `linux_stack_t' linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) linux_proto.h:517: syntax error before `)' linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) linux_proto.h:517: syntax error before `)' *** Error code 1 Stop in /usr/src/sys/modules/linux. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/ALCHEMISTRY. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 20:38:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sage-american.com (sage-american.com [216.122.141.44]) by hub.freebsd.org (Postfix) with ESMTP id 0D9DE37B405; Tue, 13 Nov 2001 20:38:11 -0800 (PST) Received: from SAGEONE (ppp-208-191-235-11.dialup.crchtx.swbell.net [208.191.235.11]) by sage-american.com (8.9.3/8.9.3) with SMTP id WAA02545; Tue, 13 Nov 2001 22:38:05 -0600 (CST) Message-Id: <3.0.5.32.20011113223808.00fbf8a8@mail.sage-american.com> X-Sender: jacks@mail.sage-american.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 13 Nov 2001 22:38:08 -0600 To: "Ilya" , , From: jacks@sage-american.com Subject: Re: kernel compile error on latest cvsup of stable In-Reply-To: <00f101c16cc5$5f979010$0100a8c0@ilya> References: <20011112095417.F25208@negwo.eastcore.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ... several messages ago have mentioned the buildkernel has a bug that crept in during the past few days... something to do with stale dependencies... I just had a similar problem (October update worked fine) tonight. This fixed mine #rm -rf /usr/obj/usr Then recompile the kernel... should be fine. At 11:32 PM 11.13.2001 -0500, Ilya wrote: >I just cvsuped 4.4 stable and kernel build fails with these: > >cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-pr >ototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fforma >t-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpre >ferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-pr >ototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fforma >t-extensions -ansi -c linux_sysent.c >In file included from linux_sysent.c:14: >linux_proto.h:57: syntax error before `linux_time_t' >linux_proto.h:57: `linux_time_t' undeclared here (not in a function) >linux_proto.h:57: syntax error before `)' >linux_proto.h:57: `linux_time_t' undeclared here (not in a function) >linux_proto.h:57: syntax error before `)' >linux_proto.h:156: syntax error before `linux_handler_t' >linux_proto.h:156: `linux_handler_t' undeclared here (not in a function) >linux_proto.h:156: `linux_handler_t' undeclared here (not in a function) >linux_proto.h:184: syntax error before `linux_dev_t' >linux_proto.h:184: `linux_dev_t' undeclared here (not in a function) >linux_proto.h:184: `linux_dev_t' undeclared here (not in a function) >linux_proto.h:189: syntax error before `linux_osigaction_t' >linux_proto.h:189: `linux_osigaction_t' undeclared here (not in a function) >linux_proto.h:189: syntax error before `)' >linux_proto.h:189: `linux_osigaction_t' undeclared here (not in a function) >linux_proto.h:189: syntax error before `)' >linux_proto.h:190: syntax error before `linux_osigaction_t' >linux_proto.h:190: `linux_osigaction_t' undeclared here (not in a function) >linux_proto.h:190: syntax error before `)' >linux_proto.h:190: `linux_osigaction_t' undeclared here (not in a function) >linux_proto.h:190: syntax error before `)' >linux_proto.h:196: syntax error before `linux_osigset_t' >linux_proto.h:196: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:196: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:200: syntax error before `linux_osigset_t' >linux_proto.h:200: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:200: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:201: syntax error before `linux_osigset_t' >linux_proto.h:201: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:201: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:204: syntax error before `linux_osigset_t' >linux_proto.h:204: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:204: syntax error before `)' >linux_proto.h:204: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:204: syntax error before `)' >linux_proto.h:216: syntax error before `linux_gid_t' >linux_proto.h:216: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:216: syntax error before `)' >linux_proto.h:216: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:216: syntax error before `)' >linux_proto.h:220: syntax error before `linux_gid_t' >linux_proto.h:220: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:220: syntax error before `)' >linux_proto.h:220: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:220: syntax error before `)' >linux_proto.h:344: syntax error before `linux_osigset_t' >linux_proto.h:344: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:344: syntax error before `)' >linux_proto.h:344: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:344: syntax error before `)' >linux_proto.h:345: syntax error before `linux_osigset_t' >linux_proto.h:345: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:345: syntax error before `)' >linux_proto.h:345: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:345: syntax error before `)' >linux_proto.h:380: syntax error before `linux_uid_t' >linux_proto.h:380: `linux_uid_t' undeclared here (not in a function) >linux_proto.h:380: `linux_uid_t' undeclared here (not in a function) >linux_proto.h:383: syntax error before `linux_gid_t' >linux_proto.h:383: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:383: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:410: syntax error before `linux_pid_t' >linux_proto.h:410: `linux_pid_t' undeclared here (not in a function) >linux_proto.h:410: `linux_pid_t' undeclared here (not in a function) >linux_proto.h:439: syntax error before `linux_uid_t' >linux_proto.h:439: `linux_uid_t' undeclared here (not in a function) >linux_proto.h:439: syntax error before `)' >linux_proto.h:439: `linux_uid_t' undeclared here (not in a function) >linux_proto.h:439: syntax error before `)' >linux_proto.h:440: syntax error before `linux_uid_t' >linux_proto.h:440: `linux_uid_t' undeclared here (not in a function) >linux_proto.h:440: syntax error before `)' >linux_proto.h:440: `linux_uid_t' undeclared here (not in a function) >linux_proto.h:440: syntax error before `)' >linux_proto.h:441: syntax error before `linux_uid_t' >linux_proto.h:441: `linux_uid_t' undeclared here (not in a function) >linux_proto.h:441: syntax error before `)' >linux_proto.h:441: `linux_uid_t' undeclared here (not in a function) >linux_proto.h:441: syntax error before `)' >linux_proto.h:453: syntax error before `linux_gid_t' >linux_proto.h:453: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:453: syntax error before `)' >linux_proto.h:453: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:453: syntax error before `)' >linux_proto.h:454: syntax error before `linux_gid_t' >linux_proto.h:454: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:454: syntax error before `)' >linux_proto.h:454: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:454: syntax error before `)' >linux_proto.h:455: syntax error before `linux_gid_t' >linux_proto.h:455: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:455: syntax error before `)' >linux_proto.h:455: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:455: syntax error before `)' >linux_proto.h:465: syntax error before `linux_sigaction_t' >linux_proto.h:465: `linux_sigaction_t' undeclared here (not in a function) >linux_proto.h:465: syntax error before `)' >linux_proto.h:465: `linux_sigaction_t' undeclared here (not in a function) >linux_proto.h:465: syntax error before `)' >linux_proto.h:466: syntax error before `linux_sigaction_t' >linux_proto.h:466: `linux_sigaction_t' undeclared here (not in a function) >linux_proto.h:466: syntax error before `)' >linux_proto.h:466: `linux_sigaction_t' undeclared here (not in a function) >linux_proto.h:466: syntax error before `)' >linux_proto.h:471: syntax error before `linux_sigset_t' >linux_proto.h:471: `linux_sigset_t' undeclared here (not in a function) >linux_proto.h:471: syntax error before `)' >linux_proto.h:471: `linux_sigset_t' undeclared here (not in a function) >linux_proto.h:471: syntax error before `)' >linux_proto.h:472: syntax error before `linux_sigset_t' >linux_proto.h:472: `linux_sigset_t' undeclared here (not in a function) >linux_proto.h:472: syntax error before `)' >linux_proto.h:472: `linux_sigset_t' undeclared here (not in a function) >linux_proto.h:472: syntax error before `)' >linux_proto.h:485: syntax error before `linux_sigset_t' >linux_proto.h:485: `linux_sigset_t' undeclared here (not in a function) >linux_proto.h:485: syntax error before `)' >linux_proto.h:485: `linux_sigset_t' undeclared here (not in a function) >linux_proto.h:485: syntax error before `)' >linux_proto.h:516: syntax error before `*' >linux_proto.h:516: syntax error before `linux_stack_t' >linux_proto.h:516: syntax error before `linux_stack_t' >linux_proto.h:517: syntax error before `linux_stack_t' >linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) >linux_proto.h:517: syntax error before `)' >linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) >linux_proto.h:517: syntax error before `)' >*** Error code 1 > >Stop in /usr/src/sys/modules/linux. >*** Error code 1 > >Stop in /usr/src/sys/modules. >*** Error code 1 > >Stop in /usr/obj/usr/src/sys/ALCHEMISTRY. >*** Error code 1 > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > > Best regards, Jack L. Stone, Server Admin Sage-American http://www.sage-american.com jacks@sage-american.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 21:25: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail3.tor.primus.ca (mail.tor.primus.ca [216.254.136.21]) by hub.freebsd.org (Postfix) with ESMTP id 02FF637B405; Tue, 13 Nov 2001 21:25:02 -0800 (PST) Received: from dialin-135-111.hamilton.primus.ca ([209.90.135.111]) by mail3.tor.primus.ca with esmtp (Exim 2.11 #1) id 163sZ1-0000eh-06; Wed, 14 Nov 2001 00:26:19 -0500 Date: Wed, 14 Nov 2001 00:24:52 -0500 (EST) From: Jason Hunt X-X-Sender: leth@lethargic.dyndns.org To: Ilya Cc: freebsd-questions@FreeBSD.ORG, Subject: Re: kernel compile error on latest cvsup of stable In-Reply-To: <00f101c16cc5$5f979010$0100a8c0@ilya> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I had this exact same problem, all I did was rm -R /usr/src/sys/compile/laptop (laptop is the name of my kernel) and then recompiled and it worked. On Tue, 13 Nov 2001, Ilya wrote: > I just cvsuped 4.4 stable and kernel build fails with these: > > cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-pr > ototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fforma > t-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpre > ferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-pr > ototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fforma > t-extensions -ansi -c linux_sysent.c > In file included from linux_sysent.c:14: > linux_proto.h:57: syntax error before `linux_time_t' > linux_proto.h:57: `linux_time_t' undeclared here (not in a function) > linux_proto.h:57: syntax error before `)' > linux_proto.h:57: `linux_time_t' undeclared here (not in a function) > ... etc ... etc ... etc ... > linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) > linux_proto.h:517: syntax error before `)' > linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) > linux_proto.h:517: syntax error before `)' > *** Error code 1 > > Stop in /usr/src/sys/modules/linux. > *** Error code 1 > > Stop in /usr/src/sys/modules. > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/ALCHEMISTRY. > *** Error code 1 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 22: 2:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from herbelot.dyndns.org (d211.dhcp212-198-26.noos.fr [212.198.26.211]) by hub.freebsd.org (Postfix) with ESMTP id 84FC837B419 for ; Tue, 13 Nov 2001 22:02:21 -0800 (PST) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id HAA43358; Wed, 14 Nov 2001 07:31:30 +0100 (CET) (envelope-from thierry@herbelot.com) Message-ID: <3BF208CE.C38E1D9D@herbelot.com> Date: Wed, 14 Nov 2001 07:01:50 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: Predius Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Problems with Znyx multiport Ethernet card References: <200111140307.fAE37vb00593@morpheus.kfu.com> <00ba01c16cc0$8a1a8900$fa01a8c0@ABERRATION> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [SNIP] on a previous project, I used the DLINK DFE-570-TX 4-port NIC, with great success (the board just works, and is priced sanely : ie around $250) the NIC spec is very similar to the Znix (same 21143 + 21152 combination) in a word : heartly recommanded -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 22:40:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dart.sr.se (dart.sr.se [134.25.0.132]) by hub.freebsd.org (Postfix) with ESMTP id CB4F837B416 for ; Tue, 13 Nov 2001 22:40:30 -0800 (PST) Received: from honken.sr.se (honken.sr.se [134.25.128.27]) by dart.sr.se (8.11.6/8.11.6) with ESMTP id fAE6ePK47873; Wed, 14 Nov 2001 07:40:25 +0100 (CET) (envelope-from gunnar@pluto.sr.se) Received: from pluto.sr.se (pluto.SR.SE [134.25.193.91]) by honken.sr.se (8.9.3/8.9.3) with ESMTP id HAA03768; Wed, 14 Nov 2001 07:40:24 +0100 (CET) (envelope-from gunnar@pluto.sr.se) Received: (from root@localhost) by pluto.sr.se (8.11.6/8.11.1) id fAE6eOs84547; Wed, 14 Nov 2001 07:40:24 +0100 (CET) (envelope-from gunnar) Received: (from gunnar@localhost) by pluto.sr.se (8.11.6/8.11.1av) id fAE6eMV84539; Wed, 14 Nov 2001 07:40:22 +0100 (CET) (envelope-from gunnar) Date: Wed, 14 Nov 2001 07:40:21 +0100 From: Gunnar Flygt To: Anto Prijosoesilo Cc: FreeBSD Stable Subject: Re: png-port-upgrade gave med defunct kde Message-ID: <20011114074021.A83972@sr.se> Reply-To: Gunnar Flygt Mail-Followup-To: Gunnar Flygt , Anto Prijosoesilo , FreeBSD Stable References: <200111140405.fAE45Od16946@gaia.inet.co.th> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200111140405.fAE45Od16946@gaia.inet.co.th>; from antop64@yahoo.com on Wed, Nov 14, 2001 at 11:05:23AM +0700 X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Nov 14, 2001 at 11:05:23AM +0700, Anto Prijosoesilo wrote: > > > Upgraded png from 1.0.12 to 1.2.0 That was a catastrophy for kde! No more > > icons at all! Anyone else seen this? Fix? kde is 2.2.1 > > Recompile qt. I had the same problem and that's the only port I recompiled to > get my KDE back. After having deinstalled, recompiled the whole stuff I realize that THAT was the proper fix, so I recompiled qt also. Now everything is running again. 3 days (and many compiling hours) later :) > > I saved the +REQUIRED_BY file from /var/db/pkg/qt-2.3.1 before doing "make > deinstall reinstall" and restored that file back after the reinstall. > > Cheers, > > Anto. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- __o regards, Gunnar ---_ \<,_ email: flygt@sr.se ---- (_)/ (_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 22:43:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from no-nonsense.org (kbl-mdb539.zeelandnet.nl [62.238.2.31]) by hub.freebsd.org (Postfix) with ESMTP id 8E27137B405 for ; Tue, 13 Nov 2001 22:43:25 -0800 (PST) Received: from peter (peter.home [10.0.0.2]) by no-nonsense.org (8.11.6/8.11.6) with SMTP id fAE6hNc72040 for ; Wed, 14 Nov 2001 07:43:24 +0100 (CET) (envelope-from peter@no-nonsense.org) Message-ID: <004101c16cd7$b714b2c0$0200000a@peter> From: "Peter C. Verhage" To: Subject: Weird load averages Date: Wed, 14 Nov 2001 07:43:48 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG last pid: 72033; load averages: 1.01, 1.02, 0.94 up 18+11:55:05 07:38:59 38 processes: 1 running, 37 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 1.2% interrupt, 98.8% idle Mem: 107M Active, 76M Inact, 33M Wired, 12M Cache, 35M Buf, 20M Free Swap: 512M Total, 156K Used, 512M Free Check the load averages. They have been like that for over 5 minutes now (I've been looking at it for 5 minutes now, so maybe even longer...). And they don't change! If I look at the CPU states and if I look at the CPU time of every process it's almost 0.00 for each process. So I don't understand why the load averages don't decrease... :/ Peter P.S. Running: FreeBSD 4.4-STABLE #2: Fri Oct 26 20:31:04 CEST 2001 (sources where updated on the same day...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 23: 9: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id B890937B405 for ; Tue, 13 Nov 2001 23:09:03 -0800 (PST) Received: from morpheus.kfu.com (morpheus.kfu.com [3ffe:1200:301b:1:2d0:b7ff:fe3f:bdd0]) by quack.kfu.com (8.11.6/8.11.6) with ESMTP id fAE78ol48565 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Tue, 13 Nov 2001 23:08:58 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com (nospam@localhost [::1]) by morpheus.kfu.com (8.11.6/8.11.6) with ESMTP id fAE78oH00649; Tue, 13 Nov 2001 23:08:50 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Message-ID: <3BF21882.4030207@quack.kfu.com> Date: Tue, 13 Nov 2001 23:08:50 -0800 From: Nick Sayer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.5) Gecko/20011112 X-Accept-Language: en, en-US, en-GB MIME-Version: 1.0 To: Thierry Herbelot , freebsd-stable@freebsd.org Subject: Re: Problems with Znyx multiport Ethernet card References: <200111140307.fAE37vb00593@morpheus.kfu.com> <00ba01c16cc0$8a1a8900$fa01a8c0@ABERRATION> <3BF208CE.C38E1D9D@herbelot.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Nice, but I got this Znyx board for $70 on eBay thanks to the Dot-Com-Flamout syndrome. In any event, I did get it working, but... how shall I put it... The PHY seems.... reluctant... to select the proper media type, especially when it's not 100 mbps (that is, when you plug one of the ports into a 10baseT hub). It sometimes needs to be pursuaded with quite a bit of coaxing. Needless to say, I am not convinced the 21143 miibus handler gizmos are 100% correct. From dmesg (finally): [...] pcib2: at device 10.0 on pci0 pci2: on pcib2 [...] dc0: port 0xd800-0xd87f mem 0xdf000000-0xdf0003ff irq 12 at device 4.0 on pci2 dc0: Ethernet address: 00:c0:95:e1:af:10 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc1: port 0xd400-0xd47f mem 0xde800000-0xde8003ff irq 15 at device 5.0 on pci2 dc1: Ethernet address: 00:c0:95:e1:af:11 miibus1: on dc1 dcphy1: on miibus1 dcphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc2: port 0xd000-0xd07f mem 0xde000000-0xde0003ff irq 11 at device 6.0 on pci2 dc2: Ethernet address: 00:c0:95:e1:af:12 miibus2: on dc2 dcphy2: on miibus2 dcphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc3: port 0xb800-0xb87f mem 0xdd800000-0xdd8003ff irq 10 at device 7.0 on pci2 dc3: Ethernet address: 00:c0:95:e1:af:13 miibus3: on dc3 dcphy3: on miibus3 dcphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Thierry Herbelot wrote: > [SNIP] > > on a previous project, I used the DLINK DFE-570-TX 4-port NIC, with > great success (the board just works, and is priced sanely : ie around > $250) > the NIC spec is very similar to the Znix (same 21143 + 21152 > combination) > > in a word : heartly recommanded > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 23:31:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gsaix2.cc.GaSoU.EDU (gsaix2.cc.GaSoU.edu [141.165.1.57]) by hub.freebsd.org (Postfix) with ESMTP id AF43537B405 for ; Tue, 13 Nov 2001 23:31:52 -0800 (PST) Received: from localhost (gsi22419@localhost) by gsaix2.cc.GaSoU.EDU (8.9.2/8.9.2) with SMTP id CAA62052; Wed, 14 Nov 2001 02:31:29 -0500 Date: Wed, 14 Nov 2001 02:31:27 -0500 (EST) From: Scott Dodson To: Thierry Herbelot Cc: Kris Kennaway , Gunnar Flygt , FreeBSD Stable Subject: Re: png-port-upgrade gave med defunct kde In-Reply-To: <3BF038EA.B5586CD8@herbelot.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG A few days ago I built E using the libpng in the ports tree and E is dependant on an older libpng. I had to build/install the older libpng manually, they seem to coexist however. -- scott On Mon, 12 Nov 2001, Thierry Herbelot wrote: > > > > > > Upgraded png from 1.0.12 to 1.2.0 That was a catastrophy for kde! No more > > > icons at all! Anyone else seen this? Fix? kde is 2.2.1 > > I just killed my 4-Stable machine by portupgrad-ing it : the result was > a total mess (anyway, a full reinstall was needed) > > this was the same libpng problem as Gunnar > > -- > Thierry Herbelot > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 13 23:39: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-80.dsl.lsan03.pacbell.net [63.207.60.80]) by hub.freebsd.org (Postfix) with ESMTP id 8E2F737B405 for ; Tue, 13 Nov 2001 23:39:05 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 37BE666BE2; Tue, 13 Nov 2001 23:39:05 -0800 (PST) Date: Tue, 13 Nov 2001 23:39:05 -0800 From: Kris Kennaway To: Scott Dodson Cc: Thierry Herbelot , Kris Kennaway , Gunnar Flygt , FreeBSD Stable Subject: Re: png-port-upgrade gave med defunct kde Message-ID: <20011113233905.A47834@xor.obsecurity.org> References: <3BF038EA.B5586CD8@herbelot.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Q68bSM7Ycu6FN28Q" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gsi22419@gsaix2.cc.GaSoU.EDU on Wed, Nov 14, 2001 at 02:31:27AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 14, 2001 at 02:31:27AM -0500, Scott Dodson wrote: >=20 > A few days ago I built E using the libpng in the ports tree and E is > dependant on an older libpng. I had to build/install the older libpng > manually, they seem to coexist however. There's only one version of libpng in the ports collection, and all dependent ports have been upgraded to use it. Probably your enlightenment port was out of date. Kris --Q68bSM7Ycu6FN28Q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE78h+YWry0BWjoQKURAqzUAJ485J2eLLoOf+yoCGYX3DFe+dhQNgCaAzNZ sezg4K4PN5fl9096j+HQWv8= =UOmY -----END PGP SIGNATURE----- --Q68bSM7Ycu6FN28Q-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 0:22: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from 217-126-145-95.uc.nombres.ttd.es (217-126-145-95.uc.nombres.ttd.es [217.126.145.95]) by hub.freebsd.org (Postfix) with ESMTP id CCD3B37B405; Wed, 14 Nov 2001 00:22:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by phoenix.ea4els.ampr.org (Postfix) with ESMTP id B0F683D4E; Wed, 14 Nov 2001 09:21:57 +0100 (CET) Date: Wed, 14 Nov 2001 09:21:57 +0100 (CET) From: Simon J Mudd To: Cc: Gregory Neil Shapiro Subject: Re: trouble compiling kernel with -stable? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Many thanks to Gregory Neil Shapiro for pointing out the solution to me, see below: On Tue, 13 Nov 2001, Simon J Mudd wrote: > I'm having trouble compiling a custom-defined -stable kernel, after having > cvsuped today. [snip] > The error I'm seeing when building the UNICORN kernel is the following: > > cc -nostdinc -O -pipe -D_KERNEL -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- > -I. -I@ -I@/../include -mpreferred-stack-boundary=2 -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -ansi -c linux_sysent.c > In file included from linux_sysent.c:14: > linux_proto.h:57: syntax error before `linux_time_t' > linux_proto.h:57: `linux_time_t' undeclared here (not in a function) ... > linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) > linux_proto.h:517: syntax error before `)' > linux_proto.h:517: `linux_stack_t' undeclared here (not in a function) > linux_proto.h:517: syntax error before `)' > *** Error code 1 > > Stop in /usr/src/sys/modules/linux. > *** Error code 1 > > Stop in /usr/src/sys/modules. > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/UNICORN. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > unicorn# cd /usr/src/sys/modules/linux make cleandir rm -rf /usr/obj/usr/src/sys/UNICORN/modules/usr/src/sys/modules/linux Recompiling the kernel after this enabled the compilation to finish without problems. Thanks Simon -- Simon J Mudd, Tel: +34-91-408 4878, Mobile: +34-605-085 219 Madrid, Spain. email: sjmudd@pobox.com, Postfix RPM Packager To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 0:25:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.mirror.kiev.ua (mail.mirror.kiev.ua [212.35.162.98]) by hub.freebsd.org (Postfix) with ESMTP id 716B037B405 for ; Wed, 14 Nov 2001 00:25:27 -0800 (PST) Received: from admin by mail.mirror.kiev.ua (8.11.6/8.11.6) with ESMTP id fAE8Yv174762 for ; Wed, 14 Nov 2001 10:34:58 +0200 (EET) Date: Wed, 14 Nov 2001 10:27:04 +0200 From: Vladislav Kushka X-Mailer: The Bat! (v1.53d) Reply-To: Vladislav Kushka Organization: Mirror Weekly X-Priority: 3 (Normal) Message-ID: <1169182338.20011114102704@mirror.kiev.ua> To: stable@freebsd.org Subject: Re: unknown kernel error message MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Monday, November 12, 2001, 5:14:13 PM: CS> A friend of mine is getting these lately, every time he boots his CS> 4.4-STABLE box (I just cvsupped him and built a new world and kernel last CS> night to see if it would help; didn't): CS> Nov 11 22:36:10 unixpros /kernel: arp: unknown hardware address format CS> (0x0800) After upgrading from 4.3-STABLE to 4.4-STABLE I become to encounter the same problems on my server. It seems to be a specific bug of this update. -- Best regards, Vlad Kushka VK3133-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 0:42:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.mirror.kiev.ua (mail.mirror.kiev.ua [212.35.162.98]) by hub.freebsd.org (Postfix) with ESMTP id A7CEC37B417 for ; Wed, 14 Nov 2001 00:42:00 -0800 (PST) Received: from admin by mail.mirror.kiev.ua (8.11.6/8.11.6) with ESMTP id fAE8od174871; Wed, 14 Nov 2001 10:50:40 +0200 (EET) Date: Wed, 14 Nov 2001 10:42:46 +0200 From: Vladislav Kushka X-Mailer: The Bat! (v1.53d) Reply-To: Vladislav Kushka Organization: Mirror Weekly X-Priority: 3 (Normal) Message-ID: <6870124113.20011114104246@mirror.kiev.ua> To: "Michael Kondrashin" , stable@freebsd.org Subject: Re[2]: unknown kernel error message In-Reply-To: <008501c16ce6$f94bd920$0106a8c0@aplog.dialup.corbina.ru> References: <1169182338.20011114102704@mirror.kiev.ua> <008501c16ce6$f94bd920$0106a8c0@aplog.dialup.corbina.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wednesday, November 14, 2001, 10:33:01 AM: MK> ----- Original Message ----- MK> From: "Vladislav Kushka" MK> To: MK> Sent: Wednesday, November 14, 2001 11:27 AM MK> Subject: Re: unknown kernel error message >> Monday, November 12, 2001, 5:14:13 PM: >> >> CS> A friend of mine is getting these lately, every time he boots his >> CS> 4.4-STABLE box (I just cvsupped him and built a new world and kernel last >> CS> night to see if it would help; didn't): >> >> CS> Nov 11 22:36:10 unixpros /kernel: arp: unknown hardware address format >> CS> (0x0800) >> MK> I have seen this problem mentioned from one that had Linux Mandrake 7.1 box on the network. It was Linux that generated bad arp packets. FreeBSD 4.4 only reports this error. If this is your case MK> that upgrade Linux to the next version. MK> Best regards, MK> Michael Kondrashin But there is one essential distinction: I've never had Mandrake on my boxes, only FreeBSD. May be this is provider, whose Linux is? -- Best regards? Vlad Kushka VK3133-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 2:11:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bilver.wjv.com (spdsl-033.wanlogistics.net [63.209.115.33]) by hub.freebsd.org (Postfix) with ESMTP id 3528537B416; Wed, 14 Nov 2001 02:11:39 -0800 (PST) Received: (from bv@localhost) by bilver.wjv.com (8.11.6/8.11.6) id fAEABX112530; Wed, 14 Nov 2001 05:11:33 -0500 (EST) (envelope-from bv) Date: Wed, 14 Nov 2001 05:11:33 -0500 From: Bill Vermillion To: stable@FreeBSD.ORG Cc: freebsd-stable-digest@FreeBSD.ORG Subject: Re: ATA hard drives Message-ID: <20011114051132.A12369@wjv.com> Reply-To: bv@wjv.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from owner-freebsd-stable-digest@FreeBSD.ORG on Wed, Nov 14, 2001 at 12:22:08AM -0800 Organization: W.J.Vermillion / Orlando - Winter Park Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Date: Tue, 13 Nov 2001 12:52:51 +0100 (CET) > From: Attila Nagy > Subject: Re: ATA Hard Drives > > Hello, > > > What is the largest/fastest ATA drives currently supported by -STABLE? > FreeBSD supports 48 bit addressing (introduced with ATA133 standard), so > the limit is quite theoretical. > BTW, the largest ATA drive I know of is the Maxtor 4G160J8 (160 GBs). > Although this may be the largest it isn't the fastest, because it spins > only with 5400 RPM. Just a comment on rotational speed. You should always check the manfacturers specs as the design of the head can greatly affect the speed of transfer to/from the platters. I have seen 5400 RPM drives move data faster than 7200 RPM drives. You don't see it often but RPM alone is not sole determining factor as much as legend would make you think it is. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 5:20:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from castle.jp.freebsd.org (castle.jp.FreeBSD.org [210.226.20.15]) by hub.freebsd.org (Postfix) with ESMTP id 26DC537B416 for ; Wed, 14 Nov 2001 05:20:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id WAA41301; Wed, 14 Nov 2001 22:19:29 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: stable@FreeBSD.org In-Reply-To: <20011114010323.A3840@grosbein.pp.ru> References: <20011114004907.D864@grosbein.pp.ru> <20011114004907.D864@grosbein.pp.ru> <20011114010323.A3840@grosbein.pp.ru> X-User-Agent: Mew/1.94.2 XEmacs/21.5 (alfalfa) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 7 From: Makoto Matsushita To: eugen@grosbein.pp.ru Subject: Re: src/lib/libc/gen/initgroups.c: warn() breaks CVS protocol Date: Wed, 14 Nov 2001 22:19:25 +0900 Message-Id: <20011114221925C.matusita@jp.FreeBSD.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG eugen> O, I see there is PR/15421 taking about this. Check current@FreeBSD.org also, it's hot topic :-) -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 5:31:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mikea.ath.cx (okc-65-30-192-11.mmcable.com [65.30.192.11]) by hub.freebsd.org (Postfix) with ESMTP id EB51337B405 for ; Wed, 14 Nov 2001 05:31:52 -0800 (PST) Received: (from mikea@localhost) by mikea.ath.cx (8.11.6/8.11.1) id fAEDVqS59974 for stable@FreeBSD.ORG; Wed, 14 Nov 2001 07:31:52 -0600 (CST) (envelope-from mikea) Date: Wed, 14 Nov 2001 07:31:52 -0600 From: mikea To: stable@FreeBSD.ORG Subject: Re: Weird load averages Message-ID: <20011114073152.A59943@mikea.ath.cx> References: <004101c16cd7$b714b2c0$0200000a@peter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <004101c16cd7$b714b2c0$0200000a@peter>; from peter@no-nonsense.org on Wed, Nov 14, 2001 at 07:43:48AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Nov 14, 2001 at 07:43:48AM +0100, Peter C. Verhage wrote: > last pid: 72033; load averages: 1.01, 1.02, 0.94 up 18+11:55:05 > 07:38:59 > 38 processes: 1 running, 37 sleeping > CPU states: 0.0% user, 0.0% nice, 0.0% system, 1.2% interrupt, 98.8% > idle > Mem: 107M Active, 76M Inact, 33M Wired, 12M Cache, 35M Buf, 20M Free > Swap: 512M Total, 156K Used, 512M Free > > Check the load averages. They have been like that for over 5 minutes now > (I've been looking at it for 5 minutes now, so maybe even longer...). And > they don't change! If I look at the CPU states and if I look at the CPU time > of every process it's almost 0.00 for each process. So I don't understand > why the load averages don't decrease... :/ The load average, IIRC, is unrelated to the CPU consumption of the running processes, and instead gives an idea of how many processes have been running over the past minutes. Note that you have 1 running and 37 sleeping processes in your "top" output. That would give you a load average of 1.0 over time. If, in addition, cron-driven processes woke up, or you ran something for a little bit, or some other process(es) woke up for a short time, that would account handily for the first two numbers in the load average vector. I account for the third by postulating that you had zero processes running for a while. -- Mike Andrews mikea@mikea.ath.cx Tired old sysadmin since 1964 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 6:28:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cc415903-b.ebnsk1.nj.home.com (cc415903-b.ebnsk1.nj.home.com [24.180.16.158]) by hub.freebsd.org (Postfix) with SMTP id 6F1EF37B405 for ; Wed, 14 Nov 2001 06:28:26 -0800 (PST) Received: (qmail 89931 invoked from network); 14 Nov 2001 14:31:40 -0000 Received: from athena.faerunhome.com (HELO athena.home.com) (192.168.0.2) by cc415903-b.ebnsk1.nj.home.com with SMTP; 14 Nov 2001 14:31:40 -0000 Message-Id: <5.1.0.14.2.20011114091338.03464ec0@netmail.home.com> X-Sender: damascus@netmail.home.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 14 Nov 2001 09:19:30 -0500 To: bv@wjv.com From: Carroll Kong Subject: Re: ATA hard drives Cc: stable@FreeBSD.ORG, freebsd-stable-digest@FreeBSD.ORG In-Reply-To: <20011114051132.A12369@wjv.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 05:11 AM 11/14/01 -0500, Bill Vermillion wrote: > > Date: Tue, 13 Nov 2001 12:52:51 +0100 (CET) > > From: Attila Nagy > > Subject: Re: ATA Hard Drives > > > > Hello, > > > > > What is the largest/fastest ATA drives currently supported by -STABLE? > > FreeBSD supports 48 bit addressing (introduced with ATA133 standard), so > > the limit is quite theoretical. > > BTW, the largest ATA drive I know of is the Maxtor 4G160J8 (160 GBs). > > Although this may be the largest it isn't the fastest, because it spins > > only with 5400 RPM. > >Just a comment on rotational speed. You should always check the >manfacturers specs as the design of the head can greatly affect the >speed of transfer to/from the platters. I have seen 5400 RPM >drives move data faster than 7200 RPM drives. You don't see it >often but RPM alone is not sole determining factor as much as >legend would make you think it is. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message Hm. I think it is more reasonable to say that density makes a big difference. Grab an old 2.0 gig 7200 rpm micropolis scsi that is not dead yet (those suckers died fast and hard), and plop in say a new 40 gig maxtor 5400 rpm drive, and I am sure the maxtor will be very close in performance. However, take any two modern drives, the one with higher rpms is almost always going to win. Because, at that point, density, seek times should be fairly close. -Carroll Kong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 6:51: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bilver.wjv.com (spdsl-033.wanlogistics.net [63.209.115.33]) by hub.freebsd.org (Postfix) with ESMTP id 2CCFE37B405 for ; Wed, 14 Nov 2001 06:50:56 -0800 (PST) Received: (from bv@localhost) by bilver.wjv.com (8.11.6/8.11.6) id fAEEom214333; Wed, 14 Nov 2001 09:50:48 -0500 (EST) (envelope-from bv) Date: Wed, 14 Nov 2001 09:50:48 -0500 From: Bill Vermillion To: Carroll Kong Cc: stable@FreeBSD.ORG Subject: Re: ATA hard drives Message-ID: <20011114095048.A14300@wjv.com> Reply-To: bv@wjv.com References: <20011114051132.A12369@wjv.com> <5.1.0.14.2.20011114091338.03464ec0@netmail.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.1.0.14.2.20011114091338.03464ec0@netmail.home.com>; from damascus@home.com on Wed, Nov 14, 2001 at 09:19:30AM -0500 Organization: W.J.Vermillion / Orlando - Winter Park Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Nov 14, 2001 at 09:19:30AM -0500, Carroll Kong thus spoke: > At 05:11 AM 11/14/01 -0500, Bill Vermillion wrote: > > > > Date: Tue, 13 Nov 2001 12:52:51 +0100 (CET) > > > From: Attila Nagy > > > Subject: Re: ATA Hard Drives > > > > What is the largest/fastest ATA drives currently supported > > > > by -STABLE? > > > FreeBSD supports 48 bit addressing (introduced with ATA133 > > > standard), so the limit is quite theoretical. BTW, the largest > > > ATA drive I know of is the Maxtor 4G160J8 (160 GBs). Although > > > this may be the largest it isn't the fastest, because it spins > > > only with 5400 RPM. > >Just a comment on rotational speed. You should always check the > >manfacturers specs as the design of the head can greatly affect the > >speed of transfer to/from the platters. I have seen 5400 RPM > >drives move data faster than 7200 RPM drives. You don't see it > >often but RPM alone is not sole determining factor as much as > >legend would make you think it is. > Hm. I think it is more reasonable to say that density makes a big > difference. Grab an old 2.0 gig 7200 rpm micropolis scsi that is > not dead yet (those suckers died fast and hard), and plop in say > a new 40 gig maxtor 5400 rpm drive, and I am sure the maxtor will > be very close in performance. However, take any two modern drives, > the one with higher rpms is almost always going to win. Because, > at that point, density, seek times should be fairly close. Not neccesarily true. About 3-4 years ago I was researching drives and found the IBM 5400RPM SCSI drives were faster than the SEAGATE Baracudda 7200RPM drives. This was because the IBM's were using a new head design. Improved media can also mean that you can write bits just a 'bit' smaller. Typically this means a higher coercivity media so that the data bit is more finely focused. You can't compare old drives to new drives - but these were both current production drives. IBM does this now and then because they are doing a lot of head research and a lot of what we see in the high capacity drive markets today comes from them. They make nice little piles of money licensing things too. Over 50% of all advances in HD technology have come from Big Blue - and we are down to just handful of drive manufacturers in the world today. The best bet it to go the manufacturers site and look at the specs. The things to notice are the speed of data from the head to the buffer - listed as internal transfer rate. If the external rate is the same - eg Wide SE/LVD/Fibrechannel/etc - between the two drives then the one with the higher internal transfer rate will be the better performer. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 7: 7:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id E869337B405 for ; Wed, 14 Nov 2001 07:07:49 -0800 (PST) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id JAA13590; Wed, 14 Nov 2001 09:07:47 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Wed, 14 Nov 2001 09:07:46 -0600 (CST) From: Chris Dillon To: Bill Vermillion Cc: Subject: Re: ATA hard drives In-Reply-To: <20011114051132.A12369@wjv.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 14 Nov 2001, Bill Vermillion wrote: > Just a comment on rotational speed. You should always check the > manfacturers specs as the design of the head can greatly affect > the speed of transfer to/from the platters. I have seen 5400 RPM > drives move data faster than 7200 RPM drives. You don't see it > often but RPM alone is not sole determining factor as much as > legend would make you think it is. Data rates aren't the only factor. It is true that higher RPM doesn't necessarily mean higher data rates since you can have a lower-RPM drive with a high areal density resulting in a higher transfer rate compared to a higher-RPM drive with lower areal density. However, the higher RPM drive does have a lower rotational latency, so it takes less time for the section of the platter with the data on it that you want to come under the head, which lowers the overall latency of the drive. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet - Available for IA32 (Intel x86) and Alpha architectures - IA64, PowerPC, UltraSPARC, and ARM architectures under development - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 7:23:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 1096837B417 for ; Wed, 14 Nov 2001 07:23:15 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 14 Nov 2001 15:23:14 +0000 (GMT) To: "Peter C. Verhage" Cc: stable@freebsd.org Subject: Re: Weird load averages In-Reply-To: Your message of "Wed, 14 Nov 2001 07:43:48 +0100." <004101c16cd7$b714b2c0$0200000a@peter> Date: Wed, 14 Nov 2001 15:23:14 +0000 From: Ian Dowse Message-ID: <200111141523.aa20567@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <004101c16cd7$b714b2c0$0200000a@peter>, "Peter C. Verhage" writes: >last pid: 72033; load averages: 1.01, 1.02, 0.94 up 18+11:55:05 > >Check the load averages. They have been like that for over 5 minutes now >(I've been looking at it for 5 minutes now, so maybe even longer...). And >they don't change! If I look at the CPU states and if I look at the CPU time >of every process it's almost 0.00 for each process. So I don't understand >why the load averages don't decrease... :/ Sometimes such "phantom" loads can occur when a system process such as the bufdaemon becomes synchronised with the timing of the samples that determine the system load average. In -current, some random variation has been added to the sample timing to avoid this problem; I must merge that change into -stable soon. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 7:30:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 4559D37B418; Wed, 14 Nov 2001 07:30:33 -0800 (PST) Received: from lanczos.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 14 Nov 2001 15:30:32 +0000 (GMT) Date: Wed, 14 Nov 2001 15:30:31 +0000 From: David Malone To: Eugene Grosbein Cc: stable@freebsd.org, hackers@freebsd.org Subject: Re: kern.vm.kmem.size Message-ID: <20011114153031.A16886@lanczos.maths.tcd.ie> References: <20011111230817.A2325@grosbein.pp.ru> <20011113151329.A44837@walton.maths.tcd.ie> <20011113224730.A864@grosbein.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011113224730.A864@grosbein.pp.ru>; from eugen@grosbein.pp.ru on Tue, Nov 13, 2001 at 10:47:30PM +0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Nov 13, 2001 at 10:47:30PM +0700, Eugene Grosbein wrote: > > you have enough physical memory. (By default there is about 1GB of > > kernel address space, so you are unlikely to be running into this > > limit - I don't think changing kern.vm.kmem.size will help you). > > Are you shure? From LINT: You're right - it is much smaller (I was thinking of something else). However it is bigger than 12MB on most systems - I think it will turn out to be 1/3 physical memory or 200MB, whichever is less. > It seems DIRHASH is limited with free space in the kernel malloc area. > It even cannot utilize default 2M of vfs.ufs.dirhash_maxmem when I do not > increase kern.vm.kmem.size. > > So, how can I estimate needed value of kern.vm.kmem.size? How much ram do you have in the machine? On a 4.4-RC1 machine with 128MB of ram we don't have any problems getting dirhash to use almost all of it's 2MB: vfs.ufs.dirhash_maxmem: 2097152 vfs.ufs.dirhash_mem: 2085797 This is with the devault value for kern.vm.kmem.size. Maybe you could print the value your system is getting with: echo print vm_kmem_size | gdb -k /kernel /dev/mem David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 8:13:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail3.enter.net (mail3.enter.net [63.65.0.23]) by hub.freebsd.org (Postfix) with ESMTP id D62FA37B405 for ; Wed, 14 Nov 2001 08:13:13 -0800 (PST) Received: from grabes2.enter.net (grabes2.enter.net [63.65.2.36]) by mail3.enter.net (8.11.6/8.11.2) with ESMTP id fAEGDCU09168 for ; Wed, 14 Nov 2001 11:13:13 -0500 (EST) Date: Wed, 14 Nov 2001 11:07:20 -0500 (EST) From: Gavin Grabias To: Subject: cucipop Message-ID: <20011114110512.Y24850-100000@grabes2.enter.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Has anyone gotten cucipop to work with DB support? I have compiled it from an up to date ports tree and the DB support looks to be compiled in. However, it never creates the state.db which it uses to record bulletins and the session state. Any help would be appreciated. Regards, Gavin Grabias - System Administration ******************************************************************** ENTER.NET - "The Road to the Internet Starts Here!" (tm) (610) 437-2221 * http://www.enter.net/ * email:support@enter.net ******************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 8:19:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from barbera.system.pl (barbera.system.pl [195.205.185.21]) by hub.freebsd.org (Postfix) with ESMTP id A110637B417 for ; Wed, 14 Nov 2001 08:19:33 -0800 (PST) Received: (from saper@localhost) by barbera.system.pl (SYSTEM Internet) id fAEGJVJ91323 for freebsd-stable@FreeBSD.ORG; Wed, 14 Nov 2001 17:19:31 +0100 (CET) Date: Wed, 14 Nov 2001 17:19:31 +0100 From: Marcin Cieslak To: freebsd-stable@FreeBSD.ORG Subject: Re: Intel 82801AA (ICH) - unable to map IO port space on PCI? (solved) Message-ID: <20011114171931.A91096@barbera.system.pl> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <20011113190339.A57871@barbera.system.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011113190339.A57871@barbera.system.pl>; from saper@system.pl on Tue, Nov 13, 2001 at 07:03:39PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, it's enough to turn off PnP OS in the BIOS - and everything works fine. Sorry for distrubance, long time no play with PC hardware:) -- << Marcin Cieslak // saper@system.pl >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 9:58: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hercules.icarz.com (ns1.icarz.com [207.99.22.7]) by hub.freebsd.org (Postfix) with ESMTP id DBB4C37B41A for ; Wed, 14 Nov 2001 09:57:59 -0800 (PST) Received: from newken (dhcp113.icarz.com [207.99.22.113]) by hercules.icarz.com (8.10.1/8.10.1) with SMTP id fAEHCCf24605 for ; Wed, 14 Nov 2001 12:12:13 -0500 (EST) Message-ID: <021001c16d2f$7f512780$711663cf@icarz.com> From: "Ken Menzel" To: Subject: vmstat reports incorrect CPU usage Date: Wed, 14 Nov 2001 12:12:10 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am having a problem with vmstat reporting what appear to be incorrect CPU usage values on all my servers. I only use vmstat in scripts so I did not notice until recently. I see an Open PR ( http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/30360 ) but I am not sure this is the same problem as I see a problem on both single and multiple CPU's. Before I go chasing a ghost, does any one else see a difference between CPU usage reported by 'top' and that reported by 'vmstat'. If so is it possible that this is not a bug but a difference in expected behavior of vmstat? Or is it possible vmstat is broke? 'top' appears to report usage figures I would expect. Thanks for any help. Ken ----------------------------------------------------- Ken Menzel ICQ# 9325188 www.icarz.com kenm@icarz.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 10:17: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from goalkeeper.d2.com (goalkeeper.d2.com [198.211.88.26]) by hub.freebsd.org (Postfix) with SMTP id D966537B416 for ; Wed, 14 Nov 2001 10:16:52 -0800 (PST) Received: from d2.com by goalkeeper.d2.com via UUCP (950413.SGI.8.6.12/(930416.SGI)1.0-D2.COM-OUTERELAY) for freebsd-stable@FreeBSD.ORG id KAA22304; Wed, 14 Nov 2001 10:16:49 -0800 Received: from d2.com by omaha.d2.com via ESMTP (940816.SGI.8.6.9/(921111.SGI)1.1-D2.COM-RELAY) for id KAA26766; Wed, 14 Nov 2001 10:16:36 -0800 Message-ID: <3BF2B4B1.2DA9A2F1@d2.com> Date: Wed, 14 Nov 2001 10:15:13 -0800 From: "Victor E. Vaile, IV" X-Mailer: Mozilla 4.75 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: kernel hang with pcm Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I've got an intel D815EEA2 motherboard (intel 815E chipset) and I've installed 4.4-RELEASE, and since then cvsupped to stable. Whenever I build a kernel with pcm (the only change from GENERIC), the kernel hangs most of the time just before the ata devices. It's never booted twice in a row with that kernel, and generic works fine. Also, I find that the few times that it has booted, mpg123 plays mp3 files too fast. I've found a couple different references from people with similar problems, but no solutions so far. Does anyone know of a fix for either of these? Thanks. -Victor Following is dmesg output while booting the GENERIC kernel: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.4-STABLE #0: Tue Nov 13 17:13:25 GMT 2001 Rvev@vev.sigbus.com:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (996.77-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383f9ff real memory = 536608768 (524032K bytes) avail memory = 517881856 (505744K bytes) Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 12 entries at 0xc00f2ea0 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci2: on pcib1 pci2: at 0.0 irq 11 pcib2: at device 30.0 on pci0 pci1: on pcib2 fxp0: port 0xdf00-0xdf3f mem 0xfc9ef000-0xfc9effff irq 11 at device 8.0 on pci1 fxp0: Ethernet address 00:03:47:a7:0d:2f inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci1: (vendor=0x14f1, dev=0x1033) at 13.0 irq 11 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xef40-0xef5f irq 11 at device 31.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: (vendor=0x8086, dev=0x2443) at 31.3 irq 9 uhci1: port 0xef80-0xef9f irq 10 at device 31.4 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: (vendor=0x8086, dev=0x2445) at 31.5 irq 9 orm0:
please put me on your mailing=20 list
------=_NextPart_000_0005_01C04E6C.4D1E74D0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 19:51:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-168.zoominternet.net [24.154.28.168]) by hub.freebsd.org (Postfix) with ESMTP id 6762437B417 for ; Wed, 14 Nov 2001 19:51:35 -0800 (PST) Received: from topperwein.dyndns.org (topperwein.dyndns.org [192.168.168.10]) by topperwein.dyndns.org (8.11.6/8.11.6) with ESMTP id fAF3paF57901 for ; Wed, 14 Nov 2001 22:51:36 -0500 (EST) (envelope-from behanna@zbzoom.net) Date: Wed, 14 Nov 2001 22:51:31 -0500 (EST) From: Chris BeHanna Reply-To: Chris BeHanna To: FreeBSD-Stable Subject: Re: Weird load averages In-Reply-To: <20011114073152.A59943@mikea.ath.cx> Message-ID: <20011114224822.G57801-100000@topperwein.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 14 Nov 2001, mikea wrote: > On Wed, Nov 14, 2001 at 07:43:48AM +0100, Peter C. Verhage wrote: > > last pid: 72033; load averages: 1.01, 1.02, 0.94 up 18+11:55:05 > > 07:38:59 > > 38 processes: 1 running, 37 sleeping > > CPU states: 0.0% user, 0.0% nice, 0.0% system, 1.2% interrupt, 98.8% > > idle > > Mem: 107M Active, 76M Inact, 33M Wired, 12M Cache, 35M Buf, 20M Free > > Swap: 512M Total, 156K Used, 512M Free > > > > Check the load averages. They have been like that for over 5 minutes now > > (I've been looking at it for 5 minutes now, so maybe even longer...). And > > they don't change! If I look at the CPU states and if I look at the CPU time > > of every process it's almost 0.00 for each process. So I don't understand > > why the load averages don't decrease... :/ > > The load average, IIRC, is unrelated to the CPU consumption of > the running processes, and instead gives an idea of how many > processes have been running over the past minutes. Actually, it says how many processes are in the run queue, on average, over the past minutes. If there's some process out there that's in a tight loop that contains a short sleep, or that performs some blocking operation over and over, that returns in fairly short order, that would account for the load average. -- Chris BeHanna Software Engineer (Remove "bogus" before responding.) behanna@bogus.zbzoom.net I was raised by a pack of wild corn dogs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 21:25:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from atos.sr.se (atos.sr.se [192.121.194.132]) by hub.freebsd.org (Postfix) with ESMTP id D31C437B418 for ; Wed, 14 Nov 2001 21:25:02 -0800 (PST) Received: from honken.sr.se (honken.sr.se [134.25.128.27]) by atos.sr.se (8.11.6/8.11.6) with ESMTP id fAF5OmM30590; Thu, 15 Nov 2001 06:24:52 +0100 (CET) (envelope-from gunnar@pluto.sr.se) Received: from pluto.sr.se (pluto.SR.SE [134.25.193.91]) by honken.sr.se (8.9.3/8.9.3) with ESMTP id GAA16470; Thu, 15 Nov 2001 06:24:45 +0100 (CET) (envelope-from gunnar@pluto.sr.se) Received: (from root@localhost) by pluto.sr.se (8.11.6/8.11.1) id fAF5Oji12764; Thu, 15 Nov 2001 06:24:45 +0100 (CET) (envelope-from gunnar) Received: (from gunnar@localhost) by pluto.sr.se (8.11.6/8.11.1av) id fAF5Ohn12756; Thu, 15 Nov 2001 06:24:43 +0100 (CET) (envelope-from gunnar) Date: Thu, 15 Nov 2001 06:24:42 +0100 From: Gunnar Flygt To: "Arthur W. Neilson III" Cc: FreeBSD Stable Subject: Re: DELL 2550 boxen Message-ID: <20011115062442.A12444@sr.se> Reply-To: Gunnar Flygt Mail-Followup-To: Gunnar Flygt , "Arthur W. Neilson III" , FreeBSD Stable References: <200111140948340450.386219BA@smtp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200111140948340450.386219BA@smtp>; from art@pilikia.net on Wed, Nov 14, 2001 at 09:48:34AM -1000 X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Nov 14, 2001 at 09:48:34AM -1000, Arthur W. Neilson III wrote: > We are looking at purchasing some DELL 2550 2U rackmount servers, > anyone using these puppies in a production environment with FreeBSD > 4.4 STABLE? Searched thru the mailing list archives and saw that some > folks had a bit of trouble with 4.3 recognising the PERC controller. > I'd appreciate any info anyone can provide.... W'ere using the 2540 which is very similar as far as I know. It wotks like a charm with the PERC. Run 4.4. on them, but it was 4.3 earlier. It was 4.2-RELEASE that didn't find the PERC controller. The fix came somewhere in April if I remember right. > -- > __ > / ) _/_ It is a capital mistake to theorise before one has data. > /--/ __ / Insensibly one begins to twist facts to suit theories, > / (_/ (_<__ Instead of theories to suit facts. > -- Sherlock Holmes, "A Scandal in Bohemia" > Arthur W. Neilson III, WH7N - FISTS #7448 > Bank of Hawaii Network Services > http://www.pilikia.net > art@pilikia.net, aneilson@boh.com, wh7n@arrl.net > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- __o regards, Gunnar ---_ \<,_ email: flygt@sr.se ---- (_)/ (_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 22:51:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns2.alphaque.com (ns2.alphaque.com [202.185.254.11]) by hub.freebsd.org (Postfix) with SMTP id 9501037B405 for ; Wed, 14 Nov 2001 22:51:17 -0800 (PST) Received: (qmail 25168 invoked from network); 15 Nov 2001 06:51:15 -0000 Received: from ns2.alphaque.com (HELO prophet.alphaque.com) (202.185.254.11) by ns2.alphaque.com with SMTP; 15 Nov 2001 06:51:15 -0000 Received: from localhost (1cei4gtthdiseijc@localhost [127.0.0.1]) by prophet.alphaque.com (8.11.6/8.11.6) with ESMTP id fAF6oZD01437 for ; Thu, 15 Nov 2001 14:50:35 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Thu, 15 Nov 2001 14:50:35 +0800 (MYT) From: Dinesh Nair To: freebsd-stable@freebsd.org Subject: ipfw fails between 10/17 and 11/6 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG here's an odd situation. cvsupped on october 17th, built and installed world, mergemastered, and everything runs fine. no problems here. since october 17, i've been cvsupping to RELENG_4, but not building world or even the kernel. the last cvsup is on november 6. today, i decide to build a new kernel, so mosey on into /usr/src/sys/i386/conf, config and build a new kernel. didnt forget to do a make depend either. installed the new kernel. upon rebooting with the new kernel, ipfw stops working. dmesg shows these lines: [start dmesg] IPFW: MOD_LOAD IP packet filtering initialized, divert disabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default [end dmesg] which is odd, since i had IPFIREWALL compiled in the kernel, and was _not_ loading ipfw.ko thru /boot/loader.conf. /sbin/ipfw commands after that fail the execute and dump core. removing IPFIREWALL and related options from the kernel doesnt help either. i never got the "IPFW: MOD_LOAD" line during the previous (oct 17) kernel. reverting back to the october 17 kernel brings all things back to normal. i know this sounds like a classic case of mismatch between userland and kernel, but they sources are just two weeks old, and both are RELENG_4 anyways. reading /usr/src/UPDATING says 20011102: ipfw/bridge/dummynet features merged from current. freebsd-stable archives brings up luigi's message that /sbin/ipfw and ipfw.ko need to be rebuilt. however, when i cd into /usr/src/sbin/ipfw and type make, i get the following error: cc -O -pipe -Wall -c /usr/src/sbin/ipfw/ipfw.c /usr/src/sbin/ipfw/ipfw.c:177: `DYN_SRC_ADDR' undeclared here (not in a function) /usr/src/sbin/ipfw/ipfw.c:177: initializer element is not constant /usr/src/sbin/ipfw/ipfw.c:177: (near initialization for `limit_masks[0].x') /usr/src/sbin/ipfw/ipfw.c:178: `DYN_SRC_PORT' undeclared here (not in a function) /usr/src/sbin/ipfw/ipfw.c:178: initializer element is not constant /usr/src/sbin/ipfw/ipfw.c:178: (near initialization for `limit_masks[1].x') /usr/src/sbin/ipfw/ipfw.c:179: `DYN_DST_ADDR' undeclared here (not in a function) /usr/src/sbin/ipfw/ipfw.c:179: initializer element is not constant /usr/src/sbin/ipfw/ipfw.c:179: (near initialization for `limit_masks[2].x') /usr/src/sbin/ipfw/ipfw.c:180: `DYN_DST_PORT' undeclared here (not in a function) /usr/src/sbin/ipfw/ipfw.c:180: initializer element is not constant /usr/src/sbin/ipfw/ipfw.c:180: (near initialization for `limit_masks[3].x') /usr/src/sbin/ipfw/ipfw.c: In function `show_ipfw': /usr/src/sbin/ipfw/ipfw.c:219: structure has no member named `dont_match_prob' /usr/src/sbin/ipfw/ipfw.c:390: structure has no member named `dyn_type' /usr/src/sbin/ipfw/ipfw.c:394: `DYN_KEEP_STATE' undeclared (first use in this function) /usr/src/sbin/ipfw/ipfw.c:394: (Each undeclared identifier is reported only once /usr/src/sbin/ipfw/ipfw.c:394: for each function it appears in.) /usr/src/sbin/ipfw/ipfw.c:397: `DYN_LIMIT' undeclared (first use in this function) /usr/src/sbin/ipfw/ipfw.c:400: structure has no member named `limit_mask' /usr/src/sbin/ipfw/ipfw.c:402: structure has no member named `conn_limit' /usr/src/sbin/ipfw/ipfw.c:392: warning: unreachable code at beginning of switch statement /usr/src/sbin/ipfw/ipfw.c: In function `list': /usr/src/sbin/ipfw/ipfw.c:826: structure has no member named `rule' /usr/src/sbin/ipfw/ipfw.c:830: structure has no member named `dyn_type' /usr/src/sbin/ipfw/ipfw.c:831: `DYN_LIMIT_PARENT' undeclared (first use in this function) /usr/src/sbin/ipfw/ipfw.c:832: structure has no member named `count' /usr/src/sbin/ipfw/ipfw.c:834: `DYN_LIMIT' undeclared (first use in this function) /usr/src/sbin/ipfw/ipfw.c:837: `DYN_KEEP_STATE' undeclared (first use in this function) /usr/src/sbin/ipfw/ipfw.c:832: warning: unreachable code at beginning of switch statement /usr/src/sbin/ipfw/ipfw.c: In function `add': /usr/src/sbin/ipfw/ipfw.c:1656: structure has no member named `dont_match_prob' /usr/src/sbin/ipfw/ipfw.c:1920: structure has no member named `dyn_type' /usr/src/sbin/ipfw/ipfw.c:1920: `DYN_LIMIT' undeclared (first use in this function) /usr/src/sbin/ipfw/ipfw.c:1921: structure has no member named `limit_mask' /usr/src/sbin/ipfw/ipfw.c:1927: structure has no member named `limit_mask' /usr/src/sbin/ipfw/ipfw.c:1937: structure has no member named `conn_limit' /usr/src/sbin/ipfw/ipfw.c:1938: structure has no member named `conn_limit' /usr/src/sbin/ipfw/ipfw.c:1940: structure has no member named `limit_mask' /usr/src/sbin/ipfw/ipfw.c:1949: structure has no member named `dyn_type' *** Error code 1 Stop in /usr/src/sbin/ipfw. any clues as to how i could resolve this issue ? problem seems to be halting me from building any new kernel until this is handled well. Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 23: 9:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by hub.freebsd.org (Postfix) with ESMTP id 14D1237B405 for ; Wed, 14 Nov 2001 23:09:18 -0800 (PST) Received: from isc.org (localhost.dv.isc.org [127.0.0.1]) by drugs.dv.isc.org (8.11.3/8.11.2) with ESMTP id fAF76fp56239; Thu, 15 Nov 2001 18:06:43 +1100 (EST) (envelope-from marka@isc.org) Message-Id: <200111150706.fAF76fp56239@drugs.dv.isc.org> To: Dinesh Nair Cc: freebsd-stable@freebsd.org From: Mark.Andrews@isc.org Subject: Re: ipfw fails between 10/17 and 11/6 In-reply-to: Your message of "Thu, 15 Nov 2001 14:50:35 +0800." Date: Thu, 15 Nov 2001 18:06:41 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Think about the command you are invoking and where the header files are being read from. cc -O -pipe -Wall -c /usr/src/sbin/ipfw/ipfw.c vs cc -O -pipe -g -Wall -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sbin/ipfw/ipfw.c when you buildworld. Mark -- Mark Andrews, Internet Software Consortium 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@isc.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 23:11:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.tor.primus.ca (mail.tor.primus.ca [216.254.136.21]) by hub.freebsd.org (Postfix) with ESMTP id 6B10637B405 for ; Wed, 14 Nov 2001 23:11:43 -0800 (PST) Received: from dialin-135-111.hamilton.primus.ca ([209.90.135.111]) by mail2.tor.primus.ca with esmtp (Exim 2.11 #1) id 164Gif-0005rQ-04; Thu, 15 Nov 2001 02:13:54 -0500 Date: Thu, 15 Nov 2001 02:11:43 -0500 (EST) From: Jason Hunt X-X-Sender: leth@lethargic.dyndns.org To: freebsd-stable@FreeBSD.ORG Cc: Dinesh Nair Subject: Re: ipfw fails between 10/17 and 11/6 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'd say that it is definately a userland and kernel mismatch. You COULD try recompiling the ipfw stuff. I'm sure lots could have changed even in two to three weeks, especially with the UPDATING stating that it was merged from -current.. I don't see why you would cvsup w/o the intention of rebuilding the world. :) Just my two cents. On Thu, 15 Nov 2001, Dinesh Nair wrote: > > here's an odd situation. > > cvsupped on october 17th, built and installed world, mergemastered, and > everything runs fine. no problems here. > > since october 17, i've been cvsupping to RELENG_4, but not building world > or even the kernel. > > the last cvsup is on november 6. > > today, i decide to build a new kernel, so mosey on into > /usr/src/sys/i386/conf, config and build a new kernel. didnt forget to do > a make depend either. installed the new kernel. > > upon rebooting with the new kernel, ipfw stops working. dmesg shows these > lines: > > [start dmesg] > IPFW: MOD_LOAD > IP packet filtering initialized, divert disabled, rule-based forwarding > enabled, default to deny, logging limited to 100 packets/entry by default > [end dmesg] > > which is odd, since i had IPFIREWALL compiled in the kernel, and was _not_ > loading ipfw.ko thru /boot/loader.conf. /sbin/ipfw commands after that > fail the execute and dump core. removing IPFIREWALL and related options > from the kernel doesnt help either. i never got the "IPFW: MOD_LOAD" line > during the previous (oct 17) kernel. > > reverting back to the october 17 kernel brings all things back to normal. > > i know this sounds like a classic case of mismatch between userland and > kernel, but they sources are just two weeks old, and both are RELENG_4 > anyways. > > reading /usr/src/UPDATING says > > 20011102: > ipfw/bridge/dummynet features merged from current. > > freebsd-stable archives brings up luigi's message that /sbin/ipfw and > ipfw.ko need to be rebuilt. however, when i cd into /usr/src/sbin/ipfw and > type make, i get the following error: > > cc -O -pipe -Wall -c /usr/src/sbin/ipfw/ipfw.c > /usr/src/sbin/ipfw/ipfw.c:177: `DYN_SRC_ADDR' undeclared here (not in a function) > /usr/src/sbin/ipfw/ipfw.c:177: initializer element is not constant > /usr/src/sbin/ipfw/ipfw.c:177: (near initialization for `limit_masks[0].x') > /usr/src/sbin/ipfw/ipfw.c:178: `DYN_SRC_PORT' undeclared here (not in a function) > /usr/src/sbin/ipfw/ipfw.c:178: initializer element is not constant > /usr/src/sbin/ipfw/ipfw.c:178: (near initialization for `limit_masks[1].x') > /usr/src/sbin/ipfw/ipfw.c:179: `DYN_DST_ADDR' undeclared here (not in a function) > /usr/src/sbin/ipfw/ipfw.c:179: initializer element is not constant > /usr/src/sbin/ipfw/ipfw.c:179: (near initialization for `limit_masks[2].x') > /usr/src/sbin/ipfw/ipfw.c:180: `DYN_DST_PORT' undeclared here (not in a function) > /usr/src/sbin/ipfw/ipfw.c:180: initializer element is not constant > /usr/src/sbin/ipfw/ipfw.c:180: (near initialization for `limit_masks[3].x') > /usr/src/sbin/ipfw/ipfw.c: In function `show_ipfw': > /usr/src/sbin/ipfw/ipfw.c:219: structure has no member named `dont_match_prob' > /usr/src/sbin/ipfw/ipfw.c:390: structure has no member named `dyn_type' > /usr/src/sbin/ipfw/ipfw.c:394: `DYN_KEEP_STATE' undeclared (first use in this function) > /usr/src/sbin/ipfw/ipfw.c:394: (Each undeclared identifier is reported only once > /usr/src/sbin/ipfw/ipfw.c:394: for each function it appears in.) > /usr/src/sbin/ipfw/ipfw.c:397: `DYN_LIMIT' undeclared (first use in this function) > /usr/src/sbin/ipfw/ipfw.c:400: structure has no member named `limit_mask' > /usr/src/sbin/ipfw/ipfw.c:402: structure has no member named `conn_limit' > /usr/src/sbin/ipfw/ipfw.c:392: warning: unreachable code at beginning of switch statement > /usr/src/sbin/ipfw/ipfw.c: In function `list': > /usr/src/sbin/ipfw/ipfw.c:826: structure has no member named `rule' > /usr/src/sbin/ipfw/ipfw.c:830: structure has no member named `dyn_type' > /usr/src/sbin/ipfw/ipfw.c:831: `DYN_LIMIT_PARENT' undeclared (first use in this function) > /usr/src/sbin/ipfw/ipfw.c:832: structure has no member named `count' > /usr/src/sbin/ipfw/ipfw.c:834: `DYN_LIMIT' undeclared (first use in this function) > /usr/src/sbin/ipfw/ipfw.c:837: `DYN_KEEP_STATE' undeclared (first use in this function) > /usr/src/sbin/ipfw/ipfw.c:832: warning: unreachable code at beginning of switch statement > /usr/src/sbin/ipfw/ipfw.c: In function `add': > /usr/src/sbin/ipfw/ipfw.c:1656: structure has no member named `dont_match_prob' > /usr/src/sbin/ipfw/ipfw.c:1920: structure has no member named `dyn_type' > /usr/src/sbin/ipfw/ipfw.c:1920: `DYN_LIMIT' undeclared (first use in this function) > /usr/src/sbin/ipfw/ipfw.c:1921: structure has no member named `limit_mask' > /usr/src/sbin/ipfw/ipfw.c:1927: structure has no member named `limit_mask' > /usr/src/sbin/ipfw/ipfw.c:1937: structure has no member named `conn_limit' > /usr/src/sbin/ipfw/ipfw.c:1938: structure has no member named `conn_limit' > /usr/src/sbin/ipfw/ipfw.c:1940: structure has no member named `limit_mask' > /usr/src/sbin/ipfw/ipfw.c:1949: structure has no member named `dyn_type' > *** Error code 1 > > Stop in /usr/src/sbin/ipfw. > > any clues as to how i could resolve this issue ? problem seems to be > halting me from building any new kernel until this is handled well. > > Regards, /\_/\ "All dogs go to heaven." > dinesh@alphaque.com (0 0) http://www.alphaque.com/ > +==========================----oOO--(_)--OOo----==========================+ > | for a in past present future; do | > | for b in clients employers associates relatives neighbours pets; do | > | echo "The opinions here in no way reflect the opinions of my $a $b." | > | done; done | > +=========================================================================+ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 23:55:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns2.alphaque.com (ns2.alphaque.com [202.185.254.11]) by hub.freebsd.org (Postfix) with SMTP id 0317E37B41B for ; Wed, 14 Nov 2001 23:55:27 -0800 (PST) Received: (qmail 25684 invoked from network); 15 Nov 2001 07:55:17 -0000 Received: from ns2.alphaque.com (HELO prophet.alphaque.com) (202.185.254.11) by ns2.alphaque.com with SMTP; 15 Nov 2001 07:55:17 -0000 Received: from localhost (okcu049p9d2b478b@localhost [127.0.0.1]) by prophet.alphaque.com (8.11.6/8.11.6) with ESMTP id fAF7ZND01581; Thu, 15 Nov 2001 15:35:23 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Thu, 15 Nov 2001 15:35:23 +0800 (MYT) From: Dinesh Nair To: Jason Hunt Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ipfw fails between 10/17 and 11/6 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 15 Nov 2001, Jason Hunt wrote: > merged from -current.. I don't see why you would cvsup w/o the intention > of rebuilding the world. :) Just my two cents. trying to keep each cvsup bandwidth down to a minimum. we're on a low quality link here. Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 23:57: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fepZ.post.tele.dk (fepz.post.tele.dk [195.41.46.133]) by hub.freebsd.org (Postfix) with ESMTP id AC32E37B41C for ; Wed, 14 Nov 2001 23:56:35 -0800 (PST) Received: from there ([62.243.16.143]) by fepZ.post.tele.dk (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20011115075632.KOYX395.fepZ.post.tele.dk@there> for ; Thu, 15 Nov 2001 08:56:32 +0100 Content-Type: text/plain; charset="iso-8859-1" From: Henrik Johansen To: freebsd-stable@freebsd.org Subject: Re: ipfw fails between 10/17 and 11/6 Date: Thu, 15 Nov 2001 08:58:24 +0100 X-Mailer: KMail [version 1.3] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <20011115075632.KOYX395.fepZ.post.tele.dk@there> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, samme problem here after last nights cvsup & rebuild ... /Henrik Johansen On Thursday 15 November 2001 07:50, you wrote: > here's an odd situation. > > cvsupped on october 17th, built and installed world, mergemastered, and > everything runs fine. no problems here. > > since october 17, i've been cvsupping to RELENG_4, but not building wor= ld > or even the kernel. > > the last cvsup is on november 6. > > today, i decide to build a new kernel, so mosey on into > /usr/src/sys/i386/conf, config and build a new kernel. didnt forget to = do > a make depend either. installed the new kernel. > > upon rebooting with the new kernel, ipfw stops working. dmesg shows the= se > lines: > > [start dmesg] > IPFW: MOD_LOAD > IP packet filtering initialized, divert disabled, rule-based forwarding > enabled, default to deny, logging limited to 100 packets/entry by defau= lt > [end dmesg] > > which is odd, since i had IPFIREWALL compiled in the kernel, and was _n= ot_ > loading ipfw.ko thru /boot/loader.conf. /sbin/ipfw commands after that > fail the execute and dump core. removing IPFIREWALL and related options > from the kernel doesnt help either. i never got the "IPFW: MOD_LOAD" li= ne > during the previous (oct 17) kernel. > > reverting back to the october 17 kernel brings all things back to norma= l. > > i know this sounds like a classic case of mismatch between userland and > kernel, but they sources are just two weeks old, and both are RELENG_4 > anyways. > > reading /usr/src/UPDATING says > > 20011102: > ipfw/bridge/dummynet features merged from current. > > freebsd-stable archives brings up luigi's message that /sbin/ipfw and > ipfw.ko need to be rebuilt. however, when i cd into /usr/src/sbin/ipfw = and > type make, i get the following error: > > cc -O -pipe -Wall -c /usr/src/sbin/ipfw/ipfw.c > /usr/src/sbin/ipfw/ipfw.c:177: `DYN_SRC_ADDR' undeclared here (not in a > function) /usr/src/sbin/ipfw/ipfw.c:177: initializer element is not > constant /usr/src/sbin/ipfw/ipfw.c:177: (near initialization for > `limit_masks[0].x') /usr/src/sbin/ipfw/ipfw.c:178: `DYN_SRC_PORT' > undeclared here (not in a function) /usr/src/sbin/ipfw/ipfw.c:178: > initializer element is not constant /usr/src/sbin/ipfw/ipfw.c:178: (nea= r > initialization for `limit_masks[1].x') /usr/src/sbin/ipfw/ipfw.c:179: > `DYN_DST_ADDR' undeclared here (not in a function) > /usr/src/sbin/ipfw/ipfw.c:179: initializer element is not constant > /usr/src/sbin/ipfw/ipfw.c:179: (near initialization for `limit_masks[2]= =2Ex') > /usr/src/sbin/ipfw/ipfw.c:180: `DYN_DST_PORT' undeclared here (not in a > function) /usr/src/sbin/ipfw/ipfw.c:180: initializer element is not > constant /usr/src/sbin/ipfw/ipfw.c:180: (near initialization for > `limit_masks[3].x') /usr/src/sbin/ipfw/ipfw.c: In function `show_ipfw': > /usr/src/sbin/ipfw/ipfw.c:219: structure has no member named > `dont_match_prob' /usr/src/sbin/ipfw/ipfw.c:390: structure has no membe= r > named `dyn_type' /usr/src/sbin/ipfw/ipfw.c:394: `DYN_KEEP_STATE' undecl= ared > (first use in this function) /usr/src/sbin/ipfw/ipfw.c:394: (Each > undeclared identifier is reported only once /usr/src/sbin/ipfw/ipfw.c:3= 94: > for each function it appears in.) > /usr/src/sbin/ipfw/ipfw.c:397: `DYN_LIMIT' undeclared (first use in thi= s > function) /usr/src/sbin/ipfw/ipfw.c:400: structure has no member named > `limit_mask' /usr/src/sbin/ipfw/ipfw.c:402: structure has no member nam= ed > `conn_limit' /usr/src/sbin/ipfw/ipfw.c:392: warning: unreachable code a= t > beginning of switch statement /usr/src/sbin/ipfw/ipfw.c: In function > `list': > /usr/src/sbin/ipfw/ipfw.c:826: structure has no member named `rule' > /usr/src/sbin/ipfw/ipfw.c:830: structure has no member named `dyn_type' > /usr/src/sbin/ipfw/ipfw.c:831: `DYN_LIMIT_PARENT' undeclared (first use= in > this function) /usr/src/sbin/ipfw/ipfw.c:832: structure has no member n= amed > `count' /usr/src/sbin/ipfw/ipfw.c:834: `DYN_LIMIT' undeclared (first us= e in > this function) /usr/src/sbin/ipfw/ipfw.c:837: `DYN_KEEP_STATE' undeclar= ed > (first use in this function) /usr/src/sbin/ipfw/ipfw.c:832: warning: > unreachable code at beginning of switch statement > /usr/src/sbin/ipfw/ipfw.c: In function `add': > /usr/src/sbin/ipfw/ipfw.c:1656: structure has no member named > `dont_match_prob' /usr/src/sbin/ipfw/ipfw.c:1920: structure has no memb= er > named `dyn_type' /usr/src/sbin/ipfw/ipfw.c:1920: `DYN_LIMIT' undeclared > (first use in this function) /usr/src/sbin/ipfw/ipfw.c:1921: structure = has > no member named `limit_mask' /usr/src/sbin/ipfw/ipfw.c:1927: structure = has > no member named `limit_mask' /usr/src/sbin/ipfw/ipfw.c:1937: structure = has > no member named `conn_limit' /usr/src/sbin/ipfw/ipfw.c:1938: structure = has > no member named `conn_limit' /usr/src/sbin/ipfw/ipfw.c:1940: structure = has > no member named `limit_mask' /usr/src/sbin/ipfw/ipfw.c:1949: structure = has > no member named `dyn_type' *** Error code 1 > > Stop in /usr/src/sbin/ipfw. > > any clues as to how i could resolve this issue ? problem seems to be > halting me from building any new kernel until this is handled well. > > Regards, /\_/\ "All dogs go to heaven." > dinesh@alphaque.com (0 0) http://www.alphaque.com/ > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D----oOO--(_)--OOo----=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ > > | for a in past present future; do = | > | for b in clients employers associates relatives neighbours pets; do= | > | echo "The opinions here in no way reflect the opinions of my $a $b.= " | > | done; done = | > > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 14 23:58: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-80.dsl.lsan03.pacbell.net [63.207.60.80]) by hub.freebsd.org (Postfix) with ESMTP id 3A2BF37B405 for ; Wed, 14 Nov 2001 23:58:01 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 353C866D03; Wed, 14 Nov 2001 23:57:56 -0800 (PST) Date: Wed, 14 Nov 2001 23:57:56 -0800 From: Kris Kennaway To: Dinesh Nair Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ipfw fails between 10/17 and 11/6 Message-ID: <20011114235755.A60439@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="3V7upXqbjpZ4EhLz" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dinesh@alphaque.com on Thu, Nov 15, 2001 at 02:50:35PM +0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 15, 2001 at 02:50:35PM +0800, Dinesh Nair wrote: >=20 > here's an odd situation. >=20 > cvsupped on october 17th, built and installed world, mergemastered, and > everything runs fine. no problems here. >=20 > since october 17, i've been cvsupping to RELENG_4, but not building world > or even the kernel. Stop right there; the only supported way to rebuild your source tree is to make buildworld. In this instance, there were header changes which the new ipfw code relies on; since your system has the old headers installed it breaks when you try and compile ipfw by hand. If you were to do a buildworld it will pick up the correct version of the headers, and all will be well. > i know this sounds like a classic case of mismatch between userland and > kernel No, that would produce a runtime failure, not a compile failure. > but they sources are just two weeks old, and both are RELENG_4 > anyways. Not relevant; when headers change, they change, and you have to recompile code against the new version, not the old (i.e. by doing a buildworld). Kris --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE783WDWry0BWjoQKURAhhVAKCyc4MejBosH+l48RbTeiYTueApPwCeIxL3 l9y2pu1D9X9RG5qR/FgHKcE= =GFK1 -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Nov 15 0: 8:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns2.alphaque.com (ns2.alphaque.com [202.185.254.11]) by hub.freebsd.org (Postfix) with SMTP id 19FE937B417 for ; Thu, 15 Nov 2001 00:08:28 -0800 (PST) Received: (qmail 25836 invoked from network); 15 Nov 2001 08:08:26 -0000 Received: from ns2.alphaque.com (HELO prophet.alphaque.com) (202.185.254.11) by ns2.alphaque.com with SMTP; 15 Nov 2001 08:08:26 -0000 Received: from localhost (q3345odvei3ktavw@localhost [127.0.0.1]) by prophet.alphaque.com (8.11.6/8.11.6) with ESMTP id fAF866D01791; Thu, 15 Nov 2001 16:06:06 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Thu, 15 Nov 2001 16:06:05 +0800 (MYT) From: Dinesh Nair To: Mark.Andrews@isc.org Cc: freebsd-stable@freebsd.org Subject: Re: ipfw fails between 10/17 and 11/6 In-Reply-To: <200111150706.fAF76fp56239@drugs.dv.isc.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 15 Nov 2001 Mark.Andrews@isc.org wrote: > cc -O -pipe -g -Wall -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sbin/ipfw/ipfw.c no difference, mark. something tells me i need to perhaps rebuild/reinstall the header files into /usr/obj, since that hasnt changed after oct 17 either. am i heading in the right direction ? Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Nov 15 0:14:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns2.alphaque.com (ns2.alphaque.com [202.185.254.11]) by hub.freebsd.org (Postfix) with SMTP id 167AC37B416 for ; Thu, 15 Nov 2001 00:14:24 -0800 (PST) Received: (qmail 25896 invoked from network); 15 Nov 2001 08:14:21 -0000 Received: from ns2.alphaque.com (HELO prophet.alphaque.com) (202.185.254.11) by ns2.alphaque.com with SMTP; 15 Nov 2001 08:14:21 -0000 Received: from localhost (gkdwycgw3kntkget@localhost [127.0.0.1]) by prophet.alphaque.com (8.11.6/8.11.6) with ESMTP id fAF8DVD01835; Thu, 15 Nov 2001 16:13:31 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Thu, 15 Nov 2001 16:13:31 +0800 (MYT) From: Dinesh Nair To: Kris Kennaway Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ipfw fails between 10/17 and 11/6 In-Reply-To: <20011114235755.A60439@xor.obsecurity.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 14 Nov 2001, Kris Kennaway wrote: > Stop right there; the only supported way to rebuild your source tree > is to make buildworld. In this instance, there were header changes ok, so the only fix is a buildworld/installworld combo. was hoping to avoid that, but i guess if it needs to be done, it's gotta be done. > > i know this sounds like a classic case of mismatch between userland and > > kernel > > No, that would produce a runtime failure, not a compile failure. it was a runtime failure which sparked off this whole thing, new kernal and older ipfw binary coredumping. > Not relevant; when headers change, they change, and you have to > recompile code against the new version, not the old (i.e. by doing a i understand that, but was sort of moaning that the headers have changed midstream within a point release, instead of being committed against the next point release. it's a minor bitch. but thanks for the pointers anyways all, i'm off to go build world. Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Nov 15 0:32: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-80.dsl.lsan03.pacbell.net [63.207.60.80]) by hub.freebsd.org (Postfix) with ESMTP id B50D637B405 for ; Thu, 15 Nov 2001 00:32:00 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id F15B966D03; Thu, 15 Nov 2001 00:31:57 -0800 (PST) Date: Thu, 15 Nov 2001 00:31:57 -0800 From: Kris Kennaway To: Dinesh Nair Cc: Kris Kennaway , freebsd-stable@FreeBSD.ORG Subject: Re: ipfw fails between 10/17 and 11/6 Message-ID: <20011115003157.A60645@xor.obsecurity.org> References: <20011114235755.A60439@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dinesh@alphaque.com on Thu, Nov 15, 2001 at 04:13:31PM +0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 15, 2001 at 04:13:31PM +0800, Dinesh Nair wrote: > > Not relevant; when headers change, they change, and you have to > > recompile code against the new version, not the old (i.e. by doing a >=20 > i understand that, but was sort of moaning that the headers have changed > midstream within a point release, instead of being committed against the > next point release. it's a minor bitch.=20 Tough :-) That's how FreeBSD is developed (there's no such thing as "committed against the next point release"), and thats why a note was added to UPDATING. Kris --Kj7319i9nmIyA2yE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE78319Wry0BWjoQKURAjwMAKDQnZF5uAqVi2cfNo9vi3GGGubVYQCgijU0 0PIejXWVLCnb9FB0WTRBY1s= =3lcm -----END PGP SIGNATURE----- --Kj7319i9nmIyA2yE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Nov 15 0:44: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id E892337B418 for ; Thu, 15 Nov 2001 00:44:03 -0800 (PST) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.32 #1) id 164I7u-0003O2-00 for freebsd-stable@freebsd.org; Thu, 15 Nov 2001 10:44:02 +0200 Received: from localhost ([127.0.0.1] helo=pampa.cs.huji.ac.il ident=danny) by pampa.cs.huji.ac.il with esmtp (Exim 3.22 #2) id 164I7u-0008U2-00 for freebsd-stable@freebsd.org; Thu, 15 Nov 2001 10:44:02 +0200 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: freebsd-stable@freebsd.org Subject: union fs Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 15 Nov 2001 10:44:02 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, I've been running several dataless/diskless machines with union-fs (for the /etc stuff) with no - apparent - problems for several months now, so i was wondering if the commnet about it being buggy still holds? danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Nov 15 0:55:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns2.alphaque.com (ns2.alphaque.com [202.185.254.11]) by hub.freebsd.org (Postfix) with SMTP id F40F137B417 for ; Thu, 15 Nov 2001 00:55:13 -0800 (PST) Received: (qmail 26203 invoked from network); 15 Nov 2001 08:55:11 -0000 Received: from ns2.alphaque.com (HELO prophet.alphaque.com) (202.185.254.11) by ns2.alphaque.com with SMTP; 15 Nov 2001 08:55:11 -0000 Received: from localhost (im1rec6pjmnbu9rl@localhost [127.0.0.1]) by prophet.alphaque.com (8.11.6/8.11.6) with ESMTP id fAF8snD01947; Thu, 15 Nov 2001 16:54:49 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Thu, 15 Nov 2001 16:54:49 +0800 (MYT) From: Dinesh Nair To: Kris Kennaway Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ipfw fails between 10/17 and 11/6 In-Reply-To: <20011115003157.A60645@xor.obsecurity.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 15 Nov 2001, Kris Kennaway wrote: > Tough :-) That's how FreeBSD is developed (there's no such thing as > "committed against the next point release"), and thats why a note was which would be a nice thing to have dont you think ? at least for stuff which requires a buildworld to fix. nevertheless, its not too big a deal, just caused some consternation on my side when it happenned. Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Nov 15 2:59:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scribble.fsn.hu (scribble.fsn.hu [193.224.40.95]) by hub.freebsd.org (Postfix) with SMTP id 2C3EE37B405 for ; Thu, 15 Nov 2001 02:59:32 -0800 (PST) Received: (qmail 18293 invoked by uid 1000); 15 Nov 2001 10:59:30 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 15 Nov 2001 10:59:30 -0000 Date: Thu, 15 Nov 2001 11:59:30 +0100 (CET) From: Attila Nagy To: Danny Braniss Cc: freebsd-stable@freebsd.org Subject: Re: union fs In-Reply-To: Message-ID: <20011115115819.P18123-100000@scribble.fsn.hu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, > I've been running several dataless/diskless machines with union-fs > (for the /etc stuff) with no - apparent - problems for several months > now, so i was wondering if the commnet about it being buggy still > holds? Try to run a program on a union-mounted FS which uses sendfile() to transfer data (the easiest to try is the webfsd from the ports tree). It will send garbage, collected from various places from your harddrive. -------------------------------------------------------------------------- Attila Nagy e-mail: Attila.Nagy@fsn.hu Budapest Polytechnic (BMF.HU) @work: +361 210 1415 (194) H-1084 Budapest, Tavaszmezo u. 15-17. cell.: +3630 306 6758 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Nov 15 3: 4:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emmi.physik.TU-Berlin.DE (emmi.physik.TU-Berlin.DE [130.149.160.103]) by hub.freebsd.org (Postfix) with ESMTP id 1030E37B419 for ; Thu, 15 Nov 2001 03:04:34 -0800 (PST) Received: (from ibex@localhost) by emmi.physik.TU-Berlin.DE (8.11.6/8.11.6) id fAFB4Wx19117; Thu, 15 Nov 2001 12:04:32 +0100 (CET) (envelope-from ibex) Date: Thu, 15 Nov 2001 12:04:32 +0100 From: Dirk Froemberg To: stable@freebsd.org Subject: Re: kernel panic if using SCSI CDROM as root device Message-ID: <20011115120432.A18404@physik.TU-Berlin.DE> References: <20011115003027.A87962@physik.TU-Berlin.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011115003027.A87962@physik.TU-Berlin.DE>; from dirk@freebsd.org on Thu, Nov 15, 2001 at 12:30:27AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! On Thu, Nov 15, 2001 at 12:30:27AM +0100, Dirk Froemberg wrote: > I build an CDROM image with a boot image containing a GENERIC kernel > and an "ordinary" FreeBSD-4.4-STABLE installation. > > After booting the kernel I get the "mountroot> " prompt. On systems > having an ATAPI-CDROM mounting the CD as a root filesystem works > (giving cd9660:/dev/acd0c as root), but not on SCSI systems (giving > cd9660:/dev/cd0c as root). On such systems a kernel panic occurs > ("Fatal trap 12: page fault while in kernel mode"). Now, some more debug information... Regards Dirk ok boot -C /kernel text=0x203a28 data=0x39464+0x19cac syms=[0x4+0x30df0+0x4+0x353fc] Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.4-STABLE #0: Thu Nov 15 11:18:56 CET 2001 dirk@bach:/usr/obj/usr/src/sys/CDROM Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 166527838 Hz CPU: Pentium/P55C (166.53-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 67043328 (65472K bytes) avail memory = 61489152 (60048K bytes) Preloaded elf kernel "kernel" at 0xc03bf000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk Using $PIR table, 6 entries at 0xc00fde70 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x6400-0x640f at device 7.1 on pci0 fxp0: port 0x6c00-0x6c3f mem 0xe9000000-0xe901ffff,0xe9020000-0xe9020fff irq 9 at device 9.0 on pci0 fxp0: Ethernet address 00:02:b3:40:db:8c inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: port 0x7000-0x70ff mem 0xe9021000-0xe9021fff irq 12 at device 10.0 on pci0 aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/255 SCBs pci0: at 12.0 irq 10 pcib1: on motherboard pci2: on pcib1 orm0: