From owner-freebsd-current Sun Jul 29 0:22:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 1D7DE37B403; Sun, 29 Jul 2001 00:22:54 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id RAA28513; Sun, 29 Jul 2001 17:22:48 +1000 Date: Sun, 29 Jul 2001 17:20:27 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Mike Smith Cc: Daniel Rock , current@FreeBSD.ORG Subject: Re: ACPI: Clock problems in -current In-Reply-To: <200107282006.f6SK6RJ01779@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 28 Jul 2001, Mike Smith wrote: > You could also try building a kernel with CLK_CALIBRATION_LOOP defined > and then booting with -v (without the timer disabled). This might be > instructive (I don't know for certain that it'll calibrate the ACPI > timer, since it may not have been probed yet). It won't. CLK_CALIBRATION_LOOP only iterates calibration of the i8254 and TSC timers relative to the RTC. None of the clock calibration stuff is very useful. All the clock frequencies depend on the temperature, so their values at boot time are only slightly more related to their values at run time than their values at a random time. Average values are probably better than boot time values. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 0:35:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by hub.freebsd.org (Postfix) with ESMTP id 606D937B401 for ; Sun, 29 Jul 2001 00:35:02 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id f6T7YPJ55232; Sat, 28 Jul 2001 21:34:30 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Sat, 28 Jul 2001 21:34:24 -1000 (HST) From: Vincent Poy To: matt Cc: Subject: Re: -current kernel panicing In-Reply-To: <20010728161828.P7031-100000@oahu.WURLDLINK.NET> Message-ID: <20010728213313.S48916-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Just a update, I did the latest buildworld with the latest -current sources and it still hapens... root@pele [9:29pm][/usr/temp] >> Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal Jul 28 21:29:40 pele /boot/kernel/kernel: 1st 0xd92fea9c process lock @ /usr/src/sys/vm/vm_glue.c:469 Jul 28 21:29:40 pele /boot/kernel/kernel: 1st 0xd92fea9c process lock @ /usr/src/sys/vm/vm_glue.c:469 Jul 28 21:29:40 pele /boot/kernel/kernel: 2nd 0xc118dfb0 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 Jul 28 21:29:40 pele /boot/kernel/kernel: 2nd 0xc118dfb0 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin On Sat, 28 Jul 2001, Vincent Poy wrote: > Interesting... I'm running on a cvsup of July 25, 2001 17:00GMT > except because of Ian Dowse mentioning in the message thread: SIGCHLD > changes causing fault on nofault entry panics, I reverted back to > src/sys/kern/kern_exit.c 1.130 and src/sys/kern/kern_sig.c 1.124 to test. > Sometimes it will just hang. I noticed that sometimes it will say when it > hangs solid: > > swap_pager: out of swap space > swap_pager_getswapspace:failed > > And this machine does have 512Megs of ram and only 64 is used most > of the time. Even swapinfo indicates that it's not using the swap yet. > > root@pele [4:23pm][/usr/home/vince] >> swapinfo > Device 1K-blocks Used Avail Capacity Type > /dev/da0s1b 262016 0 262016 0% Interleaved > > >From the following output, it seems like nfs code is at fault but we're > not even using nfs at all > > root@pele [4:24pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep > da041d9c > root@pele [4:25pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep > da041d9 > root@pele [4:25pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep > da041d > root@pele [4:25pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep > da041 > root@pele [4:25pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep > da04 > c02bda04 T nfs_curusec > > root@pele [4:25pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep > c118de00 > root@pele [4:27pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep > c118de0 > root@pele [4:27pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep > c118de > root@pele [4:27pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep > c118d > root@pele [4:27pm][/usr/home/vince] >> nm -n /boot/kernel/kernel | grep > c118 > c03dc118 ? __set_sysuninit_set_sym_M_IFADDR_uninit_sys_uninit > c03ec118 d twed_twe_driver_list > > > Cheers, > Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > WurldLink Corporation / / / / | / | __] ] > San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin > > > On Sat, 28 Jul 2001, matt wrote: > > > Something wrong in the fs lock code. > > > > ====================================== > > WWW.XGFORCE.COM > > The Next Generation Load Balance and > > Fail Safe Server Clustering Software > > for the Internet. > > ====================================== > > ----- Original Message ----- > > From: "Vincent Poy" > > To: > > Sent: Saturday, July 28, 2001 2:49 AM > > Subject: -current kernel panicing > > > > > > > I'm getting a panic in the -current kernel with using > > kernels > > > built with src/sys/kern/kern_exit.c 1.130 and > > src/sys/kern/kern_sig.c > > > 1.124 as well as with src/sys/kern/kern_exit.c 1.131 > > and > > > src/sys/kern/kern_sig.c 1.125. This seems to be a > > problem that only > > > passwd(1) and chpass(1) seems to cause. vipw appears > > to work fine as well > > > as everything else. This is what happens: > > > > > > root@pele [10:55pm][~] >> passwd toor > > > Changing local password for toor. > > > New password: > > > Retype new password: > > > passwd: updating the database... > > > passwd: done > > > root@pele [10:55pm][~] >> > > > root@pele [10:55pm][~] >> > > > root@pele [10:55pm][~] >> > > > root@pele [10:55pm][~] >> > > > root@pele [10:55pm][~] >> > > > root@pele [10:55pm][~] >> > > > root@pele [10:55pm][~] >> > > > root@pele [10:55pm][~] >> > > > After here, it just freezes solid for 1 minute then > > displays on > > > the console... > > > > > > Jul 27 22:57:24 pele /boot/kernel/kernel: lock order > > reversal > > > Jul 27 22:57:24 pele /boot/kernel/kernel: lock order > > reversal > > > Jul 27 22:57:24 pele /boot/kernel/kernel: 1st > > 0xda041d9c process lock @ > > > /usr/src/sys/vm/vm_glue.c:469 > > > Jul 27 22:57:24 pele /boot/kernel/kernel: 1st > > 0xda041d9c process lock @ > > > /usr/src/sys/vm/vm_glue.c:469 > > > Jul 27 22:57:24 pele /boot/kernel/kernel: 2nd > > 0xc118de00 lockmgr interlock > > > @ /usr/src/sys/kern/kern_lock.c:239 > > > Jul 27 22:57:24 pele /boot/kernel/kernel: 2nd > > 0xc118de00 lockmgr interlock > > > @ /usr/src/sys/kern/kern_lock.c:239 > > > > > > Then it just hangs completely, not even a db> prompt > > so had to hard reboot > > > and it goes into single user mode where one would need > > to fsck all the > > > slices and then I have to: > > > cp -p /var/backups/master.passwd.bak > > /etc/master.passwd > > > since the password database somehow got corrupted and > > then ran vipw and > > > :wq! and then shutdown the machine where it would boot > > normally. Anyone > > > have any ideas how to solve this one or what is > > causing it since the > > > previous GENERIC kernel from the 6/16/2001 build > > of -current seemed fine. > > > > > > Cheers, > > > Vince - vince@WURLDLINK.NET - Vice President > > ________ __ ____ > > > Unix Networking Operations - FreeBSD-Real Unix for > > Free / / / / | / |[__ ] > > > WurldLink Corporation > > / / / / | / | __] ] > > > San Francisco - Honolulu - Hong Kong > > / / / / / |/ / | __] ] > > > HongKong Stars/Gravis UltraSound Mailing Lists Admin > > /_/_/_/_/|___/|_|[____] > > > Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC > > Network Server Admin > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the > > message > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 1:50:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by hub.freebsd.org (Postfix) with ESMTP id 45D4937B403; Sun, 29 Jul 2001 01:50:21 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id f6T8npS55876; Sat, 28 Jul 2001 22:49:51 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Sat, 28 Jul 2001 22:49:51 -1000 (HST) From: Vincent Poy To: Ian Dowse Cc: , , Subject: Re: SIGCHLD changes causing fault on nofault entry panics In-Reply-To: <200107271451.aa00148@salmon.maths.tcd.ie> Message-ID: <20010728224835.Q48916-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 27 Jul 2001, Ian Dowse wrote: > > The panics in exit1() that have been reported on -stable appear to > be caused by these commits: > > REV:1.92.2.4 kern_exit.c 2001/07/25 17:21:46 dillon > REV:1.72.2.7 kern_sig.c 2001/07/25 17:21:46 dillon > > MFC kern_exit.c 1.131, kern_sig.c 1.125 - bring SIGCHLD SIG_IGN signal > handling in line with other operating systems. > > These probably correspond to similar panics seen in -current, but I > haven't checked the details. > > In the vmcore I just got, the panic occurred in the following > fragment in exit1(), when dereferencing p_sigacts (which is > p_procsig->ps_sigacts). I guess there is a race here if the parent > is exiting or something? > > + if ((p->p_pptr->p_procsig->ps_flag & PS_NOCLDWAIT) > + || p->p_pptr->p_sigacts->ps_sigact[_SIG_IDX(SIGCHLD)] == SIG_IGN) { > > Matt, I will just back out these changes from RELENG_4 shortly > until the issue is resolved. The change was non-essential and quite > contained, so it's probably better than waiting for a fix. > > Ian The problem seems to cause the following panic in vm_glue.c and nd kern_lock.c as well. Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal Jul 28 21:29:40 pele /boot/kernel/kernel: 1st 0xd92fea9c process lock @ /usr/src/sys/vm/vm_glue.c:469 Jul 28 21:29:40 pele /boot/kernel/kernel: 1st 0xd92fea9c process lock @ /usr/src/sys/vm/vm_glue.c:469 Jul 28 21:29:40 pele /boot/kernel/kernel: 2nd 0xc118dfb0 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 Jul 28 21:29:40 pele /boot/kernel/kernel: 2nd 0xc118dfb0 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 panic: recurse Debugger ("panic") Stopped at Debugger+0x44: push1 %ebx db> and then it just hangs solid here. Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 2: 7: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id E207C37B401 for ; Sun, 29 Jul 2001 02:07:03 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id 96B053E28; Sun, 29 Jul 2001 02:07:03 -0700 (PDT) Received: from bazooka.unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id 8BFCF3C12B for ; Sun, 29 Jul 2001 02:07:03 -0700 (PDT) To: current@freebsd.org Subject: HEADS UP: new libmp imported Date: Sun, 29 Jul 2001 02:06:58 -0700 From: Dima Dorfman Message-Id: <20010729090703.96B053E28@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've imported the libmp-in-terms-of-OpenSSL library and connected it to the build. I've also disconnected libgmp and friends from the build, but have not `cvs rm`'d it yet. Assuming no problems turn up, I plan to do that in two or three days. The only program that use libmp that I haven't been able to test is the Kerberized telnet, but since it's the same code as the other telnets, there shouldn't be any problems. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 7:29:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from neptune.he.net (neptune.he.net [216.218.166.2]) by hub.freebsd.org (Postfix) with ESMTP id 687A337B403 for ; Sun, 29 Jul 2001 07:29:29 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: from netrinsics.com ([202.108.25.152] (may be forged)) by neptune.he.net (8.8.6/8.8.2) with ESMTP id HAA29029 for ; Sun, 29 Jul 2001 07:29:29 -0700 Received: (from robinson@localhost) by netrinsics.com (8.11.2/8.11.1) id f6TETe100733 for current@outbound.freebsd.org; Sun, 29 Jul 2001 22:29:40 +0800 (+0800) (envelope-from robinson) Date: Sun, 29 Jul 2001 22:29:40 +0800 (+0800) From: Michael Robinson Message-Id: <200107291429.f6TETe100733@netrinsics.com> To: current@freebsd.org Subject: X in free(): error: recursive call. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am running -CURRENT as of 2001/01/31 12:00, more or less uneventfully for the last six months on a Dell 5000e. The one problem is that X occasionally dies without coredump or cleanup with the error 'X in free(): error: recursive call.'. This usually (but not always) happens while using Mozilla with heavy window creation/deletion and heavy (dialup) network activity. This has happened under several recent versions of Mozilla, two different versions of fvwm2, with and without session managers, and with both X 4.0.3 and 4.1.0. It took me a while to identify the problem, because it happens infrequently, unpredicably, and leaves the video drivers in an unusable state (forcing a blind reboot). I tried linking /etc/malloc.conf to 'A' to get a coredump from X, but that doesn't work. I found a very short discussion of a related problem in the -CURRENT mail archives from the beginning of January, but there wasn't any apparent resolution of the problem. I'd like to get advice on which of the following courses of action to take: 1. Isolate and fix the problem. I would need some help here. 2. Downgrade to -STABLE. The reason I was running -CURRENT originally was for ACPI support, but Dell has since released an APM-enabled BIOS for the 5000e, so -CURRENT is no longer a requirement. 3. Upgrade to current -CURRENT. I don't know if this is such a good idea judging from mailing list traffic. 4. Hang in with the status quo for another couple months until 5.0 is released, install that, and start back at #1 if that doesn't work. Any advice, comments, or suggestions warmly appreciated. Thanks. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 7:37:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id D98D537B403 for ; Sun, 29 Jul 2001 07:37:21 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15Qrhm-0000ws-00; Sun, 29 Jul 2001 16:38:06 +0200 From: Sheldon Hearn To: Michael Robinson Cc: current@FreeBSD.org Subject: Re: X in free(): error: recursive call. In-reply-to: Your message of "Sun, 29 Jul 2001 22:29:40 +0800." <200107291429.f6TETe100733@netrinsics.com> Date: Sun, 29 Jul 2001 16:38:06 +0200 Message-ID: <3649.996417486@axl.seasidesoftware.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 29 Jul 2001 22:29:40 +0800, Michael Robinson wrote: > I'd like to get advice on which of the following courses of action to take: > > 1. Isolate and fix the problem. I would need some help here. Try a better-proven release of XFree86, namely 3.3.6. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 7:46:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 9742D37B403 for ; Sun, 29 Jul 2001 07:46:37 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.4/8.11.4) id f6TEkax12138; Sun, 29 Jul 2001 07:46:36 -0700 (PDT) Date: Sun, 29 Jul 2001 07:46:36 -0700 (PDT) From: David Wolfskill Message-Id: <200107291446.f6TEkax12138@bunrab.catwhisker.org> To: robinson@netrinsics.com, sheldonh@starjuice.net Subject: Re: X in free(): error: recursive call. Cc: current@FreeBSD.ORG In-Reply-To: <3649.996417486@axl.seasidesoftware.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >From: Sheldon Hearn >Date: Sun, 29 Jul 2001 16:38:06 +0200 >On Sun, 29 Jul 2001 22:29:40 +0800, Michael Robinson wrote: >> I'd like to get advice on which of the following courses of action to take: >> 1. Isolate and fix the problem. I would need some help here. >Try a better-proven release of XFree86, namely 3.3.6. FWIW, the laptop I use is very similar to a Dell Inspiron 5000e. I was unable to use XF86 3.x because the machine has a display with a resolution of 1400x1050 (which XF86 3.x apparently doesn't cope with for the ATI Rage Mobility). Information about how I set the machine up is at http://www.catwhisker.org/~david/FreeBSD/laptop.html -- briefly, I've been tracking both -STABLE & -CURRENT daily (with a few exceptions). Though I do most of tthe work on the machine in -STABLE, I do not recall encountering the symptoms mentioned by Michael Robinson, and I do fire up netscape & a few other things in -CURRENT as a reality check fairly often. If there's a more specific sequence of events for causing the observed failure, I'll be happy to try the sequence after today's -CURRENT finishes building, and report back. Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 12:30:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from private.as (ppp-2-38.cvx6.telinco.net [212.1.135.38]) by hub.freebsd.org (Postfix) with SMTP id CD17737B403 for ; Sun, 29 Jul 2001 12:30:41 -0700 (PDT) (envelope-from jokeline@private.as) From: "John" To: Subject: Have a good laugh! Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 29 Jul 2001 20:30:25 +0100 X-Priority: 1 (Highest) Content-Transfer-Encoding: 8bit Message-Id: <20010729193041.CD17737B403@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Wind-up A Friend, Colleague, Relative Or Even An Enemy -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Call Jokeline and you'll be in stitches! With our new service you're able to wind-up, confuse and bemuse people with a choice of bogus callers that you can transfer to your victim on any UK landline or mobile and then listen in to the call and hear their reaction Don't worry though, they won't be able to hear you, nor tell that you made the call - try it on a speaker phone and a group can hear -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- Just use the easy to follow recipe: -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- (i) choose one ripe victim (ii) add Jokeline by dialling 0906 736 9265 and select 1 - Wind-up samples 2 - Mr Angry 3 - The Irate Delivery Driver 4 - An Invite To No 10 5 - There's A Bomb In Your Street 6 - You're Wanted At The Police Station 7 - The Tax Inspector 8 - You've Got My Daughter Pregnant (iii) enter your victims number and wait for the transfer (iv) when they answer, prepare yourself and ...enjoy! -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This has got to be the funniest way to wind-up anyone -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Jokeline BCM 1543 London WC1N 3XX United Kingdom Calls to 0906 numbers are charged at £1/min at all times Maximum call duration 5 mins, average 2 mins Please ensure you have the permission of the bill payer before calling -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- You've received this email as you're on our mailing list If however, you do not wish to receive any further emails simply mailto:anallyretentive@yours.com with the email address(es) to be removed inserted in the subject line To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 13:17:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id C6B2237B401; Sun, 29 Jul 2001 13:17:50 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15Qx1Y-0000NK-00; Sun, 29 Jul 2001 22:18:52 +0200 From: Sheldon Hearn To: current@FreeBSD.org Cc: jhb@FreeBSD.org Subject: Re: Help wanted: loadable SMBFS In-reply-to: Your message of "Wed, 25 Jul 2001 21:30:49 +0200." <872.996089449@axl.seasidesoftware.co.za> Date: Sun, 29 Jul 2001 22:18:51 +0200 Message-ID: <1445.996437931@axl.seasidesoftware.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have an update on this one. (John, lemme know if you want access to the crashdump). On Wed, 25 Jul 2001 21:30:49 +0200, Sheldon Hearn wrote: > > Log: > > Add build infrastructure for a libiconv loadable kernel module. > > > > This should allow the use of the smbfs module without the > > requirement to rebuild the kernel with LIBICONV. > > I haven't connected this to the modules build because I can't test that > it works. Sure, it loads fine, but I get a reproducible kernel mode > page fault in the rl(4) interrupt handler when I actually try to use it. The kernel mode page fault isn't in the if_rl interrupt handler. That was a weird red herring. It took a while to get a working crashdump. I would type panic and press enter, coming right back to the prompt. If I pressed enter or typed panic and pressed enter at the prompt, I'd get this: panic: Lock (sx) allproc not locked. [...] kern_synch.c:297 Eventually, I got a crashdump as follows: > panic > trace > panic Weird. So here's what's actually going wrong for me: #10 0xc0271480 in trap (frame={tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = -881182336, tf_esi = -1053397736, tf_ebp = -852845520, tf_isp = -852845552, tf_ebx = -1070565552, tf_edx = 0, tf_ecx = -881182336, tf_eax = -1070717408, tf_trapno = 12, tf_err = 0, tf_eip = -1071939473, tf_cs = 8, tf_eflags = 66071, tf_esp = -1053397736, tf_ss = -1054244352}) at /usr/src/sys/i386/i386/trap.c:410 410 (void) trap_pfault(&frame, FALSE, eva); #11 0xc01b806f in witness_destroy (lock=0xc1366d18) at /usr/src/sys/kern/subr_witness.c:395 #12 0xc0191b8b in mtx_destroy (m=0xc1366d18) at /usr/src/sys/kern/kern_mutex.c:680 #13 0xc134827d in smb_iod_destroy (iod=0xc1366d00) at /usr/src/sys/modules/smbfs/../../netsmb/smb_iod.c:692 [...] Looking inside frame #11... (kgdb) frame 11 #11 0xc01b806f in witness_destroy (lock=0xc1366d18) at /usr/src/sys/kern/subr_witness.c:395 395 STAILQ_REMOVE(&all_locks, lock, lock_object, lo_list); (kgdb) print *lock->lo_witness $34 = {w_name = 0xc029dbc6 "(dead)", w_class = 0xc02e0380, w_list = { stqe_next = 0xc0307778}, w_typelist = {stqe_next = 0xc0307778}, w_children = 0x0, w_file = 0xc029dbc6 "(dead)", w_line = 0, w_level = 1, w_refcount = 0, w_Giant_squawked = 0 '\000', w_other_squawked = 0 '\000', w_same_squawked = 0 '\000'} I'm absolutely stumped. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 13:20:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 1107D37B406 for ; Sun, 29 Jul 2001 13:20:25 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.140.234.Dial1.SanJose1.Level3.net [209.245.140.234]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id NAA24353; Sun, 29 Jul 2001 13:20:16 -0700 (PDT) Message-ID: <3B646CF2.F5E332A9@mindspring.com> Date: Sun, 29 Jul 2001 13:07:14 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kazutaka YOKOTA Cc: freebsd-current@freebsd.org Subject: Re: Death sentence to KLD screen savers? Comments? References: <200107241207.VAA14339@zodiac.mech.utsunomiya-u.ac.jp> <3B5E7DB3.97656D3C@mindspring.com> <200107260729.QAA25125@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote: > >> I propose to have user-land screen savers instead of KLD > >> screen savers. > > > >[ ... "performance degradation" ... ] > > > >[ ... "file access" ... ] > > > >I don't see either of these as being compelling arguments > >in favor of a user space implementation; I guess this means > >you want to do file access in your screen saver(s). > > Both points/complaints/requests have been raised several times in our > mailing lists in the past. (Sorry, I don't keep copies.) I didn't say they weren't arguments, merely that I did not find them compelling. This looks to me like change for the sake of change. > Some people don't like cputime eaten up by the screen saver in the > kernel... The simple answer for this is to run in a kproc, and set the priority to "idle", so it only runs when there is nothing else to run. Actually, running in user space adds two problems: 1) Performance degradation as a result of protection domain crossing which does not exist in the current implementation 2) Inability to disable the screen saver in, for example, a "panic" situation, where there is no opportunity to return to user space and have the screen put back into a known good state. This is analogous to the problem we have diagnosing kernel panics while X11 is running on the console: only the user space program can undo what it has done, and we can not run the user space program. > Some peopel want to write "interesting" screen savers... Now we see the real reason for this... 8^). > >Now if you could run Windows screen saver modules, you > >might have a good argument for change, above and beyond > >"change for the sake of change". > > Personally I am not interested in fancy screen savers :-) But, just want > to keep things tidy and keep the system running smoothly. By moving > much of the screen saver support from the console driver to the > user-land... The problem here is that only the video driver knows what it knows; short of converting FreeBSD's console over to something like "GGI", you will have a hard time moving *everything* to userland. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 14: 6:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 01AF237B401 for ; Sun, 29 Jul 2001 14:06:11 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.140.234.Dial1.SanJose1.Level3.net [209.245.140.234]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id OAA28687; Sun, 29 Jul 2001 14:06:07 -0700 (PDT) Message-ID: <3B647AE5.7B0DE04C@mindspring.com> Date: Sun, 29 Jul 2001 14:06:45 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: andrewl@nshore.com Cc: current@FreeBSD.ORG Subject: Re: NFS file locking fails from Solaris References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG andrewl@nshore.com wrote: > The Solaris client mounts the FreeBSD exported filesystem fine. I can > create, delete, and manipulate files fine. > > However, when I try to use fcntl to lock a file, the Solaris client hangs. > Normally, I would just let this go; however, Cadence (the VLSI CAD tool > company) requires locks to work in order to use its tools. Therefore, I > can't use FreeBSD as a fileserver in my environment. > > If I monitor the traffic on the line with ethereal, I see the request for > the version 4 nlockmgr from the Solaris client to the FreeBSD server. I > see the FreeBSD server respond with the correct version and port. > However, after this, I start seeing a bunch of SYN/RST packets being > thrown around, and I never see a lock request initiated from the Solaris > client. Who is sending the RST's? (= the connection you are attempting to use does not exist) Who is sending the SYN's? (= I am attempting to establis a new conneciton) This may be related to the "secure" initial sequence number generation algorithm FreeBSD uses; there have been several fixes that have backed this out in various branches. It may also be that your FreeBSD box is multihomes, and you are sending the response on an interface different that the one it was received on (and thus different than the IP address the client is expecting, so the client believes it's a spoof attempt). You should be able to fix this by setting up an explicit route on the FreeBSD box, and potentially the Sun box, depending on how arcane your network setup is. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 14:59:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id B6D1537B401; Sun, 29 Jul 2001 14:59:51 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15QycH-0000fV-00; Mon, 30 Jul 2001 00:00:53 +0200 From: Sheldon Hearn To: current@FreeBSD.org Cc: jhb@FreeBSD.org Subject: Re: Help wanted: loadable SMBFS In-reply-to: Your message of "Sun, 29 Jul 2001 22:18:51 +0200." <1445.996437931@axl.seasidesoftware.co.za> Date: Mon, 30 Jul 2001 00:00:53 +0200 Message-ID: <2572.996444053@axl.seasidesoftware.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 29 Jul 2001 22:18:51 +0200, Sheldon Hearn wrote: > (kgdb) frame 11 > #11 0xc01b806f in witness_destroy (lock=0xc1366d18) > at /usr/src/sys/kern/subr_witness.c:395 > 395 STAILQ_REMOVE(&all_locks, lock, lock_object, lo_list); I got a little help from some folks on IRC who helped me with a disassembly that confirms a null pointer dereference in the STAILQ_REMOVE(). So I started walking all_locks. It's a boring process. Isn't there a faster way to find out whether lock's address is the value of an lo_list->stqe_next member of any entry in all_locks before the list-terminating NULL? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 15:19:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-104-149.dsl.lsan03.pacbell.net [64.169.104.149]) by hub.freebsd.org (Postfix) with ESMTP id 2E47637B401 for ; Sun, 29 Jul 2001 15:19:48 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5A05A66B25; Sun, 29 Jul 2001 15:19:47 -0700 (PDT) Date: Sun, 29 Jul 2001 15:19:47 -0700 From: Kris Kennaway To: Dima Dorfman Cc: current@freebsd.org Subject: Re: HEADS UP: new libmp imported Message-ID: <20010729151946.B96357@xor.obsecurity.org> References: <20010729090703.96B053E28@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="5/uDoXvLw7AC5HRs" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010729090703.96B053E28@bazooka.unixfreak.org>; from dima@unixfreak.org on Sun, Jul 29, 2001 at 02:06:58AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --5/uDoXvLw7AC5HRs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Jul 29, 2001 at 02:06:58AM -0700, Dima Dorfman wrote: > I've imported the libmp-in-terms-of-OpenSSL library and connected it > to the build. I've also disconnected libgmp and friends from the > build, but have not `cvs rm`'d it yet. Assuming no problems turn up, > I plan to do that in two or three days. The only program that use > libmp that I haven't been able to test is the Kerberized telnet, but > since it's the same code as the other telnets, there shouldn't be any > problems. When Mark and I talked about this a few months ago, we concluded that we'd have to first break out the (self-contained) bignum lib from the openssl code so it's available without the crypto source code installed. This would involve a repo copy of crypto/openssl/crypto/bn to contrib/openssl-bn or something, and I'd keep the two in sync with future vendor imports. Kris --5/uDoXvLw7AC5HRs 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 iD8DBQE7ZIwCWry0BWjoQKURAh8QAKCZIcEuSA7fAXtPuu40GQzDXZ/+ogCgmPcC 9I+XexDSZQh2KlZ6ut0nyAI= =C//E -----END PGP SIGNATURE----- --5/uDoXvLw7AC5HRs-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 15:41:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 5900437B401 for ; Sun, 29 Jul 2001 15:41:27 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id BCE563E31; Sun, 29 Jul 2001 15:41:16 -0700 (PDT) Received: from bazooka.unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id B09B93C12C; Sun, 29 Jul 2001 15:41:16 -0700 (PDT) To: Kris Kennaway Cc: current@freebsd.org Subject: Re: HEADS UP: new libmp imported In-Reply-To: <20010729151946.B96357@xor.obsecurity.org>; from kris@obsecurity.org on "Sun, 29 Jul 2001 15:19:47 -0700" Date: Sun, 29 Jul 2001 15:41:11 -0700 From: Dima Dorfman Message-Id: <20010729224116.BCE563E31@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kris Kennaway writes: > On Sun, Jul 29, 2001 at 02:06:58AM -0700, Dima Dorfman wrote: > > I've imported the libmp-in-terms-of-OpenSSL library and connected it > > to the build. I've also disconnected libgmp and friends from the > > build, but have not `cvs rm`'d it yet. Assuming no problems turn up, > > I plan to do that in two or three days. The only program that use > > libmp that I haven't been able to test is the Kerberized telnet, but > > since it's the same code as the other telnets, there shouldn't be any > > problems. > > When Mark and I talked about this a few months ago, we concluded that > we'd have to first break out the (self-contained) bignum lib [...] BIGNUM isn't self-contained. It needs the ERR_* subsystem, as well as (I think) the BIO subsystem. I tried creating a libbignum by only compiling stuff from openssl/bn, and it didn't work very well. If you can get it to work, so much the better. That said, right now everything that uses libmp could be considered `crypto' code, anyway, so it may just be better to classify it as such as not install it in the NO_CRYPTO case (is there such a knob, anyway?). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 16:39:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id AEF2E37B401 for ; Sun, 29 Jul 2001 16:39:11 -0700 (PDT) (envelope-from steve@havk.org) Received: from bsd.havk.org ([24.214.56.224]) by mail.hiwaay.net (8.11.3/8.11.3) with ESMTP id f6TNd4F30066; Sun, 29 Jul 2001 18:39:05 -0500 (CDT) Received: by bsd.havk.org (Postfix, from userid 1001) id C264C1A7DE; Sun, 29 Jul 2001 18:38:36 -0500 (CDT) Date: Sun, 29 Jul 2001 18:38:36 -0500 From: Steve Price To: Kris Kennaway Cc: Dima Dorfman , current@FreeBSD.ORG Subject: Re: HEADS UP: new libmp imported Message-ID: <20010729183836.F18598@bsd.havk.org> References: <20010729090703.96B053E28@bazooka.unixfreak.org> <20010729151946.B96357@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010729151946.B96357@xor.obsecurity.org>; from kris@obsecurity.org on Sun, Jul 29, 2001 at 03:19:47PM -0700 X-Operating-System: FreeBSD 4.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I think I might have missed part of this thread so forgive me if this has already been brought up. We need to get a couple of package builds under our belts before this gets MFCd. I seem to recall there were a couple of ports that expected libgmp to be around. If so, we'll need to weed those out and either get them to use libmp if possible or provide libgmp as a port. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 16:48:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-104-149.dsl.lsan03.pacbell.net [64.169.104.149]) by hub.freebsd.org (Postfix) with ESMTP id 60D6B37B401 for ; Sun, 29 Jul 2001 16:48:26 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 210AF66B25; Sun, 29 Jul 2001 16:48:23 -0700 (PDT) Date: Sun, 29 Jul 2001 16:48:21 -0700 From: Kris Kennaway To: Steve Price Cc: Kris Kennaway , Dima Dorfman , current@FreeBSD.ORG Subject: Re: HEADS UP: new libmp imported Message-ID: <20010729164821.A10506@xor.obsecurity.org> References: <20010729090703.96B053E28@bazooka.unixfreak.org> <20010729151946.B96357@xor.obsecurity.org> <20010729183836.F18598@bsd.havk.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010729183836.F18598@bsd.havk.org>; from steve@havk.org on Sun, Jul 29, 2001 at 06:38:36PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Jul 29, 2001 at 06:38:36PM -0500, Steve Price wrote: > I think I might have missed part of this thread so forgive me > if this has already been brought up. We need to get a couple > of package builds under our belts before this gets MFCd. I > seem to recall there were a couple of ports that expected libgmp > to be around. If so, we'll need to weed those out and either > get them to use libmp if possible or provide libgmp as a port. Yep; I dont think anyone is talking about MFCing this in the near future. libgmp3 is already a port. Kris --2fHTh5uZTiUOsy+g 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 iD8DBQE7ZKDEWry0BWjoQKURAuO/AJ4qyMFVfYgWU0wwifRE9vP2w8Z7RwCeO0mi DW+gTZ4GecTAbfnt/1yRHjw= =P7tg -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 16:54:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id ED41437B403 for ; Sun, 29 Jul 2001 16:54:54 -0700 (PDT) (envelope-from steve@havk.org) Received: from bsd.havk.org (user-24-214-56-224.knology.net [24.214.56.224]) by mail.hiwaay.net (8.11.3/8.11.3) with ESMTP id f6TNsrF27307; Sun, 29 Jul 2001 18:54:53 -0500 (CDT) Received: by bsd.havk.org (Postfix, from userid 1001) id 0630C1A7DF; Sun, 29 Jul 2001 18:54:52 -0500 (CDT) Date: Sun, 29 Jul 2001 18:54:51 -0500 From: Steve Price To: Kris Kennaway Cc: Dima Dorfman , current@FreeBSD.ORG Subject: Re: HEADS UP: new libmp imported Message-ID: <20010729185451.H18598@bsd.havk.org> References: <20010729090703.96B053E28@bazooka.unixfreak.org> <20010729151946.B96357@xor.obsecurity.org> <20010729183836.F18598@bsd.havk.org> <20010729164821.A10506@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010729164821.A10506@xor.obsecurity.org>; from kris@obsecurity.org on Sun, Jul 29, 2001 at 04:48:21PM -0700 X-Operating-System: FreeBSD 4.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 29, 2001 at 04:48:21PM -0700, Kris Kennaway wrote: > > Yep; I dont think anyone is talking about MFCing this in the near > future. libgmp3 is already a port. Doh! You're right there is a libgmp3 port. Can anyone tell my brain is mush after having spent all day at a water park with 20 some odd kids all under the age of 8? :) -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 17: 1:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from CPE-61-9-164-106.vic.bigpond.net.au (unknown [144.137.9.200]) by hub.freebsd.org (Postfix) with ESMTP id D1E9E37B401 for ; Sun, 29 Jul 2001 17:01:45 -0700 (PDT) (envelope-from darrenr@reed.wattle.id.au) Received: (from root@localhost) by CPE-61-9-164-106.vic.bigpond.net.au (8.11.0/8.11.0) id f6U01hN17303 for ; Mon, 30 Jul 2001 10:01:43 +1000 (EST) From: Darren Reed Message-Id: <200107300001.KAA24098@avalon.reed.wattle.id.au> Subject: (ref5) kdump: Cannout allocate memory To: current@freebsd.org Date: Mon, 30 Jul 2001 10:01:39 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Using ktrace ref5, I created ~darrenr/ktrace.out with "ktrace -i cc ..." but trying to print it I get: % kdump -f ~/ktrace.out > lout kdump: Cannot allocate memory Is this stack corruption by kdump? ref5:~darrenr/ktrace.out is available for anyone who wants to diagnose this further. FYI: % limit cputime unlimited filesize unlimited datasize 524288 kbytes stacksize 65536 kbytes coredumpsize unlimited memoryuse unlimited descriptors 2088 memorylocked unlimited maxproc 1043 I can't see that I've got any special malloc debugging things defined either in environment variables or elsewhere. Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 29 18:33: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from west.lustig.com (west.lustig.com [209.157.26.130]) by hub.freebsd.org (Postfix) with SMTP id 5507237B401 for ; Sun, 29 Jul 2001 18:32:52 -0700 (PDT) (envelope-from barry@lustig.com) Received: (qmail 18251 invoked from network); 30 Jul 2001 01:32:51 -0000 Received: from sinister.dotcast.com (HELO lustig.com) (10.10.11.198) by west.lustig.com with SMTP; 30 Jul 2001 01:32:51 -0000 Message-ID: <3B64B93C.F55880CC@lustig.com> Date: Sun, 29 Jul 2001 21:32:44 -0400 From: Barry Lustig Organization: Barry Lustig & Associates, Inc. X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: lock panic July 27th current Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This occurred when running vmware while simultaneously compiling koffice over an NFS link. I've got dumpdev set now, so I'll get a core on the next crash. barry fxp0: promiscuous mode enabled vmnet1: promiscuous mode enabled lock order reversal 1st 0xc19e8700 pcm0:3:play @ /usr/src/sys/dev/sound/pcm/dsp.c:117 2nd 0xc19e8ac0 pcm0 @ /usr/src/sys/dev/sound/pcm/sound.c:99 lock order reversal 1st 0xcc14eb9c process lock @ /usr/src/sys/vm/vm_glue.c:469 2nd 0xc0cdaf80 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 recursed on non-recursive lock (sleep mutex) process lock @ /usr/src/sys/kern/kern_lock.c:262 first acquired @ /usr/src/sys/kern/kern_exit.c:327 panic: recurse syncing disks... 36 36 panic: Lock (sx) allproc not locked @ /usr/src/sys/kern/kern_proc.c:152. Uptime: 12m21s /dev/vmmon: Module vmmon: unloaded Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... 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 5.0-CURRENT #0: Fri Jul 27 19:50:06 EDT 2001 barry@vaio.lustig.com:/usr/obj/usr/src/sys/VAIO Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (645.21-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 201261056 (196544K bytes) avail memory = 190930944 (186456K bytes) Preloaded elf kernel "kernel" at 0xc04a7000. Preloaded elf module "ugen.ko" at 0xc04a709c. Preloaded elf module "ums.ko" at 0xc04a7138. Preloaded elf module "umass.ko" at 0xc04a71d4. Preloaded elf module "ipl.ko" at 0xc04a7274. Pentium Pro MTRR support enabled Using $PIR table, 7 entries at 0xc00fdf50 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xfca0-0xfcbf irq 9 at device 7.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 uhub1: Philips Semiconductors hub, class 9/0, rev 1.10/1.10, addr 2 uhub1: 3 ports with 3 removable, self powered umass0: Sony USB Memory Stick Slot, rev 1.10/1.31, addr 3 ums0: Logitech USB Mouse, rev 1.10/6.20, addr 4, iclass 3/1 ums0: 3 buttons and Z dir. pci0: at 7.3 (no driver attached) pci0: at 8.0 (no driver attached) pcm0: port 0xfc8c-0xfc8f,0xfcc0-0xfcff mem 0xfedf8000-0xfedfffff irq 9 at device 9.0 on pci0 pci0: at 10.0 (no driver attached) fxp0: port 0xfc40-0xfc7f mem 0xfec00000-0xfecfffff,0xfedf6000-0xfedf6fff irq 9 at device 11.0 on pci0 fxp0: Ethernet address 08:00:46:0d:8b:a9 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci_cfgintr_unique: hard-routed to irq 9 pci_cfgintr: 0:12 INTA routed to irq 9 pcic0: irq 9 at device 12.0 on pci0 pcic0: Memory mapped device, will work. pcic0: PCI Memory allocated: 0x44000000 pccard0: on pcic0 orm0: =0D=0A=0D=0A=20=20= =0D=0A=20=20=20=20=0D=0A=20=20=20=20=20=20

=0D=0A=20=20=20=20=20=20=  

=0D=0A=20=20=20=20=20=20English =0D=0A=20=20= =20=20=20=20Espa=F1ol=0D=0A=20= =20=0D=0A=0D=0A

=0D=0A=0D=0A=20=20
=0D=0A=20=20=0D=0A=20=20= =20=20=0D=0A=20=20=20=20=20=20
=0D=0A=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20<= span=20style=3D"background-color:=20#FFFFFF">=0D=0A=20=20=20=20=20=20=20=20Escape=0D=0A=20= =20=20=20=20=20=20=20to=20Paradise...!=0D=0A=20=20=20=20=20=20= =20=20

=0D=0A=20=20=20=20=20=20=20=20=0D= =0A=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20= =20=20=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20 =0D=0A=20=20=20=20=20=20= =20=20=20=20=20=20El=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20=20= =20Rancho=20Villas=0D=0A=20=20=20=20=20=20=20=20=20=20<= /center>=0D=0A=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20= =20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20
=0D=0A=20=20=20= =20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20 =0D=0A=20=20=20=20=20= =20=20=20=20=20 =0D=0A=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20<= font=20color=3D"#FFFFFF"=20face=3D"Arial"=20size=3D"2">Mazatlan,=0D=0A=20= =20=20=20=20=20=20=20=20=20=20=20Mexico

=0D=0A=20=20=20=20= =20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20 =0D=0A=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20=  =0D=0A=20=20=20=20=20= =20
=0D=0A=20=20
=0D=0A=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20= =20=20=20 

=0D=0A=20=20=20=20=20=20=20=20=20= =20=0D=0A=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20Dear=0D=0A=20=20= =20=20=20=20=20=20=20=20=20=20Friend:

=0D=0A=20=20=20=20=20= =20=20=20=20=20=20=20You've=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20been=20= selected=20to=20take=201=20night=20free=20for=20each=20one=20you=20pay=20= in=20our=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20resort=20at=20Mazatla= n,=20Mexico.

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20That's=0D=0A= =20=20=20=20=20=20=20=20=20=20=20=20right=20!!

=0D=0A=20=20=20= =20=20=20=20=20=20=20=20=20Pay=0D=0A=20=20= =20=20=20=20=20=20=20=20=20=201=20night=20and=20get=20another=20one=20F= REE!!

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20This=0D=0A=20= =20=20=20=20=20=20=20=20=20=20=20opportunity=20goes=20to=20only=20selec= ted=20people,=20so=20take=20advantage=20of=20this=0D=0A=20=20=20=20=20=20= =20=20=20=20=20=20unique=20offer=20you'll=20never=20see=20again=20a=20l= odging=20offer=20like=20this=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20o= ne. =20Your=20next=20vacation=20half=20the=20price!!

=0D= =0A=20=20=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20Why=0D=0A=20=20=20= =20=20=20=20=20=20=20=20=20don't=20you=20take=20a=20rest=20in=20the=20w= onderful=20beach=20of=20Mazatlan,=0D=0A=20=20=20=20=20=20=20=20=20=20=20= =20Mexico. =20This=20is=20your=20opportunity. =20Make=20it=20= possible=20for=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20you.

= =0D=0A=20=20=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20If=0D=0A=20=20= =20=20=20=20=20=20=20=20=20=20you=20use=20this=20wonderful=20opportunit= y,=20I'll=20also=20give=20you=20a=2020%=0D=0A=20=20=20=20=20=20=20=20= =20=20=20=20discount=20over=20drinks=20and=20food=20in=20our=20rest= aurant. =20The=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20delicious=20= flavors=20you're=20will=20taste=20there=20are=20going=20to=20be=0D=0A=20= =20=20=20=20=20=20=20=20=20=20=20unforgettable,=20believe=20me!<= /p>=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20I=0D=0A=20= =20=20=20=20=20=20=20=20=20=20=20send=20you=20our=20addresses=20for=20m= ore=20information,=20just=20in=20case=20you=20are=0D=0A=20=20=20=20=20=20= =20=20=20=20=20=20interested=20in=20the=20offer=20I'm=20sending=20you.<= /font>

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20= If=0D= =0A=20=20=20=20=20=20=20=20=20=20=20=20you=20want=20to=20use=20this=20b= enefit,=20please=20refer=20the=20code=20below=20to=20make=0D=0A=20=20=20= =20=20=20=20=20=20=20=20=20this=20offer=20valid:

=0D=0A=20=20= =20=20=20=20=20=20=20=20=20=20fRpromo0802

=0D=0A=20=20=20=20=20=20=20=20= =20=20=20=20Promotion=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20Validity: =20= from=20Aug=2015=20to=20Dec.=2015,=202001;=20excluding=20Thanksgiving=0D= =0A=20=20=20=20=20=20=20=20=20=20=20=20week.

=0D=0A=20=20=
=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20Web=20Sites:
=0D=0A= =20=20=20=20=20=20=20=20=20=20=20=20www.elrancho.com.mx

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20<= a=20href=3D"http://www.elranchovillas.com">www.elranchovillas.com

=0D=0A=20=20=20=20=20=20= =20=20=20=20=20=20e-mail:<= font=20color=3D"#0000FF">
=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20= info@elrancho.com.mx=0D=0A=20=20=20=20=20=20=20=20= =20=20=0D=0A=20= =20=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20= =20=20=0D=0A=20=20=20=20=20=20= =20=20=20=20=20=20=0D=0A=20=20= =20=20=20=20=20=20=20=20=20=20=0D=0A=20=20
=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20Reservations:=
=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20Tel:=20(1)716-0606
=0D= =0A=20=20=20=20=20=20=20=20=20=20=20=20Fax: =20(1)716-9777
=0D=0A= =20=20=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20= =20=20=20=20US=20&=20Canada:
=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20= 1-888-596-5760
=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20=0D=0A= =20=20=20=20=20=20=20=20=20=20=20=20Mexico:
=0D=0A=20=20=20=20=20=20=20=20=20= =20=20=2001-800-717-1991=0D=0A=20=20=20=20=20=20=20=20= =0D=0A=20=20=20=20=20=20=20=20=0D=0A=20=20
=0D=0A=20=20=20= =20=20=20To=20be=20removed=20= from=20our=20mailing=20list,=0D=0A=20=20=20=20=20=20please=20send=20us=20= a=20blank=20email=20to=20pro= mo@elrancho.com.mx=0D=0A=20=20=20=20=20=20with=20the=20word=20REMOV= E=20in=20the=20subject=20line.

=0D=0A=20=20=20=20=20=20=0D= =0A=20=20=20=20=0D=0A=20=20=0D=0A=20=20
=0D=0A=0D=0A 

=0D=0A&= nbsp;

=0D=0A 

=0D=0A 

=0D=0A 

=0D=0A 

=0D=0A 

=0D=0A 

=0D=0A 

=0D=0A=

=0D=0A=0D=0A= =20=20=0D=0A=20=20=20=20
=0D=0A=20=20=20=20=0D=0A=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20Escapa=0D=0A=20=20=20=20=20=20al=20pa= ra=EDso...!=0D=0A=20=20=20=20=20=20

= =0D=0A=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=0D=0A= =20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20 =0D=0A= =20=20=20=20=20=20=20=20=20=20Villas=0D=0A=20=20=20=20=20=20=20= =20=20=20=20=20El=20Rancho=0D=0A=20=20=20=20=20=20=20=20=
=0D=0A=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20&nbs= p;

=0D=0A=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=0D= =0A=20=20=20=20=20=20
=0D=0A=20=20=20=20=20=20=0D=0A=20=20=20= =20=20=20=20=20 =0D=0A=20=20=20=20=20=20=20=20 =0D=0A=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20Maz= atl=E1n,=0D=0A=20=20=20=20=20=20=20=20=20=20M=E9xico

=0D=0A= =20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20 =0D=0A=20=20=20=20=20=20=0D= =0A=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20 =0D=0A=20=20=20=20=20=20=20=20 =0D=0A=20=20=20=20=20=20=20= =20=0D=0A=20=20=20=20=20=20=20= =20=20=20=20=20Hola=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20amigo:=

=0D=0A=20=20=20=20=20=20=20=20=20=20Haz=0D=0A=20=20=20=20=20=20=20= =20=20=20sido=20seleccionado=20para=20llevarte=20una=20noche=20gratis=20= por=20cada=20una=20que=0D=0A=20=20=20=20=20=20=20=20=20=20pagues=20a=20= nuestro=20hotel=20en=20Mazatl=E1n,=20M=E9xico.

=0D=0A=20=20=20= =20=20=20=20=20=20=20Es=0D=0A=20=20=20=20=20=20=20=20=20=20en=20serio=20!!=

=0D=0A=20=20=20=20=20=20=20=20=20=20Paga=0D=0A=20=20=20=20=20=20=20=20=20=201=20noche=20y=20te=20llev= as=20otra=20totalmente=20GRATIS!!

=0D=0A=20=20=20=20=20=20= =20=20=20=20Esta=0D=0A=20=20=20=20=20=20=20=20=20=20oportunidad=20se=20da=20= s=F3lo=20a=20personas=20muy=20selectas,=20asi=20que=20aproveche=0D=0A=20= =20=20=20=20=20=20=20=20=20esta=20=FAnica=20oferta.  =20Jam=E1= s=20vera=20una=20oferta=20igual=20en=20lo=20que=0D=0A=20=20=20=20=20=20= =20=20=20=20a=20alojamiento=20se=20refiere. =20Sus=20pr=F3ximas=20= vacaciones=20por=20la=20mitad=0D=0A=20=20=20=20=20=20=20=20=20=20de=20p= recio!!

=0D=0A=20=20=20=20=20=20=20=20=20=20Por=0D=0A=20=20=20=20=20= =20=20=20=20=20qu=E9=20no=20tomar=20un=20descansito=20en=20las=20maravi= llosas=20playas=20de=20Mazatl=E1n,=0D=0A=20=20=20=20=20=20=20=20=20=20M= =E9xico. =20Esta=20es=20su=20oportunidad. =20H=E1gala=20posib= le=20por=20usted.

=0D=0A=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20= =20=20Es=0D=0A=20=20=20=20=20=20=20=20=20=20m=E1s,=20si=20usted=20hace=20u= so=20de=20esta=20incre=EDble=20oportunidad,=20adem=E1s=20le=0D=0A=20=20= =20=20=20=20=20=20=20=20regalo=20un=2020%=20de=20descuento=20en=20al= imentos=20y=20bebidas=20en=20nuestro=0D=0A=20=20=20=20=20=20=20=20=20= =20restaurante. =20Los=20sabores=20delicios=20que=20probara=20ah=ED= ,=20ser=E1n=0D=0A=20=20=20=20=20=20=20=20=20=20inolvidables,=20cr=E9ame= !

=0D=0A=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20=20=20Para=0D=0A=20=20= =20=20=20=20=20=20=20=20m=E1s=20informaci=F3n,=20le=20mando=20nuestras=20= direcciones=20electr=F3nicas,=20s=F3lo=0D=0A=20=20=20=20=20=20=20=20=20= =20en=20el=20caso=20de=20que=20se=20interese=20por=20la=20oferta=20que=20= le=20he=20hecho.

=0D=0A=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20= =20=20Si=0D=0A=20=20=20=20=20=20=20=20=20=20quiere=20usar=20el=20beneficio= ,=20por=20favor=20indique=20el=20codigo=20que=20sigue=20para=0D=0A=20=20= =20=20=20=20=20=20=20=20hacer=20v=E1lida=20esta=20oferta:

=0D= =0A=20=20=20=20=20=20=20=20=20=20<= font=20=0D=0Asize=3D"2">fRpromo0802

=0D=0A=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20Vigencia=20de=20la=20promoci=F3n:=20de=20Agosto=0D=0A=20=20=20=20=20= =20=20=2015=20a=20Diciembre=2015=20del=202001;=20se=20excluye=20la=20se= mana=20de=20Thanksgiving=20(Festividad=0D=0A=20=20=20=20=20=20=20=20en=20= EE.UU.)

=0D=0A=20=20=20=20=20=20
=0D=0A=20=20=20=20= =20=20=20=20=20=20Web=20Sites:
=0D=0A=20=20=20=20=20=20=20=20=20=20ww= w.elrancho.com.mx

=0D=0A=20=20=20=20=20=20=20=20=20= =20www.elranchovillas.com<= /p>=0D=0A=20=20=20=20=20=20=20=20=20=20e-mail:
=0D=0A=20=20=20=20=20= =20=20=20=20=20info@elrancho.com.mx=0D=0A=20=20=20= =20=20=20=20=20= =0D=0A=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20= =0D=0A=20=20=20=20=20=20=20=20=20= =20=0D=0A=20=20=20=20=20=20=20=20= =20=20=0D=0A=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20Reservaciones:
=0D=0A=20=20=20=20=20= =20=20=20=20=20Tel:=20(1)716-0606
=0D=0A=20=20=20=20=20=20=20=20=20=20= Fax: =20(1)716-9777
=0D=0A=20=20=20=20=20=20=20=20=20=20= =0D=0A=20=20=20=20=20=20=20=20=20=20M=E9xico:
=0D=0A=20=20=20=20=20=20=20=20= =20=2001-800-717-1991
=0D=0A=20=20=20=20=20=20=20=20=20=20=0D= =0A=20=20=20=20=20=20=20=20=20=20US=20&=20Canada:
=0D=0A=20=20=20=20=20=20=20= =20=20=201-888-596-5760=0D=0A=20=20=20=20=20=20=0D= =0A=20=20=20=20=20=20=0D=0A=20=20=20=20<= font=20size=3D"1">Para=20ser=20removido=20de=20nuestra=20lista=20de=0D=0A= =20=20=20=20correo,=20por=20favor=20env=EDenos=20un=20email=20en=20blan= co=20a=20la=20siguiente=20direcci=F3n=0D=0A=20=20=20=20electr=F3nica=20= :=20promo@elrancho.com.mx,=0D=0A=20=20=20=20con=20la=20palabra=20REMOVE=20en=20la=20linea=20de=20= Asunto=20(subject).

=0D=0A=20=20=20=20=0D=0A=20=20=0D= =0A=0D=0A=0D=0A=0D=0A=0D=0AThe=20message=20sent=20= by=20MailList=20Express=203.70=20=20=20Registered=20Version=20(Download= =20from=20http://Internet-Soft.com)=0D=0A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 2 18:29: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 13F3437B401 for ; Thu, 2 Aug 2001 18:29:07 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f731Sva01131; Fri, 3 Aug 2001 10:28:57 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: current@FreeBSD.org In-Reply-To: <20010802165913.A9883@caramba.cs.tu-berlin.de> References: <20010802165913.A9883@caramba.cs.tu-berlin.de> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V 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: 9 From: Makoto MATSUSHITA To: wosch@cs.tu-berlin.de Subject: Re: no new snapshot on ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/ Date: Fri, 03 Aug 2001 10:27:26 +0900 Message-Id: <20010803102726M.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG wosch> What happens? Is -current now so unstable that we cannot make a wosch> snapshot anymore? current.jp.FreeBSD.org is for you until current.freebsd.org is back again; it's not a *mirror*, but has almost same features. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 2 20:44:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 227A337B401 for ; Thu, 2 Aug 2001 20:44:39 -0700 (PDT) (envelope-from imp@harmony.village.org) 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 f733ibF01801; Thu, 2 Aug 2001 21:44:37 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f733iSH61472; Thu, 2 Aug 2001 21:44:35 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200108030344.f733iSH61472@harmony.village.org> To: Hajimu UMEMOTO Subject: Re: IPSEC/IPSEC_ESP module(s) Cc: kris@obsecurity.org, huntting@glarp.com, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 03 Aug 2001 02:25:56 +0900." <20010803.022556.45460869.ume@mahoroba.org> References: <20010803.022556.45460869.ume@mahoroba.org> <200107312255.f6VMtrQ37734@hunkular.glarp.com> <20010802025754.B94031@xor.obsecurity.org> Date: Thu, 02 Aug 2001 21:44:27 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010803.022556.45460869.ume@mahoroba.org> Hajimu UMEMOTO writes: : >>>>> On Thu, 2 Aug 2001 02:57:55 -0700 : >>>>> Kris Kennaway said: : : kris> On Tue, Jul 31, 2001 at 04:55:53PM -0600, huntting@glarp.com wrote: : > : > Has anyone attempted to make a loadable module out of IPSEC yet? : : kris> I doubt it would be possible: it has hooks all through the network : kris> code. : : Is there any chance to enable IPSEC in GENERIC? I'd love to do that, but it would have to be removed for the install disks. The kernel already is too fat for them :-( Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 2 21:10:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from mx3.163.com (unknown [202.108.44.220]) by hub.freebsd.org (Postfix) with ESMTP id CFE8337B403 for ; Thu, 2 Aug 2001 21:10:46 -0700 (PDT) (envelope-from sukenwoo@163.com) Received: by mx3.163.com (Postfix, from userid 60001) id 334541D2BC908; Fri, 3 Aug 2001 12:04:41 +0800 (CST) MIME-Version: 1.0 Message-Id: <3B6A22D9.09375@bj220.163.com> Date: Fri, 3 Aug 2001 12:04:41 +0800 (CST) From: "sukenwoo" To: freebsd-current@freebsd.org Subject: X-Priority: 3 X-Originating-IP: [210.77.118.103] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG dear I had been upgrade my system from BSD4.3-RELEASE to BSD5.0-CURRENT but I found fatal question that is my 3c905B & AHA2940 maybe use the same irq(14).As this my 3c905B do nothing. How can i do? Can't thankful enougth to you! Also I found I could not use su . suken =================================================== http://sms.163.com ÍøÒ׶ÌÐÅ ·¢×ÔÄÚÐÄ http://love.163.com Ç£ÒÁÖ®ÊÖ¹²ÏíÈËÉú»¶Ó飡NEW£¡ http://alumni.163.com ±ÌÔÆÌ죬»ÆÒ¶µØ£¬Ð£Ô°Ç黳ÒÀÈçÎô To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 2 23:52:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id 26D6C37B401 for ; Thu, 2 Aug 2001 23:52:21 -0700 (PDT) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.51.214]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "caerdonn.eurocontrol.fr", Issuer CN "CA ITM" (verified OK)) by matrix.eurocontrol.fr (Postfix/TLS) with ESMTP id 6E6B65BAB for ; Fri, 3 Aug 2001 08:52:20 +0200 (CEST) Received: by caerdonn.eurocontrol.fr (Postfix/TLS, from userid 1193) id 786C830; Fri, 3 Aug 2001 08:52:19 +0200 (CEST) Date: Fri, 3 Aug 2001 08:52:19 +0200 From: Ollivier Robert To: FreeBSD Current Users' list Subject: Re: ntpd 4.1 Message-ID: <20010803085219.A26202@caerdonn.eurocontrol.fr> Mail-Followup-To: Ollivier Robert , FreeBSD Current Users' list References: <200108021307.f72D7dr07962@grimreaper.grondar.za> <87333.996785184@axl.seasidesoftware.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <87333.996785184@axl.seasidesoftware.co.za>; from sheldonh@starjuice.net on Thu, Aug 02, 2001 at 10:46:24PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG According to Sheldon Hearn: > Unless David Mills can be convinced to manage his documentation in a > sensible fashion, this will be the last upgrade for which I'll be doing > HTML -> mdoc transcription. Don't hold your breath then, he repeated two days ago he didn't want to change the way he manages the documentation. -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- Ollivier.Robert@eurocontrol.fr FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #46: Wed Jan 3 15:52:00 CET 2001 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 1:15: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id E303137B405 for ; Fri, 3 Aug 2001 01:15:04 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15Sa6d-000FFg-00; Fri, 03 Aug 2001 10:14:51 +0200 From: Sheldon Hearn To: Warner Losh Cc: Hajimu UMEMOTO , kris@obsecurity.org, huntting@glarp.com, freebsd-current@FreeBSD.ORG Subject: Re: IPSEC/IPSEC_ESP module(s) In-reply-to: Your message of "Thu, 02 Aug 2001 21:44:27 CST." <200108030344.f733iSH61472@harmony.village.org> Date: Fri, 03 Aug 2001 10:14:51 +0200 Message-ID: <58631.996826491@axl.seasidesoftware.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 02 Aug 2001 21:44:27 CST, Warner Losh wrote: > I'd love to do that, but it would have to be removed for the install > disks. The kernel already is too fat for them :-( Have we come to a decision on when we're going to either drop floppy support or consider a different version of GENERIC for the CDROM installation? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 1:17:57 2001 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id A00E337B405 for ; Fri, 3 Aug 2001 01:17:53 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15SaAT-000FHB-00; Fri, 03 Aug 2001 10:18:49 +0200 From: Sheldon Hearn To: Ollivier Robert Cc: FreeBSD Current Users' list Subject: Re: ntpd 4.1 In-reply-to: Your message of "Fri, 03 Aug 2001 08:52:19 +0200." <20010803085219.A26202@caerdonn.eurocontrol.fr> Date: Fri, 03 Aug 2001 10:18:49 +0200 Message-ID: <58724.996826729@axl.seasidesoftware.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 03 Aug 2001 08:52:19 +0200, Ollivier Robert wrote: > > Unless David Mills can be convinced to manage his documentation in a > > sensible fashion, this will be the last upgrade for which I'll be doing > > HTML -> mdoc transcription. > > Don't hold your breath then, he repeated two days ago he didn't want to > change the way he manages the documentation. I hold my breath for very little, these days. :-) What blows my mind is that he's not even willing to use slightly more translatable markup. He's just totally anti anything other than his own paradigm, which is that local documentation is dead and the web is the only place to put it. *mutter* Ciao, Sheldon. Sheldon Hearn Prime Apostle of the Church of Disillusioned Saints To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 1:39:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 3938E37B403 for ; Fri, 3 Aug 2001 01:39:25 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f738flk01101; Fri, 3 Aug 2001 01:41:48 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108030841.f738flk01101@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "neckpain@nettaxi.com" Cc: haro@h4.dion.ne.jp, current@freebsd.org Subject: Re: acpica malfunctions In-reply-to: Your message of "Mon, 30 Jul 2001 09:00:18 PDT." <200107301600.JAA12157@mail3.bigmailbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Aug 2001 01:41:47 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks; committed. I really appreciate the help! Regards, Mike -- ... 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-current" in the body of the message From owner-freebsd-current Fri Aug 3 2:28:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from TELE23 (marketlinksolutions.com.au [203.49.3.65]) by hub.freebsd.org (Postfix) with SMTP id 20BAE37B401 for ; Fri, 3 Aug 2001 02:28:39 -0700 (PDT) (envelope-from montage@marketlinksolutions.com.au) From: montage@marketlinksolutions.com.au To: current@freebsd.org Subject: Investors and Collectors of Militaria Mime-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Date: Fri, 3 Aug 2001 19:29:50 Message-Id: <20010803092839.20BAE37B401@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Untitled Document

Investors and Collectors of Militaria

Endorsed and signed by the Australian Chief of Army
Lieutenant General Peter Cosgrove

For information and to order

Opportunities for organisations

Remove me from list
To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 2:31: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 935FA37B405; Fri, 3 Aug 2001 02:31:07 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f739XTg00741; Fri, 3 Aug 2001 02:33:30 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108030933.f739XTg00741@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Daniel Rock Cc: Mike Smith , current@freebsd.org Subject: Re: ACPI: Clock problems in -current In-reply-to: Your message of "Wed, 01 Aug 2001 21:00:06 +0200." <3B6851B6.4BD4EDD7@t-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Aug 2001 02:33:29 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I forgot: Even if I define CLK_USE_*_CALIBRATION (and get no error messages > after defining debug.acpi.timer_test), the Off/2 error still persist. Ok. I'm going to revert to the "safe" read code in a few minutes. Can you update and let me know if you're still wildly off? I'm having a hard time believing that your timer is really running at double pace, but I guess anything is possible. If it still does, I'll add some code to check it with the TSC. -- ... 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-current" in the body of the message From owner-freebsd-current Fri Aug 3 2:54:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 8C5C837B405; Fri, 3 Aug 2001 02:54:27 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f739urg01026; Fri, 3 Aug 2001 02:56:53 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108030956.f739urg01026@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: current@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/acpica acpi_pcib.c In-reply-to: Your message of "Fri, 03 Aug 2001 01:38:49 PDT." <200108030838.f738cnV49578@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Aug 2001 02:56:53 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This should fix problems people were having with PCI interrupt routing and ACPI. Please report any problems... > msmith 2001/08/03 01:38:49 PDT > > Modified files: > sys/dev/acpica acpi_pcib.c > Log: > Shoud build resources in the _CRS buffer. Oops. > > Submitted by: "neckpain@nettaxi.com" > > Revision Changes Path > 1.13 +2 -2 src/sys/dev/acpica/acpi_pcib.c > > -- ... 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-current" in the body of the message From owner-freebsd-current Fri Aug 3 3: 5: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 4558137B405 for ; Fri, 3 Aug 2001 03:05:02 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f73A7Rg01452 for ; Fri, 3 Aug 2001 03:07:27 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108031007.f73A7Rg01452@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: HEADS UP: ACPI changes Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Aug 2001 03:07:26 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've made a couple of minor changes to the ACPI code: - Fixed (hopefully) PCI interrupt routing, thanks to neckpain@nettaxi.com who was able to actually test (and correct) my code. - Changed the way ACPI timers are treated to be more pessimistic. It looks like we can't assume that the average ACPI timer is properly implemented. This is a pain; a "good" timer takes about 350 cycles to read on my PIII/500 laptop, wheras the "safe" read takes about 1050 cycles. (~700ns vs. 2us respectively). The code will still optimise if a known-good timer is detected. To test your ACPI timer, first check to see which one you have. Look at the output of 'pciconf -lv'. If you have an Intel chipset, chances are that we already know about it, and the code will do the right thing. For example: none0@pci0:7:3: class=0x068000 card=0x00000000 chip=0x71138086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82371AB PIIX4 Power Management Controller' class = bridge subclass = PCI-unknown This is the PIIX4M, (rev=0x03), known to be reliable. If you have a non-Intel chipset and you want to try it out, say set debug.acpi.timer_test="yes" at the loader prompt, then boot. If your timer has problems, you should see messages like: acpi_timer0: timer is not monotonic: 0x1d52ab4f,0x1d52ab4e,0x1d5b89ea being displayed at random intervals. If after several minutes you do not see any of these messages, please send me the output of 'pciconf -lv' and I'll see whether we can safely detect your ACPI timer. Regards, Mike -- ... 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-current" in the body of the message From owner-freebsd-current Fri Aug 3 5: 9:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 3558737B405 for ; Fri, 3 Aug 2001 05:09:17 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15SdmQ-0005Hy-00; Fri, 03 Aug 2001 14:10:14 +0200 From: Sheldon Hearn To: Ollivier Robert Cc: freebsd-current@FreeBSD.ORG Subject: Re: ntpd 4.1 In-reply-to: Your message of "Fri, 03 Aug 2001 10:18:49 +0200." <58724.996826729@axl.seasidesoftware.co.za> Date: Fri, 03 Aug 2001 14:10:14 +0200 Message-ID: <20333.996840614@axl.seasidesoftware.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 03 Aug 2001 10:18:49 +0200, Sheldon Hearn wrote: > > Don't hold your breath then, he repeated two days ago he didn't want to > > change the way he manages the documentation. By the way... How on earth does David Mills expect translators to work on NTP documentation? I've just realized that the upcoming changes to the NTP docs are going to force _every_ translation team that's worked on the NTP pages to redo all their work, or abandon it entirely. So let me guess. Not only does Mills think that the web is the only sensible distribution medium for documentation, he also thinks that English is the only sensible language for it? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 7:59:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by hub.freebsd.org (Postfix) with ESMTP id 356D437B405 for ; Fri, 3 Aug 2001 07:59:30 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id QAA27529; Fri, 3 Aug 2001 16:59:28 +0200 (CEST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.4/8.11.4) id f73ExMF05899; Fri, 3 Aug 2001 16:59:22 +0200 (CEST) (envelope-from wkb) Date: Fri, 3 Aug 2001 16:59:22 +0200 From: Wilko Bulte To: Sheldon Hearn Cc: Warner Losh , Hajimu UMEMOTO , kris@obsecurity.org, huntting@glarp.com, freebsd-current@FreeBSD.ORG Subject: Re: IPSEC/IPSEC_ESP module(s) Message-ID: <20010803165922.B5749@freebie.xs4all.nl> References: <200108030344.f733iSH61472@harmony.village.org> <58631.996826491@axl.seasidesoftware.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <58631.996826491@axl.seasidesoftware.co.za>; from sheldonh@starjuice.net on Fri, Aug 03, 2001 at 10:14:51AM +0200 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Aug 03, 2001 at 10:14:51AM +0200, Sheldon Hearn wrote: > > > On Thu, 02 Aug 2001 21:44:27 CST, Warner Losh wrote: > > > I'd love to do that, but it would have to be removed for the install > > disks. The kernel already is too fat for them :-( > > Have we come to a decision on when we're going to either drop floppy > support or consider a different version of GENERIC for the CDROM > installation? FWIW: the alpha is suffering from exactly the same problem. There a 3 (or more) floppy install set was proposed. Wilko -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 8:50:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from unifran.br (unifram-097.ctbctelecom.com.br [200.225.217.97]) by hub.freebsd.org (Postfix) with ESMTP id 102D337B406 for ; Fri, 3 Aug 2001 08:50:24 -0700 (PDT) (envelope-from eeviac@fatectq.com.br) Received: from artsom.fatectq.com.br ([200.210.70.155]) by unifran.br (8.8.8/8.8.8) with ESMTP id MAA12231 for ; Fri, 3 Aug 2001 12:51:44 -0300 (EST) (envelope-from eeviac@fatectq.com.br) Message-Id: <5.1.0.14.0.20010803053447.00a10560@200.210.2.10> X-Sender: eeviac@200.210.2.10 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 03 Aug 2001 05:54:56 -0300 To: freebsd-current@FreeBSD.ORG From: ":: Patrick Tracanelli ::" Subject: Keeping User Database loaded in Mem Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello you all; I want to know if there is a working way to keep FreeBSD's user database loaded in memory. The reason's for that is very clear, if i keep my spwd.db loaded the access to it won't be a disk access, so this will speedup any forms of authentication... The reason is that i want to avoid SQL databases in some cases where the system database works better to me. I have calculated that a database amount of 3000 (+/-) users would need about 7.6MB of memory, what sounds very good to me... If there isn't a way to it, yet, that is something i would love to see when -CURRENT becomes -RELEASE... it's an idea :) Best Regards Peace []'z Eksffa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 9:42:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251]) by hub.freebsd.org (Postfix) with ESMTP id D6C9837B407 for ; Fri, 3 Aug 2001 09:42:15 -0700 (PDT) (envelope-from huntting@hunkular.glarp.com) Received: from hunkular.glarp.com (localhost [127.0.0.1]) by hunkular.glarp.com (8.11.3/8.11.3) with ESMTP id f73GeOQ56280; Fri, 3 Aug 2001 10:40:24 -0600 (MDT) (envelope-from huntting@hunkular.glarp.com) Message-Id: <200108031640.f73GeOQ56280@hunkular.glarp.com> To: Sheldon Hearn Cc: Warner Losh , Hajimu UMEMOTO , kris@obsecurity.org, huntting@glarp.com, freebsd-current@FreeBSD.ORG Subject: Re: IPSEC/IPSEC_ESP module(s) In-Reply-To: Your message of "Fri, 03 Aug 2001 10:14:51 +0200." <58631.996826491@axl.seasidesoftware.co.za> Date: Fri, 03 Aug 2001 10:40:24 -0600 From: Brad Huntting Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Have we come to a decision on when we're going to either drop floppy > support or consider a different version of GENERIC for the CDROM > installation? Along the lines of droping floppy support: I just managed to setup a DHCP/TFTP/NFS diskless boot server that boots the floppy install images. Unfortunatly, it did require nfs. So even if floppy install is discontinued, it would be very nice to have support for installing from PXE. If anyone wants details let me know off-line. brad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 9:52:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from ghostwheel.tribble.net (ghostwheel.tribble.net [206.124.26.66]) by hub.freebsd.org (Postfix) with ESMTP id EE96C37B401 for ; Fri, 3 Aug 2001 09:52:27 -0700 (PDT) (envelope-from tribble@tribble.net) Received: (from tribble@localhost) by ghostwheel.tribble.net (8.11.3/8.11.1) id f73GqRo69298 for current@freebsd.org; Fri, 3 Aug 2001 10:52:27 -0600 (MDT) (envelope-from tribble@tribble.net) Date: Fri, 3 Aug 2001 10:52:27 -0600 From: Paul To: current@freebsd.org Subject: quick query Message-ID: <20010803105227.A69204@tribble.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG sorry to bug this list with this question. I'd like to test the newer ray(4) driver that's in -CURRENT. What snapshot should I install? Is there anything else I should know before installing -CURRENT? (besides what the "cutting edge" section of the handbook says) Regards, Paul http://www.tribble.net/ "A free society is one where it is safe to be unpopular." -- Adlai Stevenson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 10:39:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 4553D37B401 for ; Fri, 3 Aug 2001 10:39:35 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15Siut-0006OK-00; Fri, 03 Aug 2001 19:39:19 +0200 From: Sheldon Hearn To: Brad Huntting Cc: Warner Losh , Hajimu UMEMOTO , kris@obsecurity.org, freebsd-current@FreeBSD.ORG Subject: Re: IPSEC/IPSEC_ESP module(s) In-reply-to: Your message of "Fri, 03 Aug 2001 10:40:24 CST." <200108031640.f73GeOQ56280@hunkular.glarp.com> Date: Fri, 03 Aug 2001 19:39:19 +0200 Message-ID: <24571.996860359@axl.seasidesoftware.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 03 Aug 2001 10:40:24 CST, Brad Huntting wrote: > > Have we come to a decision on when we're going to either drop floppy > > support or consider a different version of GENERIC for the CDROM > > installation? > > Along the lines of droping floppy support: I just managed to setup > a DHCP/TFTP/NFS diskless boot server that boots the floppy install > images. Unfortunatly, it did require nfs. I take it from all the peripheral postings that the answer to my questions is "no". :-) I wonder how we even begin to decide such a thing. By the way, even if floppy support is not discontinued, there's nothing holding back the development of more flexible non-floppy kernel arrangements. Perhaps that's the route to take, before we even think about dropping floppies. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 10:46:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id C1B5137B406 for ; Fri, 3 Aug 2001 10:46:13 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA51920; Fri, 3 Aug 2001 12:48:42 -0700 (PDT) Date: Fri, 3 Aug 2001 12:48:41 -0700 (PDT) From: Julian Elischer To: ":: Patrick Tracanelli ::" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Keeping User Database loaded in Mem In-Reply-To: <5.1.0.14.0.20010803053447.00a10560@200.210.2.10> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG use one of the client/server authentication methods and write the server part in a way that it keeps it in memory (of course the user database is usually in cache if you are doing a lot of authentication) On Fri, 3 Aug 2001, :: Patrick Tracanelli :: wrote: > > > Hello you all; > I want to know if there is a working way to keep FreeBSD's user database > loaded in memory. The reason's for that is very clear, if i keep my spwd.db > loaded the access to it won't be a disk access, so this will speedup any > forms of authentication... > > The reason is that i want to avoid SQL databases in some cases where the > system database works better to me. I have calculated that a database > amount of 3000 (+/-) users would need about 7.6MB of memory, what sounds > very good to me... > > If there isn't a way to it, yet, that is something i would love to see when > -CURRENT becomes -RELEASE... it's an idea :) > > Best Regards > Peace []'z Eksffa > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 11: 2:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 581EE37B40A for ; Fri, 3 Aug 2001 11:02:10 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id E27D081D0A; Fri, 3 Aug 2001 13:01:44 -0500 (CDT) Date: Fri, 3 Aug 2001 13:01:44 -0500 From: Alfred Perlstein To: ":: Patrick Tracanelli ::" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Keeping User Database loaded in Mem Message-ID: <20010803130144.B85642@elvis.mu.org> References: <5.1.0.14.0.20010803053447.00a10560@200.210.2.10> 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.0.20010803053447.00a10560@200.210.2.10>; from eeviac@fatectq.com.br on Fri, Aug 03, 2001 at 05:54:56AM -0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * :: Patrick Tracanelli :: [010803 10:51] wrote: > > > Hello you all; > I want to know if there is a working way to keep FreeBSD's user database > loaded in memory. The reason's for that is very clear, if i keep my spwd.db > loaded the access to it won't be a disk access, so this will speedup any > forms of authentication... > > The reason is that i want to avoid SQL databases in some cases where the > system database works better to me. I have calculated that a database > amount of 3000 (+/-) users would need about 7.6MB of memory, what sounds > very good to me... > > If there isn't a way to it, yet, that is something i would love to see when > -CURRENT becomes -RELEASE... it's an idea :) The filesystem cache should keep the database in memory as long as there is no pressure on the cache, otherwise it may evict the file. If you _really_ want to keep it in memory what I would suggest is writing a daemon that monitors the size of the file and keeps it both mmap(2)'s and mlocked(2), this would be trivial to do and would force the system to keep the file in memory. -- -Alfred Perlstein [alfred@freebsd.org] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 11:28: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from gateway.symark.com (firewall.symark.westlake.iswest.net [207.178.203.34]) by hub.freebsd.org (Postfix) with ESMTP id AB0C137B410 for ; Fri, 3 Aug 2001 11:28:01 -0700 (PDT) (envelope-from ggross@symark.com) Received: (from mailer@localhost) by gateway.symark.com (8.9.3/8.9.3) id LAA01467; Fri, 3 Aug 2001 11:28:01 -0700 Received: from camel.symark.com(128.1.1.97) by gateway.symark.com via smap (V2.1+anti-relay+anti-spam) id xma001455; Fri, 3 Aug 01 11:27:35 -0700 Received: by localhost with Microsoft MAPI; Fri, 3 Aug 2001 11:28:10 -0700 Message-ID: <01C11C0F.5FFB33B0.ggross@symark.com> From: Glen Gross Reply-To: "ggross@symark.com" To: "'Sheldon Hearn'" , Brad Huntting Cc: Warner Losh , Hajimu UMEMOTO , "kris@obsecurity.org" , "freebsd-current@FreeBSD.ORG" Subject: !RE: IPSEC/IPSEC_ESP module(s) Date: Fri, 3 Aug 2001 11:28:09 -0700 Organization: Symark Software X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This gives me the opportunity to ask a question I have been wondering for a while... I've been building kernels with IPSEC support and was unclear what kind of load this puts on the system by default. If IPSEC has hooks into all the networking code, does this become an issue on slow or otherwise heavily loaded hardware? Currently I am running FreeBSD 4.2 [not current] on my NFS server. Is IPSEC desirable in this configuration or not? [I'm behind a firewall.] Also, I can't decide whether to comment out the IPv6 code or not in the kernel configuration file. I would like to support the new protocols, but don't want to unnecessarily burdon the system. My NFS server [on my home network] is working like a champ with only 48 megs of RAM (!). I am using it to mount my home directories. The reason this comes up for me is that someone from SSH Communications recently told me that "IPSEC supports IPv6." Does this mean that if I enable IPSEC in the kernel, I should also make sure to enable the IPv6 code? I would deeply appreciate it if someone could shed some light on this subject for me. Regards, On Friday, August 03, 2001 10:39 AM, Sheldon Hearn [SMTP:sheldonh@starjuice.net] wrote: > > > On Fri, 03 Aug 2001 10:40:24 CST, Brad Huntting wrote: > > > > Have we come to a decision on when we're going to either drop floppy > > > support or consider a different version of GENERIC for the CDROM > > > installation? > > > > Along the lines of droping floppy support: I just managed to setup > > a DHCP/TFTP/NFS diskless boot server that boots the floppy install > > images. Unfortunatly, it did require nfs. > > I take it from all the peripheral postings that the answer to my > questions is "no". :-) > > I wonder how we even begin to decide such a thing. > > By the way, even if floppy support is not discontinued, there's nothing > holding back the development of more flexible non-floppy kernel > arrangements. Perhaps that's the route to take, before we even think > about dropping floppies. > > Ciao, > Sheldon. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Glen M. Gross Unix Technical Support Specialist Symark Software 5716 Corsa Avenue, Suite 200 Westlake Village, CA 91362 http://www.symark.com pp-support@symark.com pb-support@symark.com Main: 800-234-9072 or 818-865-6100 Main fax: 818-889-1894 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 13:11:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id BD68F37B406 for ; Fri, 3 Aug 2001 13:11:48 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id GAA01467; Sat, 4 Aug 2001 06:11:25 +1000 Date: Sat, 4 Aug 2001 06:08:58 +1000 (EST) From: Bruce Evans X-X-Sender: To: David Greenman Cc: Will Andrews , Christian Weisgerber , Subject: Re: What's touching my executables? In-Reply-To: <20010802153808.A62297@nexus.root.com> Message-ID: <20010804060030.R13873-100000@besplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, David Greenman wrote: > >On Thu, Aug 02, 2001 at 06:28:59PM +0000, Christian Weisgerber (naddy@mips.inka.de) wrote: > >Probably the recent change (IIRC) that someone turned running an > >executable into a mtime change. > > There was no such change. I proposed a change that would update the atime, > but that was not committed because it has some bad side effects. I didn't see that. I saw when you objected to me fixing the bug many years ago :-). The atime update was too slow for executables on nfs filesystems. I only used it to reduce the number of non-conformances found by the NIST Posix test suite. There is now a PR about this bug (kern/25777) with a very broken patch in it (it assume that all filesystems are ufs and hacks on ufs's IN_ACCESS flag). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 14:18:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from root.com (unknown [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 794A437B406 for ; Fri, 3 Aug 2001 14:18:43 -0700 (PDT) (envelope-from dg@root.com) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id f73L4Jq67199; Fri, 3 Aug 2001 14:04:19 -0700 (PDT) (envelope-from dg) Date: Fri, 3 Aug 2001 14:04:19 -0700 From: David Greenman To: Bruce Evans Cc: Will Andrews , Christian Weisgerber , freebsd-current@FreeBSD.ORG Subject: Re: What's touching my executables? Message-ID: <20010803140419.E62297@nexus.root.com> References: <20010802153808.A62297@nexus.root.com> <20010804060030.R13873-100000@besplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010804060030.R13873-100000@besplex.bde.org>; from bde@zeta.org.au on Sat, Aug 04, 2001 at 06:08:58AM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >On Thu, 2 Aug 2001, David Greenman wrote: > >> >On Thu, Aug 02, 2001 at 06:28:59PM +0000, Christian Weisgerber (naddy@mips.inka.de) wrote: >> >Probably the recent change (IIRC) that someone turned running an >> >executable into a mtime change. >> >> There was no such change. I proposed a change that would update the atime, >> but that was not committed because it has some bad side effects. > >I didn't see that. I saw when you objected to me fixing the bug many >years ago :-). The atime update was too slow for executables on nfs >filesystems. I only used it to reduce the number of non-conformances >found by the NIST Posix test suite. There is now a PR about this bug >(kern/25777) with a very broken patch in it (it assume that all >filesystems are ufs and hacks on ufs's IN_ACCESS flag). I tried to fix the problem in the VOP_OPEN (specifically, ufs_open), since it seemed reasonable at the time that an open should be considered an 'access'. Unfortunately it was pointed out that this would break some things like 'mail unread since...', which depends on open/writes/close with no reads to not change the access time on the user's mail spool file. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 15: 0:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id C206437B407 for ; Fri, 3 Aug 2001 15:00:20 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15SmzH-0006rV-00; Sat, 04 Aug 2001 00:00:07 +0200 From: Sheldon Hearn To: "ggross@symark.com" Cc: Brad Huntting , Warner Losh , Hajimu UMEMOTO , "kris@obsecurity.org" , "freebsd-current@FreeBSD.ORG" Subject: Re: !RE: IPSEC/IPSEC_ESP module(s) In-reply-to: Your message of "Fri, 03 Aug 2001 11:28:09 MST." <01C11C0F.5FFB33B0.ggross@symark.com> Date: Sat, 04 Aug 2001 00:00:07 +0200 Message-ID: <26380.996876007@axl.seasidesoftware.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 03 Aug 2001 11:28:09 MST, Glen Gross wrote: > The reason this comes up for me is that someone from SSH Communications > recently told me that "IPSEC supports IPv6." Does this mean > that if I enable IPSEC in the kernel, I should also make sure to enable the > IPv6 code? I would deeply appreciate it > if someone could shed some light on this subject for me. Do you use IPv6 address space to address your host? If so, enable INET6. Do you use IP-layer encryption for services offered or used by your host? If so, enable IPSEC. I realize this sounds facetious, but it's really as simple as that. If you need it, you need it. Otherwise, you don't. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 19:10:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from citusc17 (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 894D737B406 for ; Fri, 3 Aug 2001 19:10:46 -0700 (PDT) (envelope-from kris@citusc17) Received: (from kris@localhost) by citusc17 (8.11.4/8.11.4) id f742AQo12534; Fri, 3 Aug 2001 19:10:27 -0700 (PDT) (envelope-from kris) Date: Fri, 3 Aug 2001 19:10:26 -0700 From: Kris Kennaway To: Glen Gross Cc: "'Sheldon Hearn'" , Brad Huntting , Warner Losh , Hajimu UMEMOTO , "kris@obsecurity.org" , "freebsd-current@FreeBSD.ORG" Subject: Re: !RE: IPSEC/IPSEC_ESP module(s) Message-ID: <20010803191026.A12509@citusc17.usc.edu> References: <01C11C0F.5FFB33B0.ggross@symark.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01C11C0F.5FFB33B0.ggross@symark.com>; from ggross@symark.com on Fri, Aug 03, 2001 at 11:28:09AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 03, 2001 at 11:28:09AM -0700, Glen Gross wrote: > This gives me the opportunity to ask a question I have been wondering for= a=20 > while... I've been building kernels with IPSEC support > and was unclear what kind of load this puts on the system by default. If= IPSEC=20 > has hooks into all the networking code, does this > become an issue on slow or otherwise heavily loaded hardware? Currently = I am=20 I wouldn't expect it to be a significant issue. > The reason this comes up for me is that someone from SSH Communications= =20 > recently told me that "IPSEC supports IPv6." Does this mean > that if I enable IPSEC in the kernel, I should also make sure to enable t= he=20 > IPv6 code? I would deeply appreciate it > if someone could shed some light on this subject for me. IPSEC supports IPv4 as well :-) The comment just means that it works with both. Kris --lrZ03NoBR/3+SXJZ 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 iD8DBQE7a1mSWry0BWjoQKURAhfBAKCm2vgnbsMyWqn/NKpXpmnwsTGiogCfdd+f PpON2ToVfXuB9bxwEYugcgc= =BW8S -----END PGP SIGNATURE----- --lrZ03NoBR/3+SXJZ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 19:21: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id AC93137B406 for ; Fri, 3 Aug 2001 19:21:04 -0700 (PDT) (envelope-from kuriyama@imgsrc.co.jp) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2:290:27ff:fe98:c0b7]) by white.imgsrc.co.jp (Postfix) with ESMTP id D6A2824D22 for ; Sat, 4 Aug 2001 11:21:03 +0900 (JST) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by black.imgsrc.co.jp (Postfix) with ESMTP id 73FEDD1401 for ; Sat, 4 Aug 2001 11:21:02 +0900 (JST) Date: Sat, 04 Aug 2001 11:21:01 +0900 Message-ID: <7mitg4lg4y.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Current Subject: named -u bind User-Agent: Wanderlust/2.6.0 (Twist And Shout) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-1?Q?Unebigory=F2mae?=) APEL/10.3 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: multipart/mixed; boundary="Multipart_Sat_Aug__4_11:21:01_2001-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --Multipart_Sat_Aug__4_11:21:01_2001-1 Content-Type: text/plain; charset=US-ASCII Are there any reasons not to use "-u bind" flag for named by default? # Or importing code to use chroot from OpenBSD? -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project --Multipart_Sat_Aug__4_11:21:01_2001-1 Content-Type: application/octet-stream; type=patch Content-Disposition: attachment; filename="bind.diff" Content-Transfer-Encoding: 7bit Index: defaults/rc.conf =================================================================== RCS file: /home/ncvs/src/etc/defaults/rc.conf,v retrieving revision 1.119 diff -u -r1.119 rc.conf --- defaults/rc.conf 2001/07/28 19:57:57 1.119 +++ defaults/rc.conf 2001/08/04 02:11:55 @@ -121,8 +121,7 @@ # named_enable="NO" # Run named, the DNS server (or NO). named_program="named" # path to named, if you want a different one. -named_flags="" # Flags for named -#named_flags="-u bind -g bind" # Flags for named +named_flags="-u bind -g bind" # Flags for named # # kerberos. Do not run the admin daemons on slave servers Index: mtree/BSD.var.dist =================================================================== RCS file: /home/ncvs/src/etc/mtree/BSD.var.dist,v retrieving revision 1.47 diff -u -r1.47 BSD.var.dist --- mtree/BSD.var.dist 2001/07/28 20:00:54 1.47 +++ mtree/BSD.var.dist 2001/08/04 02:10:08 @@ -55,6 +55,8 @@ preserve .. run + named uname=bind gname=bind + .. .. rwho gname=daemon mode=0775 .. Index: namedb/named.conf =================================================================== RCS file: /home/ncvs/src/etc/namedb/named.conf,v retrieving revision 1.9 diff -u -r1.9 named.conf --- namedb/named.conf 2001/05/28 13:43:26 1.9 +++ namedb/named.conf 2001/08/04 02:07:54 @@ -8,6 +8,7 @@ options { directory "/etc/namedb"; + pid-file "/var/run/named/pid"; // In addition to the "forwarders" clause, you can force your name // server to never initiate queries of its own, but always ask its --Multipart_Sat_Aug__4_11:21:01_2001-1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 19:51:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 7397837B406 for ; Fri, 3 Aug 2001 19:51:30 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id CB17D3E28; Fri, 3 Aug 2001 19:50:29 -0700 (PDT) Received: from bazooka.unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id AEBE63C12C; Fri, 3 Aug 2001 19:50:29 -0700 (PDT) To: Jun Kuriyama Cc: Current Subject: Re: named -u bind In-Reply-To: <7mitg4lg4y.wl@waterblue.imgsrc.co.jp>; from kuriyama@imgsrc.co.jp on "Sat, 04 Aug 2001 11:21:01 +0900" Date: Fri, 03 Aug 2001 19:50:24 -0700 From: Dima Dorfman Message-Id: <20010804025029.CB17D3E28@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jun Kuriyama writes: > --Multipart_Sat_Aug__4_11:21:01_2001-1 > Content-Type: text/plain; charset=US-ASCII > > > Are there any reasons not to use "-u bind" flag for named by default? IIRC the last time this came up somebody said something about it not being able to read zonefiles in some odd places where they like to put them. I.e., they want it to run as root so they can set their zonefile mode 600 or something. > # Or importing code to use chroot from OpenBSD? Import code? BIND can run in a chroot just fine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 20: 0:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by hub.freebsd.org (Postfix) with ESMTP id 079ED37B401 for ; Fri, 3 Aug 2001 20:00:21 -0700 (PDT) (envelope-from kuriyama@imgsrc.co.jp) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2:290:27ff:fe98:c0b7]) by white.imgsrc.co.jp (Postfix) with ESMTP id 4A02024D21 for ; Sat, 4 Aug 2001 12:00:20 +0900 (JST) Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by black.imgsrc.co.jp (Postfix) with ESMTP id 67B10D1401 for ; Sat, 4 Aug 2001 12:00:17 +0900 (JST) Date: Sat, 04 Aug 2001 12:00:15 +0900 Message-ID: <7melqslebk.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Current Subject: Re: named -u bind In-Reply-To: <20010804025029.CB17D3E28@bazooka.unixfreak.org> References: <7mitg4lg4y.wl@waterblue.imgsrc.co.jp> <20010804025029.CB17D3E28@bazooka.unixfreak.org> User-Agent: Wanderlust/2.6.0 (Twist And Shout) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-1?Q?Unebigory=F2mae?=) APEL/10.3 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At Fri, 03 Aug 2001 19:50:24 -0700, Dima Dorfman wrote: > IIRC the last time this came up somebody said something about it not > being able to read zonefiles in some odd places where they like to put > them. I.e., they want it to run as root so they can set their > zonefile mode 600 or something. If they are running on -stable, is it possible to change default behaviour on -current to use bind account? # IMHO, it requires only to do "chown bind $zonefiles" so something... > > # Or importing code to use chroot from OpenBSD? > > Import code? BIND can run in a chroot just fine. Sorry for my poor explanation. This means to get a part of shell code in /etc/rc of OpenBSD to prepare chroot environment. This seems users can use chroot'ed named easily with only setting variables at /etc/rc.conf. -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 20: 4:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 240DC37B401 for ; Fri, 3 Aug 2001 20:04:51 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id 65C7B3E28; Fri, 3 Aug 2001 20:04:50 -0700 (PDT) Received: from bazooka.unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id 530CB3C12B; Fri, 3 Aug 2001 20:04:50 -0700 (PDT) To: Jun Kuriyama Cc: Current Subject: Re: named -u bind In-Reply-To: <7melqslebk.wl@waterblue.imgsrc.co.jp>; from kuriyama@imgsrc.co.jp on "Sat, 04 Aug 2001 12:00:15 +0900" Date: Fri, 03 Aug 2001 20:04:45 -0700 From: Dima Dorfman Message-Id: <20010804030450.65C7B3E28@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jun Kuriyama writes: > At Fri, 03 Aug 2001 19:50:24 -0700, > Dima Dorfman wrote: > > IIRC the last time this came up somebody said something about it not > > being able to read zonefiles in some odd places where they like to put > > them. I.e., they want it to run as root so they can set their > > zonefile mode 600 or something. > > If they are running on -stable, is it possible to change default > behaviour on -current to use bind account? Don't ask me, I wasn't one of those people. *I* won't object to this change; I was just warning you that somebody might, for that reason. > > > # Or importing code to use chroot from OpenBSD? > > > > Import code? BIND can run in a chroot just fine. > > Sorry for my poor explanation. This means to get a part of shell code > in /etc/rc of OpenBSD to prepare chroot environment. This seems users > can use chroot'ed named easily with only setting variables at > /etc/rc.conf. This seems like a good idea whether it's the default or not. The only thing is that something running in a chroot should be built statically, unless you also want to stick libc and friends in there. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 3 20: 6:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id DA32537B401 for ; Fri, 3 Aug 2001 20:06:50 -0700 (PDT) (envelope-from david@catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.4/8.11.4) id f7436j234166 for FreeBSD-current@FreeBSD.ORG; Fri, 3 Aug 2001 20:06:45 -0700 (PDT) Date: Fri, 3 Aug 2001 20:06:45 -0700 (PDT) From: David Wolfskill Message-Id: <200108040306.f7436j234166@bunrab.catwhisker.org> Subject: Re: named -u bind Cc: FreeBSD-current@FreeBSD.ORG In-Reply-To: <20010804025029.CB17D3E28@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Date: Fri, 03 Aug 2001 19:50:24 -0700 >From: Dima Dorfman >> Are there any reasons not to use "-u bind" flag for named by default? >IIRC the last time this came up somebody said something about it not >being able to read zonefiles in some odd places where they like to put >them. I.e., they want it to run as root so they can set their >zonefile mode 600 or something. That sounds like someone overdoesed on perversity. I've been running named with user & group "bind" (53) for nearly 2 years without significant problems: I made the directory named uses /var/namedb; everything in there is (still) owned by root, except for the "sec" subdirectory, which is owned by bind. (That is where the local copies of files retrieved from zone transfers go, for the zones for which my system is a slave. Having the named process unable to modify other files is a Good Thing. Oh, yeah: I also made /etc/named.conf a symlink to /var/namedb/named.conf.) I also made /var/run mode 1777, so that /var/run/named.pid could get created with minimal hassle. (Since the box has no general-purpose logins & no keyboard, I have reasonable confidence that a local user isn't likely to abuse this.) Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 7:34:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from elmls01.ce.mediaone.net (elmls01.ce.mediaone.net [24.131.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 7E1E137B406 for ; Sat, 4 Aug 2001 07:34:17 -0700 (PDT) (envelope-from p-sides@mediaone.net) Received: from plspc3 (el02-24-131-160-10.ce.mediaone.net [24.131.160.10]) by elmls01.ce.mediaone.net (8.8.7/8.8.7) with ESMTP id JAA11308 for ; Sat, 4 Aug 2001 09:34:16 -0500 (CDT) From: "Peter Sides" To: Date: Sat, 4 Aug 2001 09:34:32 -0500 Message-ID: <000501c11cf2$945e35b0$bfb4fea9@plspc3> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01C11CC8.AB882DB0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0006_01C11CC8.AB882DB0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Peter Sides ------=_NextPart_000_0006_01C11CC8.AB882DB0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

 

Peter = Sides

<= /font>

 

------=_NextPart_000_0006_01C11CC8.AB882DB0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 7:57: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id D2ABE37B403 for ; Sat, 4 Aug 2001 07:57:01 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id QAA46740; Sat, 4 Aug 2001 16:57:00 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Sat, 4 Aug 2001 16:57:00 +0200 (CEST) Message-Id: <200108041457.QAA46740@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: quick query In-Reply-To: <20010803105227.A69204@tribble.net> X-Newsgroups: list.freebsd-current User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Paul wrote: > sorry to bug this list with this question. I'd like to test the newer > ray(4) driver that's in -CURRENT. What snapshot should I install? Is > there anything else I should know before installing -CURRENT? (besides > what the "cutting edge" section of the handbook says) I just installed the latest snapshot available from current.freebsd.org (20010618, I think) and then went from there to the latest sources using CVSup. That was on Thursday evening. Buildworld etc. went without a problem, and the box (a dual Celeron-466) is running happily since then, with SMP enabled, Soft-updates and what-have-you. Of course you should read src/UPDATING and have an eye on this mailing list and on the commits. Regards Oliver PS: My reason to try out -current was the umass driver. I was hoping to get a USB-IDE box running, but it does not look like it's willing to work with FreeBSD. :( -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 9:17:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 104F737B403; Sat, 4 Aug 2001 09:17:32 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.4/8.11.1) id f74GH7r16514; Sat, 4 Aug 2001 09:17:07 -0700 (PDT) (envelope-from obrien) Date: Sat, 4 Aug 2001 09:17:06 -0700 From: "David O'Brien" To: Jens Schweikhardt Cc: Brian Fundakowski Feldman , current@FreeBSD.org Subject: Re: quick informal survey: OpenSSH broken? Message-ID: <20010804091706.A16365@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <200107300154.f6U1sPf39683@green.bikeshed.org> <20010731151358.D76404@dragon.nuxi.com> <20010801202114.D1320@schweikhardt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010801202114.D1320@schweikhardt.net>; from schweikh@schweikhardt.net on Wed, Aug 01, 2001 at 08:21:14PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Aug 01, 2001 at 08:21:14PM +0200, Jens Schweikhardt wrote: > On Tue, Jul 31, 2001 at 03:13:58PM -0700, David O'Brien wrote: > # On Tue, Jul 31, 2001 at 01:39:14PM -0400, Robert Watson wrote: > # > what was going on, and given that scp doesn't support -1, was a bit of a > # > pain. > # > # Brian, what about adding "-1" to SCP? > > I'm late in this thread, so I don't know what has been discussed before, > but if this means to use protocol version one, scp does this already > with > > scp -o Protocol=1 ... Yes, but that is a whole lot more to have to type than `scp -1', and since we want to encorage poeple to use ssh/scp and it is typed so often, it would be nice (and oroginal since ssh has it) to add -1 to scp. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 14: 3:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.gnf.org (firewall.gnf.org [208.44.31.34]) by hub.freebsd.org (Postfix) with ESMTP id 9B96637B401 for ; Sat, 4 Aug 2001 14:03:13 -0700 (PDT) (envelope-from gordont@gnf.org) Received: by mail.gnf.org (Postfix, from userid 888) id 123F211E503; Sat, 4 Aug 2001 14:03:10 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.gnf.org (Postfix) with ESMTP id 10FD611A56A; Sat, 4 Aug 2001 14:03:10 -0700 (PDT) Date: Sat, 4 Aug 2001 14:03:10 -0700 (PDT) From: Gordon Tetlow To: Sheldon Hearn Cc: Ollivier Robert , Subject: Re: ntpd 4.1 In-Reply-To: <20333.996840614@axl.seasidesoftware.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 3 Aug 2001, Sheldon Hearn wrote: > On Fri, 03 Aug 2001 10:18:49 +0200, Sheldon Hearn wrote: > > So let me guess. Not only does Mills think that the web is the only > sensible distribution medium for documentation, he also thinks that > English is the only sensible language for it? Ha, you think that's bad. Mills doesn't want to be bothered to change his ways to use any sort of revision control. That's how set in his ways he is. Almost as bad as Linus. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 14:20:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from femail2.sdc1.sfba.home.com (femail2.sdc1.sfba.home.com [24.0.95.82]) by hub.freebsd.org (Postfix) with ESMTP id 73A2037B403 for ; Sat, 4 Aug 2001 14:20:11 -0700 (PDT) (envelope-from mixtim@home.com) Received: from cg392862-a.adubn1.nj.home.com ([65.2.79.221]) by femail2.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010804212010.PCZL12480.femail2.sdc1.sfba.home.com@cg392862-a.adubn1.nj.home.com>; Sat, 4 Aug 2001 14:20:10 -0700 Received: (from mixtim@localhost) by cg392862-a.adubn1.nj.home.com (8.11.5/8.11.5) id f74LK5300435; Sat, 4 Aug 2001 17:20:05 -0400 (EDT) (envelope-from mixtim) Date: Sat, 4 Aug 2001 17:20:05 -0400 From: Mixtim To: Gordon Tetlow Cc: Sheldon Hearn , Ollivier Robert , freebsd-current@FreeBSD.ORG Subject: Re: ntpd 4.1 Message-ID: <20010804172005.A415@home.com> References: <20333.996840614@axl.seasidesoftware.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gordont@gnf.org on Sat, Aug 04, 2001 at 02:03:10PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Aug 04, 2001 at 02:03:10PM -0700, Gordon Tetlow wrote: > Ha, you think that's bad. Mills doesn't want to be bothered to change his > ways to use any sort of revision control. That's how set in his ways he > is. Almost as bad as Linus. :pserver:anoncvs@www.ntp.org:/cvs/ntp You can checkout modules 'ntp' or 'ntpfaq'. Been there for a rather long time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 14:39:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.gnf.org (firewall.gnf.org [208.44.31.34]) by hub.freebsd.org (Postfix) with ESMTP id B9AAE37B401 for ; Sat, 4 Aug 2001 14:39:41 -0700 (PDT) (envelope-from gordont@gnf.org) Received: by mail.gnf.org (Postfix, from userid 888) id 7504111E503; Sat, 4 Aug 2001 14:39:36 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.gnf.org (Postfix) with ESMTP id 7128A11A56A; Sat, 4 Aug 2001 14:39:36 -0700 (PDT) Date: Sat, 4 Aug 2001 14:39:36 -0700 (PDT) From: Gordon Tetlow To: Mixtim Cc: Sheldon Hearn , Ollivier Robert , Subject: Re: ntpd 4.1 In-Reply-To: <20010804172005.A415@home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 4 Aug 2001, Mixtim wrote: > On Sat, Aug 04, 2001 at 02:03:10PM -0700, Gordon Tetlow wrote: > > Ha, you think that's bad. Mills doesn't want to be bothered to change his > > ways to use any sort of revision control. That's how set in his ways he > > is. Almost as bad as Linus. > > :pserver:anoncvs@www.ntp.org:/cvs/ntp > > You can checkout modules 'ntp' or 'ntpfaq'. > > Been there for a rather long time. Actually, I was talking with the guy that manages the cvs repo for it. From what I gather (and the cvs repo seems to back up) is that Mills has never actually committed a thing. Harlan Stenn does most of the CVS work. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 16:24:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.gnf.org (firewall.gnf.org [208.44.31.34]) by hub.freebsd.org (Postfix) with ESMTP id F418837B401 for ; Sat, 4 Aug 2001 16:24:10 -0700 (PDT) (envelope-from gordont@gnf.org) Received: by mail.gnf.org (Postfix, from userid 888) id D5D4311E503; Sat, 4 Aug 2001 16:24:10 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.gnf.org (Postfix) with ESMTP id D1C6011A56A for ; Sat, 4 Aug 2001 16:24:10 -0700 (PDT) Date: Sat, 4 Aug 2001 16:24:10 -0700 (PDT) From: Gordon Tetlow To: Subject: snapshot installation woes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I decided I was going to brave 5.0-CURRENT and give the snapshots available on current.jp.freebsd.org a try. I found a couple issues with installation disks (FWIW, I tried it on the lastest snapshot avail on current.freebsd.org. I got the same results). Anyway, I go through the standard kern/mfsroot floppy deal and when it boots the kernel, everything seems to be going fine until I get the following kernel panic: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xffffffab fault code = supervisor write, page not present instruction pointer = 0x8:0xc0a75ac0 stack pointer = 0x10:0xc6978f68 frame pointer = 0x10:0xc6978f80 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupts enabled, resume, IOPL = 0 current process = 26 (irq10:sn0) trap number = 12 panic: page fault syncing disks... done Uptime: 2s FWIW, it's 5.0-20010804-JPSNAP #0 available off of current.jp.freebsd.org. I noticed it said it was in sn0. So being industrious, I interrupted the autoboot and did: ok set hint.sn.0.disabled=1 Sure enough, that fixed the kernel panic, but here's the next odd piece, my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940 dmesg reports that ahc0 is there. The lines from the dmesg are (hand typed): ahc0: port 0x5000-0x50ff mem 0x50000000-0x50000fff irq 15 at device 15.0 on pci0 device_probe_and_attach: ahc0 attach returned 12 errno.h says ENOMEM is 12, so it seems that something in the ahc driver is unable to allocate memory. Dunno where or why, but something is fouling it up. By contrast 4.3-RELEASE doesn't have any issues (I'll try a recent snapshot if that would help). Sorry I can't help out any more, but the debugging tools in the installation disks seem to lacking (understandably). Any help? -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 17: 5:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from draco.over-yonder.net (draco.over-yonder.net [198.78.58.61]) by hub.freebsd.org (Postfix) with ESMTP id B28D637B401 for ; Sat, 4 Aug 2001 17:05:14 -0700 (PDT) (envelope-from gh@over-yonder.net) Received: by draco.over-yonder.net (Postfix, from userid 1012) id 45D2062D0F; Sat, 4 Aug 2001 19:05:14 -0500 (CDT) Date: Sat, 4 Aug 2001 19:05:14 -0500 From: GH To: "Matthew D. Fuller" Cc: Garance A Drosihn , Peter Wemm , current@FreeBSD.ORG Subject: Re: Userbase of -current Message-ID: <20010804190514.I48649@over-yonder.net> References: <20010718061815.BCEEE38CC@overcee.netplex.com.au> <20010719103042.E3398@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010719103042.E3398@futuresouth.com>; from fullermd@futuresouth.com on Thu, Jul 19, 2001 at 10:30:42AM -0500 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jul 19, 2001 at 10:30:42AM -0500, some SMTP stream spewed forth: > On Wed, Jul 18, 2001 at 09:34:41PM -0400, a little birdie told me > that Garance A Drosihn remarked > > At 11:18 PM -0700 7/17/01, Peter Wemm wrote: > > >If I had to guess, I'd put the total [genuine] -current userbase > > >at between 20 and 50 people. And many of those intentionally lag > > >by a few weeks to a month or two. I have a strong feeling that the -CURRENT userbase is quite a bit larger than that, but I have nothing conclusive. > > At the kernel-confab at usenix, I heard some people talking about > > how "current wasn't really as bad as people assume it is". I must > > admit I wonder how much current is actively used. I know I try > > to build a new up-to-date current every two or three weeks, but I > > don't do much more on it than test a few changes. I am certainly > > not "stress-testing" it. Almost all of my real day-to-day work is > > done on machines which are tracking -stable. > > FWIW, without extraordinary reason, I don't run 'production' machines on > -CURRENT (I think the last time I did so was when I ran a news server on > 3.0-CURRENT). However, my workstation runs -CURRENT, and my dialup router > does as well (mainly to make it easier to update), my laptop... come to > think of it, almost all my of personal machines run -CURRENT, except for > one that runs 2.1-STABLE (386SX. 4 MB RAM. 80 meg disk. Last benchmark: > 13 days for a buildworld. Don't think I'll update it any time soon). I'll second this. I do all of my daily work on -CURRENT workstations, and I have had no siginificant problems since I started nearly two years ago. Of course, there is always the slim chance of some rogue (ah hem, un-thoroughly-tested) commit destroying something, but I have faith in the developer community. All my personal boxen (three, at the moment) run -CURRENT. I don't know if I would call my general use "stress testing", but touch a large portion of the functionality on a daily (sometimes the days merge...) basis. > -- > Matthew Fuller (MF4839) | fullermd@over-yonder.net > Unix Systems Administrator | fullermd@futuresouth.com Daniel M. Kurry -- What, no one sings along with Ricky Martin anymore? My kid sister does (but then, she prefers pico to vi ...) -- Suresh Ramasubramanian, alt.sysadmin.recovery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 17:10:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from tara.freenix.org (keltia.freenix.org [62.4.20.87]) by hub.freebsd.org (Postfix) with ESMTP id 95E4837B42C for ; Sat, 4 Aug 2001 17:10:31 -0700 (PDT) (envelope-from roberto@tara.freenix.org) Received: by tara.freenix.org (Postfix/TLS, from userid 101) id D2039258; Sun, 5 Aug 2001 02:10:28 +0200 (CEST) Date: Sun, 5 Aug 2001 02:10:28 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: ntpd 4.1 Message-ID: <20010805021028.A89877@tara.freenix.org> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <20010804172005.A415@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: ; from gordont@gnf.org on Sat, Aug 04, 2001 at 02:39:36PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT K6-3D/266 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG According to Gordon Tetlow: > >From what I gather (and the cvs repo seems to back up) is that Mills has > never actually committed a thing. Harlan Stenn does most of the CVS work. That's correct. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 17:12:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from tara.freenix.org (keltia.freenix.org [62.4.20.87]) by hub.freebsd.org (Postfix) with ESMTP id EEBE437B403 for ; Sat, 4 Aug 2001 17:12:13 -0700 (PDT) (envelope-from roberto@tara.freenix.org) Received: by tara.freenix.org (Postfix/TLS, from userid 101) id E0A28258; Sun, 5 Aug 2001 02:12:16 +0200 (CEST) Date: Sun, 5 Aug 2001 02:12:16 +0200 From: Ollivier Robert To: FreeBSD Current Users' list Subject: Re: ntpd 4.1 Message-ID: <20010805021216.B89877@tara.freenix.org> Mail-Followup-To: FreeBSD Current Users' list References: <20010802122513.C89868@caerdonn.eurocontrol.fr> <200108021307.f72D7dr07962@grimreaper.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200108021307.f72D7dr07962@grimreaper.grondar.za>; from mark@grondar.za on Thu, Aug 02, 2001 at 02:07:38PM +0100 X-Operating-System: FreeBSD 5.0-CURRENT K6-3D/266 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG According to Mark Murray: > Can you make it so that if NO_OPENSSL is not defined, then openssl is used? I could of course but I don't think that having PUBKEYS by defaults (X.509 based, not the PGP ones) is probably not very useful yet as it is a fairly recent option. AUTOKEY should be enough. Any objection? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 17:26:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 96BF837B401 for ; Sat, 4 Aug 2001 17:26:18 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id 471D03E32; Sat, 4 Aug 2001 17:26:17 -0700 (PDT) Received: from bazooka.unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id 3C7DD3C12B; Sat, 4 Aug 2001 17:26:17 -0700 (PDT) To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: md/mdmfs bugs In-Reply-To: <20010729185401.A642@xor.obsecurity.org>; from kris@obsecurity.org on "Sun, 29 Jul 2001 18:54:01 -0700" Date: Sat, 04 Aug 2001 17:26:12 -0700 From: Dima Dorfman Message-Id: <20010805002617.471D03E32@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kris Kennaway writes: > 1) For some reason, my mdmfs line in /etc/fstab always does a chmod > 777 /tmp at mount-time > > /dev/md0 /tmp mfs rw,-s=65536 0 0 As previously threatened, I implemented bug-to-bug compatibility with mount_mfs(). The patch is attached below. Please try it and see if it fixes this problem. Here's an excerpt from the manual page that roughly describes what I did: COMPATIBILITY mdmfs, while designed to be fully compatible with mount_mfs(8), can be useful by itself. Since mount_mfs(8) has some silly defaults, a ``full compatibility'' mode is provided for the case where bug-to-bug compati- bility is desired. Full compatibility is enabled with the -C flag, or by starting mdmfs with mount_ at the beginning of its name (as returned by getprogname(3)). In this mode, only the options which would be accepted by mount_mfs(8) are valid. Furthermore, the following behavior, as done by mount_mfs(8), is duplicated: o The file mode of mount-point is set to 01777 as if -p 1777 was given on the command line. If you have a link from /sbin/mount_mfs to /sbin/mdmfs, you don't need to worry about all that stuff. Just apply the patch below, build it, copy it to /sbin, and umount/mount /tmp; it should DTRT. Please let me know how it works out. Thanks. Index: mdmfs.8 =================================================================== RCS file: /ref/cvsf/src/sbin/mdmfs/mdmfs.8,v retrieving revision 1.6 diff -u -r1.6 mdmfs.8 --- mdmfs.8 2001/07/30 09:13:21 1.6 +++ mdmfs.8 2001/08/05 00:17:02 @@ -25,7 +25,7 @@ .\" .\" $FreeBSD: src/sbin/mdmfs/mdmfs.8,v 1.6 2001/07/30 09:13:21 dd Exp $ .\" -.Dd May 26, 2001 +.Dd August 5, 2001 .Dt MDMFS 8 .Os .Sh NAME @@ -35,7 +35,7 @@ driver .Sh SYNOPSIS .Nm -.Op Fl DLMNSX +.Op Fl DLMNSUX .Op Fl a Ar maxcontig .Op Fl b Ar block-size .Op Fl c Ar cylinders @@ -53,6 +53,24 @@ .Op Fl w Ar user : Ns Ar group .Ar md-device .Ar mount-point +.Nm +.Fl C +.Op Fl NU +.Op Fl a Ar maxcontig +.Op Fl b Ar block-size +.Op Fl c Ar cylinders +.Op Fl d Ar rotdelay +.Op Fl e Ar maxbpg +.Op Fl F Ar file +.Op Fl f Ar frag-size +.Op Fl i Ar bytes +.Op Fl m Ar percent-free +.Op Fl n Ar rotational-positions +.Op Fl O Ar optimization +.Op Fl o Ar mount-options +.Op Fl s Ar size +.Ar md-device +.Ar mount-point .Sh DESCRIPTION The .Nm @@ -110,6 +128,13 @@ option). .It Fl b Ar block-size The block size of the filesystem, in bytes. +.It Fl C +Enable full compatibility mode with +.Xr mount_mfs 8 . +See the +.\" XXX link to another section? +.Em COMPATIBILITY +section for more information. .It Fl c Ar cylinders The number of cylinders per cylinder group in the filesystem. .It Fl D @@ -192,6 +217,13 @@ .Xr malloc 9 backed disks .Pq Dv MD_MALLOC . +.It Fl U +Enable soft-updates on the filesystem. +This is the default, even in compatibility mode, and is accepted only +for compatibility. +It is only really useful to negate the +.Fl S +flag, should such a need occur. .It Fl w Ar user : Ns Ar group Set the owner and group to .Ar user @@ -257,8 +289,46 @@ .Cm async : .Pp .Dl "mdmfs -M -S -o async -s 16m md1 /tmp" +.Sh COMPATIBILITY +.Nm , +while designed to be fully compatible with +.Xr mount_mfs 8 , +can be useful by itself. +Since +.Xr mount_mfs 8 +has some silly defaults, a +.Dq full compatibility +mode is provided for the case where bug-to-bug compatibility is desired. +.Pp +Full compatibility is enabled with the +.Fl C +flag, +or by starting +.Nm +with +.Li mount_ +at the beginning of its name +(as returned by +.Xr getprogname 3 ) . +In this mode, only the options which would be accepted by +.Xr mount_mfs 8 +are valid. +Furthermore, the following behavior, as done by +.Xr mount_mfs 8 , +is duplicated: +.Bl -bullet -offset indent -compat +.It +The file mode of +.Ar mount-point +is set to +.Li 01777 +as if +.Fl p Ar 1777 +was given on the command line. +.El .Sh SEE ALSO .Xr md 4 , +.Xr fstab 5 , .Xr disklabel 8 , .Xr mdconfig 8 , .Xr mount 8 , Index: mdmfs.c =================================================================== RCS file: /ref/cvsf/src/sbin/mdmfs/mdmfs.c,v retrieving revision 1.5 diff -u -r1.5 mdmfs.c --- mdmfs.c 2001/07/30 09:11:17 1.5 +++ mdmfs.c 2001/08/05 00:18:38 @@ -65,6 +65,7 @@ bool mi_have_mode; }; +static bool compat; /* Full compatibility with mount_mfs? */ static bool debug; /* Emit debugging information? */ static bool loudsubs; /* Suppress output from helper programs? */ static bool norun; /* Actually run the helper programs? */ @@ -115,8 +116,12 @@ newfs_arg = strdup(""); mount_arg = strdup(""); + /* If we were started as mount_*, imply -C. */ + if (strncmp(getprogname(), "mount_", 6) == 0) + compat = true; + while ((ch = getopt(ac, av, - "a:b:c:Dd:e:F:f:hi:LMm:Nn:O:o:p:Ss:t:w:X")) != -1) + "a:b:Cc:Dd:e:F:f:hi:LMm:Nn:O:o:p:Ss:t:Uw:X")) != -1) switch (ch) { case 'a': argappend(&newfs_arg, "-a %s", optarg); @@ -124,10 +129,17 @@ case 'b': argappend(&newfs_arg, "-b %s", optarg); break; + case 'C': + if (compat) + usage(); + compat = true; + break; case 'c': argappend(&newfs_arg, "-c %s", optarg); break; case 'D': + if (compat) + usage(); detach = false; break; case 'd': @@ -153,6 +165,8 @@ argappend(&newfs_arg, "-i %s", optarg); break; case 'L': + if (compat) + usage(); loudsubs = true; break; case 'M': @@ -165,6 +179,8 @@ argappend(&newfs_arg, "-m %s", optarg); break; case 'N': + if (compat) + usage(); norun = true; break; case 'n': @@ -177,6 +193,8 @@ argappend(&mount_arg, "-o %s", optarg); break; case 'p': + if (compat) + usage(); if (*optarg >= '0' && *optarg <= '7') mi.mi_mode = strtol(optarg, NULL, 8); if ((mi.mi_mode & ~07777) != 0) @@ -184,15 +202,24 @@ mi.mi_have_mode = true; break; case 'S': + if (compat) + usage(); softdep = false; break; case 's': argappend(&mdconfig_arg, "-s %s", optarg); break; + case 'U': + softdep = true; + break; case 'w': + if (compat) + usage(); extract_ugid(optarg, &mi); break; case 'X': + if (compat) + usage(); debug = true; break; default: @@ -203,6 +230,12 @@ if (ac < 2) usage(); + /* Make compatibility assumptions. */ + if (compat) { + mi.mi_mode = 01777; + mi.mi_have_mode = true; + } + /* Derive 'unit' (global). */ unitstr = av[0]; if (strncmp(unitstr, "/dev/", 5) == 0) @@ -634,12 +667,23 @@ static void usage(void) { + const char *name; - fprintf(stderr, -"usage: %s [-DLMNSX] [-a maxcontig] [-b block-size] [-c cylinders]\n" + if (compat) + name = getprogname(); + else + name = "mdmfs"; + if (!compat) + fprintf(stderr, +"Usage: %s [-DLMNSUX] [-a maxcontig [-b block-size] [-c cylinders]\n" "\t[-d rotdelay] [-e maxbpg] [-F file] [-f frag-size] [-i bytes]\n" "\t[-m percent-free] [-n rotational-positions] [-O optimization]\n" "\t[-o mount-options] [-p permissions] [-s size] [-w user:group]\n" -"\tmd-device mount-point\n", getprogname()); +"\tmd-device mount-point\n", name); + fprintf(stderr, +"Usage: %s -C [-NU] [-a maxcontig] [-b block-size] [-c cylinders]\n" +"\t[-d rotdelay] [-e maxbpg] [-F file] [-f frag-size] [-i bytes]\n" +"\t[-m percent-free] [-n rotational-positions] [-O optimization]\n" +"\t[-o mount-options] [-s size] md-device mount-point\n", name); exit(1); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 17:26:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 7687437B401; Sat, 4 Aug 2001 17:26:42 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.4/8.11.4) with ESMTP id f750QaX43287; Sun, 5 Aug 2001 01:26:36 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.4/8.11.4) with ESMTP id f750QYu96221; Sun, 5 Aug 2001 01:26:34 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200108050026.f750QYu96221@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Josef Karthauser Cc: Nik Clayton , Neil Ford , Paul Richards , freebsd-users@uk.freebsd.org, Brian Somers , freebsd-current@FreeBSD.org Subject: Should developers run current ? (was: XDM and X) In-Reply-To: Message from Josef Karthauser of "Sat, 04 Aug 2001 15:00:52 BST." <20010804150051.B48231@tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Aug 2001 01:26:34 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've cc'd freebsd-current here. This is a followup to a small thread on the UK user group list about the stability of -stable. Joe Karthauser wrote: > On Sat, Aug 04, 2001 at 02:42:44PM +0100, Nik Clayton wrote: > >=20 > > This hasn't suddenly changed in FreeBSD -- the -current/-stable branches > > have worked like this since at least the 2.x days. It's always been the > > case that if you're using FreeBSD in a production environment you should > > deploy any new version on to test machines first, and make sure that > > it works in your environment. > >=20 > > I agree. Over the years I've updated many production servers to > -stable, and of course periodically things break, I remember having > major difficulties when ------------------------ r caused regular panics > :) On the otherhand the majority of changes to -stable are for > subsystems and rarely affect the stability of the entire machine. For > my uses that was sufficient. Something has changed. IMHO the developer base has been segregated in the last year, mainly due to the the part-real, part-perceived instability of -current. There now seem to be two categories of developer: o The developer that's too dumb/stupid/smart/proud/lazy to run -stable and will keep fighting any problems that turn up in -current. o The developer that's probably been hit by one of the nastier -current bugs in the past year and has decided (on quite practical grounds) that it's better to develop under -stable. I believe this to be a bad thing. Back in the old days -stable was reserved for bug fixes and some features/enhancements. ABI and API changes weren't allowed. When someone made a mistake, they got the same clout across the back of the head that they do now, but things didn't break that often because relatively less was MFC'd. Now, because people are actively developing on -stable, they really need to push their work back into -stable so that they don't have to manage local source trees, trees that become more and more fragile as time passes. Because of this, -stable is now pretty similar to the -current we had a couple of years ago.... something that breaks a bit now and again, but not to a major degree as things should really be shaken out to some extent before they're committed there. -stable is no longer a branch that you can follow with a production system -- it's too risky. To this end, the RELEASE branches have been created. The release branches kind of address the problem because what's merged into them is kept to a minimum and is controlled by a few individuals that will not bend it's charter. There are downfalls to this system though - namely that each minor release upgrade contains huge numbers of feature additions/enhancements, making it difficult for people to regression-test production systems. Personally, I believe that the developers that are now developing under -stable should simply be lured back onto -current. Doing this may be enough to make -stable stable again -- if developers have no big incentive or requirement to have their code in -stable, but just have the overheads of having to merge it and read the -stable list, it may tip the balance back towards how things worked before. I appreciate that there are a huge number of issues -- things such as -current carrying so many enhancements that a major release upgrade becomes an enormous task. I believe there should be a balance somewhere, and to get closer to that balance, we need to attract our developers back to -current. > Joe -- Brian http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 17:55:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from citusc17 (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id BF13D37B401; Sat, 4 Aug 2001 17:55:29 -0700 (PDT) (envelope-from kris@citusc17) Received: (from kris@localhost) by citusc17 (8.11.4/8.11.4) id f750tM118189; Sat, 4 Aug 2001 17:55:23 -0700 (PDT) (envelope-from kris) Date: Sat, 4 Aug 2001 17:55:22 -0700 From: Kris Kennaway To: Brian Somers Cc: Josef Karthauser , Nik Clayton , Neil Ford , Paul Richards , freebsd-users@uk.freebsd.org, Brian Somers , freebsd-current@FreeBSD.ORG Subject: Re: Should developers run current ? (was: XDM and X) Message-ID: <20010804175522.C18102@citusc17.usc.edu> References: <200108050026.f750QYu96221@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="69pVuxX8awAiJ7fD" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200108050026.f750QYu96221@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Sun, Aug 05, 2001 at 01:26:34AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --69pVuxX8awAiJ7fD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 05, 2001 at 01:26:34AM +0100, Brian Somers wrote: > Back in the old days -stable was reserved for bug fixes and some=20 > features/enhancements. ABI and API changes weren't allowed. When=20 > someone made a mistake, they got the same clout across the back of=20 > the head that they do now, but things didn't break that often because=20 > relatively less was MFC'd. This discussion comes up periodically (usually, once per code freeze ;-) I don't think the high rate of MFCs mostly occurs because developers develop on -stable, it's because the branch can't be allowed to diverge too much from -current or porting of bugfixes becomes difficult (especially kernel bugfixes, but also other actively-developed or heavily modified systems). Many people feel seem to that the fact that this divergence was allowed to creep in between the 3.x/4.0-CURRENT branches contributed heavily to the continued poor stability of the 3.x branch towards the second half of its release cycle when it should be expected instead to mature and stabilize. If the developers all run -current, and -current is incompatible with -stable, then -stable also suffers in quality. There's a balance which needs to be struck. I run -stable on several systems and regularly upgrade. I haven't encountered sudden instability, incompatibility or sudden onset of problems. Personally, I don't think things are so bad in -stable land. Kris --69pVuxX8awAiJ7fD 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 iD8DBQE7bJl6Wry0BWjoQKURAlSNAKC5jkRBMpFcUxbuEED5iZafMrXJ8gCg0gjT b51l1qd2yY3V/9D4dZ3a644= =vTv0 -----END PGP SIGNATURE----- --69pVuxX8awAiJ7fD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 18:30:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 0214C37B401 for ; Sat, 4 Aug 2001 18:30:42 -0700 (PDT) (envelope-from daemon@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 15TCka-0005XI-01; Sun, 5 Aug 2001 03:30:40 +0200 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.5/8.11.1) id f750vi534101 for freebsd-current@freebsd.org; Sun, 5 Aug 2001 02:57:44 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: What's touching my executables? Date: Sun, 5 Aug 2001 00:57:42 +0000 (UTC) Message-ID: <9ki5m6$119c$1@kemoauc.mips.inka.de> References: <9kc65b$47n$1@kemoauc.mips.inka.de> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I wrote: > An increasing number of executables on that box are sporting ever > newer mtimes. This appears to have been going on ever since the > Jul 25 update. There is no clear pattern which executables are > touched. md5 comparisons with previous backup levels (using a Jul 13 > copy of md5) suggest that the executables have not been changed. I have updated the box (HEAD from Friday, alpha). The phenomenon still persists. I haven't observed any mtime changes on non-executable files. I'm running a small program that uses a kqueue(2) EVFILT_VNODE/NOTE_ATTRIB filter to watch for changes to /bin/*. During the last few hours some files there have changed their mtime without a kernel event being triggered. (An explicit touch(1) does trigger an event.) -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 18:31:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with SMTP id 1CF6737B401 for ; Sat, 4 Aug 2001 18:31:40 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 70408 invoked from network); 5 Aug 2001 01:31:39 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 5 Aug 2001 01:31:39 -0000 Message-ID: X-Mailer: XFMail 1.4.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: Date: Sat, 04 Aug 2001 18:31:39 -0700 (PDT) From: John Baldwin To: Gordon Tetlow Subject: RE: snapshot installation woes Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 04-Aug-01 Gordon Tetlow wrote: > I decided I was going to brave 5.0-CURRENT and give the snapshots > available on current.jp.freebsd.org a try. I found a couple issues with > installation disks (FWIW, I tried it on the lastest snapshot avail on > current.freebsd.org. I got the same results). > > Anyway, I go through the standard kern/mfsroot floppy deal and when it > boots the kernel, everything seems to be going fine until I get the > following kernel panic: > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xffffffab That's a NULL pointer deref. > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc0a75ac0 Hmmm... Can you look in the bin dist for the kernel.debug and do a 'gdb -k' on it to look up this address to see what line it is dying on? No idea on the ahc0 error. :( -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 4 21:42:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-27.dsl.lsan03.pacbell.net [63.207.60.27]) by hub.freebsd.org (Postfix) with ESMTP id BB52C37B401 for ; Sat, 4 Aug 2001 21:42:29 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B944266F38; Sat, 4 Aug 2001 21:42:28 -0700 (PDT) Date: Sat, 4 Aug 2001 21:42:28 -0700 From: Kris Kennaway To: Ollivier Robert Cc: FreeBSD Current Users' list Subject: Re: ntpd 4.1 Message-ID: <20010804214228.B8558@xor.obsecurity.org> References: <20010802122513.C89868@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ftEhullJWpWg/VHq" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010802122513.C89868@caerdonn.eurocontrol.fr>; from roberto@eurocontrol.fr on Thu, Aug 02, 2001 at 12:25:13PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --ftEhullJWpWg/VHq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 02, 2001 at 12:25:13PM +0200, Ollivier Robert wrote: > Now that ntpd 4.1.0 has been released (finally!), I'll upgrade current ve= ry > soon. >=20 > The question I have is the following: authentication was done with md5 co= de > builtin and I disabled DES support (not supported anymore). Now, with 4.1, > it can be linked to openssl but it is still an optional component. >=20 > I'm a bit reluctant to force openssl for just ntpd. >=20 > Any ideas / comments ? What we do for a number of other system components that can be built with/without openssl/crypto support is to select that based on NO_OPENSSL (and some other -- semi-redundant -- checks), and make sure it's built twice in make release. Look at release/Makefile and the ppp and tcpdump code to see how it's done. Kris --ftEhullJWpWg/VHq 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 iD8DBQE7bM6zWry0BWjoQKURAnD1AJ9eIki8cfr80VcQuS54ChQSqsYUCACgmArl bwGlhChxLAwSUvq5KZ65daY= =99vw -----END PGP SIGNATURE----- --ftEhullJWpWg/VHq-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message