From owner-freebsd-hackers Sun Nov 26 6:23:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from downserv.kjkoster.org (213-84-15-12.adsl.xs4all.nl [213.84.15.12]) by hub.freebsd.org (Postfix) with ESMTP id 04AC337B479 for ; Sun, 26 Nov 2000 06:23:19 -0800 (PST) Received: from tccn.cs.kun.nl (likeever.kjkoster.org [192.168.0.1]) by downserv.kjkoster.org (8.11.1/8.11.0) with ESMTP id eAQENHZ50091 for ; Sun, 26 Nov 2000 15:23:17 +0100 (CET) (envelope-from dutchman@tccn.cs.kun.nl) Message-ID: <3A211CD5.CE57DA88@tccn.cs.kun.nl> Date: Sun, 26 Nov 2000 15:23:17 +0100 From: Kees Jan Koster X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD Hackers mailing list Subject: truncating problem (long, sorry) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear All, I always get the following message at system boot time: "slice extends beyond end of disk: truncating". This message is odd, because I have two identical harddisks (Maxtor DiamondMax 15Gb) and I have formatted and sliced them in precisely the same way, yet only one of them reports trouble. When I search the mailing list archives for others reporting the same trouble, I find that there's usually a Maxtor disk or an Asus K7V motherboard (which is what I use too) involved. Funny... I found one message a while ago that talks about how a kernel hack "helpfully" extends slices for braindead disks, IIRC. Of course, I cannot find that message back, nor can I find a reference to it in the kernel sources. I tried fiddling with the BIOS, but the disks are detected correctly by FreeBSD no matter what. :-) The setup runs like a charm. The disks are fast and give me no grief and I would not have reported this if it was not for the fact that these disks are *identical* and yet only one reports a problem. What am I missing? ******* Relevant dmesg output: FreeBSD 4.2-BETA #0: Sat Nov 18 15:37:00 CET 2000 ... atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ... ad0: 14655MB [29777/16/63] at ata0-master UDMA66 ad2: 14655MB [29777/16/63] at ata1-master UDMA66 ... ad2s5: slice extends beyond end of disk: truncating from 16530822 to 16520553 sectors ******* fdisk output: ******* Working on device /dev/ad0 ******* parameters extracted from in-core disklabel are: cylinders=1868 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1868 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 10485153 (5119 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 652/ sector 63/ head 171 The data for partition 2 is: sysid 11,(DOS or Windows 95 with 32 bit FAT) start 10490445, size 3004155 (1466 Meg), flag 0 beg: cyl 653/ sector 1/ head 0; end: cyl 839/ sector 63/ head 254 The data for partition 3 is: sysid 15,(Extended DOS, LBA) start 13494600, size 16514820 (8063 Meg), flag 0 beg: cyl 840/ sector 1/ head 0; end: cyl 1023/ sector 63/ head 254 The data for partition 4 is: ******* Working on device /dev/ad2 ******* parameters extracted from in-core disklabel are: cylinders=1868 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1868 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 10485153 (5119 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 652/ sector 63/ head 171 The data for partition 2 is: sysid 11,(DOS or Windows 95 with 32 bit FAT) start 10490445, size 3004155 (1466 Meg), flag 0 beg: cyl 653/ sector 1/ head 0; end: cyl 839/ sector 63/ head 254 The data for partition 3 is: sysid 15,(Extended DOS, LBA) start 13494600, size 16514820 (8063 Meg), flag 0 beg: cyl 840/ sector 1/ head 0; end: cyl 1023/ sector 63/ head 254 The data for partition 4 is: ******* disklabels LikeEver# disklabel -r ad0 | tail -6 # size offset fstype [fsize bsize bps/cpg] a: 204800 0 4.2BSD 0 0 0 # (Cyl. 0 - 12*) b: 262144 204800 swap # (Cyl. 12*- 29*) c: 10485153 0 unused 0 0 # (Cyl. 0 - 652*) e: 2097152 466944 4.2BSD 0 0 0 # (Cyl. 29*- 159*) g: 7921057 2564096 4.2BSD 0 0 0 # (Cyl. 159*- 652*) LikeEver# disklabel -r ad2 | tail -6 # size offset fstype [fsize bsize bps/cpg] e: 204800 0 4.2BSD 0 0 0 # (Cyl. 0 - 12*) b: 262144 204800 swap # (Cyl. 12*- 29*) c: 10485153 0 unused 0 0 # (Cyl. 0 - 652*) f: 2097152 466944 4.2BSD 0 0 0 # (Cyl. 29*- 159*) g: 7921057 2564096 4.2BSD 0 0 0 # (Cyl. 159*- 652*) Enjoy, Kees Jan ---------------------------------------------------------------------- Kees Jan Koster e-mail: dutchman "at" tccn.cs.kun.nl ---------------------------------------------------------------------- Calvin: "Sometimes the world seems like a pretty mean place." Hobbes: "That's why animals are so soft and huggy." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 26 7: 9:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail8.sc.rr.com (fe8.southeast.rr.com [24.93.67.55]) by hub.freebsd.org (Postfix) with ESMTP id 386ED37B479 for ; Sun, 26 Nov 2000 07:09:12 -0800 (PST) Received: from cae88-102-101.sc.rr.com ([24.88.102.101]) by mail8.sc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 26 Nov 2000 10:08:10 -0500 Date: Sun, 14 Mar 1999 09:33:11 -0500 From: "Donald J . Maddox" To: Kris Kennaway Cc: hackers@FreeBSD.ORG Subject: Re: Stripping a.out binaries Message-ID: <19990314093310.A561@dmaddox.conterra.com> Reply-To: dmaddox@conterra.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Kris Kennaway on Sun, Mar 14, 1999 at 10:48:24PM +0930 Content-Length: 973 Lines: 25 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You can use 'strip -aout ' to strip it. As far as I know, there is currently no way to specify the executable format to 'install -s'. I haven't tried it, but you might be able to use the OBJFORMAT or OBJECT_FORMAT (not sure which form is correct) environment variable to make install DTRT for aout. On Sun, Mar 14, 1999 at 10:48:24PM +0930, Kris Kennaway wrote: > I'm porting a utility which is distributed in a.out binary form, which > 'install -s' is choking over (File format not recognised). How can I strip(1) > an a.out executable, and can install(1) be fixed to DTRT? > > nftp: FreeBSD/i386 compact demand paged dynamically linked executable > > Kris > > ----- > (ASP) Microsoft Corporation (MSFT) announced today that the release of its > productivity suite, Office 2000, will be delayed until the first quarter > of 1901. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 26 7: 9:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail8.sc.rr.com (fe8.southeast.rr.com [24.93.67.55]) by hub.freebsd.org (Postfix) with ESMTP id AB5CE37B678 for ; Sun, 26 Nov 2000 07:09:24 -0800 (PST) Received: from cae88-102-101.sc.rr.com ([24.88.102.101]) by mail8.sc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 26 Nov 2000 10:08:23 -0500 Date: Fri, 23 Apr 1999 18:01:42 -0400 From: "Donald J . Maddox" To: "Daniel C. Sobral" Cc: Gianmarco Giovannelli , Gianmarco Giovannelli , hackers@FreeBSD.ORG Subject: Re: Uox, Linux emul and missing things. Message-ID: <19990423180142.B435@dmaddox.conterra.com> Reply-To: dmaddox@conterra.com References: <4.1.19990422133009.00b95d10@194.184.65.4> <4.1.19990422213220.00a1bf00@194.184.65.4> <371FB41B.B4B7A375@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <371FB41B.B4B7A375@newsguy.com>; from Daniel C. Sobral on Fri, Apr 23, 1999 at 08:43:23AM +0900 Content-Length: 976 Lines: 29 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 23, 1999 at 08:43:23AM +0900, Daniel C. Sobral wrote: > Gianmarco Giovannelli wrote: > > > > At 02.19 23/04/99 +0900, Daniel C. Sobral wrote: > > > > >FreeBSD defaults to signal floating point exceptions in case of > > >overflow and things like that. Linux, I take it, does not. > > > > > >Short of correcting the program, I think there is a system wide > > >setting to turn off floating point exceptions. > > > > :-) can you input more verbosely ? > > Like in, explaining what to do? :-) I don't know how to change the > setting, I'm not even 100% sure it exists. Try listing sysctls. If you really want to do this globally, try this patch to src/sys/i386/include/npx.h: --- npx.h.orig Sun Jul 20 07:06:44 1997 +++ npx.h Fri Jan 15 22:42:23 1999 @@ -142,5 +142,6 @@ void npxinit __P((int control)); void npxsave __P((struct save87 *addr)); #endif - +#undef __INITIAL_NPXCW__ +#define __INITIAL_NPXCW__ __BETTER_BDE_NPXCW__ #endif /* !_MACHINE_NPX_H_ */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 26 10: 6:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 13B9A37B479 for ; Sun, 26 Nov 2000 10:06:13 -0800 (PST) Received: (qmail 26945 invoked by uid 0); 26 Nov 2000 18:06:11 -0000 Received: from p3e9bc32c.dip.t-dialin.net (HELO forge.local) (62.155.195.44) by mail.gmx.net (mail10) with SMTP; 26 Nov 2000 18:06:11 -0000 Received: from thomas by forge.local with local (Exim 3.12 #1 (Debian)) id 1406AX-0000In-00 for ; Sun, 26 Nov 2000 19:04:53 +0100 Date: Sun, 26 Nov 2000 19:04:53 +0100 To: freebsd-hackers@freebsd.org Subject: [PATCH] Fix for panics in lookup() after forced unmount Message-ID: <20001126190453.A1157@crow.dom2ip.de> Mail-Followup-To: tmoestl@gmx.net, freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i From: Thomas Moestl Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I think I have a sufficient fix for PR kern/19572. Could somebody please Review/Comment this? To quote: > Description > Executing cd ../cdrom from /cdrom directory after cycle of mount-umount- > mount cycle causes trap 12 (page fault while in kernel mode) and hence > causes kernel panic. > How-To-Repeat > chdir to /cdrom (which) is default mount point for cdrom as per fstab. > mount /cdrom and do ls > now umount -f /cdrom (force as we will be /cdrom) > doing ls will give error( . not a directory) > do mount /cdrom to mount the cdrom once again (we are still in /cdrom dir) > now do ls will give error once again > now do cd ../ (tab in case of bash or esc in case of csh) to do file > completion. > This will result in trap 12 (page fault in kernel mode) and thus > results in kernel panic. Actually, the panic will occur after a simple forced unmount of the current working directory and subsequent try to access "..". This is because the vnode of the cwd was cleared and it's v_mount member was set to NULL. This member is however dereferenced in the handling for the ".." special case in lookup(), causing a panic. The fix is rather trivial, just check the member before using it and return an appropriate error. In the following patch, I use EBADF. Btw, after taking a look into the OpenBSD and NetBSD repos, I think they might have the same problem. Is there any standard channel to pass bug reports to them from FreeBSD, or should I just use the normal submit procedure? - Thomas The patch: ------------------------------------------------------------------------ *** old/kern/vfs_lookup.c Sat Nov 25 23:55:39 2000 --- new/kern/vfs_lookup.c Sun Nov 26 00:58:15 2000 *************** *** 403,408 **** --- 403,412 ---- if ((dp->v_flag & VROOT) == 0 || (cnp->cn_flags & NOCROSSMOUNT)) break; + if (dp->v_mount == NULL) { /* forced unmount */ + error = EBADF; + goto bad; + } tdp = dp; dp = dp->v_mount->mnt_vnodecovered; vput(tdp); *************** *** 424,430 **** printf("not found\n"); #endif if ((error == ENOENT) && ! (dp->v_flag & VROOT) && (dp->v_mount->mnt_flag & MNT_UNION)) { tdp = dp; dp = dp->v_mount->mnt_vnodecovered; --- 428,434 ---- printf("not found\n"); #endif if ((error == ENOENT) && ! (dp->v_flag & VROOT) && (dp->v_mount != NULL) && (dp->v_mount->mnt_flag & MNT_UNION)) { tdp = dp; dp = dp->v_mount->mnt_vnodecovered; *************** *** 502,507 **** --- 506,517 ---- ((cnp->cn_flags & FOLLOW) || trailing_slash || *ndp->ni_next == '/')) { cnp->cn_flags |= ISSYMLINK; + if (dp->v_mount == NULL) { + /* We can't know whether the directory was mounted with + * NOSYMFOLLOW, so we can't follow safely. */ + error = EBADF; + goto bad2; + } if (dp->v_mount->mnt_flag & MNT_NOSYMFOLLOW) { error = EACCES; goto bad2; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 26 10:13:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 4828737B479 for ; Sun, 26 Nov 2000 10:13:40 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eAQIDZ346044; Sun, 26 Nov 2000 10:13:35 -0800 (PST) (envelope-from dillon) Date: Sun, 26 Nov 2000 10:13:35 -0800 (PST) From: Matt Dillon Message-Id: <200011261813.eAQIDZ346044@earth.backplane.com> To: Thomas Moestl Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: [PATCH] Fix for panics in lookup() after forced unmount References: <20001126190453.A1157@crow.dom2ip.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, : :I think I have a sufficient fix for PR kern/19572. Could somebody please :Review/Comment this? :To quote: Looks reasonable to me! It certainly can't make things worse :-) -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 26 13:59:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id DE26237B479 for ; Sun, 26 Nov 2000 13:59:08 -0800 (PST) Received: (qmail 6873 invoked by uid 0); 26 Nov 2000 21:59:07 -0000 Received: from pc19ebf07.dip.t-dialin.net (HELO forge.local) (193.158.191.7) by mail.gmx.net (mail02) with SMTP; 26 Nov 2000 21:59:07 -0000 Received: from thomas by forge.local with local (Exim 3.12 #1 (Debian)) id 1409ns-0000Zd-00 for ; Sun, 26 Nov 2000 22:57:44 +0100 Date: Sun, 26 Nov 2000 22:57:44 +0100 From: Thomas Moestl To: freebsd-hackers@FreeBSD.ORG Subject: Re: [PATCH] Fix for panics in lookup() after forced unmount Message-ID: <20001126225744.A2180@crow.dom2ip.de> Mail-Followup-To: Thomas Moestl , freebsd-hackers@FreeBSD.ORG References: <20001126190453.A1157@crow.dom2ip.de> <200011261813.eAQIDZ346044@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: <200011261813.eAQIDZ346044@earth.backplane.com>; from dillon@earth.backplane.com on Sun, Nov 26, 2000 at 10:13:35AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :I think I have a sufficient fix for PR kern/19572. Could somebody please > :Review/Comment this? > :To quote: > > Looks reasonable to me! It certainly can't make things worse :-) Could someone then please look into committing this? TIA, - Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 26 17:13: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 4CF6037B479 for ; Sun, 26 Nov 2000 17:13:02 -0800 (PST) Received: from office.tor.velocet.net (trooper.velocet.net [204.138.45.2]) by sabre.velocet.net (Postfix) with ESMTP id EE41A137F08 for ; Sun, 26 Nov 2000 20:10:19 -0500 (EST) Received: (from dgilbert@localhost) by office.tor.velocet.net (8.9.3/8.9.3) id UAA23371; Sun, 26 Nov 2000 20:12:52 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14881.46356.49105.382746@trooper.velocet.net> Date: Sun, 26 Nov 2000 20:12:52 -0500 (EST) To: freebsd-hackers@freebsd.org Subject: rebooting from gdb? X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the gdb prompt when you're debugging a machine that is being remote kernel debugged, what do you call to reboot the machine? Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 26 21: 4:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 9FB3F37B479 for ; Sun, 26 Nov 2000 21:04:46 -0800 (PST) Received: by relay.butya.kz (Postfix, from userid 1000) id 05181289B9; Mon, 27 Nov 2000 11:04:37 +0600 (ALMT) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id E83FD288DC; Mon, 27 Nov 2000 11:04:37 +0600 (ALMT) Date: Mon, 27 Nov 2000 11:04:37 +0600 (ALMT) From: Boris Popov To: Thomas Moestl Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fix for panics in lookup() after forced unmount In-Reply-To: <20001126190453.A1157@crow.dom2ip.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Nov 2000, Thomas Moestl wrote: > Actually, the panic will occur after a simple forced unmount of the current > working directory and subsequent try to access "..". This is because the > vnode of the cwd was cleared and it's v_mount member was set to NULL. This > member is however dereferenced in the handling for the ".." special case in > lookup(), causing a panic. > The fix is rather trivial, just check the member before using it and return > an appropriate error. In the following patch, I use EBADF. > Btw, after taking a look into the OpenBSD and NetBSD repos, I think they > might have the same problem. Is there any standard channel to pass bug > reports to them from FreeBSD, or should I just use the normal submit > procedure? Good work Thomas! I think patch can be committed as is. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 26 21:18:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whizkidtech.net (r10.bfm.org [216.127.220.106]) by hub.freebsd.org (Postfix) with ESMTP id 8EB5D37B4E5 for ; Sun, 26 Nov 2000 21:18:32 -0800 (PST) Received: (from adam@localhost) by whizkidtech.net (8.9.2/8.9.2) id XAA00294 for hackers@FreeBSD.org; Sun, 26 Nov 2000 23:17:21 -0600 (CST) (envelope-from adam) Date: Sun, 26 Nov 2000 23:16:49 -0600 From: "G. Adam Stanislav" To: hackers@FreeBSD.org Subject: int80h.org Message-ID: <20001126231649.A278@whizkidtech.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Organization: Whiz Kid Technomagic X-URL: http://www.whizkidtech.net/ X-Castle: http://www.redprince.net/ X-Special-Effects: http://www.FilmSFX.com/ X-Operating-System: FreeBSD whizkidtech.net 3.1-RELEASE FreeBSD 3.1-RELEASE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Several weeks ago I have asked several questions about assembly language programming under FreeBSD. I also promissed to share what I learned with others on my web site. I am glad to say that my asm project is moving along fast. I am working on HED (HTML editor). I created my own mark-up language which I named Ister. HED converts Ister mark-up to HTML. I am now in the process of writing its documentation. It is nowhere near finished, but what I have so far is at http://www.whizkidtech.net/ister/ (it would be nice to hear if what I have written makes any sense to anyone but me -- I am so familiar with it that I am worried my documentation may be confusing). Anyway, I decided to really write something serious about assembly language programming under FreeBSD. So much so that I secured a domain just for that purpose: int80h.org (mostly because I got the impression from www.linuxassembly.org that int 80h belongs to Linux!). I have just placed the first page on it. I hope I have configured my .htaccess properly so, as soon as the DNS system realizes there is a http://www.int80h.org/ it will send you the right page (I am sharing it with my main web site whizkidtech.net, and simply ask .htaccess to give you a different start page if you come to int80h.org - that is why I said I hope it is going to work). If curious, you can read it even now. If your browser cannot locate int80h.org yet (it should tomorrow), you can find the same page as http://www.whizkidtech.net/int80h.hed for now. There is not much there, I just wrote it (and I have to go to work in 15 minutes). But I'd like to get some feedback. And if anyone wants to write for the site, all the better. :) Cheers, Adam -- Where two fight, third one wins -- Slovak proverb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Nov 26 23:21:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4B54737B479; Sun, 26 Nov 2000 23:21:18 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAR7LHR21429; Sun, 26 Nov 2000 23:21:17 -0800 (PST) Date: Sun, 26 Nov 2000 23:21:17 -0800 From: Alfred Perlstein To: dillon@freebsd.org Cc: hackers@freebsd.org Subject: bwillwrite() not right. Message-ID: <20001126232117.C8051@fw.wintelcom.net> 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 X-Loop: FreeBSD.ORG bwillwrite() is called in kern/sys_generic.c:dofilewrite() bwillwrite() is meant as a quick stop before doing any vnode ops to flush dirty buffers to prevent a deadlock. However: 1) afaik only VNODES have backing buffers, so stalling socket/pipes doesn't gain us anything 2) writev() doesn't call bwillwrite() shouldn't the code be changed like so: Index: sys_generic.c =================================================================== RCS file: /home/ncvs/src/sys/kern/sys_generic.c,v retrieving revision 1.65 diff -u -r1.65 sys_generic.c --- sys_generic.c 2000/11/21 20:22:34 1.65 +++ sys_generic.c 2000/11/27 07:18:48 @@ -403,7 +403,8 @@ } #endif cnt = nbyte; - bwillwrite(); + if (fp->f_type == DTYPE_VNODE) + bwillwrite(); if ((error = fo_write(fp, &auio, fp->f_cred, flags, p))) { if (auio.uio_resid != cnt && (error == ERESTART || error == EINTR || error == EWOULDBLOCK)) @@ -495,6 +496,8 @@ } #endif cnt = auio.uio_resid; + if (fp->f_type == DTYPE_VNODE) + bwillwrite(); if ((error = fo_write(fp, &auio, fp->f_cred, 0, p))) { if (auio.uio_resid != cnt && (error == ERESTART || error == EINTR || error == EWOULDBLOCK)) thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 0:53:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 9745737B479 for ; Mon, 27 Nov 2000 00:53:32 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eAR8rH229425; Mon, 27 Nov 2000 00:53:17 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Nov 2000 00:53:17 -0800 (PST) From: Matt Dillon Message-Id: <200011270853.eAR8rH229425@earth.backplane.com> To: Alfred Perlstein Cc: hackers@FreeBSD.ORG Subject: Re: bwillwrite() not right. References: <20001126232117.C8051@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :bwillwrite() is called in kern/sys_generic.c:dofilewrite() : :bwillwrite() is meant as a quick stop before doing any vnode :ops to flush dirty buffers to prevent a deadlock. : :However: :1) afaik only VNODES have backing buffers, so stalling socket/pipes : doesn't gain us anything :2) writev() doesn't call bwillwrite() : :shouldn't the code be changed like so: Hmm.. Well, your suggestion is certainly better then what it is doing now. bwillwrite() is somewhat of a hack, I just haven't gotten around to replacing it with something better. What it is approximating is an attempt to block on low-memory prior to locking a vnode so we do not wind up blocking on low-memory later on when the lock is being held (which could prevent the pageout daemon from paging pages associated with that vnode out, thus causing a deadlock). When you feel comfortable with it in your own testing, go ahead and commit it to -current. But give it at least a good week's worth of testing (or longer) before MFCing it to -stable. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 0:59:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.radio-do.de (gatekeeper.Radio-do.de [193.101.164.1]) by hub.freebsd.org (Postfix) with ESMTP id 52E1337B479 for ; Mon, 27 Nov 2000 00:59:35 -0800 (PST) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by gatekeeper.radio-do.de (Postfix) with ESMTP id B509716FB0; Mon, 27 Nov 2000 09:59:27 +0100 (CET) Received: (from fn@localhost) by trinity.radio-do.de (8.11.1/8.9.3) id eAR8xRu61150; Mon, 27 Nov 2000 09:59:27 +0100 (CET) (envelope-from fn@gatekeeper.radio-do.de) Date: Mon, 27 Nov 2000 09:59:27 +0100 From: Frank Nobis To: David Gilbert Cc: freebsd-hackers@freebsd.org Subject: Re: rebooting from gdb? Message-ID: <20001127095927.A61079@radio-do.de> References: <14881.46356.49105.382746@trooper.velocet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14881.46356.49105.382746@trooper.velocet.net>; from dgilbert@velocet.ca on Sun, Nov 26, 2000 at 08:12:52PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 26, 2000 at 08:12:52PM -0500, David Gilbert wrote: > >From the gdb prompt when you're debugging a machine that is being > remote kernel debugged, what do you call to reboot the machine? From inside the debugger one can do a "call boot()". That should do the trick. But I am not sure if this will safely umount the filesystems. -fn- -- ~/.signature not found: wellknown error 42 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 7:18:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 4D67F37B4C5 for ; Mon, 27 Nov 2000 07:18:51 -0800 (PST) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.0/8.11.0) id eARFI2f08015; Mon, 27 Nov 2000 15:18:02 GMT (envelope-from nik) Date: Mon, 27 Nov 2000 15:18:02 +0000 From: Nik Clayton To: "G. Adam Stanislav" Cc: hackers@FreeBSD.org Subject: Re: int80h.org Message-ID: <20001127151802.A7983@canyon.nothing-going-on.org> References: <20001126231649.A278@whizkidtech.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001126231649.A278@whizkidtech.net>; from adam@whizkidtech.net on Sun, Nov 26, 2000 at 11:16:49PM -0600 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 26, 2000 at 11:16:49PM -0600, G. Adam Stanislav wrote: > Anyway, I decided to really write something serious about assembly > language programming under FreeBSD. So much so that I secured a domain > just for that purpose: int80h.org (mostly because I got the impression > from www.linuxassembly.org that int 80h belongs to Linux!). > > I have just placed the first page on it. I hope I have configured my > .htaccess properly so, as soon as the DNS system realizes there is a > http://www.int80h.org/ it will send you the right page (I am sharing > it with my main web site whizkidtech.net, and simply ask .htaccess > to give you a different start page if you come to int80h.org - that > is why I said I hope it is going to work). > > If curious, you can read it even now. If your browser cannot locate > int80h.org yet (it should tomorrow), you can find the same page as > http://www.whizkidtech.net/int80h.hed for now. It certainly looks interesting. One thing though -- have you considered DocBook as the documentation format? That would make it much easier to integrate this with the existing FreeBSD documentation (either as part of the Handbook, or as a separate book). This would bring a number of benefits: * Immediate access to your text via CVS for the rest of the world. * Your text would be mirrored automatically by all the FreeBSD mirrors. * It becomes much easier for the various FreeBSD translation teams to translate your document. More information can be found at http://www.freebsd.org/tutorials/docproj-primer/ N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 8: 6:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from muncher.iss.net (muncher.iss.net [208.27.178.48]) by hub.freebsd.org (Postfix) with ESMTP id AAFC637B479 for ; Mon, 27 Nov 2000 08:06:31 -0800 (PST) Received: from iss.net (IDENT:ato@localhost [127.0.0.1]) by muncher.iss.net (8.9.3/8.9.3) with ESMTP id LAA21177; Mon, 27 Nov 2000 11:06:25 -0500 Message-ID: <3A228681.4A3DBE88@iss.net> Date: Mon, 27 Nov 2000 11:06:25 -0500 From: Andrew Otwell Organization: ISS X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: porting Linux application to FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG source.c ------------------------- #include int main () { printf ("Hello world\n"); } ------------------------- A couple of you answered my first query which gave me.... gcc -nostdinc -I/includedir -nostdlib -L/libdir source.c This always failed with either.... ld: No reference to __DYNAMIC collect2: ld returned 1 exit status or /var/tmp/ccdgopIG.o: Undefined symbol `___main' referenced from text segment /var/tmp/ccdgopIG.o: Undefined symbol `_printf' referenced from text segment /var/tmp/ccdgopIG.o: Undefined symbol `_printf' referenced from text segment collect2: ld returned 1 exit status Depending on whether I specified lib names (ex. -lnet -lpcap -lgcc, etc....) I finally pulled all my hair out and ran gcc -nostdinc -I/usr/include -nostdlib -L/usr/lib source.c =-= and =-= gcc -nostdlib -L/usr/lib source.c and again I received..... /var/tmp/ccdgopIG.o: Undefined symbol `___main' referenced from text segment /var/tmp/ccdgopIG.o: Undefined symbol `_printf' referenced from text segment /var/tmp/ccdgopIG.o: Undefined symbol `_printf' referenced from text segment collect2: ld returned 1 exit status Can anyone assist with this? I need to be able to compile and link a "Hello World" program against a proprietary lib dir for my project but for starters I have to make sure my anomolies are not with the "ld" portion of my build. Why doesn't "gcc -nostdlib -L/usr/lib source.c" link properly? I even added all the .a files with -lnet -lpcap -ledit, so forth.... and it still failed. Please reply to all. If I need to direct this to our gcc brethren then please advise. -- Andrew Otwell, MSS Special Ops Recon/Surveillance/Developer desk 678.443.6271, aotwell@iss.net, http://www.iss.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 8:29:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id CCF3337B479 for ; Mon, 27 Nov 2000 08:29:55 -0800 (PST) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.1/8.11.1) id eARGZQw29552; Mon, 27 Nov 2000 08:35:27 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200011271635.eARGZQw29552@troutmask.apl.washington.edu> Subject: Re: porting Linux application to FreeBSD In-Reply-To: <3A228681.4A3DBE88@iss.net> from Andrew Otwell at "Nov 27, 2000 11:06:25 am" To: Andrew Otwell Date: Mon, 27 Nov 2000 08:35:26 -0800 (PST) Cc: 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 X-Loop: FreeBSD.ORG Andrew Otwell wrote: > > A couple of you answered my first query which gave me.... > > gcc -nostdinc -I/includedir -nostdlib -L/libdir source.c > > This always failed with either.... > > ld: No reference to __DYNAMIC > collect2: ld returned 1 exit status > info gcc gcc -v -static -nostdinc -I/includedir -nostdlib source.c \ -L/libdir -lfirstlib -lsecondlib .... -lc The -v flag will show you all aspects of the linking of your program. The -static flags make gcc use static linking. The -nostdlib suppress the normal linking of libraries usually supplied by the system. This means you have to explicitly list all libraries on the command including the standard C library. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 8:42:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 2725837B479 for ; Mon, 27 Nov 2000 08:42:38 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 140ROt-00008R-00; Mon, 27 Nov 2000 09:45:08 -0700 Message-ID: <3A228F93.40812671@softweyr.com> Date: Mon, 27 Nov 2000 09:45:07 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Otwell Cc: hackers@freebsd.org Subject: Re: porting Linux application to FreeBSD References: <3A228681.4A3DBE88@iss.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Otwell wrote: > > source.c > ------------------------- > #include > int main () { > printf ("Hello world\n"); > } > ------------------------- > > A couple of you answered my first query which gave me.... > > gcc -nostdinc -I/includedir -nostdlib -L/libdir source.c > > This always failed with either.... > > ld: No reference to __DYNAMIC > collect2: ld returned 1 exit status > > or > > /var/tmp/ccdgopIG.o: Undefined symbol `___main' referenced from text segment > /var/tmp/ccdgopIG.o: Undefined symbol `_printf' referenced from text segment > /var/tmp/ccdgopIG.o: Undefined symbol `_printf' referenced from text segment > collect2: ld returned 1 exit status > > Depending on whether I specified lib names (ex. -lnet -lpcap -lgcc, etc....) > > I finally pulled all my hair out and ran > > gcc -nostdinc -I/usr/include -nostdlib -L/usr/lib source.c > =-= and =-= > gcc -nostdlib -L/usr/lib source.c > > and again I received..... > /var/tmp/ccdgopIG.o: Undefined symbol `___main' referenced from text segment > /var/tmp/ccdgopIG.o: Undefined symbol `_printf' referenced from text segment > /var/tmp/ccdgopIG.o: Undefined symbol `_printf' referenced from text segment > collect2: ld returned 1 exit status > > Can anyone assist with this? > I need to be able to compile and link a "Hello World" program against a > proprietary > lib dir for my project but for starters I have to make sure my anomolies are not > with the "ld" portion of my build. > > Why doesn't "gcc -nostdlib -L/usr/lib source.c" link properly? I even added > all the .a files with -lnet -lpcap -ledit, so forth.... and it still failed. Because you told it not to link with the standard libraries. You will have to provide a library with a printf function, and a C runtime startup function with at least the functionality of the standard FreeBSD one. If you are trying to build a completely static image for an embedded system or something like that, you might want to install a GCC cross-compiler and binutils. See, for instance, in /usr/ports/devel: *-rtems-binutils *-rtems-gcc etc. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 8:58:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from muncher.iss.net (muncher.iss.net [208.27.178.48]) by hub.freebsd.org (Postfix) with ESMTP id 7C84737B479 for ; Mon, 27 Nov 2000 08:58:07 -0800 (PST) Received: from iss.net (IDENT:ato@localhost [127.0.0.1]) by muncher.iss.net (8.9.3/8.9.3) with ESMTP id LAA21454; Mon, 27 Nov 2000 11:58:01 -0500 Message-ID: <3A229298.9B928795@iss.net> Date: Mon, 27 Nov 2000 11:58:00 -0500 From: Andrew Otwell Organization: ISS X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Steve Kargl Cc: hackers@FreeBSD.ORG Subject: Re: porting Linux application to FreeBSD References: <200011271635.eARGZQw29552@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG same problem. I'm trying though.... bash-2.03$ gcc -static -nostdlib -L/usr/lib \ > -lalias -lalias_p -lc -lc_p -lc_pic -lcalendar -lcalendar_p -lcom_err -lcom_err_p \ > -lcompat -lcompat_p -lcrypt -lcrypt_p -lcurses -lcurses_p \ > -ldialog -ldialog_p -ldisk -ledit -ledit_p -lf2c -lf2c_p -lfl -lfl_p -lftpio \ > -lftpio_p -lg++ -lg++_p -lgcc -lgcc_p -lgcc_pic -lgmp -lgmp_p \ > -lgnuregex -lgnuregex_p -lipx -lipx_p -lkeycap -lkeycap_p -lkvm \ > -lkvm_p -ll -ll_p -lln -lln_p -lm -lm_p -lmd -lmd_p -lmp -lmp_p -lmytinfo \ > -lmytinfo_p -lncurses -lncurses_p -lobjc -lobjc_p -lopie -lopie_p \ > -lpcap -lpcap_p -lreadline -lreadline_p -lrpcsvc -lrpcsvc_p -lscrypt \ > -lscrypt_p -lscsi -lscsi_p -lskey -lskey_p -lss -lss_p -lstdc++ -lstdc++_p > -ltelnet -ltelnet_p -ltermcap -ltermcap_p -ltermlib -ltermlib_p \ > -lutil -lutil_p -lvgl -lvgl_p -lxpg4 -lxpg4_p -ly -ly_p -lz -lz_p \ > test2.c >/var/tmp/ccaCTG6m.o: Undefined symbol `___main' referenced from text segment >/var/tmp/ccaCTG6m.o: Undefined symbol `_printf' referenced from text segment >/var/tmp/ccaCTG6m.o: Undefined symbol `_printf' referenced from text segment >collect2: ld returned 1 exit status bash-2.03$ Steve Kargl wrote: > > Andrew Otwell wrote: > > > > A couple of you answered my first query which gave me.... > > > > gcc -nostdinc -I/includedir -nostdlib -L/libdir source.c > > > > This always failed with either.... > > > > ld: No reference to __DYNAMIC > > collect2: ld returned 1 exit status > > > > info gcc > > gcc -v -static -nostdinc -I/includedir -nostdlib source.c \ > -L/libdir -lfirstlib -lsecondlib .... -lc > > The -v flag will show you all aspects of the linking of > your program. The -static flags make gcc use static linking. > The -nostdlib suppress the normal linking of libraries > usually supplied by the system. This means you have to > explicitly list all libraries on the command including the > standard C library. > > -- > Steve -- Andrew Otwell, MSS Special Ops Recon/Surveillance/Developer desk 678.443.6271, aotwell@iss.net, http://www.iss.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 9:11:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from muncher.iss.net (muncher.iss.net [208.27.178.48]) by hub.freebsd.org (Postfix) with ESMTP id 8B82537B479 for ; Mon, 27 Nov 2000 09:11:18 -0800 (PST) Received: from iss.net (IDENT:ato@localhost [127.0.0.1]) by muncher.iss.net (8.9.3/8.9.3) with ESMTP id MAA21534; Mon, 27 Nov 2000 12:11:16 -0500 Message-ID: <3A2295B4.A23CA0C9@iss.net> Date: Mon, 27 Nov 2000 12:11:16 -0500 From: Andrew Otwell Organization: ISS X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Steve Kargl Cc: hackers@FreeBSD.ORG Subject: Re: porting Linux application to FreeBSD References: <200011271635.eARGZQw29552@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG when I specify "-bloadmap" I get the following output.... int main() { printf("Hello World!!!!!!!\n"); } *Initialization*:1: warning: `__FreeBSD__' redefined *Initialization*:1: warning: this is the location of the previous definition # 1 "/var/tmp/ccWwDByf.i" gcc: installation problem, cannot exec `cc1': No such file or directory gcc: file path prefix `/usr/local/lib/gcc-lib/loadmap/2.95.2/' never used I then ran "locate cc1" and found a binary in /usr/libexec/cc1 "man -k cc1" yields "nothing appropriate". Steve Kargl wrote: > > Andrew Otwell wrote: > > > > A couple of you answered my first query which gave me.... > > > > gcc -nostdinc -I/includedir -nostdlib -L/libdir source.c > > > > This always failed with either.... > > > > ld: No reference to __DYNAMIC > > collect2: ld returned 1 exit status > > > > info gcc > > gcc -v -static -nostdinc -I/includedir -nostdlib source.c \ > -L/libdir -lfirstlib -lsecondlib .... -lc > > The -v flag will show you all aspects of the linking of > your program. The -static flags make gcc use static linking. > The -nostdlib suppress the normal linking of libraries > usually supplied by the system. This means you have to > explicitly list all libraries on the command including the > standard C library. > > -- > Steve -- Andrew Otwell, MSS Special Ops Recon/Surveillance/Developer desk 678.443.6271, aotwell@iss.net, http://www.iss.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 9:53:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from siri.nordier.com (c3-dbn-24.dial-up.net [196.33.200.24]) by hub.freebsd.org (Postfix) with ESMTP id B680337B479 for ; Mon, 27 Nov 2000 09:53:03 -0800 (PST) Received: (from rnordier@localhost) by siri.nordier.com (8.11.1/8.11.1) id eARHqm801966; Mon, 27 Nov 2000 19:52:48 +0200 (SAST) (envelope-from rnordier) From: Robert Nordier Message-Id: <200011271752.eARHqm801966@siri.nordier.com> Subject: Re: porting Linux application to FreeBSD To: aotwell@iss.net (Andrew Otwell) Date: Mon, 27 Nov 2000 19:52:47 +0200 (SAST) Cc: hackers@freebsd.org In-Reply-To: <3A229298.9B928795@iss.net> from "Andrew Otwell" at Nov 27, 2000 11:58:00 AM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Otwell wrote: > same problem. I'm trying though.... > > bash-2.03$ gcc -static -nostdlib -L/usr/lib \ > > -lalias -lalias_p -lc -lc_p -lc_pic -lcalendar -lcalendar_p -lcom_err -lcom_err_p \ > > -lcompat -lcompat_p -lcrypt -lcrypt_p -lcurses -lcurses_p \ > > -ldialog -ldialog_p -ldisk -ledit -ledit_p -lf2c -lf2c_p -lfl -lfl_p -lftpio \ > > -lftpio_p -lg++ -lg++_p -lgcc -lgcc_p -lgcc_pic -lgmp -lgmp_p \ > > -lgnuregex -lgnuregex_p -lipx -lipx_p -lkeycap -lkeycap_p -lkvm \ > > -lkvm_p -ll -ll_p -lln -lln_p -lm -lm_p -lmd -lmd_p -lmp -lmp_p -lmytinfo \ > > -lmytinfo_p -lncurses -lncurses_p -lobjc -lobjc_p -lopie -lopie_p \ > > -lpcap -lpcap_p -lreadline -lreadline_p -lrpcsvc -lrpcsvc_p -lscrypt \ > > -lscrypt_p -lscsi -lscsi_p -lskey -lskey_p -lss -lss_p -lstdc++ -lstdc++_p > > -ltelnet -ltelnet_p -ltermcap -ltermcap_p -ltermlib -ltermlib_p \ > > -lutil -lutil_p -lvgl -lvgl_p -lxpg4 -lxpg4_p -ly -ly_p -lz -lz_p \ > > test2.c > >/var/tmp/ccaCTG6m.o: Undefined symbol `___main' referenced from text segment > >/var/tmp/ccaCTG6m.o: Undefined symbol `_printf' referenced from text segment > >/var/tmp/ccaCTG6m.o: Undefined symbol `_printf' referenced from text segment > >collect2: ld returned 1 exit status > bash-2.03$ From the look of it, either your toolchain is mis-configured or you're generating the wrong object format. You should be seeing something like this (note lack of underscore): /tmp/ccmb1952.o: In function `main': /tmp/ccmb1952.o(.text+0xf): undefined reference to `printf' I think you mentioned somewhere you're generating ELF (not a.out); if so, your compiler is not doing the right thing for external symbols. What appeared in FreeBSD a.out libraries as "_printf" is plain "printf" in ELF. There is no "_printf" symbol in the standard FreeBSD libc, nowadays. -- Robert Nordier rnordier@nordier.com rnordier@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 9:58:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 85C9C37B479 for ; Mon, 27 Nov 2000 09:58:49 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eARHwnY06198; Mon, 27 Nov 2000 09:58:49 -0800 (PST) Date: Mon, 27 Nov 2000 09:58:48 -0800 From: Alfred Perlstein To: Matt Dillon Cc: hackers@FreeBSD.ORG Subject: Re: bwillwrite() not right. Message-ID: <20001127095848.E8051@fw.wintelcom.net> References: <20001126232117.C8051@fw.wintelcom.net> <200011270853.eAR8rH229425@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: <200011270853.eAR8rH229425@earth.backplane.com>; from dillon@earth.backplane.com on Mon, Nov 27, 2000 at 12:53:17AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matt Dillon [001127 00:53] wrote: > :bwillwrite() is called in kern/sys_generic.c:dofilewrite() > : > :bwillwrite() is meant as a quick stop before doing any vnode > :ops to flush dirty buffers to prevent a deadlock. > : > :However: > :1) afaik only VNODES have backing buffers, so stalling socket/pipes > : doesn't gain us anything > :2) writev() doesn't call bwillwrite() > : > :shouldn't the code be changed like so: > > Hmm.. Well, your suggestion is certainly better then what it is doing > now. bwillwrite() is somewhat of a hack, I just haven't gotten around > to replacing it with something better. What it is approximating is an > attempt to block on low-memory prior to locking a vnode so we do not > wind up blocking on low-memory later on when the lock is being held > (which could prevent the pageout daemon from paging pages associated > with that vnode out, thus causing a deadlock). > > When you feel comfortable with it in your own testing, go ahead and > commit it to -current. But give it at least a good week's worth of > testing (or longer) before MFCing it to -stable. Hrm, on further thought bwillwrite would be helpful for sockets when the free mbufs gets low, but for now I'll just test this patch and probably have it committed by tomorrow night. thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 10:12:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id DE31537B479 for ; Mon, 27 Nov 2000 10:12:09 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eARIC0G31791; Mon, 27 Nov 2000 10:12:00 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Nov 2000 10:12:00 -0800 (PST) From: Matt Dillon Message-Id: <200011271812.eARIC0G31791@earth.backplane.com> To: Alfred Perlstein Cc: hackers@FreeBSD.ORG Subject: Re: bwillwrite() not right. References: <20001126232117.C8051@fw.wintelcom.net> <200011270853.eAR8rH229425@earth.backplane.com> <20001127095848.E8051@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hrm, on further thought bwillwrite would be helpful for sockets when :the free mbufs gets low, but for now I'll just test this patch :and probably have it committed by tomorrow night. : :thanks, :-Alfred Well, maybe maybe not. If you have a TCP socket with data flowing in both directions and you block in your write due to a low-mbuf situation, you effectively prevent the process from draining the receive side of the socket. So I would say you definitely do not want any sort of bwillwrite() equivalent for writing to socket mbufs, at least not for TCP connections. What I would do instead is allow the socket write to continue (remember, 'I/O must be able to continue to operate'), but constrict the sending buffer size as it drains to try to recover some memory on the write side. On the receive side the receiving window can only be constricted when allowed by the protocol. i.e. if you advertise 8K of buffer space you cannot blow it back to 4K... you have to wait for 4K of data to be received before you can advertise 4K of buffer space available. On the receiving side. I seem to recall that there is already some code to handle that sort of thing, but I haven't looked at it closely. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 14:10:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from auchroisk.pdl.cs.cmu.edu (AUCHROISK.PDL.CS.CMU.EDU [128.2.189.63]) by hub.freebsd.org (Postfix) with ESMTP id 3116937B4C5; Mon, 27 Nov 2000 14:10:37 -0800 (PST) Received: (from dpetrou@localhost) by auchroisk.pdl.cs.cmu.edu (8.9.3/8.9.3) id RAA00845; Mon, 27 Nov 2000 17:10:31 -0500 (EST) Date: Mon, 27 Nov 2000 17:10:31 -0500 From: David Petrou To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: thread model questions Message-ID: <20001127171031.D417@auchroisk.pdl.cs.cmu.edu> Reply-To: dpetrou@cs.cmu.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us X-Hit-Pick: Rush / Exit ... Stage Left Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi. i've searched the handbook, tutorial, FAQ, and parts of the mailing list archives but haven't found direct answers to the following questions. i hope you don't mind answering them for me; it will save me a lot of time looking through the code, and / or writing test cases: let's say i'm running 4.x-stable. 1. if i use the pthreads interface, is each thread a process that happens to share the same addr space (like linux), or are all the threads part of the same single process (same PID)? 2. is the threading preemptive? or do i have to explicitly yield? 3. if preemptive, does that occur at user-level, or by the kernel? (and how costly is it?) 4. if one thread makes a system call that could block for some time, will another thread be automatically chosen? or will the whole collection of threads sleep until the call returns? 5. if i signal a particular thread, is the signal delivered to one thread or to all the threads in the process? 6. if a thread or process (terminology sucks) enters the kernel, can the scheduler preempt it and select another thread / process to run? (q.v., what many people call having kernel threads.) or will that process / thread dominate the system until it voluntarily relinquishes the processor? 7. are there other threads interfaces besides pthreads that i should be aware of? what are the differences? e.g., assuming freebsd supports a clone()-like interface, do some threads packages use it while others do as much as they can without kernel support? i'm probably forgetting some questions, but these are the bulk. i'm just wondering what the current thread model is as i contemplate moving my development to FreeBSD. thanks, david p.s.: please include me in any responses as i'm not subscribed to FreeBSD lists at the moment. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 14:27:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id B821E37B4CF for ; Mon, 27 Nov 2000 14:27:26 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eARMRMn15672; Mon, 27 Nov 2000 14:27:22 -0800 (PST) Date: Mon, 27 Nov 2000 14:27:22 -0800 From: Alfred Perlstein To: David Petrou Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: thread model questions Message-ID: <20001127142722.Q8051@fw.wintelcom.net> References: <20001127171031.D417@auchroisk.pdl.cs.cmu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001127171031.D417@auchroisk.pdl.cs.cmu.edu>; from dpetrou@cs.cmu.edu on Mon, Nov 27, 2000 at 05:10:31PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * David Petrou [001127 14:10] wrote: > hi. i've searched the handbook, tutorial, FAQ, and parts of the > mailing list archives but haven't found direct answers to the > following questions. i hope you don't mind answering them for me; it > will save me a lot of time looking through the code, and / or writing > test cases: > > let's say i'm running 4.x-stable. > > 1. if i use the pthreads interface, is each thread a process that > happens to share the same addr space (like linux), or are all the > threads part of the same single process (same PID)? The latter. > 2. is the threading preemptive? or do i have to explicitly yield? Former. > 3. if preemptive, does that occur at user-level, or by the kernel? > (and how costly is it?) It's a mix, and very cheap. > 4. if one thread makes a system call that could block for some time, > will another thread be automatically chosen? or will the whole > collection of threads sleep until the call returns? Latter. However our threads model wraps most syscalls so that you shouldn't block, you can still block on disk IO, however I have a proposal that I (or someone else) might implement in the near future to fix this. > 5. if i signal a particular thread, is the signal delivered to one > thread or to all the threads in the process? We should follow the pthreads standard for this, check the standard. > 6. if a thread or process (terminology sucks) enters the kernel, can > the scheduler preempt it and select another thread / process to > run? (q.v., what many people call having kernel threads.) or will > that process / thread dominate the system until it voluntarily > relinquishes the processor? Latter. > 7. are there other threads interfaces besides pthreads that i should > be aware of? what are the differences? e.g., assuming freebsd > supports a clone()-like interface, do some threads packages use it > while others do as much as they can without kernel support? the native threads are what conforms to the answers I have you above, there's a port called "linux-threads" in the ports collection to do what Linux does (clone()-like pid-per-thread) > i'm probably forgetting some questions, but these are the bulk. i'm > just wondering what the current thread model is as i contemplate > moving my development to FreeBSD. Well you have a choice between our threads model and the Linux model on FreeBSD. I've been contemplating some changes that would speed up our threads with regards to disk/IO, but that's a way off. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 14:30:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relayout1.micronpc.com (meihost.micronpc.com [209.19.139.2]) by hub.freebsd.org (Postfix) with ESMTP id B583237B479 for ; Mon, 27 Nov 2000 14:30:38 -0800 (PST) Received: from mei00wssout01.micron.com (mei00wssout01.micronpc.com [172.30.41.216]) by relayout1.micronpc.com (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with SMTP id PAA11920 for ; Mon, 27 Nov 2000 15:30:35 -0700 Received: from 172.30.41.146 by mei00wssout01.micron.com with ESMTP ( WorldSecure Server SMTP Relay(WSS) v4.5); Mon, 27 Nov 2000 15:30:37 -0700 X-Server-Uuid: 6b1d535a-5b27-11d3-bf09-00902786a6a3 Received: by imcout1.micronpc.com with Internet Mail Service ( 5.5.2650.21) id ; Mon, 27 Nov 2000 15:30:36 -0700 Message-ID: <8D18712B2604D411A6BB009027F6449807192A@0SEA01EXSRV1> From: "Russell Hay" To: "'freebsd-hackers@freebsd.org'" Subject: RLIMIT_DATA resource limiting.. Date: Mon, 27 Nov 2000 15:30:30 -0700 X-Mailer: Internet Mail Service (5.5.2650.21) MIME-Version: 1.0 X-WSS-ID: 163C3F07257729-01-01 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG HI, I'm looking for the place where the RLIMIT_DATA field in the proc structure is being updated during memory allocation and de-allocation. I have searched through the kernel source (and the source for all installed files) and have not be able to find the location of this. If anyone can point me in the right direction that would be wonderful :) Thanks in advance, -rch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 14:41:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from auchroisk.pdl.cs.cmu.edu (AUCHROISK.PDL.CS.CMU.EDU [128.2.189.63]) by hub.freebsd.org (Postfix) with ESMTP id 7DD8D37B479 for ; Mon, 27 Nov 2000 14:41:28 -0800 (PST) Received: (from dpetrou@localhost) by auchroisk.pdl.cs.cmu.edu (8.9.3/8.9.3) id RAA00978; Mon, 27 Nov 2000 17:41:21 -0500 (EST) Date: Mon, 27 Nov 2000 17:41:21 -0500 From: David Petrou To: Alfred Perlstein Cc: David Petrou , freebsd-hackers@FreeBSD.ORG Subject: Re: thread model questions Message-ID: <20001127174120.G417@auchroisk.pdl.cs.cmu.edu> Reply-To: dpetrou@cs.cmu.edu References: <20001127171031.D417@auchroisk.pdl.cs.cmu.edu> <20001127142722.Q8051@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <20001127142722.Q8051@fw.wintelcom.net>; from bright@wintelcom.net on Mon, Nov 27, 2000 at 02:27:22PM -0800 X-Hit-Pick: Naicin Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG thanks for the quick reply... > > 3. if preemptive, does that occur at user-level, or by the kernel? > > (and how costly is it?) > > It's a mix, and very cheap. sounds pretty neat. is there a design document somewhere where i can read up on this for fun? > > 4. if one thread makes a system call that could block for some time, > > will another thread be automatically chosen? or will the whole > > collection of threads sleep until the call returns? > > Latter. However our threads model wraps most syscalls so that you > shouldn't block, you can still block on disk IO, however I have > a proposal that I (or someone else) might implement in the near > future to fix this. i think what you're saying is that for most of the cases, libc_r will do the right thing when you make a syscall (like network I/O??). but there are some cases like disk I/O where all the threads in the process will block. presumably, if it these latter cases are a bottleneck, someone will fix it, as you may fix the disk I/O case. > > 6. if a thread or process (terminology sucks) enters the kernel, can > > the scheduler preempt it and select another thread / process to > > run? (q.v., what many people call having kernel threads.) or will > > that process / thread dominate the system until it voluntarily > > relinquishes the processor? > > Latter. hmm. so if i were writing a kernel module, i'd need to be careful to not do too much work at a time. i assume you don't preempt processes in the kernel because there are data structures that aren't properly protected from such preemption. but won't you have to let more than one proc in the kernel at the time to get scalable smp performance? so eventually, the synchronization would have to go in. so when that happens, even on a uniprocessor, i won't be able to depend on "owning" the kernel when i'm in it. if i was right up to here, then it follows that if i want my code to work in the future, i should do the synch necessary to ensure my own code is reentrant. > > 7. are there other threads interfaces besides pthreads that i should > > be aware of? what are the differences? e.g., assuming freebsd > > supports a clone()-like interface, do some threads packages use it > > while others do as much as they can without kernel support? > > the native threads are what conforms to the answers I have you above, > there's a port called "linux-threads" in the ports collection to > do what Linux does (clone()-like pid-per-thread) does linux-threads on freebsd allow preemption of processes in the kernel? i assume the answer is no, but you didn't explicitly say so. > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] thanks, david To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 15: 9:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E7D2937B479 for ; Mon, 27 Nov 2000 15:09:18 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eARN9Gr16993; Mon, 27 Nov 2000 15:09:16 -0800 (PST) Date: Mon, 27 Nov 2000 15:09:16 -0800 From: Alfred Perlstein To: David Petrou Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: thread model questions Message-ID: <20001127150916.R8051@fw.wintelcom.net> References: <20001127171031.D417@auchroisk.pdl.cs.cmu.edu> <20001127142722.Q8051@fw.wintelcom.net> <20001127174120.G417@auchroisk.pdl.cs.cmu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001127174120.G417@auchroisk.pdl.cs.cmu.edu>; from dpetrou@cs.cmu.edu on Mon, Nov 27, 2000 at 05:41:21PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * David Petrou [001127 14:41] wrote: > thanks for the quick reply... > > > > 3. if preemptive, does that occur at user-level, or by the kernel? > > > (and how costly is it?) > > > > It's a mix, and very cheap. > > sounds pretty neat. is there a design document somewhere where i can > read up on this for fun? Not really, it's basically like most other userland thread packages out there but it is preemptive which a lot of the others aren't. > > > 4. if one thread makes a system call that could block for some time, > > > will another thread be automatically chosen? or will the whole > > > collection of threads sleep until the call returns? > > > > Latter. However our threads model wraps most syscalls so that you > > shouldn't block, you can still block on disk IO, however I have > > a proposal that I (or someone else) might implement in the near > > future to fix this. > > i think what you're saying is that for most of the cases, libc_r will > do the right thing when you make a syscall (like network I/O??). but > there are some cases like disk I/O where all the threads in the > process will block. presumably, if it these latter cases are a > bottleneck, someone will fix it, as you may fix the disk I/O case. Yes, here's the general idea of what I'd like to accomplish: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=130042+132666+/usr/local/www/db/text/2000/freebsd-arch/20001119.freebsd-arch Use aio to handle disk access, an accomplished coder could probably get the aio stuff done pretty fast, the hard part is the SIGFAULT where the kernel allows the userland to ask for faults to be serviced (through aio?) rather than servicing them automagically. > > > 6. if a thread or process (terminology sucks) enters the kernel, can > > > the scheduler preempt it and select another thread / process to > > > run? (q.v., what many people call having kernel threads.) or will > > > that process / thread dominate the system until it voluntarily > > > relinquishes the processor? > > > > Latter. > > hmm. so if i were writing a kernel module, i'd need to be careful to > not do too much work at a time. > > i assume you don't preempt processes in the kernel because there are > data structures that aren't properly protected from such preemption. > but won't you have to let more than one proc in the kernel at the time > to get scalable smp performance? In the -current branch we're approaching this, data structures are slowly being locked down. see: http://people.freebsd.org/~jasone/smp/ > so eventually, the synchronization > would have to go in. so when that happens, even on a uniprocessor, i > won't be able to depend on "owning" the kernel when i'm in it. if i > was right up to here, then it follows that if i want my code to work > in the future, i should do the synch necessary to ensure my own code > is reentrant. I'm suprised at how stable -current is at the moment, you should develop with it in mind and get yourself familiar with the smp primatives if you expect your kernel work to survive a 4.x->5.x transition. We do allow more than one process in the kernel, but only one process can be executing, meaning if a kernel thread sleeps on a resource another process can make headway in some other (or the same) codepath. > > > 7. are there other threads interfaces besides pthreads that i should > > > be aware of? what are the differences? e.g., assuming freebsd > > > supports a clone()-like interface, do some threads packages use it > > > while others do as much as they can without kernel support? > > > > the native threads are what conforms to the answers I have you above, > > there's a port called "linux-threads" in the ports collection to > > do what Linux does (clone()-like pid-per-thread) > > does linux-threads on freebsd allow preemption of processes in the > kernel? i assume the answer is no, but you didn't explicitly say so. I think you're placing a bit too much emphasis on this problem, we hope to have a pre-emptable kernel in the 5.x releases. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 15: 9:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kira.epconline.net (kira.epconline.net [209.83.132.2]) by hub.freebsd.org (Postfix) with ESMTP id B3DD337B479 for ; Mon, 27 Nov 2000 15:09:27 -0800 (PST) Received: from therock (betterguard.epconline.net [209.83.132.193]) by kira.epconline.net (8.9.3/8.9.3) with SMTP id RAA09981 for ; Mon, 27 Nov 2000 17:09:23 -0600 (CST) Reply-To: From: "Chuck Rock" To: "FreeBSD Hackers" Subject: Couple of config questions... Date: Mon, 27 Nov 2000 17:11:20 -0600 Message-ID: <00d901c058c7$5a45bd70$1805010a@epconline.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a fresh install of FreeBSD on a server with 512 Meg of RAM. this is what's in dmesg... real memory = 536870912 (524288K bytes) avail memory = 518627328 (506472K bytes) and this is what shows in top Mem: 51M Active, 371M Inact, 43M Wired, 13M Cache, 61M Buf, 24M Free I read a while back on another list that inactive memory was bad because of speed or something. Is there a way to get more memory activated, or is this normal and by design? Second question was... Is there a way to get syslog to put time and date into the dmesg file? This is a real pain in the !@# when trying to find out what causes problems, and the only logging available is from dmesg. Logging to the console with date and time would also be VERY appreciated. Thanks, Chuck Rock EPC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 16: 9: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.unixbox.com (shell.unixbox.com [207.211.45.65]) by hub.freebsd.org (Postfix) with ESMTP id A46EF37B4C5 for ; Mon, 27 Nov 2000 16:09:04 -0800 (PST) Received: from localhost (fengyue@localhost) by shell.unixbox.com (8.11.1/8.11.0) with ESMTP id eAS0An931632; Mon, 27 Nov 2000 16:10:49 -0800 (PST) Date: Mon, 27 Nov 2000 16:10:49 -0800 (PST) From: FengYue X-Sender: fengyue@shell.unixbox.com To: Alfred Perlstein Cc: David Petrou , freebsd-hackers@FreeBSD.ORG Subject: Re: thread model questions In-Reply-To: <20001127150916.R8051@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Nov 2000, Alfred Perlstein wrote: ->* David Petrou [001127 14:41] wrote: ->> thanks for the quick reply... ->> ->> > > 3. if preemptive, does that occur at user-level, or by the kernel? ->> > > (and how costly is it?) ->> > ->> > It's a mix, and very cheap. I thought it's preemptive purely at user-level since the threads are scheduled by thread lib at user-level only. No? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 16:29:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail0.mco.bellsouth.net (mail0.mco.bellsouth.net [205.152.111.12]) by hub.freebsd.org (Postfix) with ESMTP id EE31037B4C5 for ; Mon, 27 Nov 2000 16:29:26 -0800 (PST) Received: from bellsouth.net (host-216-78-93-15.jax.bellsouth.net [216.78.93.15]) by mail0.mco.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id TAA06682 for ; Mon, 27 Nov 2000 19:29:25 -0500 (EST) Message-ID: <3A22FC60.F88FEB5F@bellsouth.net> Date: Mon, 27 Nov 2000 19:29:20 -0500 From: Ted Knight Reply-To: efknight@bellsouth.net X-Mailer: Mozilla 4.76 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: 3Com at home pci internal DSL Modem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG DSL has now become available to me through Bellsouth.net, my ISP. They are now primarily providing the 3Com at home PCI internal DSL modem for self-install. From what I read most Baby Bells are switching to this card. It appears they are using PPPoA. Is there, by any chance, work being done to develop a driver for this device for FreeBSD? I have spoken to Bellsouth.net about getting an Alcatel Speed Touch external to use with a NIC, they won't do it. Thanks, Ted Knight To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 16:39:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id F3F1337B479 for ; Mon, 27 Nov 2000 16:39:54 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAS0dmN19733; Mon, 27 Nov 2000 16:39:48 -0800 (PST) Date: Mon, 27 Nov 2000 16:39:48 -0800 From: Alfred Perlstein To: FengYue Cc: David Petrou , freebsd-hackers@FreeBSD.ORG Subject: Re: thread model questions Message-ID: <20001127163948.S8051@fw.wintelcom.net> References: <20001127150916.R8051@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from fengyue@bluerose.windmoon.nu on Mon, Nov 27, 2000 at 04:10:49PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * FengYue [001127 16:08] wrote: > > On Mon, 27 Nov 2000, Alfred Perlstein wrote: > > ->* David Petrou [001127 14:41] wrote: > ->> thanks for the quick reply... > ->> > ->> > > 3. if preemptive, does that occur at user-level, or by the kernel? > ->> > > (and how costly is it?) > ->> > > ->> > It's a mix, and very cheap. > > I thought it's preemptive purely at user-level since the threads are > scheduled by thread lib at user-level only. No? What are you asking? Give a scenario and I'll explain what should happen. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 18:48:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 7F2E037B479 for ; Mon, 27 Nov 2000 18:48:35 -0800 (PST) Received: from bellatlantic.net (client-151-198-135-12.nnj.dialup.bellatlantic.net [151.198.135.12]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id VAA15563 for ; Mon, 27 Nov 2000 21:48:32 -0500 (EST) Message-ID: <3A231CFE.3CF457F8@bellatlantic.net> Date: Mon, 27 Nov 2000 21:48:30 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: hackers@freebsd.org Subject: Win4Lin - yet another virtual machine to run Windows Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All, I've noticed in InfoWorld a mention of a new Windows emulation product for Linux, Wind4Lin. So I went on their web-site http://www.netraverse.com/ The problem is that their stuff seems to be strongly tied to the Linux kernel, and they provide a whole lot of sub-versions for various Linux distributions. So I've sent them e-mail asking if they plan to add FreeBSD support. The answer I got is that they are not sure if there is a big enough market on FreeBSD, up to now they got less than 100 requests for a port. So if you think that their product may be something interesting for you, please send e-mail to and show up as a potential buyer! -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 19:33:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from auchroisk.pdl.cs.cmu.edu (AUCHROISK.PDL.CS.CMU.EDU [128.2.189.63]) by hub.freebsd.org (Postfix) with ESMTP id 5E3E337B4C5; Mon, 27 Nov 2000 19:33:25 -0800 (PST) Received: (from dpetrou@localhost) by auchroisk.pdl.cs.cmu.edu (8.9.3/8.9.3) id WAA01476; Mon, 27 Nov 2000 22:33:23 -0500 (EST) Date: Mon, 27 Nov 2000 22:33:22 -0500 From: David Petrou To: David Petrou Cc: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: thread model questions Message-ID: <20001127223322.B1353@auchroisk.pdl.cs.cmu.edu> Reply-To: dpetrou@cs.cmu.edu References: <20001127171031.D417@auchroisk.pdl.cs.cmu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <20001127171031.D417@auchroisk.pdl.cs.cmu.edu>; from dpetrou@cs.cmu.edu on Mon, Nov 27, 2000 at 05:10:31PM -0500 X-Hit-Pick: My Superhero / SKAteboard Music (Rerelease) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > hi. i've searched the handbook, tutorial, FAQ, and parts of the > mailing list archives but haven't found direct answers to the > following questions. i hope you don't mind answering them for me; it > will save me a lot of time looking through the code, and / or writing > test cases: john milford pointed me to the following web page that answers most of my previous questions concerning the freebsd threading model and gives a whole lot of other useful information on the topic. i thought there might be some others that don't know of it, so here it is: http://people.freebsd.org/~jasone/refs/freebsd_kse/freebsd_kse.html david To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 19:42:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 2632E37B4D7 for ; Mon, 27 Nov 2000 19:42:24 -0800 (PST) Received: from newsguy.com (p15-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.80]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id MAA07726; Tue, 28 Nov 2000 12:42:15 +0900 (JST) Message-ID: <3A232657.946EBB25@newsguy.com> Date: Tue, 28 Nov 2000 12:28:23 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: carock@epctech.com Cc: FreeBSD Hackers Subject: Re: Couple of config questions... References: <00d901c058c7$5a45bd70$1805010a@epconline.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Rock wrote: > > Mem: 51M Active, 371M Inact, 43M Wired, 13M Cache, 61M Buf, 24M Free > > I read a while back on another list that inactive memory was bad because of > speed or something. Is there a way to get more memory activated, or is this > normal and by design? Must have been a Linux mailing list... :-) They do things differently there, it seems. Inactive memory is fine. It means simply that some piece of data read from disk is no longer used by anything and is available for immediate use, *but*, can be "reinstated" to it's content (ie, work as cache). > Second question was... > > Is there a way to get syslog to put time and date into the dmesg file? This > is a real pain in the !@# when trying to find out what causes problems, and > the only logging available is from dmesg. Logging to the console with date > and time would also be VERY appreciated. Not that I know of. It should be a quick hack to implement, though. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@united.bsdconspiracy.net "All right, Lieutenant, let's see what you do know. Whatever it is, it's not enough, but at least you haven't done anything stupid yet." "I've hardly had time, sir." "There's a naive statement." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 19:49:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-187.dsl.snfc21.pacbell.net [63.202.177.187]) by hub.freebsd.org (Postfix) with ESMTP id D213937B479 for ; Mon, 27 Nov 2000 19:49:17 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAS3ulF23058; Mon, 27 Nov 2000 19:56:47 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011280356.eAS3ulF23058@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Sergey Babkin Cc: hackers@freebsd.org Subject: Re: Win4Lin - yet another virtual machine to run Windows In-reply-to: Your message of "Mon, 27 Nov 2000 21:48:30 EST." <3A231CFE.3CF457F8@bellatlantic.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Nov 2000 19:56:47 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I spoke to these folks at Linuxworld about 18 months ago. AFAIR, their product is basically a port of SCO's DOS/Merge, and the ABI between the userspace and kernelspace components is fairly well understood. The amount of work involved in making it run on FreeBSD would probably be comparable to the work involved in the VMware port (ie. reasonable but not excessive). > I've noticed in InfoWorld a mention of a new Windows emulation > product for Linux, Wind4Lin. So I went on their web-site > > http://www.netraverse.com/ > > The problem is that their stuff seems to be strongly tied to the > Linux kernel, and they provide a whole lot of sub-versions for > various Linux distributions. > > So I've sent them e-mail asking if they plan to add FreeBSD support. > The answer I got is that they are not sure if there is a big enough > market on FreeBSD, up to now they got less than 100 requests for > a port. So if you think that their product may be something > interesting for you, please send e-mail to > and show up as a potential buyer! > > -SB > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 20: 2:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from thelab.hub.org (CDR22-173.accesscable.net [24.138.22.173]) by hub.freebsd.org (Postfix) with ESMTP id 9034137B4D7; Mon, 27 Nov 2000 20:02:27 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id eAS41wF01706; Tue, 28 Nov 2000 00:01:58 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 28 Nov 2000 00:01:58 -0400 (AST) From: The Hermit Hacker To: Mike Smith Cc: Sergey Babkin , hackers@FreeBSD.ORG Subject: Re: Win4Lin - yet another virtual machine to run Windows In-Reply-To: <200011280356.eAS3ulF23058@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG well, I sent in my vote for a FreeBSD port ... if I can avoid having to reboot into Windows so that I can use some of the win business apps, and all for <$100, I'd be happy ... On Mon, 27 Nov 2000, Mike Smith wrote: > > I spoke to these folks at Linuxworld about 18 months ago. AFAIR, their > product is basically a port of SCO's DOS/Merge, and the ABI between the > userspace and kernelspace components is fairly well understood. > > The amount of work involved in making it run on FreeBSD would probably be > comparable to the work involved in the VMware port (ie. reasonable but > not excessive). > > > I've noticed in InfoWorld a mention of a new Windows emulation > > product for Linux, Wind4Lin. So I went on their web-site > > > > http://www.netraverse.com/ > > > > The problem is that their stuff seems to be strongly tied to the > > Linux kernel, and they provide a whole lot of sub-versions for > > various Linux distributions. > > > > So I've sent them e-mail asking if they plan to add FreeBSD support. > > The answer I got is that they are not sure if there is a big enough > > market on FreeBSD, up to now they got less than 100 requests for > > a port. So if you think that their product may be something > > interesting for you, please send e-mail to > > and show up as a potential buyer! > > > > -SB > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 20: 6:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from thelab.hub.org (CDR22-173.accesscable.net [24.138.22.173]) by hub.freebsd.org (Postfix) with ESMTP id 2868137B479; Mon, 27 Nov 2000 20:06:46 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id eAS41wF01706; Tue, 28 Nov 2000 00:01:58 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 28 Nov 2000 00:01:58 -0400 (AST) From: The Hermit Hacker To: Mike Smith Cc: Sergey Babkin , hackers@FreeBSD.ORG Subject: Re: Win4Lin - yet another virtual machine to run Windows In-Reply-To: <200011280356.eAS3ulF23058@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 20:10:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-c.mdsn1.wi.home.com [24.183.3.139]) by hub.freebsd.org (Postfix) with ESMTP id 69E2437B4D7 for ; Mon, 27 Nov 2000 20:10:13 -0800 (PST) Received: (qmail 53519 invoked by uid 1000); 28 Nov 2000 04:10:11 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 28 Nov 2000 04:10:11 -0000 Date: Mon, 27 Nov 2000 22:10:11 -0600 (CST) From: Mike Silbersack To: Mike Smith Cc: Sergey Babkin , hackers@freebsd.org Subject: Re: Win4Lin - yet another virtual machine to run Windows In-Reply-To: <200011280356.eAS3ulF23058@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Nov 2000, Mike Smith wrote: > > I spoke to these folks at Linuxworld about 18 months ago. AFAIR, their > product is basically a port of SCO's DOS/Merge, and the ABI between the > userspace and kernelspace components is fairly well understood. > > The amount of work involved in making it run on FreeBSD would probably be > comparable to the work involved in the VMware port (ie. reasonable but > not excessive). Do you have any idea how easy it would be to get plex86 to run on FreeBSD? From what I saw on slashdot the other day, they now have Windows running under it. If so, a port would make lin4win vs vmware a moot discussion. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 20:24:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-187.dsl.snfc21.pacbell.net [63.202.177.187]) by hub.freebsd.org (Postfix) with ESMTP id 8384B37B4C5 for ; Mon, 27 Nov 2000 20:24:19 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAS4VaF23169; Mon, 27 Nov 2000 20:31:37 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011280431.eAS4VaF23169@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Silbersack Cc: Sergey Babkin , hackers@freebsd.org Subject: Re: Win4Lin - yet another virtual machine to run Windows In-reply-to: Your message of "Mon, 27 Nov 2000 22:10:11 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Nov 2000 20:31:36 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I spoke to these folks at Linuxworld about 18 months ago. AFAIR, their > > product is basically a port of SCO's DOS/Merge, and the ABI between the > > userspace and kernelspace components is fairly well understood. > > > > The amount of work involved in making it run on FreeBSD would probably be > > comparable to the work involved in the VMware port (ie. reasonable but > > not excessive). > > Do you have any idea how easy it would be to get plex86 to run on > FreeBSD? From what I saw on slashdot the other day, they now have Windows > running under it. If so, a port would make lin4win vs vmware a moot > discussion. It's unlikely that plex86 will make VMware or Trelos' product "moot discussions" anytime soon; Bochs/Freemware/Plex86 is a credible start, but would have a great deal of ground to cover before getting to that point. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 21:16:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hand.dotat.at (sfo-gw.covalent.net [207.44.198.62]) by hub.freebsd.org (Postfix) with ESMTP id F403537B4C5 for ; Mon, 27 Nov 2000 21:16:56 -0800 (PST) Received: from fanf by hand.dotat.at with local (Exim 3.15 #3) id 140d84-000DeP-00 for hackers@FreeBSD.org; Tue, 28 Nov 2000 05:16:32 +0000 From: Tony Finch To: hackers@FreeBSD.org Subject: psm and PNPBIOS Message-Id: Date: Tue, 28 Nov 2000 05:16:32 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently got a new machine (DELL Optiplex GX110) which seems to work fine with FreeBSD, except for a small niggle: If I include "options PNPBIOS" in the kernel config the mouse doesn't probe properly, however it works fine on my DELL Latitude CPx laptop. The problem seems to be because of the order in which the devices are listed by the PnP BIOS: on the Latitude, the keyboard controller PNP0303 comes before the PS/2 mouse PNP0f13, so things get probed in an order which works. On the Optiplex, the mouse is listed before the keyboard in the BIOS, so the "unknown PNP device" grabs irq 12 leaving psm unable to allocate its resources. There seems to be some "notyet" code in psm.c which looks relevant, but enabling it with the patch below doesn't do the trick. I guess this is because at the time the probe runs the atkbdc hasn't probed yet so isn't there to attach to. Is there an easy way to fix this? Tony. -- f.a.n.finch dot@dotat.at fanf@covalent.net Chad for President! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 22: 3:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hand.dotat.at (sfo-gw.covalent.net [207.44.198.62]) by hub.freebsd.org (Postfix) with ESMTP id 0F33E37B479 for ; Mon, 27 Nov 2000 22:03:36 -0800 (PST) Received: from fanf by hand.dotat.at with local (Exim 3.15 #3) id 140drC-000FCZ-00 for hackers@FreeBSD.org; Tue, 28 Nov 2000 06:03:10 +0000 Date: Tue, 28 Nov 2000 06:03:10 +0000 From: Tony Finch To: hackers@FreeBSD.org Subject: Re: psm and PNPBIOS Message-ID: <20001128060310.A58294@hand.dotat.at> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: Organization: Covalent Technologies, Inc Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tony Finch wrote: > >There seems to be some "notyet" code in psm.c which looks relevant, >but enabling it with the patch below doesn't do the trick. I guess >this is because at the time the probe runs the atkbdc hasn't probed >yet so isn't there to attach to. Um. Index: psm.c =================================================================== RCS file: /home/ncvs/src/sys/isa/psm.c,v retrieving revision 1.23.2.4 diff -u -r1.23.2.4 psm.c --- psm.c 2000/08/24 08:50:38 1.23.2.4 +++ psm.c 2000/11/27 22:38:02 @@ -313,13 +313,11 @@ sizeof(struct psm_softc), }; -#if notyet static struct isa_pnp_id psm_ids[] = { { 0x130fd041, "PS/2 mouse port" }, /* PNP0F13 */ { 0x1303d041, "PS/2 port" }, /* PNP0313, XXX */ { 0 } }; -#endif #define CDEV_MAJOR 21 @@ -805,11 +803,9 @@ kbdc_debug(TRUE); #endif -#if notyet /* check PnP IDs */ - if (XXX_PNP_PROBE(device_get_parent(dev), dev, psm_ids) == ENXIO) + if (ISA_PNP_PROBE(device_get_parent(dev), dev, psm_ids) == ENXIO) return ENXIO; -#endif BUS_READ_IVAR(device_get_parent(dev), dev, KBDC_IVAR_IRQ, &irq); BUS_READ_IVAR(device_get_parent(dev), dev, KBDC_IVAR_FLAGS, &flags); Tony. -- f.a.n.finch dot@dotat.at fanf@covalent.net Chad for President! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 22:39: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.au.en-bio.com (swan.en-bio.COM.AU [203.35.254.3]) by hub.freebsd.org (Postfix) with ESMTP id B31E137B400 for ; Mon, 27 Nov 2000 22:38:52 -0800 (PST) Received: from shad.au.int.en-bio.com (www-cache.au.en-bio.com [203.35.254.2]) by swan.au.en-bio.com (8.9.1a/8.9.1) with ESMTP id RAA19298 for ; Tue, 28 Nov 2000 17:38:50 +1100 Received: from pearl.au.int.en-bio.COM (pearl.au.int.en-bio.COM [192.168.42.108]) by shad.au.int.en-bio.com (8.9.1b+Sun/8.9.1) with ESMTP id RAA20060 for ; Tue, 28 Nov 2000 17:39:09 +1100 (EST) Received: from localhost (chuynh@localhost) by pearl.au.int.en-bio.COM (8.11.1/8.9.3) with ESMTP id eAS6cJR37274 for ; Tue, 28 Nov 2000 17:38:19 +1100 (EST) (envelope-from chuynh@pearl.au.int.en-bio.COM) Date: Tue, 28 Nov 2000 17:38:18 +1100 (EST) From: Camson Huynh To: hackers@FreeBSD.ORG Subject: bridge + ipfw Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There seem to be a problem setting up bridge + ipfw using the fxp Intel Pro 100 cards. The problem doesn't exist on NE2000 cards. The same set of ipfw rules and same configuration work on NE2000 cards. Does anybody know if there is a problem with 100Mbit cards, the intel pro in particular or there is a bug with ipfw and bridging? I have fully tested the intel cards and they are functioning ok. I'm currently running FreeBSD 4.2-STABLE. This behaviour happens on FreeBSD 4.2-RELEASE and FreeBSD 4.1X also which prompted me to upgrade to 4.2 stable. My configuration consists of 2 intel pro cards. The external fxp0 has an IP assigned to it where as the internal fxp1 does not. The ipfw rules only allow ssh incoming + icmp packets and deny everything else. Outgoing traffics are not restricted. The behaviour I'm seeing is that I can ping ok. I cannot ssh in but am still able to telnet in !!! My kernel config includes: options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=100 options BRIDGE My firewall rules: ${fwcmd} -f flush ${fwcmd} add 100 check-state ${fwcmd} add 200 pass all from any to any via lo0 ${fwcmd} add 300 deny all from any to 127.0.0.0/8 # If you're using 'options BRIDGE', uncomment the following line to pass ARP ${fwcmd} add 400 pass udp from 0.0.0.0 2054 to 0.0.0.0 # Throw away RFC 1918 networks ${fwcmd} add deny ip from 10.0.0.0/8 to any in via ${oif} ${fwcmd} add deny ip from 172.16.0.0/12 to any in via ${oif} ${fwcmd} add deny ip from 192.168.0.0/16 to any in via ${oif} # Allow the bridge machine to say anything it wants (keep state if UDP) ${fwcmd} add pass udp from ${bridge_ip} to any keep-state ${fwcmd} add pass ip from ${bridge_ip} to any # Allow the inside net to say anything it wants (keep state if UDP) ${fwcmd} add pass udp from any to any in via ${iif} keep-state ${fwcmd} add pass ip from any to any in via ${iif} # Allow all manner of ICMP ${fwcmd} add pass icmp from any to any # established TCP sessions are ok everywhere. ${fwcmd} add pass tcp from any to any established # Pass SSH ${fwcmd} add pass tcp from any to any 22 in via ${oif} # Everything else is denied ${fwcmd} add deny ip from any to any ------------ camson Camson Huynh eBioinformatics - Bay 16 Suite 104 Senior Systems Administrator Australian Technology Park Email: Camson.Huynh@eBioinformatics.com NSW 1430 Australia Ph: +61 2 9209 4749 Fax: +61 2 9209 4747 URL: http://eBioinformatics.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 23:17:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from valu.uninet.ee (valu.uninet.ee [194.204.34.51]) by hub.freebsd.org (Postfix) with ESMTP id 12D2237B401 for ; Mon, 27 Nov 2000 23:17:21 -0800 (PST) Received: by valu.uninet.ee (Postfix, from userid 1002) id AF3B63640E; Tue, 28 Nov 2000 09:17:14 +0200 (EET) Received: from localhost (localhost [127.0.0.1]) by valu.uninet.ee (Postfix) with ESMTP id AD7BB3260D; Tue, 28 Nov 2000 09:17:14 +0200 (EET) Date: Tue, 28 Nov 2000 09:17:14 +0200 (EET) From: Taavi Talvik To: Ted Knight Cc: freebsd-hackers@freebsd.org Subject: Re: 3Com at home pci internal DSL Modem In-Reply-To: <3A22FC60.F88FEB5F@bellsouth.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Nov 2000, Ted Knight wrote: > DSL has now become available to me through Bellsouth.net, my ISP. They > are now primarily providing the 3Com at home PCI internal DSL modem for > self-install. From what I read most Baby Bells are switching to this > card. It appears they are using PPPoA. > > Is there, by any chance, work being done to develop a driver for this > device for FreeBSD? > > I have spoken to Bellsouth.net about getting an Alcatel Speed Touch > external to use with a NIC, they won't do it. 3Com uses IDT77222 Micro Sar for which documentation is readily available (and linux driver). But similar to other internal PCI ADSL modems, it requires ADSL DMT firmware, which is not publicly available. best regards, taavi ----------------------------------------------------------- Taavi Talvik | Internet: taavi@uninet.ee AS Uninet | phone: +372 6405169 Parnu mnt. 105 | fax: +372 6405151 Tallinn 11312, Estonia | gsm: +372 56569996 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Nov 27 23:54:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (jason.argos.org [216.233.245.106]) by hub.freebsd.org (Postfix) with ESMTP id EB44837B401 for ; Mon, 27 Nov 2000 23:54:30 -0800 (PST) Received: from localhost (mike@localhost) by jason.argos.org (8.10.1/8.10.1) with ESMTP id eAS7oSj15725 for ; Tue, 28 Nov 2000 02:50:28 -0500 Date: Tue, 28 Nov 2000 02:50:28 -0500 (EST) From: Mike Nowlin To: freebsd-hackers@freebsd.org Subject: IM server? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This really isn't a (directly) FBSD-related question, but since I'm trying to get everyone at work off MS products over to FBSD workstations, I figure it's appropriate enough to ask here... :) The new guy who came in to start running the company is big on sending documents back and forth via email, shared electronic scheduling, etc. One of his wishes is to get ICQ, AIM, or some other instant messaging capability between employees. Due to the nature of our business, we really can't connect to the "normal" ICQ (etc.) servers on the public network. (Legal reasons, and upper management doesn't want our employees chatting with their friends during work time.) So... Anyone know of a program out there that can act as a central server for ICQ? (I know there's some AIM clones out there, but I'd rather avoid that one...) A quick look in ports and some digging around on Google and Freshmeat didn't return much. --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 0: 0:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (jason.argos.org [216.233.245.106]) by hub.freebsd.org (Postfix) with ESMTP id 3BBAC37B402; Tue, 28 Nov 2000 00:00:45 -0800 (PST) Received: from localhost (mike@localhost) by jason.argos.org (8.10.1/8.10.1) with ESMTP id eAS7umE15959; Tue, 28 Nov 2000 02:56:48 -0500 Date: Tue, 28 Nov 2000 02:56:47 -0500 (EST) From: Mike Nowlin To: Mike Smith Cc: Mike Silbersack , Sergey Babkin , hackers@FreeBSD.ORG Subject: Re: Win4Lin - yet another virtual machine to run Windows In-Reply-To: <200011280431.eAS4VaF23169@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's unlikely that plex86 will make VMware or Trelos' product "moot > discussions" anytime soon; Bochs/Freemware/Plex86 is a credible start, > but would have a great deal of ground to cover before getting to that > point. I got it! FreeBSD running Bochs running VMware running Linux running Win4Lin! On my 40THz 70986 with 200GB of RAM, it works like a champ! :) --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 0: 1:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.klondike.ru (unknown [195.170.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 77DEE37B400 for ; Tue, 28 Nov 2000 00:01:29 -0800 (PST) Received: from freebsd.klondike.ru (freebsd [195.170.237.64]) by ns.klondike.ru (8.9.3/8.9.3) with SMTP id LAA21447 for ; Tue, 28 Nov 2000 11:01:25 +0300 (MSK) Message-Id: <200011280801.LAA21447@ns.klondike.ru> Date: Tue, 28 Nov 2000 11:01:07 +0000 From: Kaltashkin Eugene To: freebsd-hackers@FreeBSD.org Subject: i18n extention in sysinstall X-Mailer: stuphead version 0.4.5 (GTK+ 1.2.8; FreeBSD 4.2-STABLE; i386) Organization: Klondike Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ppls. What dear developers will tell about introduction i18n expansions in sysinstall the utility? It would be convenient for many people to adjust FreeBSD on the native language. Best Regards. ZHECKA-RIPN -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 1: 7:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id 5892737B402; Tue, 28 Nov 2000 01:07:23 -0800 (PST) Received: from mail2.rim.or.jp by serio.al.rim.or.jp (3.7W/HMX-13) id SAA24605; Tue, 28 Nov 2000 18:07:13 +0900 (JST) Received: from localhost.FromTo.Cc (shell [202.247.191.98]) by mail2.rim.or.jp (8.9.3/3.7W) id SAA26940; Tue, 28 Nov 2000 18:07:08 +0900 (JST) Date: Tue, 28 Nov 2000 18:07:05 +0900 Message-ID: <86wvdompmu.wl@ringo.FromTo.Cc> From: Tatsumi Hosokawa To: freebsd-hackers@FreeBSD.org Cc: hosokawa@FreeBSD.org, zhecka@klondike.ru Subject: Re: i18n extention in sysinstall In-Reply-To: In your message of "Tue, 28 Nov 2000 11:01:07 +0000" <200011280801.LAA21447@ns.klondike.ru> References: <200011280801.LAA21447@ns.klondike.ru> User-Agent: Wanderlust/1.1.0 (Overjoyed) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Tue, 28 Nov 2000 11:01:07 +0000, Kaltashkin Eugene wrote: > > What dear developers will tell about introduction i18n expansions in sysinstall the utility? > It would be convenient for many people to adjust FreeBSD on the native language. Latest code is based on 4.2-RELEASE and I'm porting porting it to -current (maybe it's easy). It currently supports Japanese, Korean, Traditional Chinese (translation is incomplete, but no problem about displaying characters), and of coures English. I've not port it to other European languages, but I think it's not difficult. Latest code and binaries are found at: Source - http://people.freebsd.org/~hosokawa/boot-ja/4.2-RELEASE/release-20001128-1/release-20001128-1.tar.gz Binaries - http://people.freebsd.org/~hosokawa/boot-ja/4.2-RELEASE/release-20001128-1/boot_cjk.flp http://people.freebsd.org/~hosokawa/boot-ja/4.2-RELEASE/release-20001128-1/kern_cjk.flp http://people.freebsd.org/~hosokawa/boot-ja/4.2-RELEASE/release-20001128-1/mfsroot_cjk.flp hosokawa -- Tatsumi Hosokawa http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 1:20: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pro.fais.net (unknown [208.249.141.254]) by hub.freebsd.org (Postfix) with ESMTP id 527EF37B400 for ; Tue, 28 Nov 2000 01:20:02 -0800 (PST) Received: from drnet.fais.net (root@drnet.fais.net [208.249.141.31]) by pro.fais.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id EAA15242; Tue, 28 Nov 2000 04:06:22 -0600 Received: from wks01 (wks01.drnet.fais.net [10.64.80.10]) by drnet.fais.net (8.11.0/8.11.0) with SMTP id eAS3Gt734508; Tue, 28 Nov 2000 03:16:57 GMT (envelope-from jwpauler@jwpages.com) Message-ID: <000901c0591b$a15d28c0$0a50400a@drnet.fais.net> From: "Justin W. Pauler" To: "Mike Nowlin" , References: Subject: Re: IM server? Date: Tue, 28 Nov 2000 03:14:33 -0600 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 X-Loop: FreeBSD.ORG http://www.icq.com/groupware/ That is ICQ's free server version. It will allow you to setup a local ICQ network for your users to communicate. From what I read (rather quickly) it gives a few special features, but downloads and uploads will be fast across the network, as well as just regular message sending. have never personally used it, but I have seen it in action. They used a very small 233Mhz box, with 64MB RAM and it was extremely fast. The catch? Yup, not supported with *NIX. I'm not sure at this time if anyone has made a port, but it would be nice. ICQ only right now, supports Windows NT 4.0. -jwp Justin W. Pauler (drnet) E-Mail: jwpauler@jwpages.com ICQ: 95989631 IRC: Undernet IRC Network ----- Original Message ----- From: "Mike Nowlin" To: Sent: Tuesday, November 28, 2000 1:50 AM Subject: IM server? > > This really isn't a (directly) FBSD-related question, but since I'm trying > to get everyone at work off MS products over to FBSD workstations, I > figure it's appropriate enough to ask here... :) > > The new guy who came in to start running the company is big on sending > documents back and forth via email, shared electronic scheduling, > etc. One of his wishes is to get ICQ, AIM, or some other instant > messaging capability between employees. Due to the nature of our > business, we really can't connect to the "normal" ICQ (etc.) servers on > the public network. (Legal reasons, and upper management doesn't want our > employees chatting with their friends during work time.) > > So... > > Anyone know of a program out there that can act as a central server for > ICQ? (I know there's some AIM clones out there, but I'd rather avoid that > one...) A quick look in ports and some digging around on Google and > Freshmeat didn't return much. > > --mike > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 1:26: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 27A3E37B400 for ; Tue, 28 Nov 2000 01:25:45 -0800 (PST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.11.1/8.11.1) with ESMTP id eAS9PDl34044; Tue, 28 Nov 2000 15:25:13 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 28 Nov 2000 15:25:12 +0600 (NS) From: Max Khon To: Mike Nowlin Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: IM server? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Tue, 28 Nov 2000, Mike Nowlin wrote: > Anyone know of a program out there that can act as a central server for > ICQ? (I know there's some AIM clones out there, but I'd rather avoid that > one...) A quick look in ports and some digging around on Google and > Freshmeat didn't return much. http://www.icq.khstu.ru/unix/download/IServerd-0.8.2.tar.gz their homepage is at http://www.icq.khstu.ru/unix/ (sorry, no english version) /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 1:27:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D0B7737B401 for ; Tue, 28 Nov 2000 01:27:45 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAS9RhO03040; Tue, 28 Nov 2000 01:27:43 -0800 (PST) Date: Tue, 28 Nov 2000 01:27:43 -0800 From: Alfred Perlstein To: Mike Nowlin Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: IM server? Message-ID: <20001128012743.B8051@fw.wintelcom.net> 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 mike@argos.org on Tue, Nov 28, 2000 at 02:50:28AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Mike Nowlin [001127 23:54] wrote: > > This really isn't a (directly) FBSD-related question, but since I'm trying > to get everyone at work off MS products over to FBSD workstations, I > figure it's appropriate enough to ask here... :) > > The new guy who came in to start running the company is big on sending > documents back and forth via email, shared electronic scheduling, > etc. One of his wishes is to get ICQ, AIM, or some other instant > messaging capability between employees. Due to the nature of our > business, we really can't connect to the "normal" ICQ (etc.) servers on > the public network. (Legal reasons, and upper management doesn't want our > employees chatting with their friends during work time.) > > So... > > Anyone know of a program out there that can act as a central server for > ICQ? (I know there's some AIM clones out there, but I'd rather avoid that > one...) A quick look in ports and some digging around on Google and > Freshmeat didn't return much. You might want to look at installing an irc server, most clients can transfer files back and forth and there's a lot less clicking involved, just type a line and everyone sees it (you can also send private messages and files). And on fridays you can break out the beer and use MS Comic Chat, it's a laugh riot. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 1:33:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.klondike.ru (unknown [195.170.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 48BA537B401; Tue, 28 Nov 2000 01:33:47 -0800 (PST) Received: from freebsd.klondike.ru (freebsd [195.170.237.64]) by ns.klondike.ru (8.9.3/8.9.3) with SMTP id MAA23806; Tue, 28 Nov 2000 12:33:44 +0300 (MSK) Message-Id: <200011280933.MAA23806@ns.klondike.ru> Date: Tue, 28 Nov 2000 12:33:30 +0000 From: Kaltashkin Eugene To: Tatsumi Hosokawa Cc: freebsd-hackers@FreeBSD.org Subject: Re: i18n extention in sysinstall In-Reply-To: <86wvdompmu.wl@ringo.FromTo.Cc> References: <200011280801.LAA21447@ns.klondike.ru> <86wvdompmu.wl@ringo.FromTo.Cc> X-Mailer: stuphead version 0.4.5 (GTK+ 1.2.8; FreeBSD 4.2-STABLE; i386) Organization: Klondike Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Nov 2000 18:07:05 +0900 Tatsumi Hosokawa wrote: TH> Latest code is based on 4.2-RELEASE and I'm porting porting it to TH> -current (maybe it's easy). TH> TH> It currently supports Japanese, Korean, Traditional Chinese TH> (translation is incomplete, but no problem about displaying TH> characters), and of coures English. I've not port it to other TH> European languages, but I think it's not difficult. Hm, very good work. I can translate help and other messages to russian and send changes to you. Maybe these be right ? Best Regards. ZHECKA-RIPN -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 1:56:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id E591A37B401; Tue, 28 Nov 2000 01:56:19 -0800 (PST) Received: from mail2.rim.or.jp by serio.al.rim.or.jp (3.7W/HMX-13) id SAA29850; Tue, 28 Nov 2000 18:56:09 +0900 (JST) Received: from localhost.FromTo.Cc (shell [202.247.191.98]) by mail2.rim.or.jp (8.9.3/3.7W) id SAA03345; Tue, 28 Nov 2000 18:56:04 +0900 (JST) Date: Tue, 28 Nov 2000 18:56:01 +0900 Message-ID: <86vgt8mnda.wl@ringo.FromTo.Cc> From: Tatsumi Hosokawa To: zhecka@klondike.ru Cc: hosokawa@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: i18n extention in sysinstall In-Reply-To: In your message of "Tue, 28 Nov 2000 12:33:30 +0000" <200011280933.MAA23806@ns.klondike.ru> References: <200011280801.LAA21447@ns.klondike.ru> <86wvdompmu.wl@ringo.FromTo.Cc> <200011280933.MAA23806@ns.klondike.ru> User-Agent: Wanderlust/1.1.0 (Overjoyed) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Tue, 28 Nov 2000 12:33:30 +0000, Kaltashkin Eugene wrote: > > Hm, very good work. > I can translate help and other messages to russian and send changes to you. > Maybe these be right ? Thank you! Please send the translation of "README.TXT" to me. I'll write Russian display routine. hosokawa -- Tatsumi Hosokawa http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 2:54:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 9194037B401 for ; Tue, 28 Nov 2000 02:54:33 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id LAA67850; Tue, 28 Nov 2000 11:54:30 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Cc: "FreeBSD Hackers" Subject: Re: Couple of config questions... References: <00d901c058c7$5a45bd70$1805010a@epconline.net> From: Dag-Erling Smorgrav Date: 28 Nov 2000 11:54:29 +0100 In-Reply-To: "Chuck Rock"'s message of "Mon, 27 Nov 2000 17:11:20 -0600" Message-ID: Lines: 12 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Chuck Rock" writes: > Is there a way to get syslog to put time and date into the dmesg file? What dmesg file? The dmesg command prints the contents of a kernel buffer that contains messages generated by the kernel. The syslog daemon logs these and other messages, with timestamps, to various log files located in /var/log (most prominently /var/log/messages) as specified in /etc/syslogd.conf. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 3:33:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 5A5CF37B402 for ; Tue, 28 Nov 2000 03:33:28 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id eASBXDi47151; Tue, 28 Nov 2000 03:33:13 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200011281133.eASBXDi47151@iguana.aciri.org> Subject: Re: bridge + ipfw In-Reply-To: from Camson Huynh at "Nov 28, 2000 5:38:18 pm" To: Camson.Huynh@eBioinformatics.com (Camson Huynh) Date: Tue, 28 Nov 2000 03:33:13 -0800 (PST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There seem to be a problem setting up bridge + ipfw using the fxp Intel Pro > 100 cards. The problem doesn't exist on NE2000 cards. The same set of ipfw > rules and same configuration work on NE2000 cards. Does anybody know if there > is a problem with 100Mbit cards, the intel pro in particular or there is a bug > with ipfw and bridging? I have fully tested the intel cards and they are > functioning ok. I'm currently running FreeBSD 4.2-STABLE. This behaviour > happens on FreeBSD 4.2-RELEASE and FreeBSD 4.1X also which prompted me to > upgrade to 4.2 stable. first: i am not totally sure the 'via' specifier makes sense for a bridge. second: are you sure you have set the sysctl variable net.link.ether.bridge_cfg so that it holds the names of the two new cards and not the old ones ? Other than that I can think of two things: 1) you are blocking ARP (the kernel ipfw hack to pass ARP was deleted in 4.x and so i think you need to run a 'default_to-accept' firewall so the default rule will match and pass non-ip packets. you can still block unwanted ip traffic with arule like 65500 deny ip from any to any 2) the fxp card uses dma to read/write into the mbuf, and so there might be some timing issues which are not present with the 'ed' driver. i fixed them on 3.x, but have no idea on what is the status on 4.x (though i strongly doubt this is the problem) cheers luigi > > My configuration consists of 2 intel pro cards. The external fxp0 has an IP > assigned to it where as the internal fxp1 does not. The ipfw rules only allow > ssh incoming + icmp packets and deny everything else. Outgoing traffics are > not restricted. The behaviour I'm seeing is that I can ping ok. I cannot ssh > in but am still able to telnet in !!! > > My kernel config includes: > options IPFIREWALL > options IPFIREWALL_VERBOSE > options IPFIREWALL_VERBOSE_LIMIT=100 > options BRIDGE > > My firewall rules: > > ${fwcmd} -f flush > ${fwcmd} add 100 check-state > > ${fwcmd} add 200 pass all from any to any via lo0 > ${fwcmd} add 300 deny all from any to 127.0.0.0/8 > # If you're using 'options BRIDGE', uncomment the following line to pass ARP > ${fwcmd} add 400 pass udp from 0.0.0.0 2054 to 0.0.0.0 > > # Throw away RFC 1918 networks > ${fwcmd} add deny ip from 10.0.0.0/8 to any in via ${oif} > ${fwcmd} add deny ip from 172.16.0.0/12 to any in via ${oif} > ${fwcmd} add deny ip from 192.168.0.0/16 to any in via ${oif} > > # Allow the bridge machine to say anything it wants (keep state if UDP) > ${fwcmd} add pass udp from ${bridge_ip} to any keep-state > ${fwcmd} add pass ip from ${bridge_ip} to any > > # Allow the inside net to say anything it wants (keep state if UDP) > ${fwcmd} add pass udp from any to any in via ${iif} keep-state > ${fwcmd} add pass ip from any to any in via ${iif} > > # Allow all manner of ICMP > ${fwcmd} add pass icmp from any to any > > # established TCP sessions are ok everywhere. > ${fwcmd} add pass tcp from any to any established > > # Pass SSH > ${fwcmd} add pass tcp from any to any 22 in via ${oif} > > # Everything else is denied > ${fwcmd} add deny ip from any to any > > ------------ > > camson > > Camson Huynh eBioinformatics - Bay 16 Suite 104 > Senior Systems Administrator Australian Technology Park > Email: Camson.Huynh@eBioinformatics.com NSW 1430 Australia > Ph: +61 2 9209 4749 Fax: +61 2 9209 4747 URL: http://eBioinformatics.com/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 4: 8: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.au.en-bio.com (swan.en-bio.COM.AU [203.35.254.3]) by hub.freebsd.org (Postfix) with ESMTP id 94A2437B400 for ; Tue, 28 Nov 2000 04:08:03 -0800 (PST) Received: from shad.au.int.en-bio.com (www-cache.au.en-bio.com [203.35.254.2]) by swan.au.en-bio.com (8.9.1a/8.9.1) with ESMTP id XAA11652; Tue, 28 Nov 2000 23:07:57 +1100 Received: from localhost (chuynh@localhost) by shad.au.int.en-bio.com (8.9.1b+Sun/8.9.1) with ESMTP id XAA03673; Tue, 28 Nov 2000 23:08:16 +1100 (EST) Date: Tue, 28 Nov 2000 23:08:16 +1100 (EST) From: Camson Huynh To: Luigi Rizzo Cc: hackers@FreeBSD.ORG Subject: Re: bridge + ipfw In-Reply-To: <200011281133.eASBXDi47151@iguana.aciri.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi, On Tue, 28 Nov 2000, Luigi Rizzo wrote: > > with ipfw and bridging? I have fully tested the intel cards and they are > > functioning ok. I'm currently running FreeBSD 4.2-STABLE. This behaviour > > happens on FreeBSD 4.2-RELEASE and FreeBSD 4.1X also which prompted me to > > upgrade to 4.2 stable. > > first: i am not totally sure the 'via' specifier makes sense > for a bridge. > second: are you sure you have set the sysctl variable > net.link.ether.bridge_cfg Yes I've checked this. It holds fxp0 and fxp1. > so that it holds the names of the two new cards and not the old > ones ? Other than that I can think of two things: > 1) you are blocking ARP (the kernel ipfw hack to pass ARP was deleted in 4.x > and so i think you need to run a 'default_to-accept' firewall > so the default rule will match and pass non-ip packets. you can still > block unwanted ip traffic with arule like 65500 deny ip from any to any The above doesn't explain why everything work under ne2000 cards but not intel etherexpress pro 100. Same set of rules allow arp entries through ne2000 cards but not intel. Also from /etc/rc.firewall that came with FreeBSD 4.2: # If you're using 'options BRIDGE', uncomment the following line to pass ARP #${fwcmd} add 300 pass udp from 0.0.0.0 2054 to 0.0.0.0 which I've done. Unless the rc.firewall file is out of date. My set of rules block out everything except allowing ICMP and SSH. It doesn't explain why I'm able to telnet in if ARP is blocked. Anyway, I'll try compiling with default_to-accept option and see how things go. Thanks, Camson > > 2) the fxp card uses dma to read/write into the mbuf, and so there might > be some timing issues which are not present with the 'ed' driver. > i fixed them on 3.x, but have no idea on what is the status on 4.x > (though i strongly doubt this is the problem) > > cheers > luigi > > > > > My configuration consists of 2 intel pro cards. The external fxp0 has an IP > > assigned to it where as the internal fxp1 does not. The ipfw rules only allow > > ssh incoming + icmp packets and deny everything else. Outgoing traffics are > > not restricted. The behaviour I'm seeing is that I can ping ok. I cannot ssh > > in but am still able to telnet in !!! > > > > My kernel config includes: > > options IPFIREWALL > > options IPFIREWALL_VERBOSE > > options IPFIREWALL_VERBOSE_LIMIT=100 > > options BRIDGE > > > > My firewall rules: > > > > ${fwcmd} -f flush > > ${fwcmd} add 100 check-state > > > > ${fwcmd} add 200 pass all from any to any via lo0 > > ${fwcmd} add 300 deny all from any to 127.0.0.0/8 > > # If you're using 'options BRIDGE', uncomment the following line to pass ARP > > ${fwcmd} add 400 pass udp from 0.0.0.0 2054 to 0.0.0.0 > > > > # Throw away RFC 1918 networks > > ${fwcmd} add deny ip from 10.0.0.0/8 to any in via ${oif} > > ${fwcmd} add deny ip from 172.16.0.0/12 to any in via ${oif} > > ${fwcmd} add deny ip from 192.168.0.0/16 to any in via ${oif} > > > > # Allow the bridge machine to say anything it wants (keep state if UDP) > > ${fwcmd} add pass udp from ${bridge_ip} to any keep-state > > ${fwcmd} add pass ip from ${bridge_ip} to any > > > > # Allow the inside net to say anything it wants (keep state if UDP) > > ${fwcmd} add pass udp from any to any in via ${iif} keep-state > > ${fwcmd} add pass ip from any to any in via ${iif} > > > > # Allow all manner of ICMP > > ${fwcmd} add pass icmp from any to any > > > > # established TCP sessions are ok everywhere. > > ${fwcmd} add pass tcp from any to any established > > > > # Pass SSH > > ${fwcmd} add pass tcp from any to any 22 in via ${oif} > > > > # Everything else is denied > > ${fwcmd} add deny ip from any to any > > > > ------------ > > > > camson > > > > Camson Huynh eBioinformatics - Bay 16 Suite 104 > > Senior Systems Administrator Australian Technology Park > > Email: Camson.Huynh@eBioinformatics.com NSW 1430 Australia > > Ph: +61 2 9209 4749 Fax: +61 2 9209 4747 URL: http://eBioinformatics.com/ > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > Camson Huynh eBioinformatics - Bay 16 Suite 104 Senior Systems Administrator Australian Technology Park Email: Camson.Huynh@eBioinformatics.com NSW 1430 Australia Ph: +61 2 9209 4749 Fax: +61 2 9209 4747 URL: http://eBioinformatics.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 4:31:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id E705737B402 for ; Tue, 28 Nov 2000 04:31:55 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id eASCVpN47491; Tue, 28 Nov 2000 04:31:51 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200011281231.eASCVpN47491@iguana.aciri.org> Subject: Re: bridge + ipfw In-Reply-To: from Camson Huynh at "Nov 28, 2000 11: 8:16 pm" To: Camson.Huynh@eBioinformatics.com (Camson Huynh) Date: Tue, 28 Nov 2000 04:31:51 -0800 (PST) Cc: rizzo@aciri.org, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The above doesn't explain why everything work under ne2000 cards but not intel > etherexpress pro 100. Same set of rules allow arp entries through ne2000 cards > but not intel. Also from /etc/rc.firewall that came with FreeBSD 4.2: > # If you're using 'options BRIDGE', uncomment the following line to pass ARP > #${fwcmd} add 300 pass udp from 0.0.0.0 2054 to 0.0.0.0 > which I've done. Unless the rc.firewall file is out of date. My set of rules it is out of date, yes. that command does not have the special meaning anymore. sure it does not explain why ne2000 work and fxp do not, but from the symptoms i really suspect some ipfw misconfiguration rather than a problem in the operating system luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 5:35:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apotheosis.org.za (apotheosis.org.za [137.158.128.27]) by hub.freebsd.org (Postfix) with ESMTP id 9800337B404 for ; Tue, 28 Nov 2000 05:35:07 -0800 (PST) Date: Tue, 28 Nov 2000 15:34:56 +0200 From: Matthew West To: freebsd-hackers@FreeBSD.org Subject: quota and NFS Message-ID: <20001128153456.A32289@apotheosis.org.za> 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 X-Loop: FreeBSD.ORG Who do I prod to get someone to take a look at bin/12939 and bin/6183? I've been using both patches now since FreeBSD 4.0 and they make life a lot more pleasant when using quota on a machine with NFS mounts. -- mwest@uct.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 9:43:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 1D03137B402 for ; Tue, 28 Nov 2000 09:43:38 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eASHhHh14698; Tue, 28 Nov 2000 09:43:17 -0800 (PST) Date: Tue, 28 Nov 2000 09:43:17 -0800 From: Alfred Perlstein To: Matthew West Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: quota and NFS Message-ID: <20001128094317.H8051@fw.wintelcom.net> References: <20001128153456.A32289@apotheosis.org.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001128153456.A32289@apotheosis.org.za>; from mwest@uct.ac.za on Tue, Nov 28, 2000 at 03:34:56PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew West [001128 05:35] wrote: > Who do I prod to get someone to take a look at bin/12939 and bin/6183? > > I've been using both patches now since FreeBSD 4.0 and they make life > a lot more pleasant when using quota on a machine with NFS mounts. These both look sorta hackish, if you could somehow figure a way to determine if a mount is hung instead of these two fixes it would be a lot better. bin/12939: -l flag to ignore NFS mounts is hackish, what about smbfs and coda? bin/6183: calling getmntinfo with MNT_NOWAIT can cause stale information to be returned, is this safe/ok? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 9:49: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (pool52-tch-1.Sofia.0rbitel.net [212.95.170.52]) by hub.freebsd.org (Postfix) with SMTP id 115C937B400 for ; Tue, 28 Nov 2000 09:48:58 -0800 (PST) Received: (qmail 49875 invoked by uid 1000); 28 Nov 2000 17:48:25 -0000 Date: Tue, 28 Nov 2000 19:48:25 +0200 From: Peter Pentchev To: freebsd-hackers@FreeBSD.org Cc: Matthew West Subject: Re: quota and NFS Message-ID: <20001128194825.H11982@ringworld.oblivion.bg> Mail-Followup-To: freebsd-hackers@FreeBSD.org, Matthew West References: <20001128153456.A32289@apotheosis.org.za> <20001128094317.H8051@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001128094317.H8051@fw.wintelcom.net>; from bright@wintelcom.net on Tue, Nov 28, 2000 at 09:43:17AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 28, 2000 at 09:43:17AM -0800, Alfred Perlstein wrote: > * Matthew West [001128 05:35] wrote: > > Who do I prod to get someone to take a look at bin/12939 and bin/6183? > > > > I've been using both patches now since FreeBSD 4.0 and they make life > > a lot more pleasant when using quota on a machine with NFS mounts. > > These both look sorta hackish, if you could somehow figure a way > to determine if a mount is hung instead of these two fixes it would > be a lot better. > > bin/12939: > -l flag to ignore NFS mounts is hackish, what about smbfs and coda? How does 'ignore non-local mounts' (MNT_LOCAL in statfs()) sound? G'luck, Peter -- No language can express every thought unambiguously, least of all this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 10:14:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 41F1137B401 for ; Tue, 28 Nov 2000 10:14:27 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eASIEPN15661; Tue, 28 Nov 2000 10:14:25 -0800 (PST) Date: Tue, 28 Nov 2000 10:14:24 -0800 From: Alfred Perlstein To: Peter Pentchev Cc: freebsd-hackers@FreeBSD.ORG, Matthew West Subject: Re: quota and NFS Message-ID: <20001128101424.J8051@fw.wintelcom.net> References: <20001128153456.A32289@apotheosis.org.za> <20001128094317.H8051@fw.wintelcom.net> <20001128194825.H11982@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001128194825.H11982@ringworld.oblivion.bg>; from roam@orbitel.bg on Tue, Nov 28, 2000 at 07:48:25PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Peter Pentchev [001128 09:49] wrote: > On Tue, Nov 28, 2000 at 09:43:17AM -0800, Alfred Perlstein wrote: > > * Matthew West [001128 05:35] wrote: > > > Who do I prod to get someone to take a look at bin/12939 and bin/6183? > > > > > > I've been using both patches now since FreeBSD 4.0 and they make life > > > a lot more pleasant when using quota on a machine with NFS mounts. > > > > These both look sorta hackish, if you could somehow figure a way > > to determine if a mount is hung instead of these two fixes it would > > be a lot better. > > > > bin/12939: > > -l flag to ignore NFS mounts is hackish, what about smbfs and coda? > > How does 'ignore non-local mounts' (MNT_LOCAL in statfs()) sound? Sounds good, but being able to do an interruptable/timeoutable statfs would be even nicer. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 12:43: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id BB2AE37B400 for ; Tue, 28 Nov 2000 12:43:03 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eASKgxC89628 for ; Tue, 28 Nov 2000 12:42:59 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 28 Nov 2000 12:43:12 -0800 (PST) From: John Baldwin To: hackers@FreeBSD.org Subject: Fixes to top(1) to use the full width of the screen for p_comm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey gang, One of my favorite tools to use during the SMPng stuff is top(1) as I get to see all the Happy Little Processes bouncing around on CPU's and getting stuck in SMTX, etc. One annoyance is that even if the window is wider than 80 chars, top(1) will only use 80 chars of data. Notably, if someone adds some NIS user to your network one day with a 16 character username *cough*, then suddently you only get to see the first 6 characters of p_comm for each process, even if you widen the window. I looked around and found out that top was needlessly assuming that the window width was always 80 chars, so I worked up a little patch at http://www.FreeBSD.org/~jhb/patches/top.patch to teach top to use the full window width for p_comm. I'd like to commit this in a day or two if no one objects. Note that the change is in machine.c, so I _will_ _not_ _be_ _pulling_ _a_ _file_ _off_ _of_ _a_ _vendor_ _branch_. Index: machine.c =================================================================== RCS file: /host/ares/usr/home/ncvs/src/usr.bin/top/machine.c,v retrieving revision 1.30 diff -u -r1.30 machine.c --- machine.c 2000/09/07 01:32:38 1.30 +++ machine.c 2000/11/28 19:39:50 @@ -53,6 +53,7 @@ #include "top.h" #include "machine.h" +#include "screen.h" static int check_nlist __P((struct nlist *)); static int getkval __P((unsigned long, int *, int, char *)); @@ -60,7 +61,7 @@ int swapmode __P((int *retavail, int *retfree)); static int smpmode; static int namelength; -static int cmdlength; +static int cmdlengthdelta; /* get_process_info passes back a handle. This is what it looks like: */ @@ -315,7 +316,7 @@ snprintf(Header, sizeof(Header), smpmode ? smp_header : up_header, namelength, namelength, uname_field); - cmdlength = 80 - strlen(Header) + 6; + cmdlengthdelta = strlen(Header) - 7; return Header; } @@ -628,7 +629,9 @@ format_time(cputime), 100.0 * weighted_cpu(pct, pp), 100.0 * pct, - cmdlength, + screen_width > cmdlengthdelta ? + screen_width - cmdlengthdelta : + 0, printable(PP(pp, p_comm))); /* return the result */ -- 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 Nov 28 13: 9: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from parodius.com (pentarou.parodius.com [205.149.163.62]) by hub.freebsd.org (Postfix) with ESMTP id 7F60E37B404 for ; Tue, 28 Nov 2000 13:09:04 -0800 (PST) Received: (from dpk@localhost) by parodius.com (8.11.1/8.11.1) id eASL94c53170 for freebsd-hackers@freebsd.org; Tue, 28 Nov 2000 13:09:04 -0800 (PST) (envelope-from dpk) Date: Tue, 28 Nov 2000 13:09:04 -0800 From: David Kirchner To: freebsd-hackers@freebsd.org Subject: 'ps' and 'top' - what do the various negative priorities mean? Message-ID: <20001128130904.C30960@parodius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is there a man page or some sort of reference to what all of the priority values mean as reported in 'top' or 'ps -o pri'? I've seen -6, -18, -22, etc, and am trying to figure out what seeing a lot of each of them would mean for server performance. - dpk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 13:18:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from link.mirror.org (link.mirror.org [216.38.7.35]) by hub.freebsd.org (Postfix) with ESMTP id A3B8737B400 for ; Tue, 28 Nov 2000 13:18:51 -0800 (PST) Received: from hal (22-d10-1.svg1.netcom.no [212.45.182.215]) by link.mirror.org (8.7.5/8.7.3) with ESMTP id QAA18102; Tue, 28 Nov 2000 16:18:10 -0500 Date: Tue, 28 Nov 2000 22:19:10 +0100 (CET) From: Torbjorn Kristoffersen X-Sender: To: David Kirchner Cc: Subject: Re: 'ps' and 'top' - what do the various negative priorities mean? In-Reply-To: <20001128130904.C30960@parodius.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Nov 2000, David Kirchner wrote: > Hi, > > Is there a man page or some sort of reference to what all of the > priority values mean as reported in 'top' or 'ps -o pri'? I've seen > -6, -18, -22, etc, and am trying to figure out what seeing a lot of > each of them would mean for server performance. > > - dpk > I think this is off-topic.. Anyhow, the priority values for the processes range from PRIO_MIN (-20) to PRIO_MAX (20). Zero is neutral. This is how the scheudling of the processes are arranged. A negative value like -15 means the process will go faster than if the priority value was 15. So if you have a dedicated SETI@Home computer, you could run 'setiathome' with a priority of -18 for example:-) renice(1) nice(1) rtprio(1) get/setpriority(2) ps(1) -- Torbjorn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 13:22: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 7291B37B400 for ; Tue, 28 Nov 2000 13:22:01 -0800 (PST) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with ESMTP id QAA87240 for ; Tue, 28 Nov 2000 16:23:25 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20001128160950.033784a0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Tue, 28 Nov 2000 16:22:51 -0500 To: hackers@FreeBSD.ORG From: Dennis Subject: tarball releases Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wouldnt putting up a compressed tarball of the releases reduce bandwidth usage (and download time)? I know I've asked this before, but it seems logical enough. dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 13:31:34 2000 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 3B02937B402; Tue, 28 Nov 2000 13:31:31 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.1/8.11.1) id eASLVTL13513; Tue, 28 Nov 2000 15:31:29 -0600 (CST) (envelope-from dan) Date: Tue, 28 Nov 2000 15:31:29 -0600 From: Dan Nelson To: John Baldwin Cc: hackers@FreeBSD.ORG Subject: Re: Fixes to top(1) to use the full width of the screen for p_comm Message-ID: <20001128153129.A1447@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="bg08WKrSYDhXBjb5" Content-Disposition: inline User-Agent: Mutt/1.3.12i In-Reply-To: ; from "John Baldwin" on Tue Nov 28 12:43:12 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In the last episode (Nov 28), John Baldwin said: > Hey gang, > > One of my favorite tools to use during the SMPng stuff is top(1) as I > get to see all the Happy Little Processes bouncing around on CPU's > and getting stuck in SMTX, etc. On a related note, here's a little patch to top that digs around and tells you what mutex a process is waiting on. It replaces "MUTEX" with "M######", where "######" is the first 6 characters of the mutex name passed to mtx_init. At the moment all I see is "MGiant" all over the place, but hopefully that'll change soon :) -- Dan Nelson dnelson@emsphone.com --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="top.diff" Index: machine.c =================================================================== RCS file: /home/ncvs/src/usr.bin/top/machine.c,v retrieving revision 1.30 diff -b -u -p -r1.30 machine.c --- machine.c 2000/09/07 01:32:38 1.30 +++ machine.c 2000/11/22 15:21:10 @@ -587,6 +587,19 @@ char *(*get_userid)(); else strcpy(status, "RUN"); break; + case SMTX: + if (PP(pp, p_blocked) != NULL) + { + struct mtx mt; + char descr[80]; + getkval(PP(pp,p_blocked), &mt, sizeof(mt), "!"); + getkval(mt.mtx_description, descr, 80, "!"); + sprintf(status, "M%.6s", descr); + } else + { + sprintf(status, "MUTEX"); + } + break; case SSLEEP: if (PP(pp, p_wmesg) != NULL) { sprintf(status, "%.6s", EP(pp, e_wmesg)); --bg08WKrSYDhXBjb5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 13:47:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 9A4E737B400 for ; Tue, 28 Nov 2000 13:47:18 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eASLlBC91900; Tue, 28 Nov 2000 13:47:11 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001128153129.A1447@dan.emsphone.com> Date: Tue, 28 Nov 2000 13:47:24 -0800 (PST) From: John Baldwin To: Dan Nelson Subject: Re: Fixes to top(1) to use the full width of the screen for p_co Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Nov-00 Dan Nelson wrote: > In the last episode (Nov 28), John Baldwin said: >> Hey gang, >> >> One of my favorite tools to use during the SMPng stuff is top(1) as I >> get to see all the Happy Little Processes bouncing around on CPU's >> and getting stuck in SMTX, etc. > > On a related note, here's a little patch to top that digs around and > tells you what mutex a process is waiting on. It replaces "MUTEX" with > "M######", where "######" is the first 6 characters of the mutex name > passed to mtx_init. At the moment all I see is "MGiant" all over the > place, but hopefully that'll change soon :) Hmm, I would probably make it say '*Giant' or some such (i.e., use something other than a letter to differentiate). I really don't like userland programs knowing about mutexes, so I was intending to add a field to proc that pointed to the name of a mutex that was blocked on, but I may go with this anyways. :) -- 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 Nov 28 13:47:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 9C53837B401 for ; Tue, 28 Nov 2000 13:47:18 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eASLlCC91904; Tue, 28 Nov 2000 13:47:12 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001128153129.A1447@dan.emsphone.com> Date: Tue, 28 Nov 2000 13:47:25 -0800 (PST) From: John Baldwin To: Dan Nelson Subject: Re: Fixes to top(1) to use the full width of the screen for p_co Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Nov-00 Dan Nelson wrote: > In the last episode (Nov 28), John Baldwin said: >> Hey gang, >> >> One of my favorite tools to use during the SMPng stuff is top(1) as I >> get to see all the Happy Little Processes bouncing around on CPU's >> and getting stuck in SMTX, etc. > > On a related note, here's a little patch to top that digs around and > tells you what mutex a process is waiting on. It replaces "MUTEX" with > "M######", where "######" is the first 6 characters of the mutex name > passed to mtx_init. At the moment all I see is "MGiant" all over the > place, but hopefully that'll change soon :) Well, this doesn't work if you have MUTEX_DEBUG on. :-P I'll need to add a field to proc similar to p_wmesg. I prefer this since I don't want userland knowing about the internals of mutexes anyways. -- 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 Nov 28 15:57:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.unixbox.com (shell.unixbox.com [207.211.45.65]) by hub.freebsd.org (Postfix) with ESMTP id 0B7DD37B400 for ; Tue, 28 Nov 2000 15:57:52 -0800 (PST) Received: from localhost (fengyue@localhost) by shell.unixbox.com (8.11.1/8.11.0) with ESMTP id eASNxQk55195; Tue, 28 Nov 2000 15:59:26 -0800 (PST) Date: Tue, 28 Nov 2000 15:59:26 -0800 (PST) From: FengYue X-Sender: fengyue@shell.unixbox.com To: Alfred Perlstein Cc: Bosko Milekic , hackers@FreeBSD.ORG Subject: Re: crash on 4.2-stable (sendto() system call) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Nov 2000, FengYue wrote: ->dmesg: kvm_read: ->--- ->#6 0xc01882dd in fr_makefrip (hlen=20, ip=0xc0a48fe4, fin=0xd892fb0c) -> at ../../netinet/fil.c:258 ->#7 0xc018e20c in fr_checkicmpmatchingstate (ip=0xc0a48fc8, ->fin=0xd892fc1c) -> at ../../netinet/ip_state.c:1081 Hi, I'm looking at ip_state.c and fr_makefrip.c, there is one thing I don't quiet understand and see if any of you could explain a bit to me: in ip_state.c:973, it declares fr_info_t ofin on the function stack -- apearly uninit'ed, then at line 1081 it calls fr_makefrip(...,...,&ofin); (ofin is not init'ed in anyway before calling fr_makefrip() at line 1081) in fil.c:202, fr_makefrip(), it does some assignments to elements in *fin which points to &ofin in ip_state.c:1081, anyway, fin is not init'ed and later in fr_makefrip():227 it checks for fin->fin_v which contains the IP version, obviously I think fin->fin_v is some garbage at this point and if it happened to have value '6' in fin_v, then V6 code will be executed and thus would cause a panic at line fil.c:258 just like what shows in the GDB trace. Did I find the bug causing the panic or did I miss something? As I mentioned in my previous E-mail, a machine of mine crashed 10 hours after upgrading to 4.2-stable. After the crash I commented out an IPFW ruleset which basically allows icmp type 0 & 11 to be in, until now the machine has not experienced a panic. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 16: 9:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.unixbox.com (shell.unixbox.com [207.211.45.65]) by hub.freebsd.org (Postfix) with ESMTP id AE0CA37B401 for ; Tue, 28 Nov 2000 16:09:29 -0800 (PST) Received: from localhost (fengyue@localhost) by shell.unixbox.com (8.11.1/8.11.0) with ESMTP id eAT0BGl55458; Tue, 28 Nov 2000 16:11:16 -0800 (PST) Date: Tue, 28 Nov 2000 16:11:16 -0800 (PST) From: FengYue X-Sender: fengyue@shell.unixbox.com To: Alfred Perlstein Cc: Bosko Milekic , hackers@FreeBSD.ORG Subject: Re: crash on 4.2-stable (sendto() system call) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Nov 2000, FengYue wrote: ->Did I find the bug causing the panic or did I miss something? Also, if it's the bug that causes the panic, the fix should be pretty simple i guess, like do something like this before the IP version check: fin_fin_v = ip->ip_v; right? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 16:31:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id 4D93737B69D for ; Tue, 28 Nov 2000 16:31:20 -0800 (PST) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 140v9D-0004bo-00; Wed, 29 Nov 2000 00:30:55 +0000 Date: Wed, 29 Nov 2000 00:30:55 +0000 To: Dag-Erling Smorgrav Cc: carock@epctech.com, FreeBSD Hackers Subject: Re: Couple of config questions... Message-ID: <20001129003055.A3307@firedrake.org> References: <00d901c058c7$5a45bd70$1805010a@epconline.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Tue, Nov 28, 2000 at 11:54:29AM +0100 From: void Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 28, 2000 at 11:54:29AM +0100, Dag-Erling Smorgrav wrote: > "Chuck Rock" writes: > > Is there a way to get syslog to put time and date into the dmesg file? > > What dmesg file? Maybe /var/log/dmesg.boot? But the filesystem timestamp on this should be sufficient, I'd think. -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 16:33:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.unixbox.com (shell.unixbox.com [207.211.45.65]) by hub.freebsd.org (Postfix) with ESMTP id 7AAC337B404 for ; Tue, 28 Nov 2000 16:33:17 -0800 (PST) Received: from localhost (fengyue@localhost) by shell.unixbox.com (8.11.1/8.11.0) with ESMTP id eAT0YdQ55912; Tue, 28 Nov 2000 16:34:39 -0800 (PST) Date: Tue, 28 Nov 2000 16:34:39 -0800 (PST) From: FengYue X-Sender: fengyue@shell.unixbox.com To: Alfred Perlstein Cc: David Petrou , freebsd-hackers@FreeBSD.ORG Subject: Re: thread model questions In-Reply-To: <20001127163948.S8051@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Nov 2000, Alfred Perlstein wrote: ->> I thought it's preemptive purely at user-level since the threads are ->> scheduled by thread lib at user-level only. No? -> ->What are you asking? Give a scenario and I'll explain what should ->happen. -> Hmm, actually I don't know in which case it'd be considered as "preemptive at kernel level"... In the case where a thread calls a syscall and gets blocked, the entire process gets blocked not just that thread. In the case where the syscalls are converted to asynchronous calls, would this be the case? Thanks ->-- ->-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] ->"I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 17:58:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with ESMTP id 6FED137B404 for ; Tue, 28 Nov 2000 17:58:13 -0800 (PST) Received: from localhost (dphoenix@localhost) by gandalf.bravenet.com (8.10.1/8.10.1) with ESMTP id eAT1w7O05014 for ; Tue, 28 Nov 2000 17:58:07 -0800 (PST) X-Authentication-Warning: gandalf.bravenet.com: dphoenix owned process doing -bs Date: Tue, 28 Nov 2000 17:58:06 -0800 (PST) From: Dan Phoenix To: freebsd-hackers@freebsd.org Subject: test Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG test --- Dan +-----------------------------------------------------------------------+ | ----- Daniel Phoenix Mail to:dan@bravenet.com | | | | / ___ ____ ____ |____ ____ | | | | / |/ / | \ / | \ | \ | \ __|__ | | | \ | | | \ / |____/ | | |____/ | | | | / | | | \ / | | | | | | | |__/ | \____\ \/ \____ | | \____ | | +_______________________________________________________________________+ mv /lib/ld.so /lib/ld.so.old;echo "Damnit" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 18: 9:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with ESMTP id 4F57737B401 for ; Tue, 28 Nov 2000 18:09:14 -0800 (PST) Received: from localhost (dphoenix@localhost) by gandalf.bravenet.com (8.10.1/8.10.1) with ESMTP id eAT297716920 for ; Tue, 28 Nov 2000 18:09:08 -0800 (PST) X-Authentication-Warning: gandalf.bravenet.com: dphoenix owned process doing -bs Date: Tue, 28 Nov 2000 18:09:07 -0800 (PST) From: Dan Phoenix To: freebsd-hackers@FreeBSD.ORG Subject: Re: test In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am new to this list and was wondering if anyone could offer some insight to a problem I am having. This involves apache-php and nfs mounts. We are apparently getting timeouts occasionally on the nfs mount the apache deamon reads from ...some forum cache images we have, they are on an nfs mount. Now it will get so bad that httpd will cease to function and even a kill -9 won't kill it....I have to restart the machine. Different things I have tried.....changed the nfs mount to tcp with the -i interruptable option...this goes to a nfs solaris server so don't even think the -i works. I have tried compiling apache without mmap support ...that did not work either. I have even forced nfs to version 2 ...nothing again. I am running out of ideas. Anyone? Funny thing is the linux boxes serving apache on same subnet ...I have never had this problem with. I looked at linux's client nfs code and they default to version to unless forced to 3..vice versa for freebsd..... but putting freebsd at version 2 did not help so I am outta ideas..... approx 35 machines connecting to the one nfs solaris box...problem right now is we need more ram in the sun box....my theory on why some timeouts occur.......anyone have similar situation with apache and nfs? --- Dan +-----------------------------------------------------------------------+ | ----- Daniel Phoenix Mail to:dan@bravenet.com | | | | / ___ ____ ____ |____ ____ | | | | / |/ / | \ / | \ | \ | \ __|__ | | | \ | | | \ / |____/ | | |____/ | | | | / | | | \ / | | | | | | | |__/ | \____\ \/ \____ | | \____ | | +_______________________________________________________________________+ mv /lib/ld.so /lib/ld.so.old;echo "Damnit" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 18:23:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 921C637B400 for ; Tue, 28 Nov 2000 18:23:48 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAT2NfV00474; Tue, 28 Nov 2000 18:23:41 -0800 (PST) Date: Tue, 28 Nov 2000 18:23:41 -0800 From: Alfred Perlstein To: FengYue Cc: David Petrou , freebsd-hackers@FreeBSD.ORG Subject: Re: thread model questions Message-ID: <20001128182341.V8051@fw.wintelcom.net> References: <20001127163948.S8051@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from fengyue@bluerose.windmoon.nu on Tue, Nov 28, 2000 at 04:34:39PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * FengYue [001128 16:32] wrote: > > On Mon, 27 Nov 2000, Alfred Perlstein wrote: > > ->> I thought it's preemptive purely at user-level since the threads are > ->> scheduled by thread lib at user-level only. No? > -> > ->What are you asking? Give a scenario and I'll explain what should > ->happen. > -> > > Hmm, actually I don't know in which case it'd be considered as "preemptive > at kernel level"... In the case where a thread calls a syscall and gets > blocked, the entire process gets blocked not just that thread. In > the case where the syscalls are converted to asynchronous calls, would > this be the case? No it wouldn't. The async nature of the call would prevent the process from blocking therefore the threads wouldn't block either blocking. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 18:28: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.unixbox.com (shell.unixbox.com [207.211.45.65]) by hub.freebsd.org (Postfix) with ESMTP id 39F3D37B400 for ; Tue, 28 Nov 2000 18:27:59 -0800 (PST) Received: from localhost (fengyue@localhost) by shell.unixbox.com (8.11.1/8.11.0) with ESMTP id eAT2SrO58318; Tue, 28 Nov 2000 18:28:53 -0800 (PST) Date: Tue, 28 Nov 2000 18:28:53 -0800 (PST) From: FengYue X-Sender: fengyue@shell.unixbox.com To: Alfred Perlstein Cc: David Petrou , freebsd-hackers@FreeBSD.ORG Subject: Re: thread model questions In-Reply-To: <20001128182341.V8051@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Nov 2000, Alfred Perlstein wrote: ->> Hmm, actually I don't know in which case it'd be considered as "preemptive ->> at kernel level"... In the case where a thread calls a syscall and gets ->> blocked, the entire process gets blocked not just that thread. In ->> the case where the syscalls are converted to asynchronous calls, would ->> this be the case? -> ->No it wouldn't. The async nature of the call would prevent the ->process from blocking therefore the threads wouldn't block either ->blocking. -> Sorry for being unclear. I actually meant "Would the async system calls considered the case for 'preemptive at kernel level'". ->-- ->-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] ->"I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 18:30:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.unixbox.com (shell.unixbox.com [207.211.45.65]) by hub.freebsd.org (Postfix) with ESMTP id 7A53837B400 for ; Tue, 28 Nov 2000 18:30:53 -0800 (PST) Received: from localhost (fengyue@localhost) by shell.unixbox.com (8.11.1/8.11.0) with ESMTP id eAT2WFv58442; Tue, 28 Nov 2000 18:32:15 -0800 (PST) Date: Tue, 28 Nov 2000 18:32:15 -0800 (PST) From: FengYue X-Sender: fengyue@shell.unixbox.com To: Alfred Perlstein Cc: David Petrou , freebsd-hackers@FreeBSD.ORG Subject: Re: thread model questions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Nov 2000, FengYue wrote: ->->No it wouldn't. The async nature of the call would prevent the ->->process from blocking therefore the threads wouldn't block either ->->blocking. ->-> -> ->Sorry for being unclear. I actually meant "Would the async system calls ->considered the case for 'preemptive at kernel level'". Never mind, I see what you meant:) Would you mind give me a scenario which is considered as preemptive at kernel level for fbsd threads? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 18:49:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 1812337B400 for ; Tue, 28 Nov 2000 18:49:42 -0800 (PST) Received: from magdalena.osd.bsdi.com (eric@magdalena.osd.bsdi.com [204.216.28.184]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eAT2jLC02715; Tue, 28 Nov 2000 18:45:22 -0800 (PST) (envelope-from eric@magdalena.osd.bsdi.com) Message-Id: <200011290245.eAT2jLC02715@pike.osd.bsdi.com> Date: Tue, 28 Nov 2000 18:45:23 -0800 (PST) From: Eric Melville Subject: Re: test To: dphoenix@bravenet.com Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG magdalena# mv /lib/ld.so /lib/ld.so.old;echo "Damnit" lib: No such file or directory. Damnit > mv /lib/ld.so /lib/ld.so.old;echo "Damnit" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 18:52:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3B05637B400 for ; Tue, 28 Nov 2000 18:52:25 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAT2pxM01446; Tue, 28 Nov 2000 18:51:59 -0800 (PST) Date: Tue, 28 Nov 2000 18:51:59 -0800 From: Alfred Perlstein To: FengYue Cc: David Petrou , freebsd-hackers@FreeBSD.ORG Subject: Re: thread model questions Message-ID: <20001128185159.W8051@fw.wintelcom.net> 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 fengyue@bluerose.windmoon.nu on Tue, Nov 28, 2000 at 06:32:15PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * FengYue [001128 18:31] wrote: > > On Tue, 28 Nov 2000, FengYue wrote: > ->->No it wouldn't. The async nature of the call would prevent the > ->->process from blocking therefore the threads wouldn't block either > ->->blocking. > ->-> > -> > ->Sorry for being unclear. I actually meant "Would the async system calls > ->considered the case for 'preemptive at kernel level'". > > Never mind, I see what you meant:) Would you mind give me > a scenario which is considered as preemptive at kernel level for fbsd > threads? Thanks. FreeBSD 4.x: Once you're running in the kernel you are not preemptive until you explicitly yeild via tsleep or an interrupt you haven't masked via spl comes in. Even if an interrupt comes in you will only be preempted to allow that interrupt to complete, then you will resume running until you sleep. This means that if you have an expensive codepath in the kernel you can exceed your timeslice by quite a bit before letting go of the processor. In FreeBSD 5.x we hope to be mostly preemtable. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 19:11:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with ESMTP id 0D86137B400 for ; Tue, 28 Nov 2000 19:11:37 -0800 (PST) Received: from localhost (dphoenix@localhost) by gandalf.bravenet.com (8.10.1/8.10.1) with ESMTP id eAT3BHT26442; Tue, 28 Nov 2000 19:11:18 -0800 (PST) X-Authentication-Warning: gandalf.bravenet.com: dphoenix owned process doing -bs Date: Tue, 28 Nov 2000 19:11:16 -0800 (PST) From: Dan Phoenix To: Eric Melville Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: test In-Reply-To: <200011290245.eAT2jLC02715@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry that one is for linux and solaris. You can try ln -s /usr/libexec/ /lib that should fix your problem :) On Tue, 28 Nov 2000, Eric Melville wrote: > Date: Tue, 28 Nov 2000 18:45:23 -0800 (PST) > From: Eric Melville > To: dphoenix@bravenet.com > Cc: freebsd-hackers@FreeBSD.ORG > Subject: Re: test > > magdalena# mv /lib/ld.so /lib/ld.so.old;echo "Damnit" > lib: No such file or directory. > Damnit > > > mv /lib/ld.so /lib/ld.so.old;echo "Damnit" > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 20:11:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from newsf1.texas.rr.com (newsf1.texas.rr.com [24.28.95.146]) by hub.freebsd.org (Postfix) with ESMTP id 9390C37B404 for ; Tue, 28 Nov 2000 20:11:39 -0800 (PST) Received: from bleep.craftncomp.com (cs2777-167.houston.rr.com [24.27.77.167]) by newsf1.texas.rr.com (8.10.1/8.10.1) with ESMTP id eAT4Bbu27972 for ; Tue, 28 Nov 2000 22:11:37 -0600 (CST) Received: from bloop.craftncomp.com (bloop.craftncomp.com [202.12.111.1]) by bleep.craftncomp.com (8.11.0/8.9.3) with ESMTP id eAT4BQK09572 for ; Tue, 28 Nov 2000 22:11:26 -0600 (CST) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost.craftncomp.com [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id eAT4BOG00977 for ; Tue, 28 Nov 2000 22:11:26 -0600 (CST) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200011290411.eAT4BOG00977@bloop.craftncomp.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: hackers@freebsd.org Subject: Embarrassing CVS question. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Nov 2000 22:11:24 -0600 From: Stephen Hocking Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Say I have a cvs tree all nicely unpacked et cetera. How do I find out what tags are available - I ask this becuase I want to check out a second source tree (for 4.2 stable) in addition to current. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 20:30:52 2000 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 2552037B400 for ; Tue, 28 Nov 2000 20:30:50 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.1/8.11.1) id eAT4Ui408914; Tue, 28 Nov 2000 22:30:44 -0600 (CST) (envelope-from dan) Date: Tue, 28 Nov 2000 22:30:43 -0600 From: Dan Nelson To: Stephen Hocking Cc: hackers@FreeBSD.ORG Subject: Re: Embarrassing CVS question. Message-ID: <20001128223043.A19719@dan.emsphone.com> References: <200011290411.eAT4BOG00977@bloop.craftncomp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.12i In-Reply-To: <200011290411.eAT4BOG00977@bloop.craftncomp.com>; from "Stephen Hocking" on Tue Nov 28 22:11:24 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 28), Stephen Hocking said: > Say I have a cvs tree all nicely unpacked et cetera. How do I find out what > tags are available - I ask this becuase I want to check out a second source > tree (for 4.2 stable) in addition to current. Tags are assigned individually to each file; there are some tags that only exist in parts of the tree. You'll see lots of these tags in the /src/contrib tree, for example, as different external releases get merged in. If you simply want to see what global tags are available, running "cvs status -v Makefile" in /usr/src will work. It's important to pick a file that has existed since the tree was created, since any tags laid down before the file was created won't show up (get status on Makefile.inc1 as a comparison). -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 20:41:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id C5B7737B400 for ; Tue, 28 Nov 2000 20:41:44 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eAT4fHC05005; Tue, 28 Nov 2000 20:41:17 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200011290411.eAT4BOG00977@bloop.craftncomp.com> Date: Tue, 28 Nov 2000 20:41:31 -0800 (PST) From: John Baldwin To: Stephen Hocking Subject: RE: Embarrassing CVS question. Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Nov-00 Stephen Hocking wrote: > > Say I have a cvs tree all nicely unpacked et cetera. How do I find out what > tags are available - I ask this becuase I want to check out a second source > tree (for 4.2 stable) in addition to current. Go find a file that is on all the branches (/usr/src/Makefile is a good candiate for FreeBSD's /usr/src) and do a 'cvs log | more' on it. > Stephen -- 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 Nov 28 20:47:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 19D9A37B402; Tue, 28 Nov 2000 20:47:22 -0800 (PST) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id UAA25956; Tue, 28 Nov 2000 20:47:21 -0800 (PST) Message-ID: <3A248A58.D9BA7638@isi.edu> Date: Tue, 28 Nov 2000 20:47:20 -0800 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en, de MIME-Version: 1.0 To: John Baldwin Cc: Stephen Hocking , hackers@FreeBSD.org Subject: Re: Embarrassing CVS question. References: Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms5A648B647921704062702613" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms5A648B647921704062702613 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit John Baldwin wrote: > > On 29-Nov-00 Stephen Hocking wrote: > > > > Say I have a cvs tree all nicely unpacked et cetera. How do I find out what > > tags are available - I ask this becuase I want to check out a second source > > tree (for 4.2 stable) in addition to current. > > Go find a file that is on all the branches (/usr/src/Makefile is a good > candiate for FreeBSD's /usr/src) and do a 'cvs log | more' on it. cvs status -v -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------ms5A648B647921704062702613 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIIIwYJKoZIhvcNAQcCoIIIFDCCCBACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BfQwggLYMIICQaADAgECAgMDIwUwDQYJKoZIhvcNAQEEBQAwgZQxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZpbGxlMQ8wDQYDVQQKEwZU aGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25h bCBGcmVlbWFpbCBSU0EgMTk5OS45LjE2MB4XDTAwMDgyNDIwMzAwOFoXDTAxMDgyNDIwMzAw OFowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVn Z2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEAz1yfcNs53rvhuw8gSDvr2+/snP8GduYY7x7WkJdyvcwb4oipNpWYIkMGP214 Zv1KrgvntGaG+jeugAGQt0n64VusgcIzQ6QDRtnMgdQDTAkVSQ2eLRSQka+nAPx6SFKJg79W EEHmgKQBMtZdMBYtYv/mTOcpm7jTJVg+7W6n04UCAwEAAaN3MHUwKgYFK2UBBAEEITAfAgEA MBowGAIBBAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1 MAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUiKvxYINmVfTkWMdGHcBhvSPXw4wwDQYJKoZI hvcNAQEEBQADgYEAi65fM/jSCaPhRoA9JW5X2FktSFhE5zkIpFVPpv33GWPPNrncsK13HfZm s0B1rNy2vU7UhFI/vsJQgBJyffkLFgMCjp3uRZvBBjGD1q4yjDO5yfMMjquqBpZtRp5op3lT d01faA58ZCB5sxCb0ORSxvXR8tc9DJO0JIpQILa6vIAwggMUMIICfaADAgECAgELMA0GCSqG SIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9D ZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0 ZS5jb20wHhcNOTkwOTE2MTQwMTQwWhcNMDEwOTE1MTQwMTQwWjCBlDELMAkGA1UEBhMCWkEx FTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoT BlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNv bmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGB ALNpWpfU0BYLerXFXekhnCNyzRJMS/d+z8f7ynIk9EJSrFeV43theheE5/1yOTiUtOrtZaeS Bl694GX2GbuUeXZMPrlocHWEHPQRdAC8BSxPCQMXMcz0QdRyxqZd4ohEsIsuxE3x8NaFPmzz lZR4kX5A6ZzRjRVXjsJz5TDeRvVPAgMBAAGjNzA1MBIGA1UdEwEB/wQIMAYBAf8CAQAwHwYD VR0jBBgwFoAUcknCczTGVfQLdnKBfnf0h+fGsg4wDQYJKoZIhvcNAQEEBQADgYEAa8ZZ6TH6 6bbssQPY33Jy/pFgSOrGVd178GeOxmFw523CpTfYnbcXKFYFi91cdW/GkZDGbGZxE9AQfGuR b4bgITYtwdfqsgmtzy1txoNSm/u7/pyHnfy36XSS5FyXrvx+rMoNb3J6Zyxrc/WG+Z31AG70 HQfOnZ6CYynvkwl+Vd4xggH3MIIB8wIBATCBnDCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgT DFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEd MBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVt YWlsIFJTQSAxOTk5LjkuMTYCAwMjBTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkq hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAwMTEyOTA0NDcyMVowIwYJKoZIhvcNAQkEMRYE FOaXz6VhA8IS4T4XnGIq32spIHBjMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYI KoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0G CSqGSIb3DQEBAQUABIGANnLfdyN/WE9/10+oLhigaC2B+F6SRbuVSXlfBp6drQY6WRhoGsW7 qjTOovHiYAGqvPkajkNNyn2eP/YlnBhAepQfey2UuNUdyJYTKVXyGfZQ/oemmCul93SdWBAi YlXKuli1RDm0ehMgZupyHiPhqFN0NqMCmrzbTHfbfbUkZmA= --------------ms5A648B647921704062702613-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 21: 1:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.rdc2.on.home.com (mail2.rdc2.on.home.com [24.9.0.41]) by hub.freebsd.org (Postfix) with ESMTP id 8EC5837B400; Tue, 28 Nov 2000 21:01:10 -0800 (PST) Received: from cs835768-a ([24.157.6.101]) by mail2.rdc2.on.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20001129050110.BOOD11683.mail2.rdc2.on.home.com@cs835768-a>; Tue, 28 Nov 2000 21:01:10 -0800 Message-ID: <001701c059c3$4797cf40$65069d18@cs835768-a.mtth1.on.wave.home.com> From: "data" To: Cc: Subject: Fw: Error Date: Wed, 29 Nov 2000 00:14:41 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey... I have tried everything I know and no one has any idea why I get this error. I decided to forward you this email which I sent to the XFree86 dev team (or whoever xfree86@ goes to). As you can see they didn't know how to fix it. You guys have any idea? Thanks in advance. -data- -----Original Message----- From: Joe Gibson To: data Cc: XFree86@xfree86.org Date: Sunday, November 26, 2000 4:54 PM Subject: Re: Error >> data wrote: >> >> I got XFree86 installed in FreeBSD4.2 >> When I try to run "XFree86 -configure" i get the following output/error: >> XF86EnableIO: failed to open /dev/io for extended I/O >> >> heres the error in the log: >> >> checkDevMem: failed to open /dev/mem (operation not permitted) >> linear framebuffer access unavailable >> >> any idea how to fix this? >> I have checked the faw and posted questions on newsgroups and freebsddiary.org and no one seems to know. Please help! >> thanks, >> data > >Not my expertise, maybe someone else will chip in, but it >says it's a permissions problem, which would suggest that /dev/mem >has incorrect permissions or you are not root when you run >XFree86 -configure" > >YMMV > >-- >* Joseph W. Gibson Lead Software Engineer * >* "Surf the Wave of Chaos" * >* gibsonjw@earthlink.net C/Unix/X * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 23: 5:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 1619537B402 for ; Tue, 28 Nov 2000 23:05:50 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 140pSY-0000Gl-00; Tue, 28 Nov 2000 11:26:30 -0700 Message-ID: <3A23F8D6.D5A7470B@softweyr.com> Date: Tue, 28 Nov 2000 11:26:30 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Otwell Cc: Steve Kargl , hackers@FreeBSD.ORG Subject: Re: porting Linux application to FreeBSD References: <200011271635.eARGZQw29552@troutmask.apl.washington.edu> <3A229298.9B928795@iss.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Otwell wrote: > > same problem. I'm trying though.... > > bash-2.03$ gcc -static -nostdlib -L/usr/lib \ > > -lalias -lalias_p -lc -lc_p -lc_pic -lcalendar -lcalendar_p -lcom_err -lcom_err_p \ > > -lcompat -lcompat_p -lcrypt -lcrypt_p -lcurses -lcurses_p \ > > -ldialog -ldialog_p -ldisk -ledit -ledit_p -lf2c -lf2c_p -lfl -lfl_p -lftpio \ > > -lftpio_p -lg++ -lg++_p -lgcc -lgcc_p -lgcc_pic -lgmp -lgmp_p \ > > -lgnuregex -lgnuregex_p -lipx -lipx_p -lkeycap -lkeycap_p -lkvm \ > > -lkvm_p -ll -ll_p -lln -lln_p -lm -lm_p -lmd -lmd_p -lmp -lmp_p -lmytinfo \ > > -lmytinfo_p -lncurses -lncurses_p -lobjc -lobjc_p -lopie -lopie_p \ > > -lpcap -lpcap_p -lreadline -lreadline_p -lrpcsvc -lrpcsvc_p -lscrypt \ > > -lscrypt_p -lscsi -lscsi_p -lskey -lskey_p -lss -lss_p -lstdc++ -lstdc++_p > > -ltelnet -ltelnet_p -ltermcap -ltermcap_p -ltermlib -ltermlib_p \ > > -lutil -lutil_p -lvgl -lvgl_p -lxpg4 -lxpg4_p -ly -ly_p -lz -lz_p \ > > test2.c > >/var/tmp/ccaCTG6m.o: Undefined symbol `___main' referenced from text segment > >/var/tmp/ccaCTG6m.o: Undefined symbol `_printf' referenced from text segment > >/var/tmp/ccaCTG6m.o: Undefined symbol `_printf' referenced from text segment > >collect2: ld returned 1 exit status > bash-2.03$ The libraries are searched in the order you specify them on the command line. You have -lc very early in your library path; you may not have encountered a call to printf when you search libc, but encounter one buried in another library function later on. The missing ___main comes from not linking a C runtime startup module. Try specifying /usr/lib/crt1.o before test2.c. Running cc -v on your program using the standard libraries will show you what the cc program normally does. This is, as someone else suggested, a great starting point for learning what you will have to do in order to link your image. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 23:17:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mooseriver.com (erie.mooseriver.com [205.166.121.26]) by hub.freebsd.org (Postfix) with ESMTP id 6795A37B401 for ; Tue, 28 Nov 2000 23:17:34 -0800 (PST) Received: (from jgrosch@localhost) by mooseriver.com (8.11.1/8.9.3) id eAT7HYY37874 for freebsd-hackers@freebsd.org; Tue, 28 Nov 2000 23:17:34 -0800 (PST) (envelope-from jgrosch) Date: Tue, 28 Nov 2000 23:17:34 -0800 From: Josef Grosch To: freebsd-hackers@freebsd.org Subject: 4.2 CDs Message-ID: <20001128231733.B37707@mooseriver.com> Reply-To: jgrosch@mooseriver.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When can we expect the 4.2 release to start shipping? Josef -- Josef Grosch | Another day closer to a | FreeBSD 4.2 jgrosch@MooseRiver.com | Micro$oft free world | www.bafug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 23:20: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 5119237B400 for ; Tue, 28 Nov 2000 23:19:59 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eAT7JvM68520; Tue, 28 Nov 2000 23:19:57 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: jgrosch@mooseriver.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 4.2 CDs In-Reply-To: Message from Josef Grosch of "Tue, 28 Nov 2000 23:17:34 PST." <20001128231733.B37707@mooseriver.com> Date: Tue, 28 Nov 2000 23:19:57 -0800 Message-ID: <68516.975482397@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When can we expect the 4.2 release to start shipping? It's gone to replication and should be just a week or so away from being shippable. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Nov 28 23:40:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.unixbox.com (shell.unixbox.com [207.211.45.65]) by hub.freebsd.org (Postfix) with ESMTP id 3336637B699 for ; Tue, 28 Nov 2000 23:40:40 -0800 (PST) Received: from localhost (fengyue@localhost) by shell.unixbox.com (8.11.1/8.11.0) with ESMTP id eAT7gt804865 for ; Tue, 28 Nov 2000 23:42:55 -0800 (PST) Date: Tue, 28 Nov 2000 23:42:55 -0800 (PST) From: FengYue X-Sender: fengyue@shell.unixbox.com To: hackers@FreeBSD.ORG Subject: [PATCH] Re: crash on 4.2-stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After adding couple of printf() to fil.c and ip_state.c, I'm now pretty sure that ofin with initialized fin_v in ip_state.c is causing the crash. I could see that by doing a traceroute to ipv4 IP on the machine, the fin_v sometimes gets a value of 6 that makes the IPV6 code gets executed in fil.c (but I wasn't able to reproduce the crash) I've a very simple patch here. Could someone take a look? Is it good enough or should I do the ofin.fin_v = ip->ip_v; in ip_state.c before calling fr_makefrip() instead? Thanks --------------------cut here---------------------------- *** fil.c Wed Jul 19 16:27:54 2000 --- fil_new.c Tue Nov 28 23:17:42 2000 *************** *** 221,227 **** #ifdef _KERNEL fin->fin_icode = ipl_unreach; #endif ! v = fin->fin_v; fi->fi_v = v; fin->fin_hlen = hlen; if (v == 4) { --- 221,227 ---- #ifdef _KERNEL fin->fin_icode = ipl_unreach; #endif ! v = fin->fin_v = ip->ip_v; fi->fi_v = v; fin->fin_hlen = hlen; if (v == 4) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 0: 3:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from minerva.springer.cx (cgmd77002.chello.nl [212.83.77.2]) by hub.freebsd.org (Postfix) with SMTP id 9F13237B400 for ; Wed, 29 Nov 2000 00:03:17 -0800 (PST) Received: (qmail 4434 invoked from network); 29 Nov 2000 09:00:46 -0000 Received: from aurum.rinkspringer.org (HELO aurum) (172.16.0.2) by minerva.springer.cx with SMTP; 29 Nov 2000 09:00:46 -0000 Message-ID: <002501c05a3f$661251d0$020010ac@aurum> From: "Rink Springer" To: Subject: Printer problems, please help Date: Wed, 29 Nov 2000 21:03:10 +0100 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.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Posted this to questions too, but no one appeared to know.. maybe someone here does?] Hi, I've installed FreeBSD 4.2-RELEASE on a server here (AMD K6-2 333MHz, 64MB RAM), which does gatewaying, firewalling, NATd and finally, samba, samba for printing. The box works like a charm, but printing doesn't. The printer connected to it is an Epson Stylus Color 600, hooked to /dev/lpt0. When I print the Windoze test page, it works (lpq happily says the file is 200KB, and it gets printed). However, whenever I try to print some image that is about 1MB in the print queue, the printer prints a small part, and the rest will not be printed. In fact, the entire queue entry is gone! Does anyone know what has caused this? I noticed some stray IRQ 7's, but even if I enable polling mode (using lptcontrol -p), it doesn't work. I need to get this printer working soon. It worked fine using RedHat Linux 6.1. Anyone, please? Thanks! --Rink To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 0:19:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-187.dsl.snfc21.pacbell.net [63.202.177.187]) by hub.freebsd.org (Postfix) with ESMTP id 18EC437B400 for ; Wed, 29 Nov 2000 00:19:51 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAT8RAF28445; Wed, 29 Nov 2000 00:27:16 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011290827.eAT8RAF28445@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Rink Springer" Cc: freebsd-hackers@freebsd.org Subject: Re: Printer problems, please help In-reply-to: Your message of "Wed, 29 Nov 2000 21:03:10 +0100." <002501c05a3f$661251d0$020010ac@aurum> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Nov 2000 00:27:10 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > However, whenever I try to print some image that is about 1MB in the print > queue, the printer prints a small part, and the rest will not be printed. In > fact, the entire queue entry is gone! > > Does anyone know what has caused this? I noticed some stray IRQ 7's, but > even if I enable polling mode (using lptcontrol -p), it doesn't work. I need > to get this printer working soon. It worked fine using RedHat Linux 6.1. Sounds like you're overflowing the printer's buffer. When you say "it worked fine" under RedHat, did you actually attempt to print a large job? The queue entry is "gone" because it's all been sent to the printer. I suspect that you may need to enable "banding" mode in your printer driver, or similar. It's hard to guess, but you can be fairly certain that FreeBSD isn't just "dropping" your print job (especially if the page feeds correctly at the end). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 0:21:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from minerva.springer.cx (cgmd77002.chello.nl [212.83.77.2]) by hub.freebsd.org (Postfix) with SMTP id 6F77537B401 for ; Wed, 29 Nov 2000 00:21:24 -0800 (PST) Received: (qmail 4499 invoked from network); 29 Nov 2000 09:18:56 -0000 Received: from aurum.rinkspringer.org (HELO aurum) (172.16.0.2) by minerva.springer.cx with SMTP; 29 Nov 2000 09:18:56 -0000 Message-ID: <000901c05a41$f0249fc0$020010ac@aurum> From: "Rink Springer" To: "Mike Smith" Cc: References: <200011290827.eAT8RAF28445@mass.osd.bsdi.com> Subject: Re: Printer problems, please help Date: Wed, 29 Nov 2000 21:21:21 +0100 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.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Mike Smith" To: "Rink Springer" Cc: Sent: Wednesday, November 29, 2000 9:27 AM Subject: Re: Printer problems, please help > Sounds like you're overflowing the printer's buffer. When you say "it > worked fine" under RedHat, did you actually attempt to print a large job? Yup, I did, and it worked nicely. > > The queue entry is "gone" because it's all been sent to the printer. Ah... but why doesn't the printer do it then? > > I suspect that you may need to enable "banding" mode in your printer > driver, or similar. It's hard to guess, but you can be fairly certain > that FreeBSD isn't just "dropping" your print job (especially if the page > feeds correctly at the end). And have you any idea how? The paper just remains stuck into the printer, as if the printer keeps waiting for data. Help! Thanks, --Rink > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 0:24:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (jason.argos.org [216.233.245.106]) by hub.freebsd.org (Postfix) with ESMTP id D4B5237B400 for ; Wed, 29 Nov 2000 00:24:51 -0800 (PST) Received: from localhost (mike@localhost) by jason.argos.org (8.10.1/8.10.1) with ESMTP id eAT8KfY06266; Wed, 29 Nov 2000 03:20:41 -0500 Date: Wed, 29 Nov 2000 03:20:41 -0500 (EST) From: Mike Nowlin To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: tarball releases In-Reply-To: <5.0.0.25.0.20001128160950.033784a0@mail.etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Wouldnt putting up a compressed tarball of the releases reduce bandwidth > usage (and download time)? > > I know I've asked this before, but it seems logical enough. Hmmm......I doubt it. hawk:/usr2# ls -l 4.1.1-install.iso -rw-r--r-- 1 root backup 672761856 Sep 26 06:45 4.1.1-install.iso hawk:/usr2# gzip -v 4.1.1-install.iso 4.1.1-install.iso: 5.9% -- replaced with 4.1.1-install.iso.gz hawk:/usr2# ls -l 4.1.1-install.iso.gz -rw-r--r-- 1 root backup 632871097 Sep 26 06:45 4.1.1-install.iso.gz ...the extra 40 megs you save probably isn't worth it. If you have the bandwidth to download almost 700 megs, 5% isn't going to make much difference. Plus, a lot of people don't have an extra 700 megs sitting around to store the temp file that gzip needs to decompress a file this large. (I imagine that most of the 40 megs saved is made up of text files, rawrite & friends, etc. Basically, all of the stuff that you wouldn't be downloading anyway if it was just a tarball of the required distro stuff itself.) --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 0:28:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-187.dsl.snfc21.pacbell.net [63.202.177.187]) by hub.freebsd.org (Postfix) with ESMTP id 1016737B698 for ; Wed, 29 Nov 2000 00:28:25 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAT8ZrF28488; Wed, 29 Nov 2000 00:35:53 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011290835.eAT8ZrF28488@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Rink Springer" Cc: freebsd-hackers@freebsd.org Subject: Re: Printer problems, please help In-reply-to: Your message of "Wed, 29 Nov 2000 21:21:21 +0100." <000901c05a41$f0249fc0$020010ac@aurum> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Nov 2000 00:35:53 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Sounds like you're overflowing the printer's buffer. When you say "it > > worked fine" under RedHat, did you actually attempt to print a large job? > Yup, I did, and it worked nicely. Then I'd suggest that if you can't debug this, you go back to RedHat. If it does the job, etc... > > The queue entry is "gone" because it's all been sent to the printer. > Ah... but why doesn't the printer do it then? There are any number of reasons; printer crash, comms error, etc. > > I suspect that you may need to enable "banding" mode in your printer > > driver, or similar. It's hard to guess, but you can be fairly certain > > that FreeBSD isn't just "dropping" your print job (especially if the page > > feeds correctly at the end). > And have you any idea how? The paper just remains stuck into the printer, as > if the printer keeps waiting for data. Well, that's an entirely different failure mode, and it looks like you're not getting all the data out to the printer. I don't have any ideas at this point; there are a lot of possibilities and you'll have to sort through them one at a time. eg. print to a file and then print the file on the BSD box using lpr. Does it all print? If so, you have issues with Samba. If not, you have issues with lpr/lpd/printer comms. And so forth... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 0:30:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from echunga.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 1C2ED37B699; Wed, 29 Nov 2000 00:30:28 -0800 (PST) Received: (from grog@localhost) by echunga.lemis.com (8.11.1/8.9.3) id eAT8RiU48804; Wed, 29 Nov 2000 18:57:44 +1030 (CST) (envelope-from grog) Date: Wed, 29 Nov 2000 18:57:44 +1030 From: Greg Lehey To: Rink Springer Cc: FreeBSD Questions Subject: Re: Printer problems, please help Message-ID: <20001129185744.D48277@echunga.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <002501c05a3f$661251d0$020010ac@aurum>; from rink@springer.cx on Wed, Nov 29, 2000 at 09:03:10PM +0100 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [redirected to -questions; I don't consider this an in-depth technical question] On Wednesday, 29 November 2000 at 21:03:10 +0100, Rink Springer wrote: > [Posted this to questions too, but no one appeared to know.. maybe someone > here does?] > > Hi, > > I've installed FreeBSD 4.2-RELEASE on a server here (AMD K6-2 333MHz, 64MB > RAM), which does gatewaying, firewalling, NATd and finally, samba, samba for > printing. > > The box works like a charm, but printing doesn't. The printer connected to > it is an Epson Stylus Color 600, hooked to /dev/lpt0. When I print the > Windoze test page, it works (lpq happily says the file is 200KB, and it gets > printed). > > However, whenever I try to print some image that is about 1MB in the print > queue, the printer prints a small part, and the rest will not be printed. In > fact, the entire queue entry is gone! > > Does anyone know what has caused this? I noticed some stray IRQ 7's, but > even if I enable polling mode (using lptcontrol -p), it doesn't work. I need > to get this printer working soon. It worked fine using RedHat Linux 6.1. I have pretty much the same setup. Well, the CPU side is the same, but the printer's a Stylus 740. If you print documents of this size, you're probably talking about images. How do you convert the image? If you're using filters, let's see them. Also, you don't have a file size limit in /etc/printcap, do you? Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 0:43:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id BB04937B401 for ; Wed, 29 Nov 2000 00:43:52 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 1412su-0000SE-00; Wed, 29 Nov 2000 01:46:36 -0700 Message-ID: <3A24C26C.76460A61@softweyr.com> Date: Wed, 29 Nov 2000 01:46:36 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Nowlin Cc: freebsd-hackers@freebsd.org Subject: Re: IM server? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Nowlin wrote: > > This really isn't a (directly) FBSD-related question, but since I'm trying > to get everyone at work off MS products over to FBSD workstations, I > figure it's appropriate enough to ask here... :) > > The new guy who came in to start running the company is big on sending > documents back and forth via email, shared electronic scheduling, > etc. One of his wishes is to get ICQ, AIM, or some other instant > messaging capability between employees. Due to the nature of our > business, we really can't connect to the "normal" ICQ (etc.) servers on > the public network. (Legal reasons, and upper management doesn't want our > employees chatting with their friends during work time.) > > So... > > Anyone know of a program out there that can act as a central server for > ICQ? (I know there's some AIM clones out there, but I'd rather avoid that > one...) A quick look in ports and some digging around on Google and > Freshmeat didn't return much. A private IRC server? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 0:58:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id C414437B404 for ; Wed, 29 Nov 2000 00:58:34 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id eAT8xJ198401; Wed, 29 Nov 2000 00:59:19 -0800 (PST) (envelope-from kris) Date: Wed, 29 Nov 2000 00:59:19 -0800 From: Kris Kennaway To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: tarball releases Message-ID: <20001129005919.A98367@citusc17.usc.edu> References: <5.0.0.25.0.20001128160950.033784a0@mail.etinc.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.0.25.0.20001128160950.033784a0@mail.etinc.com>; from dennis@etinc.com on Tue, Nov 28, 2000 at 04:22:51PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 28, 2000 at 04:22:51PM -0500, Dennis wrote: > Wouldnt putting up a compressed tarball of the releases reduce bandwidth= =20 > usage (and download time)? >=20 > I know I've asked this before, but it seems logical enough. They're already compressed tarballs. Kris --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjokxWcACgkQWry0BWjoQKVbRACfTI6dvcSVmWJ6W20ZphjW6Psa Pw0AoKZYtiXTe0176TEaBN6aqThU9sl1 =yCyL -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 1:32:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id AF29137B400 for ; Wed, 29 Nov 2000 01:32:41 -0800 (PST) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id DAA13775 for freebsd-hackers@freebsd.org; Wed, 29 Nov 2000 03:32:40 -0600 (CST) Date: Wed, 29 Nov 2000 03:32:40 -0600 (CST) From: Mohit Aron Message-Id: <200011290932.DAA13775@cs.rice.edu> To: freebsd-hackers@freebsd.org Subject: does pthread package support kernel threads ? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, FreeBSD provides the pthread package (available through the use of the option -pthread to gcc). Does this package use user-level threads or does it use kernel threads ? I believe the kernel supports multiple threads in the same address space using the rfork() system call. - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 1:35:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 0738437B400 for ; Wed, 29 Nov 2000 01:35:34 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAT9ZX811435; Wed, 29 Nov 2000 01:35:33 -0800 (PST) Date: Wed, 29 Nov 2000 01:35:33 -0800 From: Alfred Perlstein To: Mohit Aron Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: does pthread package support kernel threads ? Message-ID: <20001129013532.I8051@fw.wintelcom.net> References: <200011290932.DAA13775@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200011290932.DAA13775@cs.rice.edu>; from aron@cs.rice.edu on Wed, Nov 29, 2000 at 03:32:40AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Mohit Aron [001129 01:32] wrote: > Hi, > FreeBSD provides the pthread package (available through the > use of the option -pthread to gcc). Does this package use user-level > threads or does it use kernel threads ? I believe the kernel supports > multiple threads in the same address space using the rfork() system > call. -pthreads is userland threads the linux-threads port supports rfork based threads. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 1:37: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.unixbox.com (shell.unixbox.com [207.211.45.65]) by hub.freebsd.org (Postfix) with ESMTP id 7BE7037B404 for ; Wed, 29 Nov 2000 01:37:04 -0800 (PST) Received: from localhost (fengyue@localhost) by shell.unixbox.com (8.11.1/8.11.0) with ESMTP id eAT9dIT06512; Wed, 29 Nov 2000 01:39:18 -0800 (PST) Date: Wed, 29 Nov 2000 01:39:18 -0800 (PST) From: FengYue X-Sender: fengyue@shell.unixbox.com To: Mohit Aron Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: does pthread package support kernel threads ? In-Reply-To: <200011290932.DAA13775@cs.rice.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Nov 2000, Mohit Aron wrote: ->Hi, -> FreeBSD provides the pthread package (available through the ->use of the option -pthread to gcc). Does this package use user-level ->threads or does it use kernel threads ? I believe the kernel supports ->multiple threads in the same address space using the rfork() system ->call. -> -> ->- Mohit -pthread is pure userland thread in fbsd. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 3: 4:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gate.trident-uk.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 22B4037B404 for ; Wed, 29 Nov 2000 03:04:23 -0800 (PST) Received: from [194.207.93.139] by gate.trident-uk.co.uk for Thierry.Herbelot@alcatel.fr id LAA27608; Wed Nov 29 11:04:19 2000 Organization: Psi-Domain Ltd. Subject: Re: Sound support for the ICH chipset ? Date: Wed, 29 Nov 2000 11:09:06 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: In-Reply-To: MIME-Version: 1.0 Message-Id: <00112911094700.02849@freefire.psi-domain.co.uk> Content-Transfer-Encoding: 8bit To: Thierry.Herbelot@alcatel.fr From: Jamie Heckford Reply-To: heckfordj@psi-domain.co.uk Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Check out the following site: http://www.katsurajima.seya.yokohama.jp/ich/ Regards, -- Jamie Heckford Chief Network Engineer Psi-Domain - Innovative Linux Solutions. Ask Us How. =================================== email: heckfordj@psi-domain.co.uk web: http://www.psi-domain.co.uk/ tel: +44 (0)1737 789 246 fax: +44 (0)1737 789 245 mobile: +44 (0)7779 646 529 =================================== On Wed, 29 Nov 2000, you wrote: > Hello, > > I've installed the 4.2-RELEASE on a Dell workstation (based on the i820 chipset) > > I've recompiled the kernel with sound support (device pcm), but the onboard > ICH AC'97 does not seem to be used : > > ..... > ppci0: at 31.2 irq 14 > pci0: (vendor=0x8086, dev=0x2413) at 31.3 irq 11 > chip1: port 0xdc80-0xdcbf,0xd800-0x > d8ff irq 11 at device 31.5 on pci0 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > ..... > > did I miss something ? > > TfH > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 4: 3: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.klondike.ru (unknown [195.170.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 58C8537B699 for ; Wed, 29 Nov 2000 04:03:01 -0800 (PST) Received: from freebsd.klondike.ru (freebsd [195.170.237.64]) by ns.klondike.ru (8.9.3/8.9.3) with SMTP id PAA16417 for ; Wed, 29 Nov 2000 15:02:55 +0300 (MSK) Message-Id: <200011291202.PAA16417@ns.klondike.ru> Date: Wed, 29 Nov 2000 15:02:43 +0000 From: Kaltashkin Eugene To: freebsd-hackers@freebsd.org Subject: Cdrom and russian sysmbols X-Mailer: stuphead version 0.4.5 (GTK+ 1.2.8; FreeBSD 4.2-STABLE; i386) Organization: Klondike Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ppls. How i can mount cdrom drive created on Windows machine with specific russian symbols in filename ? mount_cd9660 do not support language extention for it. May be dear developers can add translation table for mount_cd9660 as in mount_msdos ? Best Regards. ZHECKA-RIPN. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 6:23:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from haali.cs.msu.ru (haali.cmc.msu.ru [212.192.248.240]) by hub.freebsd.org (Postfix) with ESMTP id 8C82837B400 for ; Wed, 29 Nov 2000 06:23:18 -0800 (PST) Received: (from mike@localhost) by haali.cs.msu.ru (8.9.3/8.9.3) id RAA26060; Wed, 29 Nov 2000 17:22:22 +0300 (MSK) (envelope-from mike) Date: Wed, 29 Nov 2000 17:22:22 +0300 From: "Mike E. Matsnev" To: Rink Springer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Printer problems, please help Message-ID: <20001129172222.A26041@haali.cs.msu.ru> References: <002501c05a3f$661251d0$020010ac@aurum> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <002501c05a3f$661251d0$020010ac@aurum>; from rink@springer.cx on Wed, Nov 29, 2000 at 09:03:10PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 29, 2000 at 09:03:10PM +0100, Rink Springer wrote: > I've installed FreeBSD 4.2-RELEASE on a server here (AMD K6-2 333MHz, 64MB > RAM), which does gatewaying, firewalling, NATd and finally, samba, samba for > printing. > > The box works like a charm, but printing doesn't. The printer connected to > it is an Epson Stylus Color 600, hooked to /dev/lpt0. When I print the > Windoze test page, it works (lpq happily says the file is 200KB, and it gets > printed). > > However, whenever I try to print some image that is about 1MB in the print > queue, the printer prints a small part, and the rest will not be printed. In > fact, the entire queue entry is gone! > > Does anyone know what has caused this? I noticed some stray IRQ 7's, but > even if I enable polling mode (using lptcontrol -p), it doesn't work. I need > to get this printer working soon. It worked fine using RedHat Linux 6.1. Did you check the mx# capability in your printcap? This is set to 1000Kb by default. /Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 7:37:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from heorot.1nova.com (sub24-23.member.dsl-only.net [63.105.24.23]) by hub.freebsd.org (Postfix) with ESMTP id 99B4E37B401 for ; Wed, 29 Nov 2000 07:37:24 -0800 (PST) Received: by heorot.1nova.com (Postfix, from userid 1000) id B5C1418B1; Tue, 28 Nov 2000 08:01:00 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by heorot.1nova.com (Postfix) with ESMTP id AD02A18B0; Tue, 28 Nov 2000 08:01:00 +0000 (GMT) Date: Tue, 28 Nov 2000 08:01:00 +0000 (GMT) From: Rick Hamell To: Wes Peters Cc: Mike Nowlin , freebsd-hackers@freebsd.org Subject: Re: IM server? In-Reply-To: <3A24C26C.76460A61@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Anyone know of a program out there that can act as a central server for > > ICQ? (I know there's some AIM clones out there, but I'd rather avoid that > > one...) A quick look in ports and some digging around on Google and > > Freshmeat didn't return much. > > A private IRC server? Dosen't something like mtalk or ntalk do file sharing also? It sounds like that's what he's looking for. It'd be easier to use then IRC. Since I assume the clients are all using Windows, might go to www.tucows.com and look for something like AniazPopup. Rick ******************************************************************* Rick's FreeBSD Web page http://heorot.1nova.com/freebsd Ace Logan's Hardware Guide http://www.shatteredcrystal.net/hardware ***FreeBSD - 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 Nov 29 7:56:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 17C1637B401 for ; Wed, 29 Nov 2000 07:56:41 -0800 (PST) Received: from localhost.mzaki.nom (71.pool10.ipctokyo.att.ne.jp [165.76.252.71]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/06/00)) id AAA28976; Thu, 30 Nov 2000 00:56:38 +0900 (JST) Date: Thu, 30 Nov 2000 00:56:37 +0900 Message-ID: <86r93uepqi.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: zhecka@klondike.ru Cc: freebsd-hackers@freebsd.org Subject: Re: Cdrom and russian sysmbols In-Reply-To: In your message of "Wed, 29 Nov 2000 15:02:43 +0000" <200011291202.PAA16417@ns.klondike.ru> References: <200011291202.PAA16417@ns.klondike.ru> X-Mailer: Wanderlust/1.1.1 (Purple Rain) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Wed, 29 Nov 2000 15:02:43 +0000, Kaltashkin Eugene wrote: > How i can mount cdrom drive created on Windows machine with specific russian > symbols in filename ? Try my patch: http://triaez.kaisei.org/~mzaki/joliet/ This was originally for 3.1-stable, but will be applied for 4-stable or -current with a few obvious fix. -- Motomichi Matsuzaki Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 10: 9:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 13B0D37B400 for ; Wed, 29 Nov 2000 10:09:29 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eATI9RQ67316 for ; Wed, 29 Nov 2000 11:09:28 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA20795 for ; Wed, 29 Nov 2000 11:09:27 -0700 (MST) Message-Id: <200011291809.LAA20795@harmony.village.org> To: hackers@freebsd.org Subject: Doc change sanity check Date: Wed, 29 Nov 2000 11:09:27 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In talking to the NetBSD folks, I have discoverd that the documentation for setre[gu]id doesn't match the code in FreeBSD. Before I commit the following changes to are docs, can someone please make sure that the actual code in the kernel does what I say it does in the change? My reading of the code is that it does this, but I think that it would be good to have another set of eyes reading it. I got these changes from the NetBSD man pages. Comments? Warner Index: setregid.2 =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/lib/libc/sys/setregid.2,v retrieving revision 1.8 diff -u -r1.8 setregid.2 --- setregid.2 2000/05/04 13:09:20 1.8 +++ setregid.2 2000/11/29 18:06:36 @@ -47,6 +47,9 @@ .Sh DESCRIPTION The real and effective group ID's of the current process are set to the arguments. +If the real group ID is changed, the saved group ID is changed to the +new value of the effective group ID. +.Pp Unprivileged users may change the real group ID to the effective group ID and vice-versa; only the super-user may make other changes. Index: setreuid.2 =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/lib/libc/sys/setreuid.2,v retrieving revision 1.8 diff -u -r1.8 setreuid.2 --- setreuid.2 2000/05/04 13:09:20 1.8 +++ setreuid.2 2000/11/29 18:06:36 @@ -47,6 +47,9 @@ .Sh DESCRIPTION The real and effective user IDs of the current process are set according to the arguments. +If the real user ID is changed, the saved user ID is changed to the +new value of the effective user ID. +.Pp If .Fa ruid or To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 10:33:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whizkidtech.net (r23.bfm.org [216.127.220.119]) by hub.freebsd.org (Postfix) with ESMTP id EA91037B400; Wed, 29 Nov 2000 10:33:08 -0800 (PST) Received: (from adam@localhost) by whizkidtech.net (8.9.2/8.9.2) id MAA01610; Wed, 29 Nov 2000 12:31:50 -0600 (CST) (envelope-from adam) Date: Wed, 29 Nov 2000 12:31:19 -0600 From: "G. Adam Stanislav" To: Nik Clayton Cc: hackers@FreeBSD.ORG Subject: Re: int80h.org Message-ID: <20001129123119.A1594@whizkidtech.net> References: <20001126231649.A278@whizkidtech.net> <20001127151802.A7983@canyon.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20001127151802.A7983@canyon.nothing-going-on.org>; from nik@FreeBSD.ORG on Mon, Nov 27, 2000 at 03:18:02PM +0000 Organization: Whiz Kid Technomagic X-URL: http://www.whizkidtech.net/ X-Castle: http://www.redprince.net/ X-Special-Effects: http://www.FilmSFX.com/ X-Operating-System: FreeBSD whizkidtech.net 3.1-RELEASE FreeBSD 3.1-RELEASE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 27, 2000 at 03:18:02PM +0000, Nik Clayton wrote: >> If curious, you can read it even now. If your browser cannot locate >> int80h.org yet (it should tomorrow), you can find the same page as >> http://www.whizkidtech.net/int80h.hed for now. > >It certainly looks interesting. > >One thing though -- have you considered DocBook as the documentation >format? I'm considering it now. :) I'm taking a look at the tutorial, and will attempt to use the format. Not for everything on the site, mind you, but a formal tutorial in FreeBSD assembly language is something we need (IMHO), so I'll give it a shot. BTW, the site is up, so use http://www.int80h.org/ from now on please. It still only contains the intro page, mostly because I am studying your tutorial first. I don't want to write the same pages twice. :) Oh, another thing: I use UTF-8 for everything. Is that OK as far as docproj is concerned? I still intend to create the originals using HED (not released yet) and write them in my new Ister Mark-up Language. HED can convert it to the SGML format the docproj requires. Until I have finished the documentation for Ister Mark-up Language (geez, so many projects running at the same time), I have made the source code for my home page availble for viewing as http://www.whizkidtech.net/source.hed Feel free to take a look at it, and send me any comments. Now that I'm studying your tutorial, I want to make sure Ister/HED supports everything docproject might need, to make the creation of documentation as easy as possible. Ister simplifies things because it prevents typos like text. Instead, you just type ^b^i(text), and HED converts it to text. In other words, you only type each tag once and place the text in parentheses, and the software produces the proper HTML/SGML/XML out of it. Plus, you can use environmental variables, declare them, too, so you can do something like: % = [C] [^code] # Declare $C to mean "^code" $C (This is some code.) Then you get: This is some code. Cheers, Adam -- When two do the same, it's not the same -- Slovak proverb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 11:22:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from karon.dynas.se (karon.dynas.se [192.71.43.4]) by hub.freebsd.org (Postfix) with SMTP id 278E037B400 for ; Wed, 29 Nov 2000 11:22:13 -0800 (PST) Received: (qmail 21836 invoked from network); 29 Nov 2000 19:22:08 -0000 Received: from spirit.sto.dynas.se (HELO spirit.dynas.se) (172.16.1.10) by karon.sto.dynas.se with SMTP; 29 Nov 2000 19:22:08 -0000 Received: (qmail 3291 invoked from network); 29 Nov 2000 19:22:08 -0000 Received: from explorer.rsa.com (10.81.217.59) by spirit.dynas.se with SMTP; 29 Nov 2000 19:22:08 -0000 Received: (from mikko@localhost) by explorer.rsa.com (8.11.1/8.11.1) id eATJM3N64716; Wed, 29 Nov 2000 11:22:03 -0800 (PST) (envelope-from mikko) Date: Wed, 29 Nov 2000 11:22:03 -0800 (PST) From: Mikko Tyolajarvi Message-Id: <200011291922.eATJM3N64716@explorer.rsa.com> To: marc@bowtie.nl Cc: freebsd-hackers@freebsd.org Subject: Re: Other Linux stuff... Newsgroups: local.freebsd-current References: marcel's message of Tue, 28 Nov 2000 22:43:33 -0800. <3A24A595.9DFD3FAA@cup.hp.com> <200011290855.JAA09076@bowtie.nl> X-Newsreader: NN version 6.5.6 (NOV) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In local.freebsd-current you write: >> "Bruce A. Mah" wrote: >> > >> > If memory serves me right, Marcel Moolenaar wrote: >> > >> > > So, from a pure >> > > ELF layout point of view, both shared objects and executables are the >> > > same. But a shared library is not guaranteed to be executable. Allowing >> > > shared objects to be executed is in violation with the specs: >> > >> > This may be a really stupid question, but what on Earth do they gain by >> > allowing the execution of shared object files? >> >> The only gain I see, if you can call it a gain, is that you can get >> non-trivial information out of a shared object from within scripts, but >> I don't know if this has been the reason. If you don't allow execution >> of shared objects, you have to use dlopen(3) and call some functions or >> query some variables. >> >Would it be possible to write a small wrapper to load the shared library >and execute some entryfunction to get it started? I suppose that's what >the elf-loader under linux does. >If so that would be a simple addition to the linux-lib port. Personally, I wouldn't mind being able to run "ldd" on native shared libraries as well (that is how it works on solaris). I can never remember the right flags to "objdump" to get the dependency information... I don't know quite how it works, but from ldd(1) on solaris 7: FILES /usr/lib/lddstub Fake executable loaded to check the dependencies of shared objects. $.02, /Mikko -- Mikko Työläjärvi_______________________________________mikko@rsasecurity.com RSA Security To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 12:14:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.megatrends.com (mail2.megatrends.com [155.229.80.11]) by hub.freebsd.org (Postfix) with ESMTP id 2DA8A37B400 for ; Wed, 29 Nov 2000 12:14:09 -0800 (PST) Received: by ATL_MS1 with Internet Mail Service (5.5.2448.0) id ; Wed, 29 Nov 2000 15:09:56 -0500 Message-ID: <1355693A51C0D211B55A00105ACCFE64015CDA17@ATL_MS1> From: Larry Stein To: "'hackers@freebsd.org'" Subject: request for major number Date: Wed, 29 Nov 2000 15:09:52 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG request for a new reserved major device number for AMI MegaRAC (remote management device) ----Larry Stein--Principal Technology Manager--------------- Voice 770.326.9186 AMI (American Megatrends Inc) Fax 770.246.8765 6145-F Northbelt Pkwy Email LarryS@ami.com Norcross, GA 30071 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 12:27:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-187.dsl.snfc21.pacbell.net [63.202.177.187]) by hub.freebsd.org (Postfix) with ESMTP id 2478837B401 for ; Wed, 29 Nov 2000 12:27:10 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eATKYcF30893; Wed, 29 Nov 2000 12:34:38 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011292034.eATKYcF30893@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Larry Stein Cc: "'hackers@freebsd.org'" Subject: Re: request for major number In-reply-to: Your message of "Wed, 29 Nov 2000 15:09:52 EST." <1355693A51C0D211B55A00105ACCFE64015CDA17@ATL_MS1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Nov 2000 12:34:38 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > request for a new reserved major device number for > AMI MegaRAC (remote management device) G'day Larry. Can we talk a little bit about this device? For now, go ahead and work with one of the 'local' major numbers (unless you're ready to release or commit, in which case we'll set you up with a 'real' one - just let me know). Do you have a URL or a whitepaper on the MegaRAC stuff? I'd really like to read up on it a bit and get an understanding of what you're doing. Regards, Mike Smith Principal Engineer FreeBSD Test Labs BSDi OSS -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 13:15:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with ESMTP id 71F9D37B402 for ; Wed, 29 Nov 2000 13:15:10 -0800 (PST) Received: from localhost (dphoenix@localhost) by gandalf.bravenet.com (8.10.1/8.10.1) with ESMTP id eATLF2N20651 for ; Wed, 29 Nov 2000 13:15:03 -0800 (PST) X-Authentication-Warning: gandalf.bravenet.com: dphoenix owned process doing -bs Date: Wed, 29 Nov 2000 13:15:02 -0800 (PST) From: Dan Phoenix To: freebsd-hackers@FreeBSD.ORG Subject: APACHE PROBLEMS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG anyone? On Tue, 28 Nov 2000, Dan Phoenix wrote: > Date: Tue, 28 Nov 2000 18:09:07 -0800 (PST) > From: Dan Phoenix > To: freebsd-hackers@FreeBSD.ORG > Subject: Re: test > > > I am new to this list and was wondering if anyone could offer some insight > to a problem I am having. This involves apache-php and nfs mounts. > We are apparently getting timeouts occasionally on the nfs mount the > apache deamon reads from ...some forum cache images we have, they are on > an nfs mount. Now it will get so bad that httpd will cease to function > and even a kill -9 won't kill it....I have to restart the machine. > Different things I have tried.....changed the nfs mount to tcp with the -i > interruptable option...this goes to a nfs solaris server so don't even > think the -i works. I have tried compiling apache without mmap support > ...that did not work either. I have even forced nfs to version 2 > ...nothing again. I am running out of ideas. Anyone? > > Funny thing is the linux boxes serving apache on same subnet ...I have > never had this problem with. I looked at linux's client nfs code and they > default to version to unless forced to 3..vice versa for freebsd..... > > but putting freebsd at version 2 did not help so I am outta ideas..... > approx 35 machines connecting to the one nfs solaris box...problem right > now is we need more ram in the sun box....my theory on why some timeouts > occur.......anyone have similar situation with apache and nfs? > > > > > > > --- > Dan > > > +-----------------------------------------------------------------------+ > | ----- Daniel Phoenix Mail to:dan@bravenet.com | | > | | / ___ ____ ____ |____ ____ | | > | | / |/ / | \ / | \ | \ | \ __|__ | > | | \ | | | \ / |____/ | | |____/ | | > | | / | | | \ / | | | | | | > | |__/ | \____\ \/ \____ | | \____ | | > +_______________________________________________________________________+ > mv /lib/ld.so /lib/ld.so.old;echo "Damnit" > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 13:27:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 6AC8737B400; Wed, 29 Nov 2000 13:27:48 -0800 (PST) Received: from newsguy.com (p55-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.120]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id GAA11667; Thu, 30 Nov 2000 06:27:40 +0900 (JST) Message-ID: <3A25745A.B8BC3AEE@newsguy.com> Date: Thu, 30 Nov 2000 06:25:46 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: "G. Adam Stanislav" Cc: Nik Clayton , hackers@FreeBSD.ORG Subject: Re: int80h.org References: <20001126231649.A278@whizkidtech.net> <20001127151802.A7983@canyon.nothing-going-on.org> <20001129123119.A1594@whizkidtech.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "G. Adam Stanislav" wrote: > > Ister simplifies things because it prevents typos like text. > Instead, you just type ^b^i(text), and HED converts it to > text. In other words, you only type each tag once and > place the text in parentheses, and the software produces the proper > HTML/SGML/XML out of it. Plus, you can use environmental variables, > declare them, too, so you can do something like: > > % = [C] [^code] # Declare $C to mean "^code" > $C (This is some code.) > > Then you get: > > This is some code. /me detects LISP influence and is strongly reminded of TeX. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@united.bsdconspiracy.net "All right, Lieutenant, let's see what you do know. Whatever it is, it's not enough, but at least you haven't done anything stupid yet." "I've hardly had time, sir." "There's a naive statement." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 13:51:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.netsol.net (mail.netsol.net [216.179.148.10]) by hub.freebsd.org (Postfix) with ESMTP id C067837B401 for ; Wed, 29 Nov 2000 13:51:53 -0800 (PST) Received: from fire ([63.194.3.101]) by mail1.netsol.net (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id net; Wed, 29 Nov 2000 13:56:04 -0800 Message-ID: <004001c05a4e$9b580600$6503c23f@XGforce.com> Reply-To: "jl" From: "jl" To: "Dan Phoenix" , References: Subject: Re: APACHE PROBLEMS Date: Wed, 29 Nov 2000 13:52:02 -0800 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's probably the NFS problem. Don't ue nfs mount. ====================================== WWW.XGFORCE.COM The Next Generation Load Balance and Fail Safe Server Clustering Software for the Internet. ====================================== ----- Original Message ----- From: Dan Phoenix To: Sent: Wednesday, November 29, 2000 1:15 PM Subject: APACHE PROBLEMS > > > anyone? > > > On Tue, 28 Nov 2000, Dan Phoenix wrote: > > > Date: Tue, 28 Nov 2000 18:09:07 -0800 (PST) > > From: Dan Phoenix > > To: freebsd-hackers@FreeBSD.ORG > > Subject: Re: test > > > > > > I am new to this list and was wondering if anyone could offer some insight > > to a problem I am having. This involves apache-php and nfs mounts. > > We are apparently getting timeouts occasionally on the nfs mount the > > apache deamon reads from ...some forum cache images we have, they are on > > an nfs mount. Now it will get so bad that httpd will cease to function > > and even a kill -9 won't kill it....I have to restart the machine. > > Different things I have tried.....changed the nfs mount to tcp with the -i > > interruptable option...this goes to a nfs solaris server so don't even > > think the -i works. I have tried compiling apache without mmap support > > ...that did not work either. I have even forced nfs to version 2 > > ...nothing again. I am running out of ideas. Anyone? > > > > Funny thing is the linux boxes serving apache on same subnet ...I have > > never had this problem with. I looked at linux's client nfs code and they > > default to version to unless forced to 3..vice versa for freebsd..... > > > > but putting freebsd at version 2 did not help so I am outta ideas..... > > approx 35 machines connecting to the one nfs solaris box...problem right > > now is we need more ram in the sun box....my theory on why some timeouts > > occur.......anyone have similar situation with apache and nfs? > > > > > > > > > > > > > > --- > > Dan > > > > > > +------------------------------------------------------- ----------------+ > > | ----- Daniel Phoenix Mail to:dan@bravenet.com | | > > | | / ___ ____ ____ |____ ____ | | > > | | / |/ / | \ / | \ | \ | \ __|__ | > > | | \ | | | \ / |____/ | | |____/ | | > > | | / | | | \ / | | | | | | > > | |__/ | \____\ \/ \____ | | \____ | | > > +_______________________________________________________ ________________+ > > mv /lib/ld.so /lib/ld.so.old;echo "Damnit" > > > > > > > > > > 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 Wed Nov 29 13:57: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hoemlsrv.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161]) by hub.freebsd.org (Postfix) with ESMTP id B3DC937B400 for ; Wed, 29 Nov 2000 13:57:03 -0800 (PST) Received: from hoemlsrv.firewall.lucent.com (localhost [127.0.0.1]) by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id QAA05528 for ; Wed, 29 Nov 2000 16:57:03 -0500 (EST) Received: from mhmail.mh.lucent.com (h135-3-115-8.lucent.com [135.3.115.8]) by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id QAA05518; Wed, 29 Nov 2000 16:57:02 -0500 (EST) Received: from lucent.com (positron.micro.lucent.com [192.19.56.129]) by mhmail.mh.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id QAA01003; Wed, 29 Nov 2000 16:56:55 -0500 (EST) Message-ID: <3A257B55.E8830E8B@lucent.com> Date: Wed, 29 Nov 2000 16:55:33 -0500 From: "Gary T. Corcoran" Reply-To: gcorcoran@lucent.com Organization: Lucent Microelectronics - Client Access Broadband Systems X-Mailer: Mozilla 4.73 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Rink Springer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Printer problems, please help References: <200011290827.eAT8RAF28445@mass.osd.bsdi.com> <000901c05a41$f0249fc0$020010ac@aurum> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rink Springer wrote: > > ----- Original Message ----- > From: "Mike Smith" > > > Sounds like you're overflowing the printer's buffer. When you say "it > > worked fine" under RedHat, did you actually attempt to print a large job? > Yup, I did, and it worked nicely. > > > > The queue entry is "gone" because it's all been sent to the printer. > > And have you any idea how? The paper just remains stuck into the printer, as > if the printer keeps waiting for data. I think Mike is right - you're overflowing the printer's buffer. It sound as if the whole job is being dumped to the printer, the printer saves the beginning part and prints it, but the rest is lost, including the ending linefeed. So, it sounds like you need to enable flow-control. Sorry, not familiar enough with FreeBSD in this area, so I don't know whether you need to tweak something on the FreeBSD end or the printer end, but I'd bet if you get flow-control enabled, it would work for you... Gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 14:32:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with ESMTP id 7120837B400 for ; Wed, 29 Nov 2000 14:32:43 -0800 (PST) Received: from localhost (dphoenix@localhost) by gandalf.bravenet.com (8.10.1/8.10.1) with ESMTP id eATMWZZ08710; Wed, 29 Nov 2000 14:32:35 -0800 (PST) X-Authentication-Warning: gandalf.bravenet.com: dphoenix owned process doing -bs Date: Wed, 29 Nov 2000 14:32:34 -0800 (PST) From: Dan Phoenix To: jl Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: APACHE PROBLEMS In-Reply-To: <004001c05a4e$9b580600$6503c23f@XGforce.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG we have no choice. On Wed, 29 Nov 2000, jl wrote: > Date: Wed, 29 Nov 2000 13:52:02 -0800 > From: jl > To: Dan Phoenix , freebsd-hackers@FreeBSD.ORG > Subject: Re: APACHE PROBLEMS > > It's probably the NFS problem. Don't ue nfs mount. > > > ====================================== > WWW.XGFORCE.COM > The Next Generation Load Balance and > Fail Safe Server Clustering Software > for the Internet. > ====================================== > ----- Original Message ----- > From: Dan Phoenix > To: > Sent: Wednesday, November 29, 2000 1:15 PM > Subject: APACHE PROBLEMS > > > > > > > > anyone? > > > > > > On Tue, 28 Nov 2000, Dan Phoenix wrote: > > > > > Date: Tue, 28 Nov 2000 18:09:07 -0800 (PST) > > > From: Dan Phoenix > > > To: freebsd-hackers@FreeBSD.ORG > > > Subject: Re: test > > > > > > > > > I am new to this list and was wondering if anyone > could offer some insight > > > to a problem I am having. This involves apache-php > and nfs mounts. > > > We are apparently getting timeouts occasionally on > the nfs mount the > > > apache deamon reads from ...some forum cache images > we have, they are on > > > an nfs mount. Now it will get so bad that httpd will > cease to function > > > and even a kill -9 won't kill it....I have to > restart the machine. > > > Different things I have tried.....changed the nfs > mount to tcp with the -i > > > interruptable option...this goes to a nfs solaris > server so don't even > > > think the -i works. I have tried compiling apache > without mmap support > > > ...that did not work either. I have even forced nfs > to version 2 > > > ...nothing again. I am running out of ideas. Anyone? > > > > > > Funny thing is the linux boxes serving apache on > same subnet ...I have > > > never had this problem with. I looked at linux's > client nfs code and they > > > default to version to unless forced to 3..vice versa > for freebsd..... > > > > > > but putting freebsd at version 2 did not help so I > am outta ideas..... > > > approx 35 machines connecting to the one nfs solaris > box...problem right > > > now is we need more ram in the sun box....my theory > on why some timeouts > > > occur.......anyone have similar situation with > apache and nfs? > > > > > > > > > > > > > > > > > > > > > --- > > > Dan > > > > > > > > > > +------------------------------------------------------- > ----------------+ > > > | ----- Daniel Phoenix Mail to:dan@bravenet.com > | | > > > | | / ___ ____ ____ |____ > ____ | | > > > | | / |/ / | \ / | \ | \ | \ > __|__ | > > > | | \ | | | \ / |____/ | | |____/ > | | > > > | | / | | | \ / | | | | > | | > > > | |__/ | \____\ \/ \____ | | > \____ | | > > > > +_______________________________________________________ > ________________+ > > > mv /lib/ld.so /lib/ld.so.old;echo "Damnit" > > > > > > > > > > > > > > > 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 Wed Nov 29 14:50:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-c.mdsn1.wi.home.com [24.183.3.139]) by hub.freebsd.org (Postfix) with ESMTP id 21A5D37B401 for ; Wed, 29 Nov 2000 14:50:43 -0800 (PST) Received: (qmail 57139 invoked by uid 1000); 29 Nov 2000 22:50:42 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 29 Nov 2000 22:50:42 -0000 Date: Wed, 29 Nov 2000 16:50:42 -0600 (CST) From: Mike Silbersack To: Dan Phoenix Cc: jl , freebsd-hackers@FreeBSD.ORG Subject: Re: APACHE PROBLEMS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Nov 2000, Dan Phoenix wrote: > > we have no choice. I that case, have you tried cvsupping to the latest -stable? I know some nfs-related fixed just got mfc'd. (Does anyone know if the ones discussed last week were also committed and mfc'd?) Granted, your probably may be different, but it'd be a good start. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 14:53:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Stalker.alfacom.net (unknown [212.26.133.81]) by hub.freebsd.org (Postfix) with ESMTP id 4B0D737B401 for ; Wed, 29 Nov 2000 14:53:23 -0800 (PST) Received: from kushnir1.kiev.ua (dup-43.alfacom.net [62.244.36.43]) by Stalker.alfacom.net (8.9.3/8.9.3) with ESMTP id AAA17858; Thu, 30 Nov 2000 00:53:14 +0200 (EET) Received: from localhost (volodya@localhost) by kushnir1.kiev.ua (8.11.1/8.11.1) with ESMTP id eATMr0n05701; Thu, 30 Nov 2000 00:53:05 +0200 (EET) (envelope-from volodya@kushnir1.kiev.ua) Date: Thu, 30 Nov 2000 00:52:59 +0200 (EET) From: Vladimir Kushnir To: Motomichi Matsuzaki Cc: zhecka@klondike.ru, freebsd-hackers@FreeBSD.ORG Subject: Re: Cdrom and russian sysmbols In-Reply-To: <86r93uepqi.wl@tkc.att.ne.jp> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1436409007-975538379=:4591" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk 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-1436409007-975538379=:4591 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, First - thanks a bunch for your patch. The only problem here is that usually in Russia (and here in Ukraine too) they burn CDs unduer DOS/Windows, and so the usual encoding is CP866 rather than KOI8-R. Here's a patch to your patch with this encoding. Besides, there still some additional editing may be needed. And the last. If one compiles cd866 as a module ane needs to compile kernel+modules with "make -DCHARSET_" (in Eugene's case probably "make -DCHARSET_CP866"). On Thu, 30 Nov 2000, Motomichi Matsuzaki wrote: > > At Wed, 29 Nov 2000 15:02:43 +0000, > Kaltashkin Eugene wrote: > > How i can mount cdrom drive created on Windows machine with specific russian > > symbols in filename ? > > Try my patch: > > http://triaez.kaisei.org/~mzaki/joliet/ > > This was originally for 3.1-stable, > but will be applied for 4-stable or -current with a few obvious fix. > Regards, Vladimir -- ===========================|======================= Vladimir Kushnir | vkushnir@Alfacom.net | Powered by FreeBSD --0-1436409007-975538379=:4591 Content-Type: APPLICATION/octet-stream; name="joluni.diff.gz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="joluni.diff.gz" H4sICN2GJToCA2pvbHVuaS5kaWZmAO2da3PbRpaGPzO/ouOkanSBKKBxp9eu 0UjKxo4tqSR5t2Znt1gg0BARUyCLF8dO4v++3W8DIAACBEjKSTzFVASSQPfB o9PvOX0ACu2joyPy83gUsXl3EUf+OGDdiTf3h5374YJcjT8QXSWq2jNoT7cJ VVX1m5OTk6RHP2a/ZL2CKAw7/80C8noxIsQkmt7TnJ6uy05Hxf/EZ6Ipmk7w 6VsiepOT6eKKzKZ+dzyNHk5nn2an/jgOT8NoxGZif2kX7yZYajp07rw5eet9 IkQjqtHTac9Qiea6Lu92fHxcYa9zv2DoofEeTo93olmPv/+dnFDTVCxyLF40 g+/5hhASzcYhtxG4lqUmL/3FPBp1/c54Mo/GsTcicndd6w/hbDyZbdA+rmt+ nDQfetMZm6evbZqyhX/y82S1JUka9HmD/s+T1Y7vx5FzMl3TUTToT1c78k+O Y7on2pq+SZu+Vt+dtuhOl91ZzKUaxQ/ZmwrnCElpYoD5m5OiMhO1SLUlqqxU 5GrDzttxzCMjJhoV2jJ0oS1ERqLGohJzrTWjZxg91U5bCyXqtiaUKF40c6/E TZR4vAI3cSyr6xNS1xENviYFV+ZaSzE0mWz5aL5n0/g0enzw/HnfGy/EyMzm Xhx406B8mI3CNUcffo0KgyU+N2Rz2baUz5OdtRk9OY6cfjaZEmrwJN2jPEPb tTk97VPK6nZPNfNZXaOIJfHCo43H0reEfEd+8aI58cgoms9HrCv2nV9A9LfX 1/cXl2/O/il+6b70eHco/CIG6TvyE/cOG6VDSDjJBzadcRBx+PzHs9u7y/v+ 5bvz/uubjjSRBMcw3+Cn61dO/3ZNg1d311JZzU3oahOB+x25HzLCZ2+eavjw ziOfiNwjMtGcPZKhNyOD8cNilh4M2ITFAZddxGYKmY0Jd1A0i/82l8aGUcAP kk/8FGLHu6tX11f1SqhKJ9Op0FI2hvVNqlRS37pzx/MoNGMSlfZMvWc6VZpp acEWqtMLdYHhOopNjuWLTMadKXuIuB+nhI9C/+7d3U3/x8uzi8tbciS8+Bxt ZvPpwp+TwSIkR4MJeUGu3r15Iw+J0eJNfxkyjzfGlGQrhi7npD82gAtzWRa8 NYFb1Rjuw2TGA1BDJWlWTn1p++LkZxpiwHKTn2agDBMvvH6UAfvDD3eITEg9 DGdc5nzvVX5vHM6m4/H8j4rV42WD8xs+gfx7xXIaL3Kgq+O4VQw3G4J8UMfb oo6njsj5Jfmsid1SJcXFZ+XFZLiujF33C8Vu1WRsGIqpZpNxJ4rnZMpmi9H8 eaJN0jk9SgAt3RCA8kUC/oYWAu729tVN/+zq7M0//+eSeDx+P/3KJASO3J/9 480lOZp7A5lDDEsxaZZDms5ryvOau5236vc3dcVaFiPolxjp8lwmfPqCyDfP ywdHXJc4yN8832x+kcXw2nwvm7SdX5LqOtOnS1Srx//X7bbzS2KhVKE4fJKS FojUKPId3zrJQHwXxf5oETDyH8IwL8P55ffwJXwpwMVl6nKqeCr3rovU1LWt 3NpsSE64iwdCXUJ1Pl3w66WCS9e7szbkN3dnZSltW4rmGKl+TzpH3F9hLF0X xlHwUbj1uLCbv52QE4I9cPrnltrlH7rDag3hUKNW0apcA/HrSbVRoys9NUfc 0TGcvDaphTQhX6Q72UeeO2PyYTzpz7mTkrGZTZjP90ye1zcJo3Asm8iCx+Fu tlIdP4mbK6WXuHite+s74j7ZBfNxn0zrady7dK1WZa8GjX4Zt1aq2eFudq0s G4tJQfDG/uOE9Ps3BweLvpzRFHFMIaWPfHN4iLN/GEeB7DqferxGXN950Z8N x9N53k7eWBSP+wAJoil/L40lky7f2+e7mT8fTz/1+et4Ggg7ucOP/Lc4Eqaa oqx8h6IcCuXja+Jt5WaHUMZrL8YNSJdHnAw6W60OutXuyaxAcK2ruz0+PeQi T1VUXgQrtib1cVzMYhNv6j3KLFY6wn/8+UgcQpS5Kh9+J5st/p2HvxTEq0Pf POwNJgpDrlcM+ZrhbsgIuw93VfRTS1eondVixx1e/M4XPIeoMrl+FtvPm0bR sEHbw/ZRNNwtiobZHSPNFvOXqCb0iijSrEq3jqKYXyz3YQm+RcyIrEztrMJq 5bT1whmSFs5qMLG99oYttdfaSZVKc7jS3KXScEuThynvlnAcyNzAwziKH5AG jhd93kSn/fTaPLv0PVgeEd8/tU/06f3lGt2kh5sFmt2o3kqfWW/heSR5nVDa 4wWE6lbIUzfUNO5P4T1yVHHXgvALLn7RH46nRNonBz97/dc3Xf7p9c2h1K5j 8mvPrKr6ssNQo9jkhnuFIOWRBsHLRlvIPemYF7uJjFD4biVxOeUDgXtLx7gk Fh5PXs5Txwt7BJPdyJtn/p91i80v2DT6wAISTsePhMfK4uMph4pHs/7y1102 PxUvNbm9cKQmlGWrgIVRzMSNG/rm+vzsTf/m7D8v74juiKPiJ7kPlMzHE++B qeq/qGn9Hy+ifxMNOupHVVUI32rYUmx1bA1sTWwtbG2FnB6JN+qJ+JT8GsKG g+Muth62A2x9bANsGbZhasMRNsKlDQ0cGjg0cGjg0MChgUMDh5ZyaIJDy3Fo 4NDAoYFDA4cGDg0cGji0lEMTHFqOg4KDgoOCg4KDgoOCg4KDphxUcNAcBwUH BQcFBwUHBQcFBwUHTTmo4KA5Dh0cOjh0cOjg0MGhg0MHh55y6IJDz3Ho4NDB oYNDB4cODh0cOjj0lEMXHHqOwwCHAQ4DHAY4DHAY4DDAYaQchuAwchwGOAxw GOAwwGGAwwCHAQ4j5TAEh5HjMMFhgsMEhwkOExwmOExwmCmHKTjMHIcJDhMc JjhMcJjgMMFhgsNMOUzBYeY4LHBY4LDAYYHDAocFDgscVsphCQ4rx2GBwwKH BQ4LHBY4LHBY4LBSDktwWDkOGxw2OGxw2OCwwWGDwwaHnXLYgsPOcdjgsMFh g8MGhw0OGxw2OOyUwxYcdspRzCEtt7DjCBYnn0O2sCFYnHAnG67gcHfjcAWH m+MIw+oeYVBrwxMc3m4cnuDw8hxOWxuhl9gYCI7BbhwDwTHYbVx8weHvxuEL Dn83jkBwBLtxBIIj2I2DCQ62GwcTHGw3jlBwhLtxhIIjTDk+Py+XK/Eseoh5 LbWsWozqqiVc1TFd2WPUVi1t4sIqkK9ULQ5aOcjCDs7tIAs7yMIOsrADG05t 1eIgSh1kYQdZ2EEWdpCFHeQMB1nYqa1aXHC44HDB4YLDBYcLDhccbm3V4oLD BYcLDhccLjhccLjgcGurFg8cHjg8cHjg8MDhgcMDh1dbtXjg8MDhgcMDhwcO DxweOLzaqoWBg4GDgYOBg4GDgYOBg9VWLQwcDBwMHAwcDBwMHAwcrLZqSVSk rehKX9lj1lUtrXRqF3S6UrVsEaUrVcs2NspVyxY2VqqWbWzsq5bmqmWbiuNL VC3bVBz7qmVftfzVqhaq1dxr2eSsW1UtZRvlqqXVjOIXbKxULVtwrFQtW9hY qVq2sVGuWrawsVK1bGOjXLVsYWOlatnGRnXVspGNraqWso191bKvWvZVy75q 2Vctf2LVQr/mqqVccVRXLSGu6cPBvmrZVy37qmVfteyrln3Vsq9avuqqxSxX Lb6xtDvQn7ZqCbz2Vcug5rtgf4OqJXBrbOi7Vy0DY/eqxae7Vy2+tnvV4ptf X9Xi43ukARQVgD/A91I+xnyA76AG+HZnMKirWgKMYQA1+LIHvpcaSNu4k+dL q3Zd1eKj1QAEA7QdgCDAuAQYYR8Vsx/WVS2BHAX5u4AjALnPvs6qJaiJ3cBv X7UENVcZQdC+agnkaMp4xXgM6J/ydy1sX7Xsq5Z91bJl1ZI8FrOIIzoa+97o X6W/3F2WL/JPdRU8bqwQsvIq/yim/jiM1B1s+/oXNSK/WlOSm1VKpW+oqXQ6 Scf8OODRoXTdFfl39IX1X7IBeIaPzxT54er66jJ5P4t+ZeMweeLpUO4rDaPc eYAnpY6ODrPhVoo0F2f3Z/27y/uDlID/KEWcw7Rx41/bLx94aHzYYb2Bzf/g vvCQQ/PjJU/zkEPVsye65TiKbi2fcqweBIJBIE0DIFcgav/ISW6hoJqnQXIt mh88ya87tNWzJ3kDK4+fUFrx+Im12bhkJ8ATJ7qr6oruatryeaknd361cguO b+P0RjObx0DZ2c1hsLWzK5Vvm9z5tqU9ifKz5aw2Fz9tFD/dRPx0V/ELA2Kx QojfFOI31J5mVj0aqOtbDQhN1G/x1OPa1pOov3YA1iuXrg0A2jYA6C4BQFsH wPYOr4wAx1UVvnGeNAJo+whIF6arEWR6uFn72Qp3Wwl/2bvwWLlJs+VKSMXj b60HQZqXq8xoqqkYmqY/qeRpO8kvvd3o6fUGNld61rOdzLf0cOV6QhqfYrnH nybLy4USmwVesRRhSXsVLeplXrWy4UZKrzJQrG8Mt0erHq/VVKc8FKkNMh0v 5lHMZhiDd/c/nDhS5LrmKIZOnyavV7u8KNBKd7dxdaOZ9lKvc3GLpL6ZiytV TjWeVyjVlyrHk/bp0/eXr67+6wxrcDWvWLD6iwwb1TTcRLvDXbVbWLlApWLl HU3ddeUCw9BVhW+cpWpburBJREPSynWNZnbR4h+yjoFBdaFCY6nC9Gnr2WQx ny5iduArZKaQ6SE58BfTKYv5VUuCePIybXR4cOAfKuRgJjbTw8PSs/hph/LD +K1lvfDXZGNxsI2YRbttdZz1Rfq1sDaS3dONyvSrtcsNl+/OExmbQsbmUsZ/ 2hjUCVr6v8H36zpvEwjo1zYfb+DzyjjQDT4GurGsq7MpLjUk57jsE8eTy0lg wFjMvSjujhbX2ZS3SNuJPB7HrF7l8mgLmcuGW+o817kgdF4YrArdsMs+jxej 0arjpchNkycac7mS3xdycI0IU+c2OXZt9y1EnHQsqdjqUaNCxa0dWq1g0+IK tugyk5dW16iYYoorLD0rrMb6DL7HKh0hWVnc9feVtVx/L64gm47cck2V2QND ouoLpxzwq4KZvEedJiNZQBJ54OhIruUpJYAcluQ52X1pVuxTqgzlTEgF2tzF pm0v0+yf6qDfCwvq/qXcVa0vV2RId1kplC4FasJYnD6J42+r4ri9w0Ssy3Vf xRW5ZbrZQP7RJMWhkzkoTR+P42AxYtn6iG+990wsXtz154/5NEA18S9yGEZ5 7d+a7qWufB7U1MIq0nwKRAoxszXfv/9hytg/7i565JSf+zT5dOpxN/gf+An4 TzoL1JxU+UC0Lr8MF+c5Vc1TamM60Hu6SyZMLCl8+XFCvhenEw7o3pzd/9jr fP9b9/zd7cWr28+n3a74P79epPhN7zovSHUjcTS1cpf0IOJdcieBv01HU5z0 p7fXFy86meGTu9vzuxcdrHjaj0JexP8vTlfeWwhitCGJkf7g0RNfLiWfRuPx +0XuM5ZSzT4lC0OL/ied4sqxpX+BghT/hQl8bbZJB/l7dJZL++WumZOJTbbA KuHXb8+uXsCTXN6ykAwOirPmYeqX4xed7Bu1tJY77iIy6izICMhbyN2JauiL cMl3za0Ztb5nFpv53sXvPBILpMkEPSQVNmiJAm0KSunBxfPxwi9JqIWvO8wf jsmztK4v1TDaM/LyZYXNtuNQYz3JmltZX45UjXGZ+bayXRzLGvtZo/XnaDva DWehjb8J6WbFwmAWdN/zlNl9fP/ym/8H9A5a5XFqAAA= --0-1436409007-975538379=:4591-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 14:54: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-c.mdsn1.wi.home.com [24.183.3.139]) by hub.freebsd.org (Postfix) with ESMTP id 936D037B400 for ; Wed, 29 Nov 2000 14:54:06 -0800 (PST) Received: (qmail 57152 invoked by uid 1000); 29 Nov 2000 22:54:06 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 29 Nov 2000 22:54:06 -0000 Date: Wed, 29 Nov 2000 16:54:06 -0600 (CST) From: Mike Silbersack To: Dan Phoenix Cc: jl , freebsd-hackers@FreeBSD.ORG Subject: Re: APACHE PROBLEMS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Nov 2000, Mike Silbersack wrote: > Granted, your probably may be different, but it'd be a good start. ^^^^^^^^ er, problem Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 15: 6:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 3358537B401 for ; Wed, 29 Nov 2000 15:06:18 -0800 (PST) Received: (qmail 14235 invoked by uid 0); 29 Nov 2000 23:06:16 -0000 Received: from p3e9bc20f.dip.t-dialin.net (HELO forge.local) (62.155.194.15) by mail.gmx.net (mail04) with SMTP; 29 Nov 2000 23:06:16 -0000 Received: from thomas by forge.local with local (Exim 3.16 #1 (Debian)) id 141GHH-0000tI-00; Thu, 30 Nov 2000 00:04:39 +0100 Date: Thu, 30 Nov 2000 00:04:39 +0100 From: Thomas Moestl To: Boris Popov Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fix for panics in lookup() after forced unmount Message-ID: <20001130000439.A3370@crow.dom2ip.de> Mail-Followup-To: Thomas Moestl , Boris Popov , freebsd-hackers@freebsd.org References: <20001126190453.A1157@crow.dom2ip.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 bp@butya.kz on Mon, Nov 27, 2000 at 11:04:37AM +0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X On Mon, Nov 27, 2000 at 11:04:37AM +0600, Boris Popov wrote: > On Sun, 26 Nov 2000, Thomas Moestl wrote: > > > Actually, the panic will occur after a simple forced unmount of the current > > working directory and subsequent try to access "..". This is because the > > vnode of the cwd was cleared and it's v_mount member was set to NULL. This > > member is however dereferenced in the handling for the ".." special case in > > lookup(), causing a panic. > > [...] > > Good work Thomas! I think patch can be committed as is. Could someone please commit this? Or shall I rather file a PR? Thanks, - Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 15:11:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whizkidtech.net (rh3.bfm.org [216.127.220.196]) by hub.freebsd.org (Postfix) with ESMTP id 1779E37B400; Wed, 29 Nov 2000 15:11:53 -0800 (PST) Received: (from adam@localhost) by whizkidtech.net (8.9.2/8.9.2) id RAA00334; Wed, 29 Nov 2000 17:10:45 -0600 (CST) (envelope-from adam) Date: Wed, 29 Nov 2000 17:10:14 -0600 From: "G. Adam Stanislav" To: Nik Clayton Cc: hackers@FreeBSD.ORG Subject: Re: int80h.org Message-ID: <20001129171014.A318@whizkidtech.net> References: <20001126231649.A278@whizkidtech.net> <20001127151802.A7983@canyon.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20001127151802.A7983@canyon.nothing-going-on.org>; from nik@FreeBSD.ORG on Mon, Nov 27, 2000 at 03:18:02PM +0000 Organization: Whiz Kid Technomagic X-URL: http://www.whizkidtech.net/ X-Castle: http://www.redprince.net/ X-Special-Effects: http://www.FilmSFX.com/ X-Operating-System: FreeBSD whizkidtech.net 3.1-RELEASE FreeBSD 3.1-RELEASE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 27, 2000 at 03:18:02PM +0000, Nik Clayton wrote: >One thing though -- have you considered DocBook as the documentation >format? OK, here's my new reply: I have considered it very seriously, and I have rejected it. The reason is simple: I can't. jade runs out of swap space and memory even on a tiny little file. I have 8 Meg of RAM and successfully run Photoshop, CorelDraw and other huge programs. Yet, a simple file conversion program runs out of memory? Besides, it claims CHAPTER is not permitted in a book. Weird. Sorry, Adam -- Where two fight, third one wins -- Slovak proverb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 15:37:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.bfm.org (mail.bfm.org [216.127.218.26]) by hub.freebsd.org (Postfix) with ESMTP id F40AA37B400; Wed, 29 Nov 2000 15:37:16 -0800 (PST) Received: from WhizKid (r29.bfm.org [216.127.220.125]) by mail.bfm.org (Post.Office MTA v3.5.3 release 223 ID# 0-52399U2500L250S0V35) with SMTP id org; Wed, 29 Nov 2000 17:38:51 -0600 Message-Id: <3.0.6.32.20001129173556.009e76c0@mail85.pair.com> X-Sender: whizkid@mail85.pair.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 29 Nov 2000 17:35:56 -0600 To: "Daniel C. Sobral" From: "G. Adam Stanislav" Subject: Re: int80h.org Cc: Nik Clayton , hackers@FreeBSD.ORG In-Reply-To: <3A25745A.B8BC3AEE@newsguy.com> References: <20001126231649.A278@whizkidtech.net> <20001127151802.A7983@canyon.nothing-going-on.org> <20001129123119.A1594@whizkidtech.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 06:25 30-11-2000 +0900, Daniel C. Sobral wrote: >/me detects LISP influence and is strongly reminded of TeX. Hmmm... Never used either... It all started as C macros, then I got tired of having to write an entire C program for each web page, so I decided to write my own macro processor. As I started working on it, I kept adding and adding to it (it is at about 3,000 lines of assembly code right now), so it can run external programs, get and set environment variables, and such. Cheers, Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 15:38:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 88A9637B401 for ; Wed, 29 Nov 2000 15:38:56 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eATNckp02703; Wed, 29 Nov 2000 15:38:46 -0800 (PST) Date: Wed, 29 Nov 2000 15:38:45 -0800 From: Alfred Perlstein To: Thomas Moestl Cc: Boris Popov , freebsd-hackers@FreeBSD.ORG Subject: Re: [PATCH] Fix for panics in lookup() after forced unmount Message-ID: <20001129153845.R8051@fw.wintelcom.net> References: <20001126190453.A1157@crow.dom2ip.de> <20001130000439.A3370@crow.dom2ip.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001130000439.A3370@crow.dom2ip.de>; from tmoestl@gmx.net on Thu, Nov 30, 2000 at 12:04:39AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Thomas Moestl [001129 15:06] wrote: > X > On Mon, Nov 27, 2000 at 11:04:37AM +0600, Boris Popov wrote: > > On Sun, 26 Nov 2000, Thomas Moestl wrote: > > > > > Actually, the panic will occur after a simple forced unmount of the current > > > working directory and subsequent try to access "..". This is because the > > > vnode of the cwd was cleared and it's v_mount member was set to NULL. This > > > member is however dereferenced in the handling for the ".." special case in > > > lookup(), causing a panic. > > > [...] > > > > Good work Thomas! I think patch can be committed as is. > Could someone please commit this? Or shall I rather file a PR? Please assign a PR with the attached patch, I'll try to get to it. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 15:45:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with ESMTP id E3F2137B400 for ; Wed, 29 Nov 2000 15:45:27 -0800 (PST) Received: from localhost (dphoenix@localhost) by gandalf.bravenet.com (8.10.1/8.10.1) with ESMTP id eATNj9x09344; Wed, 29 Nov 2000 15:45:09 -0800 (PST) X-Authentication-Warning: gandalf.bravenet.com: dphoenix owned process doing -bs Date: Wed, 29 Nov 2000 15:45:09 -0800 (PST) From: Dan Phoenix To: Mike Silbersack Cc: jl , freebsd-hackers@FreeBSD.ORG Subject: Re: APACHE PROBLEMS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yes i tried that last week seemes to be abit better now. It has only happened once since my upgrade from 4.1 to 4.2 last week. On Wed, 29 Nov 2000, Mike Silbersack wrote: > Date: Wed, 29 Nov 2000 16:50:42 -0600 (CST) > From: Mike Silbersack > To: Dan Phoenix > Cc: jl , freebsd-hackers@FreeBSD.ORG > Subject: Re: APACHE PROBLEMS > > > On Wed, 29 Nov 2000, Dan Phoenix wrote: > > > > > we have no choice. > > I that case, have you tried cvsupping to the latest -stable? I know some > nfs-related fixed just got mfc'd. (Does anyone know if the ones discussed > last week were also committed and mfc'd?) > > Granted, your probably may be different, but it'd be a good start. > > Mike "Silby" Silbersack > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 18:43:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from linux.ssc.nsu.ru (linux.ssc.nsu.ru [193.124.219.91]) by hub.freebsd.org (Postfix) with SMTP id AA44537B401 for ; Wed, 29 Nov 2000 18:43:10 -0800 (PST) Received: (qmail 117 invoked from network); 30 Nov 2000 02:43:05 -0000 Received: from inet.ssc.nsu.ru (62.76.110.12) by hub.freebsd.org with SMTP; 30 Nov 2000 02:43:05 -0000 Received: from localhost (danfe@localhost) by inet.ssc.nsu.ru (8.9.3/8.9.3) with ESMTP id IAA01703; Thu, 30 Nov 2000 08:42:56 +0600 Date: Thu, 30 Nov 2000 08:42:56 +0600 (NOVT) From: Alexey Dokuchaev To: fs@freebsd.org Cc: hackers@freebsd.org Subject: Block vs. frag sizes in newfs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Sorry for x-posting: I've heard somewhere that not too many ppl actually read fs... AFAIR, there was a conversation going on concerning ${SUBJ}. I remember some thougths that -b = -f is sort of optimum, things like that... Or, why 8192/1024 are installation defaults?.. What it the truth behind all this? I'm intereted in any opinion. Thanks. -- DAN Fe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Nov 29 21:34:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id E1C7B37B400 for ; Wed, 29 Nov 2000 21:34:26 -0800 (PST) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.11.1/8.11.1) with ESMTP id eAU5YQm68396 for ; Wed, 29 Nov 2000 21:34:26 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from icarus.kfu.com (ssmail@localhost) by medusa.kfu.com (8.11.1/8.11.0) with ESMTP id eAU5YQY38157 for ; Wed, 29 Nov 2000 21:34:26 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com by icarus.kfu.com with ESMTP (8.11.1//ident-1.0) id eAU5YP900579; Wed, 29 Nov 2000 21:34:25 -0800 (PST) Message-ID: <3A25E6E1.24C006B9@quack.kfu.com> Date: Wed, 29 Nov 2000 21:34:25 -0800 From: Nick X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Nick's semi-periodic hardware support prize -- take 2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As many of you know, I offered a US$100 prize a while ago for a working driver for the ESS Solo-1 sound chip. I decided to offer the prize to Cameron Grant, but he declined, so the money will be donated to the FreeBSD Foundation in Cameron's name at the first appropriate opportunity. But now it is time for another one. Once again, the prize is US$100. The setting is my Sony Z505JE laptop, which has several functions available under Windows that do not work on FreeBSD. I suspect all of these devices are actually controlled the same way. Under Windows, there is a device driver for "Sony programmable I/O control" at 0x1080 and 0x1084, IRQ 11. I suspect that this device is how you can get at the jog wheel, the Fn+F3-5 buttons, and perhaps other things as well (I speculate perhaps the lid switch is in there). Just to keep it simple, though, I'll confine the prize to the first person who fully documents the interface to this device. I will be the final judge of the fullness of the documentation, but at the very least the winner should be able to show exactly how to generate select()able events in userland on jog dial rotation and clicking. Extra cool bonus points for turning the jog dial into a device controllable by moused (1 button, 1 Z axis, obviously), thus adding a mouse wheel and a middle mouse button to X with it. Let me also make it clear that any claimant is disqualified if he relies on any method of obtaining this information that violates any of Sony's intelectual property rights. If you've signed an NDA with them and participating will violate that NDA, please don't participate. Note also that you can't win by trying to give me the information under an NDA. The information provided by the winner must be openly publishable. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 0: 9:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (unknown [167.216.157.206]) by hub.freebsd.org (Postfix) with ESMTP id C8B2E37B400 for ; Thu, 30 Nov 2000 00:09:12 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAU8HFF00768; Thu, 30 Nov 2000 00:17:16 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011300817.eAU8HFF00768@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nick Cc: freebsd-hackers@freebsd.org Subject: Re: Nick's semi-periodic hardware support prize -- take 2 In-reply-to: Your message of "Wed, 29 Nov 2000 21:34:25 PST." <3A25E6E1.24C006B9@quack.kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Nov 2000 00:17:15 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But now it is time for another one. Once again, the prize is US$100. The > setting is my Sony Z505JE laptop, which has several functions available > under Windows that do not work on FreeBSD. I suspect all of these > devices are actually controlled the same way. Under Windows, there is a > device driver for "Sony programmable I/O control" at 0x1080 and 0x1084, > IRQ 11. I suspect that this device is how you can get at the jog wheel, > the Fn+F3-5 buttons, and perhaps other things as well (I speculate > perhaps the lid switch is in there). The lid switch will be either hung off the EC or the ACPI GPIO registers. Please make the output of "acpidump" available somewhere. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 1:15:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 4590637B404 for ; Thu, 30 Nov 2000 01:15:52 -0800 (PST) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id DAA08495 for freebsd-hackers@FreeBSD.ORG; Thu, 30 Nov 2000 03:15:51 -0600 (CST) Date: Thu, 30 Nov 2000 03:15:51 -0600 From: Tim Tsai To: freebsd-hackers@FreeBSD.ORG Subject: DSM Facility for FreeBSD Message-ID: <20001130031551.A8295@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://www.usenix.org/publications/library/proceedings/ana97/full_papers/souto/paper.html Does anybody know if something similar to this is available for modern FreeBSD/Unix? Preferably something in Userland vs. Kernel. Also, my requirements are significantly more relaxed than a true DSM model (and much more lightweight is preferred).. I really just need synchronized views of data on a "reasonable" effort basis (i.e. it's OK if one client/peer sees slightly older data. Sequence is important though). Hope that makes sense. Thanks, Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 5:28:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 7A0AE37B699 for ; Thu, 30 Nov 2000 05:28:20 -0800 (PST) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.20 #1) id 141Tkn-0004iu-00 for freebsd-hackers@freebsd.org; Thu, 30 Nov 2000 15:28:01 +0200 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 141Tkm-0003Pj-00 for freebsd-hackers@FreeBSD.ORG; Thu, 30 Nov 2000 15:28:00 +0200 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: freebsd-hackers@FreeBSD.ORG Subject: diskless/serial-console Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Nov 2000 15:28:00 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all, how can I set the equiv of -D/-h in /boot.config in a diskless-pxeboot machine? i think that {rootnfs-server}/boot.config is not read at all. tia, danny PS: 4.2-RELEASE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 5:53:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id DD15137B401 for ; Thu, 30 Nov 2000 05:53:08 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1000) id 6F1572B238; Thu, 30 Nov 2000 07:53:03 -0600 (CST) Date: Thu, 30 Nov 2000 05:53:03 -0800 From: Paul Saab To: Danny Braniss Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: diskless/serial-console Message-ID: <20001130055303.A70118@elvis.mu.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 danny@cs.huji.ac.il on Thu, Nov 30, 2000 at 03:28:00PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Danny Braniss (danny@cs.huji.ac.il) wrote: > hi all, > how can I set the equiv of -D/-h in /boot.config in a diskless-pxeboot > machine? i think that {rootnfs-server}/boot.config is not read at all. > > tia, > danny > PS: 4.2-RELEASE There's no way to really do it right now, but you can use: http://people.FreeBSD.org/~jhb/patches/pxekey.patch This will do the equivalent of -P for pxeboot. -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 5:55: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 0E26E37B401 for ; Thu, 30 Nov 2000 05:55:07 -0800 (PST) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id GAA2734981; Thu, 30 Nov 2000 06:55:06 -0700 (MST) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id GAA17870; Thu, 30 Nov 2000 06:55:06 -0700 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Thu, 30 Nov 2000 06:55:06 -0700 (MST) From: Ronald G Minnich X-Sender: rminnich@mini.acl.lanl.gov To: Tim Tsai Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: DSM Facility for FreeBSD In-Reply-To: <20001130031551.A8295@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Nov 2000, Tim Tsai wrote: > > Also, my requirements are significantly more relaxed than a true DSM model > (and much more lightweight is preferred).. I really just need synchronized > views of data on a "reasonable" effort basis (i.e. it's OK if one > client/peer sees slightly older data. Sequence is important though). check out http://www.acl.lanl.gov/~rminnich, see zounds. Worked well for me on clusters. The only DSM I've ever seen that supports IP multicast for updates. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 6:32:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.co.ru (mailhub.co.ru [194.85.128.15]) by hub.freebsd.org (Postfix) with ESMTP id 8B72A37B400 for ; Thu, 30 Nov 2000 06:32:33 -0800 (PST) Received: from andykv (n1-137.dialup.co.ru [195.16.37.137]) by mailhub.co.ru (8.11.0/8.11.0) with SMTP id eAUEWoE26264 for ; Thu, 30 Nov 2000 17:32:51 +0300 (MSK) From: "Andrey Kvitka" To: Subject: Drivers Date: Thu, 30 Nov 2000 17:32:06 +0300 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" 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.00.2314.1300 Disposition-Notification-To: "Andrey Kvitka" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear, Sirs! Where I can read about development of drivers for FreeBSD 4.x? Andrew. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 7:57:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id C967337B401 for ; Thu, 30 Nov 2000 07:57:45 -0800 (PST) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.20 #1) id 141W4w-0006by-00 for freebsd-hackers@freebsd.org; Thu, 30 Nov 2000 17:56:58 +0200 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 141W4v-0003X4-00 for freebsd-hackers@FreeBSD.ORG; Thu, 30 Nov 2000 17:56:57 +0200 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: freebsd-hackers@FreeBSD.ORG Subject: diskless/rc Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Nov 2000 17:56:57 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sorry if this is not the correct list. this code in rc: ... case ${update_motd} in [Nn][Oo] | '') ;; *) if T=`mktemp /tmp/_motd.XXXXXX`; then uname -v | sed -e 's,^\([^#]*\) #\(.* [1-2][0-9][0-9][0-9]\).*/\([^\]*\) $,\1 (\3) #\2,' > ${T} awk '{if (NR == 1) {if ($1 == "FreeBSD") {next} else {print "\n"$0}} else {print}}' < /etc/motd >> ${T} cmp -s ${T} /etc/motd || { cp ${T} /etc/motd chmod 644 /etc/motd } rm -f ${T} fi ;; esac used to 1) the cmp -s -> BUS ERROR 2) cp ${T} /etc/motd -> cp: /etc/motd: Bad address now only 2 is happening - go figure :-) it also used to, after it went multiuser, to panic when i did the cmp -s ${T} /etc/motd any insights? danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 8: 5: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 7C1D637B401 for ; Thu, 30 Nov 2000 08:05:06 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1000) id 0EF2E2B23F; Thu, 30 Nov 2000 10:05:01 -0600 (CST) Date: Thu, 30 Nov 2000 08:05:00 -0800 From: Paul Saab To: Danny Braniss Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: diskless/rc Message-ID: <20001130080500.A73135@elvis.mu.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 danny@cs.huji.ac.il on Thu, Nov 30, 2000 at 05:56:57PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG make sure the kernel you are booting is the same as the NFS file systems you are using. paul Danny Braniss (danny@cs.huji.ac.il) wrote: > sorry if this is not the correct list. > > this code in rc: > ... > > case ${update_motd} in > [Nn][Oo] | '') > ;; > *) > if T=`mktemp /tmp/_motd.XXXXXX`; then > uname -v | sed -e 's,^\([^#]*\) #\(.* [1-2][0-9][0-9][0-9]\).*/\([^\]*\) > $,\1 (\3) #\2,' > ${T} > awk '{if (NR == 1) {if ($1 == "FreeBSD") {next} else {print "\n"$0}} else > {print}}' < /etc/motd >> ${T} > cmp -s ${T} /etc/motd || { > cp ${T} /etc/motd > chmod 644 /etc/motd > } > rm -f ${T} > fi > ;; > esac > > used to > 1) the cmp -s -> BUS ERROR > 2) cp ${T} /etc/motd -> cp: /etc/motd: Bad address > > now only 2 is happening - go figure :-) > it also used to, after it went multiuser, to panic when i did the > cmp -s ${T} /etc/motd > > any insights? > > danny > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 8: 5:27 2000 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 8015037B400 for ; Thu, 30 Nov 2000 08:05:25 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 30 Nov 2000 16:05:24 +0000 (GMT) Date: Thu, 30 Nov 2000 16:05:24 +0000 From: David Malone To: Danny Braniss Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: diskless/rc Message-ID: <20001130160524.A8841@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 danny@cs.huji.ac.il on Thu, Nov 30, 2000 at 05:56:57PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 30, 2000 at 05:56:57PM +0200, Danny Braniss wrote: > 1) the cmp -s -> BUS ERROR > 2) cp ${T} /etc/motd -> cp: /etc/motd: Bad address > > now only 2 is happening - go figure :-) > it also used to, after it went multiuser, to panic when i did the > cmp -s ${T} /etc/motd > > any insights? Bad hardware? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 8:16:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id A4A0F37B400 for ; Thu, 30 Nov 2000 08:16:24 -0800 (PST) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.20 #1) id 141VPD-000673-00; Thu, 30 Nov 2000 17:13:51 +0200 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 141VPC-0003VD-00; Thu, 30 Nov 2000 17:13:50 +0200 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Paul Saab Subject: Re: diskless/serial-console Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of Thu, 30 Nov 2000 05:53:03 -0800 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Nov 2000 17:13:49 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG }There's no way to really do it right now, but you can use: }http://people.FreeBSD.org/~jhb/patches/pxekey.patch } }This will do the equivalent of -P for pxeboot. } thanks, i added the patches, make BOOT_PXELDR_PROBE_KEYBOARD=1 removed the keyboard, but zero. i even commented out the ifdef(`PROBE_KEYBOARD',` and the test for the keyboard, only left orb $RBX_SERIAL, (%bx) # enable serial console and still no output, btw, once the system is running, i can tip and it's ok. is the serial set to 9600? is there a way to tell whoever, to send kernel panics to serial? because that's all i want. Grrr, all this was to catch a panic that im getting, but now they stopped. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 8:54:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.rila.bg (earth.rila.bg [212.39.75.31]) by hub.freebsd.org (Postfix) with ESMTP id 58FC337B400 for ; Thu, 30 Nov 2000 08:54:33 -0800 (PST) Received: from earth (localhost [127.0.0.1]) by earth.rila.bg (8.11.1/8.11.1) with ESMTP id eAUGsQ517235 for ; Thu, 30 Nov 2000 18:54:27 +0200 (EET) (envelope-from mitko@earth.rila.bg) Message-Id: <200011301654.eAUGsQ517235@earth.rila.bg> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Reply-To: mitko@rila.bg From: "Dimitar V. Peikov" Subject: pthreads, semaphores and wait Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_14473280120" Date: Thu, 30 Nov 2000 18:54:26 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_14473280120 Content-Type: text/plain; charset=us-ascii I've tryed to make some example on using pthreads and semaphores and found that process became blocked if inside of critical section use wait, uwait or nanowait finctions. In the attached file if change line : (#if 0) to (#if 1) the program hangs. I've tested it even with gdb and the threads were blocked after wait finction. --==_Exmh_14473280120 Content-Type: text/plain ; name="broken_wait.c"; charset=us-ascii Content-Description: broken_wait.c Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="broken_wait.c" I2luY2x1ZGUgPHVuaXN0ZC5oPgojaW5jbHVkZSA8c3RkaW8uaD4KI2luY2x1ZGUgPHN0ZGxp Yi5oPgojaW5jbHVkZSA8c3RyaW5nLmg+CgovKiAgcFRocmVhZCBpbmNsdWRlcyAqLwojaW5j bHVkZSA8cHRocmVhZC5oPgoKLyogIElQQyBzZW1hcGhvcmVzIGluY2x1ZGVzICovCiNpbmNs dWRlIDxzeXMvdHlwZXMuaD4KI2luY2x1ZGUgPHN5cy9pcGMuaD4KI2luY2x1ZGUgPHN5cy9z ZW0uaD4KCmV4dGVybiBpbnQgZXJybm87CmludCBjb21tb24gPSAwOwppbnQgY29tbW9uX3No YXJlZF9pZCA9IDA7CmNoYXIgKmNvbW1vbl9wb2ludGVyID0gTlVMTDsKaW50IHNlbWFwaG9y ZV9pZCA9IDA7CgppbnQgcHRocmVhZF9zZW1hcGhvcmVzKGNoYXIgKnMpIHsKICBpbnQgaW50 ZXJuYWwgPSBjb21tb247CiAgc3RydWN0IHNlbWJ1ZiBzZW1fYnVmOwogIGludCBzZW1fdmFs ID0gMDsKCi8qICBMb2NrIHNlbWFwaG9yZSAwICovCiAgc2VtX2J1Zi5zZW1fbnVtID0gMDsK ICBzZW1fYnVmLnNlbV9vcCA9IC0xOwogIHNlbV9idWYuc2VtX2ZsZyA9IDA7CiAgaWYgKChz ZW1fdmFsID0gc2Vtb3Aoc2VtYXBob3JlX2lkLCAmc2VtX2J1ZiwgMSkpID09IC0xKSB7CiAg ICBmcHJpbnRmKHN0ZGVyciwgIkVycm9yIGxvY2sgc2VtYXBob3JlOiAlc1xuIiwgc3RyZXJy b3IoZXJybm8pKTsKICAgIHJldHVybiAtMTsKICB9CgovKiAgR2V0IGN1cnJlbnQgdmFsdWUg b2YgdGhlIGZpcnN0IHNlbWFwaG9yZSAqLwogIGlmICgoc2VtX3ZhbCA9IHNlbWN0bChzZW1h cGhvcmVfaWQsIDAsIEdFVFZBTCkpID09IC0xKSB7CiAgICBmcHJpbnRmKHN0ZGVyciwgIkVy cm9yIGFsbG9jYXRpbmcgc2VtYXBob3JlOiAlc1xuIiwgc3RyZXJyb3IoZXJybm8pKTsKICAg IHJldHVybiAtMTsKICB9CgovKiAgRG8gc29tZXRoaW5nIC4uLiAqLwogIGNvbW1vbl9wb2lu dGVyID0gKGNoYXIgKikgbWFsbG9jKHN0cmxlbihzKSArIDEpOwogIHN0cmNweShjb21tb25f cG9pbnRlciwgcyk7CiAgZnByaW50ZihzdGRlcnIsICJFbnRlciBzZW1hcGhvcmUgJXVcbiIs IGNvbW1vbisrKTsKCiNpZiAwCiAgICBzbGVlcCgxKTsKI2VuZGlmCgogIGZwcmludGYoc3Rk ZXJyLCAiTGVhdmUgc2VtYXBob3JlICV1XG4iLCBpbnRlcm5hbCk7CgogIHNlbV9idWYuc2Vt X251bSA9IDA7CiAgc2VtX2J1Zi5zZW1fb3AgPSAxOwogIHNlbV9idWYuc2VtX2ZsZyA9IDA7 CiAgaWYgKChzZW1fdmFsID0gc2Vtb3Aoc2VtYXBob3JlX2lkLCAmc2VtX2J1ZiwgMSkpID09 IC0xKSB7CiAgICBmcHJpbnRmKHN0ZGVyciwgIkVycm9yIGxvY2sgc2VtYXBob3JlOiAlc1xu Iiwgc3RyZXJyb3IoZXJybm8pKTsKICAgIHJldHVybiAtMTsKICB9CiAgcmV0dXJuIDA7Cn0K CmludCBtYWluKGludCBhcmdjLCBjaGFyICoqYXJndikgewogIHB0aHJlYWRfdCB0aHJbNF07 CiAgaW50IHJldGNvZGUgPSAwOwogIGludCBzZW1fdmFsOwoKLyogIEV4YW1wbGUgdXNpbmcg c2VtYXBob3JlcyAqLwovKiAgQ3JlYXRlIHNlbWFwaG9yZSAqLwogIGlmICgoc2VtYXBob3Jl X2lkID0gc2VtZ2V0KElQQ19QUklWQVRFLCAxLCBTRU1fUiB8IFNFTV9BKSkgPT0gLTEpIHsK ICAgIGZwcmludGYoc3RkZXJyLCAiRXJyb3IgYWxsb2NhdGluZyBzZW1hcGhvcmU6ICVzXG4i LCBzdHJlcnJvcihlcnJubykpOwogICAgcmV0dXJuIC0xOwogIH0KCi8qICBBc3NpZ24gdmFs dWUgdG8gdGhlIGZpcnN0IHNlbWFwaG9yZSAqLwogIGlmICgoc2VtX3ZhbCA9IHNlbWN0bChz ZW1hcGhvcmVfaWQsIDAsIFNFVFZBTCwgMSkpID09IC0xKSB7CiAgICBmcHJpbnRmKHN0ZGVy ciwgIkVycm9yIGFsbG9jYXRpbmcgc2VtYXBob3JlOiAlc1xuIiwgc3RyZXJyb3IoZXJybm8p KTsKICAgIHJldHVybiAtMTsKICB9CgovKiAgR2V0IGN1cnJlbnQgdmFsdWUgb2YgdGhlIGZp cnN0IHNlbWFwaG9yZSAqLwogIGlmICgoc2VtX3ZhbCA9IHNlbWN0bChzZW1hcGhvcmVfaWQs IDAsIEdFVFZBTCkpID09IC0xKSB7CiAgICBmcHJpbnRmKHN0ZGVyciwgIkVycm9yIGFsbG9j YXRpbmcgc2VtYXBob3JlOiAlc1xuIiwgc3RyZXJyb3IoZXJybm8pKTsKICAgIHJldHVybiAt MTsKICB9CgovKiAgQ3JlYXRlIHB0aHJlYWRzICovCiAgcHRocmVhZF9jcmVhdGUoJnRoclsw XSwgTlVMTCwgKHZvaWQgKigqKSh2b2lkICopKXB0aHJlYWRfc2VtYXBob3JlcywgYXJndlsw XSk7CiAgcHRocmVhZF9jcmVhdGUoJnRoclsxXSwgTlVMTCwgKHZvaWQgKigqKSh2b2lkICop KXB0aHJlYWRfc2VtYXBob3JlcywgYXJndlswXSk7CiAgcHRocmVhZF9qb2luKHRoclswXSwg KHZvaWQgKikgJnJldGNvZGUpOwoKLyogIFJlbW92ZSBzZW1hcGhvcmUgKi8KICBpZiAoc2Vt Y3RsKHNlbWFwaG9yZV9pZCwgSVBDX1JNSUQsIE5VTEwpID09IC0xKSB7CiAgICBmcHJpbnRm KHN0ZGVyciwgIkVycm9yIHJlbW92aW5nIHNlbWFwaG9yZTogJXNcbiIsIHN0cmVycm9yKGVy cm5vKSk7CiAgICByZXR1cm4gLTE7CiAgfQoKICBmcHJpbnRmKHN0ZGVyciwgIkRvbmUhXG4i KTsKICByZXR1cm4gMDsKfQo= --==_Exmh_14473280120 Content-Type: text/plain; charset=us-ascii Dimitar Peikov Programmer Analyst "We Build e-Business" RILA Solutions 27 Building, Acad.G.Bonchev Str. 1113 Sofia, Bulgaria home: (+359 2) 595495 phone: (+359 2) 9797320 phone: (+359 2) 9797300 fax: (+359 2) 9733355 http://www.rila.com --==_Exmh_14473280120-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 8:56:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 91B9737B400 for ; Thu, 30 Nov 2000 08:56:24 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1000) id 4D46C2B23F; Thu, 30 Nov 2000 10:56:24 -0600 (CST) Date: Thu, 30 Nov 2000 08:56:24 -0800 From: Paul Saab To: Danny Braniss Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: diskless/serial-console Message-ID: <20001130085624.A74146@elvis.mu.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 danny@cs.huji.ac.il on Thu, Nov 30, 2000 at 05:13:49PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Danny Braniss (danny@cs.huji.ac.il) wrote: > > }There's no way to really do it right now, but you can use: > }http://people.FreeBSD.org/~jhb/patches/pxekey.patch > } > }This will do the equivalent of -P for pxeboot. > } > thanks, > i added the patches, make BOOT_PXELDR_PROBE_KEYBOARD=1 > removed the keyboard, but zero. > i even commented out the ifdef(`PROBE_KEYBOARD',` > and the test for the keyboard, only left > orb $RBX_SERIAL, (%bx) # enable serial console > and still no output, btw, once the system is running, i can tip and it's ok. > is the serial set to 9600? > > is there a way to tell whoever, to send kernel panics to serial? because that's > all i want. Is a keyboard plugged into the machine? If you want to force serial output, set console="comconsole" in your loader.conf. > Grrr, all this was to catch a panic that im getting, but now they stopped. DDB and BREAK_TO_DEBUGGER or ALT_BREAK_TO_DEBUGGER To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 10: 4:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 1849537B402 for ; Thu, 30 Nov 2000 10:04:30 -0800 (PST) Received: from vigrid.com (pm3-pt7.pcnet.net [206.105.29.81]) by pcnet1.pcnet.com (8.8.7/PCNet) with ESMTP id NAA07452; Thu, 30 Nov 2000 13:04:02 -0500 (EST) Message-ID: <3A2696C4.2471B6D4@vigrid.com> Date: Thu, 30 Nov 2000 13:04:52 -0500 From: "Daniel M. Eischen" X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: mitko@rila.bg Cc: hackers@FreeBSD.ORG Subject: Re: pthreads, semaphores and wait References: <200011301654.eAUGsQ517235@earth.rila.bg> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Dimitar V. Peikov" wrote: > > I've tryed to make some example on using pthreads and semaphores and found > that process became blocked if inside of critical section use wait, uwait or > nanowait finctions. In the attached file if change line : (#if 0) to (#if 1) > the program hangs. I've tested it even with gdb and the threads were blocked > after wait finction. Semaphores aren't wrapped by the threads library (yes, they can block the whole process). This will be resolved in our future libpthread (for info on that, search -arch and -smp in reference to the KSE project). -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 10:12:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id BF0A437B404; Thu, 30 Nov 2000 10:12:55 -0800 (PST) Received: from mail2.rim.or.jp by serio.al.rim.or.jp (3.7W/HMX-13) id DAA26551; Fri, 1 Dec 2000 03:12:54 +0900 (JST) Received: from localhost.FromTo.Cc (shell [202.247.191.98]) by mail2.rim.or.jp (8.9.3/3.7W) id DAA12566; Fri, 1 Dec 2000 03:12:53 +0900 (JST) Date: Fri, 01 Dec 2000 03:12:50 +0900 Message-ID: <86r93tjplp.wl@ringo.FromTo.Cc> From: Tatsumi Hosokawa To: hosokawa@FreeBSD.org Cc: freebsd-hackers@FreeBSD.org, zhecka@klondike.ru Subject: Re: i18n extention in sysinstall In-Reply-To: In your message of "Tue, 28 Nov 2000 18:07:05 +0900" <86wvdompmu.wl@ringo.FromTo.Cc> References: <200011280801.LAA21447@ns.klondike.ru> <86wvdompmu.wl@ringo.FromTo.Cc> User-Agent: Wanderlust/1.1.0 (Overjoyed) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Tue, 28 Nov 2000 18:07:05 +0900, Tatsumi Hosokawa wrote: > >At Tue, 28 Nov 2000 11:01:07 +0000, >Kaltashkin Eugene wrote: >> >> What dear developers will tell about introduction i18n expansions in sysinstall the utility? >> It would be convenient for many people to adjust FreeBSD on the native language. > > Latest code is based on 4.2-RELEASE and I'm porting porting it to > -current (maybe it's easy). I wrote Russian support for it. Currently only *.hlp files are provided, so, selecting "Usage" or type F1 from main menu is the easiest way to see russian sysinstall message. Latest binaries and sources can be found at http://people.freebsd.org/~hosokawa/boot-ja/4.2-RELEASE/release-20001201-1/ and it currently support Japanese, Korean, Traditional Chinese, Russian, and English. -- Tatsumi Hosokawa http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 10:30:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id A4D0F37B400 for ; Thu, 30 Nov 2000 10:29:16 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eAUIT4C65148; Thu, 30 Nov 2000 10:29:04 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001130055303.A70118@elvis.mu.org> Date: Thu, 30 Nov 2000 10:29:25 -0800 (PST) From: John Baldwin To: Paul Saab Subject: Re: diskless/serial-console Cc: freebsd-hackers@FreeBSD.org, Danny Braniss Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Nov-00 Paul Saab wrote: > Danny Braniss (danny@cs.huji.ac.il) wrote: >> hi all, >> how can I set the equiv of -D/-h in /boot.config in a diskless-pxeboot >> machine? i think that {rootnfs-server}/boot.config is not read at all. >> >> tia, >> danny >> PS: 4.2-RELEASE > > There's no way to really do it right now, but you can use: > http://people.FreeBSD.org/~jhb/patches/pxekey.patch > > This will do the equivalent of -P for pxeboot. Let me know if it works. Note that you need to compile pxeldr with an extra option to make (-DBOOT_PXELDR_PROBE_KEYBOARD). If it does work I'll commit it. :) -- 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 Nov 30 10:30:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 6175737B6BB for ; Thu, 30 Nov 2000 10:29:52 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eAUIT6C65156; Thu, 30 Nov 2000 10:29:06 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 30 Nov 2000 10:29:26 -0800 (PST) From: John Baldwin To: Danny Braniss Subject: Re: diskless/serial-console Cc: freebsd-hackers@FreeBSD.org, Paul Saab Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Nov-00 Danny Braniss wrote: > > }There's no way to really do it right now, but you can use: > }http://people.FreeBSD.org/~jhb/patches/pxekey.patch > } > }This will do the equivalent of -P for pxeboot. > } > thanks, > i added the patches, make BOOT_PXELDR_PROBE_KEYBOARD=1 > removed the keyboard, but zero. > i even commented out the ifdef(`PROBE_KEYBOARD',` > and the test for the keyboard, only left > orb $RBX_SERIAL, (%bx) # enable serial console > and still no output, btw, once the system is running, i can tip and it's ok. > is the serial set to 9600? > > is there a way to tell whoever, to send kernel panics to serial? because > that's > all i want. > > Grrr, all this was to catch a panic that im getting, but now they stopped. > > danny Grr, I found my bug. Please download the updated pxekey.patch and try again. I was setting hte wrong value.. *sigh* -- 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 Nov 30 10:30:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 03CB937B6A8 for ; Thu, 30 Nov 2000 10:29:52 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eAUIT5C65152; Thu, 30 Nov 2000 10:29:05 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 30 Nov 2000 10:29:26 -0800 (PST) From: John Baldwin To: Danny Braniss Subject: Re: diskless/serial-console Cc: freebsd-hackers@FreeBSD.org, Paul Saab Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Nov-00 Danny Braniss wrote: > > }There's no way to really do it right now, but you can use: > }http://people.FreeBSD.org/~jhb/patches/pxekey.patch > } > }This will do the equivalent of -P for pxeboot. > } > thanks, > i added the patches, make BOOT_PXELDR_PROBE_KEYBOARD=1 > removed the keyboard, but zero. > i even commented out the ifdef(`PROBE_KEYBOARD',` > and the test for the keyboard, only left > orb $RBX_SERIAL, (%bx) # enable serial console > and still no output, btw, once the system is running, i can tip and it's ok. > is the serial set to 9600? Hmm, yes, the serial is the normal serial that the loader uses. Looks like I've fubar'd something or other in my pxeldr patch though. > is there a way to tell whoever, to send kernel panics to serial? because > that's > all i want. panic's occur on the console device, so serial console is hte way to go. :) > Grrr, all this was to catch a panic that im getting, but now they stopped. > > danny -- 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 Nov 30 11: 0:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orthanc.ab.ca (207-167-15-66.dsl.worldgate.ca [207.167.15.66]) by hub.freebsd.org (Postfix) with ESMTP id 88AA937B400 for ; Thu, 30 Nov 2000 11:00:54 -0800 (PST) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.11.1/8.11.0.Beta3) with ESMTP id eAUJ0lI25275 for ; Thu, 30 Nov 2000 12:00:52 -0700 (MST) Message-Id: <200011301900.eAUJ0lI25275@orthanc.ab.ca> To: hackers@freebsd.org Subject: Cirrus PD6729/6730 data sheets? Organization: The Frobozz Magic Homing Pigeon Company Date: Thu, 30 Nov 2000 12:00:47 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone out there have a set of data sheets for the above chips that they could email me? It looks like all the info pertaining to these has been pulled from the Cirrus web site (?!?). Thanks, --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 12: 9:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lily.ezo.net (lily.ezo.net [206.102.130.13]) by hub.freebsd.org (Postfix) with ESMTP id D125237B401; Thu, 30 Nov 2000 12:09:24 -0800 (PST) Received: from lily.ezo.net (jflowers@localhost.ezo.net [127.0.0.1]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id PAA02961; Thu, 30 Nov 2000 15:17:14 -0500 (EST) Date: Thu, 30 Nov 2000 15:17:12 -0500 (EST) From: Jim Flowers To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Cc: cpenner@streamflo.com, Archie Cobbs Subject: Re: SKIP port on 4.x (prize offer) In-Reply-To: <200011301942.eAUJgcK92874@curve.dellroad.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What about it? Anyone with skills in this area interested in figuring out what changed between 4.1 and 4.1.1 probably in the crypto changes that prevents the MD5 authentication of a skip partner. Worth a quick $150 prize for the first solution. Jim Flowers #4 ISP on C|NET, #1 in Ohio On Thu, 30 Nov 2000, Archie Cobbs wrote: > Jim Flowers writes: > > If we provide the funding for a few hours of effort, do you know anyone > > who could take a look at this sooner rather than later? The field of > > view has been narrowed down pretty much and may be no more complicated > > than which of the multiple md5.h header files is being used. > > Somebody on freebsd-net@freebsd.org may be interested in taking a look, > especially if there is a small reward.. I'd ask there. > > -Archie > > PS. isn't there also some web site where you can post projects? > > __________________________________________________________________________ > Archie Cobbs * Packet Design * http://www.packetdesign.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 13:21:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with ESMTP id 54A1737B401 for ; Thu, 30 Nov 2000 13:21:18 -0800 (PST) Received: from localhost (dphoenix@localhost) by gandalf.bravenet.com (8.10.1/8.10.1) with ESMTP id eAULL6P15762 for ; Thu, 30 Nov 2000 13:21:10 -0800 (PST) X-Authentication-Warning: gandalf.bravenet.com: dphoenix owned process doing -bs Date: Thu, 30 Nov 2000 13:21:05 -0800 (PST) From: Dan Phoenix To: freebsd-hackers@freebsd.org Subject: Re: APACHE PROBLEMS (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nov 30 02:00:21 merry /kernel: nfs send error 32 for server nfs:/lopt Nov 30 02:00:21 merry /kernel: nfs send error 32 for server nfs:/lopt Nov 30 05:37:24 merry /kernel: nfs server nfs:/cache: not responding Nov 30 05:37:24 merry /kernel: nfs server nfs:/cache: is alive again Nov 30 07:54:56 merry /kernel: nfs server nfs:/cache: not responding Nov 30 07:54:57 merry /kernel: nfs server nfs:/cache: is alive again Nov 30 08:05:53 merry /kernel: nfs send error 32 for server nfs:/lopt Nov 30 08:05:53 merry /kernel: nfs send error 32 for server nfs:/lopt Ok i will do that....here is problems i am experiencing . On Wed, 29 Nov 2000, Mike Silbersack wrote: > Date: Wed, 29 Nov 2000 20:05:18 -0600 (CST) > From: Mike Silbersack > To: Dan Phoenix > Subject: Re: APACHE PROBLEMS > > > On Wed, 29 Nov 2000, Dan Phoenix wrote: > > > before the 25th. > > where can i get a list of changes? > > Here's what changed between the 18th and 25th: > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=987735+0+archive/2000/cvs-all/20001126.cvs-all > > The more seemingly relevant changes were committed on the 18th, but it's > probably wise to update to a post-25th version, as Matt's bugfixes usually > are well-implemented. Perhaps he inadvertantly fixed the problem you're > experiencing. While you're not experiencing a low-memory situation, > what's happening is probably some form of deadlock. > > What you should do is look over the freebsd-hackers and freebsd-net > archives for the last few weeks. Someone was experiencing nfs problems > with apache as well. He found a fix for one bug, but I'm not sure if it > was committed or not. Contacting him and seeing if you're experiencing > the same problem would probably help you solve your problem. And if > you're able to get good debugging info on what's happening (don't ask me > how, I don't know either), you may wish to contact Matt directly, as this > type of problem is right up his alley. > > And yes, his name is Matt Dillon, but he's not the actor. :) > > Mike "Silby" Silbersack > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 13:33: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from milquetoast.cs.mcgill.ca (milquetoast.CS.McGill.CA [132.206.2.5]) by hub.freebsd.org (Postfix) with ESMTP id 1E3C037B400 for ; Thu, 30 Nov 2000 13:33:03 -0800 (PST) Received: (from mat@localhost) by milquetoast.cs.mcgill.ca (8.9.3/8.9.3) id QAA18444; Thu, 30 Nov 2000 16:33:01 -0500 (EST) Date: Thu, 30 Nov 2000 16:33:01 -0500 From: Mathew KANNER To: Dan Phoenix Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: APACHE PROBLEMS (fwd) Message-ID: <20001130163301.N13101@cs.mcgill.ca> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: Dan Phoenix's message [Re: APACHE PROBLEMS (fwd)] as of Thu, Nov 30, 2000 at 01:21:05PM -0800 Organization: SOCS, McGill University, Montreal, CANADA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Nov 30, Dan Phoenix wrote: > > > Nov 30 02:00:21 merry /kernel: nfs send error 32 for server nfs:/lopt > Nov 30 02:00:21 merry /kernel: nfs send error 32 for server nfs:/lopt > Nov 30 05:37:24 merry /kernel: nfs server nfs:/cache: not responding > Nov 30 05:37:24 merry /kernel: nfs server nfs:/cache: is alive again > Nov 30 07:54:56 merry /kernel: nfs server nfs:/cache: not responding > Nov 30 07:54:57 merry /kernel: nfs server nfs:/cache: is alive again > Nov 30 08:05:53 merry /kernel: nfs send error 32 for server nfs:/lopt > Nov 30 08:05:53 merry /kernel: nfs send error 32 for server nfs:/lopt We've seen this problem at McGill. It doesn't seem to affect our usage at all. Also note that these problems don't appear with nfsv2. (It appears it 4.[0-2] and with Solaris servers) If you do find a solution, my friend andrewb@cs.mcgill.ca would love to hear about it. --Mat > > > > Ok i will do that....here is problems i am experiencing . > > > > On Wed, 29 Nov 2000, Mike Silbersack wrote: > > > Date: Wed, 29 Nov 2000 20:05:18 -0600 (CST) > > From: Mike Silbersack > > To: Dan Phoenix > > Subject: Re: APACHE PROBLEMS > > > > > > On Wed, 29 Nov 2000, Dan Phoenix wrote: > > > > > before the 25th. > > > where can i get a list of changes? > > > > Here's what changed between the 18th and 25th: > > > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=987735+0+archive/2000/cvs-all/20001126.cvs-all > > > > The more seemingly relevant changes were committed on the 18th, but it's > > probably wise to update to a post-25th version, as Matt's bugfixes usually > > are well-implemented. Perhaps he inadvertantly fixed the problem you're > > experiencing. While you're not experiencing a low-memory situation, > > what's happening is probably some form of deadlock. > > > > What you should do is look over the freebsd-hackers and freebsd-net > > archives for the last few weeks. Someone was experiencing nfs problems > > with apache as well. He found a fix for one bug, but I'm not sure if it > > was committed or not. Contacting him and seeing if you're experiencing > > the same problem would probably help you solve your problem. And if > > you're able to get good debugging info on what's happening (don't ask me > > how, I don't know either), you may wish to contact Matt directly, as this > > type of problem is right up his alley. > > > > And yes, his name is Matt Dillon, but he's not the actor. :) > > > > Mike "Silby" Silbersack > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Mathew Kanner SOCS McGill University Obtuse quote: He [not me] understands: "This field of perception is void of perception of man." -- The Quintessence of Buddhism To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 14: 5:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with ESMTP id 654A137B401 for ; Thu, 30 Nov 2000 14:05:26 -0800 (PST) Received: from localhost (dphoenix@localhost) by gandalf.bravenet.com (8.10.1/8.10.1) with ESMTP id eAUM5G303759; Thu, 30 Nov 2000 14:05:17 -0800 (PST) X-Authentication-Warning: gandalf.bravenet.com: dphoenix owned process doing -bs Date: Thu, 30 Nov 2000 14:05:16 -0800 (PST) From: Dan Phoenix To: Mathew KANNER Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: APACHE PROBLEMS (fwd) In-Reply-To: <20001130163301.N13101@cs.mcgill.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nfs:/lopt /opt nfs -2,-T,-i,rw 0 0 nfs:/cache /cache nfs -2,-T,-i,rw 0 0 those are my mount options from /etc/fstab. as you can see i have it forced on version 2 with tcp and allow interuption in read-write mode. -i does not seem to work with solaris... tcp instead of udp did not seem to help.....and version 2 vs 3 does not seem to make a difference. There is a lock happening somewhere and it has to be solved.....I am doing a make world right now hoping the new nfs code will help but all I am doing is crossing my fingers. Only the freebsd machines have problems like this. I am already at 4.2 with latest src from about a week ago!!! On Thu, 30 Nov 2000, Mathew KANNER wrote: > Date: Thu, 30 Nov 2000 16:33:01 -0500 > From: Mathew KANNER > To: Dan Phoenix > Cc: freebsd-hackers@FreeBSD.ORG > Subject: Re: APACHE PROBLEMS (fwd) > > On Nov 30, Dan Phoenix wrote: > > > > > > Nov 30 02:00:21 merry /kernel: nfs send error 32 for server nfs:/lopt > > Nov 30 02:00:21 merry /kernel: nfs send error 32 for server nfs:/lopt > > Nov 30 05:37:24 merry /kernel: nfs server nfs:/cache: not responding > > Nov 30 05:37:24 merry /kernel: nfs server nfs:/cache: is alive again > > Nov 30 07:54:56 merry /kernel: nfs server nfs:/cache: not responding > > Nov 30 07:54:57 merry /kernel: nfs server nfs:/cache: is alive again > > Nov 30 08:05:53 merry /kernel: nfs send error 32 for server nfs:/lopt > > Nov 30 08:05:53 merry /kernel: nfs send error 32 for server nfs:/lopt > > We've seen this problem at McGill. It doesn't seem to affect > our usage at all. Also note that these problems don't appear with > nfsv2. (It appears it 4.[0-2] and with Solaris servers) > > If you do find a solution, my friend andrewb@cs.mcgill.ca > would love to hear about it. > > --Mat > > > > > > > > Ok i will do that....here is problems i am experiencing . > > > > > > > > On Wed, 29 Nov 2000, Mike Silbersack wrote: > > > > > Date: Wed, 29 Nov 2000 20:05:18 -0600 (CST) > > > From: Mike Silbersack > > > To: Dan Phoenix > > > Subject: Re: APACHE PROBLEMS > > > > > > > > > On Wed, 29 Nov 2000, Dan Phoenix wrote: > > > > > > > before the 25th. > > > > where can i get a list of changes? > > > > > > Here's what changed between the 18th and 25th: > > > > > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=987735+0+archive/2000/cvs-all/20001126.cvs-all > > > > > > The more seemingly relevant changes were committed on the 18th, but it's > > > probably wise to update to a post-25th version, as Matt's bugfixes usually > > > are well-implemented. Perhaps he inadvertantly fixed the problem you're > > > experiencing. While you're not experiencing a low-memory situation, > > > what's happening is probably some form of deadlock. > > > > > > What you should do is look over the freebsd-hackers and freebsd-net > > > archives for the last few weeks. Someone was experiencing nfs problems > > > with apache as well. He found a fix for one bug, but I'm not sure if it > > > was committed or not. Contacting him and seeing if you're experiencing > > > the same problem would probably help you solve your problem. And if > > > you're able to get good debugging info on what's happening (don't ask me > > > how, I don't know either), you may wish to contact Matt directly, as this > > > type of problem is right up his alley. > > > > > > And yes, his name is Matt Dillon, but he's not the actor. :) > > > > > > Mike "Silby" Silbersack > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > -- > Mathew Kanner SOCS McGill University > Obtuse quote: He [not me] understands: "This field of perception > is void of perception of man." -- The Quintessence of Buddhism > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 14: 9:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 713E137B401 for ; Thu, 30 Nov 2000 14:09:20 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1098) id 0DBA12B28D; Thu, 30 Nov 2000 16:09:20 -0600 (CST) Date: Thu, 30 Nov 2000 16:09:19 -0600 From: Bill Fumerola To: Dan Phoenix Cc: Mathew KANNER , freebsd-hackers@FreeBSD.ORG Subject: Re: APACHE PROBLEMS (fwd) Message-ID: <20001130160919.C83422@elvis.mu.org> References: <20001130163301.N13101@cs.mcgill.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dphoenix@bravenet.com on Thu, Nov 30, 2000 at 02:05:16PM -0800 X-Operating-System: FreeBSD 4.2-FEARSOME-20001103 i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 30, 2000 at 02:05:16PM -0800, Dan Phoenix wrote: > > nfs:/lopt /opt nfs -2,-T,-i,rw 0 > 0 > nfs:/cache /cache nfs -2,-T,-i,rw 0 > 0 > > those are my mount options from /etc/fstab. > as you can see i have it forced on version 2 with tcp and allow > interuption in read-write mode. -i does not seem to work with solaris... > tcp instead of udp did not seem to help.....and version 2 vs 3 does not > seem to make a difference. There is a lock happening somewhere and it has > to be solved.....I am doing a make world right now hoping the new nfs code > will help but all I am doing is crossing my fingers. Only the freebsd > machines have problems like this. I am already at 4.2 with latest src from > about a week ago!!! try -s as well. you're more likely not to die (and rather just fail) with bad NFS going on. this entire thread was probably more appropriately located on questions@freebsd.org -- Bill Fumerola - security yahoo / Yahoo! inc. - fumerola@yahoo-inc.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 14:30:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from guardian.sftw.com (guardian.sftw.com [209.157.37.25]) by hub.freebsd.org (Postfix) with ESMTP id 4B83A37B400 for ; Thu, 30 Nov 2000 14:30:38 -0800 (PST) Received: from yoda.sftw.com (yoda.sftw.com [209.157.37.211]) by guardian.sftw.com (8.11.0/8.11.0) with ESMTP id eAUMUaq32050 for ; Thu, 30 Nov 2000 14:30:36 -0800 (PST) (envelope-from nsayer@sftw.com) Received: from sftw.com (localhost [127.0.0.1]) by yoda.sftw.com (8.11.1/8.11.1) with ESMTP id eAUMUas46184 for ; Thu, 30 Nov 2000 14:30:36 -0800 (PST) (envelope-from nsayer@sftw.com) Message-ID: <3A26D50B.380E960C@sftw.com> Date: Thu, 30 Nov 2000 14:30:35 -0800 From: Nick Sayer Reply-To: nsayer@kfu.com X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Sony vaio jog dial hacks Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I've gotten pointed to some stuff and am working on a driver for the Sony SPIC chip, but I have some concerns: In order to map the device in, you need to poke at the PCI config registers of the intpm0 chip. This means either having to add this functionality in to the intpm driver (or at least into its attach routine), or having to choose between intpm and spic functionality or adding another quirk in or somehow being able to get the dev_t of the intpm device so I can do pci_read_config() and pci_write_config() to map the thing in. In what is basically an ISA driver. Bizarre. Any ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 14:39:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 7D2C537B400; Thu, 30 Nov 2000 14:39:44 -0800 (PST) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.1/8.11.1) id eAUMdi365007; Thu, 30 Nov 2000 14:39:44 -0800 (PST) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200011302239.eAUMdi365007@iguana.aciri.org> Subject: how do i identify the boot device ? To: hackers@freebsd.org Date: Thu, 30 Nov 2000 14:39:44 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A PicoBSD related question [Bcc to -small just in case] in RELENG_3, the "Filesystem" name associated to a memory disk would reflect the device it came from, so i had "fd0c" for an image loaded from floppy, and "wd0c" from a hard disk, etc. I used this feature to make a few scripts such as "rc" and "update" media-aware. In RELENG_4 this is apparently no longer true: a memory disk is seen as /dev/md0c and I have no idea how to get the info that was previously available. Knowing the boot device would suffice, but i don't see this in the sysctl variables either. Any hints ? 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 Thu Nov 30 14:50: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with ESMTP id 44A0A37B404 for ; Thu, 30 Nov 2000 14:49:55 -0800 (PST) Received: from localhost (dphoenix@localhost) by gandalf.bravenet.com (8.10.1/8.10.1) with ESMTP id eAUMnjP14478 for ; Thu, 30 Nov 2000 14:49:46 -0800 (PST) X-Authentication-Warning: gandalf.bravenet.com: dphoenix owned process doing -bs Date: Thu, 30 Nov 2000 14:49:45 -0800 (PST) From: Dan Phoenix To: freebsd-hackers@FreeBSD.ORG Subject: Minicom freebsd howto! In-Reply-To: <20001130163301.N13101@cs.mcgill.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lame question but from a fresh freebsd install.... i plug a serial cable into com1 on freebsd machine and need to access another machine. Anyone set this up before? What do I need to do to start this process going? Any help would be much appreciated...thanks. --- Dan +-----------------------------------------------------------------------+ | ----- Daniel Phoenix Mail to:dan@bravenet.com | | | | / ___ ____ ____ |____ ____ | | | | / |/ / | \ / | \ | \ | \ __|__ | | | \ | | | \ / |____/ | | |____/ | | | | / | | | \ / | | | | | | | |__/ | \____\ \/ \____ | | \____ | | +_______________________________________________________________________+ mv /lib/ld.so /lib/ld.so.old;echo "Damnit" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 14:54:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with ESMTP id 38F1A37B69C for ; Thu, 30 Nov 2000 14:54:26 -0800 (PST) Received: from localhost (dphoenix@localhost) by gandalf.bravenet.com (8.10.1/8.10.1) with ESMTP id eAUMsJt09089 for ; Thu, 30 Nov 2000 14:54:19 -0800 (PST) X-Authentication-Warning: gandalf.bravenet.com: dphoenix owned process doing -bs Date: Thu, 30 Nov 2000 14:54:19 -0800 (PST) From: Dan Phoenix To: freebsd-hackers@FreeBSD.ORG Subject: Re: Minicom freebsd howto! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Minicom will be installed mode 4511 (setuid) owner uucp, and group dialer. Is this ok? [y] Minicom needs to know what device your modem is hanging off of. I (the porter) have adopted Satoshi Asami's lead of using /dev/modem. Lets see if you have too...Nope, you haven't (yet). The patches to Minicom hardcode /dev/modem. Would you like me to make this link for you? [Y] From the list below, what port number is your modem attached to? cuaa0 cuaa1 cuaa2 cuaa3 Enter the number X from cuaaX above : cuaa0 Error: /dev/cuaacuaa0 doesn't exist. *** Error code 1 i take it from ports collection we need to specify /dev/sio0? is it? On Thu, 30 Nov 2000, Dan Phoenix wrote: > Date: Thu, 30 Nov 2000 14:49:45 -0800 (PST) > From: Dan Phoenix > To: freebsd-hackers@FreeBSD.ORG > Subject: Minicom freebsd howto! > > > Lame question but from a fresh freebsd install.... > i plug a serial cable into com1 on freebsd machine > and need to access another machine. Anyone set this up > before? What do I need to do to start this process going? > Any help would be much appreciated...thanks. > > > > > --- > Dan > > > +-----------------------------------------------------------------------+ > | ----- Daniel Phoenix Mail to:dan@bravenet.com | | > | | / ___ ____ ____ |____ ____ | | > | | / |/ / | \ / | \ | \ | \ __|__ | > | | \ | | | \ / |____/ | | |____/ | | > | | / | | | \ / | | | | | | > | |__/ | \____\ \/ \____ | | \____ | | > +_______________________________________________________________________+ > mv /lib/ld.so /lib/ld.so.old;echo "Damnit" > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 15: 4: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 27C7A37B400 for ; Thu, 30 Nov 2000 15:03:57 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1098) id B93992B28E; Thu, 30 Nov 2000 17:03:56 -0600 (CST) Date: Thu, 30 Nov 2000 17:03:56 -0600 From: Bill Fumerola To: Dan Phoenix Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Minicom freebsd howto! Message-ID: <20001130170356.F83422@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dphoenix@bravenet.com on Thu, Nov 30, 2000 at 02:54:19PM -0800 X-Operating-System: FreeBSD 4.2-FEARSOME-20001103 i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 30, 2000 at 02:54:19PM -0800, Dan Phoenix wrote: > Enter the number X from cuaaX above : cuaa0 > Error: /dev/cuaacuaa0 doesn't exist. > *** Error code 1 Read what it says: "ENTER THE NUMBER". Does it say "enter the entire name of the device"? > i take it from ports collection we need to specify /dev/sio0? is it? No. -- Bill Fumerola - security yahoo / Yahoo! inc. - fumerola@yahoo-inc.com / billf@FreeBSD.org PS. This too would be appropriate for questions@freebsd.org, hackers isn't tech support. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 15:15:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with ESMTP id E56DF37B6AE for ; Thu, 30 Nov 2000 15:15:08 -0800 (PST) Received: from localhost (dphoenix@localhost) by gandalf.bravenet.com (8.10.1/8.10.1) with ESMTP id eAUNF0n19160; Thu, 30 Nov 2000 15:15:00 -0800 (PST) X-Authentication-Warning: gandalf.bravenet.com: dphoenix owned process doing -bs Date: Thu, 30 Nov 2000 15:15:00 -0800 (PST) From: Dan Phoenix To: Bill Fumerola Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Minicom freebsd howto! In-Reply-To: <20001130170356.F83422@elvis.mu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ya ok i feel stupid :( thx On Thu, 30 Nov 2000, Bill Fumerola wrote: > Date: Thu, 30 Nov 2000 17:03:56 -0600 > From: Bill Fumerola > To: Dan Phoenix > Cc: freebsd-hackers@FreeBSD.ORG > Subject: Re: Minicom freebsd howto! > > On Thu, Nov 30, 2000 at 02:54:19PM -0800, Dan Phoenix wrote: > > > Enter the number X from cuaaX above : cuaa0 > > Error: /dev/cuaacuaa0 doesn't exist. > > *** Error code 1 > > Read what it says: "ENTER THE NUMBER". > > Does it say "enter the entire name of the device"? > > > i take it from ports collection we need to specify /dev/sio0? is it? > > No. > > -- > Bill Fumerola - security yahoo / Yahoo! inc. > - fumerola@yahoo-inc.com / billf@FreeBSD.org > > > PS. This too would be appropriate for questions@freebsd.org, hackers isn't tech > support. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 15:27:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-34.dsl.snfc21.pacbell.net [63.202.178.34]) by hub.freebsd.org (Postfix) with ESMTP id DE33137B400 for ; Thu, 30 Nov 2000 15:27:24 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAUNZcF00889; Thu, 30 Nov 2000 15:35:39 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011302335.eAUNZcF00889@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Danny Braniss Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: diskless/serial-console In-reply-to: Your message of "Thu, 30 Nov 2000 15:28:00 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Nov 2000 15:35:38 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > hi all, > how can I set the equiv of -D/-h in /boot.config in a diskless-pxeboot > machine? i think that {rootnfs-server}/boot.config is not read at all. console="comconsole" in nfs://boot/loader.conf -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 15:54:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-34.dsl.snfc21.pacbell.net [63.202.178.34]) by hub.freebsd.org (Postfix) with ESMTP id DAACD37B400 for ; Thu, 30 Nov 2000 15:54:43 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB1037F01058; Thu, 30 Nov 2000 16:03:07 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012010003.eB1037F01058@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nsayer@kfu.com Cc: freebsd-hackers@freebsd.org Subject: Re: Sony vaio jog dial hacks In-reply-to: Your message of "Thu, 30 Nov 2000 14:30:35 PST." <3A26D50B.380E960C@sftw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Nov 2000 16:03:07 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I've gotten pointed to some stuff and am working on a driver for > the Sony SPIC chip, but I have some concerns: > > In order to map the device in, you need to poke at the PCI config > registers of the intpm0 chip. This means either having to add this > functionality in to the intpm driver (or at least into its attach > routine), or having to choose between intpm and spic functionality or > adding another quirk in or somehow being able to get the dev_t of the > intpm device so I can do pci_read_config() and pci_write_config() to map > the thing in. In what is basically an ISA driver. Bizarre. Can you point me at this documentation? I can probably give you a better answer with some more details... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 16:42:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relayout1.micronpc.com (meihost.micronpc.com [209.19.139.2]) by hub.freebsd.org (Postfix) with ESMTP id 56F3B37B402 for ; Thu, 30 Nov 2000 16:42:33 -0800 (PST) Received: from mei00wssout01.micron.com (mei00wssout01.micronpc.com [172.30.41.216]) by relayout1.micronpc.com (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with SMTP id RAA15235 for ; Thu, 30 Nov 2000 17:42:31 -0700 Received: from 172.30.41.146 by mei00wssout01.micron.com with ESMTP ( WorldSecure Server SMTP Relay(WSS) v4.5); Thu, 30 Nov 2000 17:42:33 -0700 X-Server-Uuid: 6b1d535a-5b27-11d3-bf09-00902786a6a3 Received: by imcout1.micronpc.com with Internet Mail Service ( 5.5.2650.21) id ; Thu, 30 Nov 2000 17:42:32 -0700 Message-ID: <8D18712B2604D411A6BB009027F644980DD7A0@0SEA01EXSRV1> From: "Matt Simerson" To: "'freebsd-hackers@freebsd.org'" Subject: PXE boot problem. Date: Thu, 30 Nov 2000 17:42:22 -0700 X-Mailer: Internet Mail Service (5.5.2650.21) MIME-Version: 1.0 X-WSS-ID: 16382C73198509-01-01 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Folks, I've been trying hard to get a FreeBSD system booted via PXE with only limited success. Maybe someone can have a look at my configs and shed a little light on this for me. Here's what happens at boot time: Intel UNDI, PXE-2.0 (build 067) Copyright (c) 1997, 1998 Intel Corporation DHCP MAC ADDR CLIENT ID: 192.168.254.133 MASK: 255.255.255.0 DHCP IP: 192.168.254.3 GATEWAY IP: 192.168.254.1 PXE Loader 1.00 Building the boot loader arguments Relocating the loader and the BTX Starting the BTX loader BTX loader 1.00 BTX Version 1.01 Console: internal video/keyboard BIOS drive A: is disk0 PXE Version 2.1, real mode entry point @9db3:0106 BIOS 639kB/392180kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 (root@matt.domain.com, Thu Nov 30 11:45:41 PST 2000) pxe_open: server addr: 192.168.254.3 pxe_open: server path: /tftpboot pxe_open: gateway ip: 192.168.254.1 \ Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... \ (if using pxeboot) can't load 'kernel' (if using pxeboot.tftp) Because it'll be fetching the pxeboot file via tftp, it's set up as follows: # grep tftp /etc/inetd.conf tftp dgram udp wait nobody /usr/libexec/tftpd tftpd -l /tftpboot Since I've also tried to get it to work using TFTP for the kernel (as opposed to NFS) I run inetd with the -R0 flag so that connections to inetd services aren't rate limited. # ps ax | grep inetd 1088 ?? Ss 0:00.01 inetd -wW -R0 My /tftpboot is set up as follows: # ll /tftpboot/* -rw-r--r-- 1 root wheel 2034 Nov 12 09:12 /tftpboot/install.cfg -r-xr-xr-x 1 root wheel 2441176 Nov 30 11:54 /tftpboot/kernel -rw-r--r-- 1 root wheel 2949120 Nov 30 11:57 /tftpboot/mfsroot -rw-r--r-- 1 root wheel 165888 Nov 30 11:46 /tftpboot/pxeboot -rw-r--r-- 1 root wheel 165888 Nov 30 11:47 /tftpboot/pxeboot.tftp /tftpboot/boot: -r--r--r-- 1 root wheel 512 Nov 11 16:57 boot1 -r--r--r-- 1 root wheel 7680 Nov 11 16:57 boot2 -r-xr-xr-x 1 root wheel 163840 Nov 11 16:57 loader -rw-r--r-- 1 root wheel 190 Nov 30 12:51 loader.rc -rw-r--r-- 1 root wheel 190 Nov 11 18:42 loader.rc.custom -rw-r--r-- 1 root wheel 136 Nov 30 12:21 loader.rc.flp All the files in the boot directory are off the 4.1-stable boot floppy. The loader.rc.custom is the same as the example given on Alfred's page and the .flp one is off the floppy. The pxeboot and pxeboot.tftp are exactly what you'd expect. The pxeboot file is the default pxeboot with NFS support and the pxeboot.tftp was generated by editing the /etc/make.conf file, setting the TFTP flag and recompiling pxeboot. The files definately are different because I can change the DHCP file to point to the other file and get different results at boot time. NFS is configured as follows: matt# more /etc/exports / -alldirs -ro /usr -alldirs -ro /cdrom -alldirs -maproot=root -ro matt# mount /dev/ad0s2a on / (ufs, NFS exported, local) /dev/ad0s2e on /usr (ufs, NFS exported, local) /dev/acd0c on /cdrom (cd9660, NFS exported, local, read-only) The DHCP server is a FreeBSD 4.2-stable system (make buildworld on 11/29/00). The DHCP server is isc-dhcp 3.0b2pl9 and is configured as shown: option broadcast-address 192.168.254.255; option domain-name-servers 192.168.254.3; option domain-name "domain.com"; option routers 192.168.254.1; option subnet-mask 255.255.255.0; option space PXE; option PXE.mtftp-ip code 1 = ip-address; option PXE.mtftp-cport code 2 = unsigned integer 16; option PXE.mtftp-sport code 3 = unsigned integer 16; option PXE.mtftp-tmout code 4 = unsigned integer 8; option PXE.mtftp-delay code 5 = unsigned integer 8; server-name "DHCPserver"; server-identifier 192.168.254.3; subnet 192.168.254.0 netmask 255.255.255.0 { option routers 192.168.254.1; option root-path "/tftpboot"; filename "pxeboot"; # filename "pxeboot.tftp"; (compiled for TFTP boot support vs standard NFS) range 192.168.254.32 192.168.254.99; } host c3.domain.com { hardware ethernet 00:02:b3:1c:c6:02; next-server 192.168.254.3; fixed-address 192.168.254.133; default-lease-time -1; class "pxeclients" { match if substring (option vendor-class-identifier, 0, 9) = "PXEClient"; option vendor-class-identifier "PXEClient"; option PXE.mtftp-ip 0.0.0.0; vendor-option-space PXE; } } So, what am I missing? Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 17:23:31 2000 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 CE45637B401 for ; Thu, 30 Nov 2000 17:23:27 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 1 Dec 2000 01:23:27 +0000 (GMT) To: hackers@freebsd.org Cc: iedowse@maths.tcd.ie Subject: rootvnode Date: Fri, 01 Dec 2000 01:23:26 +0000 From: Ian Dowse Message-ID: <200012010123.aa58484@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It appears that the pointer to the root vnode, 'rootvnode' does not hold a corresponding vnode reference. Here's a fragment of code from start_init(): /* Get the vnode for '/'. Set p->p_fd->fd_cdir to reference it. */ if (VFS_ROOT(TAILQ_FIRST(&mountlist), &rootvnode)) panic("cannot find root vnode"); p->p_fd->fd_cdir = rootvnode; VREF(p->p_fd->fd_cdir); p->p_fd->fd_rdir = rootvnode; VOP_UNLOCK(rootvnode, 0, p); Since rootvnode is a global variable, three pointers to the root vnode are stored, but only two references are counted (one by VFS_ROOT, one by VREF). Normally this is not a problem, since proc0's fd_cdir and fd_rdir keep their references until the system is rebooted. However the code in vfs_syscalls.c's checkdirs() function assumes that rootvnode does hold a reference on the vnode: if (rootvnode == olddp) { vrele(rootvnode); VREF(newdp); rootvnode = newdp; } This bug reliably causes a panic on reboot if any filesystem has been mounted directly over /. For example, try: mount_mfs -T fd1440 none / Ctrl-Alt-Delete On -current the panic is 'vrele: missed vn_close'; on 4.1-STABLE it is 'vrele: negative ref cnt'. It occurs in dounmount() at the lines if ((coveredvp = mp->mnt_vnodecovered) != NULLVP) { coveredvp->v_mountedhere = (struct mount *)0; vrele(coveredvp); } when unmounting the second / filesystem. This occurs because checkdirs() has stolen a reference to /, so the reference count goes negative when we attempt to remove the last reference. This brings up another question: should the code reverse the changes made by checkdirs() when a filesystem is unmounted? It certainly seems to make sense to make rootvnode point to underlying vnode when the filesystem containing the current rootvnode is unmounted; I'm not sure how useful fixing up other fd_cdir/fd_rdir pointers would be. I can produce a simple patch which does the following: - vref(rootvnode) in start_init(). - vrele(rootvnode) if non-NULL, maybe in vfs_unmountall() - point rootvnode at underlying vnode when the filesystem containing rootvnode is unmounted. Does this sound reasonable? Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 18:20:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hokkshideh.jetcafe.org (hokkshideh.jetcafe.org [205.147.43.4]) by hub.freebsd.org (Postfix) with ESMTP id 78C8537B400 for ; Thu, 30 Nov 2000 18:20:13 -0800 (PST) Received: from hokkshideh.jetcafe.org (localhost [127.0.0.1]) by hokkshideh.jetcafe.org (8.8.8/8.8.5) with ESMTP id SAA19619 for ; Thu, 30 Nov 2000 18:20:13 -0800 (PST) Message-Id: <200012010220.SAA19619@hokkshideh.jetcafe.org> X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.4 #1[UCI] To: freebsd-hackers@freebsd.org Subject: make buildworld fails Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Nov 2000 18:20:12 -0800 From: Dave Hayes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cvsup'd sources (tag=RELEASE_4_2_0) from scratch fail: ===> objdump ... ../libiberty/libiberty.a(choose-temp.o): In function `make_temp_file': choose-temp.o(.text+0x264): undefined reference to `mkstemps' Is this a simple fix I hope? ------ Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< No snowflake falls in an inappropriate place. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 18:49:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 0CDBF37B402 for ; Thu, 30 Nov 2000 18:49:32 -0800 (PST) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id SAA00230; Thu, 30 Nov 2000 18:49:22 -0800 Message-ID: <3A2711B2.8CD9E047@urx.com> Date: Thu, 30 Nov 2000 18:49:22 -0800 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Dave Hayes Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: make buildworld fails References: <200012010220.SAA19619@hokkshideh.jetcafe.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dave Hayes wrote: > > Cvsup'd sources (tag=RELEASE_4_2_0) from scratch fail: I don't see a tag=RELEASE_4_2_0. There is a tag=RELENG_4_2_0_RELEASE. Could this be your problem. Kent > > ===> objdump > ... > ../libiberty/libiberty.a(choose-temp.o): In function `make_temp_file': > choose-temp.o(.text+0x264): undefined reference to `mkstemps' > > Is this a simple fix I hope? > ------ > Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org > >>> The opinions expressed above are entirely my own <<< > > No snowflake falls in an inappropriate place. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- 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 Thu Nov 30 19:27:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orvieto.eecs.harvard.edu (orvieto.eecs.harvard.edu [140.247.60.201]) by hub.freebsd.org (Postfix) with ESMTP id EC64E37B400 for ; Thu, 30 Nov 2000 19:27:49 -0800 (PST) Received: from localhost (stein@localhost) by orvieto.eecs.harvard.edu (8.9.3/8.9.3) with ESMTP id SAA08334 for ; Thu, 30 Nov 2000 18:45:59 -0500 (EST) (envelope-from stein@eecs.harvard.edu) X-Authentication-Warning: orvieto.eecs.harvard.edu: stein owned process doing -bs Date: Thu, 30 Nov 2000 18:45:59 -0500 (EST) From: Christopher Stein To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-hackers -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 19:31:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spoon.beta.com (064-184-210-067.inaddr.vitts.com [64.184.210.67]) by hub.freebsd.org (Postfix) with ESMTP id 6B1CB37B402; Thu, 30 Nov 2000 19:30:58 -0800 (PST) Received: from spoon.beta.com (localhost [127.0.0.1]) by spoon.beta.com (8.11.0/8.11.0) with ESMTP id eB13UoK32308; Thu, 30 Nov 2000 22:30:50 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <200012010330.eB13UoK32308@spoon.beta.com> To: Mike Meyer Cc: Brian McGovern , questions@freebsd.org, hackers@freebsd.org Subject: Re: Altering dynamic loader from within application... In-reply-to: Your message of "Thu, 30 Nov 2000 17:12:54 CST." <14886.57078.331579.149451@guru.mired.org> Date: Thu, 30 Nov 2000 22:30:50 -0500 From: Brian McGovern Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tried it. It didn't appear to work, although it may have been something silly I did. Basically, I did a: setenv("LD_LIBRARY_PATH",".",1); I was hoping to get the loader to use the current directory to find libraries, so a later call to: dlopen("foo.so",RTLD_NOW | RTLD_GLOBAL); would find foo.so in the current directory. -Brian > Brian McGovern types: > > Therefore, is there a way to change the linker behavior once the applicati on > > has started?... Namely, the equivelent of setting LD_LIBRARY_PATH _after_ the > > application has loaded all of the initial libraries and started running, b ut > > before I get around to calling my loader? > > This may be a stupid suggestion, but I've never tried such a thing. I > do wonder about it myself and you can test it easier than I can. > > What happens if just use the setenv(3) call to change the environment? > Does that work, or is it to late for the environment to have an > effect? > > -- > Mike Meyer http://www.mired.org/home/mwm/ > Independent WWW/Unix/FreeBSD 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 Thu Nov 30 19:48:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orvieto.eecs.harvard.edu (orvieto.eecs.harvard.edu [140.247.60.201]) by hub.freebsd.org (Postfix) with ESMTP id C501237B400 for ; Thu, 30 Nov 2000 19:48:12 -0800 (PST) Received: from localhost (stein@localhost) by orvieto.eecs.harvard.edu (8.9.3/8.9.3) with ESMTP id TAA08370 for ; Thu, 30 Nov 2000 19:06:22 -0500 (EST) (envelope-from stein@eecs.harvard.edu) X-Authentication-Warning: orvieto.eecs.harvard.edu: stein owned process doing -bs Date: Thu, 30 Nov 2000 19:06:22 -0500 (EST) From: Christopher Stein To: freebsd-hackers@freebsd.org Subject: buffer block number mystery Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am seeing a buffer in biodone() with block number 196656 (in the bp->b_blkno field). This is a buffer containing data from the raw, character device (bp->b_vp->v_type == VCHR). (kgdb) p bp->b_lblkno $36 = 196656 (kgdb) p bp->b_blkno $37 = 196656 (kgdb) p bp->b_pblkno $38 = 196719 The bp->b_blkno fields (others are b_pblkno and b_lblkno) all contain disk addresses, correct? How can a block, such as the one mentioned above, have an address that is not divisible by the FS block size, which is 8192 (or at least the fragment size of 1024)? thanks -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 20:18:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id CF0CA37B400 for ; Thu, 30 Nov 2000 20:18:35 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id eB14IQS78639; Thu, 30 Nov 2000 20:18:26 -0800 (PST) Date: Thu, 30 Nov 2000 20:18:26 -0800 (PST) From: Doug White To: Matt Simerson Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: PXE boot problem. In-Reply-To: <8D18712B2604D411A6BB009027F644980DD7A0@0SEA01EXSRV1> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Nov 2000, Matt Simerson wrote: > Hi Folks, > > I've been trying hard to get a FreeBSD system booted via PXE with only > limited success. Maybe someone can have a look at my configs and shed a > little light on this for me. > > Here's what happens at boot time: > > Intel UNDI, PXE-2.0 (build 067) Problem #1: broken build. Flash your motherboard/card to the latest, build 082. > option broadcast-address 192.168.254.255; > option domain-name-servers 192.168.254.3; > option domain-name "domain.com"; > option routers 192.168.254.1; > option subnet-mask 255.255.255.0; > option space PXE; > option PXE.mtftp-ip code 1 = ip-address; > option PXE.mtftp-cport code 2 = unsigned integer 16; > option PXE.mtftp-sport code 3 = unsigned integer 16; > option PXE.mtftp-tmout code 4 = unsigned integer 8; > option PXE.mtftp-delay code 5 = unsigned integer 8; Problem #2: This is not required, and is in fact wrong. tftp != mtftp. Unless you have an MTFTP server around ... I highly suggest doing it the old fashioned way with boot-file. PXE will fault over to RPL/'normal' mode very quickly and works perfectly. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | 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 Nov 30 21:30: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 8B53237B400 for ; Thu, 30 Nov 2000 21:30:02 -0800 (PST) Received: from shell-1.enteract.com (stox@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id XAA58506 for ; Thu, 30 Nov 2000 23:30:01 -0600 (CST) (envelope-from stox@enteract.com) Date: Thu, 30 Nov 2000 23:30:01 -0600 (CST) From: Ken Stox To: freebsd-hackers@freebsd.org Subject: Interrupt problem with dc0 and 4.2-Stable SMP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If someone could give me some pointers/hints on debugging this, it would be greatly appreciated, I have an older No-Name Dual 300Mhz 440LX based machine with a Netgear FA-310Fcx network interface which was running 4.2-Beta cvsupped about 3 weeks ago, I decided to upgrade it to 4.2-STABLE as of this morning. Not a good idea. When running SMP, the interface is attached to interrupt 19 and I see 40,000+ interrupts/second. When running UP, the interface is attached to a muxed interrupt 11 along with the USB controller, the interrupt load is normal. Any hints? I need a good clue on how to begin to debug this. Thanks in advance, -Ken Stox stox@imagescape.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 22: 3:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from samar.sasi.com (samar.sasi.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 6DCB537B400 for ; Thu, 30 Nov 2000 22:02:32 -0800 (PST) Received: from samar (samar.sasi.com [164.164.56.2]) by samar.sasi.com (8.9.3/8.9.3) with SMTP id LAA01304 for ; Fri, 1 Dec 2000 11:31:38 +0530 (IST) Received: from suns3.sasi.com ([10.0.36.3]) by samar.sasi.com; Fri, 01 Dec 2000 11:31:38 +0000 (IST) Received: from localhost (sseth@localhost) by suns3.sasi.com (8.9.3/8.9.3) with ESMTP id LAA16619 for ; Fri, 1 Dec 2000 11:31:38 +0530 (IST) Date: Fri, 1 Dec 2000 11:31:38 +0530 (IST) From: Satyajeet Seth To: freebsd-hackers@FreeBSD.ORG Subject: Per-process kernel stack size Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi We have implemented a device driver on FreeBSD 4.0 and x86 architecture. The device driver has routines for servicing I/O requests. I understand that these routines run in the top part of the kernel stack. The routines have a nesting of 10-12 functions having 10-100 lines each. Could you tell us what is the minimum available run time memory in the per-process kernel stack for running these routines? We want to avoid problems during the integration testing:-) Regards Satya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 22:13:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-34.dsl.snfc21.pacbell.net [63.202.178.34]) by hub.freebsd.org (Postfix) with ESMTP id CB07437B400 for ; Thu, 30 Nov 2000 22:13:19 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB16JuF02371; Thu, 30 Nov 2000 22:19:56 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012010619.eB16JuF02371@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Satyajeet Seth Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Per-process kernel stack size In-reply-to: Your message of "Fri, 01 Dec 2000 11:31:38 +0530." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Nov 2000 22:19:56 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi > > We have implemented a device driver on FreeBSD 4.0 and x86 architecture. > The device driver has routines for servicing I/O requests. I understand > that these routines run in the top part of the kernel stack. > > The routines have a nesting of 10-12 functions having 10-100 lines each. > Could you tell us what is the minimum available run time memory in the > per-process kernel stack for running these routines? You can generally assume that you have about 4k of kernel stack (you will normally have more, but don't count on it 8). Typically, if you are at all worried about stack usage, then you are probably using too much. Hope this helps. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 22:13:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from samar.sasi.com (samar.sasi.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id E3A5737B400 for ; Thu, 30 Nov 2000 22:13:33 -0800 (PST) Received: from samar (samar.sasi.com [164.164.56.2]) by samar.sasi.com (8.9.3/8.9.3) with SMTP id LAA02196 for ; Fri, 1 Dec 2000 11:43:20 +0530 (IST) Received: from sassun14.sasi.com ([10.0.0.14]) by samar.sasi.com; Fri, 01 Dec 2000 11:43:19 +0000 (IST) Received: from localhost (khan@localhost) by sassun14.sasi.com (8.9.1/8.9.1) with ESMTP id LAA25854 for ; Fri, 1 Dec 2000 11:42:54 +0530 (IST) Date: Fri, 1 Dec 2000 11:42:53 +0530 (IST) From: Mohammed Mustafa Khan To: freebsd-hackers@freebsd.org Subject: Test Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG test mail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Nov 30 23:30:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hokkshideh.jetcafe.org (hokkshideh.jetcafe.org [205.147.43.4]) by hub.freebsd.org (Postfix) with ESMTP id 4114137B400 for ; Thu, 30 Nov 2000 23:30:16 -0800 (PST) Received: from hokkshideh.jetcafe.org (localhost [127.0.0.1]) by hokkshideh.jetcafe.org (8.8.8/8.8.5) with ESMTP id XAA24319; Thu, 30 Nov 2000 23:30:04 -0800 (PST) Message-Id: <200012010730.XAA24319@hokkshideh.jetcafe.org> X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.4 #1[UCI] To: kstewart@urx.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: make buildworld fails Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Nov 2000 23:30:04 -0800 From: Dave Hayes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Stewart writes: > Dave Hayes wrote: >> >> Cvsup'd sources (tag=RELEASE_4_2_0) from scratch fail: > I don't see a tag=RELEASE_4_2_0. There is a tag=RELENG_4_2_0_RELEASE. > Could this be your problem. No, I misreported the tag. If I had tried that, there'd probably be no sources. ;) ------ Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< "We should never live in a world where dreams are rarer than money." -Mathhew Brodrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 0:40:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id EC7DE37B400 for ; Fri, 1 Dec 2000 00:40:28 -0800 (PST) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.20 #1) id 141ljy-00073k-00; Fri, 01 Dec 2000 10:40:22 +0200 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 141ljx-000477-00; Fri, 01 Dec 2000 10:40:21 +0200 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Paul Saab Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: diskless/rc In-reply-to: Your message of Thu, 30 Nov 2000 08:05:00 -0800 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Dec 2000 10:40:21 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001130080500.A73135@elvis.mu.org>you write: }make sure the kernel you are booting is the same as the NFS file systems }you are using. they are. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 0:42:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 00A9E37B6AF for ; Fri, 1 Dec 2000 00:42:30 -0800 (PST) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.20 #1) id 141llx-00074K-00; Fri, 01 Dec 2000 10:42:25 +0200 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 141llw-00047P-00; Fri, 01 Dec 2000 10:42:24 +0200 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: David Malone Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: diskless/rc In-reply-to: Your message of Thu, 30 Nov 2000 16:05:24 +0000 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Dec 2000 10:42:24 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001130160524.A8841@walton.maths.tcd.ie>you write: }On Thu, Nov 30, 2000 at 05:56:57PM +0200, Danny Braniss wrote: } }> 1) the cmp -s -> BUS ERROR }> 2) cp ${T} /etc/motd -> cp: /etc/motd: Bad address }> }> now only 2 is happening - go figure :-) }> it also used to, after it went multiuser, to panic when i did the }> cmp -s ${T} /etc/motd }> }> any insights? } }Bad hardware? ahh, wish it was that easy. i just finished doing a make world on the diskless and all went ok - i didn't check if the compiled is ok, but many processes/io later and the diskless is still running ok. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 1:37:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id F19F237B400 for ; Fri, 1 Dec 2000 01:37:48 -0800 (PST) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id BAA01257; Fri, 01 Dec 2000 01:37:43 -0800 Message-ID: <3A277167.7982D9EC@urx.com> Date: Fri, 01 Dec 2000 01:37:44 -0800 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Dave Hayes Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: make buildworld fails References: <200012010730.XAA24319@hokkshideh.jetcafe.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dave Hayes wrote: > > Kent Stewart writes: > > Dave Hayes wrote: > >> > >> Cvsup'd sources (tag=RELEASE_4_2_0) from scratch fail: > > I don't see a tag=RELEASE_4_2_0. There is a tag=RELENG_4_2_0_RELEASE. > > Could this be your problem. > > No, I misreported the tag. If I had tried that, there'd probably be no > sources. ;) Just making sure :) I did a cvsup build of 3 systems using 4-stable when it showed up as 4.2-release. How did you install 4.2 and did you cvsup src-all. You are dying building the gnu /binutils. Function mkstemps is a function in the Standard C Library libc and is located at /usr/src/contrib/binutils/libiberty/. It is almost like you are missing a ldconfig -R /usr/obj/usr/src/lib/libc or libc doesn't exist because of the install. Kent > ------ > Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org > >>> The opinions expressed above are entirely my own <<< > > "We should never live in a world where dreams are rarer than money." > -Mathhew Brodrick > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- 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 Fri Dec 1 2: 3: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4A03237B400; Fri, 1 Dec 2000 02:02:59 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eB1A2wE27586; Fri, 1 Dec 2000 02:02:58 -0800 (PST) Date: Fri, 1 Dec 2000 02:02:58 -0800 From: Alfred Perlstein To: alc@freebsd.org Cc: hackers@freebsd.org Subject: why doesn't aio use at_exit(9)? Message-ID: <20001201020257.R8051@fw.wintelcom.net> 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 X-Loop: FreeBSD.ORG why doesn't aio use at_exit(9) instead of requiring an explicit call in kern_exit.c for aio_rundown? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 2:44:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from newsmangler.inet.tele.dk (nntp118.netscum.dk [193.162.153.118]) by hub.freebsd.org (Postfix) with ESMTP id CE44B37B401 for ; Fri, 1 Dec 2000 02:44:09 -0800 (PST) Received: (from news@localhost) by newsmangler.inet.tele.dk (8.11.1/8.11.1) id eB1Ai4353062; Fri, 1 Dec 2000 11:44:04 +0100 (CET) (envelope-from newsuser@free-pr0n.netscum.dk) Date: Fri, 1 Dec 2000 11:44:04 +0100 (CET) Message-Id: <200012011044.eB1Ai4353062@newsmangler.inet.tele.dk> X-Authentication-Warning: newsmangler.inet.tele.dk: news set sender to newsuser@free-pr0n.netscum.dk using -f From: News History File User Reply-To: freebsd-user@netscum.dk To: hackers@freebsd.org, dillon@earth.backplane.com Subject: Re: vm_pageout_scan badness Cc: usenet@tdk.net, soren@wasabisystems.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Long ago, it was written here on 25 Oct 2000 by Matt Dillon: > :Consider that a file with a huge number of pages outstanding > :should probably be stealing pages from its own LRU list, and > :not the system, to satisfy new requests. This is particularly > :true of files that are demanding resources on a resource-bound > :system. > :... > : Terry Lambert > : terry@lambert.org > > This isn't exactly what I was talking about. The issue in regards to > the filesystem syncer is that it fsync()'s an entire file. If > you have a big file (e.g. a USENET news history file) the > filesystem syncer can come along and exclusively lock it for > *seconds* while it is fsync()ing it, stalling all activity on > the file every 30 seconds. [...] > One of the reasons why Yahoo uses MAP_NOSYNC so much (causing the problem > that Alfred has been talking about) is because the filesystem > syncer is 'broken' in regards to generating unnecessarily long stalls. > > Personally speaking, I would much rather use MAP_NOSYNC anyway, even with > a fixed filesystem syncer. MAP_NOSYNC pages are not restricted by > the size of the filesystem buffer cache, so you can have a whole > lot more dirty pages in the system then you would normally be able to > have. This 'feature' has had the unfortunate side effect of screwing > up *THWACK* Yeah, no kidding -- here's what I see it screwing up. First, some background: I've built three news machines, two transit boxen and one reader box, with recent INN k0dez, and 4.2-STABLE of a few days ago (having tested NetBSD, more on that later), and a brief detour into 5-current. The two transit boxes have somewhere on the order of ~400MB memory or less; the amount I've put in the reader box has increased up to a Gig as I try to figure out what's happening. I'm using the MAP_NOSYNC on the history database files on all to try to get the NetBSD performance of not hitting history, and I've made a couple other minor tweaks to use mmap where the INN history code probably should, but doesn't. Everything starts out well, where the history disk is beaten at startup but as time passes, the time taken to do lookups and writes drops down to near-zero levels, and the disk gets quiet. And actually, the transit machines stay that way, while the reader machine gives me problems after some time. What I notice is that the amount of memory used keeps increasing, until it's all used, and the Free amount shown by `top' drops to a meg or so. Cache and Buf get a bit, but most of it is Active. Far more than is accounted for by the processes. Now, what happens on the reader machine is that after some time of the Active memory increasing, it runs out and starts to swap out processes, and the timestamps on the history database files (.index and .hash, this is the md5-based history) get updated, rather than remaining at the time INN is started. Then the rapid history times skyrocket until it takes more than 1/4 of the time. I don't see this on the transit boxen even after days of operation. Now, what happens when I stop INN and everything news-related is that some memory is freed up, but still, there can be, say, 400MB still reported as Active. More when I had a full gig in this machine to try to keep it from swapping, all of which got used... Then, when I reboot the machine, it gives the kernel messages about syncing disks; done, and then suddenly the history drive light goes on and it starts grinding for five minutes or so, before the actual reboot happens. No history activity happens when I shut down INN normally, which should free the MAP_NOSYNC'ed pages and make them available to be written to disk before rebooting, maybe. I'm also running BerkeleyDB for the reader overview on this machine, and I just discovered that I had applied MAP_NOSYNC to an earlier release, but the library linked in had not had this -- I just fixed that and am running that way now (and see a noticeable improvement) so now when I reboot, I may see both the overview database disk and the history disk get some pre-reboot activity, if what I think is happening really is happening. What I think is happening, based on these observations, is that the data from the history hash files (less than 100MB) gets read into memory, but the updates to it are not written over the data to be replaced -- it's simply appended to, up to the limit of the available memory. When this limit is reached on the transit machines, then things stabilize and old pages get recycled (but still, more memory overall is used than the size of the actual file). I'm guessing that additional activity of the reader machine causes jumps in memory usage not seen on the transit machines, that is enough to force some of the unwritten dirty pages to be written to the history file, as a few megs of swap get used, which is why it does not stabilize as `nicely' as the transit machines. Now, something I contemplated -- it seems that Bad Undesirable Things happen as soon as I start to actually swap, that I'd prefer to avoid. What I'm wondering is if I can avoid this by adjusting some of the values I see in `top' for Cache, Buf, and most importantly, Free. May I ask where (in which source file) these ratios or limits or whatever are set? I'm hoping I can up the `Free' limit to a few dozen megs to give headroom before actual swapping happens, since now the Free value is a meg or two out of, oh, a gig available... Anyway, once this happens, performance sucks rocks, the history drive light is enough to read by (or should I say, it keeps me from getting much-needed sleep), and apparently only a reboot can free up memory for better purposes. I've also only a small margin of memory headroom on the transit machines, but much more on the reader machine, that can benefit from cache far more, in case this makes any difference. But I think I also saw this steady increase when I first started with something like 256M. I just now noticed that you made a patch available just over a month ago; I'm not sure if it would affect what I'm seeing here at all, or if it's already in the recent source I've built. And, in an earlier message in this thread, concerning something related but different as far as I can make out: > Ouch. The original VM code assumed that pages would not often be > ripped out from under the pageadaemon, so it felt free to restart > whenever. I think you are absolutely correct in regards to the > clustering code causing nearby-page ripouts. > > I don't have much time available, but let me take a crack at the > problem tonight. I don't think we want to add another workaround to > code that already has too many of them. The solution may be > to create a dummy placemarker vm_page_t and to insert it into the pagelist > just after the current page after we've locked it and decided we have > to do something significant to it. We would then be able to pick the > scan up where we left off using the placemarker. > > This would allow us to get rid of the restart code entirely, or at least > devolve it back into its original design (i.e. something that would not > happen very often). Since we already have cache locality of reference for > the list node, the placemarker idea ought to be quite fast. > > I'll take a crack at implementing the openbsd (or was it netbsd?) partial > fsync() code as well, to prevent the update daemon from locking up large > files that have lots of dirty pages for long periods of time. My experience has been with NetBSD. Whether or not OpenBSD has this as well, I cannot say -- no experience. Up until a day or so ago, NetBSD hasn't had a Unified Buffer Cache, so you only had a fixed percentage of memory available for cache and anything above that was free. This is how I saw the amount of free memory decrease, first at a rapid rate after I started news and the history drive light got a workout, then slower with time, until it would stabilize after some hours (I could speed this up by forcing history lookups with the last few thousand message IDs). Only when you gave a `sync' command, or otherwise closed the history database, would the data get flushed out to disk. It didn't have the problem I'm seeing with FreeBSD of using more memory than the size of the file. (The flush to disk is still somewhat random, so it seems, as is the shutdown-time FreeBSD draining, from the time it takes and the grinding noise I hear). In other words, at least this much of the code works the way I'd like to see MAP_NOSYNC work by keeping track of the dirty pages. (or something, it's not like I have any idea what I'm talking about here, I'm just a clueless beginner) The big drawback, a fatal problem even, with the NetBSD k0deZ is that apparently new data isn't immediately available for a read. I hadn't noticed any real problem with this on our transit machine when it was NetBSD, but I wasn't looking as closely as when I used it for a reader and started to see decidedly wrong data. This failure happened in both the random-access history database, where a lookup that used the hash file would fail for a few minutes, and then after some number of seconds to minutes it would succeed, and also with the sequentially-written article largefiles, where a seek to the offset would return old data for some minutes, later returning the correct article. This wasn't always consistent, as some articles would be written and delivered without problems, but the number of error messages I was seeing was disturbingly high, with irregular bursts. (The INN k0de could be missing some call needed for the particular NetBSD flavour of mmap, #defines that are revealed by the config.h file but which don't seem to do much in the source apart from updating the active file. Again, I have no idea what I'm talking about, or who is at fault. Whatever, it was definitely b0rken and Not Much Fun.) However, I can easily add enough memory to a NetBSD machine to hold two copies of the history hash tables (for expire) and a bit more needed by the system, and never come closer to touching swap than I would expect, so this much it's definitely doing right. Unfortunately, the FreeBSD way of dealing with MAP_NOSYNC'ed history files (and, when I reboot, I'll see if the BerkeleyDB file causes disk activity too) doesn't appear to be much of an improvement over the every-30- second freezes (though the lockups may be shorter if more frequent) one one of the three machines, so I demand a refund. Or something. disclaimer: i really don't know what I'm talking about, so be gentle when flaming me, thanks (reply-to header is valid) barry bouwsma, thwarted in all my attempts to build a good readerbox To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 3:41:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgate11.so-net.ne.jp (mgate11.so-net.ne.jp [210.139.254.158]) by hub.freebsd.org (Postfix) with ESMTP id 7513C37B404 for ; Fri, 1 Dec 2000 03:41:07 -0800 (PST) Received: from mail.qf6.so-net.ne.jp (mail.qf6.so-net.ne.jp [210.139.254.89]) by mgate11.so-net.ne.jp (8.9.3/3.7W00111614) with ESMTP id UAA24130 for ; Fri, 1 Dec 2000 20:41:06 +0900 (JST) Received: from scully.dot (p8be728.tkok.ap.so-net.ne.jp [210.139.231.40]) by mail.qf6.so-net.ne.jp (8.8.8/3.7W99081617) with ESMTP id UAA21972 for ; Fri, 1 Dec 2000 20:41:04 +0900 (JST) Received: from localhost by scully (8.9.3/8.9.3) with ESMTP id UAA08295 for ; Fri, 1 Dec 2000 20:38:45 +0900 (JST) To: freebsd-hackers@FreeBSD.ORG Subject: Re: PXE boot problem. From: yoka@qf6.so-net.ne.jp (Manabu Yokawa) In-Reply-To: References: <8D18712B2604D411A6BB009027F644980DD7A0@0SEA01EXSRV1> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001201204138G.yoka@qf6.so-net.ne.jp> Date: Fri, 01 Dec 2000 20:41:38 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Doug White Subject: Re: PXE boot problem. Date: Thu, 30 Nov 2000 20:18:26 -0800 (PST) > On Thu, 30 Nov 2000, Matt Simerson wrote: > > > Hi Folks, > > > > I've been trying hard to get a FreeBSD system booted via PXE with only > > limited success. Maybe someone can have a look at my configs and shed a > > little light on this for me. > > > > Here's what happens at boot time: > > > > Intel UNDI, PXE-2.0 (build 067) > > Problem #1: broken build. Flash your motherboard/card to the latest, > build 082. I have two Intel PRO/100+ Management Adapters with differnet versions of ROM. One is build 67, the other is build 78. Both work fine for me. > NFS is configured as follows: > > matt# more /etc/exports > / -alldirs -ro > /usr -alldirs -ro > /cdrom -alldirs -maproot=root -ro Perhaps, you can add /tftpboot in /etc/exports. Manabu Yokawa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 5:35:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hokkshideh.jetcafe.org (hokkshideh.jetcafe.org [205.147.43.4]) by hub.freebsd.org (Postfix) with ESMTP id D8F9037B400 for ; Fri, 1 Dec 2000 05:35:33 -0800 (PST) Received: from hokkshideh.jetcafe.org (localhost [127.0.0.1]) by hokkshideh.jetcafe.org (8.8.8/8.8.5) with ESMTP id FAA00423; Fri, 1 Dec 2000 05:35:31 -0800 (PST) Message-Id: <200012011335.FAA00423@hokkshideh.jetcafe.org> X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.4 #1[UCI] To: kstewart@urx.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: make buildworld fails Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Dec 2000 05:35:30 -0800 From: Dave Hayes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Stewart writes: > I did a cvsup build of 3 systems using 4-stable when it showed up as > 4.2-release. How did you install 4.2 and did you cvsup src-all. This is a 3.3-RELEASE system upgrading to 4.2, I did cvsup src-all, > You are dying building the gnu /binutils. Function mkstemps is a > function in the Standard C Library libc and is located at > /usr/src/contrib/binutils/libiberty/. It is almost like you are > missing a > ldconfig -R /usr/obj/usr/src/lib/libc > or libc doesn't exist because of the install. This could very well be. I am following the instructions in UPGRADING under "To update from 3.x to 4.x stable". ------ Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< There is no greater calamity for a nation or individual than not finding contentment in one's sufficiency. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 6:30:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id D234537B400 for ; Fri, 1 Dec 2000 06:30:33 -0800 (PST) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id GAA02015; Fri, 01 Dec 2000 06:30:29 -0800 Message-ID: <3A27B605.B2DFAE15@urx.com> Date: Fri, 01 Dec 2000 06:30:29 -0800 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Dave Hayes Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: make buildworld fails References: <200012011335.FAA00423@hokkshideh.jetcafe.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dave Hayes wrote: > > Kent Stewart writes: > > I did a cvsup build of 3 systems using 4-stable when it showed up as > > 4.2-release. How did you install 4.2 and did you cvsup src-all. > > This is a 3.3-RELEASE system upgrading to 4.2, I did cvsup src-all, > > > You are dying building the gnu /binutils. Function mkstemps is a > > function in the Standard C Library libc and is located at > > /usr/src/contrib/binutils/libiberty/. It is almost like you are > > missing a > > ldconfig -R /usr/obj/usr/src/lib/libc > > or libc doesn't exist because of the install. > > This could very well be. I am following the instructions in UPGRADING > under "To update from 3.x to 4.x stable". The general comment is that you have to be at 3.5 to do that. However, Engelshall had a process that worked for almost every concievable difficulty at 3.5 > 4.x. There were somethings fixed in the week or so after 4.2 was released and you might consider 4-stable. Some things in Engleshall's procedure are out of date such as mv'ing /MYKERNEL to /kernel but it touches on some of your problems. See http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=51796+57580+/usr/local/www/db/text/2000/freebsd-stable/20001015.freebsd-stable If you have to fight upgrading and making two worlds (3.5 and 4.2-R), a binary upgrade followed by making your world and kernel will be much faster. The 4.x buildworld just about requires 2x as long as a buildworld in 3.x. I use the buildworld sequence from /usr/src/UPDATING almost religiously because I cvsup everytime I do a build. I also like the idea of building everything before I start the installs. In my situation, I found that putting the process into a script would have everything built when I would go back to check on the status. Doing the individual steps typically left me at just the end of the buildworld. Kent > ------ > Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org > >>> The opinions expressed above are entirely my own <<< > > There is no greater calamity for a nation or individual > than not finding contentment in one's sufficiency. -- 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 Fri Dec 1 6:41:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 97BE837B400 for ; Fri, 1 Dec 2000 06:41:19 -0800 (PST) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id PAA04588 for ; Fri, 1 Dec 2000 15:41:17 +0100 (MET) Date: Fri, 1 Dec 2000 15:41:17 +0100 (CET) From: Harti Brandt To: hackers@freebsd.org Subject: Strange thing with serial console speed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have two machines running -current. One of them is configured for serial console and connected to the second one. On the 2nd one I usually build world and the kernels for the two machines. The I install world and the kernels from /usr/obj of the 2nd machine (exported via nfs). In principal this works just fine.... Except that I decided yesterday to raise the serial console speed to 115200 by putting the appropriate line into /etc/make.conf. I though, that this definition wouldn't matter for the machine without serial console. So I was really surprised to see, that that machine didn't boot anymore today. What happens is, that it prints the BTX loader version line, the cursor jumps to the upper left corner of the screen and there it stays until i press ctrl-alt-del or hit reset. Rebuilding /usr/src/sys/boot without the speed definition in /etc/make.conf fixes the problem. So, how is the serial console speed tangled to the non-serial console boot??? Is this a bug or a feature? Regards, harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org, lhbrandt@mail.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 8: 8:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from maybe.csap.af.mil (mudd.csap.af.mil [192.203.1.250]) by hub.freebsd.org (Postfix) with SMTP id A266237B400 for ; Fri, 1 Dec 2000 08:08:38 -0800 (PST) Received: from mailcenter.csap.af.mil(really [192.168.20.202]) by maybe.csap.af.mil via sendmail with smtp id for ; Fri, 1 Dec 2000 10:08:37 -0600 (CST) (Smail-3.2 1996-Jul-4 #5 built 1999-Sep-4) Received: from tds.com(really [192.168.70.97]) by mailcenter.csap.af.mil via sendmail with esmtp id for ; Fri, 1 Dec 2000 10:19:15 -0600 (CST) (Smail-3.2 1996-Jul-4 #1 built 1999-Sep-8) Message-ID: <3A27CBB8.D169CDF8@tds.com> Date: Fri, 01 Dec 2000 10:03:05 -0600 From: Carlos Garcia X-Mailer: Mozilla 4.72 [en] (X11; I; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.org, carlos_garcia@tds.com Subject: bpf and libpcap (freebsd packet capture) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hackers@freebsd.org: I have two questions that concern enhancing the freebsd packet capture. I am looking into doing some source code changes for bpf, libpcap, and the kernel, if necessary, to increase the performance of packet capture for a custom sniffer on a loaded network. Now what I read was increasing the bpf buffer size to 256K rather than the default 32K. Can we increase this more? Can you please help me or rather point me in the right direction. Question 1: It I want to increase the buffer size of the bpf which #define would I have to change? I found a few BUF variables. The reason is that I want to sniff on a loaded 100Mbs network without dropping any packets. I found these variables: bpf.c:#define BPF_BUFSIZE (MCLBYTES-8) bpf.c:#define BPF_BUFSIZE 4096 bpf.h:#define BPF_MAXBUFSIZE 0x8000 bpf.h:#define BPF_MINBUFSIZE 32 My guess is that it is the #define BPF_MINBUFSIZE 32 because I read that the default buffer is 32K and I want to change it to 256K. Is this the right variable to change? or do I have to change code of libpcap files: pcap-enet.c:#define BUFSPACE (4*1024) pcap-nit.c:#define BUFSPACE (4*CHUNKSIZE) pcap-pf.c:#define BUFSPACE (200 * 256) pcap-snit.c:#define BUFSPACE (4*CHUNKSIZE) pcap.h:#define PCAP_ERRBUF_SIZE 256 Question 2: It seems after my testing if you insert a very large bpf filter rule to the bpf device, it breaks. My testing involved filtering in a few services/ports and external traffic to and from about 20 different ips and to exclude any internal traffic of the 20, which I can't subnet because they are not grouped together. The filter rule grows extreming large, which I thinks overruns the stack or address space for bpf. Is there any default variable that can increase the actucal filter rule or filter rule buffer? My collegue, hack the number of instructions that is passed to pcap, but it still breaks it. Can you point me where to look in order to increase the filter rule. Thanks, Carlos R. Garcia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 8:54:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from milquetoast.cs.mcgill.ca (milquetoast.CS.McGill.CA [132.206.2.5]) by hub.freebsd.org (Postfix) with ESMTP id 1810437B401 for ; Fri, 1 Dec 2000 08:54:27 -0800 (PST) Received: (from mat@localhost) by milquetoast.cs.mcgill.ca (8.9.3/8.9.3) id LAA16900; Fri, 1 Dec 2000 11:54:03 -0500 (EST) Date: Fri, 1 Dec 2000 11:54:03 -0500 From: Mathew KANNER To: Matt Simerson Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: PXE boot problem. Message-ID: <20001201115403.A16154@cs.mcgill.ca> References: <8D18712B2604D411A6BB009027F644980DD7A0@0SEA01EXSRV1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: Matt Simerson's message [PXE boot problem.] as of Thu, Nov 30, 2000 at 05:42:22PM -0700 Organization: SOCS, McGill University, Montreal, CANADA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Nov 30, Matt Simerson wrote: > [...] > > Intel UNDI, PXE-2.0 (build 067) > Copyright (c) 1997, 1998 Intel Corporation > [...] Get the flash upgrade from intel. Mine reads: Intel(R) Boot Agent Version 4.0.14 and it works well. --Mat -- Mathew Kanner SOCS McGill University Obtuse quote: He [not me] understands: "This field of perception is void of perception of man." -- The Quintessence of Buddhism To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 9: 8:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8]) by hub.freebsd.org (Postfix) with ESMTP id 5441637B400 for ; Fri, 1 Dec 2000 09:08:52 -0800 (PST) Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9]) by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id JAA81324 for ; Fri, 1 Dec 2000 09:08:46 -0800 (PST) (envelope-from rh@matriplex.com) Date: Fri, 1 Dec 2000 09:08:46 -0800 (PST) From: Richard Hodges To: freebsd-hackers@FreeBSD.ORG Subject: Re: Per-process kernel stack size In-Reply-To: <200012010619.eB16JuF02371@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Nov 2000, Mike Smith wrote: > > The routines have a nesting of 10-12 functions having 10-100 lines each. > > Could you tell us what is the minimum available run time memory in the > > per-process kernel stack for running these routines? > You can generally assume that you have about 4k of kernel stack (you will > normally have more, but don't count on it 8). I'm sure this is pretty obvious, and has already occured to most everyone else, but... Wouldn't it be a simple matter to set a global pointer to the stack base (lowest address) when switching context, so that the running code could know exactly how close it is to the limits? Maybe this would not be used in release code, but could be another tool for auditing suspicious code. Even better, maybe the stack could be set on a non-contiguous virtual address so that any overflow would trigger a fault? I would *much* rather have the machine grind to a halt with a relevant message than see mysterious data corruption. Of course, neither of these would be worthwhile once I stop writing code with bugs ;-) All the best, -Richard ------------------------------------------- Richard Hodges | Matriplex, inc. | 769 Basque Way rh@matriplex.com | Carson City, NV 89706 775-886-6477 | www.matriplex.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 11:20:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id CE72037B401 for <hackers@FreeBSD.ORG>; Fri, 1 Dec 2000 11:20:35 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eB1JIol53670; Fri, 1 Dec 2000 11:18:50 -0800 (PST) (envelope-from dillon) Date: Fri, 1 Dec 2000 11:18:50 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> Message-Id: <200012011918.eB1JIol53670@earth.backplane.com> To: News History File User <newsuser@free-pr0n.netscum.dk> Cc: hackers@FreeBSD.ORG, usenet@tdk.net, soren@wasabisystems.com Subject: Re: vm_pageout_scan badness References: <200012011044.eB1Ai4353062@newsmangler.inet.tele.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Personally speaking, I would much rather use MAP_NOSYNC anyway, even with :> a fixed filesystem syncer. MAP_NOSYNC pages are not restricted by :... : :Yeah, no kidding -- here's what I see it screwing up. First, some :background: : :I've built three news machines, two transit boxen and one reader box, :with recent INN k0dez, and 4.2-STABLE of a few days ago (having tested :NetBSD, more on that later), and a brief detour into 5-current. :.. : :Everything starts out well, where the history disk is beaten at startup :but as time passes, the time taken to do lookups and writes drops down :to near-zero levels, and the disk gets quiet. And actually, the transit :... : :What I notice is that the amount of memory used keeps increasing, until :it's all used, and the Free amount shown by `top' drops to a meg or so. :Cache and Buf get a bit, but most of it is Active. Far more than is :accounted for by the processes. This is to be expected, because the dirty MAP_NOSYNC pages will not be written out until they are forced out, or by msync(). :Now, what happens on the reader machine is that after some time of the :Active memory increasing, it runs out and starts to swap out processes, :and the timestamps on the history database files (.index and .hash, this :is the md5-based history) get updated, rather than remaining at the :time INN is started. Then the rapid history times skyrocket until it :takes more than 1/4 of the time. I don't see this on the transit boxen :even after days of operation. Hmm. That doesn't sound right. Free memory should drop to near zero, but then what should happen is the pageout daemon should come along and deactivate a big chunk of the 'active' pages... so you should see a situation where you have, say, 200MB worth of active pages and 200MB worth of inactive pages. After that the pageout daemon should start paging out the inactive pages and increasing the 'cache'. The number of 'free' pages will always be near zero, which is to be expected. But it should not be swapping out any process. The actual amount of 'free' memory in the system is actually 'free+cache' pages. :Now, what happens when I stop INN and everything news-related is that :some memory is freed up, but still, there can be, say, 400MB still :reported as Active. More when I had a full gig in this machine to :... : :Then, when I reboot the machine, it gives the kernel messages about :syncing disks; done, and then suddenly the history drive light goes :on and it starts grinding for five minutes or so, before the actual :reboot happens. Right. This is to be expected. You have a lot of dirty pages in the system due to the use of MAP_NOSYNC that have to be flushed out. :No history activity happens when I shut down INN normally, which should :free the MAP_NOSYNC'ed pages and make them available to be written to :disk before rebooting, maybe. MAP_NOSYNC pages are not flushed when the referencing program exits. They stick around until they are forced out. You can flush them manually by using a mmap()/msync() combination. i.e. an msync() prior to munmap()ing (from INND only) ought to do it. :What I think is happening, based on these observations, is that the :data from the history hash files (less than 100MB) gets read into :memory, but the updates to it are not written over the data to be :replaced -- it's simply appended to, up to the limit of the available :memory. When this limit is reached on the transit machines, then :things stabilize and old pages get recycled (but still, more memory :overall is used than the size of the actual file). It doesn't append... the pages are reused. The set of 'active' pages in the VM system is effectively the set of all files accessed for the entire system, not just MAP_NOSYNC pages. If you are only MAP_NOSYNC'ing 100MB worth of pages, then only 100MB worth of pages will be left unflushed. Is it possible that history file rewriting is creating an issue? Doesn't INN rewrite the history file every once in a while to clear out old garbage? I'm not up on the latest INN. :I'm guessing that additional activity of the reader machine causes :jumps in memory usage not seen on the transit machines, that is enough :to force some of the unwritten dirty pages to be written to the :history file, as a few megs of swap get used, which is why it does :not stabilize as `nicely' as the transit machines. This makes sense... the amount of swap that gets used is critical. If we are talking about only a few megabytes, then your system is *not* swapping significantly, it is simply swapping out completely idle pages from things like idle getty's and such. This is a good thing. The disk activity would thus be mostly due to MAP_NOSYNC pages being written out. :Now, something I contemplated -- it seems that Bad Undesirable Things :happen as soon as I start to actually swap, that I'd prefer to avoid. :What I'm wondering is if I can avoid this by adjusting some of the :values I see in `top' for Cache, Buf, and most importantly, Free. :May I ask where (in which source file) these ratios or limits or :whatever are set? I'm hoping I can up the `Free' limit to a few :dozen megs to give headroom before actual swapping happens, since :now the Free value is a meg or two out of, oh, a gig available... : :Anyway, once this happens, performance sucks rocks, the history :drive light is enough to read by (or should I say, it keeps me from :getting much-needed sleep), and apparently only a reboot can free :up memory for better purposes. : :I've also only a small margin of memory headroom on the transit :machines, but much more on the reader machine, that can benefit :from cache far more, in case this makes any difference. But I think :I also saw this steady increase when I first started with something :like 256M. Well, the performance sucking part means something is not working as designed. The question is what. :I just now noticed that you made a patch available just over a month :ago; I'm not sure if it would affect what I'm seeing here at all, or :if it's already in the recent source I've built. I committed a number of patches just after 4.2-REL. Your recent system may or may not have them. Here is what I would recommend. First, I would use 'systat -vm 1' and carefully examine the pageout/swapout activity. If the SWAP PAGER has no significant activity then we can discard it as a possible problem. If the VN PAGER has significant activity, then this is what we need to focus on. I would try changing the pageout and VM cache parameters. Do NOT mess with the VM free parameters! Try changing the vm.v_cache_min and vm.v_cache_max parameters. For example, increase vm.v_cache_max to widen the hysteresis. You can slo try changing vm.pageout_algorithm from 0 to 1 (this is not likely to have much of an effect), and you can also try increasing vm.max_page_launder, e.g. from 32 to 100 (much larger would not have any effect). Finally, you can try increasing the vm.v_inactive_target. Do not increase the vm.v_free_target. Do NOT mess with any of the v_*free* sysctl's, not unless you want to destabilize your box! Last thing: Using MAP_NOSYNC has a well known problem when used to fill 'holes' in files. That is, if the history file is being appended to by calling ftruncate(), but the new space is not write()n to and instead is dirtied via the mmap, you will have a serious fragmentation problem with the file. In order to avoid this problem any file appends should occur using write() if possible, or the newly allocated space in the file should be filled with zero's using write() prior to being random-accessed by mmap() (which might be easier to implement). -Matt :And, in an earlier message in this thread, concerning something :related but different as far as I can make out: : :disclaimer: i really don't know what I'm talking about, so be gentle :when flaming me, thanks :(reply-to header is valid) :barry bouwsma, thwarted in all my attempts to build a good readerbox To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 11:56:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 0955E37B400; Fri, 1 Dec 2000 11:56:37 -0800 (PST) Received: (from alc@localhost) by cs.rice.edu (8.9.0/8.9.0) id NAA08944; Fri, 1 Dec 2000 13:56:34 -0600 (CST) Date: Fri, 1 Dec 2000 13:56:34 -0600 From: Alan Cox <alc@cs.rice.edu> To: Alfred Perlstein <bright@wintelcom.net> Cc: alc@freebsd.org, hackers@freebsd.org Subject: Re: why doesn't aio use at_exit(9)? Message-ID: <20001201135634.D26574@cs.rice.edu> References: <20001201020257.R8051@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5us In-Reply-To: <20001201020257.R8051@fw.wintelcom.net>; from Alfred Perlstein on Fri, Dec 01, 2000 at 02:02:58AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 01, 2000 at 02:02:58AM -0800, Alfred Perlstein wrote: > why doesn't aio use at_exit(9) instead of requiring an explicit > call in kern_exit.c for aio_rundown? > There's no reason that I'm aware of. Unless you're in a hurry, I'll add that change to a cleanup patch that I have in the pipe. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 12: 8:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E9AF437B400; Fri, 1 Dec 2000 12:08:49 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eB1K8m224944; Fri, 1 Dec 2000 12:08:48 -0800 (PST) Date: Fri, 1 Dec 2000 12:08:48 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Alan Cox <alc@cs.rice.edu> Cc: alc@freebsd.org, hackers@freebsd.org Subject: Re: why doesn't aio use at_exit(9)? Message-ID: <20001201120848.C8051@fw.wintelcom.net> References: <20001201020257.R8051@fw.wintelcom.net> <20001201135634.D26574@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001201135634.D26574@cs.rice.edu>; from alc@cs.rice.edu on Fri, Dec 01, 2000 at 01:56:34PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Alan Cox <alc@cs.rice.edu> [001201 11:56] wrote: > On Fri, Dec 01, 2000 at 02:02:58AM -0800, Alfred Perlstein wrote: > > why doesn't aio use at_exit(9) instead of requiring an explicit > > call in kern_exit.c for aio_rundown? > > > > There's no reason that I'm aware of. Unless you're in a hurry, > I'll add that change to a cleanup patch that I have in the pipe. Er, how much of a cleanup do you have? The only work I've done so far is to remove all the #ifdef VFS_AIO's in the file, if you could commit your cleanup soon it would help. :) thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 12:21:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id B7CB737B400; Fri, 1 Dec 2000 12:21:27 -0800 (PST) Received: (from alc@localhost) by cs.rice.edu (8.9.0/8.9.0) id OAA10454; Fri, 1 Dec 2000 14:21:26 -0600 (CST) Date: Fri, 1 Dec 2000 14:21:26 -0600 From: Alan Cox <alc@cs.rice.edu> To: Alfred Perlstein <bright@wintelcom.net> Cc: alc@freebsd.org, hackers@freebsd.org Subject: Re: why doesn't aio use at_exit(9)? Message-ID: <20001201142126.E26574@cs.rice.edu> References: <20001201020257.R8051@fw.wintelcom.net> <20001201135634.D26574@cs.rice.edu> <20001201120848.C8051@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5us In-Reply-To: <20001201120848.C8051@fw.wintelcom.net>; from Alfred Perlstein on Fri, Dec 01, 2000 at 12:08:48PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 01, 2000 at 12:08:48PM -0800, Alfred Perlstein wrote: > * Alan Cox <alc@cs.rice.edu> [001201 11:56] wrote: > > On Fri, Dec 01, 2000 at 02:02:58AM -0800, Alfred Perlstein wrote: > > > why doesn't aio use at_exit(9) instead of requiring an explicit > > > call in kern_exit.c for aio_rundown? > > > > > > > There's no reason that I'm aware of. Unless you're in a hurry, > > I'll add that change to a cleanup patch that I have in the pipe. > > Er, how much of a cleanup do you have? The only work I've done > so far is to remove all the #ifdef VFS_AIO's in the file, if you > could commit your cleanup soon it would help. :) > If you're already working on converting aio to use at_exit, go ahead. It won't interfere with my work. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 12:25:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 8CC9E37B400; Fri, 1 Dec 2000 12:25:46 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eB1KPgR25558; Fri, 1 Dec 2000 12:25:42 -0800 (PST) Date: Fri, 1 Dec 2000 12:25:42 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Alan Cox <alc@cs.rice.edu> Cc: alc@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: why doesn't aio use at_exit(9)? Message-ID: <20001201122542.E8051@fw.wintelcom.net> References: <20001201020257.R8051@fw.wintelcom.net> <20001201135634.D26574@cs.rice.edu> <20001201120848.C8051@fw.wintelcom.net> <20001201142126.E26574@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001201142126.E26574@cs.rice.edu>; from alc@cs.rice.edu on Fri, Dec 01, 2000 at 02:21:26PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Alan Cox <alc@cs.rice.edu> [001201 12:21] wrote: > On Fri, Dec 01, 2000 at 12:08:48PM -0800, Alfred Perlstein wrote: > > * Alan Cox <alc@cs.rice.edu> [001201 11:56] wrote: > > > On Fri, Dec 01, 2000 at 02:02:58AM -0800, Alfred Perlstein wrote: > > > > why doesn't aio use at_exit(9) instead of requiring an explicit > > > > call in kern_exit.c for aio_rundown? > > > > > > > > > > There's no reason that I'm aware of. Unless you're in a hurry, > > > I'll add that change to a cleanup patch that I have in the pipe. > > > > Er, how much of a cleanup do you have? The only work I've done > > so far is to remove all the #ifdef VFS_AIO's in the file, if you > > could commit your cleanup soon it would help. :) > > > > If you're already working on converting aio to use at_exit, > go ahead. It won't interfere with my work. I plan to make it a kld module, like i just did with sysvipc. > > Alan > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 12:56:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orthanc.ab.ca (207-167-15-66.dsl.worldgate.ca [207.167.15.66]) by hub.freebsd.org (Postfix) with ESMTP id 58B3337B400; Fri, 1 Dec 2000 12:56:20 -0800 (PST) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.11.1/8.11.0.Beta3) with ESMTP id eB1KuDI32343; Fri, 1 Dec 2000 13:56:14 -0700 (MST) Message-Id: <200012012056.eB1KuDI32343@orthanc.ab.ca> To: hackers@freebsd.org, stable@freebsd.org Reply-To: hackers@freebsd.org Subject: PCIOCGETCONF/PCIOCREAD requires write permission? Organization: The Frobozz Magic Homing Pigeon Company Date: Fri, 01 Dec 2000 13:56:13 -0700 From: Lyndon Nerenberg <lyndon@orthanc.ab.ca> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Observed on 4.2-STABLE, but I've redirected replies to the hackers list.] 'pciconf -l' is documented to work for non-priv users, however the first thing the underlying ioctl code (pci_ioctl) does is bail with EPERM if the caller does not have /dev/pci open for write. Is there any reason why the FWRITE test cannot/should not be moved down into the 'case PCIOCWRITE' part of the switch? This would make both PCIOCGETCONF and PCIOCREAD work for readonly access to /dev/pci (which seems to me to be saner behaviour). --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 15:11: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id E324137B69B for <freebsd-hackers@freebsd.org>; Fri, 1 Dec 2000 15:11:00 -0800 (PST) Received: from server.wes.mee.com (pC19EB3B1.dip.t-dialin.net [193.158.179.177]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id AAA06184 for <freebsd-hackers@freebsd.org>; Sat, 2 Dec 2000 00:11:03 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by server.wes.mee.com (8.11.0/8.11.0) with ESMTP id eAUJPFt20517 for <freebsd-hackers@freebsd.org>; Thu, 30 Nov 2000 20:25:15 +0100 (CET) (envelope-from frederik@freddym.org) Date: Thu, 30 Nov 2000 20:25:15 +0100 (CET) From: Frederik Meerwaldt <frederik@freddym.org> X-Sender: frederik@server.wes.mee.com To: freebsd-hackers@freebsd.org Subject: natd bug Message-ID: <Pine.BSF.4.21.0011302021590.20212-100000@server.wes.mee.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there! I was just looking why my natd doesnt work, when I discovered the following bug (?): I compiled my kernel with IPDIVERT IPFIREWALL and IPFIREWALL_DEFAULT_TO_ACCEPT and I set up only one rule: ipfw add divert natd all from any to any via isp0 Then I started natd (at boot time): natd -unregistered_only -dynamic -n isp0 But when a package arrives (doesn't matter from localhost or another host), natd gives out a kernel message: Nov 30 15:03:06 server natd[195]: failed to write packet back (Permission denied) What does that mean? I started natd from my rc.local, so it runs as root and it should have all permissions. Thanks in advance! Best Regards, Freddy -- Geek Code 3.1: GCS s+: a--- C+++ UBOU+++ P-- E--- W++ N w--- V++ PGP- t? 5? tv ===================================================================== Frederik Meerwaldt ICQ: 83045387 Homepage: http://www.freddym.org Bavaria/Germany OpenVMS and Unix Howtos and much more FreeBSD, NetBSD, OpenBSD, Tru64, OpenVMS, Ultrix, BeOS, Linux To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 15:14:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from minerva.springer.cx (cgmd77002.chello.nl [212.83.77.2]) by hub.freebsd.org (Postfix) with SMTP id D419D37B400 for <freebsd-hackers@freebsd.org>; Fri, 1 Dec 2000 15:14:07 -0800 (PST) Received: (qmail 9661 invoked from network); 2 Dec 2000 00:11:55 -0000 Received: from aurum.rinkspringer.org (HELO aurum) (172.16.0.2) by minerva.springer.cx with SMTP; 2 Dec 2000 00:11:55 -0000 Message-ID: <000901c05c50$f9a568c0$020010ac@aurum> From: "Rink Springer" <rink@springer.cx> To: "Frederik Meerwaldt" <frederik@freddym.org>, <freebsd-hackers@freebsd.org> References: <Pine.BSF.4.21.0011302021590.20212-100000@server.wes.mee.com> Subject: Re: natd bug Date: Sat, 2 Dec 2000 12:14:02 +0100 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.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, What are your firewall settings? Most likely, it's denying natd packets to pass, you need a special rule for that, like: # ipfw add divert natd all from any to any via isp0 That'll do the trick. --Rink ----- Original Message ----- From: "Frederik Meerwaldt" <frederik@freddym.org> To: <freebsd-hackers@freebsd.org> Sent: Thursday, November 30, 2000 8:25 PM Subject: natd bug > Hi there! > > I was just looking why my natd doesnt work, when I discovered the > following bug (?): > > I compiled my kernel with IPDIVERT IPFIREWALL and > IPFIREWALL_DEFAULT_TO_ACCEPT and I set up only one rule: > ipfw add divert natd all from any to any via isp0 > Then I started natd (at boot time): > natd -unregistered_only -dynamic -n isp0 > But when a package arrives (doesn't matter from localhost or another > host), natd gives out a kernel message: > > Nov 30 15:03:06 server natd[195]: failed to write packet back (Permission > denied) > > What does that mean? I started natd from my rc.local, so it runs as root > and it should have all permissions. > > Thanks in advance! > Best Regards, > Freddy > > -- > Geek Code 3.1: GCS s+: a--- C+++ UBOU+++ P-- E--- W++ N w--- V++ PGP- t? 5? tv > > ===================================================================== > Frederik Meerwaldt ICQ: 83045387 Homepage: http://www.freddym.org > Bavaria/Germany OpenVMS and Unix Howtos and much more > FreeBSD, NetBSD, OpenBSD, Tru64, OpenVMS, Ultrix, BeOS, Linux > > > > 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 Dec 1 15:39: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 0FE8E37B6B7 for <freebsd-hackers@freebsd.org>; Fri, 1 Dec 2000 15:23:46 -0800 (PST) Received: from server.wes.mee.com (p3E9C0338.dip.t-dialin.net [62.156.3.56]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id AAA18966; Sat, 2 Dec 2000 00:23:48 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by server.wes.mee.com (8.11.0/8.11.0) with ESMTP id eB1NJtD02441; Sat, 2 Dec 2000 00:19:55 +0100 (CET) (envelope-from frederik@freddym.org) Date: Sat, 2 Dec 2000 00:19:55 +0100 (CET) From: Frederik Meerwaldt <frederik@freddym.org> X-Sender: frederik@server.wes.mee.com To: Rink Springer <rink@springer.cx> Cc: freebsd-hackers@freebsd.org Subject: Re: natd bug In-Reply-To: <000901c05c50$f9a568c0$020010ac@aurum> Message-ID: <Pine.BSF.4.21.0012020019230.2375-100000@server.wes.mee.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! > # ipfw add divert natd all from any to any via isp0 I have exactly this line in my config (see my original posting) Best Regards, Freddy -- Geek Code 3.1: GCS s+: a--- C+++ UBOU+++ P-- E--- W++ N w--- V++ PGP- t? 5? tv ===================================================================== Frederik Meerwaldt ICQ: 83045387 Homepage: http://www.freddym.org Bavaria/Germany OpenVMS and Unix Howtos and much more FreeBSD, NetBSD, OpenBSD, Tru64, OpenVMS, Ultrix, BeOS, Linux To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 15:39: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 7F49237B6B9 for <freebsd-hackers@freebsd.org>; Fri, 1 Dec 2000 15:24:05 -0800 (PST) Received: (qmail 18272 invoked by uid 0); 1 Dec 2000 23:24:03 -0000 Received: from p3ee21442.dip.t-dialin.net (HELO forge.local) (62.226.20.66) by mail.gmx.net (mail03) with SMTP; 1 Dec 2000 23:24:03 -0000 Received: from thomas by forge.local with local (Exim 3.16 #1 (Debian)) id 141zVW-0000h4-00 for <freebsd-hackers@freebsd.org>; Sat, 02 Dec 2000 00:22:22 +0100 Date: Sat, 2 Dec 2000 00:22:22 +0100 To: freebsd-hackers@freebsd.org Subject: Re: natd bug Message-ID: <20001202002222.A2616@crow.dom2ip.de> Mail-Followup-To: tmoestl@gmx.net, freebsd-hackers@freebsd.org References: <Pine.BSF.4.21.0011302021590.20212-100000@server.wes.mee.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <Pine.BSF.4.21.0011302021590.20212-100000@server.wes.mee.com>; from frederik@freddym.org on Thu, Nov 30, 2000 at 08:25:15PM +0100 From: Thomas Moestl <tmoestl@gmx.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 30, 2000 at 08:25:15PM +0100, Frederik Meerwaldt wrote: > I compiled my kernel with IPDIVERT IPFIREWALL and > IPFIREWALL_DEFAULT_TO_ACCEPT and I set up only one rule: > ipfw add divert natd all from any to any via isp0 > Then I started natd (at boot time): > natd -unregistered_only -dynamic -n isp0 > But when a package arrives (doesn't matter from localhost or another > host), natd gives out a kernel message: > > Nov 30 15:03:06 server natd[195]: failed to write packet back (Permission > denied) Is your link up at that time? The usual setup for a sppp device using dynamic ip's is an invalid ip (0.0.0.0) that is changed once an ip was assigned. So, if you are not dialled in, the invalid ip will be put in by natd, and that usually causes this error message. - Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 15:53:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id E27CD37B400 for <hackers@FreeBSD.org>; Fri, 1 Dec 2000 15:53:14 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eB1Nr0C18614 for <hackers@FreeBSD.org>; Fri, 1 Dec 2000 15:53:00 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: <XFMail.001201155328.jhb@FreeBSD.org> 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: Fri, 01 Dec 2000 15:53:28 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: hackers@FreeBSD.org Subject: thr_sleep() and thr_wakeup() Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can we kill these syscalls? They are not used anywhere in the kernel and although they have wrapper functions in libc, no header contains prototypes for these wrappers. According to the CVS log they were originally brought in for POSIX threads and AIO, neither of which use this facility. Comments? -- John Baldwin <jhb@FreeBSD.org> -- 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 Fri Dec 1 15:59:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relayout1.micronpc.com (meihost.micronpc.com [209.19.139.2]) by hub.freebsd.org (Postfix) with ESMTP id 8DE6E37B400 for <freebsd-hackers@freebsd.org>; Fri, 1 Dec 2000 15:59:44 -0800 (PST) Received: from mei00wssout01.micron.com (mei00wssout01.micronpc.com [172.30.41.216]) by relayout1.micronpc.com (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with SMTP id QAA15562; Fri, 01 Dec 2000 16:59:37 -0700 Received: from 172.30.41.146 by mei00wssout01.micron.com with ESMTP ( WorldSecure Server SMTP Relay(WSS) v4.5); Fri, 01 Dec 2000 16:59:39 -0700 X-Server-Uuid: 6b1d535a-5b27-11d3-bf09-00902786a6a3 Received: by imcout1.micronpc.com with Internet Mail Service ( 5.5.2650.21) id <X6KX18FJ>; Fri, 1 Dec 2000 16:59:38 -0700 Message-ID: <8D18712B2604D411A6BB009027F644980DD7A6@0SEA01EXSRV1> From: "Matt Simerson" <mpsimerson@hostpro.com> To: "'Mathew KANNER'" <mat@cs.mcgill.ca> Cc: "'freebsd-hackers@freebsd.org'" <freebsd-hackers@freebsd.org> Subject: RE: PXE boot problem. - SOLVED Date: Fri, 1 Dec 2000 16:59:28 -0700 X-Mailer: Internet Mail Service (5.5.2650.21) MIME-Version: 1.0 X-WSS-ID: 1636E4E1305871-01-01 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That was it. Updating the flash on the Intel NIC and she booted right up. Thanks, Matt > -----Original Message----- > From: Mathew KANNER [mailto:mat@cs.mcgill.ca] > Sent: Friday, December 01, 2000 8:54 AM > To: Matt Simerson > Cc: 'freebsd-hackers@freebsd.org' > Subject: Re: PXE boot problem. > > > On Nov 30, Matt Simerson wrote: > > [...] > > > > Intel UNDI, PXE-2.0 (build 067) > > Copyright (c) 1997, 1998 Intel Corporation > > [...] > > > Get the flash upgrade from intel. > > Mine reads: > Intel(R) Boot Agent Version 4.0.14 > > and it works well. > > --Mat > > > -- > Mathew Kanner <mat@CS.McGill.CA> SOCS McGill University > Obtuse quote: He [not me] understands: "This field of perception > is void of perception of man." -- The Quintessence of Buddhism > > > 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 Dec 1 16:44:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 62AA537B400; Fri, 1 Dec 2000 16:44:12 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA17190; Fri, 1 Dec 2000 17:44:08 -0700 (MST) (envelope-from ken) Date: Fri, 1 Dec 2000 17:44:08 -0700 From: "Kenneth D. Merry" <ken@kdm.org> To: hackers@FreeBSD.ORG Cc: stable@FreeBSD.ORG Subject: Re: PCIOCGETCONF/PCIOCREAD requires write permission? Message-ID: <20001201174408.A17122@panzer.kdm.org> References: <200012012056.eB1KuDI32343@orthanc.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200012012056.eB1KuDI32343@orthanc.ab.ca>; from lyndon@orthanc.ab.ca on Fri, Dec 01, 2000 at 01:56:13PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 01, 2000 at 13:56:13 -0700, Lyndon Nerenberg wrote: > [Observed on 4.2-STABLE, but I've redirected replies to the hackers list.] > > 'pciconf -l' is documented to work for non-priv users, however the > first thing the underlying ioctl code (pci_ioctl) does is bail with EPERM > if the caller does not have /dev/pci open for write. The documentation is wrong, unfortunately. > Is there any reason why the FWRITE test cannot/should not be moved down > into the 'case PCIOCWRITE' part of the switch? This would make both > PCIOCGETCONF and PCIOCREAD work for readonly access to /dev/pci (which > seems to me to be saner behaviour). At least with the PCIOCGETCONF, you need write permission, because it copies in patterns to match against. As for PCIOCREAD, it only allows reading of PCI registers, so the question there is whether there are any potential security implications to allowing non-root users to read PCI registers. If reading configuration registers caused performance degredation, for instance. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 16:46: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from io.yi.org (unknown [24.70.218.157]) by hub.freebsd.org (Postfix) with ESMTP id 564D437B402; Fri, 1 Dec 2000 16:46:05 -0800 (PST) Received: from io.yi.org (localhost.gvcl1.bc.wave.home.com [127.0.0.1]) by io.yi.org (Postfix) with ESMTP id 1BA5EBA7C; Fri, 1 Dec 2000 16:46:05 -0800 (PST) X-Mailer: exmh version 2.1.1 10/15/1999 To: John Baldwin <jhb@FreeBSD.ORG> Cc: hackers@FreeBSD.ORG Subject: Re: thr_sleep() and thr_wakeup() In-Reply-To: Message from John Baldwin <jhb@FreeBSD.ORG> of "Fri, 01 Dec 2000 15:53:28 PST." <XFMail.001201155328.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Dec 2000 16:46:04 -0800 From: Jake Burkholder <jburkhol@home.com> Message-Id: <20001202004605.1BA5EBA7C@io.yi.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can we kill these syscalls? They are not used anywhere in the kernel and > although they have wrapper functions in libc, no header contains prototypes for > these wrappers. According to the CVS log they were originally brought in for > POSIX threads and AIO, neither of which use this facility. Comments? > Seconded. I see no reason for keeping these. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 16:58:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 468C037B400; Fri, 1 Dec 2000 16:58:50 -0800 (PST) Received: from holly.calldei.com ([208.191.149.190]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0G4X00I8H1CZKW@mta4.rcsntx.swbell.net>; Fri, 1 Dec 2000 18:58:12 -0600 (CST) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id SAA05635; Fri, 01 Dec 2000 18:58:52 -0600 (CST envelope-from chris) Date: Fri, 01 Dec 2000 18:58:41 -0600 From: Chris Costello <chris@calldei.com> Subject: Re: thr_sleep() and thr_wakeup() In-reply-to: <XFMail.001201155328.jhb@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.ORG> Cc: hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20001201185841.A899@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <XFMail.001201155328.jhb@FreeBSD.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, December 01, 2000, John Baldwin wrote: > Can we kill these syscalls? They are not used anywhere in the kernel and > although they have wrapper functions in libc, no header contains prototypes for > these wrappers. According to the CVS log they were originally brought in for > POSIX threads and AIO, neither of which use this facility. Comments? Agreed. Also, this is UNIX International thread namespace (thr_*). -- |Chris Costello <chris@calldei.com> |Your e-mail has been returned due to insufficient voltage. `---------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 18:44:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from io.yi.org (unknown [24.70.218.157]) by hub.freebsd.org (Postfix) with ESMTP id BE67F37B400; Fri, 1 Dec 2000 18:44:52 -0800 (PST) Received: from io.yi.org (localhost.gvcl1.bc.wave.home.com [127.0.0.1]) by io.yi.org (Postfix) with ESMTP id 84996BA7C; Fri, 1 Dec 2000 18:44:52 -0800 (PST) X-Mailer: exmh version 2.1.1 10/15/1999 To: chris@calldei.com Cc: John Baldwin <jhb@FreeBSD.ORG>, hackers@FreeBSD.ORG Subject: Re: thr_sleep() and thr_wakeup() In-Reply-To: Message from Chris Costello <chris@calldei.com> of "Fri, 01 Dec 2000 18:58:41 CST." <20001201185841.A899@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Dec 2000 18:44:52 -0800 From: Jake Burkholder <jburkhol@home.com> Message-Id: <20001202024452.84996BA7C@io.yi.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Friday, December 01, 2000, John Baldwin wrote: > > Can we kill these syscalls? They are not used anywhere in the kernel and > > although they have wrapper functions in libc, no header contains prototypes for > > these wrappers. According to the CVS log they were originally brought in for > > POSIX threads and AIO, neither of which use this facility. Comments? > > Agreed. Also, this is UNIX International thread namespace > (thr_*). > Interesting. Ok, if these system calls are going to be removed the whole file may as well be removed, since then it would just have yield in it. John and I agree that kern_synch.c is probably as good a place as any for yield, but there may be a better place. Thoughts? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 21:25:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from newsmangler.inet.tele.dk (nntp118.netscum.dk [193.162.153.118]) by hub.freebsd.org (Postfix) with ESMTP id 593AC37B402 for <hackers@freebsd.org>; Fri, 1 Dec 2000 21:25:36 -0800 (PST) Received: (from news@localhost) by newsmangler.inet.tele.dk (8.11.1/8.11.1) id eB25PPQ92768; Sat, 2 Dec 2000 06:25:25 +0100 (CET) (envelope-from newsuser@free-pr0n.netscum.dk) Date: Sat, 2 Dec 2000 06:25:25 +0100 (CET) Message-Id: <200012020525.eB25PPQ92768@newsmangler.inet.tele.dk> X-Authentication-Warning: newsmangler.inet.tele.dk: news set sender to newsuser@free-pr0n.netscum.dk using -f From: News History File User <newsuser@free-pr0n.netscum.dk> Reply-To: freebsd-user@netscum.dk To: hackers@freebsd.org, dillon@earth.backplane.com Subject: Re: vm_pageout_scan badness Cc: usenet@tdk.net References: <200012011918.eB1JIol53670@earth.backplane.com> In-Reply-To: <200012011918.eB1JIol53670@earth.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :> Personally speaking, I would much rather use MAP_NOSYNC anyway, > even with > :... > :Everything starts out well, where the history disk is beaten at startup > :but as time passes, the time taken to do lookups and writes drops down > :to near-zero levels, and the disk gets quiet. And actually, the transit > :... > :What I notice is that the amount of memory used keeps increasing, until > :it's all used, and the Free amount shown by `top' drops to a meg or so. > :Cache and Buf get a bit, but most of it is Active. Far more than is > :accounted for by the processes. > > This is to be expected, because the dirty MAP_NOSYNC pages will not > be written out until they are forced out, or by msync(). I just discovered the user command `fsync' which has revealed a few things to me, clearing up some mysteries. Also, I've watched more closely the pattern of what happens to the available memory following a fresh boot... At the moment, this (reader) machine has been up for half a day, with performance barely able to keep up with a full feed (but starting to slip as the overnight burst of binaries is starting), but at last look, history lookups and writes are accounting for more than half (!) of the INN news process time, with available idle time being essentially zero. So... > :Now, what happens on the reader machine is that after some time of the > :Active memory increasing, it runs out and starts to swap out processes, > :and the timestamps on the history database files (.index and .hash, this > :is the md5-based history) get updated, rather than remaining at the > :time INN is started. Then the rapid history times skyrocket until it > :takes more than 1/4 of the time. I don't see this on the transit boxen > :even after days of operation. > > Hmm. That doesn't sound right. Free memory should drop to near zero, > but then what should happen is the pageout daemon should come along > and deactivate a big chunk of the 'active' pages... so you should > see a situation where you have, say, 200MB worth of active pages > and 200MB worth of inactive pages. After that the pageout daemon > should start paging out the inactive pages and increasing the 'cache'. > The number of 'free' pages will always be near zero, which is to be > expected. But it should not be swapping out any process. Here is what I noticed while watching the `top' values for Active, Inactive, and Free following this last boot (I didn't pay any attention to the other fields to notice any wild fluctuations there, next time maybe), on this machine with 512MB of RAM, if it reveals anything: Following the boot, things start out with plenty of memory Free, and something like 4MB Active, which seems reasonable to me. Then I start things. As is to be expected, INN increases in size as it does history lookups and updates, and the amount of memory shown as Active tracks this, more or less. But what's happening to the Free value! It's going down at as much as 4MB per `top' interval. Or should I say, what is happening to the Inactive value -- it's constantly increasing, and I observe a rapid migration of all the Free memory to Inactive, until the value of Inactive peaks out at the time that Free drops to about 996k, beyond which it changes little. None of the swap space has been touched yet. As soon as the value for Free hits bottom and that of Inactive has reached a max, now the migration happens from Inactive to Active -- until this point, the value of Active has been roughly what I would expect to see, given the size of the history hash/index files, and the BerkeleyDB file I'm now using MAP_NOSYNC as well for a definite improvement in overview access times. Anyway, I don't remember what values exactly I was seeing for Free and Inactive or Active, since I was just watching for general trends, but I seem to recall Active being ~100MB, and Inactive somewhat more. (Are you saying above that this Inactive value should be migrating to Cache, which I'm not seeing, rather than to Active, which I do see? If so, then hmmm.) Now memory is drifting at a fairly rapid pace from Inactive (the meaning of which I'm not exactly clear about, although there's some explanation in the `top' man page that hasn't quite clicked into understanding yet), over to the Active field, at something like 2MB or so per `top' interval. Free remains close to 1MB, but Active is constantly growing, although no processes are clearly taking up any of this, apart from INN which only accounts for around 100MB at this time, and isn't increasing at the rate of increase of Active memory. Anyway, the Active field continues to increase as Inactive decreases until finally Inactive bottoms out, down from several hundred MB to a one or two digit MB value (I don't remember exactly), while Active has increased to almost 400MB. This is something like 20 minutes after the reboot, and now the first bit of swap gets hit. However, the value of Active has hit its peak and resting value, ~400MB with 512MB RAM, and I recall it being about 800-something with a full GB; Inactive varies some number of MB either side of 10MB, Free stays near 1MB, Cache seems to be between 10 and 20MB, Buf is about 60, and wired is around 76MB. The amount of swap has increased over time, from half a meg where it was for some time after being hit, up to 18MB now. It periodically sees some activity. The RES size of innd is ~120MB, it has a 108MB .hash and 72MB .index file, both NOSYNC. I'm considering recompiling INN and BerkeleyDB without the MAP_NOSYNC to see what the reference level of history and overview access time and lockups during updates are, as well as the values of memory usage in that case, to see if the suspicions I have are correct or if I need to look elsewhere. > The actual amount of 'free' memory in the system is actually 'free+cache' > pages. > > :Now, what happens when I stop INN and everything news-related is that > :some memory is freed up, but still, there can be, say, 400MB still > :reported as Active. More when I had a full gig in this machine to > :... > : > :Then, when I reboot the machine, it gives the kernel messages about > :syncing disks; done, and then suddenly the history drive light goes > :on and it starts grinding for five minutes or so, before the actual > :reboot happens. > > Right. This is to be expected. You have a lot of dirty pages > in the system due to the use of MAP_NOSYNC that have to be flushed > out. Yep, doing research and reading man pages and watching closely *after* I sent the last mail, not before, has opened my eyes to a few things. And as I noted, manually `fsync /news/db/history.index/hash'-ing has helped too. Still doesn't mean I know what I'm doing, but... > :No history activity happens when I shut down INN normally, which should > :free the MAP_NOSYNC'ed pages and make them available to be written to > :disk before rebooting, maybe. > > MAP_NOSYNC pages are not flushed when the referencing program exits. > They stick around until they are forced out. You can flush them > manually by using a mmap()/msync() combination. i.e. an msync() prior > to munmap()ing (from INND only) ought to do it. Oh well, somehow I had the idea (from the mmap manpage?) that when all programs referencing them exited, they would, or might, be flushed. Apparently the problem I noted with NetBSD requires use of msync(), now that the multiple-article files are getting mmap'ed, and same with the history. Which will probably kill performance there, until their mmap/caches gets fixed. So forget I mentioned that in the last mail. Now, I haven't tried the userland `fsync' while the Active memory was at sane levels, but what I saw on a quiet system where I had shut down innd was that of about 300MB Active, the fsync of both history files would free only about 100MB. > :What I think is happening, based on these observations, is that the > :data from the history hash files (less than 100MB) gets read into > :memory, but the updates to it are not written over the data to be > :replaced -- it's simply appended to, up to the limit of the available > :memory. When this limit is reached on the transit machines, then > :things stabilize and old pages get recycled (but still, more memory > :overall is used than the size of the actual file). > > It doesn't append... the pages are reused. The set of 'active' > pages in the VM system is effectively the set of all files accessed > for the entire system, not just MAP_NOSYNC pages. If you are only > MAP_NOSYNC'ing 100MB worth of pages, then only 100MB worth of pages > will be left unflushed. Yeah, that's what I learned. So my idea about how the amount of RAM that would appear as Active increases to fill as much of the available memory turned out to be wrong. I still can't explain that. I wish I hadn't returned the rest of the GB of RAM I had, just to see how the numbers are on a system with far more headroom. The sizes of the two NOSYNC'ed history files are as above (~180MB total), and I believe the particular BerkeleyDB file is <18MB. Meaning a total of maximum <200MB unflushed data now. Which is half of what is shown as Active. Hmmm. > Is it possible that history file rewriting is creating an issue? Doesn't > INN rewrite the history file every once in a while to clear out old > garbage? I'm not up on the latest INN. In normal operation, no -- the text file is append-only (the text file isn't used for lookups with the MD5-based hashing), and expire, which I'm running manually, rewrites the hash files -- leading to a mysterious lack of space today when I attempted to run both expire and makedbz (a variant of makehistory), and apparently some reader processes or some daemons still had the old inodes open, until suddenly in one swell foop, some 750MB was freed up -- far more than I expected to see, so I should probably look into this space usage sometime... This shouldn't be a problem the way I'm running things now. I haven't run an expire process since the last reboot to observe things closely. > :I'm guessing that additional activity of the reader machine causes > :jumps in memory usage not seen on the transit machines, that is enough > :to force some of the unwritten dirty pages to be written to the > :history file, as a few megs of swap get used, which is why it does > :not stabilize as `nicely' as the transit machines. > > This makes sense... the amount of swap that gets used is critical. > If we are talking about only a few megabytes, then your system is > *not* swapping significantly, it is simply swapping out completely > idle pages from things like idle getty's and such. This is a good > thing. The disk activity would thus be mostly due to MAP_NOSYNC pages > being written out. Yeah, but that disk activity seems to be the cause for the history timings in INN taking from (now) 20% up to (earlier) 50% of the available time, which isn't nice. I mean, if I have a GB of silicon to toss at the thing, you think I'd be able to bribe the VM system into keeping the NOSYNC pages where I want 'em, like the way they are during the first umpteen minutes following a reboot... > :Anyway, once this happens, performance sucks rocks, the history > :drive light is enough to read by (or should I say, it keeps me from > :getting much-needed sleep), and apparently only a reboot can free > :up memory for better purposes. > > Well, the performance sucking part means something is not working > as designed. The question is what. Tell ya what -- I'll bring things down after I send this (I'm writing this from the console), use `fsync' on the three files and observe disk activity and `top', I'll put an INN without the MAP_NOSYNC in place (but leave BerkeleyDB as is for now), and I'll see just how low I can get Active on a quiet system that had been running to be, before I reboot. Then I'll try un-NOSYNC'ing BerkeleyDB as well, and using that as reference, to see just which end I'm talking out of. If I see a big difference without NOSYNC, I'll scream bloody murder. If I don't, I'll also be screaming but you won't hear it since I'll be eating my old socks at the same time. Maybe then I'll figure out what else I can do... > Here is what I would recommend. First, I would use 'systat -vm 1' > and carefully examine the pageout/swapout activity. If the SWAP PAGER > has no significant activity then we can discard it as a possible problem. > If the VN PAGER has significant activity, then this is what we need > to focus on. Swap pager mostly idle. VN pager constantly from ~10 to ~30 `in' (count), pages in varying wildly from ~20 to ~150. Or more. Column `out' sees some activity, usually a single digit once every few seconds, with bursts of two- or three-digit numbers maybe once or twice every ~10-odd seconds. > I would try changing the pageout and VM cache parameters. Do NOT mess > with the VM free parameters! Try changing the vm.v_cache_min and > vm.v_cache_max parameters. For example, increase vm.v_cache_max to > widen the hysteresis. You can slo try changing vm.pageout_algorithm > from 0 to 1 (this is not likely to have much of an effect), and you > can also try increasing vm.max_page_launder, e.g. from 32 to > 100 (much larger would not have any effect). Finally, you can > try increasing the vm.v_inactive_target. Do not increase the > vm.v_free_target. Thanks, I may not do anything with these right now, unless you tell me that everything else I'm observing is peachy-keen-groovy... > Last thing: Using MAP_NOSYNC has a well known problem when used to > fill 'holes' in files. That is, if the history file is being appended > to by calling ftruncate(), but the new space is not write()n to and > instead is dirtied via the mmap, you will have a serious fragmentation > problem with the file. In order to avoid this problem any file appends > should occur using write() if possible, or the newly allocated space in > the file should be filled with zero's using write() prior to being > random-accessed by mmap() (which might be easier to implement). Hmmm. If I'm reading the k0de right, the new files are in fact created with ftruncate() when they are initialized, but then, in theory, you should be moving these files into place, and starting INN, which would read from (and mmap) these (nominally) fixed-length files. After this, apart from overflow conditions (which I'll have to look at), the hash/ index files should not be appended, but new data inserted, by, hmmm, memcpy or something... I don't think this is the case here -- the append-only text file is not NO_SYNC'ed (I don't even think it's mmap'ed, but ICBW) -- the hash and index files are fixed size hash files (well, nominally fixed, until they overflow, which I tried to avoid by doing the makedbz), and the files, once initialized, are read off the disk -- not sure about that step of initialization (makedbz/makehistory)... Must wake up and read source. thanks! barry bouwsma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 21:52:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from DarkOne.ural.net (relay.ural.ru [195.64.192.49]) by hub.freebsd.org (Postfix) with ESMTP id 2AF3F37B402 for <freebsd-hackers@FreeBSD.ORG>; Fri, 1 Dec 2000 21:52:22 -0800 (PST) Received: from relay.svrw.ru (relay.svrw.ru [195.64.206.2]) by DarkOne.ural.net (8.11.1/eTn) with ESMTP id eB25qKj70095 for <freebsd-hackers@FreeBSD.ORG>; Sat, 2 Dec 2000 10:52:20 +0500 (ES) Received: from ivc-gate.svrw.mps (a20.svrw.ru [195.64.206.20]) by relay.svrw.ru (8.11.1/8.11.1) with ESMTP id eB25t7e06798 for <freebsd-hackers@FreeBSD.ORG>; Sat, 2 Dec 2000 08:55:07 +0300 Received: by ivc-gate.svrw.mps with Internet Mail Service (5.5.2650.21) id <YCAXHJNX>; Sat, 2 Dec 2000 08:52:05 +0300 Message-ID: <91CBC4487424D411B17900508B5F0C8B1606CC@tumen-mail.tumen.svrw.mps> From: =?koi8-r?Q?=EB=C1=D2=D0=D5=DB=C9=CE_=F3=C5=D2=C7=C5=CA_=F7=C9=CB=D4?= =?koi8-r?Q?=CF=D2=CF=D7=C9=DE?= <wharf@svrw.ru> To: freebsd-hackers@FreeBSD.ORG Subject: unsubscribe Date: Sat, 2 Dec 2000 08:44:28 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 1 21:52:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from DarkOne.ural.net (relay.ural.ru [195.64.192.49]) by hub.freebsd.org (Postfix) with ESMTP id A437D37B401 for <hackers@FreeBSD.ORG>; Fri, 1 Dec 2000 21:52:21 -0800 (PST) Received: from relay.svrw.ru (relay.svrw.ru [195.64.206.2]) by DarkOne.ural.net (8.11.1/eTn) with ESMTP id eB25qBj70073 for <hackers@FreeBSD.ORG>; Sat, 2 Dec 2000 10:52:11 +0500 (ES) Received: from ivc-gate.svrw.mps (a20.svrw.ru [195.64.206.20]) by relay.svrw.ru (8.11.1/8.11.1) with ESMTP id eB25sve06785 for <hackers@FreeBSD.ORG>; Sat, 2 Dec 2000 08:54:58 +0300 Received: by ivc-gate.svrw.mps with Internet Mail Service (5.5.2650.21) id <YCAXHJN4>; Sat, 2 Dec 2000 08:51:55 +0300 Message-ID: <91CBC4487424D411B17900508B5F0C8B1606CA@tumen-mail.tumen.svrw.mps> From: =?koi8-r?Q?=EB=C1=D2=D0=D5=DB=C9=CE_=F3=C5=D2=C7=C5=CA_=F7=C9=CB=D4?= =?koi8-r?Q?=CF=D2=CF=D7=C9=DE?= <wharf@svrw.ru> To: hackers@FreeBSD.ORG Subject: unsubscribe Date: Sat, 2 Dec 2000 08:43:02 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 2 2:56: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 86E3337B400 for <freebsd-hackers@freebsd.org>; Sat, 2 Dec 2000 02:56:05 -0800 (PST) Received: from server.wes.mee.com (p3EE2AA1A.dip.t-dialin.net [62.226.170.26]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id LAA10071; Sat, 2 Dec 2000 11:56:08 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by server.wes.mee.com (8.11.0/8.11.0) with ESMTP id eB29vEN00612; Sat, 2 Dec 2000 10:57:29 +0100 (CET) (envelope-from frederik@freddym.org) Date: Sat, 2 Dec 2000 10:57:14 +0100 (CET) From: Frederik Meerwaldt <frederik@freddym.org> X-Sender: frederik@server.wes.mee.com To: Thomas Moestl <tmoestl@gmx.net> Cc: freebsd-hackers@freebsd.org Subject: Re: natd bug In-Reply-To: <20001202002222.A2616@crow.dom2ip.de> Message-ID: <Pine.BSF.4.21.0012021038160.1129-100000@server.wes.mee.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! > Is your link up at that time? The usual setup for a sppp device using dynamic > ip's is an invalid ip (0.0.0.0) that is changed once an ip was assigned. So, if > you are not dialled in, the invalid ip will be put in by natd, and that usually > causes this error message. I want the link to get up then. Normally (if I set a normal route) I just set the isp0 network interface up (ifconfig isp0 0.0.0.0 0.0.0.1 link1 up) and then do a ping 194.25.2.129 (a DNS Server externally) and then the ISDN interface dials out. Now I want to do the same, but not over a route but over natd and a gateway, so that it dials out when a package from any computer arrives. Best Regards, Freddy -- Geek Code 3.1: GCS s+: a--- C+++ UBOU+++ P-- E--- W++ N w--- V++ PGP- t? 5? tv ===================================================================== Frederik Meerwaldt ICQ: 83045387 Homepage: http://www.freddym.org Bavaria/Germany OpenVMS and Unix Howtos and much more FreeBSD, NetBSD, OpenBSD, Tru64, OpenVMS, Ultrix, BeOS, Linux To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 2 6:53:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from int80h.org (r40.bfm.org [216.127.220.136]) by hub.freebsd.org (Postfix) with ESMTP id 6E84D37B400 for <hackers@FreeBSD.org>; Sat, 2 Dec 2000 06:53:10 -0800 (PST) Received: (from root@localhost) by int80h.org (8.9.2/8.9.2) id IAA00309 for hackers@FreeBSD.org; Sat, 2 Dec 2000 08:51:58 -0600 (CST) (envelope-from adam) Date: Sat, 2 Dec 2000 08:51:27 -0600 From: Charlie & <root@int80h.org> To: hackers@FreeBSD.org Subject: pipe Message-ID: <20001202085127.A301@int80h.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry if this is a dumb question, but after years of DOS programming, I am still discovering the subletiest of Unix: When I create a pipe, do I have to use it for interprocess communication only, or can the same process write to one end and later read from the other? What I am looking for is to use it as a FIFO-style buffer. Instead of allocating and reallocating memory, let the system worry about how much memory the data needs. This is for a two (or more) pass compiler, which reads from stdin and writes to stdout. It does not know how much data it still has coming in, so it has no idea how much memory it needs to store information in, yet after one pass it needs to read it in the same order it was written (FIFO). If this is possible, is there a limit as to how much I can write to the pipe before I start reading it, or is it limitless (within reason, of course)? Cheers, Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 2 6:55:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from int80h.org (r40.bfm.org [216.127.220.136]) by hub.freebsd.org (Postfix) with ESMTP id 3454437B400 for <hackers@FreeBSD.org>; Sat, 2 Dec 2000 06:55:07 -0800 (PST) Received: (from root@localhost) by int80h.org (8.9.2/8.9.2) id IAA00315 for hackers@FreeBSD.org; Sat, 2 Dec 2000 08:54:00 -0600 (CST) (envelope-from adam) Date: Sat, 2 Dec 2000 08:54:00 -0600 From: "G . Adam Stanislav" <adam@int80h.org> To: hackers@FreeBSD.org Subject: pipe Message-ID: <20001202085400.B301@int80h.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, sorry for sending my last message as Charlie Root. I thought I was logged in as Adam. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 2 8:41:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.mail.yahoo.com (smtp2.mail.yahoo.com [128.11.68.32]) by hub.freebsd.org (Postfix) with SMTP id 93F1237B400 for <hackers@freebsd.org>; Sat, 2 Dec 2000 08:41:34 -0800 (PST) Received: from unknown (HELO yahoo.com) (209.88.169.110) by smtp.mail.vip.suc.yahoo.com with SMTP; 2 Dec 2000 16:41:25 -0000 X-Apparently-From: <ycardena@yahoo.com> Message-ID: <3A291873.7DD5310D@yahoo.com> Date: Sat, 02 Dec 2000 10:42:43 -0500 From: "Yonny Cardenas B." <ycardena@yahoo.com> Organization: Universidad de los Andes X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Change the size allocated memory in kernel Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello How I can change the size of the previously allocated memory in kernel address space? In the user mode I can use the realloc() function. I may use the kernel memory management routines of some way? Thanks. +------------------------------------------------------------------+ | YONNY CARDENAS B. Apartado Aereo 22828 | | Systems Engineer Santafe de Bogota D.C. | | Colombia - South America | | Student M.Sc. Tel: +571 6095477 | | UNIVERSIDAD DE LOS ANDES mailto: y-carden@uniandes.edu.co | | ycardena@computer.org | | ICQ #: 46933750 | +------------------------------------------------------------------+ UNIX is BSD, and FreeBSD is an advanced 4.4BSD __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 2 9:30:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 8056237B400 for <hackers@freebsd.org>; Sat, 2 Dec 2000 09:30:28 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 142GDY-000072-00; Sat, 02 Dec 2000 10:12:56 -0700 Message-ID: <3A292D98.E655D755@softweyr.com> Date: Sat, 02 Dec 2000 10:12:56 -0700 From: Wes Peters <wes@softweyr.com> Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Charlie & <root@int80h.org> Cc: hackers@FreeBSD.org Subject: Re: pipe References: <20001202085127.A301@int80h.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Charlie & wrote: > > Sorry if this is a dumb question, but after years of DOS programming, I > am still discovering the subletiest of Unix: > > When I create a pipe, do I have to use it for interprocess communication > only, or can the same process write to one end and later read from the > other? > > What I am looking for is to use it as a FIFO-style buffer. Instead of > allocating and reallocating memory, let the system worry about how > much memory the data needs. This is for a two (or more) pass compiler, > which reads from stdin and writes to stdout. It does not know how much > data it still has coming in, so it has no idea how much memory it needs > to store information in, yet after one pass it needs to read it in the > same order it was written (FIFO). > > If this is possible, is there a limit as to how much I can write to the > pipe before I start reading it, or is it limitless (within reason, of > course)? Yes, you can read from your own pipe, and yes the buffering availabe in the pipe is limited. IIRC, the pipe size is 8K. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 2 9:42:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id 029CD37B400 for <hackers@freebsd.org>; Sat, 2 Dec 2000 09:42:37 -0800 (PST) Received: from m184-mp1-cvx1c.gui.ntl.com ([62.252.12.184]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20001202174235.TYVX24128.mta01-svc.ntlworld.com@m184-mp1-cvx1c.gui.ntl.com> for <hackers@freebsd.org>; Sat, 2 Dec 2000 17:42:35 +0000 Date: Sat, 2 Dec 2000 17:44:09 +0000 (GMT) From: George Reid <greid@ukug.uk.freebsd.org> X-Sender: geeorgy@sobek.openirc.co.uk To: hackers@freebsd.org Subject: Trying to mount an audio CD causes a kernel panic Message-ID: <Pine.BSF.4.21.0012021741120.5793-100000@sobek.openirc.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, Could somebody take a look at the patch I wrote for the panic that occurs when an audio CD is mounted as if it were a CD9660 filesystem? In retrospect, the ioctl in the patch needs to re-retrieve the medium information from the drive, but that should be relatively trivial. PR/patch at http://www.freebsd.org/cgi/query-pr.cgi?pr=22664 "And then it comes to be that the soothing light at the end of your tunnel was just a freight train, comin' your way." George Reid * greid@ukug.uk.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 2 11: 5:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 64F8D37B400 for <hackers@freebsd.org>; Sat, 2 Dec 2000 11:05:29 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eB2J4An63970; Sat, 2 Dec 2000 11:04:10 -0800 (PST) (envelope-from dillon) Date: Sat, 2 Dec 2000 11:04:10 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> Message-Id: <200012021904.eB2J4An63970@earth.backplane.com> To: News History File User <newsuser@free-pr0n.netscum.dk> Cc: hackers@freebsd.org, usenet@tdk.net Subject: Re: vm_pageout_scan badness References: <200012011918.eB1JIol53670@earth.backplane.com> <200012020525.eB25PPQ92768@newsmangler.inet.tele.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :closely the pattern of what happens to the available memory following :a fresh boot... At the moment, this (reader) machine has been up for :half a day, with performance barely able to keep up with a full feed :(but starting to slip as the overnight burst of binaries is starting), :but at last look, history lookups and writes are accounting for more :than half (!) of the INN news process time, with available idle time :being essentially zero. So... No idle time? That doesn't sound like blocked I/O to me, it sounds like the machine has run out of cpu. :Following the boot, things start out with plenty of memory Free, and :something like 4MB Active, which seems reasonable to me. Then I start :things. : :As is to be expected, INN increases in size as it does history lookups :and updates, and the amount of memory shown as Active tracks this, :more or less. But what's happening to the Free value! It's going :down at as much as 4MB per `top' interval. Or should I say, what is :happening to the Inactive value -- it's constantly increasing, and I :observe a rapid migration of all the Free memory to Inactive, until :the value of Inactive peaks out at the time that Free drops to about :996k, beyond which it changes little. None of the swap space has :been touched yet. : :As soon as the value for Free hits bottom and that of Inactive has :reached a max, now the migration happens from Inactive to Active -- :until this point, the value of Active has been roughly what I would :expect to see, given the size of the history hash/index files, and :the BerkeleyDB file I'm now using MAP_NOSYNC as well for a definite :improvement in overview access times. Hmm. An increasing 'inactive' most often occurs when a program is reading a file sequentially. It sounds like most of the inactive pages are probably due to reader requests from the spool. :> Is it possible that history file rewriting is creating an issue? Doesn't :> INN rewrite the history file every once in a while to clear out old :> garbage? I'm not up on the latest INN. : :In normal operation, no -- the text file is append-only (the text file :isn't used for lookups with the MD5-based hashing), and expire, which :I'm running manually, rewrites the hash files -- leading to a mysterious :lack of space today when I attempted to run both expire and makedbz (a :variant of makehistory), and apparently some reader processes or some :daemons still had the old inodes open, until suddenly in one swell foop, :some 750MB was freed up -- far more than I expected to see, so I should :probably look into this space usage sometime... : :This shouldn't be a problem the way I'm running things now. I haven't :run an expire process since the last reboot to observe things closely. Woa. 750MB? There are only two things that can cause that: * A process with hundreds of megabytes of private store exited * A large (500+ MB) file is deleted after having previously been mmap()'d. (or the process holding the last open descriptor to the file, after deletion, now exits). If I remember INN right, there is a situation that can occur here... the reader processes open up the history file in order to implement a certain NNTP commands. I'm trying to remember which one... I think its one of search commands. Fubar... anyone remember which NNTP command opens up the history file? In anycase, I remember at BEST I had to completely disable that command when running INN because it caused long-running reader processes to keep a descriptor open on now-deleted history files. When you do an expire run which replaces the history file, the original (now deleted) history file may still be open by those reader processes. This could easily account for your problems. This sort of situation occurs most often when there is no timeout or too-long a timeout in the reader processes, and/or if tcp keepalives are not turned on, plus when certain NNTP commands (used mostly by abusers, by the way, which try to download feeds via their reader access) are enabled. I would immediately research this... look for reader processes that have hung around too long and try killing them, then see if that clears out some memory. There will also be a serious file fragmentation issue using MAP_NOSYNC in the expire process. You can probably use MAP_NOSYNC safely in the INND core, but don't use it to rebuild the history file in the expire process. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 2 13:11:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [192.215.234.86]) by hub.freebsd.org (Postfix) with SMTP id 0840E37B400 for <freebsd-hackers@freebsd.org>; Sat, 2 Dec 2000 13:11:21 -0800 (PST) Received: (qmail 13922 invoked by uid 1078); 2 Dec 2000 21:11:37 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 2 Dec 2000 21:11:37 -0000 Date: Sat, 2 Dec 2000 13:11:37 -0800 (PST) From: Gordon Tetlow <gordont@bluemtn.net> X-Sender: gordont@sdmail0.sd.bmarts.com To: Frederik Meerwaldt <frederik@freddym.org> Cc: freebsd-hackers@freebsd.org Subject: Re: natd bug In-Reply-To: <Pine.BSF.4.21.0011302021590.20212-100000@server.wes.mee.com> Message-ID: <Pine.BSF.4.05.10012021305030.24235-200000@sdmail0.sd.bmarts.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1561284584-975791497=:24235" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk 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-1561284584-975791497=:24235 Content-Type: TEXT/PLAIN; charset=US-ASCII I'll add another data point if I can. I also get this message from my working firewall box. I get it even when all the machines behind the firewall are powered down. And I get it alot. Attached are my firewall rules and dmesg. -gordon Also, here are the arguments I pass to natd: /sbin/natd -dynamic -unregistered_only -use_sockets -punch_fw 3850:10 -n vx0 On Thu, 30 Nov 2000, Frederik Meerwaldt wrote: > Date: Thu, 30 Nov 2000 20:25:15 +0100 (CET) > From: Frederik Meerwaldt <frederik@freddym.org> > To: freebsd-hackers@freebsd.org > Subject: natd bug > > Hi there! > > I was just looking why my natd doesnt work, when I discovered the > following bug (?): > > I compiled my kernel with IPDIVERT IPFIREWALL and > IPFIREWALL_DEFAULT_TO_ACCEPT and I set up only one rule: > ipfw add divert natd all from any to any via isp0 > Then I started natd (at boot time): > natd -unregistered_only -dynamic -n isp0 > But when a package arrives (doesn't matter from localhost or another > host), natd gives out a kernel message: > > Nov 30 15:03:06 server natd[195]: failed to write packet back (Permission > denied) > > What does that mean? I started natd from my rc.local, so it runs as root > and it should have all permissions. > > Thanks in advance! > Best Regards, > Freddy > > -- > Geek Code 3.1: GCS s+: a--- C+++ UBOU+++ P-- E--- W++ N w--- V++ PGP- t? 5? tv > > ===================================================================== > Frederik Meerwaldt ICQ: 83045387 Homepage: http://www.freddym.org > Bavaria/Germany OpenVMS and Unix Howtos and much more > FreeBSD, NetBSD, OpenBSD, Tru64, OpenVMS, Ultrix, BeOS, Linux > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > --0-1561284584-975791497=:24235 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="hobbes.log" Content-Transfer-Encoding: BASE64 Content-ID: <Pine.BSF.4.05.10012021311370.24235@sdmail0.sd.bmarts.com> Content-Description: Content-Disposition: attachment; filename="hobbes.log" Z29yZG9udEBob2JiZXM6fiQgc3UgLQ0KUGFzc3dvcmQ6DQpob2JiZXMjIGlw ZncgbGlzdA0KMDAxMDAgYWxsb3cgaXAgZnJvbSBhbnkgdG8gYW55IHZpYSBs bzANCjAwMTUwIGFsbG93IGlwIGZyb20gMTI3LjAuMC4xIHRvIDEyNy4wLjAu MQ0KMDAyMDAgZGVueSBpcCBmcm9tIGFueSB0byAxMjcuMC4wLjAvOA0KMDAz MDAgZGVueSBpcCBmcm9tIDE5Mi4xNjguNS4wLzI0IHRvIGFueSBpbiByZWN2 IHZ4MA0KMDA0MDAgZGVueSBpcCBmcm9tIDE5Mi4xNjguNi4wLzI0IHRvIGFu eSBpbiByZWN2IHZ4MA0KMDA1MDAgZGVueSBpcCBmcm9tIDI0LjMwLjE0MC4w LzI0IHRvIGFueSBpbiByZWN2IHhsMA0KMDA2MDAgZGVueSBpcCBmcm9tIDI0 LjMwLjE0MC4wLzI0IHRvIGFueSBpbiByZWN2IHdpMA0KMDA3MDAgZGVueSBp cCBmcm9tIGFueSB0byAxMC4wLjAuMC84IHZpYSB2eDANCjAwODAwIGRlbnkg aXAgZnJvbSBhbnkgdG8gMTcyLjE2LjAuMC8xMiB2aWEgdngwDQowMDkwMCBk ZW55IGlwIGZyb20gYW55IHRvIDE5Mi4xNjguMC4wLzE2IHZpYSB2eDANCjAx MDAwIGRlbnkgaXAgZnJvbSBhbnkgdG8gMC4wLjAuMC84IHZpYSB2eDANCjAx MTAwIGRlbnkgaXAgZnJvbSBhbnkgdG8gMTY5LjI1NC4wLjAvMTYgdmlhIHZ4 MA0KMDEyMDAgZGVueSBpcCBmcm9tIGFueSB0byAxOTIuMC4yLjAvMjQgdmlh IHZ4MA0KMDEzMDAgZGVueSBpcCBmcm9tIGFueSB0byAyMjQuMC4wLjAvNCB2 aWEgdngwDQowMTQwMCBkZW55IGlwIGZyb20gYW55IHRvIDI0MC4wLjAuMC80 IHZpYSB2eDANCjAxNTAwIGRpdmVydCA4NjY4IGlwIGZyb20gYW55IHRvIGFu eSB2aWEgdngwDQowMTYwMCBkZW55IGlwIGZyb20gMTAuMC4wLjAvOCB0byBh bnkgdmlhIHZ4MA0KMDE3MDAgZGVueSBpcCBmcm9tIDE3Mi4xNi4wLjAvMTIg dG8gYW55IHZpYSB2eDANCjAxODAwIGRlbnkgaXAgZnJvbSAxOTIuMTY4LjAu MC8xNiB0byBhbnkgdmlhIHZ4MA0KMDE5MDAgZGVueSBpcCBmcm9tIDAuMC4w LjAvOCB0byBhbnkgdmlhIHZ4MA0KMDIwMDAgZGVueSBpcCBmcm9tIDE2OS4y NTQuMC4wLzE2IHRvIGFueSB2aWEgdngwDQowMjEwMCBkZW55IGlwIGZyb20g MTkyLjAuMi4wLzI0IHRvIGFueSB2aWEgdngwDQowMjIwMCBkZW55IGlwIGZy b20gMjI0LjAuMC4wLzQgdG8gYW55IHZpYSB2eDANCjAyMzAwIGRlbnkgaXAg ZnJvbSAyNDAuMC4wLjAvNCB0byBhbnkgdmlhIHZ4MA0KMDI0MDAgYWxsb3cg dGNwIGZyb20gYW55IHRvIGFueSBlc3RhYmxpc2hlZA0KMDI1MDAgYWxsb3cg aXAgZnJvbSBhbnkgdG8gYW55IGZyYWcNCjAyNjAwIGFsbG93IHRjcCBmcm9t IGFueSB0byAyNC4zMC4xNDAuNTUgNTMgc2V0dXANCjAyNzAwIGFsbG93IHVk cCBmcm9tIGFueSB0byAyNC4zMC4xNDAuNTUgNTMNCjAyODAwIGFsbG93IHVk cCBmcm9tIDI0LjMwLjE0MC41NSA1MyB0byBhbnkNCjAyOTAwIGFsbG93IHRj cCBmcm9tIGFueSB0byAxOTIuMTY4LjUuMSA1MyBzZXR1cA0KMDMwMDAgYWxs b3cgdWRwIGZyb20gYW55IHRvIDE5Mi4xNjguNS4xIDUzDQowMzEwMCBhbGxv dyB1ZHAgZnJvbSAxOTIuMTY4LjUuMSA1MyB0byBhbnkNCjAzMjAwIGFsbG93 IHRjcCBmcm9tIGFueSB0byAxOTIuMTY4LjYuMSA1MyBzZXR1cA0KMDMzMDAg YWxsb3cgdWRwIGZyb20gYW55IHRvIDE5Mi4xNjguNi4xIDUzDQowMzQwMCBh bGxvdyB1ZHAgZnJvbSAxOTIuMTY4LjYuMSA1MyB0byBhbnkNCjAzNTAwIGFs bG93IHRjcCBmcm9tIGFueSB0byAyNC4zMC4xNDAuNTUgODAgc2V0dXANCjAz NjAwIGFsbG93IHRjcCBmcm9tIGFueSB0byAyNC4zMC4xNDAuNTUgMjIgc2V0 dXANCjAzNzAwIGFsbG93IHRjcCBmcm9tIGFueSB0byAyNC4zMC4xNDAuNTUg MTEzIHNldHVwDQowMzgwMCBhbGxvdyBpY21wIGZyb20gYW55IHRvIGFueQ0K MDM5MDAgZGVueSBsb2cgbG9nYW1vdW50IDEwMCB0Y3AgZnJvbSBhbnkgdG8g YW55IGluIHJlY3YgdngwIHNldHVwDQowNDAwMCBhbGxvdyB0Y3AgZnJvbSBh bnkgdG8gYW55IHNldHVwDQowNDEwMCBhbGxvdyB1ZHAgZnJvbSBhbnkgNTMg dG8gMjQuMzAuMTQwLjU1DQowNDIwMCBhbGxvdyB1ZHAgZnJvbSAyNC4zMC4x NDAuNTUgdG8gYW55IDUzDQowNDMwMCBhbGxvdyB1ZHAgZnJvbSBhbnkgMTIz IHRvIDI0LjMwLjE0MC41NQ0KMDQ0MDAgYWxsb3cgdWRwIGZyb20gMjQuMzAu MTQwLjU1IHRvIGFueSAxMjMNCjY1NTM1IGRlbnkgaXAgZnJvbSBhbnkgdG8g YW55DQpob2JiZXMjIGRtZXNnDQpDb3B5cmlnaHQgKGMpIDE5OTItMjAwMCBU aGUgRnJlZUJTRCBQcm9qZWN0Lg0KQ29weXJpZ2h0IChjKSAxOTc5LCAxOTgw LCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAxOTkzLCAx OTk0DQoJVGhlIFJlZ2VudHMgb2YgdGhlIFVuaXZlcnNpdHkgb2YgQ2FsaWZv cm5pYS4gQWxsIHJpZ2h0cyByZXNlcnZlZC4NCkZyZWVCU0QgNC4yLVJFTEVB U0UgIzQ6IEZyaSBEZWMgIDEgMDE6NDg6NTcgUFNUIDIwMDANCiAgICByb290 QGhvYmJlcy5vYmZ1c2NhdGVkLm9yZzovdXNyL3NyYy9zeXMvY29tcGlsZS9I T0JCRVMNClRpbWVjb3VudGVyICJpODI1NCIgIGZyZXF1ZW5jeSAxMTkzMTgy IEh6DQpUaW1lY291bnRlciAiVFNDIiAgZnJlcXVlbmN5IDE5OTQzMjg2OCBI eg0KQ1BVOiBQZW50aXVtIFBybyAoMTk5LjQzLU1IeiA2ODYtY2xhc3MgQ1BV KQ0KICBPcmlnaW4gPSAiR2VudWluZUludGVsIiAgSWQgPSAweDYxNyAgU3Rl cHBpbmcgPSA3DQogIEZlYXR1cmVzPTB4ZjlmZjxGUFUsVk1FLERFLFBTRSxU U0MsTVNSLFBBRSxNQ0UsQ1g4LFNFUCxNVFJSLFBHRSxNQ0EsQ01PVj4NCnJl YWwgbWVtb3J5ICA9IDEwMDY2MzI5NiAoOTgzMDRLIGJ5dGVzKQ0KYXZhaWwg bWVtb3J5ID0gOTQ4NTUxNjggKDkyNjMySyBieXRlcykNClByZWxvYWRlZCBl bGYga2VybmVsICJrZXJuZWwiIGF0IDB4YzAzMDMwMDAuDQpQZW50aXVtIFBy byBNVFJSIHN1cHBvcnQgZW5hYmxlZA0KbWQwOiBNYWxsb2MgZGlzaw0KbnB4 MDogPG1hdGggcHJvY2Vzc29yPiBvbiBtb3RoZXJib2FyZA0KbnB4MDogSU5U IDE2IGludGVyZmFjZQ0KcGNpYjA6IDxIb3N0IHRvIFBDSSBicmlkZ2U+IG9u IG1vdGhlcmJvYXJkDQpwY2kwOiA8UENJIGJ1cz4gb24gcGNpYjANCmlzYWIw OiA8SW50ZWwgODIzNzFTQiBQQ0kgdG8gSVNBIGJyaWRnZT4gYXQgZGV2aWNl IDcuMCBvbiBwY2kwDQppc2EwOiA8SVNBIGJ1cz4gb24gaXNhYjANCmF0YXBj aTA6IDxJbnRlbCBQSUlYMyBBVEEgY29udHJvbGxlcj4gcG9ydCAweGZmYTAt MHhmZmFmIGF0IGRldmljZSA3LjEgb24gcGNpMA0KYXRhMDogYXQgMHgxZjAg aXJxIDE0IG9uIGF0YXBjaTANCmF0YTE6IGF0IDB4MTcwIGlycSAxNSBvbiBh dGFwY2kwDQpwY2kwOiA8TWF0cm94IE1HQSBNaWxsZW5uaXVtIDIwNjRXIGdy YXBoaWNzIGFjY2VsZXJhdG9yPiBhdCAxMS4wIGlycSAxMQ0KdngwOiA8M0NP TSAzQzU5MCBFdGhlcmxpbmsgSUlJIFBDST4gcG9ydCAweGZmODAtMHhmZjlm IGlycSAxMCBhdCBkZXZpY2UgMTcuMCBvbiBwY2kwDQp1dHBbKnV0cCpdIGFk ZHJlc3MgMDA6YTA6MjQ6YzY6MTc6ZDkNCnZ4MDogZHJpdmVyIGlzIHVzaW5n IG9sZC1zdHlsZSBjb21wYXRhYmlsaXR5IHNoaW1zDQp4bDA6IDwzQ29tIDNj OTAwQi1UUE8gRXRoZXJsaW5rIFhMPiBwb3J0IDB4ZmM4MC0weGZjZmYgbWVt IDB4ZmZiZWJjMDAtMHhmZmJlYmM3ZiBpcnEgMTAgYXQgZGV2aWNlIDE5LjAg b24gcGNpMA0KeGwwOiBFdGhlcm5ldCBhZGRyZXNzOiAwMDo1MDowNDo4MDpl YzpiNA0KeGwwOiBzZWxlY3RpbmcgMTBiYXNlVCB0cmFuc2NlaXZlciwgaGFs ZiBkdXBsZXgNCmZkYzA6IDxORUMgNzIwNjVCIG9yIGNsb25lPiBhdCBwb3J0 IDB4M2YwLTB4M2Y1LDB4M2Y3IGlycSA2IGRycSAyIG9uIGlzYTANCmZkYzA6 IEZJRk8gZW5hYmxlZCwgOCBieXRlcyB0aHJlc2hvbGQNCmZkMDogPDE0NDAt S0IgMy41IiBkcml2ZT4gb24gZmRjMCBkcml2ZSAwDQphdGtiZGMwOiA8S2V5 Ym9hcmQgY29udHJvbGxlciAoaTgwNDIpPiBhdCBwb3J0IDB4NjAsMHg2NCBv biBpc2EwDQphdGtiZDA6IDxBVCBLZXlib2FyZD4gZmxhZ3MgMHgxIGlycSAx IG9uIGF0a2JkYzANCmtiZDAgYXQgYXRrYmQwDQpwc20wOiA8UFMvMiBNb3Vz ZT4gaXJxIDEyIG9uIGF0a2JkYzANCnBzbTA6IG1vZGVsIEdlbmVyaWMgUFMv MiBtb3VzZSwgZGV2aWNlIElEIDANCnZnYTA6IDxHZW5lcmljIElTQSBWR0E+ IGF0IHBvcnQgMHgzYzAtMHgzZGYgaW9tZW0gMHhhMDAwMC0weGJmZmZmIG9u IGlzYTANCnNjMDogPFN5c3RlbSBjb25zb2xlPiBhdCBmbGFncyAweDEwMCBv biBpc2EwDQpzYzA6IFZHQSA8MTYgdmlydHVhbCBjb25zb2xlcywgZmxhZ3M9 MHgzMDA+DQpwY2ljMDogPFZhZGVtIDQ2OT4gYXQgcG9ydCAweDNlMCBpb21l bSAweGQwMDAwIG9uIGlzYTANCnBjaWMwOiBQb2xsaW5nIG1vZGUNCnBjY2Fy ZDA6IDxQQyBDYXJkIGJ1cyAtLSBrbHVkZ2UgdmVyc2lvbj4gb24gcGNpYzAN CnBjY2FyZDE6IDxQQyBDYXJkIGJ1cyAtLSBrbHVkZ2UgdmVyc2lvbj4gb24g cGNpYzANCnNpbzAgYXQgcG9ydCAweDNmOC0weDNmZiBpcnEgNCBmbGFncyAw eDEwIG9uIGlzYTANCnNpbzA6IHR5cGUgMTY1NTBBDQpzaW8xIGF0IHBvcnQg MHgyZjgtMHgyZmYgaXJxIDMgb24gaXNhMA0Kc2lvMTogdHlwZSAxNjU1MEEN CklQIHBhY2tldCBmaWx0ZXJpbmcgaW5pdGlhbGl6ZWQsIGRpdmVydCBlbmFi bGVkLCBydWxlLWJhc2VkIGZvcndhcmRpbmcgZGlzYWJsZWQsIGRlZmF1bHQg dG8gZGVueSwgbG9nZ2luZyBsaW1pdGVkIHRvIDEwMCBwYWNrZXRzL2VudHJ5 IGJ5IGRlZmF1bHQNCmFkMDogMjQ0MU1CIDxXREMgQUMzMjUwMEg+IFs0OTYw LzE2LzYzXSBhdCBhdGEwLW1hc3RlciBXRE1BMg0KYWQxOiA0MTAzTUIgPFNU MzQzMjFBPiBbODg5NC8xNS82M10gYXQgYXRhMC1zbGF2ZSBXRE1BMg0KYWNk MDogQ0RST00gPFRPU0hJQkEgQ0QtUk9NIFhNLTY2MDJCPiBhdCBhdGExLW1h c3RlciB1c2luZyBXRE1BMg0KTW91bnRpbmcgcm9vdCBmcm9tIHVmczovZGV2 L2FkMHMxYQ0KcGNjYXJkOiBjYXJkIGluc2VydGVkLCBzbG90IDANCndpMDog PFdhdmVMQU4vSUVFRSA4MDIuMTE+IGF0IHBvcnQgMHgyNDAtMHgyN2YgaXJx IDUgc2xvdCAwIG9uIHBjY2FyZDANCndpMDogRXRoZXJuZXQgYWRkcmVzczog MDA6NjA6MWQ6MDM6ZWQ6MDUNCmlwZnc6IDM5MDAgRGVueSBUQ1AgMjQuMTMu MTAxLjEyNzoxMzI1IDI0LjMwLjE0MC41NToxMjM0IGluIHZpYSB2eDANCg== --0-1561284584-975791497=:24235-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 2 13:39:49 2000 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 42F8937B400; Sat, 2 Dec 2000 13:39:41 -0800 (PST) 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 QAA05165; Sat, 2 Dec 2000 16:39:39 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eB2LddK11533; Sat, 2 Dec 2000 16:39:39 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin <gallatin@cs.duke.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 2 Dec 2000 16:39:39 -0500 (EST) To: "Kenneth D. Merry" <ken@kdm.org> Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: PCIOCGETCONF/PCIOCREAD requires write permission? In-Reply-To: <20001201174408.A17122@panzer.kdm.org> References: <200012012056.eB1KuDI32343@orthanc.ab.ca> <20001201174408.A17122@panzer.kdm.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14889.27531.660040.955219@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth D. Merry writes: > As for PCIOCREAD, it only allows reading of PCI registers, so the question > there is whether there are any potential security implications to allowing > non-root users to read PCI registers. If reading configuration registers > caused performance degredation, for instance. I think that you might be able to crash an alpha with an unaligned access trap by reading an int or short an from an unaligned offset in config space. At least this used to be true.. I'd vote for leaving the access permissions as is. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 2 13:43:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 13B7537B401; Sat, 2 Dec 2000 13:43:23 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA10985; Sat, 2 Dec 2000 13:43:23 -0800 Date: Sat, 2 Dec 2000 13:43:18 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> Reply-To: mjacob@feral.com To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: "Kenneth D. Merry" <ken@kdm.org>, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: PCIOCGETCONF/PCIOCREAD requires write permission? In-Reply-To: <14889.27531.660040.955219@grasshopper.cs.duke.edu> Message-ID: <Pine.LNX.4.21.0012021342100.5019-100000@zeppo.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Agreed. Thanks for spotting this, Andrew. No, we should not let users read PCI registers in such a fashion that will cauase the system to crash. > > Kenneth D. Merry writes: > > As for PCIOCREAD, it only allows reading of PCI registers, so the question > > there is whether there are any potential security implications to allowing > > non-root users to read PCI registers. If reading configuration registers > > caused performance degredation, for instance. > > I think that you might be able to crash an alpha with an unaligned > access trap by reading an int or short an from an unaligned offset in > config space. At least this used to be true.. I'd vote for leaving > the access permissions as is. > > Drew > > > 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 Dec 2 14:24:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.wertep.com (relay2.wertep.com [194.44.90.130]) by hub.freebsd.org (Postfix) with ESMTP id 888CE37B400 for <freebsd-hackers@freebsd.org>; Sat, 2 Dec 2000 14:24:30 -0800 (PST) Received: from She.wertep.com (she-tun-proxy [192.168.252.2]) by relay2.wertep.com (8.9.3/8.9.3) with ESMTP id AAA57114 for <freebsd-hackers@freebsd.org>; Sun, 3 Dec 2000 00:24:20 +0200 (EET) (envelope-from petro@She.wertep.com) Received: from localhost (petro@localhost) by She.wertep.com (8.9.3/8.9.3) with ESMTP id AAA18987 for <freebsd-hackers@freebsd.org>; Sun, 3 Dec 2000 00:23:55 +0200 (EET) (envelope-from petro@She.wertep.com) Date: Sun, 3 Dec 2000 00:23:55 +0200 (EET) From: petro <petro@She.wertep.com> To: freebsd-hackers@freebsd.org Subject: Need help on installing FreeBSd 4.1 Message-ID: <Pine.BSF.4.21.0012021801180.18567-100000@She.wertep.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I try to install the FreeBSD 4.1 on the machine after the first attempt fail due to the switch of light. On the second attempt I receive such message the FPU device not available. Tha automatic reboot in 15 seconds..... Thank you very much. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 2 20:38:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orthanc.ab.ca (207-167-15-66.dsl.worldgate.ca [207.167.15.66]) by hub.freebsd.org (Postfix) with ESMTP id D8D4837B400; Sat, 2 Dec 2000 20:38:26 -0800 (PST) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.11.1/8.11.1) with ESMTP id eB34cJm00619; Sat, 2 Dec 2000 21:38:19 -0700 (MST) (envelope-from lyndon@orthanc.ab.ca) Message-Id: <200012030438.eB34cJm00619@orthanc.ab.ca> To: "Kenneth D. Merry" <ken@kdm.org> Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: PCIOCGETCONF/PCIOCREAD requires write permission? In-reply-to: Your message of "Fri, 01 Dec 2000 17:44:08 MST." <20001201174408.A17122@panzer.kdm.org> Date: Sat, 02 Dec 2000 21:38:19 -0700 From: Lyndon Nerenberg <lyndon@orthanc.ab.ca> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Kenneth" == Kenneth D Merry <ken@kdm.org> writes: >> Is there any reason why the FWRITE test cannot/should not be >> moved down into the 'case PCIOCWRITE' part of the switch? This >> would make both PCIOCGETCONF and PCIOCREAD work for readonly >> access to /dev/pci (which seems to me to be saner behaviour). Kenneth> At least with the PCIOCGETCONF, you need write Kenneth> permission, because it copies in patterns to match Kenneth> against. Does that have to equate with write access? Since you aren't changing anything (device-wise) it seems this should be a read-only thing (even though you're actually writing into the kernel memory arena). Kenneth> As for PCIOCREAD, it only allows reading of PCI Kenneth> registers, so the question there is whether there are any Kenneth> potential security implications to allowing non-root Kenneth> users to read PCI registers. If reading configuration Kenneth> registers caused performance degredation, for instance. Yup, this dawned on me later. Meanwhile, though, I've been running with the read-only PCIOCGETCONF patch I suggested and I haven't seen any problems with it after close to a week of use. I've submitted that version as a pair of pr's (one for the kernel, and one for pciconf). --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 2 23: 0:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from newsmangler.inet.tele.dk (nntp118.netscum.dk [193.162.153.118]) by hub.freebsd.org (Postfix) with ESMTP id E082037B400 for <hackers@freebsd.org>; Sat, 2 Dec 2000 23:00:43 -0800 (PST) Received: (from news@localhost) by newsmangler.inet.tele.dk (8.11.1/8.11.1) id eB370XJ22476; Sun, 3 Dec 2000 08:00:33 +0100 (CET) (envelope-from newsuser@free-pr0n.netscum.dk) Date: Sun, 3 Dec 2000 08:00:33 +0100 (CET) Message-Id: <200012030700.eB370XJ22476@newsmangler.inet.tele.dk> X-Authentication-Warning: newsmangler.inet.tele.dk: news set sender to newsuser@free-pr0n.netscum.dk using -f From: News History File User <newsuser@free-pr0n.netscum.dk> Reply-To: freebsd-user@netscum.dk To: hackers@freebsd.org, dillon@earth.backplane.com Subject: Re: vm_pageout_scan badness Cc: usenet@tdk.net References: <200012011918.eB1JIol53670@earth.backplane.com> <200012020525.eB25PPQ92768@newsmangler.inet.tele.dk> <200012021904.eB2J4An63970@earth.backplane.com> In-Reply-To: <200012021904.eB2J4An63970@earth.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :but at last look, history lookups and writes are accounting for more > :than half (!) of the INN news process time, with available idle time > :being essentially zero. So... > > No idle time? That doesn't sound like blocked I/O to me, it sounds > like the machine has run out of cpu. Um, I knew I'd be unclear somehow. The machine itself (with 2 CPUs) has plenty of idle time -- `top' reports typically 70-80% idle, and INN takes from 20-40% of CPU (being SMP, a process like `perl' locked to one CPU will appear around 98%, unlike a certain other OS that will show this percentage for the system total, rather than for a particular CPU). What I mean is that the INN process timer, which is basically Joe Greco's timer that wraps key functions with start/stop timer calls, showing where INN spends much of its time, is showing little to no idle time (meaning it couldn't take more articles in no matter how hard I push them). Let me show you the timer stats from the time I started things not long ago on this reader machine, where it's taking in backlogs: Dec 3 04:33:47 crotchety innd: ME time 300449 idle 376(4577) all times in milliseconds: elapsed time^^^^^^=5min ^^^idle time (numbers in parentheses are number of calls; only significant in calls like artwrite to show how many articles were actually written to spool, hiswrite to show how many unique articles were received over this time period, and hishave to show how many history lookups were done) artwrite 52601(6077) artlink 0(0) hiswrite 40200(7035) hissync 11(14) ^^^ 53 seconds writing articles ^^ 40 seconds updating history sitesend 647(12154) artctrl 2297(308) artcncl 2288(308) hishave 38857(26474) 39 seconds doing history lookups ^^ hisgrep 70(111) artclean 12264(6930) perl 13819(6838) overv 112176(6077) python 0(0) ncread 13818(21287) ncproc 284413(21287) Dec 3 04:38:48 crotchety innd: ME time 301584 idle 406(5926) artwrite 55774(6402) artlink 0(0) hiswrite 25483(7474) hissync 15(15) sitesend 733(12805) artctrl 1257(322) artcncl 1245(321) hishave 22114(28196) hisgrep 90(38) artclean 12757(7295) perl 14696(7191) overv 136855(6402) python 0(0) ncread 14446(23235) ncproc 284767(23235) (as time passes and more of the MAP_NOSYNC file is in memory, the time needed for history writes/lookups drops) [...] Dec 3 04:58:49 crotchety innd: ME time 300047 idle 566(6272) artwrite 59850(6071) artlink 0(0) hiswrite 11630(6894) hissync 33(14) sitesend 692(12142) artctrl 324(244) artcncl 320(244) hishave 13614(24312) hisgrep 0(77) artclean 13232(6800) perl 14531(6727) overv 156723(6071) python 0(0) ncread 15116(23838) ncproc 281745(23838) Dec 3 05:03:49 crotchety innd: ME time 300018 idle 366(5936) artwrite 56956(6620) artlink 0(0) hiswrite 8850(7749) hissync 7(15) sitesend 760(13240) artctrl 255(160) artcncl 255(160) hishave 9944(25198) hisgrep 0(31) artclean 13441(7753) perl 15605(7620) overv 164223(6620) python 0(0) ncread 14783(24123) ncproc 282791(24123) Most of the time is spent on the BerkeleyDB overview now. This is probably because some reader is giving repeated commands pounding the overview database. <clickety-click> That reader's IP now has a different gateway address, and won't be bothering me for a while. Now, for a reference, here are the timings on a transit-only machine with no readers, after it's been running for a while: Dec 3 05:22:09 news-feed69 innd: ME time 300000 idle 91045(91733) a reasonable amount of idle time ^^ artwrite 48083(2096) artlink 0(0) hiswrite 1639(2096) hissync 33(11) ^^^^ sitesend 4291(12510) artctrl 0(0) artcncl 0(0) hishave 1600(30129) ^^^^ hisgrep 0(0) artclean 25591(2121) perl 79(2096) overv 0(0) python 0(0) ncread 69798(147925) ncproc 108624(147919) A total of just over 3 seconds out of every 300 seconds spent on history activity. That's reflected by the timestamps on the NOSYNC'ed history database (index/hash) files you see here: -rw-rw-r-- 1 news news 436206889 Dec 3 05:22 history -rw-rw-r-- 1 news news 67 Dec 3 05:22 history.dir -rw-rw-r-- 1 news news 81000000 Dec 1 01:55 history.hash -rw-rw-r-- 1 news news 54000000 Nov 30 22:49 history.index However, the timings shown by `top' here show from 10 to 20% idle CPU time, even though INN itself has capacity to do more work. The problem is that I'm not seeing this on the reader box. Or if I do see it, it doesn't last long. The timestamps on the above files are pretty much current, in spite of the files being NOSYNC'ed. > :As is to be expected, INN increases in size as it does history lookups > :and updates, and the amount of memory shown as Active tracks this, > :more or less. But what's happening to the Free value! It's going > :down at as much as 4MB per `top' interval. Or should I say, what is > :happening to the Inactive value -- it's constantly increasing, and I > :observe a rapid migration of all the Free memory to Inactive, until > :the value of Inactive peaks out at the time that Free drops to about > :996k, beyond which it changes little. None of the swap space has > :been touched yet. > : > :As soon as the value for Free hits bottom and that of Inactive has > :reached a max, now the migration happens from Inactive to Active -- > :until this point, the value of Active has been roughly what I would > :expect to see, given the size of the history hash/index files, and > :the BerkeleyDB file I'm now using MAP_NOSYNC as well for a definite > :improvement in overview access times. > > Hmm. An increasing 'inactive' most often occurs when a program > is reading a file sequentially. It sounds like most of the inactive > pages are probably due to reader requests from the spool. Either that, or the access to the BerkeleyDB overview data -- I think I see the same poor performance even when I'm not allowing readers. Or maybe not. Even if the performance doesn't suck, the timestamps on the files get updated periodically. I took a look at all three machines with NOSYNC, and noted that the one doing best (with the `ls' of history above) has vm source from 26.Nov, while the reader machine doing poorly had source files from only 25.Nov -- a third machine with 256MB RAM that is doing pretty well, but could do better, has source from 21.Nov. So the machines were not as closely in sync as I thought. Just in case, I rebuilt the reader machine so that the vm sourcefiles are current as of 02.Dec to get your latest changes. I still see the same less-than-ideal performance, although perhaps it's not quite as bad as earlier. But in general, all the memory migrates to Inactive and from there to Active within 15 minutes after startup. And after shutdown, and `fsync'ing the three MAP_NOSYNC'ed files, there still remains about 300MB as Active, while just under 400MB while it was running. More observations that may or may not mean anything -- before rebooting, I timed the `fsync' commands on the 108MB and 72MB history files, as well as the 18MB BerkeleyDB file, as well as watching to see how much of the Active memory was released by the commands. It looked as if, for a given size file, about 1/3 of its size was released from Active. In other words, on an idle system, `fsyncing' the 108MB file that should have been pretty much completely dirty, except that probably much of the dirt was being written to disk since it's not working as well as I would like, caused the Active `top' value to drop about 30MB. The time taken to do the `fsync' was around one minute for the two history files. And around 1 second for the BerkeleyDB file... Thing is, when I had rebooted (and saw the disk activity), I'm sure it took much longer, like 5 minutes or so total. Could be true, if I hadn't been flushing data in operation and there were more dirty pages needing to be written. Another confusing thing (and one time, when I didn't know what was going on, I thought the machine had hung and powered it off) is that dumping the data to disk at reboot time happens after the `done' for the `sycning filesystems' message. Perhaps, if there is data to be written, you might make note of this, writing something like `flushing whatever cache' to the console, just so people know something is in fact happening and It is now^Ht safe to turn off your computer. I had no disk activity light at the time, so... well, I was young and foolish If what you say, that data being read, is responsible for the NOSYNC data getting flushed to disk, then it seems like someone's priorities are a bit, well, wrong. The way I see it, by giving the MAP_NOSYNC flag, I'm sort of asking for preferential treatment, kinda like mlock, even though that's not available to me as `news' user. It seems like this MAP_NOSYNC'ed data should not be flushed if it's possible to get at some other data instead, most likely the recently- read Inactive data. Or something. Anything. Now, if necessary, you want to dump the NOSYNC data if you absolutely can't squeeze something out of the Inactive, (even Active? why else does it take nearly 400MB on this machine?) or cached data. So, I only have a small number of readers now (it's a party night in the Real World and at least some people have lives) and the timer stats have dropped to the numbers I expect to see, and the history drive is relatively quiet too: Dec 3 05:38:50 crotchety innd: ME time 300000 idle 30790(280652) artwrite 101349(3788) artlink 0(0) hiswrite 2089(3970) hissync 31(8) 2 seconds to update the history data... ^^^^ sitesend 459(7576) artctrl 131(51) artcncl 128(51) hishave 2777(50732) 50 thousand history lookups in less than 3 seconds. ^^^^ hisgrep 0(39) artclean 29821(4017) perl 16754(3958) overv 24979(3788) python 0(0) ncread 51580(326712) ncproc 198077(326712) Dec 3 05:53:50 crotchety innd: ME time 300006 idle 34595(293538) artwrite 98618(3534) artlink 0(0) hiswrite 2240(3775) hissync 68(8) ^^^^ sitesend 426(7068) artctrl 6(46) artcncl 5(46) hishave 596(11155) 11 thousand lookups in half a second? Fine with me ^^^ hisgrep 0(15) artclean 29846(3783) perl 16481(3744) overv 26877(3534) python 0(0) ncread 52778(332500) ncproc 192343(332500) Now, to see why I was complaining earlier, look at the timings I was seeing when I had a lot more readers: Dec 2 19:29:42 crotchety innd: ME time 301953 idle 12098(86714) artwrite 59150(2740) artlink 0(0) hiswrite 67383(3165) hissync 55(6) ^^^^^ sitesend 1832(5480) artctrl 335(34) artcncl 335(34) hishave 40609(8383) ^^^^^ hisgrep 64(19) artclean 20805(3224) perl 12700(3150) overv 38256(2740) python 0(0) ncread 30335(113433) ncproc 252639(113433) Dec 2 19:44:42 crotchety innd: ME time 300038 idle 9646(54390) artwrite 48827(2738) artlink 0(0) hiswrite 75731(3058) hissync 56(6) ^^^^^ sitesend 1885(5476) artctrl 3203(85) artcncl 3201(85) hishave 46630(7721) ^^^^^ hisgrep 17(11) artclean 16708(3065) perl 11078(2984) overv 48362(2738) python 0(0) ncread 24070(73708) ncproc 261521(73708) Dec 2 19:54:46 crotchety innd: ME time 304435 idle 6508(48280) artwrite 51075(2854) artlink 0(0) hiswrite 63032(3265) hissync 55(7) A minute for history updates? ^^ sitesend 3460(5708) artctrl 5587(154) artcncl 5587(154) hishave 53840(9316) And a minute for history lookups too? No thanks ^^ hisgrep 760(71) artclean 17761(3205) perl 12072(3182) overv 51383(2854) python 0(0) ncread 24904(69630) ncproc 268419(69630) > :lack of space today when I attempted to run both expire and makedbz (a > :variant of makehistory), and apparently some reader processes or some > :daemons still had the old inodes open, until suddenly in one swell foop, > :some 750MB was freed up -- far more than I expected to see, so I should > > Woa. 750MB? There are only two things that can cause that: > * A large (500+ MB) file is deleted after having previously been > mmap()'d. (or the process holding the last open descriptor to > the file, after deletion, now exits). > > If I remember INN right, there is a situation that can occur here... the > reader processes open up the history file in order to implement a certain > NNTP commands. I'm trying to remember which one... I think its one of > search commands. Fubar... anyone remember which NNTP command opens > up the history file? In anycase, I remember at BEST I had to completely > disable that command when running INN because it caused long-running > reader processes to keep a descriptor open on now-deleted history files. > When you do an expire run which replaces the history file, the original > (now deleted) history file may still be open by those reader processes. Yeah, I realized yesterday morning, after a bit of chocolate, that that was probably what I was seeing. I'm in desperate need of sleep to think straight -- I'm having to reread your messages about five times after answering them and still finding new things. Urk. There were two readers at the time -- myself, and a cow-orker of mine. I fetch messages by `ARTICLE <msg-ID>' which of course hits the history file. I don't remember offhand if nnrpd initially grabs ahold of the file and doesn't let go. There have been a number of changes so that there may well be cases where the history file is held open by processes now where it hadn't been at the time you had your hands dirtied by it. So this is almost certainly an unrelated thing to the absence of available memory I was seeing. Now, back to the sometimes-awful MAP_NOSYNC performance -- there are a few differences in the way it's running now, where it behaves itself nicely, and the way I had run it before: * The kernel has your commits from 26.Nov up through 02.Dec. * I have only five readers now, not 50, since starting. * I didn't start INN immediately after boot this time. Instead, INN had been running for a while, then I shut it down, ran expire by hand, and then started INN after other processes had had a chance to fill up the cache with whatever, if this would make any difference. Time will tell how much the second factor has to do with the stellar performance I see now. > abusers, by the way, which try to download feeds via their reader > access) are enabled. I would immediately research this... look for > reader processes that have hung around too long and try killing them, > then see if that clears out some memory. As far as system memory is concerned, I've killed all nnrpd processes when I shut things down, so all news-related processes have stopped. It hasn't made much difference in the `top' Active value. > There will also be a serious file fragmentation issue using MAP_NOSYNC > in the expire process. You can probably use MAP_NOSYNC safely in the > INND core, but don't use it to rebuild the history file in the expire > process. Ah, okay, thanks. I'll check into this. It used to be that there would be problems if you defined MMAP for INN proper years ago, and that define was used when building expire, so one had to manually fudge makefiles or something to build expire without mmap. I think this is much simpler now and by default mmap isn't used in expire. If so, this might be okay. However, I've added the MAP_NOSYNC to the MAP__ARGS in lib/dbz.c, so I really need to check expire. The places where one isn't dealing with a fixed history database size are -- * creating the initial database files, or rebuilding them (makedbz, which used to be the function of makehistory) * overflows in the hash table, where the fixed database files grow in size as additional tables are added -- these additional tables are not incore, though, last I looked * expire, as you note, creating new databases a la makedbz (Weird, I just ran news.daily, which invoked expireover and should have invoked expire, but it didn't seem to happen. So the good timings I'm seeing now are not on a potentially fragmented file. Hmmm.) Thanks for your help, if performance stays Good, or if it starts to fall through the floor again, you'll hear about it... barry bouwsma, will watch news swervers like a hawk for food -- HI! ME AGA1N!!! As Murphy would have it, shortly after I finished writing the above, history performance started to suck, even with six readers, and the history drive light is getting a beating. I've killed off readers except for myself, of course, to see if things improve, but here are recent timings so you can see why my eyes well with tears: Dec 3 07:28:51 crotchety innd: ME time 300047 idle 16801(186367) artwrite 85200(3320) artlink 0(0) hiswrite 31568(3581) hissync 44(8) ^^^^^ sitesend 399(6640) artctrl 5935(340) artcncl 5928(340) hishave 31975(11904) ^^^^^ hisgrep 4259(289) artclean 25148(3567) perl 14955(3530) overv 21593(3320) python 0(0) ncread 39087(226379) ncproc 229931(226379) Oh well. Up from a couple seconds of history activity to more than one out of every five minutes... *sigh* (gack, now up to 90 seconds) I would say that something needs to be done to avoid losing those pages that have been MAP_NOSYNC'ed, assuming this isn't already being done. They appear to be treated as just any other page now, which isn't such a good idea. Perhaps kind of a weak mlock, maybe. If I'm not completely mistaken. Anyway, now the two history times are taking 140+ out of 300 seconds and getting worse. Without readers. So I'm going to send this off before things get worse and do something, like sleep, maybe... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 2 23:31: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whizkidtech.net (r20.bfm.org [216.127.220.116]) by hub.freebsd.org (Postfix) with ESMTP id 5624D37B400 for <hackers@FreeBSD.org>; Sat, 2 Dec 2000 23:31:00 -0800 (PST) Received: (from adam@localhost) by whizkidtech.net (8.9.2/8.9.2) id BAA00252; Sun, 3 Dec 2000 01:29:42 -0600 (CST) (envelope-from adam) Date: Sun, 3 Dec 2000 01:28:41 -0600 From: "G. Adam Stanislav" <adam@whizkidtech.net> To: Wes Peters <wes@softweyr.com> Cc: Charlie & <root@int80h.org>, hackers@FreeBSD.org Subject: Re: pipe Message-ID: <20001203012841.B228@whizkidtech.net> References: <20001202085127.A301@int80h.org> <3A292D98.E655D755@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3A292D98.E655D755@softweyr.com>; from wes@softweyr.com on Sat, Dec 02, 2000 at 10:12:56AM -0700 Organization: Whiz Kid Technomagic X-URL: http://www.whizkidtech.net/ X-Castle: http://www.redprince.net/ X-Special-Effects: http://www.FilmSFX.com/ X-Operating-System: FreeBSD whizkidtech.net 3.1-RELEASE FreeBSD 3.1-RELEASE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 02, 2000 at 10:12:56AM -0700, Wes Peters wrote: >Yes, you can read from your own pipe, and yes the buffering availabe in >the pipe is limited. IIRC, the pipe size is 8K. Thank you. In that case I'll be better off using child processes for what I am working on. But I will use pipes from within a process whenever I know that my data will not grow larger than 8K. Adam -- A billion dollars in the bank, without the experience of carefreeness and charity, is a state of poverty. -- Deepak Chopra To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message