From owner-freebsd-hackers Sun Dec 10 0:23: 2 2000 From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 10 00:22:57 2000 Return-Path: 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 B5FA537B400; Sun, 10 Dec 2000 00:22:56 -0800 (PST) Received: from newsguy.com (p23-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.24]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id RAA21674; Sun, 10 Dec 2000 17:22:54 +0900 (JST) Message-ID: <3A333CE4.5B9FDA92@newsguy.com> Date: Sun, 10 Dec 2000 17:20:52 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: stable@FreeBSD.ORG Cc: "Chad R. Larson" , hackers@FreeBSD.ORG Subject: Re: PCIOCGETCONF/PCIOCREAD requires write permission? References: <200012080707.AAA12102@freeway.dcfinc.com> <20001208115004.B81619@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Fri, Dec 08, 2000 at 12:07:49AM -0700, Chad R. Larson wrote: > > I thought the space staked out by the *BSD gang was approximately > > this: > > NetBSD - the least amount of platform-specific code possible; run > > on most anything > > OpenBSD - pro-active security, bullet-proof from attacks > > FreeBSD - best performing on the Intel PC platform > > s/the Intel PC/server/ The Alpha has very good I/O bandwidth and 64-bit > address space. Thus it fits our niche. You also mentioned Sparc, but > really should have said sparc64(pci based). > > hopefully embeded soon too. Yep, "server" is much more to the point. And not simply best performing, but we also strive to be user-friendly. The bottomline is that we, of the BSDs, do *not* have a focus. We want to support good servers and good desktops and good notebooks, we want to provide performance and user friendlyness. We do not care about being ported to every hardware platform under sun, and we do not go out of our way to provide security. Thus, NetBSD and OpenBSD have the edge on us on these respects, but we gain by providing a better overall enviroment on the platforms we support. The problem is that you can't one-line that. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.great.underground.bsdconpiracy.org "The bronze landed last, which canceled that method of impartial choice." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 10 1: 2: 4 2000 From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 10 01:02:01 2000 Return-Path: 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 173F537B400; Sun, 10 Dec 2000 01:02:00 -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 eBA91ss62134; Sun, 10 Dec 2000 02:01:55 -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 CAA27464; Sun, 10 Dec 2000 02:01:54 -0700 (MST) Message-Id: <200012100901.CAA27464@harmony.village.org> To: "Daniel C. Sobral" Subject: Re: PCIOCGETCONF/PCIOCREAD requires write permission? Cc: stable@FreeBSD.ORG, "Chad R. Larson" , hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 10 Dec 2000 17:20:52 +0900." <3A333CE4.5B9FDA92@newsguy.com> References: <3A333CE4.5B9FDA92@newsguy.com> <200012080707.AAA12102@freeway.dcfinc.com> <20001208115004.B81619@dragon.nuxi.com> Date: Sun, 10 Dec 2000 02:01:53 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A333CE4.5B9FDA92@newsguy.com> "Daniel C. Sobral" writes: : ported to every hardware platform under sun, and we do not go out of our : way to provide security. Thus, NetBSD and OpenBSD have the edge on us on What? I don't see how you can say that about security... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 10 1:39:58 2000 From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 10 01:39:55 2000 Return-Path: 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 2489537B401; Sun, 10 Dec 2000 01:39:54 -0800 (PST) Received: from newsguy.com (p23-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.24]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id SAA03992; Sun, 10 Dec 2000 18:39:49 +0900 (JST) Message-ID: <3A334EEB.5833CE81@newsguy.com> Date: Sun, 10 Dec 2000 18:37:47 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Warner Losh Cc: stable@FreeBSD.ORG, "Chad R. Larson" , hackers@FreeBSD.ORG Subject: Re: PCIOCGETCONF/PCIOCREAD requires write permission? References: <3A333CE4.5B9FDA92@newsguy.com> <200012080707.AAA12102@freeway.dcfinc.com> <20001208115004.B81619@dragon.nuxi.com> <200012100901.CAA27464@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <3A333CE4.5B9FDA92@newsguy.com> "Daniel C. Sobral" writes: > : ported to every hardware platform under sun, and we do not go out of our > : way to provide security. Thus, NetBSD and OpenBSD have the edge on us on > > What? I don't see how you can say that about security... We don't go *out* of our way. And just because OpenBSD has an *edge*, that doesn't mean said edge is all that big. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.great.underground.bsdconpiracy.org "The bronze landed last, which canceled that method of impartial choice." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 10 4:42:35 2000 From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 10 04:42:33 2000 Return-Path: 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 424AC37B401 for ; Sun, 10 Dec 2000 04:42:33 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eBACgWP23479 for hackers@freebsd.org; Sun, 10 Dec 2000 04:42:32 -0800 (PST) Date: Sun, 10 Dec 2000 04:42:32 -0800 From: Alfred Perlstein To: hackers@freebsd.org Subject: Patching live kernels Message-ID: <20001210044232.D16205@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: bright@fw.wintelcom.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, sometimes we find a bug in a particular release where what's needed is a function replaced with fixed code. I'm wondering if it's possible to: 1) look at the kernel symbol table for a particular function in a particular object file (static functions would be even better?) 2) replace the first instruction in the function with a jmp to our newly loaded code 3) have our newly loaded code be "anonymous" meaning no symbols from it enter the kernel symbol namespace (i want to be able to re-patch a patched kernel) Is it possible? Are there any takers? :) -- -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 Sun Dec 10 10:36:13 2000 From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 10 10:36:07 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from io.yi.org (unknown [24.70.218.157]) by hub.freebsd.org (Postfix) with ESMTP id 5203F37B400 for ; Sun, 10 Dec 2000 10:36:06 -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 5DD3FBA7D; Sun, 10 Dec 2000 10:36:05 -0800 (PST) X-Mailer: exmh version 2.1.1 10/15/1999 To: Alfred Perlstein Cc: hackers@FreeBSD.ORG Subject: Re: Patching live kernels In-Reply-To: Message from Alfred Perlstein of "Sun, 10 Dec 2000 04:42:32 PST." <20001210044232.D16205@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_-6582008560" Date: Sun, 10 Dec 2000 10:36:05 -0800 From: Jake Burkholder Message-Id: <20001210183605.5DD3FBA7D@io.yi.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_-6582008560 Content-Type: text/plain; charset=us-ascii > Ok, sometimes we find a bug in a particular release where what's > needed is a function replaced with fixed code. > > I'm wondering if it's possible to: > > 1) look at the kernel symbol table for a particular function in a > particular object file (static functions would be even better?) > 2) replace the first instruction in the function with a jmp to > our newly loaded code > 3) have our newly loaded code be "anonymous" meaning no symbols > from it enter the kernel symbol namespace (i want to be able to > re-patch a patched kernel) > > Is it possible? > > Are there any takers? :) io# kldload ./syscall.ko Dec 10 10:09:14 io /boot/kernel/kernel: syscall loaded at 210 io# ./call Dec 10 10:09:26 io /boot/kernel/kernel: bad code... (kgdb) x/6i bad_code 0xc01235a0 : push %ebp 0xc01235a1 : mov %esp,%ebp 0xc01235a3 : push $0xc02cc6d0 0xc01235a8 : call 0xc0198a30 0xc01235ad : leave 0xc01235ae : ret (kgdb) x/s 0xc02cc6d0 0xc02cc6d0 <__umoddi3+672>: "bad code...\n" io# kldload ./kpatch.ko io# ./kpatch -f bad_code -t good_code Dec 10 10:11:24 io /boot/kernel/kernel: patching from: 0xc01235a0 to: 0xc0fbd4c4 (kgdb) x/i bad_code 0xc01235a0 : jmp 0xc0fbd4c4 (kgdb) x/6i 0xc0fbd4c4 0xc0fbd4c4: push %ebp 0xc0fbd4c5: mov %esp,%ebp 0xc0fbd4c7: push $0xc0fbd528 0xc0fbd4cc: call 0xc0198a30 0xc0fbd4d1: leave 0xc0fbd4d2: ret (kgdb) x/s 0xc0fbd528 0xc0fbd528: "good code!!\n" io# ./call Dec 10 10:13:17 io /boot/kernel/kernel: good code!! I'm not sure if static functions are in the kernel symbol table, but you should be able to get the address with nm and pass it to kpatch instead of the name, ./kpatch -f 0x... -t good_code; this is untested. Whatever symbols are in your module will still be in the kernel symbol table, removing them is more involved but not impossible, all the magic is in kern/kern_linker.c. Just rename whatever function you are loading, repatch, and then unload the old module. If you can ensure that nothing will call the loaded code while you're repatching you should be able to unload first to avoid the renaming. Use with extreme caution. Release, pff, you don't fool me :) Jake --==_Exmh_-6582008560 Content-Type: text/plain ; name="Makefile"; charset=us-ascii Content-Description: Makefile Content-Disposition: attachment; filename="Makefile" # Makefile for building the sample syscall module SRCS = kpatch-sys.c KMOD = kpatch KO = ${KMOD}.ko KLDMOD = t kpatch: cc -o kpatch kpatch.c CLEANFILES+= kpatch .include CFLAGS= -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpreferred-stack-boundary=2 --==_Exmh_-6582008560 Content-Type: text/plain ; name="kpatch.c"; charset=us-ascii Content-Description: kpatch.c Content-Disposition: attachment; filename="kpatch.c" #include #include #include #include #include #include #include #include #include #include #include #include extern char *optarg; extern int optind; static void usage(void); int main(int ac, char **av) { struct kld_sym_lookup from; struct kld_sym_lookup to; struct module_stat stat; int kfid; int mfid; int c; bzero(&from, sizeof from); bzero(&stat, sizeof stat); bzero(&to, sizeof to); from.version = sizeof from; stat.version = sizeof stat; to.version = sizeof to; while ((c = getopt(ac, av, "f:t:")) != -1) switch (c) { case 'f': if (bcmp(optarg, "0x", 2) == 0) from.symvalue = strtol(optarg, NULL, 16); else from.symname = optarg; break; case 't': if (bcmp(optarg, "0x", 2) == 0) to.symvalue = strtol(optarg, NULL, 16); else to.symname = optarg; break; case '?': default: usage(); } if (from.symvalue == 0) { kfid = kldfind("kernel"); kldsym(kfid, KLDSYM_LOOKUP, &from); } if (to.symvalue == 0) { for (mfid = 0; (mfid = kldnext(mfid)) != 0;) if (to.symvalue == 0 && kldsym(mfid, KLDSYM_LOOKUP, &to) == 0) break; } printf("from: 0x%lx to: 0x%lx\n", from.symvalue, to.symvalue); modstat(modfind("kpatch"), &stat); return syscall(stat.data.intval, from.symvalue, to.symvalue); } static void usage(void) { fprintf(stderr, "usage: kpatch -f -t \n"); exit(EX_USAGE); } --==_Exmh_-6582008560 Content-Type: text/plain ; name="kpatch-sys.c"; charset=us-ascii Content-Description: kpatch-sys.c Content-Disposition: attachment; filename="kpatch-sys.c" #include #include #include #include #include #include #include extern char do_jmp[]; extern char do_jmp_end[]; asm( " .globl do_jmp ; " "do_jmp: " " jmp . + 1 << 16 ; " " .globl do_jmp_end ; " "do_jmp_end: " ); struct kpatch_args { char * from; char * to; }; static int kpatch(struct proc *p, struct kpatch_args *uap) { printf("patching from: %p to: %p\n", uap->from, uap->to); bcopy(do_jmp, uap->from, do_jmp_end - do_jmp); uap->from++; *(int *)uap->from = uap->to - uap->from - 4; return 0; } static struct sysent kpatch_sysent = { 2, (sy_call_t *)kpatch }; static int offset = NO_SYSCALL; static int kpatch_load(struct module *module, int cmd, void *arg) { int error = 0; switch (cmd) { case MOD_LOAD: printf("kpatch loaded at %d\n", offset); break; case MOD_UNLOAD: printf("kpatch unloaded from %d\n", offset); break; default: error = EINVAL; break; } return error; } SYSCALL_MODULE(kpatch, &offset, &kpatch_sysent, kpatch_load, NULL); --==_Exmh_-6582008560-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 10 12: 8:53 2000 From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 10 12:08:51 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id A81B637B6A0 for ; Sun, 10 Dec 2000 12:08:49 -0800 (PST) Received: from localhost (arr@localhost) by fledge.watson.org (8.11.1/8.11.1) with SMTP id eBAK8Ww28011; Sun, 10 Dec 2000 15:08:32 -0500 (EST) (envelope-from arr@watson.org) Date: Sun, 10 Dec 2000 15:08:31 -0500 (EST) From: "Andrew R. Reiter" To: Alfred Perlstein Cc: hackers@FreeBSD.ORG, silvio@big.net.au Subject: Re: Patching live kernels In-Reply-To: <20001210044232.D16205@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 afaik, Yes. There are two articles that I know of that deal with the specifics of modifying binaries to inject ones own code. The first is one that deals mostly with libbfd (binary file descriptor) and linux. iirc, libbfd worked a great deal better under linux than under FreeBSD. I recall that libbfd under FreeBSD only supported a.out format. (yikes!) This article can be viewed at: http://phrack.infonexus.com/search.phtml?view&article=p56-9 The second article that I know of deals with hijacking functions in the kernel even if they do not have a function ptr to them. Obviously functions that have ptrs to them can easily be hijacked via a KLD (check out the examples.tar.gz in the Daemonnews article on KLDs). However, I am not sure if the author has yet published this article and I don't feel it my place to publish it for him. Perhaps, silvio, the author, will want to publish it here ;) Anyway, hope this helps. Andrew On Sun, 10 Dec 2000, Alfred Perlstein wrote: > Ok, sometimes we find a bug in a particular release where what's > needed is a function replaced with fixed code. > > I'm wondering if it's possible to: > > 1) look at the kernel symbol table for a particular function in a > particular object file (static functions would be even better?) > 2) replace the first instruction in the function with a jmp to > our newly loaded code > 3) have our newly loaded code be "anonymous" meaning no symbols > from it enter the kernel symbol namespace (i want to be able to > re-patch a patched kernel) > > Is it possible? > > Are there any takers? :) > > -- > -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 > *-------------................................................. | Andrew R. Reiter | arr@fledge.watson.org | "It requires a very unusual mind | to undertake the analysis of the obvious" -- A.N. Whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 10 12:56:24 2000 From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 10 12:56:23 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from www.newsindex.com (www.newsindex.com [64.71.138.178]) by hub.freebsd.org (Postfix) with ESMTP id DB27C37B400 for ; Sun, 10 Dec 2000 12:56:22 -0800 (PST) Received: from localhost (speck@localhost) by www.newsindex.com (8.9.3/8.9.3) with ESMTP id MAA83948 for ; Sun, 10 Dec 2000 12:56:12 -0800 (PST) (envelope-from speck@www.newsindex.com) Date: Sun, 10 Dec 2000 12:56:12 -0800 (PST) From: Sean Peck To: freebsd-hackers@freebsd.org Subject: subscribe Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: speck@www.newsindex.com 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 Sun Dec 10 14:32:38 2000 From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 10 14:32:34 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from www.newsindex.com (www.newsindex.com [64.71.138.178]) by hub.freebsd.org (Postfix) with ESMTP id 267C237B400; Sun, 10 Dec 2000 14:32:34 -0800 (PST) Received: from localhost (speck@localhost) by www.newsindex.com (8.9.3/8.9.3) with ESMTP id OAA92497; Sun, 10 Dec 2000 14:32:24 -0800 (PST) (envelope-from speck@www.newsindex.com) Date: Sun, 10 Dec 2000 14:32:24 -0800 (PST) From: Sean Peck To: freebsd-hackers@freebsd.org Cc: freebsd-questions@freebsd.org Subject: Configuring Gateway/NAT on Freebsd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: speck@www.newsindex.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to configure a FreeBSD 3.3 box to act as a gateway/NAT translater for my network. I have added the following to the my rc.conf ifconfig_tun0="inet 172.168.0.1 netmask 255.255.255.0" gateway_enabled="YES" natd_enabled="YES" natd_ingerface="tun0" and tun0 to my network_interfaces list. The box works fine on its own, but I am unable to get boxes in my 172.168.0.x space to work through it. I am confused a bit on what I need to set my other boxes too, and if I am missing something on this box I must do as well. Should I set my other boxes to gateway to this boxes 172 address, or to the real IP of this box? If it is in the 172 space, how is this box being informed it shoul be listening for it, since the only the tun0 is told it is attached to this IP, not the actual NIC... Any help would be most appreciated. Sean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 10 17: 1:32 2000 From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 10 17:01:28 2000 Return-Path: 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 41A7937B400; Sun, 10 Dec 2000 17:01:27 -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 145HOi-0000C8-00; Sun, 10 Dec 2000 18:04:56 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A342838.2345F03@softweyr.com> Date: Sun, 10 Dec 2000 18:04:56 -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: "Daniel C. Sobral" Cc: stable@FreeBSD.ORG, "Chad R. Larson" , hackers@FreeBSD.ORG Subject: Re: PCIOCGETCONF/PCIOCREAD requires write permission? References: <200012080707.AAA12102@freeway.dcfinc.com> <20001208115004.B81619@dragon.nuxi.com> <3A333CE4.5B9FDA92@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > > David O'Brien wrote: > > > > On Fri, Dec 08, 2000 at 12:07:49AM -0700, Chad R. Larson wrote: > > > I thought the space staked out by the *BSD gang was approximately > > > this: > > > NetBSD - the least amount of platform-specific code possible; run > > > on most anything > > > OpenBSD - pro-active security, bullet-proof from attacks > > > FreeBSD - best performing on the Intel PC platform > > > > s/the Intel PC/server/ The Alpha has very good I/O bandwidth and 64-bit > > address space. Thus it fits our niche. You also mentioned Sparc, but > > really should have said sparc64(pci based). > > > > hopefully embeded soon too. > > Yep, "server" is much more to the point. And not simply best performing, > but we also strive to be user-friendly. > > The bottomline is that we, of the BSDs, do *not* have a focus. We want > to support good servers and good desktops and good notebooks, we want to > provide performance and user friendlyness. We do not care about being > ported to every hardware platform under sun, and we do not go out of our > way to provide security. Thus, NetBSD and OpenBSD have the edge on us on > these respects, but we gain by providing a better overall enviroment on > the platforms we support. The problem is that you can't one-line that. BSD for the masses. -- "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 Sun Dec 10 17: 8: 0 2000 From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 10 17:07:57 2000 Return-Path: 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 A468737B400; Sun, 10 Dec 2000 17:07:53 -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 145HUn-0000CG-00; Sun, 10 Dec 2000 18:11:13 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A3429B0.A389F032@softweyr.com> Date: Sun, 10 Dec 2000 18:11:12 -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: "Daniel C. Sobral" Cc: Warner Losh , stable@FreeBSD.ORG, "Chad R. Larson" , hackers@FreeBSD.ORG Subject: Re: PCIOCGETCONF/PCIOCREAD requires write permission? References: <3A333CE4.5B9FDA92@newsguy.com> <200012080707.AAA12102@freeway.dcfinc.com> <20001208115004.B81619@dragon.nuxi.com> <200012100901.CAA27464@harmony.village.org> <3A334EEB.5833CE81@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > > Warner Losh wrote: > > > > In message <3A333CE4.5B9FDA92@newsguy.com> "Daniel C. Sobral" writes: > > : ported to every hardware platform under sun, and we do not go out of our > > : way to provide security. Thus, NetBSD and OpenBSD have the edge on us on > > > > What? I don't see how you can say that about security... > > We don't go *out* of our way. And just because OpenBSD has an *edge*, > that doesn't mean said edge is all that big. FreeBSD balances security concerns with usability, whereas OpenBSD goes for the "security" choice every time. This makes one of the systems more secure without user tuning, the other more functional without user tuning. -- "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 Sun Dec 10 18:59:40 2000 From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 10 18:59:38 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10]) by hub.freebsd.org (Postfix) with ESMTP id AE50637B400 for ; Sun, 10 Dec 2000 18:59:38 -0800 (PST) Received: from esoha-nt.cisco.com (esoha-nt.cisco.com [171.69.38.13]) by sj-msg-core-4.cisco.com (8.9.3/8.9.1) with ESMTP id SAA03978 for ; Sun, 10 Dec 2000 18:59:39 -0800 (PST) Received: (from esoha@localhost) by esoha-nt.cisco.com (8.9.3/8.9.3) id SAA00633; Sun, 10 Dec 2000 18:59:37 -0800 (PST) (envelope-from esoha@cisco.com) From: Eyal Soha MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14900.17177.554270.834023@esoha-nt.cisco.com> Date: Sun, 10 Dec 2000 18:59:37 -0800 To: freebsd-hackers@freebsd.org Subject: kern/23409, atapi_queue_cmd error codes? X-Mailer: VM 6.76 under Emacs 20.7.1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I submitted and started debugging kern/23409: CD-RW driver fails unless CD in drive at boot up. I seem to be getting error code 0x5 and 0x10 from acd_mode_sense() when I'm booting up. What do those error codes mean? Do they correspond to the error register bits listed in atapi-all.h? #define ATAPI_E_ILI 0x01 /* illegal length indication */ #define ATAPI_E_ABRT 0x04 /* command aborted */ #define ATAPI_SK_RECOVERED_ERROR 0x10 /* command OK, data recovered */ I ask because in the failure case of kern/23409, I see error 0x10 many times. In the success case, error 0x5 appears twice and then goes away before reaching a maximum retry count. Much more detailed information is available in the bug report. I'm not on the mailing list so please include me on replies. If I've sent this to the wrong mailing list, please forward it appropriately. Thanks for the help! Eyal -- Eyal Soha Work: (408) 527-9276 Software Engineer Page: (800) 365-4578 Cisco Systems Epage: esoha@epage.cisco.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 3: 4:53 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 03:04:47 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from fep09-svc.tin.it (mta09-acc.tin.it [212.216.176.40]) by hub.freebsd.org (Postfix) with ESMTP id EC74937B69D; Mon, 11 Dec 2000 03:03:58 -0800 (PST) Received: from lorix ([213.45.186.90]) by fep09-svc.tin.it (InterMail vM.4.01.02.27 201-229-119-110) with SMTP id <20001211095457.XMRP13287.fep09-svc.tin.it@lorix>; Mon, 11 Dec 2000 10:54:57 +0100 Message-ID: <004001c06358$37cc9480$016464c8@lorix> From: "Loris Degioanni" To: "Stefan Esser" , "Guy Harris" Cc: "Matt Dillon" , "Dragos Ruiu" , , , , , , "Stefan Esser" References: <0012072118150Q.09615@smp.kyx.net> <200012080547.eB85lKc17216@earth.backplane.com> <20001207233958.C352@quadrajet.flashcom.com> <20001208003839.A352@quadrajet.flashcom.com> <20001209142132.A822@StefanEsser.FreeBSD.org> Subject: R: [tcpdump-workers] Re: Re: [Ethereal-dev] Re: Fwd: kyxtech: freebsd outsniffed by wintendo !!?!? Date: Mon, 11 Dec 2000 10:49:48 +0100 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 > On 2000-12-08 00:38 -0800, Guy Harris wrote: > > (Both FreeBSD and OpenBSD have the maximum buffer size for BPF as 512KB > > in the top of the CVS tree; NetBSD still has it as 32K.) > > You can change both the default and maximum BPF buffer sizes at > run time (affecting an subsequent open()) in FreeBSD: > > # sysctl -w debug.bpf_bufsize=32768 debug.bpf_maxbufsize=4194304 > > makes the default buffer size 32K and limits the size to 4MB, for > example. Notice however that in pcap-bpf.c, pcap_open_live() forces the buffer size to 32K through an IOCTL. This means that the sysctl is overridden if BPF is used throug libpcap. Loris. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 4: 9: 0 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 04:08:56 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA02C37B6A9; Mon, 11 Dec 2000 04:08:45 -0800 (PST) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C5326E2E9B; Mon, 11 Dec 2000 01:04:11 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id KAA54241; Mon, 11 Dec 2000 10:02:46 +0100 (CET) (envelope-from des@ofug.org) Sender: 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: Wes Peters Cc: "Daniel C. Sobral" , stable@FreeBSD.ORG, "Chad R. Larson" , hackers@FreeBSD.ORG Subject: Re: PCIOCGETCONF/PCIOCREAD requires write permission? References: <200012080707.AAA12102@freeway.dcfinc.com> <20001208115004.B81619@dragon.nuxi.com> <3A333CE4.5B9FDA92@newsguy.com> <3A342838.2345F03@softweyr.com> From: Dag-Erling Smorgrav Date: 11 Dec 2000 10:02:45 +0100 In-Reply-To: Wes Peters's message of "Sun, 10 Dec 2000 18:04:56 -0700" Message-ID: Lines: 8 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 Wes Peters writes: > BSD for the masses. "BSD on every desk and in every home" DES (ducks, runs) -- 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 Mon Dec 11 6:19:45 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 06:19:39 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (pool249-tch-1.Sofia.0rbitel.net [212.95.170.249]) by hub.freebsd.org (Postfix) with SMTP id CC87637B400 for ; Mon, 11 Dec 2000 06:19:36 -0800 (PST) Received: (qmail 1969 invoked by uid 1000); 11 Dec 2000 14:18:47 -0000 Date: Mon, 11 Dec 2000 16:18:47 +0200 From: Peter Pentchev To: hackers@FreeBSD.org Subject: eye-candy hack - warp_saver changing direction :) Message-ID: <20001211161847.A606@ringworld.oblivion.bg> Mail-Followup-To: hackers@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So.. if anybody else is using the warp screen saver, here's a little patch to make it reverse direction from time to time; as my boss put it, "I don't know about you, but an hour of your screen rolling over to the right makes me dizzy." :) This one defines two sysctl's - kern.warp_dir (zero to roll to the left, non-zero to roll the other way), and kern.warp_period (number of iterations before changing direction). The warp_period is measured in.. seconds, isn't it - how often the saver is called to do its dance.. Attached are patches against -current and 4.2-STABLE; hope this does not look too ugly :) G'luck, Peter -- "yields falsehood, when appended to its quotation." yields falsehood, when appended to its quotation. Patch against -current: Index: src/sys/modules/syscons/warp/warp_saver.c =================================================================== RCS file: /home/ncvs/src/sys/modules/syscons/warp/warp_saver.c,v retrieving revision 1.9 diff -u -r1.9 warp_saver.c --- src/sys/modules/syscons/warp/warp_saver.c 2000/06/25 09:39:11 1.9 +++ src/sys/modules/syscons/warp/warp_saver.c 2000/12/11 14:00:29 @@ -35,6 +35,7 @@ #include #include #include +#include #include #include @@ -58,19 +59,35 @@ /* the rest is zero-filled by the compiler */ }; +static int warp_dir = 1, warp_period = 10000; +SYSCTL_INT(_kern, OID_AUTO, warp_dir, CTLFLAG_RW, &warp_dir, 0, "") +SYSCTL_INT(_kern, OID_AUTO, warp_period, CTLFLAG_RW, &warp_period, 0, "") + static void -warp_update(void) +warp_update(int *pdir, int period) { int i, j, k, n; + static int cur_state = 0; for (i = 1, k = 0, n = SPP*8; i < 5; i++, n /= 2) for (j = 0; j < n; j++, k++) { vid[star[k]] = 0; - star[k] += i; - if (star[k] > SCRW*SCRH) - star[k] -= SCRW*SCRH; + if (*pdir) { + star[k] += i; + if (star[k] > SCRW*SCRH) + star[k] -= SCRW*SCRH; + } else { + star[k] -= i; + if (star[k] < 0) + star[k] += SCRW*SCRH; + } vid[star[k]] = i; } + + if (++cur_state >= period) { + *pdir = !*pdir; + cur_state = 0; + } } static int @@ -94,7 +111,7 @@ } /* update display */ - warp_update(); + warp_update(&warp_dir, warp_period); } else { blanked = 0; ........................... ...and against 4.2-STABLE.. Index: src/sys/modules/syscons/warp/warp_saver.c =================================================================== RCS file: /home/ncvs/src/sys/modules/syscons/warp/warp_saver.c,v retrieving revision 1.7.2.1 diff -u -r1.7.2.1 warp_saver.c --- src/sys/modules/syscons/warp/warp_saver.c 2000/05/10 16:26:47 1.7.2.1 +++ src/sys/modules/syscons/warp/warp_saver.c 2000/12/11 13:58:14 @@ -36,6 +36,7 @@ #include #include #include +#include #include #include @@ -59,19 +60,35 @@ /* the rest is zero-filled by the compiler */ }; +static int warp_dir = 1, warp_period = 10000; +SYSCTL_INT(_kern, OID_AUTO, warp_dir, CTLFLAG_RW, &warp_dir, 0, "") +SYSCTL_INT(_kern, OID_AUTO, warp_period, CTLFLAG_RW, &warp_period, 0, "") + static void -warp_update(void) +warp_update(int *pdir, int period) { int i, j, k, n; + static int cur_state = 0; for (i = 1, k = 0, n = SPP*8; i < 5; i++, n /= 2) for (j = 0; j < n; j++, k++) { vid[star[k]] = 0; - star[k] += i; - if (star[k] > SCRW*SCRH) - star[k] -= SCRW*SCRH; + if (*pdir) { + star[k] += i; + if (star[k] > SCRW*SCRH) + star[k] -= SCRW*SCRH; + } else { + star[k] -= i; + if (star[k] < 0) + star[k] += SCRW*SCRH; + } vid[star[k]] = i; } + + if (++cur_state >= period) { + *pdir = !*pdir; + cur_state = 0; + } } static int @@ -95,7 +112,7 @@ } /* update display */ - warp_update(); + warp_update(&warp_dir, warp_period); } else { blanked = 0; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 6:32: 8 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 06:32:04 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (pool249-tch-1.Sofia.0rbitel.net [212.95.170.249]) by hub.freebsd.org (Postfix) with SMTP id C2BB037B400 for ; Mon, 11 Dec 2000 06:32:01 -0800 (PST) Received: (qmail 2120 invoked by uid 1000); 11 Dec 2000 14:31:12 -0000 Date: Mon, 11 Dec 2000 16:31:12 +0200 From: Peter Pentchev To: hackers@FreeBSD.org Subject: Re: eye-candy hack - warp_saver changing direction :) Message-ID: <20001211163112.B606@ringworld.oblivion.bg> Mail-Followup-To: hackers@FreeBSD.org References: <20001211161847.A606@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: <20001211161847.A606@ringworld.oblivion.bg>; from roam@orbitel.bg on Mon, Dec 11, 2000 at 04:18:47PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, OK, I *promise* I'll think twice before posting next time :) Here's a revised patch - a kern.warp_period <= 0 signifies no direction change, for those who prefer the old behavior. G'luck, Peter -- This sentence no verb. Patch against -current: Index: src/sys/modules/syscons/warp/warp_saver.c =================================================================== RCS file: /home/ncvs/src/sys/modules/syscons/warp/warp_saver.c,v retrieving revision 1.9 diff -u -r1.9 warp_saver.c --- src/sys/modules/syscons/warp/warp_saver.c 2000/06/25 09:39:11 1.9 +++ src/sys/modules/syscons/warp/warp_saver.c 2000/12/11 14:00:29 @@ -35,6 +35,7 @@ #include #include #include +#include #include #include @@ -58,19 +59,35 @@ /* the rest is zero-filled by the compiler */ }; +static int warp_dir = 1, warp_period = 10000; +SYSCTL_INT(_kern, OID_AUTO, warp_dir, CTLFLAG_RW, &warp_dir, 0, "") +SYSCTL_INT(_kern, OID_AUTO, warp_period, CTLFLAG_RW, &warp_period, 0, "") + static void -warp_update(void) +warp_update(int *pdir, int period) { int i, j, k, n; + static int cur_state = 0; for (i = 1, k = 0, n = SPP*8; i < 5; i++, n /= 2) for (j = 0; j < n; j++, k++) { vid[star[k]] = 0; - star[k] += i; - if (star[k] > SCRW*SCRH) - star[k] -= SCRW*SCRH; + if (*pdir) { + star[k] += i; + if (star[k] > SCRW*SCRH) + star[k] -= SCRW*SCRH; + } else { + star[k] -= i; + if (star[k] < 0) + star[k] += SCRW*SCRH; + } vid[star[k]] = i; } + + if ((period > 0) && (++cur_state >= period)) { + *pdir = !*pdir; + cur_state = 0; + } } static int @@ -94,7 +111,7 @@ } /* update display */ - warp_update(); + warp_update(&warp_dir, warp_period); } else { blanked = 0; ........................... .. and against 4.2-STABLE.. Index: src/sys/modules/syscons/warp/warp_saver.c =================================================================== RCS file: /home/ncvs/src/sys/modules/syscons/warp/warp_saver.c,v retrieving revision 1.7.2.1 diff -u -r1.7.2.1 warp_saver.c --- src/sys/modules/syscons/warp/warp_saver.c 2000/05/10 16:26:47 1.7.2.1 +++ src/sys/modules/syscons/warp/warp_saver.c 2000/12/11 13:58:14 @@ -36,6 +36,7 @@ #include #include #include +#include #include #include @@ -59,19 +60,35 @@ /* the rest is zero-filled by the compiler */ }; +static int warp_dir = 1, warp_period = 10000; +SYSCTL_INT(_kern, OID_AUTO, warp_dir, CTLFLAG_RW, &warp_dir, 0, "") +SYSCTL_INT(_kern, OID_AUTO, warp_period, CTLFLAG_RW, &warp_period, 0, "") + static void -warp_update(void) +warp_update(int *pdir, int period) { int i, j, k, n; + static int cur_state = 0; for (i = 1, k = 0, n = SPP*8; i < 5; i++, n /= 2) for (j = 0; j < n; j++, k++) { vid[star[k]] = 0; - star[k] += i; - if (star[k] > SCRW*SCRH) - star[k] -= SCRW*SCRH; + if (*pdir) { + star[k] += i; + if (star[k] > SCRW*SCRH) + star[k] -= SCRW*SCRH; + } else { + star[k] -= i; + if (star[k] < 0) + star[k] += SCRW*SCRH; + } vid[star[k]] = i; } + + if ((period > 0) && (++cur_state >= period)) { + *pdir = !*pdir; + cur_state = 0; + } } static int @@ -95,7 +112,7 @@ } /* update display */ - warp_update(); + warp_update(&warp_dir, warp_period); } else { blanked = 0; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 6:42:18 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 06:42:17 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139]) by hub.freebsd.org (Postfix) with ESMTP id 2046337B400 for ; Mon, 11 Dec 2000 06:42:16 -0800 (PST) Received: from wiliam.alcove-int ([10.16.110.19]) by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian)) id 145U9Z-0003Pz-00; Mon, 11 Dec 2000 15:42:09 +0100 Received: from nsouch by wiliam.alcove-int with local (Exim 3.12 #1 (Debian)) id 145U9X-0006gn-00; Mon, 11 Dec 2000 15:42:07 +0100 Date: Mon, 11 Dec 2000 15:42:07 +0100 From: Nicolas Souchu To: Warner Losh Cc: hackers@freebsd.org Subject: Re: Partial start on pci + serial/parallel cards Message-ID: <20001211154207.A25074@wiliam.alcove-int> References: <200012090613.XAA18688@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i In-Reply-To: <200012090613.XAA18688@harmony.village.org>; from imp@village.org on Fri, Dec 08, 2000 at 11:13:12PM -0700 Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Efr?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 08, 2000 at 11:13:12PM -0700, Warner Losh wrote: > > OK. I have a partial start on the serial/parallel cards. It isn't > attaching anything yet, but should give people an idea on the > direction I'd like to head. > > As part of this work, I'll likely remove pci attachment of sio, and > change it to puc. puc is the name NetBSD uses (I snagged the tables > and some code from NetBSD's puc driver, btw) so I kept using it. I'll > also need to add puc attachments to sio and ppc drivers. What will actually happened to them, especially ppc? Currently, ppc is isa dependent so why should we change the DRIVER_MODULE directive to attach to puc? Nicholas -- Nicolas.Souchu@alcove.fr Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 8: 1:29 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 08:01:27 2000 Return-Path: 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 3DA1037B400 for ; Mon, 11 Dec 2000 08:01:26 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id RAA55989; Mon, 11 Dec 2000 17:01:22 +0100 (CET) (envelope-from des@ofug.org) Sender: 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: Peter Pentchev Cc: hackers@FreeBSD.ORG Subject: Re: eye-candy hack - warp_saver changing direction :) References: <20001211161847.A606@ringworld.oblivion.bg> From: Dag-Erling Smorgrav Date: 11 Dec 2000 17:01:22 +0100 In-Reply-To: Peter Pentchev's message of "Mon, 11 Dec 2000 16:18:47 +0200" Message-ID: Lines: 13 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 Peter Pentchev writes: > This one defines two sysctl's - kern.warp_dir (zero to roll to the left, > non-zero to roll the other way), and kern.warp_period (number of iterations > before changing direction). The warp_period is measured in.. seconds, isn't > it - how often the saver is called to do its dance.. kern.* is not the right place for this. It should go in user.*, unless that is reserved for userland, in which case a subtree of kern.* is probably the Right Thing. 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 Mon Dec 11 8: 4:44 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 08:04:42 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (pool249-tch-1.Sofia.0rbitel.net [212.95.170.249]) by hub.freebsd.org (Postfix) with SMTP id 4095F37B402 for ; Mon, 11 Dec 2000 08:04:40 -0800 (PST) Received: (qmail 2768 invoked by uid 1000); 11 Dec 2000 16:03:47 -0000 Date: Mon, 11 Dec 2000 18:03:46 +0200 From: Peter Pentchev To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG Subject: Re: eye-candy hack - warp_saver changing direction :) Message-ID: <20001211180346.C606@ringworld.oblivion.bg> Mail-Followup-To: Dag-Erling Smorgrav , hackers@FreeBSD.ORG References: <20001211161847.A606@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Mon, Dec 11, 2000 at 05:01:22PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 11, 2000 at 05:01:22PM +0100, Dag-Erling Smorgrav wrote: > Peter Pentchev writes: > > This one defines two sysctl's - kern.warp_dir (zero to roll to the left, > > non-zero to roll the other way), and kern.warp_period (number of iterations > > before changing direction). The warp_period is measured in.. seconds, isn't > > it - how often the saver is called to do its dance.. > > kern.* is not the right place for this. It should go in user.*, unless > that is reserved for userland, in which case a subtree of kern.* is > probably the Right Thing. Yes, I was wondering about user.*, but I decided it was reserved for userland. OK, I'll put it in a subtree. How does kern.ss.warp.* sound? Or kern.saver.warp.*? Or maybe even kern.syscons.saver.warp.*? (oif!) G'luck, Peter -- You have, of course, just begun reading the sentence that you have just finished reading. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 8:56:21 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 08:56:18 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (pool249-tch-1.Sofia.0rbitel.net [212.95.170.249]) by hub.freebsd.org (Postfix) with SMTP id 9CC0437B402 for ; Mon, 11 Dec 2000 08:56:16 -0800 (PST) Received: (qmail 3324 invoked by uid 1000); 11 Dec 2000 16:55:24 -0000 Date: Mon, 11 Dec 2000 18:55:24 +0200 From: Peter Pentchev To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG Subject: Re: eye-candy hack - warp_saver changing direction :) Message-ID: <20001211185524.E606@ringworld.oblivion.bg> Mail-Followup-To: Dag-Erling Smorgrav , hackers@FreeBSD.ORG References: <20001211161847.A606@ringworld.oblivion.bg> <20001211180346.C606@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: <20001211180346.C606@ringworld.oblivion.bg>; from roam@orbitel.bg on Mon, Dec 11, 2000 at 06:03:46PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 11, 2000 at 06:03:46PM +0200, Peter Pentchev wrote: > On Mon, Dec 11, 2000 at 05:01:22PM +0100, Dag-Erling Smorgrav wrote: > > Peter Pentchev writes: > > > This one defines two sysctl's - kern.warp_dir (zero to roll to the left, > > > non-zero to roll the other way), and kern.warp_period (number of iterations > > > before changing direction). The warp_period is measured in.. seconds, isn't > > > it - how often the saver is called to do its dance.. > > > > kern.* is not the right place for this. It should go in user.*, unless > > that is reserved for userland, in which case a subtree of kern.* is > > probably the Right Thing. > > Yes, I was wondering about user.*, but I decided it was reserved for > userland. OK, I'll put it in a subtree. How does kern.ss.warp.* sound? > Or kern.saver.warp.*? Or maybe even kern.syscons.saver.warp.*? (oif!) Well, I can't quite make it work with a kern.* sysctl subtree.. It's obvious that this has something to do with SYSCTL_DECL(), but - how? :) I currently have these in my warp_saver.c (just kern.saver for simplicity): SYSCTL_DECL(_kern_saver); SYSCTL_INT(_kern_saver, OID_AUTO, dir, CTLFLAG_RW, &warp_dir, 0, "") SYSCTL_INT(_kern_saver, OID_AUTO, step, CTLFLAG_RW, &warp_step, 0, "") SYSCTL_INT(_kern_saver, OID_AUTO, period, CTLFLAG_RW, &warp_period, 0, "") It builds and installs fine, and then: [root@ringworld:v0 /usr/mysrc/sys/modules/syscons/warp]# make load /sbin/kldload -v ./warp_saver.ko link_elf: symbol sysctl__kern_saver_children undefined kldload: can't load ./warp_saver.ko: Exec format error *** Error code 1 Stop in /usr/mysrcx/sys/modules/syscons/warp. [root@ringworld:v0 /usr/mysrc/sys/modules/syscons/warp]# Apparently I'm missing something.. Help? G'luck, Peter -- If wishes were fishes, the antecedent of this conditional would be true. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 8:58:39 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 08:58:36 2000 Return-Path: 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 2333C37B400 for ; Mon, 11 Dec 2000 08:58:36 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eBBGwC091426; Mon, 11 Dec 2000 08:58:12 -0800 (PST) (envelope-from dillon) Date: Mon, 11 Dec 2000 08:58:12 -0800 (PST) From: Matt Dillon Message-Id: <200012111658.eBBGwC091426@earth.backplane.com> To: Alfred Perlstein Cc: freebsd-hackers@freebsd.org Subject: Re: cvs commit: src/sys/vm vm_pageout.c References: <200012110756.eBB7uWp34663@freefall.freebsd.org> <20001211035441.Z16205@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I feel like a dolt here, but could you run these deltas by :me or alc? : :Shouldn't it be using bogus_page here? : :-- :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Let me respond to -hackers here. My commit comment isn't that good. Lets say you have a normal filesystem (1K frag, 8K block), and a small 2K file. The struct buf associated with the file will only have a b_bufsize of 2K (rather then 8K) in this case. Now lets say you mmap() the file shared + R/W. The mmap()ing will cause the VM page backing the buffer to be made all valid (m->valid = VM_PAGE_BITS_ALL). Now lets say you dirty the page via the mmap, by writing to memory. This will cause a VM fault which will make the underlying page all dirty (m->dirty = VM_PAGE_BITS_ALL). This is all correct so far. But now the filesystem comes along and flushes the underlying filesystem buffer. This will sync the page to the filesystem, which is what we want. But remember, the file is only 2K! So the end of the I/O operation only 'cleans' the first 2K of the page, leaving m->dirty = 0xFC. The page is truely completely 'clean', but it's still left marked dirty from the VM system's point of view. Now vm_object_page_clean() comes along and says 'look! A page without a filesystem buffer that's dirty. I need to flush it'. Which it does. My KASSERT was asserting that the page had to be fully dirty, and under normal circumstances it has to be. Until we fix how the filesystem deals with backing pages in the fragment case, I have to take that part of the KASSERT out. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 9: 3: 7 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 09:03:05 2000 Return-Path: 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 0D0DF37B404 for ; Mon, 11 Dec 2000 09:03:05 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id SAA56230; Mon, 11 Dec 2000 18:03:01 +0100 (CET) (envelope-from des@ofug.org) Sender: 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: Peter Pentchev Cc: hackers@FreeBSD.ORG Subject: Re: eye-candy hack - warp_saver changing direction :) References: <20001211161847.A606@ringworld.oblivion.bg> <20001211180346.C606@ringworld.oblivion.bg> <20001211185524.E606@ringworld.oblivion.bg> From: Dag-Erling Smorgrav Date: 11 Dec 2000 18:03:00 +0100 In-Reply-To: Peter Pentchev's message of "Mon, 11 Dec 2000 18:55:24 +0200" Message-ID: Lines: 13 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 Peter Pentchev writes: > SYSCTL_DECL(_kern_saver); SYSCTL_DECL is for declaring a node that's defined elsewhere. You should use the following instead: SYSCTL_NODE(_kern, OID_AUTO, saver, CTLFLAG_RW, NULL, "Screensavers"); There's no substitute for reading src/sys/sys/sysctl.h. 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 Mon Dec 11 9:46:27 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 09:46:26 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from oden.exmandato.se (oden.exmandato.se [192.71.33.1]) by hub.freebsd.org (Postfix) with ESMTP id 38C8637B404 for ; Mon, 11 Dec 2000 09:46:25 -0800 (PST) Received: from servicefactory.se (root@oden.exmandato.se [192.71.33.1]) by oden.exmandato.se (8.8.8/8.8.5) with ESMTP id SAA08780 for ; Mon, 11 Dec 2000 18:46:23 +0100 (MET) Sender: jonas@oden.exmandato.se Message-ID: <3A3504DC.9273A77A@servicefactory.se> Date: Mon, 11 Dec 2000 17:46:20 +0100 From: Jonas Bulow X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 Cc: hackers@FreeBSD.ORG Subject: Re: kqueue microbenchmark results References: <20001024225637.A54554@prism.flugsvamp.com> <39F6655A.353FD236@alumni.caltech.edu> <20001025115457.X28123@fw.wintelcom.net> <20001025170117.C87091@prism.flugsvamp.com> <20001207154925.A25785@walton.maths.tcd.ie> <3A30E115.CF7C76E8@newsguy.com> <3A31120E.3536F07D@alumni.caltech.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Kegel wrote: ... > Don't jump to conclusions. He's honestly trying to > understand what the optimal interface would be. > Let him catch up. Help him understand the requirements > which motivated the kqueue design and why his proposed > system call does not meet them. > > His role right now is to keep the kernel as simple as possible. > You need to prove that his proposed interface is simpler than possible :-) A simple way to keep the kernel simple: http://linuxtoday.com/news_story.php3?ltsn=2000-12-09-013-20-NW-GN-KN :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 10:31:25 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 10:31:16 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (pool101-tch-1.Sofia.0rbitel.net [212.95.170.101]) by hub.freebsd.org (Postfix) with SMTP id 0B8F437B400 for ; Mon, 11 Dec 2000 10:31:12 -0800 (PST) Received: (qmail 850 invoked by uid 1000); 11 Dec 2000 18:30:19 -0000 Date: Mon, 11 Dec 2000 20:30:19 +0200 From: Peter Pentchev To: Dag-Erling Smorgrav Cc: hackers@FreeBSD.ORG Subject: Re: eye-candy hack - warp_saver changing direction :) Message-ID: <20001211203018.A449@ringworld.oblivion.bg> Mail-Followup-To: Dag-Erling Smorgrav , hackers@FreeBSD.ORG References: <20001211161847.A606@ringworld.oblivion.bg> <20001211180346.C606@ringworld.oblivion.bg> <20001211185524.E606@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Mon, Dec 11, 2000 at 06:03:00PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 11, 2000 at 06:03:00PM +0100, Dag-Erling Smorgrav wrote: > Peter Pentchev writes: > > SYSCTL_DECL(_kern_saver); > > SYSCTL_DECL is for declaring a node that's defined elsewhere. You > should use the following instead: > > SYSCTL_NODE(_kern, OID_AUTO, saver, CTLFLAG_RW, NULL, "Screensavers"); > > There's no substitute for reading src/sys/sys/sysctl.h. Yes, mea culpa :( All right then, here's a revised patch that: - adds a kern.saver.* sysctl subtree in syscons.c (I *think* this belongs there, it's not each and every screensaver's job to define the global sysctl tree); - defines 8 directions instead of just 2; - adds 4 sysctl's: warp_dir - current movement direction; warp_step - increment to warp_dir on each direction change; warp_period - how long before a direction change; warp_random - boolean flag for random direction changes. If warp_period is > 0, then each warp_period steps, the direction is changed by the following rules: - if warp_random is non-zero, the new direction is random; - if warp_random is zero, warp_dir = (warp_dir + warp_step) modulo 8. The 'standard' behavior is achieved by: warp_dir=0 warp_period=0 The currently default behavior (go round and round and round) is: warp_dir=0 warp_step=1 warp_period=100 warp_random=0 Left-and-right behavior: warp_dir=0 warp_step=4 warp_period=1000 warp_random=0 Random walk: warp_period=100 warp_random=1 G'luck, Peter -- If I were you, who would be reading this sentence? Patch against -current: Index: src/sys/dev/syscons/syscons.c =================================================================== RCS file: /home/ncvs/src/sys/dev/syscons/syscons.c,v retrieving revision 1.349 diff -u -r1.349 syscons.c --- src/sys/dev/syscons/syscons.c 2000/12/08 21:49:55 1.349 +++ src/sys/dev/syscons/syscons.c 2000/12/11 18:19:04 @@ -120,6 +120,8 @@ SYSCTL_INT(_machdep, OID_AUTO, enable_panic_key, CTLFLAG_RW, &enable_panic_key, 0, ""); +SYSCTL_NODE(_kern, OID_AUTO, saver, CTLFLAG_RW, NULL, "Console screensavers") + #define SC_CONSOLECTL 255 #define VIRTUAL_TTY(sc, x) (SC_DEV((sc), (x))->si_tty) Index: src/sys/modules/syscons/warp/warp_saver.c =================================================================== RCS file: /home/ncvs/src/sys/modules/syscons/warp/warp_saver.c,v retrieving revision 1.9 diff -u -r1.9 warp_saver.c --- src/sys/modules/syscons/warp/warp_saver.c 2000/06/25 09:39:11 1.9 +++ src/sys/modules/syscons/warp/warp_saver.c 2000/12/11 18:20:04 @@ -35,6 +35,7 @@ #include #include #include +#include #include #include @@ -58,19 +59,60 @@ /* the rest is zero-filled by the compiler */ }; +static int warp_dirs[8] = { + 1, /* E */ + SCRW+1, /* SE */ + SCRW, /* S */ + SCRW-1, /* SW */ + -1, /* W */ + -SCRW-1, /* NW */ + -SCRW, /* N */ + -SCRW+1 /* NE */ +}; +#define WARP_DIRCNT (sizeof(warp_dirs)/sizeof(warp_dirs[0])) + +static int warp_dir = 0, warp_step = 1, warp_period = 100; +static int warp_random = 0; + +/* Make use of syscons's screen saver subtree.. */ +SYSCTL_DECL(_kern_saver); +/* Add our sysctls there */ +SYSCTL_INT(_kern_saver, OID_AUTO, warp_dir, CTLFLAG_RW, &warp_dir, 0, "") +SYSCTL_INT(_kern_saver, OID_AUTO, warp_step, CTLFLAG_RW, &warp_step, 0, "") +SYSCTL_INT(_kern_saver, OID_AUTO, warp_period, CTLFLAG_RW, &warp_period, 0, "") +SYSCTL_INT(_kern_saver, OID_AUTO, warp_random, CTLFLAG_RW, &warp_random, 0, "") + static void -warp_update(void) +warp_update(int *pdir, int step, int period) { int i, j, k, n; + static int cur_state = 0; for (i = 1, k = 0, n = SPP*8; i < 5; i++, n /= 2) for (j = 0; j < n; j++, k++) { vid[star[k]] = 0; - star[k] += i; - if (star[k] > SCRW*SCRH) + + /* calculate the new position */ + star[k] += warp_dirs[*pdir]*i; + /* do not fall off the screen */ + if (star[k] >= SCRW*SCRH) star[k] -= SCRW*SCRH; + else if (star[k] < 0) + star[k] += SCRW*SCRH; + vid[star[k]] = i; } + + if ((period > 0) && (++cur_state >= period)) { + cur_state = 0; + + /* hope gcc is smart enough to optimize the %-by-power-of-two.. */ + /* (not that the random() call is less of a bottleneck :) */ + if (warp_random) + *pdir = random() % WARP_DIRCNT; + else + *pdir = (*pdir + step) % WARP_DIRCNT; + } } static int @@ -94,7 +136,7 @@ } /* update display */ - warp_update(); + warp_update(&warp_dir, warp_step, warp_period); } else { blanked = 0; .......................... ..and against 4.2-STABLE.. Index: src/sys/dev/syscons/syscons.c =================================================================== RCS file: /home/ncvs/src/sys/dev/syscons/syscons.c,v retrieving revision 1.336.2.3 diff -u -r1.336.2.3 syscons.c --- src/sys/dev/syscons/syscons.c 2000/10/29 16:59:27 1.336.2.3 +++ src/sys/dev/syscons/syscons.c 2000/12/11 17:41:30 @@ -118,6 +118,8 @@ SYSCTL_INT(_machdep, OID_AUTO, enable_panic_key, CTLFLAG_RW, &enable_panic_key, 0, ""); +SYSCTL_NODE(_kern, OID_AUTO, saver, CTLFLAG_RW, NULL, "Console screensavers") + #define SC_CONSOLECTL 255 #define VIRTUAL_TTY(sc, x) (SC_DEV((sc), (x))->si_tty) Index: src/sys/modules/syscons/warp/warp_saver.c =================================================================== RCS file: /home/ncvs/src/sys/modules/syscons/warp/warp_saver.c,v retrieving revision 1.7.2.1 diff -u -r1.7.2.1 warp_saver.c --- src/sys/modules/syscons/warp/warp_saver.c 2000/05/10 16:26:47 1.7.2.1 +++ src/sys/modules/syscons/warp/warp_saver.c 2000/12/11 17:42:06 @@ -36,6 +36,7 @@ #include #include #include +#include #include #include @@ -59,19 +60,60 @@ /* the rest is zero-filled by the compiler */ }; +static int warp_dirs[8] = { + 1, /* E */ + SCRW+1, /* SE */ + SCRW, /* S */ + SCRW-1, /* SW */ + -1, /* W */ + -SCRW-1, /* NW */ + -SCRW, /* N */ + -SCRW+1 /* NE */ +}; +#define WARP_DIRCNT (sizeof(warp_dirs)/sizeof(warp_dirs[0])) + +static int warp_dir = 0, warp_step = 1, warp_period = 100; +static int warp_random = 0; + +/* Make use of syscons's screen saver subtree.. */ +SYSCTL_DECL(_kern_saver); +/* Add our sysctls there */ +SYSCTL_INT(_kern_saver, OID_AUTO, warp_dir, CTLFLAG_RW, &warp_dir, 0, "") +SYSCTL_INT(_kern_saver, OID_AUTO, warp_step, CTLFLAG_RW, &warp_step, 0, "") +SYSCTL_INT(_kern_saver, OID_AUTO, warp_period, CTLFLAG_RW, &warp_period, 0, "") +SYSCTL_INT(_kern_saver, OID_AUTO, warp_random, CTLFLAG_RW, &warp_random, 0, "") + static void -warp_update(void) +warp_update(int *pdir, int step, int period) { int i, j, k, n; + static int cur_state = 0; for (i = 1, k = 0, n = SPP*8; i < 5; i++, n /= 2) for (j = 0; j < n; j++, k++) { vid[star[k]] = 0; - star[k] += i; - if (star[k] > SCRW*SCRH) + + /* calculate the new position */ + star[k] += warp_dirs[*pdir]*i; + /* do not fall off the screen */ + if (star[k] >= SCRW*SCRH) star[k] -= SCRW*SCRH; + else if (star[k] < 0) + star[k] += SCRW*SCRH; + vid[star[k]] = i; } + + if ((period > 0) && (++cur_state >= period)) { + cur_state = 0; + + /* hope gcc is smart enough to optimize the %-by-power-of-two.. */ + /* (not that the random() call is less of a bottleneck :) */ + if (warp_random) + *pdir = random() % WARP_DIRCNT; + else + *pdir = (*pdir + step) % WARP_DIRCNT; + } } static int @@ -95,7 +137,7 @@ } /* update display */ - warp_update(); + warp_update(&warp_dir, warp_step, warp_period); } else { blanked = 0; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 10:35:51 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 10:35:48 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from athena.lightningone.net (athena.lightningone.net [12.34.104.3]) by hub.freebsd.org (Postfix) with ESMTP id 4845537B400 for ; Mon, 11 Dec 2000 10:35:48 -0800 (PST) Received: from athena.lightningone.net (athena.lightningone.net [12.34.104.3]) by athena.lightningone.net (8.9.3/8.9.3) with ESMTP id NAA08775 for ; Mon, 11 Dec 2000 13:40:41 -0500 (EST) (envelope-from john@macusi.com) Date: Mon, 11 Dec 2000 13:40:41 -0500 (EST) From: Essenz Consulting X-Sender: john@athena.lightningone.net To: hackers@freebsd.org Subject: Re: eye-candy hack - warp_saver changing direction :) In-Reply-To: <20001211203018.A449@ringworld.oblivion.bg> 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 unsubscribe john@athena.lightningone.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 10:36:29 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 10:36:28 2000 Return-Path: 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 DF7BC37B400 for ; Mon, 11 Dec 2000 10:36:24 -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 eBBIaMs69832; Mon, 11 Dec 2000 11:36:23 -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 LAA38242; Mon, 11 Dec 2000 11:36:22 -0700 (MST) Message-Id: <200012111836.LAA38242@harmony.village.org> To: Nicolas Souchu Subject: Re: Partial start on pci + serial/parallel cards Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 11 Dec 2000 15:42:07 +0100." <20001211154207.A25074@wiliam.alcove-int> References: <20001211154207.A25074@wiliam.alcove-int> <200012090613.XAA18688@harmony.village.org> Date: Mon, 11 Dec 2000 11:36:22 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001211154207.A25074@wiliam.alcove-int> Nicolas Souchu writes: : On Fri, Dec 08, 2000 at 11:13:12PM -0700, Warner Losh wrote: : > : > OK. I have a partial start on the serial/parallel cards. It isn't : > attaching anything yet, but should give people an idea on the : > direction I'd like to head. : > : > As part of this work, I'll likely remove pci attachment of sio, and : > change it to puc. puc is the name NetBSD uses (I snagged the tables : > and some code from NetBSD's puc driver, btw) so I kept using it. I'll : > also need to add puc attachments to sio and ppc drivers. : : What will actually happened to them, especially ppc? Currently, ppc is : isa dependent so why should we change the DRIVER_MODULE directive to : attach to puc? I'd make ppc less isa specific, but it isn't that hard to do from looking at the code. I'd also think about moving it to dev/ppc with a ppc_isa.c and ppc_puc.c. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 10:40:27 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 10:40:25 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from em.cig.mot.com (ietf.207.137.74.26.tx.verio.net [207.137.74.26]) by hub.freebsd.org (Postfix) with ESMTP id 015BE37B402 for ; Mon, 11 Dec 2000 10:40:25 -0800 (PST) Sender: taz@FreeBSD.ORG Message-ID: <3A347725.AD33DDC5@em.cig.mot.com> Date: Mon, 11 Dec 2000 06:41:41 +0000 From: Jonathan "\"Taz\"" Mischo Organization: Motorola, Inc. X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Subject: SCTP implementation and pccard.conf change for Cisco 802.11B 340 series cards Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am currently at IETF 49, where I have moved from my old wi card to the new Cisco 342, which is an an card, since Cisco acquired them. The 342 does 128-bit or less encryption at 11 meg, thus it was a worthy investment. However, pccard.conf does not have an entry for the card, since it was JUST released. The appropriate entry is: #Cisco 340 series 802.11B wireless NICs card "Cisco Systems" "340 Series Wireless LAN Adapter" config 0x5 "an" ? insert /etc/pccard_ether $device remove /sbin/ifconfig $device delete This allows the Cisco 34x cards to work, including the 342. One caveat, however...I haven't looked at the source, yet, but it is pretty safe to assume that 128-bit at 11meg support is not in the driver. I will take a look at this when I have some spare time, but since I am currently tied up with writing SCTP reference code for a linux kernel (this was not my choice...it is my job), I may not have a ton of time for a bit of time. If anyone can work on this, it'd be appreciated. On a second note, I am willing to lead the SCTP implementation team for FBSD, if there is not already one in place. We will be releasing the first developer's release of the SCTP reference code (it will not be complete, but it currently works, and still will) on January 19th, 2001. At that point, we should be able to get the implementation under way. Have a good day, -Taz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 10:54: 1 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 10:53:59 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 1F46337B400 for ; Mon, 11 Dec 2000 10:53:58 -0800 (PST) Received: from localhost (arr@localhost) by fledge.watson.org (8.11.1/8.11.1) with SMTP id eBBIrql45282; Mon, 11 Dec 2000 13:53:52 -0500 (EST) (envelope-from arr@watson.org) Date: Mon, 11 Dec 2000 13:53:52 -0500 (EST) From: "Andrew R. Reiter" To: "Jonathan \"Taz\" Mischo" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SCTP implementation and pccard.conf change for Cisco 802.11B 340 series cards In-Reply-To: <3A347725.AD33DDC5@em.cig.mot.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 Any others at IETF? I am not far from where it's being held and getting a mini-freebswd group together for food would rule ;) Email me off list if you're there! On Mon, 11 Dec 2000, Jonathan "Taz" Mischo wrote: > I am currently at IETF 49, where I have moved from my old wi card to the > > new Cisco 342, which is an an card, since Cisco acquired them. The 342 > does 128-bit or less encryption at 11 meg, thus it was a worthy > investment. However, pccard.conf does not have an entry for the card, > since it was JUST released. The appropriate entry is: > > #Cisco 340 series 802.11B wireless NICs > card "Cisco Systems" "340 Series Wireless LAN Adapter" > config 0x5 "an" ? > insert /etc/pccard_ether $device > remove /sbin/ifconfig $device delete > > This allows the Cisco 34x cards to work, including the 342. One > caveat, however...I haven't looked at the source, yet, but it is pretty > safe to assume that 128-bit at 11meg support is not in the driver. I > will take a look at this when I have some spare time, but since I am > currently tied up with writing SCTP reference code for a linux kernel > (this was not my choice...it is my job), I may not have a ton of time > for a bit of time. If anyone can work on this, it'd be appreciated. > > On a second note, I am willing to lead the SCTP implementation team for > FBSD, if there is not already one in place. We will be releasing the > first developer's release of the SCTP reference code (it will not be > complete, but it currently works, and still will) on January 19th, > 2001. At that point, we should be able to get the implementation under > way. > > Have a good day, > -Taz > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > *-------------................................................. | Andrew R. Reiter | arr@fledge.watson.org | "It requires a very unusual mind | to undertake the analysis of the obvious" -- A.N. Whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 11:10:46 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 11:10:43 2000 Return-Path: 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 45C4C37B400 for ; Mon, 11 Dec 2000 11:10:36 -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 eBBJASs69987; Mon, 11 Dec 2000 12:10:32 -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 MAA38597; Mon, 11 Dec 2000 12:10:28 -0700 (MST) Message-Id: <200012111910.MAA38597@harmony.village.org> To: taz@em.cig.mot.com Subject: Re: SCTP implementation and pccard.conf change for Cisco 802.11B 340 series cards Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 11 Dec 2000 06:41:41 GMT." <3A347725.AD33DDC5@em.cig.mot.com> References: <3A347725.AD33DDC5@em.cig.mot.com> Date: Mon, 11 Dec 2000 12:10:28 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A347725.AD33DDC5@em.cig.mot.com> Jonathan "\"Taz\"" Mischo writes: : #Cisco 340 series 802.11B wireless NICs : card "Cisco Systems" "340 Series Wireless LAN Adapter" : config 0x5 "an" ? : insert /etc/pccard_ether $device : remove /sbin/ifconfig $device delete This already appears to be in -current. Thanks for the entry none the less. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 12:25:19 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 12:25:15 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id 653E837B69D for ; Mon, 11 Dec 2000 12:25:15 -0800 (PST) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA65134; Mon, 11 Dec 2000 12:23:25 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id MAA18606; Mon, 11 Dec 2000 12:23:10 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200012112023.MAA18606@whistle.com> Subject: Re: SCTP implementation and pccard.conf change for Cisco 802.11B 340 series cards In-Reply-To: <3A347725.AD33DDC5@em.cig.mot.com> from "Jonathan \"Taz\" Mischo" at "Dec 11, 2000 06:41:41 am" To: "Jonathan \\\"Taz\\\" Mischo" Date: Mon, 11 Dec 2000 12:23:10 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan \"Taz\" Mischo writes: | I am currently at IETF 49, where I have moved from my old wi card to the | | new Cisco 342, which is an an card, since Cisco acquired them. The 342 | does 128-bit or less encryption at 11 meg, thus it was a worthy | investment. However, pccard.conf does not have an entry for the card, | since it was JUST released. The appropriate entry is: | | #Cisco 340 series 802.11B wireless NICs | card "Cisco Systems" "340 Series Wireless LAN Adapter" | config 0x5 "an" ? | insert /etc/pccard_ether $device | remove /sbin/ifconfig $device delete It's in -stable and maybe 4.2 | This allows the Cisco 34x cards to work, including the 342. One | caveat, however...I haven't looked at the source, yet, but it is pretty | safe to assume that 128-bit at 11meg support is not in the driver. I Well you are sort-of right ... look at -current and it's there. Patches for stable are at http://www.ambrisko.com/doug/an.patch.wep3 for the latest greatest stuff. Several people have this code in use for a while. I've been collecting patches and posting diff's at my website and sending announces to mobile. With the latest diff's I haven't heard of any new wishes or problems. Archie just commited the patches to -current and should MFC fairly soon. BTW I just remembered a bug in that you can't do the ancontrol stuff unless you ifconfig the interface. I need to look at this. I forgot about it a long time ago when I just worked around it so it doesn't bite me .. except when I just setup a machine. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 13: 1:42 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 13:01:40 2000 Return-Path: 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 8914837B404 for ; Mon, 11 Dec 2000 13:01:39 -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 145a8D-0000DN-00; Mon, 11 Dec 2000 14:05:10 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A354185.22BCF762@softweyr.com> Date: Mon, 11 Dec 2000 14:05:09 -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: Jonas Bulow Cc: hackers@FreeBSD.ORG Subject: Re: kqueue microbenchmark results References: <20001024225637.A54554@prism.flugsvamp.com> <39F6655A.353FD236@alumni.caltech.edu> <20001025115457.X28123@fw.wintelcom.net> <20001025170117.C87091@prism.flugsvamp.com> <20001207154925.A25785@walton.maths.tcd.ie> <3A30E115.CF7C76E8@newsguy.com> <3A31120E.3536F07D@alumni.caltech.edu> <3A3504DC.9273A77A@servicefactory.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonas Bulow wrote: > > Dan Kegel wrote: > ... > > Don't jump to conclusions. He's honestly trying to > > understand what the optimal interface would be. > > Let him catch up. Help him understand the requirements > > which motivated the kqueue design and why his proposed > > system call does not meet them. > > > > His role right now is to keep the kernel as simple as possible. > > You need to prove that his proposed interface is simpler than possible :-) > > A simple way to keep the kernel simple: > http://linuxtoday.com/news_story.php3?ltsn=2000-12-09-013-20-NW-GN-KN Device drivers in Perl. What a spectacularly bad idea. ;^) -- "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 Dec 11 14:24:32 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 14:24:27 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from sender.ngi.de (sender.ngi.de [212.79.47.18]) by hub.freebsd.org (Postfix) with ESMTP id 8974D37B404; Mon, 11 Dec 2000 14:24:26 -0800 (PST) Received: from Gatekeeper.FreeBSD.org (koln-3e366425.pool.mediaWays.net [62.54.100.37]) by sender.ngi.de (Postfix) with ESMTP id 49CA896E53; Mon, 11 Dec 2000 23:16:34 +0100 (CET) Received: from StefanEsser.FreeBSD.org (StefanEsser [10.0.0.1]) by Gatekeeper.FreeBSD.org (Postfix) with ESMTP id 6B38320; Mon, 11 Dec 2000 22:43:48 +0100 (CET) Received: by StefanEsser.FreeBSD.org (Postfix, from userid 200) id 41F93145C; Mon, 11 Dec 2000 22:44:28 +0100 (CET) Date: Mon, 11 Dec 2000 22:44:28 +0100 From: Stefan Esser To: Loris Degioanni Cc: Guy Harris , Matt Dillon , Dragos Ruiu , tcpdump-workers@tcpdump.org, ethereal-dev@ethereal.com, snort-devel@lists.sourceforge.net, freebsd-hackers@FreeBSD.org, tech@openbsd.org, Stefan Esser Subject: Re: R: [tcpdump-workers] Re: Re: [Ethereal-dev] Re: Fwd: kyxtech: freebsd outsniffed by wintendo !!?!? Message-ID: <20001211224428.A73017@StefanEsser.FreeBSD.org> Reply-To: Stefan Esser References: <0012072118150Q.09615@smp.kyx.net> <200012080547.eB85lKc17216@earth.backplane.com> <20001207233958.C352@quadrajet.flashcom.com> <20001208003839.A352@quadrajet.flashcom.com> <20001209142132.A822@StefanEsser.FreeBSD.org> <004001c06358$37cc9480$016464c8@lorix> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <004001c06358$37cc9480$016464c8@lorix>; from loris@netgroup-serv.polito.it on Mon, Dec 11, 2000 at 10:49:48AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-12-11 10:49 +0100, Loris Degioanni wrote: > > # sysctl -w debug.bpf_bufsize=32768 debug.bpf_maxbufsize=4194304 > > > > makes the default buffer size 32K and limits the size to 4MB, for > > example. > > Notice however that in pcap-bpf.c, pcap_open_live() forces the buffer > size to 32K through an IOCTL. This means that the sysctl is overridden > if BPF is used throug libpcap. Yes, you are of course correct mentioning that ! The override used to up the buffer size from the kernel default of 4KB to 32KB, but now that the default has become 32KB, we probably should use the default as is and leave the user the option of choosing a different default by means of sysctl ... Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 14:39:23 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 14:39:20 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtppop1pub.verizon.net (smtppop1pub.gte.net [206.46.170.20]) by hub.freebsd.org (Postfix) with ESMTP id BC79B37B402 for ; Mon, 11 Dec 2000 14:39:19 -0800 (PST) Received: from gte.net ([63.171.197.130]) by smtppop1pub.verizon.net with ESMTP ; id QAA36915082 Mon, 11 Dec 2000 16:33:35 -0600 (CST) Message-ID: <3A3555A3.8B7E5F43@gte.net> Date: Mon, 11 Dec 2000 14:30:59 -0800 From: Soumen Biswas Reply-To: soumen.biswas@gte.net Organization: Netscaler Inc. X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: Zhiui Zhang Cc: freebsd-hackers@freebsd.org Subject: Re: ptrace(PT_GETDBREGS) message in remote debugging References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Even I get the same error .... Zhiui Zhang wrote: > I tried remote debugging on FreeBSD 4.2 this morning. Everything was > fine, except that I saw the following messages: > > (gdb) step > ptrace(PT_GETDBREGS) failed: No such process > ptrace(PT_GETDBREGS) failed: No such process > ptrace(PT_GETDBREGS) failed: No such process > 201 cred = p ? p->p_ucred : NOCRED; > > This ptrace stuff never appear before. Is this a new feature or was I > doing something wrong? > > Any help is appreciated. > > -Zhihui > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 15:32:12 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 15:32:10 2000 Return-Path: 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 2E20537B402 for ; Mon, 11 Dec 2000 15:32:10 -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 eBBNW1q59639; Mon, 11 Dec 2000 15:32:01 -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 eBBNVus27814; Mon, 11 Dec 2000 15:31:57 -0800 (PST) (envelope-from nsayer@sftw.com) Sender: nsayer@sftw.com Message-ID: <3A3563EC.7B54BCA8@sftw.com> Date: Mon, 11 Dec 2000 15:31:56 -0800 From: Nick Sayer Reply-To: Nick X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Nick's semi-periodic hardware support prize -- take 2 References: <3A25E6E1.24C006B9@quack.kfu.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am proud to announce the winners of the US$100 prize. As you may have noticed, I committed a driver today that allows one to make a /dev/jogdial and read jogdial/button events from it. While the driver is embryonic in many ways, it is sufficiently functional for the awarding of the prize. I have decided to award the prize to Andrew Tridge and Ian Dowse. The former for his page at http://samba.org/picturebook/ which has some sample code (for Linux) that illustrates how to talk to the device, and the latter for a piece of demonstration code that works entirely in userland that he e-mailed me. The latter, along with acpidump output, was largely used to craft the driver. Each of the winners is receiving a copy of this message and is invited to direct me as to where to send their US$50. If I don't hear from them, then donations in their name will be made to the FreeBSD foundation (eventually) along with the US$100 won by Cameron Grant in the first challenge. I think the prize money for the next one of these will go up a bit, as having to split US$100 is a little cheap, I think. Nick wrote: > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 16:52:26 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 16:52:22 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (mail.dobox.com [208.187.122.44]) by hub.freebsd.org (Postfix) with ESMTP id A4DD337B402; Mon, 11 Dec 2000 16:52:22 -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 145a2w-0000D7-00; Mon, 11 Dec 2000 13:59:42 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A35403E.F8808F73@softweyr.com> Date: Mon, 11 Dec 2000 13:59:42 -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: Dag-Erling Smorgrav Cc: "Daniel C. Sobral" , stable@FreeBSD.ORG, "Chad R. Larson" , hackers@FreeBSD.ORG Subject: Re: PCIOCGETCONF/PCIOCREAD requires write permission? References: <200012080707.AAA12102@freeway.dcfinc.com> <20001208115004.B81619@dragon.nuxi.com> <3A333CE4.5B9FDA92@newsguy.com> <3A342838.2345F03@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > Wes Peters writes: > > BSD for the masses. > > "BSD on every desk and in every home" > > DES (ducks, runs) You can run, but wherever you go, there'll be a BSD system waiting for you. At least that's MY goal. ;^) -- "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 Dec 11 19:16:17 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 19:16:15 2000 Return-Path: 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 2E00537B400 for ; Mon, 11 Dec 2000 19:16:15 -0800 (PST) Received: from localhost (carock@localhost) by kira.epconline.net (8.11.1/8.11.1) with ESMTP id eBC3GE636200 for ; Mon, 11 Dec 2000 21:16:14 -0600 (CST) (envelope-from carock@kira.epconline.net) Date: Mon, 11 Dec 2000 21:16:14 -0600 (CST) From: Chuck Rock To: hackers@freebsd.org Subject: Top not showing CPU utilization? 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 running FreeBSd 4.2 on machine with 2 Pentium II CPU's When I run "top", it shows my processes with 0.00% CPU Is there a problem with top, or my machine?? last pid: 34959; load averages: 0.10, 0.06, 0.05 up 8+05:27:27 21:05:14 41 processes: 1 running, 40 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle Mem: 30M Active, 350M Inact, 41M Wired, 16M Cache, 61M Buf, 64M Free Swap: 1000M Total, 1000M Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 90620 root 2 0 15640K 14836K poll 1 24:30 0.00% 0.00% named 138 root 2 0 1040K 764K select 0 2:16 0.00% 0.00% inetd 40816 root 2 -10 2516K 1796K select 0 2:16 0.00% 0.00% sendmail 115 root 2 0 924K 616K select 1 1:45 0.00% 0.00% syslogd 1787 root 2 0 1128K 760K select 0 0:36 0.00% 0.00% radiusd 44789 root 2 0 2064K 1600K select 0 0:30 0.00% 0.00% httpd 85714 root 2 0 5176K 4068K select 0 0:18 0.00% 0.00% perl 2711 root 2 0 2256K 1240K select 0 0:15 0.00% 0.00% telnetd 1786 root 2 0 1068K 676K select 0 0:12 0.00% 0.00% radiusd 150 root 2 0 2404K 1380K select 1 0:11 0.00% 0.00% sshd 140 root 10 0 960K 704K nanslp 1 0:06 0.00% 0.00% cron 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 Dec 11 21: 8: 1 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 21:07:59 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from www.stocke.com (unknown [202.101.165.60]) by hub.freebsd.org (Postfix) with ESMTP id 427C337B400 for ; Mon, 11 Dec 2000 21:07:52 -0800 (PST) Received: from xyf ([61.164.183.129]) by www.stocke.com (8.9.3/8.9.3) with SMTP id NAA20621 for ; Tue, 12 Dec 2000 13:06:42 +0800 Message-ID: <002e01c063f9$3782cf20$5ac809c0@xyf> From: "xuyifeng" To: Subject: aio stable Date: Tue, 12 Dec 2000 13:05:40 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0029_01C0643C.3A8CDF60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0029_01C0643C.3A8CDF60 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGksDQoNCiAgd2UgaGF2ZSBzb21lIHByb2dyYW1zIHVzaW5nIGFpb18qIGJlaW5nIHBvcnRlZCB0 byBGcmVlQlNELCANCkkgaGVhcmQgdGhhdCBhaW8gaW4gRnJlZUJTRCBpcyBub3QgdmVyeSBzdGFi bGUsIGJ1dCB3aGF0IGlzIA0KaXRzIHByb2JsZW0/IGNhbiBhbnlvbmUgdGVsbCBtZSwgYW5kIHdl IG1heSBhdm9pZCBpdC4NCg0KUmVnYXJkcywNClh1WWlmZW5nDQoNCg== ------=_NextPart_000_0029_01C0643C.3A8CDF60 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w MC4yNjE0LjM1MDAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8 Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5IaSw8L0ZPTlQ+PC9ESVY+ DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+Jm5ic3A7Jm5ic3A7d2UgaGF2 ZSBzb21lIHByb2dyYW1zIHVzaW5nIGFpb18qJm5ic3A7YmVpbmcgDQpwb3J0ZWQgdG8gRnJlZUJT RCwgPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+SSBoZWFyZCB0aGF0IGFpbyBpbiBG cmVlQlNEIGlzIG5vdCB2ZXJ5IHN0YWJsZSwgPC9GT05UPjxGT05UIA0Kc2l6ZT0yPmJ1dCB3aGF0 IGlzIDwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPml0cyBwcm9ibGVtPyBjYW4gYW55 b25lIHRlbGwgbWUsIGFuZCB3ZSBtYXkgYXZvaWQgDQppdC48L0ZPTlQ+PC9ESVY+DQo8RElWPiZu YnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+UmVnYXJkcyw8L0ZPTlQ+PC9ESVY+DQo8RElW PjxGT05UIHNpemU9Mj5YdVlpZmVuZzwvRk9OVD48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+PC9C T0RZPjwvSFRNTD4NCg== ------=_NextPart_000_0029_01C0643C.3A8CDF60-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 21:32: 1 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 21:31:58 2000 Return-Path: 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 7BA8A37B404 for ; Mon, 11 Dec 2000 21:31:58 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eBC5VwY27616; Mon, 11 Dec 2000 21:31:58 -0800 (PST) Date: Mon, 11 Dec 2000 21:31:58 -0800 From: Alfred Perlstein To: xuyifeng Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: aio stable Message-ID: <20001211213158.U16205@fw.wintelcom.net> References: <002e01c063f9$3782cf20$5ac809c0@xyf> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <002e01c063f9$3782cf20$5ac809c0@xyf>; from xyf@stocke.com on Tue, Dec 12, 2000 at 01:05:40PM +0800 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * xuyifeng [001211 21:08] wrote: > Hi, > > we have some programs using aio_* being ported to FreeBSD, > I heard that aio in FreeBSD is not very stable, but what is > its problem? can anyone tell me, and we may avoid it. It should be stable now, Alan Cox has done a lot of work on 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 Mon Dec 11 22:30:55 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 22:30:52 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from www.stocke.com (unknown [202.101.165.60]) by hub.freebsd.org (Postfix) with ESMTP id 7433A37B6C1 for ; Mon, 11 Dec 2000 22:30:50 -0800 (PST) Received: from xyf ([61.164.151.131]) by www.stocke.com (8.9.3/8.9.3) with SMTP id OAA03657; Tue, 12 Dec 2000 14:29:30 +0800 Message-ID: <001001c06404$cf1ffa00$5ac809c0@xyf> From: "xuyifeng" To: "Alfred Perlstein" Cc: References: <002e01c063f9$3782cf20$5ac809c0@xyf> <20001211213158.U16205@fw.wintelcom.net> Subject: Re: aio stable Date: Tue, 12 Dec 2000 14:28:28 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG SSdtIHVzaW5nIDQuMiBzdGFibGUsIGJ1dCB3aHkgZG9lcyBMSU5UIHNheSB0aGF0IHRoZXJlIGFy ZSBzb21lIHN0YWJsZSBpc3N1ZT8gaXMgaXQgZG9jdW1lbnQgYnVnPw0KDQpYdVlpZmVuZw0KDQot LS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogQWxmcmVkIFBlcmxzdGVpbiA8YnJp Z2h0QHdpbnRlbGNvbS5uZXQ+DQpUbzogeHV5aWZlbmcgPHh5ZkBzdG9ja2UuY29tPg0KQ2M6IDxm cmVlYnNkLWhhY2tlcnNARnJlZUJTRC5PUkc+DQpTZW50OiBUdWVzZGF5LCBEZWNlbWJlciAxMiwg MjAwMCAxOjMxIFBNDQpTdWJqZWN0OiBSZTogYWlvIHN0YWJsZQ0KDQoNCj4gKiB4dXlpZmVuZyA8 eHlmQHN0b2NrZS5jb20+IFswMDEyMTEgMjE6MDhdIHdyb3RlOg0KPiA+IEhpLA0KPiA+IA0KPiA+ ICAgd2UgaGF2ZSBzb21lIHByb2dyYW1zIHVzaW5nIGFpb18qIGJlaW5nIHBvcnRlZCB0byBGcmVl QlNELCANCj4gPiBJIGhlYXJkIHRoYXQgYWlvIGluIEZyZWVCU0QgaXMgbm90IHZlcnkgc3RhYmxl LCBidXQgd2hhdCBpcyANCj4gPiBpdHMgcHJvYmxlbT8gY2FuIGFueW9uZSB0ZWxsIG1lLCBhbmQg d2UgbWF5IGF2b2lkIGl0Lg0KPiANCj4gSXQgc2hvdWxkIGJlIHN0YWJsZSBub3csIEFsYW4gQ294 IGhhcyBkb25lIGEgbG90IG9mIHdvcmsgb24gaXQuDQo+IA0KPiAtLSANCj4gLUFsZnJlZCBQZXJs c3RlaW4gLSBbYnJpZ2h0QHdpbnRlbGNvbS5uZXR8YWxmcmVkQGZyZWVic2Qub3JnXQ0KPiAiSSBo YXZlIHRoZSBoZWFydCBvZiBhIGNoaWxkOyBJIGtlZXAgaXQgaW4gYSBqYXIgb24gbXkgZGVzay4i DQo+IA0KPiANCj4gVG8gVW5zdWJzY3JpYmU6IHNlbmQgbWFpbCB0byBtYWpvcmRvbW9ARnJlZUJT RC5vcmcNCj4gd2l0aCAidW5zdWJzY3JpYmUgZnJlZWJzZC1oYWNrZXJzIiBpbiB0aGUgYm9keSBv ZiB0aGUgbWVzc2FnZQ0KDQo= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 11 22:44:36 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 11 22:44:34 2000 Return-Path: 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 397C837B400 for ; Mon, 11 Dec 2000 22:44:34 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eBC6iYm29332; Mon, 11 Dec 2000 22:44:34 -0800 (PST) Date: Mon, 11 Dec 2000 22:44:33 -0800 From: Alfred Perlstein To: xuyifeng Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: aio stable Message-ID: <20001211224433.X16205@fw.wintelcom.net> References: <002e01c063f9$3782cf20$5ac809c0@xyf> <20001211213158.U16205@fw.wintelcom.net> <001001c06404$cf1ffa00$5ac809c0@xyf> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.2.5i In-Reply-To: <001001c06404$cf1ffa00$5ac809c0@xyf>; from xyf@stocke.com on Tue, Dec 12, 2000 at 02:28:28PM +0800 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * xuyifeng [001211 22:31] wrote: > I'm using 4.2 stable, but why does LINT say that there are some stable is= sue? is it document bug? as far as i know, yes. >=20 > XuYifeng >=20 > ----- Original Message -----=20 > From: Alfred Perlstein > To: xuyifeng > Cc: > Sent: Tuesday, December 12, 2000 1:31 PM > Subject: Re: aio stable >=20 >=20 > > * xuyifeng [001211 21:08] wrote: > > > Hi, > > >=20 > > > we have some programs using aio_* being ported to FreeBSD,=20 > > > I heard that aio in FreeBSD is not very stable, but what is=20 > > > its problem? can anyone tell me, and we may avoid it. > >=20 > > It should be stable now, Alan Cox has done a lot of work on it. > >=20 > > --=20 > > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > > "I have the heart of a child; I keep it in a jar on my desk." > >=20 > >=20 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message >=20 > N=85'=B2=E6=ECr=B8=9B{=FB=1E=9D=D9=9A=8A[h=99=A8=E8=AD=DA&=A3=F1ky=E0R=0F= =FA+=83=08=AD=87=FB=A7=B2=E6=ECr=B8=9By=FA=DEy=BB=1D=FE=16=9C=91=EA=EC=FE)= =ED=85=E6=E8w*=1F=B6=17=A6z=CB=1A --=20 -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 Dec 12 1: 0: 7 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 01:00:06 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id B891237B400 for ; Tue, 12 Dec 2000 01:00:05 -0800 (PST) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id BAA00486 for ; Tue, 12 Dec 2000 01:55:54 -0700 (MST) Received: from 206-132-49-154.nas-1.SCF.primenet.com(206.132.49.154), claiming to be "max" via SMTP by smtp04.primenet.com, id smtpdAAAlIai3a; Tue Dec 12 01:55:50 2000 Reply-To: From: "Steve Shoecraft" To: Subject: Accessing the Video Bios on a PCI card?? Date: Tue, 12 Dec 2000 02:01:51 -0700 Message-ID: <000401c0641a$2b382140$9a3184ce@max.home.org> 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 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a ATI rage 128 all-in-blunder agp card. I'm currently writing a driver for video capture. I got everything to work properly so far, but I'm using "plugged-in" values for certain things that REQUIRE I get them from the video bios on the card (multimedia table, tv-out table, etc.). The sample source that ATI doles out directly accesses the 0xC000-0xC800 region to get the info (the example is a linux implementation). This will only work if the card is the primary adapter. If it's not, another way must be found. No matter what, I still don't want to do that, as it seems "cheesy." I've tried using the pci_read_config(dev, PCIR_BIOS, 4) command to get the base of the card's video bios, but it comes up empty. Ok, so, how do I get the address of the video bios of the card? I've tried writing to the PCIR_BIOS register with the BIOS_ENABLE bit, but I'm pretty sure that's to SET the (physical) address of the video bios. I need to GET it. Any ideas? Suggestions? - Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 1: 5:22 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 01:05:20 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139]) by hub.freebsd.org (Postfix) with ESMTP id 78D6137B400 for ; Tue, 12 Dec 2000 01:05:19 -0800 (PST) Received: from wiliam.alcove-int ([10.16.110.19]) by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian)) id 145lN4-00075M-00; Tue, 12 Dec 2000 10:05:14 +0100 Received: from nsouch by wiliam.alcove-int with local (Exim 3.12 #1 (Debian)) id 145lN4-0001ha-00; Tue, 12 Dec 2000 10:05:14 +0100 Date: Tue, 12 Dec 2000 10:05:14 +0100 From: Nicolas Souchu To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: Partial start on pci + serial/parallel cards Message-ID: <20001212100513.B6007@wiliam.alcove-int> References: <20001211154207.A25074@wiliam.alcove-int> <200012090613.XAA18688@harmony.village.org> <20001211154207.A25074@wiliam.alcove-int> <200012111836.LAA38242@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i In-Reply-To: <200012111836.LAA38242@harmony.village.org>; from imp@village.org on Mon, Dec 11, 2000 at 11:36:22AM -0700 Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Efr?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 11, 2000 at 11:36:22AM -0700, Warner Losh wrote: > In message <20001211154207.A25074@wiliam.alcove-int> Nicolas Souchu writes: > : On Fri, Dec 08, 2000 at 11:13:12PM -0700, Warner Losh wrote: > : > > : > OK. I have a partial start on the serial/parallel cards. It isn't > : > attaching anything yet, but should give people an idea on the > : > direction I'd like to head. > : > > : > As part of this work, I'll likely remove pci attachment of sio, and > : > change it to puc. puc is the name NetBSD uses (I snagged the tables > : > and some code from NetBSD's puc driver, btw) so I kept using it. I'll > : > also need to add puc attachments to sio and ppc drivers. > : > : What will actually happened to them, especially ppc? Currently, ppc is > : isa dependent so why should we change the DRIVER_MODULE directive to > : attach to puc? > > I'd make ppc less isa specific, but it isn't that hard to do from You must think of moving the microseq interpretation in an other file. > looking at the code. I'd also think about moving it to dev/ppc with a > ppc_isa.c and ppc_puc.c. This is something I don't understand. If ppc_puc is a PCI driver why don't you put in the pci directory and let ppc_isa in isa one? Nicholas -- Nicolas.Souchu@alcove.fr Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 2:16:34 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 02:16:32 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 442D737B400 for ; Tue, 12 Dec 2000 02:16:31 -0800 (PST) Received: (qmail 25470 invoked by uid 1001); 12 Dec 2000 10:16:29 +0000 (GMT) To: carock@kira.epconline.net Cc: hackers@freebsd.org Subject: Re: Top not showing CPU utilization? From: sthaug@nethelp.no In-Reply-To: Your message of "Mon, 11 Dec 2000 21:16:14 -0600 (CST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 12 Dec 2000 11:16:29 +0100 Message-ID: <25468.976616189@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am running FreeBSd 4.2 on machine with 2 Pentium II CPU's > > When I run "top", it shows my processes with 0.00% CPU Are you by any chance running an Asus P2B-DS motherboard? There was an issue with some versions of the BIOS for the motherboards not initializing the Real time clock (as far as I remember). Anyway, if this is your problem it can be fixed by upgrading the BIOS. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 2:21:36 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 02:21:35 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from samar.sasi.com (samar.sasken.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 590BF37B400 for ; Tue, 12 Dec 2000 02:21:30 -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 PAA20387 for ; Tue, 12 Dec 2000 15:51:12 +0530 (IST) Received: from suns3.sasi.com ([10.0.36.3]) by samar.sasi.com; Tue, 12 Dec 2000 15:51:11 +0000 (IST) Received: from localhost (sseth@localhost) by suns3.sasi.com (8.9.3/8.9.3) with ESMTP id PAA01319 for ; Tue, 12 Dec 2000 15:51:10 +0530 (IST) Date: Tue, 12 Dec 2000 15:51:10 +0530 (IST) From: Satyajeet Seth To: Subject: Can kernel threads be implemented using rfork? 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 Is it possible to implement threads in FreeBSD 4.0 kernel using the rfork system call? If yes, could you give an example? I tried to get the following piece of code to work without success. #include main() { if (rfork( RFPROC | RFNOWAIT | RFMEM | RFSIGSHARE ) > 0) { while(1) printf ("Parent process's pid = %d\n", getpid()); } while(1) printf ("Child process's pid = %d\n", getpid()); } Regards Satya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 2:29:11 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 02:29:09 2000 Return-Path: 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 ACAB937B402 for ; Tue, 12 Dec 2000 02:29:09 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eBCASWe04896; Tue, 12 Dec 2000 02:28:32 -0800 (PST) Date: Tue, 12 Dec 2000 02:28:32 -0800 From: Alfred Perlstein To: Satyajeet Seth Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Can kernel threads be implemented using rfork? Message-ID: <20001212022832.C16205@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 sseth@sasken.com on Tue, Dec 12, 2000 at 03:51:10PM +0530 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Satyajeet Seth [001212 02:21] wrote: > Hi > > Is it possible to implement threads in FreeBSD 4.0 kernel using the rfork > system call? If yes, could you give an example? > > > I tried to get the following piece of code to work without success. > > #include > main() > { > if (rfork( RFPROC | RFNOWAIT | RFMEM | RFSIGSHARE ) > 0) > { > while(1) > printf ("Parent process's pid = %d\n", getpid()); > } > while(1) > printf ("Child process's pid = %d\n", getpid()); > } Use the linuxthreads port and you'll save yourself a lot of work. Btw, this question gets asked once or twice a week on this list, you should check the archives before posting to -hackers. -- -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 Dec 12 4:15:22 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 04:15:21 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from security.za.net (security.za.net [196.2.146.22]) by hub.freebsd.org (Postfix) with ESMTP id 746B537B402 for ; Tue, 12 Dec 2000 04:15:18 -0800 (PST) Received: from localhost (lists@localhost) by security.za.net (8.9.3/8.9.3) with ESMTP id OAA75740 for ; Tue, 12 Dec 2000 14:15:06 +0200 (SAST) (envelope-from lists@security.za.net) Date: Tue, 12 Dec 2000 14:15:06 +0200 (SAST) From: Lists Account To: hackers@freebsd.org Subject: AMI MegaRaid Controller Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, Perhaps one of you can help me out here, I have an AMI Megaraid controller, which my FreeBSD 4 machine picks up fine, I can see the controller no problem, I however CANNOT see scbus0 or any form of the scsi bus which will allow me to run stand alone non-raid devices on the raid scsi controller. Any ideas at all would be MUCH appreciated Many Thanks Andrew Alston To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 4:18: 0 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 04:17:59 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id D456637B400 for ; Tue, 12 Dec 2000 04:17:58 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBCCRU303631; Tue, 12 Dec 2000 04:27:31 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012121227.eBCCRU303631@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Lists Account Cc: hackers@freebsd.org Subject: Re: AMI MegaRaid Controller In-reply-to: Your message of "Tue, 12 Dec 2000 14:15:06 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Dec 2000 04:27:30 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi All, > > Perhaps one of you can help me out here, I have an AMI Megaraid > controller, which my FreeBSD 4 machine picks up fine, I can see the > controller no problem, I however CANNOT see scbus0 or any form of the scsi > bus which will allow me to run stand alone non-raid devices on the raid > scsi controller. SCSI passthrough is not supported on these controllers at this time. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 6:38:31 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 06:38:29 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from spammie.svbug.com (mg131-025.ricochet.net [204.179.131.25]) by hub.freebsd.org (Postfix) with ESMTP id 7251D37B404 for ; Tue, 12 Dec 2000 06:38:26 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id GAA03155; Tue, 12 Dec 2000 06:36:07 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200012121436.GAA03155@spammie.svbug.com> Date: Tue, 12 Dec 2000 06:36:04 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: Fwd: kyxtech: freebsd outsniffed by wintendo !!?!? To: dr@kyx.net Cc: tcpdump-workers@tcpdump.org, ethereal-dev@ethereal.com, snort-devel@lists.sourceforge.net, freebsd-hackers@FreeBSD.ORG, tech@openbsd.org In-Reply-To: <0012072118150Q.09615@smp.kyx.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: jessem@spammie.svbug.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 7 Dec, Dragos Ruiu wrote: > > (Hurm.... Wintendo outperforming unix???!?? Something's > improper about this, and it ought to be fixed... :-) > Comments? Other OS numbers: more recent > FreeBSD versions? Solaris? Tru64? Optimization > patches? Can those OO MSDN lobotomies actually > be good things? Hurm... The Italian gauntlet has > been thrown down.... --dr :-) > > url: http://netgroup-serv.polito.it/winpcap/docs/performance.htm > I'm not sure if we could find someone of this caliber to run the test again. For once I must agree with Mike Smith ;-) Clearly the page: http://netgroup-serv.polito.it/winpcap/ says, "partially sponsored by MicroSoft Research". IMHO, it bait -- bad bait at that. IMO, M$ has found some hole in the FreeBSD kernel and is intending to expose it. Although I suspect the hole's been cleaned up by now by core. If Terry Lambert can chimes in, I know we might get some real answers. I'm not convinced by this M$ agent. Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 7:53: 2 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 07:52:59 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from dnsuno.ssgrr.it (dnsuno.ssgrr.it [195.31.235.10]) by hub.freebsd.org (Postfix) with ESMTP id CA62637B400 for ; Tue, 12 Dec 2000 07:52:57 -0800 (PST) Received: from sunreiss.ssgrr.it (sunreiss [195.31.235.5]) by dnsuno.ssgrr.it (8.8.8+Sun/8.8.8) with ESMTP id QAA11239; Tue, 12 Dec 2000 16:55:23 +0100 (MET) Received: from a2pc0 (a2pc0 [195.31.236.20]) by sunreiss.ssgrr.it (8.8.8+Sun/8.8.8) with SMTP id QAA03996; Tue, 12 Dec 2000 16:52:30 +0100 (MET) Message-ID: <000701c06453$b2e83740$14ec1fc3@ssgrr.it> From: "Fulvio Risso" To: , Cc: , , , , References: <200012121436.GAA03155@spammie.svbug.com> Subject: R: [Ethereal-dev] Re: Fwd: kyxtech: freebsd outsniffed by wintendo !!?!? Date: Tue, 12 Dec 2000 16:53:31 +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.2615.200 X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I do not agree with you. Partially supported by Ms Research means that we got: - software - 1 Dell workstation That's it. I *strongly* suggest to ask someone before opening your mouth. Cheers, fulvio PS As Loris said, we sent an e-mail to tcpdump-workers asking for that. We were really surprised by the poor performances of BSD. Anyway, no one answered. So, please... ----- Original Message ----- From: To: Cc: ; ; ; ; Sent: Tuesday, December 12, 2000 3:36 PM Subject: [Ethereal-dev] Re: Fwd: kyxtech: freebsd outsniffed by wintendo !!?!? > > > On 7 Dec, Dragos Ruiu wrote: > > > > (Hurm.... Wintendo outperforming unix???!?? Something's > > improper about this, and it ought to be fixed... :-) > > Comments? Other OS numbers: more recent > > FreeBSD versions? Solaris? Tru64? Optimization > > patches? Can those OO MSDN lobotomies actually > > be good things? Hurm... The Italian gauntlet has > > been thrown down.... --dr :-) > > > > url: http://netgroup-serv.polito.it/winpcap/docs/performance.htm > > > I'm not sure if we could find someone of this caliber to > run the test again. For once I must agree with Mike Smith ;-) > > Clearly the page: > > http://netgroup-serv.polito.it/winpcap/ > > says, "partially sponsored by MicroSoft Research". > > IMHO, it bait -- bad bait at that. IMO, M$ has found > some hole in the FreeBSD kernel and is intending to expose it. > Although I suspect the hole's been cleaned up by now by core. > > If Terry Lambert can chimes in, I know we might get some > real answers. I'm not convinced by this M$ agent. > > Jessem. > > > > > _______________________________________________ > Ethereal-dev mailing list > Ethereal-dev@ethereal.com > http://www.ethereal.com/mailman/listinfo/ethereal-dev > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 8:24:53 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 08:24:50 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from off.off.to (off.off.to [63.77.233.98]) by hub.freebsd.org (Postfix) with ESMTP id 002AF37B400 for ; Tue, 12 Dec 2000 08:24:49 -0800 (PST) Received: from off.off.to (localhost [127.0.0.1]) by off.off.to (8.10.1/8.10.1) with ESMTP id eBCGMtH16626; Tue, 12 Dec 2000 11:22:55 -0500 (EST) Message-Id: <200012121622.eBCGMtH16626@off.off.to> To: "Fulvio Risso" Cc: opentrax@email.com, dr@kyx.net, tcpdump-workers@tcpdump.org, ethereal-dev@ethereal.com, snort-devel@lists.sourceforge.net, freebsd-hackers@freebsd.org, tech@openbsd.org, mts@off.off.to Subject: Re: R: [Ethereal-dev] Re: Fwd: kyxtech: freebsd outsniffed by wintendo !!?!? In-reply-to: Your message of "Tue, 12 Dec 2000 16:53:31 +0100." <000701c06453$b2e83740$14ec1fc3@ssgrr.it> Date: Tue, 12 Dec 2000 11:22:55 -0500 From: "Michael T. Stolarchuk" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <000701c06453$b2e83740$14ec1fc3@ssgrr.it>, "Fulvio Risso" writes: >I do not agree with you. >Partially supported by Ms Research means that we got: >- software >- 1 Dell workstation > >That's it. >I *strongly* suggest to ask someone before opening your mouth. >Cheers, > > fulvio > >PS As Loris said, we sent an e-mail to tcpdump-workers asking for that. We >were really surprised by the poor performances of BSD. Anyway, no one >answered. So, please... fulvio, did you write this paper? were you involved in some of the work? notice at the end of the article: Notice that WinDump has been launched with the standard kernel buffer (1MB); in presence of heavy traffic the size of this buffer can be increased with a simple command line switch, improving further the overall performance of the system. Our conclusions are that BPF architecture for Windows performs well, that the dynamic buffer improves effectively the overall performances and that, among all the Windows flavors, Windows 2000 is the best platform for an high performance network analyzer. and -- : typical buffer sizes for bpf these days are still 32K, One could then say that if you up the buffer sizes to (2) 512M buffers, you'd get much better results, but the actual results are kinda suprising.... you may/may not get better performance... by increasing the buffer size, you incur a longer kernel copy of the buffer's out into user space. In short bursts, the performance may be better, but under long heavy loads, you could get *more* packet loss... even so, 32K is abysmal... and changing it, to, say, 128K may be a much better alternative... ---------- don't discount this article and its measurements... ---------- i was asked some serious questions about sniffing by some microsoft developers... The people i talked to were very serious about doing good analysis of sniffing performance. This is another example of a similar analysis, and i do belive the results... i do not think they are skewed, but i would have liked a bit more information about the bpf which was used (for example, what were the buffer sizes which were used, do you have more information about how system resources were consumed?) But i'll also point out that there ARE several platforms in existance today which use non-windows platforms and get very good sniffing results. Even so, i'd like to know whether the `wintendo' sniffing is done without ever doing any context switches; ie: much of the bpf cost in doing sniffing arised out of the need to isolate the process spaces from the kernel spaces... if you don't have the same isolation, you lose safety, but gain performance. mts. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 8:57:42 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 08:57:40 2000 Return-Path: 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 925AB37B400 for ; Tue, 12 Dec 2000 08:57:36 -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 145seA-00009q-00; Tue, 12 Dec 2000 09:51:22 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A36578A.F58A7F68@softweyr.com> Date: Tue, 12 Dec 2000 09:51:22 -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: Fulvio Risso Cc: opentrax@email.com, dr@kyx.net, tcpdump-workers@tcpdump.org, ethereal-dev@ethereal.com, snort-devel@lists.sourceforge.net, freebsd-hackers@freebsd.org, tech@openbsd.org Subject: Re: R: [Ethereal-dev] Re: Fwd: kyxtech: freebsd outsniffed by wintendo !!?!? References: <200012121436.GAA03155@spammie.svbug.com> <000701c06453$b2e83740$14ec1fc3@ssgrr.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fulvio Risso wrote: > > I do not agree with you. > Partially supported by Ms Research means that we got: > - software > - 1 Dell workstation > > That's it. > I *strongly* suggest to ask someone before opening your mouth. Mr. Risso, you should know that jessem (who seems to be JMJr. in masquerade) is basially a cartoon character. The rest of us realize that Microsoft sponsorship of such a web site means you get their software for the same price we NORMALLY charge for ours, i.e. free. We appreciate your frank discussion of the performance of the two systems, but I have to wonder if you tried capturing data to a ufs filesystem. I found it a little strange that your FreeBSD captures were written to a FAT filesystem, my impression is that FAT performance has never been a goal of the FreeBSD project. Have you attempted the same benchmarks using an ufs filesystem, and if so, how did it perform? -- "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 Dec 12 9: 7:17 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 09:07:15 2000 Return-Path: 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 CEF9137B404 for ; Tue, 12 Dec 2000 09:07:13 -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 eBCH78s74372; Tue, 12 Dec 2000 10:07:09 -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 KAA30358; Tue, 12 Dec 2000 10:07:07 -0700 (MST) Message-Id: <200012121707.KAA30358@harmony.village.org> To: Nicolas Souchu Subject: Re: Partial start on pci + serial/parallel cards Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 12 Dec 2000 10:05:14 +0100." <20001212100513.B6007@wiliam.alcove-int> References: <20001212100513.B6007@wiliam.alcove-int> <20001211154207.A25074@wiliam.alcove-int> <200012090613.XAA18688@harmony.village.org> <20001211154207.A25074@wiliam.alcove-int> <200012111836.LAA38242@harmony.village.org> Date: Tue, 12 Dec 2000 10:07:07 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001212100513.B6007@wiliam.alcove-int> Nicolas Souchu writes: : > looking at the code. I'd also think about moving it to dev/ppc with a : > ppc_isa.c and ppc_puc.c. : : This is something I don't understand. If ppc_puc is a PCI driver why don't : you put in the pci directory and let ppc_isa in isa one? Because in FreeBSD you put all the files for a driver in one directory. In NetBSD you'd do things the way you are talking about. sio and ppc break this rule right now. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 9:13:12 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 09:13:09 2000 Return-Path: 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 2BAD837B400 for ; Tue, 12 Dec 2000 09:13:09 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBCHD2E88984; Tue, 12 Dec 2000 09:13:02 -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: <200012121707.KAA30358@harmony.village.org> Date: Tue, 12 Dec 2000 09:13:07 -0800 (PST) From: John Baldwin To: Warner Losh Subject: Re: Partial start on pci + serial/parallel cards Cc: hackers@FreeBSD.org, Nicolas Souchu Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Dec-00 Warner Losh wrote: > In message <20001212100513.B6007@wiliam.alcove-int> Nicolas Souchu writes: >: > looking at the code. I'd also think about moving it to dev/ppc with a >: > ppc_isa.c and ppc_puc.c. >: >: This is something I don't understand. If ppc_puc is a PCI driver why don't >: you put in the pci directory and let ppc_isa in isa one? > > Because in FreeBSD you put all the files for a driver in one > directory. In NetBSD you'd do things the way you are talking about. > sio and ppc break this rule right now. ...and npx; fd; joy; psm; various ISA portions of vga, syscons, and atkbd; intpm; meteor; agp; all the PCI network drivers; etc. :-) > Warner -- 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 Dec 12 9:19:25 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 09:19:23 2000 Return-Path: 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 0720137B400; Tue, 12 Dec 2000 09:19:22 -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 eBCHIxs74455; Tue, 12 Dec 2000 10:18:59 -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 KAA30522; Tue, 12 Dec 2000 10:18:59 -0700 (MST) Message-Id: <200012121718.KAA30522@harmony.village.org> To: John Baldwin Subject: Re: Partial start on pci + serial/parallel cards Cc: hackers@FreeBSD.org, Nicolas Souchu In-reply-to: Your message of "Tue, 12 Dec 2000 09:13:07 PST." References: Date: Tue, 12 Dec 2000 10:18:58 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message John Baldwin writes: : : On 12-Dec-00 Warner Losh wrote: : > In message <20001212100513.B6007@wiliam.alcove-int> Nicolas Souchu writes: : >: > looking at the code. I'd also think about moving it to dev/ppc with a : >: > ppc_isa.c and ppc_puc.c. : >: : >: This is something I don't understand. If ppc_puc is a PCI driver why don't : >: you put in the pci directory and let ppc_isa in isa one? : > : > Because in FreeBSD you put all the files for a driver in one : > directory. In NetBSD you'd do things the way you are talking about. : > sio and ppc break this rule right now. : : ...and npx; fd; joy; psm; various ISA portions of vga, syscons, and atkbd; : intpm; meteor; agp; all the PCI network drivers; etc. :-) Yes. I wasn't planning on moving them. But not all the pci network drivers break this rule. vx, at the minimum, follows the new guidelines. The "common sense rider" on this rule has been don't move anything just to move it. Move it when it makes sense to move it. Many drivers have been moved out of isa/* or i386/isa/* to this new location when they grow another bus attachment (usually for pccard). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 13:31: 8 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 13:31:05 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 4D29537B402 for ; Tue, 12 Dec 2000 13:31:04 -0800 (PST) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id OAA16856 for ; Tue, 12 Dec 2000 14:27:32 -0700 (MST) Received: from 208-48-172-178.nas-2.scf.primenet.com(208.48.172.178), claiming to be "max" via SMTP by smtp05.primenet.com, id smtpdAAAuXay2G; Tue Dec 12 14:27:24 2000 Reply-To: From: "Steve Shoecraft" To: Subject: RE: Accessing the Video Bios on a PCI card?? (vm_map ?) Date: Tue, 12 Dec 2000 14:32:49 -0700 Message-ID: <000001c06483$1479e4c0$b2ac30d0@max.home.org> 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 Importance: Normal In-Reply-To: <000401c0641a$2b382140$9a3184ce@max.home.org> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok. I've been looking at the kernel source for a bit, and come up with a couple ideas how to do this. I wanted to run it by you guys to see if this is the "right way." I'm guessing I'm gonna need to write the address where I WANT the bios to show up in the PCIR_BIOS register. The problem is, how do I get that addr. Do I: /* Alloc 4k region */ /* XXX should I use kmem_alloc_nofault? */ addr = kmem_alloc(kernel_map, PAGE_SIZE); /* Get physical addr */ /* XXX do I need this? */ paddr = vtophys(addr); /* Enable BIOS */ pci_write_config(dev, PCIR_BIOS, paddr | PCIM_BIOS_ENABLE); Will this work? I haven't tried it yet, but it sure looks like it's the wrong way to do it. It seems like as soon as I access the addr, i.e.: value = *addr; it will cause a fault to occur and have a page of physical memory attached (& zero'd ??) and my read will return from the memory, instead of the bios. Is that what will happen here? - Steve -----Original Message----- From: owner-freebsd-hackers@FreeBSD.ORG [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Steve Shoecraft Sent: Tuesday, December 12, 2000 2:02 AM To: freebsd-hackers@freebsd.org Subject: Accessing the Video Bios on a PCI card?? I have a ATI rage 128 all-in-blunder agp card. I'm currently writing a driver for video capture. I got everything to work properly so far, but I'm using "plugged-in" values for certain things that REQUIRE I get them from the video bios on the card (multimedia table, tv-out table, etc.). The sample source that ATI doles out directly accesses the 0xC000-0xC800 region to get the info (the example is a linux implementation). This will only work if the card is the primary adapter. If it's not, another way must be found. No matter what, I still don't want to do that, as it seems "cheesy." I've tried using the pci_read_config(dev, PCIR_BIOS, 4) command to get the base of the card's video bios, but it comes up empty. Ok, so, how do I get the address of the video bios of the card? I've tried writing to the PCIR_BIOS register with the BIOS_ENABLE bit, but I'm pretty sure that's to SET the (physical) address of the video bios. I need to GET it. Any ideas? Suggestions? - Steve 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 Dec 12 13:48:58 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 13:48:56 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 4583B37B400 for ; Tue, 12 Dec 2000 13:48:56 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBCLwe305252; Tue, 12 Dec 2000 13:58:40 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012122158.eBCLwe305252@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: sshoecraft@1-link.net Cc: freebsd-hackers@freebsd.org Subject: Re: Accessing the Video Bios on a PCI card?? (vm_map ?) In-reply-to: Your message of "Tue, 12 Dec 2000 14:32:49 MST." <000001c06483$1479e4c0$b2ac30d0@max.home.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Dec 2000 13:58:40 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (please wrap your messages in a sane fashion!) > Ok. I've been looking at the kernel source for a bit, and come up with > a couple ideas how to do this. I wanted to run it by you guys to see if > this is the "right way." > > I'm guessing I'm gonna need to write the address where I WANT the bios > to show up in the PCIR_BIOS register. The problem is, how do I get that > addr. Do I: This is mostly correct, however the system BIOS should have done this for you already. Is this card your primary video card? > Will this work? I haven't tried it yet, but it sure looks like it's the > wrong way to do it. It seems like as soon as I access the addr, i.e.: No, you should not do it like that. The problem is depressingly difficult to resolve "cleanly". If you just want to rummage through the BIOS, and don't actually want to call any code in it, it's a little simpler. Start off by writing 0xfffffffe to the bios base address register. Then read it back and note that what you'll get is an address mask which tells you how big the ROM is. (You can convert to a size by flipping the bits and adding 1). Find a free memory area (start off by just guessing; later you'll need to use the resource manager to actually find a block) and write the physical base address of this area into the bios base address register, remembering to set the LSB to enable the decoder. Also make sure that the memory enable bit is set in the command register. Then use pmap_mapdev() to map that physical range into kernel space. That should get you going; you can look at the cardbus code to see how to find a memory range once you get to that point. (It's not perfect yet, but it works.) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 14:51:45 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 14:51:43 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ifour.com.br (unknown [200.236.148.68]) by hub.freebsd.org (Postfix) with SMTP id 92F2C37B400 for ; Tue, 12 Dec 2000 14:51:36 -0800 (PST) Received: (qmail 68718 invoked from network); 12 Dec 2000 19:58:38 -0000 Received: from port47.tdnet.com.br (HELO ifour.com.br) (200.236.148.147) by midas.ifour.com.br with SMTP; 12 Dec 2000 19:58:38 -0000 Sender: grios@FreeBSD.ORG Message-ID: <3A368F8C.1918684F@ifour.com.br> Date: Tue, 12 Dec 2000 20:50:20 +0000 From: Gustavo Vieira Goncalves Coelho Rios X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: very big mail spool directory Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, i am planning a very big email server, currently i am planning for about 8*2^16 users. I known that ufs has not good performance for very big directories, i.e., using a single directory to hold too many entries may lead to a low level performance.Since, my approach is to hash the spool mail dir for my users. Every user will have a single id that will map it's email address into a unique directory, this later will hold the user maildir. My spool mail dir is: /var/qmail/mail and all directory will be created within' it. The functions that will hash the id, accepts an id as input and returns a string for the user dir, like: Id String returned 0 0/0/0/0/0/0/0/0 1 0/0/0/0/0/0/0/1 . ./././././././. 15 0/0/0/0/0/0/0/f 16 0/0/0/0/0/0/1/0 17 0/0/0/0/0/0/1/1 . ./././././././. 32 0/0/0/0/0/0/2/0 . ./././././././. Got the ideia ? This allow me to perform at most 8*16 lookup_dir routine to get the users mails. So, my approach only works better for a number of users bigger than 96 in traditional /var/mail (that creates one file for each user, what can make performance drop down for a large amount of users). I believe my approach is very good, since if you have (for instance) 2^32 users, seeking the user dir would not take too much time! Any way i would really enjoy your comments. What you wizard have to say about my approach? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 15:34:53 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 15:34:46 2000 Return-Path: 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 3B4D437B400 for ; Tue, 12 Dec 2000 15:34:46 -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 QAA21774; Tue, 12 Dec 2000 16:33:56 -0700 Received: from 172.30.41.146 by mei00wssout01.micron.com with ESMTP ( WorldSecure Server SMTP Relay(WSS) v4.5); Tue, 12 Dec 2000 16:27:58 -0700 X-Server-Uuid: 6b1d535a-5b27-11d3-bf09-00902786a6a3 Received: by imcout1.micronpc.com with Internet Mail Service ( 5.5.2650.21) id ; Tue, 12 Dec 2000 16:27:57 -0700 Message-ID: <8D18712B2604D411A6BB009027F644980DD7D5@0SEA01EXSRV1> From: "Matt Simerson" To: "'Gustavo Vieira Goncalves Coelho Rios'" Cc: "'freebsd-hackers@freebsd.org'" Subject: RE: very big mail spool directory Date: Tue, 12 Dec 2000 16:27:47 -0700 X-Mailer: Internet Mail Service (5.5.2650.21) MIME-Version: 1.0 X-WSS-ID: 16286BF48296-01-01 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I do it a little bit differently for my million user mail server. Rather than perform any (more) hackery on my MTA/MDA than necessary, I set up each mail domain as it's own UID/GID on the system. This approach has some limits but so far it's working great for me. With FreeBSD's pw tool and a bit of scripting it's pretty simple to build yourself a /usr/home/a/aa/aar/aardvark.com style tree. This type of solution has some great advantages. Since DNS (and consequently email addresses) is a hierarchy, it makes sense to keep the highest level (the domain name) mapping in one database. Qmail does this for us via it's users mechanism so we use that. When mail arrives qmail checks the /var/qmail/users/assign.cdb file and find's the username and home directory of domain owner. Qmail-local then mosies over to that directory (/usr/home/a/aa/aar/aardvark.com/) and obeys the contents of that domains .qmail processing. From there you can do whatever you'd like with mail for that domain. I use the vpopmail (http://www.inter7.com/vpopmail) package which includes a vdelivermail program that gets called. So, your .qmail-default has a call to vdelivermail which checks the username and does a lookup in the vpasswd.cdb that's contained in the domains home dir. There it finds the mail users actual mail directory and then drops it in there (subject to quota and other configurable limitations). The vpopmail package also has some mechanisms built on so that if the number of users for a domain exceeds a given limit (I can't remember exactly how many) then it builds a hash tree. Other than some compile time tuning, I leave the /var/qmail/queue untouched. So, you end up with something like this: #grep test /etc/passwd test:*:1454:88:test.com:/usr/home/t/te/test:/sbin/nologin #grep test.com /var/qmail/users/assign +test.com-:test.com:1454:88:/usr/home/t/te/test/domains/test.com:-:: #more /usr/home/t/te/test/domains/test.com/vpasswd test:*:1:0:testing:/usr/home/t/te/test/domains/test.com/test:1000000 test2:*:1:0:TEST2:/usr/home/t/te/test/domains/test.com/test2:10000000 Every mail message ends up with two database lookups (assign.cdb & vpasswd.cdb) but the databases are fairly compact and easy to replicate across an array of machines. It also means every authentication request (POP, IMAP, & webmail) also has two database lookups but again, the lookups are from small databases, very fast, and distributed across an array of machines. This is a very simplistic overview of how it works but so far it's been a good solution. Best of luck to you. Matt > -----Original Message----- > From: Gustavo Vieira Goncalves Coelho Rios > [mailto:gustavo@ifour.com.br] > Sent: Tuesday, December 12, 2000 12:50 PM > To: hackers@freebsd.org > Subject: very big mail spool directory > > > Hi folks, > > i am planning a very big email server, currently i am > planning for about > 8*2^16 users. > > I known that ufs has not good performance for very big directories, > i.e., using a single directory to hold too many entries may lead to a > low level performance.Since, my approach is to hash the spool mail dir > for my users. > > Every user will have a single id that will map it's email > address into a > unique directory, this later will hold the user maildir. My spool mail > dir is: /var/qmail/mail and all directory will be created within' it. > > The functions that will hash the id, accepts an id as input > and returns > a string for the user dir, like: > > Id String returned > 0 0/0/0/0/0/0/0/0 > 1 0/0/0/0/0/0/0/1 > . ./././././././. > 15 0/0/0/0/0/0/0/f > 16 0/0/0/0/0/0/1/0 > 17 0/0/0/0/0/0/1/1 > . ./././././././. > 32 0/0/0/0/0/0/2/0 > . ./././././././. > > > Got the ideia ? This allow me to perform at most 8*16 > lookup_dir routine > to get the users mails. So, my approach only works better for a number > of users bigger than 96 in traditional /var/mail (that > creates one file > for each user, what can make performance drop down for a > large amount of > users). I believe my approach is very good, since if you have (for > instance) 2^32 users, seeking the user dir would not take too > much time! > Any way i would really enjoy your comments. > > What you wizard have to say about my approach? > > > 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 Dec 12 16:26:15 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 16:26:13 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ifour.com.br (unknown [200.236.148.68]) by hub.freebsd.org (Postfix) with SMTP id A836D37B400 for ; Tue, 12 Dec 2000 16:26:10 -0800 (PST) Received: (qmail 68948 invoked from network); 12 Dec 2000 21:33:11 -0000 Received: from port89.tdnet.com.br (HELO ifour.com.br) (200.236.148.189) by midas.ifour.com.br with SMTP; 12 Dec 2000 21:33:11 -0000 Sender: grios@FreeBSD.ORG Message-ID: <3A36A5B5.A5332B83@ifour.com.br> Date: Tue, 12 Dec 2000 22:24:53 +0000 From: Gustavo Vieira Goncalves Coelho Rios X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Matt Simerson Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: very big mail spool directory References: <8D18712B2604D411A6BB009027F644980DD7D5@0SEA01EXSRV1> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Simerson wrote: > > I do it a little bit differently for my million user mail server. Rather > than perform any (more) hackery on my MTA/MDA than necessary, I set up each > mail domain as it's own UID/GID on the system. This approach has some limits > but so far it's working great for me. With FreeBSD's pw tool and a bit of > scripting it's pretty simple to build yourself a > /usr/home/a/aa/aar/aardvark.com style tree. > > This type of solution has some great advantages. Since DNS (and consequently > email addresses) is a hierarchy, it makes sense to keep the highest level > (the domain name) mapping in one database. Qmail does this for us via it's > users mechanism so we use that. When mail arrives qmail checks the > /var/qmail/users/assign.cdb file and find's the username and home directory > of domain owner. Qmail-local then mosies over to that directory > (/usr/home/a/aa/aar/aardvark.com/) and obeys the contents of that domains > .qmail processing. From there you can do whatever you'd like with mail for > that domain. > > I use the vpopmail (http://www.inter7.com/vpopmail) package which includes a > vdelivermail program that gets called. So, your .qmail-default has a call to > vdelivermail which checks the username and does a lookup in the vpasswd.cdb > that's contained in the domains home dir. There it finds the mail users > actual mail directory and then drops it in there (subject to quota and other > configurable limitations). > > The vpopmail package also has some mechanisms built on so that if the number > of users for a domain exceeds a given limit (I can't remember exactly how > many) then it builds a hash tree. > > Other than some compile time tuning, I leave the /var/qmail/queue untouched. > > So, you end up with something like this: > > #grep test /etc/passwd > test:*:1454:88:test.com:/usr/home/t/te/test:/sbin/nologin > > #grep test.com /var/qmail/users/assign > +test.com-:test.com:1454:88:/usr/home/t/te/test/domains/test.com:-:: > > #more /usr/home/t/te/test/domains/test.com/vpasswd > test:*:1:0:testing:/usr/home/t/te/test/domains/test.com/test:1000000 > test2:*:1:0:TEST2:/usr/home/t/te/test/domains/test.com/test2:10000000 > > Every mail message ends up with two database lookups (assign.cdb & > vpasswd.cdb) but the databases are fairly compact and easy to replicate > across an array of machines. It also means every authentication request > (POP, IMAP, & webmail) also has two database lookups but again, the lookups > are from small databases, very fast, and distributed across an array of > machines. This is a very simplistic overview of how it works but so far it's > been a good solution. > > Best of luck to you. Thanks for your response, but i some other questions raised: How many users your get? I would not enjoy having any system account for mail system. Qmail let me use a single UID for everytinhg, since i will only need a pop account that will allow me to retrieve the user mails. I will not need more than a single uid/gid. My ideia is to allow the more users served using the small number of resources. Would my approach permit me that ? Thanks again for your time and cooperation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 17:11:59 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 17:11:56 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id BAA2A37B400 for ; Tue, 12 Dec 2000 17:11:56 -0800 (PST) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id SAA26647 for ; Tue, 12 Dec 2000 18:09:37 -0700 (MST) Received: from 207-218-5-143.nas-1.scf.gblx.net(207.218.5.143), claiming to be "max" via SMTP by smtp03.primenet.com, id smtpdAAAMxai9Z; Tue Dec 12 18:09:27 2000 Reply-To: From: "Steve Shoecraft" To: Subject: RE: Accessing the Video Bios on a PCI card?? (vm_map ?) Date: Tue, 12 Dec 2000 18:13:40 -0700 Message-ID: <000101c064a1$ee6ce4c0$8f05dacf@max.home.org> 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 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (this is a winblows system with my work-related email on it - you expect sane wrapping?) Anyway ... I got the size of the bios using the method you suggested. I used malloc to get a chunk of memory, turned the ptr into a physical addr, then used free to get rid of it. I then used pmap_mapdev to map the phsy to virt. You suggested using the resource manager to find a block ... how do I go about doing that? I've tried bus_alloc_resource with the MEMORY type, but it always fails... Any hints? Oh, and yes, the card is my primary adapter. I just want my driver to work even if the card is not the primary adapter. - Steve -----Original Message----- From: Mike Smith [mailto:msmith@freebsd.org] Sent: Tuesday, December 12, 2000 2:59 PM To: sshoecraft@1-link.net Cc: freebsd-hackers@freebsd.org Subject: Re: Accessing the Video Bios on a PCI card?? (vm_map ?) (please wrap your messages in a sane fashion!) > Ok. I've been looking at the kernel source for a bit, and come up with > a couple ideas how to do this. I wanted to run it by you guys to see if > this is the "right way." > > I'm guessing I'm gonna need to write the address where I WANT the bios > to show up in the PCIR_BIOS register. The problem is, how do I get that > addr. Do I: This is mostly correct, however the system BIOS should have done this for you already. Is this card your primary video card? > Will this work? I haven't tried it yet, but it sure looks like it's the > wrong way to do it. It seems like as soon as I access the addr, i.e.: No, you should not do it like that. The problem is depressingly difficult to resolve "cleanly". If you just want to rummage through the BIOS, and don't actually want to call any code in it, it's a little simpler. Start off by writing 0xfffffffe to the bios base address register. Then read it back and note that what you'll get is an address mask which tells you how big the ROM is. (You can convert to a size by flipping the bits and adding 1). Find a free memory area (start off by just guessing; later you'll need to use the resource manager to actually find a block) and write the physical base address of this area into the bios base address register, remembering to set the LSB to enable the decoder. Also make sure that the memory enable bit is set in the command register. Then use pmap_mapdev() to map that physical range into kernel space. That should get you going; you can look at the cardbus code to see how to find a memory range once you get to that point. (It's not perfect yet, but it works.) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 19:52: 7 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 19:52:05 2000 Return-Path: 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 0A91F37B400 for ; Tue, 12 Dec 2000 19:52:04 -0800 (PST) Received: from newsguy.com (p27-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.92]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id MAA19990; Wed, 13 Dec 2000 12:51:34 +0900 (JST) Message-ID: <3A36BDB7.403B610@newsguy.com> Date: Wed, 13 Dec 2000 09:07:19 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Gustavo Vieira Goncalves Coelho Rios Cc: hackers@FreeBSD.ORG Subject: Re: very big mail spool directory References: <3A368F8C.1918684F@ifour.com.br> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gustavo Vieira Goncalves Coelho Rios wrote: > > The functions that will hash the id, accepts an id as input and returns > a string for the user dir, like: > > Id String returned > 0 0/0/0/0/0/0/0/0 > 1 0/0/0/0/0/0/0/1 > . ./././././././. > 15 0/0/0/0/0/0/0/f > 16 0/0/0/0/0/0/1/0 > 17 0/0/0/0/0/0/1/1 > . ./././././././. > 32 0/0/0/0/0/0/2/0 > . ./././././././. This is unnecessarily too deep. I think you would be better off with 256 entries in each directory, and cut the depth by half. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.great.underground.bsdconpiracy.org "The bronze landed last, which canceled that method of impartial choice." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 19:55:24 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 19:55:23 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from au2.samba.org (ns1.samba.org [203.17.0.92]) by hub.freebsd.org (Postfix) with ESMTP id 09A8A37B400 for ; Tue, 12 Dec 2000 19:55:22 -0800 (PST) Received: by au2.samba.org (Postfix, from userid 148) id 6B1DE659834; Wed, 13 Dec 2000 14:48:59 +1100 (EST) From: Andrew Tridgell To: nsayer@quack.kfu.com Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: <3A3563EC.7B54BCA8@sftw.com> (message from Nick Sayer on Mon, 11 Dec 2000 15:31:56 -0800) Subject: Re: Nick's semi-periodic hardware support prize -- take 2 Reply-To: tridge@linuxcare.com References: <3A25E6E1.24C006B9@quack.kfu.com> <3A3563EC.7B54BCA8@sftw.com> Message-Id: <20001213034859.6B1DE659834@au2.samba.org> Date: Wed, 13 Dec 2000 14:48:59 +1100 (EST) Sender: tridge@au2.samba.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick, Thanks for the prize! Please give the money to the FreeBSD foundation. Did you manage to get an interrupt out of the SPIC ? I suspect there is a irq mask register hidden in there somewhere that is preventing interrupts but haven't found it. Where do I get the code for your driver? Cheers, Tridge PS: I've recently added code for setting the screen brightness and querying the battery. See http://us5.samba.org/ftp/unpacked/picturebook/ The cute thing is that you can "set" the battery charge! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 12 22:21:31 2000 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 12 22:21:27 2000 Return-Path: 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 4004637B400; Tue, 12 Dec 2000 22:21:27 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eBD6LPa80568; Tue, 12 Dec 2000 22:21:25 -0800 (PST) (envelope-from dillon) Date: Tue, 12 Dec 2000 22:21:25 -0800 (PST) From: Matt Dillon Message-Id: <200012130621.eBD6LPa80568@earth.backplane.com> To: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Cc: Kachun Lee , Paul Saab Subject: Patches available (was Re: Extreme high load with 12/7 4-releng) References: <200012120230.SAA32402@pathlink.net> <200012121801.KAA42878@pathlink.net> <200012122138.NAA69074@pathlink.net> <200012122231.eBCMVE353411@earth.backplane.com> <200012130209.eBD290M79194@earth.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have made a patchset available for both -current and -stable on my site: http://apollo.backplane.com/FreeBSD4/ This patchset contains debugging code for the pageout daemon which can be turned on with: sysctl -w vm.debug_pageout_stats=1 The debugging code prints a line to dmesg and /var/log/messages each time the pageout daemon runs a scan, and tells you how many clean pages, dirty pages, and skipped pages were scanned, as well as the calculated page deficit for the invalid queue scan and the active queue scan. This output would be invaluable to me coming from people who still have major performance problems on heavily loaded machines. I would appreciate wide testing, especially by anyone running heavily loaded -stable boxes. I am especially interested in how this patchset performs on news boxes. Pleae keep in mind that -current is unstable at the moment and that the instability has nothing to do with this or other VM/low-memory related patchsets. (Paul, I'm cc'ing you to see if you could run those heavy-load tests with this patchset. My tests showed a remarkable improvement in response times). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 1:21:41 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 01:21:38 2000 Return-Path: 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 77EFC37B400 for ; Wed, 13 Dec 2000 01:21:37 -0800 (PST) Received: from [194.207.93.139] by gate.trident-uk.co.uk for freebsd-hackers@freebsd.org id JAA29588; Wed Dec 13 09:18:58 2000 Organization: Psi-Domain Ltd. Subject: Re: hardware Dell or BSDi Date: Wed, 13 Dec 2000 09:24:03 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <200012130749.IAA08219@mail.hmth.nl> In-Reply-To: <200012130749.IAA08219@mail.hmth.nl> MIME-Version: 1.0 Message-Id: <00121309232802.00233@freefire.psi-domain.co.uk> Content-Transfer-Encoding: 8bit To: freebsd-hackers@freebsd.org From: Jamie Heckford Reply-To: heckfordj@psi-domain.co.uk Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://www.psi-domain.co.uk/ alot cheaper and better. -- 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, 13 Dec 2000, you wrote: > Hello all, > > We are going to buy our first 1U 19" rack server (pizzacarton size), and > probably there will be more in the future, they have to run FreeBSD > 4.1-stable. > > Normally we buy all our hardware at Dell, they also have this kind of > servers, for instance the PowerApp Web 100, we have also seen this kind of > servers form BSDi.com, they have FreeBSD preinstalled, and say they are > completely optimized. But they are considerably more expensive. > > Can anyone tell me more about both these servers, how good is the BSDi > machine (and the organization), does FreeBSD install on the Dell and so on? > > tia > Jeroen Heijungs > Het Muziektheater > Amsterdam, The Netherlands > > > > 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 Dec 13 3:55:13 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 03:55:11 2000 Return-Path: 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 87D5A37B402 for ; Wed, 13 Dec 2000 03:55:10 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA66089; Wed, 13 Dec 2000 12:53:55 +0100 (CET) (envelope-from des@ofug.org) Sender: 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: Gustavo Vieira Goncalves Coelho Rios Cc: hackers@FreeBSD.ORG Subject: Re: very big mail spool directory References: <3A368F8C.1918684F@ifour.com.br> From: Dag-Erling Smorgrav Date: 13 Dec 2000 12:53:54 +0100 In-Reply-To: Gustavo Vieira Goncalves Coelho Rios's message of "Tue, 12 Dec 2000 20:50:20 +0000" Message-ID: Lines: 21 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 Gustavo Vieira Goncalves Coelho Rios writes: > The functions that will hash the id, accepts an id as input and returns > a string for the user dir, like: > > Id String returned > 0 0/0/0/0/0/0/0/0 > [..] That gives you 2^32 leaf directories plus approximately 2^28 intermediate directories, which is a helluva lot of inodes (4581298448 to be exact), and your files will be spread all over your disk(s), throwing performance down the drain. If you only have half a million users, pick a prime number K close to the square root of the expected number of users (724 in your case - closest primes are 719 and 727), create that many bucket directories, and place each user in bucket ID mod K. 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 Wed Dec 13 5:53:11 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 05:53:09 2000 Return-Path: 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 617E537B400 for ; Wed, 13 Dec 2000 05:53:05 -0800 (PST) Received: from localhost (dphoenix@localhost) by gandalf.bravenet.com (8.10.1/8.10.1) with ESMTP id eBDDqSN15006; Wed, 13 Dec 2000 05:52:28 -0800 (PST) X-Authentication-Warning: gandalf.bravenet.com: dphoenix owned process doing -bs Date: Wed, 13 Dec 2000 05:52:27 -0800 (PST) From: Dan Phoenix To: Bill Fumerola Cc: freebsd-hackers@FreeBSD.ORG Subject: Tun driver? 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 [root@elrond conf]# ifconfig tun0 1.1.1.1 up ifconfig: interface tun0 does not exist [root@elrond conf]# ls -al /dev/tun0 crw------- 1 uucp dialer 52, 0 Dec 12 13:30 /dev/tun0 [root@elrond conf]# this is confusing me....trying to get vtund working in ports collection. tun device is in GENERIC kernel when i checked and exist in /dev as per test above.....yet it tells me it does not exist! Ideas? -- 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 Wed Dec 13 5:56:11 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 05:56:09 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 1893437B400 for ; Wed, 13 Dec 2000 05:56:07 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eBDDsmi04583; Wed, 13 Dec 2000 14:54:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Dan Phoenix Cc: Bill Fumerola , freebsd-hackers@FreeBSD.ORG Subject: Re: Tun driver? In-Reply-To: Your message of "Wed, 13 Dec 2000 05:52:27 PST." Date: Wed, 13 Dec 2000 14:54:48 +0100 Message-ID: <4581.976715688@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You need to open the "device-side" of the tunnel (/dev/tun0) before the interface is created. Poul-Henning In message , Dan Phoenix writes: > >[root@elrond conf]# ifconfig tun0 1.1.1.1 up >ifconfig: interface tun0 does not exist >[root@elrond conf]# ls -al /dev/tun0 >crw------- 1 uucp dialer 52, 0 Dec 12 13:30 /dev/tun0 >[root@elrond conf]# > >this is confusing me....trying to get vtund working in ports collection. > >tun device is in GENERIC kernel when i checked >and exist in /dev as per test above.....yet >it tells me it does not exist! >Ideas? > > > > > > > >-- >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 > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 6: 5:54 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 06:05:51 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from crotchety.newsbastards.org (netcop.newsbastards.org [193.162.153.124]) by hub.freebsd.org (Postfix) with ESMTP id 3FAC637B400; Wed, 13 Dec 2000 06:05:50 -0800 (PST) Received: (from news@localhost) by crotchety.newsbastards.org (8.11.1/8.11.1) id eBDE50G03431; Wed, 13 Dec 2000 15:05:00 +0100 (CET) (envelope-from newsmeower@free-pr0n.netscum.dk) Date: Wed, 13 Dec 2000 15:05:00 +0100 (CET) Message-Id: <200012131405.eBDE50G03431@crotchety.newsbastards.org> X-Authentication-Warning: crotchety.newsbastards.org: news set sender to newsmeower@free-pr0n.netscum.dk using -f Reply-To: freebsd-hacker@netscum.dk To: Matt Dillon From: News Account In-Reply-To: <200012130621.eBD6LPa80568@earth.backplane.com> Cc: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Patches available (was Re: Extreme high load with 12/7 4-releng) References: <200012120230.SAA32402@pathlink.net> <200012121801.KAA42878@pathlink.net> <200012122138.NAA69074@pathlink.net> <200012122231.eBCMVE353411@earth.backplane.com> <200012130209.eBD290M79194@earth.backplane.com> <200012130621.eBD6LPa80568@earth.backplane.com> Sender: newsmeower@free-pr0n.netscum.dk Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have made a patchset available for both -current and -stable on my site: > http://apollo.backplane.com/FreeBSD4/ > sysctl -w vm.debug_pageout_stats=1 > The debugging code prints a line to dmesg and /var/log/messages each > time the pageout daemon runs a scan, and tells you how many clean pages, [...] > This output would be invaluable to me coming from people who still have > major performance problems on heavily loaded machines. > > I would appreciate wide testing, especially by anyone running heavily > loaded -stable boxes. I am especially interested in how this patchset > performs on news boxes. Okay, I'm gathering data as we speak, but, would you still want to see this data from a news box, if I had *not* been noticing major performance problems, just to have some numbers to drool over? Regardless, I'll keep running the patchset on this lightly-loaded news box (-stable) which seems to be pretty responsive... thanks! barry bouwsma, lame-duck newsmangler at tele danmark internet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 6:22:33 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 06:22:27 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from arka.ids.bielsko.pl (arka.ids.bielsko.pl [195.117.233.8]) by hub.freebsd.org (Postfix) with ESMTP id 08F4837B402 for ; Wed, 13 Dec 2000 06:21:20 -0800 (PST) Received: by arka.ids.bielsko.pl (8.9.3/8.9.3) id PAA05621 for freebsd-hackers@FreeBSD.org; Wed, 13 Dec 2000 15:18:47 +0100 (MET) Date: Wed, 13 Dec 2000 15:18:47 +0100 (MET) Message-Id: <200012131418.PAA05621@arka.ids.bielsko.pl> Subject: New European Promotional Contest From: office@euroleader.org MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Content-Type: multipart/alternative; boundary="------------070C33C436192682FC31B74B" Sender: lider@arka.ids.bielsko.pl Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------070C33C436192682FC31B74B Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit Dear Sirs, We are very pleased to welcome you and present a new economic initiative for producers from all European countries - both western and eastern. FOR THE FIRST TIME - ON SUCH A LARGE SCALE - IN THE VERY HEART OF EUROPE! [Image] "EURO LEADER 2001" This is an honourable title and prestigious Promotional Emblem in European Promotional Contest. This is an effective tool of promotion and marketing in Europe by means of which it is much easier to reach western markets, increase export and gain new partners for cooperation in the field of production and investment. The contest is a Polish initiative. It will be settled in March, 2001 in Warsaw. Therefore it will bring the best commercial effects on a stable, almost 40-million prospective customers Polish market, having over 5% economic growth, which will soon become an integral market of European Union. Click http://www.euroleader.org/ and get acquainted with the details of the contest, enter for the European competition. It will bring you success and a good start in the XXI century! You are good but are you well-known? You will be well-known! Join us. Yours faithfully, INTERRES International Building Fair and Promotion - from Poland B2B - Internet Portal Tadeusz Ziobro - President. --------------070C33C436192682FC31B74B Content-Type: multipart/related; boundary="------------CEE33E5E78D696CB4E0EC941" --------------CEE33E5E78D696CB4E0EC941 Content-Type: text/html; charset=iso-8859-2 Content-Transfer-Encoding: 8bit
Dear Sirs,

We are very pleased to welcome you and present a new economic initiative
for producers from all European countries - both western and eastern.

FOR THE FIRST TIME - ON SUCH A LARGE SCALE - IN THE VERY HEART OF EUROPE!

"EURO LEADER 2001"

This is an honourable title and prestigious Promotional Emblem
in European Promotional Contest.

This is an effective tool of promotion and marketing in Europe
by means of which it is much easier to reach western markets,
increase export and gain new partners for cooperation in the
field of production and investment.




The contest is a Polish initiative.
It will be settled in March, 2001 in Warsaw. Therefore it will bring the best commercial effects on a stable, almost 40-million
prospective customers Polish market, having over 5% economic growth, which will soon become an integral market of European Union.

Click http://www.euroleader.org/ and get acquainted with the details of the contest, enter for the European competition.

It will bring you success and a good start in the XXI century!
You are good but are you well-known? You will be well-known! Join us.

Yours faithfully,

INTERRES International Building Fair and Promotion - from Poland
B2B - Internet Portal
Tadeusz Ziobro - President.
  --------------CEE33E5E78D696CB4E0EC941 Content-Type: image/jpeg Content-ID: Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="C:\WINDOWS\TEMP\nsmail24.jpeg" /9j/4AAQSkZJRgABAgEASABIAAD//gAmRmlsZSB3cml0dGVuIGJ5IEFkb2JlIFBob3Rvc2hv cKggNS4w/+4ADkFkb2JlAGSAAAAAAf/bAIQADAgICAkIDAkJDBELCgsRFQ8MDA8VGBMTFRMT GBEMDAwMDAwRDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAENCwsNDg0QDg4QFA4ODhQU Dg4ODhQRDAwMDAwREQwMDAwMDBEMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwM/8AAEQgA eAB4AwEiAAIRAQMRAf/dAAQACP/EAT8AAAEFAQEBAQEBAAAAAAAAAAMAAQIEBQYHCAkKCwEA AQUBAQEBAQEAAAAAAAAAAQACAwQFBgcICQoLEAABBAEDAgQCBQcGCAUDDDMBAAIRAwQhEjEF QVFhEyJxgTIGFJGhsUIjJBVSwWIzNHKC0UMHJZJT8OHxY3M1FqKygyZEk1RkRcKjdDYX0lXi ZfKzhMPTdePzRieUpIW0lcTU5PSltcXV5fVWZnaGlqa2xtbm9jdHV2d3h5ent8fX5/cRAAIC AQIEBAMEBQYHBwYFNQEAAhEDITESBEFRYXEiEwUygZEUobFCI8FS0fAzJGLhcoKSQ1MVY3M0 8SUGFqKygwcmNcLSRJNUoxdkRVU2dGXi8rOEw9N14/NGlKSFtJXE1OT0pbXF1eX1VmZ2hpam tsbW5vYnN0dXZ3eHl6e3x//aAAwDAQACEQMRAD8A1Prf9b+sdH6w/FxXtNRaHAOHCxP/ABx/ rF+8z7kv8Y//AIonf1AuVWjixQMIkxGy0kvVf+OP9Yv3mfcl/wCOP9Yv3mfcuVST/Zx/uhVl 6r/xyPrF+8z7kv8AxyPrF+8z7lysGJ7BJL2cf7oVZeq/8cj6xeLPuS/8cf6x6ElgB40WJ0bA wOoZQxcvN+wF8Cq1zNzC4/mWO3N9Jdz176jdOp6LhG7Pbhs6ZW5l2S9kize71Poh30/UPsUU /ZhIRMRr4K1cH/xyPrF+8z7kv/HH+sX7zPuXMXCltrxQ51lQMMe9u1zh+85ku2KHMAak6AfF Sezj/dH2KsvVf+OP9Yv3mfcl/wCOP9Yv3mfcuby8W/DybMXIbsupdssb4EIKXtYz+iFWXqv/ ABx/rF+8z7kv/HH+sX7zPuXKpI+zj/dCrL6L9UPrf1jrHWGYuU9oqDS4ho5SWJ/i3/8AFE3+ oUlD7cPf4eEVw7KvR//QB/jH/wDFE7+oFyq6r/GP/wCKJ39QLlVqYf5uPksO6kTHZTZexl9v oVOMPt2l+0fvbG+5yjsfsNm07AdpdGm4jdtn+qo69k9T6P0z6g0P+r2ZSzNpyH55rsx8tjSW NFR3N7/nS/euE6rhYmDknGxsxudskWW1tLaw4fmse4/pVu4f19zOm14eH0+hg6diV+nZTYPd cT/PWPsH8179/p7f+uLmsh1Lr7HUNLKXPc6tjuWtJ3NYY/dUOKOQSkZnQ6jb8UmmeBdRRm0X 5FZtpqe176hA3bTuDJP7zlu5n146n1LGzcPqbGXYuY39FWwBpoe33Uuqd+e1u3371zaSklCM iCRZG3gi1fFdZ9Q6ei5/Uq8DOwPVyWTdTlNe6B6fv25FW7Z9L6D1yasYnUMvCbc3FsNJyWen a9uj9k7jW1/5m/8AP2pZImUSAaP2KD3f+MSroeG5uV9g+0Z/UAYyS9wqbsDWb9rHfpLdv5q8 8Vh2flvwW9PfYX4tb/VqrdrsdG13pu+kxr/zmKvwJPZDFAwjwk34pKklYzcHJwbW05Ldj31s uaP5NjfUZ/0VXTwb1CHqv8W//iib/UKSX+Lf/wAUTf6hSUH/AII/wU9H/9EH+Mf/AMUTv6gX N4bcN2Qxuc+yvHOj7KQHPb/K2Pjcuk/xkf8Aiid/UC5XQ88d4Wni/mo+S07vqFH1K6I/6quo ZnOdjW2DOHUNoBDWtj6H7npb15xns6fXkuZ062y/GboLrWhhcf3mMb9Gv93ctofXvrNeTW6n YzBprFDOnxNRqA2RY76brXf6Vc67aXHYNrZO1p1gfmt/soYYZIk8Zu9Qo0skr1HQus5NLL6M O2yqwSx7QII4THonVxkDFOJZ9ocw2Nqj3FgO0vS+84LI97Hcb4hxxuPD83Erhl2P2NJJXP2P 1T7WMI4tn2ot3imPdt/fSPRuqjKGH9ls+1FnqCmPds/fS+8Yf87D5eP54/zf7/8Ac/rK4T2L TSV+3oPW6mF9mDcGjk7Z/wCpVKuqy2xtVTHPseYaxoJcT4bU6GbFMGUMkZiPzGMoyEfPhUYk bgsV0H1PPTMjqdXTOo9OZnNyn7WWy4PrMbvdtc1tlPt9yz7fq/1umo22YVrWDUnbMR4hqrYe dlYNjrsSw1WuY6v1G/Sa130/Td+Y530d6aMmPNCXtZIzrS8cuLhl5wUQRuCPN9K+v37ExsBn UX9Prz8gn7LVaXHZXG5w9X0nDds93sXl5MmdBOunCNXm5VeLbhtsP2a8h1lR1aXtMttG76Nv 8tARxY+CNE8Xj4KJt6r/ABb/APiib/UKSX+Lf/xRN/qFJM/8Ef4Kuj//0gf4yP8AxRO/qBc3 i4eRmOsZjsL3VVvuePBlY32OXSf4xzH1jJiYYNDwun+oNHQcrAtz6MAYV75xLyXudW+Yc5tP qO/P/dV/3PbwxNXoFtavl3mkFu/W1nSMTqVvTemYH2QYj9llr3Oc95j8xrnOayrX+2sIKeMu IA1V90PpP1eJ/wCbOIRYKSKTFroIb7ne87vaqeFbY/62NbZlMzdmG6Law1oEunZ+iLmqj0n6 2dHxekUdPyqrbHVsLLQGhzDJcY1P8pUr/rL0/H6zj5/SsYV011Gq6na2vfuPujZ+d/KXIQ+F 85LPz49iQ98Z/anIY+A8fqh+s/nI8f8AiNw5YcOP1D08Nh3Xf+Lqv/wmVJ//AIuKv/CJ/KVW /wCeH1b9cZxx7ftmz0w7YN23/R7921ZVH1pod9Y3dWy63MoFJprrZDnAfmzwm4vh/OzEieXn j9rkZcp6+G8ub/VqOSAr1A3Pj8g9q05rMy6yx9bcBtbTWPzw8fzrnO/0e1ZH1cb07L6r1Tqm IGkPtbXU+IgbZssaPzfWeqVf15xB1C57mWuwXsb6Ygbm2DR/tn+bsWVhfWPF6X1bIu6ex1nT 8shz8d8Nc13P6Plvs/NUfL/Bue9jmoHFLHlyYMccfDUMOSMZQyZcWT/yo9H/AKUTLNDiibsA m+48f7r03S/rFkZ3WcnpzsU1Mo3bbZM+w7f0kjb+k/NXKfXDFpxuuWikBjbWNtcwaAOcPdH9 b6S6G76+9HbWXU1W2XEfQIDBP8uyVxnUM7I6jmWZmQQbLTwOAB9Fjf5LFo/BOR5jHzks55Y8 lg9kYjjlPj93KOH9Z6mPPOJgI8XHK7vsELKrXgllbngclrS6PjtC0+qfV/M6djdPudXY451H rOaGk7Xbv5v2/wDB+k9T+qmf1LE6zjMwLvS+0WNZcH61mv6Vjrmn/R17nb/zF3fX/rji5XR8 7/m/mN+24hBedvuNUhl1uLv+nt3fzi38mScZxAAIO/19Pqa4Dy/+Llrm/WMNcC1wYZBEEfFJ L/F05z/rJve4ve5pLnOMkk/nOJSQ/wDBH+Aro//TB/jI/wDFE7+oFzz+o5j8WjD9VzMfGJfV Ww7RvJ3G5236Vv8ALXQ/4yP/ABRO/qBcoSBqTHxWniAOOHktO7Yzc7Kz7vtGW/1b9rWOsP0n Bg2sNn7z9v56AeCrf7Nv/Y/7Y0+zfaPs0/ytu/du/wCgqcgg7TPwUka6dNEPR/Wqqqvp/RzW xrC7HJcWgAnRn0o+ktPJqya/qtjWYmHj21uxT9rueAHsEaWV/vvVTrD+jdR6PiOHUGsycLHh tAEl7y1v6M/u/RUc67puZ0DCrHUhRfiY53YzZPqOI/mX8N/NXMAzli5OBjkBxc1m97jxZ5xq css8XycHHH1Q4J/zcGzoDM6axFUYtn6mdPxremZD8ljXnMsNFRcAT7WH6O5VvqrW3Gp6w62l ltmGyQ2xocNzN/j/AFUfC650jp3TukYzgMiyt3qWvY4j0bHfSfY2P0nts+ip42Z0VvUOts+2 114+e1vpW6kS5p9Tbp+Y5Mzy5mUueM8eb2uYljnj9Mj6OV5qGGXt8Hr9eD1/KmPD6KIuII/x otDruNg5XSsDruLS3GfkvFeRSzRu6eWt/rNWn9casijprhj4dDcJzGC3JADbGvJ0awN/NWR1 3qXThgYXRumPN2PhuD7LyI3O/k/e5zlb+td/TOoU/asbqQc+uprBhtmHkH6Wvt3NlS48eYZf h5nHIMUcvMGAywy5ZQwe7j+6xy8H83Pg/m5Z/wCbQTGslVdR2r5v0nZx8VtlXTqX4dD+n3Ym 7MvcxoLXBrdh9T81ef3NY26xtZ3Vh7gw+LQfb/0V2ret9Jtw6emX5LBj3YPp2v1hlrdoa1+i 4gtIO3mDEjv8FY+A480ZcwcsZwsjhjIS4Zx483631/5X/J/7OGJbnIPDWv8ALZYGPyJAxxp8 Fq9D+r2Z1bKuobXZX6NFl0lpbLmj9DX7h/hLFmupvY3dZU9g4Jc1zRPh7gtwSBJF6jdgen/x b/8Aiib/AFCkl/i3/wDFE3+oUlD/AOCP8FPR/9QH+Mj/AMUTv6gXO4Gff0/JblUBjns5ZY0P Y4d2PY/95dF/jI/8UTv6gXLBxaQQYIMg+YWniF4og9lp3fZm53Tz00YfoYv7Rdjfav2V7du/ b6m3Zt/f/k715Dn9Qv6jkuyr2sY5/FdTAxjR2YxjP3UL7Rf6/wBp9R3r7t/qyd+7nfv+luUC 4uJc4ySSSfMoYsIxkm7v8FErJKTarHse9jS5lQDrHAaNBOwOd/aUVKhSSSSKlJJJJKUkiU49 17ntpYXmtjrXgdmME2P/ALKGgp9G+qf1vZ07oLbev5Ze193pYTY32+m2Gvsf+e6lln57lzn1 66pm5vWXsfki/AAbZhCs/o/TeNzX+36Vn5r3rnJP8Akoo4YxmZjc+H/RTb1X+Lf/AMUTf6hS S/xb/wDiib/UKSb/AOCP8FXR/9UH+Mj/AMUTv6gXKrqv8Y//AIonf1AuVWph/m4+Sw7qUqjU LGm1rn1z72sO1xHfa4h21yiknqfUfqv9WPq5mdCy34Vl9tHVGela66BZXsP0GQwN3Ms9y8/6 5T0bHzHY/SX33V0ktsvvIG5w9rvSraxm1rf5aOz62dYx6sOjBuOJRgD9FVXw53NlmRP896jj 9D6Czs/LObmXZbmNqdkPNj2M+iHO+ntn953uUOPHOM5GUiQdtf8ApJJQTCt4PTb87GzcmiCz p9Qut7yC7Zt/7+q9Vj6bWW1na+shzTzBHk5esfVjreBZ0XEt6sMXDyOoF1bGBraxcGksbYa4 /P8A+20c2SUACBdn+WigHyMOB4IPwUgQCCRuAOoOkjw0Wz9a+oZeV1a/GvprxWYljq68elga 0QY3ucA11jntWKpImwCRV+KH0/6idN+reZh35+Di2022MOJlV3PNjQHAOsbS930muXGfWrH6 Dg51nTuk49zH4zy2+66wukj8yqs/mf8ACOVEdb6jXg0YFFzsfHx3G0ColpdYTu9a17fc9/7i H1HqOT1LJ+15UOyHNa2ywCN5aNvqPH+k2/SUUMUhkMjImJ6X/iptqpJJKZD1X+Lf/wAUTf6h SS/xb/8Aiib/AFCkoP8AwR/gp6P/1tT63/VDrHWOsPysVjRUGhoLjysT/wAbf6xfus+9eYpK 9j9/gjw8NVot0fTv/G3+sX7rPvS/8bf6xfus+9eYpJ39I/qq0fTv/G3+sX7rPvS/8bf6xfus +9eYpJf0j+qrR9O/8bf6xfus+9Ss/wAXf1mtINm1+1oY3c6YaPosb/JXl6SX9I/qq0fULP8A F39ZrX77S17yAC5zpMAbW6lR/wDG3+sX7rPvXmKSX9I/qK0fTv8Axt/rF+6z70v/ABt/rF+6 z715ikl/SP6qtH07/wAbf6xfus+9L/xt/rF+6z715ikl/SP6qtH2n6ofVDrHR+sMyspjTUWl pLTwkvFklF+t979Hj4fpSdKf/9k= --------------CEE33E5E78D696CB4E0EC941-- --------------070C33C436192682FC31B74B-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 8:32:23 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 08:32:19 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id E1A1D37B400 for ; Wed, 13 Dec 2000 08:32:18 -0800 (PST) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id JAA12003 for ; Wed, 13 Dec 2000 09:28:46 -0700 (MST) Received: from 208-48-172-195.nas-2.scf.primenet.com(208.48.172.195), claiming to be "max" via SMTP by smtp05.primenet.com, id smtpdAAAXSaaAx; Wed Dec 13 09:28:41 2000 Reply-To: From: "Steve Shoecraft" To: Subject: RE: Accessing the Video Bios on a PCI card?? (vm_map ?) Date: Wed, 13 Dec 2000 09:34:12 -0700 Message-ID: <000201c06522$872f6ea0$c3ac30d0@max.home.org> 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 In-reply-to: <200012130145.eBD1j9306069@mass.osd.bsdi.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I never did get that to work last night. Any maps outside of the memory range on the machine (which only has 128 meg) turned up all 1s in all bits. I dropped the issue for the moment and looked at AGP ... I'm currently doing DMA transfers, but it's an AGP card, and I'm wondering a) how to detect AGP (how does the AGP register differ on PCI cards as opposed to AGP cards -- read as 0L?) and b) once detected, how to use AGP to improve capture performance. Not much progress was made -- still on the learning curve (looked alot at the agp* stuff in the /sys/pci dir). Back to the BIOS_BASE subject, I fired off a message to ATI developer support about it. And yes, suprisingly enough they _HAVE_ been very helpfull in the past about information on this card (I got the full register set refrence and the programmers manual and sample code from them). We'll see what they say. In the meantime, if you can think of anything else that might work (mapping BIOS), lemme know. - Steve -----Original Message----- From: Mike Smith [mailto:msmith@freebsd.org] Sent: Tuesday, December 12, 2000 6:45 PM To: sshoecraft@1-link.net Subject: Re: Accessing the Video Bios on a PCI card?? (vm_map ?) > > (this is a winblows system with my work-related email on it - you expect > sane wrapping?) It *is* possible, actually. 8) > Anyway ... I got the size of the bios using the method you suggested. I > used malloc to get a chunk of memory, turned the ptr into a physical addr, > then used free to get rid of it. I then used pmap_mapdev to map the phsy to > virt. That won't work. The physical pointer you referenced there is still backed by physical pages (since they were the pages allocated to you!). > You suggested using the resource manager to find a block ... how do I go > about doing that? I've tried bus_alloc_resource with the MEMORY type, but > it always fails... Any hints? For now, try just using 0x80000000. Unless you have > 2GB of RAM, that should work fine. (ie. stuff 0x80000001 into the bios base address register). When you've got it working doing this, I'll work out how to get you a better number. 8) > Oh, and yes, the card is my primary adapter. I just want my driver to > work even if the card is not the primary adapter. Ok. It doesn't matter, since expansion ROMs are never executed in-place, they're always shadowed. -- ... 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 Dec 13 10: 5:18 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 10:05:15 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from riot.yi.org (200-191-39-68-as.acessonet.com.br [200.191.39.68]) by hub.freebsd.org (Postfix) with ESMTP id D97B337B400 for ; Wed, 13 Dec 2000 10:05:11 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by riot.yi.org (8.11.0/8.10.2) with ESMTP id eBDI03m00440 for ; Wed, 13 Dec 2000 16:00:04 -0200 Date: Wed, 13 Dec 2000 16:00:03 -0200 (BRST) From: "Giovanni P. Tirloni" X-Sender: riot@riot.yi.org To: hackers@freebsd.org Subject: PPP failures in 4.2-STABLE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, After updating to 4.2-STABLE (previous version was 4.1.1-RELEASE) I'm having some strange problem with ppp. When I try to connect for the first time to an ISP the following occurs: ppp[177]: tun0: Chat: Send: ATDT22334455^M ppp[177]: tun0: Chat: Expect(120): CONNECT ppp[177]: tun0: Chat: Received: ATDT22334455^M^M ppp[177]: tun0: Chat: Received: +FHS:11^M ppp[177]: tun0: Chat: Received: ^M ppp[177]: tun0: Chat: Received: OK^M ppp[177]: tun0: Chat: Parent notified of failure (I press ^c here because nothing happens) Then, I try again and it works fine, but If the time between the first and the second connection is too long I receive the same error again, so I can't wait too much to do the second try. Another error that I got these days is the following (a bit like the previous one but with something more): ppp[315]: tun0: Chat: Send: ATDT22335040^M ppp[315]: tun0: Chat: Expect(120): CONNECT ppp[315]: tun0: Chat: Received: ATDT22335040^M^M ppp[315]: tun0: Chat: Received: +FCO^M ppp[315]: tun0: Chat: Received: ^M ppp[315]: tun0: Chat: Received: +FHS:11^M ppp[315]: tun0: Chat: Received: ^M ppp[315]: tun0: Chat: Received: OK^M ppp[315]: tun0: Chat: Parent notified of failure (I press ^C here because nothing happens) When dialing to this particular ISP other strange thing happens, cause even if I try for the second time (without spending too much time bet- ween the two tries) ppp aborts the operation: ppp[325]: tun0: Chat: Send: ATDT22335040^M ppp[325]: tun0: Chat: Expect(120): CONNECT ppp[325]: tun0: Chat: Received: ATDT22335040^M^M ppp[325]: tun0: Chat: Received: CONNECT 50666/ARQ/V90/LAPM/V42BIS^M ppp[325]: tun0: Chat: Parent notified of failure (I didn't press ^C this time) The relevant parts of my ppp.conf follows: # ppp.conf default: set log command chat tun connect set device /dev/cuaa1 set speed 115200 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 15 \"\" AT OK-AT-OK ATE1Q0 OK isp1: set redial 1 50 set phone 22334455 set authname isp1-user set authkey isp1-pass set timeout 80 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR isp2: set phone 22335040 set authname isp2-user set authkey isp2-pass set timeout 100 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR # EOF My modem is a internal USRobotics 56k (x2/v90) and as additional information this doesn't happen in Linux (2.2.17). If this isn't the correct mailing list forgive me please (perhaps -stable would be the one, but anyway). Thanks in advance, Giovanni P. Tirloni mail: riot@techie.com mail: tirloni@twu.net fone: +55 44 225 6267 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 10:20:48 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 10:20:43 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.wmptl.com (mail2.wmptl.com [216.94.6.26]) by hub.freebsd.org (Postfix) with ESMTP id 09B1737B400; Wed, 13 Dec 2000 10:20:42 -0800 (PST) Received: from wmptl.com ([10.0.0.168]) by mail2.wmptl.com (8.9.3/8.9.3) with ESMTP id NAA36767; Wed, 13 Dec 2000 13:39:05 -0500 (EST) (envelope-from webmaster@wmptl.com) Message-ID: <3A37BD57.2053CF1C@wmptl.com> Date: Wed, 13 Dec 2000 13:17:59 -0500 From: Nathan Vidican Reply-To: webmaster@wmptl.com X-Mailer: Mozilla 4.72 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: questions@freebsd.org, hackers@freebsd.org Subject: changing the way mail spools are permissioned (for using web-based email service) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm currently messing around with neomail, and it seems to do everything I need it to, but it doesn't read the mail spools properly. It needs to establish a write lock on /var/mail/. I currently have the script set to run suid/sgid 'mail', but all the spools are set to user:logingroup for ownership. Since some users have different login groups than others; this convention leaves me with two possible options, (as I see it anyhow -suggestions welcomed): 1 - change neomail too be run as suid root, which leaves me sceptical as to it's security; should something screw up I could have a big problem on my hands. 2 - (prefered), change sendmail to have all the mail spools as group writeable for the group 'mail'. This is the way I'd prefer to do things, but I have little to no clue as to exactly how to accomplish this. Seeing as how the machine this is being done on is in production, and under constant use; downtime is also an issue; (If I change it, and something else don't work...I better have it back the way it was, and quickly so). Any comments, suggestions, or otherwise would be greatly appreciated. For the record, my system information is as follows: Running: FreeBSD 4.1-20000729-STABLE (no, I don't want to cvsup/update the machine...it works fine now, and that would cause downtime) Sendmail version: ESMTP Sendmail 8.9.3/8.9.3; Wed, 13 Dec 2000 13:38:08 -0500 (EST) -- Nathan Vidican webmaster@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 10:28: 6 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 10:28:02 2000 Return-Path: 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 58EA137B400; Wed, 13 Dec 2000 10:28:02 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eBDIQaX84247; Wed, 13 Dec 2000 10:26:36 -0800 (PST) (envelope-from dillon) Date: Wed, 13 Dec 2000 10:26:36 -0800 (PST) From: Matt Dillon Message-Id: <200012131826.eBDIQaX84247@earth.backplane.com> To: News Account Cc: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Patches available (was Re: Extreme high load with 12/7 4-releng) References: <200012120230.SAA32402@pathlink.net> <200012121801.KAA42878@pathlink.net> <200012122138.NAA69074@pathlink.net> <200012122231.eBCMVE353411@earth.backplane.com> <200012130209.eBD290M79194@earth.backplane.com> <200012130621.eBD6LPa80568@earth.backplane.com> <200012131405.eBDE50G03431@crotchety.newsbastards.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> I have made a patchset available for both -current and -stable on my site: :> http://apollo.backplane.com/FreeBSD4/ :> sysctl -w vm.debug_pageout_stats=1 :> The debugging code prints a line to dmesg and /var/log/messages each :> time the pageout daemon runs a scan, and tells you how many clean pages, :[...] :> This output would be invaluable to me coming from people who still have :> major performance problems on heavily loaded machines. :> :> I would appreciate wide testing, especially by anyone running heavily :> loaded -stable boxes. I am especially interested in how this patchset :> performs on news boxes. : :Okay, I'm gathering data as we speak, but, would you still want to see :this data from a news box, if I had *not* been noticing major performance :problems, just to have some numbers to drool over? : :Regardless, I'll keep running the patchset on this lightly-loaded news :box (-stable) which seems to be pretty responsive... : :thanks! :barry bouwsma, lame-duck newsmangler at tele danmark internet Well, sure! Ego-stuffing is what we programmers live for :-) What I would be most interested in on your particular system is how this patchset performs with your madvise() hack removed and comparing that with your original numbers (prior to when you add the madvise()). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 10:31:33 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 10:31:31 2000 Return-Path: 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 2216F37B400 for ; Wed, 13 Dec 2000 10:31:29 -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 LAA05769 for ; Wed, 13 Dec 2000 11:31:04 -0700 Received: from 172.30.41.146 by mei00wssout01.micron.com with ESMTP ( WorldSecure Server SMTP Relay(WSS) v4.5); Wed, 13 Dec 2000 11:31:05 -0700 X-Server-Uuid: 6b1d535a-5b27-11d3-bf09-00902786a6a3 Received: by imcout1.micronpc.com with Internet Mail Service ( 5.5.2650.21) id ; Wed, 13 Dec 2000 11:31:05 -0700 Message-ID: <8D18712B2604D411A6BB009027F644980DD7DA@0SEA01EXSRV1> From: "Matt Simerson" To: "'freebsd-hackers@freebsd.org'" Subject: RE: hardware Dell or BSDi Date: Wed, 13 Dec 2000 11:30:59 -0700 X-Mailer: Internet Mail Service (5.5.2650.21) MIME-Version: 1.0 X-WSS-ID: 16291FE336328-01-01 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We've got a couple BSDI machines in our lab in addition to Micron's, HP's, and some black boxes we build ourselves. The BSDI box is by far the most economical (as far as buying rackmount) and perform as well as anything else. They are also using good "standard" parts which means you can find replacement components at CompUSA, Fryes, or wherever. The BSDI boxes are made by Telenet systems, a most respected hardware company (in many unix circles) who was recently purchase by BSDI. I'm pleased to say that even after the purchase they still make mighty fine servers. Matt > On Wed, 13 Dec 2000, you wrote: > > Hello all, > > > > We are going to buy our first 1U 19" rack server > (pizzacarton size), and > > probably there will be more in the future, they have to run FreeBSD > > 4.1-stable. > > > > Normally we buy all our hardware at Dell, they also have > this kind of > > servers, for instance the PowerApp Web 100, we have also > seen this kind of > > servers form BSDi.com, they have FreeBSD preinstalled, and > say they are > > completely optimized. But they are considerably more expensive. > > > > Can anyone tell me more about both these servers, how good > is the BSDi > > machine (and the organization), does FreeBSD install on the > Dell and so on? > > > > tia > > Jeroen Heijungs > > Het Muziektheater > > Amsterdam, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 10:32: 7 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 10:32:03 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 820BE37B402 for ; Wed, 13 Dec 2000 10:32:02 -0800 (PST) Received: (qmail 64114 invoked from network); 13 Dec 2000 18:29:51 -0000 Received: from unknown (HELO telehouse.ch) ([195.134.128.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 13 Dec 2000 18:29:51 -0000 Message-ID: <3A37C07A.8950B7CF@telehouse.ch> Date: Wed, 13 Dec 2000 19:31:22 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Cc: stable@freebsd.org Subject: su root hangs when logged in via SSH Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a strange problem on two of my FreeBSD machines (4.1R and 4.2-STABLE 20001207). Whenever I try to su to root it (su) just hangs and does not execute the login. Also when supplying the wrong password after emitting the message it will just hang and I have to kill it with ^C. Su'ing to another normal user works. Also su'ing to root works when logged in via telnet. On -current all this works fine. Does this ring any bells? -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 10:57: 0 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 10:56:58 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail.cruzio.com (mail.cruzio.com [165.227.128.37]) by hub.freebsd.org (Postfix) with ESMTP id 2DCA337B400; Wed, 13 Dec 2000 10:56:58 -0800 (PST) Received: from cruzio.com (bruce@sa-165-227-129-78.cruzio.com [165.227.129.78]) by mail.cruzio.com with ESMTP id KAA08827; Wed, 13 Dec 2000 10:56:54 -0800 (PST) Sender: bruce@mail.cruzio.com Message-ID: <3A37C68F.15FB8658@cruzio.com> Date: Wed, 13 Dec 2000 10:57:19 -0800 From: Bruce Korb Organization: Home X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.16 i586) X-Accept-Language: en MIME-Version: 1.0 To: obrien@FreeBSD.org Cc: bkorb@cruzio.com, GCC Development , freebsd-hackers@FreeBSD.org Subject: Re: question about "fixed" headers on FreeBSD References: <20001213012314.A75122@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > Hi Bruce, > > Can you explain why fixinc needs to do this change of stdlib.h? > > Also why GCC needs to install its own version of assert.h? > What is wrong with the base one? Obviously, nothing is really wrong with any of these files. The real question is, "Why is fixincl fixing files that ain't broke?" Fundamentally, the problem is is that the header files, as a whole, are a joint domain of the compiler and the OS. Some compiler vendors solve the problem by shipping their own headers for every approved target system. That was deemed inconvenient for GCC. Systems vendors ship headers that play well with their own compiler. GCC isn't a system vendor, either. So, GCC fixes the native headers so that it can do its job and it can emit code that talks to the local OS. This does not answer your question, but it sets the stage and it explains why it is appropriate for GCC to diddle with headers that are used for its own purposes. In the open source OS environment, the headers are generally properly formed. For one thing, they uniformly use GCC as the system compiler, so there is extra incentive to make the headers GCC-friendly. But that is only "generally" true. Buggy headers *have* been released. Furthermore, what were not bugs before have become bugs now, and what are not now bugs may become so in the future. So, GCC cannot blindly rely on correct headers, even for open source OSes. But why fix it if it is not broken? Because fixincludes could not tell that it was not broken. Fixincludes is a compromise between total processing time for all users, wasted disk space and available programmer time for putting smarts into it. It is pretty much restricted to regular expression pattern processing, but you are more than welcome to write additional methods. They will plug into the system fairly seamlessly. See "fixfixes.c", "fixtests.c" and "README" in the gcc/fixinc directory for more information. So, if you want fixincludes to stop fixing unbroken headers, *please* feel free and even encouraged to submit patches. Thank you. Regards, Bruce P.S. Does anyone think we can hack this into an appropriate FAQ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 12: 6:29 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 12:06:27 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (mail.dobox.com [208.187.122.44]) by hub.freebsd.org (Postfix) with ESMTP id 3553137B400 for ; Wed, 13 Dec 2000 12:06:27 -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 146IEA-0000N7-00; Wed, 13 Dec 2000 13:10:14 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A37D7A5.2A3F5360@softweyr.com> Date: Wed, 13 Dec 2000 13:10:13 -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: heckfordj@psi-domain.co.uk Cc: freebsd-hackers@freebsd.org Subject: Re: hardware Dell or BSDi References: <200012130749.IAA08219@mail.hmth.nl> <00121309232802.00233@freefire.psi-domain.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jamie Heckford wrote: > > http://www.psi-domain.co.uk/ > > alot cheaper and better. Quoting from the web page: Router - The freePath The freePath is suited for high performance routing and can additionally be deployed as either a firewall or proxy server. ... Based on the rock solid FreeBSD, these units are hard to match for price and performance. While I don't doubt it, this seems an interesting viewpoint for the "Innovative Linux Solutions" company. Your prices do seem reasonable, I must say. > On Wed, 13 Dec 2000, you wrote: > > Hello all, > > > > We are going to buy our first 1U 19" rack server (pizzacarton size), and > > probably there will be more in the future, they have to run FreeBSD > > 4.1-stable. > > > > Normally we buy all our hardware at Dell, they also have this kind of > > servers, for instance the PowerApp Web 100, we have also seen this kind of > > servers form BSDi.com, they have FreeBSD preinstalled, and say they are > > completely optimized. But they are considerably more expensive. > > > > Can anyone tell me more about both these servers, how good is the BSDi > > machine (and the organization), does FreeBSD install on the Dell and so on? We have recently purchased an iXtreme 1210 running OpenBSD and it has been entirely acceptable. We purchased it to server as a DNS server and it seems completely up to the job, though we haven't fed it much of a load yet. At $1327, the price is definitely on the low end for 1U servers. -- "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 Dec 13 12:30:26 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 12:29:52 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.rdc3.on.home.com (mail2.rdc3.on.home.com [24.2.9.41]) by hub.freebsd.org (Postfix) with ESMTP id CEF9037B400; Wed, 13 Dec 2000 12:28:45 -0800 (PST) Received: from host ([24.43.249.103]) by mail2.rdc3.on.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20001213202841.OLWG26458.mail2.rdc3.on.home.com@host>; Wed, 13 Dec 2000 12:28:41 -0800 Message-ID: <001501c0654b$75146f80$67f92b18@address.com> Reply-To: "Jim Gunn" From: "Jim Gunn" To: Subject: professional art community Date: Wed, 13 Dec 2000 15:26:06 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0012_01C06519.0DCCFEA0" 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 This is a multi-part message in MIME format. ------=_NextPart_000_0012_01C06519.0DCCFEA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Chalky Chalk WELCOMES YOU: This is not Spam. If you are not a part of the picture framing or art = industry this was not intended for you and we have no us for your = interest what so ever. To unsubscribe see bottom *************************************************************************= * News service for the professional art community. This information will = keep you up-to-date=20 On the latest trends and events in the industry! = *************************************************************************= * NEW SHOWCASES THIS WEEK *************************************************************************= * Finding a winner. The true winner is the art print investment that you = enjoy.=20 Time will gain the value and the value is higher with less time spent. http://www.geocities.com/chalkychalkpub5/chalkychalkpub5.htm The framing industry is picking up. Many galleries have Communicated an increase in custom framing. *************************************************************************= * Cash on the wall. Learn how anyone can invest in art and make it pay = off. How collector's buy up prints and sell.=20 www.chalkychalk.com *************************************************************************= * Sell/Trade/Buy *************************************************************************= * Potapoff SNOWED IN=20 *************************************************************************= * http://www.geocities.com/chalkychalkpub3/chalkychalkpub3.htm *************************************************************************= * LINDA HOBLEY OCTOBER FLAMES *************************************************************************= * http://www.geocities.com/chalkychalkpub2/chalkychalkpub2.htm *************************************************************************= * ANDREW KISS THE BANDIT *************************************************************************= * http://www.geocities.com/chalkychalkpub4/chalkychalkpub4.htm *************************************************************************= * LIZ MITTEN RYAN REFLECTION *************************************************************************= * http://www.geocities.com/chalkychalkpub5/chalkychalkpub5.htm *************************************************************************= * CHRIS NEWBOLD SERENITY *************************************************************************= * http://www.geocities.com/chalkychalkpub/chalkychalkpub.htm *************************************************************************= * Framing equipment. *************************************************************************= * http://www.larsonjuhl.com http://www.knoell.com http://www.clearmountcorp.com=20 http://www.speed-mat.com *************************************************************************= * Moulding, mats & supplies *************************************************************************= * http://www.pictureframes.com http://www.imageperfectglass.com http://www.crescentcardboard.com http://www.fotiou.com http://www.mtsframes.com=20 http://www.gulloinc.com=20 http://www.oxfordpictureframe.com http://www.rustic-creations.com *************************************************************************= * Art links to resources. *************************************************************************= * www.chalkychalk.com http://www.artaffairs.com http://www.dragonflyproductionsinc.com http://www.hop.ca http://www. bevellededge. com http://www.torontoimageworks.com *************************************************************************= * *************************************************************************= * The Riddle of the day=20 What am I? 1.. Everyone has me. 2.. You will all lose me. 3.. Some see me as substantial & other see me meaningless. 4.. I have never been understood and may never be understood=20 5.. Without me is to be without you and without me is to be without. 6.. I will be the one reason that grants you the possibility to salve = this riddle. 7.. Without me this riddle could never be written. To find out the answer to what am I? Look to:=20 www.chalkychalk.com *************************************************************************= * TO UNSUBSCRIBE FROM ART -NEWS, SIMPLY e-mail:=20 chalkychalk@bizland.com AND WRITE - STOP-in the subject line. This is not Spam. If you are not a part of the picture framing or art = industry this was not intended for you and we have no us for your = interest what so ever. ------=_NextPart_000_0012_01C06519.0DCCFEA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Chalky Chalk WELCOMES=20 YOU:

This is not Spam. If you are not a part of the picture framing or art = industry this was not intended for you and we have no us for your = interest what=20 so ever.

To unsubscribe see bottom


****************************************************************= **********
News=20 service for the professional art community. This information will keep = you=20 up-to-date

On the latest trends and events in the industry!=20 *************************************************************************= *

NEW SHOWCASES THIS=20 WEEK
*********************************************************= *****************
Finding=20 a winner. The true winner is the art print investment that you enjoy. =

Time will gain the value and the value is higher with less time = spent.


http://www.geocities.com/chalkychalkpub5/chalkychalkpub5.= htm

The framing industry is picking up. Many galleries have

Communicated an increase in custom framing.

**********************************************************************= ****
Cash=20 on the wall. Learn how anyone can invest in art and make it pay off. How = collector’s buy up prints and sell.


www.chalkychalk.com


****************************************************************= **********

Sell/Trade/Buy

**********************************************************************= ****

Potapoff SNOWED IN

**********************************************************************= ****
http://www.geocities.com/chalkychalkpub3/chalkychalkpub3.= htm

***********************************************= ***************************
LINDA=20 HOBLEY OCTOBER FLAMES

**********************************************************************= ****

http://www.geocities.com/chalkychalkpub2/chalkychalkpub2.htm

**********************************************************************= ****

ANDREW KISS THE BANDIT

**********************************************************************= ****

http://www.geocities.com/chalkychalkpub4/chalkychalkpub4.htm

**********************************************************************= ****

LIZ MITTEN RYAN REFLECTION

**********************************************************************= ****

http://www.geocities.com/chalkychalkpub5/chalkychalkpub5.htm

 

**********************************************************************= ****

CHRIS NEWBOLD=20 SERENITY
*************************************************************= *************

http://www.geocities.com/chalkychalkpub/chalkychalkpub.htm

**********************************************************************= ****

Framing equipment.

**********************************************************************= ****

http://www.larsonjuhl.com

http://www.knoell.com

http://www.clearmountcorp.com =

http://www.speed-mat.com

 

**********************************************************************= ****

Moulding, mats & supplies

**********************************************************************= ****

http://www.pictureframes.com

http://www.imageperfectglass.com

http://www.crescentcardboard.com

http://www.fotiou.com

http://www.mtsframes.com

http://www.gulloinc.com

http://www.oxfordpictureframe.com

http://www.rustic-creations.com

 

**********************************************************************= ****

Art links to resources.

**********************************************************************= ****

www.chalkychalk.com

http://www.artaffairs.com

http://www.dragonflyproductionsinc.com

http://www.hop.ca

http://www. = bevellededge.=20 com

http://www.torontoimageworks.com

 

**********************************************************************= ****

**********************************************************************= ****

The Riddle of the day

What am I?
  1. Everyone has me.
  2. You will all lose me.
  3. Some see me as substantial & other see me meaningless.
  4. I have never been understood and may never be understood
  5. Without me is to be without you and without me is to be = without.
  6. I will be the one reason that grants you the possibility to salve = this=20 riddle.
  7. Without me this riddle could never be written.

To find out the answer to what am I? Look to:

www.chalkychalk.com

**********************************************************************= ****

 

 

 

 

 

TO UNSUBSCRIBE FROM ART -NEWS, SIMPLY e-mail:

chalkychalk@bizland.com

AND WRITE – STOP-in the subject line.
This is not Spam. If = you are not a=20 part of the picture framing or art industry this was not intended for = you and we=20 have no us for your interest what so=20 ever.

------=_NextPart_000_0012_01C06519.0DCCFEA0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 12:47:51 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 12:47:47 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id B94CB37B400; Wed, 13 Dec 2000 12:47:46 -0800 (PST) Received: from simoeon.sentex.net (simeon.sentex.ca [209.112.4.47]) by smtp1.sentex.ca (8.11.1/8.11.1) with ESMTP id eBDKlgh06036; Wed, 13 Dec 2000 15:47:43 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.0.1.4.1.20001213153948.01fc9df0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.1 Date: Wed, 13 Dec 2000 15:41:18 -0500 To: Andre Oppermann , hackers@FreeBSD.ORG From: Mike Tancsa Subject: Re: su root hangs when logged in via SSH Cc: stable@FreeBSD.ORG In-Reply-To: <3A37C07A.8950B7CF@telehouse.ch> 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 Yeah, I had a similar problem to this in the past where syslogd was kind of hung, and the su was blocking waiting for I guess syslog to return. If you can login as root on the console, kill syslogd, restart it and see if su works once again. ---Mike At 07:31 PM 12/13/00 +0100, Andre Oppermann wrote: >I've got a strange problem on two of my FreeBSD machines (4.1R and >4.2-STABLE 20001207). > >Whenever I try to su to root it (su) just hangs and does not execute >the login. Also when supplying the wrong password after emitting the >message it will just hang and I have to kill it with ^C. > >Su'ing to another normal user works. Also su'ing to root works when >logged in via telnet. > >On -current all this works fine. > >Does this ring any bells? > >-- >Andre > > >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 Dec 13 13: 4: 4 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 13:04:01 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from crotchety.newsbastards.org (netcop.newsbastards.org [193.162.153.124]) by hub.freebsd.org (Postfix) with ESMTP id AF4C037B698 for ; Wed, 13 Dec 2000 13:04:00 -0800 (PST) Received: (from news@localhost) by crotchety.newsbastards.org (8.11.1/8.11.1) id eBDL3lw45492; Wed, 13 Dec 2000 22:03:47 +0100 (CET) (envelope-from newsmoover@free-pr0n.netscum.dk) Date: Wed, 13 Dec 2000 22:03:47 +0100 (CET) Message-Id: <200012132103.eBDL3lw45492@crotchety.newsbastards.org> X-Authentication-Warning: crotchety.newsbastards.org: news set sender to newsmoover@free-pr0n.netscum.dk using -f Reply-To: freebsd-hacker@netscum.dk To: Matt Dillon In-Reply-To: <200012131826.eBDIQaX84247@earth.backplane.com> From: News Accountant Cc: freebsd-hackers@freebsd.org Subject: Re: Patches available (was Re: Extreme high load with 12/7 4-releng) References: <200012120230.SAA32402@pathlink.net> <200012121801.KAA42878@pathlink.net> <200012122138.NAA69074@pathlink.net> <200012122231.eBCMVE353411@earth.backplane.com> <200012130209.eBD290M79194@earth.backplane.com> <200012130621.eBD6LPa80568@earth.backplane.com> <200012131405.eBDE50G03431@crotchety.newsbastards.org> <200012131826.eBDIQaX84247@earth.backplane.com> Sender: newsmoover@free-pr0n.netscum.dk Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ freebsd-stable removed from cc: list just cuz ] > :> sysctl -w vm.debug_pageout_stats=1 > :> This output would be invaluable to me coming from people who still have > :> major performance problems on heavily loaded machines. > : > :Okay, I'm gathering data as we speak, but, would you still want to see > :this data from a news box, if I had *not* been noticing major performance > > Well, sure! Ego-stuffing is what we programmers live for :-) Great, I'll gladly help you to get stuffed. Watch yer mailbox, no good point in cluttering up the list with an hour+ of logs... > What I would be most interested in on your particular system is how > this patchset performs with your madvise() hack removed and comparing > that with your original numbers (prior to when you add the madvise()). I'm going to guess that you mean the mlock() userland hack here. If so you're in luck, as I updated everything to incorporate the latest fixes to the BerkeleyDB overview method, which means that in error, I compiled the binary without the mlock() call. I caught that after a few minutes and restarted things with the binary that does mlock(), so you'll see these two sets of conditions in the logs I'll be sending. Comments are added between the two sets of stats. More details: I had been running with 02.Dec vm kernel-kode; before applying your patch I sup'ed to what was available this morning. Meaning if something broke over the last week, as the mailing list leads me to believe, I missed out on the fun. I've had to increase the size of the two history database files slightly as they were overflowing, so now they are about 135M (updated on disk) and 90M (disk timestamp never changes) in size. I still haven't researched why the larger of the two isn't acting the way I want (its on-disk updates cause noticeable lags in responsiveness, in spite of the mlock() call and other calls succeeding, and the timestamps on this file stabilize on a different transit-only machine, although on a smaller file)... I haven't made any attempts as were suggested to run helper programs to lock both files' data in memory rather than use the mlock() userland hack, yet. Mostly I've just ignored the machine since it went down last weekend. It's presently in the process of catching up since Saturday. When this is complete and it's operating normally, I'll try reverting things to closer to the default INN source k0dez. As a reminder, the changes I've made have been to... * first, enable mmap() MAP_NOSYNC on both database .index/.hash files * secondly, adding madvise() WILL_NEED for the two files, in addition to the program-supplied RANDOM * finally, cheating by enabling userland mlock() for INN only on these. There's pretty heavy disk activity on the overview BerkeleyDB database as well, and if for some reason you want more than the 1+ hour of debug numbers I'll be sending you from startup, until I start messing around with mmap/mlock/madvise options, I'll be happy to send them too. 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 Wed Dec 13 13:16:41 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 13:16:35 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id CD7C937B698 for ; Wed, 13 Dec 2000 13:16:34 -0800 (PST) Received: (qmail 67824 invoked from network); 13 Dec 2000 21:14:23 -0000 Received: from unknown (HELO telehouse.ch) ([195.134.128.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 13 Dec 2000 21:14:23 -0000 Message-ID: <3A37E70C.3A935224@telehouse.ch> Date: Wed, 13 Dec 2000 22:15:56 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Tancsa Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: su root hangs when logged in via SSH References: <5.0.1.4.1.20001213153948.01fc9df0@marble.sentex.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Tancsa wrote: > > Yeah, I had a similar problem to this in the past where syslogd was kind of > hung, and the su was blocking waiting for I guess syslog to return. If you > can login as root on the console, kill syslogd, restart it and see if su > works once again. Nope, it does not work again. But after a couple of seconds after restarting syslogd I've got this messages on the console: "syslogd: timed out waiting for child" Another note, syslogd does not go with a normal kill, it needs a kill -9 to make it into heaven. Could this be related to having a serial console? -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 13:30:28 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 13:30:25 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id 2C68F37B699 for ; Wed, 13 Dec 2000 13:30:20 -0800 (PST) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id QAA12440 for ; Wed, 13 Dec 2000 16:25:46 -0500 Date: Wed, 13 Dec 2000 16:25:46 -0500 (EST) From: Marc Tardif To: freebsd-hackers@freebsd.org Subject: syscall assembly 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 Considering the following C code: #include int main() { open("file", O_RDONLY); return 0; } compiled with gcc -S -O2, the following assembly code is generated: main: pushl %ebp movl %esp,%ebp subl $8,%esp addl $-8,%esp pushl $0 pushl $.LC0 call open xorl %eax,%eax leave What is the purpose of the subl and addl instructions? On Linux, they are simply unexistent.. Notes: FreeBSD fbsd.b0x.com 4.2-RELEASE gcc version 2.95.2 19991024 (release) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 13:44:53 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 13:44:46 2000 Return-Path: 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 091A337B6CA for ; Wed, 13 Dec 2000 13:44:43 -0800 (PST) Received: from fanf by hand.dotat.at with local (Exim 3.15 #3) id 146Jgy-0006aF-00; Wed, 13 Dec 2000 21:44:04 +0000 Date: Wed, 13 Dec 2000 21:44:04 +0000 From: Tony Finch To: Dag-Erling Smorgrav Cc: Gustavo Vieira Goncalves Coelho Rios , hackers@FreeBSD.ORG Subject: Re: very big mail spool directory Message-ID: <20001213214404.P71002@hand.dotat.at> References: <3A368F8C.1918684F@ifour.com.br> 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: fanf@dotat.at Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > >If you only have half a million users, pick a prime number K close to >the square root of the expected number of users (724 in your case - >closest primes are 719 and 727), create that many bucket directories, >and place each user in bucket ID mod K. Why a prime number? All you need is an even spread, and given that user IDs are usually allocated sequentially any modulus will do. Tony. -- f.a.n.finch fanf@covalent.net dot@dotat.at "Plan 9 deals with the resurrection of the dead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 13:53:59 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 13:53:56 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 53B2237B6A0; Wed, 13 Dec 2000 13:53:53 -0800 (PST) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.1/8.11.0) with ESMTP id eBDLrn576602; Wed, 13 Dec 2000 16:53:49 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200012132153.eBDLrn576602@whizzo.transsys.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andre Oppermann Cc: Mike Tancsa , hackers@FreeBSD.ORG, stable@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: su root hangs when logged in via SSH References: <5.0.1.4.1.20001213153948.01fc9df0@marble.sentex.ca> <3A37E70C.3A935224@telehouse.ch> In-reply-to: Your message of "Wed, 13 Dec 2000 22:15:56 +0100." <3A37E70C.3A935224@telehouse.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Dec 2000 16:53:49 -0500 Sender: louie@TransSys.COM Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Tancsa wrote: > > > > Yeah, I had a similar problem to this in the past where syslogd was kind of > > hung, and the su was blocking waiting for I guess syslog to return. If you > > can login as root on the console, kill syslogd, restart it and see if su > > works once again. > > Nope, it does not work again. But after a couple of seconds after > restarting syslogd I've got this messages on the console: > "syslogd: timed out waiting for child" > > Another note, syslogd does not go with a normal kill, it needs a kill -9 > to make it into heaven. > > Could this be related to having a serial console? This sounds very familiar to me. I had a problem like this in the past, and it was a case of syslog blocking trying to write to /dev/console and blocking. The comconsole port starts a getty on /dev/console, which might be surprising if you also had one running on ttyd0. I don't recall the details, but I think that the serial console is definately related to your problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 14:10:29 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 14:10:27 2000 Return-Path: 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 1629637B698 for ; Wed, 13 Dec 2000 14:10:27 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eBDMANR04634; Wed, 13 Dec 2000 14:10:23 -0800 (PST) Date: Wed, 13 Dec 2000 14:10:23 -0800 From: Alfred Perlstein To: Marc Tardif Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: syscall assembly Message-ID: <20001213141023.O16205@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 intmktg@CAM.ORG on Wed, Dec 13, 2000 at 04:25:46PM -0500 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Marc Tardif [001213 13:30] wrote: > Considering the following C code: > > #include > int main() { > open("file", O_RDONLY); > return 0; > } > > compiled with gcc -S -O2, the following > assembly code is generated: > > main: > pushl %ebp > movl %esp,%ebp > subl $8,%esp > addl $-8,%esp > pushl $0 > pushl $.LC0 > call open > xorl %eax,%eax > leave > > What is the purpose of the subl and addl > instructions? On Linux, they are simply > unexistent.. FreeBSD passes syscall args on the stack, Linux uses registers. -- -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 Dec 13 14:17:13 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 14:17:12 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id 7E4F837B402 for ; Wed, 13 Dec 2000 14:17:11 -0800 (PST) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id RAA12679; Wed, 13 Dec 2000 17:12:40 -0500 Date: Wed, 13 Dec 2000 17:12:40 -0500 (EST) From: Marc Tardif To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: syscall assembly In-Reply-To: <20001213141023.O16205@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 Wed, 13 Dec 2000, Alfred Perlstein wrote: > * Marc Tardif [001213 13:30] wrote: [ snip ] > > subl $8,%esp > > addl $-8,%esp > > pushl $0 > > pushl $.LC0 > > call open > > FreeBSD passes syscall args on the stack, Linux uses registers. > So why is %esp displaced by 16 bytes when only 8 bytes are necessary (4 for $0 and 4 for $.LC0)? And couldn't the compiler use a single instruction such as subl $16,%esp or addl $-16,%esp? Are two instructions used for pipelining purposes, where subl is synchro- nised with the first pushl and addl with the second pushl? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 14:21:49 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 14:21:47 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from chopper.Poohsticks.ORG (chopper.poohsticks.org [63.227.60.73]) by hub.freebsd.org (Postfix) with ESMTP id 6E37937B402 for ; Wed, 13 Dec 2000 14:21:46 -0800 (PST) Received: from chopper.Poohsticks.ORG (drew@localhost.poohsticks.org [127.0.0.1]) by chopper.Poohsticks.ORG (8.10.1/8.10.1) with ESMTP id eBDMLdh28943; Wed, 13 Dec 2000 15:21:39 -0700 Message-Id: <200012132221.eBDMLdh28943@chopper.Poohsticks.ORG> To: Alfred Perlstein Cc: Marc Tardif , freebsd-hackers@FreeBSD.ORG Subject: Re: syscall assembly In-reply-to: Your message of "Wed, 13 Dec 2000 14:10:23 PST." <20001213141023.O16205@fw.wintelcom.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <28939.976746099.1@chopper.Poohsticks.ORG> Date: Wed, 13 Dec 2000 15:21:39 -0700 From: Drew Eckhardt Sender: drew@chopper.Poohsticks.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001213141023.O16205@fw.wintelcom.net>, bright@wintelcom.net write s: >> subl $8,%esp >> addl $-8,%esp >> What is the purpose of the subl and addl >> instructions? On Linux, they are simply >> unexistent.. > >FreeBSD passes syscall args on the stack, Linux uses registers. The 'C' compiler doesn't know open is a syscall, and treats it like any other code. The pushls put the arguments on the stack. The subl/addl are there because your version of GCC is broken. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 14:25:49 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 14:25:46 2000 Return-Path: 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 ACB3437B402; Wed, 13 Dec 2000 14:25:46 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eBDMPeg05261; Wed, 13 Dec 2000 14:25:40 -0800 (PST) Date: Wed, 13 Dec 2000 14:25:40 -0800 From: Alfred Perlstein To: Drew Eckhardt Cc: Marc Tardif , freebsd-hackers@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: syscall assembly Message-ID: <20001213142539.R16205@fw.wintelcom.net> References: <20001213141023.O16205@fw.wintelcom.net> <200012132221.eBDMLdh28943@chopper.Poohsticks.ORG> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200012132221.eBDMLdh28943@chopper.Poohsticks.ORG>; from drew@PoohSticks.ORG on Wed, Dec 13, 2000 at 03:21:39PM -0700 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David, can you look at this? #include int foo() { open("file", O_RDONLY); return 0; } int main() { int x; x = foo(); return 0; } results in: foo: pushl %ebp movl %esp,%ebp subl $8,%esp addl $-8,%esp pushl $0 pushl $.LC0 call open xorl %eax,%eax leave ret why the subl then addl? ~ % gcc -v Using builtin specs. gcc version 2.95.2 19991024 (release) ~ % uname -a 4.2-STABLE FreeBSD 4.2-STABLE #1: Wed Dec 6 02:49:24 PST 2000 * Drew Eckhardt [001213 14:21] wrote: > In message <20001213141023.O16205@fw.wintelcom.net>, bright@wintelcom.net write > s: > >> subl $8,%esp > >> addl $-8,%esp > > >> What is the purpose of the subl and addl > >> instructions? On Linux, they are simply > >> unexistent.. > > > >FreeBSD passes syscall args on the stack, Linux uses registers. > > The 'C' compiler doesn't know open is a syscall, and treats it like > any other code. > > The pushls put the arguments on the stack. > > The subl/addl are there because your version of GCC is broken. -- -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 Dec 13 14:51:49 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 14:51:46 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from kwanon.research.canon.com.au (kwanon.research.canon.com.au [203.12.172.254]) by hub.freebsd.org (Postfix) with ESMTP id 4E83237B69B for ; Wed, 13 Dec 2000 14:51:46 -0800 (PST) Received: from bellmann.research.canon.com.au (bellmann.research.canon.com.au [10.5.0.3]) by kwanon.research.canon.com.au (Postfix) with ESMTP id 772F78A898; Wed, 13 Dec 2000 22:54:43 +0000 (UTC) Received: from elph.research.canon.com.au (elph.research.canon.com.au [203.12.174.253]) by bellmann.research.canon.com.au (Postfix) with ESMTP id 9EB928B10; Thu, 14 Dec 2000 09:41:43 +1100 (EST) Received: from blow.research.canon.com.au (blow.research.canon.com.au [10.8.1.4]) by elph.research.canon.com.au (Postfix) with ESMTP id 095583C8; Thu, 14 Dec 2000 09:51:02 +1100 (EST) Date: Thu, 14 Dec 2000 09:51:42 +1100 (EST) From: Iain Templeton To: freebsd-hackers@FreeBSD.ORG Cc: Alfred Perlstein , Drew Eckhardt , Marc Tardif Subject: Re: syscall assembly In-Reply-To: <20001213142539.R16205@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 Wed, 13 Dec 2000, Alfred Perlstein wrote: > David, can you look at this? > > #include > > int foo() { > open("file", O_RDONLY); > return 0; > } > int main() { > int x; > x = foo(); > return 0; > } > > results in: > > foo: > pushl %ebp > movl %esp,%ebp > subl $8,%esp > addl $-8,%esp > pushl $0 > pushl $.LC0 > call open > xorl %eax,%eax > leave > ret > > why the subl then addl? > Well, as a thoroughly rough guess, the subl is probably to create space on the stack for the args, and the addl is to align the stack to a 16 byte address? I know that the PowerPC ABI wants that, but no idea about x86. Iain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 15: 3:11 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 15:03:09 2000 Return-Path: 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 93EF937B404 for ; Wed, 13 Dec 2000 15:03:08 -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 eBDN37s82637; Wed, 13 Dec 2000 16:03:07 -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 QAA42413; Wed, 13 Dec 2000 16:03:03 -0700 (MST) Message-Id: <200012132303.QAA42413@harmony.village.org> To: Tony Finch Subject: Re: very big mail spool directory Cc: Dag-Erling Smorgrav , Gustavo Vieira Goncalves Coelho Rios , hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 13 Dec 2000 21:44:04 GMT." <20001213214404.P71002@hand.dotat.at> References: <20001213214404.P71002@hand.dotat.at> <3A368F8C.1918684F@ifour.com.br> Date: Wed, 13 Dec 2000 16:03:03 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001213214404.P71002@hand.dotat.at> Tony Finch writes: : Dag-Erling Smorgrav wrote: : > : >If you only have half a million users, pick a prime number K close to : >the square root of the expected number of users (724 in your case - : >closest primes are 719 and 727), create that many bucket directories, : >and place each user in bucket ID mod K. : : Why a prime number? All you need is an even spread, and given that : user IDs are usually allocated sequentially any modulus will do. Because Knuth has shown that prime numbers give the best spread in hash lookup tables. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 15: 3:19 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 15:03:14 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 5874837B699 for ; Wed, 13 Dec 2000 15:03:11 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id eBDN0mZ04448; Wed, 13 Dec 2000 23:00:48 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eBDN4LU69889; Wed, 13 Dec 2000 23:04:21 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200012132304.eBDN4LU69889@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Giovanni P. Tirloni" Cc: hackers@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: PPP failures in 4.2-STABLE In-Reply-To: Message from "Giovanni P. Tirloni" of "Wed, 13 Dec 2000 16:00:03 -0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Dec 2000 23:04:21 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The only thing that comes to mind here is that perhaps you've got something like hylafax or mgetty running against the same port and something's gone wrong with the port locking code. It *looks* like something's writing fax commands to your modem at the same time as you're trying to dial.... > Hi all, > > After updating to 4.2-STABLE (previous version was 4.1.1-RELEASE) I'm > having some strange problem with ppp. When I try to connect for the > first time to an ISP the following occurs: > > ppp[177]: tun0: Chat: Send: ATDT22334455^M > ppp[177]: tun0: Chat: Expect(120): CONNECT > ppp[177]: tun0: Chat: Received: ATDT22334455^M^M > ppp[177]: tun0: Chat: Received: +FHS:11^M > ppp[177]: tun0: Chat: Received: ^M > ppp[177]: tun0: Chat: Received: OK^M > ppp[177]: tun0: Chat: Parent notified of failure > (I press ^c here because nothing happens) > > Then, I try again and it works fine, but If the time between the first > and the second connection is too long I receive the same error again, > so I can't wait too much to do the second try. > > Another error that I got these days is the following (a bit like the > previous one but with something more): > > ppp[315]: tun0: Chat: Send: ATDT22335040^M > ppp[315]: tun0: Chat: Expect(120): CONNECT > ppp[315]: tun0: Chat: Received: ATDT22335040^M^M > ppp[315]: tun0: Chat: Received: +FCO^M > ppp[315]: tun0: Chat: Received: ^M > ppp[315]: tun0: Chat: Received: +FHS:11^M > ppp[315]: tun0: Chat: Received: ^M > ppp[315]: tun0: Chat: Received: OK^M > ppp[315]: tun0: Chat: Parent notified of failure > (I press ^C here because nothing happens) > > When dialing to this particular ISP other strange thing happens, cause > even if I try for the second time (without spending too much time bet- > ween the two tries) ppp aborts the operation: > > ppp[325]: tun0: Chat: Send: ATDT22335040^M > ppp[325]: tun0: Chat: Expect(120): CONNECT > ppp[325]: tun0: Chat: Received: ATDT22335040^M^M > ppp[325]: tun0: Chat: Received: CONNECT 50666/ARQ/V90/LAPM/V42BIS^M > ppp[325]: tun0: Chat: Parent notified of failure > (I didn't press ^C this time) > > The relevant parts of my ppp.conf follows: > > # ppp.conf > > default: > set log command chat tun connect > set device /dev/cuaa1 > set speed 115200 > set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 15 \"\" AT OK-AT-OK > ATE1Q0 OK > > isp1: > set redial 1 50 > set phone 22334455 > set authname isp1-user > set authkey isp1-pass > set timeout 80 > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 > add default HISADDR > > isp2: > set phone 22335040 > set authname isp2-user > set authkey isp2-pass > set timeout 100 > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 > add default HISADDR > > # EOF > > My modem is a internal USRobotics 56k (x2/v90) and as additional > information this doesn't happen in Linux (2.2.17). > > If this isn't the correct mailing list forgive me please (perhaps > -stable would be the one, but anyway). > > Thanks in advance, > > > Giovanni P. Tirloni > > mail: riot@techie.com > mail: tirloni@twu.net > fone: +55 44 225 6267 -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 15: 4:17 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 15:04:16 2000 Return-Path: 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 1012737B404 for ; Wed, 13 Dec 2000 15:04:15 -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 eBDN4Ds82656; Wed, 13 Dec 2000 16:04:13 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA42447; Wed, 13 Dec 2000 16:04:13 -0700 (MST) Message-Id: <200012132304.QAA42447@harmony.village.org> To: Marc Tardif Subject: Re: syscall assembly Cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 13 Dec 2000 17:12:40 EST." References: Date: Wed, 13 Dec 2000 16:04:13 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Marc Tardif writes: : So why is %esp displaced by 16 bytes when only 8 bytes : are necessary (4 for $0 and 4 for $.LC0)? And couldn't : the compiler use a single instruction such as : subl $16,%esp or addl $-16,%esp? Are two instructions : used for pipelining purposes, where subl is synchro- : nised with the first pushl and addl with the second : pushl? gcc tries to align stack to 16 byte boundaries as a speed optiminzation. Why it doesn't do this in one instruction is beyond me. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 15: 7:20 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 15:07:18 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id 75DDD37B69B for ; Wed, 13 Dec 2000 15:07:17 -0800 (PST) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id SAA12762; Wed, 13 Dec 2000 18:02:44 -0500 Date: Wed, 13 Dec 2000 18:02:44 -0500 (EST) From: Marc Tardif To: Iain Templeton Cc: freebsd-hackers@FreeBSD.ORG, Alfred Perlstein , Drew Eckhardt Subject: Re: syscall assembly In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Dec 2000, Iain Templeton wrote: > On Wed, 13 Dec 2000, Alfred Perlstein wrote: > > > subl $8,%esp > > addl $-8,%esp > > pushl $0 > > pushl $.LC0 > > call open > > > > why the subl then addl? > > > Well, as a thoroughly rough guess, the subl is probably to create space > on the stack for the args, and the addl is to align the stack to a 16 > byte address? > Perhaps, but no matter the degree of optimisation, the 16 byte of space is performed in two instructions. This leads me to believe is it most likely a pipelining issue for the following pushl instructions. As for subl'ing and addl'ing 8 bytes instead of 4, as required by each pushl, that can very well be an aligning issue which would seem to make more sense for the x86. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 15: 9:42 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 15:09:37 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id C66FC37B400 for ; Wed, 13 Dec 2000 15:09:36 -0800 (PST) Received: (qmail 69699 invoked from network); 13 Dec 2000 23:07:25 -0000 Received: from unknown (HELO telehouse.ch) ([195.134.128.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 13 Dec 2000 23:07:25 -0000 Message-ID: <3A380189.9B95A212@telehouse.ch> Date: Thu, 14 Dec 2000 00:08:57 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "Louis A. Mamakos" Cc: Mike Tancsa , hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: su root hangs when logged in via SSH References: <5.0.1.4.1.20001213153948.01fc9df0@marble.sentex.ca> <3A37E70C.3A935224@telehouse.ch> <200012132153.eBDLrn576602@whizzo.transsys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Louis A. Mamakos" wrote: > > > Mike Tancsa wrote: > > > > > > Yeah, I had a similar problem to this in the past where syslogd was kind of > > > hung, and the su was blocking waiting for I guess syslog to return. If you > > > can login as root on the console, kill syslogd, restart it and see if su > > > works once again. > > > > Nope, it does not work again. But after a couple of seconds after > > restarting syslogd I've got this messages on the console: > > "syslogd: timed out waiting for child" > > > > Another note, syslogd does not go with a normal kill, it needs a kill -9 > > to make it into heaven. > > > > Could this be related to having a serial console? > > This sounds very familiar to me. I had a problem like this in the > past, and it was a case of syslog blocking trying to write to /dev/console > and blocking. The comconsole port starts a getty on /dev/console, which > might be surprising if you also had one running on ttyd0. > > I don't recall the details, but I think that the serial console is > definately related to your problem. Yep, that seems to be the problem. As soon as I remove the getty it works. Interestingly enough syslogd doesn't matter at all, running or not it will not work as long as getty is active. Is there any work-around known? -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 15: 9:49 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 15:09:45 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from chopper.Poohsticks.ORG (chopper.poohsticks.org [63.227.60.73]) by hub.freebsd.org (Postfix) with ESMTP id 48E9837B69B for ; Wed, 13 Dec 2000 15:09:41 -0800 (PST) Received: from chopper.Poohsticks.ORG (drew@localhost.poohsticks.org [127.0.0.1]) by chopper.Poohsticks.ORG (8.10.1/8.10.1) with ESMTP id eBDN9eh29153 for ; Wed, 13 Dec 2000 16:09:40 -0700 Message-Id: <200012132309.eBDN9eh29153@chopper.Poohsticks.ORG> To: freebsd-hackers@FreeBSD.ORG Subject: Re: syscall assembly In-reply-to: Your message of "Wed, 13 Dec 2000 16:04:13 MST." <200012132304.QAA42447@harmony.village.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <29149.976748980.1@chopper.Poohsticks.ORG> Date: Wed, 13 Dec 2000 16:09:40 -0700 From: Drew Eckhardt Sender: drew@chopper.Poohsticks.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200012132304.QAA42447@harmony.village.org>, imp@village.org writes: >In message Marc Tar >dif writes: >: So why is %esp displaced by 16 bytes when only 8 bytes >: are necessary (4 for $0 and 4 for $.LC0)? And couldn't >: the compiler use a single instruction such as >: subl $16,%esp or addl $-16,%esp? Are two instructions >: used for pipelining purposes, where subl is synchro- >: nised with the first pushl and addl with the second >: pushl? > >gcc tries to align stack to 16 byte boundaries as a speed >optiminzation. Why it doesn't do this in one instruction is beyond >me. Kocking 16 bytes off the stack pointer won't put it any closer to a 16 byte boundary. -- Home Page For those who do, no explanation is necessary. For those who don't, no explanation is possible. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 15:18:50 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 15:18:48 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from chopper.Poohsticks.ORG (chopper.poohsticks.org [63.227.60.73]) by hub.freebsd.org (Postfix) with ESMTP id 3A5D737B404 for ; Wed, 13 Dec 2000 15:18:48 -0800 (PST) Received: from chopper.Poohsticks.ORG (drew@localhost.poohsticks.org [127.0.0.1]) by chopper.Poohsticks.ORG (8.10.1/8.10.1) with ESMTP id eBDNImh29194 for ; Wed, 13 Dec 2000 16:18:48 -0700 Message-Id: <200012132318.eBDNImh29194@chopper.Poohsticks.ORG> To: freebsd-hackers@FreeBSD.ORG Subject: Re: syscall assembly In-reply-to: Your message of "Wed, 13 Dec 2000 18:02:44 EST." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <29190.976749527.1@chopper.Poohsticks.ORG> Date: Wed, 13 Dec 2000 16:18:47 -0700 From: Drew Eckhardt Sender: drew@chopper.Poohsticks.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , intmktg@ CAM.ORG writes: >Perhaps, but no matter the degree of optimisation, the >16 byte of space is performed in two instructions. This >leads me to believe is it most likely a pipelining issue >for the following pushl instructions. As for subl'ing and >addl'ing 8 bytes instead of 4, as required by each pushl, >that can very well be an aligning issue which would seem >to make more sense for the x86. pushl puts the operand on the stack and then decrements %esp by an appropriate quantity. Nothing needs to be done to the stack before it. My best guess (if it isn't a bug) would be that it's there to keep the stack on a 32 byte (IIRC, this sounds like cache line size for the newer Intel chips) boundary when the program gets to open (4 for saved %ebp, 4 for the char * arg, 4 for the int arg, and 4 for the %eip call pushes requires 16 bytes more to preserve a 32 byte alignment) so that in a "normal" function without a lot of locals all of the locals are on the same cache line. Two instructions instead of 1 would help to facilitate alignment of the return address (I think 16 bytes is a good alignment for a jmp, and I can't see why a ret wouldn't the same), and a subl + addl combination would prevent interferance by a stupid peephole optimizer looking to combine addls with the same destination register. -- Home Page For those who do, no explanation is necessary. For those who don't, no explanation is possible. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 15:23:41 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 15:23:39 2000 Return-Path: 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 84BF737B404 for ; Wed, 13 Dec 2000 15:23:39 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eBDNNb588363; Wed, 13 Dec 2000 15:23:37 -0800 (PST) (envelope-from dillon) Date: Wed, 13 Dec 2000 15:23:37 -0800 (PST) From: Matt Dillon Message-Id: <200012132323.eBDNNb588363@earth.backplane.com> To: Drew Eckhardt Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: syscall assembly References: <200012132309.eBDN9eh29153@chopper.Poohsticks.ORG> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :>gcc tries to align stack to 16 byte boundaries as a speed :>optiminzation. Why it doesn't do this in one instruction is beyond :>me. : :Kocking 16 bytes off the stack pointer won't put it any closer to a :16 byte boundary. This is precisely my problem with gcc's 'optimization'. It's utterly stupid for it to assume that the stack is already 16-byte aligned... it makes it impossible to mix aligned and non-aligned code and still have a reasonably optimal result (e.g. like third party libraries or older libraries or whatever). And it's a huge, unnecessary waste of space when most of the time all you are storing on the stack are ints. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 15:43:38 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 15:43:36 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from chopper.Poohsticks.ORG (chopper.poohsticks.org [63.227.60.73]) by hub.freebsd.org (Postfix) with ESMTP id 74ED837B404 for ; Wed, 13 Dec 2000 15:43:35 -0800 (PST) Received: from chopper.Poohsticks.ORG (drew@localhost.poohsticks.org [127.0.0.1]) by chopper.Poohsticks.ORG (8.10.1/8.10.1) with ESMTP id eBDNhZh29326 for ; Wed, 13 Dec 2000 16:43:36 -0700 Message-Id: <200012132343.eBDNhZh29326@chopper.Poohsticks.ORG> To: freebsd-hackers@FreeBSD.ORG Subject: Re: syscall assembly In-reply-to: Your message of "Wed, 13 Dec 2000 16:18:47 MST." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <29322.976751015.1@chopper.Poohsticks.ORG> Date: Wed, 13 Dec 2000 16:43:35 -0700 From: Drew Eckhardt Sender: drew@chopper.Poohsticks.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG drew writes: >My best guess (if it isn't a bug) would be that it's there to keep the stack >on a 32 byte (IIRC, this sounds like cache line size for the newer >Intel chips) This discussion piqued my curiosity, so I popped up the Pentium III optomization manual. To quote it: On Pentium II and Pentium III processors, a misaligned access that crosses a cache line boundary does incure a penalty. A Data Cache Unit (DCU) split is a memory access that crosses a 32-byte line boundary. Unaligned accesses may cause a DCU split and stall Pentium II and Pentium III processors. For best performance, make sure that in data structures and arrays greater than 32 bytes, the structure or array elements are 32-byte-aligned and that access patterns to data structure and array elements do not break the alignment rules. IOW, the stack pointer adjustment is there so that doubles (and 80-bit floats, if GCC supports those. Does it do a long double for Intel targets?) in the called function don't cross a 32 byte data cache line boundary. >Two instructions instead of 1 would help to facilitate alignment of the >return address (I think 16 bytes is a good alignment for a jmp, and >I can't see why a ret wouldn't the same) PII/PIII processors prefetch on 16 byte boundaries, so having the return address on such a boundary may cut the number of prefetches and (marginally) improve performance. -- Home Page For those who do, no explanation is necessary. For those who don't, no explanation is possible. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 15:48:28 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 15:48:24 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from sheffield.cnchost.com (sheffield.concentric.net [207.155.252.12]) by hub.freebsd.org (Postfix) with ESMTP id EF53A37B404 for ; Wed, 13 Dec 2000 15:48:23 -0800 (PST) Received: from bitblocks.com (ts006d30.oak-ca.concentric.net [206.173.202.42]) by sheffield.cnchost.com id SAA09244; Wed, 13 Dec 2000 18:48:14 -0500 (EST) [ConcentricHost SMTP Relay 1.10] Message-ID: <200012132348.SAA09244@sheffield.cnchost.com> Errors-To: To: Iain Templeton Cc: freebsd-hackers@FreeBSD.ORG, Alfred Perlstein , Drew Eckhardt , Marc Tardif Subject: Re: syscall assembly In-Reply-To: Your message of "Thu, 14 Dec 2000 09:51:42 +1100." Date: Wed, 13 Dec 2000 15:48:13 -0800 From: Bakul Shah Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > #include > > > > int foo() { > > open("file", O_RDONLY); > > return 0; > > } > > int main() { > > int x; > > x = foo(); > > return 0; > > } > > > > results in: > > > > foo: > > pushl %ebp > > movl %esp,%ebp > > subl $8,%esp > > addl $-8,%esp > > pushl $0 > > pushl $.LC0 > > call open > > xorl %eax,%eax > > leave > > ret > > > > why the subl then addl? > > > Well, as a thoroughly rough guess, the subl is probably to create space > on the stack for the args, and the addl is to align the stack to a 16 > byte address? > > I know that the PowerPC ABI wants that, but no idea about x86. You guess about addl maintaining 16 byte alignment is right. The first subl is required to keep the initial alignment to 16 bytes due to the call to foo and saving of %ebp on the stack. Try compiling the following: extern g(); f1() { g(1,2); } f2() { g(1,2,3,4); } f3() { g(1,2,3,4,5); } f4() { g(1,2); g(1,2); } f2() does not have the addl since it has exactly 4 args. f3() has an addl $-12 to maintain 16 byte alignment (5 args take 20 bytes). f4() shows why the first subl is needed (assembly shown below). .p2align 2,0x90 .globl f4 .type f4,@function f4: pushl %ebp movl %esp,%ebp subl $8,%esp addl $-8,%esp ; g(1,2); pushl $2 pushl $1 call g addl $16,%esp addl $-8,%esp ; g(1,2); pushl $2 pushl $1 call g addl $16,%esp .L5: leave ret .Lfe4: .size f4,.Lfe4-f4 The intermediate addl $16 followed by addl$-8 is optimized when the -O flag is used but not the initial subl followed by addl. Probably because gcc treats proc prolog/epilog code specially (or it lacks a proper peephole optimizer). Note that the alignment boundary is 16 bytes, not 32 bytes as someone else claimed (see the code for f3()). But I don't see the point of this optimization -- it seems to want to put the return address on a 16 byte boundary but modern caches should be able to fetch any asked for word in a cache line first before filling in the rest of the cache.....[but PIII is not exactly modern:-) In fact by allocating 16 bytes per frame you are using up more cache lines (and more space). Its impact is worse when you compile with -fomit-frame-pointer to avoid saving/restoring the frame pointer. Now there is an unnecessary subl $12 and addl $12 on procedure entry and exit. [You don't need a framepointer *unless* you are debugging your code or doing alloca() so in well behaved code -fomit-frame-pointer savings can add up quite a bit] I guess one reason may be to make sure doubles and larger structs are aligned on 16 byte boundary but seems the cost of doing this likely outweighs the benefit. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 16: 8:40 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 16:08:37 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from db.wireless.net (adsl-gte-la-216-86-194-70.mminternet.com [216.86.194.70]) by hub.freebsd.org (Postfix) with ESMTP id 7D10137B699 for ; Wed, 13 Dec 2000 16:08:37 -0800 (PST) Received: from wireless.net (dbutter@dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with ESMTP id PAA25375 for ; Wed, 13 Dec 2000 15:53:48 -0800 (PST) (envelope-from dbutter@wireless.net) Sender: dbutter@db.wireless.net Message-ID: <3A380FA5.9BD9F23C@wireless.net> Date: Wed, 13 Dec 2000 16:09:09 -0800 From: Devin Butterfield X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.18pre21 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: StrongARM support? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Is there any work in progress to support running FreeBSD on ARM processors? If not, are there any plans to? I would be very interested in helping out with such an effort. I would love to have FreeBSD running on my iPAQ PocketPC. :) I know that linux is already running well on ARM but I would really like to see FreeBSD running in its place. -- Regards, Devin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 16:23:31 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 16:23:30 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mb2i0.ns.pitt.edu (mb2i0.ns.pitt.edu [136.142.186.36]) by hub.freebsd.org (Postfix) with ESMTP id 3614637B698 for ; Wed, 13 Dec 2000 16:23:30 -0800 (PST) Received: from pitt.edu ("port 1677"@[136.142.89.102]) by pitt.edu (PMDF V5.2-32 #41462) with ESMTP id <01JXO0N9BOPM003J3G@mb2i0.ns.pitt.edu> for freebsd-hackers@FreeBSD.ORG; Wed, 13 Dec 2000 19:23:22 EST Date: Wed, 13 Dec 2000 19:30:37 -0500 From: "Pedro F. Giffuni" Subject: Re: StrongARM support? To: Devin Butterfield Cc: freebsd-hackers@FreeBSD.ORG Message-id: <3A3814AD.6AE6E213@pitt.edu> Organization: University of Pittsburgh MIME-version: 1.0 X-Mailer: Mozilla 4.76 [en] (Win98; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en,pdf,es-CO References: <3A380FA5.9BD9F23C@wireless.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There was somone looking at the NetBSD code with hungry eyes but I never heard anything more... check the archives. Pedro. Devin Butterfield wrote: > > Hi all, > > Is there any work in progress to support running FreeBSD on ARM > processors? If not, are there any plans to? I would be very interested > in helping out with such an effort. I would love to have FreeBSD running > on my iPAQ PocketPC. :) > > I know that linux is already running well on ARM but I would really like > to see FreeBSD running in its place. > -- > Regards, Devin. > > 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 Dec 13 16:24:41 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 16:24:38 2000 Return-Path: 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 551D737B698 for ; Wed, 13 Dec 2000 16:24:38 -0800 (PST) Received: from fanf by hand.dotat.at with local (Exim 3.15 #3) id 146MBr-000C0K-00; Thu, 14 Dec 2000 00:24:07 +0000 Date: Thu, 14 Dec 2000 00:24:07 +0000 From: Tony Finch To: Warner Losh Cc: Dag-Erling Smorgrav , Gustavo Vieira Goncalves Coelho Rios , hackers@FreeBSD.ORG Subject: Re: very big mail spool directory Message-ID: <20001214002407.D30050@hand.dotat.at> References: <20001213214404.P71002@hand.dotat.at> <3A368F8C.1918684F@ifour.com.br> <20001213214404.P71002@hand.dotat.at> <200012132303.QAA42413@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200012132303.QAA42413@harmony.village.org> Organization: Covalent Technologies, Inc Sender: fanf@dotat.at Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: >In message <20001213214404.P71002@hand.dotat.at> Tony Finch writes: >: Dag-Erling Smorgrav wrote: >: > >: >If you only have half a million users, pick a prime number K close to >: >the square root of the expected number of users (724 in your case - >: >closest primes are 719 and 727), create that many bucket directories, >: >and place each user in bucket ID mod K. >: >: Why a prime number? All you need is an even spread, and given that >: user IDs are usually allocated sequentially any modulus will do. > >Because Knuth has shown that prime numbers give the best spread in >hash lookup tables. Yes, I know that, but we aren't talking about normal hash tables. The aim of the prime number is to avoid hash collisions, but in this application you are deliberately aiming for about 700 items in each bucket instead of about one. Whether the modulus is prime or not will make no detectable difference with this degree of hash collision. Tony. -- f.a.n.finch fanf@covalent.net dot@dotat.at "If I didn't see it with my own eyes I would never have believed it!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 17: 7:34 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 17:07:33 2000 Return-Path: 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 A3F7137B402 for ; Wed, 13 Dec 2000 17:07:32 -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 eBE17Vs83372; Wed, 13 Dec 2000 18:07:31 -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 SAA43600; Wed, 13 Dec 2000 18:07:30 -0700 (MST) Message-Id: <200012140107.SAA43600@harmony.village.org> To: "Pedro F. Giffuni" Subject: Re: StrongARM support? Cc: Devin Butterfield , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 13 Dec 2000 19:30:37 EST." <3A3814AD.6AE6E213@pitt.edu> References: <3A3814AD.6AE6E213@pitt.edu> <3A380FA5.9BD9F23C@wireless.net> Date: Wed, 13 Dec 2000 18:07:30 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A3814AD.6AE6E213@pitt.edu> "Pedro F. Giffuni" writes: : There was somone looking at the NetBSD code with hungry eyes but I : never heard anything more... check the archives. Last I heard, only the MIPS based PDAs were supported by NetBSD/hpcmips. I know that there are some efforts to make things run on sh3 machines and there's been talk about the arm as well, but I don't think they have been committed to the tree just yet. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 18:21:33 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 18:21:32 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ginsberg.uol.com.br (unknown [200.231.206.26]) by hub.freebsd.org (Postfix) with ESMTP id 6900F37B698 for ; Wed, 13 Dec 2000 18:21:30 -0800 (PST) Received: from 200-191-39-64-as.acessonet.com.br (200-191-39-64-as.acessonet.com.br [200.191.39.64]) by ginsberg.uol.com.br (8.9.1/8.9.1) with ESMTP id AAA12802; Thu, 14 Dec 2000 00:20:51 -0200 (BRST) Date: Thu, 14 Dec 2000 00:16:10 -0200 (BRST) From: Giovanni P Tirloni X-Sender: riot@mink01.tirloni.co.uk To: Brian Somers Cc: hackers@FreeBSD.ORG Subject: Re: PPP failures in 4.2-STABLE In-Reply-To: <200012132304.eBDN4LU69889@hak.lan.Awfulhak.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 Brian, I thought it would be something related to ppp itself after the update but in fact it was related to mgetty+sendfax as you've said before. I deinstalled it and ppp is working fine now (I'll play it mgetty again later). Thanks for your help :-) On Wed, 13 Dec 2000, Brian Somers wrote: > Hi, > > The only thing that comes to mind here is that perhaps you've got > something like hylafax or mgetty running against the same port and > something's gone wrong with the port locking code. > > It *looks* like something's writing fax commands to your modem at the > same time as you're trying to dial.... Giovanni P. Tirloni mail: riot@techie.com mail: tirloni@twu.net fone: +55 44 225 6267 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 20:46:14 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 20:46:13 2000 Return-Path: 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 2571C37B402 for ; Wed, 13 Dec 2000 20:46:12 -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 eBE4jpw78659; Wed, 13 Dec 2000 20:45:52 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: Devin Butterfield Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: StrongARM support? In-Reply-To: Message from Devin Butterfield of "Wed, 13 Dec 2000 16:09:09 PST." <3A380FA5.9BD9F23C@wireless.net> Date: Wed, 13 Dec 2000 20:45:51 -0800 Message-ID: <78656.976769151@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there any work in progress to support running FreeBSD on ARM > processors? If not, are there any plans to? I would be very interested > in helping out with such an effort. I would love to have FreeBSD running > on my iPAQ PocketPC. :) No work in progress, no plans. Would you be interested in heading such a project? That's what's needed. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 13 22: 4:10 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 13 22:04:06 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from db.wireless.net (adsl-gte-la-216-86-194-70.mminternet.com [216.86.194.70]) by hub.freebsd.org (Postfix) with ESMTP id 4818337B400 for ; Wed, 13 Dec 2000 22:04:06 -0800 (PST) Received: from wireless.net (dbutter@dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with ESMTP id VAA25801; Wed, 13 Dec 2000 21:49:00 -0800 (PST) (envelope-from dbutter@wireless.net) Sender: dbutter@db.wireless.net Message-ID: <3A3862E4.5A46E14C@wireless.net> Date: Wed, 13 Dec 2000 22:04:20 -0800 From: Devin Butterfield X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.18pre21 i686) X-Accept-Language: en MIME-Version: 1.0 To: Jordan Hubbard Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: StrongARM support? References: <78656.976769151@winston.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard wrote: > > > Is there any work in progress to support running FreeBSD on ARM > > processors? If not, are there any plans to? I would be very interested > > in helping out with such an effort. I would love to have FreeBSD running > > on my iPAQ PocketPC. :) > > No work in progress, no plans. Would you be interested in heading > such a project? That's what's needed. :) > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message Unfortunately, I don't think that I have enough knowledge to "head" such a project. I can certainly help in the effort though. I'm familiar with the FreeBSD kernel and have written drivers but I really know little about ARM or what it would take to get the FreeBSD kernel to boot on an ARM. I guess we could start by using the data collected by the NetBSD group's effort to run on ARM. Is there anyone here who is familiar with NetBSD's ARM project? Anyone here interested in such a project (and perhaps who has some prior knowledge of what would be involved in realizing such a beast)? -- Regards, Devin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 0:55: 4 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 00:55:02 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from menelao.polito.it (menelao.polito.it [130.192.3.30]) by hub.freebsd.org (Postfix) with SMTP id BCF5237B400 for ; Thu, 14 Dec 2000 00:55:01 -0800 (PST) Received: (qmail 848 invoked from network); 14 Dec 2000 08:54:53 -0000 Received: from truciolo.polito.it (HELO truciolo) (130.192.16.81) by menelao.polito.it with SMTP; 14 Dec 2000 08:54:53 -0000 From: "Fulvio Risso" To: , Cc: Subject: Kyxtech: freebsd outsniffed by wintendo!!?!? Date: Thu, 14 Dec 2000 09:53:29 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-reply-to: <200012122113.eBCLDX305049@mass.osd.bsdi.com> X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. Sorry for bothering you again. This is the last public reply on this argument. - I'm very happy to hear (from many of you) that what "Jessem" said was not the FreeBSD-people thought. - I like FreeBSD myself; we have several FreeBSD servers on our network - I apologize for not having sent a summary of our tests on the FreeBSD mlist. - Fast answers to the several questions: Buffer sizes We did not make any test about creating 1MB buffers. However our architecture does not have the problem that "large buffer" = "large time used to transfer this buffer to user level" because we are able to transfer small pieces of data according to the network status. In other words, we have a transfer similar to the BIOCIMMEDIATE mode of BSD, so the transfer should always be optimized. Context switches Are kept the lowest, because several packets can be transferred at the same time. Safety We still keep 2 buffers (kernel and user). We're evaluating a 1-buffer architecture (taking into account the security problems) UFS filesystem We used FAT to strore packets because the UFS filesystem was on a second hard disk, so that the disk could have made some difference. We can reinstall BSD and repeat the test. We'll do that for sure. Improving BPF We made source code freely availble (http://netgroup-serv.polito.it/WinPcap/). We're very happy if someone will implements these ideas in BSD, so we can discuss (and compare) ideas between us. To understand more We submitted a paper "An Architecture for High Performance Network Analysis". You can find more details (and updated tests) at http://www.polito.it/~risso/research/WinPcap.pdf Thank you again, fulvio and the WinPcap team To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 2:20:45 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 02:20:42 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rainbownet.com (ns.rainbownet.com [212.141.58.2]) by hub.freebsd.org (Postfix) with ESMTP id C70F937B400; Thu, 14 Dec 2000 02:20:40 -0800 (PST) Received: from HOME (HOME.lan.logital.it [192.168.28.135]) by mail.rainbownet.com (8.9.1/8.9.1) with SMTP id LAA08429; Thu, 14 Dec 2000 11:20:33 +0100 (CET) (envelope-from aturetta@commit.it) From: "Angelo Turetta" To: , Subject: Anyone working on ACARD SCSI driver? Date: Thu, 14 Dec 2000 11:25:55 +0100 Message-ID: <57D119A31C6AD4118DDF009027DEA83801C766@SRV00> 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 CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <57D119A31C6AD4118DDF009027DEA83801C73A@SRV00> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to find information about a FreeBSD driver for the ACARD SCSI adapter series, based on the ACARD 870 chip family. There are various models, with/without BIOS, Wide/Narrow, ranging from about $40 to $80, and they work honestly. The manufacturer distributes a Linux driver (which is included in RedHat 7.0), but I have found no info about a FreeBSD driver. Thanks for any help (reply cc: my address, please) Angelo Turetta To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 2:36:50 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 02:36:48 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id E6A4537B400 for ; Thu, 14 Dec 2000 02:36:45 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id VAA02077; Thu, 14 Dec 2000 21:06:18 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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: <57D119A31C6AD4118DDF009027DEA83801C766@SRV00> Date: Thu, 14 Dec 2000 21:06:18 +1030 (CST) Sender: doconnor@gsoft.com.au From: "Daniel O'Connor" To: Angelo Turetta Subject: RE: Anyone working on ACARD SCSI driver? Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Dec-00 Angelo Turetta wrote: > I'm trying to find information about a FreeBSD driver for the ACARD SCSI > adapter series, based on the ACARD 870 chip family. > > There are various models, with/without BIOS, Wide/Narrow, ranging from about > $40 to $80, and they work honestly. > > The manufacturer distributes a Linux driver (which is included in RedHat > 7.0), but I have found no info about a FreeBSD driver. > > Thanks for any help (reply cc: my address, please) I have the specs for this card (had to sign an NDA but it wasn't very onerous).. Unfortunatly I don't have much spare time and I have never written a SCSI driver before :) Also.. The Linux driver is written _very_ badly.. It's horrible to read :( --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 2:47:30 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 02:47:29 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id 2F62337B404 for ; Thu, 14 Dec 2000 02:47:28 -0800 (PST) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id MAA24260; Thu, 14 Dec 2000 12:53:12 +0100 Message-ID: <3A38A58A.1D69185A@i-clue.de> Date: Thu, 14 Dec 2000 11:48:42 +0100 From: Christoph Sold Organization: i-clue GmbH X-Mailer: Mozilla 4.75 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: hackers@freebsd.org Subject: ping: how to set the don't fragment bit? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Folks, to test a secure tunnel, ping should be able to set the don't fragment bit in IP packets. Our ping doesn't allow this. Linsucks does. Since I never before did any network programming: Is it complicated to add an option to do so? Either a hint how to program it, or some helpful soul with the knowledge already in place to take this task? Thanks in advance -Christoph Sold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 3:22: 3 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 03:22:01 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.189]) by hub.freebsd.org (Postfix) with SMTP id 36ED337B402 for ; Thu, 14 Dec 2000 03:21:59 -0800 (PST) Received: (qmail 1465 invoked by uid 1000); 14 Dec 2000 11:21:04 -0000 Date: Thu, 14 Dec 2000 13:21:04 +0200 From: Peter Pentchev To: Christoph Sold Cc: hackers@freebsd.org Subject: Re: ping: how to set the don't fragment bit? Message-ID: <20001214132104.C369@ringworld.oblivion.bg> Mail-Followup-To: Christoph Sold , hackers@freebsd.org References: <3A38A58A.1D69185A@i-clue.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A38A58A.1D69185A@i-clue.de>; from so@server.i-clue.de on Thu, Dec 14, 2000 at 11:48:42AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 14, 2000 at 11:48:42AM +0100, Christoph Sold wrote: > Hi Folks, > > to test a secure tunnel, ping should be able to set the don't fragment > bit in IP packets. Our ping doesn't allow this. Linsucks does. > > Since I never before did any network programming: Is it complicated to > add an option to do so? Either a hint how to program it, or some helpful > soul with the knowledge already in place to take this task? There are other utilities available to craft ICMP ECHO packets - sing and hping come to mind. I'm not sure if sing has been ported to FreeBSD, but there is a security/hping port. You might want to try a freshmeat.net search, or browse the index there. Hope that helps! G'luck, Peter -- The rest of this sentence is written in Thailand, on To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 3:27:37 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 03:27:31 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from fep19-svc.tin.it (pop09-acc.tin.it [212.216.176.72]) by hub.freebsd.org (Postfix) with ESMTP id 0439F37B400 for ; Thu, 14 Dec 2000 03:27:31 -0800 (PST) Received: from lorix ([212.171.148.94]) by fep19-svc.tin.it (InterMail vM.4.01.02.39 201-229-119-122) with SMTP id <20001214112728.FQIE18957.fep19-svc.tin.it@lorix>; Thu, 14 Dec 2000 12:27:28 +0100 Message-ID: <009801c065c0$a2bd1200$016464c8@lorix> From: "Loris Degioanni" To: "Michael T. Stolarchuk" Cc: , , , , References: <200012121622.eBCGMtH16626@off.off.to> Subject: R: [tcpdump-workers] Re: R: [Ethereal-dev] Re: Fwd: kyxtech: freebsd outsniffed by wintendo !!?!? Date: Thu, 14 Dec 2000 11:57:41 +0100 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 -----Messaggio Originale----- Da: Michael T. Stolarchuk A: Fulvio Risso Cc: ; ; ; ; ; ; ; Data invio: martedì 12 dicembre 2000 17.22 Oggetto: [tcpdump-workers] Re: R: [Ethereal-dev] Re: Fwd: kyxtech: freebsd outsniffed by wintendo !!?!? > > > typical buffer sizes for bpf these days are still 32K, > One could then say that if you up the buffer sizes to (2) 512M buffers, > you'd get much better results, but the actual results are kinda suprising.... > you may/may not get better performance... > by increasing the buffer size, you incur a longer kernel copy of > the buffer's out into user space. In short bursts, the performance > may be better, but under long heavy loads, you could get *more* > packet loss... I think this is not a satisfactory explanation. I am not a freebsd guru but, as far as I know, bpfread is invoked during normal scheduling, while bpf_tap is called by the NIC driver, therefore I suppose during an interrupt. I am sure this is the situation in Windows. This means that the tap has always higher priority and is not influenced by the copy, so having huge buffers is not a problem, because the copy is always interrupted by the arrival of a new packet. Can anyone confirm/refute this behavior in freebsd? > even so, 32K is abysmal... and changing it, to, say, 128K may > be a much better alternative... I agree. > ---------- > don't discount this article and its measurements... > ---------- > > > i was asked some serious questions about sniffing by some > microsoft developers... The people i talked to were > very serious about doing good analysis of sniffing performance. > This is another example of a similar analysis, and i do belive > the results... i do not think they are skewed, but i would > have liked a bit more information about the bpf which was > used (for example, what were the buffer sizes which > were used, do you have more information about how > system resources were consumed?) > > But i'll also point out that there ARE several platforms in > existance today which use non-windows platforms and get very > good sniffing results. I am sure of this. But very few provide a detailed analysis of the performance. Our test gives precise numbers, which can be contested, but not without other numbers. > Even so, i'd like to know whether the `wintendo' sniffing > is done without ever doing any context switches; ie: much > of the bpf cost in doing sniffing arised out of the need to > isolate the process spaces from the kernel spaces... if you > don't have the same isolation, you lose safety, but gain > performance. > `wintendo' sniffing is done in a way very similar to the one of BPF. With the same buffer size, the number of context switches is approximatly the same. Loris. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 3:28:55 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 03:28:52 2000 Return-Path: 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 7533F37B400 for ; Thu, 14 Dec 2000 03:28:46 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA71399; Thu, 14 Dec 2000 12:28:40 +0100 (CET) (envelope-from des@ofug.org) Sender: 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: Tony Finch Cc: Gustavo Vieira Goncalves Coelho Rios , hackers@FreeBSD.ORG Subject: Re: very big mail spool directory References: <3A368F8C.1918684F@ifour.com.br> <20001213214404.P71002@hand.dotat.at> From: Dag-Erling Smorgrav Date: 14 Dec 2000 12:28:40 +0100 In-Reply-To: Tony Finch's message of "Wed, 13 Dec 2000 21:44:04 +0000" 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 Tony Finch writes: > Why a prime number? All you need is an even spread, and given that > user IDs are usually allocated sequentially any modulus will do. Because a prime number is less likely to cause an imbalance in where files are actually stored on disk - just like you want an odd (and preferably prime) stripe size on RAIDs to (amongst other reasons) avoid having all the superblock backups end up on the same disk. 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 Thu Dec 14 3:40: 6 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 03:40:02 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from euromail1.genrad.com (x117.genrad.co.uk [195.99.3.117]) by hub.freebsd.org (Postfix) with ESMTP id 6E9D837B400 for ; Thu, 14 Dec 2000 03:40:01 -0800 (PST) Received: from CDP437 (cdp437.uk.genrad.com [132.223.135.120]) by euromail1.genrad.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id YV7NRVA3; Thu, 14 Dec 2000 11:40:00 -0000 From: Robert Swindells To: dbutter@wireless.net Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: <3A380FA5.9BD9F23C@wireless.net> (message from Devin Butterfield on Wed, 13 Dec 2000 16:09:09 -0800) Subject: Re: StrongARM support? Reply-To: rjs@fdy2.demon.co.uk Message-Id: <20001214114001.6E9D837B400@hub.freebsd.org> Date: Thu, 14 Dec 2000 03:40:01 -0800 (PST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Devin Butterfield wrote: >Is there any work in progress to support running FreeBSD on ARM >processors? If not, are there any plans to? I would be very interested >in helping out with such an effort. I would love to have FreeBSD running >on my iPAQ PocketPC. :) There is a project to put NetBSD/arm32 onto the iPAQ PocketPC. I am developing it on an Intel Assabet board, not the iPAQ, but the intention is that it will work on any SA-1100 or SA-1110 system. I can boot the kernel to the point where it attempts to mount the root device, but am having problems getting ethernet to work. I could certainly use some help writing extra device drivers. >I know that linux is already running well on ARM but I would really like >to see FreeBSD running in its place. NetBSD already runs on most ARM processors, just not the newer StrongARM ones. I would like to see (and work on) a FreeBSD StrongARM port though. Robert Swindells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 3:56:17 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 03:56:12 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from euromail1.genrad.com (x117.genrad.co.uk [195.99.3.117]) by hub.freebsd.org (Postfix) with ESMTP id ED97337B400 for ; Thu, 14 Dec 2000 03:56:11 -0800 (PST) Received: from CDP437 (cdp437.uk.genrad.com [132.223.135.120]) by euromail1.genrad.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id YV7NRVCV; Thu, 14 Dec 2000 11:56:10 -0000 From: Robert Swindells To: imp@village.org Cc: pfg1+@pitt.edu, dbutter@wireless.net, freebsd-hackers@FreeBSD.ORG In-reply-to: <200012140107.SAA43600@harmony.village.org> (message from Warner Losh on Wed, 13 Dec 2000 18:07:30 -0700) Subject: Re: StrongARM support? Reply-To: rjs@fdy2.demon.co.uk Message-Id: <20001214115612.ED97337B400@hub.freebsd.org> Date: Thu, 14 Dec 2000 03:56:12 -0800 (PST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In message <3A3814AD.6AE6E213@pitt.edu> "Pedro F. Giffuni" writes: >: There was somone looking at the NetBSD code with hungry eyes but I >: never heard anything more... check the archives. >Last I heard, only the MIPS based PDAs were supported by >NetBSD/hpcmips. I know that there are some efforts to make things run >on sh3 machines and there's been talk about the arm as well, but I >don't think they have been committed to the tree just yet. NetBSD/hpcmips takes a different approach to NetBSD/arm32 in that it loads on top of WinCE. As far as I can tell, the hpcmips kernel reuses the WinCE MMU translations; all the arm32 ones rely on a bootloader to map RAM to 0xf0000000. I mainly want the NetBSD SA-11x0 port to work on our own hardware where I can just put a different image into flash, so I am not looking at supporting loading on top of WinCE. So far, nothing has been committed to the tree. Robert Swindells To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 3:58:13 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 03:58:11 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139]) by hub.freebsd.org (Postfix) with ESMTP id 9AAAC37B402 for ; Thu, 14 Dec 2000 03:58:08 -0800 (PST) Received: from wiliam.alcove-int ([10.16.110.19]) by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian)) id 146X14-0003XC-00; Thu, 14 Dec 2000 12:57:42 +0100 Received: from nsouch by wiliam.alcove-int with local (Exim 3.12 #1 (Debian)) id 146X11-0004Hr-00; Thu, 14 Dec 2000 12:57:39 +0100 Date: Thu, 14 Dec 2000 12:57:39 +0100 From: Nicolas Souchu To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: Partial start on pci + serial/parallel cards Message-ID: <20001214125739.C16207@wiliam.alcove-int> References: <20001212100513.B6007@wiliam.alcove-int> <20001211154207.A25074@wiliam.alcove-int> <200012090613.XAA18688@harmony.village.org> <20001211154207.A25074@wiliam.alcove-int> <200012111836.LAA38242@harmony.village.org> <20001212100513.B6007@wiliam.alcove-int> <200012121707.KAA30358@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i In-Reply-To: <200012121707.KAA30358@harmony.village.org>; from imp@village.org on Tue, Dec 12, 2000 at 10:07:07AM -0700 Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Efr?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 12, 2000 at 10:07:07AM -0700, Warner Losh wrote: > In message <20001212100513.B6007@wiliam.alcove-int> Nicolas Souchu writes: > : > looking at the code. I'd also think about moving it to dev/ppc with a > : > ppc_isa.c and ppc_puc.c. > : > : This is something I don't understand. If ppc_puc is a PCI driver why don't > : you put in the pci directory and let ppc_isa in isa one? > > Because in FreeBSD you put all the files for a driver in one > directory. In NetBSD you'd do things the way you are talking about. > sio and ppc break this rule right now. I'm sure that this subject has been discussion many times on the lists. I'm also sure that there's a good reason for this, otherwise it wouldn't be your choice (you is the team). But as it is the opposite of my personal feeling, could you give me one reason for this in few words? Is it for maintainance purpose, so you can remove the whole driver if not anymore supported for example? NetBSD is architecture independent oriented, so I guess their choice is also good from there point of view... Nicholas -- Nicolas.Souchu@alcove.fr Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 4:13: 0 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 04:12:55 2000 Return-Path: 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 37B5437B400 for ; Thu, 14 Dec 2000 04:12:55 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBECMg901853; Thu, 14 Dec 2000 04:22:43 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012141222.eBECMg901853@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nicolas Souchu Cc: hackers@FreeBSD.ORG Subject: Re: Partial start on pci + serial/parallel cards In-reply-to: Your message of "Thu, 14 Dec 2000 12:57:39 +0100." <20001214125739.C16207@wiliam.alcove-int> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Thu, 14 Dec 2000 04:22:42 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > : This is something I don't understand. If ppc_puc is a PCI driver wh= y don't > > : you put in the pci directory and let ppc_isa in isa one? > > = > > Because in FreeBSD you put all the files for a driver in one > > directory. In NetBSD you'd do things the way you are talking about. > > sio and ppc break this rule right now. > = > I'm sure that this subject has been discussion many times on the lists.= > I'm also sure that there's a good reason for this, otherwise it wouldn'= t be > your choice (you is the team). But as it is the opposite of my personal= > feeling, could you give me one reason for this in few words? The desire was to put all of the files related to a given driver in one = place, so that when you're working on the code, you have it all in front = of you, as opposed to having to chase it down all over the tree. This = matches well with the functional separation in FreeBSD; the interface = between drivers and busses is well defined, wheras the interfaces between= = bus attachments and driver cores is left to the driver developer. Thus the things that are closely tied together at the software level (ie.= = driver bus attachments and their cores) are kept physically close = together. > Is it for maintainance purpose, so you can remove the whole driver if > not anymore supported for example? NetBSD is architecture independent > oriented, so I guess their choice is also good from there point of view= =2E.. There are good arguments for doing things each way. One valid criticism = of our approach is that if you change the interface between a bus and = drivers, you have to go and track down all of the code which interfaces = with the bus. We help work around this through the convention of naming = all driver bus attachments as _.c, so a simple = 'locate _.c' will find them all. Regards, -- = =2E.. 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 Dec 14 4:17:57 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 04:17:51 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mesache.encomix.es (mesache.encomix.es [194.143.192.3]) by hub.freebsd.org (Postfix) with SMTP id 6FAC737B400 for ; Thu, 14 Dec 2000 04:17:50 -0800 (PST) Received: (qmail 23139 invoked from network); 14 Dec 2000 12:17:35 -0000 Received: from unknown (HELO jesus) (195.114.209.1) by mesache.encomix.es with SMTP; 14 Dec 2000 12:17:35 -0000 Message-ID: <001401c065c8$7b8d5b60$4200a8c0@jesus> From: =?iso-8859-1?Q?Jes=FAs_Arn=E1iz?= To: Subject: Persistent system Date: Thu, 14 Dec 2000 13:22:08 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit 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 Hi Everyone! I need some mean to make a filesystem persistent. What kind of solutions I have in FreeBSD?. I want a system able to reboot without problems after a power off. Thanks in advance. Jesús Arnáiz ARCOMEDIA.COM. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 7:39:45 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 07:39:42 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from off.off.to (off.off.to [63.77.233.98]) by hub.freebsd.org (Postfix) with ESMTP id 4D78637B400 for ; Thu, 14 Dec 2000 07:39:41 -0800 (PST) Received: from off.off.to (localhost [127.0.0.1]) by off.off.to (8.10.1/8.10.1) with ESMTP id eBEFdNH30483; Thu, 14 Dec 2000 10:39:23 -0500 (EST) Message-Id: <200012141539.eBEFdNH30483@off.off.to> To: "Loris Degioanni" Cc: "Michael T. Stolarchuk" , tcpdump-workers@tcpdump.org, ethereal-dev@ethereal.com, snort-devel@lists.sourceforge.net, freebsd-hackers@freebsd.org, tech@openbsd.org, mts@off.off.to Subject: Re: R: [tcpdump-workers] Re: R: [Ethereal-dev] Re: Fwd: kyxtech: freebsd outsniffed by wintendo !!?!? In-reply-to: Your message of "Thu, 14 Dec 2000 11:57:41 +0100." <009801c065c0$a2bd1200$016464c8@lorix> Date: Thu, 14 Dec 2000 10:39:23 -0500 From: "Michael T. Stolarchuk" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <009801c065c0$a2bd1200$016464c8@lorix>, "Loris Degioanni" writes: > >-----Messaggio Originale----- >Da: Michael T. Stolarchuk >A: Fulvio Risso >freebsd outsniffed by wintendo !!?!? WRT: http://netgroup-serv.polito.it/winpcap/docs/performance.htm >> > >> >> typical buffer sizes for bpf these days are still 32K, >> One could then say that if you up the buffer sizes to (2) 512M >buffers, >> you'd get much better results, but the actual results are kinda >suprising.... >> you may/may not get better performance... >> by increasing the buffer size, you incur a longer kernel copy of >> the buffer's out into user space. In short bursts, the performance >> may be better, but under long heavy loads, you could get *more* >> packet loss... > >I think this is not a satisfactory explanation. I am not a freebsd guru >but, as far as I know, bpfread is invoked during normal scheduling, >while bpf_tap is called by the NIC driver, therefore I suppose during an >interrupt. I am sure this is the situation in Windows. This means that >the tap has always higher priority and is not influenced by the copy, so >having huge buffers is not a problem, because the copy is always >interrupted by the arrival of a new packet. Can anyone confirm/refute >this behavior in freebsd? ah, but the buffer sizes are fixed, and when the second buffer is full, packets are lost. yes, the tap runs at a higher prio than the buffer, but that doesn't alone guarnatee you won't see packet loss. (btw: i can confirm that behavior because i've had to work with it... i'm familiar with these effects since i wrote the nfrd sniffing and protocol decomposition stack) Or saying it another way: if you increase the buffer sizes, say to 1M each, and you're using, say completely saturdated 100Mb, which means 12.5Mbyes/sec, you have to get the copy out of bpf to process space in 1/12.5Mb/sec->80 Millisec. By copy rates, that's a long time. But, typical BPF sleep prioirities are LOW, which means that other processes complete with the bpf-processes restart to gain the processor. (As i recall, that has been fixed in a few architecutres). So if the bpf is run on a loaded machine (ie: a typical intrusion detection system) you still see periodic packet loss. That also partially explains why just test-sniffing the traffic isn't sufficient to test a platform for its ability to perform a decent job at ids... >`wintendo' sniffing is done in a way very similar to the one of BPF. >With the same buffer size, the number of context switches is >approximatly the same. I'm sorry, but i don't see that in your paper. Near the bottom of the paper it says that windoes sniffing buffers are 1M large. There are *very few* bpf's with buffers that large. In fact, in several kernels which i've used, multiple 1M kernel alloc's for space will cause the kernel to hang indefinitly (due to multiple 1M vm space allocations). i started my first reply with your text snippet noting the buffer size differences. Also, in the same article, there's not attempt at trying to uncover the cause of performance difference, i don't see measurements of context switch rates, number of kernel system calls, nor number of interrupts. If i have missed it somewhere please let me know. What i wish i had is a good tool to discover what is going on during the bpf packet loss. I was hoping (a few years back) to instructment a kernel, so that instead of being able to profile the sniffing process via statistical information about clock-tics, i could instead collect statistical about what was going on during bpf-packet-loss (ie: when the bpf second buffer is full). Turns out, that's hard to do, but i haven't forgotten how worthwhile such a hack would be... mts. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 7:44: 1 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 07:43:59 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from gradient.cis.upenn.edu (GRADIENT.CIS.UPENN.EDU [158.130.67.48]) by hub.freebsd.org (Postfix) with ESMTP id EDBEE37B400 for ; Thu, 14 Dec 2000 07:43:58 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by gradient.cis.upenn.edu (8.10.1/8.10.1) with ESMTP id eBEFhvt16045 for ; Thu, 14 Dec 2000 10:43:57 -0500 (EST) Date: Thu, 14 Dec 2000 10:43:57 -0500 (EST) From: Alwyn Goodloe To: freebsd-hackers@FreeBSD.org Subject: Firewall question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Guys, First I would like to thank everyone who responded to last weeks question. This time around my question is a little more detailed (as I managed to learn more :-) ). I was going to filter on a particular condition and divert those packets to a divert socket where some processing was to take place and if the proper conditions are met we would send the little guys on their way. But as I read the code the packet is basically gone from the routing software at that point. Any idea how to send the packets on their way once I've diverted them. I know this may be an easy question to those who do this sort of thing alot. As a last resort I was just going to hack the ip_fw_chk() fn (in ip_fw.c). Of course I don't like hacking systems internals if there is an easy way around it. Thanks for your help. Alwyn Goodloe agoodloe@gradient.cis.upenn.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 8: 3:27 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 08:03:23 2000 Return-Path: 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 CDC9437B400 for ; Thu, 14 Dec 2000 08:03:22 -0800 (PST) Received: from localhost (dphoenix@localhost) by gandalf.bravenet.com (8.10.1/8.10.1) with ESMTP id eBEG0J507771; Thu, 14 Dec 2000 08:00:19 -0800 (PST) X-Authentication-Warning: gandalf.bravenet.com: dphoenix owned process doing -bs Date: Thu, 14 Dec 2000 08:00:18 -0800 (PST) From: Dan Phoenix To: Poul-Henning Kamp Cc: Bill Fumerola , freebsd-hackers@FreeBSD.ORG Subject: Re: Tun driver? In-Reply-To: <4581.976715688@critter> 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 you mean device side? you mean server side? -- Dan +-----------------------------------------------------------------------+ | ----- Daniel Phoenix Mail to:dan@bravenet.com | | | | / ___ ____ ____ |____ ____ | | | | / |/ / | \ / | \ | \ | \ __|__ | | | \ | | | \ / |____/ | | |____/ | | | | / | | | \ / | | | | | | | |__/ | \____\ \/ \____ | | \____ | | +_______________________________________________________________________+ mv /lib/ld.so /lib/ld.so.old;echo "Damnit" On Wed, 13 Dec 2000, Poul-Henning Kamp wrote: > Date: Wed, 13 Dec 2000 14:54:48 +0100 > From: Poul-Henning Kamp > To: Dan Phoenix > Cc: Bill Fumerola , freebsd-hackers@FreeBSD.ORG > Subject: Re: Tun driver? > > > You need to open the "device-side" of the tunnel (/dev/tun0) before the > interface is created. > > Poul-Henning > > In message , Dan > Phoenix writes: > > > >[root@elrond conf]# ifconfig tun0 1.1.1.1 up > >ifconfig: interface tun0 does not exist > >[root@elrond conf]# ls -al /dev/tun0 > >crw------- 1 uucp dialer 52, 0 Dec 12 13:30 /dev/tun0 > >[root@elrond conf]# > > > >this is confusing me....trying to get vtund working in ports collection. > > > >tun device is in GENERIC kernel when i checked > >and exist in /dev as per test above.....yet > >it tells me it does not exist! > >Ideas? > > > > > > > > > > > > > > > >-- > >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 > > > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 9:12:26 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 09:12:24 2000 Return-Path: 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 30AD237B402 for ; Thu, 14 Dec 2000 09:12:23 -0800 (PST) Received: (qmail 4434 invoked from network); 14 Dec 2000 17:12:21 -0000 Received: from spirit.sto.dynas.se (HELO spirit.dynas.se) (172.16.1.10) by karon.sto.dynas.se with SMTP; 14 Dec 2000 17:12:21 -0000 Received: (qmail 27003 invoked by uid 1125); 14 Dec 2000 17:12:25 -0000 Date: Thu, 14 Dec 2000 09:12:18 -0800 (PST) From: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= X-Sender: mikko@dynas.se To: freebsd-hackers@freebsd.org Subject: Rejecting a connection: is accept(2) correct? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Reply-To: mikko@dynas.se X-MIME-Autoconverted: to 8bit by snemail 0.35 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG AFAIK there is no portable way to reject incoming connections without calling accept(). However, accept(2) states: One can obtain user connection request data without confirming the connection by issuing a recvmsg(2) call with an msg_iovlen of 0 and a non-zero msg_controllen, or by issuing a getsockopt(2) request. Similarly, one can provide user connection rejection information by issuing a sendmsg(2) call providing only the control information, or by calling setsockopt(2). Is this really true? A quick experiment with recvmsg() seems to indicate it is not, at least not for TCP sockets. ? /Mikko P.S. Anybody who claims that this works is encouraged to provide proof in the form of code... :-) 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 Thu Dec 14 9:17: 6 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 09:17:05 2000 Return-Path: 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 4384E37B400 for ; Thu, 14 Dec 2000 09:17:04 -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 eBEHH2s86651; Thu, 14 Dec 2000 10:17:03 -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 KAA48386; Thu, 14 Dec 2000 10:17:02 -0700 (MST) Message-Id: <200012141717.KAA48386@harmony.village.org> To: rjs@fdy2.demon.co.uk Subject: Re: StrongARM support? Cc: pfg1+@pitt.edu, dbutter@wireless.net, freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 14 Dec 2000 04:56:12 MST." <200012141156.EAA02263@schizoid.village.org> References: <200012141156.EAA02263@schizoid.village.org> Date: Thu, 14 Dec 2000 10:17:02 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200012141156.EAA02263@schizoid.village.org> Robert Swindells writes: : As far as I can tell, the hpcmips kernel reuses the WinCE MMU : translations; all the arm32 ones rely on a bootloader to map RAM : to 0xf0000000. The hpcmips kernel doesn't do that. The hpcmips loader does that. Once the stuff is loaded into memory, the kernel takes over. Part of that takeover is blowing away the TLB. Once the tlb has been reset, the old WinCE mappings are gone for good. : I mainly want the NetBSD SA-11x0 port to work on our own hardware : where I can just put a different image into flash, so I am not looking : at supporting loading on top of WinCE. OK. The reason that the hpcmips guys went that was was that there's a huge number of WinCE devices, some of which you can get very cheaply, that do not have the option of Flash at all. WinCE is in Mask Programmable Roms. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 9:19:49 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 09:19:48 2000 Return-Path: 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 E380137B400 for ; Thu, 14 Dec 2000 09:19:46 -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 eBEHJjs86661; Thu, 14 Dec 2000 10:19:45 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA48406; Thu, 14 Dec 2000 10:19:45 -0700 (MST) Message-Id: <200012141719.KAA48406@harmony.village.org> To: Nicolas Souchu Subject: Re: Partial start on pci + serial/parallel cards Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 14 Dec 2000 12:57:39 +0100." <20001214125739.C16207@wiliam.alcove-int> References: <20001214125739.C16207@wiliam.alcove-int> <20001212100513.B6007@wiliam.alcove-int> <20001211154207.A25074@wiliam.alcove-int> <200012090613.XAA18688@harmony.village.org> <20001211154207.A25074@wiliam.alcove-int> <200012111836.LAA38242@harmony.village.org> <20001212100513.B6007@wiliam.alcove-int> <200012121707.KAA30358@harmony.village.org> Date: Thu, 14 Dec 2000 10:19:45 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001214125739.C16207@wiliam.alcove-int> Nicolas Souchu writes: : I'm sure that this subject has been discussion many times on the lists. : I'm also sure that there's a good reason for this, otherwise it wouldn't be : your choice (you is the team). But as it is the opposite of my personal : feeling, could you give me one reason for this in few words? The basic reason for having the dev/foo thing was so that you don't have to hunt over the entire tree to maintian your driver. All the files are in one place and you can easily find them. : Is it for maintainance purpose, so you can remove the whole driver if : not anymore supported for example? NetBSD is architecture independent : oriented, so I guess their choice is also good from there point of view... NetBSD took the view that you have a core driver and then a bunch of bus attachments. The affinity is stronger to the bus code than to the device code so they built the separation they did that way. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 9:36:13 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 09:36:11 2000 Return-Path: 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 D88BC37B400 for ; Thu, 14 Dec 2000 09:36:08 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 14 Dec 2000 17:36:06 +0000 (GMT) Date: Thu, 14 Dec 2000 17:36:05 +0000 From: David Malone To: =?iso-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= Cc: freebsd-hackers@freebsd.org Subject: Re: Rejecting a connection: is accept(2) correct? Message-ID: <20001214173605.A53698@walton.maths.tcd.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: ; from mikko@dynas.se on Thu, Dec 14, 2000 at 09:12:18AM -0800 Sender: dwmalone@maths.tcd.ie Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 14, 2000 at 09:12:18AM -0800, Mikko Työläjärvi wrote: > Is this really true? A quick experiment with recvmsg() seems to > indicate it is not, at least not for TCP sockets. I think this applies after you have accepted the connection. You can call getpeername() to choose what to do about the call. You can immediately close the connection if you don't want to deal with it. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 9:41: 3 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 09:41:02 2000 Return-Path: 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 3582037B400 for ; Thu, 14 Dec 2000 09:41:01 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eBEHewj06419; Thu, 14 Dec 2000 09:40:58 -0800 (PST) Date: Thu, 14 Dec 2000 09:40:58 -0800 From: Alfred Perlstein To: =?iso-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Rejecting a connection: is accept(2) correct? Message-ID: <20001214094058.C4589@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: ; from mikko@dynas.se on Thu, Dec 14, 2000 at 09:12:18AM -0800 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Mikko Työläjärvi [001214 09:12] wrote: > > AFAIK there is no portable way to reject incoming connections without > calling accept(). However, accept(2) states: > > One can obtain user connection request data without confirming > the connection by issuing a recvmsg(2) call with an msg_iovlen of > 0 and a non-zero msg_controllen, or by issuing a getsockopt(2) > request. Similarly, one can provide user connection rejection > information by issuing a sendmsg(2) call providing only the > control information, or by calling setsockopt(2). > > Is this really true? A quick experiment with recvmsg() seems to > indicate it is not, at least not for TCP sockets. It's supposed to be used with the OSI protocols or something. :) Adapting it to TCP would be nice, but the problem in FreeBSD at least is that by the time a socket is in the listen queue is has completed the TCP connection handshake. > P.S. Anybody who claims that this works is encouraged to provide > proof in the form of code... :-) hah. -- -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 Thu Dec 14 9:43: 0 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 09:42:58 2000 Return-Path: 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 A5CBE37B402 for ; Thu, 14 Dec 2000 09:42:57 -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 MAA55342; Thu, 14 Dec 2000 12:43:51 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20001214120951.022a7560@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 14 Dec 2000 12:10:28 -0500 To: hackers@freebsd.org From: Dennis Subject: if_fxp driver??? Cc: dg@root.com 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 Has the issue with the new rev intel parts been resolved yet? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 9:43:45 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 09:43:41 2000 Return-Path: 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 DE66237B400; Thu, 14 Dec 2000 09:43:39 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 14 Dec 2000 17:43:39 +0000 (GMT) Date: Thu, 14 Dec 2000 17:43:36 +0000 From: David Malone To: Andre Oppermann Cc: "Louis A. Mamakos" , Mike Tancsa , hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: su root hangs when logged in via SSH Message-ID: <20001214174336.A54984@walton.maths.tcd.ie> References: <5.0.1.4.1.20001213153948.01fc9df0@marble.sentex.ca> <3A37E70C.3A935224@telehouse.ch> <200012132153.eBDLrn576602@whizzo.transsys.com> <3A380189.9B95A212@telehouse.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A380189.9B95A212@telehouse.ch>; from oppermann@telehouse.ch on Thu, Dec 14, 2000 at 12:08:57AM +0100 Sender: dwmalone@maths.tcd.ie Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think there is a PR in the database, assigned to me, relating to this. I guess I could go through syslogd and try to make all the IO non-blocking, but I'm not sure how easy that would be. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 9:44:23 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 09:44:21 2000 Return-Path: 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 9BE5237B400 for ; Thu, 14 Dec 2000 09:44:19 -0800 (PST) Received: (qmail 4894 invoked from network); 14 Dec 2000 17:44:17 -0000 Received: from spirit.sto.dynas.se (HELO spirit.dynas.se) (172.16.1.10) by karon.sto.dynas.se with SMTP; 14 Dec 2000 17:44:17 -0000 Received: (qmail 29228 invoked by uid 1125); 14 Dec 2000 17:44:22 -0000 Date: Thu, 14 Dec 2000 09:44:15 -0800 (PST) From: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= X-Sender: mikko@dynas.se To: David Malone Cc: freebsd-hackers@freebsd.org Subject: Re: Rejecting a connection: is accept(2) correct? In-Reply-To: <20001214173605.A53698@walton.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Reply-To: mikko@dynas.se X-MIME-Autoconverted: to 8bit by snemail 0.35 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Dec 2000, David Malone wrote: > On Thu, Dec 14, 2000 at 09:12:18AM -0800, Mikko Työläjärvi wrote: > > > Is this really true? A quick experiment with recvmsg() seems to > > indicate it is not, at least not for TCP sockets. > > I think this applies after you have accepted the connection. You > can call getpeername() to choose what to do about the call. You > can immediately close the connection if you don't want to deal with > it. Umm.. yes, that is the normal way of doing things, but that is not what (I think) it says in the man-page, which is why I was wondering. "One can obtain user connection request data without confirming the connection..." (and then goes on about recvmsg(),sendmsg() and {set,get}sockept() with little or no details). It does not state which socket this is supposed to operate on: the listening socket, or the new one. If it is the listening socket, it would be an innovation, and open up assorted new possibilities. If it is the new socket, it is old news :-) /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 Thu Dec 14 9:45:43 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 09:45:42 2000 Return-Path: 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 1548737B402 for ; Thu, 14 Dec 2000 09:45:42 -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 MAA55377 for ; Thu, 14 Dec 2000 12:46:43 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20001214121201.01f82650@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 14 Dec 2000 12:13:16 -0500 To: hackers@freebsd.org From: Dennis Subject: cp and cpio using boot disk 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 It seems that cp fails badly when used on a system booted by a boot floppy (such as the install floppy). cpio seems to work ok. What is the reason for this? DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 9:51: 4 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 09:51:01 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E5BD37B400 for ; Thu, 14 Dec 2000 09:51:01 -0800 (PST) Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id B46246E2741 for ; Thu, 14 Dec 2000 09:50:53 -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 146bQA-0000IW-00; Thu, 14 Dec 2000 09:39:54 -0700 Sender: wes@mx1.FreeBSD.org Message-ID: <3A38F7DA.6E49F47F@softweyr.com> Date: Thu, 14 Dec 2000 09:39:54 -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: Devin Butterfield Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: StrongARM support? References: <3A380FA5.9BD9F23C@wireless.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Devin Butterfield wrote: > > Hi all, > > Is there any work in progress to support running FreeBSD on ARM > processors? If not, are there any plans to? I would be very interested > in helping out with such an effort. I would love to have FreeBSD running > on my iPAQ PocketPC. :) > > I know that linux is already running well on ARM but I would really like > to see FreeBSD running in its place. NetBSD? They have existing ARM and "hpc" ports, this would be a merging of the two... -- "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 Thu Dec 14 9:56: 3 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 09:56:01 2000 Return-Path: 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 0611637B400 for ; Thu, 14 Dec 2000 09:56:01 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 14 Dec 2000 17:55:59 +0000 (GMT) To: mikko@dynas.se Cc: David Malone , freebsd-hackers@freebsd.org, dwmalone@maths.tcd.ie Subject: Re: Rejecting a connection: is accept(2) correct? In-reply-to: Your message of "Thu, 14 Dec 2000 09:44:15 PST." X-Request-Do: Date: Thu, 14 Dec 2000 17:55:58 +0000 From: David Malone Message-ID: <200012141755.aa62114@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Umm.. yes, that is the normal way of doing things, but that is not > what (I think) it says in the man-page, which is why I was wondering. > "One can obtain user connection request data without confirming the > connection..." (and then goes on about recvmsg(),sendmsg() and > {set,get}sockept() with little or no details). > It does not state which socket this is supposed to operate on: the > listening socket, or the new one. If it is the listening socket, > it would be an innovation, and open up assorted new possibilities. I'd guess it's the new socket 'cos the previous paragraph of the man page talks about protocols which require explicit confirmation, which can be caused by reading or writing to the socket. I'd guess it's just indicating that recvmsg with a zero iovlen doesn't count as a read or write. > If it is the new socket, it is old news :-) If it does work, it would mean that we could use tcp wrappers on `stream wait' services, among other things. Maybe we need an API for this. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 10:11: 2 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 10:11:00 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.161.193]) by hub.freebsd.org (Postfix) with ESMTP id 73E6637B404 for ; Thu, 14 Dec 2000 10:11:00 -0800 (PST) Received: from mail.vt.edu (gkar.cc.vt.edu [198.82.161.190]) by lennier.cc.vt.edu (8.11.0/8.11.0) with ESMTP id eBEIAxv208456 for ; Thu, 14 Dec 2000 13:10:59 -0500 (EST) Received: from flaw ([198.82.82.163]) by gkar.cc.vt.edu (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10) with SMTP id <0G5K00CBRL699I@gkar.cc.vt.edu> for freebsd-hackers@freebsd.org; Thu, 14 Dec 2000 13:10:57 -0500 (EST) Date: Thu, 14 Dec 2000 13:20:43 -0500 From: Raymond Law Subject: SNDCTL_DSP_CHANNELS not defined in soundcard.h when installing KDE 2.0.1 X-Sender: flaw@mail.vt.edu To: freebsd-hackers@freebsd.org Message-id: <3.0.1.32.20001214132043.0073fea4@mail.vt.edu> MIME-version: 1.0 X-Mailer: Windows Eudora Light Version 3.0.1 (32) Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using FreeBSD 4.0-Release and have installed kdesupport-2.0.1. I also set LIBS to -Wl,-export-dynamic as stated in ***. I did ldconfig -m $KDEDIR/lib and ldconfig -m $QTDIR/lib. I configured it and it seemed fine. But gmake fails and gives the following error: artsdsp.c: In function 'ioctl': artsdsp.c:222: 'SNDCTL_DSP_CHANNELS' undeclared (first use in this function) artsdsp.c:222: (Each undeclared identifier is reported only once artsdsp.c:222: for each function it appears in.) Any idea on why SNDCTL_DSP_CHANNELS is not defined in soundcard.h? Thanks. Ray, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 10:15:46 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 10:15:44 2000 Return-Path: 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 9A7DA37B400 for ; Thu, 14 Dec 2000 10:15:42 -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 eBEIFes86944; Thu, 14 Dec 2000 11:15:41 -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 LAA48881; Thu, 14 Dec 2000 11:15:40 -0700 (MST) Message-Id: <200012141815.LAA48881@harmony.village.org> To: Wes Peters Subject: Re: StrongARM support? Cc: Devin Butterfield , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 14 Dec 2000 09:39:54 MST." <3A38F7DA.6E49F47F@softweyr.com> References: <3A38F7DA.6E49F47F@softweyr.com> <3A380FA5.9BD9F23C@wireless.net> Date: Thu, 14 Dec 2000 11:15:40 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A38F7DA.6E49F47F@softweyr.com> Wes Peters writes: : NetBSD? They have existing ARM and "hpc" ports, this would be a merging : of the two... I didn't think that NetBSD had a hpc port. They have an hpcmips port in the tree, as well as other hpc ports not yet committed (hpcsh3 has been seen in the mailing lists as well as hpcarm, but the latter was a theoretical name for the port at the time). There's an unofficial recognition that hpcFOO means "Runs on WinCE machines for the FOO processor" but so far hpcmips is the only one in the tree. There was also talk about an ipaq or ipaqarm port that would be like the ipaq linux port and take over the machine entirely. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 10:33:34 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 10:33:31 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from puck.firepipe.net (poynting.physics.purdue.edu [128.210.146.58]) by hub.freebsd.org (Postfix) with ESMTP id 896AF37B400; Thu, 14 Dec 2000 10:33:31 -0800 (PST) Received: by puck.firepipe.net (Postfix, from userid 1000) id 478E218DB; Thu, 14 Dec 2000 13:33:31 -0500 (EST) Date: Thu, 14 Dec 2000 13:33:31 -0500 From: Will Andrews To: Raymond Law Cc: ports@FreeBSD.org Subject: Re: SNDCTL_DSP_CHANNELS not defined in soundcard.h when installing KDE 2.0.1 Message-ID: <20001214133331.P1873@puck.firepipe.net> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , Raymond Law , ports@FreeBSD.org References: <3.0.1.32.20001214132043.0073fea4@mail.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3.0.1.32.20001214132043.0073fea4@mail.vt.edu>; from rlaw@vt.edu on Thu, Dec 14, 2000 at 01:20:43PM -0500 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: will@puck.firepipe.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 14, 2000 at 01:20:43PM -0500, Raymond Law wrote: > Any idea on why SNDCTL_DSP_CHANNELS is not defined in soundcard.h? Any idea why you are not using the ports to compile KDE2? It's no secret that KDE is Linux-centric, and as such they don't bother to check for problems like slight differences in the APIs. This should be on ports@ anyhow, not hackers@. -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 11:33:33 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 11:33:31 2000 Return-Path: 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 8652D37B402 for ; Thu, 14 Dec 2000 11:33:31 -0800 (PST) Received: from fanf by hand.dotat.at with local (Exim 3.15 #3) id 146e7l-000Nr9-00; Thu, 14 Dec 2000 19:33:05 +0000 Date: Thu, 14 Dec 2000 19:33:05 +0000 From: Tony Finch To: Dag-Erling Smorgrav Cc: Gustavo Vieira Goncalves Coelho Rios , hackers@FreeBSD.ORG Subject: Re: very big mail spool directory Message-ID: <20001214193305.D92196@hand.dotat.at> References: <3A368F8C.1918684F@ifour.com.br> <20001213214404.P71002@hand.dotat.at> 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: fanf@dotat.at Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: >Tony Finch writes: >> Why a prime number? All you need is an even spread, and given that >> user IDs are usually allocated sequentially any modulus will do. > >Because a prime number is less likely to cause an imbalance in where >files are actually stored on disk - just like you want an odd (and >preferably prime) stripe size on RAIDs to (amongst other reasons) >avoid having all the superblock backups end up on the same disk. That's another situation in which the collision rate is very low. I still think any number of about the right size will do. Tony. -- f.a.n.finch fanf@covalent.net dot@dotat.at " ``Well, let's go down and find out who's grave it is.'' ``How?'' ``By going down and finding out!'' " To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 12:51:56 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 12:51:53 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from lh04.opsion.fr (lh04.opsion.fr [212.73.208.230]) by hub.freebsd.org (Postfix) with SMTP id 192C837B404 for ; Thu, 14 Dec 2000 12:51:53 -0800 (PST) Received: from 198.168.78.67 [198.168.78.67] by lh04.opsion.fr; Thu, 14 Dec 2000 20:50:04 GMT From: Thierry Reply-To: tjmsdn@ifrance.com To: freebsd-hackers@freebsd.org Subject: int foowrite( dev_t dev, struct uio *uio, int flag) { ... } documentation ?? Date: Thu, 14 Dec 2000 15:37:08 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00121415551000.00580@FreeBSD.eicon.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We are implementing our OS modem on FreeBSD, We use this definition in our driver : static d_write_t tswrite; We implemented this function: static int tswrite( dev_t dev, struct uio *uio, int flag) { ... } to receive characters from the tty. Is it possible to have documentation about this function, what value we must return ?, what is it flag ?. Is it possible to slow down the call of this function by the kernel ? Thanks in advance. Thierry Jonas. ______________________________________________________________________________ Vous avez un site perso ? 2 millions de francs à gagner sur i(france) ! Webmasters : ZE CONCOURS ! http://www.ifrance.com/_reloc/concours.emailif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 14: 9: 6 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 14:09:03 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from sm10.texas.rr.com (sm10.texas.rr.com [24.93.35.222]) by hub.freebsd.org (Postfix) with ESMTP id C4CFB37B400; Thu, 14 Dec 2000 14:09:02 -0800 (PST) Received: from bleep.craftncomp.com (cs2777-167.houston.rr.com [24.27.77.167]) by sm10.texas.rr.com (8.11.0/8.11.1) with ESMTP id eBEM5VQ04583; Thu, 14 Dec 2000 16:05:31 -0600 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 eBEM8uG28320; Thu, 14 Dec 2000 16:08:56 -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 eBEM9UG76148; Thu, 14 Dec 2000 16:09:30 -0600 (CST) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200012142209.eBEM9UG76148@bloop.craftncomp.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: multimedia@freebsd.org, hackers@freebsd.org Subject: GLide3 CVS - building & patching Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Dec 2000 16:09:30 -0600 From: Stephen Hocking Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've almost built the glide3 from sourceforge's CVS, and intend to make a port of it sometime (it's required for the latest DRI stuff) - has anyone else done this? This later version is also necessary for the voodoo 4 & 5, plus a few things in the headers have changed over time, which the DRI CVS tree seems to need. 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 Thu Dec 14 14:24:29 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 14:24:20 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from axp5.physik.fu-berlin.de (axp5.physik.fu-berlin.de [160.45.34.3]) by hub.freebsd.org (Postfix) with ESMTP id 65DA337B698 for ; Thu, 14 Dec 2000 14:24:19 -0800 (PST) Received: from oberon.physik.fu-berlin.de (oberon.physik.fu-berlin.de [160.45.33.83]) by axp5.physik.fu-berlin.de (8.9.1a/8.9.1) with ESMTP id XAA28502 for ; Thu, 14 Dec 2000 23:24:18 +0100 (MET) Received: (from thimm@localhost) by oberon.physik.fu-berlin.de (8.9.1a/8.9.1) id XAA26811 for freebsd-hackers@freebsd.org; Thu, 14 Dec 2000 23:24:17 +0100 (MET) Received: from pua.physik.fu-berlin.de (IDENT:root@thimm.dialup.fu-berlin.de [160.45.217.207]) by axp5.physik.fu-berlin.de (8.9.1a/8.9.1) with ESMTP id XAA28091; Thu, 14 Dec 2000 23:12:05 +0100 (MET) Received: (from thimm@localhost) by pua.physik.fu-berlin.de (8.11.0/8.11.0) id eBEM7v114182; Thu, 14 Dec 2000 23:07:57 +0100 Date: Thu, 14 Dec 2000 23:07:56 +0100 From: Axel Thimm To: freebsd-current@freebsd.org Cc: freebsd-hackers@freebsd.org, "David E. Cross" , vladimir-bsd-current@math.uic.edu, Brad Knowles , Andrew Gallatin , Roman Shterenzon , "Scot W. Hetzel" , Greg Lewis , cam , Erik Trulsson , Cy Schubert - ITSD Open Systems Group , Jaap Akkerhuis , Stephen Montgomery-Smith , Coleman Kane , Jeff Fisher , ragnar@sysabend.org, Doug@gorean.org, dillon@backplane.com, Andrew Gordon , andrew@ugh.net.au, Carsten Urbach , Tobias Burnus , Wolfram Klaus Subject: rpc.lockd and true NFS locks? Message-ID: <20001214230756.A13794@pua.domain> Reply-To: Axel Thimm , Carsten Urbach Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Lines: 117 Sender: thimm@oberon.physik.fu-berlin.de Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear all, rpc.lockd in FreeBSD suffers from a pubic server's lazyness --- It says it's done the job, but never did anything besides talking... Searching through the lists gives different stories. Some say that NFS locking isn't really necessary, but what about locking critical situations like delivering mail over NFS to FreeBSD homes? Procmail & fcntl made our computing department especially unhappy, and we are wondering whether we can keep our migration strategy (moving our homes to backuped FreeBSD boxes). Some of the following quoted mails (consider this mail as a review, if you like) give hope that some people were working on this (without obviously having commited anything, as one can check in cvsweb). Is this true? Has anyone any server side patches for FreeBSD? Is he/she looking for guinea pigs? Anything is better than the current situation. Our users are running away from our otherwise very comfortable FreeBSD homes. :( On Mon, Apr 03, 2000 at 02:07:54PM +0200, Brad Knowles wrote: > [...] > Besides, file locking becomes impossible in -STABLE once you've > mounted it with NFS (we don't have a working lockd, although work in this > area is progressing in -CURRENT), and NFS writes generally suck when > compared to local writes. > [...] On Fri, Apr 07, 2000 at 08:07:40PM -0400, David E. Cross wrote: > I apologize profusely for the delay of this, but lockd-0.2 is out. > The URL is: http://www.cs.rpi.edu/~crossd/FreeBSD/lockd-0.2.tar.gz > [...] > 5) this does not add the code to FreeBSD's kernel to request the NFS locks > (that is a job for people more skilled than I ;) > [...] On Sat, Apr 08, 2000 at 12:23:14AM -0400, David E. Cross wrote: > [...] > http://www.cs.rpi.edu/~crossd/FreeBSD/lockd-0.2a.tar.gz > [...] On Fri, Apr 07, 2000 at 08:44:33PM -0400, Andrew Gallatin wrote: > This might be a bit touchy, but I'm rather curious -- how will the BSDI > merger affect your lockd work? It seems like your work on lockd > (esp. client side & statd interoperation issues) could be speeded up if you > had access to the BSDI sources.. On Tue, Sep 19, 2000 at 12:38:51PM +0200, Roman Shterenzon wrote: > Quoting Andrew Gordon : > > On Mon, 4 Sep 2000, Roman Shterenzon wrote: > > > The rpc.lockd(8) is marked as broken in /etc/defaults/rc.conf in 4.1-R > > > My question is - how bad is it broken? > > The rpc.lockd in 4.x simply answers "Yes" to all locking requests, and > > does not maintain any state. This means that if your programs actually > > need locking, running rpc.lockd will cause problems (file corruption etc). > > > > On the other hand, if your programs don't need locking and are just making > > the locking calls for the hell of it, rpc.lockd will allow these programs > > to run rather than just hanging up. > > > > There was talk a few months ago about someone having implemented NFS > > locking properly, but I haven't heard any more since - check the mailing > > list archives. > > > > [I wrote the existing 'hack' implementation]. On Wed, Sep 20, 2000 at 09:28:36AM -0500, Scot W. Hetzel wrote: > From: "Roman Shterenzon" > > On Tue, 19 Sep 2000 andrew@ugh.net.au wrote: > > > [...] Someone (from something.edu, perhaps rpi.edu) posted a URL to one > > > of the lists of a working but untested rpc.lockd. [...] I believe that Andrew means "David E. Cross" , but his citation some lines above show that he hadn't worked in that direction. > I kind of remember reading about it on the current mailing list. > Current-Users: Has a working rpc.lockd been imported into CURRENT. If it > has, is there a possibility of getting it MFC'd to STABLE. On Thu, Sep 21, 2000 at 11:02:25AM +0930, Greg Lewis wrote: > Look through the freebsd-hackers archive. There was an rpc.lockd > implementation announced there looking for testers about a month or so > before the 4.0 release. The person who wrote it is David Cross who is now a > FreeBSD committer I believe. > > Thats my recollection anyway. Unfortunately I haven't seen any recent > followups. At the time it was deemed too close to the 4.0 release. If you > do test it maybe you can prod David with the results and get it committed to > -current. On Wed, Nov 08, 2000 at 05:45:21PM +0100, Erik Trulsson wrote: > On Wed, Nov 08, 2000 at 02:53:47PM +0100, cam wrote: > > I have to use rpc.lockd on my NFS server (FreeBSD 4.0-STABLE) and I've > > notice that it is broken with this line in /etc/defaults/rc.conf: > > 113: rpc_lockd_enable="NO" # Run NFS rpc.lockd (*broken!*) if nfs_server. > > You can't have looked that hard. This question did come up earlier this > year on -questions and it wasn't difficult to find the answer searching > through the list-archives. > > Anyway, the answer is that lockd is just a dummy implementation. When the > client requests a lock rpc.lockd will just say "A lock? Sure, here you have > one." without actually locking anything. > > The only reason for running this is when you have semi-broken clients > (usually DOS/Windows based) that insist on getting a lock even though they > don't really need it. Then lockd will make them work. This is not true, any true networked system might try to modify the same file, think of mail delivery agents and Mail readers. > ( I seem to remember somebody saying that there was work in progress > writing a fully functional lockd. Has anything materialized on that > front? (A quick check doesn't show anything in the repository.)) Thanks, Axel. -- Axel.Thimm@physik.fu-berlin.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 14:45:23 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 14:45:18 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 73FE437B400; Thu, 14 Dec 2000 14:45:18 -0800 (PST) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA69128; Thu, 14 Dec 2000 17:45:15 -0500 (EST) Message-Id: <200012142245.RAA69128@cs.rpi.edu> To: Axel Thimm , Carsten Urbach Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: rpc.lockd and true NFS locks? In-Reply-To: Message from Axel Thimm of "Thu, 14 Dec 2000 23:07:56 +0100." <20001214230756.A13794@pua.domain> Date: Thu, 14 Dec 2000 17:45:15 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I pruned the Cc: list a bit... One of the email messages that you quoted has the URL for the latest development of the lockd code. As far as tests go it appears to be mostly complete (there appears to be an issue with RPC64 on little endian machines, but I have not yet had a chance to crawl through the librpc code). As for "client" vs. "server", that is quite tricky.... since WRT NFS locking they are both client and server. The "server" side is done and requires no modifcations to the kernel. However a FreeBSD kernel is still unable to acquire an NFS lock. This latter case is quite likely what your users are seeing the affects of. In the end: the code is there and available for those who want to test and play with it. It has not been committed because it is still "broken". I could do it to -current or make it a port, if someone were to tell me that it would be "ok" to do so. -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 14:55: 5 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 14:54:59 2000 Return-Path: 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 C037E37B400; Thu, 14 Dec 2000 14:54:58 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eBEMssN17539; Thu, 14 Dec 2000 14:54:54 -0800 (PST) Date: Thu, 14 Dec 2000 14:54:54 -0800 From: Alfred Perlstein To: "David E. Cross" Cc: Axel Thimm , Carsten Urbach , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: rpc.lockd and true NFS locks? Message-ID: <20001214145454.I4589@fw.wintelcom.net> References: <200012142245.RAA69128@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200012142245.RAA69128@cs.rpi.edu>; from crossd@cs.rpi.edu on Thu, Dec 14, 2000 at 05:45:15PM -0500 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * David E. Cross [001214 14:45] wrote: > I pruned the Cc: list a bit... > > One of the email messages that you quoted has the URL for the latest > development of the lockd code. As far as tests go it appears to be mostly > complete (there appears to be an issue with RPC64 on little endian machines, > but I have not yet had a chance to crawl through the librpc code). > > As for "client" vs. "server", that is quite tricky.... since WRT NFS locking > they are both client and server. The "server" side is done and requires no > modifcations to the kernel. However a FreeBSD kernel is still unable to > acquire an NFS lock. This latter case is quite likely what your users are > seeing the affects of. > > In the end: the code is there and available for those who want to test and > play with it. It has not been committed because it is still "broken". > I could do it to -current or make it a port, if someone were to tell me that > it would be "ok" to do so. I would like to see it in both -current and -stable. Please take a deep breath and keep reading. :) I think that although it's partially broken if we gave appropriate warning to the users about the experimental nature of the code we'd be doing them a favor by getting the code out so that _early adopters_ so that they can give us feedback. I do not support removing the current "fake" lockd until we've had ironed out the issues with the experimental lockd. I do not like _only_ having it in -current because then people will never consider it, I have confidence that academic installations and hobbiests would give it a shot, and who knows, maybe we'll get a knock on the door from someone who's completed the client, after all, what use is the client code without the server code? As an interim solution we could put the lockd into the system as rpc.lockd-experimental. I think had we done this over six months ago when you made the initial announcement we'd have enough feedback to begin ironing out the kinks. I want this in the user's faces, taunting and enticing them to use it and give us feedback. :) So can you commit this? -- -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 Thu Dec 14 15: 9:39 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 15:09:35 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (s014.dhcp212-24.cybercable.fr [212.198.24.14]) by hub.freebsd.org (Postfix) with ESMTP id C685537B400; Thu, 14 Dec 2000 15:09:34 -0800 (PST) Received: from free.fr (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id AAA02058; Fri, 15 Dec 2000 00:09:32 +0100 (CET) (envelope-from thierry.herbelot@free.fr) Sender: thierry.herbelot@herbelot.dyndns.org Message-ID: <3A39532C.EADF9DAE@free.fr> Date: Fri, 15 Dec 2000 00:09:32 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: rpc.lockd and true NFS locks? References: <200012142245.RAA69128@cs.rpi.edu> <20001214145454.I4589@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I've recently seen in the NetBSD 1.5 release Notes that *they* claim to have a fully functional rpc.lockd manager : "Server part of NFS locking (implemented by rpc.lockd(8)) now works." could someone have a look at what our cousins have done and perhaps import it in -current ? TfH -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 15:34:44 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 15:34:42 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id B66EF37B400; Thu, 14 Dec 2000 15:34:41 -0800 (PST) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id SAA70797; Thu, 14 Dec 2000 18:34:35 -0500 (EST) Message-Id: <200012142334.SAA70797@cs.rpi.edu> To: Alfred Perlstein Cc: "David E. Cross" , Axel Thimm , Carsten Urbach , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: rpc.lockd and true NFS locks? In-Reply-To: Message from Alfred Perlstein of "Thu, 14 Dec 2000 14:54:54 PST." <20001214145454.I4589@fw.wintelcom.net> Date: Thu, 14 Dec 2000 18:34:35 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not going to take such an action w/o the blessing of -core. :) -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 15:40:58 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 15:40:56 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id E8C7537B404; Thu, 14 Dec 2000 15:40:55 -0800 (PST) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id SAA34747; Thu, 14 Dec 2000 18:40:50 -0500 (EST) Date: Thu, 14 Dec 2000 18:40:50 -0500 (EST) From: "Matthew N. Dodd" To: Warner Losh Cc: Mike Smith , John Hay , hackers@FreeBSD.ORG Subject: Re: Support for Syba pci multi i/o card? In-Reply-To: <200012072012.NAA06519@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 7 Dec 2000, Warner Losh wrote: > I've been holding off working on this until I saw what haked out of > the bus unification work that Matt Dodd has been working on. I think > he's mostly done, but I wasn't sure enough of that to proceed. If you mean the generic resource list function stuff then yes, I'm done. That work is non-impacting and is only useful in that it provides a way to eliminate duplicated code. Or was it something else you were talking about? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 15:58:21 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 15:58:17 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from isris.pair.com (isris.pair.com [209.68.2.39]) by hub.freebsd.org (Postfix) with SMTP id 04AB237B402 for ; Thu, 14 Dec 2000 15:58:16 -0800 (PST) Received: (qmail 71717 invoked by uid 3130); 14 Dec 2000 23:58:14 -0000 Date: Thu, 14 Dec 2000 18:58:14 -0500 From: Garrett Rooney To: Thierry Herbelot Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: rpc.lockd and true NFS locks? Message-ID: <20001214185814.A69710@electricjellyfish.net> Mail-Followup-To: Garrett Rooney , Thierry Herbelot , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG References: <200012142245.RAA69128@cs.rpi.edu> <20001214145454.I4589@fw.wintelcom.net> <3A39532C.EADF9DAE@free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A39532C.EADF9DAE@free.fr>; from thierry.herbelot@free.fr on Fri, Dec 15, 2000 at 12:09:32AM +0100 Sender: rooneg@isris.pair.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 15, 2000 at 12:09:32AM +0100, Thierry Herbelot wrote: > Hello, > > I've recently seen in the NetBSD 1.5 release Notes that *they* claim to > have a fully functional rpc.lockd manager : "Server part of NFS locking > (implemented by rpc.lockd(8)) now works." > > could someone have a look at what our cousins have done and perhaps > import it in -current ? according to http://mail-index.netbsd.org/cgi-bin/projects.cgi?token=&mode=viewproj&projnum=70 code to do this was committed to netbsd on jun 7 2000. -- garrett rooney my pid is inigo montoya. rooneg@electricjellyfish.net you kill -9 my parent process. http://electricjellyfish.net/ prepare to vi. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 16:11:21 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 16:11:19 2000 Return-Path: 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 46B2437B402 for ; Thu, 14 Dec 2000 16:11:19 -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 eBF0Anw49221; Thu, 14 Dec 2000 16:10:49 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: Alfred Perlstein Cc: "David E. Cross" , Axel Thimm , Carsten Urbach , freebsd-hackers@FreeBSD.ORG Subject: Re: rpc.lockd and true NFS locks? In-Reply-To: Message from Alfred Perlstein of "Thu, 14 Dec 2000 14:54:54 PST." <20001214145454.I4589@fw.wintelcom.net> Date: Thu, 14 Dec 2000 16:10:49 -0800 Message-ID: <49217.976839049@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [-current mailing list pruned; I think -hackers is enough] > I would like to see it in both -current and -stable. I think that would be wrong, at least given the current state of the lockd stuff. First off, as David himself points out, there are issues with this code and we'd be well off dealing with those *before* committing it to -stable. I also don't think that this would be achieved simply by having more eyes on it, as you intimate, but by actually having a coherent set of code to work on and the Right Developers(tm) hacking on it. I agree with Bill Joy's assertion that all bugs are NOT shallow through having enough eyes, as Linus likes to say, but through having one or two really bright people practically killing themselves to fix them. We've also had working NFS lockd code in the BSD/OS tree on builder, along with full permission to grab it, for some time now but that hasn't made it happen because the right developers have yet to take that active an interest. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 16:19:18 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 16:19:15 2000 Return-Path: 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 B340437B400; Thu, 14 Dec 2000 16:19:14 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eBF0Id999356; Thu, 14 Dec 2000 16:18:39 -0800 (PST) (envelope-from dillon) Date: Thu, 14 Dec 2000 16:18:39 -0800 (PST) From: Matt Dillon Message-Id: <200012150018.eBF0Id999356@earth.backplane.com> To: "David E. Cross" Cc: Alfred Perlstein , Axel Thimm , Carsten Urbach , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: rpc.lockd and true NFS locks? References: <200012142334.SAA70797@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm not going to take such an action w/o the blessing of -core. :) : :-- :David Cross | email: crossd@cs.rpi.edu :Lab Director | Rm: 308 Lally Hall In regards to Jordan's message just a moment ago... you know, I *total* forgot that the BSDI working lockd code was now available. On the otherhand I know that Dave and a lot of people spent a lot of hard work on lockd, and also on the kernel-side implementation. If we were to use the BSDI code the kernel-side implementation would almost certainly be retained with only minor (if any) modification. But the experiemental lockd code would be completely replaced. David, how do you feel about that potentially occuring? Would you like to make a go of it with the BSDI lockd code on builder? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 16:28: 7 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 16:28:03 2000 Return-Path: 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 62EB937B400 for ; Thu, 14 Dec 2000 16:28:03 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eBF0RnL21027; Thu, 14 Dec 2000 16:27:49 -0800 (PST) Date: Thu, 14 Dec 2000 16:27:49 -0800 From: Alfred Perlstein To: Jordan Hubbard Cc: "David E. Cross" , Axel Thimm , Carsten Urbach , freebsd-hackers@FreeBSD.ORG Subject: Re: rpc.lockd and true NFS locks? Message-ID: <20001214162748.B19572@fw.wintelcom.net> References: <49217.976839049@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <49217.976839049@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Thu, Dec 14, 2000 at 04:10:49PM -0800 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jordan Hubbard [001214 16:11] wrote: > [-current mailing list pruned; I think -hackers is enough] > > > I would like to see it in both -current and -stable. > > I think that would be wrong, at least given the current state of > the lockd stuff. > > First off, as David himself points out, there are issues with this > code and we'd be well off dealing with those *before* committing it to > -stable. I also don't think that this would be achieved simply by > having more eyes on it, as you intimate, but by actually having a > coherent set of code to work on and the Right Developers(tm) hacking > on it. I agree with Bill Joy's assertion that all bugs are NOT > shallow through having enough eyes, as Linus likes to say, but through > having one or two really bright people practically killing themselves > to fix them. My argument against this is that giving ample warning is a far cry from the Linux mantra "release early, release often, ship the system with async files, we'll let them know how to not loose data _next_ time". Here I'm proposing that we be more than honest. The current fake lockd doesn't even do fake NLMv4 locks (although there's patches that I did do it so that it would floating around). It's also a lot harder to find bugs when you're looking at your own code versus when someone sends you a crashdump because what they were doing is able to tickle a bug you'd never assume was possible. David did say that it pretty much works, and preliminary reports from a while back started getting him some feedback which quickly died off after people forgot about the announcement. > We've also had working NFS lockd code in the BSD/OS tree on builder, > along with full permission to grab it, for some time now but that > hasn't made it happen because the right developers have yet to take > that active an interest. Actually, that would do us well for the client side, however since we don't have anyone (so far) from BSD/os to explain the intracate parts of it, I'd rather see something come in that has someone familiar with the code rather than something we'd have to grok. Then again, I should take a look at the BSD/os rpc.lockd one weekend. David, you have builder access, what do you think about the BSD/os version? -- -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 Thu Dec 14 16:32:22 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 16:32:17 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id C485737B6A0; Thu, 14 Dec 2000 16:32:13 -0800 (PST) Received: from cs.rpi.edu (bill.cs.rpi.edu [128.213.2.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id TAA72567; Thu, 14 Dec 2000 19:31:54 -0500 (EST) Message-Id: <200012150031.TAA72567@cs.rpi.edu> To: Matt Dillon Cc: "David E. Cross" , Alfred Perlstein , Axel Thimm , Carsten Urbach , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: rpc.lockd and true NFS locks? In-Reply-To: Message from Matt Dillon of "Thu, 14 Dec 2000 16:18:39 PST." <200012150018.eBF0Id999356@earth.backplane.com> Date: Thu, 14 Dec 2000 19:31:53 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Going with the lockd code on builder is great with me. The last I had looked it had some of the same issues as the lockd developed here (no handling of grace periods, etc.), so on a featureset we are even. The rpics lockd has the advantage of being known by some of us to a much greater extent than the BSDI code. _However_ the BSDI code has undergone much more testing and design work than the rpics one. Given this I think the clear choice is with the BSDI code. >sigh< now, if I wasn't always getting buried with stuff. -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 16:42: 8 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 16:42:06 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id CE22837B400 for ; Thu, 14 Dec 2000 16:42:05 -0800 (PST) Received: from cs.rpi.edu (bill.cs.rpi.edu [128.213.2.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id TAA72993; Thu, 14 Dec 2000 19:40:49 -0500 (EST) Message-Id: <200012150040.TAA72993@cs.rpi.edu> To: Alfred Perlstein Cc: Jordan Hubbard , "David E. Cross" , Axel Thimm , Carsten Urbach , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: rpc.lockd and true NFS locks? In-Reply-To: Message from Alfred Perlstein of "Thu, 14 Dec 2000 16:27:49 PST." <20001214162748.B19572@fw.wintelcom.net> Date: Thu, 14 Dec 2000 19:40:48 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > David did say that it pretty much works, and preliminary reports > from a while back started getting him some feedback which quickly > died off after people forgot about the announcement. The only confirmed bug (reported from Drew Gallatin @ Duke) appears to be a result of broken RPC64. I _thought_ I had fixed it, but it would appear not. > Actually, that would do us well for the client side, however since > we don't have anyone (so far) from BSD/os to explain the intracate > parts of it, I'd rather see something come in that has someone > familiar with the code rather than something we'd have to grok. This is kinda funny... we both make the same argument, but on different sides :) > Then again, I should take a look at the BSD/os rpc.lockd one weekend. > > David, you have builder access, what do you think about the BSD/os > version? From what I recall (it has been far too long). It was very similar in design to the epics one. Much of this is dictated via the RPC interface, but we also both picked using the various QUEUE(3) macros. I think the huge benefit with their code is greater testing, and likely better overall design. I don't recall if their code has the stuff for DOS "share" NFS access. Adding that to the rpics code was never finished due to a couple of poor assumptions early on and needing to rework it later to fit. -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 16:59:26 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 16:59:24 2000 Return-Path: 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 2E0D437B400; Thu, 14 Dec 2000 16:59:21 -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 eBF0xKs89147; Thu, 14 Dec 2000 17:59:20 -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 RAA64486; Thu, 14 Dec 2000 17:59:19 -0700 (MST) Message-Id: <200012150059.RAA64486@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: Support for Syba pci multi i/o card? Cc: Mike Smith , John Hay , hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 14 Dec 2000 18:40:50 EST." References: Date: Thu, 14 Dec 2000 17:59:19 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : On Thu, 7 Dec 2000, Warner Losh wrote: : > I've been holding off working on this until I saw what haked out of : > the bus unification work that Matt Dodd has been working on. I think : > he's mostly done, but I wasn't sure enough of that to proceed. : : If you mean the generic resource list function stuff then yes, I'm : done. That work is non-impacting and is only useful in that it provides a : way to eliminate duplicated code. : : Or was it something else you were talking about? That is the stuff I was talking about. Cool. I'll likely be lookly to use it very soon :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 21:55:18 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 21:55:15 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from security.za.net (security.za.net [196.2.146.22]) by hub.freebsd.org (Postfix) with ESMTP id 7503437B400 for ; Thu, 14 Dec 2000 21:51:17 -0800 (PST) Received: from localhost (lists@localhost) by security.za.net (8.9.3/8.9.3) with ESMTP id HAA94268 for ; Fri, 15 Dec 2000 07:51:08 +0200 (SAST) (envelope-from lists@security.za.net) Date: Fri, 15 Dec 2000 07:51:08 +0200 (SAST) From: Lists Account To: hackers@freebsd.org Subject: NOS-TUN / Natd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, Just a quick question out of interests sake, I was setting up nos-tunnels yesterday, and I had the tunnel functioning 100% perfectly, however I could not get it to NAT the remote side of the tunnel, until I put an ipfw divert 8668 ip from any to any via any statement in my firewall config. What I first tried, and this failed was to divert all incoming packets coming into tun0 and nat them going out, however the system didnt even attempt to nat packets when I tried this (I used the follow ipfw statements to try it: ipfw add 1 divert 8668 ip from any to any via tun0 (This did nothing for the packets, didnt even touch them) ipfw add 1 divert 8668 ip from any to any in recv tun0 (Try and divert anything coming in via tun0, didnt even attempt to nat these packets either). Does anyone have any idea WHY I would have to divert ALL packets instead of just those on tun0 to get the nat to work? Any help would be appreciated Thanks Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 22:54:49 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 22:54:47 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by hub.freebsd.org (Postfix) with ESMTP id 3B13B37B400 for ; Thu, 14 Dec 2000 22:54:47 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id WAA02703; Thu, 14 Dec 2000 22:56:00 -0800 Date: Thu, 14 Dec 2000 22:56:00 -0800 From: Kris Kennaway To: Peter Jeremy Cc: hackers@FreeBSD.ORG, sheldonh@uunet.co.za, arnold@skeeve.com Subject: Re: BSD random for Alpha? Message-ID: <20001214225600.F2040@citusc.usc.edu> References: <20001204092348.A92196@gsmx07.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001204092348.A92196@gsmx07.alcatel.com.au>; from peter.jeremy@alcatel.com.au on Mon, Dec 04, 2000 at 09:23:48AM +1100 Sender: kris@citusc.usc.edu Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 04, 2000 at 09:23:48AM +1100, Peter Jeremy wrote: > >Hi. I've switched to the new random.c you sent me for gawk. My > >Linux/Alpha Guru reports that the code in it assumes that sizeof(long) > >is always 4, and one particular test doesn't "look" very random on > >the Alpha. > > > >My question is, is there a better version of random that can deal > >with both 32 and 64 bit systems in the same source code? Would > >the NetBSD people maybe have such a thing? > > Try a Fibonacci-sequence random number generator (they're mentioned > in Knuth). The general form is: > > X[n] = (X[n-j] + X[n-k]) mod m I think this would be bad - for a general-purpose language like awk we should be using a cryptographic-strength PRNG like arc4random() or /dev/urandom so that people can use it for any purpose. 64-bit cleanliness can presumably be taken care of easily enough. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 14 23:39:18 2000 From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 23:39:16 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a13b063.neo.rr.com [204.210.197.63]) by hub.freebsd.org (Postfix) with ESMTP id EAAAA37B400 for ; Thu, 14 Dec 2000 23:39:15 -0800 (PST) Received: from localhost (mike@localhost) by jason.argos.org (8.10.1/8.10.1) with ESMTP id eBF7XKp08342; Fri, 15 Dec 2000 02:33:20 -0500 Date: Fri, 15 Dec 2000 02:33:20 -0500 (EST) From: Mike Nowlin To: Lists Account Cc: hackers@FreeBSD.ORG Subject: Re: NOS-TUN / Natd 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 > Just a quick question out of interests sake, I was setting up nos-tunnels > yesterday, and I had the tunnel functioning 100% perfectly, however I > could not get it to NAT the remote side of the tunnel, until I put an ipfw > divert 8668 ip from any to any via any statement in my firewall config. > ipfw add 1 divert 8668 ip from any to any in recv tun0 My first thought is to do something like: ipfw add 1 allow ip from any to any in via tun0 ipfw add 2 divert 8668 ip from 1.2.3.4 to any ...where 1.2.3.4 is an IP on the remote end of the tunnel - send a few packets from 1.2.3.4, then do an "ipfw s" to see if they're hitting that rule. That should help figure out if it's a problem with the tunnel code, or a problem with your ipfw rules. (ipfw can bring up some interesting situations, especially with NAT.) mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 1:39:19 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 01:39:18 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 3AAB637B402 for ; Fri, 15 Dec 2000 01:39:17 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id eBF9dAL83193; Fri, 15 Dec 2000 10:39:10 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Fri, 15 Dec 2000 10:42:45 +0100 (CET) From: Martin Blapp To: freebsd-hackers@FreeBSD.ORG Cc: bright@wintelcom.net, crossd@cs.rpi.edu Subject: Import and merge of TI-RPC from NetBSD 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'd like to import the NetBSD RPC-Interface, based on Sun's TI-RPC code. This will made available the TI-RPC features and generated code with rpcgen will compile then without problems. The code remains backword compatible, there ar no changes needed in the codebase (therefore some are recomanded). The code I 'maintain' (mount utilities) is already patched in my codebase. I've started with merging and adapting and I'd like to have your tips and opinions. Martin PS: this fixes maybe also the issues with 64-Bit RPC code of the rpc-lockd david wrote ... Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 1:54:48 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 01:54:47 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from gwdu60.gwdg.de (gwdu60.gwdg.de [134.76.98.60]) by hub.freebsd.org (Postfix) with ESMTP id 2C22D37B400 for ; Fri, 15 Dec 2000 01:54:46 -0800 (PST) Received: from localhost (kheuer@localhost) by gwdu60.gwdg.de (8.11.1/8.9.3) with ESMTP id eBF9shx10461 for ; Fri, 15 Dec 2000 10:54:44 +0100 (CET) (envelope-from kheuer@gwdu60.gwdg.de) Date: Fri, 15 Dec 2000 10:54:43 +0100 (CET) From: Konrad Heuer To: freebsd-hackers@freebsd.org Subject: Why does lpd cause a lot of DNS traffic? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While solving some special remote printing problems I saw (4.2-STABLE) that lpd verifies printer access from a remote host by a lot of name resolution requests (my /etc/hosts.lpd has more than 300 entries). When verifying a host lpd scans hosts.lpd from the first line to the first matching line *not* by string comparison (hostname) but by requesting a name resolution for each entry (line by line) and comparing the INET address. For a heavily loaded printer server (as mine is) this seems not be a good idea ... but maybe there's a good reason to to this? Regards Konrad Heuer Personal Bookmarks: Gesellschaft f=FCr wissenschaftliche Datenverarbeitung mbH G=D6ttingen http://www.freebsd.org Am Fa=DFberg, D-37077 G=D6ttingen http://www.daemonnews.o= rg Deutschland (Germany) kheuer@gwdu60.gwdg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 2:51: 9 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 02:51:08 2000 Return-Path: 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 618A237B400 for ; Fri, 15 Dec 2000 02:51:07 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 15 Dec 2000 10:51:05 +0000 (GMT) Date: Fri, 15 Dec 2000 10:51:04 +0000 From: David Malone To: Konrad Heuer Cc: freebsd-hackers@freebsd.org Subject: Re: Why does lpd cause a lot of DNS traffic? Message-ID: <20001215105104.A73285@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 kheuer@gwdu60.gwdg.de on Fri, Dec 15, 2000 at 10:54:43AM +0100 Sender: dwmalone@maths.tcd.ie Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 15, 2000 at 10:54:43AM +0100, Konrad Heuer wrote: > For a heavily loaded printer server (as mine is) this seems not be a good > idea ... but maybe there's a good reason to to this? I presume this is so that you can list machine aliases in the hosts.lpd file, and to avoid issues with machines that may have more than one interface. One solution would be to run a caching name server on the print server and point resolv.conf at 127.0.0.1. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 3: 3:49 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 03:03:47 2000 Return-Path: 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 5F75A37B400 for ; Fri, 15 Dec 2000 03:03:46 -0800 (PST) Received: from [194.207.93.139] by gate.trident-uk.co.uk for dwmalone@maths.tcd.ie id KAA15997; Fri Dec 15 10:55:17 2000 Organization: Psi-Domain Ltd. Subject: Re: Why does lpd cause a lot of DNS traffic? Date: Fri, 15 Dec 2000 10:57:43 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <20001215105104.A73285@walton.maths.tcd.ie> In-Reply-To: <20001215105104.A73285@walton.maths.tcd.ie> MIME-Version: 1.0 Message-Id: <0012151100330S.01649@freefire.psi-domain.co.uk> Content-Transfer-Encoding: 8bit To: David Malone 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 On Fri, 15 Dec 2000, you wrote: > On Fri, Dec 15, 2000 at 10:54:43AM +0100, Konrad Heuer wrote: > > For a heavily loaded printer server (as mine is) this seems not be a good > > idea ... but maybe there's a good reason to to this? > > I presume this is so that you can list machine aliases in the > hosts.lpd file, and to avoid issues with machines that may have > more than one interface. One solution would be to run a caching > name server on the print server and point resolv.conf at 127.0.0.1. > You could also manually add them to /etc/hosts - but this will be a bit tedious when you have a lot of machines. Maybe list IP addresses in /etc/hosts.lpd instead of hostnames? This could cause alot of reverse lookups though. > David. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- 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 ===================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 3:33:31 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 03:33:29 2000 Return-Path: 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 6AFD437B400 for ; Fri, 15 Dec 2000 03:33:28 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 15 Dec 2000 11:33:27 +0000 (GMT) To: heckfordj@psi-domain.co.uk Cc: freebsd-hackers@freebsd.org Subject: Re: Why does lpd cause a lot of DNS traffic? In-reply-to: Your message of "Fri, 15 Dec 2000 10:57:43 GMT." <0012151100330S.01649@freefire.psi-domain.co.uk> X-Request-Do: Date: Fri, 15 Dec 2000 11:33:26 +0000 From: David Malone Message-ID: <200012151133.aa47244@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You could also manually add them to /etc/hosts - but this will be a bit tediou > when you have a lot of machines. Maybe list IP addresses in /etc/hosts.lpd > instead of hostnames? This could cause alot of reverse lookups though. Another, slightly strange, way to do it would be to create a set of DNS A records, all with the same name but with A records pointing to all the hosts alows to use the printers. Then you could just put this entry in hosts.lpd ;-) David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 3:42:52 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 03:42:51 2000 Return-Path: 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 38FCC37B402 for ; Fri, 15 Dec 2000 03:42:51 -0800 (PST) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=danny) by cs.huji.ac.il with esmtp (Exim 3.20 #1) id 146tGD-0004cY-00 for freebsd-hackers@FreeBSD.ORG; Fri, 15 Dec 2000 13:42:49 +0200 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: freebsd-hackers@FreeBSD.ORG Subject: diskless/pxe boot Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Dec 2000 13:42:49 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all, I can't get the pxe/dhcp to work when it's 100Mbit Ethernet, it works fine when it's 10Mbit. Actually a newer Intel MB just succeeded, but 99% of the pxe enabled cards fail at 100Mbit. from sniffing the net the broadcast dhcp request does not make it. it does not help to set the switch to 'no auto negotiation', ie fixed 100 (full or half duplex). Is there any success out there? if so, what combination of NIC and switch? 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 15 3:51: 2 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 03:51:00 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.189]) by hub.freebsd.org (Postfix) with SMTP id E86E737B400 for ; Fri, 15 Dec 2000 03:50:54 -0800 (PST) Received: (qmail 18365 invoked by uid 1000); 15 Dec 2000 11:50:00 -0000 Date: Fri, 15 Dec 2000 13:50:00 +0200 From: Peter Pentchev To: Jamie Heckford Cc: David Malone , freebsd-hackers@freebsd.org Subject: Re: Why does lpd cause a lot of DNS traffic? Message-ID: <20001215134959.D7799@ringworld.oblivion.bg> Mail-Followup-To: Jamie Heckford , David Malone , freebsd-hackers@freebsd.org References: <20001215105104.A73285@walton.maths.tcd.ie> <0012151100330S.01649@freefire.psi-domain.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <0012151100330S.01649@freefire.psi-domain.co.uk>; from heckfordj@psi-domain.co.uk on Fri, Dec 15, 2000 at 10:57:43AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 15, 2000 at 10:57:43AM +0000, Jamie Heckford wrote: > On Fri, 15 Dec 2000, you wrote: > > On Fri, Dec 15, 2000 at 10:54:43AM +0100, Konrad Heuer wrote: > > > For a heavily loaded printer server (as mine is) this seems not be a good > > > idea ... but maybe there's a good reason to to this? > > > > I presume this is so that you can list machine aliases in the > > hosts.lpd file, and to avoid issues with machines that may have > > more than one interface. One solution would be to run a caching > > name server on the print server and point resolv.conf at 127.0.0.1. > > > > You could also manually add them to /etc/hosts - but this will be a bit tedious > when you have a lot of machines. Maybe list IP addresses in /etc/hosts.lpd > instead of hostnames? This could cause alot of reverse lookups though. Adding hosts.lpd hosts to /etc/hosts could easily be automated; something like: while read host; do echo `gh -a $host` $host; done < /etc/hosts.lpd using the gh resolver query tool from the net/ghtool port; add '>> /etc/hosts' to the end, then do a sort on /etc/hosts and scan for duplicates.. Something like: awk '{print $1}' /etc/hosts | sort | uniq -c | \ egrep -v '^[[:space:]]+1[[:space:]]' ..could do the trick :) G'luck, Peter -- This sentence contradicts itself - or rather - well, no, actually it doesn't! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 4:31: 2 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 04:31:00 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id B3E8E37B400 for ; Fri, 15 Dec 2000 04:30:59 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id eBFCUv297718 for ; Fri, 15 Dec 2000 13:30:58 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Fri, 15 Dec 2000 13:34:32 +0100 (CET) From: Martin Blapp To: freebsd-hackers@FreeBSD.ORG Subject: Re: Import and merge of TI-RPC from NetBSD 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 forgot a link ... http://www.as400.ibm.com/developer/tirpc/ Cheers: Martin Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 5: 2: 8 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 05:02:07 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from roura.ac.upc.es (roura.ac.upc.es [147.83.33.10]) by hub.freebsd.org (Postfix) with ESMTP id 48D4F37B402 for ; Fri, 15 Dec 2000 05:02:02 -0800 (PST) Received: from ac.upc.es (fonoll.ac.upc.es [147.83.32.14]) by roura.ac.upc.es (8.11.0/8.11.0) with ESMTP id eBFD4eO10510 for ; Fri, 15 Dec 2000 14:04:40 +0100 (MET) Sender: oscar@ac.upc.es Message-ID: <3A3A16E8.DA626B1A@ac.upc.es> Date: Fri, 15 Dec 2000 14:04:40 +0100 From: Oscar I Lepe Organization: DAC/UPC X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: es, en MIME-Version: 1.0 To: hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 5:35:43 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 05:35:40 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from hallie.shoalhaven.net.au (hallie.shoalhaven.net.au [202.139.20.1]) by hub.freebsd.org (Postfix) with ESMTP id B8A3837B402 for ; Fri, 15 Dec 2000 05:35:38 -0800 (PST) Received: from sabacc.jaster.shoalhaven.net.au (om17.shoalhaven.net.au [202.139.20.17]) by hallie.shoalhaven.net.au (8.8.5/8.8.5) with SMTP id AAA09383 for ; Sat, 16 Dec 2000 00:35:35 +1100 (EST) From: Joshua Silver Reply-To: jaster@shoalhaven.net.au To: freebsd-hackers@FreeBSD.ORG Subject: USB Mouse + Dual P3 Date: Sat, 16 Dec 2000 00:15:50 +1100 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00121600331904.00588@sabacc.jaster.shoalhaven.net.au> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had FreeBSD 4.1 running on a Dual Celeron system for some time now with a MS USB ...... No probs. Just got a new system in the last week, and am running FreeBSD 4.2 It's on a MSI 694D-Pro Motherboard, and has had one CPU in it for the last week, the USB mouse ran fine .... Got the second CPU today, and then rebuilt the kernel with : options SMP options APIC_IO After restarting, the USB mouse did't work .... restart with the old kernel (the only change is those two lines) .... mouse works .... There is also a message on boot up that says : moused: unable to open /dev/ums0: Device busy I get this with both kernels, so it may have nothing to do with the prob since the mouse still works in the single CPU format .... Thanks in advance for the help. Josh. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 7:37: 2 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 07:37:00 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 91F7037B400 for ; Fri, 15 Dec 2000 07:37:00 -0800 (PST) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JXQNENJYI00016LQ@research.kpn.com> for hackers@FreeBSD.ORG; Fri, 15 Dec 2000 16:36:58 +0100 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Fri, 15 Dec 2000 16:36:57 +0100 Content-return: allowed Date: Fri, 15 Dec 2000 16:36:57 +0100 From: "Koster, K.J." Subject: RE: kqueue microbenchmark results To: 'Wes Peters' , Jonas Bulow Cc: hackers@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7ABF@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > A simple way to keep the kernel simple: > > > http://linuxtoday.com/news_story.php3?ltsn=2000-12-09-013-20-NW-GN-KN > > Device drivers in Perl. What a spectacularly bad idea. ;^) > That's what people used to say about writing kernels in C. Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 8: 7:50 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 08:07:48 2000 Return-Path: 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 0672F37B400 for ; Fri, 15 Dec 2000 08:07:48 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eBFG7ju13768; Fri, 15 Dec 2000 08:07:45 -0800 (PST) Date: Fri, 15 Dec 2000 08:07:45 -0800 From: Alfred Perlstein To: Martin Blapp Cc: freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Import and merge of TI-RPC from NetBSD Message-ID: <20001215080745.K19572@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 mb@imp.ch on Fri, Dec 15, 2000 at 10:42:45AM +0100 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Martin Blapp [001215 01:39] wrote: > > Hi, > > I'd like to import the NetBSD RPC-Interface, based on Sun's TI-RPC code. > > This will made available the TI-RPC features and generated code with > rpcgen will compile then without problems. The code remains backword > compatible, there ar no changes needed in the codebase (therefore some > are recomanded). The code I 'maintain' (mount utilities) is already > patched in my codebase. > > I've started with merging and adapting and I'd like to have your > tips and opinions. I'd like to see this happen, if you come across any hurdles with the code feel free to email me about it. > PS: this fixes maybe also the issues with 64-Bit RPC code of > the rpc-lockd david wrote ... Cool. -- -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 15 8:44: 2 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 08:44:00 2000 Return-Path: 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 A0BA037B400 for ; Fri, 15 Dec 2000 08:43:59 -0800 (PST) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 146xxD-0004a6-00; Fri, 15 Dec 2000 16:43:31 +0000 Date: Fri, 15 Dec 2000 16:43:31 +0000 To: Dennis Cc: hackers@freebsd.org Subject: Re: cp and cpio using boot disk Message-ID: <20001215164331.A17593@firedrake.org> References: <5.0.0.25.0.20001214121201.01f82650@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.0.25.0.20001214121201.01f82650@mail.etinc.com>; from dennis@etinc.com on Thu, Dec 14, 2000 at 12:13:16PM -0500 From: void Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 14, 2000 at 12:13:16PM -0500, Dennis wrote: > > It seems that cp fails badly when used on a system booted by a boot floppy > (such as the install floppy). cpio seems to work ok. > > What is the reason for this? What's the failure mode? -- 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 Fri Dec 15 10: 5:58 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 10:05:56 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id AE4C037B400 for ; Fri, 15 Dec 2000 10:05:55 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id B74FE57458; Fri, 15 Dec 2000 12:06:10 -0600 (CST) Date: Fri, 15 Dec 2000 12:06:10 -0600 From: "Michael C . Wu" To: "Koster, K.J." Cc: 'Wes Peters' , Jonas Bulow , hackers@FreeBSD.ORG Subject: Re: kqueue microbenchmark results Message-ID: <20001215120610.A40179@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <59063B5B4D98D311BC0D0001FA7E4522026D7ABF@l04.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D7ABF@l04.research.kpn.com>; from K.J.Koster@kpn.com on Fri, Dec 15, 2000 at 04:36:57PM +0100 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: keichii@peorth.iteration.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 15, 2000 at 04:36:57PM +0100, Koster, K.J. scribbled: | > http://linuxtoday.com/news_story.php3?ltsn=2000-12-09-013-20-NW-GN-KN | > Device drivers in Perl. What a spectacularly bad idea. ;^) | That's what people used to say about writing kernels in C. There is a difference between (compiling C device driver module and loading into an ASM kernel) and (interpreting a Perl device driver that uses userland tools.) Confusing kernel and userland results in WIN32 API+Integrated Exchange Server crashes. Or think of the linux kernel httpd project. I cannot think of that many reasons against keeping kernel in kernel, and userland in userland (if any). Latency, locking, security, and performance all goes agains this. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 10:13:51 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 10:13:48 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id C80CC37B400 for ; Fri, 15 Dec 2000 10:13:47 -0800 (PST) Received: from astra.domix.de (dial-194-8-196-29.netcologne.de [194.8.196.29]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id TAA26372 for ; Fri, 15 Dec 2000 19:13:45 +0100 (MET) Received: (from dr@localhost) by astra.domix.de (8.11.1/8.11.0) id eBFIGgu09085 for hackers@freebsd.org; Fri, 15 Dec 2000 19:16:42 +0100 (CET) (envelope-from dr) Date: Fri, 15 Dec 2000 19:16:42 +0100 From: Dominik Rothert To: hackers@freebsd.org Subject: vidcontrol VESA_800x600 Message-ID: <20001215191641.A9063@astra.local> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="W/nzBZO5zC0uMSeA" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: dr@astra.domix.de Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi there, I was wondering why VESA_800x600 refreshes to 80x25 and figured out, that size[0] = 80; /* columns */ size[1] = 25; /* rows */ for mode SW_VESA_800x600 (line 319 of src/usr.sbin/vidcontrol.c). A screen resolution of 800x600 would make size[0] = 100; /* columns */ size[1] = 37; /* rows */ Is there any reason why SW_VESA_800x600 is nothing else than 80x25 at this time? I've attached a diff for patching vidcontrol.c to this mail. Best wishes, Dominik. -- /* Dominik Rothert | dr@astorit.com * * A S T O R I T | http://www.astorit.com/ * * Hohenzollernring 52 | fon +49-221-251440 * * 50672 Cologne, Germany | fax +49-221-251443 */:wq! --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="vidcontrol.c.patch" --- vidcontrol.c.orig Fri Dec 15 19:03:02 2000 +++ vidcontrol.c Fri Dec 15 18:49:29 2000 @@ -317,8 +317,8 @@ if (ioctl(0, mode, NULL) < 0) warn("cannot set videomode"); if (mode == SW_VESA_800x600) { - size[0] = 80; /* columns */ - size[1] = 25; /* rows */ + size[0] = 100; /* columns */ + size[1] = 37; /* rows */ size[2] = 16; /* font size */ if (ioctl(0, KDRASTER, size)) { ioerr = errno; --W/nzBZO5zC0uMSeA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 10:27:43 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 10:27:41 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 4961737B400 for ; Fri, 15 Dec 2000 10:27:39 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 0B7CE57458; Fri, 15 Dec 2000 12:27:53 -0600 (CST) Date: Fri, 15 Dec 2000 12:27:52 -0600 From: "Michael C . Wu" To: Gustavo Vieira Goncalves Coelho Rios Cc: hackers@freebsd.org Subject: Re: very big mail spool directory Message-ID: <20001215122752.C40179@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <3A368F8C.1918684F@ifour.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A368F8C.1918684F@ifour.com.br>; from gustavo@ifour.com.br on Tue, Dec 12, 2000 at 08:50:20PM +0000 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: keichii@peorth.iteration.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 12, 2000 at 08:50:20PM +0000, Gustavo Vieira Goncalves Coelho Rios scribbled: | i am planning a very big email server, currently i am planning for about | 8*2^16 users. [snip] | What you wizard have to say about my approach? Why would you not want to have a distributed server in this case? I would distribute the load between 2-4 servers that will easily handle the load, creating vastly greater fault tolerance and redundancy. Incoming SMTP go to several MX'es and into a database server. The master database server would have a slave db server that constantly syncs its files from the master. In the case of primary db server failure, slave becomes the master transparently by a simple ifconfig(8) command (probably some other small config changes that can be automated by a shell script). The db servers cater to POP/IMAP servers. Outgoing SMTP is round robined and should not be too much trouble. So, for projects with less funding, a 3 server distributed system would be much more preferable. If your organization has 8*2^16 servers, it certainly can afford 3 celeron/k6/pIII boxes. (Of course, some people prefer to buy Sun Enterprise10000's...) -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 10:55:28 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 10:55:25 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 1328237B400 for ; Fri, 15 Dec 2000 10:55:22 -0800 (PST) Received: from localhost (IDENT:RT+mvA6v5ig8DzUYjzACXhaOU5X1Wov/I7w+XFefDJ2r/CX+KQBuOJW1X8RnbQxa@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.1/8.11.1/peace) with ESMTP/inet6 id eBFIqNE25181; Sat, 16 Dec 2000 03:52:23 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sat, 16 Dec 2000 03:52:19 +0900 (JST) Message-Id: <20001216.035219.74733307.ume@mahoroba.org> To: mb@imp.ch Cc: freebsd-hackers@FreeBSD.ORG, bright@wintelcom.net, crossd@cs.rpi.edu Subject: Re: Import and merge of TI-RPC from NetBSD From: Hajimu UMEMOTO In-Reply-To: References: X-Mailer: xcite1.20> Mew version 1.95b38 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT 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 Fri, 15 Dec 2000 10:42:45 +0100 (CET) >>>>> Martin Blapp said: mb> I'd like to import the NetBSD RPC-Interface, based on Sun's TI-RPC code. Oh, it's great! I heared TI-RPC is required to support IPv6 for NFS. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 13:13:59 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 13:13:57 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mailer.progressive-comp.com (docs3.abcrs.com [63.238.77.222]) by hub.freebsd.org (Postfix) with ESMTP id 365C937B400 for ; Fri, 15 Dec 2000 13:13:57 -0800 (PST) Received: (from docs@localhost) by mailer.progressive-comp.com with id QAA13296; Fri, 15 Dec 2000 16:13:23 -0500 Date: Fri, 15 Dec 2000 16:13:23 -0500 Message-Id: <200012152113.QAA13296@mailer.progressive-comp.com> From: Hank Leininger Errors-To: hlein@progressive-comp.com Reply-To: Hank Leininger To: freebsd-hackers@FreeBSD.ORG Subject: Re: Kyxtech: freebsd outsniffed by wintendo!!?!? Cc: "Fulvio Risso" Cc: tcpdump-workers@sandelman.ottawa.on.ca X-Shameless-Plug: Check out http://marc.theaimsgroup.com/ X-Warning: This mail posted via a web gateway at marc.theaimsgroup.com X-Warning: Report any violation of list policy to abuse@progressive-comp.com X-Posted-By: Hank Leininger Sender: docs@mailer.progressive-comp.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-12-14, "Fulvio Risso" wrote: > Buffer sizes > We did not make any test about creating 1MB buffers. However our > architecture does not have the problem that "large buffer" = "large > time used to transfer this buffer to user level" because we are able to [snip] > Context switches > Are kept the lowest, because several packets can be transferred at the > same time. Erm... but if you've not enlarged the buffer from the default, you've not kept context switches "at the lowest." Sure, there isn't one switch per packet. But there could be far more packets per switch if you'd enlarged the buffer (note there's some diminishing returns as you exceed different cachesize boundaries, i.e. performance will actually drop when you working set gets too big for L2 cache, etc). > UFS filesystem > We used FAT to strore packets because the UFS filesystem was on a > second hard disk, so that the disk could have made some difference. We > can reinstall BSD and repeat the test. We'll do that for sure. I suspect this will dramatically change things. Helping a friend who was working on 100mbit sustained capture on FreeBSD, I realized he was writing to a FAT filesystem (on removable drives) for ease of portability. I suggested he switch to UFS; he did so and realized a 200% performance improvement (3x). This was before softupdates, which should make things even better. FAT is an awful filesystem to begin with, and I'd not be surprised if its implementation in FreeBSD isn't as good as it could be (because, why bother?). I'm afraid, this one simple fact completely distorts your results. Of course, even if you switch to UFS it won't quite be apples-to-apples. But at least, you will be using the native/best/most appropriate filesystem for each platform you're testing. Right now, whenever you start writing packets to disk under FreeBSD, you're testing how much FAT blows, and not much else. -- Hank Leininger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 13:22:36 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 13:22:34 2000 Return-Path: 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 B935A37B400 for ; Fri, 15 Dec 2000 13:22:32 -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 QAA60445; Fri, 15 Dec 2000 16:23:35 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20001215162446.01f14c60@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Fri, 15 Dec 2000 16:25:58 -0500 To: void From: Dennis Subject: Re: cp and cpio using boot disk Cc: hackers@freebsd.org In-Reply-To: <20001215164331.A17593@firedrake.org> References: <5.0.0.25.0.20001214121201.01f82650@mail.etinc.com> <5.0.0.25.0.20001214121201.01f82650@mail.etinc.com> 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 At 11:43 AM 12/15/2000, you wrote: >On Thu, Dec 14, 2000 at 12:13:16PM -0500, Dennis wrote: > > > > It seems that cp fails badly when used on a system booted by a boot floppy > > (such as the install floppy). cpio seems to work ok. > > > > What is the reason for this? > >What's the failure mode? binaries copied with cp from a mounted zip drive to a hard drive fail to work. When copied with cpio they are ok. We havent tracked the exact reason. Random bus faults and other sigerrors. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 16:38:53 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 16:38:51 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from goliath.cnchost.com (goliath.cnchost.com [207.155.252.47]) by hub.freebsd.org (Postfix) with ESMTP id 8A66437B402 for ; Fri, 15 Dec 2000 16:38:51 -0800 (PST) Received: from buffy (w072.z064003114.lax-ca.dsl.cnc.net [64.3.114.72]) by goliath.cnchost.com id TAA16776; Fri, 15 Dec 2000 19:38:50 -0500 (EST) [ConcentricHost SMTP Relay 1.10] Errors-To: From: "SteveB" To: Subject: kernel type Date: Fri, 15 Dec 2000 16:40:31 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20001115133210.I39755@wantadilla.lemis.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for such a basic question, but I have been looking and can't find the answer. Is FreeBSD as microkernel or monolithic kernel like Linux? Can someone point me to the answer/ TIA Steve B. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 16:48:41 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 16:48:39 2000 Return-Path: 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 92A5937B400 for ; Fri, 15 Dec 2000 16:48:38 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBG0mNE35852; Fri, 15 Dec 2000 16:48:23 -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: Fri, 15 Dec 2000 16:48:38 -0800 (PST) From: John Baldwin To: SteveB Subject: RE: kernel type Cc: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Dec-00 SteveB wrote: > > Sorry for such a basic question, but I have been looking and can't > find the answer. Is FreeBSD as microkernel or monolithic kernel like > Linux? Can someone point me to the answer/ Well, it's a monolithic kernel with a built in run-time linker that allows you to load and unload parts of the kernel on the fly while the system is running. However, you can only unload something that was loaded from a module and not the main kernel file itself. > TIA > Steve B. -- 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 Fri Dec 15 16:50:34 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 16:50:33 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.jantar.org (mycenae.jantar.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id C341837B400 for ; Fri, 15 Dec 2000 16:50:30 -0800 (PST) Received: from mycenae.jantar.org (patrykz@localhost [127.0.0.1]) by mycenae.jantar.org (8.9.3/8.9.3) with ESMTP id LAA97623; Sat, 16 Dec 2000 11:50:22 +1100 (EST) (envelope-from patrykz@mycenae.jantar.org) Message-Id: <200012160050.LAA97623@mycenae.jantar.org> From: Patryk Zadarnowski To: "SteveB" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: kernel type In-Reply-To: Message from "SteveB" of "Fri, 15 Dec 2000 16:40:31 -0800." Date: Sat, 16 Dec 2000 11:50:22 +1100 Sender: patrykz@mycenae.jantar.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 15 Dec 2000, "SteveB" wrote: SteveB> Sorry for such a basic question, but I have been looking and can't SteveB> find the answer. Is FreeBSD as microkernel or monolithic kernel like SteveB> Linux? Can someone point me to the answer/ It's a monolithic kernel, like Linux and all other mainstream UNIX flavours except for OSF1 (ie. Digital UNIX or True64), which is based on a hacked-up version of the MACH microkernel. Even then, most microkernel researchers won't consider OSF1 a microkernel, as Digital (now Compaq) worked around the MACH problem (which is an i-cache hog) by moving much functionality back into the kernel. Now that I think of it, there aren't many commercial microkernel systems out there with the possible exception of QNX and lots of little embedded toys. NT, sometimes claimed to be a microkernel, is far from it. Rather, it's simply another reasonably-well structured kernel. With 300+ system calls in the nucleus, the NT kernel handles just about everything except for major GUI tasks. Pat. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Patryk Zadarnowski University of New South Wales School of Computer Science and Engineering -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 19: 9:41 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 19:09:39 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from lox.sandelman.ottawa.on.ca (lox.sandelman.ottawa.on.ca [209.151.24.2]) by hub.freebsd.org (Postfix) with ESMTP id 13DFF37B404 for ; Fri, 15 Dec 2000 19:09:35 -0800 (PST) Received: from nox.sandelman.ottawa.on.ca (nox.sandelman.ottawa.on.ca [209.151.24.6]) by lox.sandelman.ottawa.on.ca (8.8.7/8.8.8) with ESMTP id WAA15065; Fri, 15 Dec 2000 22:09:14 -0500 (EST) Received: from sandelman.ottawa.on.ca ([2002:401a:9bfe:3:2a0:24ff:feac:5c52]) by nox.sandelman.ottawa.on.ca (8.11.0/8.11.0) with ESMTP id eBCFw8k07410 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Tue, 12 Dec 2000 07:58:09 -0800 (PST) Received: by sandelman.ottawa.on.ca (8.11.0/8.11.0) id eBCFoJ807295; Tue, 12 Dec 2000 10:50:19 -0500 (EST) Received: from spammie.svbug.com (mg131-025.ricochet.net [204.179.131.25]) by lox.sandelman.ottawa.on.ca (8.8.7/8.8.8) with ESMTP id JAA12429 for ; Tue, 12 Dec 2000 09:37:45 -0500 (EST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id GAA03155; Tue, 12 Dec 2000 06:36:07 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200012121436.GAA03155@spammie.svbug.com> Date: Tue, 12 Dec 2000 06:36:04 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: Fwd: kyxtech: freebsd outsniffed by wintendo !!?!? To: dr@kyx.net Cc: tcpdump-workers@tcpdump.org, ethereal-dev@ethereal.com, snort-devel@lists.sourceforge.net, freebsd-hackers@FreeBSD.ORG, tech@openbsd.org In-Reply-To: <0012072118150Q.09615@smp.kyx.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: mcr@sandelman.ottawa.on.ca Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 7 Dec, Dragos Ruiu wrote: > > (Hurm.... Wintendo outperforming unix???!?? Something's > improper about this, and it ought to be fixed... :-) > Comments? Other OS numbers: more recent > FreeBSD versions? Solaris? Tru64? Optimization > patches? Can those OO MSDN lobotomies actually > be good things? Hurm... The Italian gauntlet has > been thrown down.... --dr :-) > > url: http://netgroup-serv.polito.it/winpcap/docs/performance.htm > I'm not sure if we could find someone of this caliber to run the test again. For once I must agree with Mike Smith ;-) Clearly the page: http://netgroup-serv.polito.it/winpcap/ says, "partially sponsored by MicroSoft Research". IMHO, it bait -- bad bait at that. IMO, M$ has found some hole in the FreeBSD kernel and is intending to expose it. Although I suspect the hole's been cleaned up by now by core. If Terry Lambert can chimes in, I know we might get some real answers. I'm not convinced by this M$ agent. Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 19:10:35 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 19:10:33 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from lox.sandelman.ottawa.on.ca (lox.sandelman.ottawa.on.ca [209.151.24.2]) by hub.freebsd.org (Postfix) with ESMTP id 9E87937B400 for ; Fri, 15 Dec 2000 19:10:31 -0800 (PST) Received: from nox.sandelman.ottawa.on.ca (nox.sandelman.ottawa.on.ca [209.151.24.6]) by lox.sandelman.ottawa.on.ca (8.8.7/8.8.8) with ESMTP id WAA15256; Fri, 15 Dec 2000 22:10:23 -0500 (EST) Received: from sandelman.ottawa.on.ca ([2002:401a:9bfe:3:2a0:24ff:feac:5c52]) by nox.sandelman.ottawa.on.ca (8.11.0/8.11.0) with ESMTP id eBCFw8k07410 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Tue, 12 Dec 2000 07:58:09 -0800 (PST) Received: by sandelman.ottawa.on.ca (8.11.0/8.11.0) id eBCFoJ807295; Tue, 12 Dec 2000 10:50:19 -0500 (EST) Received: from spammie.svbug.com (mg131-025.ricochet.net [204.179.131.25]) by lox.sandelman.ottawa.on.ca (8.8.7/8.8.8) with ESMTP id JAA12429 for ; Tue, 12 Dec 2000 09:37:45 -0500 (EST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id GAA03155; Tue, 12 Dec 2000 06:36:07 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200012121436.GAA03155@spammie.svbug.com> Date: Tue, 12 Dec 2000 06:36:04 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: Fwd: kyxtech: freebsd outsniffed by wintendo !!?!? To: dr@kyx.net Cc: tcpdump-workers@tcpdump.org, ethereal-dev@ethereal.com, snort-devel@lists.sourceforge.net, freebsd-hackers@FreeBSD.ORG, tech@openbsd.org In-Reply-To: <0012072118150Q.09615@smp.kyx.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: mcr@sandelman.ottawa.on.ca Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 7 Dec, Dragos Ruiu wrote: > > (Hurm.... Wintendo outperforming unix???!?? Something's > improper about this, and it ought to be fixed... :-) > Comments? Other OS numbers: more recent > FreeBSD versions? Solaris? Tru64? Optimization > patches? Can those OO MSDN lobotomies actually > be good things? Hurm... The Italian gauntlet has > been thrown down.... --dr :-) > > url: http://netgroup-serv.polito.it/winpcap/docs/performance.htm > I'm not sure if we could find someone of this caliber to run the test again. For once I must agree with Mike Smith ;-) Clearly the page: http://netgroup-serv.polito.it/winpcap/ says, "partially sponsored by MicroSoft Research". IMHO, it bait -- bad bait at that. IMO, M$ has found some hole in the FreeBSD kernel and is intending to expose it. Although I suspect the hole's been cleaned up by now by core. If Terry Lambert can chimes in, I know we might get some real answers. I'm not convinced by this M$ agent. Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 15 19:21:14 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 15 19:21:11 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from lox.sandelman.ottawa.on.ca (lox.sandelman.ottawa.on.ca [209.151.24.2]) by hub.freebsd.org (Postfix) with ESMTP id E569637B400 for ; Fri, 15 Dec 2000 19:21:10 -0800 (PST) Received: from nox.sandelman.ottawa.on.ca (nox.sandelman.ottawa.on.ca [209.151.24.6]) by lox.sandelman.ottawa.on.ca (8.8.7/8.8.8) with ESMTP id WAA17340; Fri, 15 Dec 2000 22:21:09 -0500 (EST) Received: from sandelman.ottawa.on.ca (wirespeed.solidum.com [207.35.224.226]) by nox.sandelman.ottawa.on.ca (8.11.0/8.11.0) with ESMTP id eBG3h6811084 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Fri, 15 Dec 2000 19:43:08 -0800 (PST) Received: by sandelman.ottawa.on.ca (8.11.0/8.11.0) id eBG3WBF04232; Fri, 15 Dec 2000 22:32:11 -0500 (EST) Received: from mailer.progressive-comp.com (docs3.abcrs.com [63.238.77.222]) by lox.sandelman.ottawa.on.ca (8.8.7/8.8.8) with ESMTP id QAA11234 for ; Fri, 15 Dec 2000 16:20:17 -0500 (EST) Received: (from docs@localhost) by mailer.progressive-comp.com with id QAA13296; Fri, 15 Dec 2000 16:13:23 -0500 Date: Fri, 15 Dec 2000 16:13:23 -0500 Message-Id: <200012152113.QAA13296@mailer.progressive-comp.com> From: Hank Leininger Errors-To: hlein@progressive-comp.com Reply-To: Hank Leininger To: freebsd-hackers@FreeBSD.ORG Subject: Re: Kyxtech: freebsd outsniffed by wintendo!!?!? Cc: "Fulvio Risso" Cc: tcpdump-workers@sandelman.ottawa.on.ca X-Shameless-Plug: Check out http://marc.theaimsgroup.com/ X-Warning: This mail posted via a web gateway at marc.theaimsgroup.com X-Warning: Report any violation of list policy to abuse@progressive-comp.com X-Posted-By: Hank Leininger Sender: mcr@sandelman.ottawa.on.ca Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-12-14, "Fulvio Risso" wrote: > Buffer sizes > We did not make any test about creating 1MB buffers. However our > architecture does not have the problem that "large buffer" = "large > time used to transfer this buffer to user level" because we are able to [snip] > Context switches > Are kept the lowest, because several packets can be transferred at the > same time. Erm... but if you've not enlarged the buffer from the default, you've not kept context switches "at the lowest." Sure, there isn't one switch per packet. But there could be far more packets per switch if you'd enlarged the buffer (note there's some diminishing returns as you exceed different cachesize boundaries, i.e. performance will actually drop when you working set gets too big for L2 cache, etc). > UFS filesystem > We used FAT to strore packets because the UFS filesystem was on a > second hard disk, so that the disk could have made some difference. We > can reinstall BSD and repeat the test. We'll do that for sure. I suspect this will dramatically change things. Helping a friend who was working on 100mbit sustained capture on FreeBSD, I realized he was writing to a FAT filesystem (on removable drives) for ease of portability. I suggested he switch to UFS; he did so and realized a 200% performance improvement (3x). This was before softupdates, which should make things even better. FAT is an awful filesystem to begin with, and I'd not be surprised if its implementation in FreeBSD isn't as good as it could be (because, why bother?). I'm afraid, this one simple fact completely distorts your results. Of course, even if you switch to UFS it won't quite be apples-to-apples. But at least, you will be using the native/best/most appropriate filesystem for each platform you're testing. Right now, whenever you start writing packets to disk under FreeBSD, you're testing how much FAT blows, and not much else. -- Hank Leininger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 2: 9:19 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 02:09:17 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from db.wireless.net (adsl-gte-la-216-86-194-70.mminternet.com [216.86.194.70]) by hub.freebsd.org (Postfix) with ESMTP id 9AA7737B400 for ; Sat, 16 Dec 2000 02:09:16 -0800 (PST) Received: from wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with ESMTP id BAA29538 for ; Sat, 16 Dec 2000 01:54:33 -0800 (PST) (envelope-from dbutter@wireless.net) Sender: dbutter@db.wireless.net Message-ID: <3A3B3F69.FAF26CFD@wireless.net> Date: Sat, 16 Dec 2000 02:09:45 -0800 From: Devin Butterfield X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Re: StrongARM support? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I guess my reply to Jordan never made it to the list, so here goes a second try... Jordan Hubbard wrote: > > > Is there any work in progress to support running FreeBSD on ARM > > processors? If not, are there any plans to? I would be very interested > > in helping out with such an effort. I would love to have FreeBSD running > > on my iPAQ PocketPC. :) > > No work in progress, no plans. Would you be interested in heading > such a project? That's what's needed. :) > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message Unfortunately, I don't think that I have enough knowledge to "head" such a project. I can certainly help in the effort though. I'm familiar with the FreeBSD kernel and have written drivers but I really know little about StrongARM or what it would take to get the FreeBSD kernel to boot on a SA1110 for example. I guess we could start by using the data collected by the NetBSD group's effort to run on the StrongARM ?? Anyone here interested in such a project (and perhaps who has some prior knowledge of what would be involved in realizing such a beast)? -- Regards, Devin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 7:44:17 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 07:44:13 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from axp5.physik.fu-berlin.de (axp5.physik.fu-berlin.de [160.45.34.3]) by hub.freebsd.org (Postfix) with ESMTP id A95E237B400; Sat, 16 Dec 2000 07:44:12 -0800 (PST) Received: from oberon.physik.fu-berlin.de (oberon.physik.fu-berlin.de [160.45.33.83]) by axp5.physik.fu-berlin.de (8.9.1a/8.9.1) with ESMTP id QAA21308; Sat, 16 Dec 2000 16:44:07 +0100 (MET) Received: (from thimm@localhost) by oberon.physik.fu-berlin.de (8.9.1a/8.9.1) id QAA17378; Sat, 16 Dec 2000 16:44:06 +0100 (MET) Date: Sat, 16 Dec 2000 16:44:05 +0100 From: Axel Thimm To: "David E. Cross" Cc: Carsten Urbach , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: rpc.lockd and true NFS locks? Message-ID: <20001216164405.C9380@oberon.physik.fu-berlin.de> Reply-To: Axel Thimm , Carsten Urbach References: <200012142245.RAA69128@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200012142245.RAA69128@cs.rpi.edu>; from crossd@cs.rpi.edu on Thu, Dec 14, 2000 at 05:45:15PM -0500 Sender: thimm@oberon.physik.fu-berlin.de Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the fast reply. On Thu, Dec 14, 2000 at 05:45:15PM -0500, David E. Cross wrote: > As for "client" vs. "server", that is quite tricky.... since WRT NFS locking > they are both client and server. The "server" side is done and requires no > modifcations to the kernel. However a FreeBSD kernel is still unable to > acquire an NFS lock. This latter case is quite likely what your users are > seeing the affects of. Just to understand it right: The current rpc.lockd is neither requesting locks, if FreeBSD is an NFS client to whatever NFS server, nor serving such requests as an NFS server to whatever client. Your (David Cross's) uncommited code does implement NFS locks for a FreeBSD NFS server. Perhaps in a development stage, but better than not having locks at all. Now I am quite surprised to learn that FreeBSD apparently is not able to request locks over NFS. Am I right? Wouldn't that mean, that you might cause data corruption if, say, I was to read my mail from a FreeBSD box over an NFS mounted spool directory (running under OSF1 in our case), and I decided to write back the mbox to the spool dir the same moment new mail is delivered? I can't imagine that, I must have misunderstood something, most probably the role of the client part of NFS locks. Could someone clarify? If I were right, then FreeBSD would only be good for read only NFS access, and we were using FreeBSD as NFS clients in our department since before 2.2.x. > In the end: the code is there and available for those who want to test and > play with it. It has not been committed because it is still "broken". > I could do it to -current or make it a port, if someone were to tell me that > it would be "ok" to do so. I would vote for port. Thanks, Axel. P.S. please reply not only to freebsd-hackers, but also Cc: me, as I am only subscribed to freebsd-current and freebsd-stable. -- Axel.Thimm@physik.fu-berlin.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 9:50:42 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 09:50:41 2000 Return-Path: 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 6784A37B400 for ; Sat, 16 Dec 2000 09:50:39 -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 MAA63144; Sat, 16 Dec 2000 12:51:16 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20001216124841.01e27c20@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 16 Dec 2000 12:53:22 -0500 To: opentrax@email.com, dr@kyx.net From: Dennis Subject: Re: Fwd: kyxtech: freebsd outsniffed by wintendo !!?!? Cc: tcpdump-workers@tcpdump.org, ethereal-dev@ethereal.com, snort-devel@lists.sourceforge.net, freebsd-hackers@FreeBSD.ORG, tech@openbsd.org In-Reply-To: <200012121436.GAA03155@spammie.svbug.com> References: <0012072118150Q.09615@smp.kyx.net> 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 Im confused as to what difference it makes? No production server should ever use bpf for any "performance" oriented function anyway. Plus if you are doing network testing you should write to dev/null or a ram disk or better yet dump the packets rather than store them, Every disk will be different so you need to get that variable out of the equation. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 9:57:46 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 09:57:43 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from eozoon.coleman.org (adsl-209-233-238-136.dsl.snfc21.pacbell.net [209.233.238.136]) by hub.freebsd.org (Postfix) with ESMTP id 6643A37B400 for ; Sat, 16 Dec 2000 09:57:42 -0800 (PST) Received: from eozoon.coleman.org (eozoon.coleman.org [127.0.0.1] (may be forged)) by eozoon.coleman.org (8.9.3/8.9.3) with ESMTP id JAA22961; Sat, 16 Dec 2000 09:57:39 -0800 (PST) Message-Id: <200012161757.JAA22961@eozoon.coleman.org> X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.3 #1[UCI] To: "David E. Cross" Cc: freebsd-hackers@freebsd.org Reply-To: don@coleman.org Subject: Re: rpc.lockd and true NFS locks? In-reply-to: Your message of "Thu, 14 Dec 2000 19:40:48 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Dec 2000 09:57:38 -0800 From: Don Coleman Sender: don@eozoon.coleman.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David, I wrote the NFS lockd code for BSD/OS (it's based on some user land stuff Keith Bostic did, and then Kirk McKusick helped clean up my basic design and the VFS layering for the server/kernel side). It has passed the connectathon tests, and has been being used by BSD/OS customers for a while, but mostly for locking mail files (why they don't use POP or IMAP, I've never been able to figure out), and locking files being edited by vi over an NFS export. I think we've had 1 bug report/fix, at least that got back to me ... it's been in BSD/OS for like 2 years now, but given the lack of bug reports, I doubt it's limits are being pushed. The main feature the BSD/OS lockd code is missing, is the client side of server side recovery... BSD/OS never crashes ;->, so our clients have never reported this problem (we mention it in our man page). If the lockd server crashes/reboots, we do go through a grace period, and we notify the clients they need to re-establish their locks, but our client side doesn't track the current lock states (even though the client kernel has that complete information, the user mode lock daemon on the client side doesn't keep a copy). So a BSD/OS server, with non-BSD/OS clients is fully functional. This problem isn't hard to fix... there is a two step fix, all user-land. First, make the client side user level lockd a single process (under BSD/OS, it is two processes)... the problem is that each process has a piece of the responsibility/knowledge you need to re-establish locks on your server when it crashes. Second, the client side user level lockd needs to be able to figure out what lockd locks the client as a whole has been given... the lockd client needs to keep it's own idea of what lock the client still holds (just keep it in memory, ordered by server, simple and quick). I already have the first part done, it just hasn't been fully tested, and since BSD/OS is customer driven, and no customers have been pushing us, I haven't committed it. Anyone who wants it, let me know, and I'll give it to you. There are also some improvements I'd suggest as you merge the code (a pair of fresh eyes and fingers is always an opportunity!) 1) we use a FIFO to pass data from the kernel to the user land process. we should at least use a socket... 2) we use a private field in the proc structure, even though it is only used by the lockd process... this was so we could clean up all the server side data if the user level process of the server side lockd crashed or was killed (Solaris admins kill lockd all the time). Using a kernel level on_exit(), or perhaps making a lockd vfs (so a lockd_close() would be called when the lockd process exits), are both possibilities. The general idea is that if you kill and restart the lockd process, it should behave just as if the server was rebooted. And of course there are the little stuff, like we don't back-off and re-try as well as we should, and errors can be dropped, and little stuff like that. I'd be happy to answer any questions, and help in any way I can. don ps: I'll be travelling in South East Asia (Bangkok, Mayanmar, Bali) from Jan 9 to Feb 15, so I will not be able to help during that time... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 10:22:27 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 10:22:24 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ducky.nz.freebsd.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id A3D0737B400; Sat, 16 Dec 2000 10:22:22 -0800 (PST) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id HAA03654; Sun, 17 Dec 2000 07:22:20 +1300 (NZDT) Message-Id: <200012161822.HAA03654@ducky.nz.freebsd.org> From: "Dan Langille" Organization: langille.org To: freebsd-hackers@FreeBSD.ORG Date: Sun, 17 Dec 2000 07:22:08 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: processing incoming mail messages (FreshPorts 2) Reply-To: dan@langille.org Cc: freebsd-ports@FreeBSD.ORG Priority: normal X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Which list would be more appropriate for asking advice on designing a mail processing strategy for FreshPorts 2 (i.e. processing all of cvs-all, not just the ports)? I'm looking for recommendations and guidance on how to capture the incoming messages and process them one at a time. As opposed to starting a separate perl script for each message (which is the the existing strategy and is usually fine, except when large numbers of messages turn up in a short period of time). -- Dan Langille The FreeBSD Diary - http://www.freebsddiary.org/ NZ ADSL - http://www.unixathome.org/adsl/ NZ Broadband - http://www.unixathome.org/broadband/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 10:27: 8 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 10:27:05 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from roura.ac.upc.es (roura.ac.upc.es [147.83.33.10]) by hub.freebsd.org (Postfix) with ESMTP id E331F37B400 for ; Sat, 16 Dec 2000 10:26:58 -0800 (PST) Received: from ac.upc.es (fonoll.ac.upc.es [147.83.32.14]) by roura.ac.upc.es (8.11.0/8.11.0) with ESMTP id eBGITaO12417; Sat, 16 Dec 2000 19:29:36 +0100 (MET) Sender: oscar@ac.upc.es Message-ID: <3A3BB490.9952EA36@ac.upc.es> Date: Sat, 16 Dec 2000 19:29:36 +0100 From: Oscar I Lepe Organization: DAC/UPC X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: es, en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Help: make buildkernel fails when a new option is added Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! following section 22 of the handbook I added some config options I just invented to guard some ad-hoc code I inserted in some kernel files for RELEASE-4.1.1. All the options go to opt_navi.h. The config program accepts this options and produces the apropriate opt_navi.h file in the compile directory. But when I run "make buildkernel" it fails at the first kernel file that references opt_navi.h (#include "opt_navi.h") saying "no such file or directory". Please help me solve this. Thanks. #mount SOURCE_CODE_SERVER:/FreeBSD4/src ~oscar/FreeBSD4/src #mount SOURCE_CODE_SERVER:/FreeBSD4/obj /usr/obj #cd ~oscar/FreeBSD4/src #vi sys/i386/conf/options (added appropriate entries) #make buildkernel KERNEL=NAVI ----------------------------------- >>> Rebuilding kernel(s) ----------------------------------- ===> NAVI ... ... ... rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/home/oscar/FreeBSD4/src/i386/usr/include /usr/home/oscar/FreeBSD4/src/sys/modules/xl/../../pci/if_xl.c /usr/home/oscar/FreeBSD4/src/sys/modules/xl/../../pci/if_xl.c:4: opt_navi.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/home/oscar/FreeBSD4/src/sys/modules/xl. *** Error code 1 Stop in /usr/home/oscar/FreeBSD4/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/home/oscar/FreeBSD4/src/sys/NAVI. *** Error code 1 Stop in /usr/home/oscar/FreeBSD4/src. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 12: 5:49 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 12:05:45 2000 Return-Path: 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 75DA337B400 for ; Sat, 16 Dec 2000 12:05:43 -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 147NeO-0000T2-00; Sat, 16 Dec 2000 13:09:48 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A3BCC0C.D6C2C1BD@softweyr.com> Date: Sat, 16 Dec 2000 13:09:48 -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: "Koster, K.J." Cc: Jonas Bulow , hackers@FreeBSD.ORG Subject: Re: kqueue microbenchmark results References: <59063B5B4D98D311BC0D0001FA7E4522026D7ABF@l04.research.kpn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Koster, K.J." wrote: > > > > > > A simple way to keep the kernel simple: > > > > > http://linuxtoday.com/news_story.php3?ltsn=2000-12-09-013-20-NW-GN-KN > > > > Device drivers in Perl. What a spectacularly bad idea. ;^) > > > That's what people used to say about writing kernels in C. But those were stupid people, and I'm not. I certainly wouldn't put it past the Linux crowd, though. -- "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 16 12:13:39 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 12:13:36 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from marlborough.cnchost.com (marlborough.concentric.net [207.155.248.14]) by hub.freebsd.org (Postfix) with ESMTP id 8CFE637B400 for ; Sat, 16 Dec 2000 12:13:36 -0800 (PST) Received: from bitblocks.com (ts003d04.oak-ca.concentric.net [206.173.201.112]) by marlborough.cnchost.com id PAA14008; Sat, 16 Dec 2000 15:13:33 -0500 (EST) [ConcentricHost SMTP Relay 1.10] Message-ID: <200012162013.PAA14008@marlborough.cnchost.com> Errors-To: To: Marc Tardif Cc: freebsd-hackers@freebsd.org Subject: Re: syscall assembly In-Reply-To: Your message of "Fri, 15 Dec 2000 14:34:10 EST." Date: Sat, 16 Dec 2000 12:13:32 -0800 From: Bakul Shah Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc sent me this: > > > > pushl %ebp > > > > movl %esp,%ebp > > > > subl $8,%esp > > > > > > > This might not be of interest to the rest of the mailing list > > > but what is the purpose of the subl instruction used before > > > calling functions? Is that where the return value is retrieved > > > from, instead of using the %eax register as would Linux? > > > > This is to keep the stack alignment to 16 bytes. Recall that > > a call will push the return address on the stack and the > > frame pointer (%ebp) pushed so now we have 8 bytes on the > > stack. If the stack was aligned before the call, we need to > > further adjust it by 8 more bytes so that after the procedure > > prolog it is once again aligned on a 16 byte boundary. > > > [ snip ] > > Consider the following code debugged with gdb: > int func() { > return 1; > } > int main() { > return func(); > } > > # gcc -g func.c > # gdb a.out > (gdb) display/x $sp > (gdb) display/i $pc > (gdb) break *&main + 3 > (gdb) run > Breakpoint 1, 0x804848c in main () at func.c:3 > 3 } > 2: x/i $eip 0x804848f : sub $0x8,%esp > 1: /x $esp = 0xbfbff820 > (gdb) si > 5 return func(); > 2: x/i $eip 0x8048492 : call 0x804847c > 1: /x $esp = 0xbfbff818 > > Oddly, it seems to me the stack top (pointed to by %esp) > is aligned _before_ the sub instruction. And then, this > instruction unaligns the stack by $0x8. How does this > make sense? May be people who know more about gcc will explain this better but I will speculate in any case! Assuming that 16 byte alignment actually helps, it would make sense to have either a) the local frame start at 16 byte boundary, or b) the args start at a 16 byte boundary The goal is to minimize the number of cache lines that need to be fetched. You want the *first free location* to be on a 16 byte boundary (where either the args start or the local frame starts). What Marc observed seems to point to a) -- the first free location is on a 16 byte boundary _after_ the procedure prolog (push %ebp). This is where you start allocating locals. gcc seems to put an additional restriction in that even args start at a 16 byte boundary. This seems unnecessary. It should do either a) or b) but not both. If you think of args to a called function as belonging to the caller's frame then a) is what makes sense. But if you want tail call optimization (like I do), you'd want args to be part of the callee's frame since in this case the caller's frame is *replaced* by the callee's (since you never return to the caller you can throw away his frame prior to the call but args to the callee must remain). In this case the frame pointer %ebp points in the middle of a frame but the frame starts with args. But I still question this optimization. Are there any stats on whether this 16 byte aligning improves performance? it certainly increases space use! -- bakul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 12:40:19 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 12:40:16 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from emu.prod.itd.earthlink.net (emu.prod.itd.earthlink.net [207.217.121.31]) by hub.freebsd.org (Postfix) with ESMTP id 802DA37B400 for ; Sat, 16 Dec 2000 12:40:16 -0800 (PST) Received: from mobile.wemm.org (pool0345.cvx20-bradley.dialup.earthlink.net [209.179.251.90]) by emu.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id MAA20963; Sat, 16 Dec 2000 12:40:07 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id eBG5b7O74256; Fri, 15 Dec 2000 21:37:08 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200012160537.eBG5b7O74256@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Alfred Perlstein Cc: Martin Blapp , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Import and merge of TI-RPC from NetBSD In-Reply-To: <20001215080745.K19572@fw.wintelcom.net> Date: Fri, 15 Dec 2000 21:37:07 -0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > * Martin Blapp [001215 01:39] wrote: > > > > Hi, > > > > I'd like to import the NetBSD RPC-Interface, based on Sun's TI-RPC code. > > > > This will made available the TI-RPC features and generated code with > > rpcgen will compile then without problems. The code remains backword > > compatible, there ar no changes needed in the codebase (therefore some > > are recomanded). The code I 'maintain' (mount utilities) is already > > patched in my codebase. > > > > I've started with merging and adapting and I'd like to have your > > tips and opinions. > > I'd like to see this happen, if you come across any hurdles with > the code feel free to email me about it. Our current RPC is based on Sun's releases of TI-RPC. It shouldn't be all that hard to go to a more recent version of it as most of the old RPC cruft got cleaned up or fixed to get it to work with the original TI-RPC import. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 13:46:17 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 13:46:15 2000 Return-Path: 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 7449037B402 for ; Sat, 16 Dec 2000 13:46:15 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1098) id D93F22B230; Sat, 16 Dec 2000 15:46:04 -0600 (CST) Date: Sat, 16 Dec 2000 15:46:04 -0600 From: Bill Fumerola To: Dan Phoenix Cc: Poul-Henning Kamp , freebsd-hackers@FreeBSD.ORG Subject: Re: Tun driver? Message-ID: <20001216154604.A72273@elvis.mu.org> References: <4581.976715688@critter> 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, Dec 14, 2000 at 08:00:18AM -0800 X-Operating-System: FreeBSD 4.2-FEARSOME-20001103 i386 Sender: billf@elvis.mu.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 14, 2000 at 08:00:18AM -0800, Dan "Mahir" Phoenix wrote: > what you mean device side? > you mean server side? He meant exactly what he said: [billf.yahoo-root 16:26:00] < /dev # ifconfig tun0 ifconfig: interface tun0 does not exist [billf.yahoo-root 16:26:09] < /dev # dd if=/dev/tun0 of=/dev/null count=0 0+0 records in 0+0 records out 0 bytes transferred in 0.000014 secs (0 bytes/sec) [billf.yahoo-root 16:26:18] < /dev # ifconfig tun0 tun0: flags=8010 mtu 1500 [billf.yahoo-root 16:26:20] < /dev # Some program needs to open() the device for it to register. The following snippet of code (around line 155 of sys/net/if_tun.c) is relevant: tp = dev->si_drv1; if (!tp) { tuncreate(dev); tp = dev->si_drv1; } .. and tuncreate() sets up the device and if_attach()s the driver, which makes it appear in the list ifconfig works off of. -- 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 Sat Dec 16 14:27:30 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 14:27:27 2000 Return-Path: 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 9BCC137B400; Sat, 16 Dec 2000 14:27:26 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.1/8.11.1) id eBGMRKt22481; Sat, 16 Dec 2000 16:27:20 -0600 (CST) (envelope-from dan) Date: Sat, 16 Dec 2000 16:27:20 -0600 From: Dan Nelson To: Axel Thimm , Carsten Urbach Cc: "David E. Cross" , freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: rpc.lockd and true NFS locks? Message-ID: <20001216162720.A11561@dan.emsphone.com> References: <200012142245.RAA69128@cs.rpi.edu> <20001216164405.C9380@oberon.physik.fu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.12i In-Reply-To: <20001216164405.C9380@oberon.physik.fu-berlin.de>; from "Axel Thimm" on Sat Dec 16 16:44:05 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: dan@dan.emsphone.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Dec 16), Axel Thimm said: > Wouldn't that mean, that you might cause data corruption if, say, I > was to read my mail from a FreeBSD box over an NFS mounted spool > directory (running under OSF1 in our case), and I decided to write > back the mbox to the spool dir the same moment new mail is delivered? That's why dotlocking is recommended for locking mail spools. Both procmail and mutt will dotlock your mail file while it's being accessed. -- 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 Sat Dec 16 14:30:27 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 14:30:25 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id D752337B400 for ; Sat, 16 Dec 2000 14:30:24 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id OAA10056; Sat, 16 Dec 2000 14:29:35 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200012162229.OAA10056@spammie.svbug.com> Date: Sat, 16 Dec 2000 14:29:31 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: R: [Ethereal-dev] Re: Fwd: kyxtech: freebsd outsniffed by winte ndo !!?!? To: risso@polito.it Cc: dr@kyx.net, tcpdump-workers@tcpdump.org, ethereal-dev@ethereal.com, snort-devel@lists.sourceforge.net, freebsd-hackers@FreeBSD.ORG, tech@openbsd.org In-Reply-To: <000701c06453$b2e83740$14ec1fc3@ssgrr.it> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: jessem@spammie.svbug.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12 Dec, Fulvio Risso wrote: > I do not agree with you. > Partially supported by Ms Research means that we got: > - software > - 1 Dell workstation > > That's it. > I *strongly* suggest to ask someone before opening your mouth. > Your tone strongly suggest your research is less than objective. Given that questioning technical ability is something I'll leave to someone else. It's not in my interest, nor is it benificial to continue discussion with yourself when you readily admit to being open to financial influences. I'll leave it at that and wish you well in life. best regards, Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 14:54:44 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 14:54:42 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from srengineering.com (dsl-64-192-147-97.telocity.com [64.192.147.97]) by hub.freebsd.org (Postfix) with ESMTP id A333A37B400 for ; Sat, 16 Dec 2000 14:54:42 -0800 (PST) Received: from buttercup (unknown [192.168.1.2]) by srengineering.com (SecureMAIL) with SMTP id 49EA12775C; Sat, 16 Dec 2000 16:50:42 +0000 (GMT) From: Emre Date: Sat, 16 Dec 2000 17:02:26 -0600 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="us-ascii" To: opentrax@email.com References: <200012162229.OAA10056@spammie.svbug.com> In-Reply-To: <200012162229.OAA10056@spammie.svbug.com> Subject: Re: R: [Ethereal-dev] Re: Fwd: kyxtech: freebsd outsniffed by winte ndo !!?!? Cc: dr@kyx.net, tcpdump-workers@tcpdump.org, ethereal-dev@ethereal.com, snort-devel@lists.sourceforge.net, freebsd-hackers@FreeBSD.ORG, tech@openbsd.org MIME-Version: 1.0 Message-Id: <00121617022600.01588@buttercup> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday 16 December 2000 16:29, opentrax@email.com wrote: > On 12 Dec, Fulvio Risso wrote: > > I do not agree with you. > > Partially supported by Ms Research means that we got: > > - software > > - 1 Dell workstation > > > > That's it. > > I *strongly* suggest to ask someone before opening your mouth. > > Your tone strongly suggest your research is less than > objective. Given that questioning technical ability > is something I'll leave to someone else. It's not > in my interest, nor is it benificial to continue > discussion with yourself when you readily admit to being > open to financial influences. Hi, Can you guys take this private? or maybe end this thread? You know this crap is going to 5 other mailing lists. Thanks -- Emre Yildirim, Information Security Officer GPG KeyID 0x92FE42F4 | http://1086362465/emre-dsa.asc emre@SRENGINEERING.COM | emre.yildirim@US.ARMY.MIL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 16:14:27 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 16:14:26 2000 Return-Path: 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 2AD3A37B400 for ; Sat, 16 Dec 2000 16:14:26 -0800 (PST) Received: from fanf by hand.dotat.at with local (Exim 3.15 #3) id 147RSp-0002Wb-00; Sun, 17 Dec 2000 00:14:07 +0000 Date: Sun, 17 Dec 2000 00:14:07 +0000 From: Tony Finch To: Patryk Zadarnowski Cc: SteveB , freebsd-hackers@FreeBSD.ORG Subject: Re: kernel type Message-ID: <20001217001407.R30096@hand.dotat.at> References: <200012160050.LAA97623@mycenae.jantar.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200012160050.LAA97623@mycenae.jantar.org> Organization: Covalent Technologies, Inc Sender: fanf@dotat.at Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patryk Zadarnowski wrote: > >Now that I think of it, there aren't many commercial microkernel >systems out there with the possible exception of QNX and lots of >little embedded toys. Mac OS X is based on Mach. Tony. -- f.a.n.finch fanf@covalent.net dot@dotat.at "And remember my friend, future events such as these will affect you in the future." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 17:37:17 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 17:37:15 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.jantar.org (mycenae.jantar.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id DB02E37B400 for ; Sat, 16 Dec 2000 17:37:13 -0800 (PST) Received: from mycenae.jantar.org (patrykz@localhost [127.0.0.1]) by mycenae.jantar.org (8.9.3/8.9.3) with ESMTP id MAA99261; Sun, 17 Dec 2000 12:36:44 +1100 (EST) (envelope-from patrykz@mycenae.jantar.org) Message-Id: <200012170136.MAA99261@mycenae.jantar.org> From: Patryk Zadarnowski To: Tony Finch Cc: SteveB , freebsd-hackers@FreeBSD.ORG Subject: Re: kernel type In-Reply-To: Message from Tony Finch of "Sun, 17 Dec 2000 00:14:07 -0000." <20001217001407.R30096@hand.dotat.at> Date: Sun, 17 Dec 2000 12:36:44 +1100 Sender: patrykz@mycenae.jantar.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Dec 2000, Tony Finch wrote: > Patryk Zadarnowski wrote: >> >> Now that I think of it, there aren't many commercial microkernel >> systems out there with the possible exception of QNX and lots of >> little embedded toys. > Mac OS X is based on Mach. Oh, that's right, that new kid on the block ;) I keep forgetting about Apple's talent for shooting itself in a foot ;) BTW, for the original poster: in case you don't know, there exists a port of 4.4BSD that runs on top of Mach (Lites.) Pat. PS. Before this starts a flame war, let me say that I really believe that MacOS X is a very good thing for everyone involved, although the choice of Mach for the microkernel seems a little arbitrary if not misguided. Pat. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Patryk Zadarnowski University of New South Wales School of Computer Science and Engineering -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 18:38:40 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 18:38:38 2000 Return-Path: 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 5948437B400 for ; Sat, 16 Dec 2000 18:38:37 -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 eBH2bvw85116; Sat, 16 Dec 2000 18:37:57 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: Patryk Zadarnowski Cc: Tony Finch , SteveB , freebsd-hackers@FreeBSD.ORG Subject: Re: kernel type In-Reply-To: Message from Patryk Zadarnowski of "Sun, 17 Dec 2000 12:36:44 +1100." <200012170136.MAA99261@mycenae.jantar.org> Date: Sat, 16 Dec 2000 18:37:56 -0800 Message-ID: <85112.977020676@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > PS. Before this starts a flame war, let me say that I really believe > that MacOS X is a very good thing for everyone involved, although the > choice of Mach for the microkernel seems a little arbitrary if not > misguided. It's hardly arbitrary, though the jury's still out as to whether it's misguided or not. You may remember that Apple bought a little company called NeXT a few years back. Well, that company's people had a lot to do with the OS design of OS X and let's not forget the design of NeXTStep. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 22:21:25 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 22:21:21 2000 Return-Path: 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 08F9437B400; Sat, 16 Dec 2000 22:21:20 -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 eBH6LIs01448; Sat, 16 Dec 2000 23:21:19 -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 XAA81955; Sat, 16 Dec 2000 23:21:18 -0700 (MST) Message-Id: <200012170621.XAA81955@harmony.village.org> To: hackers@freebsd.org, doc@freebsd.org Subject: Request for review of newfs update Date: Sat, 16 Dec 2000 23:21:18 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've made the following change to newfs man page locally. Please comment upon the style of the change as well as its technical accuracy. Style comments should be sent to doc@freebsd.org with imp@freebsd.org cc'd (I'm not on doc@). Technical content comments should be sent to hackers@freebsd.org. The change does two things. First, it removes the warning about not being able to boot off file systems that aren't 8k/1k. There was a thread here that reported this was no longer the case and that both 4k and 16k block sizes work. The second change gives an example of using a 16k block size and a 4k fragment size with 100 cylinders per group with a note that this is expected to give better performance for large file systems. Comments about changing the default should go to /dev/null, or be discussed under a different thread. :-) Warner Index: newfs.8 =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/sbin/newfs/newfs.8,v retrieving revision 1.28 diff -u -r1.28 newfs.8 --- newfs.8 2000/11/20 16:47:42 1.28 +++ newfs.8 2000/12/17 06:15:48 @@ -335,18 +335,20 @@ .El .Sh EXAMPLES .Pp +.Dl newfs -b 16384 -f 4096 -c 100 /dev/ad3s1a +.Pp +Creates a new ufs file system on ad3s1a. +.Nm +will use a block size of 16384 bytes, a fragement size of 4096 bytes +and have 100 cylinders per cylinder group rather than the defaults. +These values are tend to produce better performance than the defaults +for file systems larger than about 5 gigabytes. +.Pp .Dl mount_mfs -s 131072 -o nosuid,nodev /dev/da0s1b /tmp .Pp Mount a 64 MB large memory file system on /tmp, with .Xr mount 8 options nosuid and nodev. -.Sh BUGS -The boot code of -.Fx -assumes that the file system that carries the -kernel has blocks of 8 kilobytes and fragments of 1 kilobyte. -You will -not be able to boot from a file system that uses another size. .Sh SEE ALSO .Xr fdformat 1 , .Xr disktab 5 , To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 23:10:57 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 23:10:53 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from w250.z064001178.sjc-ca.dsl.cnc.net (w250.z064001178.sjc-ca.dsl.cnc.net [64.1.178.250]) by hub.freebsd.org (Postfix) with SMTP id BB3C137B400 for ; Sat, 16 Dec 2000 23:10:53 -0800 (PST) Received: (qmail 84394 invoked by uid 1000); 17 Dec 2000 07:11:14 -0000 Date: Sat, 16 Dec 2000 23:10:52 -0800 From: Jos Backus To: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: rpc.lockd and true NFS locks? Message-ID: <20001216231052.D80635@lizzy.bugworks.com> Reply-To: Jos Backus Mail-Followup-To: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG References: <200012142245.RAA69128@cs.rpi.edu> <20001216164405.C9380@oberon.physik.fu-berlin.de> <20001216162720.A11561@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001216162720.A11561@dan.emsphone.com>; from dnelson@emsphone.com on Sat, Dec 16, 2000 at 04:26:58PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 16, 2000 at 04:26:58PM -0600, Dan Nelson wrote: > That's why dotlocking is recommended for locking mail spools. Both > procmail and mutt will dotlock your mail file while it's being > accessed. Or Maildirs. -- Jos Backus _/ _/_/_/ "Modularity is not a hack." _/ _/ _/ -- D. J. Bernstein _/ _/_/_/ _/ _/ _/ _/ josb@cncdsl.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 16 23:43:45 2000 From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 16 23:43:43 2000 Return-Path: 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 EDE2B37B400 for ; Sat, 16 Dec 2000 23:43:42 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1098) id 548ED2B261; Sun, 17 Dec 2000 01:43:37 -0600 (CST) Date: Sun, 17 Dec 2000 01:43:37 -0600 From: Bill Fumerola To: Jordan Hubbard Cc: Patryk Zadarnowski , Tony Finch , SteveB , freebsd-hackers@FreeBSD.ORG Subject: Re: kernel type Message-ID: <20001217014337.C72273@elvis.mu.org> References: <85112.977020676@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <85112.977020676@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Sat, Dec 16, 2000 at 06:37:56PM -0800 X-Operating-System: FreeBSD 4.2-FEARSOME-20001103 i386 Sender: billf@elvis.mu.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 16, 2000 at 06:37:56PM -0800, Jordan Hubbard wrote: > It's hardly arbitrary, though the jury's still out as to whether it's > misguided or not. You may remember that Apple bought a little company > called NeXT a few years back. Well, that company's people had a lot > to do with the OS design of OS X and let's not forget the design of > NeXTStep. ... and how currently popular they[NeXT] are. ;-> -- 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