From owner-freebsd-hackers Sun Nov 7 0: 8:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (Postfix) with ESMTP id 3001715102 for ; Sun, 7 Nov 1999 00:07:47 -0800 (PST) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id AAA01199; Sun, 7 Nov 1999 00:07:47 -0800 (PST) (envelope-from sef) Date: Sun, 7 Nov 1999 00:07:47 -0800 (PST) From: Sean Eric Fagan Message-Id: <199911070807.AAA01199@kithrup.com> To: hackers@freebsd.org Reply-To: hackers@freebsd.org Subject: Re: Procfs' pointers to files. In-Reply-To: <38252A5C.2C388485.kithrup.freebsd.hackers@newsguy.com> References: Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <38252A5C.2C388485.kithrup.freebsd.hackers@newsguy.com> you write: >Brian Fundakowski Feldman wrote: >> It sounds to me that what you really want are the semantics of a >> symbolic link and not the semantics of a hard link. Is it just me, >> or does it seem as if the pathname of the executable being stored as >> a virtual symlink in procfs as "file" would solve these security >> problems? >Mmmmm... I like that... I don't, but what I like doesn't matter, it seems -- Warner knows everything. So I'm sure he knows better than I do the overhead this will impose, and the impracticality in a general system. Unix really isn't set up to carry around 'official pathnames,' due to the existence of symlinks and other fun stuff. Other systems are set up for this -- my favourite was EMBOS, by ELXSI -- and there are some _really_ nifty things you can do, if you have it. (Watchdogs and program-based-access-lists are my two favourite, the latter allowing you to get rid of SUID/SGID in many cases. There is a paper available on implementing watchdogs under unix [4.2bsd, I believe] that discusses some of this. If you're willing to cover 60-80% of the cases, instead of 95-100%, it's considerably easier.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 0:31:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7EE5814C31; Sun, 7 Nov 1999 00:31:47 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p24-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.153]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id RAA25324; Sun, 7 Nov 1999 17:31:12 +0900 (JST) Message-ID: <3825384E.C6214B61@newsguy.com> Date: Sun, 07 Nov 1999 17:29:02 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Alexey Zelkin Cc: Mike Smith , hackers@freebsd.org Subject: Re: loader security problem References: <19991105222636.B27448@scorpion.crimea.ua> <199911060019.QAA00813@dingo.cdrom.com> <19991107000520.A23479@scorpion.crimea.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexey Zelkin wrote: > > IMHO, it would be nice to have password protected loader(8) (like linux lilo) > or just ACLs for loader(8)'s "more" command (like unavailable for viewing > files) cat >/boot/passwd.4th <> /boot/loader.rc Say... does LILO have a scripting language? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 0:47:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 65EA914BD3 for ; Sun, 7 Nov 1999 00:47:20 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p24-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.153]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id RAA29395; Sun, 7 Nov 1999 17:47:01 +0900 (JST) Message-ID: <38253C03.A7036A91@newsguy.com> Date: Sun, 07 Nov 1999 17:44:51 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Jos Backus Cc: Sheldon Hearn , Jos Backus , freebsd-hackers@FreeBSD.ORG Subject: Re: ftpd feature: lock file being stored References: <19991105111518.A2328@hal.mpn.cp.philips.com> <7173.941797101@axl.noc.iafrica.com> <19991105113929.B2328@hal.mpn.cp.philips.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jos Backus wrote: > > Scanning the directory for new files, as the aforementioned script does. If > you have more than one script doing this at the same time, both may conclude > that a given file is ``available'' and try to act upon it. Inevitably, one of > those scripts will fail. Hence my solution. But maybe I don't quite understand > the problem :-) > > (Yes, I know you will say, "Don't run more than one script at a time then.". > But whether this is possible really depends on the application and moreover > seems to be an unecessary restriction.) Actually, use fstat to check against ftpd, and lockf between the scripts. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 1:57: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id EA40E1502D for ; Sun, 7 Nov 1999 01:56:58 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id BAA57541 for ; Sun, 7 Nov 1999 01:56:58 -0800 (PST) Date: Sun, 7 Nov 1999 01:56:57 -0800 (PST) From: Julian Elischer To: hackers@FreeBSD.ORG Subject: Re: Procfs' pointers to files. In-Reply-To: <199911070807.AAA01199@kithrup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 7 Nov 1999, Sean Eric Fagan wrote: > In article <38252A5C.2C388485.kithrup.freebsd.hackers@newsguy.com> you write: > >Brian Fundakowski Feldman wrote: > >> It sounds to me that what you really want are the semantics of a > >> symbolic link and not the semantics of a hard link. Is it just me, > >> or does it seem as if the pathname of the executable being stored as > >> a virtual symlink in procfs as "file" would solve these security > >> problems? > >Mmmmm... I like that... > > I don't, but what I like doesn't matter, it seems -- Warner knows everything. > So I'm sure he knows better than I do the overhead this will impose, and the > impracticality in a general system. > > Unix really isn't set up to carry around 'official pathnames,' due to the > existence of symlinks and other fun stuff. Other systems are set up for this Linux is now one of them.. the file descriptor now (I was told) leads to a name cache entry, which is the name under which it was openned. THat in turn has a pointer to teh directory that it was in...etc. > -- my favourite was EMBOS, by ELXSI -- and there are some _really_ nifty > things you can do, if you have it. (Watchdogs and program-based-access-lists > are my two favourite, the latter allowing you to get rid of SUID/SGID in many > cases. There is a paper available on implementing watchdogs under unix > [4.2bsd, I believe] that discusses some of this. If you're willing to cover > 60-80% of the cases, instead of 95-100%, it's considerably easier.) > > > > 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 Sun Nov 7 3:11:16 1999 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 D19D814E08 for ; Sun, 7 Nov 1999 03:11:11 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 7 Nov 1999 11:11:10 +0000 (GMT) To: "Daniel C. Sobral" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Procfs' pointers to files. In-reply-to: Your message of "Sun, 07 Nov 1999 02:25:55 +0900." <382464A3.F8A3ADA7@newsguy.com> X-Request-Do: Date: Sun, 07 Nov 1999 11:11:10 +0000 From: David Malone Message-ID: <199911071111.aa31599@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Err... I don't see the problem. The permissions of the hardlink will > be different, so the user might be able to see the "code", but won't > be able to run the suid (because the hardlink won't have the suid > bit set). Suid bit is stored in the inode, not the directory entry, so it will be set. I've tested it - try running su in one window, don't type the password, and then run /proc/pid/file and typing the password. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 3:44:47 1999 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 A715E14A2E for ; Sun, 7 Nov 1999 03:44:42 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 7 Nov 1999 11:44:41 +0000 (GMT) To: Sean Eric Fagan Cc: freebsd-hackers@freebsd.org Subject: Re: Procfs' pointers to files. In-reply-to: Your message of "Sat, 06 Nov 1999 11:29:40 PST." <199911061929.LAA06259@kithrup.com> X-Request-Do: Date: Sun, 07 Nov 1999 11:44:41 +0000 From: David Malone Message-ID: <199911071144.aa35139@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >You can make hard links to > > No, you cannot. Yes you can - you just need to make sure the target directory is on the same filesystem as the *original* file. 11:30:gonzo 9% cp /bin/sleep /tmp 11:30:gonzo 10% ls -l /tmp/sleep* -r-xr-xr-x 1 dwmalone wheel 45224 Nov 7 11:30 /tmp/sleep 11:30:gonzo 11% /tmp/sleep 100000 & [1] 636 11:31:gonzo 12% ln /proc/636/file /tmp/sleep2 11:31:gonzo 13% ls -l /tmp/sleep* -r-xr-xr-x 2 dwmalone wheel 45224 Nov 7 11:30 /tmp/sleep -r-xr-xr-x 2 dwmalone wheel 45224 Nov 7 11:30 /tmp/sleep2 11:32:gonzo 14% chmod u+s /tmp/sleep2 11:32:gonzo 15% ls -l /tmp/sleep* /proc/636/file -r-sr-xr-x 2 dwmalone wheel 45224 Nov 7 11:30 /proc/636/file -r-sr-xr-x 2 dwmalone wheel 45224 Nov 7 11:30 /tmp/sleep -r-sr-xr-x 2 dwmalone wheel 45224 Nov 7 11:30 /tmp/sleep2 David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 5: 5:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw-nl4.philips.com (gw-nl4.philips.com [192.68.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 2D22D14F6D for ; Sun, 7 Nov 1999 05:05:05 -0800 (PST) (envelope-from jbackus@plex.nl) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id OAA25935 for ; Sun, 7 Nov 1999 14:05:04 +0100 (MET) (envelope-from jbackus@plex.nl) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma025933; Sun, 7 Nov 99 14:05:04 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with SMTP id OAA20710 for ; Sun, 7 Nov 1999 14:05:04 +0100 (MET) Received: (qmail 48537 invoked from network); 7 Nov 1999 13:05:25 -0000 Received: from nld112-22.ods.origin-it.com (HELO jos.bugworks.com) (172.16.122.31) by hal.mpn.cp.philips.com with SMTP; 7 Nov 1999 13:05:25 -0000 Received: (qmail 3093 invoked by uid 1000); 7 Nov 1999 13:05:50 -0000 Date: Sun, 7 Nov 1999 14:05:50 +0100 From: Jos Backus To: "Daniel C. Sobral" Cc: Jos Backus , Sheldon Hearn , freebsd-hackers@FreeBSD.ORG Subject: Re: ftpd feature: lock file being stored Message-ID: <19991107140550.A2140@jos.bugworks.com> Reply-To: Jos Backus References: <19991105111518.A2328@hal.mpn.cp.philips.com> <7173.941797101@axl.noc.iafrica.com> <19991105113929.B2328@hal.mpn.cp.philips.com> <38253C03.A7036A91@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38253C03.A7036A91@newsguy.com>; from dcs@newsguy.com on Sun, Nov 07, 1999 at 05:44:51PM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 07, 1999 at 05:44:51PM +0900, Daniel C. Sobral wrote: > Actually, use fstat to check against ftpd, and lockf between the > scripts. :-) Good idea :) I think that I'll do just that. Cheers, -- Jos Backus _/ _/_/_/ "Modularity is not a hack." _/ _/ _/ -- D. J. Bernstein _/ _/_/_/ _/ _/ _/ _/ jbackus@plex.nl _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 7:58: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id B77EE14D24 for ; Sun, 7 Nov 1999 07:58:01 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id QAA13824; Sun, 7 Nov 1999 16:57:55 +0100 (CET) (envelope-from des) To: Kevin Day Cc: doconnor@gsoft.com.au (Daniel O'Connor), remy@synx.com (Remy Nonnenmacher), hackers@FreeBSD.ORG Subject: Re: Running unattended (ifo FFS thread) References: <199910280125.UAA81599@celery.dragondata.com> From: Dag-Erling Smorgrav Date: 07 Nov 1999 16:57:54 +0100 In-Reply-To: Kevin Day's message of "Wed, 27 Oct 1999 20:25:06 -0500 (CDT)" Message-ID: Lines: 10 User-Agent: Gnus/5.070097 (Pterodactyl Gnus v0.97) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kevin Day writes: > The problem is that 'fsck -py' ignores the 'p' and will fsck every time, > even if it's unneeded. This takes ages for me. I believe I submitted a PR > with a 'fix' to fsck. 'fsck -p || fsck -y' should do the trick. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 8:17:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id C0A9C14D24 for ; Sun, 7 Nov 1999 08:17:13 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca ([207.96.132.242]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.07.30.00.05.p8) with ESMTP id <0FKU009N3582NW@falla.videotron.net> for hackers@freebsd.org; Sun, 7 Nov 1999 11:16:51 -0500 (EST) Date: Sun, 07 Nov 1999 11:16:56 -0500 From: "Stephane E. Potvin" Subject: ARM support To: hackers@freebsd.org Message-id: <3825A5F8.80A0D6F4@videotron.ca> Organization: IML MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To whoever that may interest, I've now got a nearly working freebsd loader for the NetWinder. It currently only uses the serial console and miss internal hard driver support but work is underway for both these issues. I'm making some progress too in getting world to compile but work in this area is more slower as I've got no way to test what I compile and I'm not that at ease with most of the code. -- Stephane E. Potvin InnoMediaLogic Inc. - http://www.multichassis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 9: 4:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 206C715282 for ; Sun, 7 Nov 1999 09:04:04 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id RAA86320; Sun, 7 Nov 1999 17:05:10 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 7 Nov 1999 17:05:09 +0000 (GMT) From: Doug Rabson To: "Stephane E. Potvin" Cc: hackers@freebsd.org Subject: Re: ARM support In-Reply-To: <3825A5F8.80A0D6F4@videotron.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 7 Nov 1999, Stephane E. Potvin wrote: > To whoever that may interest, I've now got a nearly working freebsd > loader for the NetWinder. It currently only uses the serial console and > miss internal hard driver support but work is underway for both these > issues. > > I'm making some progress too in getting world to compile but work in > this area is more slower as I've got no way to test what I compile and > I'm not that at ease with most of the code. Hey, good work! If you have any questions on porting the kernel, don't hesitate to contact me. I also have a fair knowledge of ARM too, although its a bit dated (the last ARM machine I owned was an ARM3). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 10: 5:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from green.myip.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 6382D150A8 for ; Sun, 7 Nov 1999 10:05:49 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost ([127.0.0.1] ident=green) by green.myip.org with esmtp (Exim 3.02 #1) id 11kU2h-0001G3-00 for hackers@freebsd.org; Sun, 07 Nov 1999 10:15:43 -0500 Date: Sun, 7 Nov 1999 10:15:42 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: hackers@freebsd.org Subject: Re: Procfs' pointers to files. In-Reply-To: <199911070807.AAA01199@kithrup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 7 Nov 1999, Sean Eric Fagan wrote: > I don't, but what I like doesn't matter, it seems -- Warner knows everything. > So I'm sure he knows better than I do the overhead this will impose, and the > impracticality in a general system. > > Unix really isn't set up to carry around 'official pathnames,' due to the > existence of symlinks and other fun stuff. Other systems are set up for this > -- my favourite was EMBOS, by ELXSI -- and there are some _really_ nifty > things you can do, if you have it. (Watchdogs and program-based-access-lists > are my two favourite, the latter allowing you to get rid of SUID/SGID in many > cases. There is a paper available on implementing watchdogs under unix > [4.2bsd, I believe] that discusses some of this. If you're willing to cover > 60-80% of the cases, instead of 95-100%, it's considerably easier.) > The _REALLY_ obvious solution to this is to find the real path on exec() and store the pointer in proc. How is this full of "overhead" and "impractical"? -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 10:10: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from green.myip.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7B56114E52 for ; Sun, 7 Nov 1999 10:05:49 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost ([127.0.0.1] ident=green) by green.myip.org with esmtp (Exim 3.02 #1) id 11kCrK-0000Dg-00; Sat, 06 Nov 1999 15:54:51 -0500 Date: Sat, 6 Nov 1999 15:54:50 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.myip.org To: Warner Losh Cc: "Daniel C. Sobral" , David Malone , freebsd-hackers@FreeBSD.ORG Subject: Re: Procfs' pointers to files. In-Reply-To: <199911062006.NAA00573@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 6 Nov 1999, Warner Losh wrote: > There are ways that the user can see the code to execute it, but not > read it normally. procfs breaches this inability to read the file. > Also, there are many related problems which make a proper fix for this > that is more complicated than removing /proc/xxx/file nearly > impossible. "Proper" here means "A fix which will prevent the > disclosure of a file to unauthorized people which would normally not > be able to read the file." > > I'm convinced that it would be hard to codify all the security checks > needed to access the file originally into a single number which would > allow people that could read the original file to read /proc/xxx/file > and disallow people who couldn't read the file to also be disallowed > from reading /proc/xxx/file. It sounds to me that what you really want are the semantics of a symbolic link and not the semantics of a hard link. Is it just me, or does it seem as if the pathname of the executable being stored as a virtual symlink in procfs as "file" would solve these security problems? -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 11:52:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles527.castles.com [208.214.165.91]) by hub.freebsd.org (Postfix) with ESMTP id A9E0514D76 for ; Sun, 7 Nov 1999 11:52:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA13529; Sun, 7 Nov 1999 11:43:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911071943.LAA13529@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Stephane E. Potvin" Cc: hackers@freebsd.org Subject: Re: ARM support In-reply-to: Your message of "Sun, 07 Nov 1999 11:16:56 EST." <3825A5F8.80A0D6F4@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Nov 1999 11:43:08 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > To whoever that may interest, I've now got a nearly working freebsd > loader for the NetWinder. It currently only uses the serial console and > miss internal hard driver support but work is underway for both these > issues. Cool! Does the NetWinder use OpenFirmware, or some other firmware interface? > I'm making some progress too in getting world to compile but work in > this area is more slower as I've got no way to test what I compile and > I'm not that at ease with most of the code. If you're interested in sharing your work, I have a DNA ('shark') here that was loaned to the Project for just this purpose. I'd be really interested to see your cross-build bits integrated into our tree ASAP. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 12:13:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id 4EFCA14C4A for ; Sun, 7 Nov 1999 12:13:27 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca ([207.96.132.242]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.07.30.00.05.p8) with ESMTP id <0FKU00GDPG4HQZ@field.videotron.net> for hackers@freebsd.org; Sun, 7 Nov 1999 15:12:19 -0500 (EST) Date: Sun, 07 Nov 1999 15:12:23 -0500 From: "Stephane E. Potvin" Subject: Re: ARM support To: Mike Smith Cc: hackers@freebsd.org Message-id: <3825DD27.81742440@videotron.ca> Organization: IML MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en References: <199911071943.LAA13529@dingo.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > To whoever that may interest, I've now got a nearly working freebsd > > loader for the NetWinder. It currently only uses the serial console and > > miss internal hard driver support but work is underway for both these > > issues. > > Cool! Does the NetWinder use OpenFirmware, or some other firmware > interface? Unfortunately no. It uses a stripped down linux kernel as firmware. That's why I switched to work on the bootloader: the darn thing doesn't seems to grok ufs right. It's bad because the disk/video support have to be done from the ground up. Adding support to the Shark/acorn computers will probably be a lot easier. > > I'm making some progress too in getting world to compile but work in > > this area is more slower as I've got no way to test what I compile and > > I'm not that at ease with most of the code. > > If you're interested in sharing your work, I have a DNA ('shark') here > that was loaned to the Project for just this purpose. I'd be really > interested to see your cross-build bits integrated into our tree ASAP. I'd really like this to happens too but right now I think that would be near impossible. binutils 2.9.1 doesn't really support arm/elf so I'm currently using a recent snapshot of binutils (2.9.5) with gcc 2.95.1. I'm using a boatload of very ugly hacks to make this combitation work with current... As soon as the binutils crew releases something more official so that it could be added into the tree I'll be more than happy to send pr's for what I've got so far. Steph -- Stephane E. Potvin InnoMediaLogic Inc. - http://www.multichassis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 13: 5: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id D2A1B14D08 for ; Sun, 7 Nov 1999 13:05:04 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id B6C863E2E; Sun, 7 Nov 1999 22:05:03 +0100 (CET) Date: Sun, 7 Nov 1999 22:05:03 +0100 From: Jesper Skriver To: Dag-Erling Smorgrav Cc: Kevin Day , Daniel O'Connor , Remy Nonnenmacher , hackers@FreeBSD.ORG Subject: Re: Running unattended (ifo FFS thread) Message-ID: <19991107220503.A42362@skriver.dk> References: <199910280125.UAA81599@celery.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from des@flood.ping.uio.no on Sun, Nov 07, 1999 at 04:57:54PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 07, 1999 at 04:57:54PM +0100, Dag-Erling Smorgrav wrote: > Kevin Day writes: > > The problem is that 'fsck -py' ignores the 'p' and will fsck every time, > > even if it's unneeded. This takes ages for me. I believe I submitted a PR > > with a 'fix' to fsck. > > 'fsck -p || fsck -y' should do the trick. What about at rc.conf knob, that make /etc/rc use this instead of the normal fsck -p ?? This could be useful for servers at remote sites. Should I submit a PR with a diff ? /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 16:20:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wcug.wwu.edu (sloth.wcug.wwu.edu [140.160.164.200]) by hub.freebsd.org (Postfix) with SMTP id BE9CE150F8 for ; Sun, 7 Nov 1999 16:20:12 -0800 (PST) (envelope-from tcole@wcug.wwu.edu) Received: (qmail 32188 invoked by uid 1085); 8 Nov 1999 00:20:09 -0000 Date: Sun, 7 Nov 1999 16:20:09 -0800 From: Travis Cole To: freebsd-hackers@freebsd.org Subject: SMP changes from 3.0 to 3.3? Message-ID: <19991107162008.A32120@wcug.wwu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At work we have 18 or so web servers runing FreeBSD 3.0 on daul PIIs. When they see very high loads (~300+) the SMP starts do get confused and things randomly fail. Were there signifigant SMP changes from 3.0-RELEASE to 3.3-RELEASE that may make SMP more stable at high loads? Are their any signifiant SMP changes at all from 3.0-RELEASE to 3.3-RELEASE? Or should I just go try and read the comit logs and see if I can make any sense of this my self? Last time I tried, I didn't get to far :( Thanks much. -- --Travis "Linux is something for Windows haters, BSD is something for Unix lovers" (Heike S., Febr. 98) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 19:36:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id 8A8A814D5C for ; Sun, 7 Nov 1999 19:36:16 -0800 (PST) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id EAA34834; Mon, 8 Nov 1999 04:37:24 +0100 (CET) To: freebsd-hackers@FreeBSD.ORG Subject: SIMPLELOCK_DEBUG and apause Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 08 Nov 1999 04:37:24 +0100 Message-ID: <5lyac9d56z.fsf@assaris.sics.se> Lines: 25 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why trying to debug some locking code of my own I enabled SIMPLELOCK_DEBUG, only to find out that I was getting lots of `simple_unlock: lock not held' in lockmgr -> acquire -> apause. Looking closer at `apause' it seems rather clear that it can cause this. I proposed simple change is below. Comments? /assar --- kern_lock.c.orig Mon Nov 8 03:55:26 1999 +++ kern_lock.c Mon Nov 8 04:24:13 1999 @@ -116,9 +119,11 @@ simple_lock(&lkp->lk_interlock); if ((lkp->lk_flags & flags) == 0) return 0; + simple_unlock(&lkp->lk_interlock); break; } } + simple_lock(&lkp->lk_interlock); } return 1; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 22:32: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 44E691501F for ; Sun, 7 Nov 1999 22:31:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA89627; Sun, 7 Nov 1999 22:31:57 -0800 (PST) (envelope-from dillon) Date: Sun, 7 Nov 1999 22:31:57 -0800 (PST) From: Matthew Dillon Message-Id: <199911080631.WAA89627@apollo.backplane.com> To: John-Mark Gurney Cc: FreeBSD Hackers Subject: Re: writing much slower than reading... References: <19991106013045.13836@hydrogen.fircrest.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :well, I am working on writing a capture program to do 640x480x12bpp@30fps :to a raw disk, but writing to the raw device is SOOO slow... the reason :I say it's slow is the fact that it takes 8 times the system time writing :than reading... : :a bit about the system... k6/2-250, 100mhz system bus, pc100 64meg dimm, :VIA MVP3 chipset (IDE DMA enabled), IBM-DPTA-372730 hard disk, Hauppauge :WinCast/TV Model 61351 B226, 3.3-RELEASE... : :now the hard disk can push and pull around 20meg/sec w/o any problems.. :but when I time the disk I get: :$ time dd if=/dev/rwd0s1g of=/dev/null bs=64k count=2048 :2048+0 records in :2048+0 records out :134217728 bytes transferred in 5.747521 secs (23352281 bytes/sec) : 5.75 real 0.01 user 0.21 sys :$ time dd if=/dev/zero of=/dev/rwd0s1g bs=64k count=2048 :2048+0 records in :2048+0 records out :134217728 bytes transferred in 6.281820 secs (21366057 bytes/sec) : 6.28 real 0.00 user 1.68 sys : :now, why does it cost SOOO much more processing time to write than :read?? are there plans to fix this slow down? is it possible? can't :we just dma write out of userland since we are blocking on the write? : :-- : John-Mark Gurney Voice: +1 408 975 9651 It doesn't necessarily, but your use of dd is causing the numbers to look skewed. It's real simple: when you read from the raw disk into a fixed buffer the system is DMAing directly into the buffer. dd then 'writes' the buffer to /dev/null, which is a NOP. There is no effect on the cpu's L1 and L2 caches because the cpu never reads or copies the data anywhere. When you write to a raw disk with your dd, it is reading a block from /dev/zero into its local buffer which involves a zeroing operation that the read code never had to do, then dd writes the buffer to disk. So the write test is doing an extra scan of the buffer *and* blowing up the cpu's L1 and L2 caches due to that scan while the read test is doing no buffer copies at all so the cpu isn't touching the buffer at all - leaving the L1 and L2 caches pretty much alone. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 7 23:49:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 191DC14A15 for ; Sun, 7 Nov 1999 23:49:52 -0800 (PST) (envelope-from andreasd@ifi.uio.no) Received: from skidbladnir.ifi.uio.no (3034@skidbladnir.ifi.uio.no [129.240.64.76]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id IAA16933 for ; Mon, 8 Nov 1999 08:49:51 +0100 (MET) Received: (from andreasd@localhost) by skidbladnir.ifi.uio.no ; Mon, 8 Nov 1999 08:49:50 +0100 (MET) To: hackers@freebsd.org Subject: Re: Limitations in FreeBSD References: From: Andreas Dobloug Date: 08 Nov 1999 08:49:49 +0100 In-Reply-To: Message-ID: Lines: 7 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon | FreeBSD boxes can handle up to 4 Gigabytes of main memory. Is this true for the Alpha kernels too? -- Andreas Dobloug : email: andreasd@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 0:23:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from funkthat.com (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213]) by hub.freebsd.org (Postfix) with ESMTP id 797821518E for ; Mon, 8 Nov 1999 00:23:46 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by funkthat.com (8.9.1/8.8.7) id AAA13574; Mon, 8 Nov 1999 00:23:29 -0800 (PST) Message-ID: <19991108002329.24851@hydrogen.fircrest.net> Date: Mon, 8 Nov 1999 00:23:29 -0800 From: John-Mark Gurney To: Matthew Dillon Cc: FreeBSD Hackers Subject: Re: writing much slower than reading... References: <19991106013045.13836@hydrogen.fircrest.net> <199911080631.WAA89627@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199911080631.WAA89627@apollo.backplane.com>; from Matthew Dillon on Sun, Nov 07, 1999 at 10:31:57PM -0800 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon scribbled this message on Nov 7: > When you write to a raw disk with your dd, it is reading a block from > /dev/zero into its local buffer which involves a zeroing operation > that the read code never had to do, then dd writes the buffer to disk. thank you! this is exactly what I was looking for... :) I wrote a simple test program that uses a static buffer of 1meg to read and write from... I ran the test to transfer 512megs and their system time is almost equal... I knew it was something really stupid like that... now to find out why the bt848 card can't sustain more than 15fps when I'm writing to the disk... and only can do 7-8fps in 640x480... probably something to do w/ the pci bus getting overloaded or the chipset... -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 0:26:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles554.castles.com [208.214.165.118]) by hub.freebsd.org (Postfix) with ESMTP id 3CD3B1518E for ; Mon, 8 Nov 1999 00:26:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA16940; Mon, 8 Nov 1999 00:17:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911080817.AAA16940@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andreas Dobloug Cc: hackers@freebsd.org Subject: Re: Limitations in FreeBSD In-reply-to: Your message of "08 Nov 1999 08:49:49 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Nov 1999 00:17:47 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * Matthew Dillon > | FreeBSD boxes can handle up to 4 Gigabytes of main memory. > > Is this true for the Alpha kernels too? There are issues with > 1GB of RAM on Alphas at the moment, which may be easier to resolve soon. We have a 4100 with 1GB, which should be upgraded to 1.5 shortly and which will be available for various people to beat on at that point. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 2: 4:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id B6797151C0 for ; Mon, 8 Nov 1999 02:04:19 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p04-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.133]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id TAA05413; Mon, 8 Nov 1999 19:03:16 +0900 (JST) Message-ID: <382689DE.D440B04D@newsguy.com> Date: Mon, 08 Nov 1999 17:29:18 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "Stephane E. Potvin" Cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: ARM support References: <199911071943.LAA13529@dingo.cdrom.com> <3825DD27.81742440@videotron.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Stephane E. Potvin" wrote: > > Unfortunately no. It uses a stripped down linux kernel as firmware. In that case the source code is available, yes? Mmmmm... have you tried ext2fs? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 4:36:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id 2F49814E66; Mon, 8 Nov 1999 04:36:28 -0800 (PST) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id MAA46720; Mon, 8 Nov 1999 12:36:05 GMT (envelope-from geoffb) Date: Mon, 8 Nov 1999 12:36:05 +0000 From: Geoff Buckingham To: Richard Puga Cc: pao-report@clave.gr.jp, freebsd-mobile@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: PCMCIA Chipset Message-ID: <19991108123605.C46518@chuggalug.clues.com> References: <382276A8.D00481BF@maui.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <382276A8.D00481BF@maui.com>; from Richard Puga on Thu, Nov 04, 1999 at 08:18:17PM -1000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 04, 1999 at 08:18:17PM -1000, Richard Puga wrote: > I am having trouble with a PCMCIA chipset > > I have a ISA to PCMCIA adaptor, it is made by ActionTec model no. PC-250 > www.actiontec.com > > the chip on it has the following information on it; > > > D japan > DB6082 > 1992 DATABOOK > 1992 FMI > FUJITSU 1992 > 9412 E57 > > the avalible I/O addresses are > > 200h 240h 280h 2c0h 300h 340h and 380h > > is this controler supported by FreeBSD, PAO maybe? > > if so how do you impliment it in the kernel config. > > Thank you > I have no idea if this will work but try the PAO for 3.3_RELEASE install disks from http://www.jp.freebsd.org/PAO you should be able to see what is detected without installing anything. Failing that their FAQ has the following to say, ther is no explictit reference to ISA cards nore a Fujitsu chipset; The PC Card driver of PAO supports following PC Card controllers: Intel i82365SL (and compatibles) Cirrus Logic PD-6710 Cirrus Logic PD-6720 Cirrus Logic PD-6722 Cirrus Logic PD-6729 (PCI-PCMCIA bridge) Cirrus Logic PD-6730 (PCI-PCMCIA bridge) IBM PCIC (on some ThinkPads) IBM KING O2micro OZ6729 (PCI-PCMCIA bridge) O2micro OZ6730 (PCI-PCMCIA bridge) Ricoh RF5C296 (i82365 compatible) Ricoh RF5C396 Vadem 468 Vadem 469 VLSI 82C146 PAO does not support following PC Card controllers. (If you have laptops with these controller, please write drivers for these controllers for PAO :-). Databook TCIC (on some ancient laptops) Some PCI-CardBus bridges can be used in i82365-compatible mode. Currently it is being tested on following chipsets: Cirrus Logic PD-6832 Texas Instruments PCI-1130 Texas Instruments PCI-1131 Texas Instruments PCI-1220 Texas Instruments PCI-1221 Texas Instruments PCI-1250 Toshiba ToPIC95 Toshiba ToPIC97 Ricoh RL5C465 Ricoh RL5C475 Ricoh RL5C476 Ricoh RL5C478 If your PC Card controller is not supported, please contact me (hosokawa@jp.FreeBSD.org) or BSD-nomads team (bsd-nomads@clave.gr.jp). I need following information to hack the chip: o The name of the PC Card controller of your machine. (e.g. Cirrus Logic 6832). o PCI device ID of PC Card controller (If your PC Card controller is PCI - PC Card bridge or PCI - CardBus bridge). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 4:40:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ncc1701.iml-cti.com (g55-67.citenet.net [207.183.39.67]) by hub.freebsd.org (Postfix) with ESMTP id 3DC5A14E66 for ; Mon, 8 Nov 1999 04:40:09 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from stephanep ([207.139.62.109]) by ncc1701.iml-cti.com (8.9.3/8.9.3) with SMTP id HAA26324; Mon, 8 Nov 1999 07:44:36 -0500 From: "Stephane Potvin" To: "Daniel C. Sobral" Cc: Subject: RE: ARM support Date: Mon, 8 Nov 1999 07:41:15 -0500 Message-ID: <000201bf29e6$8bdb5f90$0100000a@stephanep.bishop> 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 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-reply-to: <382689DE.D440B04D@newsguy.com> Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Daniel C. Sobral [mailto:dcs@newsguy.com] > Sent: Monday, November 08, 1999 3:29 AM > To: Stephane E. Potvin > Cc: Mike Smith; hackers@FreeBSD.ORG > Subject: Re: ARM support > > > "Stephane E. Potvin" wrote: > > > > Unfortunately no. It uses a stripped down linux kernel as firmware. > > In that case the source code is available, yes? I guess so, I didn't tried really hard to find out. Call me lazy but I didn't want to take the chance blowing up the existing firmware and have to program a new one using jtag :) > Mmmmm... have you tried ext2fs? Yes, loading from an ext2fs partition works fine. Well, I tried for the last 10 minutes to find a suitable way to tell in a manner that would not sounds religious that using ext2fs is not really an option to no avail. I guess that my english skills are not that good :-) Thanks for the suggestion though. Steph -- Stephane E. Potvin InnoMediaLogic Inc. - http://www.multichassis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 7:26:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id B02DB14CA9 for ; Mon, 8 Nov 1999 07:26:06 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p16-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.113]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id AAA00642; Tue, 9 Nov 1999 00:25:55 +0900 (JST) Message-ID: <3826EAF5.B0C5EA55@newsguy.com> Date: Tue, 09 Nov 1999 00:23:33 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Stephane Potvin Cc: hackers@freebsd.org Subject: Re: ARM support References: <000201bf29e6$8bdb5f90$0100000a@stephanep.bishop> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephane Potvin wrote: > > > Mmmmm... have you tried ext2fs? > > Yes, loading from an ext2fs partition works fine. Well, I tried for the > last 10 minutes to find a suitable way to tell in a manner that would not > sounds religious that using ext2fs is not really an option to no avail. > I guess that my english skills are not that good :-) > Thanks for the suggestion though. Hehhehe. :-) See, the *only* thing you need on ext2fs is /boot/*. You create a fake root with fully-populated /boot on an ext2fs, and the real root (including the kernel) on another partition. Since *loader* groks ufs, you should be ok. Actually, /kernel, /kernel.old may also reside on ext2fs, as they not used after being loaded by loader. Anyway, as the end result, your system will be running fully ufs once booted. Special care will be needed when installing/upgrading boot stuff, but... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 7:43:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ncc1701.iml-cti.com (g55-67.citenet.net [207.183.39.67]) by hub.freebsd.org (Postfix) with ESMTP id 2727515221 for ; Mon, 8 Nov 1999 07:43:06 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from stephanep ([207.139.62.109]) by ncc1701.iml-cti.com (8.9.3/8.9.3) with SMTP id KAA28106; Mon, 8 Nov 1999 10:45:36 -0500 From: "Stephane Potvin" To: "Daniel C. Sobral" , "Stephane Potvin" Cc: Subject: RE: ARM support Date: Mon, 8 Nov 1999 10:42:16 -0500 Message-ID: <000301bf29ff$d5936830$0100000a@stephanep.bishop> 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 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-reply-to: <3826EAF5.B0C5EA55@newsguy.com> Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Daniel C. Sobral [mailto:dcs@newsguy.com] > Sent: Monday, November 08, 1999 10:24 AM > To: Stephane Potvin > Cc: hackers@freebsd.org > Subject: Re: ARM support > > > Stephane Potvin wrote: > > > > > Mmmmm... have you tried ext2fs? > > > > Yes, loading from an ext2fs partition works fine. Well, I tried for the > > last 10 minutes to find a suitable way to tell in a manner that > would not > > sounds religious that using ext2fs is not really an option to no avail. > > I guess that my english skills are not that good :-) > > Thanks for the suggestion though. > > Hehhehe. :-) > > See, the *only* thing you need on ext2fs is /boot/*. You create a > fake root with fully-populated /boot on an ext2fs, and the real root > (including the kernel) on another partition. Since *loader* groks > ufs, you should be ok. > > Actually, /kernel, /kernel.old may also reside on ext2fs, as they > not used after being loaded by loader. > > Anyway, as the end result, your system will be running fully ufs > once booted. Special care will be needed when installing/upgrading > boot stuff, but... Amen. This will be far less complicated that what I had in mind originally. Thanks for the tip. I'll keep you posted on the developments. Steph -- Stephane E. Potvin InnoMediaLogic Inc. - http://www.multichassis.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 8:58:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id D28C414C99; Mon, 8 Nov 1999 08:58:12 -0800 (PST) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.8.8/8.8.8) with UUCP id TAA03695; Mon, 8 Nov 1999 19:02:58 +0300 (MSK) (envelope-from phantom@scorpion.crimea.ua) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id TAA15238; Mon, 8 Nov 1999 19:51:48 +0300 (MSK) Date: Mon, 8 Nov 1999 19:51:48 +0300 From: Alexey Zelkin To: hackers@FreeBSD.org, hardware@FreeBSD.org Subject: handbook require major update Message-ID: <19991108195148.B15193@scorpion.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, I just looked over 12th chapter of the handbook (PC Hardware compatibility) and found that we _must_ update and add/extend all sub-chapters there. This chapter is mostly based on information submited at 1995. It's very sad! :-( Please, take a look over this chapter and feel free to submit any new sub-chapters, sections, paragraphs or fixes to existent ones as simple text or SGML patches to -doc maillist. Thanks you very much! -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@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 Nov 8 9:43:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles517.castles.com [208.214.165.81]) by hub.freebsd.org (Postfix) with ESMTP id C3BC7150B5 for ; Mon, 8 Nov 1999 09:43:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA19613; Mon, 8 Nov 1999 09:34:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911081734.JAA19613@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Stephane Potvin" Cc: "Daniel C. Sobral" , hackers@freebsd.org Subject: Re: ARM support In-reply-to: Your message of "Mon, 08 Nov 1999 07:41:15 EST." <000201bf29e6$8bdb5f90$0100000a@stephanep.bishop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Nov 1999 09:34:25 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Yes, loading from an ext2fs partition works fine. Well, I tried for the > last 10 minutes to find a suitable way to tell in a manner that would not > sounds religious that using ext2fs is not really an option to no avail. Well, let's be practical. Is there any alternative? If the firmware insists on loading something from an ext2 filesystem, you don't have a lot of choice. So write a tiny boot2 that lives in a tiny ext2 filesystem, and knows how to find a FreeBSD filesystem and the loader. Then you can pretend that the ext2 filesystem isn't there. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 12:55: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 071B815204 for ; Mon, 8 Nov 1999 12:54:55 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.142]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA6EF0 for ; Mon, 8 Nov 1999 21:54:49 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA51588 for hackers@freebsd.org; Mon, 8 Nov 1999 21:42:10 +0100 (CET) (envelope-from asmodai) Date: Mon, 8 Nov 1999 21:42:09 +0100 From: Jeroen Ruigrok/Asmodai To: hackers@freebsd.org Subject: machine/bus.h Message-ID: <19991108214209.A50772@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, machine/bus.h claims, in its comment section, that it supports 8 byte read/writes, but never in the whole file does it declare anything remotely akin to bus_space_read_8(). Any reason why not? The outcome of this answer will determine whether I make a patch to correct the comments or add the missing declararions. -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Pleasure's a sin, and sometimes sin's a pleasure. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 13:18:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 6061114C43; Mon, 8 Nov 1999 13:18:39 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40326>; Tue, 9 Nov 1999 08:12:45 +1100 Content-return: prohibited Date: Tue, 9 Nov 1999 08:18:32 +1100 From: Peter Jeremy Subject: Re: Procfs' pointers to files. To: green@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov9.081245est.40326@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 7 Nov 1999 10:15:42 -0500 (EST), Brian Fundakowski Feldman wrote: >The _REALLY_ obvious solution to this is to find the real path on exec() >and store the pointer in proc. How is this full of "overhead" and >"impractical"? Finding _an_ absolute path on exec() is not too hard (though it's not totally trivial). At worst, it requires knowledge of the process WD and then following a relative path (expanding symlinks along the way). The problems I can see are: - In theory, converting from a relative to absolute pathname can result in a pathname exceeding MAXPATHLEN bytes. - A process may not have the permissions to translate it's CWD into an absolute pathname. (Consider a couple of mode 111 directories). - Either proc would need to grow by MAXPATHLEN, or a suitable external buffer would need to be malloc'd to hold the path. - In the case of jail()d or chroot()d processes, the resultant path would be relative to the jail, not the `normal' filesystem. - The pathname used for the original exec() is not guaranteed to be valid after the exec() - parts of it could be deleted or moved. On Sat, 6 Nov 1999 15:54:50 -0500 (EST), Brian Fundakowski Feldman wrote: > does it seem as if the pathname of the executable being stored as >a virtual symlink in procfs as "file" would solve these security >problems? I'm not convinced that this solves all the security problems, though it does solve most of them. My major concern would be that it would leak information relating to the contents of execute-only directories (which may or may not be important). Maybe, rather than trying to solve the general case, we look at what (valid) uses there are for /proc/xxx/file, and what permissions they need. As far as I can see, the only purposes are to allow a debugger to access the executable and to allow the process to re-exec itself. In particular, I can't see any reason for UIDs other than root or the process itself having any access at all. In the case of non-setuid processes, this means that /proc/xxx/file should be owned by the process UID and the mode should be 500 or 100, depending on whether the UID had read permission to the original executable. Unfortunately, when you take setuid programs into account, it gets far less clear: Reasonable cases could be made for having the owner either the real or effective UID. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 13:40:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1]) by hub.freebsd.org (Postfix) with ESMTP id 339C014F71 for ; Mon, 8 Nov 1999 13:40:42 -0800 (PST) (envelope-from crawdad@gungnir.fnal.gov) Received: from gungnir.fnal.gov (localhost [127.0.0.1]) by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id PAA13649 for ; Mon, 8 Nov 1999 15:40:28 -0600 (CST) Message-Id: <199911082140.PAA13649@gungnir.fnal.gov> To: hackers@freebsd.org From: "Matt Crawford" Subject: Re: FreeBSD at IETF (was: Re: IETF gettogether) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13645.942097228.1@gungnir.fnal.gov> Date: Mon, 08 Nov 1999 15:40:28 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone got the Baystack IETF loaner cards working under FreeBSD yet? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 14:54:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 550FE152CC for ; Mon, 8 Nov 1999 14:54:17 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id PAA15821 for ; Mon, 8 Nov 1999 15:54:13 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id PAA02935; Mon, 8 Nov 1999 15:54:11 -0700 Date: Mon, 8 Nov 1999 15:54:11 -0700 Message-Id: <199911082254.PAA02935@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-hackers@FreeBSD.org Subject: Using non-PIC code in shared libraries? X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What happens when this is done? Can it ever work? How about the reverse, where you link in PIC compiled libraries into static (.a) libraries? Does this work? Assuming it works (in either case) are there any performance hits/advantages to either? My impression from past discussions is that you can't use non-PIC code in shared libraries (it won't work), and that you can use PIC code in static libraries, but you take a performance hit for it... Am I right? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 15:17: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E4367152DC for ; Mon, 8 Nov 1999 15:16:49 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA90521; Mon, 8 Nov 1999 16:16:47 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA13157; Mon, 8 Nov 1999 16:16:09 -0700 (MST) Message-Id: <199911082316.QAA13157@harmony.village.org> To: Jeroen Ruigrok/Asmodai Subject: Re: machine/bus.h Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 08 Nov 1999 21:42:09 +0100." <19991108214209.A50772@daemon.ninth-circle.org> References: <19991108214209.A50772@daemon.ninth-circle.org> Date: Mon, 08 Nov 1999 16:16:09 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991108214209.A50772@daemon.ninth-circle.org> Jeroen Ruigrok/Asmodai writes: : machine/bus.h claims, in its comment section, that it supports 8 byte : read/writes, but never in the whole file does it declare anything : remotely akin to bus_space_read_8(). : : Any reason why not? Because no busses that we support support atomic 8 byte accesses. At least that's my guess. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 15:32:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id 4FBEA14BDA for ; Mon, 8 Nov 1999 15:32:07 -0800 (PST) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.8.8/8.8.8) with UUCP id BAA08040; Tue, 9 Nov 1999 01:34:58 +0300 (MSK) (envelope-from phantom@scorpion.crimea.ua) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id AAA24422; Tue, 9 Nov 1999 00:08:17 +0300 (MSK) Date: Tue, 9 Nov 1999 00:08:17 +0300 From: Alexey Zelkin To: "Daniel C. Sobral" Cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: loader security problem Message-ID: <19991109000817.A23687@scorpion.crimea.ua> References: <19991105222636.B27448@scorpion.crimea.ua> <199911060019.QAA00813@dingo.cdrom.com> <19991107000520.A23479@scorpion.crimea.ua> <3825384E.C6214B61@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <3825384E.C6214B61@newsguy.com> X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, On Sun, Nov 07, 1999 at 05:29:02PM +0900, Daniel C. Sobral wrote: > > IMHO, it would be nice to have password protected loader(8) (like linux lilo) > > or just ACLs for loader(8)'s "more" command (like unavailable for viewing > > files) > > cat >/boot/passwd.4th < Say... does LILO have a scripting language? One my friend is linux-fan. And I know about lilo by his speach :) I even did not try to look to lilo's sources and I can't answer such _complex_ question :) -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@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 Nov 8 17:19:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acutiator.nacamar.de (mail.nacamar.de [194.162.162.200]) by hub.freebsd.org (Postfix) with ESMTP id DDBE11523D for ; Mon, 8 Nov 1999 17:19:09 -0800 (PST) (envelope-from rohrbach@mail.nacamar.de) Received: by acutiator.nacamar.de (Postfix, from userid 499) id 4A5395D6B; Tue, 9 Nov 1999 02:19:08 +0100 (CET) Date: Tue, 9 Nov 1999 02:19:08 +0100 From: "Karsten W. Rohrbach" To: freebsd-hackers@freebsd.org Subject: strange NFS stuff going on... (inpcb=0x0,...) Message-ID: <19991109021907.A99041@nacamar.net> Reply-To: rohrbach@nacamar.net Mail-Followup-To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i X-Arbitrary-Number-Of-The-Day: 42 X-Sender: rohrbach@nacamar.net X-Organisation: Nacamar Data Communications GmbH X-Address: Robert-Bosch-Str. 32, 63303 Dreieich, Germany X-Phone: vox: +49 6103 993 870 fax: +49 6103 993 199 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, i recently migrated our news box (which runs approx. 1MB/s nntp traffic inbound and >2MB/s outbound) to several systems and got the spool onto a vinum volume that spans 6 scsi busses (adaptec 3940UW) each 4 disks (IBM DNES 18GB). theres a private switched interconnect between the reader box and the "fileserver" now and nfs seem to crash on me somehow. nnrpd start to die after a few megabytes transfer and if i do an fstat -vp on one of the nnrpd's i get root@NEWS:black[~]31# fstat -vp 3820 USER CMD PID FD MOUNT INUM MODE SZ|DV R/W news nnrpd 3820 root / 2 drwxr-xr-x 512 r news nnrpd 3820 wd /sp 158720 drwxrwxr-x 923136 r news nnrpd 3820 text / 376 -r-xr-xr-x 90424 r news nnrpd 3820 0* internet stream tcp news nnrpd 3820 1* internet stream tcp news nnrpd 3820 2* internet stream tcp news nnrpd 3820 3* local dgram d4c7f400 <-> d4c7efc0 news nnrpd 3820 4* internet dgram udp d44b1600 news nnrpd 3820 5 /sp 158720 drwxrwxr-x 923136 r news nnrpd 3820 12* local dgram d4c7fe40 example lsof output of one of the dead nnrpd's: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME nnrpd 3820 news rtd VDIR 4,131072 512 2 / nnrpd 3820 news txt VREG 4,131072 90424 376 /home/news/bin/nnrpd nnrpd 3820 news txt VREG 4,131078 63832 182626 /usr/libexec/ld-elf.so.1 nnrpd 3820 news txt VREG 4,131078 7579 39707 /usr/lib/libscrypt.so.2 nnrpd 3820 news txt VREG 4,131078 31855 39805 /usr/lib/libutil.so.2 nnrpd 3820 news txt VREG 4,131078 517727 39742 /usr/lib/libc.so.3 nnrpd 3820 news 0u inet 0t0 TCP can't read inpcb at 0x00000000 nnrpd 3820 news 1u inet 0t0 TCP can't read inpcb at 0x00000000 nnrpd 3820 news 2u inet 0t0 TCP can't read inpcb at 0x00000000 nnrpd 3820 news 3u unix 0xd42353c0 0t0 ->0xd422edc0 nnrpd 3820 news 4u inet 0xd44b1600 0t0 UDP localhost:1276->localhost:1119 nnrpd 3820 news 5r VDIR 130,1 923136 158720 /sp/art/alt/binaries/sounds/mp3 nnrpd 3820 news 12u unix 0xd422e320 0t0 ->(none) system config is as follows: both boxes running freebsd 3.3-RELEASE fileserver backend tyan tomcat ii (i440BX) bios 1.18 p-iii 450 (options I686_CPU, NO_F00F_HACK) 256m sdram (will be 768m sdram/ecc) ahc[0..5] 3x aha-3940uw (options AHC_ALLOW_MEMIO) da0 ibm dnes 9GB uw da[1..24] 24x ibm dnes 18GB uw fxp0 intel etherexpress pro 100+/server (options NMBCLUSTERS=8192) media 100BaseTX mediaopt full-duplex filesystems on vinum w/ softupdates /db stripe, 4disks, 68GB /sp stripe, 20disks, 341GB nfs_server_flags="-u -t -n 16" newsreader frontend asus p2b-s (i440BX) bios 1011 p-iii 450 (options I686_CPU, NO_F00F_HACK) 512mb sdram (will be 1gb sdram/ecc) ahc0 adaptec u2w onboard da0 ibm dnes 9GB u2w fxp[0,1] intel etherexpress pro100+/server (options NMBCLUSTERS=8192) media 100BaseTX mediaopt full-duplex fxp0 -> internet fxp1 -> private storage network 10.0.0.0/24 nfs_client_flags="-n 8" fstab: bucket:/sp /sp nfs \ rw,bg,noatime,-r=1024,-w=1024,intr,-a=3,-d,-t=10 0 0 bucket:/db /db nfs \ rw,bg,noatime,-r=1024,-w=1024,intr,-a=3,-d,-t=10 0 0 the main question: why do those guys hang there? the nnrpd i use is from the inn-1.7.2-insync+actived distribution/patchkit any ideas? as far as i understand it chokes because of nonexistent pcb's that are set 0, but i'm not this deep into nfs anyway... any help appreciated... /k -- > "There is a God, but He drinks" -- Blore http://www.nacamar.de - http://www.nacamar.net - http://www.webmonster.de http://www.apache.de - http://www.quakeforum.de - finger rohrbach@nacamar.net KR433/KR11-RIPE - PGP-KFP = F9 A0 DF 91 74 07 6A 1C 5F 0B E0 6B 4D CD 8C 44 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 17:33: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 6913115345 for ; Mon, 8 Nov 1999 17:33:00 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id UAA04460 for ; Mon, 8 Nov 1999 20:32:59 -0500 (EST) Date: Mon, 8 Nov 1999 19:20:41 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: Use remote debugging on 3.3-Release Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did a little remote debugging with serial cable on 4.0-current a while ago. But now I can not make it work on 3.3-RELEASE. I have used kermit to make sure that the cable connection is good. I also have added necessary kernel options into the configuration file. My questions are: (1) What flag should I use with sio0. FreeBSD-current uses 0x80. What should I use with 3.3-RELEAE? I have tried 0x40. (2) Is there a bug in FreeBSD 3.3-Release that prevents me from doing remote debugging? (3) Are there anything not described in the Online manual that I should pay attention to? Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 17:42:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 54D0A15345 for ; Mon, 8 Nov 1999 17:42:28 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id SAA12087; Mon, 8 Nov 1999 18:42:26 -0700 (MST) (envelope-from ken) Message-Id: <199911090142.SAA12087@panzer.kdm.org> Subject: Re: Use remote debugging on 3.3-Release In-Reply-To: from Zhihui Zhang at "Nov 8, 1999 07:20:41 pm" To: zzhang@cs.binghamton.edu (Zhihui Zhang) Date: Mon, 8 Nov 1999 18:42:26 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zhihui Zhang wrote... > > I did a little remote debugging with serial cable on 4.0-current a while > ago. But now I can not make it work on 3.3-RELEASE. > > I have used kermit to make sure that the cable connection is good. I also > have added necessary kernel options into the configuration file. My > questions are: > > (1) What flag should I use with sio0. FreeBSD-current uses 0x80. What > should I use with 3.3-RELEAE? I have tried 0x40. I use 0x50 with -stable, and 0x80 with -current. Annoying, but it seems to work. (the stable in question isn't a up-to-the-minute version of -stable, though) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 17:51:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id B52DA15365; Mon, 8 Nov 1999 17:51:39 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id UAA16973; Mon, 8 Nov 1999 20:51:38 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Mon, 8 Nov 1999 20:51:38 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Matt Crawford Cc: hackers@freebsd.org, mobile@freebsd.org Subject: Re: FreeBSD at IETF (was: Re: IETF gettogether) In-Reply-To: <199911082140.PAA13649@gungnir.fnal.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not yet -- I'm part way into porting the driver, but my experience with pccard programming and the kernel pccard interface is somewhat dated. I hope to have better news soon--however, I'd welcome better news from someone else :-). Brian Wellington, who sits beside me with a NetBSD machine, comments that he's found the NetBSD driver to have stability problems, so.. Hope to see you on Wednesday at the FreeBSD dinner.. Robert On Mon, 8 Nov 1999, Matt Crawford wrote: > Has anyone got the Baystack IETF loaner cards working under FreeBSD yet? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 18:24: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id B5BD9150D1 for ; Mon, 8 Nov 1999 18:23:48 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 8BA7B1C03; Tue, 9 Nov 1999 10:23:46 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: nate@mt.sri.com (Nate Williams) Cc: freebsd-hackers@FreeBSD.org Subject: Re: Using non-PIC code in shared libraries? In-reply-to: Your message of "Mon, 08 Nov 1999 15:54:11 MST." <199911082254.PAA02935@mt.sri.com> Date: Tue, 09 Nov 1999 10:23:46 +0800 From: Peter Wemm Message-Id: <19991109022346.8BA7B1C03@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote: > What happens when this is done? Can it ever work? > > How about the reverse, where you link in PIC compiled libraries into > static (.a) libraries? Does this work? > > Assuming it works (in either case) are there any performance > hits/advantages to either? > > My impression from past discussions is that you can't use non-PIC code > in shared libraries (it won't work), and that you can use PIC code in > static libraries, but you take a performance hit for it... > > Am I right? You *can* use non-PIC for shared libraries, but the resulting code requires text relocations at runtime which cause copy-on-write faults and kill any shareability. This might be acceptable if you are using .so's for single-process plug-ins or something, but generally you wouldn't want it for libc (for example. :-). Of course, getting ld-elf.so and ld(1) to be quiet about it is another thing altogether... Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 19:54:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fgwmail2.fujitsu.co.jp (fgwmail2.fujitsu.co.jp [192.51.44.32]) by hub.freebsd.org (Postfix) with ESMTP id D9CE114E54; Mon, 8 Nov 1999 19:54:06 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail2.fujitsu.co.jp (8.9.3/3.7W-MX9910-Fujitsu Gateway) id MAA28010; Tue, 9 Nov 1999 12:54:02 +0900 (JST) Received: from chisato.nd.net.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-9910-Fujitsu Domain Master) id MAA11458; Tue, 9 Nov 1999 12:54:01 +0900 (JST) Received: from localhost (dhcp7186.nd.net.fujitsu.co.jp [10.18.7.186]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id MAA22597; Tue, 9 Nov 1999 12:54:00 +0900 (JST) To: freebsd-hackers@freebsd.org, freebsd-security@FreeBSD.ORG Subject: Should jail treat ip-number? X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991109125445E.shin@nd.net.fujitsu.co.jp> Date: Tue, 09 Nov 1999 12:54:45 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 30 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have some concern about jail, and would like to discuss them. Currentlly jail set an ip-number and let prisoned processes only to bind it. My concerns are, (1)When IPv6 is added to the system, more general id would be desirable. (2)What is the goal of the restriction? If physical level access protection is wanted, then specifing interface name is more general and certain way of achieving it. (Because when that ip-number is replaced to another network interface, then the restriction also will move on it) If some virtual network level protection is wanted, then specifying ip-number is suitable, but I think more general id should be used such as a pointer to a sockaddr. I think kernel change will not so much for any above addition or changes, but there will be some backword compatibility issue for API. (some member addition to the jail structure, and jail command extensions) Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 22: 5:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D9E9814A1F; Mon, 8 Nov 1999 22:05:33 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id HAA21884; Tue, 9 Nov 1999 07:05:17 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Yoshinobu Inoue Cc: freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? In-reply-to: Your message of "Tue, 09 Nov 1999 12:54:45 +0900." <19991109125445E.shin@nd.net.fujitsu.co.jp> Date: Tue, 09 Nov 1999 07:05:17 +0100 Message-ID: <21882.942127517@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991109125445E.shin@nd.net.fujitsu.co.jp>, Yoshinobu Inoue writes: >Hello, > >I have some concern about jail, and would like to discuss them. > >Currentlly jail set an ip-number and let prisoned processes >only to bind it. >My concerns are, > >(1)When IPv6 is added to the system, more general id would be > desirable. I agree, *IF* IPv6 ever becomes a reality, we will look at this. >(2)What is the goal of the restriction? To isolate people in the jail from the "real" machine and from other jails. > If physical level access protection is wanted, it isn't. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 8 23:53:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 1270B14D51; Mon, 8 Nov 1999 23:53:23 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id JAA89881; Tue, 9 Nov 1999 09:52:46 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199911090752.JAA89881@zibbi.mikom.csir.co.za> Subject: Re: Should jail treat ip-number? In-Reply-To: <21882.942127517@critter.freebsd.dk> from Poul-Henning Kamp at "Nov 9, 1999 07:05:17 am" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Tue, 9 Nov 1999 09:52:45 +0200 (SAT) Cc: shin@nd.net.fujitsu.co.jp (Yoshinobu Inoue), freebsd-hackers@FreeBSD.ORG, freebsd-security@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 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > >I have some concern about jail, and would like to discuss them. > > > >Currentlly jail set an ip-number and let prisoned processes > >only to bind it. > >My concerns are, > > > >(1)When IPv6 is added to the system, more general id would be > > desirable. > > I agree, *IF* IPv6 ever becomes a reality, we will look at this. So when will you consider that it became a reality? :-) Or am I just dreaming that some operating systems and routers ship with IPv6 and that IANA, ARIN, APNIC and RIPE are dishing out IPv6 addresses and that we are in the process of getting Kame integrated into FreeBSD? :-) John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 0: 4:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 1B43714DB2; Tue, 9 Nov 1999 00:04:47 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA22240; Tue, 9 Nov 1999 09:03:53 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Hay Cc: shin@nd.net.fujitsu.co.jp (Yoshinobu Inoue), freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? In-reply-to: Your message of "Sat, 09 Nov 1999 09:52:45 +0200." <199911090752.JAA89881@zibbi.mikom.csir.co.za> Date: Tue, 09 Nov 1999 09:03:53 +0100 Message-ID: <22238.942134633@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911090752.JAA89881@zibbi.mikom.csir.co.za>, John Hay writes: >> >My concerns are, >> > >> >(1)When IPv6 is added to the system, more general id would be >> > desirable. >> >> I agree, *IF* IPv6 ever becomes a reality, we will look at this. > >So when will you consider that it became a reality? :-) Or am I just >dreaming that some operating systems and routers ship with IPv6 and >that IANA, ARIN, APNIC and RIPE are dishing out IPv6 addresses and >that we are in the process of getting Kame integrated into FreeBSD? :-) Once I have 50% or more of my users using IPv6 I'll consider it a reality. So far IPv6 has gotten no futher than OSI ever did. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 0:25:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id DEED014DB2; Tue, 9 Nov 1999 00:25:06 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id KAA90295; Tue, 9 Nov 1999 10:24:28 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199911090824.KAA90295@zibbi.mikom.csir.co.za> Subject: Re: Should jail treat ip-number? In-Reply-To: <22238.942134633@critter.freebsd.dk> from Poul-Henning Kamp at "Nov 9, 1999 09:03:53 am" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Tue, 9 Nov 1999 10:24:28 +0200 (SAT) Cc: jhay@mikom.csir.co.za (John Hay), shin@nd.net.fujitsu.co.jp (Yoshinobu Inoue), freebsd-hackers@FreeBSD.ORG, freebsd-security@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 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> >My concerns are, > >> > > >> >(1)When IPv6 is added to the system, more general id would be > >> > desirable. > >> > >> I agree, *IF* IPv6 ever becomes a reality, we will look at this. > > > >So when will you consider that it became a reality? :-) Or am I just > >dreaming that some operating systems and routers ship with IPv6 and > >that IANA, ARIN, APNIC and RIPE are dishing out IPv6 addresses and > >that we are in the process of getting Kame integrated into FreeBSD? :-) > > Once I have 50% or more of my users using IPv6 I'll consider it a > reality. hehehe, but your users will not move to IPv6, because they will say: "We are used to being able to use jail on IPv4 and you say we must wait until there is more than 50% of us using IPv6 before we will get jail for IPv6?". :-) And we can substitute whatever functionality for jail. If we want people to even think of moving to IPv6 we will have to make as much of FreeBSD's functionality work on there as possible. > > So far IPv6 has gotten no futher than OSI ever did. I think I was lucky to have mostly been screened from OSI, so I can't really compare them. IPv6 seem quitealive to me though. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 0:30:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 7D67F14C22; Tue, 9 Nov 1999 00:30:35 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA22400; Tue, 9 Nov 1999 09:29:12 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Hay Cc: shin@nd.net.fujitsu.co.jp (Yoshinobu Inoue), freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? In-reply-to: Your message of "Sat, 09 Nov 1999 10:24:28 +0200." <199911090824.KAA90295@zibbi.mikom.csir.co.za> Date: Tue, 09 Nov 1999 09:29:11 +0100 Message-ID: <22398.942136151@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911090824.KAA90295@zibbi.mikom.csir.co.za>, John Hay writes: >If we want >people to even think of moving to IPv6 we will have to make as much >of FreeBSD's functionality work on there as possible. I personally do not see IPv6 as being desirable at this time. It suffers from second systems syndrome and doesn't provide any benefit for the end-user so there is no incentive for users to upgrade. >> So far IPv6 has gotten no futher than OSI ever did. > >I think I was lucky to have mostly been screened from OSI, so I can't >really compare them. IPv6 seem quitealive to me though. Ohh, OSI was quite a live for a long time as well, until the government funded life-support was cut, then it evaporated overnight. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 1:20:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 5000114EDD for ; Tue, 9 Nov 1999 01:20:24 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA90755; Tue, 9 Nov 1999 09:21:34 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 9 Nov 1999 09:21:34 +0000 (GMT) From: Doug Rabson To: Mike Smith Cc: Andreas Dobloug , hackers@freebsd.org Subject: Re: Limitations in FreeBSD In-Reply-To: <199911080817.AAA16940@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 8 Nov 1999, Mike Smith wrote: > > * Matthew Dillon > > | FreeBSD boxes can handle up to 4 Gigabytes of main memory. > > > > Is this true for the Alpha kernels too? > > There are issues with > 1GB of RAM on Alphas at the moment, which may > be easier to resolve soon. We have a 4100 with 1GB, which should be > upgraded to 1.5 shortly and which will be available for various people > to beat on at that point. As a special case, we support xp1000 and ds20 class alphas with upto 2G of memory (not actually tested). The real fix which will allow essentially unbounded memory size (dependant on hardware limits) will happen on the 4100. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 1:23:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 61C6814EA7 for ; Tue, 9 Nov 1999 01:23:30 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA90760; Tue, 9 Nov 1999 09:24:43 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 9 Nov 1999 09:24:43 +0000 (GMT) From: Doug Rabson To: "Daniel C. Sobral" Cc: "Stephane E. Potvin" , Mike Smith , hackers@freebsd.org Subject: Re: ARM support In-Reply-To: <382689DE.D440B04D@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 8 Nov 1999, Daniel C. Sobral wrote: > "Stephane E. Potvin" wrote: > > > > Unfortunately no. It uses a stripped down linux kernel as firmware. > > In that case the source code is available, yes? > > Mmmmm... have you tried ext2fs? Doesn't the netwinder support netbooting? If so, that is certainly the best environment for kernel porting. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 1:52: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id 573F514C3F for ; Tue, 9 Nov 1999 01:51:49 -0800 (PST) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id KAA08315; Tue, 9 Nov 1999 10:52:36 +0100 (CET) To: nate@mt.sri.com (Nate Williams) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Using non-PIC code in shared libraries? References: <199911082254.PAA02935@mt.sri.com> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 09 Nov 1999 10:52:35 +0100 In-Reply-To: Nate Williams's message of "Mon, 8 Nov 1999 15:54:11 -0700" Message-ID: <5l9048gffg.fsf@assaris.sics.se> Lines: 8 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams writes: > How about the reverse, where you link in PIC compiled libraries into > static (.a) libraries? Does this work? Sure. Look at how lib${LIB}_pic.a is done i . PIC-code is less efficient than non-PIC code. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 4: 5:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id B79DD14FFF for ; Tue, 9 Nov 1999 04:05:26 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 58332 invoked by uid 1001); 9 Nov 1999 12:05:25 +0000 (GMT) To: jhay@mikom.csir.co.za Cc: phk@critter.freebsd.dk, shin@nd.net.fujitsu.co.jp, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? From: sthaug@nethelp.no In-Reply-To: Your message of "Tue, 9 Nov 1999 09:52:45 +0200 (SAT)" References: <199911090752.JAA89881@zibbi.mikom.csir.co.za> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 09 Nov 1999 13:05:25 +0100 Message-ID: <58330.942149125@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I agree, *IF* IPv6 ever becomes a reality, we will look at this. > > So when will you consider that it became a reality? :-) Or am I just > dreaming that some operating systems and routers ship with IPv6 and > that IANA, ARIN, APNIC and RIPE are dishing out IPv6 addresses and > that we are in the process of getting Kame integrated into FreeBSD? :-) When there are several Internet Exchange points with routers using non-tunneled IPv6, exchanging significant traffic? Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 5:29: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from moo.sysabend.org (moo.sysabend.org [209.0.55.68]) by hub.freebsd.org (Postfix) with ESMTP id 65E2B14FD9 for ; Tue, 9 Nov 1999 05:28:58 -0800 (PST) (envelope-from ragnar@sysabend.org) Received: by moo.sysabend.org (Postfix, from userid 1004) id BD889753F; Tue, 9 Nov 1999 05:29:51 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id B84651D75; Tue, 9 Nov 1999 05:29:51 -0800 (PST) Date: Tue, 9 Nov 1999 05:29:51 -0800 (PST) From: Jamie Bowden To: Poul-Henning Kamp Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Should jail treat ip-number? In-Reply-To: <21882.942127517@critter.freebsd.dk> Message-ID: Approved: yep X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -security stripped On Tue, 9 Nov 1999, Poul-Henning Kamp wrote: :In message <19991109125445E.shin@nd.net.fujitsu.co.jp>, Yoshinobu Inoue writes: :>(2)What is the goal of the restriction? :To isolate people in the jail from the "real" machine and from :other jails. What does jail do that chroot doesn't? I've seen several discussions on jail on -hackers, but no explanation of why it was implemented, or how it's different from chroot. Jamie Bowden -- If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 5:41:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 6757914FD9 for ; Tue, 9 Nov 1999 05:41:25 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id OAA23739; Tue, 9 Nov 1999 14:41:04 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Jamie Bowden Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Should jail treat ip-number? In-reply-to: Your message of "Tue, 09 Nov 1999 05:29:51 PST." Date: Tue, 09 Nov 1999 14:41:04 +0100 Message-ID: <23737.942154864@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Jamie Bowden writes: > >-security stripped > >On Tue, 9 Nov 1999, Poul-Henning Kamp wrote: > >:In message <19991109125445E.shin@nd.net.fujitsu.co.jp>, Yoshinobu Inoue writes: > >:>(2)What is the goal of the restriction? > >:To isolate people in the jail from the "real" machine and from >:other jails. > >What does jail do that chroot doesn't? I've seen several discussions on >jail on -hackers, but no explanation of why it was implemented, or how >it's different from chroot. 1. All tcp/ip forced to use a particular IP#. This allows you to have several inetd/sendmail/apache running, one per jail. 2. Many things which root can normally do cannot be done if root is jailed. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 7: 5:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id B771B14D7F for ; Tue, 9 Nov 1999 07:05:17 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id KAA28385 for ; Tue, 9 Nov 1999 10:05:15 -0500 (EST) Date: Tue, 9 Nov 1999 08:52:58 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: How to use gdb to catch a panic Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have set up an environment of remote serial debugging on FreeBSD 3.3-Release. I have a program that whenever it runs the kernel panics. Is there any way I can use remote serial debugging to trace this panic process instead of examining a dead kernel (i.e., coredump)? Or, is there any way I can use to drop the debugged kernel to debugger mode whenever it runs a certain piece of code? Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 7:56: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22]) by hub.freebsd.org (Postfix) with ESMTP id D7D8314DDB; Tue, 9 Nov 1999 07:55:54 -0800 (PST) (envelope-from bmcgover@bmcgover-pc.cisco.com) Received: from bmcgover-pc.cisco.com (root@bmcgover-pc.cisco.com [171.69.104.147]) by tornado.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA19025; Tue, 9 Nov 1999 10:55:52 -0500 (EST) Received: from bmcgover-pc.cisco.com (bmcgover@localhost.pa.dtd.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.9.3/8.9.3) with ESMTP id KAA01889; Tue, 9 Nov 1999 10:55:52 -0500 (EST) (envelope-from bmcgover@bmcgover-pc.cisco.com) Message-Id: <199911091555.KAA01889@bmcgover-pc.cisco.com> To: hackers@freebsd.org, peter@freebsd.org Subject: How does sio handle full clists? Date: Tue, 09 Nov 1999 10:55:52 -0500 From: Brian McGovern Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been digging around in the sio driver, trying to find out how it handles receive interrupts when the clists are full. What I think I found (which is why I'm asking) is that if an RX interrupt occurs, and the clists are full and the driver can't offload all of the data from the UART, it disables the interrupts. I assume that at some later point (I haven't quite nailed this down), interrupts get enabled again, which will generate a fresh interrupt from the data that is still stored on the UART. I guess I'm looking for confirmation of this, and, if I'm way off, maybe a quick explanatio of what _really_ happens. I'm looking at trying to reuse the behavior elsewhere, so I want a good understanding of the process before I get myself in to too much trouble. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 8: 2:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id D77F915332 for ; Tue, 9 Nov 1999 08:02:14 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id LAA29169; Tue, 9 Nov 1999 11:02:01 -0500 (EST) Date: Tue, 9 Nov 1999 09:49:43 -0500 (EST) From: Zhihui Zhang To: Greg Lehey Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How to use gdb to catch a panic In-Reply-To: <19991109103938.63558@mojave.sitaranetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 9 Nov 1999, Greg Lehey wrote: > On Tuesday, 9 November 1999 at 8:52:58 -0500, Zhihui Zhang wrote: > > > > I have set up an environment of remote serial debugging on FreeBSD > > 3.3-Release. I have a program that whenever it runs the kernel panics. > > Is there any way I can use remote serial debugging to trace this panic > > process instead of examining a dead kernel (i.e., coredump)? > > Yes. > > > Or, is there any way I can use to drop the debugged kernel to debugger > > mode whenever it runs a certain piece of code? > > Yes. That's what breakpoints are for. If you set a breakpoint on > panic, you'll go into the debugger. But you don't need that, since > you go into the debugger on panic anyway. > > If you're expecting a breakpoint or panic, and you want to do it in > gdb as opposed to ddb, set gdb mode ahead of time. This is also > useful for debugging ddb :-) > Thanks for your reply. What confuses me is that when I use commands "gdb" (enter remote protocol mode) and "step" on the target machine, the debugging machine takes control (it executes "target remote /dev/cuaa1"). In this case, how can I run anything on the target machine to trigger a panic? How to set gdb mode ahead of time? -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 9: 2:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 3BD511503B for ; Tue, 9 Nov 1999 09:02:08 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id MAA04006; Tue, 9 Nov 1999 12:02:01 -0500 (EST) Date: Tue, 9 Nov 1999 10:49:41 -0500 (EST) From: Zhihui Zhang To: Greg Lehey Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How to use gdb to catch a panic In-Reply-To: <19991109103938.63558@mojave.sitaranetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 9 Nov 1999, Greg Lehey wrote: > On Tuesday, 9 November 1999 at 8:52:58 -0500, Zhihui Zhang wrote: > > > > I have set up an environment of remote serial debugging on FreeBSD > > 3.3-Release. I have a program that whenever it runs the kernel panics. > > Is there any way I can use remote serial debugging to trace this panic > > process instead of examining a dead kernel (i.e., coredump)? > > Yes. > > > Or, is there any way I can use to drop the debugged kernel to debugger > > mode whenever it runs a certain piece of code? > > Yes. That's what breakpoints are for. If you set a breakpoint on > panic, you'll go into the debugger. But you don't need that, since > you go into the debugger on panic anyway. > > If you're expecting a breakpoint or panic, and you want to do it in > gdb as opposed to ddb, set gdb mode ahead of time. This is also > useful for debugging ddb :-) Thanks for your reply. What confuses me is that when I use commands "gdb" (enter remote protocol mode) and "step" on the target machine, the debugging machine takes control (it executes "target remote /dev/cuaa1"). In this case, how can I run anything on the target machine to trigger a panic? How to set gdb mode ahead of time? -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 9:28:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fgwmail3.fujitsu.co.jp (fgwmail3.fujitsu.co.jp [192.51.44.33]) by hub.freebsd.org (Postfix) with ESMTP id 455A21509B; Tue, 9 Nov 1999 09:28:41 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail3.fujitsu.co.jp (8.9.3/3.7W-MX9910-Fujitsu Gateway) id CAA12659; Wed, 10 Nov 1999 02:28:07 +0900 (JST) Received: from incapgw.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-9910-Fujitsu Domain Master) id CAA21948; Wed, 10 Nov 1999 02:28:06 +0900 (JST) Received: from localhost ([192.168.245.44]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9910) id CAA29305; Wed, 10 Nov 1999 02:28:04 +0900 (JST) To: phk@critter.freebsd.dk Cc: jhay@mikom.csir.co.za, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? In-Reply-To: <22398.942136151@critter.freebsd.dk> References: <199911090824.KAA90295@zibbi.mikom.csir.co.za> <22398.942136151@critter.freebsd.dk> <22238.942134633@critter.freebsd.dk> <23737.942154864@critter.freebsd.dk> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991110022852N.shin@nd.net.fujitsu.co.jp> Date: Wed, 10 Nov 1999 02:28:52 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 47 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> I agree, *IF* IPv6 ever becomes a reality, we will look at this. Actually I just started to import KAME into freebsd-current, and found jail code in kernel pcb part. > >If we want > >people to even think of moving to IPv6 we will have to make as much > >of FreeBSD's functionality work on there as possible. Just from same reason, I would like to make IPv6 available also for jail functionality. > I personally do not see IPv6 as being desirable at this time. > > It suffers from second systems syndrome and doesn't provide any > benefit for the end-user so there is no incentive for users to > upgrade. But there is also some people like me who think IPv6 give several benefit for the end-user that IPv4 can't give. Then do you think even such people should not update jail to support IPv6? > >:>(2)What is the goal of the restriction? > > > >:To isolate people in the jail from the "real" machine and from > >:other jails. > > > 1. All tcp/ip forced to use a particular IP#. This allows you to have > several inetd/sendmail/apache running, one per jail. My imagination was poor, and thanks for your explanation. Now I have a new concern and comment. (1)It seems to me that once an IP# is specified for a jail, then that IP# should not be re-specified for another jail. Is this true? (2)If (1) is true, then number of jail is restricted to the number of IP address assigned to that machine. Then IPv6 support for jail should be very good thing, because extremely many IP addresses become available for a machine with IPv6. (which is not with IPv4) Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 9:38:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B147414C58; Tue, 9 Nov 1999 09:38:24 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA24339; Tue, 9 Nov 1999 18:37:33 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Yoshinobu Inoue Cc: jhay@mikom.csir.co.za, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? In-reply-to: Your message of "Wed, 10 Nov 1999 02:28:52 +0900." <19991110022852N.shin@nd.net.fujitsu.co.jp> Date: Tue, 09 Nov 1999 18:37:32 +0100 Message-ID: <24337.942169052@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991110022852N.shin@nd.net.fujitsu.co.jp>, Yoshinobu Inoue writes: >(1)It seems to me that once an IP# is specified for a jail, > then that IP# should not be re-specified for another jail. > Is this true? Generally yes, although nothing in the code tries to (nor should it try to) enforce it. >(2)If (1) is true, then number of jail is restricted to the > number of IP address assigned to that machine. > Then IPv6 support for jail should be very good thing, > because extremely many IP addresses become available for > a machine with IPv6. (which is not with IPv4) I'm not against adding IPv6 functionality to jail(2), my point is merely that until somebody who has sufficient time & ability to fiddle with it does it, it's not going to happen. The usual rule applies: "Great idea, why don't you send me patches which does this ?" -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 9:45: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 40D59150BB for ; Tue, 9 Nov 1999 09:44:41 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Received: from mojave.sitaranetworks.com ([199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id EAA11466 for ; Wed, 10 Nov 1999 04:14:35 +1030 (CST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991109103938.63558@mojave.sitaranetworks.com> Date: Tue, 9 Nov 1999 10:39:38 -0500 From: Greg Lehey To: Zhihui Zhang , freebsd-hackers@FreeBSD.ORG Subject: Re: How to use gdb to catch a panic Reply-To: Greg Lehey References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Zhihui Zhang on Tue, Nov 09, 1999 at 08:52:58AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 9 November 1999 at 8:52:58 -0500, Zhihui Zhang wrote: > > I have set up an environment of remote serial debugging on FreeBSD > 3.3-Release. I have a program that whenever it runs the kernel panics. > Is there any way I can use remote serial debugging to trace this panic > process instead of examining a dead kernel (i.e., coredump)? Yes. > Or, is there any way I can use to drop the debugged kernel to debugger > mode whenever it runs a certain piece of code? Yes. That's what breakpoints are for. If you set a breakpoint on panic, you'll go into the debugger. But you don't need that, since you go into the debugger on panic anyway. If you're expecting a breakpoint or panic, and you want to do it in gdb as opposed to ddb, set gdb mode ahead of time. This is also useful for debugging ddb :-) Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 9:58:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from poboxer.pobox.com (ferg5200-2-75.cpinternet.com [208.149.16.75]) by hub.freebsd.org (Postfix) with ESMTP id 8656114C58 for ; Tue, 9 Nov 1999 09:58:21 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id LAA39990; Tue, 9 Nov 1999 11:58:24 -0600 (CST) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 9 Nov 1999 11:58:23 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: jeremyp@gsmx07.alcatel.com.au Cc: hackers@freebsd.org Subject: Re: Procfs' pointers to files. X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14376.24690.546166.953937@avalon.east> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : Unfortunately, when you take setuid programs into account, it gets : far less clear: Reasonable cases could be made for having the owner : either the real or effective UID. The case for effective seems quite clear to me, but I can't see the case for real UID. What is it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 9:58:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 3C7F91531A; Tue, 9 Nov 1999 09:58:30 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m4.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX9910-Fujitsu Gateway) id CAA29762; Wed, 10 Nov 1999 02:58:08 +0900 (JST) Received: from incapgw.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-9910-Fujitsu Domain Master) id CAA22146; Wed, 10 Nov 1999 02:58:07 +0900 (JST) Received: from localhost ([192.168.245.90]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9910) id CAA29933; Wed, 10 Nov 1999 02:58:06 +0900 (JST) To: phk@critter.freebsd.dk Cc: jhay@mikom.csir.co.za, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? In-Reply-To: <24337.942169052@critter.freebsd.dk> References: <19991110022852N.shin@nd.net.fujitsu.co.jp> <24337.942169052@critter.freebsd.dk> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991110025853X.shin@nd.net.fujitsu.co.jp> Date: Wed, 10 Nov 1999 02:58:53 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 15 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not against adding IPv6 functionality to jail(2), my point is > merely that until somebody who has sufficient time & ability to > fiddle with it does it, it's not going to happen. > > The usual rule applies: > > "Great idea, why don't you send me patches which does this ?" OK, then I'll try making patches and send you. My current Idea is that adding a new member, a pointer to sockaddr to the jail structure, and leave current ip_number member for backward compatibility. (Also with associated changes in kernel and the jail command) Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 10: 7:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id BF80B15155 for ; Tue, 9 Nov 1999 10:07:51 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA02252; Tue, 9 Nov 1999 10:07:48 -0800 (PST) (envelope-from dillon) Date: Tue, 9 Nov 1999 10:07:48 -0800 (PST) From: Matthew Dillon Message-Id: <199911091807.KAA02252@apollo.backplane.com> To: "Karsten W. Rohrbach" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: strange NFS stuff going on... (inpcb=0x0,...) References: <19991109021907.A99041@nacamar.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG lsof is obviously having trouble interpreting the data from the kernel. You could try recompiling lsof, but if it produces the same junk you will just have to ignore it. I don't particularly see anything related to NFS in the information you've presented so far. I recommend using more conventional programs such as 'ktrace', 'ps axl', and 'netstat -in | fgrep tcp' to try to figure out why your nnrpd's are having problems. Considering the migration you just went through there are many potential sources to the problems you are having. -Matt Matthew Dillon : :hi, i recently migrated our news box (which runs approx. 1MB/s nntp :traffic inbound and >2MB/s outbound) to several systems and got the :spool onto a vinum volume that spans 6 scsi busses (adaptec 3940UW) each :4 disks (IBM DNES 18GB). theres a private switched interconnect between :the reader box and the "fileserver" now and nfs seem to crash on me :somehow. nnrpd start to die after a few megabytes transfer and if i do :an fstat -vp on one of the nnrpd's i get :root@NEWS:black[~]31# fstat -vp 3820 :USER CMD PID FD MOUNT INUM MODE SZ|DV R/W :news nnrpd 3820 root / 2 drwxr-xr-x 512 r :news nnrpd 3820 wd /sp 158720 drwxrwxr-x 923136 r :news nnrpd 3820 text / 376 -r-xr-xr-x 90424 r :news nnrpd 3820 0* internet stream tcp :news nnrpd 3820 1* internet stream tcp :news nnrpd 3820 2* internet stream tcp :news nnrpd 3820 3* local dgram d4c7f400 <-> d4c7efc0 :news nnrpd 3820 4* internet dgram udp d44b1600 :news nnrpd 3820 5 /sp 158720 drwxrwxr-x 923136 r :news nnrpd 3820 12* local dgram d4c7fe40 : :example lsof output of one of the dead nnrpd's: :COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME :nnrpd 3820 news rtd VDIR 4,131072 512 2 / :nnrpd 3820 news txt VREG 4,131072 90424 376 /home/news/bin/nnrpd :nnrpd 3820 news txt VREG 4,131078 63832 182626 /usr/libexec/ld-elf.so.1 :nnrpd 3820 news txt VREG 4,131078 7579 39707 /usr/lib/libscrypt.so.2 :nnrpd 3820 news txt VREG 4,131078 31855 39805 /usr/lib/libutil.so.2 :nnrpd 3820 news txt VREG 4,131078 517727 39742 /usr/lib/libc.so.3 :nnrpd 3820 news 0u inet 0t0 TCP can't read inpcb at 0x00000000 :nnrpd 3820 news 1u inet 0t0 TCP can't read inpcb at 0x00000000 :nnrpd 3820 news 2u inet 0t0 TCP can't read inpcb at 0x00000000 :nnrpd 3820 news 3u unix 0xd42353c0 0t0 ->0xd422edc0 :nnrpd 3820 news 4u inet 0xd44b1600 0t0 UDP localhost:1276->localhost:1119 :nnrpd 3820 news 5r VDIR 130,1 923136 158720 /sp/art/alt/binaries/sounds/mp3 :nnrpd 3820 news 12u unix 0xd422e320 0t0 ->(none) : :system config is as follows: :both boxes running freebsd 3.3-RELEASE :fileserver backend : tyan tomcat ii (i440BX) bios 1.18 : p-iii 450 (options I686_CPU, NO_F00F_HACK) : 256m sdram (will be 768m sdram/ecc) : ahc[0..5] 3x aha-3940uw (options AHC_ALLOW_MEMIO) : da0 ibm dnes 9GB uw : da[1..24] 24x ibm dnes 18GB uw : fxp0 intel etherexpress pro 100+/server (options NMBCLUSTERS=8192) : media 100BaseTX mediaopt full-duplex : filesystems on vinum w/ softupdates : /db stripe, 4disks, 68GB : /sp stripe, 20disks, 341GB : nfs_server_flags="-u -t -n 16" :newsreader frontend : asus p2b-s (i440BX) bios 1011 : p-iii 450 (options I686_CPU, NO_F00F_HACK) : 512mb sdram (will be 1gb sdram/ecc) : ahc0 adaptec u2w onboard : da0 ibm dnes 9GB u2w : fxp[0,1] intel etherexpress pro100+/server (options NMBCLUSTERS=8192) : media 100BaseTX mediaopt full-duplex : fxp0 -> internet : fxp1 -> private storage network 10.0.0.0/24 : nfs_client_flags="-n 8" : fstab: : bucket:/sp /sp nfs \ : rw,bg,noatime,-r=1024,-w=1024,intr,-a=3,-d,-t=10 0 0 : bucket:/db /db nfs \ : rw,bg,noatime,-r=1024,-w=1024,intr,-a=3,-d,-t=10 0 0 : :the main question: why do those guys hang there? the nnrpd i use is from :the inn-1.7.2-insync+actived distribution/patchkit : :any ideas? as far as i understand it chokes because of nonexistent pcb's :that are set 0, but i'm not this deep into nfs anyway... any help :appreciated... : :/k : :-- :> "There is a God, but He drinks" -- Blore :http://www.nacamar.de - http://www.nacamar.net - http://www.webmonster.de :http://www.apache.de - http://www.quakeforum.de - finger rohrbach@nacamar.net :KR433/KR11-RIPE - PGP-KFP = F9 A0 DF 91 74 07 6A 1C 5F 0B E0 6B 4D CD 8C 44 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 10:49:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id A98AB14C99 for ; Tue, 9 Nov 1999 10:49:55 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p18-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.147]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id DAA11005; Wed, 10 Nov 1999 03:48:59 +0900 (JST) Message-ID: <3827FF3F.8C0433BC@newsguy.com> Date: Tue, 09 Nov 1999 20:02:23 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Alexey Zelkin Cc: hackers@FreeBSD.ORG Subject: Re: loader security problem References: <19991105222636.B27448@scorpion.crimea.ua> <199911060019.QAA00813@dingo.cdrom.com> <19991107000520.A23479@scorpion.crimea.ua> <3825384E.C6214B61@newsguy.com> <19991109000817.A23687@scorpion.crimea.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexey Zelkin wrote: > > Looks fine! What about including something like that to distribution and > have enabled by default ? It's much easy for newbie users to get it enabled > by default and not hacked machine (also by default). Passwords? On the loader? By default? No! :-) Passwords on the loader is of limited use, and a potential headache. An example in /usr/share/examples/bootforth I can do. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 13: 6: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8652114A1B for ; Tue, 9 Nov 1999 13:05:51 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA94138; Tue, 9 Nov 1999 14:05:45 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA01171; Tue, 9 Nov 1999 14:04:39 -0700 (MST) Message-Id: <199911092104.OAA01171@harmony.village.org> To: Jamie Bowden Subject: Re: Should jail treat ip-number? Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 09 Nov 1999 05:29:51 PST." References: Date: Tue, 09 Nov 1999 14:04:38 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Jamie Bowden writes: : What does jail do that chroot doesn't? I've seen several discussions on : jail on -hackers, but no explanation of why it was implemented, or how : it's different from chroot. It restricts root's ability to do things which would otherwise allow, amoung other things, it to climb out of a chroot'd directory. It also doesn't allow root to create device entries, which helps to keep your data safer. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 13: 6:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 25CA514A1B for ; Tue, 9 Nov 1999 13:05:55 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA92044; Tue, 9 Nov 1999 21:07:18 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 9 Nov 1999 21:07:18 +0000 (GMT) From: Doug Rabson To: Assar Westerlund Cc: Nate Williams , freebsd-hackers@freebsd.org Subject: Re: Using non-PIC code in shared libraries? In-Reply-To: <5l9048gffg.fsf@assaris.sics.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 Nov 1999, Assar Westerlund wrote: > Nate Williams writes: > > How about the reverse, where you link in PIC compiled libraries into > > static (.a) libraries? Does this work? > > Sure. Look at how lib${LIB}_pic.a is done i . PIC-code > is less efficient than non-PIC code. True for x86. For alpha, all code is PIC but the extra registers available reduce the overhead considerably. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 13:37:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id B4BE514A2A for ; Tue, 9 Nov 1999 13:37:37 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id NAA35735; Tue, 9 Nov 1999 13:36:56 -0800 (PST) From: Archie Cobbs Message-Id: <199911092136.NAA35735@bubba.whistle.com> Subject: Re: How to use gdb to catch a panic In-Reply-To: from Zhihui Zhang at "Nov 9, 1999 09:49:43 am" To: zzhang@cs.binghamton.edu (Zhihui Zhang) Date: Tue, 9 Nov 1999 13:36:56 -0800 (PST) Cc: grog@lemis.com (Greg Lehey), 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 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zhihui Zhang writes: > Thanks for your reply. What confuses me is that when I use commands "gdb" > (enter remote protocol mode) and "step" on the target machine, the > debugging machine takes control (it executes "target remote /dev/cuaa1"). > In this case, how can I run anything on the target machine to trigger a > panic? I'm not sure if this answers your question, but the command sysctl -w debug.cebugger=1 will cause the kernel to stop and return your gdb prompt. Then you could call the function panic() directly if you wanted. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 13:46: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id B050414A1B for ; Tue, 9 Nov 1999 13:45:52 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Received: from mojave.sitaranetworks.com ([199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id IAA11672; Wed, 10 Nov 1999 08:15:44 +1030 (CST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991109164507.31840@mojave.sitaranetworks.com> Date: Tue, 9 Nov 1999 16:45:07 -0500 From: Greg Lehey To: Archie Cobbs , Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How to use gdb to catch a panic Reply-To: Greg Lehey References: <199911092136.NAA35735@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199911092136.NAA35735@bubba.whistle.com>; from Archie Cobbs on Tue, Nov 09, 1999 at 01:36:56PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 9 November 1999 at 13:36:56 -0800, Archie Cobbs wrote: > Zhihui Zhang writes: >> Thanks for your reply. What confuses me is that when I use commands "gdb" >> (enter remote protocol mode) and "step" on the target machine, the >> debugging machine takes control (it executes "target remote /dev/cuaa1"). >> In this case, how can I run anything on the target machine to trigger a >> panic? > > I'm not sure if this answers your question, but the command > > sysctl -w debug.cebugger=1 > > will cause the kernel to stop and return your gdb prompt. > Then you could call the function panic() directly if you wanted. Take a look at /usr/src/sys/modules/vinum/.gdbinit.kernel. There's some almost undocumented stuff in there, including a macro called ddb. Call it from gdb and it'll switch back to ddb. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 14:17:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id D50471515E for ; Tue, 9 Nov 1999 14:17:03 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id RAA03283; Tue, 9 Nov 1999 17:16:53 -0500 (EST) Date: Tue, 9 Nov 1999 16:04:34 -0500 (EST) From: Zhihui Zhang To: Greg Lehey , archie@whistle.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How to use gdb to catch a panic In-Reply-To: <19991109164507.31840@mojave.sitaranetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 9 Nov 1999, Greg Lehey wrote: > On Tuesday, 9 November 1999 at 13:36:56 -0800, Archie Cobbs wrote: > > Zhihui Zhang writes: > >> Thanks for your reply. What confuses me is that when I use commands "gdb" > >> (enter remote protocol mode) and "step" on the target machine, the > >> debugging machine takes control (it executes "target remote /dev/cuaa1"). > >> In this case, how can I run anything on the target machine to trigger a > >> panic? > > > > I'm not sure if this answers your question, but the command > > > > sysctl -w debug.cebugger=1 > > > > will cause the kernel to stop and return your gdb prompt. > > Then you could call the function panic() directly if you wanted. > > Take a look at /usr/src/sys/modules/vinum/.gdbinit.kernel. There's > some almost undocumented stuff in there, including a macro called > ddb. Call it from gdb and it'll switch back to ddb. > > Greg > -- Thanks! I will certainly look into them. In the same time, I add a sysctl variable and let my program calls Debugger("some string") if that sysctl variable is true. It seems working. I hope someone will write a hacker's book. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 14:28:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 9D24614C58 for ; Tue, 9 Nov 1999 14:28:27 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Received: from mojave.sitaranetworks.com ([199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id IAA11702; Wed, 10 Nov 1999 08:58:19 +1030 (CST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991109172745.27205@mojave.sitaranetworks.com> Date: Tue, 9 Nov 1999 17:27:45 -0500 From: Greg Lehey To: Zhihui Zhang , archie@whistle.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How to use gdb to catch a panic Reply-To: Greg Lehey References: <19991109164507.31840@mojave.sitaranetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Zhihui Zhang on Tue, Nov 09, 1999 at 04:04:34PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 9 November 1999 at 16:04:34 -0500, Zhihui Zhang wrote: > On Tue, 9 Nov 1999, Greg Lehey wrote: >> On Tuesday, 9 November 1999 at 13:36:56 -0800, Archie Cobbs wrote: >>> Zhihui Zhang writes: >>>> Thanks for your reply. What confuses me is that when I use commands "gdb" >>>> (enter remote protocol mode) and "step" on the target machine, the >>>> debugging machine takes control (it executes "target remote /dev/cuaa1"). >>>> In this case, how can I run anything on the target machine to trigger a >>>> panic? >>> >>> I'm not sure if this answers your question, but the command >>> >>> sysctl -w debug.cebugger=1 >>> >>> will cause the kernel to stop and return your gdb prompt. >>> Then you could call the function panic() directly if you wanted. >> >> Take a look at /usr/src/sys/modules/vinum/.gdbinit.kernel. There's >> some almost undocumented stuff in there, including a macro called >> ddb. Call it from gdb and it'll switch back to ddb. > > Thanks! I will certainly look into them. In the same time, I add a > sysctl variable and let my program calls Debugger("some string") if that > sysctl variable is true. I don't understand what that's useful for. > It seems working. I hope someone will write a hacker's book. I'm intending to write something on the subject, but don't count on it soon. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 14:35: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 2D3EF14C41 for ; Tue, 9 Nov 1999 14:34:48 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id OAA27935; Tue, 9 Nov 1999 14:34:36 -0800 (PST) Date: Tue, 9 Nov 1999 14:34:35 -0800 (PST) From: Julian Elischer To: Archie Cobbs Cc: Zhihui Zhang , Greg Lehey , freebsd-hackers@FreeBSD.ORG Subject: Re: How to use gdb to catch a panic In-Reply-To: <199911092136.NAA35735@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG uh archie, that's a whistle specific sysctl :-) On Tue, 9 Nov 1999, Archie Cobbs wrote: > Zhihui Zhang writes: > > Thanks for your reply. What confuses me is that when I use commands "gdb" > > (enter remote protocol mode) and "step" on the target machine, the > > debugging machine takes control (it executes "target remote /dev/cuaa1"). > > In this case, how can I run anything on the target machine to trigger a > > panic? > > I'm not sure if this answers your question, but the command > > sysctl -w debug.cebugger=1 > > will cause the kernel to stop and return your gdb prompt. > Then you could call the function panic() directly if you wanted. > > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com > > > 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 Tue Nov 9 14:42:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id E10611537E for ; Tue, 9 Nov 1999 14:42:00 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id OAA36411; Tue, 9 Nov 1999 14:41:23 -0800 (PST) From: Archie Cobbs Message-Id: <199911092241.OAA36411@bubba.whistle.com> Subject: Re: How to use gdb to catch a panic In-Reply-To: from Julian Elischer at "Nov 9, 1999 02:34:35 pm" To: julian@whistle.com (Julian Elischer) Date: Tue, 9 Nov 1999 14:41:23 -0800 (PST) Cc: archie@whistle.com (Archie Cobbs), zzhang@cs.binghamton.edu (Zhihui Zhang), grog@lemis.com (Greg Lehey), 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 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > uh archie, that's a whistle specific sysctl :-) Are you sure? We should check it in, it's very useful! > > I'm not sure if this answers your question, but the command > > > > sysctl -w debug.cebugger=1 ^ should be "debugger" > > > > will cause the kernel to stop and return your gdb prompt. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 14:46:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 8DA2314CF0 for ; Tue, 9 Nov 1999 14:46:11 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Received: from mojave.sitaranetworks.com ([199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id JAA11729; Wed, 10 Nov 1999 09:16:01 +1030 (CST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991109174526.14194@mojave.sitaranetworks.com> Date: Tue, 9 Nov 1999 17:45:26 -0500 From: Greg Lehey To: Archie Cobbs , Julian Elischer Cc: Zhihui Zhang , freebsd-hackers@FreeBSD.ORG Subject: Re: How to use gdb to catch a panic Reply-To: Greg Lehey References: <199911092241.OAA36411@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199911092241.OAA36411@bubba.whistle.com>; from Archie Cobbs on Tue, Nov 09, 1999 at 02:41:23PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 9 November 1999 at 14:41:23 -0800, Archie Cobbs wrote: > Julian Elischer writes: >> uh archie, that's a whistle specific sysctl :-) > > Are you sure? We should check it in, it's very useful! On my non-Whistle -CURRENT machine I have: $ sysctl -a | grep debugger debug.debugger_on_panic: 1 Is this what you're talking about? Otherwise, what's the difference? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 14:46:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 7F00F14CF0 for ; Tue, 9 Nov 1999 14:46:43 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id RAA15458; Tue, 9 Nov 1999 17:46:24 -0500 (EST) Date: Tue, 9 Nov 1999 16:34:05 -0500 (EST) From: Zhihui Zhang To: Greg Lehey Cc: archie@whistle.com, freebsd-hackers@FreeBSD.ORG Subject: Re: How to use gdb to catch a panic In-Reply-To: <19991109172745.27205@mojave.sitaranetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Thanks! I will certainly look into them. In the same time, I add a > > sysctl variable and let my program calls Debugger("some string") if that > > sysctl variable is true. > > I don't understand what that's useful for. If the kernel routine is going to be called from my code, I set the sysctl variable to be 1. > > > It seems working. I hope someone will write a hacker's book. > > I'm intending to write something on the subject, but don't count on it > soon. Maybe in a newer version of your book. > Greg > -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 15: 9:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id BC682150CE for ; Tue, 9 Nov 1999 15:09:19 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id PAA29239; Tue, 9 Nov 1999 15:09:07 -0800 (PST) Date: Tue, 9 Nov 1999 15:09:06 -0800 (PST) From: Julian Elischer To: Greg Lehey Cc: Archie Cobbs , Zhihui Zhang , freebsd-hackers@FreeBSD.ORG Subject: Re: How to use gdb to catch a panic In-Reply-To: <19991109174526.14194@mojave.sitaranetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 9 Nov 1999, Greg Lehey wrote: > > On my non-Whistle -CURRENT machine I have: > > $ sysctl -a | grep debugger > debug.debugger_on_panic: 1 > > Is this what you're talking about? Otherwise, what's the difference? This allows the USER level code to trap to the kernel debugger, and at the same time specify whether it should run the dgb robot, or the ddb debugger. e.g. when a daemon notices a particular symptom that indicates that we want to look at kernel state. We tend to use it in a similar way to the keyboard's in order to drop a remote machine (with serial console) to the gdb debugger. We may not be able to use the debugger-on-break case, and in any case that can't be done from the machine itself. The code is simplicity itself.. #if DDB static int debugger_type; static int sysctl_debug_debugger SYSCTL_HANDLER_ARGS { int odb; int error; odb = debugger_type; error = sysctl_handle_int(oidp,&debugger_type, 0, req); if ((error == 0) && req->newptr) { if (debugger_type == 0) boothowto &= ~RB_GDB; else boothowto |= RB_GDB; Debugger("sysctl asked us to enter"); } return (error); } SYSCTL_PROC(_debug, OID_AUTO, debugger, CTLTYPE_INT|CTLFLAG_RW, 0, sizeof debugger_type, sysctl_debug_debugger, "I", ""); #endif > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 15:10:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 9B00414CF0; Tue, 9 Nov 1999 15:10:24 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id AAA16499; Wed, 10 Nov 1999 00:10:21 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id B57E287AB; Wed, 10 Nov 1999 00:00:04 +0100 (CET) Date: Wed, 10 Nov 1999 00:00:04 +0100 From: Ollivier Robert To: freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? Message-ID: <19991110000004.A37063@keltia.freenix.fr> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG References: <199911090824.KAA90295@zibbi.mikom.csir.co.za> <22398.942136151@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <22398.942136151@critter.freebsd.dk> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Poul-Henning Kamp: > I personally do not see IPv6 as being desirable at this time. I see it as very desirable now for several reasons besides the usual ones (shortage of address space, explosion of routing tables): - it provides true mobility (still in the works I know), - the larger address space enables one to avoid the NAT abomination, - security is mandatory (even if many people don't wand the overhead), - autoconfiguration is really great > Ohh, OSI was quite a live for a long time as well, until the government > funded life-support was cut, then it evaporated overnight. OSI is still present in two major areas: telecom systems (GSM, supervision of the same) and Aeronautical systems (Air Traffic Management / Control). I work in the latter and we're pushing IPv6 as much as we can. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 16: 2:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (law-f63.hotmail.com [209.185.131.126]) by hub.freebsd.org (Postfix) with SMTP id B28CC15182 for ; Tue, 9 Nov 1999 16:01:57 -0800 (PST) (envelope-from rendes@hotmail.com) Received: (qmail 71064 invoked by uid 0); 10 Nov 1999 00:01:56 -0000 Message-ID: <19991110000156.71063.qmail@hotmail.com> Received: from 130.63.190.192 by www.hotmail.com with HTTP; Tue, 09 Nov 1999 16:01:51 PST X-Originating-IP: [130.63.190.192] From: "ren des" To: hackers@FreeBSD.ORG Subject: unsubscribe Date: Tue, 09 Nov 1999 16:01:51 PST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: owner-freebsd-hackers-digest@FreeBSD.ORG (freebsd-hackers-digest) >Reply-To: hackers@FreeBSD.ORG >To: freebsd-hackers-digest@FreeBSD.ORG >Subject: freebsd-hackers-digest V4 #664 >Date: Fri, 5 Nov 1999 01:41:52 -0800 (PST) >From owner-freebsd-hackers-digest@FreeBSD.ORG Fri Nov 05 01:45:07 1999 >Received: from [204.216.27.18] by hotmail.com (3.2) with ESMTP id >MHotMailB9EBF1F90021D82197DACCD81B126C6D0; Fri Nov 05 01:45:05 1999 >Received: by hub.freebsd.org (Postfix, from userid 538)id B882D158B9; Fri, >5 Nov 1999 01:41:52 -0800 (PST) >Received: from localhost (localhost [127.0.0.1])by hub.freebsd.org >(Postfix) with SMTPid 925891CD7FE; Fri, 5 Nov 1999 01:41:52 -0800 >(PST)(envelope-from owner-freebsd-hackers-digest) >Received: by hub.freebsd.org (bulk_mailer v1.12); Fri, 5 Nov 1999 01:41:52 >-0800 >Sender: owner-freebsd-hackers-digest@FreeBSD.ORG >Precedence: bulk >Message-ID: > >freebsd-hackers-digest Friday, November 5 1999 Volume 04 : Number 664 > > > >In this issue: >Re: kstat - an API for gathering kernel stats >Re: kstat - an API for gathering kernel stats >Re: kstat - an API for gathering kernel stats >Re: kstat - an API for gathering kernel stats >Re: nfs cookie spoofing patch >FreeBSD FibreChannel support >Re: kstat - an API for gathering kernel stats >Re: aio Functions >Compiling elf gcc 2.7.2.3 on FreeBSD 3.3-R? >Re: kstat - an API for gathering kernel stats >Re: FreeBSD FibreChannel support >New i2o support available for testing. (fwd) >Re: kstat - an API for gathering kernel stats >Re: aio Functions >passwd and chat >Re: kstat - an API for gathering kernel stats >Re: passwd and chat >Re: kstat - an API for gathering kernel stats >Re: kstat - an API for gathering kernel stats >Re: (forw) Reversing 32Upgrade package >Re: Compiling elf gcc 2.7.2.3 on FreeBSD 3.3-R? >Re: kstat - an API for gathering kernel stats >Re: aio Functions >Re: FreeBSD FibreChannel support >Re: FreeBSD FibreChannel support >Re: Netgear FA410 pccard ethernet? >Re: Netgear FA410 pccard ethernet? >Re: FreeBSD FibreChannel support >Re: Granularity of disk I/O >Re: Netgear FA410 pccard ethernet? >Re: Netgear FA410 pccard ethernet? >Re: FreeBSD FibreChannel support >Re: FreeBSD FibreChannel support >Re: kstat - an API for gathering kernel stats >ftpd feature: lock file being stored >Re: FreeBSD FibreChannel support >Re: Compiling elf gcc 2.7.2.3 on FreeBSD 3.3-R? >Re: FreeBSD FibreChannel support >Re: FreeBSD FibreChannel support >Re: FreeBSD FibreChannel support >unable to compile current >Re: Netgear FA410 pccard ethernet? >Re: Netgear FA410 pccard ethernet? >Re: Is there anything like #ifdef BSD >Re: kstat - an API for gathering kernel stats >Re: kstat - an API for gathering kernel stats >Re: Netgear FA410 pccard ethernet? >Re: FreeBSD FibreChannel support >Re: FreeBSD FibreChannel support >Re: kstat - an API for gathering kernel stats >Re: kstat - an API for gathering kernel stats >Re: kstat - an API for gathering kernel stats >Re: kstat - an API for gathering kernel stats >Re: kstat - an API for gathering kernel stats >Re: unable to compile current >Re: FreeBSD FibreChannel support >Re: kstat - an API for gathering kernel stats >PCMCIA Chipset >Re: kstat - an API for gathering kernel stats > >---------------------------------------------------------------------- > >Date: Thu, 4 Nov 1999 02:53:51 -0500 (EST) >From: "Matthew N. Dodd" >Subject: Re: kstat - an API for gathering kernel stats > >On Wed, 3 Nov 1999, Arun Sharma wrote: > > A user program makes a system call with this string "cpu.system" to get > > the current value of user/system/nice time etc. > >How is this different from doing: > ># sysctl -a | grep load >vm.loadavg: { 0.15 0.09 0.04 } > >Ideally we could have a syscall that could return the OID for a given name >to solve the portability and speed issues associated with doing repeated >lookups. > >Seems like you've reinvented the wheel to me. > >- -- >| 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 | This Space For Rent | ISO8802.5 4ever | > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 4 Nov 1999 00:29:59 -0800 (PST) >From: Matthew Jacob >Subject: Re: kstat - an API for gathering kernel stats > >Well, this is welcome news- Bonwick's kstat from solaris was and is an >excellent tool. I look forward to using your version. > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 04 Nov 1999 00:31:15 -0800 (PST) >From: Alex Zepeda >Subject: Re: kstat - an API for gathering kernel stats > >On Thu, 4 Nov 1999, Matthew N. Dodd wrote: > > > On Wed, 3 Nov 1999, Arun Sharma wrote: > > > A user program makes a system call with this string "cpu.system" to >get > > > the current value of user/system/nice time etc. > > > > How is this different from doing: > > > > # sysctl -a | grep load > > vm.loadavg: { 0.15 0.09 0.04 } > >How is that different from doing: > >sysctl vm.loadavg? > >- - alex > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 04 Nov 1999 00:30:06 -0800 >From: Mike Smith >Subject: Re: kstat - an API for gathering kernel stats > > > I wrote kstat as a way to improve on the current BSD method of getting > > kernel statistics, which involves looking up a particular kernel symbol > > name and then getting the value from the symbol offset. This makes any > > performance monitoring tool or an application that gets kernel stats > > non-portable across different kernel versions if for some reason, the >names > > of these variables happen to change. > >We have been progressively obsoleting this for some time in favour of >sysctl, which covers all of the features you're offering and then some. > >Probably the only major advantage your implementation has is the direct >handling of strings as identifiers, rather than the name-to-oid lookup, >but the cached OID provides a much faster lookup method for values you >want to get on a regular basis. > >- -- >\\ Give a man a fish, and you feed him for a day. \\ Mike Smith >\\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org >\\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 4 Nov 1999 10:32:12 +0000 >From: David Malone >Subject: Re: nfs cookie spoofing patch > >On Wed, Nov 03, 1999 at 11:40:39AM -0800, Matthew Dillon wrote: > > > The bug is on the server-side, not really the client side. Many >people > > have been bitten by this problem and it would be cool if someone >submitted > > a patch to fix it. I will get to it eventually but I'm kinda tied >up > > at the moment. > >I think Ian Dowse submitted a patch for this some time ago, which we have >been using with no trouble for months. See: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=13049 > >David. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 4 Nov 1999 06:02:34 -0800 (PST) >From: "Jonathan M. Bresler" >Subject: FreeBSD FibreChannel support > >Matt, > > Thank you for lunch at the South American resturant in >Berkeley during the FreeBSDCon. > > Do we have a FibreChannel driver for FreeBSD? Ideally, I am >looking for arbitrated loop support on the emulex cards. > >jmb >- -- >Jonathan M. Bresler FreeBSD Core Team, Postmaster >jmb@FreeBSD.ORG >FreeBSD--The Power to Serve JMB193 >http://www.freebsd.org/ >PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E >FB > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 04 Nov 1999 11:49:13 ART >From: "Ricardo Bernardini" >Subject: Re: kstat - an API for gathering kernel stats > >I don't think kstat does the same as sysctl, at least for one thing: it >provides for a way to dynamically add counters, if there is a way to >enumerate them and userland proceses can add their own, it will make a good >performance tool. May be I won't have kstat in all my kernels, but it would >be good to have it when you are doing some capacity planning. > >Saludos / Regards >Ricardo > > >- ----Original Message Follows---- >From: Mike Smith > > I wrote kstat as a way to improve on the current BSD method of getting > > kernel statistics, which involves looking up a particular kernel symbol > > name and then getting the value from the symbol offset. This makes any > > performance monitoring tool or an application that gets kernel stats > > non-portable across different kernel versions if for some reason, the >names > > of these variables happen to change. > >We have been progressively obsoleting this for some time in favour of >sysctl, which covers all of the features you're offering and then some. > >Probably the only major advantage your implementation has is the direct >handling of strings as identifiers, rather than the name-to-oid lookup, >but the cached OID provides a much faster lookup method for values you >want to get on a regular basis. > >- -- >\\ Give a man a fish, and you feed him for a day. \\ Mike Smith >\\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org >\\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > >+------------------------------+-----------------------------------+ >|Ricardo Bernardini | "No entiendo por que todos ponen | >|rbernardini@hotmail.com | alguna frase celebre aqui" | >|+54-11-4404-4525 | "I don't understand why everybody | >|Buenos Aires, Argentina | puts a quote in here" | >+------------------------------+-----------------------------------+ > >______________________________________________________ >Get Your Private, Free Email at http://www.hotmail.com > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 04 Nov 1999 11:50:50 ART >From: "Ricardo Bernardini" >Subject: Re: aio Functions > >Well !! That's far more than the things I'm having trouble with!! I'm not >being able to make ONE asynchronous read. I've tried the aio functions with >file I/O and it worked fine, I've also tried the socket I/O with read() and >it worked fine too. But when I issue the read to the async queue an try to >get its status aio_error returns -1 and sets errno to EINVAL. >Anyway this is a test program just to become familiar with the fucntions >before actually using them, so I really need more information about them, >and the aiocb_t struct. >Thanks for your answer. > >Saludos / Regards >Ricardo Bernardini > >- ----Original Message Follows---- >From: Christopher Sedore > > Hello list! > > > > I'm starting with aio functions (aio_read, aio_return, etc.), I've made >them > > work with disk file I/O, now I'm trying with TCP sockets not with the >same > > success. Does anyone know if it is posible to do what I'm trying? Or >where > > to find more info about this function group? I'just read the man pages >about > > them. > >Which version of FreeBSD are you using? Its best to be using -current >from my experience. TCP sockets should work, but they'll be pretty >crippled for certain kinds of uses (like trying to have an outstanding >read on more than a couple dozen sockets, etc). > >I've got a set of patches that fix this and the fact that signals don't >get issued for completion on certain types of requests. I'm hoping to get >it committed, but feel free to contact me for the latest stuff until then. >I just finished updating and consolidating my patches so they cleanly >apply to -current of a week ago. Testing thus far appears promising--I'm >balancing more than a few sockets and pushing 10MB/sec through them (disk >to socket and the inverse). I killed the last bug I knew of this week >(occasionally paniced under some wierd process shutdown conditions). > >I hope to try 1000 descriptors soon. > >- -Chris > >+------------------------------+-----------------------------------+ >|Ricardo Bernardini | "No entiendo por que todos ponen | >|rbernardini@hotmail.com | alguna frase celebre aqui" | >|+54-11-4404-4525 | "I don't understand why everybody | >|Buenos Aires, Argentina | puts a quote in here" | >+------------------------------+-----------------------------------+ > >______________________________________________________ >Get Your Private, Free Email at http://www.hotmail.com > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 4 Nov 1999 09:03:08 -0700 >From: Charles Randall >Subject: Compiling elf gcc 2.7.2.3 on FreeBSD 3.3-R? > >After an unsuccessful attempt at asking this on -questions... > >I believe that I could work my way through the problem below if I could >build a vanilla gcc 2.7.2.3 on FreeBSD 3.3-R. > >Attempting to build a fresh 2.7.2.3, > >1. configure >2. remove references to gnumalloc in Makefile and cp/Makefile >3. make LANGUAGES=c > >and I get > >- --- snip --- >./xgcc -B./ -DIN_GCC -g -I./include enquire.o -o enquire >/usr/libexec/elf/ld: cannot open crt0.o: No such file or directory >*** Error code 1 > >Stop. >- --- snip --- > >I presume that this is an a.out vs elf issue -- gcc is trying to build an >a.out version and 3.3-R is elf. However, I get the same problem if I try >configure with "configure i386-elf-freebsd". > >Suggestions? > >Charles > >P.S. I know that 3.3-R uses gcc 2.7.2.3 internally. However, I would like >to >build a separate binary for StackGuard. > >- -----Original Message----- >From: Charles Randall [mailto:crandall@matchlogic.com] >Sent: Tuesday, November 02, 1999 9:37 AM >To: freebsd-questions@freebsd.org >Subject: Immunix Stackguard for FreeBSD? > > >Has anyone successfully built Immunix stackguard on FreeBSD? > >Here's a link to the original research project, > >http://www.cse.ogi.edu/DISC/projects/immunix/StackGuard/ > >The latest development seems to be reflected here, > >http://www.wirex.com/ > >and > >http://immunix.org/ > >On the downloads page at immunix.org, there's an RPM of patches to gcc >2.7.2.3. > >I've un-packed that on my 3.3-R system, applied all of the patches, run >'configure', and 'make LANGUAGES=c'. > >First, the build fails trying to find gnumalloc. After removing that >dependency in Makefile and cp/Makefile (assuming that BSD malloc will be >used), the build eventually dies with: > >- --- snip --- >./xgcc -B./ -DIN_GCC -O -I./include enquire.o -o enquire >/usr/libexec/elf/ld: cannot open crt0.o: No such file or directory >*** Error code 1 > >Stop. >- --- snip --- > >I presume that this is because 3.3-R uses elf and gcc is trying to build an >a.out version. > >Thinking about that a bit, I ran 'make distclean', 'configure >i386-elf-freebsd', and 'make LANGUAGES=c' in an attempt to build an >elf-specific version. After removing the dependencies on gnumalloc again, >the build died in the same place, > >- --- snip --- >./xgcc -B./ -DIN_GCC -O -I./include enquire.o -o enquire >/usr/libexec/elf/ld: cannot open crt0.o: No such file or directory >*** Error code 1 > >Stop. >- --- snip --- > >Am I missing a compatibility library or something? > >Suggestions? > >Charles > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 4 Nov 1999 11:07:31 -0500 (EST) >From: "Matthew N. Dodd" >Subject: Re: kstat - an API for gathering kernel stats > >On Thu, 4 Nov 1999, Alex Zepeda wrote: > > On Thu, 4 Nov 1999, Matthew N. Dodd wrote: > > > On Wed, 3 Nov 1999, Arun Sharma wrote: > > > > A user program makes a system call with this string "cpu.system" to >get > > > > the current value of user/system/nice time etc. > > > > > > How is this different from doing: > > > > > > # sysctl -a | grep load > > > vm.loadavg: { 0.15 0.09 0.04 } > > > > How is that different from doing: > > > > sysctl vm.loadavg? > >I was more trying to demonstrate the fact that we have sysctl(3). > >- -- >| 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 | This Space For Rent | ISO8802.5 4ever | > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 4 Nov 1999 08:19:22 -0800 (PST) >From: Matthew Jacob >Subject: Re: FreeBSD FibreChannel support > >Hi- Yes- it was a fun though short lunch. > >We support the Qlogic 2100/2200 cards currently for both private loop and >fabrics. The emulex card is popular, but nobody's written a driver for it >for >FreeBSD. > > >On Thu, 4 Nov 1999, Jonathan M. Bresler wrote: > > > > > Matt, > > > > Thank you for lunch at the South American resturant in > > Berkeley during the FreeBSDCon. > > > > Do we have a FibreChannel driver for FreeBSD? Ideally, I am > > looking for arbitrated loop support on the emulex cards. > > > > jmb > > -- > > Jonathan M. Bresler FreeBSD Core Team, Postmaster >jmb@FreeBSD.ORG > > FreeBSD--The Power to Serve JMB193 >http://www.freebsd.org/ > > PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 >0E FB > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 4 Nov 1999 08:22:00 -0800 (PST) >From: Matthew Jacob >Subject: New i2o support available for testing. (fwd) > >I should point out that Simon has also been working on a DPT FC driver- I'm >not sure if this i2o OSM is part of this or not (Simon?). > >- ---------- Forwarded message ---------- >Date: Mon, 01 Nov 1999 11:04:06 -0500 >From: Simon Shapiro >To: jkh@FreeBSD.ORG >Subject: New i2o support available for testing. > >A Pre-Alpha release of a new i2o OSM for FreeBSD is now >available for testing. > >Check http://simon-shapiro.org/drivers.html for details. > >- -- > > >Sincerely Yours, Shimon@Simon-Shapiro.ORG > 404.664.6401 >Simon Shapiro > >Unwritten code has no bugs and executes at twice the speed of mouth > > > >This is the moderated mailing list freebsd-announce. >The list contains announcements of new FreeBSD capabilities, >important events and project milestones. >See also the FreeBSD Web pages at http://www.freebsd.org > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-announce" in the body of the message > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 4 Nov 1999 09:18:04 -0700 >From: "Ronald G. Minnich" >Subject: Re: kstat - an API for gathering kernel stats > >FWIW -- I think a reasonable goal of "getting stats out of the kernel" is >that pulling data out ought to run as fast as bcopy, and it would be nice >if you didn't have to drop into a syscall. Kind of an extreme position, I >guess, but if you have ever seen the rstatd on linux eat 12% of cpu to >return 10 samples/second you'd know why I want it. Given the slowness of >some stuff (it takes linux 6 milliseconds to count up free/shared memory >pages -- the code visits every page struct) bcopy speed is not a bad >yardstick. Sysctl is much faster than reading files in /proc, but still >too slow. How will kstat compare? how does it compare in solaris? Anybody >got a bandwidth number? > >Numbers I have now (sorry, just for linux at present): > Using files in /proc: awful, so slow it's not worth > measuring exactly, something like 400 bytes in 20 > milliseonds > Using sysctl: Varies depending on the strategy and how much > data you yank per variable, but O(1-10 > Mbytes/second) > >ron > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Fri, 05 Nov 1999 01:39:25 +0900 >From: "Daniel C. Sobral" >Subject: Re: aio Functions > >Ricardo Bernardini wrote: > > > > Well !! That's far more than the things I'm having trouble with!! I'm >not > > being able to make ONE asynchronous read. I've tried the aio functions >with > > file I/O and it worked fine, I've also tried the socket I/O with read() >and > > it worked fine too. But when I issue the read to the async queue an try >to > > get its status aio_error returns -1 and sets errno to EINVAL. > > Anyway this is a test program just to become familiar with the fucntions > > before actually using them, so I really need more information about >them, > > and the aiocb_t struct. > >Be aware that aio is not implemented for all things that you can get >an fd for. It was originally implemented *only* for files, though I >was under the impression that support for sockets was later added. > >- -- >Daniel C. Sobral (8-DCS) >dcs@newsguy.com >dcs@freebsd.org > > What y'all wanna do? > Wanna be hackers? Code crackers? Slackers > Wastin' time with all the chatroom yakkers? > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 04 Nov 1999 11:51:22 +0200 >From: Johan Kruger >Subject: passwd and chat > >This is a multi-part message in MIME format. >- --------------9785ED3441D1AFA72BC6E3D0 >Content-Type: text/plain; charset=us-ascii >Content-Transfer-Encoding: 7bit > >How can i use chat on the command line to enter a new password without >interaction with passwd . >For example , i want to use chat to reply on New password and Retype >password, something like this : > ># chat `passwd` ew passw: qwerty: etype pass: qwerty > >But the above doesn't work. > >- --------------9785ED3441D1AFA72BC6E3D0 >Content-Type: text/x-vcard; charset=us-ascii; > name="jkruger.vcf" >Content-Transfer-Encoding: 7bit >Content-Description: Card for Johan Kruger >Content-Disposition: attachment; > filename="jkruger.vcf" > >begin:vcard >n:Kruger;Johan >tel;cell:+27 83 3015923 >tel;fax:+27 12 6651343 >tel;home:+27 83 3015923 >tel;work:+27 12 6651338 >x-mozilla-html:FALSE >org:Nanoteq;Development >version:2.1 >email;internet:jkruger@oskar.nanoteq.co.za >title:Mr >adr;quoted-printable:;;P.O BOX >12872=0D=0AOnderstepoort=0D=0A0110=0D=0ASouth >Africa;Pretoria;Gauteng;0110;South Africa >x-mozilla-cpt:;1920 >fn:Johan Kruger >end:vcard > >- --------------9785ED3441D1AFA72BC6E3D0-- > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 4 Nov 1999 09:23:04 -0800 >From: Arun Sharma >Subject: Re: kstat - an API for gathering kernel stats > >On Thu, Nov 04, 1999 at 02:53:51AM -0500, Matthew N. Dodd wrote: > > On Wed, 3 Nov 1999, Arun Sharma wrote: > > > A user program makes a system call with this string "cpu.system" to >get > > > the current value of user/system/nice time etc. > > > > How is this different from doing: > > > > # sysctl -a | grep load > > vm.loadavg: { 0.15 0.09 0.04 } > > > > Ideally we could have a syscall that could return the OID for a given >name > > to solve the portability and speed issues associated with doing repeated > > lookups. > > > > Seems like you've reinvented the wheel to me. > >I just looked at the sysctl implementation and there are some differences. >Moreover, since it was not being used in tools like vmstat and xosview, >I thought there must be a reason. > >sysctl also seems to assume that it doesn't get called frequently. So >mapping the name to the sysctl data is a slightly more heavy duty >operation than a hash table lookup. > > -Arun > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 4 Nov 1999 10:35:39 -0700 (MST) >From: Nick Rogness >Subject: Re: passwd and chat > >On Thu, 4 Nov 1999, Johan Kruger wrote: > > > How can i use chat on the command line to enter a new password without > > interaction with passwd . > > For example , i want to use chat to reply on New password and Retype > > password, something like this : > > Why use chat when you can use pw(8)? Example: > > # echo "password" | pw usermod -n username -h 0 > >******************************************************** >Nick Rogness File not found... >System Administrator Should I fake it (Y/N)? >RapidNet, INC >******************************************************** > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > >------------------------------ > >Date: Thu, 4 Nov 1999 12:52:50 -0500 (EST) >From: "Matthew N. Dodd" >Subject: Re: kstat - an API for gathering kernel stats > >On Thu, 4 Nov 1999, Arun Sharma wrote: > > I just looked at the sysctl implementation and there are some >differences. > > Moreover, since it was not being used in tools like vmstat and xosview, ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 16:33:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id E2E7015180 for ; Tue, 9 Nov 1999 16:33:48 -0800 (PST) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id QAA24023; Tue, 9 Nov 1999 16:33:40 -0800 (PST) Message-Id: <199911100033.QAA24023@boreas.isi.edu> X-Mailer: exmh version 2.1.0 04/14/1999 To: Ollivier Robert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Should jail treat ip-number? In-Reply-To: Your message of "Wed, 10 Nov 1999 00:00:04 +0100." <19991110000004.A37063@keltia.freenix.fr> X-Url: http://www.isi.edu/~faber Date: Tue, 09 Nov 1999 16:33:39 -0800 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ollivier Robert wrote: >OSI is still present in two major areas: telecom systems (GSM, supervision of >the same) and Aeronautical systems (Air Traffic Management / Control). I work >in the latter and we're pushing IPv6 as much as we can. Suddenly I'm in no hurry to fly home for Christmas. If you're using OSI and betting on IPv6 in the near term, you may be rowing for the wrong shore. :-) - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Keys: http://www.isi.edu/~faber/pubkeys.asc -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQA/AwUBOCi9Y2lM93/mX/l7EQI5swCg6AgEJPqAHqnPA1s2OJKaZE5HYLoAnR23 QJBSbNTC581g7Her6bQ3Z1IQ =84rw -----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 Tue Nov 9 16:39:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 48742151DA; Tue, 9 Nov 1999 16:39:20 -0800 (PST) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id BAA05128; Wed, 10 Nov 1999 01:39:18 +0100 (MET) Received: by bofh.enst.fr (Postfix, from userid 12426) id C8CFCD246; Wed, 10 Nov 1999 01:39:13 +0100 (CET) Message-ID: <19991110013913.A5181@enst.fr> Date: Wed, 10 Nov 1999 01:39:13 +0100 From: Pierre Beyssac To: Yoshinobu Inoue , freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Should jail treat ip-number? References: <19991109125445E.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19991109125445E.shin@nd.net.fujitsu.co.jp>; from Yoshinobu Inoue on Tue, Nov 09, 1999 at 12:54:45PM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 09, 1999 at 12:54:45PM +0900, Yoshinobu Inoue wrote: > Currentlly jail set an ip-number and let prisoned processes > only to bind it. [ the current jail(2) interface and its future WRT IPv6 ] > I think kernel change will not so much for any above addition > or changes, but there will be some backword compatibility > issue for API. (some member addition to the jail structure, > and jail command extensions) There's been a discussion a few weeks ago on freebsd-security on this very matter. See attached mail below. The conclusion was that jail(2) should be fixed to use a sockaddr instead of a 32 bit int to specify the address. That seems to be the first logical step, even before making jail(2) IPv6-compliant. Pierre Date: Sun, 19 Sep 1999 11:58:39 -0400 (EDT) From: Garrett Wollman Message-Id: <199909191558.LAA64750@khavrinen.lcs.mit.edu> To: Matthew Dillon Cc: Poul-Henning Kamp , security@FreeBSD.ORG Subject: Re: BPF on in 3.3-RC GENERIC kernel In-Reply-To: <199909190551.WAA68627@apollo.backplane.com> References: <12516.937680952@critter.freebsd.dk> <199909190551.WAA68627@apollo.backplane.com> < said: > struct sockaddr is the standard for specifying an IP address. Jail > isn't using it, not even for IPV4. It's using an unsigned 32 bit int. > Hell, it isn't even using a struct in_addr! The field is plain and > simply inappropriately specified in the structure. For once, I agree with Matt. As titular networking czar, I'm asking you, Poul, to please fix the interface. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 9 19:38:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orange.kame.net (orange.kame.net [203.178.141.194]) by hub.freebsd.org (Postfix) with ESMTP id 127541515E for ; Tue, 9 Nov 1999 19:38:21 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from localhost (kame213.kame.net [203.178.141.213]) by orange.kame.net (8.9.1+3.1W/3.7W) with ESMTP id MAA06750; Wed, 10 Nov 1999 12:37:41 +0900 (JST) To: dot@dotat.at Cc: hackers@freebsd.org Subject: Re: Should jail treat ip-number? In-Reply-To: References: <22398.942136151@critter.freebsd.dk> <19991110022852N.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991110123829Z.shin@nd.net.fujitsu.co.jp> Date: Wed, 10 Nov 1999 12:38:29 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 23 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Then IPv6 support for jail should be very good thing, > > because extremely many IP addresses become available for > > a machine with IPv6. (which is not with IPv4) > > We have a number of machines with many thousands of IP addresses using > the patch in PR#12071. It isn't as general a solution as using a hash > table to lookup interface aliases (as in NetBSD or BSDI) but it is > much more easy to manage one alias per CIDR block than 254 aliases per > /24 (say). > > Tony. > -- > let it be dot at The patch is interesting and seems efficient, and same kind of fix for IPv6 might also work. But my point is that, on public internet environment where global IPv4 addr is necessary, there is another issue of actual IPv4 addr shortage, isn't it? Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 0:22:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a13c051.neo.rr.com [204.210.212.51]) by hub.freebsd.org (Postfix) with ESMTP id C3EAC15206 for ; Wed, 10 Nov 1999 00:22:10 -0800 (PST) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id DAA06081 for ; Wed, 10 Nov 1999 03:22:09 -0500 Date: Wed, 10 Nov 1999 03:22:09 -0500 (EST) From: Mike Nowlin To: freebsd-hackers@FreeBSD.ORG Subject: serial (std & rocketport) ioctl? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hate to sound like a bum, but I haven't figured out enough of the kernel to answer this one for myself..... :) Topic: serial driver We have an application that sends (not receives) data to a serial port to a set of brain-dead analyzers (and other stuff). For several reasons I don't feel motivated enough to get into here, we can't send data to more than one at a time. Under Linux, there's an ioctl() you can call (don't remember which one) to ask the kernel if the port in question has actually completed sending the data that has been sent to it. Last time I checked, this only worked for the 8250 family of parts, and not the more "advanced" boards like Cyclades & RocketPort -- that ioctl didn't exist for these boards. So, I was stuck using standard serial boards, and using this ioctl to wait for one transmission to complete before starting another one to a different port. Is there anything like this under FreeBSD? The Linux machine is on its way out (kernel version 1.2.8(!), plus failing hardware), and we've added more equipment -- I'd love to use a Cyclades or RP board for this, instead of lots of modified serial cards, and I've been using more and more FreeBSD for the machines at work... (Don't get me wrong - I love Linux, but I trust FreeBSD more for what we do at work -- medical testing.) mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 0:48:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D5E0315329 for ; Wed, 10 Nov 1999 00:48:24 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id BAA08541; Wed, 10 Nov 1999 01:11:57 -0800 (PST) Date: Wed, 10 Nov 1999 01:11:57 -0800 (PST) From: Alfred Perlstein To: Mike Nowlin Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: serial (std & rocketport) ioctl? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 Nov 1999, Mike Nowlin wrote: > > Hate to sound like a bum, but I haven't figured out enough of the kernel > to answer this one for myself..... :) > > Topic: serial driver > > We have an application that sends (not receives) data to a serial port to > a set of brain-dead analyzers (and other stuff). For several reasons I > don't feel motivated enough to get into here, we can't send data to more > than one at a time. > > Under Linux, there's an ioctl() you can call (don't remember which one) to > ask the kernel if the port in question has actually completed sending the > data that has been sent to it. Last time I checked, this only worked for > the 8250 family of parts, and not the more "advanced" boards like Cyclades > & RocketPort -- that ioctl didn't exist for these boards. So, I was stuck > using standard serial boards, and using this ioctl to wait for one > transmission to complete before starting another one to a different port. > > Is there anything like this under FreeBSD? The Linux machine is on its > way out (kernel version 1.2.8(!), plus failing hardware), and we've added > more equipment -- I'd love to use a Cyclades or RP board for this, instead > of lots of modified serial cards, and I've been using more and more > FreeBSD for the machines at work... (Don't get me wrong - I love Linux, > but I trust FreeBSD more for what we do at work -- medical testing.) We like FreeBSD as well. :) I'm not a serial expert, but maybe the direction you need to take is looking at /usr/include/sys/ttycom.h, several ioctl's seem to be what you're looking for, noteably: #define TIOCDRAIN _IO('t', 94) /* wait till output drained */ maybe that's incorrect, but i'm sure one or a combination of a few ioctls from that header will help you out. good luck, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 0:53: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id B5F7A15329 for ; Wed, 10 Nov 1999 00:52:58 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.040 #1) id 11lTUv-00009h-00 for hackers@freebsd.org; Wed, 10 Nov 1999 10:52:57 +0200 From: Sheldon Hearn To: hackers@freebsd.org Subject: mode_perl DSO works on STABLE, not CURRENT Date: Wed, 10 Nov 1999 10:52:57 +0200 Message-ID: <600.942223977@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, Below is a message that I sent to the modperl@apache.org mailing list regarding a problem I'm having with Apache::AuthenRadius and mod_perl. I'm mailing here in the hopes that someone here knows about a subtle difference between STABLE and CURRENT that would blow me out of the water. :-) Ciao, Sheldon. ------- Forwarded Message Date: Tue, 09 Nov 1999 17:01:06 +0200 From: Sheldon Hearn To: modperl@apache.org Subject: Undefined symbol "PL_markstack_ptr" at runtime Message-ID: <93760.942159666@axl.noc.iafrica.com> - ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-ID: <93758.942159665.1@axl.noc.iafrica.com> Hi folks, I'm setting up a FreeBSD 4.0-CURRENT machine to run an Apache server that uses RADIUS authentication. I've already done this successfully with FreeBSD 3.2-STABLE, but read on to see why I'm asking here and not on the FreeBSD mailing lists. :-) I'm using: perl 5.005_03 apache-1.3.9 mod_perl-1.21 (Built as a DSO with APXS [EVERYTHING=1]) Apache-AuthenRadius-0.3 (Perl Module) RadiusPerl-0.05 (Perl Module) MD5-1.7 (Perl Module) I've configured httpd.conf with the following pertinent directives: | [...] | LoadModule perl_module libexec/apache/libperl.so | # perl_module is the last LoadModule | | [...] | AddModule mod_perl.c | # mod_perl.c is the last AddModule | | PerlModule Apache::AuthenRadius Without the PerlModule directive, ``apachectl configtest'' reports that the syntax is OK. However, when I Uncomment the perlModule directive, the configtest produces this (tidied up) output: | Syntax error on line 261 of /usr/local/etc/apache/httpd.conf: | Can't load '/usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/MD5/MD5.so' for module MD5: /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/MD5/MD5.so: Undefined symbol "PL_markstack_ptr" at /usr/libdata/perl/5.00503/DynaLoader.pm line 169. | | at /usr/local/lib/perl5/site_perl/5.005/Authen/Radius.pm line 18 | BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.005/Authen/Radius.pm line 18. | BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.005/Apache/AuthenRadius.pm line 8. When I use Apache::AuthenRadius from a perl script and run it with the perl interpretor from the command-line, no such error occurs. That's why I'm mailing this list. I'm hoping _someone_ here knows enough to at least point me in the right direction. As suggested in mod_perl's SUPPORT document, I've attached below the output of ``perl -V''. Thanks, Sheldon. - ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-ID: <93758.942159665.2@axl.noc.iafrica.com> Content-Description: perlv 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=egcs-2.91.66 19990314 (egcs-1.1.2 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' libpth=/usr/lib libs=-lm -lc -lcrypt libc=/usr/lib/libc.so, so=so, useshrplib=true, libperl=libperl.so.3 Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' ' cccdlflags='-DPIC -fpic', lddlflags='-shared' Characteristics of this binary (from libperl): Built under freebsd Compiled at Oct 14 1999 18:16:01 @INC: /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 . - ------- =_aaaaaaaaaa0-- ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 0:58:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles553.castles.com [208.214.165.117]) by hub.freebsd.org (Postfix) with ESMTP id 3C79E15329 for ; Wed, 10 Nov 1999 00:58:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA00489; Wed, 10 Nov 1999 00:48:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911100848.AAA00489@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein Cc: Mike Nowlin , freebsd-hackers@FreeBSD.ORG Subject: Re: serial (std & rocketport) ioctl? In-reply-to: Your message of "Wed, 10 Nov 1999 01:11:57 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Nov 1999 00:48:12 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not a serial expert, but maybe the direction you need to take > is looking at /usr/include/sys/ttycom.h, several ioctl's seem to > be what you're looking for, noteably: > > #define TIOCDRAIN _IO('t', 94) /* wait till output drained */ > > maybe that's incorrect, but i'm sure one or a combination of a few > ioctls from that header will help you out. The default behaviour for most serial adapters is also to defer returning from close until the port has drained. (or timed out after an insane period). We do support waiting on drain as a general principle. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 3:59:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nic.mmc.net.ge (nic.mmc.net.ge [212.72.145.2]) by hub.freebsd.org (Postfix) with ESMTP id 0B92014D8F for ; Wed, 10 Nov 1999 03:59:16 -0800 (PST) (envelope-from dima@mmc.net.ge) Received: from mmc.net.ge (wondy.mmc.net.ge [212.72.145.9]) by nic.mmc.net.ge (8.9.3/8.9.3) with ESMTP id RAA18661 for ; Wed, 10 Nov 1999 17:04:32 +0500 (GET) Message-ID: <38295E22.CAD6801C@mmc.net.ge> Date: Wed, 10 Nov 1999 15:59:30 +0400 From: Dima X-Mailer: Mozilla 4.7 [en] (Win95; I) X-Accept-Language: en,ru MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Limiting speed of the Network Ethernet Card. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any possibility to limit speed of the Network Card (I have Intel Ether Express card - fxp driver)? I need to limit speed with only 19200 Kbps, not 10Mbps. Or if it is not posible at all, what I have to do if I have LAN and want to limit speed of the part of this LAN with only 19200? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 4:39:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oskar.dev.nanoteq.co.za (oskar.dev.nanoteq.co.za [196.7.114.5]) by hub.freebsd.org (Postfix) with ESMTP id DC78D151A2 for ; Wed, 10 Nov 1999 04:39:18 -0800 (PST) (envelope-from rbezuide@oskar.dev.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.dev.nanoteq.co.za (8.9.3/8.9.0) id OAA23318 for freebsd-hackers@freebsd.org; Wed, 10 Nov 1999 14:39:23 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199911101239.OAA23318@oskar.dev.nanoteq.co.za> Subject: cc -pthread and libc_r question To: freebsd-hackers@freebsd.org Date: Wed, 10 Nov 1999 14:39:23 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi .. I've compiled a program with the -pthread compiler option on a 3.3-STABLe system ... after doing a ldd on the executable I see that both libc_r AND lic are linked .. is this correct ? Shouldn't libc_r replace libc ? Thanks Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 4:47:36 1999 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 D15A6151A2 for ; Wed, 10 Nov 1999 04:47:34 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id HAA20284; Wed, 10 Nov 1999 07:46:18 -0500 (EST) Date: Wed, 10 Nov 1999 07:46:18 -0500 (EST) From: Daniel Eischen Message-Id: <199911101246.HAA20284@pcnet1.pcnet.com> To: freebsd-hackers@FreeBSD.ORG, rbezuide@oskar.dev.nanoteq.co.za Subject: Re: cc -pthread and libc_r question Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've compiled a program with the -pthread compiler option on a > 3.3-STABLe system ... after doing a ldd on the executable I see that > both libc_r AND lic are linked .. is this correct ? No. > Shouldn't libc_r replace libc ? Yes. Are you using a complicated Makefile, GNU configure, or something that may be explicitly including -lc as an option to the linker? Specifying -pthread will not _prevent_ linking against libc if -lc is specified. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 4:51:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 99A9B1525B for ; Wed, 10 Nov 1999 04:51:37 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.2/8.9.2) id NAA04137; Wed, 10 Nov 1999 13:51:37 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <199911101251.NAA04137@info.iet.unipi.it> Subject: Re: Limiting speed of the Network Ethernet Card. In-Reply-To: <38295E22.CAD6801C@mmc.net.ge> from Dima at "Nov 10, 1999 3:59:30 pm" To: dima@mmc.net.ge (Dima) Date: Wed, 10 Nov 1999 13:51:32 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there any possibility to limit speed of the Network Card (I have > Intel Ether Express card - fxp driver)? > I need to limit speed with only 19200 Kbps, not 10Mbps. > > Or if it is not posible at all, what I have to do if I have LAN and want > to limit speed of the part of this LAN with only 19200? on FreeBSD, you would use dummynet to do this. man ipfw, man dummynet. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 6:56:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.wuppy.net.ru (ns.wuppy.net.ru [195.9.65.100]) by hub.freebsd.org (Postfix) with ESMTP id 42CDE14E9A for ; Wed, 10 Nov 1999 06:56:27 -0800 (PST) (envelope-from romanp@wuppy.net.ru) Received: from localhost (romanp@localhost) by ns.wuppy.net.ru (8.9.3.local/8.9.3) with ESMTP id RAA18178 for ; Wed, 10 Nov 1999 17:56:22 +0300 (MSK) X-Authentication-Warning: ns.wuppy.net.ru: romanp owned process doing -bs Date: Wed, 10 Nov 1999 17:56:20 +0300 (MSK) From: "Roman V. Palagin" To: freebsd-hackers@freebsd.org Subject: What's happen with anoncvs.freebsd.org? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I don't know, is it appropriate group to ask this question, but anyway: when I try to check out /usr/src/sys from anoncvs.freebsd.org, I just get % cvs co sys /ctm/FreeBSD/anoncvs/anoncvssh: No such file or directory cvs [checkout aborted]: end of file from server (consult above messages if any) % Who can tell me is there are any chances to get things work again? /Roman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 7:38:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69]) by hub.freebsd.org (Postfix) with ESMTP id 692DB151EB for ; Wed, 10 Nov 1999 07:38:00 -0800 (PST) (envelope-from myevmenkin@att.com) Received: from flf960r1.ems.att.com ([135.71.244.37]) by kcmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id KAA23337 for ; Wed, 10 Nov 1999 10:37:48 -0500 (EST) Received: from njb140bh3.ems.att.com by flf960r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id KAA14205; Wed, 10 Nov 1999 10:33:28 -0500 (EST) Received: by njb140bh3.ems.att.com with Internet Mail Service (5.5.2448.0) id ; Wed, 10 Nov 1999 10:37:30 -0500 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'freebsd-hackers@FreeBSD.org'" Subject: Ethernet TAP driver v0.2 released Date: Wed, 10 Nov 1999 10:37:26 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="koi8-r" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All! I've released Ethernet TAP driver v0.2 for FreeBSD It provides a virtual Ethernet interface to the system. It also provides packet reception and transmission for user-space programs. It can be viewed as a simple Ethernet device, which instead of receiving packets from a physical medium, receives them from a user-space program and instead of sending packets via physical media, writes them to the user-space program. Changes since v 0.1 - FreeBSD kernel Ethernet bridging (by Luigi Rizzo) support added. This feature seems to be working, but it needs more testing. I've tested it with VTUN (http://vtun.netpedia.net). I had two Linux boxes connected with the same FreeBSD box with VTUN. The FreeBSD box was an Ethernet bridge. So all three boxes were on the same virtual Ethernet network. Thanks to Maxim Krasnyansky. DUMMYNET should be working also, but I did not test it. - Removig address from tapX interface when tapX device is closed It has been added in v 0.1a, but I did not announce it here The driver can be found at http://vtun.netpedia.net/tun/tap-0.2-freebsd.tar.gz ---------------------------------------------------------------------------- ---------- Folks, what do you think about smart user-space Ethernet bridge? Anyone needs it? Thanks, eMax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 7:42:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pluto.cpe.ku.ac.th (pluto.cpe.ku.ac.th [158.108.32.150]) by hub.freebsd.org (Postfix) with ESMTP id 299E614DDA for ; Wed, 10 Nov 1999 07:42:04 -0800 (PST) (envelope-from stt@pluto.cpe.ku.ac.th) Received: from localhost (stt@localhost) by pluto.cpe.ku.ac.th (8.9.3/8.9.3) with ESMTP id WAA21172 for ; Wed, 10 Nov 1999 22:42:42 GMT Date: Wed, 10 Nov 1999 22:42:42 +0000 (GMT) From: Sunthiti Patchararungruang To: freebsd-hackers@freebsd.org Subject: Problem about Raw IP socket Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sir, I have to create a route program for my thesis. Its operation is different from normal packet forwarding. Therefore, I need to forward all packets instead of using normal packet forwarding in FreeBSD kernel. I capture packets via Divert socket. It works well. I can grap IP packket including its header. However, I use normal Raw IP socket to write the packets to selected next-hop. I use socket option SO_DONTROUTE and IP_HDRINCL with my Raw IP socket and use "sendto" to write packets with "sockaddr" set to the IP of the next-hop-gateway. The sendto command always return error with errno=22. How can I solve this error? Thank you for all help. Regards, Sunthiti Patchararungruang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 7:45:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 930D614DDA for ; Wed, 10 Nov 1999 07:45:07 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.2/8.9.2) id QAA04767; Wed, 10 Nov 1999 16:45:21 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <199911101545.QAA04767@info.iet.unipi.it> Subject: Re: Ethernet TAP driver v0.2 released In-Reply-To: from "Yevmenkin, Maksim N, CSCIO" at "Nov 10, 1999 10:37:26 am" To: myevmenkin@att.com (Yevmenkin Maksim N CSCIO) Date: Wed, 10 Nov 1999 16:45:21 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've released Ethernet TAP driver v0.2 for FreeBSD ... > Folks, what do you think about smart user-space Ethernet bridge? > Anyone needs it? i think performance is a big problem here (same as in the case of user-space natd, but worse because a bridge touches all packets). You have too many data copies. cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) http://www.iet.unipi.it/~luigi/ngc99/ ==== First International Workshop on Networked Group Communication ==== -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 7:53:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from almso1.proxy.att.com (almso1.att.com [192.128.167.69]) by hub.freebsd.org (Postfix) with ESMTP id C82C214BF1 for ; Wed, 10 Nov 1999 07:53:21 -0800 (PST) (envelope-from myevmenkin@att.com) Received: from njb140r1.ems.att.com ([135.65.202.58]) by almso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id KAA15522; Wed, 10 Nov 1999 10:53:19 -0500 (EST) Received: from njb140bh2.ems.att.com by njb140r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id KAA09517; Wed, 10 Nov 1999 10:52:50 -0500 (EST) Received: by njb140bh2.ems.att.com with Internet Mail Service (5.5.2448.0) id ; Wed, 10 Nov 1999 10:53:19 -0500 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'Luigi Rizzo'" Cc: "'freebsd-hackers@FreeBSD.org'" Subject: RE: Smart user-space Ethernet bridge Date: Wed, 10 Nov 1999 10:53:06 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i agree, but ... we have user space ppp, with all kind of useful things like filter etc. it is slower than kernel ppp, but everybody keep using it. so may be we can build a kind of "smart" bridge. it will touch only specific interfaces, collect information about route to specific MAC's etc. thanks, emax > > I've released Ethernet TAP driver v0.2 for FreeBSD > ... > > Folks, what do you think about smart user-space Ethernet bridge? > > Anyone needs it? > > i think performance is a big problem here (same as in the case of > user-space natd, but worse because a bridge touches all packets). > You have too many data copies. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 7:59:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 3AFA914FA2 for ; Wed, 10 Nov 1999 07:59:22 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id HAA02546; Wed, 10 Nov 1999 07:58:39 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Wed, 10 Nov 1999 07:58:39 -0700 Date: Wed, 10 Nov 1999 07:58:39 -0800 (PST) From: Kip Macy X-Sender: kip@luna To: Reinier Bezuidenhout Cc: freebsd-hackers@freebsd.org Subject: Re: cc -pthread and libc_r question In-Reply-To: <199911101239.OAA23318@oskar.dev.nanoteq.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: rbezuide@oskar.dev.nanoteq.co.za,freebsd-hackers@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Which program was it? A number of programs like tcslh and wish explicitly ask for libc when linking. A practice I have never understood. On Wed, 10 Nov 1999, Reinier Bezuidenhout wrote: > Hi .. > > I've compiled a program with the -pthread compiler option on a > 3.3-STABLe system ... after doing a ldd on the executable I see that > both libc_r AND lic are linked .. is this correct ? > > Shouldn't libc_r replace libc ? > > Thanks > > Reinier > > > 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 Nov 10 8: 9:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailgate.cadence.com (mailgate.Cadence.COM [158.140.2.1]) by hub.freebsd.org (Postfix) with ESMTP id 2471214BC3 for ; Wed, 10 Nov 1999 08:09:46 -0800 (PST) (envelope-from JKN@symbionics.co.uk) Received: (from smap@localhost) by mailgate.cadence.com (8.8.5/8.6.8) id IAA26110 for ; Wed, 10 Nov 1999 08:09:45 -0800 (PST) Received: from symnt3.Cadence.COM(194.32.101.100) by mailgate.cadence.com via smap (mjr-v1.2) id xma942250183.026096; Wed, 10 Nov 99 08:09:43 -0800 Received: by symnt3.cadence.com with Internet Mail Service (5.5.2650.21) id ; Wed, 10 Nov 1999 16:09:31 -0000 Message-ID: <1E485299309FD211A2100090271E27A401809895@symnt3.cadence.com> From: Jon Nicoll To: freebsd-hackers@FreeBSD.ORG Subject: porting Linux kernel module to FreeBSD Date: Wed, 10 Nov 1999 16:09:30 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello There You may have heard that Creative Labs have put the source for the Linux driver for their SoundBlaster Live audio card under GPL (http://opensource.creative.com). This takes the form of a kernel module for Linux. I'm interested in doing (some of? ;-o) the work of porting this module to FreeBSD. I'm not very familiar with some of the issues involved in such a venture; could someone point me to a source of information on the issues that might be involved in doing this? I'm a reasonably experienced hacker but only moderately familiar with either FreeBSD(I have 3.1) or Linux(SuSE 6.2, as it happens). Pointers to FAQs or links very welcome - the FreeBSD site which discusses such things is more about making the distribution, and I'm not that far along yet... Thanks jon Nicoll To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 8:38:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 4530F14BC3 for ; Wed, 10 Nov 1999 08:38:50 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id LAA55850; Wed, 10 Nov 1999 11:38:47 -0500 (EST) Date: Wed, 10 Nov 1999 11:38:47 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Jon Nicoll Cc: freebsd-hackers@freebsd.org Subject: Re: porting Linux kernel module to FreeBSD In-Reply-To: <1E485299309FD211A2100090271E27A401809895@symnt3.cadence.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 Nov 1999, Jon Nicoll wrote: > Hello There > You may have heard that Creative Labs have put the source for the > Linux driver for their SoundBlaster Live audio card under GPL > (http://opensource.creative.com). This takes the form of a kernel module for > Linux. > > I'm interested in doing (some of? ;-o) the work of porting this module to > FreeBSD. I'm not very familiar with some of the issues involved in such a > venture; could someone point me to a source of information on the issues > that might be involved in doing this? I'm a reasonably experienced hacker > but only moderately familiar with either FreeBSD(I have 3.1) or Linux(SuSE > 6.2, as it happens). > > Pointers to FAQs or links very welcome - the FreeBSD site which discusses > such things is more about making the distribution, and I'm not that far > along yet... > I wish you the best of luck with this. You might also want to mention something on freebsd-current, though, since the sound drivers on -current are different than on -stable (ie. you may be needing to upgrade to -current to do your development if you want your work to be incorporated into the source tree). I'm not 100% sure what the differences are (I only read -current, run -stable :) ), but I'm sure someone there could probably point you in the right direction. Nonetheless, when you do get something going on this, take a second an mention your project on http://www.posi.net/freebsd/drivers/ so that others interested might know that a) someone is already working on it and b) offer any assistance you may need. Good luck, Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Director of Technical Services, ALC Communications http://www.alcnet.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 10: 6:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 228451526F for ; Wed, 10 Nov 1999 10:06:38 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id TAA06239 for freebsd-hackers@FreeBSD.ORG; Wed, 10 Nov 1999 19:06:31 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 5832C8711; Wed, 10 Nov 1999 08:08:20 +0100 (CET) Date: Wed, 10 Nov 1999 08:08:20 +0100 From: Ollivier Robert To: freebsd-hackers@FreeBSD.ORG Subject: Re: Should jail treat ip-number? Message-ID: <19991110080820.A39738@keltia.freenix.fr> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <19991110000004.A37063@keltia.freenix.fr> <199911100033.QAA24023@boreas.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <199911100033.QAA24023@boreas.isi.edu> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Ted Faber: > If you're using OSI and betting on IPv6 in the near term, you may be > rowing for the wrong shore. :-) It is more complicated than that. The _current_ equipment is not using anything (neither OSI nor IPv6). There is currently no datalink between ground and airplanes.... It is the next generation (the one for the next century) where some people want to put OSI on ! They have been working for more than 12 years to get OSI working and they still haven't succeeded... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 10:37:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 9464E15021 for ; Wed, 10 Nov 1999 10:36:58 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id KAA42838; Wed, 10 Nov 1999 10:35:47 -0800 (PST) From: Archie Cobbs Message-Id: <199911101835.KAA42838@bubba.whistle.com> Subject: Re: Problem about Raw IP socket In-Reply-To: from Sunthiti Patchararungruang at "Nov 10, 1999 10:42:42 pm" To: stt@pluto.cpe.ku.ac.th (Sunthiti Patchararungruang) Date: Wed, 10 Nov 1999 10:35:47 -0800 (PST) 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 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sunthiti Patchararungruang writes: > I have to create a route program for my thesis. Its operation is different > from normal packet forwarding. Therefore, I need to forward all packets > instead of using normal packet forwarding in FreeBSD kernel. I capture > packets via Divert socket. It works well. I can grap IP packket including > its header. However, I use normal Raw IP socket to write the packets to > selected next-hop. I use socket option SO_DONTROUTE and IP_HDRINCL with my > Raw IP socket and use "sendto" to write packets with "sockaddr" set to the > IP of the next-hop-gateway. The sendto command always return error with > errno=22. How can I solve this error? 22 = EINVAL. That can happen if your IP header is not well-formed. The relevant file is /usr/src/sys/netinet/raw_ip.c. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 11: 6:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw-nl1.origin-it.com (gw-nl1.origin-it.com [193.79.128.34]) by hub.freebsd.org (Postfix) with ESMTP id 76B0D14E16 for ; Wed, 10 Nov 1999 11:06:26 -0800 (PST) (envelope-from Hans.Zuidam@nl.origin-it.com) Received: from mail.nl.origin-it.com (localhost.origin-it.com [127.0.0.1]) by gw-nl1.origin-it.com with ESMTP id UAA24293 for ; Wed, 10 Nov 1999 20:06:25 +0100 (MET) (envelope-from Hans.Zuidam@nl.origin-it.com) Received: from mail.nl.origin-it.com(172.16.127.67) by gw-nl1.origin-it.com via mwrap (4.0a) id xma024291; Wed, 10 Nov 99 20:06:25 +0100 Received: from nlehx900.ehvovh.nl.origin-it.com (nlehx900.ehvovh.nl.origin-it.com [172.16.92.111]) by mail.nl.origin-it.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id UAA08475 for ; Wed, 10 Nov 1999 20:06:24 +0100 (MET) Received: by nlehx900.ehvovh.nl.origin-it.com with Internet Mail Service (5.5.2448.0) id ; Wed, 10 Nov 1999 20:06:23 +0100 Message-ID: <9B7E8CE3E214D311A3050008C7A4BDDB9346C4@nlehx061.ehvvon.nl.origin-it.com> From: "Zuidam, Hans" To: "'hackers@freebsd.org'" Subject: CD-ROM on Compaq Deskpro Date: Wed, 10 Nov 1999 20:06:22 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Further investigating the reason why the CD-ROM is not accessible on a Compaq Deskpro EN (changing the machine was not an option,) I've found the following: o The CD-ROM drive is on the secondary IDE controller, there is no primary controller. The HD is on a SCSI controller (ah2940); o If the drive is jumpered as a slave, the secondary IDE controller is not found by the wdc code, very weird; o If the driver is jumpered as either a master or with cable select the secondary IDE controller is found, the wdc1 controller and the drive are found but subsequently not accessible. This bothered me until I noticed the controller busy status. Somehow when the slave is probed, it fails because there is no slave device, but the controller is left in a busy state from which it (nor the sw.) never recovers: atapi1.1 at 0x170: attach called atapiX.1 at 0x170: controller busy, status=80 So, inserting in atapi_probe() line saying: if (unit > 0) { print(("unit > 0\n", unit)); return 0; } Results in the following: atapi1.1 at 0x170: attach called unit 1 > 0 Subsequently, the CD-ROM can be mounted and used. Sadly I do not know enough about either IDE nor about ATAPI to give a quick answer as to what the reason for the problem could be. If anyone has suggestions for further experiments, I'll be glad to try. Regards, Hans Hans Zuidam e-mail: hans.zuidam@nl.origin-it.com Origin, BAS/AM-CE tel. +31 40 2735569 Gebouw SK-520 fax. +31 40 2736936 Glaslaan 2 5616 LW Eindhoven To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 11:20:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 04705152A4 for ; Wed, 10 Nov 1999 11:19:49 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id LAA57499; Wed, 10 Nov 1999 11:18:59 -0800 (PST) Date: Wed, 10 Nov 1999 11:18:58 -0800 (PST) From: Julian Elischer To: Sunthiti Patchararungruang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Problem about Raw IP socket In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG set up some IPFW rules that select next hops withthe 'fwd' command e.g. 998 divert ..... 1000 skipto 10000 1002 fwd nexthop1 ip from any to any 1004 fwd nexthop2 ip from any to any 1006 fwd nexthop3 ip from any to any 10000 ....... then in the address field of the sendto specify the ( rule# -1) e.g. addr->rulenumber = 1003; /* I can't check the actual fieldname from here */ sendto(divertsock, packet, pcklen, add, addrlen,flags); /* args may be wrong order */ The address struct you get with teh divert should already contain the rule number of the rule that diverted (998). change it to 101 to send to rule 1002 or 1003 to send to rule 1004 etc. On Wed, 10 Nov 1999, Sunthiti Patchararungruang wrote: > Dear Sir, > > I have to create a route program for my thesis. Its operation is different > from normal packet forwarding. Therefore, I need to forward all packets > instead of using normal packet forwarding in FreeBSD kernel. I capture > packets via Divert socket. It works well. I can grap IP packket including > its header. However, I use normal Raw IP socket to write the packets to > selected next-hop. I use socket option SO_DONTROUTE and IP_HDRINCL with my > Raw IP socket and use "sendto" to write packets with "sockaddr" set to the > IP of the next-hop-gateway. The sendto command always return error with > errno=22. How can I solve this error? > > Thank you for all help. > > Regards, > Sunthiti Patchararungruang > > > > > 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 Nov 10 11:35:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 67A6714DDA for ; Wed, 10 Nov 1999 11:35:35 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA32032; Wed, 10 Nov 1999 20:35:31 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199911101935.UAA32032@freebsd.dk> Subject: Re: CD-ROM on Compaq Deskpro In-Reply-To: <9B7E8CE3E214D311A3050008C7A4BDDB9346C4@nlehx061.ehvvon.nl.origin-it.com> from "Zuidam, Hans" at "Nov 10, 1999 08:06:22 pm" To: Hans.Zuidam@nl.origin-it.com (Zuidam, Hans) Date: Wed, 10 Nov 1999 20:35:31 +0100 (CET) Cc: hackers@FreeBSD.ORG ('hackers@freebsd.org') X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Zuidam, Hans wrote: > Hi, > > Further investigating the reason why the CD-ROM is not accessible > on a Compaq Deskpro EN (changing the machine was not an option,) > I've found the following: > > o The CD-ROM drive is on the secondary IDE controller, > there is no primary controller. The HD is on a SCSI > controller (ah2940); > > o If the drive is jumpered as a slave, the secondary IDE > controller is not found by the wdc code, very weird; > > o If the driver is jumpered as either a master or with > cable select the secondary IDE controller is found, the > wdc1 controller and the drive are found but subsequently > not accessible. This is a known "feature" of the old wd based driver, if you are/can use -current, use the new ata driver, that should do the trick. -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 Nov 10 12:57:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id C2EC114E16 for ; Wed, 10 Nov 1999 12:57:12 -0800 (PST) (envelope-from mb@imp.ch) Received: from mephisto.imp.ch (mb@mephisto.imp.ch [157.161.1.22]) by mail.imp.ch (8.9.3/8.9.3) with ESMTP id VAA07178 for ; Wed, 10 Nov 1999 21:57:04 +0100 (MET) Received: from localhost (mb@localhost) by mephisto.imp.ch (8.9.3/8.9.3) with ESMTP id VAA02593 for ; Wed, 10 Nov 1999 21:57:02 +0100 (MEZ) Date: Wed, 10 Nov 1999 21:57:02 +0100 From: Martin Blapp To: hackers@freebsd.org Subject: HEADS UP: new command rpc.umntall in usr.sbin Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The BSD mountd(8) implementation has some design issues. It tries to call RPC.UMNTALL on SIGTERM. According to RFC 1813 it is 1. A bad idea to use broadcast RPC to do the UMNTALL. 2. Beside that our broadcast RPC implementation does use a port remapping on the remote portmapper. The port remapping is done to unprivileged ports. That explains the syslog messages we have all seen a lot: umountall request from 192.168.0.1 from unprivileged port Just a note: 192.168.0.1 is the IP adress from the server itself. This is completly wrong. The original hostaddress get's lost, the server seems to call itself to remove it's mounts. Heh. 3. It is just stupid to call RPC_UMNTALL from mountd. Running a NFS server does not mean we have NFS clients on the machine. 4. RPC_UMNTALL should be called on startup. I've modified our init(8) a little bit that we can see in rc.shutdown if we go to singleuser or not. You'll find the patches on this URL: http://www.attic.ch/patches/rpc.umntall/ Thank you for comments and suggestions. Martin Note: The userland patch has also some ISO network stuff removed. I've asked bde about that and he agreed. Attached it some part of RFC 1813: 5.2.4 Procedure 4: UMNTALL - Remove all mount entries SYNOPSIS void MOUNTPROC3_UMNTALL(void) = 4; DESCRIPTION Procedure UMNTALL removes all of the mount entries for this client previously recorded by calls to MNT. AUTH_UNIX authentication or better is required. IMPLEMENTATION This procedure should be used by clients when they are recovering after a system shutdown. If the client could not successfully unmount all of its file systems before being shutdown or the client crashed because of a software or hardware problem, there may be servers which still have mount entries for this client. This is an easy way for the client to inform all servers at once that it does not have any mounted file systems. However, since this procedure is generally implemented using broadcast RPC, it is only of limited usefullness. ERRORS There are no MOUNT protocol errors which can be returned from this procedure. However, RPC errors may be returned for authentication or other RPC failures. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 13: 7:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 4757414DC0 for ; Wed, 10 Nov 1999 13:07:35 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.3/8.9.1) id NAA14317; Wed, 10 Nov 1999 13:07:52 -0800 (PST) (envelope-from ulf) Date: Wed, 10 Nov 1999 13:07:52 -0800 From: Ulf Zimmermann To: "Roman V. Palagin" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: What's happen with anoncvs.freebsd.org? Message-ID: <19991110130751.D77202@PacHell.TelcoSucks.org> Reply-To: ulf@Alameda.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from romanp@wuppy.net.ru on Wed, Nov 10, 1999 at 05:56:20PM +0300 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 10, 1999 at 05:56:20PM +0300, Roman V. Palagin wrote: > Hello! > > I don't know, is it appropriate group to ask this question, but anyway: > when I try to check out /usr/src/sys from anoncvs.freebsd.org, I just get > > % cvs co sys > /ctm/FreeBSD/anoncvs/anoncvssh: No such file or directory > cvs [checkout aborted]: end of file from server (consult above messages if any) > % > > Who can tell me is there are any chances to get things work again? anoncvs.FreeBSD.org crashed and lost its vinum /ctm filesystem. Chuckr and Markm are working on restoring it. > > /Roman > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 13:40:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eh.est.is (eh.est.is [194.144.208.34]) by hub.freebsd.org (Postfix) with ESMTP id 4554814E86 for ; Wed, 10 Nov 1999 13:39:54 -0800 (PST) (envelope-from totii@est.is) Received: from toti.est.is (toti.est.is [194.144.208.241]) by eh.est.is (8.8.8/8.8.8) with ESMTP id VAA16418; Wed, 10 Nov 1999 21:39:52 GMT (envelope-from totii@est.is) Received: from est.is (asus.est.is [194.144.208.242]) by toti.est.is (8.9.3/8.9.1) with ESMTP id VAA19832; Wed, 10 Nov 1999 21:39:47 GMT (envelope-from totii@est.is) Message-ID: <3829E61D.64EFAEDE@est.is> Date: Wed, 10 Nov 1999 21:39:41 +0000 From: Thordur Ivarsson Reply-To: thivars@est.is X-Mailer: Mozilla 4.08 [en] (Win98; I) MIME-Version: 1.0 To: Ollivier Robert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Should jail treat ip-number? References: <19991110000004.A37063@keltia.freenix.fr> <199911100033.QAA24023@boreas.isi.edu> <19991110080820.A39738@keltia.freenix.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert wrote: > > According to Ted Faber: > > If you're using OSI and betting on IPv6 in the near term, you may be > > rowing for the wrong shore. :-) > > It is more complicated than that. > > The _current_ equipment is not using anything (neither OSI nor IPv6). There is > currently no datalink between ground and airplanes.... ??? I thought SITA used some parts of the OSI model for their data transmitting system, I installed such station here in Iceland 10 years ago and the technician told me that it worked very similar to radio amateur packet, AX25, which is OSI model application. Am I right, or not following ? > It is the next generation (the one for the next century) where some people > want to put OSI on ! They have been working for more than 12 years to get OSI > working and they still haven't succeeded... > -- Thordur Ivarsson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 15:47:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A92F414E1E for ; Wed, 10 Nov 1999 15:47:21 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA15591; Wed, 10 Nov 1999 15:47:35 -0800 Date: Wed, 10 Nov 1999 15:47:34 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jason Thorpe Cc: current-users@netbsd.org, freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD FibreChannel support In-Reply-To: <199911050142.RAA18728@lestat.nas.nasa.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 4 Nov 1999 17:21:18 -0800 (PST) > Matthew Jacob wrote: > > > > ...especially considering that a fair number of previously happy > > > Qlogic ISP users now have completely useless boards. > > > > No, that's not correct either. Here's an editted copy of what I sent to > > Well, it is. At least some AlphaStation 500 owners have reported > previously (i.e. before you changed the driver to always upload > the firmware!) that the ISP driver did NOT work with the version of > the firmware flashed into the board. > Well, the AlphaStation 600 reports: Qlogic ISP Driver, NetBSD (pci) Platform Version 0.997 Core Version 1.10 isp0: interrupting at kn20aa irq 17 isp0: Board Revision 1020A, resident F/W Revision 5.1.1 isp0: Last F/W revision was 5.1.1 isp0: 274 max I/O commands supported isp0: invalid NVRAM header (c0,f8,c0,f8) isp0: driver initiated bus reset of bus 0 scsibus0 at isp0: 16 targets, 8 luns per target isp1 at pci1 dev 2 function 0 isp1: interrupting at kn20aa irq 18 isp1: Board Revision 1020A, resident F/W Revision 5.1.1 isp1: Last F/W revision was 5.1.1 isp1: 274 max I/O commands supported isp1: invalid NVRAM header (ff,ff,ff,ff) isp1: driver initiated bus reset of bus 0 scsibus1 at isp1: 16 targets, 8 luns per target pceb0 at pci0 dev 10 function 0: Intel 82375EB/SB PCI-EISA Bridge (PCEB) (rev. 0x15) and works just fine..... And for the AlphaStation 500: Qlogic ISP Driver, FreeBSD Version 4.0, Core Version 1.10 isp0: irq 12 at device 9.0 on pci0 isp0: interrupting at CIA irq 12 isp0: Board Revision 1020A, resident F/W Revision 5.1.1 isp0: Last F/W revision was 5.1.1 isp0: 274 max I/O commands supported isab0: at device 10.0 on pci0 isa0: on isab0 that also works fine, so w/o actually getting some PRs (and I haven't seen any) or email directly too me, I'm kinda thinking that what you say is a bit of a crock. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 20: 9:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 1D34D14EA4 for ; Wed, 10 Nov 1999 20:09:07 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id FAA02353 for freebsd-hackers@FreeBSD.ORG; Thu, 11 Nov 1999 05:09:06 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 8CF5C878D; Thu, 11 Nov 1999 00:40:07 +0100 (CET) Date: Thu, 11 Nov 1999 00:40:07 +0100 From: Ollivier Robert To: freebsd-hackers@FreeBSD.ORG Subject: Re: Should jail treat ip-number? Message-ID: <19991111004007.A44926@keltia.freenix.fr> Reply-To: FreeBSD Chat Mailing List Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <19991110000004.A37063@keltia.freenix.fr> <199911100033.QAA24023@boreas.isi.edu> <19991110080820.A39738@keltia.freenix.fr> <3829E61D.64EFAEDE@est.is> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <3829E61D.64EFAEDE@est.is> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ getting off-topic, redirected to -chat ] According to Thordur Ivarsson: > ??? I thought SITA used some parts of the OSI model for their data > transmitting system, I installed such station here in Iceland 10 years > ago and the technician told me that it worked very similar to radio > amateur packet, AX25, which is OSI model application. For the SITA network probably but not for air-ground communications. Nothing close to a datalink is operational right now. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 20: 9:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id CFBBE15424 for ; Wed, 10 Nov 1999 20:09:10 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id FAA02354 for hackers@freebsd.org; Thu, 11 Nov 1999 05:09:10 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 57CC18711; Thu, 11 Nov 1999 00:45:52 +0100 (CET) Date: Thu, 11 Nov 1999 00:45:52 +0100 From: Ollivier Robert To: hackers@freebsd.org Subject: Re: mode_perl DSO works on STABLE, not CURRENT Message-ID: <19991111004552.B44926@keltia.freenix.fr> Mail-Followup-To: hackers@freebsd.org References: <600.942223977@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <600.942223977@axl.noc.iafrica.com> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Sheldon Hearn: > | Syntax error on line 261 of /usr/local/etc/apache/httpd.conf: > | Can't load '/usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/MD5/MD5.so' for module MD5: /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/MD5/MD5.so: Undefined symbol "PL_markstack_ptr" at /usr/libdata/perl/5.00503/DynaLoader.pm line 169. Your Perl binary is compiled without '-Wl,-E' (or '-Wl,--export-dynamic'). Without this option the Perl binary doesn't expoert its symbols thus preventing any dynamically loaded module to use anything from the binary. The official Perl distribution and the one in CURRENT (and 3.3-STABLE) have been fixed a long time ago. /usr/src/contrib/perl5/hints/freebsd.sh: -=-=- # Support for FreeBSD/ELF # Ollivier Robert # Date: Wed Sep 2 16:22:12 CEST 1998 ... 3.*|4.0*) objformat=`/usr/bin/objformat` if [ x$objformat = xelf ]; then libpth="/usr/lib /usr/local/lib" glibpth="/usr/lib /usr/local/lib" ldflags="-Wl,-E " lddlflags="-shared " else if [ -e /usr/lib/aout ]; then libpth="/usr/lib/aout /usr/local/lib /usr/lib" glibpth="/usr/lib/aout /usr/local/lib /usr/lib" fi lddlflags='-Bshareable' fi cccdlflags='-DPIC -fpic' ;; ... -=-=- -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 10 21:51:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from agni.wipinfo.soft.net (agni.wipinfo.soft.net [164.164.6.20]) by hub.freebsd.org (Postfix) with ESMTP id 408C914C24 for ; Wed, 10 Nov 1999 21:51:19 -0800 (PST) (envelope-from santoshm@wipinfo.soft.net) Received: from vayu.wipinfo.soft.net (vayu [192.168.200.170]) by agni.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id LAA09124 for ; Thu, 11 Nov 1999 11:21:13 +0500 (GMT) Received: from tagore.wipinfo.soft.net (ncrtagore.wipinfo.soft.net [192.168.205.3]) by vayu.wipinfo.soft.net (8.9.3/8.9.3) with SMTP id LAA11475 for <@vayu:freebsd-hackers@FreeBSD.ORG>; Thu, 11 Nov 1999 11:21:36 +0500 (GMT) Date: Thu, 11 Nov 1999 11:29:57 +0530 (IST) From: "Santhosh Kumar M [CEC-S]" X-Sender: santoshm@tagore To: freebsd-hackers@FreeBSD.ORG Subject: A Question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Can anyone give me the library call or system calls by which i can get all the IP address configured on a local system (Note: the system can be multihomed adapters). P.S: I am not a member of this list, so please do a cc to "santoshm@wipinfo.soft.net". Thanks & Rdgs Santhosh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 0: 5:54 1999 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 D0BF314D64 for ; Thu, 11 Nov 1999 00:05:44 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 11 Nov 1999 08:05:43 +0000 (GMT) Date: Thu, 11 Nov 1999 08:05:40 +0000 From: David Malone To: "Santhosh Kumar M [CEC-S]" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: A Question Message-ID: <19991111080540.A58543@walton.maths.tcd.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 11, 1999 at 11:29:57AM +0530, Santhosh Kumar M [CEC-S] wrote: > Can anyone give me the library call or system calls by which i can > get all the IP address configured on a local system (Note: the system can > be multihomed adapters). Here is a program I wrote to try to see how to find the addresses of all the interfaces. It's based on rwhod and reading how the kernel does it. I think I'm doing it the correct way, but it isn't pretty. David. #include #include #include #include #include #include #include #include #include #include #include #include /* * This is an example of how to find info about the currently configured * interfaces. * * The code in rwhod and ifconfig if pretty hard to understand as it * doesn't really exploit the structure of what you're returned. We use * a sysctl to get the interface list, which returns a buffer with a * list of things each starting with: * * msglen * version * type * * The generic type used to with this start in the kernel seems to be * "struct rt_msghdr". For this sysctl we call it returns a message of * type RTM_IFINFO followed by a list of RTM_NEWADDR for each interface. * This corrisponds to the interface and each of the configurations you * "put" on it with ifconfig. * * The RTM_IFINFO message contains a struct if_msghdr followed by a * list of struct sockaddr. The RTM_NEWADDR contains a struct ifa_msghdr * followed by a list of struct sockaddr. * * The struct sockaddr's sizes have been truncated to the nearest * power of two into which the data will fit. The struct sockaddr's * included depend on what is apropriate to this message. You can tell * which of RTAX_* sockaddr's have been included by looking at the set * bits of ifm_addrs or ifam_addrs, so you have to expand them out into * an array of struct sockaddr's of size RTAX_MAX. */ void unpack_addrs(struct sockaddr *packed,struct sockaddr *unpacked,int rti_addrs); void print_addrs(struct sockaddr *unpacked,int rti_addrs); int main(int argc, char **argv) { char *buf, *lim, *next; /* For sysctl */ size_t needed; int mib[6]; struct rt_msghdr *rtm; /* For decoding messages */ struct if_msghdr *ifm; struct ifa_msghdr *ifam; struct sockaddr *packed_addr; /* For decoding addresses */ struct sockaddr unpacked_addr[RTAX_MAX]; mib[0] = CTL_NET; mib[1] = PF_ROUTE; mib[2] = 0; mib[3] = AF_INET; mib[4] = NET_RT_IFLIST; mib[5] = 0; if (sysctl(mib, 6, NULL, &needed, NULL, 0) < 0) errx(1, "route-sysctl-estimate"); if ((buf = malloc(needed)) == NULL) errx(1, "malloc"); if (sysctl(mib, 6, buf, &needed, NULL, 0) < 0) errx(1, "actual retrieval of interface table"); lim = buf + needed; for( next = buf; next < lim; next += rtm->rtm_msglen ) { rtm = (struct rt_msghdr *)next; switch( rtm->rtm_type ) { case RTM_IFINFO: ifm = (struct if_msghdr *)next; packed_addr = (struct sockaddr *)(next + sizeof(struct if_msghdr)); printf("Found an interface.\n"); if( ifm->ifm_flags & IFF_UP ) printf("It is currently up.\n"); if( ifm->ifm_addrs != 0 ) { printf("These addresses were available:\n"); unpack_addrs(packed_addr,unpacked_addr, ifm->ifm_addrs); print_addrs(unpacked_addr,ifm->ifm_addrs); } else printf("No addresses were available.\n"); break; case RTM_NEWADDR: ifam = (struct ifa_msghdr *)next; packed_addr = (struct sockaddr *)(next + sizeof(struct ifa_msghdr)); printf("Found extra addresses associated with interface.\n"); unpack_addrs(packed_addr,unpacked_addr, ifam->ifam_addrs); print_addrs(unpacked_addr,ifam->ifam_addrs); break; default: errx(1, "unexpected rtm type"); } } exit(0); } #define ROUNDUP(a) \ ((a) > 0 ? (1 + (((a) - 1) | (sizeof(long) - 1))) : sizeof(long)) void unpack_addrs(struct sockaddr *packed,struct sockaddr *unpacked,int rti_addrs) { int i; for( i = 0; i < RTAX_MAX; i++ ) { bzero(&unpacked[i],sizeof(unpacked[i])); if( rti_addrs & (1<sa_len); packed = (struct sockaddr *)(((char *)packed) + ROUNDUP(packed->sa_len)); } } } void print_addrs(struct sockaddr *unpacked,int rti_addrs) { int i; for( i = 0; i < RTAX_MAX; i++ ) { if( (rti_addrs & (1<sin_addr)); break; default: printf("address in family %d", unpacked[i].sa_family); break; } printf(".\n"); } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 1: 5:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (Postfix) with ESMTP id 37AAB15453 for ; Thu, 11 Nov 1999 01:05:30 -0800 (PST) (envelope-from eT@post.com) Received: (from root@localhost) by Thingol.KryptoKom.DE (8.9.1/8.9.1) id KAA32051 for ; Thu, 11 Nov 1999 10:01:15 +0100 Received: from cirdan.kryptokom.de by KryptoWall via smtpp (Version 1.2.0) id kwa32039; Thu Nov 11 10:00:53 1999 Received: from post.com (Mbeki.KryptoKom.DE [192.168.6.249]) by cirdan.kryptokom.de (8.9.3/8.8.8) with ESMTP id KAA05519 for ; Thu, 11 Nov 1999 10:05:11 +0100 Message-ID: <382A86B8.915EC497@post.com> Date: Thu, 11 Nov 1999 10:04:57 +0100 From: eT X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: One bit error on BUS? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What could the possible explanation be in the following scenario: We have: arbitrary chip <---localbus---> pci controller <===pcibus===> BX Motherboard <------> RAM And somewhere in the transfer of blocks of data between the chip (on the left) and the RAM on the right we have random one bit errors. we means that for huge streams of transfer all might be ok and at random intervals exactely one bit will be set incorrectly (not always the same bit in the byte). We have a 440BX motherboard with a PII400. Is it a timing problem on data transfer on the local bus or pci bus? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 7:10:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 04E7A14D3A for ; Thu, 11 Nov 1999 07:10:44 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id KAA21347 for ; Thu, 11 Nov 1999 10:10:43 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA23674; Thu, 11 Nov 1999 10:10:13 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id KAA96198 for freebsd-hackers@freebsd.org; Thu, 11 Nov 1999 10:10:13 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199911111510.KAA96198@bb01f39.unx.sas.com> Subject: Wine: What am I missing (lseek/write) To: freebsd-hackers@freebsd.org Date: Thu, 11 Nov 1999 10:10:13 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm working on wine on a 4.0-19990827-SNAP system. The application I have calls WriteFile(), in files/file.c, line 1145. The write() call is failing with: WriteFile: File too large[27] Note: I added the fprintf() to show the above... Well, this is happenning on filedesc 14, so for grins I added the following just above the write call: if (unix_handle == 14) { off_t x = lseek(unix_handle, 0, SEEK_CUR); if (x == -1) fprintf(stderr,"WriteFile lseek %s[%d]\n",strerror(errno),errno); else fprintf(stderr,"WriteFile fd:14 SEEK_CUR,0 == %ld\n",x); } It shows: WriteFile lseek No such file or directory[2] Somewhere, somehow, I'm missing something... I've run wine with -debugmsg and I can't find any errors... I've ktraced wine to make sure the syscall parameters are correct... Any pointers or ideas on where to take this would be appreciated. Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 9: 0: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 4521615494 for ; Thu, 11 Nov 1999 09:00:01 -0800 (PST) (envelope-from crandall@matchlogic.com) Received: by houston.matchlogic.com with Internet Mail Service (5.5.2650.21) id ; Thu, 11 Nov 1999 10:00:00 -0700 Message-ID: <64003B21ECCAD11185C500805F31EC0304621CAC@houston.matchlogic.com> From: Charles Randall To: freebsd-hackers@FreeBSD.ORG Subject: RE: A Question Date: Thu, 11 Nov 1999 09:59:59 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From a shell, % /sbin/ifconfig -a that's not exactly what you were looking for, but... Charles -----Original Message----- From: Santhosh Kumar M [CEC-S] [mailto:santoshm@wipinfo.soft.net] Sent: Wednesday, November 10, 1999 11:00 PM To: freebsd-hackers@FreeBSD.ORG Subject: A Question Hi, Can anyone give me the library call or system calls by which i can get all the IP address configured on a local system (Note: the system can be multihomed adapters). P.S: I am not a member of this list, so please do a cc to "santoshm@wipinfo.soft.net". Thanks & Rdgs Santhosh 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 Nov 11 9:15:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.vr.IN-Berlin.DE (gnu.in-berlin.de [192.109.42.4]) by hub.freebsd.org (Postfix) with ESMTP id 9C43C14D6F for ; Thu, 11 Nov 1999 09:15:29 -0800 (PST) (envelope-from server.nostromo.in-berlin.de!ripley@servicia.in-berlin.de) Received: from uriela.in-berlin.de (IDENT:root@servicia.in-berlin.de [192.109.42.145]) by mail.vr.IN-Berlin.DE (8.9.3/8.9.3) with ESMTP id SAA08242 for ; Thu, 11 Nov 1999 18:15:26 +0100 (CET) (envelope-from server.nostromo.in-berlin.de!ripley@servicia.in-berlin.de) Received: by uriela.in-berlin.de (Smail-3.2.0.101 1997-Dec-17 #1) id m11lzKN-000VRJC; Thu, 11 Nov 1999 19:52:11 +0100 (CET) Received: (from ripley@localhost) by server.nostromo.in-berlin.de (8.9.3/8.9.3) id BAA49688 for freebsd-hackers@FreeBSD.ORG; Thu, 11 Nov 1999 01:08:38 +0100 (CET) (envelope-from ripley) Date: Thu, 11 Nov 1999 01:08:37 +0100 From: "H. Eckert" To: freebsd-hackers@FreeBSD.ORG Subject: Re: Should jail treat ip-number? Message-ID: <19991111010837.C48604@server.nostromo.in-berlin.de> References: <199911090824.KAA90295@zibbi.mikom.csir.co.za> <22398.942136151@critter.freebsd.dk> <19991110000004.A37063@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.6i In-Reply-To: <19991110000004.A37063@keltia.freenix.fr>; from Ollivier Robert on Wed, Nov 10, 1999 at 12:00:04AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Ollivier Robert (roberto@keltia.freenix.fr): > - the larger address space enables one to avoid the NAT abomination, Actually I like the fact very much that I can put my other machines behind my NAT gateway and have them not exposed too much into the public side of the network. If my gateway host was just a network media translator (as in ISDN to ethernet router) and the other machines had real IP's, they would be easibly addressable from the outside. Greetings, Ripley -- H. Eckert, 10777 Berlin, Germany, http://www.in-berlin.de/User/nostromo/ ISO 8859-1: Ä=Ae, Ö=Oe, Ü=Ue, ä=ae, ö=oe, ü=ue, ß=sz. "(Technobabbel)" (Jetrel) - "Müssen wir uns diesen Schwachsinn wirklich anhören?" (Neelix) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 12:12:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 5D68414F33 for ; Thu, 11 Nov 1999 12:11:51 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id UAA07198 for hackers@freebsd.org; Thu, 11 Nov 1999 20:11:49 GMT (envelope-from joe) Date: Thu, 11 Nov 1999 20:11:49 +0000 From: Josef Karthauser To: hackers@freebsd.org Subject: Severe problems with softupdates. Message-ID: <19991111201148.A5748@florence.pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, I'm still trying to recover my laptop from a really severe filesystem crash using softupdates. The machine hung due to a problem with power managment so it needed a reboot. Now fsck won't clean up without complaining bitterly about 'softupdate' problems, ultimately coming to a halt with a 'can't find inode XXXX' message. I've confirmed with fsdb that the inode in question does exist, so why is fsck complaining? Clearing the inode in question allows fsck to proceed, and ultimately land on another inode that exists, but it "can't find". I've searched the lists and this message appear to reference the same problem: Date: Wed, 20 Oct 1999 01:58:31 -0400 (EDT) From: "Joe \"Marcus\" Clarke" To: Mark Powell Cc: freebsd-questions@FreeBSD.ORG Subject: Re: How to fix cant load /kernel ???? Also soft updates fs corruption. Message-ID: In-Reply-To: I'm running -current; I don't know what Mark was running. Kirk mentioned that he was confident that softupdates was 'safe', but I've had files (from a previous crash - recovered from) in lost+found that I didn't touch, and no-way should have become disconnected from the file system - they weren't even in buffercache at the time of the crash. I believe that Brian has also had the same problems (at FreeBSDCon). Can people put their hands up if they believe that they've experienced this so that we can determine whether there's a deeper softupdates problem that we're ignoring on faith? Also if anyone knows how to recover from it I'd be very grateful to know. My /usr partition is uncleanable (although I can 'mount -f' it!! nasty!!). Joe. -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 12:27:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from [132.197.97.45] (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id 1F2D514A2F for ; Thu, 11 Nov 1999 12:27:25 -0800 (PST) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by [132.197.97.45] (8.9.3/8.9.3) id PAA49818; Thu, 11 Nov 1999 15:26:37 -0500 (EST) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19991111201148.A5748@florence.pavilion.net> Date: Thu, 11 Nov 1999 15:26:36 -0500 (EST) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: Josef Karthauser Subject: RE: Severe problems with softupdates. Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I almost lost my /var partition with exactly the same sequence of events. My desktop mashine failed to wake up from power-save mode and had to be rebooted with the reset button. When system was booting, /var filesystem was not mounted due to the massive amount of 'can't find inode' errors. fsck -y run fine, but I found that absolutely all subdirs were disconnected from the filesystem root and they ended in the lost+found directory. On 11-Nov-99 Josef Karthauser wrote: > Hi guys, > > I'm still trying to recover my laptop from a really severe filesystem > crash using softupdates. The machine hung due to a problem with > power managment so it needed a reboot. Now fsck won't clean up without > complaining bitterly about 'softupdate' problems, ultimately coming to > a halt with a 'can't find inode XXXX' message. I've confirmed with fsdb > that the inode in question does exist, so why is fsck complaining? Clearing > the inode in question allows fsck to proceed, and ultimately land on another > inode that exists, but it "can't find". > > I've searched the lists and this message appear to reference the same > problem: > > Date: Wed, 20 Oct 1999 01:58:31 -0400 (EDT) > From: "Joe \"Marcus\" Clarke" > To: Mark Powell > Cc: freebsd-questions@FreeBSD.ORG > Subject: Re: How to fix cant load /kernel ???? Also soft updates fs > corruption. > Message-ID: > In-Reply-To: > > I'm running -current; I don't know what Mark was running. > > Kirk mentioned that he was confident that softupdates was 'safe', but I've > had files (from a previous crash - recovered from) in lost+found that I > didn't touch, and no-way should have become disconnected from the file > system - they weren't even in buffercache at the time of the crash. > > I believe that Brian has also had the same problems (at FreeBSDCon). > > Can people put their hands up if they believe that they've experienced this > so that we can determine whether there's a deeper softupdates problem that > we're ignoring on faith? > > Also if anyone knows how to recover from it I'd be very grateful to know. > My /usr partition is uncleanable (although I can 'mount -f' it!! nasty!!). > > Joe. > -- > Josef Karthauser FreeBSD: How many times have you booted today? > Technical Manager Viagra for your server (http://www.uk.freebsd.org) > Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, > joe@tao.org.uk] > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message ---------------------------------- E-Mail: Alexander N. Kabaev Date: 11-Nov-99 Time: 15:19:33 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 14: 4:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 7B39C14EF1 for ; Thu, 11 Nov 1999 14:04:14 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id RAA00999 for ; Thu, 11 Nov 1999 17:11:45 -0500 (EST) Date: Thu, 11 Nov 1999 17:11:45 -0500 (EST) From: Ben Rosengart To: hackers@freebsd.org Subject: make -jN world; how to determine optimal value of N? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone know of a method for determining the optimal number of concurrent jobs with which to make world (or anything else for that matter), given the amount of RAM, speed of processor, version of FreeBSD, speed and layout of disk(s), etc.? -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 14:32:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 99B2F14EBC for ; Thu, 11 Nov 1999 14:32:48 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id XAA18224 for freebsd-hackers@FreeBSD.ORG; Thu, 11 Nov 1999 23:32:44 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 3B2788711; Thu, 11 Nov 1999 20:52:38 +0100 (CET) Date: Thu, 11 Nov 1999 20:52:38 +0100 From: Ollivier Robert To: freebsd-hackers@FreeBSD.ORG Subject: Re: Should jail treat ip-number? Message-ID: <19991111205238.A52039@keltia.freenix.fr> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <199911090824.KAA90295@zibbi.mikom.csir.co.za> <22398.942136151@critter.freebsd.dk> <19991110000004.A37063@keltia.freenix.fr> <19991111010837.C48604@server.nostromo.in-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <19991111010837.C48604@server.nostromo.in-berlin.de> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to H. Eckert: > Actually I like the fact very much that I can put my other > machines behind my NAT gateway and have them not exposed too NAT breaks too many things (like IPsec, incoming connections and many protocols) to be anything else than an abomination in my eyes. YMMV of course. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 14:50:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from foo.sics.se (foo.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 162F014FB5 for ; Thu, 11 Nov 1999 14:50:28 -0800 (PST) (envelope-from assar@foo.sics.se) Received: (from assar@localhost) by foo.sics.se (8.9.3/8.9.3) id XAA00516; Thu, 11 Nov 1999 23:50:26 +0100 (CET) (envelope-from assar) To: Ben Rosengart Cc: hackers@FreeBSD.ORG Subject: Re: make -jN world; how to determine optimal value of N? References: From: Assar Westerlund Date: 11 Nov 1999 23:50:26 +0100 In-Reply-To: Ben Rosengart's message of "Thu, 11 Nov 1999 17:11:45 -0500 (EST)" Message-ID: <5ld7tg8wy5.fsf@foo.sics.se> Lines: 9 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Rosengart writes: > Does anyone know of a method for determining the optimal number of > concurrent jobs with which to make world (or anything else for that > matter), given the amount of RAM, speed of processor, version of > FreeBSD, speed and layout of disk(s), etc.? Try it and measure? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 14:52:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id BC7C814F3E for ; Thu, 11 Nov 1999 14:52:34 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id RAA01313; Thu, 11 Nov 1999 17:59:29 -0500 (EST) Date: Thu, 11 Nov 1999 17:59:29 -0500 (EST) From: Ben Rosengart To: Assar Westerlund Cc: hackers@FreeBSD.ORG Subject: Re: make -jN world; how to determine optimal value of N? In-Reply-To: <5ld7tg8wy5.fsf@foo.sics.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11 Nov 1999, Assar Westerlund wrote: > Ben Rosengart writes: > > Does anyone know of a method for determining the optimal number of > > concurrent jobs with which to make world (or anything else for that > > matter), given the amount of RAM, speed of processor, version of > > FreeBSD, speed and layout of disk(s), etc.? > > Try it and measure? D'oh -- I *meant* to add "besides trying different values and measuring" -- if I had that much time on my hands, I wouldn't be worrying about how long a make world takes. :-) -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 14:55:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt054n7c.san.rr.com (dt054n7c.san.rr.com [24.30.152.124]) by hub.freebsd.org (Postfix) with ESMTP id 96E1914F3E for ; Thu, 11 Nov 1999 14:55:34 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gateway.gorean.org (gateway.gorean.org [10.0.0.1]) by dt054n7c.san.rr.com (8.9.3/8.8.8) with ESMTP id OAA37978 for ; Thu, 11 Nov 1999 14:55:31 -0800 (PST) (envelope-from Doug@gorean.org) Date: Thu, 11 Nov 1999 14:55:01 -0800 (PST) From: Doug Barton X-Sender: doug@dt054n7c.san.rr.com To: freebsd-hackers@freebsd.org Subject: Serious locking problem over NFS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, The following small program illustrates an obscure problem with file locking with freebsd as an NFS client. I'm aware of the problems with NFS client side locking, but this is a slightly different problem. If you compile this program, then place it on the NFS server machine and access it twice from the same NFS client, it does what you'd expect, namely the second process hangs till the first releases the lock. However if you run this program from two different FreeBSD NFS clients, both clients get a lock, which is bad. This is true whether all 3 machines are freebsd, or if two clients are freebsd and the server is sun (which is how our machines are set up in reality). However, if two sun clients run the binary located on a sun server, it works as expected, namely the second one hangs till the first one releases the lock. Any insights into this situation are welcome, including suggestions on different ways to do the locking that will work over freebsd. Of course, if there is a bug in our NFS code fixing that would be a good thing too. I'm a bit behind on my FreeBSD mail, so my apologies if this has come up recently. Thanks in advance for any help or suggestions. Doug -- "Stop it, I'm gettin' misty." - Mel Gibson as Porter, "Payback" #include #include #include int main( int argc, char *argv[] ) { int fd; struct flock fl; fd = open( "test.lck", O_CREAT | O_TRUNC | O_WRONLY, 0644 ); fl.l_type = F_WRLCK; fl.l_whence = SEEK_SET; fl.l_start = 0; fl.l_len = 1; fcntl( fd, F_SETLKW, &fl ); printf( "Got lock\n" ); sleep( 30 ); fl.l_type = F_UNLCK; fcntl( fd, F_SETLKW, &fl ); close( fd ); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 15: 1:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from foo.sics.se (foo.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 62BD714E4A for ; Thu, 11 Nov 1999 15:01:12 -0800 (PST) (envelope-from assar@foo.sics.se) Received: (from assar@localhost) by foo.sics.se (8.9.3/8.9.3) id AAA00564; Fri, 12 Nov 1999 00:01:19 +0100 (CET) (envelope-from assar) To: Ben Rosengart Cc: hackers@FreeBSD.ORG Subject: Re: make -jN world; how to determine optimal value of N? References: From: Assar Westerlund Date: 12 Nov 1999 00:01:18 +0100 In-Reply-To: Ben Rosengart's message of "Thu, 11 Nov 1999 17:59:29 -0500 (EST)" Message-ID: <5lzowk7hvl.fsf@foo.sics.se> Lines: 13 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Rosengart writes: > D'oh -- I *meant* to add "besides trying different values and measuring" > -- if I had that much time on my hands, I wouldn't be worrying about how > long a make world takes. :-) I think trying to come up with a formula for calculating the optimal value based on the amount of RAM, type of CPU, speed of CPU, version of BSD, number, speeds, layout(s), previsous contents of *... etc is really much harder than to measure it. Other than that, I think the `make -j4' suggested for a single CPU in the handbook is a fairly good approximation. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 15: 9:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id A0F6214F77 for ; Thu, 11 Nov 1999 15:09:43 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id SAA01466; Thu, 11 Nov 1999 18:16:42 -0500 (EST) Date: Thu, 11 Nov 1999 18:16:42 -0500 (EST) From: Ben Rosengart To: Assar Westerlund Cc: hackers@freebsd.org Subject: Re: make -jN world; how to determine optimal value of N? In-Reply-To: <5lzowk7hvl.fsf@foo.sics.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12 Nov 1999, Assar Westerlund wrote: > Other than that, I think the > `make -j4' suggested for a single CPU in the handbook is a fairly good > approximation. On what basis? I usually use larger values, like 12, on the theory that I have more than enough memory, and if there's free CPU, there should always be a process available to use it. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 15:59:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id CA97314F68 for ; Thu, 11 Nov 1999 15:59:51 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id PAA16235; Thu, 11 Nov 1999 15:59:18 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Thu, 11 Nov 1999 15:59:17 -0700 Date: Thu, 11 Nov 1999 15:59:17 -0800 (PST) From: Kip Macy X-Sender: kip@luna To: Ben Rosengart Cc: Assar Westerlund , hackers@freebsd.org Subject: Re: make -jN world; how to determine optimal value of N? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: ben@skunk.org,assar@sics.se,hackers@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That is the same specious logic that is used for Linux's "threads" you have diminishing marginal returns as the number gets larger due to context switching overhead. -Kip On Thu, 11 Nov 1999, Ben Rosengart wrote: > On 12 Nov 1999, Assar Westerlund wrote: > > > Other than that, I think the > > `make -j4' suggested for a single CPU in the handbook is a fairly good > > approximation. > > On what basis? I usually use larger values, like 12, on the theory that > I have more than enough memory, and if there's free CPU, there should > always be a process available to use it. > > -- > Ben Rosengart > > UNIX Systems Engineer, Skunk Group > StarMedia Network, Inc. > > > > 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 Nov 11 16: 6:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 0E83C14F5C for ; Thu, 11 Nov 1999 16:06:20 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id TAA01854; Thu, 11 Nov 1999 19:13:44 -0500 (EST) Date: Thu, 11 Nov 1999 19:13:43 -0500 (EST) From: Ben Rosengart To: Kip Macy Cc: Assar Westerlund , hackers@FreeBSD.ORG Subject: Re: make -jN world; how to determine optimal value of N? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 11 Nov 1999, Kip Macy wrote: > That is the same specious logic that is used for Linux's "threads" you > have diminishing marginal returns as the number gets larger due to context > switching overhead. Diminishing *marginal* returns I can live with, but I wonder if this strategy is actually hurting me, rather than merely failing to help much. Once I get a scratch box that I can waste on things like this, I'll run some tests and find out. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 16:14:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 2BBD914FC3 for ; Thu, 11 Nov 1999 16:14:16 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id QAA16356; Thu, 11 Nov 1999 16:13:59 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Thu, 11 Nov 1999 16:13:58 -0700 Date: Thu, 11 Nov 1999 16:13:58 -0800 (PST) From: Kip Macy X-Sender: kip@luna To: Ben Rosengart Cc: Assar Westerlund , hackers@FreeBSD.ORG Subject: Re: make -jN world; how to determine optimal value of N? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: ben@skunk.org,assar@sics.se,hackers@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Diminishing *marginal* returns I can live with, but I wonder if this > strategy is actually hurting me, rather than merely failing to help > much. That is a better way of putting it. At some point you returns are negative. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 16:14:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 0A3C0154A2 for ; Thu, 11 Nov 1999 16:14:37 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id QAA07021; Thu, 11 Nov 1999 16:39:42 -0800 (PST) Date: Thu, 11 Nov 1999 16:39:42 -0800 (PST) From: Alfred Perlstein To: Doug Barton Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Serious locking problem over NFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 11 Nov 1999, Doug Barton wrote: > Greetings, > > The following small program illustrates an obscure problem with > file locking with freebsd as an NFS client. I'm aware of the problems with We currently don't support client or server locking. work is in progress, but the dolt that took the job is extremely busy right now. (me) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 16:22: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 5864D14C0E for ; Thu, 11 Nov 1999 16:22:02 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA35722; Thu, 11 Nov 1999 16:21:11 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Ben Rosengart Cc: hackers@FreeBSD.ORG Subject: Re: make -jN world; how to determine optimal value of N? In-reply-to: Your message of "Thu, 11 Nov 1999 17:11:45 EST." Date: Thu, 11 Nov 1999 16:21:11 -0800 Message-ID: <35718.942366071@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does anyone know of a method for determining the optimal number of > concurrent jobs with which to make world (or anything else for that > matter), given the amount of RAM, speed of processor, version of > FreeBSD, speed and layout of disk(s), etc.? I doubt that such a method will ever be found, but more useful might be to figure out if there are any aspects of the Makefile hierarchy which already limit parallelization regardless of how much woof you've got in your machine. Some graphs I've done on a quad xeon strongly suggest this to be the case. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 17:26:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 3F9FA14C0E for ; Thu, 11 Nov 1999 17:26:41 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id BAA42993 for hackers@FreeBSD.ORG; Fri, 12 Nov 1999 01:26:41 GMT (envelope-from joe) Date: Fri, 12 Nov 1999 01:26:40 +0000 From: Josef Karthauser To: hackers@FreeBSD.ORG Subject: Re: Severe problems with softupdates. Message-ID: <19991112012640.B42455@florence.pavilion.net> References: <19991111201148.A5748@florence.pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991111201148.A5748@florence.pavilion.net> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've managed to recover from it with sprinklings of 'clri' and 'n' to fsck questions about reconnecting things that look bogus. It would be nice if fsck could be kinder though - and _why_ did it happen in the first place? Joe On Thu, Nov 11, 1999 at 08:11:49PM +0000, Josef Karthauser wrote: > Hi guys, > > I'm still trying to recover my laptop from a really severe filesystem > crash using softupdates. The machine hung due to a problem with > power managment so it needed a reboot. Now fsck won't clean up without > complaining bitterly about 'softupdate' problems, ultimately coming to > a halt with a 'can't find inode XXXX' message. I've confirmed with fsdb > that the inode in question does exist, so why is fsck complaining? Clearing > the inode in question allows fsck to proceed, and ultimately land on another > inode that exists, but it "can't find". > > I've searched the lists and this message appear to reference the same > problem: > > Date: Wed, 20 Oct 1999 01:58:31 -0400 (EDT) > From: "Joe \"Marcus\" Clarke" > To: Mark Powell > Cc: freebsd-questions@FreeBSD.ORG > Subject: Re: How to fix cant load /kernel ???? Also soft updates fs corruption. > Message-ID: > In-Reply-To: > > I'm running -current; I don't know what Mark was running. > > Kirk mentioned that he was confident that softupdates was 'safe', but I've > had files (from a previous crash - recovered from) in lost+found that I > didn't touch, and no-way should have become disconnected from the file > system - they weren't even in buffercache at the time of the crash. > > I believe that Brian has also had the same problems (at FreeBSDCon). > > Can people put their hands up if they believe that they've experienced this > so that we can determine whether there's a deeper softupdates problem that > we're ignoring on faith? > > Also if anyone knows how to recover from it I'd be very grateful to know. > My /usr partition is uncleanable (although I can 'mount -f' it!! nasty!!). > > Joe. > -- > Josef Karthauser FreeBSD: How many times have you booted today? > Technical Manager Viagra for your server (http://www.uk.freebsd.org) > Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 18:16: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from satsuma.mail.easynet.net (satsuma.mail.easynet.net [195.40.1.44]) by hub.freebsd.org (Postfix) with ESMTP id E90F914F16 for ; Thu, 11 Nov 1999 18:15:58 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (alister.w.easynet.co.uk [212.212.251.86]) by satsuma.mail.easynet.net (Postfix) with ESMTP id 007E57B02D for ; Fri, 12 Nov 1999 02:15:56 +0000 (GMT) Message-ID: <382B7870.C84ECFF1@freenet.co.uk> Date: Fri, 12 Nov 1999 02:16:16 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: fsck_ext2fs and fsck_msdos from Open/NetBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Both Open- and NetBSD seem to have separate fsck programs for each filesystem type - fsck_ffs, fsck_ext2fs and fsck_msdos - the actual /sbin/fsck program calling the appropriate one for a given filesystem (in a way similar to our `mount' command). The last two (fsck_ext2fs and _msdos) are nonexistent in FreeBSD. If someone (e.g. me when I have some spare time) were to port them over, would anyone object to their way of doing things? Just wondering... Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 18:52:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (Postfix) with ESMTP id 1E72A15266 for ; Thu, 11 Nov 1999 18:52:27 -0800 (PST) (envelope-from conrad@apple.com) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.9.3/8.9.3) with ESMTP id SAA18900 for ; Thu, 11 Nov 1999 18:52:26 -0800 (PST) Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com (mailgate1.apple.com- SMTPRS 2.0.15) with ESMTP id ; Thu, 11 Nov 1999 18:52:24 -0800 Received: from [17.202.43.185] (wa.apple.com [17.202.43.185]) by scv3.apple.com (8.9.3/8.9.3) with ESMTP id SAA12023; Thu, 11 Nov 1999 18:52:22 -0800 (PST) X-Sender: conrad@mail.apple.com Message-Id: In-Reply-To: References: MIME-Version: 1.0 Date: Thu, 11 Nov 1999 18:52:10 -0800 To: Alfred Perlstein , Doug Barton From: Conrad Minshall Subject: Re: Serious locking problem over NFS Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:39 PM -0800 11/11/99, Alfred Perlstein wrote: >On Thu, 11 Nov 1999, Doug Barton wrote: >> The following small program illustrates an obscure problem with >> file locking with freebsd as an NFS client. I'm aware of the problems with > >We currently don't support client or server locking. > >work is in progress, but the dolt that took the job is extremely busy >right now. (me) Yup, byte range locking fcntl APIs are present but over NFS they don't work. So shouldn't one be able to get entire-file locking with the old-fashioned: open("foo.lockfile", O_CREAT | O_EXCL, 0644) You would think so, but my experience is that reliably protects critical sections only when using NFS Version 3. Not V2. Read about EXCLUSIVE in the CREATE procedure in RFC 1813 for another level of detail. -- Conrad Minshall ... conrad@apple.com ... 408 974-2749 Apple Computer ... Mac OS X Core Operating Systems ... NFS/UDF/etc Alternative email address: rad@acm.org. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 19:41:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt054n7c.san.rr.com (dt054n7c.san.rr.com [24.30.152.124]) by hub.freebsd.org (Postfix) with ESMTP id 1B52014DD2 for ; Thu, 11 Nov 1999 19:41:43 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n7c.san.rr.com (8.9.3/8.8.8) with ESMTP id TAA41356; Thu, 11 Nov 1999 19:41:05 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <382B8C51.A80EC784@gorean.org> Date: Thu, 11 Nov 1999 19:41:05 -0800 From: Doug Barton X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT-0927 i386) X-Accept-Language: en MIME-Version: 1.0 To: Conrad Minshall Cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: Serious locking problem over NFS References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Conrad Minshall wrote: > > At 4:39 PM -0800 11/11/99, Alfred Perlstein wrote: > >On Thu, 11 Nov 1999, Doug Barton wrote: > > >> The following small program illustrates an obscure problem with > >> file locking with freebsd as an NFS client. I'm aware of the problems with > > > >We currently don't support client or server locking. > > > >work is in progress, but the dolt that took the job is extremely busy > >right now. (me) Hrrrmm... well to me the weird thing is that it *does* work when both processes run on the same FreeBSD NFS client. Where it doesn't work is when the two access points to the same file are on different clients, which, unfortunately is where (and why) we need it to work. > Yup, byte range locking fcntl APIs are present but over NFS they don't work. > > So shouldn't one be able to get entire-file locking with the old-fashioned: > > open("foo.lockfile", O_CREAT | O_EXCL, 0644) > > You would think so, but my experience is that reliably protects critical > sections only when using NFS Version 3. Not V2. Read about EXCLUSIVE in > the CREATE procedure in RFC 1813 for another level of detail. Ok, thanks for the tip. We are using V3, in fact I'm forcing it. I considered using O_EXCL but I'm not 100% sure about some of the implications for the particular application. I'll give it a try though, thanks for the tip, and the reference. Doug -- "Stop it, I'm gettin' misty." - Mel Gibson as Porter, "Payback" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 22:33:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 6DE9B1538F; Thu, 11 Nov 1999 22:33:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5F3BF1CD41E; Thu, 11 Nov 1999 22:33:05 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 11 Nov 1999 22:33:05 -0800 (PST) From: Kris Kennaway To: Alex Cc: freebsd-hackers@freebsd.org Subject: Re: fsck_ext2fs and fsck_msdos from Open/NetBSD In-Reply-To: <382B7870.C84ECFF1@freenet.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 12 Nov 1999, Alex wrote: > Both Open- and NetBSD seem to have separate fsck programs for each > filesystem type - fsck_ffs, fsck_ext2fs and fsck_msdos - the actual > /sbin/fsck program calling the appropriate one for a given filesystem > (in a way similar to our `mount' command). The last two (fsck_ext2fs > and _msdos) are nonexistent in FreeBSD. I think that would be a good thing..unless I'm mistaken, we don't have the ability to fsck those types of partition currently. Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 22:48:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from icarus.idirect.com (icarus.idirect.com [207.136.80.7]) by hub.freebsd.org (Postfix) with ESMTP id 6D53214BF7 for ; Thu, 11 Nov 1999 22:48:35 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by icarus.idirect.com (8.9.3/8.9.3) with ESMTP id BAA00468 for ; Fri, 12 Nov 1999 01:48:35 -0500 (EST) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id BAA30745 for ; Fri, 12 Nov 1999 01:48:34 -0500 (EST) Date: Fri, 12 Nov 1999 01:48:34 -0500 (EST) From: Bosko Milekic To: freebsd-hackers@freebsd.org Subject: mbuf wait code (revisited) -- review? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Attached are some diffs that provide a couple of wait routines in the out-of-mbuf and/or out-of-mbuf-cluster case(s). The attached diffs are for -STABLE and I would be greatful if somebody could review them/give feedback. I have diffs for -CURRENT but am not posting them because I haven't had too much of a chance to test the code -- whereas these below have been tested for a while now on several -STABLE machines. Since the problematic situation has been described numerous times before both on the list and in several PRs, I am not going to go over it again. Instead, a [fairly] accurate description of the situation in question can be found at: http://www.freebsd.org/cgi/query-pr.cgi?pr=14042 [Note that the patches posted in the original PR should not be considered.] There are several other open PRs which refer to a similar problem. Furthermore, I've also spotted at least one other PR which addresses a potentially related issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=9883 The above PR mentions MGET turning the provided mbuf pointer to a NULL pointer even if the call was made with M_WAIT. I don't see how this can be the case, especially since presently the code is set to panic() in the m_reclaim when out of mbufs and calling with M_WAIT. In any case, with the code below, MGET will potentially be capable of setting that NULL pointer, which is something that really can't be avoided even if the call is made with M_WAIT. The whole idea behind the provided diffs is to add a 'sleep' time before actually deciding to explicitly "fail" -- this sleep time can be modified dynamically, the diffs add a sysctl kern.ipc.mbuf_wait to tune the sleep time in the tsleep(). Anyway, I would really appreciate feedback and/or suggestions. Furthermore, if anybody's interested in testing it, I can post the -CURRENT version of the diffs (which are only slightly different). Finally, if this looks good, the next step would be to search and dig through all the code that uses the MGET, MGETHDR, MCLGET, MCLALLOC macros and m_get, m_gethdr, m_clalloc functions in order to make sure that all of that code checks whether the returned pointer is referencing a NULL (most of the problematic code resides in sys/nfs, from what I've seen. -- Bosko Milekic "I counted the steps in my walks and calculated the cubic contents of soup plates, coffee cups, and pieces of food -- otherwise my meal was unenjoyable. All repeated acts or operations I performed had to be divisible by three and if I missed I felt impelled to do it all over again, even if it took hours." -- Nikola Tesla, 1919. (Note: If the diffs below generate problems, please let me know and I'll post this stuff somewhere on the WWW). --snip snip-- diff -ruN sys.old/conf/param.c sys/conf/param.c --- sys.old/conf/param.c Sun Oct 31 23:34:16 1999 +++ sys/conf/param.c Mon Nov 1 20:07:46 1999 @@ -82,6 +82,7 @@ int maxfiles = MAXFILES; /* system wide open files limit */ int maxfilesperproc = MAXFILES; /* per-process open files limit */ int ncallout = 16 + NPROC + MAXFILES; /* maximum # of timer events */ +int mbuf_wait = 32; /* mbuf sleep time */ /* maximum # of mbuf clusters */ #ifndef NMBCLUSTERS diff -ruN sys.old/kern/uipc_mbuf.c sys/kern/uipc_mbuf.c --- sys.old/kern/uipc_mbuf.c Wed Sep 8 20:45:50 1999 +++ sys/kern/uipc_mbuf.c Fri Nov 5 21:44:51 1999 @@ -47,6 +47,10 @@ #include #include +#ifdef INVARIANTS +#include +#endif + static void mbinit __P((void *)); SYSINIT(mbuf, SI_SUB_MBUF, SI_ORDER_FIRST, mbinit, NULL) @@ -60,6 +64,8 @@ int max_hdr; int max_datalen; +static u_int m_mballoc_wid = 0, m_clalloc_wid = 0; + SYSCTL_INT(_kern_ipc, KIPC_MAX_LINKHDR, max_linkhdr, CTLFLAG_RW, &max_linkhdr, 0, ""); SYSCTL_INT(_kern_ipc, KIPC_MAX_PROTOHDR, max_protohdr, CTLFLAG_RW, @@ -67,13 +73,14 @@ SYSCTL_INT(_kern_ipc, KIPC_MAX_HDR, max_hdr, CTLFLAG_RW, &max_hdr, 0, ""); SYSCTL_INT(_kern_ipc, KIPC_MAX_DATALEN, max_datalen, CTLFLAG_RW, &max_datalen, 0, ""); +SYSCTL_INT(_kern_ipc, OID_AUTO, mbuf_wait, CTLFLAG_RW, + &mbuf_wait, 0, ""); SYSCTL_STRUCT(_kern_ipc, KIPC_MBSTAT, mbstat, CTLFLAG_RW, &mbstat, mbstat, ""); static void m_reclaim __P((void)); /* "number of clusters of pages" */ #define NCL_INIT 1 - #define NMB_INIT 16 /* ARGSUSED*/ @@ -125,6 +132,9 @@ * any more (nothing is ever freed back to the map) (XXX which * is dumb). (however you are not dead as m_reclaim might * still be able to free a substantial amount of space). + * XXX Furthermore, we can also work with "recycled" mbufs (when + * we're calling with M_WAIT the sleep procedure will be waked + * up when an mbuf is freed. See m_mballoc_wait() */ if (mb_map_full) return (0); @@ -153,6 +163,55 @@ return (1); } +/* + * The m_mballoc_wait function below is used from the mbuf + * allocation macros once the mb_map has been exhausted and if + * the caller is calling with M_WAIT in order to wait + * for a "recycled" mbuf to be freed. + */ +struct mbuf * +m_mballoc_wait(char caller, u_short type) +{ + struct mbuf *p; + + /* Sleep until something's available or until we expire. */ + m_mballoc_wid++; + if ((tsleep(&m_mballoc_wid, PVM, "mballc", + mbuf_wait)) == EWOULDBLOCK) + m_mballoc_wid--; + + /* + * Now that we (think) that we've got something, we will redo an + * MGET, but avoid getting into another instance of m_mballoc_wait() + */ + p = 0; +#define m_mballoc_wait(caller,type) (struct mbuf *)0 + if (caller & MGETHDR_C) + MGETHDR(p, M_WAIT, type); + else + MGETHDR(p, M_WAIT, type); +#undef m_mballoc_wait + + if (p != 0) /* We waited and got something... */ + mbstat.m_wait++; + + return (p); +} + +/* + * The m_mballoc_wakeup function below is used in order + * to wakeup the instance(s) of m_mballoc_wait() which + * are waiting on an mbuf to be freed. + */ +void +m_mballoc_wakeup(void) +{ + if (m_mballoc_wid) { + m_mballoc_wid = 0; + wakeup(&m_mballoc_wid); + } +} + #if MCLBYTES > PAGE_SIZE static int i_want_my_mcl; @@ -199,7 +258,8 @@ /* * Once we run out of map space, it will be impossible * to get any more (nothing is ever freed back to the - * map). + * map). From this point on, we solely rely on reclaimed + * mbufs. */ if (mb_map_full) { mbstat.m_drops++; @@ -242,6 +302,55 @@ } /* + * The m_clalloc_wait function below is used from the mbuf cluster + * allocation macros once the mb_map has been exhausted and if the + * caller is calling with M_WAIT in order to wait for a "recycled" + * mbuf cluster to be freed. + */ +caddr_t +m_clalloc_wait(void) +{ + caddr_t p; + + /* If in an interrupt context, and ifdef INVARIANTS, die. */ + KASSERT(intr_nesting_level == 0,("CLALLOC: CANNOT WAIT IN INTERRUPT")); + + /* Sleep until something's available or until we expire. */ + m_clalloc_wid++; + if ((tsleep(&m_clalloc_wid, PVM, "mclalc", + mbuf_wait)) == EWOULDBLOCK) + m_clalloc_wid--; + + /* + * Now that we (think) that we've got something, we will redo and + * MGET, but avoid getting into another instance of m_clalloc_wait() + */ + p = 0; +#define m_clalloc_wait() (caddr_t)0 + MCLALLOC(p,M_WAIT); +#undef m_clalloc_wait + + if (p != 0) /* We waited and got something... */ + mbstat.m_wait++; + + return (p); +} + +/* + * The m_clalloc_wakeup function below is used in order + * to wakeup the instance(s) of m_clalloc_wait() which + * are waiting for an mbuf cluster to be freed. + */ +void +m_clalloc_wakeup(void) +{ + if (m_clalloc_wid) { + m_clalloc_wid = 0; + wakeup(&m_clalloc_wid); + } +} + +/* * When MGET fails, ask protocols to free space when short of memory, * then re-attempt to allocate an mbuf. */ @@ -254,19 +363,28 @@ /* * Must only do the reclaim if not in an interrupt context. */ - if (i == M_WAIT) + if (i == M_WAIT) { + KASSERT(intr_nesting_level == 0, + ("MBALLOC: CANNOT WAIT IN INTERRUPT")); m_reclaim(); + } + + /* + * Both m_mballoc_wait and m_retry must be nulled because + * when the MGET macro is run from here, we deffinately do _not_ + * want to enter an instance of m_mballoc_wait() or m_retry() (again!) + */ +#define m_mballoc_wait(caller,type) (struct mbuf *)0 #define m_retry(i, t) (struct mbuf *)0 MGET(m, i, t); #undef m_retry +#undef m_mballoc_wait + if (m != NULL) { mbstat.m_wait++; - } else { - if (i == M_DONTWAIT) - mbstat.m_drops++; - else + mbstat.m_drops++; + return (m); } @@ -282,19 +400,23 @@ /* * Must only do the reclaim if not in an interrupt context. */ - if (i == M_WAIT) + if (i == M_WAIT) { + KASSERT(intr_nesting_level == 0, + ("MBALLOC: CANNOT WAIT IN INTERRUPT")); m_reclaim(); + } + +#define m_mballoc_wait(caller,type) (struct mbuf *)0 #define m_retryhdr(i, t) (struct mbuf *)0 MGETHDR(m, i, t); #undef m_retryhdr +#undef m_mballoc_wait + if (m != NULL) { mbstat.m_wait++; - } else { - if (i == M_DONTWAIT) - mbstat.m_drops++; - else - panic("Out of mbuf clusters"); - } + } else + mbstat.m_drops++; + return (m); } diff -ruN sys.old/kern/uipc_socket.c sys/kern/uipc_socket.c --- sys.old/kern/uipc_socket.c Wed Sep 8 20:45:50 1999 +++ sys/kern/uipc_socket.c Fri Nov 5 21:45:49 1999 @@ -486,15 +486,27 @@ } else do { if (top == 0) { MGETHDR(m, M_WAIT, MT_DATA); + if (m == NULL) { + error = ENOBUFS; + goto release; + } mlen = MHLEN; m->m_pkthdr.len = 0; m->m_pkthdr.rcvif = (struct ifnet *)0; } else { MGET(m, M_WAIT, MT_DATA); + if (m == NULL) { + error = ENOBUFS; + goto release; + } mlen = MLEN; } if (resid >= MINCLSIZE) { MCLGET(m, M_WAIT); + if (m == NULL) { + error = ENOBUFS; + goto release; + } if ((m->m_flags & M_EXT) == 0) goto nopages; mlen = MCLBYTES; @@ -606,6 +618,10 @@ flags = 0; if (flags & MSG_OOB) { m = m_get(M_WAIT, MT_DATA); + if (m == NULL) { + error = ENOBUFS; + goto release; + } error = (*pr->pr_usrreqs->pru_rcvoob)(so, m, flags & MSG_PEEK); if (error) goto bad; diff -ruN sys.old/kern/uipc_syscalls.c sys/kern/uipc_syscalls.c --- sys.old/kern/uipc_syscalls.c Wed Sep 8 20:45:50 1999 +++ sys/kern/uipc_syscalls.c Fri Nov 5 21:46:27 1999 @@ -1620,6 +1620,10 @@ * Get an mbuf header and set it up as having external storage. */ MGETHDR(m, M_WAIT, MT_DATA); + if (m == NULL) { + error = ENOBUFS; + goto done; + } m->m_ext.ext_free = sf_buf_free; m->m_ext.ext_ref = sf_buf_ref; m->m_ext.ext_buf = (void *)sf->kva; diff -ruN sys.old/sys/mbuf.h sys/sys/mbuf.h --- sys.old/sys/mbuf.h Sun Oct 31 23:33:54 1999 +++ sys/sys/mbuf.h Mon Nov 1 20:07:47 1999 @@ -153,6 +153,14 @@ #define M_DONTWAIT 1 #define M_WAIT 0 +/* + * Byte-long flag passed to the m_mballoc_wait function, allowing + * us to determine that the call came from an MGETHDR and not an MGET -- + * this way we are sure to run the MGETHDR macro when the call came from there. + */ +#define MGETHDR_C 0x01 +#define MGET_C 0x02 + /* Freelists: * * Normal mbuf clusters are normally treated as character arrays @@ -187,7 +195,8 @@ * allocates an mbuf and initializes it to contain a packet header * and internal data. */ -#define MGET(m, how, type) { \ +#define MGET(m, how, type) \ + do { \ int _ms = splimp(); \ if (mmbfree == 0) \ (void)m_mballoc(1, (how)); \ @@ -201,13 +210,15 @@ (m)->m_data = (m)->m_dat; \ (m)->m_flags = 0; \ splx(_ms); \ - } else { \ + } else { \ splx(_ms); \ - (m) = m_retry((how), (type)); \ - } \ -} + if (((m)=m_retry((how), (type)))==NULL && (how)==M_WAIT) \ + (m) = m_mballoc_wait(MGET_C,(type)); \ + } \ + } while(0) -#define MGETHDR(m, how, type) { \ +#define MGETHDR(m, how, type) \ + do { \ int _ms = splimp(); \ if (mmbfree == 0) \ (void)m_mballoc(1, (how)); \ @@ -221,11 +232,12 @@ (m)->m_data = (m)->m_pktdat; \ (m)->m_flags = M_PKTHDR; \ splx(_ms); \ - } else { \ + } else { \ splx(_ms); \ - (m) = m_retryhdr((how), (type)); \ - } \ -} + if (((m)=m_retryhdr((how),(type)))==NULL && (how)==M_WAIT) \ + (m) = m_mballoc_wait(MGETHDR_C,(type)); \ + } \ + } while(0) /* * Mbuf cluster macros. @@ -236,15 +248,20 @@ * freeing the cluster if the reference count has reached 0. */ #define MCLALLOC(p, how) \ - MBUFLOCK( \ + do { \ + int _ms = splimp(); \ if (mclfree == 0) \ (void)m_clalloc(1, (how)); \ if (((p) = (caddr_t)mclfree) != 0) { \ ++mclrefcnt[mtocl(p)]; \ mbstat.m_clfree--; \ mclfree = ((union mcluster *)(p))->mcl_next; \ + splx(_ms); \ + } else if ((how) == M_WAIT) { \ + splx(_ms); \ + (p) = m_clalloc_wait(); \ } \ - ) + } while(0) #define MCLGET(m, how) \ { MCLALLOC((m)->m_ext.ext_buf, (how)); \ @@ -263,6 +280,7 @@ ((union mcluster *)(p))->mcl_next = mclfree; \ mclfree = (union mcluster *)(p); \ mbstat.m_clfree++; \ + (void)m_clalloc_wakeup(); \ } \ ) @@ -284,6 +302,7 @@ ((union mcluster *)(p))->mcl_next = mclfree; \ mclfree = (union mcluster *)(p); \ mbstat.m_clfree++; \ + (void)m_clalloc_wakeup(); \ } \ } \ } \ @@ -292,6 +311,7 @@ mbstat.m_mtypes[MT_FREE]++; \ (m)->m_next = mmbfree; \ mmbfree = (m); \ + (void)m_mballoc_wakeup(); \ ) /* @@ -397,6 +417,7 @@ extern int max_protohdr; /* largest protocol header */ extern int max_hdr; /* largest link+protocol header */ extern int max_datalen; /* MHLEN - max_hdr */ +extern int mbuf_wait; /* mbuf sleep time */ struct mbuf *m_copym __P((struct mbuf *, int, int, int)); struct mbuf *m_copypacket __P((struct mbuf *, int)); @@ -408,16 +429,20 @@ struct mbuf *m_gethdr __P((int, int)); struct mbuf *m_prepend __P((struct mbuf *,int,int)); struct mbuf *m_pullup __P((struct mbuf *, int)); +struct mbuf *m_mballoc_wait __P((char,u_short)); struct mbuf *m_retry __P((int, int)); struct mbuf *m_retryhdr __P((int, int)); struct mbuf *m_split __P((struct mbuf *,int,int)); void m_adj __P((struct mbuf *, int)); void m_cat __P((struct mbuf *,struct mbuf *)); +void m_mballoc_wakeup __P((void)); +void m_clalloc_wakeup __P((void)); int m_mballoc __P((int, int)); int m_clalloc __P((int, int)); void m_copyback __P((struct mbuf *, int, int, caddr_t)); void m_copydata __P((struct mbuf *,int,int,caddr_t)); void m_freem __P((struct mbuf *)); +caddr_t m_clalloc_wait __P((void)); #endif /* KERNEL */ #endif /* !_SYS_MBUF_H_ */ --snip snip-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 11 23:46:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id D9BE814BC4 for ; Thu, 11 Nov 1999 23:46:28 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id NAA13286 for ; Fri, 12 Nov 1999 13:46:10 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Fri, 12 Nov 1999 13:46:08 +0600 (NS) From: Max Khon To: hackers@freebsd.org Subject: openssh 1.2 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! just installed the openssh port: everything is fine but i miss one feature: OpenBSD guys removed calling ssh-askpass from ssh-add (because ssh-askpass require X libs for building) and removed ssh-askpass at all. maybe it would be better to put ssh-askpass in ports (ssh 1.2.16 which was the base for openssh has ssh-askpass) and put back ssh-askpass call to ssh-add. if openssh will be put in source tree we can have dummy version of ssh-askpass there (which does nothing) and normal ssh-askpass in ports. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 0:16:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id EAC7314C0B for ; Fri, 12 Nov 1999 00:16:06 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id AAA07076; Fri, 12 Nov 1999 00:10:18 -0800 (PST) Date: Fri, 12 Nov 1999 00:10:17 -0800 (PST) From: Julian Elischer To: Bosko Milekic Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mbuf wait code (revisited) -- review? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks pretty thorough but needs more examination that I have given it yet. On Fri, 12 Nov 1999, Bosko Milekic wrote: > > Hi, > > Attached are some diffs that provide a couple of wait routines in the > out-of-mbuf and/or out-of-mbuf-cluster case(s). The attached diffs are for -STABLE > and I would be greatful if somebody could review them/give feedback. I have diffs for > -CURRENT but am not posting them because I haven't had too much of a chance to test [...] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 0:26:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles544.castles.com [208.214.165.108]) by hub.freebsd.org (Postfix) with ESMTP id 1426014C09 for ; Fri, 12 Nov 1999 00:26:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA00425; Fri, 12 Nov 1999 00:16:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911120816.AAA00425@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: eT Cc: freebsd-hackers@freebsd.org Subject: Re: One bit error on BUS? In-reply-to: Your message of "Thu, 11 Nov 1999 10:04:57 +0100." <382A86B8.915EC497@post.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Nov 1999 00:16:29 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What could the possible explanation be in the following scenario: There are dozens of possible explanations. > We have: > > arbitrary chip <---localbus---> pci controller <===pcibus===> > BX Motherboard <------> RAM > > And somewhere in the transfer of blocks of data between the chip (on the > left) and the RAM on the right we have random one bit errors. we means > that for huge streams of transfer all might be ok and at random > intervals exactely one bit will be set incorrectly (not always the same > bit in the byte). > > We have a 440BX motherboard with a PII400. > > Is it a timing problem on data transfer on the local bus or pci bus? It could be. Seriously; the question you ask is impossible to answer without access to the hardware itself and a lot of expensive test equipment. However, given that the motherboard probably works, and your custom hardware probably hasn't had the same sort of testing, it's probably safe to suspect your side of things. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 0:54:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dialup.nacamar.de (authsrv.nacamar.de [194.162.162.197]) by hub.freebsd.org (Postfix) with SMTP id BD42614D15 for ; Fri, 12 Nov 1999 00:54:46 -0800 (PST) (envelope-from Sunrise!nmh@dialup.nacamar.de) Received: (qmail 1553 invoked from network); 12 Nov 1999 08:54:38 -0000 Received: from dialup23-138.access.nacamar.de (HELO Sunrise.UUCP) (62.144.233.138) by authsrv.nacamar.de with SMTP; 12 Nov 1999 08:54:38 -0000 Date: Fri, 12 Nov 1999 09:53:21 +0100 (CET) From: Nils M Holm X-Sender: nmh@Sunrise.UUCP Reply-To: Nils M Holm To: hackers@freebsd.org Subject: Missing symbols in LIBC ??? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I am currently porting my compiler to the release 3.3. My RT lib depends on /usr/lib/libc.a. When attempting to link a program, I get messages about unresolved externals (it DOES work on release 2.x). I have seen that the C compiler no longer generates underscores on symbols by default and consequently, '_printf' in /usr/lib/libc.a has become simply 'printf'. There seem to exist kind of 'compatibility entries' for some functions, though. However, (at least) the symbols _creat, _lseek, and _memmove are not defined in /usr/lib/libc.a. (creat, lseek, and memove are defined.) Is this a bug or a feature? Will underscores vanish totally in the future? Do I have to create a workaround for the 3.x branch?? Bye, nmh. -- Nils M Holm [Please use Reply-To:] http://www.homepages.de/home/nmh/ -- The home of the T3X compiler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 0:57: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles544.castles.com [208.214.165.108]) by hub.freebsd.org (Postfix) with ESMTP id DC31B14C38 for ; Fri, 12 Nov 1999 00:56:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA00657; Fri, 12 Nov 1999 00:47:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911120847.AAA00657@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Stephane E. Potvin" Cc: hackers@freebsd.org Subject: Re: ARM support In-reply-to: Your message of "Sun, 07 Nov 1999 15:12:23 EST." <3825DD27.81742440@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Nov 1999 00:47:28 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If you're interested in sharing your work, I have a DNA ('shark') here > > that was loaned to the Project for just this purpose. I'd be really > > interested to see your cross-build bits integrated into our tree ASAP. > > I'd really like this to happens too but right now I think that would be > near impossible. binutils 2.9.1 doesn't really support arm/elf so I'm > currently using a recent snapshot of binutils (2.9.5) with gcc 2.95.1. > I'm using a boatload of very ugly hacks to make this combitation work > with current... > > As soon as the binutils crew releases something more official so that it > could be added into the tree I'll be more than happy to send pr's for > what I've got so far. Sounds good to me. If you manage to get it all together, there's a port leader hat here waiting for you... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 1:11:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 252B814C38 for ; Fri, 12 Nov 1999 01:11:36 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.040 #1) id 11mCjt-0001zR-00; Fri, 12 Nov 1999 11:11:25 +0200 From: Sheldon Hearn To: Ollivier Robert Cc: hackers@freebsd.org Subject: Re: mode_perl DSO works on STABLE, not CURRENT In-reply-to: Your message of "Thu, 11 Nov 1999 00:45:52 +0100." <19991111004552.B44926@keltia.freenix.fr> Date: Fri, 12 Nov 1999 11:11:25 +0200 Message-ID: <7652.942397885@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 11 Nov 1999 00:45:52 +0100, Ollivier Robert wrote: > Your Perl binary is compiled without '-Wl,-E' (or > '-Wl,--export-dynamic'). Without this option the Perl binary doesn't > expoert its symbols thus preventing any dynamically loaded module to > use anything from the binary. > > The official Perl distribution and the one in CURRENT (and 3.3-STABLE) > have been fixed a long time ago. I have a week old CURRENT here for which I don't mess with the perl build at all. So whatever CURRENT's perl is supposed to do, mine does. :-) Mark Murray pointed out that the only significant difference between STABLE and CURRENT in this regard is the compiler. That's unfortunate, because this really does put any solution out of my reach. I'll mark the port broken for CURRENT. :-( Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 6:40:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id 4AF9C14E7D for ; Fri, 12 Nov 1999 06:40:17 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id BAA15157; Sat, 13 Nov 1999 01:10:02 +1030 (CST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991111221412.46739@mojave.sitaranetworks.com> Date: Thu, 11 Nov 1999 22:14:12 -0500 From: Greg Lehey To: Josef Karthauser , hackers@FreeBSD.ORG Subject: Re: Severe problems with softupdates. Reply-To: Greg Lehey References: <19991111201148.A5748@florence.pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <19991111201148.A5748@florence.pavilion.net>; from Josef Karthauser on Thu, Nov 11, 1999 at 08:11:49PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 11 November 1999 at 20:11:49 +0000, Josef Karthauser wrote: > Hi guys, > > I'm still trying to recover my laptop from a really severe filesystem > crash using softupdates. The machine hung due to a problem with > power managment so it needed a reboot. Now fsck won't clean up without > complaining bitterly about 'softupdate' problems, ultimately coming to > a halt with a 'can't find inode XXXX' message. I've confirmed with fsdb > that the inode in question does exist, so why is fsck complaining? Clearing > the inode in question allows fsck to proceed, and ultimately land on another > inode that exists, but it "can't find". > > I've searched the lists and this message appear to reference the same > problem: > > Date: Wed, 20 Oct 1999 01:58:31 -0400 (EDT) > From: "Joe \"Marcus\" Clarke" > To: Mark Powell > Cc: freebsd-questions@FreeBSD.ORG > Subject: Re: How to fix cant load /kernel ???? Also soft updates fs corruption. > Message-ID: > In-Reply-To: > > I'm running -current; I don't know what Mark was running. > > Kirk mentioned that he was confident that softupdates was 'safe', but I've > had files (from a previous crash - recovered from) in lost+found that I > didn't touch, and no-way should have become disconnected from the file > system - they weren't even in buffercache at the time of the crash. > > I believe that Brian has also had the same problems (at FreeBSDCon). > > Can people put their hands up if they believe that they've experienced this > so that we can determine whether there's a deeper softupdates problem that > we're ignoring on faith? Hmm. I've had something similar recently, also running -CURRENT. I still need to clean out the lost+found directory, but many of the files hadn't been touched for months. I think that the problem was that the directory in which they were got trashed, so the files could no longer be found via the directory tree. This was the worst file system crash I have had in the 8 years I have been running BSD. This was on a laptop (Dell Latitude). From your mention of power management, it sounds like you might have had your problems on a laptop as well. > Also if anyone knows how to recover from it I'd be very grateful to know. > My /usr partition is uncleanable (although I can 'mount -f' it!! nasty!!). Hmm. I suppose the answer is still "one error at a time". There are plenty of bugs in fsck, and it's quite possible one or more of them are ganging up with your already damaged file system. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 6:51:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 00E2514D26 for ; Fri, 12 Nov 1999 06:51:42 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id IAA76135; Fri, 12 Nov 1999 08:51:25 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Fri, 12 Nov 1999 08:51:25 -0600 (CST) From: David Scheidt To: Greg Lehey Cc: Josef Karthauser , hackers@FreeBSD.ORG Subject: Re: Severe problems with softupdates. In-Reply-To: <19991111221412.46739@mojave.sitaranetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 11 Nov 1999, Greg Lehey wrote: > > Hmm. I've had something similar recently, also running -CURRENT. I > still need to clean out the lost+found directory, but many of the > files hadn't been touched for months. I think that the problem was I had a crash like this on 3.1 -STABLE box. I loaded a buggy kernel module, the box paniced, and a lot of /usr ended up in lost+found. This was an ancient Pentium box, no power management. It was a bunch of consecutive inodes. It looked like it was filesystem buffers had been randomly hosed, and panic's sync wrote them out. Most of the files touched weren't in use, but a couple I was editing at the time. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 7: 7:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id A9BCA14EB0 for ; Fri, 12 Nov 1999 07:07:12 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id PAA77375; Fri, 12 Nov 1999 15:06:56 GMT (envelope-from joe) Date: Fri, 12 Nov 1999 15:06:56 +0000 From: Josef Karthauser To: Greg Lehey Cc: hackers@FreeBSD.ORG Subject: Re: Severe problems with softupdates. Message-ID: <19991112150655.A76708@florence.pavilion.net> References: <19991111201148.A5748@florence.pavilion.net> <19991111221412.46739@mojave.sitaranetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991111221412.46739@mojave.sitaranetworks.com> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 11, 1999 at 10:14:12PM -0500, Greg Lehey wrote: > > > Also if anyone knows how to recover from it I'd be very grateful to know. > > My /usr partition is uncleanable (although I can 'mount -f' it!! nasty!!). > > Hmm. I suppose the answer is still "one error at a time". There are > plenty of bugs in fsck, and it's quite possible one or more of them > are ganging up with your already damaged file system. > I got it all back in the end, but it involve rolling up my sleaves and 'clri'ing and inteligent use of 'n' at 'RECONNECT?' messages. Fsck should have done a better job in my opinion, and it will probably end up on my plate to fix it. Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 7:22:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 13EF81500F for ; Fri, 12 Nov 1999 07:22:07 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id KAA06674; Fri, 12 Nov 1999 10:28:37 -0500 (EST) Date: Fri, 12 Nov 1999 10:28:37 -0500 (EST) From: Ben Rosengart To: Robert Watson Cc: Kip Macy , Assar Westerlund , hackers@FreeBSD.ORG Subject: Re: make -jN world; how to determine optimal value of N? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 11 Nov 1999, Robert Watson wrote: > Well, presumably at some point your memory working set exceeds your CPU > cache, and that begins to hurt. And then at some point your working > memory pages exceed the available space, and you begin to page. I've been working with systems with 512 MB or more of RAM, so that hasn't been an issue. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 7:47:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 8D67E14F1B for ; Fri, 12 Nov 1999 07:47:37 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id XAA39101; Thu, 11 Nov 1999 23:56:30 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Thu, 11 Nov 1999 23:56:30 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Ben Rosengart Cc: Kip Macy , Assar Westerlund , hackers@FreeBSD.ORG Subject: Re: make -jN world; how to determine optimal value of N? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 11 Nov 1999, Ben Rosengart wrote: > On Thu, 11 Nov 1999, Kip Macy wrote: > > > That is the same specious logic that is used for Linux's "threads" you > > have diminishing marginal returns as the number gets larger due to context > > switching overhead. > > Diminishing *marginal* returns I can live with, but I wonder if this > strategy is actually hurting me, rather than merely failing to help > much. > > Once I get a scratch box that I can waste on things like this, I'll run > some tests and find out. Well, presumably at some point your memory working set exceeds your CPU cache, and that begins to hurt. And then at some point your working memory pages exceed the available space, and you begin to page. Also, your working file block set exceeds your buffer cache, etc. Of course, with more outstanding disk requests, you give the hard disk driver and disk hardware itself more time to optimize seek patterns, but that probably doesn't make up for the increase in I/O based on not keeping as much in memory :-). Where your peak is probably depends primarily on how many processes you can fit into your physical memory, and the disk working set compared to throughput of the processes. This is all just speculation as I haven't done timings, but you should certainly see a drop in performance when N is too high :-). Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 8:19: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from omnix.net (omnix.net [195.154.168.66]) by hub.freebsd.org (Postfix) with SMTP id 91CD214F27 for ; Fri, 12 Nov 1999 08:18:52 -0800 (PST) (envelope-from didier@omnix.net) Received: (qmail 5804 invoked by uid 200); 12 Nov 1999 16:18:51 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 12 Nov 1999 16:18:50 -0000 Date: Fri, 12 Nov 1999 16:18:50 +0000 (GMT) From: Didier Derny To: hackers@freebsd.org Subject: "bsd emulation" (controle of cgi execution) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, I would like to controle the execution of the cgi on my machine (specially the path used by the scripts) each client as a unique group id / user id. the binarie I want to control are either some standard FreeBSD in a chrooted enviromnent or the cgi scripts launched by suexec (largely customized version of apache suexec). for example: I have /home/user1 and /home/user2. with chroot the users are only able to see (from the cgi) /user1 and /user2 but I would like to make /user1 hidden from /user2 (and the same for the reverse case). without having to make a separate chrooted environment for each user. one the idea would be to write a "bsd emulator" base on the linux emulator to trap the system call inside the emulator. nothing would be done by this "emulator" execpt controlling the paths. the other idea would be to modify the bsd to intercept the system call for the process with a specific flag ? (to avoid slowing down standard applications) and a system called could be: processed normaly (read, write...), treated as errors (mount...) or intercepted to controle the path (a kind of suexecd) -- Didier Derny didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 9:44:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 1950A14F69 for ; Fri, 12 Nov 1999 09:44:32 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id RAA18991; Fri, 12 Nov 1999 17:44:09 GMT (envelope-from joe) Date: Fri, 12 Nov 1999 17:44:08 +0000 From: Josef Karthauser To: Sergey Shkonda Cc: hackers@FreeBSD.ORG Subject: Re: New command for cdcontrol(1) Message-ID: <19991112174408.E76708@florence.pavilion.net> References: <19991006130508.O24928@florence.pavilion.net> <199910061239.PAA05272@bcs3.bcs.zp.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199910061239.PAA05272@bcs3.bcs.zp.ua> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 06, 1999 at 03:39:41PM +0300, Sergey Shkonda wrote: > On Wed, 6 Oct 1999 13:05:08 +0100, Josef Karthauser wrote: > > On Wed, Oct 06, 1999 at 01:02:14PM +0300, Sergey Shkonda wrote: > > > I'm using this patch for cdcontrol(1): > > > > > > cdid Print the xmcd's CD id. > > > > Is the method used by xmcd used by anything else or is it just _a_ method. > > What's the algorithm that the cddb boys use? If it's the same then I > > believe that this is a useful patch. If it's different - it should be > > made same :) > Yes, this algorithm used in cddb. Ok. I've spent a bit of time looking into this further. Here's a question for you before I commit. Why _should_ cdcontrol have the ability to print this number? I've looked in vain at the cddb.com people's site and there is no obvious way to use the id number directly. They're depricating the cddb-v1 protocol and replacing it with a "sign the official NDA" version 2. In light of this there doesn't appear to be a reason to commit the changes. Do you disagree? Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 10:18:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id DCB5E14FFC for ; Fri, 12 Nov 1999 10:18:23 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id LAA16618 for ; Fri, 12 Nov 1999 11:18:18 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA19728; Fri, 12 Nov 1999 11:18:18 -0700 Date: Fri, 12 Nov 1999 11:18:18 -0700 Message-Id: <199911121818.LAA19728@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hackers@FreeBSD.org Subject: Determining (after the fact) if a routine was compiled as PIC? X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a way to look at a compiled file to see if it was compiled as PIC? I've got some .o files that I don't have source code to, but before I throw them into a shlib, I need to know if they are legal to put into one? Thanks! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 10:20:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id AB09B14FDB for ; Fri, 12 Nov 1999 10:20:16 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA23792; Fri, 12 Nov 1999 10:20:11 -0800 (PST) (envelope-from dillon) Date: Fri, 12 Nov 1999 10:20:11 -0800 (PST) From: Matthew Dillon Message-Id: <199911121820.KAA23792@apollo.backplane.com> To: Conrad Minshall Cc: Alfred Perlstein , Doug Barton , freebsd-hackers@FreeBSD.ORG Subject: Re: Serious locking problem over NFS References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Yup, byte range locking fcntl APIs are present but over NFS they don't work. : :So shouldn't one be able to get entire-file locking with the old-fashioned: : : open("foo.lockfile", O_CREAT | O_EXCL, 0644) : :You would think so, but my experience is that reliably protects critical :sections only when using NFS Version 3. Not V2. Read about EXCLUSIVE in :the CREATE procedure in RFC 1813 for another level of detail. : :-- :Conrad Minshall ... conrad@apple.com ... 408 974-2749 :Apple Computer ... Mac OS X Core Operating Systems ... NFS/UDF/etc open w/ O_CREAT|O_EXCL does work over NFS but, of course, suffers from the 'process died and never removed the file' problem. flock() and POSIX fctl locks work locally between processes on any given host, but will NOT work between hosts. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 10:25:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from atlrel1.hp.com (atlrel1.hp.com [156.153.255.210]) by hub.freebsd.org (Postfix) with ESMTP id 3509815475 for ; Fri, 12 Nov 1999 10:25:43 -0800 (PST) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (postal.sr.hp.com [15.4.46.173]) by atlrel1.hp.com (Postfix) with ESMTP id AD4B71E4; Fri, 12 Nov 1999 13:25:38 -0500 (EST) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id KAA14698; Fri, 12 Nov 1999 10:25:46 -0800 (PST) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id KAA24080; Fri, 12 Nov 1999 10:25:35 -0800 (PST) Message-Id: <199911121825.KAA24080@mina.sr.hp.com> To: Josef Karthauser Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Severe problems with softupdates. Reply-To: Darryl Okahata In-reply-to: Your message of "Thu, 11 Nov 1999 20:11:49 GMT." Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Fri, 12 Nov 1999 10:25:35 -0800 From: Darryl Okahata Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser wrote: > I'm still trying to recover my laptop from a really severe filesystem > crash using softupdates. The machine hung due to a problem with > power managment so it needed a reboot. Now fsck won't clean up without Out of curiousity, did you get this crash while attempting to get suspend/hibernation to work (i.e., they don't work, and you're trying to get them to work)? I've noticed that, on some laptops with buggy (?) APM implementations, the IDE controller/disks are never properly reinitialized at resume time, with the result that the FS gets really trashed (I basically had to reinstall FreeBSD, because, even if the directories get reconnected, various individual files are corrupted). I've fixed this on my laptop, but never made a proper patch (or fixed it "correctly"), as few people appear to have this problem (I appear to be the only one). If you want to see what I did, see: http://www.freebsd.org/cgi/getmsg.cgi?fetch=116906+120859+/usr/local/www/db/text/1999/freebsd-mobile/19991107.freebsd-mobile -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 10:41:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id B672114F6B for ; Fri, 12 Nov 1999 10:41:07 -0800 (PST) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id TAA19247; Fri, 12 Nov 1999 19:34:10 +0100 (MET) Received: (from ticso@localhost) by mail.cicely.de (8.9.0/8.9.0) id TAA31299; Fri, 12 Nov 1999 19:41:04 +0100 (CET) Date: Fri, 12 Nov 1999 19:41:04 +0100 From: Bernd Walter To: Josef Karthauser Cc: hackers@FreeBSD.ORG Subject: Re: Severe problems with softupdates. Message-ID: <19991112194103.A31258@cicely7.cicely.de> References: <19991111201148.A5748@florence.pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <19991111201148.A5748@florence.pavilion.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 11, 1999 at 08:11:49PM +0000, Josef Karthauser wrote: > > Kirk mentioned that he was confident that softupdates was 'safe', but I've > had files (from a previous crash - recovered from) in lost+found that I > didn't touch, and no-way should have become disconnected from the file > system - they weren't even in buffercache at the time of the crash. > > I believe that Brian has also had the same problems (at FreeBSDCon). > > Can people put their hands up if they believe that they've experienced this > so that we can determine whether there's a deeper softupdates problem that > we're ignoring on faith? > > Also if anyone knows how to recover from it I'd be very grateful to know. > My /usr partition is uncleanable (although I can 'mount -f' it!! nasty!!). > fsdb is a good way to handle such cases. I know such things very well but I have to say that it only happens in case of hardware or driver failures. I never got problems because of softupdates itself. The cases I got were a disk with broken TQC in the firmware and some data- coruption in some vinum versions using R5. Softupdates seem to be able to trigger bugs in other layers. -- 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 Nov 12 11: 6:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9FCF814A19 for ; Fri, 12 Nov 1999 11:06:10 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA05271; Fri, 12 Nov 1999 12:06:10 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA18259; Fri, 12 Nov 1999 12:06:31 -0700 (MST) Message-Id: <199911121906.MAA18259@harmony.village.org> To: Ollivier Robert Subject: Re: Should jail treat ip-number? Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 11 Nov 1999 20:52:38 +0100." <19991111205238.A52039@keltia.freenix.fr> References: <19991111205238.A52039@keltia.freenix.fr> <199911090824.KAA90295@zibbi.mikom.csir.co.za> <22398.942136151@critter.freebsd.dk> <19991110000004.A37063@keltia.freenix.fr> <19991111010837.C48604@server.nostromo.in-berlin.de> Date: Fri, 12 Nov 1999 12:06:31 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991111205238.A52039@keltia.freenix.fr> Ollivier Robert writes: : NAT breaks too many things (like IPsec, incoming connections and many : protocols) to be anything else than an abomination in my eyes. It breaks any protocol that encodes an IP address and/or a port into the data stream. Without datastream snooping and translation, talk, ftp real autio and a few others would break. When I was working on TIA (a commercial SLIRP-like program) we ran into these problems all the time. As soon as we put in upgrades for a recently released protocol, a new one would come along, or an old one would break in subtle ways (eg, we did the translation when we had no business doing the translation) leading to configuration nightmares. When it worked it was cool, when it didn't... This is why you can't, for example, NAT China :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 11:12:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B425A14C10 for ; Fri, 12 Nov 1999 11:12:15 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA05287; Fri, 12 Nov 1999 12:12:13 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA18289; Fri, 12 Nov 1999 12:12:35 -0700 (MST) Message-Id: <199911121912.MAA18289@harmony.village.org> To: Ben Rosengart Subject: Re: make -jN world; how to determine optimal value of N? Cc: Assar Westerlund , hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 11 Nov 1999 17:59:29 EST." References: Date: Fri, 12 Nov 1999 12:12:35 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Ben Rosengart writes: : D'oh -- I *meant* to add "besides trying different values and measuring" : -- if I had that much time on my hands, I wouldn't be worrying about how : long a make world takes. :-) Generally on FreeBSD machines that are otherwise unused and flush with memory, the formula I've seen for n is 4 * #CPU. This appears to be the sweet spot in the curves for people that have run experiments. Beyond this point addtional jobs had no benefit or actually slowed things down, at least according to the few tests that were run. Of course there is the whole area file system tuning that also is important (having enough spindles, using soft update, noatime, etc). From experiments I did in the 3.0 time frame, I found that file system options could gain a PPro 200 about 10% for slow disks and as much as 25% for very fast disks. The cc options also had a minor effect (on the order of 5% iirc). I took an untuned make buildworld down from about 1:50:00 to 1:05:00 by using the above tuning (and building on newer, faster disks). My machine wasn't flush enough with memory (only 96mb at the time) for me to contemplate adding -j to the mix. Others have reported improvements in the few percent range. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 11:16:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7037D14C10 for ; Fri, 12 Nov 1999 11:16:02 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA05317; Fri, 12 Nov 1999 12:16:00 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA18340; Fri, 12 Nov 1999 12:16:22 -0700 (MST) Message-Id: <199911121916.MAA18340@harmony.village.org> To: Ben Rosengart Subject: Re: make -jN world; how to determine optimal value of N? Cc: Assar Westerlund , hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 11 Nov 1999 18:16:42 EST." References: Date: Fri, 12 Nov 1999 12:16:22 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Ben Rosengart writes: : On what basis? I usually use larger values, like 12, on the theory that : I have more than enough memory, and if there's free CPU, there should : always be a process available to use it. People have measured things and found that the knee in the graph goes up after 4 on UP machines. This is usually due to increased context switch times, cache effects and sometimes thrashing of the disk cache. At least those are the usual suspects that have been trotted before the court of inquiry when -j 5 was a little slower than -j 4 and -j 30 was a whole lot slower. Additional processes aren't free. There is a cost for each one. Up to 4 the cost is less than the return. After 4 the return is less than the cost so there is a net loss for each new process. Put another way, 9 women can't get together and birth a baby in just 1 month.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 11:19:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9B14814BCE for ; Fri, 12 Nov 1999 11:19:54 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA05327; Fri, 12 Nov 1999 12:19:53 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA18365; Fri, 12 Nov 1999 12:20:15 -0700 (MST) Message-Id: <199911121920.MAA18365@harmony.village.org> To: nate@mt.sri.com (Nate Williams) Subject: Re: Determining (after the fact) if a routine was compiled as PIC? Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 12 Nov 1999 11:18:18 MST." <199911121818.LAA19728@mt.sri.com> References: <199911121818.LAA19728@mt.sri.com> Date: Fri, 12 Nov 1999 12:20:15 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911121818.LAA19728@mt.sri.com> Nate Williams writes: : Is there a way to look at a compiled file to see if it was compiled as : PIC? I've got some .o files that I don't have source code to, but : before I throw them into a shlib, I need to know if they are legal to : put into one? You can likely look at the relocation section of the .o file to see what relocations it has. Naively I'd expect PIC code to have none. objdump likely has some option that would prove useful. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 12:42:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (dynamic-64.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.192]) by hub.freebsd.org (Postfix) with ESMTP id 0396815038 for ; Fri, 12 Nov 1999 12:42:05 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA01044; Fri, 12 Nov 1999 20:41:33 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id SAA00389; Fri, 12 Nov 1999 18:23:54 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911121823.SAA00389@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Josef Karthauser Cc: hackers@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: Severe problems with softupdates. In-Reply-To: Message from Josef Karthauser of "Thu, 11 Nov 1999 20:11:49 GMT." <19991111201148.A5748@florence.pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Nov 1999 18:23:54 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > I believe that Brian has also had the same problems (at FreeBSDCon). > > Can people put their hands up if they believe that they've experienced this > so that we can determine whether there's a deeper softupdates problem that > we're ignoring on faith? I have to admit that I had a rather nasty crash while doing an installworld @FreeBSDCon. The result was a trashed /usr/bin and /usr/lib among other things. When I eventually got the machine back up, another installworld sorted things out. Sooo, I don't think in my case that anything was hurt that wasn't actually being updated, *but*, I did see some ``UNEXPECTED SOFT UPDATE INCONSISTENCY'' messages when it failed to ``fsck -p'' ! I don't know enough about the fs code to say what the problem is, or even to deny that it's a transient hardware problem.... perhaps encountered during a critical bit of softupdate syncing code and causing a hard crash ???!? [.....] > Joe. > -- > Josef Karthauser FreeBSD: How many times have you booted today? > Technical Manager Viagra for your server (http://www.uk.freebsd.org) > Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] -- 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 Fri Nov 12 13:30:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id D138215035 for ; Fri, 12 Nov 1999 13:30:53 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id QAA09242; Fri, 12 Nov 1999 16:37:48 -0500 (EST) Date: Fri, 12 Nov 1999 16:37:48 -0500 (EST) From: Ben Rosengart To: Warner Losh Cc: Assar Westerlund , hackers@FreeBSD.ORG Subject: Re: make -jN world; how to determine optimal value of N? In-Reply-To: <199911121912.MAA18289@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 12 Nov 1999, Warner Losh wrote: > Generally on FreeBSD machines that are otherwise unused and flush with > memory, the formula I've seen for n is 4 * #CPU. Thank you -- I didn't need a precise answer, just a good heuristic. This will do nicely. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 18: 7:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.uni-bielefeld.de (mail.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id EA3FB150D7 for ; Fri, 12 Nov 1999 18:06:59 -0800 (PST) (envelope-from bfischer@Techfak.uni-bielefeld.de) Received: from frolic.no-support.loc (ppp36-152.hrz.uni-bielefeld.de) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FL400G7I5V7WJ@mail.uni-bielefeld.de> for freebsd-hackers@FreeBSD.ORG; Sat, 13 Nov 1999 03:06:44 +0100 (MET) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id DAA71176 for freebsd-hackers@FreeBSD.ORG; Sat, 13 Nov 1999 03:06:26 +0100 (CET envelope-from bjoern) Date: Sat, 13 Nov 1999 03:06:26 +0100 From: Bjoern Fischer Subject: Which egcs port should I use? To: freebsd-hackers@FreeBSD.ORG Message-id: <19991113030626.A659@frolic.no-support.loc> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, as it seems that egcs will be *the* C-compiler in FreeBSD4.x I would like to use it in -STABLE, too. There are at least two ports for egcs: lang/egcs and lang/gcc-devel. I want to use a version that is likely to be used in the first release of 4.x, or---at least---the version that is most compatible according to the user interface. Looking at the patches of the ports, there are some changes to the gcc user interface opposed to the 3.x old gcc-2.7.x. (e.g. no -R any more, why?). Which egcs would you recommend, if I want to minimize the hassle to switch from that egcs to the FreeBSD4.x native egcs? Both ports don't seem to fix that ${tooldir} crap. How is this handled in 4.x? Bj=F6rn --=20 -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+=20 ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 21:18:52 1999 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 5865214F45 for ; Fri, 12 Nov 1999 21:18:38 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id VAA71152; Fri, 12 Nov 1999 21:18:33 -0800 (PST) (envelope-from obrien) Date: Fri, 12 Nov 1999 21:18:33 -0800 From: "David O'Brien" To: Bjoern Fischer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Which egcs port should I use? Message-ID: <19991112211833.A71113@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <19991113030626.A659@frolic.no-support.loc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <19991113030626.A659@frolic.no-support.loc> X-Operating-System: FreeBSD 3.3-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 13, 1999 at 03:06:26AM +0100, Bjoern Fischer wrote: > Which egcs would you recommend, if I want to minimize the hassle to > switch from that egcs to the FreeBSD4.x native egcs? /usr/ports/lang/egcs. It is the one that is released code. ``gcc-devel'' is equivent to our -CURRENT and can bleed just as bad. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 22:45:50 1999 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 7A1EC14ECD for ; Fri, 12 Nov 1999 22:45:44 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id WAA71386; Fri, 12 Nov 1999 22:45:38 -0800 (PST) (envelope-from obrien) Date: Fri, 12 Nov 1999 22:45:38 -0800 From: "David O'Brien" To: John Baldwin , freebsd-hackers@FreeBSD.ORG Subject: Re: Proposal for the kill-list (userland nfs) Message-ID: <19991112224538.B71113@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <199910052249.PAA04853@miles.cs.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <199910052249.PAA04853@miles.cs.washington.edu> X-Operating-System: FreeBSD 3.3-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 05, 1999 at 03:49:31PM -0700, Alec Wolman wrote: > > Digital Unix, aka Compaq Tru64 Unix, formerly know as DEC OSF/1 > > supports this syntax. In fact, this is the only syntax it supports, > > IIRC, so FreeBSD is not the only OS to use it. Ultrix was the one that only suported this syntax. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Nov 12 22:46:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.pdc.kth.se (assaris2.pdc.kth.se [130.237.221.57]) by hub.freebsd.org (Postfix) with ESMTP id B15D915109 for ; Fri, 12 Nov 1999 22:46:38 -0800 (PST) (envelope-from assar@assaris.pdc.kth.se) Received: (from assar@localhost) by assaris.pdc.kth.se (8.9.3/8.9.3) id HAA20257; Sat, 13 Nov 1999 07:46:18 +0100 (CET) (envelope-from assar) To: Ben Rosengart Cc: hackers@freebsd.org Subject: Re: make -jN world; how to determine optimal value of N? References: From: Assar Westerlund Date: 13 Nov 1999 07:46:13 +0100 In-Reply-To: Ben Rosengart's message of "Thu, 11 Nov 1999 18:16:42 -0500 (EST)" Message-ID: <5l3dualwi2.fsf@assaris.pdc.kth.se> Lines: 13 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Rosengart writes: > On 12 Nov 1999, Assar Westerlund wrote: > > > Other than that, I think the > > `make -j4' suggested for a single CPU in the handbook is a fairly good > > approximation. > > On what basis? Simple experiments on various machines. YMMV, but I think that's a good general guideline. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 13 0:11:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3DEB014E29 for ; Sat, 13 Nov 1999 00:11:10 -0800 (PST) (envelope-from partha@cs.duke.edu) Received: from moe.cs.duke.edu (moe.cs.duke.edu [152.3.140.74]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id DAA19821 for ; Sat, 13 Nov 1999 03:11:09 -0500 (EST) Received: from localhost (partha@localhost) by moe.cs.duke.edu (8.8.5/8.6.9) with ESMTP id DAA10902 for ; Sat, 13 Nov 1999 03:10:06 -0500 (EST) X-Authentication-Warning: moe.cs.duke.edu: partha owned process doing -bs Date: Sat, 13 Nov 1999 03:10:06 -0500 (EST) From: "Parthasarathy M. Aji" To: freebsd-hackers@FreeBSD.org Subject: System Call Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sir, How do I set up a system call of my own in the FreeBSD kernel? 1) Do I just change the syscalls.master and my new function and rebuild the entire kernel?. If so where do I put my implementation files? in the same directory as syscalls.master exists? I am new to writing custom system calls.. Thank you, regards, Partha Aji To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 13 0:56:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles538.castles.com [208.214.165.102]) by hub.freebsd.org (Postfix) with ESMTP id E291B1501F; Sat, 13 Nov 1999 00:56:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA00574; Sat, 13 Nov 1999 00:46:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911130846.AAA00574@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian McGovern Cc: hackers@freebsd.org, peter@freebsd.org Subject: Re: How does sio handle full clists? In-reply-to: Your message of "Tue, 09 Nov 1999 10:55:52 EST." <199911091555.KAA01889@bmcgover-pc.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Nov 1999 00:46:56 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've been digging around in the sio driver, trying to find out how it handles > receive interrupts when the clists are full. > > What I think I found (which is why I'm asking) is that if an RX interrupt > occurs, and the clists are full and the driver can't offload all of the > data from the UART, it disables the interrupts. I don't believe it does this, no. > I guess I'm looking for confirmation of this, and, if I'm way off, maybe a > quick explanatio of what _really_ happens. I'm looking at trying to reuse > the behavior elsewhere, so I want a good understanding of the process before I > get myself in to too much trouble. You should expect to see the dreaded "tty-level buffer overflow" message, when the soft interrupt handler flushes the interrupt-level buffers into the tty subsystem. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 13 7:12:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 100D614CAB; Sat, 13 Nov 1999 07:12:20 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id KAA02046; Sat, 13 Nov 1999 10:12:18 -0500 (EST) (envelope-from jobaldwi@vt.edu) Message-Id: <199911131512.KAA02046@server.baldwin.cx> X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19991112224538.B71113@relay.nuxi.com> Date: Sat, 13 Nov 1999 10:12:18 -0500 (EST) From: John Baldwin To: "David O'Brien" Subject: Re: Proposal for the kill-list (userland nfs) Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Nov-99 David O'Brien wrote: > On Tue, Oct 05, 1999 at 03:49:31PM -0700, Alec Wolman wrote: >> > Digital Unix, aka Compaq Tru64 Unix, formerly know as DEC OSF/1 >> > supports this syntax. In fact, this is the only syntax it >> > supports, >> > IIRC, so FreeBSD is not the only OS to use it. > > Ultrix was the one that only suported this syntax. Ah. One thing to note is that the graphical configuration utilities under at least 4.0D would use the /dir@machine syntax when generating /etc/fstab. --- John Baldwin -- http://www.cslab.vt.edu/~jobaldwi/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/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 Sat Nov 13 7:57:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id C6F411506E for ; Sat, 13 Nov 1999 07:57:54 -0800 (PST) (envelope-from crandall@matchlogic.com) Received: by houston.matchlogic.com with Internet Mail Service (5.5.2650.21) id ; Sat, 13 Nov 1999 08:57:52 -0700 Message-ID: <64003B21ECCAD11185C500805F31EC0304621DC8@houston.matchlogic.com> From: Charles Randall To: freebsd-hackers@freebsd.org Subject: readdir_r vs readdir in libc_r? Date: Sat, 13 Nov 1999 08:57:43 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using FreeBSD 3.3-R and have noted that there's a readdir() in libc_r but no readdir_r(). Based on archived messages from last year, it appears that the readir() in libc_r is not reentrant. To access readdir from multiple threads with different DIR entries, it appears that all of the directory functions must be protected by a locking mechanism. What is the current status of this? Charles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 13 8:13:52 1999 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 43F8614E81 for ; Sat, 13 Nov 1999 08:13:48 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA21693; Sat, 13 Nov 1999 11:12:30 -0500 (EST) Date: Sat, 13 Nov 1999 11:12:30 -0500 (EST) From: Daniel Eischen Message-Id: <199911131612.LAA21693@pcnet1.pcnet.com> To: crandall@matchlogic.com, freebsd-hackers@FreeBSD.ORG Subject: Re: readdir_r vs readdir in libc_r? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein has ported this from NetBSD along with pthread_cancel support. I'm suppose to be reviewing it - actually I'm done, I've just got to gather my comments and get back to him. I'll get back to him this weekend. > I'm using FreeBSD 3.3-R and have noted that there's a readdir() in libc_r > but no readdir_r(). > > Based on archived messages from last year, it appears that the readir() in > libc_r is not reentrant. To access readdir from multiple threads with > different DIR entries, it appears that all of the directory functions must > be protected by a locking mechanism. > > What is the current status of this? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 13 8:28:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.uni-bielefeld.de (mail.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id 3ABE81515F; Sat, 13 Nov 1999 08:28:36 -0800 (PST) (envelope-from bfischer@Techfak.uni-bielefeld.de) Received: from frolic.no-support.loc (ppp36-224.hrz.uni-bielefeld.de) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FL5004MG9RLJS@mail.uni-bielefeld.de>; Sat, 13 Nov 1999 17:28:35 +0100 (MET) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id RAA00581; Sat, 13 Nov 1999 17:25:45 +0100 (CET envelope-from bjoern) Date: Sat, 13 Nov 1999 17:25:45 +0100 From: Bjoern Fischer Subject: Re: Which egcs port should I use? In-reply-to: <19991112211833.A71113@relay.nuxi.com>; from obrien@FreeBSD.ORG on Fri, Nov 12, 1999 at 09:18:33PM -0800 To: David O'Brien Cc: freebsd-hackers@FreeBSD.ORG Message-id: <19991113172545.A336@frolic.no-support.loc> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable References: <19991113030626.A659@frolic.no-support.loc> <19991112211833.A71113@relay.nuxi.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 12, 1999 at 09:18:33PM -0800, David O'Brien wrote: > On Sat, Nov 13, 1999 at 03:06:26AM +0100, Bjoern Fischer wrote: > > Which egcs would you recommend, if I want to minimize the hassle to > > switch from that egcs to the FreeBSD4.x native egcs? >=20 > /usr/ports/lang/egcs. It is the one that is released code. > ``gcc-devel'' is equivent to our -CURRENT and can bleed just as bad. Thank you for your help. Yes, egcs is 2.95.x and gcc-devel is 2.96 and the bleeding edge. This is irrelevant since I don't plan to use egcs for production. I'd like to know whether the ports behave like the native compiler in -CURRENT. E.g. now I tell Joe User to use -R/vol/foo/lib for the runtime library search path (Joe User is familiar with Solaris and enjoys everything he already knows). But when he wishes to perform some experiments wich egcs, then he should use -Wl,-rpath. And when we switch to the next FreeBSD brach, I tell him that he has to use something completely different for the native egcs. Bj=F6rn --=20 -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+=20 ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 13 12:28: 9 1999 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 34E2614C15 for ; Sat, 13 Nov 1999 12:28:04 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id MAA77673; Sat, 13 Nov 1999 12:28:03 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id MAA15888; Sat, 13 Nov 1999 12:28:03 -0800 (PST) (envelope-from obrien) Date: Sat, 13 Nov 1999 12:28:03 -0800 From: "David O'Brien" To: Bjoern Fischer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Which egcs port should I use? Message-ID: <19991113122802.E90421@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <19991113030626.A659@frolic.no-support.loc> <19991112211833.A71113@relay.nuxi.com> <19991113172545.A336@frolic.no-support.loc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991113172545.A336@frolic.no-support.loc>; from bfischer@Techfak.Uni-Bielefeld.DE on Sat, Nov 13, 1999 at 05:25:45PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 13, 1999 at 05:25:45PM +0100, Bjoern Fischer wrote: > I'd like to know whether the ports behave like the native compiler > in -CURRENT. E.g. now I tell Joe User to use -R/vol/foo/lib for .. > And when we switch to the next FreeBSD brach, I tell him that he > has to use something completely different for the native egcs. I try hard to put most of the FreeBSD extensions into the ports. Especially WRT compiling/linking options and behavior. I believe you'll find that things between 4.0's compiler and the `egcs' port are the same. The biggest difference is the 4.0 native compilers ability to generate a.out binaries. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 13 12:48:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from io.yi.org (24.66.174.118.bc.wave.home.com [24.66.174.118]) by hub.freebsd.org (Postfix) with ESMTP id C045214CF2 for ; Sat, 13 Nov 1999 12:48:28 -0800 (PST) (envelope-from jake@checker.org) Received: from io.yi.org (localhost [127.0.0.1]) by io.yi.org (Postfix) with ESMTP id 6CC121FCC; Sat, 13 Nov 1999 12:48:33 -0800 (PST) X-Mailer: exmh version 2.1.1 10/15/1999 To: "Parthasarathy M. Aji" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: System Call In-reply-to: Your message of "Sat, 13 Nov 1999 03:10:06 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Nov 1999 12:48:33 -0800 From: Jake Burkholder Message-Id: <19991113204833.6CC121FCC@io.yi.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Dear Sir, > How do I set up a system call of my own in the FreeBSD kernel? > 1) Do I just change the syscalls.master and my new function and rebuild > the entire kernel?. If so where do I put my implementation files? in the > same directory as syscalls.master exists? I am new to writing custom system > calls.. Thank you, I think the easiest way to do this is with a kld. It's less intrusive and allows you to unload/recompile/reload without recompiling the whole kernel and rebooting. There should be a simple example of how to do this in /usr/share/examples/kld/syscall. Also check out http://thc.inferno.tusculum.edu/files/thc/bsdkern.html hope this helps... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 13 13:14:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 7DE4C15310 for ; Sat, 13 Nov 1999 13:14:05 -0800 (PST) (envelope-from xavier@cs.duke.edu) Received: from mackerel.cs.duke.edu (mackerel.cs.duke.edu [152.3.140.156]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id QAA26433 for ; Sat, 13 Nov 1999 16:14:04 -0500 (EST) Received: from localhost (xavier@localhost) by mackerel.cs.duke.edu (8.8.5/8.6.9) with ESMTP id QAA07554 for ; Sat, 13 Nov 1999 16:14:03 -0500 (EST) X-Authentication-Warning: mackerel.cs.duke.edu: xavier owned process doing -bs Date: Sat, 13 Nov 1999 16:14:02 -0500 (EST) From: Clinton Xavier Berni To: freebsd-hackers@freebsd.org Subject: upcall Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, How do I access a user level data structure from the kernel. Are there any Upcalls that I could use? Xavier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 13 13:55:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 1FDA214BE6 for ; Sat, 13 Nov 1999 13:55:27 -0800 (PST) (envelope-from rminnich@lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id OAA63731 for ; Sat, 13 Nov 1999 14:55:26 -0700 (MST) X-Authentication-Warning: acl.lanl.gov: rminnich owned process doing -bs Date: Sat, 13 Nov 1999 14:55:26 -0700 From: "Ronald G. Minnich" To: freebsd-hackers@FreeBSD.ORG Subject: Re: System Call In-Reply-To: <19991113204833.6CC121FCC@io.yi.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 13 Nov 1999, Jake Burkholder wrote: > > How do I set up a system call of my own in the FreeBSD kernel? > > I think the easiest way to do this is with a kld. It's less intrusive yes, if you're doing a system call use freebsd's excellent kld support. It's really pretty slick. Don't muck with the kernel src tree. You may think it's hard to do this in a module if you're used to linux, but it's not hard at all in freebsd. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 13 18: 3: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from massive.geek.edu (massive.geek.edu [216.73.11.10]) by hub.freebsd.org (Postfix) with ESMTP id 47C55151EF for ; Sat, 13 Nov 1999 18:02:40 -0800 (PST) (envelope-from jontow@massive.geek.edu) Received: (from jontow@localhost) by massive.geek.edu (8.9.3/8.9.2) id VAA20062 for freebsd-hackers@freebsd.org; Sat, 13 Nov 1999 21:03:58 -0500 (EST) (envelope-from jontow) Date: Sat, 13 Nov 1999 21:03:57 -0500 From: Jonathan Towne To: freebsd-hackers@freebsd.org Subject: Thinkpad 750 Message-ID: <19991113210357.A20018@massve.geek.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a Thinkpad 750, 2 pc card slots, no cdrom, only a mere 486SL/33 CPU, and 8meg of RAM, and i'm trying to install a copy of 3.3-RELEASE on it to replace win3.11. Since the thinkpad uses an odd keyboard of some sort, i give syscons the 0x2 flag, which fixed the keyboard one time (the only time i got it to boot correctly). Anyways, i've tried the standard installation floppies, and the pccard floppies, neither would get past the "Probing devices, please wait (...)" dialog, it just hangs there, and will not accept any keyboard commands or anything like that. This problem previously happened to me on a set of installation floppies that didn't have FPU emulation in the kernel on my 486sx/25, but, 3.3-RELEASE is supposed to have it, so, I'm sure that can't be the problem, any answers would be greatly appreciated.. :) -- Jonathan Towne jontow@massive.geek.edu/wrongway@slic.com Systems Administrator http://massive.geek.edu/ -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GU d- s: a--- C+++ UB++++ P L- E--- W--- N++ o K w--- O-- M V- PS PE Y-- PGP- t+ 5 X+ R+ tv- b+ DI+ D++ G e- h-- r-- y ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 13 19:52:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pluto.cpe.ku.ac.th (pluto.cpe.ku.ac.th [158.108.32.150]) by hub.freebsd.org (Postfix) with ESMTP id C041614BC4 for ; Sat, 13 Nov 1999 19:52:30 -0800 (PST) (envelope-from stt@pluto.cpe.ku.ac.th) Received: from localhost (stt@localhost) by pluto.cpe.ku.ac.th (8.9.3/8.9.3) with ESMTP id KAA00308 for ; Sun, 14 Nov 1999 10:54:08 GMT Date: Sun, 14 Nov 1999 10:54:07 +0000 (GMT) From: Sunthiti Patchararungruang To: freebsd-hackers@freebsd.org Subject: How to do source route Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sir, I need to create a program to forward IP packets, already have IP header. All packets have destination in remote network. Therefore, I cannot send them with normal raw-IP-socket. I think I need to do source-route packet sending. However, I don't know how to do it. Please give me the method. Thank you. Regards, Sunthiti Patchararungruang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Nov 13 23:58:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id D56B014CE3 for ; Sat, 13 Nov 1999 23:58:15 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 3040702 invoked from network); 14 Nov 1999 07:58:15 -0000 Received: from d125.paris-38.cybercable.fr (HELO cybercable.fr) ([212.198.38.125]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 14 Nov 1999 07:58:15 -0000 Message-ID: <382E6BA2.83A1BF48@cybercable.fr> Date: Sun, 14 Nov 1999 08:58:26 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Jonathan Towne Cc: freebsd-hackers@freebsd.org Subject: Re: Thinkpad 750 References: <19991113210357.A20018@massve.geek.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan Towne wrote: > > I've got a Thinkpad 750, 2 pc card slots, no cdrom, only a mere > 486SL/33 CPU, and 8meg of RAM, and i'm trying to install a copy* ^^^^ There was a time where you had to have at least 12 megs of RAM to install FreeBSD. You may check the errata and release notes for 3.3 to find out if you can install with only 8 megs. TfH > of 3.3-RELEASE on it to replace win3.11. Since the thinkpad > uses an odd keyboard of some sort, i give syscons the 0x2 flag, > which fixed the keyboard one time (the only time i got it to > boot correctly). Anyways, i've tried the standard installation > floppies, and the pccard floppies, neither would get past the > "Probing devices, please wait (...)" dialog, it just hangs there, > and will not accept any keyboard commands or anything like that. > This problem previously happened to me on a set of installation > floppies that didn't have FPU emulation in the kernel on my > 486sx/25, but, 3.3-RELEASE is supposed to have it, so, I'm sure > that can't be the problem, any answers would be greatly > appreciated.. :) > > -- > Jonathan Towne jontow@massive.geek.edu/wrongway@slic.com > Systems Administrator http://massive.geek.edu/ > > -----BEGIN GEEK CODE BLOCK----- > Version: 3.1 > GU d- s: a--- C+++ UB++++ P L- E--- W--- N++ o K w--- > O-- M V- PS PE Y-- PGP- t+ 5 X+ R+ tv- b+ DI+ D++ > G e- h-- r-- y > ------END GEEK CODE BLOCK------ > > 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