From owner-freebsd-hackers Sun Oct 10 3:29:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 6115C15922 for ; Sun, 10 Oct 1999 03:26:27 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id MAA49956 for ; Sun, 10 Oct 1999 12:26:18 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Sun, 10 Oct 1999 12:26:17 +0200 (CEST) From: Leif Neland To: freebsd-hackers@freebsd.org Subject: mrtg, user-ppp 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'd like to plot uptime and number of calls from ppp to mrtg. Any 'easy' way to ask ppp for these values, getting the answer for number of seconds online since last asked? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 6:50:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id EB39715044 for ; Sun, 10 Oct 1999 06:50:52 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id JAA84558; Sun, 10 Oct 1999 09:49:21 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Sun, 10 Oct 1999 09:49:20 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Leif Neland Cc: freebsd-hackers@FreeBSD.org Subject: Re: mrtg, user-ppp 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 Sun, 10 Oct 1999, Leif Neland wrote: > I'd like to plot uptime and number of calls from ppp to mrtg. > > Any 'easy' way to ask ppp for these values, getting the answer for number > of seconds online since last asked? > Store the time from the previous call after each call, as with a (non-thread-safe) "static" variable in C. You can accomplish reading the time up pretty reasonably using either pppctl or just working directly with the ppp socket in the program. > Leif > -- 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 Oct 10 6:59:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id B89ED1520E for ; Sun, 10 Oct 1999 06:59:46 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-147.skylink.it [194.185.55.147]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id QAA10704; Sun, 10 Oct 1999 16:00:12 +0200 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id JAA06313; Sun, 10 Oct 1999 09:04:50 GMT X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Sun, 10 Oct 1999 09:04:50 GMT Date: Sun, 10 Oct 1999 11:04:50 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: "Kenneth D. Merry" Cc: Randell Jesup , hackers@FreeBSD.ORG Subject: Re: CAM-ification - documentation In-Reply-To: <199910092224.QAA09485@panzer.kdm.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 > > Ick. Polling == bad. Interrupts == good. This isn't a single- > > tasking OS ala Win9x. This goes double for SCSI drivers, which are > > inherently async and overlapped. > > I never said polling was good. Nick just asked about polling, and I > commented on how it could be done. I have no idea why he wanted to know > about polling, though. Well, I am not sure whether I need polling, but there are some problems related to the fact that multiple USB transactions are needed for one SCSI transaction. Combined with the fact that some requests are done asynchronously (clear endpoint halt at the end of a transaction if the transaction failed) it might be useful to do polling to avoid massively complex code. Nick -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 7:21:31 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 77D2F15419 for ; Sun, 10 Oct 1999 07:20:52 -0700 (PDT) (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 7C7741CC8; Sun, 10 Oct 1999 22:20:50 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: tom brown Cc: hackers@freebsd.org Subject: Re: Single character errors in source files, stop kernel compile! In-reply-to: Your message of "Sat, 09 Oct 1999 22:41:51 MST." <19991010054151.16487.rocketmail@web108.yahoomail.com> Date: Sun, 10 Oct 1999 22:20:50 +0800 From: Peter Wemm Message-Id: <19991010142050.7C7741CC8@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tom brown wrote: > Hi > > I'm running FreebSD 3.3 on a AMD-K6 box thats totally > SCSI. > The controller is Adaptec 2940 and the drive in > question is > a 40MB/sec IBM 9GB (SCSI 3?).. > > In the process of attempting to make a new kernel I > follow > the usual procedure. > > %cd /sys/i386/conf/ > %config KERNEL > %cd ../../compile/KERNEL > %make depend > > Everything to this point completes and reports no > errors. > > %make > > This is where I start to get failures. The compiler > will stop > with code 1 and will claim that the reason is a single > character > error in the source code. A typical example would be > the word > "struct" spelt "strwct". Clearly there is a problem > which I > doubt is the source code. 'u' is ascii code 0x75. 'w' is ascii code 0x77. You're seeing a classic undetected single bit error from cheap parity-less ram. Bit 1 (0x2) in some particular cell is turning on all by itself. > To work around this I just repeat the make command > again and > again until the job is done. then I install the kernel > and > reboot sucessfully. > > Any ideas? I'm tempted to think it's some kind of a > problem > with the drive, but I haven't had any real hard > failures. Either look out for a decent memory tester to locate the bad SIMM, or get the memory tested by a simm tester, or swap it out and start again. That's easier said than done with today's memory prices though. It's not overclocked is it? Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 7:40:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id E68C8151C2 for ; Sun, 10 Oct 1999 07:40:06 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id QAA13182 for FreeBSD-hackers@freebsd.org; Sun, 10 Oct 1999 16:37:37 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id IAA54305 for FreeBSD-hackers@freebsd.org; Sun, 10 Oct 1999 08:54:28 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910100654.IAA54305@yedi.iaf.nl> Subject: buildworld on alpha hangs To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Sun, 10 Oct 1999 08:54:28 +0200 (CEST) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.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 Looking at buildworld of -current on a NoName Alpha: 0 26262 26135 255 10 0 576 128 wait I+ p0 0:00.18 /usr/obj/usr 0 26263 26262 172 10 0 880 112 wait I+ p0 0:00.15 /bin/sh -ec 0 27444 26263 152 10 0 752 216 wait I+ p0 0:00.63 /usr/obj/usr 0 27505 27444 175 10 0 872 112 wait I+ p0 0:00.03 /bin/sh -ec 0 27506 27505 171 10 0 1352 336 wait I+ p0 0:00.10 cc -O -pipe 0 27507 27506 9 -18 0 1000 0 objtrm DE+ p0 0:03.49 (cpp) 0 27999 27998 11 10 0 888 536 wait Ss p1 0:00.42 -sh (sh) 0 28003 27999 36 37 0 600 424 - R+ p1 0:00.03 ps -axl 0 204 1 49 3 0 1320 128 ttyin Is+ v0 0:00.10 /usr/libexec 0 205 1 52 3 0 1320 128 ttyin Is+ v1 0:00.10 /usr/libexec The build hangs, the offending process is I think 27507. This has proven to be a repeatable hangup. There are always objtrm processes around. My other Alpha machine using the same source (which is on a local disk on each machine, so no NFS BTW) has no problems building world. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Sun Oct 10 8:57: 4 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 DDEAB155BB for ; Sun, 10 Oct 1999 08:56:34 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p06-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.135]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id AAA16503; Mon, 11 Oct 1999 00:56:28 +0900 (JST) Message-ID: <3800A516.7AE488CE@newsguy.com> Date: Sun, 10 Oct 1999 23:39: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: tom brown Cc: hackers@FreeBSD.ORG Subject: Re: Single character errors in source files, stop kernel compile! References: <19991010054151.16487.rocketmail@web108.yahoomail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tom brown wrote: > > The /etc/make.conf has -O2 optimization for the > kernel. We do not support -O2, only -O. There has been problems in the past with higher levels of optimization. Now, what that means is not that you can't you -O2. You can. But before you seek _support_, try a supported configuration. Like using a kernel built with -O. That said, it looks like bad memory. Or maybe overclocking. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 9:11:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id D41E71502F for ; Sun, 10 Oct 1999 09:11:23 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id TAA08466; Sun, 10 Oct 1999 19:11:14 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Date: Sun, 10 Oct 1999 19:11:14 +0300 (EEST) From: Narvi To: Wilfredo Sanchez Cc: Pat Dirks , FreeBSD Hackers Subject: Re: Apple's planned appoach to permissions on movable filesystems In-Reply-To: <199910070004.RAA29320@scv2.apple.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 Sorry, this is somewhat late. On Wed, 6 Oct 1999, Wilfredo Sanchez wrote: > | Have you given consideration to systems where the user/group > database is > | kept for (possibly a large) number of computers in a centralised > manner by > | say hesiod or nys (nis+). It would be nice if there was an easy > interface > | with these so that distributing the local system id numbers need not be > | done by hand. > > It's complicated. We do have a distributed database (NetInfo) and > we considered perhaps using the name of the NetInfo domain to > determine local vs. foreign. The problem is that distributed > databases are sometimes hierarchical, and can be mixed. For example: > Well, people for some reason miss the point. What I was talking about is the 'interface', and that it be easy to attach things to it. Site A will want to distribute the ids via hesiod. Site B will want to distribute the ids via nis+. Site C wants to do it via Netinfo Site D wantd to use LDAP. There may be others (SNMP?). One way to do this is for example to have: a) a parameter (by default null) that specifies which program to run to get a list of local system ids b) a parameters (by default null) that specifies which program to run if we want to verify if a certain id has been added to the set of local ids since the startup. As the program can be anything (inc. a shell script) almost any way of distributing the local systems ids can be accomodated. This is of course just one way to achieve it (think of PAM). [snip] > > -Fred > > > -- > Wilfredo Sanchez, wsanchez@apple.com > Apple Computer, Inc., Core Operating Systems / BSD > Technical Lead, Darwin Project > 1 Infinite Loop, 302-4K, Cupertino, CA 95014 > > > > 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 Oct 10 9:34:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 1BA8A155E0 for ; Sun, 10 Oct 1999 09:33:44 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id TAA08629 for ; Sun, 10 Oct 1999 19:33:44 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Date: Sun, 10 Oct 1999 19:33:44 +0300 (EEST) From: Narvi To: hackers@FreeBSD.ORG Subject: Fun with vinum 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 Should you decide to use vinum keep in mind that you: a) reboot to make sure that whatever you just set up can automatically start itself b) alternatively vinum l vinum makedev vinum create -f configfile vinum start is your friend and avoids most of the problem IMHO it should not panick the kernel when it doesn't like the disk setup. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 9:42:10 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 4EA49154B0 for ; Sun, 10 Oct 1999 09:41:57 -0700 (PDT) (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 MAA06015 for ; Sun, 10 Oct 1999 12:41:56 -0400 (EDT) (envelope-from robert@cyrus.watson.org) Date: Sun, 10 Oct 1999 12:41:55 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: hackers@freebsd.org Subject: [Fwd: clock(3) runs backwards! (fwd)] (fwd) 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 This was a BSDI mailing list post, but I gave it a try on my 3.3-RELEASE FreeBSD machine and got the following: fledge:/tmp> ./clocktest 1.000000 - 0.000000 = 1.000000 2.000000 - 1.000000 = 1.000000 1.000000 - 2.000000 = 4294967295.000000 3.000000 - 1.000000 = 2.000000 2.000000 - 3.000000 = 4294967295.000000 4.000000 - 2.000000 = 2.000000 3.000000 - 4.000000 = 4294967295.000000 5.000000 - 3.000000 = 2.000000 4.000000 - 5.000000 = 4294967295.000000 6.000000 - 4.000000 = 2.000000 5.000000 - 6.000000 = 4294967295.000000 7.000000 - 5.000000 = 2.000000 6.000000 - 7.000000 = 4294967295.000000 8.000000 - 6.000000 = 2.000000 7.000000 - 8.000000 = 4294967295.000000 9.000000 - 7.000000 = 2.000000 10.000000 - 9.000000 = 1.000000 9.000000 - 10.000000 = 4294967295.000000 10.000000 - 11.000000 = 4294967295.000000 12.000000 - 10.000000 = 2.000000 Seems like I'm seeing the behavior they describe--whether that's bad is another question, but seemed interesting. Any suggestions? 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 ---------- Forwarded message ---------- Date: Sun, 10 Oct 1999 12:33:16 -0400 From: support@safeport.com To: Robert Watson Subject: [Fwd: clock(3) runs backwards! (fwd)] Did you see this? If its not on FreeBSD, and you are not archiving the BSDI list, I can send you the thread. It turns our this is not a silly programming error, this guy wrote the current C ANSI standard. -------- Original Message -------- Subject: clock(3) runs backwards! (fwd) Date: Thu, 7 Oct 1999 14:53:48 -0400 (EDT) From: larry.jones@sdrc.com (Larry Jones) To: bsdi-users@mailinglists.org FYI. Also sent to problems@bsdi.com. > Description: > Occasionally, clock(3) will return a value which is less than > the value returned by a previous call. > > Release: > 4.0.1 > > Repeat-By: > Run the following test program; a single run is usually sufficient > to observe the problem. > > #include > #include > #include > > int main() > { > int i; > clock_t t0, t1; > > for (i = 0; i < 20; i++) { > t0 = clock(); > do { > t1 = clock(); > } while(t0 == t1); > printf( " %f - %f = %f\n", (double)t1, (double)t0, > (double)(t1-t0)); > } > return 0; > } > > Fix: > Converting the user and system time to clock ticks before adding > them together causes the problem due to roundoff error and the > system time not being monotonically increasing. Assuming that > the actuall sum of user and system time *is* monotonically > increasing (which it seems to be), adding them together before > converting will solve the problem: > > --- /cdrom/lib/libc/gen/clock.c Thu Feb 2 18:20:13 1995 > +++ ./clock.c Wed Oct 6 13:14:20 1999 > @@ -39,12 +39,6 @@ > #include > #include > > -/* > - * Convert usec to clock ticks; could do (usec * CLK_TCK) / 1000000, > - * but this would overflow if we switch to nanosec. > - */ > -#define CONVTCK(r) (r.tv_sec * CLK_TCK + r.tv_usec / (1000000 / CLK_TCK)) > - > clock_t > clock() > { > @@ -52,5 +46,7 @@ > > if (getrusage(RUSAGE_SELF, &ru)) > return ((clock_t) -1); > - return((clock_t)((CONVTCK(ru.ru_utime) + CONVTCK(ru.ru_stime)))); > + return((clock_t)((ru.ru_utime.tv_sec + ru.ru_stime.tv_sec) * CLK_TCK + > + (ru.ru_utime.tv_usec + ru.ru_stime.tv_usec) / > + (1000000 / CLK_TCK))); > } -Larry Jones Whatever it is, it's driving me crazy! -- Calvin --------------------------------------------------------------------- To unsubscribe, e-mail: bsdi-users-unsubscribe@mailinglists.org For additional commands, e-mail: bsdi-users-help@mailinglists.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 10:59:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.tvol.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id BE47C14ED2 for ; Sun, 10 Oct 1999 10:59:13 -0700 (PDT) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net (jesup.eng.tvol.net [10.32.2.26]) by mail.tvol.com (8.8.8/8.8.3) with ESMTP id NAA25618; Sun, 10 Oct 1999 13:54:35 -0400 (EDT) Reply-To: Randell Jesup To: tom brown Cc: hackers@freebsd.org Subject: Re: Single character errors in source files, stop kernel compile! From: Randell Jesup Date: 10 Oct 1999 13:54:29 +0000 In-Reply-To: tom brown's message of "Sat, 9 Oct 1999 22:41:51 -0700 (PDT)" Message-ID: X-Mailer: Gnus v5.6.43/Emacs 20.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tom brown writes: >I'm running FreebSD 3.3 on a AMD-K6 box thats totally SCSI. >This is where I start to get failures. The compiler will stop with code 1 >and will claim that the reason is a single character error in the source >code. A typical example would be the word "struct" spelt "strwct". >Any ideas? I'm tempted to think it's some kind of a problem with the >drive, but I haven't had any real hard failures. It sounds like a classic case of incorrect cabling or bad cable/termination; or possibly bad memory, or overclocking/overheating. Check your cable; make sure it's tight, make sure you're running _good_ terminators and not violating any specs (did you know the maximum stub length is ~3 inches, and that there's a _minimum_ distance between connectors? (I think it's ~12 inches.)) You are using a good terminator, yes? Are any drives outside the box? Termination at both ends of the bus? Another check may be to use camcontrol to lower the speed or width the SCSI bus is using for transfers. (camcontrol negotiate). NOTE: you can screw things up royally with camcontrol if you don't know what you're doing. Try something like: camcontrol negotiate -v to find out about the device negotiation parameters, and camcontrol negotiate -R 5.0 -a to set the max sync transfer rate to 5MHz (slow). You could add a "-W 8" to limit it to 8-bit-wide transfers. You could even try lower rates. WARNING: you can screw up your filesystems playing with camcontrol - easily. Also, while I know SCSI and CAM, I don't have SCSI on my current FreeBSD system and haven't actually used camcontrol. Read the manpage and be cautious. -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 12:17: 8 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 B8B4A155C1 for ; Sun, 10 Oct 1999 12:16:49 -0700 (PDT) (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 PAA25924 for ; Sun, 10 Oct 1999 15:16:46 -0400 (EDT) Date: Sun, 10 Oct 1999 15:16:43 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: How to prevent a system call from restart? 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 modify the day time client program from the Stevens' book and run it on both a Sun workstation and a FreeBSD machine. In the program, I use signal() and alarm() to set a 5 seconds timeout. The program works as expected on Sun (after I comment out the daytime line in the file /etc/inetd.conf) but not on the FreeBSD machine. Later I find out that the reason maybe the recvfrom() restarts *automatically* in FreeBSD. Why the default behaviour is different from SunOS? If I am correct about the reason, can anyone tell me how to prevent the recvfrom() from restart after receiving the SIGALRM signal? By the way, I also try the socket timeout option. It works immediately. 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 Sun Oct 10 12:55:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 81F6814A2B for ; Sun, 10 Oct 1999 12:55:07 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA24596 for FreeBSD-hackers@freebsd.org; Sun, 10 Oct 1999 21:48:08 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA62231 for FreeBSD-hackers@freebsd.org; Sun, 10 Oct 1999 21:50:54 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910101950.VAA62231@yedi.iaf.nl> Subject: interesting observation ;-) To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Sun, 10 Oct 1999 21:50:54 +0200 (CEST) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.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 FYI: It just took me 2 attempts to realise that the 3.3-R installation on Alpha that gave me ")2: cannot execute" in the latest 'cp' of the kernel was actually installing the *Intel* 3.3-R cdrom. Sysinstall will happily do this for you.. ;-) Problem's been fixed by adding 2 strong espresso's to the brain cells 8) Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Sun Oct 10 13:25:30 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 B8AAB1594B for ; Sun, 10 Oct 1999 13:24:59 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id WAA19670 for ; Sun, 10 Oct 1999 22:24:57 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma019668; Sun, 10 Oct 99 22:24:57 +0200 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 WAA12970 for ; Sun, 10 Oct 1999 22:24:57 +0200 (MET DST) Received: (qmail 42381 invoked by uid 666); 10 Oct 1999 20:25:19 -0000 Date: Sun, 10 Oct 1999 22:25:19 +0200 From: Jos Backus To: freebsd-hackers@freebsd.org Subject: Re: How to prevent a system call from restart? Message-ID: <19991010222519.B42122@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 10, 1999 at 03:16:43PM -0400, Zhihui Zhang wrote: > Later I find out that the reason maybe the recvfrom() restarts > *automatically* in FreeBSD. Maybe because of the following in /usr/src/lib/libc/gen/signal.c? sig_t signal(s, a) int s; sig_t a; [...] if (!sigismember(&_sigintr, s)) sa.sa_flags |= SA_RESTART; ? -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ 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 Oct 10 15:11: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles509.castles.com [208.214.165.73]) by hub.freebsd.org (Postfix) with ESMTP id 4C27815239 for ; Sun, 10 Oct 1999 15:10:57 -0700 (PDT) (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 PAA08093; Sun, 10 Oct 1999 15:02:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910102202.PAA08093@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: James Howard Cc: freebsd-hackers@freebsd.org Subject: Re: KLDs In-reply-to: Your message of "Fri, 08 Oct 1999 19:14:17 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Oct 1999 15:02:09 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Slashdot, in a discussion regarding QNX, someone described it with the > following: > > Under QNX, if your driver crashes, the kernel just restarts it. > > After reading it, I became more interested in KLDs. My only prior > experiece was installing the Linux KLD and that was done by a port. You should note that neither QNX nor FreeBSD exhibit the above behaviour. KLD is a linker; it allows you to link more stuff into the kernel after it's been started. It doesn't implement a coprocess model of any sort. > Anyway, in an effort to learn, I decided to KLD-ify EXT2FS support. It > took about 20 minutes and works great, but I still do not know how KLDs > work. :) I think the general idea is that you're not meant to worry about it. 8) If you're in need of more information, I can really only direct you to the sources. > (I submitted the patch in kern/14217, if someone could look at > it, that would be swell. I've been able to mount, read, write and umount > without any problems) (noted) > Anyway, back to the point, if it is this so simple (is it?), how much of > the kernel can be KLDs? It would be interesting to see a kernel so small > that all it had was KLD support in it and everything else was a module. Indeed it would. There's some fairly strong resistance to this being the _only_ way that FreeBSD works, but the level of modularity you describe is certainly a goal we are working towards. > Has anyone else thought about this? Is this a good idea? Is this a > bad idea? Yes, Yes, Yes. > How fundamentally different would this be from > a microkernel? Very. There is only one protection domain in the FreeBSD kernel, and KLDs live inside it. > Could things be done in such a way that like QNX, it can > kill and restart a misbehaving driver? What other cool things can be > done? QNX doesn't do that. We can't either, unfortunately. The limits on "cool things" are so wide that listing them here would be extremely tiring. 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 Sun Oct 10 15:13:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles509.castles.com [208.214.165.73]) by hub.freebsd.org (Postfix) with ESMTP id 0CA4A150E9 for ; Sun, 10 Oct 1999 15:13:21 -0700 (PDT) (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 PAA08122; Sun, 10 Oct 1999 15:05:26 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910102205.PAA08122@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kevin Vigor Cc: freebsd-hackers@freebsd.org Subject: Re: Hello & boot > cylinder 1024 suggestion In-reply-to: Your message of "Thu, 07 Oct 1999 10:14:46 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Oct 1999 15:05:26 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was recently annoyed to find that I cannot install/boot FreeBSD > from a hard drive partition extending beyond cylinder 1024 (not a > problem unique to FreeBSD by any means...). Even with LBA support, > this translates to an 8-gig limit (i.e. the boot partition must be > completely within the first 8 gigs of the hard drive). Actually, LBA support exists, unfortunately enabling it is still a little bit magic. > So, questions: has anybody thought of this before? I > couldn't find any reference to such a project anywhere, but it seems > relatively obvious. Does this sound like a idea worth pursuing? And > assuming that the previous answers are no and yes respectively, is > there anyone who can/would assist with the install integration/testing > portion of this (I am confident of my ability to code the MBR/BTX > changes, but much less confident of my understanding on the install > process). It's been looked at and basically rejected as "too bloody hard". If you have a convincing argument that this path should be followed over using the BIOS 'packet mode/EDD3' interface, and are willing to put the code together to do it, then we'll certainly look at it and see what can be done to take advantage of it. -- \\ 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 Oct 10 15:59:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 20FCD1512B; Sun, 10 Oct 1999 15:58:00 -0700 (PDT) (envelope-from stuyman@confusion.net) Received: from confusion.net (user-2iveauu.dialup.mindspring.com [165.247.43.222]) by smtp10.atl.mindspring.net (8.8.5/8.8.5) with ESMTP id SAA30789; Sun, 10 Oct 1999 18:57:57 -0400 (EDT) Message-ID: <380119D0.EDE9F379@confusion.net> Date: Sun, 10 Oct 1999 18:57:20 -0400 From: Laurence Berland Organization: B.R.A.T.T. X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Robert Sexton Cc: nsayer@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: CFD: "bogomips" CPU performance metric References: <37CEB68D.848BDAF8@sftw.com> <19990902154111.A15805@tabby.kudra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I like the idea as an optional LINT parameter that is NOT in the generic kernel. Might make some linux people feel comfortable with the switch, or might prove useful under some odd circumstances, but I agree it'd be silly to include it by default (kindof on the level of a splash screen) Robert Sexton wrote: > > On Thu, Sep 02, 1999 at 10:40:30AM -0700, Nick Sayer wrote: > > Linux generates a meric of CPU performance as a byproduct of calibrating > > a delay loop. > > We don't require doing any such thing, and so adding it would be purely > > cosmetic. > > However, I allege that cosmetic things aren't in and of themselves evil, > > so long as > > they don't break anything in the process. > > I'd have to agree with the "Lets be more professional" crowd. > > How about as a LINT option? "If you need something so banal, you can > turn it on yourself" > > -- > Robert Sexton, robert@kudra.com > "Imagine if every Thursday your shoes exploded if you tied them the > usual way. This happens to us all the time with computers, and nobody > thinks of complaining." -- Jeff Raskin, interviewed in Doctor Dobb's Journal > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Laurence Berland, Stuyvesant HS Debate <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. http://stuy.debate.net icq #7434346 aol imer E1101 The above email Copyright (C) 1999 Laurence Berland All rights reserved To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 16:24:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from altair.mayn.de (altair.mayn.de [194.145.150.157]) by hub.freebsd.org (Postfix) with ESMTP id EF9EA15670 for ; Sun, 10 Oct 1999 16:23:36 -0700 (PDT) (envelope-from mkb@altair.mayn.de) Received: (from mkb@localhost) by altair.mayn.de (8.9.3/8.9.3) id BAA01011; Mon, 11 Oct 1999 01:17:51 +0200 (CEST) (envelope-from mkb) Date: Mon, 11 Oct 1999 01:17:50 +0200 From: Matthias Buelow To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How to prevent a system call from restart? Message-ID: <19991011011750.A967@altair.mayn.de> 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 Zhihui Zhang wrote: >I modify the day time client program from the Stevens' book and run it on >both a Sun workstation and a FreeBSD machine. In the program, I use >signal() and alarm() to set a 5 seconds timeout. The program works as >expected on Sun (after I comment out the daytime line in the file >/etc/inetd.conf) but not on the FreeBSD machine. Steven's book (I assume ``Advanced Programming in the Unix Environment'') also tells you about the sigaction() system call. If you use sigaction without SA_RESTART, the signal will not restart slow system calls, causing them to flag EINTR. mkb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 17:57:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from colnta.acns.ab.ca (clgr000532.hs.telusplanet.net [161.184.82.24]) by hub.freebsd.org (Postfix) with ESMTP id AA85E15147 for ; Sun, 10 Oct 1999 17:57:23 -0700 (PDT) (envelope-from davidc@colnta.acns.ab.ca) Received: from localhost (davidc@localhost) by colnta.acns.ab.ca (8.9.3/8.9.3) with ESMTP id AAA00326 for ; Wed, 1 Jan 1997 00:19:46 -0700 (MST) (envelope-from davidc@colnta.acns.ab.ca) Date: Wed, 1 Jan 1997 00:19:46 -0700 (MST) From: Chad David To: freebsd-hackers@freebsd.org Subject: aio_read kills machine 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 am working on a small threaded program that uses aio_read(). In my first attempt to run the program it killed my machine instantly. The second time it only locked it solid. I get no messages, warnings, or errors. I am certain that my program is not correct (besides the obvious consiquence of running it :) ), but I would also like to determine why it kills the machine. I was not root either time I ran the code. I could provide additional debugging information, and the source to anybody who cares about this. I am not sure up front what would be helpful. The machine is a dual 400 with 512Mg ram, running 3.3-stable as of Sept 28 with SMP enabled. Thanks in advance. Chad davidc@acns.ab.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 18: 0: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mta1.rcsntx.swbell.net (mta1.rcsntx.swbell.net [151.164.30.25]) by hub.freebsd.org (Postfix) with ESMTP id 5C49715644; Sun, 10 Oct 1999 17:59:48 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta1.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FJE00DEHYRFMG@mta1.rcsntx.swbell.net>; Sun, 10 Oct 1999 19:59:41 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id TAA18145; Sun, 10 Oct 1999 19:58:55 -0500 (CDT envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Sun, 10 Oct 1999 19:58:55 -0500 From: Chris Costello Subject: Re: CFD: "bogomips" CPU performance metric In-reply-to: <380119D0.EDE9F379@confusion.net> To: Laurence Berland Cc: Robert Sexton , nsayer@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991010195854.C15135@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <37CEB68D.848BDAF8@sftw.com> <19990902154111.A15805@tabby.kudra.com> <380119D0.EDE9F379@confusion.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 10, 1999, Laurence Berland wrote: > I like the idea as an optional LINT parameter that is NOT in the generic > kernel. Might make some linux people feel comfortable with the switch, > or might prove useful under some odd circumstances, but I agree it'd be > silly to include it by default (kindof on the level of a splash screen) I disagree. BogoMIPS is a completely meaningless measurement and does not belong in our source tree as it will only produce repository bloat. -- |Chris Costello |A bug in the code is worth two in the documentation. `---------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 18:37:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 41A2D14E62 for ; Sun, 10 Oct 1999 18:37:09 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA23665; Mon, 11 Oct 1999 11:06:56 +0930 (CST) Date: Mon, 11 Oct 1999 11:06:56 +0930 From: Greg Lehey To: Narvi Cc: hackers@FreeBSD.ORG Subject: Re: Fun with vinum Message-ID: <19991011110656.O78191@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 10 October 1999 at 19:33:44 +0300, Narvi wrote: > > Should you decide to use vinum keep in mind that you: > > a) reboot to make sure that whatever you just set up can > automatically start itself This is always a good idea. You don't have to do it immediately, of course. > b) alternatively > vinum l > vinum makedev > vinum create -f configfile > vinum start > is your friend and avoids most of the problem I don't understand why you would want to do this. You certainly don't want vinum create followed by vinum start. > IMHO it should not panick the kernel when it doesn't like the disk > setup. IMO it shouldn't panic. Could it be there's more to this message than you're divulging? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 18:43:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mta2.rcsntx.swbell.net (mta2.rcsntx.swbell.net [151.164.30.26]) by hub.freebsd.org (Postfix) with ESMTP id CC14A156AD for ; Sun, 10 Oct 1999 18:43:39 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta2.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FJF00D6R0SN4Q@mta2.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Sun, 10 Oct 1999 20:43:36 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id UAA18430; Sun, 10 Oct 1999 20:42:52 -0500 (CDT envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Sun, 10 Oct 1999 20:42:52 -0500 From: Chris Costello Subject: Re: aio_read kills machine In-reply-to: To: Chad David Cc: freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991010204252.D15135@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 01, 1997, Chad David wrote: > I am certain that my program is not correct > (besides the obvious consiquence of running > it :) ), but I would also like to determine > why it kills the machine. I was not root > either time I ran the code. Then FreeBSD does have a problem. Please file a PR using the ``send-pr'' command or http://www.freebsd.org/send-pr.html and supply the source to your program and whatever other information you think will help us in figuring out the problem. -- |Chris Costello |Field tested: Manufacturing doesn't have a test system. `------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 19: 6: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from vitoria.ddsecurity.com.br (vitoria.ddsecurity.com.br [200.18.130.93]) by hub.freebsd.org (Postfix) with SMTP id 2082E14D00 for ; Sun, 10 Oct 1999 19:06:00 -0700 (PDT) (envelope-from grios@ddsecurity.com.br) Received: (qmail 31079 invoked from network); 11 Oct 1999 03:05:50 -0000 Received: from unknown (HELO ddsecurity.com.br) (200.236.148.114) by vitoria.ddsecurity.com.br with SMTP; 11 Oct 1999 03:05:50 -0000 Message-ID: <380145BD.A4C04C01@ddsecurity.com.br> Date: Mon, 11 Oct 1999 00:04:45 -0200 From: Gustavo V G C Rios X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: file system system calls Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG May anyone here point me where in the source tree i can see file system API implemented, like open, write, close, etc..... Thanks a lot. -- "Security is not a state, but a process." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 19:21:22 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 18C6914C2A for ; Sun, 10 Oct 1999 19:21:14 -0700 (PDT) (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 UAA09273; Sun, 10 Oct 1999 20:21:11 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id UAA12619; Sun, 10 Oct 1999 20:21:09 -0600 Date: Sun, 10 Oct 1999 20:21:09 -0600 Message-Id: <199910110221.UAA12619@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: James Howard , freebsd-hackers@FreeBSD.ORG Subject: Re: KLDs In-Reply-To: <199910102202.PAA08093@dingo.cdrom.com> References: <199910102202.PAA08093@dingo.cdrom.com> 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 > > Could things be done in such a way that like QNX, it can > > kill and restart a misbehaving driver? What other cool things can be > > done? > > QNX doesn't do that. Actually, in many cases it does. There are numerous advantages in a well-designed/optimized micro-kernel that FreeBSD will never have. [ However, as has been shown by the plethora of poor micro-kernel implementations (QNX not withstanding), it's hard to implement a well-designed/optimized micro-kernel, especially one that is not architecture dependant. ] Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 20: 2:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.atl.bellsouth.net (mail1.atl.bellsouth.net [205.152.0.28]) by hub.freebsd.org (Postfix) with ESMTP id 32B8014C02 for ; Sun, 10 Oct 1999 20:02:45 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-216-78-37-222.ath.bellsouth.net [216.78.37.222]) by mail1.atl.bellsouth.net (3.3.4alt/0.75.2) with ESMTP id WAA14390; Sun, 10 Oct 1999 22:58:11 -0400 (EDT) Received: from wghicks.bellsouth.net (IDENT:wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id XAA47903; Sun, 10 Oct 1999 23:08:19 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199910110308.XAA47903@bellsouth.net> To: nate@mt.sri.com (Nate Williams) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: KLDs In-reply-to: Your message of "Sun, 10 Oct 1999 20:21:09 MDT." <199910110221.UAA12619@mt.sri.com> Date: Sun, 10 Oct 1999 23:08:19 -0400 From: W Gerald Hicks Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Could things be done in such a way that like QNX, it can > > kill and restart a misbehaving driver? What other cool things can be > > done? > > QNX doesn't do that. > Actually, in many cases it does. There are numerous advantages in a > well-designed/optimized micro-kernel that FreeBSD will never have. Well, the implication was that QNX implements this as a kernel policy and that it's done automatically. A handful of drivers can be stopped and restarted, notably the network devices. The QNX filesystem resource managers and disk device drivers are notoriously finicky and aren't restartable in the general sense. Still, I like QNX a lot and have a major telecomm app widely deployed on it, going on five years in the field now. > However, as has been shown by the plethora of poor micro-kernel > implementations (QNX not withstanding), it's hard to implement a > well-designed/optimized micro-kernel, especially one that is not > architecture dependent. Amen! :-) Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 20:15:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 2A09214DB7 for ; Sun, 10 Oct 1999 20:15:25 -0700 (PDT) (envelope-from howardjp@wam.umd.edu) Received: from rac3.wam.umd.edu (root@rac3.wam.umd.edu [128.8.10.143]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id XAA08264; Sun, 10 Oct 1999 23:15:11 -0400 (EDT) Received: from rac3.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id XAA20565; Sun, 10 Oct 1999 23:15:15 -0400 (EDT) Received: from localhost (howardjp@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA20561; Sun, 10 Oct 1999 23:15:15 -0400 (EDT) X-Authentication-Warning: rac3.wam.umd.edu: howardjp owned process doing -bs Date: Sun, 10 Oct 1999 23:15:15 -0400 (EDT) From: James Howard To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: KLDs In-Reply-To: <199910102202.PAA08093@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 Sun, 10 Oct 1999, Mike Smith wrote: > You should note that neither QNX nor FreeBSD exhibit the above > behaviour. KLD is a linker; it allows you to link more stuff into the > kernel after it's been started. It doesn't implement a coprocess model > of any sort. Yes, I knew this for FreeBSD, and for QNX, well, Slashdot again proves to be totally unreliable. :) > Indeed it would. There's some fairly strong resistance to this being > the _only_ way that FreeBSD works, but the level of modularity you I don't think this is a good idea but it would certainly be a swank thing to see. Is it possible to compile a kernel with no filesystems supported and have the boot loader load FFS? I have built an FFS module but I have not yet had time to test it. Frankly, I am kind of afraid to for fear of trashing my system. > > Has anyone else thought about this? Is this a good idea? Is this a > > bad idea? > > Yes, Yes, Yes. Could you claify this? :) Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 21: 3:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ple.org (c431822-a.smateo1.sfba.home.com [24.7.95.203]) by hub.freebsd.org (Postfix) with ESMTP id 8007514E74 for ; Sun, 10 Oct 1999 21:02:38 -0700 (PDT) (envelope-from andy@ple.org) Received: from k1825dsf (k1825dsf [10.2.4.235]) by ple.org (8.9.3/8.9.3) with SMTP id VAA39455 for ; Sun, 10 Oct 1999 21:02:15 -0700 (PDT) Message-ID: <001501bf139c$b8c509d0$eb04020a@nt.schwab.com> From: "Andreas Pleschutznig" To: Subject: Multipath routing Date: Sun, 10 Oct 1999 20:57:22 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0012_01BF1362.0C30C9F0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0012_01BF1362.0C30C9F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi everyone, good morning ;-) Can anone shed some light on multipath routing for me? Is it already = implemented in 3.[23] And if yes where can I find documentation, if not = what do I have to do in order to get it up and running? Thanks Andreas ------=_NextPart_000_0012_01BF1362.0C30C9F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi everyone, good morning ;-)
 
Can anone shed some light on multipath routing for me? Is it = already=20 implemented in 3.[23] And if yes where can I find documentation, if not = what do=20 I have to do in order to get it up and running?
 
Thanks

