From owner-freebsd-hackers@FreeBSD.ORG Sun May 3 07:11:17 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 192D41065674 for ; Sun, 3 May 2009 07:11:17 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 2C4BE8FC14 for ; Sun, 3 May 2009 07:11:15 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 03 May 2009 07:11:14 -0000 Received: from p54A3DFED.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.223.237] by mail.gmx.net (mp062) with SMTP; 03 May 2009 09:11:14 +0200 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX1/+GocFGSb+8rHm9duOasvX86IrLHmYoWlKayL1DN IBRRJjYO+vutNb Message-ID: <49FD4391.9070605@gmx.de> Date: Sun, 03 May 2009 09:11:13 +0200 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.21 (X11/20090412) MIME-Version: 1.0 To: "M. Warner Losh" References: <49FCA148.9060707@gmx.de> <49FCAA1D.1080208@elischer.org> <49FCAFA2.60603@gmx.de> <20090502.151931.1396014860.imp@bsdimp.com> In-Reply-To: <20090502.151931.1396014860.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.57 Cc: sobomax@FreeBSD.org, freebsd-hackers@FreeBSD.org, rdivacky@FreeBSD.org, ed@FreeBSD.org, dwmalone@maths.tcd.ie, julian@elischer.org Subject: Re: C99: Suggestions for style(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: Sun, 03 May 2009 07:11:17 -0000 M. Warner Losh schrieb: > In message: <49FCAFA2.60603@gmx.de> > Christoph Mallon writes: > : Julian Elischer schrieb: > : >> Christoph Mallon wrote: > : >>>> K&R code should be changed as part of related changes if possible. > : >>>> A sweep to change a whole file is probably also ok. > : >>>> changing them one at a time is probably not ok. > : >>> > : >>> But this is what actually is practiced. > : >>> You still did not answer my question: Do you agree to remove the > : >>> clause so no new old style declarations may be added? > : > > : > I think a new clause should be added specifying what should happen > : > and replacing the old clause. > : > : This is not sensible. style(9) says right at the start that it "[...] > : specifies the preferred style for kernel source files [...]". The > : preferred style would be to use ANSI function declarations - what else > : is there to say? There is no point in adding more when less is sufficient. > > Actually, in a style guide, there is a point. > > Adding language that says we're actively removing K&R-style > declarations and definitions reinforces this point and explains to > people what's going on when they see this in the tree today. This just overcomplicates things. "removing old style definitions" is not the preferred style, but "using prototyped definitions" is. Old style definitions should not be added anymore, so just remove the clause, which allows it currently. Adding even more about old style definitions is counterproductive - I cannot support this. What to do, when you are seeing an old style definition is clear: Don't Panic! Christoph From owner-freebsd-hackers@FreeBSD.ORG Sun May 3 16:28:03 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6573106566B; Sun, 3 May 2009 16:28:03 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 68FFF8FC2C; Sun, 3 May 2009 16:28:03 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id n43GOikI039151; Sun, 3 May 2009 10:24:44 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 03 May 2009 10:24:44 -0600 (MDT) Message-Id: <20090503.102444.1683323216.imp@bsdimp.com> To: christoph.mallon@gmx.de From: "M. Warner Losh" In-Reply-To: <49FD4391.9070605@gmx.de> References: <49FCAFA2.60603@gmx.de> <20090502.151931.1396014860.imp@bsdimp.com> <49FD4391.9070605@gmx.de> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: sobomax@FreeBSD.org, freebsd-hackers@FreeBSD.org, rdivacky@FreeBSD.org, ed@FreeBSD.org, dwmalone@maths.tcd.ie, julian@elischer.org Subject: Re: C99: Suggestions for style(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: Sun, 03 May 2009 16:28:04 -0000 In message: <49FD4391.9070605@gmx.de> Christoph Mallon writes: : M. Warner Losh schrieb: : > In message: <49FCAFA2.60603@gmx.de> : > Christoph Mallon writes: : > : Julian Elischer schrieb: : > : >> Christoph Mallon wrote: : > : >>>> K&R code should be changed as part of related changes if possible. : > : >>>> A sweep to change a whole file is probably also ok. : > : >>>> changing them one at a time is probably not ok. : > : >>> : > : >>> But this is what actually is practiced. : > : >>> You still did not answer my question: Do you agree to remove the : > : >>> clause so no new old style declarations may be added? : > : > : > : > I think a new clause should be added specifying what should happen : > : > and replacing the old clause. : > : : > : This is not sensible. style(9) says right at the start that it "[...] : > : specifies the preferred style for kernel source files [...]". The : > : preferred style would be to use ANSI function declarations - what else : > : is there to say? There is no point in adding more when less is sufficient. : > : > Actually, in a style guide, there is a point. : > : > Adding language that says we're actively removing K&R-style : > declarations and definitions reinforces this point and explains to : > people what's going on when they see this in the tree today. : : This just overcomplicates things. "removing old style definitions" is : not the preferred style, but "using prototyped definitions" is. Old : style definitions should not be added anymore, so just remove the : clause, which allows it currently. Adding even more about old style : definitions is counterproductive - I cannot support this. What to do, : when you are seeing an old style definition is clear: Don't Panic! I think you are wrong, and I think your failure to take constructive criticism is alienating a lot of people that would otherwise support at least part of what you are trying to do. I know I've had it enough. Warner From owner-freebsd-hackers@FreeBSD.ORG Sun May 3 18:59:57 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CE2C106566C for ; Sun, 3 May 2009 18:59:57 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.freebsd.org (Postfix) with ESMTP id 156C48FC12 for ; Sun, 3 May 2009 18:59:55 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-216-167.belrs3.nsw.optusnet.com.au [122.106.216.167]) by mail14.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n43Ixqfl032418 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 May 2009 04:59:53 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id n43IxpYN062180; Mon, 4 May 2009 04:59:51 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id n43Ixowu062173; Mon, 4 May 2009 04:59:50 +1000 (EST) (envelope-from peter) Date: Mon, 4 May 2009 04:59:50 +1000 From: Peter Jeremy To: John Gemignani Message-ID: <20090503185950.GA62081@server.vk2pj.dyndns.org> References: <108501c9c8fe$3a30ab0e$72020a0a@desktop.isilon.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline In-Reply-To: <108501c9c8fe$3a30ab0e$72020a0a@desktop.isilon.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.19 (2009-01-05) X-Mailman-Approved-At: Sun, 03 May 2009 19:12:47 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: C99: Suggestions for style(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: Sun, 03 May 2009 18:59:57 -0000 --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2009-Apr-29 12:10:44 -0700, John Gemignani w= rote:=20 >Are local variables allocated on-the-fly on the stack or does the >compiler preallocate the space on entry? This is compiler and optimisation dependent. As a general rule, if a compiler is not performing any optimisation, it is likely to allocate all variables on the stack. An obvious code optimisation is to keep variables in registers instead of storing them on the stack. In the specific case of older gcc versions with optimisation enabled (I'm not sure of the behaviour of gcc 4.x), gcc will immediately spill (allocate on the stack) local variables that aren't eligible to be held in registers (eg too large or the variable address is taken) and allocate remaining variables to virtual registers. During code generation, virtual registers are mapped to physical registers and any remaining virtual registers are allocated on the stack. > If I have to delve into a >crashdump, having the variables on the big entry allocation has been >very helpful in the past. OTOH, not caching variables in registers has a significant adverse impact on performance. --=20 Peter Jeremy --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkn96aYACgkQ/opHv/APuIeUlQCghdfapFUS4oq1QlKxGhl+4Ui6 F9IAoLCv+iOrQcFdgTD2FCcmh6SAugca =b42X -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR-- From owner-freebsd-hackers@FreeBSD.ORG Mon May 4 15:16:26 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56C5E106566B; Mon, 4 May 2009 15:16:26 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 250358FC15; Mon, 4 May 2009 15:16:26 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: (from root@localhost) by kientzle.com (8.14.3/8.14.3) id n44FGP8a056751; Mon, 4 May 2009 08:16:25 -0700 (PDT) (envelope-from kientzle@freebsd.org) Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2]) by kientzle.com with SMTP id tmcqvhnnehmucuxk2kv4rvryja; Mon, 04 May 2009 08:16:25 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <49FF06C9.6070001@freebsd.org> Date: Mon, 04 May 2009 08:16:25 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.21) Gecko/20090409 SeaMonkey/1.1.15 MIME-Version: 1.0 To: Garrett Cooper References: <20090430214520.GA37974@flint.openpave.org> <7d6fde3d0905020546s697ad5f6r2098ff6c80a80e1e@mail.gmail.com> In-Reply-To: <7d6fde3d0905020546s697ad5f6r2098ff6c80a80e1e@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jeremy Lea , David Forsythe , freebsd-hackers@freebsd.org Subject: Re: SoC2009: libpkg, pkg tools rewrite 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, 04 May 2009 15:16:26 -0000 >> On Sat, Apr 25, 2009 at 03:20:59PM -0400, David Forsythe wrote: >>> This summer I'll be working on creating a package library and using >>> that library to rewrite the pkg tools. Jeremy Lea wrote: > Since I've already done most of the work on this already, please, > please, please, don't ignore what I have done. Garrett Cooper wrote: > There's also http://libpkg.berlios.de/ that you could use as a > starting point, and please, PLEASE, don't neglect the SoC work that > was done last year by Anders Nore. It was committed to p4, but hasn't > made it upstream to CVS yet... Good architectural summaries would help here; I know David already has a lot of background reading planned before start-of-coding this summer. Can you provide pointers to design documents or email threads discussing any of these? I'm not familiar with Anders work; what is the current status of it? Why hasn't it been pushed into SVN yet? Is there a good summary of what it does so far and what remains to be done? Cheers, Tim From owner-freebsd-hackers@FreeBSD.ORG Mon May 4 15:35:20 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA8B6106566B; Mon, 4 May 2009 15:35:19 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id A3C668FC14; Mon, 4 May 2009 15:35:19 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: (from root@localhost) by kientzle.com (8.14.3/8.14.3) id n44FZJVd057015; Mon, 4 May 2009 08:35:19 -0700 (PDT) (envelope-from kientzle@freebsd.org) Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2]) by kientzle.com with SMTP id b2sivu489rb6ncx3akvxukj33i; Mon, 04 May 2009 08:35:18 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <49FF0B36.2030805@freebsd.org> Date: Mon, 04 May 2009 08:35:18 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.21) Gecko/20090409 SeaMonkey/1.1.15 MIME-Version: 1.0 To: Jeremy Lea References: <20090430214520.GA37974@flint.openpave.org> In-Reply-To: <20090430214520.GA37974@flint.openpave.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: David Forsythe , freebsd-hackers@freebsd.org Subject: Re: SoC2009: libpkg, pkg tools rewrite 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, 04 May 2009 15:35:20 -0000 Jeremy Lea: > 1. The library needs a global "package manager". This needs to perform > all of the tasks, and it should ideally do this through a task queue > (which I didn't implement). See the lib/lib.h header in FreePKG. This sounds like a good idea to implement ... eventually. First job is to identify the tasks and a way to implement them. It's relatively straightforward to add a task queue wrapper later on. > 4. bsd.port.mk should do everything through the tools. It should have > no knowledge of the contents of /var/db/pkg. I agree with this in principle, but I think it would be better to avoid touching bsd.port.mk at all in this iteration. Certainly, it's worthwhile to read bsd.port.mk carefully to try to understand the capabilities missing from the current tools with an eye to supporting those in a future iteration, but I think it's more important to keep the scope of this summer's work as narrow as possible. > 1. I made the file->pkg database to sensitive. If there is a miss it > rebuilds the database for scratch - it should do a search through the > +CONTENTS files and only rebuild it if there was a hit (meaning the > database was wrong). I'm going to show my ignorance here: Why is this database necessary at all? On my system with just over 500 packages, it takes <1s to read all of /var/db/pkg with a warm cache (~10s cold cache), and I can only think of a couple of cases where the file->pkg database is useful at all. I fear that maintaining a file->pkg database is a lot of extra effort for very little gain. I would be more interested in experimenting with using extended attributes directly on the files to record what package they came from. In particular, that provides much more robust handling for a variety of use cases, including conflicts, stale files, and manually-updated files. > 2. There needs to be a pkgname and origin database, which can be loaded > at startup to prime the package manager. The dependency graph should > also be stored in a database. These should be rebuilt if any directory > in /var/db/pkg has a mtime later than the database (so could the file > database). Again, I'm a little skeptical of the need for separate databases here at all. In the current system, /var/db/pkg and the package archives themselves have to be authoritative, so any package system has to be able to work directly from that information. Building a separate database from that information seems like a lot of extra work that will pay off someday but can be largely avoided for the current iteration. Remember that the Single Point of Truth for any package manager is the files on disk. If someone deletes the files from disk, then the package is not installed, regardless of what any "package database" might say. In the case of the FreeBSD package system, /var/db/pkg is therefore secondary data and any additional databases you compute from /var/db/pkg are tertiary. This is getting pretty far from the SPoT and is going to lead to increasing consistency problems. If we can avoid these additional databases, we'll get a simpler, more robust system. > 3. There needs to be a set of flags which indicate how a package got > installed (as a dependency or by the user), and if it has been upgraded > in-place and might have old leftover libraries. These could go in > +CONTENTS. Yes, these are the kind of features that should be easy to add after the package tools have been rewritten around libpkg. But first we need a basic libpkg that works and a set of package tools that use it. > In addition I also began the design of a new on disk package format. I'm pretty firmly opposed to this. I think that the INDEX, /var/db/pkg, and binary format for package archives all need to be kept essentially unchanged, simply because of the growing number of third-party tools that interact with them. Eventually, such tools may all be rewritten to use libpkg, at which point it may be reasonable to reconsider, but for the foreseeable future, any changes to these would cause a lot of pain for little gain. There may be some incremental changes (such as the installation flags you mention above) that would help, but I think we're stuck with the current formats for the time being. I'll also observe that some of the concerns that drove your new package archive design are no longer relevant; libarchive allows us to use tar format without forking the tar executable. Tim From owner-freebsd-hackers@FreeBSD.ORG Mon May 4 17:22:23 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AABC0106566C for ; Mon, 4 May 2009 17:22:23 +0000 (UTC) (envelope-from msaad@datapipe.com) Received: from EXFESMQ01.datapipe-corp.net (exfesmq01.datapipe-corp.net [64.106.130.69]) by mx1.freebsd.org (Postfix) with ESMTP id 350A38FC08 for ; Mon, 4 May 2009 17:22:23 +0000 (UTC) (envelope-from msaad@datapipe.com) Received: from [192.168.128.22] (192.168.128.22) by EXFESMQ01.datapipe-corp.net (64.106.130.71) with Microsoft SMTP Server (TLS) id 8.1.340.0; Mon, 4 May 2009 13:12:09 -0400 Message-ID: <49FF21E7.4060201@datapipe.com> Date: Mon, 4 May 2009 13:12:07 -0400 From: Mark Saad User-Agent: Thunderbird 2.0.0.21 (X11/20090302) MIME-Version: 1.0 To: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Subject: ZFS ARC Cache: What is the lowest tested size X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: msaad@datapipe.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 May 2009 17:22:24 -0000 Hello List Worked on breaking ZFS we came across a interesting question; What is the lowest tested ZFS ARC Cache size ? Also could you reliably run with it set to 0 ? -- Mark Saad msaad@datapipe.com () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments This message may contain confidential or privileged information. If you ar= e not the intended recipient, please advise us immediately and delete this = message. See http://www.datapipe.com/emaildisclaimer.aspx for further info= rmation on confidentiality and the risks of non-secure electronic communica= tion. If you cannot access these links, please notify us by reply message a= nd we will send the contents to you. From owner-freebsd-hackers@FreeBSD.ORG Mon May 4 17:39:03 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A6DB1065672 for ; Mon, 4 May 2009 17:39:03 +0000 (UTC) (envelope-from matt@ixsystems.com) Received: from n18.bullet.mail.mud.yahoo.com (n18.bullet.mail.mud.yahoo.com [68.142.206.145]) by mx1.freebsd.org (Postfix) with SMTP id 19D238FC0C for ; Mon, 4 May 2009 17:39:03 +0000 (UTC) (envelope-from matt@ixsystems.com) Received: from [68.142.200.227] by n18.bullet.mail.mud.yahoo.com with NNFMP; 04 May 2009 17:25:48 -0000 Received: from [68.142.201.250] by t8.bullet.mud.yahoo.com with NNFMP; 04 May 2009 17:26:00 -0000 Received: from [127.0.0.1] by omp411.mail.mud.yahoo.com with NNFMP; 04 May 2009 17:26:00 -0000 X-Yahoo-Newman-Id: 630933.98943.bm@omp411.mail.mud.yahoo.com Received: (qmail 90366 invoked from network); 4 May 2009 17:26:00 -0000 Received: from unknown (HELO ?192.168.1.65?) (matt@75.5.240.87 with plain) by smtp102.sbc.mail.sp1.yahoo.com with SMTP; 4 May 2009 17:25:59 -0000 X-YMail-OSG: WjXOUfkVM1khyhKNWXkVGIIL0ys4iSnW2T4uVEYgfGMfam9mJ6.F6VIYWvQlfRxUADqomsMP0iW49fBEQxkJmKqg5Xcsm2vE5ybVPhWk4URqmeJledJoUVqm6H6sqDNYgDHg8JYWlVNfxsgUA.yEx.i3E9Kc6LWVR96rlAI09MFaaNV76KwlAbuTrjc9Ttm9XteDTgbR902q6m.Cx5RxPyrgHasY3TztCZgSqAK9hMq52gI1.nvL2OLq7BzyjPvBWI81g76OUcjw0B8U51hWGggAgrXT6FL1evaBB305PG58lrFQ6nD1fovZEA3UmbJvau3IjqtcC1wEWTMYhR0k8ufUDTEWneR7SnvVG6rZsPDncbt7hyN.538- X-Yahoo-Newman-Property: ymail-3 Message-Id: From: Matt Olander To: hackers@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 4 May 2009 10:25:58 -0700 X-Mailer: Apple Mail (2.930.3) Cc: Subject: VirtualBox on 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, 04 May 2009 17:39:03 -0000 Looks like the VirtualBox developers at Sun ported VirtualBox to FreeBSD in their spare time: http://www.freebsdnews.net/2009/05/02/sun-virtualbox-on-freebsd/ They're looking for developers/testers to checkout the source and try it out :-) -matt From owner-freebsd-hackers@FreeBSD.ORG Mon May 4 18:18:30 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37826106566C for ; Mon, 4 May 2009 18:18:30 +0000 (UTC) (envelope-from gamaral@amaral.com.mx) Received: from lady-of-fire.guillermoamaral.com (lady-of-fire.guillermoamaral.com [209.172.34.252]) by mx1.freebsd.org (Postfix) with ESMTP id D03578FC12 for ; Mon, 4 May 2009 18:18:29 +0000 (UTC) (envelope-from gamaral@amaral.com.mx) Received: from localhost (localhost.localdomain [127.0.0.1]) by lady-of-fire.guillermoamaral.com (Postfix) with ESMTP id A26D416AC197; Mon, 4 May 2009 13:55:24 -0400 (EDT) Received: from lady-of-fire.guillermoamaral.com ([127.0.0.1]) by localhost (lady-of-fire.guillermoamaral.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z7rbp-9I5bxb; Mon, 4 May 2009 13:55:23 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=amaral.com.mx; h=date: from:to:cc:subject:message-id:references:mime-version: content-type:in-reply-to; q=dns/txt; s=lady-of-fire; bh=rwu1R+21 uplIWD7jEln6m6LV+FU=; b=SD9pCEa9cN9DzbPT5t/x7RNASe1oivW5iIkb6qyx wTHwjinmfhHOt5vr6IRs+FiyeA+ZsmXqhCyhyOyU/2V4Tyana8Kipi87bEXoYsTj s8yUhkV1zHYmPPGbVT6VcguGw035l5uR6UxscyhtsIw6L3TtUXrS8fXYXojDhbEz 5a0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=amaral.com.mx; h=date:from:to:cc:subject:message-id:references:mime-version:content-type:in-reply-to; q=dns; s=lady-of-fire; b= YA/6vRJbdBaoRfkj0L47l6nTH/ZriJ9UTSyTkgNioqdpv2C3UYpMQmNFTf+RuUP1 bX37I34TGK1/8dZXPPPt/XyridH1laKBWS88gbr955UGULYJT6gcNOuUuqijJWVg w4MgBfJXeaT0vJCd4ZUgf/kPrx93+eZycNHcpT23sbk= Received: from amaral.com.mx (201.170.32.151.dsl.dyn.telnor.net [201.170.32.151]) (Authenticated sender: gamaral@amaral.com.mx) by lady-of-fire.guillermoamaral.com (Postfix) with ESMTP id 8285216AC14E; Mon, 4 May 2009 13:55:21 -0400 (EDT) Received: by amaral.com.mx (nbSMTP-1.00) for uid 1001 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) gamaral@amaral.com.mx; Mon, 4 May 2009 10:55:21 -0700 (PDT) Date: Mon, 4 May 2009 10:55:20 -0700 From: Guillermo Antonio Amaral Bastidas To: Matt Olander Message-ID: <20090504175520.GA3163@DAEDALUS.localdomain> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD/7.2-PRERELEASE (i386) X-Crypto: GnuPG/2.0.11 http://www.gnupg.org X-GPG-Key: http://dl.guillermoamaral.com/public.asc X-GPG-Fingerprint: E068 811D 4AA2 7FDA A327 38BD 640D 014C 76FE 7D5A Organization: gamaral User-Agent: Mutt/1.5.19 (2009-01-05) Cc: hackers@freebsd.org Subject: Re: VirtualBox on 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, 04 May 2009 18:18:30 -0000 --7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 04, 2009 at 10:25:58AM -0700, Matt Olander wrote: > Looks like the VirtualBox developers at Sun ported VirtualBox to =20 > FreeBSD in their spare time: > http://www.freebsdnews.net/2009/05/02/sun-virtualbox-on-freebsd/ >=20 > They're looking for developers/testers to checkout the source and try =20 > it out :-) Awesome! I will test it out, if it works out that means I could change my GFs desktop to FreeBSD. ^_^=20 --=20 Guillermo Antonio Amaral Bastidas (gamaral) Free/Libre/Open-Source Software Developer : http://www.guillermoamaral.com/ KDE Official Representative MX : http://www.kde.org/ PC-BSD Official Representative MX : http://www.pcbsd.org/ GPG Fingerprint: E068 811D 4AA2 7FDA A327 38BD 640D 014C 76FE 7D5A --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkn/LAcACgkQ7qhsTOTYlb1eYACguHB1Zgy/SAcn3Jcftx5S6ELZ UlEAoLEGRbfeV4bYmdD7Uw4TvGIeKchE =qLMA -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH-- From owner-freebsd-hackers@FreeBSD.ORG Mon May 4 18:27:20 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C577A1065670 for ; Mon, 4 May 2009 18:27:18 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: from mail-ew0-f171.google.com (mail-ew0-f171.google.com [209.85.219.171]) by mx1.freebsd.org (Postfix) with ESMTP id 1B6918FC0C for ; Mon, 4 May 2009 18:27:17 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: by ewy19 with SMTP id 19so4011630ewy.43 for ; Mon, 04 May 2009 11:27:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:received:date:from:to:subject :message-id:mime-version:content-type:content-disposition; bh=nRGh7h38q5ucXP9zIHZfqj/Ng92Numl2INstEQSN/0A=; b=a3JEVWOpmyVQAG3H/PnmOSshgUEXtVq7HqEAAi1j0v83Ul4dRkskcxtCk957lk1IKA ob0x/UysBkQkowq+j8N2gyu0PGKv8UiyFvmyyMatQIQsZE8QgNBILqkPcdikiN1tmoX6 KhGWCg2iYWG1osTIUrmLJ8o/bpXUCw5f9yA+I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:subject:message-id:mime-version:content-type :content-disposition; b=ODGFhcbwOpI6YvKHw0jVsGaDX7aQ1Rp6yYPKZSgyLWv66dzZkljMPzpAC6cV1e13eQ kiJjotxFvhdUaizaAMmWzlMohQ9UzZShkrljr3LbzHm8K60MLeD3/Y8bfaMtq9M7eCpD 95VY054iPUJJEl1d/e9OVwl6wia3P0EDhhJ/A= Received: by 10.210.71.11 with SMTP id t11mr5041382eba.49.1241461637126; Mon, 04 May 2009 11:27:17 -0700 (PDT) Received: from logik.internal.network (81-86-41-187.dsl.pipex.com [81.86.41.187]) by mx.google.com with ESMTPS id 18sm7829974ewy.45.2009.05.04.11.27.15 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 May 2009 11:27:16 -0700 (PDT) Received: by logik.internal.network (Postfix, from userid 11001) id 6F4C65C31; Mon, 4 May 2009 18:27:14 +0000 (UTC) Date: Mon, 4 May 2009 19:27:14 +0100 From: xorquewasp@googlemail.com To: freebsd-hackers@freebsd.org Message-ID: <20090504182714.GA52480@logik.internal.network> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: bootstrapping gnat GCC on amd64 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, 04 May 2009 18:27:21 -0000 Hello. I'm attempting to compile GNAT on AMD64 with an eye to extending support to the platform (the gnat-gcc43 port is ONLY_FOR_ARCH=i386). GNAT obviously requires an Ada compiler to bootstrap. What are my options here? I suspect that I need to create an i386 jail to build a cross compiler but am not sure. Any help would be appreciated. xw From owner-freebsd-hackers@FreeBSD.ORG Mon May 4 18:44:55 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA6AD1065678 for ; Mon, 4 May 2009 18:44:54 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 4B7188FC41 for ; Mon, 4 May 2009 18:44:54 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id n44IiqHt015336; Mon, 4 May 2009 14:44:52 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Mon, 04 May 2009 14:44:53 -0400 (EDT) Date: Mon, 4 May 2009 14:44:52 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: xorquewasp@googlemail.com In-Reply-To: <20090504182714.GA52480@logik.internal.network> Message-ID: References: <20090504182714.GA52480@logik.internal.network> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: bootstrapping gnat GCC on amd64 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, 04 May 2009 18:44:57 -0000 On Mon, 4 May 2009, xorquewasp@googlemail.com wrote: > Hello. > > I'm attempting to compile GNAT on AMD64 with an eye to > extending support to the platform (the gnat-gcc43 port > is ONLY_FOR_ARCH=i386). > > GNAT obviously requires an Ada compiler to bootstrap. > > What are my options here? > > I suspect that I need to create an i386 jail to build > a cross compiler but am not sure. Is that your only system (amd64)? I originally ported GNAT to FreeBSD x86 from a solaris-sparc32 system. I built a sparc-sun-freebsd GNAT cross compiler using the native Solaris GNAT binary and its associated sources. I also (first) had to cross build binutils similarly. This made a cross compiler that ran on Solaris and built ELF binaries for FreeBSD. I then used this cross compiler to rebuild GNAT as a FreeBSD binary. So it was 2 major steps: build a cross compiler, then use the cross to build a native compiler. It's been years since I've done that. I don't know how much has changed, but you probably have to do something similar. -- DE From owner-freebsd-hackers@FreeBSD.ORG Mon May 4 18:56:49 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E3771065674 for ; Mon, 4 May 2009 18:56:49 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: from mail-ew0-f171.google.com (mail-ew0-f171.google.com [209.85.219.171]) by mx1.freebsd.org (Postfix) with ESMTP id 802078FC0C for ; Mon, 4 May 2009 18:56:48 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: by ewy19 with SMTP id 19so4041277ewy.43 for ; Mon, 04 May 2009 11:56:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:received:date:from:to:cc :subject:message-id:references:mime-version:content-type :content-disposition:in-reply-to; bh=OCWjqmBp6Mwhr+0nkfwHnk55ZHtAS7EcsLX/4t3a4PI=; b=ROanvNdrG6wfEobDxJvSDTCw7nXiFG+VwvqDv2HRdwz0pzKmPWK2a6UUNdhkUNT9mW HWum9U/npvYdRur3fiFmMl1xexFvmehcQdXg2Mzi6hNm6S9RPFXgnqrIB4BT1e4C7qi3 Cjf9wd5BBeelu6H3u5TTTdMI0KhFiy8u2/aE8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to; b=Bs9mjphsiWl9RbSwrTp6qFKc9NN0BETxm+kPOOJw7AEQ8fhHAcm0CmEcV1WokgpvJU PkE5Cq5+L0uU36BvG2pe3oS/xHJ/nF4WxFc3rpm9Udfv8067V/7+oZgKoCR0EgEyxiJN vijxfo/4YWmjpQcdwpgLP1wiR7sA3eQ8UKZgs= Received: by 10.216.1.85 with SMTP id 63mr1865861wec.26.1241463407163; Mon, 04 May 2009 11:56:47 -0700 (PDT) Received: from logik.internal.network (81-86-41-187.dsl.pipex.com [81.86.41.187]) by mx.google.com with ESMTPS id 28sm7763274ewy.24.2009.05.04.11.56.46 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 May 2009 11:56:46 -0700 (PDT) Received: by logik.internal.network (Postfix, from userid 11001) id 77BD15C31; Mon, 4 May 2009 18:56:44 +0000 (UTC) Date: Mon, 4 May 2009 19:56:44 +0100 From: xorquewasp@googlemail.com To: Daniel Eischen Message-ID: <20090504185644.GA16315@logik.internal.network> References: <20090504182714.GA52480@logik.internal.network> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-hackers@freebsd.org Subject: Re: bootstrapping gnat GCC on amd64 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, 04 May 2009 18:56:49 -0000 On 2009-05-04 14:44:52, Daniel Eischen wrote: > Is that your only system (amd64)? I originally > ported GNAT to FreeBSD x86 from a solaris-sparc32 system. > I built a sparc-sun-freebsd GNAT cross compiler using > the native Solaris GNAT binary and its associated > sources. I also (first) had to cross build binutils > similarly. This made a cross compiler that ran on > Solaris and built ELF binaries for FreeBSD. I then > used this cross compiler to rebuild GNAT as a FreeBSD > binary. So it was 2 major steps: build a cross compiler, > then use the cross to build a native compiler. > > It's been years since I've done that. I don't know > how much has changed, but you probably have to do > something similar. > > -- > DE Hello. I have a debian system with a working x86 gnat gcc 4.3.3 and a freebsd x86 system running gnat gcc 4.3.2. I guess the first step will be an i386->amd64 cross compiler then. Thanks, xw From owner-freebsd-hackers@FreeBSD.ORG Mon May 4 19:03:34 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45FB110656B1 for ; Mon, 4 May 2009 19:03:34 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id EF4AF8FC25 for ; Mon, 4 May 2009 19:03:33 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id n44J3Wd5027394; Mon, 4 May 2009 15:03:32 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Mon, 04 May 2009 15:03:32 -0400 (EDT) Date: Mon, 4 May 2009 15:03:32 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: xorquewasp@googlemail.com In-Reply-To: <20090504185644.GA16315@logik.internal.network> Message-ID: References: <20090504182714.GA52480@logik.internal.network> <20090504185644.GA16315@logik.internal.network> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: bootstrapping gnat GCC on amd64 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, 04 May 2009 19:03:36 -0000 On Mon, 4 May 2009, xorquewasp@googlemail.com wrote: > On 2009-05-04 14:44:52, Daniel Eischen wrote: >> Is that your only system (amd64)? I originally >> ported GNAT to FreeBSD x86 from a solaris-sparc32 system. >> I built a sparc-sun-freebsd GNAT cross compiler using >> the native Solaris GNAT binary and its associated >> sources. I also (first) had to cross build binutils >> similarly. This made a cross compiler that ran on >> Solaris and built ELF binaries for FreeBSD. I then >> used this cross compiler to rebuild GNAT as a FreeBSD >> binary. So it was 2 major steps: build a cross compiler, >> then use the cross to build a native compiler. >> >> It's been years since I've done that. I don't know >> how much has changed, but you probably have to do >> something similar. >> >> -- >> DE > > Hello. > > I have a debian system with a working x86 gnat gcc 4.3.3 > and a freebsd x86 system running gnat gcc 4.3.2. > > I guess the first step will be an i386->amd64 cross > compiler then. Right, you should be able to do it from either of those, but perhaps the freebsd x86 may be easier. I would use a PREFIX other than /usr/local (or something different than whatever your actual PREFIX is) for the builds. I was looking around for my notes but can't find them. If I do find them, I'll post them. -- DE From owner-freebsd-hackers@FreeBSD.ORG Mon May 4 19:22:22 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C769F1065783 for ; Mon, 4 May 2009 19:22:22 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 92E3D8FC17 for ; Mon, 4 May 2009 19:22:22 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 4685146BA4; Mon, 4 May 2009 15:22:22 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 275E88A023; Mon, 4 May 2009 15:22:21 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Mon, 4 May 2009 10:46:02 -0400 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905041046.02920.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 04 May 2009 15:22:21 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.5 required=4.2 tests=AWL,BAYES_00, DATE_IN_PAST_03_06,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Andrew Brampton Subject: Re: Definition of NULL 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, 04 May 2009 19:22:23 -0000 On Saturday 02 May 2009 11:59:03 am Andrew Brampton wrote: > I'm writing a C++ Kernel Module, and one thing that has been bugging > me is the kernel's definition of NULL. > > sys/sys/_null.h (in CURRENT): > > #if defined(_KERNEL) || !defined(__cplusplus) > #define NULL ((void *)0) > #else > #if defined(__GNUG__) && defined(__GNUC__) && __GNUC__ >= 4 > #define NULL __null > #else > #if defined(__LP64__) > #define NULL (0L) > #else > #define NULL 0 > #endif /* __LP64__ */ > #endif /* __GNUG__ */ > #endif /* _KERNEL || !__cplusplus */ > > >From what I've read online the definition of NULL in C is (void *)0, > whereas in C++ it should be 0, or 0L (on 64bit machines). > > Now, my C++ kernel module is built with _KERNEL definited, like any > other C kernel module. This leads to NULL being defined incorrectly. > > So I have a question and two suggestions. Firstly, why is the #if > defined(_KERNEL) in _null.h? Is it to stop userland application > applications picking up this definition? Or for another reason? Yes. NULL used to be 0. When it was changed to '(void *)0' I believe it broke several applications in ports. As a compromise, NULL was restored back to 0 in userland and only set to '(void *)0' in the kernel. > and two, how about we change the first line of _null.h so that we use > a && instead of a || like so: > #if defined(_KERNEL) && !defined(__cplusplus) I think this would be ok to let C++ work in the kernel. "Embedded" C++ (no exceptions and no dynamic_cast<>) should work fine in theory. I would not change the value of NULL that userland sees though as I think that may be too risky. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Mon May 4 20:05:18 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E5C4106564A for ; Mon, 4 May 2009 20:05:18 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id 366F68FC08 for ; Mon, 4 May 2009 20:05:18 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so2501807ywe.13 for ; Mon, 04 May 2009 13:05:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=s5DIfk/aqmuAgypheE4H5A03F45i35LvIrjqAkBSiD4=; b=H14fbPo1AzD6SEr9O+m7LgycgOuC6Rz7OV9bbgyML3BaPT7zOj+rRua/pd9ekwI4xj UcU8m0lvzNiLTaygbaebp0tL+AU6SQLmOSfG8tnub6tWw7SxegMzFa2OlXVyTFiecbw/ notpO44tXGP9wCgr0L3aaQ2yS3CA6QLxdftE0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=p6bU43SctRR/4pFpjohP6SMUwPS6Vj4QuBiDpM7fjbSdacCv5l00JRX4amNPdnAP7l AlchzguhulZsq/khQlgQnrPrB+VcKb7hPczvaSPKebkm/+Ev+wVhY16nBPEImylGQCwC xpwEWCx2OztpmpzayuB5x8mtbdwcVhzAu3LoI= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.100.229.12 with SMTP id b12mr13912174anh.26.1241467517598; Mon, 04 May 2009 13:05:17 -0700 (PDT) In-Reply-To: <49FF21E7.4060201@datapipe.com> References: <49FF21E7.4060201@datapipe.com> Date: Mon, 4 May 2009 13:05:17 -0700 X-Google-Sender-Auth: d4fda1022e6fb917 Message-ID: <3c1674c90905041305g285b4609icd7435d436d3bbe0@mail.gmail.com> From: Kip Macy To: msaad@datapipe.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-hackers@freebsd.org" Subject: Re: ZFS ARC Cache: What is the lowest tested size 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, 04 May 2009 20:05:18 -0000 On Mon, May 4, 2009 at 10:12 AM, Mark Saad wrote: > > Hello List > =A0 Worked on breaking ZFS we came across a interesting question; > What is the lowest tested ZFS ARC Cache size ? I haven't tested it with just over 64MB, but the code indicates that that is the lowest you should try. http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/fs= /zfs/arc.c 3500 /* 3501 * Allow the tunables to override our calculations if they are 3502 * reasonable (ie. over 64MB) 3503 */ 3504 if (zfs_arc_max > 64<<20 && zfs_arc_max < physmem * PAGESIZE) 3505 arc_c_max =3D zfs_arc_max; 3506 if (zfs_arc_min > 64<<20 && zfs_arc_min <=3D arc_c_max) 3507 arc_c_min =3D zfs_arc_min; >Also could you reliably > run with it set to 0 ? For better and worse, ZFS isn't primarily a file system. It is a transactional object store that has a file system as one type of object. The ARC is not a file system buffer cache, it caches virtual device blocks. You might think of it as being more like a very large write-back drive cache. It might work with less than 64MB, but the ARC buffers are what ZIO sends down to disk so it certainly would not work with zero. Cheers, Kip From owner-freebsd-hackers@FreeBSD.ORG Tue May 5 00:51:30 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CEE84106566B; Tue, 5 May 2009 00:51:30 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: from mail-ew0-f171.google.com (mail-ew0-f171.google.com [209.85.219.171]) by mx1.freebsd.org (Postfix) with ESMTP id 2FBBC8FC08; Tue, 5 May 2009 00:51:30 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: by mail-ew0-f171.google.com with SMTP id 19so4307129ewy.43 for ; Mon, 04 May 2009 17:51:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:received:date:from:to:cc :subject:message-id:references:mime-version:content-type :content-disposition:in-reply-to; bh=/yztH21cmWf3z58SXOILXyVa3IgvuRUxxEHiThNi6PM=; b=fEHNGxWFEPG2tDwOWqnwAh5Jc4uuEdxf0L+OAw6kzatWcgySJm/tnv/6lvIB/1Y97e c9v6dU6RurxjN4Ng482AQSkhB7xBa08dP78Dk8OiyhnJBGj+DILIuHuq+qSnwQK6Sh7j wrK1m4Fe/UNe0sFQLreBpbwswc+0HTMMR88/Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to; b=EEG8jYhAyN0IagN7TYusDxGsPWfd5kCCewM/wT7QSEf1QlBBUeiTi0E/d9GmQXYoia QyTrAgquGHzlROPh2iwprUrtvxFV/plOlm8SzeyOtkE4m+L/bO7jBvyYvoKYQDxJpSuH +Td+YlYKLn4TjCa0YoX2Wf3Wc9zudlcWM4+TE= Received: by 10.210.71.11 with SMTP id t11mr5549254eba.61.1241484689892; Mon, 04 May 2009 17:51:29 -0700 (PDT) Received: from logik.internal.network (81-86-41-187.dsl.pipex.com [81.86.41.187]) by mx.google.com with ESMTPS id 22sm8237329ewy.112.2009.05.04.17.51.29 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 May 2009 17:51:29 -0700 (PDT) Received: by logik.internal.network (Postfix, from userid 11001) id 418245C31; Tue, 5 May 2009 00:51:28 +0000 (UTC) Date: Tue, 5 May 2009 01:51:28 +0100 From: xorquewasp@googlemail.com To: Daniel Eischen Message-ID: <20090505005128.GA4519@logik.internal.network> References: <20090504182714.GA52480@logik.internal.network> <20090504185644.GA16315@logik.internal.network> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-hackers@freebsd.org Subject: Re: bootstrapping gnat GCC on amd64 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, 05 May 2009 00:51:31 -0000 On 2009-05-04 15:03:32, Daniel Eischen wrote: > Right, you should be able to do it from either of those, > but perhaps the freebsd x86 may be easier. > > I would use a PREFIX other than /usr/local (or something > different than whatever your actual PREFIX is) for the > builds. > > I was looking around for my notes but can't find them. > If I do find them, I'll post them. I've built an i386 jail and am currently building the gnat-gcc43 port to compile a GNAT cross-compiler (i386 -> amd64). There are two reasons for this whole exercise: I just moved over to amd64 and want a native toolchain and I also have a lot of software written in Ada that I'd like to submit to FreeBSD ports but can't due a lack of an Ada compiler on amd64. I noticed that the gnat-gcc43 port downloads a rather anonymous set of gcc 4.1 bootstrap binaries. I assume I'd have to provide my own in the same manner to create a port? xw From owner-freebsd-hackers@FreeBSD.ORG Tue May 5 01:19:21 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45E6B106564A for ; Tue, 5 May 2009 01:19:21 +0000 (UTC) (envelope-from eischen@vigrid.com) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id EB3258FC22 for ; Tue, 5 May 2009 01:19:20 +0000 (UTC) (envelope-from eischen@vigrid.com) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id n450sk4j028678; Mon, 4 May 2009 20:54:46 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Mon, 04 May 2009 20:54:46 -0400 (EDT) Date: Mon, 4 May 2009 20:54:46 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: xorquewasp@googlemail.com In-Reply-To: <20090505005128.GA4519@logik.internal.network> Message-ID: References: <20090504182714.GA52480@logik.internal.network> <20090504185644.GA16315@logik.internal.network> <20090505005128.GA4519@logik.internal.network> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: bootstrapping gnat GCC on amd64 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, 05 May 2009 01:19:21 -0000 On Tue, 5 May 2009, xorquewasp@googlemail.com wrote: > On 2009-05-04 15:03:32, Daniel Eischen wrote: >> Right, you should be able to do it from either of those, >> but perhaps the freebsd x86 may be easier. >> >> I would use a PREFIX other than /usr/local (or something >> different than whatever your actual PREFIX is) for the >> builds. >> >> I was looking around for my notes but can't find them. >> If I do find them, I'll post them. > > I've built an i386 jail and am currently building the > gnat-gcc43 port to compile a GNAT cross-compiler (i386 -> > amd64). > > There are two reasons for this whole exercise: I just moved > over to amd64 and want a native toolchain and I also have a > lot of software written in Ada that I'd like to submit to > FreeBSD ports but can't due a lack of an Ada compiler on amd64. > > I noticed that the gnat-gcc43 port downloads a rather > anonymous set of gcc 4.1 bootstrap binaries. I assume I'd > have to provide my own in the same manner to create a port? Yes, you can look at my lang/gnat port to find its bootstrap compiler. I would recommend making a binary bootstrap compiler on the earliest version of FreeBSD amd64 as you can. If you use 8.0-current for instance, others will not be able to build the port on 7.x. -- DE From owner-freebsd-hackers@FreeBSD.ORG Tue May 5 02:21:55 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9869C106564A for ; Tue, 5 May 2009 02:21:55 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: from mail-ew0-f171.google.com (mail-ew0-f171.google.com [209.85.219.171]) by mx1.freebsd.org (Postfix) with ESMTP id 21F838FC1A for ; Tue, 5 May 2009 02:21:54 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: by ewy19 with SMTP id 19so4346152ewy.43 for ; Mon, 04 May 2009 19:21:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:received:date:from:to:cc :subject:message-id:references:mime-version:content-type :content-disposition:in-reply-to; bh=XtoLmuU+4KoVRzr2bAw6VfxlYVfbDORnFhAcGIYUH+A=; b=EtW5Hzk/BWwgNgx7bGuXYe0o3vNUPO4eNslH+QppNvSi4zDguhCU2nm0mr5Jus0sGZ v4KbivgKWqkTNr0jj9YFd67rnQBlTYDzxTodhho+Zf8bYzeO3DSIVlRCfbPIl7wSio5Q doz7xsmByRb6NFW5J7ekzlNnSmp07vyrs1j+4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to; b=ZYZW+iP6R8njv6CCDtqIOuoeT8/8P1JNFzlzhUIjZSkcSW80zg13oFb7oQN5D/LRaR /XdiBO0NtTFVwYqBhe3bwnh0dT4HF2HboUzxfkUDe/E79hDKz+7UBqwD/eXrru1gLTz6 LNIvVRQg/CYiQovlJbDvRfcTJgY9r3oir7WX4= Received: by 10.210.60.8 with SMTP id i8mr7122428eba.63.1241490114106; Mon, 04 May 2009 19:21:54 -0700 (PDT) Received: from logik.internal.network (81-86-41-187.dsl.pipex.com [81.86.41.187]) by mx.google.com with ESMTPS id 24sm8372723ewy.25.2009.05.04.19.21.53 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 May 2009 19:21:53 -0700 (PDT) Received: by logik.internal.network (Postfix, from userid 11001) id 4EDEC5C31; Tue, 5 May 2009 02:21:51 +0000 (UTC) Date: Tue, 5 May 2009 03:21:51 +0100 From: xorquewasp@googlemail.com To: Daniel Eischen Message-ID: <20090505022151.GA32477@logik.internal.network> References: <20090504182714.GA52480@logik.internal.network> <20090504185644.GA16315@logik.internal.network> <20090505005128.GA4519@logik.internal.network> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-hackers@freebsd.org Subject: Re: bootstrapping gnat GCC on amd64 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, 05 May 2009 02:21:55 -0000 On 2009-05-04 20:54:46, Daniel Eischen wrote: > Yes, you can look at my lang/gnat port to find its > bootstrap compiler. I would recommend making a binary > bootstrap compiler on the earliest version of FreeBSD > amd64 as you can. If you use 8.0-current for instance, > others will not be able to build the port on 7.x. Earliest version of FreeBSD that fully supports this hardware is 7.2, so I personally can't go back to an earlier release than that. From owner-freebsd-hackers@FreeBSD.ORG Tue May 5 02:24:57 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F127106564A for ; Tue, 5 May 2009 02:24:57 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id DAD8D8FC12 for ; Tue, 5 May 2009 02:24:56 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id n452Ot3g005500; Mon, 4 May 2009 22:24:55 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Mon, 04 May 2009 22:24:55 -0400 (EDT) Date: Mon, 4 May 2009 22:24:55 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: xorquewasp@googlemail.com In-Reply-To: <20090505022151.GA32477@logik.internal.network> Message-ID: References: <20090504182714.GA52480@logik.internal.network> <20090504185644.GA16315@logik.internal.network> <20090505005128.GA4519@logik.internal.network> <20090505022151.GA32477@logik.internal.network> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: bootstrapping gnat GCC on amd64 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: Tue, 05 May 2009 02:24:57 -0000 On Tue, 5 May 2009, xorquewasp@googlemail.com wrote: > On 2009-05-04 20:54:46, Daniel Eischen wrote: >> Yes, you can look at my lang/gnat port to find its >> bootstrap compiler. I would recommend making a binary >> bootstrap compiler on the earliest version of FreeBSD >> amd64 as you can. If you use 8.0-current for instance, >> others will not be able to build the port on 7.x. > > Earliest version of FreeBSD that fully supports this > hardware is 7.2, so I personally can't go back to an > earlier release than that. Keep good notes - maybe someone else can do it once you have the procedure down and working ;-) -- DE From owner-freebsd-hackers@FreeBSD.ORG Tue May 5 03:47:06 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BE281065688 for ; Tue, 5 May 2009 03:47:06 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from www.sonnenberger.org (www.ostsee-abc.de [62.206.222.50]) by mx1.freebsd.org (Postfix) with ESMTP id CC9128FC13 for ; Tue, 5 May 2009 03:47:05 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (www.sonnenberger.org [192.168.1.10]) by www.sonnenberger.org (Postfix) with ESMTP id 68BBE66794 for ; Tue, 5 May 2009 05:47:03 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1000) id A5C351BDCD7; Tue, 5 May 2009 05:47:19 +0200 (CEST) Date: Tue, 5 May 2009 05:47:19 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Message-ID: <20090505034719.GG3417@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <6101e8c40904300750i3e86fc0cnef09b0d4533627f7@mail.gmail.com> <78367CB5-7DAD-4DB1-99DA-2618CFACF376@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <78367CB5-7DAD-4DB1-99DA-2618CFACF376@mac.com> User-Agent: Mutt/1.5.19 (2009-01-05) Subject: Re: NetBSD 5.0 statistics 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, 05 May 2009 03:47:06 -0000 On Thu, Apr 30, 2009 at 01:41:42PM -0700, Marcel Moolenaar wrote: > I recall that our "make -j X" actually limits the number > of make processes/jobs to X. I don't know anything about > build.sh, so I don't know if our make is at all being > involved, but it would be good to know how the load varies > per OS. build.sh is using NetBSD's make for all but the tool build and the tool build is not included in the stats. Joerg From owner-freebsd-hackers@FreeBSD.ORG Tue May 5 03:50:24 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C48671065680 for ; Tue, 5 May 2009 03:50:24 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from www.sonnenberger.org (www.ostsee-abc.de [62.206.222.50]) by mx1.freebsd.org (Postfix) with ESMTP id 8273A8FC14 for ; Tue, 5 May 2009 03:50:19 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (www.sonnenberger.org [192.168.1.10]) by www.sonnenberger.org (Postfix) with ESMTP id 5512166794 for ; Tue, 5 May 2009 05:50:18 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1000) id BCA1C1BDCD7; Tue, 5 May 2009 05:50:34 +0200 (CEST) Date: Tue, 5 May 2009 05:50:34 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Message-ID: <20090505035034.GH3417@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <200905041046.02920.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200905041046.02920.jhb@freebsd.org> User-Agent: Mutt/1.5.19 (2009-01-05) Subject: Re: Definition of NULL 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, 05 May 2009 03:50:25 -0000 On Mon, May 04, 2009 at 10:46:02AM -0400, John Baldwin wrote: > I think this would be ok to let C++ work in the kernel. "Embedded" C++ (no > exceptions and no dynamic_cast<>) should work fine in theory. I would not > change the value of NULL that userland sees though as I think that may be too > risky. Well, use __null if present all the time, fallback to the alternatives as currently defined. Joerg From owner-freebsd-hackers@FreeBSD.ORG Tue May 5 08:35:41 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 528A41065670 for ; Tue, 5 May 2009 08:35:41 +0000 (UTC) (envelope-from jt@0xabadba.be) Received: from mail-ew0-f171.google.com (mail-ew0-f171.google.com [209.85.219.171]) by mx1.freebsd.org (Postfix) with ESMTP id D73BC8FC19 for ; Tue, 5 May 2009 08:35:40 +0000 (UTC) (envelope-from jt@0xabadba.be) Received: by ewy19 with SMTP id 19so4494649ewy.43 for ; Tue, 05 May 2009 01:35:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.8.78 with SMTP id 56mr2219024weq.210.1241510882125; Tue, 05 May 2009 01:08:02 -0700 (PDT) X-Originating-IP: [149.106.224.20] From: jt@0xabadba.be Date: Tue, 5 May 2009 04:07:47 -0400 Message-ID: To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: concurrent sysctl implementation 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, 05 May 2009 08:35:41 -0000 Hackers, I've been using FreeBSD since a boy and now its time for me to give back. I will be doing my final projects in university concerning concurrency in the FreeBSD Kernel. I've been discussing with Ed@ methods of implementing sysctl concurrently since we use sysctl quite a lot for _everything_ essentially (make, general kernel information, etc). I've been reading the sysctl man pages and some of the code in the kernel; however, I wanted to shoot this out to the public since many of you know better than I do about where I should be looking to do the required reading to get the job done correctly. I'm also open to implementing other things once this is done. I hope everyone is doing well. respectfully, =jt From owner-freebsd-hackers@FreeBSD.ORG Tue May 5 08:58:08 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08E10106566B; Tue, 5 May 2009 08:58:08 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [IPv6:2001:770:10:300::86e2:510b]) by mx1.freebsd.org (Postfix) with SMTP id BEDCF8FC08; Tue, 5 May 2009 08:58:06 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 5 May 2009 09:58:05 +0100 (BST) Date: Tue, 5 May 2009 09:58:04 +0100 From: David Malone To: "M. Warner Losh" Message-ID: <20090505085804.GA1274@walton.maths.tcd.ie> References: <1366225354.253456.1238948619308.JavaMail.root@vms124.mailsrvcs.net> <200904061154.19601.jhb@freebsd.org> <20090406.111755.1973602189.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090406.111755.1973602189.imp@bsdimp.com> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: freebsd-hackers@FreeBSD.org, babkin@verizon.net, ivoras@FreeBSD.org, jhb@FreeBSD.org Subject: Re: Patch for MS Hyper V (virtualization) 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, 05 May 2009 08:58:08 -0000 I was talking about the Hyper-V problem with a guy from MS, and he followed up on it for me. It seems this is a known issue, which should be fixed in the latest version of Hyper-V (i.e. the RC of Windows Server 2008 R2 that was released on TechNet last week). David. From owner-freebsd-hackers@FreeBSD.ORG Tue May 5 10:06:41 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A9811065676 for ; Tue, 5 May 2009 10:06:41 +0000 (UTC) (envelope-from vasanth.raonaik@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id 103C98FC12 for ; Tue, 5 May 2009 10:06:40 +0000 (UTC) (envelope-from vasanth.raonaik@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so2734328ywe.13 for ; Tue, 05 May 2009 03:06:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=8a9Edu20bBOQd29bSmKnW+5Nul7gYZvd5hrni32kYZU=; b=xir2cThPIsNQ2s4Oer1KvpTcjueRDFTIjly+xZpOyCbrhk300DzVQ6r+gI87e6SepU MIxgJFDbLU7l8a22PfT3dTDEKUgga6h0WEsIsqZcugae0odZ5EOxYZgbeJblcMUdpR+Q OU2yC+u4V5Pd7YKOJgMypQmzXZZLD6MNrAvdw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=H6/vG6Wtt/GaHnQ2LMlzNVyAjKPsbrdrVctPzD74g3ub2S92cn23N5Km3B4FCKmuxn D99dXrYYh0/qZ8xUfg+W9fU/5X3oD50v5OMvQck7lbeWiDVv6rf+ow2aQ8jNVZVz6wpC 2UC6x/Fzg26PfBf/ckl+be1zAVct3MsFj21aA= MIME-Version: 1.0 Received: by 10.100.206.14 with SMTP id d14mr15357390ang.76.1241516347612; Tue, 05 May 2009 02:39:07 -0700 (PDT) In-Reply-To: References: Date: Tue, 5 May 2009 15:09:07 +0530 Message-ID: From: vasanth raonaik To: jt@0xabadba.be Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: concurrent sysctl implementation 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, 05 May 2009 10:06:41 -0000 Hello Jt, I am a newbee in this alias. I am having a very basic question. It would be really good if you could give me some of this information. Could you please elaborate on what is the current architecture of sysctl implementation and How the concurrency would benefit us. Thanks in advance, Vasanth On Tue, May 5, 2009 at 1:37 PM, wrote: > Hackers, > > I've been using FreeBSD since a boy and now its time for me to give > back. I will be doing my final projects in university concerning > concurrency in the FreeBSD Kernel. I've been discussing with Ed@ methods > of > implementing sysctl concurrently since we use sysctl quite a lot for > _everything_ essentially (make, general kernel information, etc). I've > been > reading the sysctl man pages and some of the code in the kernel; however, I > wanted to shoot this out to the public since many of you know better than I > do about where I should be looking to do the required reading to get the > job > done correctly. I'm also open to implementing other things once this is > done. I hope everyone is doing well. > > respectfully, > > =jt > _______________________________________________ > 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 Tue May 5 10:31:13 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7029106566B for ; Tue, 5 May 2009 10:31:13 +0000 (UTC) (envelope-from simond@irrelevant.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 9C92D8FC0A for ; Tue, 5 May 2009 10:31:13 +0000 (UTC) (envelope-from simond@irrelevant.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 4A27133B904; Tue, 5 May 2009 06:14:22 -0400 (EDT) Received: from web5.messagingengine.com ([10.202.2.214]) by compute1.internal (MEProxy); Tue, 05 May 2009 06:14:22 -0400 Received: by web5.messagingengine.com (Postfix, from userid 99) id 1F6E9145AD; Tue, 5 May 2009 06:14:22 -0400 (EDT) Message-Id: <1241518462.1533.1313800225@webmail.messagingengine.com> X-Sasl-Enc: J6KP4FHEnm4LGvHZwxEW1gnXokfwo5V7jy7JJZjInnp5 1241518462 From: "Simon Dick" To: "Justin G." , freebsd-hackers@freebsd.org Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface References: <5da021490905010848q441781den54eefba85a69f342@mail.gmail.com> In-Reply-To: <5da021490905010848q441781den54eefba85a69f342@mail.gmail.com> Date: Tue, 05 May 2009 11:14:22 +0100 Cc: Subject: Re: Cobalt Raq 550 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, 05 May 2009 10:31:14 -0000 On Fri, 1 May 2009 08:48:09 -0700, "Justin G." said: > Hello Hackers, > > We came into a Cobalt Raq 550 the other day and were wondering if we > could put it to use. I've googled and googled and found only guides > for Linux installs. Much of it is quite similar, but my issue is with > the loader on the device being able to boot into FreeBSD. The device > searches for linux kernel images when booting. > > Does anyone have any experience with installing FreeBSD on a Raq 550? > I wasn't able to find a website with much detail and would appreciate > any hints or leads :-) Doesn't the RaQ 550 have a basic Linux kernel in it's flash? I worked with them at my last job, I don't remember hearing about anyone who'd managed to get anything except linux working on it though (though I'm sure someone must have!) -- Simon Dick simond@irrelevant.org From owner-freebsd-hackers@FreeBSD.ORG Tue May 5 11:37:05 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF32B1065675 for ; Tue, 5 May 2009 11:37:05 +0000 (UTC) (envelope-from jruohone@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by mx1.freebsd.org (Postfix) with ESMTP id 56C538FC1F for ; Tue, 5 May 2009 11:37:04 +0000 (UTC) (envelope-from jruohone@gmail.com) Received: by ey-out-2122.google.com with SMTP id 9so1154571eyd.7 for ; Tue, 05 May 2009 04:37:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:received:date:from:to :subject:message-id:reply-to:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=1WwopmuqBtV06apia4w6l/4X+UW0k8Fs+UTnOy0TvSQ=; b=oEIo8+Ku56CtYddhRmnMdR+Vv5hA/jIMBkG3TbsGu5vqhq9TzSh8LjiEgMeGEXZy// kHQQ6o2XNsVy0NT7x9ijymI7rMkVEzNCnCJvZY4/yoa8rmOn+OkwZeqh1nKo7sB7S/C8 /gZEBEn0OEDfCzl7moGasI6IdOy1339CY650A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:subject:message-id:reply-to:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; b=tQzk7R0HXZmKkjqsHs+yQg4js/hHo2Oik8ORUL0Sj9Qn6Cd/hNLZsnkZ0SzwOJPRWA zfc6eWtt+4p/X2z9ePOlE9rZyhq3gNSCJXaWDcnqJNyTDesP9zrB3xVqRg0ChNAHE2+p KTwPJMZxQCjcsCoYQWLnrmN8LXw7zxODkhDl4= Received: by 10.216.30.19 with SMTP id j19mr2324866wea.46.1241521428847; Tue, 05 May 2009 04:03:48 -0700 (PDT) Received: from marx.bitnet (xdsl-83-145-204-27.nebulazone.fi [83.145.204.27]) by mx.google.com with ESMTPS id 28sm1402694eye.36.2009.05.05.04.03.48 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 05 May 2009 04:03:48 -0700 (PDT) Sender: a b Received: by marx.bitnet (Postfix, from userid 1000) id 1B46B1447B; Tue, 5 May 2009 14:03:46 +0300 (EEST) Date: Tue, 5 May 2009 14:03:46 +0300 From: Jukka Ruohonen To: freebsd-hackers@freebsd.org Message-ID: <20090505110346.GA1155@marx.bitnet> Mail-Followup-To: freebsd-hackers@freebsd.org References: <5da021490905010848q441781den54eefba85a69f342@mail.gmail.com> <1241518462.1533.1313800225@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1241518462.1533.1313800225@webmail.messagingengine.com> User-Agent: Mutt/1.5.19 (2009-01-05) Subject: Re: Cobalt Raq 550 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jruohonen@iki.fi List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 11:37:06 -0000 On 05.05.2009, Simon Dick wrote: > with them at my last job, I don't remember hearing about anyone who'd > managed to get anything except linux working on it though (though I'm > sure someone must have!) Perhaps somewhat off-topic, but: http://www.netbsd.org/ports/cobalt/ - Jukka. From owner-freebsd-hackers@FreeBSD.ORG Tue May 5 15:46:09 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0B8C106564A for ; Tue, 5 May 2009 15:46:09 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id D74C78FC13 for ; Tue, 5 May 2009 15:46:08 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA21631; Tue, 05 May 2009 18:46:06 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4A005F3D.7010606@icyb.net.ua> Date: Tue, 05 May 2009 18:46:05 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.21 (X11/20090406) MIME-Version: 1.0 To: Maxim Sobolev References: <49F4070C.2000108@gmx.de> <20090428121327.GA41168@freebsd.org> <49FA8F2D.5090708@gmx.de> <49FAE36D.9030109@FreeBSD.org> In-Reply-To: <49FAE36D.9030109@FreeBSD.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers Subject: Re: C99: Suggestions for style(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: Tue, 05 May 2009 15:46:10 -0000 on 01/05/2009 14:56 Maxim Sobolev said the following: > Christoph Mallon wrote: >> Roman Divacky schrieb: >>> I like the part about using as many variables as possible because >>> of documentation and performance enhancements. I tend to like >>> the other changes as well.. >> >> This is not about using as many variables as possible. The goal is to >> use as many variables as you have logically distinct entities in the >> function. I suppose, this is what you mean, but I want to clarify this >> point. > > Why don't just put "logically distinct entities" into separate functions > on their own? It's a good indicator that the re-factoring is due when > you reach this point. I think that you overreach. A very trivial example. An array and an index into the array are two sufficiently "logically distinct entities" [as to be different variables]. But they are sufficiently related to be used in the same function. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Tue May 5 15:50:26 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F8181065675 for ; Tue, 5 May 2009 15:50:26 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 895B58FC21 for ; Tue, 5 May 2009 15:50:25 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA21763; Tue, 05 May 2009 18:50:22 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4A00603D.8000204@icyb.net.ua> Date: Tue, 05 May 2009 18:50:21 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.21 (X11/20090406) MIME-Version: 1.0 To: Erik Trulsson References: <20090502163535.GA17027@owl.midgard.homeip.net> In-Reply-To: <20090502163535.GA17027@owl.midgard.homeip.net> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Definition of NULL 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, 05 May 2009 15:50:26 -0000 on 02/05/2009 19:35 Erik Trulsson said the following: > Is the use of C++ inside the kernel really supported? I don't think so, > but I could be wrong. First question is what did you mean by "supported"? :-) Fortunately, it almost does not need to be supported, it can simply be used (with some known limitations). -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Tue May 5 22:07:23 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 830321065672 for ; Tue, 5 May 2009 22:07:23 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from server.mypc.hu (server.mypc.hu [87.229.73.95]) by mx1.freebsd.org (Postfix) with ESMTP id 300C28FC19 for ; Tue, 5 May 2009 22:07:22 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by server.mypc.hu (Postfix) with ESMTP id 2FDB414D5130 for ; Wed, 6 May 2009 00:07:22 +0200 (CEST) X-Virus-Scanned: amavisd-new at t-hosting.hu Received: from server.mypc.hu ([127.0.0.1]) by localhost (server.mypc.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id rHgRU58HFk3A for ; Wed, 6 May 2009 00:07:21 +0200 (CEST) Received: from [192.168.1.105] (catv-80-98-231-64.catv.broadband.hu [80.98.231.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by server.mypc.hu (Postfix) with ESMTPSA id A345E14D5129 for ; Wed, 6 May 2009 00:07:21 +0200 (CEST) Message-ID: <4A00B897.809@FreeBSD.org> Date: Wed, 06 May 2009 00:07:19 +0200 From: Gabor Kovesdan User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <20090427183836.GA10793@zim.MIT.EDU> <49F5FE45.2090101@freebsd.org> <20090427193326.GA7654@britannica.bec.de> <20090427194904.GA11137@zim.MIT.EDU> <49F6C7A1.6070708@FreeBSD.org> <20090428122225.GA2862@britannica.bec.de> <24e9a86bf5995ba551db8f27aa204191.squirrel@webmail.kovesdan.org> <20090428180624.GA2223@britannica.bec.de> In-Reply-To: <20090428180624.GA2223@britannica.bec.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: SoC 2009: BSD-licensed libiconv in base system 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, 05 May 2009 22:07:23 -0000 Joerg Sonnenberger escribió: > > Unicode covers Korean. It just violates the "one logic character equals > one UCS-4 character" or however you want to put. More trivial example > can be obtained when looking at both your and my name. Diacrets have > historically been part of the character, but it is possible to use > combining characters in unicode for the cleaner description. > OK, I know that but that's other problem. You explicitly wrote that there were characters, which couldn't be represented un UCS-4, that was what I reacted on: > Everything can be represented as UCS-4 is a bad > assumption, but something Americans and Europeans naturally don't have > to care about. Cheers, -- Gabor Kovesdan FreeBSD Volunteer EMAIL: gabor@FreeBSD.org .:|:. gabor@kovesdan.org WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org From owner-freebsd-hackers@FreeBSD.ORG Wed May 6 10:57:35 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3564A106566B; Wed, 6 May 2009 10:57:35 +0000 (UTC) (envelope-from alexanderchuranov@gmail.com) Received: from mail-fx0-f168.google.com (mail-fx0-f168.google.com [209.85.220.168]) by mx1.freebsd.org (Postfix) with ESMTP id 7C7E68FC18; Wed, 6 May 2009 10:57:34 +0000 (UTC) (envelope-from alexanderchuranov@gmail.com) Received: by fxm12 with SMTP id 12so16399fxm.43 for ; Wed, 06 May 2009 03:57:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=TcR9eSm35crRM7D+s7SwfWHdEDT/vT3F74GS1ki9oN0=; b=msEQtbUAiXlU38PEXd8cEeG7A5JUBCxlovL/qLBAlZpxbtFpsoqDZ53JDyIx+jzwp1 vFSl5UTVRJhBsgIt/SF+SCT8cYFfJyggNJObpvyfrtNYdG2GbMHbOczEgpqOhUV3GZ5u pf6EpsQEttuA2F8/j8X6kLdb+bDElv5uN2/xQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=quCsTB8qQ02J6sy1lWjNeeVKJvwClhtANlEVcG8b+SW6Zxx9nnX65GRriOYP00NWAx sPMMTtNTbceDpwsRvSh3LXRnxqioDyp5WEBtAc2ztVDdrdne/JwsxYACQaT44A6p26z1 0L2jRXv3CiPJaitWNGJHrlFh94JxODuV9ep4Q= MIME-Version: 1.0 Received: by 10.204.60.72 with SMTP id o8mr1058678bkh.184.1241605731024; Wed, 06 May 2009 03:28:51 -0700 (PDT) In-Reply-To: <4A00B897.809@FreeBSD.org> References: <20090427183836.GA10793@zim.MIT.EDU> <49F5FE45.2090101@freebsd.org> <20090427193326.GA7654@britannica.bec.de> <20090427194904.GA11137@zim.MIT.EDU> <49F6C7A1.6070708@FreeBSD.org> <20090428122225.GA2862@britannica.bec.de> <24e9a86bf5995ba551db8f27aa204191.squirrel@webmail.kovesdan.org> <20090428180624.GA2223@britannica.bec.de> <4A00B897.809@FreeBSD.org> Date: Wed, 6 May 2009 14:28:51 +0400 Message-ID: <3cb459ed0905060328n4ad05d98xb5ba0c2e01d356e2@mail.gmail.com> From: Alexander Churanov To: Gabor Kovesdan Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: SoC 2009: BSD-licensed libiconv in base system 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, 06 May 2009 10:57:35 -0000 Gabor, Joerg, I am currently working on UTF-8 support in syscons and highly interested in making FreeBSD using UTF-8 out of box. There is my $0.02: 1) Why discuss UCS-4 at all? UTF-32 is alreay in place. SImple, standardized, fixed-width and stateless. 2) I'm against using wchar_t internally, because C language standard does not require that a wchar_t variable can hold an UTF-32 code point. 3) Please, give an example of character that does not fit into UCS-4. I'll check whether it fits into UTF-32. I expect that any character fits into a single UTF-32 code point. Sincerely, Alexander Churanov From owner-freebsd-hackers@FreeBSD.ORG Wed May 6 13:13:20 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F6EF1065674 for ; Wed, 6 May 2009 13:13:20 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp02.sth.basefarm.net (ch-smtp02.sth.basefarm.net [80.76.149.213]) by mx1.freebsd.org (Postfix) with ESMTP id 16BEE8FC14 for ; Wed, 6 May 2009 13:13:19 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-255-48-78.bredband.comhem.se ([83.255.48.78]:52868 helo=falcon.midgard.homeip.net) by ch-smtp02.sth.basefarm.net with esmtp (Exim 4.69) (envelope-from ) id 1M1gvz-0003Wy-85 for freebsd-hackers@freebsd.org; Wed, 06 May 2009 15:13:18 +0200 Received: (qmail 62829 invoked from network); 6 May 2009 15:13:12 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 6 May 2009 15:13:12 +0200 Received: (qmail 48745 invoked by uid 1001); 6 May 2009 15:13:12 +0200 Date: Wed, 6 May 2009 15:13:12 +0200 From: Erik Trulsson To: Alexander Churanov Message-ID: <20090506131312.GA48658@owl.midgard.homeip.net> References: <20090427183836.GA10793@zim.MIT.EDU> <49F5FE45.2090101@freebsd.org> <20090427193326.GA7654@britannica.bec.de> <20090427194904.GA11137@zim.MIT.EDU> <49F6C7A1.6070708@FreeBSD.org> <20090428122225.GA2862@britannica.bec.de> <24e9a86bf5995ba551db8f27aa204191.squirrel@webmail.kovesdan.org> <20090428180624.GA2223@britannica.bec.de> <4A00B897.809@FreeBSD.org> <3cb459ed0905060328n4ad05d98xb5ba0c2e01d356e2@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3cb459ed0905060328n4ad05d98xb5ba0c2e01d356e2@mail.gmail.com> User-Agent: Mutt/1.5.19 (2009-01-05) X-Originating-IP: 83.255.48.78 X-Scan-Result: No virus found in message 1M1gvz-0003Wy-85. X-Scan-Signature: ch-smtp02.sth.basefarm.net 1M1gvz-0003Wy-85 07c38897555fe142db9529f740b5ec76 Cc: freebsd-hackers@freebsd.org, Gabor Kovesdan Subject: Re: SoC 2009: BSD-licensed libiconv in base system 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, 06 May 2009 13:13:20 -0000 On Wed, May 06, 2009 at 02:28:51PM +0400, Alexander Churanov wrote: > Gabor, Joerg, > > I am currently working on UTF-8 support in syscons and highly > interested in making FreeBSD using UTF-8 out of box. > > There is my $0.02: > > 1) Why discuss UCS-4 at all? UTF-32 is alreay in place. SImple, > standardized, fixed-width and stateless. UCS-4 and UTF-32 are, for most purposes, just two different names for the same encoding. > 2) I'm against using wchar_t internally, because C language standard > does not require that a wchar_t variable can hold an UTF-32 code > point. The C standard has very few requirements on wchar_t. It is up to each implementation to decide how wchar_t is defined. There is nothing which prevents the FreeBSD project from deciding that on FreeBSD wchar_t is always 32 bits wide, which can then be relied upon in FreeBSD-specific code. It is not like somebody else will change the relevant include files without warning. > 3) Please, give an example of character that does not fit into UCS-4. > I'll check whether it fits into UTF-32. I expect that any character > fits into a single UTF-32 code point. > > Sincerely, > Alexander Churanov > _______________________________________________ > 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" -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-hackers@FreeBSD.ORG Wed May 6 13:20:02 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCDEE106566C; Wed, 6 May 2009 13:20:02 +0000 (UTC) (envelope-from alexanderchuranov@gmail.com) Received: from mail-fx0-f168.google.com (mail-fx0-f168.google.com [209.85.220.168]) by mx1.freebsd.org (Postfix) with ESMTP id 31C278FC17; Wed, 6 May 2009 13:20:01 +0000 (UTC) (envelope-from alexanderchuranov@gmail.com) Received: by fxm12 with SMTP id 12so99030fxm.43 for ; Wed, 06 May 2009 06:20:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=u9DSBod7bLp2zkL38I5/+CxRTE7xeiyEOWnE6/9apOg=; b=R4uY5xfMQ26sDPFdW08T1VCZtbvHNlorZ9Ks1sKIu2DEJQ34qUnmw8SP0SI9L4hJJp W/kMVWG2BFyRQ2BXWAlaUmEkqr0Fh+Cijak/MHDb+FLKT8XABDGvxSlixUTI7RtLYc8+ IGb+K4flpF0jyLhg4OteWtxxoCdGummxOwtYY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=FBP5LRzxF0vT9BelNLc8S93YqzqW8ImnrO9bRj2qJZj+m+6zOTbiSaA2RxCe6bz+hb WQv+9SegN2SfK95znoWjhDnASjuXcANTk+MMP1Ob2ckXi5WJcpNhELPwQ9tKX/A5NFYi Eq+zDFNYvb6ZYo5EA6mceBxKodh/yujefYGBk= MIME-Version: 1.0 Received: by 10.204.118.66 with SMTP id u2mr1219917bkq.132.1241616000922; Wed, 06 May 2009 06:20:00 -0700 (PDT) In-Reply-To: <20090506131312.GA48658@owl.midgard.homeip.net> References: <20090427183836.GA10793@zim.MIT.EDU> <20090427193326.GA7654@britannica.bec.de> <20090427194904.GA11137@zim.MIT.EDU> <49F6C7A1.6070708@FreeBSD.org> <20090428122225.GA2862@britannica.bec.de> <24e9a86bf5995ba551db8f27aa204191.squirrel@webmail.kovesdan.org> <20090428180624.GA2223@britannica.bec.de> <4A00B897.809@FreeBSD.org> <3cb459ed0905060328n4ad05d98xb5ba0c2e01d356e2@mail.gmail.com> <20090506131312.GA48658@owl.midgard.homeip.net> Date: Wed, 6 May 2009 17:20:00 +0400 Message-ID: <3cb459ed0905060620x78b98bcak5cea5570ee3120a9@mail.gmail.com> From: Alexander Churanov To: Erik Trulsson Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, Gabor Kovesdan Subject: Re: SoC 2009: BSD-licensed libiconv in base system 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, 06 May 2009 13:20:03 -0000 2009/5/6 Erik Trulsson : > The C standard has very few requirements on wchar_t. =A0It is up to each > implementation to decide how wchar_t is defined. > There is nothing which prevents the FreeBSD project from deciding > that on FreeBSD wchar_t is always 32 bits wide, which can then be relied > upon in FreeBSD-specific code. =A0It is not like somebody else will chang= e > the relevant include files without warning. Ah, then wchar_t is for internal usage? Then it's OK. Alexander Churanov From owner-freebsd-hackers@FreeBSD.ORG Wed May 6 15:21:43 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B5EC1065672 for ; Wed, 6 May 2009 15:21:43 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by mx1.freebsd.org (Postfix) with ESMTP id B4F268FC21 for ; Wed, 6 May 2009 15:21:42 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: by ey-out-2122.google.com with SMTP id 9so58521eyd.7 for ; Wed, 06 May 2009 08:21:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:received:date:from:to:cc :subject:message-id:references:mime-version:content-type :content-disposition:in-reply-to; bh=rJS67wkEH3kGh69YhV64UOX2gwjwG7FKi28FYoswJl0=; b=QWV9SZUDbV0sdVsnevG2SV2yu1xr2/enUMsHJ5UMjjqYdOpbNwVMhsqwzXJXcw+1RP 6/UIF9PRq5Pi+Ls2rvJEj1wbffE+VOc3Xdjp0kSfdKV8KEbESIo7n7VrG1Z5ZgOEo5t2 o6TurjOiR4sU3fY6zpQdiK5DoVJ5yZ9WvVYzc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to; b=er/zH9ps8g/21tUsEQOJXQurkBGaMuHZBwQlyvMN3Ye+pfMaKIHyv/eUCGINIJxg2b NQOiIpOalHFB/Di3Lk97FFIr0/sJd9mc/2rfzQQrYP+Z2+q+GjdhrVcg9Bwi8S3NAKTw qQ7+iDOE/2MxpNny54MotZgEcW3fy3Sh4NdRY= Received: by 10.210.88.3 with SMTP id l3mr6126860ebb.55.1241623301680; Wed, 06 May 2009 08:21:41 -0700 (PDT) Received: from logik.internal.network (81-86-41-187.dsl.pipex.com [81.86.41.187]) by mx.google.com with ESMTPS id 24sm11268875ewy.1.2009.05.06.08.21.41 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 06 May 2009 08:21:41 -0700 (PDT) Received: by logik.internal.network (Postfix, from userid 11001) id F21025C31; Wed, 6 May 2009 15:21:39 +0000 (UTC) Date: Wed, 6 May 2009 16:21:39 +0100 From: xorquewasp@googlemail.com To: Daniel Eischen Message-ID: <20090506152139.GB69468@logik.internal.network> References: <20090504182714.GA52480@logik.internal.network> <20090504185644.GA16315@logik.internal.network> <20090505005128.GA4519@logik.internal.network> <20090505022151.GA32477@logik.internal.network> <20090506140325.GA69468@logik.internal.network> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-hackers@freebsd.org Subject: Re: bootstrapping gnat GCC on amd64 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, 06 May 2009 15:21:44 -0000 On 2009-05-06 10:57:25, Daniel Eischen wrote: > > Back in the day when I did it, it was with gcc-2.7.x or > gcc-2.8.x I believe. The cross build process with gnat > was a little different. I couldn't do a normal gnat build, > which did a bootstrap and then rebuilt the compiler again > using the bootstrap. I believe I had to manually build > bootstrap, gnatlib-cross, and gnattools-cross or targets > named something like that. I don't even think "install" > worked - I think I had to manually install the cross. > > This does sound vaguely familiar though. I may have > just rebuilt the target->target GNAT with the cross > GNAT, then whenever the build process stopped with > gnatmake errors, I would manually build whatever target > it stopped at with the cross gnatbind and gnatlink. > > I don't even know if gnatmake is required to rebuild > the target->target GNAT, all the dependencies should > be listed in the Makefiles, so gcc should get called > directly as opposed through gnatmake. So try going > forward with rebuilding that x86_64 native GNAT and > see what happens. This is really what your goal is, > having the i386->x86_64 cross is nice, but not really > essential. > > Hmm, I do know that building gnat as a cross > does work though, since we have and use GNAT for > sparc-solaris hosted ppc-vxworks cross compilers. > And gnatmake works just fine as a cross. Thanks for the notes. This is an example of one of the build failures when compiling the x86_64 native GNAT: mkdir -p ada/bldtools/nmake_b rm -f ada/bldtools/nmake_b/sinfo.ads ada/bldtools/nmake_b/nmake.adt ada/bldtools/nmake_b/xnmake.adb ada/bldtools/nmake_b/xutil.ads ada/bldtools/nmake_b/xutil.adb cp -p ../../gcc-4.4.0/gcc/ada/sinfo.ads ../../gcc-4.4.0/gcc/ada/nmake.adt ../../gcc-4.4.0/gcc/ada/xnmake.adb ../../gcc-4.4.0/gcc/ada/xutil.ads ../../gcc-4.4.0/gcc/ada/xutil.adb ada/bldtools/nmake_b (cd ada/bldtools/nmake_b && x86_64-unknown-freebsd7.2-gnatmake -q xnmake && ./xnmake -b ../../nmake.adb ) x86_64-unknown-freebsd7.2-gnatmake: "xnmake.ali" incompatible ALI file, please recompile x86_64-unknown-freebsd7.2-gnatmake: "xnmake.adb" compilation error gmake[2]: *** [ada/nmake.adb] Error 4 gmake[2]: Leaving directory `/root/gcc-4.4.0-obj/gcc' gmake[1]: *** [all-gcc] Error 2 gmake[1]: Leaving directory `/root/gcc-4.4.0-obj' gmake: *** [all] Error 2 The Makefiles are pretty twisted and hard to comprehend. I'll try your suggestion, stepping through each target and ideally try to get the whole process down to shell script form. More news to follow... xw From owner-freebsd-hackers@FreeBSD.ORG Wed May 6 16:22:33 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07692106564A for ; Wed, 6 May 2009 16:22:33 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from www.sonnenberger.org (www.ostsee-abc.de [62.206.222.50]) by mx1.freebsd.org (Postfix) with ESMTP id AFF078FC1F for ; Wed, 6 May 2009 16:22:32 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (www.sonnenberger.org [192.168.1.10]) by www.sonnenberger.org (Postfix) with ESMTP id 158C36676F for ; Wed, 6 May 2009 18:22:29 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1000) id 14EC91BDD74; Wed, 6 May 2009 18:22:47 +0200 (CEST) Date: Wed, 6 May 2009 18:22:47 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Message-ID: <20090506162247.GA23015@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20090427183836.GA10793@zim.MIT.EDU> <49F5FE45.2090101@freebsd.org> <20090427193326.GA7654@britannica.bec.de> <20090427194904.GA11137@zim.MIT.EDU> <49F6C7A1.6070708@FreeBSD.org> <20090428122225.GA2862@britannica.bec.de> <24e9a86bf5995ba551db8f27aa204191.squirrel@webmail.kovesdan.org> <20090428180624.GA2223@britannica.bec.de> <4A00B897.809@FreeBSD.org> <3cb459ed0905060328n4ad05d98xb5ba0c2e01d356e2@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3cb459ed0905060328n4ad05d98xb5ba0c2e01d356e2@mail.gmail.com> User-Agent: Mutt/1.5.19 (2009-01-05) Subject: Re: SoC 2009: BSD-licensed libiconv in base system 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, 06 May 2009 16:22:33 -0000 On Wed, May 06, 2009 at 02:28:51PM +0400, Alexander Churanov wrote: > 1) Why discuss UCS-4 at all? UTF-32 is alreay in place. SImple, > standardized, fixed-width and stateless. Which part of "combining characters" is stateless? Sure, you can ignore that in some/many applications, but it still exists. UCS-4 and UTF-32 are identical, so discussing one is enough. > 2) I'm against using wchar_t internally, because C language standard > does not require that a wchar_t variable can hold an UTF-32 code > point. See my original point of that locale independent wchar_t might be useful, but creates problems. If the OS supports full Unicode 3+ locales, it will have to be able to fit any UCS-4 code point into wchar_t. Joerg From owner-freebsd-hackers@FreeBSD.ORG Wed May 6 16:42:25 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B967106566B for ; Wed, 6 May 2009 16:42:25 +0000 (UTC) (envelope-from simond@irrelevant.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 715D68FC14 for ; Wed, 6 May 2009 16:42:25 +0000 (UTC) (envelope-from simond@irrelevant.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id C055B33AF8A; Wed, 6 May 2009 12:42:24 -0400 (EDT) Received: from web5.messagingengine.com ([10.202.2.214]) by compute2.internal (MEProxy); Wed, 06 May 2009 12:42:24 -0400 Received: by web5.messagingengine.com (Postfix, from userid 99) id 9C6D662419; Wed, 6 May 2009 12:42:24 -0400 (EDT) Message-Id: <1241628144.28461.1314123239@webmail.messagingengine.com> X-Sasl-Enc: 2ETALoVmokL9kCklYHNwJvkciciXKwueoIwJHDwKIpz6 1241628144 From: "Simon Dick" To: jruohonen@iki.fi, freebsd-hackers@freebsd.org Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface References: <5da021490905010848q441781den54eefba85a69f342@mail.gmail.com> <1241518462.1533.1313800225@webmail.messagingengine.com> <20090505110346.GA1155@marx.bitnet> In-Reply-To: <20090505110346.GA1155@marx.bitnet> Date: Wed, 06 May 2009 17:42:24 +0100 Cc: Subject: Re: Cobalt Raq 550 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, 06 May 2009 16:42:25 -0000 On Tue, 5 May 2009 14:03:46 +0300, "Jukka Ruohonen" said: > On 05.05.2009, Simon Dick wrote: > > with them at my last job, I don't remember hearing about anyone who'd > > managed to get anything except linux working on it though (though I'm > > sure someone must have!) > > Perhaps somewhat off-topic, but: > > http://www.netbsd.org/ports/cobalt/ Unfortunately that's just the older MIPS based ones, the RaQ4 and 550 were x86 based but with a very weird BIOS (I know it'd be possible to install onto them, I just don't think anyone's thought it worthwhile yet :) ) -- Simon Dick simond@irrelevant.org From owner-freebsd-hackers@FreeBSD.ORG Thu May 7 09:55:34 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76BC4106564A for ; Thu, 7 May 2009 09:55:34 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from hercules.mthelicon.com (hercules.mthelicon.com [66.90.118.40]) by mx1.freebsd.org (Postfix) with ESMTP id 2FCFC8FC1B for ; Thu, 7 May 2009 09:55:33 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from PegaPegII (hydra.fletchermoorland.co.uk [78.33.209.59]) (authenticated bits=0) by hercules.mthelicon.com (8.14.3/8.14.3) with ESMTP id n479IuMs001486 for ; Thu, 7 May 2009 09:18:57 GMT (envelope-from ken@mthelicon.com) Message-ID: <6CBB129E81A54104BCFD00735C71B5F4@PegaPegII> From: "Pegasus Mc Cleaft" To: Date: Thu, 7 May 2009 10:18:55 +0100 Organization: Feathers MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6001.18000 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049 X-Antivirus: avast! (VPS 090506-0, 06/05/2009), Outbound message X-Antivirus-Status: Clean Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: DAD Detected duplicate ipv6 address - 7.2 Stable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pegasus Mc Cleaft List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 09:55:35 -0000 Hi Hackers,=20 I was wondering if someone could give me some advice. I just updated = one of my servers from 7.2-pre to 7.2-stable (07/05/2009) and lost my = IPv6 connectivity. The machine has been given a static IPv6 address and = ND is not used (I set the address in the rc.conf file). On reboot, I get = messages like this in the dmesg: vr0: DAD detected duplicate IPv6 address 2001:49f0:2023::2: NS = in/out=3D3/1, NA in=3D0 vr0: DAD complete for 2001:49f0:2023::2 - duplicate found vr0: manual intervention required vr0: DAD detected duplicate IPv6 address fe80:1::213:8fff:fe5c:1a5f: NS = in/out=3D3/1, NA in=3D0 vr0: DAD complete for fe80:1::213:8fff:fe5c:1a5f - duplicate found vr0: manual intervention required vr0: possible hardware address duplication detected, disable IPv6 hercules$ ifconfig vr0: flags=3D8843 metric 0 mtu = 1500 options=3D2808 ether 00:13:8f:5c:1a:5f inet6 fe80::213:8fff:fe5c:1a5f%vr0 prefixlen 64 duplicated = scopeid 0x1=20 inet 66.90.118.40 netmask 0xffffff00 broadcast 66.90.118.255 inet6 2001:49f0:2023::2 prefixlen 64 duplicated=20 media: Ethernet autoselect (100baseTX ) status: active plip0: flags=3D108810 metric 0 = mtu 1500 lo0: flags=3D8049 metric 0 mtu 16384 inet6 ::1 prefixlen 128=20 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3=20 inet 127.0.0.1 netmask 0xff000000=20 This fault has only shown up since the upgrade and I am at a loss for = what to try to do to fix this or debug. Any advice would be appreciated. = Peg From owner-freebsd-hackers@FreeBSD.ORG Fri May 8 03:07:47 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE3A61065672 for ; Fri, 8 May 2009 03:07:47 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 92CB28FC25 for ; Fri, 8 May 2009 03:07:47 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: (from root@localhost) by kientzle.com (8.14.3/8.14.3) id n4837loT010654 for freebsd-hackers@freebsd.org; Thu, 7 May 2009 20:07:47 -0700 (PDT) (envelope-from kientzle@freebsd.org) Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2]) by kientzle.com with SMTP id 2ni49tfrgu5h5pr23if86uhb62; for freebsd-hackers@freebsd.org; Thu, 07 May 2009 20:07:46 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <4A03A202.2050101@freebsd.org> Date: Thu, 07 May 2009 20:07:46 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.21) Gecko/20090409 SeaMonkey/1.1.15 MIME-Version: 1.0 To: "'freebsd-hackers@freebsd.org'" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: fdescfs brokenness 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, 08 May 2009 03:07:48 -0000 Colin Percival recently pointed out some issues with tar and fdescfs. Part of the problem here is tar; I need to rethink some of the traversal logic. But fdescfs is really wonky: * This is a nit, but: ls /dev/fd/18 should not return EBADF; it should return ENOENT, just like any other reference to a non-existent filename. (Just because a filename reflects a file descriptor does not mean it is a file descriptor.) * The fairly routine recursive directory walker below gets hung in fdescfs. It appears that the two opendir() invocations active at the same time interfere with each other. * A similar chdir()-based version of the directory walker below breaks badly; you can chdir() into a directory under /dev/fd, but you can't chdir("..") to get back out of it. (This is the particular problem that tar is running afoul of.) * Running "find /dev/fd" generates bogus ENOENT errors because you can opendir() a directory inside of /dev/fd, and read the entries, but you can't access those entries because path searches don't work through fdescfs. I think the right solution here is to add a VOP_ACCESS handler to fdescfs that bars all access to directory nodes under /dev/fd. Basically, if your program has a directory open, that should be reflected as a directory node that you can't do anything with. The current implementation allows you to chdir(), opendir(), etc, those directory nodes, but the machinery to fully support those operations is missing so they just screw things up. I have a candidate vop_access handler partly written, but I'm a little new to filesystem work, so it will take me a little while to satisfy myself that it works. /* * Non-chdir directory walker. */ #include #include #include #include #include #include #include #include #include static char curpath[512]; void visit(char *f, int depth) { DIR *d; struct dirent *dp; size_t l = strlen(curpath); strcat(curpath, "/"); strcat(curpath, f); printf("%3d: %s\n", depth, curpath); d = opendir(curpath); if (d != NULL) { while ((dp = readdir(d)) != NULL) { if (dp->d_name[0] == '.') continue; visit(dp->d_name, depth + 1); } closedir(d); } curpath[l] = '\0'; } int main(int argc, char **argv) { visit("/dev/fd", 0); exit(0); } From owner-freebsd-hackers@FreeBSD.ORG Fri May 8 05:28:40 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B3AD106566B for ; Fri, 8 May 2009 05:28:40 +0000 (UTC) (envelope-from buganini@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id F15E58FC22 for ; Fri, 8 May 2009 05:28:39 +0000 (UTC) (envelope-from buganini@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so728883ywe.13 for ; Thu, 07 May 2009 22:28:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=0yQ28qmXTsJgl9kobptOINsnXo4oVy7wb1Mr9sqP84k=; b=vTgtlNoWG542Ccs/JvNlJnkmUwy3L3+6LYJLf58GQAqZAVWhj/mBiq0y+NYqCtbQ/y QXgY9PPlCvXOTKH/98MEUgMQQ0b/zackODk+ujU4cPamlf8NVOSQj03hFV8JXmuSZ7r0 hFO0AexT+1B5tmte//YUynqOkiauEZsTLo4jc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=A1WyFczF7Rp3TdDfjTPtqOlqA7jTalnhKA5zBRvtOZGNICqZxxGS/J6eNsqHGA5R86 qPa/z3n+347rHrqYg35NRcTieECXAn9mFQzPolrJw45WOIZsnuEBysndSOlyfEvKkuxQ NPn0/U93QLthGjX2JZw0uE1ji/lcRXZZspZnQ= MIME-Version: 1.0 Received: by 10.100.47.10 with SMTP id u10mr7493313anu.17.1241758877442; Thu, 07 May 2009 22:01:17 -0700 (PDT) In-Reply-To: <20090506162247.GA23015@britannica.bec.de> References: <20090427183836.GA10793@zim.MIT.EDU> <20090427193326.GA7654@britannica.bec.de> <20090427194904.GA11137@zim.MIT.EDU> <49F6C7A1.6070708@FreeBSD.org> <20090428122225.GA2862@britannica.bec.de> <24e9a86bf5995ba551db8f27aa204191.squirrel@webmail.kovesdan.org> <20090428180624.GA2223@britannica.bec.de> <4A00B897.809@FreeBSD.org> <3cb459ed0905060328n4ad05d98xb5ba0c2e01d356e2@mail.gmail.com> <20090506162247.GA23015@britannica.bec.de> Date: Fri, 8 May 2009 13:01:17 +0800 Message-ID: From: Buganini To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: SoC 2009: BSD-licensed libiconv in base system 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, 08 May 2009 05:28:41 -0000 Hi all, I'm also working on a BSDL charset converter library: http://github.com/buganini/bsdconv/ It's *NOT* compatible with iconv. It try to provide more function, including fallback charset, intermediary mapping. Intermediary mapping could be used to do conversion between Traditional/Simplified Chinese, CRLF/CR/LF, etc. Currently iconv can only convert Chinese from/to big5/gb2312, it can't convert Chinese in unicode data. Unicode is prefixed with 0x01 in internal encoding. Therefore charsets like CNS11643, which has symbols not in UNICODE can use other prefix. It's in early developement, supporting few charset by now. Buganini From owner-freebsd-hackers@FreeBSD.ORG Fri May 8 08:25:50 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3635106564A for ; Fri, 8 May 2009 08:25:50 +0000 (UTC) (envelope-from kheuer2@gwdg.de) Received: from tmailer.gwdg.de (tmailer.gwdg.de [134.76.10.23]) by mx1.freebsd.org (Postfix) with ESMTP id A4DA88FC08 for ; Fri, 8 May 2009 08:25:50 +0000 (UTC) (envelope-from kheuer2@gwdg.de) Received: from gwdu60.gwdg.de ([134.76.8.60]) by mailer.gwdg.de with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1M2LOv-0007ah-0y for freebsd-hackers@freebsd.org; Fri, 08 May 2009 10:25:49 +0200 Date: Fri, 8 May 2009 10:25:48 +0200 (CEST) From: Konrad Heuer To: freebsd-hackers@freebsd.org Message-ID: <20090508101555.J47014@gwdu60.gwdg.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Subject: How to invalidate NFS read cache? 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, 08 May 2009 08:25:51 -0000 Hello, sporadically, I observe a strange but serious problem in our large NFS environment. NFS servers are Linux and OS X with StorNext/Xsan cluster filesystems, NFS clients Linux and FreeBSD. NFS client A changes a file, but nfs client B (running on FreeBSD) does still see the old version. On the NFS server itself, everything looks fine. Afaik the FreeBSD kernel invalidates the NFS read cache if file modification time on the server changed which should happen here but doesn't. Can I force FreeBSD (e.g. by sysctl setting) to read file buffers again unconditionally after vfs.nfs.access_cache_timeout seconds have passed? Best regards Konrad Heuer GWDG, Am Fassberg, 37077 Goettingen, Germany, kheuer2@gwdg.de From owner-freebsd-hackers@FreeBSD.ORG Fri May 8 09:11:02 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 644A5106568A for ; Fri, 8 May 2009 09:11:02 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 21FBA8FC1E for ; Fri, 8 May 2009 09:11:01 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1M2M6e-000PRs-GA for freebsd-hackers@freebsd.org; Fri, 08 May 2009 12:11:00 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 May 2009 12:11:00 +0300 From: Danny Braniss Message-ID: Subject: undetected umass device 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, 08 May 2009 09:11:02 -0000 Hi, this is a: USB to Parallel-ATA bridge(0x0c05), Sunplus Technology Inc.(0x04fc) or in english, a nifty dongle that can be connected to ata/sata disk, but umass fails to detected it fully, and detaches it. any hints? quircks? thanks, danny From owner-freebsd-hackers@FreeBSD.ORG Fri May 8 11:54:19 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69FF31065674 for ; Fri, 8 May 2009 11:54:19 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id 013928FC25 for ; Fri, 8 May 2009 11:54:18 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=6r6v4UIe0JpOdFllLVMA:9 a=-nYwf-_hil0cRiVPMVYT2rkBWIYA:4 Received: from [81.191.55.181] (account mc467741@c2i.net HELO [10.36.2.183]) by mailfe07.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1236137340; Fri, 08 May 2009 12:54:13 +0200 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Fri, 8 May 2009 12:56:46 +0200 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905081256.47724.hselasky@c2i.net> Cc: Subject: Re: undetected umass device 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, 08 May 2009 11:54:19 -0000 On Friday 08 May 2009, Danny Braniss wrote: > Hi, > this is a: > USB to Parallel-ATA bridge(0x0c05), Sunplus Technology Inc.(0x04fc) > or in english, a nifty dongle that can be connected to ata/sata disk, but > umass fails to detected it fully, and detaches it. > > any hints? quircks? > thanks, > danny > Can you get dmesg and the USB descriptors of your device? --HPS From owner-freebsd-hackers@FreeBSD.ORG Fri May 8 14:05:04 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B8651065674 for ; Fri, 8 May 2009 14:05:04 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 0383F8FC25 for ; Fri, 8 May 2009 14:05:03 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1M2QhC-0002OH-Rt; Fri, 08 May 2009 17:05:02 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Hans Petter Selasky In-reply-to: <200905081256.47724.hselasky@c2i.net> References: <200905081256.47724.hselasky@c2i.net> Comments: In-reply-to Hans Petter Selasky message dated "Fri, 08 May 2009 12:56:46 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 May 2009 17:05:02 +0300 From: Danny Braniss Message-ID: Cc: freebsd-hackers@freebsd.org Subject: Re: undetected umass device 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, 08 May 2009 14:05:04 -0000 > On Friday 08 May 2009, Danny Braniss wrote: > > Hi, > > this is a: > > USB to Parallel-ATA bridge(0x0c05), Sunplus Technology Inc.(0x04fc) > > or in english, a nifty dongle that can be connected to ata/sata disk, but > > umass fails to detected it fully, and detaches it. > > > > any hints? quircks? > > thanks, > > danny > > > > Can you get dmesg and the USB descriptors of your device? > sure, but I guess I forgot to mention, this is with 7.2-stable. port 2 addr 3: high speed, self powered, config 1, USB to Parallel-ATA bridge(0x0c05), Sunplus Technology Inc.(0x04fc), rev 10.03 umass1: on uhub7 umass1: SCSI over Bulk-Only; quirks = 0x0000 umass1: Max Lun is 0 umass1:2:-1:-1:XPT_PATH_INQ:. umass1:2:1:-1: Attached to scbus2 umass1: Attach finished scbus2: scanning for umass1:2:1:-1 umass1:2:1:-1:XPT_PATH_INQ:. umass1:2:0:0:XPT_PATH_INQ:. umass1:2:0:0:XPT_PATH_INQ:. umass1:2:0:0:XPT_SET_TRAN_SETTINGS:. umass1:2:0:0:XPT_PATH_INQ:. umass1:2:0:0:XPT_PATH_INQ:. umass1:2:0:0:XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/36b data/18b sense umass1: CBW 1: cmd = 6b (0x120000002400), data = 36b, dir = in umass1: at uhub7 port 2 (addr 3) disconnected umass1: detached umass1: Handling BBB state 2 (BBB CBW), xfer=0xffffff00014c8c00, CANCELLED xpt0: Rescan succeeded umass1: detached cheers, danny From owner-freebsd-hackers@FreeBSD.ORG Fri May 8 14:27:21 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 927BD106566B for ; Fri, 8 May 2009 14:27:21 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 4FBEF8FC14 for ; Fri, 8 May 2009 14:27:21 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1M2R2m-0002Z4-9P for freebsd-hackers@freebsd.org; Fri, 08 May 2009 17:27:20 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 May 2009 17:27:20 +0300 From: Danny Braniss Message-ID: Subject: fputsock()/fgetsock() replacement 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, 08 May 2009 14:27:21 -0000 hi, Since the comment in the kernel is: 'Note: fputsock() is deprecated, see comment for fgetsock().' I'm looking for a replacement, on the other hand, this quote: deprecated Said of a program or feature that is considered obsolescent and in the process of being phased out, usually in favour of a specified replacement. Deprecated features can, unfortunately, linger on for many years. This term appears with distressing frequency in standards documents when the committees writing the documents realise that large amounts of extant (and presumably happily working) code depend on the feature(s) that have passed out of favour. See also {dusty deck}. [{Jargon File}] (1995-04-19) got me wondering if I should hurry. cheers, danny From owner-freebsd-hackers@FreeBSD.ORG Fri May 8 17:24:03 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4FF4106566B for ; Fri, 8 May 2009 17:24:03 +0000 (UTC) (envelope-from brampton@gmail.com) Received: from mail-bw0-f165.google.com (mail-bw0-f165.google.com [209.85.218.165]) by mx1.freebsd.org (Postfix) with ESMTP id 5FDED8FC18 for ; Fri, 8 May 2009 17:24:03 +0000 (UTC) (envelope-from brampton@gmail.com) Received: by bwz9 with SMTP id 9so1490343bwz.43 for ; Fri, 08 May 2009 10:24:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Pk7xbEe6XP8VDOgkzx/JmLKy3JyD3qfWpxU2Fsibe94=; b=Ul8Bs3L0dBzqadrVFOXOizJ0RFUX+f3t5tQVeg5qb6UTehFHyOiNi8ytnMGnda6EaC tMRAYc++TAKRsZVUkIHqltIi6JgLmvsLv/BjXqbDLvZgzD4cGPwfAXvyMXM8bsNJCKKO PpgFV92F7+1t3rwznKgKMS6ouIq+HxjN8lq8c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=FXAUt/0kZRJmtNZDQXKV7J9vh3CPyG9JzPXCx29swgfcscBZA8SvAf+lcEVUhcHWEq b7OevQ2r51kV8U2iaIGmI3wnxCytPRbxX09O6bhZbCdiegAThDaGZKlTasl7yCkBRB8a iET+ifn7TPWqz/Rz83L2Bw29jb3Ozb/Ar1dzM= MIME-Version: 1.0 Sender: brampton@gmail.com Received: by 10.223.122.15 with SMTP id j15mr2335538far.10.1241803442098; Fri, 08 May 2009 10:24:02 -0700 (PDT) Date: Fri, 8 May 2009 18:24:01 +0100 X-Google-Sender-Auth: b374440d6b8016dc Message-ID: From: Andrew Brampton To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: kthreads and sched_relinquish 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, 08 May 2009 17:24:04 -0000 Hi, I'm writing a FreeBSD kernel module and I think I really misunderstand something. My module spawns a thread, which should be running while the module is loaded. The thread does some work and then should yield for other threads. However, if there are no other threads waiting, then I would like to continue to do more work. The problem is that I am getting weird deadlocks so I wrote a simple test app to ask why this doesn't work: ------------------------ #include #include #include #include #include #include #include #include #include static void test_thread(void *blah) { unsigned int i = 100000000; /* Limit the number of iterations */ printf("Test Thread Started\n"); while (i > 0) { sched_relinquish(curthread); i--; } printf("Test Thread Exited\n"); kthread_exit(0); } /* The function called at load/unload. */ static int event_handler(struct module *module, int event, void *arg) { int e = 0; /* Error, 0 for normal return status */ switch (event) { case MOD_LOAD: printf("Test Module Loaded\n"); kthread_create(test_thread, NULL, NULL, 0, 0, "test"); break; case MOD_UNLOAD: printf("Test Module Unloaded\n"); break; default: e = EOPNOTSUPP; /* Error, Operation Not Supported */ } return e; } /* The second argument of DECLARE_MODULE. */ static moduledata_t test_conf = { "test_mod", /* module name */ event_handler, /* event handler */ NULL /* extra data */ }; DECLARE_MODULE(test_mod, test_conf, SI_SUB_DRIVERS, SI_ORDER_MIDDLE); ---------------------------- While my thread is running the rest of the system is unresponsive. The thread should sched_relinquish() every time round the loop, and from my understanding that should yield to allow other threads to run, for example the thread which executes my shell (bash). I suspect my thread is yielding and getting instantly rescheduled. I noticed that poll_idle() in sys/kern_poll.c does something similar to me, but they first lower their priority. This however has not worked for me, since my more complex module interacts with higher priority threads and ends up deadlocking. So I just want to ask, Why does this example code lock the system? Am I using sched_relinquish correctly? Or should I be doing something else? I did try using tsleep(...,1), but I don't want my thread sleeping if there are no other threads waiting. I would also be grateful if people could point me at other examples in the kernel where something like this is done. I have looked in quite a few places, but I can't see why my simple app is wrong. thanks Andrew From owner-freebsd-hackers@FreeBSD.ORG Fri May 8 18:30:34 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A2D7106566B for ; Fri, 8 May 2009 18:30:34 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-bw0-f165.google.com (mail-bw0-f165.google.com [209.85.218.165]) by mx1.freebsd.org (Postfix) with ESMTP id E6B9E8FC0A for ; Fri, 8 May 2009 18:30:33 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by bwz9 with SMTP id 9so1520614bwz.43 for ; Fri, 08 May 2009 11:30:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=255EDUDulDNo0i+WY5mpZWPIRnMGTGcVqreAjwy1pGY=; b=CsD/oA51yoNKk4kn7tNFyxfzZprQ+kmfptA3Duuyjb5C26fohSyeVbJfPPhRYKrtFH lkbHoDULp17AjQz/rQox0fxAD149VyMAXjtjwQ0ZgQeL5LdLkewNe5l75i2oj6FHYeeI K2zx9kZweWswkFAvc/0o0mnI8jTrNIifot/jg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=WSaovo/QGjJMLyjJ4LsCP868gV6ZubwtpYSxu3T+TSAav7OBe2igw30azqoQhxQn+1 0PkLAPMOdALB6IJ478coEcknoylQXy/KGZy/Uy25kU2rNlM/pCXKCpWAK7Cn567l6Ks0 UCyahLOkS//UXHA48VbP9p0yFLwSbFepVyZQY= MIME-Version: 1.0 Received: by 10.239.135.208 with SMTP id e16mr229091hbe.37.1241805557211; Fri, 08 May 2009 10:59:17 -0700 (PDT) In-Reply-To: References: Date: Fri, 8 May 2009 13:59:17 -0400 Message-ID: From: Ryan Stone To: Andrew Brampton Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: kthreads and sched_relinquish 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, 08 May 2009 18:30:34 -0000 Your kernel thread likely has a higher priority than userspace threads. Ryan Stone From owner-freebsd-hackers@FreeBSD.ORG Fri May 8 20:12:13 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CC2E106564A; Fri, 8 May 2009 20:12:13 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id F3E078FC13; Fri, 8 May 2009 20:12:12 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1M2WQU-000Kve-8y; Fri, 08 May 2009 23:12:10 +0300 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n48KC3Om094384 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 May 2009 23:12:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n48KC3oD033392; Fri, 8 May 2009 23:12:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n48KC3dU033391; Fri, 8 May 2009 23:12:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 8 May 2009 23:12:03 +0300 From: Kostik Belousov To: Tim Kientzle Message-ID: <20090508201203.GJ1948@deviant.kiev.zoral.com.ua> References: <4A03A202.2050101@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/SgVJVxFudH2R+XP" Content-Disposition: inline In-Reply-To: <4A03A202.2050101@freebsd.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1M2WQU-000Kve-8y ca587a4264363c91efc85cdea80c31f9 X-Terabit: YES Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: fdescfs brokenness 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, 08 May 2009 20:12:13 -0000 --/SgVJVxFudH2R+XP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 07, 2009 at 08:07:46PM -0700, Tim Kientzle wrote: > Colin Percival recently pointed out some issues > with tar and fdescfs. Part of the problem > here is tar; I need to rethink some of the > traversal logic. >=20 > But fdescfs is really wonky: >=20 > * This is a nit, but: ls /dev/fd/18 should not > return EBADF; it should return ENOENT, just > like any other reference to a non-existent filename. > (Just because a filename reflects a file descriptor > does not mean it is a file descriptor.) This is a traditional behaviour for fdescfs. According to man page, open("dev/fd/N") shall be equivalent to fcntl(N, F_DUPFD, 0). Solaris behaviour is the same. >=20 > * The fairly routine recursive directory walker > below gets hung in fdescfs. It appears that > the two opendir() invocations active at the > same time interfere with each other. What you mean by "gets hung" ? In my limited testing, it works. Opendir creates a new directory in /dir/fd by the mere fact of opening the directory. So it walks into that dir, returning to step 1. >=20 > * A similar chdir()-based version of the directory > walker below breaks badly; you can chdir() into > a directory under /dev/fd, but you can't chdir("..") > to get back out of it. (This is the particular > problem that tar is running afoul of.) Not sure about this one. I think that fdescfs vnodes do not support lookup on anything not being root of the fdescfs. >=20 > * Running "find /dev/fd" generates bogus ENOENT errors > because you can opendir() a directory inside of /dev/fd, > and read the entries, but you can't access those entries > because path searches don't work through fdescfs. Again, this may be a consequence of the previous issue. >=20 > I think the right solution here is to add a VOP_ACCESS > handler to fdescfs that bars all access to directory > nodes under /dev/fd. Basically, if your program has a > directory open, that should be reflected as a directory > node that you can't do anything with. The current implementation > allows you to chdir(), opendir(), etc, those directory > nodes, but the machinery to fully support those operations > is missing so they just screw things up. This would chomp the fdescfs functionality, IMHO. Why directory file descriptors should behave differently then any other file descriptor ? I think that the actual solution for the walker problems is to ignore the synthetic filesystems altogether. The information is provided by sysctl vfs.conflist (note that the output is binary), see VFCF_* flags, esp. VFCF_SYNTHETIC. The flag is correctly set at least by procfs, devfs and fdescfs. --/SgVJVxFudH2R+XP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkoEkhIACgkQC3+MBN1Mb4ieHACfSdqlU3dWNPycraSH9+63Yy3a W54AoIL1nvTk/mYAQ5b7UVQoMig81SBR =/GP5 -----END PGP SIGNATURE----- --/SgVJVxFudH2R+XP-- From owner-freebsd-hackers@FreeBSD.ORG Fri May 8 21:11:06 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0422C106566B for ; Fri, 8 May 2009 21:11:06 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: from mail-ew0-f159.google.com (mail-ew0-f159.google.com [209.85.219.159]) by mx1.freebsd.org (Postfix) with ESMTP id 7CB5B8FC1A for ; Fri, 8 May 2009 21:11:05 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: by ewy3 with SMTP id 3so2116707ewy.43 for ; Fri, 08 May 2009 14:11:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:received:date:from:to:cc :subject:message-id:references:mime-version:content-type :content-disposition:in-reply-to; bh=CYf4z87JHqMTfzzlSxjCNfqX4ZDqvqaj3T3IzOt71Cc=; b=c4i+z4a6HrNOciJG5rwPHWyj/lZwduURgx44xISIipsDJrPtUkATlGLNrFUzjST1CQ YmRZshsw/8SZk7ebkcgv3aQdlh7Gud9BFctjkoV6nXHncKxG7y9xFgCpqm8xec2HW1KC iIpzvgaXUK6TY/ww6mNI8fM0zbiYSek5APKkI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to; b=F4PznjHlq2xhchyF5OdVUEmnRa1EX+kBpPTYMN/TJQi28PwV1SHHU052Q7fRZQQjlA GD1Prfe2GWqsemyl4Gvot3LFlQS3D1TM6Ra01u4MxKGO0pizj8P2u149AGrYJI/S7MRv nj23q2HchwdC2vvfgktPCZ/afUNafs+DqCk8Q= Received: by 10.210.38.5 with SMTP id l5mr5007483ebl.54.1241817064607; Fri, 08 May 2009 14:11:04 -0700 (PDT) Received: from logik.internal.network (81-86-41-187.dsl.pipex.com [81.86.41.187]) by mx.google.com with ESMTPS id 10sm1937921ewy.36.2009.05.08.14.11.03 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 08 May 2009 14:11:03 -0700 (PDT) Received: by logik.internal.network (Postfix, from userid 11001) id D8F2B5C31; Fri, 8 May 2009 21:10:22 +0000 (UTC) Date: Fri, 8 May 2009 22:10:22 +0100 From: xorquewasp@googlemail.com To: Daniel Eischen Message-ID: <20090508211022.GA37475@logik.internal.network> References: <20090504185644.GA16315@logik.internal.network> <20090505005128.GA4519@logik.internal.network> <20090505022151.GA32477@logik.internal.network> <20090506140325.GA69468@logik.internal.network> <20090506152222.GC69468@logik.internal.network> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090506152222.GC69468@logik.internal.network> Cc: freebsd-hackers@freebsd.org Subject: Re: bootstrapping gnat GCC on amd64 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, 08 May 2009 21:11:06 -0000 Just an update. Finally managed to get the i386 -> amd64 compiler to compile gcc 4.4.0. It took a few Makefile patches as for some reason, cross compilation breaks gnatmake. About to try to get the amd64 compiler to compile itself and run the test suite. Added a system-freebsd_x86_64.ads profile and checked all the other references to freebsd in the source. I've scripted the entire bootstrap process so it should be easy to produce binaries for a port. xw From owner-freebsd-hackers@FreeBSD.ORG Fri May 8 21:41:19 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 569D01065670 for ; Fri, 8 May 2009 21:41:19 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id D8B638FC08 for ; Fri, 8 May 2009 21:41:18 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id A2AD31CCA7; Fri, 8 May 2009 23:41:17 +0200 (CEST) Date: Fri, 8 May 2009 23:41:17 +0200 From: Ed Schouten To: vasanth raonaik Message-ID: <20090508214117.GY58540@hoeg.nl> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wrbmJCjDMpeEYJph" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) Cc: FreeBSD Hackers , jt@0xabadba.be Subject: Re: concurrent sysctl implementation 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, 08 May 2009 21:41:19 -0000 --wrbmJCjDMpeEYJph Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, * vasanth raonaik wrote: > Hello Jt, >=20 > I am a newbee in this alias. I am having a very basic question. It would = be > really good if you could give me some of this information. > Could you please elaborate on what is the current architecture of sysctl > implementation and How the concurrency would benefit us. Right now sysctl is synchronized using the sysctl lock. The problem is that certain sysctls just block for a very long time (especially some of the GEOM ones). We also call sysctl when we execute new processes, to obtain a random number for the stack protector. This means we have quite a lot of contention on it. This lock needs to be there, because sysctls can be added and removed on demand. I think I discussed this with John Baldwin (right?) and I think we also have the issue that we cannot allow an unbounded amount of concurrent calls to sysctl, because sysctl wires memory. A solution would be to solve it as follows: - Use a semaphore, initialized to some insane high value to put an upper limit on the amount of concurrent sysctl calls. I'm not sure whether this is really needed. Maybe this issue is not as serious as we think it is. - Use an rw/rm/sxlock to protect the sysctl tree, but only pick up the lock when we traverse parts of the sysctl tree that has dynamically created entries. --=20 Ed Schouten WWW: http://80386.nl/ --wrbmJCjDMpeEYJph Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkoEpv0ACgkQ52SDGA2eCwUhWQCeNfDTUrL1RV9JgxoWHfNDPeEP UwYAnRjuuIZe2F1m9EW5dZz8+pgwTxBT =wI4p -----END PGP SIGNATURE----- --wrbmJCjDMpeEYJph-- From owner-freebsd-hackers@FreeBSD.ORG Fri May 8 23:05:35 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 551AD106564A; Fri, 8 May 2009 23:05:35 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay02.stack.nl [IPv6:2001:610:1108:5010::104]) by mx1.freebsd.org (Postfix) with ESMTP id DA3158FC12; Fri, 8 May 2009 23:05:34 +0000 (UTC) (envelope-from jilles@stack.nl) Received: by mx1.stack.nl (Postfix, from userid 65534) id E7DE6359962; Sat, 9 May 2009 01:05:33 +0200 (CEST) X-Spam-DCC: CTc-dcc2: scanner01.stack.nl 1031; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on scanner01.stack.nl X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=AWL, BAYES_00, J_CHICKENPOX_38, J_CHICKENPOX_51,NO_RELAYS autolearn=no version=3.2.5 X-Spam-Relay-Country: _RELAYCOUNTRY_ Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id 6BADC359951; Sat, 9 May 2009 01:05:31 +0200 (CEST) Received: by snail.stack.nl (Postfix, from userid 1677) id 5AD33228B7; Sat, 9 May 2009 01:05:31 +0200 (CEST) Date: Sat, 9 May 2009 01:05:31 +0200 From: Jilles Tjoelker To: Kostik Belousov Message-ID: <20090508230531.GA8413@stack.nl> References: <4A03A202.2050101@freebsd.org> <20090508201203.GJ1948@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090508201203.GJ1948@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: "'freebsd-hackers@freebsd.org'" , Tim Kientzle Subject: Re: fdescfs brokenness 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, 08 May 2009 23:05:35 -0000 On Fri, May 08, 2009 at 11:12:03PM +0300, Kostik Belousov wrote: > On Thu, May 07, 2009 at 08:07:46PM -0700, Tim Kientzle wrote: > > Colin Percival recently pointed out some issues > > with tar and fdescfs. Part of the problem > > here is tar; I need to rethink some of the > > traversal logic. > > But fdescfs is really wonky: > > * This is a nit, but: ls /dev/fd/18 should not > > return EBADF; it should return ENOENT, just > > like any other reference to a non-existent filename. > > (Just because a filename reflects a file descriptor > > does not mean it is a file descriptor.) > This is a traditional behaviour for fdescfs. According to man page, > open("dev/fd/N") shall be equivalent to fcntl(N, F_DUPFD, 0). > Solaris behaviour is the same. On open, yes, but stat behaves differently on a Solaris 10 machine here. A valid but unallocated fd number will still stat as a character device, like an allocated fd. % ls -l /dev/fd/0 /dev/fd/999 crw-rw-rw- 1 root root 320, 0 May 9 00:06 /dev/fd/0 crw-rw-rw- 1 root root 320, 999 May 9 00:06 /dev/fd/999 By the way, both FreeBSD and Solaris also behave strangely if you try to access fd numbers 1<<32 or higher. Linux seems to behave strangely as well: the fds show up as symlinks, some of which do not contain valid file names but can still be opened. However, a command like { read x <&5; read y > * The fairly routine recursive directory walker > > below gets hung in fdescfs. It appears that > > the two opendir() invocations active at the > > same time interfere with each other. > What you mean by "gets hung" ? In my limited testing, it works. > Opendir creates a new directory in /dir/fd by the mere fact of opening > the directory. So it walks into that dir, returning to step 1. > > * A similar chdir()-based version of the directory > > walker below breaks badly; you can chdir() into > > a directory under /dev/fd, but you can't chdir("..") > > to get back out of it. (This is the particular > > problem that tar is running afoul of.) > Not sure about this one. I think that fdescfs vnodes do not support > lookup on anything not being root of the fdescfs. > > * Running "find /dev/fd" generates bogus ENOENT errors > > because you can opendir() a directory inside of /dev/fd, > > and read the entries, but you can't access those entries > > because path searches don't work through fdescfs. > Again, this may be a consequence of the previous issue. > > I think the right solution here is to add a VOP_ACCESS > > handler to fdescfs that bars all access to directory > > nodes under /dev/fd. Basically, if your program has a > > directory open, that should be reflected as a directory > > node that you can't do anything with. The current implementation > > allows you to chdir(), opendir(), etc, those directory > > nodes, but the machinery to fully support those operations > > is missing so they just screw things up. > This would chomp the fdescfs functionality, IMHO. Why directory > file descriptors should behave differently then any other file > descriptor ? Linux and Solaris do not have these problems because their /dev/fd does not copy stat information from the underlying file, instead showing a character device (Solaris) or a symlink (Linux). I think a character device would fit best, because you can do little else with it than open it. The open operation is also different from opening the underlying file because it does not create a new open file description. devfs's /dev/fd/0, /dev/fd/1 and /dev/fd/2 work like this as well: they always show up as character devices no matter what the underlying file is. When opened, they duplicate the respective fd just like the full /dev/fd does. (These are located at the end of /sys/kern/kern_descrip.c.) Apparently someone noticed earlier this could be a problem, because the R and X mode bits are cleared from directories that show up in /dev/fd. It does not come as a surprise to me that that hack does not work. > I think that the actual solution for the walker problems is to > ignore the synthetic filesystems altogether. The information is > provided by sysctl vfs.conflist (note that the output is binary), > see VFCF_* flags, esp. VFCF_SYNTHETIC. The flag is correctly > set at least by procfs, devfs and fdescfs. I think it should be possible to write a directory walker program using only standard interfaces. -- Jilles Tjoelker From owner-freebsd-hackers@FreeBSD.ORG Sat May 9 00:13:43 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFDB1106566C for ; Sat, 9 May 2009 00:13:43 +0000 (UTC) (envelope-from jt@0xabadba.be) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by mx1.freebsd.org (Postfix) with ESMTP id 9C1348FC08 for ; Sat, 9 May 2009 00:13:43 +0000 (UTC) (envelope-from jt@0xabadba.be) Received: by wa-out-1112.google.com with SMTP id m38so983313waf.27 for ; Fri, 08 May 2009 17:13:43 -0700 (PDT) Received: by 10.114.131.11 with SMTP id e11mr3798708wad.75.1241828022929; Fri, 08 May 2009 17:13:42 -0700 (PDT) Received: from ?10.176.20.4? ([32.136.58.215]) by mx.google.com with ESMTPS id m25sm2047251waf.9.2009.05.08.17.13.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 08 May 2009 17:13:42 -0700 (PDT) References: <20090508214117.GY58540@hoeg.nl> Message-Id: <3C2B6A87-C127-4E1F-9A1E-DADF613B18BF@0xabadba.be> From: jt@0xabadba.be To: Ed Schouten In-Reply-To: <20090508214117.GY58540@hoeg.nl> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (5H11) Mime-Version: 1.0 (iPhone Mail 5H11) Date: Fri, 8 May 2009 20:13:32 -0400 Cc: FreeBSD Hackers , vasanth raonaik Subject: Re: concurrent sysctl implementation 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, 09 May 2009 00:13:44 -0000 Ed, Thanks :) I'll be implementing this as discussed over the next few months thanks for the technical detail I've been extremely busy with finals. I will write the list with my thoughts within the next week, sorry for the delay. =jt On May 8, 2009, at 17:41, Ed Schouten wrote: > Hi, > > * vasanth raonaik wrote: >> Hello Jt, >> >> I am a newbee in this alias. I am having a very basic question. It >> would be >> really good if you could give me some of this information. >> Could you please elaborate on what is the current architecture of >> sysctl >> implementation and How the concurrency would benefit us. > > Right now sysctl is synchronized using the sysctl lock. The problem is > that certain sysctls just block for a very long time (especially > some of > the GEOM ones). We also call sysctl when we execute new processes, to > obtain a random number for the stack protector. This means we have > quite > a lot of contention on it. This lock needs to be there, because > sysctls > can be added and removed on demand. > > I think I discussed this with John Baldwin (right?) and I think we > also > have the issue that we cannot allow an unbounded amount of concurrent > calls to sysctl, because sysctl wires memory. > > A solution would be to solve it as follows: > > - Use a semaphore, initialized to some insane high value to put an > upper > limit on the amount of concurrent sysctl calls. I'm not sure whether > this is really needed. Maybe this issue is not as serious as we think > it is. > > - Use an rw/rm/sxlock to protect the sysctl tree, but only pick up > the lock when we traverse parts of the sysctl tree that has > dynamically created entries. > > -- > Ed Schouten > WWW: http://80386.nl/ From owner-freebsd-hackers@FreeBSD.ORG Sat May 9 11:51:37 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B50EC1065672 for ; Sat, 9 May 2009 11:51:37 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.67.217]) by mx1.freebsd.org (Postfix) with ESMTP id 76D9A8FC17 for ; Sat, 9 May 2009 11:51:37 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: by mail.0x20.net (Postfix, from userid 1002) id 255133A581; Sat, 9 May 2009 13:35:00 +0200 (CEST) Date: Sat, 9 May 2009 13:35:00 +0200 From: Lars Engels To: Ed Schouten Message-ID: <20090509113459.GD56667@e.0x20.net> References: <20090508214117.GY58540@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i7F3eY7HS/tUJxUd" Content-Disposition: inline In-Reply-To: <20090508214117.GY58540@hoeg.nl> X-Editor: VIM - Vi IMproved 7.2 X-Operation-System: FreeBSD 5.5-RELEASE-p19 User-Agent: Mutt/1.5.19 (2009-01-05) X-Mailman-Approved-At: Sat, 09 May 2009 11:57:25 +0000 Cc: FreeBSD Hackers , jt@0xabadba.be, vasanth raonaik Subject: Re: concurrent sysctl implementation 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, 09 May 2009 11:51:38 -0000 --i7F3eY7HS/tUJxUd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 08, 2009 at 11:41:17PM +0200, Ed Schouten wrote: > Hi, >=20 > * vasanth raonaik wrote: > > Hello Jt, > >=20 > > I am a newbee in this alias. I am having a very basic question. It woul= d be > > really good if you could give me some of this information. > > Could you please elaborate on what is the current architecture of sysctl > > implementation and How the concurrency would benefit us. >=20 > Right now sysctl is synchronized using the sysctl lock. The problem is > that certain sysctls just block for a very long time (especially some of > the GEOM ones). We also call sysctl when we execute new processes, to > obtain a random number for the stack protector. This means we have quite > a lot of contention on it. This lock needs to be there, because sysctls > can be added and removed on demand. Why is sysctl used to get a random number? Can't we get a different source for it? --i7F3eY7HS/tUJxUd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkoFamMACgkQKc512sD3afgmLACfY9bwMdM+B8qWEvDPm2oEaaGe mxUAn3YSBnxkrHOkm+BSCBBdhP2PRQIw =mlf8 -----END PGP SIGNATURE----- --i7F3eY7HS/tUJxUd-- From owner-freebsd-hackers@FreeBSD.ORG Sat May 9 12:13:15 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 007A3106566C for ; Sat, 9 May 2009 12:13:15 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id 8FEC38FC0C for ; Sat, 9 May 2009 12:13:14 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id AC2501CDE9; Sat, 9 May 2009 14:13:13 +0200 (CEST) Date: Sat, 9 May 2009 14:13:13 +0200 From: Ed Schouten To: Lars Engels Message-ID: <20090509121313.GA58540@hoeg.nl> References: <20090508214117.GY58540@hoeg.nl> <20090509113459.GD56667@e.0x20.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="c9D8mOo1KWOdrF7C" Content-Disposition: inline In-Reply-To: <20090509113459.GD56667@e.0x20.net> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: FreeBSD Hackers , jt@0xabadba.be, vasanth raonaik Subject: Re: concurrent sysctl implementation 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, 09 May 2009 12:13:15 -0000 --c9D8mOo1KWOdrF7C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Lars, * Lars Engels wrote: > Why is sysctl used to get a random number? Can't we get a different > source for it? We probably could. I think I discussed this with Robert Watson some time ago and we could use things like ELF hints. But still, that doesn't prevent us from reaching this limitation later on. I think other people (Rink Springer) also reported this issue years ago, even before we had the stack protector enabled. --=20 Ed Schouten WWW: http://80386.nl/ --c9D8mOo1KWOdrF7C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkoFc1kACgkQ52SDGA2eCwWG6wCeLTizCGSrJjio+5gmA36IEvhw LSIAn1KhfYdQDqqNnaiX04vCYA3Sl3pa =yid8 -----END PGP SIGNATURE----- --c9D8mOo1KWOdrF7C-- From owner-freebsd-hackers@FreeBSD.ORG Sat May 9 13:34:15 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BAC8E106566B; Sat, 9 May 2009 13:34:15 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id 4FBA78FC25; Sat, 9 May 2009 13:34:15 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1M2mgv-000AxY-Bz; Sat, 09 May 2009 16:34:13 +0300 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n49DYAO4056502 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 9 May 2009 16:34:10 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n49DYARD053527; Sat, 9 May 2009 16:34:10 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n49DY9jJ053526; Sat, 9 May 2009 16:34:09 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 9 May 2009 16:34:09 +0300 From: Kostik Belousov To: Jilles Tjoelker Message-ID: <20090509133409.GL1948@deviant.kiev.zoral.com.ua> References: <4A03A202.2050101@freebsd.org> <20090508201203.GJ1948@deviant.kiev.zoral.com.ua> <20090508230531.GA8413@stack.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVQB43uFympFEer4" Content-Disposition: inline In-Reply-To: <20090508230531.GA8413@stack.nl> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1M2mgv-000AxY-Bz ad16b0ca0ad2a7fe86d6aae237c438a2 X-Terabit: YES Cc: "'freebsd-hackers@freebsd.org'" , Tim Kientzle Subject: Re: fdescfs brokenness 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, 09 May 2009 13:34:16 -0000 --EVQB43uFympFEer4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 09, 2009 at 01:05:31AM +0200, Jilles Tjoelker wrote: > On Fri, May 08, 2009 at 11:12:03PM +0300, Kostik Belousov wrote: > > On Thu, May 07, 2009 at 08:07:46PM -0700, Tim Kientzle wrote: > > > Colin Percival recently pointed out some issues > > > with tar and fdescfs. Part of the problem > > > here is tar; I need to rethink some of the > > > traversal logic. >=20 > > > But fdescfs is really wonky: >=20 > > > * This is a nit, but: ls /dev/fd/18 should not > > > return EBADF; it should return ENOENT, just > > > like any other reference to a non-existent filename. > > > (Just because a filename reflects a file descriptor > > > does not mean it is a file descriptor.) > > This is a traditional behaviour for fdescfs. According to man page, > > open("dev/fd/N") shall be equivalent to fcntl(N, F_DUPFD, 0). > > Solaris behaviour is the same. >=20 > On open, yes, but stat behaves differently on a Solaris 10 machine here. > A valid but unallocated fd number will still stat as a character > device, like an allocated fd. >=20 > % ls -l /dev/fd/0 /dev/fd/999 > crw-rw-rw- 1 root root 320, 0 May 9 00:06 /dev/fd/0 > crw-rw-rw- 1 root root 320, 999 May 9 00:06 /dev/fd/999 Yes, this makes sense. >=20 > By the way, both FreeBSD and Solaris also behave strangely if you try to > access fd numbers 1<<32 or higher. The strangeness is purely comsetical, in my opinion, but still. >=20 > Linux seems to behave strangely as well: the fds show up as symlinks, > some of which do not contain valid file names but can still be opened. > However, a command like > { read x <&5; read y which shows the first three lines under FreeBSD and Solaris, > shows the first line three times under Linux, so apparently it does not > duplicate file descriptors (at least in some cases). > I think it should be possible to write a directory walker program using > only standard interfaces. For standard-compiant fses, yes. AFAIR POSIX does not make any claims for the whole namespace. I did liked the idea of turning fdescfs nodes to character devices for stat(2). Besides fixing the issue, it also prevents recursive descent into the vfs, preventing the LOR. Being there, added check for the overflow. diff --git a/sys/fs/fdescfs/fdesc_vnops.c b/sys/fs/fdescfs/fdesc_vnops.c index d1788ae..9846357 100644 --- a/sys/fs/fdescfs/fdesc_vnops.c +++ b/sys/fs/fdescfs/fdesc_vnops.c @@ -264,7 +264,7 @@ fdesc_lookup(ap) struct thread *td =3D cnp->cn_thread; struct file *fp; int nlen =3D cnp->cn_namelen; - u_int fd; + u_int fd, fd1; int error; struct vnode *fvp; =20 @@ -296,7 +296,12 @@ fdesc_lookup(ap) error =3D ENOENT; goto bad; } - fd =3D 10 * fd + *pname++ - '0'; + fd1 =3D 10 * fd + *pname++ - '0'; + if (fd1 < fd) { + error =3D ENOENT; + goto bad; + } + fd =3D fd1; } =20 if ((error =3D fget(td, fd, &fp)) !=3D 0) @@ -383,78 +388,34 @@ fdesc_getattr(ap) { struct vnode *vp =3D ap->a_vp; struct vattr *vap =3D ap->a_vap; - struct thread *td =3D curthread; - struct file *fp; - struct stat stb; - u_int fd; - int error =3D 0; + + vap->va_mode =3D S_IRUSR|S_IXUSR|S_IRGRP|S_IXGRP|S_IROTH|S_IXOTH; + vap->va_fileid =3D VTOFDESC(vp)->fd_ix; + vap->va_uid =3D 0; + vap->va_gid =3D 0; + vap->va_blocksize =3D DEV_BSIZE; + vap->va_atime.tv_sec =3D boottime.tv_sec; + vap->va_atime.tv_nsec =3D 0; + vap->va_mtime =3D vap->va_atime; + vap->va_ctime =3D vap->va_mtime; + vap->va_gen =3D 0; + vap->va_flags =3D 0; + vap->va_bytes =3D 0; + vap->va_filerev =3D 0; =20 switch (VTOFDESC(vp)->fd_type) { case Froot: - vap->va_mode =3D S_IRUSR|S_IXUSR|S_IRGRP|S_IXGRP|S_IROTH|S_IXOTH; vap->va_type =3D VDIR; vap->va_nlink =3D 2; vap->va_size =3D DEV_BSIZE; - vap->va_fileid =3D VTOFDESC(vp)->fd_ix; - vap->va_uid =3D 0; - vap->va_gid =3D 0; - vap->va_blocksize =3D DEV_BSIZE; - vap->va_atime.tv_sec =3D boottime.tv_sec; - vap->va_atime.tv_nsec =3D 0; - vap->va_mtime =3D vap->va_atime; - vap->va_ctime =3D vap->va_mtime; - vap->va_gen =3D 0; - vap->va_flags =3D 0; vap->va_rdev =3D NODEV; - vap->va_bytes =3D 0; - vap->va_filerev =3D 0; break; =20 case Fdesc: - fd =3D VTOFDESC(vp)->fd_fd; - - if ((error =3D fget(td, fd, &fp)) !=3D 0) - return (error); - - bzero(&stb, sizeof(stb)); - error =3D fo_stat(fp, &stb, td->td_ucred, td); - fdrop(fp, td); - if (error =3D=3D 0) { - vap->va_type =3D IFTOVT(stb.st_mode); - vap->va_mode =3D stb.st_mode; - if (vap->va_type =3D=3D VDIR) - vap->va_mode &=3D ~(S_IRUSR|S_IXUSR|S_IRGRP|S_IXGRP|S_IROTH|S_IXOTH); - vap->va_nlink =3D 1; - vap->va_flags =3D 0; - vap->va_bytes =3D stb.st_blocks * stb.st_blksize; - vap->va_fileid =3D VTOFDESC(vp)->fd_ix; - vap->va_size =3D stb.st_size; - vap->va_blocksize =3D stb.st_blksize; - vap->va_rdev =3D stb.st_rdev; - - /* - * If no time data is provided, use the current time. - */ - if (stb.st_atimespec.tv_sec =3D=3D 0 && - stb.st_atimespec.tv_nsec =3D=3D 0) - nanotime(&stb.st_atimespec); - - if (stb.st_ctimespec.tv_sec =3D=3D 0 && - stb.st_ctimespec.tv_nsec =3D=3D 0) - nanotime(&stb.st_ctimespec); - - if (stb.st_mtimespec.tv_sec =3D=3D 0 && - stb.st_mtimespec.tv_nsec =3D=3D 0) - nanotime(&stb.st_mtimespec); - - vap->va_atime =3D stb.st_atimespec; - vap->va_mtime =3D stb.st_mtimespec; - vap->va_ctime =3D stb.st_ctimespec; - vap->va_uid =3D stb.st_uid; - vap->va_gid =3D stb.st_gid; - vap->va_gen =3D 0; - vap->va_filerev =3D 0; - } + vap->va_type =3D VCHR; + vap->va_nlink =3D 1; + vap->va_size =3D 0; + vap->va_rdev =3D makedev(0, vap->va_fileid); break; =20 default: @@ -462,9 +423,8 @@ fdesc_getattr(ap) break; } =20 - if (error =3D=3D 0) - vp->v_type =3D vap->va_type; - return (error); + vp->v_type =3D vap->va_type; + return (0); } =20 static int --EVQB43uFympFEer4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkoFhlEACgkQC3+MBN1Mb4jE9gCg5ZbgXvHn7Zwgu46EUGRXGDWu y0gAoLS6B9Epko3WxW786qfz/uj56tw5 =EjQ6 -----END PGP SIGNATURE----- --EVQB43uFympFEer4-- From owner-freebsd-hackers@FreeBSD.ORG Sat May 9 15:06:17 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23644106566C for ; Sat, 9 May 2009 15:06:17 +0000 (UTC) (envelope-from subhro.kar@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by mx1.freebsd.org (Postfix) with ESMTP id E746D8FC0A for ; Sat, 9 May 2009 15:06:16 +0000 (UTC) (envelope-from subhro.kar@gmail.com) Received: by wa-out-1112.google.com with SMTP id m38so1162433waf.27 for ; Sat, 09 May 2009 08:06:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=FltQ+pBzjS2ydBEoOQWoNwAw5CP2Pv98dQiWmXHYomQ=; b=lgA8n+7Tqv7qqRUppU8X5uEAF2GB48L+INwfZLG02oJrw/6arpW+oPOC0r3q0uVoAF wUfCgdXr/JAmYc5Dhy7J97242FZWC3pko2X9m1cPAMDbSVR+UPm5Yvj9GPCQ6cWabj5S unckoQLQbSjlVtOB32quTsc2FhZeAlz5MeAMg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=FcDTvp93VBSQdhFCgQ/Xes4tUIpQPEKIQkcLbfACiDGLC4O5YMQF9kvuShSypQu7gY uvyDKGgqB59T3GjkO8LCnnTN3YdMoOSypa36lZwywiP2IJKXGTJ+XqEv5phNbRtBrmZq RgyVuppNMUxfIoO9j49+TxPvs89uRn1aTn7qM= Received: by 10.115.79.8 with SMTP id g8mr4161752wal.95.1241879853320; Sat, 09 May 2009 07:37:33 -0700 (PDT) Received: from ?192.168.0.176? ([118.95.34.122]) by mx.google.com with ESMTPS id k14sm2930218waf.30.2009.05.09.07.37.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 09 May 2009 07:37:32 -0700 (PDT) Message-Id: From: Subhro Kar To: Aditya Sarawgi In-Reply-To: <20090424013250.GA3672@pcbsd> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Sat, 9 May 2009 20:07:15 +0530 References: <20090424013250.GA3672@pcbsd> X-Mailer: Apple Mail (2.930.3) Cc: hackers@freebsd.org Subject: Re: SoC 2009: Improving ext2fs and making it GPL free 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, 09 May 2009 15:06:17 -0000 Hello Aditya, What are the things you plan to work on? In other words, what exact improvement are you trying to implement? Thanks Subhro On 24-Apr-09, at 7:02 AM, Aditya Sarawgi wrote: > Hi, > > I'm Aditya Sarawgi from India. I will be working on FreeBSD's ext2fs > as a part of this year's summer of > code program. I will be improving the current implementation and I > will also rewrite parts of ext2fs > under GPL. My mentor is Ulf Lilleengen. For more details you can visit > http://wiki.freebsd.org/SOC2009AdityaSarawgi > > Cheers, > Aditya Sarawgi > _______________________________________________ > 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 Sat May 9 16:54:14 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 862C01065670 for ; Sat, 9 May 2009 16:54:14 +0000 (UTC) (envelope-from sarawgi.aditya@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228]) by mx1.freebsd.org (Postfix) with ESMTP id 576BA8FC1C for ; Sat, 9 May 2009 16:54:14 +0000 (UTC) (envelope-from sarawgi.aditya@gmail.com) Received: by rv-out-0506.google.com with SMTP id k40so1718968rvb.43 for ; Sat, 09 May 2009 09:54:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=JO0bJ13SBsZwStom7UhaaMOHSqhLIKPHyiQ7dwyrOMc=; b=EinjNzPByRQR6KvlkQQrecNGdyFEQK/RY82JC52IGb/imz4uYqU7zNw6gNp67CjhA/ xUfUaL6Zw/iBsEtNobaVh9mBRTYZXB07+o4/ogjbjdlIm11Wjxau+c1bX4oiJ081WfEN zBur5ZPo3QUr/97Gr46v0qxtI6+mm9ACoE82E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=TLU0B0QoE/0YjN8hFGUFZtD/ZWUH5BB09pGKh/AdkUPBm3nKGZj3Q1ROqKQNuHp9Ti D/HNQ9+BjzV9Gk90ECYJxmEI7opy+EHtTi5uI01TUSJ+l4cr7MKth6C1t6o8igs6dP3I 66kjshgag6GZw8dBE8XGz5AWaMLMZy6i8CYCI= Received: by 10.140.202.12 with SMTP id z12mr2316968rvf.228.1241886671410; Sat, 09 May 2009 09:31:11 -0700 (PDT) Received: from ([123.50.179.22]) by mx.google.com with ESMTPS id l31sm4368826rvb.39.2009.05.09.09.31.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 09 May 2009 09:31:10 -0700 (PDT) Date: Sat, 9 May 2009 22:02:19 +0530 From: Aditya Sarawgi To: freebsd-hackers@freebsd.org Message-ID: <4a05afce.1f588c0a.0ed4.0089@mx.google.com> References: <4A05A273.3010904@cable.net.co> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A05A273.3010904@cable.net.co> User-Agent: Mutt/1.4.2.3i Subject: Re: SoC 2009: Improving ext2fs and making it GPL free 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, 09 May 2009 16:54:14 -0000 On Sat, May 09, 2009 at 10:34:11AM -0500, Pedro F. Giffuni wrote: > Hi Aditya; > > Your project is very interesting, specially if you get to freeing us > from the GPL in ext2fs. > > I have a couple of short documents for you. > > First here is the description of the Mach port on which our current code > is based: > http://www.cs.utah.edu/flux/lites/html/ext2fs.html > > Here is the revision document of the NetBSD port: > http://www.feyrer.de/NetBSD/ext2fs-rev1.html > > I am unsure if it will be an easy project or not, or if it's just better > to start from scratch from the complete NetBSD port but if you happen to > have time for additional features, my personal wishlist has: > > - SEEK_HOLE and SEEK_DATA extensions for lseek(2) > - support for gjournal. > > just a wishlist... I know I am too optimistic :). > > best regards, > > Pedro. Hi, Thnaks for the lites document. Porting the entire file system from NetBSD will be quite difficult and the current implementation has only parts under GPL so my plan is to rewrite only those parts. My plan is - freeing ext2fs from GPL. - making it MPSAFE (after SoC). - adding new features like journalling (possibly using gjournal ), extended attribute support etc. Cheers, Aditya Sarawgi From owner-freebsd-hackers@FreeBSD.ORG Sat May 9 17:24:52 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA0CB106566B for ; Sat, 9 May 2009 17:24:52 +0000 (UTC) (envelope-from sarawgi.aditya@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id AA6198FC15 for ; Sat, 9 May 2009 17:24:52 +0000 (UTC) (envelope-from sarawgi.aditya@gmail.com) Received: by rv-out-0506.google.com with SMTP id k40so1728093rvb.43 for ; Sat, 09 May 2009 10:24:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=xpuvdxelzFjIqT71W4F2R+k5kKZxHZ9v4+Utf0zdIic=; b=WOSCHb3DvIN+PSlE8pwKabtL6WWtNjjW9BXWqRxuWN+TTfjlDWQPJHwkxw6ymkBbZw Og6n8d/NVqCzP/V1rPaHrE9nE0RD+axZJZL9Z/xSe0gls5zroKSaJ8Yk/CZdwo1l3Ai9 7pqQtlLZwGM8HnCfhCWVd+I2dUxUydxuQSfoY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=r+un2d8ir3Uy11kq6I9HjYg/TjX5ebcF5vAGdoxTVbMSl5GpqUpJYSLejg2kZyuE5u v/Gv0Xsrm02GrGsrRpIpMYCq4tgmwT90tUXwa5OQR35AvAjsSB3Ntwl9+L1UeqvDxolQ kTUkpkGst+5rzEWQTNdB1p/7n9KCoSU6NI3UY= Received: by 10.141.142.1 with SMTP id u1mr2030894rvn.18.1241889892201; Sat, 09 May 2009 10:24:52 -0700 (PDT) Received: from ([123.50.179.236]) by mx.google.com with ESMTPS id b39sm1806678rvf.7.2009.05.09.10.24.49 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 09 May 2009 10:24:50 -0700 (PDT) Date: Sat, 9 May 2009 22:55:58 +0530 From: Aditya Sarawgi To: freebsd-hackers@freebsd.org Message-ID: <4a05bc62.27b38c0a.0a67.ffff81b4@mx.google.com> References: <20090424013250.GA3672@pcbsd> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Subject: Re: SoC 2009: Improving ext2fs and making it GPL free 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, 09 May 2009 17:24:53 -0000 On Sat, May 09, 2009 at 08:07:15PM +0530, Subhro Kar wrote: > Hello Aditya, > > What are the things you plan to work on? In other words, what exact > improvement are you trying to implement? > > Thanks > Subhro > Hi, I will try to fix the bugs present in the current implementation and a new block allocation policy for it. If time permits I will implement hash_dir support for it and I will work on to make it MPSAFE after SoC :) Cheers, Aditya Sarawgi From owner-freebsd-hackers@FreeBSD.ORG Sat May 9 19:13:24 2009 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4BC41065716; Sat, 9 May 2009 19:13:24 +0000 (UTC) (envelope-from so14k@valentine.liquidneon.com) Received: from valentine.liquidneon.com (valentine.liquidneon.com [216.87.78.132]) by mx1.freebsd.org (Postfix) with ESMTP id 7A0258FC24; Sat, 9 May 2009 19:13:24 +0000 (UTC) (envelope-from so14k@valentine.liquidneon.com) Received: by valentine.liquidneon.com (Postfix, from userid 1018) id 070CA8FE62; Sat, 9 May 2009 13:12:54 -0600 (MDT) Date: Sat, 9 May 2009 13:12:53 -0600 From: Brad Davis To: freebsd-hackers@FreeBSD.org Message-ID: <20090509191253.GD40521@valentine.liquidneon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: FreeBSD Status Reports January - March, 2009 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, 09 May 2009 19:13:25 -0000 FreeBSD Quarterly Status Report Introduction Since the last Status Reports there has been interesting progress in FreeBSD Development. FreeBSD 7.2 was released just a few days ago. Some of the highlights include: Support for superpages in the FreeBSD Virtual Memory subsystem. The FreeBSD Kernel Virtual Address space has been increased to 6GB on amd64. An updated jail(8) subsystem that supports multi-IPv4/IPv6/noIP and much more. Lots of FreeBSD Developers are in Ottawa, Canada attending the FreeBSD Developer Summit that is before BSDCan. BSDCan officially starts tomorrow and should cover lots of interesting topics, see the BSDCan Website for more information. Thanks to all the reporters for the excellent work! We hope you enjoy reading. __________________________________________________________________ Projects * Clang replacing GCC in the base system * Device mmap() Extensions * OpenBSM * Release Engineering * Sysinfo - a set of scripts which document your system * TrustedBSD MAC Framework in GENERIC * VFS/NFS DTrace Probes * VirtualBox on FreeBSD FreeBSD Team Reports * FreeBSD BugBusting Team Architectures * FreeBSD/powerpc G5 Support * FreeBSD/sparc64 UltraSPARC III support Documentation * Dutch Documentation Project * German Documentation Project * Hungarian Documentation Project Google Summer of Code * BSD-licensed text-processing tools __________________________________________________________________ BSD-licensed text-processing tools URL: http://perforce.freebsd.org/depotTreeBrowser.cgi?FSPC=//depot/projects/ soc2008/gabor_textproc Contact: Gábor Kövesdán Currently, grep is finished and is only waiting for a portbuild test. It is known to be more or less feature complete, while it is much smaller than the GNU version. As for sort, there has been some progress with the complete rewrite and it is lacking few options. Performance is to be measured, as well. Open tasks: 1. Test grep on pointyhat. 2. Complete sort with the missing features. 3. Do performance measurements for sort and look for possible optimization opportunities. 4. Test sort on pointyhat. __________________________________________________________________ Clang replacing GCC in the base system URL: http://wiki.freebsd.org/BuildingFreeBSDWithClang URL: http://git.hoeg.nl/?p=llvm-bmake URL: http://clang.llvm.org/ Contact: Ed Schouten Contact: Roman Divacky Contact: Brooks Davis Contact: Pawel Worach The last 3-4 months we've been working together with the LLVM developers to discuss any bugs and issues we are experiencing with their Clang compiler frontend. The FreeBSD project is looking at the possibility to replace GCC with Clang as a system compiler. It can compile 99% of the FreeBSD world and can compile booting kernel on i386/amd64 but it still contains bugs and its C++ support is still immature. Ed is maintaining a patchset for the FreeBSD sources to replace cc(1) by a Clang binary and bootstrap almost all sources with the Clang compiler. The LLVM developers are very helpful fixing most of the bugs we've reported (over 100). Unfortunately we are currently blocked on some bug reports that prevent us from building libc, libm, libcrypto and various CDDL libraries with Clang but the FreeBSD kernel itself compiles and boots. Open tasks: 1. Testing Clang with compilation of various applications and reporting bugs. 2. Testing the llvm-bmake branch to find more bugs. 3. Arranging an experimental ports build. __________________________________________________________________ Device mmap() Extensions URL: http://www.FreeBSD.org/~jhb/pat/ Contact: John Baldwin GPU device drivers are increasingly requiring more sophisticated support for mapping objects into both userland and the kernel. For example, memory used for textures often needs to be mapped Write-Combining rather than Write-Back. I have recently created three patches to provide several extensions. The first patch allows device drivers to use a different VM object to back specific mmap() calls instead of always using the device pager. The second patch introduces a new VM object type that can map an arbitrary set of physical address ranges. This can be used to let userland mmap PCI BARs, etc. The third patch allows memory mappings to use different caching modes (e.g. Write-Combining or Uncacheable). Together I believe these patches provide the remaining pieces needed for an Nvidia amd64 driver. They will also be useful for future Xorg DRM support as well. The current set of patches can be safely merged back to 7.x as well. Currently I am waiting for review and feedback from several folks. I am hopeful that these patches will be in HEAD soon, prior to the 8.0 freeze. __________________________________________________________________ Dutch Documentation Project URL: http://wiki.freebsd.org/DutchDocumentationProject URL: http://www.freebsd.org/doc/nl/ URL: http://p4web.freebsd.org/@md=d&cd=//&c=pFl@//depot/projects/docproj_nl/ ?ac=83 Contact: Remko Lodder Contact: René Ladan The FreeBSD Dutch Documentation Project is an ongoing project to translate FreeBSD Documentation into the Dutch language. The translation of the Handbook was completed last January. It is kept up-to-date with the English version. Furthermore five articles and the flyer have been translated. Some initial work has been done to translate the website, but most likely more translators are needed to fully realize it. Open tasks: 1. Recruit more translators. 2. Keep the translations up-to-date with the English versions. 3. Finish the translation of the FAQ. 4. Translate more articles and maybe some books. __________________________________________________________________ FreeBSD BugBusting Team URL: http://www.FreeBSD.org/support.html#gnats URL: http://wiki.FreeBSD.org/BugBusting URL: http://people.FreeBSD.org/~linimon/studies/prs/ URL: http://people.freebsd.org/~linimon/studies/prs/recommended_prs.html Contact: Mark Linimon Contact: Remko Lodder We continue to classify PRs as they arrive, with 'tags' corresponding to the kernel subsystem, or man page references for userland PRs. These tags, in turn, produce lists of PRs sorted both by tag and by manpage Mark Linimon (linimon@) has created special reports for the Release Engineering Team to help focus on regressions and other areas of interest relating to the release of FreeBSD 7.2 in the coming weeks. This is a refinement of the 'customized reports for developers' announced in the last status report. A full list of all the automatically generated reports is also available. Any recommendations for reports which do not currently exist but which would be beneficial are welcomed. Mark Linimon also continues attempting to define the general problem and investigating possible new work flow models, and will be presenting on the subject at BSDCan. The list of PRs recommended for committer evaluation by the BugBusting team continues to receive new additions. This list contains PRs, mostly with patches, that the BugBusting team feel are probably ready to be committed as-is, or are probably trivially resolved in the hands of a committer with knowledge of the particular subsystem. All committers are invited to take a look at this list whenever they have a spare 5 minutes and wish to close a PR. Since the last status report, the number of open bugs continued to hover around the 5600 mark, although has began to rise with the 7.2 ports freeze. As always, more help is appreciated, and committers and non-committers alike are invited to join us on #freebsd-bugbusters on EFnet and help close stale PRs or commit patches from valid PRs. Open tasks: 1. Try to find ways to get more committers helping us with closing PRs that the team has already analyzed. 2. Think of some way for committers to only view PRs that have been in some way 'vetted' or 'confirmed'. 3. Generate more publicity for what we've already got in place, and for what we intend to do next. 4. Define new categories, classifications, and states for PRs, that will better match our work flow (in progress). __________________________________________________________________ FreeBSD/powerpc G5 Support Contact: Nathan Whitehorn FreeBSD 8.0-CURRENT now has support for PowerPC CPUs operating in the 64-bit bridge mode. This includes the PowerPC 970 (G5) as well as the POWER3 and POWER4. Currently only Apple systems are known to work. Open tasks: 1. IBM systems currently are not supported due to missing northbridge support. 2. Software fan control on SMU-based Apple G5 systems (G5 iMac, later Powermac G5) is not available. __________________________________________________________________ FreeBSD/sparc64 UltraSPARC III support Contact: Marius Strobl Like announced in the previous status report, support for sun4u-machines based on UltraSPARC III and beyond has been MFC'ed to stable/7 (the last missing piece was r190297) and thus will be present in the upcoming 7.2-RELEASE and can be already tested with 7.2-RC1. Additionally, as of r191076 machfb(4) has been fixed to work with UltraSPARC III and beyond, that fix unfortunately did not make it into 7.2-RC1 but will be in the final version. The X.Org 7.4 and Firefox ports as well as some other gecko-based ones like Seamonkey once again have been fixed to also work and package on sparc64, including on UltraSPARC III and UltraSPARC IIIi based machines equipped with cards driven by creator(4) or machfb(4). The driver for the Sun Cassini/Cassini+ as well as National Semiconductor DP83065 Saturn Gigabit NICs found on-board for example in Fire V440 and as add-on cards is coming along nicely, the last thing which needs to be implemented before it can hit CURRENT is support for jumbo frames. __________________________________________________________________ German Documentation Project URL: https://doc.bsdgroup.de Contact: Johann Kois Contact: Martin Wilke In February 2009 the German version of the FreeBSD Developer's handbook went online. Additionally we managed to update large areas of the FAQ thanks to the contributions of Benedict Reuschling. The website (at least the areas we see as relevant for a translation) is translated and updated constantly. More volunteers are always welcome of course, as there is still plenty of work to be done. Open tasks: 1. Update the existing documentation set (especially the handbook). 2. Read the translations. Check for problems/mistakes. Send feedback. __________________________________________________________________ Hungarian Documentation Project URL: http://www.FreeBSD.org/hu URL: http://www.FreeBSD.org/doc/hu URL: http://wiki.FreeBSD.org/HungarianDocumentationProject URL: http://p4web.freebsd.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@// depot/projects/docproj_hu/?ac=83 Contact: Gábor Kövesdán Contact: Gábor Páli We are proud to announce that the FreeBSD Hungarian web pages have been extended by the following items: * Project news entries, staring from 2009 (HTML, RSS, RDF) * Press releases, starting from 2008 (HTML, RSS) * Events, starting from 2009 (HTML, RSS) * Security advisories (HTML, RSS) We are still hoping that having the FDP Primer translated will encourage others to help our work. Feel free to contribute, every submitted line of translation or feedback is appreciated and is highly welcome. For more information on how to contribute, please read the project's introduction (in Hungarian). Open tasks: 1. Translate news entries, press releases. 2. Translate Release Notes for -CURRENT and 8.X. 3. Translate articles. 4. Translate web pages. 5. Read the translations, send feedback. __________________________________________________________________ OpenBSM URL: http://www.openbsm.org/ Contact: Robert Watson Contact: TrustedBSD audit mailing list The TrustedBSD Project has now released OpenBSM 1.1, the second production release of the OpenBSM code base. OpenBSM 1.1 has been merged to FreeBSD 8-CURRENT, and will be merged to 7-STABLE before FreeBSD 7.3. Major changes since OpenBSM 1.0 include: * Trail files now include the host where the trail is generated. Crash recovery has been improved. Trail expiration based on size and date is now supported; by default trail files will be expired after 10MB of trails. The default individual trail limit is now 2MB. * Mac OS X Snow Leopard is now a fully supported platform; launchd(8) can now be used to launchd auditd(8). Command line tools and libraries are now supported on Mac OS X Leopard. * Extended header tokens are now supported, allowing audit trails to be tagged with a host identifier. IPv6 addresses are now supported in subject tokens. BSM token and record types have been further synchronized to OpenSolaris; support for many new system calls has been added. Local errors and socket types are mapped to and from BSM values. Since the last test release, OpenBSM 1.1 beta 1, 32/64-bit compatibility has been fixed for the auditon(2) system call. A default "expire-after" of 10MB is now set in audit_control(5). Local fcntl(2) arguments are now mapped to wire BSM versions using new APIs. The audit_submit(3) man page has been fixed. A new audit event class has been added for post-login authentication and access control events. Open tasks: 1. Migrate to sbufs in token-encoding. 2. Support for auditing NFS RPCs. __________________________________________________________________ Release Engineering URL: http://www.FreeBSD.org/releng/ Contact: Release Engineering Team The Release Engineering Team (with lots of help from lots of other people) released FreeBSD 7.2 on May 4th, 2009. During this period we have also begun reminding developers of the upcoming FreeBSD 8.0 release cycle which is scheduled to begin in early June 2009 with release targeted at early September 2009. __________________________________________________________________ Sysinfo - a set of scripts which document your system URL: http://danger.rulez.sk/index.php/2009/04/14/sysinfo-a-set-of-scripts-wh ich-document-your-freebsd-system/ URL: https://forums.freebsd.org/showthread.php?p=19321 Contact: Daniel Gerzo Sysinfo a shell script which purpose is to automatically gather system information and document hardware and software configuration of the given host system. The goal is to provide a system operator with descriptive information about an unknown FreeBSD installation. It consists of several modules (also shell scripts), thus is easily extensible and provides an easy way to inspect overall system configuration. It has been written as part of my Bachelor thesis and its development is a work in progress. Therefore, I would appreciate if you could provide me with some feedback as I will defend my thesis soon. Your feedback is welcome at the forums , or alternatively you can send me a private email. The tool itself can now be installed using the Ports tree from the sysutils/sysinfo port. Open tasks: 1. Receive additional feedback. 2. Perform more testing. 3. Extend and improve the tool. __________________________________________________________________ TrustedBSD MAC Framework in GENERIC URL: http://www.trustedBSD.org/mac.html Contact: Robert Watson Contact: TrustedBSD discussion mailing list There is on-going work to allow "options MAC" to be included in the GENERIC kernel for 8.0. This primarily consists of performance work to reduce overhead when policies are used, and eliminate when none are configured. Work to date includes: * The MAC Framework now detects which object types are labeled by policies, and MAC label storage is not allocated when it won't be used. * Add MAC Framework DTrace probes so allow more easy analysis of MAC Framework and policy interactions. * Eliminate mutex-protected reference count used to prevent module unload during entry point invocation, and replace with an sx lock and an rwlock, respectively for long-sleepable and short-sleepable entry points, significantly lowering the overhead of entering the MAC Framework. If no dynamic policies are loaded, no locking overhead is taken. Open tasks: 1. Move to rmlocks for non-sleepable entry points to reduce cache line thrashing under load. 2. Macroize invocation of MAC Framework entry points from the kernel, and perform caller-side determination of whether MAC is enabled in order to avoid additional function call overhead in the caller path if MAC is disabled. __________________________________________________________________ VFS/NFS DTrace Probes Contact: Robert Watson A new DTrace provider, dtnfsclient, has been added to the FreeBSD 8.x kernel, and will be merged to 7.x before 7.3. The following probes are available: * nfsclient:{nfs2,nfs3}:{procname}:start - NFSv2 and NFSv3 RPC start probes * nfsclient:{nfs2,nfs3}:{procname}:done - NFSv2 and NFSv3 RPC done probes * nfsclient:accesscache:: - NFS access cache flush/hit/miss/load probes * nfsclient:attrcache:: - NFS attribute cache flush/hit/miss/done In addition, a number of VFS probes have been added: * vfs:vop:{vopname}:entry - VOP entry probe * vfs:vop:{vopname}:return - VOP return probe * vfs:namei:lookup:entry - VFS name lookup entry probe * vfs:namei:lookup:return - VFS name lookup return probe * vfs:namecache:*:* - VFS namecache enter/enter_negative/fullpath_enter/fullpath_hit/fullpath_miss/full path_return/lookup_hit/lookup_hit_negative/lookup_miss/purge/purge_ negative/purgevfs/zap/zap_negative probes These probes make it much easier to trace NFS and VFS events. Open tasks: 1. Add VFSOP tracing. 2. Add RPC-layer tracing, such as RPC retransmits. 3. Provide decoded NFS RPCs in order to expose transaction IDs and file handles. __________________________________________________________________ VirtualBox on FreeBSD URL: http://miwi.bsdcrew.de/2009/05/virtualbox-on-freebsd/ URL: http://miwi.bsdcrew.de/2009/05/virtualbox-on-freebsd-first-screenshots/ URL: http://vbox.innotek.de/pipermail/vbox-dev/2009-May/001369.html Contact: Beat Gaetzi Contact: Bernhard Froehlich Contact: Dennis Herrmann Contact: Martin Wilke After the first mail from Alexander Eichner on the vbox-dev mailinglist, we started the work on a VirtualBox port. 6 Days was needed to get VirtualBox to start with over 20 patches. We'd like to say thanks to Alexander Eichner, all the VirtualBox Developers, Gustau Perez and Ulf Lilleengen. If you like to play with the current port you can checkout the port here. Please do not ping us about any problems, we know about a lot and are still working to get them all solved before we do an official call for testing. Open tasks: 1. Fix kernel crashes on 7.2-RELEASE. 2. Code cleanup. 3. Fix errors on AMD64. 4. Fix user/permission problems.