From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 01:07:47 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F126116A4DF for ; Sun, 23 Jul 2006 01:07:47 +0000 (UTC) (envelope-from tyler@bleepsoft.com) Received: from zeus.lunarpages.com (zeus.lunarpages.com [216.193.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8456D43D45 for ; Sun, 23 Jul 2006 01:07:47 +0000 (GMT) (envelope-from tyler@bleepsoft.com) Received: from [24.240.211.104] (helo=[192.168.250.100]) by zeus.lunarpages.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.52) id 1G4SSe-0005xF-N2 for freebsd-hackers@freebsd.org; Sat, 22 Jul 2006 18:08:48 -0700 Mime-Version: 1.0 (Apple Message framework v752.2) To: FreeBSD Hackers Message-Id: <7ADD22A7-42DE-49D8-B411-DBA4CB2FA0CD@bleepsoft.com> Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-36--784001877" From: "R. Tyler Ballance" Date: Sat, 22 Jul 2006 20:07:37 -0500 Content-Transfer-Encoding: 7bit X-Pgp-Agent: GPGMail 1.1.2 (Tiger) X-Mailer: Apple Mail (2.752.2) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zeus.lunarpages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - bleepsoft.com X-Source: X-Source-Args: X-Source-Dir: X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Building a sandboxed kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 01:07:48 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-36--784001877 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed I'm working on a project that relies on me building kernels outside of the standard /usr/src (typically ~/perforce/projects/ ) on my relatively standard 6.1-STABLE workstation. I'm wondering if I'd be best suited by setting up a jail for kernel builds, I'm following this doc: http://people.freebsd.org/~cognet/freebsd_arm.txt loosely because I've created a new "arch folder" in src/sys for the kernel code that I want to build (right now it's unmodified i386 code) Between varying versions of userland tools (like config(8)) and path troubles, I'm wondering what tips anybody has to doing non-standard builds of the kernel (non-standard being not in /usr/src and not the host arch) Currently the make command I'm using, which doesn't work, is (/usr/ obj is chmod'd 777): make TARGET_ARCH=iguana DESTDIR=/home/tyler/iguana buildkernel Any suggestions? Cheers, -R. Tyler Ballance --Apple-Mail-36--784001877 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFEwsvaqO6nEJfroRsRAhjEAKCWHUlLBBALA6LRHNaI2S3/USqtFACdHUf7 iYn2rcg5aQCFMyISz3Wq+gA= =HFle -----END PGP SIGNATURE----- --Apple-Mail-36--784001877-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 01:51:47 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C01316A4E0 for ; Sun, 23 Jul 2006 01:51:47 +0000 (UTC) (envelope-from tyler@bleepsoft.com) Received: from zeus.lunarpages.com (zeus.lunarpages.com [216.193.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E600043D58 for ; Sun, 23 Jul 2006 01:51:45 +0000 (GMT) (envelope-from tyler@bleepsoft.com) Received: from [24.240.211.104] (helo=[192.168.250.100]) by zeus.lunarpages.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.52) id 1G4T9D-0005aT-BK for freebsd-hackers@freebsd.org; Sat, 22 Jul 2006 18:52:47 -0700 Mime-Version: 1.0 (Apple Message framework v752.2) To: FreeBSD Hackers Message-Id: Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-38--781357085" From: "R. Tyler Ballance" Date: Sat, 22 Jul 2006 20:51:41 -0500 Content-Transfer-Encoding: 7bit X-Pgp-Agent: GPGMail 1.1.2 (Tiger) X-Mailer: Apple Mail (2.752.2) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zeus.lunarpages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - bleepsoft.com X-Source: X-Source-Args: X-Source-Dir: X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Machine-dependent code extension? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 01:51:47 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-38--781357085 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed I'm just wondering, the machine-dependent assembly tied into the i386 kernel, that's all named ${FILENAME}., while in the arm/ kernel machine-dependent code is named ${FILENAME}.S, what's the difference? Or is there none, just a change in convention? Cheers, -R. Tyler Ballance --Apple-Mail-38--781357085 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFEwtYvqO6nEJfroRsRAtnPAJ4vKG9cQ/vEerTH3p6qTaMK5N9S5QCfR42z xi8JOq2Pt4sQ2snp3+QDoow= =MVtj -----END PGP SIGNATURE----- --Apple-Mail-38--781357085-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 09:18:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9F1F16A4DD; Sun, 23 Jul 2006 09:18:41 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBC4643D5F; Sun, 23 Jul 2006 09:18:31 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.7/8.13.7) with ESMTP id k6N9IO3o079925 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 23 Jul 2006 11:18:24 +0200 (CEST) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.7/8.13.3/Submit) id k6N9IOjW079924; Sun, 23 Jul 2006 11:18:24 +0200 (CEST) Date: Sun, 23 Jul 2006 11:18:24 +0200 From: Divacky Roman To: Daniel Eischen Message-ID: <20060723091824.GA79726@stud.fit.vutbr.cz> References: <200607221914.15826.lofi@freebsd.org> <200607222341.05180.lofi@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.54 on 147.229.10.14 Cc: freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org, kmacy@fsmware.com, Michael Nottebrock Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 09:18:41 -0000 On Sat, Jul 22, 2006 at 07:15:35PM -0400, Daniel Eischen wrote: > On Sat, 22 Jul 2006, Michael Nottebrock wrote: > > >On Saturday, 22. July 2006 21:20, Kip Macy wrote: > >>Thanks for your input. > >> > >>The relative merits of the different threading libraries is currently > >>under discussion. Could you also try it with libthr (it may not work > >>at all), I'd like to hear what happens. Thanks. > > > >WINE crashes in roughly the same spot. This is however with a libthr on > >FreeBSD 5.5-RELEASE-p2, which is nothing short of disastrous (with a global > >lib mapping from libpthread to libthr, about 1/3 of all the programs in my > >default KDE session start at all - the rest hangs in state sbwait). > > I think it is because WINE stomps on or TLS. Nothing we can > do about that except patch wine so it doesn't. Look at the > console messages for: > > Warning: pid XXX used static ldt allocation I dont know details but judging from what linux does I think it might be that wine requires more then one GDT entry for TLS areas. at least comment in linux sources suggests so. linux has 3 GDT entries for TLS while fbsd just 1. my 2 cents roman From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 09:31:34 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEC2716A4E1 for ; Sun, 23 Jul 2006 09:31:34 +0000 (UTC) (envelope-from shangjie.li@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 232D543D46 for ; Sun, 23 Jul 2006 09:31:33 +0000 (GMT) (envelope-from shangjie.li@gmail.com) Received: by ug-out-1314.google.com with SMTP id j3so1840176ugf for ; Sun, 23 Jul 2006 02:31:33 -0700 (PDT) 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=UBXRgHFHR7B9z+ve+Y51Zh9Kab50B4BV/BaawB27JwJrgwPSILLP6nftReF7u5wRU9jOHaEzwD/1HxxVZLKt/Suvl23GmKibPhwwG9dRY0dVC1uMou6BoAtNgY+dsRjxcuNG4WmZp84gLO4R+L2eHyIlHrcN59YM6XNvvwTpgcw= Received: by 10.78.122.11 with SMTP id u11mr1064285huc; Sun, 23 Jul 2006 02:31:33 -0700 (PDT) Received: by 10.78.127.20 with HTTP; Sun, 23 Jul 2006 02:31:32 -0700 (PDT) Message-ID: Date: Sun, 23 Jul 2006 17:31:32 +0800 From: "=?GB2312?B?wO7J0L3c?=" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: An error about IPC permission checking X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 09:31:34 -0000 in the source code kern/sysv_shm.c: 729 error = ipcperm(td, &shmseg->u.shm_perm, mode); 730 #ifdef MAC 731 error = mac_check_sysv_shmget(td->td_ucred, shmseg, uap->shmflg); 732 if (error != 0) 733 MPRINTF(("mac_check_sysv_shmget returned %d\n", error)); 734 #endif 735 if (error) 736 return (error); The return value of ipcperm() call is not be checked in time, and interrupted by mac checking, if Mac is enabled. -- -- |Best regards. |Shangjie, Li (Ph.D candidate) |Institute of Software, Chinese Academy of Sciences, |P.O. Box 8718, Beijing 100080, CHINA |Phone: (8610)62561197/62635158-1008(O), 82680528(H) |Email: shangjie02@ios.cn >---------------------------------------------------< From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 10:02:59 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75D4D16A4DD for ; Sun, 23 Jul 2006 10:02:59 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id B165D43D46 for ; Sun, 23 Jul 2006 10:02:58 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (patr530-a238.otenet.gr [212.205.215.238]) (authenticated bits=128) by igloo.linux.gr (8.13.7/8.13.7/Debian-1) with ESMTP id k6NA2aNw023824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 23 Jul 2006 13:02:40 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.7/8.13.7) with ESMTP id k6NA2OWv024862; Sun, 23 Jul 2006 13:02:25 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.7/8.13.7/Submit) id k6NA2Nhe024861; Sun, 23 Jul 2006 13:02:23 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 23 Jul 2006 13:02:23 +0300 From: Giorgos Keramidas To: "R. Tyler Ballance" Message-ID: <20060723100223.GB24435@gothmog.pc> References: <7ADD22A7-42DE-49D8-B411-DBA4CB2FA0CD@bleepsoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7ADD22A7-42DE-49D8-B411-DBA4CB2FA0CD@bleepsoft.com> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.197, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.20, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-hackers@freebsd.org Subject: Re: Building a sandboxed kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 10:02:59 -0000 On 2006-07-22 20:07, "R. Tyler Ballance" wrote: > I'm working on a project that relies on me building kernels outside > of the standard /usr/src (typically ~/perforce/projects/ ) on my > relatively standard 6.1-STABLE workstation. I'm wondering if I'd be > best suited by setting up a jail for kernel builds, I'm following > this doc: http://people.freebsd.org/~cognet/freebsd_arm.txt loosely > because I've created a new "arch folder" in src/sys for the kernel > code that I want to build (right now it's unmodified i386 code) > > Between varying versions of userland tools (like config(8)) and path > troubles, I'm wondering what tips anybody has to doing non-standard > builds of the kernel (non-standard being not in /usr/src and not the > host arch) > > Currently the make command I'm using, which doesn't work, is (/usr/ > obj is chmod'd 777): > > make TARGET_ARCH=iguana DESTDIR=/home/tyler/iguana buildkernel > > Any suggestions? You don't have to use /usr/obj for all your builds: % mkdir -p /home/tyler/obj/iguana % env MAKEOBJDIRPREFIX=/home/tyler/obj/iguana \ make TARGET_ARCH=iguana \ DESTDIR=/home/tyler/iguana \ buildkernel The trick here is to use MAKEOBJDIRPREFIX to change the default object directory prefix from `/usr/obj' to whatever suits your own setup. From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 10:08:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAF8916A4DD for ; Sun, 23 Jul 2006 10:08:42 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23C9543D4C for ; Sun, 23 Jul 2006 10:08:41 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (patr530-a238.otenet.gr [212.205.215.238]) (authenticated bits=128) by igloo.linux.gr (8.13.7/8.13.7/Debian-1) with ESMTP id k6NA8Cdx023995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 23 Jul 2006 13:08:17 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.7/8.13.7) with ESMTP id k6NA80sF024913; Sun, 23 Jul 2006 13:08:01 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.7/8.13.7/Submit) id k6NA80P2024912; Sun, 23 Jul 2006 13:08:00 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 23 Jul 2006 13:08:00 +0300 From: Giorgos Keramidas To: "R. Tyler Ballance" Message-ID: <20060723100800.GC24435@gothmog.pc> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.572, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL -0.45, BAYES_00 -2.60, INFO_TLD 1.27) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-hackers@freebsd.org Subject: Re: Machine-dependent code extension? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 10:08:42 -0000 On 2006-07-22 20:51, "R. Tyler Ballance" wrote: > I'm just wondering, the machine-dependent assembly tied into the i386 > kernel, that's all named ${FILENAME}., while in the arm/ kernel > machine-dependent code is named ${FILENAME}.S, what's the difference? > Or is there none, just a change in convention? It looks like you missed a ".s" extension in the i386 case above, right? If this is what you are asking, then the difference between *.s and *.S is that the latter is preprocessed by cpp(1). The GNU as(1) manual hints at this difference here: File: as.info, Node: Preprocessing, Next: Whitespace, Up: Syntax 3.1 Preprocessing ================= The `as' internal preprocessor: * adjusts and removes extra whitespace. It leaves one space or tab before the keywords on a line, and turns any other whitespace on the line into a single space. * removes all comments, replacing them with a single space, or an appropriate number of newlines. * converts character constants into the appropriate numeric values. It does not do macro processing, include file handling, or anything else you may get from your C compiler's preprocessor. You can do include file processing with the `.include' directive (*note `.include': ! Include.). You can use the GNU C compiler driver to get other "CPP" ! style preprocessing by giving the input file a `.S' suffix. *Note ! Options Controlling the Kind of Output: (gcc.info)Overall Options. Excess whitespace, comments, and character constants cannot be used in the portions of the input text that are not preprocessed. From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 10:52:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D785916A50A for ; Sun, 23 Jul 2006 10:52:49 +0000 (UTC) (envelope-from tyler@bleepsoft.com) Received: from zeus.lunarpages.com (zeus.lunarpages.com [216.193.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 280A943D4C for ; Sun, 23 Jul 2006 10:52:42 +0000 (GMT) (envelope-from tyler@bleepsoft.com) Received: from [24.240.211.104] (helo=[192.168.250.100]) by zeus.lunarpages.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.52) id 1G4bai-00019h-Sl for freebsd-hackers@freebsd.org; Sun, 23 Jul 2006 03:53:45 -0700 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <20060723100223.GB24435@gothmog.pc> References: <7ADD22A7-42DE-49D8-B411-DBA4CB2FA0CD@bleepsoft.com> <20060723100223.GB24435@gothmog.pc> X-Gpgmail-State: !signed Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <3320CEAC-8A5C-407D-9867-C2A22820A599@bleepsoft.com> Content-Transfer-Encoding: 7bit From: "R. Tyler Ballance" Date: Sun, 23 Jul 2006 05:52:39 -0500 To: FreeBSD Hackers X-Mailer: Apple Mail (2.752.2) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zeus.lunarpages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - bleepsoft.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: Building a sandboxed kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 10:52:49 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> Between varying versions of userland tools (like config(8)) and path >> troubles, I'm wondering what tips anybody has to doing non-standard >> builds of the kernel (non-standard being not in /usr/src and not the >> host arch) >> >> Currently the make command I'm using, which doesn't work, is (/usr/ >> obj is chmod'd 777): >> >> make TARGET_ARCH=iguana DESTDIR=/home/tyler/iguana buildkernel >> >> Any suggestions? > > You don't have to use /usr/obj for all your builds: > > % mkdir -p /home/tyler/obj/iguana > % env MAKEOBJDIRPREFIX=/home/tyler/obj/iguana \ > make TARGET_ARCH=iguana \ > DESTDIR=/home/tyler/iguana \ > buildkernel > > The trick here is to use MAKEOBJDIRPREFIX to change the default object > directory prefix from `/usr/obj' to whatever suits your own setup. This doesn't solve the problem of different versions of userland tools required. For example, my machne is RELENG_6, but I'm developing against the -CURRENT branch of code synced up in perforce. Does one necessarily need a -CURRENT userland to develop with the - CURRENT code base? All arguments of being able to test the code that is built are moot since the testing of my code will all occur within a virtualized (Qemu) machine environment. I'm sure the difference in versions between RELENG_6 and CURRENT aren't too great, but what about developing with CURRENT code on RELENG_5? I guess the basic question is, how can I maintain my normal workstation environment while using a toolset appropriate for building CURRENT? (Does it even matter really?) Cheers, - -R. Tyler Ballance -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFEw1TuqO6nEJfroRsRArxCAJ44DICg+wi65O6ymBh6BNYY8bE1tACdEPTn Tpb8/URR87blmlVDrxQV95M= =SZau -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 11:17:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0721E16A4DD for ; Sun, 23 Jul 2006 11:17:37 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8147C43D46 for ; Sun, 23 Jul 2006 11:17:36 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 69EE32083; Sun, 23 Jul 2006 13:17:31 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 51E652082; Sun, 23 Jul 2006 13:17:31 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 26B1E33C31; Sun, 23 Jul 2006 13:17:31 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: "R. Tyler Ballance" References: <7ADD22A7-42DE-49D8-B411-DBA4CB2FA0CD@bleepsoft.com> <20060723100223.GB24435@gothmog.pc> <3320CEAC-8A5C-407D-9867-C2A22820A599@bleepsoft.com> Date: Sun, 23 Jul 2006 13:17:30 +0200 In-Reply-To: <3320CEAC-8A5C-407D-9867-C2A22820A599@bleepsoft.com> (R. Tyler Ballance's message of "Sun, 23 Jul 2006 05:52:39 -0500") Message-ID: <86mzb0vad1.fsf@xps.des.no> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Hackers Subject: Re: Building a sandboxed kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 11:17:37 -0000 "R. Tyler Ballance" writes: > This doesn't solve the problem of different versions of userland > tools required. $ cd /foo/bar/src $ make kernel-toolchain TARGET_ARCH=3Diguana $ make buildkernel TARGET_ARCH=3Diguana no need for a jail or a chroot or anything; buildkernel will use the cross-building toolchain built by kernel-toolchain. note 1: you don't need DESTDIR to build, only to install. note 2: you probably want to use NO_KERNELCLEAN to avoid starting every buildkernel from scratch. note 3: most of this is documented in build(7) DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 11:23:38 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D65D216A4DA for ; Sun, 23 Jul 2006 11:23:38 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3463C43D45 for ; Sun, 23 Jul 2006 11:23:37 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.7/8.13.7) with ESMTP id k6NBNWtO083617 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 23 Jul 2006 13:23:32 +0200 (CEST) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.7/8.13.3/Submit) id k6NBNWr7083616 for hackers@freebsd.org; Sun, 23 Jul 2006 13:23:32 +0200 (CEST) Date: Sun, 23 Jul 2006 13:23:32 +0200 From: Divacky Roman To: hackers@freebsd.org Message-ID: <20060723112332.GA83581@stud.fit.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.54 on 147.229.10.14 Cc: Subject: i386 registers during a syscall X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 11:23:38 -0000 hi, I need to get content of %esi register as it was during a syscall. Should I get this info from td->td_pcb->pcb_esi or td->td_frame->tf_esi? Is it so that trapframe is "content of registers when entering a kernel" and pcb is "when leaving a kernel" ? thnx for info roman ---------------------- www.liberalnistrana.cz From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 11:53:00 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E96DF16A4DD for ; Sun, 23 Jul 2006 11:53:00 +0000 (UTC) (envelope-from tarc@tarc.po.cs.msu.su) Received: from tarc.po.cs.msu.su (tarc.po.cs.msu.su [158.250.16.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0132B43D45 for ; Sun, 23 Jul 2006 11:52:59 +0000 (GMT) (envelope-from tarc@tarc.po.cs.msu.su) Received: from tarc.po.cs.msu.su (localhost [127.0.0.1]) by tarc.po.cs.msu.su (8.13.4/8.13.4) with ESMTP id k6NBsQnp044702 for ; Sun, 23 Jul 2006 15:54:26 +0400 (MSD) (envelope-from tarc@tarc.po.cs.msu.su) Received: (from tarc@localhost) by tarc.po.cs.msu.su (8.13.4/8.13.4/Submit) id k6NBsP8M044701 for freebsd-hackers@freebsd.org; Sun, 23 Jul 2006 15:54:25 +0400 (MSD) (envelope-from tarc) Date: Sun, 23 Jul 2006 15:54:25 +0400 From: Arseny Nasokin To: freebsd-hackers@freebsd.org Message-ID: <20060723115425.GD12706@tarc.po.cs.msu.su> References: <44BFAE1D.30906@cwt.uz> <44C0D55B.60500@preved.cn> <20060722042347.GE53239@gothmog.pc> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20060722042347.GE53239@gothmog.pc> User-Agent: mutt-ng/devel-r581 (FreeBSD) Subject: Re: New Welcome message for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 11:53:01 -0000 On Sat, Jul 22, 2006 at 07:23:47AM +0300, Giorgos Keramidas wrote: > On 2006-07-21 17:23, Tarasov Alexey wrote: > >Timur Yuldashev wrote: > >> New motd-welcome message for FreeBSD. > >> > >> http://www.cwt.uz/motd > >> > >> best regards > > > > I like it! Very good. > > I don't. It is pretty "content free" when compared with our current > default motd. > > The information in the current motd file is useful and provides hints > towards stuff that may be interesting both to a new admin who just > installed FreeBSD and a new user who just happened to log into a FreeBSD > system. > > More importantly, the default /etc/motd is just a sample motd file, > which you are free to edit locally :) > I prefer put default motd to support(7) page. and set this motd as default -- Best regards, Arseny Nasokin From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 16:21:07 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6A4D16A4E9 for ; Sun, 23 Jul 2006 16:21:07 +0000 (UTC) (envelope-from tijl@ulyssis.org) Received: from outmx014.isp.belgacom.be (outmx014.isp.belgacom.be [195.238.4.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1818343D45 for ; Sun, 23 Jul 2006 16:21:06 +0000 (GMT) (envelope-from tijl@ulyssis.org) Received: from outmx014.isp.belgacom.be (localhost [127.0.0.1]) by outmx014.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6NGL4Nm020611 for ; Sun, 23 Jul 2006 18:21:04 +0200 (envelope-from ) Received: from kalimero.kotnet.org (88.193-245-81.adsl-dyn.isp.belgacom.be [81.245.193.88]) by outmx014.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6NGL0pA020572 for ; Sun, 23 Jul 2006 18:21:00 +0200 (envelope-from ) Received: from kalimero.kotnet.org (kalimero.kotnet.org [127.0.0.1]) by kalimero.kotnet.org (8.13.6/8.13.6) with ESMTP id k6NGJcYA026039 for ; Sun, 23 Jul 2006 18:19:38 +0200 (CEST) (envelope-from tijl@ulyssis.org) From: Tijl Coosemans To: freebsd-hackers@freebsd.org Date: Sun, 23 Jul 2006 18:19:30 +0200 User-Agent: KMail/1.9.3 References: <200607221914.15826.lofi@freebsd.org> <20060723091824.GA79726@stud.fit.vutbr.cz> In-Reply-To: <20060723091824.GA79726@stud.fit.vutbr.cz> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart16024009.7F5hMMiKkD"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607231819.37642.tijl@ulyssis.org> Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 16:21:07 -0000 --nextPart16024009.7F5hMMiKkD Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 23 July 2006 11:18, Divacky Roman wrote: > On Sat, Jul 22, 2006 at 07:15:35PM -0400, Daniel Eischen wrote: > > I think it is because WINE stomps on or TLS. Nothing we can > > do about that except patch wine so it doesn't. Look at the > > console messages for: > > > > Warning: pid XXX used static ldt allocation Wine's LDT code could probably be improved to bring in LDT_AUTO_ALLOC=20 and/or use the GDT entry for %fs through i386_set_fsbase() for TLS=20 instead of allocating an LDT entry (per thread). But, I don't think=20 this is currently a problem. As far as I can see FreeBSD's TLS support=20 doesn't use the LDT (anymore) so wine's static ldt allocation can't=20 possibly interfere with it. > I dont know details but judging from what linux does I think it might > be that wine requires more then one GDT entry for TLS areas. at least > comment in linux sources suggests so. > > linux has 3 GDT entries for TLS while fbsd just 1. Wine on FreeBSD doesn't use the GDT (yet?). It allocates LDT entries for=20 TLS which should work just as well. In any case, FreeBSD and Linux don't differ that much in this. =46reeBSD has 2 GDT entries available, one for %gs which is used by the=20 threading libs (following http://people.redhat.com/drepper/tls.pdf I=20 suppose) and one for %fs which is used by win32 code so wine could use=20 this instead of the LDT way. The related (undocumented) libc functions=20 are i386_get_fsbase, i386_set_fsbase, i386_get_gsbase and=20 i386_set_gsbase. Linux reserves 3 GDT entries, that can be manipulated through one=20 syscall (set_thread_area) and then it's up to the user to point %fs=20 or %gs (or some other selector?) to one of these entries. --nextPart16024009.7F5hMMiKkD Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQBEw6GZdMR2xnarec8RAiFCAKC/ac0cKBUNYC4YQm39cx7HsxjAWwCglwuq L+gCHC+iXaMNY/q2S4I8pz0= =VBHV -----END PGP SIGNATURE----- --nextPart16024009.7F5hMMiKkD-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 16:31:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45A5816A4DD; Sun, 23 Jul 2006 16:31:49 +0000 (UTC) (envelope-from tijl@ulyssis.org) Received: from outmx022.isp.belgacom.be (outmx022.isp.belgacom.be [195.238.4.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1E1543D46; Sun, 23 Jul 2006 16:31:46 +0000 (GMT) (envelope-from tijl@ulyssis.org) Received: from outmx022.isp.belgacom.be (localhost [127.0.0.1]) by outmx022.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6NGVdLA017684; Sun, 23 Jul 2006 18:31:39 +0200 (envelope-from ) Received: from kalimero.kotnet.org (88.193-245-81.adsl-dyn.isp.belgacom.be [81.245.193.88]) by outmx022.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6NGVasu017665; Sun, 23 Jul 2006 18:31:36 +0200 (envelope-from ) Received: from kalimero.kotnet.org (kalimero.kotnet.org [127.0.0.1]) by kalimero.kotnet.org (8.13.6/8.13.6) with ESMTP id k6NGVWKr026231; Sun, 23 Jul 2006 18:31:32 +0200 (CEST) (envelope-from tijl@ulyssis.org) From: Tijl Coosemans To: freebsd-hackers@freebsd.org Date: Sun, 23 Jul 2006 18:31:27 +0200 User-Agent: KMail/1.9.3 References: <200607221914.15826.lofi@freebsd.org> <20060723091824.GA79726@stud.fit.vutbr.cz> In-Reply-To: <20060723091824.GA79726@stud.fit.vutbr.cz> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3152903.kl0IZcXFWA"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607231831.32410.tijl@ulyssis.org> Cc: Daniel Eischen , Divacky Roman , kmacy@fsmware.com, freebsd-emulation@freebsd.org, Michael Nottebrock Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 16:31:49 -0000 --nextPart3152903.kl0IZcXFWA Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 23 July 2006 11:18, Divacky Roman wrote: > On Sat, Jul 22, 2006 at 07:15:35PM -0400, Daniel Eischen wrote: > > I think it is because WINE stomps on or TLS. =A0Nothing we can > > do about that except patch wine so it doesn't. =A0Look at the > > console messages for: > > > > =A0 Warning: pid XXX used static ldt allocation Wine's LDT code could probably be improved to bring in LDT_AUTO_ALLOC=20 and/or use the GDT entry for %fs through i386_set_fsbase() for TLS=20 instead of allocating an LDT entry (per thread). But, I don't think=20 this is currently a problem. As far as I can see FreeBSD's TLS support=20 doesn't use the LDT (anymore) so wine's static ldt allocation can't=20 possibly interfere with it. > I dont know details but judging from what linux does I think it might > be that wine requires more then one GDT entry for TLS areas. at least > comment in linux sources suggests so. > > linux has 3 GDT entries for TLS while fbsd just 1. Wine on FreeBSD doesn't use the GDT (yet?). It allocates LDT entries for=20 TLS which should work just as well. In any case, FreeBSD and Linux don't differ that much in this. =46reeBSD has 2 GDT entries available, one for %gs which is used by the=20 threading libs (following http://people.redhat.com/drepper/tls.pdf I=20 suppose) and one for %fs which is used by win32 code so wine could use=20 this instead of the LDT way. The related (undocumented) libc functions=20 are i386_get_fsbase, i386_set_fsbase, i386_get_gsbase and=20 i386_set_gsbase. Linux reserves 3 GDT entries, that can be manipulated through one=20 syscall (set_thread_area) and then it's up to the user to point %fs=20 or %gs (or some other selector?) to one of these entries. --nextPart3152903.kl0IZcXFWA Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQBEw6RkdMR2xnarec8RAmiZAKCxPxrOeOEXIDvTORBkVMZuFTTHMACgyNNQ s1337fO7ram0QU52sVBd/XA= =dP1Q -----END PGP SIGNATURE----- --nextPart3152903.kl0IZcXFWA-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 16:56:21 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3C8F16A4DF for ; Sun, 23 Jul 2006 16:56:20 +0000 (UTC) (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 9C61743D4C for ; Sun, 23 Jul 2006 16:56:17 +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.4/8.13.4) with ESMTP id k6NGtUdH029743; Sun, 23 Jul 2006 10:55:30 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 23 Jul 2006 10:55:49 -0600 (MDT) Message-Id: <20060723.105549.2106235963.imp@bsdimp.com> To: tyler@bleepsoft.com From: "M. Warner Losh" In-Reply-To: <3320CEAC-8A5C-407D-9867-C2A22820A599@bleepsoft.com> References: <7ADD22A7-42DE-49D8-B411-DBA4CB2FA0CD@bleepsoft.com> <20060723100223.GB24435@gothmog.pc> <3320CEAC-8A5C-407D-9867-C2A22820A599@bleepsoft.com> X-Mailer: Mew version 4.2 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]); Sun, 23 Jul 2006 10:55:31 -0600 (MDT) Cc: freebsd-hackers@freebsd.org Subject: Re: Building a sandboxed kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 16:56:21 -0000 In message: <3320CEAC-8A5C-407D-9867-C2A22820A599@bleepsoft.com> "R. Tyler Ballance" writes: : -----BEGIN PGP SIGNED MESSAGE----- : Hash: SHA1 : : >> : >> Between varying versions of userland tools (like config(8)) and path : >> troubles, I'm wondering what tips anybody has to doing non-standard : >> builds of the kernel (non-standard being not in /usr/src and not the : >> host arch) : >> : >> Currently the make command I'm using, which doesn't work, is (/usr/ : >> obj is chmod'd 777): : >> : >> make TARGET_ARCH=iguana DESTDIR=/home/tyler/iguana buildkernel : >> : >> Any suggestions? : > : > You don't have to use /usr/obj for all your builds: : > : > % mkdir -p /home/tyler/obj/iguana : > % env MAKEOBJDIRPREFIX=/home/tyler/obj/iguana \ : > make TARGET_ARCH=iguana \ : > DESTDIR=/home/tyler/iguana \ : > buildkernel : > : > The trick here is to use MAKEOBJDIRPREFIX to change the default object : > directory prefix from `/usr/obj' to whatever suits your own setup. : : : This doesn't solve the problem of different versions of userland : tools required. For example, my machne is RELENG_6, but I'm : developing against the -CURRENT branch of code synced up in perforce. : Does one necessarily need a -CURRENT userland to develop with the - : CURRENT code base? All arguments of being able to test the code that : is built are moot since the testing of my code will all occur within : a virtualized (Qemu) machine environment. : : I'm sure the difference in versions between RELENG_6 and CURRENT : aren't too great, but what about developing with CURRENT code on : RELENG_5? I guess the basic question is, how can I maintain my normal : workstation environment while using a toolset appropriate for : building CURRENT? (Does it even matter really?) Doesn't matter. I often do the following: setenv TARGET arm # this may be iguana for you setenv TARGET_ARCH arm setenv MAKEOBJDIRPREFIX /home/imp/obj cd p4/imp_arm make buildworld make buildenv # from here on out is in a subshell cd ../arm/src/sys/arm/conf config KB920X cd ../compile/KB920X make depend && make You'll notice that I built in a tree that had all the arm patches applied, and got a 'buildenv' there, but then build the kernel out of a different tree. This is a -current p4 tree for both imp_arm and arm, but I do this on a RELENG_6 system. I've done it in the recent past on a 5.3 system too. TARGET is MACHINE and TARGET_ARCH is MACHINE_ARCH. MACHINE is the kernel architecture, while MACHINE_ARCH is the CPU architecture (TARGET_CPU is the specific CPU that we're optimizing for). Chances are excellent we'll have TARGET_ARCH armel and armeb shortly. Right now we have a hack ARM_BIG_ENDIAN used to control big vs little endian, but since MACHINE_ARCH gets encoded into packages, I think we need to move it there so binary packages do the right thing. But that's a WIP in my tree right now... Warner From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 19:42:27 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9EF616A4DE; Sun, 23 Jul 2006 19:42:27 +0000 (UTC) (envelope-from lofi@freebsd.org) Received: from mail-in-04.arcor-online.net (mail-in-04.arcor-online.net [151.189.21.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9A0243D45; Sun, 23 Jul 2006 19:42:26 +0000 (GMT) (envelope-from lofi@freebsd.org) Received: from mail-in-06-z2.arcor-online.net (mail-in-06-z2.arcor-online.net [151.189.8.18]) by mail-in-04.arcor-online.net (Postfix) with ESMTP id 65BC114AAB9; Sun, 23 Jul 2006 21:42:25 +0200 (CEST) Received: from mail-in-03.arcor-online.net (mail-in-03.arcor-online.net [151.189.21.43]) by mail-in-06-z2.arcor-online.net (Postfix) with ESMTP id 56DB61A01DA; Sun, 23 Jul 2006 21:42:25 +0200 (CEST) Received: from lofi.dyndns.org (dslb-084-061-132-214.pools.arcor-ip.net [84.61.132.214]) by mail-in-03.arcor-online.net (Postfix) with ESMTP id 0C7C420F209; Sun, 23 Jul 2006 21:42:25 +0200 (CEST) Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) by lofi.dyndns.org (8.13.4/8.13.3) with ESMTP id k6NJgJ4j055372 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 23 Jul 2006 21:42:20 +0200 (CEST) (envelope-from lofi@freebsd.org) Received: from kiste.my.domain (localhost [127.0.0.1]) by kiste.my.domain (8.13.6/8.13.4) with ESMTP id k6NJgIa9036691; Sun, 23 Jul 2006 21:42:18 +0200 (CEST) (envelope-from lofi@freebsd.org) Received: by kiste.my.domain (8.13.6/8.13.4/Submit) id k6NJgG3Z036690; Sun, 23 Jul 2006 21:42:16 +0200 (CEST) (envelope-from lofi@freebsd.org) X-Authentication-Warning: kiste.my.domain: lofi set sender to lofi@freebsd.org using -f From: Michael Nottebrock To: kmacy@fsmware.com Date: Sun, 23 Jul 2006 21:42:12 +0200 User-Agent: KMail/1.9.3 References: <200607221914.15826.lofi@freebsd.org> <200607222341.05180.lofi@freebsd.org> In-Reply-To: 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: freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 19:42:27 -0000 --nextPart6206001.iiAGvT54bV Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday, 23. July 2006 00:59, Kip Macy wrote: > Thanks. That is a useful data point but David Xu has done a lot of > work on libthr that has probably not been MFC'd back to 5.x. When I > get the chance I'll try building KDE on my desktop which runs a > derivative of -CURRENT. At least on FreeBSD 5, the problems with libthr aren't just limited to KDE= =20 (which really doesn't use threads all that much - Qt has limited support fo= r=20 threads, KDE has even less and actual multithreaded KDE programs are few an= d=20 far between) - running the base-system BIND as a local DNS cache for more=20 than an hour or so with a global mapping from libpthread to libthr active i= s=20 usually enough to expose the problem (i.e. name resolution will stop=20 working). =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 --nextPart6206001.iiAGvT54bV Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQBEw9EYXhc68WspdLARAtdoAJ9XaPWldgcf6PLcEBijXom1ftg1sACgp5KD uTRrUlTSPlNa6xYRM/nlo7s= =5VrI -----END PGP SIGNATURE----- --nextPart6206001.iiAGvT54bV-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 19:43:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1A7D16A4E5; Sun, 23 Jul 2006 19:43:41 +0000 (UTC) (envelope-from lofi@freebsd.org) Received: from mail-in-05.arcor-online.net (mail-in-05.arcor-online.net [151.189.21.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9307543D60; Sun, 23 Jul 2006 19:43:31 +0000 (GMT) (envelope-from lofi@freebsd.org) Received: from mail-in-06-z2.arcor-online.net (mail-in-06-z2.arcor-online.net [151.189.8.18]) by mail-in-05.arcor-online.net (Postfix) with ESMTP id 312E81849A5; Sun, 23 Jul 2006 21:43:30 +0200 (CEST) Received: from mail-in-03.arcor-online.net (mail-in-03.arcor-online.net [151.189.21.43]) by mail-in-06-z2.arcor-online.net (Postfix) with ESMTP id 1DB801A01D6; Sun, 23 Jul 2006 21:43:30 +0200 (CEST) Received: from lofi.dyndns.org (dslb-084-061-132-214.pools.arcor-ip.net [84.61.132.214]) by mail-in-03.arcor-online.net (Postfix) with ESMTP id 8A05220F07D; Sun, 23 Jul 2006 21:43:29 +0200 (CEST) Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) by lofi.dyndns.org (8.13.4/8.13.3) with ESMTP id k6NJhPWR055382 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 23 Jul 2006 21:43:25 +0200 (CEST) (envelope-from lofi@freebsd.org) Received: from kiste.my.domain (localhost [127.0.0.1]) by kiste.my.domain (8.13.6/8.13.4) with ESMTP id k6NJhO92036730; Sun, 23 Jul 2006 21:43:24 +0200 (CEST) (envelope-from lofi@freebsd.org) Received: from localhost (localhost [[UNIX: localhost]]) by kiste.my.domain (8.13.6/8.13.4/Submit) id k6NJhOpu036729; Sun, 23 Jul 2006 21:43:24 +0200 (CEST) (envelope-from lofi@freebsd.org) X-Authentication-Warning: kiste.my.domain: lofi set sender to lofi@freebsd.org using -f From: Michael Nottebrock To: Daniel Eischen Date: Sun, 23 Jul 2006 21:43:23 +0200 User-Agent: KMail/1.9.3 References: <200607221914.15826.lofi@freebsd.org> <200607222341.05180.lofi@freebsd.org> In-Reply-To: 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: freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org, kmacy@fsmware.com Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 19:43:41 -0000 --nextPart4651305.pPGyhYvrFj Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday, 23. July 2006 01:15, Daniel Eischen wrote: > On Sat, 22 Jul 2006, Michael Nottebrock wrote: > > On Saturday, 22. July 2006 21:20, Kip Macy wrote: > I think it is because WINE stomps on or TLS. Nothing we can > do about that except patch wine so it doesn't. Look at the > console messages for: > > Warning: pid XXX used static ldt allocation Yes, it does indeed trigger those - lots of them. =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 --nextPart4651305.pPGyhYvrFj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQBEw9FcXhc68WspdLARAq7FAJ9T6Bc+eHOn4yrXInWOCqEQnKbnsQCgq1P1 dF7zDKInR3HHwFUzITWQzzU= =DFI2 -----END PGP SIGNATURE----- --nextPart4651305.pPGyhYvrFj-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 21:00:18 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02EF616A4DA for ; Sun, 23 Jul 2006 21:00:17 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D02943D45 for ; Sun, 23 Jul 2006 21:00:15 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.7/8.13.7/Debian-1) with ESMTP id k6NKxwsB019797 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 23 Jul 2006 23:59:59 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.7/8.13.7) with ESMTP id k6NKxrrj003463; Sun, 23 Jul 2006 23:59:53 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.7/8.13.7/Submit) id k6NKxrV8003224; Sun, 23 Jul 2006 23:59:53 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 23 Jul 2006 23:59:53 +0300 From: Giorgos Keramidas To: Arseny Nasokin Message-ID: <20060723205953.GA74473@gothmog.pc> References: <44BFAE1D.30906@cwt.uz> <44C0D55B.60500@preved.cn> <20060722042347.GE53239@gothmog.pc> <20060723115425.GD12706@tarc.po.cs.msu.su> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060723115425.GD12706@tarc.po.cs.msu.su> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.762, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.64, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-hackers@freebsd.org Subject: Re: New Welcome message for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 21:00:18 -0000 On 2006-07-23 15:54, Arseny Nasokin wrote: >On Sat, Jul 22, 2006 at 07:23:47AM +0300, Giorgos Keramidas wrote: >>On 2006-07-21 17:23, Tarasov Alexey wrote: >>>Timur Yuldashev wrote: >>>> New motd-welcome message for FreeBSD. >>>> >>>> http://www.cwt.uz/motd >>>> >>>> best regards >>> >>> I like it! Very good. >> >> I don't. It is pretty "content free" when compared with our current >> default motd. >> >> The information in the current motd file is useful and provides hints >> towards stuff that may be interesting both to a new admin who just >> installed FreeBSD and a new user who just happened to log into a FreeBSD >> system. >> >> More importantly, the default /etc/motd is just a sample motd file, >> which you are free to edit locally :) > > I prefer put default motd to support(7) page. > and set this motd as default You are forgetting that someone who has just logged in may not know how to reach the support(7) manpage. The current motd can *POINT* him there: | Welcome to FreeBSD! | [...] | manual page. If you are not familiar with manual pages, type `man man'. How will the user know what to do if you go ahead and hide all the information currently visible by just logging in? From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 21:06:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE2B816A4DE for ; Sun, 23 Jul 2006 21:06:35 +0000 (UTC) (envelope-from tyler@bleepsoft.com) Received: from zeus.lunarpages.com (zeus.lunarpages.com [216.193.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5421043D4C for ; Sun, 23 Jul 2006 21:06:35 +0000 (GMT) (envelope-from tyler@bleepsoft.com) Received: from 24-240-211-104.dhcp.sprn.tx.charter.com ([24.240.211.104] helo=[192.168.250.100]) by zeus.lunarpages.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.52) id 1G4lAo-00075U-Ah for freebsd-hackers@freebsd.org; Sun, 23 Jul 2006 14:07:38 -0700 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <20060723.105549.2106235963.imp@bsdimp.com> References: <7ADD22A7-42DE-49D8-B411-DBA4CB2FA0CD@bleepsoft.com> <20060723100223.GB24435@gothmog.pc> <3320CEAC-8A5C-407D-9867-C2A22820A599@bleepsoft.com> <20060723.105549.2106235963.imp@bsdimp.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <00DBA5C9-C270-4E3A-AAD0-DD294B6A2E1C@bleepsoft.com> Content-Transfer-Encoding: 7bit From: "R. Tyler Ballance" Date: Sun, 23 Jul 2006 16:06:31 -0500 To: FreeBSD Hackers X-Pgp-Agent: GPGMail 1.1.2 (Tiger) X-Mailer: Apple Mail (2.752.2) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zeus.lunarpages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - bleepsoft.com X-Source: X-Source-Args: X-Source-Dir: Subject: Platform dependent locations (was Re: Building a sandboxed kernel) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 21:06:35 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Doesn't matter. > > I often do the following: > > setenv TARGET arm # this may be iguana for you > setenv TARGET_ARCH arm > setenv MAKEOBJDIRPREFIX /home/imp/obj > cd p4/imp_arm > make buildworld > make buildenv # from here on out is in a subshell > cd ../arm/src/sys/arm/conf > config KB920X > cd ../compile/KB920X > make depend && make > > You'll notice that I built in a tree that had all the arm patches > applied, and got a 'buildenv' there, but then build the kernel out of > a different tree. This is a -current p4 tree for both imp_arm and > arm, but I do this on a RELENG_6 system. I've done it in the recent > past on a 5.3 system too. > > TARGET is MACHINE and TARGET_ARCH is MACHINE_ARCH. MACHINE is the > kernel architecture, while MACHINE_ARCH is the CPU architecture > (TARGET_CPU is the specific CPU that we're optimizing for). Chances > are excellent we'll have TARGET_ARCH armel and armeb shortly. Right > now we have a hack ARM_BIG_ENDIAN used to control big vs little > endian, but since MACHINE_ARCH gets encoded into packages, I think we > need to move it there so binary packages do the right thing. But > that's a WIP in my tree right now... Thanks a lot! Of course, this leads to more questions on my part. Firstly, is there an already outlined guide for porting to new platforms? (Which is essentially what i'm doing for this project: http://opensource.bleepsoft.com/index.php/Main/L4BSD ) Or is this something I'll get to stumble over through trial and error with 'make buildworld; ? I'm finding all sorts of extra places where the FreeBSD build system is expecting platform specific files for example: ===> sys/boot/iguana (cleandir) cd: can't cd to /usr/home/tyler/perforce/projects/l4bsd/src/sys/boot/ iguana *** Error code 2 The problem I'm having is that I just want to build the kernel specific to the "new platform" but will I necessarily have to provide the proper constructs for the build system to cope with the new "platform" in src/sys/ ? Cheers, - -R. Tyler Ballance -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFEw+TZqO6nEJfroRsRAsWnAJ9xQlqy/DuBmR7Mhyvt4CBKQike4gCfdqzu 7OkESbLqY3i8VkzdleQ5tiU= =8zez -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 21:08:55 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F4DB16A4DD; Sun, 23 Jul 2006 21:08:55 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id F166543D46; Sun, 23 Jul 2006 21:08:54 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.7/8.13.7/NETPLEX) with ESMTP id k6NL8rM4016092; Sun, 23 Jul 2006 17:08:53 -0400 (EDT) Date: Sun, 23 Jul 2006 17:08:53 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Michael Nottebrock In-Reply-To: <200607232143.24374.lofi@freebsd.org> Message-ID: References: <200607221914.15826.lofi@freebsd.org> <200607222341.05180.lofi@freebsd.org> <200607232143.24374.lofi@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org, kmacy@fsmware.com Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 21:08:55 -0000 On Sun, 23 Jul 2006, Michael Nottebrock wrote: > On Sunday, 23. July 2006 01:15, Daniel Eischen wrote: >> On Sat, 22 Jul 2006, Michael Nottebrock wrote: >>> On Saturday, 22. July 2006 21:20, Kip Macy wrote: > >> I think it is because WINE stomps on or TLS. Nothing we can >> do about that except patch wine so it doesn't. Look at the >> console messages for: >> >> Warning: pid XXX used static ldt allocation > > Yes, it does indeed trigger those - lots of them. This is a problem with the way WINE is built or something. It is not a threads problem. Please close the PR. Thanks, -- DE From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 23 21:18:59 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1432D16A4DD for ; Sun, 23 Jul 2006 21:18:59 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 964F243D45 for ; Sun, 23 Jul 2006 21:18:58 +0000 (GMT) (envelope-from asmrookie@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so697660wxd for ; Sun, 23 Jul 2006 14:18:57 -0700 (PDT) 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:x-google-sender-auth; b=J2q9NImaoqUCurgSuQMfaDfV0tzIRuKAegzm40gMrDhhl7iTyCbwlHD0U7NXNUWbvDcB6gbTFQ1/Ti5OOlgqCnYY8HKSgtDfScnCFFkDgNlReKJbYoOfpiR4bLf4n+NYrv8+Ra9Pkl8a/N/xrjgzESrpTgxQhAfZ2Mc+rb1/X1k= Received: by 10.70.29.4 with SMTP id c4mr4001710wxc; Sun, 23 Jul 2006 14:18:57 -0700 (PDT) Received: by 10.70.24.4 with HTTP; Sun, 23 Jul 2006 14:18:56 -0700 (PDT) Message-ID: <3bbf2fe10607231418y58510d02ua208acbb44ea9f8c@mail.gmail.com> Date: Sun, 23 Jul 2006 23:18:56 +0200 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Divacky Roman" In-Reply-To: <20060723112332.GA83581@stud.fit.vutbr.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060723112332.GA83581@stud.fit.vutbr.cz> X-Google-Sender-Auth: a80f7c4efd237da0 Cc: freebsd-hackers@freebsd.org Subject: Re: i386 registers during a syscall X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jul 2006 21:18:59 -0000 2006/7/23, Divacky Roman : > hi, > > I need to get content of %esi register as it was during a syscall. Should I get > this info from td->td_pcb->pcb_esi or td->td_frame->tf_esi? > > Is it so that trapframe is "content of registers when entering a kernel" and > pcb is "when leaving a kernel" ? > > thnx for info pcb and trapframe are used for very different purposes. The trapframe is built into the exception handler and it is used as 'registers gate' from userspace/kernelspace. The pcb (process control block) is used to handle registers saving during a context switch, so it seems completely ortogonal to your problem. BTW, it's unclear to me what do you need... Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 00:26:26 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B72716A4DA for ; Mon, 24 Jul 2006 00:26:26 +0000 (UTC) (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 7AFB843D45 for ; Mon, 24 Jul 2006 00:26:25 +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.4/8.13.4) with ESMTP id k6O0P4aZ080029; Sun, 23 Jul 2006 18:25:04 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 23 Jul 2006 18:25:23 -0600 (MDT) Message-Id: <20060723.182523.324389931.imp@bsdimp.com> To: tyler@bleepsoft.com From: "M. Warner Losh" In-Reply-To: <00DBA5C9-C270-4E3A-AAD0-DD294B6A2E1C@bleepsoft.com> References: <3320CEAC-8A5C-407D-9867-C2A22820A599@bleepsoft.com> <20060723.105549.2106235963.imp@bsdimp.com> <00DBA5C9-C270-4E3A-AAD0-DD294B6A2E1C@bleepsoft.com> X-Mailer: Mew version 4.2 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]); Sun, 23 Jul 2006 18:25:04 -0600 (MDT) Cc: freebsd-hackers@freebsd.org Subject: Re: Platform dependent locations X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 00:26:26 -0000 In message: <00DBA5C9-C270-4E3A-AAD0-DD294B6A2E1C@bleepsoft.com> "R. Tyler Ballance" writes: : -----BEGIN PGP SIGNED MESSAGE----- : Hash: SHA1 : : > Doesn't matter. : > : > I often do the following: : > : > setenv TARGET arm # this may be iguana for you : > setenv TARGET_ARCH arm : > setenv MAKEOBJDIRPREFIX /home/imp/obj : > cd p4/imp_arm : > make buildworld : > make buildenv # from here on out is in a subshell : > cd ../arm/src/sys/arm/conf : > config KB920X : > cd ../compile/KB920X : > make depend && make : > : > You'll notice that I built in a tree that had all the arm patches : > applied, and got a 'buildenv' there, but then build the kernel out of : > a different tree. This is a -current p4 tree for both imp_arm and : > arm, but I do this on a RELENG_6 system. I've done it in the recent : > past on a 5.3 system too. : > : > TARGET is MACHINE and TARGET_ARCH is MACHINE_ARCH. MACHINE is the : > kernel architecture, while MACHINE_ARCH is the CPU architecture : > (TARGET_CPU is the specific CPU that we're optimizing for). Chances : > are excellent we'll have TARGET_ARCH armel and armeb shortly. Right : > now we have a hack ARM_BIG_ENDIAN used to control big vs little : > endian, but since MACHINE_ARCH gets encoded into packages, I think we : > need to move it there so binary packages do the right thing. But : > that's a WIP in my tree right now... : : Thanks a lot! Of course, this leads to more questions on my part. : Firstly, is there an already outlined guide for porting to new : platforms? Sadly, no. At the moment one needs to learn by doing.... : (Which is essentially what i'm doing for this project: : http://opensource.bleepsoft.com/index.php/Main/L4BSD ) : : Or is this something I'll get to stumble over through trial and error : with 'make buildworld; ? I'm finding all sorts of extra places where : the FreeBSD build system is expecting platform specific files for : example: : : ===> sys/boot/iguana (cleandir) : cd: can't cd to /usr/home/tyler/perforce/projects/l4bsd/src/sys/boot/ : iguana : *** Error code 2 : : The problem I'm having is that I just want to build the kernel : specific to the "new platform" but will I necessarily have to provide : the proper constructs for the build system to cope with the new : "platform" in src/sys/ ? Yes. However, there may be ways to improve the build infrastructure to make more things optional, like src/sys/boot/$MACHINE... Warner From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 02:07:30 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08F2D16A4DD for ; Mon, 24 Jul 2006 02:07:30 +0000 (UTC) (envelope-from shangjie.li@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62B5B43D4C for ; Mon, 24 Jul 2006 02:07:29 +0000 (GMT) (envelope-from shangjie.li@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so2150808uge for ; Sun, 23 Jul 2006 19:07:28 -0700 (PDT) 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=SFp0QpwBZKIZj2efqDipzBC8eOHoh3hRp/uHBP7EnnJkLJYnfGA0Jsf9BD+PgKN7a29V2vN3d/i4tQU3wUKV72SFOLmbWSEVAfq/ceVzu6LPp2bMSEYyvAfFVN2pF5NKJrFUAKNFHecU1UvYmCf9UM8vMBk7PdMYJ2ykGtcMcco= Received: by 10.78.170.17 with SMTP id s17mr1281979hue; Sun, 23 Jul 2006 19:07:27 -0700 (PDT) Received: by 10.78.127.20 with HTTP; Sun, 23 Jul 2006 19:07:27 -0700 (PDT) Message-ID: Date: Mon, 24 Jul 2006 10:07:27 +0800 From: "=?GB2312?B?wO7J0L3c?=" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: A question about ipcperm() call? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 02:07:30 -0000 The code for ipcperm() call : 78 ipcperm(td, perm, mode) 79 struct thread *td; 80 struct ipc_perm *perm; 81 int mode; 82 { 83 struct ucred *cred = td->td_ucred; 84 int error; 85 86 if (cred->cr_uid != perm->cuid && cred->cr_uid != perm->uid) { 87 /* 88 * For a non-create/owner, we require privilege to 89 * modify the object protections. Note: some other 90 * implementations permit IPC_M to be delegated to 91 * unprivileged non-creator/owner uids/gids. 92 */ 93 if (mode & IPC_M) { 94 error = suser(td); 95 if (error) 96 return (error); 97 } 98 /* 99 * Try to match against creator/owner group; if not, fall 100 * back on other. 101 */ 102 mode >>= 3; 103 if (!groupmember(perm->gid, cred) && 104 !groupmember(perm->cgid, cred)) 105 mode >>= 3; 106 } else { 107 /* 108 * Always permit the creator/owner to update the object 109 * protections regardless of whether the object mode 110 * permits it. 111 */ 112 if (mode & IPC_M) 113 return (0); 114 } 115 116 if ((mode & perm->mode) != mode) { 117 if (suser(td) != 0) 118 return (EACCES); 119 } 120 return (0); 121 } why not directly return the error in line 94? |Institute of Software, Chinese Academy of Sciences, |P.O. Box 8718, Beijing 100080, CHINA |Phone: (8610)62561197/62635158-1008(O), 82680528(H) |Email: shangjie02@ios.cn >---------------------------------------------------< From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 04:24:41 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12E0216A4DA for ; Mon, 24 Jul 2006 04:24:41 +0000 (UTC) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id D45D643D46 for ; Mon, 24 Jul 2006 04:24:40 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [192.168.2.2]) ([10.251.60.31]) by a50.ironport.com with ESMTP; 23 Jul 2006 21:24:40 -0700 Message-ID: <44C44B87.8070100@elischer.org> Date: Sun, 23 Jul 2006 21:24:39 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Divacky Roman References: <20060723112332.GA83581@stud.fit.vutbr.cz> In-Reply-To: <20060723112332.GA83581@stud.fit.vutbr.cz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: i386 registers during a syscall X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 04:24:41 -0000 Divacky Roman wrote: >hi, > >I need to get content of %esi register as it was during a syscall. Should I get >this info from td->td_pcb->pcb_esi or td->td_frame->tf_esi? > >Is it so that trapframe is "content of registers when entering a kernel" and >pcb is "when leaving a kernel" ? > > pcb is when the process is sleeping or otherwise suspended. frame is when enterring the kernel, and reloaded when leaving the kernel >thnx for info > >roman > > >---------------------- >www.liberalnistrana.cz >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 05:06:38 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED57316A4E0 for ; Mon, 24 Jul 2006 05:06:38 +0000 (UTC) (envelope-from sthalik@tehran.lain.pl) Received: from mail.in5.pl (rollercoaster.insane.pl [213.251.173.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A3DC43D49 for ; Mon, 24 Jul 2006 05:06:37 +0000 (GMT) (envelope-from sthalik@tehran.lain.pl) Received: from tehran.lain.pl ([85.221.230.102] helo=tehran.local) by mail.in5.pl with esmtpsa (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (envelope-from ) id 1G4seK-000747-Ip for freebsd-hackers@freebsd.org; Mon, 24 Jul 2006 07:06:36 +0200 Received: from sthalik by tehran.local with local (Exim 4.62) (envelope-from ) id 1G4sdt-0004Q2-RZ for freebsd-hackers@freebsd.org; Mon, 24 Jul 2006 07:06:09 +0200 Date: Mon, 24 Jul 2006 07:06:09 +0200 From: Stanislaw Halik To: freebsd-hackers@freebsd.org Message-ID: <20060724050609.GA16975@localhost.localdomain> Mail-Followup-To: freebsd-hackers@freebsd.org References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://tehran.lain.pl/public.key User-Agent: Mutt/1.5.12-2006-07-14 X-User: sthalik Subject: Re: A question about ipcperm() call? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 05:06:39 -0000 --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 24, 2006, ?????? wrote: > 93 if (mode & IPC_M) { > 94 error =3D suser(td); > 95 if (error) > 96 return (error); > why not directly return the error in line 94? Assignment could return boolean false as well. --=20 Ecchi na no wa ikenai to omoimasu. --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFExFVBadU+vjT62TERAhKAAJ9f4o86nB04be/lYsnNhcInwEOwrwCghEKC pOMNqu+5OlNzwCzA8qO9efc= =QEQO -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 05:24:17 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E728416A4DD for ; Mon, 24 Jul 2006 05:24:17 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 789C443D45 for ; Mon, 24 Jul 2006 05:24:17 +0000 (GMT) (envelope-from delphij@gmail.com) Received: by py-out-1112.google.com with SMTP id b36so1881866pyb for ; Sun, 23 Jul 2006 22:23:44 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BO7gkGg3ClV0/4XPJybud/UeuWOr8re/zKeMBC40DI3iS7NctWPNZrxahxKDOLSU6+BzppAP/yiVUvM7C+5tAdRfh2WjtjnNUUyEjLnj0wPstPCDQVU+CeSDHtV/jzmtP+gh0JqesxdSL+QUYfLTJQN/ZGbKP14+MfEq0ZcCnD4= Received: by 10.35.37.18 with SMTP id p18mr6879117pyj; Sun, 23 Jul 2006 22:21:55 -0700 (PDT) Received: by 10.35.125.13 with HTTP; Sun, 23 Jul 2006 22:21:55 -0700 (PDT) Message-ID: Date: Mon, 24 Jul 2006 13:21:55 +0800 From: "Xin LI" To: "=?ISO-2022-JP?B?GyRCTXs+MFs/GyhC?=" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-hackers@freebsd.org, rwatson@freebsd.org Subject: Re: A question about ipcperm() call? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: delphij@delphij.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 05:24:18 -0000 On 7/24/06, $BM{>0[?(B wrote: > The code for ipcperm() call : > 78 ipcperm(td, perm, mode) > 79 struct thread *td; > 80 struct ipc_perm *perm; > 81 int mode; > 82 { > 83 struct ucred *cred = td->td_ucred; > 84 int error; > 85 > 86 if (cred->cr_uid != perm->cuid && cred->cr_uid != perm->uid) { > 87 /* > 88 * For a non-create/owner, we require privilege to > 89 * modify the object protections. Note: some other > 90 * implementations permit IPC_M to be delegated to > 91 * unprivileged non-creator/owner uids/gids. > 92 */ > 93 if (mode & IPC_M) { > 94 error = suser(td); > 95 if (error) > 96 return (error); > 97 } > 98 /* > 99 * Try to match against creator/owner group; if not, fall > 100 * back on other. > 101 */ > 102 mode >>= 3; > 103 if (!groupmember(perm->gid, cred) && > 104 !groupmember(perm->cgid, cred)) > 105 mode >>= 3; > 106 } else { > 107 /* > 108 * Always permit the creator/owner to update the object > 109 * protections regardless of whether the object mode > 110 * permits it. > 111 */ > 112 if (mode & IPC_M) > 113 return (0); > 114 } > 115 > 116 if ((mode & perm->mode) != mode) { > 117 if (suser(td) != 0) > 118 return (EACCES); > 119 } > 120 return (0); > 121 } > > why not directly return the error in line 94? I think it makes sense to remove the assignment and the 'error' variable. Let's see Robert's opinion. Cheers, -- Xin LI http://www.delphij.net From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 08:04:30 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0786316A4E1; Mon, 24 Jul 2006 08:04:30 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1CD943D5A; Mon, 24 Jul 2006 08:04:16 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.7/8.13.7) with ESMTP id k6O84Apx039886 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 24 Jul 2006 10:04:10 +0200 (CEST) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.7/8.13.3/Submit) id k6O84Acn039884; Mon, 24 Jul 2006 10:04:10 +0200 (CEST) Date: Mon, 24 Jul 2006 10:04:10 +0200 From: Divacky Roman To: Attilio Rao Message-ID: <20060724080410.GA39744@stud.fit.vutbr.cz> References: <20060723112332.GA83581@stud.fit.vutbr.cz> <3bbf2fe10607231418y58510d02ua208acbb44ea9f8c@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3bbf2fe10607231418y58510d02ua208acbb44ea9f8c@mail.gmail.com> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.54 on 147.229.10.14 Cc: freebsd-hackers@freebsd.org Subject: Re: i386 registers during a syscall X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 08:04:30 -0000 On Sun, Jul 23, 2006 at 11:18:56PM +0200, Attilio Rao wrote: > 2006/7/23, Divacky Roman : > >hi, > > > >I need to get content of %esi register as it was during a syscall. Should > >I get > >this info from td->td_pcb->pcb_esi or td->td_frame->tf_esi? > > > >Is it so that trapframe is "content of registers when entering a kernel" > >and > >pcb is "when leaving a kernel" ? > > > >thnx for info > > pcb and trapframe are used for very different purposes. > > The trapframe is built into the exception handler and it is used as > 'registers gate' from userspace/kernelspace. > > The pcb (process control block) is used to handle registers saving > during a context switch, so it seems completely ortogonal to your > problem. > > BTW, it's unclear to me what do you need... mov $123, %esi int $0x80 ; syscall I need the value of %esi (ie. 123) is td->td_frame->tf_esi what I need? thnx roman From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 09:07:20 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A84E016A4DD; Mon, 24 Jul 2006 09:07:20 +0000 (UTC) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58C9443D49; Mon, 24 Jul 2006 09:07:20 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [192.168.2.2]) ([10.251.60.31]) by a50.ironport.com with ESMTP; 24 Jul 2006 02:07:19 -0700 Message-ID: <44C48DC7.6050305@elischer.org> Date: Mon, 24 Jul 2006 02:07:19 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Divacky Roman References: <20060723112332.GA83581@stud.fit.vutbr.cz> <3bbf2fe10607231418y58510d02ua208acbb44ea9f8c@mail.gmail.com> <20060724080410.GA39744@stud.fit.vutbr.cz> In-Reply-To: <20060724080410.GA39744@stud.fit.vutbr.cz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Attilio Rao , freebsd-hackers@freebsd.org Subject: Re: i386 registers during a syscall X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 09:07:20 -0000 Divacky Roman wrote: >On Sun, Jul 23, 2006 at 11:18:56PM +0200, Attilio Rao wrote: > > >>2006/7/23, Divacky Roman : >> >> >>>hi, >>> >>>I need to get content of %esi register as it was during a syscall. Should >>>I get >>>this info from td->td_pcb->pcb_esi or td->td_frame->tf_esi? >>> >>>Is it so that trapframe is "content of registers when entering a kernel" >>>and >>>pcb is "when leaving a kernel" ? >>> >>>thnx for info >>> >>> >>pcb and trapframe are used for very different purposes. >> >>The trapframe is built into the exception handler and it is used as >>'registers gate' from userspace/kernelspace. >> >>The pcb (process control block) is used to handle registers saving >>during a context switch, so it seems completely ortogonal to your >>problem. >> >>BTW, it's unclear to me what do you need... >> >> > >mov $123, %esi >int $0x80 ; syscall > >I need the value of %esi (ie. 123) > >is td->td_frame->tf_esi what I need? > > yes >thnx > >roman >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 10:38:44 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DB2F16A4E0; Mon, 24 Jul 2006 10:38:44 +0000 (UTC) (envelope-from tyler@bleepsoft.com) Received: from zeus.lunarpages.com (zeus.lunarpages.com [216.193.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25ECF43D49; Mon, 24 Jul 2006 10:38:44 +0000 (GMT) (envelope-from tyler@bleepsoft.com) Received: from 24-240-211-104.dhcp.sprn.tx.charter.com ([24.240.211.104] helo=[192.168.250.100]) by zeus.lunarpages.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.52) id 1G4xql-0000pT-TQ; Mon, 24 Jul 2006 03:39:48 -0700 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: "R. Tyler Ballance" Date: Mon, 24 Jul 2006 05:38:39 -0500 To: freebsd-current@freebsd.org X-Pgp-Agent: GPGMail 1.1.2 (Tiger) X-Mailer: Apple Mail (2.752.2) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zeus.lunarpages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - bleepsoft.com X-Source: X-Source-Args: X-Source-Dir: Cc: FreeBSD Hackers Subject: Re: Failing `make buildworld` with today's source X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 10:38:44 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 freebsd-current: I figured out why this was failing on my machine, I did a clean `make buildworld` which succeeded without a hitch freebsd-hackers: After taking Warner's advice, I am building world with a different target arch, but I cannot track down exactly where this error is occurring, I'm including a new version of the error transcript in case it's helpful at all. Any porters seen this before, kmacy? arm guys? anybody? :P Cheers, - -R. Tyler Ballance =================== cc -O2 -fno-strict-aliasing -pipe -I. -DIN_GCC -DHAVE_CONFIG_H - DPREFIX=\"/usr\" -DCROSS_COMPILE -I/usr/home/tyler/builds/obj/iguana/ usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/cc_tools/../ cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/ gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/usr/home/tyler/ perforce/projects/l4bsd/src/gnu/usr.bin/cc/cc_tools/../../../../ contrib/gcc/config -DGENERATOR_FILE -I/home/tyler/builds/obj/iguana/ usr/home/tyler/perforce/projects/l4bsd/src/tmp/legacy/usr/include -c / usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/gengenrtl.c cc -O2 -fno-strict-aliasing -pipe -I. -DIN_GCC -DHAVE_CONFIG_H - DPREFIX=\"/usr\" -DCROSS_COMPILE -I/usr/home/tyler/builds/obj/iguana/ usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/cc_tools/../ cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/ gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/usr/home/tyler/ perforce/projects/l4bsd/src/gnu/usr.bin/cc/cc_tools/../../../../ contrib/gcc/config -DGENERATOR_FILE -I/home/tyler/builds/obj/iguana/ usr/home/tyler/perforce/projects/l4bsd/src/tmp/legacy/usr/include -L/ home/tyler/builds/obj/iguana/usr/home/tyler/perforce/projects/l4bsd/ src/tmp/legacy/usr/lib -o gengenrtl gengenrtl.o errors.o libiberty.a ./gengenrtl > genrtl.c ./gengenrtl -h > genrtl.h cc -O2 -fno-strict-aliasing -pipe -I. -DIN_GCC -DHAVE_CONFIG_H - DPREFIX=\"/usr\" -DCROSS_COMPILE -I/usr/home/tyler/builds/obj/iguana/ usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/cc_tools/../ cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/ gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/usr/home/tyler/ perforce/projects/l4bsd/src/gnu/usr.bin/cc/cc_tools/../../../../ contrib/gcc/config -DGENERATOR_FILE -I/home/tyler/builds/obj/iguana/ usr/home/tyler/perforce/projects/l4bsd/src/tmp/legacy/usr/include -c / usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/genattr.c In file included from /usr/home/tyler/perforce/projects/l4bsd/src/gnu/ usr.bin/cc/cc_tools/../../../../contrib/gcc/genattr.c:27: ./tm.h:4:15: /.h: No such file or directory ./tm.h:10:22: /freebsd.h: No such file or directory In file included from /usr/home/tyler/perforce/projects/l4bsd/src/gnu/ usr.bin/cc/cc_tools/../../../../contrib/gcc/genattr.c:28: /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/rtl.h:2189: warning: parameter has incomplete type /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/rtl.h:2189: warning: parameter has incomplete type /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/rtl.h:2190: warning: parameter has incomplete type /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/rtl.h:2190: warning: parameter has incomplete type /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools/../../../../contrib/gcc/rtl.h:2209: warning: parameter has incomplete type *** Error code 1 Stop in /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ cc_tools. *** Error code 1 Stop in /usr/home/tyler/perforce/projects/l4bsd/src. *** Error code 1 Stop in /usr/home/tyler/perforce/projects/l4bsd/src. *** Error code 1 Stop in /usr/home/tyler/perforce/projects/l4bsd/src. % =================== On Jul 24, 2006, at 12:31 AM, R. Tyler Ballance wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I recently integrated today's (ok, sunday's) source code into my > branch in perforce, and I'm getting these build errors: > > Anybody seen anything similar? > > ./gengenrtl > genrtl.c > ./gengenrtl -h > genrtl.h > cc -O2 -fno-strict-aliasing -pipe -I. -DIN_GCC -DHAVE_CONFIG_H - > DPREFIX=\"/usr\" -DCROSS_COMPILE -I/usr/home/tyler/builds/obj/ > iguana/usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ > cc_tools/../cc_tools -I/usr/home/tyler/perforce/projects/l4bsd/src/ > gnu/usr.bin/cc/cc_tools/../cc_tools -I/usr/home/tyler/perforce/ > projects/l4bsd/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc - > I/usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ > cc_tools/../../../../contrib/gcc/config -DGENERATOR_FILE -I/home/ > tyler/builds/obj/iguana/usr/home/tyler/perforce/projects/l4bsd/src/ > tmp/legacy/usr/include -c /usr/home/tyler/perforce/projects/l4bsd/ > src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/genattr.c > In file included from /usr/home/tyler/perforce/projects/l4bsd/src/ > gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/genattr.c:27: > ./tm.h:4:15: /.h: No such file or directory > ./tm.h:10:22: /freebsd.h: No such file or directory > In file included from /usr/home/tyler/perforce/projects/l4bsd/src/ > gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/genattr.c:28: > /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ > cc_tools/../../../../contrib/gcc/rtl.h:2189: warning: parameter has > incomplete type > /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ > cc_tools/../../../../contrib/gcc/rtl.h:2189: warning: parameter has > incomplete type > /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ > cc_tools/../../../../contrib/gcc/rtl.h:2190: warning: parameter has > incomplete type > /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ > cc_tools/../../../../contrib/gcc/rtl.h:2190: warning: parameter has > incomplete type > /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ > cc_tools/../../../../contrib/gcc/rtl.h:2209: warning: parameter has > incomplete type > *** Error code 1 > > Stop in /usr/home/tyler/perforce/projects/l4bsd/src/gnu/usr.bin/cc/ > cc_tools. > *** Error code 1 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.3 (Darwin) > > iD8DBQFExFsbqO6nEJfroRsRApY8AJ9vbI88wohJdzjb/W29kxFYwW6e6gCfa94r > C+A4qVhDRd2r7rI10nDGsoc= > =4Maf > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current- > unsubscribe@freebsd.org" > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFExKMxqO6nEJfroRsRAlVLAJ9lCVe6F55hldMVrZGp3mn4G6oKlwCeLqPn iIp1appbD1RFA2KB/17js6Q= =IsFh -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 11:47:47 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C319616A4DE; Mon, 24 Jul 2006 11:47:47 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25E8043D77; Mon, 24 Jul 2006 11:47:46 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp128-162.lns2.adl2.internode.on.net [59.167.128.162]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k6OBliYV055149 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Jul 2006 21:17:44 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "Greg 'groggy' Lehey" /T Date: Mon, 24 Jul 2006 21:17:47 +0930 User-Agent: KMail/1.9.3 References: <18075337.124391153395068232.JavaMail.root@vms068.mailsrvcs.net> <200607212338.01728.doconnor@gsoft.com.au> <20060722230330.GB16230@wantadilla.lemis.com> In-Reply-To: <20060722230330.GB16230@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3617725.AKUoabKzoc"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607242117.49685.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: freebsd-hackers@freebsd.org, babkin@users.sourceforge.net, FreeBSD Hackers , Robert Watson Subject: Re: Programs not accepting input? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 11:47:47 -0000 --nextPart3617725.AKUoabKzoc Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 23 July 2006 08:33, Greg 'groggy' Lehey wrote: > > One thing that IS a KDE problem is having it manage 2 distinct desktops > > (ie :0.0 [laptop LCD] and :0.1 [TV out]) - it occasionally decides to > > give the other display focus after a dialog has been closed.. > > Are you sure? This sounds like the issue that Peter and I have been > discussing in the context of fvwm. It seems to only happen when a dialog box closes. I can tell focus moves to the other display because I tested it when I had = a=20 TV connected by pressing ctrl-esc (which pops up the 'K' menu) and the menu= =20 showed up on the TV not the LCD (where focus should have been) > Which reminds me of the reason for click focus in the first place: on > the machines of 15 years ago, focus following the cursor could place > an unacceptable load on the X server. Maybe what we're seeing here is > related. Hmm could be.. Bit hard to tell for sure where the problem lies with so man= y=20 interacting pieces :( =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 --nextPart3617725.AKUoabKzoc Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBExLNl5ZPcIHs/zowRAp8+AJ9tyDaInEmS6hacOO8mGWIvrbtsoACghsQ6 QVWZ3Rm7M30oMuqBIDt5jME= =X2TW -----END PGP SIGNATURE----- --nextPart3617725.AKUoabKzoc-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 11:47:47 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C319616A4DE; Mon, 24 Jul 2006 11:47:47 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25E8043D77; Mon, 24 Jul 2006 11:47:46 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp128-162.lns2.adl2.internode.on.net [59.167.128.162]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k6OBliYV055149 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Jul 2006 21:17:44 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "Greg 'groggy' Lehey" /T Date: Mon, 24 Jul 2006 21:17:47 +0930 User-Agent: KMail/1.9.3 References: <18075337.124391153395068232.JavaMail.root@vms068.mailsrvcs.net> <200607212338.01728.doconnor@gsoft.com.au> <20060722230330.GB16230@wantadilla.lemis.com> In-Reply-To: <20060722230330.GB16230@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3617725.AKUoabKzoc"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607242117.49685.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: freebsd-hackers@freebsd.org, babkin@users.sourceforge.net, FreeBSD Hackers , Robert Watson Subject: Re: Programs not accepting input? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 11:47:47 -0000 --nextPart3617725.AKUoabKzoc Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 23 July 2006 08:33, Greg 'groggy' Lehey wrote: > > One thing that IS a KDE problem is having it manage 2 distinct desktops > > (ie :0.0 [laptop LCD] and :0.1 [TV out]) - it occasionally decides to > > give the other display focus after a dialog has been closed.. > > Are you sure? This sounds like the issue that Peter and I have been > discussing in the context of fvwm. It seems to only happen when a dialog box closes. I can tell focus moves to the other display because I tested it when I had = a=20 TV connected by pressing ctrl-esc (which pops up the 'K' menu) and the menu= =20 showed up on the TV not the LCD (where focus should have been) > Which reminds me of the reason for click focus in the first place: on > the machines of 15 years ago, focus following the cursor could place > an unacceptable load on the X server. Maybe what we're seeing here is > related. Hmm could be.. Bit hard to tell for sure where the problem lies with so man= y=20 interacting pieces :( =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 --nextPart3617725.AKUoabKzoc Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBExLNl5ZPcIHs/zowRAp8+AJ9tyDaInEmS6hacOO8mGWIvrbtsoACghsQ6 QVWZ3Rm7M30oMuqBIDt5jME= =X2TW -----END PGP SIGNATURE----- --nextPart3617725.AKUoabKzoc-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 11:57:13 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D67E16A4E1 for ; Mon, 24 Jul 2006 11:57:13 +0000 (UTC) (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 5C1EA43D70 for ; Mon, 24 Jul 2006 11:57:12 +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 4049E46CBD; Mon, 24 Jul 2006 07:57:11 -0400 (EDT) Date: Mon, 24 Jul 2006 12:57:11 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: delphij@delphij.net In-Reply-To: Message-ID: <20060724125154.T44945@fledge.watson.org> References: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1014467017-1153742231=:44945" Cc: freebsd-hackers@freebsd.org, =?ISO-2022-JP?B?GyRCTXs+MFs/GyhC?= Subject: Re: A question about ipcperm() call? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 11:57:13 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1014467017-1153742231=:44945 Content-Type: TEXT/PLAIN; charset=ISO-2022-JP; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Mon, 24 Jul 2006, Xin LI wrote: > On 7/24/06, =CD=FB=BE=B0=DB=BF wrote: >> The code for ipcperm() call : >> 78 ipcperm(td, perm, mode) >> 79 struct thread *td; >> 80 struct ipc_perm *perm; >> 81 int mode; >> 82 { >> 83 struct ucred *cred =3D td->td_ucred; >> 84 int error; >> 85 >> 86 if (cred->cr_uid !=3D perm->cuid && cred->cr_uid !=3D perm->= uid) { >> 87 /* >> 88 * For a non-create/owner, we require privilege to >> 89 * modify the object protections. Note: some other >> 90 * implementations permit IPC_M to be delegated to >> 91 * unprivileged non-creator/owner uids/gids. >> 92 */ >> 93 if (mode & IPC_M) { >> 94 error =3D suser(td); >> 95 if (error) >> 96 return (error); >> 97 } >> 98 /* >> 99 * Try to match against creator/owner group; if not,= =20 >> fall >> 100 * back on other. >> 101 */ >> 102 mode >>=3D 3; >> 103 if (!groupmember(perm->gid, cred) && >> 104 !groupmember(perm->cgid, cred)) >> 105 mode >>=3D 3; >> 106 } else { >> 107 /* >> 108 * Always permit the creator/owner to update the obj= ect >> 109 * protections regardless of whether the object mode >> 110 * permits it. >> 111 */ >> 112 if (mode & IPC_M) >> 113 return (0); >> 114 } >> 115 >> 116 if ((mode & perm->mode) !=3D mode) { >> 117 if (suser(td) !=3D 0) >> 118 return (EACCES); >> 119 } >> 120 return (0); >> 121 } >>=20 >> why not directly return the error in line 94? > > I think it makes sense to remove the assignment and the 'error' variable.= =20 > Let's see Robert's opinion. In almost all cases, we return the error returned by suser() in order to=20 encapsulate the notion that the "lack of privilege" error (EPERM) in suser(= )=20 rather than scattered around. I'm not sure it makes much difference, since= =20 functionally you will get back EPERM either way, but generally the conventi= on=20 has been for pieces of access control logic to return an error reflecting t= he=20 nature of the success or failure (0, EPERM, EACCES, ESRCH, etc), and for th= e=20 calling code not to perform any translation of the error unless strictly=20 necessary. For example, in procfs we do translate ESRCH into ENOENT, but o= nly=20 because ESRCH isn't a standard file system error, and ENOENT is the logical= =20 equivilent. In our TrustedBSD SEBSD branch, the MAC Framework permits=20 policies to modify the notion of privilege, so in principle they can return= =20 different errors from the privilege check, although I am not entirely sure= =20 they shold. I am not sure that I agree that we should replace the current= =20 error assignment, as it will encode EPERM as the privilege error in ipcperm= (),=20 and prevent suser() from returning a different error. Robert N M Watson Computer Laboratory University of Cambridge --0-1014467017-1153742231=:44945-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 12:04:47 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E151516A4E0 for ; Mon, 24 Jul 2006 12:04:47 +0000 (UTC) (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 BA35B43D6D for ; Mon, 24 Jul 2006 12:04:45 +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 67D4446CD8; Mon, 24 Jul 2006 08:04:45 -0400 (EDT) Date: Mon, 24 Jul 2006 13:04:45 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: delphij@delphij.net In-Reply-To: Message-ID: <20060724125831.S44945@fledge.watson.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, =?ISO-2022-JP?B?GyRCTXs+MFs/GyhC?= Subject: Re: A question about ipcperm() call? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 12:04:48 -0000 On Mon, 24 Jul 2006, Xin LI wrote: >> why not directly return the error in line 94? > > I think it makes sense to remove the assignment and the 'error' variable. > Let's see Robert's opinion. I'm sorry, my previous answer was based on a mis-reading of the question -- you're not suggesting returning EPERM directly, rather, avoiding the "fall out" to the return (0). ipcperm() is not very well structured, in part because the access control logic itself isn't very well structured. Normally I try to structure access control functions so that we check all the possible reasons not to grant a request, and return (0) only if they all pass, returning various errors along the way. This works well in many cases because we often have lots of reasons not to allow something, and few reasons to allow it. For example, the p_checkfoo() inter-process access control checks. However, when discretionary access control is present, things get a little more complex, since the first task is to identify which set of rules are required, then to compose the mandatory rules, matching discretionary rules, and privilege. This is true in vaccess() and vaccess_acl_posix1e(), and should be true in ipcperm() also. I would be interested in seeing reasonable restructurings of this code, perhaps as a set of blocks that looks at each requested operation or set of related operations and authorizes them sequentially. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 12:55:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BA0416A4DA; Mon, 24 Jul 2006 12:55:49 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7760F43D45; Mon, 24 Jul 2006 12:55:48 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5FF9C.dip.t-dialin.net [84.165.255.156]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.6/8.13.6) with ESMTP id k6OCi0s0095717; Mon, 24 Jul 2006 14:44:00 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.4/8.13.3) with ESMTP id k6OCtoIX003563; Mon, 24 Jul 2006 14:55:50 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Mon, 24 Jul 2006 14:55:50 +0200 Message-ID: <20060724145550.omhwkk0w00cgws44@netchild.homeip.net> X-Priority: 3 (Normal) Date: Mon, 24 Jul 2006 14:55:50 +0200 From: Alexander Leidinger To: Robert Watson References: <20060724125831.S44945@fledge.watson.org> In-Reply-To: <20060724125831.S44945@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.1) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new X-Mailman-Approved-At: Mon, 24 Jul 2006 13:18:41 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: A question about ipcperm() call? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 12:55:49 -0000 Quoting Robert Watson (from Mon, 24 Jul 2006 13:04:45 +0100 (BST)): > also. I would be interested in seeing reasonable restructurings of > this code, perhaps as a set of blocks that looks at each requested > operation or set of related operations and authorizes them sequentially. Feel free to send a suitable plain text version for our ideas list page (or commit an entry yourself)... Bye, Alexander. -- The worst is enemy of the bad. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 15:06:21 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E1DCC16A4DD; Mon, 24 Jul 2006 15:06:20 +0000 (UTC) (envelope-from tijl@ulyssis.org) Received: from outmx013.isp.belgacom.be (outmx013.isp.belgacom.be [195.238.5.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F5EC43D49; Mon, 24 Jul 2006 15:06:17 +0000 (GMT) (envelope-from tijl@ulyssis.org) Received: from outmx013.isp.belgacom.be (localhost [127.0.0.1]) by outmx013.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6OF6EM9027430; Mon, 24 Jul 2006 17:06:15 +0200 (envelope-from ) Received: from kalimero.kotnet.org (88.193-245-81.adsl-dyn.isp.belgacom.be [81.245.193.88]) by outmx013.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6OF6CZG027402; Mon, 24 Jul 2006 17:06:12 +0200 (envelope-from ) Received: from kalimero.kotnet.org (kalimero.kotnet.org [127.0.0.1]) by kalimero.kotnet.org (8.13.6/8.13.6) with ESMTP id k6OF684T047356; Mon, 24 Jul 2006 17:06:09 +0200 (CEST) (envelope-from tijl@ulyssis.org) From: Tijl Coosemans To: freebsd-hackers@freebsd.org Date: Mon, 24 Jul 2006 17:06:01 +0200 User-Agent: KMail/1.9.3 References: <200607221914.15826.lofi@freebsd.org> In-Reply-To: <200607221914.15826.lofi@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5011153.KMGMiH3a1f"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607241706.08396.tijl@ulyssis.org> Cc: freebsd-emulation@freebsd.org, Michael Nottebrock Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 15:06:21 -0000 --nextPart5011153.KMGMiH3a1f Content-Type: multipart/mixed; boundary="Boundary-01=_aHOxEESzu2uIOd8" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_aHOxEESzu2uIOd8 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 22 July 2006 19:14, Michael Nottebrock wrote: > WINE does have certain requirements regarding memory allocation. In > particular it (or Windows, rather) really wants a few memory ranges > for itself: > > (from wine-0.9.17/loader/preloader.c): > > * 0x00000000 - 0x00110000 the DOS area > * 0x80000000 - 0x81000000 the shared heap > * ??? - ??? the PE binary load address (usually > starting at 0x00400000) > > The first two are particularly important for WINE running in win98 > (or earlier) emulation mode, which is currently completely broken on > FreeBSD, since those two memory ranges tend to be unavailable. The reason for the second range is that wine is located way at the end=20 of the 2G range (0x7bf00000). FreeBSD's mmap preserves heap space after=20 that (for brk(2) style allocations). This is about 512Mb by default so=20 everything in 0x7bf00000-0x9bf00000 is unavailable (unless MAP_FIXED is=20 used of course). The DOS area should be available but can't be allocated by wine because=20 of a FreeBSD specific quirk in its code to work arround another mmap=20 related problem. Both problems can be solved by locating wine at say 0x20000000 instead=20 of 0x7bf00000. That leaves plenty of space for the windows executable=20 and allows us to remove mmap related freebsd quirks from wine's code. I've attached two patches that accomplish this, but this seems to=20 trigger other problems, so use at your own risk. If you want to try=20 them, place them in the port's files/ directory and add a line=20 containing "USE_AUTOTOOLS=3D autoconf:259" to the Makefile. This seems to=20 break wine+libpthread, so I've also changed the port to use libthr=20 instead. =46or the libpthread experts, I haven't investigated that much further=20 yet, but libpthread seems to fail in create_stack() from=20 _pthread_create() from _thr_start_sig_daemon(). > The preloader bit from which this is quoted is WINE's "own shared > object loader that reserves memory that is important to Wine, and > then loads the main binary and its ELF interpreter", and obviously > does not work right on FreeBSD. I'm not sure whether it can be made > to or not, perhaps somebody familiar with both our VM and runtime > linker could take a look. The preloader isn't used on FreeBSD. You either run wine-kthread or=20 wine(-pthread) directly. The reason for the preloader in linux is=20 mainly exec-shield which makes the mapping of DSOs unpredictable. > http://bugs.winehq.org/show_bug.cgi?id=3D5732 Do the above mentioned patches solve your second issue here (PE exec=20 location)? > The other big issue with WINE on FreeBSD seems to be our threading > support. WINE quite reliably manages to confuse libpthread, see > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dthreads/100701. On SMP > machines, I've even been able to trigger kernel panics with WINE (in > win2k+ emulation mode) by merely hitting the close button on a > windows application (and WINE subsequently shutting down): >=20 http://lists.freebsd.org/pipermail/freebsd-stable/2006-June/026219.html.=20 > > WINE's threads interface can be found in loader/pthread.c and > loader/kthread.c - again, it would be great, if someone to whom that > sort of code means more than just random gibberish could take a look. Wine does some freaky stack manipulations. I think that may interfere=20 with the way our threading libs handle the stack (allocation etc.). But=20 I am just guessing here really. --Boundary-01=_aHOxEESzu2uIOd8 Content-Type: text/plain; charset="iso-8859-15"; name="patch-configure.ac" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="patch-configure.ac" =2D-- configure.ac.orig Mon Jul 10 18:01:07 2006 +++ configure.ac Mon Jul 24 15:42:41 2006 @@ -149,7 +149,7 @@ dnl Check for -lresolv for Mac OS X/Darwin AC_CHECK_LIB(resolv,res_9_init) dnl Check for -lpthread =2DAC_CHECK_LIB(pthread,pthread_create,AC_SUBST(LIBPTHREAD,"-lpthread")) +AC_CHECK_LIB(thr,pthread_create,AC_SUBST(LIBPTHREAD,"-lthr")) =20 AC_SUBST(XLIB,"") AC_SUBST(XFILES,"") @@ -1116,18 +1116,18 @@ ac_cv_ld_rpath=3D"yes",ac_cv_ld_rpath=3D"no")]) if test "$ac_cv_ld_rpath" =3D "yes" then =2D AC_SUBST(LDEXERPATH,["-Wl,--rpath,\\\$\$ORIGIN/\`\$(RELPATH) \= $(bindir) \$(libdir)\`"]) =2D AC_SUBST(LDDLLRPATH,["-Wl,--rpath,\\\$\$ORIGIN/\`\$(RELPATH) \= $(dlldir) \$(libdir)\`"]) + AC_SUBST(LDEXERPATH,["-Wl,--rpath,${libdir}"]) + AC_SUBST(LDDLLRPATH,["-Wl,--rpath,${libdir}"]) fi =20 case $host_cpu in *i[[3456789]]86* | x86_64) =2D AC_CACHE_CHECK([whether we can relocate the executable to 0x= 7bf00000], ac_cv_ld_reloc_exec, =2D [WINE_TRY_CFLAGS([-Wl,--section-start,.interp=3D0x7bf00400= ], + AC_CACHE_CHECK([whether we can relocate the executable to 0x20= 000000], ac_cv_ld_reloc_exec, + [WINE_TRY_CFLAGS([-Wl,--section-start,.interp=3D0x20000400], ac_cv_ld_reloc_exec=3D"yes", ac_cv_ld_reloc= _exec=3D"no")]) if test "$ac_cv_ld_reloc_exec" =3D "yes" then =2D LDEXECFLAGS=3D"$LDEXECFLAGS -Wl,--section-start,.interp=3D= 0x7bf00400" + LDEXECFLAGS=3D"$LDEXECFLAGS -Wl,--section-start,.interp=3D0x= 20000400" fi ;; esac --Boundary-01=_aHOxEESzu2uIOd8 Content-Type: text/plain; charset="iso-8859-15"; name="patch-libs-wine-mmap.c" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="patch-libs-wine-mmap.c" =2D-- libs/wine/mmap.c.orig Mon Jul 24 11:12:42 2006 +++ libs/wine/mmap.c Mon Jul 24 11:13:39 2006 @@ -200,11 +200,6 @@ =20 if (!(flags & MAP_FIXED)) { =2D#if defined(__FreeBSD__) || defined(__FreeBSD_kernel__) =2D /* Even FreeBSD 5.3 does not properly support NULL here. */ =2D if( start =3D=3D NULL ) start =3D (void *)0x110000; =2D#endif =2D #ifdef MAP_TRYFIXED /* If available, this will attempt a fixed mapping in-kernel */ flags |=3D MAP_TRYFIXED; @@ -318,7 +313,7 @@ { struct reserved_area *area; struct list *ptr; =2D#if defined(__i386__) && !defined(__FreeBSD__) && !defined(__FreeBSD_ker= nel__) /* commented out until FreeBSD gets fixed */ +#if defined(__i386__) char stack; char * const stack_ptr =3D &stack; char *user_space_limit =3D (char *)0x7ffe0000; --Boundary-01=_aHOxEESzu2uIOd8-- --nextPart5011153.KMGMiH3a1f Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQBExOHgdMR2xnarec8RAmaXAKCMOnNwdauewwJkZeVFnJGb7C+gcwCgx/7Y zrPmcSy7QfdMB6TliKSi61k= =hLF8 -----END PGP SIGNATURE----- --nextPart5011153.KMGMiH3a1f-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 15:39:26 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD38B16A4DE; Mon, 24 Jul 2006 15:39:26 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 279DB43D45; Mon, 24 Jul 2006 15:39:26 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.7/8.13.7/NETPLEX) with ESMTP id k6OFdO41026474; Mon, 24 Jul 2006 11:39:25 -0400 (EDT) Date: Mon, 24 Jul 2006 11:39:24 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Tijl Coosemans In-Reply-To: <200607241706.08396.tijl@ulyssis.org> Message-ID: References: <200607221914.15826.lofi@freebsd.org> <200607241706.08396.tijl@ulyssis.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Content-ID: Content-Disposition: inline X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org, Michael Nottebrock Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 15:39:26 -0000 On Mon, 24 Jul 2006, Tijl Coosemans wrote: > On Saturday 22 July 2006 19:14, Michael Nottebrock wrote: >> WINE does have certain requirements regarding memory allocation. In >> particular it (or Windows, rather) really wants a few memory ranges >> for itself: >> >> (from wine-0.9.17/loader/preloader.c): >> >> * 0x00000000 - 0x00110000 the DOS area >> * 0x80000000 - 0x81000000 the shared heap >> * ??? - ??? the PE binary load address (usually >> starting at 0x00400000) >> >> The first two are particularly important for WINE running in win98 >> (or earlier) emulation mode, which is currently completely broken on >> FreeBSD, since those two memory ranges tend to be unavailable. > > The reason for the second range is that wine is located way at the end > of the 2G range (0x7bf00000). FreeBSD's mmap preserves heap space after > that (for brk(2) style allocations). This is about 512Mb by default so > everything in 0x7bf00000-0x9bf00000 is unavailable (unless MAP_FIXED is > used of course). > > The DOS area should be available but can't be allocated by wine because > of a FreeBSD specific quirk in its code to work arround another mmap > related problem. > > Both problems can be solved by locating wine at say 0x20000000 instead > of 0x7bf00000. That leaves plenty of space for the windows executable > and allows us to remove mmap related freebsd quirks from wine's code. > > I've attached two patches that accomplish this, but this seems to > trigger other problems, so use at your own risk. If you want to try > them, place them in the port's files/ directory and add a line > containing "USE_AUTOTOOLS= autoconf:259" to the Makefile. This seems to > break wine+libpthread, so I've also changed the port to use libthr > instead. > > For the libpthread experts, I haven't investigated that much further > yet, but libpthread seems to fail in create_stack() from > _pthread_create() from _thr_start_sig_daemon(). See my response to this in a previous reply to this thread. libthr and libpthread use LDT's for TLS. WINE is stomping on them because it doesn't properly create LDTs. This is not a problem with either of the thread libraries and this issue has been known ever since we implemented TLS years ago. -- DE From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 15:47:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B947916A4DD for ; Mon, 24 Jul 2006 15:47:42 +0000 (UTC) (envelope-from scheidell@secnap.net) Received: from mail.secnap.com (mail.secnap.com [204.89.241.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FDF543D45 for ; Mon, 24 Jul 2006 15:47:42 +0000 (GMT) (envelope-from scheidell@secnap.net) Received: from [10.70.3.3] (unknown [10.70.3.3]) by mail.secnap.com (Postfix) with ESMTP id 8E980164838 for ; Mon, 24 Jul 2006 11:47:41 -0400 (EDT) Message-ID: <44C4EB9D.1060106@secnap.net> Date: Mon, 24 Jul 2006 11:47:41 -0400 From: Michael Scheidell Organization: SECNAP Network Security User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 15:47:42 -0000 I had a 200ms software timer running in FBSD 5.4 that isn't working in 5.5 now. This software timer was resetting a 1 second hardware watchdog timer. Every 200ms, I sent a reset to the hardware WDT. Everything worked on 5.4, but I am getting failures on 5.5 It appears that something changed in ntpd, clock_gettime, or nanosleep. I can 'fix' it by specifying -x in ntpd (slew even if large change), but after a day, time is off by more than 5 mins. I think all I did was upgrade from 5.4 to 5.5 It fails within 1 second of getting these types of log entries: Jul 23 15:03:42 audit18 ntpd[473]: time reset -2.497234 s Jul 23 16:03:56 audit18 ntpd[473]: time reset +1.532401 s if -2.49, and we were inside of the nanosleep() and I was expecting a 200ms sleep, I get 2600ms. (yes, I think I do. the 1 second hardware timer on the WDT triggers if not reset every 1000ms (1 second)) if +1.53, I have to do some hard thinking since my nanosleep() APPEARS to have happened in -1330 ms. Oh, did I mention, this worked on 5.4? and if a prevent the 'time reset' log entries by adding the -x switch to ntpd I don't get failures? (except that the clock drifts about 2 seconds per hour!) Also, 5.4 also showed alternating -2 and +2 second time resets, about once an hour, but it didn't seem to affect nanosleep(). ntpd using strata 2 ntp server, with 2 other backups. ntpdc -c peers shows drift when using -x option. (no different then 5.4 did) -- Michael Scheidell, CTO SECNAP Network Security / www.secnap.com scheidell@secnap.net / 1+561-999-5000, x 1131 From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 15:43:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D803F16A4DA; Mon, 24 Jul 2006 15:43:41 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.131.111.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7028343D4C; Mon, 24 Jul 2006 15:43:41 +0000 (GMT) (envelope-from gerald@pfeifer.com) Received: from acrux.dbai.tuwien.ac.at (acrux [128.131.111.60]) by vexpert.dbai.tuwien.ac.at (Postfix) with ESMTP id 7221C137B4; Mon, 24 Jul 2006 17:43:40 +0200 (CEST) Received: by acrux.dbai.tuwien.ac.at (Postfix, from userid 1203) id 9E4EF1A7C2; Mon, 24 Jul 2006 17:43:44 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by acrux.dbai.tuwien.ac.at (Postfix) with ESMTP id 8E33D1A7C0; Mon, 24 Jul 2006 17:43:44 +0200 (CEST) Date: Mon, 24 Jul 2006 17:43:44 +0200 (CEST) From: Gerald Pfeifer To: Daniel Eischen In-Reply-To: Message-ID: References: <200607221914.15826.lofi@freebsd.org> <200607241706.08396.tijl@ulyssis.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Mon, 24 Jul 2006 16:18:54 +0000 Cc: Tijl Coosemans , freebsd-emulation@freebsd.org, Michael Nottebrock , freebsd-hackers@freebsd.org Subject: Re: [emulation] WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 15:43:42 -0000 On Mon, 24 Jul 2006, Daniel Eischen wrote: > See my response to this in a previous reply to this thread. libthr > and libpthread use LDT's for TLS. WINE is stomping on them because > it doesn't properly create LDTs. This is not a problem with either > of the thread libraries and this issue has been known ever since we > implemented TLS years ago. If someone could help getting this address in Wine, this would be really cool! Gerald From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 16:39:48 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CC5B16A4DA; Mon, 24 Jul 2006 16:39:48 +0000 (UTC) (envelope-from tijl@ulyssis.org) Received: from outmx004.isp.belgacom.be (outmx004.isp.belgacom.be [195.238.4.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id E917543D5D; Mon, 24 Jul 2006 16:39:47 +0000 (GMT) (envelope-from tijl@ulyssis.org) Received: from outmx004.isp.belgacom.be (localhost [127.0.0.1]) by outmx004.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6OGdihO020084; Mon, 24 Jul 2006 18:39:45 +0200 (envelope-from ) Received: from kalimero.kotnet.org (88.193-245-81.adsl-dyn.isp.belgacom.be [81.245.193.88]) by outmx004.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6OGdZlX019995; Mon, 24 Jul 2006 18:39:35 +0200 (envelope-from ) Received: from kalimero.kotnet.org (kalimero.kotnet.org [127.0.0.1]) by kalimero.kotnet.org (8.13.6/8.13.6) with ESMTP id k6OGdSqf072006; Mon, 24 Jul 2006 18:39:29 +0200 (CEST) (envelope-from tijl@ulyssis.org) From: Tijl Coosemans To: freebsd-emulation@freebsd.org, Daniel Eischen Date: Mon, 24 Jul 2006 18:39:22 +0200 User-Agent: KMail/1.9.3 References: <200607221914.15826.lofi@freebsd.org> <200607241706.08396.tijl@ulyssis.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart8584442.zxQZd1tTzu"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607241839.28229.tijl@ulyssis.org> Cc: freebsd-hackers@freebsd.org, Michael Nottebrock Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 16:39:48 -0000 --nextPart8584442.zxQZd1tTzu Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 24 July 2006 17:39, Daniel Eischen wrote: > On Mon, 24 Jul 2006, Tijl Coosemans wrote: > > I've attached two patches that accomplish this, but this seems to > > trigger other problems, so use at your own risk. If you want to try > > them, place them in the port's files/ directory and add a line > > containing "USE_AUTOTOOLS=3D autoconf:259" to the Makefile. This > > seems to break wine+libpthread, so I've also changed the port to > > use libthr instead. > > > > For the libpthread experts, I haven't investigated that much > > further yet, but libpthread seems to fail in create_stack() from > > _pthread_create() from _thr_start_sig_daemon(). > > See my response to this in a previous reply to this thread. libthr > and libpthread use LDT's for TLS. WINE is stomping on them because > it doesn't properly create LDTs. This is not a problem with either > of the thread libraries and this issue has been known ever since we > implemented TLS years ago. And as I stated later on in that thread, I don't see where libpthread=20 and libthr still use LDT entries. As far as I understand the code,=20 instead of using an LDT entry per thread (as it sure used to be), only=20 one single GDT entry is used whose base address is updated during a=20 context switch. Looking at the cvs history, it has been working like=20 this since a couple commits of Peter Wemm about a year ago. And if nothing but Wine uses the LDT, Wine's static allocation of LDT=20 entries can't be the problem. --nextPart8584442.zxQZd1tTzu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQBExPfAdMR2xnarec8RAozJAJ0R/bow6no5XbyepuehSZK+AzyTWACbBYMj ippogN6v63focdD6woOHifE= =tENU -----END PGP SIGNATURE----- --nextPart8584442.zxQZd1tTzu-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 16:49:27 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DE2916A598; Mon, 24 Jul 2006 16:49:27 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2331C43D53; Mon, 24 Jul 2006 16:49:26 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.7/8.13.7/NETPLEX) with ESMTP id k6OGnPBx017909; Mon, 24 Jul 2006 12:49:25 -0400 (EDT) Date: Mon, 24 Jul 2006 12:49:25 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Tijl Coosemans In-Reply-To: <200607241839.28229.tijl@ulyssis.org> Message-ID: References: <200607221914.15826.lofi@freebsd.org> <200607241706.08396.tijl@ulyssis.org> <200607241839.28229.tijl@ulyssis.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org, Michael Nottebrock Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 16:49:27 -0000 On Mon, 24 Jul 2006, Tijl Coosemans wrote: > On Monday 24 July 2006 17:39, Daniel Eischen wrote: >> On Mon, 24 Jul 2006, Tijl Coosemans wrote: >>> I've attached two patches that accomplish this, but this seems to >>> trigger other problems, so use at your own risk. If you want to try >>> them, place them in the port's files/ directory and add a line >>> containing "USE_AUTOTOOLS= autoconf:259" to the Makefile. This >>> seems to break wine+libpthread, so I've also changed the port to >>> use libthr instead. >>> >>> For the libpthread experts, I haven't investigated that much >>> further yet, but libpthread seems to fail in create_stack() from >>> _pthread_create() from _thr_start_sig_daemon(). >> >> See my response to this in a previous reply to this thread. libthr >> and libpthread use LDT's for TLS. WINE is stomping on them because >> it doesn't properly create LDTs. This is not a problem with either >> of the thread libraries and this issue has been known ever since we >> implemented TLS years ago. > > And as I stated later on in that thread, I don't see where libpthread > and libthr still use LDT entries. As far as I understand the code, > instead of using an LDT entry per thread (as it sure used to be), only > one single GDT entry is used whose base address is updated during a > context switch. Looking at the cvs history, it has been working like > this since a couple commits of Peter Wemm about a year ago. > > And if nothing but Wine uses the LDT, Wine's static allocation of LDT > entries can't be the problem. Look, we use %gs for TLS, period. Go see libpthread/arch/i386/i386/pthread_md.c for how libpthread does it. TLS would not work without setting aside a register for the threads library (and rtld) to use. -- DE From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 17:45:08 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9097116A4DD for ; Mon, 24 Jul 2006 17:45:08 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [80.237.196.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9951A43D45 for ; Mon, 24 Jul 2006 17:45:07 +0000 (GMT) (envelope-from erdgeist@erdgeist.org) Received: (qmail 90589 invoked by uid 0); 24 Jul 2006 17:44:08 -0000 Received: from erdgeist.org (erdgeist@erdgeist.org@80.237.196.15) by elektropost.org with AES256-SHA encrypted SMTP; 24 Jul 2006 17:44:08 -0000 Date: Mon, 24 Jul 2006 19:44:07 +0200 (CEST) From: Dirk Engling To: freebsd-hackers@freebsd.org Message-ID: <20060724192149.O46542@erdgeist.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: ezjail@erdgeist.org Subject: Rebooting jails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 17:45:08 -0000 Hello, I'm currently looking for a standardized way to 'reboot' jails from within. 'shutdown' is a simple one, just issue 'kill -TERM -1' and you're done. Now, rebooting generally involves starting up the jail afterwards. One way that works from a shell started via jexec would be to 'kill -TERM -1' all processes and execve into whatever is supposed to be the kickoff command, e.g. /bin/sh /etc/rc. However, doing this from a shell that has been run from sshd results in killing the sshd and thus the shell trying to restart the jail. Another way would be to have a daemon waiting in the host system that is checking jids in /var/run/jail_*.id say all 5 Minutes and if pgrep returns anything than 0, the jail is being restarted (you may combine that with some conditions, say having a file '/.rebootme' under jail's root directory). This approach is more a watchdog than a reboot mechanism, you would need to do unintuitive stuff like adding a line to crontab (where it would even run if no jails are active, which sucks). One could use an 'at +5m $prefix/bin/watchdog' in the script that starts the jail in the first place which calls itself the same way. All this is annoying to track, a watchdog script sleeping in the background would more easily be visible in ps. And, waiting for the host system to finally rerun to jail may cost many boring admin-5min-periods. Maybe someone can help me out with a cool idea. Regards erdgeist From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 18:38:39 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53FAA16A4DD; Mon, 24 Jul 2006 18:38:39 +0000 (UTC) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0982143D46; Mon, 24 Jul 2006 18:38:37 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.18.229]) ([10.251.18.229]) by a50.ironport.com with ESMTP; 24 Jul 2006 11:38:37 -0700 Message-ID: <44C513AD.70505@elischer.org> Date: Mon, 24 Jul 2006 11:38:37 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gerald Pfeifer References: <200607221914.15826.lofi@freebsd.org> <200607241706.08396.tijl@ulyssis.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Daniel Eischen , Tijl Coosemans , freebsd-emulation@freebsd.org, Michael Nottebrock , freebsd-hackers@freebsd.org Subject: Re: [emulation] WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 18:38:39 -0000 Gerald Pfeifer wrote: >On Mon, 24 Jul 2006, Daniel Eischen wrote: > > >>See my response to this in a previous reply to this thread. libthr >>and libpthread use LDT's for TLS. WINE is stomping on them because >>it doesn't properly create LDTs. This is not a problem with either >>of the thread libraries and this issue has been known ever since we >>implemented TLS years ago. >> >> > >If someone could help getting this address in Wine, this would be >really cool! > > wine assumes it knows what LDTs it wants and goes for them by name. FreeBSD expects you to let it give you the next free one. >Gerald >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 19:20:15 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7307A16A4DA for ; Mon, 24 Jul 2006 19:20:15 +0000 (UTC) (envelope-from dgilbert@daveg.ca) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 306F443D45 for ; Mon, 24 Jul 2006 19:20:14 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id E59E71E15D; Mon, 24 Jul 2006 15:20:13 -0400 (EDT) Received: by canoe.dclg.ca (Postfix, from userid 101) id 3AFA14AC2B; Mon, 24 Jul 2006 15:19:18 -0400 (EDT) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17605.7478.194820.171800@canoe.dclg.ca> Date: Mon, 24 Jul 2006 15:19:18 -0400 To: freebsd-hackers@freebsd.org X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid Subject: kqueue doesn't see if_tun X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 19:20:15 -0000 I have some code that sets up a tunnel device and registers a kqueue filter for it ... ending roughly in: EV_SET(&kqev, cons->tunSocket, EVFILT_READ, EV_ADD | EV_ENABLE, 0, 0, &cons->fsdkq); kevent(fsd->kq, &kqev, 1, NULL, 0, NULL); This event never fires. In another part of a the code, I have a timer --- so I call the tunnel reading function from there and (low and behold) there is a packet. Does EVFILT_READ just not work on tunnel devices? Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 21:18:52 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 512C716A4E1 for ; Mon, 24 Jul 2006 21:18:52 +0000 (UTC) (envelope-from scheidell@secnap.net) Received: from mail.secnap.com (mail.secnap.com [204.89.241.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEB4943D6E for ; Mon, 24 Jul 2006 21:18:51 +0000 (GMT) (envelope-from scheidell@secnap.net) Received: from [10.70.3.3] (unknown [10.70.3.3]) by mail.secnap.com (Postfix) with ESMTP id EDEE6164838 for ; Mon, 24 Jul 2006 17:18:50 -0400 (EDT) Message-ID: <44C5393A.6010203@secnap.net> Date: Mon, 24 Jul 2006 17:18:50 -0400 From: Michael Scheidell Organization: SECNAP Network Security User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <44C4EB9D.1060106@secnap.net> In-Reply-To: <44C4EB9D.1060106@secnap.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 21:18:52 -0000 Michael Scheidell wrote: > I had a 200ms software timer running in FBSD 5.4 that isn't working in > 5.5 now. > This software timer was resetting a 1 second hardware watchdog timer. > Every 200ms, I sent a reset to the hardware WDT. > Everything worked on 5.4, but I am getting failures on 5.5 > It appears that something changed in ntpd, clock_gettime, or nanosleep. > I can 'fix' it by specifying -x in ntpd (slew even if large change), > but after a day, time is off by more than 5 mins. > > I think all I did was upgrade from 5.4 to 5.5 I suspect, but have not found it, that on 5.4 when ntp sets time back using adjtime, it triggers any nanosleep() that would be affected. It looks like FREEBSD 5.4 doesn't do this. Reason I ask: simple program: #define MS_SLEEP(x) nanosleep(x*1000); main() { enable_our_hardware_wdt(1); // Set our hardware watchdog timer to die if not patted in 1 second. while(1) { MS_SLEEP(200); // sleep for 200ms pat_our_dog(); } } if I set clock back 2 seconds using ntpdate, or if ntpd sets clock back 2 seconds, the nanosleep sleeps for more than 1 second. Reason I know: the hardware timer goes off. I have tried starting process with nice -19, rtprio 31, doesn't matter. (ntpdate -qd us.pool.ntp.org shows offset of -2 seconds or more) Again, worked fine in 5.4. my current workaround is to run ntpd with -x to slew changes to 128ms, but after 10 hours, one of the computers is off by 10 seconds. ('date' vs ntpdate -qd us.pool.ntp.org) then every 24 hours, I have to slay ntpd, run ntpdate -b to fix the time, start ntpd and our_dog. > > It fails within 1 second of getting these types of log entries: > Jul 23 15:03:42 audit18 ntpd[473]: time reset -2.497234 s > Jul 23 16:03:56 audit18 ntpd[473]: time reset +1.532401 s > > if -2.49, and we were inside of the nanosleep() and I was expecting a > 200ms sleep, I get 2600ms. > (yes, I think I do. the 1 second hardware timer on the WDT triggers > if not reset every 1000ms (1 second)) > > if +1.53, I have to do some hard thinking since my nanosleep() APPEARS > to have happened in -1330 ms. > > Oh, did I mention, this worked on 5.4? and if a prevent the 'time > reset' log entries by adding the -x switch to ntpd I don't get > failures? (except that the clock drifts about 2 seconds per hour!) > Also, 5.4 also showed alternating -2 and +2 second time resets, about > once an hour, but it didn't seem to affect nanosleep(). > > ntpd using strata 2 ntp server, with 2 other backups. > ntpdc -c peers shows drift when using -x option. (no different then > 5.4 did) > -- Michael Scheidell, CTO SECNAP Network Security / www.secnap.com scheidell@secnap.net / 1+561-999-5000, x 1131 From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 21:36:45 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6595016A4DA for ; Mon, 24 Jul 2006 21:36:45 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id D08B543D46 for ; Mon, 24 Jul 2006 21:36:44 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (nv92z4ct8ym5hc75@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id k6OLagV4049549; Mon, 24 Jul 2006 14:36:42 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id k6OLagpk049548; Mon, 24 Jul 2006 14:36:42 -0700 (PDT) (envelope-from jmg) Date: Mon, 24 Jul 2006 14:36:42 -0700 From: John-Mark Gurney To: David Gilbert Message-ID: <20060724213642.GQ96589@funkthat.com> Mail-Followup-To: David Gilbert , freebsd-hackers@freebsd.org References: <17605.7478.194820.171800@canoe.dclg.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17605.7478.194820.171800@canoe.dclg.ca> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-hackers@freebsd.org Subject: Re: kqueue doesn't see if_tun X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 21:36:45 -0000 David Gilbert wrote this message on Mon, Jul 24, 2006 at 15:19 -0400: > I have some code that sets up a tunnel device and registers a kqueue > filter for it ... ending roughly in: > > EV_SET(&kqev, cons->tunSocket, EVFILT_READ, EV_ADD | EV_ENABLE, 0, 0, &cons->fsdkq); > kevent(fsd->kq, &kqev, 1, NULL, 0, NULL); > > This event never fires. In another part of a the code, I have a timer > --- so I call the tunnel reading function from there and (low and > behold) there is a packet. > > Does EVFILT_READ just not work on tunnel devices? No one has written a d_kqfilter entry for tun... so, until someone does, kqueue will not work on tun... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 23:23:45 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F5F816A4DF; Mon, 24 Jul 2006 23:23:45 +0000 (UTC) (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 14A6E43D46; Mon, 24 Jul 2006 23:23:45 +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.4/8.13.4) with ESMTP id k6ONMKA2003597; Mon, 24 Jul 2006 17:22:21 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 24 Jul 2006 17:22:41 -0600 (MDT) Message-Id: <20060724.172241.139505616.imp@bsdimp.com> To: tyler@bleepsoft.com From: "M. Warner Losh" In-Reply-To: References: X-Mailer: Mew version 4.2 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, 24 Jul 2006 17:22:21 -0600 (MDT) Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Failing `make buildworld` with today's source X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 23:23:45 -0000 The problem is that gcc doesn't know how to map iguana onto something it groks. Maybe you need to have TARGET_ARCH be one of the supported CPUs? I'm unsure what iguana runs on, so I'm not sure which one you should pick. Warner From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 00:22:28 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD98216A4DA for ; Tue, 25 Jul 2006 00:22:28 +0000 (UTC) (envelope-from mnorwick@centurytel.net) Received: from msa1-mx.centurytel.net (msa1-mx.centurytel.net [209.142.136.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FDFF43D55 for ; Tue, 25 Jul 2006 00:22:28 +0000 (GMT) (envelope-from mnorwick@centurytel.net) Received: from [192.168.1.15] (207-118-202-194.dyn.centurytel.net [207.118.202.194]) by msa1-mx.centurytel.net (8.13.6/8.13.6) with ESMTP id k6P0MQBL017453 for ; Mon, 24 Jul 2006 19:22:27 -0500 Message-ID: <44C56443.50106@centurytel.net> Date: Mon, 24 Jul 2006 19:22:27 -0500 From: "Michael D. Norwick" User-Agent: Debian Thunderbird 1.0.2 (X11/20060423) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Just a question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 00:22:28 -0000 The following warnings were generated by a GhostScript build during 'portmanager -u': ./src/gsfunc0.c: In function `function_Sd_enum_ptrs': ./src/gsfunc0.c:37: warning: traditional C rejects ISO C style function definitions ./src/gsfunc0.c: In function `function_Sd_reloc_ptrs': ./src/gsfunc0.c:48: warning: traditional C rejects ISO C style function definitions ./src/gsfunc0.c: In function `fn_gets_1': ./src/gsfunc0.c:74: warning: traditional C rejects ISO C style function definitions ./src/gsfunc0.c: In function `fn_gets_2': This is just a small clip of the warning when building one .c file. The build generated many of these warnings then aborted for reasons unknown to me right now. I just wanted to know what this particular warning is in reference to. Using GCC 3.4.4 (20050518). Thank You, Michael From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 00:56:02 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B946B16A4E0 for ; Tue, 25 Jul 2006 00:56:02 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF72D43D49 for ; Tue, 25 Jul 2006 00:56:00 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.7/8.13.7/Debian-1) with ESMTP id k6P0tekN007625 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 25 Jul 2006 03:55:43 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.7/8.13.7) with ESMTP id k6P0tYcQ007820; Tue, 25 Jul 2006 03:55:35 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.7/8.13.7/Submit) id k6P0tYIW007819; Tue, 25 Jul 2006 03:55:34 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Tue, 25 Jul 2006 03:55:34 +0300 From: Giorgos Keramidas To: "Michael D. Norwick" Message-ID: <20060725005534.GA7484@gothmog.pc> References: <44C56443.50106@centurytel.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44C56443.50106@centurytel.net> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.771, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.63, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-hackers@freebsd.org Subject: Re: Just a question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 00:56:02 -0000 On 2006-07-24 19:22, "Michael D. Norwick" wrote: > The following warnings were generated by a GhostScript build during > 'portmanager -u': > > ./src/gsfunc0.c: In function `function_Sd_enum_ptrs': > ./src/gsfunc0.c:37: warning: traditional C rejects ISO C style function > definitions > ./src/gsfunc0.c: In function `function_Sd_reloc_ptrs': > ./src/gsfunc0.c:48: warning: traditional C rejects ISO C style function > definitions > ./src/gsfunc0.c: In function `fn_gets_1': > ./src/gsfunc0.c:74: warning: traditional C rejects ISO C style function > definitions > ./src/gsfunc0.c: In function `fn_gets_2': > > This is just a small clip of the warning when building one .c file. The > build generated many of these warnings then aborted for reasons unknown > to me right now. I just wanted to know what this particular warning is > in reference to. Using GCC 3.4.4 (20050518). This is the warning enabled by -Wtraditional, and you get it for all functions that have full prototypes, i.e.: # giorgos@gothmog:/tmp/foo$ cc -Wtraditional foo.c # foo.c: In function `foo': # foo.c:4: warning: traditional C rejects ISO C style function definitions # foo.c: In function `main': # foo.c:10: warning: traditional C rejects ISO C style function definitions # giorgos@gothmog:/tmp/foo$ cc -Wtraditional bar.c # giorgos@gothmog:/tmp/foo$ diff -u bar.c foo.c # --- bar.c Tue Jul 25 03:53:59 2006 # +++ foo.c Tue Jul 25 03:52:13 2006 # @@ -1,12 +1,12 @@ # #include # # -int foo () # +int foo (void) # { # printf("foo\n"); # return 0; # } # # -int main() # +int main(void) # { # return foo(); # } # giorgos@gothmog:/tmp/foo$ Either the original GhostScript sources or the port uses -Wtraditional... From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 01:58:36 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1373C16A4DA; Tue, 25 Jul 2006 01:58:36 +0000 (UTC) (envelope-from tijl@ulyssis.org) Received: from outmx001.isp.belgacom.be (outmx001.isp.belgacom.be [195.238.5.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 541ED43D45; Tue, 25 Jul 2006 01:58:35 +0000 (GMT) (envelope-from tijl@ulyssis.org) Received: from outmx001.isp.belgacom.be (localhost [127.0.0.1]) by outmx001.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6P1wXqR031458; Tue, 25 Jul 2006 03:58:33 +0200 (envelope-from ) Received: from kalimero.kotnet.org (233.121-247-81.adsl-dyn.isp.belgacom.be [81.247.121.233]) by outmx001.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6P1wSs4031404; Tue, 25 Jul 2006 03:58:28 +0200 (envelope-from ) Received: from kalimero.kotnet.org (kalimero.kotnet.org [127.0.0.1]) by kalimero.kotnet.org (8.13.6/8.13.6) with ESMTP id k6P1wLYs099116; Tue, 25 Jul 2006 03:58:22 +0200 (CEST) (envelope-from tijl@ulyssis.org) From: Tijl Coosemans To: freebsd-emulation@freebsd.org, Daniel Eischen Date: Tue, 25 Jul 2006 03:58:06 +0200 User-Agent: KMail/1.9.3 References: <200607221914.15826.lofi@freebsd.org> <200607241839.28229.tijl@ulyssis.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2198738.aAC9hlQsmE"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607250358.21457.tijl@ulyssis.org> Cc: freebsd-hackers@freebsd.org, Michael Nottebrock Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 01:58:36 -0000 --nextPart2198738.aAC9hlQsmE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 24 July 2006 18:49, Daniel Eischen wrote: > On Mon, 24 Jul 2006, Tijl Coosemans wrote: > > On Monday 24 July 2006 17:39, Daniel Eischen wrote: > >> On Mon, 24 Jul 2006, Tijl Coosemans wrote: > >>> I've attached two patches that accomplish this, but this seems to > >>> trigger other problems, so use at your own risk. If you want to > >>> try them, place them in the port's files/ directory and add a > >>> line containing "USE_AUTOTOOLS=3D autoconf:259" to the Makefile. > >>> This seems to break wine+libpthread, so I've also changed the > >>> port to use libthr instead. > >>> > >>> For the libpthread experts, I haven't investigated that much > >>> further yet, but libpthread seems to fail in create_stack() from > >>> _pthread_create() from _thr_start_sig_daemon(). > >> > >> See my response to this in a previous reply to this thread.=20 > >> libthr and libpthread use LDT's for TLS. WINE is stomping on them > >> because it doesn't properly create LDTs. This is not a problem > >> with either of the thread libraries and this issue has been known > >> ever since we implemented TLS years ago. > > > > And as I stated later on in that thread, I don't see where > > libpthread and libthr still use LDT entries. As far as I understand > > the code, instead of using an LDT entry per thread (as it sure used > > to be), only one single GDT entry is used whose base address is > > updated during a context switch. Looking at the cvs history, it has > > been working like this since a couple commits of Peter Wemm about a > > year ago. > > > > And if nothing but Wine uses the LDT, Wine's static allocation of > > LDT entries can't be the problem. > > Look, we use %gs for TLS, period. Go see > libpthread/arch/i386/i386/pthread_md.c for how libpthread does it.=20 > TLS would not work without setting aside a register for the threads > library (and rtld) to use. Aaarrrrgghhh :) What you say is true of course, but %gs points to a GDT entry, not LDT.=20 libpthread and libthr no longer use LDT entries... There would be a problem of course if Wine or Windows programs=20 change %gs. Wine does seem to touch %gs but I've never actually seen it=20 change. It's always 0x001B, which is the correct value (GUGS_SEL). However, Wine/Windows uses %fs for TLS and it appears that the FreeBSD=20 kernel doesn't preserve it. It always ends up pointing to GUDATA_SEL. --nextPart2198738.aAC9hlQsmE Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQBExXq9dMR2xnarec8RAqulAJ4yxbyI98xm5NNR435SSjVRexBPGQCePcQC 2CrH4OPfAvSy7sojjFCyfg8= =hOSN -----END PGP SIGNATURE----- --nextPart2198738.aAC9hlQsmE-- From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 02:22:21 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8182816A4E1 for ; Tue, 25 Jul 2006 02:22:21 +0000 (UTC) (envelope-from mnorwick@centurytel.net) Received: from msa1-mx.centurytel.net (msa1-mx.centurytel.net [209.142.136.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id C71D343D8C for ; Tue, 25 Jul 2006 02:22:10 +0000 (GMT) (envelope-from mnorwick@centurytel.net) Received: from [192.168.1.15] (207-118-202-194.dyn.centurytel.net [207.118.202.194]) by msa1-mx.centurytel.net (8.13.6/8.13.6) with ESMTP id k6P2M8GL003616 for ; Mon, 24 Jul 2006 21:22:09 -0500 Message-ID: <44C58051.4000307@centurytel.net> Date: Mon, 24 Jul 2006 21:22:09 -0500 From: "Michael D. Norwick" User-Agent: Debian Thunderbird 1.0.2 (X11/20060423) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <44C56443.50106@centurytel.net> <20060725005534.GA7484@gothmog.pc> In-Reply-To: <20060725005534.GA7484@gothmog.pc> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Just a question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 02:22:21 -0000 Giorgos Keramidas wrote: >On 2006-07-24 19:22, "Michael D. Norwick" wrote: > > >>The following warnings were generated by a GhostScript build during >>'portmanager -u': >> >>./src/gsfunc0.c: In function `function_Sd_enum_ptrs': >>./src/gsfunc0.c:37: warning: traditional C rejects ISO C style function >>definitions >>./src/gsfunc0.c: In function `function_Sd_reloc_ptrs': >>./src/gsfunc0.c:48: warning: traditional C rejects ISO C style function >>definitions >>./src/gsfunc0.c: In function `fn_gets_1': >>./src/gsfunc0.c:74: warning: traditional C rejects ISO C style function >>definitions >>./src/gsfunc0.c: In function `fn_gets_2': >> >>This is just a small clip of the warning when building one .c file. The >>build generated many of these warnings then aborted for reasons unknown >>to me right now. I just wanted to know what this particular warning is >>in reference to. Using GCC 3.4.4 (20050518). >> >> > >This is the warning enabled by -Wtraditional, and you get it for all >functions that have full prototypes, i.e.: > ># giorgos@gothmog:/tmp/foo$ cc -Wtraditional foo.c ># foo.c: In function `foo': ># foo.c:4: warning: traditional C rejects ISO C style function definitions ># foo.c: In function `main': ># foo.c:10: warning: traditional C rejects ISO C style function definitions ># giorgos@gothmog:/tmp/foo$ cc -Wtraditional bar.c ># giorgos@gothmog:/tmp/foo$ diff -u bar.c foo.c ># --- bar.c Tue Jul 25 03:53:59 2006 ># +++ foo.c Tue Jul 25 03:52:13 2006 ># @@ -1,12 +1,12 @@ ># #include ># ># -int foo () ># +int foo (void) ># { ># printf("foo\n"); ># return 0; ># } ># ># -int main() ># +int main(void) ># { ># return foo(); ># } ># giorgos@gothmog:/tmp/foo$ > >Either the original GhostScript sources or the port uses -Wtraditional... > > > > > The compiler complaints I neglected to post were about #pragma's in 'traditional' C in numerous header files in /usr/src so this make sense. GhostScript and it's dependencies compiled and installed but now I have to wonder if the warnings will affect the funtionality. What do I put in /etc/make.conf to keep this from happening on the next upgrade? The GhostScript source I used was from the ports tree. Thank You, Michael From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 07:59:57 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BA0916A4DA for ; Tue, 25 Jul 2006 07:59:57 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail06.syd.optusnet.com.au (mail06.syd.optusnet.com.au [211.29.132.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0E3243D46 for ; Tue, 25 Jul 2006 07:59:56 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail06.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k6P7xlED007730 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 Jul 2006 17:59:52 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k6P7xlrk000964; Tue, 25 Jul 2006 17:59:47 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k6P7xkZm000963; Tue, 25 Jul 2006 17:59:46 +1000 (EST) (envelope-from peter) Date: Tue, 25 Jul 2006 17:59:46 +1000 From: Peter Jeremy To: Michael Scheidell Message-ID: <20060725075946.GA728@turion.vk2pj.dyndns.org> References: <44C4EB9D.1060106@secnap.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PEIAKu/WMn1b1Hv9" Content-Disposition: inline In-Reply-To: <44C4EB9D.1060106@secnap.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 07:59:57 -0000 --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, 2006-Jul-24 11:47:41 -0400, Michael Scheidell wrote: >This software timer was resetting a 1 second hardware watchdog timer. >Every 200ms, I sent a reset to the hardware WDT. >Everything worked on 5.4, but I am getting failures on 5.5 Basically, when you ask for a 200msec delay, the kernel sleeps until an absolute time. It looks like the handling of absolute time sleeps across time steps was changed. Unfortunately, both approaches are equally valid in different circumstances. >It fails within 1 second of getting these types of log entries: >Jul 23 15:03:42 audit18 ntpd[473]: time reset -2.497234 s >Jul 23 16:03:56 audit18 ntpd[473]: time reset +1.532401 s Rather than focussing on the changed sleep handling, I suggest you concentrate on fixing your clock: Your system clock should not be stepping. >if -2.49, and we were inside of the nanosleep() and I was expecting a=20 >200ms sleep, I get 2600ms. >(yes, I think I do. the 1 second hardware timer on the WDT triggers if=20 >not reset every 1000ms (1 second)) Say the time is 12:34:56.789 and you do nanosleep(200msec). This is implemented as "sleep until 12:34:56.989". When you set the clock back by 2.49 seconds, it then takes an additional 2.49 seconds (a total of 2.69 seconds) until the timer expires. >ntpd using strata 2 ntp server, with 2 other backups. I presume the servers are all stable (ie not stepping) and have a reasonably low delay. If so, I suspect your ntpd PLL has locked up. I've seen problems with some versions of ntpd that they can lock at +/-300ppm and just step regularly. I'm not exactly sure what triggers it but it seems to be exacerbated by noisy time servers (eg via a heavily loaded network link). A work-around is to delete ntp.drift and restart ntpd. You might like to enable some of the ntpd statistics gathering and see if anything anomolous is occurring. --=20 Peter Jeremy --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFExc9y/opHv/APuIcRAnJTAKCQeKWYEE/3MScGtt6zTrn0b2Y9/wCgrJEk 8AqMXSEBQpJpYCpSlBSFNrc= =lP4P -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9-- From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 09:13:02 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C2B516A4DA for ; Tue, 25 Jul 2006 09:13:02 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FBF843D53 for ; Tue, 25 Jul 2006 09:13:00 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5E4AF.dip.t-dialin.net [84.165.228.175]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.6/8.13.6) with ESMTP id k6P90kk8001286; Tue, 25 Jul 2006 11:00:46 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.4/8.13.3) with ESMTP id k6P9ClPC077944; Tue, 25 Jul 2006 11:12:47 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Tue, 25 Jul 2006 11:12:47 +0200 Message-ID: <20060725111247.646lw5dhsgcso48o@netchild.homeip.net> X-Priority: 3 (Normal) Date: Tue, 25 Jul 2006 11:12:47 +0200 From: Alexander Leidinger To: John-Mark Gurney References: <17605.7478.194820.171800@canoe.dclg.ca> <20060724213642.GQ96589@funkthat.com> In-Reply-To: <20060724213642.GQ96589@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.1) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new X-Mailman-Approved-At: Tue, 25 Jul 2006 11:25:48 +0000 Cc: freebsd-hackers@freebsd.org, David Gilbert Subject: Re: kqueue doesn't see if_tun X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 09:13:02 -0000 Quoting John-Mark Gurney (from Mon, 24 Jul 2006 14:36:42 -0700): > No one has written a d_kqfilter entry for tun... so, until someone > does, kqueue will not work on tun... Would you please come up with an entry for our ideas list (http://www.freebsd.org/projects/ideas/) for identifying pieces where kqueue support is missing and adding appropriate support? Something similar to existing entries or better (the more is explained, the higher the probability that someone tries to do it). A plain text version would be enough. Bye, Alexander. -- QOTD: "You're so dumb you don't even have wisdom teeth." http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 11:54:58 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D99F316A4DD for ; Tue, 25 Jul 2006 11:54:58 +0000 (UTC) (envelope-from scheidell@secnap.net) Received: from secnap2.secnap.com (secnap2.secnap.com [204.89.241.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7092043D49 for ; Tue, 25 Jul 2006 11:54:57 +0000 (GMT) (envelope-from scheidell@secnap.net) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Date: Tue, 25 Jul 2006 07:54:54 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FBSD 5.5 and software timers Thread-Index: AcavwFlZI7GndGbtRPC9lIOzU1wYvQAIG70A From: "Michael Scheidell" To: "Peter Jeremy" Cc: freebsd-hackers@freebsd.org Subject: RE: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 11:54:58 -0000 > -----Original Message----- > From: Peter Jeremy [mailto:peterjeremy@optushome.com.au]=20 > Sent: Tuesday, July 25, 2006 4:00 AM > To: Michael Scheidell > Cc: freebsd-hackers@freebsd.org > Subject: Re: FBSD 5.5 and software timers >=20 >=20 > Basically, when you ask for a 200msec delay, the kernel=20 > sleeps until an absolute time. It looks like the handling of=20 > absolute time sleeps across time steps was changed. =20 > Unfortunately, both approaches are equally valid in different=20 > circumstances. I agree >=20 > >It fails within 1 second of getting these types of log=20 > entries: Jul 23=20 > >15:03:42 audit18 ntpd[473]: time reset -2.497234 s Jul 23 16:03:56=20 > >audit18 ntpd[473]: time reset +1.532401 s >=20 > Rather than focussing on the changed sleep handling, I=20 > suggest you concentrate on fixing your clock: Your system=20 > clock should not be stepping. >=20 Except: 20 different machines. Some IBM 300's with 2.0Ghz P4,s, 305 and 306's with 2.8P4, some DELL 750's and 850's with 2.8p4 with HTT enabled. Even the 5.4 machines shows the bifurcating -1, +2, -2, +1 time resets, but timers work more like I want them to. > I presume the servers are all stable (ie not stepping) and=20 > have a reasonably low delay. If so, I suspect your ntpd PLL=20 > has locked up. I've seen problems with some versions of ntpd=20 20 different machines? From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 12:31:48 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A00416A4DA for ; Tue, 25 Jul 2006 12:31:48 +0000 (UTC) (envelope-from scheidell@secnap.net) Received: from secnap2.secnap.com (secnap2.secnap.com [204.89.241.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6D0843D45 for ; Tue, 25 Jul 2006 12:31:47 +0000 (GMT) (envelope-from scheidell@secnap.net) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Date: Tue, 25 Jul 2006 08:31:47 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FBSD 5.5 and software timers Thread-Index: AcavcHUGcLvjUUzgRPKOnUNzdYzkXwAcZPNg From: "Michael Scheidell" To: Subject: RE: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 12:31:48 -0000 > -----Original Message----- > From: Steve Watt [mailto:steve@Watt.COM]=20 > Sent: Monday, July 24, 2006 6:28 PM > To: Michael Scheidell > Cc: hackers@freebsd.com > Subject: Re: FBSD 5.5 and software timers > It sounds like ntpd isn't really synchronizing. If you keep=20 > an eye on associations (my finger-memory command is 'ntpq -c=20 > peer -c assoc -c rv') over time, you may notice that your=20 > machine never decides to synchronize. Especially interesting=20 > is the 'condition' column in the 'assoc' output. Ntp hasn't changed from 5.4 to 5.4, still acts the same. Ntp versions look like they are the same, only thing changed is kernel. ntpdc -c peers (same command) does show the * on one of them, so I assume=20 Also note, this happens across 20 different computers (ntp) but only the 5.5 built systems have a problem with nanosleep(). I guess it depends on the design reason: Did freebsd decide to change how nanosleep() worked on 5.5? Or is this a bug? On 5.4, if you set a 200ms sleep: nanosleep(200*1000) it triggered reasonably close to 200ms, no matter if the wallclock went forward or back. On 5.5, if at 12:32.20000000 you set a 200ms sleep and changed the wallclock with ntpd back 9 seconds , nanosleep expires in 9 seconds plus 200ms. Here is a 5.5 system: 20ghz, no HTT, ntpd started with -x: If I started it without the -x offsets would be in the -2 or +1 area. ntpq -c peer -c assoc -c rv remote refid st t when poll reach delay offset jitter =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D LOCAL(0) LOCAL(0) 10 l 6 64 377 0.000 0.000 0.004 +a77.coleman.edu 204.152.184.72 2 u 668 1024 377 119.466 -35277. 422.506 *meow.febo.com 192.168.1.230 2 u 319 1024 377 87.445 -35443. 436.095 +216-228-12-34.d 216.218.192.202 2 u 649 1024 377 143.816 -35295. 441.571 ind assID status conf reach auth condition last_event cnt =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D 1 14084 9014 yes yes none reject reachable 1 2 14085 b414 yes yes none candidat reachable 1 3 14086 b614 yes yes none sys.peer reachable 1 4 14087 b414 yes yes none candidat reachable 1 status=3D0684 leap_none, sync_ntp, 8 events, event_peer/strat_chg, version=3D"ntpd 4.2.0-a Wed Jul 5 17:49:24 EDT 2006 (1)", processor=3D"i386", system=3D"FreeBSD/5.5-RELEASE-p2", leap=3D00, = stratum=3D3, precision=3D-18, rootdelay=3D88.208, rootdispersion=3D35861.579, = peer=3D14086, refid=3D24.123.66.139, reftime=3Dc87086c3.b381f74c Tue, Jul 25 2006 8:02:11.701, poll=3D10, clock=3Dc8708802.e65819f6 Tue, Jul 25 2006 8:07:30.899, state=3D4, offset=3D-35343.172, frequency=3D422.004, jitter=3D462.419, = stability=3D0.119 Does anyone know if this is a design change? The handling of nanosleep() and the wallclock? Does 6.1 do this? If if 6.1 works, does this mean that 6.2 will break it also? What about posix 'real time' timers? Would I have better luck with them across os versions? >=20 > As for whys, it rather depends on what you see from the ntpq commands. >=20 Could still be, but there seems to be no way to fix it. This isnt a hardware problem, its 20 different computers, ibm 300, 305,306's, p4 2.8, and 2.0's, Dell 750's and 850's with p4 2.8's with HTT. From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 15:32:33 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF73F16A4DA for ; Tue, 25 Jul 2006 15:32:33 +0000 (UTC) (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 4B36143D45 for ; Tue, 25 Jul 2006 15:32:33 +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.4/8.13.4) with ESMTP id k6PFVvGf018961; Tue, 25 Jul 2006 09:31:57 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 25 Jul 2006 09:32:15 -0600 (MDT) Message-Id: <20060725.093215.1324585171.imp@bsdimp.com> To: peterjeremy@optushome.com.au From: "M. Warner Losh" In-Reply-To: <20060725075946.GA728@turion.vk2pj.dyndns.org> References: <44C4EB9D.1060106@secnap.net> <20060725075946.GA728@turion.vk2pj.dyndns.org> X-Mailer: Mew version 4.2 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]); Tue, 25 Jul 2006 09:31:58 -0600 (MDT) Cc: scheidell@secnap.net, freebsd-hackers@freebsd.org Subject: Re: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 15:32:33 -0000 In message: <20060725075946.GA728@turion.vk2pj.dyndns.org> Peter Jeremy writes: : On Mon, 2006-Jul-24 11:47:41 -0400, Michael Scheidell wrote: : >This software timer was resetting a 1 second hardware watchdog timer. : >Every 200ms, I sent a reset to the hardware WDT. : >Everything worked on 5.4, but I am getting failures on 5.5 : : Basically, when you ask for a 200msec delay, the kernel sleeps until : an absolute time. It looks like the handling of absolute time : sleeps across time steps was changed. Unfortunately, both approaches : are equally valid in different circumstances. With libc_r, I've had problems dating back to 3.x with sleeping during a time step. I've not investigated libthr or libpthread. : >It fails within 1 second of getting these types of log entries: : >Jul 23 15:03:42 audit18 ntpd[473]: time reset -2.497234 s : >Jul 23 16:03:56 audit18 ntpd[473]: time reset +1.532401 s : : Rather than focussing on the changed sleep handling, I suggest you : concentrate on fixing your clock: Your system clock should not be : stepping. With time running like the above indicates, you'll never get good, stable performance and you'll note all kinds of anomalous behavior. Until you can fix the above, anything else you do is futile. I'd suggest using a different timecounter. There are often times when this solves problems. : >ntpd using strata 2 ntp server, with 2 other backups. : : I presume the servers are all stable (ie not stepping) and have a : reasonably low delay. If so, I suspect your ntpd PLL has locked up. : I've seen problems with some versions of ntpd that they can lock : at +/-300ppm and just step regularly. I'm not exactly sure what : triggers it but it seems to be exacerbated by noisy time servers : (eg via a heavily loaded network link). A work-around is to delete : ntp.drift and restart ntpd. You might like to enable some of the : ntpd statistics gathering and see if anything anomolous is occurring. ntpd hates time sources (including the local oscillator) that have a frequency error of more than about 200ppm, and clamps it to 300ppm. The drift rate above was 1.532 seeconds in 3606 seconds, or about 425ppm. If your local oscillator exceeds the 300ppm clamping that ntpd does, you'll get wild swings like you are seeing. You might also try starting ntpd with the only step once flag, which will cause the above steps to stop. But it will mean that time won't be well synchronized. Warner From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 15:35:54 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F077116A4DF for ; Tue, 25 Jul 2006 15:35:54 +0000 (UTC) (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 8B69B43D46 for ; Tue, 25 Jul 2006 15:35:54 +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.4/8.13.4) with ESMTP id k6PFYBYV019001; Tue, 25 Jul 2006 09:34:11 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 25 Jul 2006 09:34:29 -0600 (MDT) Message-Id: <20060725.093429.-1648696470.imp@bsdimp.com> To: scheidell@secnap.net From: "M. Warner Losh" In-Reply-To: References: X-Mailer: Mew version 4.2 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]); Tue, 25 Jul 2006 09:34:12 -0600 (MDT) Cc: freebsd-hackers@freebsd.org Subject: Re: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 15:35:55 -0000 In message: "Michael Scheidell" writes: : > -----Original Message----- : > From: Peter Jeremy [mailto:peterjeremy@optushome.com.au] : > Sent: Tuesday, July 25, 2006 4:00 AM : > To: Michael Scheidell : > Cc: freebsd-hackers@freebsd.org : > Subject: Re: FBSD 5.5 and software timers : > : > : > Basically, when you ask for a 200msec delay, the kernel : > sleeps until an absolute time. It looks like the handling of : > absolute time sleeps across time steps was changed. : > Unfortunately, both approaches are equally valid in different : > circumstances. : I agree : > : > >It fails within 1 second of getting these types of log : > entries: Jul 23 : > >15:03:42 audit18 ntpd[473]: time reset -2.497234 s Jul 23 16:03:56 : > >audit18 ntpd[473]: time reset +1.532401 s : > : > Rather than focussing on the changed sleep handling, I : > suggest you concentrate on fixing your clock: Your system : > clock should not be stepping. : > : Except: 20 different machines. Some IBM 300's with 2.0Ghz P4,s, 305 and : 306's with 2.8P4, some DELL 750's and 850's with 2.8p4 with HTT enabled. : : Even the 5.4 machines shows the bifurcating -1, +2, -2, +1 time resets, : but timers work more like I want them to. : : > I presume the servers are all stable (ie not stepping) and : > have a reasonably low delay. If so, I suspect your ntpd PLL : > has locked up. I've seen problems with some versions of ntpd : : 20 different machines? That would strongly imply a poor choice of upstream server. Followed closely by all the machines have the same timekeeping hardware that's misbehaving. Try different kern.timecounter.hardware settings to see if the problem goes away. Warner From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 15:50:43 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CDCC16A4E2 for ; Tue, 25 Jul 2006 15:50:43 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAD6A43D45 for ; Tue, 25 Jul 2006 15:50:42 +0000 (GMT) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.221] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id k6PFogjU063667; Tue, 25 Jul 2006 08:50:42 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <44C63DD2.9080705@freebsd.org> Date: Tue, 25 Jul 2006 08:50:42 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: scheidell@secnap.net References: <20060725.093429.-1648696470.imp@bsdimp.com> In-Reply-To: <20060725.093429.-1648696470.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 15:50:43 -0000 M. Warner Losh wrote: > In message: > "Michael Scheidell" writes: > : > I presume the servers are all stable (ie not stepping) and > : > have a reasonably low delay. If so, I suspect your ntpd PLL > : > has locked up. I've seen problems with some versions of ntpd > : > : 20 different machines? > > That would strongly imply a poor choice of upstream server. It might also help to set up 1 machine as your NTP master. Have it sync to the upstream servers and have the rest of your machines sync to it. This won't solve the problem, but might make it easier to solve (once your NTP master is stable, the rest should follow). You can experiment with different upstream servers, different network settings, different NTP settings, etc. Tim P.S. ntp docs outline the following as "best practice": Use 2 local machines as NTP masters, each syncing to a completely different set of upstream masters. The rest of your machines sync to both of your local masters. This is supposed to protect you against a wide variety of timekeeping failures. From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 17:10:58 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3041516A60B; Tue, 25 Jul 2006 17:10:58 +0000 (UTC) (envelope-from scheidell@secnap.net) Received: from mail.secnap.com (mail.secnap.com [204.89.241.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id D03BD43D45; Tue, 25 Jul 2006 17:10:57 +0000 (GMT) (envelope-from scheidell@secnap.net) Received: from [10.70.3.3] (unknown [10.70.3.3]) by mail.secnap.com (Postfix) with ESMTP id A15F1164838; Tue, 25 Jul 2006 13:10:56 -0400 (EDT) Message-ID: <44C6509E.4090708@secnap.net> Date: Tue, 25 Jul 2006 13:10:54 -0400 From: Michael Scheidell Organization: SECNAP Network Security User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530) MIME-Version: 1.0 To: Tim Kientzle References: <20060725.093429.-1648696470.imp@bsdimp.com> <44C63DD2.9080705@freebsd.org> In-Reply-To: <44C63DD2.9080705@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 17:10:58 -0000 Tim Kientzle wrote: > M. Warner Losh wrote: >> In message: >> "Michael Scheidell" writes: >> : > I presume the servers are all stable (ie not stepping) and : > >> have a reasonably low delay. If so, I suspect your ntpd PLL : > has >> locked up. I've seen problems with some versions of ntpd : : 20 >> different machines? >> >> That would strongly imply a poor choice of upstream server. > > It might also help to set up 1 machine as > your NTP master. Have it sync to the upstream > servers and have the rest of your machines > sync to it. This won't solve the problem, > but might make it easier to solve (once your > NTP master is stable, the rest should follow). > Except that all 20 are on different physical networks, one in a different content. I went back and looked at out 4.11 systems, and didn't see any 'time reset' errors. Internally, here at this physical location, we do have one master ntp server, pulling from (3) servers, not two. All internal systems then pull from this one master. > You can experiment with different upstream > servers, different network settings, different > NTP settings, etc. > only ntp setting that helped was the -x option (adjust once, slew 128m max each other time) One external box is now 30 seconds out of sync (after 24 hours) Again, ntp problem is one thing, but what about the nanosleep() issue? 5.4 worked fine, 5.5 has problems. Did something change in 5.5 with clock() or nanosleep()? Its not documented in the readme for 5.5. -- Michael Scheidell, CTO SECNAP Network Security / www.secnap.com scheidell@secnap.net / 1+561-999-5000, x 1131 From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 17:16:30 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0181B16A4DF for ; Tue, 25 Jul 2006 17:16:30 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 907D843D46 for ; Tue, 25 Jul 2006 17:16:28 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k6PHGQcr053181; Tue, 25 Jul 2006 12:16:27 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44C651F6.90504@centtech.com> Date: Tue, 25 Jul 2006 12:16:38 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.4 (X11/20060612) MIME-Version: 1.0 To: Coleman Kane References: <20060430231621.GA551@pint.candc.home> <44557F34.3020906@centtech.com> <20060501190645.GB4315@odin.ac.hmc.edu> <44565DD2.1020604@centtech.com> <20060501191447.GD4315@odin.ac.hmc.edu> <44565E74.3060801@centtech.com> <20060501192920.GE4315@odin.ac.hmc.edu> <20060501212801.GA2254@pint.candc.home> <44577B56.70704@centtech.com> <447497F8.10009@centtech.com> <20060525011232.GA14233@ramen.coleyandcheryl> <44761079.4080801@centtech.com> In-Reply-To: <44761079.4080801@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1618/Mon Jul 24 20:12:40 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 17:16:30 -0000 On 05/25/06 15:15, Eric Anderson wrote: > Coleman Kane wrote: >> On Wed, May 24, 2006 at 12:29:28PM -0500, Eric Anderson wrote, and it >> was proclaimed: >>> Eric Anderson wrote: >>>> Coleman Kane wrote: >>>>> On Mon, May 01, 2006 at 12:29:20PM -0700, Brooks Davis wrote: >>>>>> On Mon, May 01, 2006 at 02:16:04PM -0500, Eric Anderson wrote: >>>>>>> Brooks Davis wrote: >>>>>>>> On Mon, May 01, 2006 at 02:13:22PM -0500, Eric Anderson wrote: >>>>>>>>> Brooks Davis wrote: >>>>>>>>>> On Sun, Apr 30, 2006 at 10:23:32PM -0500, Eric Anderson wrote: >>>>>>>>>>> Coleman Kane wrote: >>>>>>>>>>>> On Mon, Apr 24, 2006 at 09:45:09AM -0500, Eric Anderson wrote: >>>>>>>>>>>>> Eric Anderson wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> Actually, some other things got changed somewhere in the >>>>>>>>>>>>> history, that broke some things and assumptions I was >>>>>>>>>>>>> making. This patch has them fixed, and I've tested it with >>>>>>>>>>>>> all the different options: >>>>>>>>>>>>> >>>>>>>>>>>>> http://www.googlebit.com/freebsd/patches/rc_fancy.patch-9 >>>>>>>>>>>>> >>>>>>>>>>>>> It's missing the defaults/rc.conf diffs, but you should >>>>>>>>>>>>> already know those. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Eric >>>>>>>>>>>>> >>>>>>>>>>>> I have a new patch (to 7-CURRENT) of the "fancy_rc" updates. >>>>>>>>>>>> >>>>>>>>>>>> This allows the use of: >>>>>>>>>>>> rc_fancy="YES" ---> Turns on fancy reporting (w/o >>>>>>>>>>>> color) >>>>>>>>>>>> rc_fancy_color="YES" ---> Turns on fancy reporting (w/ >>>>>>>>>>>> color), needs >>>>>>>>>>>> rc_fancy="YES" >>>>>>>>>>>> rc_fancy_colour="YES" ---> Same as above for you on the >>>>>>>>>>>> other side of >>>>>>>>>>>> the pond. >>>>>>>>>>>> rc_fancy_verbose="YES" --> Turn on more verbose activity >>>>>>>>>>>> messages. >>>>>>>>>>>> This will cause what appear to be >>>>>>>>>>>> "false >>>>>>>>>>>> positives", where an unused service is >>>>>>>>>>>> "OK" instead of "SKIP". >>>>>>>>>>>> >>>>>>>>>>>> You can also customize the colors, the widths of the message >>>>>>>>>>>> brackets (e.g. [ OK ] vs. [ OK ]), the screen width, and >>>>>>>>>>>> the contents of the message (OK versus GOOD versus BUENO). >>>>>>>>>>>> >>>>>>>>>>>> Also, we have the following message combinations: >>>>>>>>>>>> OK ---> Universal good message >>>>>>>>>>>> SKIP,SKIPPED ---> Two methods for conveying the same idea? >>>>>>>>>>>> ERROR,FAILED ---> Ditto above, for failure cases >>>>>>>>>>>> >>>>>>>>>>>> Should we just have 3 different messages, rather than 5 >>>>>>>>>>>> messages >>>>>>>>>>>> in 3 categories? >>>>>>>>>>> Yes, that's something that started with my first patch, and >>>>>>>>>>> never got ironed out. I think it should be: >>>>>>>>>>> OK >>>>>>>>>>> SKIPPED >>>>>>>>>>> FAILED >>>>>>>>>>> and possibly also: >>>>>>>>>>> ERROR >>>>>>>>>>> >>>>>>>>>>> The difference between FAILED and ERROR would be that FAILED >>>>>>>>>>> means the service did not start at all, and ERROR means it >>>>>>>>>>> started but had some kind of error response. >>>>>>>>>> FAILED vs ERROR seems confusing. I'd be inclined toward >>>>>>>>>> WARNING vs >>>>>>>>>> FAILED or ERROR. >>>>>>>>> True, however I still see a difference between FAILED and >>>>>>>>> WARNING. For instance, as an example: a FAILED RAID is >>>>>>>>> different than a RAID with a WARNING. >>>>>>>> For that level of detail, the ability to provide additional >>>>>>>> output seems >>>>>>>> like the appropriate solution. >>>>>>> Yes, true, but you'd still want to show something (I would think) >>>>>>> in the [ ]'s to keep it consistent. >>>>>> My feeling is that anything short of complete success should report >>>>>> WARNING and a message unless it actually totally failed in which case >>>>>> FAILED or ERROR (I slightly perfer ERROR) should be used. >>>>>> >>>>>> -- Brooks >>>>> What situations are we determining get flagged as ERROR versus FAILED? >>>>> Is FAILED considered to be 'I was able to run the command, but it >>>>> returned an error code', versus ERROR being 'I could not even run the >>>>> command!' like bad path, file not found, etc... >>>>> >>>>> This point still kind of confuses me (and needs to be well defined). I >>>>> am an advocate of having three distinct messages: OK, SKIPPED, ERROR. >>>>> And not even bothering with the different types of ERROR/FAILED other >>>>> than having extra reporting output. >>>> I'm ok with just OK, SKIPPED, ERROR.. If there's ever a need for >>>> more, it's easy to add it. >>>> >>>> Eric >>>> >>>> >>>> >>> >>> Is this still planned to make it into -CURRENT? >>> >>> Thanks, >>> Eric >>> >>> >>> -- >>> ------------------------------------------------------------------------ >>> Eric Anderson Sr. Systems Administrator Centaur Technology >>> Anything that works is better than anything that doesn't. >>> ------------------------------------------------------------------------ >> >> Yeah, I've been working on it in my spare time. I am investigating some >> avenues regarding status reporting from the rc scripts to the console. >> Also been slow getting some hardware together to put cokane.org back up >> and online. >> >> Mostly real-life just got in the way of freebsd for a little while. >> >> -- >> coleman kane > > > Ok - just making sure it had not been forgotten. :) > > Thanks Coleman! > > Eric > > Any progress on this? Maybe another committer could take a look at it if you are too busy? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 19:27:55 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80A7A16A4DE for ; Tue, 25 Jul 2006 19:27:55 +0000 (UTC) (envelope-from scheidell@secnap.net) Received: from mail.secnap.com (mail.secnap.com [204.89.241.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32E2843D53 for ; Tue, 25 Jul 2006 19:27:55 +0000 (GMT) (envelope-from scheidell@secnap.net) Received: from [10.70.3.3] (unknown [10.70.3.3]) by mail.secnap.com (Postfix) with ESMTP id 49923164838; Tue, 25 Jul 2006 15:27:54 -0400 (EDT) Message-ID: <44C670BA.6060608@secnap.net> Date: Tue, 25 Jul 2006 15:27:54 -0400 From: Michael Scheidell Organization: SECNAP Network Security User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <20060725.093429.-1648696470.imp@bsdimp.com> <44C63DD2.9080705@freebsd.org> <44C6509E.4090708@secnap.net> In-Reply-To: <44C6509E.4090708@secnap.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 19:27:55 -0000 Found it! library libc_r Given POC: int main( int argc, char **argv ) { char execs1[256] = "/bin/date +A%Y%m%d%H%M.%S"; char execs2[256] = "/bin/date +B%Y%m%d%H%M.%S"; int a; while ( 1) { system( execs1 ); usleep( 500*1000); system( execs2 ); } return 0; } /* main */ compile with: cc -g -c nanotest.c cc -g -o nanotest nanotest.o everything works as expected. time forward, back, doesn't matter (date prints out wallclock, nanosleep() sleeps 500*1000*1000us (.5 seconds) this breaks it: cc -g -c nanotest.c cc -g -o nanotest nanotest.o -lc_r setting clock back 'hangs' during usleep (500*1000) didn't hang on 5.4. I will be writing up a bug report shortly. -- Michael Scheidell, CTO SECNAP Network Security / www.secnap.com scheidell@secnap.net / 1+561-999-5000, x 1131 From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 19:30:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8B6616A4DE for ; Tue, 25 Jul 2006 19:30:41 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out3.blueyonder.co.uk (smtp-out3.blueyonder.co.uk [195.188.213.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76E4543D46 for ; Tue, 25 Jul 2006 19:30:40 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.144] (helo=anti-virus03-07) by smtp-out3.blueyonder.co.uk with smtp (Exim 4.52) id 1G5Sc3-0000qp-5p; Tue, 25 Jul 2006 20:30:39 +0100 Received: from [82.41.33.125] (helo=[192.168.0.2]) by asmtp-out6.blueyonder.co.uk with esmtp (Exim 4.52) id 1G5Sc2-0000kB-L6; Tue, 25 Jul 2006 20:30:38 +0100 Message-ID: <44C6715E.3090904@dial.pipex.com> Date: Tue, 25 Jul 2006 20:30:38 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20060515 X-Accept-Language: en MIME-Version: 1.0 To: John Polstra References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: [Fwd: Interrupts question] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 19:30:41 -0000 John Polstra wrote: >The problem involving the "em" device was solved in -current around >January by making the device use a fast interrupt handler. If you >can update to the latest driver from -current (if it will build on >whatever version you are running), you can solve that part of the >problem. I don't think there's an equivalent fix for the "amr" >driver, though. > > Thanks for the info. When we finally upgrade to 6.1 I can see if the -current driver will work and what difference it makes. --Alex From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 19:31:54 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22BFD16A4DE for ; Tue, 25 Jul 2006 19:31:54 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out3.blueyonder.co.uk (smtp-out3.blueyonder.co.uk [195.188.213.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD9FC43D6E for ; Tue, 25 Jul 2006 19:31:53 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.144] (helo=anti-virus03-07) by smtp-out3.blueyonder.co.uk with smtp (Exim 4.52) id 1G5SdF-0001Je-3P; Tue, 25 Jul 2006 20:31:53 +0100 Received: from [82.41.33.125] (helo=[192.168.0.2]) by asmtp-out5.blueyonder.co.uk with esmtp (Exim 4.52) id 1G5SdE-0001Z6-1k; Tue, 25 Jul 2006 20:31:52 +0100 Message-ID: <44C671A8.7090005@dial.pipex.com> Date: Tue, 25 Jul 2006 20:31:52 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20060515 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG References: <200607201114.k6KBELal089267@lurza.secnetix.de> In-Reply-To: <200607201114.k6KBELal089267@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: [Fwd: Interrupts question] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 19:31:54 -0000 Oliver Fromme wrote: > > > > Thanks for the suggestion. Can you tell me how to disable specific > > controllers? Were you thinking BIOS? or FreeBSD? > >I meant to say to disable them in the BIOS. I'm afraid >there is no generic way to disable specific devices in >FreeBSD anymore. > > That's what I thought, thanks. I'll have a look at the BIOS next time I can reboot and see what can set turned off. --Alex From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 19:58:40 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C9D716A4E7; Tue, 25 Jul 2006 19:58:40 +0000 (UTC) (envelope-from scheidell@secnap.net) Received: from scanner.secnap.net (scanner.secnap.net [204.89.241.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BC2D43D46; Tue, 25 Jul 2006 19:58:40 +0000 (GMT) (envelope-from scheidell@secnap.net) Received: by scanner.secnap.net (Postfix, from userid 1001) id 4E5CF137BB7; Tue, 25 Jul 2006 15:58:39 -0400 (EDT) To: FreeBSD-gnats-submit@freebsd.org From: Michael Scheidell X-send-pr-version: 3.113 X-GNATS-Notify: Message-Id: <20060725195839.4E5CF137BB7@scanner.secnap.net> Date: Tue, 25 Jul 2006 15:58:39 -0400 (EDT) Cc: freebsd-hackers@freebsd.org Subject: FBSD 5.5 broke nanosleep in libc_r X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 19:58:40 -0000 >Submitter-Id: current-users >Originator: Michael Scheidel >Organization: SECNAP Network Security >Confidential: >Synopsis: FBSD 5.5 broke nanosleep in libc_r >Severity: serious >Priority: medium >Category: threads >Class: sw-bug >Release: FreeBSD 5.5-RELEASE-p2 i386 >Environment: System: FreeBSD audit18.hackertrap.net 5.5-RELEASE-p2 FreeBSD 5.5-RELEASE-p2 #6: Tue Jul 25 10:34:16 EDT 2006 admin@audit18.hackertrap.net:/usr/obj/usr/src/sys/HACKERTRAP_305 i386 >Description: nanosleep returns after time+delta if wallclock changed with libc_r >How-To-Repeat: 5.4 works, not including libc_r in 5.5 works Given this POC: int main( int argc, char **argv ) { char execs1[256] = "/bin/date +A%Y%m%d%H%M.%S"; char execs2[256] = "/bin/date +B%Y%m%d%H%M.%S"; int a; while ( 1) { system( execs1 ); usleep( 500*1000); system( execs2 ); } return 0; } /* main */ compile with: cc -g -c nanotest.c cc -g -o nanotest nanotest.o -lc_r run it, set clock back 45 seconds, observe 45 second delay >Fix: compile with: cc -g -c nanotest.c cc -g -o nanotest nanotest.o or compile on 5.4 system. (I have only tried compiling and running on 5.4 system. I have not yet tried compiling on 5.4 and running on 5.5 or visa versa) I used ntpdate -su to change clock. (I have an internal system that is 45 seconds behind, just for this test) output with 5.4 or without libc_r shows wallclock 'stepping' when you change time no delay in display. 5.5 with libc_r shows stepping if moving clock head, but if you move wallclock back 45 seconds, display stops for 45 seconds. From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 25 20:24:57 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B978416A4F1 for ; Tue, 25 Jul 2006 20:24:57 +0000 (UTC) (envelope-from nielsen-list@memberwebs.com) Received: from mail.npubs.com (mail.npubs.com [209.66.100.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94BA843D45 for ; Tue, 25 Jul 2006 20:24:57 +0000 (GMT) (envelope-from nielsen-list@memberwebs.com) From: Nate Nielsen User-Agent: Thunderbird 1.5.0.4 (X11/20060615) MIME-Version: 1.0 To: Dirk Engling References: <20060724192149.O46542@erdgeist.org> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20060725202456.670E9DCBD8A@mail.npubs.com> X-Virus-Scanned: ClamAV using ClamSMTP Date: Tue, 25 Jul 2006 20:24:57 +0000 (GMT) Cc: freebsd-hackers@freebsd.org, ezjail@erdgeist.org Subject: Re: Rebooting jails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: nielsen@memberwebs.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 20:24:57 -0000 'jailer' can do this but it requires a process running in each jail. http://memberwebs.com/nielsen/freebsd/jails/ Cheers, Nate Dirk Engling wrote: > I'm currently looking for a standardized way to 'reboot' jails from > within. From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 26 07:50:18 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9698116A4DE for ; Wed, 26 Jul 2006 07:50:18 +0000 (UTC) (envelope-from shangjie.li@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id D972643D49 for ; Wed, 26 Jul 2006 07:50:17 +0000 (GMT) (envelope-from shangjie.li@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so3205793uge for ; Wed, 26 Jul 2006 00:50:16 -0700 (PDT) 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=EnYPkH/YLtlsYChqYmtv1Z5byeelQ/L9sq97vD5iP6cRNIfP64OJL2s1IhbdfRBodIf7QC9lmJltUDdXHPu+cFNOytV3gkEUWAP3xBHL9wU23N51Z5vy8CLsfEjghoUASAO7Ua/1kW/HkPkE7f5lgGNkd+QJj8AaPUXgZgk8tj4= Received: by 10.78.165.16 with SMTP id n16mr2909978hue; Wed, 26 Jul 2006 00:50:16 -0700 (PDT) Received: by 10.78.127.20 with HTTP; Wed, 26 Jul 2006 00:50:16 -0700 (PDT) Message-ID: Date: Wed, 26 Jul 2006 15:50:16 +0800 From: "=?GB2312?B?wO7J0L3c?=" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: A bug in semctl() X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jul 2006 07:50:18 -0000 In file kern/sysv_sem.c: 554 __semctl(td, uap) 555 struct thread *td; 556 struct __semctl_args *uap; 557 { 558 int semid = uap->semid; <<semnum; 560 int cmd = uap->cmd; 561 u_short *array; 562 union semun *arg = uap->arg; 563 union semun real_arg; 564 struct ucred *cred = td->td_ucred; 565 int i, rval, error; 566 struct semid_ds sbuf; 567 struct semid_kernel *semakptr; 568 struct mtx *sema_mtxp; 569 u_short usval, count; 570 571 DPRINTF(("call to semctl(%d, %d, %d, 0x%x)\n", 572 semid, semnum, cmd, arg)); 573 if (!jail_sysvipc_allowed && jailed(td->td_ucred)) 574 return (ENOSYS); 575 576 array = NULL; 577 578 switch(cmd) { 579 case SEM_STAT: 580 if (semid < 0 || semid >= seminfo.semmni) <<From line 558 to line 578, there must be a mechism to convert the sem_id to the internal sema array index. In fact, it was missing, which make the semctl syscall not work well. -- -- |Best regards. |Shangjie, Li (Ph.D candidate) |Institute of Software, Chinese Academy of Sciences, |P.O. Box 8718, Beijing 100080, CHINA |Phone: (8610)62561197/62635158-1008(O), 82680528(H) |Email: shangjie02@ios.cn >---------------------------------------------------< From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 26 07:59:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD64B16A4E1 for ; Wed, 26 Jul 2006 07:59:35 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CAC743D53 for ; Wed, 26 Jul 2006 07:59:34 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost.int.ru [127.0.0.1] (may be forged)) by mp2.macomnet.net (8.13.7/8.13.3) with ESMTP id k6Q7xXml022629; Wed, 26 Jul 2006 11:59:33 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Wed, 26 Jul 2006 11:59:32 +0400 (MSD) From: Maxim Konovalov To: =?GB2312?B?wO7J0L3c?= In-Reply-To: Message-ID: <20060726115840.K62591@mp2.macomnet.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Cc: freebsd-hackers@freebsd.org Subject: Re: A bug in semctl() X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jul 2006 07:59:35 -0000 On Wed, 26 Jul 2006, 15:50+0800, ÀîÉÐ½Ü wrote: > In file kern/sysv_sem.c: > 554 __semctl(td, uap) > 555 struct thread *td; > 556 struct __semctl_args *uap; > 557 { > 558 int semid = uap->semid; << 559 int semnum = uap->semnum; > 560 int cmd = uap->cmd; > 561 u_short *array; > 562 union semun *arg = uap->arg; > 563 union semun real_arg; > 564 struct ucred *cred = td->td_ucred; > 565 int i, rval, error; > 566 struct semid_ds sbuf; > 567 struct semid_kernel *semakptr; > 568 struct mtx *sema_mtxp; > 569 u_short usval, count; > 570 > 571 DPRINTF(("call to semctl(%d, %d, %d, 0x%x)\n", > 572 semid, semnum, cmd, arg)); > 573 if (!jail_sysvipc_allowed && jailed(td->td_ucred)) > 574 return (ENOSYS); > 575 > 576 array = NULL; > 577 > 578 switch(cmd) { > 579 case SEM_STAT: > 580 if (semid < 0 || semid >= seminfo.semmni) << 581 return (EINVAL); > 582 if ((error = copyin(arg, &real_arg, sizeof(real_arg))) != > 0) > 583 return (error); > 584 semakptr = &sema[semid];<< > >From line 558 to line 578, there must be a mechism to convert the > sem_id to the internal sema array index. In fact, it was missing, > which make the semctl syscall not work well. What version of the file do you read? We have a different code in HEAD. -- Maxim Konovalov From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 26 08:27:08 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4282016A4DE for ; Wed, 26 Jul 2006 08:27:08 +0000 (UTC) (envelope-from shangjie.li@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E53E43D5D for ; Wed, 26 Jul 2006 08:27:07 +0000 (GMT) (envelope-from shangjie.li@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so3215492uge for ; Wed, 26 Jul 2006 01:27:06 -0700 (PDT) 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=CQZl4wB1q7zagFRx2DwJ8N7XWHpnwDvmnMUl0K/6yzGHZu6mq8Ov2ldxmS7XLna9dfMvW4LBvV59uPPJLGhoYcQVr0HeGrK4yUnzLTX+4dQZf/ZfHBvRF6tFde21i1fufURHUWZY+GoiTPsY9bAA2O/L7HNgoW8uPDqufSQmIoE= Received: by 10.78.177.3 with SMTP id z3mr2916875hue; Wed, 26 Jul 2006 01:27:06 -0700 (PDT) Received: by 10.78.127.20 with HTTP; Wed, 26 Jul 2006 01:27:06 -0700 (PDT) Message-ID: Date: Wed, 26 Jul 2006 16:27:06 +0800 From: "=?GB2312?B?wO7J0L3c?=" To: "Maxim Konovalov" , freebsd-hackers@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=GB2312; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline References: <20060726115840.K62591@mp2.macomnet.net> Cc: Subject: Re: A bug in semctl() X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jul 2006 08:27:08 -0000 U29ycnkhIEkgYW0gd29ya2luZyBGQi82LjAuIEJ1dCBJIGhhdmUgY2hlY2tlZCB0aGUgNi4xIGNv ZGUsIHRoaXMKcHJvbGJlbSBleGlzdHMgdG9vLgppbiBfX3NlbWN0bCgpOgoJCWVycm9yID0ga2Vy bl9zZW1jdGwodGQsIHVhcC0+c2VtaWQsIHVhcC0+c2VtbnVtLCB1YXAtPmNtZCwgJnNlbXVuLAoJ ICAgICZydmFsKTsKCmJ1dCBpbiBrZXJuX3NlbWN0bCgpIHRoZXJlIGlzIG5vIGNvbnZlcnRpb24K CtTaIDA2LTctMjajrMDuydC93DxzaGFuZ2ppZS5saUBnbWFpbC5jb20+INC0tcCjugo+IEZyZWVi c2QvNi4xIGtlcm5lbCBjb2RlCj4KPiAyMDA2LzcvMjYsIE1heGltIEtvbm92YWxvdiA8bWF4aW1A bWFjb21uZXQucnU+Ogo+ID4gT24gV2VkLCAyNiBKdWwgMjAwNiwgMTU6NTArMDgwMCwgp/Cnr6fa p+Gob6fvIHdyb3RlOgo+ID4KPiA+ID4gSW4gZmlsZSBrZXJuL3N5c3Zfc2VtLmM6Cj4gPiA+IDU1 NCBfX3NlbWN0bCh0ZCwgdWFwKQo+ID4gPiA1NTUgICAgICAgICBzdHJ1Y3QgdGhyZWFkICp0ZDsK PiA+ID4gNTU2ICAgICAgICAgc3RydWN0IF9fc2VtY3RsX2FyZ3MgKnVhcDsKPiA+ID4gNTU3IHsK PiA+ID4gNTU4ICAgICAgICAgaW50IHNlbWlkID0gdWFwLT5zZW1pZDsgPDw8aGVyZSAxCj4gPiA+ IDU1OSAgICAgICAgIGludCBzZW1udW0gPSB1YXAtPnNlbW51bTsKPiA+ID4gNTYwICAgICAgICAg aW50IGNtZCA9IHVhcC0+Y21kOwo+ID4gPiA1NjEgICAgICAgICB1X3Nob3J0ICphcnJheTsKPiA+ ID4gNTYyICAgICAgICAgdW5pb24gc2VtdW4gKmFyZyA9IHVhcC0+YXJnOwo+ID4gPiA1NjMgICAg ICAgICB1bmlvbiBzZW11biByZWFsX2FyZzsKPiA+ID4gNTY0ICAgICAgICAgc3RydWN0IHVjcmVk ICpjcmVkID0gdGQtPnRkX3VjcmVkOwo+ID4gPiA1NjUgICAgICAgICBpbnQgaSwgcnZhbCwgZXJy b3I7Cj4gPiA+IDU2NiAgICAgICAgIHN0cnVjdCBzZW1pZF9kcyBzYnVmOwo+ID4gPiA1NjcgICAg ICAgICBzdHJ1Y3Qgc2VtaWRfa2VybmVsICpzZW1ha3B0cjsKPiA+ID4gNTY4ICAgICAgICAgc3Ry dWN0IG10eCAqc2VtYV9tdHhwOwo+ID4gPiA1NjkgICAgICAgICB1X3Nob3J0IHVzdmFsLCBjb3Vu dDsKPiA+ID4gNTcwCj4gPiA+IDU3MSAgICAgICAgIERQUklOVEYoKCJjYWxsIHRvIHNlbWN0bCgl ZCwgJWQsICVkLCAweCV4KVxuIiwKPiA+ID4gNTcyICAgICAgICAgICAgIHNlbWlkLCBzZW1udW0s IGNtZCwgYXJnKSk7Cj4gPiA+IDU3MyAgICAgICAgIGlmICghamFpbF9zeXN2aXBjX2FsbG93ZWQg JiYgamFpbGVkKHRkLT50ZF91Y3JlZCkpCj4gPiA+IDU3NCAgICAgICAgICAgICAgICAgcmV0dXJu IChFTk9TWVMpOwo+ID4gPiA1NzUKPiA+ID4gNTc2ICAgICAgICAgYXJyYXkgPSBOVUxMOwo+ID4g PiA1NzcKPiA+ID4gNTc4ICAgICAgICAgc3dpdGNoKGNtZCkgewo+ID4gPiA1NzkgICAgICAgICBj YXNlIFNFTV9TVEFUOgo+ID4gPiA1ODAgICAgICAgICAgICAgICAgIGlmIChzZW1pZCA8IDAgfHwg c2VtaWQgPj0gc2VtaW5mby5zZW1tbmkpIDw8PGhlcmUgMgo+ID4gPiA1ODEgICAgICAgICAgICAg ICAgICAgICAgICAgcmV0dXJuIChFSU5WQUwpOwo+ID4gPiA1ODIgICAgICAgICAgICAgICAgIGlm ICgoZXJyb3IgPSBjb3B5aW4oYXJnLCAmcmVhbF9hcmcsIHNpemVvZihyZWFsX2FyZykpKSAhPQo+ ID4gPiAwKQo+ID4gPiA1ODMgICAgICAgICAgICAgICAgICAgICAgICAgcmV0dXJuIChlcnJvcik7 Cj4gPiA+IDU4NCAgICAgICAgICAgICAgICAgc2VtYWtwdHIgPSAmc2VtYVtzZW1pZF07PDw8aGVy ZSAzCj4gPiA+Cj4gPiA+ID5Gcm9tIGxpbmUgNTU4IHRvIGxpbmUgNTc4LCB0aGVyZSBtdXN0IGJl IGEgbWVjaGlzbSB0byBjb252ZXJ0IHRoZQo+ID4gPiBzZW1faWQgdG8gdGhlIGludGVybmFsIHNl bWEgYXJyYXkgaW5kZXguIEluIGZhY3QsIGl0IHdhcyBtaXNzaW5nLAo+ID4gPiB3aGljaCBtYWtl IHRoZSBzZW1jdGwgc3lzY2FsbCBub3Qgd29yayB3ZWxsLgo+ID4KPiA+IFdoYXQgdmVyc2lvbiBv ZiB0aGUgZmlsZSBkbyB5b3UgcmVhZD8gIFdlIGhhdmUgYSBkaWZmZXJlbnQgY29kZSBpbgo+ID4g SEVBRC4KPiA+Cj4gPiAtLQo+ID4gTWF4aW0gS29ub3ZhbG92Cj4gPgo+Cj4KPiAtLQo+IC0tCj4g fEJlc3QgcmVnYXJkcy4KPiB8U2hhbmdqaWUsIExpIChQaC5EIGNhbmRpZGF0ZSkKPiB8SW5zdGl0 dXRlIG9mIFNvZnR3YXJlLCBDaGluZXNlIEFjYWRlbXkgb2YgU2NpZW5jZXMsCj4gfFAuTy4gQm94 IDg3MTgsIEJlaWppbmcgMTAwMDgwLCBDSElOQQo+IHxQaG9uZTogKDg2MTApNjI1NjExOTcvNjI2 MzUxNTgtMTAwOChPKSwgODI2ODA1MjgoSCkKPiB8RW1haWw6IHNoYW5namllMDJAaW9zLmNuCj4g Pi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTwKPgoK Ci0tIAotLQp8QmVzdCByZWdhcmRzLgp8U2hhbmdqaWUsIExpIChQaC5EIGNhbmRpZGF0ZSkKfElu c3RpdHV0ZSBvZiBTb2Z0d2FyZSwgQ2hpbmVzZSBBY2FkZW15IG9mIFNjaWVuY2VzLAp8UC5PLiBC b3ggODcxOCwgQmVpamluZyAxMDAwODAsIENISU5BCnxQaG9uZTogKDg2MTApNjI1NjExOTcvNjI2 MzUxNTgtMTAwOChPKSwgODI2ODA1MjgoSCkKfEVtYWlsOiBzaGFuZ2ppZTAyQGlvcy5jbgo+LS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPAo= From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 26 11:21:58 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 671EF16A4DE for ; Wed, 26 Jul 2006 11:21:58 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.ipactive.de [85.214.39.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AACB43D7C for ; Wed, 26 Jul 2006 11:21:54 +0000 (GMT) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (gprs-pool-1-008.eplus-online.de [212.23.126.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 6CAB233D17 for ; Wed, 26 Jul 2006 13:21:50 +0200 (CEST) Received: from [127.0.0.1] (cesar.sz.vwsoft.com [192.168.16.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id C2DC62E52B for ; Wed, 26 Jul 2006 13:21:36 +0200 (CEST) Message-ID: <44C75054.6080009@vwsoft.com> Date: Wed, 26 Jul 2006 13:21:56 +0200 From: Volker User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: hackers@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: Subject: puc question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jul 2006 11:21:58 -0000 Hi hackers, I've found the following message in /usr/src/UPDATING: > 20060428: > The puc(4) driver has been overhauled. The ebus(4) and sbus(4) > attachments have been removed. Make sure to configure scc(4) > on sparc64. Note also that by default puc(4) will use uart(4) > and not sio(4) for serial ports because interrupt handling has > been optimized for multi-port serial cards and only uart(4) > implements the interface to support it. Does the puc driver now obsoletes sio as it's going to use uart instead? I've found nothing in the commit message for puc.c 1.47 in the cvs. The GENERIC kernel config still has device sio in it and device puc is still commented out by default. I'm wondering about puc because sio deals badly with higher baud rates (kern/51982) and the UPDATING message and puc might be a solution for that. I'm currently rebuilding world and a sio-free kernel to check that out. Greetings, Volker From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 26 11:28:44 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3290D16A4DA for ; Wed, 26 Jul 2006 11:28:44 +0000 (UTC) (envelope-from murat@enderunix.org) Received: from istanbul.enderunix.org (freefall.marmara.edu.tr [193.140.143.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4ECB643D49 for ; Wed, 26 Jul 2006 11:28:43 +0000 (GMT) (envelope-from murat@enderunix.org) Received: (qmail 22416 invoked by uid 1002); 26 Jul 2006 11:16:57 -0000 Date: Wed, 26 Jul 2006 14:16:57 +0300 From: Murat Balaban To: freebsd-hackers@freebsd.org Message-ID: <20060726111657.GA22358@enderunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: sys/dev/em/if_em.c X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jul 2006 11:28:44 -0000 Hello hackers, I have a special-purpose setting where I have a ng_hub like kernel module (ng_lb) which I've been coding. The box I'm using has two em(4) adapters, and I've hooked em0's lower with my ng_lb's link0, and em1's lower with ng_lb's link1. Situation looks like this: lower link0 link1 lower em0 ---------------> -------------> ng_lb --------------> ---------------> em1 Every packet that is received by em0 is handed over to my netgraph module and after very little modification in the packet ethernet header (changing destination mac addresss) I NG_FWD_ITEM() the packet to em1. I'm generating traffic with a packet generator, and em0 seems to be ok with around 910 Mbit/s traffic. However if I write the packets into em1, em1 seems to drop 40-60 Mbit/s (of 910 Mbit/s) data. I digged the problem a bit, and found out that, IFQ_HANDOFF, called deep inside from NG_FWD_ITEM was returning ENOBUFS. A little more investigation proved me that the source of ENOBUFS error was that the em1 was running out of Tx descriptors. The relative logic in dev/em/if_em.c (em_encap) was that if # of Tx descriptors falls below a threshold, the driver tries to clean transmit interrupts once. # of available Tx desc. is again checked and if the number is still not incresed ENOBUFS error is returned. What I'd like to ask is, instead of cleaning the transmit interrupts only once, why not do it many times till the number of available tx descriptors increases to a moderate level? The following patch solved my problem, though I wanted to get your opinions about it. Cheers, Murat http://www.enderunix.org/murat/ PS: Both cards are plugged into a 64-bit 66 Mhz PCI-X bus. I've polling enabled in both interfaces, and HZ set to 10000. --- if_em_murat.c Wed Jul 26 13:59:22 2006 +++ if_em.c Wed Jul 26 14:01:11 2006 @@ -1177,11 +1177,9 @@ * available hits the threshold */ if (adapter->num_tx_desc_avail <= EM_TX_CLEANUP_THRESHOLD) { - em_clean_transmit_interrupts(adapter); - if (adapter->num_tx_desc_avail <= EM_TX_CLEANUP_THRESHOLD) { - adapter->no_tx_desc_avail1++; - return(ENOBUFS); - } + do { + em_clean_transmit_interrupts(adapter); + while (adapter->num_tx_desc_avail <= EM_TX_CLEANUP_THRESHOLD); } /* From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 26 11:35:52 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99BEF16A4E1 for ; Wed, 26 Jul 2006 11:35:52 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38E2243D58 for ; Wed, 26 Jul 2006 11:35:50 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k6QBZkcM027143; Wed, 26 Jul 2006 06:35:46 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44C7539E.5060804@centtech.com> Date: Wed, 26 Jul 2006 06:35:58 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.4 (X11/20060612) MIME-Version: 1.0 To: Murat Balaban References: <20060726111657.GA22358@enderunix.org> In-Reply-To: <20060726111657.GA22358@enderunix.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1621/Wed Jul 26 01:13:01 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: sys/dev/em/if_em.c X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jul 2006 11:35:52 -0000 On 07/26/06 06:16, Murat Balaban wrote: > Hello hackers, > > I have a special-purpose setting where I have a ng_hub like kernel module (ng_lb) > which I've been coding. The box I'm using has two em(4) adapters, and I've > hooked em0's lower with my ng_lb's link0, and em1's lower with ng_lb's link1. > > Situation looks like this: > > lower link0 link1 lower > em0 ---------------> -------------> ng_lb --------------> ---------------> em1 > > Every packet that is received by em0 is handed over to my netgraph module and > after very little modification in the packet ethernet header (changing destination > mac addresss) I NG_FWD_ITEM() the packet to em1. > > I'm generating traffic with a packet generator, and em0 seems to be ok with around > 910 Mbit/s traffic. > > However if I write the packets into em1, em1 seems to drop 40-60 Mbit/s (of 910 Mbit/s) > data. I digged the problem a bit, and found out that, IFQ_HANDOFF, called deep inside > from NG_FWD_ITEM was returning ENOBUFS. > > A little more investigation proved me that the source of ENOBUFS error was that > the em1 was running out of Tx descriptors. The relative logic in dev/em/if_em.c > (em_encap) was that if # of Tx descriptors falls below a threshold, the driver > tries to clean transmit interrupts once. # of available Tx desc. is again checked > and if the number is still not incresed ENOBUFS error is returned. > > What I'd like to ask is, instead of cleaning the transmit interrupts only once, > why not do it many times till the number of available tx descriptors increases > to a moderate level? > > The following patch solved my problem, though I wanted to get your opinions about > it. What if adapter->num_tx_desc_avail never gets above EM_TX_CLEANUP_THRESHOLD ? Maybe adding another check (max loop counter) or something? > --- if_em_murat.c Wed Jul 26 13:59:22 2006 > +++ if_em.c Wed Jul 26 14:01:11 2006 > @@ -1177,11 +1177,9 @@ > * available hits the threshold > */ > if (adapter->num_tx_desc_avail <= EM_TX_CLEANUP_THRESHOLD) { > - em_clean_transmit_interrupts(adapter); > - if (adapter->num_tx_desc_avail <= EM_TX_CLEANUP_THRESHOLD) { > - adapter->no_tx_desc_avail1++; > - return(ENOBUFS); > - } > + do { > + em_clean_transmit_interrupts(adapter); > + while (adapter->num_tx_desc_avail <= EM_TX_CLEANUP_THRESHOLD); > } > > /* Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 26 17:38:57 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B89D16A4DE for ; Wed, 26 Jul 2006 17:38:57 +0000 (UTC) (envelope-from dgilbert@daveg.ca) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0FC243D5D for ; Wed, 26 Jul 2006 17:38:54 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 0F4991E94C; Wed, 26 Jul 2006 13:38:54 -0400 (EDT) Received: by canoe.dclg.ca (Postfix, from userid 101) id 365E84AC2B; Wed, 26 Jul 2006 13:37:51 -0400 (EDT) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17607.43119.173769.26690@canoe.dclg.ca> Date: Wed, 26 Jul 2006 13:37:51 -0400 To: Alexander Leidinger In-Reply-To: <20060725111247.646lw5dhsgcso48o@netchild.homeip.net> References: <17605.7478.194820.171800@canoe.dclg.ca> <20060724213642.GQ96589@funkthat.com> <20060725111247.646lw5dhsgcso48o@netchild.homeip.net> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid Cc: freebsd-hackers@freebsd.org, John-Mark Gurney , David Gilbert Subject: Re: kqueue doesn't see if_tun X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jul 2006 17:38:57 -0000 >>>>> "Alexander" == Alexander Leidinger writes: Alexander> Quoting John-Mark Gurney Alexander> (from Mon, 24 Jul 2006 14:36:42 -0700): >> No one has written a d_kqfilter entry for tun... so, until someone >> does, kqueue will not work on tun... Alexander> Would you please come up with an entry for our ideas list Alexander> (http://www.freebsd.org/projects/ideas/) for identifying Alexander> pieces where kqueue support is missing and adding Alexander> appropriate support? Something similar to existing entries Alexander> or better (the more is explained, the higher the Alexander> probability that someone tries to do it). A plain text Alexander> version would be enough. If someone would apply the patch in kern/100796, there's at least one less place. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 26 19:03:22 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6479116A4DA for ; Wed, 26 Jul 2006 19:03:22 +0000 (UTC) (envelope-from prvs=julian=355ecf7dd@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2274043DC0 for ; Wed, 26 Jul 2006 19:02:50 +0000 (GMT) (envelope-from prvs=julian=355ecf7dd@elischer.org) Received: from unknown (HELO [10.251.18.229]) ([10.251.18.229]) by a50.ironport.com with ESMTP; 26 Jul 2006 12:02:45 -0700 Message-ID: <44C7BC55.6010703@elischer.org> Date: Wed, 26 Jul 2006 12:02:45 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Murat Balaban References: <20060726111657.GA22358@enderunix.org> In-Reply-To: <20060726111657.GA22358@enderunix.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: sys/dev/em/if_em.c X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jul 2006 19:03:22 -0000 Murat Balaban wrote: >Hello hackers, > >I have a special-purpose setting where I have a ng_hub like kernel module (ng_lb) >which I've been coding. The box I'm using has two em(4) adapters, and I've >hooked em0's lower with my ng_lb's link0, and em1's lower with ng_lb's link1. > >Situation looks like this: > > lower link0 link1 lower >em0 ---------------> -------------> ng_lb --------------> ---------------> em1 > >Every packet that is received by em0 is handed over to my netgraph module and >after very little modification in the packet ethernet header (changing destination >mac addresss) I NG_FWD_ITEM() the packet to em1. > > somewhat similar to what ng_bridge does. >I'm generating traffic with a packet generator, and em0 seems to be ok with around >910 Mbit/s traffic. > >However if I write the packets into em1, em1 seems to drop 40-60 Mbit/s (of 910 Mbit/s) >data. I digged the problem a bit, and found out that, IFQ_HANDOFF, called deep inside >from NG_FWD_ITEM was returning ENOBUFS. > >A little more investigation proved me that the source of ENOBUFS error was that >the em1 was running out of Tx descriptors. The relative logic in dev/em/if_em.c >(em_encap) was that if # of Tx descriptors falls below a threshold, the driver >tries to clean transmit interrupts once. # of available Tx desc. is again checked >and if the number is still not incresed ENOBUFS error is returned. > >What I'd like to ask is, instead of cleaning the transmit interrupts only once, >why not do it many times till the number of available tx descriptors increases >to a moderate level? > >The following patch solved my problem, though I wanted to get your opinions about >it. > >Cheers, >Murat >http://www.enderunix.org/murat/ > >PS: Both cards are plugged into a 64-bit 66 Mhz PCI-X bus. I've polling enabled >in both interfaces, and HZ set to 10000. > > >--- if_em_murat.c Wed Jul 26 13:59:22 2006 >+++ if_em.c Wed Jul 26 14:01:11 2006 >@@ -1177,11 +1177,9 @@ > * available hits the threshold > */ > if (adapter->num_tx_desc_avail <= EM_TX_CLEANUP_THRESHOLD) { >- em_clean_transmit_interrupts(adapter); >- if (adapter->num_tx_desc_avail <= EM_TX_CLEANUP_THRESHOLD) { >- adapter->no_tx_desc_avail1++; >- return(ENOBUFS); >- } >+ do { >+ em_clean_transmit_interrupts(adapter); >+ while (adapter->num_tx_desc_avail <= EM_TX_CLEANUP_THRESHOLD); > } > > > please have some limit to the number of times that the loop can be run.. maybe 20 or something. (and maybe something to note that it has hit that limit). > /* >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 02:51:36 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D840116A4DE for ; Thu, 27 Jul 2006 02:51:36 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6999A43D4C for ; Thu, 27 Jul 2006 02:51:35 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.24] (andersonbox4.centtech.com [192.168.42.24]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k6R2pWTQ073968 for ; Wed, 26 Jul 2006 21:51:34 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44C82A40.3020009@centtech.com> Date: Wed, 26 Jul 2006 21:51:44 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.4 (X11/20060612) MIME-Version: 1.0 To: FreeBSD Hackers Content-Type: multipart/mixed; boundary="------------020206000205090101090104" X-Virus-Scanned: ClamAV 0.87.1/1623/Wed Jul 26 17:35:11 2006 on mh2.centtech.com X-Virus-Status: Clean Subject: [PATCH] adding two new options to 'cp' X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 02:51:36 -0000 This is a multi-part message in MIME format. --------------020206000205090101090104 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I'm tired of trying to use rsync or gcp (which doesn't like symlinks often) to copy trees of files/directories using hard links, so I added the gcp-ish options -a and -l. -a is 'archive' mode, which is just a quick form of -PpR. -l is 'link' mode, where regular files get hard linked instead of copied. So, you can mimic an entire tree with something like: cp -al /from/ /to/ and it's fast too! Patch is against 6-STABLE, but works well on 7-CURRENT as well. Patch is here (with man page edits): http://www.googlebit.com/freebsd/patches/cp-patch cd /tmp/ fetch http://www.googlebit.com/freebsd/patches/cp-patch cd /usr/src/ patch < /tmp/cp-patch cd bin/cp make && make install Patch was done for rsnapshot users mainly (there are quite a few of us). Comments? Flames? Committers willing to commit? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ --------------020206000205090101090104 Content-Type: text/plain; name="cp-patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="cp-patch" Index: bin/cp/cp.1 =================================================================== RCS file: /alt/ncvs/src/bin/cp/cp.1,v retrieving revision 1.33 diff -u -u -r1.33 cp.1 --- bin/cp/cp.1 25 Feb 2005 00:40:46 -0000 1.33 +++ bin/cp/cp.1 26 Jul 2006 19:52:42 -0000 @@ -45,7 +45,7 @@ .Op Fl H | Fl L | Fl P .Oc .Op Fl f | i | n -.Op Fl pv +.Op Fl aplv .Ar source_file target_file .Nm .Oo @@ -53,7 +53,7 @@ .Op Fl H | Fl L | Fl P .Oc .Op Fl f | i | n -.Op Fl pv +.Op Fl aplv .Ar source_file ... target_directory .Sh DESCRIPTION In the first synopsis form, the @@ -116,6 +116,10 @@ or .Xr pax 1 instead. +.It Fl a +Archive mode. Same as -PpR +.It Fl l +Create hard links to regular files instead of copying. .It Fl f For each existing destination pathname, remove it and create a new file, without prompting for confirmation Index: bin/cp/cp.c =================================================================== RCS file: /alt/ncvs/src/bin/cp/cp.c,v retrieving revision 1.51.2.1 diff -u -u -r1.51.2.1 cp.c --- bin/cp/cp.c 12 Nov 2005 21:21:45 -0000 1.51.2.1 +++ bin/cp/cp.c 26 Jul 2006 17:49:55 -0000 @@ -83,7 +83,7 @@ PATH_T to = { to.p_path, emptystring, "" }; -int fflag, iflag, nflag, pflag, vflag; +int fflag, iflag, lflag, nflag, pflag, vflag; static int Rflag, rflag; volatile sig_atomic_t info; @@ -102,7 +102,7 @@ char *target; Hflag = Lflag = Pflag = 0; - while ((ch = getopt(argc, argv, "HLPRfinprv")) != -1) + while ((ch = getopt(argc, argv, "HLPRfinprvla")) != -1) switch (ch) { case 'H': Hflag = 1; @@ -140,6 +140,15 @@ case 'v': vflag = 1; break; + case 'l': + lflag = 1; + break; + case 'a': + Pflag = 1; + pflag = 1; + Rflag = 1; + Hflag = Lflag = 0; + break; default: usage(); break; Index: bin/cp/extern.h =================================================================== RCS file: /alt/ncvs/src/bin/cp/extern.h,v retrieving revision 1.19.8.1 diff -u -u -r1.19.8.1 extern.h --- bin/cp/extern.h 12 Nov 2005 21:21:45 -0000 1.19.8.1 +++ bin/cp/extern.h 26 Jul 2006 17:49:55 -0000 @@ -37,7 +37,7 @@ } PATH_T; extern PATH_T to; -extern int fflag, iflag, nflag, pflag, vflag; +extern int fflag, iflag, lflag, nflag, pflag, vflag; extern volatile sig_atomic_t info; __BEGIN_DECLS Index: bin/cp/utils.c =================================================================== RCS file: /alt/ncvs/src/bin/cp/utils.c,v retrieving revision 1.45.2.1 diff -u -u -r1.45.2.1 utils.c --- bin/cp/utils.c 12 Nov 2005 21:21:45 -0000 1.45.2.1 +++ bin/cp/utils.c 26 Jul 2006 19:39:09 -0000 @@ -61,7 +61,7 @@ { static char buf[MAXBSIZE]; struct stat *fs; - int ch, checkch, from_fd, rcount, rval, to_fd; + int ch, checkch, from_fd = 0, rcount, rval, to_fd = 0; ssize_t wcount; size_t wresid; size_t wtotal; @@ -109,15 +109,20 @@ /* remove existing destination file name, * create a new file */ (void)unlink(to.p_path); - to_fd = open(to.p_path, O_WRONLY | O_TRUNC | O_CREAT, - fs->st_mode & ~(S_ISUID | S_ISGID)); - } else - /* overwrite existing destination file name */ - to_fd = open(to.p_path, O_WRONLY | O_TRUNC, 0); - } else - to_fd = open(to.p_path, O_WRONLY | O_TRUNC | O_CREAT, - fs->st_mode & ~(S_ISUID | S_ISGID)); - + if (!lflag) + to_fd = open(to.p_path, O_WRONLY | O_TRUNC | O_CREAT, + fs->st_mode & ~(S_ISUID | S_ISGID)); + } else { + if (!lflag) + /* overwrite existing destination file name */ + to_fd = open(to.p_path, O_WRONLY | O_TRUNC, 0); + } + } else { + if (!lflag) + to_fd = open(to.p_path, O_WRONLY | O_TRUNC | O_CREAT, + fs->st_mode & ~(S_ISUID | S_ISGID)); + } + if (to_fd == -1) { warn("%s", to.p_path); (void)close(from_fd); @@ -126,73 +131,81 @@ rval = 0; - /* - * Mmap and write if less than 8M (the limit is so we don't totally - * trash memory on big files. This is really a minor hack, but it - * wins some CPU back. - */ + if (!lflag) { + /* + * Mmap and write if less than 8M (the limit is so we don't totally + * trash memory on big files. This is really a minor hack, but it + * wins some CPU back. + */ #ifdef VM_AND_BUFFER_CACHE_SYNCHRONIZED - if (S_ISREG(fs->st_mode) && fs->st_size > 0 && - fs->st_size <= 8 * 1048576) { - if ((p = mmap(NULL, (size_t)fs->st_size, PROT_READ, - MAP_SHARED, from_fd, (off_t)0)) == MAP_FAILED) { - warn("%s", entp->fts_path); - rval = 1; - } else { - wtotal = 0; - for (bufp = p, wresid = fs->st_size; ; - bufp += wcount, wresid -= (size_t)wcount) { - wcount = write(to_fd, bufp, wresid); - wtotal += wcount; - if (info) { - info = 0; - (void)fprintf(stderr, - "%s -> %s %3d%%\n", - entp->fts_path, to.p_path, - cp_pct(wtotal, fs->st_size)); - - } - if (wcount >= (ssize_t)wresid || wcount <= 0) - break; - } - if (wcount != (ssize_t)wresid) { - warn("%s", to.p_path); - rval = 1; - } - /* Some systems don't unmap on close(2). */ - if (munmap(p, fs->st_size) < 0) { + if (S_ISREG(fs->st_mode) && fs->st_size > 0 && + fs->st_size <= 8 * 1048576) { + if ((p = mmap(NULL, (size_t)fs->st_size, PROT_READ, + MAP_SHARED, from_fd, (off_t)0)) == MAP_FAILED) { warn("%s", entp->fts_path); rval = 1; + } else { + wtotal = 0; + for (bufp = p, wresid = fs->st_size; ; + bufp += wcount, wresid -= (size_t)wcount) { + wcount = write(to_fd, bufp, wresid); + wtotal += wcount; + if (info) { + info = 0; + (void)fprintf(stderr, + "%s -> %s %3d%%\n", + entp->fts_path, to.p_path, + cp_pct(wtotal, fs->st_size)); + + } + if (wcount >= (ssize_t)wresid || wcount <= 0) + break; + } + if (wcount != (ssize_t)wresid) { + warn("%s", to.p_path); + rval = 1; + } + /* Some systems don't unmap on close(2). */ + if (munmap(p, fs->st_size) < 0) { + warn("%s", entp->fts_path); + rval = 1; + } } - } - } else + } else #endif - { - wtotal = 0; - while ((rcount = read(from_fd, buf, MAXBSIZE)) > 0) { - for (bufp = buf, wresid = rcount; ; - bufp += wcount, wresid -= wcount) { - wcount = write(to_fd, bufp, wresid); - wtotal += wcount; - if (info) { - info = 0; - (void)fprintf(stderr, - "%s -> %s %3d%%\n", - entp->fts_path, to.p_path, - cp_pct(wtotal, fs->st_size)); - + { + wtotal = 0; + while ((rcount = read(from_fd, buf, MAXBSIZE)) > 0) { + for (bufp = buf, wresid = rcount; ; + bufp += wcount, wresid -= wcount) { + wcount = write(to_fd, bufp, wresid); + wtotal += wcount; + if (info) { + info = 0; + (void)fprintf(stderr, + "%s -> %s %3d%%\n", + entp->fts_path, to.p_path, + cp_pct(wtotal, fs->st_size)); + + } + if (wcount >= (ssize_t)wresid || wcount <= 0) + break; } - if (wcount >= (ssize_t)wresid || wcount <= 0) + if (wcount != (ssize_t)wresid) { + warn("%s", to.p_path); + rval = 1; break; + } } - if (wcount != (ssize_t)wresid) { - warn("%s", to.p_path); + if (rcount < 0) { + warn("%s", entp->fts_path); rval = 1; - break; } } - if (rcount < 0) { - warn("%s", entp->fts_path); + } else { + if (link(entp->fts_path, to.p_path)) { + (void)close(from_fd); + warn("%s", to.p_path); rval = 1; } } @@ -204,14 +217,16 @@ * to remove it if we created it and its length is 0. */ - if (pflag && setfile(fs, to_fd)) - rval = 1; - if (pflag && preserve_fd_acls(from_fd, to_fd) != 0) - rval = 1; - (void)close(from_fd); - if (close(to_fd)) { - warn("%s", to.p_path); - rval = 1; + if (!lflag) { + if (pflag && setfile(fs, to_fd)) + rval = 1; + if (pflag && preserve_fd_acls(from_fd, to_fd) != 0) + rval = 1; + (void)close(from_fd); + if (close(to_fd)) { + warn("%s", to.p_path); + rval = 1; + } } return (rval); } Index: etc/mtree/BSD.include.dist =================================================================== RCS file: /alt/ncvs/src/etc/mtree/BSD.include.dist,v retrieving revision 1.100.2.2 diff -u -u -r1.100.2.2 BSD.include.dist --- etc/mtree/BSD.include.dist 16 Nov 2005 10:50:10 -0000 1.100.2.2 +++ etc/mtree/BSD.include.dist 26 Jul 2006 03:42:10 -0000 @@ -100,6 +100,8 @@ .. gate .. + journal + .. label .. mirror Index: include/Makefile =================================================================== RCS file: /alt/ncvs/src/include/Makefile,v retrieving revision 1.244.2.4 diff -u -u -r1.244.2.4 Makefile --- include/Makefile 17 Jul 2006 10:09:54 -0000 1.244.2.4 +++ include/Makefile 26 Jul 2006 03:42:10 -0000 @@ -42,8 +42,8 @@ fs/devfs fs/fdescfs fs/fifofs fs/msdosfs fs/ntfs fs/nullfs \ fs/nwfs fs/portalfs fs/procfs fs/smbfs fs/udf fs/umapfs \ fs/unionfs \ - geom/concat geom/eli geom/gate geom/label geom/mirror geom/nop \ - geom/raid3 geom/shsec geom/stripe \ + geom/concat geom/eli geom/gate geom/journal geom/label geom/mirror \ + geom/nop geom/raid3 geom/shsec geom/stripe \ isofs/cd9660 \ netatm/ipatm netatm/sigpvc netatm/spans netatm/uni \ netgraph/atm netgraph/netflow \ --------------020206000205090101090104-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 02:58:15 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B98B216A4DA for ; Thu, 27 Jul 2006 02:58:15 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 139A043D5A for ; Thu, 27 Jul 2006 02:58:14 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.24] (andersonbox4.centtech.com [192.168.42.24]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k6R2wEsG075019; Wed, 26 Jul 2006 21:58:14 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44C82BD2.2030002@centtech.com> Date: Wed, 26 Jul 2006 21:58:26 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.4 (X11/20060612) MIME-Version: 1.0 To: Eric Anderson References: <44C82A40.3020009@centtech.com> In-Reply-To: <44C82A40.3020009@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1623/Wed Jul 26 17:35:11 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: FreeBSD Hackers Subject: Re: [PATCH] adding two new options to 'cp' X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 02:58:15 -0000 On 07/26/06 21:51, Eric Anderson wrote: The patch attached had some junk in it. The patch on the website doesn't have that. :) Oops.. Eric [..snip..] > --- etc/mtree/BSD.include.dist 16 Nov 2005 10:50:10 -0000 1.100.2.2 > +++ etc/mtree/BSD.include.dist 26 Jul 2006 03:42:10 -0000 > @@ -100,6 +100,8 @@ > .. > gate > .. > + journal > + .. > label > .. > mirror > Index: include/Makefile > =================================================================== > RCS file: /alt/ncvs/src/include/Makefile,v > retrieving revision 1.244.2.4 > diff -u -u -r1.244.2.4 Makefile > --- include/Makefile 17 Jul 2006 10:09:54 -0000 1.244.2.4 > +++ include/Makefile 26 Jul 2006 03:42:10 -0000 > @@ -42,8 +42,8 @@ > fs/devfs fs/fdescfs fs/fifofs fs/msdosfs fs/ntfs fs/nullfs \ > fs/nwfs fs/portalfs fs/procfs fs/smbfs fs/udf fs/umapfs \ > fs/unionfs \ > - geom/concat geom/eli geom/gate geom/label geom/mirror geom/nop \ > - geom/raid3 geom/shsec geom/stripe \ > + geom/concat geom/eli geom/gate geom/journal geom/label geom/mirror \ > + geom/nop geom/raid3 geom/shsec geom/stripe \ > isofs/cd9660 \ > netatm/ipatm netatm/sigpvc netatm/spans netatm/uni \ > netgraph/atm netgraph/netflow \ > > > ------------------------------------------------------------------------ > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 03:51:14 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0748016A4DD for ; Thu, 27 Jul 2006 03:51:14 +0000 (UTC) (envelope-from prvs=julian=356e8a28d@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB08443D4C for ; Thu, 27 Jul 2006 03:51:13 +0000 (GMT) (envelope-from prvs=julian=356e8a28d@elischer.org) Received: from unknown (HELO [192.168.2.4]) ([10.251.60.53]) by a50.ironport.com with ESMTP; 26 Jul 2006 20:51:13 -0700 Message-ID: <44C83831.5050900@elischer.org> Date: Wed, 26 Jul 2006 20:51:13 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <44C82A40.3020009@centtech.com> In-Reply-To: <44C82A40.3020009@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers Subject: Re: [PATCH] adding two new options to 'cp' X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 03:51:14 -0000 Eric Anderson wrote: > I'm tired of trying to use rsync or gcp (which doesn't like symlinks > often) to copy trees of files/directories using hard links, so I added > the gcp-ish options -a and -l. > > -a is 'archive' mode, which is just a quick form of -PpR. > -l is 'link' mode, where regular files get hard linked instead of copied. > > So, you can mimic an entire tree with something like: > > cp -al /from/ /to/ I've always used: find . -depth |cpio -pdlmv $dest (fully portable) but your addition can't hurt (well it might make the larger program load a bit slower but it isn't that much.) > > and it's fast too! > > Patch is against 6-STABLE, but works well on 7-CURRENT as well. > > Patch is here (with man page edits): > http://www.googlebit.com/freebsd/patches/cp-patch > > cd /tmp/ > fetch http://www.googlebit.com/freebsd/patches/cp-patch > cd /usr/src/ > patch < /tmp/cp-patch > cd bin/cp > make && make install > > Patch was done for rsnapshot users mainly (there are quite a few of us). > > Comments? Flames? Committers willing to commit? > > Eric > From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 04:39:50 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76CB916A4DA for ; Thu, 27 Jul 2006 04:39:50 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BFC243D55 for ; Thu, 27 Jul 2006 04:39:49 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id DC974E9; Wed, 26 Jul 2006 23:39:48 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 2548761C2B; Wed, 26 Jul 2006 23:39:48 -0500 (CDT) Date: Wed, 26 Jul 2006 23:39:48 -0500 From: "Matthew D. Fuller" To: Julian Elischer Message-ID: <20060727043948.GE69505@over-yonder.net> References: <44C82A40.3020009@centtech.com> <44C83831.5050900@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44C83831.5050900@elischer.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.3 Cc: FreeBSD Hackers Subject: Re: [PATCH] adding two new options to 'cp' X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 04:39:50 -0000 On Wed, Jul 26, 2006 at 08:51:13PM -0700 I heard the voice of Julian Elischer, and lo! it spake thus: > > I've always used: > find . -depth |cpio -pdlmv $dest While we're in workarounds, I fake with: % cat ~/bin/tarcp.sh #!/bin/sh cmd1="tar -cf - -C $1 ." cmd2="tar -xvpf - -C $2" echo "$cmd1 | $cmd2" $cmd1 | $cmd2 (which has the twin advantages of telling me what it's doing as it goes, and using two processes so it can pound source and dest disks in full parallel) -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 06:40:08 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 371EA16A4DA for ; Thu, 27 Jul 2006 06:40:08 +0000 (UTC) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CF9443D46 for ; Thu, 27 Jul 2006 06:40:06 +0000 (GMT) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (localhost [IPv6:::1]) by srv1.cosmo-project.de (8.12.10/8.12.10) with ESMTP id k6R6e5nZ065453 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 27 Jul 2006 08:40:05 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.12.10/8.12.10/Submit) with UUCP id k6R6e4Gq065452 for hackers@freebsd.org; Thu, 27 Jul 2006 08:40:04 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: from titan.klemm.apsfilter.org (localhost.klemm.apsfilter.org [127.0.0.1]) by klemm.apsfilter.org (8.13.6/8.13.4) with ESMTP id k6R6ddSa002499 for ; Thu, 27 Jul 2006 08:39:39 +0200 (CEST) (envelope-from andreas@titan.klemm.apsfilter.org) Received: (from andreas@localhost) by titan.klemm.apsfilter.org (8.13.6/8.13.4/Submit) id k6R6dbXE002498 for hackers@freebsd.org; Thu, 27 Jul 2006 08:39:37 +0200 (CEST) (envelope-from andreas) Date: Thu, 27 Jul 2006 08:39:37 +0200 From: Andreas Klemm To: hackers@freebsd.org Message-ID: <20060727063936.GA1246@titan.klemm.apsfilter.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 6.1-STABLE X-Disclaimer: A free society is one where it is safe to be unpopular User-Agent: Mutt/1.5.11 Cc: Subject: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 06:40:08 -0000 Hi, DragonFly uses another disklabel as FreeBSD I discovered. Made a test installation of their 1.6 yesterday. Later I wanted to mount the dfly filesystems on FreeBSD 6.1, of course still my main Unix ;-) But it wasn't possible. The disklabel couldn't be read and as a result devfs didn't create the devices under /dev. So I compared sys/disklabel.h on the 2 BSDs and discovered a difference at the very beginning of the struct. I'm not sure for what exact purpose Matt uses his new pack identifier. Does somebody have a clue ??? Is this perhaps something useful that FreeBSD could also use/need ? Or at least adopt, to be compatible if it doesn't hurt too much ??? Would be cool to be able to mount fs's across BSDs. Our FreeBSD 6.1 one: struct disklabel { u_int32_t d_magic; /* the magic number */ u_int16_t d_type; /* drive type */ u_int16_t d_subtype; /* controller/d_type specific */ char d_typename[16]; /* type name, e.g. "eagle" */ char d_packname[16]; /* pack identifier */ /* disk geometry: */ DragonFly: struct disklabel { u_int32_t d_magic; /* the magic number */ u_int16_t d_type; /* drive type */ u_int16_t d_subtype; /* controller/d_type specific */ char d_typename[16]; /* type name, e.g. "eagle" */ /* * d_packname contains the pack identifier and is returned when * the disklabel is read off the disk or in-core copy. * d_boot0 and d_boot1 are the (optional) names of the * primary (block 0) and secondary (block 1-15) bootstraps * as found in /boot. These are returned when using * getdiskbyname(3) to retrieve the values from /etc/disktab. */ union { char un_d_packname[16]; /* pack identifier */ struct { char *un_d_boot0; /* primary bootstrap name */ char *un_d_boot1; /* secondary bootstrap name */ } un_b; } d_un; #define d_packname d_un.un_d_packname #define d_boot0 d_un.un_b.un_d_boot0 #define d_boot1 d_un.un_b.un_d_boot1 /* disk geometry: */ Andreas /// -- Andreas Klemm - Powered by FreeBSD 6 Need a magic printfilter today ? -> http://www.apsfilter.org/ From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 07:15:07 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD67F16A4EA for ; Thu, 27 Jul 2006 07:15:07 +0000 (UTC) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AC0F43D4C for ; Thu, 27 Jul 2006 07:15:06 +0000 (GMT) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (localhost [IPv6:::1]) by srv1.cosmo-project.de (8.12.10/8.12.10) with ESMTP id k6R7F5nZ065977 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 27 Jul 2006 09:15:05 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.12.10/8.12.10/Submit) with UUCP id k6R7F47M065976 for hackers@freebsd.org; Thu, 27 Jul 2006 09:15:04 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: from titan.klemm.apsfilter.org (localhost.klemm.apsfilter.org [127.0.0.1]) by klemm.apsfilter.org (8.13.6/8.13.4) with ESMTP id k6R7Buej003040 for ; Thu, 27 Jul 2006 09:11:56 +0200 (CEST) (envelope-from andreas@titan.klemm.apsfilter.org) Received: (from andreas@localhost) by titan.klemm.apsfilter.org (8.13.6/8.13.4/Submit) id k6R7BrUB003039 for hackers@freebsd.org; Thu, 27 Jul 2006 09:11:53 +0200 (CEST) (envelope-from andreas) Date: Thu, 27 Jul 2006 09:11:53 +0200 From: Andreas Klemm To: hackers@freebsd.org Message-ID: <20060727071153.GA2944@titan.klemm.apsfilter.org> References: <20060727063936.GA1246@titan.klemm.apsfilter.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060727063936.GA1246@titan.klemm.apsfilter.org> X-Operating-System: FreeBSD 6.1-STABLE X-Disclaimer: A free society is one where it is safe to be unpopular User-Agent: Mutt/1.5.11 Cc: Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 07:15:08 -0000 to followup myself ... I just see, we also have pack identifier, its the additional struct behind it that differs. "Bootstrap name" etc... Andreas /// -- Andreas Klemm - Powered by FreeBSD 6 Need a magic printfilter today ? -> http://www.apsfilter.org/ From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 10:57:12 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD47B16A4E2 for ; Thu, 27 Jul 2006 10:57:12 +0000 (UTC) (envelope-from mag@intron.ac) Received: from smtp.263.net (263.net.cn [211.150.96.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5447A43D49 for ; Thu, 27 Jul 2006 10:57:12 +0000 (GMT) (envelope-from mag@intron.ac) Received: from origin.intron.ac (unknown [127.0.0.1]) by smtp.263.net (Postfix) with ESMTP id 1081FF1D8C for ; Thu, 27 Jul 2006 18:57:17 +0800 (CST) X-KSVirus-check: 0 From: "Intron" To: freebsd-hackers@freebsd.org Date: Thu, 27 Jul 2006 18:56:05 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <1153997829.12770@origin.intron.ac> Subject: How to Use ddb(4)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 10:57:12 -0000 I have add relevant options into my kernel (7.0-CURRENT) configuration file: makeoptions DEBUG=-g options KDB options DDB options GDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN When kernel panics, the prompt "db>" will appear. But at this time I cannot control my computer with keyboard any longer. What's wrong with me? In my mind, both 7.0-CURRENT and 6.x-STABLE halt a year ago are all right in ddb(4). By the way, the loader(8) option "-a" (to let user decide which file system is taken as root file system) is also unusable. ------------------------------------------------------------------------ From Beijing, China From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 11:09:50 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9071916A4E0 for ; Thu, 27 Jul 2006 11:09:50 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 038B143D46 for ; Thu, 27 Jul 2006 11:09:49 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 678F52085; Thu, 27 Jul 2006 13:09:41 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 5B87B2082; Thu, 27 Jul 2006 13:09:41 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 42B7833C31; Thu, 27 Jul 2006 13:09:41 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: "Intron" References: <1153997829.12770@origin.intron.ac> Date: Thu, 27 Jul 2006 13:09:40 +0200 In-Reply-To: <1153997829.12770@origin.intron.ac> (mag@intron.ac's message of "Thu, 27 Jul 2006 18:56:05 +0800") Message-ID: <864px31eyz.fsf@xps.des.no> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: How to Use ddb(4)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 11:09:50 -0000 "Intron" writes: > When kernel panics, the prompt "db>" will appear. But at this time > I cannot control my computer with keyboard any longer. What's wrong > with me? I don't know what's wrong with you, but as regards your computer: disable kbdmux and use a PS/2 keyboard. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 11:14:21 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02AC716A4E0 for ; Thu, 27 Jul 2006 11:14:21 +0000 (UTC) (envelope-from shriek.007@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D71E43D4C for ; Thu, 27 Jul 2006 11:14:19 +0000 (GMT) (envelope-from shriek.007@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so213907uge for ; Thu, 27 Jul 2006 04:14:19 -0700 (PDT) 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; b=N6vGKxKBO+OGvTd24Mr3bQcHuCnsL951+zj1qDRI6D9ECBWKcFUJuVX+9Lo9l3P9HBBQN4TTTQVxKIzHMDPPQnPGbBdSsGk849aWA7+PQ5VeOhjwgDfQ2ifDD65v7/EvDKmB2o+6YhOkpd72Rqih2WTNFYiKk+rg0Fv7V5RYGjM= Received: by 10.78.164.13 with SMTP id m13mr3740432hue; Thu, 27 Jul 2006 04:14:18 -0700 (PDT) Received: by 10.78.118.14 with HTTP; Thu, 27 Jul 2006 04:14:18 -0700 (PDT) Message-ID: <3ce33f6c0607270414q4ea723f6k93959e316853bc85@mail.gmail.com> Date: Thu, 27 Jul 2006 16:44:18 +0530 From: Shriek To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Need some articles on routing sockets in FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 11:14:21 -0000 I need to understand the usage and to some level details of the routing sockets (internals may not be the exact word but still ... :-] ) .... there is this scenario of this multiple daemons that are communicating using *rt_sock *and need to trace the communication that is happening ... for this I need to know rt_sock ... are there any articles on Routing Sockets ... and their usage / internals .... From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 11:50:31 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0399F16A4DF for ; Thu, 27 Jul 2006 11:50:31 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4894F43D5C for ; Thu, 27 Jul 2006 11:50:29 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (azwtcf@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k6RBoMfO031746 for ; Thu, 27 Jul 2006 13:50:28 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k6RBoM9p031745; Thu, 27 Jul 2006 13:50:22 +0200 (CEST) (envelope-from olli) Date: Thu, 27 Jul 2006 13:50:22 +0200 (CEST) Message-Id: <200607271150.k6RBoM9p031745@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG In-Reply-To: <44C82A40.3020009@centtech.com> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Thu, 27 Jul 2006 13:50:28 +0200 (CEST) X-Mailman-Approved-At: Thu, 27 Jul 2006 12:06:07 +0000 Cc: Subject: Re: [PATCH] adding two new options to 'cp' X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 11:50:31 -0000 Eric Anderson wrote: > I'm tired of trying to use rsync or gcp (which doesn't like symlinks > often) to copy trees of files/directories using hard links, so I added > the gcp-ish options -a and -l. > > -a is 'archive' mode, which is just a quick form of -PpR. -P is the default anyway, so -a would only replace -Rp. I don't think saving one letter justifies introducing a new option. You can use an alias or shell function. > -l is 'link' mode, where regular files get hard linked instead of copied. > > So, you can mimic an entire tree with something like: > > cp -al /from/ /to/ > > and it's fast too! You can do the same with existing tools in a portable (and thus preferable) way: cd /from; find -d . | cpio -dumpl /to Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead." -- RFC 1925 From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 12:22:26 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12ED216A4DF; Thu, 27 Jul 2006 12:22:26 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from hydra.bec.de (www.ostsee-abc.de [62.206.222.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A185E43D4C; Thu, 27 Jul 2006 12:22:25 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (wlan033212.uni-rostock.de [139.30.33.212]) by hydra.bec.de (Postfix) with ESMTP id E678235707; Thu, 27 Jul 2006 14:22:19 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1000) id 47DE56CC26; Thu, 27 Jul 2006 14:21:59 +0200 (CEST) Date: Thu, 27 Jul 2006 14:21:59 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org, hackers@freebsd.org Message-ID: <20060727122159.GB4217@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org, hackers@freebsd.org References: <20060727063936.GA1246@titan.klemm.apsfilter.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060727063936.GA1246@titan.klemm.apsfilter.org> User-Agent: Mutt/1.5.11 Cc: Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 12:22:26 -0000 On Thu, Jul 27, 2006 at 08:39:37AM +0200, Andreas Klemm wrote: > Later I wanted to mount the dfly filesystems on FreeBSD 6.1, > of course still my main Unix ;-) But it wasn't possible. DragonFly disklabels allow 16 entries by default, FreeBSD still limits it to 8. That's why you can't read it directly. Joerg From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 12:22:26 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12ED216A4DF; Thu, 27 Jul 2006 12:22:26 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from hydra.bec.de (www.ostsee-abc.de [62.206.222.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A185E43D4C; Thu, 27 Jul 2006 12:22:25 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (wlan033212.uni-rostock.de [139.30.33.212]) by hydra.bec.de (Postfix) with ESMTP id E678235707; Thu, 27 Jul 2006 14:22:19 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1000) id 47DE56CC26; Thu, 27 Jul 2006 14:21:59 +0200 (CEST) Date: Thu, 27 Jul 2006 14:21:59 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org, hackers@freebsd.org Message-ID: <20060727122159.GB4217@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org, hackers@freebsd.org References: <20060727063936.GA1246@titan.klemm.apsfilter.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060727063936.GA1246@titan.klemm.apsfilter.org> User-Agent: Mutt/1.5.11 Cc: Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 12:22:26 -0000 On Thu, Jul 27, 2006 at 08:39:37AM +0200, Andreas Klemm wrote: > Later I wanted to mount the dfly filesystems on FreeBSD 6.1, > of course still my main Unix ;-) But it wasn't possible. DragonFly disklabels allow 16 entries by default, FreeBSD still limits it to 8. That's why you can't read it directly. Joerg From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 13:49:57 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7041916A4DF; Thu, 27 Jul 2006 13:49:57 +0000 (UTC) (envelope-from steve@energistic.com) Received: from energistic.com (mail.energistic.com [216.54.148.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 605E943D64; Thu, 27 Jul 2006 13:49:54 +0000 (GMT) (envelope-from steve@energistic.com) Received: from energistic.com (steve@localhost.energistic.com [127.0.0.1]) by energistic.com (8.13.6/8.13.6) with ESMTP id k6RDnm7A005763; Thu, 27 Jul 2006 09:49:48 -0400 (EDT) (envelope-from steve@energistic.com) Received: (from steve@localhost) by energistic.com (8.13.6/8.13.6/Submit) id k6RDnmN4005522; Thu, 27 Jul 2006 09:49:48 -0400 (EDT) (envelope-from steve) Date: Thu, 27 Jul 2006 09:49:48 -0400 From: Steve Ames To: freebsd-hackers@freebsd.org, hackers@freebsd.org Message-ID: <20060727134948.GA3755@energistic.com> References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060727122159.GB4217@britannica.bec.de> User-Agent: Mutt/1.5.12-2006-07-14 X-Spam-Status: No, score=-8.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS, SPF_PASS,USER_IN_WHITELIST_TO autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on energistic.com Cc: Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 13:49:57 -0000 On Thu, Jul 27, 2006 at 02:21:59PM +0200, Joerg Sonnenberger wrote: > On Thu, Jul 27, 2006 at 08:39:37AM +0200, Andreas Klemm wrote: > > Later I wanted to mount the dfly filesystems on FreeBSD 6.1, > > of course still my main Unix ;-) But it wasn't possible. > > DragonFly disklabels allow 16 entries by default, FreeBSD still limits > it to 8. That's why you can't read it directly. Are there plans to bump the default up from 8? I'm honestly torn on this topic whenever I install a new system. On the one hand I like having a lot of discrete mountpoints to control potential usage. On the other hand with drive space being so inexpensive I sometimes wonder if I need to bother and can get away with very few mountpoints. On very large disks (or arrays that appear as a single disk) I have to create multiple slices in order to get more than 8 mountpoints. Its an extra hoop to jump through. -steve From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 13:49:57 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7041916A4DF; Thu, 27 Jul 2006 13:49:57 +0000 (UTC) (envelope-from steve@energistic.com) Received: from energistic.com (mail.energistic.com [216.54.148.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 605E943D64; Thu, 27 Jul 2006 13:49:54 +0000 (GMT) (envelope-from steve@energistic.com) Received: from energistic.com (steve@localhost.energistic.com [127.0.0.1]) by energistic.com (8.13.6/8.13.6) with ESMTP id k6RDnm7A005763; Thu, 27 Jul 2006 09:49:48 -0400 (EDT) (envelope-from steve@energistic.com) Received: (from steve@localhost) by energistic.com (8.13.6/8.13.6/Submit) id k6RDnmN4005522; Thu, 27 Jul 2006 09:49:48 -0400 (EDT) (envelope-from steve) Date: Thu, 27 Jul 2006 09:49:48 -0400 From: Steve Ames To: freebsd-hackers@freebsd.org, hackers@freebsd.org Message-ID: <20060727134948.GA3755@energistic.com> References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060727122159.GB4217@britannica.bec.de> User-Agent: Mutt/1.5.12-2006-07-14 X-Spam-Status: No, score=-8.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS, SPF_PASS,USER_IN_WHITELIST_TO autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on energistic.com Cc: Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 13:49:57 -0000 On Thu, Jul 27, 2006 at 02:21:59PM +0200, Joerg Sonnenberger wrote: > On Thu, Jul 27, 2006 at 08:39:37AM +0200, Andreas Klemm wrote: > > Later I wanted to mount the dfly filesystems on FreeBSD 6.1, > > of course still my main Unix ;-) But it wasn't possible. > > DragonFly disklabels allow 16 entries by default, FreeBSD still limits > it to 8. That's why you can't read it directly. Are there plans to bump the default up from 8? I'm honestly torn on this topic whenever I install a new system. On the one hand I like having a lot of discrete mountpoints to control potential usage. On the other hand with drive space being so inexpensive I sometimes wonder if I need to bother and can get away with very few mountpoints. On very large disks (or arrays that appear as a single disk) I have to create multiple slices in order to get more than 8 mountpoints. Its an extra hoop to jump through. -steve From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 13:02:59 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D02BD16A4DE; Thu, 27 Jul 2006 13:02:59 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms040pub.verizon.net (vms040pub.verizon.net [206.46.252.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FC0343D46; Thu, 27 Jul 2006 13:02:59 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms071.mailsrvcs.net ([192.168.1.4]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0J3200G4FC8FFPVA@vms040.mailsrvcs.net>; Thu, 27 Jul 2006 08:02:39 -0500 (CDT) Received: from 198.190.8.100 ([198.190.8.100]) by vms071.mailsrvcs.net (Verizon Webmail) with HTTP; Thu, 27 Jul 2006 08:02:38 -0500 (CDT) Date: Thu, 27 Jul 2006 08:02:38 -0500 (CDT) From: Sergey Babkin X-Originating-IP: [198.190.8.100] To: Andreas Klemm , hackers@freebsd.org Message-id: <14903907.33071154005359137.JavaMail.root@vms071.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Mailman-Approved-At: Thu, 27 Jul 2006 13:59:58 +0000 Cc: Subject: Re: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: babkin@users.sf.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 13:02:59 -0000 >to followup myself ... I just see, we also have pack identifier, >its the additional struct behind it that differs. >"Bootstrap name" etc... Those are parts of an union, so the total size still shouldn't change. I'd guess that the char[] format is used on-disk and the pointers are used in-memory. -SB From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 14:13:52 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2ADDC16A4DF for ; Thu, 27 Jul 2006 14:13:52 +0000 (UTC) (envelope-from mag@intron.ac) Received: from smtp.263.net (263.net.cn [211.150.96.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FFB843D70 for ; Thu, 27 Jul 2006 14:13:43 +0000 (GMT) (envelope-from mag@intron.ac) Received: from origin.intron.ac (unknown [127.0.0.1]) by smtp.263.net (Postfix) with ESMTP id 06529F1C17 for ; Thu, 27 Jul 2006 22:13:48 +0800 (CST) X-KSVirus-check: 0 References: <1153997829.12770@origin.intron.ac> <864px31eyz.fsf@xps.des.no> In-Reply-To: <864px31eyz.fsf@xps.des.no> From: "Intron" To: des@des.no Date: Thu, 27 Jul 2006 22:12:01 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <1154009620.15704@origin.intron.ac> Cc: freebsd-hackers@freebsd.org Subject: Re: How to Use ddb(4)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 14:13:52 -0000 Dag-Erling [iso-8859-1] Smo/rgrav wrote: > "Intron" writes: >> When kernel panics, the prompt "db>" will appear. But at this time >> I cannot control my computer with keyboard any longer. What's wrong >> with me? > > I don't know what's wrong with you, but as regards your computer: > disable kbdmux and use a PS/2 keyboard. > > DES > -- > Dag-Erling Smo/rgrav - des@des.no > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" I've been comforted by you that there's nothing wrong with me. Well, FreeBSD Developers' Handbook needs to be updated now. http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-ddb.html The same to manual page ddb(4). ------------------------------------------------------------------------ From Beijing, China From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 14:18:09 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7796616A4DA for ; Thu, 27 Jul 2006 14:18:09 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0782A43D46 for ; Thu, 27 Jul 2006 14:18:08 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 104BC2089; Thu, 27 Jul 2006 16:18:04 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 031372088; Thu, 27 Jul 2006 16:18:04 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id DB1B733C31; Thu, 27 Jul 2006 16:18:03 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: "Intron" References: <1153997829.12770@origin.intron.ac> <864px31eyz.fsf@xps.des.no> Date: Thu, 27 Jul 2006 16:18:03 +0200 In-Reply-To: (mag@intron.ac's message of "Thu, 27 Jul 2006 22:12:01 +0800") Message-ID: <86psfryvvo.fsf@xps.des.no> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: How to Use ddb(4)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 14:18:09 -0000 "Intron" writes: > Dag-Erling [iso-8859-1] Smo/rgrav wrote: > > "Intron" writes: > > > When kernel panics, the prompt "db>" will appear. But at this > > > time I cannot control my computer with keyboard any longer. > > > What's wrong with me? > > I don't know what's wrong with you, but as regards your computer: > > disable kbdmux and use a PS/2 keyboard. > I've been comforted by you that there's nothing wrong with me. Glad to help :) > Well, FreeBSD Developers' Handbook needs to be updated now. No, kbdmux needs to be fixed so it works in DDB. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 14:24:51 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9C9D16A4DA for ; Thu, 27 Jul 2006 14:24:51 +0000 (UTC) (envelope-from mag@intron.ac) Received: from smtp.263.net (smtp.x263.net [211.150.96.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83A5643D4C for ; Thu, 27 Jul 2006 14:24:50 +0000 (GMT) (envelope-from mag@intron.ac) Received: from origin.intron.ac (unknown [127.0.0.1]) by smtp.263.net (Postfix) with ESMTP id 17488F1B55 for ; Thu, 27 Jul 2006 22:24:57 +0800 (CST) X-KSVirus-check: 0 From: "Intron" To: freebsd-hackers@freebsd.org Date: Thu, 27 Jul 2006 22:22:22 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <1154010289.16018@origin.intron.ac> Cc: des@des.no Subject: Warning Message from uma_zdestroy(9) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 14:24:51 -0000 Why does uma_zdestroy(9) print message like: Freed UMA keg was not empty (100 items). Lost 2 pages of memory. But actually I have made sure that uma_zalloc(9) and uma_zfree(9) appear in pair in my code. Does it represent any problems? ------------------------------------------------------------------------ From Beijing, China From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 14:37:27 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B00E16A508 for ; Thu, 27 Jul 2006 14:37:27 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69B6443D6D for ; Thu, 27 Jul 2006 14:37:23 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.236] (really [70.32.199.60]) by mta9.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060727143722.DYHX16535.mta9.adelphia.net@[192.168.1.236]>; Thu, 27 Jul 2006 10:37:22 -0400 Message-ID: <44C8CFA2.3000400@savvis.net> Date: Thu, 27 Jul 2006 07:37:22 -0700 From: maksim yevmenkin User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <1153997829.12770@origin.intron.ac> <864px31eyz.fsf@xps.des.no> <86psfryvvo.fsf@xps.des.no> In-Reply-To: <86psfryvvo.fsf@xps.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org, Intron Subject: Re: How to Use ddb(4)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 14:37:27 -0000 Dag-Erling Smørgrav wrote: > "Intron" writes: >> Dag-Erling [iso-8859-1] Smo/rgrav wrote: >>> "Intron" writes: >>>> When kernel panics, the prompt "db>" will appear. But at this >>>> time I cannot control my computer with keyboard any longer. >>>> What's wrong with me? >>> I don't know what's wrong with you, but as regards your computer: >>> disable kbdmux and use a PS/2 keyboard. >> I've been comforted by you that there's nothing wrong with me. > > Glad to help :) > >> Well, FreeBSD Developers' Handbook needs to be updated now. > > No, kbdmux needs to be fixed so it works in DDB. actually, atkbd(4) needs to be fixed to support "polled" mode :) however, this kbdmux(4) hack will, hopefully, make it work for everyone. http://lists.freebsd.org/pipermail/freebsd-current/2006-July/064727.html thanks, max From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 14:55:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C765F16A4DA for ; Thu, 27 Jul 2006 14:55:41 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (palm.hoeg.nl [83.98.131.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6068E43D73 for ; Thu, 27 Jul 2006 14:55:41 +0000 (GMT) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id AD3581CCFF; Thu, 27 Jul 2006 16:55:39 +0200 (CEST) Date: Thu, 27 Jul 2006 16:55:39 +0200 From: Ed Schouten To: Maxim Konovalov Message-ID: <20060727145539.GK48334@hoeg.nl> References: <20060726115840.K62591@mp2.macomnet.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Li7ckgedzMh1NgdW" Content-Disposition: inline In-Reply-To: <20060726115840.K62591@mp2.macomnet.net> User-Agent: Mutt/1.5.12-2006-07-14 X-Mailman-Approved-At: Thu, 27 Jul 2006 14:56:42 +0000 Cc: FreeBSD Hackers , ?????? Subject: Re: A bug in semctl() X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD Hackers List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 14:55:41 -0000 --Li7ckgedzMh1NgdW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Maxim Konovalov wrote: > What version of the file do you read? We have a different code in > HEAD. It looks like he's using RELENG_6, src/sys/kern/sysv_sem.c, 1.78. Yours, --=20 Ed Schouten WWW: http://g-rave.nl/ --Li7ckgedzMh1NgdW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEyNPr52SDGA2eCwURAvq/AJ9OaXeq6+egjjopsqg6wRqodPA1hgCeIio8 arYp1djDeCGI/euzBh6LjKw= =xSUB -----END PGP SIGNATURE----- --Li7ckgedzMh1NgdW-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 14:58:25 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAA6D16A4DF for ; Thu, 27 Jul 2006 14:58:25 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from sccmmhc92.asp.att.net (sccmmhc92.asp.att.net [204.127.203.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E8D743D66 for ; Thu, 27 Jul 2006 14:58:25 +0000 (GMT) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net ([12.207.12.9]) by sccmmhc92.asp.att.net (sccmmhc92) with ESMTP id <20060727145819m92002sv31e>; Thu, 27 Jul 2006 14:58:19 +0000 Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.6/8.13.6) with ESMTP id k6REwDpK057584; Thu, 27 Jul 2006 09:58:13 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.6/8.13.6/Submit) id k6REwDJT057583; Thu, 27 Jul 2006 09:58:13 -0500 (CDT) (envelope-from brooks) Date: Thu, 27 Jul 2006 09:58:09 -0500 From: Brooks Davis To: Steve Ames Message-ID: <20060727145808.GA49709@lor.one-eyed-alien.net> References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> <20060727134948.GA3755@energistic.com> 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: <20060727134948.GA3755@energistic.com> User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 14:58:26 -0000 --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 27, 2006 at 09:49:48AM -0400, Steve Ames wrote: > On Thu, Jul 27, 2006 at 02:21:59PM +0200, Joerg Sonnenberger wrote: > > On Thu, Jul 27, 2006 at 08:39:37AM +0200, Andreas Klemm wrote: > > > Later I wanted to mount the dfly filesystems on FreeBSD 6.1, > > > of course still my main Unix ;-) But it wasn't possible. > >=20 > > DragonFly disklabels allow 16 entries by default, FreeBSD still limits > > it to 8. That's why you can't read it directly. >=20 > Are there plans to bump the default up from 8? I'm honestly torn on > this topic whenever I install a new system. On the one hand I like > having a lot of discrete mountpoints to control potential usage. On > the other hand with drive space being so inexpensive I sometimes > wonder if I need to bother and can get away with very few mountpoints. >=20 > On very large disks (or arrays that appear as a single disk) I have > to create multiple slices in order to get more than 8 mountpoints. Its > an extra hoop to jump through. In most respects it's a pointless change since it just increases the cound from one small number to another one. If you need lots of partitions, gpt is your friend. The only problem with it at this point is that we haven't done the work to boot from it and thus do away with bsdlabels entierly. -- Brooks --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFEyNSAXY6L6fI4GtQRAsmJAKDMrIO/dxIy5kcVDK977hs9hTnOiQCfdy0a KUrQwIMAc00wK+oKUBYRSgw= =/EO/ -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 14:58:56 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED55116A4E5 for ; Thu, 27 Jul 2006 14:58:56 +0000 (UTC) (envelope-from helge.oldach@atosorigin.com) Received: from miram.origin-it.net (mail.de.atosorigin.com [194.8.96.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAE4843D53 for ; Thu, 27 Jul 2006 14:58:55 +0000 (GMT) (envelope-from helge.oldach@atosorigin.com) Received: from markab.hbg.de.int.atosorigin.com (dehsfw3e.origin-it.net [194.8.96.68]) by miram.origin-it.net (8.13.6/8.13.6/hmo020206) with ESMTP id k6REhj9H012955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jul 2006 16:58:53 +0200 (CEST) (envelope-from helge.oldach@atosorigin.com) Received: from DEHHX001.deuser.de.intra (dehhx001.hbg.de.int.atosorigin.com [161.90.164.121]) by markab.hbg.de.int.atosorigin.com (8.13.6/8.13.6/hmo020206) with ESMTP id k6QEZEH3029795; Wed, 26 Jul 2006 16:35:14 +0200 (CEST) (envelope-from helge.oldach@atosorigin.com) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Wed, 26 Jul 2006 16:35:13 +0200 Message-ID: <39AFDF50473FED469B15B6DFF2262F7A01197E92@DEHHX001.deuser.de.intra> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: puc question thread-index: AcawpcPnEDltJayVT6W2QEycKYWjJAAGju+Q From: To: , Cc: Subject: RE: puc question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 14:58:57 -0000 > > 20060428: > > The puc(4) driver has been overhauled. The ebus(4) and sbus(4) > > attachments have been removed. Make sure to configure scc(4) > > on sparc64. Note also that by default puc(4) will use uart(4) > > and not sio(4) for serial ports because interrupt handling has > > been optimized for multi-port serial cards and only uart(4) > > implements the interface to support it. >=20 > Does the puc driver now obsoletes sio as it's going to use uart = instead? # dmesg -a | egrep 'uart|puc' puc0: port 0x2000-0x201f irq 10 at device = 14.0 on pci0 uart0: <16550 or compatible> on puc0 uart1: <16550 or compatible> on puc0 uart2: <16550 or compatible> port 0x3f8-0x3ff irq 4 on acpi0 uart3: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 #=20 I have "nodevice sio" in my kernel config and kldloaded puc.ko and = uart.ko. Helge From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 17:34:57 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04EB916A4DA; Thu, 27 Jul 2006 17:34:57 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3972543D46; Thu, 27 Jul 2006 17:34:56 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k6RHYrn3078521; Thu, 27 Jul 2006 13:34:54 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 27 Jul 2006 11:21:16 -0400 User-Agent: KMail/1.9.1 References: <200607221914.15826.lofi@freebsd.org> <200607250358.21457.tijl@ulyssis.org> In-Reply-To: <200607250358.21457.tijl@ulyssis.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607271121.17313.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 27 Jul 2006 13:34:55 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1623/Wed Jul 26 18:35:11 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Daniel Eischen , Tijl Coosemans , freebsd-emulation@freebsd.org, Michael Nottebrock Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 17:34:57 -0000 On Monday 24 July 2006 21:58, Tijl Coosemans wrote: > On Monday 24 July 2006 18:49, Daniel Eischen wrote: > > On Mon, 24 Jul 2006, Tijl Coosemans wrote: > > > On Monday 24 July 2006 17:39, Daniel Eischen wrote: > > >> On Mon, 24 Jul 2006, Tijl Coosemans wrote: > > >>> I've attached two patches that accomplish this, but this seems to > > >>> trigger other problems, so use at your own risk. If you want to > > >>> try them, place them in the port's files/ directory and add a > > >>> line containing "USE_AUTOTOOLS= autoconf:259" to the Makefile. > > >>> This seems to break wine+libpthread, so I've also changed the > > >>> port to use libthr instead. > > >>> > > >>> For the libpthread experts, I haven't investigated that much > > >>> further yet, but libpthread seems to fail in create_stack() from > > >>> _pthread_create() from _thr_start_sig_daemon(). > > >> > > >> See my response to this in a previous reply to this thread. > > >> libthr and libpthread use LDT's for TLS. WINE is stomping on them > > >> because it doesn't properly create LDTs. This is not a problem > > >> with either of the thread libraries and this issue has been known > > >> ever since we implemented TLS years ago. > > > > > > And as I stated later on in that thread, I don't see where > > > libpthread and libthr still use LDT entries. As far as I understand > > > the code, instead of using an LDT entry per thread (as it sure used > > > to be), only one single GDT entry is used whose base address is > > > updated during a context switch. Looking at the cvs history, it has > > > been working like this since a couple commits of Peter Wemm about a > > > year ago. > > > > > > And if nothing but Wine uses the LDT, Wine's static allocation of > > > LDT entries can't be the problem. > > > > Look, we use %gs for TLS, period. Go see > > libpthread/arch/i386/i386/pthread_md.c for how libpthread does it. > > TLS would not work without setting aside a register for the threads > > library (and rtld) to use. > > Aaarrrrgghhh :) > > What you say is true of course, but %gs points to a GDT entry, not LDT. > libpthread and libthr no longer use LDT entries... > > There would be a problem of course if Wine or Windows programs > change %gs. Wine does seem to touch %gs but I've never actually seen it > change. It's always 0x001B, which is the correct value (GUGS_SEL). > > However, Wine/Windows uses %fs for TLS and it appears that the FreeBSD > kernel doesn't preserve it. It always ends up pointing to GUDATA_SEL. The kernel should preserve %fs across syscalls, traps, and faults. Can you point to a specific case where %fs is not preserved? It sounds like %fs is never set to a value in Wine. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 17:35:00 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A32A416A505 for ; Thu, 27 Jul 2006 17:35:00 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id D175243D46 for ; Thu, 27 Jul 2006 17:34:59 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k6RHYrn5078521; Thu, 27 Jul 2006 13:34:58 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 27 Jul 2006 11:28:19 -0400 User-Agent: KMail/1.9.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200607271128.20025.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 27 Jul 2006 13:34:59 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1623/Wed Jul 26 18:35:11 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: =?utf-8?q?=E6=9D=8E=E5=B0=9A=E6=9D=B0?= Subject: Re: A question about ipcperm() call? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 17:35:00 -0000 On Sunday 23 July 2006 22:07, =E6=9D=8E=E5=B0=9A=E6=9D=B0 wrote: > The code for ipcperm() call : > 93 if (mode & IPC_M) { > 94 error =3D suser(td); > 95 if (error) > 96 return (error); > 97 } > 116 if ((mode & perm->mode) !=3D mode) { > 117 if (suser(td) !=3D 0) > 118 return (EACCES); > 119 } >=20 > why not directly return the error in line 94? If suser() returns 0 and you just did 'return(suser(td))' then you would no= t=20 perform the additional security check in lines 116-119 which could result i= n=20 allowing access to an IPC object when it should be restricted. =2D-=20 John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 17:35:18 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0FBD16A515 for ; Thu, 27 Jul 2006 17:35:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id A717643D46 for ; Thu, 27 Jul 2006 17:35:00 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k6RHYrn6078521; Thu, 27 Jul 2006 13:34:59 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 27 Jul 2006 11:41:00 -0400 User-Agent: KMail/1.9.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200607271141.01285.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 27 Jul 2006 13:34:59 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1623/Wed Jul 26 18:35:11 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: =?utf-8?q?=E6=9D=8E=E5=B0=9A=E6=9D=B0?= Subject: Re: A bug in semctl() X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 17:35:18 -0000 On Wednesday 26 July 2006 03:50, =E6=9D=8E=E5=B0=9A=E6=9D=B0 wrote: > In file kern/sysv_sem.c: > 554 __semctl(td, uap) > 555 struct thread *td; > 556 struct __semctl_args *uap; > 557 { > 558 int semid =3D uap->semid; << 559 int semnum =3D uap->semnum; > 560 int cmd =3D uap->cmd; > 561 u_short *array; > 562 union semun *arg =3D uap->arg; > 563 union semun real_arg; > 564 struct ucred *cred =3D td->td_ucred; > 565 int i, rval, error; > 566 struct semid_ds sbuf; > 567 struct semid_kernel *semakptr; > 568 struct mtx *sema_mtxp; > 569 u_short usval, count; > 570 > 571 DPRINTF(("call to semctl(%d, %d, %d, 0x%x)\n", > 572 semid, semnum, cmd, arg)); > 573 if (!jail_sysvipc_allowed && jailed(td->td_ucred)) > 574 return (ENOSYS); > 575 > 576 array =3D NULL; > 577 > 578 switch(cmd) { > 579 case SEM_STAT: > 580 if (semid < 0 || semid >=3D seminfo.semmni) << 581 return (EINVAL); > 582 if ((error =3D copyin(arg, &real_arg,=20 sizeof(real_arg))) !=3D 0) > 583 return (error); > 584 semakptr =3D &sema[semid];<<=20 > >From line 558 to line 578, there must be a mechism to convert the > sem_id to the internal sema array index. In fact, it was missing, > which make the semctl syscall not work well. Actually, this is on purpose. SEM_STAT is just used for Linux binaries, an= d=20 they apparently specify a kernel semid rather than a user one for this=20 specific request. =2D-=20 John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 17:35:18 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 070F216A51A for ; Thu, 27 Jul 2006 17:35:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC66043D4C for ; Thu, 27 Jul 2006 17:35:00 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k6RHYrn4078521; Thu, 27 Jul 2006 13:34:55 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 27 Jul 2006 11:24:10 -0400 User-Agent: KMail/1.9.1 References: <7ADD22A7-42DE-49D8-B411-DBA4CB2FA0CD@bleepsoft.com> In-Reply-To: <7ADD22A7-42DE-49D8-B411-DBA4CB2FA0CD@bleepsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607271124.10771.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 27 Jul 2006 13:34:58 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1623/Wed Jul 26 18:35:11 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: "R. Tyler Ballance" Subject: Re: Building a sandboxed kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 17:35:18 -0000 On Saturday 22 July 2006 21:07, R. Tyler Ballance wrote: > I'm working on a project that relies on me building kernels outside > of the standard /usr/src (typically ~/perforce/projects/ ) on my > relatively standard 6.1-STABLE workstation. I'm wondering if I'd be > best suited by setting up a jail for kernel builds, I'm following > this doc: http://people.freebsd.org/~cognet/freebsd_arm.txt loosely > because I've created a new "arch folder" in src/sys for the kernel > code that I want to build (right now it's unmodified i386 code) > > Between varying versions of userland tools (like config(8)) and path > troubles, I'm wondering what tips anybody has to doing non-standard > builds of the kernel (non-standard being not in /usr/src and not the > host arch) > > Currently the make command I'm using, which doesn't work, is (/usr/ > obj is chmod'd 777): > > make TARGET_ARCH=iguana DESTDIR=/home/tyler/iguana buildkernel > > > Any suggestions? For the case where /usr/src is the same branch you can do this (I do this to test-compile cross-builds where the kernel tree isn't in /usr/src/sys): % cd /usr/src % make TARGET_ARCH=amd64 kernel-toolchain % make TARGET_ARCH=amd64 buildkernel KERNSRCDIR=/home/jhb/work/p4/smpng \ NO_KERNELCLEAN=yes -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 17:44:15 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF39516A4E1 for ; Thu, 27 Jul 2006 17:44:15 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 62DC843D6E for ; Thu, 27 Jul 2006 17:44:12 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 10769 invoked by uid 399); 27 Jul 2006 17:44:11 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 27 Jul 2006 17:44:11 -0000 Message-ID: <44C8FB65.9020102@FreeBSD.org> Date: Thu, 27 Jul 2006 10:44:05 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.4 (X11/20060604) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG References: <200607271150.k6RBoM9p031745@lurza.secnetix.de> In-Reply-To: <200607271150.k6RBoM9p031745@lurza.secnetix.de> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: [PATCH] adding two new options to 'cp' X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 17:44:16 -0000 Oliver Fromme wrote: > Eric Anderson wrote: > > I'm tired of trying to use rsync or gcp (which doesn't like symlinks > > often) to copy trees of files/directories using hard links, so I added > > the gcp-ish options -a and -l. > > > > -a is 'archive' mode, which is just a quick form of -PpR. > > -P is the default anyway, so -a would only replace -Rp. > I don't think saving one letter justifies introducing a new > option. You can use an alias or shell function. > > > -l is 'link' mode, where regular files get hard linked instead of copied. > > > > So, you can mimic an entire tree with something like: > > > > cp -al /from/ /to/ > > > > and it's fast too! > > You can do the same with existing tools in a portable > (and thus preferable) way: > > cd /from; find -d . | cpio -dumpl /to While I don't want to stifle anyone's creativity, I agree with Oliver (and other posters) on this one. The Unix way of doing things is small programs that do their jobs well, tied together to accomplish bigger things. Doug -- This .signature sanitized for your protection From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 18:04:14 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 293FA16A4DD for ; Thu, 27 Jul 2006 18:04:14 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (megan.kiwi-computer.com [63.224.10.3]) by mx1.FreeBSD.org (Postfix) with SMTP id 717AA43D4C for ; Thu, 27 Jul 2006 18:04:13 +0000 (GMT) (envelope-from rick@kiwi-computer.com) Received: (qmail 48435 invoked by uid 2001); 27 Jul 2006 18:04:12 -0000 Date: Thu, 27 Jul 2006 13:04:12 -0500 From: "Rick C. Petty" To: Steve Ames Message-ID: <20060727180412.GB48057@megan.kiwi-computer.com> References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> <20060727134948.GA3755@energistic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060727134948.GA3755@energistic.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 18:04:14 -0000 On Thu, Jul 27, 2006 at 09:49:48AM -0400, Steve Ames wrote: > On Thu, Jul 27, 2006 at 02:21:59PM +0200, Joerg Sonnenberger wrote: > > > > DragonFly disklabels allow 16 entries by default, FreeBSD still limits > > it to 8. That's why you can't read it directly. > > Are there plans to bump the default up from 8? I'm honestly torn on > this topic whenever I install a new system. On the one hand I like > having a lot of discrete mountpoints to control potential usage. On > the other hand with drive space being so inexpensive I sometimes > wonder if I need to bother and can get away with very few mountpoints. I would think that cheap disk space would mean larger disks which implies more mountpoints ??? > On very large disks (or arrays that appear as a single disk) I have > to create multiple slices in order to get more than 8 mountpoints. Its > an extra hoop to jump through. Use gpt on non boot-disks, or use gvinum if you have lots of storage and like the inherent advantage of named labels, striping, and redundancy. I wasn't very happy with gpt or bsdlabel recently because you aren't allowed to modify the partitions if the gpt/bsdlabel is in use (i.e. one of the other partitions is currently mounted as a filesystem). I hope the GEOM people are working to improve this. -- Rick C. Petty From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 17:48:12 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEE8D16A4E2; Thu, 27 Jul 2006 17:48:12 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (palm.hoeg.nl [83.98.131.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03B1843D60; Thu, 27 Jul 2006 17:48:08 +0000 (GMT) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id B1EC81CCFF; Thu, 27 Jul 2006 19:48:07 +0200 (CEST) Date: Thu, 27 Jul 2006 19:48:07 +0200 From: Ed Schouten To: John Baldwin Message-ID: <20060727174807.GL48334@hoeg.nl> References: <200607271141.01285.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lYetfuAxy9ic4HK3" Content-Disposition: inline In-Reply-To: <200607271141.01285.jhb@freebsd.org> User-Agent: Mutt/1.5.12-2006-07-14 X-Mailman-Approved-At: Thu, 27 Jul 2006 18:16:35 +0000 Cc: FreeBSD Hackers , ????????? Subject: Re: A bug in semctl() X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD Hackers List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 17:48:13 -0000 --lYetfuAxy9ic4HK3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * John Baldwin wrote: > Actually, this is on purpose. SEM_STAT is just used for Linux binaries, = and=20 > they apparently specify a kernel semid rather than a user one for this=20 > specific request. Yes. Below is a snippet from the semctl(2) manpage on a Linux machine: | SEM_STAT (Linux specific) | Returns a semid_ds structure as for IPC_STAT. However, the | semid argument is not a semaphore identifier, but instead | an index into the kernel's internal array that maintains | information about all semaphore sets on the system. Yours, --=20 Ed Schouten WWW: http://g-rave.nl/ --lYetfuAxy9ic4HK3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEyPxX52SDGA2eCwURAr6YAJ9JZwX3M4ikth49ZXRvC96HQKRVnACdG0F+ 0KRfmLkNyoE0T3rGmqR+FH4= =mk7l -----END PGP SIGNATURE----- --lYetfuAxy9ic4HK3-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 18:28:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A084B16A553 for ; Thu, 27 Jul 2006 18:28:42 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 189A543DD3 for ; Thu, 27 Jul 2006 18:28:19 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 48624 invoked by uid 1001); 27 Jul 2006 18:28:19 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Thu, 27 Jul 2006 14:28:18 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17609.1474.618423.970137@bhuda.mired.org> Date: Thu, 27 Jul 2006 14:28:18 -0400 To: rick-freebsd@kiwi-computer.com In-Reply-To: <20060727180412.GB48057@megan.kiwi-computer.com> References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> <20060727134948.GA3755@energistic.com> <20060727180412.GB48057@megan.kiwi-computer.com> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 18:28:42 -0000 In <20060727180412.GB48057@megan.kiwi-computer.com>, Rick C. Petty typed: > On Thu, Jul 27, 2006 at 09:49:48AM -0400, Steve Ames wrote: > > On Thu, Jul 27, 2006 at 02:21:59PM +0200, Joerg Sonnenberger wrote: > > > DragonFly disklabels allow 16 entries by default, FreeBSD still limits > > > it to 8. That's why you can't read it directly. > > Are there plans to bump the default up from 8? I'm honestly torn on > > this topic whenever I install a new system. On the one hand I like > > having a lot of discrete mountpoints to control potential usage. On > > the other hand with drive space being so inexpensive I sometimes > > wonder if I need to bother and can get away with very few mountpoints. > I would think that cheap disk space would mean larger disks which implies > more mountpoints ??? Nope. One of the historical uses of partitions was to act as firewalls between subsystems, so that subsystem A running out of space didn't cause subsystem B to die for lack of space. This had the downside of making it more likely that one of the two would run out of space because the excess space from another subsystem could only be used by it. With cheap disk space, you overallocate by enough to give you plenty of warning before you have to deal with the issue. You can safely share that space, and doing so means you have to "deal with the issue" less often. These days, the only technical reason I know of for having separate mountpoints is because you want to run commands that work on filesystems on the two parts with different arguments or under different conditions. > I wasn't very happy with gpt or bsdlabel recently because you aren't > allowed to modify the partitions if the gpt/bsdlabel is in use (i.e. one > of the other partitions is currently mounted as a filesystem). I hope the > GEOM people are working to improve this. Yet another reason for having fewer partitions: you're less likely to want to modify them :-). http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 18:40:44 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76C1916A4DD for ; Thu, 27 Jul 2006 18:40:44 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id E260543D6E for ; Thu, 27 Jul 2006 18:40:43 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 258082089; Thu, 27 Jul 2006 20:40:39 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 0E9932086; Thu, 27 Jul 2006 20:40:39 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id F19E133C31; Thu, 27 Jul 2006 20:40:38 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: maksim yevmenkin References: <1153997829.12770@origin.intron.ac> <864px31eyz.fsf@xps.des.no> <86psfryvvo.fsf@xps.des.no> <44C8CFA2.3000400@savvis.net> Date: Thu, 27 Jul 2006 20:40:38 +0200 In-Reply-To: <44C8CFA2.3000400@savvis.net> (maksim yevmenkin's message of "Thu, 27 Jul 2006 07:37:22 -0700") Message-ID: <868xme28nt.fsf@xps.des.no> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, Intron Subject: Re: How to Use ddb(4)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 18:40:44 -0000 maksim yevmenkin writes: > Dag-Erling Sm=F8rgrav writes: > > No, kbdmux needs to be fixed so it works in DDB. > actually, atkbd(4) needs to be fixed to support "polled" mode :) It used to work fine before kbdmux(4) came along... DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 18:59:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 092DA16A4E0 for ; Thu, 27 Jul 2006 18:59:49 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id A547B43D49 for ; Thu, 27 Jul 2006 18:59:48 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id D25D53BE58; Thu, 27 Jul 2006 13:59:47 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 04886-04-6; Thu, 27 Jul 2006 13:59:47 -0500 (CDT) Received: from [10.12.163.251] (unknown [10.12.163.251]) by mailgate1b.savvis.net (Postfix) with ESMTP id 5F2F63BE27; Thu, 27 Jul 2006 13:59:47 -0500 (CDT) Message-ID: <44C90D22.5010607@savvis.net> Date: Thu, 27 Jul 2006 11:59:46 -0700 From: Maksim Yevmenkin User-Agent: Thunderbird 1.5.0.2 (X11/20060603) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <1153997829.12770@origin.intron.ac> <864px31eyz.fsf@xps.des.no> <86psfryvvo.fsf@xps.des.no> <44C8CFA2.3000400@savvis.net> <868xme28nt.fsf@xps.des.no> In-Reply-To: <868xme28nt.fsf@xps.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at savvis.net Cc: freebsd-hackers@freebsd.org, Intron Subject: Re: How to Use ddb(4)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 18:59:49 -0000 Dag-Erling Smørgrav wrote: > maksim yevmenkin writes: >> Dag-Erling Smørgrav writes: >>> No, kbdmux needs to be fixed so it works in DDB. >> actually, atkbd(4) needs to be fixed to support "polled" mode :) > > It used to work fine before kbdmux(4) came along... because it makes certain assumptions about console (i.e. syscons(4)) driver. anyway, the link i posted in previous email contains a patch that should fix problems with kbdmux(4) and atkbd(4) not working in ddb(4), mid-boot (rootfs prompt, geli prompt, etc). so far i only got one (successful) report. would people please give it a try to see if work, so i can commit it. thanks, max From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 19:04:07 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC37616A4DE for ; Thu, 27 Jul 2006 19:04:07 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe13.swip.net [212.247.155.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1FE443D58 for ; Thu, 27 Jul 2006 19:04:06 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw== X-Cloudmark-Score: 0.000000 [] Received: from [193.217.38.32] (HELO [10.0.0.184]) by mailfe13.swip.net (CommuniGate Pro SMTP 5.0.8) with ESMTP id 74311083; Thu, 27 Jul 2006 21:04:04 +0200 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Thu, 27 Jul 2006 21:04:11 +0200 User-Agent: KMail/1.7 References: <1153997829.12770@origin.intron.ac> <44C8CFA2.3000400@savvis.net> <868xme28nt.fsf@xps.des.no> In-Reply-To: <868xme28nt.fsf@xps.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200607272104.13079.hselasky@c2i.net> Cc: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= , Intron Subject: Re: How to Use ddb(4)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 19:04:07 -0000 On Thursday 27 July 2006 20:40, Dag-Erling Sm=F8rgrav wrote: > maksim yevmenkin writes: > > Dag-Erling Sm=F8rgrav writes: > > > No, kbdmux needs to be fixed so it works in DDB. > > > > actually, atkbd(4) needs to be fixed to support "polled" mode :) > > It used to work fine before kbdmux(4) came along... > Just a comment: Don't forget to lock Giant before calling anything in the=20 keyboard layer. That means DDB must lock Giant, else at least my new USB=20 keyboard driver will panic, saying Giant is not owned. The old USB keyboard= =20 driver did not care about this. =2D-HPS From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 19:05:56 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D91F16A4E2 for ; Thu, 27 Jul 2006 19:05:56 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C23043D67 for ; Thu, 27 Jul 2006 19:05:47 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id BBD2A2089; Thu, 27 Jul 2006 21:05:43 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id AE9672082; Thu, 27 Jul 2006 21:05:43 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 8DD0C33C31; Thu, 27 Jul 2006 21:05:43 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Maksim Yevmenkin References: <1153997829.12770@origin.intron.ac> <864px31eyz.fsf@xps.des.no> <86psfryvvo.fsf@xps.des.no> <44C8CFA2.3000400@savvis.net> <868xme28nt.fsf@xps.des.no> <44C90D22.5010607@savvis.net> Date: Thu, 27 Jul 2006 21:05:43 +0200 In-Reply-To: <44C90D22.5010607@savvis.net> (Maksim Yevmenkin's message of "Thu, 27 Jul 2006 11:59:46 -0700") Message-ID: <86slkmzx4o.fsf@xps.des.no> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, Intron Subject: Re: How to Use ddb(4)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 19:05:56 -0000 Maksim Yevmenkin writes: > so far i only got one (successful) report. would people please give > it a try to see if work, so i can commit it. Please commit it. I don't see how it can do any harm. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 19:15:15 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EF6116A4DF for ; Thu, 27 Jul 2006 19:15:15 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out2.blueyonder.co.uk (smtp-out2.blueyonder.co.uk [195.188.213.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20A5D43D55 for ; Thu, 27 Jul 2006 19:15:13 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.146] (helo=anti-virus03-09) by smtp-out2.blueyonder.co.uk with smtp (Exim 4.52) id 1G6BKC-00068L-0J; Thu, 27 Jul 2006 20:15:12 +0100 Received: from [82.41.35.166] (helo=[192.168.0.2]) by asmtp-out6.blueyonder.co.uk with esmtp (Exim 4.52) id 1G6BKB-0005b4-Am; Thu, 27 Jul 2006 20:15:11 +0100 Message-ID: <44C910BE.9000108@dial.pipex.com> Date: Thu, 27 Jul 2006 20:15:10 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20060515 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> <20060727134948.GA3755@energistic.com> <20060727180412.GB48057@megan.kiwi-computer.com> <17609.1474.618423.970137@bhuda.mired.org> In-Reply-To: <17609.1474.618423.970137@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 19:15:15 -0000 Mike Meyer wrote: >In <20060727180412.GB48057@megan.kiwi-computer.com>, Rick C. Petty typed: > > >>On Thu, Jul 27, 2006 at 09:49:48AM -0400, Steve Ames wrote: >> >> >>>On Thu, Jul 27, 2006 at 02:21:59PM +0200, Joerg Sonnenberger wrote: >>> >>> >>>>DragonFly disklabels allow 16 entries by default, FreeBSD still limits >>>>it to 8. That's why you can't read it directly. >>>> >>>> >>>Are there plans to bump the default up from 8? I'm honestly torn on >>>this topic whenever I install a new system. On the one hand I like >>>having a lot of discrete mountpoints to control potential usage. On >>>the other hand with drive space being so inexpensive I sometimes >>>wonder if I need to bother and can get away with very few mountpoints. >>> >>> >>I would think that cheap disk space would mean larger disks which implies >>more mountpoints ??? >> >> > >Nope. One of the historical uses of partitions was to act as firewalls >between subsystems, so that subsystem A running out of space didn't >cause subsystem B to die for lack of space. This had the downside of >making it more likely that one of the two would run out of space >because the excess space from another subsystem could only be used by >it. With cheap disk space, you overallocate by enough to give you >plenty of warning before you have to deal with the issue. You can >safely share that space, and doing so means you have to "deal with the >issue" less often. > > You assume that "running out of space" happens over time, but with some runaway process logging to a file, for example, the partition filling up will still happen without you expecting it. It might take a bit longer with a big disk, but 20 minutes instead of 5 minutes isn't much different in terms of warning. Fill /tmp or /var and many things can fail. Fill /home and it's just users who suffer a little but mail, demons etc. just carry on. A further reason to separate partitions is that dump works at the level of a partition. Different partitions may have very different backup requirements, and for those of us without huge tape drives, partitioning to a size that can be dumped on one tape makes life easier. In some environments, fewer partitions may indeed be the new norm, but in others it would not. Personally, I would like a limit of 16. It would mean that I could fit all my regular partitions inside a single slice, freeing up other slices for, for example, experimenting with 64-bit, or -current, or whatever. Bootable FreeBSD slices will be stuck at 4 for the foreseeable future - extending the number of partitions within a slice frees up slices, which are the really limited resource. I have no real idea how hard it would be to extend from 8 to 16, but if the effort required were reasonably low, then it would get my vote. --Alex From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 20:25:10 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D845516A4DD for ; Thu, 27 Jul 2006 20:25:09 +0000 (UTC) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3381F43D49 for ; Thu, 27 Jul 2006 20:25:08 +0000 (GMT) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (localhost [IPv6:::1]) by srv1.cosmo-project.de (8.12.10/8.12.10) with ESMTP id k6RKP6nZ079142 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 27 Jul 2006 22:25:06 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.12.10/8.12.10/Submit) with UUCP id k6RKP6Zm079141 for freebsd-hackers@freebsd.org; Thu, 27 Jul 2006 22:25:06 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: from titan.klemm.apsfilter.org (localhost.klemm.apsfilter.org [127.0.0.1]) by klemm.apsfilter.org (8.13.6/8.13.4) with ESMTP id k6RKL5lk014922 for ; Thu, 27 Jul 2006 22:21:05 +0200 (CEST) (envelope-from andreas@titan.klemm.apsfilter.org) Received: (from andreas@localhost) by titan.klemm.apsfilter.org (8.13.6/8.13.4/Submit) id k6RKL5Mp014921 for freebsd-hackers@freebsd.org; Thu, 27 Jul 2006 22:21:05 +0200 (CEST) (envelope-from andreas) Date: Thu, 27 Jul 2006 22:21:05 +0200 From: Andreas Klemm To: freebsd-hackers@freebsd.org Message-ID: <20060727202105.GA14724@titan.klemm.apsfilter.org> References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> <20060727134948.GA3755@energistic.com> <20060727180412.GB48057@megan.kiwi-computer.com> <17609.1474.618423.970137@bhuda.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17609.1474.618423.970137@bhuda.mired.org> X-Operating-System: FreeBSD 6.1-STABLE X-Disclaimer: A free society is one where it is safe to be unpopular User-Agent: Mutt/1.5.11 Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 20:25:10 -0000 On Thu, Jul 27, 2006 at 02:28:18PM -0400, Mike Meyer wrote: > In <20060727180412.GB48057@megan.kiwi-computer.com>, Rick C. Petty typed: > > On Thu, Jul 27, 2006 at 09:49:48AM -0400, Steve Ames wrote: > > > On Thu, Jul 27, 2006 at 02:21:59PM +0200, Joerg Sonnenberger wrote: > > > > DragonFly disklabels allow 16 entries by default, FreeBSD still limits > > > > it to 8. That's why you can't read it directly. > > > Are there plans to bump the default up from 8? I'm honestly torn on > > > this topic whenever I install a new system. On the one hand I like > > > having a lot of discrete mountpoints to control potential usage. On > > > the other hand with drive space being so inexpensive I sometimes > > > wonder if I need to bother and can get away with very few mountpoints. > > I would think that cheap disk space would mean larger disks which implies > > more mountpoints ??? > > Nope. One of the historical uses of partitions was to act as firewalls > between subsystems, so that subsystem A running out of space didn't > cause subsystem B to die for lack of space. This had the downside of > making it more likely that one of the two would run out of space > because the excess space from another subsystem could only be used by > it. With cheap disk space, you overallocate by enough to give you > plenty of warning before you have to deal with the issue. You can > safely share that space, and doing so means you have to "deal with the > issue" less often. > > These days, the only technical reason I know of for having separate > mountpoints is because you want to run commands that work on > filesystems on the two parts with different arguments or under > different conditions. Well I still prefer to "design" my filesystems no matter how big disks are. So I have better control of what needs backup using dump and when I need to restore parts of my disk its also quicker and more reliable to restore a subtree. Also I'd gues that its still valid that less file movement in root filesystem increases robustness if you have a power outage. Same true for other important filesystems. Also it makes it easier to upgrade a system, since you only nail / and /usr, if the rest is in other filesystems. Also its easier to newfs "/" and "/usr", if "/var", "/usr/local" and "/usr/X11R6", "/home", ... are on differnet filesystems. Also you can increase system performance by choosing bigger block and frag size in filesystems with bigger files on average. If you have a news filesystem you perhaps want to finetune settings of filesystem to have more inodes available ... You see, I think there is still demand for using many filesystems if you are open minded for having the best support in every "shitty" situation ;-) Andreas /// -- Andreas Klemm - Powered by FreeBSD 6 Need a magic printfilter today ? -> http://www.apsfilter.org/ From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 20:30:08 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C6A916A4E6 for ; Thu, 27 Jul 2006 20:30:08 +0000 (UTC) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 213EB43D67 for ; Thu, 27 Jul 2006 20:30:06 +0000 (GMT) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (localhost [IPv6:::1]) by srv1.cosmo-project.de (8.12.10/8.12.10) with ESMTP id k6RKU5nZ079214 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 27 Jul 2006 22:30:05 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.12.10/8.12.10/Submit) with UUCP id k6RKU5A9079213 for freebsd-hackers@freebsd.org; Thu, 27 Jul 2006 22:30:05 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: from titan.klemm.apsfilter.org (localhost.klemm.apsfilter.org [127.0.0.1]) by klemm.apsfilter.org (8.13.6/8.13.4) with ESMTP id k6RKPS7L014990 for ; Thu, 27 Jul 2006 22:25:28 +0200 (CEST) (envelope-from andreas@titan.klemm.apsfilter.org) Received: (from andreas@localhost) by titan.klemm.apsfilter.org (8.13.6/8.13.4/Submit) id k6RKPSSW014989 for freebsd-hackers@freebsd.org; Thu, 27 Jul 2006 22:25:28 +0200 (CEST) (envelope-from andreas) Date: Thu, 27 Jul 2006 22:25:28 +0200 From: Andreas Klemm To: freebsd-hackers@freebsd.org Message-ID: <20060727202528.GA14954@titan.klemm.apsfilter.org> References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060727122159.GB4217@britannica.bec.de> X-Operating-System: FreeBSD 6.1-STABLE X-Disclaimer: A free society is one where it is safe to be unpopular User-Agent: Mutt/1.5.11 Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 20:30:08 -0000 On Thu, Jul 27, 2006 at 02:21:59PM +0200, Joerg Sonnenberger wrote: > On Thu, Jul 27, 2006 at 08:39:37AM +0200, Andreas Klemm wrote: > > Later I wanted to mount the dfly filesystems on FreeBSD 6.1, > > of course still my main Unix ;-) But it wasn't possible. > > DragonFly disklabels allow 16 entries by default, FreeBSD still limits > it to 8. That's why you can't read it directly. > Hmm, for the sake of compatibility, wouldn't it have been an option, to add this extra bit to the end of the struct ? Andreas /// -- Andreas Klemm - Powered by FreeBSD 6 Need a magic printfilter today ? -> http://www.apsfilter.org/ From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 20:38:51 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39DAD16A4DD for ; Thu, 27 Jul 2006 20:38:51 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F31043D5A for ; Thu, 27 Jul 2006 20:38:47 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 996643BEBF; Thu, 27 Jul 2006 15:38:01 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 02458-01-46; Thu, 27 Jul 2006 15:38:01 -0500 (CDT) Received: from [10.12.163.251] (unknown [10.12.163.251]) by mailgate1b.savvis.net (Postfix) with ESMTP id C02E53BE27; Thu, 27 Jul 2006 15:38:00 -0500 (CDT) Message-ID: <44C92427.90502@savvis.net> Date: Thu, 27 Jul 2006 13:37:59 -0700 From: Maksim Yevmenkin User-Agent: Thunderbird 1.5.0.2 (X11/20060603) MIME-Version: 1.0 To: Hans Petter Selasky References: <1153997829.12770@origin.intron.ac> <44C8CFA2.3000400@savvis.net> <868xme28nt.fsf@xps.des.no> <200607272104.13079.hselasky@c2i.net> In-Reply-To: <200607272104.13079.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at savvis.net Cc: freebsd-hackers@freebsd.org, Intron , =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= Subject: Re: How to Use ddb(4)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 20:38:51 -0000 Hans Petter Selasky wrote: > On Thursday 27 July 2006 20:40, Dag-Erling Smørgrav wrote: >> maksim yevmenkin writes: >>> Dag-Erling Smørgrav writes: >>>> No, kbdmux needs to be fixed so it works in DDB. >>> actually, atkbd(4) needs to be fixed to support "polled" mode :) >> It used to work fine before kbdmux(4) came along... >> > > Just a comment: Don't forget to lock Giant before calling anything in the > keyboard layer. That means DDB must lock Giant, else at least my new USB > keyboard driver will panic, saying Giant is not owned. The old USB keyboard > driver did not care about this. well, there is more work to it, imo. we will have to address this when new usb sub-system comes into the three. thanks, max From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 20:42:29 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E74316A4DE for ; Thu, 27 Jul 2006 20:42:29 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 9B27B43D53 for ; Thu, 27 Jul 2006 20:42:24 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 51294 invoked by uid 1001); 27 Jul 2006 20:42:23 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Thu, 27 Jul 2006 16:42:20 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17609.9516.506115.204334@bhuda.mired.org> Date: Thu, 27 Jul 2006 16:42:20 -0400 To: "Michael R. Wayne" , Alex Zbyslaw In-Reply-To: <20060727185721.GC25626@manor.msen.com> References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> <20060727134948.GA3755@energistic.com> <20060727180412.GB48057@megan.kiwi-computer.com> <17609.1474.618423.970137@bhuda.mired.org> <44C910BE.9000108@dial.pipex.com> <20060727185721.GC25626@manor.msen.com> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 20:42:29 -0000 In <20060727185721.GC25626@manor.msen.com>, Michael R. Wayne typed: > On Thu, Jul 27, 2006 at 02:28:18PM -0400, Mike Meyer wrote: > > These days, the only technical reason I know of for having separate > > mountpoints is because you want to run commands that work on > > filesystems on the two parts with different arguments or under > > different conditions. > Or you want to run a bunch of jails. You don't need mount points to run jails. In fact, the man page (on 5.5, anyway) provides examples that *break* if you put the jails on a separate mount point. > Or you want to give a bunch > of users a big chunk of space and > quotas are a bad fit. That's a social reason, not a technical one. That used to be really common as well, but these days "a bunch of users" tend to get their own machine. In <44C910BE.9000108@dial.pipex.com>, Alex Zbyslaw typed: > Mike Meyer wrote: > >In <20060727180412.GB48057@megan.kiwi-computer.com>, Rick C. Petty typed: > >>On Thu, Jul 27, 2006 at 09:49:48AM -0400, Steve Ames wrote: > >>>On Thu, Jul 27, 2006 at 02:21:59PM +0200, Joerg Sonnenberger wrote: > >>>>DragonFly disklabels allow 16 entries by default, FreeBSD still limits > >>>>it to 8. That's why you can't read it directly. > >>>Are there plans to bump the default up from 8? I'm honestly torn on > >>>this topic whenever I install a new system. On the one hand I like > >>>having a lot of discrete mountpoints to control potential usage. On > >>>the other hand with drive space being so inexpensive I sometimes > >>>wonder if I need to bother and can get away with very few mountpoints. > >>I would think that cheap disk space would mean larger disks which implies > >>more mountpoints ??? > >Nope. One of the historical uses of partitions was to act as firewalls > >between subsystems, so that subsystem A running out of space didn't > >cause subsystem B to die for lack of space. This had the downside of > >making it more likely that one of the two would run out of space > >because the excess space from another subsystem could only be used by > >it. With cheap disk space, you overallocate by enough to give you > >plenty of warning before you have to deal with the issue. You can > >safely share that space, and doing so means you have to "deal with the > >issue" less often. > You assume that "running out of space" happens over time, but with some > runaway process logging to a file, for example, the partition filling up > will still happen without you expecting it. It might take a bit longer > with a big disk, but 20 minutes instead of 5 minutes isn't much > different in terms of warning. Yes, I'm assuming that "running out of space" happens over time. Sustained I/O speeds on modern hardware was around 100MB/sec last time I looked. So a good, large disk - say a terabyte raid (you need raid to get those performance numbers, so call it 2 500GB disks to keep it simple) - will take about three hours to fill *if you do nothing but write to the disk*. A runaway process - especially one generating log data - is normally doing other things that it's trying to log information about. A typical installation will have smaller, slower disks. A high-end installation with faster disks will almost certainly have lots more space as well. So it's perfectly reasonable to rely on disks to not fill up in a matter of minutes. In practice, log files are several orders of magnitude smaller than the actual data dealt with by most application. A few hundred megabytes is more than adequate log space for most systems, with runaway processes filling them in a day or so. So I give those systems a gigabyte of log space, 'cause disk is *cheap*. And yes, I separate /var from /home and /usr, but not because I'm worried about them running out of space. > Fill /tmp or /var and many things can fail. Fill /home and it's just > users who suffer a little but mail, demons etc. just carry on. You're being inconsistent. Log files normally go on /var, so if you fill that, your demons may well fail, depending on how they react to not being able to log messages. On the other hand, for some demons it makes sense to treat their data just like any other user data, so they'd be on /home, and suddenly they're failing when /home fills up. I had a system fall over for lack of disk space this month. It was an old system, that only had 16GB of disk for file storage, and the 300GB drive upgrade had already been ordered. It's a four-core 3GHz opteron system, doing ETL processing as fast as it's little chips can cycle. It took *five hours* to fill up when half of the data started collecting on it instead of being loaded into the database. If it had had the disk upgrade, it would have take a couple of days. > A further reason to separate partitions is that dump works at the level > of a partition. Different partitions may have very different backup > requirements, and for those of us without huge tape drives, partitioning > to a size that can be dumped on one tape makes life easier. That's one of the technical reasons I mentioned in the part you didn't quote. > In some environments, fewer partitions may indeed be the new norm, but > in others it would not. And in some environments, Windows is the norm. The question is - is there still a good technical reason for doing that? The two primary technical reasons I used to create partitions (firewalls for space and damage) are both pretty much dead. > Personally, I would like a limit of 16. It would mean that I could fit > all my regular partitions inside a single slice, freeing up other slices > for, for example, experimenting with 64-bit, or -current, or whatever. > Bootable FreeBSD slices will be stuck at 4 for the foreseeable future - > extending the number of partitions within a slice frees up slices, which > are the really limited resource. Why do you need lots of partitions for experimental systems? And if you need that, how often is it actually a win to give up the unlimited number of logical volumes you get in an extended partition to get one (1) extra bootable FreeBSD partition? Especially if some of the system you want to experiment with aren't as limited FreeBSD, and can boot off of logical volumes? Frankly, if you're really worried about bootable slices, you should be advocating giving FreeBSD the ability to boot from a logical volume. IIRC, someone did that once, but never got it into the tree. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 20:58:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9489A16A4E1 for ; Thu, 27 Jul 2006 20:58:53 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id B9A9643D49 for ; Thu, 27 Jul 2006 20:58:52 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 51647 invoked by uid 1001); 27 Jul 2006 20:58:51 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Thu, 27 Jul 2006 16:58:51 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17609.10507.322936.614793@bhuda.mired.org> Date: Thu, 27 Jul 2006 16:58:51 -0400 To: Andreas Klemm In-Reply-To: <20060727202105.GA14724@titan.klemm.apsfilter.org> References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> <20060727134948.GA3755@energistic.com> <20060727180412.GB48057@megan.kiwi-computer.com> <17609.1474.618423.970137@bhuda.mired.org> <20060727202105.GA14724@titan.klemm.apsfilter.org> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 20:58:53 -0000 In <20060727202105.GA14724@titan.klemm.apsfilter.org>, Andreas Klemm typed: > On Thu, Jul 27, 2006 at 02:28:18PM -0400, Mike Meyer wrote: > > These days, the only technical reason I know of for having separate > > mountpoints is because you want to run commands that work on > > filesystems on the two parts with different arguments or under > > different conditions. > Well I still prefer to "design" my filesystems no matter how big > disks are. Yes, and most of those qualify as needing to "run commands that workon filesystems on the two parts with different arguments ...". > Also I'd gues that its still valid that less file movement > in root filesystem increases robustness if you have a power outage. > Same true for other important filesystems. Actually, it one of the FS gurus convincing me that this was no longer true that converted me to the idea that reducing the file system count was a good idea. What you say was certainly true for 4.2BSD, but when was the last time you saw an entire file system toasted when something failed hard? Or even significant damage to files that weren't actually in transit at the time? I know the last time it happened to me - it was over a decade ago. I had a desktop Solaris box I'd set up as web server because the IT department was a typical IT department. So it wasn't on batteries like every other server in the place. We took a power hit, and it crashed hard. Power came back, and it started fsck'ing it's file system. Partway through that we got a *second* power hit, so it crashed hard in the middle of fsck'ing. This power outage lasted long enough that the backup generators kicked in, so it came back up and started fsck'ing again. At which piont the backup generators cut out, because they hadn't been refueled after the last outage. So it crashed hard *again* in the middle of fsck'ing the file system. The file system was unrecoverable. > Also it makes it easier to upgrade a system, since you only nail > / and /usr, if the rest is in other filesystems. > > Also its easier to newfs "/" and "/usr", if "/var", "/usr/local" > and "/usr/X11R6", "/home", ... are on differnet filesystems. Right. I typically install / and /usr as distinct files systems for just that reason (/ and /usr have different backup & recovery strategies and I use dump, so that's why they are two partitions). So why does / need to be different from /var, /usr different from /usr/X11R6 and /home different from /usr/local? Seriously now - what I just described is my typical install. > You see, I think there is still demand for using many filesystems > if you are open minded for having the best support in every "shitty" > situation ;-) Well, there are always special cases. But hardware is so cheap these days, I'm used to fine-tuning the *system*, not just the partition. If something is so critical that it needs it's own partition, it's probably so critical that it needs it's own system as well. In fact, most of the thing I work on these days are so critical that they need several systems, half of them at a second site with automatic failover between them. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 21:08:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB71516A4DD; Thu, 27 Jul 2006 21:08:42 +0000 (UTC) (envelope-from tijl@ulyssis.org) Received: from outmx009.isp.belgacom.be (outmx009.isp.belgacom.be [195.238.5.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 565EB43D49; Thu, 27 Jul 2006 21:08:41 +0000 (GMT) (envelope-from tijl@ulyssis.org) Received: from outmx009.isp.belgacom.be (localhost [127.0.0.1]) by outmx009.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6RL8cUt029585; Thu, 27 Jul 2006 23:08:39 +0200 (envelope-from ) Received: from kalimero.kotnet.org (84.41-245-81.adsl-dyn.isp.belgacom.be [81.245.41.84]) by outmx009.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6RL8SQf029502; Thu, 27 Jul 2006 23:08:28 +0200 (envelope-from ) Received: from kalimero.kotnet.org (kalimero.kotnet.org [127.0.0.1]) by kalimero.kotnet.org (8.13.6/8.13.6) with ESMTP id k6RL8RQ3004931; Thu, 27 Jul 2006 23:08:28 +0200 (CEST) (envelope-from tijl@ulyssis.org) From: Tijl Coosemans To: freebsd-emulation@freebsd.org Date: Thu, 27 Jul 2006 23:08:22 +0200 User-Agent: KMail/1.9.3 References: <200607221914.15826.lofi@freebsd.org> <200607250358.21457.tijl@ulyssis.org> <200607271121.17313.jhb@freebsd.org> In-Reply-To: <200607271121.17313.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2050574.CxlVPIfA9y"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607272308.27425.tijl@ulyssis.org> Cc: Daniel Eischen , freebsd-hackers@freebsd.org, Michael Nottebrock Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 21:08:42 -0000 --nextPart2050574.CxlVPIfA9y Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 27 July 2006 17:21, John Baldwin wrote: > On Monday 24 July 2006 21:58, Tijl Coosemans wrote: > > However, Wine/Windows uses %fs for TLS and it appears that the > > FreeBSD kernel doesn't preserve it. It always ends up pointing to > > GUDATA_SEL. > > The kernel should preserve %fs across syscalls, traps, and faults.=20 > Can you point to a specific case where %fs is not preserved? It > sounds like %fs is never set to a value in Wine. Yes, it was a combination of compiler optimizations and an inline=20 assembly block missing __volatile__. --nextPart2050574.CxlVPIfA9y Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQBEyStLdMR2xnarec8RAqZ7AJ9GAvaccJ2AOXet7rLSJHpSLSzolwCfUrMf 4KQ0DZCCpmV+5bxq6uXCv4M= =Ndp6 -----END PGP SIGNATURE----- --nextPart2050574.CxlVPIfA9y-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 21:12:05 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A487716A4E0 for ; Thu, 27 Jul 2006 21:12:05 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from hydra.bec.de (www.ostsee-abc.de [62.206.222.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3987743D55 for ; Thu, 27 Jul 2006 21:12:05 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (storm.stura.uni-rostock.de [139.30.252.72]) by hydra.bec.de (Postfix) with ESMTP id C321635707 for ; Thu, 27 Jul 2006 23:11:59 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1000) id 8153B6D0FE; Thu, 27 Jul 2006 23:11:38 +0200 (CEST) Date: Thu, 27 Jul 2006 23:11:38 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Message-ID: <20060727211138.GC10790@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> <20060727202528.GA14954@titan.klemm.apsfilter.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060727202528.GA14954@titan.klemm.apsfilter.org> User-Agent: Mutt/1.5.11 Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 21:12:05 -0000 On Thu, Jul 27, 2006 at 10:25:28PM +0200, Andreas Klemm wrote: > On Thu, Jul 27, 2006 at 02:21:59PM +0200, Joerg Sonnenberger wrote: > > On Thu, Jul 27, 2006 at 08:39:37AM +0200, Andreas Klemm wrote: > > > Later I wanted to mount the dfly filesystems on FreeBSD 6.1, > > > of course still my main Unix ;-) But it wasn't possible. > > > > DragonFly disklabels allow 16 entries by default, FreeBSD still limits > > it to 8. That's why you can't read it directly. > > > > Hmm, for the sake of compatibility, wouldn't it have been an option, > to add this extra bit to the end of the struct ? The layout of the struct has not changed. FreeBSD simply rejects the disk label because the number of entries is too large. Joerg From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 21:39:57 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FCD016A4DA; Thu, 27 Jul 2006 21:39:57 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id A59AB43D6D; Thu, 27 Jul 2006 21:39:53 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k6RLdqXu080692; Thu, 27 Jul 2006 17:39:52 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 27 Jul 2006 17:30:14 -0400 User-Agent: KMail/1.9.1 References: <200607271150.k6RBoM9p031745@lurza.secnetix.de> <44C8FB65.9020102@FreeBSD.org> In-Reply-To: <44C8FB65.9020102@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607271730.14998.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 27 Jul 2006 17:39:52 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1624/Thu Jul 27 13:11:25 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Doug Barton Subject: Re: [PATCH] adding two new options to 'cp' X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 21:39:57 -0000 On Thursday 27 July 2006 13:44, Doug Barton wrote: > Oliver Fromme wrote: > > Eric Anderson wrote: > > > I'm tired of trying to use rsync or gcp (which doesn't like symlinks > > > often) to copy trees of files/directories using hard links, so I added > > > the gcp-ish options -a and -l. > > > > > > -a is 'archive' mode, which is just a quick form of -PpR. > > > > -P is the default anyway, so -a would only replace -Rp. > > I don't think saving one letter justifies introducing a new > > option. You can use an alias or shell function. > > > > > -l is 'link' mode, where regular files get hard linked instead of copied. > > > > > > So, you can mimic an entire tree with something like: > > > > > > cp -al /from/ /to/ > > > > > > and it's fast too! > > > > You can do the same with existing tools in a portable > > (and thus preferable) way: > > > > cd /from; find -d . | cpio -dumpl /to > > While I don't want to stifle anyone's creativity, I agree with Oliver (and > other posters) on this one. The Unix way of doing things is small programs > that do their jobs well, tied together to accomplish bigger things. OTOH, 'cp -al' is a lot less to type. :) It also is not NIH as it is simulating the interface of another system. Maybe I'm just stodgy b/c I never use cpio(8) (it seems to be one of the more cryptic programs). -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 21:39:58 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A09216A4DF; Thu, 27 Jul 2006 21:39:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48C3443D72; Thu, 27 Jul 2006 21:39:53 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k6RLdqXv080692; Thu, 27 Jul 2006 17:39:53 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 27 Jul 2006 17:34:23 -0400 User-Agent: KMail/1.9.1 References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727202105.GA14724@titan.klemm.apsfilter.org> <17609.10507.322936.614793@bhuda.mired.org> In-Reply-To: <17609.10507.322936.614793@bhuda.mired.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607271734.24026.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 27 Jul 2006 17:39:53 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1624/Thu Jul 27 13:11:25 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Mike Meyer Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 21:39:58 -0000 On Thursday 27 July 2006 16:58, Mike Meyer wrote: > Right. I typically install / and /usr as distinct files systems for > just that reason (/ and /usr have different backup & recovery > strategies and I use dump, so that's why they are two partitions). So > why does / need to be different from /var, /usr different from > /usr/X11R6 and /home different from /usr/local? Seriously now - what I > just described is my typical install. In my case I still have /home in /usr/home, but I should start making it separate in the hope that I could mount /usr read-only most of the time reducing the time it takes to fsck when I crash my test machines. This is peculiar to an environ where one expects to crash a lot though. :) Even so, I would be looking at /, /usr, /var, /tmp, /home, and swap. Still under 7 ('c' is reserved). -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 21:40:21 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8913516A4F2 for ; Thu, 27 Jul 2006 21:40:20 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5123743D7B for ; Thu, 27 Jul 2006 21:40:08 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k6RLdqXw080692; Thu, 27 Jul 2006 17:39:53 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 27 Jul 2006 17:35:54 -0400 User-Agent: KMail/1.9.1 References: <1153997829.12770@origin.intron.ac> <868xme28nt.fsf@xps.des.no> <200607272104.13079.hselasky@c2i.net> In-Reply-To: <200607272104.13079.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200607271735.55199.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 27 Jul 2006 17:39:54 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1624/Thu Jul 27 13:11:25 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= , Intron , Hans Petter Selasky Subject: Re: How to Use ddb(4)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 21:40:21 -0000 On Thursday 27 July 2006 15:04, Hans Petter Selasky wrote: > On Thursday 27 July 2006 20:40, Dag-Erling Sm=F8rgrav wrote: > > maksim yevmenkin writes: > > > Dag-Erling Sm=F8rgrav writes: > > > > No, kbdmux needs to be fixed so it works in DDB. > > > > > > actually, atkbd(4) needs to be fixed to support "polled" mode :) > > > > It used to work fine before kbdmux(4) came along... > > >=20 > Just a comment: Don't forget to lock Giant before calling anything in the= =20 > keyboard layer. That means DDB must lock Giant, else at least my new USB= =20 > keyboard driver will panic, saying Giant is not owned. The old USB keyboa= rd=20 > driver did not care about this. DDB should not be acquiring locks or depend on being able to do so. When y= ou=20 panic the machine is an unknown state for one, and you really want to leave= =20 the overall system state as undisturbed as possible while in the debugger t= o=20 aid in debugging. =2D-=20 John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 21:47:13 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 981C416A4E1 for ; Thu, 27 Jul 2006 21:47:13 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out5.blueyonder.co.uk (smtp-out5.blueyonder.co.uk [195.188.213.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7D2043D70 for ; Thu, 27 Jul 2006 21:47:05 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.137] (helo=anti-virus01-08) by smtp-out5.blueyonder.co.uk with smtp (Exim 4.52) id 1G6Dh8-0006VH-FJ; Thu, 27 Jul 2006 22:47:02 +0100 Received: from [82.41.35.166] (helo=[192.168.0.2]) by asmtp-out2.blueyonder.co.uk with esmtp (Exim 4.52) id 1G6Dh7-0003zE-H0; Thu, 27 Jul 2006 22:47:01 +0100 Message-ID: <44C93454.5020404@dial.pipex.com> Date: Thu, 27 Jul 2006 22:47:00 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20060515 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> <20060727134948.GA3755@energistic.com> <20060727180412.GB48057@megan.kiwi-computer.com> <17609.1474.618423.970137@bhuda.mired.org> <44C910BE.9000108@dial.pipex.com> <20060727185721.GC25626@manor.msen.com> <17609.9516.506115.204334@bhuda.mired.org> In-Reply-To: <17609.9516.506115.204334@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 21:47:13 -0000 Mike Meyer wrote: >> You assume that "running out of space" happens over time, but with some >> >>runaway process logging to a file, for example, the partition filling up >>will still happen without you expecting it. It might take a bit longer >>with a big disk, but 20 minutes instead of 5 minutes isn't much >>different in terms of warning. >> >> > >Yes, I'm assuming that "running out of space" happens over >time. Sustained I/O speeds on modern hardware was around 100MB/sec >last time I looked. So a good, large disk - say a terabyte raid (you >need raid to get those performance numbers, so call it 2 500GB disks >to keep it simple) - will take about three hours to fill *if you do >nothing but write to the disk*. A runaway process - especially one >generating log data - is normally doing other things that it's trying >to log information about. > > I don't have terabyte raids and for me a "big" disk is 250Gb. A runaway system demon writing to disk might well do other things. A badly written user program might do nothing but write to disk. If you run servers that just run a bunch of standard ports and system demons, then this is unlikely to happen to you. If you work in an environment where one or more fallible programmers churn through gigabytes of data it's depressingly easy to accidentally do *nothing* but write to disk. >> A further reason to separate partitions is that dump works at the level >> of a partition. Different partitions may have very different backup >> requirements, and for those of us without huge tape drives, partitioning >> to a size that can be dumped on one tape makes life easier. > > > >That's one of the technical reasons I mentioned in the part you >didn't quote. > > To my mind, it only takes *one* technical reason. If I need multiple partitions to make backups easy, then arguments about log files are irrelevant :-) >Well, there are always special cases. But hardware is so cheap these >days, I'm used to fine-tuning the *system*, not just the partition. >If something is so critical that it needs it's own partition, it's >probably so critical that it needs it's own system as well. In fact, >most of the thing I work on these days are so critical that they need >several systems, half of them at a second site with automatic failover >between them. > Not everyone is in a position to throw money at everything and what's cheap to you isn't cheap to everyone. I can't possibly justify one system for everything that needs a partition, nor do I even feel the need to do that. If anything, it would be a major inconvenience. >Frankly, if you're really worried about >bootable slices, you should be advocating giving FreeBSD the ability >to boot from a logical volume. > Who said I didn't? I have no objection to such a facility and would welcome it. It just imagined that extending the number of partitions from 8 to 16 would have been easier than booting from logical slices. If booting from logical slices is easier then I'm all for it. --Alex From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 21:53:33 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B52916A4E5; Thu, 27 Jul 2006 21:53:33 +0000 (UTC) (envelope-from prvs=julian=356e8a28d@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BD8943D77; Thu, 27 Jul 2006 21:53:29 +0000 (GMT) (envelope-from prvs=julian=356e8a28d@elischer.org) Received: from unknown (HELO [192.168.2.4]) ([10.251.60.53]) by a50.ironport.com with ESMTP; 27 Jul 2006 14:53:30 -0700 Message-ID: <44C935D9.8040604@elischer.org> Date: Thu, 27 Jul 2006 14:53:29 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tijl Coosemans References: <200607221914.15826.lofi@freebsd.org> <200607250358.21457.tijl@ulyssis.org> <200607271121.17313.jhb@freebsd.org> <200607272308.27425.tijl@ulyssis.org> In-Reply-To: <200607272308.27425.tijl@ulyssis.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Daniel Eischen , freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org, Michael Nottebrock Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 21:53:33 -0000 Tijl Coosemans wrote: >On Thursday 27 July 2006 17:21, John Baldwin wrote: > > >>On Monday 24 July 2006 21:58, Tijl Coosemans wrote: >> >> >>>However, Wine/Windows uses %fs for TLS and it appears that the >>>FreeBSD kernel doesn't preserve it. It always ends up pointing to >>>GUDATA_SEL. >>> >>> >>The kernel should preserve %fs across syscalls, traps, and faults. >>Can you point to a specific case where %fs is not preserved? It >>sounds like %fs is never set to a value in Wine. >> >> > >Yes, it was a combination of compiler optimizations and an inline >assembly block missing __volatile__. > > > does this mean that wine will work from now on? i.e. is the fix being fed back into wine sources? From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 27 22:37:27 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DACE16A4DA for ; Thu, 27 Jul 2006 22:37:27 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 0446343D46 for ; Thu, 27 Jul 2006 22:37:26 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 53925 invoked by uid 1001); 27 Jul 2006 22:37:26 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Thu, 27 Jul 2006 18:37:26 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17609.16421.670624.80289@bhuda.mired.org> Date: Thu, 27 Jul 2006 18:37:25 -0400 To: Alex Zbyslaw In-Reply-To: <44C93454.5020404@dial.pipex.com> References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> <20060727134948.GA3755@energistic.com> <20060727180412.GB48057@megan.kiwi-computer.com> <17609.1474.618423.970137@bhuda.mired.org> <44C910BE.9000108@dial.pipex.com> <20060727185721.GC25626@manor.msen.com> <17609.9516.506115.204334@bhuda.mired.org> <44C93454.5020404@dial.pipex.com> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jul 2006 22:37:27 -0000 In <44C93454.5020404@dial.pipex.com>, Alex Zbyslaw typed: > Mike Meyer wrote: > >> You assume that "running out of space" happens over time, but with some > >>runaway process logging to a file, for example, the partition filling up > >>will still happen without you expecting it. It might take a bit longer > >>with a big disk, but 20 minutes instead of 5 minutes isn't much > >>different in terms of warning. > >Yes, I'm assuming that "running out of space" happens over > >time. Sustained I/O speeds on modern hardware was around 100MB/sec > >last time I looked. So a good, large disk - say a terabyte raid (you > >need raid to get those performance numbers, so call it 2 500GB disks > >to keep it simple) - will take about three hours to fill *if you do > >nothing but write to the disk*. A runaway process - especially one > >generating log data - is normally doing other things that it's trying > >to log information about. > I don't have terabyte raids and for me a "big" disk is 250Gb. In that case, you don't get 100MB/sec of throughput, either. Even if you've got a relatively fast single disk, you're going to be getting maybe 50MB/sec of throughput. So it's *still* going to take hours to fill the disk even if you do nothing but write to disk. And to complete the reprise of the paragraph you elided, if you've got a system that gets a lot more than 100MB/sec to disk, you almost certainly have a lot more disk than a terabyte. > A runaway system demon writing to disk might well do other things. A > badly written user program might do nothing but write to disk. If you > run servers that just run a bunch of standard ports and system demons, > then this is unlikely to happen to you. If you work in an environment > where one or more fallible programmers churn through gigabytes of data > it's depressingly easy to accidentally do *nothing* but write to disk. You know, that's exactly the kind of environment I work in. We churn through gigaROWS of data. We have processes whose sole job is to pull data and write it to disk. Even major failures (like losing the network connection to half the consumer machines) don't cause the disk to fill in minutes. More like days on a properly configured machine. That's because, even if your system is spending *all* of it's time doing nothing but writing to the disk, it'll take hours to fill the disk given most modern disk configurations. Disks have gotten bigger faster than they've gotten faster. So while you used to be able to fill a disk in minutes (or could you?), it takes a really strange configuration to do that now. > >> A further reason to separate partitions is that dump works at the level > >> of a partition. Different partitions may have very different backup > >> requirements, and for those of us without huge tape drives, partitioning > >> to a size that can be dumped on one tape makes life easier. > >That's one of the technical reasons I mentioned in the part you > >didn't quote. > To my mind, it only takes *one* technical reason. If I need multiple > partitions to make backups easy, then arguments about log files are > irrelevant :-) If you're going to count 1, 2, many, then we already have "many" partitions, and don't need more. Once you get into finer distinctions of "many", you need to figure out which reasons are actually valid, and which are spurious, so you can pick from among those manys. > >Well, there are always special cases. But hardware is so cheap these > >days, I'm used to fine-tuning the *system*, not just the partition. > >If something is so critical that it needs it's own partition, it's > >probably so critical that it needs it's own system as well. In fact, > >most of the thing I work on these days are so critical that they need > >several systems, half of them at a second site with automatic failover > >between them. > Not everyone is in a position to throw money at everything and what's > cheap to you isn't cheap to everyone. Boxes are cheaper than disk space - my last two low-end boxes cost less than my last small disk drive, even though I ordered them all about the same time. If you can afford the disk for some process, then chances are good you can afford a system instead, or as well. > I can't possibly justify one system for everything that needs a > partition, nor do I even feel the need to do that. If anything, it > would be a major inconvenience. My claim is that your "everything that needs a partition" probably includes things that don't. But to prove that, we need to examine the reasons you think those things need a partition. I believe the only one you've given so far - as a space firewall - is specious. Your arguments remind me of the environments I worked on in the 70s and 80s. Minis and mainframes that did all the computing for an organization. All the daemons that talked to the outside world ran on the same box as the developers ran compiles and tests on, etc. While that worked really well when it came to generating a robust OS, I haven't seen an environment like that in decades. Hell, most of my clients would shit bricks at the thought of putting their source or data on a machine that could be reached from the internet at large at all. Every developler has a box - or three - on their desks. The ETL boxes are distinct from the database boxes are distinct from the internal mail server is distinct from the external mail server, etc. If I want to have a process send email notices about something, I usually have to beat on them if I want a mail server on the box. And so on.... > >Frankly, if you're really worried about > >bootable slices, you should be advocating giving FreeBSD the ability > >to boot from a logical volume. > Who said I didn't? I have no objection to such a facility and would > welcome it. It just imagined that extending the number of partitions > from 8 to 16 would have been easier than booting from logical slices. > If booting from logical slices is easier then I'm all for it. You're not asking the right question just yet. The question shouldn't be "which is easier to add", but "which provides the most benefit for the least pain" (which subsumes the pain involved in adding it). I believe that the benefits of adding more partitions per slice are minimal - there are at least three ways to add more file systems that aren't bootable, and there's a better fix to the problem of wanting more bootable partitions - and the pain involved in upgrading a system across a change in the bsdlabel would be rather high. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 00:01:03 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A41A516A505 for ; Fri, 28 Jul 2006 00:01:03 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out2.blueyonder.co.uk (smtp-out2.blueyonder.co.uk [195.188.213.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5E2F43D4C for ; Fri, 28 Jul 2006 00:01:00 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.144] (helo=anti-virus03-07) by smtp-out2.blueyonder.co.uk with smtp (Exim 4.52) id 1G6Fmm-0006Bw-3C; Fri, 28 Jul 2006 01:01:00 +0100 Received: from [82.41.35.166] (helo=[192.168.0.2]) by asmtp-out6.blueyonder.co.uk with esmtp (Exim 4.52) id 1G6Fml-0005nC-8v; Fri, 28 Jul 2006 01:00:59 +0100 Message-ID: <44C953BA.4070008@dial.pipex.com> Date: Fri, 28 Jul 2006 01:00:58 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20060515 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> <20060727134948.GA3755@energistic.com> <20060727180412.GB48057@megan.kiwi-computer.com> <17609.1474.618423.970137@bhuda.mired.org> <44C910BE.9000108@dial.pipex.com> <20060727185721.GC25626@manor.msen.com> <17609.9516.506115.204334@bhuda.mired.org> <44C93454.5020404@dial.pipex.com> <17609.16421.670624.80289@bhuda.mired.org> In-Reply-To: <17609.16421.670624.80289@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 00:01:03 -0000 Mike Meyer wrote: >>>>A further reason to separate partitions is that dump works at the level >>>>of a partition. Different partitions may have very different backup >>>>requirements, and for those of us without huge tape drives, partitioning >>>>to a size that can be dumped on one tape makes life easier. >>>> >>>> >>>That's one of the technical reasons I mentioned in the part you >>>didn't quote. >>> >>> >>To my mind, it only takes *one* technical reason. If I need multiple >>partitions to make backups easy, then arguments about log files are >>irrelevant :-) >> >> > >If you're going to count 1, 2, many, then we already have "many" >partitions, and don't need more. Once you get into finer distinctions >of "many", you need to figure out which reasons are actually valid, >and which are spurious, so you can pick from among those manys. > > I have no real idea what this means, sorry. It seems to me that whoever made the initial decision to stop at 8 (size of an integer?) clearly thought counting past 2 was worthwhile. Maybe the original reasons no longer apply since quite a lot has changed since then :-) >>>Well, there are always special cases. But hardware is so cheap these >>>days, I'm used to fine-tuning the *system*, not just the partition. >>>If something is so critical that it needs it's own partition, it's >>>probably so critical that it needs it's own system as well. In fact, >>>most of the thing I work on these days are so critical that they need >>>several systems, half of them at a second site with automatic failover >>>between them. >>> >>> >>Not everyone is in a position to throw money at everything and what's >>cheap to you isn't cheap to everyone. >> >> > >Boxes are cheaper than disk space - my last two low-end boxes cost >less than my last small disk drive, even though I ordered them all >about the same time. If you can afford the disk for some process, then >chances are good you can afford a system instead, or as well. > > I don't understand this either. Surely the box has to include the disk space so how can it cost less? If it costs less because it's a cheap piece of junk, why would I even want it? And the "cost" of the system doesn't stop at the up front price - running costs including maintaining the box surely count (not to mention that I have nowhere to put the damn thing). And I'm not sure where needing a separate partition and criticality became the same thing. I don't claim to want or need separate partitions because any particular subset of the filesystem is critical, but because I want it to be separate for at least the two reasons outlined below. >>I can't possibly justify one system for everything that needs a >>partition, nor do I even feel the need to do that. If anything, it >>would be a major inconvenience. >> >> > >My claim is that your "everything that needs a partition" probably >includes things that don't. But to prove that, we need to examine the >reasons you think those things need a partition. I believe the only >one you've given so far - as a space firewall - is specious. > > Except that we also have the "dump", and the "different params for different parts of the filesystem" arguments. I think you agreed that you counted those as technical reasons. >Your arguments remind me of the environments I worked on in the 70s >and 80s. Minis and mainframes that did all the computing for an >organization. All the daemons that talked to the outside world ran on >the same box as the developers ran compiles and tests on, etc. While >that worked really well when it came to generating a robust OS, I >haven't seen an environment like that in decades. Hell, most of my >clients would shit bricks at the thought of putting their source or >data on a machine that could be reached from the internet at large at >all. Every developler has a box - or three - on their desks. The ETL >boxes are distinct from the database boxes are distinct from the >internal mail server is distinct from the external mail server, >etc. If I want to have a process send email notices about something, I >usually have to beat on them if I want a mail server on the box. And >so on.... > > Fine. You have access to lots of money and infrastructure. I don't. Throwing money at a problem is not a solution available to everyone. >>>Frankly, if you're really worried about >>>bootable slices, you should be advocating giving FreeBSD the ability >>>to boot from a logical volume. >>> >>> >>Who said I didn't? I have no objection to such a facility and would >>welcome it. It just imagined that extending the number of partitions >>from 8 to 16 would have been easier than booting from logical slices. >>If booting from logical slices is easier then I'm all for it. >> >> > >You're not asking the right question just yet. The question shouldn't >be "which is easier to add", but "which provides the most benefit for >the least pain" (which subsumes the pain involved in adding it). I >believe that the benefits of adding more partitions per slice are >minimal - there are at least three ways to add more file systems that >aren't bootable, and there's a better fix to the problem of wanting >more bootable partitions - and the pain involved in upgrading a system >across a change in the bsdlabel would be rather high. > > This all sounds fine to me, though the OP who wanted to mount a DragonFly partition might disagree :-( The bottom line for me is this: if the number of partitions per slice were to increase from 8 to 16, that would make my life easier as I do things now. The way I do things now works very well for me. and nothing you have said tells me how I could do things differently and still have it work as well. If no-one is going to increase partitions from 8 to 16, I'll survive. If someone instead makes logical partitions bootable, I'd be happy too. If someone comes up with something completely different that makes it easier for me to boot multiple FreeBSD's on a single machine without a) adding extra disk or b) buying expensive software, I'd be thrilled to bits. >there are at least three ways to add more file systems that >aren't bootable, > Logical partitions. What would be your other two? (Off list, if you prefer and can be bothered to answer, since it has got rather OT). --Alex From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 00:11:13 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2C5E16A4DD for ; Fri, 28 Jul 2006 00:11:13 +0000 (UTC) (envelope-from george@m5p.com) Received: from mailhost.m5p.com (209-162-215-52.dq1sn.easystreet.com [209.162.215.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 525A143D4C for ; Fri, 28 Jul 2006 00:11:12 +0000 (GMT) (envelope-from george@m5p.com) Received: from m5p.com (ssh.m5p.com [IPv6:2001:418:3fd::fb]) by mailhost.m5p.com (8.13.7/8.13.7) with ESMTP id k6S0BBkC036542 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=OK) for ; Thu, 27 Jul 2006 17:11:11 -0700 (PDT) Received: (from george@localhost) by m5p.com (8.13.7/8.13.7/Submit) id k6S0BBwP030395; Thu, 27 Jul 2006 17:11:11 -0700 (PDT) Date: Thu, 27 Jul 2006 17:11:11 -0700 (PDT) Message-Id: <200607280011.k6S0BBwP030395@m5p.com> From: george+freebsd@m5p.com To: freebsd-hackers@freebsd.org X-Spam-Score: -2.197 () AWL,BAYES_00,NO_RELAYS X-Scanned-By: MIMEDefang 2.56 on IPv6:2001:418:3fd::f7 Subject: Any success with bacula and DVD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 00:11:13 -0000 Is anybody successfully using bacula with DVD? When I install the bacula-server port, it cannot pass even the trivial "btape FileStorage/temp" test, let alone trying to write to DVD. Advice cheerfully accepted! -- George Mitchell From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 01:06:59 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB62716A4DD; Fri, 28 Jul 2006 01:06:59 +0000 (UTC) (envelope-from tijl@ulyssis.org) Received: from outmx013.isp.belgacom.be (outmx013.isp.belgacom.be [195.238.5.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 286A943D4C; Fri, 28 Jul 2006 01:06:59 +0000 (GMT) (envelope-from tijl@ulyssis.org) Received: from outmx013.isp.belgacom.be (localhost [127.0.0.1]) by outmx013.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6S16ug8013028; Fri, 28 Jul 2006 03:06:56 +0200 (envelope-from ) Received: from kalimero.kotnet.org (84.41-245-81.adsl-dyn.isp.belgacom.be [81.245.41.84]) by outmx013.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6S16lPq012969; Fri, 28 Jul 2006 03:06:47 +0200 (envelope-from ) Received: from kalimero.kotnet.org (kalimero.kotnet.org [127.0.0.1]) by kalimero.kotnet.org (8.13.6/8.13.6) with ESMTP id k6S16kkM010006; Fri, 28 Jul 2006 03:06:47 +0200 (CEST) (envelope-from tijl@ulyssis.org) From: Tijl Coosemans To: freebsd-emulation@freebsd.org Date: Fri, 28 Jul 2006 03:06:37 +0200 User-Agent: KMail/1.9.3 References: <200607221914.15826.lofi@freebsd.org> <200607272308.27425.tijl@ulyssis.org> <44C935D9.8040604@elischer.org> In-Reply-To: <44C935D9.8040604@elischer.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3629864.ZBnRPTWIvW"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607280306.46465.tijl@ulyssis.org> Cc: freebsd-hackers@freebsd.org, Julian Elischer , Michael Nottebrock Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 01:07:00 -0000 --nextPart3629864.ZBnRPTWIvW Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 27 July 2006 23:53, Julian Elischer wrote: > Tijl Coosemans wrote: > > On Thursday 27 July 2006 17:21, John Baldwin wrote: > > > The kernel should preserve %fs across syscalls, traps, and faults. > > > Can you point to a specific case where %fs is not preserved? It > > > sounds like %fs is never set to a value in Wine. > > > > Yes, it was a combination of compiler optimizations and an inline > > assembly block missing __volatile__. > > does this mean that wine will work from now on? > i.e. is the fix being fed back into wine sources? Not yet. Windows9x mode should work again as well as threading and TLS,=20 but there are still some open issues, mainly with exception handling=20 and file access. Exception handling was completely broken and is now=20 mostly working, but sometimes gets stuck in a loop generating=20 exceptions and eventually overflowing the stack. I'll submit patches once Wine passes the most important unit tests,=20 unless someone already wants to have a look at them of course... --nextPart3629864.ZBnRPTWIvW Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQBEyWMmdMR2xnarec8RAstSAKClCUO26Y5RNdF5RHf2KCdiUhTMEQCgqrWy wsUBBZw08BZ1m99CKsZ8y+4= =wMov -----END PGP SIGNATURE----- --nextPart3629864.ZBnRPTWIvW-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 01:13:45 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CB9216A4DA for ; Fri, 28 Jul 2006 01:13:45 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (megan.kiwi-computer.com [63.224.10.3]) by mx1.FreeBSD.org (Postfix) with SMTP id 9F96D43D4C for ; Fri, 28 Jul 2006 01:13:44 +0000 (GMT) (envelope-from rick@kiwi-computer.com) Received: (qmail 51406 invoked by uid 2001); 28 Jul 2006 01:13:43 -0000 Date: Thu, 27 Jul 2006 20:13:43 -0500 From: "Rick C. Petty" To: freebsd-hackers@freebsd.org Message-ID: <20060728011343.GB51284@megan.kiwi-computer.com> References: <20060727122159.GB4217@britannica.bec.de> <20060727134948.GA3755@energistic.com> <20060727180412.GB48057@megan.kiwi-computer.com> <17609.1474.618423.970137@bhuda.mired.org> <44C910BE.9000108@dial.pipex.com> <20060727185721.GC25626@manor.msen.com> <17609.9516.506115.204334@bhuda.mired.org> <44C93454.5020404@dial.pipex.com> <17609.16421.670624.80289@bhuda.mired.org> <44C953BA.4070008@dial.pipex.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44C953BA.4070008@dial.pipex.com> User-Agent: Mutt/1.4.2.1i Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 01:13:45 -0000 Mike Meyer wrote: >Boxes are cheaper than disk space - my last two low-end boxes cost >less than my last small disk drive, even though I ordered them all >about the same time. If you can afford the disk for some process, then >chances are good you can afford a system instead, or as well. I'm not sure how that's even possible. A quick glance at newegg.com: $17.99 (+$6.13) [recertified] socket A motherboard $39.99 [oem] AMD Duron socket A processor $13.99 (+$4.99) 128MB RAM =============== $71.97 (+$11.12 shipping) = $83.09. This is assuming you have an extra case, power supply, and video card to throw in it. What do you consider a "small disk drive"? Newegg has a 40G for $39.99 + $5.64 shipping. Yeah, so small disk drives seem to be half the price of the cheapest possible "box". Feel free to enlighten me, I'd love to know where you shop that has a system under US$50 !!!!! -- Rick C. Petty From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 01:33:43 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54C3016A4DD for ; Fri, 28 Jul 2006 01:33:43 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id AF71143D46 for ; Fri, 28 Jul 2006 01:33:42 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 57366 invoked by uid 1001); 28 Jul 2006 01:33:41 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Thu, 27 Jul 2006 21:33:41 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17609.26997.176143.224198@bhuda.mired.org> Date: Thu, 27 Jul 2006 21:33:41 -0400 To: rick-freebsd@kiwi-computer.com In-Reply-To: <20060728011343.GB51284@megan.kiwi-computer.com> References: <20060727122159.GB4217@britannica.bec.de> <20060727134948.GA3755@energistic.com> <20060727180412.GB48057@megan.kiwi-computer.com> <17609.1474.618423.970137@bhuda.mired.org> <44C910BE.9000108@dial.pipex.com> <20060727185721.GC25626@manor.msen.com> <17609.9516.506115.204334@bhuda.mired.org> <44C93454.5020404@dial.pipex.com> <17609.16421.670624.80289@bhuda.mired.org> <44C953BA.4070008@dial.pipex.com> <20060728011343.GB51284@megan.kiwi-computer.com> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 01:33:43 -0000 In <20060728011343.GB51284@megan.kiwi-computer.com>, Rick C. Petty typed: > Mike Meyer wrote: > >Boxes are cheaper than disk space - my last two low-end boxes cost > >less than my last small disk drive, even though I ordered them all > >about the same time. If you can afford the disk for some process, then > >chances are good you can afford a system instead, or as well. > > I'm not sure how that's even possible. A quick glance at newegg.com: > > $17.99 (+$6.13) [recertified] socket A motherboard > $39.99 [oem] AMD Duron socket A processor > $13.99 (+$4.99) 128MB RAM > =============== > $71.97 (+$11.12 shipping) = $83.09. > > This is assuming you have an extra case, power supply, and video card to > throw in it. What do you consider a "small disk drive"? Newegg has a 40G > for $39.99 + $5.64 shipping. Yeah, so small disk drives seem to be half > the price of the cheapest possible "box". Feel free to enlighten me, I'd > love to know where you shop that has a system under US$50 !!!!! "Small disk drive" means "smaller than any drive I can buy at the local Best Buy/Circuit City/CompUSA/similar". At the time, I needed an 80GB drive, and paid about $60 for it. Try http://www.pcretro.com/. Their current special is the Dell PowerEdge 6350 (dual CPU, 255MB ram, 2 9GB hot swap drives on separate controllers) for $49.95. The boxes I bought had a mouse and keyboard included, no monitor or speakers. Not that I cared - I tossed the mouse and keyboard on the spare parts pile and plugged them into a KVM. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 01:41:33 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6537316A4DA for ; Fri, 28 Jul 2006 01:41:33 +0000 (UTC) (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 0011B43D46 for ; Fri, 28 Jul 2006 01:41:32 +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.4/8.13.4) with ESMTP id k6S1cQIm045641; Thu, 27 Jul 2006 19:38:26 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 27 Jul 2006 19:38:44 -0600 (MDT) Message-Id: <20060727.193844.-432837881.imp@bsdimp.com> To: scheidell@secnap.net From: "M. Warner Losh" In-Reply-To: <44C670BA.6060608@secnap.net> References: <44C63DD2.9080705@freebsd.org> <44C6509E.4090708@secnap.net> <44C670BA.6060608@secnap.net> X-Mailer: Mew version 4.2 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]); Thu, 27 Jul 2006 19:38:26 -0600 (MDT) Cc: freebsd-hackers@freebsd.org Subject: Re: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 01:41:33 -0000 In message: <44C670BA.6060608@secnap.net> Michael Scheidell writes: : Found it! library libc_r : : Given POC: : : int main( int argc, char **argv ) : { : char execs1[256] = "/bin/date +A%Y%m%d%H%M.%S"; : char execs2[256] = "/bin/date +B%Y%m%d%H%M.%S"; : int a; : : while ( 1) { : : system( execs1 ); : usleep( 500*1000); : system( execs2 ); : } : : return 0; : } /* main */ : : compile with: : cc -g -c nanotest.c : cc -g -o nanotest nanotest.o : : everything works as expected. : : time forward, back, doesn't matter (date prints out wallclock, : nanosleep() sleeps 500*1000*1000us (.5 seconds) : : this breaks it: : cc -g -c nanotest.c : cc -g -o nanotest nanotest.o -lc_r : : setting clock back 'hangs' during usleep (500*1000) : didn't hang on 5.4. : I will be writing up a bug report shortly. libc_r depends on absolute system time to do its sleeps and timeouts, and has since FreeBSD 3.4. This dependency has been the result of many conversations over time, and has had several patches posted. Since libc_r is dead technology, there's little chance they will be adopted. Warner From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 03:51:58 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1ECB16A4DA; Fri, 28 Jul 2006 03:51:58 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: from rwcrmhc14.comcast.net (rwcrmhc14.comcast.net [204.127.192.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D75143D49; Fri, 28 Jul 2006 03:51:57 +0000 (GMT) (envelope-from e.schuele@computer.org) Received: from [192.168.214.215] (c-24-1-232-64.hsd1.tx.comcast.net[24.1.232.64]) by comcast.net (rwcrmhc14) with ESMTP id <20060728035156m1400889t2e>; Fri, 28 Jul 2006 03:51:57 +0000 Message-ID: <44C989DC.6070307@computer.org> Date: Thu, 27 Jul 2006 22:51:56 -0500 From: Eric Schuele User-Agent: Thunderbird 1.5.0.4 (X11/20060604) MIME-Version: 1.0 To: Robert Watson References: <18075337.124391153395068232.JavaMail.root@vms068.mailsrvcs.net> <20060721031308.GK27268@wantadilla.lemis.com> <20060721143024.W79560@fledge.watson.org> In-Reply-To: <20060721143024.W79560@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Greg 'groggy' Lehey , babkin@users.sourceforge.net, FreeBSD Hackers Subject: Re: Programs not accepting input? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 03:51:58 -0000 On 07/21/2006 08:32, Robert Watson wrote: > > On Fri, 21 Jul 2006, Greg 'groggy' Lehey wrote: > >>>> I've been keeping a closer eye on my problem. I'm using fvwm1 with >>>> click-to-focus and lose-focus-on-screen-switch. If I move from one >>>> screen to another and quickly click on a window, the border changes >>>> colour to indicate that it has focus but keyboard input is ignored. >>> >>> This is likely an fvwm1 problem. I use it too (without 2 monitors) >>> and after some time something gets broken in its focus handling, and >>> the windows stop getting focus. Restarting fvwm clears up the problem. >> >> In my case, it's erratic. I suppose I could try restarting the window >> manager next time a window freezes. > > I've occasionally also had weird focus problems with KDE. Among other > things, it looks like occasionally the mouse release event is lost > somewhere in the system (or something along these lines) -- I don't know > if it's a driver problem, a moused problem, an X11 probem, or a KDE > problem. If I press and release each of the buttons, especially the > third button, things will often recover. As long as the button is "held > down", KDE doesn't switch the focus and other events are largely > ignored. Odd, eh? > > Robert N M Watson > Computer Laboratory > University of Cambridge > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > I think I'm seeing something similar (not sure).... so I thought I'd mention it. I can repeat the effect on demand. If I open my opera browser it launches a weather widget. If I then open a terminal (aterm in this case) and give it focus, everything is good. If I bring my mouse over the widget, it appears to capture the keybaord input. My terminal cursor goes to an empty square. (My window manager is not setup to have the focus follow the mouse. I focus on clicks.) My terminal window is still highlighted as if it actually has focus. If I then click on the terminal window, or within the window in an attempt to give it focus... I still can not type in it (the cursor is still hollow). Keypresses affect the widget only at this point. The only way is to either pick a third window, or actually click in the widget, and then back to the terminal. In fact I've done the same thing with the composing of this e-mail. The focus can be stolen from this "compose" window in a similar fashion. I've only just started using this widget today, so this is the first time I've come across this effect. If you think this is a similar problem... and there is anything I could do to help examine it, let me know. -- Regards, Eric From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 05:43:00 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81CB216A4E2; Fri, 28 Jul 2006 05:43:00 +0000 (UTC) (envelope-from ssedov@mbsd.msk.ru) Received: from com1.ht-systems.ru (com1.ht-systems.ru [83.97.104.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFCF543D53; Fri, 28 Jul 2006 05:42:59 +0000 (GMT) (envelope-from ssedov@mbsd.msk.ru) Received: from [217.118.83.1] (helo=fonon.realnet) by com1.ht-systems.ru with esmtpa (Exim 4.62) (envelope-from ) id 1G6LFQ-0006np-IB; Fri, 28 Jul 2006 09:50:59 +0400 Received: from localhost (localhost [127.0.0.1]) by fonon.realnet (Postfix) with ESMTP id BAA101208B; Fri, 28 Jul 2006 09:42:36 +0400 (MSD) Date: Fri, 28 Jul 2006 09:42:36 +0400 From: Stanislav Sedov To: freebsd-hackers@freebsd.org,freebsd-ports@freebsd.org Message-ID: <20060728094236.382b208b@localhost> In-Reply-To: <200607280011.k6S0BBwP030395@m5p.com> References: <200607280011.k6S0BBwP030395@m5p.com> Organization: MBSD labs, Inc. X-Operating-System: FreeBSD X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_yQTaaQDlczLhtul0UA7A5D+; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona 1.5.2 Cc: Subject: Re: Any success with bacula and DVD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 05:43:00 -0000 --Sig_yQTaaQDlczLhtul0UA7A5D+ Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable On Thu, 27 Jul 2006 17:11:11 -0700 (PDT) george+freebsd@m5p.com mentioned: > Is anybody successfully using bacula with DVD? When I install the > bacula-server port, it cannot pass even the trivial > "btape FileStorage/temp" test, let alone trying to write to DVD. > Advice cheerfully accepted! -- George Mitchell >=20 I don't use bacula actually, but, IMO, this problem is linked with burncd's inability to work with DVDs. Try to install dvd+rw tools and point bacula to use them. Also try to contact with bacula port maintainer. PS: freebsd-ports@freebsd.org is better suited for this question. =20 --=20 Stanislav Sedov MBSD labs, Inc. =F2=CF=D3=D3=C9=D1, =ED=CF=D3=CB=D7=C1 http://mbsd.msk.ru -------------------------------------------------------------------- If the facts don't fit the theory, change the facts. -- A. Einstein -------------------------------------------------------------------- PGP fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 --Sig_yQTaaQDlczLhtul0UA7A5D+ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEyaPMK/VZk+smlYERAnYvAJ9M2zLXL5ThOHjvy32pS+cwV/gg3wCdHVgL CuML5T/pIMU/6pXf5jrbOD4= =cyXZ -----END PGP SIGNATURE----- --Sig_yQTaaQDlczLhtul0UA7A5D+-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 06:34:15 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7E2216A4DA; Fri, 28 Jul 2006 06:34:15 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6183443D4C; Fri, 28 Jul 2006 06:34:14 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 4ABA753; Fri, 28 Jul 2006 01:34:14 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 8E42661C52; Fri, 28 Jul 2006 01:34:13 -0500 (CDT) Date: Fri, 28 Jul 2006 01:34:13 -0500 From: "Matthew D. Fuller" To: John Baldwin Message-ID: <20060728063413.GI69505@over-yonder.net> References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727202105.GA14724@titan.klemm.apsfilter.org> <17609.10507.322936.614793@bhuda.mired.org> <200607271734.24026.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200607271734.24026.jhb@freebsd.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.3 Cc: freebsd-hackers@freebsd.org, Mike Meyer Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 06:34:15 -0000 On Thu, Jul 27, 2006 at 05:34:23PM -0400 I heard the voice of John Baldwin, and lo! it spake thus: > On Thursday 27 July 2006 16:58, Mike Meyer wrote: > > Right. I typically install / and /usr as distinct files systems > > for just that reason (/ and /usr have different backup & recovery > > strategies and I use dump, so that's why they are two partitions). > > So why does / need to be different from /var, /usr different from > > /usr/X11R6 and /home different from /usr/local? Seriously now - > > what I just described is my typical install. > > In my case I still have /home in /usr/home, but I should start > making it separate in the hope that I could mount /usr read-only > most of the time reducing the time it takes to fsck when I crash my > test machines. I have / and /usr [sometimes one partition] mounted read-only on many of my systems. I like the peace of mind of KNOWING nothing'll go wonky on 'em on a crash, I like the shorter fsck times, I kinda like knowing there's that extra (very thin, but still extant) layer of protection against a lot of automated attacks... And, darnit, it just feels cleaner. I tend to have separate /var, /tmp, /home, and /usr/local which are kept rw since they have live and constantly-fiddled data on them, but everything else generally ends up ro since I only need to write them at specific discrete times. Out of the 11 partitions (multiple disks) on my workstation, only those 4 are generally rw. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 11:37:06 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C42816A4DA for ; Fri, 28 Jul 2006 11:37:06 +0000 (UTC) (envelope-from mux@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEDAF43D4C for ; Fri, 28 Jul 2006 11:37:05 +0000 (GMT) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id B477E1A4E7A; Fri, 28 Jul 2006 04:37:05 -0700 (PDT) Date: Fri, 28 Jul 2006 13:37:05 +0200 From: Maxime Henrion To: Maksim Yevmenkin Message-ID: <20060728113705.GZ8070@elvis.mu.org> References: <1153997829.12770@origin.intron.ac> <864px31eyz.fsf@xps.des.no> <86psfryvvo.fsf@xps.des.no> <44C8CFA2.3000400@savvis.net> <868xme28nt.fsf@xps.des.no> <44C90D22.5010607@savvis.net> <86slkmzx4o.fsf@xps.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86slkmzx4o.fsf@xps.des.no> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: How to Use ddb(4)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 11:37:06 -0000 Dag-Erling Sm?rgrav wrote: > Maksim Yevmenkin writes: > > so far i only got one (successful) report. would people please give > > it a try to see if work, so i can commit it. > > Please commit it. I don't see how it can do any harm. Yes please; I'd like to see this patch in HEAD as soon as possible so that we can have as much coverage as possible since this is the kind of fix that will be very desirable to MFC for 6.2-RELEASE. BTW, does your patch also fix similar problems with kbdmux(4) and the geli mountroot prompt? Cheers, Maxime From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 12:45:54 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF58016A4DF; Fri, 28 Jul 2006 12:45:54 +0000 (UTC) (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 1A41D43D78; Fri, 28 Jul 2006 12:45:51 +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 EEBBA46C6B; Fri, 28 Jul 2006 08:45:50 -0400 (EDT) Date: Fri, 28 Jul 2006 13:45:50 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Alexander Leidinger In-Reply-To: <20060728142237.lhocfctqugoocc48@netchild.homeip.net> Message-ID: <20060728133744.D56782@fledge.watson.org> References: <200607280705.k6S7585g094248@repoman.freebsd.org> <20060728092503.U4612@fledge.watson.org> <20060728142237.lhocfctqugoocc48@netchild.homeip.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: hackers@freebsd.org, Joel Dahl Subject: Re: cvs commit: www/en/projects/ideas index.sgml X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 12:45:54 -0000 On Fri, 28 Jul 2006, Alexander Leidinger wrote: >> BTW, a problem that has occurred a number of times in the past is that >> people have approached us with implementations of ideas in the idea list >> that it has later transpired we aren't actually interested in (sometimes at >> all). I think it might not be a bad idea to sprinkle the > > My impression is, that we lack some committers which not only have time to > review the submissions, but also have the necessary domain specific > knowledge at the same time. I suggest marking unreviewed ideas as unreviewed then. My biggest concern is that we have people who come along, see the idea, implement it, and it's then dropped on the floor because it turns out we didn't really want it, but it was on the list. If we don't want it, we shouldn't list it. If we're not sure if we want it, but think it might be neat, then we should say that's why it's on the list, so as to avoid misunderstandings. >> idea list with some additional cautionary language -- often ideas listed >> there are things to explore, not to adopt without very careful >> consideration. For example, the "FPU subsystem overhaul", "Process > > Uhm... the FPU one... ok. AFAIK bde reviewed it. I haven't seen the review > (or I don't remember it), but so far it looks like it would be beneficial to > commit it (AFAIR). I'm not able to review the code (I lack the necessary > domain specific knowledge), but I wanted to give it a try on my system and > then send a mail to arch to get some technical reasons why to not commit > commit it. > > Similar for the new TCP checksumming code. Initially there was a problem, it > got fixed, and now nobody takes care of it since everyone seems to think > "it's flawed". At least this is the impression I got. I have no specific technical opinion on either of these items. >> Some of the ideas on this list are distinctly "explore this direction as a >> computer scientist, not a code hacker" sorts of problems -- for example, >> the "Process checkpointing" task seems to suggest that if you can read the >> DFBSD repository and write some C code, you're set. In fact, this is not >> remotely the case. Checkpointing is a very difficult problem in computer >> science, with little consensus on how it should be done (and indeed whether >> it should be done at all) by general purpose operating systems. Not only >> that, but we would not adopt the DFBSD implementation as-is, as it solves a >> few of the easy problems, and none of the hard ones (i.e., security). The >> requirements here aren't just the ability to write code, but an >> understanding of distributed systems, our application/execution model, a >> strong understanding of the performance and security requirements, and >> willingness to not just look at code but the extensive research literature >> on this topic. > > AFAIR the process checkpointing in DFly has to be enabled (or am I mixing > this up with the magic symlinks?) in the kernel. And the man page contains > some text what is possible and what not, and about security implications. > Yes, they don't use a model which is able to solve all cases, but for some > cases where the programs (those which don't make heavy use of I/O and thus > can open/close I/O channels when they are needed) are written to make use of > this feature, you can make some users happy and the developers can > concentrate at the problem at hand. So it's one of those 80/20 solutions. > While I agree that a 100% solution would be nice, I think an implementation > of this in -current would be nice to have. It's a neat/fun hack, but I would object strongly to the current implementation going into the tree. I think 80/20 is a mischaracterization. > We need some reviewers here... while I'm able to come up with a nice > technical description of roughly expressed ideas (as long as I get the > idea), I'm not a TRB and as such aren't aware of every implication. And some > ideas are expressed in a way which make them sound like it's "common > knowledge to people which work in this field" (ATM I refer to the NFS lockd > in kernel implementation idea). Given that we can't get the user space code to work and don't have an owner for it (it appears to be abandonware), I think moving it into the kernel would be a disaster. We've been discussing ripping out the current user space code entirely on the basis that it is responsible for a huge number of bug reports and lots of problems. > So: helping hands are welcome! > > Thanks for taking some time to review some parts of the list. I'll try to take a look through the rest of them later today. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 11:30:17 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE92416A4E2 for ; Fri, 28 Jul 2006 11:30:17 +0000 (UTC) (envelope-from scheidell@secnap.net) Received: from secnap2.secnap.com (secnap2.secnap.com [204.89.241.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CE4243D49 for ; Fri, 28 Jul 2006 11:30:17 +0000 (GMT) (envelope-from scheidell@secnap.net) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Fri, 28 Jul 2006 07:30:16 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FBSD 5.5 and software timers Thread-Index: Acax5vgIWo3YcWOhSEWmmKyhnjQ2twAUejYg From: "Michael Scheidell" To: "M. Warner Losh" X-Mailman-Approved-At: Fri, 28 Jul 2006 14:34:37 +0000 Cc: freebsd-hackers@freebsd.org Subject: RE: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 11:30:17 -0000 > -----Original Message----- > From: M. Warner Losh [mailto:imp@bsdimp.com]=20 > Sent: Thursday, July 27, 2006 9:39 PM > To: Michael Scheidell > Cc: freebsd-hackers@freebsd.org > Subject: Re: FBSD 5.5 and software timers > libc_r depends on absolute system time to do its sleeps and=20 > timeouts, and has since FreeBSD 3.4. This dependency has=20 Could be, but it worked up to and including 5.4. > been the result of many conversations over time, and has had=20 > several patches posted. Since libc_r is dead technology,=20 > there's little chance they will be adopted. I replaced libc_r with libthr and two things happen: One of my threads doesn't run, and it won't die (kill -9 doesn't even kill it) I replaced libc_r with libpthread and it immediately reboots the system! I am going to try to nail down just what and why this happens and post that. (reminder: even if this change happened in 3.4, it didn't affect me till 5.5) From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 12:22:36 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11E2916A4E0; Fri, 28 Jul 2006 12:22:36 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 516E343D45; Fri, 28 Jul 2006 12:22:35 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5FAD4.dip.t-dialin.net [84.165.250.212]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.6/8.13.6) with ESMTP id k6SC9wr0018961; Fri, 28 Jul 2006 14:09:58 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.4/8.13.3) with ESMTP id k6SCMbaH078604; Fri, 28 Jul 2006 14:22:37 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Fri, 28 Jul 2006 14:22:37 +0200 Message-ID: <20060728142237.lhocfctqugoocc48@netchild.homeip.net> X-Priority: 3 (Normal) Date: Fri, 28 Jul 2006 14:22:37 +0200 From: Alexander Leidinger To: Robert Watson References: <200607280705.k6S7585g094248@repoman.freebsd.org> <20060728092503.U4612@fledge.watson.org> In-Reply-To: <20060728092503.U4612@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new X-Mailman-Approved-At: Fri, 28 Jul 2006 14:34:58 +0000 Cc: hackers@freebsd.org, Joel Dahl Subject: Re: cvs commit: www/en/projects/ideas index.sgml X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 12:22:36 -0000 Quoting Robert Watson (from Fri, 28 Jul 2006 =20 09:52:33 +0100 (BST)): [moving to hackers@... feel free to redirect if you think there's a =20 more appropriate list] > > On Fri, 28 Jul 2006, Joel Dahl wrote: > >> Modified files: >> en/projects/ideas index.sgml >> Log: >> - Extend the ktrace project with a new task. [1] [adding some warnings to this project] Thanks for reviewing and the heads up regarding problems which may =20 arise. Yes, we should add them to the entry. > BTW, a problem that has occurred a number of times in the past is that > people have approached us with implementations of ideas in the idea > list that it has later transpired we aren't actually interested in > (sometimes at all). I think it might not be a bad idea to sprinkle the My impression is, that we lack some committers which not only have =20 time to review the submissions, but also have the necessary domain =20 specific knowledge at the same time. > idea list with some additional cautionary language -- often ideas > listed there are things to explore, not to adopt without very careful > consideration. For example, the "FPU subsystem overhaul", "Process Uhm... the FPU one... ok. AFAIK bde reviewed it. I haven't seen the =20 review (or I don't remember it), but so far it looks like it would be =20 beneficial to commit it (AFAIR). I'm not able to review the code (I =20 lack the necessary domain specific knowledge), but I wanted to give it =20 a try on my system and then send a mail to arch to get some technical =20 reasons why to not commit commit it. Similar for the new TCP checksumming code. Initially there was a =20 problem, it got fixed, and now nobody takes care of it since everyone =20 seems to think "it's flawed". At least this is the impression I got. > checkpointing", "Pluggable disk shceduler", "Magic Symlinks", "NFS > Lockd (kernel implementation)", and several others -- the task here > often isn't to port/write the code, the task is to port/write and then > perform a detailed and careful evaluation of the changes to decide > whether they are a good idea, and then consider adopting the code only > if the evaluation suggests it is a good idea and after significant > refinment. So far we got not much responses from committers/developers. There's a =20 lot of interest in working on some of the entries, but so far we don't =20 get much review for the entries/ideas themself. Any refinement is =20 welcome and appreciated. So if someone has some thoughts about =20 specific entries: please, share them with us. > Some of the ideas on this list are distinctly "explore this direction > as a computer scientist, not a code hacker" sorts of problems -- for > example, the "Process checkpointing" task seems to suggest that if you > can read the DFBSD repository and write some C code, you're set. In > fact, this is not remotely the case. Checkpointing is a very difficult > problem in computer science, with little consensus on how it should be > done (and indeed whether it should be done at all) by general purpose > operating systems. Not only that, but we would not adopt the DFBSD > implementation as-is, as it solves a few of the easy problems, and none > of the hard ones (i.e., security). The requirements here aren't just > the ability to write code, but an understanding of distributed systems, > our application/execution model, a strong understanding of the > performance and security requirements, and willingness to not just look > at code but the extensive research literature on this topic. AFAIR the process checkpointing in DFly has to be enabled (or am I =20 mixing this up with the magic symlinks?) in the kernel. And the man =20 page contains some text what is possible and what not, and about =20 security implications. Yes, they don't use a model which is able to =20 solve all cases, but for some cases where the programs (those which =20 don't make heavy use of I/O and thus can open/close I/O channels when =20 they are needed) are written to make use of this feature, you can make =20 some users happy and the developers can concentrate at the problem at =20 hand. So it's one of those 80/20 solutions. While I agree that a 100% =20 solution would be nice, I think an implementation of this in -current =20 would be nice to have. > I think people often grab ideas from the list thinking that if > implemented as described, they will get committed, and this is not the > case. In many of the sorts of "scientific" cases it's likely we'll > look at the results and say, "Oh, that was a bad idea", or maybe > slightly more likely, "Oh, hmm, not so sure about that". The existing Joel and I already talked briefly about an "we don't do that" or "been =20 there, done that, wasn't a good idea" page because of this. > cautionary language captures that there might be disagreements on the > specifics, but fails to capture that there may be disagreements on the > fundamental ideas themselves. I like the ideas list idea a lot, and Ok, we should change that. Thanks for providing a big picture view for =20 those of us which don't see the forest while sitting in front it... > don't want to see it removed, but I also don't want people getting the > false impression that this is a "todo" list. Some items are todo items > and obvious short-order commit candidates, others are out-there ideas > that have potential and should be characterized as "high risk" when it > comes to the results actually being used. Maybe what we should be > thinking about is classifying the todo list items into rote items > (things where the chances of adoption of a decent implementation are > high, subject to review) and researchy things (where the chances of > adoption are low, not just because the chances of a good implementation > are low, but because there are lots of open and very difficult > questions involved). This would help prevent misunderstandings, if > nothing else. We need some reviewers here... while I'm able to come up with a nice =20 technical description of roughly expressed ideas (as long as I get the =20 idea), I'm not a TRB and as such aren't aware of every implication. =20 And some ideas are expressed in a way which make them sound like it's =20 "common knowledge to people which work in this field" (ATM I refer to =20 the NFS lockd in kernel implementation idea). So: helping hands are welcome! Thanks for taking some time to review some parts of the list. Bye, Alexander. --=20 All great discoveries are made by mistake. =09=09-- Young http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 13:27:32 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99FCC16A4E2; Fri, 28 Jul 2006 13:27:32 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AE5F43D5C; Fri, 28 Jul 2006 13:27:26 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5FAD4.dip.t-dialin.net [84.165.250.212]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.6/8.13.6) with ESMTP id k6SDEn5J019186; Fri, 28 Jul 2006 15:14:50 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.4/8.13.3) with ESMTP id k6SDRTqR087917; Fri, 28 Jul 2006 15:27:29 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Fri, 28 Jul 2006 15:27:28 +0200 Message-ID: <20060728152728.3pwcc5glesc08c0k@netchild.homeip.net> X-Priority: 3 (Normal) Date: Fri, 28 Jul 2006 15:27:28 +0200 From: Alexander Leidinger To: Robert Watson References: <200607280705.k6S7585g094248@repoman.freebsd.org> <20060728092503.U4612@fledge.watson.org> <20060728142237.lhocfctqugoocc48@netchild.homeip.net> <20060728133744.D56782@fledge.watson.org> In-Reply-To: <20060728133744.D56782@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new X-Mailman-Approved-At: Fri, 28 Jul 2006 14:35:17 +0000 Cc: hackers@FreeBSD.org, Joel Dahl Subject: Re: cvs commit: www/en/projects/ideas index.sgml X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 13:27:32 -0000 Quoting Robert Watson (from Fri, 28 Jul 2006 =20 13:45:50 +0100 (BST)): > > On Fri, 28 Jul 2006, Alexander Leidinger wrote: > >>> BTW, a problem that has occurred a number of times in the past is =20 >>> that people have approached us with implementations of ideas in =20 >>> the idea list that it has later transpired we aren't actually =20 >>> interested in (sometimes at all). I think it might not be a bad =20 >>> idea to sprinkle the >> >> My impression is, that we lack some committers which not only have =20 >> time to review the submissions, but also have the necessary domain =20 >> specific knowledge at the same time. > > I suggest marking unreviewed ideas as unreviewed then. My biggest Which isn't entirely true. We filter incoming ideas (we at least =20 rejected one or two... after talking with the submitter), but we =20 aren't able to distinguish good looking but bad ideas from good =20 looking and good ideas. Some ideas are only rejectable by someone with =20 enough domain specific knowledge and look ok for most other people. So when do you think an entry is reviewed? How to determine whom to =20 ask for review and how to get this person interested enough for a =20 review? > concern is that we have people who come along, see the idea, implement > it, and it's then dropped on the floor because it turns out we didn't > really want it, but it was on the list. If we don't want it, we > shouldn't list it. If we're not sure if we want it, but think it might > be neat, then we should say that's why it's on the list, so as to avoid > misunderstandings. I agree. >> We need some reviewers here... while I'm able to come up with a =20 >> nice technical description of roughly expressed ideas (as long as I =20 >> get the idea), I'm not a TRB and as such aren't aware of every =20 >> implication. And some ideas are expressed in a way which make them =20 >> sound like it's "common knowledge to people which work in this =20 >> field" (ATM I refer to the NFS lockd in kernel implementation idea). > > Given that we can't get the user space code to work and don't have an > owner for it (it appears to be abandonware), I think moving it into the > kernel would be a disaster. Uhm... I'm withhin the implicit assumption that we first need to fix =20 NFS lockd (an entry before the "move into the kernel" entry)... ok, we =20 need to record dependencies here. >> So: helping hands are welcome! >> >> Thanks for taking some time to review some parts of the list. > > I'll try to take a look through the rest of them later today. Thanks, Alexander. --=20 Let me put it this way: today is going to be a learning experience. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 14:43:03 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73AD016A4F1; Fri, 28 Jul 2006 14:43:03 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3295D43D8C; Fri, 28 Jul 2006 14:42:58 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.236] (really [70.32.199.60]) by mta11.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060728144252.CUAF4642.mta11.adelphia.net@[192.168.1.236]>; Fri, 28 Jul 2006 10:42:52 -0400 Message-ID: <44CA226B.1030608@savvis.net> Date: Fri, 28 Jul 2006 07:42:51 -0700 From: maksim yevmenkin User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Maxime Henrion References: <1153997829.12770@origin.intron.ac> <864px31eyz.fsf@xps.des.no> <86psfryvvo.fsf@xps.des.no> <44C8CFA2.3000400@savvis.net> <868xme28nt.fsf@xps.des.no> <44C90D22.5010607@savvis.net> <86slkmzx4o.fsf@xps.des.no> <20060728113705.GZ8070@elvis.mu.org> In-Reply-To: <20060728113705.GZ8070@elvis.mu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: How to Use ddb(4)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 14:43:03 -0000 Maxime Henrion wrote: > Dag-Erling Sm?rgrav wrote: >> Maksim Yevmenkin writes: >>> so far i only got one (successful) report. would people please give >>> it a try to see if work, so i can commit it. >> Please commit it. I don't see how it can do any harm. > > Yes please; I'd like to see this patch in HEAD as soon as possible so > that we can have as much coverage as possible since this is the kind of > fix that will be very desirable to MFC for 6.2-RELEASE. patch was committed to head yesterday. > BTW, does your patch also fix similar problems with kbdmux(4) and the > geli mountroot prompt? yes, it should. please let me know if you still have this kind of problems with kbdmux(4) and atkbd(4) thanks, max From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 14:43:13 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C96E116A580 for ; Fri, 28 Jul 2006 14:43:13 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (megan.kiwi-computer.com [63.224.10.3]) by mx1.FreeBSD.org (Postfix) with SMTP id 43A6A43D64 for ; Fri, 28 Jul 2006 14:43:11 +0000 (GMT) (envelope-from rick@kiwi-computer.com) Received: (qmail 58381 invoked by uid 2001); 28 Jul 2006 14:43:10 -0000 Date: Fri, 28 Jul 2006 09:43:10 -0500 From: "Rick C. Petty" To: Mike Meyer Message-ID: <20060728144310.GA58252@megan.kiwi-computer.com> References: <20060727180412.GB48057@megan.kiwi-computer.com> <17609.1474.618423.970137@bhuda.mired.org> <44C910BE.9000108@dial.pipex.com> <20060727185721.GC25626@manor.msen.com> <17609.9516.506115.204334@bhuda.mired.org> <44C93454.5020404@dial.pipex.com> <17609.16421.670624.80289@bhuda.mired.org> <44C953BA.4070008@dial.pipex.com> <20060728011343.GB51284@megan.kiwi-computer.com> <17609.26997.176143.224198@bhuda.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17609.26997.176143.224198@bhuda.mired.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 14:43:13 -0000 On Thu, Jul 27, 2006 at 09:33:41PM -0400, Mike Meyer wrote: > > "Small disk drive" means "smaller than any drive I can buy at the > local Best Buy/Circuit City/CompUSA/similar". At the time, I needed an > 80GB drive, and paid about $60 for it. Well then your comparison isn't really fair.. Sure, a brand new hard drive from a retail outlet is more expensive than a 10-year-old box (especially if the box is refurbished). No surprise there! I thought we were comparing oranges and oranges. In that case, check out www.geeks.com (the old computergeeks), they have a number of drives for sale under $49.95. > Try http://www.pcretro.com/. Their current special is the Dell > PowerEdge 6350 (dual CPU, 255MB ram, 2 9GB hot swap drives on separate > controllers) for $49.95. The boxes I bought had a mouse and keyboard > included, no monitor or speakers. Not that I cared - I tossed the > mouse and keyboard on the spare parts pile and plugged them into a > KVM. -- Rick C. Petty From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 14:47:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BC3F16A4DE for ; Fri, 28 Jul 2006 14:47:53 +0000 (UTC) (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 1116643DA3 for ; Fri, 28 Jul 2006 14:47: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.4/8.13.4) with ESMTP id k6SEko1D057915; Fri, 28 Jul 2006 08:46:50 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 28 Jul 2006 08:47:09 -0600 (MDT) Message-Id: <20060728.084709.-135504445.imp@bsdimp.com> To: scheidell@secnap.net From: "M. Warner Losh" In-Reply-To: References: X-Mailer: Mew version 4.2 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]); Fri, 28 Jul 2006 08:46:50 -0600 (MDT) Cc: freebsd-hackers@freebsd.org Subject: Re: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 14:47:53 -0000 In message: "Michael Scheidell" writes: : > -----Original Message----- : > From: M. Warner Losh [mailto:imp@bsdimp.com] : > Sent: Thursday, July 27, 2006 9:39 PM : > To: Michael Scheidell : > Cc: freebsd-hackers@freebsd.org : > Subject: Re: FBSD 5.5 and software timers : : > libc_r depends on absolute system time to do its sleeps and : > timeouts, and has since FreeBSD 3.4. This dependency has : : Could be, but it worked up to and including 5.4. It worked for the one simple test case that you had. I'm not sure what changed between 5.4 and 5.5 to break it. I've hit similar test cases as far back as 3.4. : > been the result of many conversations over time, and has had : > several patches posted. Since libc_r is dead technology, : > there's little chance they will be adopted. : : I replaced libc_r with libthr and two things happen: : One of my threads doesn't run, and it won't die (kill -9 doesn't even : kill it) : : I replaced libc_r with libpthread and it immediately reboots the system! Neither of these is good! Does it happen on 6? : I am going to try to nail down just what and why this happens and post : that. : (reminder: even if this change happened in 3.4, it didn't affect me till : 5.5) It might be useful to find the change. Warner From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 14:52:01 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8808916A503; Fri, 28 Jul 2006 14:52:01 +0000 (UTC) (envelope-from mux@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1F2043D69; Fri, 28 Jul 2006 14:51:57 +0000 (GMT) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id 6DEEE1A4E7E; Fri, 28 Jul 2006 07:51:57 -0700 (PDT) Date: Fri, 28 Jul 2006 16:51:57 +0200 From: Maxime Henrion To: maksim yevmenkin Message-ID: <20060728145157.GA8070@elvis.mu.org> References: <1153997829.12770@origin.intron.ac> <864px31eyz.fsf@xps.des.no> <86psfryvvo.fsf@xps.des.no> <44C8CFA2.3000400@savvis.net> <868xme28nt.fsf@xps.des.no> <44C90D22.5010607@savvis.net> <86slkmzx4o.fsf@xps.des.no> <20060728113705.GZ8070@elvis.mu.org> <44CA226B.1030608@savvis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44CA226B.1030608@savvis.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, re@freebsd.org Subject: Re: How to Use ddb(4)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 14:52:01 -0000 maksim yevmenkin wrote: > Maxime Henrion wrote: > >Dag-Erling Sm?rgrav wrote: > >>Maksim Yevmenkin writes: > >>>so far i only got one (successful) report. would people please give > >>>it a try to see if work, so i can commit it. > >>Please commit it. I don't see how it can do any harm. > > > >Yes please; I'd like to see this patch in HEAD as soon as possible so > >that we can have as much coverage as possible since this is the kind of > >fix that will be very desirable to MFC for 6.2-RELEASE. > > patch was committed to head yesterday. Yeah, I just saw it, I was quite behind with my mail. Thanks! > >BTW, does your patch also fix similar problems with kbdmux(4) and the > >geli mountroot prompt? > > yes, it should. please let me know if you still have this kind of > problems with kbdmux(4) and atkbd(4) Great. I haven't had the time to look at the patch yet, but can you foresee any problem with MFC'ing it or would you consider it safe? Cheers, Maxime From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 15:03:21 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4045B16A4DA for ; Fri, 28 Jul 2006 15:03:21 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 98B3E43D6B for ; Fri, 28 Jul 2006 15:03:20 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 74367 invoked by uid 1001); 28 Jul 2006 15:03:19 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Fri, 28 Jul 2006 11:03:17 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17610.10037.669199.494402@bhuda.mired.org> Date: Fri, 28 Jul 2006 11:03:17 -0400 To: rick-freebsd@kiwi-computer.com In-Reply-To: <20060728144310.GA58252@megan.kiwi-computer.com> References: <20060727180412.GB48057@megan.kiwi-computer.com> <17609.1474.618423.970137@bhuda.mired.org> <44C910BE.9000108@dial.pipex.com> <20060727185721.GC25626@manor.msen.com> <17609.9516.506115.204334@bhuda.mired.org> <44C93454.5020404@dial.pipex.com> <17609.16421.670624.80289@bhuda.mired.org> <44C953BA.4070008@dial.pipex.com> <20060728011343.GB51284@megan.kiwi-computer.com> <17609.26997.176143.224198@bhuda.mired.org> <20060728144310.GA58252@megan.kiwi-computer.com> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 15:03:21 -0000 In <20060728144310.GA58252@megan.kiwi-computer.com>, Rick C. Petty typed: > On Thu, Jul 27, 2006 at 09:33:41PM -0400, Mike Meyer wrote: > > "Small disk drive" means "smaller than any drive I can buy at the > > local Best Buy/Circuit City/CompUSA/similar". At the time, I needed an > > 80GB drive, and paid about $60 for it. > Well then your comparison isn't really fair.. Sure, a brand new hard drive > from a retail outlet is more expensive than a 10-year-old box (especially > if the box is refurbished). Um, I didn't buy the drive from a retail outlet. It was defined as small *because* it's to old and small for the retail outlets to carry it. Yes, it's not as old as the systems I bought, but it's the price point I had. I bought it through a price comparison engine; I'd have to dig through my records to find out who the actual seller was. > No surprise there! I thought we were comparing oranges and oranges. > In that case, check out www.geeks.com (the old computergeeks), they > have a number of drives for sale under $49.95. The oranges we are comparing are "acceptable solutions to wanting to isolate subsystems." The original solution was to buy modern disks, and put lots of partitions on them. My proposed solution is to buy a number of cheap boxes. A cheaper solution (the cheapest?) is to buy lots of small, cheap disks. (and before somebody brings it up, the costs involved only include the up-front cost.) They all have their tradeoffs, but the point I made is that objecting to my solution over the original one because of price doesn't carry that much weight. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 15:26:57 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2091016A4DF; Fri, 28 Jul 2006 15:26:57 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mta13.adelphia.net (mta13.mail.adelphia.net [68.168.78.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22A5943D4C; Fri, 28 Jul 2006 15:26:55 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.236] (really [70.32.199.60]) by mta13.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060728152654.WKCA10992.mta13.adelphia.net@[192.168.1.236]>; Fri, 28 Jul 2006 11:26:54 -0400 Message-ID: <44CA2CBE.2050207@savvis.net> Date: Fri, 28 Jul 2006 08:26:54 -0700 From: maksim yevmenkin User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Maxime Henrion References: <1153997829.12770@origin.intron.ac> <864px31eyz.fsf@xps.des.no> <86psfryvvo.fsf@xps.des.no> <44C8CFA2.3000400@savvis.net> <868xme28nt.fsf@xps.des.no> <44C90D22.5010607@savvis.net> <86slkmzx4o.fsf@xps.des.no> <20060728113705.GZ8070@elvis.mu.org> <44CA226B.1030608@savvis.net> <20060728145157.GA8070@elvis.mu.org> In-Reply-To: <20060728145157.GA8070@elvis.mu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, re@freebsd.org Subject: Re: How to Use ddb(4)? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 15:26:57 -0000 Maxime Henrion wrote: > maksim yevmenkin wrote: >> Maxime Henrion wrote: >>> Dag-Erling Sm?rgrav wrote: >>>> Maksim Yevmenkin writes: >>>>> so far i only got one (successful) report. would people please give >>>>> it a try to see if work, so i can commit it. >>>> Please commit it. I don't see how it can do any harm. >>> Yes please; I'd like to see this patch in HEAD as soon as possible so >>> that we can have as much coverage as possible since this is the kind of >>> fix that will be very desirable to MFC for 6.2-RELEASE. >> patch was committed to head yesterday. > > Yeah, I just saw it, I was quite behind with my mail. Thanks! > >>> BTW, does your patch also fix similar problems with kbdmux(4) and the >>> geli mountroot prompt? >> yes, it should. please let me know if you still have this kind of >> problems with kbdmux(4) and atkbd(4) > > Great. I haven't had the time to look at the patch yet, but can you > foresee any problem with MFC'ing it or would you consider it safe? i will mfc it in one week (just like the commit comment says). i can mfc it earlier providing that enough people try it and confirm that it fixes the problem. there should be no problem with mfc'ing it, imo. the patch is a minor hack and makes kbdmux(4) explicitly poll slave keyboards in "polled" mode only. thanks, max From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 16:17:11 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C81D16A583 for ; Fri, 28 Jul 2006 16:17:11 +0000 (UTC) (envelope-from sean-freebsd@farley.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E7CA43D4C for ; Fri, 28 Jul 2006 16:17:10 +0000 (GMT) (envelope-from sean-freebsd@farley.org) Received: from thor.farley.org (thor.farley.org [IPv6:2001:470:1f01:290:1::5]) by mail.farley.org (8.13.4/8.13.1) with ESMTP id k6SGMZmt064054; Fri, 28 Jul 2006 11:22:35 -0500 (CDT) (envelope-from sean-freebsd@farley.org) Date: Fri, 28 Jul 2006 11:17:03 -0500 (CDT) From: "Sean C. Farley" To: "M. Warner Losh" In-Reply-To: <20060728.084709.-135504445.imp@bsdimp.com> Message-ID: <20060728111116.Q82732@thor.farley.org> References: <20060728.084709.-135504445.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: scheidell@secnap.net, freebsd-hackers@freebsd.org Subject: Re: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 16:17:11 -0000 On Fri, 28 Jul 2006, M. Warner Losh wrote: > In message: > "Michael Scheidell" writes: > : > -----Original Message----- > : > From: M. Warner Losh [mailto:imp@bsdimp.com] > : > Sent: Thursday, July 27, 2006 9:39 PM > : > To: Michael Scheidell > : > Cc: freebsd-hackers@freebsd.org > : > Subject: Re: FBSD 5.5 and software timers > : > : I am going to try to nail down just what and why this happens and > : post that. > : (reminder: even if this change happened in 3.4, it didn't affect me > : till 5.5) > > It might be useful to find the change. There was a fix for an issue I had with nanosleep() in the past (gnu/77818[1]) that might be related. It went into 5.4-STABLE. Sean 1. http://www.freebsd.org/cgi/query-pr.cgi?pr=gnu/77818 -- sean-freebsd@farley.org From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 17:01:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7706516A4DD for ; Fri, 28 Jul 2006 17:01:41 +0000 (UTC) (envelope-from amdmi3@mail.ru) Received: from mx27.mail.ru (mx27.mail.ru [194.67.23.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id B852043D45 for ; Fri, 28 Jul 2006 17:01:40 +0000 (GMT) (envelope-from amdmi3@mail.ru) Received: from [213.148.29.33] (port=53264 helo=nexii.panopticon) by mx27.mail.ru with esmtp id 1G6ViV-000GGE-00; Fri, 28 Jul 2006 21:01:39 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.2]) by nexii.panopticon (Postfix) with ESMTP id 55A2911411; Fri, 28 Jul 2006 21:07:19 +0400 (MSD) Received: by hades.panopticon (Postfix, from userid 1000) id 3D24A4A; Fri, 28 Jul 2006 21:03:19 +0400 (MSD) Date: Fri, 28 Jul 2006 21:03:19 +0400 From: Dmitry Marakasov To: freebsd-hackers@freebsd.org Message-ID: <20060728170319.GA69506@hades.panopticon> Mail-Followup-To: freebsd-hackers@freebsd.org, Giorgos Keramidas , Timur Yuldashev References: <44BFAE1D.30906@cwt.uz> <44C0D55B.60500@preved.cn> <20060722042347.GE53239@gothmog.pc> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20060722042347.GE53239@gothmog.pc> User-Agent: Mutt/1.5.11 Cc: Giorgos Keramidas , Timur Yuldashev Subject: Re: New Welcome message for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 17:01:41 -0000 * Giorgos Keramidas (keramida@ceid.upatras.gr) wrote: > >> New motd-welcome message for FreeBSD. > >> > >> http://www.cwt.uz/motd > >> > >> best regards > > I like it! Very good. > I don't. It is pretty "content free" when compared with our current > default motd. I agree, FreeBSD is serious OS, and it's not good idea to add ASCII beastie and other fancy stuff anywhere (not into loader menu, nor into motd). But, if by any chance thing like this happens, I think it's best to make it eye candy as much as possible. For example, `FreeBSD' would look better in anti-aliased way, like this (just an ugly example): .sssso .ss. .ss. .sss. d' d' `b d' `' $ `& $, .ss. .ss. .ss. $ .P ?. $ `o $$so d' `' d' `b d' `b $ssss. `*o. $ @ $' $ @ssssD @ssssD $ `b `b $ .P $ $ q. q. $ .P ,. .P $ .* $ $ *ss* *ss* $ssss* ^ss' ?ss*` -- Best regards, Dmitry mailto:amdmi3@mail.ru From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 15:44:02 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE55416A4DF for ; Fri, 28 Jul 2006 15:44:02 +0000 (UTC) (envelope-from scheidell@secnap.net) Received: from mail.secnap.com (mail.secnap.com [204.89.241.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 402D343D46 for ; Fri, 28 Jul 2006 15:44:02 +0000 (GMT) (envelope-from scheidell@secnap.net) Received: from [10.70.3.3] (unknown [10.70.3.3]) by mail.secnap.com (Postfix) with ESMTP id 26721164838; Fri, 28 Jul 2006 11:44:01 -0400 (EDT) Message-ID: <44CA30C0.1090702@secnap.net> Date: Fri, 28 Jul 2006 11:44:00 -0400 From: Michael Scheidell Organization: SECNAP Network Security User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530) MIME-Version: 1.0 To: "M. Warner Losh" References: <20060728.084709.-135504445.imp@bsdimp.com> In-Reply-To: <20060728.084709.-135504445.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 28 Jul 2006 17:23:10 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: FBSD 5.5 and software timers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 15:44:02 -0000 M. Warner Losh wrote: > : > : I replaced libc_r with libpthread and it immediately reboots the system! > > Neither of these is good! Does it happen on 6? > > Don't know, I had enough trouble going from 5.4 to 5.5 :-( 6.x might not even run on my hardware. > : I am going to try to nail down just what and why this happens and post > : that. > : (reminder: even if this change happened in 3.4, it didn't affect me till > : 5.5) > > It might be useful to find the change. > > Warner > > -- Michael Scheidell, CTO SECNAP Network Security / www.secnap.com scheidell@secnap.net / 1+561-999-5000, x 1131 From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 22:36:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABC2716A4DF; Fri, 28 Jul 2006 22:36:31 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73DD043D49; Fri, 28 Jul 2006 22:36:29 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.4.20060308/8.13.4) with ESMTP id k6SMaRsT089447; Fri, 28 Jul 2006 15:36:27 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.13.4.20060308/8.13.4/Submit) id k6SMaRlj089446; Fri, 28 Jul 2006 15:36:27 -0700 (PDT) Date: Fri, 28 Jul 2006 15:36:27 -0700 (PDT) From: Matthew Dillon Message-Id: <200607282236.k6SMaRlj089446@apollo.backplane.com> To: Andreas Klemm References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> <20060727202528.GA14954@titan.klemm.apsfilter.org> Cc: freebsd-hackers@freebsd.org Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 22:36:31 -0000 :On Thu, Jul 27, 2006 at 02:21:59PM +0200, Joerg Sonnenberger wrote: :> On Thu, Jul 27, 2006 at 08:39:37AM +0200, Andreas Klemm wrote: :> > Later I wanted to mount the dfly filesystems on FreeBSD 6.1, :> > of course still my main Unix ;-) But it wasn't possible. :> :> DragonFly disklabels allow 16 entries by default, FreeBSD still limits :> it to 8. That's why you can't read it directly. :> : :Hmm, for the sake of compatibility, wouldn't it have been an option, :to add this extra bit to the end of the struct ? : : Andreas /// : :-- :Andreas Klemm - Powered by FreeBSD 6 The thing to note here is that FreeBSD had to make room for the UFS1+UFS2 boot code, so it moved the boot code back to the point where it abuts the 8-partition-sized disklabel. So at least insofar as FreeBSD goes, the partition table cannot be expanded to 16 partitions with UFS1+UFS2 boot code. I'm guessing that it *could* be expanded to 16 partitions with UFS1 only or UFS2 only boot code (assuming the boot code were relocated back to where it was originally in FreeBSD-4/5 times, before UFS2 came along). With regards to simply recognizing a DragonFly partition... yes, that would be easy to do. Since FreeBSD is now devfs-based, the bit we had to steal to support 16 partitions in /dev isn't an issue. I dunno if geom changes the equation any. Personally I have always felt that 8 partitions is restrictive. My main home server has 10 and the main DragonFly box has 11. There is another solution for FreeBSD folks, however. You *DO* have four slices to play with. You can put a disklabel with 8 partitions in it on each one (for 32 total). It isn't as convenient, but it does work. -Matt Matthew Dillon From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 28 23:00:39 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D29B16A4DA for ; Fri, 28 Jul 2006 23:00:19 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id AF07643D46 for ; Fri, 28 Jul 2006 23:00:18 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 84741 invoked by uid 1001); 28 Jul 2006 23:00:17 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Fri, 28 Jul 2006 19:00:17 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17610.38657.274287.959855@bhuda.mired.org> Date: Fri, 28 Jul 2006 19:00:17 -0400 To: Matthew Dillon In-Reply-To: <200607282236.k6SMaRlj089446@apollo.backplane.com> References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> <20060727202528.GA14954@titan.klemm.apsfilter.org> <200607282236.k6SMaRlj089446@apollo.backplane.com> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 23:00:39 -0000 In <200607282236.k6SMaRlj089446@apollo.backplane.com>, Matthew Dillon typed: > There is another solution for FreeBSD folks, however. You *DO* have > four slices to play with. You can put a disklabel with 8 partitions > in it on each one (for 32 total). It isn't as convenient, but it does > work. Um, that's "many" slices. The extended slice can hold as many slices as you want. The OS accessing them may have limits (I don't know if FreeBSD does or not). FreeBSD can put partitions in logical slices, but it can't boot from them. There are other options for those that want them. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Sat Jul 29 03:36:40 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE98C16A4DD for ; Sat, 29 Jul 2006 03:36:40 +0000 (UTC) (envelope-from mrcpu@mathisen.org) Received: from mathisen.org (main.mathisen.org [70.58.179.172]) by mx1.FreeBSD.org (Postfix) with SMTP id B4ED143D45 for ; Sat, 29 Jul 2006 03:36:39 +0000 (GMT) (envelope-from mrcpu@mathisen.org) Received: (qmail 18680 invoked by uid 29999); 29 Jul 2006 03:43:59 -0000 Date: Fri, 28 Jul 2006 20:43:59 -0700 From: Jaye Mathisen To: hackers@freebsd.org Message-ID: <20060729034359.GL15569@main.mathisen.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Cc: Subject: fdescfs functional in 6.1? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jul 2006 03:36:40 -0000 I will confess, I have on idea if this is what's supposed to be happening. The OpenBSD spam filter system need access to /dev/fd/7. Man page says that I need to mount the fdescfs to get access. Fine. I'm running 6.1-STABLE. So here's what I see, and it looks very odd: devfs is mounted, fdesc is unmounted: s2# ls -l /dev/fd total 0 crw-rw-rw- 1 root wheel 250, 0 Jul 25 03:25 0 crw-rw-rw- 1 root wheel 250, 1 Jul 25 03:28 1 crw-rw-rw- 1 root wheel 250, 2 Jul 25 03:27 2 Looks just like I think it should. Then: s2# mount -t fdescfs fdescfs /dev/fd s2# ls -l /dev/fd total 16 crw--w---- 1 root tty 5, 1 Jul 28 18:01 0 crw--w---- 1 root tty 5, 1 Jul 28 18:01 1 crw--w---- 1 root tty 5, 1 Jul 28 18:01 2 d-w------- 1 mailnull mailnull 512 Jul 23 00:01 3 d--------- 1 root wheel 512 Jul 25 03:25 4 s2# umount /dev/fd This thing is all over the map.. permissions changed, a *directory* for fd's 3 and 4? SO I can believe that fdescfs is broken, is there some way to create the entries via mknod on bootup, or some entry in the devfs source that will make say through fd 20? Or is it working just like it should, and I should just not worry about it? From owner-freebsd-hackers@FreeBSD.ORG Sat Jul 29 04:18:50 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0983516A4DD for ; Sat, 29 Jul 2006 04:18:50 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CD7843D46 for ; Sat, 29 Jul 2006 04:18:49 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.4) id k6T4ImNu055138; Fri, 28 Jul 2006 23:18:48 -0500 (CDT) (envelope-from dan) Date: Fri, 28 Jul 2006 23:18:48 -0500 From: Dan Nelson To: Jaye Mathisen Message-ID: <20060729041848.GC15827@dan.emsphone.com> References: <20060729034359.GL15569@main.mathisen.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060729034359.GL15569@main.mathisen.org> X-OS: FreeBSD 5.5-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.12-2006-07-14 Cc: hackers@freebsd.org Subject: Re: fdescfs functional in 6.1? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jul 2006 04:18:50 -0000 In the last episode (Jul 28), Jaye Mathisen said: > devfs is mounted, fdesc is unmounted: > > s2# ls -l /dev/fd > total 0 > crw-rw-rw- 1 root wheel 250, 0 Jul 25 03:25 0 > crw-rw-rw- 1 root wheel 250, 1 Jul 25 03:28 1 > crw-rw-rw- 1 root wheel 250, 2 Jul 25 03:27 2 > > Looks just like I think it should. > > Then: > s2# mount -t fdescfs fdescfs /dev/fd > s2# ls -l /dev/fd > total 16 > crw--w---- 1 root tty 5, 1 Jul 28 18:01 0 > crw--w---- 1 root tty 5, 1 Jul 28 18:01 1 > crw--w---- 1 root tty 5, 1 Jul 28 18:01 2 > d-w------- 1 mailnull mailnull 512 Jul 23 00:01 3 > d--------- 1 root wheel 512 Jul 25 03:25 4 > s2# umount /dev/fd > > This thing is all over the map.. permissions changed, a *directory* > for fd's 3 and 4? What do you expect ls to open to print a *directory* listing? :) fd's 0, 1, and 2 are /dev/tty, and the permissions look fine. fd 3 is your current directory (so I guess you're in some smtp-related directory?), and fd 4 is the directory on the commandline (/dev/fd). -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Sat Jul 29 06:09:35 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38C4016A4DD for ; Sat, 29 Jul 2006 06:09:35 +0000 (UTC) (envelope-from mrcpu@mathisen.org) Received: from mathisen.org (main.mathisen.org [70.58.179.172]) by mx1.FreeBSD.org (Postfix) with SMTP id E949A43D46 for ; Sat, 29 Jul 2006 06:09:33 +0000 (GMT) (envelope-from mrcpu@mathisen.org) Received: (qmail 20059 invoked by uid 29999); 29 Jul 2006 06:16:53 -0000 Date: Fri, 28 Jul 2006 23:16:53 -0700 From: Jaye Mathisen To: Dan Nelson Message-ID: <20060729061653.GM15569@main.mathisen.org> References: <20060729034359.GL15569@main.mathisen.org> <20060729041848.GC15827@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060729041848.GC15827@dan.emsphone.com> User-Agent: Mutt/1.5.6i Cc: hackers@freebsd.org Subject: Re: fdescfs functional in 6.1? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jul 2006 06:09:35 -0000 I guess I just expected it to print all character device entries for the file descriptors open by my process. Kind of like the old /dev/fd/1 /dev/fd/2 directories used to be under MAKEDEV... On Fri, Jul 28, 2006 at 11:18:48PM -0500, Dan Nelson wrote: > In the last episode (Jul 28), Jaye Mathisen said: > > devfs is mounted, fdesc is unmounted: > > > > s2# ls -l /dev/fd > > total 0 > > crw-rw-rw- 1 root wheel 250, 0 Jul 25 03:25 0 > > crw-rw-rw- 1 root wheel 250, 1 Jul 25 03:28 1 > > crw-rw-rw- 1 root wheel 250, 2 Jul 25 03:27 2 > > > > Looks just like I think it should. > > > > Then: > > s2# mount -t fdescfs fdescfs /dev/fd > > s2# ls -l /dev/fd > > total 16 > > crw--w---- 1 root tty 5, 1 Jul 28 18:01 0 > > crw--w---- 1 root tty 5, 1 Jul 28 18:01 1 > > crw--w---- 1 root tty 5, 1 Jul 28 18:01 2 > > d-w------- 1 mailnull mailnull 512 Jul 23 00:01 3 > > d--------- 1 root wheel 512 Jul 25 03:25 4 > > s2# umount /dev/fd > > > > This thing is all over the map.. permissions changed, a *directory* > > for fd's 3 and 4? > > What do you expect ls to open to print a *directory* listing? :) > > fd's 0, 1, and 2 are /dev/tty, and the permissions look fine. > > fd 3 is your current directory (so I guess you're in some smtp-related > directory?), and fd 4 is the directory on the commandline (/dev/fd). > > -- > Dan Nelson > dnelson@allantgroup.com > > > !DSPAM:44caf09f196113296012617! > From owner-freebsd-hackers@FreeBSD.ORG Sat Jul 29 09:50:08 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDA8116A4DE for ; Sat, 29 Jul 2006 09:50:08 +0000 (UTC) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED54543D46 for ; Sat, 29 Jul 2006 09:50:07 +0000 (GMT) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (localhost [IPv6:::1]) by srv1.cosmo-project.de (8.12.10/8.12.10) with ESMTP id k6T9o5nZ017777 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 29 Jul 2006 11:50:06 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.12.10/8.12.10/Submit) with UUCP id k6T9o51L017776 for freebsd-hackers@freebsd.org; Sat, 29 Jul 2006 11:50:05 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: from titan.klemm.apsfilter.org (localhost.klemm.apsfilter.org [127.0.0.1]) by klemm.apsfilter.org (8.13.6/8.13.4) with ESMTP id k6T9liMs005939 for ; Sat, 29 Jul 2006 11:47:44 +0200 (CEST) (envelope-from andreas@titan.klemm.apsfilter.org) Received: (from andreas@localhost) by titan.klemm.apsfilter.org (8.13.6/8.13.4/Submit) id k6T9lhn4005938 for freebsd-hackers@freebsd.org; Sat, 29 Jul 2006 11:47:43 +0200 (CEST) (envelope-from andreas) Date: Sat, 29 Jul 2006 11:47:43 +0200 From: Andreas Klemm To: freebsd-hackers@freebsd.org Message-ID: <20060729094743.GA5840@titan.klemm.apsfilter.org> References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> <20060727202528.GA14954@titan.klemm.apsfilter.org> <200607282236.k6SMaRlj089446@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200607282236.k6SMaRlj089446@apollo.backplane.com> X-Operating-System: FreeBSD 6.1-STABLE X-Disclaimer: A free society is one where it is safe to be unpopular User-Agent: Mutt/1.5.11 Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jul 2006 09:50:09 -0000 On Fri, Jul 28, 2006 at 03:36:27PM -0700, Matthew Dillon wrote: > :On Thu, Jul 27, 2006 at 02:21:59PM +0200, Joerg Sonnenberger wrote: > :> On Thu, Jul 27, 2006 at 08:39:37AM +0200, Andreas Klemm wrote: > : > :Hmm, for the sake of compatibility, wouldn't it have been an option, > :to add this extra bit to the end of the struct ? > : Andreas /// > > The thing to note here is that FreeBSD had to make room for the > UFS1+UFS2 boot code, so it moved the boot code back to the point > where it abuts the 8-partition-sized disklabel. > > So at least insofar as FreeBSD goes, the partition table cannot be > expanded to 16 partitions with UFS1+UFS2 boot code. I'm guessing > that it *could* be expanded to 16 partitions with UFS1 only or > UFS2 only boot code (assuming the boot code were relocated back > to where it was originally in FreeBSD-4/5 times, before UFS2 came > along). > > With regards to simply recognizing a DragonFly partition... yes, > that would be easy to do. Since FreeBSD is now devfs-based, the > bit we had to steal to support 16 partitions in /dev isn't an issue. Couldn't all BSDs restructure the disklabel in -current so that we would have the same base for the next major release ? Then its only a question of drivers to suppot UFS2 or not. But then compatibility would be there for some time ... Incompatible to UFS's like from Sun I think we are already, so we don't have to honour them. Remember a current thread in german BSD group where somebody complained about FreeBSD - mounting a Sun filesystem r/w - destroyed the filesystem. Luckily he could recover using fsck -b 32. Andreas /// -- Andreas Klemm - Powered by FreeBSD 6 Need a magic printfilter today ? -> http://www.apsfilter.org/ From owner-freebsd-hackers@FreeBSD.ORG Sat Jul 29 14:13:17 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEDF616A4DD for ; Sat, 29 Jul 2006 14:13:17 +0000 (UTC) (envelope-from amdmi3@mail.ru) Received: from mx2.mail.ru (mx2.mail.ru [194.67.23.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5888443D49 for ; Sat, 29 Jul 2006 14:13:17 +0000 (GMT) (envelope-from amdmi3@mail.ru) Received: from [213.148.29.33] (port=1680 helo=nexii.panopticon) by mx2.mail.ru with esmtp id 1G6pZ6-0006li-00; Sat, 29 Jul 2006 18:13:16 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.2]) by nexii.panopticon (Postfix) with ESMTP id 200F311413; Sat, 29 Jul 2006 18:13:14 +0400 (MSD) Received: by hades.panopticon (Postfix, from userid 1000) id 787424340; Sat, 29 Jul 2006 18:13:13 +0400 (MSD) Date: Sat, 29 Jul 2006 18:13:13 +0400 From: Dmitry Marakasov To: Matthew Dillon Message-ID: <20060729141313.GA43548@hades.panopticon> Mail-Followup-To: Matthew Dillon , freebsd-hackers@freebsd.org References: <20060727063936.GA1246@titan.klemm.apsfilter.org> <20060727122159.GB4217@britannica.bec.de> <20060727202528.GA14954@titan.klemm.apsfilter.org> <200607282236.k6SMaRlj089446@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <200607282236.k6SMaRlj089446@apollo.backplane.com> User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: disklabel differences FreeBSD, DragonFly X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jul 2006 14:13:17 -0000 * Matthew Dillon (dillon@apollo.backplane.com) wrote: > felt that 8 partitions is restrictive. My main home server has 10 > and the main DragonFly box has 11. > > There is another solution for FreeBSD folks, however. You *DO* have > four slices to play with. You can put a disklabel with 8 partitions > in it on each one (for 32 total). It isn't as convenient, but it does > work. About `lack' of partitions - don't forget that labels can be nested. Just do `bsdlabel -w /dev/ad0s1e` - you'll get /dev/ad0s1ea. -- Best regards, Dmitry mailto:amdmi3@mail.ru From owner-freebsd-hackers@FreeBSD.ORG Sat Jul 29 19:10:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C3F316A4E1 for ; Sat, 29 Jul 2006 19:10:53 +0000 (UTC) (envelope-from tijl@ulyssis.org) Received: from outmx009.isp.belgacom.be (outmx009.isp.belgacom.be [195.238.5.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44CAF43D5C for ; Sat, 29 Jul 2006 19:10:50 +0000 (GMT) (envelope-from tijl@ulyssis.org) Received: from outmx009.isp.belgacom.be (localhost [127.0.0.1]) by outmx009.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6TJAg4C030636 for ; Sat, 29 Jul 2006 21:10:42 +0200 (envelope-from ) Received: from kalimero.kotnet.org (64.211-245-81.adsl-dyn.isp.belgacom.be [81.245.211.64]) by outmx009.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22) with ESMTP id k6TJAdCH030602 for ; Sat, 29 Jul 2006 21:10:39 +0200 (envelope-from ) Received: from kalimero.kotnet.org (kalimero.kotnet.org [127.0.0.1]) by kalimero.kotnet.org (8.13.6/8.13.6) with ESMTP id k6TJAcvL014021 for ; Sat, 29 Jul 2006 21:10:39 +0200 (CEST) (envelope-from tijl@ulyssis.org) From: Tijl Coosemans To: freebsd-hackers@freebsd.org Date: Sat, 29 Jul 2006 21:10:32 +0200 User-Agent: KMail/1.9.3 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart10993165.DIXgWSgbTg"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607292110.37733.tijl@ulyssis.org> Subject: i386 page fault clobbers error code in trap frame X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jul 2006 19:10:53 -0000 --nextPart10993165.DIXgWSgbTg Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I'm refering to the following two lines in sys/i386/i386/trap.c /* kludge to pass faulting virtual address to sendsig */ frame->tf_err =3D eva; Isn't there some other way to do this? Wouldn't the address still be=20 available in %cr2 inside sendsig? Or could there have been other page=20 faults by then? The reason I'm asking this is that Wine wants to know the error code in=20 case of a page fault (the No eXec bit (AMD) and the read/write bit=20 specifically). --nextPart10993165.DIXgWSgbTg Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQBEy7KtdMR2xnarec8RAl9QAKCCc2Hqen6/xYDyqbXMdBu2sBlHjwCg0tQx LXotmZDebQV/s/nj3T4B+aM= =vxez -----END PGP SIGNATURE----- --nextPart10993165.DIXgWSgbTg-- From owner-freebsd-hackers@FreeBSD.ORG Sat Jul 29 19:58:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1CDC16A4E0 for ; Sat, 29 Jul 2006 19:58:53 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CCA343DD5 for ; Sat, 29 Jul 2006 19:57:53 +0000 (GMT) (envelope-from kip.macy@gmail.com) Received: by py-out-1112.google.com with SMTP id b36so142616pyb for ; Sat, 29 Jul 2006 12:57:52 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=M8zoLtkfoy2f8QCpQ0AKT7M6FRsQgibvp9FGU0f/zfHAeZiI4mCZM73kwOcWoXzqA25Ilt8FIga4l2h3CMGoUSCsbetG3vdH49pz95K0x9j905eHUpto/THlvelgzdB5bfqRY0C140h4P02bcqvNZnXNREYi2GQG2KXAxny4uRg= Received: by 10.35.114.16 with SMTP id r16mr1204753pym; Sat, 29 Jul 2006 12:57:52 -0700 (PDT) Received: by 10.35.16.20 with HTTP; Sat, 29 Jul 2006 12:57:52 -0700 (PDT) Message-ID: Date: Sat, 29 Jul 2006 12:57:52 -0700 From: "Kip Macy" To: "Tijl Coosemans" In-Reply-To: <200607292110.37733.tijl@ulyssis.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200607292110.37733.tijl@ulyssis.org> Cc: freebsd-hackers@freebsd.org Subject: Re: i386 page fault clobbers error code in trap frame X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kmacy@fsmware.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jul 2006 19:58:53 -0000 Looking at siginfo it isn't clear that there is a "right way" to provide SIGSEGV, eva, and the error code. _fault._trapno should contain the machine's error code and si_signo should contain SIGSEGV, and si_addr contains the faulting pc. Maybe one could abuse si_code to contain eva. Sorry for asking a question that has already been answered but where is eva being put currently? typedef struct __siginfo { int si_signo; /* signal number */ int si_errno; /* errno association */ /* * Cause of signal, one of the SI_ macros or signal-specific * values, i.e. one of the FPE_... values for SIGFPE. This * value is equivalent to the second argument to an old-style * FreeBSD signal handler. */ int si_code; /* signal code */ __pid_t si_pid; /* sending process */ __uid_t si_uid; /* sender's ruid */ int si_status; /* exit value */ void *si_addr; /* faulting instruction */ union sigval si_value; /* signal value */ union { struct { int _trapno;/* machine specific trap code */ } _fault; /* .... */ On 7/29/06, Tijl Coosemans wrote: > I'm refering to the following two lines in sys/i386/i386/trap.c > > /* kludge to pass faulting virtual address to sendsig */ > frame->tf_err = eva; > > Isn't there some other way to do this? Wouldn't the address still be > available in %cr2 inside sendsig? Or could there have been other page > faults by then? > > The reason I'm asking this is that Wine wants to know the error code in > case of a page fault (the No eXec bit (AMD) and the read/write bit > specifically). > > > From owner-freebsd-hackers@FreeBSD.ORG Sat Jul 29 20:30:08 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 307D416A4DD for ; Sat, 29 Jul 2006 20:30:08 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95EC943D46 for ; Sat, 29 Jul 2006 20:30:07 +0000 (GMT) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.221] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id k6TKTujU091598; Sat, 29 Jul 2006 13:30:01 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <44CBC544.4090500@freebsd.org> Date: Sat, 29 Jul 2006 13:29:56 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <44C82A40.3020009@centtech.com> In-Reply-To: <44C82A40.3020009@centtech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers Subject: Re: [PATCH] adding two new options to 'cp' X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jul 2006 20:30:08 -0000 Eric Anderson wrote: > So, you can mimic an entire tree with something like: > cp -al /from/ /to/ pax -rwl -pe /from /to is almost what you want. (It requires that /to exist first, though.) If you want to match the 'cp' semantics when /to does not exist, you can use pax's rewrite option: pax -rwl -pe -s|/from|/to| /from / As a bonus, this works on any machine that meets POSIX, unlike every other option that's been mentioned in this thread (tar and cpio were both dropped from the POSIX standard a decade ago). Tim From owner-freebsd-hackers@FreeBSD.ORG Sat Jul 29 20:47:42 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D13416A4DA for ; Sat, 29 Jul 2006 20:47:42 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25D9F43D49 for ; Sat, 29 Jul 2006 20:47:42 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.4) id k6TKlfQh063868; Sat, 29 Jul 2006 15:47:41 -0500 (CDT) (envelope-from dan) Date: Sat, 29 Jul 2006 15:47:41 -0500 From: Dan Nelson To: Jaye Mathisen Message-ID: <20060729204741.GD15827@dan.emsphone.com> References: <20060729034359.GL15569@main.mathisen.org> <20060729041848.GC15827@dan.emsphone.com> <20060729061653.GM15569@main.mathisen.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060729061653.GM15569@main.mathisen.org> X-OS: FreeBSD 5.5-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.12-2006-07-14 Cc: hackers@freebsd.org Subject: Re: fdescfs functional in 6.1? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jul 2006 20:47:42 -0000 In the last episode (Jul 28), Jaye Mathisen said: > On Fri, Jul 28, 2006 at 11:18:48PM -0500, Dan Nelson wrote: > > In the last episode (Jul 28), Jaye Mathisen said: > > > s2# mount -t fdescfs fdescfs /dev/fd > > > s2# ls -l /dev/fd > > > total 16 > > > crw--w---- 1 root tty 5, 1 Jul 28 18:01 0 > > > crw--w---- 1 root tty 5, 1 Jul 28 18:01 1 > > > crw--w---- 1 root tty 5, 1 Jul 28 18:01 2 > > > d-w------- 1 mailnull mailnull 512 Jul 23 00:01 3 > > > d--------- 1 root wheel 512 Jul 25 03:25 4 > > > s2# umount /dev/fd > > > > > > This thing is all over the map.. permissions changed, a *directory* > > > for fd's 3 and 4? > > > > What do you expect ls to open to print a *directory* listing? :) > > > > fd's 0, 1, and 2 are /dev/tty, and the permissions look fine. > > > > fd 3 is your current directory (so I guess you're in some smtp-related > > directory?), and fd 4 is the directory on the commandline (/dev/fd). > > > > I guess I just expected it to print all character device entries for > the file descriptors open by my process. fdescfs prints all file desriptors open by your process, and displays the correct info for each of them. > Kind of like the old /dev/fd/1 /dev/fd/2 directories used to be under > MAKEDEV... Before devfs, /dev/fd was populated with dummy entries from 0 to 63 and running ls on the directory had no correspondence with what your process actually had open. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Sat Jul 29 20:52:55 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEF2716A4DA for ; Sat, 29 Jul 2006 20:52:55 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (megan.kiwi-computer.com [63.224.10.3]) by mx1.FreeBSD.org (Postfix) with SMTP id D11A543D6B for ; Sat, 29 Jul 2006 20:52:54 +0000 (GMT) (envelope-from rick@kiwi-computer.com) Received: (qmail 69144 invoked by uid 2001); 29 Jul 2006 20:52:53 -0000 Date: Sat, 29 Jul 2006 15:52:53 -0500 From: "Rick C. Petty" To: Jaye Mathisen Message-ID: <20060729205253.GA69105@megan.kiwi-computer.com> References: <20060729034359.GL15569@main.mathisen.org> <20060729041848.GC15827@dan.emsphone.com> <20060729061653.GM15569@main.mathisen.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060729061653.GM15569@main.mathisen.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: fdescfs functional in 6.1? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jul 2006 20:52:56 -0000 On Fri, Jul 28, 2006 at 11:16:53PM -0700, Jaye Mathisen wrote: > I guess I just expected it to print all character device entries for the > file descriptors open by my process. It did-- well it printed all the file descriptors open by your process, which in this case was "ls". 0, 1, and 2 are stdin, stdout, and stderr (respectfully) and they point to the device you logged into. Try doing "ls -la /dev/fd | less" and I'll bet 1 will be a pipe? This seems like the correct operation; I'm not sure I understand what you expected and why that's different than what you've observed. > Kind of like the old /dev/fd/1 /dev/fd/2 directories used to be under MAKEDEV... How is that the same? MAKEDEV was in the day before devfs, so the device entries needed to be created by the underlying filesystem. In devfs, things are only present if they represent an active device. -- Rick C. Petty