From owner-freebsd-hackers Sun Jun 3 0:20:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id 8091937B422 for ; Sun, 3 Jun 2001 00:20:30 -0700 (PDT) (envelope-from netch@iv.nn.kiev.ua) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id KHU57462; Sun, 3 Jun 2001 10:20:17 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.11.3/8.11.3) id f537Inc01323; Sun, 3 Jun 2001 10:18:49 +0300 (EEST) (envelope-from netch) Date: Sun, 3 Jun 2001 10:18:49 +0300 From: Valentin Nechayev To: Jiangyi Liu Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How to recompile kernel after minor changes? Message-ID: <20010603101848.A990@iv.nn.kiev.ua> References: <878zjb20fd.fsf@fatcow.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <878zjb20fd.fsf@fatcow.home>; from gzjyliu@public.guangzhou.gd.cn on Sat, Jun 02, 2001 at 08:24:54AM +0800 X-42: On Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sat, Jun 02, 2001 at 08:24:54, gzjyliu (Jiangyi Liu) wrote about "How to recompile kernel after minor changes?": > After just changing a little in sys/kern/kern_sig.c, how can I rebuild > the kernel fast? I think it should not take such a long time as 'make > buildkernel' does. Anyway, just kern_sig.c need to be recompiled and > the kernel can be linked. So how do you guys do in such case? With changing only sys/kern/kern_sig.c, `make -DNOCLEAN -DNO_KERNELDEPEND -DNO_KERNELCONFIG -DNO_MODULES' can be used. But, cd /usr/obj/usr/src/sys/${KERNCONF} make -DNO_MODULES will be better and faster for human due to shorter commands. Really, `make buildkernel' is nesessary only for cross-platform build (`make buildworld' on earlier system is strictly considered as cross-platform build), and is too expensive for already installed system. But this receipt should be used with caution. Changes in conf/files*, e.g., require reconfiguring. Changes in headers require `make depend'. Some changes in file bodies also require `make depend', such as for aic7xxx stuff. If you don't know exactly which remakings are required by your change, do full reconfiguring and remaking. For modules, you should note that they aren't built with specified kernel config. If you strictly understand when kernel code is changed, MODULES_WITH_WORLD should be placed constantly in /etc/make.conf. ;-| For -current, `make install' in kernel compile directory will move all directory with old kernel and modules. I consider this feature too annoying, it should be off when either MODULES_WITH_WORLD or NO_MODULES is set (yes, I consider current feature as brain bug;))) /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 2: 2:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 85A9637B403 for ; Sun, 3 Jun 2001 02:02:37 -0700 (PDT) (envelope-from obrien@nuxi.ucdavis.edu) Received: from dragon.nuxi.com (root@[206.40.252.115]) by relay.nuxi.com (8.11.2/8.11.2) with ESMTP id f5392Ll86208; Sun, 3 Jun 2001 02:02:21 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f5392L589433; Sun, 3 Jun 2001 02:02:21 -0700 (PDT) (envelope-from obrien) Date: Sun, 3 Jun 2001 02:02:20 -0700 From: "David O'Brien - Hackers" To: Valentin Nechayev Cc: Jiangyi Liu , freebsd-hackers@FreeBSD.ORG Subject: Re: How to recompile kernel after minor changes? Message-ID: <20010603020220.A89269@dragon.nuxi.com> Reply-To: freebsd-hackers@FreeBSD.ORG References: <878zjb20fd.fsf@fatcow.home> <20010603101848.A990@iv.nn.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010603101848.A990@iv.nn.kiev.ua>; from netch@iv.nn.kiev.ua on Sun, Jun 03, 2001 at 10:18:49AM +0300 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jun 03, 2001 at 10:18:49AM +0300, Valentin Nechayev wrote: > > After just changing a little in sys/kern/kern_sig.c, how can I rebuild > > the kernel fast? I think it should not take such a long time as 'make > > buildkernel' does. Anyway, just kern_sig.c need to be recompiled and > > the kernel can be linked. So how do you guys do in such case? > > With changing only sys/kern/kern_sig.c, > `make -DNOCLEAN -DNO_KERNELDEPEND -DNO_KERNELCONFIG -DNO_MODULES' can be used. > But, > > cd /usr/obj/usr/src/sys/${KERNCONF} > make -DNO_MODULES or ``make kernel'' and if you want to live dangerously ``make kernel-reinstall''. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 4: 4:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from proxon.bnc.net (proxon.bnc.net [62.225.99.6]) by hub.freebsd.org (Postfix) with ESMTP id 3E48E37B401 for ; Sun, 3 Jun 2001 04:04:26 -0700 (PDT) (envelope-from noses@proxon.bnc.net) Received: (from noses@localhost) by proxon.bnc.net (8.11.3/8.11.3) id f53B4Nr07816; Sun, 3 Jun 2001 13:04:23 +0200 (CEST) (envelope-from noses) Date: Sun, 3 Jun 2001 13:04:23 +0200 (CEST) Message-Id: <200106031104.f53B4Nr07816@proxon.bnc.net> From: Noses To: hackers@freebsd.org Subject: Re: Real "technical comparison" Organization: Noses' cave In-Reply-To: X-Newsgroups: muc.lists.freebsd.hackers,mpc.lists.freebsd.hackers User-Agent: tin/1.5.6-20000803 ("Dust") (UNIX) (FreeBSD/4.3-STABLE (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article you wrote: >> Thank you for not telling it to one of my servers which is running >> around with about 100000 concurrent connections biting its tail. I >> wouldn't like to hurt its feelings. And I've got the feeling that it >> will have to bear a bit more of that beating. > > Interesting, what's that thing doing ? Grabing stuff from a number of database servers, combining it, turning it into HTML-documents (including converting graphics formats) and handing them off to the web servers which requested it. Which is causing a nice mix of network load and computations. And no, the server isn't even the highest possible end, not even near it; even my desktop machine has more CPU than this server (I'm just jelous of its RAM size). Noses. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 7:42:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id 19DBB37B403 for ; Sun, 3 Jun 2001 07:42:35 -0700 (PDT) (envelope-from netch@iv.nn.kiev.ua) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id RQJ70521; Sun, 3 Jun 2001 17:42:31 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.11.3/8.11.3) id f53AIf101075; Sun, 3 Jun 2001 13:18:41 +0300 (EEST) (envelope-from netch) Date: Sun, 3 Jun 2001 13:18:41 +0300 From: Valentin Nechayev To: freebsd-hackers@FreeBSD.ORG Cc: Jiangyi Liu Subject: Re: How to recompile kernel after minor changes? Message-ID: <20010603131841.A460@iv.nn.kiev.ua> References: <878zjb20fd.fsf@fatcow.home> <20010603101848.A990@iv.nn.kiev.ua> <20010603020220.A89269@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010603020220.A89269@dragon.nuxi.com>; from freebsd-hackers@FreeBSD.ORG on Sun, Jun 03, 2001 at 02:02:20AM -0700 X-42: On Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sun, Jun 03, 2001 at 02:02:20, freebsd-hackers (David O'Brien - Hackers) wrote about "Re: How to recompile kernel after minor changes?": > > cd /usr/obj/usr/src/sys/${KERNCONF} > > make -DNO_MODULES > or ``make kernel'' > and if you want to live dangerously ``make kernel-reinstall''. You are right, it is dangerous because it does not copy current kernel to /boot/kernel/kernel.old. I need to do it by hands (install -c -fschg ...) /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 7:49:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from maxim.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id 08EA137B401 for ; Sun, 3 Jun 2001 07:49:54 -0700 (PDT) (envelope-from gjb@gbch.net) Received: (qmail 24683 invoked by uid 1001); 4 Jun 2001 00:49:43 +1000 Message-ID: X-Posted-By: GJB-Post 2.19 02-May-2001 X-Operating-System: FreeBSD 4.2-RELEASE i386 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.gbch.net/gjb.html X-Image-URL: http://www.gbch.net/gjb/gjb-auug048.gif X-GPG-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-PGP-Public-Keys: http://www.gbch.net/keys.html Date: Mon, 04 Jun 2001 00:49:43 +1000 From: Greg Black To: Garance A Drosihn Cc: Dima Dorfman , hackers@FreeBSD.ORG Subject: Re: Fixing documented bug in env(1) References: <20010602041242.849893E33@bazooka.unixfreak.org> In-reply-to: of Sat, 02 Jun 2001 02:03:38 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Garance A Drosihn wrote: | At 9:12 PM -0700 6/1/01, Dima Dorfman wrote: | >Honestly, I don't care about this all that much. I'll | >let you and David debate this to your liking. If no | >consensus develops in the next few days, I'll just | >commit what I have now. | | For whatever it's worth, it seems more reasonable to me | to use '--' instead of '=='. Since '--' has NO equals | sign in it, it clearly can't be the setting of an | environment variable. If we're voting on this, I'm very strongly in favour of `--'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 8:29:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from jxmls04.se.mediaone.net (jxmls04.se.mediaone.net [24.129.0.51]) by hub.freebsd.org (Postfix) with ESMTP id A467637B403 for ; Sun, 3 Jun 2001 08:29:30 -0700 (PDT) (envelope-from scott@mediaone.net) Received: from bsd (rr-163-52-193.atl.mediaone.net [24.163.52.193]) by jxmls04.se.mediaone.net (8.11.1/8.11.1) with ESMTP id f53FSqL17563 for ; Sun, 3 Jun 2001 11:28:52 -0400 (EDT) Date: Sun, 3 Jun 2001 11:28:54 -0400 (EDT) From: Scott Nolde X-X-Sender: Reply-To: To: Subject: building /usr/ports/x11-fm/fsv Message-ID: <20010603112650.W75725-100000@bsd.smnolde.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG After a fresh cvsup of prts to my 4.3-STABLE system, I get the following error when building fsv: #include "confdefs.h" /* Override any gcc2 internal prototype to avoid an error. */ /* We use char because int might match the return type of a gcc2 builtin and then its argument prototype would still apply. */ char glBegin(); int main() { glBegin() ; return 0; } configure:4157: checking for glBegin in -lGL configure:4176: cc -o conftest -O -pipe -I/usr/local/include conftest.c -lGL -L/usr/X11R6/lib -L/usr/X11R6/lib -lgtk12 -lgdk12 -L/usr/local/lib -Wl,-E -lgmodule12 -lglib12 -lintl -lxpg4 -lXext -lX11 -lm -L/usr/X11R6/lib/lib -L/usr/local/lib 1>&5 /usr/X11R6/lib/libGL.so: undefined reference to `pthread_getspecific' /usr/X11R6/lib/libGL.so: undefined reference to `pthread_key_create' /usr/X11R6/lib/libGL.so: undefined reference to `pthread_setspecific' configure: failed program was: #line 4165 "configure" #include "confdefs.h" /* Override any gcc2 internal prototype to avoid an error. */ /* We use char because int might match the return type of a gcc2 builtin and then its argument prototype would still apply. */ char glBegin(); int main() { glBegin() ; return 0; } (end of "config.log") *** Error code 1 Any ideas? Thanks, Scott ---begin-encrypted-message--- !SKCUS TN SWODNIW ---end---encrypted-message--- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 9:24:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Terry.Dorm8.NCTU.edu.tw (Terry.Dorm8.NCTU.edu.tw [140.113.93.99]) by hub.freebsd.org (Postfix) with ESMTP id 03F5E37B401 for ; Sun, 3 Jun 2001 09:24:05 -0700 (PDT) (envelope-from ijliao@Terry.Dorm8.NCTU.edu.tw) Received: (from ijliao@localhost) by Terry.Dorm8.NCTU.edu.tw (8.11.3/8.11.2) id f53GNu496892; Mon, 4 Jun 2001 00:23:56 +0800 (CST) (envelope-from ijliao) Date: Mon, 4 Jun 2001 00:23:56 +0800 From: Ying-Chieh Liao To: smnoldelinux@mediaone.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: building /usr/ports/x11-fm/fsv Message-ID: <20010604002356.A95962@terry.dragon2.net> References: <20010603112650.W75725-100000@bsd.smnolde.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IJpNTDwzlM2Ie8A6" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: =?big5:gb2312:us-ascii:iso-8859-1:utf-8:x-unknown?Q?=3C20010603112650=2E?= =?big5:gb2312:us-ascii:iso-8859-1:utf-8:x-unknown?Q?W75725-100000=40bsd?= =?big5:gb2312:us-ascii:iso-8859-1:utf-8:x-unknown?Q?=2Esmnolde=2Ecom=3E?= =?big5:gb2312:us-ascii:iso-8859-1:utf-8:x-unknown?Q?=3B_from_scott=40med?= =?big5:gb2312:us-ascii:iso-8859-1:utf-8:x-unknown?Q?iaone=2Enet_on_=A4?= =?big5:gb2312:us-ascii:iso-8859-1:utf-8:x-unknown?Q?=E9=2C__6_03=2C_2001?= =?big5:gb2312:us-ascii:iso-8859-1:utf-8:x-unknown?Q?_at_11:28:54=A4W=A4?= =?big5:gb2312:us-ascii:iso-8859-1:utf-8:x-unknown?Q?=C8_-0400?= X-Operating-System: FreeBSD 5.0-CURRENT i386 X-PGP-Key-Location: http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x11C02382 X-PGP-Key-Fingerprint: 4E98 55CC 2866 7A90 EFD7 9DA5 ACC6 0165 11C0 2382 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --IJpNTDwzlM2Ie8A6 Content-Type: text/plain; charset=big5:gb2312:us-ascii:iso-8859-1:utf-8:x-unknown Content-Disposition: inline Content-Transfer-Encoding: 8bit On ¤é, 6 03, 2001 at 11:28:54 -0400, Scott Nolde wrote: > After a fresh cvsup of prts to my 4.3-STABLE system, I get the following > error when building fsv: [deleted] > configure:4157: checking for glBegin in -lGL > configure:4176: cc -o conftest -O -pipe -I/usr/local/include conftest.c > -lGL -L/usr/X11R6/lib -L/usr/X11R6/lib -lgtk12 -lgdk12 -L/usr/local/lib > -Wl,-E -lgmodule12 -lglib12 -lintl -lxpg4 -lXext -lX11 -lm > -L/usr/X11R6/lib/lib -L/usr/local/lib 1>&5 > /usr/X11R6/lib/libGL.so: undefined reference to `pthread_getspecific' > /usr/X11R6/lib/libGL.so: undefined reference to `pthread_key_create' > /usr/X11R6/lib/libGL.so: undefined reference to `pthread_setspecific' this was reported as pr/27036 -- Testing can show the presence of bugs, but not their absence. --- Edsger W. Dijkstra --IJpNTDwzlM2Ie8A6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7GmR3rMYBZRHAI4IRAmooAJ4hXsOhKmxhleVDRXImv26+jlHoewCdGoLf agU3TB90WxzlLVJPBtM+9aY= =LlOC -----END PGP SIGNATURE----- --IJpNTDwzlM2Ie8A6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 9:47:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id B944C37B401 for ; Sun, 3 Jun 2001 09:47:50 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 3 Jun 2001 17:47:50 +0100 (BST) To: Matt Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UFS large directory performance In-Reply-To: Your message of "Sat, 02 Jun 2001 10:47:56 PDT." <200106021747.f52Hluf03989@earth.backplane.com> Date: Sun, 03 Jun 2001 17:47:49 +0100 From: Ian Dowse Message-ID: <200106031747.aa54373@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200106021747.f52Hluf03989@earth.backplane.com>, Matt Dillon writes: > > I would further recommend a (dynamic) array of pointers at the first > level as part of the summary structure. Any given array entry would > either point to the second level array (the 512 byte allocations), > be NULL (no second level array was necessary), or be (void *)-1 which > would indicate that the second level array was reclaimed for other > uses. Nice idea, but I'm not sure I see the benefit of partially reclaiming second-level arrays. Because it is a hash array, there isn't really the concept of a working set; a directory that is `in use' will rarely see many create/rename/delete operations on a small fixed set of filenames. The lookup case is already cached elsewhere. I think an all-or-nothing approach is likely to perform better and be simpler to implement. Even the lazy allocation of second-level arrays is unlikely to help a lot if the hash function does its job well. > > If the zone allocator is used for the second level block allocations > it shouldn't be a problem. You can (had better be able to!) put a mutex > around zone frees in -current. The locking issues I could see were more in the area of finding inodes to free hashes from. A linked list of dirhash structures could be maintained (protected by a mutex), but to free the dirhash belonging to an inode, the inode would probably need to be locked. That means dereferencing dirhash->dh_inode->i_vnode and trying to lock it, so things become complex. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 11:53:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 837FF37B401 for ; Sun, 3 Jun 2001 11:53:54 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f53Irpe10632; Sun, 3 Jun 2001 11:53:51 -0700 (PDT) (envelope-from dillon) Date: Sun, 3 Jun 2001 11:53:51 -0700 (PDT) From: Matt Dillon Message-Id: <200106031853.f53Irpe10632@earth.backplane.com> To: Ian Dowse Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UFS large directory performance References: <200106031747.aa54373@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Nice idea, but I'm not sure I see the benefit of partially reclaiming :second-level arrays. Because it is a hash array, there isn't really :the concept of a working set; a directory that is `in use' will :rarely see many create/rename/delete operations on a small fixed :set of filenames. The lookup case is already cached elsewhere. I :think an all-or-nothing approach is likely to perform better and :be simpler to implement. Even the lazy allocation of second-level :arrays is unlikely to help a lot if the hash function does its job :well. Well, amoung other things it solves the locking problem you bring up below. Even if partial reclamation doesn't maintain performance, it still definitely allows you to reclaim second level entities on the fly from other inodes for use in a new directory scan when you hit up against the memory limit. You could in fact make the reclamation a simple FIFO rather then an LRU, simplifying the structure. :> If the zone allocator is used for the second level block allocations :> it shouldn't be a problem. You can (had better be able to!) put a mutex :> around zone frees in -current. : :The locking issues I could see were more in the area of finding :inodes to free hashes from. A linked list of dirhash structures :could be maintained (protected by a mutex), but to free the dirhash :belonging to an inode, the inode would probably need to be locked. :That means dereferencing dirhash->dh_inode->i_vnode and trying to :lock it, so things become complex. : :Ian I think you can avoid locking the inode. The dirhash is entirely independant of the inode except when it is accessed to aid in a directory operation. The access point can be locked separately with a mutex in -current, and need not be locked at all in -stable. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 13: 0: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Mail.ZEDAT.FU-Berlin.DE (mail.zedat.fu-berlin.de [130.133.1.48]) by hub.freebsd.org (Postfix) with ESMTP id A4B6037B405 for ; Sun, 3 Jun 2001 13:00:07 -0700 (PDT) (envelope-from sck@ZEDAT.FU-Berlin.DE) Received: by Mail.ZEDAT.FU-Berlin.DE (Smail3.2.0.98) id ; Sun, 3 Jun 2001 22:00:03 +0200 (MEST) Date: Sun, 3 Jun 2001 22:00:03 +0200 From: "Sven C. Koehler" To: Vojislav Milunovic Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ptrace() Message-ID: <20010603220003.A18458@zedat.fu-berlin.de> Reply-To: schween@snafu.de Mail-Followup-To: "Sven C. Koehler" , Vojislav Milunovic , freebsd-hackers@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You might also consider to get this article from http://www.ddj.com/: Dr. Dobb's Journal March 1998 - Benchmarking and Software Testing, Tracing BSD System Calls, by Sean Eric Fagan AFAIR, in this article is explained what steps were necessary to make a ptrace() for FreeBSD. Maybe, someone here knows where to get this article without buying it from ddj. Best Regards, Sven C. Koehler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 13:23: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 902BD37B403 for ; Sun, 3 Jun 2001 13:23:02 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f53KW6601613; Sun, 3 Jun 2001 13:32:07 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106032032.f53KW6601613@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: schween@snafu.de Cc: Vojislav Milunovic , freebsd-hackers@FreeBSD.ORG Subject: Re: ptrace() In-reply-to: Your message of "Sun, 03 Jun 2001 22:00:03 +0200." <20010603220003.A18458@zedat.fu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jun 2001 13:32:06 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > You might also consider to get this article from http://www.ddj.com/: > > Dr. Dobb's Journal March 1998 - Benchmarking and Software > Testing, Tracing BSD System Calls, by Sean Eric Fagan > > AFAIR, in this article is explained what steps were necessary to make a > ptrace() for FreeBSD. No, this describes the implementation of truss(1) for FreeBSD. You can just go read the sources... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 15:17:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 976F337B401 for ; Sun, 3 Jun 2001 15:17:48 -0700 (PDT) (envelope-from obrien@nuxi.ucdavis.edu) Received: from dragon.nuxi.com (root@trang.muxi.com [206.40.252.115] (may be forged)) by relay.nuxi.com (8.11.2/8.11.2) with ESMTP id f53MHhl89724; Sun, 3 Jun 2001 15:17:43 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f53MHfi30657; Sun, 3 Jun 2001 15:17:41 -0700 (PDT) (envelope-from obrien) Date: Sun, 3 Jun 2001 15:17:41 -0700 From: "David O'Brien" To: Greg Black Cc: Garance A Drosihn , Dima Dorfman , hackers@FreeBSD.ORG Subject: Re: Fixing documented bug in env(1) Message-ID: <20010603151741.A30607@dragon.nuxi.com> Reply-To: hackers@FreeBSD.ORG References: <20010602041242.849893E33@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gjb@gbch.net on Mon, Jun 04, 2001 at 12:49:43AM +1000 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jun 04, 2001 at 12:49:43AM +1000, Greg Black wrote: > | For whatever it's worth, it seems more reasonable to me > | to use '--' instead of '=='. Since '--' has NO equals > | sign in it, it clearly can't be the setting of an > | environment variable. > > If we're voting on this, I'm very strongly in favour of `--'. Why? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 15:19:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id AA92237B401 for ; Sun, 3 Jun 2001 15:19:41 -0700 (PDT) (envelope-from obrien@nuxi.ucdavis.edu) Received: from dragon.nuxi.com (root@trang.muxi.com [206.40.252.115] (may be forged)) by relay.nuxi.com (8.11.2/8.11.2) with ESMTP id f53MJel89742; Sun, 3 Jun 2001 15:19:40 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f53MJdm30672; Sun, 3 Jun 2001 15:19:39 -0700 (PDT) (envelope-from obrien) Date: Sun, 3 Jun 2001 15:19:39 -0700 From: "David O'Brien" To: Mark Valentine Cc: Peter Seebach , hackers@freebsd.org Subject: Re: Fixing documented bug in env(1) Message-ID: <20010603151939.B30607@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200106021618.f52GIjd35540@dotar-sojat.thuvia.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106021618.f52GIjd35540@dotar-sojat.thuvia.org>; from mark@thuvia.demon.co.uk on Sat, Jun 02, 2001 at 05:18:45PM +0100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mark you've given the justification and logic behind `==' much, much better than I did. Thanks! :-) -- -- David (obrien@FreeBSD.org) P.S. typically I don't quote a whole message like this, but I think it is important that at least read this one and honestly consider it. On Sat, Jun 02, 2001 at 05:18:45PM +0100, Mark Valentine wrote: > > people use -- > > to end subsequences of arguments all the time. > > No, they use ``--'' to indicate to getopt(3) the end of the _options_ and > the _start_ of the arguments. > > Since env(1) uses getopt(3), ``--'' already has meaning to env(1); it allows > environment variables and commands which start with ``-'' (the former is > obviously invalid). > > $ env -i -- -t args > > currently allows execution of command ``-t''. > > However, what Dima proposes doesn't seem to be harmful, just slightly > confusing, and less surprising than inventing a new delimieter such as > ``==''. > > $ env -i -- foo=bar -- 4=4 args > > has two distinct uses of `--'' as per Dima's proposal, the first tells > getopt(3) to stop processing options, and the second tells the argument > processing code to stop looking for variable assignments (i.e. ``4=4'' > is a command). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 15:27:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from messiah.megadeb.org (cpe.atm0-0-0-218131.arcnxx5.customer.tele.dk [62.242.79.117]) by hub.freebsd.org (Postfix) with ESMTP id 9697A37B401 for ; Sun, 3 Jun 2001 15:27:46 -0700 (PDT) (envelope-from chopra@runbox.com) Received: (from chopra@localhost) by messiah.megadeb.org (8.11.3/8.11.3) id f53MTGS08548 for freebsd-hackers@FreeBSD.ORG; Mon, 4 Jun 2001 00:29:16 +0200 (CEST) (envelope-from chopra) Date: Mon, 4 Jun 2001 00:28:01 +0200 From: Munish Chopra To: freebsd-hackers@FreeBSD.ORG Subject: Re: building /usr/ports/x11-fm/fsv Message-ID: <20010604002801.C95721@messiah.megadeb.org> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <20010603112650.W75725-100000@bsd.smnolde.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010603112650.W75725-100000@bsd.smnolde.com>; from scott@mediaone.net on Sun, Jun 03, 2001 at 11:28:54AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jun 03, 2001 at 11:28:54AM -0400, Scott Nolde wrote: > After a fresh cvsup of prts to my 4.3-STABLE system, I get the following > error when building fsv: > > #include "confdefs.h" > /* Override any gcc2 internal prototype to avoid an error. */ > /* We use char because int might match the return type of a gcc2 > builtin and then its argument prototype would still apply. */ > char glBegin(); > > int main() { > glBegin() > ; return 0; } > configure:4157: checking for glBegin in -lGL > configure:4176: cc -o conftest -O -pipe -I/usr/local/include conftest.c > -lGL -L/usr/X11R6/lib -L/usr/X11R6/lib -lgtk12 -lgdk12 -L/usr/local/lib > -Wl,-E -lgmodule12 -lglib12 -lintl -lxpg4 -lXext -lX11 -lm > -L/usr/X11R6/lib/lib -L/usr/local/lib 1>&5 > /usr/X11R6/lib/libGL.so: undefined reference to `pthread_getspecific' > /usr/X11R6/lib/libGL.so: undefined reference to `pthread_key_create' > /usr/X11R6/lib/libGL.so: undefined reference to `pthread_setspecific' > configure: failed program was: > #line 4165 "configure" > #include "confdefs.h" > /* Override any gcc2 internal prototype to avoid an error. */ > /* We use char because int might match the return type of a gcc2 > builtin and then its argument prototype would still apply. */ > char glBegin(); > > int main() { > glBegin() > ; return 0; } > (end of "config.log") > *** Error code 1 I got the same thing a few days ago trying to build net/fidelio: /tmp/ccUBd9xD.o: In function `main': /tmp/ccUBd9xD.o(.text+0x7): undefined reference to `xmlCleanURI' configure: failed program was: #line 5000 "configure" #include "confdefs.h" /* Override any gcc2 internal prototype to avoid an error. */ /* We use char because int might match the return type of a gcc2 builtin and then its argument prototype would still apply. */ char xmlCleanURI(); int main() { xmlCleanURI() ; return 0; } (end of "config.log") *** Error code 1 ...I'm assuming it's more or less the same thing. I'd be interested in answers... -- -Munish To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 15:40: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id A580937B403 for ; Sun, 3 Jun 2001 15:40:00 -0700 (PDT) (envelope-from seebs@plethora.net) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f53Mdr521522 for ; Sun, 3 Jun 2001 17:39:54 -0500 (CDT) Message-Id: <200106032239.f53Mdr521522@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: hackers@FreeBSD.ORG Subject: Re: Fixing documented bug in env(1) In-reply-to: Your message of "Sun, 03 Jun 2001 15:19:39 PDT." <20010603151939.B30607@dragon.nuxi.com> Date: Sun, 03 Jun 2001 17:39:53 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010603151939.B30607@dragon.nuxi.com>, "David O'Brien" writes: >Mark you've given the justification and logic behind `==' much, much >better than I did. Thanks! :-) And yet, he says: >> However, what Dima proposes doesn't seem to be harmful, just slightly >> confusing, and less surprising than inventing a new delimieter such as >> ``==''. == is very confusing, and it's not the way anything else has ever done delimiters. "--" already means "change the way you process words". It's only marginally surprising to use it for another change. >> $ env -i -- foo=bar -- 4=4 args >> has two distinct uses of `--'' as per Dima's proposal, the first tells >> getopt(3) to stop processing options, and the second tells the argument >> processing code to stop looking for variable assignments (i.e. ``4=4'' >> is a command). And this is fairly consistent. e.g., I used to have a utility which used '--' to indicate each *set* of options, so you could have many of them, as each set of options went to a different program. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 16:44:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from maxim.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id BB16837B403 for ; Sun, 3 Jun 2001 16:44:04 -0700 (PDT) (envelope-from gjb@gbch.net) Received: (qmail 36352 invoked by uid 1001); 4 Jun 2001 09:43:53 +1000 Message-ID: X-Posted-By: GJB-Post 2.19 02-May-2001 X-Operating-System: FreeBSD 4.2-RELEASE i386 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.gbch.net/gjb.html X-Image-URL: http://www.gbch.net/gjb/gjb-auug048.gif X-GPG-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-PGP-Public-Keys: http://www.gbch.net/keys.html Date: Mon, 04 Jun 2001 09:43:53 +1000 From: Greg Black To: hackers@FreeBSD.ORG Cc: Garance A Drosihn , Dima Dorfman Subject: Re: Fixing documented bug in env(1) References: <20010602041242.849893E33@bazooka.unixfreak.org> <20010603151741.A30607@dragon.nuxi.com> In-reply-to: <20010603151741.A30607@dragon.nuxi.com> of Sun, 03 Jun 2001 15:17:41 MST Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David O'Brien wrote: | On Mon, Jun 04, 2001 at 12:49:43AM +1000, Greg Black wrote: | > | For whatever it's worth, it seems more reasonable to me | > | to use '--' instead of '=='. Since '--' has NO equals | > | sign in it, it clearly can't be the setting of an | > | environment variable. | > | > If we're voting on this, I'm very strongly in favour of `--'. | | Why? The reasons have already been articulated. In brief, there is prior experience with using `--' as an indicator that argument processing is to change at this point; using it twice for the same purpose conflicts less with POLA than inventing the `==' thing, which has never been used for anything. The real reason for my post was that there was an indication that responses in favour of one or the other of the proposed mechanisms would be taken into account in the decision. I don't want to see this `==' idea get up. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 16:53: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from phaidor.thuvia.org (thuvia.demon.co.uk [193.237.34.248]) by hub.freebsd.org (Postfix) with ESMTP id E66F737B405 for ; Sun, 3 Jun 2001 16:52:55 -0700 (PDT) (envelope-from mark@thuvia.demon.co.uk) Received: from dotar-sojat.thuvia.org (dotar-sojat.thuvia.org [10.0.0.4]) by phaidor.thuvia.org (8.11.3/8.11.3) with ESMTP id f53Nque16910; Mon, 4 Jun 2001 00:52:56 +0100 (BST) (envelope-from mark@dotar-sojat.thuvia.org) Received: (from mark@localhost) by dotar-sojat.thuvia.org (8.11.3/8.11.3) id f53Nqvn47341; Mon, 4 Jun 2001 00:52:57 +0100 (BST) (envelope-from mark) Date: Mon, 4 Jun 2001 00:52:57 +0100 (BST) From: Mark Valentine Message-Id: <200106032352.f53Nqvn47341@dotar-sojat.thuvia.org> In-Reply-To: Peter Seebach's message of Jun 3, 10:46pm X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: seebs@plethora.net (Peter Seebach), hackers@freebsd.org Subject: Re: Fixing documented bug in env(1) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > From: seebs@plethora.net (Peter Seebach) > Date: Sun 3 Jun, 2001 > Subject: Re: Fixing documented bug in env(1) > >> However, what Dima proposes doesn't seem to be harmful, just slightly > >> confusing, and less surprising than inventing a new delimieter such as > >> ``==''. > > == is very confusing, and it's not the way anything else has ever done > delimiters. "--" already means "change the way you process words". It's > only marginally surprising to use it for another change. Yes, I was (sort of) supporting ``--'' as an "end of assignment" delimiter here; however, one more compatibility issue throws a spanner in the works... Both ``--'' and ``=='' are valid commands, and currently only the former is handled by env(1): $ env foo=bar -- args executes the command ``--''. Dima's proposal would require this to change: $ env foo=bar -- -- args David's proposal would not break this, and would allow $ env foo=bar == == args to execute the command ``==''. David's proposal only seems to break even more obscure (erroneous?) stuff like: $ env foo=bar == bar=foo command args (Tell me that no script anywhere relies on this long-standing behaviour!) Actually I don't like either solution much (if the documented bug were this easy to fix, it would have been fixed decades ago...). Commands starting with ``-'' already cause grief (e.g. in make(1)), and commands with ``='' in their names almost certainly break in all sorts of other contexts (e.g. when used unquoted in a Bourne shell). (Do any shells still treat ``foo=bar'' as an assigment anywhere on the command line?) I'd leave the "bug" alone, pending real enlightenment... By the way, who uses env(1) anyway? In the past twenty years, I've only ever used it as shorthand for printenv(1). What's this csh(1) thing? :-) Hmm, would a new csh(1) builtin help any? /bin/sh: $ foo=bar bar=foo echo hello hello $ foo=bar 'bar=foo' echo hello bar=foo: not found /bin/csh: % env foo=bar bar=foo echo hello hello % env foo=bar 'bar=foo' echo hello hello % withenv foo=bar 'bar=foo' echo hello # new withenv(1) builtin bar=foo: not found (I'm not up on csh(1)'s foibles sufficiently to tell whether this would be a done thing, but its syntax already seems fairly, erm, what's the polite word?) Cheers, Mark. -- Mark Valentine, Thuvia Labs "Tigers will do ANYTHING for a tuna fish sandwich." Mark Valentine uses "We're kind of stupid that way." *munch* *munch* and endorses FreeBSD -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 16:58: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id 55F2E37B401 for ; Sun, 3 Jun 2001 16:57:55 -0700 (PDT) (envelope-from seebs@plethora.net) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f53Nup522856 for ; Sun, 3 Jun 2001 18:56:53 -0500 (CDT) Message-Id: <200106032356.f53Nup522856@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: hackers@freebsd.org Subject: Re: Fixing documented bug in env(1) In-reply-to: Your message of "Mon, 04 Jun 2001 00:52:57 BST." <200106032352.f53Nqvn47341@dotar-sojat.thuvia.org> Date: Sun, 03 Jun 2001 18:56:51 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200106032352.f53Nqvn47341@dotar-sojat.thuvia.org>, Mark Valentine w rites: >Yes, I was (sort of) supporting ``--'' as an "end of assignment" delimiter >here; however, one more compatibility issue throws a spanner in the works... >Both ``--'' and ``=='' are valid commands, and currently only the former is >handled by env(1): I doubt that anyone's using either, but it's a good point. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 19:18:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ska.bsn (CPE-144-132-209-248.nsw.bigpond.net.au [144.132.209.248]) by hub.freebsd.org (Postfix) with ESMTP id BD7DC37B401 for ; Sun, 3 Jun 2001 19:18:41 -0700 (PDT) (envelope-from atrn@zeta.org.au) Received: from juju.bsn (juju.bsn [192.168.1.5]) by ska.bsn (8.9.3/8.9.3) with ESMTP id MAA26653 for ; Mon, 4 Jun 2001 12:18:40 +1000 (EST) (envelope-from andy@ska.bsn) Received: (from andy@localhost) by juju.bsn (8.11.1/8.9.3) id f542IeV04930 for hackers@FreeBSD.org; Mon, 4 Jun 2001 12:18:40 +1000 (EST) (envelope-from andy) Date: Mon, 4 Jun 2001 12:18:40 +1000 From: Andy Newman To: hackers@FreeBSD.org Subject: Re: Fixing documented bug in env(1) Message-ID: <20010604121840.A4547@juju.bsn> References: <200106032352.f53Nqvn47341@dotar-sojat.thuvia.org> <200106032356.f53Nup522856@guild.plethora.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200106032356.f53Nup522856@guild.plethora.net>; from seebs@plethora.net on Sun, Jun 03, 2001 at 06:56:51PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jun 03, 2001 at 06:56:51PM -0500, Peter Seebach wrote: > I doubt that anyone's using either, but it's a good point. '==' was/is part of the Bourne shell command line history stuff (*) a few people at UofSydney hacked together in the very early '80s, But you're right, very few people, if any, use it. -- Andy Newman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 20:51:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from areilly.bpc-users.org (CPE-144-132-234-126.nsw.bigpond.net.au [144.132.234.126]) by hub.freebsd.org (Postfix) with SMTP id 14CAF37B401 for ; Sun, 3 Jun 2001 20:51:07 -0700 (PDT) (envelope-from areilly@bigpond.net.au) Received: (qmail 9593 invoked by uid 1000); 4 Jun 2001 03:51:06 -0000 From: "Andrew Reilly" Date: Mon, 4 Jun 2001 13:51:06 +1000 To: Mark Valentine Cc: Peter Seebach , hackers@freebsd.org Subject: Re: Fixing documented bug in env(1) Message-ID: <20010604135106.A8896@gurney.reilly.home> References: <200106032352.f53Nqvn47341@dotar-sojat.thuvia.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106032352.f53Nqvn47341@dotar-sojat.thuvia.org>; from mark@thuvia.demon.co.uk on Mon, Jun 04, 2001 at 12:52:57AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jun 04, 2001 at 12:52:57AM +0100, Mark Valentine wrote: > I'd leave the "bug" alone, pending real enlightenment... Me too. I've never met a command name with an "=" in it. > By the way, who uses env(1) anyway? In the past twenty years, I've only > ever used it as shorthand for printenv(1). What's this csh(1) thing? :-) How else do you throw away your environment, to make sure that daemons that you start with sudo don't do anything silly? I'm pretty sure that I copied this /etc/start_if.ed0 from somewhere, rather than making it up: env - PATH=$PATH dhclient ed0 It's also quite commonly used in /usr/local/etc/rc.d scripts, including qmail and courier-imap. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 21:41:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from phaidor.thuvia.org (thuvia.demon.co.uk [193.237.34.248]) by hub.freebsd.org (Postfix) with ESMTP id 4952737B401 for ; Sun, 3 Jun 2001 21:41:32 -0700 (PDT) (envelope-from mark@thuvia.demon.co.uk) Received: from dotar-sojat.thuvia.org (dotar-sojat.thuvia.org [10.0.0.4]) by phaidor.thuvia.org (8.11.3/8.11.3) with ESMTP id f544fRm00449; Mon, 4 Jun 2001 05:41:27 +0100 (BST) (envelope-from mark@dotar-sojat.thuvia.org) Received: (from mark@localhost) by dotar-sojat.thuvia.org (8.11.3/8.11.3) id f544fOF58859; Mon, 4 Jun 2001 05:41:24 +0100 (BST) (envelope-from mark) Date: Mon, 4 Jun 2001 05:41:24 +0100 (BST) From: Mark Valentine Message-Id: <200106040441.f544fOF58859@dotar-sojat.thuvia.org> In-Reply-To: "Andrew Reilly"'s message of Jun 4, 1:51pm X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: "Andrew Reilly" Subject: Re: Fixing documented bug in env(1) Cc: Peter Seebach , hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > From: "Andrew Reilly" > Date: Mon 4 Jun, 2001 > Subject: Re: Fixing documented bug in env(1) > > By the way, who uses env(1) anyway? In the past twenty years, I've only > > ever used it as shorthand for printenv(1). What's this csh(1) thing? :-) > > How else do you throw away your environment, to make sure that > daemons that you start with sudo don't do anything silly? > > env - PATH=$PATH dhclient ed0 Using env(1) without any assumtion about command line assignment parsing purely as an illustration: $ env - sh -c "PATH=$PATH dhclient ed0" I'd probably wrap thus up in a script (or external program for ease of use by various shells) - the semantics are subtly different from env(1): $ clearenv() { env - sh -c "$*"; } # cheap and nasty to illustrate $ clearenv PATH=$PATH dhclient ed0 Making clearenv(1) an external program (which doesn't itself parse command line variable assignments) may simplify quoting, and if ``dhclient'' were instead a shell builtin such as echo(1), you'd need to avoid the shortcut above, as in: $ clearenv "PATH=$PATH; export PATH; dhclient ed0" Cheers, Mark. -- Mark Valentine, Thuvia Labs "Tigers will do ANYTHING for a tuna fish sandwich." Mark Valentine uses "We're kind of stupid that way." *munch* *munch* and endorses FreeBSD -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 21:54:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from phaidor.thuvia.org (thuvia.demon.co.uk [193.237.34.248]) by hub.freebsd.org (Postfix) with ESMTP id A4C7237B401 for ; Sun, 3 Jun 2001 21:54:20 -0700 (PDT) (envelope-from mark@thuvia.demon.co.uk) Received: from dotar-sojat.thuvia.org (dotar-sojat.thuvia.org [10.0.0.4]) by phaidor.thuvia.org (8.11.3/8.11.3) with ESMTP id f544sGm00499; Mon, 4 Jun 2001 05:54:16 +0100 (BST) (envelope-from mark@dotar-sojat.thuvia.org) Received: (from mark@localhost) by dotar-sojat.thuvia.org (8.11.3/8.11.3) id f544sNS59621; Mon, 4 Jun 2001 05:54:23 +0100 (BST) (envelope-from mark) Date: Mon, 4 Jun 2001 05:54:23 +0100 (BST) From: Mark Valentine Message-Id: <200106040454.f544sNS59621@dotar-sojat.thuvia.org> In-Reply-To: Mark Valentine's message of Jun 4, 5:41am X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: "Andrew Reilly" Subject: Re: Fixing documented bug in env(1) Cc: Peter Seebach , hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > $ clearenv() { env - sh -c "$*"; } # cheap and nasty to illustrate Hmm, my point was as clear as mud there. I was trying to show that "env -" performs a useful function, but a program which performs this function has no need to duplicate the shell's ability to _assign_ environment variables. Cheers, Mark. -- Mark Valentine, Thuvia Labs "Tigers will do ANYTHING for a tuna fish sandwich." Mark Valentine uses "We're kind of stupid that way." *munch* *munch* and endorses FreeBSD -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jun 3 23:17: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 9E4DC37B401 for ; Sun, 3 Jun 2001 23:16:59 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 4050 invoked by uid 100); 4 Jun 2001 06:16:58 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15131.10202.189874.233196@guru.mired.org> Date: Mon, 4 Jun 2001 01:16:58 -0500 To: "Andrew Reilly" Cc: Mark Valentine , Peter Seebach , hackers@freebsd.org Subject: Re: Fixing documented bug in env(1) In-Reply-To: <20010604135106.A8896@gurney.reilly.home> References: <200106032352.f53Nqvn47341@dotar-sojat.thuvia.org> <20010604135106.A8896@gurney.reilly.home> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andrew Reilly types: > On Mon, Jun 04, 2001 at 12:52:57AM +0100, Mark Valentine wrote: > > By the way, who uses env(1) anyway? In the past twenty years, I've only > > ever used it as shorthand for printenv(1). What's this csh(1) thing? :-) > How else do you throw away your environment, to make sure that > daemons that you start with sudo don't do anything silly? I think it's more commonly used in scripts, so you don't have to worry about where the interpreter is installed. The python folks are recommending the user of "#!/usr/bin/env python" instead of "#!/usr/local/bin/python" for scripts, since the former works no matter where python is installed. I understand that some of the perl installation scripts use the same trick. Even cooler - at least as far as I'm concerned - is that you can do this if your interpreter is a script. That is, where "#!/usr/local/bin/foobar" won't work because foobar is a Perl script, "#!/usr/bin/env foobar" will work just fine. This is documented on the env man page, though I don't think it's been MFC'ed yet. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 0:26:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from phaidor.thuvia.org (thuvia.demon.co.uk [193.237.34.248]) by hub.freebsd.org (Postfix) with ESMTP id 5C3EF37B405 for ; Mon, 4 Jun 2001 00:26:50 -0700 (PDT) (envelope-from mark@thuvia.demon.co.uk) Received: from dotar-sojat.thuvia.org (dotar-sojat.thuvia.org [10.0.0.4]) by phaidor.thuvia.org (8.11.3/8.11.3) with ESMTP id f547Qjm00802; Mon, 4 Jun 2001 08:26:45 +0100 (BST) (envelope-from mark@dotar-sojat.thuvia.org) Received: (from mark@localhost) by dotar-sojat.thuvia.org (8.11.3/8.11.3) id f547QqB65305; Mon, 4 Jun 2001 08:26:52 +0100 (BST) (envelope-from mark) Date: Mon, 4 Jun 2001 08:26:52 +0100 (BST) From: Mark Valentine Message-Id: <200106040726.f547QqB65305@dotar-sojat.thuvia.org> In-Reply-To: Mike Meyer's message of Jun 4, 6:21am X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: mwm@mired.org (Mike Meyer), "Andrew Reilly" Subject: Re: Fixing documented bug in env(1) Cc: Peter Seebach , hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > From: mwm@mired.org (Mike Meyer) > Date: Mon 4 Jun, 2001 > Subject: Re: Fixing documented bug in env(1) > "#!/usr/bin/env foobar" will work just fine. At the mercy of the user's path... Cheers, Mark. -- Mark Valentine, Thuvia Labs "Tigers will do ANYTHING for a tuna fish sandwich." Mark Valentine uses "We're kind of stupid that way." *munch* *munch* and endorses FreeBSD -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 0:38:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 81FC337B401 for ; Mon, 4 Jun 2001 00:38:26 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 5895 invoked by uid 100); 4 Jun 2001 07:38:25 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15131.15089.582662.703761@guru.mired.org> Date: Mon, 4 Jun 2001 02:38:25 -0500 To: Mark Valentine Cc: "Andrew Reilly" , Peter Seebach , hackers@freebsd.org Subject: Re: Fixing documented bug in env(1) In-Reply-To: <200106040726.f547QqB65305@dotar-sojat.thuvia.org> References: <200106040726.f547QqB65305@dotar-sojat.thuvia.org> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mark Valentine types: > > From: mwm@mired.org (Mike Meyer) > > Date: Mon 4 Jun, 2001 > > Subject: Re: Fixing documented bug in env(1) > > > "#!/usr/bin/env foobar" will work just fine. > At the mercy of the user's path... If you're really worried about that, do "#!/usr/bin/env /usr/local/bin/foobar". That will also work where "#!/usr/local/bin/foobar" won't. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 8:45: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 889D537B403 for ; Mon, 4 Jun 2001 08:45:02 -0700 (PDT) (envelope-from krepel@fokus.gmd.de) Received: from fokus.gmd.de (quant [193.175.133.183]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id RAA24374; Mon, 4 Jun 2001 17:45:00 +0200 (MET DST) Message-ID: <3B1BACFC.A3F2FF44@fokus.gmd.de> Date: Mon, 04 Jun 2001 17:45:00 +0200 From: Falco Krepel Organization: GMD FOKUS - CATS Group X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en, de-DE MIME-Version: 1.0 To: andrew@werple.apana.org.au Cc: hackers@FreeBSD.org Subject: cyclades Cyclom-8Ys card with newer firmware Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello Andrew, I want to use the Cyclom-8Ys card for a console server (with FreeBSD 5.0). But the driver doesn't work. First I get the error "No ports found". After debugging I found the problem. You check in cy.c in the function cy_units() the firmware version. If the firmware is between 0x40-0x4F no problem occur but my card has the firmware version 0x91. I make a strait forward approach and comment out that if-statement. I get no error message but when I try to connect to the port with kermit than I get a timeout message "channel command timeout (5001 usec)" from the function cd1400_channel_cmd_wait(). Do you have any idea what the problem may be? Thanx, Falco Krepel -- Falco Krepel Phone: +49-(0)30 - 34 63 - 7 276 GMD-FOKUS Fax: +49-(0)30 - 34 63 - 8 276 Kaiserin-Augusta-Allee 31 e-mail: krepel@fokus.gmd.de 10589 Berlin WWW: http://www.fokus.gmd.de/usr/krepel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 11:10:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id B479B37B408 for ; Mon, 4 Jun 2001 11:10:12 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f54I9pG17019; Mon, 4 Jun 2001 11:09:51 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200106030445.f534jTA07246@earth.backplane.com> Date: Mon, 04 Jun 2001 11:09:55 -0700 (PDT) From: John Baldwin To: Matt Dillon Subject: RE: Patch to fix code that kills procs when swap runs out (stabl Cc: Alfred Perlstein , hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 03-Jun-01 Matt Dillon wrote: > Alfred, I'm cc'ing you. If you have some time, could you check the > vmspace_swap_count() routine? What do I need to mutex it for -current? > For -stable I don't think there's an issue since VM objects are not > instantiated/destroyed by interrupts. > > All suggestions are welcome. Barring whatever Alfred says, it looks like you don't need any additional locking as we already hold the vm mutex by the time we get to that point in swapout_procs(). -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 11:57: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from idiom.com (idiom.com [216.240.32.1]) by hub.freebsd.org (Postfix) with ESMTP id 4C9DD37B403 for ; Mon, 4 Jun 2001 11:57:04 -0700 (PDT) (envelope-from rdm@cfcl.com) Received: from cfcl.com (cpe-24-221-169-54.ca.sprintbbd.net [24.221.169.54]) by idiom.com (8.9.3/8.9.3) with ESMTP id LAA37050 for ; Mon, 4 Jun 2001 11:57:03 -0700 (PDT) Received: from [192.168.168.205] (cerberus [192.168.168.205]) by cfcl.com (8.11.1/8.11.1) with ESMTP id f54IwbK19976 for ; Mon, 4 Jun 2001 11:58:37 -0700 (PDT) (envelope-from rdm@cfcl.com) Mime-Version: 1.0 Message-Id: Date: Mon, 4 Jun 2001 11:50:56 -0700 To: hackers@FreeBSD.ORG From: Rich Morin Subject: speeding up /etc/security Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG /etc/security takes a number of hours to run on my system. The problem is that I have some very large mounted file systems and the code to look for setuid files wants to walk through them all. I recoded the check in Perl, but it ran at about the same speed. I have considered reworking the code to do the file systems in parallel, but I thought I should ask here first. Comments? Suggestions? -r -- http://www.cfcl.com/rdm - home page, resume, etc. http://www.cfcl.com/Meta/md_fb.html - The FreeBSD Browser email: rdm@cfcl.com; phone: +1 650-873-7841 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 12: 7:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id CACD437B401 for ; Mon, 4 Jun 2001 12:07:43 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo.feral.com [192.67.166.71]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f54J7Jg80136; Mon, 4 Jun 2001 12:07:19 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Mon, 4 Jun 2001 12:07:19 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Rich Morin Cc: hackers@FreeBSD.ORG Subject: Re: speeding up /etc/security In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG That's an interesting question. A couple of ideas: a) I wonder of RWatson's ACL stuff could help here? b) This problem cries for a DMAPI type solution- you could have a daemon that monitors all creats/chmods and retains knowledge of the filenames for all SUID/SGID creats/chmods- this way /etc/security would simply summarize the current list and could be run any time. > /etc/security takes a number of hours to run on my system. The problem > is that I have some very large mounted file systems and the code to look > for setuid files wants to walk through them all. I recoded the check in > Perl, but it ran at about the same speed. I have considered reworking > the code to do the file systems in parallel, but I thought I should ask > here first. Comments? Suggestions? > > -r > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 12:13:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 175FD37B403 for ; Mon, 4 Jun 2001 12:13:13 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.22 #1) id 156zmp-0002oe-00; Mon, 04 Jun 2001 19:13:11 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.3/8.11.2) id f54JJ9l01154; Mon, 4 Jun 2001 21:19:09 +0200 (CEST) (envelope-from wkb) Date: Mon, 4 Jun 2001 21:19:09 +0200 From: Wilko Bulte To: Matthew Jacob Cc: Rich Morin , hackers@freebsd.org Subject: Re: speeding up /etc/security Message-ID: <20010604211909.B1112@freebie.demon.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Mon, Jun 04, 2001 at 12:07:19PM -0700 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jun 04, 2001 at 12:07:19PM -0700, Matthew Jacob wrote: Does /etc/security take filesystem mounted with: nosuid Do not allow set-user-identifier or set-group-identifier bits to take effect. Note: this option is worthless if a public available suid or sgid wrapper like suidperl(1) is installed on your system. into account? If so, and the filesystems have nothing on them that needs suid you could mount 'm this way Just a thought, Wilko > That's an interesting question. > > A couple of ideas: > > a) I wonder of RWatson's ACL stuff could help here? > > b) This problem cries for a DMAPI type solution- you could have a daemon that > monitors all creats/chmods and retains knowledge of the filenames for all > SUID/SGID creats/chmods- this way /etc/security would simply summarize the > current list and could be run any time. > > > /etc/security takes a number of hours to run on my system. The problem > > is that I have some very large mounted file systems and the code to look > > for setuid files wants to walk through them all. I recoded the check in > > Perl, but it ran at about the same speed. I have considered reworking > > the code to do the file systems in parallel, but I thought I should ask > > here first. Comments? Suggestions? > > > > -r > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message ---end of quoted text--- -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte Powered by FreeBSD/[alpha,x86] http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 12:25:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tabby.sonn.com (tabby.sonn.com [206.79.239.6]) by hub.freebsd.org (Postfix) with ESMTP id D035D37B401 for ; Mon, 4 Jun 2001 12:25:22 -0700 (PDT) (envelope-from gersh@tabby.sonn.com) Received: from localhost (gersh@localhost) by tabby.sonn.com (8.9.3/8.9.3) with ESMTP id MAA32393; Mon, 4 Jun 2001 12:36:08 -0700 (PDT) Date: Mon, 4 Jun 2001 12:36:08 -0700 (PDT) From: Gersh To: Matthew Jacob Cc: Rich Morin , hackers@FreeBSD.ORG Subject: Re: speeding up /etc/security In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG What about something like what process accounting does? It would be trivial to update a file (say /var/db/setxid) whenever certian chmod / fchmod actions are taken. If it only happened when chmod/fchmod actions happened that effected setxid stauts it should not impact performence to much either IMHO. I think that the real thing to consid with a approach like this is. 1) How useful would it be. 2) Because it would be used for something security relevant the "database" file would need to remain secure at all times. On Mon, 4 Jun 2001, Matthew Jacob wrote: > > That's an interesting question. > > A couple of ideas: > > a) I wonder of RWatson's ACL stuff could help here? > > b) This problem cries for a DMAPI type solution- you could have a daemon that > monitors all creats/chmods and retains knowledge of the filenames for all > SUID/SGID creats/chmods- this way /etc/security would simply summarize the > current list and could be run any time. > > > /etc/security takes a number of hours to run on my system. The problem > > is that I have some very large mounted file systems and the code to look > > for setuid files wants to walk through them all. I recoded the check in > > Perl, but it ran at about the same speed. I have considered reworking > > the code to do the file systems in parallel, but I thought I should ask > > here first. Comments? Suggestions? > > > > -r > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 12:54:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 5B90537B401 for ; Mon, 4 Jun 2001 12:54:30 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (mjacob@beppo [192.67.166.79]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f54JsNg80223; Mon, 4 Jun 2001 12:54:23 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Mon, 4 Jun 2001 12:54:23 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Gersh Cc: Rich Morin , hackers@FreeBSD.ORG Subject: Re: speeding up /etc/security In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Let me turn it around and say that process accounting should be only one of a set of actions that can be emitted from the kernel and recorded somewhere. On Mon, 4 Jun 2001, Gersh wrote: > What about something like what process accounting does? > > It would be trivial to update a file (say /var/db/setxid) > whenever certian chmod / fchmod actions are taken. > > If it only happened when chmod/fchmod actions happened that > effected setxid stauts it should not impact performence to much either > IMHO. > > I think that the real thing to consid with a approach like this is. > > 1) How useful would it be. > 2) Because it would be used for something security relevant the > "database" file would need to remain secure at all times. > > On Mon, 4 Jun 2001, Matthew Jacob wrote: > > > > > That's an interesting question. > > > > A couple of ideas: > > > > a) I wonder of RWatson's ACL stuff could help here? > > > > b) This problem cries for a DMAPI type solution- you could have a daemon that > > monitors all creats/chmods and retains knowledge of the filenames for all > > SUID/SGID creats/chmods- this way /etc/security would simply summarize the > > current list and could be run any time. > > > > > /etc/security takes a number of hours to run on my system. The problem > > > is that I have some very large mounted file systems and the code to look > > > for setuid files wants to walk through them all. I recoded the check in > > > Perl, but it ran at about the same speed. I have considered reworking > > > the code to do the file systems in parallel, but I thought I should ask > > > here first. Comments? Suggestions? > > > > > > -r > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 13:16:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.skynet.cz (ns.skynet.cz [193.165.192.9]) by hub.freebsd.org (Postfix) with ESMTP id 73C8E37B405; Mon, 4 Jun 2001 13:16:29 -0700 (PDT) (envelope-from dolecek@saruman.ics.muni.cz) Received: from saruman.ics.muni.cz (asasync80.skynet.cz [193.165.192.180]) by ns.skynet.cz (8.9.3/8.9.2) with ESMTP id WAA84108; Mon, 4 Jun 2001 22:16:22 +0200 (CEST) (envelope-from dolecek@saruman.ics.muni.cz) Received: (from dolecek@localhost) by saruman.ics.muni.cz (8.11.4/8.10.1) id f54KIAV00619; Mon, 4 Jun 2001 22:18:10 +0200 (CEST) From: Jaromír Dolecek Message-Id: <200106042018.f54KIAV00619@saruman.ics.muni.cz> Subject: pipe implementation questions To: hackers@freebsd.org Date: Mon, 4 Jun 2001 22:18:10 +0200 (CEST) Cc: alfred@freebsd.org X-Mailer: ELM [version 2.4ME+ PL78 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi folks, I'm working on a port of FreeBSD pipe implementation to NetBSD. So far, the results are pretty owesame, the new pipes are significantly faster than the old socketpair-based ones. Good work! However, I found couple of things I don't quite understand and would like to clarify if this is how things are supposed to work or if I'm consfused :) 1) SIGIO for O_ASYNC reader, sync writer I made a test program which makes a pipe, sets owner of the read end, setup signal handler for SIGIO and switches the read end to O_NONBLOCK|O_ASYNC mode. Program forks, child makes sync write to the write (synchronous) end of pipe. When parents loops calling read() on the read end until it succeeds. However, I found out the parent gets SIGIO for each read(2) attempt. This behaviour seems to be due to last couple of lines of pipe_read(): if ((rpipe->pipe_buffer.size - rpipe->pipe_buffer.cnt) >= PIPE_BUF) pipeselwakeup(rpipe); This condition is commonly true if the reader is polling for input. The code should signal the writer, not the reader - it doesn't make sense to signal possibility of writing more data to the reader itself. IMHO the code should be like: if ((rpipe->pipe_buffer.size - rpipe->pipe_buffer.cnt) >= PIPE_BUF) { struct pipe *wpipe = rpipe->pipe_peer; if (wpipe) pipeselwakeup(wpipe); } Also, the code could possibly only call the pipeselwakeup() if anything was actually read from the pipe previously (or, even better, only once since last write(2)), to avoid sending SIGIO's to the writer if the the reader found the pipe empty. 2) direct write - first uio only FreeBSD direct write code seems to handle only first uio buffer, so e.g. writev(2) with multiple buffers doesn't write all data at once. This is valid behaviour (return short write and expect writer to update itself and try again with rest), I'd like just to ensure I read the code correctly. 3) direct write - loses for huge buffers? It seems pipe_build_write_buffer() tries to fault all the address space specified by uio. However, pipe_map.ms[] has only (BIG_PIPE_SIZE/PAGE_SIZE+1) members, so this seems to lose if the covered address space (size of buffer passed to write(2)) is > 64+4=68KB. Also, the code which calls pmap_qenter() thinks the buffer size is wpipe->pipe_buffer.size + PAGE_SIZE maximum. Do I read the code correctly, or is there anything I miss? The current port to NetBSD doesn't use this particular piece of code (the difference between FreeBSD VM and UVM is too big), but it's something I encountered and would like to understand :) Thanks for you cooperation :) Jaromir P.S. Please CC: me, I'm not on the list -- Jaromir Dolecek http://www.ics.muni.cz/~dolecek/ NetBSD - just plain best OS! -=*=- Got spare MCA cards or docs? Hand me them! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 14:48:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id AA40C37B401 for ; Mon, 4 Jun 2001 14:48:38 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.3/8.11.3) with ESMTP id f54Lmal50719; Mon, 4 Jun 2001 22:48:37 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.3/8.11.3) with ESMTP id f54Lma209767; Mon, 4 Jun 2001 22:48:36 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200106042148.f54Lma209767@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Wilko Bulte Cc: Matthew Jacob , Rich Morin , hackers@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: speeding up /etc/security In-Reply-To: Message from Wilko Bulte of "Mon, 04 Jun 2001 21:19:09 +0200." <20010604211909.B1112@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Jun 2001 22:48:36 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG As you suspect, mounting nosuid makes /etc/security skip the suid checks... good for giving the security-unconscious a reason to fix their system :) I was alway quite impressed with this :) > On Mon, Jun 04, 2001 at 12:07:19PM -0700, Matthew Jacob wrote: > > Does /etc/security take filesystem mounted with: > > nosuid Do not allow set-user-identifier or set-group-identifier > bits to take effect. Note: this option is worthless if a > public available suid or sgid wrapper like suidperl(1) > is installed on your system. > > into account? If so, and the filesystems have nothing on them that > needs suid you could mount 'm this way > > Just a thought, > > Wilko > > > That's an interesting question. > > > > A couple of ideas: > > > > a) I wonder of RWatson's ACL stuff could help here? > > > > b) This problem cries for a DMAPI type solution- you could have a daemon that > > monitors all creats/chmods and retains knowledge of the filenames for all > > SUID/SGID creats/chmods- this way /etc/security would simply summarize the > > current list and could be run any time. > > > > > /etc/security takes a number of hours to run on my system. The problem > > > is that I have some very large mounted file systems and the code to look > > > for setuid files wants to walk through them all. I recoded the check in > > > Perl, but it ran at about the same speed. I have considered reworking > > > the code to do the file systems in parallel, but I thought I should ask > > > here first. Comments? Suggestions? > > > > > > -r > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > ---end of quoted text--- > > -- > | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org > |/|/ / / /( (_) Bulte Powered by FreeBSD/[alpha,x86] http://www.freebsd.org -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 16: 8:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from idiom.com (idiom.com [216.240.32.1]) by hub.freebsd.org (Postfix) with ESMTP id AA52A37B401 for ; Mon, 4 Jun 2001 16:08:29 -0700 (PDT) (envelope-from rdm@cfcl.com) Received: from cfcl.com (cpe-24-221-169-54.ca.sprintbbd.net [24.221.169.54]) by idiom.com (8.9.3/8.9.3) with ESMTP id QAA80697 for ; Mon, 4 Jun 2001 16:08:29 -0700 (PDT) Received: from [192.168.168.205] (cerberus [192.168.168.205]) by cfcl.com (8.11.1/8.11.1) with ESMTP id f54NA4K76854 for ; Mon, 4 Jun 2001 16:10:04 -0700 (PDT) (envelope-from rdm@cfcl.com) Mime-Version: 1.0 Message-Id: In-Reply-To: <200106042148.f54Lma209767@hak.lan.Awfulhak.org> References: <200106042148.f54Lma209767@hak.lan.Awfulhak.org> Date: Mon, 4 Jun 2001 15:46:17 -0700 To: hackers@FreeBSD.ORG From: Rich Morin Subject: Re: speeding up /etc/security Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 10:48 PM +0100 6/4/01, Brian Somers wrote: >As you suspect, mounting nosuid makes /etc/security skip the >suid checks... good for giving the security-unconscious a reason >to fix their system :) Works for me... -r -- email: rdm@cfcl.com; phone: +1 650-873-7841 http://www.cfcl.com/rdm - home page, resume, etc. http://www.cfcl.com/Meta/md_fb.html - The FreeBSD Browser http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 17:12:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 496DD37B401 for ; Mon, 4 Jun 2001 17:12:10 -0700 (PDT) (envelope-from kway@overtone.org) Received: from bean.overtone.org (user-2inimal.dialup.mindspring.com [165.121.89.85]) by falcon.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id RAA13996; Mon, 4 Jun 2001 17:08:36 -0700 (PDT) Received: by bean.overtone.org (Postfix, from userid 1001) id BD734317F; Mon, 4 Jun 2001 20:08:28 -0400 (EDT) Date: Mon, 4 Jun 2001 20:08:28 -0400 From: Kevin Way To: Wilko Bulte Cc: hackers@FreeBSD.ORG Subject: Re: speeding up /etc/security Message-ID: <20010604200828.A41130@bean.overtone.org> References: <20010604211909.B1112@freebie.demon.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="vkogqOf2sHV7VnPd" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010604211909.B1112@freebie.demon.nl>; from wkb@freebie.demon.nl on Mon, Jun 04, 2001 at 09:19:09PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --vkogqOf2sHV7VnPd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > Does /etc/security take filesystem mounted with: >=20 > nosuid Do not allow set-user-identifier or set-group-identifier > bits to take effect. Note: this option is worthless if a > public available suid or sgid wrapper like suidperl(1) > is installed on your system. >=20 > into account? If so, and the filesystems have nothing on them that > needs suid you could mount 'm this way The answer there is 'sort of'. /etc/security checks all ufs partitions that aren't marked nosuid. if you're using anything other than UFS (e.g. MFS,ext2,whatever), it's not getting checked at all. Kevin Way --vkogqOf2sHV7VnPd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7HCL8KxA01iDoLN4RAp9iAKC8iY8ntiS/MNS71qEFLPim0KLTyACdG/wO GexMs5Y/r4IxSYaAy4RN2p0= =gKsn -----END PGP SIGNATURE----- --vkogqOf2sHV7VnPd-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 17:17:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.unik.no (odin.unik.no [193.156.96.7]) by hub.freebsd.org (Postfix) with ESMTP id 9278737B403 for ; Mon, 4 Jun 2001 17:17:07 -0700 (PDT) (envelope-from andreasd@unik.no) Received: from r2d2.unik.no ([193.156.96.39]) by odin.unik.no with esmtp (Exim 3.16 #2) id 1574WK-0003Yl-00 for hackers@freebsd.org; Tue, 05 Jun 2001 02:16:28 +0200 Received: from andreasd by r2d2.unik.no with local (Exim 3.16 #3) id 1574Wq-000CbW-00 for hackers@freebsd.org; Tue, 05 Jun 2001 02:17:00 +0200 Date: Tue, 5 Jun 2001 02:17:00 +0200 From: "Andreas Dobloug; UiO; H98" To: hackers@freebsd.org Subject: Re: background_fsck rc.conf option Message-ID: <20010605021700.A48407@r2d2.unik.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ---- Index: etc/rc =================================================================== RCS file: /stl/src/FreeBSD/src/etc/rc,v retrieving revision 1.264 diff -u -r1.264 rc --- etc/rc 2001/05/13 20:43:30 1.264 +++ etc/rc 2001/05/21 00:19:25 @@ -184,9 +184,14 @@ case ${bootmode} in autoboot) echo 'Automatic boot in progress...' -# To restore old fsck behavior use: -# fsck -p - fsck -F -p + case ${background_fsck} in + [Yy][Ee][Ss]) + fsck -F -p [..] ---- This patch doesn't work on boxes with nfs/msdos mounts... I suggest adding "-t no,nfs,msdos,ntfs" to the parameter list. -- Andreas Dobloug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 17:46:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from enterprise.spock.org (cm-24-29-85-81.nycap.rr.com [24.29.85.81]) by hub.freebsd.org (Postfix) with ESMTP id A8AB237B401 for ; Mon, 4 Jun 2001 17:46:22 -0700 (PDT) (envelope-from jon@enterprise.spock.org) Received: (from jon@localhost) by enterprise.spock.org serial EF600Q3T-B7F8823f550kLW08639F7T for hackers@FreeBSD.ORG; Mon, 4 Jun 2001 20:46:21 -0400 (EDT) (envelope-from jon) Date: Mon, 4 Jun 2001 20:46:21 -0400 From: Jonathan Chen To: hackers@FreeBSD.ORG Subject: Resource reservation idea Message-ID: <20010604204621.A2023@enterprise.spock.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: telnet/1.1x Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Currently on FreeBSD, resources are either free, allocated or activated. As I understand it, they mean approximately the following: - Free: unused. - Allocated: Resource reserved for use by device X. - Activated: Resource actively used by device X. This leaves somewhat of a gap. What if bus Y wants to reserve some resource for an attached hardware, but the driver of the hardware does not exist (yet)? Currently, I can think of two ways this can be done: - Have the bus allocate the resource, then hand it off to the child if/when it requests it. From my experience with cardbus, this can get messy and each bus has to implement its own resource management. - Some dummy driver which grabs the resource. The dummy driver would need to be unloaded when the actual driver needs the resources. What I propose is this -- implement a new set of bus functions bus_reserve_resource(), with the following parameters: device_t parent, device_t bus, int type, u_long start, u_long end, u_int flags [I don't believe a resource id is necessary or desirable. Consider the case where a child might reserve a range in the middle of what the parent has reserved, thereby splitting the original reservation into three, rendering the rid's messed up.] The core functions can be implemented at the nexus level with the default function passing the hat to its parent. The nexus reserve functions would have the following properties: - If resource specified is free, reserve it to the bus. - If resource specified is (partially) allocated/activated by anything other than the bus's immediate child, return error. - If resource specified is (partially) already reserved, and - requested resource is completely reserved to any parent, change reservation to new device. - otherwise, fail. One flag might be RF_DEFAULT_RANGE, where child devices to that bus with automatically try to use something within that range if the resource range is not explicitly specified. bus_unreserve_resource() would simply remove the reservation for all resources within the specified range that is reserved to the bus, regardless of whether the resource is currently allocated. It would have the following parameters: device_t parent, device_t bus, int type, u_long start, u_long end There would also need to be changes in the nexus alloc_resource() functions, as follows: - If resource range is not explicitly specified, try allocation within default range. If entire resource does not fit, try fitting as much as possible. - If resource range is explicitly specified, check if any portion of the resource is reserved. If any portion of the resource is reserved to anything other than the device's immediate parent, return error. The proposed changes above should not require changes to existing bus codes to maintain compatibility. Only minimal changes should be required to take advantage of this. An alternative to this system is to provide some interface to easily hand-off resources from a bus to its child. While this will work for most cases, it does not provide functionality for a case where a bus might want to reserve a range to eventually dish out to various different children. Please comment on the necessity, portability, interface, functionality (or whatever else you can think of) of what is described here. If all goes well, I hope to have some initial implementation in not too long. On a side note, I just thought of something -- should PCI bus numbers be treated as a resource too? -- (o_ 1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2 _o) \\\_\ Jonathan Chen jon@freebsd.org /_/// <____) No electrons were harmed during production of this message (____> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 18:49:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id EECAF37B401; Mon, 4 Jun 2001 18:49:12 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f551wmL06759; Mon, 4 Jun 2001 18:58:48 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106050158.f551wmL06759@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jonathan Chen Cc: hackers@FreeBSD.ORG Subject: Re: Resource reservation idea In-reply-to: Your message of "Mon, 04 Jun 2001 20:46:21 EDT." <20010604204621.A2023@enterprise.spock.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Jun 2001 18:58:48 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Currently on FreeBSD, resources are either free, allocated or activated. > As I understand it, they mean approximately the following: > - Free: unused. > - Allocated: Resource reserved for use by device X. > - Activated: Resource actively used by device X. > > This leaves somewhat of a gap. What if bus Y wants to reserve some > resource for an attached hardware, but the driver of the hardware does > not exist (yet)? Currently, I can think of two ways this can be done: > - Have the bus allocate the resource, then hand it off to the child > if/when it requests it. From my experience with cardbus, this can > get messy and each bus has to implement its own resource management. This is how I'm doing it in the new PCI code; since PCI devices actually have these resources assigned whether a device happens to be using them or not, this is a good match. With Cardbus, you should be allocating the resources when the card arrives, then hand them off to the driver, and release them when the card goes away. This model works quite well; a resource is typically either extant and decoded, or not extant at all. The grey cases are already reasonablly well handled (multiple ownership, allocated vs. active, etc.) Resource lists make handling this fairly easy. > - Some dummy driver which grabs the resource. The dummy driver would > need to be unloaded when the actual driver needs the resources. This sounds attractive, but it's hard to find the dummy driver when you want to open the bidding for one or more devices again. You also end up with the ugly case where the device has more resources than the driver uses; you end up needing a placeholder of some sort for these as well, so you might as well just built it into the way the bus thinks about child devices and be done with it. > What I propose is this -- implement a new set of bus functions > bus_reserve_resource(), with the following parameters: I don't see that these are actually necessary. The current model works just fine. > An alternative to this system is to provide some interface to easily > hand-off resources from a bus to its child. While this will work for > most cases, it does not provide functionality for a case where a bus > might want to reserve a range to eventually dish out to various > different children. Typically, a bus isn't going to "reserve a range" in the fashion you describe. It should just request the resources it wants, and let the bridge above it (and potentially the series of bridges above it) sort out what range(s) are appropriate. In most cases, a bus really isn't going to know in advance what sort of resources it might need to assign to its children, so second-guessing will lead to suboptimal behaviour. > On a side note, I just thought of something -- should PCI bus numbers be > treated as a resource too? Yes; at least, a PCI device should be able to request a PCI bus number range. This is necessary for configuring unconfigured PCI:PCI bridges. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 19:44:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 1A88737B407 for ; Mon, 4 Jun 2001 19:44:10 -0700 (PDT) (envelope-from kway@overtone.org) Received: from bean.overtone.org (user-2inimal.dialup.mindspring.com [165.121.89.85]) by falcon.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id TAA26320; Mon, 4 Jun 2001 19:44:05 -0700 (PDT) Received: by bean.overtone.org (Postfix, from userid 1001) id 22DFE32B2; Mon, 4 Jun 2001 22:44:06 -0400 (EDT) Date: Mon, 4 Jun 2001 22:44:05 -0400 From: Kevin Way To: Kevin Way Cc: wkb@freebie.demon.nl, hackers@freebsd.org Subject: Re: speeding up /etc/security Message-ID: <20010604224405.A43677@bean.overtone.org> References: <20010604211909.B1112@freebie.demon.nl> <20010604200828.A41130@bean.overtone.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010604200828.A41130@bean.overtone.org>; from kevin.way@overtone.org on Mon, Jun 04, 2001 at 08:08:28PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > The answer there is 'sort of'. /etc/security checks all ufs partitions > that aren't marked nosuid. if you're using anything other than UFS > (e.g. MFS,ext2,whatever), it's not getting checked at all. i hate to followup to my own message, but in order for the SUID checks to be accurate, is there a reson we don't do something like the following? --- security.orig Mon Jun 4 22:26:01 2001 +++ security Mon Jun 4 22:31:47 2001 @@ -69,7 +69,7 @@ # Note that one of the original problems, the possibility of overrunning # the args to ls, is still here... # -MP=`mount -t ufs | grep -v " nosuid" | awk '{ print $3 }' | sort` +MP=`( mount -t cd9660; mount -t ext2fs; mount -t ffs; mount -t ifs; mount -t lfs; mount -t mfs; mount -t ufs ) | grep -v ' nosuid' | awk '{ print $3 }' | sort` set ${MP} while [ $# -ge 1 ]; do mount=$1 -Kevin Way --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7HEd1KxA01iDoLN4RAtgvAKCB8IEZzjJ0NHKNMWEF0yHEYgFR1wCeLGy5 MuGf6b4UvcMMha1qz7HwpWQ= =SYCQ -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jun 4 19:46:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 5C41A37B406; Mon, 4 Jun 2001 19:46:19 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id C27003E31; Mon, 4 Jun 2001 19:46:18 -0700 (PDT) To: hackers@freebsd.org Cc: phk@freebsd.org Subject: MFC'ing new md(4) functionality? Date: Mon, 04 Jun 2001 19:46:18 -0700 From: Dima Dorfman Message-Id: <20010605024618.C27003E31@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is there any reason not to MFC the new md(4) functionality (i.e., swap and vnode support)? With MFS and vn(4) gone in -current, I think that the sooner users can start moving to md(4) in -stable the less cries there will be come 5.0-RELEASE. Additionally, the porting effort is not that great. mdconfig(8) and mdioctl.h aren't in -stable so those can be brought over verbatim, and the only changes to md.c itself are bio->buf stuff, and some added spl's. I've put the diff for the latter against -stable at http://www.unixfreak.org/~dima/home/mdmfc.diff. If someone wants a diff between that and -current for review let me know and I'll generate one. I'm also willing to do the actual merges if no one else has time, so the question raised in the first paragraph remains: is there any reason not to do this? Thanks in advance, Dima Dorfman dima@unixfreak.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 1:30:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Exchange2000.com-con.ag (exchange2000.com-con.net [212.6.164.8]) by hub.freebsd.org (Postfix) with ESMTP id D325337B405 for ; Tue, 5 Jun 2001 01:30:27 -0700 (PDT) (envelope-from rh@com-con.net) Content-Class: urn:content-classes:message Subject: security log file parser / ids MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Tue, 5 Jun 2001 10:30:26 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: security log file parser / ids Thread-Index: AcDtoVoNIzbBRx6KQpGCdqF8vL9w9w== From: "Heimes, Rene" To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hiho! i am searching for a parser that parses security logs from ipfw-made up logs. anyone got a hint? (btw: what about ipfw firewalls - outdated? what would be better? ipchains? help!) other question - whats the (freeware) ids of your choice / "state of the art" for freeBSD? great thanks in advance, ren=E9 **************************************************** "who fights might loose - who does not fight has lost immediately" Bertolt Brecht (freely adapted ;-) **************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 1:32: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 454C637B403; Tue, 5 Jun 2001 01:32:04 -0700 (PDT) (envelope-from obrien@nuxi.ucdavis.edu) Received: from dragon.nuxi.com (root@trang.nuxi.com [206.40.252.115]) by relay.nuxi.com (8.11.2/8.11.2) with ESMTP id f558W3l99141; Tue, 5 Jun 2001 01:32:03 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f558VxQ49284; Tue, 5 Jun 2001 01:31:59 -0700 (PDT) (envelope-from obrien) Date: Tue, 5 Jun 2001 01:31:49 -0700 From: "David O'Brien" To: Dima Dorfman Cc: hackers@freebsd.org, phk@freebsd.org Subject: Re: MFC'ing new md(4) functionality? Message-ID: <20010605013148.A49246@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010605024618.C27003E31@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010605024618.C27003E31@bazooka.unixfreak.org>; from dima@unixfreak.org on Mon, Jun 04, 2001 at 07:46:18PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote: > Is there any reason not to MFC the new md(4) functionality Zero reason not to. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 2:57: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from newsguy.com (perry.pathlink.com [209.155.233.33]) by hub.freebsd.org (Postfix) with ESMTP id EF91D37B401 for ; Tue, 5 Jun 2001 02:56:58 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (ppp045-bsace7001.telebrasilia.net.br [200.181.80.45]) by newsguy.com (8.11.0/8.9.1) with ESMTP id f559trq79032; Tue, 5 Jun 2001 02:55:54 -0700 (PDT) Message-ID: <3B1CACDA.96599BD5@newsguy.com> Date: Tue, 05 Jun 2001 06:56:42 -0300 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en,pt-BR,pt,en-GB,en-US,ja MIME-Version: 1.0 To: Giorgos Keramidas Cc: Bob Willcox , Jesper Skriver , hackers list Subject: Re: How to disable software TCP checksumming? References: <20010529144114.I19771@luke.immure.com> <20010529221107.C49875@skriver.dk> <20010529155212.M19771@luke.immure.com> <20010530045200.A1031@hades.hell.gr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Giorgos Keramidas wrote: > > There are good reasons why checksumming in upper layers should not be disabled > even if some lower layer does checksumming of its own. I recall reading some > good points on this one at "TCP/IP Illustrated, Volume I" from (now late) > Richard W. Stevens. It seems to me to be kind of moot to check the same value twice, unless you suspect hardware problems. Aren't you talking about two different checks over the same data instead of checksum off-loading? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net wow regex humor... I'm a geek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 3:24:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.khmere.com (sdsl-216-36-70-194.dsl.sjc.megapath.net [216.36.70.194]) by hub.freebsd.org (Postfix) with ESMTP id B9A3B37B403; Tue, 5 Jun 2001 03:24:11 -0700 (PDT) (envelope-from list@khmere.com) Received: from khmere.com (ns2.khmere.com [216.36.70.196]) by ns1.khmere.com (8.11.3/8.8.7) with ESMTP id f55AO9O71735; Tue, 5 Jun 2001 03:24:09 -0700 (PDT) Message-ID: <3B1CB347.DAC04203@khmere.com> Date: Tue, 05 Jun 2001 03:24:07 -0700 From: Nathan X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: documentation help, installation and the swap partition Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am trying to document how the partitions are laid out in FreeBSD and I have noticed that the installation will place the sector offsets of the b (swap) partition before the last partition. And will also place the sector offsets of the largest partition as the last regardless to its name (ie: d or h) The question is why ? is it due to performance reasons ? or safety ? or other ? I have looked for specific documentation on this but I can't seem to find it. thanks in advance ! -nb here is an example: # size offset fstype [fsize bsize bps/cpg] a: 262144 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 260*) ######swap partition sectors start right befiore the d partitions sectors ######## b: 1048576 18087936 swap # (Cyl. 17944*- 18984*) c: 60036417 0 unused 0 0 # (Cyl. 0 - 59559*) ###### d is the last in sectors but, the 3rd usable partition (a, b, d ) ####### d: 40899905 19136512 4.2BSD 1024 8192 16 # (Cyl. 18984*- 59559*) e: 524288 262144 4.2BSD 1024 8192 16 # (Cyl. 260*- 780*) f: 524288 786432 4.2BSD 1024 8192 16 # (Cyl. 780*- 1300*) g: 8388608 1310720 4.2BSD 1024 8192 16 # (Cyl. 1300*- 9622*) h: 8388608 9699328 4.2BSD 1024 8192 16 # (Cyl. 9622*- 17944*) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 4:17:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id B1A4637B403 for ; Tue, 5 Jun 2001 04:17:50 -0700 (PDT) (envelope-from DougB@DougBarton.net) Received: from DougBarton.net (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id EAA23454 for ; Tue, 5 Jun 2001 04:17:50 -0700 (PDT) (envelope-from DougB@DougBarton.net) Message-ID: <3B1CBFDE.A16162E5@DougBarton.net> Date: Tue, 05 Jun 2001 04:17:50 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: (Interesting?) malloc debugging project Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Since people are always saying that they want interesting projects, I thought I'd throw this one out there. The default malloc settings of AJ (man malloc for more details) have uncovered two bugs in one of my ports, xscreensaver. The port consists of a server that handles screen control, (auto)locking, random screensaver rotation, etc.; and a set of helper programs, including the preferences menu and the various seperate screensaver programs themselves. The bugs are in the preferences menu (the xscreensaver-demo binary) and the screensaver called interference. In the case of the former, the first time you start the menu it creates an .xscreensaver config file in your home directory. Usually you can run it the first time cleanly, however the second time I start it every time I click an option it cores. As far as I can tell it's overflowing one of the buffers used by the conf file parsing routine as its reading in the file, but I haven't been able to track it all the way down. The interference screensaver just dumps core as soon as it's run. It seems to be sending a bad variable to the drawrectangle function in one of the X libs, but I didn't get very far with this one either. I was able to verify that it was the J option to malloc that did the damage by doing 'ln -s j /etc/malloc.conf' then running them again. Unfortunately, I don't really have a lot of time to track these bugs down right now, so if someone wants to tackle this, I'll be grateful for the help. I have a good relationship with the author, and he's already included one of our patches into his distributed code, so I'm confident that if you find a genuine bug he'd be grateful as well. Please let me know what you find. If you want me to pass it to the author I'll be sure to give you credit, of course. You can install a debug version of the script by setting your CFLAGS in make.conf to -O -g -pipe, and doing 'make STRIP='' install' in the port directory. If you're on -stable and want to give this a try, you should be able to reproduce conditions close enough to -current by doing 'ln -s AJ /etc/malloc.conf'. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 5:11:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shade.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id D76F737B403; Tue, 5 Jun 2001 05:11:09 -0700 (PDT) (envelope-from nectar@nectar.com) Received: (from nectar@localhost) by shade.nectar.com (8.11.3/8.11.3) id f55CAuC61464; Tue, 5 Jun 2001 07:10:56 -0500 (CDT) (envelope-from nectar) Date: Tue, 5 Jun 2001 07:10:56 -0500 From: "Jacques A. Vidrine" To: Dima Dorfman Cc: hackers@freebsd.org, phk@freebsd.org Subject: Re: MFC'ing new md(4) functionality? Message-ID: <20010605071055.D30939@shade.nectar.com> References: <20010605024618.C27003E31@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010605024618.C27003E31@bazooka.unixfreak.org>; from dima@unixfreak.org on Mon, Jun 04, 2001 at 07:46:18PM -0700 X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote: > mdconfig(8) and > mdioctl.h aren't in -stable so those can be brought over verbatim, Dumb question: Can we just add a RELENG_4 tag to the files in such a case? Cheers, -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 7:23:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 20B5337B401 for ; Tue, 5 Jun 2001 07:23:39 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (#6@localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.3/8.11.3) with ESMTP id f55EM4n78505; Tue, 5 Jun 2001 10:22:05 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200106051422.f55EM4n78505@whizzo.transsys.com> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: "Daniel C. Sobral" Cc: Giorgos Keramidas , Bob Willcox , Jesper Skriver , hackers list X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: How to disable software TCP checksumming? References: <20010529144114.I19771@luke.immure.com> <20010529221107.C49875@skriver.dk> <20010529155212.M19771@luke.immure.com> <20010530045200.A1031@hades.hell.gr> <3B1CACDA.96599BD5@newsguy.com> In-reply-to: Your message of "Tue, 05 Jun 2001 06:56:42 -0300." <3B1CACDA.96599BD5@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jun 2001 10:22:04 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Giorgos Keramidas wrote: > > > > There are good reasons why checksumming in upper layers should not be disabled > > even if some lower layer does checksumming of its own. I recall reading some > > good points on this one at "TCP/IP Illustrated, Volume I" from (now late) > > Richard W. Stevens. > > It seems to me to be kind of moot to check the same value twice, unless > you suspect hardware problems. Aren't you talking about two different > checks over the same data instead of checksum off-loading? Suspect hardware problem? Of course you should! That's why memory systems have parity or ECC, and I/O buses are similarlly protected. At least on real computers. The link-level CRC only protects the data as it goes over the link between the link-level hardware which generates the CRC and the box on the other end that receives it. It does not protect the data end-to-end, so if it's gets corrupted whilst sitting in memory in an intermediate node, you won't detect that. Why would it get corrupted? 1. Software. Random unrelated other software does a random store in the buffer containing your packet sitting in memory. Fancy device drivers that do scatter-gather I/O gets it wrong every now and then and points off into space. mbuf cluster which should be treated as read-only isn't, and some other code hoses it. (See PR kern/27782 at http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27782 for an example of this.) 2. Hardware. I found broken UNIBUS hardware 15 or 20 years ago this way. I had some broken hardware which took frame relay frames on a HSSI interface and turned them into AAL5 ATM cells that would get the cell reassembly wrong if you pushed too hard. Or just plain broken memory that results in packet corruption. I've personally experienced all these problems. Maybe I'm just unluckly. One common thread of my experiences is being close to the bleeding edge of technology where stuff isn't as mature as many people are used to. This end-to-end issue is not a theoretical consideration. While the 1's complement internet checksum isn't that strong, it does detect a bunch of bug-like behavior like this. Louis Mamakos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 9: 4:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-m01.mx.aol.com (imo-m01.mx.aol.com [64.12.136.4]) by hub.freebsd.org (Postfix) with ESMTP id 10FB637B401 for ; Tue, 5 Jun 2001 09:04:52 -0700 (PDT) (envelope-from Bsdguru@aol.com) Received: from Bsdguru@aol.com by imo-m01.mx.aol.com (mail_out_v30.22.) id h.94.150764fd (3969); Tue, 5 Jun 2001 12:04:37 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <94.150764fd.284e5d14@aol.com> Date: Tue, 5 Jun 2001 12:04:36 EDT Subject: Re: How to disable software TCP checksumming? To: louie@transsys.com Cc: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 06/05/2001 10:25:09 AM Eastern Daylight Time, louie@TransSys.COM writes: > Suspect hardware problem? Of course you should! That's why memory > systems have parity or ECC, and I/O buses are similarlly protected. At > least on real computers. Your view of the world is a bit misguided. I know of a situation a few years back where cascade switches were doing ATM to Frame Relay conversion and sending out mal-formed packets due to a bug in their reassembly procedure. Cisco routers (which pass data without checksuming and dont checksum pings) never saw a problem, but our unix boxes were complaining regularly. A similar situation occurred with cheap ethernet bridges that a service provider was using to colocate to a building across the street to uunet truncated packets with volumes over 2mb/s. Checksumming is there for a reason. You premise that "just because there are no physical errors, the data must be good" is simply defective. Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 9:24:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id C146837B406; Tue, 5 Jun 2001 09:24:51 -0700 (PDT) (envelope-from obrien@nuxi.ucdavis.edu) Received: from dragon.nuxi.com (root@trang.muxi.com [206.40.252.115] (may be forged)) by relay.nuxi.com (8.11.2/8.11.2) with ESMTP id f55GOgl02083; Tue, 5 Jun 2001 09:24:42 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f55GOVU91014; Tue, 5 Jun 2001 09:24:31 -0700 (PDT) (envelope-from obrien) Date: Tue, 5 Jun 2001 09:24:31 -0700 From: "David O'Brien" To: "Jacques A. Vidrine" Cc: Dima Dorfman , hackers@freebsd.org, phk@freebsd.org Subject: Re: MFC'ing new md(4) functionality? Message-ID: <20010605092431.A90996@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010605024618.C27003E31@bazooka.unixfreak.org> <20010605071055.D30939@shade.nectar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010605071055.D30939@shade.nectar.com>; from n@nectar.com on Tue, Jun 05, 2001 at 07:10:56AM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jun 05, 2001 at 07:10:56AM -0500, Jacques A. Vidrine wrote: > On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote: > > mdconfig(8) and > > mdioctl.h aren't in -stable so those can be brought over verbatim, > > Dumb question: Can we just add a RELENG_4 tag to the files in such a > case? You could get by doing things that hackish way. But it can be prone to error. The proper way is to ``cvs add'' them in a directory checked out on the branch. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 9:33:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 34DC337B403; Tue, 5 Jun 2001 09:33:28 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f55GXH170327; Tue, 5 Jun 2001 18:33:17 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: obrien@freebsd.org Cc: Dima Dorfman , hackers@freebsd.org Subject: Re: MFC'ing new md(4) functionality? In-Reply-To: Your message of "Tue, 05 Jun 2001 01:31:49 PDT." <20010605013148.A49246@dragon.nuxi.com> Date: Tue, 05 Jun 2001 18:33:17 +0200 Message-ID: <70325.991758797@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010605013148.A49246@dragon.nuxi.com>, "David O'Brien" writes: >On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote: >> Is there any reason not to MFC the new md(4) functionality > >Zero reason not to. Others see it differently, it would seriously break a lot of people who are using -stable in embedded applications. If we have abandoned the "no changes to API or ABI in -stable" paradigm, it would be a good idea, but it serious rains on that rule... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 9:59:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8A53037B405 for ; Tue, 5 Jun 2001 09:59:45 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f55Gxi046098 for ; Tue, 5 Jun 2001 09:59:45 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f55GxiG42192; Tue, 5 Jun 2001 09:59:44 -0700 (PDT) (envelope-from jdp) Date: Tue, 5 Jun 2001 09:59:44 -0700 (PDT) Message-Id: <200106051659.f55GxiG42192@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Subject: Re: MFC'ing new md(4) functionality? In-Reply-To: <20010605092431.A90996@dragon.nuxi.com> References: <20010605024618.C27003E31@bazooka.unixfreak.org> <20010605071055.D30939@shade.nectar.com> <20010605092431.A90996@dragon.nuxi.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20010605092431.A90996@dragon.nuxi.com>, David O'Brien wrote: > On Tue, Jun 05, 2001 at 07:10:56AM -0500, Jacques A. Vidrine wrote: > > > > Dumb question: Can we just add a RELENG_4 tag to the files in such a > > case? > > You could get by doing things that hackish way. But it can be prone to > error. The proper way is to ``cvs add'' them in a directory checked out > on the branch. I agree, that's the proper way to do it. The net effect is the same: it adds the RELENG_4 tag to the files. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 10:18:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (oe49.law14.hotmail.com [64.4.20.21]) by hub.freebsd.org (Postfix) with ESMTP id A7D9437B403 for ; Tue, 5 Jun 2001 10:18:51 -0700 (PDT) (envelope-from ipver4@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 5 Jun 2001 10:18:46 -0700 X-Originating-IP: [135.180.144.113] From: "ipver4" To: Subject: too many stray irq 7's Date: Tue, 5 Jun 2001 13:19:00 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2462.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 Message-ID: X-OriginalArrivalTime: 05 Jun 2001 17:18:46.0503 (UTC) FILETIME=[94229F70:01C0EDE3] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am running FreeBSD 4.3 on a P3 1GMHz PC. While I am doing some testing, I saw the kernel complained about "too many stray irq 7's." The system runs ok, but I am concerned. What could cause the warning? Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 10:20:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 740AA37B401 for ; Tue, 5 Jun 2001 10:20:19 -0700 (PDT) (envelope-from obrien@nuxi.ucdavis.edu) Received: from dragon.nuxi.com (root@trang.muxi.com [206.40.252.115] (may be forged)) by relay.nuxi.com (8.11.2/8.11.2) with ESMTP id f55HKIR05726; Tue, 5 Jun 2001 10:20:18 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f55HKHv91817; Tue, 5 Jun 2001 10:20:17 -0700 (PDT) (envelope-from obrien) Date: Tue, 5 Jun 2001 10:20:17 -0700 From: "David O'Brien" To: Poul-Henning Kamp Cc: Dima Dorfman , hackers@freebsd.org Subject: Re: MFC'ing new md(4) functionality? Message-ID: <20010605102017.E48590@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010605013148.A49246@dragon.nuxi.com> <70325.991758797@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <70325.991758797@critter>; from phk@critter.freebsd.dk on Tue, Jun 05, 2001 at 06:33:17PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jun 05, 2001 at 06:33:17PM +0200, Poul-Henning Kamp wrote: > Others see it differently, it would seriously break a lot of > people who are using -stable in embedded applications. Can you expand on this? I assume you know we are not talking about disabling vn(4). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 10:20:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2776E37B405 for ; Tue, 5 Jun 2001 10:20:16 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f55HKFE94895 for ; Tue, 5 Jun 2001 11:20:15 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200106051720.f55HKFE94895@harmony.village.org> To: hackers@freebsd.org Subject: Host dependency in sysinstall Date: Tue, 05 Jun 2001 11:20:15 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG buildworld uses the boot blocks installed on the system to build sysinstall, rather than the ones that are build tree. .if ${MACHINE} == "i386" file2c 'u_char boot0[] = {' '};' < /boot/boot0 >> makedevs.tmp echo "size_t boot0_size = sizeof(boot0);" >> makedevs.tmp file2c 'u_char mbr[] = {' '};' < /boot/mbr >> makedevs.tmp echo "size_t mbr_size = sizeof(mbr);" >> makedevs.tmp .endif .if ${MACHINE} == "pc98" file2c 'u_char boot0[] = {' '};' < /boot/boot0 >> makedevs.tmp echo "size_t boot0_size = sizeof(boot0);" >> makedevs.tmp file2c 'u_char boot05[] = {' '};' < /boot/boot0.5 >> makedevs.tmp echo "size_t boot05_size = sizeof(boot05);" >> makedevs.tmp .endif What's the right fix for this? It is breaking my cross building of pc98 on my i386 box. I don't have a /boot/boot0.5 on my i386 box :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 10:22: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 950CB37B405 for ; Tue, 5 Jun 2001 10:21:57 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #6) id 157KWi-000Il4-00 for freebsd-hackers@freebsd.org; Tue, 5 Jun 2001 18:21:56 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.3/8.11.1) id f55HLpg91184 for freebsd-hackers@freebsd.org; Tue, 5 Jun 2001 18:21:51 +0100 (BST) (envelope-from jcm) Date: Tue, 5 Jun 2001 18:21:51 +0100 From: j mckitrick To: freebsd-hackers@freebsd.org Subject: newbussifying drivers Message-ID: <20010605182151.A90883@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The newbus routines use a certain amount of overhead, but once done, you forget about it. In some device drivers, the probe methods often need to try a variety of hardware ports. In the past, inb/outb was used, along with an often hardcoded port address. Does it make sense to call bus_allocate_resource for every hardware port we probe? What is the best way to handle this so NO inb/out is used, even for probing? jcm -- "I drank WHAT ?!" - Socrates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 10:43:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 1202737B405; Tue, 5 Jun 2001 10:43:48 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f55Hhc171258; Tue, 5 Jun 2001 19:43:38 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: obrien@freebsd.org Cc: Dima Dorfman , hackers@freebsd.org Subject: Re: MFC'ing new md(4) functionality? In-Reply-To: Your message of "Tue, 05 Jun 2001 10:20:17 PDT." <20010605102017.E48590@dragon.nuxi.com> Date: Tue, 05 Jun 2001 19:43:38 +0200 Message-ID: <71256.991763018@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010605102017.E48590@dragon.nuxi.com>, "David O'Brien" writes: >On Tue, Jun 05, 2001 at 06:33:17PM +0200, Poul-Henning Kamp wrote: >> Others see it differently, it would seriously break a lot of >> people who are using -stable in embedded applications. > >Can you expand on this? I assume you know we are not talking about >disabling vn(4). We already have a previous form of md(4) in stable, -current's md(4) is not compatible with that older version. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 11:15:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.qubesoft.com (gate.qubesoft.com [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id 71FCA37B403; Tue, 5 Jun 2001 11:15:32 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from bluebottle.qubesoft.com (bluebottle [192.168.1.2]) by gate.qubesoft.com (8.11.3/8.11.3) with ESMTP id f55IFUq84716; Tue, 5 Jun 2001 19:15:30 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by bluebottle.qubesoft.com (8.11.1/8.11.3) with ESMTP id f55IFUG21433; Tue, 5 Jun 2001 19:15:30 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Tue, 5 Jun 2001 19:15:30 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@bluebottle To: Mike Smith Cc: Jonathan Chen , hackers@FreeBSD.ORG Subject: Re: Resource reservation idea In-Reply-To: <200106050158.f551wmL06759@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > - Some dummy driver which grabs the resource. The dummy driver would > > need to be unloaded when the actual driver needs the resources. > > This sounds attractive, but it's hard to find the dummy driver when > you want to open the bidding for one or more devices again. You also end > up with the ugly case where the device has more resources than the driver > uses; you end up needing a placeholder of some sort for these as well, so > you might as well just built it into the way the bus thinks about child > devices and be done with it. It was suggested some time ago to do this by having a priority value that indicates a dummy, say -10000. When a driver is loaded, all dummies are detached and the probe is restarted. The dummies are quiet if not cold booting to avoi a storm of dummies announcing themselves again and again. Nick -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 11:31:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [209.247.77.155]) by hub.freebsd.org (Postfix) with ESMTP id AE38F37B403 for ; Tue, 5 Jun 2001 11:31:33 -0700 (PDT) (envelope-from gordont@bluemtn.net) Received: from localhost (gordont@localhost) by sdmail0.sd.bmarts.com (8.11.3/8.11.2/BMA1.1) with ESMTP id f55IT2f20153; Tue, 5 Jun 2001 11:29:03 -0700 (PDT) Date: Tue, 5 Jun 2001 11:29:02 -0700 (PDT) From: Gordon Tetlow X-X-Sender: To: "Heimes, Rene" Cc: Subject: Re: security log file parser / ids In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 5 Jun 2001, Heimes, Rene wrote: > hiho! > > i am searching for a parser that parses security logs from ipfw-made up > logs. anyone got a hint? No idea on that one. There might be something in the ports collection. > (btw: what about ipfw firewalls - outdated? what would be better? > ipchains? help!) Um... ipchains is a Linux thing. > other question - whats the (freeware) ids of your choice / "state of the > art" for freeBSD? You need to rephrase the question here. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 11:37: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id CF9F437B401 for ; Tue, 5 Jun 2001 11:36:56 -0700 (PDT) (envelope-from fmela0@sm.socccd.cc.ca.us) Received: from sm.socccd.cc.ca.us (pool0643.cvx15-bradley.dialup.earthlink.net [209.179.46.133]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id LAA13843; Tue, 5 Jun 2001 11:36:45 -0700 (PDT) Message-ID: <3B1D2747.96EAC69D@sm.socccd.cc.ca.us> Date: Tue, 05 Jun 2001 11:39:03 -0700 From: Farooq Mela X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Heimes, Rene" Cc: hackers@freebsd.org Subject: Re: security log file parser / ids References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Heimes, Rene" wrote: > other question - whats the (freeware) ids of your choice / "state of the > art" for freeBSD? try /usr/ports/security/snort. Next time send questions like this to the -questions mailing list. -- farooq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 13: 8:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 7075637B401 for ; Tue, 5 Jun 2001 13:08:07 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f55K7pQ97572; Tue, 5 Jun 2001 16:07:52 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20010605190447.B9976@tao.org.uk> References: <20010602041242.849893E33@bazooka.unixfreak.org> <20010605190447.B9976@tao.org.uk> Date: Tue, 5 Jun 2001 16:07:49 -0400 To: Josef Karthauser From: Garance A Drosihn Subject: Re: Fixing documented bug in env(1) Cc: Dima Dorfman , Peter Seebach , hackers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 7:04 PM +0100 6/5/01, Josef Karthauser wrote: >On Sat, Jun 02, 2001, Garance A Drosihn wrote: > > >> It also strikes me that this might be another topic to >> send thru freebsd-standards@bostonradio.org, as Posix >> might have something to say about what's appropriate. >> > >How much traffic does this list produce and how many people >are on it? >The first I heard of it's existance was a few days ago on >one of the lists. May I propose that we make this an offical >list so that it can be utilised by the wider community? Not much traffic. Not many people. It can be used by anyone who wants to join. I think Garrett originally proposed it as a "@freebsd.org" list, but it was felt that it wouldn't see enough traffic (and indeed, it has been very low-traffic). My only fear is that I might be encouraging its use for things it wasn't really meant for. It was mainly meant to talk about efforts to update freebsd to follow the various Posix standards, such as the latest Posix draft on how /usr/include libraries should be laid out. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 13:24:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 44A2C37B406 for ; Tue, 5 Jun 2001 13:24:04 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f55KWTj01513; Tue, 5 Jun 2001 13:32:29 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106052032.f55KWTj01513@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: j mckitrick Cc: freebsd-hackers@freebsd.org Subject: Re: newbussifying drivers In-reply-to: Your message of "Tue, 05 Jun 2001 18:21:51 BST." <20010605182151.A90883@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jun 2001 13:32:29 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > The newbus routines use a certain amount of overhead, but once done, you > forget about it. In some device drivers, the probe methods often need to > try a variety of hardware ports. In the past, inb/outb was used, along with > an often hardcoded port address. > > Does it make sense to call bus_allocate_resource for every hardware port we > probe? What is the best way to handle this so NO inb/out is used, even for > probing? Typically, probe routines these days are invoked with a single set of I/O parameters to probe (and even this is only ISA devices). It's pretty rare to need to bit-bang to find a device these days anyway; you should probably be looking for PnP data or similar. This is what hints are (basically) - manually-supplied PnP data. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 14:47: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nwlynx.network-lynx.net (nwlynx.network-lynx.net [63.122.185.99]) by hub.freebsd.org (Postfix) with ESMTP id 4709237B408; Tue, 5 Jun 2001 14:47:00 -0700 (PDT) (envelope-from Don@Silver-Lynx.com) Received: from Silver-Lynx.com (doze-1.network-lynx.net [63.122.185.106]) by nwlynx.network-lynx.net (8.11.1/8.9.3/Who.Cares) with ESMTP id f55Ll4j14566; Tue, 5 Jun 2001 15:47:04 -0600 (MDT) (envelope-from Don@Silver-Lynx.com) Message-ID: <3B1D5350.FEFBD0FC@Silver-Lynx.com> Date: Tue, 05 Jun 2001 15:46:56 -0600 From: Don Wilde X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: msmith@freebsd.org, freebsd-hackers@freebsd.org Subject: IEEE P1394 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Mike - Some time ago, you corresponded with a gentleman from Japan (Katsushi Kobayashi ) about his firewire code. I've also noted a more recent query from a Wind River employee, which gives me hope that they might have interest in pursuing it. I'm not good enough to do driver code, but I'd be glad to assist in other ways. I have a Sony PCG-F420 laptop with firewire port as well as a digital video camera, and I'd be glad to act as a test dummy. The LT is currently running 4-STABLE, but it's not a critical machine so I could go -CURRENT. -- Don Wilde http://www.Silver-Lynx.com Silver Lynx Embedded Microsystems Architects 2218 Southern Bl. Ste. 12 Rio Rancho, NM 87124 505-891-4175 FAX 891-4185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 15: 0:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id D721B37B401; Tue, 5 Jun 2001 15:00:34 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 157OsL-000Lss-00; Tue, 5 Jun 2001 23:00:33 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.3/8.11.1) id f55M0Wv96535; Tue, 5 Jun 2001 23:00:32 +0100 (BST) (envelope-from jcm) Date: Tue, 5 Jun 2001 23:00:32 +0100 From: j mckitrick To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: newbussifying drivers Message-ID: <20010605230032.B96188@dogma.freebsd-uk.eu.org> References: <20010605182151.A90883@dogma.freebsd-uk.eu.org> <200106052032.f55KWTj01513@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200106052032.f55KWTj01513@mass.dis.org>; from msmith@freebsd.org on Tue, Jun 05, 2001 at 01:32:29PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG | Typically, probe routines these days are invoked with a single set of I/O | parameters to probe (and even this is only ISA devices). | | It's pretty rare to need to bit-bang to find a device these days anyway; | you should probably be looking for PnP data or similar. This is what | hints are (basically) - manually-supplied PnP data. How would you recommending fixing this, taken from the ex driver? for (ioport = 0x200; ioport < 0x3a0; ioport += 0x10) { /* No board found at address */ if (!look_for_card(ioport)) { continue; } if (bootverbose) printf("ex: Found card at 0x%03x!\n", ioport); /* Board in PnP mode */ if (eeprom_read(ioport, EE_W0) & EE_W0_PNP) { /* Reset the card. */ outb(ioport + CMD_REG, Reset_CMD); DELAY(500); if (bootverbose) printf("ex: card at 0x%03x in PnP mode!\n", iop continue; } I'm taking this on as my personal project, so the more info i get, the better work i can do. :-) jcm -- "I drank WHAT ?!" - Socrates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 16: 1:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 6B3E237B403 for ; Tue, 5 Jun 2001 16:01:10 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f55N9Zj02982; Tue, 5 Jun 2001 16:09:35 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106052309.f55N9Zj02982@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: j mckitrick Cc: freebsd-hackers@freebsd.org Subject: Re: newbussifying drivers In-reply-to: Your message of "Tue, 05 Jun 2001 23:00:32 BST." <20010605230032.B96188@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jun 2001 16:09:35 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > | Typically, probe routines these days are invoked with a single set of I/O > | parameters to probe (and even this is only ISA devices). > | > | It's pretty rare to need to bit-bang to find a device these days anyway; > | you should probably be looking for PnP data or similar. This is what > | hints are (basically) - manually-supplied PnP data. > > How would you recommending fixing this, taken from the ex driver? Ok, this is basically a manual PnP scan for a card that has pre-PnP metaconfig. The only way to do this "right" is going to be to call bus_alloc_resource() to pick up the PnP port, something like: > for (ioport = 0x200; ioport < 0x3a0; ioport += 0x10) { rid = 0; if ((res = bus_alloc_resource(parent, SYS_RES_IOPORT, &rid, ioport, ioport + 0x10, 0x10, RF_ACTIVE)) == NULL) continue; > /* No board found at address */ > if (!look_for_card(ioport)) { > continue; > } if (!look_for_card(res)) goto complete; > if (bootverbose) > printf("ex: Found card at 0x%03x!\n", ioport); > /* Board in PnP mode */ > if (eeprom_read(ioport, EE_W0) & EE_W0_PNP) { /* PnP probe will find this card */ if (eeprom_read(res, EE_WO) & EE_WO_PNP) goto complete; ... complete: bus_release_resource(parent, SYS_RES_IOPORT, rid, res); } > > > I'm taking this on as my personal project, so the more info i get, the > better work i can do. :-) You'll want to replace all the inb/outb stuff with macros that wrap the bus_space_read/write functions. You can use the same macros in the identify routine, you'll just be allocating the resources differently. I hope this helps. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 16:17:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id 0557237B401; Tue, 5 Jun 2001 16:17:41 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id BAA04372; Wed, 6 Jun 2001 01:04:26 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id 25B0414CEC; Wed, 6 Jun 2001 01:04:27 +0200 (CEST) Date: Wed, 6 Jun 2001 01:04:26 +0200 From: Alexander Langer To: j mckitrick Cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: newbussifying drivers Message-ID: <20010606010426.C28586@zerogravity.kawo2.rwth-aachen.d> References: <20010605182151.A90883@dogma.freebsd-uk.eu.org> <200106052032.f55KWTj01513@mass.dis.org> <20010605230032.B96188@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010605230032.B96188@dogma.freebsd-uk.eu.org>; from jcm@FreeBSD-uk.eu.org on Tue, Jun 05, 2001 at 11:00:32PM +0100 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake j mckitrick (jcm@FreeBSD-uk.eu.org): > | It's pretty rare to need to bit-bang to find a device these days anyway; > | you should probably be looking for PnP data or similar. This is what > | hints are (basically) - manually-supplied PnP data. > How would you recommending fixing this, taken from the ex driver? > for (ioport = 0x200; ioport < 0x3a0; ioport += 0x10) { This is exactly what Mike meant: You manually set the correct I/O port in the hints file and then you don't have to check for each port between 0x200 and 0x3a0. Just bus_alloc_resource once and test for the card. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 16:21:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from idiom.com (idiom.com [216.240.32.1]) by hub.freebsd.org (Postfix) with ESMTP id CE70837B403 for ; Tue, 5 Jun 2001 16:21:06 -0700 (PDT) (envelope-from rdm@cfcl.com) Received: from cfcl.com (cpe-24-221-169-54.ca.sprintbbd.net [24.221.169.54]) by idiom.com (8.9.3/8.9.3) with ESMTP id QAA32276 for ; Tue, 5 Jun 2001 16:21:06 -0700 (PDT) Received: from [192.168.168.205] (cerberus [192.168.168.205]) by cfcl.com (8.11.1/8.11.1) with ESMTP id f55NMdK14952 for ; Tue, 5 Jun 2001 16:22:40 -0700 (PDT) (envelope-from rdm@cfcl.com) Mime-Version: 1.0 Message-Id: In-Reply-To: <20010604224405.A43677@bean.overtone.org> References: <20010604211909.B1112@freebie.demon.nl> <20010604200828.A41130@bean.overtone.org> <20010604224405.A43677@bean.overtone.org> Date: Tue, 5 Jun 2001 16:15:02 -0700 To: freebsd-hackers@FreeBSD.ORG From: Rich Morin Subject: Does Oracle work OK under Linux comp. mode? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG A friend of mine is becoming increasingly dissatisfied with Linux. He says, however, that he can only get a Linux port of Oracle and he is worried that it will not run properly under FreeBSD's Linux compatibility mode. Can anyone give me some Real Information on this? -r -- email: rdm@cfcl.com; phone: +1 650-873-7841 http://www.cfcl.com/rdm - home page, resume, etc. http://www.cfcl.com/Meta/md_fb.html - The FreeBSD Browser http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 16:24:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 1EBA337B403 for ; Tue, 5 Jun 2001 16:24:43 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f55NOHj23130; Tue, 5 Jun 2001 16:24:17 -0700 Date: Tue, 5 Jun 2001 16:24:17 -0700 From: Brooks Davis To: Rich Morin Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Does Oracle work OK under Linux comp. mode? Message-ID: <20010605162417.A22671@Odin.AC.HMC.Edu> References: <20010604211909.B1112@freebie.demon.nl> <20010604200828.A41130@bean.overtone.org> <20010604224405.A43677@bean.overtone.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="bg08WKrSYDhXBjb5" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rdm@cfcl.com on Tue, Jun 05, 2001 at 04:15:02PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 05, 2001 at 04:15:02PM -0700, Rich Morin wrote: > A friend of mine is becoming increasingly dissatisfied with Linux. > He says, however, that he can only get a Linux port of Oracle and > he is worried that it will not run properly under FreeBSD's Linux > compatibility mode. Can anyone give me some Real Information on > this? Obviously, Oracle isn't going to actually support you unless you're careful in dealing with them, but instructions for installing it are in the handbook: http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/linuxemu-oracle.= html -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --bg08WKrSYDhXBjb5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7HWogXY6L6fI4GtQRAkojAKCB+wOWaQRZ/WxDNIgLVsYnyaUQ5wCbBhlT vIksIYi+gNZ1dGn9T7mv/d8= =7lrv -----END PGP SIGNATURE----- --bg08WKrSYDhXBjb5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 19:14:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 4AFA537B405; Tue, 5 Jun 2001 19:14:07 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 157Spi-0007jN-00; Wed, 6 Jun 2001 03:14:06 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.3/8.11.1) id f562E4D01889; Wed, 6 Jun 2001 03:14:04 +0100 (BST) (envelope-from jcm) Date: Wed, 6 Jun 2001 03:14:04 +0100 From: j mckitrick To: Alexander Langer Cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: newbussifying drivers Message-ID: <20010606031403.A1849@dogma.freebsd-uk.eu.org> References: <20010605182151.A90883@dogma.freebsd-uk.eu.org> <200106052032.f55KWTj01513@mass.dis.org> <20010605230032.B96188@dogma.freebsd-uk.eu.org> <20010606010426.C28586@zerogravity.kawo2.rwth-aachen.d> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010606010426.C28586@zerogravity.kawo2.rwth-aachen.d>; from alex@big.endian.de on Wed, Jun 06, 2001 at 01:04:26AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG | You manually set the correct I/O port in the hints file and then you | don't have to check for each port between 0x200 and 0x3a0. | | Just bus_alloc_resource once and test for the card. So without having the card for testing, i should just wrap the port access calls into bus_xxx calls? jcm -- "I drank WHAT ?!" - Socrates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 21:48:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 8148337B408 for ; Tue, 5 Jun 2001 21:48:28 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f562h0V01624; Tue, 5 Jun 2001 19:43:00 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106060243.f562h0V01624@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: j mckitrick Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: newbussifying drivers In-reply-to: Your message of "Wed, 06 Jun 2001 03:14:04 BST." <20010606031403.A1849@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jun 2001 19:42:59 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > | You manually set the correct I/O port in the hints file and then you > | don't have to check for each port between 0x200 and 0x3a0. > | > | Just bus_alloc_resource once and test for the card. > > So without having the card for testing, i should just wrap the port access > calls into bus_xxx calls? You should not even consider doing this without either a card for testing or a group of willing testers. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 22: 5: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id E632837B406 for ; Tue, 5 Jun 2001 22:04:57 -0700 (PDT) (envelope-from sethk@meow.osd.bsdi.com) Received: (from sethk@localhost) by meow.osd.bsdi.com (8.11.2/8.11.2) id f5654QS81891; Tue, 5 Jun 2001 22:04:26 -0700 (PDT) (envelope-from sethk) Date: Tue, 5 Jun 2001 22:04:26 -0700 From: Seth Kingsley To: Valentin Nechayev Cc: freebsd-hackers@FreeBSD.ORG, Jiangyi Liu Subject: Re: How to recompile kernel after minor changes? Message-ID: <20010605220426.A55274@meow.osd.bsdi.com> References: <878zjb20fd.fsf@fatcow.home> <20010603101848.A990@iv.nn.kiev.ua> <20010603020220.A89269@dragon.nuxi.com> <20010603131841.A460@iv.nn.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010603131841.A460@iv.nn.kiev.ua>; from netch@iv.nn.kiev.ua on Sun, Jun 03, 2001 at 01:18:41PM +0300 Organization: Berkeley Software Design Inc. (BSDi) X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jun 03, 2001 at 01:18:41PM +0300, Valentin Nechayev wrote: > Sun, Jun 03, 2001 at 02:02:20, freebsd-hackers (David O'Brien - Hackers) wrote about "Re: How to recompile kernel after minor changes?": > > or ``make kernel'' > > and if you want to live dangerously ``make kernel-reinstall''. > > You are right, it is dangerous because it does not copy current kernel > to /boot/kernel/kernel.old. I need to do it by hands (install -c -fschg ...) But then again, it is less dangerous in a certain sense when you are installing over a kernel that isn't something you want to fall back on as kernel.old. You don't want to preseve it using the regular 'make install'. -- || Seth Kingsley || BSDi/Open Source Division || sethk@osd.bsdi.com || To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 22:30:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from vbook.express.ru (vbook.express.ru [212.24.37.106]) by hub.freebsd.org (Postfix) with ESMTP id 1715937B401; Tue, 5 Jun 2001 22:30:24 -0700 (PDT) (envelope-from vova@vbook.express.ru) Received: (from vova@localhost) by vbook.express.ru (8.9.3/8.9.3) id JAA23214; Wed, 6 Jun 2001 09:30:30 +0400 (MSD) (envelope-from vova) From: "Vladimir B. Grebenschikov" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15133.49140.991472.942463@vbook.express.ru> Date: Wed, 6 Jun 2001 09:30:28 +0400 (MSD) To: Don Wilde Cc: msmith@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: IEEE P1394 In-Reply-To: <3B1D5350.FEFBD0FC@Silver-Lynx.com> References: <3B1D5350.FEFBD0FC@Silver-Lynx.com> X-Mailer: VM 6.72 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Don Wilde writes: > Hi, Mike - > > Some time ago, you corresponded with a gentleman from Japan (Katsushi > Kobayashi ) about his firewire code. I've also > noted a more recent query from a Wind River employee, which gives me > hope that they might have interest in pursuing it. > > I'm not good enough to do driver code, but I'd be glad to assist in > other ways. I have a Sony PCG-F420 laptop with firewire port as well as > a digital video camera, and I'd be glad to act as a test dummy. The LT > is currently running 4-STABLE, but it's not a critical machine so I > could go -CURRENT. I am interesting in working fireware code too I found link ftp://ftp.uec.ac.jp/pub/firewire/ but it seems a bit outdating. Any new links or ideas ? > -- > Don Wilde http://www.Silver-Lynx.com > Silver Lynx Embedded Microsystems Architects > 2218 Southern Bl. Ste. 12 Rio Rancho, NM 87124 > 505-891-4175 FAX 891-4185 -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, vova@express.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 22:38:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 253D837B405 for ; Tue, 5 Jun 2001 22:38:24 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f565m3A01009; Tue, 5 Jun 2001 22:48:03 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106060548.f565m3A01009@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Don Wilde Cc: freebsd-hackers@freebsd.org Subject: Re: IEEE P1394 In-reply-to: Your message of "Tue, 05 Jun 2001 15:46:56 MDT." <3B1D5350.FEFBD0FC@Silver-Lynx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 Jun 2001 22:48:03 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Some time ago, you corresponded with a gentleman from Japan (Katsushi > Kobayashi ) about his firewire code. I've also > noted a more recent query from a Wind River employee, which gives me > hope that they might have interest in pursuing it. I don't think that Bill Paul (the WRS chap I was goading to work on FireWire) has done anything on this lately. > I'm not good enough to do driver code, but I'd be glad to assist in > other ways. I have a Sony PCG-F420 laptop with firewire port as well as > a digital video camera, and I'd be glad to act as a test dummy. The LT > is currently running 4-STABLE, but it's not a critical machine so I > could go -CURRENT. At this point in time, if you're not up to coding on this project, there's not much to be done, I'm afraid. It needs a lot of development work before it'll be ready for anything resembling testing. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jun 5 23:56:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 3D4D337B401 for ; Tue, 5 Jun 2001 23:56:15 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f566u0w38376; Wed, 6 Jun 2001 09:56:00 +0300 (EEST) (envelope-from ru) Date: Wed, 6 Jun 2001 09:56:00 +0300 From: Ruslan Ermilov To: Poul-Henning Kamp Cc: hackers@FreeBSD.ORG Subject: Re: MFC'ing new md(4) functionality? Message-ID: <20010606095600.A37378@sunbay.com> Mail-Followup-To: Poul-Henning Kamp , hackers@FreeBSD.ORG References: <20010605102017.E48590@dragon.nuxi.com> <71256.991763018@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <71256.991763018@critter>; from phk@critter.freebsd.dk on Tue, Jun 05, 2001 at 07:43:38PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jun 05, 2001 at 07:43:38PM +0200, Poul-Henning Kamp wrote: > In message <20010605102017.E48590@dragon.nuxi.com>, "David O'Brien" writes: > >On Tue, Jun 05, 2001 at 06:33:17PM +0200, Poul-Henning Kamp wrote: > >> Others see it differently, it would seriously break a lot of > >> people who are using -stable in embedded applications. > > > >Can you expand on this? I assume you know we are not talking about > >disabling vn(4). > > We already have a previous form of md(4) in stable, -current's md(4) > is not compatible with that older version. > And that older version doesn't even work (at least when loaded as the module): # kldload md # disklabel -r -w md0 auto ^C^C^C^C^C^C^C^C^C Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 0:10:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id DACCF37B405; Wed, 6 Jun 2001 00:10:16 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f567A5178086; Wed, 6 Jun 2001 09:10:05 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Ruslan Ermilov Cc: hackers@FreeBSD.ORG Subject: Re: MFC'ing new md(4) functionality? In-Reply-To: Your message of "Wed, 06 Jun 2001 09:56:00 +0300." <20010606095600.A37378@sunbay.com> Date: Wed, 06 Jun 2001 09:10:05 +0200 Message-ID: <78084.991811405@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010606095600.A37378@sunbay.com>, Ruslan Ermilov writes: >On Tue, Jun 05, 2001 at 07:43:38PM +0200, Poul-Henning Kamp wrote: >> In message <20010605102017.E48590@dragon.nuxi.com>, "David O'Brien" writes: >> >On Tue, Jun 05, 2001 at 06:33:17PM +0200, Poul-Henning Kamp wrote: >> >> Others see it differently, it would seriously break a lot of >> >> people who are using -stable in embedded applications. >> > >> >Can you expand on this? I assume you know we are not talking about >> >disabling vn(4). >> >> We already have a previous form of md(4) in stable, -current's md(4) >> is not compatible with that older version. >> >And that older version doesn't even work (at least when loaded as the >module): While true, it is not really relevant to the issue of API/ABI breakage in -stable... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 1:16:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nimitz.mcnett (24-130-188-11.san.rr.com [24.130.188.11]) by hub.freebsd.org (Postfix) with ESMTP id 8CA0F37B408 for ; Wed, 6 Jun 2001 01:16:29 -0700 (PDT) (envelope-from mmcnett@cs.ucsd.edu) Received: from cs.ucsd.edu (localhost [127.0.0.1]) by nimitz.mcnett (8.11.1/8.11.1) with ESMTP id f568KKA00792 for ; Wed, 6 Jun 2001 01:20:20 -0700 (PDT) (envelope-from mmcnett@cs.ucsd.edu) Message-ID: <3B1DE7C3.C3CDF044@cs.ucsd.edu> Date: Wed, 06 Jun 2001 01:20:19 -0700 From: Marvin McNett X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: vm_object question/verification Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm confused (and probably wrong), but does the 'shadow_head' field of the vm_object structure really refer to a list of objects that the object shadows (as mentioned in the comment)? Looking at the vm_object_shadow() function (vm/vm_object.c, line 894 in 4.3), it looks like it's the other way around; ie. shadow_head refers to a list of objects which shadow the object. Thank you to anyone who could verify this for me. -Marvin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 1:19:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id 03A7B37B401; Wed, 6 Jun 2001 01:19:19 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id KAA22025; Wed, 6 Jun 2001 10:06:07 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id C971214C6A; Wed, 6 Jun 2001 10:06:06 +0200 (CEST) Date: Wed, 6 Jun 2001 10:06:06 +0200 From: Alexander Langer To: j mckitrick Cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: newbussifying drivers Message-ID: <20010606100606.A570@zerogravity.kawo2.rwth-aachen.d> References: <20010605182151.A90883@dogma.freebsd-uk.eu.org> <200106052032.f55KWTj01513@mass.dis.org> <20010605230032.B96188@dogma.freebsd-uk.eu.org> <20010606010426.C28586@zerogravity.kawo2.rwth-aachen.d> <20010606031403.A1849@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010606031403.A1849@dogma.freebsd-uk.eu.org>; from jcm@freebsd-uk.eu.org on Wed, Jun 06, 2001 at 03:14:04AM +0100 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake j mckitrick (jcm@freebsd-uk.eu.org): > So without having the card for testing, i should just wrap the port access > calls into bus_xxx calls? Yes, that's basically what has to be done. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 2:57:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from newsguy.com (perry.pathlink.com [209.155.233.33]) by hub.freebsd.org (Postfix) with ESMTP id C4BDE37B401 for ; Wed, 6 Jun 2001 02:57:49 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (ppp045-bsace7001.telebrasilia.net.br [200.181.80.45]) by newsguy.com (8.11.0/8.9.1) with ESMTP id f569vIq08510; Wed, 6 Jun 2001 02:57:19 -0700 (PDT) Message-ID: <3B1DFEAF.927E1DC3@newsguy.com> Date: Wed, 06 Jun 2001 06:58:07 -0300 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en,pt-BR,pt,en-GB,en-US,ja MIME-Version: 1.0 To: "Louis A. Mamakos" Cc: Giorgos Keramidas , Bob Willcox , Jesper Skriver , hackers list Subject: Re: How to disable software TCP checksumming? References: <20010529144114.I19771@luke.immure.com> <20010529221107.C49875@skriver.dk> <20010529155212.M19771@luke.immure.com> <20010530045200.A1031@hades.hell.gr> <3B1CACDA.96599BD5@newsguy.com> <200106051422.f55EM4n78505@whizzo.transsys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Louis A. Mamakos" wrote: > > > > > It seems to me to be kind of moot to check the same value twice, unless > > you suspect hardware problems. Aren't you talking about two different > > checks over the same data instead of checksum off-loading? > > Suspect hardware problem? Of course you should! That's why memory > systems have parity or ECC, and I/O buses are similarlly protected. At > least on real computers. > > The link-level CRC only protects the data as it goes over the link ^^^^^^^^^^ After reading the rest of his messages, I'm not so sure, but I would think he was talking about _transport_ level check sum, and verifying that with hardward (NIC) instead of software (IP stack). > between the link-level hardware which generates the CRC and the box > on the other end that receives it. It does not protect the data > end-to-end, so if it's gets corrupted whilst sitting in memory in > an intermediate node, you won't detect that. > > Why would it get corrupted? > > 1. Software. Random unrelated other software does a random store in > the buffer containing your packet sitting in memory. Fancy device drivers > that do scatter-gather I/O gets it wrong every now and then and points > off into space. mbuf cluster which should be treated as read-only isn't, > and some other code hoses it. (See PR kern/27782 at > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27782 for an example of this.) > > 2. Hardware. I found broken UNIBUS hardware 15 or 20 years ago this > way. I had some broken hardware which took frame relay frames on > a HSSI interface and turned them into AAL5 ATM cells that would get > the cell reassembly wrong if you pushed too hard. Or just plain > broken memory that results in packet corruption. > > I've personally experienced all these problems. Maybe I'm just > unluckly. One common thread of my experiences is being close to the > bleeding edge of technology where stuff isn't as mature as many people > are used to. > > This end-to-end issue is not a theoretical consideration. While the > 1's complement internet checksum isn't that strong, it does detect a > bunch of bug-like behavior like this. > > Louis Mamakos -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net wow regex humor... I'm a geek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 3:21:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 72FF837B401; Wed, 6 Jun 2001 03:21:53 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #6) id 157aRk-000OxB-00; Wed, 6 Jun 2001 11:21:52 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.3/8.11.1) id f56ALqc10619; Wed, 6 Jun 2001 11:21:52 +0100 (BST) (envelope-from jcm) Date: Wed, 6 Jun 2001 11:21:51 +0100 From: j mckitrick To: Alexander Langer Cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: newbussifying drivers Message-ID: <20010606112151.D10263@dogma.freebsd-uk.eu.org> References: <20010605182151.A90883@dogma.freebsd-uk.eu.org> <200106052032.f55KWTj01513@mass.dis.org> <20010605230032.B96188@dogma.freebsd-uk.eu.org> <20010606010426.C28586@zerogravity.kawo2.rwth-aachen.d> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010606010426.C28586@zerogravity.kawo2.rwth-aachen.d>; from alex@big.endian.de on Wed, Jun 06, 2001 at 01:04:26AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG | You manually set the correct I/O port in the hints file and then you Sorry if i misunderstand, but isn't the hints file only for -current? I was under the impression it was only to simplify driver development. Since my goal is to clean up the driver under the newbus system, how would this port address issue be handled under -stable? jcm -- "I drank WHAT ?!" - Socrates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 3:29:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id A367037B403 for ; Wed, 6 Jun 2001 03:29:09 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f56AbcU02834; Wed, 6 Jun 2001 03:37:38 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106061037.f56AbcU02834@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: j mckitrick Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: newbussifying drivers In-reply-to: Your message of "Wed, 06 Jun 2001 11:21:51 BST." <20010606112151.D10263@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Jun 2001 03:37:38 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > | You manually set the correct I/O port in the hints file and then you > > Sorry if i misunderstand, but isn't the hints file only for -current? I was > under the impression it was only to simplify driver development. > > Since my goal is to clean up the driver under the newbus system, how would > this port address issue be handled under -stable? Hints aren't appropriate in this situation; please see the lengthy response I posted to your code question. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 4:53:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tux.babel.fr (babeliens.babel.fr [212.208.27.125]) by hub.freebsd.org (Postfix) with ESMTP id 4506637B405 for ; Wed, 6 Jun 2001 04:53:15 -0700 (PDT) (envelope-from flevesque@babel.fr) Received: from babel.fr (IDENT:flevesqu@localhost.localdomain [127.0.0.1]) by tux.babel.fr (8.9.3/8.9.3) with ESMTP id MAA03892 for ; Wed, 6 Jun 2001 12:54:46 +0200 Message-ID: <3B1E0BF6.E0E8225D@babel.fr> Date: Wed, 06 Jun 2001 12:54:46 +0200 From: Franck LEVESQUE Organization: [BaBeL@STaL] X-Mailer: Mozilla 4.72 [fr] (X11; U; Linux 2.2.14-6.1.1 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Subject: no more 'root' account on my machine... References: <20010606113938.1B1C037B405@hub.freebsd.org> <3B1E0AF6.A05BA5FD@babel.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Hi, > > First of all, sorry for my bad english skills. > > As the newbie I am on FreeBSD (4.3), I did a very stupid thing while > using vipw : I deleted the root account. > > I tryed to correct my problem using the "fix it" floppy, but changing > the /etc/passwd file is not enough. > Really I am sorry to bother you with that, but I don't know that much > about the master.passwd and the way FreeBSD does to authentify users. > > Anybody has an idea about the way I shall follow to resolve my problem? > Thank you indeed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 5: 6:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nwlynx.network-lynx.net (nwlynx.network-lynx.net [63.122.185.99]) by hub.freebsd.org (Postfix) with ESMTP id C625E37B403; Wed, 6 Jun 2001 05:06:36 -0700 (PDT) (envelope-from Don@Silver-Lynx.com) Received: from Silver-Lynx.com (doze-1.network-lynx.net [63.122.185.106]) by nwlynx.network-lynx.net (8.11.1/8.9.3/Who.Cares) with ESMTP id f56C6nj60362; Wed, 6 Jun 2001 06:06:49 -0600 (MDT) (envelope-from Don@Silver-Lynx.com) Message-ID: <3B1E1CCC.4205CCAF@Silver-Lynx.com> Date: Wed, 06 Jun 2001 06:06:36 -0600 From: Don Wilde X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: IEEE P1394 References: <200106060548.f565m3A01009@mass.dis.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Smith wrote: > At this point in time, if you're not up to coding on this project, > there's not much to be done, I'm afraid. It needs a lot of development > work before it'll be ready for anything resembling testing. > > Regards, > Mike Thanks, Mike. It's a matter of knowing my limitations, including time to apply to learning. -- Don Wilde http://www.Silver-Lynx.com Silver Lynx Embedded Microsystems Architects 2218 Southern Bl. Ste. 12 Rio Rancho, NM 87124 505-891-4175 FAX 891-4185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 6: 9:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ajax2.sovam.com (ajax2.sovam.com [194.67.1.173]) by hub.freebsd.org (Postfix) with ESMTP id 1F20C37B413 for ; Wed, 6 Jun 2001 06:09:23 -0700 (PDT) (envelope-from avn@any.ru) Received: from ts9-a310.dial.sovam.com ([195.239.71.54]:1215 "EHLO srv2.any" ident: "TIMEDOUT" whoson: "-unregistered-" smtp-auth: TLS-CIPHER: "EDH-RSA-DES-CBC3-SHA keybits 192/192 version TLSv1/SSLv3" TLS-PEER: ) by ajax2.sovam.com with ESMTP id ; Wed, 6 Jun 2001 17:09:17 +0400 Received: from localhost (avn@localhost) by srv2.any (8.11.3/8.11.3) with ESMTP id f56DAW594270; Wed, 6 Jun 2001 17:10:32 +0400 (MSD) (envelope-from avn@any.ru) Date: Wed, 6 Jun 2001 17:10:32 +0400 (MSD) From: "Alexey V. Neyman" X-X-Sender: To: Franck LEVESQUE Cc: Subject: Re: no more 'root' account on my machine... In-Reply-To: <3B1E0BF6.E0E8225D@babel.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello there! First, did you edit /etc/passwd or /etc/master.passwd ? passwd does not hold any passwords and serves only for resolving name/uid/fullname references, while master.passwd holds actual passwords. Second, did you run pwd_mkdb(8) after editing that file? This should be enough IMHO. Regards, Alexey. -------------------------------------+------------------------------ Does the fish swallow the stone? | Regards, Alexey V. Neyman Perhaps, but that is not the point. | mailto: avn@any.ru ---------------------(Pkunk, SC2)----+------------------------------ On Wed, 6 Jun 2001, Franck LEVESQUE wrote: >> Hi, > >> >> First of all, sorry for my bad english skills. >> >> As the newbie I am on FreeBSD (4.3), I did a very stupid thing while >> using vipw : I deleted the root account. >> >> I tryed to correct my problem using the "fix it" floppy, but changing >> the /etc/passwd file is not enough. >> Really I am sorry to bother you with that, but I don't know that much >> about the master.passwd and the way FreeBSD does to authentify users. >> >> Anybody has an idea about the way I shall follow to resolve my problem? > >> Thank you indeed. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 7: 8:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [212.135.162.62]) by hub.freebsd.org (Postfix) with ESMTP id BF16937B407 for ; Wed, 6 Jun 2001 07:08:29 -0700 (PDT) (envelope-from joe@tao.org.uk) Received: by tao.org.uk (Postfix, from userid 100) id ED02856E; Tue, 5 Jun 2001 19:04:47 +0100 (BST) Date: Tue, 5 Jun 2001 19:04:47 +0100 From: Josef Karthauser To: Garance A Drosihn Cc: Dima Dorfman , Peter Seebach , hackers@FreeBSD.ORG Subject: Re: Fixing documented bug in env(1) Message-ID: <20010605190447.B9976@tao.org.uk> References: <20010602041242.849893E33@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="kORqDWCi7qDJ0mEj" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from drosih@rpi.edu on Sat, Jun 02, 2001 at 02:03:38AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --kORqDWCi7qDJ0mEj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 02, 2001 at 02:03:38AM -0400, Garance A Drosihn wrote: >=20 > It also strikes me that this might be another topic to > send thru freebsd-standards@bostonradio.org, as Posix > might have something to say about what's appropriate. >=20 How much traffic does this list produce and how many people are on it? The first I heard of it's existance was a few days ago on one of the lists. May I propose that we make this an offical list so that it can be utilised by the wider community? Joe --kORqDWCi7qDJ0mEj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjsdHz8ACgkQXVIcjOaxUBZvGQCg1PzSGlX5e5umnhcW86dTlFHQ F0YAnRu+0VJK0a+IgLigaRKOxUh2GkIt =ejeE -----END PGP SIGNATURE----- --kORqDWCi7qDJ0mEj-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 7:20:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 7472937B406 for ; Wed, 6 Jun 2001 07:20:40 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (#6@localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.3/8.11.3) with ESMTP id f56EJFn82513; Wed, 6 Jun 2001 10:19:15 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200106061419.f56EJFn82513@whizzo.transsys.com> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: "Daniel C. Sobral" Cc: Giorgos Keramidas , Bob Willcox , Jesper Skriver , hackers list X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: How to disable software TCP checksumming? References: <20010529144114.I19771@luke.immure.com> <20010529221107.C49875@skriver.dk> <20010529155212.M19771@luke.immure.com> <20010530045200.A1031@hades.hell.gr> <3B1CACDA.96599BD5@newsguy.com> <200106051422.f55EM4n78505@whizzo.transsys.com> <3B1DFEAF.927E1DC3@newsguy.com> In-reply-to: Your message of "Wed, 06 Jun 2001 06:58:07 -0300." <3B1DFEAF.927E1DC3@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Jun 2001 10:19:15 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > "Louis A. Mamakos" wrote: > > > > > > > > It seems to me to be kind of moot to check the same value twice, unless > > > you suspect hardware problems. Aren't you talking about two different > > > checks over the same data instead of checksum off-loading? > > > > Suspect hardware problem? Of course you should! That's why memory > > systems have parity or ECC, and I/O buses are similarlly protected. At > > least on real computers. > > > > The link-level CRC only protects the data as it goes over the link > ^^^^^^^^^^ > > After reading the rest of his messages, I'm not so sure, but I would > think he was talking about _transport_ level check sum, and verifying > that with hardward (NIC) instead of software (IP stack). If I'm not mistaken the message that started this thread inquired about adding an option to prevent TCP from doing a checksum, since the fancy gigabit hardware performed reliable link-level error detection itself. I argue that since TCP is an end-to-end transport protocol that individual error detection on a per-hop basis is not sufficient either theoretically or practically. My last message illustrated a number of cases where the transport of the packet over a link was reliably done, but the contents of the packet were corrupted by malfunctioning software or hardware which the end-to-end TCP checksum detected. I have less of an issue with the endpoints of the TCP connection offloading checksum computation to the NIC card, though you're still exposed to a certain class of error, like the PR I referenced. The problem is what happend to your data in intermediate network elements (routers, etc.) between the endpoints of the TCP connection. Louis Mamakos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 7:22: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id D926737B405 for ; Wed, 6 Jun 2001 07:21:59 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f56EIEK86555; Wed, 6 Jun 2001 17:18:14 +0300 (EEST) (envelope-from ru) Date: Wed, 6 Jun 2001 17:18:13 +0300 From: Ruslan Ermilov To: Josef Karthauser Cc: Garance A Drosihn , Dima Dorfman , Peter Seebach , hackers@FreeBSD.ORG Subject: Re: Fixing documented bug in env(1) Message-ID: <20010606171813.A83978@sunbay.com> Mail-Followup-To: Josef Karthauser , Garance A Drosihn , Dima Dorfman , Peter Seebach , hackers@FreeBSD.ORG References: <20010602041242.849893E33@bazooka.unixfreak.org> <20010605190447.B9976@tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010605190447.B9976@tao.org.uk>; from joe@tao.org.uk on Tue, Jun 05, 2001 at 07:04:47PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jun 05, 2001 at 07:04:47PM +0100, Josef Karthauser wrote: > On Sat, Jun 02, 2001 at 02:03:38AM -0400, Garance A Drosihn wrote: > > > > It also strikes me that this might be another topic to > > send thru freebsd-standards@bostonradio.org, as Posix > > might have something to say about what's appropriate. > > > > How much traffic does this list produce and how many people are on it? > The first I heard of it's existance was a few days ago on one of the > lists. > Not too much, wish it'd be higher. > May I propose that we make this an offical list so that it can > be utilised by the wider community? > Bug wollman. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 8:15:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tux.babel.fr (babeliens.babel.fr [212.208.27.125]) by hub.freebsd.org (Postfix) with ESMTP id 6527737B412 for ; Wed, 6 Jun 2001 08:15:01 -0700 (PDT) (envelope-from flevesque@babel.fr) Received: from babel.fr (IDENT:flevesqu@localhost.localdomain [127.0.0.1]) by tux.babel.fr (8.9.3/8.9.3) with ESMTP id QAA04604 for ; Wed, 6 Jun 2001 16:16:25 +0200 Message-ID: <3B1E3B39.F12C4999@babel.fr> Date: Wed, 06 Jun 2001 16:16:25 +0200 From: Franck LEVESQUE Organization: [BaBeL@STaL] X-Mailer: Mozilla 4.72 [fr] (X11; U; Linux 2.2.14-6.1.1 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Re: no more 'root' account on my machine... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thank you very much for your help. I could finally create my root account with your guide lines :) I booted into single user mode, added a correct entry into the /etc/master.passwd file, and used pwd_mkdb -p /etc/master.passwd before changing the root password. Sorry again for my newbie question. Now I know a little bit more about the way FreeBSD manages its accounts :) Have a very good day ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 8:38:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from alacran.it.uc3m.es (alacran.it.uc3m.es [163.117.139.44]) by hub.freebsd.org (Postfix) with ESMTP id 3A84C37B401 for ; Wed, 6 Jun 2001 08:38:22 -0700 (PDT) (envelope-from jrh@it.uc3m.es) Received: from it.uc3m.es (localhost [127.0.0.1]) by alacran.it.uc3m.es (8.10.2/8.10.2/SuSE Linux 8.10.0-0.3) with ESMTP id f56FdKR01056 for ; Wed, 6 Jun 2001 17:39:20 +0200 X-Authentication-Warning: alacran.it.uc3m.es: Host localhost [127.0.0.1] claimed to be it.uc3m.es Message-ID: <3B1E4EA5.528E5D59@it.uc3m.es> Date: Wed, 06 Jun 2001 17:39:17 +0200 From: Juan Fco Rodriguez Hervella X-Mailer: Mozilla 4.74 [es] (X11; U; Linux 2.4.3 i686) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.unix.bsd.freebsd.misc Cc: Lista Subject: On-Line Kernel Debugging Using Remote GDB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi: I am trying to debug a kernel using the steps specified in the Handbook. I follow the steps to compile the kernel, reboot with -d option, and in the other machine, I run gdb -k kernel and so... I have both machines joined with a serial null-modem cable, but when I try: (kgdb) target remote /dev/cuaa0 Remote debugging using /dev/cuaa0 Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Couldn't establish connection to remote target Malformed response to offset query, timeout (kgdb) I am newbie with this topics, I don know where is the problem. How can I test the communication? Do I have to change some specs of device /dev/cuaa0 to communicate with the target box ? Any suggestion will be very appreciated. -- ********************************* Juan F. Rodriguez Hervella Universidad Carlos III de Madrid ******************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 9:12:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nimitz.mcnett (24-130-188-11.san.rr.com [24.130.188.11]) by hub.freebsd.org (Postfix) with ESMTP id 8A3AD37B406 for ; Wed, 6 Jun 2001 09:12:41 -0700 (PDT) (envelope-from mmcnett@cs.ucsd.edu) Received: from cs.ucsd.edu (localhost [127.0.0.1]) by nimitz.mcnett (8.11.1/8.11.1) with ESMTP id f56GGfA00882 for ; Wed, 6 Jun 2001 09:16:41 -0700 (PDT) (envelope-from mmcnett@cs.ucsd.edu) Message-ID: <3B1E5768.8AB37017@cs.ucsd.edu> Date: Wed, 06 Jun 2001 09:16:40 -0700 From: Marvin McNett X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: On-Line Kernel Debugging Using Remote GDB References: <3B1E4EA5.528E5D59@it.uc3m.es> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm not sure if you're already doing this but, on the machine being debugged, you must switch to gdb mode by typing 'gdb' at the DDB prompt. Then, after running gdb -k on your debugging box, go back to the machine being debugged and type 's'. If you're already doing this, then it looks like you've got a communication problem. Let me know and I'll send you more information about my setup. -Marvin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 9:47:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2556437B403; Wed, 6 Jun 2001 09:47:56 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f56Glr628832; Wed, 6 Jun 2001 10:47:53 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.2/8.8.3) with ESMTP id f56GoMl00438; Wed, 6 Jun 2001 10:50:22 -0600 (MDT) Message-Id: <200106061650.f56GoMl00438@billy-club.village.org> To: Poul-Henning Kamp Subject: Re: MFC'ing new md(4) functionality? Cc: obrien@FreeBSD.ORG, Dima Dorfman , hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 05 Jun 2001 18:33:17 +0200." <70325.991758797@critter> References: <70325.991758797@critter> Date: Wed, 06 Jun 2001 10:50:22 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <70325.991758797@critter> Poul-Henning Kamp writes: : In message <20010605013148.A49246@dragon.nuxi.com>, "David O'Brien" writes: : >On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote: : >> Is there any reason not to MFC the new md(4) functionality : > : >Zero reason not to. : : Others see it differently, it would seriously break a lot of : people who are using -stable in embedded applications. : : If we have abandoned the "no changes to API or ABI in -stable" : paradigm, it would be a good idea, but it serious rains on that : rule... I've stated in the past that removing mfs from stable is going to cause me some grief. However, the addition of md won't so long as mfs remains intact. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 9:50:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id D2AC937B417 for ; Wed, 6 Jun 2001 09:50:19 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f56GoI628852; Wed, 6 Jun 2001 10:50:18 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.2/8.8.3) with ESMTP id f56Gqll00452; Wed, 6 Jun 2001 10:52:47 -0600 (MDT) Message-Id: <200106061652.f56Gqll00452@billy-club.village.org> To: j mckitrick Subject: Re: newbussifying drivers Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 05 Jun 2001 18:21:51 BST." <20010605182151.A90883@dogma.freebsd-uk.eu.org> References: <20010605182151.A90883@dogma.freebsd-uk.eu.org> Date: Wed, 06 Jun 2001 10:52:47 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010605182151.A90883@dogma.freebsd-uk.eu.org> j mckitrick writes: : The newbus routines use a certain amount of overhead, but once done, you : forget about it. In some device drivers, the probe methods often need to : try a variety of hardware ports. In the past, inb/outb was used, along with : an often hardcoded port address. : : Does it make sense to call bus_allocate_resource for every hardware port we : probe? What is the best way to handle this so NO inb/out is used, even for : probing? Most of the drivers in the past that have done the soul searching for hardware have been convereted to not do the soul searching but instead rely strictly on the hints. I think that's what we need to do for the parallel drivers as well. If it must do the soul searching, and I see no reason why it should be special as it causes other problems for wiring when you have multiple parallel ports, then you should likely bus_alloc_resource for every hardware address. This gives you a modest probability that those addresses are not used by another device and you won't hork hardware that otherwise resides there. Warenr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 9:53: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id BD67D37B406; Wed, 6 Jun 2001 09:53:00 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f56Gqx628881; Wed, 6 Jun 2001 10:52:59 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.2/8.8.3) with ESMTP id f56GtRl00468; Wed, 6 Jun 2001 10:55:27 -0600 (MDT) Message-Id: <200106061655.f56GtRl00468@billy-club.village.org> To: Nick Hibma Subject: Re: Resource reservation idea Cc: Mike Smith , Jonathan Chen , hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 05 Jun 2001 19:15:30 BST." References: Date: Wed, 06 Jun 2001 10:55:27 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message Nick Hibma writes: : > > - Some dummy driver which grabs the resource. The dummy driver would : > > need to be unloaded when the actual driver needs the resources. : > : > This sounds attractive, but it's hard to find the dummy driver when : > you want to open the bidding for one or more devices again. You also end : > up with the ugly case where the device has more resources than the driver : > uses; you end up needing a placeholder of some sort for these as well, so : > you might as well just built it into the way the bus thinks about child : > devices and be done with it. : : It was suggested some time ago to do this by having a priority value : that indicates a dummy, say -10000. When a driver is loaded, all dummies : are detached and the probe is restarted. The dummies are quiet if not : cold booting to avoi a storm of dummies announcing themselves again and : again. There are some subtle problems with this approach. Specifically, if I have a card in a bus that can live at any address. I load a driver for this card, so the bus reprobes. If all I have to go by is these drivers that have reserved resources, then if we detach them all before doing this, we could have a situation where order matters and the device could get one of the other device's resources. I also recall having a problem by not detaching all the devices at once, but I can't recall what it is at the moment. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 9:54:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 854BC37B409; Wed, 6 Jun 2001 09:54:20 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f56GsJ628894; Wed, 6 Jun 2001 10:54:19 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.2/8.8.3) with ESMTP id f56Gull00481; Wed, 6 Jun 2001 10:56:47 -0600 (MDT) Message-Id: <200106061656.f56Gull00481@billy-club.village.org> To: j mckitrick Subject: Re: newbussifying drivers Cc: Mike Smith , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 05 Jun 2001 23:00:32 BST." <20010605230032.B96188@dogma.freebsd-uk.eu.org> References: <20010605230032.B96188@dogma.freebsd-uk.eu.org> <20010605182151.A90883@dogma.freebsd-uk.eu.org> <200106052032.f55KWTj01513@mass.dis.org> Date: Wed, 06 Jun 2001 10:56:47 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010605230032.B96188@dogma.freebsd-uk.eu.org> j mckitrick writes: : How would you recommending fixing this, taken from the ex driver? By deleting it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 9:57:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 8741237B409; Wed, 6 Jun 2001 09:57:44 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f56Gvh628939; Wed, 6 Jun 2001 10:57:43 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.2/8.8.3) with ESMTP id f56H0Bl00513; Wed, 6 Jun 2001 11:00:11 -0600 (MDT) Message-Id: <200106061700.f56H0Bl00513@billy-club.village.org> To: j mckitrick Subject: Re: newbussifying drivers Cc: Alexander Langer , Mike Smith , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 06 Jun 2001 11:21:51 BST." <20010606112151.D10263@dogma.freebsd-uk.eu.org> References: <20010606112151.D10263@dogma.freebsd-uk.eu.org> <20010605182151.A90883@dogma.freebsd-uk.eu.org> <200106052032.f55KWTj01513@mass.dis.org> <20010605230032.B96188@dogma.freebsd-uk.eu.org> <20010606010426.C28586@zerogravity.kawo2.rwth-aachen.d> Date: Wed, 06 Jun 2001 11:00:11 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010606112151.D10263@dogma.freebsd-uk.eu.org> j mckitrick writes: : | You manually set the correct I/O port in the hints file and then you : : Sorry if i misunderstand, but isn't the hints file only for -current? I was : under the impression it was only to simplify driver development. Hints will be in -stable by the end of this week unless the world explodes at work. In which case they will be in by the end of next week. They are optional in stable. Also, in stable now the hints are codified in the config file for those attributes that we're talking about in this conversation. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 10: 1: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 29A0337B401; Wed, 6 Jun 2001 10:01:04 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f56H12628986; Wed, 6 Jun 2001 11:01:03 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.2/8.8.3) with ESMTP id f56H3Vl00564; Wed, 6 Jun 2001 11:03:31 -0600 (MDT) Message-Id: <200106061703.f56H3Vl00564@billy-club.village.org> Subject: Re: newbussifying drivers Cc: j mckitrick , Mike Smith , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 06 Jun 2001 10:56:47 MDT." <200106061656.f56Gull00481@billy-club.village.org> References: <200106061656.f56Gull00481@billy-club.village.org> <20010605230032.B96188@dogma.freebsd-uk.eu.org> <20010605182151.A90883@dogma.freebsd-uk.eu.org> <200106052032.f55KWTj01513@mass.dis.org> Date: Wed, 06 Jun 2001 11:03:30 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200106061656.f56Gull00481@billy-club.village.org> Warner Losh writes: : In message <20010605230032.B96188@dogma.freebsd-uk.eu.org> j mckitrick writes: : : How would you recommending fixing this, taken from the ex driver? : : By deleting it. Let me expand a little. The reason I advocate deleting it is because there are too many old hunks of random hardware that interact badly with this probe. I've often had to delete the ex driver so that they start working due to this probe. I'd keep the meat of the routine but require -current users to specify an address for cards that aren't in plug and play mode. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 10:32:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hpux36.dc.engr.scu.edu (hpux36.dc.engr.scu.edu [129.210.16.36]) by hub.freebsd.org (Postfix) with ESMTP id 9255137B407 for ; Wed, 6 Jun 2001 10:32:43 -0700 (PDT) (envelope-from dclark@applmath.scu.edu) Received: from localhost (dclark@localhost) by hpux36.dc.engr.scu.edu (8.10.2/8.10.2) with ESMTP id f56HWdi03252 for ; Wed, 6 Jun 2001 10:32:39 -0700 (PDT) Date: Wed, 6 Jun 2001 10:32:39 -0700 (PDT) From: "Dorr H. Clark" To: freebsd-hackers@freebsd.org Subject: need help: gdb -k 4.16/7 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi- < Please cc: me on any answer as I am not subscribed! Thx! > < Also, if this is the wrong list please redirect me! Thx! > I am experimenting with porting an application from the FreeBSD 2.2.x series to a more modern release, and as such I have occaision to debug kernel core files under the old release using the gdb -k option (saved via savecore). The problem is the old kernel has been customized with a different load address (new style 0xC0000000=20 vs. old style 0xF0000000). This change involves=20 updating the include file environment. I have made those changes coherent between the kernel build tree and /usr/include, then rebuilt gdb. The problem is the resulting gdb -k sessions are not fully=20 functional. I would like to know if anyone knows anything about this & can help me with some clues. Specifically, the kernel stack frames are fine, sources are fine, data/bss access is fine,=20 but attempts to access kernel malloc'ed memory fail. The debugger reports that the address is not accessible. The implementation of gdb -k in 4.16 uses a file=20 kvm-fbsd.c which mimics a real kvm access by reading from the core file instead. My understanding is the core file is a physical image of memory, so this kvm emulation has some knowledge of the virtual memory system. I am worried that there are some hidden dependencies on the original memory layout that were not handled when the KERNBASE move was reflected in the include files. After debugging this for some time, in desperation I attempted to port 4.17 and 4.18 back into the old FreeBSD environment, hoping to find a bug fix. What I got instead was a build failure in 4.17: < gdb 4.17 build log excerpt >=20 Graph cycles through config.h `all' not remade because of errors. make all-recursive Making all in doc rm -f gdb gcc -g -O2 -o gdb init.o version.o blockframe.o breakpoint.o findvar.= o stack.o thread.o source.o values.o eval.o valops.o valarith.o valprint.o= printcmd.o symtab.o symfile.o symmisc.o infcmd.o infrun.o command.o expp= rint.o environ.o gdbtypes.o copying.o i386-tdep.o i387-tdep.o solib.o ser-t= cp.o ser-unix.o fork-child.o infptrace.o inftarg.o corelow.o core-aout.o i3= 86b-nat.o remote.o dcache.o remote-utils.o tracepoint.o mem-break.o targ= et.o parse.o language.o c-exp.tab.o jv-exp.tab.o f-exp.tab.o m2-exp.tab.o b= uildsym.o exec.o bcache.o objfiles.o minsyms.o maint.o demangle.o dbxread= =2Eo coffread.o elfread.o dwarfread.o dwarf2read.o mipsread.o stabsread.o = corefile.o c-lang.o ch-exp.o ch-lang.o f-lang.o jv-lang.o jv-valprint.o j= v-typeprint.o m2-lang.o scm-exp.o scm-lang.o scm-valprint.o complaints.o t= ypeprint.o c-typeprint.o ch-typeprint.o f-typeprint.o m2-typeprint.o c-va= lprint.o cp-valprint.o ch-valprint.o f-valprint.o m2-valprint.o nlmread.o = serial.o mdebugread.o os9kread.o top.o utils.o annotate.o main.o inflow.o g= nu-regex.o ../bfd/libbfd.a ../readline/libreadline.a ../opcodes/libopco= des.a ../libiberty/libiberty.a -ltermcap -lm ../libiberty/libiberty.= a =20 gcc: ../libiberty/libiberty.a: No such file or directory gcc: ../libiberty/libiberty.a: No such file or directory *** Error code 1 Stop. < end gdb 4.17 build log excerpt >=20 The 4.18 baseline built fine, but gdb -k is no longer supported! Interestingly, the 4.16 distribution archived at ftp://www.gnu.org does not exactly match the version in the FreeBSD 2.2.x release, and doesn't build cleanly either. The build error from 4.16=20 is here: < gdb 4.16 build log excerpt >=20 if [ -n "" ]; then gcc -O2 -c -DTRAD_CORE -I. -I. -I./../include -g tr= ad-core.c -o pic/trad-core.o; else true; fi gcc -O2 -c -DTRAD_CORE -I. -I. -I./../include -g trad-core.c trad-core.c: In function `trad_unix_core_file_p': trad-core.c:108: `NBPG' undeclared (first use this function) trad-core.c:108: (Each undeclared identifier is reported only once trad-core.c:108: for each function it appears in.) *** Error code 1 Stop. < end gdb 4.16 build log excerpt >=20 Anyone who has any clues as to how to overcome any of these problems, and properly access the old kernel core files using any of the 4.16, 4.17, or 4.18 baselines, please email. Thanks, -Dorr H. Clark School of Engineering Santa Clara University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 10:53: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (Postfix) with ESMTP id 244EA37B403 for ; Wed, 6 Jun 2001 10:53:03 -0700 (PDT) (envelope-from chrisc@vmunix.com) Received: by vnode.vmunix.com (Postfix, from userid 1005) id D52F011; Wed, 6 Jun 2001 13:53:01 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by vnode.vmunix.com (Postfix) with ESMTP id B75BA49A13 for ; Wed, 6 Jun 2001 13:53:01 -0400 (EDT) Date: Wed, 6 Jun 2001 13:53:01 -0400 (EDT) From: Chris Coleman To: hackers@freebsd.org Subject: Softupdates not syncing Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On one of our servers, deleted space is not being freed and causing is to run out of disk space. To test this, I copied a 200 meg file to the /usr partition and then deleted it. I checked df before copying, after copying, and after deleting it. After deleting it, the space never became available. I waited atleast 24 hours just to make sure. 4.2-STABLE FreeBSD 4.2-STABLE #0: Mon Jan 29 10:18:20 PST 2001 I checked the disk space just a minute ago: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 125983 38405 77500 33% / /dev/da0s1e 8229668 7489763 81532 99% /usr procfs 4 4 0 100% /proc Notice how /usr is almost full. There should actually be quite a bit of space available. I mounted /usr2 and then when I umount'd /usr2, the missing space on /usr magically came back. Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 125983 38405 77500 33% / /dev/da0s1e 8229668 6702791 868504 89% /usr procfs 4 4 0 100% /proc That is almost 800Mb that was locked up. Am I doing something wrong? or is this a bug? I didn't see anything in a quick search of the mailing lists. CC me I'm not on the list. Chris Coleman Editor in Chief Daemon News E-Zine http://www.daemonnews.org Print Magazine http://magazine.daemonnews.org Open Packages http://www.openpackages.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 11: 2:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from server.soekris.com (soekris.com [216.15.61.44]) by hub.freebsd.org (Postfix) with ESMTP id 93AB637B409 for ; Wed, 6 Jun 2001 11:02:39 -0700 (PDT) (envelope-from soren@soekris.com) Received: from soekris.com (soren.soekris.com [192.168.1.4]) by server.soekris.com (8.9.2/8.9.2) with ESMTP id LAA04559 for ; Wed, 6 Jun 2001 11:02:42 -0700 (PDT) (envelope-from soren@soekris.com) Message-ID: <3B1E703D.11D7690F@soekris.com> Date: Wed, 06 Jun 2001 11:02:37 -0700 From: Soren Kristensen Organization: Soekris Engineering X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Making support for ADSL interface ?? Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Everybody, I would like to inquire about what it would take to make a driver for a specific ADSL board with direct PCI interface to FreeBSD.... First, lets assume that I will supply boards, and that all necessery documentation will be available. How good is FreeBSD current structures for running ADSL, I'm thinking about the ATM support already present, and probably using netgraph ? I would need support for the most common protocols used worldwide, t.ex PPPoATM, IPoATM.... Next, is there any takers for doing the actual work ? I would probably need somebody who has some knowledge about ADSL and ATM, and have access to some equipment and/or lines for testing. I will probably be able to offer some limited payment for the work, the driver will probably be possible to release under BSD license, and the resulting hardware will be available at low cost. Regards, Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 11:35:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nimitz.mcnett (cse-air-dhcp-208.ucsd.edu [132.239.10.208]) by hub.freebsd.org (Postfix) with ESMTP id 7440A37B401 for ; Wed, 6 Jun 2001 11:35:14 -0700 (PDT) (envelope-from mmcnett@cs.ucsd.edu) Received: from cs.ucsd.edu (localhost [127.0.0.1]) by nimitz.mcnett (8.11.1/8.11.1) with ESMTP id f56IdLU00473; Wed, 6 Jun 2001 11:39:22 -0700 (PDT) (envelope-from mmcnett@cs.ucsd.edu) Message-ID: <3B1E78D9.4F30DE9E@cs.ucsd.edu> Date: Wed, 06 Jun 2001 11:39:21 -0700 From: Marvin McNett X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Cc: Juan Fco Rodriguez Hervella Subject: Re: On-Line Kernel Debugging Using Remote GDB References: <3B1E4EA5.528E5D59@it.uc3m.es> <3B1E54FF.7C2CCEA9@cs.ucsd.edu> <3B1E67A2.B86660F1@it.uc3m.es> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Looks like you forgot to set the 'flags 080' on the sio device of the machine being debugged. This is a logical OR with what was set before. So, for me, I changed the line in my kernel config device sio0 at isa? port IO_COM1 flags 0x10 irq 4 to device sio0 at isa? port IO_COM1 flags 0x90 irq 4 and attach my serial cable to the first serial port of the machine being debugged. Also, you want to use target remote /dev/cuaa0 (the dialout serial port) assuming you've attached your serial cable to the first serial port of the debugging host. Finally, you won't have any sioX devices in /dev, so stop looking for them. :-) Juan Fco Rodriguez Hervella wrote: > When I type 'gdb', this happens: > > gdb> gdb > gdb> No gdb port enable. Set flag 0x80 on desired port > gdb> in your configuration file (currently sio only) > > Other question related: > > Which is the difference between /dev/cuaaX and /dev/ttydX ? > I have to type in REMOTE machine 'target remote /dev/cuaaX or > /dev/ttydX' ? > and also, I dont find the sioX devices in /dev. > > Thansk very much. > > Marvin McNett escribió: > > > > I'm not sure if you're already doing this but, on the machine being > > debugged, you must switch to gdb mode by typing 'gdb' at the DDB > > prompt. Then, after running gdb -k on your debugging box, go back to > > the machine being debugged and type 's'. If you're already doing this, > > then it looks like you've got a communication problem. Let me know and > > I'll send you more information about my setup. > > > > -Marvin > > -- > ********************************* > Juan F. Rodriguez Hervella > Universidad Carlos III de Madrid > ******************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 12:12:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 66E2237B407 for ; Wed, 6 Jun 2001 12:12:51 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (#6@localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.3/8.11.3) with ESMTP id f56JCmn17095; Wed, 6 Jun 2001 15:12:48 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200106061912.f56JCmn17095@whizzo.transsys.com> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Soren Kristensen Cc: freebsd-hackers@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: Making support for ADSL interface ?? References: <3B1E703D.11D7690F@soekris.com> In-reply-to: Your message of "Wed, 06 Jun 2001 11:02:37 PDT." <3B1E703D.11D7690F@soekris.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Wed, 06 Jun 2001 15:12:48 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > How good is FreeBSD current structures for running ADSL, I'm thinking a= bout the > ATM support already present, and probably using netgraph ? I would need= support > for the most common protocols used worldwide, t.ex PPPoATM, IPoATM.... You'd also need to support PPPoE, which on most ADSL systems appears as PPP on Ethernet as RFC-1490 bridged encapsulation of the ethernet frames in AAL5 ATM cells. It's unclear that this is worth doing at the ATM level since the CPE devices with an Ethernet are fairly inexpensive; the existing Ethernet interface might be the most cost effective. There's also limited standardization on management interfaces for ADSL CPE equipment. It's been a couple of years since I've been involved with the ADSL forum, but there were proposes to have some management channel to the CPE device (perhaps using ILMI? I don't recall). = Louis Mamakos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 12:31:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from server.soekris.com (soekris.com [216.15.61.44]) by hub.freebsd.org (Postfix) with ESMTP id 98D7E37B406 for ; Wed, 6 Jun 2001 12:31:27 -0700 (PDT) (envelope-from soren@soekris.com) Received: from soekris.com (soren.soekris.com [192.168.1.4]) by server.soekris.com (8.9.2/8.9.2) with ESMTP id MAA04748; Wed, 6 Jun 2001 12:31:20 -0700 (PDT) (envelope-from soren@soekris.com) Message-ID: <3B1E8502.59E4F404@soekris.com> Date: Wed, 06 Jun 2001 12:31:14 -0700 From: Soren Kristensen Organization: Soekris Engineering X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Louis A. Mamakos" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Making support for ADSL interface ?? References: <3B1E703D.11D7690F@soekris.com> <200106061912.f56JCmn17095@whizzo.transsys.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Louis, Thanks for your reply. "Louis A. Mamakos" wrote: > > You'd also need to support PPPoE, which on most ADSL systems appears > as PPP on Ethernet as RFC-1490 bridged encapsulation of the ethernet > frames in AAL5 ATM cells. It's unclear that this is worth doing at > the ATM level since the CPE devices with an Ethernet are fairly > inexpensive; the existing Ethernet interface might be the most cost > effective. I will need to support PPPoE, but netgraph can probably take care of that.... But directly, as the point is to have one single low cost box with everything, that why I'm working on doing an ADSL board with PCI interface.... And I might even put the ADSL interface on the mainboard. > There's also limited standardization on management interfaces for ADSL > CPE equipment. It's been a couple of years since I've been involved > with the ADSL forum, but there were proposes to have some management > channel to the CPE device (perhaps using ILMI? I don't recall). > The configuration and management have moved forward, take a look at the DSL Forum TR-037.... Regards, Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 12:44:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [209.247.77.155]) by hub.freebsd.org (Postfix) with ESMTP id 1E82B37B403 for ; Wed, 6 Jun 2001 12:44:56 -0700 (PDT) (envelope-from gordont@bluemtn.net) Received: from localhost (gordont@localhost) by sdmail0.sd.bmarts.com (8.11.3/8.11.2/BMA1.1) with ESMTP id f56JgGL75934 for ; Wed, 6 Jun 2001 12:42:16 -0700 (PDT) Date: Wed, 6 Jun 2001 12:42:15 -0700 (PDT) From: Gordon Tetlow X-X-Sender: To: Subject: make installworld hacking Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have a problem, I installed a bunch of machines with a very stripped down set of distributions (bin, man, dict, krb5). I'd like to update the machines, but when I do an installworld, it's going to install a bunch more than that. Is there some way of only upgrading only the bin distribution (a la make distribute)? If not, would people be interested in me attempting such a feat? -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 13:59:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id C2DEA37B403 for ; Wed, 6 Jun 2001 13:59:31 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (#6@localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.3/8.11.3) with ESMTP id f56KxSn26701; Wed, 6 Jun 2001 16:59:28 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200106062059.f56KxSn26701@whizzo.transsys.com> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Soren Kristensen Cc: freebsd-hackers@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: Making support for ADSL interface ?? References: <3B1E703D.11D7690F@soekris.com> <200106061912.f56JCmn17095@whizzo.transsys.com> <3B1E8502.59E4F404@soekris.com> In-reply-to: Your message of "Wed, 06 Jun 2001 12:31:14 PDT." <3B1E8502.59E4F404@soekris.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Wed, 06 Jun 2001 16:59:28 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Louis, > = > Thanks for your reply. > = > "Louis A. Mamakos" wrote: > > = > > You'd also need to support PPPoE, which on most ADSL systems appears > > as PPP on Ethernet as RFC-1490 bridged encapsulation of the ethernet > > frames in AAL5 ATM cells. It's unclear that this is worth doing at > > the ATM level since the CPE devices with an Ethernet are fairly > > inexpensive; the existing Ethernet interface might be the most cost > > effective. > = > I will need to support PPPoE, but netgraph can probably take care of > that.... But directly, as the point is to have one single low cost box > with everything, that why I'm working on doing an ADSL board with PCI > interface.... And I might even put the ADSL interface on the mainboard.= What I'm not sure is if the netgraph code currently has hooks into the ATM network interfaces, and if it "knows" about ethernet frame bridge encapsulation. I'm guessing that the netgraph platform would make the most sense to support this kind of application. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 14:12:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id D34F137B403 for ; Wed, 6 Jun 2001 14:12:28 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f56LCSd19141 for hackers@freebsd.org; Wed, 6 Jun 2001 14:12:28 -0700 Date: Wed, 6 Jun 2001 14:12:28 -0700 From: Brooks Davis To: hackers@freebsd.org Subject: cloning network interfaces Message-ID: <20010606141228.A13639@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm working on a project that will be using a whole lot of gif(4) devices. Since I'd written an almost-clone patch for snp and gif's current lack of cloning annoyed me, I figured I'd take a look at writing a patch for it. Unfortunately, it appears to be rather more complicated then I had hoped. With network devices that are also normal devices the way tun is, you do this by just implementing a dev_clone event handler so when the user attempts to open a non-existent instance it's created. The problem with gif is that there's no device in /dev to open. Since most network devices at attached to hardware this usually doesn't matter, but in this case it does. In Solaris the ip.tunX devices have the same problem, but they have a solution of sorts. With them you simply call "ifconfig ip.tun0 plumb" to create ip.tun0. Is this the sort of solution we'd like to use in FreeBSD? Do we instead want to make the network interface name space work like the devfs name space so "ifconfig gif blah" works? How would this work anyway? Comments, thoughts, ideas? -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7Hpy7XY6L6fI4GtQRAksEAJ40w1gR1WBloa0KVljk40F7uP0c+wCfapX1 43wemuH80Ztxovg6YdwncnE= =HJ2e -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 14:17:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id DF39837B403 for ; Wed, 6 Jun 2001 14:17:12 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f56LGv185876; Wed, 6 Jun 2001 23:16:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Brooks Davis Cc: hackers@FreeBSD.ORG Subject: Re: cloning network interfaces In-Reply-To: Your message of "Wed, 06 Jun 2001 14:12:28 PDT." <20010606141228.A13639@Odin.AC.HMC.Edu> Date: Wed, 06 Jun 2001 23:16:57 +0200 Message-ID: <85874.991862217@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010606141228.A13639@Odin.AC.HMC.Edu>, Brooks Davis writes: >With network devices that are also normal devices the way tun is, >you do this by just implementing a dev_clone event handler so when the >user attempts to open a non-existent instance it's created. The problem >with gif is that there's no device in /dev to open. Since most network >devices at attached to hardware this usually doesn't matter, but in this >case it does. > >[...] > >How would this work anyway? > >Comments, thoughts, ideas? The quick and dirty way: Make a clone handler despite the fact that there is no /dev entry needed. You don't actually have to create a dev entry in the clone handler, you could just create the gif_interface. Applications would then: stat("/dev/gif345") /* Ignore error */ system("ifconfig gif345 bla bla bla"); The slower but less dirty: Make a sysctl which returns an integer which is the next free gif device. The really slow and very dirty: Implement cloning in ifconfig. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 14:46:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from luke.immure.com (luke.immure.com [207.8.42.74]) by hub.freebsd.org (Postfix) with ESMTP id 92CD337B407 for ; Wed, 6 Jun 2001 14:46:45 -0700 (PDT) (envelope-from bob@luke.immure.com) Received: (from bob@localhost) by luke.immure.com (8.11.2/8.11.3) id f56LkFt86539; Wed, 6 Jun 2001 16:46:15 -0500 (CDT) (envelope-from bob) Date: Wed, 6 Jun 2001 16:46:15 -0500 From: Bob Willcox To: "Daniel C. Sobral" Cc: "Louis A. Mamakos" , "Daniel C. Sobral" , Giorgos Keramidas , Jesper Skriver , hackers list Subject: Re: How to disable software TCP checksumming? Message-ID: <20010606164615.A82579@luke.immure.com> Reply-To: Bob Willcox References: <20010529144114.I19771@luke.immure.com> <20010529221107.C49875@skriver.dk> <20010529155212.M19771@luke.immure.com> <20010530045200.A1031@hades.hell.gr> <3B1CACDA.96599BD5@newsguy.com> <200106051422.f55EM4n78505@whizzo.transsys.com> <3B1DFEAF.927E1DC3@newsguy.com> <200106061419.f56EJFn82513@whizzo.transsys.com> <3B1E8F6C.3000702@tcoip.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B1E8F6C.3000702@tcoip.com.br>; from daniel.sobral@tcoip.com.br on Wed, Jun 06, 2001 at 05:15:40PM -0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG As the originator of this thread (sorry), I thought I'd clear up some of the speculation as to what I'm trying to do. :-) Our adapter card is a GSN adapter, focused on the ST protocol over a hippi-6400 link. We support IP on this adapter as well but that's not its expected primary use. In asking the original question, I was trying to find out how to disable the IP/TCP software checksums and rely on the link layer LCRC and ECRC (I think that's what they're called) checks. The LCRC is a hop to hop CRC that is applied to each 32 byte micropacket that is transmitted. The ECRC is an overll message CRC that covers all micropackets of the message. It is my expectation that these two CRCs will be adaquate to catch any errors that occur within the GSN network. Note that our card has no IP specific checksum support (it does for ST) so for packets originating from, or destined to, outside of the GSN network we _must_ do the software checksuming. I understand this. My purpose in being able to turn software checksums off was strictly to measure the performance advantage of doing so. In any real network environment the software checksums are required with this card. Thanks, Bob On Wed, Jun 06, 2001 at 05:15:40PM -0300, Daniel C. Sobral wrote: > Louis A. Mamakos wrote: > > > > > If I'm not mistaken the message that started this thread inquired > > about adding an option to prevent TCP from doing a checksum, since > > the fancy gigabit hardware performed reliable link-level error detection > > > I do not recall he ever mentioning "link-level". Either my mind removed > it, or yours inserted it. :-) > > > > itself. I argue that since TCP is an end-to-end transport protocol that > > individual error detection on a per-hop basis is not sufficient either > > theoretically or practically. My last message illustrated a number of > > cases where the transport of the packet over a link was reliably > > done, but the contents of the packet were corrupted by malfunctioning > > software or hardware which the end-to-end TCP checksum detected. > > > > I have less of an issue with the endpoints of the TCP connection > > offloading checksum computation to the NIC card, though you're > > still exposed to a certain class of error, like the PR I referenced. > > The problem is what happend to your data in intermediate network > > elements (routers, etc.) between the endpoints of the TCP connection. > > > > Louis Mamakos > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > -- > Daniel C. Sobral (8-DCS) > Daniel.Sobral@tcoip.com.br > dcs@newsguy.com > dcs@freebsd.org > capo@notorious.bsdconspiracy.net > > ... if the church put in half the time on covetousness that it does > on lust, this would be a better world. > -- Garrison Keillor, "Lake Wobegon Days" -- Bob Willcox All men profess honesty as long as they can. bob@vieo.com To believe all men honest would be folly. Austin, TX To believe none so is something worse. -- John Quincy Adams To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 15:14:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from valu.uninet.ee (valu.uninet.ee [194.204.34.51]) by hub.freebsd.org (Postfix) with ESMTP id 2247C37B403 for ; Wed, 6 Jun 2001 15:14:33 -0700 (PDT) (envelope-from taavi@uninet.ee) Received: by valu.uninet.ee (Postfix, from userid 1002) id 1580E36421; Thu, 7 Jun 2001 00:14:30 +0200 (EET) Received: from localhost (localhost [127.0.0.1]) by valu.uninet.ee (Postfix) with ESMTP id 110E632616; Thu, 7 Jun 2001 00:14:30 +0200 (EET) Date: Thu, 7 Jun 2001 00:14:29 +0200 (EET) From: Taavi Talvik To: Soren Kristensen Cc: freebsd-hackers@freebsd.org Subject: Re: Making support for ADSL interface ?? In-Reply-To: <3B1E703D.11D7690F@soekris.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 6 Jun 2001, Soren Kristensen wrote: If you will give all neccessary documentation and microcode (for chipsets), then it is definitely interesting. I have unsuccessfully discussed writing drivers for ADSL cards with several vendors (alcatel, adi, efficient) but no one have not had courage to give out real information. Even released linux drivers are mostly fakes - some kernel modules providing ioctl interface for binary only userland parts. When driver for hardware is available, I believe, that then freebsd community has enough people to develop surrounding infrastructure further. > I would like to inquire about what it would take to make a driver for a specific > ADSL board with direct PCI interface to FreeBSD.... > > First, lets assume that I will supply boards, and that all necessery > documentation will be available. > > How good is FreeBSD current structures for running ADSL, I'm thinking about the > ATM support already present, and probably using netgraph ? I would need support > for the most common protocols used worldwide, t.ex PPPoATM, IPoATM.... > > Next, is there any takers for doing the actual work ? I would probably need > somebody who has some knowledge about ADSL and ATM, and have access to some > equipment and/or lines for testing. best regards, taavi PS. If only someone would provide microcode and little bit additional information for compleating driver for efficient 3060/3061 pci cards (http://home.uninet.ee/~taavi/lanai/) :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 15:36: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from jhs.muc.de (jhs.muc.de [193.149.49.84]) by hub.freebsd.org (Postfix) with ESMTP id 0599337B401; Wed, 6 Jun 2001 15:36:00 -0700 (PDT) (envelope-from jhs@jhs.muc.de) Received: (from jhs@localhost) by jhs.muc.de (8.11.0/8.11.0) id f56LUvT52317; Wed, 6 Jun 2001 21:30:57 GMT (envelope-from jhs) Date: Wed, 6 Jun 2001 21:30:57 GMT Message-Id: <200106062130.f56LUvT52317@jhs.muc.de> To: hackers@freebsd.org Cc: jkh@freebsd.org Subject: 4.3-RELEASE/src/usr.sbin/pkg_install/sign/ needs src/crypto not on CD From: "Julian Stacey" Organization: Vector Systems Ltd - Munich Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 4.3-RELEASE/src/usr.sbin/pkg_install/sign/ from cdrom needs to include: openssl/err.h openssl/evp.h openssl/objects.h openssl/pem.h openssl/rsa.h openssl/sha.h openssl/ssl.h openssl/x509.h They are not on cdrom src/, But are in src/ from CVS. src/crypto/heimdal/lib/roken/err.h src/crypto/kerberosIV/lib/roken/err.h src/crypto/openssh/rsa.h src/crypto/openssl/crypto/err/err.h src/crypto/openssl/crypto/evp/evp.h src/crypto/openssl/crypto/objects/objects.h src/crypto/openssl/crypto/pem/pem.h src/crypto/openssl/crypto/rsa/rsa.h src/crypto/openssl/crypto/sha/sha.h src/crypto/openssl/crypto/x509/x509.h src/crypto/openssl/ssl/ssl.h src/include/err.h src/lib/libmd/sha.h src/sys/i386/isa/ic/rsa.h It compiles OK after: (cd ..../src.cvsup ; tar cf - crypto kerberos5 kerberosIV secure ) | tar xf - Whoever builds BSDI CDs these days (jkh ? cc'd) may want to check the `munitions stripped' CD src/ versions can compile on binary systems that also have only a `munition stripped' /usr/include/ ? Hopefully soon all this stripping for USA Munitions & Patents etc may be history. An analysis of the content of src/ for 3 versions: CD From the ISO image of the cdrom on ftp.freebsd.org CTM As extracted from a cvs tree built from cvs-cur.7200xEmpty.gz + deltas to cvs-cur 7323 CVSUP As extracted from a cvs tree built from a cvsup tree For both CTM & CVSUP, the subsequent cvs commands were: cvs -R export -r RELENG_4_3_0_RELEASE src Result: src/ COMPONENT CD CTM CVSUP COMMENT CVS/ 1 0 0 5K Entries Repository Root Tag crypto/ 0 0 1 27 Meg kerberos5/ 0 1 1 120 K kerberosIV/ 0 1 1 125 K secure/ 0 0 1 274 K sys/crypto/ 1 0 1 236 K 0 = Missing, 1 = In src/ PS Chuck R. is looking at things missing from CTM CVS version of src/, so need to alert him. - Julian Stacey Unix Consultant - Munich Germany http://bim.bsn.com/~jhs/ Ihr Rauchen => mein allergischer Kopfschmerz ! Kau/Schnupftabak probieren ! Like Linux ? Then also look at FreeBSD with its 5000+ packages ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 17: 1:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 951CC37B403; Wed, 6 Jun 2001 17:01:30 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f570BFB01284; Wed, 6 Jun 2001 17:11:15 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106070011.f570BFB01284@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: Nick Hibma , Mike Smith , Jonathan Chen , hackers@FreeBSD.ORG Subject: Re: Resource reservation idea In-reply-to: Your message of "Wed, 06 Jun 2001 10:55:27 MDT." <200106061655.f56GtRl00468@billy-club.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Jun 2001 17:11:15 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I appear to have missed some of this thread. Dang. > : > > - Some dummy driver which grabs the resource. The dummy driver would > : > > need to be unloaded when the actual driver needs the resources. > : > > : > This sounds attractive, but it's hard to find the dummy driver when > : > you want to open the bidding for one or more devices again. You also end > : > up with the ugly case where the device has more resources than the driver > : > uses; you end up needing a placeholder of some sort for these as well, so > : > you might as well just built it into the way the bus thinks about child > : > devices and be done with it. > : > : It was suggested some time ago to do this by having a priority value > : that indicates a dummy, say -10000. When a driver is loaded, all dummies > : are detached and the probe is restarted. The dummies are quiet if not > : cold booting to avoi a storm of dummies announcing themselves again and > : again. > > There are some subtle problems with this approach. Specifically, if I > have a card in a bus that can live at any address. I load a driver > for this card, so the bus reprobes. If all I have to go by is these > drivers that have reserved resources, then if we detach them all > before doing this, we could have a situation where order matters and > the device could get one of the other device's resources. Nick's point is that you only kick off the dummies. In reality, all this is bickering about is, "what is the container object for resources"? The approach that requires a dummy driver asserts that the container object is the driver instance. This is a much, much harder approach than asserting that the container object is the device instance. In practise, if you want a driver instance holding the resources, you have to do this: - create a device for every child on the bus. - attach drivers to as many children as possible. Force them to allocate *all* their resources, not just the ones they want (this is difficult). - attach a dummy driver to the rest of the children, and force it to allocate all the resources the child has. The second step is actually more common (and more irritating) than you think. It almost forces you to take the other approach anyway: - create a device for every child on the bus. - allocate all the child's resources and attach them to the device's ivars (using eg. a resource list). - attach drivers to children. When a child asks for a resource, just hand them the resource you've already allocated. I've coded this second approach, and it works well. Note that all of this is really only relevent to busses like PCI where the existence of a resource forcibly implies that it's enabled (with some special cases). With something like pccard where you can move the mapping windows around in the bridge, it's less of an issue. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 18:57:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 9FDFA37B403 for ; Wed, 6 Jun 2001 18:57:27 -0700 (PDT) (envelope-from obrien@nuxi.ucdavis.edu) Received: from dragon.nuxi.com (root@trang.nuxi.com [206.40.252.115]) by relay.nuxi.com (8.11.2/8.11.2) with ESMTP id f571vRR16525; Wed, 6 Jun 2001 18:57:27 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f571vQM46117; Wed, 6 Jun 2001 18:57:26 -0700 (PDT) (envelope-from obrien) Date: Wed, 6 Jun 2001 18:57:26 -0700 From: "David O'Brien" To: "Dorr H. Clark" Cc: freebsd-hackers@freebsd.org Subject: Re: need help: gdb -k 4.16/7 Message-ID: <20010606185726.A46049@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dclark@applmath.scu.edu on Wed, Jun 06, 2001 at 10:32:39AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jun 06, 2001 at 10:32:39AM -0700, Dorr H. Clark wrote: > Interestingly, the 4.16 distribution archived at ftp://www.gnu.org > does not exactly match the version in the FreeBSD 2.2.x release, > and doesn't build cleanly either. Not sure why you find this so surprising. Install the 2.2.x sources and you will have the gdb sources that built the original gdb. If you want to update that to 4.17 or higher, use CVS to find the changes from the vendor branch and you will then have our modifications. Alternately, you could get the RCS files for 2.2.x's GDB and do a vendor import of 4.17 and fix the merge conflicts. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 19:41:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id BB07B37B405 for ; Wed, 6 Jun 2001 19:41:11 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id 5403A3E0B; Wed, 6 Jun 2001 19:41:10 -0700 (PDT) To: Poul-Henning Kamp Cc: hackers@freebsd.org Subject: Re: MFC'ing new md(4) functionality? In-Reply-To: <70325.991758797@critter>; from phk@critter.freebsd.dk on "Tue, 05 Jun 2001 18:33:17 +0200" Date: Wed, 06 Jun 2001 19:41:10 -0700 From: Dima Dorfman Message-Id: <20010607024110.5403A3E0B@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > In message <20010605013148.A49246@dragon.nuxi.com>, "David O'Brien" writes: > >On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote: > >> Is there any reason not to MFC the new md(4) functionality > > > >Zero reason not to. > > Others see it differently, it would seriously break a lot of > people who are using -stable in embedded applications. > > If we have abandoned the "no changes to API or ABI in -stable" > paradigm, it would be a good idea, but it serious rains on that > rule... I don't think it would be much of a practical problem for anyone since the old behvior can be emulated with the new md pretty easily, but you're right that it isn't appropriate to break compatibility in -stable. It's probably possible to retrofit the old behavior into the new code, but I think that's too much evil for too little gain. Dima Dorfman dima@unixfreak.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 19:44:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id ECEEA37B408 for ; Wed, 6 Jun 2001 19:44:55 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id 9362D3E0B; Wed, 6 Jun 2001 19:44:55 -0700 (PDT) To: Warner Losh Cc: Poul-Henning Kamp , hackers@FreeBSD.ORG Subject: Re: MFC'ing new md(4) functionality? In-Reply-To: <200106061650.f56GoMl00438@billy-club.village.org>; from imp@village.org on "Wed, 06 Jun 2001 10:50:22 -0600" Date: Wed, 06 Jun 2001 19:44:55 -0700 From: Dima Dorfman Message-Id: <20010607024455.9362D3E0B@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Warner Losh writes: > In message <70325.991758797@critter> Poul-Henning Kamp writes: > : In message <20010605013148.A49246@dragon.nuxi.com>, "David O'Brien" writes: > : >On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote: > : >> Is there any reason not to MFC the new md(4) functionality > : > > : >Zero reason not to. > : > : Others see it differently, it would seriously break a lot of > : people who are using -stable in embedded applications. > : > : If we have abandoned the "no changes to API or ABI in -stable" > : paradigm, it would be a good idea, but it serious rains on that > : rule... > > I've stated in the past that removing mfs from stable is going to > cause me some grief. However, the addition of md won't so long as mfs > remains intact. I don't think anybody is even remotely suggesting that MFS be removed, but someone (other than you) might get bitten by a change of this sort. I guess it's just a matter of whether the new functionality (and giving people a head start integrating the new behavior into their systems) is worth burning however many people depend on the old behavior. Dima Dorfman dima@unixfreak.org > > Warner > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 21:22: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from core.usrlib.org (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id 0700337B405 for ; Wed, 6 Jun 2001 21:21:55 -0700 (PDT) (envelope-from ajh3@core.usrlib.org) Received: by core.usrlib.org (Postfix, from userid 1001) id E53AFA874; Wed, 6 Jun 2001 23:20:45 -0500 (CDT) Date: Wed, 6 Jun 2001 23:20:45 -0500 From: Andrew Hesford To: FreeBSD-hackers Subject: XFree86 4.1.0 and i810 Message-ID: <20010606232045.A453@core.usrlib.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Loop: Andrew Hesford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Many have had problems with the XFree86 and i810 or i815 chipsets under FreeBSD. Specifically, the server crashes after switching to a text console and switching back to the console X is running on. Unlike versions 4.0.2 and 4.0.3 (4.0.1 magically works for me), 4.1.0 prints an error message: xf86BindGARTMemory: binding of gart memory with key %d at offset 0x%x failed (%s), where %d, %x, and %s all have their standard C interpretations. %s is the string produced by interpreting the global variable errno as set by ioctl. The file where the error occurs is in (relative to the xc directory) programs/Xserver/hw/xfree86/os-support/bsd/lnx_agp.c (a link to ../linux/lnx_agp.c), line 257. The problem is a failed AGPIOC_BIND ioctl call. The variable errno is set to 2, or "No such file or directory." The biggest problem with the crashing server is that it will not restart properly until the machine is shutdown; it seems the GART is not cleared after the crash. However, I have not investigated this at all. I submit this here in the hopes that somebody who understands ioctl (specifically AGPIOC_BIND, defined in /usr/include/sys/agpio.h) might be able to explain why I'm getting errno=2. I can't see why this specific problem would occur, unless the ioctl is trying to access the AGP GART at some device node other than /dev/agpgart. I hope somebody can provide more information. I am in the process of fetching and extracting the XFree86 4.0.1 sources, I will take a look at how they handled the ioctl. Unfortunately, I do not know enough about the design of the FreeBSD kernel to go poking in there; if XFree86 4.0.1 can't offer some hints on the right way to handle things, I'm fresh out of ideas. -- Andrew Hesford ajh3@usrlib.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 21:39:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id CD9FA37B405 for ; Wed, 6 Jun 2001 21:39:41 -0700 (PDT) (envelope-from dphoenix@bravenet.com) Received: (qmail 27172 invoked by uid 1000); 7 Jun 2001 04:39:40 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jun 2001 04:39:40 -0000 Date: Wed, 6 Jun 2001 21:39:39 -0700 (PDT) From: Dan Phoenix To: freebsd-hackers@freebsd.org Subject: rpc.statd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jun 6 18:48:10 www rpc.statd: invalid hostname to sm_stat: ^X^X^Z ^Z%8x%8x%8x%8x%8x%8x%8x%8x%8x%62716x%hn%51859x%hnM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM- ^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM -^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^P M-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^ PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM- ^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM -^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^P M-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^ PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM- ^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^P this is a message in messages before a kernel paniced on freebsd 4.3. I have token liberty of disabling, what does this look like to you guys. -- Dan +------------------------------------------------------+ | BRAVENET WEB SERVICES | | dan@bravenet.com | | screen;cd /usr/src;make buildworld;cd ~ | | cp MYKERNEL /sys/i386/conf;cd /usr/src | | make buildkernel KERNCONF=MYKERNEL | |make installkernel KERNCONF=MYKERNEL;make installworld| +______________________________________________________+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 21:50:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tomts13-srv.bellnexxia.net (tomts13.bellnexxia.net [209.226.175.34]) by hub.freebsd.org (Postfix) with ESMTP id 62F3337B414 for ; Wed, 6 Jun 2001 21:50:26 -0700 (PDT) (envelope-from matt@xena.gsicomp.on.ca) Received: from xena.gsicomp.on.ca ([64.228.152.235]) by tomts13-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010607045025.KZYQ6458.tomts13-srv.bellnexxia.net@xena.gsicomp.on.ca>; Thu, 7 Jun 2001 00:50:25 -0400 Received: from localhost (matt@localhost) by xena.gsicomp.on.ca (8.11.1/8.11.1) with ESMTP id f574lmp35080; Thu, 7 Jun 2001 00:47:49 -0400 (EDT) (envelope-from matt@xena.gsicomp.on.ca) Date: Thu, 7 Jun 2001 00:47:48 -0400 (EDT) From: Matthew Emmerton To: Dan Phoenix Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: rpc.statd In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 6 Jun 2001, Dan Phoenix wrote: > > Jun 6 18:48:10 www rpc.statd: invalid hostname to > sm_stat: ^X^X^Z > ^Z%8x%8x%8x%8x%8x%8x%8x%8x%8x%62716x%hn%51859x%hnM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM- [ snip ] It's some l33t h4x0r attemting to use a Linux RPC exploit against your FreeBSD machine. From what I've been told, It's harmless (since FreeBSD never had the hole that Linux did), and I see it quite often on some of the public boxes that I run. Are you absolutely sure that this was the cause of your kernel panic? -- Matt Emmerton GSI Computer Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 22:34: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from core.usrlib.org (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id 24B6137B409 for ; Wed, 6 Jun 2001 22:33:59 -0700 (PDT) (envelope-from ajh3@core.usrlib.org) Received: by core.usrlib.org (Postfix, from userid 1001) id 19241A859; Thu, 7 Jun 2001 00:32:50 -0500 (CDT) Date: Thu, 7 Jun 2001 00:32:50 -0500 From: Andrew Hesford To: Andrew Hesford Cc: FreeBSD-hackers Subject: Re: XFree86 4.1.0 and i810 Message-ID: <20010607003250.B40894@core.usrlib.org> References: <20010606232045.A453@core.usrlib.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010606232045.A453@core.usrlib.org>; from ajh3@usrlib.org on Wed, Jun 06, 2001 at 11:20:45PM -0500 X-Loop: Andrew Hesford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jun 06, 2001 at 11:20:45PM -0500, Andrew Hesford wrote: > I hope somebody can provide more information. I am in the process of > fetching and extracting the XFree86 4.0.1 sources, I will take a look at > how they handled the ioctl. Unfortunately, I do not know enough about > the design of the FreeBSD kernel to go poking in there; if XFree86 4.0.1 > can't offer some hints on the right way to handle things, I'm fresh out > of ideas. The XFree86 4.0.1 sources *did* offer a helpful hint. I have posted another email which includes a patch to fix the buggy i810 driver. -- Andrew Hesford ajh3@usrlib.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 22:34:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id DECE237B408 for ; Wed, 6 Jun 2001 22:34:47 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 89723 invoked by uid 1000); 7 Jun 2001 05:34:46 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jun 2001 05:34:46 -0000 Date: Thu, 7 Jun 2001 00:34:46 -0500 (CDT) From: Mike Silbersack To: Dima Dorfman Cc: Warner Losh , Poul-Henning Kamp , Subject: Re: MFC'ing new md(4) functionality? In-Reply-To: <20010607024455.9362D3E0B@bazooka.unixfreak.org> Message-ID: <20010607003353.I89714-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 6 Jun 2001, Dima Dorfman wrote: > I don't think anybody is even remotely suggesting that MFS be removed, > but someone (other than you) might get bitten by a change of this > sort. I guess it's just a matter of whether the new functionality > (and giving people a head start integrating the new behavior into > their systems) is worth burning however many people depend on the old > behavior. > > Dima Dorfman > dima@unixfreak.org Ok, silly question from the peanut gallery time. If md is different than md used to be, could the name be changed to something other than md which wouldn't conflict with the old md? Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 22:49:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 56A5337B403 for ; Wed, 6 Jun 2001 22:49:27 -0700 (PDT) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id AA4874D722; Thu, 7 Jun 2001 01:49:21 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id BAA01728; Thu, 7 Jun 2001 01:49:20 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id WAA06248; Wed, 6 Jun 2001 22:49:19 -0700 (PDT) Message-Id: <200106070549.WAA06248@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: louie@transsys.com Subject: Re: How to disable software TCP checksumming? Cc: freebsd-hackers@freebsd.org References: <20010529144114.I19771@luke.immure.com> <20010529221107.C49875@skriver.dk> <20010529155212.M19771@luke.immure.com> <20010530045200.A1031@hades.hell.gr> <20010529235215.A60177@luke.immure.com> <20010530085155.B24096@Odin.AC.HMC.Edu> <200105310204.f4V248n15260@whizzo.transsys.com> Date: Wed, 6 Jun 2001 22:49:18 -0700 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >The TCP checksum protects more than just the contents of the packet >on the wire; it's also a (somewhat) weak check on the contents >of your packet sitting in memory, and as it's going over the bus >in your computer between memory and peripherals and for other end-to-end >sorts of issues. In fact, Jonathan Stone at Stanford did some measurements of checksum errors for his thesis, and found that on a given link in the Stanford residences there were a surprising (small, but measurable) number of packets with IP header checksum errors with what appeared to be DMA errors -- e.g. 4 bytes missing from the middle of the header. When the end to end checksum is really memory to memory, it can catch errors like this... Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 23: 4:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 80E0137B406 for ; Wed, 6 Jun 2001 23:04:31 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f5764G190457; Thu, 7 Jun 2001 08:04:16 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Dima Dorfman Cc: hackers@freebsd.org Subject: Re: MFC'ing new md(4) functionality? In-Reply-To: Your message of "Wed, 06 Jun 2001 19:41:10 PDT." <20010607024110.5403A3E0B@bazooka.unixfreak.org> Date: Thu, 07 Jun 2001 08:04:16 +0200 Message-ID: <90455.991893856@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010607024110.5403A3E0B@bazooka.unixfreak.org>, Dima Dorfman write s: >Poul-Henning Kamp writes: >> In message <20010605013148.A49246@dragon.nuxi.com>, "David O'Brien" writes: >> >On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote: >> >> Is there any reason not to MFC the new md(4) functionality >> > >> >Zero reason not to. >> >> Others see it differently, it would seriously break a lot of >> people who are using -stable in embedded applications. >> >> If we have abandoned the "no changes to API or ABI in -stable" >> paradigm, it would be a good idea, but it serious rains on that >> rule... > >I don't think it would be much of a practical problem for anyone since >the old behvior can be emulated with the new md pretty easily, but >you're right that it isn't appropriate to break compatibility in >-stable. It's probably possible to retrofit the old behavior into the >new code, but I think that's too much evil for too little gain. Well, I see that we just ripped out the "wd" compat bits, so I guess we don't care about ABI/API stability that much in -stable any more... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 23:10:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 052B537B401 for ; Wed, 6 Jun 2001 23:10:48 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f576KUB05343; Wed, 6 Jun 2001 23:20:30 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106070620.f576KUB05343@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: Dima Dorfman , hackers@freebsd.org Subject: Re: MFC'ing new md(4) functionality? In-reply-to: Your message of "Thu, 07 Jun 2001 08:04:16 +0200." <90455.991893856@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Jun 2001 23:20:30 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > >I don't think it would be much of a practical problem for anyone since > >the old behvior can be emulated with the new md pretty easily, but > >you're right that it isn't appropriate to break compatibility in > >-stable. It's probably possible to retrofit the old behavior into the > >new code, but I think that's too much evil for too little gain. > > Well, I see that we just ripped out the "wd" compat bits, so I guess > we don't care about ABI/API stability that much in -stable any more... "We" being who? Your Danish henchman? 8) Actually, I do recall discussion over 'wd' being end-of-lifed in 4.x. I suspect that it would make sense to EOL 'mfs' in a similar fashion. I don't think there's a lot of good sense in pulling it out at an arbitrary point, though, any more than there was in pulling 'wd' like it was. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 23:35:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 9AD4637B405 for ; Wed, 6 Jun 2001 23:35:48 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 15189 invoked by uid 1000); 7 Jun 2001 06:34:36 -0000 Date: Thu, 7 Jun 2001 09:34:36 +0300 From: Peter Pentchev To: Gordon Tetlow Cc: hackers@freebsd.org Subject: Re: make installworld hacking Message-ID: <20010607093436.B10165@ringworld.oblivion.bg> Mail-Followup-To: Gordon Tetlow , hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gordont@bluemtn.net on Wed, Jun 06, 2001 at 12:42:15PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jun 06, 2001 at 12:42:15PM -0700, Gordon Tetlow wrote: > I have a problem, I installed a bunch of machines with a very stripped > down set of distributions (bin, man, dict, krb5). I'd like to update the > machines, but when I do an installworld, it's going to install a bunch > more than that. Is there some way of only upgrading only the bin > distribution (a la make distribute)? If not, would people be interested in > me attempting such a feat? You can set a lot of NO_xxx variables in /etc/make.conf to disable building a *lot* of stuff. G'luck, Peter -- I am not the subject of this sentence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 23:38:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id BAB8037B405 for ; Wed, 6 Jun 2001 23:38:54 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 15234 invoked by uid 1000); 7 Jun 2001 06:37:39 -0000 Date: Thu, 7 Jun 2001 09:37:39 +0300 From: Peter Pentchev To: Dan Phoenix Cc: freebsd-hackers@freebsd.org Subject: Re: rpc.statd Message-ID: <20010607093739.C10165@ringworld.oblivion.bg> Mail-Followup-To: Dan Phoenix , freebsd-hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dphoenix@bravenet.com on Wed, Jun 06, 2001 at 09:39:39PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jun 06, 2001 at 09:39:39PM -0700, Dan Phoenix wrote: > > Jun 6 18:48:10 www rpc.statd: invalid hostname to > sm_stat: ^X^X^Z > ^Z%8x%8x%8x%8x%8x%8x%8x%8x%8x%62716x%hn%51859x%hnM-^PM-^PM-^PM-^PM-^PM-^PM-^PM-^PM- [snip] > > this is a message in messages before a kernel paniced on freebsd 4.3. > I have token liberty of disabling, what does this look like to you guys. As already pointed out, this should definitely not be the cause of a kernel panic. This is, exactly as the other poster explained, a Linux-targeting expoit which has absolutely no effect on FreeBSD's rpc.statd. G'luck, Peter -- If I had finished this sentence, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 23:43:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id C95B937B401; Wed, 6 Jun 2001 23:43:29 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id CAA93623; Thu, 7 Jun 2001 02:43:25 -0400 (EDT) Date: Thu, 7 Jun 2001 02:43:24 -0400 (EDT) From: "Matthew N. Dodd" To: Warner Losh Cc: j mckitrick , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: newbussifying drivers In-Reply-To: <200106061703.f56H3Vl00564@billy-club.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 6 Jun 2001, Warner Losh wrote: > Let me expand a little. The reason I advocate deleting it is because > there are too many old hunks of random hardware that interact badly > with this probe. I've often had to delete the ex driver so that they > start working due to this probe. I'd keep the meat of the routine but > require -current users to specify an address for cards that aren't in > plug and play mode. Except that the 'ex' driver uses a non-destructive probe. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 23:49:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id ACB6637B405; Wed, 6 Jun 2001 23:49:11 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f576l3V09003; Thu, 7 Jun 2001 00:47:03 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200106070647.f576l3V09003@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: newbussifying drivers Cc: j mckitrick , Mike Smith , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 07 Jun 2001 02:43:24 EDT." References: Date: Thu, 07 Jun 2001 00:47:03 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : Except that the 'ex' driver uses a non-destructive probe. I just know that I've had some hardware start working by deleting ex from the kernel. I'll see if I was wise enough to document said hardware... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 23:49:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id B3CE537B405; Wed, 6 Jun 2001 23:49:49 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f576njV09040; Thu, 7 Jun 2001 00:49:45 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200106070649.f576njV09040@harmony.village.org> To: Mike Smith Subject: Re: MFC'ing new md(4) functionality? Cc: Poul-Henning Kamp , Dima Dorfman , hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 06 Jun 2001 23:20:30 PDT." <200106070620.f576KUB05343@mass.dis.org> References: <200106070620.f576KUB05343@mass.dis.org> Date: Thu, 07 Jun 2001 00:49:45 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200106070620.f576KUB05343@mass.dis.org> Mike Smith writes: : Actually, I do recall discussion over 'wd' being end-of-lifed in 4.x. I : suspect that it would make sense to EOL 'mfs' in a similar fashion. I : don't think there's a lot of good sense in pulling it out at an arbitrary : point, though, any more than there was in pulling 'wd' like it was. wd can't be totally EOLd until ata is smart enough to deal with pc98's controllers. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 23:50:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id A77BC37B407; Wed, 6 Jun 2001 23:50:14 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id DADD93E32; Wed, 6 Jun 2001 23:50:13 -0700 (PDT) To: Mike Smith Cc: Poul-Henning Kamp , hackers@freebsd.org Subject: Re: MFC'ing new md(4) functionality? In-Reply-To: <200106070620.f576KUB05343@mass.dis.org>; from msmith@freebsd.org on "Wed, 06 Jun 2001 23:20:30 -0700" Date: Wed, 06 Jun 2001 23:50:13 -0700 From: Dima Dorfman Message-Id: <20010607065013.DADD93E32@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Smith writes: > > >I don't think it would be much of a practical problem for anyone since > > >the old behvior can be emulated with the new md pretty easily, but > > >you're right that it isn't appropriate to break compatibility in > > >-stable. It's probably possible to retrofit the old behavior into the > > >new code, but I think that's too much evil for too little gain. > > > > Well, I see that we just ripped out the "wd" compat bits, so I guess > > we don't care about ABI/API stability that much in -stable any more... > > "We" being who? Your Danish henchman? 8) > > Actually, I do recall discussion over 'wd' being end-of-lifed in 4.x. I > suspect that it would make sense to EOL 'mfs' in a similar fashion. I > don't think there's a lot of good sense in pulling it out at an arbitrary > point, though, any more than there was in pulling 'wd' like it was. FWIW, this thread wasn't (originally) about EOL'ing mfs, but rather making the replacement of MFS (that being md(4)) available in -stable so that when MFS is finally EOL'd (which will be 5.0-REL at the latest), less people will cry. Dima Dorfman dima@unixfreak.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 23:58:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 86F1637B401 for ; Wed, 6 Jun 2001 23:58:18 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f576vtk28161; Thu, 7 Jun 2001 09:57:55 +0300 (EEST) (envelope-from ru) Date: Thu, 7 Jun 2001 09:57:55 +0300 From: Ruslan Ermilov To: Gordon Tetlow Cc: hackers@FreeBSD.ORG Subject: Re: make installworld hacking Message-ID: <20010607095755.C26609@sunbay.com> Mail-Followup-To: Gordon Tetlow , hackers@FreeBSD.ORG References: <20010607093436.B10165@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010607093436.B10165@ringworld.oblivion.bg>; from roam@orbitel.bg on Thu, Jun 07, 2001 at 09:34:36AM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 07, 2001 at 09:34:36AM +0300, Peter Pentchev wrote: > On Wed, Jun 06, 2001 at 12:42:15PM -0700, Gordon Tetlow wrote: > > I have a problem, I installed a bunch of machines with a very stripped > > down set of distributions (bin, man, dict, krb5). I'd like to update the > > machines, but when I do an installworld, it's going to install a bunch > > more than that. Is there some way of only upgrading only the bin > > distribution (a la make distribute)? If not, would people be interested in > > me attempting such a feat? > > You can set a lot of NO_xxx variables in /etc/make.conf to disable building > a *lot* of stuff. > You can also tweak SUBDIR assignments in the src/Makefile.inc1. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jun 6 23:58:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 7860A37B401; Wed, 6 Jun 2001 23:58:36 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id CAA93589; Thu, 7 Jun 2001 02:42:05 -0400 (EDT) Date: Thu, 7 Jun 2001 02:42:04 -0400 (EDT) From: "Matthew N. Dodd" To: Warner Losh Cc: j mckitrick , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: newbussifying drivers In-Reply-To: <200106061656.f56Gull00481@billy-club.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 6 Jun 2001, Warner Losh wrote: > In message <20010605230032.B96188@dogma.freebsd-uk.eu.org> j mckitrick writes: > : How would you recommending fixing this, taken from the ex driver? > > By deleting it. Uh, what? Non PnP devices that can be autodetected should be autodetected. Relying on the user to wire down hints is silly. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 4:20: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 37EAA37B403 for ; Thu, 7 Jun 2001 04:19:56 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.3/8.11.3) with ESMTP id f57BJrt40917; Thu, 7 Jun 2001 12:19:54 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.3/8.11.3) with ESMTP id f57BJr766008; Thu, 7 Jun 2001 12:19:53 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200106071119.f57BJr766008@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Poul-Henning Kamp Cc: Brooks Davis , hackers@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: cloning network interfaces In-Reply-To: Message from Poul-Henning Kamp of "Wed, 06 Jun 2001 23:16:57 +0200." <85874.991862217@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Jun 2001 12:19:53 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > In message <20010606141228.A13639@Odin.AC.HMC.Edu>, Brooks Davis writes: > > >With network devices that are also normal devices the way tun is, > >you do this by just implementing a dev_clone event handler so when the > >user attempts to open a non-existent instance it's created. The problem > >with gif is that there's no device in /dev to open. Since most network > >devices at attached to hardware this usually doesn't matter, but in this > >case it does. > > > >[...] > > > >How would this work anyway? > > > >Comments, thoughts, ideas? > > The quick and dirty way: > > Make a clone handler despite the fact that there is no /dev > entry needed. You don't actually have to create a dev entry > in the clone handler, you could just create the gif_interface. > > Applications would then: > > stat("/dev/gif345") /* Ignore error */ > system("ifconfig gif345 bla bla bla"); > > The slower but less dirty: > > Make a sysctl which returns an integer which is the next > free gif device. > > The really slow and very dirty: > > Implement cloning in ifconfig. Maybe a reasonable alternative would be to have a /dev/if_gif device with ioctls for creating and destroying interfaces. ifconfig(8) could be taught to create (and maybe even to delete) them. > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 4:40:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by hub.freebsd.org (Postfix) with ESMTP id DADBE37B403; Thu, 7 Jun 2001 04:40:50 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from [62.49.251.130] (helo=herring.nlsystems.com) by anchor-post-30.mail.demon.net with esmtp (Exim 2.12 #1) id 157yCH-0009tu-0U; Thu, 7 Jun 2001 12:43:29 +0100 Received: from herring (herring [10.0.0.2]) by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id f57BdT718128; Thu, 7 Jun 2001 12:39:29 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Thu, 7 Jun 2001 12:39:29 +0100 (BST) From: Doug Rabson To: "Matthew N. Dodd" Cc: Warner Losh , j mckitrick , Mike Smith , Subject: Re: newbussifying drivers In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 7 Jun 2001, Matthew N. Dodd wrote: > On Wed, 6 Jun 2001, Warner Losh wrote: > > In message <20010605230032.B96188@dogma.freebsd-uk.eu.org> j mckitrick writes: > > : How would you recommending fixing this, taken from the ex driver? > > > > By deleting it. > > Uh, what? > > Non PnP devices that can be autodetected should be autodetected. > > Relying on the user to wire down hints is silly. Probably they should provide an identify method to look for and create the non-PnP devices. The actual probe method should be dumb and just use the resources given to it (IMHO). -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 4:59:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from london.physics.purdue.edu (london.physics.purdue.edu [128.210.67.35]) by hub.freebsd.org (Postfix) with ESMTP id 137BB37B405 for ; Thu, 7 Jun 2001 04:59:17 -0700 (PDT) (envelope-from will@physics.purdue.edu) Received: from bohr.physics.purdue.edu (bohr.physics.purdue.edu [128.210.67.12]) by london.physics.purdue.edu (8.8.8/8.8.8) with ESMTP id GAA12745; Thu, 7 Jun 2001 06:59:16 -0500 (EST) Received: by bohr.physics.purdue.edu (Postfix, from userid 12409) id 0817A5BAA; Thu, 7 Jun 2001 06:59:15 -0500 (EST) Date: Thu, 7 Jun 2001 06:59:15 -0500 From: Will Andrews To: Andrew Hesford Cc: FreeBSD-hackers Subject: Re: XFree86 4.1.0 and i810 Message-ID: <20010607065915.V81224@bohr.physics.purdue.edu> Reply-To: Will Andrews References: <20010606232045.A453@core.usrlib.org> <20010607003250.B40894@core.usrlib.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GAoked8QSizNecZ5" Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <20010607003250.B40894@core.usrlib.org>; from ajh3@usrlib.org on Thu, Jun 07, 2001 at 12:32:50AM -0500 X-Operating-System: FreeBSD 4.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --GAoked8QSizNecZ5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 07, 2001 at 12:32:50AM -0500, Andrew Hesford (ajh3@usrlib.org) = wrote: > The XFree86 4.0.1 sources *did* offer a helpful hint. I have posted > another email which includes a patch to fix the buggy i810 driver. Are you people talking about XFree86 4.1.0 or 4.0.1? Because 4.0.1 is >WAY< outdated. :-) --=20 wca --GAoked8QSizNecZ5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7H2yTF47idPgWcsURAmqWAKCJTtTtRn/ZLhjjApiQ5xSBzuu/qwCeP1/R 6YoTdFeXFR1gOUHb57Qqy/g= =Ar6G -----END PGP SIGNATURE----- --GAoked8QSizNecZ5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 5:15:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by hub.freebsd.org (Postfix) with ESMTP id C281937B401 for ; Thu, 7 Jun 2001 05:15:22 -0700 (PDT) (envelope-from stijn@pcwin002.win.tue.nl) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.11.3/8.11.3) id f57CF2c11272; Thu, 7 Jun 2001 14:15:02 +0200 (CEST) (envelope-from stijn) Date: Thu, 7 Jun 2001 14:15:02 +0200 From: Stijn Hoop To: Will Andrews Cc: Andrew Hesford , FreeBSD-hackers Subject: Re: XFree86 4.1.0 and i810 Message-ID: <20010607141502.D8881@pcwin002.win.tue.nl> References: <20010606232045.A453@core.usrlib.org> <20010607003250.B40894@core.usrlib.org> <20010607065915.V81224@bohr.physics.purdue.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010607065915.V81224@bohr.physics.purdue.edu>; from will@physics.purdue.edu on Thu, Jun 07, 2001 at 06:59:15AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 07, 2001 at 06:59:15AM -0500, Will Andrews wrote: > On Thu, Jun 07, 2001 at 12:32:50AM -0500, Andrew Hesford (ajh3@usrlib.org) wrote: > > The XFree86 4.0.1 sources *did* offer a helpful hint. I have posted > > another email which includes a patch to fix the buggy i810 driver. > > Are you people talking about XFree86 4.1.0 or 4.0.1? Because > 4.0.1 is >WAY< outdated. :-) Uhm, yeah, but the problems with switching VT's weren't present in that version. Something changed between 4.0.1 and 4.0.2 that caused the problem, and I think Andrew wants to know what exactly. BTW, Andrew, I really hope you do succeed (esp. with the recent 4.1.0 troubles). Thanks for investigating this! --Stijn -- Nostalgia ain't what it used to be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 5:31: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id AF65E37B406 for ; Thu, 7 Jun 2001 05:30:52 -0700 (PDT) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.11.4/8.11.3) with ESMTP id f57CUoD06629 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Thu, 7 Jun 2001 14:30:51 +0200 (CEST) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.11.3/8.11.3) id f57CUoO16108 for freebsd-hackers@freebsd.org; Thu, 7 Jun 2001 14:30:50 +0200 (CEST) Date: Thu, 7 Jun 2001 14:30:50 +0200 From: Cejka Rudolf To: freebsd-hackers@freebsd.org Subject: [Patch?] signal(SIGCHLD, SIG_IGN) is against SUSv2 Message-ID: <20010607143050.A13932@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG There is following paragraph in SUSv2: If a process sets the action for the SIGCHLD signal to SIG_IGN, the behaviour is unspecified, except as specified below. If the action for the SIGCHLD signal is set to SIG_IGN, child processes of the calling processes will not be transformed into zombie processes when they terminate. If the calling process subsequently waits for its children, and the process has no unwaited for children that were transformed into zombie processes, it will block until all of its children terminate, and wait(), wait3(), waitid() and waitpid() will fail and set errno to [ECHILD]. ... However, if I use "signal(SIGCHLD, SIG_IGN)", zombies are still created in FreeBSD, which is against SUSv2. What do you think about following patch for -stable (it is usable with -current too)? Furthermore, it seems that the test "if (ps->ps_sigact[_SIG_IDX(SIGCHLD)] = SIG_IGN)" is unnecessary. After patch there are: one more question, comparison results among different systems (unbelievable how much they are different :-) and my sigtest.c program: -- Patch --- sys/kern/kern_sig.c.orig Wed Jun 6 11:52:37 2001 +++ sys/kern/kern_sig.c Thu Jun 7 11:57:45 2001 @@ -438,6 +438,8 @@ * Reset no zombies if child dies flag as Solaris does. */ p->p_procsig->ps_flag &= ~PS_NOCLDWAIT; + if (ps->ps_sigact[_SIG_IDX(SIGCHLD)] = SIG_IGN) + ps->ps_sigact[_SIG_IDX(SIGCHLD)] = SIG_DFL; } /* --- sys/kern/kern_exit.c.orig Wed Jun 6 13:13:43 2001 +++ sys/kern/kern_exit.c Thu Jun 7 11:24:03 2001 @@ -316,7 +316,8 @@ * flag set, notify process 1 instead (and hope it will handle * this situation). */ - if (p->p_pptr->p_procsig->ps_flag & PS_NOCLDWAIT) { + if (p->p_pptr->p_procsig->ps_flag & PS_NOCLDWAIT + || p->p_sigacts->ps_sigact[_SIG_IDX(SIGCHLD)] == SIG_IGN) { struct proc *pp = p->p_pptr; proc_reparent(p, initproc); /* -- Question In sys/kern/kern_sig.c in do_sigaction(), there is: if (act->sa_flags & SA_SIGINFO) { ps->ps_sigact[_SIG_IDX(sig)] = act->sa_handler; SIGADDSET(ps->ps_siginfo, sig); } else { ps->ps_sigact[_SIG_IDX(sig)] = (__sighandler_t *)act->sa_sigaction; SIGDELSET(ps->ps_siginfo, sig); } Why? I know that sa_handler and sa_sigaction are the same pointer in an union, but I think that "act->sa_handler" should be exchanged with "(__sighandler_t *)act->sa_sigaction" for clarification purposes. -- Comparison results ABCD(Z = zombie created): SIGCHLD properties before exec() -> after exec() A) SIG_IGN before exec (instead of SIG_DFL) B) SA_NOCLDWAIT before exec (instead of 0) C) SIG_IGN after exec (instead of SIG_DFL) D) SA_NOCLDWAIT after exec (instead of 0) Solaris 2.7, FreeBSD 4.3 with proposed patch: 0000(Z), 0001( ), 0010( ), 0011( ): SIG_DFL() -> SIG_DFL() 0100(Z), 0101( ), 0110( ), 0111( ): SIG_DFL(SA_NOCLDWAIT) -> SIG_DFL() 1000(Z), 1001( ), 1010( ), 1011( ): SIG_IGN() -> SIG_DFL() 1100(Z), 1101( ), 1110( ), 1111( ): SIG_IGN(SA_NOCLDWAIT) -> SIG_DFL() Irix 6.5, Unixware 7.0.1: 0000(Z), 0001( ), 0010( ), 0011( ): SIG_DFL() -> SIG_DFL() 0100(Z), 0101( ), 0110( ), 0111( ): SIG_DFL(SA_NOCLDWAIT) -> SIG_DFL() 1000(Z), 1001( ), 1010( ), 1011( ): SIG_IGN(SA_NOCLDWAIT) -> SIG_IGN() 1100(Z), 1101( ), 1110( ), 1111( ): SIG_IGN(SA_NOCLDWAIT) -> SIG_IGN() FreeBSD 4.3 without proposed patch, FreeBSD-current (Apr 27): 0000(Z), 0001( ), 0010(Z), 0011( ): SIG_DFL() -> SIG_DFL() 0100(Z), 0101( ), 0110(Z), 0111( ): SIG_DFL(SA_NOCLDWAIT) -> SIG_DFL() 1000(Z), 1001( ), 1010(Z), 1011( ): SIG_IGN() -> SIG_IGN() 1100(Z), 1101( ), 1110(Z), 1111( ): SIG_IGN(SA_NOCLDWAIT) -> SIG_IGN() Linux 2.2.17: 0000(Z), 0001(Z), 0010( ), 0011( ): SIG_DFL() -> SIG_DFL() 0100(Z), 0101(Z), 0110( ), 0111( ): SIG_DFL(SA_NOCLDWAIT) -> SIG_DFL() 1000( ), 1001(Z), 1010( ), 1011( ): SIG_IGN() -> SIG_IGN() 1100( ), 1101(Z), 1110( ), 1111( ): SIG_IGN(SA_NOCLDWAIT) -> SIG_IGN() -- testsig.c #include #include #include #include #include #include #include #include int main(int argc, char *argv[]) { int childs = 0; struct sigaction sa, so; int status; int value; if (argc > 1) { value = atoi(argv[1]); } else { printf("Usage: sigtest \n"); exit(1); } if (argc > 2 && strcmp(argv[2], "-x") == 0) { /* After exec() */ sigaction(SIGCHLD, NULL, &so); printf("After exec(): %s(%s)\n", (so.sa_handler == SIG_IGN) ? "SIG_IGN" : ((so.sa_handler == SIG_DFL) ? "SIG_DFL" : "?"), (so.sa_flags & SA_NOCLDWAIT) ? "SA_NOCLDWAIT" : ""); sigemptyset(&sa.sa_mask); if (value & 3) { sa.sa_flags = (value & 1) ? SA_NOCLDWAIT : 0; sa.sa_handler = (value & 2) ? SIG_IGN : SIG_DFL; sigaction(SIGCHLD, &sa, NULL); } sigaction(SIGCHLD, NULL, &so); printf("Before fork(): %s(%s)\n", (so.sa_handler == SIG_IGN) ? "SIG_IGN" : ((so.sa_handler == SIG_DFL) ? "SIG_DFL" : "?"), (so.sa_flags & SA_NOCLDWAIT) ? "SA_NOCLDWAIT" : ""); while (++childs <= 10) { switch (fork()) { case 0: printf("Child %d exiting...\n", childs); exit(0); case -1: printf("fork(): %s\n", strerror(errno)); exit(-1); default: break; } } printf("Sleeping...\n"); sleep(3); } else { /* Main process before exec() */ switch (fork()) { case 0: sigaction(SIGCHLD, NULL, &so); printf("Default: %s(%s)\n", (so.sa_handler == SIG_IGN) ? "SIG_IGN" : ((so.sa_handler == SIG_DFL) ? "SIG_DFL" : "?"), (so.sa_flags & SA_NOCLDWAIT) ? "SA_NOCLDWAIT" : ""); sigemptyset(&sa.sa_mask); if (value & 12) { sa.sa_flags = (value & 4) ? SA_NOCLDWAIT : 0; sa.sa_handler = (value & 8) ? SIG_IGN : SIG_DFL; sigaction(SIGCHLD, &sa, NULL); } sigaction(SIGCHLD, NULL, &so); printf("Before exec(): %s(%s)\n", (so.sa_handler == SIG_IGN) ? "SIG_IGN" : ((so.sa_handler == SIG_DFL) ? "SIG_DFL" : "?"), (so.sa_flags & SA_NOCLDWAIT) ? "SA_NOCLDWAIT" : ""); execl(argv[0], argv[0], argv[1], "-x", NULL); printf("exec(%s %s): %s\n", argv[0], "-x", strerror(errno)); return 0; case -1: printf("fork(): %s\n", strerror(errno)); exit(-1); default: (void)wait(&status); break; } } return 0; } -- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 6: 0:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id 036B537B405 for ; Thu, 7 Jun 2001 06:00:48 -0700 (PDT) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.11.4/8.11.3) with ESMTP id f57D0kD37066 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Thu, 7 Jun 2001 15:00:46 +0200 (CEST) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.11.3/8.11.3) id f57D0kx17203 for freebsd-hackers@freebsd.org; Thu, 7 Jun 2001 15:00:46 +0200 (CEST) Date: Thu, 7 Jun 2001 15:00:46 +0200 From: Cejka Rudolf To: freebsd-hackers@freebsd.org Subject: Re: [Patch?] signal(SIGCHLD, SIG_IGN) is against SUSv2 Message-ID: <20010607150046.A17132@dcse.fee.vutbr.cz> References: <20010607143050.A13932@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010607143050.A13932@dcse.fee.vutbr.cz>; from cejkar@dcse.fee.vutbr.cz on Thu, Jun 07, 2001 at 02:30:50PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Oops, kid's bugs. Thanks to David Malone ;-) Cejka Rudolf wrote (2001/06/07): > "if (ps->ps_sigact[_SIG_IDX(SIGCHLD)] = SIG_IGN)" is unnecessary. ^ == > --- sys/kern/kern_sig.c.orig Wed Jun 6 11:52:37 2001 > +++ sys/kern/kern_sig.c Thu Jun 7 11:57:45 2001 > @@ -438,6 +438,8 @@ > * Reset no zombies if child dies flag as Solaris does. > */ > p->p_procsig->ps_flag &= ~PS_NOCLDWAIT; > + if (ps->ps_sigact[_SIG_IDX(SIGCHLD)] = SIG_IGN) ^ == > + ps->ps_sigact[_SIG_IDX(SIGCHLD)] = SIG_DFL; > } > > /* -- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 6:22:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natpost.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 5ACF837B401 for ; Thu, 7 Jun 2001 06:22:37 -0700 (PDT) (envelope-from freebsd-ml@econos.de) Received: from stefan-bt (pD95024D6.dip.t-dialin.net [217.80.36.214]) by post.webmailer.de (8.9.3/8.8.7) with SMTP id PAA14707 for ; Thu, 7 Jun 2001 15:22:29 +0200 (MET DST) From: Stefan Hoffmeister To: freebsd-hackers@FreeBSD.ORG Subject: libc_r, signal handler ucontext modification Date: Thu, 07 Jun 2001 15:21:31 +0200 Organization: Econos Message-ID: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, given the following * FreeBSD 4.3 Release (i386) * an application linked against libc_r * and a signal handler installed with the SA_SIGINFO flag which implies that the signal handler will be called with int Signal, int SomethingBoring, uncontext_t* ucontext ow should the implementation of libc_r (!) behave if the application modifies the ucontext passed in to the signal handler? In particular, how should the implementation behave if the_ucontext->m_context->mc_eip is modified, setting EIP to, say, a fault handler? Some random observations: * Currently libc_r seems to ignore these changes made to the context. * When the application is linked against libc, EIP is switched (i.e. the intended effect takes place); this implies that the behaviour shown by libc and libc_r diverges. * Under Linux, modifying EIP has the intended effect. I admit that all this is somewhat anecdotal, but I haven't looked in detail yet at what happens after the signal handler has returned to uthread/uthread_sig.c -> _thread_sig_wrapper If someone needs some sample code, I'd be happy to cook up something once I have booted into FreeBSD again. Any thoughts? TIA! Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 6:36:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from core.usrlib.org (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id CB53737B405 for ; Thu, 7 Jun 2001 06:36:17 -0700 (PDT) (envelope-from ajh3@core.usrlib.org) Received: by core.usrlib.org (Postfix, from userid 1001) id F07A5A874; Thu, 7 Jun 2001 08:35:06 -0500 (CDT) Date: Thu, 7 Jun 2001 08:35:06 -0500 From: Andrew Hesford To: Will Andrews Cc: Andrew Hesford , FreeBSD-hackers Subject: Re: XFree86 4.1.0 and i810 Message-ID: <20010607083506.A42740@core.usrlib.org> References: <20010606232045.A453@core.usrlib.org> <20010607003250.B40894@core.usrlib.org> <20010607065915.V81224@bohr.physics.purdue.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010607065915.V81224@bohr.physics.purdue.edu>; from will@physics.purdue.edu on Thu, Jun 07, 2001 at 06:59:15AM -0500 X-Loop: Andrew Hesford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 07, 2001 at 06:59:15AM -0500, Will Andrews wrote: > On Thu, Jun 07, 2001 at 12:32:50AM -0500, Andrew Hesford (ajh3@usrlib.org) wrote: > > The XFree86 4.0.1 sources *did* offer a helpful hint. I have posted > > another email which includes a patch to fix the buggy i810 driver. > > Are you people talking about XFree86 4.1.0 or 4.0.1? Because > 4.0.1 is >WAY< outdated. :-) > > -- > wca I'm talking about both. The last version of XFree86 that worked properly with the i810 was 4.0.1. Driver restructuring in later versions broke VT-switching code in subsequent versions. Unfortunately, 4.1.0 did not fix this problem (although they claim to support the i810 under FreeBSD), and I managed to trace the problem to an AGPIOC_BIND ioctl. Since XFree86 4.0.1 did not have this problem, I downloaded its sources and was looking to see how the i810 driver handled VT switching. As far as I can tell, the *only* problem with 4.0.2, 4.0.3, and 4.1.0 is that they calle I810UnbindGARTMemory() when leaving the X VT, and call I810BindGARTMemory() when entering the X VT. This call to I810BindGARTMemory() is the one that makes the bad ioctl call. The solution is to comment out the calls to I810BindGARTMemory() and I810UnbindGARTMemory() in the VT-switching functions. The end result is that I810EnterVT() and I810LeaveVT() are now identical in 4.1.0 to the ones in 4.0.1, and the server no longer crashes when one switches terminals. I have attached a patch, and hope that the XFree86 port maintainer will consider adding this to the files/ directory to achieve maximum distribution. I will contact him shortly. I imagine it would be possible to apply the same changes to the drivers in 4.0.2 or 4.0.3, although now I don't see why anybody would care. -- Andrew Hesford ajh3@usrlib.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 6:37:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from core.usrlib.org (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id 0493437B401 for ; Thu, 7 Jun 2001 06:37:29 -0700 (PDT) (envelope-from ajh3@core.usrlib.org) Received: by core.usrlib.org (Postfix, from userid 1001) id 41D12A874; Thu, 7 Jun 2001 08:36:18 -0500 (CDT) Date: Thu, 7 Jun 2001 08:36:18 -0500 From: Andrew Hesford To: Andrew Hesford Cc: Will Andrews , FreeBSD-hackers Subject: Re: XFree86 4.1.0 and i810 Message-ID: <20010607083618.B42740@core.usrlib.org> References: <20010606232045.A453@core.usrlib.org> <20010607003250.B40894@core.usrlib.org> <20010607065915.V81224@bohr.physics.purdue.edu> <20010607083506.A42740@core.usrlib.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010607083506.A42740@core.usrlib.org>; from ajh3@usrlib.org on Thu, Jun 07, 2001 at 08:35:06AM -0500 X-Loop: Andrew Hesford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jun 07, 2001 at 08:35:06AM -0500, Andrew Hesford wrote: > The solution is to comment out the calls to I810BindGARTMemory() and > I810UnbindGARTMemory() in the VT-switching functions. The end result is > that I810EnterVT() and I810LeaveVT() are now identical in 4.1.0 to the > ones in 4.0.1, and the server no longer crashes when one switches > terminals. I have attached a patch, and hope that the XFree86 port > maintainer will consider adding this to the files/ directory to achieve > maximum distribution. I will contact him shortly. Damn it, I forgot to include the patch. Here we go. -- Andrew Hesford ajh3@usrlib.org --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=patch-i810 --- programs/Xserver/hw/xfree86/drivers/i810/i810_driver.c.orig Tue May 29 17:51:29 2001 +++ programs/Xserver/hw/xfree86/drivers/i810/i810_driver.c Thu Jun 7 00:12:25 2001 @@ -2006,9 +2006,10 @@ if (I810_DEBUG & DEBUG_VERBOSE_DRI) ErrorF("\n\nENTER VT\n"); +/*********BUGGY********************* if (! I810BindGARTMemory(pScrn)) return FALSE; - +***********************************/ #ifdef XF86DRI if (pI810->directRenderingEnabled) { if (I810_DEBUG & DEBUG_VERBOSE_DRI) @@ -2047,9 +2048,10 @@ } I810Restore(pScrn); +/*********BUGGY*********************** if (! I810UnbindGARTMemory(pScrn)) return; - +*************************************/ vgaHWLock(hwp); } --mP3DRpeJDSE+ciuQ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 6:43:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from core.usrlib.org (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id A4F1037B403 for ; Thu, 7 Jun 2001 06:43:30 -0700 (PDT) (envelope-from ajh3@core.usrlib.org) Received: by core.usrlib.org (Postfix, from userid 1001) id D827AA874; Thu, 7 Jun 2001 08:42:19 -0500 (CDT) Date: Thu, 7 Jun 2001 08:42:19 -0500 From: Andrew Hesford To: Stijn Hoop Cc: Will Andrews , Andrew Hesford , FreeBSD-hackers Subject: Re: XFree86 4.1.0 and i810 Message-ID: <20010607084219.C42740@core.usrlib.org> References: <20010606232045.A453@core.usrlib.org> <20010607003250.B40894@core.usrlib.org> <20010607065915.V81224@bohr.physics.purdue.edu> <20010607141502.D8881@pcwin002.win.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010607141502.D8881@pcwin002.win.tue.nl>; from stijn@win.tue.nl on Thu, Jun 07, 2001 at 02:15:02PM +0200 X-Loop: Andrew Hesford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 07, 2001 at 02:15:02PM +0200, Stijn Hoop wrote: > BTW, Andrew, I really hope you do succeed (esp. with the recent > 4.1.0 troubles). Thanks for investigating this! > > --Stijn The problem is incredibly simple. I explain it and offer a patch in my response to Will's messages. As many might know from the freebsd-stable list, another problem with the i810 exists, namely the server won't start at all. As they discussed, the solution is to add Options "NoDDC" to the i810 "Device" section of XF86Config. Unfortunately, this won't fix the VT problem. You will need to apply my patch and rebuild XFree86 for that. Don't feel bad... I think I rebuilt and reinstalled XFree86 4.1.0 six times trying to track down the problem. If I had only decided much earlier, "Hey, let's look at the 4.0.1 EnterVT and LeaveVT functions to see what could be wrong," I would have saved loads of time. -- Andrew Hesford ajh3@usrlib.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 7:15: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id DFB9237B407; Thu, 7 Jun 2001 07:15:00 -0700 (PDT) (envelope-from jmz@FreeBSD.org) Received: (from jmz@localhost) by freefall.freebsd.org (8.11.3/8.11.3) id f57EF0f64926; Thu, 7 Jun 2001 07:15:00 -0700 (PDT) (envelope-from jmz@FreeBSD.org) Date: Thu, 7 Jun 2001 07:15:00 -0700 (PDT) Message-Id: <200106071415.f57EF0f64926@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: jmz set sender to jmz@FreeBSD.org using -f From: Jean-Marc Zucconi To: Andrew Hesford Cc: Will Andrews , FreeBSD-hackers Subject: Re: XFree86 4.1.0 and i810 In-Reply-To: <20010607083618.B42740@core.usrlib.org> References: <20010606232045.A453@core.usrlib.org> <20010607003250.B40894@core.usrlib.org> <20010607065915.V81224@bohr.physics.purdue.edu> <20010607083506.A42740@core.usrlib.org> <20010607083618.B42740@core.usrlib.org> X-Mailer: Emacs 20.7.1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> Andrew Hesford writes: > On Thu, Jun 07, 2001 at 08:35:06AM -0500, Andrew Hesford wrote: >> The solution is to comment out the calls to I810BindGARTMemory() and >> I810UnbindGARTMemory() in the VT-switching functions. The end result is >> that I810EnterVT() and I810LeaveVT() are now identical in 4.1.0 to the >> ones in 4.0.1, and the server no longer crashes when one switches >> terminals. I have attached a patch, and hope that the XFree86 port >> maintainer will consider adding this to the files/ directory to achieve >> maximum distribution. I will contact him shortly. > Damn it, I forgot to include the patch. Here we go. I will commit it. Please send it to fixes@XFree86.org too. Jean-Marc -- Jean-Marc Zucconi -- PGP Key: finger jmz@FreeBSD.org [KeyID: 400B38E9] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 7:53:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natpost.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 8CB3B37B403 for ; Thu, 7 Jun 2001 07:53:19 -0700 (PDT) (envelope-from freebsd-ml@econos.de) Received: from stefan-bt (pD95024D6.dip.t-dialin.net [217.80.36.214]) by post.webmailer.de (8.9.3/8.8.7) with SMTP id QAA14692 for ; Thu, 7 Jun 2001 16:53:14 +0200 (MET DST) From: Stefan Hoffmeister To: freebsd-hackers@FreeBSD.ORG Subject: Re: libc_r, signal handler ucontext modification Date: Thu, 07 Jun 2001 16:52:16 +0200 Organization: Econos Message-ID: References: In-Reply-To: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : On Thu, 07 Jun 2001 15:21:31 +0200, Stefan Hoffmeister wrote: >I admit that all this is somewhat anecdotal, but I haven't looked in >detail yet at what happens after the signal handler has returned to > > uthread/uthread_sig.c -> _thread_sig_wrapper Looking at code in question, I wonder whether in uthread_sig.c this code: ********************************* static void thread_sigframe_add(pthread_t thread, int sig, int has_args) { ... if (has_args) { /* Copy the signal handler arguments to the signal frame: */ memcpy(&psf->uc, &_thread_sigq[psf->signo - 1].uc, sizeof(psf->uc)); memcpy(&psf->siginfo, &_thread_sigq[psf->signo - 1].siginfo, sizeof(psf->siginfo)); } ... ********************************* should get matching code ********************************* void _thread_sigframe_restore(pthread_t thread, struct pthread_signal_frame *psf) { thread->ctxtype = psf->ctxtype; - memcpy(&thread->ctx.uc, &psf->ctx.uc, sizeof(thread->ctx.uc)); + if (psf->sig_has_args) + memcpy(&thread->ctx.uc, &psf->uc, sizeof(thread->ctx.uc)); + else + memcpy(&thread->ctx.uc, &psf->ctx.uc, sizeof(thread->ctx.uc)); ********************************* or something like that. The above is completely untested, based on five minutes of staring at the code, not even compiled, and I have no idea what I am doing :-) Thoughts? TIA, Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 7:54:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from core.usrlib.org (CC2-861.charter-stl.com [24.217.115.99]) by hub.freebsd.org (Postfix) with ESMTP id A1CE837B403; Thu, 7 Jun 2001 07:54:22 -0700 (PDT) (envelope-from ajh3@core.usrlib.org) Received: by core.usrlib.org (Postfix, from userid 1001) id C5927A87B; Thu, 7 Jun 2001 09:53:10 -0500 (CDT) Date: Thu, 7 Jun 2001 09:53:10 -0500 From: Andrew Hesford To: Jean-Marc Zucconi Cc: FreeBSD-hackers Subject: Re: XFree86 4.1.0 and i810 Message-ID: <20010607095310.C43034@core.usrlib.org> References: <20010606232045.A453@core.usrlib.org> <20010607003250.B40894@core.usrlib.org> <20010607065915.V81224@bohr.physics.purdue.edu> <20010607083506.A42740@core.usrlib.org> <20010607083618.B42740@core.usrlib.org> <200106071415.f57EF0f64926@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106071415.f57EF0f64926@freefall.freebsd.org>; from jmz@FreeBSD.org on Thu, Jun 07, 2001 at 07:15:00AM -0700 X-Loop: Andrew Hesford Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 07, 2001 at 07:15:00AM -0700, Jean-Marc Zucconi wrote: > I will commit it. Please send it to fixes@XFree86.org too. > > Jean-Marc Thanks a lot, I have just submitted the patch to fixes@xfree86.org. -- Andrew Hesford ajh3@usrlib.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 8:12:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-m01.mx.aol.com (imo-m01.mx.aol.com [64.12.136.4]) by hub.freebsd.org (Postfix) with ESMTP id 4784D37B406 for ; Thu, 7 Jun 2001 08:12:53 -0700 (PDT) (envelope-from Bsdguru@aol.com) Received: from Bsdguru@aol.com by imo-m01.mx.aol.com (mail_out_v30.22.) id h.107.f0e27f (4417); Thu, 7 Jun 2001 11:12:40 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <107.f0e27f.2850f3e8@aol.com> Date: Thu, 7 Jun 2001 11:12:40 EDT Subject: Re: How to disable software TCP checksumming? To: louie@transsys.com Cc: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This thread is baffling. The bottom line is that you cant trust data coming into your machine, and you have to checksum it. The link level check only verifies that what was sent by the last forwarding point is the same as what you got, but in NO WAY implies that all of the data is valid. A link level checksum pass is a necessary, but not a sufficient condition for the data being acceptable. There are scads of reasons that it could be bad. Disabling checksumming is a kludge that you may chose to do, but its never the right thing to do. bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 9: 8:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 6F70837B406 for ; Thu, 7 Jun 2001 09:08:36 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 4731 invoked by uid 1000); 7 Jun 2001 16:07:22 -0000 Date: Thu, 7 Jun 2001 19:07:22 +0300 From: Peter Pentchev To: hackers@FreeBSD.org Subject: free() and const warnings Message-ID: <20010607190722.G724@ringworld.oblivion.bg> Mail-Followup-To: hackers@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Is free((void *) (size_t) ptr) the only way to free a const whatever *ptr with WARNS=2? (or more specifically, with -Wcast-qual) G'luck, Peter -- I've heard that this sentence is a rumor. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 9: 8:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id CF8CE37B405 for ; Thu, 7 Jun 2001 09:08:42 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id MAA21781; Thu, 7 Jun 2001 12:07:52 -0400 (EDT) Date: Thu, 7 Jun 2001 12:07:50 -0400 (EDT) From: Daniel Eischen To: Stefan Hoffmeister Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: libc_r, signal handler ucontext modification In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 7 Jun 2001, Stefan Hoffmeister wrote: > : On Thu, 07 Jun 2001 15:21:31 +0200, Stefan Hoffmeister wrote: > > >I admit that all this is somewhat anecdotal, but I haven't looked in > >detail yet at what happens after the signal handler has returned to > > > > uthread/uthread_sig.c -> _thread_sig_wrapper > > Looking at code in question, I wonder whether in uthread_sig.c this code: > > ********************************* > static void > thread_sigframe_add(pthread_t thread, int sig, int has_args) > { > > ... > > if (has_args) { > /* Copy the signal handler arguments to the signal frame: */ > memcpy(&psf->uc, &_thread_sigq[psf->signo - 1].uc, > sizeof(psf->uc)); > memcpy(&psf->siginfo, &_thread_sigq[psf->signo - 1].siginfo, > sizeof(psf->siginfo)); > } > ... > ********************************* > > should get matching code > > ********************************* > > void > _thread_sigframe_restore(pthread_t thread, struct pthread_signal_frame > *psf) > { > thread->ctxtype = psf->ctxtype; > - memcpy(&thread->ctx.uc, &psf->ctx.uc, sizeof(thread->ctx.uc)); > + if (psf->sig_has_args) > + memcpy(&thread->ctx.uc, &psf->uc, sizeof(thread->ctx.uc)); > + else > + memcpy(&thread->ctx.uc, &psf->ctx.uc, sizeof(thread->ctx.uc)); > > ********************************* You can't do that. There is no requirement that the interrupted thread is the one that handles the signal. If you copy the context back to the current threads context storage, then you'll possibly end up with 2 threads running (or trying to run) on the same stack! The only way to make that work is to suspend the thread that got interrupted until the signal handler finished. And we can never know when the signal handler finishes because the handler is allowed to longjmp out [of the handler]. You could potentially copy the context back if and only if the thread that was interrupted is the same as the thread that is handling the signal. You could also easily modify the context and do a sigreturn(ucp) on it to achieve the same effect (being careful to make sure you're not trying to jump to another threads context). -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 9:16:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monty.mutatus.co.uk (monty.mutatus.co.uk [195.184.238.178]) by hub.freebsd.org (Postfix) with ESMTP id 8CB4337B406 for ; Thu, 7 Jun 2001 09:16:50 -0700 (PDT) (envelope-from gbarr@mutatus.co.uk) Received: (from gbarr@localhost) by monty.mutatus.co.uk (8.11.3/8.11.3) id f57GF1R03492; Thu, 7 Jun 2001 17:15:01 +0100 (BST) (envelope-from gbarr) Date: Thu, 7 Jun 2001 17:15:01 +0100 From: Graham Barr To: freebsd-hackers@freebsd.org Subject: read(2) and ETIMEDOUT Message-ID: <20010607171501.S50444@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG A while ago our systems were upgraded from 4.2 to 4.3-RC, and at this time we started seeing problems that I am having a difficult time tracking down. We have a server process which is connected to by many other machines, each of them streams data in via tcp/ip. These connections are pretty much permanent. All had been running fine for a long time before the upgrade, but now we have a problem with read(2) returning an error ETIMEDOUT, which causes our code to close the connection. The strange thing is that things are fine for a few hours, then all of a sudden we see each of the connections fail with this error. Then after the clients have reconnected, all is fine for a few hours and then they all do it again. The problem I am having in tracking this down is that man 2 read does not specify ETIMEDOUT as an error that can be returned from read(2) and man errno specifies that it would be returned from connect(2) or send(2) So, here is my question. Does anyone know under what circumstance ETIMEDOUT may be returned from read(2) or is this a potential bug somewhere ? Thanks, Graham. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 9:53:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 5F61637B401 for ; Thu, 7 Jun 2001 09:53:56 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f57Grsn73369; Thu, 7 Jun 2001 09:53:54 -0700 (PDT) (envelope-from dillon) Date: Thu, 7 Jun 2001 09:53:54 -0700 (PDT) From: Matt Dillon Message-Id: <200106071653.f57Grsn73369@earth.backplane.com> To: Graham Barr Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: read(2) and ETIMEDOUT References: <20010607171501.S50444@pobox.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :A while ago our systems were upgraded from 4.2 to 4.3-RC, and at :this time we started seeing problems that I am having a difficult :time tracking down. : :We have a server process which is connected to by many other :machines, each of them streams data in via tcp/ip. These connections :are pretty much permanent. : :All had been running fine for a long time before the upgrade, but :now we have a problem with read(2) returning an error ETIMEDOUT, :which causes our code to close the connection. : :The strange thing is that things are fine for a few hours, then :all of a sudden we see each of the connections fail with this error. :Then after the clients have reconnected, all is fine for a few :hours and then they all do it again. : :The problem I am having in tracking this down is that man 2 read :does not specify ETIMEDOUT as an error that can be returned from :read(2) and man errno specifies that it would be returned from :connect(2) or send(2) : :So, here is my question. Does anyone know under what circumstance :ETIMEDOUT may be returned from read(2) or is this a potential bug :somewhere ? : :Thanks, :Graham. This seems very odd. I recommend setting errno to 0 prior to calling read() to make sure that it is actually read() that is setting the errno. You should also sift through your code and look closely at any signal handlers you might have - system calls made from inside a signal handler can rip errno right out from under the code the signal interrupted. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 9:57:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 1487F37B401 for ; Thu, 7 Jun 2001 09:57:48 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 7171 invoked by uid 1000); 7 Jun 2001 16:56:34 -0000 Date: Thu, 7 Jun 2001 19:56:34 +0300 From: Peter Pentchev To: hackers@FreeBSD.org Subject: Re: free() and const warnings Message-ID: <20010607195634.I724@ringworld.oblivion.bg> Mail-Followup-To: hackers@FreeBSD.org References: <20010607190722.G724@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010607190722.G724@ringworld.oblivion.bg>; from roam@orbitel.bg on Thu, Jun 07, 2001 at 07:07:22PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 07, 2001 at 07:07:22PM +0300, Peter Pentchev wrote: > Hi, > > Is free((void *) (size_t) ptr) the only way to free a const whatever *ptr > with WARNS=2? (or more specifically, with -Wcast-qual) Uhm. OK. So size_t may not be enough to hold a pointer. What is it then - caddr_t? G'luck, Peter -- "yields falsehood, when appended to its quotation." yields falsehood, when appended to its quotation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 10: 2: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monty.mutatus.co.uk (monty.mutatus.co.uk [195.184.238.178]) by hub.freebsd.org (Postfix) with ESMTP id 4C41537B401 for ; Thu, 7 Jun 2001 10:02:04 -0700 (PDT) (envelope-from gbarr@mutatus.co.uk) Received: (from gbarr@localhost) by monty.mutatus.co.uk (8.11.3/8.11.3) id f57H0B103830; Thu, 7 Jun 2001 18:00:11 +0100 (BST) (envelope-from gbarr) Date: Thu, 7 Jun 2001 18:00:11 +0100 From: Graham Barr To: Matt Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: read(2) and ETIMEDOUT Message-ID: <20010607180011.U50444@pobox.com> References: <20010607171501.S50444@pobox.com> <200106071653.f57Grsn73369@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106071653.f57Grsn73369@earth.backplane.com>; from dillon@earth.backplane.com on Thu, Jun 07, 2001 at 09:53:54AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks, I will try setting errno, but I don't think it is signals. I have been running truss on the process. The relevant part is gettimeofday(0xbfbffa54,0x0) = 0 (0x0) select(0x50,0x93f8c90,0x0,0x0,0xbfbffa74) = 3 (0x3) read(0x16,0xa2da000,0x8000) ERR#60 'Operation timed out' In fact there are no signals in the whole truss output Graham. On Thu, Jun 07, 2001 at 09:53:54AM -0700, Matt Dillon wrote: > :A while ago our systems were upgraded from 4.2 to 4.3-RC, and at > :this time we started seeing problems that I am having a difficult > :time tracking down. > : > :We have a server process which is connected to by many other > :machines, each of them streams data in via tcp/ip. These connections > :are pretty much permanent. > : > :All had been running fine for a long time before the upgrade, but > :now we have a problem with read(2) returning an error ETIMEDOUT, > :which causes our code to close the connection. > : > :The strange thing is that things are fine for a few hours, then > :all of a sudden we see each of the connections fail with this error. > :Then after the clients have reconnected, all is fine for a few > :hours and then they all do it again. > : > :The problem I am having in tracking this down is that man 2 read > :does not specify ETIMEDOUT as an error that can be returned from > :read(2) and man errno specifies that it would be returned from > :connect(2) or send(2) > : > :So, here is my question. Does anyone know under what circumstance > :ETIMEDOUT may be returned from read(2) or is this a potential bug > :somewhere ? > : > :Thanks, > :Graham. > > This seems very odd. I recommend setting errno to 0 prior to calling > read() to make sure that it is actually read() that is setting the > errno. You should also sift through your code and look closely at any > signal handlers you might have - system calls made from inside a signal > handler can rip errno right out from under the code the signal > interrupted. > > -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 10:18: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natpost.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id E5A4B37B406 for ; Thu, 7 Jun 2001 10:17:58 -0700 (PDT) (envelope-from Stefan.Hoffmeister@Econos.de) Received: from stefan-bt (pD95024D6.dip.t-dialin.net [217.80.36.214]) by post.webmailer.de (8.9.3/8.8.7) with SMTP id TAA24386; Thu, 7 Jun 2001 19:17:55 +0200 (MET DST) From: Stefan Hoffmeister To: Daniel Eischen Cc: Stefan Hoffmeister , freebsd-hackers@FreeBSD.ORG Subject: Re: libc_r, signal handler ucontext modification Date: Thu, 07 Jun 2001 19:16:57 +0200 Organization: Econos Message-ID: <4bdvhtgru1j77uvphko0dsg8ohpj8beloh@4ax.com> References: In-Reply-To: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : On Thu, 7 Jun 2001 12:07:50 -0400 (EDT), Daniel Eischen wrote: >On Thu, 7 Jun 2001, Stefan Hoffmeister wrote: >> [copy context back into thread] >You can't do that. There is no requirement that the interrupted thread >is the one that handles the signal. If you copy the context back to >the current threads context storage, then you'll possibly end up with >2 threads running (or trying to run) on the same stack! Ouch :-) >You could also easily modify the context and do a >sigreturn(ucp) on it to achieve the same effect (being careful to make >sure you're not trying to jump to another threads context). This sounds very good, indeed. I do not want to make a context switch; essentially all I care about is that * the changed value of EIP is taken * ESP (from context) is retained * Changed values of EAX, EDX are taken AFA sigreturn is concerned: libc_r.so (!) does not export it; it only exports _thread_sys_sigreturn. Is there some kind of "__strong_reference" missing? In a slightly daring move, I am calling _thread_sys_sigreturn and, in my trivial test scenario, this seems to work - now I wonder whether it is supposed to work? IOW, is _thread_sys_sigreturn an alias for sigreturn in libc_r.so? Thanks very much, Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 10:20:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D59F737B403 for ; Thu, 7 Jun 2001 10:20:54 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f57HKm133192; Thu, 7 Jun 2001 10:20:48 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010607195634.I724@ringworld.oblivion.bg> Date: Thu, 07 Jun 2001 10:20:51 -0700 (PDT) From: John Baldwin To: Peter Pentchev Subject: Re: free() and const warnings Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 07-Jun-01 Peter Pentchev wrote: > On Thu, Jun 07, 2001 at 07:07:22PM +0300, Peter Pentchev wrote: >> Hi, >> >> Is free((void *) (size_t) ptr) the only way to free a const whatever *ptr >> with WARNS=2? (or more specifically, with -Wcast-qual) > > Uhm. OK. So size_t may not be enough to hold a pointer. What is it then - > caddr_t? uintptr_t for data pointers. In theory I think code pointers may not fit in a uintptr_t. free((void *)(uintptr_t)ptr) should work. Of course, this begs the question of why you are free'ing a const. :) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 10:33:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 4100E37B403 for ; Thu, 7 Jun 2001 10:33:53 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f57HXov74249; Thu, 7 Jun 2001 10:33:50 -0700 (PDT) (envelope-from dillon) Date: Thu, 7 Jun 2001 10:33:50 -0700 (PDT) From: Matt Dillon Message-Id: <200106071733.f57HXov74249@earth.backplane.com> To: Graham Barr Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: read(2) and ETIMEDOUT References: <20010607171501.S50444@pobox.com> <200106071653.f57Grsn73369@earth.backplane.com> <20010607180011.U50444@pobox.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :Thanks, I will try setting errno, but I don't think it is signals. :I have been running truss on the process. The relevant part is : :gettimeofday(0xbfbffa54,0x0) = 0 (0x0) :select(0x50,0x93f8c90,0x0,0x0,0xbfbffa74) = 3 (0x3) :read(0x16,0xa2da000,0x8000) ERR#60 'Operation timed out' : :In fact there are no signals in the whole truss output : :Graham. What type of descriptor is the read being performed on? A TCP connection or, say, a reading a file over NFS? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 10:37:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monty.mutatus.co.uk (monty.mutatus.co.uk [195.184.238.178]) by hub.freebsd.org (Postfix) with ESMTP id 72E2B37B401 for ; Thu, 7 Jun 2001 10:37:21 -0700 (PDT) (envelope-from gbarr@mutatus.co.uk) Received: (from gbarr@localhost) by monty.mutatus.co.uk (8.11.3/8.11.3) id f57HZZe04162; Thu, 7 Jun 2001 18:35:35 +0100 (BST) (envelope-from gbarr) Date: Thu, 7 Jun 2001 18:35:35 +0100 From: Graham Barr To: Matt Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: read(2) and ETIMEDOUT Message-ID: <20010607183535.X50444@pobox.com> References: <20010607171501.S50444@pobox.com> <200106071653.f57Grsn73369@earth.backplane.com> <20010607180011.U50444@pobox.com> <200106071733.f57HXov74249@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106071733.f57HXov74249@earth.backplane.com>; from dillon@earth.backplane.com on Thu, Jun 07, 2001 at 10:33:50AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 07, 2001 at 10:33:50AM -0700, Matt Dillon wrote: > > : > :Thanks, I will try setting errno, but I don't think it is signals. > :I have been running truss on the process. The relevant part is > : > :gettimeofday(0xbfbffa54,0x0) = 0 (0x0) > :select(0x50,0x93f8c90,0x0,0x0,0xbfbffa74) = 3 (0x3) > :read(0x16,0xa2da000,0x8000) ERR#60 'Operation timed out' > : > :In fact there are no signals in the whole truss output > : > :Graham. > > What type of descriptor is the read being performed on? A TCP > connection or, say, a reading a file over NFS? It is a TCP/IP connection. Graham. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 10:47:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shade.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id E862937B406; Thu, 7 Jun 2001 10:47:49 -0700 (PDT) (envelope-from nectar@nectar.com) Received: (from nectar@localhost) by shade.nectar.com (8.11.3/8.11.3) id f57HlUR05191; Thu, 7 Jun 2001 12:47:30 -0500 (CDT) (envelope-from nectar) Date: Thu, 7 Jun 2001 12:47:30 -0500 From: "Jacques A. Vidrine" To: John Baldwin Cc: Peter Pentchev , hackers@FreeBSD.org Subject: Re: free() and const warnings Message-ID: <20010607124729.B4940@shade.nectar.com> References: <20010607195634.I724@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Thu, Jun 07, 2001 at 10:20:51AM -0700 X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 07, 2001 at 10:20:51AM -0700, John Baldwin wrote: > > On 07-Jun-01 Peter Pentchev wrote: > > On Thu, Jun 07, 2001 at 07:07:22PM +0300, Peter Pentchev wrote: > >> Hi, > >> > >> Is free((void *) (size_t) ptr) the only way to free a const whatever *ptr > >> with WARNS=2? (or more specifically, with -Wcast-qual) > > > > Uhm. OK. So size_t may not be enough to hold a pointer. What is it then - > > caddr_t? > > uintptr_t for data pointers. In theory I think code pointers may not fit in a > uintptr_t. C99 says of uintptr_t only that for any valid pointer p, the following is true: (void *)(uintptr_t)p == (void *)p Likewise for intptr_t. I read that as covering both code and data pointers. Of course, who's to say the way uintptr_t is implemented on our platform adheres to the same rules :-) > free((void *)(uintptr_t)ptr) should work. > > Of course, this begs the question of why you are free'ing a const. :) Indeed! Cheers, -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 11:49:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtppop1pub.verizon.net (smtppop1pub.gte.net [206.46.170.20]) by hub.freebsd.org (Postfix) with ESMTP id 40CB437B403 for ; Thu, 7 Jun 2001 11:49:24 -0700 (PDT) (envelope-from tywain.@verizon.net) Received: from hppav (2Cust34.tnt1.daleville.al.da.uu.net [63.10.102.34]) by smtppop1pub.verizon.net with SMTP for ; id NAA119867057 Thu, 7 Jun 2001 13:49:22 -0500 (CDT) Message-ID: <000b01c0ef93$6aa98760$22660a3f@hppav> From: "tywain.griffen" To: Subject: FreeBSD Date: Thu, 7 Jun 2001 13:49:55 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C0EF58.BBCE64C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C0EF58.BBCE64C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To whom this concern, Please send me a FreeBSD. My address is: 110 Juniper Dr. Ozark, Al 36360 Tywain Griffen ------=_NextPart_000_0007_01C0EF58.BBCE64C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
To whom this concern,
  Please send me a FreeBSD. My = address=20 is:
 
 
          &nbs= p;     =20 110 Juniper Dr.
          &nbs= p;      Ozark,=20 Al 36360
 
Tywain = Griffen
------=_NextPart_000_0007_01C0EF58.BBCE64C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 11:55:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailgw3a.lmco.com (mailgw3a.lmco.com [192.35.35.24]) by hub.freebsd.org (Postfix) with ESMTP id 2656837B403 for ; Thu, 7 Jun 2001 11:55:49 -0700 (PDT) (envelope-from rick.norman@lmco.com) Received: from emss01g01.ems.lmco.com ([129.197.181.54]) by mailgw3a.lmco.com (8.8.8/8.8.8) with ESMTP id OAA14641 for ; Thu, 7 Jun 2001 14:55:47 -0400 (EDT) Received: from CONVERSION-DAEMON by lmco.com (PMDF V5.2-32 #38886) id <0GEK00O01PWNCT@lmco.com> for freebsd-hackers@freebsd.org; Thu, 7 Jun 2001 11:55:35 -0700 (PDT) Received: from cui1.lmms.lmco.com ([129.197.1.64]) by lmco.com (PMDF V5.2-32 #38886) with ESMTP id <0GEK00EVMPWI42@lmco.com> for freebsd-hackers@freebsd.org; Thu, 07 Jun 2001 11:55:30 -0700 (PDT) Received: from lmco.com (CONNECTICUT1.lmms.lmco.com [129.197.23.84]) by cui1.lmms.lmco.com (8.11.0/8.9.2) with ESMTP id f57ItSA10972 for ; Thu, 07 Jun 2001 11:55:28 -0700 (PDT) Date: Thu, 07 Jun 2001 11:55:43 -0700 From: rick norman Subject: Re: read(2) and ETIMEDOUT To: freebsd-hackers@freebsd.org Message-id: <3B1FCE2F.8B20E1EC@lmco.com> MIME-version: 1.0 X-Mailer: Mozilla 4.77 [en] (WinNT; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en References: <20010607171501.S50444@pobox.com> <200106071653.f57Grsn73369@earth.backplane.com> <20010607180011.U50444@pobox.com> <200106071733.f57HXov74249@earth.backplane.com> <20010607183535.X50444@pobox.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've seen this behavior in the past. My impression is that it is load related. If you do a grep on ETIMEDOUT in /usr/src/sys/netinet, you will see where the tcp stack may return this message. There may be some sysctl params relating to timers that you can muck with. Rick Graham Barr wrote: > On Thu, Jun 07, 2001 at 10:33:50AM -0700, Matt Dillon wrote: > > > > : > > :Thanks, I will try setting errno, but I don't think it is signals. > > :I have been running truss on the process. The relevant part is > > : > > :gettimeofday(0xbfbffa54,0x0) = 0 (0x0) > > :select(0x50,0x93f8c90,0x0,0x0,0xbfbffa74) = 3 (0x3) > > :read(0x16,0xa2da000,0x8000) ERR#60 'Operation timed out' > > : > > :In fact there are no signals in the whole truss output > > : > > :Graham. > > > > What type of descriptor is the read being performed on? A TCP > > connection or, say, a reading a file over NFS? > > It is a TCP/IP connection. > > Graham. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 12: 9:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id 7B5D037B408 for ; Thu, 7 Jun 2001 12:09:22 -0700 (PDT) (envelope-from bright@superconductor.rush.net) Received: (from bright@localhost) by superconductor.rush.net (8.11.2/8.11.2) id f57J9IX08202; Thu, 7 Jun 2001 15:09:18 -0400 (EDT) Date: Thu, 7 Jun 2001 15:09:17 -0400 From: Alfred Perlstein To: Graham Barr Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: read(2) and ETIMEDOUT Message-ID: <20010607150917.U1832@superconductor.rush.net> References: <20010607171501.S50444@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <20010607171501.S50444@pobox.com>; from gbarr@pobox.com on Thu, Jun 07, 2001 at 05:15:01PM +0100 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Graham Barr [010607 12:17] wrote: Since people seem to be helping you in other ways, I'll just answer this one: > So, here is my question. Does anyone know under what circumstance > ETIMEDOUT may be returned from read(2) or is this a potential bug > somewhere ? I'm quite sure ETIMEDOUT is a result of hitting the setsockopt SO_RCVTIMEO value when doing a read. -- -Alfred Perlstein [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 12:20:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monty.mutatus.co.uk (monty.mutatus.co.uk [195.184.238.178]) by hub.freebsd.org (Postfix) with ESMTP id 7287537B403 for ; Thu, 7 Jun 2001 12:20:39 -0700 (PDT) (envelope-from gbarr@mutatus.co.uk) Received: (from gbarr@localhost) by monty.mutatus.co.uk (8.11.3/8.11.3) id f57JIk205007; Thu, 7 Jun 2001 20:18:46 +0100 (BST) (envelope-from gbarr) Date: Thu, 7 Jun 2001 20:18:46 +0100 From: Graham Barr To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: read(2) and ETIMEDOUT Message-ID: <20010607201846.E50444@pobox.com> References: <20010607171501.S50444@pobox.com> <20010607150917.U1832@superconductor.rush.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010607150917.U1832@superconductor.rush.net>; from bright@rush.net on Thu, Jun 07, 2001 at 03:09:17PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 07, 2001 at 03:09:17PM -0400, Alfred Perlstein wrote: > * Graham Barr [010607 12:17] wrote: > > Since people seem to be helping you in other ways, I'll just > answer this one: > > > So, here is my question. Does anyone know under what circumstance > > ETIMEDOUT may be returned from read(2) or is this a potential bug > > somewhere ? > > I'm quite sure ETIMEDOUT is a result of hitting the setsockopt > SO_RCVTIMEO value when doing a read. I had been thinking along those lines too. But immediately before calling read, select said there was data to read, So it should not block, but read what data is there and return. Also why does this happen only every few hours ? There is a lot of data going through these connections maybe the timer for SO_RCVTIMEO is not being reset. But then we have another server, with a similar number of clients and data through put, but it does not suffer from this problem. As you can probably tell, we have been tearing our hair out over this one. Graham. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 12:29:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id AA4CD37B403 for ; Thu, 7 Jun 2001 12:29:08 -0700 (PDT) (envelope-from steveb99@earthlink.net) Received: from DROID (dhcp206.mis.earthlink.net [207.217.66.246]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id MAA11742; Thu, 7 Jun 2001 12:28:52 -0700 (PDT) Message-ID: <013d01c0ef88$0911b500$f642d9cf@DROID> From: "Steve B." To: "tywain.griffen" , References: <000b01c0ef93$6aa98760$22660a3f@hppav> Subject: Re: FreeBSD Date: Thu, 7 Jun 2001 12:28:29 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_013A_01C0EF4D.5BDCEF60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_013A_01C0EF4D.5BDCEF60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Below is the URL on where you can download FreeBSD. =20 http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/mirrors-ftp.ht= ml IF you want it on CD-ROM below is the URL to places that sell it. http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/mirrors.html All this info and more is available at http://www.freebsd.org Steve B. ----- Original Message -----=20 From: tywain.griffen=20 To: freebsd-hackers@FreeBSD.org=20 Sent: Thursday, June 07, 2001 1:49 PM Subject: FreeBSD To whom this concern, Please send me a FreeBSD. My address is: 110 Juniper Dr. Ozark, Al 36360 Tywain Griffen ------=_NextPart_000_013A_01C0EF4D.5BDCEF60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Below is the URL on where you can = download=20 FreeBSD. 
 
http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/mi= rrors-ftp.html
 
IF you want it on CD-ROM below is = the URL to=20 places that sell it.
 
http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/mirror= s.html
 
All this info and more is available=20 at
 
http://www.freebsd.org
 
Steve B.
----- Original Message -----
From:=20 tywain.griffen
Sent: Thursday, June 07, 2001 = 1:49=20 PM
Subject: FreeBSD

To whom this concern,
  Please send me a FreeBSD. My = address=20 is:
 
 
          &nbs= p;     =20 110 Juniper Dr.
          &nbs= p;      Ozark,=20 Al 36360
 
Tywain=20 Griffen
------=_NextPart_000_013A_01C0EF4D.5BDCEF60-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 12:53:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 0768F37B401 for ; Thu, 7 Jun 2001 12:53:47 -0700 (PDT) (envelope-from chris@holly.calldei.com) Received: from holly.calldei.com ([208.191.149.190]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10) with ESMTP id <0GEK000IQPX5ZK@mta4.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Thu, 7 Jun 2001 13:55:59 -0500 (CDT) Received: (from chris@localhost) by holly.calldei.com (8.11.1/8.9.3) id f57IsgA43048; Thu, 07 Jun 2001 13:54:42 -0500 (CDT envelope-from chris) Date: Thu, 07 Jun 2001 13:53:09 -0500 From: Chris Costello Subject: Re: FreeBSD In-reply-to: <000b01c0ef93$6aa98760$22660a3f@hppav>; from tywain.@verizon.net on Thu, Jun 07, 2001 at 01:49:55PM -0700 To: "tywain.griffen" <"tywain."@verizon.net> Cc: freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20010607135309.C36740@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <000b01c0ef93$6aa98760$22660a3f@hppav> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thursday, June 07, 2001, tywain.griffen wrote: > To whom this concern, > Please send me a FreeBSD. My address is: > > > 110 Juniper Dr. > Ozark, Al 36360 If anything, this should've gone to freebsd-questions@FreeBSD.org, but it really doesn't belong there, either. To get FreeBSD sent to you, please order it from http://www.FreeBSDMall.com/. Thanks. -- +-------------------+--------------------------------------------+ | Chris Costello | Anybody can win, | | chris@calldei.com | unless there happens to be a second entry. | +-------------------+--------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 13:16:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 8713037B41A for ; Thu, 7 Jun 2001 13:16:21 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 7 Jun 2001 21:16:20 +0100 (BST) To: Graham Barr Cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: read(2) and ETIMEDOUT In-Reply-To: Your message of "Thu, 07 Jun 2001 20:18:46 BST." <20010607201846.E50444@pobox.com> Date: Thu, 07 Jun 2001 21:16:19 +0100 From: Ian Dowse Message-ID: <200106072116.aa63698@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010607201846.E50444@pobox.com>, Graham Barr writes: >Also why does this happen only every few hours ? There is a lot of >data going through these connections maybe the timer for SO_RCVTIMEO >is not being reset. > >But then we have another server, with a similar number of clients and >data through put, but it does not suffer from this problem. I suspect that the server seeing this problem has a client that occasionally disappears from the network, or for whatever reason fails to respond to any packets for a long time (something like 5 or 10 minutes). I've seen blocking TCP writes return ETIMEDOUT when the network between the client and the server goes down. In the non-blocking case I think the following can happen: 1) Client is connected to server. 2) Network goes down, or client is turned off 3) Server performs non-blocking write() on socket 4) Server uses poll/select/kevent waiting for data from socket 5) The write operation times out because no acknowledgements have been received. This occurs after TCP_MAXRXTSHIFT retransmits, so->so_error is set to ETIMEDOUT and the connection is shut down (I haven't read the code very carefully, so the details could be wrong. 6) select/poll/kevent notes the EOF condition, and says that the descriptor is ready to read. 7) read() returns the real error, which is ETIMEDOUT. I guess this should possibly be documented in read(2), but in practice there are numerous network errors that can be returned from read(). Normal practice in single-process servers is to consider any unknown errors from read(),write() etc as only fatal to that client rather than the whole server. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 13:24:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monty.mutatus.co.uk (monty.mutatus.co.uk [195.184.238.178]) by hub.freebsd.org (Postfix) with ESMTP id 2F89E37B401 for ; Thu, 7 Jun 2001 13:24:17 -0700 (PDT) (envelope-from gbarr@mutatus.co.uk) Received: (from gbarr@localhost) by monty.mutatus.co.uk (8.11.3/8.11.3) id f57KMP905622; Thu, 7 Jun 2001 21:22:25 +0100 (BST) (envelope-from gbarr) Date: Thu, 7 Jun 2001 21:22:24 +0100 From: Graham Barr To: Ian Dowse Cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: read(2) and ETIMEDOUT Message-ID: <20010607212224.M50444@pobox.com> References: <20010607201846.E50444@pobox.com> <200106072116.aa63698@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106072116.aa63698@salmon.maths.tcd.ie>; from iedowse@maths.tcd.ie on Thu, Jun 07, 2001 at 09:16:19PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG While this does sound very plausable,... The server does not do any writes, data only travels from the clients to the server. The clients and the server are connected to the same switch. The other server which is similar is on the same network and is connected to by the same machines as clients, yet it does not see any problems. But thanks for the insight. I will place a sniffer of the port and see if there are excessive retransmits Graham. On Thu, Jun 07, 2001 at 09:16:19PM +0100, Ian Dowse wrote: > In message <20010607201846.E50444@pobox.com>, Graham Barr writes: > > >Also why does this happen only every few hours ? There is a lot of > >data going through these connections maybe the timer for SO_RCVTIMEO > >is not being reset. > > > >But then we have another server, with a similar number of clients and > >data through put, but it does not suffer from this problem. > > I suspect that the server seeing this problem has a client that > occasionally disappears from the network, or for whatever reason > fails to respond to any packets for a long time (something like 5 > or 10 minutes). I've seen blocking TCP writes return ETIMEDOUT when > the network between the client and the server goes down. In the > non-blocking case I think the following can happen: > > 1) Client is connected to server. > 2) Network goes down, or client is turned off > 3) Server performs non-blocking write() on socket > 4) Server uses poll/select/kevent waiting for data from socket > 5) The write operation times out because no acknowledgements > have been received. This occurs after TCP_MAXRXTSHIFT > retransmits, so->so_error is set to ETIMEDOUT and the > connection is shut down (I haven't read the code very > carefully, so the details could be wrong. > 6) select/poll/kevent notes the EOF condition, and says that > the descriptor is ready to read. > 7) read() returns the real error, which is ETIMEDOUT. > > I guess this should possibly be documented in read(2), but in > practice there are numerous network errors that can be returned > from read(). Normal practice in single-process servers is to > consider any unknown errors from read(),write() etc as only > fatal to that client rather than the whole server. > > Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 15: 1:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 04C5C37B405 for ; Thu, 7 Jun 2001 15:01:23 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id SAA13329; Thu, 7 Jun 2001 18:00:41 -0400 (EDT) Date: Thu, 7 Jun 2001 18:00:41 -0400 (EDT) From: Daniel Eischen To: Stefan Hoffmeister Cc: Stefan Hoffmeister , freebsd-hackers@FreeBSD.ORG Subject: Re: libc_r, signal handler ucontext modification In-Reply-To: <4bdvhtgru1j77uvphko0dsg8ohpj8beloh@4ax.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 7 Jun 2001, Stefan Hoffmeister wrote: > : On Thu, 7 Jun 2001 12:07:50 -0400 (EDT), Daniel Eischen wrote: > > >On Thu, 7 Jun 2001, Stefan Hoffmeister wrote: > > >> [copy context back into thread] > > >You can't do that. There is no requirement that the interrupted thread > >is the one that handles the signal. If you copy the context back to > >the current threads context storage, then you'll possibly end up with > >2 threads running (or trying to run) on the same stack! > > Ouch :-) > > >You could also easily modify the context and do a > >sigreturn(ucp) on it to achieve the same effect (being careful to make > >sure you're not trying to jump to another threads context). > > This sounds very good, indeed. I do not want to make a context switch; > essentially all I care about is that > > * the changed value of EIP is taken > > * ESP (from context) is retained > > * Changed values of EAX, EDX are taken > > AFA sigreturn is concerned: libc_r.so (!) does not export it; it only > exports _thread_sys_sigreturn. Is there some kind of "__strong_reference" > missing? > > In a slightly daring move, I am calling _thread_sys_sigreturn and, in my > trivial test scenario, this seems to work - now I wonder whether it is > supposed to work? > > IOW, is _thread_sys_sigreturn an alias for sigreturn in libc_r.so? Yeah, I don't know why sigreturn is hidden any longer. I don't think there's a need for it to be hidden. I suppose we could wrap it and check to make sure the thread performing the sigreturn isn't trying to return to a stack that isn't its own (like we do for siglongjmp/longjmp). -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 15: 2:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hokkshideh.jetcafe.org (hokkshideh.jetcafe.org [205.147.43.4]) by hub.freebsd.org (Postfix) with ESMTP id 179E337B406 for ; Thu, 7 Jun 2001 15:02:18 -0700 (PDT) (envelope-from dave@jetcafe.org) Received: from hokkshideh.jetcafe.org (localhost [127.0.0.1]) by hokkshideh.jetcafe.org (8.8.8/8.8.5) with ESMTP id PAA04400 for ; Thu, 7 Jun 2001 15:02:07 -0700 (PDT) Message-Id: <200106072202.PAA04400@hokkshideh.jetcafe.org> X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.4 #1[UCI] To: freebsd-hackers@freebsd.org Subject: Why does fsck try to fsck a CDROM? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Jun 2001 15:02:06 -0700 From: Dave Hayes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If I boot from a CDROM (of my own creation admittedly), fsck -p wants to fsck the CD partition, /dev/ad0c. It is mounted as root. I look at the source and in preen.c I'm not able to see any way for fsck to do that. Granted I've never looked at fsck source before (I looked in /usr/src/sbin/fsck for it). Does anyone have any clues or am I going to have to insert printf() calls into it to see what is going on? ------ Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< "Challenges make you discover things about yourself that you never really knew." -Cicely Tyson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 15:11: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id 8DCC737B405 for ; Thu, 7 Jun 2001 15:11:05 -0700 (PDT) (envelope-from bright@superconductor.rush.net) Received: (from bright@localhost) by superconductor.rush.net (8.11.2/8.11.2) id f57MAhN30422; Thu, 7 Jun 2001 18:10:43 -0400 (EDT) Date: Thu, 7 Jun 2001 18:10:42 -0400 From: Alfred Perlstein To: Dave Hayes Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Why does fsck try to fsck a CDROM? Message-ID: <20010607181041.A1832@superconductor.rush.net> References: <200106072202.PAA04400@hokkshideh.jetcafe.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <200106072202.PAA04400@hokkshideh.jetcafe.org>; from dave@jetcafe.org on Thu, Jun 07, 2001 at 03:02:06PM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Dave Hayes [010607 18:02] wrote: > If I boot from a CDROM (of my own creation admittedly), fsck -p > wants to fsck the CD partition, /dev/ad0c. It is mounted as root. from fstab(5): The sixth field, (fs_passno), is used by the fsck(8) program to determine the order in which filesystem checks are done at reboot time. The root filesystem should be specified with a fs_passno of 1, and other filesys- tems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not present or is zero, a value of zero is returned and fsck(8) will assume that the filesystem does not need to be checked. -- -Alfred Perlstein [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 15:21: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 766B637B401 for ; Thu, 7 Jun 2001 15:21:00 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f57MKwv78170; Thu, 7 Jun 2001 15:20:58 -0700 (PDT) (envelope-from dillon) Date: Thu, 7 Jun 2001 15:20:58 -0700 (PDT) From: Matt Dillon Message-Id: <200106072220.f57MKwv78170@earth.backplane.com> To: Graham Barr Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: read(2) and ETIMEDOUT References: <20010607171501.S50444@pobox.com> <200106071653.f57Grsn73369@earth.backplane.com> <20010607180011.U50444@pobox.com> <200106071733.f57HXov74249@earth.backplane.com> <20010607183535.X50444@pobox.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :On Thu, Jun 07, 2001 at 10:33:50AM -0700, Matt Dillon wrote: :> :> : :> :Thanks, I will try setting errno, but I don't think it is signals. :> :I have been running truss on the process. The relevant part is :> : :> :gettimeofday(0xbfbffa54,0x0) = 0 (0x0) :> :select(0x50,0x93f8c90,0x0,0x0,0xbfbffa74) = 3 (0x3) :> :read(0x16,0xa2da000,0x8000) ERR#60 'Operation timed out' :> : :> :In fact there are no signals in the whole truss output :> : :> :Graham. :> :> What type of descriptor is the read being performed on? A TCP :> connection or, say, a reading a file over NFS? : :It is a TCP/IP connection. : :Graham. You can get this if the TCP connection times out, either through a keepalive timeout or the protocol hits the maximum number of transmit retries. I'd have to delve into the cvs logs to see when it was added, but it seems reasonable. You should treat it simply as an EIO or something like that. Generally speaking you should handle return codes from system calls by handling the codes you know about and simply assuming that anything else is fatal to the particular connection. if (systemcall(...) < 0) { switch(errno) { case EINTR: case EAGAIN: ... deal with non-blocking situations ... . . . default: ... assume everything else is a fatal error on the socket ... ... close the descriptor and cleanup its state ... } } This gives you the maximum portability between platforms and between releases. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 15:32:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hokkshideh.jetcafe.org (hokkshideh.jetcafe.org [205.147.43.4]) by hub.freebsd.org (Postfix) with ESMTP id 73E5837B405 for ; Thu, 7 Jun 2001 15:32:23 -0700 (PDT) (envelope-from dave@jetcafe.org) Received: from hokkshideh.jetcafe.org (localhost [127.0.0.1]) by hokkshideh.jetcafe.org (8.8.8/8.8.5) with ESMTP id PAA04935; Thu, 7 Jun 2001 15:32:19 -0700 (PDT) Message-Id: <200106072232.PAA04935@hokkshideh.jetcafe.org> X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.4 #1[UCI] To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Why does fsck try to fsck a CDROM? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Jun 2001 15:32:19 -0700 From: Dave Hayes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alfred Perlstein writes: > The sixth field, (fs_passno), is used by the fsck(8) program to > determine the order in which filesystem checks are done at > reboot time. Yep, good that you asked this, but not the problem. I not only set this field to zero *I deleted the /cdrom fstab entry from the file* and it still tried to preen it. ;) ------ Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< There *is* no such thing as peer pressure, only weak people. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 16:48:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 8579337B401 for ; Thu, 7 Jun 2001 16:48:31 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f57NmCV06179; Thu, 7 Jun 2001 16:48:12 -0700 Date: Thu, 7 Jun 2001 16:48:12 -0700 From: Brooks Davis To: Brian Somers Cc: Poul-Henning Kamp , hackers@FreeBSD.ORG Subject: Re: cloning network interfaces Message-ID: <20010607164812.A32379@Odin.AC.HMC.Edu> References: <200106071119.f57BJr766008@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="1yeeQ81UyVL57Vl7" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106071119.f57BJr766008@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Thu, Jun 07, 2001 at 12:19:53PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 07, 2001 at 12:19:53PM +0100, Brian Somers wrote: > > The quick and dirty way: > >=20 > > Make a clone handler despite the fact that there is no /dev > > entry needed. You don't actually have to create a dev entry > > in the clone handler, you could just create the gif_interface. > >=20 > > Applications would then: > >=20 > > stat("/dev/gif345") /* Ignore error */ > > system("ifconfig gif345 bla bla bla"); > >=20 > > The slower but less dirty: > >=20 > > Make a sysctl which returns an integer which is the next > > free gif device. > >=20 > > The really slow and very dirty: > >=20 > > Implement cloning in ifconfig. >=20 > Maybe a reasonable alternative would be to have a /dev/if_gif device=20 > with ioctls for creating and destroying interfaces. ifconfig(8)=20 > could be taught to create (and maybe even to delete) them. Ok, I've got the quick and dirty way working for testing (a nine line clone handler works great for that), but I think Brian's suggestion is probably best for a real solution especialy since it's rather easier to check for permissions before allowing creation this way. My current patch lets joe user create 2^15 gif devices by doing "ls /dev/gif###" 2^15 times because I didn't have a proc structure handy. The other advantage is that it should be fairly easy to backport to -stable which is where the project I'm working on this for is currently being developed. I think I'll add a to ifconfig function styled after ifmaybeload() that trys to create interfaces if the user trys to do something with them. I'm still thinking about the right way to handle creation of new, free devices, perhaps a syntax like: ifconfig gif# where ifconfig returns the interface name the way mdconfig does when you don't specify a unit. If we decied that interfaces that want to grow this way will have a /dev/if_ device that accepts the appropriate ioctl(s), that should be fairly easy to implement so it works in all cases without further hacks to ifconfig. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --1yeeQ81UyVL57Vl7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7IBK7XY6L6fI4GtQRArgRAKCTEczHrnop8a5ipQCGC3+Q/xeMPgCgrxNu pTNli7jJmp7iaLAUgpIZbmc= =tXUK -----END PGP SIGNATURE----- --1yeeQ81UyVL57Vl7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 18:51:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0EAD337B401 for ; Thu, 7 Jun 2001 18:51:34 -0700 (PDT) (envelope-from obrien@nuxi.ucdavis.edu) Received: from dragon.nuxi.com (root@trang.muxi.com [206.40.252.115] (may be forged)) by relay.nuxi.com (8.11.2/8.11.2) with ESMTP id f581pLR23303; Thu, 7 Jun 2001 18:51:21 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f581pLC98564; Thu, 7 Jun 2001 18:51:21 -0700 (PDT) (envelope-from obrien) Date: Thu, 7 Jun 2001 18:51:21 -0700 From: "David O'Brien -Hackers" To: Dave Hayes Cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: Why does fsck try to fsck a CDROM? Message-ID: <20010607185120.A98526@dragon.nuxi.com> Reply-To: freebsd-hackers@FreeBSD.ORG References: <200106072232.PAA04935@hokkshideh.jetcafe.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106072232.PAA04935@hokkshideh.jetcafe.org>; from dave@jetcafe.org on Thu, Jun 07, 2001 at 03:32:19PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 07, 2001 at 03:32:19PM -0700, Dave Hayes wrote: > Alfred Perlstein writes: > > The sixth field, (fs_passno), is used by the fsck(8) program to > > determine the order in which filesystem checks are done at > > reboot time. > > Yep, good that you asked this, but not the problem. I not only set > this field to zero *I deleted the /cdrom fstab entry from the file* > and it still tried to preen it. ;) You mentioned though that your CDROM is /. How about posting the real /etc/fstab from your root partition for us to have a look at? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 18:55:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2094337B403; Thu, 7 Jun 2001 18:55:55 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f581tsV16004; Thu, 7 Jun 2001 19:55:54 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200106080155.f581tsV16004@harmony.village.org> To: John Baldwin Subject: Re: free() and const warnings Cc: Peter Pentchev , hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 07 Jun 2001 10:20:51 PDT." References: Date: Thu, 07 Jun 2001 19:55:54 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message John Baldwin writes: : Of course, this begs the question of why you are free'ing a const. :) Sometimes that's the only handle that you have on the object :-). I sometimes think that changing free to be const void * is the right answer, but that has its own set problems :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 19: 9:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hokkshideh.jetcafe.org (hokkshideh.jetcafe.org [205.147.43.4]) by hub.freebsd.org (Postfix) with ESMTP id 6692637B401 for ; Thu, 7 Jun 2001 19:09:42 -0700 (PDT) (envelope-from dave@jetcafe.org) Received: from hokkshideh.jetcafe.org (localhost [127.0.0.1]) by hokkshideh.jetcafe.org (8.8.8/8.8.5) with ESMTP id TAA08276 for ; Thu, 7 Jun 2001 19:09:41 -0700 (PDT) Message-Id: <200106080209.TAA08276@hokkshideh.jetcafe.org> X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.4 #1[UCI] To: freebsd-hackers@FreeBSD.ORG Subject: Re: Why does fsck try to fsck a CDROM? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Jun 2001 19:09:41 -0700 From: Dave Hayes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David O'Brien -Hackers writes: > You mentioned though that your CDROM is /. How about posting the real > /etc/fstab from your root partition for us to have a look at? There is none. No default fstab exists. ------ Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< "It's freedom of speech, as long as you don't say too much." -Aaron Neville To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 20: 2:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id ACC0537B405; Thu, 7 Jun 2001 20:02:15 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by probity.mcc.ac.uk with esmtp (Exim 2.05 #7) id 158CXN-0008tM-00; Fri, 8 Jun 2001 04:02:13 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.3/8.11.1) id f5832Bs61511; Fri, 8 Jun 2001 04:02:11 +0100 (BST) (envelope-from jcm) Date: Fri, 8 Jun 2001 04:02:11 +0100 From: j mckitrick To: Doug Rabson Cc: "Matthew N. Dodd" , Warner Losh , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: newbussifying drivers Message-ID: <20010608040211.A61278@dogma.freebsd-uk.eu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from dfr@nlsystems.com on Thu, Jun 07, 2001 at 12:39:29PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG | > > : How would you recommending fixing this, taken from the ex driver? | > > | > > By deleting it. | > | > Uh, what? | > | > Non PnP devices that can be autodetected should be autodetected. | > | > Relying on the user to wire down hints is silly. | | Probably they should provide an identify method to look for and create the | non-PnP devices. The actual probe method should be dumb and just use the | resources given to it (IMHO). Okay, there is something i'm not understanding here. In the ed driver, there are many possible cards, which each have different i/o ports, correct? The driver has a lot of probe routines, and it looks like they are just using different macros with hard-coded (#defined) port addresses. So, how do you CORRECTLY use the newbus calls to probe these ports? I am not running -current, so i do not have 'hints'. jcm -- "I drank WHAT ?!" - Socrates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 20:13:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 458B837B405; Thu, 7 Jun 2001 20:13:19 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f583BnV16330; Thu, 7 Jun 2001 21:11:49 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200106080311.f583BnV16330@harmony.village.org> To: j mckitrick Subject: Re: newbussifying drivers Cc: Doug Rabson , "Matthew N. Dodd" , Mike Smith , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 08 Jun 2001 04:02:11 BST." <20010608040211.A61278@dogma.freebsd-uk.eu.org> References: <20010608040211.A61278@dogma.freebsd-uk.eu.org> Date: Thu, 07 Jun 2001 21:11:49 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010608040211.A61278@dogma.freebsd-uk.eu.org> j mckitrick writes: : Okay, there is something i'm not understanding here. In the ed driver, : there are many possible cards, which each have different i/o ports, correct? Not really. The ed driver is the most twisted driver in the tree when it comes to probe. : The driver has a lot of probe routines, and it looks like they are just : using different macros with hard-coded (#defined) port addresses. Usually no. There are many different ways to hook up the hardware and each ISA card vendor chose differently before ne2000 became standard. : So, how do you CORRECTLY use the newbus calls to probe these ports? I am : not running -current, so i do not have 'hints'. hints are in -stable, they just live in the kernel config file there. I'm not sure what the best thing to do is. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jun 7 22:26: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from aries.ai.net (aries.ai.net [205.134.163.4]) by hub.freebsd.org (Postfix) with ESMTP id B8F8A37B403 for ; Thu, 7 Jun 2001 22:25:54 -0700 (PDT) (envelope-from deepak@ai.net) Received: from blood (adsl-138-88-76-66.dc.adsl.bellatlantic.net [138.88.76.66]) by aries.ai.net (8.9.3/8.9.3) with SMTP id BAA28987 for ; Fri, 8 Jun 2001 01:25:53 -0400 (EDT) (envelope-from deepak@ai.net) Reply-To: From: "Deepak Jain" To: Subject: New error - lost data? Date: Fri, 8 Jun 2001 01:29:50 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've never seen this error. Its been occuring randomly on this machine, sometimes as often as every few minutes, sometimes days apart. Others have seen this error (based on a Google search) but nothing recent and nothing that conclusive. This is a very standard config that has been stable for quite a while. The panic: malloc: lost data implies to me that something is misbehaving with its memory allocations. Is this a hardware issue or an application problem? The kernel is 4.1 RELEASE. The RAM is ECC. Any assistance would be appreciated! Thanks, Deepak Jain AiNET Jun 5 01:02:56 play /kernel: panic: malloc: lost data Jun 5 01:02:56 play /kernel: Jun 5 01:02:56 play /kernel: syncing disks... 440 440 440 440 440 440 440 440 Jun 5 01:02:56 play /kernel: giving up on 433 buffers Jun 5 01:02:56 play /kernel: Uptime: 3m11s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 0:33:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 7871337B401 for ; Fri, 8 Jun 2001 00:33:18 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.138.245.Dial1.SanJose1.Level3.net [209.245.138.245]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA00768; Fri, 8 Jun 2001 00:33:12 -0700 (PDT) Message-ID: <3B207642.A7C7E7C@mindspring.com> Date: Thu, 07 Jun 2001 23:52:50 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ian Dowse Cc: Matt Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: UFS large directory performance References: <200106021207.aa78407@salmon.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ian Dowse wrote: > > The only potential problem I see here is that you could > > end up seriously fragmenting the malloc pool you are > > using to allocate the slot arrays. And, of course, the > > two issues you brought up in regards to regularing memory > > use. > > Thanks for the comments :-) Yes, malloc pool fragmentation is a > problem. I think that it can be addressed to some extent by using > a 2-level system (an array of pointers to fixed-size arrays) instead > of a single large array, but I'm open to any better suggestions. Use a chain allocator. I would suggest using the zone allocator, but it has some fundamental problems that I don't think are really resolvable without a rewrite. Unlike the zone allocator, which rounds to 64 byte units, a chain allocator allocates a free chain that is fit to a 32 bit boundary (4 bytes instead of 64, for an average wastage of 2, instead of 32, bytes, if there is any at all). In addition, the allocator will allocate based on least common multiple (after 32 bit rounding), and will use a backing object size to get the multiple. For a 60 byte object, this would mean allocating 15 pages, and dividing it into 1024 objexts (2048 for Alpha, with its 8k page size). But the memory can be backed by kmem_malloc() or alloc(), which allocates page units, instead of by the power of 2 allocator. And there are zero bytes wasted. The memory also need not be permanently type stable, like memory in a zone, though you would need to build a reclaimer that ran in the background. You could make it deterministic, by sorting the freelist in chunks of the allocation unit at a time (see Knuth; a quicksort is really not appropriate). You could use a second level reclaim to return memory to the system; this would effectively make it a hybrid between the Dynix zone allocator (on which it is modelled), and a slab allocator. Finally, you could maintain per-cpu chains to allow the allocations and frees to occur on a per CPU basis; that would mean that there was no IPI or bus contention for allocations or deallocations (whether you want to defer migration of objects to the chains of their home CPU, or let the free to the system at a low watermark take care of that for you, giving preference to frees of non-local origin elements, is reall a policy decision). I've actually written one of these, without the Dynix style reclaimer (e.g. the memory becomes type stable only after allocation, which makes it an improvement on the zone allocator, at the cost of not being usable at interrupt time for allocations), as part of some performance improvement work in a modified FreeBSD kernel. > If the second-level array size was fixed at around 4k, that would > keep the variable-length first-level array small enough not to > cause too many fragmentation issues. The per-DIRBLKSIZ free space > summary array is probably relatively okay as it is now. If you are going to fix it, and your object happens to be an even power of 2 in size, at the very least, make the backing object be the page size, so it will still work well on the Alpha, without page fragmentation. I rather expect that the IA64 will end up forcing our Intel page size to be increased. > The other main issue, that of discarding old hashes when the memory > limit is reached, may be quite tricky to resolve. Any approach > based on doing this from ufsdirhash_build() is likely to become a > locking nightmare. My original idea was to have ufsdirhash_build() > walk a list of other inodes with hashes attached and free them if > possible, but that would involve locking the other inode, so things > could get messy. Add an LRU field, and lock the hashes on a "32 object at a time" or similarly high granularity. This is more natural with a chain block, of course, but works well in any case. I have been considering moving the per process open file table into a direct/indirect object list, similar to the SVR4 method, rather than the size doubling, for similar performance reasons. Locking a block of files, and maintaining per block freelists (instead of a hints pointer -- what the heck else are you keeping in those idle structs anyway, such that you _shouldn't_ be cating them into a list?!?). If you poke around in that area long enough, you'll see that there are some "magic" numbers like "NFILES", which started out as an optimization, but which all the recent additions for things like kqueue event chains have turned into hopeless pessimizations. 8-(. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 0:44:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 684E237B405 for ; Fri, 8 Jun 2001 00:44:24 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.138.245.Dial1.SanJose1.Level3.net [209.245.138.245]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA19091; Fri, 8 Jun 2001 00:44:20 -0700 (PDT) Message-ID: <3B208271.9F1E93B1@mindspring.com> Date: Fri, 08 Jun 2001 00:44:49 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ian Dowse Cc: Matt Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: UFS large directory performance References: <200106031747.aa54373@salmon.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ian Dowse wrote: > Nice idea, but I'm not sure I see the benefit of partially reclaiming > second-level arrays. Because it is a hash array, there isn't really > the concept of a working set; a directory that is `in use' will > rarely see many create/rename/delete operations on a small fixed > set of filenames. The lookup case is already cached elsewhere. I > think an all-or-nothing approach is likely to perform better and > be simpler to implement. Even the lazy allocation of second-level > arrays is unlikely to help a lot if the hash function does its job > well. From this perspective, it seems to me that there could be significant benefit in getting rid of the ihash cache; but then I've always hated the thing, since there's no way to reassociate a vnode with valid, clean data hanging off it with an ihash entry, when you get an ihash cache hit. Totally off the dirpref topic, cut of the same philosophical bent that your statement above seems to advocate... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 1:38:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 8553D37B401 for ; Fri, 8 Jun 2001 01:38:22 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.138.245.Dial1.SanJose1.Level3.net [209.245.138.245]) by snipe.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA20638; Fri, 8 Jun 2001 01:38:13 -0700 (PDT) Message-ID: <3B208F11.87722148@mindspring.com> Date: Fri, 08 Jun 2001 01:38:41 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bill Fenner Cc: louie@transsys.com, freebsd-hackers@FreeBSD.ORG Subject: Re: How to disable software TCP checksumming? References: <20010529144114.I19771@luke.immure.com> <20010529221107.C49875@skriver.dk> <20010529155212.M19771@luke.immure.com> <20010530045200.A1031@hades.hell.gr> <20010529235215.A60177@luke.immure.com> <20010530085155.B24096@Odin.AC.HMC.Edu> <200105310204.f4V248n15260@whizzo.transsys.com> <200106070549.WAA06248@windsor.research.att.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bill Fenner wrote: > > >The TCP checksum protects more than just the contents of the packet > >on the wire; it's also a (somewhat) weak check on the contents > >of your packet sitting in memory, and as it's going over the bus > >in your computer between memory and peripherals and for other > >end-to-end sorts of issues. > > In fact, Jonathan Stone at Stanford did some measurements of > checksum errors for his thesis, and found that on a given link > in the Stanford residences there were a surprising (small, but > measurable) number of packets with IP header checksum errors > with what appeared to be DMA errors -- e.g. 4 bytes missing > from the middle of the header. When the end to end checksum > is really memory to memory, it can catch errors like this... You need to read the ethernet drivers in /sys/pci/if_*... Specifically, look for m_devget() uses, and the comments about why they are necessary. I will bet you that the 4 byte "holes" that appear to be "DMA errors" are actually driver errors, with drivers sending unaligned packets down to the the DMA engine. Further, if you characterize them, I bet you will see that the majority of them are Linux machines. The problem is that many cards require 4 byte alignment (one of the gigabit cards requires 64 bit alignment) for the DMA engine on the card to function properly. This annoys the piss out of TCP/IP stacks in host machines, which like to cast headers to pointers, and directly access the packet header contents. Naieve driver writers will do a 2 byte align on their assembled TCP/IP packets (causing the IP address to be on a 4 + 2 byte boundary, instead of a 4 byte boundary, and the DMA engine will choke. This all came from IP headers being 14 bytes long, instead of 16. Why card manufacturers can't make their DMA engine use an offset shif buffer is beyond me, but they don't do that, and so unaligned accesses happen. This slows down host processing, best case; worst case, the host is not careful to make the cards happy, and "holes" appear. In fact, it would not surprise me if the person conducting the research had the problem on his system, and the stuff on the network itself was actually all right, since it is generally a receive processing introduced error. 8-). In any case, I still would like an option to turn on the processing in the card, and let me assume that my hardware is monolithic, my card supports checksum offloading, and if I have problems with corruption between my ethernet card and my CPU, I have really, reall bad problems because the CPU and the etherent interface are sitting on the same silicon die which they were fabricated to share. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 1:51:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id DE7FC37B406 for ; Fri, 8 Jun 2001 01:51:10 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 30362 invoked by uid 1000); 8 Jun 2001 08:49:57 -0000 Date: Fri, 8 Jun 2001 11:49:57 +0300 From: Peter Pentchev To: John Baldwin Cc: hackers@FreeBSD.org Subject: Re: free() and const warnings Message-ID: <20010608114957.C19938@ringworld.oblivion.bg> Mail-Followup-To: John Baldwin , hackers@FreeBSD.org References: <20010607195634.I724@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Thu, Jun 07, 2001 at 10:20:51AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 07, 2001 at 10:20:51AM -0700, John Baldwin wrote: > > On 07-Jun-01 Peter Pentchev wrote: > > On Thu, Jun 07, 2001 at 07:07:22PM +0300, Peter Pentchev wrote: > >> Hi, > >> > >> Is free((void *) (size_t) ptr) the only way to free a const whatever *ptr > >> with WARNS=2? (or more specifically, with -Wcast-qual) > > > > Uhm. OK. So size_t may not be enough to hold a pointer. What is it then - > > caddr_t? > > uintptr_t for data pointers. In theory I think code pointers may not fit in a > uintptr_t. > > free((void *)(uintptr_t)ptr) should work. > > Of course, this begs the question of why you are free'ing a const. :) OK, here's a scenario: struct validation_fun { const char *name; valfun *fun; int dyn; }; This is a structure for a set of validation functions, referenced by name from another type of object. There are some predefined functions, present in the code at compile-time, and hardcoded in an array, with names given as "strings". Thus, the 'const'. However, some of the functions may be defined at runtime, with both name and code sent by a server. In that case, the name is a dynamically allocated char *, which needs to be freed upon cleanup. So I have: [cleanup function] ... if (val->dyn) free(val->name); Any suggestions on how to improve the design to avoid this, if possible, would be greatly welcome. G'luck, Peter -- I am the meaning of this sentence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 1:53:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 4193B37B406 for ; Fri, 8 Jun 2001 01:53:36 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.138.245.Dial1.SanJose1.Level3.net [209.245.138.245]) by snipe.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA14095; Fri, 8 Jun 2001 01:53:32 -0700 (PDT) Message-ID: <3B2092A9.67B58DA6@mindspring.com> Date: Fri, 08 Jun 2001 01:54:01 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Cejka Rudolf Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: [Patch?] signal(SIGCHLD, SIG_IGN) is against SUSv2 References: <20010607143050.A13932@dcse.fee.vutbr.cz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Cejka Rudolf wrote: > > There is following paragraph in SUSv2: > > If a process sets the action for the SIGCHLD signal to SIG_IGN, > the behaviour is unspecified, except as specified below. If the > action for the SIGCHLD signal is set to SIG_IGN, child processes > of the calling processes will not be transformed into zombie > processes when they terminate. If the calling process subsequently > waits for its children, and the process has no unwaited for children > that were transformed into zombie processes, it will block until all > of its children terminate, and wait(), wait3(), waitid() and waitpid() > will fail and set errno to [ECHILD]. ... > > However, if I use "signal(SIGCHLD, SIG_IGN)", zombies are still > created in FreeBSD, which is against SUSv2. Look at the sigaction() man page. There is a POSIX way to do what you want, using the sa_flags bits. If you hack up signal() to do this, it should be done by noting the SIG_IGN and the fact you are using the historical compatability signal() wrapper to the POSIX interface, and just set the sa_flags bit to do the job. I'm pretty sure the "wait" and other behaviour is also documented on that page, in the context of the sa_flags bit. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 2: 5:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id B30AC37B401 for ; Fri, 8 Jun 2001 02:05:23 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.138.245.Dial1.SanJose1.Level3.net [209.245.138.245]) by snipe.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id CAA01540; Fri, 8 Jun 2001 02:05:14 -0700 (PDT) Message-ID: <3B209567.1AE09631@mindspring.com> Date: Fri, 08 Jun 2001 02:05:43 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ian Dowse Cc: Graham Barr , Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: read(2) and ETIMEDOUT References: <200106072116.aa63698@salmon.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ian Dowse wrote: > > In message <20010607201846.E50444@pobox.com>, Graham Barr writes: > > >Also why does this happen only every few hours ? There is a lot of > >data going through these connections maybe the timer for SO_RCVTIMEO > >is not being reset. > > > >But then we have another server, with a similar number of clients and > >data through put, but it does not suffer from this problem. > > I suspect that the server seeing this problem has a client that > occasionally disappears from the network, or for whatever reason > fails to respond to any packets for a long time (something like 5 > or 10 minutes). I've seen blocking TCP writes return ETIMEDOUT when > the network between the client and the server goes down. In the > non-blocking case I think the following can happen: I believe the proxy ARP normally sent on an interface coming up can have this effect in the case a client goes down, and someone else gets their DHCP lease. You don't often see this on FreeBSD clients after 4.1, since the gratuitous proxy ARP became broken around then (if you change your IP address, it won't send the ARP unless you down the interface first and bring it back up, and it caches bad clone routes, too, just to make your life miserable). Probably your lease expiration times are set too low. This is usually the case in networks where people have transient connections for things like mobile users, and have exhaused their IP address space, and are trying to conserve it by using much shorter leases. A good, real fix for this is to have incredibly long lease lifetimes (basically, the DHCP server hands out the lease, and if the computer comes back days later, it gets the same lease). For this to work, you are probably going to have to make the local DHCP server give out 10.x addresses, and then NAT the 10.x net for real Internet connectivity. Alternately, it could be something completely different. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 2:17:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id 686BD37B401 for ; Fri, 8 Jun 2001 02:17:37 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.138.245.Dial1.SanJose1.Level3.net [209.245.138.245]) by hawk.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id CAA11862; Fri, 8 Jun 2001 02:17:29 -0700 (PDT) Message-ID: <3B209846.152DCFE7@mindspring.com> Date: Fri, 08 Jun 2001 02:17:58 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dave Hayes Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Why does fsck try to fsck a CDROM? References: <200106080209.TAA08276@hokkshideh.jetcafe.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dave Hayes wrote: > > David O'Brien -Hackers writes: > > You mentioned though that your CDROM is /. How about posting the real > > /etc/fstab from your root partition for us to have a look at? > > There is none. No default fstab exists. There is no Dana, only Zuul... I think that root gets fsck'ed in the rc files, even if there is no /etc/fstab, on the theory that that might be one of the reasons fsck needs to be run. Fsck normally runs on root when it is mounted r/o, and root gets mounted r/w only after it passes. The question is whether you can distinguish between a r/o device vs. a r/o mount of a r/w device... that is what fsck would have to do to decide to skip the fsck entirely for a cdrom. ...on the other hand, you could have burnt a dirty FS on the CDROM, in which case, it should check it and refuse to boot until you "fix" the errors by running fsck manually (quite the trick with the hole in it)... 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 3:15:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 2D40137B403 for ; Fri, 8 Jun 2001 03:15:44 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Jun 2001 11:15:43 +0100 (BST) To: tlambert2@mindspring.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: UFS large directory performance In-Reply-To: Your message of "Thu, 07 Jun 2001 23:52:50 PDT." <3B207642.A7C7E7C@mindspring.com> Date: Fri, 08 Jun 2001 11:15:42 +0100 From: Ian Dowse Message-ID: <200106081115.aa43142@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3B207642.A7C7E7C@mindspring.com>, Terry Lambert writes: > >Use a chain allocator. I would suggest using the zone >allocator, but it has some fundamental problems that I >don't think are really resolvable without a rewrite. Heh, maybe, but I'm not sure I want to write a new allocator for this :-) Based on Matt's suggestions, I implemented the 2-level approach. It currently uses 256 slots per second-level block; these 1k blocks are allocated using zalloc(). The variable-length first-level arrays are still allocated with malloc, but these don't grow to more than a few kb in size unless the directories are enormous. There's now a simple LRU list of dirhash structures that have memory attached, and a new function ufsdirhash_recycle() that will free up memory when the sysctl limit is reached. Adding this required some locking, but the problematic inode locking is avoided by leaving the dirhash structure attached to the inode when its hash array is freed. An updated patch is available at http://www.maths.tcd.ie/~iedowse/FreeBSD/dirhash.diff3 I haven't had a chance to do more than a minimal amount of testing, so there may be many issues remaining. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 3:53:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fjord.dignus.com (sdsl-66-80-58-206.dsl.lax.megapath.net [66.80.58.206]) by hub.freebsd.org (Postfix) with ESMTP id 71C2137B407; Fri, 8 Jun 2001 03:53:32 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by fjord.dignus.com (8.11.1/8.11.1) with ESMTP id f58AsTf99215; Fri, 8 Jun 2001 06:54:29 -0400 (EDT) (envelope-from rivers@dignus.com) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id GAA49069; Fri, 8 Jun 2001 06:55:50 -0400 (EDT) Date: Fri, 8 Jun 2001 06:55:50 -0400 (EDT) From: Thomas David Rivers Message-Id: <200106081055.GAA49069@lakes.dignus.com> To: jhb@FreeBSD.ORG, roam@orbitel.bg Subject: Re: free() and const warnings Cc: hackers@FreeBSD.ORG In-Reply-To: <20010608114957.C19938@ringworld.oblivion.bg> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Pentchev wrote: > > On Thu, Jun 07, 2001 at 10:20:51AM -0700, John Baldwin wrote: > > > > On 07-Jun-01 Peter Pentchev wrote: > > > On Thu, Jun 07, 2001 at 07:07:22PM +0300, Peter Pentchev wrote: > > >> Hi, > > >> > > >> Is free((void *) (size_t) ptr) the only way to free a const whatever *ptr > > >> with WARNS=2? (or more specifically, with -Wcast-qual) > > > > > > Uhm. OK. So size_t may not be enough to hold a pointer. What is it then - > > > caddr_t? > > > > uintptr_t for data pointers. In theory I think code pointers may not fit in a > > uintptr_t. > > > > free((void *)(uintptr_t)ptr) should work. > > > > Of course, this begs the question of why you are free'ing a const. :) > > OK, here's a scenario: > > struct validation_fun { > const char *name; > valfun *fun; > int dyn; > }; > > This is a structure for a set of validation functions, referenced by > name from another type of object. There are some predefined functions, > present in the code at compile-time, and hardcoded in an array, with > names given as "strings". Thus, the 'const'. > > However, some of the functions may be defined at runtime, with both > name and code sent by a server. In that case, the name is a dynamically > allocated char *, which needs to be freed upon cleanup. So I have: > > [cleanup function] > ... > if (val->dyn) > free(val->name); > > Any suggestions on how to improve the design to avoid this, if possible, > would be greatly welcome. > > G'luck, > Peter Since some strings are non-constant (the are allocated) - I believe the `const' qualifier in the structure declaration is incorrect. What happens if you simply don't have it in the structure declaration? - Dave Rivers - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 4:47:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 1554C37B405 for ; Fri, 8 Jun 2001 04:47:33 -0700 (PDT) (envelope-from rasputin@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #6) id 158Kjk-000Pvg-00 for hackers@freebsd.org; Fri, 8 Jun 2001 12:47:32 +0100 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.11.3/8.11.1) id f58BlVk70974 for hackers@freebsd.org; Fri, 8 Jun 2001 12:47:31 +0100 (BST) (envelope-from rasputin) Date: Fri, 8 Jun 2001 12:47:31 +0100 From: Rasputin To: hackers@freebsd.org Subject: problem with systm.h trying to call resettodr() Message-ID: <20010608124731.A70666@dogma.freebsd-uk.eu.org> Reply-To: Rasputin Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm playing with resettodr(9), to set the BIOS clock from the system time.. When I try to compile the following snippet, [rasputin@dogma rasputin]$ cat b0rken.c #include #include #include int main(void){ resettodr(); return(0); } I get warning about syntax errors in systm.h: [rasputin@dogma rasputin]$ gcc b0rken.c In file included from b0rken.c:3: /usr/include/sys/systm.h:333: syntax error before `int' /usr/include/sys/systm.h:334: syntax error before `int' /usr/include/sys/systm.h:335: syntax error before `(' (System is STABLE/RELENG_4 freshly cvsupped a few days ago, although /usr/src/sys/sys/systm.h doesn't seem to have changed in STABLE for four months. Any ideas? I know I'm not exactly '3l337' but I'd say that header file was screwed. Or am I missing some wierd ass compiler option? Thanks. -- What you don't know can hurt you, only you won't know it. Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 4:52:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id B394C37B407 for ; Fri, 8 Jun 2001 04:52:25 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (#6@localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.3/8.11.3) with ESMTP id f58BqNI30908; Fri, 8 Jun 2001 07:52:23 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200106081152.f58BqNI30908@whizzo.transsys.com> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Rasputin Cc: hackers@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: problem with systm.h trying to call resettodr() References: <20010608124731.A70666@dogma.freebsd-uk.eu.org> In-reply-to: Your message of "Fri, 08 Jun 2001 12:47:31 BST." <20010608124731.A70666@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Jun 2001 07:52:23 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I didn't think resettodr(9) was a system call exposed to user program, but instead a function available to be called from kernel code. Thus, the section 9 manual page. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 5:17:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 686A837B403 for ; Fri, 8 Jun 2001 05:17:35 -0700 (PDT) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id OAA63008; Fri, 8 Jun 2001 14:17:37 +0200 (CEST) (envelope-from assar) To: Garance A Drosihn Cc: hackers@FreeBSD.ORG Subject: Re: 'make clean' vs automake vs /bin/sh, which to fix? References: From: Assar Westerlund Date: 08 Jun 2001 14:17:37 +0200 In-Reply-To: Garance A Drosihn's message of "Mon, 28 May 2001 06:00:38 -0400" Message-ID: <5lofrztbby.fsf@assaris.sics.se> Lines: 14 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Garance A Drosihn writes: > So, we could fix this by: > 1) changing /bin/sh This you have already done and I think it's ok. > 2) changing make not to call /bin/sh with -e > 3) changing 'automake' to include a "true;" statement > in that 'for' loop (or some other trick) when > spitting out the target for things like clean-recursive I believe this has also been fixed in more modern automake. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 5:24:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 0419637B403 for ; Fri, 8 Jun 2001 05:24:22 -0700 (PDT) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id OAA63015; Fri, 8 Jun 2001 14:24:23 +0200 (CEST) (envelope-from assar) To: tlambert2@mindspring.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How to disable software TCP checksumming? References: <20010529144114.I19771@luke.immure.com> <20010529221107.C49875@skriver.dk> <20010529155212.M19771@luke.immure.com> <20010530045200.A1031@hades.hell.gr> <20010529235215.A60177@luke.immure.com> <20010530085155.B24096@Odin.AC.HMC.Edu> <200105310204.f4V248n15260@whizzo.transsys.com> <200106070549.WAA06248@windsor.research.att.com> <3B208F11.87722148@mindspring.com> From: Assar Westerlund Date: 08 Jun 2001 14:24:23 +0200 In-Reply-To: Terry Lambert's message of "Fri, 08 Jun 2001 01:38:41 -0700" Message-ID: <5lk82ntb0o.fsf@assaris.sics.se> Lines: 7 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert writes: > This all came from IP headers being 14 bytes long, instead > of 16. Hu? An IPv4 header (not including options) is 20 bytes long. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 5:33:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id C7F9F37B403 for ; Fri, 8 Jun 2001 05:33:41 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 7532 invoked by uid 1000); 8 Jun 2001 12:32:25 -0000 Date: Fri, 8 Jun 2001 15:32:25 +0300 From: Peter Pentchev To: Rasputin Cc: hackers@freebsd.org Subject: Re: problem with systm.h trying to call resettodr() Message-ID: <20010608153225.I19938@ringworld.oblivion.bg> Mail-Followup-To: Rasputin , hackers@freebsd.org References: <20010608124731.A70666@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010608124731.A70666@dogma.freebsd-uk.eu.org>; from rara.rasputin@virgin.net on Fri, Jun 08, 2001 at 12:47:31PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 08, 2001 at 12:47:31PM +0100, Rasputin wrote: > I'm playing with resettodr(9), to set the BIOS clock from the system time.. > > When I try to compile the following snippet, > > [rasputin@dogma rasputin]$ cat b0rken.c > #include > #include > #include > > int main(void){ > resettodr(); > return(0); > } > > I get warning about syntax errors in systm.h: > > [rasputin@dogma rasputin]$ gcc b0rken.c > In file included from b0rken.c:3: > /usr/include/sys/systm.h:333: syntax error before `int' > /usr/include/sys/systm.h:334: syntax error before `int' > /usr/include/sys/systm.h:335: syntax error before `(' > > (System is STABLE/RELENG_4 freshly cvsupped a few days ago, although > /usr/src/sys/sys/systm.h doesn't seem to have changed in STABLE > for four months. > > Any ideas? I know I'm not exactly '3l337' but I'd say that header file > was screwed. Or am I missing some wierd ass compiler option? As others pointed out, resettodr(9) is a kernel-space function. Section 9 of the manual is for those - see the intro(9) manual page with man 9 intro (just man intro would probably show you intro(1)). G'luck, Peter -- If I had finished this sentence, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 5:35:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 7416637B401; Fri, 8 Jun 2001 05:35:48 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f58CZii92512; Fri, 8 Jun 2001 15:35:44 +0300 (EEST) (envelope-from ru) Date: Fri, 8 Jun 2001 15:35:44 +0300 From: Ruslan Ermilov To: Assar Westerlund Cc: tlambert2@mindspring.com, freebsd-hackers@FreeBSD.ORG Subject: Re: How to disable software TCP checksumming? Message-ID: <20010608153544.C87737@sunbay.com> Mail-Followup-To: Assar Westerlund , tlambert2@mindspring.com, freebsd-hackers@FreeBSD.ORG References: <20010529144114.I19771@luke.immure.com> <20010529221107.C49875@skriver.dk> <20010529155212.M19771@luke.immure.com> <20010530045200.A1031@hades.hell.gr> <20010529235215.A60177@luke.immure.com> <20010530085155.B24096@Odin.AC.HMC.Edu> <200105310204.f4V248n15260@whizzo.transsys.com> <200106070549.WAA06248@windsor.research.att.com> <3B208F11.87722148@mindspring.com> <5lk82ntb0o.fsf@assaris.sics.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5lk82ntb0o.fsf@assaris.sics.se>; from assar@FreeBSD.ORG on Fri, Jun 08, 2001 at 02:24:23PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 08, 2001 at 02:24:23PM +0200, Assar Westerlund wrote: > Terry Lambert writes: > > This all came from IP headers being 14 bytes long, instead > > of 16. > > Hu? An IPv4 header (not including options) is 20 bytes long. > Terry meant the length of an IPv4 header up to but not including the checksum field. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 5:37:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cartman.techsupport.co.uk (cabletel1.cableol.net [194.168.3.4]) by hub.freebsd.org (Postfix) with ESMTP id 1D2FD37B405 for ; Fri, 8 Jun 2001 05:37:09 -0700 (PDT) (envelope-from ceri@techsupport.co.uk) Received: from ceri by cartman.techsupport.co.uk with local (Exim 3.22 #2) id 158LXt-0004An-00; Fri, 08 Jun 2001 13:39:21 +0100 Date: Fri, 8 Jun 2001 13:39:21 +0100 From: Ceri To: Rasputin Cc: hackers@freebsd.org Subject: Re: problem with systm.h trying to call resettodr() Message-ID: <20010608133921.A15179@cartman.techsupport.co.uk> References: <20010608124731.A70666@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010608124731.A70666@dogma.freebsd-uk.eu.org>; from rara.rasputin@virgin.net on Fri, Jun 08, 2001 at 12:47:31PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 08, 2001 at 12:47:31PM +0100, Rasputin said: > I'm playing with resettodr(9), to set the BIOS clock from the system time.. > > I get warning about syntax errors in systm.h: > > [rasputin@dogma rasputin]$ gcc b0rken.c > In file included from b0rken.c:3: > /usr/include/sys/systm.h:333: syntax error before `int' > /usr/include/sys/systm.h:334: syntax error before `int' > /usr/include/sys/systm.h:335: syntax error before `(' I been getting the exact same thing, so it's definitely not local to you. Ceri -- Your local RFC Nazi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 5:42:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 89F9137B401; Fri, 8 Jun 2001 05:42:44 -0700 (PDT) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id OAA63084; Fri, 8 Jun 2001 14:42:47 +0200 (CEST) (envelope-from assar) To: Ruslan Ermilov Cc: tlambert2@mindspring.com, freebsd-hackers@FreeBSD.ORG Subject: Re: How to disable software TCP checksumming? References: <20010529144114.I19771@luke.immure.com> <20010529221107.C49875@skriver.dk> <20010529155212.M19771@luke.immure.com> <20010530045200.A1031@hades.hell.gr> <20010529235215.A60177@luke.immure.com> <20010530085155.B24096@Odin.AC.HMC.Edu> <200105310204.f4V248n15260@whizzo.transsys.com> <200106070549.WAA06248@windsor.research.att.com> <3B208F11.87722148@mindspring.com> <5lk82ntb0o.fsf@assaris.sics.se> <20010608153544.C87737@sunbay.com> From: Assar Westerlund Date: 08 Jun 2001 14:42:46 +0200 In-Reply-To: Ruslan Ermilov's message of "Fri, 8 Jun 2001 15:35:44 +0300" Message-ID: <5lofrzrvll.fsf@assaris.sics.se> Lines: 33 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ruslan Ermilov writes: > On Fri, Jun 08, 2001 at 02:24:23PM +0200, Assar Westerlund wrote: > > Terry Lambert writes: > > > This all came from IP headers being 14 bytes long, instead > > > of 16. > > > > Hu? An IPv4 header (not including options) is 20 bytes long. > > > Terry meant the length of an IPv4 header up to but not including > the checksum field. I'm confused. From rfc791: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Version| IHL |Type of Service| Total Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Identification |Flags| Fragment Offset | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Time to Live | Protocol | Header Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Options | Padding | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Which to me says that an IP header up to but not including the checksum is 10 bytes? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 5:44:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id A839137B405 for ; Fri, 8 Jun 2001 05:44:05 -0700 (PDT) (envelope-from roam@ringworld.nanolink.com) Received: (qmail 7693 invoked by uid 1000); 8 Jun 2001 12:42:49 -0000 Date: Fri, 8 Jun 2001 15:42:49 +0300 From: Peter Pentchev To: Thomas David Rivers Cc: jhb@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: free() and const warnings Message-ID: <20010608154249.A7671@ringworld.oblivion.bg> Mail-Followup-To: Thomas David Rivers , jhb@FreeBSD.ORG, hackers@FreeBSD.ORG References: <20010608114957.C19938@ringworld.oblivion.bg> <200106081055.GAA49069@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106081055.GAA49069@lakes.dignus.com>; from rivers@dignus.com on Fri, Jun 08, 2001 at 06:55:50AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 08, 2001 at 06:55:50AM -0400, Thomas David Rivers wrote: > Peter Pentchev wrote: > > > > On Thu, Jun 07, 2001 at 10:20:51AM -0700, John Baldwin wrote: > > > > > > On 07-Jun-01 Peter Pentchev wrote: > > > > On Thu, Jun 07, 2001 at 07:07:22PM +0300, Peter Pentchev wrote: > > > >> Hi, > > > >> > > > >> Is free((void *) (size_t) ptr) the only way to free a const whatever *ptr > > > >> with WARNS=2? (or more specifically, with -Wcast-qual) > > > > > > > > Uhm. OK. So size_t may not be enough to hold a pointer. What is it then - > > > > caddr_t? > > > > > > uintptr_t for data pointers. In theory I think code pointers may not fit in a > > > uintptr_t. > > > > > > free((void *)(uintptr_t)ptr) should work. > > > > > > Of course, this begs the question of why you are free'ing a const. :) > > > > OK, here's a scenario: > > > > struct validation_fun { > > const char *name; > > valfun *fun; > > int dyn; > > }; > > > > This is a structure for a set of validation functions, referenced by > > name from another type of object. There are some predefined functions, > > present in the code at compile-time, and hardcoded in an array, with > > names given as "strings". Thus, the 'const'. > > > > However, some of the functions may be defined at runtime, with both > > name and code sent by a server. In that case, the name is a dynamically > > allocated char *, which needs to be freed upon cleanup. So I have: > > > > [cleanup function] > > ... > > if (val->dyn) > > free(val->name); > > > > Any suggestions on how to improve the design to avoid this, if possible, > > would be greatly welcome. > > > > G'luck, > > Peter > > Since some strings are non-constant (the are allocated) - I believe > the `const' qualifier in the structure declaration is incorrect. > > What happens if you simply don't have it in the structure declaration? GCC complains when I try to initialize the structure with something like: struct validation_fun val_init[] = { {"init", valfun_init, 0} }; This can be avoided by: struct validation_fun val_init[] = { {(char *) (uintptr_t) "init", valfun_init, 0} }; ..but as a matter of fact, static, pre-initialized valfun structs are the rule rather than the exception in this program, so having this syntax for all of them seems.. well.. ugly :) G'luck, Peter -- You have, of course, just begun reading the sentence that you have just finished reading. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 5:49:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id DCEBA37B403 for ; Fri, 8 Jun 2001 05:49:13 -0700 (PDT) (envelope-from rasputin@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #6) id 158LhQ-00037B-00; Fri, 8 Jun 2001 13:49:12 +0100 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.11.3/8.11.1) id f58CnCK72190; Fri, 8 Jun 2001 13:49:12 +0100 (BST) (envelope-from rasputin) Date: Fri, 8 Jun 2001 13:49:12 +0100 From: Rasputin To: Peter Pentchev Cc: freebsd-hackers@freebsd.org Subject: Re: problem with systm.h trying to call resettodr() Message-ID: <20010608134912.A71963@dogma.freebsd-uk.eu.org> Reply-To: Rasputin References: <20010608124731.A70666@dogma.freebsd-uk.eu.org> <20010608153225.I19938@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010608153225.I19938@ringworld.oblivion.bg>; from roam@orbitel.bg on Fri, Jun 08, 2001 at 03:32:25PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Peter Pentchev [010608 13:35]: > On Fri, Jun 08, 2001 at 12:47:31PM +0100, Rasputin wrote: > > I'm playing with resettodr(9), to set the BIOS clock from the system time.. > As others pointed out, resettodr(9) is a kernel-space function. > Section 9 of the manual is for those - see the intro(9) manual page > with man 9 intro (just man intro would probably show you intro(1)). Thanks, I'd already read intro(9), but it doesn't explain how to *use* kernel-space functions. I suppose the manpage would be huge then, though.... maybe book size? Is this another 'get that daemon book, you tight-fisted...' situation? So the syntax errors in systm.h are related to what- Missing compiler flags (-DKERNEL?), or missing headers? I *know* you guys all know, but where did you get this knowledge from? Is there a secret BSD monastery you all hang out at, or is there a secret switch you give man that lets you into the *real* details ? Thanks. I'll bring water wings next time.... -- "These are the propulsion systems used by NASA for the moonshots," said Tom apologetically. Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 5:49:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fjord.dignus.com (sdsl-66-80-58-206.dsl.lax.megapath.net [66.80.58.206]) by hub.freebsd.org (Postfix) with ESMTP id CDE8E37B408; Fri, 8 Jun 2001 05:49:36 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by fjord.dignus.com (8.11.1/8.11.1) with ESMTP id f58CoXf99446; Fri, 8 Jun 2001 08:50:33 -0400 (EDT) (envelope-from rivers@dignus.com) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id IAA49852; Fri, 8 Jun 2001 08:51:54 -0400 (EDT) Date: Fri, 8 Jun 2001 08:51:54 -0400 (EDT) From: Thomas David Rivers Message-Id: <200106081251.IAA49852@lakes.dignus.com> To: rivers@dignus.com, roam@orbitel.bg Subject: Re: free() and const warnings Cc: hackers@FreeBSD.ORG, jhb@FreeBSD.ORG In-Reply-To: <20010608154249.A7671@ringworld.oblivion.bg> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > GCC complains when I try to initialize the structure with something like: > > struct validation_fun val_init[] = { > {"init", valfun_init, 0} > }; > > This can be avoided by: > > struct validation_fun val_init[] = { > {(char *) (uintptr_t) "init", valfun_init, 0} > }; > > ..but as a matter of fact, static, pre-initialized valfun structs are > the rule rather than the exception in this program, so having this > syntax for all of them seems.. well.. ugly :) > Ah.. I see.. (I don't think you need (uintptr_t) - you can cast a (const char *) to a (char *) without having to go "through" that - I believe.) Is this C, or C++.. there are some differences in the type of a constant character string between the two... But - basically, what you are trying to describe is a field which is sometimes 'const' and othertimes isn't... which doesn't make sense in the context of the C standard... you'll need a cast for the initialization, or some other approach besides static initialization I believe... (or, just "live" with the warning... which isn't pleasant at all.) - Dave R. - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 5:54:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 9C19337B403 for ; Fri, 8 Jun 2001 05:54:29 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 7847 invoked by uid 1000); 8 Jun 2001 12:53:14 -0000 Date: Fri, 8 Jun 2001 15:53:13 +0300 From: Peter Pentchev To: Rasputin Cc: freebsd-hackers@freebsd.org Subject: Re: problem with systm.h trying to call resettodr() Message-ID: <20010608155313.C7671@ringworld.oblivion.bg> Mail-Followup-To: Rasputin , freebsd-hackers@freebsd.org References: <20010608124731.A70666@dogma.freebsd-uk.eu.org> <20010608153225.I19938@ringworld.oblivion.bg> <20010608134912.A71963@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010608134912.A71963@dogma.freebsd-uk.eu.org>; from rara.rasputin@virgin.net on Fri, Jun 08, 2001 at 01:49:12PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 08, 2001 at 01:49:12PM +0100, Rasputin wrote: > * Peter Pentchev [010608 13:35]: > > On Fri, Jun 08, 2001 at 12:47:31PM +0100, Rasputin wrote: > > > I'm playing with resettodr(9), to set the BIOS clock from the system time.. > > > As others pointed out, resettodr(9) is a kernel-space function. > > Section 9 of the manual is for those - see the intro(9) manual page > > with man 9 intro (just man intro would probably show you intro(1)). > > Thanks, I'd already read intro(9), but it doesn't explain how to *use* > kernel-space functions. You can only use kernel-space functions in kernel code, that is, writing a kernel module, or writing a piece of code that is to be compiled along with the rest in src/sys. If you're doing that, look at some kernel source files to see which header files need to be included. If you're not doing that, you cannot use the functions documented in section 9. G'luck, Peter -- This sentence claims to be an Epimenides paradox, but it is lying. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 5:56:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 6007637B405 for ; Fri, 8 Jun 2001 05:56:43 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 7898 invoked by uid 1000); 8 Jun 2001 12:55:28 -0000 Date: Fri, 8 Jun 2001 15:55:28 +0300 From: Peter Pentchev To: Thomas David Rivers Cc: hackers@FreeBSD.ORG, jhb@FreeBSD.ORG Subject: Re: free() and const warnings Message-ID: <20010608155527.D7671@ringworld.oblivion.bg> Mail-Followup-To: Thomas David Rivers , hackers@FreeBSD.ORG, jhb@FreeBSD.ORG References: <20010608154249.A7671@ringworld.oblivion.bg> <200106081251.IAA49852@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106081251.IAA49852@lakes.dignus.com>; from rivers@dignus.com on Fri, Jun 08, 2001 at 08:51:54AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 08, 2001 at 08:51:54AM -0400, Thomas David Rivers wrote: > > > > GCC complains when I try to initialize the structure with something like: > > > > struct validation_fun val_init[] = { > > {"init", valfun_init, 0} > > }; > > > > This can be avoided by: > > > > struct validation_fun val_init[] = { > > {(char *) (uintptr_t) "init", valfun_init, 0} > > }; > > > > ..but as a matter of fact, static, pre-initialized valfun structs are > > the rule rather than the exception in this program, so having this > > syntax for all of them seems.. well.. ugly :) > > > > Ah.. I see.. > > (I don't think you need (uintptr_t) - you can cast a (const char *) > to a (char *) without having to go "through" that - I believe.) Errrr.. this was the whole point of this thread. I *can't* cast a (const char *) to a (char *) when using the -Wcast-qual gcc flag - the -Wcast-qual flag produces exactly this type of warnings, to make sure you don't treat const * pointers as normal pointers, and pass them to functions that do stupid things like modify them or free them :) > Is this C, or C++.. there are some differences in the type of > a constant character string between the two... > > But - basically, what you are trying to describe is a field which > is sometimes 'const' and othertimes isn't... which doesn't make > sense in the context of the C standard... you'll need a cast > for the initialization, or some other approach besides static > initialization I believe... (or, just "live" with the warning... > which isn't pleasant at all.) Well, I can't live with the warning with -Werror ;) So I guess I'll live with casting in free() :) G'luck, Peter -- If wishes were fishes, the antecedent of this conditional would be true. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 5:59:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fjord.dignus.com (sdsl-66-80-58-206.dsl.lax.megapath.net [66.80.58.206]) by hub.freebsd.org (Postfix) with ESMTP id 2657137B403; Fri, 8 Jun 2001 05:59:12 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by fjord.dignus.com (8.11.1/8.11.1) with ESMTP id f58D09f99490; Fri, 8 Jun 2001 09:00:09 -0400 (EDT) (envelope-from rivers@dignus.com) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id JAA50018; Fri, 8 Jun 2001 09:01:29 -0400 (EDT) Date: Fri, 8 Jun 2001 09:01:29 -0400 (EDT) From: Thomas David Rivers Message-Id: <200106081301.JAA50018@lakes.dignus.com> To: rivers@dignus.com, roam@orbitel.bg Subject: Re: free() and const warnings Cc: hackers@FreeBSD.ORG, jhb@FreeBSD.ORG In-Reply-To: <20010608155527.D7671@ringworld.oblivion.bg> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > On Fri, Jun 08, 2001 at 08:51:54AM -0400, Thomas David Rivers wrote: > > > > > > GCC complains when I try to initialize the structure with something like: > > > > > > struct validation_fun val_init[] = { > > > {"init", valfun_init, 0} > > > }; > > > > > > This can be avoided by: > > > > > > struct validation_fun val_init[] = { > > > {(char *) (uintptr_t) "init", valfun_init, 0} > > > }; > > > > > > ..but as a matter of fact, static, pre-initialized valfun structs are > > > the rule rather than the exception in this program, so having this > > > syntax for all of them seems.. well.. ugly :) > > > > > > > Ah.. I see.. > > > > (I don't think you need (uintptr_t) - you can cast a (const char *) > > to a (char *) without having to go "through" that - I believe.) > > Errrr.. this was the whole point of this thread. I *can't* cast > a (const char *) to a (char *) when using the -Wcast-qual gcc flag - > the -Wcast-qual flag produces exactly this type of warnings, to make > sure you don't treat const * pointers as normal pointers, and pass them > to functions that do stupid things like modify them or free them :) Yes - I see now... sorry for being slow on the "uptake" :-) > > > Is this C, or C++.. there are some differences in the type of > > a constant character string between the two... > > > > But - basically, what you are trying to describe is a field which > > is sometimes 'const' and othertimes isn't... which doesn't make > > sense in the context of the C standard... you'll need a cast > > for the initialization, or some other approach besides static > > initialization I believe... (or, just "live" with the warning... > > which isn't pleasant at all.) > > Well, I can't live with the warning with -Werror ;) So I guess I'll > live with casting in free() :) It's not pretty either way... is it? - Dave R. - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 6: 3: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 2C28637B403; Fri, 8 Jun 2001 06:02:58 -0700 (PDT) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id PAA63231; Fri, 8 Jun 2001 15:02:56 +0200 (CEST) (envelope-from assar) To: Peter Pentchev Cc: Thomas David Rivers , jhb@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: free() and const warnings References: <20010608114957.C19938@ringworld.oblivion.bg> <200106081055.GAA49069@lakes.dignus.com> <20010608154249.A7671@ringworld.oblivion.bg> From: Assar Westerlund Date: 08 Jun 2001 15:02:56 +0200 In-Reply-To: Peter Pentchev's message of "Fri, 8 Jun 2001 15:42:49 +0300" Message-ID: <5ld78frunz.fsf@assaris.sics.se> Lines: 35 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Pentchev writes: > GCC complains when I try to initialize the structure with something like: > > struct validation_fun val_init[] = { > {"init", valfun_init, 0} > }; > > This can be avoided by: > > struct validation_fun val_init[] = { > {(char *) (uintptr_t) "init", valfun_init, 0} > }; > > ..but as a matter of fact, static, pre-initialized valfun structs are > the rule rather than the exception in this program, so having this > syntax for all of them seems.. well.. ugly :) What version of gcc is this? 2.96? All versions of 2.95.x that I've tried seems to eat the following program with: gcc -O -g -Werror -Wcast-qual -c foo.c /assar struct validation_fun { const char *name; void *fun; int dyn; }; struct validation_fun val_init[] = { {"init", 0, 0} }; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 6: 4:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 8C7BE37B406 for ; Fri, 8 Jun 2001 06:04:19 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 8146 invoked by uid 1000); 8 Jun 2001 13:03:04 -0000 Date: Fri, 8 Jun 2001 16:03:04 +0300 From: Peter Pentchev To: Assar Westerlund Cc: Thomas David Rivers , jhb@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: free() and const warnings Message-ID: <20010608160304.G7671@ringworld.oblivion.bg> Mail-Followup-To: Assar Westerlund , Thomas David Rivers , jhb@FreeBSD.ORG, hackers@FreeBSD.ORG References: <20010608114957.C19938@ringworld.oblivion.bg> <200106081055.GAA49069@lakes.dignus.com> <20010608154249.A7671@ringworld.oblivion.bg> <5ld78frunz.fsf@assaris.sics.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5ld78frunz.fsf@assaris.sics.se>; from assar@FreeBSD.ORG on Fri, Jun 08, 2001 at 03:02:56PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 08, 2001 at 03:02:56PM +0200, Assar Westerlund wrote: > Peter Pentchev writes: > > GCC complains when I try to initialize the structure with something like: > > > > struct validation_fun val_init[] = { > > {"init", valfun_init, 0} > > }; > > > > This can be avoided by: > > > > struct validation_fun val_init[] = { > > {(char *) (uintptr_t) "init", valfun_init, 0} > > }; > > > > ..but as a matter of fact, static, pre-initialized valfun structs are > > the rule rather than the exception in this program, so having this > > syntax for all of them seems.. well.. ugly :) > > What version of gcc is this? 2.96? > > All versions of 2.95.x that I've tried seems to eat the following > program with: > > gcc -O -g -Werror -Wcast-qual -c foo.c > > /assar > > struct validation_fun { > const char *name; > void *fun; > int dyn; > }; > > struct validation_fun val_init[] = { > {"init", 0, 0} > }; My explanation was a reply to a suggestion to remove the 'const' in the structure definition. G'luck, Peter -- If I had finished this sentence, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 6: 6:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 8B3E737B408 for ; Fri, 8 Jun 2001 06:06:33 -0700 (PDT) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id PAA63239; Fri, 8 Jun 2001 15:06:34 +0200 (CEST) (envelope-from assar) To: Cc: Subject: Re: New error - lost data? References: From: Assar Westerlund Date: 08 Jun 2001 15:06:34 +0200 In-Reply-To: "Deepak Jain"'s message of "Fri, 8 Jun 2001 01:29:50 -0400" Message-ID: <5l8zj3ruhx.fsf@assaris.sics.se> Lines: 15 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Deepak Jain" writes: > Others have seen this error (based on a Google search) but nothing recent > and nothing that conclusive. This is a very standard config that has been > stable for quite a while. The panic: malloc: lost data implies to me that > something is misbehaving with its memory allocations. > > Is this a hardware issue or an application problem? The kernel is 4.1 > RELEASE. The RAM is ECC. It should not be an application problem. It indicates that the memory pool administered by the kernel malloc is corrupt. Either it's a bug in the kernel or bad memory. Does it only happen on that particular machine with that particular memory? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 6: 9:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id EC21F37B407; Fri, 8 Jun 2001 06:09:50 -0700 (PDT) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id PAA63250; Fri, 8 Jun 2001 15:09:53 +0200 (CEST) (envelope-from assar) To: Peter Pentchev Cc: Thomas David Rivers , jhb@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: free() and const warnings References: <20010608114957.C19938@ringworld.oblivion.bg> <200106081055.GAA49069@lakes.dignus.com> <20010608154249.A7671@ringworld.oblivion.bg> <5ld78frunz.fsf@assaris.sics.se> <20010608160304.G7671@ringworld.oblivion.bg> From: Assar Westerlund Date: 08 Jun 2001 15:09:53 +0200 In-Reply-To: Peter Pentchev's message of "Fri, 8 Jun 2001 16:03:04 +0300" Message-ID: <5lsnhbqfry.fsf@assaris.sics.se> Lines: 20 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Pentchev writes: > My explanation was a reply to a suggestion to remove the 'const' in > the structure definition. My fault. The code that I should have shown was without the 'const'. With gcc 2.95.3 and 'gcc -O -g -Werror -Wall -W -Wcast-qual -c foo.c' I don't get any errors with the const-less program (below). I was wondering if this is something that has changed in recent gcc. /assar struct validation_fun { char *name; void *fun; int dyn; }; struct validation_fun val_init[] = { {"init", 0, 0} }; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 6:20:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 0769237B405 for ; Fri, 8 Jun 2001 06:20:33 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 8375 invoked by uid 1000); 8 Jun 2001 13:19:10 -0000 Date: Fri, 8 Jun 2001 16:19:10 +0300 From: Peter Pentchev To: Assar Westerlund Cc: Thomas David Rivers , jhb@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: free() and const warnings Message-ID: <20010608161909.H7671@ringworld.oblivion.bg> Mail-Followup-To: Assar Westerlund , Thomas David Rivers , jhb@FreeBSD.ORG, hackers@FreeBSD.ORG References: <20010608114957.C19938@ringworld.oblivion.bg> <200106081055.GAA49069@lakes.dignus.com> <20010608154249.A7671@ringworld.oblivion.bg> <5ld78frunz.fsf@assaris.sics.se> <20010608160304.G7671@ringworld.oblivion.bg> <5lsnhbqfry.fsf@assaris.sics.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5lsnhbqfry.fsf@assaris.sics.se>; from assar@FreeBSD.ORG on Fri, Jun 08, 2001 at 03:09:53PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 08, 2001 at 03:09:53PM +0200, Assar Westerlund wrote: > Peter Pentchev writes: > > My explanation was a reply to a suggestion to remove the 'const' in > > the structure definition. > > My fault. The code that I should have shown was without the 'const'. > With gcc 2.95.3 and 'gcc -O -g -Werror -Wall -W -Wcast-qual -c foo.c' > I don't get any errors with the const-less program (below). I was > wondering if this is something that has changed in recent gcc. Errrr d'oh, ok, my fault - it's not -Wcast-qual, it's -Wwrite-strings that causes the problem :) WARNS=2 in -current makes it go boom. G'luck, Peter -- If this sentence didn't exist, somebody would have invented it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 7:10: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.popsite.net (smtp.popsite.net [216.126.128.17]) by hub.freebsd.org (Postfix) with ESMTP id 3CF9637B405 for ; Fri, 8 Jun 2001 07:09:59 -0700 (PDT) (envelope-from bill@twwells.com) Received: from twwells.com (01-051.051.popsite.net [64.24.21.51]) by smtp.popsite.net (Postfix) with ESMTP id 4C29950899 for ; Fri, 8 Jun 2001 09:09:46 -0500 (CDT) Received: from bill by twwells.com with local (Exim 3.22 #1) id 158MxL-0004BT-00; Fri, 08 Jun 2001 10:09:43 -0400 Subject: Re: free() and const warnings To: roam@orbitel.bg (Peter Pentchev) Date: Fri, 8 Jun 2001 10:09:43 -0400 (EDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <20010608155527.D7671@ringworld.oblivion.bg> from "Peter Pentchev" at Jun 08, 2001 03:55:28 PM X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: "T. William Wells" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Errrr.. this was the whole point of this thread. I *can't* cast > a (const char *) to a (char *) when using the -Wcast-qual gcc flag - Not all -W options are equally useful and some are actively harmful. This is one of them. There are several situations where it is necessary to remove a qualifier (any code for strchr, e.g.). Adding nonportable hacks to your code to avoid a gcc error message is just plain bad coding. Perhaps gcc has a way to turn off warnings temporarily; I haven't checked lately. If not, roll your own. Define a comment like /*CASTOK*/, to stick on each line with such a cast, then filter the gcc output using a script that examines the source code for such comments and removes the bogus error messages. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 7:26:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 429B037B401; Fri, 8 Jun 2001 07:26:16 -0700 (PDT) (envelope-from julian@elischer.org) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id IAA73310; Fri, 8 Jun 2001 08:33:47 -0700 (PDT) Message-ID: <3B20DEA6.711EB17C@elischer.org> Date: Fri, 08 Jun 2001 07:18:14 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Assar Westerlund Cc: Ruslan Ermilov , tlambert2@mindspring.com, freebsd-hackers@FreeBSD.ORG Subject: Re: How to disable software TCP checksumming? References: <20010529144114.I19771@luke.immure.com> <20010529221107.C49875@skriver.dk> <20010529155212.M19771@luke.immure.com> <20010530045200.A1031@hades.hell.gr> <20010529235215.A60177@luke.immure.com> <20010530085155.B24096@Odin.AC.HMC.Edu> <200105310204.f4V248n15260@whizzo.transsys.com> <200106070549.WAA06248@windsor.research.att.com> <3B208F11.87722148@mindspring.com> <5lk82ntb0o.fsf@assaris.sics.se> <20010608153544.C87737@sunbay.com> <5lofrzrvll.fsf@assaris.sics.se> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Assar Westerlund wrote: > > Ruslan Ermilov writes: > > On Fri, Jun 08, 2001 at 02:24:23PM +0200, Assar Westerlund wrote: > > > Terry Lambert writes: > > > > This all came from IP headers being 14 bytes long, instead > > > > of 16. > > > > > > Hu? An IPv4 header (not including options) is 20 bytes long. > > > > > Terry meant the length of an IPv4 header up to but not including > > the checksum field. no he meant to say "ethernet header" -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 8:56:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gnome01.sovam.com (gnome01.sovam.com [194.67.1.179]) by hub.freebsd.org (Postfix) with ESMTP id A544B37B405 for ; Fri, 8 Jun 2001 08:56:21 -0700 (PDT) (envelope-from avn@any.ru) Received: from ts9-a53.dial.sovam.com ([195.239.70.53]:1542 "EHLO srv2.any" ident: "TIMEDOUT" whoson: "-unregistered-" smtp-auth: TLS-CIPHER: TLS-PEER: ) by gnome01.sovam.com with ESMTP id ; Fri, 8 Jun 2001 19:55:59 +0400 Received: from localhost (avn@localhost) by srv2.any (8.11.3/8.11.3) with ESMTP id f58FvLB16746; Fri, 8 Jun 2001 19:57:21 +0400 (MSD) (envelope-from avn@any.ru) Date: Fri, 8 Jun 2001 19:57:21 +0400 (MSD) From: "Alexey V. Neyman" X-X-Sender: To: Peter Pentchev Cc: Rasputin , Subject: Re: problem with systm.h trying to call resettodr() In-Reply-To: <20010608155313.C7671@ringworld.oblivion.bg> Message-ID: <20010608195523.X16723-100000@srv2.any> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 8 Jun 2001, Peter Pentchev wrote: >On Fri, Jun 08, 2001 at 01:49:12PM +0100, Rasputin wrote: >You can only use kernel-space functions in kernel code, that is, writing >a kernel module, or writing a piece of code that is to be compiled along >with the rest in src/sys. By the way, are there any underwater stones in linking userland programs against libkern with '-static -nostdlib' to gcc? Regards, Alexey. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 9: 8:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-r05.mx.aol.com (imo-r05.mx.aol.com [152.163.225.101]) by hub.freebsd.org (Postfix) with ESMTP id 18A4637B403 for ; Fri, 8 Jun 2001 09:08:45 -0700 (PDT) (envelope-from Bsdguru@aol.com) Received: from Bsdguru@aol.com by imo-r05.mx.aol.com (mail_out_v30.22.) id n.84.1717a060 (25313) for ; Fri, 8 Jun 2001 12:08:39 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <84.1717a060.28525287@aol.com> Date: Fri, 8 Jun 2001 12:08:39 EDT Subject: Re: How to disable software TCP checksumming? To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This thread is baffling. The bottom line is that you cant trust data coming into your machine, and you have to checksum it. The link level check only verifies that what was sent by the last forwarding point is the same as what you got, but in NO WAY implies that all of the data is valid. A link level checksum pass is a necessary, but not a sufficient condition for the data being acceptable. There are scads of reasons that it could be bad. Disabling checksumming is a kludge that you may chose to do, but its never the right thing to do. bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 9:41:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 0732C37B405 for ; Fri, 8 Jun 2001 09:41:36 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f58Geqr63121; Fri, 8 Jun 2001 11:40:52 -0500 (CDT) (envelope-from jlemon) Date: Fri, 8 Jun 2001 11:40:52 -0500 (CDT) From: Jonathan Lemon Message-Id: <200106081640.f58Geqr63121@prism.flugsvamp.com> To: Bsdguru@aol.com, hackers@freebsd.org Subject: Re: How to disable software TCP checksumming? X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article you write: >This thread is baffling. The bottom line is that you cant trust data coming >into your machine, and you have to checksum it. The link level check only >verifies that what was sent by the last forwarding point is the same as what >you got, but in NO WAY implies that all of the data is valid. A link level >checksum pass is a necessary, but not a sufficient condition for the data >being acceptable. There are scads of reasons that it could be bad. Disabling >checksumming is a kludge that you may chose to do, but its never the right >thing to do. I think there's some confusion here. There are two types of checksums: 1. CRC link-level checksum on the ethernet packet. 2. Upper layer checksums (TCP/IP) All hardware that I'm aware of automatically performs #1, I'm not sure if there is anything that will permit disabling this. Step 2 is usually known as the "end-to-end" checksum, and is traditionally performed by the host CPU. Depending on your view of what constitutes an "endpoint", these checksums may be performed by the network adapter itself. I believe that this is what the original meant by disabling software checksums, in the sense that his hardware would do this work. Dispensing with TCP/IP checksum altogether is a fairly bad idea, but I don't think that is what was being proposed here. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 10: 9:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from temphost.dragondata.com (temphost.dragondata.com [63.167.131.128]) by hub.freebsd.org (Postfix) with ESMTP id 365F737B403 for ; Fri, 8 Jun 2001 10:09:34 -0700 (PDT) (envelope-from toasty@temphost.dragondata.com) Received: (from toasty@localhost) by temphost.dragondata.com (8.9.3/8.9.3) id MAA42527; Fri, 8 Jun 2001 12:09:39 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <200106081709.MAA42527@temphost.dragondata.com> Subject: Access to symbol table(including dynamics) at runtime To: hackers@freebsd.org Date: Fri, 8 Jun 2001 12:09:39 -0500 (CDT) X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is there a simple way that I can lookup a symbol name(by address) during runtime? I know I can exec nm, look up for the address I need, and get local symbols, but it would be really nice if I could get addresses of functions in dynamic libraries as well. I know I could use ldd to get offsets of each .so and calculate from there, but I'm starting to think I'm reproducing work that was done somewhere else. If someone could point me at a man page to something that can do what I need, tell me of a library that does something similar, or tell me why this can't be done, i'd be very thankful. :) -- Kevin Day toasty@dragondata.com - kevin@stileproject.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 10:14: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 82D9D37B403 for ; Fri, 8 Jun 2001 10:13:53 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 52634 invoked by uid 1000); 8 Jun 2001 17:12:32 -0000 Date: Fri, 8 Jun 2001 20:12:32 +0300 From: Peter Pentchev To: Kevin Day Cc: hackers@freebsd.org Subject: Re: Access to symbol table(including dynamics) at runtime Message-ID: <20010608201232.G535@ringworld.oblivion.bg> Mail-Followup-To: Kevin Day , hackers@freebsd.org References: <200106081709.MAA42527@temphost.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106081709.MAA42527@temphost.dragondata.com>; from toasty@temphost.dragondata.com on Fri, Jun 08, 2001 at 12:09:39PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 08, 2001 at 12:09:39PM -0500, Kevin Day wrote: > > > Is there a simple way that I can lookup a symbol name(by address) during > runtime? > > I know I can exec nm, look up for the address I need, and get local > symbols, but it would be really nice if I could get addresses of functions > in dynamic libraries as well. I know I could use ldd to get offsets of each > .so and calculate from there, but I'm starting to think I'm reproducing work > that was done somewhere else. > > If someone could point me at a man page to something that can do what I > need, tell me of a library that does something similar, or tell me why this > can't be done, i'd be very thankful. :) OK, you asked for it, here's a minimalistic answer: dlopen(3) :) G'luck, Peter -- If wishes were fishes, the antecedent of this conditional would be true. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 10:14:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 0446437B407 for ; Fri, 8 Jun 2001 10:14:23 -0700 (PDT) (envelope-from fmela0@sm.socccd.cc.ca.us) Received: from sm.socccd.cc.ca.us (pool0572.cvx14-bradley.dialup.earthlink.net [209.179.40.62]) by albatross.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id KAA03946; Fri, 8 Jun 2001 10:14:09 -0700 (PDT) Message-ID: <3B21086C.A1A6FAED@sm.socccd.cc.ca.us> Date: Fri, 08 Jun 2001 10:16:28 -0700 From: Farooq Mela X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Kevin Day Cc: hackers@freebsd.org Subject: Re: Access to symbol table(including dynamics) at runtime References: <200106081709.MAA42527@temphost.dragondata.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kevin Day wrote: > > Is there a simple way that I can lookup a symbol name(by address) during > runtime? man dlopen. -- farooq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 10:16:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 33E7237B405 for ; Fri, 8 Jun 2001 10:16:24 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.11.3/8.11.3) id f58HGGv26529; Fri, 8 Jun 2001 12:16:16 -0500 (CDT) (envelope-from dan) Date: Fri, 8 Jun 2001 12:16:16 -0500 From: Dan Nelson To: Kevin Day Cc: hackers@FreeBSD.ORG Subject: Re: Access to symbol table(including dynamics) at runtime Message-ID: <20010608121616.A23647@dan.emsphone.com> References: <200106081709.MAA42527@temphost.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200106081709.MAA42527@temphost.dragondata.com> User-Agent: Mutt/1.3.19i X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Jun 08), Kevin Day said: > Is there a simple way that I can lookup a symbol name(by address) > during runtime? > > I know I can exec nm, look up for the address I need, and get local > symbols, but it would be really nice if I could get addresses of > functions in dynamic libraries as well. I know I could use ldd to get > offsets of each .so and calculate from there, but I'm starting to > think I'm reproducing work that was done somewhere else. > > If someone could point me at a man page to something that can do what > I need, tell me of a library that does something similar, or tell me > why this can't be done, i'd be very thankful. :) Would dladdr() do what you want? -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 10:17:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from temphost.dragondata.com (temphost.dragondata.com [63.167.131.128]) by hub.freebsd.org (Postfix) with ESMTP id 6EAA037B403 for ; Fri, 8 Jun 2001 10:17:26 -0700 (PDT) (envelope-from toasty@temphost.dragondata.com) Received: (from toasty@localhost) by temphost.dragondata.com (8.9.3/8.9.3) id MAA43035; Fri, 8 Jun 2001 12:17:41 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <200106081717.MAA43035@temphost.dragondata.com> Subject: Re: Access to symbol table(including dynamics) at runtime To: fmela0@sm.socccd.cc.ca.us (Farooq Mela) Date: Fri, 8 Jun 2001 12:17:41 -0500 (CDT) Cc: hackers@freebsd.org In-Reply-To: from "Farooq Mela" at Jun 08, 2001 10:16:28 AM X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Kevin Day wrote: > > > > Is there a simple way that I can lookup a symbol name(by address) during > > runtime? > > man dlopen. > I looked at this.. I see how I can dlopen my own executable, and dlsym() will let me get addresses from symbol names, but how do I do the reverse? I have an address and need to get the symbol name from it, not vice versa. -- Kevin Day toasty@dragondata.com - kevin@stileproject.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 10:18:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-d01.mx.aol.com (imo-d01.mx.aol.com [205.188.157.33]) by hub.freebsd.org (Postfix) with ESMTP id 8666537B406 for ; Fri, 8 Jun 2001 10:18:52 -0700 (PDT) (envelope-from Bsdguru@aol.com) Received: from Bsdguru@aol.com by imo-d01.mx.aol.com (mail_out_v30.22.) id n.e4.162cb0b4 (4243) for ; Fri, 8 Jun 2001 13:18:44 -0400 (EDT) From: Bsdguru@aol.com Message-ID: Date: Fri, 8 Jun 2001 13:18:44 EDT Subject: sysKonnect dual gig adapter To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Looking at the description of the sysKonnect dual adapter, its not clear if this is a real 2 port nic or that the second port is only a failover port. I have 2 questions for anyone who has one: 1) Can this be used as a 2 port gigabit NIC? 2) Does this NIC have hardware failover (that is, when power is cut the 2 ports will be physically tied together. I dont know of any PC plug in that does this, but its a neat feature. Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 10:20:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from temphost.dragondata.com (temphost.dragondata.com [63.167.131.128]) by hub.freebsd.org (Postfix) with ESMTP id 2CA4E37B401 for ; Fri, 8 Jun 2001 10:20:22 -0700 (PDT) (envelope-from toasty@temphost.dragondata.com) Received: (from toasty@localhost) by temphost.dragondata.com (8.9.3/8.9.3) id MAA43236; Fri, 8 Jun 2001 12:20:27 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <200106081720.MAA43236@temphost.dragondata.com> Subject: Re: Access to symbol table(including dynamics) at runtime To: dnelson@emsphone.com (Dan Nelson) Date: Fri, 8 Jun 2001 12:20:26 -0500 (CDT) Cc: hackers@FreeBSD.ORG In-Reply-To: <20010608121616.A23647@dan.emsphone.com> from "Dan Nelson" at Jun 08, 2001 12:16:16 PM X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > In the last episode (Jun 08), Kevin Day said: > > Is there a simple way that I can lookup a symbol name(by address) > > during runtime? > > > > I know I can exec nm, look up for the address I need, and get local > > symbols, but it would be really nice if I could get addresses of > > functions in dynamic libraries as well. I know I could use ldd to get > > offsets of each .so and calculate from there, but I'm starting to > > think I'm reproducing work that was done somewhere else. > > > > If someone could point me at a man page to something that can do what > > I need, tell me of a library that does something similar, or tell me > > why this can't be done, i'd be very thankful. :) > > Would dladdr() do what you want? AHH! YES! I'll buy a beer to the first person who adds dladdr(3) to the SEE ALSO section of dlopen's man page. Thank you! -- Kevin Day toasty@dragondata.com - kevin@stileproject.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 10:23:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id DFCAC37B401 for ; Fri, 8 Jun 2001 10:23:45 -0700 (PDT) (envelope-from bright@superconductor.rush.net) Received: (from bright@localhost) by superconductor.rush.net (8.11.2/8.11.2) id f58HNL024696; Fri, 8 Jun 2001 13:23:21 -0400 (EDT) Date: Fri, 8 Jun 2001 13:23:21 -0400 From: Alfred Perlstein To: Kevin Day Cc: Dan Nelson , hackers@FreeBSD.ORG Subject: Re: Access to symbol table(including dynamics) at runtime Message-ID: <20010608132320.F1832@superconductor.rush.net> References: <20010608121616.A23647@dan.emsphone.com> <200106081720.MAA43236@temphost.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <200106081720.MAA43236@temphost.dragondata.com>; from toasty@temphost.dragondata.com on Fri, Jun 08, 2001 at 12:20:26PM -0500 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Kevin Day [010608 13:21] wrote: > > > > In the last episode (Jun 08), Kevin Day said: > > > Is there a simple way that I can lookup a symbol name(by address) > > > during runtime? > > > > > > I know I can exec nm, look up for the address I need, and get local > > > symbols, but it would be really nice if I could get addresses of > > > functions in dynamic libraries as well. I know I could use ldd to get > > > offsets of each .so and calculate from there, but I'm starting to > > > think I'm reproducing work that was done somewhere else. > > > > > > If someone could point me at a man page to something that can do what > > > I need, tell me of a library that does something similar, or tell me > > > why this can't be done, i'd be very thankful. :) > > > > Would dladdr() do what you want? > > > AHH! YES! > > I'll buy a beer to the first person who adds dladdr(3) to the SEE ALSO > section of dlopen's man page. If you want to be able to see symbols in your main executable you _may_ need to also compile it with -export-dynamic or something like that. -- -Alfred Perlstein [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 10:23:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Exchange2000.com-con.ag (exchange2000.com-con.net [212.6.164.8]) by hub.freebsd.org (Postfix) with ESMTP id E34B037B408 for ; Fri, 8 Jun 2001 10:23:48 -0700 (PDT) (envelope-from rh@com-con.net) Content-Class: urn:content-classes:message Subject: AW: sysKonnect dual gig adapter MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Fri, 8 Jun 2001 19:23:47 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: sysKonnect dual gig adapter Thread-Index: AcDwR42BCnH1NHAcQ/W5W/JSDo9/5wAAElEQ From: "Heimes, Rene" To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG i can only answer question 1) - yes, it can be used as a dual port gigabit nic i can hardly imagine the syskonnect offers failover... hth cu ren=E9 -----Urspr=FCngliche Nachricht----- Von: Bsdguru@aol.com [mailto:Bsdguru@aol.com] Gesendet: Freitag, 8. Juni 2001 18:19 An: freebsd-hackers@freebsd.org Betreff: sysKonnect dual gig adapter Looking at the description of the sysKonnect dual adapter, its not clear if=20 this is a real 2 port nic or that the second port is only a failover port. I=20 have 2 questions for anyone who has one: 1) Can this be used as a 2 port gigabit NIC? 2) Does this NIC have hardware failover (that is, when power is cut the 2=20 ports will be physically tied together. I dont know of any PC plug in that=20 does this, but its a neat feature. Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 10:28:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id C54E737B407 for ; Fri, 8 Jun 2001 10:28:09 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f58HS4W26921; Fri, 8 Jun 2001 10:28:04 -0700 Date: Fri, 8 Jun 2001 10:28:04 -0700 From: Brooks Davis To: Bsdguru@aol.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: sysKonnect dual gig adapter Message-ID: <20010608102804.A26295@Odin.AC.HMC.Edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="J2SCkAp4GZ/dPZZf" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from Bsdguru@aol.com on Fri, Jun 08, 2001 at 01:18:44PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 08, 2001 at 01:18:44PM -0400, Bsdguru@aol.com wrote: > Looking at the description of the sysKonnect dual adapter, its not clear = if=20 > this is a real 2 port nic or that the second port is only a failover port= . I=20 > have 2 questions for anyone who has one: >=20 > 1) Can this be used as a 2 port gigabit NIC? > 2) Does this NIC have hardware failover (that is, when power is cut the 2= =20 > ports will be physically tied together. I dont know of any PC plug in tha= t=20 > does this, but its a neat feature. As the other respondent said, it's a 2-port NIC. If you want failover, you may want to check out Bill Paul's Fast EtherChannel module at: http://people.freebsd.org/~wpaul/FEC/ -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --J2SCkAp4GZ/dPZZf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7IQshXY6L6fI4GtQRAlnkAJ93PUyrRMpcVAhWyDy/kqjd84ajRwCgpFp/ 4XXP/b12dOjo00fdt1DHtVU= =+5ud -----END PGP SIGNATURE----- --J2SCkAp4GZ/dPZZf-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 10:52:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natpost.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 3FB7537B403 for ; Fri, 8 Jun 2001 10:52:07 -0700 (PDT) (envelope-from freebsd-ml@Econos.de) Received: from stefan-bt (p3EE2946E.dip.t-dialin.net [62.226.148.110]) by post.webmailer.de (8.9.3/8.8.7) with SMTP id TAA23827 for ; Fri, 8 Jun 2001 19:52:05 +0200 (MET DST) From: Stefan Hoffmeister To: freebsd-hackers@FreeBSD.ORG Subject: Wide character support - wchar.h? Date: Fri, 08 Jun 2001 19:51:08 +0200 Organization: Econos Message-ID: <4b32itsv8s5fepl1o6d1i3n4fg3r5s362a@4ax.com> X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG What are the status of / plans for support of select wide character routines, such as the ones declared in wchar.h? Particularly, I am looking for wcsoll, towupper, and towlower - IOW, the whole barrage of wide character transformation and collation :-) I haven't found anything conclusive in the mailing list archives. Has anyone tried to "fake" support for these functions via iconv operations from wide characters to the locale charset, performing a "normal" toupper / tolower / strcoll, and then transforming back? I am not certain whether these two transformations would be lossy or not. TIA, Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 11:11:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 0613637B407 for ; Fri, 8 Jun 2001 11:08:21 -0700 (PDT) (envelope-from roam@ringworld.nanolink.com) Received: (qmail 54114 invoked by uid 1000); 8 Jun 2001 18:06:35 -0000 Date: Fri, 8 Jun 2001 21:06:35 +0300 From: Peter Pentchev To: Stefan Hoffmeister Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Wide character support - wchar.h? Message-ID: <20010608210635.A54030@ringworld.oblivion.bg> Mail-Followup-To: Stefan Hoffmeister , freebsd-hackers@FreeBSD.ORG References: <4b32itsv8s5fepl1o6d1i3n4fg3r5s362a@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <4b32itsv8s5fepl1o6d1i3n4fg3r5s362a@4ax.com>; from freebsd-ml@Econos.de on Fri, Jun 08, 2001 at 07:51:08PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 08, 2001 at 07:51:08PM +0200, Stefan Hoffmeister wrote: > > What are the status of / plans for support of select wide character > routines, such as the ones declared in wchar.h? > > Particularly, I am looking for wcsoll, towupper, and towlower - IOW, the > whole barrage of wide character transformation and collation :-) > > I haven't found anything conclusive in the mailing list archives. > > Has anyone tried to "fake" support for these functions via iconv > operations from wide characters to the locale charset, performing a > "normal" toupper / tolower / strcoll, and then transforming back? > > I am not certain whether these two transformations would be lossy or not. I guess I should leave the answers to someone more familiar with this than I am (next to none), but I do believe that Takuya SHIOZAKI is currently working on multibyte support in -current's libc. G'luck, Peter -- Do you think anybody has ever had *precisely this thought* before? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 11:16:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id E78D237B403; Fri, 8 Jun 2001 11:16:08 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f58IQ4r01256; Fri, 8 Jun 2001 11:26:04 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106081826.f58IQ4r01256@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Thomas David Rivers Cc: jhb@FreeBSD.ORG, roam@orbitel.bg, hackers@FreeBSD.ORG Subject: Re: free() and const warnings In-reply-to: Your message of "Fri, 08 Jun 2001 06:55:50 EDT." <200106081055.GAA49069@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Jun 2001 11:26:04 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Since some strings are non-constant (the are allocated) - I believe > the `const' qualifier in the structure declaration is incorrect. 'const' just means "I will not be modifying this"; it's a way for a function prototype to constrain the function's implementation. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 11:29: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from primo.verat.net (primo.verat.net [217.26.64.130]) by hub.freebsd.org (Postfix) with ESMTP id 2115237B401 for ; Fri, 8 Jun 2001 11:27:54 -0700 (PDT) (envelope-from milunovic@sendmail.ru) Received: from scorpion.cosmos.all.net (ppp65-048.verat.net [217.26.65.48]) by primo.verat.net (8.10.2/8.10.2/RedHat5.0+CyGnUSs patch+pro) with ESMTP id f58IQmJ21053 for ; Fri, 8 Jun 2001 20:26:54 +0200 X-Authentication-Warning: primo.verat.net: Host ppp65-048.verat.net [217.26.65.48] claimed to be scorpion.cosmos.all.net Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by scorpion.cosmos.all.net (8.11.4/8.11.4) with ESMTP id f58IXJZ01278 for ; Fri, 8 Jun 2001 20:33:20 +0200 (CEST) Date: Fri, 8 Jun 2001 20:33:15 +0200 (CEST) From: milunovic X-Sender: milunovic@scorpion.cosmos.all.net To: hackers@freebsd.org Subject: ELF p_offset & p_vaddr Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- I'm little confused.I'm reading ELF specification and I found that p_offset and p_vaddr should be congrunet to module PAGE_SIZE. So is this correct ? If it isn't can anybody tell me what is correct. #define PAGE_SIZE 4096 p_offset % PAGE_SIZE == p_vaddr % PAGE_SIZE Vojislav Milunovic milunovic@sendmail.ru -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQEVAwUBOyEaby3gPLld8IkLAQFB6Af/Y5jFvo4/YOLuawln6JBsavjG3AtxbxVd gMMow39Jy1npYhmb+bzn7Dm2U4flhdlnLjF7j4Q02959uDH0qe1NHO665wu3dRoj SjgzfV/sG/eO+0QDc5gVMQmvJUZLlDn4weThqlBzzrRusexxndOeiXC6VkQJI21z eWKaB4cHSZ5QXIM3dCXyihNjEEMki9hLXwThtnd4jb83RRh6EWxkMsJn3lxJMSon B8H482ldbUv2GK3hnfV2V7AaMqgcitcLpdkpNQTqrRtZkLXHjcFBSKYumhXwfX4g cgTHJ01QTwQcdz2kd1Nlhfj017aZZK+iVYd57/13TEwfpZpT34Q5mg== =wCU+ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 12:12:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from aries.ai.net (aries.ai.net [205.134.163.4]) by hub.freebsd.org (Postfix) with ESMTP id 8DE2D37B406; Fri, 8 Jun 2001 12:07:57 -0700 (PDT) (envelope-from deepak@ai.net) Received: from blood (adsl-138-88-72-84.dc.adsl.bellatlantic.net [138.88.72.84]) by aries.ai.net (8.9.3/8.9.3) with SMTP id PAA24600; Fri, 8 Jun 2001 15:06:51 -0400 (EDT) (envelope-from deepak@ai.net) Reply-To: From: "Deepak Jain" To: "Assar Westerlund" Cc: Subject: RE: New error - lost data? Date: Fri, 8 Jun 2001 15:10:49 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <5l8zj3ruhx.fsf@assaris.sics.se> Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yes, its only happening on this one chassis so far. We'll try replacing the memory and see what happens. Thanks! Deepak Jain AiNET -----Original Message----- From: assar@assaris.sics.se [mailto:assar@assaris.sics.se]On Behalf Of Assar Westerlund Sent: Friday, June 08, 2001 9:07 AM To: deepak@ai.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: New error - lost data? "Deepak Jain" writes: > Others have seen this error (based on a Google search) but nothing recent > and nothing that conclusive. This is a very standard config that has been > stable for quite a while. The panic: malloc: lost data implies to me that > something is misbehaving with its memory allocations. > > Is this a hardware issue or an application problem? The kernel is 4.1 > RELEASE. The RAM is ECC. It should not be an application problem. It indicates that the memory pool administered by the kernel malloc is corrupt. Either it's a bug in the kernel or bad memory. Does it only happen on that particular machine with that particular memory? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 12:12:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 3A66E37B420 for ; Fri, 8 Jun 2001 12:12:37 -0700 (PDT) (envelope-from keramidi@otenet.gr) Received: from hades.hell.gr (patr530-a236.otenet.gr [212.205.215.236]) by mailsrv.otenet.gr (8.11.1/8.11.1) with ESMTP id f58JCSf05121; Fri, 8 Jun 2001 22:12:28 +0300 (EEST) Received: (from charon@localhost) by hades.hell.gr (8.11.3/8.11.3) id f58Fl1A16604; Fri, 8 Jun 2001 18:47:01 +0300 (EEST) (envelope-from keramidi@otenet.gr) Date: Fri, 8 Jun 2001 18:47:01 +0300 (EEST) From: Giorgos Keramidas X-X-Sender: To: Deepak Jain Cc: Subject: Re: New error - lost data? In-Reply-To: Message-ID: <20010608184100.K15426-100000@hades.hell.gr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 8 Jun 2001, Deepak Jain wrote: > I've never seen this error. Its been occuring randomly on this > machine, sometimes as often as every few minutes, sometimes days > apart. > > Others have seen this error (based on a Google search) but nothing recent > and nothing that conclusive. This is a very standard config that has been > stable for quite a while. The panic: malloc: lost data implies to me that > something is misbehaving with its memory allocations. > > Is this a hardware issue or an application problem? The kernel is 4.1 > RELEASE. The RAM is ECC. Well, this is definitely not an application problem. Your kernel panics before the malloc data for allocated/free memory is corrupt somehow. This seems to be a hardware problem. Namely one of your memory chips playing tricks on you. I would start by removing a few RAM chips and seeing if this happens when a particular set of them are being used. If the problem persists but only when a certain chip is present, you know whats wrong :) -giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 12:38:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 26F1A37B401 for ; Fri, 8 Jun 2001 12:38:34 -0700 (PDT) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f58JcU677055; Fri, 8 Jun 2001 21:38:30 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f58JdG227807; Fri, 8 Jun 2001 21:39:16 +0200 (CEST) Date: Fri, 8 Jun 2001 21:39:15 +0200 From: Bernd Walter To: Matt Dillon Cc: Graham Barr , freebsd-hackers@FreeBSD.ORG Subject: Re: read(2) and ETIMEDOUT Message-ID: <20010608213915.A27537@cicely20.cicely.de> References: <20010607171501.S50444@pobox.com> <200106071653.f57Grsn73369@earth.backplane.com> <20010607180011.U50444@pobox.com> <200106071733.f57HXov74249@earth.backplane.com> <20010607183535.X50444@pobox.com> <200106072220.f57MKwv78170@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106072220.f57MKwv78170@earth.backplane.com>; from dillon@earth.backplane.com on Thu, Jun 07, 2001 at 03:20:58PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 07, 2001 at 03:20:58PM -0700, Matt Dillon wrote: > > : > :On Thu, Jun 07, 2001 at 10:33:50AM -0700, Matt Dillon wrote: > :> > :> : > :> :Thanks, I will try setting errno, but I don't think it is signals. > :> :I have been running truss on the process. The relevant part is > :> : > :> :gettimeofday(0xbfbffa54,0x0) = 0 (0x0) > :> :select(0x50,0x93f8c90,0x0,0x0,0xbfbffa74) = 3 (0x3) > :> :read(0x16,0xa2da000,0x8000) ERR#60 'Operation timed out' > :> : > :> :In fact there are no signals in the whole truss output > :> : > :> :Graham. > :> > :> What type of descriptor is the read being performed on? A TCP > :> connection or, say, a reading a file over NFS? > : > :It is a TCP/IP connection. > : > :Graham. > > You can get this if the TCP connection times out, either through a > keepalive timeout or the protocol hits the maximum number of transmit > retries. I'd have to delve into the cvs logs to see when it was added, > but it seems reasonable. You should treat it simply as an EIO or > something like that. Keepalives are a good point. I know of OS/2 Systems that can't handle them and behave the way you describe. What system is on the other side? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 12:45:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from monty.mutatus.co.uk (monty.mutatus.co.uk [195.184.238.178]) by hub.freebsd.org (Postfix) with ESMTP id E02EA37B403 for ; Fri, 8 Jun 2001 12:45:08 -0700 (PDT) (envelope-from gbarr@mutatus.co.uk) Received: (from gbarr@localhost) by monty.mutatus.co.uk (8.11.3/8.11.3) id f58Jh9h15391; Fri, 8 Jun 2001 20:43:09 +0100 (BST) (envelope-from gbarr) Date: Fri, 8 Jun 2001 20:43:08 +0100 From: Graham Barr To: Bernd Walter Cc: Matt Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: read(2) and ETIMEDOUT Message-ID: <20010608204308.S50444@pobox.com> References: <20010607171501.S50444@pobox.com> <200106071653.f57Grsn73369@earth.backplane.com> <20010607180011.U50444@pobox.com> <200106071733.f57HXov74249@earth.backplane.com> <20010607183535.X50444@pobox.com> <200106072220.f57MKwv78170@earth.backplane.com> <20010608213915.A27537@cicely20.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010608213915.A27537@cicely20.cicely.de>; from ticso@mail.cicely.de on Fri, Jun 08, 2001 at 09:39:15PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 08, 2001 at 09:39:15PM +0200, Bernd Walter wrote: > On Thu, Jun 07, 2001 at 03:20:58PM -0700, Matt Dillon wrote: > > > > : > > :On Thu, Jun 07, 2001 at 10:33:50AM -0700, Matt Dillon wrote: > > :> > > :> : > > :> :Thanks, I will try setting errno, but I don't think it is signals. > > :> :I have been running truss on the process. The relevant part is > > :> : > > :> :gettimeofday(0xbfbffa54,0x0) = 0 (0x0) > > :> :select(0x50,0x93f8c90,0x0,0x0,0xbfbffa74) = 3 (0x3) > > :> :read(0x16,0xa2da000,0x8000) ERR#60 'Operation timed out' > > :> : > > :> :In fact there are no signals in the whole truss output > > :> : > > :> :Graham. > > :> > > :> What type of descriptor is the read being performed on? A TCP > > :> connection or, say, a reading a file over NFS? > > : > > :It is a TCP/IP connection. > > : > > :Graham. > > > > You can get this if the TCP connection times out, either through a > > keepalive timeout or the protocol hits the maximum number of transmit > > retries. I'd have to delve into the cvs logs to see when it was added, > > but it seems reasonable. You should treat it simply as an EIO or > > something like that. > > Keepalives are a good point. > I know of OS/2 Systems that can't handle them and behave the way you > describe. > What system is on the other side? All the systems are exactly the same Graham. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 12:56: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-r06.mx.aol.com (imo-r06.mx.aol.com [152.163.225.102]) by hub.freebsd.org (Postfix) with ESMTP id 689D437B401 for ; Fri, 8 Jun 2001 12:56:01 -0700 (PDT) (envelope-from Bsdguru@aol.com) Received: from Bsdguru@aol.com by imo-r06.mx.aol.com (mail_out_v30.22.) id n.43.16651c62 (4240) for ; Fri, 8 Jun 2001 15:55:55 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <43.16651c62.285287cb@aol.com> Date: Fri, 8 Jun 2001 15:55:55 EDT Subject: Re: sysKonnect dual gig adapter To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 06/08/2001 1:28:22 PM Eastern Daylight Time, brooks@one-eyed-alien.net writes: > > 1) Can this be used as a 2 port gigabit NIC? > > 2) Does this NIC have hardware failover (that is, when power is cut the 2 > > ports will be physically tied together. I dont know of any PC plug in that > > > does this, but its a neat feature. > > As the other respondent said, it's a 2-port NIC. If you want failover, > you may want to check out Bill Paul's Fast EtherChannel module at: > http://people.freebsd.org/~wpaul/FEC/ I specifically said "physical" failover. I guess no-one understands what that means? If it was a feature of the card, there would be no driver support required. But thanks for the info. Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 13: 9: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 49A0B37B405 for ; Fri, 8 Jun 2001 13:05:15 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 56702 invoked by uid 1000); 8 Jun 2001 20:03:33 -0000 Date: Fri, 8 Jun 2001 23:03:33 +0300 From: Peter Pentchev To: Bsdguru@aol.com Cc: freebsd-hackers@freebsd.org Subject: Re: sysKonnect dual gig adapter Message-ID: <20010608230333.F54030@ringworld.oblivion.bg> Mail-Followup-To: Bsdguru@aol.com, freebsd-hackers@freebsd.org References: <43.16651c62.285287cb@aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <43.16651c62.285287cb@aol.com>; from Bsdguru@aol.com on Fri, Jun 08, 2001 at 03:55:55PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 08, 2001 at 03:55:55PM -0400, Bsdguru@aol.com wrote: > In a message dated 06/08/2001 1:28:22 PM Eastern Daylight Time, > brooks@one-eyed-alien.net writes: > > > > 1) Can this be used as a 2 port gigabit NIC? > > > 2) Does this NIC have hardware failover (that is, when power is cut the > 2 > > > ports will be physically tied together. I dont know of any PC plug in > that > > > > > does this, but its a neat feature. > > > > As the other respondent said, it's a 2-port NIC. If you want failover, > > you may want to check out Bill Paul's Fast EtherChannel module at: > > http://people.freebsd.org/~wpaul/FEC/ > > I specifically said "physical" failover. I guess no-one understands what that > means? If it was a feature of the card, there would be no driver support > required. But thanks for the info. I have no idea whether this card-feature-no-driver statement is correct in this particular case, but it is definitely not correct in general: if it is a feature of the card, and especially if it is an advanced feature of the card, you need driver support to enable it. G'luck, Peter -- .siht ekil ti gnidaer eb d'uoy ,werbeH ni erew ecnetnes siht fI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 13:25:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fjord.dignus.com (sdsl-66-80-58-206.dsl.lax.megapath.net [66.80.58.206]) by hub.freebsd.org (Postfix) with ESMTP id F26CF37B403; Fri, 8 Jun 2001 13:25:11 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by fjord.dignus.com (8.11.1/8.11.1) with ESMTP id f58KQ8f01076; Fri, 8 Jun 2001 16:26:08 -0400 (EDT) (envelope-from rivers@dignus.com) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id QAA51955; Fri, 8 Jun 2001 16:27:27 -0400 (EDT) Date: Fri, 8 Jun 2001 16:27:27 -0400 (EDT) From: Thomas David Rivers Message-Id: <200106082027.QAA51955@lakes.dignus.com> To: msmith@FreeBSD.ORG, rivers@dignus.com Subject: Re: free() and const warnings Cc: hackers@FreeBSD.ORG, jhb@FreeBSD.ORG, roam@orbitel.bg In-Reply-To: <200106081826.f58IQ4r01256@mass.dis.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > Since some strings are non-constant (the are allocated) - I believe > > the `const' qualifier in the structure declaration is incorrect. > > 'const' just means "I will not be modifying this"; it's a way for a > function prototype to constrain the function's implementation. > Yes - it is.. However, "a string" is a const array of char. malloc(9) isn't. (And, can't be, since you have to, presumably, malloc the space and then write something meaningful to it...) So, if you declare a variable as const char * and then have different "constness" in assigning to that data, you are asking for the one variable to be both `const' and non-`const'... I was taking it from the "other side" (not the call to free() side, but the declaration of the data type...) Saying that the datum isn't actually `const' - it's only "sometimes const" (and only during the static initialization.) "sometimes const" doesn't make sense... But - then, if you remove the `const' - you get warnings from the initialization - assigning a pointer-to-const to a pointer-to-non-const. So... what's a programmer to do? That's the issue, right? - Dave R. - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 13:42:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 19A9237B403 for ; Fri, 8 Jun 2001 13:42:25 -0700 (PDT) (envelope-from sethk@meow.osd.bsdi.com) Received: (from sethk@localhost) by meow.osd.bsdi.com (8.11.3/8.11.2) id f58Kfex53797; Fri, 8 Jun 2001 13:41:40 -0700 (PDT) (envelope-from sethk) Date: Fri, 8 Jun 2001 13:41:40 -0700 From: Seth Kingsley To: Kevin Day Cc: Farooq Mela , hackers@FreeBSD.ORG Subject: Re: Access to symbol table(including dynamics) at runtime Message-ID: <20010608134140.A53292@meow.osd.bsdi.com> References: <200106081717.MAA43035@temphost.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106081717.MAA43035@temphost.dragondata.com>; from toasty@temphost.dragondata.com on Fri, Jun 08, 2001 at 12:17:41PM -0500 Organization: Wind River Systems X-Operating-System: FreeBSD 4.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 08, 2001 at 12:17:41PM -0500, Kevin Day wrote: > I looked at this.. I see how I can dlopen my own executable, and dlsym() > will let me get addresses from symbol names, but how do I do the reverse? I > have an address and need to get the symbol name from it, not vice versa. dladdr(3) of course. Not referenced in dlopen(3) either. -- || Seth Kingsley || Platforms Lab Opps || seth.kingsley@windriver.com || To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 14:15:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from messiah.megadeb.org (cpe.atm0-0-0-218131.arcnxx5.customer.tele.dk [62.242.79.117]) by hub.freebsd.org (Postfix) with ESMTP id 60BD837B40A for ; Fri, 8 Jun 2001 14:15:36 -0700 (PDT) (envelope-from chopra@runbox.com) Received: (from chopra@localhost) by messiah.megadeb.org (8.11.3/8.11.3) id f58LFwi53684 for freebsd-hackers@FreeBSD.ORG; Fri, 8 Jun 2001 23:15:58 +0200 (CEST) (envelope-from chopra) Date: Fri, 8 Jun 2001 23:14:43 +0200 From: Munish Chopra To: freebsd-hackers@FreeBSD.ORG Subject: Re: New error - lost data? Message-ID: <20010608231443.D39309@messiah.megadeb.org> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <20010608184100.K15426-100000@hades.hell.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010608184100.K15426-100000@hades.hell.gr>; from keramidi@otenet.gr on Fri, Jun 08, 2001 at 06:47:01PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 08, 2001 at 06:47:01PM +0300, Giorgos Keramidas wrote: > On Fri, 8 Jun 2001, Deepak Jain wrote: > > > Is this a hardware issue or an application problem? The kernel is 4.1 > > RELEASE. The RAM is ECC. > > I would start by removing a few RAM chips and seeing if this happens > when a particular set of them are being used. If the problem persists > but only when a certain chip is present, you know whats wrong :) Check out http://reality.sgi.com/cbrady_denver/memtest86/ while you're at it. I hear it's helped a lot of people find faulty RAM. -- -Munish To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 16:37: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 1B34F37B405; Fri, 8 Jun 2001 16:36:53 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f58Naj299417; Fri, 8 Jun 2001 16:36:45 -0700 (PDT) (envelope-from dillon) Date: Fri, 8 Jun 2001 16:36:45 -0700 (PDT) From: Matt Dillon Message-Id: <200106082336.f58Naj299417@earth.backplane.com> To: Peter Pentchev Cc: John Baldwin , hackers@FreeBSD.ORG Subject: Re: free() and const warnings References: <20010607195634.I724@ringworld.oblivion.bg> <20010608114957.C19938@ringworld.oblivion.bg> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :OK, here's a scenario: : :struct validation_fun { : const char *name; : valfun *fun; : int dyn; :}; : :This is a structure for a set of validation functions, referenced by :name from another type of object. There are some predefined functions, :present in the code at compile-time, and hardcoded in an array, with :names given as "strings". Thus, the 'const'. : :However, some of the functions may be defined at runtime, with both :name and code sent by a server. In that case, the name is a dynamically :allocated char *, which needs to be freed upon cleanup. So I have: : :[cleanup function] : ... : if (val->dyn) : free(val->name); : :Any suggestions on how to improve the design to avoid this, if possible, :would be greatly welcome. : :G'luck, :Peter I am a great believer in const char * ... it's saved my ass on more occassions then I can count. I have very similar situations where certain elements of a structure are usually static but sometimes dynamic. My recommendation is that you NOT attempt to overload the duel nature of 'name'. Instead make it always a 'const char *'. Here is my suggestion: struct validation_fun { const char *name; valfun *fun; int dyn; /* * OPAQUE */ char *allocations; /* or make it an array for more */ }; As far as 99.9% of your codebase is concerned, 'name' points to a read-only entity and is not dynamically allocated, even from the point of view of FreeValidationFun(). But if you need to dynamically allocate the string for name you have a field to hold the dynamic allocation, in this case 'allocations'. You ALSO assign the result to 'name', but FreeValidationFun() only looks to 'allocations' to determine if there is anything it must free() and, of course, 'allocations' can remain NULL. This neatly solves the problem and guarentees that no confusion will occur. Here's another example: Lets say you have a routine that can return an error code AND an error message, and to make it fast you want to be able to return static strings for the message. But sometimes the error message is allocated. So: char *alloc = NULL; const char *emsg; error = TheRoutine1(parameters, &emsg, &alloc); ... process emsg ... error = TheRoutine2(parameters, &emsg, &alloc); ... process emsg ... error = TheRoutine3(parameters, &emsg, &alloc); ... process emsg ... safe_free(&alloc); TheRoutine*() assigns the error message simply with something like: *emsg = "Yah, Everything is fine"; But if TheRoutine*() needs to allocate the error message it does this: safe_replacef(alloc, "You screwed up %d times!", n); *emsg = alloc; I have three helper routines to make this sort of string management trivial: void safe_free(char **ptr); If *ptr is not NULL, free(*ptr) then set *ptr to NULL. void safe_replace(char **ptr, const char *str); If *ptr is not NULL, free(*ptr) then set *ptr = strdup(str); void safe_replacef(char **ptr, const char *ctl, ...); If *ptr is not NULL, free(*ptr) then use varargs and vasprintf() to allocate the replacement string. I call these routines 'safe' because if their internal malloc()s fail they assert and exit... I don't like checking for memory failures in thousands of places in my code, I prefer to check them in just a handful of places. Probably a more involved answer then you were looking for, but hey! BTW, I don't use static buffers for virtually anything any more... I use asprintf() (or in my case, safe_asprintf()), safe_strdup(), safe_replace(), safe_replacef(), safe_free(), etc... My 'safe' routines. I use them for everything these days. It removes all possibilities of a buffer overflow from my code. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 16:39:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id A47EC37B403; Fri, 8 Jun 2001 16:39:44 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f58Ndg399460; Fri, 8 Jun 2001 16:39:42 -0700 (PDT) (envelope-from dillon) Date: Fri, 8 Jun 2001 16:39:42 -0700 (PDT) From: Matt Dillon Message-Id: <200106082339.f58Ndg399460@earth.backplane.com> To: Peter Pentchev Cc: John Baldwin , hackers@FreeBSD.ORG Subject: Re: free() and const warnings References: <20010607195634.I724@ringworld.oblivion.bg> <20010608114957.C19938@ringworld.oblivion.bg> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Here is the whole set of supporting routines. -Matt /* * STRDUP.C * * $Backplane: backplane/src/libsupport/strdup.c,v 1.13 2001/04/03 00:03:18 dillon Exp $ */ #include "defs.h" Export char *safe_strdup(const char *s); Export char *safe_strdup_segment(const char *start, const char *end); Export char *safe_replace(char **pptr, const char *s); Export char *safe_replacef(char **pptr, const char *ctl, ...); Export char *safe_append(char **pptr, const char *s); Export char *safe_appendf(char **pptr, const char *ctl, ...); /* * safe_strdup() - Safe version of strdup(), core dump if alloc fails */ char * safe_strdup(const char *s) { char *r; if (s == NULL) return(NULL); if ((r = strdup(s)) == NULL) fatalmem(); return(r); } /* * safe_replace() - Free existing string, allocate copy * * Allocates a copy of 's' and stores the copy in *pptr. The * previous contents of *ptr is freed. * * Typical useage is to initialize *pptr to NULL, then use * safe_replace() as many times as necessary (or within a loop), * then safe_free(pptr) after all operations are complete. * * This code optimizes the case where 's' is the same as *pptr. */ char * safe_replace(char **pptr, const char *s) { /* * Same data (also occurs if s == *ptr), nothing to do */ if (*pptr) { if (s && strcmp(s, *pptr) == 0) return(*pptr); free(*pptr); } /* * free old, dup new. */ *pptr = (s) ? strdup(s) : NULL; return(*pptr); } /* * safe_replacef() - Free existing string, allocate copy, with formatting * * This operates the same as safe_replace(), except a printf-style * format string and arguments is passed rather then a simple string. */ char * safe_replacef(char **pptr, const char *ctl, ...) { va_list va; char *optr = *pptr; if (ctl) { va_start(va, ctl); if (vasprintf(pptr, ctl, va) < 0) fatalmem(); va_end(va); } safe_free(&optr); return(*pptr); } /* * safe_append() - Append to an existing string, reallocating as required * * *pptr represents allocated storage or NULL. *pptr is replaced * with a new string which is the original string with the 's' argument * appended. The original string is deallocated. * * *pptr is usually initialized to NULL, causing this routine to do * the initial allocation as well as the reallocation in successive * calls. safe_free(pptr) is typically called after all operations * are complete and the result string is no longer needed. */ char * safe_append(char **pptr, const char *s) { char *old; char *new; if ((old = *pptr) != NULL) { int newLen = strlen(old) + strlen(s) + 1; new = malloc(newLen); snprintf(new, newLen, "%s%s", old, s); free(old); } else { new = strdup(s); } *pptr = new; return(new); } /* * safe_appendf() - Var-args version of safe_append() * * Operates like safe_append(), but using a printf-like format string * and additional arguments to generate the string to append. */ char * safe_appendf(char **pptr, const char *ctl, ...) { char *old; char *new; va_list va; va_start(va, ctl); if ((old = *pptr) != NULL) { if (vasprintf(&new, ctl, va) < 0) DBASSERT(0); *pptr = new; asprintf(&new, "%s%s", old, new); free(*pptr); free(old); } else { if (vasprintf(&new, ctl, va) < 0) DBASSERT(0); } va_end(va); *pptr = new; return(new); } /* * safe_strdup_segment() - duplicate a portion of a string * * Returns an allocated string representing the specified segment * between start and end (end non-inclusive). Dumps core if the * allocation fails. The returned string will be null terminated. */ char * safe_strdup_segment(const char *start, const char *end) { char *new; int len; if (start == NULL || end == NULL) return(NULL); if (start > end) { const char *temp = end; end = start; start = temp; } len = end - start; new = safe_malloc(len + 1); memcpy(new, start, len); new[len] = '\0'; return(new); } /* * ASPRINTF.C * * $Backplane: backplane/src/libsupport/asprintf.c,v 1.4 2001/04/03 00:03:18 dillon Exp $ */ #include "defs.h" Export void safe_asprintf(char **pptr, const char *ctl, ...); Export void safe_vasprintf(char **pptr, const char *ctl, va_list va); /* * safe_asprintf() - safe version of asprintf() * * This routine implements a safe version of asprintf(), which allocates * the result string and stored it in *ptr. The program will dump * core if the allocation fails. * * *ptr need not be initialized to anything in particular prior to * calling this routine. * * Since the return value from the stdc asprintf() is not portable, we * simply return void in our safe version. */ void safe_asprintf(char **pptr, const char *ctl, ...) { va_list va; int r; va_start(va, ctl); r = vasprintf(pptr, ctl, va); va_end(va); DBASSERT(r >= 0); } /* * safe_vasprintf() - safe version of var-args asprintf. * * This routine implements a safe version of vasprintf(), which allocates * the result string and stored it in *ptr. The program will dump * core if the allocation fails. * * *ptr need not be initialized to anything in particular prior to * calling this routine. * * Since the return value from the stdc vasprintf() is not portable, we * simply return void in our safe version. */ void safe_vasprintf(char **pptr, const char *ctl, va_list va) { int r; r = vasprintf(pptr, ctl, va); DBASSERT(r >= 0); } /* * MALLOC.C * * $Backplane: backplane/src/libsupport/malloc.c,v 1.11 2001/04/03 00:03:18 dillon Exp $ */ #include "defs.h" Export void *safe_malloc(size_t bytes); Export void *safe_realloc(void *ptr, size_t size); Export void safe_free(char **ptr); /* * safe_malloc() - safe version of malloc. Dumps core if the allocation fails */ void * safe_malloc(size_t bytes) { char *ptr = malloc(bytes); if (ptr == NULL) fatalmem(); return(ptr); } /* * safe_realloc() - safe version of realloc. Dumps core if the * allocation fails */ void * safe_realloc(void *ptr, size_t size) { if (ptr == NULL) ptr = malloc(size); else ptr = realloc(ptr, size); if (ptr == NULL) fatalmem(); return(ptr); } /* * safe_free() - free a string pointer safely. * * Given the address of the pointer (rather then the pointer itself), * this routine is a NOP if the pointer is NULL, and will free() and * NULL-out the pointer if it is non-NULL. * * This function is typically only used on string pointers. Structural * allocations should use zalloc() and zfree(). */ void safe_free(char **ptr) { if (*ptr) { free(*ptr); *ptr = NULL; } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 16:44:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id C0DE037B405; Fri, 8 Jun 2001 16:44:53 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f58NirE99600; Fri, 8 Jun 2001 16:44:53 -0700 (PDT) (envelope-from dillon) Date: Fri, 8 Jun 2001 16:44:53 -0700 (PDT) From: Matt Dillon Message-Id: <200106082344.f58NirE99600@earth.backplane.com> To: Matt Dillon Cc: Peter Pentchev , John Baldwin , hackers@FreeBSD.ORG Subject: Re: free() and const warnings References: <20010607195634.I724@ringworld.oblivion.bg> <20010608114957.C19938@ringworld.oblivion.bg> <200106082339.f58Ndg399460@earth.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Oh my, and just posting these I found a couple of bugs! :char * :safe_replace(char **pptr, const char *s) :{ : /* : * Same data (also occurs if s == *ptr), nothing to do : */ : if (*pptr) { : if (s && strcmp(s, *pptr) == 0) : return(*pptr); : free(*pptr); : } : : /* : * free old, dup new. : */ : *pptr = (s) ? strdup(s) : NULL; : return(*pptr); :} Should call safe_strdup(), not strdup(). :char * :safe_append(char **pptr, const char *s) :{ : char *old; : char *new; : : if ((old = *pptr) != NULL) { : int newLen = strlen(old) + strlen(s) + 1; : new = malloc(newLen); : snprintf(new, newLen, "%s%s", old, s); : free(old); : } else { : new = strdup(s); : } : *pptr = new; : return(new); :} Ditto. Should call safe_strdup(), not strdup(). I probably should have cleaned the source up before posting it. I also have a fatalmem() routine which assert(0)'s, and DBASSERT(0) is simply assert(0)... really should be a fatalmem() call too. Oh well. You get the picture! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 16:52:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp4ve.mailsrvcs.net (smtp4vepub.gte.net [206.46.170.25]) by hub.freebsd.org (Postfix) with ESMTP id C10FE37B401; Fri, 8 Jun 2001 16:52:44 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-117-210.nnj.dialup.bellatlantic.net [151.198.117.210]) by smtp4ve.mailsrvcs.net (8.9.1/8.9.1) with ESMTP id XAA41437936; Fri, 8 Jun 2001 23:50:12 GMT Message-ID: <3B2164B3.84284526@bellatlantic.net> Date: Fri, 08 Jun 2001 19:50:11 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: j mckitrick Cc: Doug Rabson , "Matthew N. Dodd" , Warner Losh , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: newbussifying drivers References: <20010608040211.A61278@dogma.freebsd-uk.eu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG j mckitrick wrote: > > Okay, there is something i'm not understanding here. In the ed driver, > there are many possible cards, which each have different i/o ports, correct? > The driver has a lot of probe routines, and it looks like they are just > using different macros with hard-coded (#defined) port addresses. > > So, how do you CORRECTLY use the newbus calls to probe these ports? I am > not running -current, so i do not have 'hints'. As Doug Rabson said, write an 'identify' routine. Look at the ep driver for an example. And my artile in DaemonNews (www.daemonnews.org) from I think August 2000 or somewhere around that time gives some description of the newbussified ISA drivers. It should also be included into the Handbook by now. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 17:54: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 1290B37B403 for ; Fri, 8 Jun 2001 17:53:58 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f590rp216371; Fri, 8 Jun 2001 17:53:51 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f590roD50858; Fri, 8 Jun 2001 17:53:50 -0700 (PDT) (envelope-from jdp) Date: Fri, 8 Jun 2001 17:53:50 -0700 (PDT) Message-Id: <200106090053.f590roD50858@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: milunovic@sendmail.ru Subject: Re: ELF p_offset & p_vaddr In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article , milunovic wrote: > > I'm little confused.I'm reading ELF specification and I found that > p_offset and p_vaddr should be congrunet to module PAGE_SIZE. > So is this correct ? If it isn't can anybody tell me what is correct. It is correct. It is done that way so that the file can be loaded into memory simply by mapping it. Mapping occurs on page boundaries. > #define PAGE_SIZE 4096 > p_offset % PAGE_SIZE == p_vaddr % PAGE_SIZE Yes, that's correct. For example, notice that the final 3 digits are the same here in the "VMA" and "File off" columns. PAGE_SIZE == 4096 == 0x1000. blake$ objdump -h /usr/bin/id /usr/bin/id: file format elf32-i386 Sections: Idx Name Size VMA LMA File off Algn 0 .interp 00000019 080480f4 080480f4 000000f4 2**0 CONTENTS, ALLOC, LOAD, READONLY, DATA 1 .note.ABI-tag 00000018 08048110 08048110 00000110 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 2 .hash 000000d8 08048128 08048128 00000128 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 3 .dynsym 00000230 08048200 08048200 00000200 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 4 .dynstr 00000138 08048430 08048430 00000430 2**0 CONTENTS, ALLOC, LOAD, READONLY, DATA 5 .rel.bss 00000010 08048568 08048568 00000568 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 6 .rel.plt 00000098 08048578 08048578 00000578 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 7 .init 0000000b 08048610 08048610 00000610 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE 8 .plt 00000140 0804861c 0804861c 0000061c 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE 9 .text 00000928 0804875c 0804875c 0000075c 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE 10 .fini 00000006 08049084 08049084 00001084 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE 11 .rodata 0000035a 080490a0 080490a0 000010a0 2**5 CONTENTS, ALLOC, LOAD, READONLY, DATA 12 .data 0000000c 0804a3fc 0804a3fc 000013fc 2**2 CONTENTS, ALLOC, LOAD, DATA 13 .eh_frame 00000004 0804a408 0804a408 00001408 2**2 CONTENTS, ALLOC, LOAD, DATA 14 .ctors 00000008 0804a40c 0804a40c 0000140c 2**2 CONTENTS, ALLOC, LOAD, DATA 15 .dtors 00000008 0804a414 0804a414 00001414 2**2 CONTENTS, ALLOC, LOAD, DATA 16 .got 00000058 0804a41c 0804a41c 0000141c 2**2 CONTENTS, ALLOC, LOAD, DATA 17 .dynamic 00000088 0804a474 0804a474 00001474 2**2 CONTENTS, ALLOC, LOAD, DATA 18 .bss 00000130 0804a4fc 0804a4fc 000014fc 2**3 ALLOC 19 .comment 000000c8 00000000 00000000 000014fc 2**0 CONTENTS, READONLY 20 .note 00000050 00000000 00000000 000015c4 2**0 CONTENTS, READONLY John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 19: 1:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 1D9E437B401; Fri, 8 Jun 2001 19:01:47 -0700 (PDT) Subject: Re: sysKonnect dual gig adapter In-Reply-To: from "Bsdguru@aol.com" at "Jun 8, 2001 01:18:44 pm" To: Bsdguru@aol.com Date: Fri, 8 Jun 2001 19:01:47 -0700 (PDT) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20010609020147.1D9E437B401@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Looking at the description of the sysKonnect dual adapter, its not clear if > this is a real 2 port nic or that the second port is only a failover port. I > have 2 questions for anyone who has one: > > 1) Can this be used as a 2 port gigabit NIC? Yes. You will have two interfaces, sk0 and sk1, which represent the two ports. Each interface operates independently of the other. > 2) Does this NIC have hardware failover (that is, when power is cut the 2 > ports will be physically tied together. I dont know of any PC plug in that > does this, but its a neat feature. No. SysKonnect advertises the cards for use in failover applications with their Windows (and Linux) drivers. However this is a feature of their driver software only: it has nothing to do with the hardware. When I wrote the if_sk driver, I decided that setting it up as a real dual port NIC was more useful. (If you're really curious, go to www.syskonnect.com and download their Linux driver source. It has all of their failover magic in it.) The SysKonnect cards consist of the SysKonnect GEnesis chip and the XaQti XMAC II chip. (XaQti no longer exists, it was assimilated by Vitesse.) The XMAC is a gigabit MAC with a generic bus interface. The GEnesis provides the PCI interface, DMA support, some packet buffering and arbitration. Basically, the GEnesis is what lets you connect the XMAC to a PCI bus. But the GEnesis is designed to support _two_ XMAC chips: it has two sets of DMA queues and two register windows so you can twiddle both XMACs at once. That's how the dual link cards work: there's one GEnesis and two XMACs, and if you have a copper card, two Broadcom copper gigabit PHYs. This is a bit different from the usual multiport NIC design where you have two PCI-based MAC chips and a PCI-PCI bridge. Functionally, this is the same as having a bunch of single-port PCI NICs in their own slots. The SysKonnect multiplexes both MACs through a single PCI slot instead. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 19: 9: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id C9FA537B401; Fri, 8 Jun 2001 19:09:01 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id UAA75726; Fri, 8 Jun 2001 20:18:11 -0700 (PDT) Date: Fri, 8 Jun 2001 20:18:09 -0700 (PDT) From: Julian Elischer To: Sergey Babkin Cc: j mckitrick , Doug Rabson , "Matthew N. Dodd" , Warner Losh , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: newbussifying drivers In-Reply-To: <3B2164B3.84284526@bellatlantic.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I don;t know why people always forget it, but also look at the sample driver in -current. /usr/share/examples/drivers/make_device_driver.sh (the 4.x version is way out of date) On Fri, 8 Jun 2001, Sergey Babkin wrote: > j mckitrick wrote: > > > > Okay, there is something i'm not understanding here. In the ed driver, > > there are many possible cards, which each have different i/o ports, correct? > > The driver has a lot of probe routines, and it looks like they are just > > using different macros with hard-coded (#defined) port addresses. > > > > So, how do you CORRECTLY use the newbus calls to probe these ports? I am > > not running -current, so i do not have 'hints'. > > As Doug Rabson said, write an 'identify' routine. Look at the > ep driver for an example. And my artile in DaemonNews > (www.daemonnews.org) from I think August 2000 or somewhere around > that time gives some description of the newbussified ISA drivers. > It should also be included into the Handbook by now. > > -SB > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 19:19: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 93C6937B401 for ; Fri, 8 Jun 2001 19:19:05 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f592J4720842; Fri, 8 Jun 2001 19:19:04 -0700 Date: Fri, 8 Jun 2001 19:19:04 -0700 From: Brooks Davis To: hackers@FreeBSD.ORG Cc: Brian Somers , Poul-Henning Kamp Subject: Re: cloning network interfaces Message-ID: <20010608191904.A18847@Odin.AC.HMC.Edu> References: <200106071119.f57BJr766008@hak.lan.Awfulhak.org> <20010607164812.A32379@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010607164812.A32379@Odin.AC.HMC.Edu>; from brooks@one-eyed-alien.net on Thu, Jun 07, 2001 at 04:48:12PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Following Brian's suggestion, I've modified gif to create a /dev/if_gif device with is controlled by the IOCIFMANAGE ioctl which allows creation and deletion of specific devices and creation of wildcard devices. I've hacked ifconfig to support this in a general manner. If you know which one you want to use you can do something like ifconfig gif783 10.0.0.1 10.0.0.2 # gifconfig has to come second because I didn't add creation support to # it because I want to kill it off in favor of ifconfig "tsrc" and # "tdst" parameters like Solaris uses. gifconfig gif783 blah or if you don't care which one you use you can do newgif=3D`ifconfig gif#` gifconfig ${newgif} blah=20 ifconfig ${newgif} 10.0.0.1 10.0.0.2 You can also delete interfaces: ifconfig -D gif783 Additionaly, I removed all the annoying refrences to gif.h and NGIF, and moved things around so gif can be loaded and unloaded as a module. A copy of the diff as avaiable at the URL below and I'm submitting a PR titled "[PATCH] make gif fully dynamic". http://www.one-eyed-alien.net/~brooks/FreeBSD/gif.diff -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7IYeXXY6L6fI4GtQRAmlnAJ48CBNaHhSgTCUMVtQLya+p9o9ovACdH77w vtSanFX9GDrkNFOONycYVwY= =f8KG -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jun 8 23:31:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id E85CD37B405 for ; Fri, 8 Jun 2001 23:31:35 -0700 (PDT) (envelope-from DougB@DougBarton.net) Received: from DougBarton.net (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id XAA53619; Fri, 8 Jun 2001 23:31:28 -0700 (PDT) (envelope-from DougB@DougBarton.net) Message-ID: <3B21C2BF.F8B317C1@DougBarton.net> Date: Fri, 08 Jun 2001 23:31:27 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Chris Coleman Cc: hackers@FreeBSD.ORG Subject: Re: Softupdates not syncing References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Chris Coleman wrote: > > On one of our servers, deleted space is not being freed and causing is to > run out of disk space. To test this, I copied a 200 meg file to the /usr > partition and then deleted it. I checked df before copying, after copying, > and after deleting it. After deleting it, the space never became > available. I waited atleast 24 hours just to make sure. > > 4.2-STABLE FreeBSD 4.2-STABLE #0: Mon Jan 29 10:18:20 PST 2001 Please upgrade to 4.3-Stable and try your tests again. There is no way to know whether or not your situation was improved by the many changes in RELENG_4 in the last 4 months. Thanks, Doug -- If you're never wrong, you're not trying hard enough. Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 0:49:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from zorg.centauri.org (adsl-206-170-148-73.dsl.snfc21.pacbell.net [206.170.148.73]) by hub.freebsd.org (Postfix) with ESMTP id 1942E37B405 for ; Sat, 9 Jun 2001 00:49:51 -0700 (PDT) (envelope-from neild@adira.centauri.org) Received: by zorg.centauri.org (Postfix, from userid 1001) id A5D959BC6; Sat, 9 Jun 2001 00:49:40 -0700 (PDT) Date: Sat, 9 Jun 2001 00:49:40 -0700 From: Damien Neil To: hackers@FreeBSD.ORG Subject: Re: free() and const warnings Message-ID: <20010609004940.B50335@misago.org> References: <20010607195634.I724@ringworld.oblivion.bg> <20010607124729.B4940@shade.nectar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <20010607124729.B4940@shade.nectar.com>; from n@nectar.com on Thu, Jun 07, 2001 at 12:47:30PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 07, 2001 at 12:47:30PM -0500, Jacques A. Vidrine wrote: > C99 says of uintptr_t only that for any valid pointer p, the following > is true: > > (void *)(uintptr_t)p == (void *)p > > Likewise for intptr_t. I read that as covering both code and data > pointers. C89, at least, does not guarantee that you can convert between code and data pointers. I believe the same holds for C99. - Damien To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 9: 7:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from jhs.muc.de (jhs.muc.de [193.149.49.84]) by hub.freebsd.org (Postfix) with ESMTP id 757CF37B401 for ; Sat, 9 Jun 2001 09:07:45 -0700 (PDT) (envelope-from jhs@jhs.muc.de) Received: from park.jhs.private (localhost [127.0.0.1]) by jhs.muc.de (8.11.0/8.11.0) with ESMTP id f59986S65481; Sat, 9 Jun 2001 09:08:06 GMT (envelope-from jhs@park.jhs.private) Message-Id: <200106090908.f59986S65481@jhs.muc.de> To: Dave Hayes Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Why does fsck try to fsck a CDROM? From: "Julian Stacey" Organization: Vector Systems Ltd - Munich Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ In-reply-to: Your message of "Thu, 07 Jun 2001 19:09:41 PDT." <200106080209.TAA08276@hokkshideh.jetcafe.org> Date: Sat, 09 Jun 2001 11:08:06 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > There is none. No default fstab exists. Maybe it comes from the /etc/fstab that is unpacked into ram disc, that is extracted from the 2.88M boot floppy, that is part of a bootable CD ? ( BTW if you'r going to get into questions around bootable cdroms etc, it's a frequent area of interest on freebsd-small@freebsd.org ) Julian - Julian Stacey Unix Consultant - Munich Germany http://bim.bsn.com/~jhs/ Ihr Rauchen => mein allergischer Kopfschmerz ! Kau/Schnupftabak probieren ! Like Linux ? Then also look at FreeBSD with its 5000+ packages ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 9:55:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 8A09F37B405; Sat, 9 Jun 2001 09:55:37 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.133.57.Dial1.SanJose1.Level3.net [209.245.133.57]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id MAA02414; Sat, 9 Jun 2001 12:55:35 -0400 (EDT) Message-ID: <3B225525.8C4695D@mindspring.com> Date: Sat, 09 Jun 2001 09:56:05 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Assar Westerlund Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How to disable software TCP checksumming? References: <20010529144114.I19771@luke.immure.com> <20010529221107.C49875@skriver.dk> <20010529155212.M19771@luke.immure.com> <20010530045200.A1031@hades.hell.gr> <20010529235215.A60177@luke.immure.com> <20010530085155.B24096@Odin.AC.HMC.Edu> <200105310204.f4V248n15260@whizzo.transsys.com> <200106070549.WAA06248@windsor.research.att.com> <3B208F11.87722148@mindspring.com> <5lk82ntb0o.fsf@assaris.sics.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Assar Westerlund wrote: > > Terry Lambert writes: > > This all came from IP headers being 14 bytes long, instead > > of 16. > > Hu? An IPv4 header (not including options) is 20 bytes long. Sorry; ethernet header. The problem is the 14 bytes making the code unaligned on a 32 or 64 bit boundary... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 10:21:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from johnson.mail.mindspring.net (johnson.mail.mindspring.net [207.69.200.177]) by hub.freebsd.org (Postfix) with ESMTP id A369E37B405 for ; Sat, 9 Jun 2001 10:21:39 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.133.57.Dial1.SanJose1.Level3.net [209.245.133.57]) by johnson.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id NAA00599; Sat, 9 Jun 2001 13:21:38 -0400 (EDT) Message-ID: <3B225B3E.5C3D0FC0@mindspring.com> Date: Sat, 09 Jun 2001 10:22:06 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bsdguru@aol.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How to disable software TCP checksumming? References: <84.1717a060.28525287@aol.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bsdguru@aol.com wrote: > > This thread is baffling. The bottom line is that you cant > trust data coming into your machine, and you have to > checksum it. The link level check only verifies that what > was sent by the last forwarding point is the same as what > you got, but in NO WAY implies that all of the data is > valid. A link level checksum pass is a necessary, but not > a sufficient condition for the data being acceptable. There > are scads of reasons that it could be bad. Disabling > checksumming is a kludge that you may chose to do, but its > never the right thing to do. Tell me: at what point are you willing to trust the data? Is "the card plus the motherboard" my machine, or is it just "the motherboard"? The cards support offloading the checksum to hardware; you are saying that it is never reasonable to do this. Fine. That basically means that we need to checksum the contents of memory once they have been loaded into the L2 cache, to make sure they arrived safely from memory. Wait... now we need to checksum them in L1 cache, once they have arrived from L2. Wait... now we need to checksum them in the pipeline, as they have arrived from our untrustworthy L1 cache... At some point you have to draw the boundary between the "inside" and the "outside". I am happy to draw this boundary at the etherenet cable; why are you insisting that I draw it at the PCI bus instead? Does your requirement apply to devices integrated on the motherboard, or is your concern solely with the mechanical PCI connectors between the boards and the motherboard? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 12:17:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id BD6F237B401 for ; Sat, 9 Jun 2001 12:17:13 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f59JH9c08727; Sat, 9 Jun 2001 12:17:09 -0700 (PDT) (envelope-from dillon) Date: Sat, 9 Jun 2001 12:17:09 -0700 (PDT) From: Matt Dillon Message-Id: <200106091917.f59JH9c08727@earth.backplane.com> To: Ian Dowse Cc: tlambert2@mindspring.com, freebsd-hackers@FreeBSD.ORG Subject: Re: UFS large directory performance References: <200106081115.aa43142@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :leaving the dirhash structure attached to the inode when its hash :array is freed. : :An updated patch is available at : : http://www.maths.tcd.ie/~iedowse/FreeBSD/dirhash.diff3 : :I haven't had a chance to do more than a minimal amount of testing, :so there may be many issues remaining. : :Ian I'll have a chance to do some testing tonight now that I have the swap-full fixes rolling down the hill. The two-level approach looks a lot cleaner - we should be able to solve whatever performance/load/scaleability issues arise with it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 13:12:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id B7F3137B401 for ; Sat, 9 Jun 2001 13:12:49 -0700 (PDT) (envelope-from reichert@natto.numachi.com) Received: (qmail 8765 invoked by uid 3001); 9 Jun 2001 20:12:48 -0000 Received: from natto.numachi.com (198.175.254.216) by numachi.numachi.com with SMTP; 9 Jun 2001 20:12:48 -0000 Received: (qmail 58418 invoked by uid 1001); 9 Jun 2001 20:12:48 -0000 Date: 9 Jun 2001 20:12:48 -0000 Message-ID: <20010609201248.58417.qmail@natto.numachi.com> From: reichert@natto.numachi.com To: perlbug@perl.com Subject: oct() doesn't handle binary strings Cc: hackers@FreeBSD.org Reply-To: reichert@numachi.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a bug report for perl from reichert@numachi.com, generated with the help of perlbug 1.26 running under perl 5.00503. ----------------------------------------------------------------- [Please enter your report here] From perlfunc(1): oct EXPR ... (If EXPR happens to start off with 0x, interprets it as a hex string. If EXPR starts off with 0b, it is interpreted as a binary string.) But the binary string conversion doesn't seem to work: natto% perl -e 'print oct("0b11000110")."\n"' 0 This is otherwise a valid binary string: natto% perl -e 'print unpack('C', (pack("B8", "11000110")))."\n"' 198 The hex string conversion function does work: natto% perl -e 'print oct("0xC6")."\n"' 198 [Please do not change anything below this line] ----------------------------------------------------------------- --- Site configuration information for perl 5.00503: Configured by markm at Sun Mar 5 13:39:27 SAST 2000. Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration: Platform: osname=freebsd, osvers=4.0-current, archname=i386-freebsd uname='FreeBSD freefall.FreeBSD.org 4.0-current FreeBSD 4.0-current #0: $Date$' hint=recommended, useposix=true, d_sigaction=define usethreads=undef useperlio=undef d_sfio=undef Compiler: cc='cc', optimize='undef', gccversion=2.95.2 19991024 (release) cppflags='' ccflags ='' stdchar='char', d_stdstdio=undef, usevfork=true intsize=4, longsize=4, ptrsize=4, doublesize=8 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 alignbytes=4, usemymalloc=n, prototype=define Linker and Libraries: ld='cc', ldflags ='-Wl,-E -lperl -lm ' libpth=/usr/lib libs=-lm -lc -lcrypt libc=, so=so, useshrplib=true, libperl=libperl.so.3 Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' -Wl,-R/usr/lib' cccdlflags='-DPIC -fpic', lddlflags='-Wl,-E -shared -lperl -lm ' Locally applied patches: --- @INC for perl 5.00503: /home/reichert/lib/perl /usr/libdata/perl/5.00503/mach /usr/libdata/perl/5.00503 /usr/local/lib/perl5/site_perl/5.005/i386-freebsd /usr/local/lib/perl5/site_perl/5.005 . --- Environment for perl 5.00503: HOME=/home/reichert LANG (unset) LANGUAGE (unset) LD_LIBRARY_PATH (unset) LOGDIR (unset) PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/ucb:/usr/libexec:/usr/X11R6/bin:/usr/etc:/usr/games:/usr/local/games/bin:/home/reichert/bin:/home/reichert/bin PERL5LIB=/home/reichert/lib/perl PERL_BADLANG (unset) SHELL=/bin/tcsh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 13:13:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from onion.perl.org (onion.valueclick.com [209.85.157.220]) by hub.freebsd.org (Postfix) with SMTP id 5CA7437B403 for ; Sat, 9 Jun 2001 13:13:21 -0700 (PDT) (envelope-from perlbug@rfi.net) Received: (qmail 54554 invoked by uid 1007); 9 Jun 2001 20:13:14 -0000 Date: 9 Jun 2001 20:13:14 -0000 X-Perlbug-Url-Bug: http://bugs.perl.org/index.html?req=bug_id&bug_id=20010609.007 To: reichert@numachi.com X-Original-Message-Id: <20010609201248.58417.qmail@natto.numachi.com> Cc: hackers@freebsd.org X-Original-To: perlbug@perl.com X-Original-CC: hackers@FreeBSD.org Subject: Ack: [ID 20010609.007] oct() doesn't handle binary strings X-Errors-To: perlbug@rfi.net From: perlbugtron@bugs.perl.org X-Perlbug: Perlbug(tron) v2.75 X-Perlbug-Admin-Url-Bug: http://bugs.perl.org/index.html?req=bug_id&bug_id=20010609.007 X-Original-Subject: oct() doesn't handle binary strings X-Original-Perlbug: X-Original-From: reichert@natto.numachi.com Reply-To: perlbug@rfi.net Message-Id: <54530_442698013.235035@bugs.perl.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Your e-mail has been received by the Perl Bug Squashing Team. Original subject: oct() doesn't handle binary strings A Bug ID (20010609.007) has been assigned and is shown in the subject of this email. Please include this bug ID in the subject line of any followup messages. This is an automatic confirmation message. If you do not wish to recieve this confirmation, in the future, put 'ack=no' somewhere in the body of your mail. -- Perl Bug Squashing Team Message from the Perlbug squashing team at 'perlbug@perl.org' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 13:24:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 0AC3737B401 for ; Sat, 9 Jun 2001 13:24:26 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.3/8.11.3) with ESMTP id f59KONt88614; Sat, 9 Jun 2001 21:24:23 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.4/8.11.4) with ESMTP id f59KOMA07577; Sat, 9 Jun 2001 21:24:22 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200106092024.f59KOMA07577@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Brooks Davis Cc: Brian Somers , Poul-Henning Kamp , hackers@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: cloning network interfaces In-Reply-To: Message from Brooks Davis of "Thu, 07 Jun 2001 16:48:12 PDT." <20010607164812.A32379@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Jun 2001 21:24:22 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Ok, I've got the quick and dirty way working for testing (a nine line > clone handler works great for that), but I think Brian's suggestion is > probably best for a real solution especialy since it's rather easier to > check for permissions before allowing creation this way. My current > patch lets joe user create 2^15 gif devices by doing "ls /dev/gif###" > 2^15 times because I didn't have a proc structure handy. The other > advantage is that it should be fairly easy to backport to -stable which > is where the project I'm working on this for is currently being developed. > > I think I'll add a to ifconfig function styled after ifmaybeload() that > trys to create interfaces if the user trys to do something with them. > I'm still thinking about the right way to handle creation of new, free > devices, perhaps a syntax like: > > ifconfig gif# > > where ifconfig returns the interface name the way mdconfig does when you > don't specify a unit. If we decied that interfaces that want to grow > this way will have a /dev/if_ device that accepts the appropriate > ioctl(s), that should be fairly easy to implement so it works in all > cases without further hacks to ifconfig. I think it'd be better to use the solaris ``plumb'' keyword. I can't recall how it works (something like ``ifconfig gif0 plumb'' - I haven't got a Solaris machine handy here), but it seemed cleaner, making it more obvious what's being done. An ``unplumb'' keyword may be appropriate for doing the removal. > -- Brooks -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 13:59:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id D6E4937B403 for ; Sat, 9 Jun 2001 13:59:17 -0700 (PDT) (envelope-from nectar@nectar.com) Received: by gw.nectar.com (Postfix, from userid 1001) id 6660CAF213; Sat, 9 Jun 2001 15:59:17 -0500 (CDT) Date: Sat, 9 Jun 2001 15:59:17 -0500 From: "Jacques A. Vidrine" To: Damien Neil Cc: hackers@FreeBSD.ORG Subject: Re: free() and const warnings Message-ID: <20010609155917.A2954@hellblazer.nectar.com> References: <20010607195634.I724@ringworld.oblivion.bg> <20010607124729.B4940@shade.nectar.com> <20010609004940.B50335@misago.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010609004940.B50335@misago.org>; from neild@misago.org on Sat, Jun 09, 2001 at 12:49:40AM -0700 X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Jun 09, 2001 at 12:49:40AM -0700, Damien Neil wrote: > On Thu, Jun 07, 2001 at 12:47:30PM -0500, Jacques A. Vidrine wrote: > > C99 says of uintptr_t only that for any valid pointer p, the following > > is true: > > > > (void *)(uintptr_t)p == (void *)p > > > > Likewise for intptr_t. I read that as covering both code and data > > pointers. > > C89, at least, does not guarantee that you can convert between code > and data pointers. I believe the same holds for C99. Agreed. The original point was whether or not a uintptr_t was big enough for both types of pointers. Cheers, -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 14:25:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 88AB737B401 for ; Sat, 9 Jun 2001 14:25:23 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f59LZW701229; Sat, 9 Jun 2001 14:35:33 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106092135.f59LZW701229@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: tlambert2@mindspring.com Cc: Bsdguru@aol.com, freebsd-hackers@FreeBSD.ORG Subject: Re: How to disable software TCP checksumming? In-reply-to: Your message of "Sat, 09 Jun 2001 10:22:06 PDT." <3B225B3E.5C3D0FC0@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Jun 2001 14:35:32 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Tell me: at what point are you willing to trust the data? > > Is "the card plus the motherboard" my machine, or is it > just "the motherboard"? > > The cards support offloading the checksum to hardware; > you are saying that it is never reasonable to do this. No, that's not what's being said. > Fine. That basically means that we need to checksum the > contents of memory once they have been loaded into the > L2 cache, to make sure they arrived safely from memory. That's why you have an ECC memory datapath. > Wait... now we need to checksum them in L1 cache, once > they have arrived from L2. And that's why you run ECC on the L2 cache as well. > Wait... now we need to checksum them in the pipeline, as > they have arrived from our untrustworthy L1 cache... And... yes, you got it. Some people will even ECC the L1 cache. > At some point you have to draw the boundary between the > "inside" and the "outside". I am happy to draw this > boundary at the etherenet cable; why are you insisting > that I draw it at the PCI bus instead? Well, if PCI parity worked, you could trust the PCI bus more, but the bottom line is simply that you can't trust *anything*, and the more that you do trust, the more you expose yourself to risk. > Does your requirement apply to devices integrated on the > motherboard, or is your concern solely with the mechanical > PCI connectors between the boards and the motherboard? PCI is typically implemented as a no-parity bus. Anything from poor drive to coupled noise to a simple alpha-decay error in a pipeline FIFO somewhere will cause PCI bus data corruption. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 14:27:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-m08.mx.aol.com (imo-m08.mx.aol.com [64.12.136.163]) by hub.freebsd.org (Postfix) with ESMTP id 7521E37B401 for ; Sat, 9 Jun 2001 14:27:07 -0700 (PDT) (envelope-from Bsdguru@aol.com) Received: from Bsdguru@aol.com by imo-m08.mx.aol.com (mail_out_v30.22.) id d.99.16194e84 (16790); Sat, 9 Jun 2001 17:27:04 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <99.16194e84.2853eea7@aol.com> Date: Sat, 9 Jun 2001 17:27:03 EDT Subject: Re: How to disable software TCP checksumming? To: tlambert2@mindspring.com Cc: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 06/09/2001 1:21:45 PM Eastern Daylight Time, tlambert2@mindspring.com writes: > Bsdguru@aol.com wrote: > > > > This thread is baffling. The bottom line is that you cant > > trust data coming into your machine, and you have to > > checksum it. The link level check only verifies that what > > was sent by the last forwarding point is the same as what > > you got, but in NO WAY implies that all of the data is > > valid. A link level checksum pass is a necessary, but not > > a sufficient condition for the data being acceptable. There > > are scads of reasons that it could be bad. Disabling > > checksumming is a kludge that you may chose to do, but its > > never the right thing to do. > > Tell me: at what point are you willing to trust the data? > > Is "the card plus the motherboard" my machine, or is it > just "the motherboard"? > > The cards support offloading the checksum to hardware; > you are saying that it is never reasonable to do this. > > Fine. That basically means that we need to checksum the > contents of memory once they have been loaded into the > L2 cache, to make sure they arrived safely from memory. > > Wait... now we need to checksum them in L1 cache, once > they have arrived from L2. > no, if your system is bad, you are sunk in general. This discussion was transforming into a "the link level check is good enough" discussion, and that what I was commenting on. Of course if the hardware does the IP and tcp checksumming its adaquate, although unreported DMA errors are not that uncommon, so it is safer to do the checks AFTER the data has been copied to memory. It may be a mistake to assume that all bus transfers are 100% reliable. Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 15: 8:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from szit.bme.hu (fourier.szit.bme.hu [152.66.84.8]) by hub.freebsd.org (Postfix) with SMTP id 7F4F037B405 for ; Sat, 9 Jun 2001 15:08:38 -0700 (PDT) (envelope-from gyori@szit.bme.hu) Received: (qmail 78074 invoked by uid 8452); 9 Jun 2001 22:08:37 -0000 Date: Sun, 10 Jun 2001 00:08:37 +0200 (CEST) From: Gyori Sandor To: Subject: nsswitch dynamically loadable modules Message-ID: <20010610000004.V77923-100000@fourier.szit.bme.hu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, FreeBSD 4.x has no support to nsswitch, and even the -CURRENT supports only very few, predefined methods such as files, nis, nisplus for user authentication in nsswitch.conf. Dynamically loadable modules can't be used, for example nss_ldap for authentication via LDAP. There are patches to solve this problem at http://www.nectar.com/freebsd/nsswitch but only a part of them was built in to -CURRENT (the statical part). Could anybody tell me why? This is a serious deficiency of FreeBSD which has been solved on Linux for ages. Is there any security or other reason not to implement a fully functional nsswitch feature into FreeBSD? Is there anybody who use _properly working_ nsswitch and nss_ldap on FreeBSD? Is there anybody who can do authentication via LDAP on a FreeBSD box? Best wishes, Sandor Gyori Technical University of Budapest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 17:32:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 49E3037B401 for ; Sat, 9 Jun 2001 17:32:56 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f5A0WtV34285 for ; Sat, 9 Jun 2001 18:32:55 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200106100032.f5A0WtV34285@harmony.village.org> To: hackers@freebsd.org Subject: Strange request: Reading RX-50 (aka DEC Rainbow 100) disks Date: Sat, 09 Jun 2001 18:32:55 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have the need to read a whole pile of DEC Rainbow 100 floppies. I can do it on the DEC Rainbow, but that's a huge pita since it isn't networked. I'd like to either connect a RX-50 drive to my machine, or use a 1.2M 5.25" floppy drive that I can scrounge easily enough to do the deed. 80 tracks, 10 spt, 1 side. 400k in size. I think it uses either 250kb/s or 300kb/s for the data transfer rate (same as the 3.5" low density drives, if my memory isn't going south). Has anybody done this before? Any pointers? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 18:29:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 0052437B401 for ; Sat, 9 Jun 2001 18:29:41 -0700 (PDT) (envelope-from scanner@jurai.net) Received: from localhost (scanner@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id VAA46210; Sat, 9 Jun 2001 21:29:28 -0400 (EDT) Date: Sat, 9 Jun 2001 21:29:27 -0400 (EDT) From: To: Gyori Sandor Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: nsswitch dynamically loadable modules In-Reply-To: <20010610000004.V77923-100000@fourier.szit.bme.hu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 10 Jun 2001, Gyori Sandor wrote: > Hello, > > There are patches to solve this problem at > http://www.nectar.com/freebsd/nsswitch > but only a part of them was built in to -CURRENT (the statical part). > > Could anybody tell me why? This is a serious deficiency of FreeBSD which > has been solved on Linux for ages. Is there any security or other reason > not to implement a fully functional nsswitch feature into FreeBSD? If it's such a deficiency where are you're patches to fix the missing bits? I fail to see them attached to this mail. Maybe my mailer dropped them on the floor. Please resend them! thanks! > Is there anybody who use _properly working_ nsswitch and nss_ldap on > FreeBSD? Many of us are waiting on nectars code. He is very busy working on other things. And last time I checked he hoped to be picking it back up in June. He is doing the best he can. You can help by finishing his work and submitting the changes back so we get complete support sooner. I await you're contribution. ============================================================================= -Chris Watson (316) 326-3862 | FreeBSD Consultant, FreeBSD Geek Work: scanner@jurai.net | Open Systems Inc., Wellington, Kansas Home: scanner@deceptively.shady.org | http://open-systems.net ============================================================================= WINDOWS: "Where do you want to go today?" LINUX: "Where do you want to go tomorrow?" BSD: "Are you guys coming or what?" ============================================================================= irc.openprojects.net #FreeBSD -Join the revolution! ICQ: 20016186 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 19: 2:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 5B7ED37B408 for ; Sat, 9 Jun 2001 19:02:25 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f5A22E209082; Sat, 9 Jun 2001 19:02:14 -0700 Date: Sat, 9 Jun 2001 19:02:14 -0700 From: Brooks Davis To: Brian Somers Cc: Brooks Davis , Poul-Henning Kamp , hackers@FreeBSD.ORG Subject: Re: cloning network interfaces Message-ID: <20010609190214.A6854@Odin.AC.HMC.Edu> References: <200106092024.f59KOMA07577@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="9jxsPFA5p3P2qPhR" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106092024.f59KOMA07577@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Sat, Jun 09, 2001 at 09:24:22PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 09, 2001 at 09:24:22PM +0100, Brian Somers wrote: > I think it'd be better to use the solaris ``plumb'' keyword. I can't=20 > recall how it works (something like ``ifconfig gif0 plumb'' - I=20 > haven't got a Solaris machine handy here), but it seemed cleaner,=20 > making it more obvious what's being done. An ``unplumb'' keyword may=20 > be appropriate for doing the removal. That's how it works. I've though about adding (un)plumb functions, but that gets a bit weird. With the current way ifconfig parses options would require that you peak at the argument list early because you need to create the device before arguments are processed. Also, given the way the FreeBSD rc system works you have to support commands like: ifconfig gif0 plumb inet 10.0.0.1 10.0.0.2 tsrc 192.168.1.6 tdst 192.168.1.7 because you only get one shot at each device[0]. In -stable I think I'd like to leave the current create behavior where devices are created if you try to use them and perhaps emit a warning suggesting using plumb to avoid breaking configs. In 5.0 I'd be reasionably happy to force plumbing of interfaces if there's come concensus that it's the right way to go. Alternativly, we could hack the rc system to try plumbing all interfaces before they are used. Any opinions on this? -- Brooks [0] This is actually a serious problem with wireless interfaces today because you can't write: ifconfig wi0 ssid XXX wepmode on wepkey 1:12345 DHCP which is exactly what you want to do on most home networks. IMO following the Solaris example of teaching ifconfig about dhcp is the right way to go here. Perhaps by allowing plugable external parameters to keep it general. --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7ItUlXY6L6fI4GtQRAgoxAKCURYzCIfMXEo5wuLpK7tCTht5AUACfXa9o h/v0w/StECrMyVS4RT1/NQc= =Doz6 -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 19:52:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.netcom.com (freebsd.netcom.com [199.174.33.250]) by hub.freebsd.org (Postfix) with ESMTP id 773AA37B401 for ; Sat, 9 Jun 2001 19:52:50 -0700 (PDT) (envelope-from bugs@freebsd.netcom.com) Received: (from bugs@localhost) by freebsd.netcom.com (8.8.8+Sun/8.8.8) id VAA23587 for hackers@freebsd.org; Sat, 9 Jun 2001 21:52:49 -0500 (CDT) From: Mark Hittinger Message-Id: <200106100252.VAA23587@freebsd.netcom.com> Subject: re: Strange request: Reading RX-50 (aka DEC Rainbow 100) disks To: hackers@freebsd.org Date: Sat, 9 Jun 2001 21:52:49 -0500 (CDT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Has anybody done this before? Any pointers? I'm very familiar with the RX50 on the Rainbow. I wrote the "copy protected disk copier" for it in that bygone era. ARRRRR!! The Rainbow ran several operating systems, CPM, CPM/86, MSDOS 2, and MSDOS 3. The Rainbow had both a z80 cpu and an 8088 cpu with the lowest 2k ram shared between the z80 and the 8088. The z80 controlled the floppy drive via a WD 1793 chip. I'd actually recommend trying to use kermit to get the data out via the serial port first :-) There is a rainbow kermit out there. I remember being able to transfer files between the Rainbow and the IBM PC using a lower density single sided format - like 40 tracks. This was in MSDOS world only and not CPM. I'd bet there are utilities on simtel20 that would read a CPM format floppy in 40 track format. I formatted them on the IBM PC in low density mode and then wrote data to them on the Rainbow. There is also a version of DECNET for the Rainbow that works via the serial port. If you can find someone with a PDP-11 or a MicroVAX unix system somewhere you might be able to just dd them. I still have my Rainbow and I have to use an air blower to get rid of dust in order to get the floppies to even read at all anymore. My apple ][ floppies still read solid with no air blower. Good Luck! Mark Hittinger Earthlink bugs@freebsd.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 20: 2:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.147.224.201]) by hub.freebsd.org (Postfix) with ESMTP id CC7D937B401 for ; Sat, 9 Jun 2001 20:02:14 -0700 (PDT) (envelope-from jim@thehousleys.net) Received: (from root@localhost) by thehousleys.net (8.11.3/8.11.2) id f5A323s58398; Sat, 9 Jun 2001 23:02:03 -0400 (EDT) (envelope-from jim@thehousleys.net) Received: from thehousleys.net (baby.int.thehousleys.net [192.168.0.24]) (authenticated) by thehousleys.net (8.11.3/8.11.3) with ESMTP id f5A322r58390; Sat, 9 Jun 2001 23:02:02 -0400 (EDT) (envelope-from jim@thehousleys.net) Message-ID: <3B22E32A.38BA6238@thehousleys.net> Date: Sat, 09 Jun 2001 23:02:02 -0400 From: James Housley X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Hittinger Cc: hackers@freebsd.org Subject: Re: Strange request: Reading RX-50 (aka DEC Rainbow 100) disks References: <200106100252.VAA23587@freebsd.netcom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mark Hittinger wrote: > > MSDOS world only and not CPM. I'd bet there are utilities on simtel20 that > would read a CPM format floppy in 40 track format. I formatted them on the A quick search returned 10 matches with this one looking like what you want. http://www.simtel.net/pub/pd/44392.shtml Jim -- /"\ ASCII Ribbon Campaign . \ / - NO HTML/RTF in e-mail . X - NO Word docs in e-mail . / \ ----------------------------------------------------------------- jeh@FreeBSD.org http://www.FreeBSD.org The Power to Serve jim@TheHousleys.Net http://www.TheHousleys.net --------------------------------------------------------------------- It's always a long day, 86400 doesn't fit into a short. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 20: 5:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id D1A0037B403 for ; Sat, 9 Jun 2001 20:05:34 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f5A35W646711; Sat, 9 Jun 2001 21:05:33 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.2/8.8.3) with ESMTP id f5A38el17955; Sat, 9 Jun 2001 21:08:40 -0600 (MDT) Message-Id: <200106100308.f5A38el17955@billy-club.village.org> To: Mark Hittinger Subject: Re: Strange request: Reading RX-50 (aka DEC Rainbow 100) disks Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 09 Jun 2001 21:52:49 CDT." <200106100252.VAA23587@freebsd.netcom.com> References: <200106100252.VAA23587@freebsd.netcom.com> Date: Sat, 09 Jun 2001 21:08:40 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200106100252.VAA23587@freebsd.netcom.com> Mark Hittinger writes: : I'd actually recommend trying to use kermit to get the data out via the : serial port first :-) There is a rainbow kermit out there. Not an option. I have about 100 floppies to transfer. I know I could set this up, but 9600 baud is just too slow. : I remember being able to transfer files between the Rainbow and the IBM PC : using a lower density single sided format - like 40 tracks. This was in : MSDOS world only and not CPM. I'd bet there are utilities on simtel20 that : would read a CPM format floppy in 40 track format. I formatted them on the : IBM PC in low density mode and then wrote data to them on the Rainbow. Well, I could use the IMPDRIVE driver that I wrote for the 720k low density floppy and transfer things that way. I don't want to do that either. While less painful than serial, it is still painful. There was a driver for DOS that would do this, but I don't have DOS on my machines. This tells me that the 1.2M drives will read them w/o a problem. Writing I know is a problem due to different head technologies used between them. : If you can find someone with a PDP-11 or a MicroVAX unix system somewhere : you might be able to just dd them. I do have the options of connection the hardware up to the floppy controller in my desktop too :-). I have both the RX-50 drives, as well as a pair of TEAC FD55 drives (that do the same data rate as the RX-50's, with the same heads, but with only one drive per spindle and two read heads instead of one). Trouble is, it looks like our floppy driver doesn't grok single sided 400k disks :-(. That's what I'm looking to hack and advise on how to hack. : I still have my Rainbow and I have to use an air blower to get rid of dust : in order to get the floppies to even read at all anymore. My apple ][ : floppies still read solid with no air blower. I had to use the air blower as well, but most of the disks read after that :-). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 20: 7:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id C172B37B401 for ; Sat, 9 Jun 2001 20:07:38 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f5A37b646726; Sat, 9 Jun 2001 21:07:37 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.2/8.8.3) with ESMTP id f5A3Ail18008; Sat, 9 Jun 2001 21:10:44 -0600 (MDT) Message-Id: <200106100310.f5A3Ail18008@billy-club.village.org> To: James Housley Subject: Re: Strange request: Reading RX-50 (aka DEC Rainbow 100) disks Cc: Mark Hittinger , hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 09 Jun 2001 23:02:02 EDT." <3B22E32A.38BA6238@thehousleys.net> References: <3B22E32A.38BA6238@thehousleys.net> <200106100252.VAA23587@freebsd.netcom.com> Date: Sat, 09 Jun 2001 21:10:44 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3B22E32A.38BA6238@thehousleys.net> James Housley writes: : Mark Hittinger wrote: : > : > MSDOS world only and not CPM. I'd bet there are utilities on simtel20 that : > would read a CPM format floppy in 40 track format. I formatted them on the : : A quick search returned 10 matches with this one looking like what you : want. : : http://www.simtel.net/pub/pd/44392.shtml Right, but none of them run under FreeBSD. I have at least two or three of these programs already. My problem is getting the bits off the disk on a FreeBSD box. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jun 9 21:16:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 9289337B403 for ; Sat, 9 Jun 2001 21:16:15 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f5A4GF317496; Sat, 9 Jun 2001 21:16:15 -0700 Date: Sat, 9 Jun 2001 21:16:15 -0700 From: Brooks Davis To: hackers@FreeBSD.ORG Cc: Brian Somers , Poul-Henning Kamp , hackers@FreeBSD.ORG Subject: Re: cloning network interfaces Message-ID: <20010609211615.A17310@Odin.AC.HMC.Edu> References: <200106092024.f59KOMA07577@hak.lan.Awfulhak.org> <20010609190214.A6854@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="3MwIy2ne0vdjdPXF" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010609190214.A6854@Odin.AC.HMC.Edu>; from brooks@one-eyed-alien.net on Sat, Jun 09, 2001 at 07:02:14PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 09, 2001 at 07:02:14PM -0700, Brooks Davis wrote: > On Sat, Jun 09, 2001 at 09:24:22PM +0100, Brian Somers wrote: > > I think it'd be better to use the solaris ``plumb'' keyword. I can't= =20 > > recall how it works (something like ``ifconfig gif0 plumb'' - I=20 > > haven't got a Solaris machine handy here), but it seemed cleaner,=20 > > making it more obvious what's being done. An ``unplumb'' keyword may= =20 > > be appropriate for doing the removal. >=20 > That's how it works. I've though about adding (un)plumb functions, but > that gets a bit weird. With the current way ifconfig parses options > would require that you peak at the argument list early because you need > to create the device before arguments are processed. Also, given the > way the FreeBSD rc system works you have to support commands like: >=20 > ifconfig gif0 plumb inet 10.0.0.1 10.0.0.2 tsrc 192.168.1.6 tdst 192.168.= 1.7 >=20 > because you only get one shot at each device[0]. In -stable I think I'd > like to leave the current create behavior where devices are created if > you try to use them and perhaps emit a warning suggesting using plumb > to avoid breaking configs. In 5.0 I'd be reasionably happy to force > plumbing of interfaces if there's come concensus that it's the right > way to go. Alternativly, we could hack the rc system to try plumbing > all interfaces before they are used. Any opinions on this? I went ahead and nuked the auto-creation and -D flag in favor of plumb and unplumb in the patch at: http://www.one-eyed-alien.net/~brooks/FreeBSD/gif.diff This version includes a change to rc.network to plumb gif interfaces before calling gifcreate. This will still trip up users who build static gif tunnels from hosts with dynamic addresses since they can't run gifconfig yet, but we don't really have any means of supporting that in the rc files yet anyway. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --3MwIy2ne0vdjdPXF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7IvSOXY6L6fI4GtQRAj67AKCEaNm4lly1YlvyQiG9wiPAoISSmQCgrQSC kdMWzg4ZRUKpmXrziDFti9o= =8I8a -----END PGP SIGNATURE----- --3MwIy2ne0vdjdPXF-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message