Andreas
------=_NextPart_000_0012_01BF1362.0C30C9F0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 21:14:57 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 891AA14E74 for ; Sun, 10 Oct 1999 21:14:55 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id VAA25590; Sun, 10 Oct 1999 21:34:27 -0700 (PDT) Date: Sun, 10 Oct 1999 21:34:27 -0700 (PDT) From: Alfred Perlstein To: Gustavo V G C Rios Cc: hackers@FreeBSD.ORG Subject: Re: file system system calls In-Reply-To: <380145BD.A4C04C01@ddsecurity.com.br> 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, 11 Oct 1999, Gustavo V G C Rios wrote: > May anyone here point me where in the source tree i can see file system > API implemented, like open, write, close, etc..... src/sys/kern/vfs_syscalls.c because freebsd follows (for the most part) style(9) you can usually find where a function is implemented by just going to the sys source directory and doing a simple: grep ^somefuncname */* this is because the concention is to write functions like so: int somefunctioname(foo) { -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 21:16:27 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 E384514E74 for ; Sun, 10 Oct 1999 21:16:25 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id VAA25690; Sun, 10 Oct 1999 21:36:05 -0700 (PDT) Date: Sun, 10 Oct 1999 21:36:05 -0700 (PDT) From: Alfred Perlstein To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How to prevent a system call from restart? 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 Sun, 10 Oct 1999, Zhihui Zhang wrote: > > I modify the day time client program from the Stevens' book and run it on > both a Sun workstation and a FreeBSD machine. In the program, I use > signal() and alarm() to set a 5 seconds timeout. The program works as > expected on Sun (after I comment out the daytime line in the file > /etc/inetd.conf) but not on the FreeBSD machine. > > Later I find out that the reason maybe the recvfrom() restarts > *automatically* in FreeBSD. Why the default behaviour is different from > SunOS? If I am correct about the reason, can anyone tell me how to prevent > the recvfrom() from restart after receiving the SIGALRM signal? > > By the way, I also try the socket timeout option. It works immediately. > > Any help is appreciated. from sigaction's manpage: If a signal is caught during the system calls listed below, the call may be forced to terminate with the error EINTR, the call may return with a data transfer shorter than requested, or the call may be restarted. Restart of pending calls is requested by setting the SA_RESTART bit in sa_flags. The affected system calls include open(2), read(2), write(2), sendto(2), recvfrom(2), sendmsg(2) and recvmsg(2) on a communications channel or a slow device (such as a terminal, but not a regular file) and during a wait(2) or ioctl(2). However, calls that have already committed are not restarted, but instead return a partial success (for example, a short read count). you want to turn off SA_RESTART. -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [bright@wintelcom.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 21:17: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 47BD415249 for ; Sun, 10 Oct 1999 21:16:58 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FJF00HXT7W2ML@mta4.rcsntx.swbell.net> for hackers@FreeBSD.ORG; Sun, 10 Oct 1999 23:16:51 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id XAA19149; Sun, 10 Oct 1999 23:16:06 -0500 (CDT envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Sun, 10 Oct 1999 23:16:04 -0500 From: Chris Costello Subject: Re: file system system calls In-reply-to: To: Alfred Perlstein Cc: Gustavo V G C Rios , hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991010231604.A19110@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <380145BD.A4C04C01@ddsecurity.com.br> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 10, 1999, Alfred Perlstein wrote: > grep ^somefuncname */* > > this is because the concention is to write functions like so: > > int > somefunctioname(foo) { You mean int somefuncname(char *foo) { -- |Chris Costello |Death is a nonmaskable interrupt. `---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 23: 7:21 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 7639114E26 for ; Sun, 10 Oct 1999 23:07:14 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id XAA28589; Sun, 10 Oct 1999 23:26:48 -0700 (PDT) Date: Sun, 10 Oct 1999 23:26:47 -0700 (PDT) From: Alfred Perlstein To: Chris Costello Cc: Gustavo V G C Rios , hackers@FreeBSD.ORG Subject: Re: file system system calls In-Reply-To: <19991010231604.A19110@holly.calldei.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, 10 Oct 1999, Chris Costello wrote: > On Sun, Oct 10, 1999, Alfred Perlstein wrote: > > grep ^somefuncname */* > > > > this is because the concention is to write functions like so: > > > > int > > somefunctioname(foo) { > > You mean > > int > somefuncname(char *foo) > { err, yes. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 10 23:46:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id B5F0714BB8 for ; Sun, 10 Oct 1999 23:46:18 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id JAA14908; Mon, 11 Oct 1999 09:46:08 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Date: Mon, 11 Oct 1999 09:46:08 +0300 (EEST) From: Narvi To: Greg Lehey Cc: hackers@FreeBSD.ORG Subject: Re: Fun with vinum In-Reply-To: <19991011110656.O78191@freebie.lemis.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, 11 Oct 1999, Greg Lehey wrote: > On Sunday, 10 October 1999 at 19:33:44 +0300, Narvi wrote: > > > > Should you decide to use vinum keep in mind that you: > > > > a) reboot to make sure that whatever you just set up can > > automatically start itself > > This is always a good idea. You don't have to do it immediately, of > course. > > > b) alternatively > > vinum l > > vinum makedev > > vinum create -f configfile > > vinum start > > is your friend and avoids most of the problem > > I don't understand why you would want to do this. You certainly don't > want vinum create followed by vinum start. > Well, maybe 'vinum start' is not needed. vinum l -> load vinum, but not teh disk conf vinum makedev -> clean the /dev/vinum directory vinum create ... -> tell vinum what the setup is. > > IMHO it should not panick the kernel when it doesn't like the disk > > setup. > > IMO it shouldn't panic. Could it be there's more to this message than > you're divulging? > Well, that happens if you post too late. The problem is (see a)) that it does not automatically start, or rather, it tries but immediately panicks. And vinum read panicks the system, as does vinum start. The system is 3.3-STABLE, less than a week old. > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 0:22:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id C6F2814DB7 for ; Mon, 11 Oct 1999 00:22:48 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id QAA25641; Mon, 11 Oct 1999 16:52:39 +0930 (CST) Date: Mon, 11 Oct 1999 16:52:39 +0930 From: Greg Lehey To: Narvi Cc: hackers@FreeBSD.ORG Subject: Re: Fun with vinum Message-ID: <19991011165239.A78191@freebie.lemis.com> References: <19991011110656.O78191@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 11 October 1999 at 9:46:08 +0300, Narvi wrote: > > On Mon, 11 Oct 1999, Greg Lehey wrote: > >> On Sunday, 10 October 1999 at 19:33:44 +0300, Narvi wrote: >>> >>> Should you decide to use vinum keep in mind that you: >>> >>> a) reboot to make sure that whatever you just set up can >>> automatically start itself >> >> This is always a good idea. You don't have to do it immediately, of >> course. >> >>> b) alternatively >>> vinum l >>> vinum makedev >>> vinum create -f configfile >>> vinum start >>> is your friend and avoids most of the problem >> >> I don't understand why you would want to do this. You certainly don't >> want vinum create followed by vinum start. > > Well, maybe 'vinum start' is not needed. In fact, *only* 'vinum start' is needed. From vinum(8): start [-w] [volume | plex | subdisk] start starts (brings into to the up state) one or more vinum ob- jects. If no object names are specified, vinum scans the disks known to the system for vinum drives and then reads in the configuration as described under the read commands. The vinum drive contains a header with all information about the data stored on the drive, including the names of the other drives which are required in or- der to represent plexes and volumes. > vinum l -> load vinum, but not teh disk conf No. From vinum(8): list [-r] [-V] [volume | plex | subdisk] l [-r] [-V] [volume | plex | subdisk] list is used to show information about the specified object. If the argument is omitted, information is shown about all objects known to vinum. The l command is a synonym for list. > vinum makedev -> clean the /dev/vinum directory In emergencies. From vinum(8): makedev The makedev command removes the directory /dev/vinum and recre- ates it with device nodes which reflect the current configura- tion. This command is not intended for general use, and is pro- vided for emergency use only. > vinum create ... -> tell vinum what the setup is. Well, create new objects. From vinum(8): create [-f description-file] vinum create is used to create any object. ... Note that the vinum create function is additive: if you run it multiple times, you will create multiple copies of all unnamed objects. >>> IMHO it should not panick the kernel when it doesn't like the disk >>> setup. >> >> IMO it shouldn't panic. Could it be there's more to this message than >> you're divulging? > > Well, that happens if you post too late. The problem is (see a)) that it > does not automatically start, or rather, it tries but immediately > panicks. And vinum read panicks the system, as does vinum start. vinum(4) contains information about how to handle panics in vinum. So does http://www.lemis.com/vinum/how-to-debug.html. If you're having that kind of problem, I want to know about it. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 1:59:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id 96C0814D32 for ; Mon, 11 Oct 1999 01:56:53 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id LAA41874; Mon, 11 Oct 1999 11:55:06 +0300 (EEST) (envelope-from ru) Date: Mon, 11 Oct 1999 11:55:06 +0300 From: Ruslan Ermilov To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.org Subject: Re: How to prevent a system call from restart? Message-ID: <19991011115506.A34243@relay.ucb.crimea.ua> Mail-Followup-To: Zhihui Zhang , freebsd-hackers@FreeBSD.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Zhihui Zhang on Sun, Oct 10, 1999 at 03:16:43PM -0400 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 10, 1999 at 03:16:43PM -0400, Zhihui Zhang wrote: > > I modify the day time client program from the Stevens' book and run it on > both a Sun workstation and a FreeBSD machine. In the program, I use > signal() and alarm() to set a 5 seconds timeout. The program works as > expected on Sun (after I comment out the daytime line in the file > /etc/inetd.conf) but not on the FreeBSD machine. > > Later I find out that the reason maybe the recvfrom() restarts > *automatically* in FreeBSD. Why the default behaviour is different from > SunOS? If I am correct about the reason, can anyone tell me how to prevent > the recvfrom() from restart after receiving the SIGALRM signal? > > By the way, I also try the socket timeout option. It works immediately. > > Any help is appreciated. > Refer to the siginterrupt(3) manpage, it has all info you are looking for. Cheers, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 2: 5:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.10]) by hub.freebsd.org (Postfix) with ESMTP id DD81714D32 for ; Mon, 11 Oct 1999 02:04:59 -0700 (PDT) (envelope-from rbezuide@oskar.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.nanoteq.co.za (8.9.0/8.9.0) id LAA26466 for freebsd-hackers@freebsd.org; Mon, 11 Oct 1999 11:08:08 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199910110908.LAA26466@oskar.nanoteq.co.za> Subject: More libpcap problems To: freebsd-hackers@freebsd.org Date: Mon, 11 Oct 1999 11:08:08 +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 have an application which uses libpcap ... after running for several weeks normally .. the application coredumps .. I've traced the problem back to libpcap which somehow reads garbage packet information (or is given garbage). Here is a short view of the gdb .. (gdb) p *(struct bpf_hdr *)pkt $2 = {bh_tstamp = {tv_sec = 0, tv_usec = 0}, bh_caplen = 0, bh_datalen = 4294922246, bh_hdrlen = 24577} (gdb) p *pkt $3 = {ts = {tv_sec = 0, tv_usec = 0}, caplen = 0, len = 4294922246} (gdb) Take a look at the bh_datalen and bh_hdrlen ... those values are not ok. The only value which makes sense is the bh_caplen. Should I use that to determine if I should try and examine the packet ??? I've already had to make a change to libpcap where it got stuck in and endless loop after receiving such "bad" data. (It has been submitted in a PR) Thanks Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 2:12:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay1.bcs.zp.ua (bcs-zyx-eth.marka.net.ua [195.248.171.202]) by hub.freebsd.org (Postfix) with ESMTP id B614114D32 for ; Mon, 11 Oct 1999 02:07:29 -0700 (PDT) (envelope-from serg@bcs3.bcs.zp.ua) Received: from bcs3.bcs.zp.ua (bcs3.bcs.zp.ua [212.8.35.73]) by relay1.bcs.zp.ua (8.9.3/8.9.3) with ESMTP id LAA16050 for ; Mon, 11 Oct 1999 11:43:38 +0300 (EEST) Received: (from serg@localhost) by bcs3.bcs.zp.ua (8.8.8/8.8.8) id LAA02664 for hackers@freebsd.org; Mon, 11 Oct 1999 11:43:38 +0300 (EEST) (envelope-from serg) From: Sergey Shkonda Message-Id: <199910110843.LAA02664@bcs3.bcs.zp.ua> Subject: Ukrainian locale & co To: hackers@freebsd.org Date: Mon, 11 Oct 1999 11:43:38 +0300 (EEST) X-Mailer: ELM [version 2.4ME+ PL61 (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 There is a ukrainian locale sources. Can someone commit it ? -- Sergey Shkonda begin 644 ukrainian_locale.tgz M'XL(`*N@`3@``^Q<6W,41Y;V*^=7E,&:!H\1=;_0C=A&$D@@)(UN-HQF/%7= M5:A12ZWIBT#,Y;?8C/%ZQP'\A;77Q(1W'`8#LVSL@\,P$>N7C?6C7_=S"^S\IS*.E])HM6H#T:5U1.O[>.AV;KG.-IK&AUZ!ZH+ MS=-UW3),SW`TS=`=RWY-<_9S4NG1:C3#NJ:]5J_5FCNUN[84Q]6#F-#!'BWE M_Y7E:JT45N/]"(0]^-_P=/*_:9E&W_\'<73YOQPVPY<'6S42S]T#$/77=O>UO^FI]N;S[]C MN^A_UW7TUS3]9=[H=L<_N/]/O`G:F]K$U'!Q8O1=]K26U.K:_'(]K*Q6PE5M MN5;QC[>TTE)8#TO-N*XUXJ9V=.;LL&D9P3'L?`)&)X>G1L8GSQTZ/#DU.7H8 M%HHSX\4S$Z/IT[TS&<`1.*+-+54:&OX_U$JUE95XM8FUQ8GIL>*A0[EB3CNN MY2[GM%S(9S=RFGX]M+"(J"CI6*E?3Q(8GIJS;.7AH4^%2X5%1 MWII+.8'I^EIGLGF@J@5B&@F$7)5W^.:W-MO-14C7,\$SH3R;@S,3Q'1XO3N#9]!B&`]?" MQ>(T+Z.:PJ'"UCV-:KW>7+B-W*7-MN7>7+B-UV70NK@T%7;MU,PBS5HZ=WLM? MS/5JD5W^'BVT32]$UI;QT.;R9VNS77BA([NC2U=MM@LO=.1V=.FJS7;AA8Z\ MCBY=M=DNO-!1N:-+S]KVY8_U=FO[\I-U;BK[".+:;CZ!V**'.7T8T6STLF\^ MMF)_D?U_I_?_\+3ONOO__L>WOI')_TQ^_^M.__U_$,)006]JQ.'"D]F]W*3!&C;T]H6:BNWX=D076)209E#0IE# MXK]8HO#CRA$R&[N:@B_;<:CW;!1LKDYF1^]LA,O&KNS]HM[T_`[#;(7$3L,8 MGMN,'OJ`W2VA]Q$M(_7MF1YG^E6K5:CI-]^3G`GK[_._3]SS1LM__][R". M3O_OP^??O?C?LBR;OO_J3O_[[X$A&\SEB"UX\18KO3A#&,T'J@ZEQ:0O1U6%\G-*!<)S2A7"6TH,77 M-K3XVH%UOG9AG:\]*'-_'UJ,`:PSAC!']^U',,%8@K.,9:@RQC##F,`@W7>@ MPTE&`TXSFC#>(K0@X6L;&K0>@0,S-._`A=/DE\"#4P5"'X9.$08PR>U#&*?Y M!1&,G",L@/]L#F*?U"4.8Y^L(6A1/80GF:3YA&:XP7PSK;$]@@=I' M.#Y=1P:L4_L([Y_\'EEP:930A@6N=V"MC.,7]$CA/ M^TVL0Y'ZQ0:<831AF!&?/T;<;Q@=.,OHPCE&#\88?1AG#.`\8P@7&#'^&4MP MD;$,DXPQ3#$F,$V8Z'"^2&C`#%^;,,MHP1RC#?.,#ERF^2_X9G6QWO?]?U^M]_#^0XDOY,]F@4EI:OA?4R?7A="YN5J!IKURK-):TX M.SP^?HR_SKXQ7CZIM44'1L4;:*)ON9@U:EN9(]3JY1@W6^Q5JJTVZ[5J`PX5 M)N>'\H.#@_G"_.Q0'FU4A6>%V>FA_.OYQM[('S7?*IBS0\?R%@\1"/_) M_&(^OUC(%TX5AO*G\H430Z>&\D/YT_G"<`U'*C9Y'EHI7*LTPRH<*G+GRS1\ MH8A-"V>H6*#B'!>C-#\Z&Z7B$EV.XW0+EP>H.,43+XR3;7R<&E!QGBXO4#%! MQ44J)JF8HF*:BAG56:)W':`'6R=\+=.]U*F:(8T9:E:ODPA&: M,ME:9)NGLWG5H$4-6A-40V?K9%NG5@MTMJ!:K;.-6BU04::Q1\84`UVT:"+S M=#;/4Z*S=3I;6))6P_D.]P/H/]0/K/]0)K/\POV;]5U;Z#_-QUG^8A[/^PSR<]5^D]%^D M]!_J']9]F*>RWL,\EG4=YJNLXQ*EXS#/9?V&NH+U&^H>UF^H$UB_83[->BM1 M.BY1^@WS9M9OF"^/U$5/L+Y#_5)FG>7#"-^?TG>HHUC?H0YA?8>ZA/4=ZA[6 M=ZBG6-^AOIKGZY+H.]1)K.]0)[&^0QVTGNJX*)TG>8 MUR\PKZOT'\Z/[A=UT@BM,^HDUG^HLUC_H9YB_8=ZBO4?ZC#6?ZB/6/^A7EK@ M>J7_4!>P_D,]POH/=3#K/]3!):5S6/^%2O^%2O^A'F+]A_IX2>DBUG^H@UG_ MH0YF_8:R@]UE1ZK*7T M&.N_4.D_U.FL_U!?;2B]Q?H/=3GK/]1EK/]0=['^0WW&^@]U&^L_U&FL_X)8 M])^OB_[S#=%_@2OZSU?ZSU?Z+[!%__F6Z+_`$?WG^Z+__$#TGQ^*_O,CT7]^ M2?2?7Q;]Y\>B__Q$]%^0B/X+=-%_@2'Z+S!%_P66Z#]?Z3_?%/T7E$3_!9'H M/]\3_1?XHO^"LNB_(!#]1]]-N%_X_TG_I;_^L__Z3_#L=#7RF]^6/OC+''G[^Z[K\^Y^ZZ3C]G_\> MQ"'^;U96XOWZ[8\]^=]&SZ/_Z0-PW_\'<;3[?S]^^V-OS[]CT_EO]MDW[_R[$LHY__'\1!/]5YNS@S.3YY[J366`M+ M<0/S^PTMBK6XT8A7FY6PJH5-K;F$%:MEK99HUZ]]F'7WP%#^[SR?V_PI,/GSR^_Q!/ M<$;W/J.;?TSW_"#WU>,O/_\WG.C?/KW_^!-F?.?=9(7^%&)@[.3`Q9,#LUQY M/:TL#PZL#`YL<&4IK0RU@5@;B+2!=[2!2VP*5[`XVKQ64XX^!IK,=PT-\.`! MG^,6$'=17&*6RQTND#O3*JM:F/FSCJ167Q&OW/OR/\DMG_^[>(4NR2V$Y!=" M<@PW^_P!`;F&D'U#)^0.2Y=?M_B.JC?R&R6_],E\CXC!!9;Q(B,R.R$^``C#C(K:=T@B,]$_O3 M9W?NOOR0$]S^0(.[MS6X^4R#I]]H\"WB73I_?Z>X=/[OP9;GY_\]F=;_`$)W7K`UJ$9W3O=W/?/;O]T7]_!T___OZ=9^\=5$YP M]^[S_S]US;[ M_C^0H[?_6\OUP=(:_5[@X')4?M$Q=L[_+,\R4?^[GN?BJ6Z1_UW#Z/_]_X$< M1[0?>N`[GW[ML!2N;M.@M-JL5]O:;X'8JK72,O_J:#G6M"AL8*DUEBI)<[.S MNE)]>]G0?E,"@ZZ5_L(CC:BT+93F]/0=%)__07P;%> M%/KV2ZTH.#J/2[-WI9FLE8*=;(J"H_.4-/MYKUGL8%,4%)V1D"HHQ]4,[&13 M%!2=2TUIU@RCKI%494^;HN#H_*U,]A<,Y9*1`<,-&.BS1J=-&V8*CLYK0O$V M0]R,,F!:.E,X>K=-47!TQD(Q*A2KO\V`:?+PANUUVQ0%1V==*&;4C9@9,#R9 MA>5WVX3"Y.AL"L6)3=B=-L4!4=G M2RCF)7S"Y0P8KE!81K=-47!T5H1BG$%%B0+3DB5QS&Z;HN"]LR844PR-BI8! M4Q;!<*QNFZ+@O7--**9E.:MQ!@Q7G&HYW39%P='Y2Z'XG2QGV\O'-"4Z[:#; M)@'.@9/[E5#\@>&*/%$*3$M\ZS"8PF3:?H:"SDMUKE"P6LW"3C9%0:S5$K_V M]PQ"P0\1_:.%FOR[J+344HSC%$:M,4,#RY$=OJMBD*CLXEH1@3BK8-US0E+FR[VZ8H.#JO"L7Y7+?O M#4]1F-TV1<'1N2P4%QC69:D4&)[LPE;0;5,4O'=6A6*"(4FT#!BNS$*>^7:; MHN"],[]]&F*XKE#8W3:)3INC,]>6DK4U,^4%8C@JIE2$V1D*CL[?",4?>[U3 M=[`I"KK%JN35>P9%P=&Y*"/]7I93G*Y@)YNBX.B\(7+7A>(=!J53%)BR^QN.T6U3%!R=):$85J_EZQDP3?6,.-TV1<'1N2X4 M"W(C&ZL9,#QYV-G['39%P=$9"<49H9`A%!BN[%K\,'78%`5'YZI03*J-3\N` M:4ITRC[5;A,*SCQR*T)Q49:S;<\V97C#<;MMBH*C4Q+L7*'G,R(>D3=2K^CD MMZU*L'-#/9\160O'WY:"H_/$]DGR3C9%0=%9EY#?,R@*CLXWVY1`V^:VDTU1 MT$)711;O&10%1ZJ:#1:JQM72D*6NB05#QZ>Z^@*,C=R7*\@;*9 M`)4!`3Y;!+CI-4IU4M0(AD#F2BCX=<<4IE#80N$*A<^=3.DDD+E2%$9*(<,; M,CPF/TP1<"=+.EG2,M#3*T5AIA0RO"'#XTN8P.;6I*BIDZTHC/1*45@IA0QO MR/#X1#`%MR9%39T<16&F5XK"3BED>$.&QVR"*;@U*6KJ))"Y4A1.2B'#&S*\ M)?[!_9TZ>5IO4!1N2B'#FS*\)?[!_9U:^UIO4!1>2B'#FS*\)?[!/9=:!UIO M4!2^HC!D>%.&M\0_N-O1;>M:;U`4`3]X'*][!J%@V=20FCV#HDBC$[?R]#O# MKD&;9(HT.G$K3[\S[!H411J=N)6GWQEV#8HBC4[C M78.B2*,3M_+TX]&N05&DT8E;>?KQ:->@*-+HQ*U;8/2B*=._$K3S](KAK M$`H_W3MQ*T^_".X:%$4:G;B5IU\$=PV*(HU.W,K3[T^[!D5!T:F^[J0YP@X0 MU5A2*5`4%)WJ;;9GD"?5I^A\L<_'OOOB%&ET&K)IFK)I6O)6L;W,R[0;%,7F MWBF;IOE_[5UM<]O(D<[7\%<(@@Q*-D0(E$0!ADR"HDUIO:0(FK8$FA"`W%YR ME;K*)I5-JN[GW_1TSPM`&J8`E[/)8FPM3!#3F.GIZ9EY^E$O.LUS7%4N/&TQ MW;Z0"+#.9L=^'ZSS[WB*?_:%1/!])^WJGGLA$="EGW_A[20]%T'[KX^(#];Y MES_^XP]U+B1"^,X+7[\,_!TWMRXD0OK.,_UR=;;CYM:%1$C?Z>J7*W?'S:T+ MB9"^\UR_7)WON+EU(1'2=U[JEZO+'3>W+B1"\YW:Y>IJQ\VM"Q?AGFF^4[M< M>3MN;EU(A.8[M!*RXEWXDB MP#H;[7+<,V&=@_[S+R1"6.?@_/D7$B&L;6V6]NG?WFUMEO;IW]YM;9 M;VZ=_>;6V6]NG?V&UFEV1-2B83O`/I_-P-##7AA^:<3`P/AB%#9A8HHIE4<7.(!$<\:Q@652Q,T@$Q^,K6!95[`P2P1'/ M"I9%%3N#1'`\OH)E4<7.(!$<' MU2R+*G8&B0#55K$LJM@9)`*M4V=9%!D8179&B8&!(L`Z&T$Q&'=NQ,#`L%P5 MRZ**G4$=\0_*+(LB`Z/(SMC!P$!R1!7+HHJ=02+<@VJ6114[@T3`^ZM8%E7L M#!)Q?E#-LJAB9Y`([CLK6!95[`P2<7E0S;*H8F>0B,%!-P+*K8&2B"1XNJ6!95QD\B=#R^%@/#Y=&B M1@P,ET>+&C$P7!XM:L3`<'FT:'\&1I&(02+`%!HQ,%P9+:K-P'!EM*@V`\/U M)`^D+@/#Y=$B+J(N`\/U)0^D+@/#]24/I"X#P_4E#Z0N`\.5T:+:#`Q71HMJ M,S!<&2VJS;2H$0/#Y=&B9K$)&2VJS<#HJVA1709&7T6+ZC(P^C):5)N! MT3^3/)"Z#(S^F>2!U&5@]&6TJ#8#HR^C1;49&'T9+:K-P.B?R5AF709&_TS& M,NLR,/JNL,[:#(P^7PX:,3#Z?#EHQ,#H-X\6]9M'B_JNL,[:#(R^*WUG709& MGT>+&AW[^SQ:U(B!T9LC]:I=G,#`0+"7?J5V>PNW^1^^1VGS/[3Y'[:^(Q%M_@#AG(LZVO]LW_P-?[P33HE[^AS[:!4;C!5N"!UB$ MB'^/_`^($PL>4+W\#R[Q#3!R2O%H3YLC7\W_@-"18"[4R__@8V,P^GO^AC^I$,I1@2_"`K!#QV\G_<$84)W?[NWWS/_1Q44,^5;W\#RYZ M<&3OU,K_@%$,P3JIE?\!@T*"Z%8O_X.+ND`J2[W\#R[.$61UU(-O^#$M'F?VCS/[3Y'ZK8!VW^!UU$F_]!B6CS/R@1;?Z' M-O]#F__ARR-B?IO\#R"B$8&A32'1II`H74C$MT@A\?M?00*)W].,X>^IDSZB M(*!.\HB"@#9U1",1;>H():)-'2%%M*DC-!'-K;--'5%H1YLZ0HEH4T MJ2.J"!K[IHZH(&CLF3JBBJ"Q;^J(`D&C)*)`["B1-_X34T=4$#3V31U10=#8 M-W5$!4%CS]01502-/5-'5!$T]DT=44'0V#=U1`5!8]_4$14$C3U31U01--K4 M$?M=2$2;.J)-'=&FCJ@B;[2I(W01;>H():)-':%$M*DCVM01;>J(RA%I4T>T MJ2.*%Q+Q*TD=T8QY\6T21S1C7O3/+YHQ+_KGETV8%__J7\+_%Y9B_H<__?7G M?_SB?.MW'%R<7;&Y^SON4K?R/^`'D?^!_V:#>^ZZY[\[N/S6#=E5?N/Y'W:- M_T]_\P:#?YYZ_^=>]/[T4O%89QXX MFS1;K).>(>N>];JK=&2&9^*&94;).AW=6D:8T"W/Z6ZRSCQ[C#WVK7HO>\(Q MZ(5.QLLZ<=@[L?#[YG)Z]O9DVID[^)%_$ZVG3PO_ECZP#H3Q:_MV8J_L94RR M$W_J3QUCG+)VY-1O,UDYJSRRNV8D'AL]G&;>P^G$3T=3:IEGG+6?^K)>OK)$V-.S=H',ASEQ"?[S1)/)HI.B=H2=:F^._ M/:L;)YVYI41YIA/;VF>F#R/,IGFDW\IM,X^<6+P;RUW@K&.S#`>L7$7 M[6*BTNQVF?0T.]AI:Y[#K`-:*EH+NCDI/118JY39&E-/-EW.>+^-<;*1MYHA?1S+,MTY@NJ1T]5J?7#:X[4EV6HYU>M:9%/E`CJW"_W.MA_B.I#-"7GKP^A8W##8B"UGF^'3 M?0#]I)MA/*0QE;/3]GA%SPY247/)'H%9XJF:>73M6"L["YG)4\UL!N,;6<;, M%[,S!F5D=L!JRYK.QN+B026Y>">T:<4T+&JR=S(C'K'WFMU0]1O[QUHK>TS_ M!I%"6;SU7/_X&-7NQO@C1.$37$OJG>RSH2P(9@]K^7PS?)RO62?3!VJF5K+*9^QTQ4UQ$R9C=X-K?&-OZ!; MSGKJ3OYP-0=OW5-,1$_MD*BR+]?N>>0<^5V0_K?4B2!]G&^V=7!<6^AQ6R-WLG'8\(UE^2D-3-=WD5@&H=+,2IF M%-&\CL1HLED=7O._TDNS.48/V2:V]@S>E5<5)P''Z(EWETHWM$=L[-Y0:V/6 MS"%:4:(>`NV"K:EY#>]?SE9:3=)O&MEJ=@:6&R9D+MJ[NP%82V*2Q<`[@R[H M*1#>"N9AK(\)U%8W_:F7B)K,UMA[9,U86*B^6K/:O57*1FH@1@7*HX5SI=A/ MS7M!.5WB*ICH`M]`S[O@<<5\-Z_?L#723\W9YB97K6F,M&WQ:K&=:36YK@:W5Y);KIT:(\Q]K9S.P->%MV4+# MM',-&LJI];0"$QWR["6\EN3V#V!RG,,3FO4V]JG(CAD[V>WA*'LU?9+A"2_^E?,FGN7]QV5U>P`B+?N.J4EA3 MF'96\\W#&L88:C+ML3;V'A?!5&LK'^^2_S+B!Y\\@+"@7=X+_LWVBKK/[*ZV M?$DV4_Z%:I)_!X\L;8@\O.[?I:>2^U-\Y_(VYKU$K<'.\8'OTV(I#/SGR!PG M@2W?B78'?YR8+TBL-GF^D;8EXY+PAP;*#.2]+#'Y'LRY82-FFQ';C7H/HI\1 MVP\G^.2*:H(;+-H!TX]QXS%K.0F5AE9SD,UK2J?/]\23]=2_UR8/>:_.G+S0 MH3%AH]Y=3H6'D/J]7:IW\IKQ!W"CPUR?8UW6>N:%LB@1.P=F18M-7O0(P6#T MXGSPB?1#.K<\VRB^D]D:V)6TU\U]#:Z7OT\CF"_/Z/BMY MK_(S459KO#@ZNCAS7;IVYO"OR]<_7+Y_-WBOKC^^>?/TZ?'Q:J2N MRU"N_.*'>0?QR2E]RSZGT@M[W"9.)P%=O0>EM=R)Q5UJ[7;-IU#5%#^=N?:) M:L;64^DI5E-Z)7F?K;?:;D^T-B\7,R[WEQFN&F]Y-XNV:F8[:LI3CK;#%C7E M4Y-RS9%64^_WJMC/TU6>E1J1V>9U\9G%-7MWN;599#Z6=/NHU23-)KRMXAQ* MNM5JBM;#DU2D1/%&O=]*0\I*DZTQ=C3]H*UUEZ%^O(2B:T@)6VU;2Y"56VLY MB5<>J6T[R$?*SK.MHJ:[NF>"VY,_;(?-_EN\!S_J^?(+:5>2Z'LFW'\5YG5W M_5KLPT715P+2.7.XHWEQ)#U98_6P( MGV$'K,Y:9CPSXQ5;#1[560C6E2=VRGG2:B9\)0@TCYDG_CBVV%Y9WRO:FR!E M:\A*JSF:+=DZMN(K0[#CA,-7_QFL+.S$*-:4H]26.V?ME2X!$$*KL%^+[`DL M#@4LP[%\]J3T[\G6+A,490I+Y;JV/'7L47C2W88E7%]"L?>>//__WKS;$ M4(W_#KX'_GO.MW]VDRPK60]250O3`F@=.[3AZ60L)A'O7,*'4V<4)8,6DM M]'K=R29UQG'/""7@)]%;0'3%35^;%$GK,.;>T&]CO2\&19#L>S M;!K=%>X9;&_/O&VFK3]0MG'E+Q2!+'NXUR&A<`)XN_VP,0-$&W#F@%`G'6'F M&(U":7/S!:8XX=''74@I'E[C@'66<:;<_YOO&UIBRE?=Z>. MDR1RW*E\"7?.<2<=B=I4RCK7G]8_:1BTOE-BIRQ^\E((EF6.Y7Y>>8@5XL06 M1[8$#J?A!AK.S/00P9XCY=-+2'`VH`7`Y$(=N5:HM-Z&;.9MX=*$_[*GBN MK9`MF`&`+!20#QVUUO9YA#27D.O<&<^$[P@FWG!HCC*+<\R4FG+V3;6K?!OUBX9+<43`M.5)KB?8P]H+;7MFE%POAH%$ND?!=99@O MDP*BW8-#YWA&4="YOE_'$YF&=>==]@DB5F5,'%9@?A+1SV\*&2\=`SBRS/Z, MV)F,L"EHA;5\X&VXEXU78+@VFG0(P=M37T2>N00?;5A)T!&.PCYFXVSX.8_9 MFM8/0,+],BXE+=,O2'B4L>.1+ISC_KN0\Y,M/3#?8OMA85]@@((Q2G(ZUA\6 M2"9%37,QWM3:X@[`%A9^V$%1FP4(F[(Q9JK6:; MP?H>>R'W3-+;:C$=$5,HX.^ZKP7/I+SM+H\_VA'3$]@H^;6M=:LX.\6Z55BU MNNO7&@XJ'U:HO*:'Q.IN@C(NCYA[T(U@!SG3VJ#0>0V7H;F6"L"+M':ZT!%Y M(2$H(/>TYTA?@>O$XP2S%JE+#DNM4()$O@.YWYD6Z>$A<=1_0+>O_U#$K(=D0*0P$Z2FF[U2(!2 MK>I%7BHXWND.C8B(@"Z!X^!;M7GK=L10-/1:/[-EA=HJUK`M8520(&,MWN-6 ME(3]7$=."7+,=T4*$-W/=N`M3I(_E6,/Q8B!'`N(-9BZ)F040I>P(W+`(PRB MY<$6.LZC$9H>M/N[HT.Z!*GS[K8>I";)SC4-[;*Y;$B[$PHL[\@>V@/\ASOMX+,MWM;]2[#8"E?N4QC+;4+Y7Q'^^;A'^^$O\Y MN+R`#!VE^$_[___\/F5'_,?3MR-&&KX>(.7_EH=Y.-6?$_QO^;%5!7/,<=)C M]YFK9/\Z,O)XY*R3'JS_(ECC*.*^(.P[;,&5H9@HZ;*%]?&1$UP=2X9=,GN5 M8*B%`BQ^&N33R[MDG5XG@Q^F1+H_Y*[RF.CVQT2#YT$,&2CAX1$DU>?.U(X# M*XH%`,E:?KM.,?P!M=@V@XCT`EJ@\(NBR&O4>#A>RB#&6W_QA(1UD+;`4!0$ MLE30"HO='0,2RFK;$&X0Y%9.:L>P@]U=Y<-\%<-JM41ZH06!!2"P0U#!XZ`Z MB4,4&8`WP**-$$%FC9YNFV:B1^6!R4Z076%I@#XIR)\MA9RZ-P*N.#)BD[P[ M89=Q"!N**!_:D=U#($V0R8>YL\J!K0#Z[5E\C\"^-Y,5$>M!`JO-_@M/##D4 M%W&^)F\A;C'X*@VMY&T1"#OLKAU.7D#8G?<3V@"PO`T;*P#.9T;,1@A.X.SX M&W&`!H[8&6PXD-`--`."PP$*SXC>D(4`\@#QD:W/`';;9L]G>TO80&6PC6)G M7R#AY8BN<3`;@6QV_`8ZXW0=TBH/6Q()GWCL"`KFMX%-7(A`/FS6.!1-FT/0 MP^IT&7?I,,[!&:8C=N,:WI"].HOPW4,%721B>SOU:;&Y7X8FE\[!-@3: M>40%:).OF:8`9#)$3"_.;1&:.,[%+Q(,=Y">.;B<%V4G8>0S"^TR2;!9[LR[Z$,X5)GW M6,N-"*9,_D8#NR7!%X#'J9\"`(Q45;#;46X0/,,.#-VU/,OV"&[+9GY*Y]P4 M@*K19)D^/,T@!&,!`NHS;PM0]3I]`\`(L^O@=OT`[P"-7@.,$BH2L+!:!/PX M3,=]*`7$8;/>74N8>F31\88'S*%=\'VL#FE<@A/R-G#*+`^G6_#+5V&";<`_ MHPA:@-Q$IO-3!;8)D"V+."J">N#P33!\7'BY@-"8GN))#D17XVX9<[@L0ZC, MX8`7TVVH62UKL<=T@9MY@]-7ZIT]T$^+UG MDP2N50S(6Y9_/[I%$`K)\WS2H(ZYQ032:L5XY_Q7#[BVN%6BCO,2P+1%']6. MN*AS`:-(L,?D$(VDA69$/%3?!P_&8@<`I($]\`0>N_C!/,0U1X=RX(BG6D*' M_R)4HY$!Z6">"R"&U>:@EW@B$4](H`5!$,'(3B)!T-1A%";+$3#)M7@BER") M&3R*[RTB7+)"U$4E(9&@AP9`X/<(!N&CU$:N<_ZP`KT2\0X-3M(`"@)!=#`B MR14`400<%)51G0VYK0LJ`7I\ MR*P)"(,?#K,[(X66G\?:8?QHB$U/O)D91]9Q@A*8JLPX'RI_'T$,$%9!MFX= MC3&6S-:4"[5F0(DQU&L?&N&Y_9KM46^2Q=W]RH;>2@`;4[CRPLE M_BT<>XOGOU]^^OO/?_G#W[YQ"H#]?_^_?\93*[GGEU=7[>__?X_RA?'_W[_^ MV3O]9_:/OV9X+.S]\M-?:K_C*^?_@P%D)RN<_Z_.W?;\_UV*.O_#D/^SC\,- M?OGH,(_.7ACA]?'AV=TK,__8,Y>Y>S2V+UZXWI5EO'UM+:,WW7$2'O>/)R>' M%].3#^$/+V]FL\[\53]>V.;1!WMU]HFMP7'O_&[CF!]3YZ-AG+T]/7(O_&[_ MZ-W+_L?EZ?G;I[.+RY/SRQ>7@\M/8[\S'[R;7U]=KD>>]>+&>W#?^=,W=Z\' M/_S(3C7WP:.QO+X]_?CFRG\<=M]]'CXNGT:WV='LZ7T6G=Z:G?G^?SL\_O-JL%G;0 M7;VZ8BO*TZO;A]1>.!_M'[UDMDDV[P_'Z_?]=^N7SKOW+Z?OWW_^,/_Q?;:( M>]V;^//KFTWO_O9S[_&'=?I^V!F%Q]9@?#RX"->#XQOO_:O)\4-OLD[/WOHO MS\=W+Z^G\=!CV\&KZ7WWYK>PNK2E+6UI2UO:TI:VM*4M;6E+6]K2EK:TI2UM 5:4M;VM*6MK3E>Y?_!^0_E#(`0`$` ` end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 3: 6:44 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 2FB7B14D76 for ; Mon, 11 Oct 1999 03:06:27 -0700 (PDT) (envelope-from singuru@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 PAA05847 for ; Mon, 11 Oct 1999 15:36:45 +0500 (GMT) Received: from canine.wipinfo.soft.net (root@canine.wipinfo.soft.net [192.168.205.6]) by vayu.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id PAA09122 for ; Mon, 11 Oct 1999 15:37:25 +0500 (GMT) Received: from tagore (ncrtagore.wipinfo.soft.net [192.168.205.3]) by canine.wipinfo.soft.net (8.9.3/8.9.3) with SMTP id PAA03540 for ; Mon, 11 Oct 1999 15:37:12 +0530 Date: Mon, 11 Oct 1999 15:43:28 +0530 (IST) From: Singuru RadhaKrishna X-Sender: singuru@tagore To: freebsd-hackers@FreeBSD.ORG Subject: multicast set TTL regarding... 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 all, I'm using the following call to set the ttl value (after doing a successful socket call) ------ ttl=5; if (setsockopt(sockfd, IPPROTO_IP, IP_MULTICAST_TTL, (char *)&ttl, sizeof(ttl)) < 0) { printf("\nserv.c: setting of TTL value failed \n"); perror("setsockopt"); exit(1); } --------- It gives the following message : ------ serv.c: setting of TTL value failed setsockopt: Invalid argument -------- I tried with "root" perms also. But it didn't help. I would be thankful if any one can provide me some help on this. PS: I'm not in this mailing list. Please mark a copy to "singuru@wipinfo.soft.net" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 3:30:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 31C1814E20 for ; Mon, 11 Oct 1999 03:30:15 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id MAA25593; Mon, 11 Oct 1999 12:32:20 +0100 From: Luigi Rizzo Message-Id: <199910111132.MAA25593@labinfo.iet.unipi.it> Subject: Re: multicast set TTL regarding... To: singuru@wipinfo.soft.net (Singuru RadhaKrishna) Date: Mon, 11 Oct 1999 12:32:19 +0100 (MET) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Singuru RadhaKrishna" at Oct 11, 99 03:43:09 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 418 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > all, > I'm using the following call to set the ttl value (after doing a > successful > socket call) > ------ > ttl=5; > if (setsockopt(sockfd, IPPROTO_IP, IP_MULTICAST_TTL, > (char *)&ttl, sizeof(ttl)) < 0) check the type of "ttl". On Unix it should be char; on Windows it needs to be int. Some implementations can be more or less tolerant on size mismatch cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 3:40:18 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 E290314E23 for ; Mon, 11 Oct 1999 03:40:07 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id DAA04735; Mon, 11 Oct 1999 03:59:49 -0700 (PDT) Date: Mon, 11 Oct 1999 03:59:49 -0700 (PDT) From: Alfred Perlstein To: Mohit Aron Cc: freebsd-hackers@FreeBSD.ORG Subject: work in progress, (was Re: sbappend() is not scalable) In-Reply-To: <199910082051.PAA25028@cs.rice.edu> 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, 8 Oct 1999, Mohit Aron wrote: > Hi, > I recently did some experiments with TCP over a high b/w-delay path > and found a scalability problem in sbappend(). The experimental setup > consisted of a 100Mbps network with a round-trip delay of 100ms. Under this > situation, FreeBSD's TCP version is incapable of attaining more than 65 Mbps > on a 300MHz Pentium II - even without slow-start. > > I tracked down the problem to sbappend() - the routine that appends user data > into the socket buffers for network transmission. Every time a TCP ACK > acknowledges some data, space is created in the socket buffer that permits > more data to be appended. Unfortunately, the implementation does not maintain > a pointer to the end of the list of mbufs in the socket buffer. Thus each > time any data is added, the whole list of mbufs is traversed to reach the > very end where the data is added. Since the b/w-delay product is large, there > can be about 600 mbufs in the socket buffer waiting to be acknowledged. Thus > upon every ACK, about 600 mbufs are traversed causing the TCP sender to run > out of CPU. > > The problem is not limited only to high b/w networks - it is also present in > long latency paths (satellite links). Thus a server transferring a large file > over a satellite link can spend lot of CPU due to the above problem. > > Hope the problem shall be fixed in future releases, I started work on this, addmittedly i'm pretty new to the uipc code and right now I have some work done towards this: http://www.freebsd.org/~alfred/sockbuf3.diff (pre green's socketbuf limiting stuff) however it panics the box if you send a lot of data, a good way to have it blow up is to "ls -lR /" through telnet. It's also pretty verbose with debug printfs. It panics when tcp_output does an mcopy with invalid parameters, it seems that sb_mb is getting set to NULL somehow (my new sbcompress may be the culpret) the reason i'm posting it is that i'm tired and and hoping to wake up with a email saying "here just fix line xxx of zzz" :) the patches also address (or try to address) a flaw in the sbcompress() function, right now it always tries to copy mbuf 'backwards' my patch tries to do a copy forward if it can. personally i don't like sbcompress I'm interested in what people think about making it 'lazy' the algorithm would work like so: on sbcompress, walk the mbuf list free'ing empty bufs (already done) note any places where a copy would work to compress, but instead of compressing, just update a counter in the socketbuf. if sbcompress notices the that the amount of "fragmanentation" has exceeded a certain level then it will walk the entire socket compressing it and reset the counters. It would also be interesting to vary how sbcompress works based on the amount of free mbufs in the system (using phk's green/yellow/red state to determine what to do) either way this would _really_ help with short lived sockets that are transmitting small amounts of data. the only problem is that i'm not sure if it's ok to mess with the mbufs after they've been put into the socketbuffer because someone else my be holding a reference to it. comments? the patch also adds a whole lot of comments, and removes some useless casts and changes a lot of m = 0 to m = NULL. And if anyone made it this far, :) do you happen to know what the #ifdef notyet along with mcopypack stuff is for? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 7:44:51 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 67B6914E2F for ; Mon, 11 Oct 1999 07:44:48 -0700 (PDT) (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 KAA16597; Mon, 11 Oct 1999 10:44:39 -0400 (EDT) Date: Mon, 11 Oct 1999 10:44:35 -0400 (EDT) From: Zhihui Zhang To: Gustavo V G C Rios Cc: hackers@FreeBSD.ORG Subject: Re: file system system calls In-Reply-To: <380145BD.A4C04C01@ddsecurity.com.br> 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, 11 Oct 1999, Gustavo V G C Rios wrote: > May anyone here point me where in the source tree i can see file system > API implemented, like open, write, close, etc..... Check files /sys/src/sys/kern/vfs_syscalls.c and /sys/src/sys/kern/sys_generic.c -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 8:14:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id D430D150AF; Mon, 11 Oct 1999 08:14:22 -0700 (PDT) (envelope-from leif@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id RAA58245; Mon, 11 Oct 1999 17:14:13 +0200 (CEST) (envelope-from leif@neland.dk) Message-ID: <014801bf13fb$5225ef00$0e00a8c0@neland.dk> From: "Leif Neland" To: "Brian F. Feldman" Cc: References: Subject: Sv: mrtg, user-ppp Date: Mon, 11 Oct 1999 17:14:23 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message -----=20 From: Brian F. Feldman To: Leif Neland Cc: Sent: Sunday, October 10, 1999 3:49 PM Subject: Re: mrtg, user-ppp > On Sun, 10 Oct 1999, Leif Neland wrote: >=20 > > I'd like to plot uptime and number of calls from ppp to mrtg. > >=20 > > Any 'easy' way to ask ppp for these values, getting the answer for = number > > of seconds online since last asked? > >=20 >=20 > Store the time from the previous call after each call, as with a > (non-thread-safe) "static" variable in C. You can accomplish reading = the > time up pretty reasonably using either pppctl or just working directly > with the ppp socket in the program. I can't seem to find an accumulated off-hook time. pppctl only lists the = off-hook time of the last call. So 3 calls of one minute will only be = shown as one minute when queryed by mrtg. Looking into the code, no such accumulated timer exists. I either have to write a "proxy" querying ppp every 30 secs (faster than = idle timeout), accumulating the values for mrtg to query every 5 = minutes, or modify ppp itself. Perhaps a "pppctl show mrtg", giving = output directly in the format mrtg likes... Leif >=20 > > Leif > >=20 >=20 > --=20 > Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! = / > green@FreeBSD.org `------------------------------' >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 8:15:20 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 80C9B151F5 for ; Mon, 11 Oct 1999 08:15:18 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id IAA10976; Mon, 11 Oct 1999 08:35:00 -0700 (PDT) Date: Mon, 11 Oct 1999 08:35:00 -0700 (PDT) From: Alfred Perlstein To: Mohit Aron Cc: freebsd-hackers@FreeBSD.ORG Subject: testable! Re: work in progress, (was Re: sbappend() is not scalable) 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 replying to my own message. :) I have a newer version of the patch, it doesn't look like it's panic'ing but it really needs some serious testing. http://www.freebsd.org/~alfred/sockbuf4.diff If you are running -current and know how to get a crashdump please give this a whirl and tell me what it does for you. thanks, -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [bright@wintelcom.net] On Mon, 11 Oct 1999, Alfred Perlstein wrote: > > On Fri, 8 Oct 1999, Mohit Aron wrote: > > > Hi, > > I recently did some experiments with TCP over a high b/w-delay path > > and found a scalability problem in sbappend(). The experimental setup > > consisted of a 100Mbps network with a round-trip delay of 100ms. Under this > > situation, FreeBSD's TCP version is incapable of attaining more than 65 Mbps > > on a 300MHz Pentium II - even without slow-start. > > > > I tracked down the problem to sbappend() - the routine that appends user data > > into the socket buffers for network transmission. Every time a TCP ACK > > acknowledges some data, space is created in the socket buffer that permits > > more data to be appended. Unfortunately, the implementation does not maintain > > a pointer to the end of the list of mbufs in the socket buffer. Thus each > > time any data is added, the whole list of mbufs is traversed to reach the > > very end where the data is added. Since the b/w-delay product is large, there > > can be about 600 mbufs in the socket buffer waiting to be acknowledged. Thus > > upon every ACK, about 600 mbufs are traversed causing the TCP sender to run > > out of CPU. > > > > The problem is not limited only to high b/w networks - it is also present in > > long latency paths (satellite links). Thus a server transferring a large file > > over a satellite link can spend lot of CPU due to the above problem. > > > > Hope the problem shall be fixed in future releases, > > I started work on this, addmittedly i'm pretty new to the uipc code > and right now I have some work done towards this: > > http://www.freebsd.org/~alfred/sockbuf3.diff > > (pre green's socketbuf limiting stuff) > > however it panics the box if you send a lot of data, a good way > to have it blow up is to "ls -lR /" through telnet. It's also > pretty verbose with debug printfs. > > It panics when tcp_output does an mcopy with invalid parameters, it > seems that sb_mb is getting set to NULL somehow (my new sbcompress > may be the culpret) > > the reason i'm posting it is that i'm tired and and hoping to wake > up with a email saying "here just fix line xxx of zzz" :) > > the patches also address (or try to address) a flaw in the sbcompress() > function, right now it always tries to copy mbuf 'backwards' my patch > tries to do a copy forward if it can. > > personally i don't like sbcompress I'm interested in what people think > about making it 'lazy' the algorithm would work like so: > > on sbcompress, > walk the mbuf list free'ing empty bufs (already done) > note any places where a copy would work to compress, but instead > of compressing, just update a counter in the socketbuf. > if sbcompress notices the that the amount of "fragmanentation" > has exceeded a certain level then it will walk the entire > socket compressing it and reset the counters. > > It would also be interesting to vary how sbcompress works based > on the amount of free mbufs in the system (using phk's > green/yellow/red state to determine what to do) > > either way this would _really_ help with short lived sockets > that are transmitting small amounts of data. > > the only problem is that i'm not sure if it's ok to mess with > the mbufs after they've been put into the socketbuffer because > someone else my be holding a reference to it. > > comments? > > the patch also adds a whole lot of comments, and removes some > useless casts and changes a lot of m = 0 to m = NULL. > > And if anyone made it this far, :) do you happen to know what > the #ifdef notyet along with mcopypack stuff is for? > > -Alfred > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 8:18:50 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 43EDE14BE7 for ; Mon, 11 Oct 1999 08:18:48 -0700 (PDT) (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 LAA25451; Mon, 11 Oct 1999 11:05:30 -0400 (EDT) Date: Mon, 11 Oct 1999 11:05:26 -0400 (EDT) From: Zhihui Zhang To: Ruslan Ermilov Cc: freebsd-hackers@FreeBSD.org Subject: Re: How to prevent a system call from restart? In-Reply-To: <19991011115506.A34243@relay.ucb.crimea.ua> 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, 11 Oct 1999, Ruslan Ermilov wrote: > On Sun, Oct 10, 1999 at 03:16:43PM -0400, Zhihui Zhang wrote: > > > > I modify the day time client program from the Stevens' book and run it on > > both a Sun workstation and a FreeBSD machine. In the program, I use > > signal() and alarm() to set a 5 seconds timeout. The program works as > > expected on Sun (after I comment out the daytime line in the file > > /etc/inetd.conf) but not on the FreeBSD machine. > > > > Later I find out that the reason maybe the recvfrom() restarts > > *automatically* in FreeBSD. Why the default behaviour is different from > > SunOS? If I am correct about the reason, can anyone tell me how to prevent > > the recvfrom() from restart after receiving the SIGALRM signal? > > > > By the way, I also try the socket timeout option. It works immediately. > > > > Any help is appreciated. > > > Refer to the siginterrupt(3) manpage, it has all info you are looking for. Thanks! I add the following line after signal(), then it works: (void) signal(SIGALRM, sig_alarm); siginterrupt(SIGALRM, 1); <-- only add this line. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 8:21: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from enterprise.sanyusan.se (enterprise.sanyusan.se [195.24.160.51]) by hub.freebsd.org (Postfix) with ESMTP id 70E7114D6F for ; Mon, 11 Oct 1999 08:21:04 -0700 (PDT) (envelope-from anders@enterprise.sanyusan.se) Received: (from anders@localhost) by enterprise.sanyusan.se (8.9.3/8.9.3) id RAA67789; Mon, 11 Oct 1999 17:20:58 +0200 (CEST) (envelope-from anders) Date: Mon, 11 Oct 1999 17:20:58 +0200 From: Anders Andersson To: Kazutaka YOKOTA Cc: hackers@FreeBSD.ORG Subject: Re: keeping termcap up to date Message-ID: <19991011172058.A67712@enterprise.sanyusan.se> References: <199909201558.AAA07459@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199909201558.AAA07459@zodiac.mech.utsunomiya-u.ac.jp> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tis, Sep 21, 1999 at 12:58:37am +0900, Kazutaka YOKOTA wrote: > I just wonder why don't we just import termcap database from > the master site: http://www.tuxedo.org/terminfo, rather than > maintaining our own copy? > > In the past, it has been pointed out that some of the termcap entries > needs updating. Some entries have been revised. But, it appears that > some others haven't, and we are now getting out of sync with the > latest version of the terminal database. > > The simplest and the easiest thing to do is to just import > the master copy from the above site... This sounds great! You can look at both NetBSD and OpenBSD for example how to merge it since both use their termcap from ESR master. Although NetBSD is a bit dated. Best regards, Anders -- Anders Andersson anders@sanyusan.se Sanyusan International AB http://www.sanyusan.se/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 10:35:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (dynamic-110.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.110]) by hub.freebsd.org (Postfix) with ESMTP id BD3CF153CB; Mon, 11 Oct 1999 10:35:28 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id SAA02509; Mon, 11 Oct 1999 18:31:37 +0100 (BST) (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 RAA00460; Mon, 11 Oct 1999 17:50:11 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199910111650.RAA00460@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Leif Neland" Cc: "Brian F. Feldman" , freebsd-hackers@FreeBSD.ORG Subject: Re: Sv: mrtg, user-ppp In-reply-to: Your message of "Mon, 11 Oct 1999 17:14:23 +0200." <014801bf13fb$5225ef00$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Oct 1999 17:50:11 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > Looking into the code, no such accumulated timer exists. > I either have to write a "proxy" querying ppp every 30 secs (faster than idle timeout), accumulating the values for mrtg to query every 5 minutes, or modify ppp itself. Perhaps a "pppctl show mrtg", giving output directly in the format mrtg likes... > > Leif Hmm, something a bit more generic would be preferred (w/ patches ?). There's an item on my TODO list that will allow ``display variable'' so that people can show the values of individual variables in a consistent way. The possible values of ``variable'' will be documented - in much the same way as the output of ``show ...'' isn't. The ultimate objective is to write a tcl based front end that will give you xload-style throughput graphs, connect/disconnect buttons, timeout slide bars etc. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 10:57:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id AC5E214A01 for ; Mon, 11 Oct 1999 10:57:56 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id NAA04164; Mon, 11 Oct 1999 13:57:16 -0400 (EDT) (envelope-from luoqi) Date: Mon, 11 Oct 1999 13:57:16 -0400 (EDT) From: Luoqi Chen Message-Id: <199910111757.NAA04164@lor.watermarkgroup.com> To: davidc@acns.ab.ca, freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read kills machine Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am working on a small threaded program > that uses aio_read(). In my first attempt > to run the program it killed my machine > instantly. The second time it only locked > it solid. I get no messages, warnings, or > errors. > > I am certain that my program is not correct > (besides the obvious consiquence of running > it :) ), but I would also like to determine > why it kills the machine. I was not root > either time I ran the code. > > I could provide additional debugging information, > and the source to anybody who cares about this. > I am not sure up front what would be helpful. > > The machine is a dual 400 with 512Mg ram, running > 3.3-stable as of Sept 28 with SMP enabled. > > Thanks in advance. > > Chad > davidc@acns.ab.ca > You need to go to -current for this. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 11: 1: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194]) by hub.freebsd.org (Postfix) with ESMTP id 7863A15616; Mon, 11 Oct 1999 11:01:01 -0700 (PDT) (envelope-from sa-list@avantgo.com) Received: from avantgo.com ([10.0.128.109]) by bomber.avantgo.com (Netscape Messaging Server 3.5) with ESMTP id 115; Mon, 11 Oct 1999 10:56:06 -0700 Message-ID: <3802261F.BBEF68C3@avantgo.com> Date: Mon, 11 Oct 1999 11:02:07 -0700 From: Stevan Arychuk Reply-To: sa-list@avantgo.com Organization: AvantGo Inc. X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: dg@root.com, FreeBSD-hackers@FreeBSD.ORG, FreeBSD-stable@FreeBSD.ORG Subject: Re: SMP + fxp0 wierdness References: <199910081833.LAA00799@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So if this problem is NOT related to specific hardware, how can we get the driver fixed? Stevan Arychuk AvantGo Inc. stevan@avantgo.com Mike Smith wrote: > > > Thanks for your response David. > > > > Do you think the problem is isolated to just the onboard devices? Would > > a PCI NIC help or is it the entire N440BX board? > > We've seen these symptoms on non-Intel boards. (eg. ASUS P2L, P2B). > > -- > \\ 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 Oct 11 11:31:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 51DCB14A2A; Mon, 11 Oct 1999 11:31:18 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA01100; Mon, 11 Oct 1999 11:22:30 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910111822.LAA01100@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: sa-list@avantgo.com Cc: Mike Smith , dg@root.com, FreeBSD-hackers@FreeBSD.ORG, FreeBSD-stable@FreeBSD.ORG Subject: Re: SMP + fxp0 wierdness In-reply-to: Your message of "Mon, 11 Oct 1999 11:02:07 PDT." <3802261F.BBEF68C3@avantgo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Oct 1999 11:22:30 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So if this problem is NOT related to specific hardware, how can we get > the driver fixed? Talk to the maintainer (David). We've offered him cores and kernels before. Alternatively, you'll need to experiment with your setup to determine what characterises the failures and help David out with more data. > Stevan Arychuk > AvantGo Inc. > stevan@avantgo.com > > Mike Smith wrote: > > > > > Thanks for your response David. > > > > > > Do you think the problem is isolated to just the onboard devices? Would > > > a PCI NIC help or is it the entire N440BX board? > > > > We've seen these symptoms on non-Intel boards. (eg. ASUS P2L, P2B). > > > > -- > > \\ 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 > -- \\ 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 Oct 11 11:46:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from colnta.acns.ab.ca (clgr000532.hs.telusplanet.net [161.184.82.24]) by hub.freebsd.org (Postfix) with ESMTP id 6AF2515585 for ; Mon, 11 Oct 1999 11:46:41 -0700 (PDT) (envelope-from davidc@colnta.acns.ab.ca) Received: from localhost (davidc@localhost) by colnta.acns.ab.ca (8.9.3/8.9.3) with ESMTP id MAA00383; Mon, 11 Oct 1999 12:46:29 -0600 (MDT) (envelope-from davidc@colnta.acns.ab.ca) Date: Mon, 11 Oct 1999 12:46:29 -0600 (MDT) From: Chad David To: Chris Costello Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read kills machine In-Reply-To: <19991010204252.D15135@holly.calldei.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 I have submitted a PR. Upon closer inspection I found that it is not (directly) the call to aio_read() that kills the machine, but instead a call to sched_yield() after a call to pthread_cond_wait() with a NULL in the mutex field. Even a print statement before the call to sched_yield() prevents the kill. Some replys indicated that I should use -current for aio_*. Would this be true also for any serious threading? Is -current ready for a semi-production environment? The source for this code is available from http://www.guild.ab.ca/killer.tar.gz if anyone would like to take a look. The crash has been truncating main.c, so you may want to copy it before running the program. Thanks. Chad On Sun, 10 Oct 1999, Chris Costello wrote: > On Wed, Jan 01, 1997, Chad David wrote: > > I am certain that my program is not correct > > (besides the obvious consiquence of running > > it :) ), but I would also like to determine > > why it kills the machine. I was not root > > either time I ran the code. > > Then FreeBSD does have a problem. Please file a PR using the > ``send-pr'' command or http://www.freebsd.org/send-pr.html and > supply the source to your program and whatever other information > you think will help us in figuring out the problem. > > -- > |Chris Costello > |Field tested: Manufacturing doesn't have a test system. > `------------------------------------------------------- > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 11:48:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailgw01.execpc.com (mailgw01.execpc.com [169.207.2.78]) by hub.freebsd.org (Postfix) with ESMTP id D1A8315603 for ; Mon, 11 Oct 1999 11:48:38 -0700 (PDT) (envelope-from rmukerji@execpc.com) Received: from earth.execpc.com (rmukerji@earth.execpc.com [169.207.16.1]) by mailgw01.execpc.com (8.9.1) id NAA26426 for ; Mon, 11 Oct 1999 13:48:38 -0500 Received: (from rmukerji@localhost) by earth.execpc.com (8.9.0) id NAA06028 for freebsd-hackers@FreeBSD.ORG; Mon, 11 Oct 1999 13:48:37 -0500 (CDT) Date: Mon, 11 Oct 1999 13:48:37 -0500 From: Arindum Mukerji To: freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read kills machine Message-ID: <19991011134837.A3440@earth.execpc.com> References: <199910111757.NAA04164@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3us In-Reply-To: <199910111757.NAA04164@lor.watermarkgroup.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Luoqi Chen (luoqi@watermarkgroup.com) [991011 12:58]: > You need to go to -current for this. > Surely the relevant patches should be backported to -release, then? Given the severity of the problem and the fact that this problem purportedly hangs the entire system from an unprivileged context, going to -current should take a back seat to backporting the relevant fix to -release. Let me know if I can help with this. Just my $0.02. -- Arindum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 11:58:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mta1.rcsntx.swbell.net (mta1.rcsntx.swbell.net [151.164.30.25]) by hub.freebsd.org (Postfix) with ESMTP id 410981532F for ; Mon, 11 Oct 1999 11:58:24 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta1.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FJG00HQWCP4R2@mta1.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Mon, 11 Oct 1999 13:58:17 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id NAA21772; Mon, 11 Oct 1999 13:57:29 -0500 (CDT envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Mon, 11 Oct 1999 13:57:28 -0500 From: Chris Costello Subject: Re: aio_read kills machine In-reply-to: To: Chad David Cc: freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991011135728.F19110@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <19991010204252.D15135@holly.calldei.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 11, 1999, Chad David wrote: > Some replys indicated that I should use -current > for aio_*. Would this be true also for any > serious threading? Is -current ready for a > semi-production environment? Not really. The fact is that a user program can crash 3.3-STABLE and that is unacceptable. No user program should be able to bring down a system, _especially_ in -STABLE. > The source for this code is available from > http://www.guild.ab.ca/killer.tar.gz if anyone > would like to take a look. The crash has been > truncating main.c, so you may want to copy it > before running the program. > > Thanks. > > Chad -- |Chris Costello |TRAPEZOID - A device for catching zoids. `---------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 12:26:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29]) by hub.freebsd.org (Postfix) with ESMTP id 51F4514C4A for ; Mon, 11 Oct 1999 12:26:17 -0700 (PDT) (envelope-from cmsedore@mailbox.syr.edu) Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.F79F6CD0@mailer.syr.edu>; Mon, 11 Oct 1999 15:26:19 -0400 Received: from localhost (cmsedore@localhost) by rodan.syr.edu (8.8.7/8.8.7) with ESMTP id PAA05228; Mon, 11 Oct 1999 15:26:16 -0400 (EDT) X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs Date: Mon, 11 Oct 1999 15:26:16 -0400 (EDT) From: Christopher Sedore X-Sender: cmsedore@rodan.syr.edu To: Chris Costello Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read kills machine In-Reply-To: <19991011135728.F19110@holly.calldei.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, 11 Oct 1999, Chris Costello wrote: > On Mon, Oct 11, 1999, Chad David wrote: > > Some replys indicated that I should use -current > > for aio_*. Would this be true also for any > > serious threading? Is -current ready for a > > semi-production environment? > > Not really. The fact is that a user program can crash > 3.3-STABLE and that is unacceptable. No user program should be > able to bring down a system, _especially_ in -STABLE. You need to rip out most of aio_* in -stable or -current for this to be true. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 13:55: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id DFE341500A for ; Mon, 11 Oct 1999 13:54:49 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from localhost (localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id GAA06824; Tue, 12 Oct 1999 06:54:27 +1000 (EST) (envelope-from andyf@speednet.com.au) Date: Tue, 12 Oct 1999 06:54:27 +1000 (EST) From: Andy Farkas X-Sender: andyf@localhost To: Chris Costello Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read kills machine In-Reply-To: <19991011135728.F19110@holly.calldei.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, 11 Oct 1999, Chris Costello wrote: > Not really. The fact is that a user program can crash > 3.3-STABLE and that is unacceptable. No user program should be > able to bring down a system, _especially_ in -STABLE. > Running ``nmap -sP 172.22.0.0/16'' as a normal user will cause a panic on a recent 3.3-STABLE system :( -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 14:19:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 3DAB8150FB for ; Mon, 11 Oct 1999 14:19:43 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA01973; Mon, 11 Oct 1999 14:10:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910112110.OAA01973@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andy Farkas Cc: Chris Costello , freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read kills machine In-reply-to: Your message of "Tue, 12 Oct 1999 06:54:27 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Oct 1999 14:10:39 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 11 Oct 1999, Chris Costello wrote: > > > Not really. The fact is that a user program can crash > > 3.3-STABLE and that is unacceptable. No user program should be > > able to bring down a system, _especially_ in -STABLE. > > > > Running ``nmap -sP 172.22.0.0/16'' as a normal user will cause a panic on > a recent 3.3-STABLE system :( Could you be any less specific about the panic? Any sort of detail is just going to make us want to fix it. -- \\ 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 Oct 11 14:23:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id F112B14CD5 for ; Mon, 11 Oct 1999 14:23:17 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from localhost (localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id HAA06878; Tue, 12 Oct 1999 07:22:47 +1000 (EST) (envelope-from andyf@speednet.com.au) Date: Tue, 12 Oct 1999 07:22:47 +1000 (EST) From: Andy Farkas X-Sender: andyf@localhost To: Mike Smith Cc: Chris Costello , freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read kills machine In-Reply-To: <199910112110.OAA01973@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, 11 Oct 1999, Mike Smith wrote: > > Running ``nmap -sP 172.22.0.0/16'' as a normal user will cause a panic on > > a recent 3.3-STABLE system :( > > Could you be any less specific about the panic? Any sort of detail is > just going to make us want to fix it. Here most of the message I posted to -stable: ----snip---- *From andyf@speednet.com.au Tue Oct 12 07:20:08 1999 Date: Mon, 27 Sep 1999 19:43:21 +1000 (EST) To: freebsd-stable@FreeBSD.ORG Subject: nmap V. 2.3BETA5 causes panic The system will panic with an 'out of mbufs' message when I run the above nmap command ("ping scan" a class B subnet - my internal IP network). Should this be happening when run as a normal user?? The kernel is pretty stock with maxusers 32, no NMBCLUSTERS option, unneeded devices removed. There is 64M RAM and 256M swap; it is has dual 90MHz P54C's. This system (my workstation) is a: FreeBSD 3.3-STABLE #0: Mon Sep 20 09:44:35 EST 1999 I am: bash-2.03$ id uid=1000(andyf) gid=1000(andyf) groups=1000(andyf), 0(wheel) I have: bash-2.03$ limits Resource limits (current): cputime infinity secs filesize 1048576 kb datasize 65536 kb stacksize 8192 kb coredumpsize 131072 kb memoryuse 65536 kb memorylocked 8192 kb maxprocesses 256 openfiles 256 I use: bash-2.03$ How would you go about preventing this problem? Thanks. ----snip---- > > -- > \\ 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 > > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 14:30: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 771AC14C36 for ; Mon, 11 Oct 1999 14:29:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA02032; Mon, 11 Oct 1999 14:20:08 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910112120.OAA02032@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andy Farkas Cc: Mike Smith , Chris Costello , freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read kills machine In-reply-to: Your message of "Tue, 12 Oct 1999 07:22:47 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Oct 1999 14:20:08 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Mon, 11 Oct 1999, Mike Smith wrote: > > > > Running ``nmap -sP 172.22.0.0/16'' as a normal user will cause a panic on > > > a recent 3.3-STABLE system :( > > > > Could you be any less specific about the panic? Any sort of detail is > > just going to make us want to fix it. > > Here most of the message I posted to -stable: Oh, that one. You need to increase maxusers or NMBCLUSTERS. This is the subject of ongoing work in -current that ought to make it back to -stable eventually. > ----snip---- > *From andyf@speednet.com.au Tue Oct 12 07:20:08 1999 > Date: Mon, 27 Sep 1999 19:43:21 +1000 (EST) > To: freebsd-stable@FreeBSD.ORG > Subject: nmap V. 2.3BETA5 causes panic > > The system will panic with an 'out of mbufs' message when I run the above > nmap command ("ping scan" a class B subnet - my internal IP network). > > Should this be happening when run as a normal user?? The kernel is pretty > stock with maxusers 32, no NMBCLUSTERS option, unneeded devices removed. > There is 64M RAM and 256M swap; it is has dual 90MHz P54C's. > > This system (my workstation) is a: > FreeBSD 3.3-STABLE #0: Mon Sep 20 09:44:35 EST 1999 > > I am: > bash-2.03$ id > uid=1000(andyf) gid=1000(andyf) groups=1000(andyf), 0(wheel) > > I have: > bash-2.03$ limits > Resource limits (current): > cputime infinity secs > filesize 1048576 kb > datasize 65536 kb > stacksize 8192 kb > coredumpsize 131072 kb > memoryuse 65536 kb > memorylocked 8192 kb > maxprocesses 256 > openfiles 256 > > I use: > bash-2.03$ > > How would you go about preventing this problem? > > Thanks. > ----snip---- > > > > > -- > > \\ 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 > > > > > > -- > > :{ andyf@speednet.com.au > > Andy Farkas > System Administrator > Speednet Communications > http://www.speednet.com.au/ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ 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 Oct 11 15: 2:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from octo.memory.se (octo.memory.se [193.13.247.17]) by hub.freebsd.org (Postfix) with ESMTP id 8987215623 for ; Mon, 11 Oct 1999 15:02:36 -0700 (PDT) (envelope-from hno@hem.passagen.se) Received: from [193.13.248.241] by octo.memory.se for id AAB06565; Tue Oct 12 00:01:03 1999 Received: from henrik.localdomain (localhost [127.0.0.1]) by henrik.localdomain (8.9.3/8.9.3) with SMTP id WAA01499; Mon, 11 Oct 1999 22:36:42 +0200 Message-ID: <38024A5A.57F046EC@hem.passagen.se> Date: Mon, 11 Oct 1999 22:36:42 +0200 X-Mailer: Mozilla 3.01 (X11; I; Linux 2.2.12 i586) MIME-Version: 1.0 Subject: Re: Squid under FreeBSD 3.3-STABLE ... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Marc G. Fournier" From: Henrik Nordstrom Cc: squid-users@ircache.net, freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc G. Fournier wrote: > 4. Decreased TCP's Maximum Segment Lifetime to three seconds > - did it This tweak is specific to PolyGraph testing in high speed LAN environment. It is defenitely NOT recommended tuning for an Internet connected system... MSL should in WAN connections be no less than 30 seconds. -- Henrik Nordstrom Squid hacker To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 15: 2:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 8F50815715 for ; Mon, 11 Oct 1999 15:02:38 -0700 (PDT) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id RAA04761; Mon, 11 Oct 1999 17:02:19 -0500 (EST) (envelope-from steve) Date: Mon, 11 Oct 1999 17:02:19 -0500 (EST) From: Steven Ames Message-Id: <199910112202.RAA04761@virtual-voodoo.com> To: andyf@speednet.com.au, mike@smith.net.au Subject: Re: aio_read kills machine Cc: chris@calldei.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199910112120.OAA02032@dingo.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Running ``nmap -sP 172.22.0.0/16'' as a normal user will cause > > > > a panic on a recent 3.3-STABLE system :( > > > > > > Could you be any less specific about the panic? Any sort of detail > > > is just going to make us want to fix it. > > > > Here most of the message I posted to -stable: > > Oh, that one. You need to increase maxusers or NMBCLUSTERS. This is > the subject of ongoing work in -current that ought to make it back to > -stable eventually. Could someone define what NMBCLUSTERS is and what it is used for? I've seen a lot of cases where increasing it (beyond the default 1024?) has helped systems be more stable, but what is it? If someone does bother to respond to this with a good definition then maybe that definition could make it into LINT? -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 15:10: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id 12F5B15B32 for ; Mon, 11 Oct 1999 15:09:56 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from localhost (localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id IAA06978; Tue, 12 Oct 1999 08:09:40 +1000 (EST) (envelope-from andyf@speednet.com.au) Date: Tue, 12 Oct 1999 08:09:40 +1000 (EST) From: Andy Farkas X-Sender: andyf@localhost To: Steven Ames Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read kills machine In-Reply-To: <199910112202.RAA04761@virtual-voodoo.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, 11 Oct 1999, Steven Ames wrote: > Could someone define what NMBCLUSTERS is and what it is used for? I've > seen a lot of cases where increasing it (beyond the default 1024?) has > helped systems be more stable, but what is it? > Here is an informative email from David Greenman: ----snip---- From dg@root.com Tue Oct 12 08:07:20 1999 Date: Mon, 17 May 1999 18:58:06 -0700 From: David Greenman To: Nicole Harrington Cc: stable@FreeBSD.ORG, Brian Behlendorf Subject: Re: maxusers/nmbclusters > I have read that if you have needs that would require turning up NMBclusters, >and certain sysctl options, etc, that you should do so independantly and not >increase maxusers up much above 256. Will that recomendation change with 3.2 as >well? If you specify NMBCLUSTERS, then you only need to tune maxusers for increased number of processes (nproc = 16 * maxusers). This is true in all versions of FreeBSD. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com ----snip---- > -Steve > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 16:15:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 8EBF2150BC for ; Mon, 11 Oct 1999 16:15:34 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id TAA38682; Mon, 11 Oct 1999 19:15:00 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Mon, 11 Oct 1999 19:15:00 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Mike Smith Cc: Andy Farkas , Chris Costello , freebsd-hackers@FreeBSD.org Subject: Re: aio_read kills machine In-Reply-To: <199910112120.OAA02032@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 I'd like everyone to note that for now, if you are providing user-access to a 4.0 box (and you don't absolutely trust your users), you should be using the RLIMIT_SBSIZE for limiting network memory usage just as you use other RLIMITs for memory limiting, etc. -- 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 Mon Oct 11 16:21:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id A0F48150D4; Mon, 11 Oct 1999 16:21:46 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id TAA38839; Mon, 11 Oct 1999 19:21:28 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Mon, 11 Oct 1999 19:21:27 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Chris Costello Cc: Laurence Berland , Robert Sexton , nsayer@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: CFD: "bogomips" CPU performance metric In-Reply-To: <19991010195854.C15135@holly.calldei.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, 10 Oct 1999, Chris Costello wrote: > On Sun, Oct 10, 1999, Laurence Berland wrote: > > I like the idea as an optional LINT parameter that is NOT in the generic > > kernel. Might make some linux people feel comfortable with the switch, > > or might prove useful under some odd circumstances, but I agree it'd be > > silly to include it by default (kindof on the level of a splash screen) > > I disagree. BogoMIPS is a completely meaningless measurement > and does not belong in our source tree as it will only produce > repository bloat. > Right. If you're worried that there's something wrong with your CPU speed, you can always bootverbose and check out the clocks and bzero tests. -- 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 Mon Oct 11 17: 7:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 6A0EC14A03; Mon, 11 Oct 1999 17:07:44 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id RAA15131; Mon, 11 Oct 1999 17:06:43 -0700 (PDT) Message-Id: <199910120006.RAA15131@implode.root.com> To: Mike Smith Cc: sa-list@avantgo.com, dg@root.com, FreeBSD-hackers@FreeBSD.ORG, FreeBSD-stable@FreeBSD.ORG Subject: Re: SMP + fxp0 wierdness In-reply-to: Your message of "Mon, 11 Oct 1999 11:22:30 PDT." <199910111822.LAA01100@dingo.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 11 Oct 1999 17:06:43 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> So if this problem is NOT related to specific hardware, how can we get >> the driver fixed? > >Talk to the maintainer (David). We've offered him cores and kernels >before. Alternatively, you'll need to experiment with your setup to >determine what characterises the failures and help David out with more >data. Hotmail has troubleshooted the problem down to the NCR controller. It appears that the problem only occurs when using one of those. If they plug in an Adaptec 2940 and use it instead of the onboard NCR then the problems disappear. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 17:12:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 920AE14A2C; Mon, 11 Oct 1999 17:12:51 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA02842; Mon, 11 Oct 1999 17:04:12 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910120004.RAA02842@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dg@root.com Cc: Mike Smith , sa-list@avantgo.com, FreeBSD-hackers@FreeBSD.ORG, FreeBSD-stable@FreeBSD.ORG Subject: Re: SMP + fxp0 wierdness In-reply-to: Your message of "Mon, 11 Oct 1999 17:06:43 PDT." <199910120006.RAA15131@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Oct 1999 17:04:12 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> So if this problem is NOT related to specific hardware, how can we get > >> the driver fixed? > > > >Talk to the maintainer (David). We've offered him cores and kernels > >before. Alternatively, you'll need to experiment with your setup to > >determine what characterises the failures and help David out with more > >data. > > Hotmail has troubleshooted the problem down to the NCR controller. It > appears that the problem only occurs when using one of those. If they plug > in an Adaptec 2940 and use it instead of the onboard NCR then the problems > disappear. We did this (you remember that we went through all this a while back, right?), but we've also been seing reports from people that aren't using NCR controllers. -- \\ 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 Oct 11 17:18:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 3070015729; Mon, 11 Oct 1999 17:18:41 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id RAA15224; Mon, 11 Oct 1999 17:17:54 -0700 (PDT) Message-Id: <199910120017.RAA15224@implode.root.com> To: Mike Smith Cc: sa-list@avantgo.com, FreeBSD-hackers@FreeBSD.ORG, FreeBSD-stable@FreeBSD.ORG Subject: Re: SMP + fxp0 wierdness In-reply-to: Your message of "Mon, 11 Oct 1999 17:04:12 PDT." <199910120004.RAA02842@dingo.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 11 Oct 1999 17:17:54 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> So if this problem is NOT related to specific hardware, how can we get >> >> the driver fixed? >> > >> >Talk to the maintainer (David). We've offered him cores and kernels >> >before. Alternatively, you'll need to experiment with your setup to >> >determine what characterises the failures and help David out with more >> >data. >> >> Hotmail has troubleshooted the problem down to the NCR controller. It >> appears that the problem only occurs when using one of those. If they plug >> in an Adaptec 2940 and use it instead of the onboard NCR then the problems >> disappear. > >We did this (you remember that we went through all this a while back, >right?), but we've also been seing reports from people that aren't >using NCR controllers. I haven't seen a report yet from someone not using an NCR/Symbios controller. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 17:38:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from funbox.demon.co.uk (funbox.demon.co.uk [158.152.85.52]) by hub.freebsd.org (Postfix) with SMTP id 9870114A0E for ; Mon, 11 Oct 1999 17:38:06 -0700 (PDT) (envelope-from dev.null@funbox.demon.co.uk) Received: from funbox.demon.co.uk, ID 3802270B-0731, Mon, 11 Oct 1999 18:06:03 UTC To: freebsd-hackers@freebsd.org From: dev.null@funbox.demon.co.uk (do not use this address) X-Date: Mon, 11 Oct 1999 19:06:03 +0100 Subject: Re: Single character errors in source files, stop kernel Message-ID: <3802270B.0731@funbox.demon.co.uk> Date: Mon, 11 Oct 1999 19:06:03 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a similar problem. There was a pattern to the changes; one bit was being set (I think it was bit 5) occasionally. It gradually became more frequent, and turned out to be a faulty IDE controller card. Needless to say, I had thought that it was the connector/s, the cable, or the drive, in that order. -- Tim Jackson ------------------------------------------------------------------------ please reply to: t i m . j @ f u n b o x . d e m o n . c o . u k ======================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 18:35:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 1C08014CD0 for ; Mon, 11 Oct 1999 18:35:05 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA32099; Tue, 12 Oct 1999 11:04:50 +0930 (CST) Date: Tue, 12 Oct 1999 11:04:50 +0930 From: Greg Lehey To: Andy Farkas Cc: Steven Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read kills machine Message-ID: <19991012110450.M78191@freebie.lemis.com> References: <199910112202.RAA04761@virtual-voodoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 12 October 1999 at 8:09:40 +1000, Andy Farkas wrote: > > On Mon, 11 Oct 1999, Steven Ames wrote: > >> Could someone define what NMBCLUSTERS is and what it is used for? I've >> seen a lot of cases where increasing it (beyond the default 1024?) has >> helped systems be more stable, but what is it? >> > > Here is an informative email from David Greenman: > > ----snip---- What mailer are you using? It didn't quote the "From " at the beginning of the message, so David's message appeared as a separate message. If you're looking for it, sort your messages in mailbox order and it'll be the next message after Andy's original. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 18:40: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 8B41A14C4E for ; Mon, 11 Oct 1999 18:39:58 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id UAA02029; Mon, 11 Oct 1999 20:39:11 -0500 (CDT) Date: Mon, 11 Oct 1999 20:39:11 -0500 From: "Matthew D. Fuller" To: Greg Lehey Cc: Andy Farkas , Steven Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read kills machine Message-ID: <19991011203911.G4124@futuresouth.com> References: <199910112202.RAA04761@virtual-voodoo.com> <19991012110450.M78191@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <19991012110450.M78191@freebie.lemis.com> X-OS: FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 12, 1999 at 11:04:50AM +0930, a little birdie told me that Greg Lehey remarked > > What mailer are you using? It didn't quote the "From " at the > beginning of the message, so David's message appeared as a separate > message. If you're looking for it, sort your messages in mailbox > order and it'll be the next message after Andy's original. He appears to be using Pine, and it quoted it just fine for me. And I do believe we're both using the same MUA, so I don't know where it burped on the way to you. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ FutureSouth Communications | ISPHelp ISP Consulting "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 19:12:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 2234C14CC1 for ; Mon, 11 Oct 1999 19:12:29 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA32433; Tue, 12 Oct 1999 11:42:11 +0930 (CST) Date: Tue, 12 Oct 1999 11:42:11 +0930 From: Greg Lehey To: "Matthew D. Fuller" Cc: Andy Farkas , Steven Ames , freebsd-hackers@FreeBSD.ORG Subject: Unquoted mail (was: aio_read kills machine) Message-ID: <19991012114211.O78191@freebie.lemis.com> References: <199910112202.RAA04761@virtual-voodoo.com> <19991012110450.M78191@freebie.lemis.com> <19991011203911.G4124@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991011203911.G4124@futuresouth.com> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 11 October 1999 at 20:39:11 -0500, Matthew D. Fuller wrote: > On Tue, Oct 12, 1999 at 11:04:50AM +0930, a little birdie told me > that Greg Lehey remarked >> >> What mailer are you using? It didn't quote the "From " at the >> beginning of the message, so David's message appeared as a separate >> message. If you're looking for it, sort your messages in mailbox >> order and it'll be the next message after Andy's original. > > He appears to be using Pine, and it quoted it just fine for me. > And I do believe we're both using the same MUA, so I don't know where it > burped on the way to you. It doesn't have anything to do with the MUA. The message arrived here without a > in front of the 'From ' at the beginning of the line, which is an indication that it's a new message. But it's interesting that it didn't happen to everybody. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 19:15:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 7531414CC1 for ; Mon, 11 Oct 1999 19:15:35 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FJG007IWWXN1N@mta4.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Mon, 11 Oct 1999 21:15:24 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id VAA23100; Mon, 11 Oct 1999 21:14:33 -0500 (CDT envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Mon, 11 Oct 1999 21:14:33 -0500 From: Chris Costello Subject: Re: Unquoted mail (was: aio_read kills machine) In-reply-to: <19991012114211.O78191@freebie.lemis.com> To: Greg Lehey Cc: "Matthew D. Fuller" , Andy Farkas , Steven Ames , freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991011211433.H19110@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <199910112202.RAA04761@virtual-voodoo.com> <19991012110450.M78191@freebie.lemis.com> <19991011203911.G4124@futuresouth.com> <19991012114211.O78191@freebie.lemis.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 12, 1999, Greg Lehey wrote: > It doesn't have anything to do with the MUA. The message arrived here > without a > in front of the 'From ' at the beginning of the line, > which is an indication that it's a new message. But it's interesting > that it didn't happen to everybody. Some MTA between him and me (his mail server, calldei.com's mail server, or my fetchmail) has quoted it on my message. > Greg -- |Chris Costello |State-of-the-art: What we could do with enough money. `----------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 21:12:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt011n66.san.rr.com (dt011n66.san.rr.com [204.210.13.102]) by hub.freebsd.org (Postfix) with ESMTP id A861514F63 for ; Mon, 11 Oct 1999 21:12:29 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n66.san.rr.com (8.9.3/8.8.8) with ESMTP id VAA20221; Mon, 11 Oct 1999 21:12:24 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <3802B527.CB34008C@gorean.org> Date: Mon, 11 Oct 1999 21:12:23 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT-0927 i386) X-Accept-Language: en MIME-Version: 1.0 To: dg@root.com Cc: FreeBSD-hackers@FreeBSD.ORG Subject: Re: SMP + fxp0 wierdness References: <199910120006.RAA15131@implode.root.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman wrote: > > >> So if this problem is NOT related to specific hardware, how can we get > >> the driver fixed? > > > >Talk to the maintainer (David). We've offered him cores and kernels > >before. Alternatively, you'll need to experiment with your setup to > >determine what characterises the failures and help David out with more > >data. > > Hotmail has troubleshooted the problem down to the NCR controller. It > appears that the problem only occurs when using one of those. If they plug > in an Adaptec 2940 and use it instead of the onboard NCR then the problems > disappear. Well that's not good, since I have almost convinced my boss to replace the crappy IDE drives on our shiny new Intel N440BX mb's with scsi drives since the controller is built in. :-/ Does this look like a soluble problem, or is it just going to be a case of "don't do that?" Anything I can do to help mail me and let me know. 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 Mon Oct 11 21:17:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 436F914F63 for ; Mon, 11 Oct 1999 21:17:49 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA04018; Mon, 11 Oct 1999 21:08:57 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910120408.VAA04018@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Cc: dg@root.com, FreeBSD-hackers@FreeBSD.ORG Subject: Re: SMP + fxp0 wierdness In-reply-to: Your message of "Mon, 11 Oct 1999 21:12:23 PDT." <3802B527.CB34008C@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Oct 1999 21:08:57 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well that's not good, since I have almost convinced my boss to replace > the crappy IDE drives on our shiny new Intel N440BX mb's with scsi > drives since the controller is built in. :-/ Does this look like a > soluble problem, or is it just going to be a case of "don't do that?" > Anything I can do to help mail me and let me know. You could try turning on DMA and discovering that these drives aren't _that_ shitty. 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 Oct 11 23:26: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a1-3a123.neo.rr.com [24.93.180.123]) by hub.freebsd.org (Postfix) with ESMTP id 1AAD614E6A; Mon, 11 Oct 1999 23:25:58 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA15746; Tue, 12 Oct 1999 02:25:27 -0400 Date: Tue, 12 Oct 1999 02:25:27 -0400 (EDT) From: Mike Nowlin To: Chris Costello Cc: Laurence Berland , Robert Sexton , nsayer@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: CFD: "bogomips" CPU performance metric In-Reply-To: <19991010195854.C15135@holly.calldei.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 > I disagree. BogoMIPS is a completely meaningless measurement > and does not belong in our source tree as it will only produce > repository bloat. I would agree.. BogoMIPS actually stands for "Bogus, Misleading Indication of Processor Speed"... In an old Linux Journal article I have (will dig it up upon request), it describes how BogoMIPS is calculated -- it's VERY processor-dependant, and only really (sort of) useful for comparing motherboards with the same processor on them..... Switch from an Intel 486/66 to an AMD 486/100, and the numbers do NOT match up to what you'd think.... And if you change to a Pentium, forget it. The biggest thing it's good for is as an ego-booster.... Of course, my dual-PII/450 box has a bigger BogoMIPS rating than any machine at work.. :) --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 11 23:32:59 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 EF5F8152AF for ; Mon, 11 Oct 1999 23:32:51 -0700 (PDT) (envelope-from singuru@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 MAA11059 for ; Tue, 12 Oct 1999 12:02:07 +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 MAA29171 for <@vayu:freebsd-hackers@FreeBSD.ORG>; Tue, 12 Oct 1999 12:02:47 +0500 (GMT) Message-ID: <9910121209.AA23161@tagore.wipinfo.soft.net> Subject: getsockopt not working?? To: freebsd-hackers@FreeBSD.ORG, linux-net@vger.rutgers.edu Date: Tue, 12 Oct 1999 12:08:50 +0530 (IST) From: "S.RadhaKrishna" Reply-To: singuru@wipinfo.soft.net Return-Reply-To: singuru@wipinfo.soft.net Location: Wipro Infotech, Mission Rd., Bangalore India X-Mailer: ELM [version 2.4 PL23] 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 using getsockopt to get IP_MULTICAST_TTL. But it always returns ttl as 0. It doesn't fail either. Here is the call I'm using : ----------- int get_ttl=0; u_char ttlSize=0; if (getsockopt(sockfd, IPPROTO_IP, IP_MULTICAST_TTL, (void*)&get_ttl,(int *)&ttlSize) < 0) { printf("ttl.c:get ttl failed\n"); perror("getsockopt"); exit(1); } ---------- I used setsockopt to set ttl value. It works fine (I saw the packets on the network using a sniffer). But getsockopt returns always 0. Any help on this would be appreciated. regards radha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 1:22:21 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 BF8C214DC3 for ; Tue, 12 Oct 1999 01:22:12 -0700 (PDT) (envelope-from sharadj@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 NAA15584; Tue, 12 Oct 1999 13:52:36 +0500 (GMT) Received: from rishabh.wipinfo.soft.net (root@rishabh.wipinfo.soft.net [192.168.2.5]) by vayu.wipinfo.soft.net (8.9.3/8.9.3) with ESMTP id NAA09456; Tue, 12 Oct 1999 13:53:17 +0500 (GMT) Received: from rishabh.wipinfo.soft.net (sharadj@rishabh.wipinfo.soft.net [192.168.2.5]) by rishabh.wipinfo.soft.net (8.9.3/8.9.3) with SMTP id OAA05234; Tue, 12 Oct 1999 14:04:38 +0530 Date: Tue, 12 Oct 1999 14:04:36 +0530 (IST) From: Sharad Joshi To: "S.RadhaKrishna" Cc: freebsd-hackers@FreeBSD.ORG, linux-net@vger.rutgers.edu Subject: Re: getsockopt not working?? In-Reply-To: <9910121210.AA23607@tagore.wipinfo.soft.net> 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, 12 Oct 1999, S.RadhaKrishna wrote: + hi, + I'm using getsockopt to get IP_MULTICAST_TTL. But it always returns ttl + as 0. It doesn't fail either. + Here is the call I'm using : + ----------- + int get_ttl=0; + u_char ttlSize=0; ^^^^^^^^^ 'Coz of this i presume. Should'nt this be 4? Sharad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 2:37:32 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 593D01529B for ; Tue, 12 Oct 1999 02:37:07 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id QAA51499 for ; Tue, 12 Oct 1999 16:36:39 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 12 Oct 1999 16:36:39 +0700 (NSS) From: Max Khon To: hackers@freebsd.org Subject: FreeBSD CVS mirror 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! maybe i'm posting into wrong list, but how is FreeBSD CVS repository mirrored? We probably will have an opportunity to set up local FreeBSD mirror here (we do not have space for full mirror but some parts, including CVS repository is desired) /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 3:11:15 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 0208115005 for ; Tue, 12 Oct 1999 03:11:03 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id LAA63413; Tue, 12 Oct 1999 11:04:01 +0100 (BST) (envelope-from joe) Date: Tue, 12 Oct 1999 11:04:00 +0100 From: Josef Karthauser To: Max Khon Cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD CVS mirror Message-ID: <19991012110359.J70248@florence.pavilion.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, 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 Tue, Oct 12, 1999 at 04:36:39PM +0700, Max Khon wrote: > hi, there! > > maybe i'm posting into wrong list, but how is FreeBSD > CVS repository mirrored? > We probably will have an opportunity to set up local FreeBSD mirror here > (we do not have space for full mirror but some parts, including > CVS repository is desired) > > /fjoe Take a look at the /usr/ports/net/cvsup-mirror port. It sets up you machine to act as a mirror (using the 'cvsup' program to get the distribution on a regular basis, and the 'cvsupd' program to allow people to connect and update their source tree.) 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 Tue Oct 12 3:15:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id C1B8115005 for ; Tue, 12 Oct 1999 03:15:40 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id DAA16112; Tue, 12 Oct 1999 03:14:54 -0700 (PDT) Message-Id: <199910121014.DAA16112@implode.root.com> To: Doug Cc: FreeBSD-hackers@FreeBSD.ORG Subject: Re: SMP + fxp0 wierdness In-reply-to: Your message of "Mon, 11 Oct 1999 21:12:23 PDT." <3802B527.CB34008C@gorean.org> From: David Greenman Reply-To: dg@root.com Date: Tue, 12 Oct 1999 03:14:54 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >David Greenman wrote: >> >> >> So if this problem is NOT related to specific hardware, how can we get >> >> the driver fixed? >> > >> >Talk to the maintainer (David). We've offered him cores and kernels >> >before. Alternatively, you'll need to experiment with your setup to >> >determine what characterises the failures and help David out with more >> >data. >> >> Hotmail has troubleshooted the problem down to the NCR controller. It >> appears that the problem only occurs when using one of those. If they plug >> in an Adaptec 2940 and use it instead of the onboard NCR then the problems >> disappear. > > Well that's not good, since I have almost convinced my boss to replace >the crappy IDE drives on our shiny new Intel N440BX mb's with scsi >drives since the controller is built in. :-/ Does this look like a >soluble problem, or is it just going to be a case of "don't do that?" >Anything I can do to help mail me and let me know. Intel generally makes good stuff. On the other hand, I'm not too happy with the NCR/Symbios support in FreeBSD...the conversion to CAM wasn't all that great and the driver really needs a rewrite. I wouldn't personally put a machine with an NCR/Symbios into production - I have just too much negative history with it. I don't understand why some machines are having this problem with the Intel Pro/100B/100+ and (most) others never do. All indications right now is that it is a DMA corruption problem of some kind, but I don't have any clue what might be causing it. I don't think it is a software bug, but it's conceivable that the problem could be worked around with software if I knew what was causing it. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 3:55:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gwfiifo.fiifo.u-psud.fr (gwfiifo.fiifo.u-psud.fr [193.55.37.3]) by hub.freebsd.org (Postfix) with ESMTP id 568E614E50 for ; Tue, 12 Oct 1999 03:55:48 -0700 (PDT) (envelope-from ghane@fiifo.u-psud.fr) Received: from dahlia.fiifo.u-psud.fr (dahlia.fiifo.u-psud.fr [193.55.37.7]) by gwfiifo.fiifo.u-psud.fr (8.9.1a/jtpda-5.3.1) with ESMTP id MAA09020 ; Tue, 12 Oct 1999 12:56:15 +0200 Received: from (ghane@localhost) by dahlia.fiifo.u-psud.fr (8.9.1a/jtpda-5.3.1) id MAA38190 ; Tue, 12 Oct 1999 12:56:14 +0200 Date: Tue, 12 Oct 1999 12:56:14 +0200 From: Sameh Ghane To: Max Khon Cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD CVS mirror Message-ID: <19991012125614.A34334@fiifo.u-psud.fr> 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 Tue, Oct 12, 1999 at 04:36:39PM +0700, Max Khon wrote: > hi, there! > > maybe i'm posting into wrong list, but how is FreeBSD > CVS repository mirrored? > We probably will have an opportunity to set up local FreeBSD mirror here > (we do not have space for full mirror but some parts, including > CVS repository is desired) For the set up of mirrors, send your request to: admin@freebsd.org. -- Sameh Ghane. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 7:32:14 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 6A5EA15753 for ; Tue, 12 Oct 1999 07:32:11 -0700 (PDT) (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 KAA01008 for ; Tue, 12 Oct 1999 10:32:06 -0400 (EDT) Date: Tue, 12 Oct 1999 10:32:00 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: Search a symbol in the source tree 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 Can anyone suggest me a way of searching symbols in the entire /usr/src tree? I normally use grep */*. But grep does not work recursively, right? Something like a small shell script may do this. Thanks a lot. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 7:43:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id C3455157E4 for ; Tue, 12 Oct 1999 07:43:07 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11b38q-0005uu-00; Tue, 12 Oct 1999 08:43:04 -0600 Message-ID: <380348F6.FFC43221@softweyr.com> Date: Tue, 12 Oct 1999 08:43:02 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Matthew D. Fuller" Cc: Greg Lehey , Andy Farkas , Steven Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read kills machine References: <199910112202.RAA04761@virtual-voodoo.com> <19991012110450.M78191@freebie.lemis.com> <19991011203911.G4124@futuresouth.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew D. Fuller" wrote: > > On Tue, Oct 12, 1999 at 11:04:50AM +0930, a little birdie told me > that Greg Lehey remarked > > > > What mailer are you using? It didn't quote the "From " at the > > beginning of the message, so David's message appeared as a separate > > message. If you're looking for it, sort your messages in mailbox > > order and it'll be the next message after Andy's original. > > He appears to be using Pine, and it quoted it just fine for me. > And I do believe we're both using the same MUA, so I don't know where it > burped on the way to you. It blew it for me, too. I wonder if the MTA might have something to do with it. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 7:59:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id D453A1515F for ; Tue, 12 Oct 1999 07:59:15 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id JAA15055; Tue, 12 Oct 1999 09:59:04 -0500 (CDT) (envelope-from dan) Date: Tue, 12 Oct 1999 09:59:04 -0500 From: Dan Nelson To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Search a symbol in the source tree Message-ID: <19991012095904.A8849@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Oct 12), Zhihui Zhang said: > Can anyone suggest me a way of searching symbols in the entire /usr/src > tree? I normally use grep */*. But grep does not work recursively, right? > Something like a small shell script may do this. Thanks a lot. If you use zsh, it has a "recursive glob": grep draw_mouse **/*.c You could also use find | xargs: find . -name "*.c" | xargs grep draw_mouse Or you could use gtags/global: gtags global -gx "draw_mouse" If you're really looking for the source file that defines a symbol, global is the way to go. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 8: 0:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bantu.cl.msu.edu (bantu.cl.msu.edu [35.8.3.18]) by hub.freebsd.org (Postfix) with ESMTP id D777C1515F for ; Tue, 12 Oct 1999 08:00:47 -0700 (PDT) (envelope-from dervish@bantu.cl.msu.edu) Received: (from dervish@localhost) by bantu.cl.msu.edu (8.9.3/8.9.3) id KAA34683; Tue, 12 Oct 1999 10:59:11 -0400 (EDT) (envelope-from dervish) Date: Tue, 12 Oct 1999 10:59:11 -0400 From: bush doctor To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Search a symbol in the source tree Message-ID: <19991012105911.A34544@bantu.cl.msu.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Zhihui Zhang on Tue, Oct 12, 1999 at 10:32:00AM -0400 X-Operating-System: FreeBSD 4.0-CURRENT i386 X-PGP-Fingerprint: 35 95 F8 63 DA 5B 32 51 8F A9 AC 3C B4 74 F3 BA WWW-Home-Page: http://www.msu.edu/~ikhala Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of da blue Zhihui Zhang aka (zzhang@cs.binghamton.edu) said: > > Can anyone suggest me a way of searching symbols in the entire /usr/src > tree? I normally use grep */*. But grep does not work recursively, right? > Something like a small shell script may do this. Thanks a lot. Have you taken a look at global, gtags, or htags. They are part of the base system. Also 'http://lxr.linux.no/freebsd/source' is rather helpful ... > > -Zhihui > > > #:^) -- So ya want ta here da roots? Dem that feels it knows it ... bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 8:52:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 91421151B5; Tue, 12 Oct 1999 08:52:42 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id KAA16014; Tue, 12 Oct 1999 10:52:38 -0500 (CDT) From: Mohit Aron Message-Id: <199910121552.KAA16014@cs.rice.edu> Subject: paper on fine-grained OS timers To: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org, tech-net@netbsd.org Date: Tue, 12 Oct 1999 10:52:38 -0500 (CDT) X-Mailer: ELM [version 2.4 PL25] 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'd like to tell the BSD community about my paper entitled "Soft timers: efficient microsecond software timer support for network processing" that's going to appear in SOSP 1999. The abstract for the paper is attached below. The gzip'd postcript for the paper can be downloaded from: http://www.cs.rice.edu/~aron/papers/soft-timers.ps.gz Thanks, - Mohit Abstract: This paper proposes and evaluates soft timers, a new operating system facility that allows the efficient scheduling of software events at a granularity down to tens of microseconds. Soft timers can be used to avoid interrupts and reduce context switches associated with network processing without sacrificing low communication delays. More specifically, soft timers enable transport protocols like TCP to efficiently perform rate-based clocking of packet transmissions. Experiments show that rate-based clocking can improve HTTP response time over connections with high bandwidth-delay products by up to 89% and that soft timers allow a server to employ rate-based clocking with little CPU overhead (2--6%) at high aggregate bandwidths. Soft timers can also be used to perform network polling, which eliminates network interrupts and increases the memory access locality of the network subsystem without sacrificing delay. Experiments show that this technique can improve the throughput of a Web server by up to 25%. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 8:57:52 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 27B6215A6D for ; Tue, 12 Oct 1999 08:57:37 -0700 (PDT) (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 JAA37638 for ; Tue, 12 Oct 1999 09:57:36 -0600 (MDT) (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 JAA96469 for ; Tue, 12 Oct 1999 09:58:21 -0600 (MDT) Message-Id: <199910121558.JAA96469@harmony.village.org> To: hackers@freebsd.org Subject: Symbols and klds Date: Tue, 12 Oct 1999 09:58:21 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How does one tell ddb about dynamic modules? I've had a couple of crashes in my code where I've needed symbols from things dynamically loaded... Does gdb grok them any better? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 9: 3:35 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 784201523D; Tue, 12 Oct 1999 09:03:31 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p25-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.154]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id BAA13136; Wed, 13 Oct 1999 01:03:11 +0900 (JST) Message-ID: <3803269D.A4B94379@newsguy.com> Date: Tue, 12 Oct 1999 21:16:29 +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: "Brian F. Feldman" Cc: Mike Smith , Andy Farkas , Chris Costello , freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read kills machine References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brian F. Feldman" wrote: > > I'd like everyone to note that for now, if you are providing user-access > to a 4.0 box (and you don't absolutely trust your users), you should be > using the RLIMIT_SBSIZE for limiting network memory usage just as > you use other RLIMITs for memory limiting, etc. Ah, so *that* is what RLIMIT_SBSIZE is! I don't recall the files in the commit message... did it get documented in login.conf's man page? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 9: 4: 6 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 560E315ABC for ; Tue, 12 Oct 1999 09:03:52 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p25-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.154]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id BAA13197; Wed, 13 Oct 1999 01:03:32 +0900 (JST) Message-ID: <3803367A.BA9B7395@newsguy.com> Date: Tue, 12 Oct 1999 22:24:10 +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: Gustavo V G C Rios Cc: hackers@FreeBSD.ORG Subject: Re: file system system calls References: <380145BD.A4C04C01@ddsecurity.com.br> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gustavo V G C Rios wrote: > > May anyone here point me where in the source tree i can see file system > API implemented, like open, write, close, etc..... I strongly suggest you start by buying The Design and Implementation of 4.4 BSD, and reading it. You'll make *much* more progress this way. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 10:33: 8 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 BDD1A15C43 for ; Tue, 12 Oct 1999 10:33:03 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p05-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.134]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id CAA25438; Wed, 13 Oct 1999 02:32:59 +0900 (JST) Message-ID: <38036C65.D5B1BD3E@newsguy.com> Date: Wed, 13 Oct 1999 02:14:13 +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: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Search a symbol in the source tree References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zhihui Zhang wrote: > > Can anyone suggest me a way of searching symbols in the entire /usr/src > tree? I normally use grep */*. But grep does not work recursively, right? > Something like a small shell script may do this. Thanks a lot. find /usr/src -name \*.\[ch] -print | xargs grep pattern or similar. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 12:51:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 021A514BED; Tue, 12 Oct 1999 12:51:15 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E73AD1CD487; Tue, 12 Oct 1999 12:51:15 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Tue, 12 Oct 1999 12:51:15 -0700 (PDT) From: Kris Kennaway To: bush doctor Cc: Zhihui Zhang , freebsd-hackers@FreeBSD.ORG Subject: Re: Search a symbol in the source tree In-Reply-To: <19991012105911.A34544@bantu.cl.msu.edu> 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, 12 Oct 1999, bush doctor wrote: > Have you taken a look at global, gtags, or htags. They are part of > the base system. Also 'http://lxr.linux.no/freebsd/source' is rather > helpful ... or the glimpse port. or grep -R, which is recursive grep. Kris ---- XOR for AES -- join the campaign! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 14:40:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by hub.freebsd.org (Postfix) with SMTP id E260214DE9 for ; Tue, 12 Oct 1999 14:40:07 -0700 (PDT) (envelope-from rohitd@zubin.dnrc.bell-labs.com) Received: from zubin.dnrc.bell-labs.com ([135.180.130.56]) by crufty; Tue Oct 12 17:39:07 EDT 1999 Received: (from rohitd@localhost) by zubin.dnrc.bell-labs.com (8.9.3/8.9.3) id RAA08377 for hackers@freebsd.org; Tue, 12 Oct 1999 17:39:06 -0400 (EDT) Date: Tue, 12 Oct 1999 17:39:06 -0400 (EDT) From: Rohit Dube Message-Id: <199910122139.RAA08377@zubin.dnrc.bell-labs.com> To: hackers@freebsd.org Subject: threaded applications on freebsd 3.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Looking through the mailing list archives, support for threaded applications wasn't quite clear to me so I ask here. I have a threaded application working on Red Hat Linux 6.0 which uses pthreads. I was trying to port it over to FreeBSD 3.3 on a 2 processor intel machine. Not having done threaded work on FreeBSD before, I need to figure out what compiler-options/libraries/kernel to use for the port - a) What do I need to do, to compile an application which uses pthreads on freebsd 3.3. The gcc (2.7.2.3) man page suggests that it should be invoked with -pthread. Is that sufficient or do I also need to recompile the standard libraries with DTHREAD_SAFE? How about with gcc295 (which comes on the 3.3 CD), it doesn't seem to have this option at all, going by the man page. b) The mailing list archives seem to suggest that on freebsd (at least upto 3.2), a (p)thread doesn't map to a kernel thread. I.e scheduling of (p)threads in a process is done in user space. Is there any way at all to map a user-level thread to a kernel thread 1:1? Again there seems to be -kthread option for gcc (2.7.2.3) but none for gcc295. c) Is the generic 3.3 default kernel threaded and able to run a multiprocessor machine or do I need to build a custom kernel with specific options. Sorry my freebsd is a bit rusty as I have been away for more than a year. Thanks, --rohit. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 14:55:49 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 2614C1516B for ; Tue, 12 Oct 1999 14:55:37 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id OAA16168; Tue, 12 Oct 1999 14:55:19 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Tue, 12 Oct 1999 14:55:18 -0700 Date: Tue, 12 Oct 1999 14:55:18 -0700 (PDT) From: Kip Macy X-Sender: kip@luna To: Rohit Dube Cc: hackers@freebsd.org Subject: Re: threaded applications on freebsd 3.3 In-Reply-To: <199910122139.RAA08377@zubin.dnrc.bell-labs.com> 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: rohitd@dnrc.bell-labs.com,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 On Tue, 12 Oct 1999, Rohit Dube wrote: > Hi, > > Looking through the mailing list archives, support for threaded > applications wasn't quite clear to me so I ask here. I have a > threaded application working on Red Hat Linux 6.0 which uses pthreads. > I was trying to port it over to FreeBSD 3.3 on a 2 processor intel machine. > Not having done threaded work on FreeBSD before, I need to figure out what > compiler-options/libraries/kernel to use for the port - The linux version will work out of the box - however you will have to add a couple of options to your kernel config file to keep syslog from overwhelming you with bogus warnings. > > a) What do I need to do, to compile an application which uses pthreads > on freebsd 3.3. The gcc (2.7.2.3) man page suggests that it should > be invoked with -pthread. Is that sufficient or do I also need to recompile > the standard libraries with DTHREAD_SAFE? How about with gcc295 > (which comes on the 3.3 CD), it doesn't seem to have this option > at all, going by the man page. -pthread will work just fine. FreeBSD does not have _r calls for everything yet. Keep in mind that Linux's _r calls are not POSIX compliant, i.e. they are different from every other UNIX with threads. > b) The mailing list archives seem to suggest that on freebsd (at least > upto 3.2), a (p)thread doesn't map to a kernel thread. I.e scheduling > of (p)threads in a process is done in user space. Is there any way at > all to map a user-level thread to a kernel thread 1:1? Again there seems > to be -kthread option for gcc (2.7.2.3) but none for gcc295. Don't know - for I/O bound activity kernel threads are a really bad idea. > c) Is the generic 3.3 default kernel threaded and able to run a multiprocessor > machine or do I need to build a custom kernel with specific options. You will need to rebuild for SMP. See LINT for details. > > Sorry my freebsd is a bit rusty as I have been away for more than a year. > Thanks, > --rohit. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 16: 0:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 6475515387 for ; Tue, 12 Oct 1999 16:00:48 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id TAA66794; Tue, 12 Oct 1999 19:00:16 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Tue, 12 Oct 1999 19:00:16 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: "Daniel C. Sobral" Cc: Mike Smith , Andy Farkas , Chris Costello , freebsd-hackers@FreeBSD.org Subject: Re: aio_read kills machine In-Reply-To: <3803269D.A4B94379@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 Tue, 12 Oct 1999, Daniel C. Sobral wrote: > "Brian F. Feldman" wrote: > > > > I'd like everyone to note that for now, if you are providing user-access > > to a 4.0 box (and you don't absolutely trust your users), you should be > > using the RLIMIT_SBSIZE for limiting network memory usage just as > > you use other RLIMITs for memory limiting, etc. > > Ah, so *that* is what RLIMIT_SBSIZE is! I don't recall the files in > the commit message... did it get documented in login.conf's man > page? No, I got limits.1 but not login.conf.5. Would you like to do it, or shall I? > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "I always feel generous when I'm in the inner circle of a > conspiracy to subvert the world order and, with a small group of > allies, just defeated an alien invasion. Maybe I should value myself > a little more?" > > -- 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 Tue Oct 12 17: 7:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id E8B4D14D5C for ; Tue, 12 Oct 1999 17:07:49 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA40530; Wed, 13 Oct 1999 09:37:41 +0930 (CST) Date: Wed, 13 Oct 1999 09:37:41 +0930 From: Greg Lehey To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Search a symbol in the source tree Message-ID: <19991013093741.S78191@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 12 October 1999 at 10:32:00 -0400, Zhihui Zhang wrote: > > Can anyone suggest me a way of searching symbols in the entire /usr/src > tree? I normally use grep */*. But grep does not work recursively, right? > Something like a small shell script may do this. Thanks a lot. I use etags for this, in conjunction with Emacs. Like that, I can position the cursor on a word, press Alt-., and it will find the definition for me. It will also search for all occurrences with Alt-S. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 17:41:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D35D01553A for ; Tue, 12 Oct 1999 17:41:30 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA05668; Tue, 12 Oct 1999 17:41:26 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA02730; Tue, 12 Oct 1999 17:41:26 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 12 Oct 1999 17:41:26 -0700 (PDT) Message-Id: <199910130041.RAA02730@vashon.polstra.com> To: ghane@fiifo.u-psud.fr Subject: Re: FreeBSD CVS mirror In-Reply-To: <19991012125614.A34334@fiifo.u-psud.fr> References: <19991012125614.A34334@fiifo.u-psud.fr> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19991012125614.A34334@fiifo.u-psud.fr>, Sameh Ghane wrote: > On Tue, Oct 12, 1999 at 04:36:39PM +0700, Max Khon wrote: > > hi, there! > > > > maybe i'm posting into wrong list, but how is FreeBSD > > CVS repository mirrored? > > We probably will have an opportunity to set up local FreeBSD mirror here > > (we do not have space for full mirror but some parts, including > > CVS repository is desired) > > For the set up of mirrors, send your request to: admin@freebsd.org. That mailing list doesn't exist any more. For CVSup mirrors, send the request to jdp@freebsd.org or hubs@freebsd.org. John Polstra CVSup Mirrormeister -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 17:53:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id B2C5A14A0D for ; Tue, 12 Oct 1999 17:53:35 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 366B51C4F; Tue, 12 Oct 1999 19:56:36 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 27652381A; Tue, 12 Oct 1999 19:56:36 -0400 (EDT) Date: Tue, 12 Oct 1999 19:56:36 -0400 (EDT) From: Bill Fumerola To: John Polstra Cc: ghane@fiifo.u-psud.fr, hackers@freebsd.org Subject: Re: FreeBSD CVS mirror In-Reply-To: <199910130041.RAA02730@vashon.polstra.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, 12 Oct 1999, John Polstra wrote: > > For the set up of mirrors, send your request to: admin@freebsd.org. > > That mailing list doesn't exist any more. For CVSup mirrors, send the > request to jdp@freebsd.org or hubs@freebsd.org. It still exists in some documentation, if I recall. /me goes off to look. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 20:38:31 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 69FA214C32; Tue, 12 Oct 1999 20:38:25 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id XAA21979; Tue, 12 Oct 1999 23:38:23 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id XAA51696; Tue, 12 Oct 1999 23:37:53 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 12 Oct 1999 23:37:53 -0400 (EDT) To: freebsd-alpha@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: alpha scheduling needs some tuning X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14339.64335.748030.108662@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anybody noticed that scheduling appears to be broken on the alpha? On both i386 & alpha, try: echo "main(){for(;;);}" > foo.c cc foo.c /usr/bin/nice -20 ./a.out & ; ./a.out & & watch the programs run in top. You'll notice that on the i386, the non-niced job will get about 2/3 of the cpu & the niced job will get about one third: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 51676 gallatin 94 0 764K 204K RUN 5:37 64.31% 64.31% a.out 51675 gallatin 105 20 764K 204K RUN 2:42 32.71% 32.71% a.out On the alpha, its close to dead even & the nice'd job is actually getting more CPU!: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 76397 gallatin 105 20 1168K 960K RUN 4:10 49.61% 49.61% a.out 76398 gallatin 105 0 1168K 960K RUN 4:38 48.00% 48.00% a.out The i386 (a PII) shows this for kern.clockrate: kern.clockrate: { hz = 100, tick = 10000, tickadj = 5, profhz = 1024, stathz = 128 } And the alpha shows this: kern.clockrate: { hz = 1024, tick = 976, tickadj = 5, profhz = 1024, stathz = 1024 } I fully admit that I don't have a good understanding of the scheduling algorithm. I was hoping somebody who does might be able to suggest a fix. Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 21:12:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id E725214C2F; Tue, 12 Oct 1999 21:12:11 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id VAA19287; Tue, 12 Oct 1999 21:12:04 -0700 (PDT) Message-Id: <199910130412.VAA19287@lestat.nas.nasa.gov> To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: alpha scheduling needs some tuning Reply-To: Jason Thorpe From: Jason Thorpe Date: Tue, 12 Oct 1999 21:12:03 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 12 Oct 1999 23:37:53 -0400 (EDT) Andrew Gallatin wrote: > Has anybody noticed that scheduling appears to be broken on the alpha? > > On both i386 & alpha, try: > > echo "main(){for(;;);}" > foo.c > cc foo.c > /usr/bin/nice -20 ./a.out & ; ./a.out & FWIW, Ross Harvey fixed a whole slew of scheduler bugs in NetBSD that tickled themselves on the Alpha (due to it's high statclock rate). -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 12 22:56:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 46C6314C4F for ; Tue, 12 Oct 1999 22:56:40 -0700 (PDT) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19991013055639.PZLH28137.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com> for ; Tue, 12 Oct 1999 22:56:39 -0700 Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id WAA31178 for freebsd-hackers@freebsd.org; Tue, 12 Oct 1999 22:56:39 -0700 Date: Tue, 12 Oct 1999 22:56:39 -0700 From: Arun Sharma To: freebsd-hackers@freebsd.org Subject: vm_map.h and C++ warnings Message-ID: <19991012225639.A31171@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following patch fixes it. -Arun # diff -u vm_map.h- vm_map.h --- vm_map.h- Tue Oct 12 22:52:10 1999 +++ vm_map.h Tue Oct 12 22:54:58 1999 @@ -229,7 +229,7 @@ #if defined(MAP_LOCK_DIAGNOSTIC) printf("locking map LK_EXCLUPGRADE: 0x%x\n", map); #endif - error = lockmgr(&map->lock, LK_EXCLUPGRADE, (void *)0, p); + error = lockmgr(&map->lock, LK_EXCLUPGRADE, (struct simplelock *)0, p); if (error == 0) map->timestamp++; return error; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 0: 7:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from icon.icon-bg.net (icon-bg.net [212.56.11.2]) by hub.freebsd.org (Postfix) with ESMTP id 6683714C0F for ; Wed, 13 Oct 1999 00:07:14 -0700 (PDT) (envelope-from v0rbiz@icon-bg.net) Received: from plamen (rado.icon-bg.net [212.56.11.4] (may be forged)) by icon.icon-bg.net (8.9.3/8.9.3) with SMTP id KAA28208 for ; Wed, 13 Oct 1999 10:08:01 +0300 Message-ID: <005701bf1551$d7788f80$040b38d4@plamen.icon-bg.net> From: "Victor Ivanov" To: Subject: Re: Search a symbol in the source tree Date: Wed, 13 Oct 1999 10:06:18 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Can anyone suggest me a way of searching symbols in the entire /usr/src >tree? I normally use grep */*. But grep does not work recursively, right? >Something like a small shell script may do this. Thanks a lot. > >-Zhihui > find . -name '*' | xargs grep expression ...or something :) regards, v0rbiz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 0: 9:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.bsb.nutecnet.com.br (mail.bsb.nutecnet.com.br [200.252.253.5]) by hub.freebsd.org (Postfix) with ESMTP id 9696114C0F; Wed, 13 Oct 1999 00:09:46 -0700 (PDT) (envelope-from visi0n@aux-tech.org) Received: from variola.chinatown.org (dl7073-bsb.bsb.nutecnet.com.br [200.252.208.73]) by mail.bsb.nutecnet.com.br (8.8.5/SCA-6.6) with SMTP id FAA29412; Wed, 13 Oct 1999 05:08:12 -0300 (BRA) Date: Tue, 12 Oct 1999 04:11:59 +0000 ( ) From: visi0n X-Sender: visi0n@variola.chinatown.org To: freebsd-net@FreeBSD.ORG Cc: freebsd-hackers@freebsd.org Subject: Isa Ether Devices (ne2000) 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, Im studying the network part of the kernel and trying to found where's the function which do the interruption in the ne2000 isa card when a packet is in the "wire", and what function of the kernel initialize the ne2000 isa card. Thanx =============================================================================== visi0n AUX Technologies www.aux-tech.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 0:14:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 8BDF814E79; Wed, 13 Oct 1999 00:14:27 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id QAA21463; Wed, 13 Oct 1999 16:44:07 +0930 (CST) (envelope-from doconnor@gsoft.com.au) 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: Date: Wed, 13 Oct 1999 16:44:07 +0930 (CST) From: "Daniel O'Connor" To: visi0n Subject: RE: Isa Ether Devices (ne2000) Cc: freebsd-hackers@freebsd.org, freebsd-net@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Oct-99 visi0n wrote: > Hi, Im studying the network part of the kernel and trying to found > where's the function which do the interruption in the ne2000 isa card when > a packet is in the "wire", and what function of the kernel initialize the > ne2000 isa card. Look in /usr/src/sys/i386/isa/if_ed.c You might want to look at something less complex like the fxp driver (/usr/src/sys/pci/if_fxp.c). It has less cruft about PCMCIA and other junk. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 0:23:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.atl.bellsouth.net (mail2.atl.bellsouth.net [205.152.0.22]) by hub.freebsd.org (Postfix) with ESMTP id 1DB7514E79 for ; Wed, 13 Oct 1999 00:23:40 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-216-78-101-24.asm.bellsouth.net [216.78.101.24]) by mail2.atl.bellsouth.net (3.3.4alt/0.75.2) with ESMTP id DAA01033 for ; Wed, 13 Oct 1999 03:23:38 -0400 (EDT) Received: from wghicks.bellsouth.net (IDENT:wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id DAA05354 for ; Wed, 13 Oct 1999 03:29:28 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199910130729.DAA05354@bellsouth.net> To: freebsd-hackers@freebsd.org Subject: --enable-haifa Date: Wed, 13 Oct 1999 03:29:28 -0400 From: W Gerald Hicks Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just curious what effect using the --enable-haifa flag for building gcc-2.95.1/x86 would have so I did a comparison using the Dhrystone benchmark from /usr/ports/benchmarks/bytebench. This was run on a Ziatech 200Mhz Pentium cPCI system. I don't know if this is really worth further testing but it seems interesting. Cheers, Jerry Hicks wghicks@bellsouth.net stock -current (1999/10/05) gcc ============================================================================= Dhrystone 2 without register variables 321955.8 lps (10 secs, 6 samples) BASELINE RESULT INDEX Dhrystone 2 without register variables 22366.3 321955.8 14.4 i386-portbld-FreeBSD4.0 --enable-haifa ============================================================================= Dhrystone 2 without register variables 323767.4 lps (10 secs, 6 samples) BASELINE RESULT INDEX Dhrystone 2 without register variables 22366.3 323767.4 14.5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 0:28:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail3.atl.bellsouth.net (mail3.atl.bellsouth.net [205.152.0.38]) by hub.freebsd.org (Postfix) with ESMTP id 53B0E14E79 for ; Wed, 13 Oct 1999 00:28:37 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-216-78-101-24.asm.bellsouth.net [216.78.101.24]) by mail3.atl.bellsouth.net (3.3.4alt/0.75.2) with ESMTP id DAA04887; Wed, 13 Oct 1999 03:28:25 -0400 (EDT) Received: from wghicks.bellsouth.net (IDENT:wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id DAA05466; Wed, 13 Oct 1999 03:34:25 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199910130734.DAA05466@bellsouth.net> To: "Victor Ivanov" Cc: freebsd-hackers@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: Search a symbol in the source tree In-reply-to: Your message of "Wed, 13 Oct 1999 10:06:18 +0200." <005701bf1551$d7788f80$040b38d4@plamen.icon-bg.net> Date: Wed, 13 Oct 1999 03:34:25 -0400 From: W Gerald Hicks Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I find it ironic that nobody has suggested global yet; That sure would make a nice port, especially since we could easily recommend gozilla as a nice way to browse and search the source tree. Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 1:30:50 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 A7FA014DDB for ; Wed, 13 Oct 1999 01:30:45 -0700 (PDT) (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 JAA98248; Wed, 13 Oct 1999 09:33:05 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 13 Oct 1999 09:33:05 +0100 (BST) From: Doug Rabson To: Warner Losh Cc: hackers@freebsd.org Subject: Re: Symbols and klds In-Reply-To: <199910121558.JAA96469@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 Tue, 12 Oct 1999, Warner Losh wrote: > > How does one tell ddb about dynamic modules? I've had a couple of > crashes in my code where I've needed symbols from things dynamically > loaded... Does gdb grok them any better? > I thought ddb was supposed to know about them already but perhaps that only works for pre-loaded modules. GDB can be forced to see them but its tricky - Greg Lehey has some gdb macros to help him get vinum into GDB. One thing I would like to do with GDB (if I ever get to it) is to fake up the data structures which it expects to see from ld.so so that it can walk our module list directly. -- 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 Wed Oct 13 3:57:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ockle.nanoteq.co.za (ockle.nanoteq.co.za [196.37.91.54]) by hub.freebsd.org (Postfix) with ESMTP id 92A2515401 for ; Wed, 13 Oct 1999 03:56:57 -0700 (PDT) (envelope-from jkruger@oskar.nanoteq.co.za) Received: from oskar.nanoteq.co.za (localhost.nanoteq.co.za [127.0.0.1]) by ockle.nanoteq.co.za (8.9.3/8.9.3) with ESMTP id MAA27567 for ; Wed, 13 Oct 1999 12:55:29 +0200 (SAST) (envelope-from jkruger@oskar.nanoteq.co.za) Message-ID: <3804651F.1F173045@oskar.nanoteq.co.za> Date: Wed, 13 Oct 1999 12:55:27 +0200 From: Johan Kruger Reply-To: jkruger@oskar.nanoteq.co.za Organization: Nanoteq X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Generating interrupts ? Content-Type: multipart/mixed; boundary="------------434C544169A81A5471FA9F12" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------434C544169A81A5471FA9F12 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit In DOS it's possible to load the AX register with DA8C and generate a int 15, which will return the BIOS version string and the chipset identification int CL register. How do i do it in FreeBSD, and how do i generate a interrupt for that manner ? Greeting fellow FreeBSD users, by the way, 4.0-CURRENT builds a release just fine, and it's Linux emulator (sorry for the word emulator ) is exellent, try it. --------------434C544169A81A5471FA9F12 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:;0 fn:Johan Kruger end:vcard --------------434C544169A81A5471FA9F12-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 4: 8:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id AFBAC14F2E for ; Wed, 13 Oct 1999 04:08:44 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id OAA47074; Wed, 13 Oct 1999 14:06:52 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Date: Wed, 13 Oct 1999 14:06:52 +0300 (EEST) From: Narvi To: Johan Kruger Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Generating interrupts ? In-Reply-To: <3804651F.1F173045@oskar.nanoteq.co.za> 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, 13 Oct 1999, Johan Kruger wrote: > In DOS it's possible to load the AX register with DA8C and generate a > int 15, which will return the BIOS version string and the chipset > identification int CL register. How do i do it in FreeBSD, and how do i > generate a interrupt for that manner ? > You don't. Well, at least not without VM86. Why do you want it? (and what about freebsd-alpha mchines?) > Greeting fellow FreeBSD users, by the way, 4.0-CURRENT builds a release > just fine, and it's Linux emulator (sorry for the word emulator ) is > exellent, try it. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 4:16:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ockle.nanoteq.co.za (ockle.nanoteq.co.za [196.37.91.54]) by hub.freebsd.org (Postfix) with ESMTP id 0DF8914CF4 for ; Wed, 13 Oct 1999 04:16:20 -0700 (PDT) (envelope-from jkruger@oskar.nanoteq.co.za) Received: from oskar.nanoteq.co.za (localhost.nanoteq.co.za [127.0.0.1]) by ockle.nanoteq.co.za (8.9.3/8.9.3) with ESMTP id NAA29163; Wed, 13 Oct 1999 13:14:58 +0200 (SAST) (envelope-from jkruger@oskar.nanoteq.co.za) Message-ID: <380469B1.A59EA53D@oskar.nanoteq.co.za> Date: Wed, 13 Oct 1999 13:14:57 +0200 From: Johan Kruger Reply-To: jkruger@oskar.nanoteq.co.za Organization: Nanoteq X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Narvi , freebsd-hackers@freebsd.org Subject: Re: Generating interrupts ? References: Content-Type: multipart/mixed; boundary="------------0AC8A9355CD50C154ABCD855" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------0AC8A9355CD50C154ABCD855 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I want to read the the type of motherboard the system is running on, as well as the BIOS version string. It's easy to read the harware the bios detects ( it's in the 64 bytes you can read from port 71 ) but i need the the other info ass well. --------------0AC8A9355CD50C154ABCD855 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:;0 fn:Johan Kruger end:vcard --------------0AC8A9355CD50C154ABCD855-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 6:54:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 2248714D81 for ; Wed, 13 Oct 1999 06:54:27 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id XAA53525; Wed, 13 Oct 1999 23:22:13 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199910131352.XAA53525@gizmo.internode.com.au> Subject: Re: Generating interrupts ? To: jkruger@oskar.nanoteq.co.za Date: Wed, 13 Oct 1999 23:22:13 +0930 (CST) Cc: narvi@haldjas.folklore.ee, freebsd-hackers@FreeBSD.ORG In-Reply-To: <380469B1.A59EA53D@oskar.nanoteq.co.za> from "Johan Kruger" at Oct 13, 99 01:14:57 pm X-Mailer: ELM [version 2.4 PL25] 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 Johan Kruger wrote: > I want to read the the type of motherboard the system is running on, as well > as the BIOS version string. With all due respect, part of the whole point of UNIX is that you don't need to care about that. Why not tell us what you're actually trying to achieve (instead of how you're trying to achieve it) and we'll be able to give you a different way of doing it which actually makes sense. - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 7:15:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ockle.nanoteq.co.za (ockle.nanoteq.co.za [196.37.91.54]) by hub.freebsd.org (Postfix) with ESMTP id 9D8FA15263 for ; Wed, 13 Oct 1999 07:15:10 -0700 (PDT) (envelope-from jkruger@oskar.nanoteq.co.za) Received: from oskar.nanoteq.co.za (localhost.nanoteq.co.za [127.0.0.1]) by ockle.nanoteq.co.za (8.9.3/8.9.3) with ESMTP id QAA47623; Wed, 13 Oct 1999 16:08:09 +0200 (SAST) (envelope-from jkruger@oskar.nanoteq.co.za) Message-ID: <38049249.F3453D17@oskar.nanoteq.co.za> Date: Wed, 13 Oct 1999 16:08:09 +0200 From: Johan Kruger Reply-To: jkruger@oskar.nanoteq.co.za Organization: Nanoteq X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Newton , freebsd-hackers@freebsd.org Subject: Re: Generating interrupts ? References: <199910131352.XAA53525@gizmo.internode.com.au> Content-Type: multipart/mixed; boundary="------------F4D03F86B50D2430F6157E38" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------F4D03F86B50D2430F6157E38 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hmmmm, OK , well, i want to use the specific strings as part of the info with which i am going to encrypt the kernel. Don't ask why, i am not at liberty to say. Don't worry , it'l work, i just need the info from the motherboard and bios rev --------------F4D03F86B50D2430F6157E38 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:;0 fn:Johan Kruger end:vcard --------------F4D03F86B50D2430F6157E38-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 7:32:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id B45161520E for ; Wed, 13 Oct 1999 07:32:14 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id AAA53879; Thu, 14 Oct 1999 00:00:36 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199910131430.AAA53879@gizmo.internode.com.au> Subject: Re: Generating interrupts ? To: jkruger@oskar.nanoteq.co.za Date: Thu, 14 Oct 1999 00:00:36 +0930 (CST) Cc: newton@internode.com.au, freebsd-hackers@freebsd.org In-Reply-To: <38049249.F3453D17@oskar.nanoteq.co.za> from "Johan Kruger" at Oct 13, 99 04:08:09 pm X-Mailer: ELM [version 2.4 PL25] 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 Johan Kruger wrote: > Hmmmm, OK , well, i want to use the specific strings as part of the > info with which i am going to encrypt the kernel. Don't ask why, i am > not at liberty to say. Great. We get to deal with someone who wants assistance but is too concerned with intrigue to fully explain the problem domain. We shall press on. It sounds like you want a kernel that's only able to boot on a particular machine, and you figure that that information from the BIOS is the closest thing a PC has to a hostid. I assume you'll have a kernel with an unencrypted entrypoint which knows how to decrypt the rest. > Don't worry , it'l work, i just need the info from the motherboard > and bios rev Have a look at i386_vm86(2) and its associated kernel support in /sys/i386, or (perhaps a better idea) think about doing your decryption in the bootloader where you have full access to the BIOS. While you're reading through it all, always keep the fact that there's probably a better way at the forefront of your mind :-) - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 7:58:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ockle.nanoteq.co.za (ockle.nanoteq.co.za [196.37.91.54]) by hub.freebsd.org (Postfix) with ESMTP id 2D5C014E25 for ; Wed, 13 Oct 1999 07:57:45 -0700 (PDT) (envelope-from jkruger@oskar.nanoteq.co.za) Received: from oskar.nanoteq.co.za (localhost.nanoteq.co.za [127.0.0.1]) by ockle.nanoteq.co.za (8.9.3/8.9.3) with ESMTP id QAA49394; Wed, 13 Oct 1999 16:55:18 +0200 (SAST) (envelope-from jkruger@oskar.nanoteq.co.za) Message-ID: <38049D55.FF4E2812@oskar.nanoteq.co.za> Date: Wed, 13 Oct 1999 16:55:17 +0200 From: Johan Kruger Reply-To: jkruger@oskar.nanoteq.co.za Organization: Nanoteq X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Newton , freebsd-hackers@freebsd.org Subject: Re: Generating interrupts ? References: <199910131430.AAA53879@gizmo.internode.com.au> Content-Type: multipart/mixed; boundary="------------4AF8CDD17664E320C38956C7" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------4AF8CDD17664E320C38956C7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Your close. I actually made a bootable CD which installs a modified version of FreeBSD, with our product running on on top of it. The CD automatically boots up, installs everything, configures everything and then it asks you for a password. At this stage it gathered information of the particular system. It uses this information and a private key to encrypt the root password and then generates a signiture. The customer phones / mail us with this signiture, we decrypt it using our public key. Now we generate the required key which they have to enter for the installation to complete. In this signiture we got from them we have the followinf info : --> Motherboard used --> Bios Revision --> Root password --> admin password --> other info like disk sizes etc. Only we have the root password, they can change the admin password, and you have to log in as admin first before you can login as root. So, we can do support on the product, since we have the root password, if they give us access via admin password. No problem, the product has been working something like this for 11 years. Now, the machine won't be able to boot if they had'nt entered the correct code which we mail to them, since the kernel is encrypted with it etc etc. So can you pleasssseee now tel me how to get this info ? --> Motherboard used --> Bios Revision Greetings --------------4AF8CDD17664E320C38956C7 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:;0 fn:Johan Kruger end:vcard --------------4AF8CDD17664E320C38956C7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 8:12: 8 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 712C2152DA; Wed, 13 Oct 1999 08:11:56 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id LAA00717; Wed, 13 Oct 1999 11:11:52 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id LAA55430; Wed, 13 Oct 1999 11:11:22 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 13 Oct 1999 11:11:21 -0400 (EDT) To: Jason Thorpe Cc: freebsd-alpha@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: alpha scheduling needs some tuning In-Reply-To: <199910130412.VAA19287@lestat.nas.nasa.gov> References: <199910130412.VAA19287@lestat.nas.nasa.gov> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14340.41179.427200.433885@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Thorpe writes: > On Tue, 12 Oct 1999 23:37:53 -0400 (EDT) > Andrew Gallatin wrote: > > > Has anybody noticed that scheduling appears to be broken on the alpha? > > > > On both i386 & alpha, try: > > > > echo "main(){for(;;);}" > foo.c > > cc foo.c > > /usr/bin/nice -20 ./a.out & ; ./a.out & > > FWIW, Ross Harvey fixed a whole slew of scheduler bugs in NetBSD that > tickled themselves on the Alpha (due to it's high statclock rate). > > -- Jason R. Thorpe Jason, Thanks for the pointer. I think I've gleaned a fix to the FreeBSD/alpha niceness problem. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 8:30:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 81BA215289 for ; Wed, 13 Oct 1999 08:30:19 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id BAA06611; Thu, 14 Oct 1999 01:29:52 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma006602; Thu, 14 Oct 99 01:29:50 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id BAA01227; Thu, 14 Oct 1999 01:29:19 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id BAA01927; Thu, 14 Oct 1999 01:29:18 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id BAA12794; Thu, 14 Oct 1999 01:29:18 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199910131529.BAA12794@nymph.detir.qld.gov.au> To: Greg Lehey Cc: freebsd-hackers@freebsd.org, syssgm@detir.qld.gov.au Subject: Re: Unquoted mail (was: aio_read kills machine) References: <19991012114211.O78191@freebie.lemis.com> In-Reply-To: <19991012114211.O78191@freebie.lemis.com> from Greg Lehey at "Tue, 12 Oct 1999 11:42:11 +0930" Date: Thu, 14 Oct 1999 01:29:17 +1000 From: Stephen McKay Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 12th October 1999, Greg Lehey wrote: >On Monday, 11 October 1999 at 20:39:11 -0500, Matthew D. Fuller wrote: >> On Tue, Oct 12, 1999 at 11:04:50AM +0930, a little birdie told me >> that Greg Lehey remarked >>> >>> What mailer are you using? It didn't quote the "From " at the >>> beginning of the message, so David's message appeared as a separate >>> message. If you're looking for it, sort your messages in mailbox >>> order and it'll be the next message after Andy's original. >> >> He appears to be using Pine, and it quoted it just fine for me. >> And I do believe we're both using the same MUA, so I don't know where it >> burped on the way to you. > >It doesn't have anything to do with the MUA. The message arrived here >without a > in front of the 'From ' at the beginning of the line, >which is an indication that it's a new message. But it's interesting >that it didn't happen to everybody. It's perfectly OK for 'From ' to appear at the beginning of the line in mail. It's not in any way special in standard conformant mail. It's only when you want to store it in the traditional mailbox format that you end up with a spurious mail delimiter. If your mail delivery program stores mail in such a format, it must be able to detect and neutralise unintended markers. My mailer (mh) does not use 'From ' as a marker and stores it unaltered. The message in question arrived here unmolested (ie with no '>' indicator). That is good. /usr/libexec/mail.local (the default delivery program) will insert '>' before 'From ' though only if there is a preceding blank line. I expect that the '>' some people observed was added by their local delivery agent, though by my reading of the code it can't have been mail.local. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 9:15:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 135F314A28 for ; Wed, 13 Oct 1999 09:15:20 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA09606; Wed, 13 Oct 1999 09:15:19 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA04522; Wed, 13 Oct 1999 09:15:18 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 13 Oct 1999 09:15:18 -0700 (PDT) Message-Id: <199910131615.JAA04522@vashon.polstra.com> To: wghicks@bellsouth.net Subject: Re: Search a symbol in the source tree In-Reply-To: <199910130734.DAA05466@bellsouth.net> References: <199910130734.DAA05466@bellsouth.net> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199910130734.DAA05466@bellsouth.net>, W Gerald Hicks wrote: > I find it ironic that nobody has suggested global yet; > > That sure would make a nice port, especially since we could > easily recommend gozilla as a nice way to browse and search > the source tree. Er, global is part of the base system. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 9:32:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 0F65B15012 for ; Wed, 13 Oct 1999 09:31:34 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 86B4D1C52; Wed, 13 Oct 1999 11:34:33 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 7DA30381A; Wed, 13 Oct 1999 11:34:33 -0400 (EDT) Date: Wed, 13 Oct 1999 11:34:33 -0400 (EDT) From: Bill Fumerola To: John Polstra Cc: wghicks@bellsouth.net, hackers@freebsd.org Subject: Re: Search a symbol in the source tree In-Reply-To: <199910131615.JAA04522@vashon.polstra.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, 13 Oct 1999, John Polstra wrote: > > That sure would make a nice port, especially since we could > > easily recommend gozilla as a nice way to browse and search > > the source tree. > > Er, global is part of the base system. :-) And for those who like to point and laugh: c [1998/08/11] ports/7580 ports new port: devel/global -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 10:25:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 2EAE214ECD for ; Wed, 13 Oct 1999 10:25:17 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA09918; Wed, 13 Oct 1999 10:25:16 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA04762; Wed, 13 Oct 1999 10:25:16 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 13 Oct 1999 10:25:16 -0700 (PDT) Message-Id: <199910131725.KAA04762@vashon.polstra.com> To: aron@cs.rice.edu Subject: Re: paper on fine-grained OS timers In-Reply-To: <199910121552.KAA16014@cs.rice.edu> References: <199910121552.KAA16014@cs.rice.edu> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199910121552.KAA16014@cs.rice.edu>, Mohit Aron wrote: > I'd like to tell the BSD community about my paper entitled > "Soft timers: efficient microsecond software timer support for network > processing" that's going to appear in SOSP 1999. The abstract for the paper > is attached below. The gzip'd postcript for the paper can be downloaded from: > http://www.cs.rice.edu/~aron/papers/soft-timers.ps.gz This looks like it would be a nice solution to a known problem with dummynet. From dummynet(4): dummynet performs its task once per timer tick. The granularity of operation is thus controlled by the kernel option options HZ whose default value (100) means a granularity of 10ms. For an accurate simulation of high data rates it might be necessary to reduce the timer granularity to 1ms or less. Consider, however, that some interfaces using programmed I/O may require a considerable time to output packets. So, re- ducing the granularity too much might actually cause ticks to be missed thus reducing the accuracy of operation. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 10:57: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 4A23314BD6; Wed, 13 Oct 1999 10:56:59 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 3B1441CD488; Wed, 13 Oct 1999 10:56:59 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Wed, 13 Oct 1999 10:56:58 -0700 (PDT) From: Kris Kennaway To: W Gerald Hicks Cc: freebsd-hackers@freebsd.org Subject: Re: --enable-haifa In-Reply-To: <199910130729.DAA05354@bellsouth.net> 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, 13 Oct 1999, W Gerald Hicks wrote: > Just curious what effect using the --enable-haifa flag for building > gcc-2.95.1/x86 would have so I did a comparison using the Dhrystone > benchmark from /usr/ports/benchmarks/bytebench. This seems marginal, in other words. How did the results vary when you ran the tests multiple times? Kris ---- XOR for AES -- join the campaign! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 12:15:10 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 28AB815573 for ; Wed, 13 Oct 1999 12:14:17 -0700 (PDT) (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 PAA00741 for ; Wed, 13 Oct 1999 15:14:16 -0400 (EDT) Date: Wed, 13 Oct 1999 15:14:10 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: The meaning of LK_INTERLOCK 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 comments say that the flag LK_INTERLOCK means "unlock passed simple lock after getting lk_interlock". Under what circumstances are we going to need two simple locks (release the first one after getting the second one)? I can not understand this easily from the source 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 Wed Oct 13 13:15:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 5DB2B14C3A for ; Wed, 13 Oct 1999 13:15:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id NAA00709; Wed, 13 Oct 1999 13:05:10 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910132005.NAA00709@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: jkruger@oskar.nanoteq.co.za Cc: Narvi , freebsd-hackers@freebsd.org Subject: Re: Generating interrupts ? In-reply-to: Your message of "Wed, 13 Oct 1999 13:14:57 +0200." <380469B1.A59EA53D@oskar.nanoteq.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Oct 1999 13:05:10 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I want to read the the type of motherboard the system is running on, as well > as the BIOS version string. > It's easy to read the harware the bios detects ( it's in the 64 bytes you > can read from port 71 ) but i need the the other info ass well. Read the Intel paper on UUIDs and GUIDs and consider using boards that have writable and lockable UUID support. None of the other tokens you're contemplating are worthwhile. You might also mandate a particular ethernet adapter and use the MAC address. -- \\ 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 Oct 13 13:27:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 93C511519C for ; Wed, 13 Oct 1999 13:27:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id NAA00823; Wed, 13 Oct 1999 13:18:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910132018.NAA00823@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: jkruger@oskar.nanoteq.co.za Cc: freebsd-hackers@freebsd.org Subject: Re: Generating interrupts ? In-reply-to: Your message of "Wed, 13 Oct 1999 16:55:17 +0200." <38049D55.FF4E2812@oskar.nanoteq.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Oct 1999 13:18:31 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Your close. > I actually made a bootable CD which installs a modified version of FreeBSD, with > our product running on on top of it. The CD automatically boots up, installs > everything, configures everything and then it asks you for a password. At this > stage it gathered information of the particular system. > It uses this information and a private key to encrypt the root password and then > generates a signiture. The customer phones / mail us with this signiture, we > decrypt it using our public key. Now we generate the required key which they > have to enter for the installation to complete. > > In this signiture we got from them we have the followinf info : > --> Motherboard used > --> Bios Revision > --> Root password > --> admin password > --> other info like disk sizes etc. "gross" > So can you pleasssseee now tel me how to get this info ? > --> Motherboard used > --> Bios Revision See sys/i386/bios.c for how to make BIOS calls out of the kernel. But note that obtaining this information in the kernel is too late. See sys/boot/i386/libi386/biosdisk.c for how to call the BIOS in the loader, where you have a chance to obtain this information and use it to decrypt your kernel. -- \\ 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 Oct 13 13:31:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 76EE81519C for ; Wed, 13 Oct 1999 13:31:43 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id NAA00872; Wed, 13 Oct 1999 13:22:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910132022.NAA00872@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: jkruger@oskar.nanoteq.co.za, freebsd-hackers@freebsd.org Subject: Re: Generating interrupts ? In-reply-to: Your message of "Wed, 13 Oct 1999 13:18:31 PDT." <199910132018.NAA00823@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Oct 1999 13:22:01 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > See sys/i386/bios.c for how to make BIOS calls out of the kernel. But > note that obtaining this information in the kernel is too late. See > sys/boot/i386/libi386/biosdisk.c for how to call the BIOS in the > loader, where you have a chance to obtain this information and use it > to decrypt your kernel. I forgot to mention that there's a simpler example of calling the real-mode BIOS in sys/i386/apm/apm.c (on -current), which is probably what you want. -- \\ 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 Oct 13 15: 6:19 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 C7F7414E9F for ; Wed, 13 Oct 1999 15:06:04 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Thu, 14 Oct 1999 07:34:25 +1000 Content-return: prohibited Date: Thu, 14 Oct 1999 07:38:21 +1000 From: Peter Jeremy Subject: Re: Search a symbol in the source tree To: hackers@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct14.073425est.40323@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 Tue, 12 Oct 1999 10:32:00 -0400 (EDT), Zhihui Zhang wrote: >Can anyone suggest me a way of searching symbols in the entire /usr/src >tree? I use id-utils (/usr/ports/devel/id-utils). It builds a single database file and has a variety of tools (including e-lisp) to search the database. Since global(1) was mentioned in this threaad, I decided to have a look at it. It seems much slower and my sample (samba-2.0.5a) database was nearly 20 times larger. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 15:44:45 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 D77E1154A4 for ; Wed, 13 Oct 1999 15:44:24 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id AAA23787 for freebsd-hackers@freebsd.org; Thu, 14 Oct 1999 00:44:20 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 4D2A0885C; Thu, 14 Oct 1999 00:28:43 +0200 (CEST) Date: Thu, 14 Oct 1999 00:28:43 +0200 From: Ollivier Robert To: freebsd-hackers@freebsd.org Subject: Re: --enable-haifa Message-ID: <19991014002843.A64703@keltia.freenix.fr> Mail-Followup-To: freebsd-hackers@freebsd.org References: <199910130729.DAA05354@bellsouth.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <199910130729.DAA05354@bellsouth.net> 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 W Gerald Hicks: > Just curious what effect using the --enable-haifa flag for building > gcc-2.95.1/x86 would have so I did a comparison using the Dhrystone > benchmark from /usr/ports/benchmarks/bytebench. I think the Haifa scheduler is only really effective on pure RISC processors like the Alpha or PA-8000. I remember doing some tests with older versions of egcs and not seeing any significant changes... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 15:46:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail0.atl.bellsouth.net (mail0.atl.bellsouth.net [205.152.0.27]) by hub.freebsd.org (Postfix) with ESMTP id 76799153B4 for ; Wed, 13 Oct 1999 15:46:13 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-216-78-100-222.asm.bellsouth.net [216.78.100.222]) by mail0.atl.bellsouth.net (3.3.4alt/0.75.2) with ESMTP id SAA20630; Wed, 13 Oct 1999 18:43:58 -0400 (EDT) Received: from wghicks.bellsouth.net (IDENT:wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id SAA07080; Wed, 13 Oct 1999 18:51:47 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199910132251.SAA07080@bellsouth.net> To: John Polstra Cc: wghicks@bellsouth.net, hackers@freebsd.org, wghicks@wghicks.bellsouth.net Subject: Re: Search a symbol in the source tree In-reply-to: Your message of "Wed, 13 Oct 1999 09:15:18 PDT." <199910131615.JAA04522@vashon.polstra.com> Date: Wed, 13 Oct 1999 18:51:47 -0400 From: W Gerald Hicks Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Er, global is part of the base system. :-) Hehe, I knew that. My point was that the entire package isn't built and the author's going GPL anyway and since nobody recommended it ... That sure would make a nice port ;-) For the original poster gtags/htags is an excellent tool for your purposes. In its full installation it can generate html versions of your code and is chock full of other features too. Give it a test drive :-) Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 17:47: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from marcy.nas.nasa.gov (marcy.nas.nasa.gov [129.99.113.17]) by hub.freebsd.org (Postfix) with ESMTP id 15C3C14F2F for ; Wed, 13 Oct 1999 17:46:54 -0700 (PDT) (envelope-from wrstuden@marcy.nas.nasa.gov) Received: from localhost (wrstuden@localhost) by marcy.nas.nasa.gov (8.9.3/NAS8.8.7n) with SMTP id RAA10555; Wed, 13 Oct 1999 17:46:38 -0700 (PDT) Date: Wed, 13 Oct 1999 17:46:37 -0700 (PDT) From: Bill Studenmund To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: The meaning of LK_INTERLOCK 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, 13 Oct 1999, Zhihui Zhang wrote: > > The comments say that the flag LK_INTERLOCK means "unlock passed simple > lock after getting lk_interlock". Under what circumstances are we going to > need two simple locks (release the first one after getting the second > one)? I can not understand this easily from the source code. > > Any help is appreciated. The idea is that the other interlock protects something whose value determines if we want to grab the lock. For example, vn_lock() grabs the vnode interlock and looks at v_flag. If VXLOCK is clear, we then call VOP_LOCK. By doing this interlock trick, no one can get in and modify the flags before we've entered the lock manager. Take care, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 13 19:38:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 43A5B14DF6 for ; Wed, 13 Oct 1999 19:38:25 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id WAA64449; Wed, 13 Oct 1999 22:38:19 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Wed, 13 Oct 1999 22:38:19 -0400 (EDT) From: Chuck Robey To: W Gerald Hicks Cc: John Polstra , hackers@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: Search a symbol in the source tree In-Reply-To: <199910132251.SAA07080@bellsouth.net> 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, 13 Oct 1999, W Gerald Hicks wrote: > > Er, global is part of the base system. :-) > > Hehe, I knew that. > > My point was that the entire package isn't built and the author's > going GPL anyway and since nobody recommended it ... That sure would > make a nice port ;-) That's simply not true, and we know (since it was on the mailing list) that you know better. The author's committed to keeping the BSD version current, and in the present license. You said you were for pruning down the size of FreeBSD, which is a defensible position, but misrepresenting the author is really unfair, and you can't justify what you're doing here because of it. You were called on this when you did it then, too. > > For the original poster gtags/htags is an excellent tool for your > purposes. In its full installation it can generate html versions > of your code and is chock full of other features too. Give it a > test drive :-) > > Cheers, > > Jerry Hicks > wghicks@bellsouth.net > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 1: 4:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 00F0A14CD4 for ; Thu, 14 Oct 1999 01:04:38 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from kim.ispra.webweaving.org (va-164.skylink.it [194.185.55.164]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id KAA00891 for ; Thu, 14 Oct 1999 10:04:58 +0200 Received: from brunte.ispra.webweaving.org (brunte.ispra.webweaving.org [10.0.0.12]) by kim.ispra.webweaving.org (8.8.8/8.8.5) with ESMTP id IAA14899 for ; Thu, 14 Oct 1999 08:03:45 GMT X-Passed: MX on Ispra.WebWeaving.org Thu, 14 Oct 1999 08:03:45 GMT and masked X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Thu, 14 Oct 1999 08:03:45 GMT Date: Thu, 14 Oct 1999 10:03:44 +0200 (CEST) From: Dirk-Willem van Gulik X-Sender: dirkx@brunte.ispra.webweaving.org To: freebsd-hackers@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 FYI: The last make world (from a delta of 3 weeks) caused: Oct 14 10:01:48 brunte /kernel: ahc0: Data Parity Error Detected during address or write data phase Oct 14 10:02:04 brunte /kernel: ahc0: Data Parity Error Detected during address or write data phase The entertaining thing is that _nothing_ is attaced to ahc0 at all. Dw. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 2:32:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 789B014DB3 for ; Thu, 14 Oct 1999 02:32:21 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id MAA59639; Thu, 14 Oct 1999 12:32:14 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Date: Thu, 14 Oct 1999 12:32:14 +0300 (EEST) From: Narvi To: Ollivier Robert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: --enable-haifa In-Reply-To: <19991014002843.A64703@keltia.freenix.fr> 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, 14 Oct 1999, Ollivier Robert wrote: > According to W Gerald Hicks: > > Just curious what effect using the --enable-haifa flag for building > > gcc-2.95.1/x86 would have so I did a comparison using the Dhrystone > > benchmark from /usr/ports/benchmarks/bytebench. > > I think the Haifa scheduler is only really effective on pure RISC processors > like the Alpha or PA-8000. I remember doing some tests with older versions of > egcs and not seeing any significant changes... According to my vague recollectiosn from the early times of egcs when faifa was integrated, etc. part of the problem is that to have haifa be really effective, all old kluges need be removed... Something that back then happened/had happened only to a few cpus, like HP-PA. Not sure what may have happened since, but I doubt somebody has redone x86 code generation and fully integrated haifa ins scheduler. > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 4:45:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from avalon.informatik.uni-freiburg.de (avalon.informatik.uni-freiburg.de [132.230.150.1]) by hub.freebsd.org (Postfix) with ESMTP id 2F04F14CCC for ; Thu, 14 Oct 1999 04:45:35 -0700 (PDT) (envelope-from heller@informatik.uni-freiburg.de) Received: from merkur.informatik.uni-freiburg.de (merkur.informatik.uni-freiburg.de [132.230.151.11]) by avalon.informatik.uni-freiburg.de (8.9.0/8.9.0) with ESMTP id NAA14197; Thu, 14 Oct 1999 13:45:33 +0200 (MET DST) Received: from localhost (heller@localhost) by merkur.informatik.uni-freiburg.de (8.8.7/8.8.7) with SMTP id NAA00659; Thu, 14 Oct 1999 13:45:31 +0200 (MET DST) Date: Thu, 14 Oct 1999 13:45:31 +0200 (MET DST) From: Martin Heller To: Narvi Cc: Ollivier Robert , freebsd-hackers@freebsd.org Subject: Re: --enable-haifa 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, 14 Oct 1999, Narvi wrote: [snip] > According to my vague recollectiosn from the early times of egcs when > faifa was integrated, etc. part of the problem is that to have haifa be > really effective, all old kluges need be removed... > > Something that back then happened/had happened only to a few cpus, like > HP-PA. Not sure what may have happened since, but I doubt somebody has > redone x86 code generation and fully integrated haifa ins scheduler. Richard Henderson rewrote the whole ia32 backend and the merger was completed on September 2, 1999 . I don't know if haifa was fully integrated, but I bet it was (IIRC, R. Henderson did this for alpha). Martin > > > -- > > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > > FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 > > > > > > 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 Oct 14 4:51:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay1.bcs.zp.ua (bcs-zyx-eth.marka.net.ua [195.248.171.202]) by hub.freebsd.org (Postfix) with ESMTP id 3C70A14C4E for ; Thu, 14 Oct 1999 04:51:07 -0700 (PDT) (envelope-from serg@bcs3.bcs.zp.ua) Received: from bcs3.bcs.zp.ua (bcs3.bcs.zp.ua [212.8.35.73]) by relay1.bcs.zp.ua (8.9.3/8.9.3) with ESMTP id OAA22682 for ; Thu, 14 Oct 1999 14:51:04 +0300 (EEST) Received: (from serg@localhost) by bcs3.bcs.zp.ua (8.8.8/8.8.8) id OAA18802 for hackers@freebsd.org; Thu, 14 Oct 1999 14:51:04 +0300 (EEST) (envelope-from serg) From: Sergey Shkonda Message-Id: <199910141151.OAA18802@bcs3.bcs.zp.ua> Subject: Memory requirements... To: hackers@freebsd.org Date: Thu, 14 Oct 1999 14:51:04 +0300 (EEST) X-Mailer: ELM [version 2.4ME+ PL61 (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 Why on 3.3-RELEASE getty (and other programs) takes to much memory ? On 2.2-STABLE i have: # ps axlw|grep getty 0 306 1 0 3 0 188 144 ttyin Is+ v0 0:00.07 /usr/libexec/getty Pc0 ttyv0 0 15745 1 0 3 0 184 364 ttyin Is+ v3 0:00.01 /usr/libexec/getty Pc ttyv3 0 22272 1 0 3 0 184 160 ttyin Is+ v6 0:00.01 /usr/libexec/getty Pc ttyv6 0 14509 1 0 3 0 184 156 ttyin Is+ v7 0:00.01 /usr/libexec/getty Pc ttyv7 0 28974 1 0 3 0 184 192 ttyin Is+ v8 0:00.01 /usr/libexec/getty Pc ttyv8 On 3.3-RELEASE: # ps axlw|grep getty 0 263 1 0 3 0 832 496 ttyin Is+ v0 0:00.01 /usr/libexec/getty Pc0 ttyv0 0 265 1 0 3 0 832 496 ttyin Is+ v2 0:00.01 /usr/libexec/getty Pc ttyv2 0 266 1 0 3 0 832 496 ttyin Is+ v3 0:00.01 /usr/libexec/getty Pc ttyv3 0 267 1 0 3 0 832 496 ttyin Is+ v4 0:00.01 /usr/libexec/getty Pc ttyv4 0 268 1 0 3 0 832 496 ttyin Is+ v5 0:00.01 /usr/libexec/getty Pc ttyv5 0 269 1 0 3 0 832 496 ttyin Is+ v8 0:00.01 /usr/libexec/getty Pc ttyv8 -- Sergey Shkonda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 5:25:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eltex.ru (ELTEX-2-SPIIRAS.nw.ru [195.19.204.46]) by hub.freebsd.org (Postfix) with ESMTP id F156114BC4; Thu, 14 Oct 1999 05:24:32 -0700 (PDT) (envelope-from antuan@eltex.ru) Received: from gadget.eltex.ru (root@gadget.eltex.ru [195.19.198.14]) by eltex.ru (8.9.3/8.9.3) with SMTP id QAA21520; Thu, 14 Oct 1999 16:24:35 +0400 (MSD) Received: by gadget.eltex.ru (ssmtp TIS-0.5alpha, 19 Oct 1998); Thu, 14 Oct 1999 16:24:09 +0400 Received: from undisclosed-intranet-sender id xma015479; Thu, 14 Oct 99 16:23:41 +0400 Received: (from antuan@localhost) by tyger.hq.eltex.ru (8.9.3/8.9.3) id QAA86621; Thu, 14 Oct 1999 16:24:30 +0400 (MSD) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 14 Oct 1999 16:24:29 +0400 (MSD) From: Antuan Avdioukhine To: freebsd-hackers@freebsd.org Subject: policy routing and freebsd Cc: freebsd-questions@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG People, does anybody made policy routing under freebsd? I have to substitute different aliased IP's source address when packet departs from the same interface but with another destinations rather then default. There is similar feature in linux (each alias address related with an kind of "subinterface" which makes possible point to it in routing tables). ------ Antuan Avdioukhine St.-Petersburg, Russia 14-Oct-99 16:18:47 ------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 5:32:19 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 66C3914E11 for ; Thu, 14 Oct 1999 05:32:11 -0700 (PDT) (envelope-from singuru@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 SAA07218 for ; Thu, 14 Oct 1999 18:02:33 +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 PAA07397 for <@vayu:freebsd-hackers@FreeBSD.ORG>; Thu, 14 Oct 1999 15:50:54 +0500 (GMT) Message-ID: <9910141559.AA23897@tagore.wipinfo.soft.net> Subject: multicast set ttl value... (fwd) To: freebsd-hackers@FreeBSD.ORG Date: Thu, 14 Oct 1999 15:57:42 +0530 (IST) From: "S.RadhaKrishna" Reply-To: singuru@wipinfo.soft.net Return-Reply-To: singuru@wipinfo.soft.net Location: Wipro Infotech, Mission Rd., Bangalore India X-Mailer: ELM [version 2.4 PL23] 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 all, I'm using the following call to set the ttl value (after doing a successful socket call) ------ ttl=5; if (setsockopt(sockfd, IPPROTO_IP, IP_MULTICAST_TTL, (char *)&ttl, sizeof(ttl)) < 0) { printf("\nserv.c: setting of TTL value failed \n"); perror("setsockopt"); exit(1); } --------- It works on unix but not on NT/98. I tried declaring "ttl" as char/int/short. But it didn't help. I would be thankful if any one can provide me some help on this. PS: I'm sorry if I've posted the question in the wrong group. Would be happy if any one can direct me to the proper group. regards radha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 5:37:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.dti.ne.jp (smtp.dti.ne.jp [210.170.128.120]) by hub.freebsd.org (Postfix) with ESMTP id 9C3CC14BC4 for ; Thu, 14 Oct 1999 05:37:19 -0700 (PDT) (envelope-from shigio@tamacom.com) Received: from choota.signet.or.jp (PPP65.tama-ap5.dti.ne.jp [210.170.192.83]) by smtp.dti.ne.jp (8.9.0/3.7W) with ESMTP id VAA28289 for ; Thu, 14 Oct 1999 21:37:17 +0900 (JST) Received: from choota.signet.or.jp (localhost [127.0.0.1]) by choota.signet.or.jp (8.8.8/) with ESMTP id VAA07300 for ; Thu, 14 Oct 1999 21:34:15 +0900 (JST) Message-Id: <199910141234.VAA07300@tamacom.com> To: hackers@FreeBSD.ORG Subject: Nvi's new variable '@' Date: Thu, 14 Oct 1999 21:34:15 +0900 From: Shigio Yamaguchi Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I made a private patch for nvi(1) that enable you to use new variable '@' in arguments of ex's ! or !! command. The '@' is similar to '%' which means the editing file name. If you are editing file.c at 110 line then ':!echo @' means ':!echo 110'. It is convenient to use with gozilla(1). If you have hypertext of source code generated by htags with -l option then you can display editing text on mozilla as a hypertext. :!gozilla +@ % Suggested .nexrc: +-------------------------- |map ^G :!gozilla +@ %^M But this is a serious modification of nvi's spec. You cannot use '@' as a constant in nvi's shell command line. So, you had better use this patch personally. Here is a patch for /usr/src/contrib/nvi/ex/ex_argv.c in freebsd-current. *** ex_argv.c.org Fri Nov 1 15:45:30 1996 --- ex_argv.c Thu Oct 14 20:30:04 1999 *************** *** 326,331 **** --- 326,332 ---- EX_PRIVATE *exp; char *bp, *t; size_t blen, len, off, tlen; + char b[30]; /* Replace file name characters. */ for (bp = *bpp, blen = *blenp, len = *lenp; cmdlen > 0; --cmdlen, ++cmd) *************** *** 348,354 **** F_SET(excp, E_MODIFY); break; case '%': ! if ((t = sp->frp->name) == NULL) { msgq(sp, M_ERR, "116|No filename to substitute for %%"); return (1); --- 349,359 ---- F_SET(excp, E_MODIFY); break; case '%': ! case '@': /* replace with line number */ ! if (*cmd == '@') { ! snprintf(b, sizeof(b), "%d", sp->lno); ! t = b; ! } else if ((t = sp->frp->name) == NULL) { msgq(sp, M_ERR, "116|No filename to substitute for %%"); return (1); -- Shigio Yamaguchi - Tama Communications Corporation Mail: shigio@tamacom.com, WWW: http://www.tamacom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 6:27:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cesium.clock.org (cesium.clock.org [209.179.181.185]) by hub.freebsd.org (Postfix) with ESMTP id 3286514F67 for ; Thu, 14 Oct 1999 06:27:14 -0700 (PDT) (envelope-from smd@clock.org) Received: from localhost (user: 'smd', uid#42) by cesium.clock.org id <7350-10662>; Thu, 14 Oct 1999 06:26:43 -0700 From: smd@clock.org To: freebsd-hackers@freebsd.org Subject: Re: --enable-haifa Message-Id: <19991014132657Z7350-10662+3@cesium.clock.org> Date: Thu, 14 Oct 1999 06:26:43 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of curiosity, were the benchmarks done with any of the Haifa command-line-options, notably -fsched-interblock, -fsched-spec, -fsched-spec-load, and -fbranch-count-reg ? (toplev.c, grep for '#ifdef HAIFA', and read the comments scattered elsewhere (haifa-sched.c)) Sean. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 6:47:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from anon.lcs.mit.edu (anon.lcs.mit.edu [18.26.0.254]) by hub.freebsd.org (Postfix) with SMTP id 188F914F07 for ; Thu, 14 Oct 1999 06:47:22 -0700 (PDT) (envelope-from serge69@nym.alias.net) Date: 14 Oct 1999 13:47:20 -0000 Message-ID: <19991014134720.2433.qmail@nym.alias.net> From: Sergey Subject: Re: policy routing and freebsd To: "Antuan Avdioukhine" , Cc: References: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > People, does anybody made policy routing under freebsd? > I have to substitute different aliased IP's source address when packet departs > from the same interface but with another destinations rather then default. It's relative simple if your source addresses are on the different IP networks. But you should set aliased address on your router too. In other case, I guess that two natd daemons and firewall controled diverting would help you. > There is similar feature in linux (each alias address related with an kind of > "subinterface" which makes possible point to it in routing tables). > You can do similar thing here too. I presume that router has 2 IP: 192.168.1.1 and 172.17.1.1. # ifconfig ed0 inet 172.16.1.2 # ifconfig ed0 alias 192.168.1.2 # route add my.specific.destination 192.168.1.1 With best regards, Sergey. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 6:51:14 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 7A04114FCC for ; Thu, 14 Oct 1999 06:50:53 -0700 (PDT) (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.037 #1) id 11blFz-0000gF-00; Thu, 14 Oct 1999 15:49:23 +0200 From: Sheldon Hearn To: Shigio Yamaguchi Cc: hackers@FreeBSD.ORG Subject: Re: Nvi's new variable '@' In-reply-to: Your message of "Thu, 14 Oct 1999 21:34:15 +0900." <199910141234.VAA07300@tamacom.com> Date: Thu, 14 Oct 1999 15:49:23 +0200 Message-ID: <2618.939908963@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Oct 1999 21:34:15 +0900, Shigio Yamaguchi wrote: > I made a private patch for nvi(1) that enable you to use new variable '@' > in arguments of ex's ! or !! command. Be sure to pass this on to this contributed software's maintainer, Keith Bostic . Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 7:18:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 1EA2414C32 for ; Thu, 14 Oct 1999 07:18:03 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id QAA04948; Thu, 14 Oct 1999 16:18:07 +0100 From: Luigi Rizzo Message-Id: <199910141518.QAA04948@labinfo.iet.unipi.it> Subject: Re: multicast set ttl value... (fwd) To: singuru@wipinfo.soft.net Date: Thu, 14 Oct 1999 16:18:07 +0100 (MET) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <9910141559.AA23897@tagore.wipinfo.soft.net> from "S.RadhaKrishna" at Oct 14, 99 03:57:23 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1423 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi all, > I'm using the following call to set the ttl value (after doing a successful > socket call) > ------ > ttl=5; > if (setsockopt(sockfd, IPPROTO_IP, IP_MULTICAST_TTL, > (char *)&ttl, sizeof(ttl)) < 0) > { > printf("\nserv.c: setting of TTL value failed \n"); > perror("setsockopt"); > exit(1); > } > --------- > It works on unix but not on NT/98. I tried declaring "ttl" as > char/int/short. But it didn't help. I would be thankful if any one can > provide me some help on this. been there, done that, on windows apart from the different type (i think it needs to be int) you can only set the ttl after you have bound the socket to a multicast address. not totally nonsense, but definitely "different" from unix 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 9:59:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pak2.texar.com (pak2.texar.com [216.208.160.130]) by hub.freebsd.org (Postfix) with ESMTP id BD10015032 for ; Thu, 14 Oct 1999 09:59:41 -0700 (PDT) (envelope-from dseg@pak2.texar.com) Received: from localhost (dseg@localhost) by pak2.texar.com (8.9.2/8.8.3) with ESMTP id MAA97359 for ; Thu, 14 Oct 1999 12:59:40 -0400 (EDT) Date: Thu, 14 Oct 1999 12:59:40 -0400 (EDT) From: Dan Seguin To: FreeBSD Hackers Subject: Kernel APIs - Solaris 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 all. I know this isn't a Solaris group, but you guys tend to know loads of stuff about other Unices, so: I'm looking for information pertaining to the Solaris 2.x Kernel. We're writing auditing tools for system calls, and therefore need to write loadable modules (I've done this in FreeBSD, works flawlessly). Does anyone know where/how to get the Kernel APIs for Solaris. We're willing to pay/register/sign NDAs/whatever for this. After two weeks of dealing with clueless Sun people, I'm going mental. Thanks Dan Seguin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 10: 7: 9 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 CE8A615245 for ; Thu, 14 Oct 1999 10:06:46 -0700 (PDT) (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 KAA00683; Thu, 14 Oct 1999 10:06:31 -0700 Date: Thu, 14 Oct 1999 10:06:31 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Dan Seguin Cc: FreeBSD Hackers Subject: Re: Kernel APIs - Solaris 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 Talk to me. On Thu, 14 Oct 1999, Dan Seguin wrote: > > > Hi all. I know this isn't a Solaris group, but you guys tend to know loads > of stuff about other Unices, so: > > I'm looking for information pertaining to the Solaris 2.x Kernel. We're > writing auditing tools for system calls, and therefore need to write > loadable modules (I've done this in FreeBSD, works flawlessly). > > > Does anyone know where/how to get the Kernel APIs for Solaris. We're > willing to pay/register/sign NDAs/whatever for this. After two weeks of > dealing with clueless Sun people, I'm going mental. > > Thanks > > Dan Seguin > > > > 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 Oct 14 10:22:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.atl.bellsouth.net (mail2.atl.bellsouth.net [205.152.0.22]) by hub.freebsd.org (Postfix) with ESMTP id 27FB115032 for ; Thu, 14 Oct 1999 10:22:33 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-216-78-43-104.ath.bellsouth.net [216.78.43.104]) by mail2.atl.bellsouth.net (3.3.4alt/0.75.2) with ESMTP id NAA16442; Thu, 14 Oct 1999 13:22:31 -0400 (EDT) Received: from wghicks.bellsouth.net (IDENT:wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id NAA09399; Thu, 14 Oct 1999 13:28:25 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199910141728.NAA09399@bellsouth.net> To: smd@clock.org Cc: freebsd-hackers@FreeBSD.ORG, wghicks@wghicks.bellsouth.net Subject: Re: --enable-haifa In-reply-to: Your message of "Thu, 14 Oct 1999 06:26:43 PDT." <19991014132657Z7350-10662+3@cesium.clock.org> Date: Thu, 14 Oct 1999 13:28:25 -0400 From: W Gerald Hicks Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Out of curiosity, were the benchmarks done with any of the Haifa > command-line-options, notably -fsched-interblock, -fsched-spec, > -fsched-spec-load, and -fbranch-count-reg ? > (toplev.c, grep for '#ifdef HAIFA', and read the comments > scattered elsewhere (haifa-sched.c)) Not yet, but thanks for the pointers! :-) I don't have a shiny new K7 yet, where I might expect the haifa build to make more of a difference than my crusty old Pentium... Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 10:25:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pak2.texar.com (pak2.texar.com [216.208.160.130]) by hub.freebsd.org (Postfix) with ESMTP id 7016814F58 for ; Thu, 14 Oct 1999 10:25:25 -0700 (PDT) (envelope-from dseg@pak2.texar.com) Received: from localhost (dseg@localhost) by pak2.texar.com (8.9.2/8.8.3) with ESMTP id NAA98261; Thu, 14 Oct 1999 13:24:50 -0400 (EDT) Date: Thu, 14 Oct 1999 13:24:50 -0400 (EDT) From: Dan Seguin To: Matthew Jacob Cc: FreeBSD Hackers Subject: Re: Kernel APIs - Solaris 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 Hi. Thanks for your response. As I mentioned in my post, we're looking for the Kernel API specs. We don't need the source, just the (credible, authoritive) info on Kernel functions and their return values. We have to do this legally, but are having tons of trouble trying to find the right people at Sun. If we wait another 10-12 months, maybe we'll get it through the Community license, but we're not holding our breath. Any ideas, leads? On Thu, 14 Oct 1999, Matthew Jacob wrote: > > Talk to me. > > > On Thu, 14 Oct 1999, Dan Seguin wrote: > > > > > > > Hi all. I know this isn't a Solaris group, but you guys tend to know loads > > of stuff about other Unices, so: > > > > I'm looking for information pertaining to the Solaris 2.x Kernel. We're > > writing auditing tools for system calls, and therefore need to write > > loadable modules (I've done this in FreeBSD, works flawlessly). > > > > > > Does anyone know where/how to get the Kernel APIs for Solaris. We're > > willing to pay/register/sign NDAs/whatever for this. After two weeks of > > dealing with clueless Sun people, I'm going mental. > > > > Thanks > > > > Dan Seguin > > > > > > > > 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 Oct 14 10:36:10 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 4985614ED7 for ; Thu, 14 Oct 1999 10:36:06 -0700 (PDT) (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 KAA00859; Thu, 14 Oct 1999 10:36:02 -0700 Date: Thu, 14 Oct 1999 10:36:02 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Dan Seguin Cc: FreeBSD Hackers Subject: Re: Kernel APIs - Solaris 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 Well, the section 9 man pages are pretty complete. The device driver stuff is actually pretty easily available. In fact, this instead of performance was supposed to be one of the main design goals for Solaris (and I know- I was part of that effort- Gawd, I'm *sorry*.....) There *is* a DDK- I can't remember the order number off the top of my head, but it has enough information to write SCSI target drivers, streams modules, pseudo drivers, etc. It misses several important items that have been added recently (64 bit clean drivers with a 32 bit user ABI) or power mode and/or the rather important DDI_SUSPEND functions for the E10K. There's always an option of hiring a consultant. -matt On Thu, 14 Oct 1999, Dan Seguin wrote: > > > Hi. Thanks for your response. > > As I mentioned in my post, we're looking for the Kernel API specs. We > don't need the source, just the (credible, authoritive) info on Kernel > functions and their return values. > > We have to do this legally, but are having tons of trouble trying to find > the right people at Sun. > > If we wait another 10-12 months, maybe we'll get it through the Community > license, but we're not holding our breath. > > Any ideas, leads? > > > > On Thu, 14 Oct 1999, Matthew Jacob wrote: > > > > > Talk to me. > > > > > > On Thu, 14 Oct 1999, Dan Seguin wrote: > > > > > > > > > > > Hi all. I know this isn't a Solaris group, but you guys tend to know loads > > > of stuff about other Unices, so: > > > > > > I'm looking for information pertaining to the Solaris 2.x Kernel. We're > > > writing auditing tools for system calls, and therefore need to write > > > loadable modules (I've done this in FreeBSD, works flawlessly). > > > > > > > > > Does anyone know where/how to get the Kernel APIs for Solaris. We're > > > willing to pay/register/sign NDAs/whatever for this. After two weeks of > > > dealing with clueless Sun people, I'm going mental. > > > > > > Thanks > > > > > > Dan Seguin > > > > > > > > > > > > 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 Oct 14 11: 6:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt050n71.san.rr.com (dt050n71.san.rr.com [204.210.31.113]) by hub.freebsd.org (Postfix) with ESMTP id 0E14E152F8 for ; Thu, 14 Oct 1999 11:06:23 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gateway.gorean.org (gateway.gorean.org [10.0.0.1]) by dt050n71.san.rr.com (8.9.3/8.8.8) with ESMTP id LAA09208 for ; Thu, 14 Oct 1999 11:06:20 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Thu, 14 Oct 1999 11:06:20 -0700 (PDT) From: Doug X-Sender: doug@dt050n71.san.rr.com To: freebsd-hackers@freebsd.org Subject: How to determine data/text/stack sizes of running proccesses? 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'm trying to set some intelligent resource limits on a CGI server setup, and I'm running into trouble with it. I've set the memoryuse option in login.conf and that does seem to kill them off, but I'd like to be able to fine tune the limits down a little more, while still not interfering with other processes on the system. What I need to do is find out whether the processes that are running away are sucking up virtual memory in the data segment or the stack segment, or both; and how much. I've been looking through man pages, searching the archives, etc. for a couple days now and haven't found anything that will give me this information on a running process. Any pointers would be welcome. Thanks, 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 Oct 14 12: 0:42 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 61B8714A2F for ; Thu, 14 Oct 1999 12:00:39 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id OAA08821; Thu, 14 Oct 1999 14:59:26 -0400 (EDT) Date: Thu, 14 Oct 1999 14:59:26 -0400 (EDT) From: Daniel Eischen Message-Id: <199910141859.OAA08821@pcnet1.pcnet.com> To: dseg@texar.com, mjacob@feral.com Subject: Re: Kernel APIs - Solaris Cc: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > Well, the section 9 man pages are pretty complete. The device driver > stuff is actually pretty easily available. In fact, this instead of > performance was supposed to be one of the main design goals for Solaris > (and I know- I was part of that effort- Gawd, I'm *sorry*.....) > > There *is* a DDK- I can't remember the order number off the top of my > head, but it has enough information to write SCSI target drivers, streams > modules, pseudo drivers, etc. It misses several important items that > have been added recently (64 bit clean drivers with a 32 bit user ABI) > or power mode and/or the rather important DDI_SUSPEND functions for the > E10K. There's always an option of hiring a consultant. All the Sun docs are on-line at http://docs.sun.com/ They are pretty complete, even explaining the DDI_SUSPEND command at: http://docs.sun.com:80/ab2/coll.45.10/DRIVER/@Ab2PageView/37501?Ab2Lang=C&Ab2Enc=iso-8859-1 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 Thu Oct 14 12: 6:52 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 341F814E08 for ; Thu, 14 Oct 1999 12:06:45 -0700 (PDT) (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 NAA31065; Thu, 14 Oct 1999 13:06:43 -0600 (MDT) (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 NAA54571; Thu, 14 Oct 1999 13:07:53 -0600 (MDT) Message-Id: <199910141907.NAA54571@harmony.village.org> To: Dan Seguin Subject: Re: Kernel APIs - Solaris Cc: FreeBSD Hackers In-reply-to: Your message of "Thu, 14 Oct 1999 12:59:40 EDT." References: Date: Thu, 14 Oct 1999 13:07:53 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Dan Seguin writes: : I'm looking for information pertaining to the Solaris 2.x Kernel. We're : writing auditing tools for system calls, and therefore need to write : loadable modules (I've done this in FreeBSD, works flawlessly). For docs on suns, I usually go to: http://docs.sun.com/ The software developers collection may be useful: http://docs.sun.com:80/ab2/coll.45.10/@Ab2CollView?Ab2Lang=C&Ab2Enc=iso-8859-1 Evidentally you can also buy this same information on dead trees. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 12: 8:17 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 7A62114F70 for ; Thu, 14 Oct 1999 12:08:13 -0700 (PDT) (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 NAA31073; Thu, 14 Oct 1999 13:08:11 -0600 (MDT) (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 NAA54591; Thu, 14 Oct 1999 13:09:21 -0600 (MDT) Message-Id: <199910141909.NAA54591@harmony.village.org> To: Dan Seguin Subject: Re: Kernel APIs - Solaris Cc: Matthew Jacob , FreeBSD Hackers In-reply-to: Your message of "Thu, 14 Oct 1999 13:24:50 EDT." References: Date: Thu, 14 Oct 1999 13:09:21 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Dan Seguin writes: : As I mentioned in my post, we're looking for the Kernel API specs. We : don't need the source, just the (credible, authoritive) info on Kernel : functions and their return values. No such animal exists. Sun has many levels of API commitment from the "gotta have it won't change" to the "put in on the whim of a developer to make some system utility easier to code, but will be gutted if the wind changes". The former are documented well in the man pages for man(2), while the latter are generally undocumented. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 15: 1:20 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 312CC14BDC for ; Thu, 14 Oct 1999 15:01:17 -0700 (PDT) (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 SAA08652 for ; Thu, 14 Oct 1999 18:01:14 -0400 (EDT) Date: Thu, 14 Oct 1999 16:58:38 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: Determine # of open files via fdesc 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 do not know whether it is a good idea to determine the number of open files of a process by enabling fdesc in the kernel. Anyway, I do the following: # mount_fdesc -o union fdesc /dev # ls -al /dev/fd > list > cat list total 1 crw------- 1 root tty 12, 0 Oct 15 17:09 0 -rw-r--r-- 1 root wheel 0 Oct 15 17:09 1 crw------- 1 root tty 12, 0 Oct 15 17:09 2 drw-r--r-- 5 root wheel 1024 Oct 15 17:09 3 dr--r--r-- 2 root wheel 512 Oct 15 16:28 4 I do not know why 3 and 4 are labeled as directory. 1 was labeled as character device but is changed probably by the redirection >. I run a small program to open three files and run forever in the background. After this, I expect to see three more items under /dev/fd, but there are not. Can anyone explain this to me? 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 Thu Oct 14 20: 4: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 90CDE14CF0 for ; Thu, 14 Oct 1999 20:03:52 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (root@postal.sr.hp.com [15.4.46.173]) by palrel3.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id UAA17972 for ; Thu, 14 Oct 1999 20:03:39 -0700 (PDT) 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 UAA23419 for ; Thu, 14 Oct 1999 20:03:28 -0700 (PDT) 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 UAA04572 for ; Thu, 14 Oct 1999 20:03:12 -0700 (PDT) Message-Id: <199910150303.UAA04572@mina.sr.hp.com> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Search a symbol in the source tree Reply-To: Darryl Okahata In-reply-to: Your message of "Thu, 14 Oct 1999 07:38:21 +1000." Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Thu, 14 Oct 1999 20:03:11 -0700 From: Darryl Okahata Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > I use id-utils (/usr/ports/devel/id-utils). It builds a single database > file and has a variety of tools (including e-lisp) to search the database. > > Since global(1) was mentioned in this threaad, I decided to have a look > at it. It seems much slower and my sample (samba-2.0.5a) database was > nearly 20 times larger. Well, as a longtime-user of mkid, mkid2, and mkid3 (the predecessors to id-utils), here are some comments on the various packages: [ Note: in the following, I'm not quite comparing apples and apples. However, I'm too lazy to do a strict comparison, but this should still give people a vague idea of each package's performance. Take the following as you will, with a grain of salt. ] * As a baseline, let's look at plain grep. First, generate a list of files to search (this assumes that we don't want to look through all files, including Makefiles, man pages, etc.): cd /usr/src find * -type f | time grep '\.[chsSly][cxp]*$' > /tmp/foo Now, on my system (-current from Aug. 21, a PII 300MHz w/128MB & a F/W SCSI disk), this takes around 50 seconds (real time): xargs grep ptrace < /tmp/foo Not too bad, but not great, either. Let's try looking for utmp.h: xargs grep 'utmp\.h' < /tmp/foo This takes around a minute. Now, let's look at "grep -R": cd /usr/src grep -R ptrace . # 2 minutes 42 seconds grep -R 'utmp\.h' . # 2 minutes 40 seconds In other words, with grep, you need to limit your searches. Also, "grep -R" doesn't work very well if you also happen to have glimpse, global, or mkid/id-utils indices under /usr/src. * Global is OK (does not appear to support C++, though), but generates HUGE databases (by default). For /usr/src, the databases are around as large as the total size of the indexed source files (the gtags "-c" option was not used). Indexing is slow, but searching seems to be quite fast. In particular, "global -x name" is nice, because it just return where "name" is defined, as opposed to a plain grep which can also return matches on "fooname" and "namebar", as well as where "name" is used. However, global appears to be optimized for locating where a function is defined. It appears to be difficult to locate, for example, where a preprocessor macro is defined; except for "global -g" (which is often too slow to be usable), I haven't found a way of getting global to search through .h header files. On my system, indexing /usr/src took around an hour, and the indices took up around 240MB+ (this was with "gtags" and not "gtags -c"). This is 20+ times larger than a glimpse or mkid/id-utils database. It's interesting to note that "global -x -g ptrace" takes around twice as long to execute (over two minutes), compared to plain grep. However, "global -x -s ptrace" is very fast (under 1 second). Searching for ptrace generates two (2) lines of output, in well under one second: global -x ptrace as do these: global -x -s ptrace global -x -s uap Looking for where "utmp.h" is used: global -x -s utmp.h This takes more than 2212 seconds (over 36 minutes!), and outputs nothing. Well, let's try this instead: global -x -g utmp.h This works, taking a bit over a minute and a half. However, plain grep is faster (note that, as global searches through source files only, you have to compare it to the source-file-only grep, and not "grep -R"). However, looking for the definition of a preprocessor macro is a pain. Try looking for KBD_DATA_PORT: global -x KBD_DATA_PORT This runs quickly, but displays nothing. Next, try: global -x -s KBD_DATA_PORT This runs quickly, and shows where this is used in .c source files. However, where's the definition? It's not shown. This works: global -x -g KBD_DATA_PORT However, this takes around two minutes to run, which is much slower than a plain grep. * Glimpse is a general-purpose text indexer which can be used to index source files. It's basically an intelligent grep, but it works quite well. Unlike mkid, you can search through comments and non-source files (like Makefiles, man pages, README's, etc.). On my system, indexing /usr/src took around 6 minutes (using the "-M 20" option), and the indices took up around 10MB. On my system, searching for ptrace took 35 seconds, with 505 lines of output (ChangeLogs, man pages, etc. account for the extra lines): glimpse -w ptrace Searching for uap takes around 21 seconds: glimpse -w uap Looking for utmp.h: glimpse -y -w utmp.h This takes a bit over 45 seconds. However, glimpse searched through (and displayed hits in) non-source files, like configure, configure.in, Makefiles, etc.. It is possible to have glimpse exclude certain files and index only those files you want indexed. However, I don't have the time to configure and test this. Perhaps someone else will do this. * Mkid/mkid2/mkid3/id-utils appear to generate the smallest index databases, and they run quickly. They're great for looking up where a particular identifier is used (e.g., "gid ptrace", which is an intelligent grep), but it can't just tell you where something is defined, and only that place. The place where something is defined is output along with every place that it's used. You're basically doing a very intelligent grep. However, grep'ing via gid is *MUCH* faster than "global -g" (it's like 100X faster); on the other hand, "global -s" is often comparable to gid. Mkid and friends can also (supposedly, as I've never tried it) tell you where a number occurs, in any base. If you know the number 100 is somewhere in your source code, mkid can show you where it occurs, as "100" (decimal), "64" (hex)", or "144" (octal). Only source files are indexed, as mkid & friends only know about certain languages (C, C++, & assembly being a few). Also, comments aren't indexed, although gid will display hits in comments (because the file being grep'd contains a hit in a non-comment line). However, the "id-utils-3.2" package for -current dumps core when used to index /usr/src. I don't have the time to track this down. On my system, indexing /usr/src using mkid3 took a bit over 2 minutes, and the indices took up around 9.1MB. The index was built using: find . -type f | grep '\.[chsSly][cxp]*$' | time mkid - (Note: id-utils is further broken, since it cannot take the list of files to index from stdin or a file -- this example is for mkid3.) Both glimpse and global index more files by default (in the case of glimpse, Makefiles, CVS/Root, CVS/Repository, COPYRIGHT files, etc. were indexed). It's VERY fast. On my system, searching for ptrace takes under 0.5 sec.: gid ptrace Yup, that's under one-half second, with 195 lines of output. Let's try looking for where "utmp.h" is used: gid utmp.h This takes around 2.5 seconds. ***** Bottom line: For general-purpose use, mkid and friends is best, as long as you don't need to search through comments or non-source files (Makefiles, README's, etc.). The database index is reasonably small, the indexing time is relatively quick, and the search times are often comparable to or better than those of global. However, mkid and friends can't just tell you where something is defined; they can only show where it is defined and used. If you need to search through comments, or need to search non-source files, glimpse is good. The index is larger than that of mkid/id-utils, and the search speed is decent, but not great. For many searches, it's faster than plain grep, although it can be comparable to grep in some cases. I've got mixed feelings about global. On the one hand, you can't beat it for locating where a function is defined, and it's very good at showing where a variable is used. However, for best results, you have to remember to use different options when searching for function definitions, identifier usage, preprocessor definitions, etc., and you may still have to resort to doing a full grep because, for some searches, global is too slow. The indices for global are HUGE, and indexing takes much longer than other approaches. I'm surprised that global is part of the base distribution, instead of being a port. -- 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 Hewlett-Packard, 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 Thu Oct 14 21:35:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (Postfix) with ESMTP id 796CF14D29; Thu, 14 Oct 1999 21:35:11 -0700 (PDT) (envelope-from puga@mauibuilt.com) Received: from mauibuilt.com (puga@puga.mauibuilt.com [205.166.10.2]) by mauibuilt.com (8.9.3/8.9.3) with ESMTP id SAA05172; Thu, 14 Oct 1999 18:36:22 -1000 (HST) (envelope-from puga@mauibuilt.com) Message-ID: <3806AEA7.61784866@mauibuilt.com> Date: Thu, 14 Oct 1999 18:33:43 -1000 From: Richard Puga X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-multimedia@freebsd.org Subject: Bt848 based server 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 way to use a bt848 as a web cam or streaming video server through any format other than the metor .ppm snapshots. Thanks in advance Richard Puga puga@mauibuilt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 14 23:29:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from not.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with ESMTP id 8A2EA14BD4 for ; Thu, 14 Oct 1999 23:28:59 -0700 (PDT) (envelope-from will@not.demophon.com) Received: (from will@localhost) by not.demophon.com (8.9.3/8.8.7) id JAA57670; Fri, 15 Oct 1999 09:27:46 +0300 (EEST) (envelope-from will) To: wghicks@bellsouth.net (W Gerald Hicks) Cc: hackers@freebsd.org Subject: Re: --enable-haifa References: <19991014132657Z7350-10662+3@cesium.clock.org> <199910141728.NAA09399@bellsouth.net> From: Ville-Pertti Keinonen Date: 15 Oct 1999 09:27:45 +0300 In-Reply-To: wghicks@bellsouth.net's message of "14 Oct 1999 20:23:27 +0300" Message-ID: <86zoxljfz2.fsf@not.demophon.com> Lines: 8 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG wghicks@bellsouth.net (W Gerald Hicks) writes: > I don't have a shiny new K7 yet, where I might expect the haifa > build to make more of a difference than my crusty old Pentium... Processors with out-of-order execution benefit *less* from scheduling than non-OOO superscalar processors. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 0: 3:17 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 BF51E14BD4 for ; Fri, 15 Oct 1999 00:03:15 -0700 (PDT) (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 AAA04476; Fri, 15 Oct 1999 00:00:00 -0700 Date: Fri, 15 Oct 1999 00:00:00 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Daniel Eischen Cc: dseg@texar.com, FreeBSD-Hackers@FreeBSD.ORG Subject: Re: Kernel APIs - Solaris In-Reply-To: <199910141859.OAA08821@pcnet1.pcnet.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 Well, whaddya know... thanks... On Thu, 14 Oct 1999, Daniel Eischen wrote: > Matthew Jacob wrote: > > Well, the section 9 man pages are pretty complete. The device driver > > stuff is actually pretty easily available. In fact, this instead of > > performance was supposed to be one of the main design goals for Solaris > > (and I know- I was part of that effort- Gawd, I'm *sorry*.....) > > > > There *is* a DDK- I can't remember the order number off the top of my > > head, but it has enough information to write SCSI target drivers, streams > > modules, pseudo drivers, etc. It misses several important items that > > have been added recently (64 bit clean drivers with a 32 bit user ABI) > > or power mode and/or the rather important DDI_SUSPEND functions for the > > E10K. There's always an option of hiring a consultant. > > All the Sun docs are on-line at http://docs.sun.com/ They are pretty complete, > even explaining the DDI_SUSPEND command at: > > http://docs.sun.com:80/ab2/coll.45.10/DRIVER/@Ab2PageView/37501?Ab2Lang=C&Ab2Enc=iso-8859-1 > > 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 Fri Oct 15 2:10:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id B457A152D7; Fri, 15 Oct 1999 02:10:30 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (grog@localhost) by mojave.lemis.com (8.9.3/8.6.12) id OAA00345; Fri, 15 Oct 1999 14:10:24 +1300 (NZDT) Message-ID: <19991015111024.37498@mojave.lemis.com> Date: Fri, 15 Oct 1999 11:10:24 +1000 From: Greg Lehey To: srii_u1@yahoo.com, FreeBSD Hackers Subject: Re: debugging References: <380579C3.106A39BD@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <380579C3.106A39BD@cisco.com>; from Srinivasan. R on Thu, Oct 14, 1999 at 12:05:48PM +0530 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 14 October 1999 at 12:05:48 +0530, Srinivasan. R wrote: > can you tell me how to debug an application with ptrace systemcall and > how can i fetch the processor register values stored at that particular > moment and how can i access the u-area structure members along with > the address of them. Sorry, I haven't much experience in this. But you'll probably get better results from -hackers. I'm copying this reply there. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html 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 Oct 15 2:24:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id D953915294; Fri, 15 Oct 1999 02:23:49 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id KAA23078 Fri, 15 Oct 1999 10:23:33 +0100 (BST) Message-ID: <3806F294.794B@cs.strath.ac.uk> Date: Fri, 15 Oct 1999 10:23:32 +0100 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: Richard Puga Cc: freebsd-hackers@FreeBSD.ORG, freebsd-multimedia@FreeBSD.ORG Subject: Re: Bt848 based server References: <3806AEA7.61784866@mauibuilt.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Puga wrote: > > Is there any way to use a bt848 as a web cam or streaming video server > through any format other than the metor .ppm > snapshots. Tom, who did the BSDi port, has written code to do this. We has a web cam up and running on his site. I'll grab the sources and put them on the Bt848 driver homepage. When they are there, I'll send another email with the URL Roger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 3: 9:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 3622014FE1 for ; Fri, 15 Oct 1999 03:09:46 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id MAA15217 for ; Fri, 15 Oct 1999 12:09:41 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma015211; Fri, 15 Oct 99 12:09:42 +0200 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 MAA04502 for ; Fri, 15 Oct 1999 12:09:41 +0200 (MET DST) Received: (qmail 83412 invoked by uid 666); 15 Oct 1999 10:10:02 -0000 Date: Fri, 15 Oct 1999 12:10:02 +0200 From: Jos Backus To: freebsd-hackers@freebsd.org Subject: SUIDDIR problem Message-ID: <19991015121002.A82950@hal.mpn.cp.philips.com> Reply-To: Jos Backus Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Maybe this is -questions/-stable material, I'm not sure. Please flame appropriately.] On a very recent -stable system: I have a directory, say /ftp/foocust/in. This directory - resides in a filesystem mounted on /ftp with the suiddir option (with SUIDDIR in the kernel). - is owned by uid root,group ftp - has mode u=rws,g=rwx,o= A user foo, group ftp, puts a file there using ftp (I'm running the stock FreeBSD ftpd). I would expect this file to subsequently become owned by root instead of foo, but nevertheless the file stays owned by foo. What am I doing wrong? Thanks, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ 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 Fri Oct 15 3:15: 4 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 8F19C14FE1 for ; Fri, 15 Oct 1999 03:14:59 -0700 (PDT) (envelope-from eT@post.com) Received: (from root@localhost) by Thingol.KryptoKom.DE (8.9.1/8.9.1) id OAA31393 for ; Fri, 15 Oct 1999 14:09:07 +0200 Received: from cirdan.kryptokom.de by KryptoWall via smtpp (Version 1.2.0) id kwa31391; Fri Oct 15 14:08:58 1999 Received: from post.com ([192.168.6.40]) by cirdan.kryptokom.de (8.9.3/8.8.8) with ESMTP id MAA02602 for ; Fri, 15 Oct 1999 12:20:13 +0200 Message-ID: <3806FFBA.3CEA5755@post.com> Date: Fri, 15 Oct 1999 12:19:39 +0200 From: eT X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Upgrading a different way 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 an installed FreeBSD-2.2.x Release on a Hard disk. Is it possible to upgrade to FreeBSD 3.2 by just copying the distribution files over the existing 2.2.x filesystem? How would the booting issues be overcome: 1. the booting? there is a new booting sequence and it seems like new boot blocks will have to be written to master boot record? eT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 4:46:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from begemot.org (negara.cs.waikato.ac.nz [130.217.248.112]) by hub.freebsd.org (Postfix) with ESMTP id 4B68615361; Fri, 15 Oct 1999 04:45:58 -0700 (PDT) (envelope-from grog@lemis.com) Received: from mojave.lemis.com (modem16.slip.waikato.ac.nz [130.217.97.115]) by begemot.org (8.9.3/8.9.2) with ESMTP id VAA07528; Fri, 15 Oct 1999 21:59:10 +1300 (NZDT) (envelope-from grog@lemis.com) Received: (grog@localhost) by mojave.lemis.com (8.9.3/8.6.12) id OAA00345; Fri, 15 Oct 1999 14:10:24 +1300 (NZDT) Message-ID: <19991015111024.37498@mojave.lemis.com> Date: Fri, 15 Oct 1999 11:10:24 +1000 From: Greg Lehey To: srii_u1@yahoo.com, FreeBSD Hackers Subject: Re: debugging References: <380579C3.106A39BD@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <380579C3.106A39BD@cisco.com>; from Srinivasan. R on Thu, Oct 14, 1999 at 12:05:48PM +0530 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 14 October 1999 at 12:05:48 +0530, Srinivasan. R wrote: > can you tell me how to debug an application with ptrace systemcall and > how can i fetch the processor register values stored at that particular > moment and how can i access the u-area structure members along with > the address of them. Sorry, I haven't much experience in this. But you'll probably get better results from -hackers. I'm copying this reply there. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html 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 Oct 15 5: 6:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from vdslsystems.com (www.vdslsystems.com [194.100.44.117]) by hub.freebsd.org (Postfix) with ESMTP id C7BE8150A3 for ; Fri, 15 Oct 1999 05:05:53 -0700 (PDT) (envelope-from hsu@vdslsystems.com) Received: (from hsu@localhost) by vdslsystems.com (8.9.1/8.9.0) id PAA11434; Fri, 15 Oct 1999 15:06:52 +0300 (EEST) From: Heikki Suonsivu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14343.6364.567743.552931@vdslsystems.com> Date: Fri, 15 Oct 1999 15:06:52 +0300 (EEST) To: freebsd-hackers@freebsd.org Subject: VDSL cards for FreeBSD, any interest ? X-Mailer: VM 6.47 under Emacs 19.34.1 Organization: VDSL Systems Inc, Espoo, Finland Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If any of you are visiting at telecom99 in Geneva, see our booth at hall 8, turn right from the door, it is in the corner. We are presenting VDSL access system and VDSL PCI cards for up to 52 Mbps (13-26Mbps is more realistic in real xDSL environment). All IP, no ATM, so you get good performance and simple deployment. Why in freebsd-hackers: the access system is built on (Free)BSD, and the VDSL modem cards are drop-in for FreeBSD-based applications. We do offer the cards for OEM market if there is interest. Feedback appreciated, please mail hsu@vdslsystems.com. -- Heikki Suonsivu / Taysikuu 10 C 83 / FI-02150 Espoo / FINLAND, hsu@vdslsystems.com mobile +358-40-5519679 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 5: 9:54 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 09F2415017 for ; Fri, 15 Oct 1999 05:09:51 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id OAA32351; Fri, 15 Oct 1999 14:09:48 +0200 (CEST) (envelope-from des) To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Determine # of open files via fdesc References: From: Dag-Erling Smorgrav Date: 15 Oct 1999 14:09:47 +0200 In-Reply-To: Zhihui Zhang's message of "Thu, 14 Oct 1999 16:58:38 -0400 (EDT)" Message-ID: Lines: 29 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zhihui Zhang writes: > I do not know whether it is a good idea to determine the number of open > files of a process by enabling fdesc in the kernel. Anyway, I do the > following: > > # mount_fdesc -o union fdesc /dev > # ls -al /dev/fd > list > > cat list > total 1 > crw------- 1 root tty 12, 0 Oct 15 17:09 0 > -rw-r--r-- 1 root wheel 0 Oct 15 17:09 1 > crw------- 1 root tty 12, 0 Oct 15 17:09 2 > drw-r--r-- 5 root wheel 1024 Oct 15 17:09 3 > dr--r--r-- 2 root wheel 512 Oct 15 16:28 4 > > I do not know why 3 and 4 are labeled as directory. 1 was labeled as > character device but is changed probably by the redirection >. I run a > small program to open three files and run forever in the background. After > this, I expect to see three more items under /dev/fd, but there are not. > Can anyone explain this to me? Each process only sees its own file descriptors. The five descriptors you see above belong to ls. 0 (stdin) and 2 (stderr) are whichever tty or pty you typed this into, 1 (stdout) is the file you redirected the output from ls into, 3 is /dev and 4 is /dev/fd. 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 Fri Oct 15 5:10:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ctlmailgw.comptel.com (ctlmailgw.comptel.com [192.102.20.151]) by hub.freebsd.org (Postfix) with ESMTP id 7811515384 for ; Fri, 15 Oct 1999 05:10:32 -0700 (PDT) (envelope-from stefan.parvu@comptel.com) Received: from mgw-in.comptel.com (unverified [192.102.20.150]) by ctlmailgw.comptel.com (Data Fellows SMTPRS 2.04) with ESMTP id ; Fri, 15 Oct 1999 15:03:23 +0300 Received: from xf174 ([195.237.135.174]) by mgw-in.comptel.com with Microsoft SMTPSVC(5.5.1877.197.19); Fri, 15 Oct 1999 15:03:49 +0300 Message-Id: <3.0.6.32.19991015161001.0097c580@miina.comptel.com> X-Sender: sparvu@miina.comptel.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 15 Oct 1999 16:10:01 -0700 To: Heikki Suonsivu , freebsd-hackers@FreeBSD.ORG From: Stefan Parvu Subject: Re: VDSL cards for FreeBSD, any interest ? In-Reply-To: <14343.6364.567743.552931@vdslsystems.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Well I am in Helsinki and it's good to hear about this. What about prices ? VDSL PCI Stef At 03:06 PM 10/15/99 +0300, Heikki Suonsivu wrote: > >If any of you are visiting at telecom99 in Geneva, see our booth at hall 8, >turn right from the door, it is in the corner. We are presenting VDSL >access system and VDSL PCI cards for up to 52 Mbps (13-26Mbps is more >realistic in real xDSL environment). All IP, no ATM, so you get good >performance and simple deployment. > >Why in freebsd-hackers: the access system is built on (Free)BSD, and the >VDSL modem cards are drop-in for FreeBSD-based applications. We do offer >the cards for OEM market if there is interest. Feedback appreciated, >please mail hsu@vdslsystems.com. > >-- >Heikki Suonsivu / Taysikuu 10 C 83 / FI-02150 Espoo / FINLAND, >hsu@vdslsystems.com mobile +358-40-5519679 > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 5:12:13 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 6528515081 for ; Fri, 15 Oct 1999 05:12:10 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id OAA32380; Fri, 15 Oct 1999 14:12:08 +0200 (CEST) (envelope-from des) To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Determine # of open files via fdesc References: From: Dag-Erling Smorgrav Date: 15 Oct 1999 14:12:08 +0200 In-Reply-To: Dag-Erling Smorgrav's message of "15 Oct 1999 14:09:47 +0200" Message-ID: Lines: 11 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > Each process only sees its own file descriptors. The five descriptors > you see above belong to ls. 0 (stdin) and 2 (stderr) are whichever tty > or pty you typed this into, 1 (stdout) is the file you redirected the > output from ls into, 3 is /dev and 4 is /dev/fd. OBTW, this is adequately documented in the fdesc(5) man page. 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 Fri Oct 15 6:23:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 5D50014CA3 for ; Fri, 15 Oct 1999 06:23:28 -0700 (PDT) (envelope-from babolo@links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id RAA22353 for freebsd-hackers@FreeBSD.ORG; Fri, 15 Oct 1999 17:24:12 +0400 (MSD) Message-Id: <199910151324.RAA22353@aaz.links.ru> Subject: how mkdir without .. ? To: freebsd-hackers@FreeBSD.ORG Date: Fri, 15 Oct 1999 17:24:12 +0400 (MSD) From: "Aleksandr A.Babaylov" 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 need in directories without link to parent in it or with link to parent renamed to something exotic name. What is the method to do it without kernel patching in FreeBSD 2.2.X or 3.X ? -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 8: 2:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ockle.nanoteq.co.za (ockle.nanoteq.co.za [196.37.91.54]) by hub.freebsd.org (Postfix) with ESMTP id 8498714A05 for ; Fri, 15 Oct 1999 08:01:41 -0700 (PDT) (envelope-from jkruger@oskar.nanoteq.co.za) Received: from oskar.nanoteq.co.za (localhost.nanoteq.co.za [127.0.0.1]) by ockle.nanoteq.co.za (8.9.3/8.9.3) with ESMTP id RAA61831 for ; Fri, 15 Oct 1999 17:00:18 +0200 (SAST) (envelope-from jkruger@oskar.nanoteq.co.za) Message-ID: <38074180.682FA436@oskar.nanoteq.co.za> Date: Fri, 15 Oct 1999 17:00:16 +0200 From: Johan Kruger Reply-To: jkruger@oskar.nanoteq.co.za Organization: Nanoteq X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: kmem_suballoc: bad status return of 3 ?? Content-Type: multipart/mixed; boundary="------------C485C0785EFBECF15C2DBD83" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------C485C0785EFBECF15C2DBD83 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I get this error when booting with a 2.2.8 kernel with maxusers = 2000 which is greater than 512. I compiled a 2.2.6 and 2.2.7 kernel before with 2000 users with no problem. If i decrease the maxusers to say 256 then it works, so i guess something has changed with the calculation of the mbufs and such. I looked in vm_kern.c from where the error is generated and in param.c which use MAXUSERS to determine some stuff. Any help on this subject will be appreciated. --------------C485C0785EFBECF15C2DBD83 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:;0 fn:Johan Kruger end:vcard --------------C485C0785EFBECF15C2DBD83-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 8:30: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f305.hotmail.com [207.82.251.218]) by hub.freebsd.org (Postfix) with SMTP id 4493515408 for ; Fri, 15 Oct 1999 08:30:04 -0700 (PDT) (envelope-from gupz@hotmail.com) Received: (qmail 54338 invoked by uid 0); 15 Oct 1999 15:30:03 -0000 Message-ID: <19991015153003.54337.qmail@hotmail.com> Received: from 161.44.52.23 by www.hotmail.com with HTTP; Fri, 15 Oct 1999 08:30:03 PDT X-Originating-IP: [161.44.52.23] From: "Dodge Ram" To: freebsd-hackers@freebsd.org Subject: Handling segV's Date: Fri, 15 Oct 1999 08:30:03 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am looking at ways to handle segV's gracefully without letting a process die. I am aware of the siglongjmp() call and don't know if that is the only way to handle segV's Any pointers on how to gracefully (?) handle segV and not letting the process die will be of great help. Also, given that I have a solution to test, what are all the ways I can ensure that my process handles segV's rightly ? thanks and regards, ramC ______________________________________________________ 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 Fri Oct 15 9: 2:21 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 E6F0F14D66 for ; Fri, 15 Oct 1999 09:02:05 -0700 (PDT) (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 IAA03342; Fri, 15 Oct 1999 08:52:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910151552.IAA03342@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: jkruger@oskar.nanoteq.co.za Cc: freebsd-hackers@freebsd.org Subject: Re: kmem_suballoc: bad status return of 3 ?? In-reply-to: Your message of "Fri, 15 Oct 1999 17:00:16 +0200." <38074180.682FA436@oskar.nanoteq.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Oct 1999 08:52:42 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I get this error when booting with a 2.2.8 kernel with maxusers = 2000 > which is greater than 512. 2000 is a completely insane value for maxusers. 256 is pushing it for a 2.2.x family kernel as well. Stick with 64 or 128 and tune the other items that you actually _need_. -- \\ 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 Oct 15 9: 6:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id D883C15462 for ; Fri, 15 Oct 1999 09:06:17 -0700 (PDT) (envelope-from gram@cequrux.com) Received: (from nobody@localhost) by citadel.cequrux.com (8.9.3/8.9.3) id SAA17797; Fri, 15 Oct 1999 18:05:31 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 17793; Fri Oct 15 18:04:49 1999 From: Graham Wheeler To: "Dodge Ram" , freebsd-hackers@FreeBSD.ORG Subject: Re: Handling segV's Date: Fri, 15 Oct 1999 17:57:58 +0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <19991015153003.54337.qmail@cequrux.com> In-Reply-To: <19991015153003.54337.qmail@cequrux.com> MIME-Version: 1.0 Message-Id: <9910151800080A.11153@cequrux.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 15 Oct 1999, Dodge Ram wrote: > Hi, > > I am looking at ways to handle segV's gracefully without > letting a process die. I am aware of the siglongjmp() call and don't > know if that is the only way to handle segV's > > Any pointers on how to gracefully (?) handle segV and not > letting the process die will be of great help. > > Also, given that I have a solution to test, what are all the > ways I can ensure that my process handles segV's rightly ? Well, you can't return from the signal handler, as that will just cause the SEGV again. Also, you shouldn't do any heap manipulation from within the signal handler (that may have changed now that there is thread support, but certainly in older systems these routines are no re-entrant). So that will limit your options considerably... -- Dr Graham Wheeler E-mail: gram@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data/Network Security Specialists WWW: http://www.cequrux.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 9:22:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id B921914A18 for ; Fri, 15 Oct 1999 09:22:50 -0700 (PDT) (envelope-from gram@cequrux.com) Received: (from nobody@localhost) by citadel.cequrux.com (8.9.3/8.9.3) id SAA19047 for ; Fri, 15 Oct 1999 18:22:49 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 18981; Fri Oct 15 18:22:25 1999 From: Graham Wheeler To: hackers@freebsd.org Subject: ISA Plug 'n Play support / kernel -c bug / IETF Date: Fri, 15 Oct 1999 18:12:25 +0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <9910151817440B.11153@cequrux.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all While PCI plug 'n play devices seem to work nicely with FreeBSD, we find that ISA ones are not detected and that we have to configure them as though they are not plug 'n play. Is the pnp0 controller in the kernel config for PCI only? Or is there a way to get the ISA ones to be automagically detected upon bootup? Maybe with some BIOS tweak? On a different note, we have noticed with 3.2 FreeBSD that changes made to the kernel config upon bootup are not recorded to the disk image (even though the message `saving kernel -c changes' appears during the boot sequence). Is this a 3.2 specific bug that is fiixed in 3.3? And on a final note - are any of the FreeBSD hackers going to the IETF meet in November? It would be good to meet some of the crew... ta gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data/Network Security Specialists WWW: http://www.cequrux.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 9:27: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from D2SI.COM (D2SI.COM [63.224.10.2]) by hub.freebsd.org (Postfix) with ESMTP id E4B2214CFC for ; Fri, 15 Oct 1999 09:26:55 -0700 (PDT) (envelope-from ajk@paw-in-eye.net) Received: (from ajk@localhost) by D2SI.COM (8.9.3/8.9.3) id LAA25438; Fri, 15 Oct 1999 11:23:37 -0500 (CDT) (envelope-from ajk) From: Alec Kloss Message-Id: <199910151623.LAA25438@D2SI.COM> Subject: Re: Handling segV's In-Reply-To: <19991015153003.54337.qmail@hotmail.com> from Dodge Ram at "Oct 15, 1999 8:30: 3 am" To: gupz@hotmail.com (Dodge Ram) Date: Fri, 15 Oct 1999 11:23:37 -0500 (CDT) 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 Dodge Ram said: > Hi, > > I am looking at ways to handle segV's gracefully without > letting a process die. I am aware of the siglongjmp() call and don't > know if that is the only way to handle segV's > > Any pointers on how to gracefully (?) handle segV and not > letting the process die will be of great help. > > Also, given that I have a solution to test, what are all the > ways I can ensure that my process handles segV's rightly ? > > thanks and regards, > > ramC > Attempting to recover from a SIGSEGV seems like a very risky proposition. Essentially, ANY writeable memory by the process may have been clobbered before the process decided to write to read-only memory generating the SIGSEGV. Suppose you recover and longjump somewhere and then flush your IO buffers out to disk. For all you know, the buffers are now total garbage, so now you have a running program working with incorrect data on disk. Yikes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 10: 7: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f16.hotmail.com [207.82.250.27]) by hub.freebsd.org (Postfix) with SMTP id 87A2315029 for ; Fri, 15 Oct 1999 10:07:01 -0700 (PDT) (envelope-from gupz@hotmail.com) Received: (qmail 19287 invoked by uid 0); 15 Oct 1999 17:07:00 -0000 Message-ID: <19991015170700.19286.qmail@hotmail.com> Received: from 161.44.52.23 by www.hotmail.com with HTTP; Fri, 15 Oct 1999 10:07:00 PDT X-Originating-IP: [161.44.52.23] From: "Dodge Ram" To: ajk@paw-in-eye.net, gupz@hotmail.com Cc: freebsd-hackers@freebsd.org Subject: Re: Handling segV's Date: Fri, 15 Oct 1999 10:07:00 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Theoretically, if I have backup's of all the relevant data structures, and I clear out all the process's memory(the one receiving the segV) and datastrcutures and restore from the backup store, is that a safe approach ? Will that minimize me hitting the segV again. Also, is there a list of reasons for a SIGSEGV ? thanks and regards, ramesh >From: Alec Kloss >To: gupz@hotmail.com (Dodge Ram) >CC: freebsd-hackers@freebsd.org >Subject: Re: Handling segV's >Date: Fri, 15 Oct 1999 11:23:37 -0500 (CDT) > >Dodge Ram said: > > > Hi, > > > > I am looking at ways to handle segV's gracefully without > > letting a process die. I am aware of the siglongjmp() call and don't > > know if that is the only way to handle segV's > > > > Any pointers on how to gracefully (?) handle segV and not > > letting the process die will be of great help. > > > > Also, given that I have a solution to test, what are all the > > ways I can ensure that my process handles segV's rightly ? > > > > thanks and regards, > > > > ramC > > > >Attempting to recover from a SIGSEGV seems like a very risky proposition. >Essentially, ANY writeable memory by the process may have been >clobbered before the process decided to write to read-only memory >generating the SIGSEGV. Suppose you recover and longjump somewhere >and then flush your IO buffers out to disk. For all you know, the >buffers are now total garbage, so now you have a running program >working with incorrect data on disk. > >Yikes. > ______________________________________________________ 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 Fri Oct 15 10:10: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 B94C31511F for ; Fri, 15 Oct 1999 10:10:50 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id KAA13379; Fri, 15 Oct 1999 10:09:25 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Fri, 15 Oct 1999 10:09:25 -0700 Date: Fri, 15 Oct 1999 10:09:24 -0700 (PDT) From: Kip Macy X-Sender: kip@luna To: Alec Kloss Cc: Dodge Ram , freebsd-hackers@freebsd.org Subject: Re: Handling segV's In-Reply-To: <199910151623.LAA25438@D2SI.COM> 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: ajk@paw-in-eye.net,gupz@hotmail.com,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 DDD somehow manages to do this, however, even if you tell it to ignore it and continue it will almost invariably segV again shortly thereafter. -Kip On Fri, 15 Oct 1999, Alec Kloss wrote: > Dodge Ram said: > > > Hi, > > > > I am looking at ways to handle segV's gracefully without > > letting a process die. I am aware of the siglongjmp() call and don't > > know if that is the only way to handle segV's > > > > Any pointers on how to gracefully (?) handle segV and not > > letting the process die will be of great help. > > > > Also, given that I have a solution to test, what are all the > > ways I can ensure that my process handles segV's rightly ? > > > > thanks and regards, > > > > ramC > > > > Attempting to recover from a SIGSEGV seems like a very risky proposition. > Essentially, ANY writeable memory by the process may have been > clobbered before the process decided to write to read-only memory > generating the SIGSEGV. Suppose you recover and longjump somewhere > and then flush your IO buffers out to disk. For all you know, the > buffers are now total garbage, so now you have a running program > working with incorrect data on disk. > > Yikes. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 10:30:22 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 3F75514C20 for ; Fri, 15 Oct 1999 10:30:18 -0700 (PDT) (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 KAA67916; Fri, 15 Oct 1999 10:29:05 -0700 (PDT) Date: Fri, 15 Oct 1999 10:29:04 -0700 (PDT) From: Julian Elischer To: Jos Backus Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SUIDDIR problem In-Reply-To: <19991015121002.A82950@hal.mpn.cp.philips.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 SUIDDIR will work for any user EXCEPT ROOT I did this because I felt it was a security hole to allow users to create files owned by root. (from memory it will also refuse to do files that have the execute bit set but I can't remember for sure) We use it all the time on our PC fileservers so that DOS users always own the files in their dropbox directories but they can give each other files (e.g. documents). On Fri, 15 Oct 1999, Jos Backus wrote: > [Maybe this is -questions/-stable material, I'm not sure. Please flame > appropriately.] > > On a very recent -stable system: > > I have a directory, say /ftp/foocust/in. This directory > - resides in a filesystem mounted on /ftp with the suiddir option > (with SUIDDIR in the kernel). > - is owned by uid root,group ftp > - has mode u=rws,g=rwx,o= > > A user foo, group ftp, puts a file there using ftp (I'm running the stock > FreeBSD ftpd). I would expect this file to subsequently become owned by root > instead of foo, but nevertheless the file stays owned by foo. > > What am I doing wrong? Nothing, they just can't be owned by root. > > Thanks, > -- > Jos Backus _/ _/_/_/ "Reliability means never > _/ _/ _/ having to say you're sorry." > _/ _/_/_/ -- D. J. Bernstein > _/ _/ _/ _/ > Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 11: 3:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from colnta.acns.ab.ca (clgr000532.hs.telusplanet.net [161.184.82.24]) by hub.freebsd.org (Postfix) with ESMTP id F38DA151A1 for ; Fri, 15 Oct 1999 11:03:06 -0700 (PDT) (envelope-from davidc@colnta.acns.ab.ca) Received: from localhost (davidc@localhost) by colnta.acns.ab.ca (8.9.3/8.9.3) with ESMTP id MAA16842 for ; Fri, 15 Oct 1999 12:03:05 -0600 (MDT) (envelope-from davidc@colnta.acns.ab.ca) Date: Fri, 15 Oct 1999 12:03:05 -0600 (MDT) From: Chad David To: freebsd-hackers@freebsd.org Subject: FreeBSD hackers (fwd) 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 was asked this question today, and searching the mailing lists doesn't bring up anything current. Has any additional work been done on if_vlan? From the cvs headers in if_vlan.c is appears there has, so would FreeBSD work in this situation? A number of interface man pages (ti(4), sk(4)) mention vlan(4) which doesn't exist on any of our stable or current machines. Also I found vlan.h in the compile directory (NVLAN = 0 by default), but didn't find anything obvious in LINT for adding a vlan interface. Any pointers in the right direction would be appreciated. Thanks Chad. QUESTION: Chad, I'm looking for vlan trunking support in FreeBSD. There are currently two protocols used for vlan trunking: ISL (cisco) and 802.1q (open standard). Either would work fine for me. I want to have one 100BaseTX ethernet port that trunks multiple vlans from a Cisco switch to a FreeBSD DHCP server. The FreeBSD server would have one subinterfaces or aliases per vlan assigned to the trunk. The configuration would look like the following: Cat ----- 100baseTX,FD ---------- FreeBSD Server Switch Vlans 1,3,7 -- ========================================================================= Clinton Work work@scripty.com Calgary, Alberta To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 11:27:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194]) by hub.freebsd.org (Postfix) with ESMTP id C1AB8153A4 for ; Fri, 15 Oct 1999 11:27:10 -0700 (PDT) (envelope-from sa-list@avantgo.com) Received: from avantgo.com ([10.0.128.109]) by bomber.avantgo.com (Netscape Messaging Server 3.5) with ESMTP id 384; Fri, 15 Oct 1999 11:21:38 -0700 Message-ID: <380771FE.3CC44A0B@avantgo.com> Date: Fri, 15 Oct 1999 11:27:10 -0700 From: Stevan Arychuk Reply-To: sa-list@avantgo.com Organization: AvantGo Inc. X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: dg@root.com Cc: FreeBSD-hackers@FreeBSD.ORG Subject: Re: SMP + fxp0 wierdness References: <199910121014.DAA16112@implode.root.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would be more than willing to do run some hardware tests in our lab enviroment here, but our main problem is that we can't acurately reproduce the problem. The reboots seem to happen maybe 3-4 times a week from a pool of about 7 machines. I'm not sure if someone could write a piece of code that would do it, but it's definately beyond me. - Stevan Stevan Arychuk AvantGo Inc. stevan@avantgo.com David Greenman wrote: > > >David Greenman wrote: > >> > >> >> So if this problem is NOT related to specific hardware, how can we get > >> >> the driver fixed? > >> > > >> >Talk to the maintainer (David). We've offered him cores and kernels > >> >before. Alternatively, you'll need to experiment with your setup to > >> >determine what characterises the failures and help David out with more > >> >data. > >> > >> Hotmail has troubleshooted the problem down to the NCR controller. It > >> appears that the problem only occurs when using one of those. If they plug > >> in an Adaptec 2940 and use it instead of the onboard NCR then the problems > >> disappear. > > > > Well that's not good, since I have almost convinced my boss to replace > >the crappy IDE drives on our shiny new Intel N440BX mb's with scsi > >drives since the controller is built in. :-/ Does this look like a > >soluble problem, or is it just going to be a case of "don't do that?" > >Anything I can do to help mail me and let me know. > > Intel generally makes good stuff. On the other hand, I'm not too happy with > the NCR/Symbios support in FreeBSD...the conversion to CAM wasn't all that > great and the driver really needs a rewrite. I wouldn't personally put a > machine with an NCR/Symbios into production - I have just too much negative > history with it. > I don't understand why some machines are having this problem with the Intel > Pro/100B/100+ and (most) others never do. All indications right now is that it > is a DMA corruption problem of some kind, but I don't have any clue what might > be causing it. I don't think it is a software bug, but it's conceivable that > the problem could be worked around with software if I knew what was causing > it. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org > Creator of high-performance Internet servers - http://www.terasolutions.com > Pave the road of life with opportunities. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 12:18:19 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 E76C914D5D for ; Fri, 15 Oct 1999 12:18:15 -0700 (PDT) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl4.philips.com with ESMTP id VAA24059 for ; Fri, 15 Oct 1999 21:18:13 +0200 (MEST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl4.philips.com via mwrap (4.0a) id xma024057; Fri, 15 Oct 99 21:18:13 +0200 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 VAA21234 for ; Fri, 15 Oct 1999 21:18:12 +0200 (MET DST) Received: (qmail 98620 invoked by uid 666); 15 Oct 1999 19:18:34 -0000 Date: Fri, 15 Oct 1999 21:18:34 +0200 From: Jos Backus To: Julian Elischer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SUIDDIR problem Message-ID: <19991015211834.B91574@hal.mpn.cp.philips.com> Reply-To: Jos Backus References: <19991015121002.A82950@hal.mpn.cp.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 15, 1999 at 10:29:04AM -0700, Julian Elischer wrote: > SUIDDIR will work for any user EXCEPT ROOT Ahh I see, a big thanks to you Julian! OK, I'll use a different userid, say, bar (and make the directory sticky so foo cannot remove the file it just created - it will be owned by bar). Cheers, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ 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 Fri Oct 15 12:49: 1 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 AD439153C3 for ; Fri, 15 Oct 1999 12:48:57 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p28-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.157]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id EAA13967; Sat, 16 Oct 1999 04:48:29 +0900 (JST) Message-ID: <380783FD.789DFD8C@newsguy.com> Date: Sat, 16 Oct 1999 04:43:57 +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: Graham Wheeler Cc: hackers@FreeBSD.ORG Subject: Re: ISA Plug 'n Play support / kernel -c bug / IETF References: <9910151817440B.11153@cequrux.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Graham Wheeler wrote: > > On a different note, we have noticed with 3.2 FreeBSD that changes made to > the kernel config upon bootup are not recorded to the disk image (even though > the message `saving kernel -c changes' appears during the boot sequence). > Is this a 3.2 specific bug that is fiixed in 3.3? mmmmm.... I thought this was mentioned in the 3.2 Release Notes or 3.2 errata. Well, maybe it only appeared in the 3.1 errata, *BUT*, if it was, and you just have failed to read them, you might be interested in seeing some new pointy hat models I just received. :-) Anyway, man loader.conf(5), or just check /boot/defaults/loader.conf, and create a /boot/loader.conf with the appropriate line. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 14:10:41 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 F091F15408 for ; Fri, 15 Oct 1999 14:10:35 -0700 (PDT) (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 WAA96291; Fri, 15 Oct 1999 22:11:19 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 15 Oct 1999 22:11:19 +0100 (BST) From: Doug Rabson To: Graham Wheeler Cc: hackers@freebsd.org Subject: Re: ISA Plug 'n Play support / kernel -c bug / IETF In-Reply-To: <9910151817440B.11153@cequrux.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 Fri, 15 Oct 1999, Graham Wheeler wrote: > Hi all > > While PCI plug 'n play devices seem to work nicely with FreeBSD, we find > that ISA ones are not detected and that we have to configure them as though > they are not plug 'n play. Is the pnp0 controller in the kernel config for PCI > only? Or is there a way to get the ISA ones to be automagically detected > upon bootup? Maybe with some BIOS tweak? 4.0 will have a complete PnP system, including automagic detection and configuration, support for pnpbios (and probably acpi). The code is in -current now and being tested. By the time 4.0 ships we should have enough drivers so that you can have a kernel config with *no* custom settings at all and it will detect all your hardware magically. -- 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 Fri Oct 15 15:46:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.dti.ne.jp (smtp.dti.ne.jp [210.170.128.120]) by hub.freebsd.org (Postfix) with ESMTP id 93F1C153A0 for ; Fri, 15 Oct 1999 15:46:45 -0700 (PDT) (envelope-from shigio@tamacom.com) Received: from choota.signet.or.jp (PPP84.tama-ap5.dti.ne.jp [210.170.192.102]) by smtp.dti.ne.jp (8.9.0/3.7W) with ESMTP id HAA18289; Sat, 16 Oct 1999 07:46:43 +0900 (JST) Received: from choota.signet.or.jp (localhost [127.0.0.1]) by choota.signet.or.jp (8.8.8/) with ESMTP id HAA10317; Sat, 16 Oct 1999 07:43:22 +0900 (JST) Message-Id: <199910152243.HAA10317@tamacom.com> To: hackers@FreeBSD.ORG Cc: shigio@tamacom.com Subject: Re: Search a symbol in the source tree Date: Sat, 16 Oct 1999 07:43:22 +0900 From: Shigio Yamaguchi Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Darryl Okahata wrote: > Looking for where "utmp.h" is used: > > global -x -s utmp.h > > This takes more than 2212 seconds (over 36 minutes!), and outputs It seems that something wrong (bug?) occurred. Would you please tell me the version of FreeBSD and GLOBAL? > This runs quickly, but displays nothing. Next, try: > > global -x -s KBD_DATA_PORT > > This runs quickly, and shows where this is used in .c source files. > However, where's the definition? It's not shown. It's a bug that appeared between GLOBAL-3.3 and 3.44 and fixed in 3.5. -- Shigio Yamaguchi - Tama Communications Corporation Mail: shigio@tamacom.com, WWW: http://www.tamacom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 16:40:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 17DB11517E for ; Fri, 15 Oct 1999 16:40:35 -0700 (PDT) (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 IAA03397; Fri, 15 Oct 1999 08:56:51 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910151556.IAA03397@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey Cc: srii_u1@yahoo.com, FreeBSD Hackers Subject: Re: debugging In-reply-to: Your message of "Fri, 15 Oct 1999 11:10:24 +1000." <19991015111024.37498@mojave.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Oct 1999 08:56:50 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thursday, 14 October 1999 at 12:05:48 +0530, Srinivasan. R wrote: > > can you tell me how to debug an application with ptrace systemcall and > > how can i fetch the processor register values stored at that particular > > moment and how can i access the u-area structure members along with > > the address of them. > > Sorry, I haven't much experience in this. But you'll probably get > better results from -hackers. I'm copying this reply there. The short answer is "use gdb". The slightly longer answer is "read ptrace(2)". -- \\ 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 Oct 15 17:29:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from genie.gene.com (genie-open.gene.com [192.12.78.1]) by hub.freebsd.org (Postfix) with ESMTP id 0491114E1F for ; Fri, 15 Oct 1999 17:29:10 -0700 (PDT) (envelope-from elhauge@gene.com) Received: from kin.gene.com (kin.gene.com [128.137.49.57]) by genie.gene.com (8.9.3/8.9.1) with ESMTP id RAA18470 for ; Fri, 15 Oct 1999 17:29:10 -0700 (PDT) Received: from gene.com (dhcp194-152.gene.com [128.137.194.152]) by kin.gene.com (8.9.3/8.9.1) with ESMTP id RAA18234 for ; Fri, 15 Oct 1999 17:29:07 -0700 (PDT) Message-ID: <3807C6D3.A7126CE1@gene.com> Date: Fri, 15 Oct 1999 17:29:07 -0700 From: Edward Elhauge Organization: Genentech, Inc. X-Sender: "Edward Elhauge" X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: FreeBSD and HP Jornado 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 been thinking about getting an HP Jornado instead of either a Notebook PC or a Palm Pilot. I wonder what people out in FreeBSD land know about interfacing the Jornado with FreeBSD or Linux. The Jornado is a CE machine. Are there Unix utilities to synchronize the file systems? I know there is a lot of support for Palm Pilots but I want to take notes via touch typing. My other questions is if is a way of replacing the CE OS with something easier to customize and that might run either Perl or Java? -- Edward Elhauge | "Pollution is a symptom of man's Uncanny Inc., San Francisco | inability to transform waste." | -- Patti Smith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 18:37:27 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 E634E14D5D for ; Fri, 15 Oct 1999 18:37:24 -0700 (PDT) (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 VAA21962 for ; Fri, 15 Oct 1999 21:37:22 -0400 (EDT) Date: Fri, 15 Oct 1999 20:34:45 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: Status of UMAPFS 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 Is the UMAPFS working? I add "options UMAPFS" to the configuration file of FreeBSD 3.3-Release and rebuilt the kernel. I got the following errors: loading kernel umap_vnops.o: In function `umap_lock': umap_vnops.o(.text+0x568): undefined reference to `null_bypass' umap_vnops.o: In function `umap_unlock': umap_vnops.o(.text+0x58e): undefined reference to `null_bypass' *** Error code 1 Stop. 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 Fri Oct 15 18:40:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.multinet-media.com (ns1.multinet-media.com [207.18.212.40]) by hub.freebsd.org (Postfix) with ESMTP id B0A6214D22 for ; Fri, 15 Oct 1999 18:40:37 -0700 (PDT) (envelope-from drew@multinet-media.com) Received: from multinet-media.com (231door249.door.net [208.234.231.249]) by ns1.multinet-media.com (8.8.8/8.8.8) with ESMTP id BAA09142 for ; Sat, 16 Oct 1999 01:34:59 -0500 (CDT) (envelope-from drew@multinet-media.com) Message-ID: <3807817E.98654568@multinet-media.com> Date: Fri, 15 Oct 1999 20:33:18 +0100 From: Drew Wiggins Organization: MultiNetMedia X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: Mailing list not Content-Type: multipart/mixed; boundary="------------D79CE06F32C410DA7AD71A2A" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------D79CE06F32C410DA7AD71A2A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit reverse name resolution is not working outside of your own name servers... ex. ######################################################### % nslookup Default Server: localhost.multinet-media.com Address: 127.0.0.1 > server ns2.uncanny.net Default Server: ns2.uncanny.net Address: 140.174.20.7 > 140.174.20.7 Server: ns2.uncanny.net Address: 140.174.20.7 Name: ns2.uncanny.net Address: 140.174.20.7 > server ns1.root.com Default Server: ns1.root.com Address: 209.102.106.178 > 140.174.20.7 Server: ns1.root.com Address: 209.102.106.178 *** ns1.root.com can't find 140.174.20.7: Server failed ######################################################### whoever is responsible for the IP block(s, classes) you are using would need to add PTR records; as they are the authority ( there is a record for ns1 ). Having reverse lookup on your own nameservers is a good thing to have, but that's not where the rest of the world is going to query from, unless they're using your DNS. or supposedly an entry like... 140.174.20.254 IN NS ns2.uncanny.net. in the 20.174.140.in-addr records ( on the providers nameserver ) will work. This would (supposedly) cause remote queries to be redirected to your namesever. I've never tried it, though. Good Luck, -Drew Edward Elhauge wrote: > I'm getting the following message when I try to post to the > freebsd-hackers list from uncanny.net. > > -- Ed Elhauge > > =========== START of ERROR MAIL =================== > The original message was received at Fri, 15 Oct 1999 02:23:43 -0700 > (PDT) > from sandbox.uncanny.net [140.174.20.254] > > ----- The following addresses had transient non-fatal errors ----- > > > ----- Transcript of session follows ----- > ... while talking to hub.freebsd.org.: > >>> EHLO ns2.uncanny.net > <<< 450 Cannot find your hostname, [140.174.20.7] > ... Deferred: 450 Cannot find your > hostname, [140.1 > 74.20.7] > Warning: message still undelivered after 4 hours > Will keep trying until message is 5 days old > ==============END of ERROR MAIL =========================== > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message --------------D79CE06F32C410DA7AD71A2A Content-Type: text/x-vcard; charset=us-ascii; name="drew.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Drew Wiggins Content-Disposition: attachment; filename="drew.vcf" begin:vcard n:Wiggins;John tel;cell:(806) 786-2764 tel;fax:(806) 472-0858 tel;home:(806) 786-2764 tel;work:(806) 791-9993 x-mozilla-html:TRUE url:http://www.MultiNet-Media.com/ org:MultiNetMedia;Operations version:2.1 email;internet:drew@multinet-media.com title:IT Director adr;quoted-printable:;;1316 27th Street=0D=0A;Lubbock;TX ;79405;USA x-mozilla-cpt:;15408 fn:Drew Wiggins end:vcard --------------D79CE06F32C410DA7AD71A2A-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 20: 6:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 84D5F14C86 for ; Fri, 15 Oct 1999 20:06:08 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id MAA67986; Sat, 16 Oct 1999 12:35:57 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199910160305.MAA67986@gizmo.internode.com.au> Subject: Re: Handling segV's To: gupz@hotmail.com (Dodge Ram) Date: Sat, 16 Oct 1999 12:35:57 +0930 (CST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <19991015170700.19286.qmail@hotmail.com> from "Dodge Ram" at Oct 15, 99 10:07:00 am X-Mailer: ELM [version 2.4 PL25] 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 Dodge Ram wrote: > Also, is there a list of reasons for a SIGSEGV ? Only one: "Your program is buggy" :-) - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 15 21:56:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 6FC4814E74 for ; Fri, 15 Oct 1999 21:56:40 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from root@localhost) by celery.dragondata.com (8.9.3/8.9.3) id XAA21178; Fri, 15 Oct 1999 23:57:19 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199910160457.XAA21178@celery.dragondata.com> Subject: Re: Handling segV's To: newton@internode.com.au (Mark Newton) Date: Fri, 15 Oct 1999 23:57:19 -0500 (CDT) Cc: gupz@hotmail.com (Dodge Ram), freebsd-hackers@FreeBSD.ORG In-Reply-To: <199910160305.MAA67986@gizmo.internode.com.au> from "Mark Newton" at Oct 16, 1999 12:35:57 PM X-Mailer: ELM [version 2.5 PL1] 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 > > Dodge Ram wrote: > > > Also, is there a list of reasons for a SIGSEGV ? > > Only one: "Your program is buggy" :-) > > - mark I've actually got a SIGSEGV/SIGBUS handler in one of my programs that I needed, and couldn't figure a way around... I mmap() files in, then copy them to a device. This works great except when someone tries to change that file during the copy. If the size of the file shrinks, I'll SIGBUS or SIGSEGV when i try to touch past the new file size. So, i setup a signal handler and longjmp into some recovery code. Perhaps there's a better way, but I don't consider this a bug really, and i'll get a SEGV. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 0:51:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from topsecret.blackprojects.org (host249.dinnaken.com [207.109.8.249]) by hub.freebsd.org (Postfix) with ESMTP id A6E1D14D11 for ; Sat, 16 Oct 1999 00:51:36 -0700 (PDT) (envelope-from griffin@blackprojects.org) Received: from vortex (gary [207.109.8.98]) by topsecret.blackprojects.org (8.9.3/8.9.3) with ESMTP id CAA03650 for ; Sat, 16 Oct 1999 02:51:31 -0500 (CDT) (envelope-from griffin@blackprojects.org) Message-ID: <199910160251370480.0B9DA297@207.109.8.249> X-Mailer: Calypso Version 3.00.00.14 (2) Date: Sat, 16 Oct 1999 02:51:37 -0500 From: "Jimbo Bahooli" To: freebsd-hackers@freebsd.org Subject: Balancing Outgoing traffic over 2 nics, and nic limitations. Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello my FreeBSD friends. I have two issues. The first is how to balance outbound traffic over 2 nics that are on the same subnet. Example configuration: fxp0: 12.2.2.5 netmask 255.255.255.0 fxp1: 12.2.2.6 netmask 255.255.255.255 router at: 12.2.2.1 Currently I have the obvious static route to 12.2.2.1, which locks onto fxp0 so all outbound traffic flows out over that link. Inbound traffic balances per ip as I would expect. I hope to find a scalable solution as I hope to build a server that will utilize 3 nics. This configuration is neccessary because by my estimation I have run into a limit on the intel pro 100 netcards of 6,000 packets/second. This limit equates to about 30 to 32 megabit/second of web traffic in our situation. I am wondering if anyone else has noticed this limit? This limit was hit on 2 very different machines, one with significantly less power. Any feedback on either of these issues would be appreciated. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 1:10:22 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 7E6B614F06 for ; Sat, 16 Oct 1999 01:10:18 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 30552 invoked by uid 1001); 16 Oct 1999 08:10:17 +0000 (GMT) To: griffin@blackprojects.org Cc: freebsd-hackers@freebsd.org Subject: Re: Balancing Outgoing traffic over 2 nics, and nic limitations. From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 16 Oct 1999 02:51:37 -0500" References: <199910160251370480.0B9DA297@207.109.8.249> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 16 Oct 1999 10:10:17 +0200 Message-ID: <30550.940061417@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This configuration is neccessary because by my estimation I have run > into a limit on the intel pro 100 netcards of 6,000 packets/second. > This limit equates to about 30 to 32 megabit/second of web traffic in > our situation. I am wondering if anyone else has noticed this limit? The Pro 100B/Pro 100+ models, using the fxp driver, are fully capable of saturating a 100 Mbps Ethernet. With maximum sized packets, this gives you more than 8000 packets per second. I have measured this many times myself. Thus I think the limitation you're seeing is not in the Intel Ethernet cards. 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 Sat Oct 16 2:12:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a1-3a123.neo.rr.com [24.93.180.123]) by hub.freebsd.org (Postfix) with ESMTP id 18F6714D40 for ; Sat, 16 Oct 1999 02:12:18 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id FAA25456; Sat, 16 Oct 1999 05:12:11 -0400 Date: Sat, 16 Oct 1999 05:12:11 -0400 (EDT) From: Mike Nowlin To: Julian Elischer Cc: Jos Backus , freebsd-hackers@FreeBSD.ORG Subject: Re: SUIDDIR problem 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 > SUIDDIR will work for any user EXCEPT ROOT > I did this because I felt it was a security hole to allow users to create > files owned by root. > (from memory it will also refuse to do files that have the execute bit set > but I can't remember for sure) In a mildly drunken state, I respond..... :) Without looking, I'd imagine that if the chmod command of FTP will allow you to do a "chmod 4755 file-I-just-uploaded" -- if you have the ability to execute programs on the machine you uploaded to, this could be a major problem..... Hence, I'd agree with your decision. --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 2:29: 3 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 4575B14D40 for ; Sat, 16 Oct 1999 02:29:01 -0700 (PDT) (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 CAA25018; Sat, 16 Oct 1999 02:25:40 -0700 (PDT) Date: Sat, 16 Oct 1999 02:25:39 -0700 (PDT) From: Julian Elischer To: Mike Nowlin Cc: Jos Backus , freebsd-hackers@FreeBSD.ORG Subject: Re: SUIDDIR problem 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 Sat, 16 Oct 1999, Mike Nowlin wrote: > > > SUIDDIR will work for any user EXCEPT ROOT > > I did this because I felt it was a security hole to allow users to create > > files owned by root. > > (from memory it will also refuse to do files that have the execute bit set > > but I can't remember for sure) > > In a mildly drunken state, I respond..... :) > > Without looking, I'd imagine that if the chmod command of FTP will allow > you to do a "chmod 4755 file-I-just-uploaded" -- if you have the ability > to execute programs on the machine you uploaded to, this could be a major > problem..... Hence, I'd agree with your decision. Since the ftp daemon will create files without the x bits set, they will succeeed, and will immediatly be owned by the owner of the directory. The sender no-longer owns them and cannot set mode bits, whether or not the ftp daemon would allow it to. > > --mike > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 8:26:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id B403A14FCE for ; Sat, 16 Oct 1999 08:26:38 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id IAA26801; Sat, 16 Oct 1999 08:26:26 -0700 (PDT) Message-Id: <199910161526.IAA26801@lestat.nas.nasa.gov> To: Edward Elhauge Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD and HP Jornado Reply-To: Jason Thorpe From: Jason Thorpe Date: Sat, 16 Oct 1999 08:26:25 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 15 Oct 1999 17:29:07 -0700 Edward Elhauge wrote: > My other questions is if is a way of replacing the CE OS with something > easier to customize and that might run either Perl or Java? What sort of processor does the Jornado have? If it's a MIPS-based machine, getting it to run NetBSD/hpcmips might be a possibility. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 8:38:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (Postfix) with ESMTP id E449914CA3 for ; Sat, 16 Oct 1999 08:38:25 -0700 (PDT) (envelope-from puga@mauibuilt.com) Received: from mauibuilt.com (puga@puga.mauibuilt.com [205.166.10.2]) by mauibuilt.com (8.9.3/8.9.3) with ESMTP id FAA11349; Sat, 16 Oct 1999 05:40:45 -1000 (HST) (envelope-from puga@mauibuilt.com) Message-ID: <38089B83.EDB75A76@mauibuilt.com> Date: Sat, 16 Oct 1999 05:36:36 -1000 From: Richard Puga X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: ikuo@intec.co.jp, freebsd-hackers@freebsd.org Subject: ftpmirror proxy Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I realy like ftpmirror it is a great program. I was wondering if ftpmirror can use a squid proxy server which runs on port 3128? Is there a way to use ftp-gateway on a specific port? below is a sampe of the configurations I have tried. Thank you for your time Richard Puga puga@mauibuilt.com ftp-user = anonymous ftp-pass = puga@mauibuilt.com ftp-stats = yes temp-directory = /usr/tmp package = FreeBSD ftp-server = ftp.freebsd.org # ftp-gateway = ftp.squid.proxy.server 3128 ftp-gateway = ftp.squid.proxy.server :3128 remote-directory = /pub/FreeBSD local-directory = /usr/var/ftp/pub/FreeBSD transfer-file-regexp += !/\/core$/ transfer-file-regexp += !/\.core$/ transfer-file-regexp += !/\/\ko-/ transfer-file-regexp += !/\/\ja-/ transfer-file-regexp += !/\/\zh-/ transfer-directory-regexp += !/\/CERT\/$/ transfer-directory-regexp += !/\/releases\/alpha\/$/ transfer-directory-regexp += !/\/development\/$/ transfer-directory-regexp += !/\/doc\/mailing\-lists\/$/ transfer-directory-regexp += !/\/ports\/alpha\/$/ transfer-directory-regexp += !/\/ports\/i386\/packages\-3\.0\-aout\/$/ transfer-directory-regexp += !/\/branches\/\-current\/XF86333\/$/ transfer-directory-regexp += !/\/branches\/\-current\/packages\-aout\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 10: 7: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fdy2.demon.co.uk (fdy2.demon.co.uk [194.222.102.143]) by hub.freebsd.org (Postfix) with ESMTP id 6003B1505F for ; Sat, 16 Oct 1999 10:07:01 -0700 (PDT) (envelope-from rjs@fdy2.demon.co.uk) Received: (from rjs@localhost) by fdy2.demon.co.uk (8.8.8/8.8.8) id RAA00811; Sat, 16 Oct 1999 17:57:37 +0100 (BST) (envelope-from rjs) Date: Sat, 16 Oct 1999 17:57:37 +0100 (BST) Message-Id: <199910161657.RAA00811@fdy2.demon.co.uk> From: Robert Swindells To: thorpej@nas.nasa.gov Cc: elhauge@gene.com, freebsd-hackers@freebsd.org In-reply-to: <199910161526.IAA26801@lestat.nas.nasa.gov> (message from Jason Thorpe on Sat, 16 Oct 1999 08:26:25 -0700) Subject: Re: FreeBSD and HP Jornado Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason R. Thorpe wrote: > Edward Elhauge wrote: >> My other questions is if is a way of replacing the CE OS with something >> easier to customize and that might run either Perl or Java? >What sort of processor does the Jornado have? If it's a MIPS-based machine, >getting it to run NetBSD/hpcmips might be a possibility. The high end one (820 ?) has a 190MHz SA1100 StrongArm. I don't think that there is any support in NetBSD/arm32 for either the SA1100 or SA1110. Robert Swindells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 10:43:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles550.castles.com [208.214.165.114]) by hub.freebsd.org (Postfix) with ESMTP id A3B1014BEB for ; Sat, 16 Oct 1999 10:43:31 -0700 (PDT) (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 KAA06493; Sat, 16 Oct 1999 10:35:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910161735.KAA06493@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jimbo Bahooli" Cc: freebsd-hackers@freebsd.org Subject: Re: Balancing Outgoing traffic over 2 nics, and nic limitations. In-reply-to: Your message of "Sat, 16 Oct 1999 02:51:37 CDT." <199910160251370480.0B9DA297@207.109.8.249> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Oct 1999 10:35:34 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello my FreeBSD friends. > > I have two issues. > > The first is how to balance outbound traffic over 2 nics that are on > the same subnet. Example configuration: > > fxp0: 12.2.2.5 netmask 255.255.255.0 > fxp1: 12.2.2.6 netmask 255.255.255.255 > > router at: 12.2.2.1 You can't do this. If all of the outbound traffic is headed for the same router, put two cards in the router and use two separate nets. > Currently I have the obvious static route to 12.2.2.1, which locks onto > fxp0 so all outbound traffic flows out over that link. Inbound traffic > balances per ip as I would expect. I hope to find a scalable solution > as I hope to build a server that will utilize 3 nics. This is not a sensible course of action. > This configuration is neccessary because by my estimation I have run > into a limit on the intel pro 100 netcards of 6,000 packets/second. These cards do not exhibit such a limit. You may have run into some issues with FreeBSD's ability to handle very large numbers of small packets with your particular application mix. > This limit equates to about 30 to 32 megabit/second of web traffic in > our situation. I am wondering if anyone else has noticed this limit? Not in my recollection. The fxp driver in recent incarnations limits the number of interrupts it generates by restricting them to low-resource conditions rather than generating one per packet. And I've personally seen an SMP kernel run tolerably while taking > 100,000 interrupts per second. > This limit was hit on 2 very different machines, one with significantly > less power. Any feedback on either of these issues would be > appreciated. I'd start by eliminating the network adapter and driver; move to an up-to-date FreeBSD-stable and substitute a 3C905B or C and determine for yourselves whether this is really an issue with the card. General experience would suggest that you should be able to come close to saturating your network with even relatively small datagrams using either of these adapters. You also don't mention whether you're running on a switched network; at that sort of traffic level you will definitely want to be using a switch that supports full duplex operation. -- \\ 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 Oct 16 10:51: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt050n71.san.rr.com (dt050n71.san.rr.com [204.210.31.113]) by hub.freebsd.org (Postfix) with ESMTP id 7775614BEB for ; Sat, 16 Oct 1999 10:50:58 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt050n71.san.rr.com (8.9.3/8.8.8) with ESMTP id KAA66494; Sat, 16 Oct 1999 10:50:49 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <3808BAF9.9E8A2474@gorean.org> Date: Sat, 16 Oct 1999 10:50:49 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT-0927 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Aleksandr A.Babaylov" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: how mkdir without .. ? References: <199910151324.RAA22353@aaz.links.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Aleksandr A.Babaylov" wrote: > > I need in directories without link to parent in it > or with link to parent renamed to something exotic name. What are you trying to accomplish? If you are trying to create directories that users cannot "escape" out of, all you need to do is remove the world rx permissions on the parent directory, and make sure that they don't have access via the group permissions. You might also want to look at chroot. Good luck, 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 Sat Oct 16 11:17:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from web1606.mail.yahoo.com (web1606.mail.yahoo.com [128.11.23.206]) by hub.freebsd.org (Postfix) with SMTP id 222C01506E for ; Sat, 16 Oct 1999 11:17:49 -0700 (PDT) (envelope-from ycardena@yahoo.com) Message-ID: <19991016182432.16140.rocketmail@web1606.mail.yahoo.com> Received: from [200.13.193.121] by web1606.mail.yahoo.com; Sat, 16 Oct 1999 11:24:32 PDT Date: Sat, 16 Oct 1999 11:24:32 -0700 (PDT) From: Yonny Cardenas Subject: I can't boot FreeBSD 3.2 from Installation CD (fwd To: hackers@FreeBSD.org Cc: giffunip@asme.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Sorry, I have sent this e-mail to questions from monday but no I haven't received any answer. Thanks for your help. -------- Original Message -------- Subject: I can't boot FreeBSD 3.2 from Installation CD (fwd) Date: Mon, 11 Oct 1999 16:25:07 -0500 (COT) From: Yonny Cardenas Baron To: freebsd-questions@FreeBSD.ORG I have a problem with the installation of FreeBSD Releases 3.1 and 3.2. My box can't boot from CD or installation floppies, the following message was showed: -------------------------------------------------------------- BTX loader BIOS drive A: is disk0 BIOS drive B: is disk1 Can't work out which disk we are booting from Guessed BIOS device 0x8b not found by probes defaulting to disk0: ----------------------------------------------------------------- Now, I is running well FreeBSD 2.2.5 this computer, I can boot from CD and floppies installation 2.2.5. It is a IBM PC Personal Computer 300GL with Pentium II, RAM 64M and HD 3Gb. Thanks for your help. YONNY CARDENAS B. Escuela Colombiana de Ingenieria e-mail: ycadena@escuelaing.edu.co ycardena@yahoo.com ===== __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 11:20:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alive.znep.com (alive.znep.com [207.167.15.58]) by hub.freebsd.org (Postfix) with ESMTP id 1BE7B15162 for ; Sat, 16 Oct 1999 11:20:12 -0700 (PDT) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.3/8.9.1) with ESMTP id MAA14034 for ; Sat, 16 Oct 1999 12:20:11 -0600 (MDT) (envelope-from marcs@znep.com) Date: Sat, 16 Oct 1999 12:20:11 -0600 (MDT) From: Marc Slemko To: hackers@freebsd.org Subject: MAXPATHLEN not enforced Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why does FreeBSD let you create paths longer than MAXPATHLEN? =20 I often have various trees that are as deep as possible for testing various programs for holes, and I finally figured out why locate wasn't updating it= s database properly; it was choking as soon as it saw a path length=20 >MAXPATHLEN long. The question, however, is why can it see a path length longer than MAXPATHLEN? I would also wonder if there aren't some security issues resulting from this. From what gdb shows, locate seems to trash its stack before spitting out the error about the path being too long... marcs@alive:/tmp$ mkdir erm... marcs@alive:/tmp$ cd erm... marcs@alive:/tmp/erm...$ while mkdir xxxxx; do cd xxxxx; done cd: could not get current directory: getcwd: cannot access parent directori= es: Result too large cd: could not get current directory: getcwd: cannot access parent directori= es: Result too large ^Cjob-working-directory: could not get current directory: getcwd: cannot ac= cess parent directories: Result too large cd_links: could not get current directory: getcwd: cannot access parent dir= ectories: Result too large ^C^C^C^C^Ccd: could not get current directory: getcwd: cannot access parent= directories: Result too large ^C^C^C^C^Ccd: could not get current directory: getcwd: cannot access parent= directories: Result too large ^C^C^C^C^C^C^C^C^C^C^C^C^C ^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C marcs@alive:.$ cd / cd_links: could not get current directory: getcwd: cannot access parent dir= ectories: Result too large marcs@alive:/$ find /tmp/erm.../ | perl -ne 'if (length($_) > 1024) { print= length($_), ": $_\n" }' (...a few other results...) 1038: /tmp/erm.../xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxx= xx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/= xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxx= xx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/= xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxx= xx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/= xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxx= xx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/= xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxx= xx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/= xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxx= xx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/= xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxx= xx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx/xxxxx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 11:25:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from topsecret.blackprojects.org (host249.dinnaken.com [207.109.8.249]) by hub.freebsd.org (Postfix) with ESMTP id 8B7CD15162 for ; Sat, 16 Oct 1999 11:25:29 -0700 (PDT) (envelope-from griffin@blackprojects.org) Received: from vortex (gary [207.109.8.98]) by topsecret.blackprojects.org (8.9.3/8.9.3) with ESMTP id NAA06364; Sat, 16 Oct 1999 13:25:22 -0500 (CDT) (envelope-from griffin@blackprojects.org) Message-ID: <199910161325230440.0DE208AE@207.109.8.249> In-Reply-To: <199910161735.KAA06493@dingo.cdrom.com> References: <199910161735.KAA06493@dingo.cdrom.com> X-Mailer: Calypso Version 3.00.00.14 (2) Date: Sat, 16 Oct 1999 13:25:23 -0500 From: "Jimbo Bahooli" To: "Mike Smith" Cc: freebsd-hackers@freebsd.org Subject: Re: Balancing Outgoing traffic over 2 nics, and nic limitations. Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10/16/99 at 10:35 AM Mike Smith wrote: >> Hello my FreeBSD friends. >> >> I have two issues. >> >> The first is how to balance outbound traffic over 2 nics that are on >> the same subnet. Example configuration: >> >> fxp0: 12.2.2.5 netmask 255.255.255.0 >> fxp1: 12.2.2.6 netmask 255.255.255.255 >> >> router at: 12.2.2.1 > > >You can't do this. If all of the outbound traffic is headed for the >same router, put two cards in the router and use two separate nets. > >> Currently I have the obvious static route to 12.2.2.1, which locks onto >> fxp0 so all outbound traffic flows out over that link. Inbound traffic >> balances per ip as I would expect. I hope to find a scalable solution >> as I hope to build a server that will utilize 3 nics. > >This is not a sensible course of action. > Sounds fair. :) >> This configuration is neccessary because by my estimation I have run >> into a limit on the intel pro 100 netcards of 6,000 packets/second. > >These cards do not exhibit such a limit. You may have run into some >issues with FreeBSD's ability to handle very large numbers of small >packets with your particular application mix. > >> This limit equates to about 30 to 32 megabit/second of web traffic in >> our situation. I am wondering if anyone else has noticed this limit? > >Not in my recollection. The fxp driver in recent incarnations limits >the number of interrupts it generates by restricting them to >low-resource conditions rather than generating one per packet. And >I've personally seen an SMP kernel run tolerably while taking > 100,000 >interrupts per second. > >> This limit was hit on 2 very different machines, one with significantly >> less power. Any feedback on either of these issues would be >> appreciated. > >I'd start by eliminating the network adapter and driver; move to an >up-to-date FreeBSD-stable and substitute a 3C905B or C and determine >for yourselves whether this is really an issue with the card. > >General experience would suggest that you should be able to come close >to saturating your network with even relatively small datagrams using >either of these adapters. > >You also don't mention whether you're running on a switched network; at >that sort of traffic level you will definitely want to be using a >switch that supports full duplex operation. Of course its a switched network with full duplex operation. But now that the general answer is that it is not a limitation of the nic card I am going to look elsewhere. I was not to sure if it was actually a limit myself, its just that I observed it on two different machines. They however were not huge powerhouses, one was a p2-450, and one was a dual p2 333. Both running real new versions of 3.3-stable. Thanks for the replies at any rate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 11:31:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id 8525C15162 for ; Sat, 16 Oct 1999 11:31:14 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id LAA28972; Sat, 16 Oct 1999 11:30:47 -0700 (PDT) Message-Id: <199910161830.LAA28972@lestat.nas.nasa.gov> To: Robert Swindells Cc: elhauge@gene.com, freebsd-hackers@freebsd.org Subject: Re: FreeBSD and HP Jornado Reply-To: Jason Thorpe From: Jason Thorpe Date: Sat, 16 Oct 1999 11:30:47 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 16 Oct 1999 17:57:37 +0100 (BST) Robert Swindells wrote: > The high end one (820 ?) has a 190MHz SA1100 StrongArm. > > I don't think that there is any support in NetBSD/arm32 for either the > SA1100 or SA1110. No, but it probably wouldn't be that hard to make it go :-) -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 11:34:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles549.castles.com [208.214.165.113]) by hub.freebsd.org (Postfix) with ESMTP id 6DF7615227 for ; Sat, 16 Oct 1999 11:34:28 -0700 (PDT) (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 LAA06742; Sat, 16 Oct 1999 11:26:24 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910161826.LAA06742@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jimbo Bahooli" Cc: "Mike Smith" , freebsd-hackers@freebsd.org Subject: Re: Balancing Outgoing traffic over 2 nics, and nic limitations. In-reply-to: Your message of "Sat, 16 Oct 1999 13:25:23 CDT." <199910161325230440.0DE208AE@207.109.8.249> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Oct 1999 11:26:23 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Of course its a switched network with full duplex operation. But now > that the general answer is that it is not a limitation of the nic card > I am going to look elsewhere. I was not to sure if it was actually a > limit myself, its just that I observed it on two different machines. You should be looking at some basic system statistics to see where your limiting factor actually is; try watching 'systat -vmstat 1' while you're hitting your limit. > They however were not huge powerhouses, one was a p2-450, and one was a > dual p2 333. Both running real new versions of 3.3-stable. Note also that Apache isn't the fastest of animals; you might want to use a lighter-weight server like thttpd if all you're doing is serving static content. -- \\ 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 Oct 16 11:34:35 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 E135E1522C for ; Sat, 16 Oct 1999 11:34:29 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 40064 invoked by uid 1001); 16 Oct 1999 18:34:28 +0000 (GMT) To: griffin@blackprojects.org Cc: mike@smith.net.au, freebsd-hackers@freebsd.org Subject: Re: Balancing Outgoing traffic over 2 nics, and nic limitations. From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 16 Oct 1999 13:25:23 -0500" References: <199910161325230440.0DE208AE@207.109.8.249> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 16 Oct 1999 20:34:28 +0200 Message-ID: <40062.940098868@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Of course its a switched network with full duplex operation. But now > that the general answer is that it is not a limitation of the nic card > I am going to look elsewhere. I was not to sure if it was actually a > limit myself, its just that I observed it on two different machines. > They however were not huge powerhouses, one was a p2-450, and one was a > dual p2 333. Both running real new versions of 3.3-stable. FWIW, FreeBSD 3.x with an Intel Pro 100B/100+ card can saturate a 100 Mbps Ethernet with something like a P-166. This is with maximum sized frames, running ttcp or Netperf. You *don't* need a huge powerhouse with FreeBSD :-) 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 Sat Oct 16 11:39: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles549.castles.com [208.214.165.113]) by hub.freebsd.org (Postfix) with ESMTP id 724B815227 for ; Sat, 16 Oct 1999 11:38:59 -0700 (PDT) (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 LAA06781; Sat, 16 Oct 1999 11:30:59 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910161830.LAA06781@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: sthaug@nethelp.no Cc: griffin@blackprojects.org, freebsd-hackers@freebsd.org Subject: Re: Balancing Outgoing traffic over 2 nics, and nic limitations. In-reply-to: Your message of "Sat, 16 Oct 1999 20:34:28 +0200." <40062.940098868@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Oct 1999 11:30:58 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Of course its a switched network with full duplex operation. But now > > that the general answer is that it is not a limitation of the nic card > > I am going to look elsewhere. I was not to sure if it was actually a > > limit myself, its just that I observed it on two different machines. > > They however were not huge powerhouses, one was a p2-450, and one was a > > dual p2 333. Both running real new versions of 3.3-stable. > > FWIW, FreeBSD 3.x with an Intel Pro 100B/100+ card can saturate a 100 Mbps > Ethernet with something like a P-166. This is with maximum sized frames, > running ttcp or Netperf. You *don't* need a huge powerhouse with FreeBSD > :-) The issue here isn't big frames though, it's little frames. You don't appear to have noticed that, and it's potentially very relevant. -- \\ 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 Oct 16 11:40:57 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 E6BD915227 for ; Sat, 16 Oct 1999 11:40:55 -0700 (PDT) (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 OAA08334 for ; Sat, 16 Oct 1999 14:40:55 -0400 (EDT) Date: Sat, 16 Oct 1999 13:38:14 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@FreeBSD.ORG Subject: Re: Status of UMAPFS 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 Fri, 15 Oct 1999, Zhihui Zhang wrote: > > Is the UMAPFS working? I add "options UMAPFS" to the configuration file > of FreeBSD 3.3-Release and rebuilt the kernel. I got the following > errors: > > loading kernel > umap_vnops.o: In function `umap_lock': > umap_vnops.o(.text+0x568): undefined reference to `null_bypass' > umap_vnops.o: In function `umap_unlock': > umap_vnops.o(.text+0x58e): undefined reference to `null_bypass' > *** Error code 1 > > Stop. > I find out that you must also include NULLFS in the kernel to compile. I have tested NULLFS and UMAPFS with some trivial commands. Both works. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 12:12:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from topsecret.blackprojects.org (host249.dinnaken.com [207.109.8.249]) by hub.freebsd.org (Postfix) with ESMTP id D4B0014C3C for ; Sat, 16 Oct 1999 12:11:54 -0700 (PDT) (envelope-from griffin@blackprojects.org) Received: from vortex (gary [207.109.8.98]) by topsecret.blackprojects.org (8.9.3/8.9.3) with ESMTP id OAA06473; Sat, 16 Oct 1999 14:11:48 -0500 (CDT) (envelope-from griffin@blackprojects.org) Message-ID: <199910161411480990.0E0C8D04@207.109.8.249> In-Reply-To: <199910161826.LAA06742@dingo.cdrom.com> References: <199910161826.LAA06742@dingo.cdrom.com> X-Mailer: Calypso Version 3.00.00.14 (2) Date: Sat, 16 Oct 1999 14:11:48 -0500 From: "Jimbo Bahooli" To: "Mike Smith" Cc: freebsd-hackers@freebsd.org Subject: Re: Balancing Outgoing traffic over 2 nics, and nic limitations. Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10/16/99 at 11:26 AM Mike Smith wrote: >> >> Of course its a switched network with full duplex operation. But now >> that the general answer is that it is not a limitation of the nic card >> I am going to look elsewhere. I was not to sure if it was actually a >> limit myself, its just that I observed it on two different machines. > >You should be looking at some basic system statistics to see where your >limiting factor actually is; try watching 'systat -vmstat 1' while >you're hitting your limit. > >> They however were not huge powerhouses, one was a p2-450, and one was a >> dual p2 333. Both running real new versions of 3.3-stable. > >Note also that Apache isn't the fastest of animals; you might want to >use a lighter-weight server like thttpd if all you're doing is serving >static content. > We are actually using Zeus web server. Which is based on the select()/poll() model much like thttpd. Its extremely fast. It is also fully featured like apache, but 5 times faster. And boy, you are right about apache not being the fastest of animals. :) And to everyone following, this is web traffic, not huge tcp benchmark packets. Its not so bad now, we can push 35 megabit from one machine, where before apache would do about 10, but we could get it to 25 by putting a huge load on the machine. But I will look at systat now. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 21: 8:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt050n71.san.rr.com (dt050n71.san.rr.com [204.210.31.113]) by hub.freebsd.org (Postfix) with ESMTP id BC34214F69 for ; Sat, 16 Oct 1999 21:08:50 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt050n71.san.rr.com (8.9.3/8.8.8) with ESMTP id VAA00676; Sat, 16 Oct 1999 21:08:40 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <38094BC8.B4040C5C@gorean.org> Date: Sat, 16 Oct 1999 21:08:40 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: dg@root.com, FreeBSD-hackers@FreeBSD.ORG Subject: Re: SMP + fxp0 wierdness References: <199910120408.VAA04018@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > Well that's not good, since I have almost convinced my boss to replace > > the crappy IDE drives on our shiny new Intel N440BX mb's with scsi > > drives since the controller is built in. :-/ Does this look like a > > soluble problem, or is it just going to be a case of "don't do that?" > > Anything I can do to help mail me and let me know. > > You could try turning on DMA and discovering that these drives aren't > _that_ shitty. 8) Heh... well I've already enabled flags 0xb0ff, which has improved things somewhat, but our hardware vendor slipped in some IBM DeskStar drives on us, and they've been no end of trouble. He _may_ live to regret his "mistake." The good news is that the first machine rebuilt with the SCSI drives and using ncr0 + fxp0 is not showing any signs of trouble. Crossing fingers, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 21:30:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 598381505F for ; Sat, 16 Oct 1999 21:30:36 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11chxm-0001mU-00; Sat, 16 Oct 1999 22:30:30 -0600 Message-ID: <3809416D.2C6C741D@softweyr.com> Date: Sat, 16 Oct 1999 21:24:29 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Jimbo Bahooli Cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: Balancing Outgoing traffic over 2 nics, and niclimitations. References: <199910161735.KAA06493@dingo.cdrom.com> <199910161325230440.0DE208AE@207.109.8.249> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jimbo Bahooli wrote: > > Of course its a switched network with full duplex operation. But now > that the general answer is that it is not a limitation of the nic card > I am going to look elsewhere. I was not to sure if it was actually a > limit myself, its just that I observed it on two different machines. > They however were not huge powerhouses, one was a p2-450, and one was a > dual p2 333. Both running real new versions of 3.3-stable. No possibility of moving to a Gigabit adapter and sticking a Gigabit blade in your switch? Another possibility, depending on your switch vendor, may be to query them about some sort of channel aggregation. They might even be willing to open their source code -- who knows? Stranger things have happened. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 21:30:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id BEBD9150D4 for ; Sat, 16 Oct 1999 21:30:41 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11chxv-0001nZ-00; Sat, 16 Oct 1999 22:30:40 -0600 Message-ID: <38094B9B.33C55A3F@softweyr.com> Date: Sat, 16 Oct 1999 22:07:55 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Jason Thorpe Cc: Robert Swindells , elhauge@gene.com, freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD and HP Jornado References: <199910161830.LAA28972@lestat.nas.nasa.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Thorpe wrote: > > On Sat, 16 Oct 1999 17:57:37 +0100 (BST) > Robert Swindells wrote: > > > The high end one (820 ?) has a 190MHz SA1100 StrongArm. > > > > I don't think that there is any support in NetBSD/arm32 for either the > > SA1100 or SA1110. > > No, but it probably wouldn't be that hard to make it go :-) The Digital DNARD ran NetBSD/arm, but it was an SA-110. The 1100 is the same processor with more "system support" built in; it shouldn't be much of a leap. Jornada/BSD would be killer. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 21:32:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 4194814D94 for ; Sat, 16 Oct 1999 21:32:48 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11chzu-00025S-00; Sat, 16 Oct 1999 22:32:42 -0600 Message-ID: <38095168.FE3F1535@softweyr.com> Date: Sat, 16 Oct 1999 22:32:40 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Kevin Day Cc: Mark Newton , Dodge Ram , freebsd-hackers@FreeBSD.ORG Subject: Re: Handling segV's References: <199910160457.XAA21178@celery.dragondata.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kevin Day wrote: > > I mmap() files in, then copy them to a device. This works great except when > someone tries to change that file during the copy. If the size of the file > shrinks, I'll SIGBUS or SIGSEGV when i try to touch past the new file size. > So, i setup a signal handler and longjmp into some recovery code. > > Perhaps there's a better way, but I don't consider this a bug really, and > i'll get a SEGV. :) MAP_PRIVATE? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 22:23:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 32B1114FBA for ; Sat, 16 Oct 1999 22:23:18 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from root@localhost) by celery.dragondata.com (8.9.3/8.9.3) id AAA26797; Sun, 17 Oct 1999 00:24:15 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199910170524.AAA26797@celery.dragondata.com> Subject: Re: Handling segV's To: wes@softweyr.com (Wes Peters) Date: Sun, 17 Oct 1999 00:24:15 -0500 (CDT) Cc: toasty@dragondata.com (Kevin Day), newton@internode.com.au (Mark Newton), gupz@hotmail.com (Dodge Ram), freebsd-hackers@FreeBSD.ORG In-Reply-To: <38095168.FE3F1535@softweyr.com> from "Wes Peters" at Oct 16, 1999 10:32:40 PM X-Mailer: ELM [version 2.5 PL1] 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 > > Kevin Day wrote: > > > > I mmap() files in, then copy them to a device. This works great except when > > someone tries to change that file during the copy. If the size of the file > > shrinks, I'll SIGBUS or SIGSEGV when i try to touch past the new file size. > > So, i setup a signal handler and longjmp into some recovery code. > > > > Perhaps there's a better way, but I don't consider this a bug really, and > > i'll get a SEGV. :) > > MAP_PRIVATE? > This has the undesired effect of me not noticing that the file changed then. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 23:19:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.dti.ne.jp (smtp.dti.ne.jp [210.170.128.120]) by hub.freebsd.org (Postfix) with ESMTP id D08B114EE5 for ; Sat, 16 Oct 1999 23:19:12 -0700 (PDT) (envelope-from shigio@tamacom.com) Received: from choota.signet.or.jp (PPP128.tama-ap5.dti.ne.jp [210.170.192.164]) by smtp.dti.ne.jp (8.9.0/3.7W) with ESMTP id PAA29721; Sun, 17 Oct 1999 15:19:09 +0900 (JST) Received: from choota.signet.or.jp (localhost [127.0.0.1]) by choota.signet.or.jp (8.8.8/) with ESMTP id PAA16821; Sun, 17 Oct 1999 15:15:57 +0900 (JST) Message-Id: <199910170615.PAA16821@tamacom.com> To: hackers@FreeBSD.ORG Cc: shigio@tamacom.com Subject: Re: Search a symbol in the source tree Date: Sun, 17 Oct 1999 15:15:57 +0900 From: Shigio Yamaguchi Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > > Looking for where "utmp.h" is used: > > > > global -x -s utmp.h > > > > This takes more than 2212 seconds (over 36 minutes!), and outputs > > It seems that something wrong (bug?) occurred. > Would you please tell me the version of FreeBSD and GLOBAL? A structural problem was found in GLOBAL. I will optimize it. Thanks Darryl for his report. [work around] When you use regular expressions, please put prefix '^' to it like: global -x -s '^utmp.h' '.' is a regular expression which means any character. So, 'utmp.h' will match with 'aaautmpbhccc'. The '^' enables global to use index effectively. -- Shigio Yamaguchi - Tama Communications Corporation Mail: shigio@tamacom.com, WWW: http://www.tamacom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 23:31:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id C9F5914C8E for ; Sat, 16 Oct 1999 23:31:24 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 2.12 #2) id 11cjql-000538-00; Sun, 17 Oct 1999 00:31:23 -0600 Message-ID: <38096D39.794E9EC0@softweyr.com> Date: Sun, 17 Oct 1999 00:31:21 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Kevin Day Cc: Mark Newton , Dodge Ram , freebsd-hackers@FreeBSD.ORG Subject: Re: Handling segV's References: <199910170524.AAA26797@celery.dragondata.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kevin Day wrote: > > > > > Kevin Day wrote: > > > > > > I mmap() files in, then copy them to a device. This works great except when > > > someone tries to change that file during the copy. If the size of the file > > > shrinks, I'll SIGBUS or SIGSEGV when i try to touch past the new file size. > > > So, i setup a signal handler and longjmp into some recovery code. > > > > > > Perhaps there's a better way, but I don't consider this a bug really, and > > > i'll get a SEGV. :) > > > > MAP_PRIVATE? > > > > This has the undesired effect of me not noticing that the file changed then. stat(2) it after the copy? OK, I'm reaching. Handling SEGV seems like a rather iffy solution at best. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 16 23:34:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 06B0514F21 for ; Sat, 16 Oct 1999 23:34:14 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from root@localhost) by celery.dragondata.com (8.9.3/8.9.3) id BAA10112; Sun, 17 Oct 1999 01:35:42 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199910170635.BAA10112@celery.dragondata.com> Subject: Re: Handling segV's To: wes@softweyr.com (Wes Peters) Date: Sun, 17 Oct 1999 01:35:42 -0500 (CDT) Cc: toasty@dragondata.com (Kevin Day), newton@internode.com.au (Mark Newton), gupz@hotmail.com (Dodge Ram), freebsd-hackers@FreeBSD.ORG In-Reply-To: <38096D39.794E9EC0@softweyr.com> from "Wes Peters" at Oct 17, 1999 12:31:21 AM X-Mailer: ELM [version 2.5 PL1] 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 mmap() files in, then copy them to a device. This works great except when > > > > someone tries to change that file during the copy. If the size of the file > > > > shrinks, I'll SIGBUS or SIGSEGV when i try to touch past the new file size. > > > > So, i setup a signal handler and longjmp into some recovery code. > > > > > > > > Perhaps there's a better way, but I don't consider this a bug really, and > > > > i'll get a SEGV. :) > > > > > > MAP_PRIVATE? > > > > > > > This has the undesired effect of me not noticing that the file changed then. > > stat(2) it after the copy? OK, I'm reaching. Handling SEGV seems like a > rather iffy solution at best. In my case, it's a very very very rare thing that the file's been changed out from under me, and I'm doing several thousand copies per second, so doing a stat() on each copy makes things very slow. I know it's a crappy solution, but it's the only one that works. :) Also, consider that *during* the copy, the file could be changed. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message