From owner-freebsd-stable@FreeBSD.ORG Sun Oct 30 10:14:27 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAF7716A41F for ; Sun, 30 Oct 2005 10:14:27 +0000 (GMT) (envelope-from kouye@wanadoo.fr) Received: from smtp9.wanadoo.fr (smtp9.wanadoo.fr [193.252.22.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7576743D45 for ; Sun, 30 Oct 2005 10:14:27 +0000 (GMT) (envelope-from kouye@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0907.wanadoo.fr (SMTP Server) with ESMTP id 32E481C00171 for ; Sun, 30 Oct 2005 11:14:26 +0100 (CET) Received: from [192.168.1.3] (ASte-Genev-Bois-151-1-42-131.w83-114.abo.wanadoo.fr [83.114.152.131]) by mwinf0907.wanadoo.fr (SMTP Server) with ESMTP id 047E51C0015F for ; Sun, 30 Oct 2005 11:14:25 +0100 (CET) X-ME-UUID: 20051030101426185.047E51C0015F@mwinf0907.wanadoo.fr Message-ID: <43649CE8.6010004@wanadoo.fr> Date: Sun, 30 Oct 2005 11:14:00 +0100 From: edward User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051004) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: HFS/HFS+ support in 5.4 Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 10:14:28 -0000 Hi, I need to mount an iPod mini formatted in HFS+. I don't believe this file system is supported in 5.4 Stable, at least not on a standard kernel. I get : # ls /sbin/mount_* /sbin/mount_cd9660 /sbin/mount_msdosfs /sbin/mount_std /sbin/mount_devfs /sbin/mount_nfs /sbin/mount_udf /sbin/mount_ext2fs /sbin/mount_nfs4 /sbin/mount_umapfs /sbin/mount_fdescfs /sbin/mount_ntfs /sbin/mount_unionfs /sbin/mount_linprocfs /sbin/mount_nullfs /sbin/mount_mfs /sbin/mount_procfs The following page offers a HFS/HFS+ kernel module based on Darwin code. But it seems kind of out of date (2003) : http://people.freebsd.org/~yar/hfs/ What would be the best way of building HFS/HFS+ support into my kernel ? Thanks all, Edward From owner-freebsd-stable@FreeBSD.ORG Sun Oct 30 10:36:47 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2EB016A41F for ; Sun, 30 Oct 2005 10:36:47 +0000 (GMT) (envelope-from cristiano.deana@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AED643D46 for ; Sun, 30 Oct 2005 10:36:47 +0000 (GMT) (envelope-from cristiano.deana@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so373387wra for ; Sun, 30 Oct 2005 02:36:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=GSj+672cNiRdG3HUg7jvA+PoGrsTKBAdxfV76bPHvRsWGlPlAzLwVbGsZ6XaUjxezOViiIVkOWoRWq89A4kIlw46dEwuUwI5hg3tDegZGgmxUYHjyDZb5BqJaXwiwXItvvhdVuf/Mo80ouJlMW7F66iBcNR+WjLD7EbmpfX/8No= Received: by 10.54.121.5 with SMTP id t5mr536317wrc; Sun, 30 Oct 2005 02:36:46 -0800 (PST) Received: by 10.54.114.5 with HTTP; Sun, 30 Oct 2005 02:36:46 -0800 (PST) Message-ID: Date: Sun, 30 Oct 2005 11:36:46 +0100 From: Cristiano Deana To: FreeBSD Stable Mailing List MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 10:36:47 -0000 Hi, I've seen that 'GENERIC' file has been modified, moving some lines to 'DEFAULTS': device isa device mem # Memory and kernel memory devices =09 device io # I/O device Why? What does it mean? Should we include 'DEFAULTS' in our customized 'GENERIC'= ? Or those lines are no more mandatory? I think it should be written in 'UPDATING'. Regards. -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.org/ From owner-freebsd-stable@FreeBSD.ORG Sun Oct 30 10:49:49 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4154E16A41F for ; Sun, 30 Oct 2005 10:49:49 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0278343D48 for ; Sun, 30 Oct 2005 10:49:49 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id DAABF1A3C25; Sun, 30 Oct 2005 02:49:48 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 49B1C51376; Sun, 30 Oct 2005 05:49:48 -0500 (EST) Date: Sun, 30 Oct 2005 05:49:48 -0500 From: Kris Kennaway To: Cristiano Deana Message-ID: <20051030104948.GA32502@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: FreeBSD Stable Mailing List Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 10:49:49 -0000 --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 30, 2005 at 11:36:46AM +0100, Cristiano Deana wrote: > Hi, >=20 > I've seen that 'GENERIC' file has been modified, moving some lines to > 'DEFAULTS': >=20 > device isa >=20 > device mem # Memory and kernel memory devices =09 > device io # I/O device >=20 > Why? > What does it mean? Should we include 'DEFAULTS' in our customized 'GENERI= C'? It's included by DEFAULT. > Or those lines are no more mandatory? The point of a DEFAULTS file is that to contain things that are used by DEFAULT, including those which are mandatory. > I think it should be written in 'UPDATING'. No action is necessary. Kris --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZKVMWry0BWjoQKURAvmlAKD7r7ZMI7BxMpGZiftYEOshqEb1igCcDm79 3fYgcoAJ//zPZCEZkaLgfZQ= =OkeU -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/-- From owner-freebsd-stable@FreeBSD.ORG Sun Oct 30 10:53:59 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D462416A41F for ; Sun, 30 Oct 2005 10:53:59 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-152-166.sn2.eutelia.it [83.211.152.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FDD343D49 for ; Sun, 30 Oct 2005 10:53:58 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id 6EB202C90D for ; Sun, 30 Oct 2005 11:53:56 +0100 (CET) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id C78022C90E for ; Sun, 30 Oct 2005 11:53:55 +0100 (CET) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id 8B2152C90C for ; Sun, 30 Oct 2005 11:53:55 +0100 (CET) From: Massimo Lusetti To: freebsd-stable@freebsd.org In-Reply-To: References: Content-Type: text/plain Organization: CEDOC - Modena Date: Sun, 30 Oct 2005 11:53:55 +0100 Message-Id: <1130669635.4300.3.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 10:53:59 -0000 On Sun, 2005-10-30 at 11:36 +0100, Cristiano Deana wrote: > Hi, > > I've seen that 'GENERIC' file has been modified, moving some lines to > 'DEFAULTS': > > device isa > > device mem # Memory and kernel memory devices > device io # I/O device > > Why? > What does it mean? Should we include 'DEFAULTS' in our customized 'GENERIC'? > Or those lines are no more mandatory? DEFAULTS will be included automatically by the new config(8), quoting from markm@ "Its an anti-foot-shooting thing. Scott was concerned that far too many people with kernels based on GENERIC before io was made a separate module were being flummoxed by X not running. This is a way to make npx, mem and io default for even those kernels, as long as they run a modern(tm) config(8)." Look for discussion in cvs-src@. -- Massimo.run(); From owner-freebsd-stable@FreeBSD.ORG Sun Oct 30 10:56:29 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD03F16A41F for ; Sun, 30 Oct 2005 10:56:29 +0000 (GMT) (envelope-from cristiano.deana@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41FB643D46 for ; Sun, 30 Oct 2005 10:56:29 +0000 (GMT) (envelope-from cristiano.deana@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so374058wra for ; Sun, 30 Oct 2005 02:56:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qiILN5u/C8E2c5ZagU1os8FcM8eKCuUQq9w+3ylj5ijKh6AxZoELsJRhuakYBwTtb/0XuynvldUrgGV4kItocgp5yBSchCO2eF4FwOvnUPFE9k+Zc7xQlvvOakWNoq/9RAOiiqNkDtvCOTof/ciu3C1CcTlPmqXNd4SGKUt8e9U= Received: by 10.54.142.5 with SMTP id p5mr563218wrd; Sun, 30 Oct 2005 02:56:28 -0800 (PST) Received: by 10.54.114.5 with HTTP; Sun, 30 Oct 2005 02:56:28 -0800 (PST) Message-ID: Date: Sun, 30 Oct 2005 11:56:28 +0100 From: Cristiano Deana To: FreeBSD Stable Mailing List In-Reply-To: <20051030104948.GA32502@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051030104948.GA32502@xor.obsecurity.org> Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 10:56:29 -0000 Thank you , Kris. > It's included by DEFAULT. > The point of a DEFAULTS file is that to contain things that are used > by DEFAULT, including those which are mandatory. As I thought, but how? I didn't see any "include" in GENERIC or any modify in Makefile. > > I think it should be written in 'UPDATING'. > No action is necessary. Maybe just an explanation into 'GENERIC' or 'DEFAULTS'. Remember that we had for years "Do not remove 'device isa' from kernel!" and now it disappears. :) Thank you again. -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.org/ From owner-freebsd-stable@FreeBSD.ORG Sun Oct 30 10:57:51 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4300116A41F for ; Sun, 30 Oct 2005 10:57:51 +0000 (GMT) (envelope-from ph.schulz@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 7C87643D6B for ; Sun, 30 Oct 2005 10:57:47 +0000 (GMT) (envelope-from ph.schulz@gmx.de) Received: (qmail invoked by alias); 30 Oct 2005 10:57:44 -0000 Received: from dslb-084-056-232-222.pools.arcor-ip.net (EHLO [192.168.1.6]) [84.56.232.222] by mail.gmx.net (mp012) with SMTP; 30 Oct 2005 11:57:44 +0100 X-Authenticated: #1954550 Message-ID: <4364A727.9090106@gmx.de> Date: Sun, 30 Oct 2005 11:57:43 +0100 From: "Philip S. Schulz" User-Agent: Thunderbird 1.4 (Macintosh/20050908) MIME-Version: 1.0 To: Cristiano Deana References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: FreeBSD Stable Mailing List Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 10:57:51 -0000 on 30.10.2005 11:36 Uhr Cristiano Deana said the following: > Hi, > > I've seen that 'GENERIC' file has been modified, moving some lines to > 'DEFAULTS': > > device isa > > device mem # Memory and kernel memory devices > device io # I/O device > > Why? > What does it mean? Should we include 'DEFAULTS' in our customized 'GENERIC'? > Or those lines are no more mandatory? > No, you don't need to include 'DEFAULTS', config(8) will take care of that for you. http://docs.FreeBSD.org/cgi/mid.cgi?200510271713.j9RHDNTo013082 AFAICT, this was done in order to automatically include devices which are essential in most cases so less experienced users won't accidentally break their systems and later complain that e.g. X doesn't work anymore. HTH, Phil. -- Don't fix it if it ain't broke. From owner-freebsd-stable@FreeBSD.ORG Sun Oct 30 11:04:14 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF6F816A41F for ; Sun, 30 Oct 2005 11:04:14 +0000 (GMT) (envelope-from mat@mat.cc) Received: from plouf.absolight.net (plouf.absolight.net [193.30.224.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EE7A43D48 for ; Sun, 30 Oct 2005 11:04:14 +0000 (GMT) (envelope-from mat@mat.cc) Date: Sun, 30 Oct 2005 12:04:11 +0100 From: Mathieu Arnold To: freebsd-stable@freebsd.org Message-ID: In-Reply-To: <1130669635.4300.3.camel@massimo.datacode.it> References: <1130669635.4300.3.camel@massimo.datacode.it> X-Mailer: Mulberry/3.1.6 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 11:04:14 -0000 +-le 30/10/2005 11:53 +0100, Massimo Lusetti =E9crivait : | On Sun, 2005-10-30 at 11:36 +0100, Cristiano Deana wrote: |=20 |> Hi, |>=20 |> I've seen that 'GENERIC' file has been modified, moving some lines to |> 'DEFAULTS': |>=20 |> device isa |>=20 |> device mem # Memory and kernel memory devices |> device io # I/O device |>=20 |> Why? |> What does it mean? Should we include 'DEFAULTS' in our customized |> 'GENERIC'? Or those lines are no more mandatory? |=20 | DEFAULTS will be included automatically by the new config(8), quoting | from markm@ | "Its an anti-foot-shooting thing. Scott was concerned that far too many | people with kernels based on GENERIC before io was made a separate | module were being flummoxed by X not running. This is a way to make | npx, mem and io default for even those kernels, as long as they run a | modern(tm) config(8)." |=20 | Look for discussion in cvs-src@. In that case, how do we remove io or mem so that they get in as kld at boot time ? --=20 Mathieu Arnold From owner-freebsd-stable@FreeBSD.ORG Sun Oct 30 11:46:57 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4757016A41F; Sun, 30 Oct 2005 11:46:57 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABAF243D46; Sun, 30 Oct 2005 11:46:56 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.3/8.13.3) with ESMTP id j9UBktGw085574; Sun, 30 Oct 2005 14:46:55 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Sun, 30 Oct 2005 14:46:55 +0300 (MSK) From: Dmitry Morozovsky To: freebsd-stable@FreeBSD.org Message-ID: <20051030144228.C53366@woozle.rinet.ru> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (woozle.rinet.ru [0.0.0.0]); Sun, 30 Oct 2005 14:46:55 +0300 (MSK) Cc: pjd@FreeBSD.org Subject: gmirror panic @ RELENG_5/amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 11:46:57 -0000 Dear colleagues, after several hangs once our router drops to debugger with the following: any hints? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x8:0xffffffff80584578 stack pointer = 0x10:0xffffffffa4747bb0 frame pointer = 0x10:0xffffff00009f4c00 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 48 (g_mirror m0f) [thread pid 48 tid 100035 ] Stopped at g_mirror_event_remove+0x38: decl %eax db> db> trace Tracing pid 48 tid 100035 td 0xffffff001ec18c80 g_mirror_event_remove() at g_mirror_event_remove+0x38 db> panic [here it hangs solid] From owner-freebsd-stable@FreeBSD.ORG Sun Oct 30 14:03:43 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9F1B16A41F for ; Sun, 30 Oct 2005 14:03:43 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-152-166.sn2.eutelia.it [83.211.152.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 482DA43D45 for ; Sun, 30 Oct 2005 14:03:42 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id 375252C90C for ; Sun, 30 Oct 2005 15:03:41 +0100 (CET) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id 13A502C90A for ; Sun, 30 Oct 2005 15:03:40 +0100 (CET) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id C746B2C906 for ; Sun, 30 Oct 2005 15:03:39 +0100 (CET) From: Massimo Lusetti To: freebsd-stable@freebsd.org In-Reply-To: References: <1130669635.4300.3.camel@massimo.datacode.it> Content-Type: text/plain Organization: CEDOC - Modena Date: Sun, 30 Oct 2005 15:03:39 +0100 Message-Id: <1130681019.4304.1.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 14:03:43 -0000 On Sun, 2005-10-30 at 12:04 +0100, Mathieu Arnold wrote: > In that case, how do we remove io or mem so that they get in as kld at boot > time ? With the nodevice directive. -- Massimo.run(); From owner-freebsd-stable@FreeBSD.ORG Sun Oct 30 14:21:25 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C254116A41F for ; Sun, 30 Oct 2005 14:21:25 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: from mail.interbgc.com (mx02.interbgc.com [217.9.224.227]) by mx1.FreeBSD.org (Postfix) with SMTP id B94E343D45 for ; Sun, 30 Oct 2005 14:21:23 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: (qmail 72865 invoked from network); 30 Oct 2005 14:21:20 -0000 Received: from nike_d@cytexbg.com by keeper.interbgc.com by uid 1002 with qmail-scanner-1.14 (uvscan: v4.2.40/v4374. spamassassin: 2.63. Clear:SA:0(-2.5/8.0):. Processed in 4.625836 secs); 30 Oct 2005 14:21:20 -0000 X-Spam-Status: No, hits=-2.5 required=8.0 Received: from unknown (HELO tormentor.totalterror.net) (213.240.205.57) by mx02.interbgc.com with SMTP; 30 Oct 2005 14:21:15 -0000 Received: (qmail 38326 invoked from network); 30 Oct 2005 14:21:12 -0000 Received: from qmail by qscan (mail filter); 30 Oct 2005 14:21:12 +0000 Received: from unknown (HELO ?10.0.0.3?) (ndenev@10.0.0.3) by tormentor.totalterror.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 30 Oct 2005 14:21:12 -0000 Message-ID: <4364D6D3.6010508@cytexbg.com> Date: Sun, 30 Oct 2005 16:21:07 +0200 From: Niki Denev User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <436311C2.6090708@cytexbg.com> <20051029061513.GG36235@tnn.dglawrence.com> <43631721.50504@cytexbg.com> <4363E333.5000803@cytexbg.com> In-Reply-To: <4363E333.5000803@cytexbg.com> X-Enigmail-Version: 0.92.1.0 OpenPGP: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: sendfile + non local filesystem + lighttpd = EOPNOTSUPP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 14:21:25 -0000 Niki Denev wrote: > > > I get the same behaviour also with 6.0-RC1 (cvsupped an hour ago) > Ok, In this awful piece of code created for testing purposes if i set FILETOSEND to local file it works ok, but if the file is located on smbfs sendfile returns "Operation not supported". If this is not a bug, maybe it should be documented? (also the error code that sendfile returns) (again, the machine is 6.0-RC1 cvsupped yesterday, with SMP kernel) ---[sendfile_test.c]--- #include #include #include #include #include #include #include #include #include #include #include #include #include #define FILETOSEND "/var/log/messages" //#define FILETOSEND "/mnt/smb/somefile.dat" int main() { int fd; int sock; int result; struct sockaddr_in sa; fd = open(FILETOSEND, O_RDONLY); sock = socket(PF_INET, SOCK_STREAM, 0); memset(&sa, 0, sizeof(sa)); sa.sin_family = AF_INET; sa.sin_port = htons(9); /* discard enabled in inetd */ inet_aton("127.0.0.1", &sa.sin_addr); printf("connecting socket ... "); errno = 0; result = connect(sock, (struct sockaddr *)&sa, sizeof(sa)); printf("%s\n", errno?strerror(errno):"ok"); printf("calling sendfile ... "); errno = 0; result = sendfile(fd, sock, 0, 0, NULL, NULL, 0); printf("%s\n", errno?strerror(errno):"ok"); close(fd); close(sock); return(0); } ---[end of sendfile_test.c]--- From owner-freebsd-stable@FreeBSD.ORG Sun Oct 30 15:14:26 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5973016A420 for ; Sun, 30 Oct 2005 15:14:26 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: from mail.interbgc.com (mx01.interbgc.com [217.9.224.225]) by mx1.FreeBSD.org (Postfix) with SMTP id E86C343D48 for ; Sun, 30 Oct 2005 15:14:24 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: (qmail 64037 invoked from network); 30 Oct 2005 15:14:22 -0000 Received: from nike_d@cytexbg.com by keeper.interbgc.com by uid 1002 with qmail-scanner-1.14 (uvscan: v4.2.40/v4374. spamassassin: 2.63. Clear:SA:0(-2.6/8.0):. Processed in 4.236475 secs); 30 Oct 2005 15:14:22 -0000 X-Spam-Status: No, hits=-2.6 required=8.0 Received: from unknown (HELO tormentor.totalterror.net) (213.240.205.57) by mx01.interbgc.com with SMTP; 30 Oct 2005 15:14:18 -0000 Received: (qmail 45962 invoked from network); 30 Oct 2005 15:14:16 -0000 Received: from qmail by qscan (mail filter); 30 Oct 2005 15:14:16 +0000 Received: from unknown (HELO ?10.0.0.3?) (ndenev@10.0.0.3) by tormentor.totalterror.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 30 Oct 2005 15:14:16 -0000 Message-ID: <4364E342.9050505@cytexbg.com> Date: Sun, 30 Oct 2005 17:14:10 +0200 From: Niki Denev User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <436311C2.6090708@cytexbg.com> <20051029061513.GG36235@tnn.dglawrence.com> <43631721.50504@cytexbg.com> <4363E333.5000803@cytexbg.com> <4364D6D3.6010508@cytexbg.com> In-Reply-To: <4364D6D3.6010508@cytexbg.com> X-Enigmail-Version: 0.92.1.0 OpenPGP: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: sendfile + non local filesystem + lighttpd = EOPNOTSUPP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 15:14:26 -0000 This thread seems to relate to the same problem in dfbsd : http://leaf.dragonflybsd.org/mailarchive/kernel/2005-03/msg00101.html I think that this should be fixed, the man page did not mentions EOPNOTSUPP and this can lead to further confusion because it seems that HP-UX for example sets errno to EOPNOTSUPP when the socket is not TCP. Any comments? P.S.: It seems like i'm talking to myslef, i hope it's because it's sunday :) --niki From owner-freebsd-stable@FreeBSD.ORG Sun Oct 30 15:23:18 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74E0A16A41F; Sun, 30 Oct 2005 15:23:18 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id B779743D48; Sun, 30 Oct 2005 15:23:17 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.3/8.13.3) with ESMTP id j9UFNG2r093948; Sun, 30 Oct 2005 18:23:16 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Sun, 30 Oct 2005 18:23:16 +0300 (MSK) From: Dmitry Morozovsky To: freebsd-stable@freebsd.org In-Reply-To: <20051030144228.C53366@woozle.rinet.ru> Message-ID: <20051030182217.D87851@woozle.rinet.ru> References: <20051030144228.C53366@woozle.rinet.ru> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (woozle.rinet.ru [0.0.0.0]); Sun, 30 Oct 2005 18:23:16 +0300 (MSK) Cc: pjd@freebsd.org Subject: Re: gmirror panic @ RELENG_5/amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 15:23:18 -0000 On Sun, 30 Oct 2005, Dmitry Morozovsky wrote: DM> Dear colleagues, DM> DM> after several hangs once our router drops to debugger with the following: DM> DM> any hints? Source found: almost dead CPU cooler. Strange that mbmon did not found raised temperature. Sorry for the noise. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Sun Oct 30 23:22:41 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 655E416A41F for ; Sun, 30 Oct 2005 23:22:41 +0000 (GMT) (envelope-from freebsd-stable@box559.com) Received: from mx4.x15.net (mx4.x15.net [69.55.237.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3556043D49 for ; Sun, 30 Oct 2005 23:22:41 +0000 (GMT) (envelope-from freebsd-stable@box559.com) Received: from j1.x15.net [63.196.213.76] by mx4.x15.net with ESMTP id 510201052X1EWMVc000GrJNu for ; Sun, 30 Oct 2005 23:22:40 +0000 Message-ID: <436555A1.3010305@box559.com> Date: Sun, 30 Oct 2005 15:22:09 -0800 From: Pete Slagle MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4364A727.9090106@gmx.de> In-Reply-To: <4364A727.9090106@gmx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 23:22:41 -0000 >> I've seen that 'GENERIC' file has been modified, moving some lines to >> 'DEFAULTS': >> >> device isa >> >> device mem # Memory and kernel memory devices >> device io # I/O device >> >> Why? >> What does it mean? Should we include 'DEFAULTS' in our customized >> 'GENERIC'? >> Or those lines are no more mandatory? >> > > No, you don't need to include 'DEFAULTS', config(8) will take care of > that for you. > > http://docs.FreeBSD.org/cgi/mid.cgi?200510271713.j9RHDNTo013082 > > AFAICT, this was done in order to automatically include devices which > are essential in most cases so less experienced users won't accidentally > break their systems and later complain that e.g. X doesn't work anymore. The whole mechanism seems like an obvious POLA violation. All the more so without a note in UPDATING. Personally, I prefer less automated "help." In general, it might be better to encourage those who need a nanny to run Windows, leaving FreeBSD unencumbered for those who don't. IMHO. From owner-freebsd-stable@FreeBSD.ORG Sun Oct 30 23:27:22 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 868B916A41F for ; Sun, 30 Oct 2005 23:27:22 +0000 (GMT) (envelope-from edwin@mavetju.org) Received: from mail3out.barnet.com.au (mail3out.barnet.com.au [202.83.176.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF84E43D49 for ; Sun, 30 Oct 2005 23:27:21 +0000 (GMT) (envelope-from edwin@mavetju.org) Received: by mail3out.barnet.com.au (Postfix, from userid 27) id BFEF3877CA7; Mon, 31 Oct 2005 10:27:19 +1100 (EST) X-Viruscan-Id: <436556D7000111838B0A54@BarNet> Received: from mail3-auth.barnet.com.au (mail3.barnet.com.au [202.83.176.16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.barnet.com.au", Issuer "BarNet Root Certificate Authority" (verified OK)) by mail3.barnet.com.au (Postfix) with ESMTP id 8BB01877C51; Mon, 31 Oct 2005 10:27:19 +1100 (EST) Received: from k7.mavetju (edwin-3.int.barnet.com.au [10.10.12.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "edwin.adsl.barnet.com.au", Issuer "BarNet Root Certificate Authority" (not verified)) by mail3-auth.barnet.com.au (Postfix) with ESMTP id 1BE3B877C30; Mon, 31 Oct 2005 10:27:19 +1100 (EST) Received: by k7.mavetju (Postfix, from userid 1001) id 8A9C0611F; Mon, 31 Oct 2005 10:27:17 +1100 (EST) Date: Mon, 31 Oct 2005 10:27:17 +1100 From: Edwin Groothuis To: Carl Makin Message-ID: <20051030232717.GA1277@k7.mavetju> Mail-Followup-To: Edwin Groothuis , Carl Makin , freebsd-stable@freebsd.org References: <43616CEA.9020600@xena.ipaustralia.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43616CEA.9020600@xena.ipaustralia.gov.au> User-Agent: Mutt/1.5.9i Cc: freebsd-stable@freebsd.org Subject: Re: Easy way to kill a 5.x/6.x box as a basic user. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 23:27:22 -0000 On Fri, Oct 28, 2005 at 10:12:26AM +1000, Carl Makin wrote: > I've been playing with some GIS software and 32Mb TIFF images. Running > ImageMagick's "convert" utility under my normal user login to convert > the image to gif or jpeg blows away the system every time. No panic > seen on the console and no core dump found, the system just quietly > reboots. Upon reboot /var is full and corrupt and takes ages for the > background fsck to fix it so I normally boot into single user mode and > do it myself. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/67919 Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://weblog.barnet.com.au/edwin/ From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 00:03:57 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5286416A41F; Mon, 31 Oct 2005 00:03:57 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABF3343D48; Mon, 31 Oct 2005 00:03:55 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from palle.girgensohn.se ([213.114.205.87] [213.114.205.87]) by mxfep01.bredband.com with ESMTP id <20051031000354.CSMH28583.mxfep01.bredband.com@palle.girgensohn.se>; Mon, 31 Oct 2005 01:03:54 +0100 Received: from palle.girgensohn.se (palle.girgensohn.se [127.0.0.1]) by palle.girgensohn.se (Postfix) with ESMTP id 96D4917BBD; Mon, 31 Oct 2005 01:03:54 +0100 (CET) Date: Mon, 31 Oct 2005 01:03:54 +0100 From: Palle Girgensohn To: Brian Fundakowski Feldman , Michael Nottebrock , freebsd-stable@freebsd.org Message-ID: <7FC4EB5F5513F86A61F43F20@palle.girgensohn.se> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; FORMAT=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: nectar@freebsd.org Subject: Re: linking problems with heimdal in base (ports version works) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 00:03:57 -0000 --On m=E5ndag, oktober 17, 2005 18.18.56 -0400 Brian Fundakowski Feldman=20 wrote: > On Sun, Oct 16, 2005 at 09:04:58PM +0400, Igor Pokrovsky wrote: >> On Sun, Oct 16, 2005 at 06:35:51PM +0200, Michael Nottebrock wrote: >> > On Sunday, 16. October 2005 09:06, Igor Pokrovsky wrote: >> > > On Fri, Oct 14, 2005 at 09:49:51PM +0200, Michael Nottebrock wrote: >> > > > On Friday, 14. October 2005 21:11, Igor Pokrovsky wrote: >> > > > > > Still, isn't it strange that the kerberos libs don't have any >> > > > > > dependencies registered? A quick check shows that they are >> > > > > > almost the only libs in /usr/lib that have zero output from >> > > > > > ldd. >> > > > > >> > > > > Probably they are statically linked. >> > > > >> > > > No, static libraries don't come with an .so extension. :-) >> > > >> > > No, you missed my point. I mean that kerberos libs are dynamic but >> > > linked against other libraries statically. >> > >> > If they were, there would be no problem in the first place. >> >> Sorry, it seems I missed a part of the thread. > > Either the ports that use libkrb5 must know its dependencies or they > must be encoded in the shared library's header as dependencies. I vote > for #1 because it's too late for #2. See previous post about how to > solve this. Hi, I'm back on this subject. Just to make things clear: there are no static linking in heimdal. The=20 dependencies between the different libs are just not registered in the base = userland dist, but they are in the heimdal port. The Postgresql port does make use of krb5-config --libs. Problem is, they=20 don't get into libpq.so, so all dependant ports must also know that they=20 need kerberos if postgresql was linked with it. the pg_config utility has=20 no way of helping out here. My view is that the base heimdal installation=20 is buggy, it should register dependencies between the shared libs. Here's how libpq.so is linked: palle:libpq$ cc -O -pipe -march=3Dathlon-xp -Wall -Wmissing-prototypes=20 -Wpointer-arith -Wdeclaration-after-statement -Wold-style-definition=20 -Wendif-labels -fno-strict-aliasing -fPIC -DPIC -shared=20 -Wl,-x,-soname,libpq.so.4 fe-auth.o fe-connect.o fe-exec.o fe-misc.o=20 fe-print.o fe-lobj.o fe-protocol2.o fe-protocol3.o pqexpbuffer.o pqsignal.o = fe-secure.o md5.o ip.o wchar.o encnames.o noblock.o pgstrcasecmp.o thread.o = -L../../../src/port -L/usr/lib -L/usr/local/lib -lssl -lcrypto -lkrb5=20 -lcrypto -lcrypt -lroken -lasn1 -lcom_err -Wl,-R/usr/local/lib -o = libpq.so.4 palle:libpq$ ldd libpq.so libpq.so: libssl.so.3 =3D> /usr/lib/libssl.so.3 (0x28190000) libcrypto.so.3 =3D> /lib/libcrypto.so.3 (0x281c3000) libkrb5.so.7 =3D> /usr/lib/libkrb5.so.7 (0x282d4000) libcrypt.so.2 =3D> /lib/libcrypt.so.2 (0x28312000) libcom_err.so.2 =3D> /usr/lib/libcom_err.so.2 (0x2832b000) palle:libpq$ as you can see, the libasn1 is missing, and that fact makes other stuff,=20 like libpqxx, fail to build, since it misses symbols: configure:20828: checking for main in -lpq configure:20852: cc -o conftest -O -pipe -march=3Dathlon-xp=20 -I/usr/local/include -L/usr/local/lib conftest.c -lpq -L/usr/local/lib = >&5 /usr/lib/libkrb5.so.7: undefined reference to `length_PA_ENC_TS_ENC' /usr/lib/libkrb5.so.7: undefined reference to `length_KDC_REQ_BODY' /usr/lib/libkrb5.so.7: undefined reference to `free_Principal' /usr/lib/libkrb5.so.7: undefined reference to `bswap16' /usr/lib/libkrb5.so.7: undefined reference to `length_EncKrbCredPart' /usr/lib/libkrb5.so.7: undefined reference to `copy_Realm' /usr/lib/libkrb5.so.7: undefined reference to `strlwr' /usr/lib/libkrb5.so.7: undefined reference to `length_TGS_REQ' /usr/lib/libkrb5.so.7: undefined reference to `decode_TGS_REP' /usr/lib/libkrb5.so.7: undefined reference to `copy_PrincipalName' Now, you might argue that every single port must know that it shall use=20 kerberos, and add relevant libs to its linker lines, but why all that=20 effort? The security/heimdal port has dependencies registered, so that=20 works fine to link. (The base heimdal must be removed so it won't be picked = up by the linker) Is there any way to "force" dependencies into a lib? If so, I could=20 register -lasn1 in libpq.som and everything would be dandy. If you need to fresh your memory up, here's the original question: > I'm having some difficulties using postgresql version 8.0.x with heimdal > installed from /usr/src (i.e. the base system). This is on FreeBSD-5.x. > When using the port of heimdal, from /usr/ports/security/heimdal, it > works. > > The port install into /usr/local, whereas the base system is in /usr. > Here's the difference between the heimdal port and the heimdal > distributed in the base: > > $ ldd /usr/local/lib/libkrb5.so > /usr/local/lib/libkrb5.so: > libcrypto.so.3 =3D> /lib/libcrypto.so.3 (0x281b3000) > libasn1.so.6 =3D> /usr/local/lib/libasn1.so.6 (0x282c4000) > libroken.so.16 =3D> /usr/local/lib/libroken.so.16 (0x282ea000) > libcrypt.so.2 =3D> /lib/libcrypt.so.2 (0x282f8000) > libcom_err.so.2 =3D> /usr/lib/libcom_err.so.2 (0x28311000) > $ ldd /usr/lib/libkrb5.so > /usr/lib/libkrb5.so: > $ > > Same goes for the other heimdal libs, libasn1.so and libcom_err.so. > > I don't know enough about linking details, but shouldn't the > /usr/lib/libkrb5.so lib also contain info about libraries it depends on? ... Regards, Palle From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 00:40:30 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0ACD416A41F for ; Mon, 31 Oct 2005 00:40:30 +0000 (GMT) (envelope-from freebsd-stable@auscert.org.au) Received: from titania.auscert.org.au (gw.auscert.org.au [203.5.112.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72DF343D46 for ; Mon, 31 Oct 2005 00:40:28 +0000 (GMT) (envelope-from freebsd-stable@auscert.org.au) Received: from app.auscert.org.au (app [10.0.1.192]) by titania.auscert.org.au (8.12.10/8.12.10) with ESMTP id j9V0dBio044733; Mon, 31 Oct 2005 10:39:11 +1000 (EST) Received: from app.auscert.org.au (localhost.auscert.org.au [127.0.0.1]) by app.auscert.org.au (8.13.1/8.13.1) with ESMTP id j9V0eRs3019720; Mon, 31 Oct 2005 10:40:27 +1000 (EST) (envelope-from freebsd-stable@auscert.org.au) Message-Id: <200510310040.j9V0eRs3019720@app.auscert.org.au> To: freebsd-stable@freebsd.org from: freebsd-stable@auscert.org.au In-Reply-To: Your message of "Wed, 26 Oct 2005 09:06:52 +0200." <20051026070652.GB440@pc5-179.lri.fr> Date: Mon, 31 Oct 2005 10:40:27 +1000 Cc: Subject: Re: 6.0 RC1 usbd.conf (and installation comments) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 00:40:30 -0000 > Just a few words on that point ... after some use of mergemaster, it > seems to me that a big part of /etc have to be update blindly for most > users (things in rc.d, and some other places where there's files that > haven't to changed or that are system script that most users won't > modify.) > > I hadn't time to add a possibility for mergemaster to perform blind > updates of such files[1], but it seems not so complicated to do so. > > Does anyone else thinks that's an interesting idea ? > > [1] : providing a list of directories and/or files to mergemaster for > which blind updates could be perform, for example ... Interesting, but for mine it sounds like more complexity than needed. I'd be happy with a simple option to automatically replace any files with newer CVS ID, and just make sure I took a backup of /etc before beginning. cheers, joel -- Joel Hatton -- Security Analyst | Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland | WWW: www.auscert.org.au Qld 4072 Australia | Email: auscert@auscert.org.au From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 00:50:43 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D1A916A41F for ; Mon, 31 Oct 2005 00:50:43 +0000 (GMT) (envelope-from freebsd-stable@auscert.org.au) Received: from titania.auscert.org.au (gw.auscert.org.au [203.5.112.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BD9F43D48 for ; Mon, 31 Oct 2005 00:50:42 +0000 (GMT) (envelope-from freebsd-stable@auscert.org.au) Received: from app.auscert.org.au (app [10.0.1.192]) by titania.auscert.org.au (8.12.10/8.12.10) with ESMTP id j9V0nPio044772; Mon, 31 Oct 2005 10:49:25 +1000 (EST) Received: from app.auscert.org.au (localhost.auscert.org.au [127.0.0.1]) by app.auscert.org.au (8.13.1/8.13.1) with ESMTP id j9V0oc8n020913; Mon, 31 Oct 2005 10:50:38 +1000 (EST) (envelope-from freebsd-stable@auscert.org.au) Message-Id: <200510310050.j9V0oc8n020913@app.auscert.org.au> To: freebsd-stable@freebsd.org from: Joel Hatton In-Reply-To: Message from Joel Hatton of "Wed, 26 Oct 2005 10:46:43 +1000." <200510260046.j9Q0khYU004317@app.auscert.org.au> Date: Mon, 31 Oct 2005 10:50:38 +1000 Cc: Subject: 6.0 RC1 dhclient (was Re: 6.0 RC1 usbd.conf (and installation comments)) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 00:50:44 -0000 I said: > > DHCP configuration - for some reason my machine didn't acquire a > default route on boot, but rerunning the dhclient script after > boot caused the interface to be set up again successfully. I > haven't looked into this further yet, I'll repost if it is a > repeatable problem. This issue is repeatable. Although I haven't had time to trace it further, I have worked out that if I configure my dhcp interface with an alias eg ifconfig_em0_alias0 a default route is not added; after commenting that line in /etc/rc.conf the route is ok again on reboot. I've tried alternating between commented/uncommented with consistent success/fail results so I guess this needs looking at. joel -- Joel Hatton -- Security Analyst | Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland | WWW: www.auscert.org.au Qld 4072 Australia | Email: auscert@auscert.org.au From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 01:54:10 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0F1516A41F for ; Mon, 31 Oct 2005 01:54:10 +0000 (GMT) (envelope-from Mark_Andrews@isc.org) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AB8443D67 for ; Mon, 31 Oct 2005 01:54:07 +0000 (GMT) (envelope-from Mark_Andrews@isc.org) Received: from drugs.dv.isc.org (localhost [IPv6:::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id 8C066677F9 for ; Mon, 31 Oct 2005 01:54:04 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.13.4/8.13.1) with ESMTP id j9V1qqOh041103; Mon, 31 Oct 2005 12:53:01 +1100 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200510310153.j9V1qqOh041103@drugs.dv.isc.org> To: Joel Hatton From: Mark Andrews In-reply-to: Your message of "Mon, 31 Oct 2005 10:50:38 +1000." <200510310050.j9V0oc8n020913@app.auscert.org.au> Date: Mon, 31 Oct 2005 12:52:52 +1100 Sender: Mark_Andrews@isc.org Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 RC1 dhclient (was Re: 6.0 RC1 usbd.conf (and installation comments)) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 01:54:10 -0000 > I said: > > > > DHCP configuration - for some reason my machine didn't acquire a > > default route on boot, but rerunning the dhclient script after > > boot caused the interface to be set up again successfully. I > > haven't looked into this further yet, I'll repost if it is a > > repeatable problem. > > This issue is repeatable. Although I haven't had time to trace it further, > I have worked out that if I configure my dhcp interface with an alias eg > ifconfig_em0_alias0 a default route is not added; after commenting that > line in /etc/rc.conf the route is ok again on reboot. I've tried > alternating between commented/uncommented with consistent success/fail > results so I guess this needs looking at. > > joel ALIAS DECLARATIONS alias { declarations ... } Some DHCP clients running TCP/IP roaming protocols may require that in addition to the lease they may acquire via DHCP, their interface also be configured with a predefined IP alias so that they can have a perma- nent IP address even while roaming. The Internet Software Consortium DHCP client doesn't support roaming with fixed addresses directly, but in order to facilitate such experimentation, the dhcp client can be set up to configure an IP alias using the alias declaration. The alias declaration resembles a lease declaration, except that options other than the subnet-mask option are ignored by the standard client configuration script, and expiry times are ignored. A typical alias declaration includes an interface declaration, a fixed-address declaration for the IP alias address, and a subnet-mask option declara- tion. A medium statement should never be included in an alias decla- ration. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 02:05:19 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5394916A41F for ; Mon, 31 Oct 2005 02:05:19 +0000 (GMT) (envelope-from vvelox@vvelox.net) Received: from S1.cableone.net (s1.cableone.net [24.116.0.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE90A43D45 for ; Mon, 31 Oct 2005 02:05:18 +0000 (GMT) (envelope-from vvelox@vvelox.net) Received: from vixen42.vulpes (unverified [24.119.122.41]) by S1.cableone.net (CableOne SMTP Service S1) with ESMTP id 35768589 for ; Sun, 30 Oct 2005 19:05:37 -0700 Date: Sun, 30 Oct 2005 20:09:42 -0600 From: "Z.C.B." To: freebsd-stable@freebsd.org Message-ID: <20051030200942.682494c5@vixen42.vulpes> In-Reply-To: <20051029000835.6289fedc@vixen42.vulpes> References: <20051029000835.6289fedc@vixen42.vulpes> X-Mailer: Sylpheed-Claws 1.9.15 (GTK+ 2.6.10; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-NotAscii: charset=us-ascii X-IP-stats: Incoming Last 1, First 165, in=274, out=0, spam=0 X-External-IP: 24.119.122.41 X-Abuse-Info: Send abuse complaints to abuse@cableone.net Subject: Re: releng_5_4 install problems and a question about a possible work around (solved) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 02:05:19 -0000 On Sat, 29 Oct 2005 00:08:35 -0500 Vulpes Velox wrote: > Well just working on installing Freebsd 5.4 on a Toshiba Tecra M3. > The problem I have run into is that it hangs during the loading the > kernel up. It hangs right after seeing uhci. FreeBSD 6.0 can get > past it, but decided to whack the MBR in the proccess even when > told not to mess with it. > > I was wondering what it would take to rework the 5.4 install cd to > it had a 5stable kernel. IIRC I remember seeing some changes to usb > code on it some time post 5.4. Any ways what I did was to get around the problem of it the partition table and/or mbr being screwed up by 6.0 was just use partition magic to convert the ntfs partition to fat32. What this did is it allows me to use the freebsd boot selector. Then I just installed 6.0. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 02:27:50 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D02E016A41F for ; Mon, 31 Oct 2005 02:27:50 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B74343D45 for ; Mon, 31 Oct 2005 02:27:50 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by wproxy.gmail.com with SMTP id i35so425164wra for ; Sun, 30 Oct 2005 18:27:49 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XOoeSzahnXtrUVYeIB3mQJGiLdlBESiKAuEKScst5jB0qAocl+L5vsnTU1a9VIqwdfLB31W6R5iduv3sFm6aorOtah8qVAWgrBtvzOB1NnkvumF/Gt19OdQMFzOsXbxXl31MX7+6qEEUtSAmoeopfR81tWMbRNcp9rGWY3qz9Fc= Received: by 10.65.116.4 with SMTP id t4mr1166765qbm; Sun, 30 Oct 2005 18:27:49 -0800 (PST) Received: by 10.65.105.11 with HTTP; Sun, 30 Oct 2005 18:27:49 -0800 (PST) Message-ID: Date: Mon, 31 Oct 2005 10:27:49 +0800 From: Jiawei Ye To: Bryan Fullerton In-Reply-To: <35de0c300510291159h5b9d62edw19751cc3859a0b3f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <436116D3.908@samsco.org> <621b657f0510280859g14f5cfc6yf933cda94b580f33@mail.gmail.com> <43624C82.5050407@t-hosting.hu> <200510281213.01222.jkim@FreeBSD.org> <35de0c300510291159h5b9d62edw19751cc3859a0b3f@mail.gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 02:27:50 -0000 On 10/30/05, Bryan Fullerton wrote: > > I have raised this issue in the past, but no one responded. > > Did you submit a PR? > > Bryan No I didn't. There was no response so I figured maybe I was the only one affected. Jiawei -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 06:51:06 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76DFB16A41F for ; Mon, 31 Oct 2005 06:51:06 +0000 (GMT) (envelope-from kolicz@EUnet.yu) Received: from smtpclu-6.eunet.yu (smtpclu-6.eunet.yu [194.247.192.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id C019A43D4C for ; Mon, 31 Oct 2005 06:51:05 +0000 (GMT) (envelope-from kolicz@EUnet.yu) Received: from faust.net (P-14.88.EUnet.yu [213.240.14.88]) by smtpclu-6.eunet.yu (8.12.11/8.12.11) with ESMTP id j9V6p1Lg002191 for ; Mon, 31 Oct 2005 07:51:02 +0100 Received: by faust.net (Postfix, from userid 1001) id 8364B4206; Mon, 31 Oct 2005 07:48:55 +0100 (CET) Date: Mon, 31 Oct 2005 07:48:55 +0100 From: Zoran Kolic To: freebsd-stable@freebsd.org Message-ID: <20051031064855.GA644@faust.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scan: EUnet-AVAS-Milter X-AVAS-Virus-Status: clean X-Spam-Checker: EUnet-AVAS-Milter X-AVAS-Spam-Score: 0.0 X-AVAS-Spam-Symbols: BAYES_56 Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 06:51:06 -0000 Hi all! Since the amount of files goes up, there is a chance to mess something with the best in mind. Personaly, I like simple style of making new kernel. Defaults? OK if works well, without complaints for people, who need nothing more than necessary. What's about "compat" options for clean install from medium? Do I need "freebsd4 and 5" if I use only ports for ie amd64? Do I go into failure with something of libraries? And, more curious to me, "ahc_ahd_reg_ _pretty_print"? If I don't make any debug output, could I erase it from my kernel? "Sysv..." memory, queue and semaphores? Sorry if I asked already answered issue. Best regards Zoran From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 07:26:35 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE8AB16A41F for ; Mon, 31 Oct 2005 07:26:35 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8124643D49 for ; Mon, 31 Oct 2005 07:26:34 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr11.xs4all.nl (8.13.3/8.13.3) with ESMTP id j9V7QSjh093678; Mon, 31 Oct 2005 08:26:28 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 261B9B84D; Mon, 31 Oct 2005 08:26:28 +0100 (CET) Date: Mon, 31 Oct 2005 08:26:28 +0100 From: Roland Smith To: Pete Slagle Message-ID: <20051031072628.GA46091@slackbox.xs4all.nl> Mail-Followup-To: Pete Slagle , freebsd-stable@freebsd.org References: <4364A727.9090106@gmx.de> <436555A1.3010305@box559.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline In-Reply-To: <436555A1.3010305@box559.com> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 07:26:35 -0000 --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 30, 2005 at 03:22:09PM -0800, Pete Slagle wrote: > >>I've seen that 'GENERIC' file has been modified, moving some lines to > >>'DEFAULTS': > >> > >>device isa > >> > >>device mem # Memory and kernel memory devices = =20 > >>device io # I/O device > >> > >>Why? > >>What does it mean? Should we include 'DEFAULTS' in our customized=20 > >>'GENERIC'? > >>Or those lines are no more mandatory? > >> > > > >No, you don't need to include 'DEFAULTS', config(8) will take care of=20 > >that for you. > > > >http://docs.FreeBSD.org/cgi/mid.cgi?200510271713.j9RHDNTo013082 > > > >AFAICT, this was done in order to automatically include devices which=20 > >are essential in most cases so less experienced users won't accidentally= =20 > >break their systems and later complain that e.g. X doesn't work anymore. >=20 > The whole mechanism seems like an obvious POLA violation. All the more= =20 > so without a note in UPDATING. Agreed. A heads-up in the beginning of GENERIC would also be nice. =20 > Personally, I prefer less automated "help." In general, it might be=20 > better to encourage those who need a nanny to run Windows, leaving=20 > FreeBSD unencumbered for those who don't. IMHO. HMO exactly. Spreading the kernel configuration over two different files that interact in a non-obvious way is a PITA. Do I now have to create two files to build a custom kernel? Let's keep it simple and stick to one kernel config file, please. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZcckEnfvsMMhpyURAj6fAJ44fYXu8CT4wOz0EH4UnxVoM1oHSACghmie JNGpQnsNf24LJzQ5due+hrg= =6lJi -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z-- From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 08:12:03 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E66BA16A41F for ; Mon, 31 Oct 2005 08:12:03 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63BAD43D46 for ; Mon, 31 Oct 2005 08:12:03 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1EWUlt-000B8i-Fm; Mon, 31 Oct 2005 10:12:01 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Pete Slagle In-reply-to: Your message of Sun, 30 Oct 2005 15:22:09 -0800 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Oct 2005 10:12:01 +0200 From: Danny Braniss Message-ID: Cc: freebsd-stable@freebsd.org Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 08:12:04 -0000 > >> I've seen that 'GENERIC' file has been modified, moving some lines to > >> 'DEFAULTS': > >> > >> device isa > >> > >> device mem # Memory and kernel memory devices > >> device io # I/O device > >> > >> Why? > >> What does it mean? Should we include 'DEFAULTS' in our customized > >> 'GENERIC'? > >> Or those lines are no more mandatory? > >> > > > > No, you don't need to include 'DEFAULTS', config(8) will take care of > > that for you. > > > > http://docs.FreeBSD.org/cgi/mid.cgi?200510271713.j9RHDNTo013082 > > > > AFAICT, this was done in order to automatically include devices which > > are essential in most cases so less experienced users won't accidentally > > break their systems and later complain that e.g. X doesn't work anymore. > > The whole mechanism seems like an obvious POLA violation. All the more > so without a note in UPDATING. > > Personally, I prefer less automated "help." In general, it might be > better to encourage those who need a nanny to run Windows, leaving > FreeBSD unencumbered for those who don't. IMHO. i agree 100%, i hate wizardy/black-magic, and this 'fix' falls in that class. Why was a 5ton hammer used to fix non existing problem? a small comment like 'you better keep these lines to make X happy' would have sufficed. my .5c, btw, im a happy freebsd user! danny From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 08:28:11 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D8DB16A41F for ; Mon, 31 Oct 2005 08:28:11 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D612A43D48 for ; Mon, 31 Oct 2005 08:28:10 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id B57F01A3C1A; Mon, 31 Oct 2005 00:28:10 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3B8A8512CE; Mon, 31 Oct 2005 03:28:08 -0500 (EST) Date: Mon, 31 Oct 2005 03:28:08 -0500 From: Kris Kennaway To: Danny Braniss Message-ID: <20051031082807.GA68204@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mYCpIKhGyMATD0i+" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 08:28:11 -0000 --mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Oct 31, 2005 at 10:12:01AM +0200, Danny Braniss wrote: > i agree 100%, i hate wizardy/black-magic, and this 'fix' falls in that > class. Why was a 5ton hammer used to fix non existing problem? > a small comment like 'you better keep these lines to make X happy' > would have sufficed. You've clearly never spent much time on the FreeBSD support forums, where every few days someone posts for help 1) with an error caused by removing one of those "Do not remove this!" lines, and 2) for help on getting X working when they forgot to add /dev/io and /dev/mem to their kernel. Those of us who spend a lot of time answering such questions will surely welcome the change, since it will hopefully reduce our workload. Kris --mYCpIKhGyMATD0i+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZdWWWry0BWjoQKURApLcAKDRqElRJUIw6HJy1JzSgtx2Tcq0gQCcD8Ea UF3bYHG6Iyhx3Y9OHpwYzSA= =RrTJ -----END PGP SIGNATURE----- --mYCpIKhGyMATD0i+-- From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 08:46:39 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3007516A41F for ; Mon, 31 Oct 2005 08:46:39 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE2BA43D45 for ; Mon, 31 Oct 2005 08:46:38 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1EWVJN-000CHW-JS; Mon, 31 Oct 2005 10:46:37 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Kris Kennaway In-reply-to: Your message of Mon, 31 Oct 2005 03:28:08 -0500 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Oct 2005 10:46:37 +0200 From: Danny Braniss Message-ID: Cc: freebsd-stable@freebsd.org Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 08:46:39 -0000 > You've clearly never spent much time on the FreeBSD support forums, > where every few days someone posts for help > > 1) with an error caused by removing one of those "Do not remove this!" > lines, and > > 2) for help on getting X working when they forgot to add /dev/io and > /dev/mem to their kernel. > > Those of us who spend a lot of time answering such questions will > surely welcome the change, since it will hopefully reduce our > workload. > I understand - and appreciate, your problem. I still think that the solution is wrong. I'm now checking, since it seems that io and mem are loadable modules, that maybe the X start, or rc.d will make sure that these modules are loaded? So that if someone who removes them from the MYKERNCONF is still protected? danny From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 08:50:45 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F11C16A41F for ; Mon, 31 Oct 2005 08:50:45 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5015643D48 for ; Mon, 31 Oct 2005 08:50:45 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 3498C1A3C25; Mon, 31 Oct 2005 00:50:45 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 70FF3512CE; Mon, 31 Oct 2005 03:50:44 -0500 (EST) Date: Mon, 31 Oct 2005 03:50:44 -0500 From: Kris Kennaway To: Danny Braniss Message-ID: <20051031085044.GA79715@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PNTmBPCT7hxwcZjr" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 08:50:45 -0000 --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 31, 2005 at 10:46:37AM +0200, Danny Braniss wrote: >=20 > > You've clearly never spent much time on the FreeBSD support forums, > > where every few days someone posts for help > >=20 > > 1) with an error caused by removing one of those "Do not remove this!" > > lines, and > >=20 > > 2) for help on getting X working when they forgot to add /dev/io and > > /dev/mem to their kernel. > >=20 > > Those of us who spend a lot of time answering such questions will > > surely welcome the change, since it will hopefully reduce our > > workload. > >=20 > I understand - and appreciate, your problem. I still think that > the solution is wrong. I'm now checking, since it seems that io and > mem are loadable modules, that maybe the X start, or rc.d will make sure > that these modules are loaded? So that if someone who removes them from t= he > MYKERNCONF is still protected? Many users who build custom kernels do not build modules, since they want to compile everything they (think they) need into the kernel statically. Kris --PNTmBPCT7hxwcZjr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZdrjWry0BWjoQKURAjfvAKCOLDlNpvuz5CnDucLOyrmVw5GkPQCgjEJW KqsEbM4Xf8XE+Ip5Am3NHLY= =qoDc -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr-- From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 09:18:40 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1680916A41F for ; Mon, 31 Oct 2005 09:18:40 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 577DA43D46 for ; Mon, 31 Oct 2005 09:18:39 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1EWVoM-000D0z-6B; Mon, 31 Oct 2005 11:18:38 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Kris Kennaway In-reply-to: Your message of Mon, 31 Oct 2005 03:50:44 -0500 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Oct 2005 11:18:38 +0200 From: Danny Braniss Message-ID: Cc: freebsd-stable@freebsd.org Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 09:18:40 -0000 [...] > Many users who build custom kernels do not build modules, since they > want to compile everything they (think they) need into the kernel > statically. you probably know many scenarios that i - thankfully - am no aware of, but by creating the magic DEFAULTS file the problem still exits! What will prevent from Joe Shootmyfoot to comment out the lines in DEFAULTS? by the way, by just looking at DEFAULTS, there is no warning of the concequenses. a line like: ** DON'T TOUCH ANYTHING HERE UNLESS YOU REALY, REALY ** KNOW WHAT YOU ARE DOING might help. danny From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 09:36:27 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D67FF16A420 for ; Mon, 31 Oct 2005 09:36:27 +0000 (GMT) (envelope-from brad@stop.mail-abuse.org) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68C1843D46 for ; Mon, 31 Oct 2005 09:36:27 +0000 (GMT) (envelope-from brad@stop.mail-abuse.org) Received: from [10.0.1.210] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.11/8.12.3) with ESMTP id j9V9aGBH089382; Mon, 31 Oct 2005 04:36:17 -0500 (EST) (envelope-from brad@stop.mail-abuse.org) Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Mon, 31 Oct 2005 10:36:09 +0200 To: Danny Braniss From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 09:36:27 -0000 At 11:18 AM +0200 2005-10-31, Danny Braniss wrote: > you probably know many scenarios that i - thankfully - am no > aware of, but by creating the magic DEFAULTS file the problem > still exits! What will prevent from Joe Shootmyfoot to comment out > the lines in DEFAULTS? chflags schg DEFAULTS -- Brad Knowles, "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See for more info. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 09:52:06 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F2D116A421 for ; Mon, 31 Oct 2005 09:52:06 +0000 (GMT) (envelope-from neil.hoggarth@physiol.ox.ac.uk) Received: from relay1.mail.ox.ac.uk (relay1.mail.ox.ac.uk [129.67.1.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56B8943D64 for ; Mon, 31 Oct 2005 09:52:03 +0000 (GMT) (envelope-from neil.hoggarth@physiol.ox.ac.uk) Received: from wren.physiol.ox.ac.uk ([163.1.249.100] helo=mail.physiol.ox.ac.uk) by relay1.mail.ox.ac.uk with esmtp (Exim 4.52) id 1EWWKf-0003Nf-5e for freebsd-stable@freebsd.org; Mon, 31 Oct 2005 09:52:01 +0000 Received: from saros.physiol (saros.physiol [163.1.249.131]) by mail.physiol.ox.ac.uk (8.12.10/8.12.8) with ESMTP id j9V9q0Wv022664 for ; Mon, 31 Oct 2005 09:52:01 GMT Date: Mon, 31 Oct 2005 09:52:00 +0000 (GMT) From: Neil Hoggarth X-X-Sender: njh@saros.physiol To: freebsd-stable@freebsd.org In-Reply-To: <790a9fff0510240909o5f3d5accvfa55a4f228b77629@mail.gmail.com> Message-ID: References: <790a9fff0510240909o5f3d5accvfa55a4f228b77629@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: 6.0 RC1 - problems with HighPoint RocketRAID 1640? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 09:52:06 -0000 On Mon, 24 Oct 2005, Scot Hetzel wrote: > On 10/24/05, Neil Hoggarth wrote: >> I tried a source-upgrade from RELENG_5 to RELENG_6 over the weekend >> (cvsuped RELENG_6 at around 10am Sunday morning, UK time). I was using a >> GENERIC kernel. The procedure from UPDATING was working fine, up to the >> point when I ran "make installworld". The system froze solid very early >> in the installworld process (the comment printed on the screen prior to >> the freeze suggests that it was copying, or preparing to copy, include >> files). > > Did you reboot after installing the 6.0 Kernel and before the installworld? > This ensures that the 6.0 Kernel works on your system before the 6.0 > binaries are installed. Yes. I'd successfully rebooted single-user on the 6.0 kernel, and run "mergemaster -p" without incident. >> Any pointers on how I might go about diagnosing this, and hopefully >> producing a more useful problem report concerning the difficultes that >> my hardware seems to have with 6.0 kernels? >> > You'll need to ensure that you have the debugging options enabled in > the 6.0 kernel, this way your kernel will hopefully break to the > debugger when the problem reoccurs. > > See the handbooks chapter on debugging for more details. I had another go this weekend. I created a new kernel config by adding the following to GENERIC: options KDB options DDB options GDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS On this kernel the "boot single-user / mergemaster -p / make installworld / mergemaster -i" sequence worked okay. Unfortunately the system wedged on me once again when I rebooted multi-user following the install (system got as far as presenting a login prompt, but was completely unresponsive to the keyboard or the network there after). After reset the system would repeatably lock up just after the point where the SATA disks are probed and geom_mirror picks up my mirroring setup. The debugging kernel doesn't panic, break to the debugger, or print any additional diagnostics that I can see. CTRL+ALT+ESC does not break to the debugger. I was going to try online debugging using remote GDB (as described in section 10.6 of the Developers' Handbook), using my laptop (which I have successfully upgraded to RELENG_6) as the debugging machine; however it appears that "gdb -k" doesn't work any more? I get: gdb: unrecognized option `-k' Use `gdb --help' for a complete list of options. Regards, -- Neil Hoggarth Departmental Computing Manager Laboratory of Physiology http://www.physiol.ox.ac.uk/~njh/ University of Oxford, UK From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 10:02:01 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0293716A41F for ; Mon, 31 Oct 2005 10:02:01 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC3FF43D66 for ; Mon, 31 Oct 2005 10:01:57 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1EWWUG-000Ek7-OT; Mon, 31 Oct 2005 12:01:56 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Brad Knowles In-Reply-To: Message from Brad Knowles of "Mon, 31 Oct 2005 10:36:09 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Oct 2005 12:01:56 +0200 From: Danny Braniss Message-ID: Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 10:02:01 -0000 > At 11:18 AM +0200 2005-10-31, Danny Braniss wrote: > > > you probably know many scenarios that i - thankfully - am no > > aware of, but by creating the magic DEFAULTS file the problem > > still exits! What will prevent from Joe Shootmyfoot to comment out > > the lines in DEFAULTS? > > chflags schg DEFAULTS yes if it's you, but not if im Joe Shootmyfoot! danny From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 15:06:09 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C7C616A420 for ; Mon, 31 Oct 2005 15:06:09 +0000 (GMT) (envelope-from brad@stop.mail-abuse.org) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC99543D45 for ; Mon, 31 Oct 2005 15:06:08 +0000 (GMT) (envelope-from brad@stop.mail-abuse.org) Received: from [10.0.1.210] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.11/8.12.3) with ESMTP id j9VF60jc013029; Mon, 31 Oct 2005 10:06:01 -0500 (EST) (envelope-from brad@stop.mail-abuse.org) Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Mon, 31 Oct 2005 15:47:55 +0200 To: Danny Braniss From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" Cc: Brad Knowles , freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 15:06:09 -0000 At 12:01 PM +0200 2005-10-31, Danny Braniss wrote: >> > you probably know many scenarios that i - thankfully - am no >> > aware of, but by creating the magic DEFAULTS file the problem >> > still exits! What will prevent from Joe Shootmyfoot to comment out >> > the lines in DEFAULTS? >> >> chflags schg DEFAULTS > > yes if it's you, but not if im Joe Shootmyfoot! At least it will slow them down. They road to shooting themselves in the foot will dead-end, and they'll be forced to turn left or right before they can continue towards that goal. Put a big enough roadblock there, and most of those idiots will probably manage to avoid shooting themselves in the foot. Not all, of course. But most. -- Brad Knowles, "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See for more info. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 15:18:11 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 127E616A41F for ; Mon, 31 Oct 2005 15:18:11 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4ED343D46 for ; Mon, 31 Oct 2005 15:18:10 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 8A252A2FC8; Mon, 31 Oct 2005 16:18:09 +0100 (CET) Received: by hammer.stack.nl (Postfix, from userid 333) id 77F2C61F5; Mon, 31 Oct 2005 16:18:09 +0100 (CET) Date: Mon, 31 Oct 2005 16:18:09 +0100 From: Marc Olzheim To: Scott Long Message-ID: <20051031151809.GA83253@stack.nl> References: <436116D3.908@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline In-Reply-To: <436116D3.908@samsco.org> X-Operating-System: FreeBSD hammer.stack.nl 6.0-BETA4 FreeBSD 6.0-BETA4 X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.11 Cc: stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 15:18:11 -0000 --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Oct 27, 2005 at 12:05:07PM -0600, Scott Long wrote: > Everyone is still welcome to update their sources on the RELENG_6_0 > branch and provide feedback for the next 48 hours or so. The release > will likely be announced by the end of the weekend or early next > week, at the latest. Anyone having updates for my showstopper page, please, notify me... http://www.stack.nl/%7Emarcolz/FreeBSD/showstoppers.html We are still installing new servers with 4.x, because I haven't seen a really stable FreeBSD-stable release since... This includes current RELENG_6_0. Marc --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZjWxezjnobFOgrERAr9ZAKCeCxEHGlLy5+DZ7JldmeRYSmUkswCff04P G1EAM2xwxA0MIaxkZiHCP6A= =FtHL -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q-- From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 15:36:43 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFB6016A41F for ; Mon, 31 Oct 2005 15:36:43 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57CF543D46 for ; Mon, 31 Oct 2005 15:36:42 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id j9VFafXF040899; Mon, 31 Oct 2005 08:36:41 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43663A0A.4040608@samsco.org> Date: Mon, 31 Oct 2005 08:36:42 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marc Olzheim References: <436116D3.908@samsco.org> <20051031151809.GA83253@stack.nl> In-Reply-To: <20051031151809.GA83253@stack.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 15:36:44 -0000 Marc Olzheim wrote: > On Thu, Oct 27, 2005 at 12:05:07PM -0600, Scott Long wrote: > >> Everyone is still welcome to update their sources on the RELENG_6_0 >> branch and provide feedback for the next 48 hours or so. The release >> will likely be announced by the end of the weekend or early next >> week, at the latest. > > > Anyone having updates for my showstopper page, please, notify me... > > http://www.stack.nl/%7Emarcolz/FreeBSD/showstoppers.html > > We are still installing new servers with 4.x, because I haven't seen a > really stable FreeBSD-stable release since... This includes current > RELENG_6_0. > > Marc The pty problem is likely a side effect of known locking problems with ttys and ptys in general. This probably the weakest part of the kernel right now and I don't know of a good work-around for apps that use these extensively. That said, there doesn't seem to be much of a problem with casual use; I use screen(1) quite a bit on my production 6.0-RC mailserver+firewall. Is the 'VM/VFS overruns' item still a problem? That was likely fixed a couple of months ago. If not then it's definitely something that I'll track for the 6.1 release. The ACPI+sio problem is known. I have a motherboard with a similar problem, though a different brand than yours. I solved it by removing the ACPI attachment from the sio code. The better solution is to allow loader hints to override ACPI hints. I tried talking to John Baldwin about this but didn't get much of a response. I haven't seen ktrace discussed much. Peter Edwards is welcome to pass his patch around some more and commit it if he wants. GDB problems are numerous, and what we really need is for someone with interest in it to spend some quality time on it. Scott From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 16:01:54 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 554F816A41F for ; Mon, 31 Oct 2005 16:01:54 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA37343D45 for ; Mon, 31 Oct 2005 16:01:51 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id D91E0A2FCC; Mon, 31 Oct 2005 17:01:50 +0100 (CET) Received: by hammer.stack.nl (Postfix, from userid 333) id BF56661F5; Mon, 31 Oct 2005 17:01:50 +0100 (CET) Date: Mon, 31 Oct 2005 17:01:50 +0100 From: Marc Olzheim To: Scott Long Message-ID: <20051031160150.GB87483@stack.nl> References: <436116D3.908@samsco.org> <20051031151809.GA83253@stack.nl> <43663A0A.4040608@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline In-Reply-To: <43663A0A.4040608@samsco.org> X-Operating-System: FreeBSD hammer.stack.nl 6.0-BETA4 FreeBSD 6.0-BETA4 X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.11 Cc: Marc Olzheim , stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 16:01:54 -0000 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 31, 2005 at 08:36:42AM -0700, Scott Long wrote: > >Anyone having updates for my showstopper page, please, notify me... > > > >http://www.stack.nl/%7Emarcolz/FreeBSD/showstoppers.html > > The pty problem is likely a side effect of known locking problems with > ttys and ptys in general. This probably the weakest part of the kernel > right now and I don't know of a good work-around for apps that use these > extensively. That said, there doesn't seem to be much of a problem with= =20 > casual use; I use screen(1) quite a bit on my production 6.0-RC=20 > mailserver+firewall. I know it doesn't trigger too often for most users, but still, for us, once a week per server on 2 production servers we installed FreeBSD 5 and 6 on, is way too often. :-( More so because these kernel panics on SMP systems tend to utterly destroy soft-updates consistency giving fsck quite a workout and resulting in data loss... > Is the 'VM/VFS overruns' item still a problem? That was likely fixed a= =20 > couple of months ago. If not then it's definitely something that I'll > track for the 6.1 release. I'll retest that one, but it wasn't fixed yet in -CURRENT of a month ago. > The ACPI+sio problem is known. I have a motherboard with a similar=20 > problem, though a different brand than yours. I solved it by removing > the ACPI attachment from the sio code. The better solution is to allow > loader hints to override ACPI hints. I tried talking to John Baldwin > about this but didn't get much of a response. I've tried all suggestions so far, but to no avail on most servers. Too many broken ACPI implementations I fear... Too bad motherboard vendors don't take the time to push proper software in their flash. In any case, thanks for thinking along with me. :-) Marc --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZj/uezjnobFOgrERAs47AKDDpE3d3OLSkTMdz7JVe97z3t4suwCfbVNg ayoAAlb5tyWYzlAGoxLVsKM= =CzJq -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G-- From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 17:34:42 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4E6916A41F for ; Mon, 31 Oct 2005 17:34:42 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4258543D49 for ; Mon, 31 Oct 2005 17:34:42 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9VHY8uO005589; Mon, 31 Oct 2005 10:34:08 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 31 Oct 2005 10:34:08 -0700 (MST) Message-Id: <20051031.103408.71093019.imp@bsdimp.com> To: marcolz@stack.nl From: Warner Losh In-Reply-To: <20051031160150.GB87483@stack.nl> References: <20051031151809.GA83253@stack.nl> <43663A0A.4040608@samsco.org> <20051031160150.GB87483@stack.nl> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 31 Oct 2005 10:34:11 -0700 (MST) Cc: stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 17:34:42 -0000 > > The ACPI+sio problem is known. I have a motherboard with a similar > > problem, though a different brand than yours. I solved it by removing > > the ACPI attachment from the sio code. The better solution is to allow > > loader hints to override ACPI hints. I tried talking to John Baldwin > > about this but didn't get much of a response. > > I've tried all suggestions so far, but to no avail on most servers. Too > many broken ACPI implementations I fear... Too bad motherboard vendors > don't take the time to push proper software in their flash. Right now acpi tells us there's a device, and we use it. Loader hints should be used to map locations to device instances. It is more general than just ACPI, however. People want to bind sio to a specific port that comes out the back. People also want to bind rl0 to the card in slot 3. Consider my system: sio0 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.SBRG.UAR1 sio1 pnpinfo _HID=PNP0501 _UID=2 at handle=\_SB_.PCI0.SBRG.UAR2 On this system, UAR1 is the port that comes out the back, so I have what I want. However, I'd like to be able to say: hint.sio.0.at="acpi" hint.sio.0.location="\_SB_.PCI0.SBRG.UAR2" or hint.sio.0.at="acpi" hint.sio.0.location="UAR2" or hint.fxp.0.at="pci" hint.fxp.0.location="bus=2 slot=3 function=0" hint.fxp.1.at="pci" hint.fxp.1.location="pci2:2:0" Since we really want to map the devices in some arbitrary ACPI tree to instances in the system, rather than mapping devices that happen to live at a specific resource address to specific instances in the tree. However, there are a number of issues in doing this generically and with error cases. How does one deal with the different syntaxes? What extensions to the newbus system are there? etc. Warner From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 17:42:41 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A732716A41F for ; Mon, 31 Oct 2005 17:42:41 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE99F43D48 for ; Mon, 31 Oct 2005 17:42:36 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.21] (rat.samsco.home [192.168.254.21]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id j9VHgWh9054528; Mon, 31 Oct 2005 10:42:33 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43665788.4070807@samsco.org> Date: Mon, 31 Oct 2005 10:42:32 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050321 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Warner Losh References: <20051031151809.GA83253@stack.nl> <43663A0A.4040608@samsco.org> <20051031160150.GB87483@stack.nl> <20051031.103408.71093019.imp@bsdimp.com> In-Reply-To: <20051031.103408.71093019.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: marcolz@stack.nl, stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 17:42:41 -0000 Warner Losh wrote: >>>The ACPI+sio problem is known. I have a motherboard with a similar >>>problem, though a different brand than yours. I solved it by removing >>>the ACPI attachment from the sio code. The better solution is to allow >>>loader hints to override ACPI hints. I tried talking to John Baldwin >>>about this but didn't get much of a response. >> >>I've tried all suggestions so far, but to no avail on most servers. Too >>many broken ACPI implementations I fear... Too bad motherboard vendors >>don't take the time to push proper software in their flash. > > > Right now acpi tells us there's a device, and we use it. Loader hints > should be used to map locations to device instances. It is more > general than just ACPI, however. People want to bind sio to a > specific port that comes out the back. People also want to bind rl0 > to the card in slot 3. > > Consider my system: > sio0 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.SBRG.UAR1 > sio1 pnpinfo _HID=PNP0501 _UID=2 at handle=\_SB_.PCI0.SBRG.UAR2 > > On this system, UAR1 is the port that comes out the back, so I have > what I want. However, I'd like to be able to say: > > hint.sio.0.at="acpi" > hint.sio.0.location="\_SB_.PCI0.SBRG.UAR2" > > or > > hint.sio.0.at="acpi" > hint.sio.0.location="UAR2" > > or > > hint.fxp.0.at="pci" > hint.fxp.0.location="bus=2 slot=3 function=0" > hint.fxp.1.at="pci" > hint.fxp.1.location="pci2:2:0" > > Since we really want to map the devices in some arbitrary ACPI tree to > instances in the system, rather than mapping devices that happen to > live at a specific resource address to specific instances in the tree. > > However, there are a number of issues in doing this generically and > with error cases. How does one deal with the different syntaxes? > What extensions to the newbus system are there? etc. > > Warner Well, in my case at least, what ACPI says about the sio resources is simply wrong, and I'm not smart enough to figure out how to correct the ASL or get it loaded correctly on boot. It would be easier if the sio-acpi attachment honored the hints that already exist for the purpose of describing the sio resources. Last I checked, neither Windows nor Linux nor Solaris required users to read the ACPI 2.0 spec to get their comms ports working. Having the flexibility to do what you describe above would be nice, but allowing mortal users to get their hardware working would be ever nicer. Scott From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 18:34:08 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCE5B16A41F for ; Mon, 31 Oct 2005 18:34:08 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1ADBF43D45 for ; Mon, 31 Oct 2005 18:34:08 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9VIXBeb006066; Mon, 31 Oct 2005 11:33:11 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 31 Oct 2005 11:33:11 -0700 (MST) Message-Id: <20051031.113311.104037760.imp@bsdimp.com> To: scottl@samsco.org From: Warner Losh In-Reply-To: <43665788.4070807@samsco.org> References: <20051031160150.GB87483@stack.nl> <20051031.103408.71093019.imp@bsdimp.com> <43665788.4070807@samsco.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 31 Oct 2005 11:33:13 -0700 (MST) Cc: marcolz@stack.nl, stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 18:34:09 -0000 From: Scott Long Subject: Re: HEADS UP! 6.0-RELEASE coming Date: Mon, 31 Oct 2005 10:42:32 -0700 > Warner Losh wrote: > >>>The ACPI+sio problem is known. I have a motherboard with a similar > >>>problem, though a different brand than yours. I solved it by removing > >>>the ACPI attachment from the sio code. The better solution is to allow > >>>loader hints to override ACPI hints. I tried talking to John Baldwin > >>>about this but didn't get much of a response. > >> > >>I've tried all suggestions so far, but to no avail on most servers. Too > >>many broken ACPI implementations I fear... Too bad motherboard vendors > >>don't take the time to push proper software in their flash. > > > > > > Right now acpi tells us there's a device, and we use it. Loader hints > > should be used to map locations to device instances. It is more > > general than just ACPI, however. People want to bind sio to a > > specific port that comes out the back. People also want to bind rl0 > > to the card in slot 3. > > > > Consider my system: > > sio0 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.SBRG.UAR1 > > sio1 pnpinfo _HID=PNP0501 _UID=2 at handle=\_SB_.PCI0.SBRG.UAR2 > > > > On this system, UAR1 is the port that comes out the back, so I have > > what I want. However, I'd like to be able to say: > > > > hint.sio.0.at="acpi" > > hint.sio.0.location="\_SB_.PCI0.SBRG.UAR2" > > > > or > > > > hint.sio.0.at="acpi" > > hint.sio.0.location="UAR2" > > > > or > > > > hint.fxp.0.at="pci" > > hint.fxp.0.location="bus=2 slot=3 function=0" > > hint.fxp.1.at="pci" > > hint.fxp.1.location="pci2:2:0" > > > > Since we really want to map the devices in some arbitrary ACPI tree to > > instances in the system, rather than mapping devices that happen to > > live at a specific resource address to specific instances in the tree. > > > > However, there are a number of issues in doing this generically and > > with error cases. How does one deal with the different syntaxes? > > What extensions to the newbus system are there? etc. > > > > Warner > > Well, in my case at least, what ACPI says about the sio resources is > simply wrong, and I'm not smart enough to figure out how to correct the > ASL or get it loaded correctly on boot. It would be easier if the > sio-acpi attachment honored the hints that already exist for the purpose > of describing the sio resources. Last I checked, neither Windows nor > Linux nor Solaris required users to read the ACPI 2.0 spec to get their > comms ports working. Having the flexibility to do what you describe > above would be nice, but allowing mortal users to get their hardware > working would be ever nicer. I didn't need to read the AML to get the serial ports working in the above example. devinfo -v gave me all I needed to know, a command that's very accessible to mere mortals, as you put it. The issue with other boards that I've seen is that you have things like PORTA and PORTB which are listed in COM2 and then COM1 resource order. I could have sworn that the AML that you'd posted a while ago was a mirror of this. I'd be happy to take a look at the AML of the system you are having trouble with to confirm this. There is a secondary issue to this as well. That is that some com ports can be assigned to one of many different addresses. That also needs to be addressed, but so far appears to be fairly uncommon. Warner From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 19:21:25 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DBED16A41F for ; Mon, 31 Oct 2005 19:21:25 +0000 (GMT) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from mailhost.u-strasbg.fr (mailhost.u-strasbg.fr [130.79.200.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id 643BE43D48 for ; Mon, 31 Oct 2005 19:21:24 +0000 (GMT) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from baal.u-strasbg.fr (baal.u-strasbg.fr [IPv6:2001:660:2402::41]) by mailhost.u-strasbg.fr (8.13.3/jtpda-5.5pre1) with ESMTP id j9VJLMZf029458 ; Mon, 31 Oct 2005 20:21:22 +0100 (CET) Received: from [127.0.0.1] (crc.u-strasbg.fr [IPv6:2001:660:2402:1001::1]) by baal.u-strasbg.fr (8.13.4/jtpda-5.5pre1) with ESMTP id j9VJLJNT018220 ; Mon, 31 Oct 2005 20:21:19 +0100 Message-ID: <43666E4C.4090205@crc.u-strasbg.fr> Date: Mon, 31 Oct 2005 20:19:40 +0100 From: Philippe PEGON User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051016) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marc Olzheim References: <436116D3.908@samsco.org> <20051031151809.GA83253@stack.nl> <43663A0A.4040608@samsco.org> <20051031160150.GB87483@stack.nl> In-Reply-To: <20051031160150.GB87483@stack.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87/1151/Mon Oct 31 19:34:04 2005 on mr4.u-strasbg.fr X-Virus-Scanned: ClamAV 0.87/1150/Sun Oct 30 12:20:38 2005 on baal.u-strasbg.fr X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (mailhost.u-strasbg.fr [IPv6:2001:660:2402::154]); Mon, 31 Oct 2005 20:21:22 +0100 (CET) X-Spam-Status: No, score=-0.0 required=5.0 tests=AWL,NO_RELAYS autolearn=disabled version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mr4.u-strasbg.fr Cc: stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 19:21:25 -0000 Marc Olzheim wrote: > On Mon, Oct 31, 2005 at 08:36:42AM -0700, Scott Long wrote: > >>>Anyone having updates for my showstopper page, please, notify me... >>> >>>http://www.stack.nl/%7Emarcolz/FreeBSD/showstoppers.html >> >>The pty problem is likely a side effect of known locking problems with >>ttys and ptys in general. This probably the weakest part of the kernel >>right now and I don't know of a good work-around for apps that use these >>extensively. That said, there doesn't seem to be much of a problem with >>casual use; I use screen(1) quite a bit on my production 6.0-RC >>mailserver+firewall. > > > I know it doesn't trigger too often for most users, but still, for us, > once a week per server on 2 production servers we installed FreeBSD 5 > and 6 on, is way too often. :-( for information, we have the same problem on our productions servers with FreeBSD 5 and I know that we are not alone. We hoped a lot for a solution with FreeBSD 6 after this thread : http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-June/016154.html but I have just tested with FreeBSD 6.0-RC1 and the problem is always there :-( -- Philippe PEGON From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 19:31:57 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7026116A41F for ; Mon, 31 Oct 2005 19:31:57 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48B5D43D46 for ; Mon, 31 Oct 2005 19:31:49 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j9VJVk8F007510; Mon, 31 Oct 2005 11:31:46 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j9VJVkZp007509; Mon, 31 Oct 2005 11:31:46 -0800 Date: Mon, 31 Oct 2005 11:31:46 -0800 From: Brooks Davis To: Joel Hatton Message-ID: <20051031193146.GB32660@odin.ac.hmc.edu> References: <200510260046.j9Q0khYU004317@app.auscert.org.au> <200510310050.j9V0oc8n020913@app.auscert.org.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LpQ9ahxlCli8rRTG" Content-Disposition: inline In-Reply-To: <200510310050.j9V0oc8n020913@app.auscert.org.au> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 RC1 dhclient (was Re: 6.0 RC1 usbd.conf (and installation comments)) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 19:31:57 -0000 --LpQ9ahxlCli8rRTG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 31, 2005 at 10:50:38AM +1000, Joel Hatton wrote: > I said: > >=20 > > DHCP configuration - for some reason my machine didn't acquire a > > default route on boot, but rerunning the dhclient script after > > boot caused the interface to be set up again successfully. I > > haven't looked into this further yet, I'll repost if it is a > > repeatable problem. >=20 > This issue is repeatable. Although I haven't had time to trace it further, > I have worked out that if I configure my dhcp interface with an alias eg > ifconfig_em0_alias0 a default route is not added; after commenting that > line in /etc/rc.conf the route is ok again on reboot. I've tried > alternating between commented/uncommented with consistent success/fail > results so I guess this needs looking at. Ah, that's they key. aliases don't work with dhclient at the moment for most interfaces because the interfaces generate bogus link events when aliases are modified. We hope to fix this, but it's going to take some time. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --LpQ9ahxlCli8rRTG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDZnEeXY6L6fI4GtQRAoUoAJ9njtiE+mopNIqX6NLne4+EAwTVDACfQju8 qGqIrBm/67VWrEA4xQRWCk8= =0Odg -----END PGP SIGNATURE----- --LpQ9ahxlCli8rRTG-- From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 19:48:53 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F6D116A41F for ; Mon, 31 Oct 2005 19:48:53 +0000 (GMT) (envelope-from scottl@pooker.samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B620543D4C for ; Mon, 31 Oct 2005 19:48:52 +0000 (GMT) (envelope-from scottl@pooker.samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id j9VJmnbc068539; Mon, 31 Oct 2005 12:48:50 -0700 (MST) (envelope-from scottl@pooker.samsco.org) Date: Mon, 31 Oct 2005 12:48:49 -0700 (MST) From: Scott To: Warner Losh In-Reply-To: <20051031.113311.104037760.imp@bsdimp.com> Message-ID: <20051031124649.M19239@pooker.samsco.org> References: <20051031160150.GB87483@stack.nl> <20051031.103408.71093019.imp@bsdimp.com> <43665788.4070807@samsco.org> <20051031.113311.104037760.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: marcolz@stack.nl, stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 19:48:53 -0000 On Mon, 31 Oct 2005, Warner Losh wrote: > From: Scott Long > Subject: Re: HEADS UP! 6.0-RELEASE coming > Date: Mon, 31 Oct 2005 10:42:32 -0700 > >> Warner Losh wrote: >>>>> The ACPI+sio problem is known. I have a motherboard with a similar >>>>> problem, though a different brand than yours. I solved it by removing >>>>> the ACPI attachment from the sio code. The better solution is to allow >>>>> loader hints to override ACPI hints. I tried talking to John Baldwin >>>>> about this but didn't get much of a response. >>>> >>>> I've tried all suggestions so far, but to no avail on most servers. Too >>>> many broken ACPI implementations I fear... Too bad motherboard vendors >>>> don't take the time to push proper software in their flash. >>> >>> >>> Right now acpi tells us there's a device, and we use it. Loader hints >>> should be used to map locations to device instances. It is more >>> general than just ACPI, however. People want to bind sio to a >>> specific port that comes out the back. People also want to bind rl0 >>> to the card in slot 3. >>> >>> Consider my system: >>> sio0 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.SBRG.UAR1 >>> sio1 pnpinfo _HID=PNP0501 _UID=2 at handle=\_SB_.PCI0.SBRG.UAR2 >>> >>> On this system, UAR1 is the port that comes out the back, so I have >>> what I want. However, I'd like to be able to say: >>> >>> hint.sio.0.at="acpi" >>> hint.sio.0.location="\_SB_.PCI0.SBRG.UAR2" >>> >>> or >>> >>> hint.sio.0.at="acpi" >>> hint.sio.0.location="UAR2" >>> >>> or >>> >>> hint.fxp.0.at="pci" >>> hint.fxp.0.location="bus=2 slot=3 function=0" >>> hint.fxp.1.at="pci" >>> hint.fxp.1.location="pci2:2:0" >>> >>> Since we really want to map the devices in some arbitrary ACPI tree to >>> instances in the system, rather than mapping devices that happen to >>> live at a specific resource address to specific instances in the tree. >>> >>> However, there are a number of issues in doing this generically and >>> with error cases. How does one deal with the different syntaxes? >>> What extensions to the newbus system are there? etc. >>> >>> Warner >> >> Well, in my case at least, what ACPI says about the sio resources is >> simply wrong, and I'm not smart enough to figure out how to correct the >> ASL or get it loaded correctly on boot. It would be easier if the >> sio-acpi attachment honored the hints that already exist for the purpose >> of describing the sio resources. Last I checked, neither Windows nor >> Linux nor Solaris required users to read the ACPI 2.0 spec to get their >> comms ports working. Having the flexibility to do what you describe >> above would be nice, but allowing mortal users to get their hardware >> working would be ever nicer. > > I didn't need to read the AML to get the serial ports working in the > above example. devinfo -v gave me all I needed to know, a command > that's very accessible to mere mortals, as you put it. > > The issue with other boards that I've seen is that you have things > like PORTA and PORTB which are listed in COM2 and then COM1 resource > order. I could have sworn that the AML that you'd posted a while ago > was a mirror of this. I'd be happy to take a look at the AML of the > system you are having trouble with to confirm this. > > There is a secondary issue to this as well. That is that some com > ports can be assigned to one of many different addresses. That also > needs to be addressed, but so far appears to be fairly uncommon. > > Warner > I guess I'm missing the jump between running devinfo and knowing how to parse and manipulate ASL/AML. Scott From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 20:22:27 2005 Return-Path: X-Original-To: stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4961A16A421 for ; Mon, 31 Oct 2005 20:22:27 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCAFD43D46 for ; Mon, 31 Oct 2005 20:22:26 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9VKKIFK007274; Mon, 31 Oct 2005 13:20:18 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 31 Oct 2005 13:20:18 -0700 (MST) Message-Id: <20051031.132018.112620008.imp@bsdimp.com> To: scottl@pooker.samsco.org From: Warner Losh In-Reply-To: <20051031124649.M19239@pooker.samsco.org> References: <43665788.4070807@samsco.org> <20051031.113311.104037760.imp@bsdimp.com> <20051031124649.M19239@pooker.samsco.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 31 Oct 2005 13:20:18 -0700 (MST) Cc: marcolz@stack.nl, stable@FreeBSD.ORG Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 20:22:27 -0000 From: Scott Subject: Re: HEADS UP! 6.0-RELEASE coming Date: Mon, 31 Oct 2005 12:48:49 -0700 (MST) > On Mon, 31 Oct 2005, Warner Losh wrote: > > From: Scott Long > > Subject: Re: HEADS UP! 6.0-RELEASE coming > > Date: Mon, 31 Oct 2005 10:42:32 -0700 > > > >> Warner Losh wrote: > >>>>> The ACPI+sio problem is known. I have a motherboard with a similar > >>>>> problem, though a different brand than yours. I solved it by removing > >>>>> the ACPI attachment from the sio code. The better solution is to allow > >>>>> loader hints to override ACPI hints. I tried talking to John Baldwin > >>>>> about this but didn't get much of a response. > >>>> > >>>> I've tried all suggestions so far, but to no avail on most servers. Too > >>>> many broken ACPI implementations I fear... Too bad motherboard vendors > >>>> don't take the time to push proper software in their flash. > >>> > >>> > >>> Right now acpi tells us there's a device, and we use it. Loader hints > >>> should be used to map locations to device instances. It is more > >>> general than just ACPI, however. People want to bind sio to a > >>> specific port that comes out the back. People also want to bind rl0 > >>> to the card in slot 3. > >>> > >>> Consider my system: > >>> sio0 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.SBRG.UAR1 > >>> sio1 pnpinfo _HID=PNP0501 _UID=2 at handle=\_SB_.PCI0.SBRG.UAR2 > >>> > >>> On this system, UAR1 is the port that comes out the back, so I have > >>> what I want. However, I'd like to be able to say: > >>> > >>> hint.sio.0.at="acpi" > >>> hint.sio.0.location="\_SB_.PCI0.SBRG.UAR2" > >>> > >>> or > >>> > >>> hint.sio.0.at="acpi" > >>> hint.sio.0.location="UAR2" > >>> > >>> or > >>> > >>> hint.fxp.0.at="pci" > >>> hint.fxp.0.location="bus=2 slot=3 function=0" > >>> hint.fxp.1.at="pci" > >>> hint.fxp.1.location="pci2:2:0" > >>> > >>> Since we really want to map the devices in some arbitrary ACPI tree to > >>> instances in the system, rather than mapping devices that happen to > >>> live at a specific resource address to specific instances in the tree. > >>> > >>> However, there are a number of issues in doing this generically and > >>> with error cases. How does one deal with the different syntaxes? > >>> What extensions to the newbus system are there? etc. > >>> > >>> Warner > >> > >> Well, in my case at least, what ACPI says about the sio resources is > >> simply wrong, and I'm not smart enough to figure out how to correct the > >> ASL or get it loaded correctly on boot. It would be easier if the > >> sio-acpi attachment honored the hints that already exist for the purpose > >> of describing the sio resources. Last I checked, neither Windows nor > >> Linux nor Solaris required users to read the ACPI 2.0 spec to get their > >> comms ports working. Having the flexibility to do what you describe > >> above would be nice, but allowing mortal users to get their hardware > >> working would be ever nicer. > > > > I didn't need to read the AML to get the serial ports working in the > > above example. devinfo -v gave me all I needed to know, a command > > that's very accessible to mere mortals, as you put it. > > > > The issue with other boards that I've seen is that you have things > > like PORTA and PORTB which are listed in COM2 and then COM1 resource > > order. I could have sworn that the AML that you'd posted a while ago > > was a mirror of this. I'd be happy to take a look at the AML of the > > system you are having trouble with to confirm this. > > > > There is a secondary issue to this as well. That is that some com > > ports can be assigned to one of many different addresses. That also > > needs to be addressed, but so far appears to be fairly uncommon. > > > > Warner > > > > I guess I'm missing the jump between running devinfo and knowing how to > parse and manipulate ASL/AML. You'd indicated that you'd prefer a method of specification that didn't require one understand ASL. With devinfo, one can get all the information one needs to create the location hints that I describe above w/o needing to know ASL, look at ASL, etc. Warner From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 23:31:44 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77F3C16A41F for ; Mon, 31 Oct 2005 23:31:44 +0000 (GMT) (envelope-from joel@auscert.org.au) Received: from titania.auscert.org.au (gw.auscert.org.au [203.5.112.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB32143D48 for ; Mon, 31 Oct 2005 23:31:43 +0000 (GMT) (envelope-from joel@auscert.org.au) Received: from app.auscert.org.au (app [10.0.1.192]) by titania.auscert.org.au (8.12.10/8.12.10) with ESMTP id j9VNUNio052635; Tue, 1 Nov 2005 09:30:23 +1000 (EST) Received: from app.auscert.org.au (localhost.auscert.org.au [127.0.0.1]) by app.auscert.org.au (8.13.1/8.13.1) with ESMTP id j9VNVbd0025784; Tue, 1 Nov 2005 09:31:41 +1000 (EST) (envelope-from joel@app.auscert.org.au) Message-Id: <200510312331.j9VNVbd0025784@app.auscert.org.au> To: Brooks Davis In-Reply-To: Your message of "Mon, 31 Oct 2005 11:31:46 PST." <20051031193146.GB32660@odin.ac.hmc.edu> Date: Tue, 01 Nov 2005 09:31:37 +1000 From: Joel Hatton Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 RC1 dhclient (was Re: 6.0 RC1 usbd.conf (and installation comments)) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 23:31:44 -0000 > Ah, that's they key. aliases don't work with dhclient at the moment for > most interfaces because the interfaces generate bogus link events when > aliases are modified. We hope to fix this, but it's going to take some > time. Ok - thanks. I'm fortunate at the moment that I've stopped using the jail I had on that particular machine. Even though this is a somewhat unusual situation (ie dhcp + jail alias) I don't suppose there's any move to in the mean time incorporate a 'DHCLIENT=' make option for ISC/OpenBSD versions? ;) joel -- Joel Hatton -- Security Analyst | Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland | WWW: www.auscert.org.au Qld 4072 Australia | Email: auscert@auscert.org.au From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 23:36:04 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AF5C16A41F for ; Mon, 31 Oct 2005 23:36:04 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0F9F43D46 for ; Mon, 31 Oct 2005 23:36:03 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j9VNa14m013955; Mon, 31 Oct 2005 15:36:01 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j9VNa11v013954; Mon, 31 Oct 2005 15:36:01 -0800 Date: Mon, 31 Oct 2005 15:36:01 -0800 From: Brooks Davis To: Joel Hatton Message-ID: <20051031233601.GA13072@odin.ac.hmc.edu> References: <20051031193146.GB32660@odin.ac.hmc.edu> <200510312331.j9VNVbd0025784@app.auscert.org.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy" Content-Disposition: inline In-Reply-To: <200510312331.j9VNVbd0025784@app.auscert.org.au> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-stable@freebsd.org Subject: Re: 6.0 RC1 dhclient (was Re: 6.0 RC1 usbd.conf (and installation comments)) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 23:36:04 -0000 --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 01, 2005 at 09:31:37AM +1000, Joel Hatton wrote: > > Ah, that's they key. aliases don't work with dhclient at the moment for > > most interfaces because the interfaces generate bogus link events when > > aliases are modified. We hope to fix this, but it's going to take some > > time. >=20 > Ok - thanks. I'm fortunate at the moment that I've stopped using the jail > I had on that particular machine. Even though this is a somewhat unusual > situation (ie dhcp + jail alias) I don't suppose there's any move to in > the mean time incorporate a 'DHCLIENT=3D' make option for ISC/OpenBSD > versions? ;) Such an option would be very difficult because the ISC and openbsd dhclients require vastly different support infrastructure. As I said, we do plan to fix this despite the fact that such a configuration is fundamentally perverse. :) It's just going to take some time. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --KsGdsel6WgEHnImy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDZqpdXY6L6fI4GtQRAvEeAJ9AfnhK70tbYHOIglVeywA2oGcyXwCffGz/ Lmc1Byfg8UrEhNUzK+ng7m4= =8luB -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy-- From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 23:47:29 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7626516A41F for ; Mon, 31 Oct 2005 23:47:29 +0000 (GMT) (envelope-from freebsd-stable@box559.com) Received: from mx4.x15.net (mx4.x15.net [69.55.237.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BE0743D77 for ; Mon, 31 Oct 2005 23:47:28 +0000 (GMT) (envelope-from freebsd-stable@box559.com) Received: from j1.x15.net [63.196.213.76] by mx4.x15.net with ESMTP id 510201052X1EWjN9000KSbPK; Mon, 31 Oct 2005 23:47:27 +0000 Message-ID: <4366ACF0.20606@box559.com> Date: Mon, 31 Oct 2005 15:46:56 -0800 From: Pete Slagle MIME-Version: 1.0 To: Kris Kennaway , freebsd-stable@freebsd.org References: <20051031082807.GA68204@xor.obsecurity.org> In-Reply-To: <20051031082807.GA68204@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 23:47:29 -0000 >>i agree 100%, i hate wizardy/black-magic, and this 'fix' falls in that >>class. Why was a 5ton hammer used to fix non existing problem? >>a small comment like 'you better keep these lines to make X happy' >>would have sufficed. > > > You've clearly never spent much time on the FreeBSD support forums, > where every few days someone posts for help > > 1) with an error caused by removing one of those "Do not remove this!" > lines, and > > 2) for help on getting X working when they forgot to add /dev/io and > /dev/mem to their kernel. > > Those of us who spend a lot of time answering such questions will > surely welcome the change, since it will hopefully reduce our > workload. Abundant thanks and sympathy are due to the generous souls that staff the support forums. That said, it is far from clear that ease-of-use considerations are the most important factor. Freedom to not have the O/S second guess one's choices, or worse, silently override them, is one of the main differentiators between FreeBSD and other available operating systems. Many (most?) of us are here because we do not want excessive complexity and hand holding. Let's not give away the fundamental character of FreeBSD in an (undoubtedly futile) attempt to make it idiot-proof. This is a small case in itself, but it represents a much larger issue concerning future direction. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 31 23:54:38 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5048116A41F for ; Mon, 31 Oct 2005 23:54:38 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFF2343DBA for ; Mon, 31 Oct 2005 23:54:37 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 0F34A46BA4; Mon, 31 Oct 2005 18:54:37 -0500 (EST) Date: Mon, 31 Oct 2005 23:54:36 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Marc Olzheim In-Reply-To: <20051031151809.GA83253@stack.nl> Message-ID: <20051031235311.D18382@fledge.watson.org> References: <436116D3.908@samsco.org> <20051031151809.GA83253@stack.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 23:54:38 -0000 On Mon, 31 Oct 2005, Marc Olzheim wrote: > On Thu, Oct 27, 2005 at 12:05:07PM -0600, Scott Long wrote: >> Everyone is still welcome to update their sources on the RELENG_6_0 >> branch and provide feedback for the next 48 hours or so. The release >> will likely be announced by the end of the weekend or early next >> week, at the latest. > > Anyone having updates for my showstopper page, please, notify me... > > http://www.stack.nl/%7Emarcolz/FreeBSD/showstoppers.html > > We are still installing new servers with 4.x, because I haven't seen a > really stable FreeBSD-stable release since... This includes current > RELENG_6_0. I started going through the ktrace code a few days ago to look at adding thread IDs to ktrace records. I'm happy to pick up the ktrace item in your todo list. My plan is basically to restore elements of the 4.x queueing model: rather than asynchronously dispatching all ktrace records to a single worker thread, dispatch them to disk from the system call return path for a thread. There are a few issues with threading that require attention -- in particular, avoiding writes on the vnode operation after close. This will also slow down ktracing again, but should avoid dropping records. I hope to have something hacked together in a few days, but not in time for 6.0. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 00:00:57 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBDFB16A41F for ; Tue, 1 Nov 2005 00:00:57 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E01843DCA for ; Mon, 31 Oct 2005 23:59:25 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 46E1D1A3C25; Mon, 31 Oct 2005 15:57:55 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B271A51262; Mon, 31 Oct 2005 18:57:51 -0500 (EST) Date: Mon, 31 Oct 2005 18:57:51 -0500 From: Kris Kennaway To: Pete Slagle Message-ID: <20051031235751.GA34385@xor.obsecurity.org> References: <20051031082807.GA68204@xor.obsecurity.org> <4366ACF0.20606@box559.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: <4366ACF0.20606@box559.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 00:00:57 -0000 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 31, 2005 at 03:46:56PM -0800, Pete Slagle wrote: > >>i agree 100%, i hate wizardy/black-magic, and this 'fix' falls in that > >>class. Why was a 5ton hammer used to fix non existing problem? > >>a small comment like 'you better keep these lines to make X happy' > >>would have sufficed. > > > > > >You've clearly never spent much time on the FreeBSD support forums, > >where every few days someone posts for help > > > >1) with an error caused by removing one of those "Do not remove this!" > >lines, and > > > >2) for help on getting X working when they forgot to add /dev/io and > >/dev/mem to their kernel. > > > >Those of us who spend a lot of time answering such questions will > >surely welcome the change, since it will hopefully reduce our > >workload. >=20 > Abundant thanks and sympathy are due to the generous souls that staff=20 > the support forums. That said, it is far from clear that ease-of-use=20 > considerations are the most important factor. >=20 > Freedom to not have the O/S second guess one's choices, or worse,=20 > silently override them, is one of the main differentiators between=20 > FreeBSD and other available operating systems. Many (most?) of us are=20 > here because we do not want excessive complexity and hand holding. Let's= =20 > not give away the fundamental character of FreeBSD in an (undoubtedly=20 > futile) attempt to make it idiot-proof. >=20 > This is a small case in itself, but it represents a much larger issue=20 > concerning future direction. It doesn't silently override them, you can remove the defaults with appropriate nodevice settings. However, I bet you don't even want to build a kernel without npx, mem or io support, so you're just arguing for the sake of it. kris --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZq9/Wry0BWjoQKURAqeLAJ9Xf66okoXHqujkpMdhsJ1BV7RKQwCg3s/x 7KSwGi0VQWwb1L5LIBYe0Zg= =kUk6 -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 00:40:46 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30F6C16A41F for ; Tue, 1 Nov 2005 00:40:46 +0000 (GMT) (envelope-from fjoe@neo.samodelkin.net) Received: from neo.samodelkin.net (samodelkin.net [195.62.0.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 773C843D4C for ; Tue, 1 Nov 2005 00:40:44 +0000 (GMT) (envelope-from fjoe@neo.samodelkin.net) Received: by neo.samodelkin.net (Postfix, from userid 1000) id 388781701F; Tue, 1 Nov 2005 06:40:42 +0600 (NOVT) Date: Tue, 1 Nov 2005 06:40:42 +0600 From: Max Khon To: Marc Olzheim Message-ID: <20051101004042.GA28233@samodelkin.net> References: <436116D3.908@samsco.org> <20051031151809.GA83253@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051031151809.GA83253@stack.nl> User-Agent: Mutt/1.4.2i Cc: stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 00:40:46 -0000 Hi! On Mon, Oct 31, 2005 at 04:18:09PM +0100, Marc Olzheim wrote: > > Everyone is still welcome to update their sources on the RELENG_6_0 > > branch and provide feedback for the next 48 hours or so. The release > > will likely be announced by the end of the weekend or early next > > week, at the latest. > > Anyone having updates for my showstopper page, please, notify me... > > http://www.stack.nl/%7Emarcolz/FreeBSD/showstoppers.html > > We are still installing new servers with 4.x, because I haven't seen a > really stable FreeBSD-stable release since... This includes current > RELENG_6_0. Linking against -lthr (or even -lc_r!) instead of -lpthread solves gdb "The program no longer exists." problem for me on RELENG_6. /fjoe From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 01:15:50 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8109E16A41F for ; Tue, 1 Nov 2005 01:15:50 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE44C43D45 for ; Tue, 1 Nov 2005 01:15:49 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jA11FeM4004040; Mon, 31 Oct 2005 18:15:40 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4366C1BB.8080202@samsco.org> Date: Mon, 31 Oct 2005 18:15:39 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pete Slagle References: <20051031082807.GA68204@xor.obsecurity.org> <4366ACF0.20606@box559.com> In-Reply-To: <4366ACF0.20606@box559.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 01:15:50 -0000 Pete Slagle wrote: >>> i agree 100%, i hate wizardy/black-magic, and this 'fix' falls in that >>> class. Why was a 5ton hammer used to fix non existing problem? >>> a small comment like 'you better keep these lines to make X happy' >>> would have sufficed. >> >> >> >> You've clearly never spent much time on the FreeBSD support forums, >> where every few days someone posts for help >> >> 1) with an error caused by removing one of those "Do not remove this!" >> lines, and >> >> 2) for help on getting X working when they forgot to add /dev/io and >> /dev/mem to their kernel. >> >> Those of us who spend a lot of time answering such questions will >> surely welcome the change, since it will hopefully reduce our >> workload. > > > Abundant thanks and sympathy are due to the generous souls that staff > the support forums. That said, it is far from clear that ease-of-use > considerations are the most important factor. > > Freedom to not have the O/S second guess one's choices, or worse, > silently override them, is one of the main differentiators between > FreeBSD and other available operating systems. Many (most?) of us are > here because we do not want excessive complexity and hand holding. Let's > not give away the fundamental character of FreeBSD in an (undoubtedly > futile) attempt to make it idiot-proof. > > This is a small case in itself, but it represents a much larger issue > concerning future direction. > The future direction is that FreeBSD will continue to be friendly to novice users while still affording power users the control that they seek. This feature is not going to be a dumping ground of dubious and secret options that are impossible to control. If you truly don't want the isa, npx, io, or mem devices in your kernel, then you can exclude them via the 'nodevice' directive. You can even just delete the DEFAULT file entirely if you choose, though I really don't recommend this. Scott From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 02:07:23 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FCD316A420 for ; Tue, 1 Nov 2005 02:07:23 +0000 (GMT) (envelope-from fjoe@neo.samodelkin.net) Received: from neo.samodelkin.net (samodelkin.net [195.62.0.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 859C443D48 for ; Tue, 1 Nov 2005 02:07:22 +0000 (GMT) (envelope-from fjoe@neo.samodelkin.net) Received: by neo.samodelkin.net (Postfix, from userid 1000) id 07E721701A; Tue, 1 Nov 2005 08:07:19 +0600 (NOVT) Date: Tue, 1 Nov 2005 08:07:19 +0600 From: Max Khon To: Marc Olzheim Message-ID: <20051101020719.GA31148@samodelkin.net> References: <436116D3.908@samsco.org> <20051031151809.GA83253@stack.nl> <20051101004042.GA28233@samodelkin.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051101004042.GA28233@samodelkin.net> User-Agent: Mutt/1.4.2i Cc: stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 02:07:23 -0000 Hi! On Tue, Nov 01, 2005 at 06:40:42AM +0600, Max Khon wrote: > > > Everyone is still welcome to update their sources on the RELENG_6_0 > > > branch and provide feedback for the next 48 hours or so. The release > > > will likely be announced by the end of the weekend or early next > > > week, at the latest. > > > > Anyone having updates for my showstopper page, please, notify me... > > > > http://www.stack.nl/%7Emarcolz/FreeBSD/showstoppers.html > > > > We are still installing new servers with 4.x, because I haven't seen a > > really stable FreeBSD-stable release since... This includes current > > RELENG_6_0. > > Linking against -lthr (or even -lc_r!) instead of -lpthread solves gdb > "The program no longer exists." problem for me on RELENG_6. More on this: setting env var LIBPTHREAD_SYSTEM_SCOPE also fixes the problem (with -lpthread). /fjoe From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 02:08:05 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03AD216A41F for ; Tue, 1 Nov 2005 02:08:05 +0000 (GMT) (envelope-from dpkirchner@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81F5A43D45 for ; Tue, 1 Nov 2005 02:08:04 +0000 (GMT) (envelope-from dpkirchner@gmail.com) Received: by xproxy.gmail.com with SMTP id s13so798006wxc for ; Mon, 31 Oct 2005 18:08:03 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WQLfJaelCbpCRhv2TYuECkfC54QJ2LyS1KrSU/h2y/EPy83MZttHWYk7OUIXzg3svyMEoBZezFalfuu6IsZ3S71Wa47dYUNtW6jIqUnQdjAbWxYaRc+JPtYUcjmr4lin4tC9slPSWl4X6jsiLf8AOzgN/kHOWyOvN82N9Vo5Gs8= Received: by 10.70.124.10 with SMTP id w10mr2190503wxc; Mon, 31 Oct 2005 18:08:03 -0800 (PST) Received: by 10.70.104.18 with HTTP; Mon, 31 Oct 2005 18:08:03 -0800 (PST) Message-ID: <35c231bf0510311808y48bac9a3vb9e2d5e0fed1e203@mail.gmail.com> Date: Mon, 31 Oct 2005 18:08:03 -0800 From: David Kirchner Sender: dpkirchner@gmail.com To: Scott Long In-Reply-To: <4366C1BB.8080202@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051031082807.GA68204@xor.obsecurity.org> <4366ACF0.20606@box559.com> <4366C1BB.8080202@samsco.org> Cc: Kris Kennaway , freebsd-stable@freebsd.org Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 02:08:05 -0000 On 10/31/05, Scott Long wrote: > The future direction is that FreeBSD will continue to be friendly to > novice users while still affording power users the control that they > seek. This feature is not going to be a dumping ground of dubious > and secret options that are impossible to control. If you truly don't > want the isa, npx, io, or mem devices in your kernel, then you can > exclude them via the 'nodevice' directive. You can even just delete the > DEFAULT file entirely if you choose, though I really don't recommend > this. If the goal is to make FreeBSD more friendly to novice users, then sure, having a "failsafe" DEFAULT file makes sense. Along those lines -- something else that I feel would help novice users would be a default kernel, always available unless specifically removed, that contains most of the drivers most of them use. It could be the kernel that they used to install the device in the first place, or something similar. That way if they build a couple of kernels in a row that don't end up working like they want, wiping out the working kernel, they could be directed to try this default kernel. At least then they could have the system working again. From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 09:54:12 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84E5B16A41F for ; Tue, 1 Nov 2005 09:54:12 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: from mail.interbgc.com (mx04.interbgc.com [217.9.224.231]) by mx1.FreeBSD.org (Postfix) with SMTP id 426FC43D53 for ; Tue, 1 Nov 2005 09:54:10 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: (qmail 15683 invoked from network); 1 Nov 2005 09:54:08 -0000 Received: from nike_d@cytexbg.com by keeper.interbgc.com by uid 1002 with qmail-scanner-1.14 (uvscan: v4.2.40/v4374. spamassassin: 2.63. Clear:SA:0(-2.5/8.0):. Processed in 2.564737 secs); 01 Nov 2005 09:54:08 -0000 X-Spam-Status: No, hits=-2.5 required=8.0 Received: from 213-240-205-57.1697748.ddns.cablebg.net (HELO tormentor.totalterror.net) (213.240.205.57) by mx04.interbgc.com with SMTP; 1 Nov 2005 09:54:05 -0000 Received: (qmail 55184 invoked from network); 1 Nov 2005 09:54:04 -0000 Received: from qmail by qscan (mail filter); 1 Nov 2005 09:54:04 +0000 Received: from unknown (HELO ?10.0.0.3?) (ndenev@10.0.0.3) by tormentor.totalterror.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Nov 2005 09:54:04 -0000 Message-ID: <43673B3B.3010607@cytexbg.com> Date: Tue, 01 Nov 2005 11:54:03 +0200 From: Niki Denev User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.92.1.0 OpenPGP: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: calcru: runtime went backwards ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 09:54:12 -0000 Hi, I've recently upgraded my server from 5.4-STABLE to 6.0-RC1 and shortly after that i began to see these messages in my dmesg: calcru: runtime went backwards from 1488581 usec to 1488580 usec for pid 65583 (mpsnmp) calcru: runtime went backwards from 12674015 usec to 12674008 usec for pid 98187 (mpsnmp) calcru: runtime went backwards from 3507422 usec to 3507421 usec for pid 19660 (mpsnmp) calcru: runtime went backwards from 4453368 usec to 4453367 usec for pid 28319 (mpsnmp) calcru: runtime went backwards from 6126291 usec to 6126280 usec for pid 24134 (mpsnmp) I've searched for this message, but haven't really found something that explains what is going on. The machine is dual Athlon MP with like i said 6.0-RC1 and stock SMP kernel, and "mpsnmp" is a multithreaded snmp collector which stores the data in RRD files. (i wrote it, maybe the problem is in it, but i haven't seen these messages before). So, is this something i should worry about? Thanks, --niki From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 10:16:28 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06B0C16A41F for ; Tue, 1 Nov 2005 10:16:28 +0000 (GMT) (envelope-from Juergen.Dankoweit@t-online.de) Received: from mailout08.sul.t-online.com (mailout08.sul.t-online.com [194.25.134.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3972C43D45 for ; Tue, 1 Nov 2005 10:16:27 +0000 (GMT) (envelope-from Juergen.Dankoweit@t-online.de) Received: from fwd31.aul.t-online.de by mailout08.sul.t-online.com with smtp id 1EWtBp-0007jd-01; Tue, 01 Nov 2005 11:16:25 +0100 Received: from mailsmtp.juergendankoweit.net (rXKyTeZY8e8itwg4wMYpXMAC2BlzsCj04rCJL7+a+0H1nSZixf9HY7@[84.150.79.48]) by fwd31.sul.t-online.de with esmtp id 1EWtBX-1S7MkS0; Tue, 1 Nov 2005 11:16:07 +0100 Received: from localhost.juergendankoweit.net (localhost.juergendankoweit.net [127.0.0.1]) by mailsmtp.juergendankoweit.net (Postfix) with ESMTP id 1AC6B33FDD for ; Tue, 1 Nov 2005 11:16:06 +0100 (CET) Received: from mailsmtp.juergendankoweit.net (localhost.juergendankoweit.net [127.0.0.1]) by localhost.juergendankoweit.net (AvMailGate-2.0.2-9) id 01444-16FD7246; Tue, 01 Nov 2005 11:16:05 +0100 Received: from primergy470.juergendankoweit.net (primergy470.juergendankoweit.net [192.168.1.1]) by mailsmtp.juergendankoweit.net (Postfix) with ESMTP id 8A8A433C4C for ; Tue, 1 Nov 2005 11:16:05 +0100 (CET) From: Juergen Dankoweit To: FreeBSD-Stable Content-Type: text/plain Date: Tue, 01 Nov 2005 11:16:04 +0100 Message-Id: <1130840164.1289.8.camel@primergy470.juergendankoweit.net> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-AntiVirus: checked by AntiVir MailGate (version: 2.0.2-9; AVE: 6.32.0.8; VDF: 6.32.0.127; host: primergy470.juergendankoweit.net) X-ID: rXKyTeZY8e8itwg4wMYpXMAC2BlzsCj04rCJL7+a+0H1nSZixf9HY7 X-TOI-MSGID: ddfd7bc3-56c9-4f4d-9b4d-1138ba803519 Subject: Dual Symbios/LSI-HBA and FreeBSD 6.0 RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Juergen.Dankoweit@T-Online.de List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 10:16:28 -0000 Hello, on my Siemens Primergy 470 (dual PIII 450MHz) with two Symbios/LSI 83C895 I have great troubles: While booting FreeBSD it hangs on probing the SCSI devices. This error was in FreeBSD 5.3 STABLE 2, too! When will this bug being fixed? Here the SCSI tree and dmesg from FBSD 5.3: ------------------------------------------- primergy470# dmesg | grep sym sym0: <895> port 0x3000-0x30ff mem 0xf0200000-0xf0200fff,0xf0201000-0xf02010ff irq 23 at device 1.0 on pci2 sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym1: <895> port 0x1800-0x18ff mem 0xf0101000-0xf0101fff,0xf0102000-0xf01020ff irq 17 at device 13.0 on pci0 sym1: Symbios NVRAM, ID 7, Fast-40, SE, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. [^^^^^^^^^^^^^^^^^^^^^^^^^^ on FBSD 6.0RC1 it hangs here!] (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. (noperiph:sym1:0:-1:-1): SCSI BUS mode change from SE to SE. (probe7:sym0:0:8:0): phase change 6-7 6@0f76078c resid=4. ses0 at sym0 bus 0 target 8 lun 0 da0 at sym0 bus 0 target 0 lun 0 da1 at sym0 bus 0 target 10 lun 0 cd1 at sym1 bus 0 target 4 lun 0 cd0 at sym1 bus 0 target 5 lun 0 Many thanks for your answer. Best regards Juergen From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 10:33:07 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 982FE16A420 for ; Tue, 1 Nov 2005 10:33:07 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: from mail.interbgc.com (mx03.interbgc.com [217.9.224.229]) by mx1.FreeBSD.org (Postfix) with SMTP id 7376043D48 for ; Tue, 1 Nov 2005 10:33:05 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: (qmail 55711 invoked from network); 1 Nov 2005 10:33:04 -0000 Received: from nike_d@cytexbg.com by keeper.interbgc.com by uid 1002 with qmail-scanner-1.14 (uvscan: v4.2.40/v4374. spamassassin: 2.63. Clear:SA:0(-2.6/8.0):. Processed in 2.768104 secs); 01 Nov 2005 10:33:04 -0000 X-Spam-Status: No, hits=-2.6 required=8.0 Received: from 213-240-205-57.1697748.ddns.cablebg.net (HELO tormentor.totalterror.net) (213.240.205.57) by mx03.interbgc.com with SMTP; 1 Nov 2005 10:33:01 -0000 Received: (qmail 71499 invoked from network); 1 Nov 2005 10:33:00 -0000 Received: from qmail by qscan (mail filter); 1 Nov 2005 10:33:00 +0000 Received: from unknown (HELO ?10.0.0.3?) (ndenev@10.0.0.3) by tormentor.totalterror.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Nov 2005 10:33:00 -0000 Message-ID: <4367445B.4030601@cytexbg.com> Date: Tue, 01 Nov 2005 12:32:59 +0200 From: Niki Denev User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <43673B3B.3010607@cytexbg.com> In-Reply-To: <43673B3B.3010607@cytexbg.com> X-Enigmail-Version: 0.92.1.0 OpenPGP: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: joseph.koshy@gmail.com Subject: Re: calcru: runtime went backwards ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 10:33:07 -0000 Niki Denev wrote: > Hi, > > I've recently upgraded my server from 5.4-STABLE to 6.0-RC1 > and shortly after that i began to see these messages in my dmesg: > > calcru: runtime went backwards from 1488581 usec to 1488580 usec for pid > 65583 (mpsnmp) [snip] dmesg and output of kern.timecounter sysctl can be found here : http://totalterror.net/freebsd/calcru/ --niki From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 10:51:59 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4964A16A41F for ; Tue, 1 Nov 2005 10:51:59 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B53A43D58 for ; Tue, 1 Nov 2005 10:51:56 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by xproxy.gmail.com with SMTP id s13so890337wxc for ; Tue, 01 Nov 2005 02:51:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WAmTLxiI53MH/WjHIj7plUljTSNmjGh9GbjC++nbXcg3zbEADB06kn53ohwbILyjmeeaCy6fV/3aX7vzCaQ72lMv7ngfKu9C4ZB+hcNE5u+WC4+Z/RzH5HT+9sLPxeWghOPD6WNd4oZzIUJopD+v5ro0+wHHlj7gIR+DhXJW43Q= Received: by 10.70.118.9 with SMTP id q9mr2416495wxc; Tue, 01 Nov 2005 02:51:55 -0800 (PST) Received: by 10.70.105.13 with HTTP; Tue, 1 Nov 2005 02:51:55 -0800 (PST) Message-ID: <84dead720511010251tb63131bs954c2e98b46820c2@mail.gmail.com> Date: Tue, 1 Nov 2005 16:21:55 +0530 From: Joseph Koshy To: Niki Denev In-Reply-To: <4367445B.4030601@cytexbg.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43673B3B.3010607@cytexbg.com> <4367445B.4030601@cytexbg.com> Cc: freebsd-stable@freebsd.org Subject: Re: calcru: runtime went backwards ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 10:51:59 -0000 > dmesg and output of kern.timecounter sysctl can be found here : Changing your timecounter to "i8254" may help. Bug 43491 and 72338 seem to be related: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D72338 http://www.freebsd.org/cgi/query-pr.cgi?pr=3D43491 -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 11:02:07 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10A6116A41F for ; Tue, 1 Nov 2005 11:02:07 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: from mail.interbgc.com (mx03.interbgc.com [217.9.224.229]) by mx1.FreeBSD.org (Postfix) with SMTP id 686E243D66 for ; Tue, 1 Nov 2005 11:01:59 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: (qmail 63494 invoked from network); 1 Nov 2005 11:01:59 -0000 Received: from nike_d@cytexbg.com by keeper.interbgc.com by uid 1002 with qmail-scanner-1.14 (uvscan: v4.2.40/v4374. spamassassin: 2.63. Clear:SA:0(-2.6/8.0):. Processed in 3.040997 secs); 01 Nov 2005 11:01:58 -0000 X-Spam-Status: No, hits=-2.6 required=8.0 Received: from 213-240-205-57.1697748.ddns.cablebg.net (HELO tormentor.totalterror.net) (213.240.205.57) by mx03.interbgc.com with SMTP; 1 Nov 2005 11:01:55 -0000 Received: (qmail 75784 invoked from network); 1 Nov 2005 11:01:55 -0000 Received: from qmail by qscan (mail filter); 1 Nov 2005 11:01:55 +0000 Received: from unknown (HELO ?10.0.0.3?) (ndenev@10.0.0.3) by tormentor.totalterror.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Nov 2005 11:01:55 -0000 Message-ID: <43674B22.2010205@cytexbg.com> Date: Tue, 01 Nov 2005 13:01:54 +0200 From: Niki Denev User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joseph Koshy References: <43673B3B.3010607@cytexbg.com> <4367445B.4030601@cytexbg.com> <84dead720511010251tb63131bs954c2e98b46820c2@mail.gmail.com> In-Reply-To: <84dead720511010251tb63131bs954c2e98b46820c2@mail.gmail.com> X-Enigmail-Version: 0.92.1.0 OpenPGP: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: calcru: runtime went backwards ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 11:02:07 -0000 Joseph Koshy wrote: >>dmesg and output of kern.timecounter sysctl can be found here : > > > Changing your timecounter to "i8254" may help. > > Bug 43491 and 72338 seem to be related: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=72338 > http://www.freebsd.org/cgi/query-pr.cgi?pr=43491 > > -- > FreeBSD Volunteer, http://people.freebsd.org/~jkoshy Thanks, i've changed it to i8254 and will watch it for a couple of days. --niki From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 11:24:04 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E630C16A41F for ; Tue, 1 Nov 2005 11:24:04 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8051A43D46 for ; Tue, 1 Nov 2005 11:24:03 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id DF7ABA300A; Tue, 1 Nov 2005 12:24:02 +0100 (CET) Received: by hammer.stack.nl (Postfix, from userid 333) id BEB3D657A; Tue, 1 Nov 2005 12:24:02 +0100 (CET) Date: Tue, 1 Nov 2005 12:24:02 +0100 From: Marc Olzheim To: Scott Long Message-ID: <20051101112402.GA4878@stack.nl> References: <436116D3.908@samsco.org> <20051031151809.GA83253@stack.nl> <43663A0A.4040608@samsco.org> <20051031160150.GB87483@stack.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z" Content-Disposition: inline In-Reply-To: <20051031160150.GB87483@stack.nl> X-Operating-System: FreeBSD hammer.stack.nl 6.0-BETA4 FreeBSD 6.0-BETA4 X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.11 Cc: Marc Olzheim , stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 11:24:05 -0000 --Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 31, 2005 at 05:01:50PM +0100, Marc Olzheim wrote: > > Is the 'VM/VFS overruns' item still a problem? That was likely fixed a= =20 > > couple of months ago. If not then it's definitely something that I'll > > track for the 6.1 release. >=20 > I'll retest that one, but it wasn't fixed yet in -CURRENT of a month ago. I'm happy to confirm that it works fine now in today's RELENG_6. :-) Marc --Nq2Wo0NMKNjxTN9z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZ1BSezjnobFOgrERApNYAJ4pIMlwdVXrHuH4GLncUUkCa2NsqgCgxF7f IXxSdfkTgpA3oH3KRrE0hy0= =OJdq -----END PGP SIGNATURE----- --Nq2Wo0NMKNjxTN9z-- From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 11:29:01 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7D1A16A41F for ; Tue, 1 Nov 2005 11:29:01 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A3C543D45 for ; Tue, 1 Nov 2005 11:29:01 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 74F9CA3034; Tue, 1 Nov 2005 12:29:00 +0100 (CET) Received: by hammer.stack.nl (Postfix, from userid 333) id 53D35657A; Tue, 1 Nov 2005 12:29:00 +0100 (CET) Date: Tue, 1 Nov 2005 12:29:00 +0100 From: Marc Olzheim To: Max Khon Message-ID: <20051101112900.GA4903@stack.nl> References: <436116D3.908@samsco.org> <20051031151809.GA83253@stack.nl> <20051101004042.GA28233@samodelkin.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bg08WKrSYDhXBjb5" Content-Disposition: inline In-Reply-To: <20051101004042.GA28233@samodelkin.net> X-Operating-System: FreeBSD hammer.stack.nl 6.0-BETA4 FreeBSD 6.0-BETA4 X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.11 Cc: Marc Olzheim , stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 11:29:01 -0000 --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Nov 01, 2005 at 06:40:42AM +0600, Max Khon wrote: > Linking against -lthr (or even -lc_r!) instead of -lpthread solves gdb > "The program no longer exists." problem for me on RELENG_6. Well, yes, but that's not the same. While running on M:N KSE, all sorts of locking needs to be correct, which with non M:N threading you can get away with some (intentional or not) sloppiness. So debugging a fully threaded program with a non M:N threadlib is not always useful. Marc --bg08WKrSYDhXBjb5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZ1F8ezjnobFOgrERAtrBAKCFkNVFlOymIfNiT1Hmp+AdyAyi9gCeOiHd 0C+/MG5o0n7FW5mQkEl3oMM= =jo5k -----END PGP SIGNATURE----- --bg08WKrSYDhXBjb5-- From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 11:41:03 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 217BA16A41F for ; Tue, 1 Nov 2005 11:41:03 +0000 (GMT) (envelope-from p.cherkaev@omk-kuzbass.ru) Received: from proxy.omk-kuzbass.ru (omk-kuzbass.ru [62.231.164.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C41443D45 for ; Tue, 1 Nov 2005 11:41:01 +0000 (GMT) (envelope-from p.cherkaev@omk-kuzbass.ru) Received: from [192.168.0.50] ([192.168.0.50]) by proxy.omk-kuzbass.ru (8.13.4/8.13.4) with ESMTP id jA1BeLbH000986 for ; Tue, 1 Nov 2005 18:40:21 +0700 (KRAT) (envelope-from p.cherkaev@omk-kuzbass.ru) Message-ID: <43675433.5020301@omk-kuzbass.ru> Date: Tue, 01 Nov 2005 18:40:35 +0700 From: =?KOI8-R?Q?=22=F0=C1=D7=C5=CC_=E5=2E_=FE=C5=D2=CB=C1=C5=D7=22?= User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: ru-ru, ru MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.3 required=5.0 tests=ALL_TRUSTED,URIBL_SBL autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on proxy.omk-kuzbass.ru Subject: Qualcomm modem via USB X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 11:41:03 -0000 console: ucom0: Qualcomm, Incorporated Qualcomm CDMA Technologies MSM, rev 1.01/0.00, addr 2, iclass 2/2 ucom0: data interface 1, has CM over data, has break ucom0: could not set data multiplex mode device_attach: ucom0 attach returned 6 #uname -a FreeBSD proxy.omk-kuzbass.ru 5.4-STABLE FreeBSD 5.4-STABLE #0: what i can add to my kernel configuration ? I need this modem :( From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 12:20:07 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B668A16A41F for ; Tue, 1 Nov 2005 12:20:07 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from ash25e.internode.on.net (ash25e.internode.on.net [203.16.214.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id F253743D45 for ; Tue, 1 Nov 2005 12:20:06 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from midget.dons.net.au (ppp128-213.lns2.adl2.internode.on.net [59.167.128.213]) by ash25e.internode.on.net (8.12.9/8.12.6) with ESMTP id jA1CJxQu016501; Tue, 1 Nov 2005 22:50:04 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.dons.net.au (inchoate.dons.net.au [10.0.2.101]) (authenticated bits=0) by midget.dons.net.au (8.13.4/8.13.3) with ESMTP id jA1CJu8J085388 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 1 Nov 2005 22:49:58 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Tue, 1 Nov 2005 22:49:41 +1030 User-Agent: KMail/1.8.2 References: <43675433.5020301@omk-kuzbass.ru> In-Reply-To: <43675433.5020301@omk-kuzbass.ru> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1385154.0nam7ViHs5"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200511012249.48943.doconnor@gsoft.com.au> X-Spam-Score: 2.45 (**) MIME_CHARSET_FARAWAY X-Scanned-By: MIMEDefang 2.52 on 10.0.2.7 Cc: =?utf-8?b?0J/QsNCy0LXQuyDQlS4=?= =?utf-8?b?INCn0LXRgNC60LDQtdCy?= Subject: Re: Qualcomm modem via USB X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 12:20:07 -0000 --nextPart1385154.0nam7ViHs5 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 1 Nov 2005 22:10, =F0=C1=D7=C5=CC =E5. =FE=C5=D2=CB=C1=C5=D7 wrote: > console: > ucom0: Qualcomm, Incorporated Qualcomm CDMA Technologies MSM, rev > 1.01/0.00, addr 2, iclass 2/2 > ucom0: data interface 1, has CM over data, has break > ucom0: could not set data multiplex mode > device_attach: ucom0 attach returned 6 I woulud say it's because umodem doesn't support modems that don't do=20 multiplexed mode. See /usr/src/sys/dev/usb/umodem.c line 78. So, basically, it's an unsupported device unless someone writes the code to= =20 get it going. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1385154.0nam7ViHs5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDZ11k5ZPcIHs/zowRAmwiAJ9aYhhtMzu2sP/o6oljoJ3DXeOiqQCfbrT4 D4f9iRVl1utS0Sn+DLIdEIE= =eSX0 -----END PGP SIGNATURE----- --nextPart1385154.0nam7ViHs5-- From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 12:33:24 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A882116A41F for ; Tue, 1 Nov 2005 12:33:24 +0000 (GMT) (envelope-from fjoe@neo.samodelkin.net) Received: from neo.samodelkin.net (samodelkin.net [195.62.0.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id E62E443D49 for ; Tue, 1 Nov 2005 12:33:23 +0000 (GMT) (envelope-from fjoe@neo.samodelkin.net) Received: by neo.samodelkin.net (Postfix, from userid 1000) id 843B517054; Tue, 1 Nov 2005 18:33:21 +0600 (NOVT) Date: Tue, 1 Nov 2005 18:33:21 +0600 From: Max Khon To: Marc Olzheim Message-ID: <20051101123321.GA39888@samodelkin.net> References: <436116D3.908@samsco.org> <20051031151809.GA83253@stack.nl> <20051101004042.GA28233@samodelkin.net> <20051101112900.GA4903@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051101112900.GA4903@stack.nl> User-Agent: Mutt/1.4.2i Cc: stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 12:33:24 -0000 Hi! On Tue, Nov 01, 2005 at 12:29:00PM +0100, Marc Olzheim wrote: > > Linking against -lthr (or even -lc_r!) instead of -lpthread solves gdb > > "The program no longer exists." problem for me on RELENG_6. > > Well, yes, but that's not the same. While running on M:N KSE, all sorts > of locking needs to be correct, which with non M:N threading you can get > away with some (intentional or not) sloppiness. So debugging a fully > threaded program with a non M:N threadlib is not always useful. I do not think that maintaining M:N thread lib is feasible, given the lack of resources. Solaris has already moved from M:N to 1:1. Linux (NPTL) is 1:1 as well. /fjoe From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 13:02:48 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C14916A41F for ; Tue, 1 Nov 2005 13:02:48 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E7AC43D46 for ; Tue, 1 Nov 2005 13:02:46 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 7B64FA3044; Tue, 1 Nov 2005 14:02:45 +0100 (CET) Received: by hammer.stack.nl (Postfix, from userid 333) id 6111B657A; Tue, 1 Nov 2005 14:02:45 +0100 (CET) Date: Tue, 1 Nov 2005 14:02:45 +0100 From: Marc Olzheim To: Max Khon Message-ID: <20051101130245.GE5237@stack.nl> References: <436116D3.908@samsco.org> <20051031151809.GA83253@stack.nl> <20051101004042.GA28233@samodelkin.net> <20051101112900.GA4903@stack.nl> <20051101123321.GA39888@samodelkin.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Pk6IbRAofICFmK5e" Content-Disposition: inline In-Reply-To: <20051101123321.GA39888@samodelkin.net> X-Operating-System: FreeBSD hammer.stack.nl 6.0-BETA4 FreeBSD 6.0-BETA4 X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.11 Cc: Marc Olzheim , stable@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 13:02:48 -0000 --Pk6IbRAofICFmK5e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 01, 2005 at 06:33:21PM +0600, Max Khon wrote: > Hi! >=20 > On Tue, Nov 01, 2005 at 12:29:00PM +0100, Marc Olzheim wrote: >=20 > > > Linking against -lthr (or even -lc_r!) instead of -lpthread solves gdb > > > "The program no longer exists." problem for me on RELENG_6. > >=20 > > Well, yes, but that's not the same. While running on M:N KSE, all sorts > > of locking needs to be correct, which with non M:N threading you can get > > away with some (intentional or not) sloppiness. So debugging a fully > > threaded program with a non M:N threadlib is not always useful. >=20 > I do not think that maintaining M:N thread lib is feasible, given the lack > of resources. Solaris has already moved from M:N to 1:1. Linux (NPTL) is = 1:1 > as well. Well, each threading system has it's own application. Having an easy way to have one multithreaded process use multiple CPUs is a big win in any case. Especially in computationally intensive tasks... Marc --Pk6IbRAofICFmK5e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZ2d1ezjnobFOgrERAthQAKDPpJoRiATWrc+ltAGLjViCPtXSsACgql5C FMh9lJrh9Yu1OTYC+wXeTM4= =Ts/7 -----END PGP SIGNATURE----- --Pk6IbRAofICFmK5e-- From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 13:54:50 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42E1A16A41F for ; Tue, 1 Nov 2005 13:54:50 +0000 (GMT) (envelope-from lofi@freebsd.org) Received: from mail-in-08.arcor-online.net (mail-in-08.arcor-online.net [151.189.21.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67AD143D46 for ; Tue, 1 Nov 2005 13:54:49 +0000 (GMT) (envelope-from lofi@freebsd.org) Received: from mail-in-02-z2.arcor-online.net (mail-in-02-z2.arcor-online.net [151.189.8.14]) by mail-in-08.arcor-online.net (Postfix) with ESMTP id 29ABE9F1C2; Tue, 1 Nov 2005 14:54:48 +0100 (CET) Received: from mail-in-09.arcor-online.net (mail-in-09.arcor-online.net [151.189.21.49]) by mail-in-02-z2.arcor-online.net (Postfix) with ESMTP id 1D35A18955A; Tue, 1 Nov 2005 14:54:48 +0100 (CET) Received: from lofi.dyndns.org (dslb-084-061-136-063.pools.arcor-ip.net [84.61.136.63]) by mail-in-09.arcor-online.net (Postfix) with ESMTP id C619E9E9E0; Tue, 1 Nov 2005 14:54:47 +0100 (CET) Received: from kiste.my.domain (root@kiste.my.domain [192.168.8.4]) by lofi.dyndns.org (8.13.4/8.13.3) with ESMTP id jA1DsifM013524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Nov 2005 14:54:45 +0100 (CET) (envelope-from lofi@freebsd.org) Received: from kiste.my.domain (lofi@localhost [127.0.0.1]) by kiste.my.domain (8.13.1/8.13.1) with ESMTP id jA1DsgTj011008; Tue, 1 Nov 2005 14:54:42 +0100 (CET) (envelope-from lofi@freebsd.org) Received: from localhost (localhost [[UNIX: localhost]]) by kiste.my.domain (8.13.1/8.13.1/Submit) id jA1Dsf7v011007; Tue, 1 Nov 2005 14:54:41 +0100 (CET) (envelope-from lofi@freebsd.org) X-Authentication-Warning: kiste.my.domain: lofi set sender to lofi@freebsd.org using -f From: Michael Nottebrock To: freebsd-stable@freebsd.org Date: Tue, 1 Nov 2005 14:54:38 +0100 User-Agent: KMail/1.8.2 References: <43649CE8.6010004@wanadoo.fr> In-Reply-To: <43649CE8.6010004@wanadoo.fr> X-Face: =Ym$`&q\+S2X$4`X%x%6"L4>Y,$]<":'L%c9"#7#`2tb&E&wsN31on!N\)3BD[g<=?utf-8?q?=2EjnfV=5B=0A=093=23?=>XchLK,o; >bD>c:]^; :>0>vyZ.X[,63GW`&M>}nYnr]-Fp``,[[@lJ!QL|sfW!s)=?utf-8?q?A2!*=0A=09vNkB/=7CL-?=>&QdSbQg X-Virus-Scanned: by amavisd-new Cc: edward Subject: Re: HFS/HFS+ support in 5.4 Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 13:54:50 -0000 --nextPart1787612.XDsyWeh6dT Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday, 30. October 2005 11:14, edward wrote: > Hi, > I need to mount an iPod mini formatted in HFS+. I don't believe this > file system is supported in 5.4 Stable, at least not on a standard > kernel. I get : > # ls /sbin/mount_* > /sbin/mount_cd9660 /sbin/mount_msdosfs /sbin/mount_std > /sbin/mount_devfs /sbin/mount_nfs /sbin/mount_udf > /sbin/mount_ext2fs /sbin/mount_nfs4 /sbin/mount_umapfs > /sbin/mount_fdescfs /sbin/mount_ntfs /sbin/mount_unionfs > /sbin/mount_linprocfs /sbin/mount_nullfs > /sbin/mount_mfs /sbin/mount_procfs > The following page offers a HFS/HFS+ kernel module based on Darwin code. > But it seems kind of out of date (2003) : > http://people.freebsd.org/~yar/hfs/ > What would be the best way of building HFS/HFS+ support into my kernel ? You will need to add options GEOM_APPLE to your kernel configuration and use the filesystem driver from the URL you= =20 quoted. FreeBSD currently does not ship with hfs filesystem support. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart1787612.XDsyWeh6dT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDZ3OgXhc68WspdLARAnf9AJ9OznCcYoGwhuTalekpvxr0eBEWcwCffm1J ZHCkne+lspNZab3eJJbvrks= =ll0x -----END PGP SIGNATURE----- --nextPart1787612.XDsyWeh6dT-- From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 14:26:40 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4517716A41F for ; Tue, 1 Nov 2005 14:26:40 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26FC743D64 for ; Tue, 1 Nov 2005 14:26:32 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jA1EQUDr087803; Tue, 1 Nov 2005 07:26:31 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43677B16.4040706@samsco.org> Date: Tue, 01 Nov 2005 07:26:30 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marc Olzheim References: <436116D3.908@samsco.org> <20051031151809.GA83253@stack.nl> <20051101004042.GA28233@samodelkin.net> <20051101112900.GA4903@stack.nl> <20051101123321.GA39888@samodelkin.net> <20051101130245.GE5237@stack.nl> In-Reply-To: <20051101130245.GE5237@stack.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: stable@freebsd.org, Max Khon Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 14:26:40 -0000 Marc Olzheim wrote: > On Tue, Nov 01, 2005 at 06:33:21PM +0600, Max Khon wrote: > >>Hi! >> >>On Tue, Nov 01, 2005 at 12:29:00PM +0100, Marc Olzheim wrote: >> >> >>>>Linking against -lthr (or even -lc_r!) instead of -lpthread solves gdb >>>>"The program no longer exists." problem for me on RELENG_6. >>> >>>Well, yes, but that's not the same. While running on M:N KSE, all sorts >>>of locking needs to be correct, which with non M:N threading you can get >>>away with some (intentional or not) sloppiness. So debugging a fully >>>threaded program with a non M:N threadlib is not always useful. >> >>I do not think that maintaining M:N thread lib is feasible, given the lack >>of resources. Solaris has already moved from M:N to 1:1. Linux (NPTL) is 1:1 >>as well. > > > Well, each threading system has it's own application. Having an easy way > to have one multithreaded process use multiple CPUs is a big win in any > case. Especially in computationally intensive tasks... > > Marc There is little difference between 1:1 and M:N from the application's point of view. Both will allow multiple application threads to run concurrently on multiple CPUs, and both will allow other process threads to run when the current thread blocks in the kernel. The difference is in the details with how they are scheduled and what kernel resources they use. 1:1 has the advantage of being much less complex to implement and maintain, while M:N has the theoretical advantage of cheaper thread context switches. That theory hasn't panned out, though, due to synchronization requirements and the technical requirements of proper TLS support. Scott From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 15:29:57 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EED2A16A41F for ; Tue, 1 Nov 2005 15:29:57 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 906E443D45 for ; Tue, 1 Nov 2005 15:29:57 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 535A046B91; Tue, 1 Nov 2005 10:29:56 -0500 (EST) Date: Tue, 1 Nov 2005 15:29:56 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Scott Long In-Reply-To: <43677B16.4040706@samsco.org> Message-ID: <20051101152728.U45155@fledge.watson.org> References: <436116D3.908@samsco.org> <20051031151809.GA83253@stack.nl> <20051101004042.GA28233@samodelkin.net> <20051101112900.GA4903@stack.nl> <20051101123321.GA39888@samodelkin.net> <20051101130245.GE5237@stack.nl> <43677B16.4040706@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Marc Olzheim , stable@freebsd.org, Max Khon Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 15:29:58 -0000 On Tue, 1 Nov 2005, Scott Long wrote: > There is little difference between 1:1 and M:N from the application's > point of view. Both will allow multiple application threads to run > concurrently on multiple CPUs, and both will allow other process threads > to run when the current thread blocks in the kernel. The difference is > in the details with how they are scheduled and what kernel resources > they use. 1:1 has the advantage of being much less complex to implement > and maintain, while M:N has the theoretical advantage of cheaper thread > context switches. That theory hasn't panned out, though, due to > synchronization requirements and the technical requirements of proper > TLS support. I've observed at least one situation in which m:n threading has performed significantly better as a result of better use of CPU resources. Specifically, it appears (on face value) as though libpthread is avoiding over-contention of resources by limiting the number of threads entering the kernel in contentious situations on SMP. I've not yet had the opportunity to confirm this outside of micro-benchmark environments, and plan to do so in the next few weeks. This doesn't mean that this is impossible to do with libthr, just that we may need some more scheduler investigation to make libthr catch up on SMP in that environment. Details to follow as available. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Tue Nov 1 16:54:08 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9144216A41F for ; Tue, 1 Nov 2005 16:54:08 +0000 (GMT) (envelope-from imb@protected-networks.net) Received: from aaron.protected-networks.net (aaron.protected-networks.net [202.12.127.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF74243D48 for ; Tue, 1 Nov 2005 16:54:07 +0000 (GMT) (envelope-from imb@protected-networks.net) Received: from localhost (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 5FEE8C1FB for ; Tue, 1 Nov 2005 11:54:04 -0500 (EST) Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 4854BC22D for ; Tue, 1 Nov 2005 11:53:58 -0500 (EST) Authentication-Results: aaron.protected-networks.net from=imb@protected-networks.net; domainkey=pass Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id C30D9C20B for ; Tue, 1 Nov 2005 11:53:57 -0500 (EST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=200509; d=protected-networks.net; b=Y4EV406DVG5rybBVDep/9n/XoKZUkU21gyKQALGaYPWB48umsSd4PRJSALXe4EEn/ KQYL/56XDC0CLpyOe/tDPbMVL2MDxwaxvYiya+NPAIIIhr4Zt0/Nv36Bsnm2jcQ Received: from [10.12.211.74] (usstls-23.savvis.net [64.242.52.23]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "imb@protected-networks.net", Issuer "Protected Networks Certificate Authority" (verified OK)) (Authenticated sender: imb@protected-networks.net) by aaron.protected-networks.net (Postfix) with ESMTP id 43C1CC1D1 for ; Tue, 1 Nov 2005 11:53:57 -0500 (EST) Message-ID: <43679D9A.9020504@protected-networks.net> Date: Tue, 01 Nov 2005 11:53:46 -0500 From: Michael Butler User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.93.0.0 OpenPGP: id=5E873CC5 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 6.x-RC1 instability with HighPoint HPT372N UDMA133 controller X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 16:54:08 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I just upgraded this thing to RELENG_6 and have all manner of issues when there are a lot of files to be removed; as is typical when I do the recommended "portupgrade -af" so as to remove all of the references to RELENG_5 libraries. With Soren's ata-mk3n patch-kit on RELENG_5, I got a panic along with "FAILURE - out of memory in ata_raid_init_request". With RELENG_6, I just get a spontaneous reboot; no messages to speak of (and it's remote so I can't see the console :-(). This is a cpu and memory-constrained machine with 4 drives configured using RAID 0+1 .. dmesg as follows .. suggestions? Copyright (c) 1992-2005 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 6.0-RC1 #3: Mon Oct 31 06:46:37 EST 2005 ~ imb@mail.auburn.protected-networks.net:/usr/obj/usr/src/sys/AUBURN Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (349.88-MHz 686-class CPU) ~ Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183f9ff real memory = 402653184 (384 MB) avail memory = 388767744 (370 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 11 on acpi0 pci_link1: irq 10 on acpi0 pci_link2: irq 5 on acpi0 pci_link3: irq 9 on acpi0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe0000000-0xefffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1000-0x100f at device 7.1 on pci0 ata0: on atapci0 ata1: on atapci0 uhci0: port 0x1020-0x103f irq 9 at device 7.2 on pci0 uhci0: [GIANT-LOCKED] 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 intpm0: port 0x7000-0x700f irq 9 at device 7.3 on pci0 intpm0: I/O mapped 7000 intpm0: intr IRQ 9 enabled revision 0 intpm0: [GIANT-LOCKED] intsmb0: on intpm0 smbus1: on intsmb0 smb0: on smbus1 intpm0: PM I/O mapped 8000 atapci1: port 0x1040-0x1047,0x1014-0x1017,0x1018-0x101f, 0x1010-0x1013,0x1400-0x14ff irq 11 at device 13.0 on pci0 ata2: on atapci1 ata3: on atapci1 ahc0: port 0x1800-0x18ff mem 0xd0000000-0xd0000fff irq 10 at device 14.0 on pci0 ahc0: [GIANT-LOCKED] aic7860: Ultra Single Channel A, SCSI Id=7, 3/253 SCBs xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x1080-0x10ff mem 0xd0001000-0xd000107f irq 5 at device 15.0 on pci0 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:10:5a:17:a3:79 pci0: at device 16.0 (no driver attached) atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff,0xcc000-0xcc7ff, 0xdc000-0xdffff,0xe4000-0xeffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 349880525 Hz quality 800 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging unlimited Waiting 5 seconds for SCSI devices to settle acd0: CDROM at ata1-master UDMA33 ad4: 152627MB at ata2-master UDMA133 ad5: 152627MB at ata2-slave UDMA133 ad6: 152627MB at ata3-master UDMA133 ad7: 152627MB at ata3-slave UDMA133 sa0 at ahc0 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) pass1 at ata1 bus 0 target 0 lun 0 pass1: Removable CD-ROM SCSI-0 device pass1: 33.000MB/s transfers ar0: 305255MB status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (master) using ad5 at ata2-slave ar0: disk2 READY (mirror) using ad6 at ata3-master ar0: disk3 READY (mirror) using ad7 at ata3-slave Trying to mount root from ufs:/dev/ar0s1a -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) iD8DBQFDZ52aiJykeV6HPMURAl7QAJ97CPsPu0V86o/JwAo8h/2lVnbEtwCgkSsj sqeyzK6yD0bHqiyPja6+ZkQ= =WZ3y -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Wed Nov 2 06:28:38 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8A8216A41F for ; Wed, 2 Nov 2005 06:28:38 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: from mail.interbgc.com (mx01.interbgc.com [217.9.224.225]) by mx1.FreeBSD.org (Postfix) with SMTP id 0C18743D53 for ; Wed, 2 Nov 2005 06:28:32 +0000 (GMT) (envelope-from nike_d@cytexbg.com) Received: (qmail 49633 invoked from network); 2 Nov 2005 06:28:30 -0000 Received: from nike_d@cytexbg.com by keeper.interbgc.com by uid 1002 with qmail-scanner-1.14 (uvscan: v4.2.40/v4374. spamassassin: 2.63. Clear:SA:0(-2.6/8.0):. Processed in 3.230043 secs); 02 Nov 2005 06:28:30 -0000 X-Spam-Status: No, hits=-2.6 required=8.0 Received: from 213-240-205-57.1697748.ddns.cablebg.net (HELO tormentor.totalterror.net) (213.240.205.57) by mx01.interbgc.com with SMTP; 2 Nov 2005 06:28:27 -0000 Received: (qmail 18435 invoked from network); 2 Nov 2005 06:28:26 -0000 Received: from qmail by qscan (mail filter); 2 Nov 2005 06:28:26 +0000 Received: from unknown (HELO ?10.0.0.3?) (ndenev@10.0.0.3) by tormentor.totalterror.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Nov 2005 06:28:26 -0000 Message-ID: <43685C8C.8010609@cytexbg.com> Date: Wed, 02 Nov 2005 08:28:28 +0200 From: Niki Denev User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, Joseph Koshy References: <43673B3B.3010607@cytexbg.com> <4367445B.4030601@cytexbg.com> <84dead720511010251tb63131bs954c2e98b46820c2@mail.gmail.com> <43674B22.2010205@cytexbg.com> In-Reply-To: <43674B22.2010205@cytexbg.com> X-Enigmail-Version: 0.92.1.0 OpenPGP: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: calcru: runtime went backwards ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 06:28:38 -0000 Niki Denev wrote: > Joseph Koshy wrote: > >>>dmesg and output of kern.timecounter sysctl can be found here : >> >> >>Changing your timecounter to "i8254" may help. >> >>Bug 43491 and 72338 seem to be related: >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=72338 >> http://www.freebsd.org/cgi/query-pr.cgi?pr=43491 >> >>-- >>FreeBSD Volunteer, http://people.freebsd.org/~jkoshy > > > Thanks, i've changed it to i8254 and will watch it for a > couple of days. > > --niki i've got three more of them this morning... and it seems that only my program triggers them. i think it's the only application that uses threads on my system, maybe this is related? --niki From owner-freebsd-stable@FreeBSD.ORG Wed Nov 2 07:43:35 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7EE016A420 for ; Wed, 2 Nov 2005 07:43:35 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: from web36202.mail.mud.yahoo.com (web36202.mail.mud.yahoo.com [209.191.68.228]) by mx1.FreeBSD.org (Postfix) with SMTP id 6629F43D58 for ; Wed, 2 Nov 2005 07:43:30 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: (qmail 50147 invoked by uid 60001); 2 Nov 2005 07:43:29 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=gfik0ZYCtbwkuOjahwcPvHdhmb4LkCB/AuSKAPHWnx2caiQYY4QQr9zgD74A1Myi2PkS0fuRB2dBz54jCs8tsFiLipe2IzU7c6epa0m1FUoPehCQuDZChWaNn4RgCfX8K7mydP1MweZdCQ6SMFmI8h727AfjJecARvDBKkvbvas= ; Message-ID: <20051102074329.50145.qmail@web36202.mail.mud.yahoo.com> Received: from [147.46.44.181] by web36202.mail.mud.yahoo.com via HTTP; Tue, 01 Nov 2005 23:43:29 PST Date: Tue, 1 Nov 2005 23:43:29 -0800 (PST) From: Rob To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Kris Kennaway Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 07:43:35 -0000 Kris Kennaway wrote: > > You've clearly never spent much time on the FreeBSD > support forums, where every few days someone posts > for help > > 1) with an error caused by removing one of those > "Do not remove this!" lines, and > > 2) for help on getting X working when they forgot > to add /dev/io and /dev/mem to their kernel. I believe *BSD can offer a better solution for such issues. For example, when having firewall_enable="YES", then /etc/rc.d/ipfw does: if ! ${SYSCTL} net.inet.ip.fw.enable; then if ! kldload ipfw; then warn unable to load firewall module. return 1 fi fi So if ipfw is not supported by the kernel, this script will automagically load the ipfw module, or issue a warning what is missing. (Similarly, but not yet implemented, /etc/rc.d/sshd should automagically load the random module, if not in the kernel). My point is then to follow this strategy also for X: instead of a DEFAULTS file, have a /etc/rc.d/xdm script, which starts X and loads the modules io/mem if needed. Rob. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-stable@FreeBSD.ORG Wed Nov 2 07:54:11 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8C1216A41F for ; Wed, 2 Nov 2005 07:54:11 +0000 (GMT) (envelope-from cristiano.deana@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13A7C43D46 for ; Wed, 2 Nov 2005 07:54:10 +0000 (GMT) (envelope-from cristiano.deana@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so32003wra for ; Tue, 01 Nov 2005 23:54:10 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ncloVMWxahmYZVXcUy20kyg5KNKlsdsI16l2sKZWtTkKlnOgunx5ADmekSzC6GDFf9+YdhRdrnvVqBNVTZHPLNjkssld33DyGwULAOZSX1BcSLY6AU+JxXziCh9WeAaQuSSh9VYiKvEPOg8Rqsktemp8QgvGMfVIoXU0LmJHrnI= Received: by 10.54.112.11 with SMTP id k11mr1894898wrc; Tue, 01 Nov 2005 23:54:10 -0800 (PST) Received: by 10.54.114.5 with HTTP; Tue, 1 Nov 2005 23:54:10 -0800 (PST) Message-ID: Date: Wed, 2 Nov 2005 08:54:10 +0100 From: Cristiano Deana To: Scott Long In-Reply-To: <4366C1BB.8080202@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051031082807.GA68204@xor.obsecurity.org> <4366ACF0.20606@box559.com> <4366C1BB.8080202@samsco.org> Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 07:54:11 -0000 2005/11/1, Scott Long : > The future direction is that FreeBSD will continue to be friendly to > novice users while still affording power users the control that they > seek. Scott, that's right. but: we can have our personal way to shoot in the foot, we can use big, BIG, advice "dont remove this line!" in our kernel, we can have our DEAFULTS file. No difference what we/you choose, but a little explanation for any of us about changes I thing should be in GENERIC or in DEFAULTS (better in UPDATING). Thank to you and all re@ people for this great 6.0. Good job. -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.org/ From owner-freebsd-stable@FreeBSD.ORG Wed Nov 2 07:54:11 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD90D16A420 for ; Wed, 2 Nov 2005 07:54:11 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 952D343D48 for ; Wed, 2 Nov 2005 07:54:11 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 5FBC51A3C2D; Tue, 1 Nov 2005 23:54:11 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5159A51370; Wed, 2 Nov 2005 02:54:10 -0500 (EST) Date: Wed, 2 Nov 2005 02:54:10 -0500 From: Kris Kennaway To: Rob Message-ID: <20051102075409.GA75458@xor.obsecurity.org> References: <20051102074329.50145.qmail@web36202.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <20051102074329.50145.qmail@web36202.mail.mud.yahoo.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 07:54:12 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 01, 2005 at 11:43:29PM -0800, Rob wrote: > Kris Kennaway wrote: > > > > You've clearly never spent much time on the FreeBSD > > support forums, where every few days someone posts > > for help > >=20 > > 1) with an error caused by removing one of those > > "Do not remove this!" lines, and > >=20 > > 2) for help on getting X working when they forgot > > to add /dev/io and /dev/mem to their kernel. >=20 > I believe *BSD can offer a better solution for such > issues. >=20 > For example, when having firewall_enable=3D"YES", > then /etc/rc.d/ipfw does: >=20 > if ! ${SYSCTL} net.inet.ip.fw.enable; then > if ! kldload ipfw; then > warn unable to load firewall module. > return 1 > fi > fi >=20 > So if ipfw is not supported by the kernel, this > script will automagically load the ipfw module, > or issue a warning what is missing. >=20 > (Similarly, but not yet implemented, /etc/rc.d/sshd > should automagically load the random module, if > not in the kernel). >=20 > My point is then to follow this strategy also for X: > instead of a DEFAULTS file, have a /etc/rc.d/xdm > script, which starts X and loads the modules io/mem > if needed. You missed the part where I said that the error is commonly reported by people who have chosen not to build modules. Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDaHChWry0BWjoQKURAhzBAKDlYAKvGH9q1csi9BEbkbz/nvhIIwCg2n7V 3+YsaiLBF+8yHbGHgiV1emw= =sY0Q -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- From owner-freebsd-stable@FreeBSD.ORG Wed Nov 2 09:31:38 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14A8E16A420 for ; Wed, 2 Nov 2005 09:31:38 +0000 (GMT) (envelope-from steve@sohara.org) Received: from sohara.org (sohara.org [192.220.64.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A45243D46 for ; Wed, 2 Nov 2005 09:31:37 +0000 (GMT) (envelope-from steve@sohara.org) Received: (qmail 90570 invoked by uid 16563); 2 Nov 2005 09:31:36 -0000 Received: from unknown (HELO df1.marelmo.com) ([194.145.135.85]) (envelope-sender ) by 192.220.64.179 (qmail-ldap-1.03) with SMTP for ; 2 Nov 2005 09:31:36 -0000 Date: Wed, 2 Nov 2005 09:30:29 +0000 From: Steve O'Hara-Smith To: Rob Message-Id: <20051102093029.2028d5a1.steve@sohara.org> In-Reply-To: <20051102074329.50145.qmail@web36202.mail.mud.yahoo.com> References: <20051102074329.50145.qmail@web36202.mail.mud.yahoo.com> X-Mailer: Sylpheed version 2.0.3 (GTK+ 2.8.6; i386-pc-dragonfly1) X-Face: %]+HVL}K`P8>+8ZcY-WGHP6j@&mxMo9JH6_WdgIgUGH)JX/usO0%jy7T~IVgqjumD^OBqX, Kv^-GM6mlw(fI^$"QRKyZ$?xx/ Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 09:31:38 -0000 On Tue, 1 Nov 2005 23:43:29 -0800 (PST) Rob wrote: > My point is then to follow this strategy also for X: > instead of a DEFAULTS file, have a /etc/rc.d/xdm > script, which starts X and loads the modules io/mem > if needed. Not everybody uses xdm, some use the KDE version and some of us use xinit or startx and ~/.xinitrc is a very bad place to try loading kernel modules. -- C:>WIN | Directable Mirror Arrays The computer obeys and wins. | A better way to focus the sun You lose and Bill collects. | licences available see | http://www.sohara.org/ From owner-freebsd-stable@FreeBSD.ORG Wed Nov 2 10:36:22 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 741E416A41F for ; Wed, 2 Nov 2005 10:36:22 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: from web36201.mail.mud.yahoo.com (web36201.mail.mud.yahoo.com [209.191.68.227]) by mx1.FreeBSD.org (Postfix) with SMTP id 7574543D5E for ; Wed, 2 Nov 2005 10:36:20 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: (qmail 40728 invoked by uid 60001); 2 Nov 2005 10:36:19 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=b3hBWoCvuWBNZ4TRBayWddiEZwkqRoc9dSqL4OoyOwHcM1G5MAH09yNmHKXyg//8UsBpaM91lFmP5yNJVzNc2HYrr2aAarK6ixY40Glh/mQm6Ayi2l3C74XgiLSArd2efBNeeoKOl1T78va7XiNb+ZSXrXOKMIx+tL8tBMJDaQY= ; Message-ID: <20051102103619.40726.qmail@web36201.mail.mud.yahoo.com> Received: from [147.46.44.181] by web36201.mail.mud.yahoo.com via HTTP; Wed, 02 Nov 2005 02:36:19 PST Date: Wed, 2 Nov 2005 02:36:19 -0800 (PST) From: Rob To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Kris Kennaway Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 10:36:22 -0000 Kris Kennaway wrote: > > You missed the part where I said that the error is > commonly reported by people who have chosen not to > build modules. The DEFAULTS construction is put in place to help 'novices' not to do stupid things (as removing io/mem). However, does 'building a kernel without modules' qualify as a novice action? I wonder. I think if you know how to do that, you've quite progressed in the world of kernel building! Rob. __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com From owner-freebsd-stable@FreeBSD.ORG Wed Nov 2 12:29:49 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A7D416A41F for ; Wed, 2 Nov 2005 12:29:49 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2ADB43D46 for ; Wed, 2 Nov 2005 12:29:48 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 01C7246B09; Wed, 2 Nov 2005 07:29:48 -0500 (EST) Date: Wed, 2 Nov 2005 12:29:47 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Rob In-Reply-To: <20051102103619.40726.qmail@web36201.mail.mud.yahoo.com> Message-ID: <20051102122547.Y45155@fledge.watson.org> References: <20051102103619.40726.qmail@web36201.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 12:29:49 -0000 On Wed, 2 Nov 2005, Rob wrote: > Kris Kennaway wrote: >> >> You missed the part where I said that the error is commonly reported by >> people who have chosen not to build modules. > > The DEFAULTS construction is put in place to help 'novices' not to do > stupid things (as removing io/mem). > > However, does 'building a kernel without modules' qualify as a novice > action? I wonder. I think if you know how to do that, you've quite > progressed in the world of kernel building! My hope is that, increasingly, FreeBSD users will create kernel configuration files using the "include" directive to specify a set of changes relative to GENERIC. That will also help lower the rate of foot shooting involving kernel components becoming optional. Most of my kernel configuration files now look something like this: include GENERIC ident FLEDGE makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options COMPAT_AOUT options KDB options DDB options BREAK_TO_DEBUGGER options ALT_BREAK_TO_DEBUGGER options IPFIREWALL options DUMMYNET options IPDIVERT options INVARIANTS options INVARIANT_SUPPORT nooptions WITNESS nooptions WITNESS_SKIP_SPIN Whereby I rely on GENERIC to provide the defaults for the configuration, and then tweak to add/remove particular options or devices. I've found this to be a more reliable way to track changing branches, as I don't have to notice when the details of GENERIC (and now DEFAULTS) changes: I get new device drivers when they are added, and unless I take specific action, things don't disappear out from under me when they become optional, which was the problem most people had with device mem and device io. They would upgrade their source tree, but not resync their configuration file to the latest tweaks in GENERIC. This was not an error, of course, since options are there so they can be optional, but it did result in hard to debug problems. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Wed Nov 2 15:13:37 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBE7D16A420 for ; Wed, 2 Nov 2005 15:13:37 +0000 (GMT) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B2FB43D46 for ; Wed, 2 Nov 2005 15:13:37 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.1.6] (unknown [192.168.1.6]) by yertle.kcilink.com (Postfix) with ESMTP id 435FCB816 for ; Wed, 2 Nov 2005 10:13:34 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <20051102074329.50145.qmail@web36202.mail.mud.yahoo.com> References: <20051102074329.50145.qmail@web36202.mail.mud.yahoo.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Wed, 2 Nov 2005 10:13:32 -0500 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.746.2) Subject: Re: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:13:38 -0000 On Nov 2, 2005, at 2:43 AM, Rob wrote: > My point is then to follow this strategy also for X: > instead of a DEFAULTS file, have a /etc/rc.d/xdm > script, which starts X and loads the modules io/mem > if needed. > but these devices are also needed for things like netstat. you pretty much need to load them always, unless you have a very specific embedded application which doesn't need those stats. From owner-freebsd-stable@FreeBSD.ORG Wed Nov 2 15:41:04 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E058F16A41F for ; Wed, 2 Nov 2005 15:41:04 +0000 (GMT) (envelope-from thomas@FreeBSD.ORG) Received: from melusine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [82.225.155.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68BEA43D55 for ; Wed, 2 Nov 2005 15:41:04 +0000 (GMT) (envelope-from thomas@FreeBSD.ORG) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id 5355E2C441; Wed, 2 Nov 2005 16:41:00 +0100 (CET) Date: Wed, 2 Nov 2005 16:41:00 +0100 From: Thomas Quinot To: rihad Message-ID: <20051102154100.GD59716@melusine.cuivre.fr.eu.org> References: <43477BBC.7000904@mail.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43477BBC.7000904@mail.ru> X-message-flag: WARNING! Using Outlook can damage your computer. User-Agent: Mutt/1.5.8i Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD binary upgrade / gmirror X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:41:05 -0000 * rihad, 2005-10-08 : > Now I want to do a binary upgrade to FreeBSD 5.4, but the new > sysinstall's disklabel editor only recognizes the IDE disks and does not > consider the GEOM mirror (mentioned in /etc/fstab, btw). How do I go > about this? Thanks. Did you try "gmirror load" from a sysinstall shell? Thomas. From owner-freebsd-stable@FreeBSD.ORG Wed Nov 2 21:39:34 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D2D116A41F for ; Wed, 2 Nov 2005 21:39:34 +0000 (GMT) (envelope-from kenfreebsd@icarz.com) Received: from miramanee.icarz.com (miramanee.icarz.com [207.99.22.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05F7B43D48 for ; Wed, 2 Nov 2005 21:39:33 +0000 (GMT) (envelope-from kenfreebsd@icarz.com) Received: from deanna.icarz.com (deanna.icarz.com [207.99.22.19]) by miramanee.icarz.com (8.13.3/8.13.1) with ESMTP id jA2LdWPA022524 for ; Wed, 2 Nov 2005 16:39:32 -0500 (EST) (envelope-from kenfreebsd@icarz.com) Received: from kenxp (netb-138.icarz.com [209.123.219.138]) by deanna.icarz.com (8.12.11/8.12.9) with SMTP id jA2LdUxr078788 for ; Wed, 2 Nov 2005 16:39:30 -0500 (EST) (envelope-from kenfreebsd@icarz.com) Message-ID: <075001c5dff5$e859fbc0$8adb7bd1@icarz.com> From: "Ken Menzel" To: Date: Wed, 2 Nov 2005 16:39:30 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Spam-Score: -99.999 () BAYES_50,UPPERCASE_25_50,USER_IN_WHITELIST X-Scanned-By: MIMEDefang 2.39 Cc: Subject: Fw: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ken Menzel List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 21:39:34 -0000 > options INVARIANT_SUPPORT > > nooptions WITNESS > nooptions WITNESS_SKIP_SPIN If I include GENERIC can I comment out the following? #cpu I486_CPU #cpu I586_CPU Does this make any difference? I have always done this out of habit. would it become nocpu I486_CPU ? Or is this irrelevant as the build knows what CPU I have? Thanks, Ken From owner-freebsd-stable@FreeBSD.ORG Wed Nov 2 22:09:57 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E665416A41F for ; Wed, 2 Nov 2005 22:09:57 +0000 (GMT) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 975D943D45 for ; Wed, 2 Nov 2005 22:09:57 +0000 (GMT) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id jA2M9scS051790 for ; Wed, 2 Nov 2005 14:09:54 -0800 (PST) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.13.3/8.13.1/Submit) id jA2M9sCU051789 for stable@freebsd.org; Wed, 2 Nov 2005 14:09:54 -0800 (PST) (envelope-from david) Date: Wed, 2 Nov 2005 14:09:54 -0800 From: David Wolfskill To: stable@freebsd.org Message-ID: <20051102220954.GM69015@bunrab.catwhisker.org> Mail-Followup-To: David Wolfskill , stable@freebsd.org References: <075001c5dff5$e859fbc0$8adb7bd1@icarz.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <075001c5dff5$e859fbc0$8adb7bd1@icarz.com> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: Fw: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 22:09:58 -0000 On Wed, Nov 02, 2005 at 04:39:30PM -0500, Ken Menzel wrote: > ... > If I include GENERIC can I comment out the following? > #cpu I486_CPU > #cpu I586_CPU Well, it's your (copy of) the file; I suppose you can do whatever you want to with it. :-) > Does this make any difference? I have always done this out of habit. I believe it will make some difference, yes. > would it become > > nocpu I486_CPU ? As of FreeeBSD 6.0-STABLE, /usr/src/usr.sbin/config/lang.l (rev. 1.41, last updated 2005/02/10 10:46:27) has tokens defined such as "cpu", "device", "nodevice", etc., but not "nocpu". It might be worth adding, though. Of course, some semantics would need to be associated with it in config.y. > Or is this irrelevant as the build knows what CPU I have? It might know what kind you havem but that's no guarantee that you plan to run the kernel you build on the same machine. Peace, david -- David H. Wolfskill david@catwhisker.org Prediction is difficult, especially if it involves the future. -- Niels Bohr See http://www.catwhisker.org/~david/publickey.gpg for public key. From owner-freebsd-stable@FreeBSD.ORG Wed Nov 2 22:28:56 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B489116A41F for ; Wed, 2 Nov 2005 22:28:56 +0000 (GMT) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from mailhost.u-strasbg.fr (mailhost.u-strasbg.fr [130.79.200.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EE9843D45 for ; Wed, 2 Nov 2005 22:28:55 +0000 (GMT) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from baal.u-strasbg.fr (baal.u-strasbg.fr [IPv6:2001:660:2402::41]) by mailhost.u-strasbg.fr (8.13.3/jtpda-5.5pre1) with ESMTP id jA2MSr3C063556 ; Wed, 2 Nov 2005 23:28:53 +0100 (CET) Received: from [127.0.0.1] (crc.u-strasbg.fr [IPv6:2001:660:2402:1001::1]) by baal.u-strasbg.fr (8.13.4/jtpda-5.5pre1) with ESMTP id jA2MSrVl018096 ; Wed, 2 Nov 2005 23:28:53 +0100 Message-ID: <43693D43.2000400@crc.u-strasbg.fr> Date: Wed, 02 Nov 2005 23:27:15 +0100 From: Philippe PEGON User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051016) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken Menzel References: <075001c5dff5$e859fbc0$8adb7bd1@icarz.com> In-Reply-To: <075001c5dff5$e859fbc0$8adb7bd1@icarz.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87/1160/Wed Nov 2 17:26:43 2005 on mr5.u-strasbg.fr X-Virus-Scanned: ClamAV 0.87/1160/Wed Nov 2 17:26:43 2005 on baal.u-strasbg.fr X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (mailhost.u-strasbg.fr [IPv6:2001:660:2402::155]); Wed, 02 Nov 2005 23:28:54 +0100 (CET) X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS autolearn=disabled version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mr5.u-strasbg.fr Cc: freebsd-stable@freebsd.org Subject: Re: Fw: GENERIC and DEFAULTS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 22:28:56 -0000 Ken Menzel wrote: >> options INVARIANT_SUPPORT >> >> nooptions WITNESS >> nooptions WITNESS_SKIP_SPIN > > > If I include GENERIC can I comment out the following? > #cpu I486_CPU > #cpu I586_CPU > > Does this make any difference? I have always done this out of habit. > would it become in /usr/src/sys/i386/conf/NOTES we can read : # # You must specify at least one CPU (the one you intend to run on); # deleting the specification for CPUs you don't need to use may make # parts of the system run faster. # cpu I486_CPU cpu I586_CPU # aka Pentium(tm) cpu I686_CPU # aka Pentium Pro(tm) > > nocpu I486_CPU ? > > Or is this irrelevant as the build knows what CPU I have? if the description is true, it's relevant ;) > > Thanks, > Ken -- Philippe PEGON From owner-freebsd-stable@FreeBSD.ORG Wed Nov 2 23:19:37 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CF8216A41F for ; Wed, 2 Nov 2005 23:19:37 +0000 (GMT) (envelope-from jeff@sailorfej.net) Received: from mail.sailorfej.net (mail.sailorfej.net [65.102.14.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD4C543D46 for ; Wed, 2 Nov 2005 23:19:36 +0000 (GMT) (envelope-from jeff@sailorfej.net) Received: from [192.168.150.40] (doorwarden.sailorfej.net [65.102.14.161]) (authenticated bits=0) by mail.sailorfej.net (8.13.1/8.12.11) with ESMTP id jA2NJUXi070672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Nov 2005 15:19:31 -0800 (PST) (envelope-from jeff@sailorfej.net) Message-ID: <4369497D.6030504@sailorfej.net> Date: Wed, 02 Nov 2005 15:19:25 -0800 From: Jeffrey Williams User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, misc@openbsd.org X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV 0.85.1/1160/Wed Nov 2 08:26:43 2005 on mail.sailorfej.net X-Virus-Status: Clean Cc: Subject: Problems with HP dx5150/ATI Xpress 200 chipset X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 23:19:37 -0000 I have recently purchased a number HP DX5150 SFF desktops with idea of using them as basic infrastructure servers (e.g. DNS, DHCP, and firewall). I prefer to use -stable versions of FreeBSD and OpenBSD. Following are the specs on the boxes: HP dx5150 AMD Sempron 3000+ ATI Radeon Xpress 200 chipset ATI SATA/100 hdd ATI USB ATI Integrated Graphics Broadcom BCM5751 network HP/ATI specific Award bios, v1.06 I have tried installs with fbsd 4.11, 5.4 and obsd 3.7 and 3.8. I have done enough searching of mailing lists and google to know that this chipset is problematic at the moment for BSD and for that matter linux, however I hoping that someone can suggest fixes, work arounds, and expected upcoming releases that will allow me to run these boxes reliably on stable versions of fbsd and obsd. For all the installs I made the following changes to the default BIOS settings: Advanced Chipset features: GFX Multi-Function Mode: disabled UMA Frame Buffer Size: 16M Video Display Devices: CRT only Init Display First: Onboard fbsd 4.11 was the only one I was able to get to install fully and with basic functionality, including network working. Although I am not confident in its long term stability (continuous stray IRQ errors, incorrect drive geometry detection which is not correctable via fdisk, disfunctional APM) fbsd 5.4 boot fails unless APIC mode is completely disabled under Advanced BIOS Features, I tried it active with both MPS versions 1.1 and 1.4. It will boot fully with APIC disabled but the bge driver fails to initialize and drive geometry is incorrectly detected as in 4.11, and the install invariably fails with a panic at various point during the copying of files to the new volumes (possibly to bad drive geometry?). APM driver(s) also seem to fail initialization. obsd 3.7 boots and installs, but unless USB Legacy support under Integrated Perifpherals/OnChip USB Controller is disabled the PS/2 attached keyboard ceases to function (stalling install at the install/upgrade/shell prompt unless using serial console). As with fbsd5.4 the bge driver and apm driver(s) fail to initialize. obsd also incorrectly detects drive geometry but gets closer to the actual numbers fbsd, I did not try to manually correct, I am not as familiar/comfortable with openbsd's disklabel, the drive did "seem" more stable. obsd 3.8 boot fails completely unless USB Legacy support is disabled, with it disabled I was able to complete the install, however as with 3.7 and fbsd5.4 the bge and apm drivers fail to initialize. APIC settings did not seem to affect obsd boot or installs, also there are no specific BIOS settings specifically identifying the installed OS as PNP or not. The PNP settings consist of "Reset Confifuration Data [enable/disable]", "Resources Controlled By [Auto(ESCD)/Manual]" with a Manual sub-menu of "IRQ x [PCI/reserved]", "Assign IRQ for VGA [enable/disable]", and "Assign IRQ for USB [enable/disable]". Manipulation of these settings had no apparent effect on the obsd or fbsd booting. Attached are the dmesg dumps from the various boot/install attempts, if you need any other info to help diagnose please let me know. I am hoping someone can help me get these to work, as I am not looking for forward to trying to return them to the vendor. Thanks Jeffrey Williams jeff@sailorfej.net dmesgs for fbsd4.11, fbsd5.4-APIC1.1, fbsd5.4-APIC1.4, fbsd5.4-noAPIC, obsd3.7-legUSB, obsd3.7-nolegUSB, obsd3.8-legUSB, obsd3.8-nolegUSB ************************************* ************************** fbsd 4.11 ************************************* Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.11-RELEASE #0: Fri Jan 21 17:21:22 GMT 2005 root@perseus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: AMD Sempron(tm) Processor 3000+ (1790.84-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x10ff0 Stepping = 0 Features=0x78bfbff AMD Features=0xc0500000<,AMIE,DSP,3DNow!> real memory = 233766912 (228288K bytes) avail memory = 221896704 (216696K bytes) Preloaded elf kernel "kernel" at 0xc055c000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib5: at device 1.0 on pci0 pci1: on pcib5 pci1: at 5.0 irq 11 pcib6: at device 5.0 on pci0 pci2: on pcib6 bge0: mem 0xfdef0000-0xfdefffff irq 11 at device 0.0 on pci2 bge0: Ethernet address: 00:13:d3:95:43:b9 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto atapci0: port 0xec00-0xec0f,0xf000-0xf003,0xf400-0xf407,0xf800-0xf803,0xfc00-0xfc07 mem 0xfe02f000-0xfe02f1ff irq 5 at device 18.0 on pci0 ata2: at 0xfc00 on atapci0 ata3: at 0xf400 on atapci0 ohci0: mem 0xfe02e000-0xfe02efff irq 10 at device 19.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1002) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1: mem 0xfe02d000-0xfe02dfff irq 10 at device 19.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: (0x1002) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered pci0: at 19.2 irq 10 pci0: (vendor=0x1002, dev=0x4372) at 20.0 atapci1: port 0xe400-0xe40f,0-0x3,0-0x7,0-0x3,0-0x7 at device 20.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 isab0: at device 20.3 on pci0 isa0: on isab0 pcib7: at device 20.4 on pci0 pci3: on pcib7 pcib1: on motherboard pci4: on pcib1 pcib2: on motherboard pci5: on pcib2 pcib3: on motherboard pci6: on pcib3 pcib4: on motherboard pci7: on pcib4 orm0: