From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 00:03:47 2008 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 14DC016A40B; Sun, 24 Feb 2008 00:03:47 +0000 (UTC) (envelope-from ap@bnc.net) Received: from bis.bonn.org (www.bis.bonn.org [217.110.117.102]) by mx1.freebsd.org (Postfix) with ESMTP id 61AEE13C4CE; Sun, 24 Feb 2008 00:03:45 +0000 (UTC) (envelope-from ap@bnc.net) X-Junk-Score: 2 [X] X-SpamCatcher-Score: 2 [X] X-Junk-Score: 0 [] X-Cloudmark-Score: 0 [] Received: from [194.39.192.125] (account bnc-mail@mailrelay.mailomat.net HELO bnc.net) by bis.bonn.org (CommuniGate Pro SMTP 5.2c4) with ESMTPSA id 9480312; Sun, 24 Feb 2008 00:05:53 +0100 X-SpamCatcher-Score: 2 [X] Received: from [194.39.194.142] (account ap HELO wasabi.wlan.bnc.net) by bnc.net (CommuniGate Pro SMTP 5.2.0) with ESMTPSA id 3077324; Sun, 24 Feb 2008 00:03:35 +0100 Message-Id: <31648FC5-26B9-4359-ACC8-412504D3257B@bnc.net> From: Achim Patzner To: "David E. Thiel" In-Reply-To: <20080223222733.GI12067@redundancy.redundancy.org> Content-Type: multipart/signed; boundary=Apple-Mail-3-14831615; micalg=sha1; protocol="application/pkcs7-signature" Mime-Version: 1.0 (Apple Message framework v919.2) Date: Sun, 24 Feb 2008 00:03:32 +0100 References: <20080223010856.7244.qmail@smasher.org> <20080223222733.GI12067@redundancy.redundancy.org> X-Mailer: Apple Mail (2.919.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 24 Feb 2008 00:03:47 -0000 --Apple-Mail-3-14831615 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit >> article below. does anyone know how this affects eli/geli? > > There's fairly little any disk crypto system can do to thoroughly > defend > against this. Hm. Strange. Serious hardware is very well suited to do that (usually by adding well defended crypto hardware). Keys don't have to be stored in unsafe places. Achim Patzner --Apple-Mail-3-14831615-- From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 00:16:56 2008 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 B569216A404 for ; Sun, 24 Feb 2008 00:16:56 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (bhuda.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 6E51613C45B for ; Sun, 24 Feb 2008 00:16:56 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 57615 invoked by uid 1001); 24 Feb 2008 00:15:40 -0000 Received: from bhuda.mired.org (localhost.localdomain [127.0.0.1]) by bhuda.mired.org (tmda-ofmipd) with ESMTP; Sat, 23 Feb 2008 19:15:40 -0500 Date: Sat, 23 Feb 2008 19:15:39 -0500 To: freebsd-hackers@freebsd.org Message-ID: <20080223191539.4b29880d@bhuda.mired.org> In-Reply-To: <20080223.162836.-1286958600.imp@bsdimp.com> References: <20080223131937.182373b2@bhuda.mired.org> <20080223.120546.74701383.imp@bsdimp.com> <20080223155355.3f80b77f@bhuda.mired.org> <20080223.162836.-1286958600.imp@bsdimp.com> Organization: Meyer Consulting X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.12; amd64-portbld-freebsd6.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAG1BMVEXguIzRkGnhyaz069mXhW0WHRnbrnR9WCQ6LB0CchNMAAACSUlEQVQ4jV2TQW7jMAxFGaPQOgQEdZaGMsgBrAvUA03dCxj1Uu4U2gfwQD7AGNax51NK07RcxXz6/CSl0Ij450vkPG1jzpIZM1UwDCl/xB14TWnNX8A00Qj5a0mnVFVbVUz4MeErea2HikSRqZzY894zwg9p2+/AtO8LzxFED+tNAUFeU29iFOLRxlZAcdo9A8wi8ZBMV4BKPde82Oxrvs6BTkulQIClte0DLFzzsKk9j1MBex8iUaP00Bd78S/muyFScrTXz6zLkEUxJp+SabQfNOs4f4Jpx5qSZ/304PWwlEWP1cOn/mJQR7EOD+uKhjcBLziuL7xoY5Xm+VFAUSw/LwwwsHEHxihpwV4EJH0xXRkbw1PkRw+X4pEuSJwBggqk+HEYKkiL5/74/nQkogigzQsAFrakxZyfw3wMIEEZPv4AWMfxwqE5GNxGaERjmH+PG8AE0L4/w9g0lsp1raLYAN5azQa+AOoO9NwcpFkTrG2VKNMNEL5UKUUAw34tha0z7onUG0oBoNtczE04GwFE3wCHc0ChezAJ6A1WMV81AtY7wDAJSlXwV+4cwBvsOsrQMRawfQEBz0deEZ7WNpV2szckIKo5VpDHDSDvF1GItwqqAlG01Hh50BGtVhuUkjkasg/14bYFGCgWg1fSWHvmOoJck2xdp9ZvZBHzDVTzX23TkrOn7qe5U2COEw5D4Vx3qEQpFY2Z/3QFnJxzp7YCmSMG19nOUoe869zZfOQb5ywQuWu0yCn5+8gxZz+BE7vG3j4/wbf4D/sXN9Wug1s7AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Delivery-Agent: TMDA/1.1.11 (Ladyburn) From: Mike Meyer Subject: Re: find -lname and -ilname implemented 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, 24 Feb 2008 00:16:56 -0000 On Sat, 23 Feb 2008 16:28:36 -0700 (MST) "M. Warner Losh" wrote: > In message: <20080223155355.3f80b77f@bhuda.mired.org> > Mike Meyer writes: > : > In short, I'm continuig the long tradition that we've done as FreeBSD > : > and that BSD and other Unix vendors did before us: compatibility with > : > other implementations. > : > : I suspect your definition of "long tradition" is a lot shorter than > : mine. That's they only way I can make that statement make sense - at > : least the part about BSD and other Unix vendors. > > Long tradition here spans about 30 years. SunOS 3.5 had many switches > that did nothing, but were there for compatibility with System III > systems, as one example. That's one example. On the other hand, trying to go from SunOS 3 or 4 (or BSD 4) to other systems - HPUX, AIX, OSF, RiscOS, UniCOS and SunOS 5 being the easy ones to recall - left users wondering what the hell had hit them. Being compatible with other vendors was so unimportant to most vendors that the unix market was generally regarded as balkanized. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 00:28:02 2008 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 1160B16A409 for ; Sun, 24 Feb 2008 00:28:02 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (bhuda.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id B962913C45E for ; Sun, 24 Feb 2008 00:28:01 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 57738 invoked by uid 1001); 24 Feb 2008 00:26:45 -0000 Received: from bhuda.mired.org (localhost.localdomain [127.0.0.1]) by bhuda.mired.org (tmda-ofmipd) with ESMTP; Sat, 23 Feb 2008 19:26:45 -0500 Date: Sat, 23 Feb 2008 19:26:44 -0500 To: freebsd-hackers@freebsd.org Message-ID: <20080223192644.13a33408@bhuda.mired.org> In-Reply-To: <20080223214913.GE39699@lor.one-eyed-alien.net> References: <20080222.225937.-146245356.imp@bsdimp.com> <20080223.000308.686168314.imp@bsdimp.com> <20080223123556.3eee709d@bhuda.mired.org> <20080223.110047.-397883947.imp@bsdimp.com> <20080223131937.182373b2@bhuda.mired.org> <20080223214913.GE39699@lor.one-eyed-alien.net> Organization: Meyer Consulting X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.12; amd64-portbld-freebsd6.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAG1BMVEXguIzRkGnhyaz069mXhW0WHRnbrnR9WCQ6LB0CchNMAAACSUlEQVQ4jV2TQW7jMAxFGaPQOgQEdZaGMsgBrAvUA03dCxj1Uu4U2gfwQD7AGNax51NK07RcxXz6/CSl0Ij450vkPG1jzpIZM1UwDCl/xB14TWnNX8A00Qj5a0mnVFVbVUz4MeErea2HikSRqZzY894zwg9p2+/AtO8LzxFED+tNAUFeU29iFOLRxlZAcdo9A8wi8ZBMV4BKPde82Oxrvs6BTkulQIClte0DLFzzsKk9j1MBex8iUaP00Bd78S/muyFScrTXz6zLkEUxJp+SabQfNOs4f4Jpx5qSZ/304PWwlEWP1cOn/mJQR7EOD+uKhjcBLziuL7xoY5Xm+VFAUSw/LwwwsHEHxihpwV4EJH0xXRkbw1PkRw+X4pEuSJwBggqk+HEYKkiL5/74/nQkogigzQsAFrakxZyfw3wMIEEZPv4AWMfxwqE5GNxGaERjmH+PG8AE0L4/w9g0lsp1raLYAN5azQa+AOoO9NwcpFkTrG2VKNMNEL5UKUUAw34tha0z7onUG0oBoNtczE04GwFE3wCHc0ChezAJ6A1WMV81AtY7wDAJSlXwV+4cwBvsOsrQMRawfQEBz0deEZ7WNpV2szckIKo5VpDHDSDvF1GItwqqAlG01Hh50BGtVhuUkjkasg/14bYFGCgWg1fSWHvmOoJck2xdp9ZvZBHzDVTzX23TkrOn7qe5U2COEw5D4Vx3qEQpFY2Z/3QFnJxzp7YCmSMG19nOUoe869zZfOQb5ywQuWu0yCn5+8gxZz+BE7vG3j4/wbf4D/sXN9Wug1s7AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Delivery-Agent: TMDA/1.1.11 (Ladyburn) From: Mike Meyer Subject: Re: find -lname and -ilname implemented 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, 24 Feb 2008 00:28:02 -0000 On Sat, 23 Feb 2008 15:49:13 -0600 Brooks Davis wrote: > On Sat, Feb 23, 2008 at 01:19:37PM -0500, Mike Meyer wrote: > > On Sat, 23 Feb 2008 11:00:47 -0700 (MST) "M. Warner Losh" wrote: > > While I understand that it's easier to fix the BSD find, have you > > tried filing bug reports with patches for the tools that assume GNU > > find? That would help people outside the BSD community as well. > I think you may underestimate the value of compatibility. For example, I > think a lot of the successes bsdtar is having are due to the fact that > it's as much of a dropin replacement for gnutar is possible. If we want > to increase our market share one of the ways we can do it is to make > things easier for people who are interested in adopting our technologies > for what ever reason. If we can spend a few KB here and there to make > their transition easier, I think it's well worth it. If anything, what I'm miss-estimating is the value of a quality implementation, and ranking it to high. I have a long history of choosing things based on technical excellence rather than popularity, and the closet full of orphans to prove it. In particular, given the choice between a tool becoming useless because it's become an unsupported orphan, or having it become useless because the developers started choosing popularity over quality (and I've seen that happen as well), I'll take the former every time. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 06:58:51 2008 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 8BABF16A403 for ; Sun, 24 Feb 2008 06:58:51 +0000 (UTC) (envelope-from tim1timau@yahoo.com) Received: from web50310.mail.re2.yahoo.com (web50310.mail.re2.yahoo.com [206.190.38.243]) by mx1.freebsd.org (Postfix) with SMTP id 5579613C442 for ; Sun, 24 Feb 2008 06:58:51 +0000 (UTC) (envelope-from tim1timau@yahoo.com) Received: (qmail 92462 invoked by uid 60001); 24 Feb 2008 06:58:50 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=jXhFq6KLBz9uJQ6vH6mg3iXqqRI3M6ZWaYmshzHv0Q7LtooX0d1lURSphncePvlKxQl9O+r+bePZM9vNW28lGesFz4aKptS7M7VUYmED96gm2KcL9zy95Q9wuhQzrPN9J2WnY8f7kibaoFNSjyVehJDgqyyJr2Gn9Tl6AXzz9U4=; X-YMail-OSG: hkm2SUYVM1lpXIerLpNnie6e6J8pF6nUgH.Z6SH4ITRVN5nBzFxi2GsS.BEiRefkCJY8DFmKxQNZGh8Mqtp_UI3YbGJ7pTBXqa0Dl2b7GYD5RZUz3fP4Ll9edYZ3nKJrcp8SijZXYp_GoQc9BsEZ3V7ygQ-- Received: from [210.215.149.194] by web50310.mail.re2.yahoo.com via HTTP; Sat, 23 Feb 2008 22:58:50 PST Date: Sat, 23 Feb 2008 22:58:50 -0800 (PST) From: Tim Clewlow To: hackers@freebsd.org In-Reply-To: <47C0AD9D.2070701@andric.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <257786.91158.qm@web50310.mail.re2.yahoo.com> Cc: Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 24 Feb 2008 06:58:51 -0000 --- Dimitry Andric wrote: > On 2008-02-23 02:08, Atom Smasher wrote: > > article below. does anyone know how this affects eli/geli? > > > > from the geli man page: "detach - Detach the given providers, which means > > remove the devfs entry and clear the keys from memory." does that mean > > that geli properly wipes keys from RAM when a laptop is turned off? > > This is a physical attack, and there's nothing you can do in software to > prevent it. Of course geli or other software can attempt to erase the > keys from RAM as soon as it's done using them, but it won't prevent > hijacking them beforehand. > > It's the same with all physical attacks: hardware sniffers, keyloggers, > TEMPEST, etc. You need physical (hardware) protection to secure > against these, not software. The cracking method relies on the ability to find the key in memory, so, if the key is obfuscated then this would mean the cracking method could no longer find the key even if it has access to memory. For example, create a series of random bytes of equal length to the key, lets call that the "obfuscator". And now xor that with the key, lets call that the "xord key". To use the enc/dec system an extra step would need to xor back to the original key. The idea is that real key is only created when needed for use, and then immediately overwritten after use. If the "obfuscator" and the "xord key" are stored in memory at unpredictable locations, ie dont just have them sitting next to each other, then this would make it much more difficult to _find_ the key as it would now involve identifying two groups of randomly located (in memory) bytes that are xor'd to create the real key. Yes, with sufficient reverse engineering it would be possible to find out where the "obfuscator" and "xord key" have been stored, but this would at least stop the relatively trivial search method being used in the paper. Just a thought, and yes, I have now actually read the paper. Tim. ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 07:46:18 2008 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 E5DB516A400 for ; Sun, 24 Feb 2008 07:46:18 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.freebsd.org (Postfix) with ESMTP id 9948B13C465 for ; Sun, 24 Feb 2008 07:46:18 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail03.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m1O7kBfh029485 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 24 Feb 2008 18:46:13 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.1) with ESMTP id m1O7kBQ1098189; Sun, 24 Feb 2008 18:46:11 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m1O7kAmL098188; Sun, 24 Feb 2008 18:46:10 +1100 (EST) (envelope-from peter) Date: Sun, 24 Feb 2008 18:46:10 +1100 From: Peter Jeremy To: "M. Warner Losh" Message-ID: <20080224074610.GJ34425@server.vk2pj.dyndns.org> References: <20080223.120546.74701383.imp@bsdimp.com> <20080223155355.3f80b77f@bhuda.mired.org> <20080223220620.GH34425@server.vk2pj.dyndns.org> <20080223.165002.-1219417475.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4bRzO86E/ozDv8r1" Content-Disposition: inline In-Reply-To: <20080223.165002.-1219417475.imp@bsdimp.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-hackers@freebsd.org Subject: Re: find -lname and -ilname implemented 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, 24 Feb 2008 07:46:19 -0000 --4bRzO86E/ozDv8r1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 23, 2008 at 04:50:02PM -0700, M. Warner Losh wrote: >In message: <20080223220620.GH34425@server.vk2pj.dyndns.org> > Peter Jeremy writes: >: At the same, time, the find(1) man page needs to clearly distinguish >: between the parts of find that are POSIX-complaint, the parts that are >: GNU extensions and the parts that are [Free]BSD extensions. > >All the GNU extensions were flagged as such when I committed the man >page updates. I wrote my email before I saw that you had actually committed the changes. My comment was a general comment and was not intended as a slight on your man page changes. My apologies for any offence I may have inadvertently caused. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --4bRzO86E/ozDv8r1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHwSDC/opHv/APuIcRAtRiAJ9BtfBU6grIFFmfpfXAjbLBy7S6fQCeOLAA LCHSHtK8sOFM8KFAPGntJbg= =Mbu8 -----END PGP SIGNATURE----- --4bRzO86E/ozDv8r1-- From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 07:51:47 2008 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 B209E16A401 for ; Sun, 24 Feb 2008 07:51:47 +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 9175313C468 for ; Sun, 24 Feb 2008 07:51:47 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m1O7ntvM056732; Sun, 24 Feb 2008 00:49:55 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 24 Feb 2008 00:50:19 -0700 (MST) Message-Id: <20080224.005019.-1254318719.imp@bsdimp.com> To: peterjeremy@optushome.com.au From: "M. Warner Losh" In-Reply-To: <20080224074610.GJ34425@server.vk2pj.dyndns.org> References: <20080223220620.GH34425@server.vk2pj.dyndns.org> <20080223.165002.-1219417475.imp@bsdimp.com> <20080224074610.GJ34425@server.vk2pj.dyndns.org> 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: freebsd-hackers@freebsd.org Subject: Re: find -lname and -ilname implemented 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, 24 Feb 2008 07:51:47 -0000 In message: <20080224074610.GJ34425@server.vk2pj.dyndns.org> Peter Jeremy writes: : On Sat, Feb 23, 2008 at 04:50:02PM -0700, M. Warner Losh wrote: : >In message: <20080223220620.GH34425@server.vk2pj.dyndns.org> : > Peter Jeremy writes: : >: At the same, time, the find(1) man page needs to clearly distinguish : >: between the parts of find that are POSIX-complaint, the parts that are : >: GNU extensions and the parts that are [Free]BSD extensions. : > : >All the GNU extensions were flagged as such when I committed the man : >page updates. : : I wrote my email before I saw that you had actually committed the : changes. My comment was a general comment and was not intended as : a slight on your man page changes. My apologies for any offence I : may have inadvertently caused. No offense taken. I'm serious: if there's ways we can make find(1) better, I'm all ears. Warner From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 10:52:50 2008 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 35CAF16A400 for ; Sun, 24 Feb 2008 10:52:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by mx1.freebsd.org (Postfix) with ESMTP id 199AC13C467 for ; Sun, 24 Feb 2008 10:52:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by wf-out-1314.google.com with SMTP id 25so660365wfa.7 for ; Sun, 24 Feb 2008 02:52:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; bh=Wsv/f3/WOgRnarO9x1Aoe9JiUGJB76aL4xvyNDlMHcI=; b=OxNLnbCd/8Qt2g4UzflDJ47KvGtHXOrm0L7/honiEUOK6D9H4wHjwAsKu9PIrZ3p+zO0Hatc+wgeNozTTqjOOq0K4Ot8UaqdJnl0OXX2xE+O0ciBNUNvd1hnBQOAcXTObrUEExHlQPOsK+DWUBV5l63VUXB3nJMFc0svFLbYSQ0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=x7TU4jrUhUfW2mKEgJQVh6YdKeBv7jYdTf5UbSOzCK1oEo+t1bt3653OU75bN0ctlldCINi9ysUWyFruRlNANMS7/sxVUBmoXufKpV9h8zMxgSlZGoQBZsSacLzmgul4PMkvFanZY6fTxJozB+IQOJ9iTQag9XfqFGRymcKx9EM= Received: by 10.142.148.7 with SMTP id v7mr997151wfd.218.1203848764827; Sun, 24 Feb 2008 02:26:04 -0800 (PST) Received: by 10.143.125.7 with HTTP; Sun, 24 Feb 2008 02:26:04 -0800 (PST) Message-ID: Date: Sun, 24 Feb 2008 19:26:04 +0900 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: fb3a8dfa5a177185 Cc: Subject: Modular type GENERIC? 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, 24 Feb 2008 10:52:50 -0000 G'day, I was just wondering why we're not shipping a GENERIC type configuration that simply loads the modules at startup, rather than a statically linked kernel. I thought that was a large part of the push for the modular framework in years past. As a quick experiment, I trimmed all the modular devices out of RELENG_7 GENERIC into a "BASE" configuration file and filled /boot/loader.conf with modules relevant to my system. Everything booted just fine. How feasible do people think it would be to ship a "GENERIC" configuration which simply includes all the devices in a default module list, and users can select/deselect modules they wish to load? Here's the kernel and loader configuration files I'm using just on my system. I think acpi_load is a bit extraneous as acpi is included in the amd64 DEFAULTS. http://people.freebsd.org/~adrian/BASE.txt http://people.freebsd.org/~adrian/loader.conf -- Adrian Chadd - adrian@freebsd.org From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 14:29:51 2008 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 5859E16A404 for ; Sun, 24 Feb 2008 14:29:51 +0000 (UTC) (envelope-from atom@smasher.org) Received: from atom.smasher.org (atom.smasher.org [69.55.237.145]) by mx1.freebsd.org (Postfix) with SMTP id 2AF8613C4EE for ; Sun, 24 Feb 2008 14:29:51 +0000 (UTC) (envelope-from atom@smasher.org) Received: (qmail 23282 invoked by uid 1000); 24 Feb 2008 05:21:41 -0000 Message-ID: <20080224052141.23275.qmail@smasher.org> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Date: Sun, 24 Feb 2008 18:21:39 +1300 (NZDT) From: Atom Smasher In-Reply-To: <20080223131937.182373b2@bhuda.mired.org> MIME-Version: 1.0 OpenPGP: id=0xB88D52E4D9F57808; algo=1 (RSA); size=4096; url=http://atom.smasher.org/pgp.txt References: <20080222.225937.-146245356.imp@bsdimp.com> <20080223.000308.686168314.imp@bsdimp.com> <20080223123556.3eee709d@bhuda.mired.org> <20080223.110047.-397883947.imp@bsdimp.com> <20080223131937.182373b2@bhuda.mired.org> To: freebsd-hackers@freebsd.org X-POM: The Moon is Waning Gibbous (91% of Full) X-Hashcash: 1:20:0802240521:freebsd-hackers@freebsd.org::0OIjZZ6hi+xh8yhf:000000 0000000000000000000000003K35 Subject: Re: find -lname and -ilname implemented 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, 24 Feb 2008 14:29:51 -0000 On Sat, 23 Feb 2008, Mike Meyer wrote: > The problem with this argument is that there are no limits on it, other > than the developers definition of "trivial". OS X has already carried > this argument to the point that they've replaced /bin/sh with bash. ======================= i've seen that on linux, that /bin/sh is a symlink to /bin/bash and IMHO that's just wrong. otherwise, i think there's nothing wrong with adding functionality to 'find', as long as it doesn't break anything. a bash script that starts with '#!/bin/sh' is begging to break things (i filed a kde bug report about that; there was a bash-centric script that didn't work with sh), i can't think of a case that added functionality to find would break anything. i'm especially in favor of adding "unnecessary" functionality since i've recently been working on some core-install solaris boxes... the find function doesn't support 'maxdepth', the grep has no '-A', '-B' or '-C' options... i could go on, but the security requirements don't allow us to install gnu-find, gnu-grep, etc... if it doesn't break anything and it increases compatibility, i can't think of any reason to fight it. you seem opposed to the changes to find, but haven't cited any cases where the added functionality would be a problem. if we were to draw two columns on a piece of paper and label the columns "pro" and "con", then list consequences of the added functionality to find, we'd come up with a few things for the "pro" column... but you haven't really convinced me that anything needs to be added to the "con" column, except that you think it's not needed. -- ...atom ________________________ http://atom.smasher.org/ 762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808 ------------------------------------------------- "It really depends upon how our nation conducts itself in foreign policy. If we're an arrogant nation, they'll resent us. If we're a humble nation, but strong, they'll welcome us." -- George "dubya" Bush Bush-Gore debate, 11 Oct 2000 From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 14:34:06 2008 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 B119D16A404 for ; Sun, 24 Feb 2008 14:34:06 +0000 (UTC) (envelope-from atom@smasher.org) Received: from atom.smasher.org (atom.smasher.org [69.55.237.145]) by mx1.freebsd.org (Postfix) with SMTP id 6CDC013C455 for ; Sun, 24 Feb 2008 14:34:06 +0000 (UTC) (envelope-from atom@smasher.org) Received: (qmail 50098 invoked by uid 1000); 24 Feb 2008 05:32:56 -0000 Message-ID: <20080224053256.50097.qmail@smasher.org> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Date: Sun, 24 Feb 2008 18:32:54 +1300 (NZDT) From: Atom Smasher In-Reply-To: <20080223.120546.74701383.imp@bsdimp.com> MIME-Version: 1.0 OpenPGP: id=0xB88D52E4D9F57808; algo=1 (RSA); size=4096; url=http://atom.smasher.org/pgp.txt References: <20080223123556.3eee709d@bhuda.mired.org> <20080223.110047.-397883947.imp@bsdimp.com> <20080223131937.182373b2@bhuda.mired.org> <20080223.120546.74701383.imp@bsdimp.com> To: freebsd-hackers@freebsd.org X-POM: The Moon is Waning Gibbous (91% of Full) X-Hashcash: 1:20:0802240532:freebsd-hackers@freebsd.org::ZEHfyQqin9MiuuNy:000000 00000000000000000000000048hX Subject: Re: find -lname and -ilname implemented 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, 24 Feb 2008 14:34:06 -0000 On Sat, 23 Feb 2008, Warner Losh wrote: <> agree. > Or course, we may need to adopt features from bash into our /bin/sh as > time marches forward. =============== i'll disagree on this one. linux (that i've seen) uses a symlink from sh to bash. if you execute /bin/sh, it's running bash. if you write a script on linux and it works with /bin/sh it may not work with a "real" bourne shell. i've seen it in kde, where it seems most of the development is done on linux. when i saw it, i filed a bug report with a fix (to make the script compatible with bourne shell). in that case, the answer is to suggest that kde/linux do the right thing, not emulate them when they do the wrong thing. <> agree. -- ...atom ________________________ http://atom.smasher.org/ 762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808 ------------------------------------------------- "As soon as men decide that all means are permitted to fight an evil, then their good becomes indistinguishable from the evil that they set out to destroy." -- Christopher Dawson, The Judgment of Nations, 1942 From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 14:54:05 2008 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 18A4916A400 for ; Sun, 24 Feb 2008 14:54:05 +0000 (UTC) (envelope-from jonathan+freebsd-hackers@hst.org.za) Received: from hermes.hst.org.za (onix.hst.org.za [209.203.2.133]) by mx1.freebsd.org (Postfix) with ESMTP id 2B54313C469 for ; Sun, 24 Feb 2008 14:54:03 +0000 (UTC) (envelope-from jonathan+freebsd-hackers@hst.org.za) Received: from [10.1.11.1] ([10.1.11.1]) (authenticated bits=0) by hermes.hst.org.za (8.13.8/8.13.8) with ESMTP id m1OEjkRZ092991 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 24 Feb 2008 16:45:47 +0200 (SAST) (envelope-from jonathan+freebsd-hackers@hst.org.za) From: Jonathan McKeown To: freebsd-hackers@freebsd.org Date: Sun, 24 Feb 2008 16:54:17 +0200 User-Agent: KMail/1.9.4 References: <200802232322.45288.jonathan+freebsd-hackers@hst.org.za> <20080223.164806.-674897155.imp@bsdimp.com> In-Reply-To: <20080223.164806.-674897155.imp@bsdimp.com> MIME-Version: 1.0 Content-Disposition: inline X-Face: $@VrUx^RHy/}yu]jKf/<4T%/d|F+$j-Ol2"2J$q+%OK1]&/G_S9(=?iso-8859-1?q?HkaQ*=60!=3FYOK=3FY!=27M=60C=0A=09aP=5C9nVPF8Q=7DCilHH8l?= =?iso-8859-1?q?=3B=7E!42HK6=273lg4J=7Daz?=@1Dqqh:J]M^"YPn*2IWrZON$1+G?oX3@ =?iso-8859-1?q?k=230=0A=0954XDRg=3DYn=5FF-etwot4U=24b?=dTS{i X-Spam-Score: -4.399 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.61 on 209.203.2.133 Subject: Re: find -lname and -ilname implemented 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, 24 Feb 2008 14:54:05 -0000 On Sunday 24 February 2008 01:48, M. Warner Losh wrote: > The change absolutely makes sense, and so far none of the arguments > against it are really worth the time to respond to. I'm using > packages not in the ports system. Frankly, the more gratuitous > differences with the gnu tools we have, the harder the sell will be > for companies wanting to replace their Linux systems with FreeBSD > ones. The changes I made were absolutely trivial in the scheme of > things. > > This knee-jerk reaction against gnu find functionality baffles me. > The changes are trivial and make FreeBSD more compatible. It is such > an obvious no-brainer that I frankly didn't expect anybody to bat an > eye. You're adding some functions from GNU find which may or may not be currently available, and some synonyms for existing functionality to emulate GNU behaviour. You're right - that's reasonably unexceptionable, although it's by no means clear whether -lname name refers to the name of the link, as the revised manpage suggests (making it just an abbreviation for -name name -type l), or the name of the link's target, which is useful as there's currently no way to do that (I'm assuming that when DES tells me it does the latter, it's based on reading the source, which I haven't done). If you'd simply said that, I doubt you would have got much reaction at all. It was more the lengthy discussion of how we ``must'' be GNU-compatible, which prompted (certainly in my case) a philosophical discussion. Incidentally, while there are differences between the GNU tools and the BSD versions, I'm not sure (other than sheer weight of numbers) why that is judged to be a problem of ``gratuitous differences'' on the FreeBSD side, or why it is FreeBSD that must be ``more compatible'' with Linux rather than there being a mutual effort towards interoperability. Look at the find(1) manpage. It was already long, complex and intimidating. It's now a little longer to read, a little more complex to understand (do all these multiple options which appear to mean the same thing actually do different things, or not?), and a little more intimidating - and it's one of those manpages that people probably read over and over again (I know I often have to check the details of options for a complicated invocation). The gain is that we can now tell people not to worry about the fundamental differences between Linux and FreeBSD, because we've fixed a couple of trivial differences. Oh, and we've done it by adding marginally useful complexity to FreeBSD, which has always struck me as elegant and simple compared to the GNU/Linux kitchen-sink approach. FreeBSD and Linux are different. If it isn't the arguments to the find command that trip up potential converts, it'll be something else - unless we convert FreeBSD into Linux, at which point we can all go home. I'm sorry, I seem to be jumping up and down on you rather hard and in heavy boots over something quite minor. That's not my intention; but I would like to see a bit more discussion (perhaps in a more appropriate forum) about this more general issue: to what extent does the need for GNU compatibility override the desire for elegant and coherent design? Jonathan From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 14:59:40 2008 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 C1FD216A401 for ; Sun, 24 Feb 2008 14:59:40 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id A6FAB13C447 for ; Sun, 24 Feb 2008 14:59:40 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 8593C1CC033; Sun, 24 Feb 2008 06:59:40 -0800 (PST) Date: Sun, 24 Feb 2008 06:59:40 -0800 From: Jeremy Chadwick To: freebsd-hackers@freebsd.org Message-ID: <20080224145940.GA41037@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-09) Subject: loader and ficl/Forth help 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, 24 Feb 2008 14:59:40 -0000 So I've finally gotten around to attempting a feature I mentionted back in June 2007: using ASCII line-drawing characters for the borders around beastie/fbsdlogo in frames.4th: http://lists.freebsd.org/pipermail/freebsd-hackers/2007-June/020851.html I was hoping there might be some folks familiar with the existing Forth pieces in /boot who could help, since debugging this is incredibly difficult. This is my first time with Forth, which is probably where the true problem lies... My idea was to implement a loader_logo_lines loader variable, which you could set to "ascii" to achieve the desired effect -- but simultaneously retaining support for the PC98 character set, and the CP437 (IBM PC ANSI) set if the variable isn't defined, or is set to something it doesn't understand. So far I've managed to crash loader(8) doing the below, with the message "sh_el not found" from ficl on the serial console, then either an infinite register dump or an automatic reboot. I moved the PC98 and CP437 line constants into routines named pc98_lines and cp437_lines repectively, and made one called ascii_lines. The main code piece I changed in frames.4th became this: s" loader_logo_lines" getenv dup -1 = if drop s" arch-pc98" environment? if drop pc98_lines else drop cp437_lines then then 2dup s" ascii" compare-insensitive 0= if 2drop ascii_lines then 2drop cp437_lines I suspect this is what's broken, causing none of the routines to get executed, thus sh_el never gets defined. The version is here: http://jdc.parodius.com/freebsd/frames.4th.new -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 15:16:56 2008 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 6F5A916A402 for ; Sun, 24 Feb 2008 15:16:56 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.freebsd.org (Postfix) with ESMTP id E316B13C4D1 for ; Sun, 24 Feb 2008 15:16:55 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so480395uge.37 for ; Sun, 24 Feb 2008 07:16:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=hIArNVNz3SGLkU4EpNvFucYvwEQaUUnWfKsdagDZnOE=; b=q8e4pIOnQTaDmoqJr64CXqV8wq9Z6bA45YGLb+xjYGQ+bRimjmb/5sCIF/oF/KQ6X1isWHaHoNgOJ5FYyfWq8FBmNJ5xKmHWg/6KhWz6r825jswPIokjfgcupV5YgNCP71ebrVVwRtSbMBeLt+vRCyCYKQ5WvpiGs5AwUsyT0x4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=XI4KDIy17B5kQDc88xqnaXnLzOD/X9Iya+MhWDiG4tywTSABhH9DtU/E5wJ2dXhWWZWmo8HQ9/HgyTijXnUyYxkmM1v2sqVYSydFLOHjfhVo9ru3PUCrADAsUQvwKZMDM1Fg6gD3GdUth3pZ/sPOhhjNIq7Cgb87/yyVXZ5NdFg= Received: by 10.67.19.17 with SMTP id w17mr1866803ugi.33.1203866214935; Sun, 24 Feb 2008 07:16:54 -0800 (PST) Received: by 10.66.248.11 with HTTP; Sun, 24 Feb 2008 07:16:54 -0800 (PST) Message-ID: Date: Sun, 24 Feb 2008 15:16:54 +0000 From: "Igor Mozolevsky" Sender: mozolevsky@gmail.com To: "Bill Moran" In-Reply-To: <20080224100924.c8e08776.wmoran@collaborativefusion.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47C06E1F.5020308@thedarkside.nl> <760775.85636.qm@web50306.mail.re2.yahoo.com> <20080223203316.GC38485@lor.one-eyed-alien.net> <20080224100924.c8e08776.wmoran@collaborativefusion.com> X-Google-Sender-Auth: 535fb5d9fc51f832 Cc: hackers@freebsd.org Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 24 Feb 2008 15:16:56 -0000 On 24/02/2008, Bill Moran wrote: > "Igor Mozolevsky" wrote: > > > > On 23/02/2008, Brooks Davis wrote: > > > > > > > > You should actually read the paper. :) They successfully defeat both > > > of these type of protections by using canned air to chill the ram and > > > transplanting it into another machine. > > > > Easy to get around this attack - store the key on a usb > > stick/cd/whatever and every time the OS needs to access the encrypted > > date the key should be read, data decrypted, then key wiped from the > > memory; or have the daemon erase the key from memory every T minutes > > and re-acquire the key at next access attempt... > > > This is only effective if the sensitive data is infrequently accessed. > If the unit is asleep, then software isn't running and it's not possible > to kick of a timer to clear the memory, so it doesn't even start to > solve that problem. IMO the possibility of such attack is so remote that it doesn't really warrant any special attention, it's just something that should be kept in mind when writing "secure" crypto stuff... From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 15:19:30 2008 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 7B26316A402 for ; Sun, 24 Feb 2008 15:19:30 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 2D77413C457 for ; Sun, 24 Feb 2008 15:19:29 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from working (c-71-60-127-199.hsd1.pa.comcast.net [71.60.127.199]) (AUTH: LOGIN wmoran, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Sun, 24 Feb 2008 10:09:25 -0500 id 0005641D.47C188A5.00012960 Date: Sun, 24 Feb 2008 10:09:24 -0500 From: Bill Moran To: "Igor Mozolevsky" Message-Id: <20080224100924.c8e08776.wmoran@collaborativefusion.com> In-Reply-To: References: <47C06E1F.5020308@thedarkside.nl> <760775.85636.qm@web50306.mail.re2.yahoo.com> <20080223203316.GC38485@lor.one-eyed-alien.net> Organization: Collaborative Fusion Inc. X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 24 Feb 2008 15:19:30 -0000 "Igor Mozolevsky" wrote: > > On 23/02/2008, Brooks Davis wrote: > > > > > You should actually read the paper. :) They successfully defeat both > > of these type of protections by using canned air to chill the ram and > > transplanting it into another machine. > > Easy to get around this attack - store the key on a usb > stick/cd/whatever and every time the OS needs to access the encrypted > date the key should be read, data decrypted, then key wiped from the > memory; or have the daemon erase the key from memory every T minutes > and re-acquire the key at next access attempt... This is only effective if the sensitive data is infrequently accessed. If the unit is asleep, then software isn't running and it's not possible to kick of a timer to clear the memory, so it doesn't even start to solve that problem. > Or you could carry something that emits a huge EMI pulse to destroy > the data on the disk... Or laptop vendors could make "secure" laptops that always lose memory on shutdown. There are a number of vendors out there who make so-called "secure" laptops (hell, even the new Lenovos brag of security with their fingerprint readers). I wonder if they tested different hardware ... i.e. if some laptops are more vulnerable than others, or even some laptop hardware is _not_ vulnerable at all? I'm also disappointed that they took the tack of calling this a "software" problem and investigating so many different softwares. They should have identified it as a limitation of the hardware and tested different hardware. -- Bill Moran Collaborative Fusion Inc. wmoran@collaborativefusion.com Phone: 412-422-3463x4023 From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 16:30:01 2008 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 7418A16A400 for ; Sun, 24 Feb 2008 16:30:01 +0000 (UTC) (envelope-from chris@arnold.se) Received: from mailstore.infotropic.com (mailstore.infotropic.com [213.136.34.3]) by mx1.freebsd.org (Postfix) with ESMTP id A0D6713C46A for ; Sun, 24 Feb 2008 16:30:00 +0000 (UTC) (envelope-from chris@arnold.se) Received: (qmail 41736 invoked by uid 89); 24 Feb 2008 16:03:18 -0000 Received: by simscan 1.2.0 ppid: 41731, pid: 41733, t: 0.1040s scanners: attach: 1.2.0 clamav: 0.90/m:42 Received: from unknown (HELO ?192.168.123.123?) (chris@arnold.se@82.182.86.134) by mailstore.infotropic.com with ESMTPA; 24 Feb 2008 16:03:18 -0000 Date: Sun, 24 Feb 2008 17:03:17 +0100 (CET) From: Christopher Arnold X-X-Sender: chris@localhost To: hackers@freebsd.org In-Reply-To: <20080224100924.c8e08776.wmoran@collaborativefusion.com> Message-ID: <20080224165956.X34646@localhost> References: <47C06E1F.5020308@thedarkside.nl> <760775.85636.qm@web50306.mail.re2.yahoo.com> <20080223203316.GC38485@lor.one-eyed-alien.net> <20080224100924.c8e08776.wmoran@collaborativefusion.com> X-message-flag: =?ISO-8859-1?Q?Outlook_isn=B4t_compliant_with_current_standards?= =?ISO-8859-1?Q?_please_install_another_mail_client!?= MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 24 Feb 2008 16:30:01 -0000 On Sun, 24 Feb 2008, Bill Moran wrote: > Or laptop vendors could make "secure" laptops that always lose memory > on shutdown. > That dosn't really change anything, just don't shutdown the laptop. Cut an opening in the case and attach a probe to monitor memory access and wait for the key being accessed. /Chris -- http://www.arnold.se/ From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 17:33:31 2008 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 550EF16A403 for ; Sun, 24 Feb 2008 17:33:31 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id F3AC313C45A for ; Sun, 24 Feb 2008 17:33:30 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from working (c-71-60-127-199.hsd1.pa.comcast.net [71.60.127.199]) (AUTH: LOGIN wmoran, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Sun, 24 Feb 2008 12:33:29 -0500 id 0005641F.47C1AA69.00013C3A Date: Sun, 24 Feb 2008 12:33:28 -0500 From: Bill Moran To: "Igor Mozolevsky" Message-Id: <20080224123328.a0a85d7c.wmoran@collaborativefusion.com> In-Reply-To: References: <47C06E1F.5020308@thedarkside.nl> <760775.85636.qm@web50306.mail.re2.yahoo.com> <20080223203316.GC38485@lor.one-eyed-alien.net> <20080224100924.c8e08776.wmoran@collaborativefusion.com> Organization: Collaborative Fusion Inc. X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 24 Feb 2008 17:33:31 -0000 "Igor Mozolevsky" wrote: > > On 24/02/2008, Bill Moran wrote: > > "Igor Mozolevsky" wrote: > > > > > > On 23/02/2008, Brooks Davis wrote: > > > > > > > > > > > You should actually read the paper. :) They successfully defeat both > > > > of these type of protections by using canned air to chill the ram and > > > > transplanting it into another machine. > > > > > > Easy to get around this attack - store the key on a usb > > > stick/cd/whatever and every time the OS needs to access the encrypted > > > date the key should be read, data decrypted, then key wiped from the > > > memory; or have the daemon erase the key from memory every T minutes > > > and re-acquire the key at next access attempt... > > > > > > This is only effective if the sensitive data is infrequently accessed. > > If the unit is asleep, then software isn't running and it's not possible > > to kick of a timer to clear the memory, so it doesn't even start to > > solve that problem. > > IMO the possibility of such attack is so remote that it doesn't really > warrant any special attention, it's just something that should be kept > in mind when writing "secure" crypto stuff... Then you're not using this to protect data of a particular sensitive nature, or you're being a fool. Fact is, data is "sensitive" to different degrees. It's also valuable to different degrees. If you're worried about your personal financial information on your laptop being stolen, then modern disk encryption is fine. But, if you've got a mobile device with the sensitive information from 1000s of people on it, the stakes are different. That device is liable to be the target of an attack specifically to get the _data_. You're correct in 90% of the cases, but there's still the 10% that some of us need to consider. The fact is that the attack is not difficult, and it's not a matter of whether or not someone _can_ bypass your disk encryption, it's more a matter of whether or not they actually care enough to bother, or whether the $$$ they can get for the stolen hardware alone will satisfy them. Each user/organization really needs to evaluate this information with regards to their own situation, but it's important to understand the details of the risk when making such a decision. -- Bill Moran Collaborative Fusion Inc. wmoran@collaborativefusion.com Phone: 412-422-3463x4023 From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 17:38:41 2008 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 6AC3D16A400; Sun, 24 Feb 2008 17:38:41 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id B8D7D13C448; Sun, 24 Feb 2008 17:38:40 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m1OHccpR031634; Sun, 24 Feb 2008 18:38:39 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m1OHccfW031633; Sun, 24 Feb 2008 18:38:38 +0100 (CET) (envelope-from olli) Date: Sun, 24 Feb 2008 18:38:38 +0100 (CET) Message-Id: <200802241738.m1OHccfW031633@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, koitsu@FreeBSD.ORG In-Reply-To: <20080224145940.GA41037@eos.sc1.parodius.com> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Sun, 24 Feb 2008 18:38:39 +0100 (CET) Cc: Subject: Re: loader and ficl/Forth help X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, koitsu@FreeBSD.ORG List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Feb 2008 17:38:41 -0000 Jeremy Chadwick wrote: > So I've finally gotten around to attempting a feature I mentionted back > in June 2007: using ASCII line-drawing characters for the borders around > beastie/fbsdlogo in frames.4th: > > http://lists.freebsd.org/pipermail/freebsd-hackers/2007-June/020851.html > > I was hoping there might be some folks familiar with the existing Forth > pieces in /boot who could help, since debugging this is incredibly > difficult. This is my first time with Forth, which is probably where > the true problem lies... There's a debugging aid called "testmain" so you can run Forth code interactively in multi-user mode for testing purposes. For details please read the thread starting here: http://lists.freebsd.org/pipermail/freebsd-stable/2005-May/015387.html Personally I use qemu for testing loader things. I wrote a trivial script that updates a small disk image and then boot its in qemu, which only takes two or three seconds, so testing cycles are pretty short. > My idea was to implement a loader_logo_lines loader variable, which you > could set to "ascii" to achieve the desired effect -- but simultaneously > retaining support for the PC98 character set, and the CP437 (IBM PC > ANSI) set if the variable isn't defined, or is set to something it > doesn't understand. I suggest you switch to ASCII characters automatically if the loader is running on comconsole (i.e. serial), and use CP437 it it is running on vidconsole (i.e. VGA). Then there will be no need to manually switch a variable. > So far I've managed to crash loader(8) doing the below, with the message > "sh_el not found" from ficl on the serial console, then either an > infinite register dump or an automatic reboot. > > I moved the PC98 and CP437 line constants into routines named pc98_lines > and cp437_lines repectively, and made one called ascii_lines. The main > code piece I changed in frames.4th became this: > > s" loader_logo_lines" getenv > dup -1 = if > drop > s" arch-pc98" environment? if > drop > pc98_lines > else > drop > cp437_lines > then > then > 2dup s" ascii" compare-insensitive 0= if > 2drop > ascii_lines > then > 2drop > cp437_lines I think the stack layout is not correct, particularly the drops aren't quite right in some branches of the "if" statements, I think. It's best to make a stack diagram on paper and go through all possible branches with it. The following snippet should work better, but I have't actually tried it myself, so it's just theory. s" loader_logo_lines" getenv dup -1 = if drop s" arch-pc98" environment? if drop pc98_lines else cp437_lines then else s" ascii" compare-insensitive 0= if ascii_lines else cp437_lines then then Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Emacs ist für mich kein Editor. Für mich ist das genau das gleiche, als wenn ich nach einem Fahrrad (für die Sonntagbrötchen) frage und einen pangalaktischen Raumkreuzer mit 10 km Gesamtlänge bekomme. Ich weiß nicht, was ich damit soll." -- Frank Klemm, de.comp.os.unix.discussion From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 17:44:09 2008 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 8D92416A400 for ; Sun, 24 Feb 2008 17:44:09 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from smtp.ht-systems.ru (mr0.ht-systems.ru [78.110.50.55]) by mx1.freebsd.org (Postfix) with ESMTP id DB7C913C4E3 for ; Sun, 24 Feb 2008 17:44:08 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from [78.110.49.49] (helo=quasar.ht-systems.ru) by smtp.ht-systems.ru with esmtpa (Exim 4.62) (envelope-from ) id 1JTKOK-0000fL-72; Sun, 24 Feb 2008 20:11:56 +0300 Received: by quasar.ht-systems.ru (Postfix, from userid 1024) id 255BA7D11C3; Sun, 24 Feb 2008 20:11:55 +0300 (MSK) Date: Sun, 24 Feb 2008 20:11:55 +0300 From: Stanislav Sedov To: "M. Warner Losh" Message-ID: <20080224171155.GD51827@dracon.ht-systems.ru> References: <20080222.225937.-146245356.imp@bsdimp.com> <20080223.000308.686168314.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080223.000308.686168314.imp@bsdimp.com> Organization: The FreeBSD Project X-Voice: +7 916 849 20 23 X-XMPP: ssedov@jabber.ru X-Yahoo: stanislav_sedov X-PGP-Fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 X-University: MEPhI X-Mailer: carrier-pigeon X-Operating-System: FreeBSD quasar.ht-systems.ru 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE Cc: hackers@freebsd.org Subject: Re: find -lname and -ilname implemented 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, 24 Feb 2008 17:44:09 -0000 On Sat, Feb 23, 2008 at 12:03:08AM -0700 M. Warner Losh mentioned: > > Comments? > > Warner > > Index: find.1 > =================================================================== > RCS file: /cache/ncvs/src/usr.bin/find/find.1,v > retrieving revision 1.82 > diff -u -r1.82 find.1 > --- find.1 28 Feb 2007 10:19:25 -0000 1.82 > +++ find.1 23 Feb 2008 06:53:39 -0000 > @@ -293,6 +293,12 @@ > Please refer to the > .Ic -atime > primary description for information on supported time units. > +.It Ic -d > +Same as > +.Ic depth . > +Gnu find implements this as a primary in mistaken emulation of Should be, probably, spelled as GNU, it's an abbrev. > +.Fx > +.Xr find 1 . > .It Ic -delete > Delete found files and/or directories. > Always returns true. > @@ -365,6 +371,15 @@ > the string > .Dq Li {} > is not qualified. > +.It Ic -execdir Ar utility Oo Ar argument ... Oc Li {} + > +Same as > +.Ic -execdir , > +except that > +.Dq Li {} > +is replaced with as many pathnames as possible for each invocation of > +.Ar utility . > +This behaviour is similar to that of > +.Xr xargs 1 . > .It Ic -flags Oo Cm - Ns | Ns Cm + Oc Ns Ar flags , Ns Ar notflags > The flags are specified using symbolic names (see > .Xr chflags 1 ) . > @@ -436,6 +451,10 @@ > is numeric and there is no such group name, then > .Ar gname > is treated as a group ID. > +.It Ic -ilname Ar pattern > +Like > +.Ic -lname , > +but the match is case insensitive. > .It Ic -iname Ar pattern > Like > .Ic -name , > @@ -451,10 +470,18 @@ > Like > .Ic -regex , > but the match is case insensitive. > +.It Ic -iwholename Ar pattern > +The same thing as > +.Ic -ipath , > +for Gnu find compatibility. The same. > .It Ic -links Ar n > True if the file has > .Ar n > links. > +.It Ic -lname Ar pattern > +Like > +.Ic -name , > +but the matched file must also be a symbolic link. > .It Ic -ls > This primary always evaluates to true. > The following information for the current file is written to standard output: > @@ -497,6 +524,10 @@ > .It Ic -mnewer Ar file > Same as > .Ic -newer . > +.It Ic -mount > +The same thing as > +.Ic -xdev , > +for Gnu find compatibility. GNU? > .It Ic -mtime Ar n Ns Op Cm smhdw > If no units are specified, this primary evaluates to > true if the difference between the file last modification time and the time > @@ -747,6 +778,10 @@ > is numeric and there is no such user name, then > .Ar uname > is treated as a user ID. > +.It Ic -wholename Ar pattern > +The same thing as > +.Ic -path , > +for Gnu find compatibility. Similar. > @@ -1353,7 +1357,7 @@ > return new; > } > > -/* c_simple covers c_prune, c_openparen, c_closeparen, c_not, c_or */ > +/* c_simple covers c_prune, c_openparen, c_closeparen, c_not, c_or, c_true, c_false */ > As the result of modification the line now exceeds 80 characters, which is, obviously, bad. > Index: option.c > =================================================================== > RCS file: /cache/ncvs/src/usr.bin/find/option.c,v > retrieving revision 1.25 > diff -u -r1.25 option.c > --- option.c 5 Apr 2006 23:06:11 -0000 1.25 > +++ option.c 23 Feb 2008 06:57:54 -0000 > @@ -58,6 +58,7 @@ > int typecompare(const void *, const void *); > > /* NB: the following table must be sorted lexically. */ > +/* Options listed with C++ comments are in gnu find, but not our find */ Please, don't commit C++ comments, that violates style(9). Also, gnu should be spelled as GNU. > static OPTION const options[] = { > { "!", c_simple, f_not, 0 }, > { "(", c_simple, f_openparen, 0 }, > @@ -74,26 +75,38 @@ > { "-cmin", c_Xmin, f_Xmin, F_TIME_C }, > { "-cnewer", c_newer, f_newer, F_TIME_C }, > { "-ctime", c_Xtime, f_Xtime, F_TIME_C }, > + { "-d", c_depth, f_depth, 0 }, > +// -daystart > { "-delete", c_delete, f_delete, 0 }, > { "-depth", c_depth, f_depth, 0 }, Why to add just a shortcut for already existent -depth option? It makes the utility much complex, but don't add value at all. > { "-empty", c_empty, f_empty, 0 }, > { "-exec", c_exec, f_exec, 0 }, > { "-execdir", c_exec, f_exec, F_EXECDIR }, > - { "-false", c_simple, f_not, 0 }, > + { "-false", c_simple, f_false, 0 }, This brakes FreeBSD compatiblity in the favor of GNU. What will old FreeBSD user think when his scripts will stop working after next cvsup? I suppose our target not to make FreeBSD to look like Linux. If you want to add GNU-like false option, please, add it under the different name. > { "-flags", c_flags, f_flags, 0 }, > +// -fls > { "-follow", c_follow, f_always_true, 0 }, > +// -fprint > +// -fprint0 > +// -fprintf > { "-fstype", c_fstype, f_fstype, 0 }, > +// -gid > { "-group", c_group, f_group, 0 }, > +// -ignore_readdir_race > + { "-ilname", c_name, f_name, F_LINK | F_IGNCASE }, > { "-iname", c_name, f_name, F_IGNCASE }, > { "-inum", c_inum, f_inum, 0 }, > { "-ipath", c_name, f_path, F_IGNCASE }, > { "-iregex", c_regex, f_regex, F_IGNCASE }, > + { "-iwholename",c_name, f_path, F_IGNCASE }, No space between "-iwholename" and c_name. Also, just a shortcut to -ipath. Also, -iname is much shorter. > { "-links", c_links, f_links, 0 }, > + { "-lname", c_name, f_name, F_LINK }, > { "-ls", c_ls, f_ls, 0 }, > { "-maxdepth", c_mXXdepth, f_always_true, F_MAXDEPTH }, > { "-mindepth", c_mXXdepth, f_always_true, 0 }, > { "-mmin", c_Xmin, f_Xmin, 0 }, > { "-mnewer", c_newer, f_newer, 0 }, > + { "-mount", c_xdev, f_always_true, 0 }, SHortuct to -xdev. Again, much longer one. > { "-mtime", c_Xtime, f_Xtime, 0 }, > { "-name", c_name, f_name, 0 }, > { "-newer", c_newer, f_newer, 0 }, > @@ -118,6 +131,8 @@ > { "-newermm", c_newer, f_newer, 0 }, > { "-newermt", c_newer, f_newer, F_TIME2_T }, > { "-nogroup", c_nogroup, f_nogroup, 0 }, > +// -noignore_readdir_race > +// -noleaf > { "-not", c_simple, f_not, 0 }, > { "-nouser", c_nouser, f_nouser, 0 }, > { "-o", c_simple, f_or, 0 }, > @@ -128,12 +143,19 @@ > { "-perm", c_perm, f_perm, 0 }, > { "-print", c_print, f_print, 0 }, > { "-print0", c_print, f_print0, 0 }, > +// -printf > { "-prune", c_simple, f_prune, 0 }, > +// -quit > { "-regex", c_regex, f_regex, 0 }, > +// -samefile > { "-size", c_size, f_size, 0 }, > + { "-true", c_simple, f_always_true, 0 }, > { "-type", c_type, f_type, 0 }, > +// -uid n > { "-user", c_user, f_user, 0 }, > + { "-wholename", c_name, f_path, 0 }, Wouldn't be "-path" better? > { "-xdev", c_xdev, f_always_true, 0 }, > +// -xtype > }; > > /* Warner, I fully understand your intention to make FreeBSD more compatible with GNU, but FreeBSD Project historically had much more important target - to make a clean designed and not bloated system. I'll be happy to see new useful options added to find, but in case they isn't just shortcuts to existing ones and don't break existing functionality. If'll take a direction to become a Linux one day - we'll certainly loose. There'a lot of examples of this in history - I don't want to make the same mistake. It's quite common for BSD and GNU world to make different desicions on design of their systems. That's pretty normal. BSD people tend to prefer a clean and simple design, where duplication is a bad thing, where GNU people prefer to implement every possible functionality in their programs. Linux camp - is 'just works' camp, where BSD - 'works perfectly' camp. I understand, that you want to attract more people from the GNU/Linux camp to FreeBSD. But think - people go from Linux to FreeBSD for a reason, a reason they want a more clean and simple disigned system, perfect system, where good design - is the first, and everything another - the last. If we'll take the GNU way - what will be the reason for them to go for FreeBSD? -- Stanislav Sedov ST4096-RIPE From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 17:44:10 2008 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 B085B16A401 for ; Sun, 24 Feb 2008 17:44:10 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from smtp.ht-systems.ru (mr0.ht-systems.ru [78.110.50.55]) by mx1.freebsd.org (Postfix) with ESMTP id 584FA13C4E5 for ; Sun, 24 Feb 2008 17:44:10 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from [78.110.49.49] (helo=quasar.ht-systems.ru) by smtp.ht-systems.ru with esmtpa (Exim 4.62) (envelope-from ) id 1JTKar-0000hq-G3; Sun, 24 Feb 2008 20:24:53 +0300 Received: by quasar.ht-systems.ru (Postfix, from userid 1024) id 6B68C7D11C3; Sun, 24 Feb 2008 20:24:52 +0300 (MSK) Date: Sun, 24 Feb 2008 20:24:52 +0300 From: Stanislav Sedov To: Deomid Ryabkov Message-ID: <20080224172452.GE51827@dracon.ht-systems.ru> References: <4503B525.4040800@rojer.pp.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4503B525.4040800@rojer.pp.ru> Organization: The FreeBSD Project X-Voice: +7 916 849 20 23 X-XMPP: ssedov@jabber.ru X-Yahoo: stanislav_sedov X-PGP-Fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 X-University: MEPhI X-Mailer: carrier-pigeon X-Operating-System: FreeBSD quasar.ht-systems.ru 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE Cc: freebsd-hackers@freebsd.org Subject: Re: VM design doc? 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, 24 Feb 2008 17:44:10 -0000 On Sat, Sep 09, 2006 at 11:48:05PM -0700 Deomid Ryabkov mentioned: > Having noted that with time my understanding of how VM works in FreeBSD > has somewhat blurred (not to say that it was ever complete), > I reckoned it's time to go and read up on it. > > Thus I wonder, what relevance the "Design elements of the FreeBSD VM system" > (http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vm-design/index.html) > article has to both -CURRENT and -STABLE? > Were there notable changes not mentioned in the article? > Is there a better document on FreeBSD's current VM? > I'm not an expert in this field, but AFAIK the main design principles of the VM subsystem remain. For further study I afraid you need to go for the source code (sys/vm and sys/kern). Also, McKusick book on FreeBSD, might be helpful too. -- Stanislav Sedov ST4096-RIPE From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 17:51:40 2008 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 7E17116A402 for ; Sun, 24 Feb 2008 17:51:40 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 11A7013C448 for ; Sun, 24 Feb 2008 17:51:39 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from working (c-71-60-127-199.hsd1.pa.comcast.net [71.60.127.199]) (AUTH: LOGIN wmoran, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Sun, 24 Feb 2008 12:51:39 -0500 id 0005642C.47C1AEAB.00013E2E Date: Sun, 24 Feb 2008 12:51:38 -0500 From: Bill Moran To: Christopher Arnold Message-Id: <20080224125138.b56cab48.wmoran@collaborativefusion.com> In-Reply-To: <20080224165956.X34646@localhost> References: <47C06E1F.5020308@thedarkside.nl> <760775.85636.qm@web50306.mail.re2.yahoo.com> <20080223203316.GC38485@lor.one-eyed-alien.net> <20080224100924.c8e08776.wmoran@collaborativefusion.com> <20080224165956.X34646@localhost> Organization: Collaborative Fusion Inc. X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 24 Feb 2008 17:51:40 -0000 Christopher Arnold wrote: > > > > On Sun, 24 Feb 2008, Bill Moran wrote: > > > Or laptop vendors could make "secure" laptops that always lose memory > > on shutdown. > > > That dosn't really change anything, just don't shutdown the laptop. It reduces the risk greatly when combined with other measures. For example, alter the sysctls so the lid switch powers the laptop off instead of putting it to sleep. This changes the scene a good bit, as it's guaranteed to be powered off when in storage and transport, which is when it is most likely to be stolen. > Cut an opening in the case and attach a probe to monitor memory access and > wait for the key being accessed. That attack only works if you can steal the laptop when it's powered on. With a unit known to be a security risk, it's going to be monitored while powered on, so it's less likely to be stolen at that time. As far as mitigation is concerned, there's not 1 or 0. But smart deployment can reduce the risks. -- Bill Moran Collaborative Fusion Inc. wmoran@collaborativefusion.com Phone: 412-422-3463x4023 From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 19:07:23 2008 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 64F0116A408 for ; Sun, 24 Feb 2008 19:07:23 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id 2A5BB13C457 for ; Sun, 24 Feb 2008 19:07:22 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: by wa-out-1112.google.com with SMTP id k17so1423101waf.3 for ; Sun, 24 Feb 2008 11:07:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=9FQYRISEXTda7j3DVOZgYM4hQMAbWvKX+ObdZ28Ovv4=; b=g6u04nOgbIHptKdTbLz/v8vd0EDarai2wONnr8FQ6qAaThxt9DR++0k8kClJ25DJTjHlAGkLZH3KfMUfR+U8Dn1Hfb60mZbJIwj8XWk5kck2XiKAlMdbHQaRUWLXlU99L6KhunptDKYLsAR5HnjzIGRU47NW0FLcCFLopu29hWk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=OUi+GG6ZeAOPKtB3MLU6CNc8+Pt07GsYEQdsxcU77aaGOLWzeS0ScSjwYPI2tyDnw6Mxb9G8HXeM3zuFRlAnWCHlkLz1C0bTj1IWvVaUiqxUgXYpLvLj0gfAXIHO6WAlwcLmVVzZhnhxV/Ly0FUCT4BSZscRaoyK7c6pHhMMyR4= Received: by 10.114.121.1 with SMTP id t1mr2288949wac.55.1203878521186; Sun, 24 Feb 2008 10:42:01 -0800 (PST) Received: by 10.115.33.6 with HTTP; Sun, 24 Feb 2008 10:42:01 -0800 (PST) Message-ID: <5a08be760802241042x2cd93d63of5787a744e745fe5@mail.gmail.com> Date: Sun, 24 Feb 2008 19:42:01 +0100 From: "cali clarke" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Anybody have a patch for pdksh derivatives, for jails? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Feb 2008 19:07:23 -0000 Hi. pdksh and derivatives (openbsd ksh, mirbsd mksh etc) all have the same "bug" with regards to jails. On all of my systems, trying to start *ksh in a jail results in a message that /dev/tty could not be opened (device busy) and that the shell will not have job control. For some reason, this makes pretty much any curses or screen editor fail to run. Note that also, this problem does NOT occur if you use ssh to enter the jail as I believe ssh handles tty allocation in advance. I wondered if anybody had patched their *ksh to workaround this problem? I've had a look at the sources myself and... ugh. The insides of a unix shell are not something I particularly want to spend much time examining... From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 19:46:08 2008 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 87BEA16A400; Sun, 24 Feb 2008 19:46:08 +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 188C713C459; Sun, 24 Feb 2008 19:46:08 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m1OJhDqM070672; Sun, 24 Feb 2008 12:43:13 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 24 Feb 2008 12:43:39 -0700 (MST) Message-Id: <20080224.124339.-1302545914.imp@bsdimp.com> To: stas@freebsd.org From: "M. Warner Losh" In-Reply-To: <20080224171155.GD51827@dracon.ht-systems.ru> References: <20080222.225937.-146245356.imp@bsdimp.com> <20080223.000308.686168314.imp@bsdimp.com> <20080224171155.GD51827@dracon.ht-systems.ru> 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: hackers@freebsd.org Subject: Re: find -lname and -ilname implemented 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, 24 Feb 2008 19:46:08 -0000 In message: <20080224171155.GD51827@dracon.ht-systems.ru> Stanislav Sedov writes: : Should be, probably, spelled as GNU, it's an abbrev. Actually, you are right, but for the wrong reason. GNU is an acronym, so should be all caps. : > -/* c_simple covers c_prune, c_openparen, c_closeparen, c_not, c_or */ : > +/* c_simple covers c_prune, c_openparen, c_closeparen, c_not, c_or, c_true, c_false */ : > : : As the result of modification the line now exceeds 80 characters, which is, obviously, bad. I have a couple of other places to clean up. : > Index: option.c : > =================================================================== : > RCS file: /cache/ncvs/src/usr.bin/find/option.c,v : > retrieving revision 1.25 : > diff -u -r1.25 option.c : > --- option.c 5 Apr 2006 23:06:11 -0000 1.25 : > +++ option.c 23 Feb 2008 06:57:54 -0000 : > @@ -58,6 +58,7 @@ : > int typecompare(const void *, const void *); : > : > /* NB: the following table must be sorted lexically. */ : > +/* Options listed with C++ comments are in gnu find, but not our find */ : : Please, don't commit C++ comments, that violates style(9). Also, gnu should be : spelled as GNU. Understood. Not that I'm going to change it, but understood. : > static OPTION const options[] = { : > { "!", c_simple, f_not, 0 }, : > { "(", c_simple, f_openparen, 0 }, : > @@ -74,26 +75,38 @@ : > { "-cmin", c_Xmin, f_Xmin, F_TIME_C }, : > { "-cnewer", c_newer, f_newer, F_TIME_C }, : > { "-ctime", c_Xtime, f_Xtime, F_TIME_C }, : > + { "-d", c_depth, f_depth, 0 }, : > +// -daystart : > { "-delete", c_delete, f_delete, 0 }, : > { "-depth", c_depth, f_depth, 0 }, : : Why to add just a shortcut for already existent -depth option? : It makes the utility much complex, but don't add value at all. Because it makes it more compatible with existing de-facto standards. It costs us very little to do so. : > { "-empty", c_empty, f_empty, 0 }, : > { "-exec", c_exec, f_exec, 0 }, : > { "-execdir", c_exec, f_exec, F_EXECDIR }, : > - { "-false", c_simple, f_not, 0 }, : > + { "-false", c_simple, f_false, 0 }, : : This brakes FreeBSD compatiblity in the favor of GNU. What will : old FreeBSD user think when his scripts will stop working : after next cvsup? I suppose our target not to make FreeBSD : to look like Linux. If you want to add GNU-like false option, : please, add it under the different name. I considered it, but rejected it. The current -false option doesn't make any sense at all, likely isn't used, is just a short-cut for '!' and had a very dubious justification when it was committed. : No space between "-iwholename" and c_name. : : Also, just a shortcut to -ipath. Also, -iname is much shorter. Again, for compatibility with existing scripts. I didn't pick the names here. : > { "-links", c_links, f_links, 0 }, : > + { "-lname", c_name, f_name, F_LINK }, : > { "-ls", c_ls, f_ls, 0 }, : > { "-maxdepth", c_mXXdepth, f_always_true, F_MAXDEPTH }, : > { "-mindepth", c_mXXdepth, f_always_true, 0 }, : > { "-mmin", c_Xmin, f_Xmin, 0 }, : > { "-mnewer", c_newer, f_newer, 0 }, : > + { "-mount", c_xdev, f_always_true, 0 }, : : SHortuct to -xdev. Again, much longer one. Agreed, but for compatibility with existing scripts... : Warner, I fully understand your intention to make FreeBSD more : compatible with GNU, but FreeBSD Project historically had much more : important target - to make a clean designed and not bloated : system. I'll be happy to see new useful options added to find, but : in case they isn't just shortcuts to existing ones and don't break : existing functionality. There's at least one that adds real, new functionality (-lname and -ilname). The minor breakage to FreeBSD users for -false likely will affect fewer people than the removal of the 'ie' driver. : If'll take a direction to become a Linux one day - we'll certainly : loose. There'a lot of examples of this in history - I don't want to : make the same mistake. It's quite common for BSD and GNU world to : make different desicions on design of their systems. That's pretty : normal. BSD people tend to prefer a clean and simple design, where : duplication is a bad thing, where GNU people prefer to implement : every possible functionality in their programs. Linux camp - is : 'just works' camp, where BSD - 'works perfectly' camp. It can be a tough judgment call here. While I generally favor cleanliness, there's also a lot of gain to be had with being compatible. : I understand, that you want to attract more people from the : GNU/Linux camp to FreeBSD. But think - people go from Linux to : FreeBSD for a reason, a reason they want a more clean and simple : disigned system, perfect system, where good design - is the first, : and everything another - the last. If we'll take the GNU way - what : will be the reason for them to go for FreeBSD? I think you miss my point. It certainly isn't to attract people from Linux to FreeBSD. Rather, it is to remove speed-bumps along the way if someone has already made that decision. There's also a fair number of tools out there that are using the GNU extensions. If it were one or two, I'd fix the tools. However, I keep stubbing my toe on these issues. In addition, many of these tools are moving to GPLv3 when they make relatively minor patches. This makes them harder to use and deploy. While one can tolerate GPLv3 software on one's development system, the deployed systems typically can't tolerate it at all. By making the BSD tools more compatible, they can more easily be dropped in to replace the GNU tools without having to redo one's scripts. Warner From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 20:03:06 2008 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 37AFD16A401 for ; Sun, 24 Feb 2008 20:03:06 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0625613C4E1 for ; Sun, 24 Feb 2008 20:03:05 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id E963F1CC033; Sun, 24 Feb 2008 12:03:05 -0800 (PST) Date: Sun, 24 Feb 2008 12:03:05 -0800 From: Jeremy Chadwick To: Oliver Fromme Message-ID: <20080224200305.GA49564@eos.sc1.parodius.com> References: <20080224145940.GA41037@eos.sc1.parodius.com> <200802241738.m1OHccfW031633@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200802241738.m1OHccfW031633@lurza.secnetix.de> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-hackers@freebsd.org Subject: Re: loader and ficl/Forth help 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, 24 Feb 2008 20:03:06 -0000 On Sun, Feb 24, 2008 at 06:38:38PM +0100, Oliver Fromme wrote: > There's a debugging aid called "testmain" so you can run > Forth code interactively in multi-user mode for testing > purposes. For details please read the thread starting > here: > > http://lists.freebsd.org/pipermail/freebsd-stable/2005-May/015387.html Thanks! This helps a lot. I'm able to reproduce the sh_el not found condition with testmain. > Personally I use qemu for testing loader things. I wrote > a trivial script that updates a small disk image and then > boot its in qemu, which only takes two or three seconds, > so testing cycles are pretty short. Hmm, interesting software. I'm used to VMware myself, but this seems a bit less bloated. I'd have to run it on Windows, since I don't use FreeBSD as a workstation (no SDL, no VNC/X, etc.). The FreeBSD box in my home runs Samba, so I should be able to set up a method of creating ISO images of FreeBSD, which I can then test via qemu on Windows via CIFS/SMB share... > I suggest you switch to ASCII characters automatically if > the loader is running on comconsole (i.e. serial), and use > CP437 it it is running on vidconsole (i.e. VGA). Then > there will be no need to manually switch a variable. Great idea; I think I'll go with that. > I think the stack layout is not correct, particularly the > drops aren't quite right in some branches of the "if" > statements, I think. It's best to make a stack diagram > on paper and go through all possible branches with it. I have a lot more reading to do on the subject of Forth. Stacks are hardly a new concept to me, but the conditions where Forth puts something onto the stack are. I've never worked with a language like this before (at least RPN doesn't frustrate me!). I've already found some reading material which should help. > s" loader_logo_lines" getenv > dup -1 = if > drop > s" arch-pc98" environment? if > drop > pc98_lines > else > cp437_lines > then > else > s" ascii" compare-insensitive 0= if > ascii_lines > else > cp437_lines > then > then Again, thanks -- I don't quite understand the changes yet, but will after I read aforementioned documents. Sadly, the "sh_el not found" error still continues with this code -- but it does fix the crashing I was seeing. I believe the problem is that constants cannot be put inside of a function (functions being runtime things, not compile-time things). Since the original code used compile-time conditions ([if], etc.), it meant that only one declaration for sh_el, sv_el, etc. was made. Since the *_lines functions are doing the assignments, I had to change them all to runtime, e.g.: 149 sh_el ! 150 sv_el ! And so on, ditto with adding "variable sh_el", "variable sv_el" and others to the very top of frames.4th. This actually fixed the "not found" error, and now I'm stuck with "Error: compile only!" being induced by the "dup -1 = if" line. The same happens when running this natively (outside of testmain). I'll have to get the qemu stuff set up so I can test this more easily. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 21:16:26 2008 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 032E816A401; Sun, 24 Feb 2008 21:16:26 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id 6885713C45A; Sun, 24 Feb 2008 21:16:25 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:Content-Transfer-Encoding:In-Reply-To:Sender:X-Spam-Status:Subject; b=F0H29h0qRw4T7lGqf4pYcQMbuvysVtd85dcLPMADQI2av+rjCtWiaIOndCaBwNAGmuuPiEZfc0sAJIae0ukS3S3EmRoXEIEBS18yIR6BXQeDnkjgq3+GwooMzGlVn1eASx9gSIiQgFq0dH58o8Tot+6DFpTkLVCnD+zmjArD13A=; Received: from amnesiac.at.no.dns (ppp85-141-160-161.pppoe.mtu-net.ru [85.141.160.161]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1JTOCt-000LDX-K2; Mon, 25 Feb 2008 00:16:24 +0300 Date: Mon, 25 Feb 2008 00:16:22 +0300 From: Eygene Ryabinkin To: Jeremy Chadwick Message-ID: References: <20080223010856.7244.qmail@smasher.org> <47C068B5.2090000@thedarkside.nl> <20080223185620.GA98105@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-2.2 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_05 Cc: hackers@freebsd.org, security@freebsd.org Subject: Re: Zeroing sensitive memory chunks [Was: Security Flaw in Popular Disk Encryption Technologies] 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, 24 Feb 2008 21:16:26 -0000 Good day. I am posting the follow-up to the -hackers and CC'ing to the -security, because some more-or-less nasty points were found. Sat, Feb 23, 2008 at 10:32:02PM +0300, Eygene Ryabinkin wrote: > But there is another concern with bzero(): it is well-known function. > Especially for compilers. And it is bad: some arrays inside g_eli, > that hold decryption keys are the local variables. And they are > not used after the final bzero() call, so optimizing compiler can > eliminate the bzero() completely, as the "not relevant". I don't > know if GCC does it -- I should check and will do this tomorrow, > because it is already too late in Russia for this day ;)) Generally speaking, there is nothing special in this finding: "Secure Programming Cookbook for C and C++" from O'Reilly warns the reader about it (page 705 and below, citing by the current edition, http://www.oreilly.com/catalog/secureprgckbk/). OK, gcc 4.2.1 does the dead code removal and sometimes bzero/memset can be omitted (gcc 3.4.6, the one I have at hand from the 3.x branch, is never omitting these functions). It really depends on the size of the local array. The test program is: ----- #include #include #include #define bar(n) \ void bar ## n(void) \ { \ char b[n]; \ scanf("%" #n "s", b); \ memset(b, '\0', sizeof(b)); \ } #define foo(n) \ void foo ## n(void) \ { \ char b[n]; \ scanf("%" #n "s", b); \ bzero(b, sizeof(b)); \ } foo(16) foo(24) foo(32) foo(1024) bar(16) bar(24) bar(28) bar(30) bar(31) bar(32) bar(1024) int main(void) { foo16(); foo24(); foo28(); foo32(); foo1024(); bar16(); bar24(); bar28(); bar30(); bar31(); bar32(); bar1024(); return 0; } ----- Compiled with '-O' switch, it eliminates bzero/memset for all functions with the local array size < 32. For example, this is the assembler code of bar31 (taken from 'gcc -O -S -o test.s test.c'): ----- .globl bar31 .type bar31, @function bar31: pushl %ebp movl %esp, %ebp subl $40, %esp leal -31(%ebp), %eax movl %eax, 4(%esp) movl $.LC2, (%esp) call scanf leave ret .size bar31, .-bar31 .section .rodata.str1.1 .LC3: .string "%30s" .text .p2align 4,,15 ----- The simple PoC session transcript follows: ----- $ cat poc.c #include #include #include void pass(void) { char buffer[31]; printf("Password: "); scanf("%30s", buffer); memset(buffer, 0, sizeof(buffer)); } int main(void) { pass(); return 0; } $ gcc -O -g -o poc poc.c $ gdb poc GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"... (gdb) b main Breakpoint 1 at 0x8048450: file poc.c, line 15. (gdb) run Starting program: /some/path/poc Breakpoint 1, main () at poc.c:15 15 { (gdb) step main () at poc.c:16 16 pass(); (gdb) step pass () at poc.c:9 9 printf("Password: "); (gdb) print &buffer $1 = (char (*)[31]) 0xbfbfec69 (gdb) step 10 scanf("%30s", buffer); (gdb) Password: ASDFGHJKLQWERTYUIO 12 } (gdb) main () at poc.c:18 18 } (gdb) 0x080483af in _start () (gdb) x/35c 0xbfbfec69 0xbfbfec69: 65 'A' 83 'S' 68 'D' 70 'F' 71 'G' 72 'H' 74 'J' 75 'K' 0xbfbfec71: 76 'L' 81 'Q' 87 'W' 69 'E' 82 'R' 84 'T' 89 'Y' 85 'U' 0xbfbfec79: 73 'I' 79 'O' 0 '\0' 1 '\001' 0 '\0' 0 '\0' 0 '\0' -36 'Ü' 0xbfbfec81: -20 'ì' -65 '¿' -65 '¿' 0 '\0' 0 '\0' 0 '\0' 0 '\0' -104 '\230' 0xbfbfec89: -20 'ì' -65 '¿' -65 '¿' (gdb) ----- Currently, I was not able to identify gcc's code that removes the memset in question, so if anyone has ideas -- it will be appreciated. Just now there should be no flaws in the geli code if not dead code elimination occurs for array sizes >= 32: all local buffers that are cleared by bzero() are at least 64 bytes. But there can be other parts of a kernel that needs to be verified and gcc's conditions for the memset elimination should be analyzed. I will continue to investigate. And still, if some old/new gcc's (or other compilers, although they are not suspported for the kernel builds) will change their mind about elimination conditions for the tail memset(), we can be in trouble. Sure, stack-based variables can be rewritten by further calls to other functions, but it is better to be safe, then sorry ;-/ And it seems not to matter that kernel library has its own memset implementation, because a) gcc changes bzero -> memset in the single pass and the internal memset is tried first (gcc's builtins.c, lines 3529 and down); b) gcc tries to eliminate memset() even if there is such local function. Here is the test example: ----- $ cat poc1.c #include #include void * memset(void *b, int c, size_t len) { char *bb; for (bb = (char *)b; len--; ) *bb++ = c; return (b); } int foo31() { char buffer[31]; scanf("%30s", buffer); memset(buffer, 0, sizeof(buffer)); } int bar31() { char buffer[31]; scanf("%30s", buffer); bzero(buffer, sizeof(buffer)); } int main() { bar31(); foo31(); return 0; } ----- As one can verify with 'gcc -O -S -o poc1.s poc1.c', there will be no cleaning in both foo31() and bar31(). > For example, OpenSSL has the OPENSSL_cleanse() function whose purpose > is two-fold (from http://cvs.openssl.org/chngview?cn=9301): > ----- > *) New function OPENSSL_cleanse(), which is used to cleanse a section of > memory from it's contents. This is done with a counter that will > place alternating values in each byte. This can be used to solve > two issues: 1) the removal of calls to memset() by highly optimizing > compilers, and 2) cleansing with other values than 0, since those can > be read through on certain media, for example a swap space on disk. > [Geoff Thorpe] > ----- > > The '1)' is what I was talking about. '2)' is not very clear to > me now, I should research what Geoff meant. If anyone has an idea, > please comment. > > May be the crypto(4,9) framework should receive the function, that > will be simular to the OPENSSL_cleanse. And that function should > be used for wiping of the sensitive data. I rethinked this issue: the function should go (if it should be ever added) to the general kernel library. The reason is that there can be other code that will need data sanitization and it should not rely on the crypto framework. -- Eygene From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 21:43:43 2008 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 3EFF716A403; Sun, 24 Feb 2008 21:43:43 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 91DD413C458; Sun, 24 Feb 2008 21:43:42 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m1OLheEW040879; Sun, 24 Feb 2008 22:43:41 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m1OLhe9l040878; Sun, 24 Feb 2008 22:43:40 +0100 (CET) (envelope-from olli) Date: Sun, 24 Feb 2008 22:43:40 +0100 (CET) Message-Id: <200802242143.m1OLhe9l040878@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, koitsu@FreeBSD.ORG In-Reply-To: <20080224200305.GA49564@eos.sc1.parodius.com> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Sun, 24 Feb 2008 22:43:41 +0100 (CET) Cc: Subject: Re: loader and ficl/Forth help X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, koitsu@FreeBSD.ORG List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Feb 2008 21:43:43 -0000 Jeremy Chadwick wrote: > I have a lot more reading to do on the subject of Forth. Stacks are > hardly a new concept to me, but the conditions where Forth puts > something onto the stack are. I've never worked with a language like > this before (at least RPN doesn't frustrate me!). I've already found > some reading material which should help. It also took me some time to get familiar with it. It's also somewhat non-trivial to find out what the FreeBSD- specific things do. For example, "environment?" picks a string from the stack and searches for that name in an internal dictionary of environment attributes. It leaves the result of the attribute on the stack and true if found, otherwise false. So, for the arch-* attributes there are three possible results: false (not found) false true (found, value is false) true true (found, value is true) The attribute "arch-pc98" is special: If it is set, it is always true, and all the other arch-* are not set: s" arch-pc98" environment? --> true true s" arch-i386" environment? --> false s" arch-ia64" environment? --> false s" arch-powerpc" environment? --> false In all other cases (i.e. non-pc98), arch-pc98 is not set, and all the others are set to either true or false. For example, in the case of i386: s" arch-pc98" environment? --> false s" arch-i386" environment? --> true true s" arch-ia64" environment? --> false true s" arch-powerpc" environment? --> false true I don't know why it is that way. That inconsistency makes if-branches somewhat more complicated. Another thing to keep in mind is that getenv leaves two values on the stack if the name was found (a Forth string consists of two values: the actual string and its length). If not found, only one value is left on the stack (-1). 2dup and 2drop are suitable for strings. > Sadly, the "sh_el not found" error still continues with this code -- but > it does fix the crashing I was seeing. I believe the problem is that > constants cannot be put inside of a function (functions being runtime > things, not compile-time things). Since the original code used > compile-time conditions ([if], etc.), it meant that only one declaration > for sh_el, sv_el, etc. was made. Maybe you should declare these as variables (outside of functions) instead of constants, and only assign to them within the functions. That should work. > And so on, ditto with adding "variable sh_el", "variable sv_el" and > others to the very top of frames.4th. This actually fixed the "not > found" error, and now I'm stuck with "Error: compile only!" being > induced by the "dup -1 = if" line. "if" is for compile mode, and "[if]" is for immediate mode. If you're not in a function definition, then you're not in compile mode. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "C++ is the only current language making COBOL look good." -- Bertrand Meyer From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 22:01:14 2008 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 B574E16A401 for ; Sun, 24 Feb 2008 22:01:14 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 92BA313C459 for ; Sun, 24 Feb 2008 22:01:14 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 91C3F1CC033; Sun, 24 Feb 2008 14:01:14 -0800 (PST) Date: Sun, 24 Feb 2008 14:01:14 -0800 From: Jeremy Chadwick To: Oliver Fromme Message-ID: <20080224220114.GA52366@eos.sc1.parodius.com> References: <20080224145940.GA41037@eos.sc1.parodius.com> <200802241738.m1OHccfW031633@lurza.secnetix.de> <20080224200305.GA49564@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080224200305.GA49564@eos.sc1.parodius.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-hackers@freebsd.org Subject: Re: loader and ficl/Forth help 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, 24 Feb 2008 22:01:14 -0000 On Sun, Feb 24, 2008 at 12:03:05PM -0800, Jeremy Chadwick wrote: > I'll have to get the qemu stuff set up so I can test this more easily. I re-thought the method a bit, and went with something slightly more hackish, plus added code to deal with the case where one uses -h or -Dh in /boot.config (thus setting boot_serial=YES). The Forth code can probably be simplified, but since I got this to work, I'll submit a PR for the whole thing. We can hash out details/improvements there. \ Used when serial console is detected (-|+ characters) 45 constant ascii_dash 124 constant ascii_pipe 43 constant ascii_plus : set_serial_charset ( -- ) s" console" getenv dup -1 = if drop exit then s" comconsole" compare-insensitive 0= if drop ascii_dash h_el ! ascii_pipe v_el ! ascii_plus lt_el ! ascii_plus lb_el ! ascii_plus rt_el ! ascii_plus rb_el ! then s" boot_serial" getenv dup -1 = if drop exit then s" YES" compare-insensitive 0= if drop ascii_dash h_el ! ascii_pipe v_el ! ascii_plus lt_el ! ascii_plus lb_el ! ascii_plus rt_el ! ascii_plus rb_el ! then ; set_serial_charset should be called after f_single in frames.4th. I just tested it on our development box, which uses -S115200 -Dh in /boot.config and nothing serial-related in loader.conf: +-----------------------------------------+ | | | | ______ | | | ____| __ ___ ___ | Welcome to FreeBSD! | | |__ | '__/ _ \/ _ \ | | | __|| | | __/ __/ | | | | | | | | | | 1. Boot FreeBSD [default] | |_| |_| \___|\___| | 2. Boot FreeBSD with ACPI disabled | ____ _____ _____ | 3. Boot FreeBSD in Safe Mode | | _ \ / ____| __ \ | 4. Boot FreeBSD in single user mode | | |_) | (___ | | | | | 5. Boot FreeBSD with verbose logging | | _ < \___ \| | | | | 6. Escape to loader prompt | | |_) |____) | |__| | | 7. Reboot | | | | | | | |____/|_____/|_____/ | | | | | | | Select option, [Enter] for default | | or [Space] to pause timer 6 | +-----------------------------------------+ -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 22:21:24 2008 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 CE14216A400 for ; Sun, 24 Feb 2008 22:21:24 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id AF25A13C458 for ; Sun, 24 Feb 2008 22:21:24 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id AE77F1CC033; Sun, 24 Feb 2008 14:21:24 -0800 (PST) Date: Sun, 24 Feb 2008 14:21:24 -0800 From: Jeremy Chadwick To: Oliver Fromme Message-ID: <20080224222124.GA54599@eos.sc1.parodius.com> References: <20080224145940.GA41037@eos.sc1.parodius.com> <200802241738.m1OHccfW031633@lurza.secnetix.de> <20080224200305.GA49564@eos.sc1.parodius.com> <20080224220114.GA52366@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080224220114.GA52366@eos.sc1.parodius.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-hackers@freebsd.org Subject: Re: loader and ficl/Forth help 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, 24 Feb 2008 22:21:24 -0000 On Sun, Feb 24, 2008 at 02:01:14PM -0800, Jeremy Chadwick wrote: > ... I'll submit a PR for the whole thing. We can hash out > details/improvements there. http://www.freebsd.org/cgi/query-pr.cgi?pr=121064 -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 23:13:46 2008 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 B69A216A405 for ; Sun, 24 Feb 2008 23:13:46 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.freebsd.org (Postfix) with ESMTP id 6E32D13C46B for ; Sun, 24 Feb 2008 23:13:46 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so2196855pyb.10 for ; Sun, 24 Feb 2008 15:13:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer; bh=+hllXM/UNPLQiVk3FZY80rMmnNHPYBtTIdI5oMvL1Xo=; b=hxqzLXOLh7Wbt9LKf5tgF+a60PFUngbbIhzesErOQ4U+HqiCthqJiEK7W1dK6qJiM3KW778xXLZuLXEOg7tB+QZ3pCE1pOtQtDIPalSvNZXyWBOi6XA2stMA/Mzm/iHtTi9jnBmOtL35BJBa0KvpYI1Vbnho7+eiz4+qdkUNyg0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer; b=bBj7Ila8OmcAqcMeMfyB8jzuklMVF+blYmKdUNFKm+31///AVHfMPG+sbWumJ3ln3pm+eDzgrjuix+M+EZJsTA5WQh2UiKzgC8fOP57bkeZy+L++0AO68giH/0R366qGDrEw0vNtVh1M07+bfHmj8wX1B2LvLYqD4yKYgrKpb5w= Received: by 10.35.90.1 with SMTP id s1mr2622958pyl.53.1203893299442; Sun, 24 Feb 2008 14:48:19 -0800 (PST) Received: from ?192.168.1.4? ( [98.212.164.35]) by mx.google.com with ESMTPS id n27sm4902994pyh.11.2008.02.24.14.48.17 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 24 Feb 2008 14:48:18 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v624) In-Reply-To: <20080224.124339.-1302545914.imp@bsdimp.com> References: <20080222.225937.-146245356.imp@bsdimp.com> <20080223.000308.686168314.imp@bsdimp.com> <20080224171155.GD51827@dracon.ht-systems.ru> <20080224.124339.-1302545914.imp@bsdimp.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <86c537e091aaaebaf6ba00e5259c5eb1@gmail.com> Content-Transfer-Encoding: 7bit From: Joshua Isom Date: Sun, 24 Feb 2008 16:50:05 -0600 To: hackers@freebsd.org X-Mailer: Apple Mail (2.624) Cc: Subject: Re: find -lname and -ilname implemented 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, 24 Feb 2008 23:13:46 -0000 Instead of all the debate about GNU compatibility and the fact that the patch adds a feature not readily available, why not improve FreeBSD's find without caring about GNU's find? I have not seen a way to capture output from a command and compare it to another command. Imagine something conceptually like `find . -type l -execout readlink '{}' \; -eq "foobar.txt" -print`? Then it's possible to achieve the same possibility as -lname, and far far more. You could search for all files with "foobar" in the last ten lines of the file even. The closest "viable" option to this that I know of is find2perl, and then custom editing. Not to mention, I imagine you'd soon see GNU find struggling for FreeBSD find compatibility. From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 05:28:33 2008 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 36F0616A406 for ; Mon, 25 Feb 2008 05:28:33 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outI.internet-mail-service.net (outI.internet-mail-service.net [216.240.47.232]) by mx1.freebsd.org (Postfix) with ESMTP id 18B2413C447 for ; Mon, 25 Feb 2008 05:28:32 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Sun, 24 Feb 2008 21:28:32 -0800 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 83223127346; Sun, 24 Feb 2008 21:28:31 -0800 (PST) Message-ID: <47C2520C.5080100@elischer.org> Date: Sun, 24 Feb 2008 21:28:44 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Mike Meyer References: <20080223123556.3eee709d@bhuda.mired.org> <20080223.110047.-397883947.imp@bsdimp.com> <20080223131937.182373b2@bhuda.mired.org> <20080223.120546.74701383.imp@bsdimp.com> <20080223155355.3f80b77f@bhuda.mired.org> In-Reply-To: <20080223155355.3f80b77f@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: find -lname and -ilname implemented 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, 25 Feb 2008 05:28:33 -0000 Mike Meyer wrote: > > What's ridiculous? That the only limit is the developers definition of > "trivial"? Care to provide another one? That OS X turned /bin/sh into > bash? I'd agree that that's ridiculous, except it's a fact. That they > did it to make OS X more compatible with Linux? Would you like me to > try and dig up the mail from jkh (I'm pretty sure it was him) that > says that's why they did it? > > I suspect your definition of "long tradition" is a lot shorter than > mine. That's they only way I can make that statement make sense - at > least the part about BSD and other Unix vendors. It's been in my tradition for Unix developement since 1986 when I first joined comp.unix anyhow, I think this is silly. If you saw what Warner and others have to do to in battling the Linux hordes, you'd also be looking to remove all the trivial complaints that are made as excuses to not use BSD. I think that we have to make a conscious decision as a project to acknowledge the position we find ourselves in WRT 3rd party software and make moves to lower the barriers to entry as much as we can. for what it's worth I'm solidly with Warner on this one. > > 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 DE0BD16A406 for ; Mon, 25 Feb 2008 05:55:45 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (bhuda.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 752F213C448 for ; Mon, 25 Feb 2008 05:55:44 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 25595 invoked by uid 1001); 25 Feb 2008 05:54:31 -0000 Received: from bhuda.mired.org (localhost.localdomain [127.0.0.1]) by bhuda.mired.org (tmda-ofmipd) with ESMTP; Mon, 25 Feb 2008 00:54:30 -0500 Date: Mon, 25 Feb 2008 00:54:29 -0500 To: freebsd-hackers@freebsd.org Message-ID: <20080225005429.38f0c91a@bhuda.mired.org> In-Reply-To: <47C2520C.5080100@elischer.org> References: <20080223123556.3eee709d@bhuda.mired.org> <20080223.110047.-397883947.imp@bsdimp.com> <20080223131937.182373b2@bhuda.mired.org> <20080223.120546.74701383.imp@bsdimp.com> <20080223155355.3f80b77f@bhuda.mired.org> <47C2520C.5080100@elischer.org> Organization: Meyer Consulting X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.12; amd64-portbld-freebsd6.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAG1BMVEXguIzRkGnhyaz069mXhW0WHRnbrnR9WCQ6LB0CchNMAAACSUlEQVQ4jV2TQW7jMAxFGaPQOgQEdZaGMsgBrAvUA03dCxj1Uu4U2gfwQD7AGNax51NK07RcxXz6/CSl0Ij450vkPG1jzpIZM1UwDCl/xB14TWnNX8A00Qj5a0mnVFVbVUz4MeErea2HikSRqZzY894zwg9p2+/AtO8LzxFED+tNAUFeU29iFOLRxlZAcdo9A8wi8ZBMV4BKPde82Oxrvs6BTkulQIClte0DLFzzsKk9j1MBex8iUaP00Bd78S/muyFScrTXz6zLkEUxJp+SabQfNOs4f4Jpx5qSZ/304PWwlEWP1cOn/mJQR7EOD+uKhjcBLziuL7xoY5Xm+VFAUSw/LwwwsHEHxihpwV4EJH0xXRkbw1PkRw+X4pEuSJwBggqk+HEYKkiL5/74/nQkogigzQsAFrakxZyfw3wMIEEZPv4AWMfxwqE5GNxGaERjmH+PG8AE0L4/w9g0lsp1raLYAN5azQa+AOoO9NwcpFkTrG2VKNMNEL5UKUUAw34tha0z7onUG0oBoNtczE04GwFE3wCHc0ChezAJ6A1WMV81AtY7wDAJSlXwV+4cwBvsOsrQMRawfQEBz0deEZ7WNpV2szckIKo5VpDHDSDvF1GItwqqAlG01Hh50BGtVhuUkjkasg/14bYFGCgWg1fSWHvmOoJck2xdp9ZvZBHzDVTzX23TkrOn7qe5U2COEw5D4Vx3qEQpFY2Z/3QFnJxzp7YCmSMG19nOUoe869zZfOQb5ywQuWu0yCn5+8gxZz+BE7vG3j4/wbf4D/sXN9Wug1s7AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Delivery-Agent: TMDA/1.1.11 (Ladyburn) From: Mike Meyer Subject: Re: find -lname and -ilname implemented 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, 25 Feb 2008 05:55:46 -0000 On Sun, 24 Feb 2008 21:28:44 -0800 Julian Elischer wrote: > It's been in my tradition for Unix developement since 1986 when I > first joined comp.unix It has happened. But from my perspective, what happened going from v6 to v7 tends to be the rule, and your tradition is the exception. > If you saw what Warner and others have to do to in battling the Linux > hordes, you'd also be looking to remove all the trivial complaints > that are made as excuses to not use BSD. No, I wouldn't. You're assuming that popularity is inherently a good thing, which is a common misconception I don't share. More accurately, I don't believe that popularity is in and of itself a good thing, to be catered to at all costs. Makes me wonder if there's a connection between GNU distros treating their users like idiots and those same users not being able to see beyond the trivialities. > I think that we have to make a conscious decision as a project to > acknowledge the position we find ourselves in WRT 3rd party software > and make moves to lower the barriers to entry as much as we can. Um, if FreeBSD has to become GNU in order to win GNU users, what's the point? Skip the pain, switch to GNU, and get the popularity you want and the platform you deserve with no delay. Of course, since GNU is well on the way to becoming Windows in order to get people to switch to GNU from Windows, maybe we should just skip a step and start catering to Windows users? After all, there are an order of magnitude more of them... http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 07:09:58 2008 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 3FEEC16A405 for ; Mon, 25 Feb 2008 07:09:58 +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 D474313C4EC for ; Mon, 25 Feb 2008 07:09:57 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m1P77HUN077956; Mon, 25 Feb 2008 00:07:18 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 25 Feb 2008 00:07:44 -0700 (MST) Message-Id: <20080225.000744.-345418608.imp@bsdimp.com> To: mwm-keyword-freebsdhackers2.e313df@mired.org From: "M. Warner Losh" In-Reply-To: <20080225005429.38f0c91a@bhuda.mired.org> References: <20080223155355.3f80b77f@bhuda.mired.org> <47C2520C.5080100@elischer.org> <20080225005429.38f0c91a@bhuda.mired.org> 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: freebsd-hackers@freebsd.org Subject: Re: find -lname and -ilname implemented 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, 25 Feb 2008 07:09:58 -0000 In message: <20080225005429.38f0c91a@bhuda.mired.org> Mike Meyer writes: : On Sun, 24 Feb 2008 21:28:44 -0800 Julian Elischer wrote: : > It's been in my tradition for Unix developement since 1986 when I : > first joined comp.unix : : It has happened. But from my perspective, what happened going from v6 : to v7 tends to be the rule, and your tradition is the exception. Then clearly you haven't been paying attention. While many of the attempts to make different versions of Unix compatible have failed, the attempts have been there from the start. In addition, all of the tools in the tree that aren't based on gnu tools have had many gnu extensions added continuously over the course of the years in FreeBSD. : > If you saw what Warner and others have to do to in battling the Linux : > hordes, you'd also be looking to remove all the trivial complaints : > that are made as excuses to not use BSD. : : No, I wouldn't. You're assuming that popularity is inherently a good : thing, which is a common misconception I don't share. Popularity has nothing to do with it. : More accurately, : I don't believe that popularity is in and of itself a good thing, to : be catered to at all costs. Makes me wonder if there's a connection : between GNU distros treating their users like idiots and those same : users not being able to see beyond the trivialities. You fail to understand the complex interplay of politics here. These people do not want to see beyond it. They want to shut you down because you aren't using their beloved Linux. They use stupid excuses to not do things. This is about removing barriers to entry. This isn't about being popular. : > I think that we have to make a conscious decision as a project to : > acknowledge the position we find ourselves in WRT 3rd party software : > and make moves to lower the barriers to entry as much as we can. : : Um, if FreeBSD has to become GNU in order to win GNU users, what's the : point? Skip the pain, switch to GNU, and get the popularity you want : and the platform you deserve with no delay. Hello? BSDL calling. You left your GPL here and we don't want it. It is funny, but the same sorts of arguments were made against POSIX constructs only a few years ago. They were evil. Something was wrong with them. But they have proven to be OK in the fullness of time, and POSIX now is the exception rather than the rule. It was proposed back in 1990 or so, and it took until the early part of this century to be adopted. Many of the GNU tools are about 5 years behind that curve. : Of course, since GNU is well on the way to becoming Windows in order : to get people to switch to GNU from Windows, maybe we should just skip : a step and start catering to Windows users? After all, there are an : order of magnitude more of them... Ture, but irrelevant. Warner From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 09:17:47 2008 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 DD08616A402 for ; Mon, 25 Feb 2008 09:17:47 +0000 (UTC) (envelope-from sharadc@in.niksun.com) Received: from in.niksun.com (210.18.76.166.sify.net [210.18.76.166]) by mx1.freebsd.org (Postfix) with ESMTP id 796E213C448 for ; Mon, 25 Feb 2008 09:17:47 +0000 (UTC) (envelope-from sharadc@in.niksun.com) Received: from sharadc.in.niksun.com (unknown [10.60.5.27]) by in.niksun.com (Postfix) with ESMTP id 0BD8B5D19; Mon, 25 Feb 2008 15:02:31 +0530 (IST) From: Sharad Chandra Organization: NIKSUN To: freebsd-hackers@freebsd.org Date: Mon, 25 Feb 2008 14:40:56 +0530 User-Agent: KMail/1.9.4 References: <200802221558.42443.sharadc@in.niksun.com> <200802221437.48293.wundram@beenic.net> In-Reply-To: <200802221437.48293.wundram@beenic.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802251440.56435.sharadc@in.niksun.com> Cc: "Heiko Wundram \(Beenic\)" Subject: Re: usleep 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, 25 Feb 2008 09:17:48 -0000 ,---- [Heiko Wundram (Beenic) wrote:] | Am Freitag, 22. Februar 2008 11:28:42 schrieb Sharad Chandra: | > Does usleep work for you? i just saw it is implemented over nanosleep | > which passes a struct timeval to "select". | | Quoting from POSIX: | | """ | The usleep() function will cause the calling thread to be suspended from | execution until either the number of real-time microseconds specified by | the argument useconds has elapsed or a signal is delivered to the calling | thread and its action is to invoke a signal-catching function or to | terminate the process. The suspension time may be longer than requested due | to the scheduling of other activity by the system. | """ Yes, exactly. "microseconds" is giving me image we can go up to 1 micro but not a single time it sleeps for that much, or +- 10-20 micro sec. does suspension time mean 1000 micro secs? | | See the last sentence, specifically. | | So, yes, the behaviour you're seeing is pretty much expected, simply | because _user_ processes are scheduled in timeslices, which depend on the | HZ setting of the kernel. I was looking some where and i found process switching time is around 10ms. That means time slice is 10ms. say some peace of code just called usleep or nanosleep and scheduling occurs so at least it will take 10 ms. I didn't find sleeping more than 10 ms if usec = 1 to few us. Similarly, For setitimer, it goes the same too. if my code is right value.it_interval.tv_sec = 0; /* Zero seconds */ value.it_interval.tv_usec = 000000; value.it_value.tv_sec = 0; /* Zero seconds */ value.it_value.tv_usec = 1; /* 1 us */ result = setitimer( which, &value, &ovalue ); gettimeofday (&t1, NULL); for( count=0; ((count 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 333E316A401 for ; Mon, 25 Feb 2008 09:39:37 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from mail.beenic.net (mail.beenic.net [83.246.72.40]) by mx1.freebsd.org (Postfix) with ESMTP id BF19C13C45A for ; Mon, 25 Feb 2008 09:39:36 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from [192.168.1.38] (a89-182-20-101.net-htp.de [89.182.20.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.beenic.net (Postfix) with ESMTP id CC79BA44529 for ; Mon, 25 Feb 2008 10:39:34 +0100 (CET) From: "Heiko Wundram (Beenic)" Organization: Beenic Networks GmbH To: freebsd-hackers@freebsd.org Date: Mon, 25 Feb 2008 10:39:59 +0100 User-Agent: KMail/1.9.7 References: <200802221558.42443.sharadc@in.niksun.com> <200802221437.48293.wundram@beenic.net> <200802251440.56435.sharadc@in.niksun.com> In-Reply-To: <200802251440.56435.sharadc@in.niksun.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802251039.59767.wundram@beenic.net> Subject: Re: usleep 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, 25 Feb 2008 09:39:37 -0000 Am Montag, 25. Februar 2008 10:10:56 schrieb Sharad Chandra: > So does it mean, freebsd has limitation. sleeping will only work for its > value more than 1 milli sec because % of +- error value is comparitivly > low? I am curious to know, is there any method which sleeps for few > microseconds. Some one please give me link where to look for "select". No, this does not mean that FreeBSD has a limitation, but rather that FreeBSD is not a real-time operating system. You'll see the similar behaviour on pretty much any other operating system that is _not_ a RTOS (for example, Windows has a fixed resolution of non-Multimedia-Timers of around 10ms [where Multimedia Timers are a specific interface to sleep with a higher resolution, designed for Multimedia applications, but the resolution isn't that much higher, anyway], and on Linux, it also depends on the Tick-Frequency, similar to FreeBSD's HZ setting, but actually I don't know how the tickless Linux-kernel [which is implemented only in the latest versions, and not default anyway] behaves here). There is no way (AFAIK) for a userland application to _sleep_ for a finer grained amount of time than a timeslice, except in a busy loop which calls gettimeofday or similar repeatedly to break when the "timeout" occurs, but even then you don't have a guarantee that you won't sleep longer, simply because the process might be preempted just before the timeout occurs because another process also wants its timeslice. But, more specifically, why do you need to sleep for a short time in a user process anyway? Normally, you're blocking on some form of condition, which will "wake you up" as soon as the condition triggers and you can be scheduled (and in this "active scheduling" case the time-slice "rule" doesn't apply). If you give some more info on what you're trying to do (and why you need such a high resolution sleep), maybe someone will be able to help you better and show you how to achieve what you're trying to do without blocking on a timeout. -- Heiko Wundram Product & Application Development From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 10:51:54 2008 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 4087016A400 for ; Mon, 25 Feb 2008 10:51:54 +0000 (UTC) (envelope-from sharadc@in.niksun.com) Received: from in.niksun.com (210.18.76.166.sify.net [210.18.76.166]) by mx1.freebsd.org (Postfix) with ESMTP id C10F113C45D for ; Mon, 25 Feb 2008 10:51:53 +0000 (UTC) (envelope-from sharadc@in.niksun.com) Received: from sharadc.in.niksun.com (unknown [10.60.5.27]) by in.niksun.com (Postfix) with ESMTP id CA7535D3A; Mon, 25 Feb 2008 16:36:37 +0530 (IST) From: Sharad Chandra Organization: NIKSUN To: freebsd-hackers@freebsd.org Date: Mon, 25 Feb 2008 16:15:02 +0530 User-Agent: KMail/1.9.4 References: <200802221558.42443.sharadc@in.niksun.com> <200802251440.56435.sharadc@in.niksun.com> <200802251039.59767.wundram@beenic.net> In-Reply-To: <200802251039.59767.wundram@beenic.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802251615.03040.sharadc@in.niksun.com> Cc: "Heiko Wundram \(Beenic\)" Subject: Re: usleep 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, 25 Feb 2008 10:51:54 -0000 ,---- [Heiko Wundram (Beenic) wrote:] | Am Montag, 25. Februar 2008 10:10:56 schrieb Sharad Chandra: | > So does it mean, freebsd has limitation. sleeping will only work for its | > value more than 1 milli sec because % of +- error value is comparitivly | > low? I am curious to know, is there any method which sleeps for few | > microseconds. Some one please give me link where to look for "select". | | No, this does not mean that FreeBSD has a limitation, but rather that | FreeBSD is not a real-time operating system. You'll see the similar | behaviour on pretty much any other operating system that is _not_ a RTOS | (for example, Windows has a fixed resolution of non-Multimedia-Timers of | around 10ms [where Multimedia Timers are a specific interface to sleep with | a higher resolution, designed for Multimedia applications, but the | resolution isn't that much higher, anyway], and on Linux, it also depends | on the Tick-Frequency, similar to FreeBSD's HZ setting, but actually I | don't know how the tickless Linux-kernel [which is implemented only in the | latest versions, and not default anyway] behaves here). | | There is no way (AFAIK) for a userland application to _sleep_ for a finer | grained amount of time than a timeslice, except in a busy loop which calls | gettimeofday or similar repeatedly to break when the "timeout" occurs, but | even then you don't have a guarantee that you won't sleep longer, simply | because the process might be preempted just before the timeout occurs | because another process also wants its timeslice. | | But, more specifically, why do you need to sleep for a short time in a user | process anyway? Normally, you're blocking on some form of condition, which | will "wake you up" as soon as the condition triggers and you can be | scheduled (and in this "active scheduling" case the time-slice "rule" | doesn't apply). I got out-of-order captured packets on my starfire dual port card ie ack get lower time-stamp than its corresponding seq in tcp traffic. I don't have much nic card level knowledge, so decided to produce delay to send ack and increase it till no out-of-order packet. delay in 1000 micro seconds or above will not let me know the time difference figure. I am also searching for what kind of scheduling this card do in picking the one of buffer by time stamper and for what much time. Where should i look for these info? | | If you give some more info on what you're trying to do (and why you need | such a high resolution sleep), maybe someone will be able to help you | better and show you how to achieve what you're trying to do without | blocking on a timeout. `---- -- Thanks in advance. Sharad Chandra From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 11:04:20 2008 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 09DD016A406 for ; Mon, 25 Feb 2008 11:04:20 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from mail.beenic.net (mail.beenic.net [83.246.72.40]) by mx1.freebsd.org (Postfix) with ESMTP id C12BE13C474 for ; Mon, 25 Feb 2008 11:04:19 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from [192.168.1.38] (a89-182-20-101.net-htp.de [89.182.20.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.beenic.net (Postfix) with ESMTP id 752A0A44529 for ; Mon, 25 Feb 2008 12:04:18 +0100 (CET) From: "Heiko Wundram (Beenic)" Organization: Beenic Networks GmbH To: freebsd-hackers@freebsd.org Date: Mon, 25 Feb 2008 12:04:42 +0100 User-Agent: KMail/1.9.7 References: <200802221558.42443.sharadc@in.niksun.com> <200802251039.59767.wundram@beenic.net> <200802251615.03040.sharadc@in.niksun.com> In-Reply-To: <200802251615.03040.sharadc@in.niksun.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802251204.43070.wundram@beenic.net> Subject: Re: usleep 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, 25 Feb 2008 11:04:20 -0000 Am Montag, 25. Februar 2008 11:45:02 schrieb Sharad Chandra: > I got out-of-order captured packets on my starfire dual port card ie ack > get lower time-stamp than its corresponding seq in tcp traffic. I don't > have much nic card level knowledge, so decided to produce delay to send ack > and increase it till no out-of-order packet. delay in 1000 micro seconds or > above will not let me know the time difference figure. I am also searching > for what kind of scheduling this card do in picking the one of buffer by > time stamper and for what much time. Where should i look for these info? As I noted above: if it's just for a test program, try a busy loop calling gettimeofday (or I'd rather use clock_gettime(CLOCK_MONOTONIC), but checking clock_getres(CLOCK_MONOTONIC) if the resolution is actually high enough for your needs) repeatedly and comparing the times until the timeout is lower or equal to the current time. That should get you the timing resolution you need/want (mostly). Other than that, I'm not into NIC programming either, so I can't help you for the rest... -- Heiko Wundram Product & Application Development From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 11:24:02 2008 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 A095516A400 for ; Mon, 25 Feb 2008 11:24:02 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id 2202D13C447 for ; Mon, 25 Feb 2008 11:24:01 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so819757uge.37 for ; Mon, 25 Feb 2008 03:24:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=8vIC5nlYfbvvmBAfb2koksQBsK2NJF0coqP2AwcdxqQ=; b=dj/l355ZN+RB7rRBpXWsSr3So98dQmpOXiuB9i/jW+LOHGOOU2Zq1V2afwFtKlOZtWkdWd2zym5v1WMaZkGPISixwQ5lzNR6G3wZ7zfAc74ZWIWmW/DxpG5napOzPEFHD2rcBcVdbHm3JPvycpKDaFAxrN9Y3DGKbEskC3cDCeQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=oA6/HT58kvaamh7hvfibDZYnLpdKFoc08Svn4+3M3fit4Yizi3SKTwUh9rWGn6X9QMmPQfW+2iF2C2gdyxbdkaFGYcxzJ9jFmdg9kX7UxXziLSV+xt3bpk2MCWCrw+QVqQPHShfmAyOF/0PM/V3MTWEbEu9xS0CoC4HRPxF3bh0= Received: by 10.67.23.5 with SMTP id a5mr3002807ugj.8.1203938640713; Mon, 25 Feb 2008 03:24:00 -0800 (PST) Received: by 10.66.248.11 with HTTP; Mon, 25 Feb 2008 03:24:00 -0800 (PST) Message-ID: Date: Mon, 25 Feb 2008 11:24:00 +0000 From: "Igor Mozolevsky" Sender: mozolevsky@gmail.com To: "Bill Moran" In-Reply-To: <20080224123328.a0a85d7c.wmoran@collaborativefusion.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47C06E1F.5020308@thedarkside.nl> <760775.85636.qm@web50306.mail.re2.yahoo.com> <20080223203316.GC38485@lor.one-eyed-alien.net> <20080224100924.c8e08776.wmoran@collaborativefusion.com> <20080224123328.a0a85d7c.wmoran@collaborativefusion.com> X-Google-Sender-Auth: 00885f214db39c66 Cc: hackers@freebsd.org Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 25 Feb 2008 11:24:02 -0000 On 24/02/2008, Bill Moran wrote: > "Igor Mozolevsky" wrote: [snip] > > IMO the possibility of such attack is so remote that it doesn't really > > warrant any special attention, it's just something that should be kept > > in mind when writing "secure" crypto stuff... > > > Then you're not using this to protect data of a particular sensitive > nature, or you're being a fool. Not at all! > Fact is, data is "sensitive" to different degrees. It's also valuable > to different degrees. > > If you're worried about your personal financial information on your > laptop being stolen, then modern disk encryption is fine. But, if you've > got a mobile device with the sensitive information from 1000s of people > on it, the stakes are different. That device is liable to be the target > of an attack specifically to get the _data_. > > You're correct in 90% of the cases, but there's still the 10% that some > of us need to consider. Crypto is merely a way of obfuscating data, and we all know the truth about security by obscurity, right? Why would you have sensitive data on a laptop that anyone could potentially snatch out of your hand??? If it's sensitive enough to be paranoid, it should never leave the site! There are better ways to protect data than simple disk encryption, *if you really have to* to take it offsite on a laptop. There's only one thing disk crypto is useful for - swap encryption, I'd not use straight crypto for anything else... But again, how many of us here actually use S/Key for remote logins?.. > The fact is that the attack is not difficult, and it's not a matter of > whether or not someone _can_ bypass your disk encryption, it's more a > matter of whether or not they actually care enough to bother, or whether > the $$$ they can get for the stolen hardware alone will satisfy them. > Each user/organization really needs to evaluate this information with > regards to their own situation, but it's important to understand the > details of the risk when making such a decision. It's not a "not difficult" attack - someone has to get hold of your laptop first! Then there's things like BIOS passwords, restricting boot partitions, and if you don't want memory covers to be unscrewed (or your laptop case as a whole, for that matter) you can always use a bit of loctite! As the saying goes, those who think that crypto is the solution to their problem, don't crypto nor the problem... Igor :-) From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 12:36:25 2008 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 0367216A410 for ; Mon, 25 Feb 2008 12:36:25 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from mailout1.zih.tu-dresden.de (mailout1.zih.tu-dresden.de [141.30.67.72]) by mx1.freebsd.org (Postfix) with ESMTP id BCCBB13C46B for ; Mon, 25 Feb 2008 12:36:24 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from rmc67-31.zih.tu-dresden.de ([141.30.67.31] helo=server-n) by mailout1.zih.tu-dresden.de with esmtp (Exim 4.63) (envelope-from ) id 1JTcZ8-0005qu-Uz for freebsd-hackers@freebsd.org; Mon, 25 Feb 2008 13:36:23 +0100 Received: from martin (p5B0EF940.dip.t-dialin.net [91.14.249.64]) by server-n (Postfix) with ESMTP id 80565100A091 for ; Mon, 25 Feb 2008 13:36:18 +0100 (CET) Date: Mon, 25 Feb 2008 13:36:17 +0100 To: freebsd-hackers@freebsd.org From: "Martin Laabs" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable Message-ID: User-Agent: Opera Mail/9.25 (Linux) X-TUD-Virus-Scanned: mailout1.zih.tu-dresden.de Subject: emulate an end-of-media 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, 25 Feb 2008 12:36:25 -0000 Hi, I'll write a script that back up my data on dvd-r and dvd-rams. (And some incremental backups also at some internet storage services.) Therefore I'd like to use dump. It is not too hard to create dump-volumes with fixed size through the -B option. But now I'd like to use some sort of compression. (bzip2 seems far to be to slow. Maybe I'll use gzip or compress) However - with compression I can't use the -B switch of dump because I can't be sure about the compression ratio. This means I have to use the '-a' switch. With that switch enabled, dump starts a new volume after it detects an EOM signal. Because dump itself does not support compression I have to build a pipe like that: dump -aL0 -f - /MYFILESYSTEM|compress -c|aespipe ...|cdrecord dev=3D... = - This obvisouly does not work. I tried to wrote a script that close the pipe after the amount of compressed data reached 4.6GB. But if I close the pipe in that script dump aborts (because of the broken pipe) at all instead of just starting a new volume. What I'd need is a magaic pipe device that converts a ordenary close at the one side to an EOM at the other. Then I could do something like this: dump -aL0 -f /dev/MyMagicDevice & dd if=3D/dev/MyMagicDevice bs=3D1M count=3D4600|./compress -c|cdrecord d= ev=3D... - Before I try to write a kernel module that will do the job (I never wrote a freebsd kernel module before but I think it is some fun to learn that.) I want to ask if anyone see another solution for that problem. (Maybe patching dump - but I don't want to fudge in the CORE source.) Thank you in advance, Martin L. PS: Splitting up the huge (maybe compressed) dump file (also in stream operation) is not a good idea beacause I'd need to insert all the media - even if I resore only a single file. From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 13:24:40 2008 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 918CE16A400 for ; Mon, 25 Feb 2008 13:24:40 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id 5008A13C44B for ; Mon, 25 Feb 2008 13:24:40 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (p54A56D7A.dip.t-dialin.net [84.165.109.122]) by redbull.bpaserver.net (Postfix) with ESMTP id A6F942E125; Mon, 25 Feb 2008 14:24:18 +0100 (CET) Received: from webmail.leidinger.net (webmail.leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id D99611F050; Mon, 25 Feb 2008 14:24:13 +0100 (CET) Received: (from www@localhost) by webmail.leidinger.net (8.14.2/8.13.8/Submit) id m1PDODME060715; Mon, 25 Feb 2008 14:24:13 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Mon, 25 Feb 2008 14:24:12 +0100 Message-ID: <20080225142412.hqn9n6kagw0w0w4o@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Mon, 25 Feb 2008 14:24:12 +0100 From: Alexander Leidinger To: cali clarke References: <5a08be760802241042x2cd93d63of5787a744e745fe5@mail.gmail.com> In-Reply-To: <5a08be760802241042x2cd93d63of5787a744e745fe5@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.5) / FreeBSD-8.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-12.823, required 6, BAYES_00 -15.00, BR_SPAMMER_URI 2.00, RDNS_DYNAMIC 0.10, TW_PD 0.08) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No X-Mailman-Approved-At: Mon, 25 Feb 2008 14:07:54 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Anybody have a patch for pdksh derivatives, for jails? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2008 13:24:40 -0000 Quoting cali clarke (from Sun, 24 Feb 2008 =20 19:42:01 +0100): > Hi. > > pdksh and derivatives (openbsd ksh, mirbsd mksh etc) all have > the same "bug" with regards to jails. On all of my systems, trying > to start *ksh in a jail results in a message that /dev/tty could > not be opened (device busy) and that the shell will not have > job control. For some reason, this makes pretty much any > curses or screen editor fail to run. > > Note that also, this problem does NOT occur if you use ssh > to enter the jail as I believe ssh handles tty allocation in > advance. You don't give enough info. I assume you talk about a login into the =20 host system and then doing a "jexec X pdksh" to login into a jail. The =20 important question here is the how you login into the host system. > I wondered if anybody had patched their *ksh to workaround > this problem? So far it is not clear that the bug is within the *ksh. It may be also =20 the case that the problem should be fixed somewhere else. Bye, Alexander. --=20 It's easier to get forgiveness for being wrong than forgiveness for being right. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 13:37:05 2008 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 E61F216A400 for ; Mon, 25 Feb 2008 13:37:05 +0000 (UTC) (envelope-from robert.woolley@rwoolley.com) Received: from turtle-out.mxes.net (turtle-out.mxes.net [216.86.168.191]) by mx1.freebsd.org (Postfix) with ESMTP id BFC1913C45D for ; Mon, 25 Feb 2008 13:37:05 +0000 (UTC) (envelope-from robert.woolley@rwoolley.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by turtle-in.mxes.net (Postfix) with ESMTP id BCF18163F78 for ; Mon, 25 Feb 2008 08:15:52 -0500 (EST) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 114F323E4AD for ; Mon, 25 Feb 2008 08:15:49 -0500 (EST) Date: Mon, 25 Feb 2008 13:15:46 +0000 From: Robert Woolley To: freebsd-hackers@freebsd.org Message-ID: <20080225131546.0d9d2f22@gumby.homeunix.com.> In-Reply-To: <200802251039.59767.wundram@beenic.net> References: <200802221558.42443.sharadc@in.niksun.com> <200802221437.48293.wundram@beenic.net> <200802251440.56435.sharadc@in.niksun.com> <200802251039.59767.wundram@beenic.net> X-Mailer: Claws Mail 3.3.0 (GTK+ 2.12.8; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 25 Feb 2008 14:25:58 +0000 Subject: Re: usleep 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, 25 Feb 2008 13:37:06 -0000 On Mon, 25 Feb 2008 10:39:59 +0100 "Heiko Wundram (Beenic)" wrote: > Am Montag, 25. Februar 2008 10:10:56 schrieb Sharad Chandra: > > So does it mean, freebsd has limitation. sleeping will only work > > for its value more than 1 milli sec because % of +- error value is > > comparitivly low? I am curious to know, is there any method which > > sleeps for few microseconds. Some one please give me link where to > > look for "select". > > No, this does not mean that FreeBSD has a limitation, but rather that > FreeBSD is not a real-time operating system. You'll see the similar > behaviour on pretty much any other operating system that is _not_ a > RTOS It's actually not a distinguishing feature of RTOSs. I haven't worked on them for a few years, but when I did, both pSOS and VxWorks had this limitation. The important thing is that RTOSs handle interrupts well. In traditional real-time software, sleeping is something that happens in non-critical background tasks. From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 13:55:46 2008 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 059A816A402; Mon, 25 Feb 2008 13:55:46 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id B606713C46B; Mon, 25 Feb 2008 13:55:45 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (p54A56D7A.dip.t-dialin.net [84.165.109.122]) by redbull.bpaserver.net (Postfix) with ESMTP id 8683F2E125; Mon, 25 Feb 2008 14:38:13 +0100 (CET) Received: from webmail.leidinger.net (webmail.leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id 8B4C11F1A8; Mon, 25 Feb 2008 14:38:09 +0100 (CET) Received: (from www@localhost) by webmail.leidinger.net (8.14.2/8.13.8/Submit) id m1PDc9lX062969; Mon, 25 Feb 2008 14:38:09 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Mon, 25 Feb 2008 14:38:08 +0100 Message-ID: <20080225143808.dp3me068g8gsgkow@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Mon, 25 Feb 2008 14:38:08 +0100 From: Alexander Leidinger To: Adrian Chadd References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.5) / FreeBSD-8.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-14.9, required 6, BAYES_00 -15.00, RDNS_DYNAMIC 0.10) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No X-Mailman-Approved-At: Mon, 25 Feb 2008 14:26:09 +0000 Cc: hackers@freebsd.org Subject: Re: Modular type GENERIC? 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, 25 Feb 2008 13:55:46 -0000 Quoting Adrian Chadd (from Sun, 24 Feb 2008 =20 19:26:04 +0900): > G'day, > > I was just wondering why we're not shipping a GENERIC type > configuration that simply loads the modules at startup, rather than a > statically linked kernel. I thought that was a large part of the push > for the modular framework in years past. Using modules needs more space than having all in the kernel (or =20 generating one big "super-module" which contains the code from all =20 modules). There's some kind of space overhead for each module. When =20 module support was added, space on the install media was a critical =20 resource. Today this could be revisited (at least for the kernel which =20 will be installed on the destination medium). > As a quick experiment, I trimmed all the modular devices out of > RELENG_7 GENERIC into a "BASE" configuration file and filled > /boot/loader.conf with modules relevant to my system. Everything > booted just fine. > > How feasible do people think it would be to ship a "GENERIC" > configuration which simply includes all the devices in a default > module list, and users can select/deselect modules they wish to load? I'm running a mini kernel since years, and everything I need is added =20 as a module (if possible). So I would probably be one of the consumers =20 of such a config. > Here's the kernel and loader configuration files I'm using just on my > system. I think acpi_load is a bit extraneous as acpi is included in > the amd64 DEFAULTS. acpi is also loaded automatically on i386 (or not, if specified in the =20 loader, so it should not be added in the config) > http://people.freebsd.org/~adrian/BASE.txt > http://people.freebsd.org/~adrian/loader.conf I haven't looked at this. Bye, Alexander. --=20 Some men are so macho they'll get you pregnant just to kill a rabbit. =09=09-- Maureen Murphy http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 14:46:47 2008 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 C981416A40A for ; Mon, 25 Feb 2008 14:46:47 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from mail.beenic.net (mail.beenic.net [83.246.72.40]) by mx1.freebsd.org (Postfix) with ESMTP id 926EF13C442 for ; Mon, 25 Feb 2008 14:46:47 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from [192.168.1.38] (a89-182-20-101.net-htp.de [89.182.20.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.beenic.net (Postfix) with ESMTP id C8520A44529 for ; Mon, 25 Feb 2008 15:46:45 +0100 (CET) From: "Heiko Wundram (Beenic)" Organization: Beenic Networks GmbH To: freebsd-hackers@freebsd.org Date: Mon, 25 Feb 2008 15:47:09 +0100 User-Agent: KMail/1.9.7 References: <200802221558.42443.sharadc@in.niksun.com> <200802251039.59767.wundram@beenic.net> <20080225131546.0d9d2f22@gumby.homeunix.com.> In-Reply-To: <20080225131546.0d9d2f22@gumby.homeunix.com.> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802251547.10068.wundram@beenic.net> Subject: Re: usleep 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, 25 Feb 2008 14:46:47 -0000 Am Montag, 25. Februar 2008 14:15:46 schrieb Robert Woolley: > On Mon, 25 Feb 2008 10:39:59 +0100 > "Heiko Wundram (Beenic)" wrote: > > Am Montag, 25. Februar 2008 10:10:56 schrieb Sharad Chandra: > > > So does it mean, freebsd has limitation. sleeping will only work > > > for its value more than 1 milli sec because % of +- error value is > > > comparitivly low? I am curious to know, is there any method which > > > sleeps for few microseconds. Some one please give me link where to > > > look for "select". > > > > No, this does not mean that FreeBSD has a limitation, but rather that > > FreeBSD is not a real-time operating system. You'll see the similar > > behaviour on pretty much any other operating system that is _not_ a > > RTOS > > It's actually not a distinguishing feature of RTOSs. I haven't worked on > them for a few years, but when I did, both pSOS and VxWorks had this > limitation. The important thing is that RTOSs handle interrupts > well. In traditional real-time software, sleeping is something that > happens in non-critical background tasks. When you read what I wrote in detail, I just said that he should expect to see the "sliced sleeping" behaviour on pretty much any operating system that is not an RTOS, but didn't say that for an RTOS he should expect exact sleeping (the old "all Spartans are Greeks, but not all Greeks are Spartans" thingy). At least that's what I wanted to say, but I can see that the first sentence might have been slightly misleading wrt. to my intention. Anyway, as a uni project, I had to implement a minimalistic RTOS for an integrated CPU which had the requirement to sleep more or less exactly (because of timing hardware accesses and sensor data acquisition with the sleeps without having interrupts from the external hardware), but I know that this isn't a distinguishing feature. -- Heiko Wundram Product & Application Development From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 14:52:06 2008 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 9729C16A400 for ; Mon, 25 Feb 2008 14:52:06 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 6D1D013C45B for ; Mon, 25 Feb 2008 14:52:06 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from vanquish.ws.pitbpa0.priv.collaborativefusion.com (vanquish.ws.pitbpa0.priv.collaborativefusion.com [192.168.2.162]) (SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Mon, 25 Feb 2008 09:52:05 -0500 id 00056437.47C2D615.00005985 Date: Mon, 25 Feb 2008 09:52:05 -0500 From: Bill Moran To: "Igor Mozolevsky" Message-Id: <20080225095205.def9414d.wmoran@collaborativefusion.com> In-Reply-To: References: <47C06E1F.5020308@thedarkside.nl> <760775.85636.qm@web50306.mail.re2.yahoo.com> <20080223203316.GC38485@lor.one-eyed-alien.net> <20080224100924.c8e08776.wmoran@collaborativefusion.com> <20080224123328.a0a85d7c.wmoran@collaborativefusion.com> Organization: Collaborative Fusion X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.8; i386-portbld-freebsd6.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 25 Feb 2008 14:52:06 -0000 In response to "Igor Mozolevsky" : > On 24/02/2008, Bill Moran wrote: > > "Igor Mozolevsky" wrote: [snip] > > Fact is, data is "sensitive" to different degrees. It's also valuable > > to different degrees. > > > > If you're worried about your personal financial information on your > > laptop being stolen, then modern disk encryption is fine. But, if you've > > got a mobile device with the sensitive information from 1000s of people > > on it, the stakes are different. That device is liable to be the target > > of an attack specifically to get the _data_. > > > > You're correct in 90% of the cases, but there's still the 10% that some > > of us need to consider. > > Crypto is merely a way of obfuscating data, and we all know the truth > about security by obscurity, right? I don't think you correctly understand the concept of "security through obscurity" ... as crypto is _not_ an example of that. > Why would you have sensitive data > on a laptop that anyone could potentially snatch out of your hand??? > If it's sensitive enough to be paranoid, it should never leave the > site! That's like saying, "Why would you ever drive a car on the freeway when you know how many people are killed in auto accidents every day." The answer is, "because you must." > There are better ways to protect data than simple disk encryption, *if > you really have to* to take it offsite on a laptop. Name 3. > There's only one > thing disk crypto is useful for - swap encryption, I'd not use > straight crypto for anything else... Again, I find you opinions odd, and possibly misinformed. > But again, how many of us here > actually use S/Key for remote logins?.. S/Key isn't the magical solution to all security. > > The fact is that the attack is not difficult, and it's not a matter of > > whether or not someone _can_ bypass your disk encryption, it's more a > > matter of whether or not they actually care enough to bother, or whether > > the $$$ they can get for the stolen hardware alone will satisfy them. > > Each user/organization really needs to evaluate this information with > > regards to their own situation, but it's important to understand the > > details of the risk when making such a decision. > > It's not a "not difficult" attack - someone has to get hold of your > laptop first! Given. > Then there's things like BIOS passwords, How does a BIOS password protect RAM from being removed? > restricting > boot partitions, and if you don't want memory covers to be unscrewed > (or your laptop case as a whole, for that matter) you can always use a > bit of loctite! Sure, the old "superglue in the USB port" trick. I'm sure HW manufacturers love it when they see that ... warranty out the door! But in this case, if the attacker is after the data, breaking the RAM door to get it open isn't a very big deal, now is it? > As the saying goes, those who think that crypto is the solution to > their problem, don't crypto nor the problem... Not sure I understand what you mean by that, but your flippant dismissal of strong cryptography is not justified by any facts I've ever seen. -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ wmoran@collaborativefusion.com Phone: 412-422-3463x4023 From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 15:33:32 2008 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 9F6F816A402 for ; Mon, 25 Feb 2008 15:33:32 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.freebsd.org (Postfix) with ESMTP id E20C813C4D3 for ; Mon, 25 Feb 2008 15:33:31 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so909802uge.37 for ; Mon, 25 Feb 2008 07:33:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=7jvjA69IkBfCtvw+EIub+Ex82taMfrNu6MHwcghrAiQ=; b=mNT8B6T0AjdPaebbpt+F+Y0/f60jNSEWxHJhK3brPqlsI4D+u2ksP7Fib91mfSza3VRsVkvIeR1J9zGbauBd0fm94YpRaGoitB2pTOVGs9wqv9Dl/zcLbJEYS6DVaoz+sk4NTYfKCTLnzjNgw+ceixi6FAzK5ywlb620HSjQRao= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=KE5CRauJhJKq6OIZQyqazwHSMTKp1qD8/V6DCYl0uGxr9Ut5N7VY3WH04x2ZJZWk9RxVWWH0bld/+7CDWypsWaMHeJpznuqNIDiM4pzq9l6GFGW4rE7nnVGqhILooarn6PuZ5FetKruHOsZ1aHCtsyrHJFafdKCKC2Q9jMQ6nds= Received: by 10.66.221.6 with SMTP id t6mr3333236ugg.0.1203953610559; Mon, 25 Feb 2008 07:33:30 -0800 (PST) Received: by 10.66.248.11 with HTTP; Mon, 25 Feb 2008 07:33:30 -0800 (PST) Message-ID: Date: Mon, 25 Feb 2008 15:33:30 +0000 From: "Igor Mozolevsky" Sender: mozolevsky@gmail.com To: "Bill Moran" In-Reply-To: <20080225095205.def9414d.wmoran@collaborativefusion.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47C06E1F.5020308@thedarkside.nl> <760775.85636.qm@web50306.mail.re2.yahoo.com> <20080223203316.GC38485@lor.one-eyed-alien.net> <20080224100924.c8e08776.wmoran@collaborativefusion.com> <20080224123328.a0a85d7c.wmoran@collaborativefusion.com> <20080225095205.def9414d.wmoran@collaborativefusion.com> X-Google-Sender-Auth: 952a577368dd8237 Cc: hackers@freebsd.org Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 25 Feb 2008 15:33:32 -0000 On 25/02/2008, Bill Moran wrote: > In response to "Igor Mozolevsky" : > > > Crypto is merely a way of obfuscating data, and we all know the truth > > about security by obscurity, right? > > > I don't think you correctly understand the concept of "security through > obscurity" ... as crypto is _not_ an example of that. You have way too much faith in crypto - any crypto system can be broken given enough time + computing power + determinism... You can't break a system when half the data that you need is missing (see * later). > > Why would you have sensitive data > > on a laptop that anyone could potentially snatch out of your hand??? > > If it's sensitive enough to be paranoid, it should never leave the > > site! > > > That's like saying, "Why would you ever drive a car on the freeway when > you know how many people are killed in auto accidents every day." > > The answer is, "because you must." That's a ridiculous analogy! Such as when?.. > > There are better ways to protect data than simple disk encryption, *if > > you really have to* to take it offsite on a laptop. > > > Name 3. 1) Store the data on a USB stick, or other portable medium which you can detach from the laptop*; or 2) Use crypto system that requires a physical token to decrypt the data (which can be detached from the laptop in transit); and I don't have time to think of a third one ATM... > > There's only one > > thing disk crypto is useful for - swap encryption, I'd not use > > straight crypto for anything else... > > > Again, I find you opinions odd, and possibly misinformed. How could it be misinformed - you've just said that HD crypto is easy to compromise using the aforementioned method, clearly it's not good enough to encrypt sensitive data?.. > > But again, how many of us here > > actually use S/Key for remote logins?.. > > > S/Key isn't the magical solution to all security. I know, I was merely using it as an example of security solution being 'out there' and hardly anyone using it... > > Then there's things like BIOS passwords, > > > How does a BIOS password protect RAM from being removed? Password protecting BIOS prevents the attacker from manipulating permissible boot partitions... > > restricting > > boot partitions, and if you don't want memory covers to be unscrewed > > (or your laptop case as a whole, for that matter) you can always use a > > bit of loctite! > > > Sure, the old "superglue in the USB port" trick. I'm sure HW manufacturers > love it when they see that ... warranty out the door! But in this case, > if the attacker is after the data, breaking the RAM door to get it open > isn't a very big deal, now is it? Once the computer is off you only need to delay the extraction of RAM sufficiently for the attack to be ineffective... And as for the warranty, you have a choice, you either make the system secure and compromise the warranty, or you make the system comply with warranty T&C and compromise the security... > > As the saying goes, those who think that crypto is the solution to > > their problem, don't crypto nor the problem... > > > Not sure I understand what you mean by that, but your flippant dismissal > of strong cryptography is not justified by any facts I've ever seen. The issue is not how strong crypto is, but how people use it - if one relies on the fact that their highly sensitive national secrets are safe just because they've encrypted the hard drive the data is on, and haven't taken any other precautions then you can easily see how a simple attack like that would screw them over, and quite frankly they would deserve it!.. Crypto is not a replacement for common sense! Igor From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 16:00:55 2008 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 90BFE16A408 for ; Mon, 25 Feb 2008 16:00:55 +0000 (UTC) (envelope-from rink@tragedy.rink.nu) Received: from mx1.rink.nu (alastor.rink.nu [213.34.49.5]) by mx1.freebsd.org (Postfix) with ESMTP id 4EAB413C4DB for ; Mon, 25 Feb 2008 16:00:55 +0000 (UTC) (envelope-from rink@tragedy.rink.nu) Received: from localhost (alastor.rink.nu [213.34.49.5]) by mx1.rink.nu (Postfix) with ESMTP id 1D414BFECA7; Mon, 25 Feb 2008 15:44:07 +0000 (UTC) X-Virus-Scanned: amavisd-new at rink.nu Received: from mx1.rink.nu ([213.34.49.5]) by localhost (alastor.rink.nu [213.34.49.5]) (amavisd-new, port 10024) with ESMTP id UeU+ekj4+q13; Mon, 25 Feb 2008 15:43:59 +0000 (UTC) Received: from tragedy.rink.nu (tragedy.rink.nu [213.34.49.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.rink.nu (Postfix) with ESMTP id 2F163BFE830; Mon, 25 Feb 2008 15:43:59 +0000 (UTC) Received: from tragedy.rink.nu (tragedy.rink.nu [213.34.49.3]) by tragedy.rink.nu (8.13.8/8.13.8) with ESMTP id m1PFhxQR008147; Mon, 25 Feb 2008 16:43:59 +0100 (CET) (envelope-from rink@tragedy.rink.nu) Received: (from rink@localhost) by tragedy.rink.nu (8.13.8/8.13.8/Submit) id m1PFhwVt008144; Mon, 25 Feb 2008 16:43:58 +0100 (CET) (envelope-from rink) Date: Mon, 25 Feb 2008 16:43:58 +0100 From: Rink Springer To: Igor Mozolevsky Message-ID: <20080225154358.GF23743@rink.nu> References: <47C06E1F.5020308@thedarkside.nl> <760775.85636.qm@web50306.mail.re2.yahoo.com> <20080223203316.GC38485@lor.one-eyed-alien.net> <20080224100924.c8e08776.wmoran@collaborativefusion.com> <20080224123328.a0a85d7c.wmoran@collaborativefusion.com> <20080225095205.def9414d.wmoran@collaborativefusion.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Cc: hackers@freebsd.org, Bill Moran Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 25 Feb 2008 16:00:55 -0000 On Mon, Feb 25, 2008 at 03:33:30PM +0000, Igor Mozolevsky wrote: > [text] Guys, can you take this to chat@ please... -- Rink P.W. Springer - http://rink.nu "Anyway boys, this is America. Just because you get more votes doesn't mean you win." - Fox Mulder From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 17:16:26 2008 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 600BD16A401 for ; Mon, 25 Feb 2008 17:16:26 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by mx1.freebsd.org (Postfix) with ESMTP id E097E13C468 for ; Mon, 25 Feb 2008 17:16:24 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: by nf-out-0910.google.com with SMTP id b2so946325nfb.33 for ; Mon, 25 Feb 2008 09:16:24 -0800 (PST) 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=id7gJxzah7hm9h3dKnla+tuXsy9UrtNl9i5xIFhTWiI=; b=uA/9pUq1hLy0E45N2/bl8woGoKjocwUJ9d1TBuOPqXztbjsxfuZ3VVmG3NkHIHjUY7FguUQQv4VyAXLac6wwDrlIDgafhCnHqIvRcjDiNvmfGE6Rt+F+qJwa9sKrCJvP5VWELu7qfoBYgpXKigW+FPOtgxf0MR/guV3Pzg3HzI4= 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=XubfFLyRdPEfqTmmp01gQ9jfEEqkmH6pM9dYx1gAb4JApvyt1sS+dgMXIJEt0AIZyrudpIyG94gF0kwzbjJWAfI2IciAv/cpi3cHWml2O1O3+DhSu57NRnYv33f1HQ833Tvw5oGDBHAgT98DKAM79bA0I5kUqEH069ySRf0sfjs= Received: by 10.82.167.5 with SMTP id p5mr6423208bue.38.1203959783852; Mon, 25 Feb 2008 09:16:23 -0800 (PST) Received: from logik.internal.network ( [81.86.41.187]) by mx.google.com with ESMTPS id y34sm9133977iky.6.2008.02.25.09.16.21 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 25 Feb 2008 09:16:22 -0800 (PST) Received: by logik.internal.network (Postfix, from userid 11001) id 358D95C82; Mon, 25 Feb 2008 17:16:18 +0000 (UTC) Date: Mon, 25 Feb 2008 17:16:17 +0000 From: xorquewasp@googlemail.com To: Alexander Leidinger Message-ID: <20080225171617.GA9177@logik.internal.network> References: <5a08be760802241042x2cd93d63of5787a744e745fe5@mail.gmail.com> <20080225142412.hqn9n6kagw0w0w4o@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080225142412.hqn9n6kagw0w0w4o@webmail.leidinger.net> Cc: freebsd-hackers@freebsd.org Subject: Re: Anybody have a patch for pdksh derivatives, for jails? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2008 17:16:26 -0000 On 20080225 14:24:12, Alexander Leidinger wrote: > Quoting cali clarke (from Sun, 24 Feb 2008 >> Note that also, this problem does NOT occur if you use ssh >> to enter the jail as I believe ssh handles tty allocation in >> advance. > > You don't give enough info. I assume you talk about a login into the host > system and then doing a "jexec X pdksh" to login into a jail. The important > question here is the how you login into the host system. Hi. Yes, exactly that. A login on the host system followed by a jexec of *ksh OR a jexec of another shell such as /bin/sh followed by an ordinary exec of any *ksh. >> I wondered if anybody had patched their *ksh to workaround >> this problem? > > So far it is not clear that the bug is within the *ksh. It may be also the > case that the problem should be fixed somewhere else. The problem appears to be that *ksh does various checks to determine if it can run with job control and one of those checks is based on whether or not it can successfully open /dev/tty, which can't happen in a jail (device busy). The other shells in base such as /bin/sh and /bin/csh don't appear to make these checks and therefore just work. I could of course patch *ksh to ignore the fact that it can't open /dev/tty but I'm unsure about what else this would break in the shell due to the hard-to-read source - hence my question about whether or not anybody else had already patched it. From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 18:05:05 2008 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 CDEF016A405 for ; Mon, 25 Feb 2008 18:05:05 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id B989C13C442 for ; Mon, 25 Feb 2008 18:05:05 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id m1PI4u1a082555; Mon, 25 Feb 2008 10:04:56 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.2/8.14.1/Submit) id m1PI4qmV082553; Mon, 25 Feb 2008 10:04:52 -0800 (PST) (envelope-from obrien) Date: Mon, 25 Feb 2008 10:04:51 -0800 From: "David O'Brien" To: "M. Warner Losh" Message-ID: <20080225180451.GD81874@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, "M. Warner Losh" , stas@freebsd.org, hackers@freebsd.org References: <20080222.225937.-146245356.imp@bsdimp.com> <20080223.000308.686168314.imp@bsdimp.com> <20080224171155.GD51827@dracon.ht-systems.ru> <20080224.124339.-1302545914.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080224.124339.-1302545914.imp@bsdimp.com> X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: stas@freebsd.org, hackers@freebsd.org Subject: Re: find -lname and -ilname implemented X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2008 18:05:05 -0000 On Sun, Feb 24, 2008 at 12:43:39PM -0700, M. Warner Losh wrote: > : > { "-empty", c_empty, f_empty, 0 }, > : > { "-exec", c_exec, f_exec, 0 }, > : > { "-execdir", c_exec, f_exec, F_EXECDIR }, > : > - { "-false", c_simple, f_not, 0 }, > : > + { "-false", c_simple, f_false, 0 }, > : > : This brakes FreeBSD compatiblity in the favor of GNU. What will > : old FreeBSD user think when his scripts will stop working > : after next cvsup? I suppose our target not to make FreeBSD > : to look like Linux. If you want to add GNU-like false option, > : please, add it under the different name. > > I considered it, but rejected it. The current -false option doesn't > make any sense at all, likely isn't used, is just a short-cut for '!' > and had a very dubious justification when it was committed. Hum... did you survey a sufficient number of folks to get a feel for its usage in the wild? Do the other BSD's have this option and how have they implemented it? Changing existing BSD behavior to match GNU seems wrong on the surface as compatibility with FreeBSD is definitely > compatibility with GNU. If you have looked into these things - cool. -- -- David (obrien@FreeBSD.org) From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 18:22:05 2008 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 15FA116A403 for ; Mon, 25 Feb 2008 18:22:05 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id F192313C43E for ; Mon, 25 Feb 2008 18:22:04 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id m1PHwf08082353 for ; Mon, 25 Feb 2008 09:58:41 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.2/8.14.1/Submit) id m1PHwfZr082352 for freebsd-hackers@freebsd.org; Mon, 25 Feb 2008 09:58:41 -0800 (PST) (envelope-from obrien) Date: Mon, 25 Feb 2008 09:58:41 -0800 From: "David O'Brien" To: freebsd-hackers@freebsd.org Message-ID: <20080225175841.GC81874@dragon.NUXI.org> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20080223155355.3f80b77f@bhuda.mired.org> <47C2520C.5080100@elischer.org> <20080225005429.38f0c91a@bhuda.mired.org> <20080225.000744.-345418608.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080225.000744.-345418608.imp@bsdimp.com> X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Subject: Re: find -lname and -ilname implemented X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2008 18:22:05 -0000 On Mon, Feb 25, 2008 at 12:07:44AM -0700, M. Warner Losh wrote: > In message: <20080225005429.38f0c91a@bhuda.mired.org> > Mike Meyer writes: > You fail to understand the complex interplay of politics here. These > people do not want to see beyond it. They want to shut you down > because you aren't using their beloved Linux. They use stupid excuses > to not do things. This is about removing barriers to entry. This > isn't about being popular. .. > : Um, if FreeBSD has to become GNU in order to win GNU users, what's the > : point? Skip the pain, switch to GNU, and get the popularity you want > : and the platform you deserve with no delay. > > Hello? BSDL calling. You left your GPL here and we don't want it. For some of these uses of FreeBSD - I really have to wonder if GNU/kFreeBSD (Debian GNU/kFreeBSD is a port that consists of GNU userland using the GNU C library on top of FreeBSD's kernel) isn't a better choice. http://www.debian.org/ports/kfreebsd-gnu/ One can keep their kernel changes private IP without worry. I doubt most companies would claim they have IP that needs protecting in their GNU userland changes. -- -- David (obrien@FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? Let's not play "Jeopardy-style quoting" From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 18:23:21 2008 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 D494B16A404 for ; Mon, 25 Feb 2008 18:23:21 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id B0DB113C4DB for ; Mon, 25 Feb 2008 18:23:21 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id m1PHiBqR081957; Mon, 25 Feb 2008 09:44:11 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.2/8.14.1/Submit) id m1PHiBZ9081956; Mon, 25 Feb 2008 09:44:11 -0800 (PST) (envelope-from obrien) Date: Mon, 25 Feb 2008 09:44:11 -0800 From: "David O'Brien" To: Adrian Chadd Message-ID: <20080225174410.GA81874@dragon.NUXI.org> Mail-Followup-To: freebsd-hackers@freebsd.org, Adrian Chadd , hackers@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: hackers@freebsd.org Subject: Re: Modular type GENERIC? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2008 18:23:21 -0000 On Sun, Feb 24, 2008 at 07:26:04PM +0900, Adrian Chadd wrote: > I was just wondering why we're not shipping a GENERIC type > configuration that simply loads the modules at startup, rather than a > statically linked kernel. I thought that was a large part of the push > for the modular framework in years past. .. > http://people.freebsd.org/~adrian/loader.conf As you've shown the magic is in the loader.conf. I don't know a good way to handle this other than attempt to load every module (like Microsoft NT installer does) - and hope the probe of a driver that doesn't claim a device doesn't leave that device in a bad state. Have you tried putting every module in /boot/kernel into loader.conf in a "load" statement? -- -- David (obrien@FreeBSD.org) From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 18:28:48 2008 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 6E10716A405 for ; Mon, 25 Feb 2008 18:28:48 +0000 (UTC) (envelope-from mwm@mired.org) Received: from mired.org (bhuda.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 0E26113C45B for ; Mon, 25 Feb 2008 18:28:47 +0000 (UTC) (envelope-from mwm@mired.org) Received: (qmail 80554 invoked from network); 25 Feb 2008 18:27:34 -0000 Received: from unknown (HELO mbook-fbsd) (192.168.195.2) by 0 with SMTP; 25 Feb 2008 18:27:34 -0000 Date: Mon, 25 Feb 2008 13:28:00 -0500 From: Mike Meyer To: "Martin Laabs" Message-ID: <20080225132800.7954bcf7@mbook-fbsd> In-Reply-To: References: Organization: Meyer Consulting X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.5; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 25 Feb 2008 18:37:25 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: emulate an end-of-media 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, 25 Feb 2008 18:28:48 -0000 On Mon, 25 Feb 2008 13:36:17 +0100 "Martin Laabs" wrote: > Hi, > > I'll write a script that back up my data on dvd-r and dvd-rams. > (And some incremental backups also at some internet storage > services.) > Therefore I'd like to use dump. It is not too hard to create > dump-volumes with fixed size through the -B option. But now > I'd like to use some sort of compression. (bzip2 seems far to be > to slow. Maybe I'll use gzip or compress) > However - with compression I can't use the -B switch of dump > because I can't be sure about the compression ratio. This means > I have to use the '-a' switch. With that switch enabled, dump > starts a new volume after it detects an EOM signal. > > Because dump itself does not support compression I have to > build a pipe like that: > dump -aL0 -f - /MYFILESYSTEM|compress -c|aespipe ...|cdrecord dev=... - > This obvisouly does not work. I tried to wrote a script that > close the pipe after the amount of compressed data reached > 4.6GB. But if I close the pipe in that script dump aborts > (because of the broken pipe) at all instead of just starting > a new volume. You might want to play with the -P option to dump. Your above could be written as: dump -aL0 -P 'compress -c' /MYFILESYSTEM | cdrecord dev=... - Assuming that compress -c & cdrecord play nice (which your magic device solution also requires), then all you need to do is make "-a" DTRT when the pipe to it's -P option is closed. Dealing with buffering could be an interesting problem in all these cases. > What I'd need is a magaic pipe device that converts a ordenary > close at the one side to an EOM at the other. > Then I could do something like this: > > dump -aL0 -f /dev/MyMagicDevice & > dd if=/dev/MyMagicDevice bs=1M count=4600|./compress -c|cdrecord dev=... - > > Before I try to write a kernel module that will do the > job (I never wrote a freebsd kernel module before but > I think it is some fun to learn that.) I want to ask if > anyone see another solution for that problem. (Maybe > patching dump - but I don't want to fudge in the CORE > source.) Your magic pipe device might be more generally useful, but I'm not sure how many commands use EOM for anything at all. On the other hand, having dump -a and -P work as expected (doesn't look like they do as of 6.2) seems to be a good thing as well. > PS: Splitting up the huge (maybe compressed) dump file (also in > stream operation) is not a good idea beacause I'd need to insert > all the media - even if I resore only a single file. Well, if -B worked on compressed output, then you could split it up on volumes, which wouldn't be quite so bad. So add making -P and -B play nice together (again, they don't seem to as of 6.2) as a possible solution. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 19:04:00 2008 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 06E7016A401 for ; Mon, 25 Feb 2008 19:04:00 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron3.sfsu.edu (iron3.sfsu.edu [130.212.10.128]) by mx1.freebsd.org (Postfix) with ESMTP id EBE3D13C4EA for ; Mon, 25 Feb 2008 19:03:59 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAH6fwkeC1Apk/2dsb2JhbACrWw Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron3.sfsu.edu with ESMTP; 25 Feb 2008 11:03:59 -0800 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF100) with ESMTP id 2008022511035735-4463 ; Mon, 25 Feb 2008 11:03:57 -0800 Date: Mon, 25 Feb 2008 11:03:57 -0800 (PST) From: KAYVEN RIESE To: Sharad Chandra In-Reply-To: <200802251440.56435.sharadc@in.niksun.com> Message-ID: References: <200802221558.42443.sharadc@in.niksun.com> <200802221437.48293.wundram@beenic.net> <200802251440.56435.sharadc@in.niksun.com> MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF100 | December 5, 2007) at 02/25/2008 11:03:57, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF312 | February 8, 2008) at 02/25/2008 11:03:58, Serialize complete at 02/25/2008 11:03:58 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, "Heiko Wundram \(Beenic\)" Subject: Re: usleep 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, 25 Feb 2008 19:04:00 -0000 On Mon, 25 Feb 2008, Sharad Chandra wrote: > ,---- [Heiko Wundram (Beenic) wrote:] > | Am Freitag, 22. Februar 2008 11:28:42 schrieb Sharad Chandra: > > I was looking some where and i found process switching time is around 10ms. > That means time slice is 10ms. say some peace of code just called usleep or > nanosleep and scheduling occurs so at least it will take 10 ms. I didn't find > sleeping more than 10 ms if usec = 1 to few us. I hope I am not pandering the obvious here, but the metric prefix "m" stands for milli. 1sec = 1 000msec 1 000 000 usec > > -- > > Thanks > Sharad Chandra > _______________________________________________ > 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" > *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 20:19:39 2008 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 D55A616A412 for ; Mon, 25 Feb 2008 20:19:39 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from mailout1.zih.tu-dresden.de (mailout1.zih.tu-dresden.de [141.30.67.72]) by mx1.freebsd.org (Postfix) with ESMTP id 654F913C469 for ; Mon, 25 Feb 2008 20:19:39 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from rmc67-31.zih.tu-dresden.de ([141.30.67.31] helo=server-n) by mailout1.zih.tu-dresden.de with esmtp (Exim 4.63) (envelope-from ) id 1JTjnS-0002fJ-Tc for freebsd-hackers@freebsd.org; Mon, 25 Feb 2008 21:19:38 +0100 Received: from martin (p5B0ED680.dip.t-dialin.net [91.14.214.128]) by server-n (Postfix) with ESMTP id 716DB100A092 for ; Mon, 25 Feb 2008 21:19:34 +0100 (CET) Date: Mon, 25 Feb 2008 21:19:33 +0100 To: "freebsd-hackers@freebsd.org" From: "Martin Laabs" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable Message-ID: User-Agent: Opera Mail/9.25 (Linux) X-TUD-Virus-Scanned: mailout1.zih.tu-dresden.de Subject: Re: emulate an end-of-media 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, 25 Feb 2008 20:19:39 -0000 Hi, On Mon, 25 Feb 2008 20:34:31 +0100, wrote: > You might want to play with the -P option to dump. Your above could be= > written as: > > dump -aL0 -P 'compress -c' /MYFILESYSTEM | cdrecord dev=3D... - Unfornunately this does not work as you expect. Dump just takes its data an pass it to the script specified to -P. It does not grab the output of the script to count the data after- wards. This means the -a option does not work at all (because a pipe has no EOM-Signal) and the -B option will limit the input data only: $ dump -0 -B 100 -P 'dd' /dev/md4 > /dev/null DUMP: Date of this level 0 dump: Mon Feb 25 21:11:40 2008 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md4 to child pipeline process DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 30022 tape blocks on 291.38 tape(s). DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] 200+0 records in 200+0 records out 102400 bytes transferred in 0.031908 secs (3209223 bytes/sec) DUMP: Closing child pipeline process DUMP: Change Volumes: Mount volume #2 DUMP: Is the new volume mounted and ready to go?: ("yes" or "no") In contrast with: $ dump -0 -B 100 -P 'compress -c' /dev/md4 | dd > /dev/null DUMP: Date of this level 0 dump: Mon Feb 25 21:12:23 2008 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md4 to child pipeline process DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 30022 tape blocks on 291.38 tape(s). DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: Closing child pipeline process DUMP: Change Volumes: Mount volume #2 DUMP: Is the new volume mounted and ready to go?: ("yes" or "no") ^C 59+1 records in 59+0 records out 30208 bytes transferred in 6.315456 secs (4783 bytes/sec) > Assuming that compress -c & cdrecord play nice (which your magic > device solution also requires) My solution can just close the pipe at the one "end" of the magic device which would be realy simple to implement in a script. Of cause cdrecord will indeet close the pipe when the media is full. But= I think the media will not be usable since there is i.e. just no more space for finalisation of the dvd. But this is not a big probleme since I can use my "count compressed data and close stdin after is reaches limit x"-script. > Well, if -B worked on compressed output, then you could split it up > on volumes, which wouldn't be quite so bad. So add making -P and -B > play nice together (again, they don't seem to as of 6.2) as a > possible solution. Yes - this would be the best solution at all. But as I wrote - the -B option only counts the data thats thrown out to stdout from dump and doesn't fetch stout again. Changing this behaviour of dump would break the backward compati- bility. (However - I could introduce a new Option i.e. -C for compress := -) But I worrie about updates with such a modified dump because I would have to patch the original dump every time after I'd updated my system. How hard is it to get those a change into the CORE-Tree when coded and tested well? Thank you, Martin L. From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 20:46:10 2008 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 BD6BA16A411 for ; Mon, 25 Feb 2008 20:46:10 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (bhuda.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 5863013C44B for ; Mon, 25 Feb 2008 20:46:09 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 88565 invoked by uid 1001); 25 Feb 2008 20:44:57 -0000 Received: from bhuda.mired.org (localhost.localdomain [127.0.0.1]) by bhuda.mired.org (tmda-ofmipd) with ESMTP; Mon, 25 Feb 2008 15:44:56 -0500 Date: Mon, 25 Feb 2008 15:44:55 -0500 To: freebsd-hackers@freebsd.org Message-ID: <20080225154455.4822e72a@bhuda.mired.org> In-Reply-To: References: Organization: Meyer Consulting X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.12; amd64-portbld-freebsd6.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAG1BMVEXguIzRkGnhyaz069mXhW0WHRnbrnR9WCQ6LB0CchNMAAACSUlEQVQ4jV2TQW7jMAxFGaPQOgQEdZaGMsgBrAvUA03dCxj1Uu4U2gfwQD7AGNax51NK07RcxXz6/CSl0Ij450vkPG1jzpIZM1UwDCl/xB14TWnNX8A00Qj5a0mnVFVbVUz4MeErea2HikSRqZzY894zwg9p2+/AtO8LzxFED+tNAUFeU29iFOLRxlZAcdo9A8wi8ZBMV4BKPde82Oxrvs6BTkulQIClte0DLFzzsKk9j1MBex8iUaP00Bd78S/muyFScrTXz6zLkEUxJp+SabQfNOs4f4Jpx5qSZ/304PWwlEWP1cOn/mJQR7EOD+uKhjcBLziuL7xoY5Xm+VFAUSw/LwwwsHEHxihpwV4EJH0xXRkbw1PkRw+X4pEuSJwBggqk+HEYKkiL5/74/nQkogigzQsAFrakxZyfw3wMIEEZPv4AWMfxwqE5GNxGaERjmH+PG8AE0L4/w9g0lsp1raLYAN5azQa+AOoO9NwcpFkTrG2VKNMNEL5UKUUAw34tha0z7onUG0oBoNtczE04GwFE3wCHc0ChezAJ6A1WMV81AtY7wDAJSlXwV+4cwBvsOsrQMRawfQEBz0deEZ7WNpV2szckIKo5VpDHDSDvF1GItwqqAlG01Hh50BGtVhuUkjkasg/14bYFGCgWg1fSWHvmOoJck2xdp9ZvZBHzDVTzX23TkrOn7qe5U2COEw5D4Vx3qEQpFY2Z/3QFnJxzp7YCmSMG19nOUoe869zZfOQb5ywQuWu0yCn5+8gxZz+BE7vG3j4/wbf4D/sXN9Wug1s7AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Delivery-Agent: TMDA/1.1.11 (Ladyburn) From: Mike Meyer Subject: Re: emulate an end-of-media 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, 25 Feb 2008 20:46:11 -0000 On Mon, 25 Feb 2008 21:19:33 +0100 "Martin Laabs" wrote: > Hi, > > On Mon, 25 Feb 2008 20:34:31 +0100, wrote: > > > You might want to play with the -P option to dump. Your above could be > > written as: > > > > dump -aL0 -P 'compress -c' /MYFILESYSTEM | cdrecord dev=... - > > Unfornunately this does not work as you expect. Actually, it works exactly as I expect. It just doesn't do what you need. I propose you fix that rather than write a magic signal propagating device. > Dump just takes > its data an pass it to the script specified to -P. > It does not grab the output of the script to count the data after- > wards. This means the -a option does not work at all (because a > pipe has no EOM-Signal) No, a pipe has a SIGPIPE signal. The fix (assuming it will work with the multi-process dump design) would be to make dump treat a sigpipe like an EOM. > and the -B option will limit the input data only: Correct. But that behavior is less desirable than fixing this to do what you want. > > > Assuming that compress -c & cdrecord play nice (which your magic > > device solution also requires) > > My solution can just close the pipe at the one "end" of the magic > device which would be realy simple to implement in a script. While you're proposing a magic device that catches sigpipe, and delivers an EOM to make dump -a happy. I'm proposing that dump catch the sigpipe, and treat it like an EOM if it has -a. This may be non-workable, in that you have to be able to tell if it was the -P process or a slave process that generated the sigpipe, but I think it's the best solution. > Of cause cdrecord will indeet close the pipe when the media is full. But > I think the media will not be usable since there is i.e. just no > more space for finalisation of the dvd. > But this is not a big probleme since I can use my "count compressed > data and close stdin after is reaches limit x"-script. That same script should work with both fixes. > > Well, if -B worked on compressed output, then you could split it up > > on volumes, which wouldn't be quite so bad. So add making -P and -B > > play nice together (again, they don't seem to as of 6.2) as a > > possible solution. > Yes - this would be the best solution at all. But as I wrote - the > -B option only counts the data thats thrown out to stdout from dump > and doesn't fetch stout again. Yup. And as I wrote, fixing this is desirable. I think fixing -a is better, but this would be nearly as good. This would involve rewriting your block-counting script in C inside dump, and having that work on the output of the -P process. > But I worrie about updates with such a modified dump because I > would have to patch the original dump every time after I'd > updated my system. > How hard is it to get those a change into the CORE-Tree when coded > and tested well? The last time I provided patches to dump (fixing -w/-W so they didn't skip every other day), it took longer for it to get MFC'ed than it did to get the patches committed in the first place. In the interim, I kept a patch file in my home directory, and would just reapply the patch after doing updating the source tree. Neither one was a major problem. If you agree that this is the better solution (if not - well, that's your choice), then don't let worries about having to maintain patches outside the tree stop you from doing it. There are tool sets for dealing with such available, either in ports or via google (haven't needed it for a while, so I'd have to look). http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 20:48:18 2008 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 7359A16A404 for ; Mon, 25 Feb 2008 20:48:18 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id E550B13C448 for ; Mon, 25 Feb 2008 20:48:17 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (adsl92-189.kln.forthnet.gr [77.49.59.189]) (authenticated bits=0) by igloo.linux.gr (8.14.1/8.14.1/Debian-9) with ESMTP id m1PKXgRx021273; Mon, 25 Feb 2008 22:33:48 +0200 Received: by kobe.laptop (Postfix, from userid 1000) id BFC4122802; Mon, 25 Feb 2008 22:33:41 +0200 (EET) Date: Mon, 25 Feb 2008 22:33:41 +0200 From: Giorgos Keramidas To: "M. Warner Losh" Message-ID: <20080225203341.GA4150@kobe.laptop> References: <200802232322.45288.jonathan+freebsd-hackers@hst.org.za> <20080223.164806.-674897155.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080223.164806.-674897155.imp@bsdimp.com> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.906, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.49, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-hackers@freebsd.org, jonathan+freebsd-hackers@hst.org.za Subject: Re: find -lname and -ilname implemented 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, 25 Feb 2008 20:48:18 -0000 On 2008-02-23 16:48, "M. Warner Losh" wrote: > In message: <200802232322.45288.jonathan+freebsd-hackers@hst.org.za> > Jonathan McKeown writes: > : Yes, where it makes sense. I'm not at all convinced that this change makes as > : much sense as you obviously think it does - especially given that it doesn't > : add previously unavailable functionality, and that we have a ports system > : which includes a patch stage for dealing with this sort of gratuitous > : non-portability in ported applications. > > The change absolutely makes sense, and so far none of the arguments > against it are really worth the time to respond to. I'm using > packages not in the ports system. Frankly, the more gratuitous > differences with the gnu tools we have, the harder the sell will be > for companies wanting to replace their Linux systems with FreeBSD > ones. The changes I made were absolutely trivial in the scheme of > things. > > This knee-jerk reaction against gnu find functionality baffles me. > The changes are trivial and make FreeBSD more compatible. It is such > an obvious no-brainer that I frankly didn't expect anybody to bat an > eye. So should I expect similar knee-jerk reactions to the just committed `finger compatibility' option to implement du -l for hardlinks? I think there *is* value in making things `less hard' for the user who migrates from Linux, as long as the cost of implementing the compatibility `shims' is not humongous. I'm completely baffled by the reactions to the recent find changes :/ From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 21:53:38 2008 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 5FA0016A406; Mon, 25 Feb 2008 21:53:38 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from falcon.cybervisiontech.com (falcon.cybervisiontech.com [217.20.163.9]) by mx1.freebsd.org (Postfix) with ESMTP id 95EB813C461; Mon, 25 Feb 2008 21:53:36 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (localhost [127.0.0.1]) by falcon.cybervisiontech.com (Postfix) with ESMTP id 0847F744002; Mon, 25 Feb 2008 23:53:35 +0200 (EET) X-Virus-Scanned: Debian amavisd-new at falcon.cybervisiontech.com Received: from falcon.cybervisiontech.com ([127.0.0.1]) by localhost (falcon.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id JA5AczlB3-xx; Mon, 25 Feb 2008 23:53:34 +0200 (EET) Received: from [10.74.68.211] (unknown [193.138.145.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by falcon.cybervisiontech.com (Postfix) with ESMTP id 65B25744001; Mon, 25 Feb 2008 23:53:33 +0200 (EET) Message-ID: <47C338D5.2080906@icyb.net.ua> Date: Mon, 25 Feb 2008 23:53:25 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.9 (X11/20071208) MIME-Version: 1.0 To: Torfinn Ingolfsen References: <1203711782.00029509.1203698401@10.7.7.3> <1203711788.00029531.1203700205@10.7.7.3> In-Reply-To: <1203711788.00029531.1203700205@10.7.7.3> References: <20080222180012.aeda99e5.torfinn.ingolfsen@broadpark.no> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-i386@freebsd.org Subject: Re: sbc: isa plug-n-play 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, 25 Feb 2008 21:53:38 -0000 on 22/02/2008 19:00 Torfinn Ingolfsen said the following: > On Fri, 22 Feb 2008 18:17:27 +0200 > Andriy Gapon wrote: > >> Everything works great. But recently I had an itch to go trough BIOS >> settings. I spotted one named "Plug-n-Play OS" and it was set to > > The BIOS setting "Plug and Play OS" usually means that the OS will do > its own little dance to set up any devices, so the bios just leaves > them alone. Yes. >> After that no joy, the soundcard stopped to work. It was detected as >> before, there is no difference in dmesg whatsoever, but it did not > > Are you sure that it was detected _exactly_ as before? With the same > irq(s), dma channels and so on? Yes, 100%, but see below. >> So I disabled the option again and everything is fine. >> Practical conclusion: don't do it. >> Question of curiosity: what is it that BIOS can do with this card that >> our driver can not ? > > Well, the bios (and acpi on systems that have it) set up devices by > assigning them irqs, io, memory and whatnot, if I undertstand this > correctly. > > My understanding is that FreeBSD uses this information to attach drivers > to the devices. If the devices are not set up correctly, FreeBSD either > might not find them or it can't use them correctly. Well, FreeBSD is a complete OS while BIOS is a small utility in NVRAM, so FreeBSD should be able and is able to do everything BIOS can and more (proprietary stuff excluded). Thank you for pointing me into the right direction - while the soundcard lines were precisely the same in both cases there were some interesting differences in other parts. Verbose dmesg with "non pnp os" bios setting: http://www.icyb.net.ua/~avg/verbose.dmesg.gz Verbose dmesg with "pnp os" bios setting: http://www.icyb.net.ua/~avg/verbose-pnp-os.dmesg.gz Diff between the former and the latter is pasted in-line at the end of this email. My understanding of that diff is the following. In the first case BIOS performs ISA PnP duties, finds the soundcard and assigns its resources (IRQ5 in particular). When the OS performs device probing and resource allocation it sees that IRQ5 is already taken. In the second case BIOS does nothing in this area. Then the OS first processes PCI devices and it assigns IRQ5 to one of the PCI devices (to avoid having to use irq sharing like it had in the previous case). Then the OS does ISA PnP probing, at this point IRQ5 is already taken. As I understand, at this moment there are actually no available IRQs that could be used by the soundcard (the card supports irqs 5,7,9,10 and they are all in use). In my opinion there should have been some kind of error here. Instead, the OS still assigns IRQ5 to the card and apparently that kind of interrupt "sharing"/assignment can not work. Some questions that I would like to ask in this regard: 1. Shouldn't FreeBSD have failed in the second case to find any resources for the soundcard? 2. Shouldn't resources for ISA PnP devices be allocated before resource allocation for PCI devices? 3. Maybe this is my own mistake? Should I mark resources used by ISA PnP devices as used by "legacy devices" in BIOS? I know this must help in my case, but my question is "must I be smart or must the OS be smart?". ============= The diff ==================================== > @@ -82,6 +82,7 @@ > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: wakeup code va 0xca041000 pa 0x1000 > +atpic: Programming IRQ9 as level/low ^^^ interesting > pci_open(1): mode 1 addr port (0x0cf8) is 0x80010014 > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) > @@ -90,8 +91,8 @@ > Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 > pci_link0: Index IRQ Rtd Ref IRQs > - Initial Probe 0 7 N 0 3 4 5 6 7 10 11 12 14 15 > - Validation 0 7 N 0 3 4 5 6 7 10 11 12 14 15 > + Initial Probe 0 5 N 0 3 4 5 6 7 10 11 12 14 15 > + Validation 0 5 N 0 3 4 5 6 7 10 11 12 14 15 > After Disable 0 255 N 0 3 4 5 6 7 10 11 12 14 15 > pci_link1: Index IRQ Rtd Ref IRQs > Initial Probe 0 10 N 0 3 4 5 6 7 10 11 12 14 15 > @@ -106,8 +107,8 @@ > Validation 0 11 N 0 3 4 5 6 7 10 11 12 14 15 > After Disable 0 255 N 0 3 4 5 6 7 10 11 12 14 15 > pci_link3: Index IRQ Rtd Ref IRQs > - Initial Probe 0 9 N 0 3 4 5 6 7 10 11 12 14 15 > - Validation 0 9 N 0 3 4 5 6 7 10 11 12 14 15 > + Initial Probe 0 7 N 0 3 4 5 6 7 10 11 12 14 15 > + Validation 0 7 N 0 3 4 5 6 7 10 11 12 14 15 > After Disable 0 255 N 0 3 4 5 6 7 10 11 12 14 15 > cpu0: on acpi0 > cpu0: switching to generic Cx mode > @@ -115,7 +116,7 @@ > pcib0: port 0xcf8-0xcff,0x4000-0x4041,0x5000-0x500f on acpi0 > ACPI: Found matching pin for 0.9.INTA at func 0: 10 > ACPI: Found matching pin for 0.10.INTA at func 0: 11 > -ACPI: Found matching pin for 0.7.INTD at func 2: 9 > +ACPI: Found matching pin for 0.7.INTD at func 2: 7 > pci0: on pcib0 > pci0: domain=0, physical bus=0 > found-> vendor=0x8086, dev=0x7190, revid=0x03 > @@ -145,10 +146,10 @@ > class=0c-03-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) > lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > - intpin=d, irq=9 > + intpin=d, irq=7 ^^^ interesting > map[20]: type I/O Port, range 32, base 0xd000, size 5, enabled > pcib0: matched entry for 0.7.INTD (src \\_SB_.PCI0.ISA_.LNKD:0) > -pcib0: slot 7 INTD routed to irq 9 via \\_SB_.PCI0.ISA_.LNKD > +pcib0: slot 7 INTD routed to irq 7 via \\_SB_.PCI0.ISA_.LNKD > found-> vendor=0x8086, dev=0x7113, revid=0x02 > domain=0, bus=0, slot=7, func=3 > class=06-80-00, hdrtype=0x00, mfdev=0 > @@ -201,7 +202,7 @@ > class=03-00-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0007, statreg=0x02b0, cachelnsz=8 (dwords) > lattimer=0x20 (960 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) > - intpin=a, irq=7 > + intpin=a, irq=5 ^^^ interesting > powerspec 2 supports D0 D1 D2 D3 current D0 > map[10]: type Prefetchable Memory, range 32, base 0xd0000000, size 27, enabled > pcib1: requested memory range 0xd0000000-0xd7ffffff: good > @@ -210,8 +211,8 @@ > map[18]: type Memory, range 32, base 0xe1000000, size 16, enabled > pcib1: requested memory range 0xe1000000-0xe100ffff: good > pcib0: matched entry for 0.1.INTA (src \\_SB_.PCI0.ISA_.LNKA:0) > -pcib0: slot 1 INTA routed to irq 7 via \\_SB_.PCI0.ISA_.LNKA > -pcib1: slot 0 INTA is routed to irq 7 > +pcib0: slot 1 INTA routed to irq 5 via \\_SB_.PCI0.ISA_.LNKA > +pcib1: slot 0 INTA is routed to irq 5 > found-> vendor=0x1002, dev=0x5940, revid=0x01 > domain=0, bus=1, slot=0, func=1 > class=03-80-00, hdrtype=0x00, mfdev=0 > @@ -222,7 +223,7 @@ > pcib1: requested memory range 0xd8000000-0xdfffffff: good > map[14]: type Memory, range 32, base 0xe1010000, size 16, enabled > pcib1: requested memory range 0xe1010000-0xe101ffff: good > -vgapci0: port 0xc000-0xc0ff mem 0xd0000000-0xd7ffffff,0xe1000000-0xe100ffff irq 7 at device 0.0 on pci1 > +vgapci0: port 0xc000-0xc0ff mem 0xd0000000-0xd7ffffff,0xe1000000-0xe100ffff irq 5 at device 0.0 on pci1 > drm0: on vgapci0 > info: [drm] AGP at 0xe2000000 16MB > info: [drm] Initialized radeon 1.25.0 20060524 > @@ -249,7 +250,7 @@ > ata1: reset tp2 stat0=00 stat1=00 devices=0x4 > ata1: [MPSAFE] > ata1: [ITHREAD] > -uhci0: port 0xd000-0xd01f irq 9 at device 7.2 on pci0 > +uhci0: port 0xd000-0xd01f irq 7 at device 7.2 on pci0 > uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xd000 > uhci0: [GIANT-LOCKED] > uhci0: [ITHREAD] > @@ -322,7 +323,6 @@ > atkbdc: atkbdc0 already exists; skipping it > sio: sio0 already exists; skipping it > pnp_identify: Trying Read_Port at 203 > -pnp_identify: Trying Read_Port at 243 > CTL0044: start dependent (0) > CTL0044: adding irq mask 0x20 > CTL0044: adding dma mask 0x2 > @@ -391,8 +391,8 @@ > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) > -sio1: irq maps: 0x21 0x29 0x21 0x21 > -sio1: irq maps: 0x21 0x29 0x21 0x21 > +sio1: irq maps: 0x1 0x9 0x1 0x1 > +sio1: irq maps: 0x1 0x9 0x1 0x1 > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > sio1: [FILTER] -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 22:00:48 2008 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 34A7116A40E for ; Mon, 25 Feb 2008 22:00:48 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from mk-outboundfilter-1.mail.uk.tiscali.com (mk-outboundfilter-1.mail.uk.tiscali.com [212.74.114.37]) by mx1.freebsd.org (Postfix) with ESMTP id C914713C4E1 for ; Mon, 25 Feb 2008 22:00:47 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) X-Trace: 48440314/mk-outboundfilter-1.mail.uk.tiscali.com/PIPEX/$INTERNET-ACCEPTED/None/62.31.10.181 X-SBRS: None X-RemoteIP: 62.31.10.181 X-IP-MAIL-FROM: xfb52@dial.pipex.com X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAACfCwkc+Hwq1/2dsb2JhbAAIq2c X-IP-Direction: OUT Received: from 62-31-10-181.cable.ubr05.edin.blueyonder.co.uk (HELO [192.168.23.2]) ([62.31.10.181]) by smtp.pipex.tiscali.co.uk with ESMTP; 25 Feb 2008 21:30:45 +0000 Message-ID: <47C33384.6040701@dial.pipex.com> Date: Mon, 25 Feb 2008 21:30:44 +0000 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20061205 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <20080225154455.4822e72a@bhuda.mired.org> In-Reply-To: <20080225154455.4822e72a@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: emulate an end-of-media 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, 25 Feb 2008 22:00:48 -0000 Mike Meyer wrote: >On Mon, 25 Feb 2008 21:19:33 +0100 "Martin Laabs" wrote: > > >>Hi, >> >>On Mon, 25 Feb 2008 20:34:31 +0100, wrote: >> >> >> >>>You might want to play with the -P option to dump. Your above could be >>>written as: >>> >>>dump -aL0 -P 'compress -c' /MYFILESYSTEM | cdrecord dev=... - >>> >>> >> Why compress? It's ancient technology and will be vastly outperformed by gzip (and bzip2 but that's slower). >>>Assuming that compress -c & cdrecord play nice (which your magic >>>device solution also requires) >>> >>> >>My solution can just close the pipe at the one "end" of the magic >>device which would be realy simple to implement in a script. >> >> > >While you're proposing a magic device that catches sigpipe, and >delivers an EOM to make dump -a happy. I'm proposing that dump catch >the sigpipe, and treat it like an EOM if it has -a. This may be >non-workable, in that you have to be able to tell if it was the -P >process or a slave process that generated the sigpipe, but I think >it's the best solution. > > Are there not (at least) two more alternatives? 1) Add gzip/zlib support to dump. That would seem easier than new devices. Then -a would just work. 2) Instead of using cdrecord directly you have a wrapper which "emulates" the dump -a behaviour by writing 650/700Mb of data using cdrecord then prompting for the next cd. You don't close the pipe, and dump should just block waiting for your "device" to be ready. Might have trouble accessing /dev/tty - not sure. --Alex From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 22:40:35 2008 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 F245916A401 for ; Mon, 25 Feb 2008 22:40:35 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from flat.berklix.org (flat.berklix.org [83.236.223.115]) by mx1.freebsd.org (Postfix) with ESMTP id 864CA13C461 for ; Mon, 25 Feb 2008 22:40:35 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A7EF5.dip.t-dialin.net [84.154.126.245]) (authenticated bits=0) by flat.berklix.org (8.13.8/8.13.8) with ESMTP id m1PMeWTi031035; Mon, 25 Feb 2008 23:40:33 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id m1PMhiJ1077054; Mon, 25 Feb 2008 23:43:44 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id m1PMhTeq016201; Mon, 25 Feb 2008 23:43:39 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200802252243.m1PMhTeq016201@fire.js.berklix.net> To: Alex Zbyslaw In-reply-to: <47C33384.6040701@dial.pipex.com> References: <20080225154455.4822e72a@bhuda.mired.org> <47C33384.6040701@dial.pipex.com> Comments: In-reply-to Alex Zbyslaw message dated "Mon, 25 Feb 2008 21:30:44 +0000." Date: Mon, 25 Feb 2008 23:43:29 +0100 From: "Julian H. Stacey" Cc: freebsd-hackers@freebsd.org Subject: Re: emulate an end-of-media 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, 25 Feb 2008 22:40:36 -0000 > Why compress? It's ancient technology and will be vastly outperformed Also some nasty person has a software patent on compress (they filed the patent application, published the code & waited some years till lots got hooked, but they didnt patent decompress algorithm & everyone decompresseed & went to better freer tools :-) Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 23:06:03 2008 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 DC54116A419 for ; Mon, 25 Feb 2008 23:06:03 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from mk-outboundfilter-1.mail.uk.tiscali.com (mk-outboundfilter-1.mail.uk.tiscali.com [212.74.114.37]) by mx1.freebsd.org (Postfix) with ESMTP id 7CCC113C4D5 for ; Mon, 25 Feb 2008 23:06:03 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) X-Trace: 48487556/mk-outboundfilter-1.mail.uk.tiscali.com/PIPEX/$INTERNET-ACCEPTED/None/62.31.10.181 X-SBRS: None X-RemoteIP: 62.31.10.181 X-IP-MAIL-FROM: xfb52@dial.pipex.com X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAIPYwkc+Hwq1/2dsb2JhbAAIq3Y X-IP-Direction: OUT Received: from 62-31-10-181.cable.ubr05.edin.blueyonder.co.uk (HELO [192.168.23.2]) ([62.31.10.181]) by smtp.pipex.tiscali.co.uk with ESMTP; 25 Feb 2008 23:06:01 +0000 Message-ID: <47C349D9.8090504@dial.pipex.com> Date: Mon, 25 Feb 2008 23:06:01 +0000 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20061205 X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <200802232322.45288.jonathan+freebsd-hackers@hst.org.za> <20080223.164806.-674897155.imp@bsdimp.com> <20080225203341.GA4150@kobe.laptop> In-Reply-To: <20080225203341.GA4150@kobe.laptop> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: find -lname and -ilname implemented 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, 25 Feb 2008 23:06:03 -0000 Giorgos Keramidas wrote: >On 2008-02-23 16:48, "M. Warner Losh" wrote: > > >>This knee-jerk reaction against gnu find functionality baffles me. >>The changes are trivial and make FreeBSD more compatible. It is such >>an obvious no-brainer that I frankly didn't expect anybody to bat an >>eye. >> >> > >So should I expect similar knee-jerk reactions to the just committed >`finger compatibility' option to implement du -l for hardlinks? > > FWIW, a vote in favour of compatibility shims. It's just a shame that this won't cut both ways - it would be nice, for example, if Linux find would implement proper units to -atime etc. The FreeBSD syntax of -atime +12h is so much nicer than -amin +720. Ah well, can but dream... --Alex From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 25 23:30:00 2008 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 B876116A402; Mon, 25 Feb 2008 23:30:00 +0000 (UTC) (envelope-from gemini@geminix.org) Received: from geminix.org (geminix.org [213.73.82.81]) by mx1.freebsd.org (Postfix) with ESMTP id 758EA13C44B; Mon, 25 Feb 2008 23:30:00 +0000 (UTC) (envelope-from gemini@geminix.org) Message-ID: <47C345C9.8010901@geminix.org> Date: Mon, 25 Feb 2008 23:48:41 +0100 From: Uwe Doering Organization: Private UNIX Site User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080129 SeaMonkey/1.1.8 (Ubuntu-1.1.8+nobinonly-0ubuntu1) MIME-Version: 1.0 To: Achim Patzner References: <20080223010856.7244.qmail@smasher.org> <20080223222733.GI12067@redundancy.redundancy.org> <31648FC5-26B9-4359-ACC8-412504D3257B@bnc.net> In-Reply-To: <31648FC5-26B9-4359-ACC8-412504D3257B@bnc.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received: from gemini by geminix.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JTm7m-000MyW-26; Tue, 26 Feb 2008 00:29:59 +0100 Cc: freebsd-hackers@freebsd.org, "David E. Thiel" Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 25 Feb 2008 23:30:00 -0000 Achim Patzner wrote: >>> article below. does anyone know how this affects eli/geli? >> >> There's fairly little any disk crypto system can do to thoroughly defend >> against this. > > Hm. Strange. Serious hardware is very well suited to do that (usually > by adding well defended crypto hardware). Keys don't have to be stored > in unsafe places. Since it hasn't been mentioned so far: There are hard disk drives that do encryption on the firmware level, so you don't have to store keys on the OS level. While this doesn't solve the problem completely it at least makes getting at the key much more difficult. You would have to somehow preserve and later get at the contents of the RAM inside the controller chip on the HDD PCB, and you probably can't risk throwing the entire HDD into liquid nitrogen because there is a good chance that it would be damaged afterwards. Hitachi makes such drives, for instance (2.5" SATA models for notebooks). There the HDD password doubles as encryption key, AFAIK. So if the data you carry around is really that sensitive I would suggest to consider that approach. Regards, Uwe -- Uwe Doering | EscapeBox - Managed On-Demand UNIX Servers gemini@geminix.org | http://www.escapebox.net From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 00:42:36 2008 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 494EC16A406 for ; Tue, 26 Feb 2008 00:42:36 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id DB46A13C46A for ; Tue, 26 Feb 2008 00:42:35 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m1Q0gRLu079303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Feb 2008 11:12:27 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org Date: Tue, 26 Feb 2008 11:12:17 +1030 User-Agent: KMail/1.9.7 References: <20080225154455.4822e72a@bhuda.mired.org> <47C33384.6040701@dial.pipex.com> In-Reply-To: <47C33384.6040701@dial.pipex.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2814839.qx05Vb5oxd"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200802261112.25449.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Alex Zbyslaw Subject: Re: emulate an end-of-media 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, 26 Feb 2008 00:42:36 -0000 --nextPart2814839.qx05Vb5oxd Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 26 Feb 2008, Alex Zbyslaw wrote: > Are there not (at least) two more alternatives? > > 1) Add gzip/zlib support to dump. That would seem easier than > new devices. Then -a would just work. > > 2) Instead of using cdrecord directly you have a wrapper which > "emulates" the dump -a behaviour by writing 650/700Mb of data using > cdrecord then prompting for the next cd. You don't close the pipe, > and dump should just block waiting for your "device" to be ready.=20 > Might have trouble accessing /dev/tty - not sure. The general solution would be nicer, then you could compress & encrypt. Although I'm not sure it's so simple as adding SIGPIPE because at the=20 end of the media the compressor will be holding some data that it has=20 read but will never make it out to the media..=20 The only way I could think to solve this was to add an argument that=20 specified a pipeline to stick after the data is generated but before=20 it's fed to the output, although even then it gets a bit gnarly..=20 =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart2814839.qx05Vb5oxd Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHw2Bx5ZPcIHs/zowRAt2pAJkBECSy5V18ViClTVmTLGsOFh4CMgCfYM12 mC3Z80jz3UweyfhAVSncFUA= =kbOz -----END PGP SIGNATURE----- --nextPart2814839.qx05Vb5oxd-- From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 04:56:29 2008 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 2919316A404 for ; Tue, 26 Feb 2008 04:56:29 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168]) by mx1.freebsd.org (Postfix) with ESMTP id F26D613C4DD for ; Tue, 26 Feb 2008 04:56:28 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by wf-out-1314.google.com with SMTP id 25so1254415wfa.7 for ; Mon, 25 Feb 2008 20:56:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=Pu2j32xBElV/9uhAR8TjGEQiCEhr469F3jdUuq11xZQ=; b=v4GW4I4MUM6MmPVnPJRiKOGuzJXVcygoCVWaIWdUOHIERx8u3qZPKrIeSeaIHH0S5nsUT6g02weKo/1wYfB2l2CW1TN9nmwjlfQOh0fEIUI6tGe65VQlMHrpiiREP5Px5lI5zaRbepoYScwWGiKCQDA9uX9GhpqJGamPNFlg2wo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=n2/IpakZahd1F1Q6AyNSNlxwQ3N0m6hr97xAstAPvraML494ppO55yGVeEVEyRFkM8XKw1rPIgfVQktj9XOYJ0IntPfN88KzQddhRYbqsL1iw+bd4Vd85W/TM0vx3YLAk4NNcHdPs5jUZk1rr1KpWG0pi719o9RPO7tlhMs4HA8= Received: by 10.142.203.13 with SMTP id a13mr3206298wfg.190.1204001788168; Mon, 25 Feb 2008 20:56:28 -0800 (PST) Received: by 10.143.125.7 with HTTP; Mon, 25 Feb 2008 20:56:28 -0800 (PST) Message-ID: Date: Tue, 26 Feb 2008 13:56:28 +0900 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: freebsd-hackers@freebsd.org, "Adrian Chadd" , hackers@freebsd.org In-Reply-To: <20080225174410.GA81874@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080225174410.GA81874@dragon.NUXI.org> X-Google-Sender-Auth: 114f56c7d8cf0a81 Cc: Subject: Re: Modular type GENERIC? 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, 26 Feb 2008 04:56:29 -0000 On 26/02/2008, David O'Brien wrote: > As you've shown the magic is in the loader.conf. I don't know a good way > to handle this other than attempt to load every module (like Microsoft NT > installer does) - and hope the probe of a driver that doesn't claim a > device doesn't leave that device in a bad state. > > Have you tried putting every module in /boot/kernel into loader.conf in a > "load" statement? I'm going to try doing that tonight. Adrian -- Adrian Chadd - adrian@freebsd.org From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 05:23:12 2008 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 499DF16A405 for ; Tue, 26 Feb 2008 05:23:12 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 1063713C4D5 for ; Tue, 26 Feb 2008 05:23:11 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.204] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id m1Q5MmMa016547; Mon, 25 Feb 2008 21:22:49 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <47C3A228.7090703@freebsd.org> Date: Mon, 25 Feb 2008 21:22:48 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Julian H. Stacey" References: <20080225154455.4822e72a@bhuda.mired.org> <47C33384.6040701@dial.pipex.com> <200802252243.m1PMhTeq016201@fire.js.berklix.net> In-Reply-To: <200802252243.m1PMhTeq016201@fire.js.berklix.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Alex Zbyslaw Subject: Re: emulate an end-of-media 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, 26 Feb 2008 05:23:12 -0000 >Why compress? It's ancient technology and will be vastly outperformed Yes, gzip or bzip2 compress better, but they also: * Are a lot slower. * Use a lot more data memory. * Require a lot more code. > Also some nasty person has a software patent on compress... That was over 20 years ago; the patent expired already. Cheers, Tim Kientzle From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 05:23:51 2008 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 7FF0916A408 for ; Tue, 26 Feb 2008 05:23:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.176]) by mx1.freebsd.org (Postfix) with ESMTP id 3B99E13C4D5 for ; Tue, 26 Feb 2008 05:23:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by el-out-1112.google.com with SMTP id r27so1721814ele.3 for ; Mon, 25 Feb 2008 21:23:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=Pu2j32xBElV/9uhAR8TjGEQiCEhr469F3jdUuq11xZQ=; b=v4GW4I4MUM6MmPVnPJRiKOGuzJXVcygoCVWaIWdUOHIERx8u3qZPKrIeSeaIHH0S5nsUT6g02weKo/1wYfB2l2CW1TN9nmwjlfQOh0fEIUI6tGe65VQlMHrpiiREP5Px5lI5zaRbepoYScwWGiKCQDA9uX9GhpqJGamPNFlg2wo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=n2/IpakZahd1F1Q6AyNSNlxwQ3N0m6hr97xAstAPvraML494ppO55yGVeEVEyRFkM8XKw1rPIgfVQktj9XOYJ0IntPfN88KzQddhRYbqsL1iw+bd4Vd85W/TM0vx3YLAk4NNcHdPs5jUZk1rr1KpWG0pi719o9RPO7tlhMs4HA8= Received: by 10.142.203.13 with SMTP id a13mr3206298wfg.190.1204001788168; Mon, 25 Feb 2008 20:56:28 -0800 (PST) Received: by 10.143.125.7 with HTTP; Mon, 25 Feb 2008 20:56:28 -0800 (PST) Message-ID: Date: Tue, 26 Feb 2008 13:56:28 +0900 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: freebsd-hackers@freebsd.org, "Adrian Chadd" , hackers@freebsd.org In-Reply-To: <20080225174410.GA81874@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080225174410.GA81874@dragon.NUXI.org> X-Google-Sender-Auth: 114f56c7d8cf0a81 Cc: Subject: Re: Modular type GENERIC? 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, 26 Feb 2008 05:23:51 -0000 On 26/02/2008, David O'Brien wrote: > As you've shown the magic is in the loader.conf. I don't know a good way > to handle this other than attempt to load every module (like Microsoft NT > installer does) - and hope the probe of a driver that doesn't claim a > device doesn't leave that device in a bad state. > > Have you tried putting every module in /boot/kernel into loader.conf in a > "load" statement? I'm going to try doing that tonight. Adrian -- Adrian Chadd - adrian@freebsd.org From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 05:27:28 2008 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 8C95A16A407 for ; Tue, 26 Feb 2008 05:27:28 +0000 (UTC) (envelope-from jonathan+freebsd-hackers@hst.org.za) Received: from hermes.hst.org.za (onix.hst.org.za [209.203.2.133]) by mx1.freebsd.org (Postfix) with ESMTP id 9A2F213C448 for ; Tue, 26 Feb 2008 05:27:26 +0000 (UTC) (envelope-from jonathan+freebsd-hackers@hst.org.za) Received: from [10.1.11.1] ([10.1.11.1]) (authenticated bits=0) by hermes.hst.org.za (8.13.8/8.13.8) with ESMTP id m1Q5J4Ij088266 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 26 Feb 2008 07:19:05 +0200 (SAST) (envelope-from jonathan+freebsd-hackers@hst.org.za) From: Jonathan McKeown To: freebsd-hackers@freebsd.org Date: Tue, 26 Feb 2008 07:27:30 +0200 User-Agent: KMail/1.9.4 References: <200802232322.45288.jonathan+freebsd-hackers@hst.org.za> <20080225203341.GA4150@kobe.laptop> <47C349D9.8090504@dial.pipex.com> In-Reply-To: <47C349D9.8090504@dial.pipex.com> X-Face: $@VrUx^RHy/}yu]jKf/<4T%/d|F+$j-Ol2"2J$q+%OK1]&/G_S9(=?utf-8?q?HkaQ*=60!=3FYOK=3FY!=27M=60C=0A=09aP=5C9nVPF8Q=7DCilHH8l=3B=7E!4?= =?utf-8?q?2HK6=273lg4J=7Daz?=@1Dqqh:J]M^"YPn*2IWrZON$1+G?oX3@ =?utf-8?q?k=230=0A=0954XDRg=3DYn=5FF-etwot4U=24b?=dTS{i X-Spam-Score: -4.399 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.61 on 209.203.2.133 Subject: Re: find -lname and -ilname implemented 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, 26 Feb 2008 05:27:28 -0000 On Tuesday 26 February 2008 01:06, Alex Zbyslaw wrote: > Giorgos Keramidas wrote: > >On 2008-02-23 16:48, "M. Warner Losh" wrote: > >>This knee-jerk reaction against gnu find functionality baffles me. > >>The changes are trivial and make FreeBSD more compatible. It is such > >>an obvious no-brainer that I frankly didn't expect anybody to bat an > >>eye. > > > >So should I expect similar knee-jerk reactions to the just committed > >`finger compatibility' option to implement du -l for hardlinks? > > FWIW, a vote in favour of compatibility shims. > > It's just a shame that this won't cut both ways - it would be nice, for > example, if Linux find would implement proper units to -atime etc. The > FreeBSD syntax of -atime +12h is so much nicer than -amin +720. Ah > well, can but dream... I replied to Giorgos and Warner off-list, but (and this is the last time I'll say it as I'm starting to get boring): I don't have a problem with compatibility shims. I would hope that the requirement for them, and also the amount of utility they add, are balanced against the extra complexity and obfuscation they cause. In the case of find, already a fearsomely complicated command, I wasn't sure the balance had been struck - although it turns out that I had misunderstood the purpose of -lname/-ilname, and I now see that as a useful (pair of) option(s). What I wasn't thrilled about, and hoped to trigger a discussion of, was the apparent suggestion that FreeBSD must be Linux-compatible at all costs because weight of numbers makes Linux and GNU a de-facto standard. That's the argument which has allowed Microsoft to dictate some really bad software choices to the rest of the world - and if you doubt the problems caused by Microsoft software, try adminning a mail server and watching the zombie spam attacks from compromised Windows PCs. I do think that where we are having problems because Linux developers are stuck in their bubble and don't understand the concept of portability, adding compatibility shims to FreeBSD should go hand-in-hand with filing bug reports and hoping they realise the world is more than just Linux (possibly a vain hope) - because there will always be some differences: and after all, it was the GNU project that came up with autoconf, wasn't it? Jonathan From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 06:46:29 2008 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 3834B16A402 for ; Tue, 26 Feb 2008 06:46:29 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail05.syd.optusnet.com.au (mail05.syd.optusnet.com.au [211.29.132.186]) by mx1.freebsd.org (Postfix) with ESMTP id C6E0713C44B for ; Tue, 26 Feb 2008 06:46:28 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail05.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m1Q6kLBt021163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Feb 2008 17:46:25 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.1) with ESMTP id m1Q6kLQP083726; Tue, 26 Feb 2008 17:46:21 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m1Q6kLDw083725; Tue, 26 Feb 2008 17:46:21 +1100 (EST) (envelope-from peter) Date: Tue, 26 Feb 2008 17:46:21 +1100 From: Peter Jeremy To: Jonathan McKeown Message-ID: <20080226064621.GA83599@server.vk2pj.dyndns.org> References: <200802232322.45288.jonathan+freebsd-hackers@hst.org.za> <20080225203341.GA4150@kobe.laptop> <47C349D9.8090504@dial.pipex.com> <200802260727.30384.jonathan+freebsd-hackers@hst.org.za> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline In-Reply-To: <200802260727.30384.jonathan+freebsd-hackers@hst.org.za> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-hackers@freebsd.org Subject: Re: find -lname and -ilname implemented 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, 26 Feb 2008 06:46:29 -0000 --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 26, 2008 at 07:27:30AM +0200, Jonathan McKeown wrote: >What I wasn't thrilled about, and hoped to trigger a discussion of, was th= e=20 >apparent suggestion that FreeBSD must be Linux-compatible at all costs=20 >because weight of numbers makes Linux and GNU a de-facto standard. Whilst I agree that people have stated that GNU/Linux is a de-facto standard, I don't believe that "FreeBSD must be Linux-compatible at all costs" is a logical consequence of this and don't believe anyone implying it in this thread. There _is_ a fine line between adding functionality because it's easy to do/provides useful functionality/ makes it easier to port code and turning FreeBSD into a BSD-licensed Linux. I would suggest that a general discussion of this boundary belongs in a distinct thread. >I do think that where we are having problems because Linux developers are= =20 >stuck in their bubble and don't understand the concept of portability, This is aided and abetted by the GNU embrace-and-extend philosophy. >hope) - because there will always be some differences: and after all, it w= as=20 >the GNU project that came up with autoconf, wasn't it? GNU autoconf may have an admirable objective but it fails dismally as a tool for assisting in the creation of portable software. Based on my recent experiences with a variety of common autoconf FOSS applications, I'd go so far as to say that it impedes portability. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHw7W9/opHv/APuIcRAtJvAJ0ZeJJphoH2WsZCwtdWBeAaBZkCWgCcDAGw EXZRLtfqb3HjIA+ARP7PtIA= =bJ/5 -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND-- From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 07:51:05 2008 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 08D9616A406 for ; Tue, 26 Feb 2008 07:51:05 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail05.syd.optusnet.com.au (mail05.syd.optusnet.com.au [211.29.132.186]) by mx1.freebsd.org (Postfix) with ESMTP id 95B1813C458 for ; Tue, 26 Feb 2008 07:51:04 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail05.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m1Q7p2aZ023738 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 26 Feb 2008 18:51:03 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.1) with ESMTP id m1Q7p2YQ084092 for ; Tue, 26 Feb 2008 18:51:02 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m1Q7p22m084091 for freebsd-hackers@freebsd.org; Tue, 26 Feb 2008 18:51:02 +1100 (EST) (envelope-from peter) Date: Tue, 26 Feb 2008 18:51:02 +1100 From: Peter Jeremy To: freebsd-hackers@freebsd.org Message-ID: <20080226075102.GE83599@server.vk2pj.dyndns.org> References: <20080225154455.4822e72a@bhuda.mired.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TakKZr9L6Hm6aLOc" Content-Disposition: inline In-Reply-To: <20080225154455.4822e72a@bhuda.mired.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Subject: Re: emulate an end-of-media 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, 26 Feb 2008 07:51:05 -0000 --TakKZr9L6Hm6aLOc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 25, 2008 at 03:44:55PM -0500, Mike Meyer wrote: >On Mon, 25 Feb 2008 21:19:33 +0100 "Martin Laabs" wrote: >> My solution can just close the pipe at the one "end" of the magic >> device which would be realy simple to implement in a script. > >While you're proposing a magic device that catches sigpipe, and >delivers an EOM to make dump -a happy. I'm proposing that dump catch >the sigpipe, and treat it like an EOM if it has -a. This may be >non-workable, in that you have to be able to tell if it was the -P >process or a slave process that generated the sigpipe, but I think >it's the best solution. I'm not sure wheher Martin is trying to create a dump that is a single logical volume split over multiple physical volumes or a multi-volume dump. In the former case, then dump doesn't need to see the physical volume changes. The downside is that a partial restore would be painful as would a media error partway through the dump. I suspect Martin is trying for the latter case - which has a number of advantages (like partial restores are much faster and a failed write can be retried on new media). But it also has some gotchas. The biggest one is that dump needs to be able to write past EOM (so it can record an end-of-volume block). This isn't a problem for physical tapes (which report a logical EOM somewhat prior to the physical EOM and will allow writing beyond the logical EOM). But it does mean that your magic device needs to be able to return EOM to dump early enough that dump can record end-of-volume and the compressor can dump that block and any trailing state before it runs out of media. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --TakKZr9L6Hm6aLOc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHw8Tm/opHv/APuIcRApYtAJ9ZiqUWBsol5FnKtUEBlyCLTMg+mACgrRtm SQJVZkeQ96ldRMQHOKXtE5Y= =8go8 -----END PGP SIGNATURE----- --TakKZr9L6Hm6aLOc-- From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 11:45:47 2008 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 C0DD2106566C; Tue, 26 Feb 2008 11:45:47 +0000 (UTC) (envelope-from gemini@geminix.org) Received: from geminix.org (geminix.org [213.73.82.81]) by mx1.freebsd.org (Postfix) with ESMTP id 8DBDF13C4F5; Tue, 26 Feb 2008 11:45:47 +0000 (UTC) (envelope-from gemini@geminix.org) Message-ID: <47C3FBE8.8010201@geminix.org> Date: Tue, 26 Feb 2008 12:45:44 +0100 From: Uwe Doering Organization: Private UNIX Site User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080129 SeaMonkey/1.1.8 (Ubuntu-1.1.8+nobinonly-0ubuntu1) MIME-Version: 1.0 To: Achim Patzner References: <20080223010856.7244.qmail@smasher.org> <20080223222733.GI12067@redundancy.redundancy.org> <31648FC5-26B9-4359-ACC8-412504D3257B@bnc.net> <47C345C9.8010901@geminix.org> <9111966B-DB9C-41E3-9D30-168D668585A9@bnc.net> In-Reply-To: <9111966B-DB9C-41E3-9D30-168D668585A9@bnc.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received: from gemini by geminix.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JTyFl-000FCr-Ho; Tue, 26 Feb 2008 12:45:45 +0100 Cc: freebsd-hackers@freebsd.org, "David E. Thiel" Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 26 Feb 2008 11:45:47 -0000 Achim Patzner wrote: > Am 25.02.2008 um 23:48 schrieb Uwe Doering: >> Since it hasn't been mentioned so far: There are hard disk drives that >> do encryption on the firmware level, so you don't have to store keys >> on the OS level. > > I wouldn't go that far as there isn't (better: I didn't find) > enough documentation on their mechanisms to satisfy my curiosity. I haven't tried so far, but perhaps they can provide additional docs or pointers to already downloadable whitebooks on request. In the past, I found a number of whitebooks on their web site detailing various aspects of their storage technology. Quite interesting stuff. :-) > You might want to take a look at eNova (http://www.enovatech.net/) > who are pointing at interesting hardware using their crypto technology. Interesting approach as well. Thanks for the pointer. However, given that notebooks are the most vulnerable group of computers in this regard, the drawback I see is that the notebook manufacturers first have to adopt this solution, since you normally cannot put such additional hardware into a notebook yourself. This restricts your choice of notebooks, and you also still have no solution for notebooks that you already have. For this reason it struck me as a clever idea to do the encryption in the HDD's firmware. This way you need no additional hardware and can equip each and every notebook sporting an SATA interface with sufficiently secure HDD encryption, without support from the notebook manufacturer because a HDD is a user replaceable part. Regards, Uwe -- Uwe Doering | EscapeBox - Managed On-Demand UNIX Servers gemini@geminix.org | http://www.escapebox.net From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 11:47:46 2008 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 A53B510658D5; Tue, 26 Feb 2008 11:47:46 +0000 (UTC) (envelope-from ap@bnc.net) Received: from bis.bonn.org (www.bis.bonn.org [217.110.117.102]) by mx1.freebsd.org (Postfix) with ESMTP id 90DDD13E3D9; Tue, 26 Feb 2008 10:28:38 +0000 (UTC) (envelope-from ap@bnc.net) X-Junk-Score: 2 [X] X-SpamCatcher-Score: 2 [X] Received: from [194.39.192.125] (account bnc-mail@mailrelay.mailomat.net HELO bnc.net) by bis.bonn.org (CommuniGate Pro SMTP 5.2c4) with ESMTPSA id 9525726; Tue, 26 Feb 2008 11:30:47 +0100 X-SpamCatcher-Score: 2 [X] Received: from [194.39.194.142] (account ap HELO wasabi.wlan.bnc.net) by bnc.net (CommuniGate Pro SMTP 5.2.0) with ESMTPSA id 3078495; Tue, 26 Feb 2008 11:28:28 +0100 Message-Id: <9111966B-DB9C-41E3-9D30-168D668585A9@bnc.net> From: Achim Patzner To: Uwe Doering In-Reply-To: <47C345C9.8010901@geminix.org> Content-Type: multipart/signed; boundary=Apple-Mail-55-228725498; micalg=sha1; protocol="application/pkcs7-signature" Mime-Version: 1.0 (Apple Message framework v919.2) Date: Tue, 26 Feb 2008 11:28:27 +0100 References: <20080223010856.7244.qmail@smasher.org> <20080223222733.GI12067@redundancy.redundancy.org> <31648FC5-26B9-4359-ACC8-412504D3257B@bnc.net> <47C345C9.8010901@geminix.org> X-Mailer: Apple Mail (2.919.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, "David E. Thiel" Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 26 Feb 2008 11:47:47 -0000 --Apple-Mail-55-228725498 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Am 25.02.2008 um 23:48 schrieb Uwe Doering: > Since it hasn't been mentioned so far: There are hard disk drives > that do encryption on the firmware level, so you don't have to store > keys on the OS level. I wouldn't go that far as there isn't (better: I didn't find) enough documentation on their mechanisms to satisfy my curiosity. You might want to take a look at eNova (http://www.enovatech.net/) who are pointing at interesting hardware using their crypto technology. Achim --Apple-Mail-55-228725498-- From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 11:51:30 2008 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 097251065770; Tue, 26 Feb 2008 11:51:30 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from mk-outboundfilter-1.mail.uk.tiscali.com (mk-outboundfilter-1.mail.uk.tiscali.com [212.74.114.37]) by mx1.freebsd.org (Postfix) with ESMTP id CA4A113DF0B; Tue, 26 Feb 2008 09:32:21 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) X-Trace: 48707078/mk-outboundfilter-1.mail.uk.tiscali.com/PIPEX/$INTERNET-ACCEPTED/None/62.31.10.181 X-SBRS: None X-RemoteIP: 62.31.10.181 X-IP-MAIL-FROM: xfb52@dial.pipex.com X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAOdqw0c+Hwq1/2dsb2JhbAAIrE8 X-IP-Direction: OUT Received: from 62-31-10-181.cable.ubr05.edin.blueyonder.co.uk (HELO [192.168.23.2]) ([62.31.10.181]) by smtp.pipex.tiscali.co.uk with ESMTP; 26 Feb 2008 09:32:19 +0000 Message-ID: <47C3DCA0.5000205@dial.pipex.com> Date: Tue, 26 Feb 2008 09:32:16 +0000 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20061205 X-Accept-Language: en MIME-Version: 1.0 To: Tim Kientzle References: <20080225154455.4822e72a@bhuda.mired.org> <47C33384.6040701@dial.pipex.com> <200802252243.m1PMhTeq016201@fire.js.berklix.net> <47C3A228.7090703@freebsd.org> In-Reply-To: <47C3A228.7090703@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: emulate an end-of-media 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, 26 Feb 2008 11:51:31 -0000 Tim Kientzle wrote: >> Why compress? It's ancient technology and will be vastly outperformed > > > Yes, gzip or bzip2 compress better, but they also: > * Are a lot slower. > * Use a lot more data memory. > * Require a lot more code. I don't understand what "a lot more code" has to do with anything. gzip/zlib is part of base and portable. In my quick tests on some real dump files, *if* you are able to specify the compression quality, then gzip -1 is both faster and better compressing than compress. If I'm reading time correctly, then gzip at any compression level used less memory than compress. bzip2 uses more memory but -9 always uses roughly the same amount of memory: ~9Mb. 180672 -r--r----- 1 root alex - 184893440 Feb 26 09:08 cartman-root.dump.0 131 {root @ ren} # time compress cartman-root.dump.0 7.948u 0.264s 0:08.93 91.8% 15+744k 0+725io 0pf+0w 92896 -r--r----- 1 root alex - 95051115 Feb 26 09:08 cartman-root.dump.0.Z 134 {root @ ren} # time gzip -1 cartman-root.dump.0 6.543u 0.288s 0:06.93 98.4% 56+585k 1+549io 2pf+0w 70368 -r--r----- 1 root alex - 71979780 Feb 26 09:08 cartman-root.dump.0.gz 137 {root @ ren} # time gzip -9 cartman-root.dump.0 44.588u 0.304s 0:46.53 96.4% 56+584k 0+494io 0pf+0w 63344 -r--r----- 1 root alex - 64800326 Feb 26 09:08 cartman-root.dump.0.gz 140 {root @ ren} # time bzip2 cartman-root.dump.0 51.327u 0.398s 0:53.44 96.7% 30+9638k 3+471io 3pf+0w 60384 -r--r----- 1 root alex - 61769750 Feb 26 09:08 cartman-root.dump.0.bz2 And for a largely text filesystem dump: 58352 -r--r----- 1 root alex - 59699200 Feb 26 09:13 cartman-var.dump.0 152 {root @ ren} # time compress cartman-var.dump.0 2.179u 0.102s 0:02.31 98.2% 15+737k 0+156io 1pf+0w 20000 -r--r----- 1 root alex - 20456769 Feb 26 09:13 cartman-var.dump.0.Z 155 {root @ ren} # time gzip -1 cartman-var.dump.0 1.441u 0.069s 0:01.53 98.0% 57+592k 0+116io 0pf+0w 14992 -r--r----- 1 root alex - 15328819 Feb 26 09:13 cartman-var.dump.0.gz 158 {root @ ren} # time gzip -9 cartman-var.dump.0 4.807u 0.062s 0:04.89 99.3% 56+583k 0+104io 0pf+0w 13424 -r--r----- 1 root alex - 13727598 Feb 26 09:13 cartman-var.dump.0.gz 161 {root @ ren} # time bzip2 cartman-var.dump.0 28.057u 0.132s 0:28.97 97.2% 30+9629k 0+91io 0pf+0w 11792 -r--r----- 1 root alex - 12052157 Feb 26 09:13 cartman-var.dump.0.bz2 --Alex From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 11:56:38 2008 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 C75291066379 for ; Tue, 26 Feb 2008 11:56:38 +0000 (UTC) (envelope-from ap@bnc.net) Received: from mailomat.net (mailomat.net [217.110.117.101]) by mx1.freebsd.org (Postfix) with ESMTP id 75EE313C746 for ; Tue, 26 Feb 2008 11:51:47 +0000 (UTC) (envelope-from ap@bnc.net) X-Mailomat-SpamCatcher-Score: 2 [X] X-Mailomat-Cloudmark-Score: 0.000000 [] Received: from [194.39.192.125] (account bnc-mail@mailrelay.mailomat.net HELO bnc.net) by mailomat.net (CommuniGate Pro SMTP 5.2.0) with ESMTPSA id 40116939; Tue, 26 Feb 2008 12:51:46 +0100 X-SpamCatcher-Score: 2 [X] Received: from [194.39.194.142] (account ap HELO wasabi.wlan.bnc.net) by bnc.net (CommuniGate Pro SMTP 5.2.0) with ESMTPSA id 3078549; Tue, 26 Feb 2008 12:51:39 +0100 Message-Id: From: Achim Patzner To: Uwe Doering In-Reply-To: <47C3FBE8.8010201@geminix.org> Content-Type: multipart/signed; boundary=Apple-Mail-56-233715870; micalg=sha1; protocol="application/pkcs7-signature" Mime-Version: 1.0 (Apple Message framework v919.2) Date: Tue, 26 Feb 2008 12:51:38 +0100 References: <20080223010856.7244.qmail@smasher.org> <20080223222733.GI12067@redundancy.redundancy.org> <31648FC5-26B9-4359-ACC8-412504D3257B@bnc.net> <47C345C9.8010901@geminix.org> <9111966B-DB9C-41E3-9D30-168D668585A9@bnc.net> <47C3FBE8.8010201@geminix.org> X-Mailer: Apple Mail (2.919.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 26 Feb 2008 11:56:40 -0000 --Apple-Mail-56-233715870 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Am 26.02.2008 um 12:45 schrieb Uwe Doering: >> You might want to take a look at eNova (http://www.enovatech.net/) >> who are pointing at interesting hardware using their crypto >> technology. > > Interesting approach as well. Thanks for the pointer. However, > given that notebooks are the most vulnerable group of computers in > this regard, the drawback I see is that the notebook manufacturers > first have to adopt this solution, since you normally cannot put > such additional hardware into a notebook yourself. I put a few of these into MSI S262 systems. But I really love my Dremel... You might consider buying barebone systems which provide an USB connector you can remove in some way. Achim Patzner --Apple-Mail-56-233715870-- From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 12:51:47 2008 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 873471065677 for ; Tue, 26 Feb 2008 12:51:47 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 4148213C442 for ; Tue, 26 Feb 2008 12:51:46 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id DA44A45F21; Tue, 26 Feb 2008 13:18:31 +0100 (CET) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 3ABA7456AB; Tue, 26 Feb 2008 13:18:25 +0100 (CET) Date: Tue, 26 Feb 2008 13:17:51 +0100 From: Pawel Jakub Dawidek To: Atom Smasher Message-ID: <20080226121750.GF77530@garage.freebsd.pl> References: <20080223010856.7244.qmail@smasher.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IU5/I01NYhRvwH70" Content-Disposition: inline In-Reply-To: <20080223010856.7244.qmail@smasher.org> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: hackers@freebsd.org Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 26 Feb 2008 12:51:47 -0000 --IU5/I01NYhRvwH70 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 23, 2008 at 02:08:54PM +1300, Atom Smasher wrote: > article below. does anyone know how this affects eli/geli? >=20 > from the geli man page: "detach - Detach the given providers, which means= =20 > remove the devfs entry and clear the keys from memory." does that mean=20 > that geli properly wipes keys from RAM when a laptop is turned off? Yes, geli tries to clear sensitive informations on detach (mostly keys). I use a script to suspend my laptop, which detach my encrypted partition before suspend. In perforce I've suspend/resume geli(8) subcommands that helps a bit here - on 'geli suspend' command the keys are cleared and all I/O requests are suspended until 'geli resume' provides proper keys. This way one doesn't have to unmount file systems to allow 'geli detach' to succeed. Of course even if keys are cleared there could still be important data in RAM (eg. file system's buffer cache). --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --IU5/I01NYhRvwH70 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHxANuForvXbEpPzQRAr6QAKDARJFmdtLKJSxWtsHELETlLlFHnACeJXLz UnN+N9kFqqQhUKvmcMgUSKU= =U6kc -----END PGP SIGNATURE----- --IU5/I01NYhRvwH70-- From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 15:17:28 2008 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 E8B841065673 for ; Tue, 26 Feb 2008 15:17:28 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.188]) by mx1.freebsd.org (Postfix) with ESMTP id 7DDD613C46A for ; Tue, 26 Feb 2008 15:17:28 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: by fk-out-0910.google.com with SMTP id b27so2785919fka.11 for ; Tue, 26 Feb 2008 07:17:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; bh=2PUOa3MOT4GKj7VEqNZri3tUV5JV21jrNWtUmWwN7Bo=; b=bk7AJMffuSy1KvZFHpljwNDv1VhHXxZo8e0Vv0BgDJd2TUIBMELhklpx8tT/VoYJjHDHm3sDIJ7Y+jNQHhq70GkRLn3AY7vaenwMYzPkdv31H+VLHLLTv7GR6be4sJAagCy6ckIpSAemvSyC8FN6GaRvcUT9iFPsksg0TCITDx0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=nyFHgs+5LPeb5ojl8n6H238i2dTeg4u7DUtshxriVBjc/8GY68Pojai4iouSnyKnt5p3hG8FELfbGDEGC8OVnolzASs22wK8cQp3xfgGGWEeKhev+oYvGPqOL2nUbOFy+tJi2XG/9ZNjyzxM8OLFSW0oJSRzE3KlP8LXRInoccc= Received: by 10.82.162.14 with SMTP id k14mr9131265bue.35.1204039046766; Tue, 26 Feb 2008 07:17:26 -0800 (PST) Received: from ?127.0.0.1? ( [217.206.187.79]) by mx.google.com with ESMTPS id q9sm5390964gve.10.2008.02.26.07.17.24 (version=SSLv3 cipher=RC4-MD5); Tue, 26 Feb 2008 07:17:25 -0800 (PST) From: Tom Evans To: cali clarke In-Reply-To: <5a08be760802241042x2cd93d63of5787a744e745fe5@mail.gmail.com> References: <5a08be760802241042x2cd93d63of5787a744e745fe5@mail.gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-eBeptl1kAAvBW3kBvHaW" Date: Tue, 26 Feb 2008 15:17:24 +0000 Message-Id: <1204039044.2126.121.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.2 FreeBSD GNOME Team Port Cc: freebsd-hackers@freebsd.org Subject: Re: Anybody have a patch for pdksh derivatives, for jails? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2008 15:17:29 -0000 --=-eBeptl1kAAvBW3kBvHaW Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2008-02-24 at 19:42 +0100, cali clarke wrote: > Hi. >=20 > pdksh and derivatives (openbsd ksh, mirbsd mksh etc) all have > the same "bug" with regards to jails. On all of my systems, trying > to start *ksh in a jail results in a message that /dev/tty could > not be opened (device busy) and that the shell will not have > job control. For some reason, this makes pretty much any > curses or screen editor fail to run. >=20 > Note that also, this problem does NOT occur if you use ssh > to enter the jail as I believe ssh handles tty allocation in > advance. >=20 > I wondered if anybody had patched their *ksh to workaround > this problem? >=20 > I've had a look at the sources myself and... ugh. The insides > of a unix shell are not something I particularly want to spend > much time examining... Running something like 'jexec 1 /bin/sh' won't allow you to allocate a tty. If instead you enable sshd inside the jail, and ssh into the jail, sshd will allocate you a tty, and everything will work normally. HTH --=-eBeptl1kAAvBW3kBvHaW Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBHxC2BlcRvFfyds/cRAqgnAJ4lIDQGbxMN2eG58bR7mYA8F0WbYQCghwCK 0G7CqZ4VyPoqJLfxrEoYS3w= =FLJ0 -----END PGP SIGNATURE----- --=-eBeptl1kAAvBW3kBvHaW-- From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 18:45:08 2008 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 11EA2106566B for ; Tue, 26 Feb 2008 18:45:08 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from mailout2.zih.tu-dresden.de (mailout2.zih.tu-dresden.de [141.30.67.73]) by mx1.freebsd.org (Postfix) with ESMTP id BD15113C448 for ; Tue, 26 Feb 2008 18:45:07 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from rmc67-31.zih.tu-dresden.de ([141.30.67.31] helo=server-n) by mailout2.zih.tu-dresden.de with esmtp (Exim 4.63) (envelope-from ) id 1JU4nW-0006U6-6Q for freebsd-hackers@freebsd.org; Tue, 26 Feb 2008 19:45:06 +0100 Received: from martin (p5B0ED270.dip.t-dialin.net [91.14.210.112]) by server-n (Postfix) with ESMTP id BD048100A08E for ; Tue, 26 Feb 2008 19:44:49 +0100 (CET) To: "freebsd-hackers@freebsd.org" From: "Martin Laabs" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 In-Reply-To: <47C3A228.7090703@freebsd.org> References: <20080225154455.4822e72a@bhuda.mired.org> <47C33384.6040701@dial.pipex.com> <200802252243.m1PMhTeq016201@fire.js.berklix.net> <47C3A228.7090703@freebsd.org> Content-Transfer-Encoding: Quoted-Printable Date: Tue, 26 Feb 2008 19:44:48 +0100 Message-ID: User-Agent: Opera Mail/9.25 (Linux) X-TUD-Virus-Scanned: mailout2.zih.tu-dresden.de Subject: Re: emulate an end-of-media 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, 26 Feb 2008 18:45:08 -0000 Hi, > Yes, gzip or bzip2 compress better, but they also: > * Are a lot slower. Yesterday I made a comparison regarding the speed of compress, bzip2 and gzip. And actually compress is much slower than gzip: $ dd if=3D/dev/random |compress -c > /dev/null 3883204 bytes/sec $ dd if=3D/dev/random |gzip -c > /dev/null 8357889 bytes/sec $ dd if=3D/dev/random |bzip2 -c > /dev/null 1042735 bytes/sec I also made a comparison between gzip and bzip2 regarding the compression ratio on a dump of my home directory (3.2GB) bzip2 took about 74min to compress, gzip only 11minutes. And in terms of compression ratio bzip2 was only 3% better than gzip. Best greet, Martin L. From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 18:45:09 2008 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 7705B1065671 for ; Tue, 26 Feb 2008 18:45:09 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from mailout2.zih.tu-dresden.de (mailout2.zih.tu-dresden.de [141.30.67.73]) by mx1.freebsd.org (Postfix) with ESMTP id 2EB2813C457 for ; Tue, 26 Feb 2008 18:45:09 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from rmc67-31.zih.tu-dresden.de ([141.30.67.31] helo=server-n) by mailout2.zih.tu-dresden.de with esmtp (Exim 4.63) (envelope-from ) id 1JU4nY-0006bE-5C for freebsd-hackers@freebsd.org; Tue, 26 Feb 2008 19:45:08 +0100 Received: from martin (p5B0ED270.dip.t-dialin.net [91.14.210.112]) by server-n (Postfix) with ESMTP id EAB56100A092 for ; Tue, 26 Feb 2008 19:45:03 +0100 (CET) To: "freebsd-hackers@freebsd.org" From: "Martin Laabs" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 In-Reply-To: <20080226075102.GE83599@server.vk2pj.dyndns.org> References: <20080225154455.4822e72a@bhuda.mired.org> <20080226075102.GE83599@server.vk2pj.dyndns.org> Content-Transfer-Encoding: 7bit Date: Tue, 26 Feb 2008 19:45:03 +0100 Message-ID: User-Agent: Opera Mail/9.25 (Linux) X-TUD-Virus-Scanned: mailout2.zih.tu-dresden.de Subject: Re: emulate an end-of-media 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, 26 Feb 2008 18:45:09 -0000 Hi, > I'm not sure wheher Martin is trying to create a dump that is a single > logical volume split over multiple physical volumes or a multi-volume > dump. I want to make a real multi-volume dump over multiple media. Because if I had only one big volume I'd - in the worst case - have to insert all media also if i want to recover only one file. And worser: I'd had to read and decompress all media up to the end. I could of cause use another backup backend but I think dump is one of the best and reliablest backup mechanism. (Because it works on inode-basis and not the user file-system level.) > I suspect Martin is trying for the latter case - which has a number of > advantages (like partial restores are much faster and a failed write > can be retried on new media). But it also has some gotchas. The > biggest one is that dump needs to be able to write past EOM (so it can > record an end-of-volume block). Oh - that are bad news. Do you know how many blocks/bytes dump needs afterwards? > [...] But it does mean that > your magic device needs to be able to return EOM to dump early enough > that dump can record end-of-volume and the compressor can dump that > block and any trailing state before it runs out of media. And it makes the idea to convert a sigpipe to an EOM useless. I've to think about that. (I thought I could just change dump in that way that it handle a sigpipe like an EOM which would be very easy.) Maybe I now have to implement the output byte counting of the script or pipe specified by -P when -B was given. Thak you, Martin L. From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 18:45:40 2008 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 832171065677 for ; Tue, 26 Feb 2008 18:45:40 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from mailout1.zih.tu-dresden.de (mailout1.zih.tu-dresden.de [141.30.67.72]) by mx1.freebsd.org (Postfix) with ESMTP id 3BBA913C465 for ; Tue, 26 Feb 2008 18:45:40 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from rmc67-31.zih.tu-dresden.de ([141.30.67.31] helo=server-n) by mailout1.zih.tu-dresden.de with esmtp (Exim 4.63) (envelope-from ) id 1JU4o2-0001pr-KY for freebsd-hackers@freebsd.org; Tue, 26 Feb 2008 19:45:38 +0100 Received: from martin (p5B0ED270.dip.t-dialin.net [91.14.210.112]) by server-n (Postfix) with ESMTP id 6FEA3100A08E for ; Tue, 26 Feb 2008 19:45:34 +0100 (CET) To: "freebsd-hackers@freebsd.org" From: "Martin Laabs" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 In-Reply-To: <20080226075102.GE83599@server.vk2pj.dyndns.org> References: <20080225154455.4822e72a@bhuda.mired.org> <20080226075102.GE83599@server.vk2pj.dyndns.org> Content-Transfer-Encoding: 7bit Date: Tue, 26 Feb 2008 19:45:33 +0100 Message-ID: User-Agent: Opera Mail/9.25 (Linux) X-TUD-Virus-Scanned: mailout1.zih.tu-dresden.de Subject: Re: emulate an end-of-media 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, 26 Feb 2008 18:45:40 -0000 Hi, On Tue, 26 Feb 2008 08:51:02 +0100, Peter Jeremy wrote: > [...] But it also has some gotchas. The > biggest one is that dump needs to be able to write past EOM (so it can > record an end-of-volume block). Just even I tried the following: -create a 50MB filesystem (with md) -put 29MB data on it -create 3 10MB md-devices -dump the 50MB filesystem at the three 10MB devices -restore the file into another, fresh 50MB filesystem Restore reported no error, all files are there and the number of used inodes is the same. Also the md5 checksum above all files does not differ. Since I'm almost sure that the md-devices does not allow to write behind the EOM signal this test would be an equvilalent to the SIGPIPE to SIGEOM thing. (Regardless how I implement this at the end.) So it doesn't seem that dump can handle such an abrupt EOM. This evening I'll try to change dump to interprete SIGPIPE like SIGEOM. Best regards, Martin L. From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 18:46:28 2008 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 DA34E106566B for ; Tue, 26 Feb 2008 18:46:28 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from mailout2.zih.tu-dresden.de (mailout2.zih.tu-dresden.de [141.30.67.73]) by mx1.freebsd.org (Postfix) with ESMTP id 9101913C474 for ; Tue, 26 Feb 2008 18:46:28 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from rmc67-31.zih.tu-dresden.de ([141.30.67.31] helo=server-n) by mailout2.zih.tu-dresden.de with esmtp (Exim 4.63) (envelope-from ) id 1JU4op-0006cY-G0 for freebsd-hackers@freebsd.org; Tue, 26 Feb 2008 19:46:27 +0100 Received: from martin (p5B0ED270.dip.t-dialin.net [91.14.210.112]) by server-n (Postfix) with ESMTP id 48B3F100A08E for ; Tue, 26 Feb 2008 19:46:23 +0100 (CET) To: "freebsd-hackers@freebsd.org" From: "Martin Laabs" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 In-Reply-To: <47C345C9.8010901@geminix.org> References: <20080223010856.7244.qmail@smasher.org> <20080223222733.GI12067@redundancy.redundancy.org> <31648FC5-26B9-4359-ACC8-412504D3257B@bnc.net> <47C345C9.8010901@geminix.org> Date: Tue, 26 Feb 2008 19:46:22 +0100 Message-ID: User-Agent: Opera Mail/9.25 (Linux) Content-Transfer-Encoding: quoted-printable X-TUD-Virus-Scanned: mailout2.zih.tu-dresden.de Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 26 Feb 2008 18:46:29 -0000 Hi, Maybe someone could implement a memory section that is overwritten by the bios after reboot. Then all the sensitive keys could be stored there. This would prevent an attack that just boots from another media and dump the whole memory out of i.e. an USB-stick. Preventing the physical access to the memory modules could be done with a light sensor or a simple switch at the computer case. If you implement also a temperature- sensor near the memory-modules you could prevent cooling them down before removal. (You'd just overwrite the keys if the temperature falls i.e. below 10=B0C) Greets, Martin L. From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 19:08:13 2008 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 808A0106566B; Tue, 26 Feb 2008 19:08:13 +0000 (UTC) (envelope-from gregoryd.freebsd@free.fr) Received: from postfix1-g20.free.fr (postfix1-g20.free.fr [212.27.60.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0AF9613C4CE; Tue, 26 Feb 2008 19:08:12 +0000 (UTC) (envelope-from gregoryd.freebsd@free.fr) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by postfix1-g20.free.fr (Postfix) with ESMTP id 9B84A232A9BC; Tue, 26 Feb 2008 19:42:26 +0100 (CET) Received: from smtp1-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp1-g19.free.fr (Postfix) with ESMTP id A5E981AB2B2; Tue, 26 Feb 2008 19:42:24 +0100 (CET) Received: from imp8-g19.free.fr (imp8-g19.free.fr [212.27.42.39]) by smtp1-g19.free.fr (Postfix) with ESMTP id 3511E1AB30D; Tue, 26 Feb 2008 19:42:24 +0100 (CET) Received: by imp8-g19.free.fr (Postfix, from userid 33) id 3B2AF3DD1; Tue, 26 Feb 2008 19:42:18 +0100 (CET) Received: from 145.242.11.2 ([145.242.11.2]) by imp.free.fr (IMP) with HTTP for ; Tue, 26 Feb 2008 19:42:17 +0100 Message-ID: <1204051337.47c45d89ea6eb@imp.free.fr> Date: Tue, 26 Feb 2008 19:42:17 +0100 From: gregoryd.freebsd@free.fr To: Eygene Ryabinkin References: <20080223010856.7244.qmail@smasher.org> <47C068B5.2090000@thedarkside.nl> <20080223185620.GA98105@eos.sc1.parodius.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.8 X-Originating-IP: 145.242.11.2 Cc: Jeremy Chadwick , hackers@freebsd.org, Pieter de Boer , Atom Smasher Subject: Re: Zeroing sensitive memory chunks [Was: Security Flaw in Popular Disk Encryption Technologies] 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, 26 Feb 2008 19:08:13 -0000 Quoting Eygene Ryabinkin : > *) New function OPENSSL_cleanse(), which is used to cleanse a section of > memory from it's contents. This is done with a counter that will > place alternating values in each byte. This can be used to solve > two issues: 1) the removal of calls to memset() by highly optimizing > compilers, and 2) cleansing with other values than 0, since those can > be read through on certain media, for example a swap space on disk. > [Geoff Thorpe] > > The '1)' is what I was talking about. '2)' is not very clear to > me now, I should research what Geoff meant. If anyone has an idea, > please comment. I thought it might mean that on certain media, such as disks, data can be read even after it has been overwriten a certain number of times (magnetic properties of the media, this is a method used by some police labs to recover lost data, I've been told, but maybe the man was just a paranoid). So even "cleansing" a crypted swap space this way would not render it safe (you would have to repeat it enough times so that the layers are definitively overwritten) Now I am no physics/chemics specialist, and this might not be the meaning of Geoff Thorpe: anyway you asked for an idea :-) And I would also like to know the end of it... gregory From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 19:23:23 2008 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 84891106566B for ; Tue, 26 Feb 2008 19:23:23 +0000 (UTC) (envelope-from pav@FreeBSD.org) Received: from raven.customer.vol.cz (raven.customer.vol.cz [195.250.144.108]) by mx1.freebsd.org (Postfix) with ESMTP id F064B13C478 for ; Tue, 26 Feb 2008 19:23:22 +0000 (UTC) (envelope-from pav@FreeBSD.org) Received: from [192.168.0.23] (rb5dg130.net.upc.cz [89.176.238.130]) (authenticated bits=0) by raven.customer.vol.cz (8.14.1/8.14.1) with ESMTP id m1QJN6MP042289; Tue, 26 Feb 2008 20:23:09 +0100 (CET) (envelope-from pav@FreeBSD.org) From: Pav Lucistnik To: Andriy Gapon In-Reply-To: <1202235368.68281.12.camel@ikaros.oook.cz> References: <200612221824.kBMIOhfM049471@freefall.freebsd.org> <47A2EDB0.8000801@icyb.net.ua> <47A2F404.7010208@icyb.net.ua> <47A735A4.3060506@icyb.net.ua> <47A75B47.2040604@elischer.org> <1202155663.62432.0.camel@ikaros.oook.cz> <47A8754C.5010607@icyb.net.ua> <1202235368.68281.12.camel@ikaros.oook.cz> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-SccF/h9dD4yQBrgLXecY" Date: Tue, 26 Feb 2008 20:23:06 +0100 Message-Id: <1204053786.1799.0.camel@ikaros.oook.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 FreeBSD GNOME Team Port X-Spam-Score: -2.556 () AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 195.250.144.108 X-Milter: Spamilter (Reciever: raven.customer.vol.cz; Sender-ip: 89.176.238.130; Sender-helo: [192.168.0.23]; ) Cc: Bruce Evans , freebsd-hackers@FreeBSD.org, scottl@FreeBSD.org, freebsd-fs@FreeBSD.org, Julian Elischer , Remko Lodder Subject: Re: fs/udf: vm pages "overlap" while reading large dir [patch] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pav@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2008 19:23:23 -0000 --=-SccF/h9dD4yQBrgLXecY Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable Pav Lucistnik p=ED=B9e v =FAt 05. 02. 2008 v 19:16 +0100: > Andriy Gapon p=ED=B9e v =FAt 05. 02. 2008 v 16:40 +0200: >=20 > > > Yay, and can you fix the sequential read performance while you're at = it? > > > Kthx! >=20 > > this was almost trivial :-) > > See the attached patch, first hunk is just for consistency. > > The code was borrowed from cd9660, only field/variable names are adjust= ed. Just tested it with my shiny new Bluray drive, and it work wonders. Finally seamless playback of media files off UDF carrying media. So, how does it look WRT committing it? --=20 Pav Lucistnik Somebody ought to cross ball point pens with coat hangers so that the pens will multiply instead of disappear. --=-SccF/h9dD4yQBrgLXecY Content-Type: application/pgp-signature; name=signature.asc Content-Description: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEABECAAYFAkfEZxcACgkQntdYP8FOsoKvjQCcDDNmE1Ym815jgDNPmw7Xnyvn jLUAn0KZCW73j0nJqlQAyoay/ucksU2E =TBsO -----END PGP SIGNATURE----- --=-SccF/h9dD4yQBrgLXecY-- From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 19:49:41 2008 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 36CBD1065672; Tue, 26 Feb 2008 19:49:41 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id D69D113C455; Tue, 26 Feb 2008 19:49:40 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender:X-Spam-Status:Subject; b=pD8TR1CjRB9C3sSzWfVTbPtGnEGNyl0XjdirWpmsDCiBAPKhwTbKJNvNBPzgLjqq4sM3thv2fRWWjgH8o6YTXOfuV0uR6ok8jWQ0KttAhkBk44sWMk/m2b0/jCa56CsKVTOdKUHQb7wI62R2cxtPDjLmsE4EYDrylaj6NesXHxs=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1JU5o3-000GaV-8B; Tue, 26 Feb 2008 22:49:39 +0300 Date: Tue, 26 Feb 2008 22:49:37 +0300 From: Eygene Ryabinkin To: gregoryd.freebsd@free.fr Message-ID: References: <20080223010856.7244.qmail@smasher.org> <47C068B5.2090000@thedarkside.nl> <20080223185620.GA98105@eos.sc1.parodius.com> <1204051337.47c45d89ea6eb@imp.free.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <1204051337.47c45d89ea6eb@imp.free.fr> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-1.7 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_50 Cc: Jeremy Chadwick , hackers@freebsd.org, Pieter de Boer , Atom Smasher Subject: Re: Zeroing sensitive memory chunks [Was: Security Flaw in Popular Disk Encryption Technologies] 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, 26 Feb 2008 19:49:41 -0000 Gregory, good day. Tue, Feb 26, 2008 at 07:42:17PM +0100, gregoryd.freebsd@free.fr wrote: > Quoting Eygene Ryabinkin : > > > *) New function OPENSSL_cleanse(), which is used to cleanse a section of > > memory from it's contents. This is done with a counter that will > > place alternating values in each byte. This can be used to solve > > two issues: 1) the removal of calls to memset() by highly optimizing > > compilers, and 2) cleansing with other values than 0, since those can > > be read through on certain media, for example a swap space on disk. > > [Geoff Thorpe] > > > > The '1)' is what I was talking about. '2)' is not very clear to > > me now, I should research what Geoff meant. If anyone has an idea, > > please comment. > > I thought it might mean that on certain media, such as disks, data > can be read even after it has been overwriten a certain number of > times (magnetic properties of the media, this is a method used by > some police labs to recover lost data, I've been told, but maybe > the man was just a paranoid). So even "cleansing" a crypted swap > space this way would not render it safe (you would have to repeat > it enough times so that the layers are definitively overwritten) Yes, Geoff just responded to my private question: it was Peter Gutmann, who pointed him to the thing you're talking about. There is a paper by Peter, http://www.usenix.org/publications/library/proceedings/sec96/full_papers/gutmann/ I still don't understand how cleaning of a memory area will help to clean the swapped page, but may be there are some systems which will update the swapped page on the memory access. May be this even called 'read-through' -- I really don't know. Perhaps this will help for the memory-mapped files, but may be not: the system's write cache can collapse many successive overwrites to just one. The mmap'ped files are using the write cache, aren't they? Thanks for the comment! -- Eygene From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 20:22:11 2008 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 A30B6106566C for ; Tue, 26 Feb 2008 20:22:11 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.189]) by mx1.freebsd.org (Postfix) with ESMTP id 2953513C4EF for ; Tue, 26 Feb 2008 20:22:10 +0000 (UTC) (envelope-from xorquewasp@googlemail.com) Received: by mu-out-0910.google.com with SMTP id w9so3030817mue.6 for ; Tue, 26 Feb 2008 12:22:09 -0800 (PST) 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=MM4m5rfxAVuv3KbT1RFtz0v4sh2QUOD9c9iJqgaHB34=; b=cj7pJWwVOIYWMzJCuYY8+kClSDMfBAFi0f433dofmnHp7lmOIo7lwTxjknuyWw/fO/NpRgG2FjraG/VZg63ZbwE7NR4OFMu3UgjimSErwk6VzQEV8HjcVOK97zMB+gNOZ7SVCd9JQAe79xYUHd5ImSKTThAPA4gbnXcbtKsVDT8= 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=HaDeaC7lRxUCDFsmOcyDVpB/MoUtSeahqSAmykNJM0ZVmImVhtqgbRzDnfC5imVM0u27QqFpKlHiGTDSQnXIslyvKtdQK+jDA5LMMM7+PEwiFfRiNykluRn7jej67YPjGh7ETzMA8FtR/x3nIF++ykfkMh8BYUQysxK8dhXXkYE= Received: by 10.82.151.14 with SMTP id y14mr9961879bud.19.1204057329389; Tue, 26 Feb 2008 12:22:09 -0800 (PST) Received: from logik.internal.network ( [81.86.41.187]) by mx.google.com with ESMTPS id y34sm11816943iky.6.2008.02.26.12.22.06 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Feb 2008 12:22:08 -0800 (PST) Received: by logik.internal.network (Postfix, from userid 11001) id 00F205D2E; Tue, 26 Feb 2008 20:22:02 +0000 (UTC) Date: Tue, 26 Feb 2008 20:22:02 +0000 From: xorquewasp@googlemail.com To: Tom Evans Message-ID: <20080226202202.GA96964@logik.internal.network> References: <5a08be760802241042x2cd93d63of5787a744e745fe5@mail.gmail.com> <1204039044.2126.121.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1204039044.2126.121.camel@localhost> Cc: freebsd-hackers@freebsd.org Subject: Re: Anybody have a patch for pdksh derivatives, for jails? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2008 20:22:11 -0000 On 20080226 15:17:24, Tom Evans wrote: > Running something like 'jexec 1 /bin/sh' won't allow you to allocate a > tty. If instead you enable sshd inside the jail, and ssh into the jail, > sshd will allocate you a tty, and everything will work normally. Hi. As I mentioned in my first email, the issue isn't precisely that a tty isn't allocated, it's that *ksh does extra pedantic checking to discover whether or not it really does have a controlling terminal. The restrictions that exist in jails (eg. not being able to open /dev/tty) cause the shell to believe that it doesn't have a controlling terminal. The shells in base don't do this extra checking and therefore work fine. This is simply an OS specific artifact that the *ksh authors couldn't possibly have forseen! Given that it seems nobody has patched *ksh to work in a jail, I'll try myself. I expect the easiest way will be to add a command line flag that says "I really do have a controlling terminal". Thanks anyway. From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 20:29:53 2008 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 188D7106566C for ; Tue, 26 Feb 2008 20:29:53 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from www.pkgsrc-box.org (www.ostsee-abc.de [62.206.222.50]) by mx1.freebsd.org (Postfix) with ESMTP id B00C313C465 for ; Tue, 26 Feb 2008 20:29:52 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (www.pkgsrc-box.org [127.0.0.1]) by www.pkgsrc-box.org (Postfix) with ESMTP id 4DD07E7A3E0 for ; Tue, 26 Feb 2008 20:29:51 +0000 (UTC) Received: by britannica.bec.de (Postfix, from userid 1000) id 53E31175D0; Tue, 26 Feb 2008 21:28:53 +0100 (CET) Date: Tue, 26 Feb 2008 21:28:53 +0100 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Message-ID: <20080226202853.GA859@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20080225154455.4822e72a@bhuda.mired.org> <47C33384.6040701@dial.pipex.com> <200802252243.m1PMhTeq016201@fire.js.berklix.net> <47C3A228.7090703@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Subject: Re: emulate an end-of-media 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, 26 Feb 2008 20:29:53 -0000 On Tue, Feb 26, 2008 at 07:44:48PM +0100, Martin Laabs wrote: > I also made a comparison between gzip and bzip2 regarding > the compression ratio on a dump of my home directory (3.2GB) > bzip2 took about 74min to compress, gzip only 11minutes. And > in terms of compression ratio bzip2 was only 3% better than > gzip. That's not a realistic test case. bzip2 normally takes trice the time and compresses 10% better. I can't comment on compress. Joerg From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 26 21:01:14 2008 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 0AC101065675 for ; Tue, 26 Feb 2008 21:01:14 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (bhuda.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 98BE013C469 for ; Tue, 26 Feb 2008 21:01:13 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 41566 invoked by uid 1001); 26 Feb 2008 21:00:02 -0000 Received: from bhuda.mired.org (localhost.localdomain [127.0.0.1]) by bhuda.mired.org (tmda-ofmipd) with ESMTP; Tue, 26 Feb 2008 16:00:01 -0500 Date: Tue, 26 Feb 2008 16:00:00 -0500 To: freebsd-hackers@freebsd.org Message-ID: <20080226160000.624c5d0f@bhuda.mired.org> In-Reply-To: <20080226202853.GA859@britannica.bec.de> References: <20080225154455.4822e72a@bhuda.mired.org> <47C33384.6040701@dial.pipex.com> <200802252243.m1PMhTeq016201@fire.js.berklix.net> <47C3A228.7090703@freebsd.org> <20080226202853.GA859@britannica.bec.de> Organization: Meyer Consulting X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.12; amd64-portbld-freebsd6.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAG1BMVEXguIzRkGnhyaz069mXhW0WHRnbrnR9WCQ6LB0CchNMAAACSUlEQVQ4jV2TQW7jMAxFGaPQOgQEdZaGMsgBrAvUA03dCxj1Uu4U2gfwQD7AGNax51NK07RcxXz6/CSl0Ij450vkPG1jzpIZM1UwDCl/xB14TWnNX8A00Qj5a0mnVFVbVUz4MeErea2HikSRqZzY894zwg9p2+/AtO8LzxFED+tNAUFeU29iFOLRxlZAcdo9A8wi8ZBMV4BKPde82Oxrvs6BTkulQIClte0DLFzzsKk9j1MBex8iUaP00Bd78S/muyFScrTXz6zLkEUxJp+SabQfNOs4f4Jpx5qSZ/304PWwlEWP1cOn/mJQR7EOD+uKhjcBLziuL7xoY5Xm+VFAUSw/LwwwsHEHxihpwV4EJH0xXRkbw1PkRw+X4pEuSJwBggqk+HEYKkiL5/74/nQkogigzQsAFrakxZyfw3wMIEEZPv4AWMfxwqE5GNxGaERjmH+PG8AE0L4/w9g0lsp1raLYAN5azQa+AOoO9NwcpFkTrG2VKNMNEL5UKUUAw34tha0z7onUG0oBoNtczE04GwFE3wCHc0ChezAJ6A1WMV81AtY7wDAJSlXwV+4cwBvsOsrQMRawfQEBz0deEZ7WNpV2szckIKo5VpDHDSDvF1GItwqqAlG01Hh50BGtVhuUkjkasg/14bYFGCgWg1fSWHvmOoJck2xdp9ZvZBHzDVTzX23TkrOn7qe5U2COEw5D4Vx3qEQpFY2Z/3QFnJxzp7YCmSMG19nOUoe869zZfOQb5ywQuWu0yCn5+8gxZz+BE7vG3j4/wbf4D/sXN9Wug1s7AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Delivery-Agent: TMDA/1.1.11 (Ladyburn) From: Mike Meyer Subject: Re: emulate an end-of-media 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, 26 Feb 2008 21:01:14 -0000 On Tue, 26 Feb 2008 21:28:53 +0100 Joerg Sonnenberger wrote: > On Tue, Feb 26, 2008 at 07:44:48PM +0100, Martin Laabs wrote: > > I also made a comparison between gzip and bzip2 regarding > > the compression ratio on a dump of my home directory (3.2GB) > > bzip2 took about 74min to compress, gzip only 11minutes. And > > in terms of compression ratio bzip2 was only 3% better than > > gzip. > That's not a realistic test case. bzip2 normally takes trice the time > and compresses 10% better. I can't comment on compress. Considering we're talking about compression methods to use on dump output, that would seem to be the definition of a "realistic test case". Telling us what it "normally" does without defining what input is considered "normal" doesn't help much. In any case, this is a good argument for using -P, and letting the end user choose the compression tool they want. gzip if they want speed, bzip2 if they want better compression, compress if they want portability back to 4BSD, or next years superduperzipper. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 00:30:18 2008 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 2CBCB1065670 for ; Wed, 27 Feb 2008 00:30:18 +0000 (UTC) (envelope-from fbsd06+TQ=e8b94b1b@mlists.homeunix.com) Received: from turtle-out.mxes.net (turtle-out.mxes.net [216.86.168.191]) by mx1.freebsd.org (Postfix) with ESMTP id EBD9713C458 for ; Wed, 27 Feb 2008 00:30:17 +0000 (UTC) (envelope-from fbsd06+TQ=e8b94b1b@mlists.homeunix.com) Received: from mxout-04.mxes.net (mxout-04.mxes.net [216.86.168.179]) by turtle-in.mxes.net (Postfix) with ESMTP id D0905164694 for ; Tue, 26 Feb 2008 19:12:28 -0500 (EST) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 431A0D05A6 for ; Tue, 26 Feb 2008 19:12:27 -0500 (EST) Date: Wed, 27 Feb 2008 00:12:23 +0000 From: RW To: freebsd-hackers@freebsd.org Message-ID: <20080227001223.5fa02d7d@gumby.homeunix.com.> In-Reply-To: References: <20080223010856.7244.qmail@smasher.org> <47C068B5.2090000@thedarkside.nl> <20080223185620.GA98105@eos.sc1.parodius.com> <1204051337.47c45d89ea6eb@imp.free.fr> X-Mailer: Claws Mail 3.3.0 (GTK+ 2.12.8; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Zeroing sensitive memory chunks [Was: Security Flaw in Popular Disk Encryption Technologies] 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, 27 Feb 2008 00:30:18 -0000 On Tue, 26 Feb 2008 22:49:37 +0300 Eygene Ryabinkin wrote: > Yes, Geoff just responded to my private question: it was Peter > Gutmann, who pointed him to the thing you're talking about. There > is a paper by Peter, > http://www.usenix.org/publications/library/proceedings/sec96/full_papers/gutmann/ There's an updated copy of this paper on Gutmann's site that points-out that he was writing about devices that were being decommissioned in the early nineties, and that he's sceptical about anything being recovered from modern drives once they have been overwritten - even once. The idea that that forensic scientists use this kind of technique to recover deleted files is a myth. > I still don't understand how cleaning of a memory area will help > to clean the swapped page, but may be there are some systems which > will update the swapped page on the memory access. That shouldn't be an issue since it's easy to encrypt swap with a one-time key. In FreeBSD you simply append .eli to the swap device name in fstab. From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 07:12:49 2008 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 5D3E51065684 for ; Wed, 27 Feb 2008 07:12:49 +0000 (UTC) (envelope-from atom@smasher.org) Received: from atom.smasher.org (atom.smasher.org [69.55.237.145]) by mx1.freebsd.org (Postfix) with SMTP id 1EADE13C45B for ; Wed, 27 Feb 2008 07:12:48 +0000 (UTC) (envelope-from atom@smasher.org) Received: (qmail 61176 invoked by uid 1000); 27 Feb 2008 02:12:21 -0000 Message-ID: <20080227021221.61175.qmail@smasher.org> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Date: Wed, 27 Feb 2008 15:12:18 +1300 (NZDT) From: Atom Smasher In-Reply-To: <9111966B-DB9C-41E3-9D30-168D668585A9@bnc.net> MIME-Version: 1.0 OpenPGP: id=0xB88D52E4D9F57808; algo=1 (RSA); size=4096; url=http://atom.smasher.org/pgp.txt References: <20080223010856.7244.qmail@smasher.org> <20080223222733.GI12067@redundancy.redundancy.org> <31648FC5-26B9-4359-ACC8-412504D3257B@bnc.net> <47C345C9.8010901@geminix.org> <9111966B-DB9C-41E3-9D30-168D668585A9@bnc.net> To: freebsd-hackers@freebsd.org X-POM: The Moon is Waning Gibbous (69% of Full) X-Hashcash: 1:20:0802270212:freebsd-hackers@freebsd.org::Rpcs9P/w9+HHodY+:000000 0000000000000000000000004ftB Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 27 Feb 2008 07:12:49 -0000 On Tue, 26 Feb 2008, Achim Patzner wrote: > You might want to take a look at eNova (http://www.enovatech.net/) who > are pointing at interesting hardware using their crypto technology. ================= the idea of closed-source hardware-based crypto disk drive may appeal to some, but i've seen too many similar things fail through stupidity, malice, etc. http://www.schneier.com/blog/archives/2004/10/the_doghouse_le.html http://www.google.com/search?q=%22crypto+ag%22+nsa one probably wouldn't have to look hard for more examples of "secure hardware" that isn't secure. there's just no way that hardware crypto can provide the peace of mind that open-source crypto does (or maybe my tin-foil hat is too tight). -- ...atom ________________________ http://atom.smasher.org/ 762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808 ------------------------------------------------- "No two men are alike, and both of them are happy for it." -- Morris Mandel From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 08:35:16 2008 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 C88AB1065699 for ; Wed, 27 Feb 2008 08:35:16 +0000 (UTC) (envelope-from sanjeevfiles@yahoo.com) Received: from web57708.mail.re3.yahoo.com (web57708.mail.re3.yahoo.com [68.142.236.71]) by mx1.freebsd.org (Postfix) with SMTP id 6FB9E13C45A for ; Wed, 27 Feb 2008 08:35:11 +0000 (UTC) (envelope-from sanjeevfiles@yahoo.com) Received: (qmail 73502 invoked by uid 60001); 27 Feb 2008 08:08:28 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=xejIS8NTpcgS8dmInRrQX+Rm1rjNXN3vNzu/iBgoJmXVn0p9UjswMPS5yeEe2yICJCIGFAQ9sJqvfbf8QnW9kDaKaSc8X5+yofCAe00P17EPIXqwkp0CqOf+U5e1z0+1PzevTc7jDBdCB/J+UnNMbQ6FIJlz5Nzi9/fxljF/NlQ=; X-YMail-OSG: 6vF.0PAVM1kBC0qZfLTuFDmei78sflIT0mFrpz_z1H81o_zux_dpmyeaS.Hg91YpKkQrdtFREAtbQE.Va0Zsc0eyNM6OwIpDLU.cHLoMKOwc3okVhyFpAD_cFThTwQ-- Received: from [124.30.112.50] by web57708.mail.re3.yahoo.com via HTTP; Wed, 27 Feb 2008 00:08:28 PST Date: Wed, 27 Feb 2008 00:08:28 -0800 (PST) From: "Sanjeev Kumar.S" To: hackers@freebsd.org In-Reply-To: <1204051337.47c45d89ea6eb@imp.free.fr> MIME-Version: 1.0 Message-ID: <284719.71279.qm@web57708.mail.re3.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: synchronous freebsd print 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, 27 Feb 2008 08:35:16 -0000 Hi, I have a quick question, and I believe this will be a common requirement. I do a print of some data and then immediately in a next statement there is a crash. But the print is not complete, before it completes there is a crash, the print is about 6-9 lines . Is there anyway to get the complete print before executing the next instruction. like putting a delay before executing the next instruction. Regards, Sanjeev. --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 08:59:41 2008 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 64C3F106567A for ; Wed, 27 Feb 2008 08:59:41 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail35.syd.optusnet.com.au (mail35.syd.optusnet.com.au [211.29.133.51]) by mx1.freebsd.org (Postfix) with ESMTP id D6F6413C45E for ; Wed, 27 Feb 2008 08:59:35 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail35.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m1R8xX1O024331 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Feb 2008 19:59:33 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.1) with ESMTP id m1R8xWIi082636; Wed, 27 Feb 2008 19:59:32 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m1R8xWZ3082635; Wed, 27 Feb 2008 19:59:32 +1100 (EST) (envelope-from peter) Date: Wed, 27 Feb 2008 19:59:32 +1100 From: Peter Jeremy To: "Sanjeev Kumar.S" Message-ID: <20080227085932.GV83599@server.vk2pj.dyndns.org> References: <1204051337.47c45d89ea6eb@imp.free.fr> <284719.71279.qm@web57708.mail.re3.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fmEUq8M7S0s+Fl0V" Content-Disposition: inline In-Reply-To: <284719.71279.qm@web57708.mail.re3.yahoo.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: hackers@freebsd.org Subject: Re: synchronous freebsd print 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, 27 Feb 2008 08:59:41 -0000 --fmEUq8M7S0s+Fl0V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 27, 2008 at 12:08:28AM -0800, Sanjeev Kumar.S wrote: > I have a quick question, and I believe this will=20 > be a common requirement. This is a standard C question. =20 > I do a print of some data and then immediately=20 > in a next statement there is a crash. =2E.. > Is there anyway to get the complete print > before executing the next instruction. Look at fflush(3) --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --fmEUq8M7S0s+Fl0V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHxSZ0/opHv/APuIcRAqpFAJ4mPDFCzNTjUvbaIsuEV1beVE53HQCgwjlc 3vDPrp9fvtc+jIXNfp/1oPs= =8kK9 -----END PGP SIGNATURE----- --fmEUq8M7S0s+Fl0V-- From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 09:29:28 2008 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 DD1D81065678 for ; Wed, 27 Feb 2008 09:29:28 +0000 (UTC) (envelope-from ap@bnc.net) Received: from bis.bonn.org (www.bis.bonn.org [217.110.117.102]) by mx1.freebsd.org (Postfix) with ESMTP id 383E613C4FF for ; Wed, 27 Feb 2008 09:29:27 +0000 (UTC) (envelope-from ap@bnc.net) X-Junk-Score: 2 [X] X-SpamCatcher-Score: 2 [X] X-Junk-Score: 0 [] X-Cloudmark-Score: 0 [] Received: from [194.39.192.125] (account bnc-mail@mailrelay.mailomat.net HELO bnc.net) by bis.bonn.org (CommuniGate Pro SMTP 5.2c4) with ESMTPSA id 9544898; Wed, 27 Feb 2008 10:31:35 +0100 X-SpamCatcher-Score: 2 [X] Received: from [194.39.194.142] (account ap HELO wasabi.wlan.bnc.net) by bnc.net (CommuniGate Pro SMTP 5.2.0) with ESMTPSA id 3079073; Wed, 27 Feb 2008 10:29:12 +0100 Message-Id: <91F98C79-91CC-45A0-9E96-B4FE7F38D727@bnc.net> From: Achim Patzner To: Atom Smasher In-Reply-To: <20080227021221.61175.qmail@smasher.org> Content-Type: multipart/signed; boundary=Apple-Mail-59-311568495; micalg=sha1; protocol="application/pkcs7-signature" Mime-Version: 1.0 (Apple Message framework v919.2) Date: Wed, 27 Feb 2008 10:29:07 +0100 References: <20080223010856.7244.qmail@smasher.org> <20080223222733.GI12067@redundancy.redundancy.org> <31648FC5-26B9-4359-ACC8-412504D3257B@bnc.net> <47C345C9.8010901@geminix.org> <9111966B-DB9C-41E3-9D30-168D668585A9@bnc.net> <20080227021221.61175.qmail@smasher.org> X-Mailer: Apple Mail (2.919.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 27 Feb 2008 09:29:29 -0000 --Apple-Mail-59-311568495 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit >> You might want to take a look at eNova (http://www.enovatech.net/) >> who are pointing at interesting hardware using their crypto >> technology. > ================= > > the idea of closed-source hardware-based crypto disk drive may > appeal to some, but i've seen too many similar things fail through > stupidity, malice, etc. Compared to in-core keys which have to stay there while the device is mounted? Yeah. Great disadvantage. > one probably wouldn't have to look hard for more examples of "secure > hardware" that isn't secure. I guess you never did a formal evaluation of you security relevant subsystems anyway. > there's just no way that hardware crypto can provide the peace of > mind that open-source crypto does Let's put it that way: There is no open source solution that doesn't spill its beans too easily - key container and crypto engine should be brought together close enough to force complete destruction of the keys should anyone try to get access to them _or_ to the data path between them. Just take a look at Apple's last failure in this regard (the iPhone) and you'll see an example of "not close enough". And no, I'm not talking about a mobile system, I'm more worried about the case of physical security not being strong enough (like in the case of governmental goons breaking down your doors or US customs and immigration staff seizing running machines ["turn your machine on and prove to us that it isn't a bomb... Thank you, now it's ours."] as they have already done); emergency shutdown of all systems should reliably render your data inaccessible. The fact that British authorities lost four mobile computers with masses of sensitive data (like a complete list of their military reserve personnel including complete financial details) on their disks since October 2007 rather makes me laugh - they don't deserve crypto solutions but a good flogging with a bundle power cords. Anyway: I don't completely trust any system where keys have to travel across an unprotected bus. I'm still sad about TPMs not having made their way at least into 99% of the server mainboards. Just take a look at ISBN://978-0-7506-7960-2 (you just shouldn't completely hand over the device to your friendly OS vendor) and ISBN://0-387-23916-2 (which will prove your point - even IBM didn't follow the "think before crypto" rule). > (or maybe my tin-foil hat is too tight). You got too close to Theo the Rat, that's all. I guess we should take this off (at least *this* list). And tell me if you want to read the books. Achim Patzner --Apple-Mail-59-311568495-- From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 09:35:25 2008 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 C0533106567D for ; Wed, 27 Feb 2008 09:35:25 +0000 (UTC) (envelope-from mark.linn@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.190]) by mx1.freebsd.org (Postfix) with ESMTP id 542BF13C4EB for ; Wed, 27 Feb 2008 09:35:25 +0000 (UTC) (envelope-from mark.linn@gmail.com) Received: by ti-out-0910.google.com with SMTP id j2so1916963tid.3 for ; Wed, 27 Feb 2008 01:35:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=MuF2GmuK2eArqw52Fsdoqbl9UaZgRA7idewbsTZoBLM=; b=tQLISvQ/8wPkuh7Dei5PG42Jd4FIU7nuB5V55bd2M/edzoVXe/tY5SZzMO4LDiDzONCidQs9QhSwqDJ2TcvXDSN2+dE4v//Wan7gBUXVJnBUu9buyuTf6u7tUxCTpl7ypD5WZwMFAytILjyxZ/XoPSBVKVwkM7REMYLzVo4INts= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=doVExqNbhag4fpB+ObA5q22OKkJMDsegM12/OJwmzRfYoec9/kxyIRCJwUGwFaDsJDXNtfv6646Cc1ey4O33LDaQAFZ8R+KNEnNe1k+2KSZxaEsjmocGQmDUIqenESagZZOxbUUJyAqoSt3CIgLSM2UNC75GvP4Y8nl8jZasiIQ= Received: by 10.150.92.11 with SMTP id p11mr2150740ybb.36.1204103247303; Wed, 27 Feb 2008 01:07:27 -0800 (PST) Received: by 10.150.226.21 with HTTP; Wed, 27 Feb 2008 01:07:27 -0800 (PST) Message-ID: <84fb42ef0802270107y4ddb8fd2scd83fe086414869f@mail.gmail.com> Date: Wed, 27 Feb 2008 01:07:27 -0800 From: "Mark Linn" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: non-blocking io, EINTR 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, 27 Feb 2008 09:35:25 -0000 Hi, I am setting the O_NONBLOCK flag on a socket file descriptor using fcntl, will a read() on the socket return EINTR when the process get a signal? Thanks Mark From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 11:00:48 2008 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 E77701065673 for ; Wed, 27 Feb 2008 11:00:47 +0000 (UTC) (envelope-from sanjeevfiles@yahoo.com) Received: from web57710.mail.re3.yahoo.com (web57710.mail.re3.yahoo.com [68.142.236.73]) by mx1.freebsd.org (Postfix) with SMTP id B041F8FC13 for ; Wed, 27 Feb 2008 11:00:47 +0000 (UTC) (envelope-from sanjeevfiles@yahoo.com) Received: (qmail 13356 invoked by uid 60001); 27 Feb 2008 11:00:46 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=d+94ytNCE41koElhLg4PJ3QNkIUYbEcPvrGKabceEMwZW07Qdpa29tS5SbvRE4XaV702N3W5PorTWpp4pkZRUHm3Fr1YAluhJZaAP3xSLFaYcqLRKKgLY3U71Ro/mNaIj+Uqeh1UiaIMwuDNSlN1OZd9W1no3lfH+7SI7FA6s/g=; X-YMail-OSG: _8641HoVM1nJaB5HnbSFDPWfo83Xai3SB4nW5VBIacek8Vw8jutAcml7v4SopP6gfPvUkosr_gt0FdRI773i9EdIJ7Wejr0hz3xeFJ.VMdsVCoka8sOe8v.l8ko01sY- Received: from [124.30.112.50] by web57710.mail.re3.yahoo.com via HTTP; Wed, 27 Feb 2008 03:00:46 PST Date: Wed, 27 Feb 2008 03:00:46 -0800 (PST) From: "Sanjeev Kumar.S" To: Peter Jeremy In-Reply-To: <20080227085932.GV83599@server.vk2pj.dyndns.org> MIME-Version: 1.0 Message-ID: <670902.8665.qm@web57710.mail.re3.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: hackers@freebsd.org Subject: Re: synchronous freebsd print 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, 27 Feb 2008 11:00:48 -0000 > This is a standard C question. Sorry, if this clarification is too simple, but I thought freeBSD kernel implemented its own print function. and the man for fflush says it is in the standard C-library. and the kernel source has no defn for fflush. I saw lots of kernel related questions asked in this list, so I posted my question here. Please correct me if I am wrong. and Yes in the kernel code I have a "\n" at the end of my print, still the print is not complete and the line next to it that causes the crash does not give the result I want. Is this a common scenario or am I doing something wrong. Sanjeev. Peter Jeremy wrote: On Wed, Feb 27, 2008 at 12:08:28AM -0800, Sanjeev Kumar.S wrote: > I have a quick question, and I believe this will > be a common requirement. This is a standard C question. > I do a print of some data and then immediately > in a next statement there is a crash. ... > Is there anyway to get the complete print > before executing the next instruction. Look at fflush(3) -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 12:51:53 2008 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 12FCD1065673 for ; Wed, 27 Feb 2008 12:51:53 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from www.pkgsrc-box.org (www.ostsee-abc.de [62.206.222.50]) by mx1.freebsd.org (Postfix) with ESMTP id DF80E8FC17 for ; Wed, 27 Feb 2008 12:51:47 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (www.pkgsrc-box.org [127.0.0.1]) by www.pkgsrc-box.org (Postfix) with ESMTP id 39F72E7A3E0 for ; Wed, 27 Feb 2008 12:51:44 +0000 (UTC) Received: by britannica.bec.de (Postfix, from userid 1000) id 1F0C8175D0; Wed, 27 Feb 2008 13:50:48 +0100 (CET) Date: Wed, 27 Feb 2008 13:50:48 +0100 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Message-ID: <20080227125048.GE352@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20080225154455.4822e72a@bhuda.mired.org> <47C33384.6040701@dial.pipex.com> <200802252243.m1PMhTeq016201@fire.js.berklix.net> <47C3A228.7090703@freebsd.org> <20080226202853.GA859@britannica.bec.de> <20080226160000.624c5d0f@bhuda.mired.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080226160000.624c5d0f@bhuda.mired.org> User-Agent: Mutt/1.5.16 (2007-06-09) Subject: Re: emulate an end-of-media 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, 27 Feb 2008 12:51:53 -0000 On Tue, Feb 26, 2008 at 04:00:00PM -0500, Mike Meyer wrote: > On Tue, 26 Feb 2008 21:28:53 +0100 Joerg Sonnenberger wrote: > > On Tue, Feb 26, 2008 at 07:44:48PM +0100, Martin Laabs wrote: > > > I also made a comparison between gzip and bzip2 regarding > > > the compression ratio on a dump of my home directory (3.2GB) > > > bzip2 took about 74min to compress, gzip only 11minutes. And > > > in terms of compression ratio bzip2 was only 3% better than > > > gzip. > > That's not a realistic test case. bzip2 normally takes trice the time > > and compresses 10% better. I can't comment on compress. > > Considering we're talking about compression methods to use on dump > output, that would seem to be the definition of a "realistic test > case". Telling us what it "normally" does without defining what input > is considered "normal" doesn't help much. Source code in my case and various other documents. The test case above certainly was not normal. Joerg From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 12:57:14 2008 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 5C93C1065670 for ; Wed, 27 Feb 2008 12:57:14 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id 27D318FC1C for ; Wed, 27 Feb 2008 12:57:14 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender:X-Spam-Status:Subject; b=HbcjWVUBQdP7/o28S6DvG+KhjRhBq3VqBUxkTIpk1DJl/tvx06yS/al8LVCaJaQ+fyRS07UEF9DWEFqLBR7nnoZLWm0zOkmCJ/om37MIoXQe/L33Ibo3YXbL2figpiC3/SnNy8cXoj+KZRjTg92eqNMuQRqWPhHFbsdPpRn7Blk=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1JULqS-000Mai-9T; Wed, 27 Feb 2008 15:57:12 +0300 Date: Wed, 27 Feb 2008 15:57:11 +0300 From: Eygene Ryabinkin To: "Sanjeev Kumar.S" Message-ID: References: <20080227085932.GV83599@server.vk2pj.dyndns.org> <670902.8665.qm@web57710.mail.re3.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <670902.8665.qm@web57710.mail.re3.yahoo.com> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-1.7 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_50 Cc: hackers@freebsd.org Subject: Re: synchronous freebsd print 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, 27 Feb 2008 12:57:14 -0000 Sanjeev, Wed, Feb 27, 2008 at 03:00:46AM -0800, Sanjeev Kumar.S wrote: > and Yes in the kernel code I have a "\n" at the end > of my print, still the print is not complete and > the line next to it that causes the crash does > not give the result I want. Is this a common > scenario or am I doing something wrong. If you're not defining PRINTF_BUFR_SIZE, then, judging by the /sys/kern/subr_prf.c, output will be unbuffered in any case. However, kernel printf is not protected by locks, so it can be interrupted by another thread, if I am correct. May be ddb(4) will become your friend? -- Eygene From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 13:16:22 2008 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 5F5121065671 for ; Wed, 27 Feb 2008 13:16:22 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from smtp.ht-systems.ru (mr0.ht-systems.ru [78.110.50.55]) by mx1.freebsd.org (Postfix) with ESMTP id 3AB298FC1C for ; Wed, 27 Feb 2008 13:16:21 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from [78.110.49.49] (helo=quasar.ht-systems.ru) by smtp.ht-systems.ru with esmtpa (Exim 4.62) (envelope-from ) id 1JUM8x-0001VE-Bv; Wed, 27 Feb 2008 16:16:19 +0300 Received: by quasar.ht-systems.ru (Postfix, from userid 1024) id 2E3007D11C8; Wed, 27 Feb 2008 16:16:18 +0300 (MSK) Date: Wed, 27 Feb 2008 16:16:18 +0300 From: Stanislav Sedov To: "M. Warner Losh" Message-ID: <20080227131617.GN51827@dracon.ht-systems.ru> References: <20080222.225937.-146245356.imp@bsdimp.com> <20080223.000308.686168314.imp@bsdimp.com> <20080224171155.GD51827@dracon.ht-systems.ru> <20080224.124339.-1302545914.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080224.124339.-1302545914.imp@bsdimp.com> Organization: The FreeBSD Project X-Voice: +7 916 849 20 23 X-XMPP: ssedov@jabber.ru X-Yahoo: stanislav_sedov X-PGP-Fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 X-University: MEPhI X-Mailer: carrier-pigeon X-Operating-System: FreeBSD quasar.ht-systems.ru 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE Cc: hackers@freebsd.org Subject: Re: find -lname and -ilname implemented 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, 27 Feb 2008 13:16:22 -0000 On Sun, Feb 24, 2008 at 12:43:39PM -0700 M. Warner Losh mentioned: > : > : Please, don't commit C++ comments, that violates style(9). Also, gnu should be > : spelled as GNU. > > Understood. Not that I'm going to change it, but understood. Why not? You took a good peace of code, and now it looks inconsistent. > > Because it makes it more compatible with existing de-facto standards. > It costs us very little to do so. > It costs extra complexity. A very important thing, though... -- Stanislav Sedov ST4096-RIPE From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 13:45:29 2008 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 5F89E1065675 for ; Wed, 27 Feb 2008 13:45:29 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [87.251.61.211]) by mx1.freebsd.org (Postfix) with ESMTP id 2A1E28FC15 for ; Wed, 27 Feb 2008 13:45:28 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 1ADAB1CC40; Wed, 27 Feb 2008 14:20:41 +0100 (CET) Date: Wed, 27 Feb 2008 14:20:41 +0100 From: Ed Schouten To: Mark Linn Message-ID: <20080227132041.GD71045@hoeg.nl> References: <84fb42ef0802270107y4ddb8fd2scd83fe086414869f@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WK3l2KTTmXPVedZ6" Content-Disposition: inline In-Reply-To: <84fb42ef0802270107y4ddb8fd2scd83fe086414869f@mail.gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: FreeBSD Hackers Subject: Re: non-blocking io, EINTR 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, 27 Feb 2008 13:45:29 -0000 --WK3l2KTTmXPVedZ6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Mark Linn wrote: > I am setting the O_NONBLOCK flag on a socket file descriptor using fcntl, >=20 > will a read() on the socket return EINTR when the process get a signal? Probably not, because that would only happen if the kernel would call the *sleep() routines, which it won't do, because the O_NONBLOCK flag disables that. --=20 Ed Schouten WWW: http://g-rave.nl/ --WK3l2KTTmXPVedZ6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAkfFY6kACgkQ52SDGA2eCwXYzgCaA9sgTxXhxgBexz3/wfwFFES/ rasAn199mwGsm5wxxLnnIjSQBd96Odc+ =5w55 -----END PGP SIGNATURE----- --WK3l2KTTmXPVedZ6-- From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 13:51:52 2008 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 60EF51065673 for ; Wed, 27 Feb 2008 13:51:52 +0000 (UTC) (envelope-from jimmy@mammothcheese.ca) Received: from smtp103.rog.mail.re2.yahoo.com (smtp103.rog.mail.re2.yahoo.com [206.190.36.81]) by mx1.freebsd.org (Postfix) with SMTP id F08E08FC1E for ; Wed, 27 Feb 2008 13:51:51 +0000 (UTC) (envelope-from jimmy@mammothcheese.ca) Received: (qmail 38494 invoked from network); 27 Feb 2008 13:25:11 -0000 Received: from unknown (HELO ?99.250.61.49?) (jazzturk@rogers.com@99.250.61.49 with plain) by smtp103.rog.mail.re2.yahoo.com with SMTP; 27 Feb 2008 13:25:11 -0000 X-YMail-OSG: BbV2udAVM1mWYlWcJ7u4re1vJoZluGi2g6YnUmaeK6Bc_BgO5r1x8CYLl4.eeo_m_g-- X-Yahoo-Newman-Property: ymail-3 Message-ID: <47C564B6.10906@mammothcheese.ca> Date: Wed, 27 Feb 2008 08:25:10 -0500 From: James Bailie User-Agent: Thunderbird 2.0.0.9 (X11/20080123) MIME-Version: 1.0 To: Mark Linn , freebsd-hackers@freebsd.org References: <84fb42ef0802270107y4ddb8fd2scd83fe086414869f@mail.gmail.com> In-Reply-To: <84fb42ef0802270107y4ddb8fd2scd83fe086414869f@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: non-blocking io, EINTR 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, 27 Feb 2008 13:51:52 -0000 Mark Linn wrote: > I am setting the O_NONBLOCK flag on a socket file descriptor using fcntl, > > will a read() on the socket return EINTR when the process get a signal? By default, read() will restart itself automatically, regardless of whether the socket is blocking or not, as long as there is data to be read in the socket receive buffer. You can change this behavior by calling sigaction(). For example, the code below will make SIGTERM interrupt system calls. They will return an error code, usually -1, with the global errno set to EINTR. If the socket is non-blocking and the socket receive buffer is empty, then read() will also return an error, but with errno set to EWOULDBLOCK. #include struct sigaction sigact; sigact.sa_handler = sigterm_handler; sigemptyset( &sigact.sa_mask ); sigact.sa_flags = 0; if ( sigaction( SIGTERM, &sigact, NULL ) < 0 ) { perror( "sigaction()" ); exit( 1 ); } -- James Bailie http://www.mammothcheese.ca From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 14:28:04 2008 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 8D2C21065672 for ; Wed, 27 Feb 2008 14:28:04 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by mx1.freebsd.org (Postfix) with ESMTP id 20D348FC1C for ; Wed, 27 Feb 2008 14:28:03 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so2115058fgg.35 for ; Wed, 27 Feb 2008 06:28:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=k0qU/7u8iFymwGS+exl9xWSc7yCWYP416M9M/ozOTIw=; b=X0/zLCNF4aCapMv2lhS5hDD5W1KRdtVtM9YgLI3Q+mk6y8tkKLelQVYgS6YZI8sO+FZ8Ykkvmj0a0l2mR7dbJirGLywwnjAzW41IeAxDqpSWYA4RR4VFP4G+6Xd9ZLYeofAQ9w3wmUkLPSR5DqppF1Znpt7Rl8OPtfkAz6eMqRo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=oAO/FdzmNOmy+FaWiP3BPiNDnqbOyarmxqjWcgEgMnt+5WeWVtCHsbcjuEvcduLaXonXNbgBRfrShg8JVX0Cs/Vzn/qoMY5864nTVi80IYVqlBdKFHZ4fK0fiHI764NXCTLmAIH3qw3nplEzUib4T9P1CmGdCQQtb4ddansX/90= Received: by 10.86.97.7 with SMTP id u7mr6119388fgb.54.1204122482697; Wed, 27 Feb 2008 06:28:02 -0800 (PST) Received: from ?192.168.12.92? ( [217.74.44.57]) by mx.google.com with ESMTPS id d6sm9205560fga.9.2008.02.27.06.28.01 (version=SSLv3 cipher=RC4-MD5); Wed, 27 Feb 2008 06:28:01 -0800 (PST) Message-ID: <47C57359.4020504@gmail.com> Date: Wed, 27 Feb 2008 17:27:37 +0300 From: sam User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <46C55191.2050205@gmail.com> <20070821145603.L50579@fledge.watson.org> <46CAF217.7040204@gmail.com> <20070821151108.Y53914@fledge.watson.org> <46CAF4E9.2030700@gmail.com> <20070821152327.R53914@fledge.watson.org> <46CBE096.90805@gmail.com> <20070828175313.B90180@fledge.watson.org> <47BD7337.2020503@gmail.com> In-Reply-To: <47BD7337.2020503@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: OpenBSM & Jails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 14:28:04 -0000 hello i am using OpenBSM on System with jails part of praudit output / action write file in jail -------------------------------------------------- header,176,10,open(2) - write,creat,trunc,0,Thu Feb 21 13:45:06 2008, + 501 msec,argument,3,0x81ed,mode,argument,2,0x601,flags,path,//site/svn/dev.lineage2.dom/pamm/hooks/post-commit,attribute,755,www,www,88,800911,3234053,subject,lynx,root,wheel,root,wheel,44680,44668,56876,10.15.1.116,return,success,4,trailer,176, -------------------------------------------------- please add jail-identification in output (cat /dev/auditpipe | praudit -lp) /Vladimir Ermakov From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 15:28:23 2008 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 64D8B1065672 for ; Wed, 27 Feb 2008 15:28:23 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [212.17.241.230]) by mx1.freebsd.org (Postfix) with ESMTP id E711A8FC23 for ; Wed, 27 Feb 2008 15:28:22 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m1REnuv4006865; Wed, 27 Feb 2008 15:49:56 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m1REnuQU006864; Wed, 27 Feb 2008 15:49:56 +0100 (CET) (envelope-from olli) Date: Wed, 27 Feb 2008 15:49:56 +0100 (CET) Message-Id: <200802271449.m1REnuQU006864@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG In-Reply-To: X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 27 Feb 2008 15:49:58 +0100 (CET) Cc: Subject: Re: Security Flaw in Popular Disk Encryption Technologies 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, 27 Feb 2008 15:28:23 -0000 Martin Laabs wrote: > Preventing the physical access to the memory modules > could be done with a light sensor or a simple switch > at the computer case. Easily to circumvent, too. > If you implement also a temperature- > sensor near the memory-modules you could prevent cooling > them down before removal. (You'd just overwrite the keys > if the temperature falls i.e. below 10°C) Cool ... Then I won't be able to boot my laptop when I have to wait at the train station in winter ... Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd > Can the denizens of this group enlighten me about what the > advantages of Python are, versus Perl ? "python" is more likely to pass unharmed through your spelling checker than "perl". -- An unknown poster and Fredrik Lundh From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 15:48:46 2008 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 3814B1065671 for ; Wed, 27 Feb 2008 15:48:46 +0000 (UTC) (envelope-from jhein@timing.com) Received: from Daffy.timing.com (smtp.timing.com [206.168.13.218]) by mx1.freebsd.org (Postfix) with ESMTP id F20A18FC15 for ; Wed, 27 Feb 2008 15:48:45 +0000 (UTC) (envelope-from jhein@timing.com) Received: from gromit.timing.com (gromit.timing.com [206.168.13.209]) by Daffy.timing.com (8.13.1/8.13.1) with ESMTP id m1RFaV3B070053 for ; Wed, 27 Feb 2008 08:36:31 -0700 (MST) (envelope-from jhein@timing.com) Received: from gromit.timing.com (localhost [127.0.0.1]) by gromit.timing.com (8.14.2/8.14.2) with ESMTP id m1RFaUc9030355; Wed, 27 Feb 2008 08:36:30 -0700 (MST) (envelope-from jhein@gromit.timing.com) Received: (from jhein@localhost) by gromit.timing.com (8.14.2/8.14.2/Submit) id m1RFaUSF030352; Wed, 27 Feb 2008 08:36:30 -0700 (MST) (envelope-from jhein) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18373.33662.614583.231211@gromit.timing.com> Date: Wed, 27 Feb 2008 08:36:30 -0700 From: John Hein To: hackers@freebsd.org X-Mailer: VM 7.19 under Emacs 22.1.1 X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on Daffy.timing.com X-Virus-Status: Clean Cc: Subject: cvs tag renaming after repo copy 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, 27 Feb 2008 15:48:46 -0000 Can someone point me at a script that does tag renaming after a repo copy? From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 16:15:40 2008 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 E24851065674 for ; Wed, 27 Feb 2008 16:15:40 +0000 (UTC) (envelope-from jtoothman@about.com) Received: from mail.about.com (mta.about.com [207.241.148.60]) by mx1.freebsd.org (Postfix) with ESMTP id A1ED58FC13 for ; Wed, 27 Feb 2008 16:15:40 +0000 (UTC) (envelope-from jtoothman@about.com) Received: (qmail 36074 invoked from network); 27 Feb 2008 15:48:57 -0000 Received: from unknown (HELO JKT.local) ([216.223.13.111]) (envelope-sender ) by mail4.ops.about-inc.com (qmail-ldap-1.03) with SMTP for ; 27 Feb 2008 15:48:57 -0000 Message-ID: <47C586C4.9010703@about.com> Date: Wed, 27 Feb 2008 10:50:28 -0500 From: "James K. Toothman" Organization: About, Inc. User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 References: <1204051337.47c45d89ea6eb@imp.free.fr> <284719.71279.qm@web57708.mail.re3.yahoo.com> <20080227085932.GV83599@server.vk2pj.dyndns.org> In-Reply-To: <20080227085932.GV83599@server.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: synchronous freebsd print X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jtoothman@about.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 16:15:41 -0000 Use fprintf(stderr, ...) instead, as stderr is unbuffered by default. James Toothman About.com Peter Jeremy wrote: > On Wed, Feb 27, 2008 at 12:08:28AM -0800, Sanjeev Kumar.S wrote: > >> I have a quick question, and I believe this will >> be a common requirement. >> > > This is a standard C question. > > >> I do a print of some data and then immediately >> in a next statement there is a crash. >> > ... > >> Is there anyway to get the complete print >> before executing the next instruction. >> > > Look at fflush(3) > > From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 17:09:52 2008 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 03F771065673; Wed, 27 Feb 2008 17:09:52 +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 D77868FC1F; Wed, 27 Feb 2008 17:09:51 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m1RH7f21038322; Wed, 27 Feb 2008 10:07:41 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 27 Feb 2008 10:08:12 -0700 (MST) Message-Id: <20080227.100812.-963151432.imp@bsdimp.com> To: freebsd-hackers@freebsd.org, obrien@freebsd.org From: "M. Warner Losh" In-Reply-To: <20080225175841.GC81874@dragon.NUXI.org> References: <20080225005429.38f0c91a@bhuda.mired.org> <20080225.000744.-345418608.imp@bsdimp.com> <20080225175841.GC81874@dragon.NUXI.org> 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: Subject: Re: find -lname and -ilname implemented 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, 27 Feb 2008 17:09:52 -0000 In message: <20080225175841.GC81874@dragon.NUXI.org> "David O'Brien" writes: : On Mon, Feb 25, 2008 at 12:07:44AM -0700, M. Warner Losh wrote: : > In message: <20080225005429.38f0c91a@bhuda.mired.org> : > Mike Meyer writes: : > You fail to understand the complex interplay of politics here. These : > people do not want to see beyond it. They want to shut you down : > because you aren't using their beloved Linux. They use stupid excuses : > to not do things. This is about removing barriers to entry. This : > isn't about being popular. : .. : > : Um, if FreeBSD has to become GNU in order to win GNU users, what's the : > : point? Skip the pain, switch to GNU, and get the popularity you want : > : and the platform you deserve with no delay. : > : > Hello? BSDL calling. You left your GPL here and we don't want it. : : For some of these uses of FreeBSD - I really have to wonder if : GNU/kFreeBSD (Debian GNU/kFreeBSD is a port that consists of GNU userland : using the GNU C library on top of FreeBSD's kernel) isn't a better : choice. http://www.debian.org/ports/kfreebsd-gnu/ : : One can keep their kernel changes private IP without worry. I doubt most : companies would claim they have IP that needs protecting in their GNU : userland changes. True, but using the GPL goes beyond just giving out your changes. If you mess up in shipping your product, even once, even by accident, the GPL has a provision that terminates your license, so you are unable to ship that "work" any more until you go back to the license hold and get it restored. This aspect of the GPL is used by GPL-trolls to extract payments from companies. It is also little enforced by other IP holders if you make it right. Warner From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 16:50:38 2008 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 34802106566B for ; Wed, 27 Feb 2008 16:50:38 +0000 (UTC) (envelope-from mwm@mired.org) Received: from mired.org (student.mired.org [66.92.153.77]) by mx1.freebsd.org (Postfix) with SMTP id EDCF68FC19 for ; Wed, 27 Feb 2008 16:50:27 +0000 (UTC) (envelope-from mwm@mired.org) Received: (qmail 76780 invoked from network); 27 Feb 2008 16:49:17 -0000 Received: from unknown (HELO mbook-fbsd) (192.168.195.250) by 0 with SMTP; 27 Feb 2008 16:49:17 -0000 Date: Wed, 27 Feb 2008 11:50:46 -0500 From: Mike Meyer To: Joerg Sonnenberger Message-ID: <20080227115046.2e029ff0@mbook-fbsd> In-Reply-To: <20080227125048.GE352@britannica.bec.de> References: <20080225154455.4822e72a@bhuda.mired.org> <47C33384.6040701@dial.pipex.com> <200802252243.m1PMhTeq016201@fire.js.berklix.net> <47C3A228.7090703@freebsd.org> <20080226202853.GA859@britannica.bec.de> <20080226160000.624c5d0f@bhuda.mired.org> <20080227125048.GE352@britannica.bec.de> Organization: Meyer Consulting X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.5; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 27 Feb 2008 17:16:44 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: emulate an end-of-media 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, 27 Feb 2008 16:50:38 -0000 On Wed, 27 Feb 2008 13:50:48 +0100 Joerg Sonnenberger wrote: > On Tue, Feb 26, 2008 at 04:00:00PM -0500, Mike Meyer wrote: > > On Tue, 26 Feb 2008 21:28:53 +0100 Joerg Sonnenberger wrote: > > > On Tue, Feb 26, 2008 at 07:44:48PM +0100, Martin Laabs wrote: > > > > I also made a comparison between gzip and bzip2 regarding > > > > the compression ratio on a dump of my home directory (3.2GB) > > > > bzip2 took about 74min to compress, gzip only 11minutes. And > > > > in terms of compression ratio bzip2 was only 3% better than > > > > gzip. > > > That's not a realistic test case. bzip2 normally takes trice the time > > > and compresses 10% better. I can't comment on compress. > > > > Considering we're talking about compression methods to use on dump > > output, that would seem to be the definition of a "realistic test > > case". Telling us what it "normally" does without defining what input > > is considered "normal" doesn't help much. > > Source code in my case and various other documents. The test case above > certainly was not normal. So it sounds like your "normal" is mostly text documents of various kinds. I would expect such data to be a relatively small part of any dump data set, which, as you say, means that such data isn't normal. Given that the use case under discussion is abnormal, any tests using normal data are pretty much irrelevant. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 18:31:42 2008 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 5DC0D10656D0 for ; Wed, 27 Feb 2008 18:31:42 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 434118FC17 for ; Wed, 27 Feb 2008 18:31:37 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id m1RIVJPb054661; Wed, 27 Feb 2008 10:31:28 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.2/8.14.1/Submit) id m1RIVDj4054658; Wed, 27 Feb 2008 10:31:13 -0800 (PST) (envelope-from obrien) Date: Wed, 27 Feb 2008 10:31:13 -0800 From: "David O'Brien" To: Giorgos Keramidas Message-ID: <20080227183113.GA54600@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Giorgos Keramidas , "M. Warner Losh" , freebsd-hackers@freebsd.org, jonathan+freebsd-hackers@hst.org.za References: <200802232322.45288.jonathan+freebsd-hackers@hst.org.za> <20080223.164806.-674897155.imp@bsdimp.com> <20080225203341.GA4150@kobe.laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080225203341.GA4150@kobe.laptop> X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-hackers@freebsd.org, jonathan+freebsd-hackers@hst.org.za Subject: Re: find -lname and -ilname implemented X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 18:31:42 -0000 On Mon, Feb 25, 2008 at 10:33:41PM +0200, Giorgos Keramidas wrote: > On 2008-02-23 16:48, "M. Warner Losh" wrote: > > This knee-jerk reaction against gnu find functionality baffles me. > > The changes are trivial and make FreeBSD more compatible. It is such > > an obvious no-brainer that I frankly didn't expect anybody to bat an > > eye. > > So should I expect similar knee-jerk reactions to the just committed > `finger compatibility' option to implement du -l for hardlinks? You added a new useful feature - and you based the option letter on prior-art (and resumable doen't conflict with POSIX). -- -- David (obrien@FreeBSD.org) From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 18:43:17 2008 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 6C2351065673 for ; Wed, 27 Feb 2008 18:43:17 +0000 (UTC) (envelope-from mark.linn@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.190]) by mx1.freebsd.org (Postfix) with ESMTP id F3F218FC25 for ; Wed, 27 Feb 2008 18:43:16 +0000 (UTC) (envelope-from mark.linn@gmail.com) Received: by ti-out-0910.google.com with SMTP id j2so2255565tid.3 for ; Wed, 27 Feb 2008 10:43:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=68a3Wd+OSYAE1gtU65L+xyRAs/YPi9V+SbjJmX50b9I=; b=BXJEZFf5n60Ww3YkWEDReElnKtlEO4tjYbHYc7rM7pjfHuucTa97qIut2A0e0aq7OVneSGgU43tIe9V03sw4RlIAUK8Oji9+Rx25O4CZxHs87Ta8hbBN7oQ7Fz6gQskGfxXUYnvpyxvrO3LwHZL9lAuDy+3qAHJGo1hM1dhtzfs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=yFXBNhXpmSKZOlVzpNXCyPtc6QMCTfSy0yGy4GdXBQGqTTcv6vyJDiU0uwXR7EZE34Y2v/8Wu6ke5mhTHEduJTjld1rMX1hQQeORz9DQBZZHkeNqifNZWLAfIHCvQKGCklmo8HEATXxzB5/4YO1X0B7vRt4rUHdy65tHP2JFTjI= Received: by 10.150.191.10 with SMTP id o10mr2433154ybf.84.1204137793535; Wed, 27 Feb 2008 10:43:13 -0800 (PST) Received: by 10.150.226.21 with HTTP; Wed, 27 Feb 2008 10:43:13 -0800 (PST) Message-ID: <84fb42ef0802271043n1f5d8318ie259b7b4e9622c1d@mail.gmail.com> Date: Wed, 27 Feb 2008 10:43:13 -0800 From: "Mark Linn" To: "James Bailie" In-Reply-To: <47C564B6.10906@mammothcheese.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <84fb42ef0802270107y4ddb8fd2scd83fe086414869f@mail.gmail.com> <47C564B6.10906@mammothcheese.ca> Cc: freebsd-hackers@freebsd.org Subject: Re: non-blocking io, EINTR 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, 27 Feb 2008 18:43:17 -0000 On Wed, Feb 27, 2008 at 5:25 AM, James Bailie wrote: > Mark Linn wrote: > > > I am setting the O_NONBLOCK flag on a socket file descriptor using fcntl, > > > > will a read() on the socket return EINTR when the process get a signal? > > By default, read() will restart itself automatically, regardless > of whether the socket is blocking or not, as long as there is > data to be read in the socket receive buffer. You can change > this behavior by calling sigaction(). For example, the code > below will make SIGTERM interrupt system calls. They will return > an error code, usually -1, with the global errno set to EINTR. > If the socket is non-blocking and the socket receive buffer is > empty, then read() will also return an error, but with errno set > to EWOULDBLOCK. > > #include > > struct sigaction sigact; > > sigact.sa_handler = sigterm_handler; > sigemptyset( &sigact.sa_mask ); > sigact.sa_flags = 0; > > if ( sigaction( SIGTERM, &sigact, NULL ) < 0 ) > { > perror( "sigaction()" ); > exit( 1 ); > } > > -- > James Bailie > http://www.mammothcheese.ca > Thanks, Ed and James, Then why in the world the sample code in this acm paper would test EINTR in read and write? link is here. http://delivery.acm.org/10.1145/1350000/1344155/9815.html?key1=1344155&key2=2950393021&coll=GUIDE&dl=&CFID=15151515&CFTOKEN=6184618 From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 18:47:23 2008 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 4AE981065672 for ; Wed, 27 Feb 2008 18:47:23 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outQ.internet-mail-service.net (outQ.internet-mail-service.net [216.240.47.240]) by mx1.freebsd.org (Postfix) with ESMTP id 37E628FC25 for ; Wed, 27 Feb 2008 18:47:23 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Wed, 27 Feb 2008 10:47:22 -0800 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id CFCB312738C; Wed, 27 Feb 2008 10:47:21 -0800 (PST) Message-ID: <47C5B04A.40400@elischer.org> Date: Wed, 27 Feb 2008 10:47:38 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: obrien@freebsd.org, Giorgos Keramidas , "M. Warner Losh" , freebsd-hackers@freebsd.org, jonathan+freebsd-hackers@hst.org.za References: <200802232322.45288.jonathan+freebsd-hackers@hst.org.za> <20080223.164806.-674897155.imp@bsdimp.com> <20080225203341.GA4150@kobe.laptop> <20080227183113.GA54600@dragon.NUXI.org> In-Reply-To: <20080227183113.GA54600@dragon.NUXI.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: find -lname and -ilname implemented 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, 27 Feb 2008 18:47:23 -0000 David O'Brien wrote: > On Mon, Feb 25, 2008 at 10:33:41PM +0200, Giorgos Keramidas wrote: >> On 2008-02-23 16:48, "M. Warner Losh" wrote: >>> This knee-jerk reaction against gnu find functionality baffles me. >>> The changes are trivial and make FreeBSD more compatible. It is such >>> an obvious no-brainer that I frankly didn't expect anybody to bat an >>> eye. >> So should I expect similar knee-jerk reactions to the just committed >> `finger compatibility' option to implement du -l for hardlinks? > > You added a new useful feature - and you based the option letter on > prior-art (and resumable doen't conflict with POSIX). can we form an anti-knee-jerk cabal that can get a quorum when needed? From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 18:52:02 2008 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 52E031065670 for ; Wed, 27 Feb 2008 18:52:02 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outM.internet-mail-service.net (outM.internet-mail-service.net [216.240.47.236]) by mx1.freebsd.org (Postfix) with ESMTP id 442D18FC14 for ; Wed, 27 Feb 2008 18:52:02 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Wed, 27 Feb 2008 10:52:01 -0800 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 22936125E89; Wed, 27 Feb 2008 10:52:01 -0800 (PST) Message-ID: <47C5B161.3040707@elischer.org> Date: Wed, 27 Feb 2008 10:52:17 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: "Sanjeev Kumar.S" References: <284719.71279.qm@web57708.mail.re3.yahoo.com> In-Reply-To: <284719.71279.qm@web57708.mail.re3.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: synchronous freebsd print 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, 27 Feb 2008 18:52:02 -0000 Sanjeev Kumar.S wrote: > Hi, > I have a quick question, and I believe this will > be a common requirement. > > I do a print of some data and then immediately > in a next statement there is a crash. But the > print is not complete, before it completes there > is a crash, the print is about 6-9 lines . > Is there anyway to get the complete print > before executing the next instruction. like > putting a delay before executing the next > instruction. > in the kernel or in a program? > Regards, > Sanjeev. > > > > > --------------------------------- > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. > _______________________________________________ > 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 Wed Feb 27 19:17:49 2008 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 B0C971065679; Wed, 27 Feb 2008 19:17:49 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4BC4F8FC24; Wed, 27 Feb 2008 19:17:44 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 4F4D446B24; Wed, 27 Feb 2008 14:17:43 -0500 (EST) Date: Wed, 27 Feb 2008 19:17:43 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: sam In-Reply-To: <47BD7337.2020503@gmail.com> Message-ID: <20080227191603.X17238@fledge.watson.org> References: <46C55191.2050205@gmail.com> <20070821145603.L50579@fledge.watson.org> <46CAF217.7040204@gmail.com> <20070821151108.Y53914@fledge.watson.org> <46CAF4E9.2030700@gmail.com> <20070821152327.R53914@fledge.watson.org> <46CBE096.90805@gmail.com> <20070828175313.B90180@fledge.watson.org> <47BD7337.2020503@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, trustedbsd-audit@FreeBSD.org, csjp@FreeBSD.org, freebsd-audit@freebsd.org Subject: Re: OpenBSM & Jails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 19:17:49 -0000 On Thu, 21 Feb 2008, sam wrote: > i am using OpenBSM on System with jails > > part of praudit output / action write file in jail > > -------------------------------------------------- > header,176,10,open(2) - write,creat,trunc,0,Thu Feb 21 13:45:06 2008, + 501 > msec,argument,3,0x81ed,mode,argument,2,0x601,flags,path,//site/svn/dev.lineage2.dom/pamm/hooks/post-commit,attribute,755,www,www,88,800911,3234053,subject,lynx,root,wheel,root,wheel,44680,44668,56876,10.15.1.116,return,success,4,trailer,176, > -------------------------------------------------- > > please add jail-identification in output (cat /dev/auditpipe | praudit -lp) Vladimir, I believe Christian has plans to use the Solaris "zone" BSM token to this end, as well as plans to enhance our support for hostid header fields so that when audit trails are aggregated from many sources, they can be processed with awareness of which source they came from. I've added him to the CC line, and he may be able to expand on this. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 19:18:21 2008 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 3AFBB106566C for ; Wed, 27 Feb 2008 19:18:21 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 825E38FC16 for ; Wed, 27 Feb 2008 19:18:20 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (vader.bytemobile-rio.ondsl.gr [83.235.57.37]) (authenticated bits=0) by igloo.linux.gr (8.14.1/8.14.1/Debian-9) with ESMTP id m1RJ4vuK006740; Wed, 27 Feb 2008 21:05:04 +0200 Received: by kobe.laptop (Postfix, from userid 1000) id B3C4A22802; Wed, 27 Feb 2008 21:04:48 +0200 (EET) Date: Wed, 27 Feb 2008 21:04:48 +0200 From: Giorgos Keramidas To: John Hein Message-ID: <20080227190448.GA50031@kobe.laptop> References: <18373.33662.614583.231211@gromit.timing.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18373.33662.614583.231211@gromit.timing.com> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.971, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.43, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: hackers@freebsd.org Subject: Re: cvs tag renaming after repo copy 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, 27 Feb 2008 19:18:21 -0000 On 2008-02-27 08:36, John Hein wrote: > Can someone point me at a script that does tag renaming > after a repo copy? You don't really need a `script' to do this. Tags in CVS are not versioned, so you can force-tag the repo-copied files and move the tag to its new place. For example if you have two files: foo.c,v bar.c,v and bar.c,v is a repo-copy of foo.c,v then you move the tag only for the bar.c file by checking it out, and running: cvs tag -f -r 1.2 bar.c This should force/move the tag to point revision 1.2. From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 19:21:33 2008 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 C7F0A106566B for ; Wed, 27 Feb 2008 19:21:33 +0000 (UTC) (envelope-from jhein@timing.com) Received: from Daffy.timing.com (w.timing.com [206.168.13.218]) by mx1.freebsd.org (Postfix) with ESMTP id 767D48FC24 for ; Wed, 27 Feb 2008 19:21:28 +0000 (UTC) (envelope-from jhein@timing.com) Received: from gromit.timing.com (gromit.timing.com [206.168.13.209]) by Daffy.timing.com (8.13.1/8.13.1) with ESMTP id m1RJLPgo006059; Wed, 27 Feb 2008 12:21:25 -0700 (MST) (envelope-from jhein@timing.com) Received: from gromit.timing.com (localhost [127.0.0.1]) by gromit.timing.com (8.14.2/8.14.2) with ESMTP id m1RJLPd0036199; Wed, 27 Feb 2008 12:21:25 -0700 (MST) (envelope-from jhein@gromit.timing.com) Received: (from jhein@localhost) by gromit.timing.com (8.14.2/8.14.2/Submit) id m1RJLPCH036196; Wed, 27 Feb 2008 12:21:25 -0700 (MST) (envelope-from jhein) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18373.47157.425456.583623@gromit.timing.com> Date: Wed, 27 Feb 2008 12:21:25 -0700 From: John Hein To: Giorgos Keramidas In-Reply-To: <20080227190448.GA50031@kobe.laptop> References: <18373.33662.614583.231211@gromit.timing.com> <20080227190448.GA50031@kobe.laptop> X-Mailer: VM 7.19 under Emacs 22.1.1 X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on Daffy.timing.com X-Virus-Status: Clean Cc: hackers@freebsd.org Subject: Re: cvs tag renaming after repo copy 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, 27 Feb 2008 19:21:33 -0000 Giorgos Keramidas wrote at 21:04 +0200 on Feb 27, 2008: > On 2008-02-27 08:36, John Hein wrote: > > Can someone point me at a script that does tag renaming > > after a repo copy? > > You don't really need a `script' to do this. > > Tags in CVS are not versioned, so you can force-tag the repo-copied > files and move the tag to its new place. > > For example if you have two files: > > foo.c,v > bar.c,v > > and bar.c,v is a repo-copy of foo.c,v then you move the tag only for the > bar.c file by checking it out, and running: > > cvs tag -f -r 1.2 bar.c ------------------------^^^ you're missing the tag name in this example, but... > This should force/move the tag to point revision 1.2. I don't want to move the tag... I want to invalidate old tags by renaming them to something else (like foo-1-2-3 -> old_foo-1-2-3). Note that just using cvs to rename a tag (by tagging with the new name and then removing the former name) has issues when you try to do that with branch tags. Anyway, I'm pretty sure the FreeBSD cvs-meisters run something to invalidate tags after doing a repo copy. That's the information I was looking for. From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 19:32:35 2008 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 60FA11065674; Wed, 27 Feb 2008 19:32:35 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 4BBDD8FC22; Wed, 27 Feb 2008 19:32:35 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id m1RJWYve056428; Wed, 27 Feb 2008 11:32:34 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.2/8.14.1/Submit) id m1RJWY37056427; Wed, 27 Feb 2008 11:32:34 -0800 (PST) (envelope-from obrien) Date: Wed, 27 Feb 2008 11:32:34 -0800 From: "David O'Brien" To: Adrian Chadd Message-ID: <20080227193234.GB54600@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Adrian Chadd , freebsd-hackers@freebsd.org, hackers@freebsd.org References: <20080225174410.GA81874@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-hackers@freebsd.org, hackers@freebsd.org Subject: Re: Modular type GENERIC? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 19:32:35 -0000 On Tue, Feb 26, 2008 at 01:56:28PM +0900, Adrian Chadd wrote: > On 26/02/2008, David O'Brien wrote: > > > As you've shown the magic is in the loader.conf. I don't know a good way > > to handle this other than attempt to load every module (like Microsoft NT > > installer does) - and hope the probe of a driver that doesn't claim a > > device doesn't leave that device in a bad state. > > > > Have you tried putting every module in /boot/kernel into loader.conf in a > > "load" statement? > > I'm going to try doing that tonight. Cool. Please let us(me) know how it goes. -- -- David (obrien@FreeBSD.org) From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 19:32:35 2008 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 60FA11065674; Wed, 27 Feb 2008 19:32:35 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 4BBDD8FC22; Wed, 27 Feb 2008 19:32:35 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id m1RJWYve056428; Wed, 27 Feb 2008 11:32:34 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.2/8.14.1/Submit) id m1RJWY37056427; Wed, 27 Feb 2008 11:32:34 -0800 (PST) (envelope-from obrien) Date: Wed, 27 Feb 2008 11:32:34 -0800 From: "David O'Brien" To: Adrian Chadd Message-ID: <20080227193234.GB54600@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Adrian Chadd , freebsd-hackers@freebsd.org, hackers@freebsd.org References: <20080225174410.GA81874@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-hackers@freebsd.org, hackers@freebsd.org Subject: Re: Modular type GENERIC? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 19:32:35 -0000 On Tue, Feb 26, 2008 at 01:56:28PM +0900, Adrian Chadd wrote: > On 26/02/2008, David O'Brien wrote: > > > As you've shown the magic is in the loader.conf. I don't know a good way > > to handle this other than attempt to load every module (like Microsoft NT > > installer does) - and hope the probe of a driver that doesn't claim a > > device doesn't leave that device in a bad state. > > > > Have you tried putting every module in /boot/kernel into loader.conf in a > > "load" statement? > > I'm going to try doing that tonight. Cool. Please let us(me) know how it goes. -- -- David (obrien@FreeBSD.org) From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 19:36:57 2008 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 0D426106566B for ; Wed, 27 Feb 2008 19:36:57 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 56EF18FC1A for ; Wed, 27 Feb 2008 19:36:56 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (vader.bytemobile-rio.ondsl.gr [83.235.57.37]) (authenticated bits=0) by igloo.linux.gr (8.14.1/8.14.1/Debian-9) with ESMTP id m1RJaKrb008409; Wed, 27 Feb 2008 21:36:26 +0200 Received: by kobe.laptop (Postfix, from userid 1000) id B6F7E22802; Wed, 27 Feb 2008 21:36:14 +0200 (EET) Date: Wed, 27 Feb 2008 21:36:14 +0200 From: Giorgos Keramidas To: obrien@freebsd.org, "M. Warner Losh" , freebsd-hackers@freebsd.org, jonathan+freebsd-hackers@hst.org.za Message-ID: <20080227193614.GA50391@kobe.laptop> References: <200802232322.45288.jonathan+freebsd-hackers@hst.org.za> <20080223.164806.-674897155.imp@bsdimp.com> <20080225203341.GA4150@kobe.laptop> <20080227183113.GA54600@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080227183113.GA54600@dragon.NUXI.org> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.971, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.43, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: Subject: Re: find -lname and -ilname implemented 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, 27 Feb 2008 19:36:57 -0000 On 2008-02-27 10:31, David O'Brien wrote: >On Mon, Feb 25, 2008 at 10:33:41PM +0200, Giorgos Keramidas wrote: >>On 2008-02-23 16:48, "M. Warner Losh" wrote: >>> This knee-jerk reaction against gnu find functionality baffles me. >>> The changes are trivial and make FreeBSD more compatible. It is such >>> an obvious no-brainer that I frankly didn't expect anybody to bat an >>> eye. >> >> So should I expect similar knee-jerk reactions to the just committed >> `finger compatibility' option to implement du -l for hardlinks? > > You added a new useful feature - and you based the option letter on > prior-art (and resumable doen't conflict with POSIX). Fortunately, no, there is no conflict :-) The du(1) manpage at the online version of SUSv3 mentions only the -L option, for dereferencing symlinks. I should have probably mentioned this in the commit log, now that I think about it. From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 19:47:15 2008 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 4168F106566B for ; Wed, 27 Feb 2008 19:47:15 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id B0DA08FC19 for ; Wed, 27 Feb 2008 19:47:14 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (vader.bytemobile-rio.ondsl.gr [83.235.57.37]) (authenticated bits=0) by igloo.linux.gr (8.14.1/8.14.1/Debian-9) with ESMTP id m1RJkj1P008799; Wed, 27 Feb 2008 21:46:51 +0200 Received: by kobe.laptop (Postfix, from userid 1000) id 3F02722802; Wed, 27 Feb 2008 21:46:40 +0200 (EET) Date: Wed, 27 Feb 2008 21:46:40 +0200 From: Giorgos Keramidas To: John Hein Message-ID: <20080227194639.GA50523@kobe.laptop> References: <18373.33662.614583.231211@gromit.timing.com> <20080227190448.GA50031@kobe.laptop> <18373.47157.425456.583623@gromit.timing.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18373.47157.425456.583623@gromit.timing.com> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.971, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.43, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: hackers@freebsd.org Subject: Re: cvs tag renaming after repo copy 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, 27 Feb 2008 19:47:15 -0000 On 2008-02-27 12:21, John Hein wrote: >Giorgos Keramidas wrote at 21:04 +0200 on Feb 27, 2008: >> On 2008-02-27 08:36, John Hein wrote: >> > Can someone point me at a script that does tag renaming >> > after a repo copy? >> >> You don't really need a `script' to do this. >> >> Tags in CVS are not versioned, so you can force-tag the repo-copied >> files and move the tag to its new place. >> >> For example if you have two files: >> >> foo.c,v >> bar.c,v >> >> and bar.c,v is a repo-copy of foo.c,v then you move the tag only for the >> bar.c file by checking it out, and running: >> >> cvs tag -f -r 1.2 bar.c > > ------------------------^^^ you're missing the tag name in this > example, but... > >> This should force/move the tag to point revision 1.2. > > I don't want to move the tag... I want to invalidate old tags by > renaming them to something else (like foo-1-2-3 -> old_foo-1-2-3). Ah, now I see. Sorry for the confusion :/ > Note that just using cvs to rename a tag (by tagging with the new name > and then removing the former name) has issues when you try to do that > with branch tags. > > Anyway, I'm pretty sure the FreeBSD cvs-meisters run something to > invalidate tags after doing a repo copy. That's the information I was > looking for. Scripting is probably risky for this sort of thing, but I'll let the CVS meisters reply :) From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 19:58:57 2008 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 75D0B1065676 for ; Wed, 27 Feb 2008 19:58:57 +0000 (UTC) (envelope-from jhein@timing.com) Received: from Daffy.timing.com (smtp.timing.com [206.168.13.218]) by mx1.freebsd.org (Postfix) with ESMTP id 4A7388FC1B for ; Wed, 27 Feb 2008 19:58:57 +0000 (UTC) (envelope-from jhein@timing.com) Received: from gromit.timing.com (gromit.timing.com [206.168.13.209]) by Daffy.timing.com (8.13.1/8.13.1) with ESMTP id m1RJwrHX011693; Wed, 27 Feb 2008 12:58:53 -0700 (MST) (envelope-from jhein@timing.com) Received: from gromit.timing.com (localhost [127.0.0.1]) by gromit.timing.com (8.14.2/8.14.2) with ESMTP id m1RJwmQj037485; Wed, 27 Feb 2008 12:58:48 -0700 (MST) (envelope-from jhein@gromit.timing.com) Received: (from jhein@localhost) by gromit.timing.com (8.14.2/8.14.2/Submit) id m1RJwmqc037481; Wed, 27 Feb 2008 12:58:48 -0700 (MST) (envelope-from jhein) MIME-Version: 1.0 Content-Type: text/plain; charset=unknown Content-Transfer-Encoding: 7bit Message-ID: <18373.49400.143413.571279@gromit.timing.com> Date: Wed, 27 Feb 2008 12:58:48 -0700 From: John Hein To: "=?UTF-8?Q?Amol_Dharmadhikar?= =?UTF-8?Q?i_=E0=A4=85=E0=A4=AE=E0=A5=8B=E0=A4=B2_=E0=A4=A7=E0=A4=B0?= =?UTF-8?Q?=E0=A5=8D=E0=A4=AE=E0=A4=BE=E0=A4=A7?= =?UTF-8?Q?=E0=A5=80=E0=A4=95=E0=A4=BE=E0=A4=B0=E0=A5=80?=" In-Reply-To: <61ed81c80802271147t3346f52lcb85233fbd3b6884@mail.gmail.com> References: <18373.33662.614583.231211@gromit.timing.com> <20080227190448.GA50031@kobe.laptop> <18373.47157.425456.583623@gromit.timing.com> <61ed81c80802271147t3346f52lcb85233fbd3b6884@mail.gmail.com> X-Mailer: VM 7.19 under Emacs 22.1.1 X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on Daffy.timing.com X-Virus-Status: Clean Cc: hackers@freebsd.org Subject: Re: cvs tag renaming after repo copy 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, 27 Feb 2008 19:58:57 -0000 Amol Dharmadhikar i ???? ?? ???? ????? wrote at 11:47 -0800 on Feb 27, 2008: > On Wed, Feb 27, 2008 at 11:21 AM, John Hein wrote: > > I don't want to move the tag... I want to invalidate old tags by > > renaming them to something else (like foo-1-2-3 -> old_foo-1-2-3). > > > > Note that just using cvs to rename a tag (by tagging with the new name > > and then removing the former name) has issues when you try to do that > > with branch tags. [*] > > > > Anyway, I'm pretty sure the FreeBSD cvs-meisters run something to > > invalidate tags after doing a repo copy. That's the information I was > > looking for. > > > > I dont think you can rename tags using a single command. What you can > do instead is create a new tag at the same point as the old tag, and > then delete the old tag. > > eg - > cvs rtag -r old-foo-1-2-3 new-foo-1-2-3 > cvs rtag -d old-foo-1-2-3 Yes, I mentioned that above [*]. You can't do that with branch tags. You can use cvs admin -n or -N with branch tags. Anyway, I'm wondering if anyone has a script which iterates over existing tags and renames them to old_*. Maybe that will make it more clear what I'm looking for? From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 20:12:25 2008 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 DA2801065678 for ; Wed, 27 Feb 2008 20:12:25 +0000 (UTC) (envelope-from amol@dharmadhikari.org) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.182]) by mx1.freebsd.org (Postfix) with ESMTP id 96AED8FC27 for ; Wed, 27 Feb 2008 20:12:20 +0000 (UTC) (envelope-from amol@dharmadhikari.org) Received: by el-out-1112.google.com with SMTP id r27so2689188ele.3 for ; Wed, 27 Feb 2008 12:12:19 -0800 (PST) Received: by 10.142.188.4 with SMTP id l4mr5698457wff.151.1204141659190; Wed, 27 Feb 2008 11:47:39 -0800 (PST) Received: by 10.142.11.15 with HTTP; Wed, 27 Feb 2008 11:47:39 -0800 (PST) Message-ID: <61ed81c80802271147t3346f52lcb85233fbd3b6884@mail.gmail.com> Date: Wed, 27 Feb 2008 11:47:39 -0800 From: "=?UTF-8?Q?Amol_Dharmadhikar?= =?UTF-8?Q?i_=E0=A4=85=E0=A4=AE=E0=A5=8B=E0=A4=B2_=E0=A4=A7=E0=A4=B0?= =?UTF-8?Q?=E0=A5=8D=E0=A4=AE=E0=A4=BE=E0=A4=A7?= =?UTF-8?Q?=E0=A5=80=E0=A4=95=E0=A4=BE=E0=A4=B0=E0=A5=80?=" To: "John Hein" In-Reply-To: <18373.47157.425456.583623@gromit.timing.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <18373.33662.614583.231211@gromit.timing.com> <20080227190448.GA50031@kobe.laptop> <18373.47157.425456.583623@gromit.timing.com> Cc: Giorgos Keramidas , hackers@freebsd.org Subject: Re: cvs tag renaming after repo copy 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, 27 Feb 2008 20:12:26 -0000 On Wed, Feb 27, 2008 at 11:21 AM, John Hein wrote: > Giorgos Keramidas wrote at 21:04 +0200 on Feb 27, 2008: > > > On 2008-02-27 08:36, John Hein wrote: > > > Can someone point me at a script that does tag renaming > > > after a repo copy? > > > > You don't really need a `script' to do this. > > > > Tags in CVS are not versioned, so you can force-tag the repo-copied > > files and move the tag to its new place. > > > > For example if you have two files: > > > > foo.c,v > > bar.c,v > > > > and bar.c,v is a repo-copy of foo.c,v then you move the tag only for the > > bar.c file by checking it out, and running: > > > > cvs tag -f -r 1.2 bar.c > ------------------------^^^ you're missing the tag name in this example, but... > > > This should force/move the tag to point revision 1.2. > > I don't want to move the tag... I want to invalidate old tags by > renaming them to something else (like foo-1-2-3 -> old_foo-1-2-3). > > Note that just using cvs to rename a tag (by tagging with the new name > and then removing the former name) has issues when you try to do that > with branch tags. > > Anyway, I'm pretty sure the FreeBSD cvs-meisters run something to > invalidate tags after doing a repo copy. That's the information I was > looking for. > I dont think you can rename tags using a single command. What you can do instead is create a new tag at the same point as the old tag, and then delete the old tag. eg - cvs rtag -r old-foo-1-2-3 new-foo-1-2-3 cvs rtag -d old-foo-1-2-3 Amol From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 20:28:59 2008 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 5C52C106566B for ; Wed, 27 Feb 2008 20:28:59 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from mx.nitro.dk (zarniwoop.nitro.dk [83.92.207.38]) by mx1.freebsd.org (Postfix) with ESMTP id 0CB158FC1E for ; Wed, 27 Feb 2008 20:28:51 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from zaphod.nitro.dk (unknown [192.168.3.39]) by mx.nitro.dk (Postfix) with ESMTP id 0082D1E8C44; Wed, 27 Feb 2008 20:11:54 +0000 (UTC) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 1BAFB11492; Wed, 27 Feb 2008 12:12:04 -0800 (PST) Date: Wed, 27 Feb 2008 12:12:04 -0800 From: "Simon L. Nielsen" To: John Hein Message-ID: <20080227201203.GA1101@zaphod.nitro.dk> References: <18373.33662.614583.231211@gromit.timing.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18373.33662.614583.231211@gromit.timing.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: hackers@freebsd.org Subject: Re: cvs tag renaming after repo copy 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, 27 Feb 2008 20:28:59 -0000 On 2008.02.27 08:36:30 -0700, John Hein wrote: > Can someone point me at a script that does tag renaming > after a repo copy? John Polstra has made a script (Fixtags) for it which we use for the FreeBSD repository. I don't think he has any problems with it being distributed, but as it doesn't have a copyright statement i just want to ask before I distribute it... -- Simon L. Nielsen Hat: FreeBSD.org cvsmeister From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 21:07:50 2008 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 E0162106566C for ; Wed, 27 Feb 2008 21:07:50 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mail0.rawbw.com (mail0.rawbw.com [198.144.192.41]) by mx1.freebsd.org (Postfix) with ESMTP id D096B8FC13 for ; Wed, 27 Feb 2008 21:07:50 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mail0.rawbw.com (localhost [127.0.0.1]) by mail0.rawbw.com (8.13.8/8.13.8) with ESMTP id m1RL7o9l002078; Wed, 27 Feb 2008 13:07:50 -0800 (PST) Received: (from www@localhost) by mail0.rawbw.com (8.13.8/8.13.8/Submit) id m1RL7oTZ002077; Wed, 27 Feb 2008 13:07:50 -0800 (PST) X-Authentication-Warning: mail0.rawbw.com: www set sender to yuri@rawbw.com using -f Received: from ip224.carlyle.sfo.ygnition.net (ip224.carlyle.sfo.ygnition.net [24.219.144.224]) by webmail.rawbw.com (IMP) with HTTP for ; Wed, 27 Feb 2008 13:07:50 -0800 Message-ID: <1204146470.47c5d1267ceee@webmail.rawbw.com> Date: Wed, 27 Feb 2008 13:07:50 -0800 From: Yuri To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.1 X-Originating-IP: 24.219.144.224 Subject: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver? 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, 27 Feb 2008 21:07:51 -0000 I have a Linksys PCI wireless card that is being attached by "ral" driver: ral0: mem 0xcffe8000-0xcffeffff irq 17 at device 10.0 on pci0 ral0: MAC/BBP RT2561C, RF RT2527 ral0: Ethernet address: 00:18:f8:2e:40:25 ral0: [ITHREAD] But when I do 'ifconfig ral0 list caps' it returns: ral0=2181e500 and WEP isn't there. This looks amazing since WEP is older and very widespread. So how can I tell if this card can't really support WEP or it's the driver that can't support it? Also command: ifconfig ral0 inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap wepmode on weptxkey 3 wepkey 3:0x3456789012 authmode open mode 11g mediaopt hostap succeeds though CAPS doesn't have WEP. Isn't this a bug? Yuri From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 21:30:14 2008 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 A04CF106566C for ; Wed, 27 Feb 2008 21:30:14 +0000 (UTC) (envelope-from yuri@tsoft.com) Received: from shell.rawbw.com (shell.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8F80F8FC13 for ; Wed, 27 Feb 2008 21:30:14 +0000 (UTC) (envelope-from yuri@tsoft.com) Received: from eagle.syrec.org (ip224.carlyle.sfo.ygnition.net [24.219.144.224]) (authenticated bits=0) by shell.rawbw.com (8.13.6/8.13.6) with ESMTP id m1RKpZZv042899 for ; Wed, 27 Feb 2008 12:51:35 -0800 (PST) Message-ID: <47C5CD60.9090607@tsoft.com> Date: Wed, 27 Feb 2008 12:51:44 -0800 From: Yuri User-Agent: Thunderbird 2.0.0.9 (X11/20080122) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 27 Feb 2008 21:34:31 +0000 Subject: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuri@tsoft.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 21:30:14 -0000 I have a Linksys PCI wireless card that is being attached by "ral" driver: ral0: mem 0xcffe8000-0xcffeffff irq 17 at device 10.0 on pci0 ral0: MAC/BBP RT2561C, RF RT2527 ral0: Ethernet address: 00:18:f8:2e:40:25 ral0: [ITHREAD] But when I do 'ifconfig ral0 list caps' it returns: ral0=2181e500 and WEP isn't there. This looks amazing since WEP is older and very widespread. So how can I tell if this card can't really support WEP or it's the driver that can't support it? Also command: ifconfig ral0 inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap wepmode on weptxkey 3 wepkey 3:0x3456789012 authmode open mode 11g mediaopt hostap succeeds though CAPS doesn't have WEP. Isn't this a bug? Yuri From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 21:41:11 2008 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 82B2E106566B for ; Wed, 27 Feb 2008 21:41:11 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 5C66D8FC27 for ; Wed, 27 Feb 2008 21:41:11 +0000 (UTC) (envelope-from sam@errno.com) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m1RLfAmp020217 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Feb 2008 13:41:11 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <47C5D8F6.20608@errno.com> Date: Wed, 27 Feb 2008 13:41:10 -0800 From: Sam Leffler User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: Yuri References: <1204146470.47c5d1267ceee@webmail.rawbw.com> In-Reply-To: <1204146470.47c5d1267ceee@webmail.rawbw.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-hackers@freebsd.org Subject: Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver? 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, 27 Feb 2008 21:41:11 -0000 Yuri wrote: > I have a Linksys PCI wireless card that is being attached by "ral" driver: > ral0: mem 0xcffe8000-0xcffeffff irq 17 at device > 10.0 on pci0 > ral0: MAC/BBP RT2561C, RF RT2527 > ral0: Ethernet address: 00:18:f8:2e:40:25 > ral0: [ITHREAD] > > But when I do 'ifconfig ral0 list caps' it returns: > ral0=2181e500 > and WEP isn't there. > > This looks amazing since WEP is older and very widespread. > > So how can I tell if this card can't really support WEP or it's the driver that > can't support it? > WEP is always supported. The WEP capability bit means the driver uses the hardware. Many driver writers were too lazy to implement full driver support and just fall back on the host to do crypto. > Also command: > ifconfig ral0 inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap wepmode on > weptxkey 3 wepkey 3:0x3456789012 authmode open mode 11g mediaopt hostap > succeeds though CAPS doesn't have WEP. > Isn't this a bug? > > No, see above. Sam From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 22:01:44 2008 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 527941065678 for ; Wed, 27 Feb 2008 22:01:44 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mail0.rawbw.com (mail0.rawbw.com [198.144.192.41]) by mx1.freebsd.org (Postfix) with ESMTP id 3947B8FC1D for ; Wed, 27 Feb 2008 22:01:44 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mail0.rawbw.com (localhost [127.0.0.1]) by mail0.rawbw.com (8.13.8/8.13.8) with ESMTP id m1RM0MUD004564; Wed, 27 Feb 2008 14:00:22 -0800 (PST) Received: (from www@localhost) by mail0.rawbw.com (8.13.8/8.13.8/Submit) id m1RM0MGA004563; Wed, 27 Feb 2008 14:00:22 -0800 (PST) X-Authentication-Warning: mail0.rawbw.com: www set sender to yuri@rawbw.com using -f Received: from ip139.carlyle.sfo.ygnition.net (ip139.carlyle.sfo.ygnition.net [24.219.144.139]) by webmail.rawbw.com (IMP) with HTTP for ; Wed, 27 Feb 2008 14:00:22 -0800 Message-ID: <1204149622.47c5dd76995ba@webmail.rawbw.com> Date: Wed, 27 Feb 2008 14:00:22 -0800 From: Yuri To: Sam Leffler References: <1204146470.47c5d1267ceee@webmail.rawbw.com> <47C5D8F6.20608@errno.com> In-Reply-To: <47C5D8F6.20608@errno.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.1 X-Originating-IP: 24.219.144.139 Cc: freebsd-hackers@freebsd.org Subject: Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver? 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, 27 Feb 2008 22:01:44 -0000 > WEP is always supported. The WEP capability bit means the driver uses > the hardware. Many driver writers were too lazy to implement full > driver support and just fall back on the host to do crypto. I see. I am sure anybody who doesn't know this will get confused and will have the same question. Isn't it better to have 2 separate flags in CAPS: for example WEP and WEPHW? WEP would mean that WEP is supported and WEPHW would mean that it's supported through hardware. Yuri From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 22:28:47 2008 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 31EC8106566C for ; Wed, 27 Feb 2008 22:28:47 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron1.sfsu.edu (iron1.sfsu.edu [130.212.10.35]) by mx1.freebsd.org (Postfix) with ESMTP id 168308FC19 for ; Wed, 27 Feb 2008 22:28:46 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAL9yxUeC1Apk/2dsb2JhbACuaw Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron1.sfsu.edu with ESMTP; 27 Feb 2008 14:28:46 -0800 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF100) with ESMTP id 2008022714284518-31 ; Wed, 27 Feb 2008 14:28:45 -0800 Date: Wed, 27 Feb 2008 14:28:45 -0800 (PST) From: KAYVEN RIESE To: Sam Leffler In-Reply-To: <47C5D8F6.20608@errno.com> Message-ID: References: <1204146470.47c5d1267ceee@webmail.rawbw.com> <47C5D8F6.20608@errno.com> MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF100 | December 5, 2007) at 02/27/2008 14:28:45, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF312 | February 8, 2008) at 02/27/2008 14:28:46, Serialize complete at 02/27/2008 14:28:46 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Yuri , freebsd-hackers@freebsd.org Subject: Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver? 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, 27 Feb 2008 22:28:47 -0000 On Wed, 27 Feb 2008, Sam Leffler wrote: > Yuri wrote: >> I have a Linksys PCI wireless card that is being attached by "ral" driver: >> ral0: mem 0xcffe8000-0xcffeffff irq 17 at >> device >> 10.0 on pci0 >> ral0: MAC/BBP RT2561C, RF RT2527 >> ral0: Ethernet address: 00:18:f8:2e:40:25 >> ral0: [ITHREAD] >> >> But when I do 'ifconfig ral0 list caps' it returns: >> ral0=2181e500 >> and WEP isn't there. >> >> This looks amazing since WEP is older and very widespread. I am about to do a talk on WEP versus WPA for a course in internet security. I became acquainted with the protocols through a 60 minutes story. http://tinyurl.com/2wucm3 WEP is not fully secure. WPA or WPA2 is the improvement. The above story notes that American businesses are in arears with respect to properly upgrading the wireless routers that they use for financial processing. >> >> So how can I tell if this card can't really support WEP or it's the driver >> that >> can't support it? >> > > WEP is always supported. The WEP capability bit means the driver uses the > hardware. Many driver writers were too lazy to implement full driver support > and just fall back on the host to do crypto. > >> Also command: >> ifconfig ral0 inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap wepmode >> on >> weptxkey 3 wepkey 3:0x3456789012 authmode open mode 11g mediaopt hostap >> succeeds though CAPS doesn't have WEP. >> Isn't this a bug? >> >> > > No, see above. > > Sam > > _______________________________________________ > 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" > *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 22:41:08 2008 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 627451065673 for ; Wed, 27 Feb 2008 22:41:08 +0000 (UTC) (envelope-from jimmy@mammothcheese.ca) Received: from smtprelay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by mx1.freebsd.org (Postfix) with ESMTP id 2BD938FC1C for ; Wed, 27 Feb 2008 22:41:07 +0000 (UTC) (envelope-from jimmy@mammothcheese.ca) Received: from smtprelay.hostedemail.com (ff-bigip1 [10.5.19.254]) by smtpgrave02.hostedemail.com (Postfix) with ESMTP id 355E4D808 for ; Wed, 27 Feb 2008 22:23:56 +0000 (UTC) Received: from emd2-omf02.hostedemail.com (ff-bigip1 [10.5.19.254]) by smtprelay01.hostedemail.com (Postfix) with ESMTP id B277EE2D94; Wed, 27 Feb 2008 22:23:54 +0000 (UTC) X-SpamScore: 30 X-Spamcatcher-Summary: 30, 2, 0, e4013d13fb5189ca, a89d87f3f5ce8227, jimmy@mammothcheese.ca, -, RULES_HIT:152:355:375:379:599:967:973:980:983:988:989:1212:1224:1260:1311:1313:1314:1345:1431:1437:1513:1515:1516:1517:1521:1534:1541:1567:1593:1594:1676:1699:1711:1714:1730:1747:1766:1792:2068:2069:2196:2198:2199:2200:2393:2525:2553:2559:2564:2682:2685:2737:2827:2857:2859:2902:2904:2933:2937:2939:2942:2945:2947:2951:2954:3022:3027:3865:3867:3868:3869:3870:3871:3934:3936:3938:3941:3944:4250: 4321:4699:5007:6119:6261:7514:7679, 0, RBL:none, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:, MSBL:none, DNSBL:none X-Spamcatcher-Explanation: (50%) BODY: text/html email has no html tag; (50%) BODY: content type is strictly "text/html"; Received: from webmail03 (imap-ext [216.40.42.5]) (Authenticated sender: jimmy@mammothcheese.ca) by emd2-omf02.hostedemail.com (Postfix) with ESMTP; Wed, 27 Feb 2008 22:23:54 +0000 (UTC) Date: Wed, 27 Feb 2008 22:23:54 +0000 (GMT) From: To: mark.linn@gmail.com Message-ID: <1702965342.3351204151034722.JavaMail.mail@webmail03> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, jimmy@mammothcheese.ca Subject: Re: Re: non-blocking io, EINTR X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jimmy@mammothcheese.ca List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 22:41:08 -0000 The author is=C2=A0just trying to=C2=A0make his reads and w= rites=C2=A0robust. The=C2=A0functions he=C2=A0has written have no kno= wledge whether or not signals have been set to=C2=A0interrupt system = calls, so he makes sure they test for EINTR in case they have been. On Feb 27, 2008, mark.linn@gmail.com wro= te: Thanks, E= d and James, Then why in the world the sample code in this acm p= aper would test EINTR in read and write? link is here. [1]http://delivery.acm.org/10.1145/1350000/= 1344155/9815.html?key1=3D1344155&key2=3D2950393021&coll=3DGUIDE&= ;dl=3D&CFID=3D15151515&CFTOKEN=3D6184618 References 1. 3D"http://delivery.acm.org/10.1145/1350000/1344155/9815.html= From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 23:35:59 2008 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 E3E3010676BA for ; Wed, 27 Feb 2008 23:35:59 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell.rawbw.com (shell.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id B0F288FC1D for ; Wed, 27 Feb 2008 23:35:59 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from eagle.syrec.org (ip224.carlyle.sfo.ygnition.net [24.219.144.224]) (authenticated bits=0) by shell.rawbw.com (8.13.6/8.13.6) with ESMTP id m1RNYa6N038502; Wed, 27 Feb 2008 15:34:36 -0800 (PST) Message-ID: <47C5F395.1050105@rawbw.com> Date: Wed, 27 Feb 2008 15:34:45 -0800 From: Yuri User-Agent: Thunderbird 2.0.0.9 (X11/20080122) MIME-Version: 1.0 To: KAYVEN RIESE References: <1204146470.47c5d1267ceee@webmail.rawbw.com> <47C5D8F6.20608@errno.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuri@rawbw.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 23:36:00 -0000 KAYVEN RIESE wrote: > I am about to do a talk on WEP versus WPA for a course in internet > security. I became acquainted with the protocols through a > 60 minutes story. > > http://tinyurl.com/2wucm3 > > WEP is not fully secure. WPA or WPA2 is the improvement. The > above story notes that American businesses are in arears with > respect to properly upgrading the wireless routers that they > use for financial processing. > Sorry, Your response has nothing to do with the question. Yuri From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 23:39:47 2008 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 2188110679B8 for ; Wed, 27 Feb 2008 23:39:47 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron3.sfsu.edu (iron3.sfsu.edu [130.212.10.128]) by mx1.freebsd.org (Postfix) with ESMTP id 0230E8FC14 for ; Wed, 27 Feb 2008 23:39:46 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CACeDxUeC1Apk/2dsb2JhbACuUg Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron3.sfsu.edu with ESMTP; 27 Feb 2008 15:39:45 -0800 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF100) with ESMTP id 2008022715394523-39 ; Wed, 27 Feb 2008 15:39:45 -0800 Date: Wed, 27 Feb 2008 15:39:45 -0800 (PST) From: KAYVEN RIESE To: Yuri In-Reply-To: <47C5F395.1050105@rawbw.com> Message-ID: References: <1204146470.47c5d1267ceee@webmail.rawbw.com> <47C5D8F6.20608@errno.com> <47C5F395.1050105@rawbw.com> MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF100 | December 5, 2007) at 02/27/2008 15:39:45, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF312 | February 8, 2008) at 02/27/2008 15:39:46, Serialize complete at 02/27/2008 15:39:46 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver? 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, 27 Feb 2008 23:39:47 -0000 On Wed, 27 Feb 2008, Yuri wrote: > KAYVEN RIESE wrote: >> >> WEP is not fully secure. WPA or WPA2 is the improvement. The >> above story notes that American businesses are in arears with >> respect to properly upgrading the wireless routers that they >> use for financial processing. >> > Sorry, Your response has nothing to do with the question. I tend to beg to differ. Backward compatibility standards imply the answer to your question (that was actually already answered anyway). I considered it relevant to realize the importance of WPA upgrade. Sorry if you already knew that and I wasted your time. > > Yuri > > *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 27 23:50:19 2008 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 D65041067FB0 for ; Wed, 27 Feb 2008 23:50:19 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell.rawbw.com (shell.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id BD27E8FC1A for ; Wed, 27 Feb 2008 23:50:19 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from eagle.syrec.org (ip224.carlyle.sfo.ygnition.net [24.219.144.224]) (authenticated bits=0) by shell.rawbw.com (8.13.6/8.13.6) with ESMTP id m1RNoJ3f045868 for ; Wed, 27 Feb 2008 15:50:19 -0800 (PST) Message-ID: <47C5F744.8020608@rawbw.com> Date: Wed, 27 Feb 2008 15:50:28 -0800 From: Yuri User-Agent: Thunderbird 2.0.0.9 (X11/20080122) MIME-Version: 1.0 References: <1204146470.47c5d1267ceee@webmail.rawbw.com> <47C5D8F6.20608@errno.com> <1204149622.47c5dd76995ba@webmail.rawbw.com> <47C5F356.3000101@FreeBSD.org> In-Reply-To: <47C5F356.3000101@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org Subject: Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuri@rawbw.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 23:50:20 -0000 Pietro Cerutti wrote: > It wouldn't make sense. Flags are used to specify capabilities of the > > interface, not things provided by the operating system. > > This is very confusing to user. User is assumed to have this bit of knowledge that WEP flag actually means only hardware support, not support in general. On another note WEP is actually supported by interface but driver authors didn't bother to use it. So WEP flag doesn't represent actual capabilities of the interface and this is again confusing. When I type 'ifconfig ...' I am mostly interested what can I use from that side, not what is supported by hardware. Is there any way to know what is logically supported by network interface as passed to 'ifconfig' vs. what is supported by hardware interface? Yuri From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 00:52:41 2008 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 E8CF21065671 for ; Thu, 28 Feb 2008 00:52:41 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id B677D8FC22 for ; Thu, 28 Feb 2008 00:52:41 +0000 (UTC) (envelope-from sam@errno.com) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m1S0qeSn021547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Feb 2008 16:52:41 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <47C605D8.1030106@errno.com> Date: Wed, 27 Feb 2008 16:52:40 -0800 From: Sam Leffler User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: yuri@rawbw.com References: <1204146470.47c5d1267ceee@webmail.rawbw.com> <47C5D8F6.20608@errno.com> <1204149622.47c5dd76995ba@webmail.rawbw.com> <47C5F356.3000101@FreeBSD.org> <47C5F744.8020608@rawbw.com> In-Reply-To: <47C5F744.8020608@rawbw.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-SIHOPE-DCC-3-Metrics: ebb.errno.com; whitelist Cc: freebsd-hackers@freebsd.org Subject: Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 00:52:42 -0000 Yuri wrote: > Pietro Cerutti wrote: >> It wouldn't make sense. Flags are used to specify capabilities of the >> interface, not things provided by the operating system. >> >> > This is very confusing to user. > User is assumed to have this bit of knowledge that WEP flag actually > means only hardware support, not support in general. > > On another note WEP is actually supported by interface but driver authors > didn't bother to use it. So WEP flag doesn't represent actual > capabilities of > the interface and this is again confusing. > > When I type 'ifconfig ...' I am mostly interested what can I > use from > that side, not what is supported by hardware. Is there any way to know > what is > logically supported by network interface as passed to 'ifconfig' vs. what > is supported by hardware interface? If you cannot use a feature you'll get an error when you try to use it. There simply are not enough capability bits around to waste on features that are always true. If I reorg this stuff (and I intend to to split crypto out into a separate features word because we are out of bits) then I can look into expanding the status. To be honest you're the first person that's even noticed you can list capabilities in the 3+ years that's been in place (or at least made public mention). Hardly seems like something that's constantly confused people. Sam From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 01:16:03 2008 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 5A8BF106566C for ; Thu, 28 Feb 2008 01:16:03 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell.rawbw.com (shell.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3DC148FC1A for ; Thu, 28 Feb 2008 01:16:02 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from eagle.syrec.org (ip224.carlyle.sfo.ygnition.net [24.219.144.224]) (authenticated bits=0) by shell.rawbw.com (8.13.6/8.13.6) with ESMTP id m1S1Efkf090089; Wed, 27 Feb 2008 17:14:41 -0800 (PST) Message-ID: <47C60B0A.3060205@rawbw.com> Date: Wed, 27 Feb 2008 17:14:50 -0800 From: Yuri User-Agent: Thunderbird 2.0.0.9 (X11/20080122) MIME-Version: 1.0 To: Sam Leffler References: <1204146470.47c5d1267ceee@webmail.rawbw.com> <47C5D8F6.20608@errno.com> <1204149622.47c5dd76995ba@webmail.rawbw.com> <47C5F356.3000101@FreeBSD.org> <47C5F744.8020608@rawbw.com> <47C605D8.1030106@errno.com> In-Reply-To: <47C605D8.1030106@errno.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuri@rawbw.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 01:16:03 -0000 Sam Leffler wrote: > If you cannot use a feature you'll get an error when you try to use > it. There simply are not enough capability bits around to waste on > features that are always true. If I reorg this stuff (and I intend to > to split crypto out into a separate features word because we are out > of bits) then I can look into expanding the status. > Exactly, I got errors while trying to use WEP with FreeBSD-based wireless access point. And I looked in four eyes at all options and capabilities. And I first thought that WEP support is a problem. Basically AP with WEP encryption doesn't work with this card. Now I wonder if this software-based WEP support can be responsible for this failure. > To be honest you're the first person that's even noticed you can list > capabilities in the 3+ years that's been in place (or at least made > public mention). Hardly seems like something that's constantly > confused people. > Ok I will correct myself: this is very confusing to people who look and notice. Though there are not too many obviously. But caps are mentioned in the handbook. And it particularly says there: ifconfig /ath0/ list caps This output displays the card capabilities Various supported ciphers are also mentioned: WEP, TKIP, WPA2, etc., these informations are important to know what security protocols could be set on the Access Point. So from this one can conclude that WEP isn't supported. I guess it's good to mention here that WEP is always supported no matter what WEP flag says. Yuri From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 01:27:23 2008 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 217DB1065708 for ; Thu, 28 Feb 2008 01:27:23 +0000 (UTC) (envelope-from kayve@sfsu.edu) Received: from iron1.sfsu.edu (iron1.sfsu.edu [130.212.10.35]) by mx1.freebsd.org (Postfix) with ESMTP id 02B968FC34 for ; Thu, 28 Feb 2008 01:27:22 +0000 (UTC) (envelope-from kayve@sfsu.edu) X-onepass: IPPSC X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CALicxUeC1Apk/2dsb2JhbACubA Received: from smtp01.sfsu.edu ([130.212.10.100]) by iron1.sfsu.edu with ESMTP; 27 Feb 2008 17:27:22 -0800 Received: from libra.sfsu.edu ([130.212.10.238]) by mail05a.sfsu.edu (Lotus Domino Release 7.0.3HF100) with ESMTP id 2008022717272031-55 ; Wed, 27 Feb 2008 17:27:20 -0800 Date: Wed, 27 Feb 2008 17:27:20 -0800 (PST) From: KAYVEN RIESE To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on MAIL05a/SERVERS/SFSU(Release 7.0.3HF100 | December 5, 2007) at 02/27/2008 17:27:20, Serialize by Router on SMTP01/SERVERS/SFSU(Release 7.0.3HF312 | February 8, 2008) at 02/27/2008 17:27:22, Serialize complete at 02/27/2008 17:27:22 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Java 1.6 Berkeley Oracle DB XML Bioinformatics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 01:27:23 -0000 I am in a whirlwind of re(?)installation confusion revolving around making sure I have prerequisites for a Bioinformatics progam. Here is that program's installation page: http://www.fruitfly.org/annot/apollo/install.html I selected the "Any UNIX" to get this script called apolloinst.bin that seems to just set up a bunch of environment variables. I got a JVM error [:: clip command line ::] zip232.tar.gz kv_bsd#sh ./apolloinst.bin Preparing to install... Extracting the installation resources from the installer archive... Configuring the installer for this system's environment... No Java virtual machine could be found from your PATH environment variable. You must install a VM prior to running this program. kv_bsd#echo $PATH /sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/root/bin kv_bsd#cp apolloinst.bin /usr/home/kayve kv_bsd#uname -a FreeBSD kv_bsd 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 10:40:27 UTC 2007 root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 kv_bsd# [kayve@kv_bsd ~]$ java sdf Exception in thread "main" java.lang.NoClassDefFoundError: sdf [kayve@kv_bsd ~]$ [::end clip::] "kv_bsd#" is root prompt "[kayve@kv_bsd ~]$" is user prompt. I was told to add the line JAVA_HOME="/usr/local/bin/java" to the script, but in the meantime I have been distracted by reinstalling java. Since my error message diagnostic "java [garbage]" above shows that I do have a java, the JVM error made me feel like reinstalling java (spurious and impulsive, I know). My Java 1.6 port installation has been proceeding for over 30 hours now! In the meanwhile, I decided to add the Berkeley Oracle DB port, but got distracted by the possibilities 1)vanilla (??) 2) Java DB or 3) XML DB Are these three possibilities to all be installed, or only one of them? Anyway, with the java 1.6 make still running (I know, nuts.. but fatal?) I decided to make install clean /usr/ports/databases/dbXML and got this message: kv_bsd#cd dbXML/ kv_bsd#make install clean ===> Vulnerability check disabled, database not found => dbXML-Core-1.0b2.tar.gz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from http://heanet.dl.sourceforge.net/sourceforge/dbxml-core/. dbXML-Core-1.0b2.tar.gz 100% of 4799 kB 293 kBps 00m00s ===> Extracting for dbXML-1.0b2_2 => MD5 Checksum OK for dbXML-Core-1.0b2.tar.gz. => SHA256 Checksum OK for dbXML-Core-1.0b2.tar.gz. ===> Patching for dbXML-1.0b2_2 ===> Applying FreeBSD patches for dbXML-1.0b2_2 ===> Configuring for dbXML-1.0b2_2 ===> Installing for dbXML-1.0b2_2 ===> dbXML-1.0b2_2 depends on file: /usr/local/jdk1.3.1/bin/java - not found ===> Verifying install for /usr/local/jdk1.3.1/bin/java in /usr/ports/java/jdk13 ===> jdk-1.3.1p9_8 : Due to licensing restrictions, certain files must be fetched manually. Please open http://www.sun.com/software/communitysource/j2se/java2/download.xml in a web browser and follow the "Download" link for the "Java(TM) 2 SDK 1.3.1". You will be required to log in and register, but you can create an account on this page. After registration and accepting the Sun Community Source License, download the SCSL Source file, j2sdk-1_3_1-src.tar.gz. In addition, please download the patchset, bsd-jdk131-patches-9.tar.gz, from http://www.eyesbeyond.com/freebsddom/java/jdk13.html. Then place the downloaded files in /usr/ports/distfiles and restart the build. .*** Error code 1 Stop in /usr/ports/java/jdk13. *** Error code 1 Stop in /usr/ports/databases/dbXML. kv_bsd#pwd /usr/ports/databases/dbXML kv_bsd# Okay. To boil it down, what is happening with Java 1.6, should I kill it, and is it the right thing to get these older patches and put them in /usr/ports/distfiles.. Oh, also, here are the patches I currently have for the jdks: [kayve@kv_bsd ~]$ ls /usr/ports/distfiles/bsd* /usr/ports/distfiles/bsd-jdk14-patches-8.tar.gz /usr/ports/distfiles/bsd-jdk16-patches-3.tar.bz2 /usr/ports/distfiles/bsd-jdk16-patches-4.tar.bz2 [kayve@kv_bsd ~]$ Does it make sense to keep patches for different versions, and e.g. the jdk patch 3 and patch4 both being there, does that make sense? Is it okay to just get all that patches? Is it best to only have the most recent patch? Does this depend on other ports like dbXML that may NEED something in PARTICULAR from a older patch from the current version or from an older version? *----------------------------------------------------------* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *----------------------------------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 06:26:57 2008 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 CB8721065671 for ; Thu, 28 Feb 2008 06:26:57 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id 482958FC1C for ; Thu, 28 Feb 2008 06:26:57 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so161641uge.37 for ; Wed, 27 Feb 2008 22:26:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=7feoWqW/kST8lDw0ymhjo3vNusCg7icfwweZTDv+uWc=; b=aLSLHHgeogaG3B0l/M9JbqMTO21LLlRn93p9XB7xcD+rsdzBwGBI7mIKzdXwLegKnyKYSucBx6n5hg5eK8XiXLA2CBNA+wbwYEqKlg6SX42QGTPS4oaKaykLunblo26Qv+DAIW6Ei1itmvMVtxLiSybtMBrEQMQyhxymXDHN41U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=MqHjxH/wDBu4TgERPoXoKzqv1JRoLHoSEatnyZlMYjdmV8Tag3yQkZv4+Xb52IRBjtD6bNBS/QgdnEhXvbGshZzIufEpuKAtJ4ar2Lt+OutL2mjehpx8ODHYXPWrnwAjk2PVX0j1LsDfyeNG8o2L+MVue+kRg77cXBiRVA3JFG4= Received: by 10.151.105.13 with SMTP id h13mr2596176ybm.180.1204180015283; Wed, 27 Feb 2008 22:26:55 -0800 (PST) Received: by 10.150.144.2 with HTTP; Wed, 27 Feb 2008 22:26:55 -0800 (PST) Message-ID: Date: Thu, 28 Feb 2008 15:26:55 +0900 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: obrien@freebsd.org, "Adrian Chadd" , freebsd-hackers@freebsd.org, hackers@freebsd.org In-Reply-To: <20080227193234.GB54600@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080225174410.GA81874@dragon.NUXI.org> <20080227193234.GB54600@dragon.NUXI.org> X-Google-Sender-Auth: 5d51d1e488d36cc3 Cc: Subject: Re: Modular type GENERIC? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 06:26:57 -0000 On 28/02/2008, David O'Brien wrote: > On Tue, Feb 26, 2008 at 01:56:28PM +0900, Adrian Chadd wrote: > > On 26/02/2008, David O'Brien wrote: > > > > > As you've shown the magic is in the loader.conf. I don't know a good way > > > to handle this other than attempt to load every module (like Microsoft NT > > > installer does) - and hope the probe of a driver that doesn't claim a > > > device doesn't leave that device in a bad state. > > > > > > Have you tried putting every module in /boot/kernel into loader.conf in a > > > "load" statement? > > > > I'm going to try doing that tonight. > > > Cool. Please let us(me) know how it goes. Is there some sane-ish way of auto-generating a list of modules given a config file? The "device" statements don't match up with the module name in all bar 4 or 5 places. Is there some chain of files I can munge to match things up? Adrian -- Adrian Chadd - adrian@freebsd.org From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 06:26:57 2008 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 CFA731065675 for ; Thu, 28 Feb 2008 06:26:57 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.freebsd.org (Postfix) with ESMTP id 4A7D98FC1D for ; Thu, 28 Feb 2008 06:26:57 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so161643uge.37 for ; Wed, 27 Feb 2008 22:26:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=7feoWqW/kST8lDw0ymhjo3vNusCg7icfwweZTDv+uWc=; b=aLSLHHgeogaG3B0l/M9JbqMTO21LLlRn93p9XB7xcD+rsdzBwGBI7mIKzdXwLegKnyKYSucBx6n5hg5eK8XiXLA2CBNA+wbwYEqKlg6SX42QGTPS4oaKaykLunblo26Qv+DAIW6Ei1itmvMVtxLiSybtMBrEQMQyhxymXDHN41U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=MqHjxH/wDBu4TgERPoXoKzqv1JRoLHoSEatnyZlMYjdmV8Tag3yQkZv4+Xb52IRBjtD6bNBS/QgdnEhXvbGshZzIufEpuKAtJ4ar2Lt+OutL2mjehpx8ODHYXPWrnwAjk2PVX0j1LsDfyeNG8o2L+MVue+kRg77cXBiRVA3JFG4= Received: by 10.151.105.13 with SMTP id h13mr2596176ybm.180.1204180015283; Wed, 27 Feb 2008 22:26:55 -0800 (PST) Received: by 10.150.144.2 with HTTP; Wed, 27 Feb 2008 22:26:55 -0800 (PST) Message-ID: Date: Thu, 28 Feb 2008 15:26:55 +0900 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: obrien@freebsd.org, "Adrian Chadd" , freebsd-hackers@freebsd.org, hackers@freebsd.org In-Reply-To: <20080227193234.GB54600@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080225174410.GA81874@dragon.NUXI.org> <20080227193234.GB54600@dragon.NUXI.org> X-Google-Sender-Auth: 5d51d1e488d36cc3 Cc: Subject: Re: Modular type GENERIC? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 06:26:57 -0000 On 28/02/2008, David O'Brien wrote: > On Tue, Feb 26, 2008 at 01:56:28PM +0900, Adrian Chadd wrote: > > On 26/02/2008, David O'Brien wrote: > > > > > As you've shown the magic is in the loader.conf. I don't know a good way > > > to handle this other than attempt to load every module (like Microsoft NT > > > installer does) - and hope the probe of a driver that doesn't claim a > > > device doesn't leave that device in a bad state. > > > > > > Have you tried putting every module in /boot/kernel into loader.conf in a > > > "load" statement? > > > > I'm going to try doing that tonight. > > > Cool. Please let us(me) know how it goes. Is there some sane-ish way of auto-generating a list of modules given a config file? The "device" statements don't match up with the module name in all bar 4 or 5 places. Is there some chain of files I can munge to match things up? Adrian -- Adrian Chadd - adrian@freebsd.org From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 06:44:17 2008 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 EAA001065670; Thu, 28 Feb 2008 06:44:17 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id BB9B98FC2D; Thu, 28 Feb 2008 06:44:17 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id m1S6iHG8098303; Wed, 27 Feb 2008 22:44:17 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.2/8.14.1/Submit) id m1S6iHKJ098302; Wed, 27 Feb 2008 22:44:17 -0800 (PST) (envelope-from obrien) Date: Wed, 27 Feb 2008 22:44:17 -0800 From: "David O'Brien" To: Adrian Chadd Message-ID: <20080228064417.GA98258@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Adrian Chadd , freebsd-hackers@freebsd.org, hackers@freebsd.org References: <20080225174410.GA81874@dragon.NUXI.org> <20080227193234.GB54600@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-hackers@freebsd.org, hackers@freebsd.org Subject: Re: Modular type GENERIC? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 06:44:18 -0000 On Thu, Feb 28, 2008 at 03:26:55PM +0900, Adrian Chadd wrote: > Is there some sane-ish way of auto-generating a list of modules given > a config file? The "device" statements don't match up with the module > name in all bar 4 or 5 places. Is there some chain of files I can > munge to match things up? Not that I know of. :-( -- -- David (obrien@FreeBSD.org) From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 06:44:17 2008 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 EAA001065670; Thu, 28 Feb 2008 06:44:17 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id BB9B98FC2D; Thu, 28 Feb 2008 06:44:17 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id m1S6iHG8098303; Wed, 27 Feb 2008 22:44:17 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.2/8.14.1/Submit) id m1S6iHKJ098302; Wed, 27 Feb 2008 22:44:17 -0800 (PST) (envelope-from obrien) Date: Wed, 27 Feb 2008 22:44:17 -0800 From: "David O'Brien" To: Adrian Chadd Message-ID: <20080228064417.GA98258@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Adrian Chadd , freebsd-hackers@freebsd.org, hackers@freebsd.org References: <20080225174410.GA81874@dragon.NUXI.org> <20080227193234.GB54600@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-hackers@freebsd.org, hackers@freebsd.org Subject: Re: Modular type GENERIC? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 06:44:18 -0000 On Thu, Feb 28, 2008 at 03:26:55PM +0900, Adrian Chadd wrote: > Is there some sane-ish way of auto-generating a list of modules given > a config file? The "device" statements don't match up with the module > name in all bar 4 or 5 places. Is there some chain of files I can > munge to match things up? Not that I know of. :-( -- -- David (obrien@FreeBSD.org) From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 06:50:34 2008 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 DFF2E106566B for ; Thu, 28 Feb 2008 06:50:34 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.178]) by mx1.freebsd.org (Postfix) with ESMTP id 45F4A8FC19 for ; Thu, 28 Feb 2008 06:50:34 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by el-out-1112.google.com with SMTP id r27so2977212ele.3 for ; Wed, 27 Feb 2008 22:50:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=OHYKxtWPHx09/M7O/EPt8Se9bghXf7SMq5Ne4NbGzlw=; b=ZYJyBY1vEjX1XpSxBeHHfuMfiIL5ORpJ3iDn5mejxOa7uk5EiyK5Ie2JMRq/lTgonj8LIa5LvXeH0rx4d176BkIor98/5/psTmflMNPO1tSFfXvXV8g5iq6i1WJpNz33RAIFlcKk7SR0nzfN8GcEBWdUtvpceCAED2DDuZ+VRaY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=v22uAQGzqZbJMw4vlICSsqK8zKTUQyYoQMpaG3fgQoPR9/E6GqwugyZgUvAiBrQYthzKuNtMyJ95qGqDFSgSvEhNMAAwg1gN1bONeqeh8Un3MecU8VZj4sPfUZbyE9xx65hxfDni5WfMoBFxaHeeyvX0IHQGss3OLfMqaNKAYaI= Received: by 10.150.192.7 with SMTP id p7mr2601108ybf.90.1204181433580; Wed, 27 Feb 2008 22:50:33 -0800 (PST) Received: by 10.150.144.2 with HTTP; Wed, 27 Feb 2008 22:50:33 -0800 (PST) Message-ID: Date: Thu, 28 Feb 2008 15:50:33 +0900 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: obrien@freebsd.org, "Adrian Chadd" , freebsd-hackers@freebsd.org, hackers@freebsd.org In-Reply-To: <20080228064417.GA98258@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080225174410.GA81874@dragon.NUXI.org> <20080227193234.GB54600@dragon.NUXI.org> <20080228064417.GA98258@dragon.NUXI.org> X-Google-Sender-Auth: 0330b6c50ae772c6 Cc: Subject: Re: Modular type GENERIC? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 06:50:35 -0000 On 28/02/2008, David O'Brien wrote: > On Thu, Feb 28, 2008 at 03:26:55PM +0900, Adrian Chadd wrote: > > Is there some sane-ish way of auto-generating a list of modules given > > a config file? The "device" statements don't match up with the module > > name in all bar 4 or 5 places. Is there some chain of files I can > > munge to match things up? > > Not that I know of. :-( Crap. I may have to hand-massage something together just for testing then. Adrian -- Adrian Chadd - adrian@freebsd.org From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 06:50:35 2008 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 27A061065672 for ; Thu, 28 Feb 2008 06:50:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.179]) by mx1.freebsd.org (Postfix) with ESMTP id 4F5EA8FC26 for ; Thu, 28 Feb 2008 06:50:34 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by el-out-1112.google.com with SMTP id r27so2977213ele.3 for ; Wed, 27 Feb 2008 22:50:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=OHYKxtWPHx09/M7O/EPt8Se9bghXf7SMq5Ne4NbGzlw=; b=ZYJyBY1vEjX1XpSxBeHHfuMfiIL5ORpJ3iDn5mejxOa7uk5EiyK5Ie2JMRq/lTgonj8LIa5LvXeH0rx4d176BkIor98/5/psTmflMNPO1tSFfXvXV8g5iq6i1WJpNz33RAIFlcKk7SR0nzfN8GcEBWdUtvpceCAED2DDuZ+VRaY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=v22uAQGzqZbJMw4vlICSsqK8zKTUQyYoQMpaG3fgQoPR9/E6GqwugyZgUvAiBrQYthzKuNtMyJ95qGqDFSgSvEhNMAAwg1gN1bONeqeh8Un3MecU8VZj4sPfUZbyE9xx65hxfDni5WfMoBFxaHeeyvX0IHQGss3OLfMqaNKAYaI= Received: by 10.150.192.7 with SMTP id p7mr2601108ybf.90.1204181433580; Wed, 27 Feb 2008 22:50:33 -0800 (PST) Received: by 10.150.144.2 with HTTP; Wed, 27 Feb 2008 22:50:33 -0800 (PST) Message-ID: Date: Thu, 28 Feb 2008 15:50:33 +0900 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: obrien@freebsd.org, "Adrian Chadd" , freebsd-hackers@freebsd.org, hackers@freebsd.org In-Reply-To: <20080228064417.GA98258@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080225174410.GA81874@dragon.NUXI.org> <20080227193234.GB54600@dragon.NUXI.org> <20080228064417.GA98258@dragon.NUXI.org> X-Google-Sender-Auth: 0330b6c50ae772c6 Cc: Subject: Re: Modular type GENERIC? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 06:50:35 -0000 On 28/02/2008, David O'Brien wrote: > On Thu, Feb 28, 2008 at 03:26:55PM +0900, Adrian Chadd wrote: > > Is there some sane-ish way of auto-generating a list of modules given > > a config file? The "device" statements don't match up with the module > > name in all bar 4 or 5 places. Is there some chain of files I can > > munge to match things up? > > Not that I know of. :-( Crap. I may have to hand-massage something together just for testing then. Adrian -- Adrian Chadd - adrian@freebsd.org From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 08:33:26 2008 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 16FCB1065670; Thu, 28 Feb 2008 08:33:26 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from falcon.cybervisiontech.com (falcon.cybervisiontech.com [217.20.163.9]) by mx1.freebsd.org (Postfix) with ESMTP id AEDAC8FC28; Thu, 28 Feb 2008 08:33:25 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (localhost [127.0.0.1]) by falcon.cybervisiontech.com (Postfix) with ESMTP id BA70B74400E; Thu, 28 Feb 2008 10:33:24 +0200 (EET) X-Virus-Scanned: Debian amavisd-new at falcon.cybervisiontech.com Received: from falcon.cybervisiontech.com ([127.0.0.1]) by localhost (falcon.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id 0PAqPK9BJGFv; Thu, 28 Feb 2008 10:33:24 +0200 (EET) Received: from [91.193.172.111] (unknown [91.193.172.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by falcon.cybervisiontech.com (Postfix) with ESMTP id 6CF3474400D; Thu, 28 Feb 2008 10:33:23 +0200 (EET) Message-ID: <47C671CF.9020101@icyb.net.ua> Date: Thu, 28 Feb 2008 10:33:19 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.9 (X11/20071208) MIME-Version: 1.0 To: pav@FreeBSD.org References: <200612221824.kBMIOhfM049471@freefall.freebsd.org> <47A2EDB0.8000801@icyb.net.ua> <47A2F404.7010208@icyb.net.ua> <47A735A4.3060506@icyb.net.ua> <47A75B47.2040604@elischer.org> <1202155663.62432.0.camel@ikaros.oook.cz> <47A8754C.5010607@icyb.net.ua> <1202235368.68281.12.camel@ikaros.oook.cz> <1204053786.1799.0.camel@ikaros.oook.cz> In-Reply-To: <1204053786.1799.0.camel@ikaros.oook.cz> Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit Cc: Bruce Evans , freebsd-hackers@FreeBSD.org, scottl@FreeBSD.org, freebsd-fs@FreeBSD.org, Julian Elischer , Remko Lodder Subject: Re: fs/udf: vm pages "overlap" while reading large dir [patch] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 08:33:26 -0000 on 26/02/2008 21:23 Pav Lucistnik said the following: > Pav Lucistnik pí¹e v út 05. 02. 2008 v 19:16 +0100: >> Andriy Gapon pí¹e v út 05. 02. 2008 v 16:40 +0200: >> >>>> Yay, and can you fix the sequential read performance while you're at it? >>>> Kthx! >>> this was almost trivial :-) >>> See the attached patch, first hunk is just for consistency. >>> The code was borrowed from cd9660, only field/variable names are adjusted. > > Just tested it with my shiny new Bluray drive, and it work wonders. > Finally seamless playback of media files off UDF carrying media. > > So, how does it look WRT committing it? > Pav, thank you for the feedback/reminder. In my personal option the latest patch posted and described at the following like is a very good candidate for commit: http://docs.FreeBSD.org/cgi/mid.cgi?47AA43B9.1040608 It might have a couple of style related issues, but it should improve things a bit even if some larger VM/VFS/GEOM issues remain. And by the way, a patch from the following PR would be a good "side-dish" for the above patch: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/78987 I think it is simple and obvious enough. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 09:25:06 2008 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 87A801065672 for ; Thu, 28 Feb 2008 09:25:06 +0000 (UTC) (envelope-from gahr@FreeBSD.org) Received: from cpanel03.rubas-s03.net (cpanel03.rubas-s03.net [195.182.222.73]) by mx1.freebsd.org (Postfix) with ESMTP id 417F48FC1D for ; Thu, 28 Feb 2008 09:25:06 +0000 (UTC) (envelope-from gahr@FreeBSD.org) Received: from 80-218-191-236.dclient.hispeed.ch ([80.218.191.236] helo=gahrtop.localhost) by cpanel03.rubas-s03.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1JUVmt-0006q9-Sp; Thu, 28 Feb 2008 00:34:12 +0100 Message-ID: <47C5F356.3000101@FreeBSD.org> Date: Thu, 28 Feb 2008 00:33:42 +0100 From: Pietro Cerutti Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20080208) MIME-Version: 1.0 To: Yuri References: <1204146470.47c5d1267ceee@webmail.rawbw.com> <47C5D8F6.20608@errno.com> <1204149622.47c5dd76995ba@webmail.rawbw.com> In-Reply-To: <1204149622.47c5dd76995ba@webmail.rawbw.com> X-Enigmail-Version: 0.95.5 OpenPGP: id=9571F78E; url=http://gahr.ch/pgp/ Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cpanel03.rubas-s03.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - FreeBSD.org X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-hackers@freebsd.org Subject: Re: Is it possible that modern wireless card only supports WPA and not WEP or this is a bug in the driver? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 09:25:06 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Yuri wrote: > Isn't it better to have 2 separate flags in CAPS: for example WEP and WEPHW? > WEP would mean that WEP is supported and WEPHW would mean that it's supported > through hardware. It wouldn't make sense. Flags are used to specify capabilities of the interface, not things provided by the operating system. > > Yuri - -- Pietro Cerutti gahr@FreeBSD.org PGP Public Key: http://gahr.ch/pgp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEAREKAAYFAkfF81YACgkQwMJqmJVx946NRQCggHH4abFDjkRObQst1QgXm2Wb UlAAn2Y9B4u9v1o2FYg38txv8VlYjysF =10Nx -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 10:16:23 2008 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 72E221065672; Thu, 28 Feb 2008 10:16:23 +0000 (UTC) (envelope-from pav@FreeBSD.org) Received: from nat-application.b1.lan.prg.vol.cz (nat-application.b1.lan.prg.vol.cz [195.122.204.152]) by mx1.freebsd.org (Postfix) with ESMTP id 091108FC19; Thu, 28 Feb 2008 10:16:20 +0000 (UTC) (envelope-from pav@FreeBSD.org) Received: from pav.hide.vol.cz (localhost [127.0.0.1]) by nat-application.b1.lan.prg.vol.cz (8.14.2/8.14.2) with ESMTP id m1S9xpqi054619; Thu, 28 Feb 2008 10:59:51 +0100 (CET) (envelope-from pav@FreeBSD.org) Received: (from pav@localhost) by pav.hide.vol.cz (8.14.2/8.14.2/Submit) id m1S9xllK054618; Thu, 28 Feb 2008 10:59:47 +0100 (CET) (envelope-from pav@FreeBSD.org) X-Authentication-Warning: pav.hide.vol.cz: pav set sender to pav@FreeBSD.org using -f From: Pav Lucistnik To: Andriy Gapon In-Reply-To: <47C671CF.9020101@icyb.net.ua> References: <200612221824.kBMIOhfM049471@freefall.freebsd.org> <47A2EDB0.8000801@icyb.net.ua> <47A2F404.7010208@icyb.net.ua> <47A735A4.3060506@icyb.net.ua> <47A75B47.2040604@elischer.org> <1202155663.62432.0.camel@ikaros.oook.cz> <47A8754C.5010607@icyb.net.ua> <1202235368.68281.12.camel@ikaros.oook.cz> <1204053786.1799.0.camel@ikaros.oook.cz> <47C671CF.9020101@icyb.net.ua> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-yd8j2hHcryoNidCpOQUb" Date: Thu, 28 Feb 2008 10:59:47 +0100 Message-Id: <1204192787.54462.1.camel@pav.hide.vol.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 FreeBSD GNOME Team Port Cc: Bruce Evans , freebsd-hackers@FreeBSD.org, scottl@FreeBSD.org, freebsd-fs@FreeBSD.org, Julian Elischer , Remko Lodder Subject: Re: fs/udf: vm pages "overlap" while reading large dir [patch] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pav@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 10:16:23 -0000 --=-yd8j2hHcryoNidCpOQUb Content-Type: text/plain; charset=ISO8859-2 Content-Transfer-Encoding: quoted-printable Andriy Gapon p=ED=B9e v =E8t 28. 02. 2008 v 10:33 +0200: And while I have your attention, I have a related question. I have produced a bunch of ISO9660 Level 3 / UDF hybrid media with mkisofs, and when I mount the UDF part of them, the mount point (root directory of media) have 0x000 permissions. Yes that's right, d--------- in ls -l. That makes the whole volume inaccessible for everyone except root. Is this something you can mend in our UDF driver, or should I go dig inside mkisofs guts? Windows handle these media without any visible problems. --=20 Pav Lucistnik How will you recognize experienced hacker from beginner? Beginner thinks that kilobyte have 1000 bytes. Experienced hacker thinks one kilometer have 1024 meters. --=-yd8j2hHcryoNidCpOQUb Content-Type: application/pgp-signature; name=signature.asc Content-Description: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEABECAAYFAkfGhg8ACgkQntdYP8FOsoLwyACgrP5zeovnsFlldAbsoaMpLJ0u NlQAoMuA43/HAfJaFUJ3ht9vaCQamj+B =pU05 -----END PGP SIGNATURE----- --=-yd8j2hHcryoNidCpOQUb-- From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 11:12:24 2008 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 878DC1065671 for ; Thu, 28 Feb 2008 11:12:24 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: from mail.irbisnet.ru (mail.irbisnet.ru [IPv6:2001:470:1f09:aa:203:baff:fe18:f4c1]) by mx1.freebsd.org (Postfix) with ESMTP id 00DDC8FC13 for ; Thu, 28 Feb 2008 11:12:23 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: from mail.irbisnet.ru (yuri@mail.irbisnet.ru [IPv6:::1]) by mail.irbisnet.ru (8.14.2/8.14.2) with ESMTP id m1SBCMex099973; Thu, 28 Feb 2008 14:12:22 +0300 (MSK) (envelope-from yuri.pankov@gmail.com) Received: (from yuri@localhost) by mail.irbisnet.ru (8.14.2/8.14.2/Submit) id m1SBCMnO099972; Thu, 28 Feb 2008 14:12:22 +0300 (MSK) (envelope-from yuri.pankov@gmail.com) X-Authentication-Warning: mail.irbisnet.ru: yuri set sender to yuri.pankov@gmail.com using -f Date: Thu, 28 Feb 2008 14:12:22 +0300 From: Yuri Pankov To: freebsd-hackers@freebsd.org Message-ID: <20080228111222.GE92245@mail.irbisnet.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) Subject: pfind() in ithread handler X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 11:12:24 -0000 Hi, I'm trying to understand the cause of following panic. panic: Trying sleep, but thread marked as sleeping prohibited cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x17d sleepq_add() at sleepq_add+0x2e1 _sx_slock_hard() at _sx_slock_hard+0x15d _sx_slock() at _sx_slock+0xc1 pfind() at pfind+0x24 saa_intr() at saa_intr+0x313 ithread_loop() at ithread_loop+0xda fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffac3c0d30, rbp = 0 --- Can someone enlighten me on what is causing the panic and is it ok to use pfind() in interrupt handler (I have very limited understanding of kernel internals)? Code in question (taken from saa driver http://freebsd.ricin.com/ports/distfiles/kbtv-1.92.tbz) can be found at http://www.pastebin.ca/921830 TIA, Yuri From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 12:32:33 2008 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 676021065679; Thu, 28 Feb 2008 12:32:33 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from falcon.cybervisiontech.com (falcon.cybervisiontech.com [217.20.163.9]) by mx1.freebsd.org (Postfix) with ESMTP id 0A2838FC23; Thu, 28 Feb 2008 12:32:32 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (localhost [127.0.0.1]) by falcon.cybervisiontech.com (Postfix) with ESMTP id 1595074400A; Thu, 28 Feb 2008 14:32:32 +0200 (EET) X-Virus-Scanned: Debian amavisd-new at falcon.cybervisiontech.com Received: from falcon.cybervisiontech.com ([127.0.0.1]) by localhost (falcon.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sol3PhN4C6H5; Thu, 28 Feb 2008 14:32:31 +0200 (EET) Received: from [10.2.1.87] (gateway.cybervisiontech.com.ua [88.81.251.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by falcon.cybervisiontech.com (Postfix) with ESMTP id 4794E43DFCA; Thu, 28 Feb 2008 14:32:31 +0200 (EET) Message-ID: <47C6A9DE.1010708@icyb.net.ua> Date: Thu, 28 Feb 2008 14:32:30 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.9 (X11/20080123) MIME-Version: 1.0 To: pav@FreeBSD.org References: <200612221824.kBMIOhfM049471@freefall.freebsd.org> <47A2EDB0.8000801@icyb.net.ua> <47A2F404.7010208@icyb.net.ua> <47A735A4.3060506@icyb.net.ua> <47A75B47.2040604@elischer.org> <1202155663.62432.0.camel@ikaros.oook.cz> <47A8754C.5010607@icyb.net.ua> <1202235368.68281.12.camel@ikaros.oook.cz> <1204053786.1799.0.camel@ikaros.oook.cz> <47C671CF.9020101@icyb.net.ua> <1204192787.54462.1.camel@pav.hide.vol.cz> In-Reply-To: <1204192787.54462.1.camel@pav.hide.vol.cz> Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit Cc: Bruce Evans , freebsd-hackers@FreeBSD.org, scottl@FreeBSD.org, freebsd-fs@FreeBSD.org, Julian Elischer , Remko Lodder Subject: Re: fs/udf: vm pages "overlap" while reading large dir [patch] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 12:32:33 -0000 on 28/02/2008 11:59 Pav Lucistnik said the following: > Andriy Gapon pí¹e v èt 28. 02. 2008 v 10:33 +0200: > > And while I have your attention, I have a related question. > > I have produced a bunch of ISO9660 Level 3 / UDF hybrid media with > mkisofs, and when I mount the UDF part of them, the mount point (root > directory of media) have 0x000 permissions. Yes that's right, d--------- > in ls -l. That makes the whole volume inaccessible for everyone except > root. > > Is this something you can mend in our UDF driver, or should I go dig > inside mkisofs guts? Windows handle these media without any visible > problems. > I think this ought to be something in mkisofs, last I checked our code was fully conforming to the specs in this regard. And obviously it works with windoz, because it simply ignores the permissions :-) We might consider adding a fixup for such broken media (if my assessment is correct), but I'd rather prefer that it is fixed at the source. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 13:17:48 2008 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 525481065683 for ; Thu, 28 Feb 2008 13:17:48 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.freebsd.org (Postfix) with ESMTP id 7CB6A8FC2A for ; Thu, 28 Feb 2008 13:17:47 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so313949uge.37 for ; Thu, 28 Feb 2008 05:17:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=x8AAZH1iwiylNXdfHpXfBQYHWRo88q0t4dVVYsLPv5U=; b=Ouyq91gAJVfc/NUJihNuDY3dUv5Ms6JTJQV4TWReeplNVA37WL7Z2jVZkijklXGnFgR+41LtXLVoos21L2EBuT/YbkADoihPxh5ay6wX635lanYUdJVkjoXQ0xVqKqTgyb3B0QJJ50dGKWpXNa5VO6rzuJxfObfc1ZlyT8VDgPU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oBQx+fRWjVGcXcfCwftH3FCBcQmjYX0o1TfWjyCi/eVF0qkHiqFa7fMiizLcTAJTc6D+1XN3YZy9M1WsWt9wM70gpzOqI2wMLT3JBP71qsAOYNFef/io3Km8RPDi6kx9D01H1NzJRfzlGsm4VF4oF/m/ZrvX25ahVNWyRU9Ids4= Received: by 10.78.151.3 with SMTP id y3mr8160049hud.62.1204204665498; Thu, 28 Feb 2008 05:17:45 -0800 (PST) Received: by 10.78.46.11 with HTTP; Thu, 28 Feb 2008 05:17:45 -0800 (PST) Message-ID: Date: Thu, 28 Feb 2008 16:17:45 +0300 From: pluknet To: "Yuri Pankov" In-Reply-To: <20080228111222.GE92245@mail.irbisnet.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080228111222.GE92245@mail.irbisnet.ru> Cc: freebsd-hackers@freebsd.org Subject: Re: pfind() in ithread handler X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 13:17:48 -0000 On 28/02/2008, Yuri Pankov wrote: > Hi, > > I'm trying to understand the cause of following panic. > > panic: Trying sleep, but thread marked as sleeping prohibited > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > panic() at panic+0x17d > sleepq_add() at sleepq_add+0x2e1 > _sx_slock_hard() at _sx_slock_hard+0x15d > _sx_slock() at _sx_slock+0xc1 > pfind() at pfind+0x24 > saa_intr() at saa_intr+0x313 > ithread_loop() at ithread_loop+0xda > fork_exit() at fork_exit+0x12a > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffffffac3c0d30, rbp = 0 --- > > Can someone enlighten me on what is causing the panic and is it ok to > use pfind() in interrupt handler (I have very limited understanding of > kernel internals)? > > Code in question (taken from saa driver > http://freebsd.ricin.com/ports/distfiles/kbtv-1.92.tbz) can be found at > http://www.pastebin.ca/921830 > > > TIA, > Yuri You cannot sleep in high priority ithread handler, pfind() uses sleepable sx(9) lock. In your case it fail to acquire a shared lock and trying to sleep. Probably you should call pfind() elsewhere. wbr, pluknet From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 13:59:02 2008 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 3CD9F106566B; Thu, 28 Feb 2008 13:59:02 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id E8AA18FC15; Thu, 28 Feb 2008 13:59:01 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 245EB2091; Thu, 28 Feb 2008 14:58:55 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.3/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id C7DDC2088; Thu, 28 Feb 2008 14:58:53 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Simon L. Nielsen" References: <18373.33662.614583.231211@gromit.timing.com> <20080227201203.GA1101@zaphod.nitro.dk> Date: Thu, 28 Feb 2008 14:58:53 +0100 In-Reply-To: <20080227201203.GA1101@zaphod.nitro.dk> (Simon L. Nielsen's message of "Wed\, 27 Feb 2008 12\:12\:04 -0800") Message-ID: <86fxvd18te.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: hackers@freebsd.org, John Hein Subject: Re: cvs tag renaming after repo copy X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 13:59:02 -0000 "Simon L. Nielsen" writes: > John Polstra has made a script (Fixtags) for it which we use for the > FreeBSD repository. I don't think he has any problems with it being > distributed, but as it doesn't have a copyright statement i just want > to ask before I distribute it... Uh... I wrote a replacement for that in 2001 (~des/bin/fixtags.pl). I'm surprised you still use John's version, which is excruciatingly slow, since 1) it's a shell script, 2) it's a *recursive* shell script, 3) it runs rcs twice for every modified tag. My version was under 3-clause BSD; I just switched it to 2-clause. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 14:04:09 2008 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 CF71C1065672; Thu, 28 Feb 2008 14:04:09 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from mx.utwente.nl (unknown [IPv6:2001:610:1908:1000:204:23ff:feba:632a]) by mx1.freebsd.org (Postfix) with ESMTP id 426A68FC12; Thu, 28 Feb 2008 14:04:09 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from lux.student.utwente.nl (lux.student.utwente.nl [130.89.170.81]) by mx.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id m1SE3SQp008813; Thu, 28 Feb 2008 15:03:29 +0100 From: Pieter de Goeje To: freebsd-hackers@freebsd.org Date: Thu, 28 Feb 2008 15:03:28 +0100 User-Agent: KMail/1.9.7 References: <20080228064417.GA98258@dragon.NUXI.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802281503.28615.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact servicedesk@icts.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: Adrian Chadd , hackers@freebsd.org Subject: Re: Modular type GENERIC? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 14:04:10 -0000 On Thursday 28 February 2008, Adrian Chadd wrote: > On 28/02/2008, David O'Brien wrote: > > On Thu, Feb 28, 2008 at 03:26:55PM +0900, Adrian Chadd wrote: > > > Is there some sane-ish way of auto-generating a list of modules given > > > a config file? The "device" statements don't match up with the module > > > name in all bar 4 or 5 places. Is there some chain of files I can > > > munge to match things up? > > > > Not that I know of. :-( > > Crap. I may have to hand-massage something together just for testing then. > > > > Adrian How about: cd /boot/kernel; ls *.ko | sed 's/\.ko/_load="YES"/' I think you still want to remove some modules by hand, for example snd_driver. -- Pieter de Goeje From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 14:04:09 2008 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 CF71C1065672; Thu, 28 Feb 2008 14:04:09 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from mx.utwente.nl (unknown [IPv6:2001:610:1908:1000:204:23ff:feba:632a]) by mx1.freebsd.org (Postfix) with ESMTP id 426A68FC12; Thu, 28 Feb 2008 14:04:09 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from lux.student.utwente.nl (lux.student.utwente.nl [130.89.170.81]) by mx.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id m1SE3SQp008813; Thu, 28 Feb 2008 15:03:29 +0100 From: Pieter de Goeje To: freebsd-hackers@freebsd.org Date: Thu, 28 Feb 2008 15:03:28 +0100 User-Agent: KMail/1.9.7 References: <20080228064417.GA98258@dragon.NUXI.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802281503.28615.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact servicedesk@icts.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: Adrian Chadd , hackers@freebsd.org Subject: Re: Modular type GENERIC? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 14:04:10 -0000 On Thursday 28 February 2008, Adrian Chadd wrote: > On 28/02/2008, David O'Brien wrote: > > On Thu, Feb 28, 2008 at 03:26:55PM +0900, Adrian Chadd wrote: > > > Is there some sane-ish way of auto-generating a list of modules given > > > a config file? The "device" statements don't match up with the module > > > name in all bar 4 or 5 places. Is there some chain of files I can > > > munge to match things up? > > > > Not that I know of. :-( > > Crap. I may have to hand-massage something together just for testing then. > > > > Adrian How about: cd /boot/kernel; ls *.ko | sed 's/\.ko/_load="YES"/' I think you still want to remove some modules by hand, for example snd_driver. -- Pieter de Goeje From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 14:32:34 2008 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 2F0AB106566C for ; Thu, 28 Feb 2008 14:32:34 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id A94DF8FC20 for ; Thu, 28 Feb 2008 14:32:32 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so2580785fgg.35 for ; Thu, 28 Feb 2008 06:32:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=1AbyXVTqjiqcRdElqVLFIj8JZolOodCQ/DGMESuCH+k=; b=HRj1VNZbPhEKzJVlia/jGjMBXhwjwgGpQt4YXACwwrRTwS7JkHOIEeF4SgOR965QE01S/g5qyWZNHpBAa9uwnDtefmoGXnHV5UxIyqmIMk56JB4JgVSNbba+qeXAZTddJE7ZAbd31Iw4XBv4Tr6bwmGrqbJlGwI5ukYaQ78Zk8A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=A4jwRaaYEu4cWfXDwvG6/jP++dQ16+XUMerXxec9c1sPeWwkeyQiZUdP5da5DJb1K61Sf7gBwqbvtpQar8JCtpg/USVOp8zXiP48sLuBwjxH2P39EmxqU8r00IJEz0vPcpYCzem7SRX4/yD84GLZkZN6RuVXZ40WDANHZtS6Ixs= Received: by 10.86.31.18 with SMTP id e18mr8238397fge.35.1204207495489; Thu, 28 Feb 2008 06:04:55 -0800 (PST) Received: by 10.86.30.17 with HTTP; Thu, 28 Feb 2008 06:04:55 -0800 (PST) Message-ID: <3bbf2fe10802280604t4266c0a9uaa0075689ce67632@mail.gmail.com> Date: Thu, 28 Feb 2008 15:04:55 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Yuri Pankov" In-Reply-To: <20080228111222.GE92245@mail.irbisnet.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080228111222.GE92245@mail.irbisnet.ru> X-Google-Sender-Auth: a5721e333098e17f Cc: freebsd-hackers@freebsd.org Subject: Re: pfind() in ithread handler X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 14:32:34 -0000 2008/2/28, Yuri Pankov : > Hi, > > I'm trying to understand the cause of following panic. > > panic: Trying sleep, but thread marked as sleeping prohibited > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > panic() at panic+0x17d > sleepq_add() at sleepq_add+0x2e1 > _sx_slock_hard() at _sx_slock_hard+0x15d > _sx_slock() at _sx_slock+0xc1 > pfind() at pfind+0x24 > saa_intr() at saa_intr+0x313 > ithread_loop() at ithread_loop+0xda > fork_exit() at fork_exit+0x12a > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffffffac3c0d30, rbp = 0 --- > > Can someone enlighten me on what is causing the panic and is it ok to > use pfind() in interrupt handler (I have very limited understanding of > kernel internals)? > > Code in question (taken from saa driver > http://freebsd.ricin.com/ports/distfiles/kbtv-1.92.tbz) can be found at > http://www.pastebin.ca/921830 ithreads cannot perform unbound sleeps and pfind() needs to access to allproc_lock which is a sx lock and *performs* an unbound sleep, so there is a mismatch. Btw, it sounds like allproc_lock and other similar locks are just using an sx lock for *legacy*, they should be probabilly converted to rwlock. It also imposes little problems in the TTY layer, for example, where I saw you need to use a unbounded sleeping primitive because of processes locks acquisitions. A nice janitor task would be to convert these sx locks into rw and see what happens. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 15:59:55 2008 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 D82B61065670; Thu, 28 Feb 2008 15:59:55 +0000 (UTC) (envelope-from jhein@timing.com) Received: from Daffy.timing.com (w.timing.com [206.168.13.218]) by mx1.freebsd.org (Postfix) with ESMTP id 910A58FC22; Thu, 28 Feb 2008 15:59:55 +0000 (UTC) (envelope-from jhein@timing.com) Received: from gromit.timing.com (gromit.timing.com [206.168.13.209]) by Daffy.timing.com (8.13.1/8.13.1) with ESMTP id m1SFxpfZ090101; Thu, 28 Feb 2008 08:59:51 -0700 (MST) (envelope-from jhein@timing.com) Received: from gromit.timing.com (localhost [127.0.0.1]) by gromit.timing.com (8.14.2/8.14.2) with ESMTP id m1SFxoTX084676; Thu, 28 Feb 2008 08:59:50 -0700 (MST) (envelope-from jhein@gromit.timing.com) Received: (from jhein@localhost) by gromit.timing.com (8.14.2/8.14.2/Submit) id m1SFxnWE084670; Thu, 28 Feb 2008 08:59:49 -0700 (MST) (envelope-from jhein) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <18374.55925.429800.520009@gromit.timing.com> Date: Thu, 28 Feb 2008 08:59:49 -0700 From: John E Hein To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= In-Reply-To: <86fxvd18te.fsf@ds4.des.no> References: <18373.33662.614583.231211@gromit.timing.com> <20080227201203.GA1101@zaphod.nitro.dk> <86fxvd18te.fsf@ds4.des.no> X-Mailer: VM 7.19 under Emacs 22.1.1 X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on Daffy.timing.com X-Virus-Status: Clean Cc: hackers@FreeBSD.org, "Simon L. Nielsen" Subject: Re: cvs tag renaming after repo copy X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 15:59:55 -0000 Dag-Erling Sm=F8rgrav wrote at 14:58 +0100 on Feb 28, 2008: > "Simon L. Nielsen" writes: > > John Polstra has made a script (Fixtags) for it which we use for the= > > FreeBSD repository. I don't think he has any problems with it being= > > distributed, but as it doesn't have a copyright statement i just wan= t > > to ask before I distribute it... > = > Uh... I wrote a replacement for that in 2001 (~des/bin/fixtags.pl). > I'm surprised you still use John's version, which is excruciatingly > slow, since 1) it's a shell script, 2) it's a *recursive* shell script= , > 3) it runs rcs twice for every modified tag. > = > My version was under 3-clause BSD; I just switched it to 2-clause. Sounds nice. But for those of us aren't in the club and don't have a freefall account (or wherever home dirs reside these days) ... ? From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 19:36:34 2008 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 859AF106569C; Thu, 28 Feb 2008 19:36:34 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 381728FC16; Thu, 28 Feb 2008 19:36:34 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 00A81207F; Thu, 28 Feb 2008 20:36:30 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.3/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 0421D207E; Thu, 28 Feb 2008 20:36:29 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: John E Hein References: <18373.33662.614583.231211@gromit.timing.com> <20080227201203.GA1101@zaphod.nitro.dk> <86fxvd18te.fsf@ds4.des.no> <18374.55925.429800.520009@gromit.timing.com> Date: Thu, 28 Feb 2008 20:36:29 +0100 In-Reply-To: <18374.55925.429800.520009@gromit.timing.com> (John E. Hein's message of "Thu\, 28 Feb 2008 08\:59\:49 -0700") Message-ID: <86r6ew27r6.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: hackers@FreeBSD.org, "Simon L. Nielsen" Subject: Re: cvs tag renaming after repo copy X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 19:36:34 -0000 John E Hein writes: > Dag-Erling Sm=C3=B8rgrav wrote at 14:58 +0100 on Feb 28, 2008: > > "Simon L. Nielsen" writes: > > > John Polstra has made a script (Fixtags) for it which we use for the > > > FreeBSD repository. I don't think he has any problems with it being > > > distributed, but as it doesn't have a copyright statement i just want > > > to ask before I distribute it... > >=20 > > Uh... I wrote a replacement for that in 2001 (~des/bin/fixtags.pl). > > I'm surprised you still use John's version, which is excruciatingly > > slow, since 1) it's a shell script, 2) it's a *recursive* shell script, > > 3) it runs rcs twice for every modified tag. > >=20 > > My version was under 3-clause BSD; I just switched it to 2-clause. > > Sounds nice. But for those of us aren't in the club and don't have a > freefall account (or wherever home dirs reside these days) ... ? http://people.freebsd.org/~des/software/fixtags Unfortunately, Apache is set up in such a manner that I can't set the correct mime type (if I name it fixtags.pl, it thinks it's a CGI script and gives you a 403...) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 19:03:16 2008 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 6364E1065680; Thu, 28 Feb 2008 19:03:16 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 017388FC22; Thu, 28 Feb 2008 19:03:15 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m1SJ3402041093; Thu, 28 Feb 2008 12:03:05 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <47C70568.7070208@samsco.org> Date: Thu, 28 Feb 2008 12:03:04 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.11) Gecko/20071128 SeaMonkey/1.1.7 MIME-Version: 1.0 To: pav@FreeBSD.org References: <200612221824.kBMIOhfM049471@freefall.freebsd.org> <47A2EDB0.8000801@icyb.net.ua> <47A2F404.7010208@icyb.net.ua> <47A735A4.3060506@icyb.net.ua> <47A75B47.2040604@elischer.org> <1202155663.62432.0.camel@ikaros.oook.cz> <47A8754C.5010607@icyb.net.ua> <1202235368.68281.12.camel@ikaros.oook.cz> <1204053786.1799.0.camel@ikaros.oook.cz> <47C671CF.9020101@icyb.net.ua> <1204192787.54462.1.camel@pav.hide.vol.cz> In-Reply-To: <1204192787.54462.1.camel@pav.hide.vol.cz> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.4 required=5.4 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org X-Mailman-Approved-At: Thu, 28 Feb 2008 20:20:03 +0000 Cc: Bruce Evans , freebsd-hackers@FreeBSD.org, scottl@FreeBSD.org, Andriy Gapon , freebsd-fs@FreeBSD.org, Julian Elischer , Remko Lodder Subject: Re: fs/udf: vm pages "overlap" while reading large dir [patch] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 19:03:16 -0000 Pav Lucistnik wrote: > Andriy Gapon píše v Ät 28. 02. 2008 v 10:33 +0200: > > And while I have your attention, I have a related question. > > I have produced a bunch of ISO9660 Level 3 / UDF hybrid media with > mkisofs, and when I mount the UDF part of them, the mount point (root > directory of media) have 0x000 permissions. Yes that's right, d--------- > in ls -l. That makes the whole volume inaccessible for everyone except > root. > > Is this something you can mend in our UDF driver, or should I go dig > inside mkisofs guts? Windows handle these media without any visible > problems. > I wonder if Windows even observes the permissions bits. You'd have to special-case the UDF driver code in FreeBSD, which certainly possible but not terribly attractive. I'd be interested to see what exactly mkiso is doing. Maybe it's putting permissions into extended attributes and assuming the filesystem driver will read those instead. Scott From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 20:20:22 2008 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 0819E106566B; Thu, 28 Feb 2008 20:20:22 +0000 (UTC) (envelope-from jhein@timing.com) Received: from Daffy.timing.com (smtp.timing.com [206.168.13.218]) by mx1.freebsd.org (Postfix) with ESMTP id 7FB578FC15; Thu, 28 Feb 2008 20:20:21 +0000 (UTC) (envelope-from jhein@timing.com) Received: from gromit.timing.com (gromit.timing.com [206.168.13.209]) by Daffy.timing.com (8.13.1/8.13.1) with ESMTP id m1SKKINp032254; Thu, 28 Feb 2008 13:20:18 -0700 (MST) (envelope-from jhein@timing.com) Received: from gromit.timing.com (localhost [127.0.0.1]) by gromit.timing.com (8.14.2/8.14.2) with ESMTP id m1SKKEc0091376; Thu, 28 Feb 2008 13:20:14 -0700 (MST) (envelope-from jhein@gromit.timing.com) Received: (from jhein@localhost) by gromit.timing.com (8.14.2/8.14.2/Submit) id m1SKKEbZ091372; Thu, 28 Feb 2008 13:20:14 -0700 (MST) (envelope-from jhein) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <18375.6014.235239.783773@gromit.timing.com> Date: Thu, 28 Feb 2008 13:20:14 -0700 From: John E Hein To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= In-Reply-To: <86r6ew27r6.fsf@ds4.des.no> References: <18373.33662.614583.231211@gromit.timing.com> <20080227201203.GA1101@zaphod.nitro.dk> <86fxvd18te.fsf@ds4.des.no> <18374.55925.429800.520009@gromit.timing.com> <86r6ew27r6.fsf@ds4.des.no> X-Mailer: VM 7.19 under Emacs 22.1.1 X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on Daffy.timing.com X-Virus-Status: Clean Cc: hackers@FreeBSD.org, "Simon L. Nielsen" Subject: Re: cvs tag renaming after repo copy X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 20:20:22 -0000 Dag-Erling Sm=F8rgrav wrote at 20:36 +0100 on Feb 28, 2008: > http://people.freebsd.org/~des/software/fixtags > = > Unfortunately, Apache is set up in such a manner that I can't set the > correct mime type (if I name it fixtags.pl, it thinks it's a CGI scrip= t > and gives you a 403...) Thanks. I did something similar (not using cvs ops, but rather directly munging the ,v file) with awk, but I had issues with binary files. I also didn't have any fancy exclude/include feature (nice!) or try to guess which tags are vendor tags (it looks like you're just trying to match a '.' - why does that make it a vendor tag?). Minor issue... syntax error at /tmp/jhein/fixtags line 68, near "&&" syntax error at /tmp/jhein/fixtags line 68, near "@exclude)" syntax error at /tmp/jhein/fixtags line 69, near "@include)" syntax error at /tmp/jhein/fixtags line 74, near "} else" --- fixtags.orig 2008-02-28 13:11:33.000000000 -0700 +++ fixtags 2008-02-28 13:10:16.000000000 -0700 @@ -64,7 +64,7 @@ } elsif ($phase =3D=3D 2) { if (m/^\t([^:]+):([0-9.]+);?\s*$/) { $tag =3D $1; - if ($tag !~ m/\./ && # skip vendor tags + if ($tag !~ m/\./ # skip vendor tags && (!@exclude || !grep({ $_ eq $tag } @exclude)) && (!@include || grep({ $_ eq $tag } @include))) { print(" $tag -> old_$tag\n") From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 19:04:07 2008 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 6F1CE1065680 for ; Thu, 28 Feb 2008 19:04:07 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 10A668FC20 for ; Thu, 28 Feb 2008 19:04:06 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m1SJ42cS041119; Thu, 28 Feb 2008 12:04:02 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <47C705A2.9030502@samsco.org> Date: Thu, 28 Feb 2008 12:04:02 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.11) Gecko/20071128 SeaMonkey/1.1.7 MIME-Version: 1.0 To: Andriy Gapon References: <200612221824.kBMIOhfM049471@freefall.freebsd.org> <47A2EDB0.8000801@icyb.net.ua> <47A2F404.7010208@icyb.net.ua> <47A735A4.3060506@icyb.net.ua> <47A75B47.2040604@elischer.org> <1202155663.62432.0.camel@ikaros.oook.cz> <47A8754C.5010607@icyb.net.ua> <1202235368.68281.12.camel@ikaros.oook.cz> <1204053786.1799.0.camel@ikaros.oook.cz> <47C671CF.9020101@icyb.net.ua> In-Reply-To: <47C671CF.9020101@icyb.net.ua> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.4 required=5.4 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org X-Mailman-Approved-At: Thu, 28 Feb 2008 20:21:19 +0000 Cc: Bruce Evans , freebsd-hackers@FreeBSD.org, freebsd-fs@FreeBSD.org, pav@FreeBSD.org, Julian Elischer , Remko Lodder Subject: Re: fs/udf: vm pages "overlap" while reading large dir [patch] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 19:04:08 -0000 Andriy Gapon wrote: > on 26/02/2008 21:23 Pav Lucistnik said the following: >> Pav Lucistnik píše v út 05. 02. 2008 v 19:16 +0100: >>> Andriy Gapon píše v út 05. 02. 2008 v 16:40 +0200: >>> >>>>> Yay, and can you fix the sequential read performance while you're at it? >>>>> Kthx! >>>> this was almost trivial :-) >>>> See the attached patch, first hunk is just for consistency. >>>> The code was borrowed from cd9660, only field/variable names are adjusted. >> Just tested it with my shiny new Bluray drive, and it work wonders. >> Finally seamless playback of media files off UDF carrying media. >> >> So, how does it look WRT committing it? >> > > Pav, > > thank you for the feedback/reminder. > In my personal option the latest patch posted and described at the > following like is a very good candidate for commit: > http://docs.FreeBSD.org/cgi/mid.cgi?47AA43B9.1040608 > It might have a couple of style related issues, but it should improve > things a bit even if some larger VM/VFS/GEOM issues remain. > > And by the way, a patch from the following PR would be a good > "side-dish" for the above patch: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/78987 > I think it is simple and obvious enough. > I will commit both of these to CVS today. Thanks again. Scott From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 20:30:28 2008 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 71246106567E for ; Thu, 28 Feb 2008 20:30:28 +0000 (UTC) (envelope-from tim1timau@yahoo.com) Received: from web50308.mail.re2.yahoo.com (web50308.mail.re2.yahoo.com [206.190.38.62]) by mx1.freebsd.org (Postfix) with SMTP id E67AA8FC26 for ; Thu, 28 Feb 2008 20:30:27 +0000 (UTC) (envelope-from tim1timau@yahoo.com) Received: (qmail 78189 invoked by uid 60001); 28 Feb 2008 20:30:27 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=sPrw3ZFsrDhvYquFLqOh0li6LQzrJAyf/fKZehLRZZoouDK/acTuD0w0WNfkQoC1QIkoYrIgoQo8ornTwwYqVCgDVEQxq4RtftfpyniBxsE2LsiUOJscA3fxkCkkrH3+oueiJsFBAq0lxqpXA/TYL8GFuvfDxIDolY8WDmj2lj4=; X-YMail-OSG: eFwWv_sVM1mKnPkxYlfg6_QzHkaPa0vlhwKkweYpM4i1mVw1uSZh_7wfkUekvFaGCfSxK.vchei8I3kl9qG7yOsYnD0sTcNBZas5uqOSm4B5QzwDehEAsaKGkyvQJ399kJpJRktEbbZQphk- Received: from [210.215.149.194] by web50308.mail.re2.yahoo.com via HTTP; Thu, 28 Feb 2008 12:30:26 PST Date: Thu, 28 Feb 2008 12:30:26 -0800 (PST) From: Tim Clewlow To: freebsd-current@freebsd.org, hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <114098.31819.qm@web50308.mail.re2.yahoo.com> Cc: Subject: PXE on 7.0 problem and solution X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 20:30:28 -0000 Hi there, Installing 7.0 via PXE has a slight problem that is easily worked around. The file /boot/mfsroot.gz on the installation media needs to be unzipped to make PXE boot via tftp/nfs work. Otherwise the loader ultimately complains that it cant find the device to boot from. For example, if you have the installation media living at /usr/pxe/nfs/ on the PXE server, then do: gzip -d /usr/pxe/nfs/boot/mfsroot.gz After doing this it now loads the kernel and starts the installation procedure as expected. Someone more knowledgeable than me might want to let whoever needs to know about this. Apart from that, it looks great, the work is appreciated, thanks for the new release :-) Cheers, Tim. We are BSD ... resistance is futile. http://www.freebsd.org/ - http://www.openbsd.org/ - http://www.netbsd.org/ ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 21:00:27 2008 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 0AE7A1065677; Thu, 28 Feb 2008 21:00:27 +0000 (UTC) (envelope-from jhein@timing.com) Received: from Daffy.timing.com (mx2.timing.com [206.168.13.218]) by mx1.freebsd.org (Postfix) with ESMTP id 026148FC35; Thu, 28 Feb 2008 21:00:25 +0000 (UTC) (envelope-from jhein@timing.com) Received: from gromit.timing.com (gromit.timing.com [206.168.13.209]) by Daffy.timing.com (8.13.1/8.13.1) with ESMTP id m1SL0NrO038315; Thu, 28 Feb 2008 14:00:23 -0700 (MST) (envelope-from jhein@timing.com) Received: from gromit.timing.com (localhost [127.0.0.1]) by gromit.timing.com (8.14.2/8.14.2) with ESMTP id m1SL0L6e092860; Thu, 28 Feb 2008 14:00:21 -0700 (MST) (envelope-from jhein@gromit.timing.com) Received: (from jhein@localhost) by gromit.timing.com (8.14.2/8.14.2/Submit) id m1SL0LoA092857; Thu, 28 Feb 2008 14:00:21 -0700 (MST) (envelope-from jhein) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18375.8421.35599.358681@gromit.timing.com> Date: Thu, 28 Feb 2008 14:00:21 -0700 From: John E Hein To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= In-Reply-To: <18375.6014.235239.783773@gromit.timing.com> References: <18373.33662.614583.231211@gromit.timing.com> <20080227201203.GA1101@zaphod.nitro.dk> <86fxvd18te.fsf@ds4.des.no> <18374.55925.429800.520009@gromit.timing.com> <86r6ew27r6.fsf@ds4.des.no> <18375.6014.235239.783773@gromit.timing.com> X-Mailer: VM 7.19 under Emacs 22.1.1 X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on Daffy.timing.com X-Virus-Status: Clean Cc: hackers@FreeBSD.org, "Simon L. Nielsen" Subject: Re: cvs tag renaming after repo copy X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 21:00:29 -0000 John E Hein wrote at 13:20 -0700 on Feb 28, 2008: > Thanks. I did something similar (not using cvs ops, but rather > directly munging the ,v file) with awk, but I had issues with binary > files. Regarding binary files, I tried my awk again, but this time with gawk, and it had no problems. I wonder if I stumbled onto a one-true-awk issue (or if my expectations were wrong). From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 20:52:13 2008 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 2C5141065684; Thu, 28 Feb 2008 20:52:13 +0000 (UTC) (envelope-from erik@cederstrand.dk) Received: from mx2.itu.dk (unknown [130.226.142.29]) by mx1.freebsd.org (Postfix) with ESMTP id D99E08FC2F; Thu, 28 Feb 2008 20:52:12 +0000 (UTC) (envelope-from erik@cederstrand.dk) Received: from wimac.littlebit.dk (unknown [85.233.238.191]) by mx2.itu.dk (Postfix) with ESMTP id 8A6A7F48072; Thu, 28 Feb 2008 21:52:11 +0100 (CET) Message-ID: <47C71EC1.3010500@cederstrand.dk> Date: Thu, 28 Feb 2008 21:51:13 +0100 From: Erik Cederstrand User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Tim Clewlow References: <114098.31819.qm@web50308.mail.re2.yahoo.com> In-Reply-To: <114098.31819.qm@web50308.mail.re2.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 28 Feb 2008 21:07:41 +0000 Cc: hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: PXE on 7.0 problem and solution X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 20:52:13 -0000 Tim Clewlow wrote: > Hi there, > > Installing 7.0 via PXE has a slight problem that is easily worked around. The > file /boot/mfsroot.gz on the installation media needs to be unzipped to make > PXE boot via tftp/nfs work. Otherwise the loader ultimately complains that it > cant find the device to boot from. For example, if you have the installation > media living at /usr/pxe/nfs/ on the PXE server, then do: > > gzip -d /usr/pxe/nfs/boot/mfsroot.gz > > After doing this it now loads the kernel and starts the installation procedure > as expected. Someone more knowledgeable than me might want to let whoever needs > to know about this. > > Apart from that, it looks great, the work is appreciated, thanks for the new > release :-) I've had problems with other files fetched over NFS in the past. In theory (at least that's what a tcpdump says), it should be possible to provide all files gzipped, and even split the files in smaller chunks. Files are tried in this order: boot/loader.rc.split boot/loader.rc.gz.split boot/loader.rc.gz boot/loader.rc However, I only got the plain files to work reliably. Erik From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 21:42:32 2008 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 2D8271065673 for ; Thu, 28 Feb 2008 21:42:32 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.3]) by mx1.freebsd.org (Postfix) with ESMTP id 017EC8FC20 for ; Thu, 28 Feb 2008 21:42:31 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: (qmail 25253 invoked from network); 28 Feb 2008 21:42:31 -0000 Received: from april.chuckr.org (chuckr@[66.92.151.30]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 28 Feb 2008 21:42:31 -0000 Message-ID: <47C7294E.9000804@chuckr.org> Date: Thu, 28 Feb 2008 16:36:14 -0500 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: FreeBSD-Hackers X-Enigmail-Version: 0.95.5 OpenPGP: id=F3DCA0E9; url=http://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: problem with ldconfig X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 21:42:32 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I had a problem with my raid array, and during a fix, I noticed that a thing I'd gotten very used to during my time running Linux was a really bad thing for FreeBSD (the usage of a /boot partition for booting only, to store the kernel, but nothing else). Well, after I had reloaded my raid, and fixed the /boot to be one nice big parition, I have a several very weird things that have cropped up. First one, I'd kept a 100G IDE disk hanging around just in case I hadn't installed the raid right, so I could use it for backup, and this saved me, but now, it no longer boots right. I used to either hit F1 (to boot the 100G IDE, called ad1, ad0 being a cdrom), or I would hit F5 then F1, to boot from the raid, called da0. Well, now, no matter what Function key I hit, it boots from ad1 regardless, and the only way I can boot the raid is the use the #6 option of the beastie menu (to catch the ld cli) and set currdev to disk2s1a, unload, load, then boot. This works fine, but howcome I can't just get it to boot without all this intervention? I have already tried reloading the boot manager into both ad1s1 and da0s1, no change. Well, the other thing that's come up, I can't get my nvidia driver to work along with xorg. It used to show it's arrival both in kldstat, AND also because, in /dev, a file named nvidiactl would show up. This has stopped happening. I had been using the old version 100.14.19, and when I checked the nvidia website, it seems a couple of newer versions had appeared, so I downloaded and built version 169.12. Don't ask me why the crazy version numbering, I looked around for something like a changelog, but had no luck. Anyhow, updating to the newer version wasn't too hard, but didn't show any change. Consulting the /var/log/Xorg.0.log file, even though kldstat says that nvidia.ko is loaded, it never shows a /dev/nvidiactl, and the log file says clearly that it never finds the Nvidia kernel module. Using it with Vesa lets me limp, so I do that, but howcome? OK, I'm not giving my ldconfig problem to you folks, its quite likely its a FreeBSD-current problem, so let those folks handle that one. Boy, I feel like the little boy who cried wolf! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHxylOz62J6PPcoOkRAudcAJ9ex65oZUoh+0gf/7WcpNi6KhwsxwCgje63 m4GwVJZrkoU3McfHK1NAArk= =wLpy -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 22:14:59 2008 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 79F4C1065677 for ; Thu, 28 Feb 2008 22:14:59 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell.rawbw.com (shell.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5D9A48FC2F for ; Thu, 28 Feb 2008 22:14:59 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from eagle.syrec.org (ip224.carlyle.sfo.ygnition.net [24.219.144.224]) (authenticated bits=0) by shell.rawbw.com (8.13.6/8.13.6) with ESMTP id m1SMExhp086251; Thu, 28 Feb 2008 14:14:59 -0800 (PST) Message-ID: <47C73262.1020805@rawbw.com> Date: Thu, 28 Feb 2008 14:14:58 -0800 From: Yuri User-Agent: Thunderbird 2.0.0.9 (X11/20080122) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "J.R. Oldroyd" Subject: umass: should the device specific information be moved from C code to the text file? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yuri@rawbw.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 22:14:59 -0000 Currently all devices supported by umass driver are listed in * sys/dev/usb/usbdevs - which has vendor table (vendor-id/name) - and product table (ref-to-vendor-id/product-id/name) and * sys/dev/usb/umass.c - which has some per-device flags. The problem with this way is that some people might want to disable umass for particular devices. For example some people prefer to use gphoto2 with usb-cameras and gphoto2 needs the device to be ugen. I suggest device specific information should be moved from sys/dev/usb/usbdevs and sys/dev/usb/umass.c to some text file (ex. /etc/umass-devices) which would be read by umass driver when it's loaded. This way users will be able to easily remove/add entries without the need to recompile the module. Yuri From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 23:16:21 2008 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 1B0A21065672 for ; Thu, 28 Feb 2008 23:16:21 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from mx.nitro.dk (zarniwoop.nitro.dk [83.92.207.38]) by mx1.freebsd.org (Postfix) with ESMTP id C08C38FC1C for ; Thu, 28 Feb 2008 23:16:20 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from zaphod.nitro.dk (unknown [192.168.3.39]) by mx.nitro.dk (Postfix) with ESMTP id 898AF1E8C09; Thu, 28 Feb 2008 23:16:07 +0000 (UTC) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 58B9B11492; Thu, 28 Feb 2008 15:16:18 -0800 (PST) Date: Thu, 28 Feb 2008 15:16:18 -0800 From: "Simon L. Nielsen" To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Message-ID: <20080228231616.GA1104@zaphod.nitro.dk> References: <18373.33662.614583.231211@gromit.timing.com> <20080227201203.GA1101@zaphod.nitro.dk> <86fxvd18te.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <86fxvd18te.fsf@ds4.des.no> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: hackers@freebsd.org, John Hein Subject: Re: cvs tag renaming after repo copy X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 23:16:21 -0000 On 2008.02.28 14:58:53 +0100, Dag-Erling Smørgrav wrote: > "Simon L. Nielsen" writes: > > John Polstra has made a script (Fixtags) for it which we use for the > > FreeBSD repository. I don't think he has any problems with it being > > distributed, but as it doesn't have a copyright statement i just want > > to ask before I distribute it... > > Uh... I wrote a replacement for that in 2001 (~des/bin/fixtags.pl). > I'm surprised you still use John's version, which is excruciatingly > slow, since 1) it's a shell script, 2) it's a *recursive* shell script, > 3) it runs rcs twice for every modified tag. If it ain't borken :-). Speed is rarely an issue since the CVS master server is fast, and most of the time only a few files are copied. For other intersted parties I got OK from John Polstra to put his script online with std. BSD license so it can now be found at http://people.freebsd.org/~simon/scripts/Fixtags . In case anyone is interested I put the script I use for repo-copies at FreeBSD.org online as http://people.freebsd.org/~simon/scripts/cvs_repo_copy . The script probably need to be adjusted to local config and use at your own risk etc - but it hasn't done anything bad for me yet :-). -- Simon L. Nielsen From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 28 23:55:11 2008 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 3E404106566B; Thu, 28 Feb 2008 23:55:11 +0000 (UTC) (envelope-from skip@menantico.com) Received: from vms048pub.verizon.net (vms048pub.verizon.net [206.46.252.48]) by mx1.freebsd.org (Postfix) with ESMTP id 132C58FC19; Thu, 28 Feb 2008 23:55:11 +0000 (UTC) (envelope-from skip@menantico.com) Received: from mx.menantico.com ([71.168.194.131]) by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JWZ002KI3RFF583@vms048.mailsrvcs.net>; Thu, 28 Feb 2008 17:54:51 -0600 (CST) Date: Thu, 28 Feb 2008 18:57:27 -0500 From: Skip Ford In-reply-to: <20080228231616.GA1104@zaphod.nitro.dk> To: "Simon L. Nielsen" Message-id: <20080228235727.GA967@menantico.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline References: <18373.33662.614583.231211@gromit.timing.com> <20080227201203.GA1101@zaphod.nitro.dk> <86fxvd18te.fsf@ds4.des.no> <20080228231616.GA1104@zaphod.nitro.dk> User-Agent: Mutt/1.4.2.3i Cc: Dag-Erling =?unknown-8bit?Q?Sm=F8rgrav?= , hackers@freebsd.org, John Hein Subject: Re: cvs tag renaming after repo copy X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2008 23:55:11 -0000 Simon L. Nielsen wrote: > For other intersted parties I got OK from John Polstra to put his > script online with std. BSD license so it can now be found at > http://people.freebsd.org/~simon/scripts/Fixtags . > > In case anyone is interested I put the script I use for repo-copies at > FreeBSD.org online as > http://people.freebsd.org/~simon/scripts/cvs_repo_copy . The script > probably need to be adjusted to local config and use at your own risk > etc - but it hasn't done anything bad for me yet :-). Thanks for these. Any reason they couldn't be added to the repository in src/tools/tools/repocopy/ or similar so those who are interested don't have to worry about having a stale version in the future? -- Skip From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 29 02:43:35 2008 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 F20001065670 for ; Fri, 29 Feb 2008 02:43:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.190]) by mx1.freebsd.org (Postfix) with ESMTP id 775AA8FC23 for ; Fri, 29 Feb 2008 02:43:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by ti-out-0910.google.com with SMTP id j2so3442014tid.3 for ; Thu, 28 Feb 2008 18:43:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=s3yATTW9flVByhCIH3SDo9/1F7hJbvH0v7G6bgnwQn0=; b=EDPfiptzz6maTBPLnU8piX27PIMKD3CtF7BtDYYrVIq97duFhYBEOcH29lOwsCl/JS+yXtE0escT/2BWYTnbveYDnD/K3G+gxDkHNdvXep0uwNHx7kpRQVVKua+lICzC80ud13FBTOfAeMRhX3HhYFrdpysilFmUIK3jFs+kAOw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=E8nvek6TAmCYC0UHXJcgpmOZrvZuH3HsrJ3rpNRVSo33gEHp+5TbnYC+e2Nfw8vACA2Lq3k5Z6hjDWt5nmrpaBG0KHvujnukfxcs7/exeKqIOFYTY0fKQqSY9qOmMgHiBusQYISqgcWVh87Mmw0murxPW2T9Q7dUY6liMrzmMfo= Received: by 10.151.156.2 with SMTP id i2mr3109381ybo.121.1204253010817; Thu, 28 Feb 2008 18:43:30 -0800 (PST) Received: by 10.150.144.2 with HTTP; Thu, 28 Feb 2008 18:43:30 -0800 (PST) Message-ID: Date: Fri, 29 Feb 2008 11:43:30 +0900 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: "Pieter de Goeje" In-Reply-To: <200802281503.28615.pieter@degoeje.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080228064417.GA98258@dragon.NUXI.org> <200802281503.28615.pieter@degoeje.nl> X-Google-Sender-Auth: ae8b86594ac80ac5 Cc: freebsd-hackers@freebsd.org, hackers@freebsd.org Subject: Re: Modular type GENERIC? 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, 29 Feb 2008 02:43:36 -0000 On 28/02/2008, Pieter de Goeje wrote: > > cd /boot/kernel; ls *.ko | sed 's/\.ko/_load="YES"/' > > I think you still want to remove some modules by hand, for example snd_driver. Yes, but I'm reasonably sure GENERIC doesn't include -everything-. In any case, simply doing that confused loader quite badly. It crashed after all the modules had been loaded. Adrian -- Adrian Chadd - adrian@freebsd.org From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 29 02:43:36 2008 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 787E31065671 for ; Fri, 29 Feb 2008 02:43:36 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.191]) by mx1.freebsd.org (Postfix) with ESMTP id 795E28FC24 for ; Fri, 29 Feb 2008 02:43:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by ti-out-0910.google.com with SMTP id j2so3442015tid.3 for ; Thu, 28 Feb 2008 18:43:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=s3yATTW9flVByhCIH3SDo9/1F7hJbvH0v7G6bgnwQn0=; b=EDPfiptzz6maTBPLnU8piX27PIMKD3CtF7BtDYYrVIq97duFhYBEOcH29lOwsCl/JS+yXtE0escT/2BWYTnbveYDnD/K3G+gxDkHNdvXep0uwNHx7kpRQVVKua+lICzC80ud13FBTOfAeMRhX3HhYFrdpysilFmUIK3jFs+kAOw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=E8nvek6TAmCYC0UHXJcgpmOZrvZuH3HsrJ3rpNRVSo33gEHp+5TbnYC+e2Nfw8vACA2Lq3k5Z6hjDWt5nmrpaBG0KHvujnukfxcs7/exeKqIOFYTY0fKQqSY9qOmMgHiBusQYISqgcWVh87Mmw0murxPW2T9Q7dUY6liMrzmMfo= Received: by 10.151.156.2 with SMTP id i2mr3109381ybo.121.1204253010817; Thu, 28 Feb 2008 18:43:30 -0800 (PST) Received: by 10.150.144.2 with HTTP; Thu, 28 Feb 2008 18:43:30 -0800 (PST) Message-ID: Date: Fri, 29 Feb 2008 11:43:30 +0900 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: "Pieter de Goeje" In-Reply-To: <200802281503.28615.pieter@degoeje.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080228064417.GA98258@dragon.NUXI.org> <200802281503.28615.pieter@degoeje.nl> X-Google-Sender-Auth: ae8b86594ac80ac5 Cc: freebsd-hackers@freebsd.org, hackers@freebsd.org Subject: Re: Modular type GENERIC? 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, 29 Feb 2008 02:43:36 -0000 On 28/02/2008, Pieter de Goeje wrote: > > cd /boot/kernel; ls *.ko | sed 's/\.ko/_load="YES"/' > > I think you still want to remove some modules by hand, for example snd_driver. Yes, but I'm reasonably sure GENERIC doesn't include -everything-. In any case, simply doing that confused loader quite badly. It crashed after all the modules had been loaded. Adrian -- Adrian Chadd - adrian@freebsd.org From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 29 03:30:04 2008 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 542AC106566C; Fri, 29 Feb 2008 03:30:04 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 106718FC15; Fri, 29 Feb 2008 03:30:03 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 688E62087; Fri, 29 Feb 2008 04:30:00 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.3/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 58ACC207E; Fri, 29 Feb 2008 04:29:59 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: John E Hein References: <18373.33662.614583.231211@gromit.timing.com> <20080227201203.GA1101@zaphod.nitro.dk> <86fxvd18te.fsf@ds4.des.no> <18374.55925.429800.520009@gromit.timing.com> <86r6ew27r6.fsf@ds4.des.no> <18375.6014.235239.783773@gromit.timing.com> Date: Fri, 29 Feb 2008 04:29:58 +0100 In-Reply-To: <18375.6014.235239.783773@gromit.timing.com> (John E. Hein's message of "Thu\, 28 Feb 2008 13\:20\:14 -0700") Message-ID: <86ir081lu1.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: hackers@FreeBSD.org, "Simon L. Nielsen" Subject: Re: cvs tag renaming after repo copy 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, 29 Feb 2008 03:30:04 -0000 John E Hein writes: > - if ($tag !~ m/\./ && # skip vendor tags > + if ($tag !~ m/\./ # skip vendor tags > && (!@exclude || !grep({ $_ eq $tag } @exclude)) > && (!@include || grep({ $_ eq $tag } @include))) { Oops... Maybe that's why people were still using John's version :) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 29 07:42:15 2008 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 ED36D1065672 for ; Fri, 29 Feb 2008 07:42:15 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail05.syd.optusnet.com.au (mail05.syd.optusnet.com.au [211.29.132.186]) by mx1.freebsd.org (Postfix) with ESMTP id 06D508FC29 for ; Fri, 29 Feb 2008 07:42:14 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail05.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m1T7gAv0013153 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Feb 2008 18:42:12 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.1) with ESMTP id m1T7gA94062721; Fri, 29 Feb 2008 18:42:10 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m1T7g8wg062720; Fri, 29 Feb 2008 18:42:08 +1100 (EST) (envelope-from peter) Date: Fri, 29 Feb 2008 18:42:08 +1100 From: Peter Jeremy To: Yuri Message-ID: <20080229074208.GT83599@server.vk2pj.dyndns.org> References: <47C73262.1020805@rawbw.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PkEWctFf+8E2rcii" Content-Disposition: inline In-Reply-To: <47C73262.1020805@rawbw.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-hackers@freebsd.org, "J.R. Oldroyd" Subject: Re: umass: should the device specific information be moved from C code to the text file? 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, 29 Feb 2008 07:42:16 -0000 --PkEWctFf+8E2rcii Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 28, 2008 at 02:14:58PM -0800, Yuri wrote: >Currently all devices supported by umass driver are listed in >* sys/dev/usb/usbdevs > - which has vendor table (vendor-id/name) > - and product table (ref-to-vendor-id/product-id/name) >and >* sys/dev/usb/umass.c > - which has some per-device flags. And (for completeness): * src/sys/cam/scsi/scsi_da.c - contains device quirks. >I suggest device specific information should be moved from=20 >sys/dev/usb/usbdevs and sys/dev/usb/umass.c >to some text file (ex. /etc/umass-devices) which would be read by umass=20 >driver when it's loaded. This sounds like a nice idea - it's also a nuisance having to recompile the kernel just to support a weird new USB device you've acquired. Unfortunately, accessing the filesystem from within the kernel is not that easy. One problem with your suggestion of accessing the file when umass is "loaded" is that if imass is compiled into the kernel, it will go through the probe/attach phase before there's a root filesystem - which makes reading files somewhat difficult. What might be more useful is for the USB system to interrogate a file (or similar) when a USB device is inserted to allow the user to control which usb driver gains control of the device - as well as the camera example you use, this would also be useful with multi-function printer/scanner/... devices. Again, accessing a file is not trivial but may be practical. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --PkEWctFf+8E2rcii Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHx7dQ/opHv/APuIcRAh6JAJ9Vxzg86CJGZBJI91dkQGEGHVwdmACfRTh5 fVf09ImGND3yd9JdfeYZuqA= =zRn2 -----END PGP SIGNATURE----- --PkEWctFf+8E2rcii-- From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 29 11:45:03 2008 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 EA4CF106566C for ; Fri, 29 Feb 2008 11:45:03 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 9D26F8FC25 for ; Fri, 29 Feb 2008 11:45:03 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1JV3fi-0000Gp-4k for freebsd-hackers@freebsd.org; Fri, 29 Feb 2008 11:45:02 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 29 Feb 2008 11:45:02 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 29 Feb 2008 11:45:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Fri, 29 Feb 2008 12:44:44 +0100 Lines: 37 Message-ID: References: <47C73262.1020805@rawbw.com> <20080229074208.GT83599@server.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE56D3D117332E9A06561754D" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.6 (X11/20071022) In-Reply-To: <20080229074208.GT83599@server.vk2pj.dyndns.org> X-Enigmail-Version: 0.95.0 Sender: news Subject: Re: umass: should the device specific information be moved from C code to the text file? 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, 29 Feb 2008 11:45:04 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE56D3D117332E9A06561754D Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Peter Jeremy wrote: > This sounds like a nice idea - it's also a nuisance having to recompile= > the kernel just to support a weird new USB device you've acquired. You can probably keep USB support as a module if you need to recompile it often :) On the original topic: please don't do that. Recent ultra-modern Linux systems have started offloading such critical kernel functionalities to the userland, making it almost impossible to deal with when things go bad (e.g. in single user mode). See also trouble ZFS has in single user mode because it relies on files in the file system and a userland rc.d script (hostid). --------------enigE56D3D117332E9A06561754D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHx/AsldnAQVacBcgRAitIAKCxtGLGhqBdSRIf2738+8tAqiIwVQCfRZkZ 68o50mNmtW3TeqJX+V1nClA= =el9e -----END PGP SIGNATURE----- --------------enigE56D3D117332E9A06561754D-- From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 29 13:41:03 2008 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 EE4311065670 for ; Fri, 29 Feb 2008 13:41:03 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: from ag-out-0708.google.com (ag-out-0708.google.com [72.14.246.251]) by mx1.freebsd.org (Postfix) with ESMTP id A5D7A8FC1C for ; Fri, 29 Feb 2008 13:41:03 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: by ag-out-0708.google.com with SMTP id 5so10258905agb.7 for ; Fri, 29 Feb 2008 05:41:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Gy5cB5xDpgVxteYULue1NrGvTPdS5iRWPED9RSN7K9I=; b=mcxo0PTD/IJIKiToJtllfIiio7AIq2BAvvIUIDUSps0N8PmvQReJV9DtWiiI/GH0F/BaSFVanmNM6nlRG45x1r9a4+FqdO4BzY0a8l67fJ7NsPBMexgEBsLEqun4g6hh83pWgf7ElkOTWh1saCbxFtzI+M4AUG/7orueh0SyQkk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YOp6FxdiX5Fj55k3w8kYQ8wNqE6vfGPayDc/G5YEu7byEKQltu766nXCxGF5kvIJORgKC5Va78J5+BPLhZlWQcRFw/gdvWBasP0kY+/UX+0iqBIdU1DcTnJsHfgZTCLPrzu2GOGl9Eze/Oun8YW4LVbfqwfRkw1I5dxuRpnWasY= Received: by 10.100.137.11 with SMTP id k11mr19274983and.73.1204291540155; Fri, 29 Feb 2008 05:25:40 -0800 (PST) Received: by 10.100.248.5 with HTTP; Fri, 29 Feb 2008 05:25:40 -0800 (PST) Message-ID: <47d0403c0802290525l11dab3f7gac5601f5dd01bde3@mail.gmail.com> Date: Fri, 29 Feb 2008 08:25:40 -0500 From: "Ben Kaduk" To: "Chuck Robey" In-Reply-To: <47C7294E.9000804@chuckr.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47C7294E.9000804@chuckr.org> Cc: FreeBSD-Hackers Subject: Re: problem with ldconfig 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, 29 Feb 2008 13:41:04 -0000 Hi Chuck, On 2/28/08, Chuck Robey wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > [snip RAID/loader interaction] > Well, the other thing that's come up, I can't get my nvidia driver to work > along with xorg. It used to show it's arrival both in kldstat, AND also > because, in /dev, a file named nvidiactl would show up. This has stopped > happening. I had been using the old version 100.14.19, and when I checked > the nvidia website, it seems a couple of newer versions had appeared, so I > downloaded and built version 169.12. Don't ask me why the crazy version > numbering, I looked around for something like a changelog, but had no luck. > Anyhow, updating to the newer version wasn't too hard, but didn't show any > change. Consulting the /var/log/Xorg.0.log file, even though kldstat says > that nvidia.ko is loaded, it never shows a /dev/nvidiactl, and the log file > says clearly that it never finds the Nvidia kernel module. Using it with > Vesa lets me limp, so I do that, but howcome? The nvidia kernel module now needs to be loaded at boot-time; it won't supercede the default vga support if loaded later. cat nvidia_load="YES"" >> /boot/loader.conf -Ben Kaduk > > OK, I'm not giving my ldconfig problem to you folks, its quite likely its a > FreeBSD-current problem, so let those folks handle that one. > > Boy, I feel like the little boy who cried wolf! > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.4 (FreeBSD) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHxylOz62J6PPcoOkRAudcAJ9ex65oZUoh+0gf/7WcpNi6KhwsxwCgje63 > m4GwVJZrkoU3McfHK1NAArk= > =wLpy > -----END PGP SIGNATURE----- > _______________________________________________ > 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 Fri Feb 29 14:17:07 2008 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 63B21106566B for ; Fri, 29 Feb 2008 14:17:07 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id C12B28FC1A for ; Fri, 29 Feb 2008 14:17:06 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id m1TEH4AI062983; Fri, 29 Feb 2008 15:17:04 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id m1TEGqlb062308 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Feb 2008 15:16:52 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id m1TEGpMs011921; Fri, 29 Feb 2008 15:16:51 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id m1TEGp9g011920; Fri, 29 Feb 2008 15:16:51 +0100 (CET) (envelope-from ticso) Date: Fri, 29 Feb 2008 15:16:51 +0100 From: Bernd Walter To: Ivan Voras Message-ID: <20080229141650.GM7101@cicely12.cicely.de> References: <47C73262.1020805@rawbw.com> <20080229074208.GT83599@server.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, BAYES_00=-2.599 autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on cicely12.cicely.de Cc: freebsd-hackers@freebsd.org Subject: Re: umass: should the device specific information be moved from C code to the text file? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Feb 2008 14:17:07 -0000 On Fri, Feb 29, 2008 at 12:44:44PM +0100, Ivan Voras wrote: > Peter Jeremy wrote: > > > This sounds like a nice idea - it's also a nuisance having to recompile > > the kernel just to support a weird new USB device you've acquired. > > You can probably keep USB support as a module if you need to recompile > it often :) > > On the original topic: please don't do that. Recent ultra-modern Linux > systems have started offloading such critical kernel functionalities to > the userland, making it almost impossible to deal with when things go > bad (e.g. in single user mode). See also trouble ZFS has in single user > mode because it relies on files in the file system and a userland rc.d > script (hostid). It doesn't work anyway, since umass doesn't attach to device/vendor-ID. umass(4) is a interface class driver and attaches to each device containg a umass class interface independend of vendor/device-ID. There may be some exeptions for devices, which fail to supply the correct decriptor tables however, but the majority of supported devices are unknown to the driver. If you need ugen and umass, then fix ugen to attach even if another driver(s) already controls the device or some interfaces. This may be tricky, since ugen allows things that may break the expectations of other drivers, but we should have a solution for this problem anyway. Maybe we can live with this risk, while ugen is enhanced to do dafety catches - we have much more dangerous risks with USB right now, such as detaching mounted umass media. Not sure if HPS stack already handles the ugen vs. other driver problematic. AFAIK under Linux the generic userland interface allows claiming devices/interfaces from userland. It could be good idea for us as well and it would be good for libusb support as well. -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 29 15:35:44 2008 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 AF3C21065671; Fri, 29 Feb 2008 15:35:44 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9E56A8FC1D; Fri, 29 Feb 2008 15:35:44 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 93FF41CC038; Fri, 29 Feb 2008 07:35:44 -0800 (PST) Date: Fri, 29 Feb 2008 07:35:44 -0800 From: Jeremy Chadwick To: Tim Clewlow Message-ID: <20080229153544.GA94345@eos.sc1.parodius.com> References: <114098.31819.qm@web50308.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <114098.31819.qm@web50308.mail.re2.yahoo.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: PXE on 7.0 problem and solution 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, 29 Feb 2008 15:35:44 -0000 On Thu, Feb 28, 2008 at 12:30:26PM -0800, Tim Clewlow wrote: > Hi there, > > Installing 7.0 via PXE has a slight problem that is easily worked around. The > file /boot/mfsroot.gz on the installation media needs to be unzipped to make > PXE boot via tftp/nfs work. Otherwise the loader ultimately complains that it > cant find the device to boot from. For example, if you have the installation > media living at /usr/pxe/nfs/ on the PXE server, then do: I documented this in my "how to get FreeBSD to install via PXE and serial console" document: http://jdc.parodius.com/freebsd/pxeboot_serial_install.html I opened a PR at the time of this discovery as well: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/120127 -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 29 17:11:02 2008 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 56F65106566B for ; Fri, 29 Feb 2008 17:11:02 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: from mail7.sea5.speakeasy.net (mail7.sea5.speakeasy.net [69.17.117.9]) by mx1.freebsd.org (Postfix) with ESMTP id 334EF8FC1E for ; Fri, 29 Feb 2008 17:11:02 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: (qmail 25862 invoked from network); 29 Feb 2008 17:11:01 -0000 Received: from april.chuckr.org (chuckr@[66.92.151.30]) (envelope-sender ) by mail7.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 29 Feb 2008 17:11:01 -0000 Message-ID: <47C83B2A.3050808@chuckr.org> Date: Fri, 29 Feb 2008 12:04:42 -0500 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: Ben Kaduk References: <47C7294E.9000804@chuckr.org> <47d0403c0802290525l11dab3f7gac5601f5dd01bde3@mail.gmail.com> In-Reply-To: <47d0403c0802290525l11dab3f7gac5601f5dd01bde3@mail.gmail.com> X-Enigmail-Version: 0.95.5 OpenPGP: id=F3DCA0E9; url=http://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD-Hackers Subject: Re: problem with ldconfig; nvidia loading fixed 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, 29 Feb 2008 17:11:02 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ben Kaduk wrote: > Hi Chuck, > > On 2/28/08, Chuck Robey wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> > [snip RAID/loader interaction] >> Well, the other thing that's come up, I can't get my nvidia driver to work >> along with xorg. It used to show it's arrival both in kldstat, AND also >> because, in /dev, a file named nvidiactl would show up. This has stopped >> happening. I had been using the old version 100.14.19, and when I checked >> the nvidia website, it seems a couple of newer versions had appeared, so I >> downloaded and built version 169.12. Don't ask me why the crazy version >> numbering, I looked around for something like a changelog, but had no luck. >> Anyhow, updating to the newer version wasn't too hard, but didn't show any >> change. Consulting the /var/log/Xorg.0.log file, even though kldstat says >> that nvidia.ko is loaded, it never shows a /dev/nvidiactl, and the log file >> says clearly that it never finds the Nvidia kernel module. Using it with >> Vesa lets me limp, so I do that, but howcome? > > The nvidia kernel module now needs to be loaded at boot-time; > it won't supercede the default vga support if loaded later. > > cat nvidia_load="YES"" >> /boot/loader.conf I'd never heard that about it needing absolutely to load at boot time, but you were absolutely right, I have it working now. It also made my loading problem (I don't know if I complained on hackers about that or not). No, in looking back to by send-cache, I don't think I did, Immediately after I finally got all my raid array proboems fixed, I found really that there was only 1 remaining: booting my raid. I have definitely the boot-manager loaded onto ad1 (my 100G emergency eide disk) and da0 (my raid). I normally would strike f1 to load the eide for emergencies, and f5, then f1, to load from the raid. Well, now, no matter what I press, I load from the eide disk. If I intercept the boot at the beastie menu, and press 6 to get into the loader, I find currdev is _always_ set to disk1s1a (the eide, ad1). If I want to boot the raid, I need to manually do a "set currdev=disk2s1a" then unload, then load the kernel AND manually load all the modules, because loder.conf isn't getting read either. Once I went thru all that, the nvidia driver worked fine, as you predicted, any notion why the loading has gone screwey? I can add one thing: When I initially installed the system, I was just coming back from using Linux for some years, and I forgot that while Linux is in love with using a small /boot partition to store the kernels and the bootloader, FreeBSD isn't. I had stuck the /boot only onto da1s1d, with my root onto da0s1a. I was loading my root via /etc/fstab, I thought, but in fact, I had an old version of a just-useable boot onto myu da1s1a, and that was what was actually booting. When I got rid of the /boot mount line in fstab, and expected things to work ok, this odd refusal to correctly boot from disk2s1a began. Any idea here? Booting is a real drag now. thanks! > > > -Ben Kaduk > > >> OK, I'm not giving my ldconfig problem to you folks, its quite likely its a >> FreeBSD-current problem, so let those folks handle that one. >> >> Boy, I feel like the little boy who cried wolf! >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.4 (FreeBSD) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org >> >> iD8DBQFHxylOz62J6PPcoOkRAudcAJ9ex65oZUoh+0gf/7WcpNi6KhwsxwCgje63 >> m4GwVJZrkoU3McfHK1NAArk= >> =wLpy >> -----END PGP SIGNATURE----- >> _______________________________________________ >> 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" >> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHyDsqz62J6PPcoOkRAiHkAJ4irPHgJa8Cdx/0Q/cAK6sfzntLhQCgm/W+ 82dYth4MSJgdPHLuCSo4b70= =wKsU -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 29 18:01:59 2008 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 9DF1B106566B for ; Fri, 29 Feb 2008 18:01:59 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: from mail5.sea5.speakeasy.net (mail5.sea5.speakeasy.net [69.17.117.7]) by mx1.freebsd.org (Postfix) with ESMTP id 43C488FC1E for ; Fri, 29 Feb 2008 18:01:59 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: (qmail 24408 invoked from network); 29 Feb 2008 18:01:58 -0000 Received: from april.chuckr.org (chuckr@[66.92.151.30]) (envelope-sender ) by mail5.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 29 Feb 2008 18:01:58 -0000 Message-ID: <47C8471A.5080007@chuckr.org> Date: Fri, 29 Feb 2008 12:55:38 -0500 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: Ben Kaduk References: <47C7294E.9000804@chuckr.org> <47d0403c0802290525l11dab3f7gac5601f5dd01bde3@mail.gmail.com> <47C83B2A.3050808@chuckr.org> In-Reply-To: <47C83B2A.3050808@chuckr.org> X-Enigmail-Version: 0.95.5 OpenPGP: id=F3DCA0E9; url=http://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD-Hackers Subject: Re: problem with loading 1/2 fixed 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, 29 Feb 2008 18:01:59 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chuck Robey wrote: > Ben Kaduk wrote: > >> cat nvidia_load="YES"" >> /boot/loader.conf > > I'd never heard that about it needing absolutely to load at boot time, but > you were absolutely right, I have it working now. > > It also made my loading problem (I don't know if I complained on hackers > about that or not). No, in looking back to by send-cache, I don't think I > did, Immediately after I finally got all my raid array proboems fixed, I > found really that there was only 1 remaining: booting my raid. > > I have definitely the boot-manager loaded onto ad1 (my 100G emergency eide > disk) and da0 (my raid). I normally would strike f1 to load the eide for > emergencies, and f5, then f1, to load from the raid. Well, now, no matter > what I press, I load from the eide disk. If I intercept the boot at the > beastie menu, and press 6 to get into the loader, I find currdev is > _always_ set to disk1s1a (the eide, ad1). If I want to boot the raid, I > need to manually do a "set currdev=disk2s1a" then unload, then load the > kernel AND manually load all the modules, because loder.conf isn't getting > read either. > > Once I went thru all that, the nvidia driver worked fine, as you predicted, > any notion why the loading has gone screwey? I can add one thing: When I > initially installed the system, I was just coming back from using Linux for > some years, and I forgot that while Linux is in love with using a small > /boot partition to store the kernels and the bootloader, FreeBSD isn't. I > had stuck the /boot only onto da1s1d, with my root onto da0s1a. I was > loading my root via /etc/fstab, I thought, but in fact, I had an old > version of a just-useable boot onto myu da1s1a, and that was what was > actually booting. When I got rid of the /boot mount line in fstab, and > expected things to work ok, this odd refusal to correctly boot from > disk2s1a began. Well, found 50% of the problems, my device,hints had a line mis-setting currdev, once I fixed that, it now boots from the right disk. One booting problem remaining: it won't read my /boot/loader.conf. simple file, 2 whole lines: TCSH-april:chuckr:~:#101-12:50>cat /boot/loader.conf linux_load="YES" nvidia_load="YES" that's all, but when (in the loader, preboot) I execute the read-conf command to force it to read the file, it comes back with a syntax error, saying exactly this: " ^ That's it, the single (double) quote, and a caret in column 1 beneath that. Noting else. Could it maybe be something to do with what zi have in rc.conf? I have a line in rc.conf, linux_enable="YES", that's ok along with the loader line, right? > > Any idea here? Booting is a real drag now. > > thanks! > > >> -Ben Kaduk > > >>> OK, I'm not giving my ldconfig problem to you folks, its quite likely its a >>> FreeBSD-current problem, so let those folks handle that one. >>> >>> Boy, I feel like the little boy who cried wolf! >>> _______________________________________________ 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" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHyEcaz62J6PPcoOkRAmSCAKCPS+g/rJ7A4fjfErjLcoxOzq/IawCcDcat B7Y4mGGyvrtv7sP6Cn097QI= =6eLu -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 29 18:34:56 2008 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 3DDA21065672 for ; Fri, 29 Feb 2008 18:34:56 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: from mail3.sea5.speakeasy.net (mail3.sea5.speakeasy.net [69.17.117.5]) by mx1.freebsd.org (Postfix) with ESMTP id 1A64B8FC3A for ; Fri, 29 Feb 2008 18:34:56 +0000 (UTC) (envelope-from chuckr@chuckr.org) Received: (qmail 14756 invoked from network); 29 Feb 2008 18:34:54 -0000 Received: from april.chuckr.org (chuckr@[66.92.151.30]) (envelope-sender ) by mail3.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 29 Feb 2008 18:34:53 -0000 Message-ID: <47C84ED2.500@chuckr.org> Date: Fri, 29 Feb 2008 13:28:34 -0500 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: Ben Kaduk References: <47C7294E.9000804@chuckr.org> <47d0403c0802290525l11dab3f7gac5601f5dd01bde3@mail.gmail.com> <47C83B2A.3050808@chuckr.org> <47C8471A.5080007@chuckr.org> In-Reply-To: <47C8471A.5080007@chuckr.org> X-Enigmail-Version: 0.95.5 OpenPGP: id=F3DCA0E9; url=http://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD-Hackers Subject: Re: problem with loading all fixed now 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, 29 Feb 2008 18:34:56 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chuck Robey wrote: > Chuck Robey wrote: >> Ben Kaduk wrote: > >>> cat nvidia_load="YES"" >> /boot/loader.conf >> I'd never heard that about it needing absolutely to load at boot time, but >> you were absolutely right, I have it working now. > >> It also made my loading problem (I don't know if I complained on hackers >> about that or not). No, in looking back to by send-cache, I don't think I >> did, Immediately after I finally got all my raid array proboems fixed, I >> found really that there was only 1 remaining: booting my raid. > >> I have definitely the boot-manager loaded onto ad1 (my 100G emergency eide >> disk) and da0 (my raid). I normally would strike f1 to load the eide for >> emergencies, and f5, then f1, to load from the raid. Well, now, no matter >> what I press, I load from the eide disk. If I intercept the boot at the >> beastie menu, and press 6 to get into the loader, I find currdev is >> _always_ set to disk1s1a (the eide, ad1). If I want to boot the raid, I >> need to manually do a "set currdev=disk2s1a" then unload, then load the >> kernel AND manually load all the modules, because loder.conf isn't getting >> read either. > >> Once I went thru all that, the nvidia driver worked fine, as you predicted, >> any notion why the loading has gone screwey? I can add one thing: When I >> initially installed the system, I was just coming back from using Linux for >> some years, and I forgot that while Linux is in love with using a small >> /boot partition to store the kernels and the bootloader, FreeBSD isn't. I >> had stuck the /boot only onto da1s1d, with my root onto da0s1a. I was >> loading my root via /etc/fstab, I thought, but in fact, I had an old >> version of a just-useable boot onto myu da1s1a, and that was what was >> actually booting. When I got rid of the /boot mount line in fstab, and >> expected things to work ok, this odd refusal to correctly boot from >> disk2s1a began. > > Well, found 50% of the problems, my device,hints had a line mis-setting > currdev, once I fixed that, it now boots from the right disk. One booting > problem remaining: it won't read my /boot/loader.conf. simple file, 2 > whole lines: I found that my linker.hints was loading one module, so (thinks I) why not try to load them all there, and it workedd like a charm. My loader.conf isn't working now, but it really doesn't bother me all that much. I have only a single problem remaining, it's a audio one, so I am off to the multimedia list, and I thank you for letting me lean on you whilst I stewed in my problems. They all seem to come to me in big waves, never one at a time, and it's not even a thing of one problme having multiple symptoms, they each had t heir own fix. God is watching me and having a nice chuckle over this, I guess. > > TCSH-april:chuckr:~:#101-12:50>cat /boot/loader.conf > linux_load="YES" > nvidia_load="YES" > > that's all, but when (in the loader, preboot) I execute the read-conf > command to force it to read the file, it comes back with a syntax error, > saying exactly this: > > " > ^ > > That's it, the single (double) quote, and a caret in column 1 beneath that. > Noting else. Could it maybe be something to do with what zi have in > rc.conf? I have a line in rc.conf, linux_enable="YES", that's ok along > with the loader line, right? > >> Any idea here? Booting is a real drag now. > >> thanks! > > >>> -Ben Kaduk > >>>> OK, I'm not giving my ldconfig problem to you folks, its quite likely its a >>>> FreeBSD-current problem, so let those folks handle that one. >>>> >>>> Boy, I feel like the little boy who cried wolf! >>>> > > _______________________________________________ > 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" > _______________________________________________ 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" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHyE7Rz62J6PPcoOkRAtjmAKCJPKipDoRaoW5lKch/DEecBnDN7QCfbD8I pN43DuNTPuoxu58VankO0mQ= =7VXA -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 29 21:45:25 2008 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 525DC1065675 for ; Fri, 29 Feb 2008 21:45:25 +0000 (UTC) (envelope-from fchang@cs.ubc.ca) Received: from smtp.cs.ubc.ca (smtp.cs.ubc.ca [142.103.6.52]) by mx1.freebsd.org (Postfix) with ESMTP id 209E78FC25 for ; Fri, 29 Feb 2008 21:45:24 +0000 (UTC) (envelope-from fchang@cs.ubc.ca) Received: from cascade.cs.ubc.ca (cascade.cs.ubc.ca [142.103.7.7]) by smtp.cs.ubc.ca (8.13.7/8.13.6) with ESMTP id m1TLTNNI023712 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Feb 2008 13:29:24 -0800 Date: Fri, 29 Feb 2008 13:29:23 -0800 (PST) From: fchang@cs.ubc.ca To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Fri, 29 Feb 2008 22:22:43 +0000 Subject: Updating vmware3 (and missing "avail_end" from /usr/include/machine/pmap.h) 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, 29 Feb 2008 21:45:25 -0000 Hi all: I'm trying to get vmware3 working on FreeBSD RELEASE 7.0 for i386 I've resolved every compilation problem except one: the driver.c in vmware3 requires the "avail_end" variable in 6.2's /usr/include/machine/pmap.h but is missing from 7.0's /usr/include/machine/pmap.h The vmware3 code goes like this: r = malloc(sizeof *r, M_DEVBUF, M_WAITOK); if (r == NULL) return ENOMEM; if (avail_end > ISA_DMA_BOUNCE_THRESHOLD) high = trunc_page(ISA_DMA_BOUNCE_THRESHOLD); else high = trunc_page(avail_end); It turns out "avail_end" was removed from /usr/include/machine/pmap.h by revision 1.125, whose commit message reads: The global variable avail_end is redundant and only used once. Eliminate it. Make avail_start static to the pmap on amd64. (It no longer exists on other architectures.) So it appears that we can still get the value represented by the old avail_end variable, but I don't know anything about the kernel and I don't understand that comment. Could some kind soul help me decipher that so I can try to get vmware3 compilable again? Thank you! From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 1 12:17:06 2008 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 817DE1065670 for ; Sat, 1 Mar 2008 12:17:06 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (vlk.vlakno.cz [62.168.28.247]) by mx1.freebsd.org (Postfix) with ESMTP id 335188FC27 for ; Sat, 1 Mar 2008 12:17:05 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id F2367673415; Sat, 1 Mar 2008 13:17:03 +0100 (CET) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (vlk.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rWDfg44qNyJF; Sat, 1 Mar 2008 13:17:02 +0100 (CET) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 9D736666E71; Sat, 1 Mar 2008 13:17:02 +0100 (CET) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.13.8/8.13.8/Submit) id m21CH1wc073540; Sat, 1 Mar 2008 13:17:01 +0100 (CET) (envelope-from rdivacky) Date: Sat, 1 Mar 2008 13:17:01 +0100 From: Roman Divacky To: fchang@cs.ubc.ca Message-ID: <20080301121701.GA73096@freebsd.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-hackers@freebsd.org Subject: Re: Updating vmware3 (and missing "avail_end" from /usr/include/machine/pmap.h) 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, 01 Mar 2008 12:17:06 -0000 On Fri, Feb 29, 2008 at 01:29:23PM -0800, fchang@cs.ubc.ca wrote: > Hi all: > > I'm trying to get vmware3 working on FreeBSD RELEASE 7.0 for i386 > I've resolved every compilation problem except one: > the driver.c in vmware3 requires the "avail_end" variable > in 6.2's /usr/include/machine/pmap.h > but is missing from 7.0's /usr/include/machine/pmap.h > > The vmware3 code goes like this: > > r = malloc(sizeof *r, M_DEVBUF, M_WAITOK); > if (r == NULL) return ENOMEM; > if (avail_end > ISA_DMA_BOUNCE_THRESHOLD) > high = trunc_page(ISA_DMA_BOUNCE_THRESHOLD); > else > high = trunc_page(avail_end); > > It turns out "avail_end" was removed from /usr/include/machine/pmap.h > by revision 1.125, whose commit message reads: > > The global variable avail_end is redundant and only used once. > Eliminate it. Make avail_start static to the pmap on amd64. > (It no longer exists on other architectures.) > > So it appears that we can still get the value represented by > the old avail_end variable, but I don't know anything about the kernel > and I don't understand that comment. Could some kind soul help me > decipher that so I can try to get vmware3 compilable again? I think you can use "ptoa(Maxmem) - round_page(MSGBUF_SIZE)", the ptoa(Maxmem) being the thing written during dmesg as: real memory = 1039007744 (990 MB), I think its exported as hw.realmem sysctl hope that helps.. let us know about your VMWare experiences! roman From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 1 12:20:44 2008 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 4E44C1065670 for ; Sat, 1 Mar 2008 12:20:44 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (vlk.vlakno.cz [62.168.28.247]) by mx1.freebsd.org (Postfix) with ESMTP id 013EB8FC1C for ; Sat, 1 Mar 2008 12:20:43 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 29BF6673415; Sat, 1 Mar 2008 13:20:43 +0100 (CET) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (vlk.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gJYgKXOsmUXO; Sat, 1 Mar 2008 13:20:42 +0100 (CET) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id F3D60666E71; Sat, 1 Mar 2008 13:20:41 +0100 (CET) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.13.8/8.13.8/Submit) id m21CKfac073707; Sat, 1 Mar 2008 13:20:41 +0100 (CET) (envelope-from rdivacky) Date: Sat, 1 Mar 2008 13:20:41 +0100 From: Roman Divacky To: fchang@cs.ubc.ca Message-ID: <20080301122041.GB73096@freebsd.org> References: <20080301121701.GA73096@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080301121701.GA73096@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-hackers@freebsd.org Subject: Re: Updating vmware3 (and missing "avail_end" from /usr/include/machine/pmap.h) 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, 01 Mar 2008 12:20:44 -0000 On Sat, Mar 01, 2008 at 01:17:01PM +0100, Roman Divacky wrote: > On Fri, Feb 29, 2008 at 01:29:23PM -0800, fchang@cs.ubc.ca wrote: > > Hi all: > > > > I'm trying to get vmware3 working on FreeBSD RELEASE 7.0 for i386 > > I've resolved every compilation problem except one: > > the driver.c in vmware3 requires the "avail_end" variable > > in 6.2's /usr/include/machine/pmap.h > > but is missing from 7.0's /usr/include/machine/pmap.h > > > > The vmware3 code goes like this: > > > > r = malloc(sizeof *r, M_DEVBUF, M_WAITOK); > > if (r == NULL) return ENOMEM; > > if (avail_end > ISA_DMA_BOUNCE_THRESHOLD) > > high = trunc_page(ISA_DMA_BOUNCE_THRESHOLD); > > else > > high = trunc_page(avail_end); > > > > It turns out "avail_end" was removed from /usr/include/machine/pmap.h > > by revision 1.125, whose commit message reads: > > > > The global variable avail_end is redundant and only used once. > > Eliminate it. Make avail_start static to the pmap on amd64. > > (It no longer exists on other architectures.) > > > > So it appears that we can still get the value represented by > > the old avail_end variable, but I don't know anything about the kernel > > and I don't understand that comment. Could some kind soul help me > > decipher that so I can try to get vmware3 compilable again? > > I think you can use "ptoa(Maxmem) - round_page(MSGBUF_SIZE)", the ptoa(Maxmem) > being the thing written during dmesg as: > > real memory = 1039007744 (990 MB), I think its exported as hw.realmem sysctl > > hope that helps.. let us know about your VMWare experiences! erm.. what I meant to say what that hw.realmem - round_page(MSGBUF_SIZE) should work From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 1 13:38:25 2008 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 3B68F1065671 for ; Sat, 1 Mar 2008 13:38:25 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from mailout2.zih.tu-dresden.de (mailout2.zih.tu-dresden.de [141.30.67.73]) by mx1.freebsd.org (Postfix) with ESMTP id CA1EA8FC25 for ; Sat, 1 Mar 2008 13:38:24 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from rmc67-31.zih.tu-dresden.de ([141.30.67.31] helo=server-n) by mailout2.zih.tu-dresden.de with esmtp (Exim 4.63) (envelope-from ) id 1JVRus-0003U5-Vh for freebsd-hackers@freebsd.org; Sat, 01 Mar 2008 14:38:23 +0100 Received: from martin (p5B0EEDA0.dip.t-dialin.net [91.14.237.160]) by server-n (Postfix) with ESMTP id ABF88100A091 for ; Sat, 1 Mar 2008 14:38:18 +0100 (CET) Date: Sat, 01 Mar 2008 14:38:17 +0100 To: "freebsd-hackers@freebsd.org" From: "Martin Laabs" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable Message-ID: User-Agent: Opera Mail/9.25 (Linux) X-TUD-Virus-Scanned: mailout2.zih.tu-dresden.de Subject: SIGPIPE propagation 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, 01 Mar 2008 13:38:25 -0000 Hello, as you probably know I want to expand dump in such a way it enableds multivolume dumps also when the output data is written to stdout/a pipe. Now I ran into a serious problem. Dump counts the written bytes to remember where it has to proceede after the volumen change. Now the SIGPIPE signal does not propagate fast enought through the system. Thus dump writes some time after the pipe has got broken data into the pipe while it doesn't exist anymore. This short time it does not receive any error about that. (Until the signal propagates to dump.) I wrote a small test progam to demonstrate this effect (and get clear about it by myself). It just write data to stdout and counts it until the pipe is broken (and the write call will return -1) This is the output of a few successively runs: $ ./a.out |asdf $ asdf: command not found cought broken pipe i: 12 could only wrote -1 bytes. total wrote: 61440 $ ./a.out |asdf $ asdf: command not found cought broken pipe i: 1 could only wrote -1 bytes. total wrote: 5120 $ ./a.out |asdf $ asdf: command not found cought broken pipe i: 12 could only wrote -1 bytes. total wrote: 61440 $ ./a.out |asdf $ asdf: command not found cought broken pipe i: 0 could only wrote -1 bytes. total wrote: 0 Dump encounters the same effect and I don't know how to handle this problem. Do you have any idea how I can manage this? Thank you, Martin L. PS: Here's the code of the small test-program: -----------------:<---------------- #include #include #include #include #include #include #include #include #define MUL 5 char buffer [1024 * MUL]; void sigpipe(int signo __unused) { fprintf(stderr, "cought broken pipe\n"); } main() { int i , w; int wr =3D 0; signal(SIGPIPE, sigpipe); for (i =3D 0; i <=3D 100; i++) { w =3D write(STDOUT_FILENO, buffer, MUL * 1024); if (w > 0) wr +=3D w; if (w !=3D 1024 * MUL) { fprintf(stderr, "i: %d could only wrote %d byte= s. = total break; } } } ------------------------:<-------------------------------- From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 1 15:07:04 2008 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 40AD11065678 for ; Sat, 1 Mar 2008 15:07:04 +0000 (UTC) (envelope-from fchang@cs.ubc.ca) Received: from smtp.cs.ubc.ca (smtp.cs.ubc.ca [142.103.6.52]) by mx1.freebsd.org (Postfix) with ESMTP id 0A02D8FC13 for ; Sat, 1 Mar 2008 15:07:03 +0000 (UTC) (envelope-from fchang@cs.ubc.ca) Received: from cascade.cs.ubc.ca (cascade.cs.ubc.ca [142.103.7.7]) by smtp.cs.ubc.ca (8.13.7/8.13.6) with ESMTP id m21F71K4024541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 1 Mar 2008 07:07:02 -0800 Date: Sat, 1 Mar 2008 07:07:01 -0800 (PST) From: fchang@cs.ubc.ca To: Roman Divacky In-Reply-To: <20080301122041.GB73096@freebsd.org> Message-ID: References: <20080301121701.GA73096@freebsd.org> <20080301122041.GB73096@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Sat, 01 Mar 2008 15:20:14 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Updating vmware3 (and missing "avail_end" from /usr/include/machine/pmap.h) 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, 01 Mar 2008 15:07:04 -0000 On Sat, 1 Mar 2008, Roman Divacky wrote: > I think you can use "ptoa(Maxmem) - round_page(MSGBUF_SIZE)", > the ptoa(Maxmem) > erm.. what I meant to say what > that hw.realmem - round_page(MSGBUF_SIZE) should work Hi: Before I saw your message, I continued my search and found an January 2007 mailing list message by Kip Macy on how to compute avail_end: http://groups.google.com/group/mailing.freebsd.current/msg/7039973c1586a8a7 static vm_paddr_t get_avail_end(void) { vm_paddr_t avail_end; int i; avail_end = phys_avail[1]; for (i = 0; phys_avail[i + 1]; i += 2) { if (phys_avail[i + 1] > avail_end) avail_end = phys_avail[i + 1]; } return avail_end; } Are the two methods equivalent? Also, how do I use hw.realmem like you suggested? I tried the following, but the file wouldn't compile: static vm_paddr_t avail_end = hw.realmem - round_page(MSGBUF_SIZE); Thank you! From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 1 15:40:28 2008 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 6D5211065675 for ; Sat, 1 Mar 2008 15:40:28 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from mx.utwente.nl (unknown [IPv6:2001:610:1908:1000:204:23ff:feb7:b8fe]) by mx1.freebsd.org (Postfix) with ESMTP id DF3AA8FC2D for ; Sat, 1 Mar 2008 15:40:27 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from lux.student.utwente.nl (lux.student.utwente.nl [130.89.170.81]) by mx.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id m21Fe3Xs023453; Sat, 1 Mar 2008 16:40:03 +0100 From: Pieter de Goeje To: freebsd-hackers@freebsd.org Date: Sat, 1 Mar 2008 16:40:02 +0100 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: <200803011640.02961.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact servicedesk@icts.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: Martin Laabs Subject: Re: SIGPIPE propagation 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, 01 Mar 2008 15:40:28 -0000 On Saturday 01 March 2008, Martin Laabs wrote: > Hello, > > as you probably know I want to expand dump in such > a way it enableds multivolume dumps also when the > output data is written to stdout/a pipe. > Now I ran into a serious problem. > Dump counts the written bytes to remember where > it has to proceede after the volumen change. > Now the SIGPIPE signal does not propagate fast > enought through the system. Thus dump writes > some time after the pipe has got broken data into > the pipe while it doesn't exist anymore. This short > time it does not receive any error about that. > (Until the signal propagates to dump.) > I wrote a small test progam to demonstrate this > effect (and get clear about it by myself). It just > write data to stdout and counts it until the pipe > is broken (and the write call will return -1) This > is the output of a few successively runs: This problem cannot be solved using sigpipe. You will always have a race condition because the reader's only way of notifying the writer that it shouldn't write anymore is through closing the pipe, after which the reader cannot read any remaining data that was just written to the pipe buffer. Given ./a.out | asdf Consider the fact that when you create a pipe, both ends are open. At this point it is possible to write a small amount of data to the pipe without blocking, because of the pipe buffer. The reader intends to close the pipe as soon as possible (command does not exist). Which of these events occurs first is however undefined, so sometimes a.out succeeds in writing data and sometimes it doesn't. writer reader | | write() (succeeds) | | close() | | sigpipe() | write() (fails) | The data in the pipe is now lost. > > > $ ./a.out |asdf > $ asdf: command not found > cought broken pipe > i: 12 could only wrote -1 bytes. total wrote: 61440 > > $ ./a.out |asdf > $ asdf: command not found > cought broken pipe > i: 1 could only wrote -1 bytes. total wrote: 5120 > > $ ./a.out |asdf > $ asdf: command not found > cought broken pipe > i: 12 could only wrote -1 bytes. total wrote: 61440 > > $ ./a.out |asdf > $ asdf: command not found > cought broken pipe > i: 0 could only wrote -1 bytes. total wrote: 0 -- Pieter de Goeje From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 1 20:11:40 2008 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 915A6106566B for ; Sat, 1 Mar 2008 20:11:40 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from mailout2.zih.tu-dresden.de (mailout2.zih.tu-dresden.de [141.30.67.73]) by mx1.freebsd.org (Postfix) with ESMTP id 4F70C8FC16 for ; Sat, 1 Mar 2008 20:11:39 +0000 (UTC) (envelope-from martin.laabs@mailbox.tu-dresden.de) Received: from rmc67-31.zih.tu-dresden.de ([141.30.67.31] helo=server-n) by mailout2.zih.tu-dresden.de with esmtp (Exim 4.63) (envelope-from ) id 1JVY3S-0002ax-My for freebsd-hackers@freebsd.org; Sat, 01 Mar 2008 21:11:38 +0100 Received: from martin (p5B0EEEFB.dip.t-dialin.net [91.14.238.251]) by server-n (Postfix) with ESMTP id 54682100A091 for ; Sat, 1 Mar 2008 21:11:34 +0100 (CET) Date: Sat, 01 Mar 2008 21:11:33 +0100 To: "freebsd-hackers@freebsd.org" From: "Martin Laabs" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Message-ID: User-Agent: Opera Mail/9.25 (Linux) X-TUD-Virus-Scanned: mailout2.zih.tu-dresden.de Subject: multi volume dump with gzip/crypt - solved 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, 01 Mar 2008 20:11:40 -0000 Hi, I solved the dump problem in a not very clean way. First I changed dumps behaviour to ignore the SIGPIPE signal when the -P and -a option is given. The problem with occured than was the loss of data because of the race condition between "write date to pipe" and "receive SIGPIPE". I solved that problem with a script that takes the data from the pipe of dump, compress it and sends a dedicated SIGPIPE to the three dump processes when the output volume is nealy full. After that it flushs the rest out of the pipe to avoid data loss. Greetings, Martin L.