From owner-freebsd-hackers Sun Sep 16 1:42:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id 57CC737B401; Sun, 16 Sep 2001 01:42:32 -0700 (PDT) Received: from chojin (Cho@chojin.lan.tarakan-network.com [192.168.69.2] (may be forged)) by tarakan-network.com (8.11.6/8.11.3) with SMTP id f8G8gTe00695; Sun, 16 Sep 2001 10:42:30 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <000b01c13e8b$84826980$0245a8c0@chojin> From: "Chojin" To: , Subject: Kernel Panic after upgrade Date: Sun, 16 Sep 2001 10:42:27 +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 6.00.2526.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2526.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, yesterday I cvsup my system with RELENG_4 branch. I recompiled my system, kernel, no error. I reboot with new kernel and just after it booted it says: panic: pmap_bootstrap: no local apic! mp_lock = 00000009; cpuid = 0; lapic.id =00000000 Uptime: 0s What I need to do ? Chojin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 1:44:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id AAA0637B407; Sun, 16 Sep 2001 01:44:32 -0700 (PDT) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id KAA09714; Sun, 16 Sep 2001 10:43:50 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.3/8.8.8) with ESMTP id f8G8hRA12955; Sun, 16 Sep 2001 10:43:27 +0200 (CEST) (envelope-from root@nihil) Date: Sun, 16 Sep 2001 10:43:26 +0200 (CEST) From: Michael Reifenberger To: Warner Losh Cc: "Daniel C. Sobral" , , Subject: Re: Multiple kernels selector... In-Reply-To: <200109160636.f8G6akW20252@harmony.village.org> Message-ID: <20010916103459.P12856-100000@nihil> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 16 Sep 2001, Warner Losh wrote: > In message <39B51E16.E8AD4BC8@newsguy.com> "Daniel C. Sobral" writes: > : ." Loading /boot/current.conf. Please wait..." cr > : s" /boot/current.conf" read-conf > > What's the difference beteen ." and s"? A . dot command does print the TOS (Top of Stack) usually. ."" does print a constant string. So ."FOO" does print FOO. s"" does put a constant string on top of the stack. Which seemd to get used by read-conf later on. I hope my memory didn't fool me here. Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 1:48:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id D0DD937B408; Sun, 16 Sep 2001 01:48:50 -0700 (PDT) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id KAA09730; Sun, 16 Sep 2001 10:48:13 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.3/8.8.8) with ESMTP id f8G8lqJ12974; Sun, 16 Sep 2001 10:47:52 +0200 (CEST) (envelope-from root@nihil) Date: Sun, 16 Sep 2001 10:47:52 +0200 (CEST) From: Michael Reifenberger To: Warner Losh Cc: "Daniel C. Sobral" , , Subject: Re: Multiple kernels selector... In-Reply-To: <200109160636.f8G6akW20252@harmony.village.org> Message-ID: <20010916104444.Y12856-100000@nihil> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 16 Sep 2001, Warner Losh wrote: ... > What's the difference beteen ." and s"? > BTW: Following the Tutorials link on http://ficl.sourceforge.net/ficl.html there is at least on good-looking Forth primer. Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 10: 6:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from newsguy.com (smtp.newsguy.com [209.155.56.71]) by hub.freebsd.org (Postfix) with ESMTP id 6A11737B406; Sun, 16 Sep 2001 10:06:17 -0700 (PDT) Received: from newsguy.com (ppp232-bsace7002.telebrasilia.net.br [200.181.81.232]) by newsguy.com (8.9.1a/8.9.1) with ESMTP id KAA91612; Sun, 16 Sep 2001 10:06:07 -0700 (PDT) Message-ID: <3BA4DCF8.26277131@newsguy.com> Date: Sun, 16 Sep 2001 14:10:16 -0300 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en,pt-BR,pt,en-GB,en-US,ja MIME-Version: 1.0 To: Warner Losh Cc: bp@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Multiple kernels selector... References: <39B51E16.E8AD4BC8@newsguy.com> <200109160636.f8G6akW20252@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Warner Losh wrote: > > [[ Please excuse me for replying to a one year old message, but I have > a question or two ]] > > In message <39B51E16.E8AD4BC8@newsguy.com> "Daniel C. Sobral" writes: > : ." Loading /boot/current.conf. Please wait..." cr > : s" /boot/current.conf" read-conf > > What's the difference beteen ." and s"? > > : s" /boot/stable.conf" read-conf > > What should go in /boot/stable.conf vs /boot/current.conf? > > also, is there a good way of clearing out the environment and starting > over? If I'd like to load /boot/loader.conf from inside of > stable.conf or current.conf after setting currdev? > > What I'm trying to do: > > I have a disk (ad0) in my laptop. It has two slices (one BSD one > DOS). The BSD slice has partitions a, b, e, f, and g. I'd like to > put current on partition g and stable on a. I'd like a "stable" > command that sets up the environment to boot stable and a "current" > command that sets it up to do current. Can I do that or am I SOL? Do you know the Japanese ISO image with three versions selector: 3.x, 4.x and current? That might help some, as might the stuff in /usr/share/examples/bootforth. Now, to the questions: ." xxxx" prints xxxx s" xxxx" places a string on the stack. It must be used only inside definitions, because, otherwise, the space where the string is placed is reused. No, there is no way of clearing out the environment. As a matter of fact, a few environment variables are actually set by loader itself, and at least these should be preserved. Since environment variables are not FICL-bound, such a command might as well be done entirely in C and provided as a builtin. The module stuff, though, must be taken care of in Forth. If I ever find time, this stuff will be dealt with using environment variables too, but... My own boot environment, which is available with slight variations on /usr/share/examples/bootforth, presents me with a menu which present me the option of loading, in addition to the other conf files, stable.conf, current.conf or nothing else. I see no reason why you couldn't set currdev before doing it. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net wow regex humor... I'm a geek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 11: 5: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id 7A1F137B403 for ; Sun, 16 Sep 2001 11:04:57 -0700 (PDT) Received: (qmail 77064 invoked by uid 1000); 16 Sep 2001 18:05:18 -0000 Date: Sun, 16 Sep 2001 20:05:18 +0200 From: "Karsten W. Rohrbach" To: Chojin Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel Panic after upgrade Message-ID: <20010916200518.F76493@mail.webmonster.de> Mail-Followup-To: "Karsten W. Rohrbach" , Chojin , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG References: <000b01c13e8b$84826980$0245a8c0@chojin> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ChQOR20MqfxkMJg9" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <000b01c13e8b$84826980$0245a8c0@chojin>; from freebsd@tarakan-network.com on Sun, Sep 16, 2001 at 10:42:27AM +0200 X-Arbitrary-Number-Of-The-Day: 42 X-URL: http://www.webmonster.de/ X-Disclaimer: My opinions do not necessarily represent those of my employer X-Work-URL: http://www.ngenn.net/ X-Work-Address: nGENn GmbH, Schloss Kransberg, D-61250 Usingen-Kransberg, Germany X-Work-Phone: +49-6081-682-304 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --ChQOR20MqfxkMJg9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Chojin(freebsd@tarakan-network.com)@2001.09.16 10:42:27 +0000: > Hello, >=20 > yesterday I cvsup my system with RELENG_4 branch. > I recompiled my system, kernel, no error. >=20 > I reboot with new kernel and just after it booted it says: > panic: pmap_bootstrap: no local apic! > mp_lock =3D 00000009; cpuid =3D 0; lapic.id =3D00000000 > Uptime: 0s >=20 > What I need to do ? compile without options SMP and options APIC_IO if it is a single processor system, i think. /k --=20 > A Christian is a man who feels repentance on Sunday for what he did on > Saturday and is going to do on Monday. --Thomas Ybarra KR433/KR11-RIPE -- WebMonster Community Founder -- nGENn GmbH Senior Techie http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.ngenn.n= et/ karsten&rohrbach.de -- alpha&ngenn.net -- alpha&scene.org -- catch@spam.de GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 B= F46 Please do not remove my address from To: and Cc: fields in mailing lists. 1= 0x --ChQOR20MqfxkMJg9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7pOndM0BPTilkv0YRAv4nAKCpXKeFONUNOt0CNQRvxcun8qZeRACePq5e LHRNbApYSUrlEgfKfn2lT/M= =JxWr -----END PGP SIGNATURE----- --ChQOR20MqfxkMJg9-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 13: 0:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ewey.excite.com (ewey-rwcmta.excite.com [198.3.99.191]) by hub.freebsd.org (Postfix) with ESMTP id A995D37B406; Sun, 16 Sep 2001 13:00:47 -0700 (PDT) Received: from doby.excite.com ([199.172.152.182]) by ewey.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20010916200047.LXLM7149.ewey.excite.com@doby.excite.com>; Sun, 16 Sep 2001 13:00:47 -0700 Message-ID: <24460926.1000670447361.JavaMail.imail@doby.excite.com> Date: Sun, 16 Sep 2001 13:00:41 -0700 (PDT) From: john_wilson100@excite.com To: Greg Lehey Subject: Re: VINUM PANIC ON -STABLE Cc: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Excite Inbox X-Sender-Ip: 62.90.91.23 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 16 Sep 2001 11:42:38 +0930, Greg Lehey wrote: > > 6) Supply an extract of the file /var/log/messages. > > > > Sep 12 14:06:10 depot login: ROOT LOGIN (root) ON ttyv0 > > Sep 12 14:07:29 depot login: ROOT LOGIN (root) ON ttyv1 > > Sep 13 01:58:14 depot /kernel: vinum: loaded > > Sep 13 01:58:15 depot /kernel: vinum: drive data1 is up > > Sep 13 01:58:15 depot /kernel: vinum: drive home1 is up > > Sep 13 01:58:15 depot /kernel: vinum: drive home2 is up > > Sep 13 01:58:15 depot /kernel: vinum: removing 499 blocks of partial stripe at the end of data.p0 > > Sep 13 01:58:15 depot /kernel: vinum: data.p0 must have equal sized subdisks > > Sep 13 01:58:15 depot /kernel: Correcting length of data.p0: was 20970756, is 20970757 > > I suspect that this is the problem. I've seen isolated cases where > the stripe size didn't get fixed correctly, leaving holes in the > volume. Could you send me the output of 'vinum l -v', please? And > please don't wrap log output, it makes it a pain to read. Hmm, I don't think I wrapped anything, if you go to http://docs.freebsd.org/mail/current/ (or wherever the last week's messages are), you'll see that the log output is not wrapped. It must be your own mailer that wraps it on receipt. Here's the output of "vinum l -v": 4 drives: Drive data1: Device /dev/ad4s1g Created on depot at Thu Sep 13 01:58:14 2001 Config last updated Sun Sep 16 03:28:31 2001 Size: 10737418240 bytes (10240 MB) Used: 10737162752 bytes (10239 MB) Available: 255488 bytes (0 MB) State: up Last error: none Active requests: 0 Maximum active: 0 Drive home1: Device /dev/ad4s1h Created on depot at Thu Sep 13 01:58:14 2001 Config last updated Sun Sep 16 03:28:31 2001 Size: 40822630912 bytes (38931 MB) Used: 40822528000 bytes (38931 MB) Available: 102912 bytes (0 MB) State: up Last error: none Active requests: 0 Maximum active: 0 Drive data2: Device /dev/ad6s1e Created on depot at Thu Sep 13 02:02:33 2001 Config last updated Sun Sep 16 03:28:31 2001 Size: 10737418240 bytes (10240 MB) Used: 10737162752 bytes (10239 MB) Available: 255488 bytes (0 MB) State: up Last error: none Active requests: 0 Maximum active: 0 Drive home2: Device /dev/ad6s1f Created on depot at Thu Sep 13 02:02:33 2001 Config last updated Sun Sep 16 03:28:31 2001 Size: 39566415872 bytes (37733 MB) Used: 39566312960 bytes (37733 MB) Available: 102912 bytes (0 MB) State: up Last error: none Active requests: 0 Maximum active: 0 2 volumes: Volume data: Size: 21474054144 bytes (20479 MB) State: up Flags: 1 plexes Read policy: round robin Volume home: Size: 80388569600 bytes (76664 MB) State: up Flags: 1 plexes Read policy: round robin 2 plexes: Plex data.p0: Size: 21474054144 bytes (20479 MB) Subdisks: 2 State: up Organization: striped Stripe size: 279 kB Part of volume data Plex home.p0: Size: 80388569600 bytes (76664 MB) Subdisks: 2 State: up Organization: striped Stripe size: 279 kB Part of volume home 4 subdisks: Subdisk data.p0.s0: Size: 10737027072 bytes (10239 MB) State: up Plex data.p0 at offset 0 (0 B) Drive data1 (/dev/ad4s1g) at offset 135680 (132 kB) Subdisk data.p0.s1: Size: 10737027072 bytes (10239 MB) State: up Plex data.p0 at offset 285696 (279 kB) Drive data2 (/dev/ad6s1e) at offset 135680 (132 kB) Subdisk home.p0.s0: Size: 40822392320 bytes (38931 MB) State: up Plex home.p0 at offset 0 (0 B) Drive home1 (/dev/ad4s1h) at offset 135680 (132 kB) Subdisk home.p0.s1: Size: 39566177280 bytes (37733 MB) State: up Plex home.p0 at offset 285696 (279 kB) Drive home2 (/dev/ad6s1f) at offset 135680 (132 kB) > Agreed. You're collateral damage. But I can't find that out > until I hear about it. I've opened the server for you. I'm not sure I like being called "collateral damage", but thanks anyway. John > > Greg > -- > When replying to this message, please take care not to mutilate the > original text. > For more information, see http://www.lemis.com/email.html > See complete headers for address and phone numbers _______________________________________________________ Send a cool gift with your E-Card http://www.bluemountain.com/giftcenter/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 13:46: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 1C16737B403; Sun, 16 Sep 2001 13:45:58 -0700 (PDT) Received: from mindspring.com (dialup-209.245.132.139.Dial1.SanJose1.Level3.net [209.245.132.139]) by swan.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id NAA25610; Sun, 16 Sep 2001 13:45:55 -0700 (PDT) Message-ID: <3BA50FB2.B0FF58FD@mindspring.com> Date: Sun, 16 Sep 2001 13:46:42 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: Bruce Evans , freebsd-hackers@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/lib/libatm atm_addr.c cache_key.c ioctl_subr.c ip_addr.c ip_checksum.c timer.c References: <200109151939.f8FJdKF28278@earth.backplane.com> <20010916062557.V30137-100000@delplex.bde.org> <20010915170831.A84246@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Sun, Sep 16, 2001 at 06:35:27AM +1000, Bruce Evans wrote: > > Especially the empty line after the copyright message: > > Agreed. > > > __FBSDID("$FreeBSD: src/lib/libatm/atm_addr.c,v 1.6 2001/09/15 19:36:55 dillon Exp $"); > > What about changing this to __FBSD(), which is what I was using in a > prototype to reduce the number of characters in the macro name (and thus > reduce the wrap around). That's a silly reason to change a macro. If you need two characters back, you should change Matt Dillon's login from "dillon" to "matt". (Now see how stupid the original suggestion sounded?). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 14:58:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from robin.mail.pas.earthlink.net (robin.mail.pas.earthlink.net [207.217.120.65]) by hub.freebsd.org (Postfix) with ESMTP id D65D837B408 for ; Sun, 16 Sep 2001 14:58:43 -0700 (PDT) Received: from mindspring.com (dialup-209.245.132.139.Dial1.SanJose1.Level3.net [209.245.132.139]) by robin.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f8GLwfD09022; Sun, 16 Sep 2001 14:58:41 -0700 (PDT) Message-ID: <3BA520BC.E26A64F0@mindspring.com> Date: Sun, 16 Sep 2001 14:59:24 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Stephen Montgomery-Smith Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Could not bind References: <3BA3F70D.27C2136@math.missouri.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Stephen Montgomery-Smith wrote: > > I have written a server program that listens on port 3000. The program > works very well except for one feature. I am asking if that is normal, > or whether I forgot something. > > If I run the program it does fine. If I then kill the program (after it > has accepted connections), and then run the program again, the bind > function fails to work, and I get a message like "Could not bind" (see > program below). If I wait a while, like a minute or two, then the > program will work again. Is this normal behavior, or did I miss > something? This is normal. When a server closes the connection, which will occur in the resource-track-cleanup case of you killing the server, the connections effectively undergo a "host close". If the clients are still around and responsive, these conections will go away quickly. If not, then these connections will hand around a long time. In addition, in the case of client initiated closes prior to your temination of the program, the sockets will be in TIME_WAIT state for 2MSL -- 60 seconds, by default. So in normal operation, you should expect that you will not be able to restart the server for at least 60 seconds, and perhaps more, unless you have unset the "keepalive" socket option on the sockets to prevent the FIN_WAIT_2 state. A common overreaction to improrper state tracking by the programmer, or improper "clean shutdown" of a server is to set SO_REUSEADDR on the listen socket of the server. THis lets you restart the server. But it also lets you start multiple instances of the server, so if you are doing things like cookie state tracking which are server instance specific (e.g. for an HTTP server), then you have shot yourself in the foot, unless this state is shared between all server instances, and your servers are anonymous work-to-do engines, rather than being specific-purpose (this is because you can not control the connections to make them go to one server vs. another, if both are listening on the same port). Ideally, you would correct the shutdown so that it was clean, and correct the socket options, if what you are intending is to abort the server without sending complete data to the client (e.g. unsetting SO_LINGER will cause the sending of an RST on close, avoiding the TIME_WAIT, but potentially leaving the client hanging until the longer -- 2 hour, by default -- clock on the client sends a keepalive, and the RST is resent; this is because RST's are not resent, as they do not get acknowledgement). As a workaround, you can set SO_REUSEADDR on the socket. Above, I labelled this as an overreaction... it is. For this to work, you will probably need to make sure your server creates a pid file in /var/run/.pid, and then, before you reopen the socket, verify via kill(2), using a argument of 0, that the process is in fact dead, before grabbing its port out from under it for half the inbound connections (see the "2 kill" man page for details on the 0 signal; a 0 return or a -1 return with errno == EPERM mean the process your are trying to replace is already running). > I got the programming style from Richard Steven's book on network > programming. The structure of the program is something like this: [ ... example elided ... ] That's all fine; the problem is just an incomplete understanding of the TCP protocol; hopefully the above will fill you in; in the man time, you may want to get the internals volumes from the Steven's books series, and read them, as well, since it's often useful to understand why you are seeing what you are seeing; the user space volumes are only half the story. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 17:40:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f243.law8.hotmail.com [216.33.241.243]) by hub.freebsd.org (Postfix) with ESMTP id BB84D37B410 for ; Sun, 16 Sep 2001 17:40:15 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 16 Sep 2001 17:40:15 -0700 Received: from 203.18.39.2 by lw8fd.law8.hotmail.msn.com with HTTP; Mon, 17 Sep 2001 00:40:15 GMT X-Originating-IP: [203.18.39.2] From: "Tim Allshorn" To: freebsd-hackers@freebsd.org Subject: Cron pickle Date: Mon, 17 Sep 2001 10:40:15 +1000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 17 Sep 2001 00:40:15.0706 (UTC) FILETIME=[517A7BA0:01C13F11] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello. I need to be able to run a particular program at the last minute of each month and yes I know it would be much easier to run it at the first minute of each month, but my hands are tied and my brain is too puny to work it out. I know the cron command has to be something like : 59 23 ? ? * , with maybe some condition on the end. If someone could help, it would be much appreciated. Thanks _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 17:47:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.switch.aust.com (ussmbox.ozemail.com.au [203.108.63.250]) by hub.freebsd.org (Postfix) with ESMTP id D060B37B40A; Sun, 16 Sep 2001 17:47:02 -0700 (PDT) Received: from smtp2.switch.aust.com (IDENT:root@ras.wa [10.0.1.140] (may be forged)) by server1.ussbris (8.9.3/8.9.3) with ESMTP id MAA01316; Fri, 14 Sep 2001 12:04:53 +1000 X-Authentication-Warning: server1.ussbris: Host IDENT:root@ras.wa [10.0.1.140] (may be forged) claimed to be smtp2.switch.aust.com Received: from freebsd06.udt (nelsont@freebsd06.udt [10.0.2.56]) by smtp2.switch.aust.com (8.11.3/8.11.3) with SMTP id f8E2LXK25099; Fri, 14 Sep 2001 10:21:33 +0800 Received: by freebsd06.udt (sSMTP sendmail emulation); Fri, 14 Sep 2001 10:12:29 +0800 Date: Fri, 14 Sep 2001 10:12:29 +0800 From: Trent Nelson To: john_wilson100@excite.com Cc: Greg Lehey , freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: Vinum Panic (was Re: HPT370 RAID or Vinum?) Message-ID: <20010914101229.G58338@freebsd06.udt> Mail-Followup-To: Trent Nelson , john_wilson100@excite.com, Greg Lehey , freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG References: <20775668.1000430889008.JavaMail.imail@doby.excite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20775668.1000430889008.JavaMail.imail@doby.excite.com>; from john_wilson100@excite.com on Thu, Sep 13, 2001 at 06:28:02PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Sep 13, 2001 at 06:28:02PM -0700, john_wilson100@excite.com wrote: > Well, I have to say that Vinum feels a lot faster than HPT RAID... I will > quantify this statement when someone tells me how to turn off ATA write > caching, because > > sysctl -w hw.ata.wc=0 > > doesn't work, says "sysctl: oid 'hw.ata.wc' is read only" # echo 'hw.ata.wc="1"' >> /boot/loader.conf Read-only sysctls have to be set here. On the note of write-caching - I was extremely surprised to notice how significant the performance increase is with it turned on. What used to take ~5 seconds to dump a 20-30MB core, now takes <1s. Regards, Trent. -- Trent Nelson - Software Engineer - nelsont@switch.aust.com "A man with unlimited enthusiasm can achieve almost anything." --unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 17:49:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id F3C0B37B40A for ; Sun, 16 Sep 2001 17:49:36 -0700 (PDT) Received: from strontium.shef.vinosystems.com ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.30 #1) id 15imbN-000IT5-00; Mon, 17 Sep 2001 01:49:33 +0100 Received: (from ben@localhost) by strontium.shef.vinosystems.com (8.11.6/8.11.4) id f8H0nXi27354; Mon, 17 Sep 2001 01:49:33 +0100 (BST) (envelope-from ben@FreeBSD.org) X-Authentication-Warning: strontium.shef.vinosystems.com: ben set sender to ben@FreeBSD.org using -f Date: Mon, 17 Sep 2001 01:49:32 +0100 From: Ben Smithurst To: Tim Allshorn Cc: freebsd-hackers@freebsd.org Subject: Re: Cron pickle Message-ID: <20010917014932.V43502@strontium.shef.vinosystems.com> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="7mIJwGTFTwAlEXlA" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: X-PGP-Key: http://www.smithurst.org/ben/pgp-key.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --7mIJwGTFTwAlEXlA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Tim Allshorn wrote: > I know the cron command has to be something like : 59 23 ? ? * , with= =20 > maybe some condition on the end. I think you could use something like 59 23 28-31 * * [ `date -v+1M +%d` -eq 1 ] && /path/to/your/program i.e., check that in one minute's time the day of the month is 1, if so, run the program. --=20 Ben Smithurst / ben@FreeBSD.org FreeBSD: The Power To Serve http://www.FreeBSD.org/ --7mIJwGTFTwAlEXlA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7pUicbPzJ+yzvRCwRAiL+AKC8EdzNAbS+PRSwxLsDrT7tyrQylgCdFpUb wVswnd2SkB2cB2Blyg+98vE= =62V8 -----END PGP SIGNATURE----- --7mIJwGTFTwAlEXlA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 18: 7:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 092BF37B401; Sun, 16 Sep 2001 18:07:20 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id C26E981D08; Sun, 16 Sep 2001 20:07:14 -0500 (CDT) Date: Sun, 16 Sep 2001 20:07:14 -0500 From: Alfred Perlstein To: Ben Smithurst Cc: Tim Allshorn , freebsd-hackers@freebsd.org Subject: Re: Cron pickle Message-ID: <20010916200714.X968@elvis.mu.org> References: <20010917014932.V43502@strontium.shef.vinosystems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010917014932.V43502@strontium.shef.vinosystems.com>; from ben@FreeBSD.org on Mon, Sep 17, 2001 at 01:49:32AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Ben Smithurst [010916 19:49] wrote: > Tim Allshorn wrote: > > > I know the cron command has to be something like : 59 23 ? ? * , with > > maybe some condition on the end. > > I think you could use something like > > 59 23 28-31 * * [ `date -v+1M +%d` -eq 1 ] && /path/to/your/program > > i.e., check that in one minute's time the day of the month is 1, if so, > run the program. I'm not a date(1) wizard, but there's a possible issue here, if the system is loaded cron may skip a beat possibly and that conditional may be delayed such that it doesn't trigger. My suggestion would be to use something more sophisticated such as a file someplace that tracks the last time it was run to make sure there's no race here. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 18:19:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 5052437B406 for ; Sun, 16 Sep 2001 18:19:22 -0700 (PDT) Received: from strontium.shef.vinosystems.com ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.30 #1) id 15in49-000676-00; Mon, 17 Sep 2001 02:19:17 +0100 Received: (from ben@localhost) by strontium.shef.vinosystems.com (8.11.6/8.11.4) id f8H1JHe94356; Mon, 17 Sep 2001 02:19:17 +0100 (BST) (envelope-from ben@FreeBSD.org) X-Authentication-Warning: strontium.shef.vinosystems.com: ben set sender to ben@FreeBSD.org using -f Date: Mon, 17 Sep 2001 02:19:17 +0100 From: Ben Smithurst To: Alfred Perlstein Cc: Tim Allshorn , freebsd-hackers@freebsd.org Subject: Re: Cron pickle Message-ID: <20010917021917.W43502@strontium.shef.vinosystems.com> References: <20010917014932.V43502@strontium.shef.vinosystems.com> <20010916200714.X968@elvis.mu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="nKvJs6ze6az+4fwY" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010916200714.X968@elvis.mu.org> X-PGP-Key: http://www.smithurst.org/ben/pgp-key.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --nKvJs6ze6az+4fwY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Alfred Perlstein wrote: > * Ben Smithurst [010916 19:49] wrote: >> Tim Allshorn wrote: >>=20 >>> I know the cron command has to be something like : 59 23 ? ? * , wi= th=20 >>> maybe some condition on the end. >>=20 >> I think you could use something like >>=20 >> 59 23 28-31 * * [ `date -v+1M +%d` -eq 1 ] && /path/to/your/program >>=20 >> i.e., check that in one minute's time the day of the month is 1, if so, >> run the program. >=20 > I'm not a date(1) wizard, but there's a possible issue here, if > the system is loaded cron may skip a beat possibly and that > conditional may be delayed such that it doesn't trigger. I thought only advancing it 1 minute would make it safe. My reasoning for not advancing it by 1 day was that if there was enough load to delay by 61 seconds, then advancing the time from there by one day would lead to the 2nd. But I think there would have to be about a 24 hour delay here for this to go wrong, since advancing it by a minute will still lead it to end up in the 1st for that long... but then I'm not a date wizard either, maybe someone who is can step in. :-) Although just using a file like you suggest might stop everyone being paranoid that it might go wrong. --=20 Ben Smithurst / ben@FreeBSD.org FreeBSD: The Power To Serve http://www.FreeBSD.org/ --nKvJs6ze6az+4fwY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7pU+UbPzJ+yzvRCwRAsXaAJwICGNgjapGaxjZvYyZCDNIsh95CgCfZG48 bXVNpU5PMGBaUs2k0T4qGhY= =PgYR -----END PGP SIGNATURE----- --nKvJs6ze6az+4fwY-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 18:33:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id C699A37B409; Sun, 16 Sep 2001 18:33:39 -0700 (PDT) Received: by tao.org.uk (Postfix, from userid 100) id 288DB3B6; Mon, 17 Sep 2001 02:33:34 +0100 (BST) Date: Mon, 17 Sep 2001 02:33:34 +0100 From: Josef Karthauser To: Alfred Perlstein Cc: Ben Smithurst , Tim Allshorn , freebsd-hackers@freebsd.org Subject: Re: Cron pickle Message-ID: <20010917023333.A3916@tao.org.uk> Mail-Followup-To: Josef Karthauser , Alfred Perlstein , Ben Smithurst , Tim Allshorn , freebsd-hackers@freebsd.org References: <20010917014932.V43502@strontium.shef.vinosystems.com> <20010916200714.X968@elvis.mu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010916200714.X968@elvis.mu.org>; from bright@mu.org on Sun, Sep 16, 2001 at 08:07:14PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 16, 2001 at 08:07:14PM -0500, Alfred Perlstein wrote: >=20 > I'm not a date(1) wizard, but there's a possible issue here, if > the system is loaded cron may skip a beat possibly and that > conditional may be delayed such that it doesn't trigger. >=20 > My suggestion would be to use something more sophisticated such as > a file someplace that tracks the last time it was run to make sure > there's no race here. Or something less sophisticated like 12 cron entries, one for each month. Joe --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjulUu0ACgkQXVIcjOaxUBa8gwCgthWVXLM+oh584cNSLgbjDRoi nrUAn3w4aRz+Wcu643QCzd0UbhXW5SyS =wsit -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 18:46:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 9F1C037B406 for ; Sun, 16 Sep 2001 18:46:54 -0700 (PDT) Received: from mindspring.com (dialup-209.245.138.236.Dial1.SanJose1.Level3.net [209.245.138.236]) by albatross.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id SAA29588; Sun, 16 Sep 2001 18:46:51 -0700 (PDT) Message-ID: <3BA55638.91CD4CCA@mindspring.com> Date: Sun, 16 Sep 2001 18:47:36 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Tim Allshorn Cc: freebsd-hackers@freebsd.org Subject: Re: Cron pickle References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Tim Allshorn wrote: > > Hello. > I need to be able to run a particular program at the last > minute of each month and yes I know it would be much easier to > run it at the first minute of each month, but my hands are tied > and my brain is too puny to work it out. 1) Run it the first minute of each month. 2) Set your system clock back one minute. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 18:58:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id E801837B40F for ; Sun, 16 Sep 2001 18:58:55 -0700 (PDT) Received: (from dan@localhost) by dan.emsphone.com (8.11.4/8.11.4) id f8H1wqv25331; Sun, 16 Sep 2001 20:58:52 -0500 (CDT) (envelope-from dan) Date: Sun, 16 Sep 2001 20:58:52 -0500 From: Dan Nelson To: Terry Lambert Cc: Tim Allshorn , freebsd-hackers@FreeBSD.ORG Subject: Re: Cron pickle Message-ID: <20010916205852.A14117@dan.emsphone.com> References: <3BA55638.91CD4CCA@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BA55638.91CD4CCA@mindspring.com> User-Agent: Mutt/1.3.22.1i X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Sep 16), Terry Lambert said: > Tim Allshorn wrote: > > I need to be able to run a particular program at the last > > minute of each month and yes I know it would be much easier to run > > it at the first minute of each month, but my hands are tied and my > > brain is too puny to work it out. > > 1) Run it the first minute of each month. > > 2) Set your system clock back one minute. or: 1) Run it the last minute of each day 2) Exit immediately unless it's the last day of the month If you do not have source to the program, wrap it in a script that does the date check. -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 19: 1:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by hub.freebsd.org (Postfix) with ESMTP id 0162037B403 for ; Sun, 16 Sep 2001 19:01:28 -0700 (PDT) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.11.1/8.11.1) id f8H21Rn36517 for freebsd-hackers@FreeBSD.ORG; Sun, 16 Sep 2001 22:01:27 -0400 (EDT) (envelope-from bicknell) Date: Sun, 16 Sep 2001 22:01:27 -0400 From: Leo Bicknell To: freebsd-hackers@FreeBSD.ORG Subject: Re: Cron pickle Message-ID: <20010916220127.A35836@ussenterprise.ufp.org> Mail-Followup-To: Leo Bicknell , freebsd-hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ta_iy@hotmail.com on Mon, Sep 17, 2001 at 10:40:15AM +1000 Organization: United Federation of Planets Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 17, 2001 at 10:40:15AM +1000, Tim Allshorn wrote: > I need to be able to run a particular program at the last minute of each > month and yes I know it would be much easier to run it at the first minute > of each month, but my hands are tied and my brain is too puny to work it > out. I think you want 12 cron entries, one for each month. That said, you might want to rethink what you are doing. While it would be unusual, on a heavily loaded machine, or a machine experiencing some form of clock skew (eg our recent fast clock SMP issue) there is no guarantee that the process is actually run in the last minute, or even if it is started in the last minute that it would complete in that minute. Since running on the first minute seems unacceptable for some reason I can only assume that is important in your current setup. -- Leo Bicknell - bicknell@ufp.org Systems Engineer - Internetworking Engineer - CCIE 3440 Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 19:17:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id 7CB5637B40E for ; Sun, 16 Sep 2001 19:17:33 -0700 (PDT) Received: (qmail 89980 invoked by uid 1001); 17 Sep 2001 12:17:30 +1000 Message-ID: X-Posted-By: GJB-Post 2.21 16-Jun-2001 X-Operating-System: FreeBSD 4.2-RELEASE i386 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.gbch.net/gjb.html X-Image-URL: http://www.gbch.net/gjb/gjb-auug048.gif X-GPG-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-PGP-Public-Keys: http://www.gbch.net/keys.html Date: Mon, 17 Sep 2001 12:17:30 +1000 From: Greg Black To: Tim Allshorn Cc: freebsd-hackers@freebsd.org Subject: Re: Cron pickle References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Tim Allshorn wrote: | I need to be able to run a particular program at the last | minute of each month and yes I know it would be much easier to | run it at the first minute of each month, but my hands are tied | and my brain is too puny to work it out. This cannot be done with cron, even with multiple entries. You can use cron to schedule something for minute zero of each month and that should be good enough for any reasonable use. If you are working for somebody irrational who thinks he needs something done on the last minute of each month, you'll have to run it at 23:59 on days 28-31 every month and have the program determine for itself if this is the last day of this month this year. For those who think it can be done with multiple entries, you have forgotten that one month has a variable number of days and cron has no concept of years -- so you can't specify the right thing for the last day of February in a crontab file. And if you don't care about the leap year case for February, then you can't possibly care if the job is run on the zeroth minute of the first of the month, and that's easy to specify. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 19:34:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id EB8FE37B408 for ; Sun, 16 Sep 2001 19:34:28 -0700 (PDT) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 85A706AD6A; Mon, 17 Sep 2001 12:04:27 +0930 (CST) Date: Mon, 17 Sep 2001 12:04:27 +0930 From: Greg Lehey To: john_wilson100@excite.com Cc: freebsd-hackers@freebsd.org Subject: Re: VINUM PANIC ON -STABLE Message-ID: <20010917120427.M3782@wantadilla.lemis.com> References: <24460926.1000670447361.JavaMail.imail@doby.excite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <24460926.1000670447361.JavaMail.imail@doby.excite.com>; from john_wilson100@excite.com on Sun, Sep 16, 2001 at 01:00:41PM -0700 Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday, 16 September 2001 at 13:00:41 -0700, john_wilson100@excite.com wrote: > > On Sun, 16 Sep 2001 11:42:38 +0930, Greg Lehey wrote: > >>> 6) Supply an extract of the file /var/log/messages. >>> >>> Sep 12 14:06:10 depot login: ROOT LOGIN (root) ON ttyv0 >>> Sep 12 14:07:29 depot login: ROOT LOGIN (root) ON ttyv1 >>> Sep 13 01:58:14 depot /kernel: vinum: loaded >>> Sep 13 01:58:15 depot /kernel: vinum: drive data1 is up >>> Sep 13 01:58:15 depot /kernel: vinum: drive home1 is up >>> Sep 13 01:58:15 depot /kernel: vinum: drive home2 is up >>> Sep 13 01:58:15 depot /kernel: vinum: removing 499 blocks of partial > stripe at the end of data.p0 >>> Sep 13 01:58:15 depot /kernel: vinum: data.p0 must have equal sized > subdisks >>> Sep 13 01:58:15 depot /kernel: Correcting length of data.p0: was > 20970756, is 20970757 >> >> I suspect that this is the problem. I've seen isolated cases where >> the stripe size didn't get fixed correctly, leaving holes in the >> volume. Could you send me the output of 'vinum l -v', please? And >> please don't wrap log output, it makes it a pain to read. > > Hmm, I don't think I wrapped anything, if you go to > > http://docs.freebsd.org/mail/current/ > > (or wherever the last week's messages are), you'll see that the log > output is not wrapped. It must be your own mailer that wraps it > on receipt. Did you read the URL I quoted? Many MUAs wrap text without telling you. mutt, which I use, isn't one of them, and the MTA definitely doesn't. It arrived that way. > Here's the output of "vinum l -v": > 4 subdisks: > Subdisk data.p0.s0: > Size: 10737027072 bytes (10239 MB) > State: up > Plex data.p0 at offset 0 (0 B) > Drive data1 (/dev/ad4s1g) at offset 135680 (132 kB) > > Subdisk data.p0.s1: > Size: 10737027072 bytes (10239 MB) > State: up > Plex data.p0 at offset 285696 (279 kB) > Drive data2 (/dev/ad6s1e) at offset 135680 (132 kB) OK, look at these two: they're both the same size, like they should be. > Subdisk home.p0.s0: > Size: 40822392320 bytes (38931 MB) > State: up > Plex home.p0 at offset 0 (0 B) > Drive home1 (/dev/ad4s1h) at offset 135680 (132 kB) > > Subdisk home.p0.s1: > Size: 39566177280 bytes (37733 MB) > State: up > Plex home.p0 at offset 285696 (279 kB) > Drive home2 (/dev/ad6s1f) at offset 135680 (132 kB) These ones, though, are different. That's a bug in Vinum. You didn't say, but I assume that it was the newfs of home that caused the crash. This is directly related to the fact that your two partitions are of different size: Drive home1: Device /dev/ad4s1h Created on depot at Thu Sep 13 01:58:14 2001 Config last updated Sun Sep 16 03:28:31 2001 Size: 40822630912 bytes (38931 MB) Used: 40822528000 bytes (38931 MB) Available: 102912 bytes (0 MB) State: up Last error: none Active requests: 0 Maximum active: 0 Drive home2: Device /dev/ad6s1f Created on depot at Thu Sep 13 02:02:33 2001 Config last updated Sun Sep 16 03:28:31 2001 Size: 39566415872 bytes (37733 MB) Used: 39566312960 bytes (37733 MB) Available: 102912 bytes (0 MB) You should really repartition your physical drives (spindles) to have only one Vinum drive each. Then make sure that both subdisks are of the same size, and you shouldn't have any more problems. Yes, this doesn't fix the bug, but I'll work on that. >> Agreed. You're collateral damage. But I can't find that out >> until I hear about it. I've opened the server for you. > > I'm not sure I like being called "collateral damage", but thanks > anyway. You're not supposed to. But you're really the first person from excite who wanted to contact me. Greg -- 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 Sun Sep 16 20: 0: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by hub.freebsd.org (Postfix) with ESMTP id 27B6937B405 for ; Sun, 16 Sep 2001 20:00:04 -0700 (PDT) Received: (from root@localhost) by www.svzserv.kemerovo.su (8.9.3/8.9.3) id KAA07166; Mon, 17 Sep 2001 10:59:32 +0800 (KRAST) (envelope-from eu) Date: Mon, 17 Sep 2001 10:59:32 +0800 From: Eugene Grosbein To: Greg Black Cc: Tim Allshorn , freebsd-hackers@freebsd.org Subject: Re: Cron pickle Message-ID: <20010917105932.A5338@svzserv.kemerovo.su> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gjb@gbch.net on Mon, Sep 17, 2001 at 12:17:30PM +1000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 17, 2001 at 12:17:30PM +1000, Greg Black wrote: > | I need to be able to run a particular program at the last > | minute of each month and yes I know it would be much easier to > | run it at the first minute of each month, but my hands are tied > | and my brain is too puny to work it out. > > This cannot be done with cron, even with multiple entries. You > can use cron to schedule something for minute zero of each month > and that should be good enough for any reasonable use. This can be done with cron with single entry and small overhead. Run whis script at last minute of every day (or every 28-31): #!/bin/sh tomorrow=`date -v+1d %d` if [ $tomorroq -ne "01" ]; then exit # if tomorrow is not begin of month, do nothing fi # do work now ... Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 20: 4:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gigi.excite.com (gigi.excite.com [199.172.152.110]) by hub.freebsd.org (Postfix) with ESMTP id EF81337B40B; Sun, 16 Sep 2001 20:04:52 -0700 (PDT) Received: from doby.excite.com ([199.172.152.182]) by gigi.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20010917030452.USKW24199.gigi.excite.com@doby.excite.com>; Sun, 16 Sep 2001 20:04:52 -0700 Message-ID: <29623361.1000695892678.JavaMail.imail@doby.excite.com> Date: Sun, 16 Sep 2001 20:04:46 -0700 (PDT) From: john_wilson100@excite.com To: Greg Lehey Subject: Re: VINUM PANIC ON -STABLE Cc: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Excite Inbox X-Sender-Ip: 62.90.91.30 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Greg, On Mon, 17 Sep 2001 12:04:27 +0930, Greg Lehey wrote: > > > Subdisk home.p0.s0: > > Size: 40822392320 bytes (38931 MB) > > State: up > > Plex home.p0 at offset 0 (0 B) > > Drive home1 (/dev/ad4s1h) at offset 135680 (132 kB) > > > > Subdisk home.p0.s1: > > Size: 39566177280 bytes (37733 MB) > > State: up > > Plex home.p0 at offset 285696 (279 kB) > > Drive home2 (/dev/ad6s1f) at offset 135680 (132 kB) > > These ones, though, are different. That's a bug in Vinum. You > didn't say, but I assume that it was the newfs of home that caused > the crash. It was newfs indeed. I had initially miscounted the size of the second partition and instead of repartitioning, decided to put 0 in the config file hoping that Vinum would choose the lowest common denominator. > You should really repartition your physical drives (spindles) to > have only one Vinum drive each. Then make sure that both subdisks > are of the same size, and you shouldn't have any more problems. > Yes, this doesn't fix the bug, but I'll work on that. Great, I'll do that. Do you have enough information to fix the bug? I presume the coredumps are of little use to you, because you already know what caused the crash, but please let me know if you want me to keep them. Thanks John > >> Agreed. You're collateral damage. But I can't find that out > >> until I hear about it. I've opened the server for you. > > > > I'm not sure I like being called "collateral damage", but thanks > > anyway. > > You're not supposed to. But you're really the first person from > excite who wanted to contact me. > > Greg > -- > See complete headers for address and phone numbers _______________________________________________________ Send a cool gift with your E-Card http://www.bluemountain.com/giftcenter/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 20: 8:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id CC8C137B40B for ; Sun, 16 Sep 2001 20:08:02 -0700 (PDT) Received: (qmail 92928 invoked by uid 1001); 17 Sep 2001 13:07:59 +1000 Message-ID: X-Posted-By: GJB-Post 2.21 16-Jun-2001 X-Operating-System: FreeBSD 4.2-RELEASE i386 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.gbch.net/gjb.html X-Image-URL: http://www.gbch.net/gjb/gjb-auug048.gif X-GPG-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-PGP-Public-Keys: http://www.gbch.net/keys.html Date: Mon, 17 Sep 2001 13:07:59 +1000 From: Greg Black To: Eugene Grosbein Cc: Tim Allshorn , freebsd-hackers@freebsd.org Subject: Re: Cron pickle References: <20010917105932.A5338@svzserv.kemerovo.su> In-reply-to: <20010917105932.A5338@svzserv.kemerovo.su> of Mon, 17 Sep 2001 10:59:32 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Eugene Grosbein wrote: | On Mon, Sep 17, 2001 at 12:17:30PM +1000, Greg Black wrote: | | > | I need to be able to run a particular program at the last | > | minute of each month and yes I know it would be much easier to | > | run it at the first minute of each month, but my hands are tied | > | and my brain is too puny to work it out. | > | > This cannot be done with cron, even with multiple entries. You | > can use cron to schedule something for minute zero of each month | > and that should be good enough for any reasonable use. | | This can be done with cron with single entry and small overhead. | Run whis script at last minute of every day (or every 28-31): | | #!/bin/sh | | tomorrow=`date -v+1d %d` | if [ $tomorroq -ne "01" ]; then | exit # if tomorrow is not begin of month, do nothing | fi | | # do work now Sure: $ date -v+1d %d date: illegal time format usage: date [-nu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ... [-f fmt date | [[[[[cc]yy]mm]dd]HH]MM[.ss]] [+format] $ date '-v+1d %d' +1d %d: Cannot apply date adjustment usage: date [-nu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ... [-f fmt date | [[[[[cc]yy]mm]dd]HH]MM[.ss]] [+format] Assuming you actually figure out how to get this thing right, it makes my point -- you can't do this with a cron specification, but you have to do the decision-making in the program. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 20:22:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (bdsl.66.12.217.106.gte.net [66.12.217.106]) by hub.freebsd.org (Postfix) with ESMTP id 0B5BA37B406 for ; Sun, 16 Sep 2001 20:22:01 -0700 (PDT) Received: (from steve@localhost) by virtual-voodoo.com (8.11.6/8.11.5) id f8H3HTR15682; Sun, 16 Sep 2001 22:17:29 -0500 (EST) (envelope-from steve) Date: Sun, 16 Sep 2001 22:17:29 -0500 From: Steve Ames To: Greg Black Cc: Eugene Grosbein , Tim Allshorn , freebsd-hackers@FreeBSD.ORG Subject: Re: Cron pickle Message-ID: <20010916221729.A25329@virtual-voodoo.com> References: <20010917105932.A5338@svzserv.kemerovo.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gjb@gbch.net on Mon, Sep 17, 2001 at 01:07:59PM +1000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 17, 2001 at 01:07:59PM +1000, Greg Black wrote: > Eugene Grosbein wrote: > | This can be done with cron with single entry and small overhead. > | Run whis script at last minute of every day (or every 28-31): > | > | #!/bin/sh > | > | tomorrow=`date -v+1d %d` > | if [ $tomorroq -ne "01" ]; then > | exit # if tomorrow is not begin of month, do nothing > | fi > | > | # do work now > > Sure: > > $ date -v+1d %d date -v+1d +%d -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 21:33:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by hub.freebsd.org (Postfix) with ESMTP id 0242837B403 for ; Sun, 16 Sep 2001 21:33:20 -0700 (PDT) Received: from svzserv.kemerovo.su (kost [213.184.65.82]) by www.svzserv.kemerovo.su (8.9.3/8.9.3) with ESMTP id LAA11455; Mon, 17 Sep 2001 11:33:29 +0800 (KRAST) (envelope-from eugen@svzserv.kemerovo.su) Message-ID: <3BA56F0E.6A5C4076@svzserv.kemerovo.su> Date: Mon, 17 Sep 2001 11:33:35 +0800 From: Eugene Grosbein Organization: SVZServ X-Mailer: Mozilla 4.76 [en] (Win95; U) X-Accept-Language: ru,en MIME-Version: 1.0 To: Greg Black Cc: Eugene Grosbein , Tim Allshorn , freebsd-hackers@freebsd.org Subject: Re: Cron pickle References: <20010917105932.A5338@svzserv.kemerovo.su> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greg Black wrote: > > Eugene Grosbein wrote: > > | On Mon, Sep 17, 2001 at 12:17:30PM +1000, Greg Black wrote: > | > | > | I need to be able to run a particular program at the last > | > | minute of each month and yes I know it would be much easier to > | > | run it at the first minute of each month, but my hands are tied > | > | and my brain is too puny to work it out. > | > > | > This cannot be done with cron, even with multiple entries. You > | > can use cron to schedule something for minute zero of each month > | > and that should be good enough for any reasonable use. > | > | This can be done with cron with single entry and small overhead. > | Run whis script at last minute of every day (or every 28-31): > | > | #!/bin/sh > | > | tomorrow=`date -v+1d %d` > | if [ $tomorroq -ne "01" ]; then > | exit # if tomorrow is not begin of month, do nothing > | fi > | > | # do work now > > Sure: > > $ date -v+1d %d > date: illegal time format > usage: date [-nu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ... > [-f fmt date | [[[[[cc]yy]mm]dd]HH]MM[.ss]] [+format] Sorry, my example is full of mistakes. Really it should look like this: #!/bin/sh tomorrow=`date -v+1d +%d` if [ $tomorrow -ne "01" ]; then exit fi # proceed now Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 16 22: 6: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 1EC3337B40C for ; Sun, 16 Sep 2001 22:05:59 -0700 (PDT) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 2C6FA6AD6A; Mon, 17 Sep 2001 14:35:57 +0930 (CST) Date: Mon, 17 Sep 2001 14:35:57 +0930 From: Greg Lehey To: john_wilson100@excite.com Cc: freebsd-hackers@freebsd.org Subject: Re: VINUM PANIC ON -STABLE Message-ID: <20010917143557.F494@wantadilla.lemis.com> References: <29623361.1000695892678.JavaMail.imail@doby.excite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <29623361.1000695892678.JavaMail.imail@doby.excite.com>; from john_wilson100@excite.com on Sun, Sep 16, 2001 at 08:04:46PM -0700 Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday, 16 September 2001 at 20:04:46 -0700, john_wilson100@excite.com wrote: > Hi Greg, > > > On Mon, 17 Sep 2001 12:04:27 +0930, Greg Lehey wrote: >> >>> Subdisk home.p0.s0: >>> Size: 40822392320 bytes (38931 MB) >>> State: up >>> Plex home.p0 at offset 0 (0 B) >>> Drive home1 (/dev/ad4s1h) at offset 135680 (132 kB) >>> >>> Subdisk home.p0.s1: >>> Size: 39566177280 bytes (37733 MB) >>> State: up >>> Plex home.p0 at offset 285696 (279 kB) >>> Drive home2 (/dev/ad6s1f) at offset 135680 (132 kB) >> >> These ones, though, are different. That's a bug in Vinum. You >> didn't say, but I assume that it was the newfs of home that caused >> the crash. > > It was newfs indeed. I had initially miscounted the size of the > second partition and instead of repartitioning, decided to put 0 in > the config file hoping that Vinum would choose the lowest common > denominator. It should do. As I say, it's a bug. >> You should really repartition your physical drives (spindles) to >> have only one Vinum drive each. Then make sure that both subdisks >> are of the same size, and you shouldn't have any more problems. >> Yes, this doesn't fix the bug, but I'll work on that. > > Great, I'll do that. Do you have enough information to fix the bug? I think so. If not, I hope I have enough information to reproduce it. If anybody else listening wants to have a go, it's in the function update_plex_config in vinumconfig.c. I've taken a look, and there's no check there that the sizes are the same, though it does check that the subdisk sizes are a multiple of the stripe size. > I presume the coredumps are of little use to you, because you > already know what caused the crash, but please let me know if you > want me to keep them. No, I should be able to reproduce it here. Thanks for the offer. Greg -- 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 Sun Sep 16 22: 6:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.urx.com (2811.dynacom.net [206.107.213.4]) by hub.freebsd.org (Postfix) with ESMTP id 2BC0837B407; Sun, 16 Sep 2001 22:06:17 -0700 (PDT) Received: from urx.com [206.159.132.160] by mail.urx.com with ESMTP (SMTPD32-7.03) id A4C0937017E; Sun, 16 Sep 2001 22:06:08 -0700 Message-ID: <3BA584BC.906CD737@urx.com> Date: Sun, 16 Sep 2001 22:06:04 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: David O'Brien , rnordier@FreeBSD.org, msmith@FreeBSD.org, roam@ringlet.net, freebsd-hackers@FreeBSD.org Subject: Re: Does boot1 still have a > 1023 cyl limit? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > > On 15-Sep-01 David O'Brien wrote: > > On Fri, Sep 14, 2001 at 03:05:01PM -0700, John Baldwin wrote: > >> 'disklabel -B ad0' as root, where 'ad0' is the disk that boots FreeBSD > > > > Isn't `disklable -B ad0sX' more proper? (especially if the disk has > > multiple FreeBSD slices) > > On x86, yes. I think disklabel -B ad0 will still work though. (It finds the > first FreeBSD slice and does it I think). I tried some more things today since I had a running system. The "disklabel -B ad0s3" works on my system. I can't use the ntldr until I replace the boot record used to boot FreeBSD. Once I copied boot1 to bootsect.bsd, which is what I have in boot.ini, W2K would boot FreeBSD. Having to replace what ntldr was using didn't occur to me until I made the W2K partition the active one and it wouldn't boot FreeBSD. Once I had a matched set, everything was ok. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 1:44:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shaft.techsupport.co.uk (shaft.techsupport.co.uk [212.250.77.214]) by hub.freebsd.org (Postfix) with ESMTP id 0A95937B405 for ; Mon, 17 Sep 2001 01:44:23 -0700 (PDT) Received: from rasputin by shaft.techsupport.co.uk with local (Exim 3.22 #1) id 15iu4Y-000AKc-00 for hackers@freebsd.org; Mon, 17 Sep 2001 09:48:10 +0100 Date: Mon, 17 Sep 2001 09:48:10 +0100 From: Rasputin To: hackers@freebsd.org Subject: Re: 802.11 with best Apple compatibility? Message-ID: <20010917094810.A39701@shaft.techsupport.co.uk> Reply-To: Rasputin References: <20010914150203.A30720@shaft.techsupport.co.uk> <20010914103037.A5619@ussenterprise.ufp.org> <20010914101548.B7169@Odin.AC.HMC.Edu> <3BA23F2E.23F68B29@mitre.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BA23F2E.23F68B29@mitre.org>; from jandrese@mitre.org on Fri, Sep 14, 2001 at 01:32:30PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Jason Andresen [010914 18:39]: > Brooks Davis wrote: > > > > On Fri, Sep 14, 2001 at 10:30:37AM -0400, Leo Bicknell wrote: > > > On Fri, Sep 14, 2001 at 03:02:03PM +0100, Rasputin wrote: > > > > Is there any difference between Gold and Silver cards from > > > > a compatibility standpoint (with the usual Apple Airport cards)? > > > > > > With WEP encryption turned off they both work together fine. I've > > > seen many used in mixed enviornments. With WEP turned on, they > > > are completely incomptable. The silver cards do a 40 bit encryption, > > > and the gold cards do a 128 bit encryption, and it seems the gold > > > cards can't be stepped back to 40 bit. > > > > Unless Apple is mangling the firmware or someone screwed up the driver, > > this is false. Gold Lucent cards are capable of 40-bit crypto. > > Aren't the airport cards just plain old Silver Lucent cards? If so, > then > either the Gold or the Silver should work fine. > In fact I know the silver works fine because I have an Airport at home > that > I talk to with a Silver card. There's a FreeBSD port that lets you > configure the box from your machine. In Windowsland there's a program > called FreeBase, and of course the Airport comes with Mac tools bundled. Thnaks a lot for the confirmation - for the record, I'm trying to replace a basestation, not communicate with one. But as long as Lucents are compatible, I 'll go for one of those.. (I only need WEP while I get a crash course in IPSec :) ) I take it the PCI PCMCIA adapters are still unsupported? (on 4-STABLE) -- Did you know that if you took all the economists in the world and lined them up end to end, they'd still point in the wrong direction? Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 1:55:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id 8BE9637B407 for ; Mon, 17 Sep 2001 01:55:34 -0700 (PDT) Received: from mindspring.com (dialup-209.244.106.50.Dial1.SanJose1.Level3.net [209.244.106.50]) by scaup.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA08114; Mon, 17 Sep 2001 01:55:31 -0700 (PDT) Message-ID: <3BA5BAB2.9098CC61@mindspring.com> Date: Mon, 17 Sep 2001 01:56:18 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rasputin Cc: hackers@freebsd.org Subject: Re: 802.11 with best Apple compatibility? References: <20010914150203.A30720@shaft.techsupport.co.uk> <20010914103037.A5619@ussenterprise.ufp.org> <20010914101548.B7169@Odin.AC.HMC.Edu> <3BA23F2E.23F68B29@mitre.org> <20010917094810.A39701@shaft.techsupport.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Rasputin wrote: > Thnaks a lot for the confirmation - for the record, I'm trying > to replace a basestation, not communicate with one. The timing for access points requires different firmware; you can't do it in software alone. Talk to Julian Elisher; he presented on a company that sells a FreeBSD driver with firmware (binary only for the whole thing) that can make a FreeBSD box into an access point, using specific hardware. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 3:43:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id D902C37B408 for ; Mon, 17 Sep 2001 03:43:30 -0700 (PDT) Received: (qmail 94665 invoked by uid 1000); 17 Sep 2001 10:43:49 -0000 Date: Mon, 17 Sep 2001 12:43:49 +0200 From: "Karsten W. Rohrbach" To: Tim Allshorn Cc: freebsd-hackers@freebsd.org Subject: Re: Cron pickle Message-ID: <20010917124349.C93774@mail.webmonster.de> Mail-Followup-To: "Karsten W. Rohrbach" , Tim Allshorn , freebsd-hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="bAmEntskrkuBymla" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ta_iy@hotmail.com on Mon, Sep 17, 2001 at 10:40:15AM +1000 X-Arbitrary-Number-Of-The-Day: 42 X-URL: http://www.webmonster.de/ X-Disclaimer: My opinions do not necessarily represent those of my employer X-Work-URL: http://www.ngenn.net/ X-Work-Address: nGENn GmbH, Schloss Kransberg, D-61250 Usingen-Kransberg, Germany X-Work-Phone: +49-6081-682-304 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --bAmEntskrkuBymla Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Tim Allshorn(ta_iy@hotmail.com)@2001.09.17 10:40:15 +0000: > Hello. > I need to be able to run a particular program at the last minute of e= ach=20 > month and yes I know it would be much easier to run it at the first minut= e=20 > of each month, but my hands are tied and my brain is too puny to work it= =20 > out. cron is not a good idea, because it might start the process delayed. naturally, the same with at. you might check out runwhen or other alternative schedulers that actually give you the instrumentation you need. [http://multivac.cwru.edu/runwhen/] might be a candidate /k --=20 > Condoms are like listening to a symphony with cotton in your ears. KR433/KR11-RIPE -- WebMonster Community Founder -- nGENn GmbH Senior Techie http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.ngenn.n= et/ karsten&rohrbach.de -- alpha&ngenn.net -- alpha&scene.org -- catch@spam.de GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 B= F46 Please do not remove my address from To: and Cc: fields in mailing lists. 1= 0x --bAmEntskrkuBymla Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7pdPlM0BPTilkv0YRAioUAJ9SUyZvQvPIa/C8Fwu+82zvthYUBACgqIYe 0JIhqXCe5X84FyQkriYytyc= =IJ8y -----END PGP SIGNATURE----- --bAmEntskrkuBymla-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 4:29:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 7953937B40F for ; Mon, 17 Sep 2001 04:29:21 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [fec0::1:12]) by Awfulhak.org (8.11.6/8.11.6) with ESMTP id f8HBTGg23481; Mon, 17 Sep 2001 12:29:18 +0100 (BST) (envelope-from brian@freebsd-services.com) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.6/8.11.6) with ESMTP id f8HBTAR28246; Mon, 17 Sep 2001 12:29:10 +0100 (BST) (envelope-from brian@freebsd-services.com) Message-Id: <200109171129.f8HBTAR28246@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Giorgos Keramidas Cc: Brian Somers , hackers@FreeBSD.ORG, brian@freebsd-services.com Subject: Re: Checking changes to listening ports in /etc/security In-Reply-To: Message from Giorgos Keramidas of "Fri, 14 Sep 2001 17:57:18 +0300." <20010914175718.A1118@hades.hell.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Sep 2001 12:29:10 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > From: Brian Somers > Subject: Re: Checking changes to listening ports in /etc/security > Date: Fri, Sep 14, 2001 at 12:18:43PM +0100 > > > I think the attached patch makes things slightly better. We only run > > sockstat once, and remove the trailing whitespace that sockstat emits > > (making the diff lines look better when viewed on an 80 column > > screen). > > Ahem, that's what happens when one works in 132 column modes. > Yes, trailing spaces are better removed. > > > Could you look these over ? If you're happy with this I can commit > > it. > > Looks great to me. I tested it with the usual four runs of > periodic/daily/450.status-security that I used for my versions. > It works great :) I found a problem... if you reboot a machine, lots of diffs come up because of the PID column. I've got a version running locally that dykes out the PID stuff from the report. It also displays the header line above the diff output for a bit of context. If it works ok over the next few days I'll commit it. I've attached the patch FYI. > -giorgos -- Brian http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! Index: security =================================================================== RCS file: /home/ncvs/src/etc/security,v retrieving revision 1.55 diff -u -r1.55 security --- security 4 Jul 2001 12:49:17 -0000 1.55 +++ security 17 Sep 2001 00:37:01 -0000 @@ -128,6 +128,31 @@ tee /dev/stderr | wc -l) [ $n -gt 0 -a $rc -lt 1 ] && rc=1 +# Show changes in listening tcp and udp ports: +# +sockstat -l46 | { + read line + echo "${line}" + sed -e /^USER/d -e /comsat/d -e '/^[ ]*$/d' | sort +5 +} | sed -e 's/[ ][ ]*$//' -e 's/\(..................\)...../\1/' >${TMP} + +if [ ! -f ${LOG}/sockstat.today ]; then + [ ${rc} -lt 1 ] && rc=1 + separator + echo "${host} changes in listening ports:" + diff -b /dev/null ${TMP} + touch ${LOG}/sockstat.yesterday || rc=3 + mv ${TMP} ${LOG}/sockstat.today || rc=3 +elif ! cmp ${LOG}/sockstat.today ${TMP} >/dev/null 2>&1; then + [ ${rc} -lt 1 ] && rc=1 + separator + echo "${host} changes in listening ports:" + sed '1{ s/^/ /; q; }' ${TMP} + diff -b ${LOG}/sockstat.today ${TMP} + mv ${LOG}/sockstat.today ${LOG}/sockstat.yesterday || rc=3 + mv ${TMP} ${LOG}/sockstat.today || rc=3 +fi + # Show denied packets # if ipfw -a l 2>/dev/null | egrep "deny|reset|unreach" > ${TMP}; then To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 4:32:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shaft.techsupport.co.uk (shaft.techsupport.co.uk [212.250.77.214]) by hub.freebsd.org (Postfix) with ESMTP id BA60137B40C for ; Mon, 17 Sep 2001 04:32:35 -0700 (PDT) Received: from rasputin by shaft.techsupport.co.uk with local (Exim 3.22 #1) id 15iwhO-000ASV-00 for hackers@freebsd.org; Mon, 17 Sep 2001 12:36:26 +0100 Date: Mon, 17 Sep 2001 12:36:26 +0100 From: Rasputin To: hackers@freebsd.org Subject: Re: 802.11 with best Apple compatibility? Message-ID: <20010917123625.A40193@shaft.techsupport.co.uk> Reply-To: Rasputin Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Terry Lambert [010917 10:00]: > Rasputin wrote: > > Thnaks a lot for the confirmation - for the record, I'm trying > > to replace a basestation, not communicate with one. > > The timing for access points requires different firmware; you > can't do it in software alone. > > Talk to Julian Elisher; he presented on a company that sells > a FreeBSD driver with firmware (binary only for the whole > thing) that can make a FreeBSD box into an access point, > using specific hardware. Cheers Terry, I'm really only after a wireless gateway (don't need all the other bells and whistles of a basestation) so I'll just set it up in ad-hoc mode and set it as default route, I think. -- Arbitrary systems, pl.n.: Systems about which nothing general can be said, save "nothing general can be said." Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 4:44:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 07CC437B407 for ; Mon, 17 Sep 2001 04:44:23 -0700 (PDT) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 15iwp2-000OrJ-00 for hackers@FreeBSD.org; Mon, 17 Sep 2001 13:44:20 +0200 From: Sheldon Hearn To: hackers@FreeBSD.org Subject: Recent changes to libdialog are weird Date: Mon, 17 Sep 2001 13:44:20 +0200 Message-ID: <95560.1000727060@axl.seasidesoftware.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi folks, Recently, libdialog's use of tab, space and enter seems to have changed. Now, space and enter mean the same thing. Before, enter was a context-insensitive short-cut to the currently selected dialogue "submit" button. What many folks may not realize is that the new behaviour, while "safer" than what we had before, makes libdialog behave differently from at least Motif, Windows, JavaAWT, JavaSwing. So what we have now is a libdialog that protects the finger-happy, while confounding those who expect "pretty standard behaviour". I reckon if sysinstall needs to be weird, sysinstall should use its own weird version of libdialog and leave the distributed libdialog alone. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 4:51:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by hub.freebsd.org (Postfix) with ESMTP id 270CF37B407 for ; Mon, 17 Sep 2001 04:51:07 -0700 (PDT) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.11.6/8.11.4) id f8HBomX46625; Mon, 17 Sep 2001 13:50:48 +0200 (CEST) (envelope-from stijn) Date: Mon, 17 Sep 2001 13:50:45 +0200 From: Stijn Hoop To: Sheldon Hearn Cc: hackers@freebsd.org Subject: Re: Recent changes to libdialog are weird Message-ID: <20010917135045.B455@pcwin002.win.tue.nl> References: <95560.1000727060@axl.seasidesoftware.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <95560.1000727060@axl.seasidesoftware.co.za>; from sheldonh@starjuice.net on Mon, Sep 17, 2001 at 01:44:20PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 17, 2001 at 01:44:20PM +0200, Sheldon Hearn wrote: > Recently, libdialog's use of tab, space and enter seems to have changed. > Now, space and enter mean the same thing. Before, enter was a > context-insensitive short-cut to the currently selected dialogue > "submit" button. Yes, and for the better; see below: > What many folks may not realize is that the new behaviour, while "safer" > than what we had before, makes libdialog behave differently from at > least Motif, Windows, JavaAWT, JavaSwing. Eh, no. While it's true that pressing in a dialog box is commonly recognized as meaning 'use the default button', that's only used if the default button is clearly focused, and when not selecting things in a subframe - in other words, not always. What was wrong in libdialog (and which I and others have been complaining about for a long time) is that while selecting items from lists in subframes you still selected the default button instead of crossing the item in the list. Ditto in other places, where people expected to select the current item. I can't count the number of times I had to restart selecting things anymore. It isn't just sysinstall either - ports/www/mod_php4, which has a nice interactive menu, also uses dialog(1) which had the same behaviour. I'd like to see the person that intuitively pressed 'space' instead of 'enter' to select an option in that menu. > So what we have now is a libdialog that protects the finger-happy, while > confounding those who expect "pretty standard behaviour". IMHO, you just got used to it. Present the interface to a Windows user who hasn't seen it before and watch them getting frustrated the third time sysinstall asks 'Proceed?' while they tried to select the disk they would be installing on... > I reckon if sysinstall needs to be weird, sysinstall should use its own > weird version of libdialog and leave the distributed libdialog alone. No - I vote to keep the current code. It's made my life easier already. --Stijn -- ] Nothing safer than a 'cat /dev/wallet | grep $price > real-person; \ ] mv $thing-to-buy $my-case I'd prefer 'mv $thing-to-buy $my-case && cat /dev/wallet | \ grep $price > real-person -- Anonymous, freebsd-questions@freebsd.org, in message <200108020628.IAA11775@hugo10.ka.punkt.de> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 5: 0:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 15DC137B410 for ; Mon, 17 Sep 2001 05:00:20 -0700 (PDT) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 15ix4H-000OwF-00; Mon, 17 Sep 2001 14:00:05 +0200 From: Sheldon Hearn To: Stijn Hoop Cc: hackers@freebsd.org Subject: Re: Recent changes to libdialog are weird In-reply-to: Your message of "Mon, 17 Sep 2001 13:50:45 +0200." <20010917135045.B455@pcwin002.win.tue.nl> Date: Mon, 17 Sep 2001 14:00:05 +0200 Message-ID: <95866.1000728005@axl.seasidesoftware.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 17 Sep 2001 13:50:45 +0200, Stijn Hoop wrote: > IMHO, you just got used to it. Present the interface to a Windows user > who hasn't seen it before and watch them getting frustrated the third > time sysinstall asks 'Proceed?' while they tried to select the disk they > would be installing on... Fine, as long as that assumption has been TESTED with "standard non-power Windows users", i.e. the masses. Since I come from a Windows background, and since I avoided using a mouse like the plague, I figured I was well-qualified to comment. I realize now that I may not have a very representative view of what sensible dialogue behaviour is, given your comments above. So long as you're not just saying that, and someone's actually proven it to be true by taking a reasonably sized sample. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 5:11:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by hub.freebsd.org (Postfix) with ESMTP id D299A37B40F for ; Mon, 17 Sep 2001 05:11:18 -0700 (PDT) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.11.6/8.11.4) id f8HCB8646735; Mon, 17 Sep 2001 14:11:08 +0200 (CEST) (envelope-from stijn) Date: Mon, 17 Sep 2001 14:11:08 +0200 From: Stijn Hoop To: Sheldon Hearn Cc: hackers@freebsd.org Subject: Re: Recent changes to libdialog are weird Message-ID: <20010917141108.C455@pcwin002.win.tue.nl> References: <20010917135045.B455@pcwin002.win.tue.nl> <95866.1000728005@axl.seasidesoftware.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <95866.1000728005@axl.seasidesoftware.co.za>; from sheldonh@starjuice.net on Mon, Sep 17, 2001 at 02:00:05PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 17, 2001 at 02:00:05PM +0200, Sheldon Hearn wrote: > On Mon, 17 Sep 2001 13:50:45 +0200, Stijn Hoop wrote: > > IMHO, you just got used to it. Present the interface to a Windows user > > who hasn't seen it before and watch them getting frustrated the third > > time sysinstall asks 'Proceed?' while they tried to select the disk they > > would be installing on... > > Fine, as long as that assumption has been TESTED with "standard > non-power Windows users", i.e. the masses. Yes, that would be a good idea. > Since I come from a Windows background, and since I avoided using a > mouse like the plague, I figured I was well-qualified to comment. I think everyone is qualified - user interface isn't about qualification, it just needs to be non-intrusive and easily accessible for everyone. [1] I don't know if my opinion is shared by the majority - it just seems so to me, given that I've heard a lot of friends of mine, windowsy people who were trying to install FreeBSD, complaining about this behaviour of the space/enter combo. > I realize now that I may not have a very representative view of what > sensible dialogue behaviour is, given your comments above. So long as > you're not just saying that, and someone's actually proven it to be > true by taking a reasonably sized sample. Agreed. Maybe me and my friends are just weird :) Problem is, how do we take a sample? --Stijn [1] Yes this is an ideal which probably can't be achieved - but we can try to make things better, can't we? :) -- The right half of the brain controls the left half of the body. This means that only left handed people are in their right mind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 5:12:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by hub.freebsd.org (Postfix) with SMTP id A8BAE37B413 for ; Mon, 17 Sep 2001 05:12:32 -0700 (PDT) Received: (qmail 27158 invoked from network); 17 Sep 2001 12:11:35 -0000 Received: from unknown (HELO digitaldaemon.com) (192.168.0.73) by digitaldaemon.com with SMTP; 17 Sep 2001 12:11:35 -0000 Message-ID: <3BA5E799.4040308@digitaldaemon.com> Date: Mon, 17 Sep 2001 08:07:53 -0400 From: Jan Knepper User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: FreeBSD ISP , FreeBSD Questions , FreeBSD Hackers , FreeBSD Announce , ezmlm Subject: AWO!!!! (America Will Overcome!!!!) Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I found the following in one of my many mailboxes this morning. I thought it was great and really wanted to share it with everyone! Please, check out http://www.mp3.com/justjouett and play the song "Made In America" It certainly made my day! Thanks! Jan PS: What is stronger/better: AWO (America Will Overcome) ASO (America Shall Overcome) Better idea's?! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 5:39:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from diogenis.ceid.upatras.gr (diogenis.ceid.upatras.gr [150.140.141.181]) by hub.freebsd.org (Postfix) with SMTP id A597B37B405 for ; Mon, 17 Sep 2001 05:39:08 -0700 (PDT) Received: (qmail 4023 invoked from network); 17 Sep 2001 12:38:02 -0000 Received: from pc-e8.cc.ceid.upatras.gr (HELO pce8) (150.140.140.168) by diogenis.ceid.upatras.gr with SMTP; 17 Sep 2001 12:38:02 -0000 Message-ID: <004201c13f73$6db9b300$a88c8c96@cc.ceid.upatras.gr> From: "Giorgos Keramidas" To: "Brian Somers" Cc: "Brian Somers" , References: <200109171129.f8HBTAR28246@hak.lan.Awfulhak.org> Subject: Re: Checking changes to listening ports in /etc/security Date: Mon, 17 Sep 2001 15:22:33 +0300 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 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Brian Somers" Sent: Monday, September 17, 2001 2:29 PM Subject: Re: Checking changes to listening ports in /etc/security > I found a problem... if you reboot a machine, lots of diffs come up > because of the PID column. I've got a version running locally that > dykes out the PID stuff from the report. It also displays the header > line above the diff output for a bit of context. If it works ok over > the next few days I'll commit it. Damn, I knew that being stable would prove bad in a way or another :-) Thanks for testing this very thoroughly Brian, --giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 6:42:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.infowest.com (ns1.infowest.com [204.17.177.10]) by hub.freebsd.org (Postfix) with ESMTP id D7D0037B40C for ; Mon, 17 Sep 2001 06:42:45 -0700 (PDT) Received: from beware.dragonknight.net (unknown [208.186.107.192]) by ns1.infowest.com (Postfix) with SMTP id E5CB521202; Mon, 17 Sep 2001 07:42:39 -0600 (MDT) Content-Type: text/plain; charset="iso-8859-1" From: Samuel Greear To: Sheldon Hearn , hackers@FreeBSD.org Subject: Re: Recent changes to libdialog are weird Date: Mon, 17 Sep 2001 07:42:24 -0600 X-Mailer: KMail [version 1.2] References: <95560.100 In-Reply-To: <95560.100 MIME-Version: 1.0 Message-Id: <01091707422403.00758@beware.dragonknight.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday 17 September 2001 05:44 am, Sheldon Hearn wrote: > > > Hi folks, > > Recently, libdialog's use of tab, space and enter seems to have changed. > Now, space and enter mean the same thing. Before, enter was a > context-insensitive short-cut to the currently selected dialogue > "submit" button. > > What many folks may not realize is that the new behaviour, while "safer" > than what we had before, makes libdialog behave differently from at > least Motif, Windows, JavaAWT, JavaSwing. > > So what we have now is a libdialog that protects the finger-happy, while > confounding those who expect "pretty standard behaviour". > > I reckon if sysinstall needs to be weird, sysinstall should use its own > weird version of libdialog and leave the distributed libdialog alone. > > Ciao, > Sheldon. The new changes suck, they've been annoying the hell out of me. The first time I installed, as a Windows user, I found that everything worked as I expected. At one point you just jumped into the menu, ran through it selecting things, and hit enter. It was cheeze, I liked it. It seems FUBAR now. -- Samuel J. Greear Developer - GetMegabits, Inc. http://www.itmom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 7: 7:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [129.83.20.90]) by hub.freebsd.org (Postfix) with ESMTP id 3B79037B40A for ; Mon, 17 Sep 2001 07:07:28 -0700 (PDT) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id f8HE6Wc02334; Mon, 17 Sep 2001 10:06:33 -0400 (EDT) Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31]) by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id f8HE6Uf16936; Mon, 17 Sep 2001 10:06:30 -0400 (EDT) Received: from dhcp-105-164.mitre.org (128.29.105.164) by mailhub1.mitre.org with SMTP id 7630342; Mon, 17 Sep 2001 10:05:35 -0400 Message-ID: <3BA60363.747A3582@mitre.org> Date: Mon, 17 Sep 2001 10:06:27 -0400 From: Jason Andresen Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Samuel Greear Cc: Sheldon Hearn , hackers@freebsd.org Subject: Re: Recent changes to libdialog are weird References: <95560.100 <01091707422403.00758@beware.dragonknight.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Samuel Greear wrote: > > The new changes suck, they've been annoying the hell out of me. > The first time I installed, as a Windows user, I found that everything > worked as I expected. At one point you just jumped into the menu, > ran through it selecting things, and hit enter. It was cheeze, I liked > it. It seems FUBAR now. You were definatly in the minority with this one. The first time I ran the installer I kept hitting enter to select the items (I'd used enter for everything else, so I didn't see why it would change), which jumped me to some other screen with no obvious way to return. In fact this changing between spacebar and enter was the number one complaint I heard from my friends who tried out FreeBSD (at least during the install stage). It's just unnatural to people used to mouse environments, it's like making people right click on checkboxes to select them and immediatly jumping to some other dialog if they left click on the checkbox. -- \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org |\/ | | | / _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 7:18: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id E9D3E37B409 for ; Mon, 17 Sep 2001 07:17:55 -0700 (PDT) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 15izDG-000PZI-00; Mon, 17 Sep 2001 16:17:30 +0200 From: Sheldon Hearn To: Jason Andresen Cc: Samuel Greear , hackers@freebsd.org Subject: Re: Recent changes to libdialog are weird In-reply-to: Your message of "Mon, 17 Sep 2001 10:06:27 -0400." <3BA60363.747A3582@mitre.org> Date: Mon, 17 Sep 2001 16:17:30 +0200 Message-ID: <98287.1000736250@axl.seasidesoftware.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 17 Sep 2001 10:06:27 -0400, Jason Andresen wrote: > You were definatly in the minority with this one. Guys, guys, please! So far, NOBODY has come forward with evidence of a serious survey. If you can't present new evidence of such a survey conducted, you're unlikely to change anything with your post. Can we try to avoid flaming and personal opinions and try to stick to serious research? If no serious research has been conducted, fine. In that case, I'd like to know what motivation the libdialog behaviour changes were based on. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 7:45:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 951B437B401 for ; Mon, 17 Sep 2001 07:45:39 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f8HEjYa00550; Mon, 17 Sep 2001 07:45:34 -0700 Date: Mon, 17 Sep 2001 07:45:34 -0700 From: Brooks Davis To: Rasputin Cc: hackers@FreeBSD.ORG Subject: Re: 802.11 with best Apple compatibility? Message-ID: <20010917074534.B28199@Odin.AC.HMC.Edu> References: <20010914150203.A30720@shaft.techsupport.co.uk> <20010914103037.A5619@ussenterprise.ufp.org> <20010914101548.B7169@Odin.AC.HMC.Edu> <3BA23F2E.23F68B29@mitre.org> <20010917094810.A39701@shaft.techsupport.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="y0ulUmNC+osPPQO6" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010917094810.A39701@shaft.techsupport.co.uk>; from rara.rasputin@virgin.net on Mon, Sep 17, 2001 at 09:48:10AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --y0ulUmNC+osPPQO6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 17, 2001 at 09:48:10AM +0100, Rasputin wrote: > I take it the PCI PCMCIA adapters are still unsupported? > (on 4-STABLE) They should be working. That was one of the primary points of the work Warner has been doing on PC Card. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --y0ulUmNC+osPPQO6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7pgyNXY6L6fI4GtQRAnLgAKClnEErPNflRezFZ05JddWkBfOSJwCgnTPO MZh/fJfNuoXQKHUewfG04x8= =yEp3 -----END PGP SIGNATURE----- --y0ulUmNC+osPPQO6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 8:14:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id D84E837B408 for ; Mon, 17 Sep 2001 08:14:29 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f8HFERu07244; Mon, 17 Sep 2001 09:14:28 -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.11.3/8.11.4) with ESMTP id f8HFERW57023; Mon, 17 Sep 2001 09:14:27 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109171514.f8HFERW57023@harmony.village.org> To: Rasputin Subject: Re: 802.11 with best Apple compatibility? Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Sep 2001 09:48:10 BST." <20010917094810.A39701@shaft.techsupport.co.uk> References: <20010917094810.A39701@shaft.techsupport.co.uk> <20010914150203.A30720@shaft.techsupport.co.uk> <20010914103037.A5619@ussenterprise.ufp.org> <20010914101548.B7169@Odin.AC.HMC.Edu> <3BA23F2E.23F68B29@mitre.org> Date: Mon, 17 Sep 2001 09:14:27 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010917094810.A39701@shaft.techsupport.co.uk> Rasputin writes: : I take it the PCI PCMCIA adapters are still unsupported? : (on 4-STABLE) I did a boatload of changes to -stable to make them work. While I didn't test the PCI cards with the last set of code for the 4.4-RELEASE, they were working fairly well with the RC code. There are some issues with some motherboards and interrupt routing which may bite you, but otherwise it should work. There's also some configuration issues too for some of the older Orinoco boards. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 9:31: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web20003.mail.yahoo.com (web20003.mail.yahoo.com [216.136.225.48]) by hub.freebsd.org (Postfix) with SMTP id 929FA37B403 for ; Mon, 17 Sep 2001 09:30:58 -0700 (PDT) Message-ID: <20010917163056.65463.qmail@web20003.mail.yahoo.com> Received: from [193.123.204.66] by web20003.mail.yahoo.com via HTTP; Mon, 17 Sep 2001 17:30:56 BST Date: Mon, 17 Sep 2001 17:30:56 +0100 (BST) From: =?iso-8859-1?q?Gavin=20Kenny?= Subject: CAN bus To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Is there a CAN bus driver for FreeBSD? please cc me your answer many thanks Gavin ____________________________________________________________ Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 10:28:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by hub.freebsd.org (Postfix) with ESMTP id 0C4E637B408 for ; Mon, 17 Sep 2001 10:28:08 -0700 (PDT) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id TAA24241; Mon, 17 Sep 2001 19:28:06 +0200 (CEST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.4) id f8HHS5400835; Mon, 17 Sep 2001 19:28:05 +0200 (CEST) (envelope-from wkb) Date: Mon, 17 Sep 2001 19:28:05 +0200 From: Wilko Bulte To: Jason Andresen Cc: Samuel Greear , Sheldon Hearn , hackers@FreeBSD.ORG Subject: Re: Recent changes to libdialog are weird Message-ID: <20010917192805.B347@freebie.xs4all.nl> References: <95560.100 <01091707422403.00758@beware.dragonknight.net> <3BA60363.747A3582@mitre.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BA60363.747A3582@mitre.org>; from jandrese@mitre.org on Mon, Sep 17, 2001 at 10:06:27AM -0400 X-OS: FreeBSD 4.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 17, 2001 at 10:06:27AM -0400, Jason Andresen wrote: > Samuel Greear wrote: > > > > > The new changes suck, they've been annoying the hell out of me. > > The first time I installed, as a Windows user, I found that everything > > worked as I expected. At one point you just jumped into the menu, > > ran through it selecting things, and hit enter. It was cheeze, I liked > > it. It seems FUBAR now. > > You were definatly in the minority with this one. The first time I > ran the installer I kept hitting enter to select the items (I'd used > enter for everything else, so I didn't see why it would change), which > jumped me to some other screen with no obvious way to return. > > In fact this changing between spacebar and enter was the number one > complaint I heard from my friends who tried out FreeBSD (at least > during the install stage). It's just unnatural to people used to > mouse environments, it's like making people right click on checkboxes Agreed. FWIW I also have some problems convincing people that Quit or Cancel is really what they want .. -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 10:37:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by hub.freebsd.org (Postfix) with ESMTP id C9CA337B40F for ; Mon, 17 Sep 2001 10:37:29 -0700 (PDT) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id TAA28635; Mon, 17 Sep 2001 19:37:27 +0200 (CEST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.4) id f8HHbRv00946; Mon, 17 Sep 2001 19:37:27 +0200 (CEST) (envelope-from wkb) Date: Mon, 17 Sep 2001 19:37:27 +0200 From: Wilko Bulte To: Rasputin Cc: hackers@FreeBSD.ORG Subject: Re: 802.11 with best Apple compatibility? Message-ID: <20010917193727.G347@freebie.xs4all.nl> References: <20010914150203.A30720@shaft.techsupport.co.uk> <20010914103037.A5619@ussenterprise.ufp.org> <20010914101548.B7169@Odin.AC.HMC.Edu> <3BA23F2E.23F68B29@mitre.org> <20010917094810.A39701@shaft.techsupport.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010917094810.A39701@shaft.techsupport.co.uk>; from rara.rasputin@virgin.net on Mon, Sep 17, 2001 at 09:48:10AM +0100 X-OS: FreeBSD 4.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 17, 2001 at 09:48:10AM +0100, Rasputin wrote: > * Jason Andresen [010914 18:39]: > > Brooks Davis wrote: > > Aren't the airport cards just plain old Silver Lucent cards? If so, > > then > > either the Gold or the Silver should work fine. > > In fact I know the silver works fine because I have an Airport at home > > that > > I talk to with a Silver card. There's a FreeBSD port that lets you > > configure the box from your machine. In Windowsland there's a program > > called FreeBase, and of course the Airport comes with Mac tools bundled. > > Thnaks a lot for the confirmation - for the record, I'm trying > to replace a basestation, not communicate with one. > > But as long as Lucents are compatible, I 'll go for one of those.. > (I only need WEP while I get a crash course in IPSec :) ) > > I take it the PCI PCMCIA adapters are still unsupported? > (on 4-STABLE) In a generic sense, or with Wlan cards? I have one here in a -stable box that appears to work for a PCMCIA modem card. I don't have a FreeBSD-supported wlan card to test with. W/ -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 11:53:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [129.83.20.90]) by hub.freebsd.org (Postfix) with ESMTP id 4F3B937B407 for ; Mon, 17 Sep 2001 11:53:21 -0700 (PDT) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id f8HIqec00428; Mon, 17 Sep 2001 14:52:40 -0400 (EDT) Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31]) by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id f8HIqaf13135; Mon, 17 Sep 2001 14:52:36 -0400 (EDT) Received: from dhcp-105-164.mitre.org (128.29.105.164) by mailhub1.mitre.org with SMTP id 7633574; Mon, 17 Sep 2001 13:43:01 -0400 Message-ID: <3BA6365A.B4827CA@mitre.org> Date: Mon, 17 Sep 2001 13:43:54 -0400 From: Jason Andresen Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Wilko Bulte Cc: Rasputin , hackers@freebsd.org Subject: Re: 802.11 with best Apple compatibility? References: <20010914150203.A30720@shaft.techsupport.co.uk> <20010914103037.A5619@ussenterprise.ufp.org> <20010914101548.B7169@Odin.AC.HMC.Edu> <3BA23F2E.23F68B29@mitre.org> <20010917094810.A39701@shaft.techsupport.co.uk> <20010917193727.G347@freebie.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > On Mon, Sep 17, 2001 at 09:48:10AM +0100, Rasputin wrote: > > Thnaks a lot for the confirmation - for the record, I'm trying > > to replace a basestation, not communicate with one. > > > > But as long as Lucents are compatible, I 'll go for one of those.. > > (I only need WEP while I get a crash course in IPSec :) ) > > > > I take it the PCI PCMCIA adapters are still unsupported? > > (on 4-STABLE) > > In a generic sense, or with Wlan cards? I have one here in a -stable > box that appears to work for a PCMCIA modem card. I don't have a > FreeBSD-supported wlan card to test with. I think they're going to be unsupported until the CardBus stuff MFCs (or until 5.x is -STABLE). -- \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org |\/ | | | / _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 11:56:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by hub.freebsd.org (Postfix) with ESMTP id 5D75337B412 for ; Mon, 17 Sep 2001 11:56:51 -0700 (PDT) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA22199; Mon, 17 Sep 2001 20:56:49 +0200 (CEST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.4) id f8HIum001548; Mon, 17 Sep 2001 20:56:48 +0200 (CEST) (envelope-from wkb) Date: Mon, 17 Sep 2001 20:56:48 +0200 From: Wilko Bulte To: Jason Andresen Cc: Rasputin , hackers@freebsd.org Subject: Re: 802.11 with best Apple compatibility? Message-ID: <20010917205648.C1402@freebie.xs4all.nl> References: <20010914150203.A30720@shaft.techsupport.co.uk> <20010914103037.A5619@ussenterprise.ufp.org> <20010914101548.B7169@Odin.AC.HMC.Edu> <3BA23F2E.23F68B29@mitre.org> <20010917094810.A39701@shaft.techsupport.co.uk> <20010917193727.G347@freebie.xs4all.nl> <3BA6365A.B4827CA@mitre.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BA6365A.B4827CA@mitre.org>; from jandrese@mitre.org on Mon, Sep 17, 2001 at 01:43:54PM -0400 X-OS: FreeBSD 4.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 17, 2001 at 01:43:54PM -0400, Jason Andresen wrote: > Wilko Bulte wrote: > > > > On Mon, Sep 17, 2001 at 09:48:10AM +0100, Rasputin wrote: > > > Thnaks a lot for the confirmation - for the record, I'm trying > > > to replace a basestation, not communicate with one. > > > > > > But as long as Lucents are compatible, I 'll go for one of those.. > > > (I only need WEP while I get a crash course in IPSec :) ) > > > > > > I take it the PCI PCMCIA adapters are still unsupported? > > > (on 4-STABLE) > > > > In a generic sense, or with Wlan cards? I have one here in a -stable > > box that appears to work for a PCMCIA modem card. I don't have a > > FreeBSD-supported wlan card to test with. > > I think they're going to be unsupported until the CardBus stuff MFCs > (or until 5.x is -STABLE). Well... mine works. 5-stable is over a year away, I do expect things to end in 4-stable at some point. But I could be wrong of course. -- | / o / / _ email: wilko@FreeBSD.org |/|/ / / /< (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 13:21:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 754D937B405 for ; Mon, 17 Sep 2001 13:21:11 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f8HKL9u08073; Mon, 17 Sep 2001 14:21:09 -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.11.3/8.11.4) with ESMTP id f8HKL9W58885; Mon, 17 Sep 2001 14:21:09 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109172021.f8HKL9W58885@harmony.village.org> To: Jason Andresen Subject: Re: 802.11 with best Apple compatibility? Cc: Wilko Bulte , Rasputin , hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Sep 2001 13:43:54 EDT." <3BA6365A.B4827CA@mitre.org> References: <3BA6365A.B4827CA@mitre.org> <20010914150203.A30720@shaft.techsupport.co.uk> <20010914103037.A5619@ussenterprise.ufp.org> <20010914101548.B7169@Odin.AC.HMC.Edu> <3BA23F2E.23F68B29@mitre.org> <20010917094810.A39701@shaft.techsupport.co.uk> <20010917193727.G347@freebie.xs4all.nl> Date: Mon, 17 Sep 2001 14:21:09 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3BA6365A.B4827CA@mitre.org> Jason Andresen writes: : Wilko Bulte wrote: : > : > On Mon, Sep 17, 2001 at 09:48:10AM +0100, Rasputin wrote: : > > Thnaks a lot for the confirmation - for the record, I'm trying : > > to replace a basestation, not communicate with one. : > > : > > But as long as Lucents are compatible, I 'll go for one of those.. : > > (I only need WEP while I get a crash course in IPSec :) ) : > > : > > I take it the PCI PCMCIA adapters are still unsupported? : > > (on 4-STABLE) : > : > In a generic sense, or with Wlan cards? I have one here in a -stable : > box that appears to work for a PCMCIA modem card. I don't have a : > FreeBSD-supported wlan card to test with. : : I think they're going to be unsupported until the CardBus stuff MFCs : (or until 5.x is -STABLE). No. 4.4 supports them. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 13:32: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 1069937B408 for ; Mon, 17 Sep 2001 13:32:07 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f8HKW6M41638; Mon, 17 Sep 2001 13:32:06 -0700 (PDT) (envelope-from dillon) Date: Mon, 17 Sep 2001 13:32:06 -0700 (PDT) From: Matt Dillon Message-Id: <200109172032.f8HKW6M41638@earth.backplane.com> To: hackers@FreeBSD.org Subject: bug in sshd - signal during free() Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG sshd died on one of our machines today. The traceback seems to indicate that a signal is interrupting a free(). I'm going to play with the code a bit to see if there's an easy fix. This bug can't occur very often... the key regeneration signal has to occur *just* as sshd is trying to free() something. -Matt (gdb) back #0 0x28231e34 in kill () from /usr/lib/libc.so.4 #1 0x2826dd8a in abort () from /usr/lib/libc.so.4 #2 0x2826c899 in isatty () from /usr/lib/libc.so.4 #3 0x2826c8cf in isatty () from /usr/lib/libc.so.4 #4 0x2826d907 in malloc () from /usr/lib/libc.so.4 #5 0x2826be58 in __smakebuf () from /usr/lib/libc.so.4 #6 0x2826bdec in __swsetup () from /usr/lib/libc.so.4 #7 0x282663ef in vfprintf () from /usr/lib/libc.so.4 #8 0x28266059 in fprintf () from /usr/lib/libc.so.4 #9 0x2824e0ed in vsyslog () from /usr/lib/libc.so.4 #10 0x2824e009 in syslog () from /usr/lib/libc.so.4 #11 0x804feb3 in do_log () #12 0x806ade3 in log () #13 0x804c742 in key_regeneration_alarm () #14 0xbfbfffac in ?? () #15 0x2826da35 in free () from /usr/lib/libc.so.4 #16 0x805f087 in xfree () #17 0x804d8be in main () #18 0x804c50d in _start () (gdb) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 13:49:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 80E0D37B40E for ; Mon, 17 Sep 2001 13:49:25 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f8HKnPj41790; Mon, 17 Sep 2001 13:49:25 -0700 (PDT) (envelope-from dillon) Date: Mon, 17 Sep 2001 13:49:25 -0700 (PDT) From: Matt Dillon Message-Id: <200109172049.f8HKnPj41790@earth.backplane.com> To: hackers@FreeBSD.org Subject: Proposed patch (was Re: bug in sshd - signal during free()) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I looked at the code and there is definitely a serious issue. This proposed patch should solve the problem. Here it is for review before I commit it and send a bug report off to the openssh folks. I am testing it now. -Matt Index: sshd.c =================================================================== RCS file: /home/ncvs/src/crypto/openssh/sshd.c,v retrieving revision 1.6.2.7 diff -u -r1.6.2.7 sshd.c --- sshd.c 2001/03/04 15:13:08 1.6.2.7 +++ sshd.c 2001/09/17 20:45:54 @@ -134,6 +134,11 @@ char *server_version_string = NULL; /* + * Indicates that a key-regeneration alarm occured. + */ +int received_regeneration; + +/* * Any really sensitive data in the application is contained in this * structure. The idea is that this structure could be locked into memory so * that the pages do not get written into swap. However, there are some @@ -260,19 +265,26 @@ fatal("Timeout before authentication for %s.", get_remote_ipaddr()); } -/* - * Signal handler for the key regeneration alarm. Note that this - * alarm only occurs in the daemon waiting for connections, and it does not - * do anything with the private key or random state before forking. - * Thus there should be no concurrency control/asynchronous execution - * problems. - */ -/* XXX do we really want this work to be done in a signal handler ? -m */ void key_regeneration_alarm(int sig) { - int save_errno = errno; + received_regeneration = 1; + /* Reschedule the alarm. */ + signal(SIGALRM, key_regeneration_alarm); + alarm(options.key_regeneration_time); +} +/* + * Regenerate the keys. Note that this alarm only occurs in the daemon + * waiting for connections, and it does not do anything with the + * private key or random state before forking. However, it calls routines + * which may malloc() so we do not call this routine directly from the + * signal handler. + */ +void +key_regeneration(void) +{ + received_regeneration = 0; /* Check if we should generate a new key. */ if (key_used) { /* This should really be done in the background. */ @@ -292,10 +304,6 @@ key_used = 0; log("RSA key generation complete."); } - /* Reschedule the alarm. */ - signal(SIGALRM, key_regeneration_alarm); - alarm(options.key_regeneration_time); - errno = save_errno; } void @@ -854,6 +862,8 @@ for (;;) { if (received_sighup) sighup_restart(); + if (received_regeneration) + key_regeneration(); if (fdset != NULL) xfree(fdset); fdsetsz = howmany(maxfd, NFDBITS) * sizeof(fd_mask); @@ -994,6 +1004,8 @@ */ alarm(0); signal(SIGALRM, SIG_DFL); + received_regeneration = 0; + signal(SIGHUP, SIG_DFL); signal(SIGTERM, SIG_DFL); signal(SIGQUIT, SIG_DFL); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 13:57:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180]) by hub.freebsd.org (Postfix) with ESMTP id 5718937B413 for ; Mon, 17 Sep 2001 13:57:33 -0700 (PDT) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f8HKvXM92760 for ; Mon, 17 Sep 2001 13:57:33 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 084EB3808; Mon, 17 Sep 2001 13:57:33 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Matt Dillon Cc: hackers@FreeBSD.ORG Subject: Re: Proposed patch (was Re: bug in sshd - signal during free()) In-Reply-To: <200109172049.f8HKnPj41790@earth.backplane.com> Date: Mon, 17 Sep 2001 13:57:33 -0700 From: Peter Wemm Message-Id: <20010917205733.084EB3808@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matt Dillon wrote: > I looked at the code and there is definitely a serious issue. This > proposed patch should solve the problem. Here it is for review before > I commit it and send a bug report off to the openssh folks. I am testing > it now. If it is going into the vendor release, then commit it on the vendor branch. Preferably using the code that they actually commit. Dont diverge from the baseline, and then cause additional complications for the next import when it collides with the official fix. Secondly, this area of the tree is maintained by Brian Feldman. Be sure to coordinate this with him. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 14: 1:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 500E737B40C for ; Mon, 17 Sep 2001 14:01:08 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 38B3281D01; Mon, 17 Sep 2001 16:01:03 -0500 (CDT) Date: Mon, 17 Sep 2001 16:01:03 -0500 From: Alfred Perlstein To: Matt Dillon Cc: hackers@FreeBSD.org Subject: Re: bug in sshd - signal during free() Message-ID: <20010917160103.Z968@elvis.mu.org> References: <200109172032.f8HKW6M41638@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109172032.f8HKW6M41638@earth.backplane.com>; from dillon@earth.backplane.com on Mon, Sep 17, 2001 at 01:32:06PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Matt Dillon [010917 15:32] wrote: > sshd died on one of our machines today. The traceback seems to > indicate that a signal is interrupting a free(). I'm going to > play with the code a bit to see if there's an easy fix. > > This bug can't occur very often... the key regeneration signal > has to occur *just* as sshd is trying to free() something. The bug seems more likely to be caused by use of unsafe functions in a signal handler. I'm really suprised that the OpenSSH team didn't slap whomever decided to do so much processing within a signal handler silly. > > -Matt > > (gdb) back > #0 0x28231e34 in kill () from /usr/lib/libc.so.4 > #1 0x2826dd8a in abort () from /usr/lib/libc.so.4 > #2 0x2826c899 in isatty () from /usr/lib/libc.so.4 > #3 0x2826c8cf in isatty () from /usr/lib/libc.so.4 > #4 0x2826d907 in malloc () from /usr/lib/libc.so.4 > #5 0x2826be58 in __smakebuf () from /usr/lib/libc.so.4 > #6 0x2826bdec in __swsetup () from /usr/lib/libc.so.4 > #7 0x282663ef in vfprintf () from /usr/lib/libc.so.4 > #8 0x28266059 in fprintf () from /usr/lib/libc.so.4 > #9 0x2824e0ed in vsyslog () from /usr/lib/libc.so.4 > #10 0x2824e009 in syslog () from /usr/lib/libc.so.4 > #11 0x804feb3 in do_log () > #12 0x806ade3 in log () > #13 0x804c742 in key_regeneration_alarm () > #14 0xbfbfffac in ?? () > #15 0x2826da35 in free () from /usr/lib/libc.so.4 > #16 0x805f087 in xfree () > #17 0x804d8be in main () > #18 0x804c50d in _start () > (gdb) -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 14: 4:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 8944037B409 for ; Mon, 17 Sep 2001 14:04:06 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f8HL45641959; Mon, 17 Sep 2001 14:04:05 -0700 (PDT) (envelope-from dillon) Date: Mon, 17 Sep 2001 14:04:05 -0700 (PDT) From: Matt Dillon Message-Id: <200109172104.f8HL45641959@earth.backplane.com> To: Alfred Perlstein Cc: hackers@FreeBSD.org Subject: Re: bug in sshd - signal during free() References: <200109172032.f8HKW6M41638@earth.backplane.com> <20010917160103.Z968@elvis.mu.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :* Matt Dillon [010917 15:32] wrote: :> sshd died on one of our machines today. The traceback seems to :> indicate that a signal is interrupting a free(). I'm going to :> play with the code a bit to see if there's an easy fix. :> :> This bug can't occur very often... the key regeneration signal :> has to occur *just* as sshd is trying to free() something. : :The bug seems more likely to be caused by use of unsafe functions :in a signal handler. : :I'm really suprised that the OpenSSH team didn't slap whomever decided :to do so much processing within a signal handler silly. It's funny... they had an XXX comment in there so obviously someone was a little jittery about it. I think they just didn't realize that a malloc() might occur inside the signal handler or they would have fixed it long ago. UNIX signals suck. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 14:15:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 5B23F37B407 for ; Mon, 17 Sep 2001 14:15:40 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 2358481D09; Mon, 17 Sep 2001 16:15:40 -0500 (CDT) Date: Mon, 17 Sep 2001 16:15:40 -0500 From: Alfred Perlstein To: Matt Dillon Cc: hackers@FreeBSD.org Subject: Re: bug in sshd - signal during free() Message-ID: <20010917161540.A968@elvis.mu.org> References: <200109172032.f8HKW6M41638@earth.backplane.com> <20010917160103.Z968@elvis.mu.org> <200109172104.f8HL45641959@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109172104.f8HL45641959@earth.backplane.com>; from dillon@earth.backplane.com on Mon, Sep 17, 2001 at 02:04:05PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Matt Dillon [010917 16:04] wrote: > > : > :* Matt Dillon [010917 15:32] wrote: > :> sshd died on one of our machines today. The traceback seems to > :> indicate that a signal is interrupting a free(). I'm going to > :> play with the code a bit to see if there's an easy fix. > :> > :> This bug can't occur very often... the key regeneration signal > :> has to occur *just* as sshd is trying to free() something. > : > :The bug seems more likely to be caused by use of unsafe functions > :in a signal handler. > : > :I'm really suprised that the OpenSSH team didn't slap whomever decided > :to do so much processing within a signal handler silly. > > It's funny... they had an XXX comment in there so obviously someone > was a little jittery about it. I think they just didn't realize that > a malloc() might occur inside the signal handler or they would have > fixed it long ago. > > UNIX signals suck. Any async notification would require the same amount of care. Most programmers suck. :) -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 14:24: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id B398F37B406 for ; Mon, 17 Sep 2001 14:24:01 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f8HLO1T42166; Mon, 17 Sep 2001 14:24:01 -0700 (PDT) (envelope-from dillon) Date: Mon, 17 Sep 2001 14:24:01 -0700 (PDT) From: Matt Dillon Message-Id: <200109172124.f8HLO1T42166@earth.backplane.com> To: Peter Wemm Cc: hackers@FreeBSD.ORG Subject: Re: Proposed patch (was Re: bug in sshd - signal during free()) References: <20010917205733.084EB3808@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I forwarded the whole thing to Brian. We'll wait to see what he decides to do. Obviously a fix like this needs to go, it's just a matter of who, how, and when. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 14:40:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta1-rme.xtra.co.nz (mta1-rme.xtra.co.nz [203.96.92.1]) by hub.freebsd.org (Postfix) with ESMTP id 2A1CE37B40A for ; Mon, 17 Sep 2001 14:40:08 -0700 (PDT) Received: from development.wgtn.csg.co.nz ([210.86.1.68]) by mta1-rme.xtra.co.nz with SMTP id <20010917214006.IVFW2579036.mta1-rme.xtra.co.nz@development.wgtn.csg.co.nz> for ; Tue, 18 Sep 2001 09:40:06 +1200 Content-Type: text/plain; charset="iso-8859-1" From: David Preece Reply-To: davep@afterswish.com To: freebsd-hackers@freebsd.org Subject: Fwd: MTU table? Date: Tue, 18 Sep 2001 09:40:22 +1200 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01091809402216.83234@development.wgtn.csg.co.nz> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I tried this on -questions but to no avail. It strikes me as something that is either dead easy, or can't be done. Does anyone have any ideas? Thanks, Dave ---------- Forwarded Message ---------- Subject: MTU table? Date: Mon, 17 Sep 2001 17:40:35 +1200 From: David Preece To: freebsd-questions@freebsd.org Hi, I have a network consisting of: Server (mtu1500)<->(mtu1500)gateway(mtu576)<->Client (mtu1500) The server and gateway are both FreeBSD4.x machines and the client is NT4, hence changing MTU is a bit of a mystery, but I digress. So, the first time the client connects to the server and the server attempts to send back a packet of over 576 bytes, the gateway objects and sends back an ICMP 3(4) saying that the packet can't be forwarded until the MTU is reduced to 576. The server tries again with the new MTU and all is well. The kernel on the server also has the good sense to remember that there's an MTU of 576 bytes on that route and doesn't try anything larger in future. This would be great *except* that I'm trying to turn the whole thing into a factory for ICMP cannot fragment messages. Is there a simple way to flush the route->mtu table on the server? Thanks, Dave ------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 14:47:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id B86F737B40B for ; Mon, 17 Sep 2001 14:47:55 -0700 (PDT) Received: (from dan@localhost) by dan.emsphone.com (8.11.4/8.11.4) id f8HLlrI06320; Mon, 17 Sep 2001 16:47:53 -0500 (CDT) (envelope-from dan) Date: Mon, 17 Sep 2001 16:47:42 -0500 From: Dan Nelson To: David Preece Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Fwd: MTU table? Message-ID: <20010917164742.A13516@dan.emsphone.com> References: <01091809402216.83234@development.wgtn.csg.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01091809402216.83234@development.wgtn.csg.co.nz> User-Agent: Mutt/1.3.22.1i X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Sep 18), David Preece said: > I tried this on -questions but to no avail. It strikes me as something that > is either dead easy, or can't be done. Does anyone have any ideas? If "route get " shows an MTU of 576, "route delete " should clear it. > I have a network consisting of: > > Server (mtu1500)<->(mtu1500)gateway(mtu576)<->Client (mtu1500) > > The server and gateway are both FreeBSD4.x machines and the client is > NT4, hence changing MTU is a bit of a mystery, but I digress. So, the > first time the client connects to the server and the server attempts > to send back a packet of over 576 bytes, the gateway objects and > sends back an ICMP 3(4) saying that the packet can't be forwarded > until the MTU is reduced to 576. The server tries again with the new > MTU and all is well. > > The kernel on the server also has the good sense to remember that > there's an MTU of 576 bytes on that route and doesn't try anything > larger in future. This would be great *except* that I'm trying to > turn the whole thing into a factory for ICMP cannot fragment > messages. Is there a simple way to flush the route->mtu table on the > server? -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 14:56: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id C394F37B40E for ; Mon, 17 Sep 2001 14:55:58 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA17630; Mon, 17 Sep 2001 15:31:59 -0700 (PDT) Date: Mon, 17 Sep 2001 15:31:58 -0700 (PDT) From: Julian Elischer To: Matt Dillon Cc: hackers@FreeBSD.org Subject: Re: bug in sshd - signal during free() In-Reply-To: <200109172032.f8HKW6M41638@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG signale interrupying 'free' is ok.. Free is not 'signal-safe' so no malloc/free can be done in a signal.. set the malloc config that catches recursive frees&malocs. On Mon, 17 Sep 2001, Matt Dillon wrote: > sshd died on one of our machines today. The traceback seems to > indicate that a signal is interrupting a free(). I'm going to > play with the code a bit to see if there's an easy fix. > > This bug can't occur very often... the key regeneration signal > has to occur *just* as sshd is trying to free() something. > > -Matt > > (gdb) back > #0 0x28231e34 in kill () from /usr/lib/libc.so.4 > #1 0x2826dd8a in abort () from /usr/lib/libc.so.4 > #2 0x2826c899 in isatty () from /usr/lib/libc.so.4 > #3 0x2826c8cf in isatty () from /usr/lib/libc.so.4 > #4 0x2826d907 in malloc () from /usr/lib/libc.so.4 > #5 0x2826be58 in __smakebuf () from /usr/lib/libc.so.4 > #6 0x2826bdec in __swsetup () from /usr/lib/libc.so.4 > #7 0x282663ef in vfprintf () from /usr/lib/libc.so.4 > #8 0x28266059 in fprintf () from /usr/lib/libc.so.4 > #9 0x2824e0ed in vsyslog () from /usr/lib/libc.so.4 > #10 0x2824e009 in syslog () from /usr/lib/libc.so.4 > #11 0x804feb3 in do_log () > #12 0x806ade3 in log () > #13 0x804c742 in key_regeneration_alarm () > #14 0xbfbfffac in ?? () > #15 0x2826da35 in free () from /usr/lib/libc.so.4 > #16 0x805f087 in xfree () > #17 0x804d8be in main () > #18 0x804c50d in _start () > (gdb) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 14:57:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id 15A4037B410; Mon, 17 Sep 2001 14:56:53 -0700 (PDT) Received: from chojin (chojin.lan.tarakan-network.com [192.168.69.2] (may be forged)) by tarakan-network.com (8.11.6/8.11.3) with SMTP id f8HLuVt78128; Mon, 17 Sep 2001 23:56:31 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <00c501c13fc3$9e9aeb10$0245a8c0@chojin> From: "Chojin" To: "Chojin" , "Joe Clarke" Cc: "Jean-Francois Dive" , , References: <20010912143244.B43876-100000@shumai.marcuscom.com> <017801c13bc1$5bc3a580$0245a8c0@chojin> Subject: Re: Problem with snmpd Date: Mon, 17 Sep 2001 23:55:28 +0200 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_00C2_01C13FD4.3A5B1970" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2526.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2526.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_00C2_01C13FD4.3A5B1970 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit I didn't resolved my problem. Even after upgraded to 4.4-stable (because there was maybe a bug in snmpd :-p). I don't know what I could do. ----- Original Message ----- From: "Chojin" To: "Joe Clarke" Cc: "Jean-Francois Dive" ; ; Sent: Wednesday, September 12, 2001 9:30 PM Subject: Re: Problem with snmpd > I tried your snmpd.conf but with no success :'( > ----- Original Message ----- > From: "Joe Clarke" > To: "Chojin" > Cc: "Jean-Francois Dive" ; ; > > Sent: Wednesday, September 12, 2001 8:34 PM > Subject: Re: Problem with snmpd > > > > Can you send your snmp.conf file? These are the relevant bits of mine: > > > > com2sec local localhost public > > com2sec localrw localhost private > > com2sec mynetwork 172.18.0.0/24 public > > com2sec mynetworkrw 172.18.0.0/24 private > > > > #### > > # Second, map the security names into group names: > > > > # sec.model sec.name > > group LocalRWGroup v1 localrw > > group LocalRWGroup v2c localrw > > group LocalRWGroup usm localrw > > group LocalROGroup v1 local > > group LocalROGroup v2c local > > group LocalROGroup usm local > > group NetROGroup v1 mynetwork > > group NetROGroup v2c mynetwork > > group NetROGroup usm mynetwork > > group NetRWGroup v1 mynetworkrw > > group NetRWGroup v2c mynetworkrw > > group NetRWGroup usm mynetworkrw > > > > #### > > # Third, create a view for us to let the groups have rights to: > > > > # incl/excl subtree mask > > view all included .1 80 > > > > #### > > # Finally, grant the 2 groups access to the 1 view with different > > # write permissions: > > > > # context sec.model sec.level match read write notif > > access LocalROGroup "" any noauth exact all none none > > access LocalRWGroup "" any noauth exact all all none > > access NetROGroup "" any noauth exact all none none > > access NetRWGroup "" any noauth exact all all none > > > > > > public@localhost does work on my machine. > > > > Joe > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > I used TMRTGCHO as community name before, but since I've got this > problem I > > > use now public. > > > Request from localhost or any other interface doesn't work. > > > I cleaned snmpd.log, restarted snmpd: > > > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l > > > /var/log/snmpd.log > > > > > > and a new one is located at http://www.tarakan-network.com/snmpd.log (I > did > > > a snmpwalk and snmpget for public@localhost but no success) > > > > > > ----- Original Message ----- > > > From: "Jean-Francois Dive" > > > To: "Chojin" > > > Sent: Wednesday, September 12, 2001 10:38 AM > > > Subject: Re: Problem with snmpd > > > > > > > > > > Hi (salut) > > > > > > > > In fact, i see some successfull request with the community: > > > > TMRTGCHO and no attemps with the localhost one... seems pretty odd. > did > > > > you only got those requests from localhost not working ? > > > > > > > > Otherwise, purge the log file, be *sure* that no requests are comming > from > > > > somewhere else and resart to see some failures... > > > > > > > > JeF > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > I launched in debug mode > > > > > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l > > > > > /var/log/snmpd.log > > > > > I attached snmpd.log > > > > > There are so many informations I can't detect the problem :pp > > > > > > > > > > ----- Original Message ----- > > > > > From: "Jean-Francois Dive" > > > > > To: "Chojin" > > > > > Cc: ; > > > > > Sent: Wednesday, September 12, 2001 9:53 AM > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > i think it is possible to start the snmpd and not send it to > > > backgroud, > > > > > > and see if it does printout some error messages..Otherwise use the > > > truss > > > > > > command to follow the syscalls made by the daemon while processing > > > your > > > > > > request, this could point you to a problem.. > > > > > > > > > > > > JeF > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > snmpd.log is empty... > > > > > > > > > > > > > > I did #netstat -an | grep 161 > > > > > > > udp4 0 0 *.161 *.* > > > > > > > > > > > > > > port 161 exists then it should work... > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > From: "Jean-Francois Dive" > > > > > > > To: "Chojin" > > > > > > > Cc: ; > > > > > > > > Sent: Wednesday, September 12, 2001 3:21 AM > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > So you have any traces in a log file or something similar ? > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > > > I have a problem with snmpd. > > > > > > > > > > > > > > > > > > In fact, one day, for unknown reason ( I didn't modify any > > > > > setting ), > > > > > > > snmpd > > > > > > > > > didn't work anymore: > > > > > > > > > When I do a snmpwalk or snmpget to public@localhost it > doesn't > > > > > respond. > > > > > > > > > I checked snmpd, recreated snmpd.conf and launched again > snmpd > > > > > with -c > > > > > > > > > and -l to be sure it uses the correct files. > > > > > > > > > But even if snmpd is in background process, > public@localhost > > > > > doesn't > > > > > > > work. > > > > > > > > > I don't have any firewall rule that block it. > > > > > > > > > > > > > > > > > > #snmpwalk localhost public > > > > > > > > > Timeout: No Response from localhost > > > > > > > > > #snmpget localhost public SysName > > > > > > > > > Timeout: No Response from localhost. > > > > > > > > > > > > > > > > > > After I upgraded my system from 4.3-STABLE to 4.4-RC, it > didn't > > > > > change > > > > > > > > > anything for snmpd. > > > > > > > > > > > > > > > > > > If someone has got any idea... > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > Chojin > > > > > > > > > > > > > > > > > > > > > > > > > > > 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-questions" in the body of the message > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > ------=_NextPart_000_00C2_01C13FD4.3A5B1970 Content-Type: application/octet-stream; name="snmpd.conf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="snmpd.conf" com2sec local localhost public=0A= com2sec localrw localhost private=0A= com2sec mynetwork 192.168.0.0/24 public=0A= com2sec mynetworkrw 192.168.0.0/24 private=0A= =0A= ####=0A= # Second, map the security names into group names:=0A= =0A= # sec.model sec.name=0A= group LocalRWGroup v1 localrw=0A= group LocalRWGroup v2c localrw=0A= group LocalRWGroup usm localrw=0A= group LocalROGroup v1 local=0A= group LocalROGroup v2c local=0A= group LocalROGroup usm local=0A= group NetROGroup v1 mynetwork=0A= group NetROGroup v2c mynetwork=0A= group NetROGroup usm mynetwork=0A= group NetRWGroup v1 mynetworkrw=0A= group NetRWGroup v2c mynetworkrw=0A= group NetRWGroup usm mynetworkrw=0A= =0A= ####=0A= # Third, create a view for us to let the groups have rights to:=0A= =0A= # incl/excl subtree mask=0A= view all included .1 80=0A= =0A= ####=0A= # Finally, grant the 2 groups access to the 1 view with different=0A= # write permissions:=0A= =0A= # context sec.model sec.level match read write notif=0A= access LocalROGroup "" any noauth exact all none none=0A= access LocalRWGroup "" any noauth exact all all none=0A= access NetROGroup "" any noauth exact all none none=0A= access NetRWGroup "" any noauth exact all all none=0A= =0A= =0A= rocommunity public localhost=0A= ------=_NextPart_000_00C2_01C13FD4.3A5B1970-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 15:19: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from creme-brulee.marcuscom.com (rdu57-28-046.nc.rr.com [66.57.28.46]) by hub.freebsd.org (Postfix) with ESMTP id E01A137B407; Mon, 17 Sep 2001 15:18:15 -0700 (PDT) Received: from shumai.marcuscom.com (shumai.marcuscom.com [192.168.1.4]) by creme-brulee.marcuscom.com (8.11.3/8.11.3) with ESMTP id f8HMGW508567; Mon, 17 Sep 2001 18:16:32 -0400 (EDT) (envelope-from marcus@marcuscom.com) Received: from localhost (marcus@localhost) by shumai.marcuscom.com (8.11.3/8.11.3) with ESMTP id f8HMIU773467; Mon, 17 Sep 2001 18:18:30 -0400 (EDT) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: shumai.marcuscom.com: marcus owned process doing -bs Date: Mon, 17 Sep 2001 18:18:30 -0400 (EDT) From: Joe Clarke To: Chojin Cc: Jean-Francois Dive , , Subject: Re: Problem with snmpd In-Reply-To: <00c501c13fc3$9e9aeb10$0245a8c0@chojin> Message-ID: <20010917181428.Q69881-200000@shumai.marcuscom.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-840846285-1000765110=:69881" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-840846285-1000765110=:69881 Content-Type: TEXT/PLAIN; charset=US-ASCII Not sure. I have snmpd 4.2.1 working perfectly on 4.3-RELEASE and 4.4-STABLE as of an hour ago. Attached is my entire config file. I keep it in /usr/local/lib/snmp (which is the default location). Joe On Mon, 17 Sep 2001, Chojin wrote: > I didn't resolved my problem. > Even after upgraded to 4.4-stable (because there was maybe a bug in snmpd > :-p). > > I don't know what I could do. > > ----- Original Message ----- > From: "Chojin" > To: "Joe Clarke" > Cc: "Jean-Francois Dive" ; ; > > Sent: Wednesday, September 12, 2001 9:30 PM > Subject: Re: Problem with snmpd > > > > I tried your snmpd.conf but with no success :'( > > ----- Original Message ----- > > From: "Joe Clarke" > > To: "Chojin" > > Cc: "Jean-Francois Dive" ; > ; > > > > Sent: Wednesday, September 12, 2001 8:34 PM > > Subject: Re: Problem with snmpd > > > > > > > Can you send your snmp.conf file? These are the relevant bits of mine: > > > > > > com2sec local localhost public > > > com2sec localrw localhost private > > > com2sec mynetwork 172.18.0.0/24 public > > > com2sec mynetworkrw 172.18.0.0/24 private > > > > > > #### > > > # Second, map the security names into group names: > > > > > > # sec.model sec.name > > > group LocalRWGroup v1 localrw > > > group LocalRWGroup v2c localrw > > > group LocalRWGroup usm localrw > > > group LocalROGroup v1 local > > > group LocalROGroup v2c local > > > group LocalROGroup usm local > > > group NetROGroup v1 mynetwork > > > group NetROGroup v2c mynetwork > > > group NetROGroup usm mynetwork > > > group NetRWGroup v1 mynetworkrw > > > group NetRWGroup v2c mynetworkrw > > > group NetRWGroup usm mynetworkrw > > > > > > #### > > > # Third, create a view for us to let the groups have rights to: > > > > > > # incl/excl subtree mask > > > view all included .1 80 > > > > > > #### > > > # Finally, grant the 2 groups access to the 1 view with different > > > # write permissions: > > > > > > # context sec.model sec.level match read write notif > > > access LocalROGroup "" any noauth exact all none > none > > > access LocalRWGroup "" any noauth exact all all > none > > > access NetROGroup "" any noauth exact all none > none > > > access NetRWGroup "" any noauth exact all all > none > > > > > > > > > public@localhost does work on my machine. > > > > > > Joe > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > I used TMRTGCHO as community name before, but since I've got this > > problem I > > > > use now public. > > > > Request from localhost or any other interface doesn't work. > > > > I cleaned snmpd.log, restarted snmpd: > > > > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l > > > > /var/log/snmpd.log > > > > > > > > and a new one is located at http://www.tarakan-network.com/snmpd.log > (I > > did > > > > a snmpwalk and snmpget for public@localhost but no success) > > > > > > > > ----- Original Message ----- > > > > From: "Jean-Francois Dive" > > > > To: "Chojin" > > > > Sent: Wednesday, September 12, 2001 10:38 AM > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > Hi (salut) > > > > > > > > > > In fact, i see some successfull request with the community: > > > > > TMRTGCHO and no attemps with the localhost one... seems pretty odd. > > did > > > > > you only got those requests from localhost not working ? > > > > > > > > > > Otherwise, purge the log file, be *sure* that no requests are > comming > > from > > > > > somewhere else and resart to see some failures... > > > > > > > > > > JeF > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > I launched in debug mode > > > > > > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l > > > > > > /var/log/snmpd.log > > > > > > I attached snmpd.log > > > > > > There are so many informations I can't detect the problem :pp > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Jean-Francois Dive" > > > > > > To: "Chojin" > > > > > > Cc: ; > > > > > > Sent: Wednesday, September 12, 2001 9:53 AM > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > i think it is possible to start the snmpd and not send it to > > > > backgroud, > > > > > > > and see if it does printout some error messages..Otherwise use > the > > > > truss > > > > > > > command to follow the syscalls made by the daemon while > processing > > > > your > > > > > > > request, this could point you to a problem.. > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > snmpd.log is empty... > > > > > > > > > > > > > > > > I did #netstat -an | grep 161 > > > > > > > > udp4 0 0 *.161 *.* > > > > > > > > > > > > > > > > port 161 exists then it should work... > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > To: "Chojin" > > > > > > > > Cc: ; > > > > > > > > > > Sent: Wednesday, September 12, 2001 3:21 AM > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > So you have any traces in a log file or something similar ? > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > > > > > I have a problem with snmpd. > > > > > > > > > > > > > > > > > > > > In fact, one day, for unknown reason ( I didn't modify any > > > > > > setting ), > > > > > > > > snmpd > > > > > > > > > > didn't work anymore: > > > > > > > > > > When I do a snmpwalk or snmpget to public@localhost it > > doesn't > > > > > > respond. > > > > > > > > > > I checked snmpd, recreated snmpd.conf and launched again > > snmpd > > > > > > with -c > > > > > > > > > > and -l to be sure it uses the correct files. > > > > > > > > > > But even if snmpd is in background process, > > public@localhost > > > > > > doesn't > > > > > > > > work. > > > > > > > > > > I don't have any firewall rule that block it. > > > > > > > > > > > > > > > > > > > > #snmpwalk localhost public > > > > > > > > > > Timeout: No Response from localhost > > > > > > > > > > #snmpget localhost public SysName > > > > > > > > > > Timeout: No Response from localhost. > > > > > > > > > > > > > > > > > > > > After I upgraded my system from 4.3-STABLE to 4.4-RC, it > > didn't > > > > > > change > > > > > > > > > > anything for snmpd. > > > > > > > > > > > > > > > > > > > > If someone has got any idea... > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > > > Chojin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 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-questions" in the body of the message > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > --0-840846285-1000765110=:69881 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="snmpd.conf" Content-Transfer-Encoding: BASE64 Content-ID: <20010917181830.F69881@shumai.marcuscom.com> Content-Description: Content-Disposition: attachment; filename="snmpd.conf" IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIw0KIw0KIyBFWEFN UExFLmNvbmY6DQojICAgQW4gZXhhbXBsZSBjb25maWd1cmF0aW9uIGZpbGUg Zm9yIGNvbmZpZ3VyaW5nIHRoZSB1Y2Qtc25tcCBzbm1wZCBhZ2VudC4NCiMN CiMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMNCiMNCiMgVGhp cyBmaWxlIGlzIGludGVuZGVkIHRvIG9ubHkgYmUgYW4gZXhhbXBsZS4gIElm LCBob3dldmVyLCB5b3Ugd2FudA0KIyB0byB1c2UgaXQsIGl0IHNob3VsZCBi ZSBwbGFjZWQgaW4gL3Vzci9sb2NhbC9zaGFyZS9zbm1wL3NubXBkLmNvbmYu DQojIFdoZW4gdGhlIHNubXBkIGFnZW50IHN0YXJ0cyB1cCwgdGhpcyBpcyB3 aGVyZSBpdCB3aWxsIGxvb2sgZm9yIGl0Lg0KIw0KIyBOb3RlOiBUaGlzIGZp bGUgaXMgYXV0b21hdGljYWxseSBnZW5lcmF0ZWQgZnJvbSBFWEFNUExFLmNv bmYuZGVmLg0KIyBEbyBOT1QgcmVhZCB0aGUgRVhBTVBMRS5jb25mLmRlZiBm aWxlISBJbnN0ZWFkLCBhZnRlciB5b3UgaGF2ZSBydW4NCiMgY29uZmlndXJl ICYgbWFrZSwgYW5kIHRoZW4gbWFrZSBzdXJlIHlvdSByZWFkIHRoZSBFWEFN UExFLmNvbmYgZmlsZQ0KIyBpbnN0ZWFkLCBhcyBpdCB3aWxsIHRhaWxvciBp dHNlbGYgdG8geW91ciBjb25maWd1cmF0aW9uLg0KDQojIEFsbCBsaW5lcyBi ZWdpbm5pbmcgd2l0aCBhICcjJyBhcmUgY29tbWVudHMgYW5kIGFyZSBpbnRl bmRlZCBmb3IgeW91DQojIHRvIHJlYWQuICBBbGwgb3RoZXIgbGluZXMgYXJl IGNvbmZpZ3VyYXRpb24gY29tbWFuZHMgZm9yIHRoZSBhZ2VudC4NCg0KIw0K IyBQTEVBU0U6IHJlYWQgdGhlIHNubXBkLmNvbmYoNSkgbWFudWFsIHBhZ2Ug YXMgd2VsbCENCiMNCg0KDQojIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjDQojIEFjY2VzcyBDb250cm9sDQojIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjDQoNCiMgWU9VIFNIT1VMRCBDSEFOR0UgVEhFICJD T01NVU5JVFkiIFRPS0VOIEJFTE9XIFRPIEEgTkVXIEtFWVdPUkQgT05MWQ0K IyBLTk9XTiBBVCBZT1VSIFNJVEUuICBZT1UgKk1VU1QqIENIQU5HRSBUSEUg TkVUV09SSyBUT0tFTiBCRUxPVyBUTw0KIyBTT01FVEhJTkcgUkVGTEVDVElO RyBZT1VSIExPQ0FMIE5FVFdPUksgQUREUkVTUyBTUEFDRS4NCg0KIyBCeSBm YXIsIHRoZSBtb3N0IGNvbW1vbiBxdWVzdGlvbiBJIGdldCBhYm91dCB0aGUg YWdlbnQgaXMgIndoeSB3b24ndA0KIyBpdCB3b3JrPyIsIHdoZW4gcmVhbGx5 IGl0IHNob3VsZCBiZSAiaG93IGRvIEkgY29uZmlndXJlIHRoZSBhZ2VudCB0 bw0KIyBhbGxvdyBtZSB0byBhY2Nlc3MgaXQ/Ig0KIw0KIyBCeSBkZWZhdWx0 LCB0aGUgYWdlbnQgcmVzcG9uZHMgdG8gdGhlICJwdWJsaWMiIGNvbW11bml0 eSBmb3IgcmVhZA0KIyBvbmx5IGFjY2VzcywgaWYgcnVuIG91dCBvZiB0aGUg Ym94IHdpdGhvdXQgYW55IGNvbmZpZ3VyYXRpb24gZmlsZSBpbiANCiMgcGxh Y2UuICBUaGUgZm9sbG93aW5nIGV4YW1wbGVzIHNob3cgeW91IG90aGVyIHdh eXMgb2YgY29uZmlndXJpbmcNCiMgdGhlIGFnZW50IHNvIHRoYXQgeW91IGNh biBjaGFuZ2UgdGhlIGNvbW11bml0eSBuYW1lcywgYW5kIGdpdmUNCiMgeW91 cnNlbGYgd3JpdGUgYWNjZXNzIGFzIHdlbGwuDQojDQojIFRoZSBmb2xsb3dp bmcgbGluZXMgY2hhbmdlIHRoZSBhY2Nlc3MgcGVybWlzc2lvbnMgb2YgdGhl IGFnZW50IHNvDQojIHRoYXQgdGhlIENPTU1VTklUWSBzdHJpbmcgcHJvdmlk ZXMgcmVhZC1vbmx5IGFjY2VzcyB0byB5b3VyIGVudGlyZQ0KIyBORVRXT1JL IChFRzogMTAuMTAuMTAuMC8yNCksIGFuZCByZWFkL3dyaXRlIGFjY2VzcyB0 byBvbmx5IHRoZQ0KIyBsb2NhbGhvc3QgKDEyNy4wLjAuMSwgbm90IGl0cyBy ZWFsIGlwYWRkcmVzcykuDQojDQojIEZvciBtb3JlIGluZm9ybWF0aW9uLCBy ZWFkIHRoZSBGQVEgYXMgd2VsbCBhcyB0aGUgc25tcGQuY29uZig1KQ0KIyBt YW51YWwgcGFnZS4NCg0KIyMjIw0KIyBGaXJzdCwgbWFwIHRoZSBjb21tdW5p dHkgbmFtZSAoQ09NTVVOSVRZKSBpbnRvIGEgc2VjdXJpdHkgbmFtZQ0KIyAo bG9jYWwgYW5kIG15bmV0d29yaywgZGVwZW5kaW5nIG9uIHdoZXJlIHRoZSBy ZXF1ZXN0IGlzIGNvbWluZw0KIyBmcm9tKToNCg0KIyAgICAgICBzZWMubmFt ZSAgc291cmNlICAgICAgICAgIGNvbW11bml0eQ0KY29tMnNlYyBsb2NhbCAg ICAgbG9jYWxob3N0ICAgICAgIHB1YmxpYw0KY29tMnNlYyBsb2NhbHJ3ICAg bG9jYWxob3N0ICAgICAgIHByaXZhdGUNCmNvbTJzZWMgbXluZXR3b3JrIDE3 Mi4xOC4wLjAvMTYgcHVibGljDQpjb20yc2VjIG15bmV0d29ya3J3IDE3Mi4x OC4wLjAvMTYgIHByaXZhdGUNCg0KIyMjIw0KIyBTZWNvbmQsIG1hcCB0aGUg c2VjdXJpdHkgbmFtZXMgaW50byBncm91cCBuYW1lczoNCg0KIyAgICAgICAg ICAgICAJc2VjLm1vZGVsICBzZWMubmFtZQ0KZ3JvdXAgTG9jYWxSV0dyb3Vw CXYxICAgICAgICAgbG9jYWxydw0KZ3JvdXAgTG9jYWxSV0dyb3VwCXYyYyAg ICAgICAgbG9jYWxydw0KZ3JvdXAgTG9jYWxSV0dyb3VwCXVzbSAgICAgICAg bG9jYWxydw0KZ3JvdXAgTG9jYWxST0dyb3VwCXYxCSAgIGxvY2FsDQpncm91 cCBMb2NhbFJPR3JvdXAJdjJjCSAgIGxvY2FsDQpncm91cCBMb2NhbFJPR3Jv dXAJdXNtCSAgIGxvY2FsDQpncm91cCBOZXRST0dyb3VwIHYxICAgICAgICAg bXluZXR3b3JrDQpncm91cCBOZXRST0dyb3VwIHYyYyAgICAgICAgbXluZXR3 b3JrDQpncm91cCBOZXRST0dyb3VwIHVzbSAgICAgICAgbXluZXR3b3JrDQpn cm91cCBOZXRSV0dyb3VwIHYxICAgICAgICAgbXluZXR3b3JrcncNCmdyb3Vw IE5ldFJXR3JvdXAgdjJjICAgICAgICBteW5ldHdvcmtydw0KZ3JvdXAgTmV0 UldHcm91cCB1c20gICAgICAgIG15bmV0d29ya3J3DQoNCiMjIyMNCiMgVGhp cmQsIGNyZWF0ZSBhIHZpZXcgZm9yIHVzIHRvIGxldCB0aGUgZ3JvdXBzIGhh dmUgcmlnaHRzIHRvOg0KDQojICAgICAgICAgICBpbmNsL2V4Y2wgc3VidHJl ZSAgICAgICAgICAgICAgICAgICAgICAgICAgbWFzaw0KdmlldyBhbGwgICAg aW5jbHVkZWQgIC4xICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDgw DQoNCiMjIyMNCiMgRmluYWxseSwgZ3JhbnQgdGhlIDIgZ3JvdXBzIGFjY2Vz cyB0byB0aGUgMSB2aWV3IHdpdGggZGlmZmVyZW50DQojIHdyaXRlIHBlcm1p c3Npb25zOg0KDQojICAgICAgICAgICAgICAgIGNvbnRleHQgc2VjLm1vZGVs IHNlYy5sZXZlbCBtYXRjaCAgcmVhZCAgIHdyaXRlICBub3RpZg0KYWNjZXNz IExvY2FsUk9Hcm91cCAiIiAgICAgIGFueSAgICAgICBub2F1dGggICAgZXhh Y3QgIGFsbCAgICBub25lICAgbm9uZQ0KYWNjZXNzIExvY2FsUldHcm91cCAi IiAgICAgIGFueSAgICAgICBub2F1dGggICAgZXhhY3QgIGFsbCAgICBhbGwg ICAgbm9uZQ0KYWNjZXNzIE5ldFJPR3JvdXAgICAiIiAgICAgIGFueSAgICAg ICBub2F1dGggICAgZXhhY3QgIGFsbCAgICBub25lICAgbm9uZQ0KYWNjZXNz IE5ldFJXR3JvdXAgICAiIiAgICAgIGFueSAgICAgICBub2F1dGggICAgZXhh Y3QgIGFsbCAgICBhbGwgICAgbm9uZQ0KDQojIC0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tDQoNCg0KIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIw0KIyBTeXN0ZW0gY29udGFjdCBpbmZvcm1hdGlvbg0KIw0K DQojIEl0IGlzIGFsc28gcG9zc2libGUgdG8gc2V0IHRoZSBzeXNDb250YWN0 IGFuZCBzeXNMb2NhdGlvbiBzeXN0ZW0NCiMgdmFyaWFibGVzIHRocm91Z2gg dGhlIHNubXBkLmNvbmYgZmlsZToNCg0Kc3lzbG9jYXRpb24gUlRQLU5NUyBT ZXJ2ZXIgUmFjaw0Kc3lzY29udGFjdCBKb2UgQ2xhcmtlIDxqY2xhcmtlQGNp c2NvLmNvbT4NCg0KDQojIEV4YW1wbGUgb3V0cHV0IG9mIHNubXB3YWxrOg0K IyAgICUgc25tcHdhbGsgLXYgMSBsb2NhbGhvc3QgcHVibGljIHN5c3RlbQ0K IyAgIHN5c3RlbS5zeXNEZXNjci4wID0gIlN1bk9TIG5hbWUgc3VuNGMiDQoj ICAgc3lzdGVtLnN5c09iamVjdElELjAgPSBPSUQ6IGVudGVycHJpc2VzLnVj ZGF2aXMudWNkU25tcEFnZW50LnN1bm9zNA0KIyAgIHN5c3RlbS5zeXNVcFRp bWUuMCA9IFRpbWV0aWNrczogKDU5NTYzNzU0OCkgNjggZGF5cywgMjI6MzI6 NTUNCiMgICBzeXN0ZW0uc3lzQ29udGFjdC4wID0gIk1lIDxtZUBzb21ld2hl cmUub3JnPiINCiMgICBzeXN0ZW0uc3lzTmFtZS4wID0gIm5hbWUiDQojICAg c3lzdGVtLnN5c0xvY2F0aW9uLjAgPSAiUmlnaHQgaGVyZSwgcmlnaHQgbm93 LiINCiMgICBzeXN0ZW0uc3lzU2VydmljZXMuMCA9IDcyDQoNCg0KIyAtLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQoNCiMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMNCiMgUHJvY2VzcyBjaGVja3MuDQoj DQojICBUaGUgZm9sbG93aW5nIGFyZSBleGFtcGxlcyBvZiBob3cgdG8gdXNl IHRoZSBhZ2VudCB0byBjaGVjayBmb3INCiMgIHByb2Nlc3NlcyBydW5uaW5n IG9uIHRoZSBob3N0LiAgVGhlIHN5bnRheCBsb29rcyBzb21ldGhpbmcgbGlr ZToNCiMNCiMgIHByb2MgTkFNRSBbTUFYPTBdIFtNSU49MF0NCiMNCiMgIE5B TUU6ICB0aGUgbmFtZSBvZiB0aGUgcHJvY2VzcyB0byBjaGVjayBmb3IuICBJ dCBtdXN0IG1hdGNoDQojICAgICAgICAgZXhhY3RseSAoaWUsIGh0dHAgd2ls bCBub3QgZmluZCBodHRwZCBwcm9jZXNzZXMpLg0KIyAgTUFYOiAgIHRoZSBt YXhpbXVtIG51bWJlciBhbGxvd2VkIHRvIGJlIHJ1bm5pbmcuICBEZWZhdWx0 cyB0byAwLg0KIyAgTUlOOiAgIHRoZSBtaW5pbXVtIG51bWJlciB0byBiZSBy dW5uaW5nLiAgRGVmYXVsdHMgdG8gMC4NCg0KIw0KIyAgRXhhbXBsZXM6DQoj DQoNCiMgIE1ha2Ugc3VyZSBtb3VudGQgaXMgcnVubmluZw0KcHJvYyBpbmV0 ZA0KDQoNCiMgIE1ha2Ugc3VyZSBhdCBsZWFzdCBvbmUgc2VuZG1haWwsIGJ1 dCBsZXNzIHRoYW4gb3IgZXF1YWwgdG8gMTAgYXJlIHJ1bm5pbmcuDQpwcm9j IHNlbmRtYWlsIDEwIDENCg0KDQojICBBIHNubXB3YWxrIG9mIHRoZSBwcm9j ZXNzIG1pYiB0cmVlIHdvdWxkIGxvb2sgc29tZXRoaW5nIGxpa2UgdGhpczoN CiMgDQojICUgc25tcHdhbGsgLXYgMSBsb2NhbGhvc3QgcHVibGljIC4xLjMu Ni4xLjQuMS4yMDIxLjINCiMgZW50ZXJwcmlzZXMudWNkYXZpcy5wcm9jVGFi bGUucHJFbnRyeS5wckluZGV4LjEgPSAxDQojIGVudGVycHJpc2VzLnVjZGF2 aXMucHJvY1RhYmxlLnByRW50cnkucHJJbmRleC4yID0gMg0KIyBlbnRlcnBy aXNlcy51Y2RhdmlzLnByb2NUYWJsZS5wckVudHJ5LnBySW5kZXguMyA9IDMN CiMgZW50ZXJwcmlzZXMudWNkYXZpcy5wcm9jVGFibGUucHJFbnRyeS5wck5h bWVzLjEgPSAibW91bnRkIg0KIyBlbnRlcnByaXNlcy51Y2RhdmlzLnByb2NU YWJsZS5wckVudHJ5LnByTmFtZXMuMiA9ICJudGFsa2QiDQojIGVudGVycHJp c2VzLnVjZGF2aXMucHJvY1RhYmxlLnByRW50cnkucHJOYW1lcy4zID0gInNl bmRtYWlsIg0KIyBlbnRlcnByaXNlcy51Y2RhdmlzLnByb2NUYWJsZS5wckVu dHJ5LnByTWluLjEgPSAwDQojIGVudGVycHJpc2VzLnVjZGF2aXMucHJvY1Rh YmxlLnByRW50cnkucHJNaW4uMiA9IDANCiMgZW50ZXJwcmlzZXMudWNkYXZp cy5wcm9jVGFibGUucHJFbnRyeS5wck1pbi4zID0gMQ0KIyBlbnRlcnByaXNl cy51Y2RhdmlzLnByb2NUYWJsZS5wckVudHJ5LnByTWF4LjEgPSAwDQojIGVu dGVycHJpc2VzLnVjZGF2aXMucHJvY1RhYmxlLnByRW50cnkucHJNYXguMiA9 IDQNCiMgZW50ZXJwcmlzZXMudWNkYXZpcy5wcm9jVGFibGUucHJFbnRyeS5w ck1heC4zID0gMTANCiMgZW50ZXJwcmlzZXMudWNkYXZpcy5wcm9jVGFibGUu cHJFbnRyeS5wckNvdW50LjEgPSAwDQojIGVudGVycHJpc2VzLnVjZGF2aXMu cHJvY1RhYmxlLnByRW50cnkucHJDb3VudC4yID0gMA0KIyBlbnRlcnByaXNl cy51Y2RhdmlzLnByb2NUYWJsZS5wckVudHJ5LnByQ291bnQuMyA9IDENCiMg ZW50ZXJwcmlzZXMudWNkYXZpcy5wcm9jVGFibGUucHJFbnRyeS5wckVycm9y RmxhZy4xID0gMQ0KIyBlbnRlcnByaXNlcy51Y2RhdmlzLnByb2NUYWJsZS5w ckVudHJ5LnByRXJyb3JGbGFnLjIgPSAwDQojIGVudGVycHJpc2VzLnVjZGF2 aXMucHJvY1RhYmxlLnByRW50cnkucHJFcnJvckZsYWcuMyA9IDANCiMgZW50 ZXJwcmlzZXMudWNkYXZpcy5wcm9jVGFibGUucHJFbnRyeS5wckVyck1lc3Nh Z2UuMSA9ICJObyBtb3VudGQgcHJvY2VzcyBydW5uaW5nLiINCiMgZW50ZXJw cmlzZXMudWNkYXZpcy5wcm9jVGFibGUucHJFbnRyeS5wckVyck1lc3NhZ2Uu MiA9ICIiDQojIGVudGVycHJpc2VzLnVjZGF2aXMucHJvY1RhYmxlLnByRW50 cnkucHJFcnJNZXNzYWdlLjMgPSAiIg0KIyBlbnRlcnByaXNlcy51Y2Rhdmlz LnByb2NUYWJsZS5wckVudHJ5LnByRXJyRml4LjEgPSAwDQojIGVudGVycHJp c2VzLnVjZGF2aXMucHJvY1RhYmxlLnByRW50cnkucHJFcnJGaXguMiA9IDAN CiMgZW50ZXJwcmlzZXMudWNkYXZpcy5wcm9jVGFibGUucHJFbnRyeS5wckVy ckZpeC4zID0gMA0KIw0KIyAgTm90ZSB0aGF0IHRoZSBlcnJvckZsYWcgZm9y IG1vdW50ZCBpcyBzZXQgdG8gMSBiZWNhdXNlIG9uZSBpcyBub3QNCiMgIHJ1 bm5pbmcgKGluIHRoaXMgY2FzZSBhbiBycGMubW91bnRkIGlzLCBidXQgdGhh dHMgbm90IGdvb2QgZW5vdWdoKSwNCiMgIGFuZCB0aGUgRXJyTWVzc2FnZSB0 ZWxscyB5b3Ugd2hhdCdzIHdyb25nLiAgVGhlIGNvbmZpZ3VyYXRpb24NCiMg IGltcG9zZWQgaW4gdGhlIHNubXBkLmNvbmYgZmlsZSBpcyBhbHNvIHNob3du LiAgDQojIA0KIyAgU3BlY2lhbCBDYXNlOiAgV2hlbiB0aGUgbWluIGFuZCBt YXggbnVtYmVycyBhcmUgYm90aCAwLCBpdCBhc3N1bWVzDQojICB5b3Ugd2Fu dCBhIG1heCBvZiBpbmZpbml0eSBhbmQgYSBtaW4gb2YgMS4NCiMNCg0KDQoj IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCg0KIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIw0KIyBFeGVjdXRhYmxlcy9z Y3JpcHRzDQojDQoNCiMNCiMgIFlvdSBjYW4gYWxzbyBoYXZlIHByb2dyYW1z IHJ1biBieSB0aGUgYWdlbnQgdGhhdCByZXR1cm4gYSBzaW5nbGUNCiMgIGxp bmUgb2Ygb3V0cHV0IGFuZCBhbiBleGl0IGNvZGUuICBIZXJlIGFyZSB0d28g ZXhhbXBsZXMuDQojDQojICBleGVjIE5BTUUgUFJPR1JBTSBbQVJHUyAuLi5d DQojDQojICBOQU1FOiAgICAgQSBnZW5lcmljIG5hbWUuDQojICBQUk9HUkFN OiAgVGhlIHByb2dyYW0gdG8gcnVuLiAgSW5jbHVkZSB0aGUgcGF0aCENCiMg IEFSR1M6ICAgICBvcHRpb25hbCBhcmd1bWVudHMgdG8gYmUgcGFzc2VkIHRv IHRoZSBwcm9ncmFtDQoNCiMgYSBzaW1wbGUgaGVsbG8gd29ybGQNCiNleGVj IGVjaG90ZXN0IC9iaW4vZWNobyBoZWxsbyB3b3JsZA0KDQojIFJ1biBhIHNo ZWxsIHNjcmlwdCBjb250YWluaW5nOg0KIw0KIyAjIS9iaW4vc2gNCiMgZWNo byBoZWxsbyB3b3JsZA0KIyBlY2hvIGhpIHRoZXJlDQojIGV4aXQgMzUNCiMN CiMgTm90ZTogIHRoaXMgaGFzIGJlZW4gc3BlY2lmaWNhbGx5IGNvbW1lbnRl ZCBvdXQgdG8gcHJldmVudA0KIyBhY2NpZGVudGFsIHNlY3VyaXR5IGhvbGVz IGR1ZSB0byBzb21lb25lIGVsc2Ugb24geW91ciBzeXN0ZW0gd3JpdGluZw0K IyBhIC90bXAvc2h0ZXN0IGJlZm9yZSB5b3UgZG8uICBVbmNvbW1lbnQgdG8g dXNlIGl0Lg0KIw0KI2V4ZWMgc2hlbGx0ZXN0IC9iaW4vc2ggL3RtcC9zaHRl c3QNCg0KIyBUaGVuLCANCiMgJSBzbm1wd2FsayAtdiAxIGxvY2FsaG9zdCBw dWJsaWMgLjEuMy42LjEuNC4xLjIwMjEuOA0KIyBlbnRlcnByaXNlcy51Y2Rh dmlzLmV4dFRhYmxlLmV4dEVudHJ5LmV4dEluZGV4LjEgPSAxDQojIGVudGVy cHJpc2VzLnVjZGF2aXMuZXh0VGFibGUuZXh0RW50cnkuZXh0SW5kZXguMiA9 IDINCiMgZW50ZXJwcmlzZXMudWNkYXZpcy5leHRUYWJsZS5leHRFbnRyeS5l eHROYW1lcy4xID0gImVjaG90ZXN0Ig0KIyBlbnRlcnByaXNlcy51Y2Rhdmlz LmV4dFRhYmxlLmV4dEVudHJ5LmV4dE5hbWVzLjIgPSAic2hlbGx0ZXN0Ig0K IyBlbnRlcnByaXNlcy51Y2RhdmlzLmV4dFRhYmxlLmV4dEVudHJ5LmV4dENv bW1hbmQuMSA9ICIvYmluL2VjaG8gaGVsbG8gd29ybGQiDQojIGVudGVycHJp c2VzLnVjZGF2aXMuZXh0VGFibGUuZXh0RW50cnkuZXh0Q29tbWFuZC4yID0g Ii9iaW4vc2ggL3RtcC9zaHRlc3QiDQojIGVudGVycHJpc2VzLnVjZGF2aXMu ZXh0VGFibGUuZXh0RW50cnkuZXh0UmVzdWx0LjEgPSAwDQojIGVudGVycHJp c2VzLnVjZGF2aXMuZXh0VGFibGUuZXh0RW50cnkuZXh0UmVzdWx0LjIgPSAz NQ0KIyBlbnRlcnByaXNlcy51Y2RhdmlzLmV4dFRhYmxlLmV4dEVudHJ5LmV4 dE91dHB1dC4xID0gImhlbGxvIHdvcmxkLiINCiMgZW50ZXJwcmlzZXMudWNk YXZpcy5leHRUYWJsZS5leHRFbnRyeS5leHRPdXRwdXQuMiA9ICJoZWxsbyB3 b3JsZC4iDQojIGVudGVycHJpc2VzLnVjZGF2aXMuZXh0VGFibGUuZXh0RW50 cnkuZXh0RXJyRml4LjEgPSAwDQojIGVudGVycHJpc2VzLnVjZGF2aXMuZXh0 VGFibGUuZXh0RW50cnkuZXh0RXJyRml4LjIgPSAwDQoNCiMgTm90ZSB0aGF0 IHRoZSBzZWNvbmQgbGluZSBvZiB0aGUgL3RtcC9zaHRlc3Qgc2hlbGwgc2Ny aXB0IGlzIGN1dA0KIyBvZmYuICBBbHNvIG5vdGUgdGhhdCB0aGUgZXhpdCBz dGF0dXMgb2YgMzUgd2FzIHJldHVybmVkLg0KDQojIC0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tDQoNCg0KIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIw0KIyBkaXNrIGNoZWNrcw0KIw0KDQojIFRoZSBhZ2Vu dCBjYW4gY2hlY2sgdGhlIGFtb3VudCBvZiBhdmFpbGFibGUgZGlzayBzcGFj ZSwgYW5kIG1ha2UNCiMgc3VyZSBpdCBpcyBhYm92ZSBhIHNldCBsaW1pdC4g IA0KDQojIGRpc2sgUEFUSCBbTUlOPURFRkRJU0tNSU5JTVVNU1BBQ0VdDQoj DQojIFBBVEg6ICBtb3VudCBwYXRoIHRvIHRoZSBkaXNrIGluIHF1ZXN0aW9u Lg0KIyBNSU46ICAgRGlza3Mgd2l0aCBzcGFjZSBiZWxvdyB0aGlzIHZhbHVl IHdpbGwgaGF2ZSB0aGUgTWliJ3MgZXJyb3JGbGFnIHNldC4NCiMgICAgICAg IERlZmF1bHQgdmFsdWUgPSBERUZESVNLTUlOSU1VTVNQQUNFLg0KDQojIENo ZWNrIHRoZSAvIHBhcnRpdGlvbiBhbmQgbWFrZSBzdXJlIGl0IGNvbnRhaW5z IGF0IGxlYXN0IDEwIG1lZ3MuDQoNCmRpc2sgLyAxMCUNCmRpc2sgL3VzciAx MCUNCmRpc2sgL3ZhciAxMCUNCg0KDQojICUgc25tcHdhbGsgLXYgMSBsb2Nh bGhvc3QgcHVibGljIC4xLjMuNi4xLjQuMS4yMDIxLjkNCiMgZW50ZXJwcmlz ZXMudWNkYXZpcy5kaXNrVGFibGUuZHNrRW50cnkuZGlza0luZGV4LjEgPSAw DQojIGVudGVycHJpc2VzLnVjZGF2aXMuZGlza1RhYmxlLmRza0VudHJ5LmRp c2tQYXRoLjEgPSAiLyIgSGV4OiAyRiANCiMgZW50ZXJwcmlzZXMudWNkYXZp cy5kaXNrVGFibGUuZHNrRW50cnkuZGlza0RldmljZS4xID0gIi9kZXYvZHNr L2MyMDFkNnMwIg0KIyBlbnRlcnByaXNlcy51Y2RhdmlzLmRpc2tUYWJsZS5k c2tFbnRyeS5kaXNrTWluaW11bS4xID0gMTAwMDANCiMgZW50ZXJwcmlzZXMu dWNkYXZpcy5kaXNrVGFibGUuZHNrRW50cnkuZGlza1RvdGFsLjEgPSA4Mzcx MzANCiMgZW50ZXJwcmlzZXMudWNkYXZpcy5kaXNrVGFibGUuZHNrRW50cnku ZGlza0F2YWlsLjEgPSAzMTYzMjUNCiMgZW50ZXJwcmlzZXMudWNkYXZpcy5k aXNrVGFibGUuZHNrRW50cnkuZGlza1VzZWQuMSA9IDQzNzA5Mg0KIyBlbnRl cnByaXNlcy51Y2RhdmlzLmRpc2tUYWJsZS5kc2tFbnRyeS5kaXNrUGVyY2Vu dC4xID0gNTgNCiMgZW50ZXJwcmlzZXMudWNkYXZpcy5kaXNrVGFibGUuZHNr RW50cnkuZGlza0Vycm9yRmxhZy4xID0gMA0KIyBlbnRlcnByaXNlcy51Y2Rh dmlzLmRpc2tUYWJsZS5kc2tFbnRyeS5kaXNrRXJyb3JNc2cuMSA9ICIiDQoN CiMgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KDQojIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjDQojIGxvYWQgYXZlcmFn ZSBjaGVja3MNCiMNCg0KIyBsb2FkIFsxTUFYPURFRk1BWExPQURBVkVdIFs1 TUFYPURFRk1BWExPQURBVkVdIFsxNU1BWD1ERUZNQVhMT0FEQVZFXQ0KIw0K IyAxTUFYOiAgIElmIHRoZSAxIG1pbnV0ZSBsb2FkIGF2ZXJhZ2UgaXMgYWJv dmUgdGhpcyBsaW1pdCBhdCBxdWVyeQ0KIyAgICAgICAgIHRpbWUsIHRoZSBl cnJvckZsYWcgd2lsbCBiZSBzZXQuDQojIDVNQVg6ICAgU2ltaWxhciwgYnV0 IGZvciA1IG1pbiBhdmVyYWdlLg0KIyAxNU1BWDogIFNpbWlsYXIsIGJ1dCBm b3IgMTUgbWluIGF2ZXJhZ2UuDQoNCiMgQ2hlY2sgZm9yIGxvYWRzOg0KbG9h ZCAyIDIgNA0KDQojICUgc25tcHdhbGsgLXYgMSBsb2NhbGhvc3QgcHVibGlj IC4xLjMuNi4xLjQuMS4yMDIxLjEwDQojIGVudGVycHJpc2VzLnVjZGF2aXMu bG9hZFRhYmxlLmxhRW50cnkubG9hZGF2ZUluZGV4LjEgPSAxDQojIGVudGVy cHJpc2VzLnVjZGF2aXMubG9hZFRhYmxlLmxhRW50cnkubG9hZGF2ZUluZGV4 LjIgPSAyDQojIGVudGVycHJpc2VzLnVjZGF2aXMubG9hZFRhYmxlLmxhRW50 cnkubG9hZGF2ZUluZGV4LjMgPSAzDQojIGVudGVycHJpc2VzLnVjZGF2aXMu bG9hZFRhYmxlLmxhRW50cnkubG9hZGF2ZU5hbWVzLjEgPSAiTG9hZC0xIg0K IyBlbnRlcnByaXNlcy51Y2RhdmlzLmxvYWRUYWJsZS5sYUVudHJ5LmxvYWRh dmVOYW1lcy4yID0gIkxvYWQtNSINCiMgZW50ZXJwcmlzZXMudWNkYXZpcy5s b2FkVGFibGUubGFFbnRyeS5sb2FkYXZlTmFtZXMuMyA9ICJMb2FkLTE1Ig0K IyBlbnRlcnByaXNlcy51Y2RhdmlzLmxvYWRUYWJsZS5sYUVudHJ5LmxvYWRh dmVMb2FkLjEgPSAiMC40OSIgSGV4OiAzMCAyRSAzNCAzOSANCiMgZW50ZXJw cmlzZXMudWNkYXZpcy5sb2FkVGFibGUubGFFbnRyeS5sb2FkYXZlTG9hZC4y ID0gIjAuMzEiIEhleDogMzAgMkUgMzMgMzEgDQojIGVudGVycHJpc2VzLnVj ZGF2aXMubG9hZFRhYmxlLmxhRW50cnkubG9hZGF2ZUxvYWQuMyA9ICIwLjI2 IiBIZXg6IDMwIDJFIDMyIDM2IA0KIyBlbnRlcnByaXNlcy51Y2RhdmlzLmxv YWRUYWJsZS5sYUVudHJ5LmxvYWRhdmVDb25maWcuMSA9ICIxMi4wMCINCiMg ZW50ZXJwcmlzZXMudWNkYXZpcy5sb2FkVGFibGUubGFFbnRyeS5sb2FkYXZl Q29uZmlnLjIgPSAiMTQuMDAiDQojIGVudGVycHJpc2VzLnVjZGF2aXMubG9h ZFRhYmxlLmxhRW50cnkubG9hZGF2ZUNvbmZpZy4zID0gIjE0LjAwIg0KIyBl bnRlcnByaXNlcy51Y2RhdmlzLmxvYWRUYWJsZS5sYUVudHJ5LmxvYWRhdmVF cnJvckZsYWcuMSA9IDANCiMgZW50ZXJwcmlzZXMudWNkYXZpcy5sb2FkVGFi bGUubGFFbnRyeS5sb2FkYXZlRXJyb3JGbGFnLjIgPSAwDQojIGVudGVycHJp c2VzLnVjZGF2aXMubG9hZFRhYmxlLmxhRW50cnkubG9hZGF2ZUVycm9yRmxh Zy4zID0gMA0KIyBlbnRlcnByaXNlcy51Y2RhdmlzLmxvYWRUYWJsZS5sYUVu dHJ5LmxvYWRhdmVFcnJNZXNzYWdlLjEgPSAiIg0KIyBlbnRlcnByaXNlcy51 Y2RhdmlzLmxvYWRUYWJsZS5sYUVudHJ5LmxvYWRhdmVFcnJNZXNzYWdlLjIg PSAiIg0KIyBlbnRlcnByaXNlcy51Y2RhdmlzLmxvYWRUYWJsZS5sYUVudHJ5 LmxvYWRhdmVFcnJNZXNzYWdlLjMgPSAiIg0KDQojIC0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tDQoNCg0KIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIw0KIyBFeHRlbnNpYmxlIHNlY3Rpb25zLg0KIyANCg0K IyBUaGlzIGFsbGV2aWF0ZXMgdGhlIG11bHRpcGxlIGxpbmUgb3V0cHV0IHBy b2JsZW0gZm91bmQgaW4gdGhlDQojIHByZXZpb3VzIGV4ZWN1dGFibGUgbWli IGJ5IHBsYWNpbmcgZWFjaCBtaWIgaW4gaXRzIG93biBtaWIgdGFibGU6DQoN CiMgUnVuIGEgc2hlbGwgc2NyaXB0IGNvbnRhaW5pbmc6DQojDQojICMhL2Jp bi9zaA0KIyBlY2hvIGhlbGxvIHdvcmxkDQojIGVjaG8gaGkgdGhlcmUNCiMg ZXhpdCAzNQ0KIw0KIyBOb3RlOiAgdGhpcyBoYXMgYmVlbiBzcGVjaWZpY2Fs bHkgY29tbWVudGVkIG91dCB0byBwcmV2ZW50DQojIGFjY2lkZW50YWwgc2Vj dXJpdHkgaG9sZXMgZHVlIHRvIHNvbWVvbmUgZWxzZSBvbiB5b3VyIHN5c3Rl bSB3cml0aW5nDQojIGEgL3RtcC9zaHRlc3QgYmVmb3JlIHlvdSBkby4gIFVu Y29tbWVudCB0byB1c2UgaXQuDQojDQojIGV4ZWMgLjEuMy42LjEuNC4xLjIw MjEuNTAgc2hlbGx0ZXN0IC9iaW4vc2ggL3RtcC9zaHRlc3QNCg0KIyAlIHNu bXB3YWxrIC12IDEgbG9jYWxob3N0IHB1YmxpYyAuMS4zLjYuMS40LjEuMjAy MS41MA0KIyBlbnRlcnByaXNlcy51Y2RhdmlzLjUwLjEuMSA9IDENCiMgZW50 ZXJwcmlzZXMudWNkYXZpcy41MC4yLjEgPSAic2hlbGx0ZXN0Ig0KIyBlbnRl cnByaXNlcy51Y2RhdmlzLjUwLjMuMSA9ICIvYmluL3NoIC90bXAvc2h0ZXN0 Ig0KIyBlbnRlcnByaXNlcy51Y2RhdmlzLjUwLjEwMC4xID0gMzUNCiMgZW50 ZXJwcmlzZXMudWNkYXZpcy41MC4xMDEuMSA9ICJoZWxsbyB3b3JsZC4iDQoj IGVudGVycHJpc2VzLnVjZGF2aXMuNTAuMTAxLjIgPSAiaGkgdGhlcmUuIg0K IyBlbnRlcnByaXNlcy51Y2RhdmlzLjUwLjEwMi4xID0gMA0KDQojIE5vdyB0 aGUgT3V0cHV0IGhhcyBncm93biB0byB0d28gbGluZXMsIGFuZCB3ZSBjYW4g c2VlIHRoZSAnaGkNCiMgdGhlcmUuJyBvdXRwdXQgYXMgdGhlIHNlY29uZCBs aW5lIGZyb20gb3VyIHNoZWxsIHNjcmlwdC4NCiMNCiMgTm90ZSB0aGF0IHlv dSBtdXN0IGFsdGVyIHRoZSBtaWIudHh0IGZpbGUgdG8gYmUgY29ycmVjdCBp ZiB5b3Ugd2FudA0KIyB0aGUgLjUwLiogb3V0cHV0cyBhYm92ZSB0byBjaGFu Z2UgdG8gcmVhc29uYWJsZSB0ZXh0IGRlc2NyaXB0aW9ucy4NCg0KIyBPdGhl ciBpZGVhczoNCiMgDQojIGV4ZWMgLjEuMy42LjEuNC4xLjIwMjEuNTEgcHMg L2Jpbi9wcyANCiMgZXhlYyAuMS4zLjYuMS40LjEuMjAyMS41MiB0b3AgL3Vz ci9sb2NhbC9iaW4vdG9wDQojIGV4ZWMgLjEuMy42LjEuNC4xLjIwMjEuNTMg bWFpbHEgL3Vzci9iaW4vbWFpbHENCg0KIyAtLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLQ0KDQoNCiMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMNCiMgUGFzcyB0aHJvdWdoIGNvbnRyb2wuDQojIA0KDQojIFVz YWdlOg0KIyAgIHBhc3MgTUlCT0lEIEVYRUMtQ09NTUFORA0KIw0KIyBUaGlz IHdpbGwgcGFzcyB0b3RhbCBjb250cm9sIG9mIHRoZSBtaWIgdW5kZXJuZWF0 aCB0aGUgTUlCT0lEDQojIHBvcnRpb24gb2YgdGhlIG1pYiB0byB0aGUgRVhF Qy1DT01NQU5ELiAgDQojDQojIE5vdGU6ICBZb3UnbGwgaGF2ZSB0byBjaGFu Z2UgdGhlIHBhdGggb2YgdGhlIHBhc3N0ZXN0IHNjcmlwdCB0byB5b3VyDQoj IHNvdXJjZSBkaXJlY3Rvcnkgb3IgaW5zdGFsbCBpdCBpbiB0aGUgZ2l2ZW4g bG9jYXRpb24uDQojIA0KIyBFeGFtcGxlOiAgKHNlZSB0aGUgc2NyaXB0IGZv ciBkZXRhaWxzKQ0KIyAgICAgICAgICAgKGNvbW1lbnRlZCBvdXQgaGVyZSBz aW5jZSBpdCByZXF1aXJlcyB0aGF0IHlvdSBwbGFjZSB0aGUNCiMgICAgICAg ICAgIHNjcmlwdCBpbiB0aGUgcmlnaHQgbG9jYXRpb24uIChpdHMgbm90IGlu c3RhbGxlZCBieSBkZWZhdWx0KSkNCg0KIyBwYXNzIC4xLjMuNi4xLjQuMS4y MDIxLjI1NSAvYmluL3NoIC91c3IvbG9jYWwvbG9jYWwvcGFzc3Rlc3QNCg0K IyAlIHNubXB3YWxrIC12IDEgbG9jYWxob3N0IHB1YmxpYyAuMS4zLjYuMS40 LjEuMjAyMS4yNTUNCiMgZW50ZXJwcmlzZXMudWNkYXZpcy4yNTUuMSA9ICJs aWZlIHRoZSB1bml2ZXJzZSBhbmQgZXZlcnl0aGluZyINCiMgZW50ZXJwcmlz ZXMudWNkYXZpcy4yNTUuMi4xID0gNDINCiMgZW50ZXJwcmlzZXMudWNkYXZp cy4yNTUuMi4yID0gT0lEOiA0Mi40Mi40Mg0KIyBlbnRlcnByaXNlcy51Y2Rh dmlzLjI1NS4zID0gVGltZXRpY2tzOiAoMzYzMTM2MjAwKSA0MiBkYXlzLCAw OjQyOjQyDQojIGVudGVycHJpc2VzLnVjZGF2aXMuMjU1LjQgPSBJcEFkZHJl c3M6IDEyNy4wLjAuMQ0KIyBlbnRlcnByaXNlcy51Y2RhdmlzLjI1NS41ID0g NDINCiMgZW50ZXJwcmlzZXMudWNkYXZpcy4yNTUuNiA9IEdhdWdlOiA0Mg0K Iw0KIyAlIHNubXBnZXQgLXYgMSBsb2NhbGhvc3QgcHVibGljIC4xLjMuNi4x LjQuMS4yMDIxLjI1NS41DQojIGVudGVycHJpc2VzLnVjZGF2aXMuMjU1LjUg PSA0Mg0KIw0KIyAlIHNubXBzZXQgLXYgMSBsb2NhbGhvc3QgcHVibGljIC4x LjMuNi4xLjQuMS4yMDIxLjI1NS4xIHMgIk5ldyBzdHJpbmciDQojIGVudGVy cHJpc2VzLnVjZGF2aXMuMjU1LjEgPSAiTmV3IHN0cmluZyINCiMNCg0KIyBG b3Igc3BlY2lmaWMgdXNhZ2UgaW5mb3JtYXRpb24sIHNlZSB0aGUgbWFuL3Nu bXBkLmNvbmYuNSBtYW51YWwgcGFnZQ0KIyBhcyB3ZWxsIGFzIHRoZSBsb2Nh bC9wYXNzdGVzdCBzY3JpcHQgdXNlZCBpbiB0aGUgYWJvdmUgZXhhbXBsZS4N Cg0KIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIw0KIyBGdXJ0 aGVyIEluZm9ybWF0aW9uDQojDQojICBTZWUgdGhlIHNubXBkLmNvbmYgbWFu dWFsIHBhZ2UsIGFuZCB0aGUgb3V0cHV0IG9mICJzbm1wZCAtSCIuDQojICBN VUNIIG1vcmUgY2FuIGJlIGRvbmUgd2l0aCB0aGUgc25tcGQuY29uZiB0aGFu IGlzIHNob3duIGFzIGFuDQojICBleGFtcGxlIGhlcmUuDQo= --0-840846285-1000765110=:69881-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 15:25:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta2-rme.xtra.co.nz (mta2-rme.xtra.co.nz [203.96.92.3]) by hub.freebsd.org (Postfix) with ESMTP id 9D7BC37B403 for ; Mon, 17 Sep 2001 15:25:37 -0700 (PDT) Received: from development.wgtn.csg.co.nz ([210.86.1.68]) by mta2-rme.xtra.co.nz with SMTP id <20010917222536.IJCP2668682.mta2-rme.xtra.co.nz@development.wgtn.csg.co.nz>; Tue, 18 Sep 2001 10:25:36 +1200 Content-Type: text/plain; charset="iso-8859-1" From: David Preece Reply-To: davep@afterswish.com To: Dan Nelson Subject: Re: Fwd: MTU table? Date: Tue, 18 Sep 2001 10:25:51 +1200 X-Mailer: KMail [version 1.2] References: <01091809402216.83234@development.wgtn.csg.co.nz> <20010917164742.A13516@dan.emsphone.com> In-Reply-To: <20010917164742.A13516@dan.emsphone.com> Cc: freebsd-hackers@freebsd.org MIME-Version: 1.0 Message-Id: <01091810255119.83234@development.wgtn.csg.co.nz> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 18 Sep 2001 09:47, you wrote: > If "route get " shows an MTU of 576, "route delete > " should clear it. Yeah, that does it a treat. Thanks, Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 15:28:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id ED71C37B403; Mon, 17 Sep 2001 15:27:55 -0700 (PDT) Received: from chojin (chojin.lan.tarakan-network.com [192.168.69.2] (may be forged)) by tarakan-network.com (8.11.6/8.11.3) with SMTP id f8HMRmt81561; Tue, 18 Sep 2001 00:27:48 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <017001c13fc7$fd0b1bd0$0245a8c0@chojin> From: "Chojin" To: "Joe Clarke" Cc: "Jean-Francois Dive" , , References: <20010917181428.Q69881-200000@shumai.marcuscom.com> Subject: Re: Problem with snmpd Date: Tue, 18 Sep 2001 00:27:51 +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 6.00.2526.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2526.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG My default location is /usr/local/share/snmp/snmpd.conf I used your file (just modified for 192.168... lan). To be sure snmpd uses the good file I used -c #/usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf #ps aux | grep snmpd root 81374 7.2 0.4 3256 2624 p0 S 12:25AM 0:00.15 /usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf #snmpwalk -v 1 localhost public system Timeout: No Response from localhost As you see, without success... ----- Original Message ----- From: "Joe Clarke" To: "Chojin" Cc: "Jean-Francois Dive" ; ; Sent: Tuesday, September 18, 2001 12:18 AM Subject: Re: Problem with snmpd > Not sure. I have snmpd 4.2.1 working perfectly on 4.3-RELEASE and > 4.4-STABLE as of an hour ago. Attached is my entire config file. I keep > it in /usr/local/lib/snmp (which is the default location). > > Joe > > On Mon, 17 Sep 2001, Chojin wrote: > > > I didn't resolved my problem. > > Even after upgraded to 4.4-stable (because there was maybe a bug in snmpd > > :-p). > > > > I don't know what I could do. > > > > ----- Original Message ----- > > From: "Chojin" > > To: "Joe Clarke" > > Cc: "Jean-Francois Dive" ; ; > > > > Sent: Wednesday, September 12, 2001 9:30 PM > > Subject: Re: Problem with snmpd > > > > > > > I tried your snmpd.conf but with no success :'( > > > ----- Original Message ----- > > > From: "Joe Clarke" > > > To: "Chojin" > > > Cc: "Jean-Francois Dive" ; > > ; > > > > > > Sent: Wednesday, September 12, 2001 8:34 PM > > > Subject: Re: Problem with snmpd > > > > > > > > > > Can you send your snmp.conf file? These are the relevant bits of mine: > > > > > > > > com2sec local localhost public > > > > com2sec localrw localhost private > > > > com2sec mynetwork 172.18.0.0/24 public > > > > com2sec mynetworkrw 172.18.0.0/24 private > > > > > > > > #### > > > > # Second, map the security names into group names: > > > > > > > > # sec.model sec.name > > > > group LocalRWGroup v1 localrw > > > > group LocalRWGroup v2c localrw > > > > group LocalRWGroup usm localrw > > > > group LocalROGroup v1 local > > > > group LocalROGroup v2c local > > > > group LocalROGroup usm local > > > > group NetROGroup v1 mynetwork > > > > group NetROGroup v2c mynetwork > > > > group NetROGroup usm mynetwork > > > > group NetRWGroup v1 mynetworkrw > > > > group NetRWGroup v2c mynetworkrw > > > > group NetRWGroup usm mynetworkrw > > > > > > > > #### > > > > # Third, create a view for us to let the groups have rights to: > > > > > > > > # incl/excl subtree mask > > > > view all included .1 80 > > > > > > > > #### > > > > # Finally, grant the 2 groups access to the 1 view with different > > > > # write permissions: > > > > > > > > # context sec.model sec.level match read write notif > > > > access LocalROGroup "" any noauth exact all none > > none > > > > access LocalRWGroup "" any noauth exact all all > > none > > > > access NetROGroup "" any noauth exact all none > > none > > > > access NetRWGroup "" any noauth exact all all > > none > > > > > > > > > > > > public@localhost does work on my machine. > > > > > > > > Joe > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > I used TMRTGCHO as community name before, but since I've got this > > > problem I > > > > > use now public. > > > > > Request from localhost or any other interface doesn't work. > > > > > I cleaned snmpd.log, restarted snmpd: > > > > > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l > > > > > /var/log/snmpd.log > > > > > > > > > > and a new one is located at http://www.tarakan-network.com/snmpd.log > > (I > > > did > > > > > a snmpwalk and snmpget for public@localhost but no success) > > > > > > > > > > ----- Original Message ----- > > > > > From: "Jean-Francois Dive" > > > > > To: "Chojin" > > > > > Sent: Wednesday, September 12, 2001 10:38 AM > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > Hi (salut) > > > > > > > > > > > > In fact, i see some successfull request with the community: > > > > > > TMRTGCHO and no attemps with the localhost one... seems pretty odd. > > > did > > > > > > you only got those requests from localhost not working ? > > > > > > > > > > > > Otherwise, purge the log file, be *sure* that no requests are > > comming > > > from > > > > > > somewhere else and resart to see some failures... > > > > > > > > > > > > JeF > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > I launched in debug mode > > > > > > > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l > > > > > > > /var/log/snmpd.log > > > > > > > I attached snmpd.log > > > > > > > There are so many informations I can't detect the problem :pp > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > From: "Jean-Francois Dive" > > > > > > > To: "Chojin" > > > > > > > Cc: ; > > > > > > > Sent: Wednesday, September 12, 2001 9:53 AM > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > i think it is possible to start the snmpd and not send it to > > > > > backgroud, > > > > > > > > and see if it does printout some error messages..Otherwise use > > the > > > > > truss > > > > > > > > command to follow the syscalls made by the daemon while > > processing > > > > > your > > > > > > > > request, this could point you to a problem.. > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > snmpd.log is empty... > > > > > > > > > > > > > > > > > > I did #netstat -an | grep 161 > > > > > > > > > udp4 0 0 *.161 *.* > > > > > > > > > > > > > > > > > > port 161 exists then it should work... > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > > To: "Chojin" > > > > > > > > > Cc: ; > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 3:21 AM > > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > So you have any traces in a log file or something similar ? > > > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > > > > > > > I have a problem with snmpd. > > > > > > > > > > > > > > > > > > > > > > In fact, one day, for unknown reason ( I didn't modify any > > > > > > > setting ), > > > > > > > > > snmpd > > > > > > > > > > > didn't work anymore: > > > > > > > > > > > When I do a snmpwalk or snmpget to public@localhost it > > > doesn't > > > > > > > respond. > > > > > > > > > > > I checked snmpd, recreated snmpd.conf and launched again > > > snmpd > > > > > > > with -c > > > > > > > > > > > and -l to be sure it uses the correct files. > > > > > > > > > > > But even if snmpd is in background process, > > > public@localhost > > > > > > > doesn't > > > > > > > > > work. > > > > > > > > > > > I don't have any firewall rule that block it. > > > > > > > > > > > > > > > > > > > > > > #snmpwalk localhost public > > > > > > > > > > > Timeout: No Response from localhost > > > > > > > > > > > #snmpget localhost public SysName > > > > > > > > > > > Timeout: No Response from localhost. > > > > > > > > > > > > > > > > > > > > > > After I upgraded my system from 4.3-STABLE to 4.4-RC, it > > > didn't > > > > > > > change > > > > > > > > > > > anything for snmpd. > > > > > > > > > > > > > > > > > > > > > > If someone has got any idea... > > > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > > > > > Chojin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 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-questions" in the body of the message > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 15:32:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from creme-brulee.marcuscom.com (rdu57-28-046.nc.rr.com [66.57.28.46]) by hub.freebsd.org (Postfix) with ESMTP id C946137B427; Mon, 17 Sep 2001 15:31:42 -0700 (PDT) Received: from shumai.marcuscom.com (shumai.marcuscom.com [192.168.1.4]) by creme-brulee.marcuscom.com (8.11.3/8.11.3) with ESMTP id f8HMU0508642; Mon, 17 Sep 2001 18:30:00 -0400 (EDT) (envelope-from marcus@marcuscom.com) Received: from localhost (marcus@localhost) by shumai.marcuscom.com (8.11.3/8.11.3) with ESMTP id f8HMVwm73525; Mon, 17 Sep 2001 18:31:58 -0400 (EDT) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: shumai.marcuscom.com: marcus owned process doing -bs Date: Mon, 17 Sep 2001 18:31:58 -0400 (EDT) From: Joe Clarke To: Chojin Cc: Jean-Francois Dive , , Subject: Re: Problem with snmpd In-Reply-To: <017001c13fc7$fd0b1bd0$0245a8c0@chojin> Message-ID: <20010917183033.Q69881-100000@shumai.marcuscom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG What does netstat -a and ifconfig -a show? Something is not right on your machine. I compiled /usr/ports/net/net-snmp and it worked out of the box. I'm using the default /usr/local/etc/rc.d/snmpd.sh script to start snmpd. Joe On Tue, 18 Sep 2001, Chojin wrote: > My default location is /usr/local/share/snmp/snmpd.conf > I used your file (just modified for 192.168... lan). > To be sure snmpd uses the good file I used -c > #/usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf > #ps aux | grep snmpd > root 81374 7.2 0.4 3256 2624 p0 S 12:25AM 0:00.15 > /usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf > #snmpwalk -v 1 localhost public system > Timeout: No Response from localhost > > As you see, without success... > > ----- Original Message ----- > From: "Joe Clarke" > To: "Chojin" > Cc: "Jean-Francois Dive" ; ; > > Sent: Tuesday, September 18, 2001 12:18 AM > Subject: Re: Problem with snmpd > > > > Not sure. I have snmpd 4.2.1 working perfectly on 4.3-RELEASE and > > 4.4-STABLE as of an hour ago. Attached is my entire config file. I keep > > it in /usr/local/lib/snmp (which is the default location). > > > > Joe > > > > On Mon, 17 Sep 2001, Chojin wrote: > > > > > I didn't resolved my problem. > > > Even after upgraded to 4.4-stable (because there was maybe a bug in > snmpd > > > :-p). > > > > > > I don't know what I could do. > > > > > > ----- Original Message ----- > > > From: "Chojin" > > > To: "Joe Clarke" > > > Cc: "Jean-Francois Dive" ; > ; > > > > > > Sent: Wednesday, September 12, 2001 9:30 PM > > > Subject: Re: Problem with snmpd > > > > > > > > > > I tried your snmpd.conf but with no success :'( > > > > ----- Original Message ----- > > > > From: "Joe Clarke" > > > > To: "Chojin" > > > > Cc: "Jean-Francois Dive" ; > > > ; > > > > > > > > Sent: Wednesday, September 12, 2001 8:34 PM > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > Can you send your snmp.conf file? These are the relevant bits of > mine: > > > > > > > > > > com2sec local localhost public > > > > > com2sec localrw localhost private > > > > > com2sec mynetwork 172.18.0.0/24 public > > > > > com2sec mynetworkrw 172.18.0.0/24 private > > > > > > > > > > #### > > > > > # Second, map the security names into group names: > > > > > > > > > > # sec.model sec.name > > > > > group LocalRWGroup v1 localrw > > > > > group LocalRWGroup v2c localrw > > > > > group LocalRWGroup usm localrw > > > > > group LocalROGroup v1 local > > > > > group LocalROGroup v2c local > > > > > group LocalROGroup usm local > > > > > group NetROGroup v1 mynetwork > > > > > group NetROGroup v2c mynetwork > > > > > group NetROGroup usm mynetwork > > > > > group NetRWGroup v1 mynetworkrw > > > > > group NetRWGroup v2c mynetworkrw > > > > > group NetRWGroup usm mynetworkrw > > > > > > > > > > #### > > > > > # Third, create a view for us to let the groups have rights to: > > > > > > > > > > # incl/excl subtree mask > > > > > view all included .1 80 > > > > > > > > > > #### > > > > > # Finally, grant the 2 groups access to the 1 view with different > > > > > # write permissions: > > > > > > > > > > # context sec.model sec.level match read write > notif > > > > > access LocalROGroup "" any noauth exact all none > > > none > > > > > access LocalRWGroup "" any noauth exact all all > > > none > > > > > access NetROGroup "" any noauth exact all none > > > none > > > > > access NetRWGroup "" any noauth exact all all > > > none > > > > > > > > > > > > > > > public@localhost does work on my machine. > > > > > > > > > > Joe > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > I used TMRTGCHO as community name before, but since I've got this > > > > problem I > > > > > > use now public. > > > > > > Request from localhost or any other interface doesn't work. > > > > > > I cleaned snmpd.log, restarted snmpd: > > > > > > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l > > > > > > /var/log/snmpd.log > > > > > > > > > > > > and a new one is located at > http://www.tarakan-network.com/snmpd.log > > > (I > > > > did > > > > > > a snmpwalk and snmpget for public@localhost but no success) > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Jean-Francois Dive" > > > > > > To: "Chojin" > > > > > > Sent: Wednesday, September 12, 2001 10:38 AM > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > Hi (salut) > > > > > > > > > > > > > > In fact, i see some successfull request with the community: > > > > > > > TMRTGCHO and no attemps with the localhost one... seems pretty > odd. > > > > did > > > > > > > you only got those requests from localhost not working ? > > > > > > > > > > > > > > Otherwise, purge the log file, be *sure* that no requests are > > > comming > > > > from > > > > > > > somewhere else and resart to see some failures... > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > I launched in debug mode > > > > > > > > #/usr/local/sbin/snmpd -D -c > /usr/local/share/snmp/snmpd.conf -l > > > > > > > > /var/log/snmpd.log > > > > > > > > I attached snmpd.log > > > > > > > > There are so many informations I can't detect the problem :pp > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > To: "Chojin" > > > > > > > > Cc: ; > > > > > > > > > Sent: Wednesday, September 12, 2001 9:53 AM > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > i think it is possible to start the snmpd and not send it to > > > > > > backgroud, > > > > > > > > > and see if it does printout some error messages..Otherwise > use > > > the > > > > > > truss > > > > > > > > > command to follow the syscalls made by the daemon while > > > processing > > > > > > your > > > > > > > > > request, this could point you to a problem.. > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > snmpd.log is empty... > > > > > > > > > > > > > > > > > > > > I did #netstat -an | grep 161 > > > > > > > > > > udp4 0 0 *.161 *.* > > > > > > > > > > > > > > > > > > > > port 161 exists then it should work... > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > > > To: "Chojin" > > > > > > > > > > Cc: ; > > > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 3:21 AM > > > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > > > So you have any traces in a log file or something > similar ? > > > > > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > > > > > > > > > I have a problem with snmpd. > > > > > > > > > > > > > > > > > > > > > > > > In fact, one day, for unknown reason ( I didn't modify > any > > > > > > > > setting ), > > > > > > > > > > snmpd > > > > > > > > > > > > didn't work anymore: > > > > > > > > > > > > When I do a snmpwalk or snmpget to public@localhost it > > > > doesn't > > > > > > > > respond. > > > > > > > > > > > > I checked snmpd, recreated snmpd.conf and launched > again > > > > snmpd > > > > > > > > with -c > > > > > > > > > > > > and -l to be sure it uses the correct files. > > > > > > > > > > > > But even if snmpd is in background process, > > > > public@localhost > > > > > > > > doesn't > > > > > > > > > > work. > > > > > > > > > > > > I don't have any firewall rule that block it. > > > > > > > > > > > > > > > > > > > > > > > > #snmpwalk localhost public > > > > > > > > > > > > Timeout: No Response from localhost > > > > > > > > > > > > #snmpget localhost public SysName > > > > > > > > > > > > Timeout: No Response from localhost. > > > > > > > > > > > > > > > > > > > > > > > > After I upgraded my system from 4.3-STABLE to 4.4-RC, > it > > > > didn't > > > > > > > > change > > > > > > > > > > > > anything for snmpd. > > > > > > > > > > > > > > > > > > > > > > > > If someone has got any idea... > > > > > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > > > > > > > Chojin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 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-questions" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 15:36:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id 26AB037B40A; Mon, 17 Sep 2001 15:35:33 -0700 (PDT) Received: from chojin (chojin.lan.tarakan-network.com [192.168.69.2] (may be forged)) by tarakan-network.com (8.11.6/8.11.3) with SMTP id f8HMZOt82524; Tue, 18 Sep 2001 00:35:25 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <019a01c13fc9$0d56e720$0245a8c0@chojin> From: "Chojin" To: "Joe Clarke" Cc: "Jean-Francois Dive" , , References: <20010917183033.Q69881-100000@shumai.marcuscom.com> Subject: Re: Problem with snmpd Date: Tue, 18 Sep 2001 00:35:28 +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 6.00.2526.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2526.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >I compiled /usr/ports/net/net-snmp me too #netstat -a Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1618 TIME_WAIT tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1616 TIME_WAIT tcp4 0 0 chojin.adsl.neri.4110 208.141.100.35.socks TIME_WAIT tcp4 0 0 chojin.adsl.neri.4108 208.141.100.35.socks TIME_WAIT tcp4 0 0 chojin.adsl.neri.4107 208.141.100.35.socks TIME_WAIT tcp4 0 0 chojin.adsl.neri.4105 Hacker.gs.2532 SYN_SENT tcp4 0 0 chojin.adsl.neri.4103 208.141.100.35.socks TIME_WAIT tcp4 0 0 chojin.adsl.neri.4100 Hacker.gs.2532 ESTABLISHED tcp4 0 0 chojin.adsl.neri.smtp rdu57-28-046.nc..1889 TIME_WAIT tcp4 0 0 chojin.adsl.neri.4098 AFontenayssB-101.3340 SYN_SENT tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1615 TIME_WAIT tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1613 TIME_WAIT tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1612 TIME_WAIT tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1610 TIME_WAIT tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1609 TIME_WAIT tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1607 TIME_WAIT tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1606 TIME_WAIT tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1604 TIME_WAIT tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1603 TIME_WAIT tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1601 TIME_WAIT tcp4 0 0 chojin.adsl.neri.auth Hacker.gs.1628 FIN_WAIT_2 tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1597 TIME_WAIT tcp4 0 0 chojin.adsl.neri.4084 Hacker.gs.2532 FIN_WAIT_2 tcp4 0 0 chojin.adsl.neri.3832 deneb.freedomshe.4386 ESTABLISHED tcp4 0 0 chojin.adsl.neri.3682 deneb.freedomshe.4969 ESTABLISHED tcp4 0 0 tarakan.lan.tara.netbi chojin.lan.tarak.1299 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1742 ACBD133F.ipt.aol.1031 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1809 aboukir-101-1-4-.5557 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1493 paris.fr.eu.unde.6667 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1481 undernet.span.ch.6667 ESTABLISHED tcp4 0 0 *.http *.* LISTEN tcp4 0 0 chojin.adsl.neri.4950 arne.swip.net.6669 ESTABLISHED tcp4 0 0 chojin.adsl.neri.4730 no-security.net.8367 ESTABLISHED tcp4 0 0 chojin.adsl.neri.4540 irc.carrier1.net.6667 ESTABLISHED tcp4 0 0 tarakan.lan.tara.ssh chojin.lan.tarak.2099 ESTABLISHED tcp4 0 0 chojin.adsl.neri.3145 ACBE8C24.ipt.aol.3419 ESTABLISHED tcp4 0 55 tarakan.lan.tara.22006 chojin.lan.tarak.1980 ESTABLISHED tcp4 0 0 chojin.adsl.neri.3070 entrechat.net.6667 ESTABLISHED tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36867 ESTABLISHED tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36875 ESTABLISHED tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36870 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1657 skippy.solidshel.2843 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1390 entrechat.net.6668 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1380 powertech.no.eu..afs3- ESTABLISHED tcp4 0 0 chojin.adsl.neri.1379 uu194-7-27-98.un.8080 ESTABLISHED tcp4 0 0 chojin.adsl.neri.4267 chojin.adsl.neri.1373 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1373 chojin.adsl.neri.4267 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1742 *.* LISTEN tcp4 0 0 chojin.adsl.neri.3337 chojin.adsl.neri.1254 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1254 chojin.adsl.neri.3337 ESTABLISHED tcp4 0 0 chojin.adsl.neri.3337 208.141.100.35.30790 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1208 208.141.100.35.socks ESTABLISHED tcp4 0 0 chojin.adsl.neri.1204 208.141.100.35.socks ESTABLISHED tcp4 0 0 *.3331 *.* LISTEN tcp4 0 0 chojin.adsl.neri.1198 skippy.solidshel.2843 ESTABLISHED tcp4 0 0 chojin.adsl.neri.dec-n *.* LISTEN tcp4 0 0 chojin.adsl.neri.3337 NS1.ipvh.2787 ESTABLISHED tcp4 0 0 chojin.adsl.neri.3337 NS1.ipvh.2778 ESTABLISHED tcp4 0 0 chojin.adsl.neri.3337 box1.TyranZ.3847 ESTABLISHED tcp4 0 0 *.3337 *.* LISTEN tcp4 0 0 chojin.adsl.neri.1112 skippy.solidshel.2843 ESTABLISHED tcp4 0 0 chojin.adsl.neri.domai *.* LISTEN tcp4 0 0 chojin.adsl.neri.1084 TyranZ.20801 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1080 ircnet.kaptech.6667 ESTABLISHED tcp4 0 0 tarakan.lan.tara.6667 tarakan.lan.tara.1072 ESTABLISHED tcp4 0 0 tarakan.lan.tara.1072 tarakan.lan.tara.6667 ESTABLISHED tcp4 0 0 *.2211 *.* LISTEN tcp4 0 0 chojin.adsl.neri.1065 AVelizy-101-2-2-.1982 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1063 irc1-2.free.fr.6667 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1062 hitomi.ecranbleu.dec-n ESTABLISHED tcp4 0 0 *.12345 *.* LISTEN tcp4 0 0 chojin.adsl.neri.3682 vega.freedomshel.1534 ESTABLISHED tcp4 0 0 chojin.adsl.neri.3682 vega.freedomshel.1524 ESTABLISHED tcp4 0 0 *.22011 *.* LISTEN tcp4 0 48 tarakan.lan.tara.ssh chojin.lan.tarak.1164 ESTABLISHED tcp4 0 0 tarakan.lan.tara.6667 tarakan.lan.tara.1048 ESTABLISHED tcp4 0 0 tarakan.lan.tara.1048 tarakan.lan.tara.6667 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1047 www.skydirect.ne.6667 ESTABLISHED tcp4 0 0 tarakan.lan.tara.4400 tarakan.lan.tara.1042 ESTABLISHED tcp4 0 0 tarakan.lan.tara.1042 tarakan.lan.tara.4400 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1041 bloob.oxyd.fr.4400 ESTABLISHED tcp4 0 0 *.4400 *.* LISTEN tcp4 0 0 *.6669 *.* LISTEN tcp4 0 0 *.6668 *.* LISTEN tcp4 0 0 *.6667 *.* LISTEN tcp4 0 0 *.6665 *.* LISTEN tcp4 0 0 *.6666 *.* LISTEN tcp4 0 0 *.4401 *.* LISTEN tcp4 0 0 *.13333 *.* LISTEN tcp4 0 0 chojin.adsl.neri.1035 rinka.nerim.net.6667 ESTABLISHED tcp4 0 0 chojin.adsl.neri.3682 chojin.adsl.neri.1032 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1032 chojin.adsl.neri.3682 ESTABLISHED tcp4 0 0 chojin.adsl.neri.1031 irc.planetintern.6667 ESTABLISHED tcp4 0 0 tarakan.lan.tara.21003 chojin.lan.tarak.1163 ESTABLISHED tcp4 0 0 tarakan.lan.tara.22002 chojin.lan.tarak.1162 ESTABLISHED tcp4 0 0 chojin.adsl.neri.2532 *.* LISTEN tcp4 0 0 chojin.adsl.neri.4695 *.* LISTEN tcp4 0 0 chojin.adsl.neri.3418 *.* LISTEN tcp4 0 0 chojin.adsl.neri.4267 *.* LISTEN tcp4 0 0 chojin.adsl.neri.6632 *.* LISTEN tcp4 0 0 chojin.adsl.neri.3682 *.* LISTEN tcp4 0 0 *.netbios-ssn *.* LISTEN tcp46 0 0 *.22005 *.* LISTEN tcp4 0 0 *.22005 *.* LISTEN tcp46 0 0 *.22006 *.* LISTEN tcp46 0 0 *.22002 *.* LISTEN tcp4 0 0 *.22006 *.* LISTEN tcp46 0 0 *.21003 *.* LISTEN tcp4 0 0 *.21003 *.* LISTEN tcp4 0 0 *.22002 *.* LISTEN tcp4 0 0 tarakan.lan.tara.11982 *.* LISTEN tcp46 0 0 *.auth *.* LISTEN tcp4 0 0 *.submission *.* LISTEN tcp4 0 0 *.smtp *.* LISTEN tcp4 0 0 *.ssh *.* LISTEN tcp46 0 0 *.ssh *.* LISTEN tcp4 0 0 *.swat *.* LISTEN tcp4 0 0 *.auth *.* LISTEN tcp4 0 0 *.pop3 *.* LISTEN tcp6 0 0 *.ftp *.* LISTEN tcp4 0 0 *.ftp *.* LISTEN tcp4 0 0 *.sunrpc *.* LISTEN tcp4 0 0 localhost.domain *.* LISTEN tcp4 0 0 tarakan.lan.tara.domai *.* LISTEN tcp4 0 0 modem-adsl.domain *.* LISTEN udp4 0 0 *.4659 *.* udp4 0 0 *.snmp *.* udp4 0 0 localhost.3336 *.* udp4 0 0 *.3704 *.* udp4 0 0 *.2409 *.* udp4 0 0 chojin.adsl.neri.domai *.* udp4 0 0 *.1488 *.* udp4 0 0 *.* *.* udp4 0 0 *.1380 *.* udp4 0 0 *.afs3-bos *.* udp4 0 0 *.4183 *.* udp4 0 0 *.1291 *.* udp4 0 0 *.1244 *.* udp4 0 0 tarakan.lan.tara.netbi *.* udp4 0 0 tarakan.lan.tara.netbi *.* udp4 0 0 *.netbios-dgm *.* udp4 0 0 *.netbios-ns *.* udp4 0 0 *.10000 *.* udp4 0 0 chojin.adsl.neri.1124 chojin.adsl.neri.syslo udp4 0 0 *.bootps *.* udp4 0 0 *.sunrpc *.* udp4 0 0 *.1028 *.* udp4 0 0 localhost.domain *.* udp4 0 0 tarakan.lan.tara.domai *.* udp4 0 0 modem-adsl.domain *.* udp4 0 0 *.syslog *.* udp6 0 0 *.syslog *.* ip 4 0 0 *.* *.* icm4 0 0 *.* *.* ip64 0 0 *.* *.* Netgraph sockets Type Recv-Q Send-Q Node Address #Hooks ctrl 0 0 data 0 0 Active UNIX domain sockets Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr d04c2d80 stream 0 0 d04f9580 0 0 0 /var/pwcheck/pwcheck d04c2e40 stream 0 0 d04f7240 0 0 0 /tmp/.s.PGSQL.5432 d04c2f40 stream 0 0 d04bd800 0 0 0 /var/run/ndc d04c2d00 dgram 0 0 0 d04c2fc0 0 d04c2c80 d04c2c80 dgram 0 0 0 d04c2fc0 0 d04c2e00 d04c2e00 dgram 0 0 0 d04c2fc0 0 d04c2dc0 d04c2dc0 dgram 0 0 0 d04c2fc0 0 d04c2e80 d04c2e80 dgram 0 0 0 d04c2fc0 0 d04c2ec0 d04c2ec0 dgram 0 0 0 d04c2fc0 0 d04c2f00 d04c2f00 dgram 0 0 0 d04c2fc0 0 d04c2f80 d04c2f80 dgram 0 0 0 d04c2fc0 0 0 d04c2fc0 dgram 0 0 d04be940 0 d04c2d00 0 /var/run/log #ifconfig -a ed0: flags=8843 mtu 1500 inet 10.0.0.10 netmask 0xffffff00 broadcast 10.0.0.255 inet6 fe80::24f:49ff:fe0a:b2dd%ed0 prefixlen 64 scopeid 0x1 ether 00:4f:49:0a:b2:dd ed1: flags=8843 mtu 1500 inet 192.168.69.1 netmask 0xffffff00 broadcast 192.168.69.255 inet6 fe80::5054:5ff:fef9:761d%ed1 prefixlen 64 scopeid 0x2 ether 52:54:05:f9:76:1d lp0: flags=8810 mtu 1500 faith0: flags=8000 mtu 1500 stf0: flags=0<> mtu 1280 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet 127.0.0.1 netmask 0xff000000 ppp0: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 tun0: flags=8051 mtu 1492 inet6 fe80::24f:49ff:fe0a:b2dd%tun0 prefixlen 64 scopeid 0x9 inet 62.4.22.98 --> 194.206.78.3 netmask 0xff000000 Opened by PID 168 Anything wrong? ----- Original Message ----- From: "Joe Clarke" To: "Chojin" Cc: "Jean-Francois Dive" ; ; Sent: Tuesday, September 18, 2001 12:31 AM Subject: Re: Problem with snmpd > What does netstat -a and ifconfig -a show? Something is not right on your > machine. I compiled /usr/ports/net/net-snmp and it worked out of the box. > I'm using the default /usr/local/etc/rc.d/snmpd.sh script to start snmpd. > > Joe > > On Tue, 18 Sep 2001, Chojin wrote: > > > My default location is /usr/local/share/snmp/snmpd.conf > > I used your file (just modified for 192.168... lan). > > To be sure snmpd uses the good file I used -c > > #/usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf > > #ps aux | grep snmpd > > root 81374 7.2 0.4 3256 2624 p0 S 12:25AM 0:00.15 > > /usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf > > #snmpwalk -v 1 localhost public system > > Timeout: No Response from localhost > > > > As you see, without success... > > > > ----- Original Message ----- > > From: "Joe Clarke" > > To: "Chojin" > > Cc: "Jean-Francois Dive" ; ; > > > > Sent: Tuesday, September 18, 2001 12:18 AM > > Subject: Re: Problem with snmpd > > > > > > > Not sure. I have snmpd 4.2.1 working perfectly on 4.3-RELEASE and > > > 4.4-STABLE as of an hour ago. Attached is my entire config file. I keep > > > it in /usr/local/lib/snmp (which is the default location). > > > > > > Joe > > > > > > On Mon, 17 Sep 2001, Chojin wrote: > > > > > > > I didn't resolved my problem. > > > > Even after upgraded to 4.4-stable (because there was maybe a bug in > > snmpd > > > > :-p). > > > > > > > > I don't know what I could do. > > > > > > > > ----- Original Message ----- > > > > From: "Chojin" > > > > To: "Joe Clarke" > > > > Cc: "Jean-Francois Dive" ; > > ; > > > > > > > > Sent: Wednesday, September 12, 2001 9:30 PM > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > I tried your snmpd.conf but with no success :'( > > > > > ----- Original Message ----- > > > > > From: "Joe Clarke" > > > > > To: "Chojin" > > > > > Cc: "Jean-Francois Dive" ; > > > > ; > > > > > > > > > > Sent: Wednesday, September 12, 2001 8:34 PM > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > Can you send your snmp.conf file? These are the relevant bits of > > mine: > > > > > > > > > > > > com2sec local localhost public > > > > > > com2sec localrw localhost private > > > > > > com2sec mynetwork 172.18.0.0/24 public > > > > > > com2sec mynetworkrw 172.18.0.0/24 private > > > > > > > > > > > > #### > > > > > > # Second, map the security names into group names: > > > > > > > > > > > > # sec.model sec.name > > > > > > group LocalRWGroup v1 localrw > > > > > > group LocalRWGroup v2c localrw > > > > > > group LocalRWGroup usm localrw > > > > > > group LocalROGroup v1 local > > > > > > group LocalROGroup v2c local > > > > > > group LocalROGroup usm local > > > > > > group NetROGroup v1 mynetwork > > > > > > group NetROGroup v2c mynetwork > > > > > > group NetROGroup usm mynetwork > > > > > > group NetRWGroup v1 mynetworkrw > > > > > > group NetRWGroup v2c mynetworkrw > > > > > > group NetRWGroup usm mynetworkrw > > > > > > > > > > > > #### > > > > > > # Third, create a view for us to let the groups have rights to: > > > > > > > > > > > > # incl/excl subtree mask > > > > > > view all included .1 80 > > > > > > > > > > > > #### > > > > > > # Finally, grant the 2 groups access to the 1 view with different > > > > > > # write permissions: > > > > > > > > > > > > # context sec.model sec.level match read write > > notif > > > > > > access LocalROGroup "" any noauth exact all none > > > > none > > > > > > access LocalRWGroup "" any noauth exact all all > > > > none > > > > > > access NetROGroup "" any noauth exact all none > > > > none > > > > > > access NetRWGroup "" any noauth exact all all > > > > none > > > > > > > > > > > > > > > > > > public@localhost does work on my machine. > > > > > > > > > > > > Joe > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > I used TMRTGCHO as community name before, but since I've got this > > > > > problem I > > > > > > > use now public. > > > > > > > Request from localhost or any other interface doesn't work. > > > > > > > I cleaned snmpd.log, restarted snmpd: > > > > > > > #/usr/local/sbin/snmpd -D -c /usr/local/share/snmp/snmpd.conf -l > > > > > > > /var/log/snmpd.log > > > > > > > > > > > > > > and a new one is located at > > http://www.tarakan-network.com/snmpd.log > > > > (I > > > > > did > > > > > > > a snmpwalk and snmpget for public@localhost but no success) > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > From: "Jean-Francois Dive" > > > > > > > To: "Chojin" > > > > > > > Sent: Wednesday, September 12, 2001 10:38 AM > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > Hi (salut) > > > > > > > > > > > > > > > > In fact, i see some successfull request with the community: > > > > > > > > TMRTGCHO and no attemps with the localhost one... seems pretty > > odd. > > > > > did > > > > > > > > you only got those requests from localhost not working ? > > > > > > > > > > > > > > > > Otherwise, purge the log file, be *sure* that no requests are > > > > comming > > > > > from > > > > > > > > somewhere else and resart to see some failures... > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > I launched in debug mode > > > > > > > > > #/usr/local/sbin/snmpd -D -c > > /usr/local/share/snmp/snmpd.conf -l > > > > > > > > > /var/log/snmpd.log > > > > > > > > > I attached snmpd.log > > > > > > > > > There are so many informations I can't detect the problem :pp > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > > To: "Chojin" > > > > > > > > > Cc: ; > > > > > > > > > > > Sent: Wednesday, September 12, 2001 9:53 AM > > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > > > > i think it is possible to start the snmpd and not send it to > > > > > > > backgroud, > > > > > > > > > > and see if it does printout some error messages..Otherwise > > use > > > > the > > > > > > > truss > > > > > > > > > > command to follow the syscalls made by the daemon while > > > > processing > > > > > > > your > > > > > > > > > > request, this could point you to a problem.. > > > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > > > snmpd.log is empty... > > > > > > > > > > > > > > > > > > > > > > I did #netstat -an | grep 161 > > > > > > > > > > > udp4 0 0 *.161 *.* > > > > > > > > > > > > > > > > > > > > > > port 161 exists then it should work... > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > > > > To: "Chojin" > > > > > > > > > > > Cc: ; > > > > > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 3:21 AM > > > > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > > > > > So you have any traces in a log file or something > > similar ? > > > > > > > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > > > > > > > > > > > I have a problem with snmpd. > > > > > > > > > > > > > > > > > > > > > > > > > > In fact, one day, for unknown reason ( I didn't modify > > any > > > > > > > > > setting ), > > > > > > > > > > > snmpd > > > > > > > > > > > > > didn't work anymore: > > > > > > > > > > > > > When I do a snmpwalk or snmpget to public@localhost it > > > > > doesn't > > > > > > > > > respond. > > > > > > > > > > > > > I checked snmpd, recreated snmpd.conf and launched > > again > > > > > snmpd > > > > > > > > > with -c > > > > > > > > > > > > > and -l to be sure it uses the correct files. > > > > > > > > > > > > > But even if snmpd is in background process, > > > > > public@localhost > > > > > > > > > doesn't > > > > > > > > > > > work. > > > > > > > > > > > > > I don't have any firewall rule that block it. > > > > > > > > > > > > > > > > > > > > > > > > > > #snmpwalk localhost public > > > > > > > > > > > > > Timeout: No Response from localhost > > > > > > > > > > > > > #snmpget localhost public SysName > > > > > > > > > > > > > Timeout: No Response from localhost. > > > > > > > > > > > > > > > > > > > > > > > > > > After I upgraded my system from 4.3-STABLE to 4.4-RC, > > it > > > > > didn't > > > > > > > > > change > > > > > > > > > > > > > anything for snmpd. > > > > > > > > > > > > > > > > > > > > > > > > > > If someone has got any idea... > > > > > > > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > > > > > > > > > Chojin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 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-questions" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 15:41:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from creme-brulee.marcuscom.com (rdu57-28-046.nc.rr.com [66.57.28.46]) by hub.freebsd.org (Postfix) with ESMTP id C8A6F37B412; Mon, 17 Sep 2001 15:40:17 -0700 (PDT) Received: from shumai.marcuscom.com (shumai.marcuscom.com [192.168.1.4]) by creme-brulee.marcuscom.com (8.11.3/8.11.3) with ESMTP id f8HMcY508701; Mon, 17 Sep 2001 18:38:35 -0400 (EDT) (envelope-from marcus@marcuscom.com) Received: from localhost (marcus@localhost) by shumai.marcuscom.com (8.11.3/8.11.3) with ESMTP id f8HMeXr73560; Mon, 17 Sep 2001 18:40:33 -0400 (EDT) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: shumai.marcuscom.com: marcus owned process doing -bs Date: Mon, 17 Sep 2001 18:40:33 -0400 (EDT) From: Joe Clarke To: Chojin Cc: Jean-Francois Dive , , Subject: Re: Problem with snmpd In-Reply-To: <019a01c13fc9$0d56e720$0245a8c0@chojin> Message-ID: <20010917183916.L69881-100000@shumai.marcuscom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Those look fine. What about nslookup localhost (or if you're using hosts before bind, what does /etc/hosts look like)? It may be that localhost resolves to something other than 127.0.0.1. Have you tried: snmpwalk 127.0.0.1 public system ? That should also work. Joe On Tue, 18 Sep 2001, Chojin wrote: > >I compiled /usr/ports/net/net-snmp > me too > > #netstat -a > Active Internet connections (including servers) > Proto Recv-Q Send-Q Local Address Foreign Address (state) > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1618 TIME_WAIT > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1616 TIME_WAIT > tcp4 0 0 chojin.adsl.neri.4110 208.141.100.35.socks TIME_WAIT > tcp4 0 0 chojin.adsl.neri.4108 208.141.100.35.socks TIME_WAIT > tcp4 0 0 chojin.adsl.neri.4107 208.141.100.35.socks TIME_WAIT > tcp4 0 0 chojin.adsl.neri.4105 Hacker.gs.2532 SYN_SENT > tcp4 0 0 chojin.adsl.neri.4103 208.141.100.35.socks TIME_WAIT > tcp4 0 0 chojin.adsl.neri.4100 Hacker.gs.2532 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.smtp rdu57-28-046.nc..1889 TIME_WAIT > tcp4 0 0 chojin.adsl.neri.4098 AFontenayssB-101.3340 SYN_SENT > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1615 TIME_WAIT > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1613 TIME_WAIT > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1612 TIME_WAIT > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1610 TIME_WAIT > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1609 TIME_WAIT > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1607 TIME_WAIT > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1606 TIME_WAIT > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1604 TIME_WAIT > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1603 TIME_WAIT > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1601 TIME_WAIT > tcp4 0 0 chojin.adsl.neri.auth Hacker.gs.1628 > FIN_WAIT_2 > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1597 TIME_WAIT > tcp4 0 0 chojin.adsl.neri.4084 Hacker.gs.2532 > FIN_WAIT_2 > tcp4 0 0 chojin.adsl.neri.3832 deneb.freedomshe.4386 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.3682 deneb.freedomshe.4969 > ESTABLISHED > tcp4 0 0 tarakan.lan.tara.netbi chojin.lan.tarak.1299 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1742 ACBD133F.ipt.aol.1031 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1809 aboukir-101-1-4-.5557 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1493 paris.fr.eu.unde.6667 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1481 undernet.span.ch.6667 > ESTABLISHED > tcp4 0 0 *.http *.* LISTEN > tcp4 0 0 chojin.adsl.neri.4950 arne.swip.net.6669 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.4730 no-security.net.8367 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.4540 irc.carrier1.net.6667 > ESTABLISHED > tcp4 0 0 tarakan.lan.tara.ssh chojin.lan.tarak.2099 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.3145 ACBE8C24.ipt.aol.3419 > ESTABLISHED > tcp4 0 55 tarakan.lan.tara.22006 chojin.lan.tarak.1980 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.3070 entrechat.net.6667 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36867 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36875 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36870 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1657 skippy.solidshel.2843 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1390 entrechat.net.6668 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1380 powertech.no.eu..afs3- > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1379 uu194-7-27-98.un.8080 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.4267 chojin.adsl.neri.1373 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1373 chojin.adsl.neri.4267 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1742 *.* LISTEN > tcp4 0 0 chojin.adsl.neri.3337 chojin.adsl.neri.1254 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1254 chojin.adsl.neri.3337 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.3337 208.141.100.35.30790 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1208 208.141.100.35.socks > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1204 208.141.100.35.socks > ESTABLISHED > tcp4 0 0 *.3331 *.* LISTEN > tcp4 0 0 chojin.adsl.neri.1198 skippy.solidshel.2843 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.dec-n *.* LISTEN > tcp4 0 0 chojin.adsl.neri.3337 NS1.ipvh.2787 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.3337 NS1.ipvh.2778 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.3337 box1.TyranZ.3847 > ESTABLISHED > tcp4 0 0 *.3337 *.* LISTEN > tcp4 0 0 chojin.adsl.neri.1112 skippy.solidshel.2843 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.domai *.* LISTEN > tcp4 0 0 chojin.adsl.neri.1084 TyranZ.20801 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1080 ircnet.kaptech.6667 > ESTABLISHED > tcp4 0 0 tarakan.lan.tara.6667 tarakan.lan.tara.1072 > ESTABLISHED > tcp4 0 0 tarakan.lan.tara.1072 tarakan.lan.tara.6667 > ESTABLISHED > tcp4 0 0 *.2211 *.* LISTEN > tcp4 0 0 chojin.adsl.neri.1065 AVelizy-101-2-2-.1982 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1063 irc1-2.free.fr.6667 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1062 hitomi.ecranbleu.dec-n > ESTABLISHED > tcp4 0 0 *.12345 *.* LISTEN > tcp4 0 0 chojin.adsl.neri.3682 vega.freedomshel.1534 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.3682 vega.freedomshel.1524 > ESTABLISHED > tcp4 0 0 *.22011 *.* LISTEN > tcp4 0 48 tarakan.lan.tara.ssh chojin.lan.tarak.1164 > ESTABLISHED > tcp4 0 0 tarakan.lan.tara.6667 tarakan.lan.tara.1048 > ESTABLISHED > tcp4 0 0 tarakan.lan.tara.1048 tarakan.lan.tara.6667 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1047 www.skydirect.ne.6667 > ESTABLISHED > tcp4 0 0 tarakan.lan.tara.4400 tarakan.lan.tara.1042 > ESTABLISHED > tcp4 0 0 tarakan.lan.tara.1042 tarakan.lan.tara.4400 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1041 bloob.oxyd.fr.4400 > ESTABLISHED > tcp4 0 0 *.4400 *.* LISTEN > tcp4 0 0 *.6669 *.* LISTEN > tcp4 0 0 *.6668 *.* LISTEN > tcp4 0 0 *.6667 *.* LISTEN > tcp4 0 0 *.6665 *.* LISTEN > tcp4 0 0 *.6666 *.* LISTEN > tcp4 0 0 *.4401 *.* LISTEN > tcp4 0 0 *.13333 *.* LISTEN > tcp4 0 0 chojin.adsl.neri.1035 rinka.nerim.net.6667 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.3682 chojin.adsl.neri.1032 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1032 chojin.adsl.neri.3682 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.1031 irc.planetintern.6667 > ESTABLISHED > tcp4 0 0 tarakan.lan.tara.21003 chojin.lan.tarak.1163 > ESTABLISHED > tcp4 0 0 tarakan.lan.tara.22002 chojin.lan.tarak.1162 > ESTABLISHED > tcp4 0 0 chojin.adsl.neri.2532 *.* LISTEN > tcp4 0 0 chojin.adsl.neri.4695 *.* LISTEN > tcp4 0 0 chojin.adsl.neri.3418 *.* LISTEN > tcp4 0 0 chojin.adsl.neri.4267 *.* LISTEN > tcp4 0 0 chojin.adsl.neri.6632 *.* LISTEN > tcp4 0 0 chojin.adsl.neri.3682 *.* LISTEN > tcp4 0 0 *.netbios-ssn *.* LISTEN > tcp46 0 0 *.22005 *.* LISTEN > tcp4 0 0 *.22005 *.* LISTEN > tcp46 0 0 *.22006 *.* LISTEN > tcp46 0 0 *.22002 *.* LISTEN > tcp4 0 0 *.22006 *.* LISTEN > tcp46 0 0 *.21003 *.* LISTEN > tcp4 0 0 *.21003 *.* LISTEN > tcp4 0 0 *.22002 *.* LISTEN > tcp4 0 0 tarakan.lan.tara.11982 *.* LISTEN > tcp46 0 0 *.auth *.* LISTEN > tcp4 0 0 *.submission *.* LISTEN > tcp4 0 0 *.smtp *.* LISTEN > tcp4 0 0 *.ssh *.* LISTEN > tcp46 0 0 *.ssh *.* LISTEN > tcp4 0 0 *.swat *.* LISTEN > tcp4 0 0 *.auth *.* LISTEN > tcp4 0 0 *.pop3 *.* LISTEN > tcp6 0 0 *.ftp *.* LISTEN > tcp4 0 0 *.ftp *.* LISTEN > tcp4 0 0 *.sunrpc *.* LISTEN > tcp4 0 0 localhost.domain *.* LISTEN > tcp4 0 0 tarakan.lan.tara.domai *.* LISTEN > tcp4 0 0 modem-adsl.domain *.* LISTEN > udp4 0 0 *.4659 *.* > udp4 0 0 *.snmp *.* > udp4 0 0 localhost.3336 *.* > udp4 0 0 *.3704 *.* > udp4 0 0 *.2409 *.* > udp4 0 0 chojin.adsl.neri.domai *.* > udp4 0 0 *.1488 *.* > udp4 0 0 *.* *.* > udp4 0 0 *.1380 *.* > udp4 0 0 *.afs3-bos *.* > udp4 0 0 *.4183 *.* > udp4 0 0 *.1291 *.* > udp4 0 0 *.1244 *.* > udp4 0 0 tarakan.lan.tara.netbi *.* > udp4 0 0 tarakan.lan.tara.netbi *.* > udp4 0 0 *.netbios-dgm *.* > udp4 0 0 *.netbios-ns *.* > udp4 0 0 *.10000 *.* > udp4 0 0 chojin.adsl.neri.1124 chojin.adsl.neri.syslo > udp4 0 0 *.bootps *.* > udp4 0 0 *.sunrpc *.* > udp4 0 0 *.1028 *.* > udp4 0 0 localhost.domain *.* > udp4 0 0 tarakan.lan.tara.domai *.* > udp4 0 0 modem-adsl.domain *.* > udp4 0 0 *.syslog *.* > udp6 0 0 *.syslog *.* > ip 4 0 0 *.* *.* > icm4 0 0 *.* *.* > ip64 0 0 *.* *.* > Netgraph sockets > Type Recv-Q Send-Q Node Address #Hooks > ctrl 0 0 > data 0 0 > Active UNIX domain sockets > Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr > d04c2d80 stream 0 0 d04f9580 0 0 0 > /var/pwcheck/pwcheck > d04c2e40 stream 0 0 d04f7240 0 0 0 > /tmp/.s.PGSQL.5432 > d04c2f40 stream 0 0 d04bd800 0 0 0 > /var/run/ndc > d04c2d00 dgram 0 0 0 d04c2fc0 0 d04c2c80 > d04c2c80 dgram 0 0 0 d04c2fc0 0 d04c2e00 > d04c2e00 dgram 0 0 0 d04c2fc0 0 d04c2dc0 > d04c2dc0 dgram 0 0 0 d04c2fc0 0 d04c2e80 > d04c2e80 dgram 0 0 0 d04c2fc0 0 d04c2ec0 > d04c2ec0 dgram 0 0 0 d04c2fc0 0 d04c2f00 > d04c2f00 dgram 0 0 0 d04c2fc0 0 d04c2f80 > d04c2f80 dgram 0 0 0 d04c2fc0 0 0 > d04c2fc0 dgram 0 0 d04be940 0 d04c2d00 0 > /var/run/log > > #ifconfig -a > ed0: flags=8843 mtu 1500 > inet 10.0.0.10 netmask 0xffffff00 broadcast 10.0.0.255 > inet6 fe80::24f:49ff:fe0a:b2dd%ed0 prefixlen 64 scopeid 0x1 > ether 00:4f:49:0a:b2:dd > ed1: flags=8843 mtu 1500 > inet 192.168.69.1 netmask 0xffffff00 broadcast 192.168.69.255 > inet6 fe80::5054:5ff:fef9:761d%ed1 prefixlen 64 scopeid 0x2 > ether 52:54:05:f9:76:1d > lp0: flags=8810 mtu 1500 > faith0: flags=8000 mtu 1500 > stf0: flags=0<> mtu 1280 > lo0: flags=8049 mtu 16384 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 > inet 127.0.0.1 netmask 0xff000000 > ppp0: flags=8010 mtu 1500 > sl0: flags=c010 mtu 552 > tun0: flags=8051 mtu 1492 > inet6 fe80::24f:49ff:fe0a:b2dd%tun0 prefixlen 64 scopeid 0x9 > inet 62.4.22.98 --> 194.206.78.3 netmask 0xff000000 > Opened by PID 168 > > Anything wrong? > > ----- Original Message ----- > From: "Joe Clarke" > To: "Chojin" > Cc: "Jean-Francois Dive" ; ; > > Sent: Tuesday, September 18, 2001 12:31 AM > Subject: Re: Problem with snmpd > > > > What does netstat -a and ifconfig -a show? Something is not right on your > > machine. I compiled /usr/ports/net/net-snmp and it worked out of the box. > > I'm using the default /usr/local/etc/rc.d/snmpd.sh script to start snmpd. > > > > Joe > > > > On Tue, 18 Sep 2001, Chojin wrote: > > > > > My default location is /usr/local/share/snmp/snmpd.conf > > > I used your file (just modified for 192.168... lan). > > > To be sure snmpd uses the good file I used -c > > > #/usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf > > > #ps aux | grep snmpd > > > root 81374 7.2 0.4 3256 2624 p0 S 12:25AM 0:00.15 > > > /usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf > > > #snmpwalk -v 1 localhost public system > > > Timeout: No Response from localhost > > > > > > As you see, without success... > > > > > > ----- Original Message ----- > > > From: "Joe Clarke" > > > To: "Chojin" > > > Cc: "Jean-Francois Dive" ; > ; > > > > > > Sent: Tuesday, September 18, 2001 12:18 AM > > > Subject: Re: Problem with snmpd > > > > > > > > > > Not sure. I have snmpd 4.2.1 working perfectly on 4.3-RELEASE and > > > > 4.4-STABLE as of an hour ago. Attached is my entire config file. I > keep > > > > it in /usr/local/lib/snmp (which is the default location). > > > > > > > > Joe > > > > > > > > On Mon, 17 Sep 2001, Chojin wrote: > > > > > > > > > I didn't resolved my problem. > > > > > Even after upgraded to 4.4-stable (because there was maybe a bug in > > > snmpd > > > > > :-p). > > > > > > > > > > I don't know what I could do. > > > > > > > > > > ----- Original Message ----- > > > > > From: "Chojin" > > > > > To: "Joe Clarke" > > > > > Cc: "Jean-Francois Dive" ; > > > ; > > > > > > > > > > Sent: Wednesday, September 12, 2001 9:30 PM > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > I tried your snmpd.conf but with no success :'( > > > > > > ----- Original Message ----- > > > > > > From: "Joe Clarke" > > > > > > To: "Chojin" > > > > > > Cc: "Jean-Francois Dive" ; > > > > > ; > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 8:34 PM > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > Can you send your snmp.conf file? These are the relevant bits > of > > > mine: > > > > > > > > > > > > > > com2sec local localhost public > > > > > > > com2sec localrw localhost private > > > > > > > com2sec mynetwork 172.18.0.0/24 public > > > > > > > com2sec mynetworkrw 172.18.0.0/24 private > > > > > > > > > > > > > > #### > > > > > > > # Second, map the security names into group names: > > > > > > > > > > > > > > # sec.model sec.name > > > > > > > group LocalRWGroup v1 localrw > > > > > > > group LocalRWGroup v2c localrw > > > > > > > group LocalRWGroup usm localrw > > > > > > > group LocalROGroup v1 local > > > > > > > group LocalROGroup v2c local > > > > > > > group LocalROGroup usm local > > > > > > > group NetROGroup v1 mynetwork > > > > > > > group NetROGroup v2c mynetwork > > > > > > > group NetROGroup usm mynetwork > > > > > > > group NetRWGroup v1 mynetworkrw > > > > > > > group NetRWGroup v2c mynetworkrw > > > > > > > group NetRWGroup usm mynetworkrw > > > > > > > > > > > > > > #### > > > > > > > # Third, create a view for us to let the groups have rights to: > > > > > > > > > > > > > > # incl/excl subtree mask > > > > > > > view all included .1 80 > > > > > > > > > > > > > > #### > > > > > > > # Finally, grant the 2 groups access to the 1 view with > different > > > > > > > # write permissions: > > > > > > > > > > > > > > # context sec.model sec.level match read write > > > notif > > > > > > > access LocalROGroup "" any noauth exact all > none > > > > > none > > > > > > > access LocalRWGroup "" any noauth exact all > all > > > > > none > > > > > > > access NetROGroup "" any noauth exact all > none > > > > > none > > > > > > > access NetRWGroup "" any noauth exact all > all > > > > > none > > > > > > > > > > > > > > > > > > > > > public@localhost does work on my machine. > > > > > > > > > > > > > > Joe > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > I used TMRTGCHO as community name before, but since I've got > this > > > > > > problem I > > > > > > > > use now public. > > > > > > > > Request from localhost or any other interface doesn't work. > > > > > > > > I cleaned snmpd.log, restarted snmpd: > > > > > > > > #/usr/local/sbin/snmpd -D -c > /usr/local/share/snmp/snmpd.conf -l > > > > > > > > /var/log/snmpd.log > > > > > > > > > > > > > > > > and a new one is located at > > > http://www.tarakan-network.com/snmpd.log > > > > > (I > > > > > > did > > > > > > > > a snmpwalk and snmpget for public@localhost but no success) > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > To: "Chojin" > > > > > > > > Sent: Wednesday, September 12, 2001 10:38 AM > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > Hi (salut) > > > > > > > > > > > > > > > > > > In fact, i see some successfull request with the community: > > > > > > > > > TMRTGCHO and no attemps with the localhost one... seems > pretty > > > odd. > > > > > > did > > > > > > > > > you only got those requests from localhost not working ? > > > > > > > > > > > > > > > > > > Otherwise, purge the log file, be *sure* that no requests > are > > > > > comming > > > > > > from > > > > > > > > > somewhere else and resart to see some failures... > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > I launched in debug mode > > > > > > > > > > #/usr/local/sbin/snmpd -D -c > > > /usr/local/share/snmp/snmpd.conf -l > > > > > > > > > > /var/log/snmpd.log > > > > > > > > > > I attached snmpd.log > > > > > > > > > > There are so many informations I can't detect the problem > :pp > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > > > To: "Chojin" > > > > > > > > > > Cc: ; > > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 9:53 AM > > > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > i think it is possible to start the snmpd and not send > it to > > > > > > > > backgroud, > > > > > > > > > > > and see if it does printout some error > messages..Otherwise > > > use > > > > > the > > > > > > > > truss > > > > > > > > > > > command to follow the syscalls made by the daemon while > > > > > processing > > > > > > > > your > > > > > > > > > > > request, this could point you to a problem.. > > > > > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > > > > > snmpd.log is empty... > > > > > > > > > > > > > > > > > > > > > > > > I did #netstat -an | grep 161 > > > > > > > > > > > > udp4 0 0 *.161 *.* > > > > > > > > > > > > > > > > > > > > > > > > port 161 exists then it should work... > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > > > > > To: "Chojin" > > > > > > > > > > > > Cc: ; > > > > > > > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 3:21 AM > > > > > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > > > > > > > So you have any traces in a log file or something > > > similar ? > > > > > > > > > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > > > > > > > > > > > > > I have a problem with snmpd. > > > > > > > > > > > > > > > > > > > > > > > > > > > > In fact, one day, for unknown reason ( I didn't > modify > > > any > > > > > > > > > > setting ), > > > > > > > > > > > > snmpd > > > > > > > > > > > > > > didn't work anymore: > > > > > > > > > > > > > > When I do a snmpwalk or snmpget to > public@localhost it > > > > > > doesn't > > > > > > > > > > respond. > > > > > > > > > > > > > > I checked snmpd, recreated snmpd.conf and launched > > > again > > > > > > snmpd > > > > > > > > > > with -c > > > > > > > > > > > > > > and -l to be sure it uses the correct files. > > > > > > > > > > > > > > But even if snmpd is in background process, > > > > > > public@localhost > > > > > > > > > > doesn't > > > > > > > > > > > > work. > > > > > > > > > > > > > > I don't have any firewall rule that block it. > > > > > > > > > > > > > > > > > > > > > > > > > > > > #snmpwalk localhost public > > > > > > > > > > > > > > Timeout: No Response from localhost > > > > > > > > > > > > > > #snmpget localhost public SysName > > > > > > > > > > > > > > Timeout: No Response from localhost. > > > > > > > > > > > > > > > > > > > > > > > > > > > > After I upgraded my system from 4.3-STABLE to > 4.4-RC, > > > it > > > > > > didn't > > > > > > > > > > change > > > > > > > > > > > > > > anything for snmpd. > > > > > > > > > > > > > > > > > > > > > > > > > > > > If someone has got any idea... > > > > > > > > > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > > > > > > > > > > > Chojin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 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-questions" in the body of the > message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 15:48:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id 09FC937B409 for ; Mon, 17 Sep 2001 15:48:05 -0700 (PDT) Received: (qmail 68341 invoked by uid 1001); 17 Sep 2001 22:59:08 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Sep 2001 22:59:08 -0000 Date: Mon, 17 Sep 2001 15:59:08 -0700 (PDT) From: Dan To: Frank Nobis Cc: Stephen Hurd , Subject: Re: PIO mode In-Reply-To: <20010915110300.E225A16F96@gatekeeper.radio-do.de> Message-ID: <20010917155839.F76124-100000@gandalf.bravenet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You were completely right. I replaced the IDE cable and that fixed it. Thankyou very much. Dan. On Sat, 15 Sep 2001, Frank Nobis wrote: > Date: Sat, 15 Sep 2001 13:03:00 +0200 > From: Frank Nobis > To: Stephen Hurd > Cc: Dan , freebsd-hackers@freebsd.org > Subject: Re: PIO mode > > > Am Samstag, 15. September 2001 um 07:33 schrieb Stephen Hurd: > > >> ad0s1a: UDMA ICRC error reading fsbn 191 of 64-79 (ad0s1 bn 191; cn 0 tn > >> 3 > >> sn 2) retrying > > > > Actually, the ICRC error IS a bit frigtening... I always got read timeouts > > when it was a bad HD/controller combo... I'd like to revise my opinion to > > say > > "Get your data off now while you still can!" But maybe dig through the ata > > source... there's probobly helpful comments in that bit. > > > > I had those problems once with a HPT370 controller. The problem was at last > bad cable. After trying three different 80 wire types I had success. I had > no more ICRC errors since then. > > Frank > > -- > Frank Nobis > Landgrafenstr. 130 > 44139 Dortmund > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 15:51:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id 0AEC837B409; Mon, 17 Sep 2001 15:49:32 -0700 (PDT) Received: from chojin (chojin.lan.tarakan-network.com [192.168.69.2] (may be forged)) by tarakan-network.com (8.11.6/8.11.3) with SMTP id f8HMnGt84153; Tue, 18 Sep 2001 00:49:16 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <01bc01c13fca$fcf01260$0245a8c0@chojin> From: "Chojin" To: "Joe Clarke" Cc: "Jean-Francois Dive" , , References: <20010917183916.L69881-100000@shumai.marcuscom.com> Subject: Re: Problem with snmpd Date: Tue, 18 Sep 2001 00:49:19 +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 6.00.2526.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2526.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG #snmpwalk 127.0.0.1 public system Timeout: No Response from 127.0.0.1 no success again... but better to use 127.0.0.1 because : #host localhost localhost.com has address 63.231.68.113 localhost.com mail is handled (pri=10) by ghost.localhost.com (even with bind killed) /etc/hosts: ::1 localhost localhost.my.domain myname.my.domain 127.0.0.1 localhost localhost.my.domain myname.my.domain ... /etc/host.conf # First try the /etc/hosts file hosts # Now try the nameserver next. bind ----- Original Message ----- From: "Joe Clarke" To: "Chojin" Cc: "Jean-Francois Dive" ; ; Sent: Tuesday, September 18, 2001 12:40 AM Subject: Re: Problem with snmpd > Those look fine. What about nslookup localhost (or if you're using hosts > before bind, what does /etc/hosts look like)? It may be that localhost > resolves to something other than 127.0.0.1. Have you tried: > > snmpwalk 127.0.0.1 public system > > ? That should also work. > > Joe > > On Tue, 18 Sep 2001, Chojin wrote: > > > >I compiled /usr/ports/net/net-snmp > > me too > > > > #netstat -a > > Active Internet connections (including servers) > > Proto Recv-Q Send-Q Local Address Foreign Address (state) > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1618 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1616 TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.4110 208.141.100.35.socks TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.4108 208.141.100.35.socks TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.4107 208.141.100.35.socks TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.4105 Hacker.gs.2532 SYN_SENT > > tcp4 0 0 chojin.adsl.neri.4103 208.141.100.35.socks TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.4100 Hacker.gs.2532 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.smtp rdu57-28-046.nc..1889 TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.4098 AFontenayssB-101.3340 SYN_SENT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1615 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1613 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1612 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1610 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1609 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1607 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1606 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1604 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1603 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1601 TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.auth Hacker.gs.1628 > > FIN_WAIT_2 > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1597 TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.4084 Hacker.gs.2532 > > FIN_WAIT_2 > > tcp4 0 0 chojin.adsl.neri.3832 deneb.freedomshe.4386 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3682 deneb.freedomshe.4969 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.netbi chojin.lan.tarak.1299 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1742 ACBD133F.ipt.aol.1031 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1809 aboukir-101-1-4-.5557 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1493 paris.fr.eu.unde.6667 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1481 undernet.span.ch.6667 > > ESTABLISHED > > tcp4 0 0 *.http *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.4950 arne.swip.net.6669 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.4730 no-security.net.8367 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.4540 irc.carrier1.net.6667 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.ssh chojin.lan.tarak.2099 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3145 ACBE8C24.ipt.aol.3419 > > ESTABLISHED > > tcp4 0 55 tarakan.lan.tara.22006 chojin.lan.tarak.1980 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3070 entrechat.net.6667 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36867 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36875 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36870 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1657 skippy.solidshel.2843 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1390 entrechat.net.6668 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1380 powertech.no.eu..afs3- > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1379 uu194-7-27-98.un.8080 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.4267 chojin.adsl.neri.1373 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1373 chojin.adsl.neri.4267 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1742 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.3337 chojin.adsl.neri.1254 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1254 chojin.adsl.neri.3337 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3337 208.141.100.35.30790 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1208 208.141.100.35.socks > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1204 208.141.100.35.socks > > ESTABLISHED > > tcp4 0 0 *.3331 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.1198 skippy.solidshel.2843 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.dec-n *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.3337 NS1.ipvh.2787 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3337 NS1.ipvh.2778 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3337 box1.TyranZ.3847 > > ESTABLISHED > > tcp4 0 0 *.3337 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.1112 skippy.solidshel.2843 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.domai *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.1084 TyranZ.20801 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1080 ircnet.kaptech.6667 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.6667 tarakan.lan.tara.1072 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.1072 tarakan.lan.tara.6667 > > ESTABLISHED > > tcp4 0 0 *.2211 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.1065 AVelizy-101-2-2-.1982 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1063 irc1-2.free.fr.6667 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1062 hitomi.ecranbleu.dec-n > > ESTABLISHED > > tcp4 0 0 *.12345 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.3682 vega.freedomshel.1534 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3682 vega.freedomshel.1524 > > ESTABLISHED > > tcp4 0 0 *.22011 *.* LISTEN > > tcp4 0 48 tarakan.lan.tara.ssh chojin.lan.tarak.1164 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.6667 tarakan.lan.tara.1048 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.1048 tarakan.lan.tara.6667 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1047 www.skydirect.ne.6667 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.4400 tarakan.lan.tara.1042 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.1042 tarakan.lan.tara.4400 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1041 bloob.oxyd.fr.4400 > > ESTABLISHED > > tcp4 0 0 *.4400 *.* LISTEN > > tcp4 0 0 *.6669 *.* LISTEN > > tcp4 0 0 *.6668 *.* LISTEN > > tcp4 0 0 *.6667 *.* LISTEN > > tcp4 0 0 *.6665 *.* LISTEN > > tcp4 0 0 *.6666 *.* LISTEN > > tcp4 0 0 *.4401 *.* LISTEN > > tcp4 0 0 *.13333 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.1035 rinka.nerim.net.6667 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3682 chojin.adsl.neri.1032 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1032 chojin.adsl.neri.3682 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1031 irc.planetintern.6667 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.21003 chojin.lan.tarak.1163 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.22002 chojin.lan.tarak.1162 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.2532 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.4695 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.3418 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.4267 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.6632 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.3682 *.* LISTEN > > tcp4 0 0 *.netbios-ssn *.* LISTEN > > tcp46 0 0 *.22005 *.* LISTEN > > tcp4 0 0 *.22005 *.* LISTEN > > tcp46 0 0 *.22006 *.* LISTEN > > tcp46 0 0 *.22002 *.* LISTEN > > tcp4 0 0 *.22006 *.* LISTEN > > tcp46 0 0 *.21003 *.* LISTEN > > tcp4 0 0 *.21003 *.* LISTEN > > tcp4 0 0 *.22002 *.* LISTEN > > tcp4 0 0 tarakan.lan.tara.11982 *.* LISTEN > > tcp46 0 0 *.auth *.* LISTEN > > tcp4 0 0 *.submission *.* LISTEN > > tcp4 0 0 *.smtp *.* LISTEN > > tcp4 0 0 *.ssh *.* LISTEN > > tcp46 0 0 *.ssh *.* LISTEN > > tcp4 0 0 *.swat *.* LISTEN > > tcp4 0 0 *.auth *.* LISTEN > > tcp4 0 0 *.pop3 *.* LISTEN > > tcp6 0 0 *.ftp *.* LISTEN > > tcp4 0 0 *.ftp *.* LISTEN > > tcp4 0 0 *.sunrpc *.* LISTEN > > tcp4 0 0 localhost.domain *.* LISTEN > > tcp4 0 0 tarakan.lan.tara.domai *.* LISTEN > > tcp4 0 0 modem-adsl.domain *.* LISTEN > > udp4 0 0 *.4659 *.* > > udp4 0 0 *.snmp *.* > > udp4 0 0 localhost.3336 *.* > > udp4 0 0 *.3704 *.* > > udp4 0 0 *.2409 *.* > > udp4 0 0 chojin.adsl.neri.domai *.* > > udp4 0 0 *.1488 *.* > > udp4 0 0 *.* *.* > > udp4 0 0 *.1380 *.* > > udp4 0 0 *.afs3-bos *.* > > udp4 0 0 *.4183 *.* > > udp4 0 0 *.1291 *.* > > udp4 0 0 *.1244 *.* > > udp4 0 0 tarakan.lan.tara.netbi *.* > > udp4 0 0 tarakan.lan.tara.netbi *.* > > udp4 0 0 *.netbios-dgm *.* > > udp4 0 0 *.netbios-ns *.* > > udp4 0 0 *.10000 *.* > > udp4 0 0 chojin.adsl.neri.1124 chojin.adsl.neri.syslo > > udp4 0 0 *.bootps *.* > > udp4 0 0 *.sunrpc *.* > > udp4 0 0 *.1028 *.* > > udp4 0 0 localhost.domain *.* > > udp4 0 0 tarakan.lan.tara.domai *.* > > udp4 0 0 modem-adsl.domain *.* > > udp4 0 0 *.syslog *.* > > udp6 0 0 *.syslog *.* > > ip 4 0 0 *.* *.* > > icm4 0 0 *.* *.* > > ip64 0 0 *.* *.* > > Netgraph sockets > > Type Recv-Q Send-Q Node Address #Hooks > > ctrl 0 0 > > data 0 0 > > Active UNIX domain sockets > > Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr > > d04c2d80 stream 0 0 d04f9580 0 0 0 > > /var/pwcheck/pwcheck > > d04c2e40 stream 0 0 d04f7240 0 0 0 > > /tmp/.s.PGSQL.5432 > > d04c2f40 stream 0 0 d04bd800 0 0 0 > > /var/run/ndc > > d04c2d00 dgram 0 0 0 d04c2fc0 0 d04c2c80 > > d04c2c80 dgram 0 0 0 d04c2fc0 0 d04c2e00 > > d04c2e00 dgram 0 0 0 d04c2fc0 0 d04c2dc0 > > d04c2dc0 dgram 0 0 0 d04c2fc0 0 d04c2e80 > > d04c2e80 dgram 0 0 0 d04c2fc0 0 d04c2ec0 > > d04c2ec0 dgram 0 0 0 d04c2fc0 0 d04c2f00 > > d04c2f00 dgram 0 0 0 d04c2fc0 0 d04c2f80 > > d04c2f80 dgram 0 0 0 d04c2fc0 0 0 > > d04c2fc0 dgram 0 0 d04be940 0 d04c2d00 0 > > /var/run/log > > > > #ifconfig -a > > ed0: flags=8843 mtu 1500 > > inet 10.0.0.10 netmask 0xffffff00 broadcast 10.0.0.255 > > inet6 fe80::24f:49ff:fe0a:b2dd%ed0 prefixlen 64 scopeid 0x1 > > ether 00:4f:49:0a:b2:dd > > ed1: flags=8843 mtu 1500 > > inet 192.168.69.1 netmask 0xffffff00 broadcast 192.168.69.255 > > inet6 fe80::5054:5ff:fef9:761d%ed1 prefixlen 64 scopeid 0x2 > > ether 52:54:05:f9:76:1d > > lp0: flags=8810 mtu 1500 > > faith0: flags=8000 mtu 1500 > > stf0: flags=0<> mtu 1280 > > lo0: flags=8049 mtu 16384 > > inet6 ::1 prefixlen 128 > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 > > inet 127.0.0.1 netmask 0xff000000 > > ppp0: flags=8010 mtu 1500 > > sl0: flags=c010 mtu 552 > > tun0: flags=8051 mtu 1492 > > inet6 fe80::24f:49ff:fe0a:b2dd%tun0 prefixlen 64 scopeid 0x9 > > inet 62.4.22.98 --> 194.206.78.3 netmask 0xff000000 > > Opened by PID 168 > > > > Anything wrong? > > > > ----- Original Message ----- > > From: "Joe Clarke" > > To: "Chojin" > > Cc: "Jean-Francois Dive" ; ; > > > > Sent: Tuesday, September 18, 2001 12:31 AM > > Subject: Re: Problem with snmpd > > > > > > > What does netstat -a and ifconfig -a show? Something is not right on your > > > machine. I compiled /usr/ports/net/net-snmp and it worked out of the box. > > > I'm using the default /usr/local/etc/rc.d/snmpd.sh script to start snmpd. > > > > > > Joe > > > > > > On Tue, 18 Sep 2001, Chojin wrote: > > > > > > > My default location is /usr/local/share/snmp/snmpd.conf > > > > I used your file (just modified for 192.168... lan). > > > > To be sure snmpd uses the good file I used -c > > > > #/usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf > > > > #ps aux | grep snmpd > > > > root 81374 7.2 0.4 3256 2624 p0 S 12:25AM 0:00.15 > > > > /usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf > > > > #snmpwalk -v 1 localhost public system > > > > Timeout: No Response from localhost > > > > > > > > As you see, without success... > > > > > > > > ----- Original Message ----- > > > > From: "Joe Clarke" > > > > To: "Chojin" > > > > Cc: "Jean-Francois Dive" ; > > ; > > > > > > > > Sent: Tuesday, September 18, 2001 12:18 AM > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > Not sure. I have snmpd 4.2.1 working perfectly on 4.3-RELEASE and > > > > > 4.4-STABLE as of an hour ago. Attached is my entire config file. I > > keep > > > > > it in /usr/local/lib/snmp (which is the default location). > > > > > > > > > > Joe > > > > > > > > > > On Mon, 17 Sep 2001, Chojin wrote: > > > > > > > > > > > I didn't resolved my problem. > > > > > > Even after upgraded to 4.4-stable (because there was maybe a bug in > > > > snmpd > > > > > > :-p). > > > > > > > > > > > > I don't know what I could do. > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Chojin" > > > > > > To: "Joe Clarke" > > > > > > Cc: "Jean-Francois Dive" ; > > > > ; > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 9:30 PM > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > I tried your snmpd.conf but with no success :'( > > > > > > > ----- Original Message ----- > > > > > > > From: "Joe Clarke" > > > > > > > To: "Chojin" > > > > > > > Cc: "Jean-Francois Dive" ; > > > > > > ; > > > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 8:34 PM > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > Can you send your snmp.conf file? These are the relevant bits > > of > > > > mine: > > > > > > > > > > > > > > > > com2sec local localhost public > > > > > > > > com2sec localrw localhost private > > > > > > > > com2sec mynetwork 172.18.0.0/24 public > > > > > > > > com2sec mynetworkrw 172.18.0.0/24 private > > > > > > > > > > > > > > > > #### > > > > > > > > # Second, map the security names into group names: > > > > > > > > > > > > > > > > # sec.model sec.name > > > > > > > > group LocalRWGroup v1 localrw > > > > > > > > group LocalRWGroup v2c localrw > > > > > > > > group LocalRWGroup usm localrw > > > > > > > > group LocalROGroup v1 local > > > > > > > > group LocalROGroup v2c local > > > > > > > > group LocalROGroup usm local > > > > > > > > group NetROGroup v1 mynetwork > > > > > > > > group NetROGroup v2c mynetwork > > > > > > > > group NetROGroup usm mynetwork > > > > > > > > group NetRWGroup v1 mynetworkrw > > > > > > > > group NetRWGroup v2c mynetworkrw > > > > > > > > group NetRWGroup usm mynetworkrw > > > > > > > > > > > > > > > > #### > > > > > > > > # Third, create a view for us to let the groups have rights to: > > > > > > > > > > > > > > > > # incl/excl subtree mask > > > > > > > > view all included .1 80 > > > > > > > > > > > > > > > > #### > > > > > > > > # Finally, grant the 2 groups access to the 1 view with > > different > > > > > > > > # write permissions: > > > > > > > > > > > > > > > > # context sec.model sec.level match read write > > > > notif > > > > > > > > access LocalROGroup "" any noauth exact all > > none > > > > > > none > > > > > > > > access LocalRWGroup "" any noauth exact all > > all > > > > > > none > > > > > > > > access NetROGroup "" any noauth exact all > > none > > > > > > none > > > > > > > > access NetRWGroup "" any noauth exact all > > all > > > > > > none > > > > > > > > > > > > > > > > > > > > > > > > public@localhost does work on my machine. > > > > > > > > > > > > > > > > Joe > > > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > I used TMRTGCHO as community name before, but since I've got > > this > > > > > > > problem I > > > > > > > > > use now public. > > > > > > > > > Request from localhost or any other interface doesn't work. > > > > > > > > > I cleaned snmpd.log, restarted snmpd: > > > > > > > > > #/usr/local/sbin/snmpd -D -c > > /usr/local/share/snmp/snmpd.conf -l > > > > > > > > > /var/log/snmpd.log > > > > > > > > > > > > > > > > > > and a new one is located at > > > > http://www.tarakan-network.com/snmpd.log > > > > > > (I > > > > > > > did > > > > > > > > > a snmpwalk and snmpget for public@localhost but no success) > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > > To: "Chojin" > > > > > > > > > Sent: Wednesday, September 12, 2001 10:38 AM > > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi (salut) > > > > > > > > > > > > > > > > > > > > In fact, i see some successfull request with the community: > > > > > > > > > > TMRTGCHO and no attemps with the localhost one... seems > > pretty > > > > odd. > > > > > > > did > > > > > > > > > > you only got those requests from localhost not working ? > > > > > > > > > > > > > > > > > > > > Otherwise, purge the log file, be *sure* that no requests > > are > > > > > > comming > > > > > > > from > > > > > > > > > > somewhere else and resart to see some failures... > > > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > > > I launched in debug mode > > > > > > > > > > > #/usr/local/sbin/snmpd -D -c > > > > /usr/local/share/snmp/snmpd.conf -l > > > > > > > > > > > /var/log/snmpd.log > > > > > > > > > > > I attached snmpd.log > > > > > > > > > > > There are so many informations I can't detect the problem > > :pp > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > > > > To: "Chojin" > > > > > > > > > > > Cc: ; > > > > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 9:53 AM > > > > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > i think it is possible to start the snmpd and not send > > it to > > > > > > > > > backgroud, > > > > > > > > > > > > and see if it does printout some error > > messages..Otherwise > > > > use > > > > > > the > > > > > > > > > truss > > > > > > > > > > > > command to follow the syscalls made by the daemon while > > > > > > processing > > > > > > > > > your > > > > > > > > > > > > request, this could point you to a problem.. > > > > > > > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > > > > > > > snmpd.log is empty... > > > > > > > > > > > > > > > > > > > > > > > > > > I did #netstat -an | grep 161 > > > > > > > > > > > > > udp4 0 0 *.161 *.* > > > > > > > > > > > > > > > > > > > > > > > > > > port 161 exists then it should work... > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > > > > > > To: "Chojin" > > > > > > > > > > > > > Cc: ; > > > > > > > > > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 3:21 AM > > > > > > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > > > > > > > > > So you have any traces in a log file or something > > > > similar ? > > > > > > > > > > > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I have a problem with snmpd. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > In fact, one day, for unknown reason ( I didn't > > modify > > > > any > > > > > > > > > > > setting ), > > > > > > > > > > > > > snmpd > > > > > > > > > > > > > > > didn't work anymore: > > > > > > > > > > > > > > > When I do a snmpwalk or snmpget to > > public@localhost it > > > > > > > doesn't > > > > > > > > > > > respond. > > > > > > > > > > > > > > > I checked snmpd, recreated snmpd.conf and launched > > > > again > > > > > > > snmpd > > > > > > > > > > > with -c > > > > > > > > > > > > > > > and -l to be sure it uses the correct files. > > > > > > > > > > > > > > > But even if snmpd is in background process, > > > > > > > public@localhost > > > > > > > > > > > doesn't > > > > > > > > > > > > > work. > > > > > > > > > > > > > > > I don't have any firewall rule that block it. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > #snmpwalk localhost public > > > > > > > > > > > > > > > Timeout: No Response from localhost > > > > > > > > > > > > > > > #snmpget localhost public SysName > > > > > > > > > > > > > > > Timeout: No Response from localhost. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > After I upgraded my system from 4.3-STABLE to > > 4.4-RC, > > > > it > > > > > > > didn't > > > > > > > > > > > change > > > > > > > > > > > > > > > anything for snmpd. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > If someone has got any idea... > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Chojin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 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-questions" in the body of the > > message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 15:53:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id 4787237B40C; Mon, 17 Sep 2001 15:52:35 -0700 (PDT) Received: from chojin (chojin.lan.tarakan-network.com [192.168.69.2] (may be forged)) by tarakan-network.com (8.11.6/8.11.3) with SMTP id f8HMqOt84533; Tue, 18 Sep 2001 00:52:24 +0200 (CEST) (envelope-from freebsd@tarakan-network.com) Message-ID: <01d001c13fcb$6d44f030$0245a8c0@chojin> From: "Chojin" To: "Joe Clarke" Cc: "Jean-Francois Dive" , , References: <20010917183916.L69881-100000@shumai.marcuscom.com> Subject: Re: Problem with snmpd Date: Tue, 18 Sep 2001 00:52:28 +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 6.00.2526.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2526.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG # sec.name source community com2sec local 127.0.0.1 public com2sec localrw 127.0.0.1 private hehe now it works! problem came from localhost that was not correctly resolved (but why?) ----- Original Message ----- From: "Joe Clarke" To: "Chojin" Cc: "Jean-Francois Dive" ; ; Sent: Tuesday, September 18, 2001 12:40 AM Subject: Re: Problem with snmpd > Those look fine. What about nslookup localhost (or if you're using hosts > before bind, what does /etc/hosts look like)? It may be that localhost > resolves to something other than 127.0.0.1. Have you tried: > > snmpwalk 127.0.0.1 public system > > ? That should also work. > > Joe > > On Tue, 18 Sep 2001, Chojin wrote: > > > >I compiled /usr/ports/net/net-snmp > > me too > > > > #netstat -a > > Active Internet connections (including servers) > > Proto Recv-Q Send-Q Local Address Foreign Address (state) > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1618 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1616 TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.4110 208.141.100.35.socks TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.4108 208.141.100.35.socks TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.4107 208.141.100.35.socks TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.4105 Hacker.gs.2532 SYN_SENT > > tcp4 0 0 chojin.adsl.neri.4103 208.141.100.35.socks TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.4100 Hacker.gs.2532 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.smtp rdu57-28-046.nc..1889 TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.4098 AFontenayssB-101.3340 SYN_SENT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1615 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1613 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1612 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1610 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1609 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1607 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1606 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1604 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1603 TIME_WAIT > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1601 TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.auth Hacker.gs.1628 > > FIN_WAIT_2 > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1597 TIME_WAIT > > tcp4 0 0 chojin.adsl.neri.4084 Hacker.gs.2532 > > FIN_WAIT_2 > > tcp4 0 0 chojin.adsl.neri.3832 deneb.freedomshe.4386 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3682 deneb.freedomshe.4969 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.netbi chojin.lan.tarak.1299 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1742 ACBD133F.ipt.aol.1031 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1809 aboukir-101-1-4-.5557 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1493 paris.fr.eu.unde.6667 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1481 undernet.span.ch.6667 > > ESTABLISHED > > tcp4 0 0 *.http *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.4950 arne.swip.net.6669 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.4730 no-security.net.8367 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.4540 irc.carrier1.net.6667 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.ssh chojin.lan.tarak.2099 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3145 ACBE8C24.ipt.aol.3419 > > ESTABLISHED > > tcp4 0 55 tarakan.lan.tara.22006 chojin.lan.tarak.1980 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3070 entrechat.net.6667 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36867 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36875 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36870 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1657 skippy.solidshel.2843 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1390 entrechat.net.6668 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1380 powertech.no.eu..afs3- > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1379 uu194-7-27-98.un.8080 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.4267 chojin.adsl.neri.1373 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1373 chojin.adsl.neri.4267 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1742 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.3337 chojin.adsl.neri.1254 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1254 chojin.adsl.neri.3337 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3337 208.141.100.35.30790 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1208 208.141.100.35.socks > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1204 208.141.100.35.socks > > ESTABLISHED > > tcp4 0 0 *.3331 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.1198 skippy.solidshel.2843 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.dec-n *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.3337 NS1.ipvh.2787 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3337 NS1.ipvh.2778 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3337 box1.TyranZ.3847 > > ESTABLISHED > > tcp4 0 0 *.3337 *.* LISTE N > > tcp4 0 0 chojin.adsl.neri.1112 skippy.solidshel.2843 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.domai *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.1084 TyranZ.20801 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1080 ircnet.kaptech.6667 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.6667 tarakan.lan.tara.1072 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.1072 tarakan.lan.tara.6667 > > ESTABLISHED > > tcp4 0 0 *.2211 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.1065 AVelizy-101-2-2-.1982 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1063 irc1-2.free.fr.6667 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1062 hitomi.ecranbleu.dec-n > > ESTABLISHED > > tcp4 0 0 *.12345 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.3682 vega.freedomshel.1534 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3682 vega.freedomshel.1524 > > ESTABLISHED > > tcp4 0 0 *.22011 *.* LISTEN > > tcp4 0 48 tarakan.lan.tara.ssh chojin.lan.tarak.1164 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.6667 tarakan.lan.tara.1048 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.1048 tarakan.lan.tara.6667 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1047 www.skydirect.ne.6667 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.4400 tarakan.lan.tara.1042 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.1042 tarakan.lan.tara.4400 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1041 bloob.oxyd.fr.4400 > > ESTABLISHED > > tcp4 0 0 *.4400 *.* LISTEN > > tcp4 0 0 *.6669 *.* LISTEN > > tcp4 0 0 *.6668 *.* LISTEN > > tcp4 0 0 *.6667 *.* LISTEN > > tcp4 0 0 *.6665 *.* LISTEN > > tcp4 0 0 *.6666 *.* LISTEN > > tcp4 0 0 *.4401 *.* LISTEN > > tcp4 0 0 *.13333 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.1035 rinka.nerim.net.6667 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.3682 chojin.adsl.neri.1032 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1032 chojin.adsl.neri.3682 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.1031 irc.planetintern.6667 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.21003 chojin.lan.tarak.1163 > > ESTABLISHED > > tcp4 0 0 tarakan.lan.tara.22002 chojin.lan.tarak.1162 > > ESTABLISHED > > tcp4 0 0 chojin.adsl.neri.2532 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.4695 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.3418 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.4267 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.6632 *.* LISTEN > > tcp4 0 0 chojin.adsl.neri.3682 *.* LISTEN > > tcp4 0 0 *.netbios-ssn *.* LISTEN > > tcp46 0 0 *.22005 *.* LISTEN > > tcp4 0 0 *.22005 *.* LISTEN > > tcp46 0 0 *.22006 *.* LISTEN > > tcp46 0 0 *.22002 *.* LISTEN > > tcp4 0 0 *.22006 *.* LISTEN > > tcp46 0 0 *.21003 *.* LISTEN > > tcp4 0 0 *.21003 *.* LISTEN > > tcp4 0 0 *.22002 *.* LISTEN > > tcp4 0 0 tarakan.lan.tara.11982 *.* LISTEN > > tcp46 0 0 *.auth *.* LISTEN > > tcp4 0 0 *.submission *.* LISTEN > > tcp4 0 0 *.smtp *.* LISTEN > > tcp4 0 0 *.ssh *.* LISTEN > > tcp46 0 0 *.ssh *.* LISTEN > > tcp4 0 0 *.swat *.* LISTEN > > tcp4 0 0 *.auth *.* LISTEN > > tcp4 0 0 *.pop3 *.* LISTEN > > tcp6 0 0 *.ftp *.* LISTEN > > tcp4 0 0 *.ftp *.* LISTEN > > tcp4 0 0 *.sunrpc *.* LISTEN > > tcp4 0 0 localhost.domain *.* LISTEN > > tcp4 0 0 tarakan.lan.tara.domai *.* LISTEN > > tcp4 0 0 modem-adsl.domain *.* LISTEN > > udp4 0 0 *.4659 *.* > > udp4 0 0 *.snmp *.* > > udp4 0 0 localhost.3336 *.* > > udp4 0 0 *.3704 *.* > > udp4 0 0 *.2409 *.* > > udp4 0 0 chojin.adsl.neri.domai *.* > > udp4 0 0 *.1488 *.* > > udp4 0 0 *.* *.* > > udp4 0 0 *.1380 *.* > > udp4 0 0 *.afs3-bos *.* > > udp4 0 0 *.4183 *.* > > udp4 0 0 *.1291 *.* > > udp4 0 0 *.1244 *.* > > udp4 0 0 tarakan.lan.tara.netbi *.* > > udp4 0 0 tarakan.lan.tara.netbi *.* > > udp4 0 0 *.netbios-dgm *.* > > udp4 0 0 *.netbios-ns *.* > > udp4 0 0 *.10000 *.* > > udp4 0 0 chojin.adsl.neri.1124 chojin.adsl.neri.syslo > > udp4 0 0 *.bootps *.* > > udp4 0 0 *.sunrpc *.* > > udp4 0 0 *.1028 *.* > > udp4 0 0 localhost.domain *.* > > udp4 0 0 tarakan.lan.tara.domai *.* > > udp4 0 0 modem-adsl.domain *.* > > udp4 0 0 *.syslog *.* > > udp6 0 0 *.syslog *.* > > ip 4 0 0 *.* *.* > > icm4 0 0 *.* *.* > > ip64 0 0 *.* *.* > > Netgraph sockets > > Type Recv-Q Send-Q Node Address #Hooks > > ctrl 0 0 > > data 0 0 > > Active UNIX domain sockets > > Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr > > d04c2d80 stream 0 0 d04f9580 0 0 0 > > /var/pwcheck/pwcheck > > d04c2e40 stream 0 0 d04f7240 0 0 0 > > /tmp/.s.PGSQL.5432 > > d04c2f40 stream 0 0 d04bd800 0 0 0 > > /var/run/ndc > > d04c2d00 dgram 0 0 0 d04c2fc0 0 d04c2c80 > > d04c2c80 dgram 0 0 0 d04c2fc0 0 d04c2e00 > > d04c2e00 dgram 0 0 0 d04c2fc0 0 d04c2dc0 > > d04c2dc0 dgram 0 0 0 d04c2fc0 0 d04c2e80 > > d04c2e80 dgram 0 0 0 d04c2fc0 0 d04c2ec0 > > d04c2ec0 dgram 0 0 0 d04c2fc0 0 d04c2f00 > > d04c2f00 dgram 0 0 0 d04c2fc0 0 d04c2f80 > > d04c2f80 dgram 0 0 0 d04c2fc0 0 0 > > d04c2fc0 dgram 0 0 d04be940 0 d04c2d00 0 > > /var/run/log > > > > #ifconfig -a > > ed0: flags=8843 mtu 1500 > > inet 10.0.0.10 netmask 0xffffff00 broadcast 10.0.0.255 > > inet6 fe80::24f:49ff:fe0a:b2dd%ed0 prefixlen 64 scopeid 0x1 > > ether 00:4f:49:0a:b2:dd > > ed1: flags=8843 mtu 1500 > > inet 192.168.69.1 netmask 0xffffff00 broadcast 192.168.69.255 > > inet6 fe80::5054:5ff:fef9:761d%ed1 prefixlen 64 scopeid 0x2 > > ether 52:54:05:f9:76:1d > > lp0: flags=8810 mtu 1500 > > faith0: flags=8000 mtu 1500 > > stf0: flags=0<> mtu 1280 > > lo0: flags=8049 mtu 16384 > > inet6 ::1 prefixlen 128 > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 > > inet 127.0.0.1 netmask 0xff000000 > > ppp0: flags=8010 mtu 1500 > > sl0: flags=c010 mtu 552 > > tun0: flags=8051 mtu 1492 > > inet6 fe80::24f:49ff:fe0a:b2dd%tun0 prefixlen 64 scopeid 0x9 > > inet 62.4.22.98 --> 194.206.78.3 netmask 0xff000000 > > Opened by PID 168 > > > > Anything wrong? > > > > ----- Original Message ----- > > From: "Joe Clarke" > > To: "Chojin" > > Cc: "Jean-Francois Dive" ; ; > > > > Sent: Tuesday, September 18, 2001 12:31 AM > > Subject: Re: Problem with snmpd > > > > > > > What does netstat -a and ifconfig -a show? Something is not right on your > > > machine. I compiled /usr/ports/net/net-snmp and it worked out of the box. > > > I'm using the default /usr/local/etc/rc.d/snmpd.sh script to start snmpd. > > > > > > Joe > > > > > > On Tue, 18 Sep 2001, Chojin wrote: > > > > > > > My default location is /usr/local/share/snmp/snmpd.conf > > > > I used your file (just modified for 192.168... lan). > > > > To be sure snmpd uses the good file I used -c > > > > #/usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf > > > > #ps aux | grep snmpd > > > > root 81374 7.2 0.4 3256 2624 p0 S 12:25AM 0:00.15 > > > > /usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf > > > > #snmpwalk -v 1 localhost public system > > > > Timeout: No Response from localhost > > > > > > > > As you see, without success... > > > > > > > > ----- Original Message ----- > > > > From: "Joe Clarke" > > > > To: "Chojin" > > > > Cc: "Jean-Francois Dive" ; > > ; > > > > > > > > Sent: Tuesday, September 18, 2001 12:18 AM > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > Not sure. I have snmpd 4.2.1 working perfectly on 4.3-RELEASE and > > > > > 4.4-STABLE as of an hour ago. Attached is my entire config file. I > > keep > > > > > it in /usr/local/lib/snmp (which is the default location). > > > > > > > > > > Joe > > > > > > > > > > On Mon, 17 Sep 2001, Chojin wrote: > > > > > > > > > > > I didn't resolved my problem. > > > > > > Even after upgraded to 4.4-stable (because there was maybe a bug in > > > > snmpd > > > > > > :-p). > > > > > > > > > > > > I don't know what I could do. > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Chojin" > > > > > > To: "Joe Clarke" > > > > > > Cc: "Jean-Francois Dive" ; > > > > ; > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 9:30 PM > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > I tried your snmpd.conf but with no success :'( > > > > > > > ----- Original Message ----- > > > > > > > From: "Joe Clarke" > > > > > > > To: "Chojin" > > > > > > > Cc: "Jean-Francois Dive" ; > > > > > > ; > > > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 8:34 PM > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > Can you send your snmp.conf file? These are the relevant bits > > of > > > > mine: > > > > > > > > > > > > > > > > com2sec local localhost public > > > > > > > > com2sec localrw localhost private > > > > > > > > com2sec mynetwork 172.18.0.0/24 public > > > > > > > > com2sec mynetworkrw 172.18.0.0/24 private > > > > > > > > > > > > > > > > #### > > > > > > > > # Second, map the security names into group names: > > > > > > > > > > > > > > > > # sec.model sec.name > > > > > > > > group LocalRWGroup v1 localrw > > > > > > > > group LocalRWGroup v2c localrw > > > > > > > > group LocalRWGroup usm localrw > > > > > > > > group LocalROGroup v1 local > > > > > > > > group LocalROGroup v2c local > > > > > > > > group LocalROGroup usm local > > > > > > > > group NetROGroup v1 mynetwork > > > > > > > > group NetROGroup v2c mynetwork > > > > > > > > group NetROGroup usm mynetwork > > > > > > > > group NetRWGroup v1 mynetworkrw > > > > > > > > group NetRWGroup v2c mynetworkrw > > > > > > > > group NetRWGroup usm mynetworkrw > > > > > > > > > > > > > > > > #### > > > > > > > > # Third, create a view for us to let the groups have rights to: > > > > > > > > > > > > > > > > # incl/excl subtree mask > > > > > > > > view all included .1 80 > > > > > > > > > > > > > > > > #### > > > > > > > > # Finally, grant the 2 groups access to the 1 view with > > different > > > > > > > > # write permissions: > > > > > > > > > > > > > > > > # context sec.model sec.level match read write > > > > notif > > > > > > > > access LocalROGroup "" any noauth exact all > > none > > > > > > none > > > > > > > > access LocalRWGroup "" any noauth exact all > > all > > > > > > none > > > > > > > > access NetROGroup "" any noauth exact all > > none > > > > > > none > > > > > > > > access NetRWGroup "" any noauth exact all > > all > > > > > > none > > > > > > > > > > > > > > > > > > > > > > > > public@localhost does work on my machine. > > > > > > > > > > > > > > > > Joe > > > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > I used TMRTGCHO as community name before, but since I've got > > this > > > > > > > problem I > > > > > > > > > use now public. > > > > > > > > > Request from localhost or any other interface doesn't work. > > > > > > > > > I cleaned snmpd.log, restarted snmpd: > > > > > > > > > #/usr/local/sbin/snmpd -D -c > > /usr/local/share/snmp/snmpd.conf -l > > > > > > > > > /var/log/snmpd.log > > > > > > > > > > > > > > > > > > and a new one is located at > > > > http://www.tarakan-network.com/snmpd.log > > > > > > (I > > > > > > > did > > > > > > > > > a snmpwalk and snmpget for public@localhost but no success) > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > > To: "Chojin" > > > > > > > > > Sent: Wednesday, September 12, 2001 10:38 AM > > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi (salut) > > > > > > > > > > > > > > > > > > > > In fact, i see some successfull request with the community: > > > > > > > > > > TMRTGCHO and no attemps with the localhost one... seems > > pretty > > > > odd. > > > > > > > did > > > > > > > > > > you only got those requests from localhost not working ? > > > > > > > > > > > > > > > > > > > > Otherwise, purge the log file, be *sure* that no requests > > are > > > > > > comming > > > > > > > from > > > > > > > > > > somewhere else and resart to see some failures... > > > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > > > I launched in debug mode > > > > > > > > > > > #/usr/local/sbin/snmpd -D -c > > > > /usr/local/share/snmp/snmpd.conf -l > > > > > > > > > > > /var/log/snmpd.log > > > > > > > > > > > I attached snmpd.log > > > > > > > > > > > There are so many informations I can't detect the problem > > :pp > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > > > > To: "Chojin" > > > > > > > > > > > Cc: ; > > > > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 9:53 AM > > > > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > i think it is possible to start the snmpd and not send > > it to > > > > > > > > > backgroud, > > > > > > > > > > > > and see if it does printout some error > > messages..Otherwise > > > > use > > > > > > the > > > > > > > > > truss > > > > > > > > > > > > command to follow the syscalls made by the daemon while > > > > > > processing > > > > > > > > > your > > > > > > > > > > > > request, this could point you to a problem.. > > > > > > > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > > > > > > > snmpd.log is empty... > > > > > > > > > > > > > > > > > > > > > > > > > > I did #netstat -an | grep 161 > > > > > > > > > > > > > udp4 0 0 *.161 *.* > > > > > > > > > > > > > > > > > > > > > > > > > > port 161 exists then it should work... > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > > > > > > To: "Chojin" > > > > > > > > > > > > > Cc: ; > > > > > > > > > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 3:21 AM > > > > > > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > > > > > > > > > So you have any traces in a log file or something > > > > similar ? > > > > > > > > > > > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I have a problem with snmpd. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > In fact, one day, for unknown reason ( I didn't > > modify > > > > any > > > > > > > > > > > setting ), > > > > > > > > > > > > > snmpd > > > > > > > > > > > > > > > didn't work anymore: > > > > > > > > > > > > > > > When I do a snmpwalk or snmpget to > > public@localhost it > > > > > > > doesn't > > > > > > > > > > > respond. > > > > > > > > > > > > > > > I checked snmpd, recreated snmpd.conf and launched > > > > again > > > > > > > snmpd > > > > > > > > > > > with -c > > > > > > > > > > > > > > > and -l to be sure it uses the correct files. > > > > > > > > > > > > > > > But even if snmpd is in background process, > > > > > > > public@localhost > > > > > > > > > > > doesn't > > > > > > > > > > > > > work. > > > > > > > > > > > > > > > I don't have any firewall rule that block it. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > #snmpwalk localhost public > > > > > > > > > > > > > > > Timeout: No Response from localhost > > > > > > > > > > > > > > > #snmpget localhost public SysName > > > > > > > > > > > > > > > Timeout: No Response from localhost. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > After I upgraded my system from 4.3-STABLE to > > 4.4-RC, > > > > it > > > > > > > didn't > > > > > > > > > > > change > > > > > > > > > > > > > > > anything for snmpd. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > If someone has got any idea... > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Chojin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 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-questions" in the body of the > > message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 16:36:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id B869F37B401 for ; Mon, 17 Sep 2001 16:36:23 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA17998; Mon, 17 Sep 2001 17:15:07 -0700 (PDT) Date: Mon, 17 Sep 2001 17:15:07 -0700 (PDT) From: Julian Elischer To: =?iso-8859-1?q?Gavin=20Kenny?= Cc: freebsd-hackers@freebsd.org Subject: Re: CAN bus In-Reply-To: <20010917163056.65463.qmail@web20003.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ok so I have to ask... what is CAN bus? (besides a piece of string between 2 cans.). On Mon, 17 Sep 2001, [iso-8859-1] Gavin Kenny wrote: > Hi, > > Is there a CAN bus driver for FreeBSD? > > please cc me your answer > > many thanks > > Gavin > > ____________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk > or your free @yahoo.ie address at http://mail.yahoo.ie > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 16:45:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta11.onebox.com (mta11.onebox.com [64.68.76.121]) by hub.freebsd.org (Postfix) with ESMTP id B503637B406 for ; Mon, 17 Sep 2001 16:45:36 -0700 (PDT) Received: from onebox.com ([10.1.111.7]) by mta11.onebox.com (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20010917234536.JEJS12461.mta11.onebox.com@onebox.com> for ; Mon, 17 Sep 2001 16:45:36 -0700 Received: from [165.121.195.81] by onebox.com with HTTP; Mon, 17 Sep 2001 16:45:36 -0700 Date: Mon, 17 Sep 2001 16:45:36 -0700 Subject: Version of XFree86 in FreeBSD Release 4.4 From: "glenn gombert" To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Message-Id: <20010917234536.JEJS12461.mta11.onebox.com@onebox.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does anyone know what version of XFree86 that is going to be released with FreeBSD 4.4 this weekend?? Thanks, Glenn G. ___________________________________________________________________ To get your own FREE ZDNet Onebox - FREE voicemail, email, and fax, all in one place - sign up today at http://www.zdnetonebox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 16:48:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id 13B0037B406 for ; Mon, 17 Sep 2001 16:48:40 -0700 (PDT) Received: (qmail 70199 invoked by uid 1001); 17 Sep 2001 23:59:44 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Sep 2001 23:59:44 -0000 Date: Mon, 17 Sep 2001 16:59:44 -0700 (PDT) From: Dan To: Subject: hardware chipset compat list Message-ID: <20010917165258.S76124-100000@gandalf.bravenet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The Intel PRO/100 S Server Adapter contains the Intel 82550EY Fast Ethernet controller I am trying to find where i can find the chipset supported page. For future reference. All i see on the main hardware compat page is the make.....if someone could point me to this page...would be most appreciated. # The `fxp' device provides support for the Intel EtherExpress Pro/100B # PCI Fast Ethernet adapters. found this in the LINT kernel....can;t tell again what chipsets. -- Dan +------------------------------------------------------+ | BRAVENET WEB SERVICES | | dan@bravenet.com | | screen;cd /usr/src;make buildworld;cd ~ | | cp MYKERNEL /sys/i386/conf;cd /usr/src | | make buildkernel KERNCONF=MYKERNEL | |make installkernel KERNCONF=MYKERNEL;make installworld| +______________________________________________________+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 17:24:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 08B2937B40D for ; Mon, 17 Sep 2001 17:24:21 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id f8I0OCi93880; Mon, 17 Sep 2001 17:24:12 -0700 (PDT) (envelope-from obrien) Date: Mon, 17 Sep 2001 17:24:08 -0700 From: "David O'Brien" To: glenn gombert Cc: freebsd-hackers@freebsd.org Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Message-ID: <20010917172408.A93860@dragon.nuxi.com> Reply-To: freebsd-hackers@freebsd.org References: <20010917234536.JEJS12461.mta11.onebox.com@onebox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010917234536.JEJS12461.mta11.onebox.com@onebox.com>; from glenngombert@zdnetonebox.com on Mon, Sep 17, 2001 at 04:45:36PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 17, 2001 at 04:45:36PM -0700, glenn gombert wrote: > Does anyone know what version of XFree86 that is going to be released > with FreeBSD 4.4 this weekend?? 3.3.7. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 17:24:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id DFAA637B40B for ; Mon, 17 Sep 2001 17:24:19 -0700 (PDT) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f8I0OI633381; Tue, 18 Sep 2001 02:24:18 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f8I0OnO26677; Tue, 18 Sep 2001 02:24:49 +0200 (CEST) Date: Tue, 18 Sep 2001 02:24:48 +0200 From: Bernd Walter To: Julian Elischer Cc: Gavin Kenny , freebsd-hackers@FreeBSD.ORG Subject: Re: CAN bus Message-ID: <20010918022448.B25833@cicely20.cicely.de> References: <20010917163056.65463.qmail@web20003.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from julian@elischer.org on Mon, Sep 17, 2001 at 05:15:07PM -0700 X-Operating-System: NetBSD cicely20.cicely.de 1.5 sparc Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 17, 2001 at 05:15:07PM -0700, Julian Elischer wrote: > Ok so I have to ask... what is CAN bus? (besides a piece of string > between 2 cans.). CAN stands for Controller Area Network. It's a fieldbus widely used in automation systems. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 17:35:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 8181A37B40E; Mon, 17 Sep 2001 17:35:47 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id SAA18181; Mon, 17 Sep 2001 18:08:02 -0700 (PDT) Date: Mon, 17 Sep 2001 18:08:01 -0700 (PDT) From: Julian Elischer To: current@freebsd.org, hackers@freebsd.org Subject: testig request for your code.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG As many FreeBSD users know, a large set of changes was committed to -current recently, as part of the development of real threading support. Most parts of the kernel were changed to a greater or lesser extent. Some parts have not been able to be tested fully however. If you have a section of the kernel, that you use, but otherwise might not often test (e.g. CODA or a special driver) it may be a good time to compile up a -current kernel and see if it still works. There have been few problems but it will be easier to catch these things right now than to try find problems further down the track. If you find a module that worked in a kernel from before September 11 but does not work on -current, please let Julian@freebsd.org know. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 17:42:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 706A437B410 for ; Mon, 17 Sep 2001 17:42:26 -0700 (PDT) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id f8I0gNO00978; Mon, 17 Sep 2001 17:42:23 -0700 (PDT) (envelope-from jkh@freebsd.org) To: glenngombert@zdnetonebox.com Cc: freebsd-hackers@freebsd.org Subject: Re: Version of XFree86 in FreeBSD Release 4.4 In-Reply-To: <20010917234536.JEJS12461.mta11.onebox.com@onebox.com> References: <20010917234536.JEJS12461.mta11.onebox.com@onebox.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010917174223Z.jkh@freebsd.org> Date: Mon, 17 Sep 2001 17:42:23 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 8 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Does anyone know what version of XFree86 that is going to be released > with FreeBSD 4.4 this weekend?? 3.3.6. We're still waiting for 4.0's "support footprint" to widen a bit more before subjecting people to it by default. Hopefully by 4.5. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 17:48:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 3717737B40E for ; Mon, 17 Sep 2001 17:48:22 -0700 (PDT) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id f8I0mBO01053; Mon, 17 Sep 2001 17:48:11 -0700 (PDT) (envelope-from jkh@freebsd.org) To: freebsd-hackers@freebsd.org, dev-null@NUXI.com Cc: glenngombert@zdnetonebox.com Subject: Re: Version of XFree86 in FreeBSD Release 4.4 In-Reply-To: <20010917172408.A93860@dragon.nuxi.com> References: <20010917234536.JEJS12461.mta11.onebox.com@onebox.com> <20010917172408.A93860@dragon.nuxi.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010917174811J.jkh@freebsd.org> Date: Mon, 17 Sep 2001 17:48:11 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 16 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG No, 3.3.6. There is no such thing as 3.3.7 (at least not according to www.xfree86.org) and even if there were, enough version-number specifics are encoded into sysinstall that I would had to have been told at least a week or two ago if any such version number bump were contemplated. :) - Jordan > On Mon, Sep 17, 2001 at 04:45:36PM -0700, glenn gombert wrote: > > Does anyone know what version of XFree86 that is going to be released > > with FreeBSD 4.4 this weekend?? > > 3.3.7. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 18: 4:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with ESMTP id 3E88A37B412 for ; Mon, 17 Sep 2001 18:04:29 -0700 (PDT) Received: (qmail 90574 invoked from network); 18 Sep 2001 01:04:28 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 18 Sep 2001 01:04:28 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010917174811J.jkh@freebsd.org> Date: Mon, 17 Sep 2001 18:04:16 -0700 (PDT) From: John Baldwin To: Jordan Hubbard Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Cc: glenngombert@zdnetonebox.com, dev-null@NUXI.com, freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-Sep-01 Jordan Hubbard wrote: > No, 3.3.6. There is no such thing as 3.3.7 (at least not according to > www.xfree86.org) and even if there were, enough version-number > specifics are encoded into sysinstall that I would had to have been > told at least a week or two ago if any such version number bump were > contemplated. :) If you look in the release notes from the big 3.3.6a patch, it does call itself 3.3.7. However, the port still calls it 3.3.6. *shrug* > - Jordan > >> On Mon, Sep 17, 2001 at 04:45:36PM -0700, glenn gombert wrote: >> > Does anyone know what version of XFree86 that is going to be released >> > with FreeBSD 4.4 this weekend?? >> >> 3.3.7. >> >> 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 -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 18:42:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from poseidon.student.umd.edu (poseidon.student.umd.edu [129.2.239.23]) by hub.freebsd.org (Postfix) with ESMTP id CAC5C37B406 for ; Mon, 17 Sep 2001 18:42:36 -0700 (PDT) Received: from glue.umd.edu (localhost [127.0.0.1]) by poseidon.student.umd.edu (8.11.6/8.11.6) with ESMTP id f8I1gY000481; Mon, 17 Sep 2001 21:42:34 -0400 (EDT) (envelope-from bfoz@glue.umd.edu) Message-ID: <3BA6A68A.3D962840@glue.umd.edu> Date: Mon, 17 Sep 2001 21:42:34 -0400 From: Brandon Fosdick X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Gavin Kenny Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: CAN bus References: <20010917163056.65463.qmail@web20003.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Gavin Kenny wrote: > Is there a CAN bus driver for FreeBSD? I don't know of any such driver. I'm working on a home automation project that uses CAN so I'll also be needing a driver at some point. Most of the "CAN for a PC" devices I've seen convert the CAN data to RS-232, so I'm not sure that what we need is technically a driver, its more like PPP or other protocols that use the serial port. Don't know enough about the kernel architecture to make any serious conjectures about that. Yet. > please cc me your answer SOP for this list. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 18:54: 4 2001 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 1CA4937B40B; Mon, 17 Sep 2001 18:54:00 -0700 (PDT) Received: from cain.gsoft.com.au (root@spare0.gsoft.com.au [203.38.152.114]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA04962; Tue, 18 Sep 2001 11:23:54 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010917174223Z.jkh@freebsd.org> Date: Tue, 18 Sep 2001 11:23:54 +0930 (CST) From: "Daniel O'Connor" To: Jordan Hubbard Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Cc: freebsd-hackers@freebsd.org, glenngombert@zdnetonebox.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-Sep-2001 Jordan Hubbard wrote: > > Does anyone know what version of XFree86 that is going to be released > > with FreeBSD 4.4 this weekend?? > > 3.3.6. We're still waiting for 4.0's "support footprint" to widen > a bit more before subjecting people to it by default. Hopefully > by 4.5. It's a pitty you can't pick either :) There are, of course, several issue, the most difficult is the fact that packages are built against XFree 3.3.6 and pkg_add can't 'adjust' that during install :( --- 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 Mon Sep 17 20:30:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (okc-94-248-46.mmcable.com [24.94.248.46]) by hub.freebsd.org (Postfix) with SMTP id 0665A37B408 for ; Mon, 17 Sep 2001 20:30:19 -0700 (PDT) Received: (qmail 82975 invoked by uid 100); 18 Sep 2001 03:30:17 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15270.49097.5043.451524@guru.mired.org> Date: Mon, 17 Sep 2001 22:30:17 -0500 To: Stijn Hoop Cc: hackers@freebsd.org Subject: Re: Recent changes to libdialog are weird In-Reply-To: <20010917141108.C455@pcwin002.win.tue.nl> References: <20010917135045.B455@pcwin002.win.tue.nl> <95866.1000728005@axl.seasidesoftware.co.za> <20010917141108.C455@pcwin002.win.tue.nl> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Stijn Hoop types: > I think everyone is qualified - user interface isn't about qualification, > it just needs to be non-intrusive and easily accessible for everyone. [1] Well, if it's not easily accessible to everyone, then it's clearly failed. That's the easy part. As for non-intrusive, I think nearly everyone is equally qualified, including me. I've leared the hard way that UI's that I think of as non-intrusive and obvious are a major PITA for most people, so I stopped doing UI design. Unfortunately, most other designers at my qualification level didn't stop, so most UIs suck. The exceptions are accidental, or the product of those few people who are better-qualifed than "nearly everyone". > [1] Yes this is an ideal which probably can't be achieved - but we can try to > make things better, can't we? :) Depends on how you decide what's better. If you use "feels better to me", then it's not at all clear that you're moving in the right direction. If you use a quantitive measure of some kind - the GOMS keystroke model seems to be a good fit here, but I'm not really qualified - then you can not only tell that it's better, but how much better, and how close to perfect you've gotten. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 17 22: 2:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from creme-brulee.marcuscom.com (rdu57-28-046.nc.rr.com [66.57.28.46]) by hub.freebsd.org (Postfix) with ESMTP id BE27037B408; Mon, 17 Sep 2001 22:01:23 -0700 (PDT) Received: from shumai.marcuscom.com (shumai.marcuscom.com [192.168.1.4]) by creme-brulee.marcuscom.com (8.11.3/8.11.3) with ESMTP id f8I4xd510921; Tue, 18 Sep 2001 00:59:39 -0400 (EDT) (envelope-from marcus@marcuscom.com) Received: from localhost (marcus@localhost) by shumai.marcuscom.com (8.11.3/8.11.3) with ESMTP id f8I51dY75105; Tue, 18 Sep 2001 01:01:39 -0400 (EDT) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: shumai.marcuscom.com: marcus owned process doing -bs Date: Tue, 18 Sep 2001 01:01:39 -0400 (EDT) From: Joe Clarke To: Chojin Cc: Jean-Francois Dive , , Subject: Re: Problem with snmpd In-Reply-To: <01d001c13fcb$6d44f030$0245a8c0@chojin> Message-ID: <20010918010033.X75069-100000@shumai.marcuscom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Why? Since localhost couldn't be resolved correctly, snmpd was trying to match localhost.com when it created its in-memory ACL. You really should fix your localhost resolution. This is what my host file looks like on one of my marcuscom machines: 127.0.0.1 localhost.marcuscom.com localhost Joe On Tue, 18 Sep 2001, Chojin wrote: > # sec.name source community > com2sec local 127.0.0.1 public > com2sec localrw 127.0.0.1 private > > hehe now it works! > > problem came from localhost that was not correctly resolved (but why?) > ----- Original Message ----- > From: "Joe Clarke" > To: "Chojin" > Cc: "Jean-Francois Dive" ; ; > > Sent: Tuesday, September 18, 2001 12:40 AM > Subject: Re: Problem with snmpd > > > > Those look fine. What about nslookup localhost (or if you're using hosts > > before bind, what does /etc/hosts look like)? It may be that localhost > > resolves to something other than 127.0.0.1. Have you tried: > > > > snmpwalk 127.0.0.1 public system > > > > ? That should also work. > > > > Joe > > > > On Tue, 18 Sep 2001, Chojin wrote: > > > > > >I compiled /usr/ports/net/net-snmp > > > me too > > > > > > #netstat -a > > > Active Internet connections (including servers) > > > Proto Recv-Q Send-Q Local Address Foreign Address > (state) > > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1618 > TIME_WAIT > > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1616 > TIME_WAIT > > > tcp4 0 0 chojin.adsl.neri.4110 208.141.100.35.socks > TIME_WAIT > > > tcp4 0 0 chojin.adsl.neri.4108 208.141.100.35.socks > TIME_WAIT > > > tcp4 0 0 chojin.adsl.neri.4107 208.141.100.35.socks > TIME_WAIT > > > tcp4 0 0 chojin.adsl.neri.4105 Hacker.gs.2532 > SYN_SENT > > > tcp4 0 0 chojin.adsl.neri.4103 208.141.100.35.socks > TIME_WAIT > > > tcp4 0 0 chojin.adsl.neri.4100 Hacker.gs.2532 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.smtp rdu57-28-046.nc..1889 > TIME_WAIT > > > tcp4 0 0 chojin.adsl.neri.4098 AFontenayssB-101.3340 > SYN_SENT > > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1615 > TIME_WAIT > > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1613 > TIME_WAIT > > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1612 > TIME_WAIT > > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1610 > TIME_WAIT > > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1609 > TIME_WAIT > > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1607 > TIME_WAIT > > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1606 > TIME_WAIT > > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1604 > TIME_WAIT > > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1603 > TIME_WAIT > > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1601 > TIME_WAIT > > > tcp4 0 0 chojin.adsl.neri.auth Hacker.gs.1628 > > > FIN_WAIT_2 > > > tcp4 0 0 tarakan.lan.tara.pop3 chojin.lan.tarak.1597 > TIME_WAIT > > > tcp4 0 0 chojin.adsl.neri.4084 Hacker.gs.2532 > > > FIN_WAIT_2 > > > tcp4 0 0 chojin.adsl.neri.3832 deneb.freedomshe.4386 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.3682 deneb.freedomshe.4969 > > > ESTABLISHED > > > tcp4 0 0 tarakan.lan.tara.netbi chojin.lan.tarak.1299 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1742 ACBD133F.ipt.aol.1031 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1809 aboukir-101-1-4-.5557 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1493 paris.fr.eu.unde.6667 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1481 undernet.span.ch.6667 > > > ESTABLISHED > > > tcp4 0 0 *.http *.* > LISTEN > > > tcp4 0 0 chojin.adsl.neri.4950 arne.swip.net.6669 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.4730 no-security.net.8367 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.4540 irc.carrier1.net.6667 > > > ESTABLISHED > > > tcp4 0 0 tarakan.lan.tara.ssh chojin.lan.tarak.2099 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.3145 ACBE8C24.ipt.aol.3419 > > > ESTABLISHED > > > tcp4 0 55 tarakan.lan.tara.22006 chojin.lan.tarak.1980 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.3070 entrechat.net.6667 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36867 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36875 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.3337 aboukir-101-1-4-.36870 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1657 skippy.solidshel.2843 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1390 entrechat.net.6668 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1380 powertech.no.eu..afs3- > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1379 uu194-7-27-98.un.8080 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.4267 chojin.adsl.neri.1373 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1373 chojin.adsl.neri.4267 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1742 *.* > LISTEN > > > tcp4 0 0 chojin.adsl.neri.3337 chojin.adsl.neri.1254 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1254 chojin.adsl.neri.3337 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.3337 208.141.100.35.30790 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1208 208.141.100.35.socks > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1204 208.141.100.35.socks > > > ESTABLISHED > > > tcp4 0 0 *.3331 *.* > LISTEN > > > tcp4 0 0 chojin.adsl.neri.1198 skippy.solidshel.2843 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.dec-n *.* > LISTEN > > > tcp4 0 0 chojin.adsl.neri.3337 NS1.ipvh.2787 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.3337 NS1.ipvh.2778 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.3337 box1.TyranZ.3847 > > > ESTABLISHED > > > tcp4 0 0 *.3337 *.* LISTE > N > > > tcp4 0 0 chojin.adsl.neri.1112 skippy.solidshel.2843 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.domai *.* > LISTEN > > > tcp4 0 0 chojin.adsl.neri.1084 TyranZ.20801 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1080 ircnet.kaptech.6667 > > > ESTABLISHED > > > tcp4 0 0 tarakan.lan.tara.6667 tarakan.lan.tara.1072 > > > ESTABLISHED > > > tcp4 0 0 tarakan.lan.tara.1072 tarakan.lan.tara.6667 > > > ESTABLISHED > > > tcp4 0 0 *.2211 *.* > LISTEN > > > tcp4 0 0 chojin.adsl.neri.1065 AVelizy-101-2-2-.1982 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1063 irc1-2.free.fr.6667 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1062 hitomi.ecranbleu.dec-n > > > ESTABLISHED > > > tcp4 0 0 *.12345 *.* > LISTEN > > > tcp4 0 0 chojin.adsl.neri.3682 vega.freedomshel.1534 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.3682 vega.freedomshel.1524 > > > ESTABLISHED > > > tcp4 0 0 *.22011 *.* > LISTEN > > > tcp4 0 48 tarakan.lan.tara.ssh chojin.lan.tarak.1164 > > > ESTABLISHED > > > tcp4 0 0 tarakan.lan.tara.6667 tarakan.lan.tara.1048 > > > ESTABLISHED > > > tcp4 0 0 tarakan.lan.tara.1048 tarakan.lan.tara.6667 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1047 www.skydirect.ne.6667 > > > ESTABLISHED > > > tcp4 0 0 tarakan.lan.tara.4400 tarakan.lan.tara.1042 > > > ESTABLISHED > > > tcp4 0 0 tarakan.lan.tara.1042 tarakan.lan.tara.4400 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1041 bloob.oxyd.fr.4400 > > > ESTABLISHED > > > tcp4 0 0 *.4400 *.* > LISTEN > > > tcp4 0 0 *.6669 *.* > LISTEN > > > tcp4 0 0 *.6668 *.* > LISTEN > > > tcp4 0 0 *.6667 *.* > LISTEN > > > tcp4 0 0 *.6665 *.* > LISTEN > > > tcp4 0 0 *.6666 *.* > LISTEN > > > tcp4 0 0 *.4401 *.* > LISTEN > > > tcp4 0 0 *.13333 *.* > LISTEN > > > tcp4 0 0 chojin.adsl.neri.1035 rinka.nerim.net.6667 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.3682 chojin.adsl.neri.1032 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1032 chojin.adsl.neri.3682 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.1031 irc.planetintern.6667 > > > ESTABLISHED > > > tcp4 0 0 tarakan.lan.tara.21003 chojin.lan.tarak.1163 > > > ESTABLISHED > > > tcp4 0 0 tarakan.lan.tara.22002 chojin.lan.tarak.1162 > > > ESTABLISHED > > > tcp4 0 0 chojin.adsl.neri.2532 *.* > LISTEN > > > tcp4 0 0 chojin.adsl.neri.4695 *.* > LISTEN > > > tcp4 0 0 chojin.adsl.neri.3418 *.* > LISTEN > > > tcp4 0 0 chojin.adsl.neri.4267 *.* > LISTEN > > > tcp4 0 0 chojin.adsl.neri.6632 *.* > LISTEN > > > tcp4 0 0 chojin.adsl.neri.3682 *.* > LISTEN > > > tcp4 0 0 *.netbios-ssn *.* > LISTEN > > > tcp46 0 0 *.22005 *.* > LISTEN > > > tcp4 0 0 *.22005 *.* > LISTEN > > > tcp46 0 0 *.22006 *.* > LISTEN > > > tcp46 0 0 *.22002 *.* > LISTEN > > > tcp4 0 0 *.22006 *.* > LISTEN > > > tcp46 0 0 *.21003 *.* > LISTEN > > > tcp4 0 0 *.21003 *.* > LISTEN > > > tcp4 0 0 *.22002 *.* > LISTEN > > > tcp4 0 0 tarakan.lan.tara.11982 *.* > LISTEN > > > tcp46 0 0 *.auth *.* > LISTEN > > > tcp4 0 0 *.submission *.* > LISTEN > > > tcp4 0 0 *.smtp *.* > LISTEN > > > tcp4 0 0 *.ssh *.* > LISTEN > > > tcp46 0 0 *.ssh *.* > LISTEN > > > tcp4 0 0 *.swat *.* > LISTEN > > > tcp4 0 0 *.auth *.* > LISTEN > > > tcp4 0 0 *.pop3 *.* > LISTEN > > > tcp6 0 0 *.ftp *.* > LISTEN > > > tcp4 0 0 *.ftp *.* > LISTEN > > > tcp4 0 0 *.sunrpc *.* > LISTEN > > > tcp4 0 0 localhost.domain *.* > LISTEN > > > tcp4 0 0 tarakan.lan.tara.domai *.* > LISTEN > > > tcp4 0 0 modem-adsl.domain *.* > LISTEN > > > udp4 0 0 *.4659 *.* > > > udp4 0 0 *.snmp *.* > > > udp4 0 0 localhost.3336 *.* > > > udp4 0 0 *.3704 *.* > > > udp4 0 0 *.2409 *.* > > > udp4 0 0 chojin.adsl.neri.domai *.* > > > udp4 0 0 *.1488 *.* > > > udp4 0 0 *.* *.* > > > udp4 0 0 *.1380 *.* > > > udp4 0 0 *.afs3-bos *.* > > > udp4 0 0 *.4183 *.* > > > udp4 0 0 *.1291 *.* > > > udp4 0 0 *.1244 *.* > > > udp4 0 0 tarakan.lan.tara.netbi *.* > > > udp4 0 0 tarakan.lan.tara.netbi *.* > > > udp4 0 0 *.netbios-dgm *.* > > > udp4 0 0 *.netbios-ns *.* > > > udp4 0 0 *.10000 *.* > > > udp4 0 0 chojin.adsl.neri.1124 chojin.adsl.neri.syslo > > > udp4 0 0 *.bootps *.* > > > udp4 0 0 *.sunrpc *.* > > > udp4 0 0 *.1028 *.* > > > udp4 0 0 localhost.domain *.* > > > udp4 0 0 tarakan.lan.tara.domai *.* > > > udp4 0 0 modem-adsl.domain *.* > > > udp4 0 0 *.syslog *.* > > > udp6 0 0 *.syslog *.* > > > ip 4 0 0 *.* *.* > > > icm4 0 0 *.* *.* > > > ip64 0 0 *.* *.* > > > Netgraph sockets > > > Type Recv-Q Send-Q Node Address #Hooks > > > ctrl 0 0 > > > data 0 0 > > > Active UNIX domain sockets > > > Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr > > > d04c2d80 stream 0 0 d04f9580 0 0 0 > > > /var/pwcheck/pwcheck > > > d04c2e40 stream 0 0 d04f7240 0 0 0 > > > /tmp/.s.PGSQL.5432 > > > d04c2f40 stream 0 0 d04bd800 0 0 0 > > > /var/run/ndc > > > d04c2d00 dgram 0 0 0 d04c2fc0 0 d04c2c80 > > > d04c2c80 dgram 0 0 0 d04c2fc0 0 d04c2e00 > > > d04c2e00 dgram 0 0 0 d04c2fc0 0 d04c2dc0 > > > d04c2dc0 dgram 0 0 0 d04c2fc0 0 d04c2e80 > > > d04c2e80 dgram 0 0 0 d04c2fc0 0 d04c2ec0 > > > d04c2ec0 dgram 0 0 0 d04c2fc0 0 d04c2f00 > > > d04c2f00 dgram 0 0 0 d04c2fc0 0 d04c2f80 > > > d04c2f80 dgram 0 0 0 d04c2fc0 0 0 > > > d04c2fc0 dgram 0 0 d04be940 0 d04c2d00 0 > > > /var/run/log > > > > > > #ifconfig -a > > > ed0: flags=8843 mtu 1500 > > > inet 10.0.0.10 netmask 0xffffff00 broadcast 10.0.0.255 > > > inet6 fe80::24f:49ff:fe0a:b2dd%ed0 prefixlen 64 scopeid 0x1 > > > ether 00:4f:49:0a:b2:dd > > > ed1: flags=8843 mtu 1500 > > > inet 192.168.69.1 netmask 0xffffff00 broadcast 192.168.69.255 > > > inet6 fe80::5054:5ff:fef9:761d%ed1 prefixlen 64 scopeid 0x2 > > > ether 52:54:05:f9:76:1d > > > lp0: flags=8810 mtu 1500 > > > faith0: flags=8000 mtu 1500 > > > stf0: flags=0<> mtu 1280 > > > lo0: flags=8049 mtu 16384 > > > inet6 ::1 prefixlen 128 > > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 > > > inet 127.0.0.1 netmask 0xff000000 > > > ppp0: flags=8010 mtu 1500 > > > sl0: flags=c010 mtu 552 > > > tun0: flags=8051 mtu 1492 > > > inet6 fe80::24f:49ff:fe0a:b2dd%tun0 prefixlen 64 scopeid 0x9 > > > inet 62.4.22.98 --> 194.206.78.3 netmask 0xff000000 > > > Opened by PID 168 > > > > > > Anything wrong? > > > > > > ----- Original Message ----- > > > From: "Joe Clarke" > > > To: "Chojin" > > > Cc: "Jean-Francois Dive" ; > ; > > > > > > Sent: Tuesday, September 18, 2001 12:31 AM > > > Subject: Re: Problem with snmpd > > > > > > > > > > What does netstat -a and ifconfig -a show? Something is not right on > your > > > > machine. I compiled /usr/ports/net/net-snmp and it worked out of the > box. > > > > I'm using the default /usr/local/etc/rc.d/snmpd.sh script to start > snmpd. > > > > > > > > Joe > > > > > > > > On Tue, 18 Sep 2001, Chojin wrote: > > > > > > > > > My default location is /usr/local/share/snmp/snmpd.conf > > > > > I used your file (just modified for 192.168... lan). > > > > > To be sure snmpd uses the good file I used -c > > > > > #/usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf > > > > > #ps aux | grep snmpd > > > > > root 81374 7.2 0.4 3256 2624 p0 S 12:25AM 0:00.15 > > > > > /usr/local/sbin/snmpd -c /usr/local/share/snmp/snmpd.conf > > > > > #snmpwalk -v 1 localhost public system > > > > > Timeout: No Response from localhost > > > > > > > > > > As you see, without success... > > > > > > > > > > ----- Original Message ----- > > > > > From: "Joe Clarke" > > > > > To: "Chojin" > > > > > Cc: "Jean-Francois Dive" ; > > > ; > > > > > > > > > > Sent: Tuesday, September 18, 2001 12:18 AM > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > Not sure. I have snmpd 4.2.1 working perfectly on 4.3-RELEASE and > > > > > > 4.4-STABLE as of an hour ago. Attached is my entire config file. > I > > > keep > > > > > > it in /usr/local/lib/snmp (which is the default location). > > > > > > > > > > > > Joe > > > > > > > > > > > > On Mon, 17 Sep 2001, Chojin wrote: > > > > > > > > > > > > > I didn't resolved my problem. > > > > > > > Even after upgraded to 4.4-stable (because there was maybe a bug > in > > > > > snmpd > > > > > > > :-p). > > > > > > > > > > > > > > I don't know what I could do. > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > From: "Chojin" > > > > > > > To: "Joe Clarke" > > > > > > > Cc: "Jean-Francois Dive" ; > > > > > ; > > > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 9:30 PM > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > I tried your snmpd.conf but with no success :'( > > > > > > > > ----- Original Message ----- > > > > > > > > From: "Joe Clarke" > > > > > > > > To: "Chojin" > > > > > > > > Cc: "Jean-Francois Dive" ; > > > > > > > ; > > > > > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 8:34 PM > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > Can you send your snmp.conf file? These are the relevant > bits > > > of > > > > > mine: > > > > > > > > > > > > > > > > > > com2sec local localhost public > > > > > > > > > com2sec localrw localhost private > > > > > > > > > com2sec mynetwork 172.18.0.0/24 public > > > > > > > > > com2sec mynetworkrw 172.18.0.0/24 private > > > > > > > > > > > > > > > > > > #### > > > > > > > > > # Second, map the security names into group names: > > > > > > > > > > > > > > > > > > # sec.model sec.name > > > > > > > > > group LocalRWGroup v1 localrw > > > > > > > > > group LocalRWGroup v2c localrw > > > > > > > > > group LocalRWGroup usm localrw > > > > > > > > > group LocalROGroup v1 local > > > > > > > > > group LocalROGroup v2c local > > > > > > > > > group LocalROGroup usm local > > > > > > > > > group NetROGroup v1 mynetwork > > > > > > > > > group NetROGroup v2c mynetwork > > > > > > > > > group NetROGroup usm mynetwork > > > > > > > > > group NetRWGroup v1 mynetworkrw > > > > > > > > > group NetRWGroup v2c mynetworkrw > > > > > > > > > group NetRWGroup usm mynetworkrw > > > > > > > > > > > > > > > > > > #### > > > > > > > > > # Third, create a view for us to let the groups have rights > to: > > > > > > > > > > > > > > > > > > # incl/excl subtree mask > > > > > > > > > view all included .1 80 > > > > > > > > > > > > > > > > > > #### > > > > > > > > > # Finally, grant the 2 groups access to the 1 view with > > > different > > > > > > > > > # write permissions: > > > > > > > > > > > > > > > > > > # context sec.model sec.level match read > write > > > > > notif > > > > > > > > > access LocalROGroup "" any noauth exact all > > > none > > > > > > > none > > > > > > > > > access LocalRWGroup "" any noauth exact all > > > all > > > > > > > none > > > > > > > > > access NetROGroup "" any noauth exact all > > > none > > > > > > > none > > > > > > > > > access NetRWGroup "" any noauth exact all > > > all > > > > > > > none > > > > > > > > > > > > > > > > > > > > > > > > > > > public@localhost does work on my machine. > > > > > > > > > > > > > > > > > > Joe > > > > > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > I used TMRTGCHO as community name before, but since I've > got > > > this > > > > > > > > problem I > > > > > > > > > > use now public. > > > > > > > > > > Request from localhost or any other interface doesn't > work. > > > > > > > > > > I cleaned snmpd.log, restarted snmpd: > > > > > > > > > > #/usr/local/sbin/snmpd -D -c > > > /usr/local/share/snmp/snmpd.conf -l > > > > > > > > > > /var/log/snmpd.log > > > > > > > > > > > > > > > > > > > > and a new one is located at > > > > > http://www.tarakan-network.com/snmpd.log > > > > > > > (I > > > > > > > > did > > > > > > > > > > a snmpwalk and snmpget for public@localhost but no > success) > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > > > To: "Chojin" > > > > > > > > > > Sent: Wednesday, September 12, 2001 10:38 AM > > > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi (salut) > > > > > > > > > > > > > > > > > > > > > > In fact, i see some successfull request with the > community: > > > > > > > > > > > TMRTGCHO and no attemps with the localhost one... seems > > > pretty > > > > > odd. > > > > > > > > did > > > > > > > > > > > you only got those requests from localhost not working ? > > > > > > > > > > > > > > > > > > > > > > Otherwise, purge the log file, be *sure* that no > requests > > > are > > > > > > > comming > > > > > > > > from > > > > > > > > > > > somewhere else and resart to see some failures... > > > > > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > > > > > I launched in debug mode > > > > > > > > > > > > #/usr/local/sbin/snmpd -D -c > > > > > /usr/local/share/snmp/snmpd.conf -l > > > > > > > > > > > > /var/log/snmpd.log > > > > > > > > > > > > I attached snmpd.log > > > > > > > > > > > > There are so many informations I can't detect the > problem > > > :pp > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > > > > > To: "Chojin" > > > > > > > > > > > > Cc: ; > > > > > > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 9:53 AM > > > > > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > i think it is possible to start the snmpd and not > send > > > it to > > > > > > > > > > backgroud, > > > > > > > > > > > > > and see if it does printout some error > > > messages..Otherwise > > > > > use > > > > > > > the > > > > > > > > > > truss > > > > > > > > > > > > > command to follow the syscalls made by the daemon > while > > > > > > > processing > > > > > > > > > > your > > > > > > > > > > > > > request, this could point you to a problem.. > > > > > > > > > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, 12 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > snmpd.log is empty... > > > > > > > > > > > > > > > > > > > > > > > > > > > > I did #netstat -an | grep 161 > > > > > > > > > > > > > > udp4 0 0 *.161 *.* > > > > > > > > > > > > > > > > > > > > > > > > > > > > port 161 exists then it should work... > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > > > > > From: "Jean-Francois Dive" > > > > > > > > > > > > > > To: "Chojin" > > > > > > > > > > > > > > Cc: ; > > > > > > > > > > > > > > > > > > > > > > Sent: Wednesday, September 12, 2001 3:21 AM > > > > > > > > > > > > > > Subject: Re: Problem with snmpd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > So you have any traces in a log file or > something > > > > > similar ? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > JeF > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, 11 Sep 2001, Chojin wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I have a problem with snmpd. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > In fact, one day, for unknown reason ( I > didn't > > > modify > > > > > any > > > > > > > > > > > > setting ), > > > > > > > > > > > > > > snmpd > > > > > > > > > > > > > > > > didn't work anymore: > > > > > > > > > > > > > > > > When I do a snmpwalk or snmpget to > > > public@localhost it > > > > > > > > doesn't > > > > > > > > > > > > respond. > > > > > > > > > > > > > > > > I checked snmpd, recreated snmpd.conf and > launched > > > > > again > > > > > > > > snmpd > > > > > > > > > > > > with -c > > > > > > > > > > > > > > > > and -l to be sure it uses the correct files. > > > > > > > > > > > > > > > > But even if snmpd is in background process, > > > > > > > > public@localhost > > > > > > > > > > > > doesn't > > > > > > > > > > > > > > work. > > > > > > > > > > > > > > > > I don't have any firewall rule that block it. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > #snmpwalk localhost public > > > > > > > > > > > > > > > > Timeout: No Response from localhost > > > > > > > > > > > > > > > > #snmpget localhost public SysName > > > > > > > > > > > > > > > > Timeout: No Response from localhost. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > After I upgraded my system from 4.3-STABLE to > > > 4.4-RC, > > > > > it > > > > > > > > didn't > > > > > > > > > > > > change > > > > > > > > > > > > > > > > anything for snmpd. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > If someone has got any idea... > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Chojin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 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-questions" in the body of the > > > message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > > > > with "unsubscribe freebsd-questions" in the body of the > message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > > > with "unsubscribe freebsd-questions" in the body of the > message > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 5:10:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 02FE137B40A; Tue, 18 Sep 2001 05:10:06 -0700 (PDT) Received: from vega.vega.com (root@dialup13-46.iptelecom.net.ua [212.9.229.46]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id PAA21866; Tue, 18 Sep 2001 15:09:29 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.4/8.11.3) with ESMTP id f8IC80917102; Tue, 18 Sep 2001 15:08:00 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3BA7397D.A82C213@FreeBSD.org> Date: Tue, 18 Sep 2001 15:09:33 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: chris@calldei.com Cc: phk@critter.freebsd.dk, brent@rcfile.org, current@FreeBSD.org, hackers@FreeBSD.org, marcel@FreeBSD.org Subject: Re: Junior Kernel Hacker task: improve vnode->v_tag References: <20010908030110.E548@holly.calldei.com> <200109081154.OAA95138@www.abc.com.ua> <20010908150620.F548@holly.calldei.com> Content-Type: multipart/mixed; boundary="------------EB2B6B9ED6329EFA77147776" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------EB2B6B9ED6329EFA77147776 Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Chris Costello wrote: > On Saturday, September 08, 2001, Maxim Sobolev wrote: > > I don't like idea to hardcode the same string ("procfs"), with the > > same meaning in several places across kernel. As for your proposition > > to use f_fstypename to set v_tag, it is even more bogus because > > value of the f_fstypename is supplied from the user level, so > > potentially it could be anything and we can't make any reasonable > > assumptions about mapping between its value and type of the filesystem > > in question. > > How do you figure? The contents if `f_fstypename' must match > a configured file system exactly, so it could _not_ be anything. > To quote sys/kern/vfs_syscalls.c:mount(): Oh, yes, you are correct obviously (don't know what I was thinking about). In this case, it looks like v_tag is redundant, because f_fstypename could be used instead in a few places where v_tag is abused (the same applies to the statfs.f_type because essentually it is the same thing as v_tag). Poul, what do you think about it? In the meantime, I found another place in the kernel where VT_* macros are [ab]used - it is Linuxlator, attached please find patches to fix it - please review. -Maxim --------------EB2B6B9ED6329EFA77147776 Content-Type: text/plain; charset=x-user-defined; name="linux_stats.c.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="linux_stats.c.diff" Index: linux_stats.c =================================================================== RCS file: /home/ncvs/src/sys/compat/linux/linux_stats.c,v retrieving revision 1.37 diff -d -u -r1.37 linux_stats.c --- linux_stats.c 2001/09/12 08:36:57 1.37 +++ linux_stats.c 2001/09/18 11:52:02 @@ -187,10 +187,6 @@ l_int f_spare[6]; }; -#ifndef VT_NWFS -#define VT_NWFS VT_TFS /* XXX - bug compat. with sys/fs/nwfs/nwfs_node.h */ -#endif - #define LINUX_CODA_SUPER_MAGIC 0x73757245L #define LINUX_EXT2_SUPER_MAGIC 0xEF53L #define LINUX_HPFS_SUPER_MAGIC 0xf995e849L @@ -202,34 +198,30 @@ #define LINUX_PROC_SUPER_MAGIC 0x9fa0L #define LINUX_UFS_SUPER_MAGIC 0x00011954L /* XXX - UFS_MAGIC in Linux */ -/* - * ext2fs uses the VT_UFS tag. A mounted ext2 filesystem will therefore - * be seen as an ufs filesystem. - */ static long -bsd_to_linux_ftype(int tag) +bsd_to_linux_ftype(const char *fstypename) { - switch (tag) { - case VT_CODA: + if (strcmp(fstypename, "coda") == 0) return (LINUX_CODA_SUPER_MAGIC); - case VT_HPFS: + else if (strcmp(fstypename, "hpfs") == 0) return (LINUX_HPFS_SUPER_MAGIC); - case VT_ISOFS: + else if (strcmp(fstypename, "cd9660") == 0) return (LINUX_ISOFS_SUPER_MAGIC); - case VT_MSDOSFS: + else if (strcmp(fstypename, "msdosfs") == 0) return (LINUX_MSDOS_SUPER_MAGIC); - case VT_NFS: + else if (strcmp(fstypename, "nfs") == 0) return (LINUX_NFS_SUPER_MAGIC); - case VT_NTFS: + else if (strcmp(fstypename, "ntfs") == 0) return (LINUX_NTFS_SUPER_MAGIC); - case VT_NWFS: + else if (strcmp(fstypename, "nwfs") == 0) return (LINUX_NCP_SUPER_MAGIC); - case VT_PROCFS: + else if (strcmp(fstypename, "procfs") == 0) return (LINUX_PROC_SUPER_MAGIC); - case VT_UFS: + else if (strcmp(fstypename, "ufs") == 0) return (LINUX_UFS_SUPER_MAGIC); - } + else if (strcmp(fstypename, "ext2fs") == 0) + return (LINUX_EXT2_SUPER_MAGIC); return (0L); } @@ -265,7 +257,7 @@ if (error) return error; bsd_statfs->f_flags = mp->mnt_flag & MNT_VISFLAGMASK; - linux_statfs.f_type = bsd_to_linux_ftype(bsd_statfs->f_type); + linux_statfs.f_type = bsd_to_linux_ftype(bsd_statfs->f_fstypename); linux_statfs.f_bsize = bsd_statfs->f_bsize; linux_statfs.f_blocks = bsd_statfs->f_blocks; linux_statfs.f_bfree = bsd_statfs->f_bfree; @@ -301,7 +293,7 @@ if (error) return error; bsd_statfs->f_flags = mp->mnt_flag & MNT_VISFLAGMASK; - linux_statfs.f_type = bsd_to_linux_ftype(bsd_statfs->f_type); + linux_statfs.f_type = bsd_to_linux_ftype(bsd_statfs->f_fstypename); linux_statfs.f_bsize = bsd_statfs->f_bsize; linux_statfs.f_blocks = bsd_statfs->f_blocks; linux_statfs.f_bfree = bsd_statfs->f_bfree; --------------EB2B6B9ED6329EFA77147776-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 5:16:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from holly.dyndns.org (adsl-208-191-154-55.dsl.hstntx.swbell.net [208.191.154.55]) by hub.freebsd.org (Postfix) with ESMTP id 15AF237B412; Tue, 18 Sep 2001 05:16:33 -0700 (PDT) Received: (from chris@localhost) by holly.dyndns.org (8.11.4/8.9.3) id f8ICG6b30888; Tue, 18 Sep 2001 07:16:06 -0500 (CDT) (envelope-from chris) Date: Tue, 18 Sep 2001 07:15:55 -0500 From: Chris Costello To: Maxim Sobolev Cc: phk@critter.freebsd.dk, brent@rcfile.org, current@FreeBSD.ORG, hackers@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: Junior Kernel Hacker task: improve vnode->v_tag Message-ID: <20010918071554.H17889@holly.calldei.com> Reply-To: chris@FreeBSD.ORG References: <20010908030110.E548@holly.calldei.com> <200109081154.OAA95138@www.abc.com.ua> <20010908150620.F548@holly.calldei.com> <3BA7397D.A82C213@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BA7397D.A82C213@FreeBSD.org>; from sobomax@FreeBSD.ORG on Tue, Sep 18, 2001 at 03:09:33PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday, September 18, 2001, Maxim Sobolev wrote: > Oh, yes, you are correct obviously (don't know what I was thinking about). In this > case, it looks like v_tag is redundant, because f_fstypename could be used instead > in a few places where v_tag is abused (the same applies to the statfs.f_type > because essentually it is the same thing as v_tag). Poul, what do you think about > it? In the meantime, I found another place in the kernel where VT_* macros are > [ab]used - it is Linuxlator, attached please find patches to fix it - please > review. Actually, I've got work that's a lot like the patch you attached to this message; when I can merge some of the latest changes, I'll have a diff at least to KSE_PRE_MILESTONE_2. Give me more time and I'll have a diff to HEAD. -- +-------------------+--------------------------------------------+ | Chris Costello | Performance is easier to add than clarity. | | chris@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 Sep 18 5:33: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id AF13A37B40D; Tue, 18 Sep 2001 05:33:00 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.4/8.11.4) with ESMTP id f8ICWvv25284; Tue, 18 Sep 2001 14:32:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Maxim Sobolev Cc: chris@calldei.com, brent@rcfile.org, current@FreeBSD.ORG, hackers@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: Junior Kernel Hacker task: improve vnode->v_tag In-Reply-To: Your message of "Tue, 18 Sep 2001 15:09:33 +0300." <3BA7397D.A82C213@FreeBSD.org> Date: Tue, 18 Sep 2001 14:32:57 +0200 Message-ID: <25282.1000816377@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3BA7397D.A82C213@FreeBSD.org>, Maxim Sobolev writes: >> How do you figure? The contents if `f_fstypename' must match >> a configured file system exactly, so it could _not_ be anything. >> To quote sys/kern/vfs_syscalls.c:mount(): > >Oh, yes, you are correct obviously (don't know what I was thinking about). In this >case, it looks like v_tag is redundant, because f_fstypename could be used instead >in a few places where v_tag is abused (the same applies to the statfs.f_type >because essentually it is the same thing as v_tag). Poul, what do you think about >it? In the meantime, I found another place in the kernel where VT_* macros are >[ab]used - it is Linuxlator, attached please find patches to fix it - please >review. Sounds like a plan, and a quick eyeball of the patch shows no trouble. Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 6:59:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (Postfix) with ESMTP id D0DD837B41C; Tue, 18 Sep 2001 06:59:35 -0700 (PDT) Received: from mailhost.BayNetworks.COM (ns1.baynetworks.com [134.177.1.107]) by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id GAA24156; Tue, 18 Sep 2001 06:47:09 -0700 (PDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id GAA08652; Tue, 18 Sep 2001 06:55:58 -0700 (PDT) Received: from tuva.engeast.baynetworks.com (tuva [192.32.150.102]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id JAA25623; Tue, 18 Sep 2001 09:58:10 -0400 for Message-Id: <200109181358.JAA25623@pobox.engeast.BayNetworks.COM> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: "Daniel O'Connor" Cc: Jordan Hubbard , freebsd-hackers@freebsd.org, glenngombert@zdnetonebox.com Subject: Re: Version of XFree86 in FreeBSD Release 4.4 In-Reply-To: Message from Daniel O'Connor of "Tue, 18 Sep 2001 11:23:54 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Sep 2001 09:58:11 -0400 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG doconnor@gsoft.com.au said: :- It's a pitty you can't pick either :) :- There are, of course, several issue, the most difficult is the fact :- that packages are built against XFree 3.3.6 and pkg_add can't 'adjust' :- that during install :( Seconded. We are in a straddling situation where some cards are better supported by 4.0 and other by 3.x. I've played with manually symlinking the stuff in /var/db, but I'd hardly recommend that as a general solution. I know it is slimy, but couldn't there be a dummy "port" just called "XFree86" that is what most other ports depend on? The minority of ports that actually care what version of X is installed could always use the version-specific names... -- Robert Withrow -- (+1 978 288 8256, ESN 248) BWithrow@NortelNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 7: 5:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from r220-1.rz.RWTH-Aachen.DE (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by hub.freebsd.org (Postfix) with ESMTP id 5587037B407; Tue, 18 Sep 2001 07:05:40 -0700 (PDT) Received: from r220-1.rz.RWTH-Aachen.DE (relay2.RWTH-Aachen.DE [134.130.3.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3-2) with ESMTP id f8IE5c609815; Tue, 18 Sep 2001 16:05:39 +0200 (MEST) Received: from kawoserv.kawo2.rwth-aachen.de (root@kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3/6) with ESMTP id f8IE5cx09811; Tue, 18 Sep 2001 16:05:38 +0200 (MEST) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id QAA32682; Tue, 18 Sep 2001 16:05:36 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f8IE63F90901; Tue, 18 Sep 2001 16:06:03 +0200 (CEST) (envelope-from alex) Date: Tue, 18 Sep 2001 16:06:02 +0200 From: Alexander Langer To: Robert Withrow Cc: "Daniel O'Connor" , Jordan Hubbard , freebsd-hackers@FreeBSD.ORG, glenngombert@zdnetonebox.com Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Message-ID: <20010918160602.B90244@fump.kawo2.rwth-aachen.de> References: <200109181358.JAA25623@pobox.engeast.BayNetworks.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109181358.JAA25623@pobox.engeast.BayNetworks.COM>; from bwithrow@nortelnetworks.com on Tue, Sep 18, 2001 at 09:58:11AM -0400 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Robert Withrow (bwithrow@nortelnetworks.com): > I know it is slimy, but couldn't there be a dummy "port" just > called "XFree86" that is what most other ports depend on? The minority > of ports that actually care what version of X is installed could always > use the version-specific names... Would be nice if we had a package system that lets you just install - let me call them - "features", such as a "XFree86" feature, other ports could depend on. Multiple packages could supply this feature then and ports could also say if they depend on a specific version. Alex, hiding in a dark corner. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 7:13:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shikima.mine.nu (pc2-card3-0-cust61.cdf.cable.ntl.com [213.107.2.61]) by hub.freebsd.org (Postfix) with ESMTP id EF1A337B41B for ; Tue, 18 Sep 2001 07:13:23 -0700 (PDT) Received: from rasputin by shikima.mine.nu with local (Exim 3.33 #1) id 15jLcf-000BHz-00; Tue, 18 Sep 2001 15:13:13 +0100 Date: Tue, 18 Sep 2001 15:13:13 +0100 From: Rasputin To: Alexander Langer Cc: hackers@freebsd.org Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Message-ID: <20010918151313.A43143@shikima.mine.nu> Reply-To: Rasputin References: <200109181358.JAA25623@pobox.engeast.BayNetworks.COM> <20010918160602.B90244@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010918160602.B90244@fump.kawo2.rwth-aachen.de>; from alex@big.endian.de on Tue, Sep 18, 2001 at 04:06:02PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Alexander Langer [010918 15:07]: > Thus spake Robert Withrow (bwithrow@nortelnetworks.com): > > > I know it is slimy, but couldn't there be a dummy "port" just > > called "XFree86" that is what most other ports depend on? The minority > > of ports that actually care what version of X is installed could always > > use the version-specific names... > > Would be nice if we had a package system that lets you just install > - let me call them - "features", such as a "XFree86" feature, other > ports could depend on. Multiple packages could supply this feature > then and ports could also say if they depend on a specific version. > > Alex, > hiding in a dark corner. Isn't this what XFREE86_VERSION does? -- Reality is for those who can't face Science Fiction. Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 7:18:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 25D2037B405; Tue, 18 Sep 2001 07:18:52 -0700 (PDT) Received: from cain.gsoft.com.au (darius@midget.dons.net.au [203.31.81.7]) by midget.dons.net.au (8.11.6/8.9.3) with ESMTP id f8IEIYV49124; Tue, 18 Sep 2001 23:48:34 +0930 (CST) (envelope-from darius@dons.net.au) Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010918160602.B90244@fump.kawo2.rwth-aachen.de> Date: Tue, 18 Sep 2001 23:48:34 +0930 (CST) From: "Daniel O'Connor" To: Alexander Langer Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Cc: glenngombert@zdnetonebox.com, freebsd-hackers@FreeBSD.ORG, Jordan Hubbard , "Daniel O'Connor" , Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-Sep-2001 Alexander Langer wrote: > Thus spake Robert Withrow (bwithrow@nortelnetworks.com): > > > I know it is slimy, but couldn't there be a dummy "port" just > > called "XFree86" that is what most other ports depend on? The minority > > of ports that actually care what version of X is installed could always > > use the version-specific names... > > Would be nice if we had a package system that lets you just install > - let me call them - "features", such as a "XFree86" feature, other > ports could depend on. Multiple packages could supply this feature > then and ports could also say if they depend on a specific version. Yes, I suspect the answer is along the lines of 'yes that's coming' :) The previous suggestion (have a generic XFree86 port) is a) hacky, but b) workable in the current package framework I suspect.. Probably have to trap a port guru and subject them to torture before it got implemented though ;) --- 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 Tue Sep 18 7:32:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from r220-1.rz.RWTH-Aachen.DE (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by hub.freebsd.org (Postfix) with ESMTP id 98B9637B418 for ; Tue, 18 Sep 2001 07:32:16 -0700 (PDT) Received: from r220-1.rz.RWTH-Aachen.DE (relay2.RWTH-Aachen.DE [134.130.3.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3-2) with ESMTP id f8IEWF615928; Tue, 18 Sep 2001 16:32:15 +0200 (MEST) Received: from kawoserv.kawo2.rwth-aachen.de (root@kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3/6) with ESMTP id f8IEWEx15924; Tue, 18 Sep 2001 16:32:14 +0200 (MEST) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id QAA01418; Tue, 18 Sep 2001 16:32:12 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f8IEWdY91020; Tue, 18 Sep 2001 16:32:39 +0200 (CEST) (envelope-from alex) Date: Tue, 18 Sep 2001 16:32:38 +0200 From: Alexander Langer To: Rasputin Cc: hackers@FreeBSD.ORG Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Message-ID: <20010918163238.E90244@fump.kawo2.rwth-aachen.de> References: <200109181358.JAA25623@pobox.engeast.BayNetworks.COM> <20010918160602.B90244@fump.kawo2.rwth-aachen.de> <20010918151313.A43143@shikima.mine.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010918151313.A43143@shikima.mine.nu>; from rasputin@submonkey.net on Tue, Sep 18, 2001 at 03:13:13PM +0100 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Rasputin (rasputin@submonkey.net): > Isn't this what XFREE86_VERSION does? Nope, this is a build-time option. I can't remember a commit to the pkg tools that check for XFREE86_VERSION. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 7:34:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from r220-1.rz.RWTH-Aachen.DE (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by hub.freebsd.org (Postfix) with ESMTP id 4895137B40F; Tue, 18 Sep 2001 07:34:26 -0700 (PDT) Received: from r220-1.rz.RWTH-Aachen.DE (relay2.RWTH-Aachen.DE [134.130.3.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3-2) with ESMTP id f8IEXY616099; Tue, 18 Sep 2001 16:33:34 +0200 (MEST) Received: from kawoserv.kawo2.rwth-aachen.de (root@kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3/6) with ESMTP id f8IEXRx16089; Tue, 18 Sep 2001 16:33:27 +0200 (MEST) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id QAA01472; Tue, 18 Sep 2001 16:33:25 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f8IEXqA91027; Tue, 18 Sep 2001 16:33:53 +0200 (CEST) (envelope-from alex) Date: Tue, 18 Sep 2001 16:33:52 +0200 From: Alexander Langer To: "Daniel O'Connor" Cc: glenngombert@zdnetonebox.com, freebsd-hackers@FreeBSD.ORG, Jordan Hubbard , "Daniel O'Connor" , Robert Withrow Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Message-ID: <20010918163352.F90244@fump.kawo2.rwth-aachen.de> References: <20010918160602.B90244@fump.kawo2.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from darius@dons.net.au on Tue, Sep 18, 2001 at 11:48:34PM +0930 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Daniel O'Connor (darius@dons.net.au): > Yes, I suspect the answer is along the lines of 'yes that's coming' :) :-) > The previous suggestion (have a generic XFree86 port) is a) hacky, but b) > workable in the current package framework I suspect.. Yes, would be a nice workaround. I don't use packages, though :) Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 8:33:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id C597337B40C for ; Tue, 18 Sep 2001 08:33:47 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f8IFXku10912; Tue, 18 Sep 2001 09:33:46 -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.11.3/8.11.4) with ESMTP id f8IFXjW64533; Tue, 18 Sep 2001 09:33:45 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109181533.f8IFXjW64533@harmony.village.org> To: Julian Elischer Subject: Re: CAN bus Cc: =?iso-8859-1?q?Gavin=20Kenny?= , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Sep 2001 17:15:07 PDT." References: Date: Tue, 18 Sep 2001 09:33:45 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message Julian Elischer writes: : Ok so I have to ask... what is CAN bus? (besides a piece of string : between 2 cans.). A data acquisition bus that was popular in manufacturing a few years ago. Don't know if it is still popular or not. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 9:25:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.yadt.co.uk (yadt.demon.co.uk [158.152.4.134]) by hub.freebsd.org (Postfix) with SMTP id C2CD137B40D for ; Tue, 18 Sep 2001 09:23:51 -0700 (PDT) Received: (qmail 33348 invoked from network); 18 Sep 2001 16:23:08 -0000 Received: from gattaca.local.yadt.co.uk (HELO mail.gattaca.yadt.co.uk) (qmailr@10.0.0.2) by xfiles.yadt.co.uk with SMTP; 18 Sep 2001 16:23:08 -0000 Received: (qmail 7351 invoked by uid 1000); 18 Sep 2001 16:23:08 -0000 Date: Tue, 18 Sep 2001 17:23:08 +0100 From: David Taylor To: Julian Elischer Cc: current@freebsd.org, hackers@freebsd.org Subject: Re: testig request for your code.. Message-ID: <20010918172308.A6968@gattaca.yadt.co.uk> Mail-Followup-To: Julian Elischer , current@freebsd.org, hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from julian@elischer.org on Mon, Sep 17, 2001 at 18:08:01 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 17 Sep 2001, Julian Elischer wrote: > > If you find a module that worked in a kernel from before September 11 > but does not work on -current, please let Julian@freebsd.org know. > NTFS was working correctly in a kernel from sometime in August, it now fails with an easily reproducable panic about locks. Unfortunately, I never wrote down the trace since I was planning on using gdb -k to debug it.. but: # gdb -k kernel.6 vmcore.6 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... IdlePTD 4620288 initial pcb at 370340 panicstr: bremfree: bp 0xc8977ba0 not locked panic messages: --- panic: lockmgr: pid 943, not exclusive lock holder 942 unlocking dumping to dev ad0s4b, offset 584197 dump ata0: resetting devices .. done 256 [snip] 1 --- Bus error (core dumped) So, I guess I'll need to copy it down by hand next time I'm prepared to crash my system.. (A simple cd /mnt/w2k/; ls; crashes the box. Oddly enough, it didn't seem to have the same effect in single-user mode, not sure why...) -- David Taylor davidt@yadt.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 9:38:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from calcon.calcon.net (calcon.net [63.149.52.2]) by hub.freebsd.org (Postfix) with ESMTP id EA66E37B409 for ; Tue, 18 Sep 2001 09:38:25 -0700 (PDT) Received: from calcon.net (vpn1.calcon.net [63.149.52.253]) by calcon.calcon.net (8.11.2/8.11.2) with ESMTP id f8IGbk526530 for ; Tue, 18 Sep 2001 11:37:46 -0500 Message-ID: <3BA77880.91744255@calcon.net> Date: Tue, 18 Sep 2001 11:38:24 -0500 From: Douglas Egan X-Mailer: Mozilla 4.75 [en] (X11; U; NetBSD 1.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: where to set hw.ata.wc Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I want to run with 'soft updates' on ATA-100 Western Digital drives, so I want to make sure that hw.ata.wc="0" I am looking for the definitive solution for modifying this sysctl value. Previous threads talked about a couple of places: /etc/sysctl.conf - since it is read only value, it has been said by the time it gets here it is too late. I have verified that this has no effect. /boot/loader.conf - didn't try, but upgrading OS might overwrite file /boot/loader.conf.local - effective, but am unsure if this file is unaffected by upgrading. It seems /boot/loader.conf.local is the place, but I would like to know for sure. Thanks, Doug Egan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 9:39:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 72BFD37B40A for ; Tue, 18 Sep 2001 09:39:44 -0700 (PDT) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f8IGdfI15658; Tue, 18 Sep 2001 09:39:41 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Tue, 18 Sep 2001 09:39:31 -0700 (PDT) From: Matthew Jacob Reply-To: To: Douglas Egan Cc: Subject: Re: where to set hw.ata.wc In-Reply-To: <3BA77880.91744255@calcon.net> Message-ID: <20010918093920.I44838-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG /boot/loader.conf On Tue, 18 Sep 2001, Douglas Egan wrote: > I want to run with 'soft updates' on ATA-100 Western Digital drives, so > I want to make sure that hw.ata.wc="0" > > I am looking for the definitive solution for modifying this sysctl > value. > > Previous threads talked about a couple of places: > > /etc/sysctl.conf - since it is read only value, it has been said > by the time it gets here it is too late. I have > verified that this has no effect. > > /boot/loader.conf - didn't try, but upgrading OS might overwrite file > > /boot/loader.conf.local - effective, but am unsure if this file is > unaffected by upgrading. > > It seems /boot/loader.conf.local is the place, but I would like to know > for sure. > > Thanks, > > Doug Egan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 9:43:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.bmi.net (smtp.bmi.net [204.57.191.31]) by hub.freebsd.org (Postfix) with ESMTP id 3AFE937B409 for ; Tue, 18 Sep 2001 09:43:39 -0700 (PDT) Received: from johncoop.MSHOME (drumheller-router.bmi.net [206.63.201.3] (may be forged)) by smtp.bmi.net (Pro-8.9.3/Pro-8.9.3) with ESMTP id QAA26178; Tue, 18 Sep 2001 16:50:44 -0700 Date: Tue, 18 Sep 2001 09:43:27 -0700 From: John Merryweather Cooper To: Douglas Egan Cc: hackers@freebsd.org Subject: Re: where to set hw.ata.wc Message-ID: <20010918094327.U1513@johncoop.MSHOME> References: <3BA77880.91744255@calcon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: <3BA77880.91744255@calcon.net>; from degan@calcon.net on Tue, Sep 18, 2001 at 09:38:24 -0700 X-Mailer: Balsa 1.1.7 Lines: 43 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2001.09.18 09:38 Douglas Egan wrote: > I want to run with 'soft updates' on ATA-100 Western Digital drives, > so > I want to make sure that hw.ata.wc="0" > > I am looking for the definitive solution for modifying this sysctl > value. > > Previous threads talked about a couple of places: > > /etc/sysctl.conf - since it is read only value, it has been said > by the time it gets here it is too late. I have > verified that this has no effect. > > /boot/loader.conf - didn't try, but upgrading OS might overwrite file > > /boot/loader.conf.local - effective, but am unsure if this file is > unaffected by upgrading. > > It seems /boot/loader.conf.local is the place, but I would like to > know > for sure. > > Thanks, > > Doug Egan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > /boot/loader.conf An OS upgrade SHOULD only touch /boot/defaults/loader.conf. -- jmc MacroHard -- the perfection of form over substance, marketing over performance, and greed over design . . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 9:53:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id DF86A37B407 for ; Tue, 18 Sep 2001 09:53:05 -0700 (PDT) Received: (qmail 31529 invoked by uid 1000); 18 Sep 2001 16:53:26 -0000 Date: Tue, 18 Sep 2001 18:53:26 +0200 From: "Karsten W. Rohrbach" To: Warner Losh Cc: Julian Elischer , Gavin Kenny , freebsd-hackers@FreeBSD.ORG Subject: Re: CAN bus Message-ID: <20010918185326.K27375@mail.webmonster.de> Mail-Followup-To: "Karsten W. Rohrbach" , Warner Losh , Julian Elischer , Gavin Kenny , freebsd-hackers@FreeBSD.ORG References: <200109181533.f8IFXjW64533@harmony.village.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="vSsTm1kUtxIHoa7M" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109181533.f8IFXjW64533@harmony.village.org>; from imp@harmony.village.org on Tue, Sep 18, 2001 at 09:33:45AM -0600 X-Arbitrary-Number-Of-The-Day: 42 X-URL: http://www.webmonster.de/ X-Disclaimer: My opinions do not necessarily represent those of my employer X-Work-URL: http://www.ngenn.net/ X-Work-Address: nGENn GmbH, Schloss Kransberg, D-61250 Usingen-Kransberg, Germany X-Work-Phone: +49-6081-682-304 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --vSsTm1kUtxIHoa7M Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Warner Losh(imp@harmony.village.org)@2001.09.18 09:33:45 +0000: > In message Julian Elischer writes: > : Ok so I have to ask... what is CAN bus? (besides a piece of string=20 > : between 2 cans.). >=20 > A data acquisition bus that was popular in manufacturing a few years > ago. Don't know if it is still popular or not. it is quite standard in industrial environments and still popular (at least in europe) but existant installations slowly get replaced with ethernet based (100baseFX) or industrial ethernet (10Mbit) transceivers. it is not an open standard. i presume that most larger shops try to get rid of it in favor of ethernet/ip based solutions except for very low latency applications which appear to be migrating to firewire based systems. /k --=20 > Should the US government lift the export controls on strong encryption? > Yes, I think so. You can buy better stuff in Europe than you can here. > We don't have a monopoly on brains.=20 > --Interview with Walter Wriston as reported in Wired 4.10=20 KR433/KR11-RIPE -- WebMonster Community Founder -- nGENn GmbH Senior Techie http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.ngenn.n= et/ karsten&rohrbach.de -- alpha&ngenn.net -- alpha&scene.org -- catch@spam.de GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 B= F46 Please do not remove my address from To: and Cc: fields in mailing lists. 1= 0x --vSsTm1kUtxIHoa7M Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7p3wFM0BPTilkv0YRAsvTAKCrrKpIY5GJaM3vmPLF+HeywN2trACfZ715 mKHnVQKp7QJikfH9Z4UEp1E= =W13k -----END PGP SIGNATURE----- --vSsTm1kUtxIHoa7M-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 9:53:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id 4146237B40F for ; Tue, 18 Sep 2001 09:53:54 -0700 (PDT) Received: (qmail 31567 invoked by uid 1000); 18 Sep 2001 16:54:15 -0000 Date: Tue, 18 Sep 2001 18:54:15 +0200 From: "Karsten W. Rohrbach" To: John Merryweather Cooper Cc: Douglas Egan , hackers@freebsd.org Subject: Re: where to set hw.ata.wc Message-ID: <20010918185415.L27375@mail.webmonster.de> Mail-Followup-To: "Karsten W. Rohrbach" , John Merryweather Cooper , Douglas Egan , hackers@freebsd.org References: <3BA77880.91744255@calcon.net> <20010918094327.U1513@johncoop.MSHOME> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="RwGu8mu1E+uYXPWP" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010918094327.U1513@johncoop.MSHOME>; from john_m_cooper@yahoo.com on Tue, Sep 18, 2001 at 09:43:27AM -0700 X-Arbitrary-Number-Of-The-Day: 42 X-URL: http://www.webmonster.de/ X-Disclaimer: My opinions do not necessarily represent those of my employer X-Work-URL: http://www.ngenn.net/ X-Work-Address: nGENn GmbH, Schloss Kransberg, D-61250 Usingen-Kransberg, Germany X-Work-Phone: +49-6081-682-304 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --RwGu8mu1E+uYXPWP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable John Merryweather Cooper(john_m_cooper@yahoo.com)@2001.09.18 09:43:27 +0000: > /boot/loader.conf >=20 > An OS upgrade SHOULD only touch /boot/defaults/loader.conf. why is there /boot/loader.conf.local, then? /k --=20 > Anxiety, n.: The first time you can't do it a second time. > Panic, n.: The second time you can't do it the first time. KR433/KR11-RIPE -- WebMonster Community Founder -- nGENn GmbH Senior Techie http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.ngenn.n= et/ karsten&rohrbach.de -- alpha&ngenn.net -- alpha&scene.org -- catch@spam.de GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 B= F46 Please do not remove my address from To: and Cc: fields in mailing lists. 1= 0x --RwGu8mu1E+uYXPWP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7p3w3M0BPTilkv0YRAln2AJ4+CWU5V6RKDn3dXYw7RlutY+tp6ACfRgBm D+EWugZK056ai1c98NA5fnE= =7nuY -----END PGP SIGNATURE----- --RwGu8mu1E+uYXPWP-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 10:21: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta11.onebox.com (mta11.onebox.com [64.68.76.121]) by hub.freebsd.org (Postfix) with ESMTP id 1B45B37B410 for ; Tue, 18 Sep 2001 10:20:56 -0700 (PDT) Received: from onebox.com ([10.1.111.7]) by mta11.onebox.com (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20010918172055.BSRJ12461.mta11.onebox.com@onebox.com> for ; Tue, 18 Sep 2001 10:20:55 -0700 Received: from [63.49.207.168] by onebox.com with HTTP; Tue, 18 Sep 2001 10:20:55 -0700 Date: Tue, 18 Sep 2001 10:20:55 -0700 Subject: Re: Version of XFree86 in FreeBSD Release 4.4 From: "glenn gombert" To: hackers@FreeBSD.ORG Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Message-Id: <20010918172055.BSRJ12461.mta11.onebox.com@onebox.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG My interest in a later version of XFree86 is that in trying to install FreeBSD-Current on my Dell Insperion 4000e Laptop, the ATI Rage 128 3D graphics accelerator used is not supported at all under XFree86 3.3.6. So I am forced to upgrade to a later version of XFree86 to get 'X' to work at all.... Can someone outline the easiest way to do that given how things are in the FreeBSD-4.3 Release?? Thanks in Advance, Glenn G. ---- Alexander Langer wrote: > Thus spake Robert Withrow (bwithrow@nortelnetworks.com): > > > I know it is slimy, but couldn't there be a dummy "port" just > > called "XFree86" that is what most other ports depend on? The minority > > of ports that actually care what version of X is installed could > always > > use the version-specific names... > > Would be nice if we had a package system that lets you just install > - let me call them - "features", such as a "XFree86" feature, other > ports could depend on. Multiple packages could supply this feature > then and ports could also say if they depend on a specific version. > > Alex, > hiding in a dark corner. > ___________________________________________________________________ To get your own FREE ZDNet Onebox - FREE voicemail, email, and fax, all in one place - sign up today at http://www.zdnetonebox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 10:35:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id BD99837B40A for ; Tue, 18 Sep 2001 10:35:06 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA21637; Tue, 18 Sep 2001 11:03:36 -0700 (PDT) Date: Tue, 18 Sep 2001 11:03:35 -0700 (PDT) From: Julian Elischer To: Douglas Egan Cc: hackers@freebsd.org Subject: Re: where to set hw.ata.wc In-Reply-To: <3BA77880.91744255@calcon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 18 Sep 2001, Douglas Egan wrote: > I want to run with 'soft updates' on ATA-100 Western Digital drives, so > I want to make sure that hw.ata.wc="0" > > I am looking for the definitive solution for modifying this sysctl > value. > > Previous threads talked about a couple of places: > > /etc/sysctl.conf - since it is read only value, it has been said > by the time it gets here it is too late. I have > verified that this has no effect. > > /boot/loader.conf - didn't try, but upgrading OS might overwrite file this is the place because it overrides /boot/defaults/loader.conf > > /boot/loader.conf.local - effective, but am unsure if this file is > unaffected by upgrading. I'm not sure this is "supported" > > It seems /boot/loader.conf.local is the place, but I would like to know > for sure. > > Thanks, > > Doug Egan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 10:35:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id E846A37B41B; Tue, 18 Sep 2001 10:35:23 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA21635; Tue, 18 Sep 2001 11:01:37 -0700 (PDT) Date: Tue, 18 Sep 2001 11:01:36 -0700 (PDT) From: Julian Elischer To: David Taylor Cc: current@freebsd.org, hackers@freebsd.org Subject: Re: testig request for your code.. In-Reply-To: <20010918172308.A6968@gattaca.yadt.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If you can try a kernel from JUST before the KSE integration.. that migh talso be a good test.. On Tue, 18 Sep 2001, David Taylor wrote: > On Mon, 17 Sep 2001, Julian Elischer wrote: > > > > If you find a module that worked in a kernel from before September 11 > > but does not work on -current, please let Julian@freebsd.org know. > > > > NTFS was working correctly in a kernel from sometime in August, it now fails > with an easily reproducable panic about locks. Unfortunately, I never wrote > down the trace since I was planning on using gdb -k to debug it.. but: > > # gdb -k kernel.6 vmcore.6 > GNU gdb 4.18 > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-freebsd"... > (no debugging symbols found)... > IdlePTD 4620288 > initial pcb at 370340 > panicstr: bremfree: bp 0xc8977ba0 not locked > panic messages: > --- > panic: lockmgr: pid 943, not exclusive lock holder 942 unlocking > > dumping to dev ad0s4b, offset 584197 > dump ata0: resetting devices .. done > 256 [snip] 1 > --- > Bus error (core dumped) > > So, I guess I'll need to copy it down by hand next time I'm prepared to > crash my system.. (A simple cd /mnt/w2k/; ls; crashes the box. Oddly > enough, it didn't seem to have the same effect in single-user mode, not sure > why...) > > -- > David Taylor > davidt@yadt.co.uk > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 10:39:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from saturn.bsdhome.com (unknown [24.25.2.210]) by hub.freebsd.org (Postfix) with ESMTP id C6D0D37B40D; Tue, 18 Sep 2001 10:39:20 -0700 (PDT) Received: from neutrino.bsdhome.com (jupiter [192.168.220.13]) by saturn.bsdhome.com (8.11.4/8.11.4) with ESMTP id f8IHdBf18951; Tue, 18 Sep 2001 13:39:12 -0400 (EDT) Received: (from bsd@localhost) by neutrino.bsdhome.com (8.11.6/8.11.6) id f8IHd6P67309; Tue, 18 Sep 2001 13:39:06 -0400 (EDT) (envelope-from bsd) Date: Tue, 18 Sep 2001 13:39:06 -0400 From: Brian Dean To: Jordan Hubbard Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Message-ID: <20010918133906.B65488@neutrino.bsdhome.com> References: <20010917234536.JEJS12461.mta11.onebox.com@onebox.com> <20010917172408.A93860@dragon.nuxi.com> <20010917174811J.jkh@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010917174811J.jkh@freebsd.org>; from jkh@FreeBSD.ORG on Mon, Sep 17, 2001 at 05:48:11PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 17, 2001 at 05:48:11PM -0700, Jordan Hubbard wrote: > No, 3.3.6. There is no such thing as 3.3.7 (at least not according to > www.xfree86.org) and even if there were, enough version-number > specifics are encoded into sysinstall that I would had to have been > told at least a week or two ago if any such version number bump were > contemplated. :) Which reminds me ... shouldn't sysinstall read this kind of information from the distribution area instead of hard-coding it within sysinstall itself? This would require "make release" to generate some metadata about the release area, but then other installers would have easy access to what's available for installation as well, and you wouldn't have to modify sysinstall so much when things change. -Brian -- Brian Dean bsd@FreeBSD.org bsd@bsdhome.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 10:53:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 1D75F37B407 for ; Tue, 18 Sep 2001 10:53:09 -0700 (PDT) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id f8IHqUO04715; Tue, 18 Sep 2001 10:52:30 -0700 (PDT) (envelope-from jkh@freebsd.org) To: bsd@bsdhome.com Cc: freebsd-hackers@freebsd.org Subject: Re: Version of XFree86 in FreeBSD Release 4.4 In-Reply-To: <20010918133906.B65488@neutrino.bsdhome.com> References: <20010917172408.A93860@dragon.nuxi.com> <20010917174811J.jkh@freebsd.org> <20010918133906.B65488@neutrino.bsdhome.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010918105230S.jkh@freebsd.org> Date: Tue, 18 Sep 2001 10:52:30 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 26 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is only one of many different areas in which sysinstall is insufficiently dynamic. Patches, as always, are cheerfully accepted. :) - Jordan > On Mon, Sep 17, 2001 at 05:48:11PM -0700, Jordan Hubbard wrote: > > No, 3.3.6. There is no such thing as 3.3.7 (at least not according to > > www.xfree86.org) and even if there were, enough version-number > > specifics are encoded into sysinstall that I would had to have been > > told at least a week or two ago if any such version number bump were > > contemplated. :) > > Which reminds me ... shouldn't sysinstall read this kind of > information from the distribution area instead of hard-coding it > within sysinstall itself? This would require "make release" to > generate some metadata about the release area, but then other > installers would have easy access to what's available for installation > as well, and you wouldn't have to modify sysinstall so much when > things change. > > -Brian > -- > Brian Dean > bsd@FreeBSD.org > bsd@bsdhome.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 12:11: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id C09E537B407 for ; Tue, 18 Sep 2001 12:11:03 -0700 (PDT) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id f8IJB1g45545; Tue, 18 Sep 2001 14:11:01 -0500 (CDT) (envelope-from tinguely) Date: Tue, 18 Sep 2001 14:11:01 -0500 (CDT) From: mark tinguely Message-Id: <200109181911.f8IJB1g45545@web.cs.ndsu.nodak.edu> To: imp@harmony.village.org, karsten@rohrbach.de Subject: Re: CAN bus Cc: freebsd-hackers@FreeBSD.ORG, gavinkenny@yahoo.co.uk, julian@elischer.org In-Reply-To: <20010918185326.K27375@mail.webmonster.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > it is quite standard in industrial environments and still popular (at > least in europe) but existant installations slowly get replaced with > ethernet based (100baseFX) or industrial ethernet (10Mbit) transceivers. I believe it was designed for noisy environments and is still used in automotive and large equipment (farm tractors, combines, etc). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 12:30:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.yadt.co.uk (yadt.demon.co.uk [158.152.4.134]) by hub.freebsd.org (Postfix) with SMTP id CF9B737B40F for ; Tue, 18 Sep 2001 12:29:59 -0700 (PDT) Received: (qmail 34310 invoked from network); 18 Sep 2001 19:29:57 -0000 Received: from gattaca.local.yadt.co.uk (HELO mail.gattaca.yadt.co.uk) (qmailr@10.0.0.2) by xfiles.yadt.co.uk with SMTP; 18 Sep 2001 19:29:57 -0000 Received: (qmail 992 invoked by uid 1000); 18 Sep 2001 19:29:56 -0000 Date: Tue, 18 Sep 2001 20:29:56 +0100 From: David Taylor To: Julian Elischer Cc: current@freebsd.org, hackers@freebsd.org Subject: Re: testig request for your code.. Message-ID: <20010918202955.A961@gattaca.yadt.co.uk> Mail-Followup-To: Julian Elischer , current@freebsd.org, hackers@freebsd.org References: <20010918172308.A6968@gattaca.yadt.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from julian@elischer.org on Tue, Sep 18, 2001 at 11:01:36 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, 18 Sep 2001, Julian Elischer wrote: > If you can try a kernel from JUST before the KSE integration.. >=20 > that migh talso be a good test.. >=20 A kernel from cvs up -D2001-09-10 works perfectly, A kernel from after the KSE milestone 2 produces various panics like the following: (find .; running on ntfs partition) | (sleep; god knows where) | ( it came from ) v v panic: lockmgr: pid 30856, not exclusive lock holder 30814 unlocking. backtrace: panic lockmgr vop_stdunlock ntfs_inactive vput lstat Unfortunately, gdb -k kernel.X vmcore.X is still coring on startup, so I can't get any more info, unless someone has something they want me to do at the DDB prompt. --=20 David Taylor davidt@yadt.co.uk --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7p6CzfIqKXSsJ/xERAnnHAKDCkRpWdzXMqbiOjARpObYfA6cdiwCgrGFU 7eGdAo+ZvnL8vFqOnjtYkY8= =kv7r -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 12:31:57 2001 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 5078537B414; Tue, 18 Sep 2001 12:29:52 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f8IJTfB76329; Tue, 18 Sep 2001 15:29:41 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 18 Sep 2001 15:29:40 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: developers@FreeBSD.org, hackers@FreeBSD.org Subject: FreeBSD Monthly Status Report, August 2001 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG August 2001 Status Report Introduction The FreeBSD Project made substantial progress in the month of August, 2001, both on continuing the development of the RELENG_4 line (4.x-STABLE and 4.x-RELEASE), and on 5.0-CURRENT, the main development branch. During this month, the decision was made to push the release of 5.0-CURRENT back so that KSE (support for fine-grained user threads) could be completed in time for the release, rather than postponing that support for 6.0. As such, the lifespan of the RELENG_4 line will be extended, with new features continuing to be backported to that branch. 4.4-RELEASE went into final beta during this month, and will also be available shortly. This month's edition of the status report has been written with the assistance of Nik Clayton and Chris Costello. Future submissions For next month, the submission procedures remain the same: reports should be between one and two paragraphs long, sent by e-mail, and in a format approximately that of this month's submissions (Project, Contact, URL, and text). Reminders will be mailed to the hackers@FreeBSD.org and developers@FreeBSD.org mailing lists at least a week before the deadline; complete submission instructions may be found in those reminders. -- Robert Watson * aac driver * ARM port * BSDCon Europe * CAM * Compressed TCP state * CVSROOT script rewrite/tidy * Documentation Project * fbsd-nvdriver * Fibre Channel Support * floppy driver overhaul * FreeBSD core-secretary * FreeBSD Java Project * FreeBSD PAM * FreeBSD Release Engineering * FreeBSD/sparc64 port * GNOME Desktop for FreeBSD * ia64 Port * Improved TCP Initial Sequence Numbers * Intel Gigabit Ethernet * IP Multicast Routing support * jpman project * KAME * KSE * libh Project * LOMAC * Mbuf SMPng allocator * Netgraph ATM * network device cloning * Network device nodes * Network SMP locking * OLDCARD improvements * Porting ppp to hurd & linux * PPP IPv6 Support * pppoa * pppoed * PRFW - hooks for the FreeBSD kernel * Problem Reports * RAIDframe for FreeBSD * RELNOTESng * SCSI Tape Support * SMPng * sppp(4) merge * SYN cache implemetation for FreeBSD * TrustedBSD * TrustedBSD Capabilities aac driver URL: http://people.freebsd.org/~scottl/aac Contact: Scott Long The aac driver has been given a lot of attention lately and is now nearly feature complete. Changes include crashdump support, correct handling of controller initiated commands, and more complete management interface support. The Linux RAID management tool available from Dell and HP now fully works; a FreeBSD native version of the tool is also in the works. These changes have been checked into -current, and will appear in -stable once 4.4 has been released. ---------------------------------------------------------------------- ARM port URL: http://pages.infinit.net/sepotvin/ Contact: Stephane Potvin Basic footbridge support is now functional and the kernel is now able to probe the pci bus. Access primitives for the bus are still missing so I can't attach any drivers yet. ---------------------------------------------------------------------- BSDCon Europe Contact: Paul Richards Planning for BSDCon Europe is going well. We're still accepting proposals for talks but the schedule is starting to fill up so we may not be for much longer. An update of the site that includes accommodation information, a preliminary schedule, a list of speakers and an online payment page will be launched on Wednesday 19 September. The fee will be -L-150 for individuals and -L-250 for corporations. The individual pricing is valid only until the end of September, the price will rise to -L-200 for October and late registrations in November will be -L-250. The updated website will include a list of sponsorship options, we're still looking for more sponsorship. ---------------------------------------------------------------------- CAM Contact: Matthew Jacob Contact: Justin Gibbs Contact: Kenneth Merry No change since last status. Some discussion amongst all of us occurred, but lack of time and commitment to FreeBSD has meant little has actually been committed to the tree. SMPNG work will be left to those who seem to have a notion about what needs to be done. ---------------------------------------------------------------------- Compressed TCP state Contact: Jonathan Lemon State information for TCP connections is primarily kept in the TCP/IP control blocks in the kernel. Not all of the TCP states make use of the entire structure, and significant memory savings can be had by using a cut-down version of the state in some cases. The first phase of this project will address connections that are in the TIME_WAIT state by moving them into a smaller structure. This project has completed the initial research and rough design phases, with actual code development starting immediately. ---------------------------------------------------------------------- CVSROOT script rewrite/tidy Contact: Josef Karthauser Work is still progressing to make all of the perl scripts run using perl's 'strict' mode, and to migrate all FreeBSD specific options into the configuration file (CVSROOT/cfg.pm). I'll be looking for help soon to write a guide on how to make use of these scripts for use in your own repository. Anyone interested in helping should contact me at the above email address. ---------------------------------------------------------------------- Documentation Project URL: http://www.FreeBSD.org/docs.html URL: http://www.FreeBSD.org/docproj/index.html Contact: Nik Clayton Contact: Documentation Project The Handbook has been the main focus of activity this month. Due to go to the printers on the 15th a vast amount of new content has been submitted and committed. This includes a complete rewrite of the "Installing FreeBSD", which massively expands the amount of information available to people new to FreeBSD. It even includes screenshots. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install.html Comments, and contributions are, of course, welcome. ---------------------------------------------------------------------- fbsd-nvdriver URL: http://fbsd-nvdriver.sourceforge.net Contact: Erik Greenwald Contact: Joel Willson NVIDIA Corporation releases Linux drivers by using a combination of binary object files and source (under a constrictive license). The FreeBSD NVIDIA driver project aimed to completely replace the source component of the driver using code targetting FreeBSD 4.3 and released under the BSD license. The binary module provided is supposedly the same module used on Windows, BeOS, and OS/2, so it should be portable between different i80x86 based OS's. The project is currently on indefinite hold. Our contact at NVIDIA seemed enthusiastic about the project, and was fairly quick about returning email, but when we discovered issues that prevented porting without changes to the binary component or error codes we needed decyphered, Nick (the contact) said he'd look into it and never got back. The first major problem was the ioctl interface, the nvidia driver passes a pointer and depends on the kernel side to copyout the right amount, where FreeBSD expect the parameters to be correct and the copyout is performed by the subsystem. This was worked around using Dave Rufinos "ioctl tunnel" idea. After that, we found that X refused to load and traced it down to an ioctl defined in the binary component erroring. We cannot tell what that ioctl is, were told that we could not sign an nda for source to that component, and have been waiting a month for Nick to "look into it". Therefore progress is impossible (without breaking the license) and we believe that the flaws make the driver unportable to any *nix other than Linux. ---------------------------------------------------------------------- Fibre Channel Support URL: http://www.feral.com/isp.html Contact: Matthew Jacob 2 Gigabit support was integrated on 8/31/2001 (QLogic 2300/2312 cards). Because of the author's shrinking time commitment for FreeBSD, the previously planned "next step" which would have been more complete new CAM Transport integration is now probably just the addition of an FC-IP adjunct (as this can benefit many platforms simultaneously). ---------------------------------------------------------------------- floppy driver overhaul Contact: Joerg Wunsch As part of some ongoing development activity, the floppy driver (fdc(4)) enjoyed some overhaul in the past which is part of an ongoing process. Automatic density selection will come next, something i meant to implement for years now. As part of that, the entire density selection stuff has been rewritten. 2.88 MB floppies are on the wishlist as well, but I need a working 2.88 drive before attempting to implement that. ---------------------------------------------------------------------- FreeBSD core-secretary Contact: Alan Clegg Contact: The position of Core Secretary was filled by Alan Clegg The first core-secretary report should be available the second week in September and will cover the issues discussed by core during August 2001. ---------------------------------------------------------------------- FreeBSD Java Project URL: http://www.freebsd.org/java/ Contact: Greg Lewis Most of the work this month has focused on development of the native JDK 1.3.1 patchset. The 3rd patchset is out and has been accompanied with the creation of a FreeBSD "port". This has allowed early adopters much easier access to the code and naturally resulted in a number of bugs being found. Development work has mostly focused on fixing these problems and the project is now set to release fourth patchset over the weekend, which should see the JDK in a reasonable useable state. One of the big challenges left is producing a working HotSpot JVM, which looks like it will require some heavy hacking. We also welcome OpenBSD's Heikki Korpela to the porting team :) ---------------------------------------------------------------------- FreeBSD PAM Contact: Mark Murray Development is continuing; pam_unix has gained the ability to change passwords, login(1) has had PAM made compulsory (and is going to have more PAM-capable features handed over to PAM). ---------------------------------------------------------------------- FreeBSD Release Engineering Contact: FreeBSD Release Engineer Team The FreeBSD release engineering process for FreeBSD 4.4 started to ramp up around August 1st when the "code slush" took affect. During this time all commits to the RELENG_4 branch were reviewed by re@FreeBSD.org (over 250 code snippets had to be reviewed). After the first release candidate on August 15th, all submissions were scrutinized under a more strict potential risk vs benefit curve. The best way to help get involved with the release engineering process is to simply follow the low volume freebsd-qa mailing list, help out with the neverending supply of PRs related to our installation tools (sysinstall), or to work on a possible next-generation replacement for our installation technology, such as the libh or OpenPackages projects. Many companies donated equipment, network access, or paychecks to finance these activities. Including Compaq, Yahoo!, Wind River Systems, and many more. ---------------------------------------------------------------------- FreeBSD/sparc64 port Contact: Jake Burkholder Contact: Thomas Moestl Contact: Robert Drehmel Sparc64 development is still continuing rapidly and we're making some excellent progress. Of note, some problems with the way the pmap module implements copy-on-write mappings have been fixed and fork() now works as expected, support for signals has been added, and the port has been updated for kse in the perforce repository. Thomas Moestl has begun work on pci bus support, and a basic nexus bus for sparc64 has been written. The driver for the Sun `Psycho' and `Sabre' UPA-to-PCI bridges and associated code has been ported from NetBSD (the Sabre is the on-chip version found in the UltraSparc IIi and IIe). PCI configuration, I/O and memory space accesses do already work, as well as interrupt assignment and delivery for devices attached directly to the bridge, and the first PCI device drivers can attach and seem to work mostly. Interrupt routing and busdma support still need much work. ---------------------------------------------------------------------- GNOME Desktop for FreeBSD Contact: Maxim Sobolev Contact: FreeBSD GNOME Team Getting GNOME Fifth-Toe metaport ready for 4.4-RELEASE was the main focus of activity this month. In the process many components were updated, many bugs were tracked down and solved, which allowed to make this 97-component meta-package building and working properly. Next month the project will be focused on organising work of the FreeBSD GNOME Team as well as on attempts to increase amount of people participating in the team (anybody who is willing to participate is welcome to drop a note to gnome@FreeBSD with a short explanation of how he/she could help). ---------------------------------------------------------------------- ia64 Port Contact: Doug Rabson Current status is that the ia64 kernel builds and runs in a simulator environment up to single user mode and has been tested lightly in that environment. My current focus is on completing the ia64 loader so that I can start to get kernels working on the real hardware. The loader is coming along well and I expect to be able to load kernels (but not necessary execute them) soon. ---------------------------------------------------------------------- Improved TCP Initial Sequence Numbers Contact: Mike Silbersack In mid March, 2001, Tim Newsham of Guardent identified an attack possible against the initial sequence number generation scheme of FreeBSD (and other OSes.) In order to guard against this threat, a randomized sequence number generation scheme was ported over from OpenBSD and included in 4.3-release. Unfortunately, non-monotonic generation was found to cause major problems with applications which initiate continuous, rapid connections to a single host. In order to restore proper operation under such circumstances while still providing strong resistance against sequence number prediction, FreeBSD 4.4 uses the algorithm specified in RFC 1948. This algorithm hashes together host and port information with a piece of secret data to generate a unique sequence number space for each connection. As a result, outgoing initial sequence numbers are again monotonic, but also unguessable by an attacker. ---------------------------------------------------------------------- Intel Gigabit Ethernet Contact: Matthew Jacob No new status to report. This driver will be worked on again soon and cleaned up to work better. ---------------------------------------------------------------------- IP Multicast Routing support Contact: Bill Fenner FreeBSD's IP Multicast Routing support was recently updated in several ways. One big change is that it's now able to be loaded as a KLD instead of statically compiled into the kernel; this is especially useful for experimentation or updating of an existing system. It also now coexists nicely with the kernel IP encapsulation infrastructure, so that multicast tunnels can better coexist with MobileIP, certain IPSec tunnels and generic IPv4-in-IPv4 tunnels. ---------------------------------------------------------------------- jpman project URL: http://www.jp.FreeBSD.org/man-jp/ Contact: Kazuo Horikawa Contact: Targeting 4.4-RELEASE, one team has been translating newly MFC'ed section [125678] manpages. The other team has been updating section 3 since May and one third (1/3) is finished. The port ja-groff is updated to be groff-1.17.2 based, and now it has the same functionality as base system does. The port ja-man is updated to have the search capability under an architecture subdirectory, as base system does. The doc/ja_JP.eucJP/man hierarchy update (adding architecture subdirectories) is planned after 4.4-RELEASE. ---------------------------------------------------------------------- KAME URL: http://www.kame.net/ Contact: Munechika Sumikawa The KAME project (http://www.kame.net/) has merged its IPv6 and IPsec implementation as of July 2001 to FreeBSD CURRENT and STABLE, in cooperation with some contributors of the project. The latest code includes a number of bug fixes, has been fully tested in FreeBSD STABLE, and will appear in FreeBSD 4.4 RELEASE. Thus, the new RELEASE version will be quite stable in terms of IPv6 and IPsec. The project has assigned a talented guy to be responsible for merge from KAME to FreeBSD, so future merge efforts will be smoother. ---------------------------------------------------------------------- KSE Contact: Julian Elischer Contact: Peter Wemm Contact: Matt Dillon Work in adding supporting infrastructure to the kernel for KSE threading support has reached "milestone 2". Milestone 2 is where the kernel source consistently refers to its resources in terms of per-thread and per-process resources, in the way that it will need to when there are > 1 threads per process, but the LOGICAL changes to such things as the scheduler, and fork and exit, have not yet been made to allow more than one thread to be created. (nor have new threading syscalls been added yet). This is an important milestone as it represents the last point where the kernel has only "mechanical" changes. To go further we must start adding new algorythms and functions. The kernel for milestone 2 is reliable and has no noticable performance degradations when compared to a matchung -current kernel. (the differences are less than the margin of error, so that sometimes the new kernel actually fractionally beats the unaltered kernel). We hope that by the time this is published, the KSE patches will have been committed. The Major effect for most developers will be only that the device driver interface requires a 'thread' pointer instead of a Proc pointer in the open, close and ioctl entrypoints. I'm sure there will be small teething problems but we are not expecting great problems at the commit. ---------------------------------------------------------------------- libh Project Contact: Alexander Langer Contact: Nathan Ahistrom I have access to the libh CVS repo again and am testing a new, OBJDIR capable build structure at the moment. Done that, I'm going to continue testing the package library and implement the missing functionality. Currently, import of libh into the base system is under discussion (arch mailinglist). Now that 5.0-RELEASE has been shifted, I want 5.0 ship with a libh installer and package system. We can really need people who are good in C++, are able to understand what the current implementation does and also feel that working on libh is fun and thus are willing to help. ---------------------------------------------------------------------- LOMAC Contact: Brian Feldman The port of LOMAC to FreeBSD is progressing well, and already has a very high level of stability (no known outstanding bugs!). Aspects which have already been implemented include a stacking filesystem overlay with fully-functional access controls (for files and directories) based on path names, access controls for sending signals, and file-backed-memory revocation for processes. ---------------------------------------------------------------------- Mbuf SMPng allocator URL: http://people.freebsd.org/~bmilekic/code/mb_slab/ Contact: Bosko Milekic The allocator appears to be stable. Mbtypes statistics have been re-activated thanks, in part, to Jiangyi Liu although the diff has not yet been committed (I'm just in the process of cleaning it up a little and final testing). More work to come: cleanups, follow TODO from the original commit, and perhaps an eventual generalization of the allocator for various network-related allocations (in a more distant future). ---------------------------------------------------------------------- Netgraph ATM Contact: Hartmut Brandt The ATM stack has been tested with a number of FreeBSD machines and a Marconi ATM switch and seems to be quite stable running CLIP. Multi port support for the native ATM API has been implemented but needs some testing. ---------------------------------------------------------------------- network device cloning Contact: Brooks Davis Support for cloning vlan devices via ifconfig has been committed to -current and will be MFC'd after further testing. Additionaly, Maksim Yevmenkin submitted code to allow cloning of tap and vmnet devices on devfs systems. Code for faith and stf should be committed shortly. ---------------------------------------------------------------------- Network device nodes Contact: Jonathan Lemon Currently, all network devices (fxp0, lo0, etc) exist in their own namespace, and are accessed through a socket interface. This project creates device nodes in /dev for network devices, and allows control and access in that fashion. This is experimental work, and suggestions for APIs and functionality are strongly encouraged and welcomed. In is not clear whether it will be possible (or desirable) to provide the exact same set of operations that can be done through the socket interface. Benefits of approach include the fact that a kqueue filter can be attached to a network device for monitoring purposes. Initial code exists to send a kq event whever the network link status changes. Other benefits may include better access control by using filesystem ACLs to control access to the device. ---------------------------------------------------------------------- Network SMP locking Contact: Jonathan Lemon For 5.0, the goal is for the network stack to run without the Giant lock. Initial development in this area may focus on partitioning the code and data structures into distinct areas of responsibilities. A first pass of locking may involve using a several smaller mini-giant code locks in order to reduce the problem to a manageable size. Progress for this month includes the creation of a perforce repository to officially track the locking changes, and the initial submission of locks for the &ifnet list. Some code cleanup has also been done to the main tree in order to better support future locking additions. ---------------------------------------------------------------------- OLDCARD improvements Contact: Warner Losh The OLDCARD improvements have been completed, except for a few edge cases for older laptops with CL-PD6729/30 chips and some pci bios issues. Some minor work will continue, but after 4.4R is released, only a few remaining bugs will be fixed before the author moves on to greener fields of NEWCARD development. ---------------------------------------------------------------------- Porting ppp to hurd & linux Contact: Brian Somers Status is unchanged since last month. Patches have been submitted to get ppp working under HURD, and mostly under Linux. There are GPL copyright problems that need to be addressed. Many conflicts are expected after the commit of IPv6 support in ppp. ---------------------------------------------------------------------- PPP IPv6 Support Contact: Brian Somers The software has been committed to -current and seems functional. Outstanding issues include dealing with IPV6CP events (linkup & linkdown scripts) and allocating site-local and global addresses (currently, ``iface add'' is the only way to actually use the link). ---------------------------------------------------------------------- pppoa Contact: Brian Somers I looked at bringing PPPoA into the base system, but could not because of an overly restrictive distribution license on the Alcatel Speedtouch modem firmware. It has been committed as a port instead and is running live at a FreeBSD Services client site. ---------------------------------------------------------------------- pppoed Contact: Brian Somers Making pppoed function in a production environment. All known problems have been fixed and committed. ---------------------------------------------------------------------- PRFW - hooks for the FreeBSD kernel URL: http://www.freesoftware.fsf.org/jailuser Contact: Evan Sarmiento PRFW is a set of hooks for the FreeBSD kernel. It allows users to insert code into system calls, for such purposes as creating extended security features. Last week, PRFW reached 0.1.0, with many bugfixes and cleaning. I urge anyone who is interested to please visit the site, join the mailing list. Also take a peek at lsm.immunix.org, the Linux hooks. It will be a good contrast. ---------------------------------------------------------------------- Problem Reports URL: http://phk.freebsd.dk/Gnats/ Contact: Poul-Henning Kamp We are making some progress, we are now down to 2170 open PR's down from an all time high of 3270 just 3 months ago. The aim is still to get rid of all the dead-wood in the PR database so only relevant PRs in the database. A big thanks from me to the people who have made this happen! ---------------------------------------------------------------------- RAIDframe for FreeBSD URL: http://people.freebsd.org/~scottl/rf Contact: Scott Long After two months of little progress, RAIDframe work is gearing up again. The port to -stable has some known bugs but is fairly stable. The port to -current was recently completed and patches will be released soon. RAIDframe is a multi-platform RAID subsystem designed at CMU. This is a port of the NetBSD version by Greg Oster. ---------------------------------------------------------------------- RELNOTESng URL: http://people.freebsd.org/~bmah/relnotes/ Contact: Bruce Mah RELNOTESng, the DocBook-ified set of release documentation files, has been merged to the RELENG_4 branch. 4.4-RELEASE will be the first release of FreeBSD with the new-style release notes, hardware list, etc. Some of these documents are being translated by the Japanese and Russian translation teams. Snapshots of RELNOTESng for CURRENT and 4-STABLE in HTML, text, and PDF are available at the above URL and are updated irregularly but frequently. Dima Dorfman and Nik Clayton have been working to have automatically-generated snapshots on the main FreeBSD web site. On my TODO list: 1) Resynchronize the FreeBSD installation document with the installation chapter in the Handbook. 2) Update the hardware lists (with particular emphasis on PCCARD and USB devices). 3) Update the infrastructure to allow the architecture-dependent parts of RELNOTESng to scale to more hardware platforms. ---------------------------------------------------------------------- SCSI Tape Support Contact: Matthew Jacob A major update to error handling was done on 8/28/2001 which should correct most of the EOM detection problems that have been around for a while. There are several things to fix. The principle thing to fix next is the establishment of a loader(8) mediated device quirks method. ---------------------------------------------------------------------- SMPng URL: http://www.FreeBSD.org/~jasone/smp/ Contact: John Baldwin Contact: Peter Wemm Updates to things from last month: * The ast() fixes were committed last month. * The work on the preemptive kernel is stalled for the time being. It is still unstable on Alpha and SMP systems. New stuff since last month: * sx locks now support upgrades and downgrades. * Witness now supports lock upgrades and downgrades. * Jason Evans has committed a semaphore implementation. * Matt Dillon has pushed Giant down into all of the syscalls. * John Baldwin has been working on proc locking in a p4 'jhb_proc' branch. * John is also currently working on making the ktrace code use a work thread to asynchronously write trace data out to the trace file. This will make ktrace safe almost completely MP safe with the exception that a few ktrace events need Giant in order to call malloc(9) and that ktrgenio() is still synchronous. Specifically, however, ktrpsig(), ktrsysret(), and ktrcsw() no longer need Giant. * Jonathan Lemon has started work on locking the network stack in a p4 'netlock' branch. ---------------------------------------------------------------------- sppp(4) merge Contact: Joerg Wunsch sppp(4) should be merged with the ISDN4BSD offspring variant. This will merge some features and bugfixes from the i4b branch (like VJ compression), and eventually end up in a single sppp(4) in the tree. While being at that, incorporating many changes and bugfixes from NetBSD is considered as well. ---------------------------------------------------------------------- SYN cache implemetation for FreeBSD Contact: Jonathan Lemon The syncache implementation is completed, and currently under testing and review. The code should be committed to -current in the near future, and a patchset for -stable made available. ---------------------------------------------------------------------- TrustedBSD URL: http://www.TrustedBSD.org/ Contact: Robert Watson Contact: The TrustedBSD project continues to move ahead, with progress made in the ACL, Capability, and MAC implementations. In addition, support from DARPA is permitting new work to improve the extended attribute code, improve security abstractions, and work on security documentation. Due to the push-back of the FreeBSD 5.0 release, it should now be possible to include a complete MAC implementation in that release. Specific status reports appear for components where substantial progress is being made. ---------------------------------------------------------------------- TrustedBSD Capabilities Contact: Robert Watson Contact: Thomas Moestl Contact: Capabilities support is currently being comitted to the base FreeBSD tree--userland libraries are now fully committed, and kernel infrastructure is being integrated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 13: 3: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.yadt.co.uk (yadt.demon.co.uk [158.152.4.134]) by hub.freebsd.org (Postfix) with SMTP id 9BC2937B401 for ; Tue, 18 Sep 2001 13:02:46 -0700 (PDT) Received: (qmail 34491 invoked from network); 18 Sep 2001 20:02:44 -0000 Received: from gattaca.local.yadt.co.uk (HELO mail.gattaca.yadt.co.uk) (qmailr@10.0.0.2) by xfiles.yadt.co.uk with SMTP; 18 Sep 2001 20:02:44 -0000 Received: (qmail 55692 invoked by uid 1000); 18 Sep 2001 20:02:44 -0000 Date: Tue, 18 Sep 2001 21:02:44 +0100 From: David Taylor To: hackers@freebsd.org Subject: Re: where to set hw.ata.wc Message-ID: <20010918210244.D961@gattaca.yadt.co.uk> Mail-Followup-To: hackers@freebsd.org References: <3BA77880.91744255@calcon.net> <20010918094327.U1513@johncoop.MSHOME> <20010918185415.L27375@mail.webmonster.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="IpbVkmxF4tDyP/Kb" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010918185415.L27375@mail.webmonster.de>; from karsten@rohrbach.de on Tue, Sep 18, 2001 at 18:54:15 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --IpbVkmxF4tDyP/Kb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, 18 Sep 2001, Karsten W. Rohrbach wrote: > John Merryweather Cooper(john_m_cooper@yahoo.com)@2001.09.18 09:43:27 +00= 00: > > An OS upgrade SHOULD only touch /boot/defaults/loader.conf. >=20 > why is there /boot/loader.conf.local, then? >=20 boot.loader(5): /boot/loader.conf user defined settings. /boot/loader.conf.local machine-specific settings for sites with a common loader.conf. So you can have a standard /boot/loader.conf across your site, but still deal with hardware/setup/etc differences. -- David Taylor davidt@yadt.co.uk --IpbVkmxF4tDyP/Kb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7p6hkfIqKXSsJ/xERAgSMAKC+aXsD4tx6MFnW1GO+NjhCiYJy4gCgpv2i LQ0FGPjhlmsA32D6PiU/6N4= =jYjQ -----END PGP SIGNATURE----- --IpbVkmxF4tDyP/Kb-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 13:25:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po4.glue.umd.edu (po4.glue.umd.edu [128.8.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 6C3C137B406 for ; Tue, 18 Sep 2001 13:25:41 -0700 (PDT) Received: from glue.umd.edu (darkstar.umd.edu [128.8.215.163]) by po4.glue.umd.edu (8.10.1/8.10.1) with ESMTP id f8IKPHt02017; Tue, 18 Sep 2001 16:25:21 -0400 (EDT) Message-ID: <3BA7ADB9.769A7BB@glue.umd.edu> Date: Tue, 18 Sep 2001 16:25:29 -0400 From: Brandon Fosdick X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: mark tinguely Cc: imp@harmony.village.org, karsten@rohrbach.de, freebsd-hackers@FreeBSD.ORG, gavinkenny@yahoo.co.uk, julian@elischer.org Subject: Re: CAN bus References: <200109181911.f8IJB1g45545@web.cs.ndsu.nodak.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG mark tinguely wrote: > > > it is quite standard in industrial environments and still popular (at > > least in europe) but existant installations slowly get replaced with > > ethernet based (100baseFX) or industrial ethernet (10Mbit) transceivers. > > I believe it was designed for noisy environments and is still used in > automotive and large equipment (farm tractors, combines, etc). Thats why I chose it for my home automation project. There are a lot of places where I had to run the network wires right next to power wires. Since CAN is supposedly noise resistant and I don't need much bandwidth it seemed like a logical choice. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 13:27:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from reservoir.absolight.com (reservoir.absolight.com [212.43.217.72]) by hub.freebsd.org (Postfix) with ESMTP id B13DE37B40D for ; Tue, 18 Sep 2001 13:27:19 -0700 (PDT) Received: from bilbo.in.mat.cc (bilbo.in.mat.cc [212.43.217.121]) by reservoir.absolight.com (Postfix) with ESMTP id 537F1D3AEC; Tue, 18 Sep 2001 22:27:17 +0200 (CEST) Received: from bilbo.org (localhost [127.0.0.1]) by bilbo.in.mat.cc (Postfix) with ESMTP id 2922865554; Tue, 18 Sep 2001 21:34:27 +0200 (CEST) Received: from club-internet.fr (sauron.in.mat.cc [212.43.217.122]) by bilbo.in.mat.cc (Postfix) with ESMTP id 6BFDC65554; Tue, 18 Sep 2001 21:34:18 +0200 (CEST) Message-ID: <3BA7AE18.4B490E6B@club-internet.fr> Date: Tue, 18 Sep 2001 22:27:04 +0200 From: Mathieu Arnold Organization: http://www.absolight.com/ X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: IP Filter , freebsd-hackers@freebsd.org Subject: Re: no memory problem References: <20010916182420.7CD723E02@drawbridge.oasis.IAEhv.nl> <3BA5234D.77226C3A@club-internet.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mathieu Arnold wrote: > > Frank Volf wrote: > > > > Mathieu Arnold wrote: > > > > What is the output of > > > > > > > > vmstat -m | egrep -i '(pfil|filter|temp)' > > > > > > well, for now, it's ok, as I rebooted the box yesterday > > > temp 27491 12187K 16963K 40960K 15021633 0 0 > > > 16,32,64,128,256,512,1K,4K,16K,512K > > > but it will soon reach the 40960K limit. And I don't see where I can > > > move this limit upper. > > > > You haven't reached the limits yet. I was wondering whether you were hitting > > the limit for the zone or the limit for all malloced area. > > well, that's because I rebooted the box, usually, the max is 40964K. here we go again : IP states added: 9469918 TCP 1654588 UDP 1451233 ICMP 2869559782 hits 100258517 misses 0 maximum 72605 no memory 2915 bkts in use 9766 active 3099381 expired 9393987 closed temp 82729 39223K 40961K 40960K 51082243 0 442 16,32,64,128,256,512,1K,4K,16K,512K does someone here know how to raise that 40960K limit ? -- Mathieu Arnold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 14:57:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 3ACF837B40B; Tue, 18 Sep 2001 14:57:49 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id f8ILvSc98831; Tue, 18 Sep 2001 14:57:28 -0700 (PDT) (envelope-from obrien) Date: Tue, 18 Sep 2001 14:57:22 -0700 From: "David O'Brien" To: Jordan Hubbard Cc: glenngombert@zdnetonebox.com, freebsd-hackers@freebsd.org Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Message-ID: <20010918145722.A97809@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010917234536.JEJS12461.mta11.onebox.com@onebox.com> <20010917174223Z.jkh@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010917174223Z.jkh@freebsd.org>; from jkh@freebsd.org on Mon, Sep 17, 2001 at 05:42:23PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 17, 2001 at 05:42:23PM -0700, Jordan Hubbard wrote: > We're still waiting for 4.0's "support footprint" to widen > a bit more before subjecting people to it by default. Hopefully > by 4.5. Are you really considering using XFree86 4.x in FreeBSD-4.5? When I asked you about this in the past, you had said you wanted to keep the same X in RELENG_4 (presumable to not "rock the boat" mid-branch). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 14:59: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 4F29837B40B; Tue, 18 Sep 2001 14:58:57 -0700 (PDT) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id f8ILwsO05540; Tue, 18 Sep 2001 14:58:54 -0700 (PDT) (envelope-from jkh@freebsd.org) To: obrien@freebsd.org Cc: glenngombert@zdnetonebox.com, freebsd-hackers@freebsd.org Subject: Re: Version of XFree86 in FreeBSD Release 4.4 In-Reply-To: <20010918145722.A97809@dragon.nuxi.com> References: <20010917234536.JEJS12461.mta11.onebox.com@onebox.com> <20010917174223Z.jkh@freebsd.org> <20010918145722.A97809@dragon.nuxi.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010918145854D.jkh@freebsd.org> Date: Tue, 18 Sep 2001 14:58:54 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 15 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Considering it, yes. But only considering. - Jordan > On Mon, Sep 17, 2001 at 05:42:23PM -0700, Jordan Hubbard wrote: > > We're still waiting for 4.0's "support footprint" to widen > > a bit more before subjecting people to it by default. Hopefully > > by 4.5. > > Are you really considering using XFree86 4.x in FreeBSD-4.5? > When I asked you about this in the past, you had said you wanted to keep > the same X in RELENG_4 (presumable to not "rock the boat" mid-branch). > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 15: 3: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 97B0237B40C for ; Tue, 18 Sep 2001 15:02:58 -0700 (PDT) Received: from laptop.baldwin.cx ([147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id PAA06551 for ; Tue, 18 Sep 2001 15:02:27 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 18 Sep 2001 15:02:13 -0700 (PDT) From: John Baldwin To: hackers@FreeBSD.org Subject: JKH Project: x86: pcb_ext Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Here's a Junior Kernel Hacker project for someone: - Move pcb_ext and pcb_ldt out of the pcb of struct thread and into struct mdproc; I.e., you probably want to do something like this: - Rename struct pcb_ext to struct proc_tss and struct pcb_ldt to struct proc_ldt. (Fixup pcb_ext member names to use a tss_ prefix instead of ext_) - Have a struct mdproc as so: struct mdproc { struct proc_tss *md_tss; struct proc_ldt *md_ldt; } Prior to KSE this was just annoyance but wasn't an actual problem. With KSE threads are temporary, whereas the ldt and tss are per-process properties that need to stick around. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 15:15: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id D2BEE37B410; Tue, 18 Sep 2001 15:14:56 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA22852; Tue, 18 Sep 2001 15:58:46 -0700 (PDT) Date: Tue, 18 Sep 2001 15:58:46 -0700 (PDT) From: Julian Elischer To: John Baldwin Cc: hackers@FreeBSD.org Subject: Re: JKH Project: x86: pcb_ext In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG this is already on my list of "non 1:1 fixes needed" On Tue, 18 Sep 2001, John Baldwin wrote: > Here's a Junior Kernel Hacker project for someone: > > - Move pcb_ext and pcb_ldt out of the pcb of struct thread and into > struct mdproc; I.e., you probably want to do something like this: > - Rename struct pcb_ext to struct proc_tss and struct pcb_ldt to > struct proc_ldt. (Fixup pcb_ext member names to use a tss_ > prefix instead of ext_) > - Have a struct mdproc as so: > > struct mdproc { > struct proc_tss *md_tss; > struct proc_ldt *md_ldt; > } > > Prior to KSE this was just annoyance but wasn't an actual problem. With KSE > threads are temporary, whereas the ldt and tss are per-process properties that > need to stick around. > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 15:21:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 885) id C45D737B416; Tue, 18 Sep 2001 15:21:42 -0700 (PDT) Date: Tue, 18 Sep 2001 15:21:42 -0700 From: Eric Melville To: Sheldon Hearn Cc: hackers@FreeBSD.org Subject: Re: Recent changes to libdialog are weird Message-ID: <20010918152142.A48126@FreeBSD.org> References: <95560.1000727060@axl.seasidesoftware.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <95560.1000727060@axl.seasidesoftware.co.za>; from sheldonh@starjuice.net on Mon, Sep 17, 2001 at 01:44:20PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Recently, libdialog's use of tab, space and enter seems to have changed. > Now, space and enter mean the same thing. Before, enter was a > context-insensitive short-cut to the currently selected dialogue > "submit" button. There's nothing context-insensitive about libdialog. Pressing enter does not submit the network interface configuration form. > What many folks may not realize is that the new behaviour, while "safer" > than what we had before, makes libdialog behave differently from at > least Motif, Windows, JavaAWT, JavaSwing. It seems to me that in popular toolkits, one moves the curson over the desired component and presses a button. To do this with a keyboard, tab is used to move the cursor, and space is used to press a button. > So what we have now is a libdialog that protects the finger-happy, while > confounding those who expect "pretty standard behaviour". What we have now, at best, is an interface that is usable by someone with no proir experiance. At worst, it is an archaic interface, but has behaviour that is documented on the very screen on which it is implemented (at least in the case of sysinstall), and thus is no worse than what we had before. > I reckon if sysinstall needs to be weird, sysinstall should use its own > weird version of libdialog and leave the distributed libdialog alone. This would be disasterous. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 15:43:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 31BE237B40A for ; Tue, 18 Sep 2001 15:43:04 -0700 (PDT) Received: from laptop.baldwin.cx ([147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id PAA04399; Tue, 18 Sep 2001 15:42:27 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 18 Sep 2001 15:42:13 -0700 (PDT) From: John Baldwin To: Julian Elischer Subject: Re: JKH Project: x86: pcb_ext Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-Sep-01 Julian Elischer wrote: > this is already on my list of "non 1:1 fixes needed" Heh, it was on my todo list for the past few months. :) Andrew Reiter has expressed interest in doing this. Do you object to him getting this done and freeing us both up for other things or do you wish to do it yourself? > On Tue, 18 Sep 2001, John Baldwin wrote: > >> Here's a Junior Kernel Hacker project for someone: >> >> - Move pcb_ext and pcb_ldt out of the pcb of struct thread and into >> struct mdproc; I.e., you probably want to do something like this: >> - Rename struct pcb_ext to struct proc_tss and struct pcb_ldt to >> struct proc_ldt. (Fixup pcb_ext member names to use a tss_ >> prefix instead of ext_) >> - Have a struct mdproc as so: >> >> struct mdproc { >> struct proc_tss *md_tss; >> struct proc_ldt *md_ldt; >> } >> >> Prior to KSE this was just annoyance but wasn't an actual problem. With KSE >> threads are temporary, whereas the ldt and tss are per-process properties >> that >> need to stick around. >> >> -- >> >> John Baldwin -- http://www.FreeBSD.org/~jhb/ >> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc >> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hackers" in the body of the message >> > -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 15:54:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id AA67237B40A; Tue, 18 Sep 2001 15:54:48 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA23052; Tue, 18 Sep 2001 16:38:58 -0700 (PDT) Date: Tue, 18 Sep 2001 16:38:57 -0700 (PDT) From: Julian Elischer To: John Baldwin Cc: hackers@FreeBSD.org Subject: Re: JKH Project: x86: pcb_ext In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG it's fine by me.... On Tue, 18 Sep 2001, John Baldwin wrote: > > On 18-Sep-01 Julian Elischer wrote: > > this is already on my list of "non 1:1 fixes needed" > > Heh, it was on my todo list for the past few months. :) Andrew Reiter has > expressed interest in doing this. Do you object to him getting this done and > freeing us both up for other things or do you wish to do it yourself? > > > On Tue, 18 Sep 2001, John Baldwin wrote: > > > >> Here's a Junior Kernel Hacker project for someone: > >> > >> - Move pcb_ext and pcb_ldt out of the pcb of struct thread and into > >> struct mdproc; I.e., you probably want to do something like this: > >> - Rename struct pcb_ext to struct proc_tss and struct pcb_ldt to > >> struct proc_ldt. (Fixup pcb_ext member names to use a tss_ > >> prefix instead of ext_) > >> - Have a struct mdproc as so: > >> > >> struct mdproc { > >> struct proc_tss *md_tss; > >> struct proc_ldt *md_ldt; > >> } > >> > >> Prior to KSE this was just annoyance but wasn't an actual problem. With KSE > >> threads are temporary, whereas the ldt and tss are per-process properties > >> that > >> need to stick around. > >> > >> -- > >> > >> John Baldwin -- http://www.FreeBSD.org/~jhb/ > >> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > >> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > >> > >> To Unsubscribe: send mail to majordomo@FreeBSD.org > >> with "unsubscribe freebsd-hackers" in the body of the message > >> > > > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 16:59:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id 8E94437B413; Tue, 18 Sep 2001 16:59:07 -0700 (PDT) Received: (from marcel@localhost) by kayak.xcllnt.net (8.11.4/8.11.4) id f8INx6Q02746; Tue, 18 Sep 2001 16:59:06 -0700 (PDT) (envelope-from marcel) Date: Tue, 18 Sep 2001 16:58:24 -0700 From: Marcel Moolenaar To: Maxim Sobolev Cc: chris@calldei.com, phk@critter.freebsd.dk, brent@rcfile.org, current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Junior Kernel Hacker task: improve vnode->v_tag Message-ID: <20010918165824.A2715@kayak.xcllnt.net> References: <20010908030110.E548@holly.calldei.com> <200109081154.OAA95138@www.abc.com.ua> <20010908150620.F548@holly.calldei.com> <3BA7397D.A82C213@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BA7397D.A82C213@FreeBSD.org> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Sep 18, 2001 at 03:09:33PM +0300, Maxim Sobolev wrote: The patch looks ok. There's a slight functional change that an ext2fs filesystem is now correctly returned as such. I don't expect Linux binaries to break, but it may be remotely possible that certain tools, now that they detect ext2fs filesystems, will use more specific ext2fs queries for whatever reason they need. I don't think it's something to worry about... > - case VT_UFS: > + else if (strcmp(fstypename, "ufs") == 0) > return (LINUX_UFS_SUPER_MAGIC); > - } > + else if (strcmp(fstypename, "ext2fs") == 0) > + return (LINUX_EXT2_SUPER_MAGIC); -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 17:15: 6 2001 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 50C5637B412; Tue, 18 Sep 2001 17:14:56 -0700 (PDT) Received: from cain.gsoft.com.au (root@spare0.gsoft.com.au [203.38.152.114]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id JAA20566; Wed, 19 Sep 2001 09:44:37 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010918163352.F90244@fump.kawo2.rwth-aachen.de> Date: Wed, 19 Sep 2001 09:44:38 +0930 (CST) From: "Daniel O'Connor" To: Alexander Langer Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Cc: Robert Withrow Cc: Robert Withrow , Jordan Hubbard , freebsd-hackers@FreeBSD.ORG, glenngombert@zdnetonebox.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-Sep-2001 Alexander Langer wrote: > > The previous suggestion (have a generic XFree86 port) is a) hacky, but b) > > workable in the current package framework I suspect.. > > Yes, would be a nice workaround. > > I don't use packages, though :) I'm forced not to if I'm using a machine which needs X4.. Usually for a fresh install I use packages since it gets a working machine quicker :) --- 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 Tue Sep 18 17:23:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nipsi.de (dsl-213-023-032-065.arcor-ip.net [213.23.32.65]) by hub.freebsd.org (Postfix) with SMTP id A9AD137B419 for ; Tue, 18 Sep 2001 17:23:01 -0700 (PDT) Received: (qmail 16561 invoked from network); 19 Sep 2001 00:21:10 -0000 Received: from unknown (HELO nipsi.de) (172.16.1.101) by nipsi with SMTP; 19 Sep 2001 00:21:10 -0000 Message-ID: <3BA7E580.9CFE9EBD@nipsi.de> Date: Wed, 19 Sep 2001 02:23:28 +0200 From: Dennis Berger X-Mailer: Mozilla 4.75 [de] (Windows NT 5.0; U) X-Accept-Language: de MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: problem: FreeBSD iplog tun-device Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG For some reason iplog doesn't work for tun-devices I don't know why, I think it happens after forking a new process, then a resource is not available. note this happens only if I run "iplog -i tun0", "iplog -i xl0" for example works fine. Maybe it happens because tun-device is opened by user-ppp. But a few month ago iplog works fine with tun-device although the device was opened. I added two ifconfigs and one processtrace of iplog. ------------------------------- Nipsi# ifconfig tun0 tun0: flags=8051 mtu 1492 inet6 fe80::210:4bff:feb3:ecd5%tun0 prefixlen 64 scopeid 0xc inet 213.23.32.65 --> 145.253.1.164 netmask 0xffffff00 Opened by PID 204 -------------------------------- -------------------------------- xl0: flags=8843 mtu 1500 inet 172.16.1.1 netmask 0xffff0000 broadcast 172.16.255.255 inet6 fe80::210:4bff:feb3:ecd5%xl0 prefixlen 64 scopeid 0x1 ether 00:10:4b:b3:ec:d5 media: Ethernet autoselect (100baseTX) status: active ------------------------------- -------------------------------------- Nipsi# truss -S iplog -i tun0 __sysctl(0xbfbffad0,0x2,0x28068c08,0xbfbffacc,0x0,0x0) = 0 (0x0) mmap(0x0,32768,0x3,0x1002,-1,0x0) = 671522816 (0x2806a000) geteuid() = 0 (0x0) getuid() = 0 (0x0) getegid() = 0 (0x0) getgid() = 0 (0x0) open("/var/run/ld-elf.so.hints",0,00) = 3 (0x3) read(0x3,0xbfbffab0,0x80) = 128 (0x80) lseek(3,0x80,0) = 128 (0x80) read(0x3,0x2806e000,0x51) = 81 (0x51) close(3) = 0 (0x0) access("/usr/lib/libpcap.so.2",0) = 0 (0x0) open("/usr/lib/libpcap.so.2",0,027757775450) = 3 (0x3) fstat(3,0xbfbffaf8) = 0 (0x0) read(0x3,0xbfbfeac8,0x1000) = 4096 (0x1000) mmap(0x0,106496,0x5,0x2,3,0x0) = 671555584 (0x28072000) mmap(0x2808a000,4096,0x3,0x12,3,0x17000) = 671653888 (0x2808a000) mmap(0x2808b000,4096,0x3,0x1012,-1,0x0) = 671657984 (0x2808b000) close(3) = 0 (0x0) access("/usr/lib/libc_r.so.4",0) = 0 (0x0) open("/usr/lib/libc_r.so.4",0,027757775450) = 3 (0x3) fstat(3,0xbfbffaf8) = 0 (0x0) read(0x3,0xbfbfeac8,0x1000) = 4096 (0x1000) mmap(0x0,745472,0x5,0x2,3,0x0) = 671662080 (0x2808c000) mmap(0x28122000,24576,0x3,0x12,3,0x95000) = 672276480 (0x28122000) mmap(0x28128000,106496,0x3,0x1012,-1,0x0) = 672301056 (0x28128000) close(3) = 0 (0x0) sigaction(SIGILL,0xbfbffb50,0xbfbffb38) = 0 (0x0) sigprocmask(0x1,0x0,0x28068b3c) = 0 (0x0) sigaction(SIGILL,0xbfbffb38,0x0) = 0 (0x0) getpid() = 16306 (0x3fb2) fcntl(0x0,0x3,0x0) = 2 (0x2) fcntl(0x1,0x3,0x0) = 2 (0x2) fcntl(0x2,0x3,0x0) = 2 (0x2) pipe() = 3 (0x3) fcntl(0x3,0x3,0x0) = 2 (0x2) fcntl(0x3,0x4,0x6) = 0 (0x0) fcntl(0x4,0x3,0x0) = 2 (0x2) fcntl(0x4,0x4,0x6) = 0 (0x0) readlink("/etc/malloc.conf",0xbfbff9a4,63) ERR#2 'No such file or directory' mmap(0x0,4096,0x3,0x1002,-1,0x0) = 672407552 (0x28142000) break(0x8059000) = 0 (0x0) break(0x805a000) = 0 (0x0) break(0x805b000) = 0 (0x0) break(0x805c000) = 0 (0x0) mmap(0xbfaff000,4096,0x0,0x1000,-1,0x0) = -1078988800 (0xbfaff000) gettimeofday(0x28124188,0x0) = 0 (0x0) break(0x8066000) = 0 (0x0) sigaltstack(0x2813fd40,0x0) = 0 (0x0) sigaction(SIGHUP,0x0,0x2813c5c0) = 0 (0x0) sigaction(SIGINT,0x0,0x2813c5d8) = 0 (0x0) sigaction(SIGQUIT,0x0,0x2813c5f0) = 0 (0x0) sigaction(SIGILL,0x0,0x2813c608) = 0 (0x0) sigaction(SIGTRAP,0x0,0x2813c620) = 0 (0x0) sigaction(SIGABRT,0x0,0x2813c638) = 0 (0x0) sigaction(SIGEMT,0x0,0x2813c650) = 0 (0x0) sigaction(SIGFPE,0x0,0x2813c668) = 0 (0x0) sigaction(SIGBUS,0x0,0x2813c698) = 0 (0x0) sigaction(SIGSEGV,0x0,0x2813c6b0) = 0 (0x0) sigaction(SIGSYS,0x0,0x2813c6c8) = 0 (0x0) sigaction(SIGPIPE,0x0,0x2813c6e0) = 0 (0x0) sigaction(SIGALRM,0x0,0x2813c6f8) = 0 (0x0) sigaction(SIGTERM,0x0,0x2813c710) = 0 (0x0) sigaction(SIGURG,0x0,0x2813c728) = 0 (0x0) sigaction(SIGTSTP,0x0,0x2813c758) = 0 (0x0) sigaction(SIGCONT,0x0,0x2813c770) = 0 (0x0) sigaction(SIGCHLD,0x0,0x2813c788) = 0 (0x0) sigaction(SIGTTIN,0x0,0x2813c7a0) = 0 (0x0) sigaction(SIGTTOU,0x0,0x2813c7b8) = 0 (0x0) sigaction(SIGIO,0x0,0x2813c7d0) = 0 (0x0) sigaction(SIGXCPU,0x0,0x2813c7e8) = 0 (0x0) sigaction(SIGXFSZ,0x0,0x2813c800) = 0 (0x0) sigaction(SIGVTALRM,0x0,0x2813c818) = 0 (0x0) sigaction(SIGPROF,0x0,0x2813c830) = 0 (0x0) sigaction(SIGWINCH,0x0,0x2813c848) = 0 (0x0) sigaction(SIGINFO,0x0,0x2813c860) = 0 (0x0) sigaction(SIGUSR1,0x0,0x2813c878) = 0 (0x0) sigaction(SIGUSR2,0x0,0x2813c890) = 0 (0x0) sigaction(SIGPROF,0xbfbffa88,0x0) = 0 (0x0) sigaction(SIGINFO,0xbfbffa88,0x0) = 0 (0x0) sigaction(SIGCHLD,0xbfbffa88,0x0) = 0 (0x0) sigprocmask(0x3,0x0,0x281241f8) = 0 (0x0) __sysctl(0xbfbffa80,0x2,0xbfbffaa0,0xbfbffa7c,0x0,0x0) = 0 (0x0) getdtablesize() = 32768 (0x8000) break(0x8086000) = 0 (0x0) break(0x80c6000) = 0 (0x0) break(0x80c7000) = 0 (0x0) fcntl(0x0,0x4,0x6) = 0 (0x0) fcntl(0x1,0x4,0x6) = 0 (0x0) fcntl(0x2,0x4,0x6) = 0 (0x0) break(0x80c8000) = 0 (0x0) sigprocmask(0x1,0x28068b00,0xbfbffb78) = 0 (0x0) sigprocmask(0x3,0x28068b10,0x0) = 0 (0x0) open("/usr/local/etc/iplog.conf",0,00) ERR#2 'No such file or directory' break(0x80c9000) = 0 (0x0) socket(0x1,0x2,0x0) = 5 (0x5) fcntl(0x5,0x3,0x0) = 2 (0x2) fcntl(0x5,0x4,0x6) = 0 (0x0) fcntl(0x5,0x2,0x1) = 0 (0x0) connect(0x5,0xbfbffac8,0x6a) = 0 (0x0) gettimeofday(0xbfbfee5c,0x0) = 0 (0x0) access("/etc/localtime",4) = 0 (0x0) open("/etc/localtime",0,00) = 6 (0x6) fcntl(0x6,0x3,0x0) = 0 (0x0) fcntl(0x6,0x4,0x4) = 0 (0x0) fstat(6,0xbfbfece4) = 0 (0x0) read(0x6,0xbfbfc9d8,0x1f08) = 837 (0x345) fstat(6,0xbfbfc924) = 0 (0x0) fcntl(0x6,0x3,0x0) = 4 (0x4) fcntl(0x6,0x4,0x0) = 0 (0x0) close(6) = 0 (0x0) getpid() = 16306 (0x3fb2) sendto(0x5,0xbfbff2e4,0x30,0x0,0x0,0x0) = 48 (0x30) fork() = 16307 (0x3fb3) sigreturn(0x8065e7c) = 16307 (0x3fb3) read(0x3,0x805bf38,0x80) ERR#35 'Resource temporarily unavailable' fcntl(0x0,0x4,0x6) = 0 (0x0) fcntl(0x1,0x4,0x6) = 0 (0x0) fcntl(0x2,0x4,0x6) = 0 (0x0) fcntl(0x5,0x4,0x6) = 0 (0x0) setitimer(0x2,0xbfbffb74,0x0) = 0 (0x0) close(3) = 0 (0x0) close(4) = 0 (0x0) fcntl(0x0,0x3,0x0) = 6 (0x6) fcntl(0x0,0x4,0x2) = 0 (0x0) fcntl(0x1,0x3,0x0) = 2 (0x2) fcntl(0x1,0x4,0x2) = 0 (0x0) fcntl(0x2,0x3,0x0) = 2 (0x2) fcntl(0x2,0x4,0x2) = 0 (0x0) fcntl(0x5,0x3,0x0) = 6 (0x6) fcntl(0x5,0x4,0x2) = 0 (0x0) exit(0x0) process exit, rval = 0 ----------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 17:28: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 5CEB137B40C for ; Tue, 18 Sep 2001 17:27:58 -0700 (PDT) Received: (qmail 355 invoked by uid 1001); 19 Sep 2001 00:27:57 -0000 Date: 18 Sep 2001 17:27:57 -0700 Date: Tue, 18 Sep 2001 17:27:57 -0700 From: Bill Swingle To: Eric Melville Cc: Sheldon Hearn , hackers@FreeBSD.org Subject: Re: Recent changes to libdialog are weird Message-ID: <20010918172757.A97849@dub.net> References: <95560.1000727060@axl.seasidesoftware.co.za> <20010918152142.A48126@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010918152142.A48126@FreeBSD.org>; from eric@FreeBSD.org on Tue, Sep 18, 2001 at 03:21:42PM -0700 X-Operating-System: FreeBSD toxic.magnesium.net 4.3-STABLE FreeBSD 4.3-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 18, 2001 at 03:21:42PM -0700, Eric Melville wrote: > > What many folks may not realize is that the new behaviour, while "safer" > > than what we had before, makes libdialog behave differently from at > > least Motif, Windows, JavaAWT, JavaSwing. >=20 > It seems to me that in popular toolkits, one moves the curson over the > desired component and presses a button. To do this with a keyboard, tab is > used to move the cursor, and space is used to press a button. I agree with and like the new behaviour but I think it is still lacking in one aspect. When using a mouse to position your cursor it's very obvious where that cursor is and what it's pointing to. With lidialog it's hard to tell at just a glance where the cursor is because it's only a few characters wide even if the "button" it's on is wider, and it's a drab gray color. If the cursor were something brighter and unique it might make it easier to distinguish as "the cursor" and there for easier to understand. Red maybe? Anyone else think this is a good idea? -Bill --=20 -=3D| Bill Swingle - -=3D| Every message PGP signed -=3D| Fingerprint: C1E3 49D1 EFC9 3EE0 EA6E 6414 5200 1C95 8E09 0223 -=3D| Different all twisty a of in maze are you, passages little --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7p+aNUgAclY4JAiMRAtrvAKCxq/6DyifFHydxdZGCHgIO3XcbqgCdGjel EwLcADoZMdKjgptIdXzBVBM= =cQwC -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 17:43:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 885) id 3EC4437B410; Tue, 18 Sep 2001 17:43:14 -0700 (PDT) Date: Tue, 18 Sep 2001 17:43:14 -0700 From: Eric Melville To: Bill Swingle Cc: Sheldon Hearn , hackers@FreeBSD.org Subject: Re: Recent changes to libdialog are weird Message-ID: <20010918174314.A68063@FreeBSD.org> References: <95560.1000727060@axl.seasidesoftware.co.za> <20010918152142.A48126@FreeBSD.org> <20010918172757.A97849@dub.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010918172757.A97849@dub.net>; from unfurl@dub.net on Tue, Sep 18, 2001 at 05:27:57PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I agree with and like the new behaviour but I think it is still lacking > in one aspect. When using a mouse to position your cursor it's very > obvious where that cursor is and what it's pointing to. With lidialog > it's hard to tell at just a glance where the cursor is because it's only > a few characters wide even if the "button" it's on is wider, and it's a > drab gray color. If the cursor were something brighter and unique it > might make it easier to distinguish as "the cursor" and there for easier > to understand. Red maybe? > > Anyone else think this is a good idea? That would be excellent. However, according to jkh there is no easy means of doing this, which leaves us with the option of changing the grey background around. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 17:50: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id 27A6837B40E for ; Tue, 18 Sep 2001 17:49:59 -0700 (PDT) Received: (qmail 45260 invoked by uid 1001); 19 Sep 2001 10:49:56 +1000 Message-ID: X-Posted-By: GJB-Post 2.21 16-Jun-2001 X-Operating-System: FreeBSD 4.2-RELEASE i386 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.gbch.net/gjb.html X-Image-URL: http://www.gbch.net/gjb/gjb-auug048.gif X-GPG-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-PGP-Public-Keys: http://www.gbch.net/keys.html Date: Wed, 19 Sep 2001 10:49:56 +1000 From: Greg Black To: Eric Melville Cc: Bill Swingle , Sheldon Hearn , hackers@FreeBSD.org Subject: Re: Recent changes to libdialog are weird References: <95560.1000727060@axl.seasidesoftware.co.za> <20010918152142.A48126@FreeBSD.org> <20010918172757.A97849@dub.net> <20010918174314.A68063@FreeBSD.org> In-reply-to: <20010918174314.A68063@FreeBSD.org> of Tue, 18 Sep 2001 17:43:14 MST Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Eric Melville wrote: | > I agree with and like the new behaviour but I think it is still lacking | > in one aspect. When using a mouse to position your cursor it's very | > obvious where that cursor is and what it's pointing to. With lidialog | > it's hard to tell at just a glance where the cursor is because it's only | > a few characters wide even if the "button" it's on is wider, and it's a | > drab gray color. If the cursor were something brighter and unique it | > might make it easier to distinguish as "the cursor" and there for easier | > to understand. Red maybe? | > | > Anyone else think this is a good idea? | | That would be excellent. However, according to jkh there is no easy means | of doing this, which leaves us with the option of changing the grey | background around. What it needs more than anything else is to learn to respond to Ctrl-L to repaint its screen. When something messes up the screen, it's a total nightmare to complete an install the way it is now. And it needs a way to go back step by step through the menus. There are too many ways that you can end up having to completely restart an install if you get tricked by one of the unintuitive keystrokes and go forward a level by mistake. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 17:51:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.viasoft.com.cn (unknown [61.153.1.177]) by hub.freebsd.org (Postfix) with ESMTP id C2E5237B40E; Tue, 18 Sep 2001 17:51:53 -0700 (PDT) Received: from davidwnt (davidwnt.viasoft.com.cn [192.168.1.239]) by mail.viasoft.com.cn (8.9.3/8.9.3) with SMTP id IAA17478; Wed, 19 Sep 2001 08:55:56 +0800 Message-ID: <002701c140a4$c5735a10$ef01a8c0@davidwnt> From: "David Xu" To: "Daniel O'Connor" , "Alexander Langer" Cc: "Robert Withrow" , "Jordan Hubbard" , , References: Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Date: Wed, 19 Sep 2001 08:48:14 +0800 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.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm confused why Open and NetBSD both have XF4 installed, while we = can't. why! David Xu ----- Original Message -----=20 From: "Daniel O'Connor" To: "Alexander Langer" Cc: "Robert Withrow" ; "Robert Withrow" = ; "Jordan Hubbard" ; = ; Sent: Wednesday, September 19, 2001 8:14 AM Subject: Re: Version of XFree86 in FreeBSD Release 4.4 >=20 > On 18-Sep-2001 Alexander Langer wrote: > > > The previous suggestion (have a generic XFree86 port) is a) hacky, = but b) > > > workable in the current package framework I suspect.. > > =20 > > Yes, would be a nice workaround. > > =20 > > I don't use packages, though :) >=20 > I'm forced not to if I'm using a machine which needs X4.. >=20 > Usually for a fresh install I use packages since it gets a working = machine > quicker :) >=20 > --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 18: 0:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.earlham.edu (cs.earlham.edu [159.28.230.3]) by hub.freebsd.org (Postfix) with ESMTP id 2A54F37B405 for ; Tue, 18 Sep 2001 18:00:54 -0700 (PDT) Received: from quark.cs.earlham.edu (quark.cs.earlham.edu [159.28.230.3]) by cs.earlham.edu (8.11.3/8.11.1) with ESMTP id f8J10Zu28381 for ; Tue, 18 Sep 2001 20:00:38 -0500 (EST) (envelope-from hassan@cs.earlham.edu) Date: Tue, 18 Sep 2001 20:00:35 -0500 (EST) From: Hassan Halta To: Subject: Compiling top in SMP Message-ID: <20010918195233.I27560-100000@quark.cs.earlham.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I hope some person will be able to help in this problem. I have a SMP enviorment with 2 CPUs, and things are working just fine, and the kernel recognizes everything. But The only problem that's top is misbehaving. However, it recognizes that there are 2 CPUs in the systems, but in the top stats it shows that every process is 0.00% of the CPU. Which's not true at all, we ran some testing to hammer the CPU and processes that should take 99.9% of the CPU, but it's always stuck on 0.00%. I tried to compile top which exists in /usr/src/contrib/top/ and it turns out that it's missing some modules of lists so that it can go ahead and compile, so I got that list, and got the codes for that, and tried to compile, but top just doesn't compile. I am not sure if I am in the right track by compiling top on the system. I was also wondering if there's another way to solve that problem. Thanks a lot, Hassan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 18:15:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 72DD837B40B for ; Tue, 18 Sep 2001 18:15:24 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id SAA23778; Tue, 18 Sep 2001 18:54:02 -0700 (PDT) Date: Tue, 18 Sep 2001 18:54:00 -0700 (PDT) From: Julian Elischer To: Hassan Halta Cc: freebsd-hackers@freebsd.org Subject: Re: Compiling top in SMP In-Reply-To: <20010918195233.I27560-100000@quark.cs.earlham.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG you don't say what version.... On Tue, 18 Sep 2001, Hassan Halta wrote: > Hello, > > I hope some person will be able to help in this problem. I have a > SMP enviorment with 2 CPUs, and things are working just fine, and the > kernel recognizes everything. But The only problem that's top is > misbehaving. However, it recognizes that there are 2 CPUs in the systems, > but in the top stats it shows that every process is 0.00% of the CPU. > Which's not true at all, we ran some testing to hammer the CPU and > processes that should take 99.9% of the CPU, but it's always stuck on > 0.00%. I tried to compile top which exists in /usr/src/contrib/top/ and it > turns out that it's missing some modules of lists so that it can go ahead > and compile, so I got that list, and got the codes for that, and tried to > compile, but top just doesn't compile. I am not sure if I am in the right > track by compiling top on the system. I was also wondering if there's > another way to solve that problem. > > Thanks a lot, > > Hassan > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 18:25:17 2001 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 549A837B405 for ; Tue, 18 Sep 2001 18:25:13 -0700 (PDT) Received: from cain.gsoft.com.au (root@spare0.gsoft.com.au [203.38.152.114]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA21445; Wed, 19 Sep 2001 10:55:07 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010918172055.BSRJ12461.mta11.onebox.com@onebox.com> Date: Wed, 19 Sep 2001 10:55:05 +0930 (CST) From: "Daniel O'Connor" To: glenn gombert Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-Sep-2001 glenn gombert wrote: > My interest in a later version of XFree86 is that in trying to install > FreeBSD-Current on my Dell Insperion 4000e Laptop, the ATI Rage 128 3D > graphics accelerator used is not supported at all under XFree86 3.3.6. > So I am forced to upgrade to a later version of XFree86 to get 'X' to > work at all.... > > Can someone outline the easiest way to do that given how things are > in the FreeBSD-4.3 Release?? Install the base OS, then build X from ports, or fetch the X4 package. Then start building packages that require X.. (Adding packages will fail because they all want X3, so you have to use ports) --- 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 Tue Sep 18 18:28: 9 2001 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 0D95C37B421; Tue, 18 Sep 2001 18:28:05 -0700 (PDT) Received: from cain.gsoft.com.au (root@spare0.gsoft.com.au [203.38.152.114]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA21472; Wed, 19 Sep 2001 10:57:52 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <002701c140a4$c5735a10$ef01a8c0@davidwnt> Date: Wed, 19 Sep 2001 10:57:52 +0930 (CST) From: "Daniel O'Connor" To: David Xu Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Cc: glenngombert@zdnetonebox.com, freebsd-hackers@FreeBSD.ORG, Jordan Hubbard , Robert Withrow , Alexander Langer Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 19-Sep-2001 David Xu wrote: > I'm confused why Open and NetBSD both have XF4 installed, while we can't. > why! Because X4 sucks to configure. (X -configure is neat but still not very friendly) X3 has a nice point and drool interface. X3 also supports more of the hardware out there than X4. --- 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 Tue Sep 18 18:31:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.earlham.edu (cs.earlham.edu [159.28.230.3]) by hub.freebsd.org (Postfix) with ESMTP id 4D54437B40B for ; Tue, 18 Sep 2001 18:31:11 -0700 (PDT) Received: from quark.cs.earlham.edu (quark.cs.earlham.edu [159.28.230.3]) by cs.earlham.edu (8.11.3/8.11.1) with ESMTP id f8J1UZu31250; Tue, 18 Sep 2001 20:30:35 -0500 (EST) (envelope-from hassan@cs.earlham.edu) Date: Tue, 18 Sep 2001 20:30:35 -0500 (EST) From: Hassan Halta To: Julian Elischer Cc: Subject: Re: Compiling top in SMP In-Reply-To: Message-ID: <20010918203022.Y31191-100000@quark.cs.earlham.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG FreeBSD 4.3 ;).. sorry.. -Hassan On Tue, 18 Sep 2001, Julian Elischer wrote: > Date: Tue, 18 Sep 2001 18:54:00 -0700 (PDT) > From: Julian Elischer > To: Hassan Halta > Cc: freebsd-hackers@FreeBSD.ORG > Subject: Re: Compiling top in SMP > > you don't say what version.... > > > On Tue, 18 Sep 2001, Hassan Halta wrote: > > > Hello, > > > > I hope some person will be able to help in this problem. I have a > > SMP enviorment with 2 CPUs, and things are working just fine, and the > > kernel recognizes everything. But The only problem that's top is > > misbehaving. However, it recognizes that there are 2 CPUs in the systems, > > but in the top stats it shows that every process is 0.00% of the CPU. > > Which's not true at all, we ran some testing to hammer the CPU and > > processes that should take 99.9% of the CPU, but it's always stuck on > > 0.00%. I tried to compile top which exists in /usr/src/contrib/top/ and it > > turns out that it's missing some modules of lists so that it can go ahead > > and compile, so I got that list, and got the codes for that, and tried to > > compile, but top just doesn't compile. I am not sure if I am in the right > > track by compiling top on the system. I was also wondering if there's > > another way to solve that problem. > > > > Thanks a lot, > > > > Hassan > > > > > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 20:54:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id A4B5E37B40D; Tue, 18 Sep 2001 20:54:05 -0700 (PDT) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id f8J3rjO06500; Tue, 18 Sep 2001 20:53:47 -0700 (PDT) (envelope-from jkh@freebsd.org) To: gjb@gbch.net Cc: eric@freebsd.org, unfurl@dub.net, sheldonh@starjuice.net, hackers@freebsd.org Subject: Re: Recent changes to libdialog are weird In-Reply-To: References: <20010918172757.A97849@dub.net> <20010918174314.A68063@FreeBSD.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010918205345P.jkh@freebsd.org> Date: Tue, 18 Sep 2001 20:53:45 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 60 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG libdialog(3) is extremely limited, as we've been saying for literally years now, and what I wish is that people would stop telling these lists "what it needs" and simply Do It. We've certainly never lacked for ideas on how to improve it, just the bodies to actually do so. The problem is that dealing with that code is extremely icky, and though I sometimes am mistakenly credited with writing it, I did not. It's a mish-mash of code from Savio Lam, a hacker in Hong Kong, Stuart Herbert in the UK and the project's own Andrey Chernov. I simply added call-back support and a few other tweaks to what was already an expanding ball of furr. Anyway, I've already made my opinion of libdialog(3) plain in other email so I won't repeat all that invective here. What I will say is that time is long overdue for someone to simply start from scratch and write another CUI library which isn't as horrible as libdialog but perhaps not so complex and object-oriented as TurboVision (maybe a higher-level C interface to some canned TV objects?). Then sysinstall could be re-targeted to that UI and people could finally have their nice item traversal and back-buttons and all that good stuff. I also really don't want to hear from Terry that he'd write such a thing if he were allowed to make it a commercial, closed-source component. Replacing a GPL'd library (libdialog) with some black-box binary-only solution wouldn't be a step in the right direction, it would be a side-ways step at best. A step in the *right* direction would be a BSD-licensed, world-buildable interface library of some sort. - Jordan > Eric Melville wrote: > > | > I agree with and like the new behaviour but I think it is still lacking > | > in one aspect. When using a mouse to position your cursor it's very > | > obvious where that cursor is and what it's pointing to. With lidialog > | > it's hard to tell at just a glance where the cursor is because it's only > | > a few characters wide even if the "button" it's on is wider, and it's a > | > drab gray color. If the cursor were something brighter and unique it > | > might make it easier to distinguish as "the cursor" and there for easier > | > to understand. Red maybe? > | > > | > Anyone else think this is a good idea? > | > | That would be excellent. However, according to jkh there is no easy means > | of doing this, which leaves us with the option of changing the grey > | background around. > > What it needs more than anything else is to learn to respond to > Ctrl-L to repaint its screen. When something messes up the > screen, it's a total nightmare to complete an install the way it > is now. > > And it needs a way to go back step by step through the menus. > There are too many ways that you can end up having to completely > restart an install if you get tricked by one of the unintuitive > keystrokes and go forward a level by mistake. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 20:55:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 004D237B403 for ; Tue, 18 Sep 2001 20:55:54 -0700 (PDT) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id f8J3smO06513; Tue, 18 Sep 2001 20:54:48 -0700 (PDT) (envelope-from jkh@freebsd.org) To: bsddiy@163.net Cc: doconnor@gsoft.com.au, alex@big.endian.de, bwithrow@nortelnetworks.com, freebsd-hackers@freebsd.org, glenngombert@zdnetonebox.com Subject: Re: Version of XFree86 in FreeBSD Release 4.4 In-Reply-To: <002701c140a4$c5735a10$ef01a8c0@davidwnt> References: <002701c140a4$c5735a10$ef01a8c0@davidwnt> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010918205448E.jkh@freebsd.org> Date: Tue, 18 Sep 2001 20:54:48 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 44 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Nobody ever said we couldn't. The word you're looking for is "won't" and if you want to know why, search the mailing list archives because it's all been discussed before and there's no point in going over old ground. - Jordan From: "David Xu" Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Date: Wed, 19 Sep 2001 08:48:14 +0800 > > I'm confused why Open and NetBSD both have XF4 installed, while we can't. why! > > David Xu > > ----- Original Message ----- > From: "Daniel O'Connor" > To: "Alexander Langer" > Cc: "Robert Withrow" ; "Robert Withrow" ; "Jordan Hubbard" ; ; > Sent: Wednesday, September 19, 2001 8:14 AM > Subject: Re: Version of XFree86 in FreeBSD Release 4.4 > > > > > > On 18-Sep-2001 Alexander Langer wrote: > > > > The previous suggestion (have a generic XFree86 port) is a) hacky, but b) > > > > workable in the current package framework I suspect.. > > > > > > Yes, would be a nice workaround. > > > > > > I don't use packages, though :) > > > > I'm forced not to if I'm using a machine which needs X4.. > > > > Usually for a fresh install I use packages since it gets a working machine > > quicker :) > > > > --- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 21:28:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id 7B94C37B416 for ; Tue, 18 Sep 2001 21:28:35 -0700 (PDT) Received: (qmail 57896 invoked by uid 1001); 19 Sep 2001 14:28:33 +1000 Message-ID: X-Posted-By: GJB-Post 2.21 16-Jun-2001 X-Operating-System: FreeBSD 4.2-RELEASE i386 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.gbch.net/gjb.html X-Image-URL: http://www.gbch.net/gjb/gjb-auug048.gif X-GPG-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-PGP-Public-Keys: http://www.gbch.net/keys.html Date: Wed, 19 Sep 2001 14:28:33 +1000 From: Greg Black To: Jordan Hubbard Cc: eric@freebsd.org, unfurl@dub.net, sheldonh@starjuice.net, hackers@freebsd.org Subject: Re: Recent changes to libdialog are weird References: <20010918172757.A97849@dub.net> <20010918174314.A68063@FreeBSD.org> <20010918205345P.jkh@freebsd.org> In-reply-to: <20010918205345P.jkh@freebsd.org> of Tue, 18 Sep 2001 20:53:45 MST Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jordan Hubbard wrote: | libdialog(3) is extremely limited, as we've been saying for literally | years now, and what I wish is that people would stop telling these | lists "what it needs" and simply Do It. We've certainly never lacked | for ideas on how to improve it, just the bodies to actually do so. I have no time to look at this project this year. If we get to 2002 and nobody has stepped up to the plate, feel free to remind me that I volunteered. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 21:29:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180]) by hub.freebsd.org (Postfix) with ESMTP id 6C62337B408; Tue, 18 Sep 2001 21:29:29 -0700 (PDT) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f8J4TTM97574; Tue, 18 Sep 2001 21:29:29 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id F229F380A; Tue, 18 Sep 2001 21:29:28 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: John Baldwin Cc: hackers@FreeBSD.ORG Subject: Re: JKH Project: x86: pcb_ext In-Reply-To: Date: Tue, 18 Sep 2001 21:29:28 -0700 From: Peter Wemm Message-Id: <20010919042928.F229F380A@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > Here's a Junior Kernel Hacker project for someone: > > - Move pcb_ext and pcb_ldt out of the pcb of struct thread and into > struct mdproc; I.e., you probably want to do something like this: > - Rename struct pcb_ext to struct proc_tss and struct pcb_ldt to > struct proc_ldt. (Fixup pcb_ext member names to use a tss_ > prefix instead of ext_) > - Have a struct mdproc as so: > > struct mdproc { > struct proc_tss *md_tss; > struct proc_ldt *md_ldt; > } > > Prior to KSE this was just annoyance but wasn't an actual problem. With KSE > threads are temporary, whereas the ldt and tss are per-process properties > that need to stick around. Just so that somebody doesn't get a nasty suprise.. this is not as simple as it sounds.. There are several configurations of "extended" pcb, including having a seperate i386tss.. The nasty part is that some of this is per-thread because there is a per-thread kernel stack pointer embedded in it. The upshot of this is that there probably needs to be a "master" pcb extension that gets propagated to thread children. In particular, look at these fragmets of swtch.s: movl PCB_EXT(%edx), %edi /* new tss descriptor */ [..] movl %edx, PCPU(COMMON_TSS) + TSS_ESP0 /* stack is below pcb */ [..] movl PCPU(TSS_GDT), %ebx /* entry in GDT */ movl 0(%edi), %eax movl %eax, 0(%ebx) movl 4(%edi), %eax movl %eax, 4(%ebx) movl $GPROC0_SEL*8, %esi /* GSEL(entry, SEL_KPL) */ ltr %si I think this is actually broken right now since the tss_esp0 is pointing to the wrong location.. It's actually pointing to an unmapped page. And note how we install the per-thread tss extension pointer into the per-cpu tss slot in the gdt. And, sys_machdep.c: ext->ext_tss.tss_esp0 = td->td_kstack + ctob(KSTACK_PAGES) - sizeof(struct pcb) - 16; We cannot entirely move the extended tss into into a mdproc since td_kstack is different in each thread. The more I think about it, the right place may be the kse, since that outlives the threads and is per-cpu unlike the process. Or, we just say "no pcb extensions for kse processes". Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 22: 8:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.clickarray.com (dune.clickarray.com [209.10.62.213]) by hub.freebsd.org (Postfix) with ESMTP id 12E1337B410; Tue, 18 Sep 2001 22:08:56 -0700 (PDT) Received: from vader.clickarray.com (nattedaddress.clickarray.com [10.2.1.199]) by mail.clickarray.com (Postfix) with ESMTP id 9B4235EF05; Tue, 18 Sep 2001 21:56:17 -0700 (PDT) Received: (from asami@localhost) by vader.clickarray.com (8.11.0/8.11.0) id f8J4kf343651; Tue, 18 Sep 2001 21:46:41 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) X-Authentication-Warning: vader.clickarray.com: asami set sender to asami@cs.berkeley.edu using -f To: obrien@FreeBSD.ORG Cc: Jordan Hubbard , glenngombert@zdnetonebox.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Version of XFree86 in FreeBSD Release 4.4 References: <20010917234536.JEJS12461.mta11.onebox.com@onebox.com> <20010917174223Z.jkh@freebsd.org> <20010918145722.A97809@dragon.nuxi.com> From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Date: 18 Sep 2001 21:46:41 -0700 In-Reply-To: <20010918145722.A97809@dragon.nuxi.com> (David O'Brien's message of "Tue, 18 Sep 2001 14:57:22 -0700") Message-ID: Lines: 21 User-Agent: T-gnus/6.14.5 (based on Gnus v5.8.7) (revision 06) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/20.7 (i386--freebsd) MULE/4.0 =?ISO-2022-JP?B?KBskQjJWMWMbKEIp?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Date: Tue, 18 Sep 2001 14:57:22 -0700 * From: "David O'Brien" * On Mon, Sep 17, 2001 at 05:42:23PM -0700, Jordan Hubbard wrote: * > We're still waiting for 4.0's "support footprint" to widen What do you mean by "support footprint"? If you mean graphic cards, all we need to do is to provide XF3 servers in addition to the XF4 bits. * > a bit more before subjecting people to it by default. Hopefully * > by 4.5. * * Are you really considering using XFree86 4.x in FreeBSD-4.5? * When I asked you about this in the past, you had said you wanted to keep * the same X in RELENG_4 (presumable to not "rock the boat" mid-branch). Given that FreeBSD 5.0 is pushed back a year, I think you should seriously reconsider that position... Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 22:54:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id D167437B41D; Tue, 18 Sep 2001 22:54:26 -0700 (PDT) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA24764; Tue, 18 Sep 2001 23:21:00 -0700 (PDT) Message-ID: <3BA82E8A.E297428E@elischer.org> Date: Tue, 18 Sep 2001 22:35:06 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Peter Wemm Cc: John Baldwin , hackers@FreeBSD.ORG Subject: Re: JKH Project: x86: pcb_ext References: <20010919042928.F229F380A@overcee.netplex.com.au> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Wemm wrote: > > John Baldwin wrote: > > Here's a Junior Kernel Hacker project for someone: > > > > - Move pcb_ext and pcb_ldt out of the pcb of struct thread and into > > struct mdproc; I.e., you probably want to do something like this: > > - Rename struct pcb_ext to struct proc_tss and struct pcb_ldt to > > struct proc_ldt. (Fixup pcb_ext member names to use a tss_ > > prefix instead of ext_) > > - Have a struct mdproc as so: > > > > struct mdproc { > > struct proc_tss *md_tss; > > struct proc_ldt *md_ldt; > > } > > > > Prior to KSE this was just annoyance but wasn't an actual problem. With KSE > > threads are temporary, whereas the ldt and tss are per-process properties > > that need to stick around. > > Just so that somebody doesn't get a nasty suprise.. this is not as > simple as it sounds.. There are several configurations of "extended" pcb, > including having a seperate i386tss.. The nasty part is that some of this > is per-thread because there is a per-thread kernel stack pointer embedded > in it. per cpu and per process... this is the domain of the KSE.. It should be duplicated from the 'master' one for each KSE created, and the appropriate stack pointer shifted into it when the thread is attached to the KSE to run. Since KSEs are per processor, there can only be one processor using each at a time, however there is still a problem with keeping the extensions UP TO DATE with each others when they are changed... We should be ok, if changes to the extension are only done via a well defined interface though. > > The upshot of this is that there probably needs to be a "master" pcb extension > that gets propagated to thread children. > > In particular, look at these fragmets of swtch.s: > > movl PCB_EXT(%edx), %edi /* new tss descriptor */ > [..] > movl %edx, PCPU(COMMON_TSS) + TSS_ESP0 /* stack is below pcb */ > [..] > movl PCPU(TSS_GDT), %ebx /* entry in GDT */ > movl 0(%edi), %eax > movl %eax, 0(%ebx) > movl 4(%edi), %eax > movl %eax, 4(%ebx) > movl $GPROC0_SEL*8, %esi /* GSEL(entry, SEL_KPL) */ > ltr %si > > I think this is actually broken right now since the tss_esp0 is pointing > to the wrong location.. It's actually pointing to an unmapped page. > > And note how we install the per-thread tss extension pointer into the > per-cpu tss slot in the gdt. > > And, sys_machdep.c: > ext->ext_tss.tss_esp0 = td->td_kstack + ctob(KSTACK_PAGES) - > sizeof(struct pcb) - 16; > > We cannot entirely move the extended tss into into a mdproc since td_kstack > is different in each thread. > > The more I think about it, the right place may be the kse, since that outlives > the threads and is per-cpu unlike the process. ah yes.. that's what I said...... > > Or, we just say "no pcb extensions for kse processes". I think we can do it.. though what would it be useful for? (unlikely that Multiple threads would be that useful in emulating DOS programs.. NT programs, maybe but the addaption layer would be a nightmare..) > > Cheers, > -Peter > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 18 23:48:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 5A43B37B410; Tue, 18 Sep 2001 23:48:11 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f8J6lou13070; Wed, 19 Sep 2001 00:47:50 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f8J6lZ700935; Wed, 19 Sep 2001 00:47:45 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109190647.f8J6lZ700935@harmony.village.org> To: "Daniel O'Connor" Subject: Re: Version of XFree86 in FreeBSD Release 4.4 Cc: David Xu , glenngombert@zdnetonebox.com, freebsd-hackers@FreeBSD.ORG, Jordan Hubbard , Robert Withrow , Alexander Langer In-reply-to: Your message of "Wed, 19 Sep 2001 10:57:52 +0930." References: Date: Wed, 19 Sep 2001 00:47:35 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message "Daniel O'Connor" writes: : X3 also supports more of the hardware out there than X4. X3 supports more OLDER hardware, while X4 supports some newer hardware better. X -configure is great when it works, but sucks otherwise. I've had both cases happen.. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 0:13:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rfhs8012.fh-regensburg.de (rfhs8012.fh-regensburg.de [194.95.108.29]) by hub.freebsd.org (Postfix) with ESMTP id 52F2437B421 for ; Wed, 19 Sep 2001 00:13:15 -0700 (PDT) Received: from rfhpc8320.fh-regensburg.de (wup34966@rfhpc8320.fh-regensburg.de [194.95.108.32]) by rfhs8012.fh-regensburg.de (8.11.6/8.11.6) with ESMTP id f8J7DE213013 for ; Wed, 19 Sep 2001 09:13:15 +0200 (MEST) Received: (from wup34966@localhost) by rfhpc8320.fh-regensburg.de (8.9.1/8.8.3) id JAA27357 for freebsd-hackers@freebsd.org; Wed, 19 Sep 2001 09:13:13 +0200 (MET DST) Date: Wed, 19 Sep 2001 09:13:13 +0200 From: Peter Wullinger To: freebsd-hackers@freebsd.org Subject: Re: where to set hw.ata.wc Message-ID: <20010919091313.A27353@rfhpc8320.fh-regensburg.de> References: <3BA77880.91744255@calcon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BA77880.91744255@calcon.net>; from degan@calcon.net on Tue, Sep 18, 2001 at 11:38:24AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG While at the topic: Anybody yet thought about a mountable filesystem for sysctl() values? Would be like Linux-procfs, but a lot cleaner (wth has pci/ to do with /proc?) Peter --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 1:14:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from reservoir.absolight.com (reservoir.absolight.com [212.43.217.72]) by hub.freebsd.org (Postfix) with ESMTP id 424F137B417 for ; Wed, 19 Sep 2001 01:14:46 -0700 (PDT) Received: from bilbo.in.mat.cc (bilbo.in.mat.cc [212.43.217.121]) by reservoir.absolight.com (Postfix) with ESMTP id D39E2D3B00; Wed, 19 Sep 2001 10:14:43 +0200 (CEST) Received: from bilbo.org (localhost [127.0.0.1]) by bilbo.in.mat.cc (Postfix) with ESMTP id D5A9B65554; Wed, 19 Sep 2001 12:16:22 +0200 (CEST) Received: from club-internet.fr (sauron.in.mat.cc [212.43.217.122]) by bilbo.in.mat.cc (Postfix) with ESMTP id 4CCF165554; Wed, 19 Sep 2001 12:16:19 +0200 (CEST) Message-ID: <3BA853EE.D99D7055@club-internet.fr> Date: Wed, 19 Sep 2001 10:14:38 +0200 From: Mathieu Arnold Organization: http://www.absolight.com/ X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Mathieu Arnold Cc: IP Filter , freebsd-hackers@freebsd.org Subject: Re: no memory problem References: <20010916182420.7CD723E02@drawbridge.oasis.IAEhv.nl> <3BA5234D.77226C3A@club-internet.fr> <3BA7AE18.4B490E6B@club-internet.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mathieu Arnold wrote: > > Mathieu Arnold wrote: > > > > Frank Volf wrote: > > > > > > Mathieu Arnold wrote: > > > > > What is the output of > > > > > > > > > > vmstat -m | egrep -i '(pfil|filter|temp)' > > > > > > > > well, for now, it's ok, as I rebooted the box yesterday > > > > temp 27491 12187K 16963K 40960K 15021633 0 0 > > > > 16,32,64,128,256,512,1K,4K,16K,512K > > > > but it will soon reach the 40960K limit. And I don't see where I can > > > > move this limit upper. > > > > > > You haven't reached the limits yet. I was wondering whether you were hitting > > > the limit for the zone or the limit for all malloced area. > > > > well, that's because I rebooted the box, usually, the max is 40964K. > > here we go again : > IP states added: > 9469918 TCP > 1654588 UDP > 1451233 ICMP > 2869559782 hits > 100258517 misses > 0 maximum > 72605 no memory > 2915 bkts in use > 9766 active > 3099381 expired > 9393987 closed > > temp 82729 39223K 40961K 40960K 51082243 0 442 > 16,32,64,128,256,512,1K,4K,16K,512K > > does someone here know how to raise that 40960K limit ? answering to myself, I found out (raised kern.vm.kmem.size in my loader.conf). but my point now is this : # ifdef M_PFIL # define KMALLOC(a, b) MALLOC((a), b, sizeof(*(a)), M_PFIL, M_NOWAIT) # define KMALLOCS(a, b, c) MALLOC((a), b, (c), M_PFIL, M_NOWAIT) # define KFREE(x) FREE((x), M_PFIL) # define KFREES(x,s) FREE((x), M_PFIL) # else # define KMALLOC(a, b) MALLOC((a), b, sizeof(*(a)), M_TEMP, M_NOWAIT) # define KMALLOCS(a, b, c) MALLOC((a), b, (c), M_TEMP, M_NOWAIT) # define KFREE(x) FREE((x), M_TEMP) # define KFREES(x,s) FREE((x), M_TEMP) # endif /* M_PFIL */ which is in ip_compat.h from the ipfilter source tree. why does it not define somewhere a space for itself ? should it be : MALLOC_DEFINE(M_PFIL, "ipfilter", "some bigger description"); or static MALLOC_DEFINE(M_PFIL, "ipfilter", "some bigger description"); ? regards -- Mathieu Arnold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 1:18:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.tecc.co.uk (luggage.tecc.co.uk [193.128.6.129]) by hub.freebsd.org (Postfix) with SMTP id 78CF737B427 for ; Wed, 19 Sep 2001 01:18:11 -0700 (PDT) Received: from fw-smtp.tecc.co.uk [195.217.37.39] by relay.tecc.co.uk with esmtp (Exim 1.70 #1) id 15jcYX-0007ab-00; Wed, 19 Sep 2001 09:18:05 +0100 Received: from [195.217.37.153] (helo=leven) by fw-smtp.tecc.co.uk with smtp (Exim 2.12 #3) id 15jcYX-00017z-00; Wed, 19 Sep 2001 09:18:05 +0100 From: "Andy" To: "Brandon Fosdick" , "mark tinguely" Cc: , , , , Subject: RE: CAN bus Date: Wed, 19 Sep 2001 09:18:26 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 In-Reply-To: <3BA7ADB9.769A7BB@glue.umd.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I designed a CAN controller for an embedded app some years ago now. However, I seem to remember the serial bit rate was pretty slow. Here's a link to more info if anyone's interested: http://www.can-ucan.com/ Regards Ak > Subject: Re: CAN bus > > mark tinguely wrote: > > > > > it is quite standard in industrial environments and still popular (at > > > least in europe) but existant installations slowly get replaced with > > > ethernet based (100baseFX) or industrial ethernet (10Mbit) > transceivers. > > > > I believe it was designed for noisy environments and is still used in > > automotive and large equipment (farm tractors, combines, etc). > > Thats why I chose it for my home automation project. There are a > lot of places > where I had to run the network wires right next to power wires. > Since CAN is > supposedly noise resistant and I don't need much bandwidth it > seemed like a > logical choice. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 1:19:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.tecc.co.uk (luggage.tecc.co.uk [193.128.6.129]) by hub.freebsd.org (Postfix) with SMTP id 923E337B412 for ; Wed, 19 Sep 2001 01:19:42 -0700 (PDT) Received: from fw-smtp.tecc.co.uk [195.217.37.39] by relay.tecc.co.uk with esmtp (Exim 1.70 #1) id 15jca2-0007ay-00; Wed, 19 Sep 2001 09:19:38 +0100 Received: from [195.217.37.153] (helo=leven) by fw-smtp.tecc.co.uk with smtp (Exim 2.12 #3) id 15jca1-0001B4-00; Wed, 19 Sep 2001 09:19:37 +0100 From: "Andy" To: "Brandon Fosdick" , "mark tinguely" Cc: , , , , Subject: RE: CAN bus Date: Wed, 19 Sep 2001 09:19:58 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <3BA7ADB9.769A7BB@glue.umd.edu> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I designed a CAN controller for an embedded app some years ago now. However, I seem to remember the serial bit rate was pretty slow. Here's a link to more info if anyone's interested: http://www.can-ucan.com/ Regards Ak > Subject: Re: CAN bus > > mark tinguely wrote: > > > > > it is quite standard in industrial environments and still popular (at > > > least in europe) but existant installations slowly get replaced with > > > ethernet based (100baseFX) or industrial ethernet (10Mbit) > transceivers. > > > > I believe it was designed for noisy environments and is still used in > > automotive and large equipment (farm tractors, combines, etc). > > Thats why I chose it for my home automation project. There are a > lot of places > where I had to run the network wires right next to power wires. > Since CAN is > supposedly noise resistant and I don't need much bandwidth it > seemed like a > logical choice. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 1:23:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from star.rila.bg (star.rila.bg [194.141.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 3D9B037B415; Wed, 19 Sep 2001 01:23:33 -0700 (PDT) Received: from star.rila.bg (vlady@localhost [127.0.0.1]) by star.rila.bg (8.11.4/8.11.4) with ESMTP id f8J8Pkc09377; Wed, 19 Sep 2001 11:25:46 +0300 (EEST) (envelope-from vlady@star.rila.bg) Message-Id: <200109190825.f8J8Pkc09377@star.rila.bg> X-Mailer: exmh version 2.4 05/15/2001 with nmh-1.0.3 To: freebsd-hackers@freebsd.org Cc: freebsd-ipfw@freebsd.org From: "Vladimir Terziev" Subject: Problem with IPFW and NATD (also sent to freebad-net mailing list) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Sep 2001 11:25:45 +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I have a gateway machine which runs NATD and have IP packet filter IPFW with the following rules: ipfw add 100 allow ip from any to any via lo0 ipfw add 10002 skipto 20000 tcp from 192.168.15.2 to any 21 ipfw add 10003 skipto 20000 tcp from 192.168.15.2 to any 53,6667,6668 ipfw add 10004 skipto 20000 udp from 192.168.15.2 to any 53,4000 ipfw add 11000 deny ip from 192.168.15.0/24 to any ipfw add 20000 divert natd ip from any to any via an0 ipfw add 63000 allow ip from PUBLIC_IP to any ipfw add 64000 allow ip from any to PUBLIC_IP ipfw add 30001 allow tcp from any 21 to 192.168.15.2 established ipfw add 30002 allow tcp from any 53,6667,6668 to 192.168.15.2 established ipfw add 30003 allow udp from any 53,4000 to 192.168.15.2 ipfw add 65000 deny ip from any to any The gateway machine is FreeBSD 4.4-RC and has 2 interfaces (internal, and external - an0). I need only one of machines in the local network to have connectivity to "the rest of the world". I've read all the documentation about ipfw(8), divert(4) and natd(8). Regarding to it the above rules should provide what I want, but they don't !!! Does anybody have an idea why? regards, Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 1:25:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from reservoir.absolight.com (reservoir.absolight.com [212.43.217.72]) by hub.freebsd.org (Postfix) with ESMTP id 407DD37B425 for ; Wed, 19 Sep 2001 01:25:09 -0700 (PDT) Received: from bilbo.in.mat.cc (bilbo.in.mat.cc [212.43.217.121]) by reservoir.absolight.com (Postfix) with ESMTP id 10920D3B05; Wed, 19 Sep 2001 10:25:07 +0200 (CEST) Received: from bilbo.org (localhost [127.0.0.1]) by bilbo.in.mat.cc (Postfix) with ESMTP id 0A66965554; Wed, 19 Sep 2001 12:26:45 +0200 (CEST) Received: from club-internet.fr (sauron.in.mat.cc [212.43.217.122]) by bilbo.in.mat.cc (Postfix) with ESMTP id 506D765554; Wed, 19 Sep 2001 12:26:42 +0200 (CEST) Message-ID: <3BA8565D.4A9686E3@club-internet.fr> Date: Wed, 19 Sep 2001 10:25:01 +0200 From: Mathieu Arnold Organization: http://www.absolight.com/ X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Mathieu Arnold Cc: IP Filter , freebsd-hackers@freebsd.org Subject: Re: no memory problem References: <20010916182420.7CD723E02@drawbridge.oasis.IAEhv.nl> <3BA5234D.77226C3A@club-internet.fr> <3BA7AE18.4B490E6B@club-internet.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mathieu Arnold wrote: > > Mathieu Arnold wrote: > > > > Frank Volf wrote: > > > > > > Mathieu Arnold wrote: > > > > > What is the output of > > > > > > > > > > vmstat -m | egrep -i '(pfil|filter|temp)' > > > > > > > > well, for now, it's ok, as I rebooted the box yesterday > > > > temp 27491 12187K 16963K 40960K 15021633 0 0 > > > > 16,32,64,128,256,512,1K,4K,16K,512K > > > > but it will soon reach the 40960K limit. And I don't see where I can > > > > move this limit upper. > > > > > > You haven't reached the limits yet. I was wondering whether you were hitting > > > the limit for the zone or the limit for all malloced area. > > > > well, that's because I rebooted the box, usually, the max is 40964K. > > here we go again : > IP states added: > 9469918 TCP > 1654588 UDP > 1451233 ICMP > 2869559782 hits > 100258517 misses > 0 maximum > 72605 no memory > 2915 bkts in use > 9766 active > 3099381 expired > 9393987 closed > > temp 82729 39223K 40961K 40960K 51082243 0 442 > 16,32,64,128,256,512,1K,4K,16K,512K > > does someone here know how to raise that 40960K limit ? answering to myself, I found out (raised kern.vm.kmem.size in my loader.conf). but my point now is this : # ifdef M_PFIL # define KMALLOC(a, b) MALLOC((a), b, sizeof(*(a)), M_PFIL, M_NOWAIT) # define KMALLOCS(a, b, c) MALLOC((a), b, (c), M_PFIL, M_NOWAIT) # define KFREE(x) FREE((x), M_PFIL) # define KFREES(x,s) FREE((x), M_PFIL) # else # define KMALLOC(a, b) MALLOC((a), b, sizeof(*(a)), M_TEMP, M_NOWAIT) # define KMALLOCS(a, b, c) MALLOC((a), b, (c), M_TEMP, M_NOWAIT) # define KFREE(x) FREE((x), M_TEMP) # define KFREES(x,s) FREE((x), M_TEMP) # endif /* M_PFIL */ which is in ip_compat.h from the ipfilter source tree. why does it not define somewhere a space for itself ? should it be : MALLOC_DEFINE(M_PFIL, "ipfilter", "some bigger description"); or static MALLOC_DEFINE(M_PFIL, "ipfilter", "some bigger description"); ? regards -- Mathieu Arnold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 3:58:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from brunel.uk1.vbc.net (brunel.uk1.vbc.net [194.207.2.8]) by hub.freebsd.org (Postfix) with ESMTP id 149A137B408 for ; Wed, 19 Sep 2001 03:58:28 -0700 (PDT) Received: from localhost (jcv@localhost) by brunel.uk1.vbc.net (8.11.6/8.11.6) with ESMTP id f8JAwQY13994 for ; Wed, 19 Sep 2001 11:58:27 +0100 (BST) X-Authentication-Warning: brunel.uk1.vbc.net: jcv owned process doing -bs Date: Wed, 19 Sep 2001 11:58:26 +0100 (BST) From: Jean-Christophe Varaillon X-Sender: jcv@brunel.uk1.vbc.net To: freebsd-hackers@FreeBSD.ORG Subject: Boot proccess Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Newbie, I need to understand the differents steps of a booting process from the 2 floppies (kern.flp & mfsroot.flp). How it comes and the FreeBSD machine can understand the fact that it has to find kern.flp & mfsroot.flp from the floppy, uncompress them, load them in the RAM and make them running ? In short, which program gives enough knowledge to the microprocessor (?) and allow him to use kern.flp & mfsroot.flp in order to boot and make the operating system running. Thanks in advance. Christophe. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 7: 4:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from star.rila.bg (star.rila.bg [194.141.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 3851037B416; Wed, 19 Sep 2001 07:04:27 -0700 (PDT) Received: from star.rila.bg (vlady@localhost [127.0.0.1]) by star.rila.bg (8.11.4/8.11.4) with ESMTP id f8JE6cc12197; Wed, 19 Sep 2001 17:06:39 +0300 (EEST) (envelope-from vlady@star.rila.bg) Message-Id: <200109191406.f8JE6cc12197@star.rila.bg> X-Mailer: exmh version 2.4 05/15/2001 with nmh-1.0.3 To: freebsd-net@freebsd.org Cc: freebsd-hackers@freebsd.org From: "Vladimir Terziev" Subject: Problem with IPFW and NATD (refined) !!! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Sep 2001 17:06:38 +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sorry, but there is a rule number mistake in my previous e-mail with the same subject. I have a gateway machine which runs NATD (natd -unregistered_only -interface an0) and have IP packet filter IPFW with the following rules: ipfw add 100 allow ip from any to any via lo0 ipfw add 10002 skipto 20000 tcp from 192.168.15.2 to any 21 ipfw add 10003 skipto 20000 tcp from 192.168.15.2 to any 53,6667,6668 ipfw add 10004 skipto 20000 udp from 192.168.15.2 to any 53,4000 ipfw add 11000 deny ip from 192.168.15.0/24 to any ipfw add 20000 divert natd ip from any to any via an0 ipfw add 30000 allow ip from PUBLIC_IP to any ipfw add 30000 allow ip from any to PUBLIC_IP ipfw add 40001 allow tcp from any 21 to 192.168.15.2 established ipfw add 40002 allow tcp from any 53,6667,6668 to 192.168.15.2 established ipfw add 40003 allow udp from any 53,4000 to 192.168.15.2 ipfw add 65000 deny ip from any to any The gateway machine is FreeBSD 4.4-RC and has 2 interfaces (internal, and external - an0). I need only one of machines in the local network to have connectivity to "the rest of the world". I've read all the documentation about ipfw(8), divert(4) and natd(8). Regarding to it the above rules should provide what I want, but they don't !!! Does anybody have an idea why? regards, Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 7:24:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id CD65537B411; Wed, 19 Sep 2001 07:23:52 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f8JEMFA99360; Wed, 19 Sep 2001 17:22:15 +0300 (EEST) (envelope-from ru) Date: Wed, 19 Sep 2001 17:22:15 +0300 From: Ruslan Ermilov To: Vladimir Terziev Cc: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Problem with IPFW and NATD (refined) !!! Message-ID: <20010919172215.E66974@sunbay.com> References: <200109191406.f8JE6cc12197@star.rila.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109191406.f8JE6cc12197@star.rila.bg>; from vladimirt@rila.bg on Wed, Sep 19, 2001 at 05:06:38PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [Please don't cross-post] You did not tell us what exactly does not work. DNS should work, and FTP should not as it requires data channel on a separate port. If that's the case, you may run natd(8) with the -punch_fw option. On Wed, Sep 19, 2001 at 05:06:38PM +0300, Vladimir Terziev wrote: > Sorry, but there is a rule number mistake in my previous e-mail with the same > subject. > > I have a gateway machine which runs NATD (natd -unregistered_only -interface > an0) and have IP packet filter IPFW with the following rules: > > > ipfw add 100 allow ip from any to any via lo0 > > ipfw add 10002 skipto 20000 tcp from 192.168.15.2 to any 21 > ipfw add 10003 skipto 20000 tcp from 192.168.15.2 to any 53,6667,6668 > ipfw add 10004 skipto 20000 udp from 192.168.15.2 to any 53,4000 > > ipfw add 11000 deny ip from 192.168.15.0/24 to any > > ipfw add 20000 divert natd ip from any to any via an0 > > ipfw add 30000 allow ip from PUBLIC_IP to any > ipfw add 30000 allow ip from any to PUBLIC_IP > > ipfw add 40001 allow tcp from any 21 to 192.168.15.2 established > ipfw add 40002 allow tcp from any 53,6667,6668 to 192.168.15.2 established > ipfw add 40003 allow udp from any 53,4000 to 192.168.15.2 > > ipfw add 65000 deny ip from any to any > > > The gateway machine is FreeBSD 4.4-RC and has 2 interfaces (internal, and > external - an0). I need only one of machines in the local network to have > connectivity to "the rest of the world". > > I've read all the documentation about ipfw(8), divert(4) and natd(8). > Regarding to it the above rules should provide what I want, but they don't !!! > > Does anybody have an idea why? > > regards, > Vladimir -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 10:26:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 973B037B419 for ; Wed, 19 Sep 2001 10:26:41 -0700 (PDT) Received: from laptop.baldwin.cx ([147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id KAA08043; Wed, 19 Sep 2001 10:26:35 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010919042928.F229F380A@overcee.netplex.com.au> Date: Wed, 19 Sep 2001 10:26:21 -0700 (PDT) From: John Baldwin To: Peter Wemm Subject: Re: JKH Project: x86: pcb_ext Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 19-Sep-01 Peter Wemm wrote: > The more I think about it, the right place may be the kse, since that > outlives > the threads and is per-cpu unlike the process. > > Or, we just say "no pcb extensions for kse processes". Each thread would need its own TSS, and to preserve existing semantics, we would have to change the TSS of all threads for each TSS related syscall. In light of that, I vote in favor of "no TSS's for kse processes" since TSS's are used for very few things anyways. LDT's are another matter and can be moved w/o a problem. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 10:52:59 2001 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 41D0337B417; Wed, 19 Sep 2001 10:52:54 -0700 (PDT) Received: from localhost (arr@localhost) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f8JHZ5I97074; Wed, 19 Sep 2001 13:35:05 -0400 (EDT) (envelope-from arr@watson.org) Date: Wed, 19 Sep 2001 13:35:04 -0400 (EDT) From: "Andrew R. Reiter" To: John Baldwin Cc: Peter Wemm , hackers@FreeBSD.ORG Subject: Re: JKH Project: x86: pcb_ext In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 19 Sep 2001, John Baldwin wrote: : :Each thread would need its own TSS, and to preserve existing semantics, we :would have to change the TSS of all threads for each TSS related syscall. In :light of that, I vote in favor of "no TSS's for kse processes" since TSS's are :used for very few things anyways. LDT's are another matter and can be moved :w/o a problem. Currently fixing a bug in my patch for moving ldt -> mdproc (in struct proc), when done I will let you know -- should be mid-day today. Cheers, Andrew *-------------................................................. | Andrew R. Reiter | arr@fledge.watson.org | "It requires a very unusual mind | to undertake the analysis of the obvious" -- A.N. Whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 15: 2:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shinatama.hayai.de (tekkno.tv [212.222.165.65]) by hub.freebsd.org (Postfix) with ESMTP id 0013437B40A for ; Wed, 19 Sep 2001 15:02:17 -0700 (PDT) Received: (from marco@localhost) by shinatama.hayai.de (8.11.6/8.11.3) id f8K02C760884; Thu, 20 Sep 2001 00:02:12 GMT (envelope-from marco) Date: Thu, 20 Sep 2001 00:02:12 +0000 From: Marco Wertejuk To: Jean-Christophe Varaillon Cc: freebsd-hackers@FREEBSD.ORG Subject: Re: Boot proccess Message-ID: <20010920000212.B60704@localhost.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jcv@vbc.net on Wed, Sep 19, 2001 at 11:58:26AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, | In short, which program gives enough knowledge to the microprocessor (?) | and allow him to use kern.flp & mfsroot.flp in order to boot and make the | operating system running. your BIOS reads the first sektor from your floppy which consists of a boot loader, which usually loads the 2nd step boot loader and this one loads the kernel. -- Mit freundlichen Gruessen, Marco Wertejuk - mwcis.com Computer/Internet/Security-Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 18:45:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id D812637B412; Wed, 19 Sep 2001 18:45:25 -0700 (PDT) Subject: Need testers, Broadcom BCM570x gigE driver To: freebsd-hackers@freebsd.org Date: Wed, 19 Sep 2001 18:45:25 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20010920014525.D812637B412@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ok, it's taken some doing, but I finally have a preliminary driver for the Broadcom BCM570x gigE controllers ready for testing. The code is at: http://www.freebsd.org/~wpaul/Broadcom/4.x This is for people with the following hardware: 3Com 3c996-T gigE NIC SysKonnect 9D21 gigE NIC Dell PowerEdge 2550 server with integrated BCM5700 I should have a FreeBSD 5.0-current driver ready soon (like, probably tomorrow). For now, only the source is available, and you need to perform the following steps to use it: 1) Install FreeBSD 4.3-RELEASE or later 2) Make sure you have the kernel source installed in /usr/src 3) Copy brgphy.c and brgphyreg.h to /sys/dev/mii. These files replace the copies that are already there. (You can save the older versions if you want.) 4) mkdir /sys/dev/bge 5) Copy if_bge.c and if_bgereg.h to /sys/dev/bge 6) Edit /sys/conf/files and add the following line: dev/bge/if_bge.c optional bge 7) Edit your kernel config file (e.g. /sys/i386/conf/MYKERNEL) and add the following line device bge # Broadcom BCM570x gigabit ethernet 8) Config and compile a new kernel Preliminary tests have yielded the following results: TCP, normal size frames: 440Mbps TCP, jumbo frames: 650Mbps UDP TX, normal frames: 710Mbps UDP TX, jumbo frames: 915Mbps Hardware checksum offload is enabled by default. These tests were done with the card in a 64-bit PCI slot. Anyone who has one of these cards and can test this driver for me, please do so and let me know your results. There may be one or two rough edges, so don't be too surprised if you run into an unusual problem. Only problem I've observed so far: on my 32-bit test box, RX checksum offload sometimes didn't behave right. To disable checksum offload, #define BGE_CSUM_FEATURES to 0, then recompile. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "I like zees guys. Zey are fonny guys. Just keel one of zem." -- The 3 Amigos ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 19: 3:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180]) by hub.freebsd.org (Postfix) with ESMTP id 3981937B40C for ; Wed, 19 Sep 2001 19:01:37 -0700 (PDT) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f8K21aM00883; Wed, 19 Sep 2001 19:01:37 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id E7F61380A; Wed, 19 Sep 2001 19:01:36 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: John Baldwin Cc: hackers@FreeBSD.org Subject: Re: JKH Project: x86: pcb_ext In-Reply-To: Date: Wed, 19 Sep 2001 19:01:36 -0700 From: Peter Wemm Message-Id: <20010920020136.E7F61380A@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > > On 19-Sep-01 Peter Wemm wrote: > > The more I think about it, the right place may be the kse, since that > > outlives > > the threads and is per-cpu unlike the process. > > > > Or, we just say "no pcb extensions for kse processes". > > Each thread would need its own TSS, and to preserve existing semantics, we > would have to change the TSS of all threads for each TSS related syscall. In > light of that, I vote in favor of "no TSS's for kse processes" since TSS's ar e > used for very few things anyways. LDT's are another matter and can be moved > w/o a problem. The main two things we seem to use the per-process TSS stuff for are: Fine grained IO port permission bitmap VM86 mode I think we can well do without the complexity of mixing KSE with those two. We still would need to sync LDT reloads.. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 19:53:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 04E3237B417; Wed, 19 Sep 2001 19:53:44 -0700 (PDT) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id UAA29293; Wed, 19 Sep 2001 20:39:08 -0700 (PDT) Message-ID: <3BA959E7.43CD9CD6@elischer.org> Date: Wed, 19 Sep 2001 19:52:23 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Peter Wemm Cc: John Baldwin , hackers@FreeBSD.org Subject: Re: JKH Project: x86: pcb_ext References: <20010920020136.E7F61380A@overcee.netplex.com.au> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Wemm wrote: > > John Baldwin wrote: > > > > On 19-Sep-01 Peter Wemm wrote: > > > The more I think about it, the right place may be the kse, since that > > > outlives > > > the threads and is per-cpu unlike the process. > > > > > > Or, we just say "no pcb extensions for kse processes". > > > > Each thread would need its own TSS, and to preserve existing semantics, we > > would have to change the TSS of all threads for each TSS related syscall. In > > light of that, I vote in favor of "no TSS's for kse processes" since TSS's ar > e > > used for very few things anyways. LDT's are another matter and can be moved > > w/o a problem. > > The main two things we seem to use the per-process TSS stuff for are: > Fine grained IO port permission bitmap > VM86 mode > I think we can well do without the complexity of mixing KSE with those two. I could IMAGINE a vm86 version that ran the control/exception thread on another processor as a different thread. (though who would write it?) I could also imagine a muli-threaded program doing IO to a device as a userland driver. but of course hey'd need to be writen explicitly for it.. > > We still would need to sync LDT reloads.. that's more of a worry for me. Do we still have separate a LDT for threads? > > Cheers, > -Peter > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 21: 0:53 2001 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 03CD837B40F; Wed, 19 Sep 2001 21:00:50 -0700 (PDT) Received: from localhost (arr@localhost) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f8K40AM04407; Thu, 20 Sep 2001 00:00:11 -0400 (EDT) (envelope-from arr@watson.org) Date: Thu, 20 Sep 2001 00:00:10 -0400 (EDT) From: "Andrew R. Reiter" To: Julian Elischer Cc: Peter Wemm , John Baldwin , hackers@FreeBSD.ORG Subject: Re: JKH Project: x86: pcb_ext In-Reply-To: <3BA959E7.43CD9CD6@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 19 Sep 2001, Julian Elischer wrote: :> :> We still would need to sync LDT reloads.. : :that's more of a worry for me. :Do we still have separate a LDT for threads? : LDT is per process therefore, in the patch I made, I moved pcb_ldt out of struct pcb and into mdproc (which is in struct proc). I've asked Peter to take a look at it and jhb, however, it is located at: http://www.watson.org/~arr/fbsd-patches/ldt-2-mdproc.diff Cheers, Andrew *-------------................................................. | Andrew R. Reiter | arr@fledge.watson.org | "It requires a very unusual mind | to undertake the analysis of the obvious" -- A.N. Whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 19 23: 3:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180]) by hub.freebsd.org (Postfix) with ESMTP id 390CE37B41A; Wed, 19 Sep 2001 23:03:12 -0700 (PDT) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f8K63BM01403; Wed, 19 Sep 2001 23:03:11 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id C6E9B380A; Wed, 19 Sep 2001 23:03:11 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: "Andrew R. Reiter" Cc: Julian Elischer , John Baldwin , hackers@FreeBSD.ORG Subject: Re: JKH Project: x86: pcb_ext In-Reply-To: Date: Wed, 19 Sep 2001 23:03:11 -0700 From: Peter Wemm Message-Id: <20010920060311.C6E9B380A@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Andrew R. Reiter" wrote: > On Wed, 19 Sep 2001, Julian Elischer wrote: > > :> > :> We still would need to sync LDT reloads.. > : > :that's more of a worry for me. > :Do we still have separate a LDT for threads? > : > > LDT is per process therefore, in the patch I made, I moved pcb_ldt out > of struct pcb and into mdproc (which is in struct proc). > > I've asked Peter to take a look at it and jhb, however, it is located at: > http://www.watson.org/~arr/fbsd-patches/ldt-2-mdproc.diff One comment: - cmpl $0, PCB_USERLDT(%edx) /* if there is one */ + movl TD_PROC(%ecx), %eax /* load struct proc from CURTHREAD */ + leal P_MD(%eax), %eax /* get mdproc from proc */ + cmpl $0, MD_LDT(%eax) /* if there is one */ This can be written as: movl TD_PROC(%ecx), %eax cmpl $0, P_MD+MD_LDT(%eax) This is evaluated at assemble time. And this change: movl %eax,PCPU(CURRENTLDT) /* store what we have */ jmp 2f -1: pushl %edx /* call a non-trusting routine */ +1: pushl %eax /* call a non-trusting routine */ call set_user_ldt /* to check and load the ldt */ - popl %edx + popl %eax 2: is not good.. you still need to save %edx since set_user_ldt is free to trash it (%edx is the secondary return value from a C function). eg: 0xc02e75c4 : mov 0x10(%ebx),%edx 0xc02e75c7 : mov %edx,(%eax,%ecx,1) 0xc02e75ca : mov 0x14(%ebx),%edx 0xc02e75cd : mov %edx,0x4(%eax,%ecx,1) The code after this in swtch.s depends on %edx being preserved. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 0:18:50 2001 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 A8FF537B411; Thu, 20 Sep 2001 00:18:46 -0700 (PDT) Received: from localhost (arr@localhost) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f8K7HI706415; Thu, 20 Sep 2001 03:18:03 -0400 (EDT) (envelope-from arr@watson.org) Date: Thu, 20 Sep 2001 03:17:18 -0400 (EDT) From: "Andrew R. Reiter" To: Peter Wemm Cc: Julian Elischer , John Baldwin , hackers@FreeBSD.ORG Subject: Re: JKH Project: x86: pcb_ext In-Reply-To: <20010920060311.C6E9B380A@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 19 Sep 2001, Peter Wemm wrote: : :One comment: : :- cmpl $0, PCB_USERLDT(%edx) /* if there is one */ :+ movl TD_PROC(%ecx), %eax /* load struct proc from CURTHREAD */ :+ leal P_MD(%eax), %eax /* get mdproc from proc */ :+ cmpl $0, MD_LDT(%eax) /* if there is one */ : : :This can be written as: : movl TD_PROC(%ecx), %eax : cmpl $0, P_MD+MD_LDT(%eax) : :This is evaluated at assemble time. Yea, Kinda dumb on my part :-/ : :And this change: : movl %eax,PCPU(CURRENTLDT) /* store what we have */ : jmp 2f : :-1: pushl %edx /* call a non-trusting routine */ :+1: pushl %eax /* call a non-trusting routine */ : call set_user_ldt /* to check and load the ldt */ :- popl %edx :+ popl %eax : 2: : :is not good.. you still need to save %edx since set_user_ldt is free :to trash it (%edx is the secondary return value from a C function). : Hmm interesting. Thanks. :eg: :0xc02e75c4 : mov 0x10(%ebx),%edx :0xc02e75c7 : mov %edx,(%eax,%ecx,1) :0xc02e75ca : mov 0x14(%ebx),%edx :0xc02e75cd : mov %edx,0x4(%eax,%ecx,1) : :The code after this in swtch.s depends on %edx being preserved. : :Cheers, :-Peter :-- :Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au :"All of this is for nothing if we don't go to the stars" - JMS/B5 : : *-------------................................................. | Andrew R. Reiter | arr@fledge.watson.org | "It requires a very unusual mind | to undertake the analysis of the obvious" -- A.N. Whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 1:59: 9 2001 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 94C5837B417; Thu, 20 Sep 2001 01:58:56 -0700 (PDT) Received: from localhost (arr@localhost) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f8K8wDN07417; Thu, 20 Sep 2001 04:58:22 -0400 (EDT) (envelope-from arr@watson.org) Date: Thu, 20 Sep 2001 04:58:13 -0400 (EDT) From: "Andrew R. Reiter" To: Peter Wemm Cc: Julian Elischer , John Baldwin , hackers@FreeBSD.ORG Subject: Re: JKH Project: x86: pcb_ext In-Reply-To: <20010920060311.C6E9B380A@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-739125287-1000976293=:7409" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-739125287-1000976293=:7409 Content-Type: TEXT/PLAIN; charset=US-ASCII Peter, Attached is the fix wrt your previous email. Again, can be found in www.watson.org/~arr/fbsd-patches/ Cheers, Andrew --0-739125287-1000976293=:7409 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="ldt-2-mdproc.fix.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: LS0tIGluY2x1ZGUvcGNiLmgub3JpZwlXZWQgU2VwIDE5IDAyOjA3OjQ4IDIw MDENCisrKyBpbmNsdWRlL3BjYi5oCVdlZCBTZXAgMTkgMDI6MDg6MzcgMjAw MQ0KQEAgLTYxLDcgKzYxLDYgQEANCiAJaW50ICAgICBwY2JfZHI2Ow0KIAlp bnQgICAgIHBjYl9kcjc7DQogDQotCXN0cnVjdAlwY2JfbGR0ICpwY2JfbGR0 OwkvKiBwZXIgcHJvY2VzcyAodXNlcikgTERUICovDQogCXVuaW9uCXNhdmVm cHUJcGNiX3NhdmU7DQogCXVfY2hhcglwY2JfZmxhZ3M7DQogI2RlZmluZQlG UF9TT0ZURlAJMHgwMQkvKiBwcm9jZXNzIHVzaW5nIHNvZnR3YXJlIGZsdG5n IHBudCBlbXVsYXRvciAqLw0KLS0tIGluY2x1ZGUvcGNiX2V4dC5oLm9yaWcJ V2VkIFNlcCAxOSAwMjowNzo1NCAyMDAxDQorKysgaW5jbHVkZS9wY2JfZXh0 LmgJV2VkIFNlcCAxOSAwMjoxMDozNyAyMDAxDQpAQCAtNDMsMjAgKzQzLDkg QEANCiAJc3RydWN0CXZtODZfa2VybmVsIGV4dF92bTg2OwkvKiB2bTg2IGFy ZWEgKi8NCiB9Ow0KIA0KLXN0cnVjdCBwY2JfbGR0IHsNCi0JY2FkZHJfdAls ZHRfYmFzZTsNCi0JaW50CWxkdF9sZW47DQotCWludAlsZHRfcmVmY250Ow0K LQl1X2xvbmcJbGR0X2FjdGl2ZTsNCi0Jc3RydWN0CXNlZ21lbnRfZGVzY3Jp cHRvciBsZHRfc2Q7DQotfTsNCi0NCiAjaWZkZWYgX0tFUk5FTA0KIA0KIGlu dCBpMzg2X2V4dGVuZF9wY2IgX19QKChzdHJ1Y3QgdGhyZWFkICopKTsNCi12 b2lkIHNldF91c2VyX2xkdCBfX1AoKHN0cnVjdCBwY2IgKikpOw0KLXN0cnVj dCBwY2JfbGR0ICp1c2VyX2xkdF9hbGxvYyBfX1AoKHN0cnVjdCBwY2IgKiwg aW50KSk7DQotdm9pZCB1c2VyX2xkdF9mcmVlIF9fUCgoc3RydWN0IHBjYiAq KSk7DQogDQogI2VuZGlmDQogDQotLS0gaW5jbHVkZS9wcm9jLmgub3JpZwlX ZWQgU2VwIDE5IDAyOjA3OjU5IDIwMDENCisrKyBpbmNsdWRlL3Byb2MuaAlX ZWQgU2VwIDE5IDAzOjI4OjU1IDIwMDENCkBAIC0zOCw2ICszOCwxNSBAQA0K ICNkZWZpbmUJX01BQ0hJTkVfUFJPQ19IXw0KIA0KICNpbmNsdWRlIDxtYWNo aW5lL2dsb2JhbHMuaD4NCisjaW5jbHVkZSA8bWFjaGluZS9zZWdtZW50cy5o Pg0KKw0KK3N0cnVjdCBwcm9jX2xkdCB7DQorICAgICAgICBjYWRkcl90IGxk dF9iYXNlOw0KKyAgICAgICAgaW50ICAgICBsZHRfbGVuOw0KKyAgICAgICAg aW50ICAgICBsZHRfcmVmY250Ow0KKyAgICAgICAgdV9sb25nICBsZHRfYWN0 aXZlOw0KKyAgICAgICAgc3RydWN0ICBzZWdtZW50X2Rlc2NyaXB0b3IgbGR0 X3NkOw0KK307DQogDQogLyoNCiAgKiBNYWNoaW5lLWRlcGVuZGVudCBwYXJ0 IG9mIHRoZSBwcm9jIHN0cnVjdHVyZSBmb3IgaTM4Ni4NCkBAIC00Niw2ICs1 NSwxNSBAQA0KIH07DQogDQogc3RydWN0IG1kcHJvYyB7DQorCXN0cnVjdCBw cm9jX2xkdCAqbWRfbGR0OwkvKiBwZXItcHJvY2VzcyBsZHQgKi8NCiB9Ow0K Kw0KKyNpZmRlZglfS0VSTkVMDQorDQordm9pZCAJc2V0X3VzZXJfbGR0IF9f UCgoc3RydWN0IG1kcHJvYyAqKSk7DQorc3RydWN0IAlwcm9jX2xkdCAqdXNl cl9sZHRfYWxsb2MgX19QKChzdHJ1Y3QgbWRwcm9jICosIGludCkpOw0KK3Zv aWQgCXVzZXJfbGR0X2ZyZWUgX19QKChzdHJ1Y3QgdGhyZWFkICopKTsNCisN CisjZW5kaWYJLyogX0tFUk5FTCAqLw0KIA0KICNlbmRpZiAvKiAhX01BQ0hJ TkVfUFJPQ19IXyAqLw0KLS0tIGkzODYvZ2VuYXNzeW0uYy5vcmlnCVdlZCBT ZXAgMTkgMDI6MTY6MzQgMjAwMQ0KKysrIGkzODYvZ2VuYXNzeW0uYwlXZWQg U2VwIDE5IDEzOjAzOjQ1IDIwMDENCkBAIC02Myw2ICs2Myw3IEBADQogI2lu Y2x1ZGUgPHZtL3BtYXAuaD4NCiAjaW5jbHVkZSA8dm0vdm1fbWFwLmg+DQog I2luY2x1ZGUgPHN5cy91c2VyLmg+DQorI2luY2x1ZGUgPHN5cy9wcm9jLmg+ DQogI2luY2x1ZGUgPG5ldC9pZi5oPg0KICNpbmNsdWRlIDxuZXRpbmV0L2lu Lmg+DQogI2luY2x1ZGUgPG5mcy9uZnNwcm90by5oPg0KQEAgLTc2LDYgKzc3 LDcgQEANCiAjaW5jbHVkZSA8bWFjaGluZS9zaWdmcmFtZS5oPg0KICNpbmNs dWRlIDxtYWNoaW5lL2dsb2JhbGRhdGEuaD4NCiAjaW5jbHVkZSA8bWFjaGlu ZS92bTg2Lmg+DQorI2luY2x1ZGUgPG1hY2hpbmUvcHJvYy5oPg0KIA0KIEFT U1lNKFBfVk1TUEFDRSwgb2Zmc2V0b2Yoc3RydWN0IHByb2MsIHBfdm1zcGFj ZSkpOw0KIEFTU1lNKFZNX1BNQVAsIG9mZnNldG9mKHN0cnVjdCB2bXNwYWNl LCB2bV9wbWFwKSk7DQpAQCAtOTIsNiArOTQsOSBAQA0KIEFTU1lNKFREX1BS T0MsIG9mZnNldG9mKHN0cnVjdCB0aHJlYWQsIHRkX3Byb2MpKTsNCiBBU1NZ TShURF9JTlRSX05FU1RJTkdfTEVWRUwsIG9mZnNldG9mKHN0cnVjdCB0aHJl YWQsIHRkX2ludHJfbmVzdGluZ19sZXZlbCkpOw0KIA0KK0FTU1lNKFBfTUQs IG9mZnNldG9mKHN0cnVjdCBwcm9jLCBwX21kKSk7DQorQVNTWU0oTURfTERU LCBvZmZzZXRvZihzdHJ1Y3QgbWRwcm9jLCBtZF9sZHQpKTsNCisNCiBBU1NZ TShLRV9GTEFHUywgb2Zmc2V0b2Yoc3RydWN0IGtzZSwga2VfZmxhZ3MpKTsN CiANCiBBU1NZTShLRUZfQVNUUEVORElORywgS0VGX0FTVFBFTkRJTkcpOw0K QEAgLTEyNiw3ICsxMzEsNiBAQA0KIEFTU1lNKFBDQl9FSVAsIG9mZnNldG9m KHN0cnVjdCBwY2IsIHBjYl9laXApKTsNCiBBU1NZTShUU1NfRVNQMCwgb2Zm c2V0b2Yoc3RydWN0IGkzODZ0c3MsIHRzc19lc3AwKSk7DQogDQotQVNTWU0o UENCX1VTRVJMRFQsIG9mZnNldG9mKHN0cnVjdCBwY2IsIHBjYl9sZHQpKTsN CiBBU1NZTShQQ0JfR1MsIG9mZnNldG9mKHN0cnVjdCBwY2IsIHBjYl9ncykp Ow0KIEFTU1lNKFBDQl9EUjAsIG9mZnNldG9mKHN0cnVjdCBwY2IsIHBjYl9k cjApKTsNCiBBU1NZTShQQ0JfRFIxLCBvZmZzZXRvZihzdHJ1Y3QgcGNiLCBw Y2JfZHIxKSk7DQotLS0gaTM4Ni9tYWNoZGVwLmMub3JpZwlXZWQgU2VwIDE5 IDAyOjE2OjM5IDIwMDENCisrKyBpMzg2L21hY2hkZXAuYwlXZWQgU2VwIDE5 IDA0OjU3OjMxIDIwMDENCkBAIC0xMDMsNiArMTAzLDcgQEANCiAjaW5jbHVk ZSA8bWFjaGluZS9tZF92YXIuaD4NCiAjaW5jbHVkZSA8bWFjaGluZS9wYy9i aW9zLmg+DQogI2luY2x1ZGUgPG1hY2hpbmUvcGNiX2V4dC5oPgkJLyogcGNi LmggaW5jbHVkZWQgdmlhIHN5cy91c2VyLmggKi8NCisjaW5jbHVkZSA8bWFj aGluZS9wcm9jLmg+DQogI2luY2x1ZGUgPG1hY2hpbmUvZ2xvYmFscy5oPg0K ICNpZmRlZiBQRVJGTU9ODQogI2luY2x1ZGUgPG1hY2hpbmUvcGVyZm1vbi5o Pg0KQEAgLTg4MCw4ICs4ODEsOCBAQA0KIAlzdHJ1Y3QgdHJhcGZyYW1lICpy ZWdzID0gdGQtPnRkX2ZyYW1lOw0KIAlzdHJ1Y3QgcGNiICpwY2IgPSB0ZC0+ dGRfcGNiOw0KIA0KLQlpZiAocGNiLT5wY2JfbGR0KQ0KLQkJdXNlcl9sZHRf ZnJlZShwY2IpOw0KKwlpZiAodGQtPnRkX3Byb2MtPnBfbWQubWRfbGR0KQ0K KwkJdXNlcl9sZHRfZnJlZSh0ZCk7DQogICANCiAJYnplcm8oKGNoYXIgKily ZWdzLCBzaXplb2Yoc3RydWN0IHRyYXBmcmFtZSkpOw0KIAlyZWdzLT50Zl9l aXAgPSBlbnRyeTsNCi0tLSBpMzg2L3N3dGNoLnMub3JpZwlXZWQgU2VwIDE5 IDAyOjE2OjE0IDIwMDENCisrKyBpMzg2L3N3dGNoLnMJVGh1IFNlcCAyMCAw Mzo1MTo1NSAyMDAxDQpAQCAtMjQ2LDcgKzI0Niw4IEBADQogCS8qIFhYWCBG SVhNRTogd2Ugc2hvdWxkIGJlIHJlc3RvcmluZyB0aGUgbG9jYWwgQVBJQyBU UFIgKi8NCiAjZW5kaWYgLyogU01QICovDQogDQotCWNtcGwJJDAsIFBDQl9V U0VSTERUKCVlZHgpCS8qIGlmIHRoZXJlIGlzIG9uZSAqLw0KKwltb3ZsCVRE X1BST0MoJWVjeCksICVlYXgJLyogbG9hZCBzdHJ1Y3QgcHJvYyBmcm9tIENV UlRIUkVBRCAqLw0KKwljbXBsICAgICQwLCBQX01EK01EX0xEVCglZWF4KSAg IC8qIHNlZSBpZiBtZF9sZHQgPT0gMCAqLw0KIAlqbnoJMWYJCQkvKiB0aGVu IHVzZSBpdCAqLw0KIAltb3ZsCV9kZWZhdWx0X2xkdCwlZWF4CS8qIFdlIHdp bGwgdXNlIHRoZSBkZWZhdWx0ICovDQogCWNtcGwJUENQVShDVVJSRU5UTERU KSwlZWF4CS8qIGNoZWNrIHRvIHNlZSBpZiBhbHJlYWR5IGxvYWRlZCAqLw0K QEAgLTI1NSw5ICsyNTYsMTEgQEANCiAJbW92bAklZWF4LFBDUFUoQ1VSUkVO VExEVCkJLyogc3RvcmUgd2hhdCB3ZSBoYXZlICovDQogCWptcAkyZg0KIA0K LTE6CXB1c2hsCSVlZHgJCQkvKiBjYWxsIGEgbm9uLXRydXN0aW5nIHJvdXRp bmUgKi8NCi0JY2FsbAlzZXRfdXNlcl9sZHQJCS8qIHRvIGNoZWNrIGFuZCBs b2FkIHRoZSBsZHQgKi8NCi0JcG9wbAklZWR4DQorMToJcHVzaGwJJWVkeAkJ CS8qIHNhdmUgZWR4ICovDQorCXB1c2hsCVBfTUQrTURfTERUKCVlYXgpCS8q IHBhc3NpbmcgcF9tZCAtPiBzZXRfdXNlcl9sZHQgKi8NCisJY2FsbAlzZXRf dXNlcl9sZHQJCS8qIGNoZWNrIGFuZCBsb2FkIHRoZSBsZHQgKi8NCisJcG9w bAklZWF4CQkJLyogZ2V0IHBfbWQgb2ZmIHN0YWNrICovDQorCXBvcGwJJWVk eAkJCS8qIHJlc3RvcmUgZWR4ICovDQogMjoNCiANCiAJLyogVGhpcyBtdXN0 IGJlIGRvbmUgYWZ0ZXIgbG9hZGluZyB0aGUgdXNlciBMRFQuICovDQotLS0g aTM4Ni9zeXNfbWFjaGRlcC5jLm9yaWcJV2VkIFNlcCAxOSAwMjoxNjoyMiAy MDAxDQorKysgaTM4Ni9zeXNfbWFjaGRlcC5jCVdlZCBTZXAgMTkgMDQ6MzQ6 MzAgMjAwMQ0KQEAgLTU0LDYgKzU0LDcgQEANCiANCiAjaW5jbHVkZSA8bWFj aGluZS9jcHUuaD4NCiAjaW5jbHVkZSA8bWFjaGluZS9wY2JfZXh0Lmg+CS8q IHBjYi5oIGluY2x1ZGVkIGJ5IHN5cy91c2VyLmggKi8NCisjaW5jbHVkZSA8 bWFjaGluZS9wcm9jLmg+DQogI2luY2x1ZGUgPG1hY2hpbmUvc3lzYXJjaC5o Pg0KIA0KICNpbmNsdWRlIDx2bS92bV9rZXJuLmg+CQkvKiBmb3Iga2VybmVs X21hcCAqLw0KQEAgLTcwLDcgKzcxLDcgQEANCiBzdGF0aWMgaW50IGkzODZf Z2V0X2lvcGVybQlfX1AoKHN0cnVjdCB0aHJlYWQgKiwgY2hhciAqKSk7DQog c3RhdGljIGludCBpMzg2X3NldF9pb3Blcm0JX19QKChzdHJ1Y3QgdGhyZWFk ICosIGNoYXIgKikpOw0KICNpZmRlZiBTTVANCi1zdGF0aWMgdm9pZCBzZXRf dXNlcl9sZHRfcnYJX19QKChzdHJ1Y3QgcGNiICopKTsNCitzdGF0aWMgdm9p ZCBzZXRfdXNlcl9sZHRfcnYJX19QKChzdHJ1Y3QgdGhyZWFkICopKTsNCiAj ZW5kaWYNCiANCiAjaWZuZGVmIF9TWVNfU1lTUFJPVE9fSF8NCkBAIC0yNTcs MTUgKzI1OCwxNSBAQA0KICAqIGN1cnByb2MgYnV0IGJlZm9yZSBzY2hlZF9s b2NrJ3Mgb3duZXIgaXMgdXBkYXRlZCBpbiBtaV9zd2l0Y2goKS4NCiAgKi8g ICANCiB2b2lkDQotc2V0X3VzZXJfbGR0KHN0cnVjdCBwY2IgKnBjYikNCitz ZXRfdXNlcl9sZHQoc3RydWN0IG1kcHJvYyAqbWRwKQ0KIHsNCi0Jc3RydWN0 IHBjYl9sZHQgKnBjYl9sZHQ7DQorCXN0cnVjdCBwcm9jX2xkdCAqcGxkdDsN CiANCi0JcGNiX2xkdCA9IHBjYi0+cGNiX2xkdDsNCisJcGxkdCA9IG1kcC0+ bWRfbGR0Ow0KICNpZmRlZiBTTVANCi0JZ2R0W1BDUFVfR0VUKGNwdWlkKSAq IE5HRFQgKyBHVVNFUkxEVF9TRUxdLnNkID0gcGNiX2xkdC0+bGR0X3NkOw0K KwlnZHRbUENQVV9HRVQoY3B1aWQpICogTkdEVCArIEdVU0VSTERUX1NFTF0u c2QgPSBwbGR0LT5sZHRfc2Q7DQogI2Vsc2UNCi0JZ2R0W0dVU0VSTERUX1NF TF0uc2QgPSBwY2JfbGR0LT5sZHRfc2Q7DQorCWdkdFtHVVNFUkxEVF9TRUxd LnNkID0gcGxkdC0+bGR0X3NkOw0KICNlbmRpZg0KIAlsbGR0KEdTRUwoR1VT RVJMRFRfU0VMLCBTRUxfS1BMKSk7DQogCVBDUFVfU0VUKGN1cnJlbnRsZHQs IEdTRUwoR1VTRVJMRFRfU0VMLCBTRUxfS1BMKSk7DQpAQCAtMjczLDE0ICsy NzQsMTQgQEANCiANCiAjaWZkZWYgU01QDQogc3RhdGljIHZvaWQNCi1zZXRf dXNlcl9sZHRfcnYoc3RydWN0IHBjYiAqcGNiKQ0KK3NldF91c2VyX2xkdF9y dihzdHJ1Y3QgdGhyZWFkICp0ZCkNCiB7DQogDQotCWlmIChwY2IgIT0gUENQ VV9HRVQoY3VycGNiKSkNCisJaWYgKHRkICE9IFBDUFVfR0VUKGN1cnRocmVh ZCkpDQogCQlyZXR1cm47DQogDQogCW10eF9sb2NrX3NwaW4oJnNjaGVkX2xv Y2spOw0KLQlzZXRfdXNlcl9sZHQocGNiKTsNCisJc2V0X3VzZXJfbGR0KCZ0 ZC0+dGRfcHJvYy0+cF9tZCk7DQogCW10eF91bmxvY2tfc3Bpbigmc2NoZWRf bG9jayk7DQogfQ0KICNlbmRpZg0KQEAgLTI4OSwxNSArMjkwLDE1IEBADQog ICogTXVzdCBiZSBjYWxsZWQgd2l0aCBlaXRoZXIgc2NoZWRfbG9jayBmcmVl IG9yIGhlbGQgYnV0IG5vdCByZWN1cnNlZC4NCiAgKiBJZiBpdCBkb2VzIG5v dCByZXR1cm4gTlVMTCwgaXQgd2lsbCByZXR1cm4gd2l0aCBpdCBvd25lZC4N CiAgKi8NCi1zdHJ1Y3QgcGNiX2xkdCAqDQotdXNlcl9sZHRfYWxsb2Moc3Ry dWN0IHBjYiAqcGNiLCBpbnQgbGVuKQ0KK3N0cnVjdCBwcm9jX2xkdCAqDQor dXNlcl9sZHRfYWxsb2Moc3RydWN0IG1kcHJvYyAqbWRwLCBpbnQgbGVuKQ0K IHsNCi0Jc3RydWN0IHBjYl9sZHQgKnBjYl9sZHQsICpuZXdfbGR0Ow0KKwlz dHJ1Y3QgcHJvY19sZHQgKnBsZHQsICpuZXdfbGR0Ow0KIA0KIAlpZiAobXR4 X293bmVkKCZzY2hlZF9sb2NrKSkNCiAJCW10eF91bmxvY2tfc3Bpbigmc2No ZWRfbG9jayk7DQogCW10eF9hc3NlcnQoJnNjaGVkX2xvY2ssIE1BX05PVE9X TkVEKTsNCi0JTUFMTE9DKG5ld19sZHQsIHN0cnVjdCBwY2JfbGR0ICosIHNp emVvZihzdHJ1Y3QgcGNiX2xkdCksDQorCU1BTExPQyhuZXdfbGR0LCBzdHJ1 Y3QgcHJvY19sZHQgKiwgc2l6ZW9mKHN0cnVjdCBwcm9jX2xkdCksDQogCQlN X1NVQlBST0MsIE1fV0FJVE9LKTsNCiANCiAJbmV3X2xkdC0+bGR0X2xlbiA9 IGxlbiA9IE5FV19NQVhfTEQobGVuKTsNCkBAIC0zMTUsMTEgKzMxNiwxMSBA QA0KIAlnZHRfc2Vnc1tHVVNFUkxEVF9TRUxdLnNzZF9saW1pdCA9IGxlbiAq IHNpemVvZih1bmlvbiBkZXNjcmlwdG9yKSAtIDE7DQogCXNzZHRvc2QoJmdk dF9zZWdzW0dVU0VSTERUX1NFTF0sICZuZXdfbGR0LT5sZHRfc2QpOw0KIA0K LQlpZiAoKHBjYl9sZHQgPSBwY2ItPnBjYl9sZHQpKSB7DQotCQlpZiAobGVu ID4gcGNiX2xkdC0+bGR0X2xlbikNCi0JCQlsZW4gPSBwY2JfbGR0LT5sZHRf bGVuOw0KLQkJYmNvcHkocGNiX2xkdC0+bGR0X2Jhc2UsIG5ld19sZHQtPmxk dF9iYXNlLA0KLQkJCWxlbiAqIHNpemVvZih1bmlvbiBkZXNjcmlwdG9yKSk7 DQorCWlmICgocGxkdCA9IG1kcC0+bWRfbGR0KSkgew0KKwkJaWYgKGxlbiA+ IHBsZHQtPmxkdF9sZW4pDQorCQkJbGVuID0gcGxkdC0+bGR0X2xlbjsNCisJ CWJjb3B5KHBsZHQtPmxkdF9iYXNlLCBuZXdfbGR0LT5sZHRfYmFzZSwNCisJ CSAgICBsZW4gKiBzaXplb2YodW5pb24gZGVzY3JpcHRvcikpOw0KIAl9IGVs c2Ugew0KIAkJYmNvcHkobGR0LCBuZXdfbGR0LT5sZHRfYmFzZSwgc2l6ZW9m KGxkdCkpOw0KIAl9DQpAQCAtMzI4LDMwICszMjksMzEgQEANCiANCiAvKg0K ICAqIE11c3QgYmUgY2FsbGVkIGVpdGhlciB3aXRoIHNjaGVkX2xvY2sgZnJl ZSBvciBoZWxkIGJ1dCBub3QgcmVjdXJzZWQuDQotICogSWYgcGNiLT5wY2Jf bGR0IGlzIG5vdCBOVUxMLCBpdCB3aWxsIHJldHVybiB3aXRoIHNjaGVkX2xv Y2sgcmVsZWFzZWQuDQorICogSWYgbWRfbGR0IGlzIG5vdCBOVUxMLCBpdCB3 aWxsIHJldHVybiB3aXRoIHNjaGVkX2xvY2sgcmVsZWFzZWQuDQogICovDQog dm9pZA0KLXVzZXJfbGR0X2ZyZWUoc3RydWN0IHBjYiAqcGNiKQ0KK3VzZXJf bGR0X2ZyZWUoc3RydWN0IHRocmVhZCAqdGQpDQogew0KLQlzdHJ1Y3QgcGNi X2xkdCAqcGNiX2xkdCA9IHBjYi0+cGNiX2xkdDsNCisJc3RydWN0IG1kcHJv YyAqbWRwID0gJnRkLT50ZF9wcm9jLT5wX21kOw0KKwlzdHJ1Y3QgcHJvY19s ZHQgKnBsZHQgPSBtZHAtPm1kX2xkdDsNCiANCi0JaWYgKHBjYl9sZHQgPT0g TlVMTCkNCisJaWYgKHBsZHQgPT0gTlVMTCkNCiAJCXJldHVybjsNCiANCiAJ aWYgKCFtdHhfb3duZWQoJnNjaGVkX2xvY2spKQ0KIAkJbXR4X2xvY2tfc3Bp bigmc2NoZWRfbG9jayk7DQogCW10eF9hc3NlcnQoJnNjaGVkX2xvY2ssIE1B X09XTkVEIHwgTUFfTk9UUkVDVVJTRUQpOw0KLQlpZiAocGNiID09IFBDUFVf R0VUKGN1cnBjYikpIHsNCisJaWYgKHRkID09IFBDUFVfR0VUKGN1cnRocmVh ZCkpIHsNCiAJCWxsZHQoX2RlZmF1bHRfbGR0KTsNCiAJCVBDUFVfU0VUKGN1 cnJlbnRsZHQsIF9kZWZhdWx0X2xkdCk7DQogCX0NCiANCi0JcGNiLT5wY2Jf bGR0ID0gTlVMTDsNCi0JaWYgKC0tcGNiX2xkdC0+bGR0X3JlZmNudCA9PSAw KSB7DQorCW1kcC0+bWRfbGR0ID0gTlVMTDsNCisJaWYgKC0tcGxkdC0+bGR0 X3JlZmNudCA9PSAwKSB7DQogCQltdHhfdW5sb2NrX3NwaW4oJnNjaGVkX2xv Y2spOw0KLQkJa21lbV9mcmVlKGtlcm5lbF9tYXAsICh2bV9vZmZzZXRfdClw Y2JfbGR0LT5sZHRfYmFzZSwNCi0JCQlwY2JfbGR0LT5sZHRfbGVuICogc2l6 ZW9mKHVuaW9uIGRlc2NyaXB0b3IpKTsNCi0JCUZSRUUocGNiX2xkdCwgTV9T VUJQUk9DKTsNCisJCWttZW1fZnJlZShrZXJuZWxfbWFwLCAodm1fb2Zmc2V0 X3QpcGxkdC0+bGR0X2Jhc2UsDQorCQkJcGxkdC0+bGR0X2xlbiAqIHNpemVv Zih1bmlvbiBkZXNjcmlwdG9yKSk7DQorCQlGUkVFKHBsZHQsIE1fU1VCUFJP Qyk7DQogCX0gZWxzZQ0KIAkJbXR4X3VubG9ja19zcGluKCZzY2hlZF9sb2Nr KTsNCiB9DQpAQCAtMzYyLDggKzM2NCw3IEBADQogCWNoYXIgKmFyZ3M7DQog ew0KIAlpbnQgZXJyb3IgPSAwOw0KLQlzdHJ1Y3QgcGNiICpwY2IgPSB0ZC0+ dGRfcGNiOw0KLQlzdHJ1Y3QgcGNiX2xkdCAqcGNiX2xkdCA9IHBjYi0+cGNi X2xkdDsNCisJc3RydWN0IHByb2NfbGR0ICpwbGR0ID0gdGQtPnRkX3Byb2Mt PnBfbWQubWRfbGR0Ow0KIAlpbnQgbmxkdCwgbnVtOw0KIAl1bmlvbiBkZXNj cmlwdG9yICpscDsNCiAJc3RydWN0IGkzODZfbGR0X2FyZ3MgdWEsICp1YXAg PSAmdWE7DQpAQCAtMzgwLDEwICszODEsMTAgQEANCiAJaWYgKCh1YXAtPnN0 YXJ0IDwgMCkgfHwgKHVhcC0+bnVtIDw9IDApKQ0KIAkJcmV0dXJuKEVJTlZB TCk7DQogDQotCWlmIChwY2JfbGR0KSB7DQotCQlubGR0ID0gcGNiX2xkdC0+ bGR0X2xlbjsNCisJaWYgKHBsZHQpIHsNCisJCW5sZHQgPSBwbGR0LT5sZHRf bGVuOw0KIAkJbnVtID0gbWluKHVhcC0+bnVtLCBubGR0KTsNCi0JCWxwID0g JigodW5pb24gZGVzY3JpcHRvciAqKShwY2JfbGR0LT5sZHRfYmFzZSkpW3Vh cC0+c3RhcnRdOw0KKwkJbHAgPSAmKCh1bmlvbiBkZXNjcmlwdG9yICopKHBs ZHQtPmxkdF9iYXNlKSlbdWFwLT5zdGFydF07DQogCX0gZWxzZSB7DQogCQlu bGR0ID0gc2l6ZW9mKGxkdCkvc2l6ZW9mKGxkdFswXSk7DQogCQludW0gPSBt aW4odWFwLT5udW0sIG5sZHQpOw0KQEAgLTQwNiw4ICs0MDcsOSBAQA0KIHsN CiAJaW50IGVycm9yID0gMCwgaSwgbjsNCiAJaW50IGxhcmdlc3RfbGQ7DQor CXN0cnVjdCBtZHByb2MgKm1kcCA9ICZ0ZC0+dGRfcHJvYy0+cF9tZDsNCiAJ c3RydWN0IHBjYiAqcGNiID0gdGQtPnRkX3BjYjsNCi0Jc3RydWN0IHBjYl9s ZHQgKnBjYl9sZHQgPSBwY2ItPnBjYl9sZHQ7DQorCXN0cnVjdCBwcm9jX2xk dCAqcGxkdCA9IG1kcC0+bWRfbGR0Ow0KIAlzdHJ1Y3QgaTM4Nl9sZHRfYXJn cyB1YSwgKnVhcCA9ICZ1YTsNCiAJY2FkZHJfdCBvbGRfbGR0X2Jhc2U7DQog CWludCBvbGRfbGR0X2xlbjsNCkBAIC00MzIsMTYgKzQzNCwxNiBAQA0KIAkJ cmV0dXJuKEVJTlZBTCk7DQogDQogCS8qIGFsbG9jYXRlIHVzZXIgbGR0ICov DQotCWlmICghcGNiX2xkdCB8fCBsYXJnZXN0X2xkID49IHBjYl9sZHQtPmxk dF9sZW4pIHsNCi0JCXN0cnVjdCBwY2JfbGR0ICpuZXdfbGR0ID0gdXNlcl9s ZHRfYWxsb2MocGNiLCBsYXJnZXN0X2xkKTsNCisJaWYgKCFwbGR0IHx8IGxh cmdlc3RfbGQgPj0gcGxkdC0+bGR0X2xlbikgew0KKwkJc3RydWN0IHByb2Nf bGR0ICpuZXdfbGR0ID0gdXNlcl9sZHRfYWxsb2MobWRwLCBsYXJnZXN0X2xk KTsNCiAJCWlmIChuZXdfbGR0ID09IE5VTEwpDQogCQkJcmV0dXJuIEVOT01F TTsNCi0JCWlmIChwY2JfbGR0KSB7DQotCQkJb2xkX2xkdF9iYXNlID0gcGNi X2xkdC0+bGR0X2Jhc2U7DQotCQkJb2xkX2xkdF9sZW4gPSBwY2JfbGR0LT5s ZHRfbGVuOw0KLQkJCXBjYl9sZHQtPmxkdF9zZCA9IG5ld19sZHQtPmxkdF9z ZDsNCi0JCQlwY2JfbGR0LT5sZHRfYmFzZSA9IG5ld19sZHQtPmxkdF9iYXNl Ow0KLQkJCXBjYl9sZHQtPmxkdF9sZW4gPSBuZXdfbGR0LT5sZHRfbGVuOw0K KwkJaWYgKHBsZHQpIHsNCisJCQlvbGRfbGR0X2Jhc2UgPSBwbGR0LT5sZHRf YmFzZTsNCisJCQlvbGRfbGR0X2xlbiA9IHBsZHQtPmxkdF9sZW47DQorCQkJ cGxkdC0+bGR0X3NkID0gbmV3X2xkdC0+bGR0X3NkOw0KKwkJCXBsZHQtPmxk dF9iYXNlID0gbmV3X2xkdC0+bGR0X2Jhc2U7DQorCQkJcGxkdC0+bGR0X2xl biA9IG5ld19sZHQtPmxkdF9sZW47DQogCQkJbXR4X3VubG9ja19zcGluKCZz Y2hlZF9sb2NrKTsNCiAJCQlrbWVtX2ZyZWUoa2VybmVsX21hcCwgKHZtX29m ZnNldF90KW9sZF9sZHRfYmFzZSwNCiAJCQkJb2xkX2xkdF9sZW4gKiBzaXpl b2YodW5pb24gZGVzY3JpcHRvcikpOw0KQEAgLTQ1MCwxNiArNDUyLDE3IEBA DQogCQkJbXR4X2xvY2tfc3Bpbigmc2NoZWRfbG9jayk7DQogI2VuZGlmDQog CQl9IGVsc2Ugew0KLQkJCXBjYi0+cGNiX2xkdCA9IHBjYl9sZHQgPSBuZXdf bGR0Ow0KKwkJCW1kcC0+bWRfbGR0ID0gcGxkdCA9IG5ld19sZHQ7DQogI2lm ZGVmIFNNUA0KIAkJCW10eF91bmxvY2tfc3Bpbigmc2NoZWRfbG9jayk7DQog I2VuZGlmDQogCQl9DQogI2lmZGVmIFNNUA0KIAkJLyogc2lnbmFsIG90aGVy IGNwdXMgdG8gcmVsb2FkIGxkdCAqLw0KLQkJc21wX3JlbmRlenZvdXMoTlVM TCwgKHZvaWQgKCopKHZvaWQgKikpc2V0X3VzZXJfbGR0X3J2LCBOVUxMLCBw Y2IpOw0KKwkJc21wX3JlbmRlenZvdXMoTlVMTCwgKHZvaWQgKCopKHZvaWQg Kikpc2V0X3VzZXJfbGR0X3J2LCANCisJCSAgICBOVUxMLCB0ZCk7DQogI2Vs c2UNCi0JCXNldF91c2VyX2xkdChwY2IpOw0KKwkJc2V0X3VzZXJfbGR0KG1k cCk7DQogCQltdHhfdW5sb2NrX3NwaW4oJnNjaGVkX2xvY2spOw0KICNlbmRp Zg0KIAl9DQpAQCAtNTMzLDcgKzUzNiw3IEBADQogCS8qIEZpbGwgaW4gcmFu Z2UgKi8NCiAJc2F2ZWNyaXQgPSBjcml0aWNhbF9lbnRlcigpOw0KIAllcnJv ciA9IGNvcHlpbih1YXAtPmRlc2NzLCANCi0JICAgICYoKHVuaW9uIGRlc2Ny aXB0b3IgKikocGNiX2xkdC0+bGR0X2Jhc2UpKVt1YXAtPnN0YXJ0XSwNCisJ ICAgICYoKHVuaW9uIGRlc2NyaXB0b3IgKikocGxkdC0+bGR0X2Jhc2UpKVt1 YXAtPnN0YXJ0XSwNCiAJICAgIHVhcC0+bnVtICogc2l6ZW9mKHVuaW9uIGRl c2NyaXB0b3IpKTsNCiAJaWYgKCFlcnJvcikNCiAJCXRkLT50ZF9yZXR2YWxb MF0gPSB1YXAtPnN0YXJ0Ow0KLS0tIGkzODYvdm1fbWFjaGRlcC5jLm9yaWcJ V2VkIFNlcCAxOSAwMjoxNjoyOCAyMDAxDQorKysgaTM4Ni92bV9tYWNoZGVw LmMJV2VkIFNlcCAxOSAwMzozOToxNCAyMDAxDQpAQCAtMTI1LDYgKzEyNSw3 IEBADQogCXJlZ2lzdGVyIHN0cnVjdCBwcm9jICpwMTsNCiAJc3RydWN0IHRo cmVhZCAqdGQyOw0KIAlzdHJ1Y3QgcGNiICpwY2IyOw0KKwlzdHJ1Y3QgbWRw cm9jICptZHAyOw0KICNpZmRlZiBERVZfTlBYDQogCWludCBzYXZlY3JpdDsN CiAjZW5kaWYNCkBAIC0xMzQsMTUgKzEzNSwxNSBAQA0KIAlpZiAoKGZsYWdz ICYgUkZQUk9DKSA9PSAwKSB7DQogCQlpZiAoKGZsYWdzICYgUkZNRU0pID09 IDApIHsNCiAJCQkvKiB1bnNoYXJlIHVzZXIgTERUICovDQotCQkJc3RydWN0 IHBjYiAqcGNiMSA9IHRkMS0+dGRfcGNiOw0KLQkJCXN0cnVjdCBwY2JfbGR0 ICpwY2JfbGR0ID0gcGNiMS0+cGNiX2xkdDsNCi0JCQlpZiAocGNiX2xkdCAm JiBwY2JfbGR0LT5sZHRfcmVmY250ID4gMSkgew0KLQkJCQlwY2JfbGR0ID0g dXNlcl9sZHRfYWxsb2MocGNiMSxwY2JfbGR0LT5sZHRfbGVuKTsNCi0JCQkJ aWYgKHBjYl9sZHQgPT0gTlVMTCkNCisJCQlzdHJ1Y3QgbWRwcm9jICptZHAx ID0gJnRkMS0+dGRfcHJvYy0+cF9tZDsNCisJCQlzdHJ1Y3QgcHJvY19sZHQg KnBsZHQgPSBtZHAxLT5tZF9sZHQ7DQorCQkJaWYgKHBsZHQgJiYgcGxkdC0+ bGR0X3JlZmNudCA+IDEpIHsNCisJCQkJcGxkdCA9IHVzZXJfbGR0X2FsbG9j KG1kcDEsIHBsZHQtPmxkdF9sZW4pOw0KKwkJCQlpZiAocGxkdCA9PSBOVUxM KQ0KIAkJCQkJcGFuaWMoImNvdWxkIG5vdCBjb3B5IExEVCIpOw0KLQkJCQlw Y2IxLT5wY2JfbGR0ID0gcGNiX2xkdDsNCi0JCQkJc2V0X3VzZXJfbGR0KHBj YjEpOw0KLQkJCQl1c2VyX2xkdF9mcmVlKHBjYjEpOw0KKwkJCQltZHAxLT5t ZF9sZHQgPSBwbGR0Ow0KKwkJCQlzZXRfdXNlcl9sZHQobWRwMSk7DQorCQkJ CXVzZXJfbGR0X2ZyZWUodGQxKTsNCiAJCQl9DQogCQl9DQogCQlyZXR1cm47 DQpAQCAtMTYyLDkgKzE2MywxMyBAQA0KIAlwY2IyID0gKHN0cnVjdCBwY2Ig KikodGQyLT50ZF9rc3RhY2sgKyBLU1RBQ0tfUEFHRVMgKiBQQUdFX1NJWkUp IC0gMTsNCiAJdGQyLT50ZF9wY2IgPSBwY2IyOw0KIA0KLQkvKiBDb3B5IHAx J3MgcGNiLiAqLw0KKwkvKiBDb3B5IHAxJ3MgcGNiICovDQogCWJjb3B5KHRk MS0+dGRfcGNiLCBwY2IyLCBzaXplb2YoKnBjYjIpKTsNCiANCisJLyogUG9p bnQgbWRwcm9jIGFuZCB0aGVuIGNvcHkgb3ZlciB0ZDEncyBjb250ZW50cyAq Lw0KKwltZHAyID0gJnRkMi0+dGRfcHJvYy0+cF9tZDsNCisJYmNvcHkoJnRk MS0+dGRfcHJvYy0+cF9tZCwgbWRwMiwgc2l6ZW9mKCptZHAyKSk7DQorDQog CS8qDQogCSAqIENyZWF0ZSBhIG5ldyBmcmVzaCBzdGFjayBmb3IgdGhlIG5l dyBwcm9jZXNzLg0KIAkgKiBDb3B5IHRoZSB0cmFwIGZyYW1lIGZvciB0aGUg cmV0dXJuIHRvIHVzZXIgbW9kZSBhcyBpZiBmcm9tIGENCkBAIC0xOTAsNyAr MTk1LDYgQEANCiAJcGNiMi0+cGNiX2VpcCA9IChpbnQpZm9ya190cmFtcG9s aW5lOw0KIAkvKi0NCiAJICogcGNiMi0+cGNiX2RyKjoJY2xvbmVkIGFib3Zl Lg0KLQkgKiBwY2IyLT5wY2JfbGR0OglkdXBsaWNhdGVkIGJlbG93LCBpZiBu ZWNlc3NhcnkuDQogCSAqIHBjYjItPnBjYl9zYXZlZnB1OgljbG9uZWQgYWJv dmUuDQogCSAqIHBjYjItPnBjYl9mbGFnczoJY2xvbmVkIGFib3ZlLg0KIAkg KiBwY2IyLT5wY2Jfb25mYXVsdDoJY2xvbmVkIGFib3ZlIChhbHdheXMgTlVM TCBoZXJlPykuDQpAQCAtMjA1LDEzICsyMDksMTMgQEANCiANCiAgICAgICAg IC8qIENvcHkgdGhlIExEVCwgaWYgbmVjZXNzYXJ5LiAqLw0KIAltdHhfbG9j a19zcGluKCZzY2hlZF9sb2NrKTsNCi0gICAgICAgIGlmIChwY2IyLT5wY2Jf bGR0ICE9IDApIHsNCisgICAgICAgIGlmIChtZHAyLT5tZF9sZHQgIT0gMCkg ew0KIAkJaWYgKGZsYWdzICYgUkZNRU0pIHsNCi0JCQlwY2IyLT5wY2JfbGR0 LT5sZHRfcmVmY250Kys7DQorCQkJbWRwMi0+bWRfbGR0LT5sZHRfcmVmY250 Kys7DQogCQl9IGVsc2Ugew0KLQkJCXBjYjItPnBjYl9sZHQgPSB1c2VyX2xk dF9hbGxvYyhwY2IyLA0KLQkJCQlwY2IyLT5wY2JfbGR0LT5sZHRfbGVuKTsN Ci0JCQlpZiAocGNiMi0+cGNiX2xkdCA9PSBOVUxMKQ0KKwkJCW1kcDItPm1k X2xkdCA9IHVzZXJfbGR0X2FsbG9jKG1kcDIsDQorCQkJICAgIG1kcDItPm1k X2xkdC0+bGR0X2xlbik7DQorCQkJaWYgKG1kcDItPm1kX2xkdCA9PSBOVUxM KQ0KIAkJCQlwYW5pYygiY291bGQgbm90IGNvcHkgTERUIik7DQogCQl9DQog ICAgICAgICB9DQpAQCAtMjUzLDcgKzI1Nyw3IEBADQogCXJlZ2lzdGVyIHN0 cnVjdCB0aHJlYWQgKnRkOw0KIHsNCiAJc3RydWN0IHBjYiAqcGNiID0gdGQt PnRkX3BjYjsgDQotDQorCXN0cnVjdCBtZHByb2MgKm1kcCA9ICZ0ZC0+dGRf cHJvYy0+cF9tZDsNCiAjaWZkZWYgREVWX05QWA0KIAlucHhleGl0KHRkKTsN CiAjZW5kaWYNCkBAIC0yNjYsOCArMjcwLDggQEANCiAJCSAgICBjdG9iKElP UEFHRVMgKyAxKSk7DQogCQlwY2ItPnBjYl9leHQgPSAwOw0KIAl9DQotCWlm IChwY2ItPnBjYl9sZHQpDQotCQl1c2VyX2xkdF9mcmVlKHBjYik7DQorCWlm IChtZHAtPm1kX2xkdCkNCisJCXVzZXJfbGR0X2ZyZWUodGQpOw0KICAgICAg ICAgaWYgKHBjYi0+cGNiX2ZsYWdzICYgUENCX0RCUkVHUykgew0KICAgICAg ICAgICAgICAgICAvKg0KICAgICAgICAgICAgICAgICAgKiBkaXNhYmxlIGFs bCBoYXJkd2FyZSBicmVha3BvaW50cw0K --0-739125287-1000976293=:7409-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 2: 0:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180]) by hub.freebsd.org (Postfix) with ESMTP id 228DD37B406; Thu, 20 Sep 2001 02:00:52 -0700 (PDT) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f8K90pM02065; Thu, 20 Sep 2001 02:00:51 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id B7D3F39F5; Thu, 20 Sep 2001 02:00:51 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: "Andrew R. Reiter" Cc: Julian Elischer , John Baldwin , hackers@FreeBSD.ORG Subject: Re: JKH Project: x86: pcb_ext In-Reply-To: Date: Thu, 20 Sep 2001 02:00:51 -0700 From: Peter Wemm Message-Id: <20010920090051.B7D3F39F5@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Andrew R. Reiter" wrote: > On Wed, 19 Sep 2001, Peter Wemm wrote: > : > :One comment: > : > :- cmpl $0, PCB_USERLDT(%edx) /* if there is one */ > :+ movl TD_PROC(%ecx), %eax /* load struct proc from CURTHREAD */ > :+ leal P_MD(%eax), %eax /* get mdproc from proc */ > :+ cmpl $0, MD_LDT(%eax) /* if there is one */ > : > : > :This can be written as: > : movl TD_PROC(%ecx), %eax > : cmpl $0, P_MD+MD_LDT(%eax) > : > :This is evaluated at assemble time. > > Yea, Kinda dumb on my part :-/ No, I just happened to miss the same shortcut recently, so I noticed it. :-) Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 4:20: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from vbook.express.ru (asplinux.ru [195.133.213.194]) by hub.freebsd.org (Postfix) with ESMTP id C42FA37B409; Thu, 20 Sep 2001 04:20:03 -0700 (PDT) Received: from vova by vbook.express.ru with local (Exim 3.31 #2) id 15k1tE-0000r2-00; Thu, 20 Sep 2001 15:21:08 +0400 To: FreeBSD-gnats-submit@freebsd.org Subject: uptime and w utilities lie about real uptime From: Vladimir B.Grebenschikov Reply-To: Vladimir B.Grebenschikov Cc: freebsd-hackers@freebsd.org X-send-pr-version: 3.113 X-GNATS-Notify: Message-Id: Date: Thu, 20 Sep 2001 15:21:08 +0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Submitter-Id: current-users >Originator: Vladimir B. Grebenschikov >Organization: TSB "Russian Express" >Confidential: no >Synopsis: uptime and w utilities lie about real uptime >Severity: non-critical >Priority: low >Category: bin >Class: sw-bug >Release: FreeBSD 5.0-CURRENT i386 >Environment: System: FreeBSD vbook.express.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Sep 19 20:26:25 MSD 2001 root@vbook.express.ru:/usr/src.local/sys/i386/compile/VBOOK i386 >Description: Just after very fast boot uptimealways shows more than 30 sec. looking to src/usr/bin/w/w.c: if (sysctl(mib, 2, &boottime, &size, NULL, 0) != -1 && boottime.tv_sec != 0) { uptime = now - boottime.tv_sec; uptime += 30; ====================== ^^^^^ days = uptime / 86400; uptime %= 86400; hrs = uptime / 3600; uptime %= 3600; mins = uptime / 60; secs = uptime % 60; (void)printf(" up"); why utility increases uptime on 30 seconds ?? Is any real reasons for it ? >How-To-Repeat: Boot and run uptime >Fix: --- src/usr.bin/w.c.orig Thu Sep 20 15:20:01 2001 +++ src/usr.bin/w.c Thu Sep 20 15:20:11 2001 @@ -450,7 +450,6 @@ if (sysctl(mib, 2, &boottime, &size, NULL, 0) != -1 && boottime.tv_sec != 0) { uptime = now - boottime.tv_sec; - uptime += 30; days = uptime / 86400; uptime %= 86400; hrs = uptime / 3600; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 4:44:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mx.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with SMTP id 3E9FE37B410 for ; Thu, 20 Sep 2001 04:44:25 -0700 (PDT) To: "Vladimir B.Grebenschikov" Cc: FreeBSD-gnats-submit@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Received: From MAIL.TVOL.NET (10.1.1.4[10.1.1.4 port:3933]) by mx.wgate.comMail essentials (server 2.429) with SMTP id: <6978@mx.wgate.com>transfer for ; Thu, 20 Sep 2001 7:43:09 AM -0400 ;transfer smtpmailfrom X-MESINK_Inbound: 0 X-MESINK_MailForType: SMTP X-MESINK_SenderType: SMTP X-MESINK_Sender: msinz@wgate.com X-MESINK_MailFor: freebsd-hackers@FreeBSD.ORG Received: from sinz.eng.tvol.net ([10.32.2.99]) by mail.tvol.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)id THV3CRM7; Thu, 20 Sep 2001 07:43:00 -0400 Received: from wgate.com (localhost [127.0.0.1])by sinz.eng.tvol.net (8.11.6/8.11.6) with ESMTP id f8KBi6s93355;Thu, 20 Sep 2001 07:44:06 -0400 (EDT)(envelope-from msinz@wgate.com) Date: Thu, 20 Sep 2001 07:44:06 -0400 From: Michael Sinz Organization: WorldGate Communications Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-STABLE i386) X-Accept-Language: en Subject: Re: uptime and w utilities lie about real uptime References: <400de87e0423b007d1@[192.168.1.4]> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit x-receiver: freebsd-hackers@FreeBSD.ORG x-sender: msinz@wgate.com MIME-Version: 1.0 Message-ID: <402390ae04246407d1@[192.168.1.4]> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Vladimir B.Grebenschikov" wrote: > > >Submitter-Id: current-users > >Originator: Vladimir B. Grebenschikov > >Organization: TSB "Russian Express" > >Confidential: no > >Synopsis: uptime and w utilities lie about real uptime > >Severity: non-critical > >Priority: low > >Category: bin > >Class: sw-bug > >Release: FreeBSD 5.0-CURRENT i386 > >Environment: > System: FreeBSD vbook.express.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Sep 19 20:26:25 MSD 2001 root@vbook.express.ru:/usr/src.local/sys/i386/compile/VBOOK i386 > > >Description: > > Just after very fast boot uptimealways shows more than 30 sec. > > looking to src/usr/bin/w/w.c: > > if (sysctl(mib, 2, &boottime, &size, NULL, 0) != -1 && > boottime.tv_sec != 0) { > uptime = now - boottime.tv_sec; > uptime += 30; > ====================== ^^^^^ > days = uptime / 86400; > uptime %= 86400; > hrs = uptime / 3600; > uptime %= 3600; > mins = uptime / 60; > secs = uptime % 60; > (void)printf(" up"); > > why utility increases uptime on 30 seconds ?? > Is any real reasons for it ? From my reading of this, it seems to want to round the uptime to the nearest minute -- afterall, w and uptime both only show the uptime in minutes (well, days, hours, and minutes) -- Michael Sinz ---- Worldgate Communications ---- msinz@wgate.com A master's secrets are only as good as the master's ability to explain them to others. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 4:51:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from vbook.express.ru (asplinux.ru [195.133.213.194]) by hub.freebsd.org (Postfix) with ESMTP id D21DF37B421; Thu, 20 Sep 2001 04:51:38 -0700 (PDT) Received: from vova by vbook.express.ru with local (Exim 3.31 #2) id 15k2Nl-0000tr-00; Thu, 20 Sep 2001 15:52:41 +0400 From: "Vladimir B. Grebenschikov" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15273.55432.957586.417711@vbook.express.ru> Date: Thu, 20 Sep 2001 15:52:40 +0400 To: Michael Sinz Cc: FreeBSD-gnats-submit@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: uptime and w utilities lie about real uptime In-Reply-To: <402390ae04246407d1@[192.168.1.4]> References: <400de87e0423b007d1@[192.168.1.4]> <402390ae04246407d1@[192.168.1.4]> X-Mailer: VM 6.95 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Michael Sinz writes: > > if (sysctl(mib, 2, &boottime, &size, NULL, 0) != -1 && > > boottime.tv_sec != 0) { > > uptime = now - boottime.tv_sec; > > uptime += 30; > > ====================== ^^^^^ > > days = uptime / 86400; > > uptime %= 86400; > > hrs = uptime / 3600; > > uptime %= 3600; > > mins = uptime / 60; > > secs = uptime % 60; > > (void)printf(" up"); > > > > why utility increases uptime on 30 seconds ?? > > Is any real reasons for it ? > > >From my reading of this, it seems to want to round the uptime to > the nearest minute -- afterall, w and uptime both only show the uptime > in minutes (well, days, hours, and minutes) not exactly right: ... DUMMYNET initialized (010124) Waiting 2 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s2a da0 at ahc0 bus 0 target 12 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) Enter full pathname of shell or RETURN for /bin/sh: # mount -a # uptime 3:12PM up 42 secs, 3 users, load averages: 0.21, 0.05, 0.02 # 42sec instead of more realistic 12sec looking into w.c more: if (days > 0) (void)printf(" %d day%s,", days, days > 1 ? "s" : ""); if (hrs > 0 && mins > 0) (void)printf(" %2d:%02d,", hrs, mins); else if (hrs > 0) (void)printf(" %d hr%s,", hrs, hrs > 1 ? "s" : ""); else if (mins > 0) (void)printf(" %d min%s,", mins, mins > 1 ? "s" : ""); else (void)printf(" %d sec%s,", secs, secs > 1 ? "s" : ""); } -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, vova@express.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 4:57:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from newsguy.com (smtp.newsguy.com [209.155.56.71]) by hub.freebsd.org (Postfix) with ESMTP id 9AC5237B407 for ; Thu, 20 Sep 2001 04:57:35 -0700 (PDT) Received: from newsguy.com (ppp232-bsace7002.telebrasilia.net.br [200.181.81.232]) by newsguy.com (8.9.1a/8.9.1) with ESMTP id EAA19864; Thu, 20 Sep 2001 04:57:20 -0700 (PDT) Message-ID: <3BA9DAA1.BEC5D482@newsguy.com> Date: Thu, 20 Sep 2001 09:01:37 -0300 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en,pt-BR,pt,en-GB,en-US,ja MIME-Version: 1.0 To: Jean-Christophe Varaillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Boot proccess References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jean-Christophe Varaillon wrote: > > Hi, > > Newbie, I need to understand the differents steps of a booting process > from the 2 floppies (kern.flp & mfsroot.flp). > > How it comes and the FreeBSD machine can understand the fact that it has > to find kern.flp & mfsroot.flp from the floppy, uncompress them, load them > in the RAM and make them running ? > > In short, which program gives enough knowledge to the microprocessor (?) > and allow him to use kern.flp & mfsroot.flp in order to boot and make the > operating system running. apropos boot -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net wow regex humor... I'm a geek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 5:31:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id C748637B418; Thu, 20 Sep 2001 05:31:50 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 20 Sep 2001 13:31:49 +0100 (BST) Date: Thu, 20 Sep 2001 13:31:49 +0100 From: David Malone To: "Vladimir B.Grebenschikov" Cc: FreeBSD-gnats-submit@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: bin/30680: uptime and w utilities lie about real uptime Message-ID: <20010920133149.A96422@walton.maths.tcd.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from vova@express.ru on Thu, Sep 20, 2001 at 03:21:08PM +0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Sep 20, 2001 at 03:21:08PM +0400, Vladimir B.Grebenschikov wrote: > why utility increases uptime on 30 seconds ?? > Is any real reasons for it ? It adds 30 because it wants to round the number of minutes to the nearest minute, instead of rounding down. Unfortunately this isn't a sensible thing to do if you are also going to display the number of seconds. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 6:28:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [129.83.20.90]) by hub.freebsd.org (Postfix) with ESMTP id B15BD37B40F for ; Thu, 20 Sep 2001 06:28:18 -0700 (PDT) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id f8KDSFE01307 for ; Thu, 20 Sep 2001 09:28:17 -0400 (EDT) Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31]) by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id f8KDSEf17818 for ; Thu, 20 Sep 2001 09:28:14 -0400 (EDT) Received: from dhcp-105-164.mitre.org (128.29.105.164) by mailhub1.mitre.org with SMTP id 7673493; Thu, 20 Sep 2001 09:28:03 -0400 Message-ID: <3BA9EEED.B7F0A194@mitre.org> Date: Thu, 20 Sep 2001 09:28:13 -0400 From: Jason Andresen Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: No tools on 4.4-RELEASE ISO? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is the tools directory supposed to be missing on the 4.4 CDs? I downloaded the full disk 1 ISO yesterday and burned it only to discover that fdimage.exe was nowhere to be found on the CD. This is not a good thing when you have to create boot floppies because your BIOS refuses to acknowledge the existance of your CD-ROM. Strangely the documentation on the CD still references fdimage and the floppies are still on there, I guess you are supposed to have a net connection and get anything you need from the FTP site? -- \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org |\/ | | | / _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 7:29: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by hub.freebsd.org (Postfix) with ESMTP id E388837B419; Thu, 20 Sep 2001 07:29:00 -0700 (PDT) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.11.1/8.11.1) id f8KESur51565; Thu, 20 Sep 2001 10:28:56 -0400 (EDT) (envelope-from bicknell) Date: Thu, 20 Sep 2001 10:28:56 -0400 From: Leo Bicknell To: "Vladimir B.Grebenschikov" Cc: FreeBSD-gnats-submit@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: uptime and w utilities lie about real uptime Message-ID: <20010920102856.B51134@ussenterprise.ufp.org> Mail-Followup-To: Leo Bicknell , "Vladimir B.Grebenschikov" , FreeBSD-gnats-submit@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from vova@express.ru on Thu, Sep 20, 2001 at 03:21:08PM +0400 Organization: United Federation of Planets Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It's rounding to minutes when it shouldn't, uptime only displays seconds for very short uptimes, and then always rounds to minutes. Your patch causes it to truncate, which is probably the right thing to do, the alternative would be: if (uptime > 60) uptime += 30; That way it won't start rounding until a full minute has passed, allowing the first 60 seconds to be displayed properly. This has less of a chance of breaking things depending on the rounding, but I would hope ther are none of those. -- Leo Bicknell - bicknell@ufp.org Systems Engineer - Internetworking Engineer - CCIE 3440 Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 10: 7:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f294.law10.hotmail.com [64.4.14.169]) by hub.freebsd.org (Postfix) with ESMTP id C1EC837B40D for ; Thu, 20 Sep 2001 10:07:23 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 20 Sep 2001 10:07:23 -0700 Received: from 213.131.162.34 by lw10fd.law10.hotmail.msn.com with HTTP; Thu, 20 Sep 2001 17:07:23 GMT X-Originating-IP: [213.131.162.34] From: "damie odessa" To: freebsd-hackers@FreeBSD.org Date: Thu, 20 Sep 2001 17:07:23 +0000 Mime-Version: 1.0 Content-Type: text/html Message-ID: X-OriginalArrivalTime: 20 Sep 2001 17:07:23.0577 (UTC) FILETIME=[B747A290:01C141F6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG
Hello,
I am installing freebsd 4.2 and at the point of configuring the DHCP, it crashes with a Signal 11. Assist please.
Or is there a site I could visit for troubleshooting
 
Thanks
 
Desperately yours
 
damie  

Get your FREE download of MSN Explorer at http://explorer.msn.com
To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 10:11:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gekko.ms-agentur.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id 45D9F37B405 for ; Thu, 20 Sep 2001 10:11:47 -0700 (PDT) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.ms-agentur.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id TAA29298; Thu, 20 Sep 2001 19:21:17 +0200 Message-ID: <3BAA234E.8050808@i-clue.de> Date: Thu, 20 Sep 2001 19:11:42 +0200 From: Christoph Sold User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:0.9.4+) Gecko/20010916 X-Accept-Language: de, en MIME-Version: 1.0 To: damie odessa Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [Please ask questions at the FreeBSD-Questions mailing list. Hackers is reserved for discussing development.] damie odessa wrote: > Hello, > > I am installing freebsd 4.2 and at the point of configuring the DHCP, > it crashes with a Signal 11. Assist please. > Did you install from ports? Had you lloked at the core? > Or is there a site I could visit for troubleshooting > As stated above, try at FreeBSD-Questions. HTH -Christoph Sold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 10:38:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id CEA2C37B40B for ; Thu, 20 Sep 2001 10:38:22 -0700 (PDT) Received: (qmail 50557 invoked from network); 20 Sep 2001 17:38:22 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 20 Sep 2001 17:38:22 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3BA959E7.43CD9CD6@elischer.org> Date: Thu, 20 Sep 2001 10:38:08 -0700 (PDT) From: John Baldwin To: Julian Elischer Subject: Re: JKH Project: x86: pcb_ext Cc: hackers@FreeBSD.org, Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 20-Sep-01 Julian Elischer wrote: > Peter Wemm wrote: >> >> John Baldwin wrote: >> > >> > On 19-Sep-01 Peter Wemm wrote: >> > > The more I think about it, the right place may be the kse, since that >> > > outlives >> > > the threads and is per-cpu unlike the process. >> > > >> > > Or, we just say "no pcb extensions for kse processes". >> > >> > Each thread would need its own TSS, and to preserve existing semantics, we >> > would have to change the TSS of all threads for each TSS related syscall. >> > In >> > light of that, I vote in favor of "no TSS's for kse processes" since TSS's >> > ar >> e >> > used for very few things anyways. LDT's are another matter and can be >> > moved >> > w/o a problem. >> >> The main two things we seem to use the per-process TSS stuff for are: >> Fine grained IO port permission bitmap >> VM86 mode >> I think we can well do without the complexity of mixing KSE with those two. > > > I could IMAGINE a vm86 version that ran the control/exception > thread on another processor as a different thread. (though who would write > it?) > I could also imagine a muli-threaded program doing IO to a device as a > userland > driver. > > but of course hey'd need to be writen explicitly for it.. > >> >> We still would need to sync LDT reloads.. > > that's more of a worry for me. > Do we still have separate a LDT for threads? What you will have to do for the LDT reload (an LDT is per-process, not per-thread) is perform a context switch (or possibly just a LDT reload) on all processors running threads from thsi process. We already do this in a way when we change an LDT that is shared, IIRC. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 11: 9:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 13D1C37B40A; Thu, 20 Sep 2001 11:09:25 -0700 (PDT) Subject: Re: Need testers, Broadcom BCM570x gigE driver To: freebsd-hackers@freebsd.org Date: Thu, 20 Sep 2001 11:09:25 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20010920180925.13D1C37B40A@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ack. Ok, I realized that I forgot to upload a couple of files to http://www.freebsd.org/~wpaul/Broadcom/4.x yesterday. The brgphy driver needs an updated version of the miidevs file, and the ones generated from it. I have placed these on the web site along with all the other stuff. In addition to the steps I mentioned yesterday for installing the driver, you'll need to copy the updated miidevs files to /sys/dev/mii. Also: if you're going to perform tests, please tell me everything about how you do them. Tell me what hardware you're using. Tell me exactly which card you have. Tell me what software you're using to perform tests. If you observe a problem, don't evaluate it for me: just tell me what you see and let me work it out. I don't want to hear people say "it drops packets." Tell me how you observed the packets being dropped. I'm going to cook up a -current version of the code presently. Watch this space. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "I like zees guys. Zey are fonny guys. Just keel one of zem." -- The 3 Amigos ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 11:38: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id D24AF37B40D; Thu, 20 Sep 2001 11:37:58 -0700 (PDT) Subject: Re: Need testers, Broadcom BCM570x gigE driver To: freebsd-hackers@freebsd.org Date: Thu, 20 Sep 2001 11:37:58 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20010920183758.D24AF37B40D@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG There is now a -current version of the bge driver at the following URL: http://www.freebsd.org/~wpaul/Broadcom/5.x The brgphy driver in -current has already been updated so support the BCM5401 and BCM5411 PHYs, so no other changes are necessary. Share and enjoy. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 11:42:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-35.dsl.lsan03.pacbell.net [63.207.60.35]) by hub.freebsd.org (Postfix) with ESMTP id 9777237B412 for ; Thu, 20 Sep 2001 11:42:48 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CB6D966DDA; Thu, 20 Sep 2001 11:42:47 -0700 (PDT) Date: Thu, 20 Sep 2001 11:42:47 -0700 From: Kris Kennaway To: Hassan Halta Cc: freebsd-hackers@freebsd.org Subject: Re: Compiling top in SMP Message-ID: <20010920114247.A75088@xor.obsecurity.org> References: <20010918195233.I27560-100000@quark.cs.earlham.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010918195233.I27560-100000@quark.cs.earlham.edu>; from hassan@cs.earlham.edu on Tue, Sep 18, 2001 at 08:00:35PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 18, 2001 at 08:00:35PM -0500, Hassan Halta wrote: > Hello, >=20 > I hope some person will be able to help in this problem. I have a > SMP enviorment with 2 CPUs, and things are working just fine, and the > kernel recognizes everything. But The only problem that's top is > misbehaving. However, it recognizes that there are 2 CPUs in the systems, > but in the top stats it shows that every process is 0.00% of the CPU. > Which's not true at all, we ran some testing to hammer the CPU and > processes that should take 99.9% of the CPU, but it's always stuck on > 0.00%. I tried to compile top which exists in /usr/src/contrib/top/ and it > turns out that it's missing some modules of lists so that it can go ahead > and compile, so I got that list, and got the codes for that, and tried to > compile, but top just doesn't compile. I am not sure if I am in the right > track by compiling top on the system. I was also wondering if there's > another way to solve that problem. You don't compile things in /usr/src/contrib in FreeBSD, that's just where parts of the vendor code live. Top is rebuilt from usr.bin/top. Make sure your userland is in sync with your kernel; if you update your kernel sources and rebuild your kernel, you must rebuild world as well, otherwise some things (like top) are likely to stop working. Kris --RnlQjJ0d97Da+TV1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7qjinWry0BWjoQKURAhXNAJoDlhKHQ85iTPNV2Cm67nkHw90UtACeOFe0 XUQ2XtgCJE4HaBNOYaXj0Js= =kI5k -----END PGP SIGNATURE----- --RnlQjJ0d97Da+TV1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 12:49:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailgw3a.lmco.com (mailgw3a.lmco.com [192.35.35.24]) by hub.freebsd.org (Postfix) with ESMTP id 3CF2137B413 for ; Thu, 20 Sep 2001 12:49:13 -0700 (PDT) Received: from emss01g01.ems.lmco.com ([129.197.181.54]) by mailgw3a.lmco.com (8.8.8/8.8.8) with ESMTP id PAA09183 for ; Thu, 20 Sep 2001 15:49:03 -0400 (EDT) Received: from CONVERSION-DAEMON by lmco.com (PMDF V5.2-32 #38886) id <0GJZ009018BF20@lmco.com> for freebsd-hackers@freebsd.org; Thu, 20 Sep 2001 12:48:38 -0700 (PDT) Received: from cui1.lmms.lmco.com ([129.197.1.64]) by lmco.com (PMDF V5.2-32 #38886) with ESMTP id <0GJZ000KZ8BKQX@lmco.com> for freebsd-hackers@freebsd.org; Thu, 20 Sep 2001 12:47:44 -0700 (PDT) Received: from lmco.com (CONNECTICUT1.lmms.lmco.com [129.197.23.84]) by cui1.lmms.lmco.com (8.11.0/8.9.2) with ESMTP id f8KJlh627834 for ; Thu, 20 Sep 2001 12:47:43 -0700 (PDT) Date: Thu, 20 Sep 2001 12:47:44 -0700 From: rick norman Subject: ipfw and dummynet To: freebsd-hackers@freebsd.org Message-id: <3BAA47DF.5924E6B6@lmco.com> MIME-version: 1.0 X-Mailer: Mozilla 4.77 [en] (WinNT; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I tried "questions" for this but no answer. I am attempting to use ipfw and dummynet to instrument some network traffic tests. I am running freebsd 4.3 release and have built the kernel with ipfirewall, dummynet, and default to enabled. For a simple test, I added a pipe "ipfw add pipe 1 icmp from any to any". When I ping this machine, I can do "ipfw pipe 1 show" and watch the counters increment, but the machine doing the pinging does not see a response to the ping. That's my first question. Next, when I try to delete the pipe, "ipfw pipe 1 delete", it won't delete. The only way I can get rid of it is to do a flush. That's the second question. Third question, if I type "ipfw pipe 1 config bw 10Bytes/s", I would expect the bw to be limited and the counters to reflect this limit. The counters indicate no change in the 64 byte/s generated by my windows client. I have read the man pages for ipfw, dummynet, and ipfirewall. If these are obvious questions, I would appreciate a pointer to a good reference. Thanks -- Logically speaking, logic is not the answer. Rick Norman rick.norman@lmco.com 408 742 1619 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 14:56:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp010.mail.yahoo.com (smtp010.mail.yahoo.com [216.136.173.30]) by hub.freebsd.org (Postfix) with SMTP id C5ECB37B405 for ; Thu, 20 Sep 2001 14:56:38 -0700 (PDT) Received: from mkc-65-31-219-45.kc.rr.com (HELO yahoo.com) (65.31.219.45) by smtp.mail.vip.sc5.yahoo.com with SMTP; 20 Sep 2001 21:56:25 -0000 X-Apparently-From: Message-ID: <3BAA6608.1020906@yahoo.com> Date: Thu, 20 Sep 2001 16:56:24 -0500 From: Jim Bryant Reply-To: kc5vdj@yahoo.com User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: damie odessa Cc: freebsd-hackers@FreeBSD.org Subject: Re: References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You may want to install FreeBSD-4.4, it was released yesterday, so this means that you are attempting to install something two versions behind. There are security issues with 4.2... damie odessa wrote: > Hello, > > I am installing freebsd 4.2 and at the point of configuring the DHCP, it > crashes with a Signal 11. Assist please. > > Or is there a site I could visit for troubleshooting > > > > Thanks > > > > Desperately yours > > > > damie jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! ----------------------------------------------------- POWER TO THE PEOPLE! ----------------------------------------------------- "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 15:33:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from q1-rme.xtra.co.nz (q1-rme.xtra.co.nz [203.96.92.29]) by hub.freebsd.org (Postfix) with ESMTP id 3771637B417 for ; Thu, 20 Sep 2001 15:33:25 -0700 (PDT) Received: from development.wgtn.csg.co.nz ([210.86.1.68]) by q1-rme.xtra.co.nz with SMTP id <20010920223323.WKQ147022.q1-rme.xtra.co.nz@development.wgtn.csg.co.nz> for ; Fri, 21 Sep 2001 10:33:23 +1200 Content-Type: text/plain; charset="iso-8859-1" From: David Preece Reply-To: davep@afterswish.com To: hackers@freebsd.org Subject: sendto not sending what I asked... Date: Fri, 21 Sep 2001 10:33:38 +1200 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01092110333803.36513@development.wgtn.csg.co.nz> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I'm trying to write a raw (SYN) packet with sendto. I've opened the socket with socket(AF_INET, SOCK_RAW, IPPROTO_RAW), the result is checked and it is unbound. A buffer and a sockaddr_in are formed then sent down the socket with sendto(sck,pBuffer,40,0,(struct sockaddr *)&sin,sizeof(sin)) and the packet captured using ethereal. While the packet does send, with the correct source and destination addresses, the buffer I pass is appended as data on the end of an IP packet with unknown protocol, rather than replacing the IP and TCP headers (i.e. appending the ethernet header) as I had hoped. Has anyone seen this before? Is there a socket option I have missed? I've R'dTFM till I'm blue in the face, and all the examples I can find seem to be for Linux on big endian machines :( Cheers, Dave PS. No, not a packet kiddie. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 15:48: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 645A137B410 for ; Thu, 20 Sep 2001 15:48:04 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 45CED81D05; Thu, 20 Sep 2001 17:47:59 -0500 (CDT) Date: Thu, 20 Sep 2001 17:47:59 -0500 From: Alfred Perlstein To: David Preece Cc: hackers@freebsd.org Subject: Re: sendto not sending what I asked... Message-ID: <20010920174759.B61456@elvis.mu.org> References: <01092110333803.36513@development.wgtn.csg.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01092110333803.36513@development.wgtn.csg.co.nz>; from davep@afterswish.com on Fri, Sep 21, 2001 at 10:33:38AM +1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * David Preece [010920 17:35] wrote: > Hi, > > I'm trying to write a raw (SYN) packet with sendto. I've opened the socket > with socket(AF_INET, SOCK_RAW, IPPROTO_RAW), the result is checked and it is > unbound. A buffer and a sockaddr_in are formed then sent down the socket with > sendto(sck,pBuffer,40,0,(struct sockaddr *)&sin,sizeof(sin)) and the packet > captured using ethereal. While the packet does send, with the correct source > and destination addresses, the buffer I pass is appended as data on the end > of an IP packet with unknown protocol, rather than replacing the IP and TCP > headers (i.e. appending the ethernet header) as I had hoped. > > Has anyone seen this before? Is there a socket option I have missed? I've > R'dTFM till I'm blue in the face, and all the examples I can find seem to be > for Linux on big endian machines :( It would help if you'd provided what you think you're sending and what the other end is actually seeing. Without that I can't help much except to suggest that you make sure you're using htons/htonl in the right spot and on the right size types. I used htons instead of htonl on a 32 bit datum and it took me a good half a day to figure out what i had done wrong. > PS. No, not a packet kiddie. none of us are... really. >;) -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 16:23: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta3-rme.xtra.co.nz (mta3-rme.xtra.co.nz [203.96.92.13]) by hub.freebsd.org (Postfix) with ESMTP id 0694337B40E for ; Thu, 20 Sep 2001 16:23:03 -0700 (PDT) Received: from development.wgtn.csg.co.nz ([210.86.1.68]) by mta3-rme.xtra.co.nz with SMTP id <20010920232301.BJGZ3395984.mta3-rme.xtra.co.nz@development.wgtn.csg.co.nz>; Fri, 21 Sep 2001 11:23:01 +1200 Content-Type: text/plain; charset="iso-8859-1" From: David Preece Reply-To: davep@afterswish.com To: Alfred Perlstein Subject: Re: sendto not sending what I asked... Date: Fri, 21 Sep 2001 11:23:16 +1200 X-Mailer: KMail [version 1.2] References: <01092110333803.36513@development.wgtn.csg.co.nz> <20010920174759.B61456@elvis.mu.org> In-Reply-To: <20010920174759.B61456@elvis.mu.org> Cc: hackers@freebsd.org MIME-Version: 1.0 Message-Id: <01092111231604.36513@development.wgtn.csg.co.nz> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 21 Sep 2001 10:47, you wrote: > > the > > buffer I pass is appended as data on the end of an IP packet with unknown > > protocol, rather than replacing the IP and TCP headers (i.e. appending > > the ethernet header) as I had hoped. > It would help if you'd provided what you think you're sending and > what the other end is actually seeing. Sure, The contents of the buffer are: struct packet { ip ipbit; tcphdr tcpbit; }; //fill in some basics of the packet we are about to send packet pkt; pkt.ipbit.ip_v=4; pkt.ipbit.ip_hl=5; pkt.ipbit.ip_tos=0; pkt.ipbit.ip_len=htons(40); pkt.ipbit.ip_off=0; pkt.ipbit.ip_ttl=64; pkt.ipbit.ip_p=6; pkt.ipbit.ip_src.s_addr=/*inet_addr(argv[4])*/inet_addr("10.0.0.102"); pkt.ipbit.ip_dst.s_addr=/*inet_addr(argv[2])*/inet_addr("10.0.0.103"); pkt.tcpbit.th_dport=/*htons(atoi(argv[3]))*/htons(80); pkt.tcpbit.th_ack=0; pkt.tcpbit.th_x2=0; pkt.tcpbit.th_off=5; //20 bytes, no options pkt.tcpbit.th_flags=TH_SYN; pkt.tcpbit.th_win=htons(65535); //advertise a big window pkt.tcpbit.th_urp=0; [snip, fast forward to later in the code] //fill in random bits of packet pkt.ipbit.ip_id=/*rand()%65536*/htons(0x1234); pkt.tcpbit.th_sport=/*htons(1024+rand()%64511)*/htons(0x4321); pkt.tcpbit.th_seq=/*rand()*/htonl(0x12345678); //find checksums pkt.ipbit.ip_sum=0; pkt.tcpbit.th_sum=0; pkt.ipbit.ip_sum=in_cksum((unsigned short*)(void*)&pkt,20); pkt.tcpbit.th_sum=tcpsum(&pkt.ipbit); where both in_cksum and tcpsump have been used before and appear to work :) the sin structure is filled out: sockaddr_in sin; bzero(&sin,sizeof(struct sockaddr_in)); sin.sin_family=AF_INET; sin.sin_addr.s_addr=pkt.ipbit.ip_dst.s_addr; sin.sin_port=pkt.tcpbit.th_dport; finally I send with this (where pBuffer is just put in to give the debugger something to look at). void* pBuffer=&pkt; sendto(sck,pBuffer,40,0,(struct sockaddr *)&sin,sizeof(sin)); OK, so at this point the contents of the buffer are: 0xbfbff9dc: 0x45 0x00 0x00 0x28 0x12 0x34 0x00 0x00 0xbfbff9e4: 0x40 0x06 0x53 0xd0 0x0a 0x00 0x00 0x66 0xbfbff9ec: 0x0a 0x00 0x00 0x67 0x43 0x21 0x00 0x50 0xbfbff9f4: 0x12 0x34 0x56 0x78 0x00 0x00 0x00 0x00 0xbfbff9fc: 0x50 0x02 0xff 0xff 0xee 0xf8 0x00 0x00 And the packet that actually gets sent: 0000 00 d0 b7 1b b2 6c 00 80 ad 72 b6 cc 08 00 45 00 0010 00 3c 1f dd 00 00 ff ff 86 19 0a 00 00 66 0a 00 0020 00 67 45 00 00 28 12 34 00 00 40 06 53 d0 0a 00 0030 00 66 0a 00 00 67 43 21 00 50 12 34 56 78 00 00 0040 00 00 50 02 ff ff ee f8 00 00 So here we have the two hardware addresses (ending 0xb6 0xcc, top line), marking as IP protocol (0x08 0x00), then the IP packet written by the OS (0x45 0x00 top line, to 0x00 0x67 on the third line) followed by the buffer I provided for a total length of 60 bytes. Interestingly the IP packet written by the OS has a protocol of 0xff=unknown (the 0x17th byte). >Without that I can't help > much except to suggest that you make sure you're using htons/htonl > in the right spot and on the right size types. Yeah, been bitten by this before, but in my experience providing a packet with broken checksums results in it either not being sent, or being ignored by the recipient. This behaviour is entirely new and suggests there's something I don't understand about the interface onto the OS since if I was wanting to send a packet of data over IP without declaring which protocol it was for, this would be a pretty good way of doing it :) Oh, experience yes, I have worked with divert sockets before, but not raw - hence the confusion. Cheers, Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 17: 5: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta6-rme.xtra.co.nz (mta6-rme.xtra.co.nz [203.96.92.19]) by hub.freebsd.org (Postfix) with ESMTP id 973A937B409 for ; Thu, 20 Sep 2001 17:05:06 -0700 (PDT) Received: from development.wgtn.csg.co.nz ([210.86.1.68]) by mta6-rme.xtra.co.nz with SMTP id <20010921000505.BVXP2560251.mta6-rme.xtra.co.nz@development.wgtn.csg.co.nz>; Fri, 21 Sep 2001 12:05:05 +1200 Content-Type: text/plain; charset="iso-8859-1" From: David Preece Reply-To: davep@afterswish.com To: davidc@acns.ab.ca, sridharv@ufl.edu, bright@mu.org Subject: Raw sockets: Stevens shall provide. Date: Fri, 21 Sep 2001 12:05:20 +1200 X-Mailer: KMail [version 1.2] Cc: hackers@freebsd.org MIME-Version: 1.0 Message-Id: <01092112052007.36513@development.wgtn.csg.co.nz> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks for your help, as suggested the combination of IP_HDRINCL and reading Stevens seems to have me back on the right path. Part of the confusion was the Linux implementation of IP_HDRINCL appears to need the hardware addresses writing as well, consequently there are lots of examples of this being done in order to forge arp replies etc - not what I needed. Or rather, it was actually. Anyway, the code is now refusing to send packets entirely, which is actually good because it implies a checksum is broken somewhere and that's a bug, not a misunderstanding about the API. Thanks again, Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 18:18:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web20303.mail.yahoo.com (web20303.mail.yahoo.com [216.136.226.84]) by hub.freebsd.org (Postfix) with SMTP id BEB6437B416 for ; Thu, 20 Sep 2001 18:18:52 -0700 (PDT) Message-ID: <20010921011851.93437.qmail@web20303.mail.yahoo.com> Received: from [63.103.141.168] by web20303.mail.yahoo.com via HTTP; Thu, 20 Sep 2001 18:18:50 PDT Date: Thu, 20 Sep 2001 18:18:50 -0700 (PDT) From: Anthony Peters Subject: ASSISTANCE NEEDED URGENTLY! To: hackers@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG MR ANTHONY PETERS EMAIL:tony_pet_ers@yahoo.com DEAR FRIEND, I AM MR ANTHONY PETERS, A ONE TIME PERSONAL ASSISTANT TO AN EXPATRIATE DIAMOND ENGINEER IN THE NIMBA COUNTY MINES OF SIERRA-LEON. I AM SEEKING YOUR ASSISTANCE IN A BUSINESS THAT WOULD NEED YOUR CONFIDENTIALITY TRUST AND SUPPORT. MY BOSS WAS KILLED WITH HIS ENTIRE FAMILY OF A WIFE AND THREE CHILDREN DURING THE REVOLUTIONARY UNITED FRONT RAID ON THE NIMBA COUNTY DIAMOND QUARRY OF 1993 WHERE ALMOST SIXTY PEOPLE WERE KILLED.PRIOR TO HIS DEATH, I ASSISTED HIM IN DEPOSITING A HUGE SUM OF MONEY WITH A PRIVATE SECURITY FIRM IN EUROPE.SINCE HIS DEATH,I HAVE TRIED TO CONTACT HIS FAMILY TO NO AVAIL, I HAVE NOT SEEN NOR HEARD FROM ANYBODY CONCERNING HIM. RECENTLY THE SECURITY COMPANY IN EUROPE WHERE THE EXISTENCE OF THE DEPOSIT WAS CONFIRMED TO ME, I WAS THEN ASKED TO PRODUCE HIS NEXT OF KIN TO CLAIM THIS DEPOSIT. I NEED YOUR HELP IN CLAIMING THIS DEPOSIT AS HIS NEXT OF KIN.I HAVE ALL THE PAPERS TO SUCCESSFULLY IMPLEMENT THIS, ALL I ASK, IS YOUR CO-OPERATION AND TRUST. IF YOU ARE INTERESTED,REACH ME BY RETURN MAIL FOR A MORE COMPREHENSIVE BRIEF OF THIS PROJECT. THANK YOU MR ANTHONY PETERS __________________________________________________ Terrorist Attacks on U.S. - How can you help? Donate cash, emergency relief information http://dailynews.yahoo.com/fc/US/Emergency_Information/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 19: 8:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 2536037B414 for ; Thu, 20 Sep 2001 19:08:20 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id D3DD081D05; Thu, 20 Sep 2001 21:08:14 -0500 (CDT) Date: Thu, 20 Sep 2001 21:08:14 -0500 From: Alfred Perlstein To: hackers@FreeBSD.org Subject: Re: ASSISTANCE NEEDED URGENTLY! Message-ID: <20010920210814.F61456@elvis.mu.org> References: <20010921011851.93437.qmail@web20303.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010921011851.93437.qmail@web20303.mail.yahoo.com>; from tony_pet_ers@yahoo.com on Thu, Sep 20, 2001 at 06:18:50PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Removed spammer from cc list... If you found this amusing see: http://www.buddyweiserman.com/ it's sorta amusing. :) * Anthony Peters [010920 20:19] wrote: > > MR ANTHONY PETERS > EMAIL:tony_pet_ers@yahoo.com > > DEAR FRIEND, > > I AM MR ANTHONY PETERS, A ONE TIME PERSONAL ASSISTANT > TO AN EXPATRIATE DIAMOND ENGINEER IN THE NIMBA COUNTY > MINES OF SIERRA-LEON. I AM SEEKING YOUR ASSISTANCE IN > A BUSINESS THAT WOULD NEED YOUR CONFIDENTIALITY TRUST > AND SUPPORT. > > MY BOSS WAS KILLED WITH HIS ENTIRE FAMILY OF A WIFE > AND THREE CHILDREN DURING THE REVOLUTIONARY UNITED > FRONT RAID ON THE NIMBA COUNTY DIAMOND QUARRY OF 1993 > WHERE ALMOST SIXTY PEOPLE WERE KILLED.PRIOR TO HIS > DEATH, I ASSISTED HIM IN DEPOSITING A HUGE SUM OF > MONEY WITH A PRIVATE SECURITY FIRM IN EUROPE.SINCE HIS > DEATH,I HAVE TRIED TO CONTACT HIS FAMILY TO NO AVAIL, > I HAVE NOT SEEN NOR HEARD FROM ANYBODY CONCERNING HIM. > RECENTLY THE SECURITY COMPANY IN EUROPE WHERE THE > EXISTENCE OF THE DEPOSIT WAS CONFIRMED TO ME, I WAS > THEN ASKED TO PRODUCE HIS NEXT OF KIN TO CLAIM THIS > DEPOSIT. > I NEED YOUR HELP IN CLAIMING THIS DEPOSIT AS HIS NEXT > OF KIN.I HAVE ALL THE PAPERS TO SUCCESSFULLY IMPLEMENT > THIS, ALL I ASK, IS YOUR CO-OPERATION AND TRUST. > IF YOU ARE INTERESTED,REACH ME BY RETURN MAIL FOR A > MORE COMPREHENSIVE BRIEF OF THIS PROJECT. > > THANK YOU > > MR ANTHONY PETERS > > > > > > > __________________________________________________ > Terrorist Attacks on U.S. - How can you help? > Donate cash, emergency relief information > http://dailynews.yahoo.com/fc/US/Emergency_Information/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 19:50:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns3.safety.net (ns3.safety.net [216.40.201.32]) by hub.freebsd.org (Postfix) with ESMTP id 8A64A37B405 for ; Thu, 20 Sep 2001 19:50:26 -0700 (PDT) Received: (from les@localhost) by ns3.safety.net (8.10.2/8.10.2) id f8L2oO615274; Thu, 20 Sep 2001 21:50:24 -0500 From: Les Biffle Message-Id: <200109210250.f8L2oO615274@ns3.safety.net> Subject: Re: sendto not sending what I asked... In-Reply-To: <01092111231604.36513@development.wgtn.csg.co.nz> To: davep@afterswish.com Date: Thu, 20 Sep 2001 21:50:23 -0500 (CDT) Cc: Alfred Perlstein , hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL94 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > pkt.ipbit.ip_sum=in_cksum((unsigned short*)(void*)&pkt,20); > pkt.tcpbit.th_sum=tcpsum(&pkt.ipbit); You need to do the TCP checksum first. It changes the payload (the TCP checksum). The IP checksum includes all data, so must be done after the payload changes are done. -Les -- Les Biffle (480) 585-4099 les@safety.net http://www.les.safety.net/ Network Safety Corp., 5831 E. Dynamite Blvd., Cave Creek, AZ 85331 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 20:40:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ipperformance.com (ipperf.com [206.225.36.162]) by hub.freebsd.org (Postfix) with ESMTP id 8291337B41F for ; Thu, 20 Sep 2001 20:40:09 -0700 (PDT) Received: from ipperformance.com (cs6668163-239.austin.rr.com [66.68.163.239]) by ipperformance.com (8.9.3/8.9.3) with SMTP id WAA12218; Thu, 20 Sep 2001 22:39:41 -0500 (CDT) (envelope-from matt@ipperformance.com) Message-ID: <3BAAB547.C065FF97@ipperformance.com> Date: Thu, 20 Sep 2001 22:34:31 -0500 From: Matt Finlay X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Les Biffle Cc: davep@afterswish.com, Alfred Perlstein , hackers@FreeBSD.ORG Subject: Re: sendto not sending what I asked... References: <200109210250.f8L2oO615274@ns3.safety.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Les Biffle wrote: > > pkt.ipbit.ip_sum=in_cksum((unsigned short*)(void*)&pkt,20); > > pkt.tcpbit.th_sum=tcpsum(&pkt.ipbit); > > You need to do the TCP checksum first. It changes the payload (the TCP > checksum). The IP checksum includes all data, so must be done after the > payload changes are done. i think this is incorrect. the IP checksum only includes the IP header and any IP options. therefore order should not matter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 20:45:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ipperformance.com (ipperf.com [206.225.36.162]) by hub.freebsd.org (Postfix) with ESMTP id 16ED937B406 for ; Thu, 20 Sep 2001 20:45:44 -0700 (PDT) Received: from ipperformance.com (cs6668163-239.austin.rr.com [66.68.163.239]) by ipperformance.com (8.9.3/8.9.3) with SMTP id WAA12240; Thu, 20 Sep 2001 22:45:36 -0500 (CDT) (envelope-from matt@ipperformance.com) Message-ID: <3BAAB6AA.9D7EDD99@ipperformance.com> Date: Thu, 20 Sep 2001 22:40:26 -0500 From: Matt Finlay X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Les Biffle , davep@afterswish.com, Alfred Perlstein , hackers@FreeBSD.ORG Subject: Re: sendto not sending what I asked... References: <200109210250.f8L2oO615274@ns3.safety.net> <3BAAB547.C065FF97@ipperformance.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG come to think of it... perhaps you are not calculating the tcp checksum correctly because of the tcp/ip pseudo header. i no longer have the code that was posted, but thinking back i believe this might be the case. Matt Finlay wrote: > Les Biffle wrote: > > > > pkt.ipbit.ip_sum=in_cksum((unsigned short*)(void*)&pkt,20); > > > pkt.tcpbit.th_sum=tcpsum(&pkt.ipbit); > > > > You need to do the TCP checksum first. It changes the payload (the TCP > > checksum). The IP checksum includes all data, so must be done after the > > payload changes are done. > > i think this is incorrect. the IP checksum only includes the IP header and > any IP options. therefore order should not matter. > > 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 Sep 20 21:32: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4-rme.xtra.co.nz (mta4-rme.xtra.co.nz [203.96.92.15]) by hub.freebsd.org (Postfix) with ESMTP id B23D037B41C for ; Thu, 20 Sep 2001 21:32:01 -0700 (PDT) Received: from development.wgtn.csg.co.nz ([210.86.1.68]) by mta4-rme.xtra.co.nz with SMTP id <20010921043200.ESPG2545455.mta4-rme.xtra.co.nz@development.wgtn.csg.co.nz> for ; Fri, 21 Sep 2001 16:32:00 +1200 Content-Type: text/plain; charset="iso-8859-1" From: David Preece Reply-To: davep@afterswish.com To: freebsd-hackers@freebsd.org Subject: More grief in raw packet land - Can someone commit this patch? Date: Fri, 21 Sep 2001 16:31:39 +1200 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <0109211612220H.36513@development.wgtn.csg.co.nz> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG OK, Apologies for my slowness, it's just been one of those slow days. Y'know not enough coffee, too much food? Like that. One of our cats didn't help at about 2am either. So I get a TCP packet together and send it through (the now correctly optioned) socket. sendto fails and returns -1, derefencing __error() gives us 22=EINVAL. A little searching around reveals this to be a prevention of user error fix that went in at some point comparing the length of the buffer sent to sendto and the stated length of the IP packet - if there was a difference the packet doesn't get sent, presumably to prevent the random contents of memory being spilled across the network. This is all good, but as Pascal Bouchareine points out in PR21737 (http://www.FreeBSD.org/cgi/query-pr.cgi?pr=21737) the part of the raw IP code that is responsible for this doesn't convert network to host byte order first and consequently the comparison will always fail for valid packets. This effectively stops anyone from being able to spoof TCP/UDP packets since it is impossible to have both the correct checksum, and get past this length check thing. Unless the length of the packet is 'symmetrical' in hex, but I digress. I've just applied Pascal's suggested patch (althought I just went in and did it manually) to my 4.3-Release development machine and it works fine. Can someone commit this patch to -current, or -stable, or do whatever it is you do :) Cheers, Dave BTW: A personal note - I used to code for windows, and increasingly have crawled down the abstraction layers throught my career (mainly trying to get away from API of the week and get on with writing quality code). This is the first time I've actually gone into the source, fixed it, and made my previously broken kernel work properly. It feels unbelievable, I can't believe what Ethereal is telling me just happened. I may be going to pick up some of those 'junior kernel hacker' tasks soon and see what I can do with them. But not yet, deadlines and baby are coming :) Anyway, over the last 18 months I have _SO_ become a convert. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 22: 6:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [171.66.112.163]) by hub.freebsd.org (Postfix) with ESMTP id 6191137B421 for ; Thu, 20 Sep 2001 22:06:54 -0700 (PDT) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id WAA14233; Thu, 20 Sep 2001 22:00:03 -0700 (PDT) Date: Thu, 20 Sep 2001 22:00:03 -0700 (PDT) From: Annelise Anderson To: Jason Andresen Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: No tools on 4.4-RELEASE ISO? In-Reply-To: <3BA9EEED.B7F0A194@mitre.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 20 Sep 2001, Jason Andresen wrote: > Is the tools directory supposed to be missing on the 4.4 CDs? > I downloaded the full disk 1 ISO yesterday and burned it only to > discover that fdimage.exe was nowhere to be found on the CD. This is > not a good thing when you have to create boot floppies because your > BIOS refuses to acknowledge the existance of your CD-ROM. Strangely > the documentation on the CD still references fdimage and the floppies > are still on there, I guess you are supposed to have a net connection > and get anything you need from the FTP site? > > No tools directory on the mini.iso either--so I guess you need to download fdimage.exe (in a common tools directory) and whatever else from tools you want. fips, osbsbeta, whatever. Annelise -- Annelise Anderson Author of: FreeBSD: An Open-Source Operating System for Your PC Book Website: http://www.bittreepress.com/FreeBSD/introbook/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 22:37:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-35.dsl.lsan03.pacbell.net [63.207.60.35]) by hub.freebsd.org (Postfix) with ESMTP id C58C637B417 for ; Thu, 20 Sep 2001 22:37:30 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6784166D20; Thu, 20 Sep 2001 22:37:30 -0700 (PDT) Date: Thu, 20 Sep 2001 22:37:30 -0700 From: Kris Kennaway To: Annelise Anderson Cc: Jason Andresen , freebsd-hackers@FreeBSD.ORG Subject: Re: No tools on 4.4-RELEASE ISO? Message-ID: <20010920223730.A82191@xor.obsecurity.org> References: <3BA9EEED.B7F0A194@mitre.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from andrsn@andrsn.stanford.edu on Thu, Sep 20, 2001 at 10:00:03PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 20, 2001 at 10:00:03PM -0700, Annelise Anderson wrote: > On Thu, 20 Sep 2001, Jason Andresen wrote: >=20 > > Is the tools directory supposed to be missing on the 4.4 CDs?=20 > > I downloaded the full disk 1 ISO yesterday and burned it only to > > discover that fdimage.exe was nowhere to be found on the CD. This is > > not a good thing when you have to create boot floppies because your=20 > > BIOS refuses to acknowledge the existance of your CD-ROM. Strangely > > the documentation on the CD still references fdimage and the floppies > > are still on there, I guess you are supposed to have a net connection > > and get anything you need from the FTP site? > >=20 > >=20 > No tools directory on the mini.iso either--so I guess you need > to download fdimage.exe (in a common tools directory) and whatever > else from tools you want. fips, osbsbeta, whatever. I seem to recall these programs were owned by WCCDROM (then BSDi, then WRS), and there may have been problems in putting them on the ISO now that WRS isn't responsible for the "official ISO" creation. If so, the WRS CD release should probably end up containing them. Kris --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7qtIZWry0BWjoQKURAnE/AKDRZzNZciU7nR+CcFH6e8UKhHkQEgCg1q3u BnJ0KBQ0y2PepS6jK2ntGDs= =Vo7q -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 23:46:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 6A10637B419 for ; Thu, 20 Sep 2001 23:46:16 -0700 (PDT) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id f8L6jrO16789; Thu, 20 Sep 2001 23:45:54 -0700 (PDT) (envelope-from jkh@freebsd.org) To: kris@obsecurity.org Cc: andrsn@andrsn.stanford.edu, jandrese@mitre.org, freebsd-hackers@freebsd.org Subject: Re: No tools on 4.4-RELEASE ISO? In-Reply-To: <20010920223730.A82191@xor.obsecurity.org> References: <3BA9EEED.B7F0A194@mitre.org> <20010920223730.A82191@xor.obsecurity.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010920234553S.jkh@freebsd.org> Date: Thu, 20 Sep 2001 23:45:53 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 7 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I seem to recall these programs were owned by WCCDROM (then BSDi, then Naw, I'd long since prunted tools/ to just the stuff that was freely redistributable. Murray simply forgot to put it on the ISOs he created. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 20 23:58:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 438BB37B41B for ; Thu, 20 Sep 2001 23:58:43 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f8L6v4130766; Fri, 21 Sep 2001 09:57:04 +0300 (EEST) (envelope-from ru) Date: Fri, 21 Sep 2001 09:57:04 +0300 From: Ruslan Ermilov To: David Preece Cc: davidc@acns.ab.ca, sridharv@ufl.edu, bright@mu.org, hackers@FreeBSD.ORG Subject: Re: Raw sockets: Stevens shall provide. Message-ID: <20010921095704.F27714@sunbay.com> References: <01092112052007.36513@development.wgtn.csg.co.nz> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01092112052007.36513@development.wgtn.csg.co.nz>; from davep@afterswish.com on Fri, Sep 21, 2001 at 12:05:20PM +1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Sep 21, 2001 at 12:05:20PM +1200, David Preece wrote: > Thanks for your help, as suggested the combination of IP_HDRINCL and reading > Stevens seems to have me back on the right path. Part of the confusion was > the Linux implementation of IP_HDRINCL appears to need the hardware addresses > writing as well, consequently there are lots of examples of this being done > in order to forge arp replies etc - not what I needed. Or rather, it was > actually. > > Anyway, the code is now refusing to send packets entirely, which is actually > good because it implies a checksum is broken somewhere and that's a bug, not > a misunderstanding about the API. > I didn't follow the thread, but the error may be caused by supplying some header fields in incorrect byte order. Some fields are expected in host byte order, and some are in net byte order, e.g. the ip_id (if non-zero). I wrote the demo program that uses IP_HDRINCL option, attached. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="rawip.c" #include #include #include #include #include #include #include #include #include struct udppacket { struct ip ip; struct udphdr uh; char data[IP_MAXPACKET - sizeof(struct ip) - sizeof(struct udphdr)]; }; /* struct ip { }; struct udphdr { u_short uh_sport; # source port u_short uh_dport; # destination port u_short uh_ulen; # udp length u_short uh_sum; # udp checksum }; */ int main(void) { int s; int hincl = 1; struct udppacket packet; struct sockaddr_in to; bzero(&to, sizeof to); to.sin_len = sizeof to; to.sin_family = AF_INET; to.sin_addr.s_addr = htonl(INADDR_LOOPBACK); to.sin_port = 0; bzero(&packet, offsetof(struct udppacket, data)); packet.ip.ip_v = IPVERSION; packet.ip.ip_hl = sizeof(packet.ip) >> 2; packet.ip.ip_len = sizeof(packet.ip) + sizeof(packet.uh); packet.ip.ip_id = 0; packet.ip.ip_off = 0; packet.ip.ip_ttl = MAXTTL; packet.ip.ip_p = IPPROTO_UDP; packet.ip.ip_src.s_addr = packet.ip.ip_dst.s_addr = htonl(INADDR_LOOPBACK); if ((s = socket(AF_INET, SOCK_RAW, 0)) == -1) err(1, "socket"); if (setsockopt(s, IPPROTO_IP, IP_HDRINCL, &hincl, sizeof(hincl)) == -1) err(1, "setsockopt(IP_HDRINCL)"); if (sendto(s, &packet, 28, 0, (struct sockaddr *)&to, sizeof to) == -1) err(1, "sendto"); return (0); } --NzB8fVQJ5HfG6fxh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 0: 7: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [171.66.112.163]) by hub.freebsd.org (Postfix) with ESMTP id 4B2AC37B40D for ; Fri, 21 Sep 2001 00:06:57 -0700 (PDT) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id AAA14592; Fri, 21 Sep 2001 00:00:05 -0700 (PDT) Date: Fri, 21 Sep 2001 00:00:05 -0700 (PDT) From: Annelise Anderson To: Kris Kennaway Cc: Jason Andresen , freebsd-hackers@FreeBSD.ORG Subject: Re: No tools on 4.4-RELEASE ISO? In-Reply-To: <20010920223730.A82191@xor.obsecurity.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 20 Sep 2001, Kris Kennaway wrote: > > On Thu, 20 Sep 2001, Jason Andresen wrote: > > > > > Is the tools directory supposed to be missing on the 4.4 CDs? > > I seem to recall these programs were owned by WCCDROM (then BSDi, then > WRS), and there may have been problems in putting them on the ISO now > that WRS isn't responsible for the "official ISO" creation. If so, > the WRS CD release should probably end up containing them. > I get this with strings: Borland C++ - Copyright 1991 Borland Intl. Version 1.5 Copyright (c) 1996-7 Robert Nordier fdimage.exe is available in various linux and OpenBSD directories that turn up with google...guess you just need a bootable cdrom these days... Annelise -- Annelise Anderson Author of: FreeBSD: An Open-Source Operating System for Your PC Book Website: http://www.bittreepress.com/FreeBSD/introbook/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 0:12:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 4658D37B41D; Fri, 21 Sep 2001 00:12:32 -0700 (PDT) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id JAA57756; Fri, 21 Sep 2001 09:03:12 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200109210703.JAA57756@info.iet.unipi.it> Subject: any reason to use m_devget in the "dc" driver ? To: hackers@freebsd.org, wpaul@freebsd.org Date: Fri, 21 Sep 2001 09:03:12 +0200 (CEST) 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does anyone know of specific reasons to use m_devget() to extract received packets from the rx buffer in the "dc" driver, as opposed to passing up the mbuf and just replacing it with a fresh one in the controller's queue ? Other drivers just happily do the latter, including the "de" driver, so there seems to be no problem with the chipset in handling this ? Bill, any comments ? cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone (510) 666 2927 . ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 1:14:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id BF05537B426 for ; Fri, 21 Sep 2001 01:14:48 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.4/8.11.4) with ESMTP id f8L8Emv66895 for ; Fri, 21 Sep 2001 10:14:48 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: hackers@freebsd.org Subject: Cheap SCSI-Analyzers From: Poul-Henning Kamp Date: Fri, 21 Sep 2001 10:14:48 +0200 Message-ID: <66893.1001060088@critter> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG These guys have 2 SCSI analyzers at $200 each: http://www.metricsales.com/bargains.asp -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 3:52:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from samar.sasken.com (samar.sasken.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 8103E37B416 for ; Fri, 21 Sep 2001 03:52:33 -0700 (PDT) Received: from samar (localhost [127.0.0.1]) by samar.sasken.com (8.11.3/8.11.3) with SMTP id f8LAqUV16284 for ; Fri, 21 Sep 2001 16:22:30 +0530 (IST) Received: from localhost (pmk@localhost) by sunk2.sasi.com (8.9.3/8.9.3) with ESMTP id QAA14079 for ; Fri, 21 Sep 2001 16:22:29 +0530 (IST) Date: Fri, 21 Sep 2001 16:22:29 +0530 (IST) From: Mohana Krishna Penumetcha X-Sender: To: Subject: arguments to driver ioctl commands SIOC[ADD|DEL]MULTI In-Reply-To: <66893.1001060088@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG when the driver ioctl (i.e. ifp->if_ioctl) is called with either SIOCADDMULTI or SIOCDELMULT, NULL value is passed as data argument to the ioctl function. but going through the code(in net/if.c file if_addmulti and if_delmulti functions) doesn't reveal the logic behind it. can anyone tell me why NULL pointer is passed instead of pointer to the multicast address structre either being added or deleted. my implementation of the driver requires this value, can anyone suggest a method to get those values? regards, mohan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 6:14: 8 2001 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 E987A37B405; Fri, 21 Sep 2001 06:14:05 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA10693; Fri, 21 Sep 2001 09:12:36 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f8LDCAR26996; Fri, 21 Sep 2001 09:12:10 -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 Message-ID: <15275.15530.678683.65377@grasshopper.cs.duke.edu> Date: Fri, 21 Sep 2001 09:12:10 -0400 (EDT) To: Luigi Rizzo Cc: hackers@freebsd.org, wpaul@freebsd.org Subject: Re: any reason to use m_devget in the "dc" driver ? In-Reply-To: <200109210703.JAA57756@info.iet.unipi.it> References: <200109210703.JAA57756@info.iet.unipi.it> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Luigi Rizzo writes: > Does anyone know of specific reasons to use m_devget() > to extract received packets from the rx buffer in the "dc" > driver, as opposed to passing up the mbuf and just > replacing it with a fresh one in the controller's queue ? > > Other drivers just happily do the latter, including the "de" > driver, so there seems to be no problem with the chipset > in handling this ? I imagine that this was done to follow alignment constraints on non-i386 platforms where having the ip header misaligned is fatal. (the tulip is not capable of byte granularity DMA, so you can't intentionally misalign the ethernet header & end up with an aligned IP header) I imagine the i386 should be made an exception. See rev 1.17 of sys/dev/nge/if_nge.c Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 7:48:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from c527597-a.cstvl1.sfba.home.com (c527597-a.cstvl1.sfba.home.com [24.176.204.87]) by hub.freebsd.org (Postfix) with ESMTP id 6E9A137B41C; Fri, 21 Sep 2001 07:48:42 -0700 (PDT) Received: (from bmah@localhost) by c527597-a.cstvl1.sfba.home.com (8.11.6/8.11.6) id f8LEmfd54113; Fri, 21 Sep 2001 07:48:41 -0700 (PDT) (envelope-from bmah) Message-Id: <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Jordan Hubbard Cc: kris@obsecurity.org, andrsn@andrsn.stanford.edu, jandrese@mitre.org, freebsd-hackers@FreeBSD.ORG Subject: Re: No tools on 4.4-RELEASE ISO? In-Reply-To: <20010920234553S.jkh@freebsd.org> References: <3BA9EEED.B7F0A194@mitre.org> <20010920223730.A82191@xor.obsecurity.org> <20010920234553S.jkh@freebsd.org> Comments: In-reply-to Jordan Hubbard message dated "Thu, 20 Sep 2001 23:45:53 -0700." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-358163300P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 21 Sep 2001 07:48:41 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --==_Exmh_-358163300P Content-Type: text/plain; charset=us-ascii If memory serves me right, Jordan Hubbard wrote: > > I seem to recall these programs were owned by WCCDROM (then BSDi, then > > Naw, I'd long since prunted tools/ to just the stuff that was freely > redistributable. Murray simply forgot to put it on the ISOs he > created. :) OK, it sounds like I need to make an(other) entry in the errata file. What about something like: The tools/ directory of a FreeBSD CDROM distribution typically contains some DOS programs for i386 machines, such as fdimage and fips. This directory was inadvertently omitted from the 4.4-RELEASE ISO images generated by the FreeBSD Project. The contents of the tools/ directory are, however, available by anonymous FTP at ftp://ftp.FreeBSD.org/pub/ FreeBSD/tools (many mirrors also have a copy of this directory). (Use your imagination to get the right markup.) How's that? Bruce. --==_Exmh_-358163300P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE7q1NI2MoxcVugUsMRAkrMAJ9vT6DckBB9he0zc3W2J54DOyqhNwCgnFfE 6HOf4ENak7MbkBVuUz0SmpI= =jvlc -----END PGP SIGNATURE----- --==_Exmh_-358163300P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 7:51: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 6630437B41C; Fri, 21 Sep 2001 07:50:56 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 70CEA81D01; Fri, 21 Sep 2001 09:50:56 -0500 (CDT) Date: Fri, 21 Sep 2001 09:50:56 -0500 From: Alfred Perlstein To: "Bruce A. Mah" Cc: Jordan Hubbard , kris@obsecurity.org, andrsn@andrsn.stanford.edu, jandrese@mitre.org, freebsd-hackers@FreeBSD.ORG Subject: Re: No tools on 4.4-RELEASE ISO? Message-ID: <20010921095056.M61456@elvis.mu.org> References: <3BA9EEED.B7F0A194@mitre.org> <20010920223730.A82191@xor.obsecurity.org> <20010920234553S.jkh@freebsd.org> <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com>; from bmah@FreeBSD.ORG on Fri, Sep 21, 2001 at 07:48:41AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Bruce A. Mah [010921 09:49] wrote: > If memory serves me right, Jordan Hubbard wrote: > > > I seem to recall these programs were owned by WCCDROM (then BSDi, then > > > > Naw, I'd long since prunted tools/ to just the stuff that was freely > > redistributable. Murray simply forgot to put it on the ISOs he > > created. :) > > OK, it sounds like I need to make an(other) entry in the errata file. > > What about something like: > > The tools/ directory of a FreeBSD CDROM distribution typically contains > some DOS programs for i386 machines, such as fdimage and fips. This > directory was inadvertently omitted from the 4.4-RELEASE ISO images > generated by the FreeBSD Project. The contents of the tools/ directory > are, however, available by anonymous FTP at ftp://ftp.FreeBSD.org/pub/ > FreeBSD/tools (many mirrors also have a copy of this directory). > > (Use your imagination to get the right markup.) > > How's that? I don't know, missing the tool to make disk images from DOS is a pretty bad thing IMO, any way to get this fixed? -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 8:18:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from c527597-a.cstvl1.sfba.home.com (c527597-a.cstvl1.sfba.home.com [24.176.204.87]) by hub.freebsd.org (Postfix) with ESMTP id 1B39F37B40A; Fri, 21 Sep 2001 08:18:39 -0700 (PDT) Received: (from bmah@localhost) by c527597-a.cstvl1.sfba.home.com (8.11.6/8.11.6) id f8LFITg54534; Fri, 21 Sep 2001 08:18:29 -0700 (PDT) (envelope-from bmah) Message-Id: <200109211518.f8LFITg54534@c527597-a.cstvl1.sfba.home.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Alfred Perlstein Cc: "Bruce A. Mah" , Jordan Hubbard , kris@obsecurity.org, andrsn@andrsn.stanford.edu, jandrese@mitre.org, freebsd-hackers@FreeBSD.ORG Subject: Re: No tools on 4.4-RELEASE ISO? In-Reply-To: <20010921095056.M61456@elvis.mu.org> References: <3BA9EEED.B7F0A194@mitre.org> <20010920223730.A82191@xor.obsecurity.org> <20010920234553S.jkh@freebsd.org> <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> <20010921095056.M61456@elvis.mu.org> Comments: In-reply-to Alfred Perlstein message dated "Fri, 21 Sep 2001 09:50:56 -0500." From: bmah@FreeBSD.ORG (Bruce A. Mah) Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_276878188P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 21 Sep 2001 08:18:29 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --==_Exmh_276878188P Content-Type: text/plain; charset=us-ascii If memory serves me right, Alfred Perlstein wrote: > I don't know, missing the tool to make disk images from DOS is > a pretty bad thing IMO, any way to get this fixed? I can't think of any way to do this besides re-rolling the ISO images. Note that people buying the physical CDROMs might not see this problem at all...this is why I wrote "generated by the FreeBSD Project" in the proposed errata entry. If the release engineers for the various vendors making CDROM/DVD distributions are following along, hopefully they'll avoid making the same mistake. Note that the set of people affected is going to be "people who can't do anonymous FTP, don't have bootable CDROMs, and *only* have the ISO images to work with". I don't know for sure, but I'd expect this set to be pretty small...if they don't have Internet access, how'd they get the ISO images? Bruce. --==_Exmh_276878188P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE7q1pF2MoxcVugUsMRAgfuAJ9Ln+puJblbLYyx49rVpfmJa5vPSACeK6SP NX7gsJIvRe4dBpihWnKTxX0= =a1OL -----END PGP SIGNATURE----- --==_Exmh_276878188P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 8:20:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from math.missouri.edu (math.missouri.edu [128.206.49.180]) by hub.freebsd.org (Postfix) with ESMTP id BD5AE37B41C for ; Fri, 21 Sep 2001 08:20:27 -0700 (PDT) Received: from math.missouri.edu (cauchy.math.missouri.edu [128.206.49.166]) by math.missouri.edu (8.11.3/8.11.3) with ESMTP id f8LFKRK63232 for ; Fri, 21 Sep 2001 10:20:27 -0500 (CDT) (envelope-from stephen@math.missouri.edu) Message-ID: <3BAB5ABB.2364244@math.missouri.edu> Date: Fri, 21 Sep 2001 10:20:27 -0500 From: Stephen Montgomery-Smith Organization: University of Missouri X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Re: Could not bind References: <3BA3F70D.27C2136@math.missouri.edu> <3BA520BC.E26A64F0@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks everyone for exellent answers - I learned something from every single email I received in response. Thanks, Stephen > Stephen Montgomery-Smith wrote: > > > > I have written a server program that listens on port 3000. The program > > works very well except for one feature. I am asking if that is normal, > > or whether I forgot something. > > > > If I run the program it does fine. If I then kill the program (after it > > has accepted connections), and then run the program again, the bind > > function fails to work, and I get a message like "Could not bind" (see > > program below). If I wait a while, like a minute or two, then the > > program will work again. Is this normal behavior, or did I miss > > something? > -- Stephen Montgomery-Smith stephen@math.missouri.edu 307 Math Science Building stephen@showme.missouri.edu Department of Mathematics stephen@missouri.edu University of Missouri-Columbia Columbia, MO 65211 USA Phone (573) 882 4540 Fax (573) 882 1869 http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 8:39:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 5CB8137B415; Fri, 21 Sep 2001 08:39:16 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 49D7781D07; Fri, 21 Sep 2001 10:39:16 -0500 (CDT) Date: Fri, 21 Sep 2001 10:39:16 -0500 From: Alfred Perlstein To: "Bruce A. Mah" Cc: Jordan Hubbard , kris@obsecurity.org, andrsn@andrsn.stanford.edu, jandrese@mitre.org, freebsd-hackers@FreeBSD.ORG Subject: Re: No tools on 4.4-RELEASE ISO? Message-ID: <20010921103916.A97903@elvis.mu.org> References: <3BA9EEED.B7F0A194@mitre.org> <20010920223730.A82191@xor.obsecurity.org> <20010920234553S.jkh@freebsd.org> <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> <20010921095056.M61456@elvis.mu.org> <200109211518.f8LFITg54534@c527597-a.cstvl1.sfba.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109211518.f8LFITg54534@c527597-a.cstvl1.sfba.home.com>; from bmah@FreeBSD.ORG on Fri, Sep 21, 2001 at 08:18:29AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Bruce A. Mah [010921 10:18] wrote: > If memory serves me right, Alfred Perlstein wrote: > > > I don't know, missing the tool to make disk images from DOS is > > a pretty bad thing IMO, any way to get this fixed? > > I can't think of any way to do this besides re-rolling the ISO images. > > Note that people buying the physical CDROMs might not see this problem > at all...this is why I wrote "generated by the FreeBSD Project" in the > proposed errata entry. If the release engineers for the various vendors > making CDROM/DVD distributions are following along, hopefully they'll > avoid making the same mistake. > > Note that the set of people affected is going to be "people who can't do > anonymous FTP, don't have bootable CDROMs, and *only* have the ISO > images to work with". I don't know for sure, but I'd expect this set to > be pretty small...if they don't have Internet access, how'd they get the > ISO images? Wouldn't it be trivial to just mount the ISO, tar copy it, add the files then rerun mkisofs? -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 8:45: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from amun.isnic.is (amun.isnic.is [193.4.58.10]) by hub.freebsd.org (Postfix) with ESMTP id B988437B40E; Fri, 21 Sep 2001 08:44:59 -0700 (PDT) Received: (from oli@localhost) by amun.isnic.is (8.11.6/8.11.6/isnic) id f8LFivi34440; Fri, 21 Sep 2001 15:44:57 GMT (envelope-from oli) Date: Fri, 21 Sep 2001 15:44:56 +0000 From: Olafur Osvaldsson To: Alfred Perlstein Cc: "Bruce A. Mah" , Jordan Hubbard , kris@obsecurity.org, andrsn@andrsn.stanford.edu, jandrese@mitre.org, freebsd-hackers@FreeBSD.ORG Subject: Re: No tools on 4.4-RELEASE ISO? Message-ID: <20010921154456.C29490@isnic.is> References: <3BA9EEED.B7F0A194@mitre.org> <20010920223730.A82191@xor.obsecurity.org> <20010920234553S.jkh@freebsd.org> <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> <20010921095056.M61456@elvis.mu.org> <200109211518.f8LFITg54534@c527597-a.cstvl1.sfba.home.com> <20010921103916.A97903@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010921103916.A97903@elvis.mu.org>; from bright@mu.org on Fri, Sep 21, 2001 at 10:39:16AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 21 Sep 2001, Alfred Perlstein wrote: > Wouldn't it be trivial to just mount the ISO, tar copy it, add the > files then rerun mkisofs? > This would result in all mirrors re-downloading the image wich is not such a big deal except now there are a minimum of 5 users downloading the image at any given time wich locks the file so it won't get updated unless the admin disconnects the users and then the user can't resume the download and can't start again untill the mirror site has finished downloading the image from the master wich in some cases takes hours. This will probably result in a lot more annoyed users than the first problem. Oli -- Olafur Osvaldsson Systems Administrator Internet Iceland inc. Tel: +354 525-5291 Email: oli@isnic.is To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 9: 4:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [129.83.20.90]) by hub.freebsd.org (Postfix) with ESMTP id E65E137B412; Fri, 21 Sep 2001 09:04:46 -0700 (PDT) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id f8LG4dE17051; Fri, 21 Sep 2001 12:04:39 -0400 (EDT) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id f8LG4af18844; Fri, 21 Sep 2001 12:04:36 -0400 (EDT) Received: from dhcp-105-164.mitre.org (128.29.105.164) by mailhub2.mitre.org with SMTP id 7799361; Fri, 21 Sep 2001 12:04:34 -0400 Message-ID: <3BAB6513.F6251E77@mitre.org> Date: Fri, 21 Sep 2001 12:04:35 -0400 From: Jason Andresen Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: bmah@freebsd.org Cc: Alfred Perlstein , Jordan Hubbard , kris@obsecurity.org, andrsn@andrsn.stanford.edu, freebsd-hackers@freebsd.org Subject: Re: No tools on 4.4-RELEASE ISO? References: <3BA9EEED.B7F0A194@mitre.org> <20010920223730.A82191@xor.obsecurity.org> <20010920234553S.jkh@freebsd.org> <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> <20010921095056.M61456@elvis.mu.org> <200109211518.f8LFITg54534@c527597-a.cstvl1.sfba.home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Bruce A. Mah" wrote: > > Note that the set of people affected is going to be "people who can't do > anonymous FTP, don't have bootable CDROMs, and *only* have the ISO > images to work with". I don't know for sure, but I'd expect this set to > be pretty small...if they don't have Internet access, how'd they get the > ISO images? Probably more often that you'd expect. I know I had to install 4.4 in our lab (which blocks most net access) full of old machines. Fortunatly I have a 4.3 ISO sitting here that I just grabbed fdimage from and went on, but it did seem like a rather noticable oversight. What about the boot managers in that directory? Certainly people will want to dual boot their new FreeBSD installs? -- \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org |\/ | | | / _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 9:16:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [129.83.20.90]) by hub.freebsd.org (Postfix) with ESMTP id 6824637B41C; Fri, 21 Sep 2001 09:16:20 -0700 (PDT) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id f8LGFwE19782; Fri, 21 Sep 2001 12:15:59 -0400 (EDT) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id f8LGFkf21745; Fri, 21 Sep 2001 12:15:46 -0400 (EDT) Received: from dhcp-105-164.mitre.org (128.29.105.164) by mailhub2.mitre.org with SMTP id 7799564; Fri, 21 Sep 2001 12:15:45 -0400 Message-ID: <3BAB67B1.99D6DC27@mitre.org> Date: Fri, 21 Sep 2001 12:15:45 -0400 From: Jason Andresen Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Olafur Osvaldsson Cc: Alfred Perlstein , "Bruce A. Mah" , Jordan Hubbard , kris@obsecurity.org, andrsn@andrsn.stanford.edu, freebsd-hackers@freebsd.org Subject: Re: No tools on 4.4-RELEASE ISO? References: <3BA9EEED.B7F0A194@mitre.org> <20010920223730.A82191@xor.obsecurity.org> <20010920234553S.jkh@freebsd.org> <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> <20010921095056.M61456@elvis.mu.org> <200109211518.f8LFITg54534@c527597-a.cstvl1.sfba.home.com> <20010921103916.A97903@elvis.mu.org> <20010921154456.C29490@isnic.is> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Olafur Osvaldsson wrote: > > On Fri, 21 Sep 2001, Alfred Perlstein wrote: > > > Wouldn't it be trivial to just mount the ISO, tar copy it, add the > > files then rerun mkisofs? > > > > This would result in all mirrors re-downloading the image wich is not such a > big deal except now there are a minimum of 5 users downloading the image at > any given time wich locks the file so it won't get updated unless the admin > disconnects the users and then the user can't resume the download and can't > start again untill the mirror site has finished downloading the image from the > master wich in some cases takes hours. > > This will probably result in a lot more annoyed users than the first problem. Why not burn the new ISO as 4.4-install_with_tools.iso and distribute that? You could then distribute a little readme with the new ISO explaning what it is and why you should get it. Heck, a lot of the mirrors don't even have the original ISO yet, you can probably fix this before they mirror the first ISO. -- \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org |\/ | | | / _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 9:46: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id D5F5C37B401; Fri, 21 Sep 2001 09:46:01 -0700 (PDT) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id f8LGjlO18682; Fri, 21 Sep 2001 09:45:48 -0700 (PDT) (envelope-from jkh@freebsd.org) To: bmah@freebsd.org Cc: kris@obsecurity.org, andrsn@andrsn.stanford.edu, jandrese@mitre.org, freebsd-hackers@freebsd.org Subject: Re: No tools on 4.4-RELEASE ISO? In-Reply-To: <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> References: <20010920223730.A82191@xor.obsecurity.org> <20010920234553S.jkh@freebsd.org> <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010921094547M.jkh@freebsd.org> Date: Fri, 21 Sep 2001 09:45:47 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 31 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sounds fine to me! From: "Bruce A. Mah" Subject: Re: No tools on 4.4-RELEASE ISO? Date: Fri, 21 Sep 2001 07:48:41 -0700 > If memory serves me right, Jordan Hubbard wrote: > > > I seem to recall these programs were owned by WCCDROM (then BSDi, then > > > > Naw, I'd long since prunted tools/ to just the stuff that was freely > > redistributable. Murray simply forgot to put it on the ISOs he > > created. :) > > OK, it sounds like I need to make an(other) entry in the errata file. > > What about something like: > > The tools/ directory of a FreeBSD CDROM distribution typically contains > some DOS programs for i386 machines, such as fdimage and fips. This > directory was inadvertently omitted from the 4.4-RELEASE ISO images > generated by the FreeBSD Project. The contents of the tools/ directory > are, however, available by anonymous FTP at ftp://ftp.FreeBSD.org/pub/ > FreeBSD/tools (many mirrors also have a copy of this directory). > > (Use your imagination to get the right markup.) > > How's that? > > Bruce. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 9:47:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id A016F37B410; Fri, 21 Sep 2001 09:47:38 -0700 (PDT) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id f8LGlLO18698; Fri, 21 Sep 2001 09:47:22 -0700 (PDT) (envelope-from jkh@freebsd.org) To: bright@mu.org Cc: bmah@freebsd.org, kris@obsecurity.org, andrsn@andrsn.stanford.edu, jandrese@mitre.org, freebsd-hackers@freebsd.org Subject: Re: No tools on 4.4-RELEASE ISO? In-Reply-To: <20010921095056.M61456@elvis.mu.org> References: <20010920234553S.jkh@freebsd.org> <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> <20010921095056.M61456@elvis.mu.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010921094721N.jkh@freebsd.org> Date: Fri, 21 Sep 2001 09:47:21 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 45 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It will require re-rolling 4.4-install.iso and 4.4-mini.iso. If you want to petition hubs@freebsd.org to see if they'd object to re-mirroring them, that would be a good first step. If they don't disagree, I'm sure Murray would be happy to fix them in his ISO build tree and push them back up to ftp-master again. I believe he already did this for the set going out from WRS. - Jordan > * Bruce A. Mah [010921 09:49] wrote: > > If memory serves me right, Jordan Hubbard wrote: > > > > I seem to recall these programs were owned by WCCDROM (then BSDi, then > > > > > > Naw, I'd long since prunted tools/ to just the stuff that was freely > > > redistributable. Murray simply forgot to put it on the ISOs he > > > created. :) > > > > OK, it sounds like I need to make an(other) entry in the errata file. > > > > What about something like: > > > > The tools/ directory of a FreeBSD CDROM distribution typically contains > > some DOS programs for i386 machines, such as fdimage and fips. This > > directory was inadvertently omitted from the 4.4-RELEASE ISO images > > generated by the FreeBSD Project. The contents of the tools/ directory > > are, however, available by anonymous FTP at ftp://ftp.FreeBSD.org/pub/ > > FreeBSD/tools (many mirrors also have a copy of this directory). > > > > (Use your imagination to get the right markup.) > > > > How's that? > > I don't know, missing the tool to make disk images from DOS is > a pretty bad thing IMO, any way to get this fixed? > > > > -- > -Alfred Perlstein [alfred@freebsd.org] > 'Instead of asking why a piece of software is using "1970s technology," > start asking why software is ignoring 30 years of accumulated wisdom.' > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 10:27:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id DE66937B41E; Fri, 21 Sep 2001 10:27:36 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 9F8CB81D05; Fri, 21 Sep 2001 12:27:31 -0500 (CDT) Date: Fri, 21 Sep 2001 12:27:31 -0500 From: Alfred Perlstein To: Jordan Hubbard Cc: bmah@freebsd.org, kris@obsecurity.org, andrsn@andrsn.stanford.edu, jandrese@mitre.org, freebsd-hackers@freebsd.org Subject: Re: No tools on 4.4-RELEASE ISO? Message-ID: <20010921122731.D97903@elvis.mu.org> References: <20010920234553S.jkh@freebsd.org> <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> <20010921095056.M61456@elvis.mu.org> <20010921094721N.jkh@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010921094721N.jkh@freebsd.org>; from jkh@freebsd.org on Fri, Sep 21, 2001 at 09:47:21AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Jordan Hubbard [010921 11:47] wrote: > It will require re-rolling 4.4-install.iso and 4.4-mini.iso. If you > want to petition hubs@freebsd.org to see if they'd object to > re-mirroring them, that would be a good first step. If they don't > disagree, I'm sure Murray would be happy to fix them in his ISO build > tree and push them back up to ftp-master again. I believe he already > did this for the set going out from WRS. Oh, I don't give a cr*p about ISO downloaders, I find them annoying. People downloading ISO can find it, people trying to install from pressed CDroms without net access might find it a bit more difficult. As long as the media shipped out has the tools I'm fine. My concern was some newbie getting a boxed set then hating life because he now has another hurdle to leap to get FreeBSD installed. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 10:32:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from c527597-a.cstvl1.sfba.home.com (c527597-a.cstvl1.sfba.home.com [24.176.204.87]) by hub.freebsd.org (Postfix) with ESMTP id AB54237B403; Fri, 21 Sep 2001 10:32:15 -0700 (PDT) Received: (from bmah@localhost) by c527597-a.cstvl1.sfba.home.com (8.11.6/8.11.6) id f8LHWFG76723; Fri, 21 Sep 2001 10:32:15 -0700 (PDT) (envelope-from bmah) Message-Id: <200109211732.f8LHWFG76723@c527597-a.cstvl1.sfba.home.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Jordan Hubbard Cc: bmah@freebsd.org, kris@obsecurity.org, andrsn@andrsn.stanford.edu, jandrese@mitre.org, freebsd-hackers@freebsd.org Subject: Re: No tools on 4.4-RELEASE ISO? In-Reply-To: <20010921094547M.jkh@freebsd.org> References: <20010920223730.A82191@xor.obsecurity.org> <20010920234553S.jkh@freebsd.org> <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> <20010921094547M.jkh@freebsd.org> Comments: In-reply-to Jordan Hubbard message dated "Fri, 21 Sep 2001 09:45:47 -0700." From: bmah@freebsd.org (Bruce A. Mah) Reply-To: bmah@freebsd.org X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-2074614972P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 21 Sep 2001 10:32:15 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --==_Exmh_-2074614972P Content-Type: text/plain; charset=us-ascii If memory serves me right, Jordan Hubbard wrote: > Sounds fine to me! OK. I'll go ahead and do this. In the event that the decision is made to reroll the ISO image(s), we'd have to write up something anyways. Bruce. --==_Exmh_-2074614972P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE7q3mf2MoxcVugUsMRArDYAJ44MtzOldWsBljK1MJecB2HONOc0gCfT8AQ iofIBx6kNpTWQseg8FmmC1o= =Zzj+ -----END PGP SIGNATURE----- --==_Exmh_-2074614972P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 10:46:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 3D74437B406; Fri, 21 Sep 2001 10:46:47 -0700 (PDT) Received: from mindspring.com (dialup-209.247.138.70.Dial1.SanJose1.Level3.net [209.247.138.70]) by falcon.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f8LHjp301264; Fri, 21 Sep 2001 10:45:51 -0700 (PDT) Message-ID: <3BAB7CFD.D5776F77@mindspring.com> Date: Fri, 21 Sep 2001 10:46:37 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: Luigi Rizzo , hackers@freebsd.org, wpaul@freebsd.org Subject: Re: any reason to use m_devget in the "dc" driver ? References: <200109210703.JAA57756@info.iet.unipi.it> <15275.15530.678683.65377@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andrew Gallatin wrote: > I imagine that this was done to follow alignment constraints on > non-i386 platforms where having the ip header misaligned is fatal. > (the tulip is not capable of byte granularity DMA, so you can't > intentionally misalign the ethernet header & end up with an aligned IP > header) This is the reason: the ethernet header is 14 bytes. > I imagine the i386 should be made an exception. See rev 1.17 of > sys/dev/nge/if_nge.c I disagree with this code; the elemenets in the header are referenced multiple times. If you are doing the checksum check, you might as well be relocating the data, as well. The change I would make would be to integrate the checksum calculation with the m_devget(), to ensure a single pass, in the case that m_devget() must be used to get aligned packet payload, and the checksum has not been offloaded to hardware. When Bill finishes the Tigon III driver, he will find out that it does not have the firmware problem the Tigon II has, and that he can actually leave the checksum offload active, and still be able to use VLANs (something that you can not do with the Tigon II without serious changes to the firmware). IMO, in the vast majority of cases, it makes sense to do the m_devget(), even though it looks like you can do the unaligned access in 2 bus cycles instead of 1, and come out ahead, for the IP and TCP header elements. This could be fixed by reducing the references to the elements so that they are extracted only once, at which point, the cost breaks even at a 32 byte or larger payload size, and it is better to do the unaligned references than the copy (assuming checksum offload, rather than opportunistic copy at checksum calculation time). Reordering the code to do it this way is an ...interesting... exercise, since you have to make some assumptions that may not be valid (e.g. that it is an IP payload) before you get to the ipinput code. In any case, I think it would be useful to turn on the CR bit that causes unaligned access faults on the 486 and above Intel processors, as well (this discussion has taken place before). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 10:54:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-35.dsl.lsan03.pacbell.net [63.207.60.35]) by hub.freebsd.org (Postfix) with ESMTP id EF37C37B40C; Fri, 21 Sep 2001 10:54:51 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6EA4866D20; Fri, 21 Sep 2001 10:54:51 -0700 (PDT) Date: Fri, 21 Sep 2001 10:54:51 -0700 From: Kris Kennaway To: Olafur Osvaldsson Cc: Alfred Perlstein , "Bruce A. Mah" , Jordan Hubbard , kris@obsecurity.org, andrsn@andrsn.stanford.edu, jandrese@mitre.org, freebsd-hackers@FreeBSD.ORG Subject: Re: No tools on 4.4-RELEASE ISO? Message-ID: <20010921105451.C88881@xor.obsecurity.org> References: <3BA9EEED.B7F0A194@mitre.org> <20010920223730.A82191@xor.obsecurity.org> <20010920234553S.jkh@freebsd.org> <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> <20010921095056.M61456@elvis.mu.org> <200109211518.f8LFITg54534@c527597-a.cstvl1.sfba.home.com> <20010921103916.A97903@elvis.mu.org> <20010921154456.C29490@isnic.is> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="z4+8/lEcDcG5Ke9S" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010921154456.C29490@isnic.is>; from oli@isnic.is on Fri, Sep 21, 2001 at 03:44:56PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --z4+8/lEcDcG5Ke9S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 21, 2001 at 03:44:56PM +0000, Olafur Osvaldsson wrote: >=20 > On Fri, 21 Sep 2001, Alfred Perlstein wrote: >=20 > > Wouldn't it be trivial to just mount the ISO, tar copy it, add the > > files then rerun mkisofs? > >=20 >=20 > This would result in all mirrors re-downloading the image wich is not suc= h a > big deal except now there are a minimum of 5 users downloading the image = at > any given time wich locks the file so it won't get updated unless the adm= in > disconnects the users and then the user can't resume the download and can= 't > start again untill the mirror site has finished downloading the image fro= m the > master wich in some cases takes hours. Just call the new one 4.4-RELEASE-with-tools.iso or whatever the naming scheme is. Kris --z4+8/lEcDcG5Ke9S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7q37qWry0BWjoQKURAkSNAJ91oXMqwQHp/hHXtVkOb6zWRhM8jwCg9QdB fyY3+0O+N+twi6NRKyF7BjU= =jVVw -----END PGP SIGNATURE----- --z4+8/lEcDcG5Ke9S-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 11: 6:51 2001 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 DB08637B40E; Fri, 21 Sep 2001 11:06:45 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA19032; Fri, 21 Sep 2001 14:06:39 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f8LI6DX37320; Fri, 21 Sep 2001 14:06:13 -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 Message-ID: <15275.33173.594275.19570@grasshopper.cs.duke.edu> Date: Fri, 21 Sep 2001 14:06:13 -0400 (EDT) To: tlambert2@mindspring.com Cc: Luigi Rizzo , hackers@freebsd.org, wpaul@freebsd.org Subject: Re: any reason to use m_devget in the "dc" driver ? In-Reply-To: <3BAB7CFD.D5776F77@mindspring.com> References: <200109210703.JAA57756@info.iet.unipi.it> <15275.15530.678683.65377@grasshopper.cs.duke.edu> <3BAB7CFD.D5776F77@mindspring.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert writes: > Andrew Gallatin wrote: > > I imagine that this was done to follow alignment constraints on > > non-i386 platforms where having the ip header misaligned is fatal. > > (the tulip is not capable of byte granularity DMA, so you can't > > intentionally misalign the ethernet header & end up with an aligned IP > > header) > > This is the reason: the ethernet header is 14 bytes. > > > > I imagine the i386 should be made an exception. See rev 1.17 of > > sys/dev/nge/if_nge.c > > I disagree with this code; the elemenets in the header > are referenced multiple times. If you are doing the > checksum check, you might as well be relocating the data, > as well. The change I would make would be to integrate > the checksum calculation with the m_devget(), to ensure > a single pass, in the case that m_devget() must be used > to get aligned packet payload, and the checksum has not > been offloaded to hardware. Interesting idea... However, what if you're a bridge or a router? You've just done a whole lot of work for nothing. I imagine its just this case that Luigi cares about. If you want to integrate a checksum & a copy, it should really be done at the copyout() stage. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 11:30: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp011.mail.yahoo.com (smtp011.mail.yahoo.com [216.136.173.31]) by hub.freebsd.org (Postfix) with SMTP id 08E4437B41E for ; Fri, 21 Sep 2001 11:29:58 -0700 (PDT) Received: from mkc-65-31-219-45.kc.rr.com (HELO yahoo.com) (65.31.219.45) by smtp.mail.vip.sc5.yahoo.com with SMTP; 21 Sep 2001 18:20:57 -0000 X-Apparently-From: Message-ID: <3BAB8508.2010706@yahoo.com> Date: Fri, 21 Sep 2001 13:20:56 -0500 From: Jim Bryant Reply-To: kc5vdj@yahoo.com User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: Jason Andresen Cc: bmah@freebsd.org, Alfred Perlstein , Jordan Hubbard , kris@obsecurity.org, andrsn@andrsn.stanford.edu, freebsd-hackers@freebsd.org Subject: Re: No tools on 4.4-RELEASE ISO? References: <3BA9EEED.B7F0A194@mitre.org> <20010920223730.A82191@xor.obsecurity.org> <20010920234553S.jkh@freebsd.org> <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> <20010921095056.M61456@elvis.mu.org> <200109211518.f8LFITg54534@c527597-a.cstvl1.sfba.home.com> <3BAB6513.F6251E77@mitre.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jason Andresen wrote: > "Bruce A. Mah" wrote: > >>Note that the set of people affected is going to be "people who can't do >>anonymous FTP, don't have bootable CDROMs, and *only* have the ISO >>images to work with". I don't know for sure, but I'd expect this set to >>be pretty small...if they don't have Internet access, how'd they get the >>ISO images? >> > > Probably more often that you'd expect. I know I had to install 4.4 in > our lab (which blocks most net access) full of old machines. Fortunatly > I have a 4.3 ISO sitting here that I just grabbed fdimage from and > went on, but it did seem like a rather noticable oversight. > > What about the boot managers in that directory? Certainly people will > want > to dual boot their new FreeBSD installs? > > I've been in the same situation at a military site... Having the tools directory is very important. Many people also install freebsd on low-power old boxes, hell, we run our gateway/router/firewall at home on an old dell p-133 optiplex pizzabox we bought for $50, non-bootable cd-rom at that. We can just use dd to create the floppy, since it's running FreeBSD already for the task, but if someone had to start from scratch, the tool wouldn't be available. It may be a pain in the ass, especially after i've burned two copies of the distribution already, but i'll waste another handful of cd-r's to get something usable in every situation if new ISOs are made. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! ----------------------------------------------------- POWER TO THE PEOPLE! ----------------------------------------------------- "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 13: 3:47 2001 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 B114837B40B for ; Fri, 21 Sep 2001 13:03:41 -0700 (PDT) Received: from onyx (onyx.cs.binghamton.edu [128.226.140.171]) by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f8LK3eo10511 for ; Fri, 21 Sep 2001 16:03:40 -0400 (EDT) Date: Fri, 21 Sep 2001 16:03:25 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@onyx To: freebsd-hackers@freebsd.org Subject: Kernel module debugging help Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am using gdb a lot recently and find out that most of the bugs are memory related. I am wondering how to set up a hardware breakpoint which is triggered whenever a memory address is written again. I have no experience with this subject. Another minor question is how to set a static variable inside a function. Acoording the GDB manual, I should be able to say: (gdb) set function_name::my_static_variable = somevalue But it does not work. I am using 4.3-release on a PC. Thanks for your help. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 13:20: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mao.stokely.org (mao.stokely.org [65.84.64.228]) by hub.freebsd.org (Postfix) with ESMTP id 1CE0037B40E; Fri, 21 Sep 2001 13:20:01 -0700 (PDT) Received: by mao.stokely.org (Postfix, from userid 2074) id 842064B667; Fri, 21 Sep 2001 13:20:00 -0700 (PDT) Date: Fri, 21 Sep 2001 13:20:00 -0700 From: Murray Stokely To: Alfred Perlstein Cc: Jordan Hubbard , bmah@freebsd.org, kris@obsecurity.org, andrsn@andrsn.stanford.edu, jandrese@mitre.org, freebsd-hackers@freebsd.org Subject: Re: No tools on 4.4-RELEASE ISO? Message-ID: <20010921132000.G26542@windriver.com> References: <20010920234553S.jkh@freebsd.org> <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> <20010921095056.M61456@elvis.mu.org> <20010921094721N.jkh@freebsd.org> <20010921122731.D97903@elvis.mu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010921122731.D97903@elvis.mu.org>; from bright@mu.org on Fri, Sep 21, 2001 at 12:27:31PM -0500 X-GPG-Key-ID: 1024D/0E451F7D X-GPG-Key-Fingerprint: E2CA 411D DD44 53FD BB4B 3CB5 B4D7 10A2 0E45 1F7D Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 21, 2001 at 12:27:31PM -0500, Alfred Perlstein wrote: > Oh, I don't give a cr*p about ISO downloaders, I find them annoying. > People downloading ISO can find it, people trying to install from > pressed CDroms without net access might find it a bit more difficult. [ Picking a random message to reply to ] Yea. Just to confirm, the 4-CD sets going out from WRS will indeed have a 'tools' directory, I've emailed Brian from freebsd-services to make sure he's read this thread and remembers to add the Tools directory for their products as well. The tools directory is on the FTP site, it will be on the replicated CDs, and I really think that pushing up another ISO right now will get more complaints from hubs@ than the missing tools directory generated in the first place. =20 > As long as the media shipped out has the tools I'm fine. My concern > was some newbie getting a boxed set then hating life because he now > has another hurdle to leap to get FreeBSD installed. =20 Yea, I'm sure our tech support guys would have been swamped if they had to walk users through the usage of a hex editor or DEBUG.COM, to manually craft the floppies in DOS. ;) - Murray --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQE7q6DvtNcQog5FH30RAgLfAKCDS5KTI22/yBTu6Eyz7gntYCxm/gCgkXOU oq1nROhm7Lr7aa95hkdhT5o= =st0V -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 15:23:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id CF3B037B412; Fri, 21 Sep 2001 15:23:07 -0700 (PDT) Received: from hades.hell.gr (patr530-a125.otenet.gr [212.205.215.125]) by mailsrv.otenet.gr (8.11.5/8.11.5) with ESMTP id f8LMN1n20784; Sat, 22 Sep 2001 01:23:01 +0300 (EEST) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id f8LHSPm81397; Fri, 21 Sep 2001 20:28:26 +0300 (EEST) (envelope-from charon@labs.gr) Date: Fri, 21 Sep 2001 20:28:25 +0300 From: Giorgos Keramidas To: Jordan Hubbard Cc: kris@obsecurity.org, andrsn@andrsn.stanford.edu, jandrese@mitre.org, freebsd-hackers@FreeBSD.ORG Subject: Re: No tools on 4.4-RELEASE ISO? Message-ID: <20010921202824.B75838@hades.hell.gr> References: <3BA9EEED.B7F0A194@mitre.org> <20010920223730.A82191@xor.obsecurity.org> <20010920234553S.jkh@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010920234553S.jkh@freebsd.org> User-Agent: Mutt/1.3.22.1i X-GPG-Fingerprint: C1EB 0653 DB8B A557 3829 00F9 D60F 941A 3186 03B6 X-URL: http://labs.gr/~charon/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jordan Hubbard wrote: > > I seem to recall these programs were owned by WCCDROM (then BSDi, then > > Naw, I'd long since prunted tools/ to just the stuff that was freely > redistributable. Murray simply forgot to put it on the ISOs he > created. :) Does this mean the ISO's are soon to be rebuilt `with the tools/ directory'? -giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 15:56:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id C238937B413 for ; Fri, 21 Sep 2001 15:56:40 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f8LN4ol04157; Fri, 21 Sep 2001 16:04:56 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200109212304.f8LN4ol04157@mass.dis.org> To: Marco Wertejuk Cc: Jean-Christophe Varaillon , freebsd-hackers@FREEBSD.ORG Subject: Re: Boot proccess In-Reply-To: Message from Marco Wertejuk of "Thu, 20 Sep 2001 00:02:12 -0000." <20010920000212.B60704@localhost.com> Date: Fri, 21 Sep 2001 16:04:50 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Hello, > > | In short, which program gives enough knowledge to the microprocessor (?) > | and allow him to use kern.flp & mfsroot.flp in order to boot and make the > | operating system running. > > your BIOS reads the first sektor from your floppy which consists > of a boot loader, which usually loads the 2nd step boot loader > and this one loads the kernel. Not quite. The second stage bootstrap loads /boot/loader, which reads /boot/loader.rc, which is what causes the kernel and mfsroot to be loaded. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 21:12:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from heaven.gigo.com (gigo.com [207.173.11.186]) by hub.freebsd.org (Postfix) with ESMTP id 831FF37B412 for ; Fri, 21 Sep 2001 21:12:56 -0700 (PDT) Received: from 200.181.48.39 (unknown [200.181.48.39]) by heaven.gigo.com (Postfix) with ESMTP id 66F3AB85E for ; Fri, 21 Sep 2001 21:12:26 -0700 (PDT) Received: (qmail 44644 invoked by uid 1001); 22 Sep 2001 04:13:24 -0000 From: "Mario Sergio Fujikawa Ferreira" Date: Sat, 22 Sep 2001 01:13:02 -0300 To: freebsd-hackers@freebsd.org Subject: bug in shell `` expansion code? Message-ID: <20010922011302.A44620@exxodus.fedaykin.here> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, While working on a make .mk code, I and Chris Wasser (TDF on IRC) came across an interesting behavior: sh -c 'TDF="echo a && echo b";for i in `${TDF}`; do echo "i:$i"; done' This should return: i:a i:b instead, it returns: i:a i:&& i:echo i:b If this is not a bug, how do we get it working? Regards, -- Mario S F Ferreira - UnB - Brazil - "I guess this is a signature." lioux at ( freebsd dot org | linf dot unb dot br ) flames to beloved devnull@someotherworldbeloworabove.org feature, n: a documented bug | bug, n: an undocumented feature To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 21:14:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 3D52337B413 for ; Fri, 21 Sep 2001 21:14:04 -0700 (PDT) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id GAA64667; Sat, 22 Sep 2001 06:04:35 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200109220404.GAA64667@info.iet.unipi.it> Subject: Re: ipfw and dummynet In-Reply-To: <3BAA47DF.5924E6B6@lmco.com> from rick norman at "Sep 20, 2001 12:47:44 pm" To: rick norman Date: Sat, 22 Sep 2001 06:04:35 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, can you show me the output of ipfw show and ipfw pipe show Reading your questions, i have the feeling you are doing something wrong in the commands. For the last one, the client will keep generating its stream of data, it is just after going through the pipe that you will see the limitation in effect. cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone (510) 666 2927 . ----------------------------------+----------------------------------------- > I tried "questions" for this but no answer. > > I am attempting to use ipfw and dummynet to instrument some network > traffic tests. I am running freebsd 4.3 release and have built the > kernel > with ipfirewall, dummynet, and default to enabled. For a simple test, I > > added a pipe "ipfw add pipe 1 icmp from any to any". When I ping this > machine, I can do "ipfw pipe 1 show" and watch the counters increment, > but the machine doing the pinging does not see a response to the ping. > That's > my first question. Next, when I try to delete the pipe, "ipfw pipe 1 > delete", it > won't delete. The only way I can get rid of it is to do a flush. That's > > the second > question. Third question, if I type "ipfw pipe 1 config bw 10Bytes/s", > I would > expect the bw to be limited and the counters to reflect this limit. The > > counters > indicate no change in the 64 byte/s generated by my windows client. > > I have read the man pages for ipfw, dummynet, and ipfirewall. If these > are > obvious questions, I would appreciate a pointer to a good reference. > > Thanks > > > > -- > > Logically speaking, logic is not the answer. > > Rick Norman > rick.norman@lmco.com > 408 742 1619 > > > > 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 Sep 21 21:25:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.bmi.net (smtp.bmi.net [204.57.191.31]) by hub.freebsd.org (Postfix) with ESMTP id E408337B403 for ; Fri, 21 Sep 2001 21:25:43 -0700 (PDT) Received: from johncoop.MSHOME (drumheller-router.bmi.net [206.63.201.3] (may be forged)) by smtp.bmi.net (Pro-8.9.3/Pro-8.9.3) with ESMTP id EAA15191; Sat, 22 Sep 2001 04:32:46 -0700 Date: Fri, 21 Sep 2001 21:25:30 -0700 From: John Merryweather Cooper To: Mario Sergio Fujikawa Ferreira Cc: freebsd-hackers@freebsd.org Subject: Re: bug in shell `` expansion code? Message-ID: <20010921212530.G24650@johncoop.MSHOME> References: <20010922011302.A44620@exxodus.fedaykin.here> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: <20010922011302.A44620@exxodus.fedaykin.here>; from lioux@uol.com.br on Fri, Sep 21, 2001 at 21:13:02 -0700 X-Mailer: Balsa 1.2.0 Lines: 51 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2001.09.21 21:13 Mario Sergio Fujikawa Ferreira wrote: > Hi, > > While working on a make .mk code, I and Chris Wasser (TDF > on IRC) came across an interesting behavior: > > sh -c 'TDF="echo a && echo b";for i in `${TDF}`; do echo "i:$i"; done' > > This should return: > > i:a > i:b > > instead, it returns: > > i:a > i:&& > i:echo > i:b > > If this is not a bug, how do we get it working? > > Regards, > > -- > Mario S F Ferreira - UnB - Brazil - "I guess this is a signature." > lioux at ( freebsd dot org | linf dot unb dot br ) > flames to beloved devnull@someotherworldbeloworabove.org > feature, n: a documented bug | bug, n: an undocumented feature > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > This works: $ sh -c 'TDF="echo a && echo b";for i in `eval ${TDF}`; do echo "i:$i"; done' I believe eval is necessary in this context, otherwise the && is not "evaluated." I checked, and the same behavior holds if sh is changed to bash. -- jmc MacroHard -- the perfection of form over substance, marketing over performance, and greed over design . . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 21:31:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id C090237B401 for ; Fri, 21 Sep 2001 21:31:06 -0700 (PDT) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id WAA39315; Fri, 21 Sep 2001 22:15:19 -0700 (PDT) Message-ID: <3BAC12E1.6D87CB57@elischer.org> Date: Fri, 21 Sep 2001 21:26:09 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Mario Sergio Fujikawa Ferreira Cc: freebsd-hackers@freebsd.org Subject: Re: bug in shell `` expansion code? References: <20010922011302.A44620@exxodus.fedaykin.here> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mario Sergio Fujikawa Ferreira wrote: > > Hi, > > While working on a make .mk code, I and Chris Wasser (TDF > on IRC) came across an interesting behavior: > > sh -c 'TDF="echo a && echo b";for i in `${TDF}`; do echo "i:$i"; done' > > This should return: > > i:a > i:b > > instead, it returns: > > i:a > i:&& > i:echo > i:b > > If this is not a bug, how do we get it working? try: julian@jules:sh -c 'TDF="echo a && echo b";for i in `eval ${TDF}`; do echo "i:$i"; done' i:a i:b the trouble is that TDF is interpretted as a single string including spaces where you want to interpret is as a list of separate words > > Regards, > > -- > Mario S F Ferreira - UnB - Brazil - "I guess this is a signature." > lioux at ( freebsd dot org | linf dot unb dot br ) > flames to beloved devnull@someotherworldbeloworabove.org > feature, n: a documented bug | bug, n: an undocumented feature > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 21:44:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2out.giga.net.tw (mail2out.giga.net.tw [203.133.1.11]) by hub.freebsd.org (Postfix) with ESMTP id B341737B406 for ; Fri, 21 Sep 2001 21:44:15 -0700 (PDT) Received: from index (u24-164.u203-203.giga.net.tw [203.203.24.164]) by mail2out.giga.net.tw (Postfix) with SMTP id DD52B14268 for ; Sat, 22 Sep 2001 12:44:08 +0800 (CST) To: From: gd168@24k.com.tw Subject: Àô«O¹p®gºÒ¯»§X±MÃD¬ã¨s³ø§i Date: ¬P´Á¤», 22 ¤E¤ë 2001 12:42:13 +0800 Message-Id: <37156.529322800928000.74271@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ¨ü¤åªÌ¡G§e¡@°ê¥ß¥xÆW¤j¾Çº[©ÒÄݦæ¬F¾Ç³N¬ã¨s³æ¦ì¡þ ¡@¡@¡@¡@¡@¡@¥þ°ê¦U¯Å¾÷Ãö¹ÎÅé¡þ¤½¥q¦æ¸¹¡þ¤½·|©Î­Ó¤H¡@½Ðų®Ö¡I µo¤åªÌ¡G¥øÀs¿ì¤½¥Î«~¦³­­¤½¥q¡@¹q¸Ü¡G(02)2701-2000 ¥D¡@¦®¡G¨Ï¥Î¡eÀô«O¹p®gºÒ¯»§X¡f¤§ÀuÂI¤Î±ÄÁÊ­nÂI¡C »¡¡@©ú¡GÀô«O¹p®gºÒ¯»§X¤§±MÃD¬ã¨s³ø§i ¡]¤@¡^«e¨¥ ¡@¡@¡@¡@¡@ªñ¦~¨Ó¡A¥Ñ©ó¦U¶µ¬ÛÃö§Þ³N¦¨¼ô¡A°t¦X¥b¾ÉÅé²£·~ÁO«kµo®i ¡@¡@¡@¨Ï±o¹p®g¦Lªí¾÷»ù®æ¤j´T¤U·Æ¡A¦U¼t°ÓµL¤£À£§C»ù®æ¡A¥HÂX¤j¥« ¡@¡@¡@³õ¦û¦³²v¡A¦A¥H«áÄòªº¯Ó§÷ÁȦ^¨ä§Q¼í¡A±zªá¦bºÒ¯»§Xªº¶O¥Î¡A ¡@¡@¡@ªø´Á¦Ó¨¥¹ê¦b¬O¤@µ§¥iÆ[ªº¤ä¥X¡C ¡@¡@¡@¡@¡@¡@¡@¡@¡e¨Ï¥ÎÀô«O¹p®gºÒ¯»§X¤§¤T¤j²z¥Ñ¡f ¡@¡@¡@¡@ (1)§Þ³N¤W¤w¬ð¯}¡G¦³Å²©óºÒ¯»§X©M¾¥¤ô§X»Ý¨D¶q¤£Â_¦¨ªø¡A ¡@¡@¡@°ê¤H¤­¦~«e¶}©lµÛ¤â¡A°w¹ï¹p®g¦Lªí¾÷¹q¤l¼g¯u§Þ³N¤ÎºÒ¯»·P¥ú ¡@¡@¡@Åé¡A¶i¦æ¬ÛÃö¬ãµo¤u§@¡A¬ãµo¤p²Õ¦¨­û¬Ò¬°³ÕºÓ¤h¾Ç¾ú¡A¬ãµo¤p ¡@¡@¡@²Õ¦¨­û°w¹ï¦U¤j¼tµP¾÷¾¹ºë±Kµ²ºc¡A¤w¦³²`«×¤F¸Ñ¡A´x´¤³\¦h¬Û ¡@¡@¡@Ãö§Þ³N¡A¹ïºÒ¯»§Xªº§÷®Æ¤Î»sµ{°Ñ¼Æ¦³­Y¤z§ï¶i¡A¥H¾AÀ³¥xÆW¨È ¡@¡@¡@¼ö±a°ª·Å¼éÀ㪺®ð­ÔÀô¹Ò¡A¸gÄY®æ«~ºÞ±±¨î¡A°ê¤H©Ò¥Í²£ªºÀô«O ¡@¡@¡@¹p®gºÒ¯»§X¡A¦C¦L«~½è©M­ì¼t¦P¼Ë²M´·¡A¥B¤£·|¶Ë®`¾÷¾¹¡C ¡@¡@¡@¡@ (2)¬°Àô«OºÉ¤ß¤O¡GºÒ¯»§X³y¦¨¹ïÀô¹Òªº¦Ã¬V»P¤é­Ñ¼W¡A¤HÃþ ¡@¡@¡@À³¤Ï¬Ùı®©¡A§Ú­Ì¥u¦³¤@­Ó¦a²y¡A¬°¥þ¤HÃþ¤Î«á¥N¤l®]¡A«O¯d¤@ ¡@¡@¡@­Ó°®²bªº¥Í¦sÀô¹Ò¡A¤w¨ì¨è¤£®e½wªº¦a¨B¡IÅý§Ú­Ì±q®Õ¶é°µ°_¡A ¡@¡@¡@¤@°_¨Ó¦^¦¬¨Ã¨Ï¥ÎÀô«O¹p®gºÒ¯»§X¡C ¡@¡@¡@¡@ (3)¸`¬Ù¦C¦L¶O¥Î¡G®Ú¾Ú¤u°Ó®É³ø 90¦~4¤ë12¤é³ø¾É«ü¥X¡A¥Î ¡@¡@¡@Àô«O¹p®gºÒ¯»§X¥i¸`¬Ù¢³¦¨¥ª¥kªº¶O¥Î¡A¤£¥²¦hªá¿ú¡C ¡]¤G¡^¥þ²yÁͶդÀªR ¡@¡@¡@¡@¡@1999¦~ºÒ¯»¥d§X¦A¥Í¦^¦¬¨Ï¥Î¤ñ¸û¡G ¡@¡@¡@¼Ú¬ü¥«³õ¦A¥Í¦^¦¬¥d§X¨Ï¥Î²v ¢²¢¯¢H (¬ù1/3) ¡@¡@¡@¥xÆW¥«³õ¦A¥Í¦^¦¬¥d§X¨Ï¥Î²v ¡@¢´¢H ¡@¡@¡@(¸ê®Æ¨Ó·½¡GRecharger´Á¥Z) ¡@¡@¡@¡@¡@¥xÆW¬ù¦³50¸U¥x¹p®g¦Lªí¾÷¡A¹w¦ô¨C¦~¨Ï¥Î¬ù100¡ã200¸U¤ä ¡@¡@¡@¹p®gºÒ¯»§X¡A»s³y¥X¬ù2000¡ã2500¤½¾·©TÅé¼o±óª«¡A¨Ã¥B¨C¦~³o ¡@¡@¡@­Ó¼Æ¥Ø¥¿¦b¦¨ªø¡C¦Ó³o¨Ç¶ì½¦¼o±óª«¶·­n¶W¹L¤Q­Ó¥@¬ö¨Ó¤À¸Ñ¡A ¡@¡@¡@¹ï¥xÆW¤T¸U¤»¤d¥­¤è¤½¨½ªº¤g¦a¤W¡A³y¦¨ÄY­«ªº­t²ü¡C ¡@¡@¡@¡@¡@¼Ú¬ü¦U°ê¬ÛÃöÀô«Oªk¥O±j¨î³W©w»s³y¼t°Óªº¦^¦¬¤ñ²v¡A¤w¦æ ¡@¡@¡@¤§¦h¦~¡A¹ï©ó¦^¦¬·~ªÌ¤]¦³¹ïÀ³ªº»²§U¬Fµ¦¡A¨Ã¤£Â_ªº±Ð¨|¨Ï¥Î ¡@¡@¡@ªÌ¦^¦¬¡B´î¶q¦A§Q¥Î(Recycle, Reduce, Reuse)ªºÆ[©À¡C ¡@¡@¡@¡@¡@¨Æ¹êÃÒ©ú¡A¦¹Á|¤£¶È¦³§U©óÀô«O¥B¯à­°§C¤ä¥X¡A¬ü°ê¤w©ú¥O ¡@¡@¡@Áp¨¹¬F©²ªº¦U³æ¦ì¥²¶·¨Ï¥ÎÀô«OºÒ¯»§X¡C ¡]¤T¡^¹ïÀô¹Ò«OÅ@¤Î¸ê·½¦^¦¬¦A§Q¥Î¡A¨ã¦³¥¿­±·N¸q ¡@¡@¡@¡@¡@¡@¦pªG»s³y¨C­Ó¥d§X»Ý­n¶W¹L¤T¦j²æªo¡A¨º»ò¥xÆW¨C¦~´N·| ¡@¡@¡@¥Î±¼ªñ100 ¸U¥[±[ªº¥Ûªo¡C¦pªG±z´«¶RÀô«OºÒ¯»§X¡A«Ü©ú½T¦a¡A ¡@¡@¡@±z¤w¸g¹ï«OÅ@Àô¹Ò°µ¥X°^Äm¤F¡A¦]¬°§Ú­Ìªº§£§£³õ¥i¥H´î¤Ö¤@­Ó ¡@¡@¡@ªÅ¶¡¨Ó¦s©ñ±zªº¥d§X¡C ¡@¡@¡@¡@¡@¥H¥xÆW¥Ø«e¨Ï¥Î¶q·U¨Ó·U¦hªº¹p®g¦Lªí¾÷¦Ó¨¥¡A¨C¤Ñ¥á±óªº ¡@¡@¡@ºÒ¯»§X¤£ª¾¦h¤Ö¡A¦Ó³o¨ÇºÒ¯»§X¸ÌªººÒ¯»¦â¾¯·L²É¡A¤Ø¤o¬ù6-12 ¡@¡@¡@·L¦Ì¡A«o·|º¯¤J¦a¤U¤ô¡A¦Ã¬V¤ô·½¡A­Y·Q±q¤ô¤¤°£¥h³o¨ÇºÒ¯»·L ¡@¡@¡@²É¡A´N¥²¶·¥[¸Ë¯S®íÂo¤ô³]³Æ¡A¦]¦¹µL½×¤½¥q¥ø·~©Î¾Ç®Õ¤Î­Ó¤H ¡@¡@¡@³£¦³³d¥ô¤@°_¨Ó¨¾¤îºÒ¯»§X¦Ã¬VÀô¹Òªº¤u§@¡AºÒ¯»§Xªº¦^¦¬¦A§Q ¡@¡@¡@¥Î¡A¬O¥Ø«eªº°ß¤@³~®|¡C ¡]¥|¡^Àô«OºÒ¯»§X¤§±ÄÁÊ­nÂI ¡@¡@¡@¡@¡@¥Ñ©ó¥«°âÀô«OºÒ¯»§X¡A¨ÑÀ³°Ó¹L¦h¡A¦U®aªº«~½è°Ñ®t¤£»ô¡A ¡@¡@¡@·q½Ð»{©ú¥øÀs¥N²zªºÀô«OºÒ¯»§X¡A¬°¥Ø«e¥xÆW°ß¤@±M·~¾É¦V¤§Àô ¡@¡@¡@«O¹p®gºÒ¯»§X¡A«~½èº¡·N«OÃÒ¡A¤£º¡¥]°h¡A½T«O®ø¶OÅv¯q¡AÁקK ¡@¡@¡@¶R¨ì¦H½è«~¡A¿ï¾Ü¥øÀs¡A«~½è¦³«O»Ù¡I ¡@¡@¡@±ÄÁÊ«e°È¥²¸ß°Ý¤U¦C­«­n°Ñ¦Ò¨Ì¾Ú¡G ¡@¡@¡@1.Àô«O¹p®gºÒ¯»§X¡A¬O§_§¹¥þ¥H¼Ð·Ç»sµ{»s³y¡H¡@»sµ{¤¤¡A¼oºÒ ¡@¡@¡@¡@¯»¼Ñ¤Î¬ÛÃö¹s¥ó¬O§_²M²z°®²b¨ÃÀ˸դ¸¥ó©Ê¯à¡H ¡@¡@¡@2.Àx¯»¼Ñ¬O§_§¹¥þ²M¼ä°®²b«á¡A¤~­«·s¸Ë¶ñ¥þ·sºÒ¯»¡H ¡@¡@¡@3.©Ò¥R¶ñ¤§ºÒ¯»¡A¬O§_¬°°ê»Ú¶¡ª¾¦WºÒ¯»¼t¥X«~¡H ¡@¡@¡@4.©Ò¦³Àx¯»¼Ñ¡A¬O§_¥H«Ê±ø±K«Ê¡A§¹¾ã¥æ¥I¨Ï¥Î¤H¡H ¡@¡@¡@5.ºÒ¯»§X¬O§_³q¹L§¹¾ã¦ÓÄY®æ«~ºÞ´ú¸Õ«á¤~¥X¼t¡H ¡@¡@¡@6.´ú¸Õ¥Î¤§ºÒ¯»¬O§_¬°¥~¥[¡H¡@©Ò¥R¶ñªººÒ¯»¼Æ¶q©M­ì¼tºÒ¯»§X ¡@¡@¡@¡@®e¶q¬O§_¬Û¦P¡A·|¤£·|µu¤Ö¡H ¡@¡@¡@7.¥R¶ñ¤§ºÒ¯»¬O§_¸g¹Lºë±K´ú¸Õ¡A½T»{¤ñ¼Ð·Ç­È°ª¤~¸Ë¶ñ¡H ¡@¡@¡@8.©Ò§ó´«¤§·P¥ú¹ª¬O§_¬°°ê»Ú¶¡ª¾¦W¤§°ª¬ì§Þ¼tµP²£«~¡H ¡@¡@¡@9.ºÒ¯»§X¦¨«~¬O§_¥H¶Â¦â¶ì½¦¯È¹ê¬IÁ×¥ú¥]¸Ë«á¡A¨Ã¥H®ðªw³U©Î ¡@¡@¡@¡@¯S®íŨ¹Ô«OÅ@¡A¦A¸Ë¤J«OÅ@¼Ñ¡A¥H½T«O¹B¿é³~¤¤¤D¦Ü¨Ï¥Î«e¡A ¡@¡@¡@¡@¤£¨ü¥ô¦ó¥ú½u¨ä¥Lª«²z©Ê¡A¤Æ¾Ç©Ê¶Ë®`¡H ¡@¡@¡@¡@¥øÀs¥N²zªºÀô«O¹p®gºÒ¯»§X·~¤w¥þ¼Æ³q¹L¤W­z´ú¸Õ¡A¥þ­±¹ê¬I ¡@¡@¡@¡@«~½èº¡·N«OÃÒ¦A­qÁÊ¡A¤£º¡·N«OÃÒ°h³f¡I ¡]¤­¡^»ù®æ¸ê°T¡GÀô«O¹p®gºÒ¯»§X¤§»ù®æ¤w¤½¥¬©óºô¯¸¡AÅwªï¤Wºô¬d¸ß ¡@¡@¡@¡@¡@¡@¡@¡@ºô§}¡Ghttp://clik.to/96969180 ¡]¤»¡^Ápµ¸¸ê°T¡G¥H¤W¸ê®Æ¥Ñ¥øÀs¿ì¤½¥Î«~¦³­­¤½¥q©Ò´£¨Ñ¡A¦p»Ý­qÁÊ ¡@¡@¡@¡@¡@¡@¡@¡@½Ð¹q¡G(02)2701-2000§Ú­Ì¼ö¸Ûªº¦P¤¯¬°±zªA°È¡C To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 21:48:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2out.giga.net.tw (mail2out.giga.net.tw [203.133.1.11]) by hub.freebsd.org (Postfix) with ESMTP id D05AC37B417 for ; Fri, 21 Sep 2001 21:47:56 -0700 (PDT) Received: from index (u24-164.u203-203.giga.net.tw [203.203.24.164]) by mail2out.giga.net.tw (Postfix) with SMTP id 760CA146E0 for ; Sat, 22 Sep 2001 12:47:54 +0800 (CST) To: From: gd168@24k.com.tw Subject: Àô«O¹p®gºÒ¯»§X±MÃD¬ã¨s³ø§i Date: ¬P´Á¤», 22 ¤E¤ë 2001 12:45:59 +0800 Message-Id: <37156.531932986112000.95313@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ¨ü¤åªÌ¡G§e¡@°ê¥ß¥xÆW¤j¾Çº[©ÒÄݦæ¬F¾Ç³N¬ã¨s³æ¦ì¡þ ¡@¡@¡@¡@¡@¡@¥þ°ê¦U¯Å¾÷Ãö¹ÎÅé¡þ¤½¥q¦æ¸¹¡þ¤½·|©Î­Ó¤H¡@½Ðų®Ö¡I µo¤åªÌ¡G¥øÀs¿ì¤½¥Î«~¦³­­¤½¥q¡@¹q¸Ü¡G(02)2701-2000 ¥D¡@¦®¡G¨Ï¥Î¡eÀô«O¹p®gºÒ¯»§X¡f¤§ÀuÂI¤Î±ÄÁÊ­nÂI¡C »¡¡@©ú¡GÀô«O¹p®gºÒ¯»§X¤§±MÃD¬ã¨s³ø§i ¡]¤@¡^«e¨¥ ¡@¡@¡@¡@¡@ªñ¦~¨Ó¡A¥Ñ©ó¦U¶µ¬ÛÃö§Þ³N¦¨¼ô¡A°t¦X¥b¾ÉÅé²£·~ÁO«kµo®i ¡@¡@¡@¨Ï±o¹p®g¦Lªí¾÷»ù®æ¤j´T¤U·Æ¡A¦U¼t°ÓµL¤£À£§C»ù®æ¡A¥HÂX¤j¥« ¡@¡@¡@³õ¦û¦³²v¡A¦A¥H«áÄòªº¯Ó§÷ÁȦ^¨ä§Q¼í¡A±zªá¦bºÒ¯»§Xªº¶O¥Î¡A ¡@¡@¡@ªø´Á¦Ó¨¥¹ê¦b¬O¤@µ§¥iÆ[ªº¤ä¥X¡C ¡@¡@¡@¡@¡@¡@¡@¡@¡e¨Ï¥ÎÀô«O¹p®gºÒ¯»§X¤§¤T¤j²z¥Ñ¡f ¡@¡@¡@¡@ (1)§Þ³N¤W¤w¬ð¯}¡G¦³Å²©óºÒ¯»§X©M¾¥¤ô§X»Ý¨D¶q¤£Â_¦¨ªø¡A ¡@¡@¡@°ê¤H¤­¦~«e¶}©lµÛ¤â¡A°w¹ï¹p®g¦Lªí¾÷¹q¤l¼g¯u§Þ³N¤ÎºÒ¯»·P¥ú ¡@¡@¡@Åé¡A¶i¦æ¬ÛÃö¬ãµo¤u§@¡A¬ãµo¤p²Õ¦¨­û¬Ò¬°³ÕºÓ¤h¾Ç¾ú¡A¬ãµo¤p ¡@¡@¡@²Õ¦¨­û°w¹ï¦U¤j¼tµP¾÷¾¹ºë±Kµ²ºc¡A¤w¦³²`«×¤F¸Ñ¡A´x´¤³\¦h¬Û ¡@¡@¡@Ãö§Þ³N¡A¹ïºÒ¯»§Xªº§÷®Æ¤Î»sµ{°Ñ¼Æ¦³­Y¤z§ï¶i¡A¥H¾AÀ³¥xÆW¨È ¡@¡@¡@¼ö±a°ª·Å¼éÀ㪺®ð­ÔÀô¹Ò¡A¸gÄY®æ«~ºÞ±±¨î¡A°ê¤H©Ò¥Í²£ªºÀô«O ¡@¡@¡@¹p®gºÒ¯»§X¡A¦C¦L«~½è©M­ì¼t¦P¼Ë²M´·¡A¥B¤£·|¶Ë®`¾÷¾¹¡C ¡@¡@¡@¡@ (2)¬°Àô«OºÉ¤ß¤O¡GºÒ¯»§X³y¦¨¹ïÀô¹Òªº¦Ã¬V»P¤é­Ñ¼W¡A¤HÃþ ¡@¡@¡@À³¤Ï¬Ùı®©¡A§Ú­Ì¥u¦³¤@­Ó¦a²y¡A¬°¥þ¤HÃþ¤Î«á¥N¤l®]¡A«O¯d¤@ ¡@¡@¡@­Ó°®²bªº¥Í¦sÀô¹Ò¡A¤w¨ì¨è¤£®e½wªº¦a¨B¡IÅý§Ú­Ì±q®Õ¶é°µ°_¡A ¡@¡@¡@¤@°_¨Ó¦^¦¬¨Ã¨Ï¥ÎÀô«O¹p®gºÒ¯»§X¡C ¡@¡@¡@¡@ (3)¸`¬Ù¦C¦L¶O¥Î¡G®Ú¾Ú¤u°Ó®É³ø 90¦~4¤ë12¤é³ø¾É«ü¥X¡A¥Î ¡@¡@¡@Àô«O¹p®gºÒ¯»§X¥i¸`¬Ù¢³¦¨¥ª¥kªº¶O¥Î¡A¤£¥²¦hªá¿ú¡C ¡]¤G¡^¥þ²yÁͶդÀªR ¡@¡@¡@¡@¡@1999¦~ºÒ¯»¥d§X¦A¥Í¦^¦¬¨Ï¥Î¤ñ¸û¡G ¡@¡@¡@¼Ú¬ü¥«³õ¦A¥Í¦^¦¬¥d§X¨Ï¥Î²v ¢²¢¯¢H (¬ù1/3) ¡@¡@¡@¥xÆW¥«³õ¦A¥Í¦^¦¬¥d§X¨Ï¥Î²v ¡@¢´¢H ¡@¡@¡@(¸ê®Æ¨Ó·½¡GRecharger´Á¥Z) ¡@¡@¡@¡@¡@¥xÆW¬ù¦³50¸U¥x¹p®g¦Lªí¾÷¡A¹w¦ô¨C¦~¨Ï¥Î¬ù100¡ã200¸U¤ä ¡@¡@¡@¹p®gºÒ¯»§X¡A»s³y¥X¬ù2000¡ã2500¤½¾·©TÅé¼o±óª«¡A¨Ã¥B¨C¦~³o ¡@¡@¡@­Ó¼Æ¥Ø¥¿¦b¦¨ªø¡C¦Ó³o¨Ç¶ì½¦¼o±óª«¶·­n¶W¹L¤Q­Ó¥@¬ö¨Ó¤À¸Ñ¡A ¡@¡@¡@¹ï¥xÆW¤T¸U¤»¤d¥­¤è¤½¨½ªº¤g¦a¤W¡A³y¦¨ÄY­«ªº­t²ü¡C ¡@¡@¡@¡@¡@¼Ú¬ü¦U°ê¬ÛÃöÀô«Oªk¥O±j¨î³W©w»s³y¼t°Óªº¦^¦¬¤ñ²v¡A¤w¦æ ¡@¡@¡@¤§¦h¦~¡A¹ï©ó¦^¦¬·~ªÌ¤]¦³¹ïÀ³ªº»²§U¬Fµ¦¡A¨Ã¤£Â_ªº±Ð¨|¨Ï¥Î ¡@¡@¡@ªÌ¦^¦¬¡B´î¶q¦A§Q¥Î(Recycle, Reduce, Reuse)ªºÆ[©À¡C ¡@¡@¡@¡@¡@¨Æ¹êÃÒ©ú¡A¦¹Á|¤£¶È¦³§U©óÀô«O¥B¯à­°§C¤ä¥X¡A¬ü°ê¤w©ú¥O ¡@¡@¡@Áp¨¹¬F©²ªº¦U³æ¦ì¥²¶·¨Ï¥ÎÀô«OºÒ¯»§X¡C ¡]¤T¡^¹ïÀô¹Ò«OÅ@¤Î¸ê·½¦^¦¬¦A§Q¥Î¡A¨ã¦³¥¿­±·N¸q ¡@¡@¡@¡@¡@¡@¦pªG»s³y¨C­Ó¥d§X»Ý­n¶W¹L¤T¦j²æªo¡A¨º»ò¥xÆW¨C¦~´N·| ¡@¡@¡@¥Î±¼ªñ100 ¸U¥[±[ªº¥Ûªo¡C¦pªG±z´«¶RÀô«OºÒ¯»§X¡A«Ü©ú½T¦a¡A ¡@¡@¡@±z¤w¸g¹ï«OÅ@Àô¹Ò°µ¥X°^Äm¤F¡A¦]¬°§Ú­Ìªº§£§£³õ¥i¥H´î¤Ö¤@­Ó ¡@¡@¡@ªÅ¶¡¨Ó¦s©ñ±zªº¥d§X¡C ¡@¡@¡@¡@¡@¥H¥xÆW¥Ø«e¨Ï¥Î¶q·U¨Ó·U¦hªº¹p®g¦Lªí¾÷¦Ó¨¥¡A¨C¤Ñ¥á±óªº ¡@¡@¡@ºÒ¯»§X¤£ª¾¦h¤Ö¡A¦Ó³o¨ÇºÒ¯»§X¸ÌªººÒ¯»¦â¾¯·L²É¡A¤Ø¤o¬ù6-12 ¡@¡@¡@·L¦Ì¡A«o·|º¯¤J¦a¤U¤ô¡A¦Ã¬V¤ô·½¡A­Y·Q±q¤ô¤¤°£¥h³o¨ÇºÒ¯»·L ¡@¡@¡@²É¡A´N¥²¶·¥[¸Ë¯S®íÂo¤ô³]³Æ¡A¦]¦¹µL½×¤½¥q¥ø·~©Î¾Ç®Õ¤Î­Ó¤H ¡@¡@¡@³£¦³³d¥ô¤@°_¨Ó¨¾¤îºÒ¯»§X¦Ã¬VÀô¹Òªº¤u§@¡AºÒ¯»§Xªº¦^¦¬¦A§Q ¡@¡@¡@¥Î¡A¬O¥Ø«eªº°ß¤@³~®|¡C ¡]¥|¡^Àô«OºÒ¯»§X¤§±ÄÁÊ­nÂI ¡@¡@¡@¡@¡@¥Ñ©ó¥«°âÀô«OºÒ¯»§X¡A¨ÑÀ³°Ó¹L¦h¡A¦U®aªº«~½è°Ñ®t¤£»ô¡A ¡@¡@¡@·q½Ð»{©ú¥øÀs¥N²zªºÀô«OºÒ¯»§X¡A¬°¥Ø«e¥xÆW°ß¤@±M·~¾É¦V¤§Àô ¡@¡@¡@«O¹p®gºÒ¯»§X¡A«~½èº¡·N«OÃÒ¡A¤£º¡¥]°h¡A½T«O®ø¶OÅv¯q¡AÁקK ¡@¡@¡@¶R¨ì¦H½è«~¡A¿ï¾Ü¥øÀs¡A«~½è¦³«O»Ù¡I ¡@¡@¡@±ÄÁÊ«e°È¥²¸ß°Ý¤U¦C­«­n°Ñ¦Ò¨Ì¾Ú¡G ¡@¡@¡@1.Àô«O¹p®gºÒ¯»§X¡A¬O§_§¹¥þ¥H¼Ð·Ç»sµ{»s³y¡H¡@»sµ{¤¤¡A¼oºÒ ¡@¡@¡@¡@¯»¼Ñ¤Î¬ÛÃö¹s¥ó¬O§_²M²z°®²b¨ÃÀ˸դ¸¥ó©Ê¯à¡H ¡@¡@¡@2.Àx¯»¼Ñ¬O§_§¹¥þ²M¼ä°®²b«á¡A¤~­«·s¸Ë¶ñ¥þ·sºÒ¯»¡H ¡@¡@¡@3.©Ò¥R¶ñ¤§ºÒ¯»¡A¬O§_¬°°ê»Ú¶¡ª¾¦WºÒ¯»¼t¥X«~¡H ¡@¡@¡@4.©Ò¦³Àx¯»¼Ñ¡A¬O§_¥H«Ê±ø±K«Ê¡A§¹¾ã¥æ¥I¨Ï¥Î¤H¡H ¡@¡@¡@5.ºÒ¯»§X¬O§_³q¹L§¹¾ã¦ÓÄY®æ«~ºÞ´ú¸Õ«á¤~¥X¼t¡H ¡@¡@¡@6.´ú¸Õ¥Î¤§ºÒ¯»¬O§_¬°¥~¥[¡H¡@©Ò¥R¶ñªººÒ¯»¼Æ¶q©M­ì¼tºÒ¯»§X ¡@¡@¡@¡@®e¶q¬O§_¬Û¦P¡A·|¤£·|µu¤Ö¡H ¡@¡@¡@7.¥R¶ñ¤§ºÒ¯»¬O§_¸g¹Lºë±K´ú¸Õ¡A½T»{¤ñ¼Ð·Ç­È°ª¤~¸Ë¶ñ¡H ¡@¡@¡@8.©Ò§ó´«¤§·P¥ú¹ª¬O§_¬°°ê»Ú¶¡ª¾¦W¤§°ª¬ì§Þ¼tµP²£«~¡H ¡@¡@¡@9.ºÒ¯»§X¦¨«~¬O§_¥H¶Â¦â¶ì½¦¯È¹ê¬IÁ×¥ú¥]¸Ë«á¡A¨Ã¥H®ðªw³U©Î ¡@¡@¡@¡@¯S®íŨ¹Ô«OÅ@¡A¦A¸Ë¤J«OÅ@¼Ñ¡A¥H½T«O¹B¿é³~¤¤¤D¦Ü¨Ï¥Î«e¡A ¡@¡@¡@¡@¤£¨ü¥ô¦ó¥ú½u¨ä¥Lª«²z©Ê¡A¤Æ¾Ç©Ê¶Ë®`¡H ¡@¡@¡@¡@¥øÀs¥N²zªºÀô«O¹p®gºÒ¯»§X·~¤w¥þ¼Æ³q¹L¤W­z´ú¸Õ¡A¥þ­±¹ê¬I ¡@¡@¡@¡@«~½èº¡·N«OÃÒ¦A­qÁÊ¡A¤£º¡·N«OÃÒ°h³f¡I ¡]¤­¡^»ù®æ¸ê°T¡GÀô«O¹p®gºÒ¯»§X¤§»ù®æ¤w¤½¥¬©óºô¯¸¡AÅwªï¤Wºô¬d¸ß ¡@¡@¡@¡@¡@¡@¡@¡@ºô§}¡Ghttp://clik.to/96969180 ¡]¤»¡^Ápµ¸¸ê°T¡G¥H¤W¸ê®Æ¥Ñ¥øÀs¿ì¤½¥Î«~¦³­­¤½¥q©Ò´£¨Ñ¡A¦p»Ý­qÁÊ ¡@¡@¡@¡@¡@¡@¡@¡@½Ð¹q¡G(02)2701-2000§Ú­Ì¼ö¸Ûªº¦P¤¯¬°±zªA°È¡C To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 23: 0:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from robin.mail.pas.earthlink.net (robin.mail.pas.earthlink.net [207.217.120.65]) by hub.freebsd.org (Postfix) with ESMTP id 9745D37B41D; Fri, 21 Sep 2001 23:00:14 -0700 (PDT) Received: from mindspring.com (dialup-209.245.141.15.Dial1.SanJose1.Level3.net [209.245.141.15]) by robin.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f8M604H04015; Fri, 21 Sep 2001 23:00:04 -0700 (PDT) Message-ID: <3BAC2910.90CE4265@mindspring.com> Date: Fri, 21 Sep 2001 23:00:48 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: Luigi Rizzo , hackers@freebsd.org, wpaul@freebsd.org Subject: Re: any reason to use m_devget in the "dc" driver ? References: <200109210703.JAA57756@info.iet.unipi.it> <15275.15530.678683.65377@grasshopper.cs.duke.edu> <3BAB7CFD.D5776F77@mindspring.com> <15275.33173.594275.19570@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andrew Gallatin wrote: > > I disagree with this code; the elemenets in the header > > are referenced multiple times. If you are doing the > > checksum check, you might as well be relocating the data, > > as well. The change I would make would be to integrate > > the checksum calculation with the m_devget(), to ensure > > a single pass, in the case that m_devget() must be used > > to get aligned packet payload, and the checksum has not > > been offloaded to hardware. > > Interesting idea... However, what if you're a bridge or a router? > You've just done a whole lot of work for nothing. I imagine its just > this case that Luigi cares about. > > If you want to integrate a checksum & a copy, it should really be done > at the copyout() stage. You're missing the point. You do the m_devget() only when you decide to do a checksum, which means you've decided to handle the packet yourself. The alignment is done via a copy of the header field; specifically, a byte copy of the protocol type, when you decide how to handle it. In the case of the bridge, it's very easy: you don't care about the contents of the packet, unless it's destined for you. For a router, you are operating above layer 2, so you _do_ care, and must hterefore do the checksum to be correct (since you should not reference the field contents without knowledge that the checksum is correct). The Cisco approach of ignoring the checksums is all well and good, if the work is being done in hardware, but for most software, it very definitely cares (it's more overhead to relay bad packets onto your network, even if you assume it's OK for a router to do that). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 23: 8: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id D84A037B5AF; Fri, 21 Sep 2001 23:07:50 -0700 (PDT) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id HAA64949; Sat, 22 Sep 2001 07:58:25 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200109220558.HAA64949@info.iet.unipi.it> Subject: Re: any reason to use m_devget in the "dc" driver ? In-Reply-To: <3BAC2910.90CE4265@mindspring.com> from Terry Lambert at "Sep 21, 2001 11:00:48 pm" To: tlambert2@mindspring.com Date: Sat, 22 Sep 2001 07:58:25 +0200 (CEST) Cc: Andrew Gallatin , hackers@freebsd.org, wpaul@freebsd.org 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I probably missed some emails ? In any case i was only concerned about the additional copy done by m_devget when the controller can already DMA into an mbuf, and there are no alignment constraints. cheers luigi > Andrew Gallatin wrote: > > > I disagree with this code; the elemenets in the header > > > are referenced multiple times. If you are doing the > > > checksum check, you might as well be relocating the data, > > > as well. The change I would make would be to integrate > > > the checksum calculation with the m_devget(), to ensure > > > a single pass, in the case that m_devget() must be used > > > to get aligned packet payload, and the checksum has not > > > been offloaded to hardware. > > > > Interesting idea... However, what if you're a bridge or a router? > > You've just done a whole lot of work for nothing. I imagine its just > > this case that Luigi cares about. > > > > If you want to integrate a checksum & a copy, it should really be done > > at the copyout() stage. > > You're missing the point. You do the m_devget() only when > you decide to do a checksum, which means you've decided to handle > the packet yourself. The alignment is done via a copy of the > header field; specifically, a byte copy of the protocol type, > when you decide how to handle it. > > In the case of the bridge, it's very easy: you don't care about > the contents of the packet, unless it's destined for you. For > a router, you are operating above layer 2, so you _do_ care, > and must hterefore do the checksum to be correct (since you > should not reference the field contents without knowledge that > the checksum is correct). The Cisco approach of ignoring the > checksums is all well and good, if the work is being done in > hardware, but for most software, it very definitely cares (it's > more overhead to relay bad packets onto your network, even if > you assume it's OK for a router to do that). > > -- Terry > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 21 23:15:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ipperformance.com (ipperf.com [206.225.36.162]) by hub.freebsd.org (Postfix) with ESMTP id DBED837B41F for ; Fri, 21 Sep 2001 23:15:36 -0700 (PDT) Received: from ipperformance.com (cs6668163-239.austin.rr.com [66.68.163.239]) by ipperformance.com (8.9.3/8.9.3) with SMTP id BAA14750; Sat, 22 Sep 2001 01:15:34 -0500 (CDT) (envelope-from matt@ipperformance.com) Message-ID: <3BAC2B4E.47E32A07@ipperformance.com> Date: Sat, 22 Sep 2001 01:10:22 -0500 From: Matt Finlay X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Mario Sergio Fujikawa Ferreira Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: bug in shell `` expansion code? References: <20010922011302.A44620@exxodus.fedaykin.here> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mario Sergio Fujikawa Ferreira wrote: > Hi, > > While working on a make .mk code, I and Chris Wasser (TDF > on IRC) came across an interesting behavior: > > sh -c 'TDF="echo a && echo b";for i in `${TDF}`; do echo "i:$i"; done' > i do not believe this is a bug... it is the way the bash shell executes commands. this is what is happening: first TDF gets set to "echo a && echo b", when you get to the for statement... `${TDF}` causes "echo a && echo b"(TDF) to be executed. however instead of executing the way you are intending it actually executes echo "a && echo b"... this value get stored back into TDF. so that is why you are getting the output i:a i:&& i:echo i:b > > This should return: > > i:a > i:b > > instead, it returns: > > i:a > i:&& > i:echo > i:b > > If this is not a bug, how do we get it working? > > Regards, > > -- > Mario S F Ferreira - UnB - Brazil - "I guess this is a signature." > lioux at ( freebsd dot org | linf dot unb dot br ) > flames to beloved devnull@someotherworldbeloworabove.org > feature, n: a documented bug | bug, n: an undocumented feature > > 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 Sep 21 23:59:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.121.50]) by hub.freebsd.org (Postfix) with ESMTP id 8A95237B41F; Fri, 21 Sep 2001 23:59:30 -0700 (PDT) Received: from dialup-209.245.141.15.dial1.sanjose1.level3.net ([209.245.141.15] helo=mindspring.com) by avocet.mail.pas.earthlink.net with esmtp (Exim 3.32 #2) id 15kgl4-0003XK-00; Fri, 21 Sep 2001 23:59:27 -0700 Message-ID: <3BAC36F4.1B9E8E2E@mindspring.com> Date: Sat, 22 Sep 2001 00:00:04 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Luigi Rizzo Cc: Andrew Gallatin , hackers@freebsd.org, wpaul@freebsd.org Subject: Re: any reason to use m_devget in the "dc" driver ? References: <200109220558.HAA64949@info.iet.unipi.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Luigi Rizzo wrote: > > I probably missed some emails ? > In any case i was only concerned about the additional copy > done by m_devget when the controller can already DMA into > an mbuf, and there are no alignment constraints. I guess we are talking about a protocol other than IP? The ethernet header is 14 bytes in length, which means that the elements in the IP header are not longword aligned, unless the card can DMA onto a 2 byte boundary, and does so, to ensure that the IP header starts on a 16 byte boundary, and therefore the contents are correctly aligned for direct reference in a single bus cycle (or at all, on Alpha, where unaligned access is not permitted). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 22 0:40:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from reservoir.absolight.com (reservoir.absolight.com [212.43.217.72]) by hub.freebsd.org (Postfix) with ESMTP id 3D25137B422 for ; Sat, 22 Sep 2001 00:40:33 -0700 (PDT) Received: from bilbo.in.mat.cc (bilbo.in.mat.cc [212.43.217.121]) by reservoir.absolight.com (Postfix) with ESMTP id 78EA0D3AE6 for ; Sat, 22 Sep 2001 09:40:25 +0200 (CEST) Received: from bilbo.org (localhost [127.0.0.1]) by bilbo.in.mat.cc (Postfix) with ESMTP id 66F7F65554 for ; Sat, 22 Sep 2001 09:40:23 +0200 (CEST) Received: from club-internet.fr (sauron.in.mat.cc [212.43.217.122]) by bilbo.in.mat.cc (Postfix) with ESMTP id BA32065554 for ; Sat, 22 Sep 2001 09:39:41 +0200 (CEST) Message-ID: <3BAC403D.A89893D3@club-internet.fr> Date: Sat, 22 Sep 2001 09:39:41 +0200 From: Mathieu Arnold Organization: http://www.absolight.com/ X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd hackers Subject: MALLOC_DEFINE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi I'm having memory problems using ipfilter. I have a lot of rules, and a lot of traffic, here is what i have from time to time : IP states added: 9469918 TCP 1654588 UDP 1451233 ICMP 2869559782 hits 100258517 misses 0 maximum 72605 no memory 2915 bkts in use 9766 active 3099381 expired 9393987 closed and that, because ipfilter uses the temp memory zone, which is used by many other kernel stuff, and sometime gets full. in ip_state.h, I found : # ifdef M_PFIL # define KMALLOC(a, b) MALLOC((a), b, sizeof(*(a)), M_PFIL, M_NOWAIT) # define KMALLOCS(a, b, c) MALLOC((a), b, (c), M_PFIL, M_NOWAIT) # define KFREE(x) FREE((x), M_PFIL) # define KFREES(x,s) FREE((x), M_PFIL) # else # define KMALLOC(a, b) MALLOC((a), b, sizeof(*(a)), M_TEMP, M_NOWAIT) # define KMALLOCS(a, b, c) MALLOC((a), b, (c), M_TEMP, M_NOWAIT) # define KFREE(x) FREE((x), M_TEMP) # define KFREES(x,s) FREE((x), M_TEMP) # endif /* M_PFIL */ I was wondering if it was possible to add some MALLOC_DEFINE(M_PFIL, "ipfilter", "some bigger description"); or static MALLOC_DEFINE(M_PFIL, "ipfilter", "some bigger description"); but I do not know where to put it, neither which one to use, as both are used in the kernel source tree. Some help would really be appreciated. ps: FreeBSD mano.absolight.com 4.3-RELEASE-p19 FreeBSD 4.3-RELEASE-p19 #2: Fri Sep 14 20:09:37 CEST 2001 -- Mathieu Arnold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 22 1:36:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kuku.excite.com (kuku-rwcmta.excite.com [198.3.99.63]) by hub.freebsd.org (Postfix) with ESMTP id C291E37B410 for ; Sat, 22 Sep 2001 01:36:56 -0700 (PDT) Received: from swirly ([199.172.153.107]) by kuku.excite.com (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP id <20010922083656.ZSSZ22472.kuku.excite.com@swirly> for ; Sat, 22 Sep 2001 01:36:56 -0700 Message-ID: <15935111.1001147816474.JavaMail.imail@swirly> Date: Sat, 22 Sep 2001 01:36:45 -0700 (PDT) From: john_wilson100@excite.com To: freebsd-hackers@freebsd.org Subject: FreeBSD tar and large files (> 2Gb) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Excite Inbox X-Sender-Ip: 62.90.91.30 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I thought this was solved *years* ago: depot:~$ ls -l streets.* -rw-r--r-- 1 john john 2501946753 Sep 22 10:37 streets.dbf depot:~$ tar czvf streets.tgz streets.dbf streets.dbf depot:~$ ls -l streets.tgz -rw-r--r-- 1 john john 129 Sep 22 11:20 streets.tgz depot:~$ tar tzvf streets.tgz -rw-r--r-- john/john -1793020543 Sep 22 10:37 2001 streets.dbf I'm running FreeBSD 4.4-RC (built Sep 12) John _______________________________________________________ Send a cool gift with your E-Card http://www.bluemountain.com/giftcenter/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 22 5: 8:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id B50AA37B418 for ; Sat, 22 Sep 2001 05:08:41 -0700 (PDT) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id PDD14653; Sat, 22 Sep 2001 15:08:11 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.11.6/8.11.6) id f8MBsQ602932; Sat, 22 Sep 2001 14:54:26 +0300 (EEST) (envelope-from netch) Date: Sat, 22 Sep 2001 14:54:26 +0300 From: Valentin Nechayev To: Matt Dillon Cc: Alfred Perlstein , hackers@FreeBSD.ORG Subject: Re: bug in sshd - signal during free() Message-ID: <20010922145426.A686@iv.nn.kiev.ua> References: <200109172032.f8HKW6M41638@earth.backplane.com> <20010917160103.Z968@elvis.mu.org> <200109172104.f8HL45641959@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200109172104.f8HL45641959@earth.backplane.com>; from dillon@earth.backplane.com on Mon, Sep 17, 2001 at 02:04:05PM -0700 X-42: On Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mon, Sep 17, 2001 at 14:04:05, dillon (Matt Dillon) wrote about "Re: bug in sshd - signal during free()": > It's funny... they had an XXX comment in there so obviously someone > was a little jittery about it. I think they just didn't realize that > a malloc() might occur inside the signal handler or they would have > fixed it long ago. Have they real reason to do regeneration in signal handler, instead of interrupting a wait and using a notification variable? I cannot imagine such reason. > UNIX signals suck. - I hate cats! They smells, their hair flies everywhere! - Oh, dear, you simply should study how to cook them better. (sorry for possible translation stones) /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 22 6:57:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from buffoon.automagic.org (buffoon.automagic.org [208.185.30.208]) by hub.freebsd.org (Postfix) with SMTP id DE33137B41C for ; Sat, 22 Sep 2001 06:57:44 -0700 (PDT) Received: (qmail 23491 invoked by uid 1000); 22 Sep 2001 13:57:37 -0000 Date: Sat, 22 Sep 2001 09:57:37 -0400 From: Joe Abley To: Olafur Osvaldsson Cc: Alfred Perlstein , "Bruce A. Mah" , Jordan Hubbard , kris@obsecurity.org, andrsn@andrsn.stanford.edu, jandrese@mitre.org, freebsd-hackers@FreeBSD.ORG Subject: Re: No tools on 4.4-RELEASE ISO? Message-ID: <20010922095737.V4205@buffoon.automagic.org> References: <3BA9EEED.B7F0A194@mitre.org> <20010920223730.A82191@xor.obsecurity.org> <20010920234553S.jkh@freebsd.org> <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> <20010921095056.M61456@elvis.mu.org> <200109211518.f8LFITg54534@c527597-a.cstvl1.sfba.home.com> <20010921103916.A97903@elvis.mu.org> <20010921154456.C29490@isnic.is> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010921154456.C29490@isnic.is> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Sep 21, 2001 at 03:44:56PM +0000, Olafur Osvaldsson wrote: > > On Fri, 21 Sep 2001, Alfred Perlstein wrote: > > > Wouldn't it be trivial to just mount the ISO, tar copy it, add the > > files then rerun mkisofs? > > > > This would result in all mirrors re-downloading the image wich is not such a > big deal except now there are a minimum of 5 users downloading the image at > any given time wich locks the file so it won't get updated unless the admin > disconnects the users and then the user can't resume the download and can't > start again untill the mirror site has finished downloading the image from the > master wich in some cases takes hours. Surely most mirror scripts pull down new content to a temporary file with no general read privs, then atomically mv that temporary file to the name of the updated file? Similarly on the master ftp server. I see no locking issues, or need to disconnect anybody. The only issue is that some people will have versions of the ISO without tools. Producing a new "with-tools" ISO sounds like a needless waste of mirror operators' disk :) Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 22 7:16: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nollie.summersault.com (nollie.summersault.com [208.10.44.140]) by hub.freebsd.org (Postfix) with SMTP id C271A37B41E for ; Sat, 22 Sep 2001 07:15:54 -0700 (PDT) Received: (qmail 30190 invoked by uid 1001); 22 Sep 2001 14:15:54 -0000 Date: Sat, 22 Sep 2001 09:15:54 -0500 (EST) From: Chris Hardie To: freebsd-hackers@freebsd.org, Subject: net.inet.ip.fw.one_pass=0 not effective in filtering bridge? Message-ID: X-Request-PGP: http://www.summersault.com/chris/me/pgp-pubring.txt MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi. I've got a filtering bridge running on FreeBSD 4.3 with ipfw and a customized rc.firewall config. The setup has been working well for a while now. I was unfortunately alerted to a hole after a box behind the firewall was cracked because ports that I thought were protected...weren't. It turns out that traffic to/from the machine in question was being passed through a pipe early in the rc.firewall config, and that the ipfw processing terminated when the packets came out of the pipe, so they never saw the rules farther down that would have dropped those packets headed for bad places. A-ha! "Easy" you say - just do sysctl -w net.inet.ip.fw.one_pass=0 and according to the ipfw man page, that will cause the packets to be re-injected into the firewall when they come out of the pipe, starting where they left off. Well, this just doesn't seem to be taking effect! I've crawled through docs and mailing lists. Setting net.inet.ip.fw.one_pass seems to be the common solution, but a few other people have mentioned the same ineffectiveness of that, and then those threads just drop off. So I'm wondering if it's possible that, because the kernel is compiled with "options BRIDGE", that packets are strictly only going through the firewall rules once, and that net.inet.ip.fw.one_pass=0 isn't having an effect in this case? If my wondering is in error, I'm looking for suggestions about how to verify the behavior I'm seeing and how to achieve the desired result: to use pipes AND deny rules that come after. I'm happy to send along the particular rules, but wanted to see if the question could be answered using theory first. (This message addresses an issue similar to but separate from the "ipfw" thread on freebsd-questions started by Rick Norman on Sep 18. I also posted this message there.) Any help is much appreciated. Thanks, Chris -- Chris Hardie ----------------------------- ----- mailto:chris@summersault.com ---------- -------- http://www.summersault.com/chris/ -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 22 8:17:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 1D23E37B41C; Sat, 22 Sep 2001 08:17:50 -0700 (PDT) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id RAA66779; Sat, 22 Sep 2001 17:08:20 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200109221508.RAA66779@info.iet.unipi.it> Subject: Re: net.inet.ip.fw.one_pass=0 not effective in filtering bridge? In-Reply-To: from Chris Hardie at "Sep 22, 2001 09:15:54 am" To: Chris Hardie Date: Sat, 22 Sep 2001 17:08:20 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-ipfw@FreeBSD.ORG 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG in fact one_pass does not work with bridging, it might be as simple as changing one line in bridge.c if (ip_fw_chk_ptr && bdg_ipfw != 0 && src != NULL) { struct ip *ip ; int i; - if (rule != NULL) /* dummynet packet, already partially processed */ + if (rule != NULL && fw_one_pass) goto forward; /* HACK! I should obey the fw_one_pass */ but i never had a chance to test it. If you want to give this a try, I'd be glad to know how it works. cheers luigi > Hi. I've got a filtering bridge running on FreeBSD 4.3 with ipfw and > a customized rc.firewall config. The setup has been working well for > a while now. I was unfortunately alerted to a hole after a box behind > the firewall was cracked because ports that I thought were > protected...weren't. > > It turns out that traffic to/from the machine in question was being > passed through a pipe early in the rc.firewall config, and that the > ipfw processing terminated when the packets came out of the pipe, so > they never saw the rules farther down that would have dropped those > packets headed for bad places. > > A-ha! "Easy" you say - just do > sysctl -w net.inet.ip.fw.one_pass=0 > and according to the ipfw man page, that will cause the packets to be > re-injected into the firewall when they come out of the pipe, starting > where they left off. Well, this just doesn't seem to be taking > effect! > > I've crawled through docs and mailing lists. Setting > net.inet.ip.fw.one_pass seems to be the common solution, but a few > other people have mentioned the same ineffectiveness of that, and then > those threads just drop off. So I'm wondering if it's possible that, > because the kernel is compiled with "options BRIDGE", that packets are > strictly only going through the firewall rules once, and that > net.inet.ip.fw.one_pass=0 isn't having an effect in this case? > > If my wondering is in error, I'm looking for suggestions about how to > verify the behavior I'm seeing and how to achieve the desired result: to > use pipes AND deny rules that come after. I'm happy to send along the > particular rules, but wanted to see if the question could be answered > using theory first. > > (This message addresses an issue similar to but separate from the "ipfw" > thread on freebsd-questions started by Rick Norman on Sep 18. I also > posted this message there.) > > Any help is much appreciated. > > Thanks, > Chris > > -- Chris Hardie ----------------------------- > ----- mailto:chris@summersault.com ---------- > -------- http://www.summersault.com/chris/ -- > > > > 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 Sat Sep 22 8:58:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nollie.summersault.com (nollie.summersault.com [208.10.44.140]) by hub.freebsd.org (Postfix) with SMTP id 54F5637B43A for ; Sat, 22 Sep 2001 08:58:29 -0700 (PDT) Received: (qmail 34812 invoked by uid 1001); 22 Sep 2001 15:58:28 -0000 Date: Sat, 22 Sep 2001 10:58:28 -0500 (EST) From: Chris Hardie To: Luigi Rizzo Cc: freebsd-hackers@FreeBSD.ORG, , Subject: Re: net.inet.ip.fw.one_pass=0 not effective in filtering bridge? In-Reply-To: <200109221508.RAA66779@info.iet.unipi.it> Message-ID: X-Request-PGP: http://www.summersault.com/chris/me/pgp-pubring.txt MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Luigi, I don't currently have a box I can experiment with, but I'll try to put something together. Do you have a sense of how "risky" your proposed change is? :) In any case, I might recommend an update to the dummynet(4) man page that clarifies this behavior. These two excerpts: "When acting as a bridge, the ipfw filter is invoked only once, in the in- put path, for bridged packets." AND "Depending on the setting of the sysctl variable `net.inet.ip.fw.one_pass', packets coming from a pipe can be either forwarded to their destination, or passed again through the ipfw rules, starting from the one after the matching rule." could probably be more proximal to each other, and/or you could explicitly state that the sysctl variable has no effect in current bridging. I see that you've done this on your ip_dummynet section of your personal website: "NOTE: there is always one pass for bridged packets." It may also be useful to explicitly state this in the Filtering Bridges article by Nick Sayer: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/filtering-bridges/filtering-bridges-ipfirewall.html My concern is that typical users won't read or test closely enough to know this, and will assume that their dummynet bridges are working the way I thought mine was. Thanks, Chris On Sat, 22 Sep 2001, Luigi Rizzo wrote: > in fact one_pass does not work with bridging, > it might be as simple as changing one line in bridge.c > > if (ip_fw_chk_ptr && bdg_ipfw != 0 && src != NULL) { > struct ip *ip ; > int i; > > - if (rule != NULL) /* dummynet packet, already partially processed */ > + if (rule != NULL && fw_one_pass) > goto forward; /* HACK! I should obey the fw_one_pass */ > > but i never had a chance to test it. > If you want to give this a try, I'd be glad to know how it works. > > cheers > luigi > > > Hi. I've got a filtering bridge running on FreeBSD 4.3 with ipfw and > > a customized rc.firewall config. The setup has been working well for > > a while now. I was unfortunately alerted to a hole after a box behind > > the firewall was cracked because ports that I thought were > > protected...weren't. > > > > It turns out that traffic to/from the machine in question was being > > passed through a pipe early in the rc.firewall config, and that the > > ipfw processing terminated when the packets came out of the pipe, so > > they never saw the rules farther down that would have dropped those > > packets headed for bad places. > > > > A-ha! "Easy" you say - just do > > sysctl -w net.inet.ip.fw.one_pass=0 > > and according to the ipfw man page, that will cause the packets to be > > re-injected into the firewall when they come out of the pipe, starting > > where they left off. Well, this just doesn't seem to be taking > > effect! > > > > I've crawled through docs and mailing lists. Setting > > net.inet.ip.fw.one_pass seems to be the common solution, but a few > > other people have mentioned the same ineffectiveness of that, and then > > those threads just drop off. So I'm wondering if it's possible that, > > because the kernel is compiled with "options BRIDGE", that packets are > > strictly only going through the firewall rules once, and that > > net.inet.ip.fw.one_pass=0 isn't having an effect in this case? > > > > If my wondering is in error, I'm looking for suggestions about how to > > verify the behavior I'm seeing and how to achieve the desired result: to > > use pipes AND deny rules that come after. I'm happy to send along the > > particular rules, but wanted to see if the question could be answered > > using theory first. > > > > (This message addresses an issue similar to but separate from the "ipfw" > > thread on freebsd-questions started by Rick Norman on Sep 18. I also > > posted this message there.) > > > > Any help is much appreciated. > > > > Thanks, > > Chris > > > > -- Chris Hardie ----------------------------- > > ----- mailto:chris@summersault.com ---------- > > -------- http://www.summersault.com/chris/ -- > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 22 11:53: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 7E61A37B40F; Sat, 22 Sep 2001 11:53:02 -0700 (PDT) Subject: Re: any reason to use m_devget in the "dc" driver ? In-Reply-To: <200109220558.HAA64949@info.iet.unipi.it> from Luigi Rizzo at "Sep 22, 2001 07:58:25 am" To: luigi@info.iet.unipi.it (Luigi Rizzo) Date: Sat, 22 Sep 2001 11:53:02 -0700 (PDT) Cc: gallatin@cs.duke.edu, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20010922185302.7E61A37B40F@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I probably missed some emails ? And you can't go back and read them from the archives because...? > In any case i was only concerned about the additional copy > done by m_devget when the controller can already DMA into > an mbuf, and there are no alignment constraints. I don't know what you're talking about. There are no cases where we use m_devget() when there *aren't* any alignment constraints. Show us exactly what line of code you're talking about please, otherwise drop this topic, because it's been discussed to death and I'm tired of somebody trying to argue it with me every few months. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 22 13:23:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 55EDD37B418 for ; Sat, 22 Sep 2001 13:23:25 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f8MKMpU81911; Sat, 22 Sep 2001 13:22:51 -0700 (PDT) (envelope-from dillon) Date: Sat, 22 Sep 2001 13:22:51 -0700 (PDT) From: Matt Dillon Message-Id: <200109222022.f8MKMpU81911@earth.backplane.com> To: Seigo Tanimura , phk@critter.freebsd.dk, tanimura@r.dl.itc.u-tokyo.ac.jp, bright@wintelcom.net Cc: hackers@freebsd.org Subject: More on the cache_purgeleafdirs() routine References: <200104161024.f3GAO7Z34787@rina.r.dl.itc.u-tokyo.ac.jp> <1198.987417363@critter> <200104161223.f3GCNZZ51680@rina.r.dl.itc.u-tokyo.ac.jp> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi guys. I've been tracking down issues with vnode recycling.. specifically, getnewvnode() deadlocks in -stable in large-memory configurations. I took a real good look at cache_purgeleafdirs() in -current to see if it was MFCable as a solution. But.... There are a number of issues... well, there is really one big issue, and that is the simple fact that there can be upwards of 260,000+ entries in the name cache and cache_purgeleafdirs() doesn't scale. It is an O(N*M) algorithm. Any system that requires a great deal of vnode recycling -- for example Yahoo's userbase lookup (one file per userid) would be terribly impacted by this algorithm. It seems to me that the best way to deal with this is to simply have getnewvnode() zap the namei-cache, and have vfs_lookup() requeue (for LRU purposes) any namei cache associated vnodes that are on the freelist. The patch is much less complex... here's is a preliminary patch (without the LRU requeueing, I haven't gotten to that yet, and I haven't completely removed the non-scaleable recycling code). This code seems to work quite well even without the LRU requeueing, especialy if you turn on vfs.vmiodirenable. I don't see any reason to be totally rabid about keeping top level directory entries in-core... at least not at the cost of the current algorithm in -current. We want to try to keep them in core, but I believe that LRU requeueing in vfs_lookup() may be sufficient for that... or possibly even something as simple as a flag in the namei caching structure that guarentees the first N directory levels are left in-core. Or something like that. But not a complete scan of the namei cache! -Matt Index: kern/vfs_cache.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_cache.c,v retrieving revision 1.61 diff -u -r1.61 vfs_cache.c --- kern/vfs_cache.c 2001/09/12 08:37:46 1.61 +++ kern/vfs_cache.c 2001/09/22 20:13:47 @@ -101,8 +101,10 @@ SYSCTL_ULONG(_debug, OID_AUTO, numcache, CTLFLAG_RD, &numcache, 0, ""); static u_long numcachehv; /* number of cache entries with vnodes held */ SYSCTL_ULONG(_debug, OID_AUTO, numcachehv, CTLFLAG_RD, &numcachehv, 0, ""); +#if 0 static u_long numcachepl; /* number of cache purge for leaf entries */ SYSCTL_ULONG(_debug, OID_AUTO, numcachepl, CTLFLAG_RD, &numcachepl, 0, ""); +#endif struct nchstats nchstats; /* cache effectiveness statistics */ static int doingcache = 1; /* 1 => enable the cache */ @@ -476,6 +478,20 @@ } /* + * Flush the namei cache references associated with a vnode. + * The vnode remains valid. + */ +void +cache_flush(vp) + struct vnode *vp; +{ + while (!LIST_EMPTY(&vp->v_cache_src)) + cache_zap(LIST_FIRST(&vp->v_cache_src)); + while (!TAILQ_EMPTY(&vp->v_cache_dst)) + cache_zap(TAILQ_FIRST(&vp->v_cache_dst)); +} + +/* * Flush all entries referencing a particular filesystem. * * Since we need to check it anyway, we will flush all the invalid @@ -499,6 +515,8 @@ } } +#if 0 + /* * Flush all dirctory entries with no child directories held in * the cache. @@ -554,6 +572,8 @@ } numcachepl++; } + +#endif /* * Perform canonical checks and cache lookup and pass on to filesystem Index: kern/vfs_subr.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_subr.c,v retrieving revision 1.319 diff -u -r1.319 vfs_subr.c --- kern/vfs_subr.c 2001/09/12 08:37:47 1.319 +++ kern/vfs_subr.c 2001/09/22 20:15:11 @@ -110,6 +110,8 @@ /* Number of vnodes in the free list. */ static u_long freevnodes = 0; SYSCTL_LONG(_debug, OID_AUTO, freevnodes, CTLFLAG_RD, &freevnodes, 0, ""); + +#if 0 /* Number of vnode allocation. */ static u_long vnodeallocs = 0; SYSCTL_LONG(_debug, OID_AUTO, vnodeallocs, CTLFLAG_RD, &vnodeallocs, 0, ""); @@ -125,6 +127,7 @@ /* Number of vnodes attempted to recycle at a time. */ static u_long vnoderecyclenumber = 3000; SYSCTL_LONG(_debug, OID_AUTO, vnoderecyclenumber, CTLFLAG_RW, &vnoderecyclenumber, 0, ""); +#endif /* * Various variables used for debugging the new implementation of @@ -556,8 +559,13 @@ * Don't recycle if active in the namecache or * if it still has cached pages or we cannot get * its interlock. + * + * XXX the namei cache can hold onto vnodes too long, + * causing us to run out of MALLOC space. Instead, we + * should make path lookups requeue any vnodes on the free + * list. */ - if (LIST_FIRST(&vp->v_cache_src) != NULL || + if (/* LIST_FIRST(&vp->v_cache_src) != NULL || */ (VOP_GETVOBJECT(vp, &object) == 0 && (object->resident_page_count || object->ref_count)) || !mtx_trylock(&vp->v_interlock)) { @@ -636,6 +644,7 @@ vfs_object_create(vp, td, td->td_proc->p_ucred); +#if 0 vnodeallocs++; if (vnodeallocs % vnoderecycleperiod == 0 && freevnodes < vnoderecycleminfreevn && @@ -643,6 +652,7 @@ /* Recycle vnodes. */ cache_purgeleafdirs(vnoderecyclenumber); } +#endif return (0); } Index: sys/vnode.h =================================================================== RCS file: /home/ncvs/src/sys/sys/vnode.h,v retrieving revision 1.157 diff -u -r1.157 vnode.h --- sys/vnode.h 2001/09/13 22:52:42 1.157 +++ sys/vnode.h 2001/09/22 20:18:45 @@ -558,8 +558,8 @@ int cache_lookup __P((struct vnode *dvp, struct vnode **vpp, struct componentname *cnp)); void cache_purge __P((struct vnode *vp)); +void cache_flush __P((struct vnode *vp)); void cache_purgevfs __P((struct mount *mp)); -void cache_purgeleafdirs __P((int ndir)); void cvtstat __P((struct stat *st, struct ostat *ost)); void cvtnstat __P((struct stat *sb, struct nstat *nsb)); int getnewvnode __P((enum vtagtype tag, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 22 13:44:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 77E0537B426 for ; Sat, 22 Sep 2001 13:44:32 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.4/8.11.4) with ESMTP id f8MKhZv88903; Sat, 22 Sep 2001 22:43:35 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matt Dillon Cc: Seigo Tanimura , bright@wintelcom.net, hackers@freebsd.org Subject: Re: More on the cache_purgeleafdirs() routine In-Reply-To: Your message of "Sat, 22 Sep 2001 13:22:51 PDT." <200109222022.f8MKMpU81911@earth.backplane.com> Date: Sat, 22 Sep 2001 22:43:35 +0200 Message-ID: <88901.1001191415@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200109222022.f8MKMpU81911@earth.backplane.com>, Matt Dillon writes: > > There are a number of issues... well, there is really one big issue, and > that is the simple fact that there can be upwards of 260,000+ entries > in the name cache and cache_purgeleafdirs() doesn't scale. It is an > O(N*M) algorithm. I agree, I've never been too fond of the purgeleafdirs() code myself for that reason and others. If we disregard the purgeleafdirs() workaround, the current cache code was built around the assumption that VM page reclaims would be enough to keep the vnode cache flushed and any vnode which could be potentially useful was kept around until it wasn't. Your patch changes this to the opposite: we kill vnodes as soon as possible, and pick them off the freelist next time we hit them, if they survice that long. I think that more or less neuters the vfs cache for anything but open files, which I think is not in general an optimal solution either. I still lean towards finding a dynamic limit on the number of vnodes and have the cache operation act accordingly as the least generally lousy algorithm we can employ. Either way, I think that we should not replace the current code with a new algorithm until we have some solid data for it, it is a complex interrelationship and some serious benchmarking is needed before we can know what to do. In particular we need to know: What ratio of directories are reused as a function of the number of children they have in the cache. What ratio of files are reused as a function of them being open or not. What ratio of files are being reused as a function of the number of pages they have in-core. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 22 14:21:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 8EE6737B42A for ; Sat, 22 Sep 2001 14:21:24 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f8MLLHe82202; Sat, 22 Sep 2001 14:21:17 -0700 (PDT) (envelope-from dillon) Date: Sat, 22 Sep 2001 14:21:17 -0700 (PDT) From: Matt Dillon Message-Id: <200109222121.f8MLLHe82202@earth.backplane.com> To: Poul-Henning Kamp Cc: Seigo Tanimura , bright@wintelcom.net, hackers@freebsd.org Subject: Re: More on the cache_purgeleafdirs() routine References: <88901.1001191415@critter> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :I agree, I've never been too fond of the purgeleafdirs() code myself :for that reason and others. : :If we disregard the purgeleafdirs() workaround, the current cache code :was built around the assumption that VM page reclaims would be enough :to keep the vnode cache flushed and any vnode which could be potentially :useful was kept around until it wasn't. : :Your patch changes this to the opposite: we kill vnodes as soon as :possible, and pick them off the freelist next time we hit them, :if they survice that long. : :I think that more or less neuters the vfs cache for anything but :open files, which I think is not in general an optimal solution :either. : :I still lean towards finding a dynamic limit on the number of vnodes :and have the cache operation act accordingly as the least generally :lousy algorithm we can employ. : :Either way, I think that we should not replace the current code with :a new algorithm until we have some solid data for it, it is a complex :interrelationship and some serious benchmarking is needed before we :can know what to do. : :In particular we need to know: : : What ratio of directories are reused as a function of : the number of children they have in the cache. : : What ratio of files are reused as a function of them : being open or not. : : What ratio of files are being reused as a function of : the number of pages they have in-core. : :-- :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 :phk@FreeBSD.ORG | TCP/IP since RFC 956 Well, wait a sec... all I do is zap the namei cache for the vnode. The check to see if the vnode's object still has resident pages is still in there so I don't quite understand how I turned things around. In my tests it appears to cache vnodes as long as there are resident pages associated with them. We could also throw a flag into the namei structure for a sub-directory count and only blow leaf nodes - which would be roughly equivalent to what the existing code does except without the overhead. But I don't think it is necessary. In regards to directory reuse... well, if you thought it was complex before consider how complex it is now with the ufs dirhash code. Still, the core of directory caching is still the buffer cache and if vfs.vmiodirenable is turned on, it becomes the VM Page cache which is already fairly optimal. This alone will prevent actively used directories from being blown out. And, in fact, in the tests I've done so far the system still merrily caches tens of thousands of vnodes while doing a 'tar cf /dev/null /'. I'm setting up a postfix test too. As far as I can tell, my changes have had no effect on namei cache efficiency other then eating less cpu. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 22 14:39:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id DF82637B414 for ; Sat, 22 Sep 2001 14:39:44 -0700 (PDT) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id f8MLJZ730278; Sat, 22 Sep 2001 14:19:35 -0700 (PDT) (envelope-from dg) Date: Sat, 22 Sep 2001 14:19:34 -0700 From: David Greenman To: Matt Dillon Cc: Poul-Henning Kamp , Seigo Tanimura , bright@wintelcom.net, hackers@freebsd.org Subject: Re: More on the cache_purgeleafdirs() routine Message-ID: <20010922141934.C28469@nexus.root.com> References: <88901.1001191415@critter> <200109222121.f8MLLHe82202@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200109222121.f8MLLHe82202@earth.backplane.com>; from dillon@earth.backplane.com on Sat, Sep 22, 2001 at 02:21:17PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Well, wait a sec... all I do is zap the namei cache for the vnode. The > check to see if the vnode's object still has resident pages is still in > there so I don't quite understand how I turned things around. In my > tests it appears to cache vnodes as long as there are resident pages > associated with them. Sounds like a very good first step. I would like to point out that the problem may still occur on large memory systems with a few hundred thousand tiny files (that consume just one page of memory). There really needs to be a hard limit as well - something low enough so that the FFS node KVM malloc limit isn't reached, but still large enough to not significantly pessimize the use of otherwise free physical memory for file caching. Considering that a 4GB machine has about 1 million pages and that the malloc limit hits at about 250,000 vnodes, this is an impossible goal to acheive in that case without increasing the malloc limit by at least 4X. Of course this many 1 page files is extremely rare, however, and I don't think we should optimize for it. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - 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 Sat Sep 22 15:10: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 10FF137B403 for ; Sat, 22 Sep 2001 15:09:58 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f8MM9qs82489; Sat, 22 Sep 2001 15:09:52 -0700 (PDT) (envelope-from dillon) Date: Sat, 22 Sep 2001 15:09:52 -0700 (PDT) From: Matt Dillon Message-Id: <200109222209.f8MM9qs82489@earth.backplane.com> To: David Greenman Cc: Poul-Henning Kamp , Seigo Tanimura , bright@wintelcom.net, hackers@FreeBSD.ORG Subject: Re: More on the cache_purgeleafdirs() routine References: <88901.1001191415@critter> <200109222121.f8MLLHe82202@earth.backplane.com> <20010922141934.C28469@nexus.root.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :> Well, wait a sec... all I do is zap the namei cache for the vnode. The :> check to see if the vnode's object still has resident pages is still in :> there so I don't quite understand how I turned things around. In my :> tests it appears to cache vnodes as long as there are resident pages :> associated with them. : : Sounds like a very good first step. I would like to point out that the :problem may still occur on large memory systems with a few hundred thousand :tiny files (that consume just one page of memory). There really needs to :be a hard limit as well - something low enough so that the FFS node KVM malloc :limit isn't reached, but still large enough to not significantly pessimize :the use of otherwise free physical memory for file caching. Considering that :a 4GB machine has about 1 million pages and that the malloc limit hits at :about 250,000 vnodes, this is an impossible goal to acheive in that case :without increasing the malloc limit by at least 4X. Of course this many :1 page files is extremely rare, however, and I don't think we should optimize :for it. : :-DG Yes, it's easy to hit 250,000 vnodes. On a 512M machine I can hit 80,000 vnodes without breaking a sweat. The reason is simply due to the way the VM Page cache works... even medium sized files can wind up with just one page in core after a while. It does stabilize, but at a level that is too high for comfort. On -stable we've exasperated the problem because inode->i_dirhash increased the size of struct inode to 260 bytes, causing it to use a 512 byte MALLOC chunk (FFS node malloc type) instead of a 256 byte chunk. I'm working with Ian to get struct inode back down to 256 bytes (It isn't a problem in -current). Unfortunately this introduced additional issues in our 4.4 release for people with > 2GB of ram and at least one person is seeing system deadlocks from it. I think it would be fairly easy to release VM pages underlying objects associated with vnodes being reused when we determine that we have too many vnodes. We would have to be careful, because what Poul said really would come true if we blindly released VM pages based on the vnode free list! Alternatively we might be able to adjust the VM paging system to release nearby VM pages in idle VM objects, getting them cleared out more quickly and allowing their vnodes to be reused without compromising the VM system's excellent page selection code. At least then it would truely take a million 'small' files to create an issue. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 22 17:58:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail36.sdc1.sfba.home.com (femail36.sdc1.sfba.home.com [24.254.60.26]) by hub.freebsd.org (Postfix) with ESMTP id BC9F837B422; Sat, 22 Sep 2001 17:58:44 -0700 (PDT) Received: from home.com ([24.12.186.185]) by femail36.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010921161635.GMSR13666.femail36.sdc1.sfba.home.com@home.com>; Fri, 21 Sep 2001 09:16:35 -0700 Message-ID: <3BAB67BA.B0C1A149@home.com> Date: Fri, 21 Sep 2001 09:15:54 -0700 From: Rob X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Jason Andresen Cc: bmah@FreeBSD.ORG, Alfred Perlstein , Jordan Hubbard , kris@obsecurity.org, andrsn@andrsn.stanford.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: No tools on 4.4-RELEASE ISO? References: <3BA9EEED.B7F0A194@mitre.org> <20010920223730.A82191@xor.obsecurity.org> <20010920234553S.jkh@freebsd.org> <200109211448.f8LEmfd54113@c527597-a.cstvl1.sfba.home.com> <20010921095056.M61456@elvis.mu.org> <200109211518.f8LFITg54534@c527597-a.cstvl1.sfba.home.com> <3BAB6513.F6251E77@mitre.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jason Andresen wrote: > > "Bruce A. Mah" wrote: > > > > Note that the set of people affected is going to be "people who can't do > > anonymous FTP, don't have bootable CDROMs, and *only* have the ISO > > images to work with". I don't know for sure, but I'd expect this set to > > be pretty small...if they don't have Internet access, how'd they get the > > ISO images? > > Probably more often that you'd expect. I know I had to install 4.4 in > our lab (which blocks most net access) full of old machines. Fortunatly > I have a 4.3 ISO sitting here that I just grabbed fdimage from and > went on, but it did seem like a rather noticable oversight. > > What about the boot managers in that directory? Certainly people will > want > to dual boot their new FreeBSD installs? > > -- > \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org > |\/ | | | / _| Network and Distributed Systems Engineer > _| _|___| _| _|_\___| Office: 703-883-7755 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message How about a new directory called .../Fixed_Isos Rob. -- The Numeric Python EM Project www.members.home.net/europax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 22 23:42:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id B270B37B42B for ; Sat, 22 Sep 2001 23:42:31 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f8N6gPj84955; Sat, 22 Sep 2001 23:42:25 -0700 (PDT) (envelope-from dillon) Date: Sat, 22 Sep 2001 23:42:25 -0700 (PDT) From: Matt Dillon Message-Id: <200109230642.f8N6gPj84955@earth.backplane.com> To: David Greenman Cc: Poul-Henning Kamp , Seigo Tanimura , bright@wintelcom.net, hackers@FreeBSD.ORG Subject: Conclusions on... was Re: More on the cache_purgeleafdirs() routine References: <88901.1001191415@critter> <200109222121.f8MLLHe82202@earth.backplane.com> <20010922141934.C28469@nexus.root.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, this has turned into a rather sticky little problem. I've spent all day going through the vnode/name-cache reclaim code, looking both at Seigo's cache_purgeleafdirs() and my own patch. This is what is going on: The old code refused to reuse any vnode that had (A) Cached VM Pages associated with it *AND* (B) refused to reuse directory vnodes residing in the namei cache that contained any subdirectory or file. (B) does not apply to file vnodes since they obviously cannot have subdirectories or files 'under' them in the namei cache. The problem is that when you take the union of (A) and (B), just about every directory vnode in the system winds up being immunue from reclamation. Thus directory vnodes appear to grow forever... so it isn't just the fact that most directories are small that is the problem, it's the presence of (B). This is why small files don't cause the same problem (or at least do not cause it to the same degree). Both Seigo's cache_purgeleafdirs() and my simpler patch simply remove the (B) requirement, making directory reclamation work approximately the same as file reclamation. The only difference between Seigo's patch and mine is that Seigo's makes an effort to remove directories intelligently... it tries to avoid removing higher level directories. My patch doesn't make a distinction but assumes that (A) will tend to hold for higher level directories: that is, that higher level directories tend to be accessed more often and thus will tend to have pages in the VM Page Cache, and thus not be candidates for reuse anyway. So my patch has a very similar effect but without the overhead. In all the testing I've done I cannot perceive any performance difference between Seigo's patch and mine, but from an algorithmic point of view mine ought to scale much, much better. Even if we adjust cache_purgeleafdirs() to run even less often, we still run up against the fact that the scanning algorithm is O(N*M) and we know from history that this can create serious breakage. People may recall that we had similar problems with the VM Pageout daemon, where under certain load conditions the pageout daemon wound up running continuously, eating enormous amounts of cpu. We lived with the problem for years because the scaling issues didn't rear their heads until machines got hefty enough to have enough pages for the algorithms to break down. People may also recall that we had similar problems with the buffer cache code.... specifically, the scan 'restart' conditions could break down algorithmically and result in massive cpu use by bufdaemon. I think cache_purgeleafdirs() had the right idea. From my experience with the VM system, however, I have to recommend that we remove it from the system and, at least initially, replace it with my simpler patch. We could extend my patch to do the same check -- that is, only remove directory vnodes at lower levels in the namei cache, simply by scanning the namei cache list at the vnode in question. So in fact it would be possible to adjust my patch to have the same effect that cache_purgeleafdirs() had, but without the scaling issue (or at least with less of an issue.. it would be O(N) rather then O(M*N)). - The bigger problem is exactly as DG has stated... it isn't the namei cache that is our enemy, it's the VM Page cache preventing vnodes from being recycled. For the moment I believe that cache_purgeleafdirs() or my patch solves the problem well enough that we can run with it for a while. The real solution, I believe, is to give us the ability to take cached VM Pages associated with a file and rename them to cached VM Pages associated with the filesystem device - we can do this only for page-aligned blocks of course, not fragments (which we would simply throw away)... but it would allow us to reclaim vnodes independant of the VM Page cache without losing the cached pages. I think this is doable but it will require a considerable amount of work. It isn't something I can do in a day. I also believe that this can dovetail quite nicely into the I/O model that we have slowly been moving towards over the last year (Poul's work). Inevitably we will have to manage device-based I/O on a page-by-page basis and being able to do it via a VM Object seems to fit the bill in my opinion. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message