From owner-freebsd-hackers Sun Sep 3 0:16:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.wertep.com (relay2.wertep.com [194.44.90.130]) by hub.freebsd.org (Postfix) with ESMTP id 1BBB137B423 for ; Sun, 3 Sep 2000 00:16:08 -0700 (PDT) Received: from She.wertep.com (she-tun-proxy [192.168.252.2]) by relay2.wertep.com (8.9.3/8.9.3) with ESMTP id KAA83230 for ; Sun, 3 Sep 2000 10:16:04 +0300 (EEST) (envelope-from petro@She.wertep.com) Received: from localhost (petro@localhost) by She.wertep.com (8.9.3/8.9.3) with ESMTP id KAA54418 for ; Sun, 3 Sep 2000 10:16:58 +0300 (EEST) (envelope-from petro@She.wertep.com) Date: Sun, 3 Sep 2000 10:16:56 +0300 (EEST) From: petro To: freebsd-hackers@FreeBSD.ORG Subject: SCSI disks. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I have the following problem: I installed FreeBSD 4.1 on Compaq Proliant with SCSI disks. I tried to change in kernel such parameters config kernel root on wd0 to config kernel root on id0 also I added such strings controller ida0 disk id0 at ida0 drive0 disk id1 at ida0 drive1 but when i try to config KERNEL_NAME I receive such message config id:unknown device config; line 36: no root device specified. If someone can help, please... Thank you very much... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 3 1: 0:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by hub.freebsd.org (Postfix) with ESMTP id 7D8A637B423; Sun, 3 Sep 2000 01:00:20 -0700 (PDT) Received: from rumi.usc.edu (rumi.usc.edu [128.125.51.41]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id BAA34002; Sun, 3 Sep 2000 01:00:20 -0700 (PDT) Received: from rumi (localhost [127.0.0.1]) by rumi.usc.edu (8.9.3/8.9.3) with ESMTP id BAA32964; Sun, 3 Sep 2000 01:00:19 -0700 (PDT) Message-Id: <200009030800.BAA32964@rumi.usc.edu> To: freebsd-hackers@freebsd.org, sef@freebsd.org Cc: pavlin@catarina.usc.edu Subject: Q: System call interception Date: Sun, 03 Sep 2000 01:00:19 -0700 From: Pavlin Ivanov Radoslavov Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I need to write some code that will be like a wrapper for some user-level binaries and will intercept some system calls before and after each call, and eventually modify the arguments and/or the result. First I was looking at ptrace(3), but seems that the *BSD ptrace doesn't have the equivalent of PTRACE_SYSCALL. I tried to use the /proc file system, but I ran into a problem. By adapting the truss(1) code I could intercept a child process's system calls (before and after the syscall is completed). However, if I want to modify the return result for example by writing to the registers (using write() to "/proc/%d/regs"), I get error "Device busy". The procfs(5) man page says that I can write to the registers only if the child process is stopped, but seems like that successful "ioctl(PIOCWAIT)" before the writing to the registers is not enough. Playing with writing "attach", "wait", etc. to /proc/%d/ctl didn't help either. I did some search around to find sample code how to modify the intercepted syscalls behavior, but coudn't find any. Any suggestions or ideas? Thanks, Pavlin P.S. Tested OS version: FreeBSD-4.1 and 3.2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 3 1: 5:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.wertep.com (relay2.wertep.com [194.44.90.130]) by hub.freebsd.org (Postfix) with ESMTP id B517A37B424 for ; Sun, 3 Sep 2000 01:05:19 -0700 (PDT) Received: from She.wertep.com (she-tun-proxy [192.168.252.2]) by relay2.wertep.com (8.9.3/8.9.3) with ESMTP id LAA84942 for ; Sun, 3 Sep 2000 11:05:16 +0300 (EEST) (envelope-from petro@She.wertep.com) Received: from localhost (petro@localhost) by She.wertep.com (8.9.3/8.9.3) with ESMTP id LAA54606 for ; Sun, 3 Sep 2000 11:06:12 +0300 (EEST) (envelope-from petro@She.wertep.com) Date: Sun, 3 Sep 2000 11:06:12 +0300 (EEST) From: petro To: freebsd-hackers@FreeBSD.ORG Subject: Kernel problem... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Excuse that I again trouble you. I installed FreeBSD 4.1 on Compaq Proliant and I try to compile kernel I make such things #config KERNEL_NAME #cd ../../compile/KERNEL_NAME #make depend ......making.... #make Nothing happening I again receive # Then I try to run #make install but I receive such message you first must build the kernel and then install it. I will be happy to receive any ideas. Thank you... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 3 1:32:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id 8BA6537B422 for ; Sun, 3 Sep 2000 01:32:18 -0700 (PDT) Received: from teabag.demon.co.uk ([193.237.4.110]) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 13VVCL-0006pT-0Y for freebsd-hackers@freebsd.org; Sun, 3 Sep 2000 09:32:17 +0100 Received: from localhost (cbh@localhost) by teabag.demon.co.uk (8.11.0/8.9.3) with ESMTP id e838V3Z37097 for ; Sun, 3 Sep 2000 09:31:11 +0100 (BST) (envelope-from cbh@teabag.demon.co.uk) Date: Sun, 3 Sep 2000 09:31:03 +0100 (BST) From: Chris Hedley X-Sender: cbh@teabag.cbhnet To: freebsd-hackers@freebsd.org Subject: Re: SCSI disks. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 3 Sep 2000, petro wrote: > Hi! I have the following problem: > I installed FreeBSD 4.1 on Compaq Proliant with SCSI disks. I tried to > change in kernel such parameters > config kernel root on wd0 > to > config kernel root on id0 > also I added such strings > controller ida0 > disk id0 at ida0 drive0 > disk id1 at ida0 drive1 > > but when i try to > config KERNEL_NAME > I receive such message > config id:unknown device > config; line 36: no root device specified. As I understand it, the problem is that there isn't necessarily a direct naming convention between the controller and the devices which use it: you still need to specify scbus (I think) and use the da (discs), sa (tapes), cd (cdroms) and pass (passthrough) devices as per standard SCSI configuration. I don't think it's necessary to specify each disc individually, but rather as a "meta-driver;" that said, I've been using the 5.0 configuration for ages so please check all this against the 4.x standards! Also, I think that since release 4, specifying the root device in your kernel config may be more trouble than it's worth; someone with more experience may wish to either elaborate or correct as they see fit! Cheers, Chris. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 3 10:18:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from plan9.hert.org (plan9.hert.org [195.3.2.198]) by hub.freebsd.org (Postfix) with ESMTP id CAC7D37B423; Sun, 3 Sep 2000 10:18:12 -0700 (PDT) Received: from localhost (awr@localhost) by plan9.hert.org (8.9.3/8.9.1) with ESMTP id UAA26799; Sat, 2 Sep 2000 20:01:51 +0200 (CEST) Date: Sat, 2 Sep 2000 20:01:50 +0200 (CEST) From: awr To: Pavlin Ivanov Radoslavov Cc: freebsd-hackers@FreeBSD.ORG, sef@FreeBSD.ORG Subject: Re: Q: System call interception In-Reply-To: <200009030800.BAA32964@rumi.usc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Intercepting syscalls is very easy. In my mind, what you should do is write a KLD that creates a syscall that mimicks the actions of what syscall you are going to hijack. Your new syscall will only look at the struct ##syscall_args *uap pointer [kernel land argument to syscall] and modify it. After modifying, all you'll have to do is just call the old syscall. In generic terms, here's what i did for hijacking open(2): static int open_wrap(struct proc *p, struct open_args *uap) { /* mess with what's getting pased */ ret = open(p, uap); /* call real open */ return(ret); } statitc struct sysent open_wrap_s = { 3, /* # of argumentsbeing passed to it */ open_wrap /* func pointer to our syscall */ }; static int load_handler(...) { ... MOD_LOAD: ... sysent[SYS_open] = open_wrap_s; .... MOD_UNLOAD sysent[SYS_open].sy_call = (sy_call_t *)open; /* put back old */ } Then, all you'ld have to do is load the kld and your calls would be intercepted by the wrapping syscall. For more details: http://subterrain.net/~awr/KLD-Tutorial/ Introduction to writing KLDs & an examples tar.gz http://thc.pimmel.com/files/thc/bsdkern.html Good tutorial on more blackhat related things to do with KLDs. Hope this helps. Andrew On Sun, 3 Sep 2000, Pavlin Ivanov Radoslavov wrote: > > I need to write some code that will be like a wrapper > for some user-level binaries and will intercept some system calls > before and after each call, and eventually modify the arguments > and/or the result. > > First I was looking at ptrace(3), but seems that the > *BSD ptrace doesn't have the equivalent of PTRACE_SYSCALL. > > I tried to use the /proc file system, but I ran into a problem. > By adapting the truss(1) code I could intercept > a child process's system calls (before and after the syscall is > completed). > However, if I want to modify the return result for example by > writing to the registers (using write() to "/proc/%d/regs"), I get > error "Device busy". > The procfs(5) man page says that I can write to the registers only > if the child process is stopped, but seems like that > successful "ioctl(PIOCWAIT)" before the writing to the registers is > not enough. > Playing with writing "attach", "wait", etc. to /proc/%d/ctl > didn't help either. > > I did some search around to find sample code how to modify the > intercepted syscalls behavior, but coudn't find any. Any suggestions > or ideas? > > Thanks, > Pavlin > > P.S. Tested OS version: FreeBSD-4.1 and 3.2 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 3 13:22:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.wertep.com (relay2.wertep.com [194.44.90.130]) by hub.freebsd.org (Postfix) with ESMTP id 3584437B422 for ; Sun, 3 Sep 2000 13:22:22 -0700 (PDT) Received: from She.wertep.com (she-tun-proxy [192.168.252.2]) by relay2.wertep.com (8.9.3/8.9.3) with ESMTP id XAA12936 for ; Sun, 3 Sep 2000 23:22:18 +0300 (EEST) (envelope-from petro@She.wertep.com) Received: from localhost (petro@localhost) by She.wertep.com (8.9.3/8.9.3) with ESMTP id XAA56273 for ; Sun, 3 Sep 2000 23:23:17 +0300 (EEST) (envelope-from petro@She.wertep.com) Date: Sun, 3 Sep 2000 23:23:16 +0300 (EEST) From: petro To: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel problem... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It said that it doesn't now how to buildkernel. Also excuse I installed 3.5-RELEASE and not 4.1 but I must change this config root kernel on wd0 because I have only SCSI disks so after machine rebooted I receive such message can't mount root(2) it is because he tried to find root on wd0. I also tried to run make all, but I receive empty string, so if someone can please help me how to compile kernel in 3.5-RELEASE to boot from SCSI disk and not from IDE.(I use Compaq Proliant 1500) On Sun, 3 Sep 2000, void wrote: > In UPDATING, there is a description of the new kernel build procedure. > > # cd /usr/src > # make buildkernel KERNEL=KERNEL_NAME > # make installkernel KERNEL=KERNEL_NAME > > You can set KERNEL in /etc/make.conf so you don't have to specify it on > the command line, I just learned the other day. > > On Sun, Sep 03, 2000 at 11:06:12AM +0300, petro wrote: > > Excuse that I again trouble you. > > I installed FreeBSD 4.1 on Compaq Proliant and I try to compile kernel I > > make such things > > #config KERNEL_NAME > > #cd ../../compile/KERNEL_NAME > > #make depend > > ......making.... > > #make > > Nothing happening I again receive # > > Then I try to run > > #make install > > but I receive such message you first must build the kernel and then > > install it. > > > > I will be happy to receive any ideas. > > Thank you... > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > -- > 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 Sun Sep 3 14: 9:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.wertep.com (relay2.wertep.com [194.44.90.130]) by hub.freebsd.org (Postfix) with ESMTP id 726A637B42C; Sun, 3 Sep 2000 14:09:11 -0700 (PDT) Received: from She.wertep.com (she-tun-proxy [192.168.252.2]) by relay2.wertep.com (8.9.3/8.9.3) with ESMTP id AAA14867; Mon, 4 Sep 2000 00:09:03 +0300 (EEST) (envelope-from petro@She.wertep.com) Received: from localhost (petro@localhost) by She.wertep.com (8.9.3/8.9.3) with ESMTP id AAA56402; Mon, 4 Sep 2000 00:09:58 +0300 (EEST) (envelope-from petro@She.wertep.com) Date: Mon, 4 Sep 2000 00:09:58 +0300 (EEST) From: petro To: freebsd-hackers@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Boot problem! 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 Excuse that I again trouble you, but after I read snth on Freebsd.org I have such questions. I installed FreeBSD 3.5 on Compaq Proliant 1500 with SCSI disks and after booting I receive such message: changing root device to wd0s1a changing root device to wd0a error 6: panic: cannot mount root (2) My / filesystem is on idad0s1a so I tried when booting wrote so boot: 0:da(0,a)/boot/loader but it doesn't help, please answer me what I must write in the beggining of booting(or somewhere else) to boot from my SCSI disks.... Thank you very much.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 3 16: 7:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by hub.freebsd.org (Postfix) with ESMTP id B89BF37B43C; Sun, 3 Sep 2000 16:07:17 -0700 (PDT) Received: from rumi.usc.edu (rumi.usc.edu [128.125.51.41]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id QAA36094; Sun, 3 Sep 2000 16:07:16 -0700 (PDT) Received: from rumi (localhost [127.0.0.1]) by rumi.usc.edu (8.9.3/8.9.3) with ESMTP id QAA34204; Sun, 3 Sep 2000 16:07:14 -0700 (PDT) Message-Id: <200009032307.QAA34204@rumi.usc.edu> To: Andrzej Bialecki Cc: awr , Pavlin Ivanov Radoslavov , freebsd-hackers@FreeBSD.ORG, sef@FreeBSD.ORG Subject: Re: Q: System call interception In-reply-to: Your message of "Sun, 03 Sep 2000 19:56:42 +0200." Date: Sun, 03 Sep 2000 16:07:14 -0700 From: Pavlin Ivanov Radoslavov Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Intercepting syscalls is very easy. In my mind, what you should do is > > write a KLD that creates a syscall that mimicks the actions of what Thanks for the detailed info and the pointers. However, I forgot to mention that the solution I need should not require modifications to the system, and should not require root privilege. Pavlin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Sep 3 18:52:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from blackstar.krsu.edu.kg (blackstar.krsu.edu.kg [195.254.161.130]) by hub.freebsd.org (Postfix) with ESMTP id A4C4037B423 for ; Sun, 3 Sep 2000 18:52:48 -0700 (PDT) Received: from krsu.edu.kg (krsu.edu.kg [195.254.164.3]) by blackstar.krsu.edu.kg (8.9.1a/8.9.1) with ESMTP id IAA10586; Thu, 10 Aug 2000 08:33:19 +0600 (KGST) Received: from localhost (slash@localhost) by krsu.edu.kg (8.9.3/8.9.3) with ESMTP id HAA17447; Mon, 4 Sep 2000 07:56:13 +0600 (KGST) (envelope-from slash@krsu.edu.kg) Date: Mon, 4 Sep 2000 07:56:13 +0600 (KGST) From: CrazZzy Slash To: petro Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel problem... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG try after #cd ../../compile/KERNEL_NAME do #vi Makefile and look through it.. P.S. Sorry for my bad English.. :) On Sun, 3 Sep 2000, petro wrote: > Excuse that I again trouble you. > I installed FreeBSD 4.1 on Compaq Proliant and I try to compile kernel I > make such things > #config KERNEL_NAME > #cd ../../compile/KERNEL_NAME > #make depend > ......making.... > #make > Nothing happening I again receive # > Then I try to run > #make install > but I receive such message you first must build the kernel and then > install it. > > I will be happy to receive any ideas. > Thank you... > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- Key fingerprint = 08 2C 60 63 FB DE A5 67 96 38 02 0F FA 9B 81 86 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 4 6:33:19 2000 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 695AD37B42C; Mon, 4 Sep 2000 06:33:15 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id JAA83292; Mon, 4 Sep 2000 09:31:30 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 4 Sep 2000 09:31:30 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Pavlin Ivanov Radoslavov Cc: Andrzej Bialecki , awr , freebsd-hackers@FreeBSD.ORG, sef@FreeBSD.ORG Subject: Re: Q: System call interception In-Reply-To: <200009032307.QAA34204@rumi.usc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 3 Sep 2000, Pavlin Ivanov Radoslavov wrote: > > > > > > Intercepting syscalls is very easy. In my mind, what you should do is > > > write a KLD that creates a syscall that mimicks the actions of what > > Thanks for the detailed info and the pointers. > However, I forgot to mention that the solution I need should not > require modifications to the system, and should not require root > privilege. A number of spiffy replacement/wrapper libc libraries exist. In FreeBSD, applications generally invoke a syscall wrapper compiled into libc automatically using the syscall table (/usr/src/sys/kern/syscalls.master). By interposing a replacement library ahead of libc (must be dynamically linked), you can intercept invocations of these and other functions in libc, replacing them with your own calls. This is done to support socks, for example, wherein socket calls are replaced with socks versions of the same calls. The userland network stack, (Alpine?) was recently posted about on freebsd-net, and does much the same, replacing network calls in the application with invocations of the userland network stack. It's easy to imagine other types of syscall replacement, including catch invocations of syscall(2) directly by the application. Won't help you with assembly code, but whether or not this is an issue depends on whether the syscall interception is intended for functionality additions (SOCKS) or security. If security, the ptrace()/procfs scheme should be able to do that, but I'm not so familiar with that -- take a look at the FreeBSD-specific components of gdb to get an idea here. As mentioned already, our kernel is designed to support replaceable syscall handlers, and TIS has actually released a "wrapper toolkit" to allow the writing of security wrappers to impose new policies. This is implemented on FreeBSD, Solaris, and I believe work is underway for Windows NT and Linux. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 4 7:55:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.wertep.com (relay2.wertep.com [194.44.90.130]) by hub.freebsd.org (Postfix) with ESMTP id BA95037B422 for ; Mon, 4 Sep 2000 07:55:25 -0700 (PDT) Received: from She.wertep.com (she-tun-proxy [192.168.252.2]) by relay2.wertep.com (8.9.3/8.9.3) with ESMTP id RAA58332 for ; Mon, 4 Sep 2000 17:55:21 +0300 (EEST) (envelope-from petro@She.wertep.com) Received: from localhost (petro@localhost) by She.wertep.com (8.9.3/8.9.3) with ESMTP id RAA58176 for ; Mon, 4 Sep 2000 17:56:24 +0300 (EEST) (envelope-from petro@She.wertep.com) Date: Mon, 4 Sep 2000 17:56:23 +0300 (EEST) From: petro To: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel problem... In-Reply-To: <20000904043544.A6257@firedrake.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 The old procedure doesn't work after I run make I receive empty string, and then when I try to run make install I received First start to built the kernel and then install it. Also I tried to change smth in Makefile but nothing help, please if somebody can answer how I can boot my FreeBSD-3.5 if his root filesystem is on /dev/idad0s1a. I tried to enter everything when FreeBSD boot, but every time I receiving Can't mount root on wd0 Can't mount root on wda0 and after this my system rebooting Even if I enter boot: 0:da(0,a) Excuse for my English. On Mon, 4 Sep 2000, void wrote: > On Sun, Sep 03, 2000 at 11:24:43PM +0300, petro wrote: > > > > How can I set KERNEL in /etc/make.conf -??? please write me more, because > > I am not so power user .... > > Thank you.... > > KERNEL= KERNEL_NAME > > just the same way all the other variables in make.conf are set ... but > if you're using 3.x, then I think the old build procedure is what you > want: > > cd /sys/i386/conf > config KERNEL_NAME > cd ../../compile/KERNEL_NAME > make depend > make > make install > > -- > 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 Mon Sep 4 9:41:24 2000 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 5EF2937B42C; Mon, 4 Sep 2000 09:41:16 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e84GfEN53061; Mon, 4 Sep 2000 18:41:14 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org, hackers@freebsd.org Subject: looking for "microuptime went backwards" victims... From: Poul-Henning Kamp Date: Mon, 04 Sep 2000 18:41:14 +0200 Message-ID: <53059.968085674@critter> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm looking for the remaining victims of the dreaded "microuptime went backwards" message. If you can reliably reproduce the problem, please contact me, so we can arrange for some very detailed tracing to try to find out what exactly is going on. I have not been able to trigger the problem in my lab in a long time. If you see the message only occationally, please try the attached patch and let me know if this changes the picture. The patch is not meant as a fix, but it might reduce the impact of this condition considerably when it happens. Basically by reducing the width of the timecounter the magnitude of the hit we take if the timecounter goes backwards is reduced from about an hour to approx 110msec. Reducing the width to less than 17 bits starts to run the risk of ambiguity due to clock rollover. This patch may not be safe with PCAUDIO. Poul-Henning Index: clock.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v retrieving revision 1.155 diff -u -r1.155 clock.c --- clock.c 2000/07/30 21:05:22 1.155 +++ clock.c 2000/09/04 16:34:16 @@ -194,7 +194,7 @@ static struct timecounter i8254_timecounter = { i8254_get_timecount, /* get_timecount */ 0, /* no poll_pps */ - ~0u, /* counter_mask */ + 0x1ffff, /* counter_mask */ 0, /* frequency */ "i8254" /* name */ }; -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Mon Sep 4 21:11:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.prod.itd.earthlink.net [207.217.121.50]) by hub.freebsd.org (Postfix) with ESMTP id F269F37B423 for ; Mon, 4 Sep 2000 21:11:17 -0700 (PDT) Received: from mike (sdn-ar-001txfworP071.dialsprint.net [168.191.159.55]) by avocet.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with SMTP id VAA13157 for ; Mon, 4 Sep 2000 21:11:12 -0700 (PDT) From: Michael Owens To: hackers@freebsd.org Subject: dlopen() Date: Mon, 4 Sep 2000 23:16:17 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00090423164501.01182@mike> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying an example I got from a magazine originally written for Linux which dynamically loads shared libraries and instantiates C++ classes within them. Being a recent FreeBSD convert, I intended to run this example on it. However, I am having a problem. I did read the man page for dlopen(), and searched the mailing lists for similar problems. Consequently, I learned to use -Wl,export-dynamic, but still have not seemed to resolve the problem: when the program calls dlopen to load the library, it returns ./libcircle.so: Undefined symbol "__pure_virtual" Now if I remove all pure virtual functions, it naturally just leads to some other symbol not being found, so I assume it's not a C++ related matter. Am I just not linking correctly? My makefile is as follows: --------- .cc.o: g++ -ggdb -c -fpic -fPIC $< default: make testdcl testdcl: testdcl.o g++ -Wl,-export-dynamic -o testdcl testdcl.o libcircle.so: circle.o g++ -shared -Wl,-export-dynamic -o libcircle.so circle.o libsquare.so: square.o g++ -shared -Wl,-export-dynamic -o libsquare.so square.o all: testdcl libcircle.so libsquare.so clean: rm -f *.so *.o testdcl -------- Any help would be greatly appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Sep 4 23:57:28 2000 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 88FDF37B42C for ; Mon, 4 Sep 2000 23:57:22 -0700 (PDT) Received: from localhost (lists@localhost) by security.za.net (8.9.3/8.9.3) with ESMTP id IAA30745 for ; Tue, 5 Sep 2000 08:57:13 +0200 (SAST) (envelope-from lists@security.za.net) Date: Tue, 5 Sep 2000 08:57:13 +0200 (SAST) From: Lists Account To: hackers@freebsd.org Subject: Kernel compile problem? 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 wondered if anyone could help me out here, Im trying to cvsup from 4.0-RELEASE to 4.1-STABLE and on a make depend on my kernel I get the following: ===> agp make: don't know how to make agp_if.c. Stop *** Error code 2 Stop in /usr/src/sys/modules. *** Error code 1 Anyone else getting this error on a build? I last cvsupped at 8:50am GMT+2 Thanks Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 0: 6: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 14C6F37B423 for ; Tue, 5 Sep 2000 00:05:47 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id AAA09065; Tue, 05 Sep 2000 00:05:32 -0700 Message-ID: <39B49B3C.4D5F0C64@urx.com> Date: Tue, 05 Sep 2000 00:05:32 -0700 From: Kent Stewart Organization: Dynacom Net X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Lists Account Cc: hackers@FreeBSD.ORG Subject: Re: Kernel compile problem? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lists Account wrote: > > Hi all, > > Just wondered if anyone could help me out here, Im trying to cvsup from > 4.0-RELEASE to 4.1-STABLE and on a make depend on my kernel I get the > following: It doesn't work this way. When you cvsup, you need to follow the recipe in /usr/src/UPDATING. There is a section on upgrading from 4.x to 4.1-stable. The safe route is to follow the buildworld, build[install]kernel, installworld sequence. Kent > > ===> agp > make: don't know how to make agp_if.c. Stop > *** Error code 2 > > Stop in /usr/src/sys/modules. > *** Error code 1 > > Anyone else getting this error on a build? > > I last cvsupped at 8:50am GMT+2 > > Thanks > > Andrew > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 0: 6:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2CE7837B423 for ; Tue, 5 Sep 2000 00:06:15 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA24954; Tue, 5 Sep 2000 01:06:12 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA58873; Tue, 5 Sep 2000 01:05:32 -0600 (MDT) Message-Id: <200009050705.BAA58873@harmony.village.org> To: Lists Account Subject: Re: Kernel compile problem? Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 05 Sep 2000 08:57:13 +0200." References: Date: Tue, 05 Sep 2000 01:05:32 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Lists Account writes: : Just wondered if anyone could help me out here, Im trying to cvsup from : 4.0-RELEASE to 4.1-STABLE and on a make depend on my kernel I get the : following: : : ===> agp : make: don't know how to make agp_if.c. Stop : *** Error code 2 : : Stop in /usr/src/sys/modules. : *** Error code 1 : : Anyone else getting this error on a build? Just those people that haven't read UPDATING :-) make buildkernel is your friend... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 0: 8: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kbgroup.co.nz (gateway.kbgroup.co.nz [203.96.151.81]) by hub.freebsd.org (Postfix) with ESMTP id E29E737B423; Tue, 5 Sep 2000 00:07:55 -0700 (PDT) Received: from kb_exchange.kbgroup.co.nz ([202.202.203.10]) by gateway.kbgroup.co.nz with ESMTP id <115201>; Tue, 5 Sep 2000 19:30:13 +1200 Received: by internet.kbgroup.co.nz with Internet Mail Service (5.5.2650.21) id ; Tue, 5 Sep 2000 19:18:26 +1200 Message-ID: <67B808B0DD93D211ABEE0000B498356B3617AF@internet.kbgroup.co.nz> From: "Dave Preece (KB Group)" To: Lists Account Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: RE: Kernel compile problem? MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 5 Sep 2000 19:30:03 +1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just wondered if anyone could help me out here, Im trying to > cvsup from > 4.0-RELEASE to 4.1-STABLE and on a make depend on my kernel I get the > following: > > ===> agp > make: don't know how to make agp_if.c. Stop > *** Error code 2 > > Anyone else getting this error on a build? Yup. I've spent the last hour or two banging my head on it. There's a variety of answers on freebsd-questions (http://www.freebsd.org/cgi/search.cgi?words=agp+cvsup&max=25&sort=score&sou rce=freebsd-questions). These include " 'make buildkernel' works fine ", "RTFM /usr/src/UPDATING" and "get usr-share as well". None of which work for me. I currently have a really minimal install, so I'm currently installing all the 4.0 sources to do a cvsup with src-all then a make buildkernel (or even a world) to see how it goes. Last time I tried cvsup'ing it was 3.3 to 4.0 and a complete disaster. Had to use the CD's in the end (me=lam3r). Dave BTW, Best directed onto -questions, por favor. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 0:15:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8A70E37B43F; Tue, 5 Sep 2000 00:15:18 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA24978; Tue, 5 Sep 2000 01:15:16 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA58950; Tue, 5 Sep 2000 01:14:36 -0600 (MDT) Message-Id: <200009050714.BAA58950@harmony.village.org> To: "Dave Preece (KB Group)" Subject: Re: Kernel compile problem? Cc: Lists Account , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG In-reply-to: Your message of "Tue, 05 Sep 2000 19:30:03 +1200." <67B808B0DD93D211ABEE0000B498356B3617AF@internet.kbgroup.co.nz> References: <67B808B0DD93D211ABEE0000B498356B3617AF@internet.kbgroup.co.nz> Date: Tue, 05 Sep 2000 01:14:36 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <67B808B0DD93D211ABEE0000B498356B3617AF@internet.kbgroup.co.nz> "Dave Preece (KB Group)" writes: : (http://www.freebsd.org/cgi/search.cgi?words=agp+cvsup&max=25&sort=score&sou : rce=freebsd-questions). These include " 'make buildkernel' works fine ", : "RTFM /usr/src/UPDATING" and "get usr-share as well". None of which work for : me. I currently have a really minimal install, so I'm currently installing : all the 4.0 sources to do a cvsup with src-all then a make buildkernel (or : even a world) to see how it goes. Ah. You need to have a complete make buildworld tree in place before doing the make buildkernel target. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 2:43: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tungsten.btinternet.com (tungsten.btinternet.com [194.73.73.81]) by hub.freebsd.org (Postfix) with ESMTP id 3B5F837B423 for ; Tue, 5 Sep 2000 02:43:00 -0700 (PDT) Received: from host62-7-73-207.btinternet.com ([62.7.73.207] helo=btinternet.com) by tungsten.btinternet.com with esmtp (Exim 3.03 #83) id 13WFFq-0003NJ-00 for freebsd-hackers@freebsd.org; Tue, 05 Sep 2000 10:42:58 +0100 Message-ID: <39B4BD1D.676139D4@btinternet.com> Date: Tue, 05 Sep 2000 10:30:05 +0100 From: John Toon X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Shared Memory Issues Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've scoured through the net and the mailing archives, but was unable to find any satisfactory information on a certain problem I'm suffering at the moment. After getting the dreaded "shmget() failed" error message, I have since tried several recompiles of the kernel to fix the problem. I added options SHMMAXPGS=16385 options SHMMAX=(SHMMAXPGS*PAGE_SIZE+1) to my new kernel and recompiled. However, under XFree86 4.0, I still seem to be getting shared memory issues. Compupic refuses to start under GNOME issuing X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 146 (MIT-SHM) Minor opcode of failed request: 1 (X_ShmAttach) Serial number of failed request: 2961 Current serial number in output stream: 2962 Yet works under VTWM - until I load up a few applications, when it terminates again, with the same problem. More annoyingly, FXTV also dies with the same problem. Next, I tried another kernel, this time with the following options: options SEMMNI=100 options SEMMNS=300 options SEMUME=100 options SEMMNU=150 options SHMMAXPGS=16385 I omitted the SHMMAX option, as I have read that this option is now deprecated. Unfortunately, this kernel was not better. I'm currently running FreeBSD 4.0-RELEASE. Several questions; 1. If I upgrade to 4.1-STABLE (which I will be soon), will the shared memory issue disappear? 2. I am not sure as to the exact options (and combination of options I should be choosing). My computer has 384MB of RAM - I want to be able to make *optimum* use of all that memory, and run X sessions with heavy loads - can someone suggest the particular values I should be using? 3. ...and of course, how do I fix this? With the amount of RAM I've got, getting memory issues is silly, so I would like to resolve this. Finally, can anyone recommend any books/URLs on the SYSV shared memory management? I'm curious to know more about the way different applications utilize memory; most applications run perfectly; the GIMP loads up in about 1 second. Thanks, John. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 3:35:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.dante.org.uk (alpha.dante.org.uk [193.63.211.19]) by hub.freebsd.org (Postfix) with ESMTP id E0B9D37B422 for ; Tue, 5 Sep 2000 03:35:36 -0700 (PDT) Received: from theta.dante.org.uk ([193.63.211.7]) by alpha.dante.org.uk with esmtp (Exim 3.12 #4) id 13WG4l-0003kk-00; Tue, 05 Sep 2000 11:35:35 +0100 Received: from localhost ([127.0.0.1] helo=dante.org.uk) by theta.dante.org.uk with esmtp (Exim 3.12 #4) id 13WG4k-0000A7-00; Tue, 05 Sep 2000 11:35:34 +0100 Message-ID: <39B4CC75.F6532F21@dante.org.uk> Date: Tue, 05 Sep 2000 11:35:34 +0100 From: Konstantin Chuguev Organization: Delivery of Advanced Networking Service to Europe Ltd. X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: en, ru MIME-Version: 1.0 To: John Toon Cc: freebsd-hackers@freebsd.org Subject: Re: Shared Memory Issues References: <39B4BD1D.676139D4@btinternet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Toon wrote: > Hi, > > I've scoured through the net and the mailing archives, but was unable to > find any satisfactory information on a certain problem I'm suffering at > the moment. > > After getting the dreaded "shmget() failed" error message, I have since > tried several recompiles of the kernel to fix the problem. > The same with me. > > I added > > options SHMMAXPGS=16385 > options SHMMAX=(SHMMAXPGS*PAGE_SIZE+1) > > to my new kernel and recompiled. > I tried this without success. > > However, under XFree86 4.0, I still seem to be getting shared memory > issues. > I'm using XFree86 3.3.6 with the server of 3.3.5. The problem is not in XFree, but in imlib. > > Compupic refuses to start under GNOME issuing > > X Error of failed request: BadAccess (attempt to access private > resource denied) > Major opcode of failed request: 146 (MIT-SHM) > Minor opcode of failed request: 1 (X_ShmAttach) > Serial number of failed request: 2961 > Current serial number in output stream: 2962 > > Yet works under VTWM - until I load up a few applications, when it > terminates again, with the same problem. More annoyingly, FXTV also dies > with the same problem. > > Next, I tried another kernel, this time with the following options: > > options SEMMNI=100 > options SEMMNS=300 > options SEMUME=100 > options SEMMNU=150 > options SHMMAXPGS=16385 > > I omitted the SHMMAX option, as I have read that this option is now > deprecated. Unfortunately, this kernel was not better. > For me, playing with SHM options made things worse than it was in the default SHM kernel configuration. > > I'm currently running FreeBSD 4.0-RELEASE. > > Several questions; > > 1. If I upgrade to 4.1-STABLE (which I will be soon), will the shared > memory issue disappear? I doubt so. I'm running 5.0-CURRENT, and still have the problem. -- * * Konstantin Chuguev - Application Engineer * * Francis House, 112 Hills Road * Cambridge CB2 1PQ, United Kingdom D A N T E WWW: http://www.dante.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 5:48:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palnet.com (mail.palnet.com [192.116.19.220]) by hub.freebsd.org (Postfix) with ESMTP id 15AEC37B422 for ; Tue, 5 Sep 2000 05:48:49 -0700 (PDT) Received: from nawari.palnet.com (dogbert.palnet.com [192.116.17.51]) by mail.palnet.com (8.9.3/8.9.3) with ESMTP id OAA49631; Tue, 5 Sep 2000 14:51:14 +0200 (IST) Message-Id: <5.0.0.13.0.20000905154701.01be28f8@mail.palnet.com> X-Sender: mustafa@mail.palnet.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.0.13 (Beta) Date: Tue, 05 Sep 2000 15:47:45 +0200 To: Konstantin Chuguev , John Toon From: Mustafa Deeb Subject: Re: Shared Memory Issues Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <39B4CC75.F6532F21@dante.org.uk> References: <39B4BD1D.676139D4@btinternet.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 I think that there is an application that is not releasing memory resources you can check that with ipcs and ipcsrm cheers At 11:35 AM 9/5/2000 +0100, Konstantin Chuguev wrote: >John Toon wrote: > > > Hi, > > > > I've scoured through the net and the mailing archives, but was unable to > > find any satisfactory information on a certain problem I'm suffering at > > the moment. > > > > After getting the dreaded "shmget() failed" error message, I have since > > tried several recompiles of the kernel to fix the problem. > > > >The same with me. > > > > > I added > > > > options SHMMAXPGS=16385 > > options SHMMAX=(SHMMAXPGS*PAGE_SIZE+1) > > > > to my new kernel and recompiled. > > > >I tried this without success. > > > > > However, under XFree86 4.0, I still seem to be getting shared memory > > issues. > > > >I'm using XFree86 3.3.6 with the server of 3.3.5. The problem is not in >XFree, but in imlib. > > > > > Compupic refuses to start under GNOME issuing > > > > X Error of failed request: BadAccess (attempt to access private > > resource denied) > > Major opcode of failed request: 146 (MIT-SHM) > > Minor opcode of failed request: 1 (X_ShmAttach) > > Serial number of failed request: 2961 > > Current serial number in output stream: 2962 > > > > Yet works under VTWM - until I load up a few applications, when it > > terminates again, with the same problem. More annoyingly, FXTV also dies > > with the same problem. > > > > Next, I tried another kernel, this time with the following options: > > > > options SEMMNI=100 > > options SEMMNS=300 > > options SEMUME=100 > > options SEMMNU=150 > > options SHMMAXPGS=16385 > > > > I omitted the SHMMAX option, as I have read that this option is now > > deprecated. Unfortunately, this kernel was not better. > > > >For me, playing with SHM options made things worse than it was in the >default SHM kernel configuration. > > > > > I'm currently running FreeBSD 4.0-RELEASE. > > > > Several questions; > > > > 1. If I upgrade to 4.1-STABLE (which I will be soon), will the shared > > memory issue disappear? > >I doubt so. I'm running 5.0-CURRENT, and still have the problem. > >-- > * * Konstantin Chuguev - Application Engineer > * * Francis House, 112 Hills Road > * Cambridge CB2 1PQ, United Kingdom > D A N T E WWW: http://www.dante.net > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 8: 2:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from host.cer.ntnu.edu.tw (cer.ntnu.edu.tw [140.122.119.9]) by hub.freebsd.org (Postfix) with ESMTP id 8A06B37B423 for ; Tue, 5 Sep 2000 08:01:59 -0700 (PDT) Received: (from clive@localhost) by host.cer.ntnu.edu.tw (8.11.0/8.11.0) id e85F1AI09654; Tue, 5 Sep 2000 23:01:10 +0800 (CST) (envelope-from clive) Date: Tue, 5 Sep 2000 23:01:10 +0800 From: Clive Lin To: John Toon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Shared Memory Issues Message-ID: <20000905230110.A9425@host.cer.ntnu.edu.tw> Reply-To: Clive Lin References: <39B4BD1D.676139D4@btinternet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39B4BD1D.676139D4@btinternet.com>; from j.a.toon@btinternet.com on Tue, Sep 05, 2000 at 10:30:05AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Tue, Sep 05, 2000 at 10:30:05AM +0100, John Toon wrote: > options SEMMNI=100 > options SEMMNS=300 > options SEMUME=100 > options SEMMNU=150 > options SHMMAXPGS=16385 Would you like to try below ? options SHMALL=4097 options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAXPGS=4097 options SHMMIN=2 options SHMMNI=512 options SHMSEG=1024 That's all SHM* tuning I have in my kernel configuration. I could have gnome, enlightenment, samba and postgresql7 running at the same time without any problem... > I omitted the SHMMAX option, as I have read that this option is now > deprecated. Unfortunately, this kernel was not better. Hm... long time ago I asked google about those SHM* and I thought SHMSEG may be the key point. Because SHMSEG stands for maximum number of shared segments per process. > I'm currently running FreeBSD 4.0-RELEASE. > > Several questions; > > 1. If I upgrade to 4.1-STABLE (which I will be soon), will the shared > memory issue disappear? I have 5.0 and 4.1 machines with the same SHM* tuning above. All work fine, even with some gtk theme with lots pixmaps. > 2. I am not sure as to the exact options (and combination of options I > should be choosing). My computer has 384MB of RAM - I want to be able to > make *optimum* use of all that memory, and run X sessions with heavy > loads - can someone suggest the particular values I should be using? Hm... my experience tells me that those SHM* are not the problem. The X-TT, netscape, mozilla, (x)emacs, cvsupd and so on are real memory monsters. > 3. ...and of course, how do I fix this? With the amount of RAM I've got, > getting memory issues is silly, so I would like to resolve this. > > Finally, can anyone recommend any books/URLs on the SYSV shared memory > management? I'm curious to know more about the way different > applications utilize memory; most applications run perfectly; the GIMP > loads up in about 1 second. Ask google ? It's really powerful... About the SYSV options, I have small notes about them. Though, I couldn't make sure they are 100% correct. It just works, and I have no more interests to dig more :-> SHMALL max shared mem system wide (in pages). SHMMAX max shared memory segment size (bytes). SHMMIN min shared memory segment size (bytes). SHMMNI max num of shared segments system wide. SHMSEG maximum number of shared segments per process. Regards, Clive -- CirX - This site doesnt' exist. 9c k9o h9 s1bg s1f, 7v .y xqx a sj m8r ffg1 vg5 a6 asox tmul h38. ant sj m8r ob ? 1fj mwby a1 tao vg5. soq df v' .a. CirX. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 9:24: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.uni-bielefeld.de (mail2.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id D569637B43F for ; Tue, 5 Sep 2000 09:24:04 -0700 (PDT) Received: from frolic.no-support.loc (ppp36-292.hrz.uni-bielefeld.de [129.70.37.36]) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.4.0.2000.05.17.04.13.p6) with ESMTP id <0G0F00G0W9K0TK@mail.uni-bielefeld.de> for hackers@FreeBSD.ORG; Tue, 5 Sep 2000 18:24:02 +0200 (MET DST) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id SAA00683; Tue, 05 Sep 2000 18:20:24 +0200 (CEST envelope-from bjoern) Date: Tue, 05 Sep 2000 18:20:23 +0200 From: Bjoern Fischer Subject: Re: dlopen() In-reply-to: <00090423164501.01182@mike>; from owensmk@earthlink.net on Mon, Sep 04, 2000 at 11:16:17PM -0500 To: Michael Owens Cc: hackers@FreeBSD.ORG Message-id: <20000905182023.A255@frolic.no-support.loc> 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 References: <00090423164501.01182@mike> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 04, 2000 at 11:16:17PM -0500, Michael Owens wrote: [...] > -Wl,export-dynamic, but still have not seemed to resolve the problem: whe= n the > program calls dlopen to load the library, it returns >=20 > ./libcircle.so: Undefined symbol "__pure_virtual" It seems that this is a libgcc issue. When linking `testdcl', the linker does not add unneeded symbols from libgcc. Symbols from libgcc needed in libcircle.so or libsquare.so, but unneeded in testdcl won't get resolved. Try linking libgcc to libcircle.so and libsquare.so. Look after how g++ invokes the linker (g++ -v), you may have to call the linker by yourself. This is a dirty hack. The proper solution is to convert libgcc into a shared library. This work is already under way. Bj=F6rn --=20 -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+=20 ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 9:24:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id EB77E37B42C; Tue, 5 Sep 2000 09:24:19 -0700 (PDT) Received: from newsguy.com (p19-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.20]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id BAA11545; Wed, 6 Sep 2000 01:24:18 +0900 (JST) Message-ID: <39B51E16.E8AD4BC8@newsguy.com> Date: Wed, 06 Sep 2000 01:23:51 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: bp@freebsd.org, hackers@freebsd.org Subject: Multiple kernels selector... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is an adaptation from menuconf.4th: \ Simple greeting screen, presenting basic options. \ XXX This is far too trivial - I don't have time now to think \ XXX about something more fancy... :-/ \ $FreeBSD: /c/ncvs/src/share/examples/bootforth/menuconf.4th,v 1.4 1999/09/29 04:46:01 dcs Exp $ : title ." Welcome to BootFORTH!" cr cr ; : menu ." 1. Start FreeBSD with /boot/stable.conf." cr ." 2. Start FreeBSD with /boot/current.conf." cr ." 3. Start FreeBSD with standard configuration. " cr ." 4. Reboot." cr cr ; : tkey ( d -- flag | char ) seconds + begin 1 while dup seconds u< if drop -1 exit then key? if drop key exit then repeat ; : prompt ." Enter your option (1,2,3,4): " 10 tkey dup 32 = if drop key then dup 0< if drop 51 then dup emit cr ; : (reboot) 0 reboot ; : main_menu begin 1 while title menu prompt cr cr dup 49 = if drop ." Loading /boot/stable.conf. Please wait..." cr s" /boot/stable.conf" read-conf 0 boot-conf exit then dup 50 = if drop ." Loading /boot/current.conf. Please wait..." cr s" /boot/current.conf" read-conf 0 boot-conf exit then dup 51 = if drop ." Proceeding with standard boot. Please wait..." cr 0 boot-conf exit then dup 52 = if drop ['] (reboot) catch abort" Error rebooting" then ." Key " emit ." is not a valid option!" cr ." Press any key to continue..." key drop cr repeat ; This reads stable.conf or current.conf depending on option 1 or 2 (or standard boot for option 3), and then boots. You can simplify it in the following way. Replace the lines s" /boot/stable.conf" read-conf 0 boot-conf exit (and similar for current.conf) with the line s" kernel.stable" 1 boot-conf exit and you'll just try to boot the standard configuration using the kernel named kernel.stable. If you need to match modules to kernels, keep both kernel and modules in the same directory, under either root or /boot, for each kernel/modules set. Then, if you want to boot the kernel and modules inside the directory /boot/stable or /stable, for example, you replace the two lines with: s" stable" 1 boot-conf exit You can, of course, add more options easily. And you can mix all of the above options: .conf files names, kernel names and directory names, depending on what option you choose. Put this stuff in a file (asciimenu.4th, for example) and then replace the "start" on loader.rc with the following: s" /boot/asciimenu.4th" fopen dup fload fclose initialize drop main_menu -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@white.bunnies.bsdconspiracy.net OK, so the solar flares are my fault.. I am sorry, ok?!?! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 11:46:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.wertep.com (relay2.wertep.com [194.44.90.130]) by hub.freebsd.org (Postfix) with ESMTP id 579C637B422 for ; Tue, 5 Sep 2000 11:46:39 -0700 (PDT) Received: from She.wertep.com (she-tun-proxy [192.168.252.2]) by relay2.wertep.com (8.9.3/8.9.3) with ESMTP id VAA29142 for ; Tue, 5 Sep 2000 21:46:27 +0300 (EEST) (envelope-from petro@She.wertep.com) Received: from localhost (petro@localhost) by She.wertep.com (8.9.3/8.9.3) with ESMTP id VAA00429 for ; Tue, 5 Sep 2000 21:46:25 +0300 (EEST) (envelope-from petro@She.wertep.com) Date: Tue, 5 Sep 2000 21:46:20 +0300 (EEST) From: petro To: freebsd-hackers@FreeBSD.ORG Subject: Need quick help. 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 tried to change smth in my interfaces and now receive such message in /var/log/messages /kernel: arp: IP_number is on rl2 but got reply from MAC_ADDRESS an ed1 Please need quick help. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 11:51:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id A371D37B422 for ; Tue, 5 Sep 2000 11:51:26 -0700 (PDT) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id UAA20928; Tue, 5 Sep 2000 20:52:22 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200009051852.UAA20928@info.iet.unipi.it> Subject: Re: Need quick help. In-Reply-To: from petro at "Sep 5, 2000 09:46:20 pm" To: petro Date: Tue, 5 Sep 2000 20:52:22 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I tried to change smth in my interfaces and now receive such message in > /var/log/messages > /kernel: arp: IP_number is on rl2 but got reply from MAC_ADDRESS an ed1 presumably you have bridging enabled ? cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 12:34: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mir.kapi.net (mir.kapi.net [195.165.21.13]) by hub.freebsd.org (Postfix) with ESMTP id 9A53A37B42C for ; Tue, 5 Sep 2000 12:34:05 -0700 (PDT) Received: from kapi.net (kapi.net [195.165.21.10]) by mir.kapi.net (8.9.3/8.9.3) with ESMTP id WAA34709 for ; Tue, 5 Sep 2000 22:33:58 +0300 (EEST) (envelope-from esko@kapi.net) Received: from localhost (esko@localhost) by kapi.net (8.9.2/8.9.3) with ESMTP id WAA73640 for ; Tue, 5 Sep 2000 22:33:58 +0300 (EEST) (envelope-from esko@kapi.net) X-Authentication-Warning: kapi.net: esko owned process doing -bs Date: Tue, 5 Sep 2000 22:33:58 +0300 (EEST) From: Esko Petteri Matinsola X-Sender: esko@sputnik To: hackers@freebsd.org Subject: Promise PDC20265 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have Asus A7V motherboard that has integrated UDMA100-controller PDC20265 made by Promise and Maxtor 54098H8 hard disk. When plugged to the UDMA66-controller the Maxtor works properly, boots and is fast. But when plugged to the PDC20265 BIOS detects it, kernel boots but don't detect the controller nor the disk so it complains about root not found. I checked the ata driver (I have 4.1-STABLE by yesterday) and it has support for Promise 100 (I presume it's PDC20265) but it doesn't work ? Any suggestions will be appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 17: 4: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id E689637B43E for ; Tue, 5 Sep 2000 17:04:05 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e8603uS87326; Tue, 5 Sep 2000 17:03:56 -0700 (PDT) Date: Tue, 5 Sep 2000 17:03:56 -0700 (PDT) From: Doug White To: petro Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Need quick help. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Sep 2000, petro wrote: > I tried to change smth in my interfaces and now receive such message in > /var/log/messages > /kernel: arp: IP_number is on rl2 but got reply from MAC_ADDRESS an ed1 Your networks are broken. It appears the two interfaces are plugged into the same physical network. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 17: 7:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from neodymium.btinternet.com (neodymium.btinternet.com [194.73.73.83]) by hub.freebsd.org (Postfix) with ESMTP id C82C737B423 for ; Tue, 5 Sep 2000 17:07:16 -0700 (PDT) Received: from host213-123-24-15.btinternet.com ([213.123.24.15] helo=btinternet.com) by neodymium.btinternet.com with esmtp (Exim 3.03 #83) id 13WSkE-0007Cn-00 for freebsd-hackers@freebsd.org; Wed, 06 Sep 2000 01:07:15 +0100 Message-ID: <39B58ABD.1B215190@btinternet.com> Date: Wed, 06 Sep 2000 01:07:25 +0100 From: John Toon X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: Shared Memory Issues References: <39B4BD1D.676139D4@btinternet.com> <20000905230110.A9425@host.cer.ntnu.edu.tw> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Clive Lin wrote: > > Hm... long time ago I asked google about those SHM* and > I thought SHMSEG may be the key point. Because SHMSEG stands for > maximum number of shared segments per process. Fantastic! You're absolutely correct. Everything is now working perfectly. My mistake had been to think that the system was running out of actual shared memory pages, but successive increases of the maximum pages had no effect. The actual problem, as you've rightly pointed out, was that each process was running out of shared memory segments... Incidentally, how many pages does a segment in FreeBSD correspond to? 4? 16? > Ask google ? It's really powerful... I know ;^) Google is considerably better than any other search engine... > About the SYSV options, I have small notes about them. Though, I couldn't > make sure they are 100% correct. It just works, and I have no more interests > to dig more :-> > > SHMALL max shared mem system wide (in pages). > SHMMAX max shared memory segment size (bytes). > SHMMIN min shared memory segment size (bytes). > SHMMNI max num of shared segments system wide. > SHMSEG maximum number of shared segments per process. > > Regards, > Clive Just as a side note, are there any commands available that will inform me how many shared memory pages are currently being used by the running system? Thanks. -- :s/Windows/UNIX John Toon | j.a.toon@btinternet.com | "Sonnilon" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 17:11:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 9132837B422 for ; Tue, 5 Sep 2000 17:11:41 -0700 (PDT) Received: (from newton@localhost) by gizmo.internode.com.au (8.11.0/8.9.3) id e860BZf54487 for freebsd-hackers@freebsd.org; Wed, 6 Sep 2000 09:41:35 +0930 (CST) (envelope-from newton) Date: Wed, 6 Sep 2000 09:41:35 +0930 From: Mark Newton To: freebsd-hackers@freebsd.org Subject: GeForce 6600 driver Message-ID: <20000906094135.A54461@internode.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nvidia have released source code for a linux kernel driver and an XFree86 module which provides 3D accelleration via OpenGL. Having just acquired one of these boards, I'm intersted in knowing whether anyone has been interested in porting that driver from Linux to FreeBSD. I believe the XFree86 module should work without modification (include file locations notwithstanding). The kernel module might require a bit of work, though. Has anyone already made any progress on this which I could build on? Or any useful contacts inside Nvidia who could help out? Thanks, - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 18:28:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from thelma.NVidia.COM (nvgate.nvidia.com [140.174.105.2]) by hub.freebsd.org (Postfix) with ESMTP id 47E2437B424 for ; Tue, 5 Sep 2000 18:28:07 -0700 (PDT) Received: from exchange.nvidia.com (exchange [172.16.30.109]) by thelma.NVidia.COM (8.8.8+Sun/8.8.8) with ESMTP id SAA11424 for ; Tue, 5 Sep 2000 18:28:06 -0700 (PDT) Received: by exchange.nvidia.com with Internet Mail Service (5.5.2650.21) id ; Tue, 5 Sep 2000 18:28:06 -0700 Message-ID: <04311C809F7CD411B97D00D0B78EC6B90C6650@nvapollo.nvidia.com> From: Dennis Wong To: "'freebsd-hackers@freebsd.org'" Subject: FW: GeForce 6600 driver Date: Tue, 5 Sep 2000 18:25:50 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI.. > -----Original Message----- > From: Nick Triantos > Sent: Tuesday, September 05, 2000 6:20 PM > To: Dennis Wong > Subject: RE: GeForce 6600 driver > > Hi Dennis, > > Actually, we haven't done it yet. However, all of our major Linux > dependencies should be in the 3 source files which ship as part of our > kernel module's tarball. If those files were ported to BSD, in theory > everything else "should" work, though I'm sure we'd need a bit of testing > before that became fully true. > > We do plan to start on a FreeBSD port soon, we just haven't had time yet. > However, if there's someone interested in trying to help do this port, > we'd be happy to talk to them. They can email me at nick@nvidia.com. > > BTW, we did also speak with the FreeBSD guys at linuxworld, I think we > have a possible way we could check our code into the FreeBSD tree, which > would be great once we do get it working well. > > Feel free to post this, btw. I also really like BSD. > > -Nick > > -----Original Message----- > From: Dennis Wong > Sent: Tuesday, September 05, 2000 5:28 PM > To: Nick Triantos > Subject: FW: GeForce 6600 driver > > ...So, can we help these guys out? I love FreeBSD.. > > -----Original Message----- > From: Mark Newton [SMTP:newton@internode.com.au] > Sent: Tuesday, September 05, 2000 5:12 PM > To: freebsd-hackers@freebsd.org > Subject: GeForce 6600 driver > > Nvidia have released source code for a linux kernel driver and an XFree86 > module which provides 3D accelleration via OpenGL. > > Having just acquired one of these boards, I'm intersted in knowing whether > anyone has been interested in porting that driver from Linux to FreeBSD. > > I believe the XFree86 module should work without modification (include > file locations notwithstanding). The kernel module might require a bit > of work, though. > > Has anyone already made any progress on this which I could build on? Or > any useful contacts inside Nvidia who could help out? > > Thanks, > > - mark > > -- > Mark Newton Email: newton@internode.com.au > (W) > Network Engineer Email: newton@atdot.dotat.org > (H) > Internode Systems Pty Ltd Desk: +61-8-82232999 > "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Sep 5 23:50:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C5DE137B423 for ; Tue, 5 Sep 2000 23:50:31 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA39695; Wed, 6 Sep 2000 08:52:04 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200009060652.IAA39695@freebsd.dk> Subject: Re: Promise PDC20265 In-Reply-To: from Esko Petteri Matinsola at "Sep 5, 2000 10:33:58 pm" To: esko@kapi.net (Esko Petteri Matinsola) Date: Wed, 6 Sep 2000 08:52:04 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Esko Petteri Matinsola wrote: > Hello, I have Asus A7V motherboard that has integrated UDMA100-controller > PDC20265 made by Promise and Maxtor 54098H8 hard disk. > > When plugged to the UDMA66-controller the Maxtor works properly, boots and > is fast. But when plugged to the PDC20265 BIOS detects it, kernel boots > but don't detect the controller nor the disk so it complains about root > not found. > > I checked the ata driver (I have 4.1-STABLE by yesterday) and it has > support for Promise 100 (I presume it's PDC20265) but it doesn't work ? > > Any suggestions will be appreciated. I have it in my local tree, it should go in soon... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 3:17:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from genius.systems.pavilion.net (genius.systems.pavilion.net [212.74.1.100]) by hub.freebsd.org (Postfix) with ESMTP id 4BE4B37B423; Wed, 6 Sep 2000 03:17:14 -0700 (PDT) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 79EB09B40; Wed, 6 Sep 2000 11:17:13 +0100 (BST) Date: Wed, 6 Sep 2000 11:17:13 +0100 From: Josef Karthauser To: Poul-Henning Kamp Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: looking for "microuptime went backwards" victims... Message-ID: <20000906111713.E1081@pavilion.net> Mail-Followup-To: Josef Karthauser , Poul-Henning Kamp , current@FreeBSD.ORG, hackers@FreeBSD.ORG References: <53059.968085674@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <53059.968085674@critter>; from phk@FreeBSD.ORG on Mon, Sep 04, 2000 at 06:41:14PM +0200 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got this last night running 'mtv' on a system with heavy disk I/O. The errors were: Sep 5 23:12:14 genius /kernel: pcm0: hwptr went backwards 8208 -> 8192 Sep 5 23:12:47 genius /kernel: pcm0: hwptr went backwards 8420 -> 8192 Sep 5 23:12:57 genius /kernel: pcm0: hwptr went backwards 8212 -> 8192 Sep 5 23:13:04 genius /kernel: pcm0: hwptr went backwards 8196 -> 8192 Sep 5 23:13:21 genius /kernel: pcm0: hwptr went backwards 8208 -> 8192 etc. Joe FreeBSD genius.systems.pavilion.net 5.0-CURRENT FreeBSD 5.0-CURRENT #11: Tue Sep 5 12:45:45 BST 2000 joe@genius.systems.pavilion.net:/usr/obj/usr/src/sys/GENIUS i386 On Mon, Sep 04, 2000 at 06:41:14PM +0200, Poul-Henning Kamp wrote: > > I'm looking for the remaining victims of the dreaded "microuptime > went backwards" message. > > If you can reliably reproduce the problem, please contact me, so > we can arrange for some very detailed tracing to try to find out > what exactly is going on. I have not been able to trigger the > problem in my lab in a long time. > > If you see the message only occationally, please try the attached > patch and let me know if this changes the picture. The patch is > not meant as a fix, but it might reduce the impact of this condition > considerably when it happens. Basically by reducing the width of > the timecounter the magnitude of the hit we take if the timecounter > goes backwards is reduced from about an hour to approx 110msec. > > Reducing the width to less than 17 bits starts to run the risk of > ambiguity due to clock rollover. > > This patch may not be safe with PCAUDIO. > > Poul-Henning > > Index: clock.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v > retrieving revision 1.155 > diff -u -r1.155 clock.c > --- clock.c 2000/07/30 21:05:22 1.155 > +++ clock.c 2000/09/04 16:34:16 > @@ -194,7 +194,7 @@ > static struct timecounter i8254_timecounter = { > i8254_get_timecount, /* get_timecount */ > 0, /* no poll_pps */ > - ~0u, /* counter_mask */ > + 0x1ffff, /* counter_mask */ > 0, /* frequency */ > "i8254" /* name */ > }; > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD coreteam member | 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 -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 3:26: 6 2000 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 D65F537B422; Wed, 6 Sep 2000 03:25:56 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e86APrN64556; Wed, 6 Sep 2000 12:25:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Josef Karthauser Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: looking for "microuptime went backwards" victims... In-Reply-To: Your message of "Wed, 06 Sep 2000 11:17:13 BST." <20000906111713.E1081@pavilion.net> Date: Wed, 06 Sep 2000 12:25:53 +0200 Message-ID: <64554.968235953@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Uhm, that is from the sound driver, not from the timecounter... Poul-Henning In message <20000906111713.E1081@pavilion.net>, Josef Karthauser writes: >I got this last night running 'mtv' on a system with heavy disk I/O. >The errors were: > >Sep 5 23:12:14 genius /kernel: pcm0: hwptr went backwards 8208 -> 8192 >Sep 5 23:12:47 genius /kernel: pcm0: hwptr went backwards 8420 -> 8192 >Sep 5 23:12:57 genius /kernel: pcm0: hwptr went backwards 8212 -> 8192 >Sep 5 23:13:04 genius /kernel: pcm0: hwptr went backwards 8196 -> 8192 >Sep 5 23:13:21 genius /kernel: pcm0: hwptr went backwards 8208 -> 8192 > >etc. > >Joe > >FreeBSD genius.systems.pavilion.net 5.0-CURRENT FreeBSD 5.0-CURRENT #11: Tue Sep 5 12:45:45 BST 2000 joe@genius.systems.pavilion.net:/usr/obj/usr/src/sys/GENIUS i386 > >On Mon, Sep 04, 2000 at 06:41:14PM +0200, Poul-Henning Kamp wrote: >> >> I'm looking for the remaining victims of the dreaded "microuptime >> went backwards" message. >> >> If you can reliably reproduce the problem, please contact me, so >> we can arrange for some very detailed tracing to try to find out >> what exactly is going on. I have not been able to trigger the >> problem in my lab in a long time. >> >> If you see the message only occationally, please try the attached >> patch and let me know if this changes the picture. The patch is >> not meant as a fix, but it might reduce the impact of this condition >> considerably when it happens. Basically by reducing the width of >> the timecounter the magnitude of the hit we take if the timecounter >> goes backwards is reduced from about an hour to approx 110msec. >> >> Reducing the width to less than 17 bits starts to run the risk of >> ambiguity due to clock rollover. >> >> This patch may not be safe with PCAUDIO. >> >> Poul-Henning >> >> Index: clock.c >> =================================================================== >> RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v >> retrieving revision 1.155 >> diff -u -r1.155 clock.c >> --- clock.c 2000/07/30 21:05:22 1.155 >> +++ clock.c 2000/09/04 16:34:16 >> @@ -194,7 +194,7 @@ >> static struct timecounter i8254_timecounter = { >> i8254_get_timecount, /* get_timecount */ >> 0, /* no poll_pps */ >> - ~0u, /* counter_mask */ >> + 0x1ffff, /* counter_mask */ >> 0, /* frequency */ >> "i8254" /* name */ >> }; >> >> -- >> Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 >> phk@FreeBSD.ORG | TCP/IP since RFC 956 >> FreeBSD coreteam member | 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 > >-- >Josef Karthauser FreeBSD: How many times have you booted today? >Technical Manager Viagra for your server (http://www.uk.freebsd.org) >Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | 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 Sep 6 6: 2: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id EDA3437B422 for ; Wed, 6 Sep 2000 06:01:59 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id DD0336A901 for ; Wed, 6 Sep 2000 15:01:58 +0200 (CEST) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.04) id A11886FC013A; Wed, 06 Sep 2000 15:05:28 +0200 Message-Id: <4.3.2.7.2.20000906145953.00d07900@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 06 Sep 2000 15:02:05 +0200 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: Token Ring ?? 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 We deal lot with AS/400 customers with TRN systems. I see 4.1 release still doesn't have a TRN card supported. Anybody got any ideas how to support TRN in FreeBSD? Len http://BIND8NT.MEIway.com: ISC BIND 8.2.2 p5 installable binary for NT4 http://IMGate.MEIway.com: Build free, hi-perf, anti-spam mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 6:12:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id BB49137B422 for ; Wed, 6 Sep 2000 06:12:49 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id HAA31151 for ; Wed, 6 Sep 2000 07:12:47 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id HAA68224 for ; Wed, 6 Sep 2000 07:12:03 -0600 (MDT) Message-Id: <200009061312.HAA68224@harmony.village.org> To: hackers@freebsd.org Subject: FYI: RSA Donated to the public domain Date: Wed, 06 Sep 2000 07:12:03 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://www.rsasecurity.com/news/pr/000906-1.html RSA Security Releases RSA Encryption Algorithm into Public Domain .... Maybe this means that the breakage in -current won't last too long :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 6:18:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D513837B423 for ; Wed, 6 Sep 2000 06:18:32 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id HAA31193 for ; Wed, 6 Sep 2000 07:18:31 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id HAA68280 for ; Wed, 6 Sep 2000 07:17:47 -0600 (MDT) Message-Id: <200009061317.HAA68280@harmony.village.org> Subject: Re: FYI: RSA Donated to the public domain To: hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 06 Sep 2000 07:12:03 MDT." <200009061312.HAA68224@harmony.village.org> References: <200009061312.HAA68224@harmony.village.org> Date: Wed, 06 Sep 2000 07:17:47 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009061312.HAA68224@harmony.village.org> Warner Losh writes: : RSA Security Releases RSA Encryption Algorithm into Public Domain Note that other information at the site says that RSAREF isn't released into the public domain. Its use is still governed by copyright law, so we'll have to use the international version of RSAREF if we want to get RSA into -current. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 6:18:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from genius.systems.pavilion.net (genius.systems.pavilion.net [212.74.1.100]) by hub.freebsd.org (Postfix) with ESMTP id 18E0437B422; Wed, 6 Sep 2000 06:18:34 -0700 (PDT) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 3FBDB9B41; Wed, 6 Sep 2000 14:18:33 +0100 (BST) Date: Wed, 6 Sep 2000 14:18:33 +0100 From: Josef Karthauser To: Poul-Henning Kamp Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: looking for "microuptime went backwards" victims... Message-ID: <20000906141833.I1081@pavilion.net> Mail-Followup-To: Josef Karthauser , Poul-Henning Kamp , current@FreeBSD.ORG, hackers@FreeBSD.ORG References: <20000906111713.E1081@pavilion.net> <64554.968235953@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <64554.968235953@critter>; from phk@critter.freebsd.dk on Wed, Sep 06, 2000 at 12:25:53PM +0200 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 06, 2000 at 12:25:53PM +0200, Poul-Henning Kamp wrote: > > Uhm, that is from the sound driver, not from the timecounter... > > Poul-Henning Oops, "You are in a maze of twisty passages all alike. Which direction do you want to go?". Joe > In message <20000906111713.E1081@pavilion.net>, Josef Karthauser writes: > >I got this last night running 'mtv' on a system with heavy disk I/O. > >The errors were: > > > >Sep 5 23:12:14 genius /kernel: pcm0: hwptr went backwards 8208 -> 8192 > >Sep 5 23:12:47 genius /kernel: pcm0: hwptr went backwards 8420 -> 8192 > >Sep 5 23:12:57 genius /kernel: pcm0: hwptr went backwards 8212 -> 8192 > >Sep 5 23:13:04 genius /kernel: pcm0: hwptr went backwards 8196 -> 8192 > >Sep 5 23:13:21 genius /kernel: pcm0: hwptr went backwards 8208 -> 8192 -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 6:27:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from online.thecia.ie (online.thecia.ie [159.134.244.168]) by hub.freebsd.org (Postfix) with ESMTP id 43B4C37B422 for ; Wed, 6 Sep 2000 06:27:08 -0700 (PDT) Received: from prospero.office.thecia.ie (osi.office.thecia.ie [10.0.0.2]) by online.thecia.ie (8.10.1/8.10.1) with SMTP id e86ELgg28240; Wed, 6 Sep 2000 14:21:42 GMT From: "Barry O'Mahony" Date: Wed, 06 Sep 2000 14:27:41 GMT Message-ID: <20000906.14274100@prospero.office.thecia.ie> Subject: Re: Token Ring ?? To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Reply-To: baz@thecia.ie In-Reply-To: <4.3.2.7.2.20000906145953.00d07900@mail.Go2France.com> References: <4.3.2.7.2.20000906145953.00d07900@mail.Go2France.com> X-Mailer: Mozilla/3.0 (compatible; StarOffice/5.1; Linux) X-Priority: 3 (Normal) 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 AHHHHHHHHHHHHHHHHHHHHHHHHHHHHH No Token Ring Bad Token Ring...... :) I Had to do this about 2 months ago for a client. And to be quite=20 honest, IT WAS AWEFUL!!!!!!!! I ended up just installing Win98 (I used to be a linux freak, Then this was the final straw,=20 installation was no fun Long Live Chuckie) Nice support would be good,=20 But God.....=20 Why Token Ring? :) > We deal lot with AS/400 customers with TRN systems. I see 4.1 release > still doesn't have a TRN card supported. > Anybody got any ideas how to support TRN in FreeBSD? > Len ################################# http://www.theyshoulddie.com # # Making the world a better place,# one person at a time. # ################################# To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 7:10:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtprch2.nortel.com (smtprch2.nortelnetworks.com [192.135.215.15]) by hub.freebsd.org (Postfix) with ESMTP id 999E337B422 for ; Wed, 6 Sep 2000 07:10:22 -0700 (PDT) Received: from zrchb213.us.nortel.com (actually zrchb213) by smtprch2.nortel.com; Wed, 6 Sep 2000 09:02:38 -0500 Received: by zrchb213.us.nortel.com with Internet Mail Service (5.5.2652.35) id ; Wed, 6 Sep 2000 09:06:17 -0500 Message-ID: From: "Hao Zhang" To: freebsd-hackers@FreeBSD.ORG Subject: Duplicating packets Date: Wed, 6 Sep 2000 09:06:07 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.35) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0180B.99D98450" X-Orig: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0180B.99D98450 Content-Type: text/plain; charset="iso-8859-1" I am doing some testing on FreeBSD 3.3 platform by sending some UDP packets thru FreeBSD routers. It's found that FreeBSD duplicates some packet. That results in that the received packet are more than sent ones. How can I disable the duplication in FreeBSD config. Or did I do some wrong in the FreeBSD config. The FreeBSD 3.3 is running on Pentium III, and NIC is 3C905B-Tx. Thanks in advance for any comments. - Hao ------_=_NextPart_001_01C0180B.99D98450 Content-Type: text/html; charset="iso-8859-1" Duplicating packets

I am doing some testing on FreeBSD 3.3 platform by sending some UDP packets
thru FreeBSD routers. It's found that FreeBSD duplicates some packet.
That results in that the received packet are more than sent ones. How
can I disable the duplication in FreeBSD config. Or did I do some wrong
in the FreeBSD config. The FreeBSD 3.3 is running on Pentium III, and NIC is
3C905B-Tx.

Thanks in advance for any comments.

- Hao

------_=_NextPart_001_01C0180B.99D98450-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 7:18:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 5A9D637B423; Wed, 6 Sep 2000 07:18:43 -0700 (PDT) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.9.3/8.9.3) id QAA21384; Wed, 6 Sep 2000 16:18:23 +0200 (CEST) (envelope-from asmodai) Date: Wed, 6 Sep 2000 16:18:22 +0200 From: Jeroen Ruigrok van der Werven To: Dennis Wong , Nick Triantos Cc: "'freebsd-hackers@freebsd.org'" , Doug Rabson Subject: Re: FW: GeForce 6600 driver Message-ID: <20000906161822.M17616@lucifer.bart.nl> References: <04311C809F7CD411B97D00D0B78EC6B90C6650@nvapollo.nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <04311C809F7CD411B97D00D0B78EC6B90C6650@nvapollo.nvidia.com>; from DWong@nvidia.com on Tue, Sep 05, 2000 at 06:25:50PM -0700 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Dennis, Nick, et al. -On [20000906 03:30], Dennis Wong (DWong@nvidia.com) wrote: > >> -----Original Message----- >> From: Nick Triantos >> Sent: Tuesday, September 05, 2000 6:20 PM >> To: Dennis Wong >> Subject: RE: GeForce 6600 driver >> >> Hi Dennis, >> >> Actually, we haven't done it yet. However, all of our major Linux >> dependencies should be in the 3 source files which ship as part of our >> kernel module's tarball. If those files were ported to BSD, in theory >> everything else "should" work, though I'm sure we'd need a bit of testing >> before that became fully true. >> >> We do plan to start on a FreeBSD port soon, we just haven't had time yet. >> However, if there's someone interested in trying to help do this port, >> we'd be happy to talk to them. They can email me at nick@nvidia.com. Doug Rabson is the person responsible for the agp miniport driver currently in FreeBSD and I believe he is also a programmer working on the Direct Rendering Infrastructure over at Sourceforge. Basically what should require work is probably the detection of your [Nvidia] cards and its subsequent support in DRI. I might be a bit off here, but I am sure one of my more knowledgable committers or fellow BSD users will correct me if wrong. >> BTW, we did also speak with the FreeBSD guys at linuxworld, I think we >> have a possible way we could check our code into the FreeBSD tree, which >> would be great once we do get it working well. There's the opportunity of one or more of your people to become a FreeBSD committer, or you can proxy through a committer, such as Mike Smith is doing for Adaptec's DPT driver. >> Feel free to post this, btw. I also really like BSD. Nice to see some BSD interest from the major companies aside from all the Linux hype. =) You cannot believe how happy I am to read things like this. Kind regards, -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Lead us not into temptation, but deliver us from evil... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 7:19:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 470CC37B43E for ; Wed, 6 Sep 2000 07:19:37 -0700 (PDT) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.9.3/8.9.3) id QAA21398; Wed, 6 Sep 2000 16:19:19 +0200 (CEST) (envelope-from asmodai) Date: Wed, 6 Sep 2000 16:19:19 +0200 From: Jeroen Ruigrok van der Werven To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Token Ring ?? Message-ID: <20000906161919.N17616@lucifer.bart.nl> References: <4.3.2.7.2.20000906145953.00d07900@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <4.3.2.7.2.20000906145953.00d07900@mail.Go2France.com>; from lconrad@Go2France.com on Wed, Sep 06, 2000 at 03:02:05PM +0200 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000906 15:05], Len Conrad (lconrad@Go2France.com) wrote: >We deal lot with AS/400 customers with TRN systems. I see 4.1 release >still doesn't have a TRN card supported. > >Anybody got any ideas how to support TRN in FreeBSD? If I am not mistaking Token Ring _is_ supported in FreeBSD. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl There can be no justice so long as laws are absolute... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 7:46:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 9A5BA37B423 for ; Wed, 6 Sep 2000 07:46:26 -0700 (PDT) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 12CD04C; Wed, 6 Sep 2000 10:46:25 -0400 (AST) Message-ID: <39B658C0.CD9A2E37@vangelderen.org> Date: Wed, 06 Sep 2000 10:46:24 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: FYI: RSA Donated to the public domain References: <200009061312.HAA68224@harmony.village.org> <200009061317.HAA68280@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 <200009061312.HAA68224@harmony.village.org> Warner Losh writes: > : RSA Security Releases RSA Encryption Algorithm into Public Domain > > Note that other information at the site says that RSAREF isn't > released into the public domain. Its use is still governed by > copyright law, so we'll have to use the international version of > RSAREF if we want to get RSA into -current. RSAREF was only neccessary whilst the patent was enforced. Now that RSA is released[1] we can use the OpenSSL RSA implementation which is better. [1] The press release talk about RSADSI "waiving its rights to enforce the RSA patent for any development activities" This is very cunning as the patent never actually covered development. Instead it covers usage and sales of products incorporating RSA, both of which are not explicitly allowed for in the press release. Better be careful, better get written approval! Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 8: 2:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw1.MEIway.com (mgw1.meiway.com [212.73.210.75]) by hub.freebsd.org (Postfix) with ESMTP id 84FF537B422 for ; Wed, 6 Sep 2000 08:02:34 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 607D46A903 for ; Wed, 6 Sep 2000 17:02:33 +0200 (CEST) Received: from sv.Go2France.com [212.73.210.79] by mail.Go2France.com with ESMTP (SMTPD32-6.04) id AD5BDAE50088; Wed, 06 Sep 2000 17:06:03 +0200 Message-Id: <4.3.2.7.2.20000906170138.02870f00@mail.Go2France.com> X-Sender: lconrad%Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 06 Sep 2000 17:02:38 +0200 To: freebsd-hackers@FreeBSD.ORG From: Len Conrad Subject: Re: Token Ring ?? In-Reply-To: <20000906161919.N17616@lucifer.bart.nl> References: <4.3.2.7.2.20000906145953.00d07900@mail.Go2France.com> <4.3.2.7.2.20000906145953.00d07900@mail.Go2France.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 >If I am not mistaking Token Ring _is_ supported in FreeBSD. Stealthy support it is, then, as I cannot find it here: http://www.freebsd.org/releases/4.1R/notes.html Len http://BIND8NT.MEIway.com: ISC BIND 8.2.2 p5 installable binary for NT4 http://IMGate.MEIway.com: Build free, hi-perf, anti-spam mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 8: 7:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 4474A37B424 for ; Wed, 6 Sep 2000 08:07:34 -0700 (PDT) Received: (qmail 50755 invoked by uid 1000); 6 Sep 2000 15:07:35 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Sep 2000 15:07:35 -0000 Date: Wed, 6 Sep 2000 10:07:35 -0500 (CDT) From: Mike Silbersack To: "Jeroen C. van Gelderen" Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: FYI: RSA Donated to the public domain In-Reply-To: <39B658C0.CD9A2E37@vangelderen.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 Wed, 6 Sep 2000, Jeroen C. van Gelderen wrote: > [1] The press release talk about RSADSI "waiving its > rights to enforce the RSA patent for any development > activities" > > This is very cunning as the patent never actually > covered development. Instead it covers usage and > sales of products incorporating RSA, both of which > are not explicitly allowed for in the press release. > Better be careful, better get written approval! All of the pages they've put up on their website seems to disagree with what you've just said. I think you're confusing use of RSA and use of RSAREF/BSAFE, which they're still maintaining control over (as Warner said.) Somehow I rather doubt they're trying to trick people into using RSA for the next week, and then going on a mass lawsuit spree. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 8:12:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 344D337B422 for ; Wed, 6 Sep 2000 08:12:37 -0700 (PDT) Received: (qmail 50777 invoked by uid 1000); 6 Sep 2000 15:12:39 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Sep 2000 15:12:39 -0000 Date: Wed, 6 Sep 2000 10:12:39 -0500 (CDT) From: Mike Silbersack To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Token Ring ?? In-Reply-To: <4.3.2.7.2.20000906170138.02870f00@mail.Go2France.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Sep 2000, Len Conrad wrote: > >If I am not mistaking Token Ring _is_ supported in FreeBSD. > > Stealthy support it is, then, as I cannot find it here: > > http://www.freebsd.org/releases/4.1R/notes.html > > Len Multiple Token Ring cards are listed in LINT. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 8:14:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 9195137B424 for ; Wed, 6 Sep 2000 08:14:33 -0700 (PDT) Received: (qmail 50785 invoked by uid 1000); 6 Sep 2000 15:14:35 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Sep 2000 15:14:35 -0000 Date: Wed, 6 Sep 2000 10:14:35 -0500 (CDT) From: Mike Silbersack To: "Jeroen C. van Gelderen" Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: FYI: RSA Donated to the public domain In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Sep 2000, Mike Silbersack wrote: > Somehow I rather doubt they're trying to trick people into using RSA for > the next week, and then going on a mass lawsuit spree. Ugh, please forgive my poor English. It's before noon. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 8:20:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id A0DFE37B424 for ; Wed, 6 Sep 2000 08:20:21 -0700 (PDT) Received: (qmail 50819 invoked by uid 1000); 6 Sep 2000 15:20:23 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Sep 2000 15:20:23 -0000 Date: Wed, 6 Sep 2000 10:20:23 -0500 (CDT) From: Mike Silbersack To: Warner Losh Cc: hackers@freebsd.org Subject: Re: FYI: RSA Donated to the public domain In-Reply-To: <200009061312.HAA68224@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 Wed, 6 Sep 2000, Warner Losh wrote: > http://www.rsasecurity.com/news/pr/000906-1.html > > RSA Security Releases RSA Encryption Algorithm into Public Domain Ok, now I have a question. Using STARTTLS with sendmail is obviously OK for us, since sendmail got the export liscense. However, AFAIK, qmail and postfix have obtained no such permission. So, can we put in the STARTTLS patches for those two MTAs into the ports tree? Since the actual encryption duties are handled by OpenSSL in both cases, I suspect it's in the same boat as OpenSSH, US export-wise. However, I've never been clear on what boat OpenSSH is actually in. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 8:29:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id 9752037B43F for ; Wed, 6 Sep 2000 08:29:10 -0700 (PDT) Received: from heathers (heathers [199.89.192.5]) by heathers.stdio.com (8.9.3/8.8.8) with ESMTP id LAA22381; Wed, 6 Sep 2000 11:28:22 -0400 (EDT) (envelope-from lile@stdio.com) Date: Wed, 6 Sep 2000 11:28:22 -0400 (EDT) From: Larry Lile To: Mike Silbersack Cc: Len Conrad , "Barry O'Mahony" , Jeroen Ruigrok van der Werven , freebsd-hackers@FreeBSD.ORG Subject: Re: Token Ring ?? 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 Token-ring is supported in FreeBSD, we are lacking in the fact that we have only one working driver. Olicom PCI token-ring adapters are supported. ISA adapters will be supported, but I have not had time to finish the code. http://www.jurai.net/~winter/tr/tr.html freebsd-tokenring@freebsd.org Feel free to help out :-) -- Larry Lile lile@stdio.com On Wed, 6 Sep 2000, Mike Silbersack wrote: > > On Wed, 6 Sep 2000, Len Conrad wrote: > > > >If I am not mistaking Token Ring _is_ supported in FreeBSD. > > > > Stealthy support it is, then, as I cannot find it here: > > > > http://www.freebsd.org/releases/4.1R/notes.html > > > > Len > > Multiple Token Ring cards are listed in LINT. > > Mike "Silby" Silbersack > > > > 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 Sep 6 8:29:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id AA33C37B443 for ; Wed, 6 Sep 2000 08:29:12 -0700 (PDT) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id 877CE4C; Wed, 6 Sep 2000 11:29:11 -0400 (AST) Message-ID: <39B662C7.80E69F1@vangelderen.org> Date: Wed, 06 Sep 2000 11:29:11 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Silbersack Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: FYI: RSA Donated to the public domain References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Silbersack wrote: > > On Wed, 6 Sep 2000, Jeroen C. van Gelderen wrote: > > > [1] The press release talk about RSADSI "waiving its > > rights to enforce the RSA patent for any development > > activities" > > > > This is very cunning as the patent never actually > > covered development. Instead it covers usage and > > sales of products incorporating RSA, both of which > > are not explicitly allowed for in the press release. > > Better be careful, better get written approval! > > All of the pages they've put up on their website seems to disagree with > what you've just said. I just pointed out that the press release (from which I quoted) doesn't state that use/selling of RSA is allowed now. It seems that the FAQ allows for use and sale. Which document prevails is up in lawyer land... > I think you're confusing use of RSA and use of > RSAREF/BSAFE, Nope, the press release explicitly (see quote above) talks about the patent (which covers the algorithm, not RSAREF) and I was pointing out just that. > which they're still maintaining control over (as Warner > said.) Which is not an issue as we don't need RSAREF, not even an international version of RSAREF :-) > Somehow I rather doubt they're trying to trick people into using RSA for > the next week, and then going on a mass lawsuit spree. You may very well be right but in case you are not, it would be rather nasty if we got harassed, right? RSADSI has not been nice about their IP in the past couple of years and I have no reason to believe they will be now. Cheers, Jeroen -- Jeroen C. van Gelderen o _ _ _ jeroen@vangelderen.org _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_ \_| \ _|/' \/ (_)>(_) (_) (_) (_) (_)' _\o_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 8:58:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from karon.dynas.se (karon.dynas.se [192.71.43.4]) by hub.freebsd.org (Postfix) with SMTP id E049F37B423 for ; Wed, 6 Sep 2000 08:58:16 -0700 (PDT) Received: (qmail 61617 invoked from network); 6 Sep 2000 15:58:15 -0000 Received: from spirit.sto.dynas.se (HELO spirit.dynas.se) (172.16.1.10) by karon.sto.dynas.se with SMTP; 6 Sep 2000 15:58:15 -0000 Received: (qmail 17257 invoked from network); 6 Sep 2000 15:58:18 -0000 Received: from explorer.rsa.com (10.81.217.59) by spirit.dynas.se with SMTP; 6 Sep 2000 15:58:18 -0000 Received: (from mikko@localhost) by explorer.rsa.com (8.9.3/8.9.3) id IAA18365; Wed, 6 Sep 2000 08:58:09 -0700 (PDT) (envelope-from mikko) Date: Wed, 6 Sep 2000 08:58:09 -0700 (PDT) From: Mikko Tyolajarvi Message-Id: <200009061558.IAA18365@explorer.rsa.com> To: freebsd-hackers@freebsd.org Subject: Re: Need quick help. Newsgroups: local.freebsd-hackers References: X-Newsreader: NN version 6.5.6 (NOV) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In local.freebsd-hackers Doug White wrote: >On Tue, 5 Sep 2000, petro wrote: >> I tried to change smth in my interfaces and now receive such message in >> /var/log/messages >> /kernel: arp: IP_number is on rl2 but got reply from MAC_ADDRESS an ed1 >Your networks are broken. It appears the two interfaces are plugged into >the same physical network. These messages can also occur if one of the interfaces is connected to a "hostile network", such as via a cable-tv modem. How hostile depends on the relative cluelessness of the cable-tv operator/ISP (this particular one [Chello in Stockholm] can be considered "pretty damn clueless"). $.02, /Mikko -- Mikko Työläjärvi_______________________________________mikko@rsasecurity.com RSA Security To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 9: 0: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from outpost.hstn.tensor.pgs.com (outpost.hstn.tensor.pgs.com [157.147.25.67]) by hub.freebsd.org (Postfix) with ESMTP id 25AA037B42C for ; Wed, 6 Sep 2000 09:00:06 -0700 (PDT) Received: from hap.hstn.tensor.pgs.com (hap.hstn.tensor.pgs.com [157.147.136.13]) by outpost.hstn.tensor.pgs.com (8.9.3/8.9.3) with ESMTP id KAA29725 for ; Wed, 6 Sep 2000 10:59:56 -0500 (CDT) Received: from penguin.hstn.tensor.pgs.com (penguin.hstn.tensor.pgs.com [157.147.132.155]) by hap.hstn.tensor.pgs.com (8.9.3/8.9.3) with ESMTP id KAA02526 for ; Wed, 6 Sep 2000 10:59:55 -0500 (CDT) Received: from hstn.tensor.pgs.com (localhost [127.0.0.1]) by penguin.hstn.tensor.pgs.com (8.8.8+Sun/8.8.8) with ESMTP id KAA13334 for ; Wed, 6 Sep 2000 10:59:54 -0500 (CDT) Message-Id: <200009061559.KAA13334@penguin.hstn.tensor.pgs.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Subject: DHCP clients moving between NIS domains Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Sep 2000 10:59:54 -0500 From: Steve Hocking Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone hacked the dhclient-script to fire up YP appropriately after determining what NIS domain the machine (my trusty laptop) has ended ujp in this time? I know that the Linux client can do it. 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 Wed Sep 6 11:19:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from federation.addy.com (federation.addy.com [208.11.142.20]) by hub.freebsd.org (Postfix) with ESMTP id 0B87D37B424 for ; Wed, 6 Sep 2000 11:19:22 -0700 (PDT) Received: from localhost (jim@localhost) by federation.addy.com (8.9.3/8.9.3) with ESMTP id OAA51894 for ; Wed, 6 Sep 2000 14:19:16 -0400 (EDT) (envelope-from jim@federation.addy.com) Date: Wed, 6 Sep 2000 14:19:16 -0400 (EDT) From: Jim Sander Cc: hackers@FreeBSD.ORG Subject: Re: FYI: RSA Donated to the public domain In-Reply-To: <39B662C7.80E69F1@vangelderen.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 From the rsa website (the quiz, hey- who can resist a free T-Shirt) there is the following tidbit... > With the patent expiration, software developers are now free to develop > their own implementation of the RSA algorithm from scratch. However, > RSA BSAFE and RSAREF code is still proprietary and subject to licensing. But since there are already other (better?) coded implementations of RSA's algorithms, if those are used we all should be golden. Correct? -=Jim=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 11:21:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 7B59737B422 for ; Wed, 6 Sep 2000 11:21:25 -0700 (PDT) Received: from office (p3E9D16BF.dip.t-dialin.net [62.157.22.191]) by post.webmailer.de (8.9.3/8.8.7) with SMTP id UAA28937; Wed, 6 Sep 2000 20:21:05 +0200 (MET DST) Message-ID: <000201c0182e$b9cc7380$1401a8c0@wes.mee.com> From: "Frederik Meerwaldt" To: "Hao Zhang" Cc: References: Subject: Re: Duplicating packets Date: Wed, 6 Sep 2000 20:16:15 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! > I am doing some testing on FreeBSD 3.3 platform by sending some UDP packets > thru FreeBSD routers. It's found that FreeBSD duplicates some packet. > That results in that the received packet are more than sent ones. How > can I disable the duplication in FreeBSD config. Or did I do some wrong > in the FreeBSD config. The FreeBSD 3.3 is running on Pentium III, and NIC is > 3C905B-Tx. Could you please inform us about details regarding this problem? Which routing software are you using? natd? routed? Interface Characteristics (output of ifconfig of the interfaces)? netstat -r Best Regards, Freddy -- www.freddym.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 12:11:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 472EB37B424 for ; Wed, 6 Sep 2000 12:11:08 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13Wkb6-0000Ug-01; Wed, 06 Sep 2000 19:11:01 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e86Ib2v01036; Wed, 6 Sep 2000 20:37:02 +0200 (CEST) (envelope-from wkb) Date: Wed, 6 Sep 2000 20:37:02 +0200 From: Wilko Bulte To: Mikko Tyolajarvi Cc: freebsd-hackers@freebsd.org Subject: Re: Need quick help. Message-ID: <20000906203702.A978@freebie.demon.nl> References: <200009061558.IAA18365@explorer.rsa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200009061558.IAA18365@explorer.rsa.com>; from mikko@dynas.se on Wed, Sep 06, 2000 at 08:58:09AM -0700 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 06, 2000 at 08:58:09AM -0700, Mikko Tyolajarvi wrote: > In local.freebsd-hackers Doug White wrote: > > >On Tue, 5 Sep 2000, petro wrote: > > >> I tried to change smth in my interfaces and now receive such message in > >> /var/log/messages > >> /kernel: arp: IP_number is on rl2 but got reply from MAC_ADDRESS an ed1 > > >Your networks are broken. It appears the two interfaces are plugged into > >the same physical network. > > These messages can also occur if one of the interfaces is connected to > a "hostile network", such as via a cable-tv modem. How hostile > depends on the relative cluelessness of the cable-tv operator/ISP > (this particular one [Chello in Stockholm] can be considered "pretty > damn clueless"). OK, which makes Chello a truly international clueless company.. Wilko (happy back to using a reliable ISDN link) -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 12:29:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtprch2.nortel.com (smtprch2.nortelnetworks.com [192.135.215.15]) by hub.freebsd.org (Postfix) with ESMTP id C1C6037B422 for ; Wed, 6 Sep 2000 12:29:17 -0700 (PDT) Received: from zrchb213.us.nortel.com (actually zrchb213) by smtprch2.nortel.com; Wed, 6 Sep 2000 14:23:41 -0500 Received: by zrchb213.us.nortel.com with Internet Mail Service (5.5.2652.35) id ; Wed, 6 Sep 2000 14:27:22 -0500 Message-ID: From: "Hao Zhang" To: 'Frederik Meerwaldt' , freebsd-hackers Subject: RE: Duplicating packets Date: Wed, 6 Sep 2000 14:27:14 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.35) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C01838.764BACC0" X-Orig: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C01838.764BACC0 Content-Type: text/plain; charset="iso-8859-1" Since the router we are testing is a standalone box, we are not using any routing protocols. The actual testbed is using Gated. Here is the info from the router. Thanks in advance. # ifconfig -au xl0: flags=8843 mtu 1500 inet 200.1.16.10 netmask 0xfffff000 broadcast 200.1.31.255 ether 00:50:04:0d:bf:46 media: 10baseT/UTP supported media: autoselect 100baseTX 100baseTX 100 baseTX 10baseT/UTP 10baseT/UTP 10baseT/UTP xl1: flags=8843 mtu 1500 inet 200.2.16.10 netmask 0xfffff000 broadcast 200.2.31.255 ether 00:50:04:0d:bc:82 media: 10baseT/UTP supported media: autoselect 100baseTX 100baseTX 100 baseTX 10baseT/UTP 10baseT/UTP 10baseT/UTP xl2: flags=8843 mtu 1500 inet 200.3.16.10 netmask 0xfffff000 broadcast 200.3.31.255 ether 00:b0:d0:2a:79:b2 media: 10baseT/UTP supported media: autoselect 100baseTX 100baseTX 100 baseTX 10baseT/UTP 10baseT/UTP 10baseT/UTP xl3: flags=8843 mtu 1500 inet 200.4.16.10 netmask 0xfffff000 broadcast 200.4.31.255 ether 00:50:04:71:5a:76 media: 10baseT/UTP supported media: autoselect 100baseTX 100baseTX 100 baseTX 10baseT/UTP 10baseT/UTP 10baseT/UTP rl0: flags=8843 mtu 1500 inet 200.5.16.10 netmask 0xfffff000 broadcast 200.5.31.255 ether 00:48:54:87:9f:de media: autoselect supported media: autoselect 100baseTX 100baseTX 100 baseTX 10baseT/UTP 10baseT/UTP 10baseT/UTP rl1: flags=8843 mtu 1500 inet 200.6.16.10 netmask 0xfffff000 broadcast 200.6.31.255 ether 00:48:54:87:e0:3f media: autoselect supported media: autoselect 100baseTX 100baseTX 100 baseTX 10baseT/UTP 10baseT/UTP 10baseT/UTP # # netstat -r Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire 200.1.16/20 link#1 UC 0 0 xl0 200.1.16.10 0:50:4:d:bf:46 UHLW 0 432 lo0 200.1.16.100 0:de:bb:1:0:0 UHLW 0 0 xl0 1167 200.2.16/20 link#2 UC 0 0 xl1 200.2.16.100 0:de:bb:1:1:0 UHLW 0 142164 xl1 1167 200.3.16/20 link#3 UC 0 0 xl2 200.3.16.100 0:de:bb:1:2:0 UHLW 0 0 xl2 1167 200.4.16/20 link#4 UC 0 0 xl3 200.4.16.100 0:de:bb:1:3:0 UHLW 0 0 xl3 1167 200.5.16/20 link#5 UC 0 0 rl0 200.5.16.100 0:de:bb:1:10:0 UHLW 0 142243 rl0 1167 200.6.16/20 link#6 UC 0 0 rl1 200.6.16.100 0:de:bb:1:11:0 UHLW 1 9048110 rl1 1167 # --Hao -----Original Message----- From: Frederik Meerwaldt [mailto:frederik@freddym.org] Sent: Wednesday, September 06, 2000 2:16 PM To: Zhang, Hao [WDLN2:AN22:EXCH] Cc: freebsd-hackers Subject: Re: Duplicating packets Hi! > I am doing some testing on FreeBSD 3.3 platform by sending some UDP packets > thru FreeBSD routers. It's found that FreeBSD duplicates some packet. > That results in that the received packet are more than sent ones. How > can I disable the duplication in FreeBSD config. Or did I do some wrong > in the FreeBSD config. The FreeBSD 3.3 is running on Pentium III, and NIC is > 3C905B-Tx. Could you please inform us about details regarding this problem? Which routing software are you using? natd? routed? Interface Characteristics (output of ifconfig of the interfaces)? netstat -r Best Regards, Freddy -- www.freddym.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message ------_=_NextPart_001_01C01838.764BACC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Duplicating packets

Since the router we are testing is a standalone box, = we are not using any routing protocols. 
The actual testbed is using Gated. Here is the info = from the router. Thanks in advance.

# ifconfig -au
xl0: = flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu = 1500
        inet = 200.1.16.10 netmask 0xfffff000 broadcast 200.1.31.255
        ether = 00:50:04:0d:bf:46
        media: = 10baseT/UTP <half-duplex>
        supported = media: autoselect 100baseTX <full-duplex> 100baseTX = <half-duplex> 100
baseTX 10baseT/UTP <full-duplex> 10baseT/UTP = <half-duplex> 10baseT/UTP
xl1: = flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu = 1500
        inet = 200.2.16.10 netmask 0xfffff000 broadcast 200.2.31.255
        ether = 00:50:04:0d:bc:82
        media: = 10baseT/UTP <half-duplex>
        supported = media: autoselect 100baseTX <full-duplex> 100baseTX = <half-duplex> 100
baseTX 10baseT/UTP <full-duplex> 10baseT/UTP = <half-duplex> 10baseT/UTP
xl2: = flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu = 1500
        inet = 200.3.16.10 netmask 0xfffff000 broadcast 200.3.31.255
        ether = 00:b0:d0:2a:79:b2
        media: = 10baseT/UTP <half-duplex>
        supported = media: autoselect 100baseTX <full-duplex> 100baseTX = <half-duplex> 100
baseTX 10baseT/UTP <full-duplex> 10baseT/UTP = <half-duplex> 10baseT/UTP
xl3: = flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu = 1500
        inet = 200.4.16.10 netmask 0xfffff000 broadcast 200.4.31.255
        ether = 00:50:04:71:5a:76
        media: = 10baseT/UTP <half-duplex>
        supported = media: autoselect 100baseTX <full-duplex> 100baseTX = <half-duplex> 100
baseTX 10baseT/UTP <full-duplex> 10baseT/UTP = <half-duplex> 10baseT/UTP
rl0: = flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu = 1500
        inet = 200.5.16.10 netmask 0xfffff000 broadcast 200.5.31.255
        ether = 00:48:54:87:9f:de
        media: = autoselect
        supported = media: autoselect 100baseTX <full-duplex> 100baseTX = <half-duplex> 100
baseTX 10baseT/UTP <full-duplex> 10baseT/UTP = 10baseT/UTP <half-duplex>
rl1: = flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu = 1500
        inet = 200.6.16.10 netmask 0xfffff000 broadcast 200.6.31.255
        ether = 00:48:54:87:e0:3f
        media: = autoselect
        supported = media: autoselect 100baseTX <full-duplex> 100baseTX = <half-duplex> 100
baseTX 10baseT/UTP <full-duplex> 10baseT/UTP = 10baseT/UTP <half-duplex>
#

# netstat -r
Routing tables

Internet:
Destination        = Gateway           = ; Flags     Refs     = Use     Netif Expire
200.1.16/20        = link#1           =   UC          = 0        = 0      xl0
200.1.16.10        = 0:50:4:d:bf:46     = UHLW        = 0      432      = lo0
200.1.16.100       = 0:de:bb:1:0:0      = UHLW        = 0        = 0      xl0   1167
200.2.16/20        = link#2           =   UC          = 0        = 0      xl1
200.2.16.100       = 0:de:bb:1:1:0      = UHLW        0   = 142164      xl1   1167
200.3.16/20        = link#3           =   UC          = 0        = 0      xl2
200.3.16.100       = 0:de:bb:1:2:0      = UHLW        = 0        = 0      xl2   1167
200.4.16/20        = link#4           =   UC          = 0        = 0      xl3
200.4.16.100       = 0:de:bb:1:3:0      = UHLW        = 0        = 0      xl3   1167
200.5.16/20        = link#5           =   UC          = 0        = 0      rl0
200.5.16.100       = 0:de:bb:1:10:0     UHLW     = ;   0   142243      = rl0   1167
200.6.16/20        = link#6           =   UC          = 0        = 0      rl1
200.6.16.100       = 0:de:bb:1:11:0     = UHLW        1  = 9048110      rl1   1167
#

--Hao

-----Original Message-----
From: Frederik Meerwaldt [mailto:frederik@freddym.org]
Sent: Wednesday, September 06, 2000 2:16 PM
To: Zhang, Hao [WDLN2:AN22:EXCH]
Cc: freebsd-hackers
Subject: Re: Duplicating packets


Hi!

> I am doing some testing on FreeBSD 3.3 platform = by sending some UDP
packets
> thru FreeBSD routers. It's found that FreeBSD = duplicates some packet.
> That results in that the received packet are = more than sent ones. How
> can I disable the duplication in FreeBSD = config. Or did I do some wrong
> in the FreeBSD config. The FreeBSD 3.3 is = running on Pentium III, and NIC
is
> 3C905B-Tx.

Could you please inform us about details regarding = this problem?
Which routing software are you using? natd? routed? = Interface
Characteristics (output of ifconfig of the = interfaces)?
netstat -r

Best Regards,
    Freddy
--
www.freddym.org







To Unsubscribe: send mail to = majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the = body of the message

------_=_NextPart_001_01C01838.764BACC0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 13:46:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4401E37B424; Wed, 6 Sep 2000 13:46:14 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA59534; Wed, 6 Sep 2000 13:46:14 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 6 Sep 2000 13:46:14 -0700 (PDT) From: Kris Kennaway To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: FYI: RSA Donated to the public domain In-Reply-To: <200009061317.HAA68280@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 Wed, 6 Sep 2000, Warner Losh wrote: > In message <200009061312.HAA68224@harmony.village.org> Warner Losh writes: > : RSA Security Releases RSA Encryption Algorithm into Public Domain > > Note that other information at the site says that RSAREF isn't > released into the public domain. Its use is still governed by > copyright law, so we'll have to use the international version of > RSAREF if we want to get RSA into -current. There's no reason why we would want to continue to use RSAREF, except perhaps for source code compatability with something that was written to link against it. The OpenSSL implementation is much better, and basically we just have to build it by default now. I'm not sure whether it's okay to build a shim for OpenSSL which translates the RSAREF API into the native one (the reverse of the OpenSSL -> RSAREF code which currently exists), but it would be mildly useful for those legacy apps. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 14:19:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.wertep.com (relay2.wertep.com [194.44.90.130]) by hub.freebsd.org (Postfix) with ESMTP id 3A16E37B422; Wed, 6 Sep 2000 14:19:16 -0700 (PDT) Received: from She.wertep.com (she-tun-proxy [192.168.252.2]) by relay2.wertep.com (8.9.3/8.9.3) with ESMTP id AAA97554; Thu, 7 Sep 2000 00:19:05 +0300 (EEST) (envelope-from petro@She.wertep.com) Received: from localhost (petro@localhost) by She.wertep.com (8.9.3/8.9.3) with ESMTP id AAA00528; Thu, 7 Sep 2000 00:19:04 +0300 (EEST) (envelope-from petro@She.wertep.com) Date: Thu, 7 Sep 2000 00:19:00 +0300 (EEST) From: petro To: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Problem!! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I have the following problem my local network (192.168.x.x) is connected to server, and use squid on the next server to run Explorer, Nescape. I can run Inetner Explorer and Netscape but when I try to run ping any.hos I receive only it's number arequested timed out . My ipfw is working good, also named works good(I receive IP address of machines) but I can't understand where is problem Thank you very much To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 14:33:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.wertep.com (relay2.wertep.com [194.44.90.130]) by hub.freebsd.org (Postfix) with ESMTP id 97A3B37B423 for ; Wed, 6 Sep 2000 14:33:29 -0700 (PDT) Received: from She.wertep.com (she-tun-proxy [192.168.252.2]) by relay2.wertep.com (8.9.3/8.9.3) with ESMTP id AAA98211 for ; Thu, 7 Sep 2000 00:33:23 +0300 (EEST) (envelope-from petro@She.wertep.com) Received: from localhost (petro@localhost) by She.wertep.com (8.9.3/8.9.3) with ESMTP id AAA00607 for ; Thu, 7 Sep 2000 00:33:20 +0300 (EEST) (envelope-from petro@She.wertep.com) Date: Thu, 7 Sep 2000 00:33:20 +0300 (EEST) From: petro To: freebsd-hackers@FreeBSD.ORG Subject: Promiscuous mode 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 rl0: promiscuous mode enabled rl0: promiscuous mode disabled What does it mean and how I can set this ???? Thank you very much. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 14:37: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.accessus.net (postal.accessus.net [209.145.150.75]) by hub.freebsd.org (Postfix) with ESMTP id 66D6B37B423 for ; Wed, 6 Sep 2000 14:36:58 -0700 (PDT) Received: from exchange.accessus.net (exchange.accessus.net [207.206.171.65]) by mail1.accessus.net (Postfix) with ESMTP id C2CF972685; Wed, 6 Sep 2000 16:36:52 -0500 (CDT) Received: by exchange.accessus.net with Internet Mail Service (5.5.2650.21) id ; Wed, 6 Sep 2000 16:30:09 -0500 Message-ID: From: Jason Young To: 'petro' , freebsd-hackers@FreeBSD.ORG Subject: RE: Promiscuous mode Date: Wed, 6 Sep 2000 16:30:08 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It means something set your Ethernet interface "rl0" to promiscuous mode, which allows it to receive all Ethernet frames on the wire it's attached to instead of just its own. Common applications that do this are tcpdump, trafshow and ntop. If you've used one of these they will by default try and analyze -all- traffic they can get hold of, instead of just that destined for one of your machines. It is logged because it is a potential security issue. If you have not used any tools like the above, you could have a password sniffer or something like that installed without your knowledge. Jason Young Access US(tm) Chief Network Engineer > -----Original Message----- > From: petro [mailto:petro@She.wertep.com] > Sent: Wednesday, September 06, 2000 4:33 PM > To: freebsd-hackers@FreeBSD.ORG > Subject: Promiscuous mode > > > rl0: promiscuous mode enabled > rl0: promiscuous mode disabled > What does it mean and how I can set this ???? > Thank you very much. > > > > 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 Sep 6 14:37:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 53E6237B423; Wed, 6 Sep 2000 14:37:14 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e86Lafu23535; Wed, 6 Sep 2000 14:36:41 -0700 (PDT) Date: Wed, 6 Sep 2000 14:36:41 -0700 From: Alfred Perlstein To: petro Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Problem!! Message-ID: <20000906143641.P18862@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from petro@She.wertep.com on Thu, Sep 07, 2000 at 12:19:00AM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * petro [000906 14:19] wrote: > Hi! > I have the following problem my local network (192.168.x.x) is connected > to server, and use squid on the next server to run Explorer, Nescape. I > can run Inetner Explorer and Netscape but when I try to run ping > any.hos I receive only it's number arequested timed out . My ipfw is > working good, also named works good(I receive IP address of machines) but > I can't understand where is problem > Thank you very much Unless you're using NAT then your packets are going out onto the internet as 192.168.x.x and the internet has no clue how to get these packets back to you. Solution, install NATd. -- -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 Sep 6 14:39:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id 1688937B422 for ; Wed, 6 Sep 2000 14:39:16 -0700 (PDT) Received: (qmail 5810 invoked from network); 6 Sep 2000 21:48:14 -0000 Received: from jhs.muc.de (HELO park.jhs.private) (193.149.49.84) by slarti.muc.de with SMTP; 6 Sep 2000 21:48:14 -0000 Received: from park.jhs.private (localhost [127.0.0.1]) by park.jhs.private (8.9.3/8.9.3) with ESMTP id TAA28296; Wed, 6 Sep 2000 19:14:33 GMT (envelope-from jhs@park.jhs.private) Message-Id: <200009061914.TAA28296@park.jhs.private> To: Mike Silbersack Cc: "Jeroen C. van Gelderen" , Warner Losh , hackers@FreeBSD.ORG Subject: Re: FYI: RSA Donated to the public domain From: "Julian Stacey" Organization: Vector Systems Ltd - Munich Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ In-reply-to: Your message of "Wed, 06 Sep 2000 10:07:35 CDT." Date: Wed, 06 Sep 2000 21:14:33 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Somehow I rather doubt they're trying to trick people into using RSA for > the next week, and then going on a mass lawsuit spree. No idea about RSA motives, but "Submarice patents" are a well known strategem. AFAIR owners of compress.c registered it, then published it, & only years later tried to extract money for it (& Jean Luc Gailly wrote the more efficient gzip, under GPL, & we all abandoned compress :-) Julian - Julian Stacey http://bim.bsn.com/~jhs/ Munich Unix Consultant. Free BSD Unix with 3600 packages & sources. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 17:38: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id CBDD437B422 for ; Wed, 6 Sep 2000 17:38:01 -0700 (PDT) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id UAA28088 for ; Wed, 6 Sep 2000 20:38:39 -0400 (EDT) Message-Id: <200009070038.UAA28088@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 06 Sep 2000 20:38:08 -0400 To: hackers@freebsd.org From: Dennis Subject: dc driver issues Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With freebsd 4.1, I have 2 "problems" with the dc driver. Im using a 4 port DLINK card in this test: 1) It always give me a "device timeout" on first startup. It seems to work ok though. The de driver (oppositely) gives me an "enabled" on the connected ports on startup. 2). It numbers the ports in the opposite order expected. Bottom to top. Is there a simple patch to correct this...or is this a system or MB issue? the MB is an Intel ATX, pretty standard stuff. any ideas? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Sep 6 22: 0:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.houston.rr.com (sm1.texas.rr.com [24.93.35.54]) by hub.freebsd.org (Postfix) with ESMTP id 6C5BC37B43F for ; Wed, 6 Sep 2000 22:00:11 -0700 (PDT) Received: from bleep.craftncomp.com ([24.27.77.164]) by mail.houston.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Thu, 7 Sep 2000 00:01:56 -0500 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 e87507V09997 for ; Thu, 7 Sep 2000 00:00:08 -0500 (CDT) (envelope-from shocking@houston.rr.com) Received: from bloop.craftncomp.com (localhost [127.0.0.1]) by bloop.craftncomp.com (8.11.0/8.9.3) with ESMTP id e87506G44740 for ; Thu, 7 Sep 2000 00:00:07 -0500 (CDT) (envelope-from shocking@bloop.craftncomp.com) Message-Id: <200009070500.e87506G44740@bloop.craftncomp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Subject: What's the best PCMCIA Ethernet card? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Sep 2000 00:00:06 -0500 From: Stephen Hocking Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Preferably 10/100. This old Megahertz CC10BT doesn't seem to be terribly quick. 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 Wed Sep 6 23:22:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 1967737B423 for ; Wed, 6 Sep 2000 23:22:51 -0700 (PDT) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13Wv5G-000G7O-00; Thu, 07 Sep 2000 06:22:50 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.0/8.11.0) id e8762ii08742; Thu, 7 Sep 2000 08:02:44 +0200 (CEST) (envelope-from wkb) Date: Thu, 7 Sep 2000 08:02:44 +0200 From: Wilko Bulte To: petro Cc: freebsd-hackers@freebsd.org Subject: Re: Promiscuous mode Message-ID: <20000907080244.C8695@freebie.demon.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from petro@She.wertep.com on Thu, Sep 07, 2000 at 12:33:20AM +0300 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 07, 2000 at 12:33:20AM +0300, petro wrote: > rl0: promiscuous mode enabled > rl0: promiscuous mode disabled > What does it mean and how I can set this ???? This means the interface rl0 now listens to all traffic on the wire. Happens for example when you run dhcpd W/ -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 1:48:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from netplex.com.au (adsl-63-207-30-186.dsl.snfc21.pacbell.net [63.207.30.186]) by hub.freebsd.org (Postfix) with ESMTP id 63DDD37B423 for ; Thu, 7 Sep 2000 01:48:19 -0700 (PDT) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.11.0/8.9.3) with ESMTP id e878m5G55687; Thu, 7 Sep 2000 01:48:05 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200009070848.e878m5G55687@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Silbersack Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: FYI: RSA Donated to the public domain In-Reply-To: Date: Thu, 07 Sep 2000 01:48:05 -0700 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Silbersack wrote: > > On Wed, 6 Sep 2000, Warner Losh wrote: > > > http://www.rsasecurity.com/news/pr/000906-1.html > > > > RSA Security Releases RSA Encryption Algorithm into Public Domain > > Ok, now I have a question. Using STARTTLS with sendmail is obviously OK > for us, since sendmail got the export liscense. However, AFAIK, qmail and > postfix have obtained no such permission. Postfix has done the BXA hoop thing too. It is fully exportable (and reexportable) and has a TLS etc implementation. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 2:11: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.2.7]) by hub.freebsd.org (Postfix) with ESMTP id 1DD9837B423 for ; Thu, 7 Sep 2000 02:10:59 -0700 (PDT) Received: from hermes.tue.nl (hermes.tue.nl [131.155.2.46]) by kweetal.tue.nl (8.11.0/8.11.0) with ESMTP id e879Avu17792 for ; Thu, 7 Sep 2000 11:10:57 +0200 (MDT) Received: from deathstar (n152.dial.tue.nl [131.155.209.151]) by hermes.tue.nl (Postfix) with ESMTP id A2B6E2E802 for ; Thu, 7 Sep 2000 11:10:56 +0200 (CEST) From: "Marco van de Voort" To: freebsd-hackers@freebsd.org Date: Thu, 7 Sep 2000 11:11:34 +0100 Subject: pthread In-reply-to: <20000907080244.C8695@freebie.demon.nl> References: ; from petro@She.wertep.com on Thu, Sep 07, 2000 at 12:33:20AM +0300 X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: <20000907091056.A2B6E2E802@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What does this line (from clone.s linuxpthread port) do? jmp PIC_PLT(HIDENAME(cerror)) Marco van de Voort (MarcoV@Stack.nl or marco@freepascal.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 2:15:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 339DD37B423; Thu, 7 Sep 2000 02:15:48 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id CAA86795; Thu, 7 Sep 2000 02:15:48 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 7 Sep 2000 02:15:47 -0700 (PDT) From: Kris Kennaway To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Token Ring ?? In-Reply-To: <4.3.2.7.2.20000906170138.02870f00@mail.Go2France.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Sep 2000, Len Conrad wrote: > > >If I am not mistaking Token Ring _is_ supported in FreeBSD. > > Stealthy support it is, then, as I cannot find it here: > > http://www.freebsd.org/releases/4.1R/notes.html Unfortunately, the release notes tend to lag behind the actual state of the system, sometimes significantly. This may be improving. As always, the code is the definitive reference :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 6:53: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from doorman.brann.org (remote-brann-gw.nyc.dsl.access.net [166.84.145.254]) by hub.freebsd.org (Postfix) with ESMTP id 1D81837B43E for ; Thu, 7 Sep 2000 06:52:56 -0700 (PDT) Received: from freebie.brann.org (freebie.brann.org [10.0.0.2]) by doorman.brann.org (8.9.3/8.9.3) with ESMTP id JAA69819 for ; Thu, 7 Sep 2000 09:52:55 -0400 (EDT) (envelope-from john@brann.org) Received: (from john@localhost) by freebie.brann.org (8.9.3/8.9.3) id JAA52395 for hackers@freebsd.org; Thu, 7 Sep 2000 09:52:54 -0400 (EDT) (envelope-from john) Date: Thu, 7 Sep 2000 09:52:54 -0400 From: John Brann To: hackers@freebsd.org Subject: [john: tty behaviour] Message-ID: <20000907095254.A52345@freebie.brann.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="sm4nu43k4a2Rpi4c" X-Mailer: Mutt 1.0i Organization: Not while I'm at home X-Operating-System: FreeBSD 4.1-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii I sent this to questions a couple of weeks ago, but didn't receive any helpful replies. Anyone doing this - two machines connected by a null-modem cable with the ability to create a serial terminal session from either side, with suitable juggling of getty processes? John --sm4nu43k4a2Rpi4c Content-Type: message/rfc822 Date: Thu, 10 Aug 2000 17:31:07 -0400 From: John Brann To: questions@freebsd.org Subject: tty behaviour Message-ID: <20000810173107.A16021@freebie.brann.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: Not while I'm at home X-Operating-System: FreeBSD 4.1-STABLE Hi, I have two FreeBSD boxes, one runs headless and uses a serial console. This serial console is provided by the second machine, via a null-modem cable: +------------+ +------------+ | machine 1 | | machine 2 | | 3.5-STABLE | | 4.1-STABLE | | HEADLESS | Null-modem cable | | | port sio0 |=======================| port sio1 | +------------+ +------------+ The serial console works perfectly. I can use cu / tip on machine 2 to watch boot messages and log in (I have configured /etc/ttys to provide a getty on /dev/ttyd0 on machine 1). I would like to be able to do the reverse - log in to machine 1 through a network connection, and use it to control machine 2. My steps to accomplish this were: on Machine 1: change /etc/ttys to remove the getty on /dev/ttyd0 kill -HUP 1 on Machine 2: change /etc/ttys to run a getty on /dev/ttyd1 kill -HUP 1 on Machine 1: cu -l cuaa0 Doesn't work. 'cu' tells me I am connected, but no login prompt appears. No characters I type are echoed. I then removed the getty on machine 2 and tried some simpler experiments: Machine 1 Machine 2 cu -l cuaa0 cu -l cuaa1 type characters echoed characters echoed type So the cable is OK. The connection _can_ work. Machine 1 Machine 2 cat < /dev/ttyd0 cu -l cuaa1 lines echoed type then Enter key So the line-discipline is different, but there is no problem using the ttyd0 device on machine1. Machine 1 Machine 2 cu -l cuaa0 cat < /dev/ttyd1 type (no echo on terminal) NO ECHO This does not work. It appears that the tty device on machine 2 is my problem. Any ideas how I can make it work? There are no permissions problems, the devices on both machines have been re-built (so they are not stale device files). Please reply directly (and thank you if you've read this far!) since I'm not on the questions list. John -- Unreal City, Under the brown fog of a winter dawn, finger john@doorman.brann.org for pgp public key --sm4nu43k4a2Rpi4c-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 7:54:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 590BA37B422 for ; Thu, 7 Sep 2000 07:54:32 -0700 (PDT) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id KAA29557 for ; Thu, 7 Sep 2000 10:55:19 -0400 (EDT) Message-Id: <200009071455.KAA29557@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 07 Sep 2000 10:54:37 -0400 To: hackers@FreeBSD.ORG From: Dennis Subject: dc driver issues Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With freebsd 4.1, I have 2 "problems" with the dc driver. Im using a 4 port DLINK card in this test: 1) It always give me a "device timeout" on first startup. It seems to work ok though. The de driver (oppositely) gives me an "enabled" on the connected ports on startup. 2). It numbers the ports in the opposite order expected. Bottom to top. Is there a simple patch to correct this...or is this a system or MB issue? the MB is an Intel ATX, pretty standard stuff. any ideas? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 11:22:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from thelma.NVidia.COM (nvgate.nvidia.com [140.174.105.2]) by hub.freebsd.org (Postfix) with ESMTP id 69BBA37B422; Thu, 7 Sep 2000 11:22:27 -0700 (PDT) Received: from exchange.nvidia.com (exchange [172.16.30.109]) by thelma.NVidia.COM (8.8.8+Sun/8.8.8) with ESMTP id LAA27770; Thu, 7 Sep 2000 11:22:00 -0700 (PDT) Received: by exchange.nvidia.com with Internet Mail Service (5.5.2650.21) id ; Thu, 7 Sep 2000 11:22:00 -0700 Message-ID: <3B87FDB45291D311B89C009027D3B5F8019A5818@nvtom.nvidia.com> From: Nick Triantos To: "'Jeroen Ruigrok van der Werven'" Cc: "'freebsd-hackers@freebsd.org'" , Doug Rabson , Dennis Wong Subject: RE: FW: GeForce 6600 driver Date: Thu, 7 Sep 2000 11:21:59 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We'll be happy to work with people to get our code up and running, but it's important to note that our drivers do not use DRI, we use our own direct rendering mechanism. There are exactly 3 source files which need to be ported from linux to freebsd, then after that, it should be fairly simple to get all of our drivers running on FreeBSD. Again, we do intend to do this, we've just been swamped and haven't yet had bandwidth to do this work. Regards, -Nick > -----Original Message----- > From: Jeroen Ruigrok van der Werven [mailto:jruigrok@via-net-works.nl] > Sent: Wednesday, September 06, 2000 7:18 AM > To: Dennis Wong; Nick Triantos > Cc: 'freebsd-hackers@freebsd.org'; Doug Rabson > Subject: Re: FW: GeForce 6600 driver > > > Hi Dennis, Nick, et al. > > -On [20000906 03:30], Dennis Wong (DWong@nvidia.com) wrote: > > > >> -----Original Message----- > >> From: Nick Triantos > >> Sent: Tuesday, September 05, 2000 6:20 PM > >> To: Dennis Wong > >> Subject: RE: GeForce 6600 driver > >> > >> Hi Dennis, > >> > >> Actually, we haven't done it yet. However, all of our major Linux > >> dependencies should be in the 3 source files which ship as > part of our > >> kernel module's tarball. If those files were ported to > BSD, in theory > >> everything else "should" work, though I'm sure we'd need a > bit of testing > >> before that became fully true. > >> > >> We do plan to start on a FreeBSD port soon, we just > haven't had time yet. > >> However, if there's someone interested in trying to help > do this port, > >> we'd be happy to talk to them. They can email me at > nick@nvidia.com. > > Doug Rabson is the person responsible for the agp miniport driver > currently in FreeBSD and I believe he is also a programmer working on > the Direct Rendering Infrastructure over at Sourceforge. > > > Basically what should require work is probably the detection of your > [Nvidia] cards and its subsequent support in DRI. I might be > a bit off > here, but I am sure one of my more knowledgable committers or > fellow BSD > users will correct me if wrong. > > >> BTW, we did also speak with the FreeBSD guys at > linuxworld, I think we > >> have a possible way we could check our code into the > FreeBSD tree, which > >> would be great once we do get it working well. > > There's the opportunity of one or more of your people to become a > FreeBSD committer, or you can proxy through a committer, such as Mike > Smith is doing for Adaptec's DPT driver. > > >> Feel free to post this, btw. I also really like BSD. > > Nice to see some BSD interest from the major companies aside from all > the Linux hype. =) > You cannot believe how happy I am to read things like this. > > Kind regards, > > -- > Jeroen Ruigrok van der Werven Network- and > systemadministrator > VIA Net.Works The Netherlands > BSD: Technical excellence at its best http://www.via-net-works.nl > Lead us not into temptation, but deliver us from evil... > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 11:33:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from box23.westin33.flyingcroc.net (box23.westin33.flyingcroc.net [207.246.151.23]) by hub.freebsd.org (Postfix) with ESMTP id 3A97937B423 for ; Thu, 7 Sep 2000 11:33:54 -0700 (PDT) Received: from flyingcroc.net (localhost [127.0.0.1]) by box23.westin33.flyingcroc.net (8.9.3/8.9.3) with ESMTP id LAA35076 for ; Thu, 7 Sep 2000 11:33:19 -0700 (PDT) (envelope-from jkraft@flyingcroc.net) Message-ID: <39B7DF6E.3E39A863@flyingcroc.net> Date: Thu, 07 Sep 2000 11:33:19 -0700 From: Jason Kraft X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.1-RC3 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: BIOS statistics Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way to gather BIOS statistics within FreeBSD? I would like to monitor internal CPU temperature, and fan speeds. When I go into the BIOS menu, I can see these statistics, but don't really do any good since most of these gauge values rise after the machine has been on for long periods of time. Thanks, Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 11:37:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 01B8E37B422 for ; Thu, 7 Sep 2000 11:37:14 -0700 (PDT) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id NAA18041; Thu, 7 Sep 2000 13:37:12 -0500 (CDT) (envelope-from dan) Date: Thu, 7 Sep 2000 13:37:12 -0500 From: Dan Nelson To: Jason Kraft Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: BIOS statistics Message-ID: <20000907133712.A17987@dan.emsphone.com> References: <39B7DF6E.3E39A863@flyingcroc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.3.8i In-Reply-To: <39B7DF6E.3E39A863@flyingcroc.net>; from "Jason Kraft" on Thu Sep 7 11:33:19 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Sep 07), Jason Kraft said: > Is there any way to gather BIOS statistics within FreeBSD? I would like > to monitor internal CPU temperature, and fan speeds. When I go into > the BIOS menu, I can see these statistics, but don't really do any good > since most of these gauge values rise after the machine has been on for > long periods of time. ports/sysutils/healthd should do the trick. -- 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 Thu Sep 7 11:38:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 2A72137B422 for ; Thu, 7 Sep 2000 11:38:27 -0700 (PDT) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 15C279B05; Thu, 7 Sep 2000 14:38:26 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 0B2F4BA03; Thu, 7 Sep 2000 14:38:26 -0400 (EDT) Date: Thu, 7 Sep 2000 14:38:26 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Jason Kraft Cc: freebsd-hackers@freebsd.org Subject: Re: BIOS statistics In-Reply-To: <39B7DF6E.3E39A863@flyingcroc.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 Thu, 7 Sep 2000, Jason Kraft wrote: > Is there any way to gather BIOS statistics within FreeBSD? I would like > to monitor internal CPU temperature, and fan speeds. When I go into > the BIOS menu, I can see these statistics, but don't really do any good > since most of these gauge values rise after the machine has been on for > long periods of time. > lmmon, wmlmmon, consolehm, wmhm, healthd (in ports/sysutils) ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 11:52: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (Postfix) with ESMTP id 70BC537B50B for ; Thu, 7 Sep 2000 11:51:57 -0700 (PDT) Received: from vpop.net ([209.102.16.48]) by boromir.vpop.net (8.9.3/8.9.3) with ESMTP id LAA51861; Thu, 7 Sep 2000 11:51:55 -0700 (PDT) (envelope-from mreimer@vpop.net) Message-ID: <39B7E3D1.2DB30D69@vpop.net> Date: Thu, 07 Sep 2000 11:52:01 -0700 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Cc: Nick Triantos Subject: Re: FW: GeForce 6600 driver References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sign me up as a tester, when the time comes! (I have a TNT2 Ultra 32M.) Matt Nick Triantos wrote: > > We'll be happy to work with people to get our code up and running, but it's > important to note that our drivers do not use DRI, we use our own direct > rendering mechanism. There are exactly 3 source files which need to be > ported from linux to freebsd, then after that, it should be fairly simple to > get all of our drivers running on FreeBSD. Again, we do intend to do this, > we've just been swamped and haven't yet had bandwidth to do this work. > > Regards, > -Nick > > > -----Original Message----- > > From: Jeroen Ruigrok van der Werven [mailto:jruigrok@via-net-works.nl] > > Sent: Wednesday, September 06, 2000 7:18 AM > > To: Dennis Wong; Nick Triantos > > Cc: 'freebsd-hackers@freebsd.org'; Doug Rabson > > Subject: Re: FW: GeForce 6600 driver > > > > > > Hi Dennis, Nick, et al. > > > > -On [20000906 03:30], Dennis Wong (DWong@nvidia.com) wrote: > > > > > >> -----Original Message----- > > >> From: Nick Triantos > > >> Sent: Tuesday, September 05, 2000 6:20 PM > > >> To: Dennis Wong > > >> Subject: RE: GeForce 6600 driver > > >> > > >> Hi Dennis, > > >> > > >> Actually, we haven't done it yet. However, all of our major Linux > > >> dependencies should be in the 3 source files which ship as > > part of our > > >> kernel module's tarball. If those files were ported to > > BSD, in theory > > >> everything else "should" work, though I'm sure we'd need a > > bit of testing > > >> before that became fully true. > > >> > > >> We do plan to start on a FreeBSD port soon, we just > > haven't had time yet. > > >> However, if there's someone interested in trying to help > > do this port, > > >> we'd be happy to talk to them. They can email me at > > nick@nvidia.com. > > > > Doug Rabson is the person responsible for the agp miniport driver > > currently in FreeBSD and I believe he is also a programmer working on > > the Direct Rendering Infrastructure over at Sourceforge. > > > > > > Basically what should require work is probably the detection of your > > [Nvidia] cards and its subsequent support in DRI. I might be > > a bit off > > here, but I am sure one of my more knowledgable committers or > > fellow BSD > > users will correct me if wrong. > > > > >> BTW, we did also speak with the FreeBSD guys at > > linuxworld, I think we > > >> have a possible way we could check our code into the > > FreeBSD tree, which > > >> would be great once we do get it working well. > > > > There's the opportunity of one or more of your people to become a > > FreeBSD committer, or you can proxy through a committer, such as Mike > > Smith is doing for Adaptec's DPT driver. > > > > >> Feel free to post this, btw. I also really like BSD. > > > > Nice to see some BSD interest from the major companies aside from all > > the Linux hype. =) > > You cannot believe how happy I am to read things like this. > > > > Kind regards, > > > > -- > > Jeroen Ruigrok van der Werven Network- and > > systemadministrator > > VIA Net.Works The Netherlands > > BSD: Technical excellence at its best http://www.via-net-works.nl > > Lead us not into temptation, but deliver us from evil... > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 14: 7:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from diogenis.ceid.upatras.gr (diogenis.ceid.upatras.gr [150.140.141.181]) by hub.freebsd.org (Postfix) with SMTP id 3A86837B422 for ; Thu, 7 Sep 2000 14:07:32 -0700 (PDT) Received: (qmail 20520 invoked by uid 1604); 7 Sep 2000 21:03:58 -0000 Date: Fri, 8 Sep 2000 00:03:58 +0300 (EET DST) From: Balis George To: freebsd-hackers@freebsd.org Subject: ports cvsup Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The last days I am trying to cvs both the latest stable source and the latest ports from several servers. The problem is that when I am cvsing the ports I get a segmentation faults and cvsup exits ungracefully with a core dump. What could be wrong? I include some maybe helpful info achilles# uname -a FreeBSD achilles 4.1-RELEASE FreeBSD 4.1-RELEASE #0: Wed Aug 30 18:30:24 EEST 2000 root@achilles:/usr/src/sys/compile/ACHILLES i386 --------------------------------------------------------------------------------- achilles# /usr/local/bin/cvsup -g -L 2 /usr/local/etc/cvsup/freebsd-ports-supfile Parsing supfile "/usr/local/etc/cvsup/freebsd-ports-supfile" Connecting to cvsup3.FreeBSD.org Connected to cvsup3.FreeBSD.org Server software version: REL_16_1 Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running Updating collection ports-base/cvs Edit ports/INDEX Add delta 1.293 2000.09.05.19.23.28 asami Checkout ports/Mk/bsd.ruby.mk Edit ports/Mk/bsd.sites.mk Add delta 1.9 2000.09.05.01.04.52 steve Illegal instruction (core dumped) achilles# pkg_info -a | grep cvsup Information for cvsup-16.1: Information for cvsup-bin-16.1: Information for cvsupd-bin-16.1: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 15:54:51 2000 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 2FDE637B43E; Thu, 7 Sep 2000 15:54:48 -0700 (PDT) Received: from bagabeedaboo.security.at12.de (dial-213-168-64-109.netcologne.de [213.168.64.109]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id AAA23711; Fri, 8 Sep 2000 00:54:46 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.11.0/8.11.0) with ESMTP id e87MscP00647; Fri, 8 Sep 2000 00:54:39 +0200 (CEST) (envelope-from pherman@frenchfries.net) Date: Fri, 8 Sep 2000 00:54:38 +0200 (CEST) From: Paul Herman To: freebsd-hackers@FreeBSD.ORG Subject: the ol' init securelevel thread 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, [ Bcc'ed to -current ] Perhaps it was a mistake :) but I took up someone else's cause and started a thread on -current which now probably belongs on -hackers. So: What are the dangers of having init lower the securelevel to 0 when the system goes into single user? Looking at the mailing list archive, this seems to be a re-occuring thread which always ended up open-ended with no real answer. Already established: * you _can't_ ptrace(2) init when securelevel > 0 * rev1.9 of kern_mib.c unfortunately states nothing concrete * both NetBSD and OpenBSD allow this behaviour * Easy, I'm not married to this idea :-) Just interested "academicaly" So, what dangers are there? -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 19:28: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f159.pav1.hotmail.com [64.4.31.159]) by hub.freebsd.org (Postfix) with ESMTP id 6126337B424; Thu, 7 Sep 2000 19:27:58 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 7 Sep 2000 19:27:57 -0700 Received: from 165.247.24.83 by pv1fd.pav1.hotmail.msn.com with HTTP; Fri, 08 Sep 2000 02:27:57 GMT X-Originating-IP: [165.247.24.83] From: "John Doh!" To: security@freebsd.org, hackers@freebsd.org Subject: How to stop problems from printf Date: Thu, 07 Sep 2000 18:27:57 AKDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 08 Sep 2000 02:27:57.0802 (UTC) FILETIME=[66B194A0:01C0193C] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello to you am I C coder who to wish write programs we cannot exploit via code such as below. > > main(int argc, char **argv) > { > if(argc > 1) { > printf(gettext("usage: %s filename\n"),argv[0]); > exit(0); > } > printf("normal execution proceeds...\n"); > } Issue is must be getting format string from "untrusted" place, but want to limit substitution of %... to the substitution of say in example the argv[0], but to not do others so that say given "usage: %s filename %p" %p not interpret but to be print instead as literally so we get output of (saying to be argv[0] as test just for example) usage: test filename %p any hints you have I am very greatful for. _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 19:33:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 8DACE37B424; Thu, 7 Sep 2000 19:33:14 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e882XEv16204; Thu, 7 Sep 2000 19:33:14 -0700 (PDT) Date: Thu, 7 Sep 2000 19:33:14 -0700 From: Alfred Perlstein To: John Doh! Cc: security@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: How to stop problems from printf Message-ID: <20000907193314.B12231@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from johndoh_@hotmail.com on Thu, Sep 07, 2000 at 06:27:57PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * John Doh! [000907 19:28] wrote: > Hello to you am I C coder who to wish write programs we cannot exploit via > code such as below. > > > > > main(int argc, char **argv) > > { > > if(argc > 1) { > > printf(gettext("usage: %s filename\n"),argv[0]); > > exit(0); > > } > > printf("normal execution proceeds...\n"); > > } > > Issue is must be getting format string from "untrusted" place, but want to > limit substitution of %... to the substitution of say in example the > argv[0], but to not do others so that say given "usage: %s filename %p" %p > not interpret but to be print instead as literally so we get output of > (saying to be argv[0] as test just for example) usage: test filename %p > > any hints you have I am very greatful for. try "%%p" -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 19:37:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f151.pav1.hotmail.com [64.4.31.151]) by hub.freebsd.org (Postfix) with ESMTP id AC76937B42C; Thu, 7 Sep 2000 19:37:34 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 7 Sep 2000 19:37:34 -0700 Received: from 165.247.24.83 by pv1fd.pav1.hotmail.msn.com with HTTP; Fri, 08 Sep 2000 02:37:34 GMT X-Originating-IP: [165.247.24.83] From: "John Doh!" To: bright@wintelcom.net Cc: security@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: How to stop problems from printf Date: Thu, 07 Sep 2000 18:37:34 AKDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 08 Sep 2000 02:37:34.0507 (UTC) FILETIME=[BE6FC7B0:01C0193D] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Alfred Perlstein >To: John Doh! >CC: security@FreeBSD.ORG, hackers@FreeBSD.ORG >Subject: Re: How to stop problems from printf >Date: Thu, 7 Sep 2000 19:33:14 -0700 > >* John Doh! [000907 19:28] wrote: > > Hello to you am I C coder who to wish write programs we cannot exploit >via > > code such as below. > > > > > > > > main(int argc, char **argv) > > > { > > > if(argc > 1) { > > > printf(gettext("usage: %s filename\n"),argv[0]); > > > exit(0); > > > } > > > printf("normal execution proceeds...\n"); > > > } > > > > Issue is must be getting format string from "untrusted" place, but want >to > > limit substitution of %... to the substitution of say in example the > > argv[0], but to not do others so that say given "usage: %s filename %p" >%p > > not interpret but to be print instead as literally so we get output of > > (saying to be argv[0] as test just for example) usage: test filename %p > > > > any hints you have I am very greatful for. > >try "%%p" > >-Alfred That is what I would do if I could always control string, but point is input string is not trusted...how to either validate or else to have printf limit to its arguments. Any ideas? _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 19:59:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 070B137B423; Thu, 7 Sep 2000 19:59:40 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id UAA40578; Thu, 7 Sep 2000 20:59:38 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id UAA50393; Thu, 7 Sep 2000 20:59:18 -0600 (MDT) Message-Id: <200009080259.UAA50393@harmony.village.org> To: "John Doh!" Subject: Re: How to stop problems from printf Cc: security@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 07 Sep 2000 18:27:57 +0700." References: Date: Thu, 07 Sep 2000 20:59:18 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "John Doh!" writes: : Issue is must be getting format string from "untrusted" place, but want to : limit substitution of %... to the substitution of say in example the : argv[0], but to not do others so that say given "usage: %s filename %p" %p : not interpret but to be print instead as literally so we get output of : (saying to be argv[0] as test just for example) usage: test filename %p : : any hints you have I am very greatful for. Fix gettext to only allow N arguments in the same order that the original message had. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 20:16:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from milquetoast.cs.mcgill.ca (milquetoast.CS.McGill.CA [132.206.2.5]) by hub.freebsd.org (Postfix) with ESMTP id 1C81737B423 for ; Thu, 7 Sep 2000 20:16:43 -0700 (PDT) Received: (from mat@localhost) by milquetoast.cs.mcgill.ca (8.9.3/8.9.3) id XAA27688 for freebsd-hackers@freebsd.org; Thu, 7 Sep 2000 23:16:42 -0400 (EDT) Date: Thu, 7 Sep 2000 23:16:42 -0400 From: Mathew KANNER To: freebsd-hackers@freebsd.org Subject: md5 in boot loader Message-ID: <20000907231642.B25604@cs.mcgill.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Organization: SOCS, McGill University, Montreal, CANADA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, What about md5 in the boot loader. I've included a patch to src/sys/boot/ficl/words.c No doubt with lots of little errors. I added this after concerns while working on PXE booting. I'm looking for a sense of direction... Is using MD5 better than just a clear text password or am I wasting my time adding a roll-bar to a little red wagon? --Mat bash-2.03# ./testmain ficl Version 2.03 Sep 7 2000 32 allocate drop dup s" asd" rot md5 32 cr type cr 7815696ecbf1c96e6894b779456d330e ok> bash-2.03# md5 -s "asd" MD5 ("asd") = 7815696ecbf1c96e6894b779456d330e bash-2.03# --- words.c Mon Jun 12 12:46:28 2000 +++ words-md5.c Thu Sep 7 23:01:35 2000 @@ -17,6 +17,7 @@ #else #include #endif +#include #include #include "ficl.h" #include "math64.h" @@ -1207,7 +1208,33 @@ return; } - +/* +** md5 ( s-addr slen d-addr -- ) +** calculate md5 hash of s-addr, stores in d-addr which must be at least +** 32 bytes longs. +*/ +static void md5(FICL_VM *pVM) +{ + STRINGINFO si2; + STRINGINFO si1; + MD5_CTX ctx; + static const char hex[]="0123456789abcdef"; + unsigned char final[16]; + int i; + + SI_SETPTR(si1, stackPopPtr(pVM->pStack)); + SI_SETLEN(si2, stackPopUNS(pVM->pStack)); + SI_SETPTR(si2, stackPopPtr(pVM->pStack)); + MD5Init(&ctx); + MD5Update(&ctx, si2.cp, si2.count); + MD5Final(final,&ctx); + for(i=0; i<16; i++) { + si1.cp[i+i] = hex[final[i] >> 4]; + si1.cp[i+i+1] = hex[final[i] & 0x0f]; + final[i]=0; + } + return; +} /************************************************************************** i n t e r p r e t ** This is the "user interface" of a Forth. It does the following: @@ -4979,6 +5006,7 @@ dictAppendWord(dp, "forget-wid",forgetWid, FW_DEFAULT); dictAppendWord(dp, "hash", hash, FW_DEFAULT); dictAppendWord(dp, "number?", ficlIsNum, FW_DEFAULT); + dictAppendWord(dp, "md5", md5, FW_DEFAULT); dictAppendWord(dp, "parse-word",parseNoCopy, FW_DEFAULT); dictAppendWord(dp, "sliteral", sLiteralCoIm, FW_COMPIMMED); /* STRING */ dictAppendWord(dp, "wid-set-super", -- Mathew Kanner , SOCS McGill University Obtuse quote: He [not me] understands: "This field of perception is void of perception of man." -- The Quintessence of Buddhism To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 20:21:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9FB2437B42C; Thu, 7 Sep 2000 20:21:15 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id UAA69687; Thu, 7 Sep 2000 20:21:15 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 7 Sep 2000 20:21:15 -0700 (PDT) From: Kris Kennaway To: Warner Losh Cc: John Doh! , security@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: How to stop problems from printf In-Reply-To: <200009080259.UAA50393@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 Sep 2000, Warner Losh wrote: > In message "John Doh!" writes: > : Issue is must be getting format string from "untrusted" place, but want to > : limit substitution of %... to the substitution of say in example the > : argv[0], but to not do others so that say given "usage: %s filename %p" %p > : not interpret but to be print instead as literally so we get output of > : (saying to be argv[0] as test just for example) usage: test filename %p > : > : any hints you have I am very greatful for. > > Fix gettext to only allow N arguments in the same order that the > original message had. gettext() doesnt take any additional arguments, AFAIK it just munges the string. The argument substitution was being done by printf() in the example given. "usage: %s filename" -> "blurgle: %s flobodob" But if you're looking up in an untrusted catalog, then it could return "blurgle: %s flobodob %n%n%n%n%n" in which case your function might be insecure. The only possibilities I immediately see are: 1) Don't do that (look up in untrusted catalogs) 2) Write a vgettext(char *buf, int size, const char *fmt...) which a) looks up the message in the catalog, b) verifies the returned string has the same number and type of format strings, and c) substitutes the arguments passed to it using vsnprintf() into the passed buffer. The resulting string should then be handled using function("%s", buf) to deal with escaped format strings ("%%s" which would be parsed to %s by the vsnprintf()). I don't think you can do it securely otherwise, unless I'm missing something. The problem is that you want gettext to substitute arguments into the string, but it doesn't do that, and the string it returns has an unknown number of format strings so it's not safe to use in a varargs function. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 20:52:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8F3D937B42C; Thu, 7 Sep 2000 20:52:16 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA40783; Thu, 7 Sep 2000 21:52:13 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA51001; Thu, 7 Sep 2000 21:52:03 -0600 (MDT) Message-Id: <200009080352.VAA51001@harmony.village.org> To: Kris Kennaway Subject: Re: How to stop problems from printf Cc: John Doh! , security@FreeBSD.org, hackers@FreeBSD.org In-reply-to: Your message of "Thu, 07 Sep 2000 20:21:15 PDT." References: Date: Thu, 07 Sep 2000 21:52:03 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kris Kennaway writes: : gettext() doesnt take any additional arguments, AFAIK it just munges the : string. The argument substitution was being done by printf() in the : example given. Right. You know how many args are expected, since you know printf. : The only possibilities I immediately see are: : : 1) Don't do that (look up in untrusted catalogs) : : 2) Write a vgettext(char *buf, int size, const char *fmt...) which a) : looks up the message in the catalog, b) verifies the returned string has : the same number and type of format strings, and c) substitutes the : arguments passed to it using vsnprintf() into the passed buffer. The : resulting string should then be handled using function("%s", buf) to deal : with escaped format strings ("%%s" which would be parsed to %s by the : vsnprintf()). I don't think you can do it securely otherwise, unless I'm : missing something. : : The problem is that you want gettext to substitute arguments into the : string, but it doesn't do that, and the string it returns has an unknown : number of format strings so it's not safe to use in a varargs function. 3) figure out how many args a string needs and forbid strings with more than that in them. It knows from the original number of % args, can apply the printf rules. It would be trivial to write one function to do must of this. You get the number of args in the key, you get the number of args in the new string using the same routine. If the two numbers aren't equal, you return the original key string, or abort. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 20:57:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8868037B422; Thu, 7 Sep 2000 20:57:07 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id UAA73640; Thu, 7 Sep 2000 20:57:07 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 7 Sep 2000 20:57:07 -0700 (PDT) From: Kris Kennaway To: Warner Losh Cc: John Doh! , security@FreeBSD.org, hackers@FreeBSD.org Subject: Re: How to stop problems from printf In-Reply-To: <200009080352.VAA51001@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 Sep 2000, Warner Losh wrote: > In message Kris Kennaway writes: > : gettext() doesnt take any additional arguments, AFAIK it just munges the > : string. The argument substitution was being done by printf() in the > : example given. > > Right. You know how many args are expected, since you know printf. > > : The only possibilities I immediately see are: > : > : 1) Don't do that (look up in untrusted catalogs) > : > : 2) Write a vgettext(char *buf, int size, const char *fmt...) which a) > : looks up the message in the catalog, b) verifies the returned string has > : the same number and type of format strings, and c) substitutes the > : arguments passed to it using vsnprintf() into the passed buffer. The > : resulting string should then be handled using function("%s", buf) to deal > : with escaped format strings ("%%s" which would be parsed to %s by the > : vsnprintf()). I don't think you can do it securely otherwise, unless I'm > : missing something. > : > : The problem is that you want gettext to substitute arguments into the > : string, but it doesn't do that, and the string it returns has an unknown > : number of format strings so it's not safe to use in a varargs function. > > 3) figure out how many args a string needs and forbid strings with > more than that in them. It knows from the original number of > % args, can apply the printf rules. It would be trivial to write > one function to do must of this. You get the number of args in the > key, you get the number of args in the new string using the same > routine. If the two numbers aren't equal, you return the original > key string, or abort. It also needs to check they are all of the same type, as changing a %d to a %s for example could conceivably be exploitable. And you would have to forbid escaped % characters as well. Yeah, I think that would be doable. We probably should talk to the gnu gettext guys. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 21: 3:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp-out1.bellatlantic.net (smtp-out1.bellatlantic.net [199.45.39.156]) by hub.freebsd.org (Postfix) with ESMTP id 0063C37B423; Thu, 7 Sep 2000 21:03:22 -0700 (PDT) Received: from smartsoft.cc (client-209-158-91-204.bellatlantic.net [209.158.91.204]) by smtp-out1.bellatlantic.net (8.9.1/8.9.1) with ESMTP id AAA05747; Fri, 8 Sep 2000 00:03:11 -0400 (EDT) Message-ID: <39B864D5.5BCC24E7@smartsoft.cc> Date: Fri, 08 Sep 2000 00:02:29 -0400 From: Jan Knepper Organization: Smartsoft, LLC X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "John Doh!" Cc: bright@wintelcom.net, security@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: How to stop problems from printf References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know what you are doing with the 'gettext' in the call to 'printf'. However for printf usage I would always limit the size of a string being displayed with "%s", thus as "%-.80s" for instance. I would *never* do: printf ( argv [ 0 ] ); Since argv [ 0 ] indeed is untrusted. However: printf ( "%s", argv [ 0 ] ); already is a lot safer. You should not have to worry about any content of argv [ 0 ] other than the length if that ever would be an issue. The content of argv [ 0 ] in this case is not being parsed as a C-format string. However for just displaying strings I would use puts or fputs. I mean why call a heavy duty function as printf when the job can be very easily done with a puts/fputs. HTH Jan "John Doh!" wrote: > >From: Alfred Perlstein > >To: John Doh! > >CC: security@FreeBSD.ORG, hackers@FreeBSD.ORG > >Subject: Re: How to stop problems from printf > >Date: Thu, 7 Sep 2000 19:33:14 -0700 > > > >* John Doh! [000907 19:28] wrote: > > > Hello to you am I C coder who to wish write programs we cannot exploit > >via > > > code such as below. > > > > > > > > > > > main(int argc, char **argv) > > > > { > > > > if(argc > 1) { > > > > printf(gettext("usage: %s filename\n"),argv[0]); > > > > exit(0); > > > > } > > > > printf("normal execution proceeds...\n"); > > > > } > > > > > > Issue is must be getting format string from "untrusted" place, but want > >to > > > limit substitution of %... to the substitution of say in example the > > > argv[0], but to not do others so that say given "usage: %s filename %p" > >%p > > > not interpret but to be print instead as literally so we get output of > > > (saying to be argv[0] as test just for example) usage: test filename %p > > > > > > any hints you have I am very greatful for. > > > >try "%%p" > > > >-Alfred > That is what I would do if I could always control string, but point is input > string is not trusted...how to either validate or else to have printf limit > to its arguments. Any ideas? > > _________________________________________________________________________ > Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. > > Share information about yourself, create your own public profile at > http://profiles.msn.com. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message -- Jan Knepper Smartsoft, LLC 88 Petersburg Road Petersburg, NJ 08270 U.S.A. http://www.smartsoft.cc/ http://www.mp3.com/pianoprincess Phone : 609-628-4260 FAX : 609-628-1267 FAX : 303-845-6415 http://www.fax4free.com/ Phone : 020-873-3837 http://www.xoip.nl/ (Dutch) FAX : 020-873-3837 http://www.xoip.nl/ (Dutch) In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 21:14:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8B50D37B422; Thu, 7 Sep 2000 21:14:40 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA40865; Thu, 7 Sep 2000 22:14:38 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA51177; Thu, 7 Sep 2000 22:14:28 -0600 (MDT) Message-Id: <200009080414.WAA51177@harmony.village.org> To: Kris Kennaway Subject: Re: How to stop problems from printf Cc: John Doh! , security@FreeBSD.org, hackers@FreeBSD.org In-reply-to: Your message of "Thu, 07 Sep 2000 20:57:07 PDT." References: Date: Thu, 07 Sep 2000 22:14:28 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kris Kennaway writes: : It also needs to check they are all of the same type, as changing a %d to : a %s for example could conceivably be exploitable. And you would have to : forbid escaped % characters as well. Yeah, I think that would be : doable. We probably should talk to the gnu gettext guys. Hmmm, yes, you would have to check as well. I thought I said that originally. No need to forbid %%, however. That's not exploitable unless you nest these things, and then all bets are off. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 21:56:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id B629A37B422 for ; Thu, 7 Sep 2000 21:56:24 -0700 (PDT) Received: (qmail 19447 invoked by uid 0); 8 Sep 2000 04:56:22 -0000 Received: from p3ee2160d.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.13) by mail.gmx.net with SMTP; 8 Sep 2000 04:56:22 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id GAA15943; Fri, 8 Sep 2000 06:46:25 +0200 Date: Fri, 8 Sep 2000 06:46:25 +0200 From: Gerhard Sittig To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: mtree problem - readlink(2) or chdir(2) failure? Message-ID: <20000908064625.P252@speedy.gsinet> Mail-Followup-To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: System Defenestrators Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG May I attract your attention towards the bin/21017 PR (see http://www.freebsd.org/cgi/query-pr.cgi?pr=21017 for more details) about how mtree(1) fails to compare a file system against a database? I'm stuck in narrowing down what causes the problem and I wouldn't want to be the responsible developer trying to fix this bug with the little and confuse info provided so far. :) It's not that I didn't try to work things out. It's just that I fail to see what's going wrong ... :( Is anybody else using mtree in a similar way? Is somebody else experiencing this failure? Does anybody even know what conditions would "help" to cause the failure (this would be the best thing that could happen)? I apologize for crossposting to multiple lists, but I'm trying to reach the appropriate audience with the will to eliminate this bug. Please don't burden the lists and reply via PM instead, I will summarize and use the gained knowledge to help and solve the problem, of course. Or feel free to f'up to the PR directly when you think the info will be of general interest. This will keep the details in the audit trail and won't bother uninterested list members. Thank you for reading this and considering what would aid in solving the problem. Have a nice day! virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 22: 2:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 879B937B423; Thu, 7 Sep 2000 22:02:45 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id WAA89347; Thu, 7 Sep 2000 22:02:45 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 7 Sep 2000 22:02:45 -0700 (PDT) From: Kris Kennaway To: Jan Knepper Cc: John Doh! , bright@wintelcom.net, security@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: How to stop problems from printf In-Reply-To: <39B864D5.5BCC24E7@smartsoft.cc> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 8 Sep 2000, Jan Knepper wrote: > I don't know what you are doing with the 'gettext' in the call to 'printf'. Translate the string into a localized version. You can't just printf("%s", gettext(...), args) because the arguments won't be printed, only the raw string returned from gettext will, which contains operators you wanted to be substituted for. See the original example. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 22:44:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [203.2.75.105]) by hub.freebsd.org (Postfix) with ESMTP id 7003F37B422 for ; Thu, 7 Sep 2000 22:44:37 -0700 (PDT) Received: from senet.com.au (adlax4-071.dialup.optusnet.com.au [198.142.83.71]) by mail02.syd.optusnet.com.au (8.9.3/8.9.3) with ESMTP id QAA26704 for ; Fri, 8 Sep 2000 16:43:56 +1100 Message-ID: <39B87CB0.A5095CD@senet.com.au> Date: Fri, 08 Sep 2000 15:14:16 +0930 From: Jeff Kirby 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: possible modification / usage of psm driver Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, I'm using a manual switch box for my 3 computers, 1 of which is a bsd box. The switch box is ps/2 kband mouse and video. When i switch away from the bsd box, the mouse won't come back. i can re-enable it using a moused deamon, but its 'out of sync' ( get that error ) and it doesn;t work right ( can move up and right no worries.. any other dir it jumps to bottom of screen) The mouse is a Cordless Logitech Mouseman plus... however this occurs with all my ps/2 mice ( non logitech and MS ). I'm using the psm0 device and at auto port ( comes up as sysmouse Intellimouse) Ive tried using the 'no sync check' flags but to no avail. So heres what i want to do.. in short, when the mouse gets out of sync, reset it. Now ive looked at the code, but im missing some of the information required to make the changes.. i can't find mouse.h for one thing :(.. So any help here would be great :) BSD version is 4.1 release, no updates. Regards Jeff Kirby To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Sep 7 23: 9:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a1-3a105.neo.rr.com [24.93.180.105]) by hub.freebsd.org (Postfix) with ESMTP id 52ECA37B422 for ; Thu, 7 Sep 2000 23:09:19 -0700 (PDT) Received: from localhost (mike@localhost) by jason.argos.org (8.10.1/8.10.1) with ESMTP id e8864qL06245; Fri, 8 Sep 2000 02:04:52 -0400 Date: Fri, 8 Sep 2000 02:04:52 -0400 (EDT) From: Mike Nowlin To: John Brann Cc: hackers@FreeBSD.ORG Subject: Re: [john: tty behaviour] In-Reply-To: <20000907095254.A52345@freebie.brann.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 > I sent this to questions a couple of weeks ago, but didn't receive any > helpful replies. Anyone doing this - two machines connected by a null-modem > cable with the ability to create a serial terminal session from either > side, with suitable juggling of getty processes? Used to do this in Linux w/o any problems... Just make sure that each side waits for CD to go high before actively "starting" the getty process, and that DTR is NOT asserted while the lines are idle. Kick up kermit (or whatever) on the box 1, and the DTR signal from box 1 goes to CD of box 2 - box 2 sends a login prompt, and life is good. (If memory's working, I had to beat up getty a bit to keep DTR low when it was idle, but that wasn't too difficult - one ioctl at the appropriate place... If I remember, I'll look at this a little more carefully when I'm not so fried.) mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 0: 9:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 013A437B423 for ; Fri, 8 Sep 2000 00:09:13 -0700 (PDT) Received: (qmail 56413 invoked by uid 1000); 8 Sep 2000 07:09:10 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 8 Sep 2000 07:09:10 -0000 Date: Fri, 8 Sep 2000 02:09:10 -0500 (CDT) From: Mike Silbersack To: Peter Wemm Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: FYI: RSA Donated to the public domain In-Reply-To: <200009070848.e878m5G55687@netplex.com.au> 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 Sep 2000, Peter Wemm wrote: > Mike Silbersack wrote: > > Ok, now I have a question. Using STARTTLS with sendmail is obviously OK > > for us, since sendmail got the export liscense. However, AFAIK, qmail and > > postfix have obtained no such permission. > > Postfix has done the BXA hoop thing too. It is fully exportable (and > reexportable) and has a TLS etc implementation. > > Cheers, > -Peter Excellent, glad that 2/3 MTAs are done. Now, on to qmail. I'm assuming that Bernstein won't go through the hassle of getting approval, especially since I don't know where the snuffle trial is currently at in appeals. However, the TLS patch for qmail at http://www.esat.kuleuven.ac.be/~vermeule/qmail/tls.patch patches cleanly, and works great. Like OpenSSH / etc, it uses OpenSSL for all crypto work. Which of the following options would be legal: 1. Have the port fetch the patch from the .be site, patch qmail, and finish building it. 2. Include a (possibly modified) version of the patch in the ports tree, which would be applied when building qmail. (The port makefile would also wish to call the patched qmail makefile to create a CA during the build process as well. I'm not sure if that has additional implications.) I'm assuming #1's good, since that's how the OpenSSH port worked. Would #2 be any different? Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 3:59:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from distortion.dk (distortion.dk [195.249.147.156]) by hub.freebsd.org (Postfix) with ESMTP id A4D6437B424 for ; Fri, 8 Sep 2000 03:59:14 -0700 (PDT) Received: (from npp@localhost) by distortion.dk (8.9.3/8.9.1) id NAA38560 for hackers@freebsd.org; Fri, 8 Sep 2000 13:01:23 +0200 (CEST) (envelope-from npp) Date: Fri, 8 Sep 2000 13:01:23 +0200 (CEST) From: Nicolai Petri Message-Id: <200009081101.NAA38560@distortion.dk> To: hackers@freebsd.org Subject: Creating a list of newbus devices. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible from kernel mode to create a list of newbus devices ? And how do I'll get a pointer to the new-bus root (or whatever it's tecnical name is :) --- Nicolai Petri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 4:46:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C457537B42C; Fri, 8 Sep 2000 04:46:44 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA90969; Fri, 8 Sep 2000 13:48:41 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200009081148.NAA90969@freebsd.dk> Subject: New ATA tagged queuing patch available To: current@freebsd.org, hackers@freebsd.org Date: Fri, 8 Sep 2000 13:48:40 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the README: ATA-tagged-queueing-diff-0908: Add support for ATA channels with both a master and a slave, even combos where only on of them supports tagged queuing should work now. Also only switch on tagged queuing on IBM DPTA & DTLA series drives, the older DJNA has firmware problems. I am working on a SW solution to that, but for now only enable tagged queuing on drives that is known to work. Get it from http://freebsd.dk, and let me know your results If I dont get any serious problem reports I'll commit this shortly, making FreeBSD the first OS that has tagged Queuing support for ATA drives :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 6:39: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from calcaphon.demon.co.uk (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 9A11537B43E for ; Fri, 8 Sep 2000 06:39:01 -0700 (PDT) Received: from henny.webweaving.org (henny.qubesoft.com [192.168.1.5]) by calcaphon.demon.co.uk (8.9.3/8.9.1) with ESMTP id OAA19225; Fri, 8 Sep 2000 14:39:00 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id OAA60881; Fri, 8 Sep 2000 14:37:44 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Fri, 8 Sep 2000 14:37:44 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: Nicolai Petri Cc: FreeBSD Hackers Mailing List Subject: Re: Creating a list of newbus devices. In-Reply-To: <200009081101.NAA38560@distortion.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The answers are 'no' and 'root_bus'. The 'no' could be revised into something more useful if you are able to tell us what you are trying to do. Nick On Fri, 8 Sep 2000, Nicolai Petri wrote: > Is it possible from kernel mode to create a list of newbus devices ? > And how do I'll get a pointer to the new-bus root (or whatever it's > tecnical name is :) > > --- > Nicolai Petri > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 6:59: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from guardian.hermes.si (guardian.hermes.si [193.77.5.150]) by hub.freebsd.org (Postfix) with ESMTP id 94F4937B423 for ; Fri, 8 Sep 2000 06:58:56 -0700 (PDT) Received: from hermes.si (primus.hermes.si [193.77.5.98]) by guardian.hermes.si (8.9.3/8.9.3) with ESMTP id PAA22419 for ; Fri, 8 Sep 2000 15:58:39 +0200 (METDST) Received: (from uucp@localhost) by hermes.si (8.9.3/8.9.3) id PAA17985 for ; Fri, 8 Sep 2000 15:58:34 +0200 Received: from lamu.hermes.si(10.17.1.230) by primus.hermes.si via smap (V2.1) id xmab19107; Fri, 8 Sep 00 15:53:11 +0200 Received: (from mitja@localhost) by lamu.hermes.si (8.9.3/8.9.3) id PAA16456 for freebsd-hackers@freebsd.org; Fri, 8 Sep 2000 15:44:10 +0200 (CEST) Date: Fri, 8 Sep 2000 15:44:10 +0200 From: Mitja Horvat To: freebsd-hackers@freebsd.org Subject: makecontext() & friends ? Message-ID: <20000908154410.A16446@lamu.hermes.si> Reply-To: mitja@herme.si.hermes.si Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, are there any plans to implement makecontext() & friends functions in FreeBSD? Is there any other way to implement user-level threads? (I know it can be done in assembler, but this is not portable) Using pthreads is not an option for me, although pthreads are implemented as userlevel threads in FreeBSD, but not on most other Unixes. Thanx for your answers, Mitja To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 6:59:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from guardian.hermes.si (guardian.hermes.si [193.77.5.150]) by hub.freebsd.org (Postfix) with ESMTP id E58BF37B42C for ; Fri, 8 Sep 2000 06:59:11 -0700 (PDT) Received: from hermes.si (primus.hermes.si [193.77.5.98]) by guardian.hermes.si (8.9.3/8.9.3) with ESMTP id PAA22456 for ; Fri, 8 Sep 2000 15:59:07 +0200 (METDST) Received: (from uucp@localhost) by hermes.si (8.9.3/8.9.3) id PAA21343 for ; Fri, 8 Sep 2000 15:59:04 +0200 Received: from lamu.hermes.si(10.17.1.230) by primus.hermes.si via smap (V2.1) id xmad19107; Fri, 8 Sep 00 15:53:11 +0200 Received: (from mitja@localhost) by lamu.hermes.si (8.9.3/8.9.3) id PAA15868 for freebsd-hackers@freebsd.org; Fri, 8 Sep 2000 15:19:43 +0200 (CEST) Date: Fri, 8 Sep 2000 15:19:42 +0200 From: Mitja Horvat To: freebsd-hackers@freebsd.org Subject: makecontext & friends ? Message-ID: <20000908151942.A15852@lamu.hermes.si> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, are there any plans to implement makecontext() & friends functions in FreeBSD? Is there any other way to implement user-level threads? (I know it can be done in assembler, but this is not portable) Using pthreads is not an option for me, although pthreads are implemented as userlevel threads in FreeBSD, but not on most other Unixes. Thanx for your answers, Mitja To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 7: 5: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tungsten.btinternet.com (tungsten.btinternet.com [194.73.73.81]) by hub.freebsd.org (Postfix) with ESMTP id C9F7137B43E for ; Fri, 8 Sep 2000 07:04:58 -0700 (PDT) Received: from host62-6-66-155.btinternet.com ([62.6.66.155] helo=btinternet.com) by tungsten.btinternet.com with esmtp (Exim 3.03 #83) id 13XOly-00006V-00 for freebsd-hackers@freebsd.org; Fri, 08 Sep 2000 15:04:54 +0100 Message-ID: <39B8EFFA.785E6D46@btinternet.com> Date: Fri, 08 Sep 2000 14:56:10 +0100 From: John Toon X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: Shared Memory Issues References: <39B4BD1D.676139D4@btinternet.com> <20000905230110.A9425@host.cer.ntnu.edu.tw> <39B58ABD.1B215190@btinternet.com> <39B7C08B.5841BA62@linkline.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lance Rocker wrote: > Hello, > > I too had problems with running out of shared mem segments, so I wrote > my first ever perl script that does something useful for me. I've > attached it to this email and I'll paste it in below too, for > convenience. > > I noticed that many (most?) of the shared mem segments in use, when I > was running out of them, didn't actually have any processes attached to > them. This perl script just goes through, finds those non-attached > shared mem segments, and deletes them. I've found running it > periodically works great for me, you may even want to put it in your > crontab and let it run once a day, just as a little proactive > housekeeping. Hey, nice script. Is there anything Perl can't do these days? ;^) I'm currently just enjoying the power of awk. I hope it doesn't get forgotten in the shadow of Perl. However, it seems strange that you're getting non-attached memory segments. Surely it is the job of the kernel to clean up after processes (if they're badly programmed and don't do it themselves)? Perhaps one program is leaking? My system has been up for two days now since last reboot, I just ran your program, and I had 55 shared memory segments, 0 non-attached... > For the record, here are the kernel options I use with this kernel: > > options SYSVSHM #SYSV-style shared memory > options SYSVMSG #SYSV-style message queues > options SYSVSEM #SYSV-style semaphores > options SHMALL=16384 > options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" > options SHMMAXPGS=8192 > options SHMMIN=128 > options SHMMNI=128 > options SHMSEG=96 > > I think that last one makes the biggest difference, and is the one you > may want to make as large as possible, though 96 works fine for my 64MB > of ram. This is a 4.0-release kernel, and I use XFree86 4.0 with > Enlightenment as my window manager. It definitely does! The default setting, as someone correctly pointed out, in LINT, is SHMSEG=9. As you can see above, my system is currently using 55, more than 5X that limit! I've sent in a brief e-mail to freebsd-stable, suggesting that the GENERIC kernel default is altered to something a little higher. The SHMSEG setting is under the "undocumented" options in LINT, which is not helpful or conducive to people fixing this problem. It's a good job freebsd-hackers exists... ;^) The SHMSEG=1024 setting I've got is probably excessive, but I would guess the performance degradation is negligible to non-existent in having more than you need, especially due to FreeBSD's unmatched memory management, as I've noticed no difference in performance. > yes, ipcs and ipcrm are the ones my perl script uses. Check out the > manpage for each of them. . . I like to run "ipcs -mbop" to get a lot > of info about used shared mem segments. > > -Lance Yes, they both have more settings than I was aware of. Oh, the joy of manpages... -- "I'm entirely unaccountable for any moments of sanity contained herein." :s/Windows/UNIX John Toon | j.a.toon@btinternet.com | "Sonnilon" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 7:16:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id 4B31237B43F for ; Fri, 8 Sep 2000 07:16:41 -0700 (PDT) Received: (qmail 25205 invoked by uid 66); 8 Sep 2000 14:25:35 -0000 Received: from en by slarti with UUCP; Fri Sep 8 14:25:35 2000 -0000 Received: by en1.engelschall.com (Sendmail 8.11.0+) for freebsd-hackers@freebsd.org id e88EFgc87915; Fri, 8 Sep 2000 16:15:42 +0200 (CEST) Date: Fri, 8 Sep 2000 16:15:42 +0200 From: "Ralf S. Engelschall" To: freebsd-hackers@freebsd.org Subject: Re: makecontext & friends ? Message-ID: <20000908161542.A87619@engelschall.com> Reply-To: rse@engelschall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Engelschall, Germany. X-Web-Homepage: http://www.engelschall.com/ X-PGP-Public-Key: https://www.engelschall.com/ho/rse/pgprse.asc X-PGP-Fingerprint: 00 C9 21 8E D1 AB 70 37 DD 67 A2 3A 0A 6F 8D A5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000908151942.A15852@lamu.hermes.si> you wrote: > are there any plans to implement makecontext() & friends > functions in FreeBSD? I don't know of any plans myself, but I would appreciate that we support this standardized ucontext(3) API in FreeBSD. The API is actually not the problem, the question is on what should this API internally be based? On an own mechanism or on an existing mechanism (jmp_buf, etc)? > Is there any other way to implement user-level threads? > (I know it can be done in assembler, but this is not > portable) Sure, it can. See my GNU Portable Threads under http://www.gnu.org/software/pth/. We have a port under devel/pth, too. It bases its user-land threads on ucontext(3) if available or on setjmp(3)'s jmp_buf, etc. All without any assembler things. For details read my USENIX paper under http://www.gnu.org/software/pth/rse-pmt.ps. > Using pthreads is not an option for me, although pthreads > are implemented as userlevel threads in FreeBSD, but not > on most other Unixes. If you need maximum portability, then GNU Pth certainly is an option for you. Ralf S. Engelschall rse@engelschall.com www.engelschall.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 7:18: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-04-real.cdsnet.net (mail-04-real.cdsnet.net [63.163.68.109]) by hub.freebsd.org (Postfix) with SMTP id AB97637B43E for ; Fri, 8 Sep 2000 07:18:02 -0700 (PDT) Received: (qmail 10767 invoked from network); 8 Sep 2000 14:17:56 -0000 Received: from apocalypse.cdsnet.net (63.163.68.5) by mail-04-real.cdsnet.net with SMTP; 8 Sep 2000 14:17:56 -0000 Date: Fri, 8 Sep 2000 07:17:56 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@apocalypse.cdsnet.net To: ports@freebsd.org Cc: hackers@freebsd.org Subject: How many -k's does a build need? 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 noticed this little oddity while building XFree86-4, from ports supped today: make -k -f xmakefile all root 17383 0.0 0.2 628 244 p6 I+ 6:30AM 0:00.00 (sh) root 36617 0.0 0.5 1076 680 p6 I+ 6:51AM 0:00.05 make -k -k CDEBUGFLAGS= all root 36618 0.0 0.2 628 244 p6 I+ 6:51AM 0:00.05 (sh) root 39601 0.0 0.6 1164 768 p6 I+ 6:57AM 0:00.10 make -k -k -k -k CDEBUGFLAGS= all root 45736 0.0 0.2 628 244 p6 I+ 7:12AM 0:00.00 /bin/sh -ec cd hw/xfree86 ; echo "making all in programs/Xserver/hw/x root 45737 0.0 0.6 1128 756 p6 I+ 7:12AM 0:00.07 make -k -k -k -k -k -k -k -k CDEBUGFLAGS= LDSTRIPFLAGS=-x all root 45766 0.0 0.2 628 244 p6 I+ 7:12AM 0:00.01 (sh) root 47311 0.0 0.6 1116 716 p6 I+ 7:14AM 0:00.05 make -k -k -k -k -k -k -k -k -k -k -k -k -k -k -k -k CDEBUGFLAGS= LDS root 47312 0.0 0.2 628 244 p6 S+ 7:14AM 0:00.00 (sh) root 47648 0.4 0.7 1256 880 p6 S+ 7:16AM 0:00.13 make -k -k -k -k -k -k -k Maybe more make it go faster... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 9:28:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 695AD37B43E for ; Fri, 8 Sep 2000 09:28:36 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA43366; Fri, 8 Sep 2000 10:28:34 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA55850; Fri, 8 Sep 2000 10:28:22 -0600 (MDT) Message-Id: <200009081628.KAA55850@harmony.village.org> To: Nicolai Petri Subject: Re: Creating a list of newbus devices. Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 08 Sep 2000 13:01:23 +0200." <200009081101.NAA38560@distortion.dk> References: <200009081101.NAA38560@distortion.dk> Date: Fri, 08 Sep 2000 10:28:22 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009081101.NAA38560@distortion.dk> Nicolai Petri writes: : Is it possible from kernel mode to create a list of newbus devices ? : And how do I'll get a pointer to the new-bus root (or whatever it's : tecnical name is :) Yes. You keep asking for parents until you get none. The one that has a null parent is the nexus. You can then walk the tree from there. See kern/subr_bus.c for the routines to do this, and read the assocaited man pages. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 9:51:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id A888437B423 for ; Fri, 8 Sep 2000 09:51:19 -0700 (PDT) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id MAA14561; Fri, 8 Sep 2000 12:50:47 -0400 (EDT) Date: Fri, 8 Sep 2000 12:50:47 -0400 (EDT) From: Daniel Eischen To: mitja@herme.si.hermes.si Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: makecontext() & friends ? In-Reply-To: <20000908154410.A16446@lamu.hermes.si> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 8 Sep 2000, Mitja Horvat wrote: > Hi, > > are there any plans to implement makecontext() & friends > functions in FreeBSD? > > Is there any other way to implement user-level threads? > (I know it can be done in assembler, but this is not > portable) > > Using pthreads is not an option for me, although pthreads > are implemented as userlevel threads in FreeBSD, but not > on most other Unixes. I have implemented {make,get,set,swap}context as library routines for FreeBSD. They're gathering dust somewhere and need a bit of polishing. If you give me some time I can dust them off and send them to you. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 9:55:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id C3A1737B424; Fri, 8 Sep 2000 09:55:32 -0700 (PDT) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id MAA353916; Fri, 8 Sep 2000 12:55:29 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Fri, 8 Sep 2000 12:57:08 -0400 To: "John Doh!" , security@FreeBSD.ORG, hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: How to stop problems from printf Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:27 PM -0400 9/7/00, John Doh! wrote: >Hello to you am I C coder who to wish write programs we cannot >exploit via code such as below. > >> >> main(int argc, char **argv) >> { >> if(argc > 1) { >> printf(gettext("usage: %s filename\n"),argv[0]); >> exit(0); >> } >> printf("normal execution proceeds...\n"); >> } > >Issue is must be getting format string from "untrusted" place, but want >to limit substitution of %... to the substitution of say in example the >argv[0], but to not do others so that say given "usage: %s filename %p" >%p not interpret but to be print instead as literally so we get output >of (saying to be argv[0] as test just for example) >usage: test filename %p Since gettext is getting a string from an untrusted place, you should treat it as you would treat a string being typed in from a user. For the example you give, you know that you are expecting ONE %s argument, and that ONE %s is the only substitution you will allow. So, have gettext return it's value into some string. Then, YOU search that string for '%s'. then you do a printf of: printf("%s%s%s", textBefore%s, argv[0], textAfter%s); For the given example, this is pretty trivial. If you have several different values you will substitute in the string returned by gettext, then it gets a bit more cumbersome. My suggestion is a fine solution for your example (IMO :-), but if you did have more substitutions then I might try some alternate strategy. One has to be careful about buffer overflows in that temp string, of course. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 10: 1: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 2FCE737B42C for ; Fri, 8 Sep 2000 10:01:02 -0700 (PDT) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id NAA15859; Fri, 8 Sep 2000 13:00:43 -0400 (EDT) Date: Fri, 8 Sep 2000 13:00:42 -0400 (EDT) From: Daniel Eischen To: "Ralf S. Engelschall" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: makecontext & friends ? In-Reply-To: <20000908161542.A87619@engelschall.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 8 Sep 2000, Ralf S. Engelschall wrote: > > In article <20000908151942.A15852@lamu.hermes.si> you wrote: > > > are there any plans to implement makecontext() & friends > > functions in FreeBSD? > > I don't know of any plans myself, but I would appreciate that we support this > standardized ucontext(3) API in FreeBSD. The API is actually not the problem, > the question is on what should this API internally be based? On an own > mechanism or on an existing mechanism (jmp_buf, etc)? My implementation of it was based on a trapframe, so it would be easy to pass a ucontext_t to the kernel and have it switch to the context at appropriate times (scheduler activations). A trapframe is the same as a sigcontext_t (ucontext_t) for i386 but not for the alpha. I think I got around this by adding a type field to the ucontext (or mcontext) to indicate which format it was for alpha. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 10:35:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (r148m178.cybercable.tm.fr [195.132.148.178]) by hub.freebsd.org (Postfix) with ESMTP id A3DF437B42C for ; Fri, 8 Sep 2000 10:35:19 -0700 (PDT) Received: from cybercable.fr (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id TAA35001; Fri, 8 Sep 2000 19:03:54 +0200 (CEST) (envelope-from herbelot@cybercable.fr) Message-ID: <39B91BFA.CEA71E57@cybercable.fr> Date: Fri, 08 Sep 2000 19:03:54 +0200 From: Thierry Herbelot X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: hackers@freebsd.org Subject: Re: New ATA tagged queuing patch available References: <200009081148.NAA90969@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > > >From the README: > > ATA-tagged-queueing-diff-0908: > Add support for ATA channels with both a master and a slave, even > combos where only on of them supports tagged queuing should work now. > Also only switch on tagged queuing on IBM DPTA & DTLA series > drives, the older DJNA has firmware problems. I am working on > a SW solution to that, but for now only enable tagged queuing > on drives that is known to work. > > Get it from http://freebsd.dk, and let me know your results > > If I dont get any serious problem reports I'll commit this > shortly, making FreeBSD the first OS that has tagged Queuing > support for ATA drives :) > > -Søren Nice try ! Any chance an older IBM drive might be supported ? 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 Fri Sep 8 11: 5:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B856737B42C for ; Fri, 8 Sep 2000 11:05:26 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA81585; Fri, 8 Sep 2000 20:07:25 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200009081807.UAA81585@freebsd.dk> Subject: Re: New ATA tagged queuing patch available In-Reply-To: <39B91BFA.CEA71E57@cybercable.fr> from Thierry Herbelot at "Sep 8, 2000 07:03:54 pm" To: herbelot@cybercable.fr (Thierry Herbelot) Date: Fri, 8 Sep 2000 20:07:25 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Thierry Herbelot wrote: > Soren Schmidt wrote: > > > > >From the README: > > > > ATA-tagged-queueing-diff-0908: > > Add support for ATA channels with both a master and a slave, even > > combos where only on of them supports tagged queuing should work now. > > Also only switch on tagged queuing on IBM DPTA & DTLA series > > drives, the older DJNA has firmware problems. I am working on > > a SW solution to that, but for now only enable tagged queuing > > on drives that is known to work. > > > > Get it from http://freebsd.dk, and let me know your results > > > > If I dont get any serious problem reports I'll commit this > > shortly, making FreeBSD the first OS that has tagged Queuing > > support for ATA drives :) > > > > -Søren > > Nice try ! Yeah :) > Any chance an older IBM drive might be supported ? > Well, the DTTA's say they support tagged queuing, but since the newer DJNA has firmware problems the DTTA probably has that too. To be fair I havn't tried it yet, so if you feel adventurous you can try to add it to the ad_tagsupported function in ata-disk.c and see what happens.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 11:28:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B38D937B422 for ; Fri, 8 Sep 2000 11:28:41 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA01293; Fri, 8 Sep 2000 11:28:27 -0700 Date: Fri, 8 Sep 2000 11:24:47 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Soren Schmidt Cc: Thierry Herbelot , hackers@FreeBSD.ORG Subject: Re: New ATA tagged queuing patch available In-Reply-To: <200009081807.UAA81585@freebsd.dk> 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 > > Yeah :) > > > Any chance an older IBM drive might be supported ? > > > > Well, the DTTA's say they support tagged queuing, but since the > newer DJNA has firmware problems the DTTA probably has that > too. To be fair I havn't tried it yet, so if you feel adventurous > you can try to add it to the ad_tagsupported function in ata-disk.c > and see what happens.... Gee. You can upgrade F/W in SCSI drives. How about ATA drives? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 11:35:58 2000 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 1289E37B446 for ; Fri, 8 Sep 2000 11:35:55 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e88IZmN81787; Fri, 8 Sep 2000 20:35:48 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: Soren Schmidt , Thierry Herbelot , hackers@FreeBSD.ORG Subject: Re: New ATA tagged queuing patch available In-Reply-To: Your message of "Fri, 08 Sep 2000 11:24:47 PDT." Date: Fri, 08 Sep 2000 20:35:48 +0200 Message-ID: <81785.968438148@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: >> >> Yeah :) >> >> > Any chance an older IBM drive might be supported ? >> > >> >> Well, the DTTA's say they support tagged queuing, but since the >> newer DJNA has firmware problems the DTTA probably has that >> too. To be fair I havn't tried it yet, so if you feel adventurous >> you can try to add it to the ad_tagsupported function in ata-disk.c >> and see what happens.... > >Gee. You can upgrade F/W in SCSI drives. How about ATA drives? Same thing, the trick is to get the update microcode out of IBM. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 12:25: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mir.kapi.net (mir.kapi.net [195.165.21.13]) by hub.freebsd.org (Postfix) with ESMTP id 68D8B37B423 for ; Fri, 8 Sep 2000 12:24:58 -0700 (PDT) Received: from kapi.net (kapi.net [195.165.21.10]) by mir.kapi.net (8.9.3/8.9.3) with ESMTP id WAA63008 for ; Fri, 8 Sep 2000 22:24:51 +0300 (EEST) (envelope-from esko@kapi.net) Received: from localhost (esko@localhost) by kapi.net (8.9.2/8.9.3) with ESMTP id WAA00967 for ; Fri, 8 Sep 2000 22:24:51 +0300 (EEST) (envelope-from esko@kapi.net) X-Authentication-Warning: kapi.net: esko owned process doing -bs Date: Fri, 8 Sep 2000 22:24:51 +0300 (EEST) From: Esko Petteri Matinsola X-Sender: esko@sputnik To: hackers@freebsd.org Subject: Vinum RAID-5 performance problem 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 Thank you for your last reply about the Promise 100 controller, I got it working with that patch. But now, I have Asus P2L97 mobo with 64MB RAM, 266MHz P2 and 4 Maxtor 54098H8's, two per channel. OS is FreeBSD 4.1-STABLE. When I use vinum with the following config: drive drive0 device /dev/ad0e drive drive1 device /dev/ad1e drive drive2 device /dev/ad2e drive drive3 device /dev/ad3e volume raid0 plex org striped 256k sd length 512m drive drive0 sd length 512m drive drive1 so I have RAID-0 with the master and slave drive from controller one. bonnie -s 512 on that gives me: -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 512 13287 97.3 20237 41.0 8023 25.6 8572 97.8 21442 29.4 128.1 2.2 not bad, even when two drives on the same controller. Next, I tried vinum with the following config: drive drive0 device /dev/ad0e drive drive1 device /dev/ad1e drive drive2 device /dev/ad2e drive drive3 device /dev/ad3e volume raid0 plex org striped 256k sd length 512m drive drive0 sd length 512m drive drive2 so I have RAID-0 with the masters from both controllers. bonnie -s 512 gives me: -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 512 13263 97.4 21340 43.7 8169 26.1 8572 98.0 25858 36.6 213.4 3.9 only a little better, except the seeks. Now next to my problem. When I use vinum with the following config: drive drive0 device /dev/ad0e drive drive1 device /dev/ad1e drive drive2 device /dev/ad2e drive drive3 device /dev/ad3e volume raid5 plex org raid5 256k sd length 512m drive drive0 sd length 512m drive drive1 sd length 512m drive drive2 sd length 512m drive drive3 so I have RAID-5 with all the drives from both controllers. bonnie -s 512 gives me: -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 512 2368 17.7 2358 4.8 2016 6.6 8218 94.4 20068 29.1 232.5 4.3 read performance and seeks seems OK, but block writes only about 1/9th ! As I read from www.vinumvm.org I should get something like 5MBps block writes. Have I misunderstood something, configured someting improperly, it's because of only two IDE-controllers or why I get so lousy write performance ? I could live with 5MBps, if I only could get that ! :) Thanks for any suggestions and sorry for too long email. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 12:38:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 86E2C37B423 for ; Fri, 8 Sep 2000 12:38:18 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id UAA00511; Thu, 7 Sep 2000 20:23:11 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009080323.UAA00511@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "John Doh!" Cc: hackers@FreeBSD.ORG Subject: Re: How to stop problems from printf In-reply-to: Your message of "Thu, 07 Sep 2000 18:27:57 +0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Sep 2000 20:23:11 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello to you am I C coder who to wish write programs we cannot exploit via > code such as below. > > > > > main(int argc, char **argv) > > { > > if(argc > 1) { > > printf(gettext("usage: %s filename\n"),argv[0]); > > exit(0); > > } > > printf("normal execution proceeds...\n"); > > } > > Issue is must be getting format string from "untrusted" place, but want to > limit substitution of %... to the substitution of say in example the > argv[0], but to not do others so that say given "usage: %s filename %p" %p > not interpret but to be print instead as literally so we get output of > (saying to be argv[0] as test just for example) usage: test filename %p If you don't trust gettext, you need to write a validation wrapper for it that compares the format specifiers in the source and destination strings. There's no way to "fix" printf to do this. Personally, I'd fix the security on your gettext database and deal with it at that level. -- ... 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] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 12:38:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 9211537B443; Fri, 8 Sep 2000 12:38:19 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id UAA00530; Thu, 7 Sep 2000 20:24:33 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009080324.UAA00530@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: "John Doh!" , security@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: How to stop problems from printf In-reply-to: Your message of "Thu, 07 Sep 2000 20:59:18 MDT." <200009080259.UAA50393@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Sep 2000 20:24:33 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message "John Doh!" writes: > : Issue is must be getting format string from "untrusted" place, but want to > : limit substitution of %... to the substitution of say in example the > : argv[0], but to not do others so that say given "usage: %s filename %p" %p > : not interpret but to be print instead as literally so we get output of > : (saying to be argv[0] as test just for example) usage: test filename %p > : > : any hints you have I am very greatful for. > > Fix gettext to only allow N arguments in the same order that the > original message had. Typically you want to use positional arguments with printf so that your gettext responses can reorder things to get better results, but the same basically applies. -- ... 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] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 12:38:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 6D02A37B43E for ; Fri, 8 Sep 2000 12:38:19 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id UAA00713; Thu, 7 Sep 2000 20:37:20 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009080337.UAA00713@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mathew KANNER Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: md5 in boot loader In-reply-to: Your message of "Thu, 07 Sep 2000 23:16:42 EDT." <20000907231642.B25604@cs.mcgill.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Sep 2000 20:37:18 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello, > What about md5 in the boot loader. I've included a patch to > src/sys/boot/ficl/words.c No doubt with lots of little errors. I > added this after concerns while working on PXE booting. > I'm looking for a sense of direction... Is using MD5 better > than just a clear text password or am I wasting my time adding a > roll-bar to a little red wagon? It's not enough. If you're concerned about diskless booting (a good thing to worry about), you want to look at BIS (bootstrap integrity services) which interacts with PXE and should address most of your concerns. (Making it work will involve some code, mostly on the server side. If you're interested in getting involved in the PXE deal in general, there are several openings for some useful work to be done... > --Mat > > bash-2.03# ./testmain > ficl Version 2.03 > Sep 7 2000 > 32 allocate drop dup s" asd" rot md5 32 cr type cr > > 7815696ecbf1c96e6894b779456d330e > ok> > bash-2.03# md5 -s "asd" > MD5 ("asd") = 7815696ecbf1c96e6894b779456d330e > bash-2.03# > > > --- words.c Mon Jun 12 12:46:28 2000 > +++ words-md5.c Thu Sep 7 23:01:35 2000 > @@ -17,6 +17,7 @@ > #else > #include > #endif > +#include > #include > #include "ficl.h" > #include "math64.h" > @@ -1207,7 +1208,33 @@ > return; > } > > - > +/* > +** md5 ( s-addr slen d-addr -- ) > +** calculate md5 hash of s-addr, stores in d-addr which must be at least > +** 32 bytes longs. > +*/ > +static void md5(FICL_VM *pVM) > +{ > + STRINGINFO si2; > + STRINGINFO si1; > + MD5_CTX ctx; > + static const char hex[]="0123456789abcdef"; > + unsigned char final[16]; > + int i; > + > + SI_SETPTR(si1, stackPopPtr(pVM->pStack)); > + SI_SETLEN(si2, stackPopUNS(pVM->pStack)); > + SI_SETPTR(si2, stackPopPtr(pVM->pStack)); > + MD5Init(&ctx); > + MD5Update(&ctx, si2.cp, si2.count); > + MD5Final(final,&ctx); > + for(i=0; i<16; i++) { > + si1.cp[i+i] = hex[final[i] >> 4]; > + si1.cp[i+i+1] = hex[final[i] & 0x0f]; > + final[i]=0; > + } > + return; > +} > /************************************************************************** > i n t e r p r e t > ** This is the "user interface" of a Forth. It does the following: > @@ -4979,6 +5006,7 @@ > dictAppendWord(dp, "forget-wid",forgetWid, FW_DEFAULT); > dictAppendWord(dp, "hash", hash, FW_DEFAULT); > dictAppendWord(dp, "number?", ficlIsNum, FW_DEFAULT); > + dictAppendWord(dp, "md5", md5, FW_DEFAULT); > dictAppendWord(dp, "parse-word",parseNoCopy, FW_DEFAULT); > dictAppendWord(dp, "sliteral", sLiteralCoIm, FW_COMPIMMED); /* STRING */ > dictAppendWord(dp, "wid-set-super", > > > -- > Mathew Kanner , SOCS McGill University > Obtuse quote: He [not me] understands: "This field of perception > is void of perception of man." -- The Quintessence of Buddhism > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- ... 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] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 12:47:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 73FDB37B42C for ; Fri, 8 Sep 2000 12:47:41 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id NAA00899; Fri, 8 Sep 2000 13:00:26 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009082000.NAA00899@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nicolai Petri Cc: hackers@freebsd.org Subject: Re: Creating a list of newbus devices. In-reply-to: Your message of "Fri, 08 Sep 2000 13:01:23 +0200." <200009081101.NAA38560@distortion.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Sep 2000 13:00:26 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is it possible from kernel mode to create a list of newbus devices ? And > how do I'll get a pointer to the new-bus root (or whatever it's tecnical > name is :) extern devclass_t nexus_devclass; nexus = devclass_get_device(nexus_devclass, 0); static void device_enumerate_children(device_t dev) { device_t *devp; int ndevs, i; if (device_get_children(dev, &devp, &ndevs) || (ndevs == 0)) return; for (i = 0; i < ndevs; i++, devp++) device_enumerate_children(*devp); } -- ... 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] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 12:56:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.desktop.com (mail.desktop.com [166.90.128.242]) by hub.freebsd.org (Postfix) with ESMTP id A8E4937B42C for ; Fri, 8 Sep 2000 12:56:09 -0700 (PDT) Received: from [192.168.1.42] (jumpgate.desktop.com [166.90.128.243]) by mail.desktop.com (8.9.3/8.9.2) with ESMTP id MAA57147; Fri, 8 Sep 2000 12:55:38 -0700 (PDT) (envelope-from clark@desktop.com) Mime-Version: 1.0 X-Sender: clark@mail.desktop.com Message-Id: In-Reply-To: References: Date: Fri, 8 Sep 2000 12:55:51 -0700 To: Esko Petteri Matinsola , hackers@FreeBSD.ORG From: Clark Shishido Subject: Re: Vinum RAID-5 performance problem Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 22:24 +0300 2000.09.08, Esko Petteri Matinsola wrote: > >read performance and seeks seems OK, but block writes only about 1/9th ! >As I read from www.vinumvm.org I should get something like 5MBps block >writes. > >Have I misunderstood something, configured someting improperly, it's >because of only two IDE-controllers or why I get so lousy write >performance ? Your configuration looks fine. I just recently tried a similar setup using Promise Ultra66 controllers with some Quantum and IBM drives (tried both). I got lousy performance doing sustained writes to a RAID5 volume, using 4 UDMA66 drives each a master on a controller. just doing a cat /dev/zero > blah I just decided to stick with striping and make regular backups. I may try vinum with RAID5 on a SCSI array later. FWIW, FreeBSD 4.1-STABLE Abit BP6 dual 466 Celerons (not using the HPT controller) Promise Ultra66 Quantum KA 13.6 gig and IBM Deskstar 30 gig drives --clark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 14:28:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id 9464337B440 for ; Fri, 8 Sep 2000 14:28:42 -0700 (PDT) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13XVhE-0002gj-00; Fri, 08 Sep 2000 22:28:28 +0100 Date: Fri, 8 Sep 2000 22:28:28 +0100 To: John Toon Cc: freebsd-hackers@freebsd.org Subject: Re: Shared Memory Issues Message-ID: <20000908222828.A32477@firedrake.org> References: <39B4BD1D.676139D4@btinternet.com> <20000905230110.A9425@host.cer.ntnu.edu.tw> <39B58ABD.1B215190@btinternet.com> <39B7C08B.5841BA62@linkline.com> <39B8EFFA.785E6D46@btinternet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39B8EFFA.785E6D46@btinternet.com>; from j.a.toon@btinternet.com on Fri, Sep 08, 2000 at 02:56:10PM +0100 From: void Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 08, 2000 at 02:56:10PM +0100, John Toon wrote: > > However, it seems strange that you're getting non-attached memory > segments. Surely it is the job of the kernel to clean up after processes > (if they're badly programmed and don't do it themselves)? Perhaps one > program is leaking? SysV shared memory segments are defined to stick around until some appropriately-privileged user process deletes them. I was thinking recently that it might be nice to extend that API so a process creating such a segment could ask the kernel to reference-count it and delete it if the refcount goes to zero, but any app that wants that behavior can just use mmap() anyway, which has the advantage of being portable. -- 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 Sep 8 15:14:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id 1335B37B443 for ; Fri, 8 Sep 2000 15:14:11 -0700 (PDT) Received: (qmail 7374 invoked by uid 66); 8 Sep 2000 22:23:07 -0000 Received: from en by slarti with UUCP; Fri Sep 8 22:23:07 2000 -0000 Received: by en1.engelschall.com (Sendmail 8.11.0+) for freebsd-hackers@freebsd.org id e88MDoc05007; Sat, 9 Sep 2000 00:13:50 +0200 (CEST) Date: Sat, 9 Sep 2000 00:13:49 +0200 From: "Ralf S. Engelschall" To: freebsd-hackers@freebsd.org Subject: Re: makecontext & friends ? Message-ID: <20000909001349.A4997@engelschall.com> Reply-To: rse@engelschall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Engelschall, Germany. X-Web-Homepage: http://www.engelschall.com/ X-PGP-Public-Key: https://www.engelschall.com/ho/rse/pgprse.asc X-PGP-Fingerprint: 00 C9 21 8E D1 AB 70 37 DD 67 A2 3A 0A 6F 8D A5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you wrote: > On Fri, 8 Sep 2000, Ralf S. Engelschall wrote: >> >> In article <20000908151942.A15852@lamu.hermes.si> you wrote: >> >> > are there any plans to implement makecontext() & friends >> > functions in FreeBSD? >> >> I don't know of any plans myself, but I would appreciate that we support this >> standardized ucontext(3) API in FreeBSD. The API is actually not the problem, >> the question is on what should this API internally be based? On an own >> mechanism or on an existing mechanism (jmp_buf, etc)? > > My implementation of it was based on a trapframe, so it would be > easy to pass a ucontext_t to the kernel and have it switch to > the context at appropriate times (scheduler activations). A > trapframe is the same as a sigcontext_t (ucontext_t) for i386 > but not for the alpha. I think I got around this by adding a > type field to the ucontext (or mcontext) to indicate which > format it was for alpha. Sounds good -- where can I find a copy of your implementation? I would like to look at it in more detail. Ralf S. Engelschall rse@engelschall.com www.engelschall.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 19: 3:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id C639037B424 for ; Fri, 8 Sep 2000 19:03:47 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8923Jx06181; Sat, 9 Sep 2000 11:33:19 +0930 (CST) (envelope-from grog) Date: Sat, 9 Sep 2000 11:33:19 +0930 From: Greg Lehey To: Esko Petteri Matinsola , Clark Shishido Cc: hackers@FreeBSD.ORG Subject: Re: Vinum RAID-5 performance problem Message-ID: <20000909113319.E5876@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from esko@kapi.net on Fri, Sep 08, 2000 at 10:24:51PM +0300 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 8 September 2000 at 22:24:51 +0300, Esko Petteri Matinsola wrote: > Thank you for your last reply about the Promise 100 controller, I got it > working with that patch. > > But now, I have Asus P2L97 mobo with 64MB RAM, 266MHz P2 and 4 Maxtor > 54098H8's, two per channel. OS is FreeBSD 4.1-STABLE. > > When I use vinum with the following config: > > drive drive0 device /dev/ad0e > drive drive1 device /dev/ad1e > drive drive2 device /dev/ad2e > drive drive3 device /dev/ad3e > > > volume raid0 > plex org striped 256k > sd length 512m drive drive0 > sd length 512m drive drive1 > > > so I have RAID-0 with the master and slave drive from controller one. > bonnie -s 512 on that gives me: > > > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > 512 13287 97.3 20237 41.0 8023 25.6 8572 97.8 21442 29.4 128.1 2.2 Please don't use bonnie. It's not measuring what you think it is. > not bad, even when two drives on the same controller. Next, I tried vinum > with the following config: > > drive drive0 device /dev/ad0e > drive drive1 device /dev/ad1e > drive drive2 device /dev/ad2e > drive drive3 device /dev/ad3e > > volume raid0 > plex org striped 256k > sd length 512m drive drive0 > sd length 512m drive drive2 > > so I have RAID-0 with the masters from both controllers. bonnie -s 512 > gives me: > > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > 512 13263 97.4 21340 43.7 8169 26.1 8572 98.0 25858 36.6 213.4 3.9 > > only a little better, except the seeks. Of course. The seeks are the only thing which relate to real-life performance. Look at the sequential character output, for example. It's showing clearly that the bottleneck is the CPU, not the storage subsystem. In block writes, the real-world performance of the first configuration is in fact worse than what you see there, but since bonnie is only writing one file at a time, you don't run into any contention problems. You should be using rawio, which will show you what the storage system is doing. > Now next to my problem. When I use vinum with the following config: > > drive drive0 device /dev/ad0e > drive drive1 device /dev/ad1e > drive drive2 device /dev/ad2e > drive drive3 device /dev/ad3e > > volume raid5 > plex org raid5 256k > sd length 512m drive drive0 > sd length 512m drive drive1 > sd length 512m drive drive2 > sd length 512m drive drive3 > > > so I have RAID-5 with all the drives from both controllers. bonnie -s 512 > gives me: > > > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > 512 2368 17.7 2358 4.8 2016 6.6 8218 94.4 20068 29.1 232.5 4.3 > > read performance and seeks seems OK, but block writes only about 1/9th ! > As I read from www.vinumvm.org I should get something like 5MBps block > writes. I don't know how you'd find anything at vinumvm.org which tells you what to expect from bonnie. > Have I misunderstood something, configured someting improperly, it's > because of only two IDE-controllers or why I get so lousy write > performance ? Well, firstly I don't know what your write performance is. It really depends on what you're trying to do. But yes, having only two controllers will halve your RAID-5 write performance. Note also that with a 256 kB stripe, you'll run into drive contention problems because all your superblocks will be on the same subdisk. Take a size like 273 kB, for example. > I could live with 5MBps, if I only could get that ! :) I'd expect the performance to increase by about 50% or 60% if you use four controllers. On Friday, 8 September 2000 at 12:55:51 -0700, Clark Shishido wrote: > At 22:24 +0300 2000.09.08, Esko Petteri Matinsola wrote: >> >> read performance and seeks seems OK, but block writes only about 1/9th ! >> As I read from www.vinumvm.org I should get something like 5MBps block >> writes. >> >> Have I misunderstood something, configured someting improperly, it's >> because of only two IDE-controllers or why I get so lousy write >> performance ? > > Your configuration looks fine. Well, using master and slave together isn't fine in my book. > I just recently tried a similar setup using Promise Ultra66 controllers > with some Quantum and IBM drives (tried both). I got lousy performance > doing sustained writes to a RAID5 volume, using 4 UDMA66 drives each a > master on a controller. just doing a cat /dev/zero > blah > > I just decided to stick with striping and make regular backups. > I may try vinum with RAID5 on a SCSI array later. > > FWIW, > FreeBSD 4.1-STABLE > Abit BP6 dual 466 Celerons > (not using the HPT controller) > Promise Ultra66 > Quantum KA 13.6 gig and IBM Deskstar 30 gig drives Again, it would be nice to see some real figures. Why aren't you using the onboard controller on the BP6? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 8 19:46:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.tor3.targetnet.com (smtp.tor3.targetnet.com [207.176.132.71]) by hub.freebsd.org (Postfix) with ESMTP id 72ADA37B42C for ; Fri, 8 Sep 2000 19:46:44 -0700 (PDT) Received: from equinox.targetnet.com ([216.13.75.130] helo=pluto) by smtp.tor3.targetnet.com with smtp (Exim 3.16 #1) id 13Xade-0008Fv-00; Fri, 08 Sep 2000 22:45:06 -0400 From: "Brandon Gale" To: "Greg Lehey" , "Esko Petteri Matinsola" , "Clark Shishido" Cc: Subject: RE: Vinum RAID-5 performance problem Date: Fri, 8 Sep 2000 22:45:48 -0400 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0020_01C019E6.87FC5F50" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <20000909113319.E5876@wantadilla.lemis.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0020_01C019E6.87FC5F50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Note* rawio will overwrite your data, so be careful! Here are tests that I ran using a 4 disk array (10k RPM SCSI disks). I have about 20 datafiles comprising 8 different stripe sizes for 3 different raid configurations (0,5,1+0) if anyone is interested (Greg?). Thanks, brandon > -----Original Message----- > From: owner-freebsd-hackers@FreeBSD.ORG > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Greg Lehey > Sent: Friday, September 08, 2000 10:03 PM > To: Esko Petteri Matinsola; Clark Shishido > Cc: hackers@FreeBSD.ORG > Subject: Re: Vinum RAID-5 performance problem > > > On Friday, 8 September 2000 at 22:24:51 +0300, Esko Petteri > Matinsola wrote: > > Thank you for your last reply about the Promise 100 controller, I got it > > working with that patch. > > > > But now, I have Asus P2L97 mobo with 64MB RAM, 266MHz P2 and 4 Maxtor > > 54098H8's, two per channel. OS is FreeBSD 4.1-STABLE. > > > > When I use vinum with the following config: > > > > drive drive0 device /dev/ad0e > > drive drive1 device /dev/ad1e > > drive drive2 device /dev/ad2e > > drive drive3 device /dev/ad3e > > > > > > volume raid0 > > plex org striped 256k > > sd length 512m drive drive0 > > sd length 512m drive drive1 > > > > > > so I have RAID-0 with the master and slave drive from controller one. > > bonnie -s 512 on that gives me: > > > > > > -------Sequential Output-------- ---Sequential Input-- --Random-- > > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > > MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > > 512 13287 97.3 20237 41.0 8023 25.6 8572 97.8 21442 29.4 128.1 2.2 > > Please don't use bonnie. It's not measuring what you think it is. > > > not bad, even when two drives on the same controller. Next, I > tried vinum > > with the following config: > > > > drive drive0 device /dev/ad0e > > drive drive1 device /dev/ad1e > > drive drive2 device /dev/ad2e > > drive drive3 device /dev/ad3e > > > > volume raid0 > > plex org striped 256k > > sd length 512m drive drive0 > > sd length 512m drive drive2 > > > > so I have RAID-0 with the masters from both controllers. bonnie -s 512 > > gives me: > > > > -------Sequential Output-------- ---Sequential Input-- --Random-- > > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > > MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > > 512 13263 97.4 21340 43.7 8169 26.1 8572 98.0 25858 36.6 213.4 3.9 > > > > only a little better, except the seeks. > > Of course. The seeks are the only thing which relate to real-life > performance. Look at the sequential character output, for example. > It's showing clearly that the bottleneck is the CPU, not the storage > subsystem. In block writes, the real-world performance of the first > configuration is in fact worse than what you see there, but since > bonnie is only writing one file at a time, you don't run into any > contention problems. You should be using rawio, which will show you > what the storage system is doing. > > > Now next to my problem. When I use vinum with the following config: > > > > drive drive0 device /dev/ad0e > > drive drive1 device /dev/ad1e > > drive drive2 device /dev/ad2e > > drive drive3 device /dev/ad3e > > > > volume raid5 > > plex org raid5 256k > > sd length 512m drive drive0 > > sd length 512m drive drive1 > > sd length 512m drive drive2 > > sd length 512m drive drive3 > > > > > > so I have RAID-5 with all the drives from both controllers. > bonnie -s 512 > > gives me: > > > > > > -------Sequential Output-------- ---Sequential Input-- --Random-- > > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > > MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > > 512 2368 17.7 2358 4.8 2016 6.6 8218 94.4 20068 29.1 232.5 4.3 > > > > read performance and seeks seems OK, but block writes only about 1/9th ! > > As I read from www.vinumvm.org I should get something like 5MBps block > > writes. > > I don't know how you'd find anything at vinumvm.org which tells you > what to expect from bonnie. > > > Have I misunderstood something, configured someting improperly, it's > > because of only two IDE-controllers or why I get so lousy write > > performance ? > > Well, firstly I don't know what your write performance is. It really > depends on what you're trying to do. But yes, having only two > controllers will halve your RAID-5 write performance. Note also that > with a 256 kB stripe, you'll run into drive contention problems > because all your superblocks will be on the same subdisk. Take a size > like 273 kB, for example. > > > I could live with 5MBps, if I only could get that ! :) > > I'd expect the performance to increase by about 50% or 60% if you use > four controllers. > > On Friday, 8 September 2000 at 12:55:51 -0700, Clark Shishido wrote: > > At 22:24 +0300 2000.09.08, Esko Petteri Matinsola wrote: > >> > >> read performance and seeks seems OK, but block writes only > about 1/9th ! > >> As I read from www.vinumvm.org I should get something like 5MBps block > >> writes. > >> > >> Have I misunderstood something, configured someting improperly, it's > >> because of only two IDE-controllers or why I get so lousy write > >> performance ? > > > > Your configuration looks fine. > > Well, using master and slave together isn't fine in my book. > > > I just recently tried a similar setup using Promise Ultra66 controllers > > with some Quantum and IBM drives (tried both). I got lousy performance > > doing sustained writes to a RAID5 volume, using 4 UDMA66 drives each a > > master on a controller. just doing a cat /dev/zero > blah > > > > I just decided to stick with striping and make regular backups. > > I may try vinum with RAID5 on a SCSI array later. > > > > FWIW, > > FreeBSD 4.1-STABLE > > Abit BP6 dual 466 Celerons > > (not using the HPT controller) > > Promise Ultra66 > > Quantum KA 13.6 gig and IBM Deskstar 30 gig drives > > Again, it would be nice to see some real figures. Why aren't you > using the onboard controller on the BP6? > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > ------=_NextPart_000_0020_01C019E6.87FC5F50 Content-Type: application/octet-stream; name="results.raid5_256k" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="results.raid5_256k" drive ds1 device /dev/da2s1e drive ds2 device /dev/da3s1e drive ds3 device /dev/da4s1e drive ds4 device /dev/da5s1e drive ds5 device /dev/da6s1e volume datasilo plex org raid5 256k sd drive ds1 length 0 sd drive ds2 length 0 sd drive ds3 length 0 sd drive ds4 length 0 sd drive ds5 length 0 thread count: 8 iteration: 1 /usr/local/bin/rawio -a -p 8 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 6411.6 398 10504.6 641 2040.8 127 2035.5 124=09 iteration: 2 /usr/local/bin/rawio -a -p 8 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 6411.8 397 12057.8 736 2066.5 127 2013.0 123=09 iteration: 3 /usr/local/bin/rawio -a -p 8 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 6318.8 395 9115.1 556 2058.4 128 1981.7 121=09 iteration: 4 /usr/local/bin/rawio -a -p 8 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 6346.2 395 9430.7 576 2065.0 128 1982.1 121=09 iteration: 5 /usr/local/bin/rawio -a -p 8 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 6384.1 398 9752.9 595 2052.7 128 2019.0 123=09 thread count: 16 iteration: 1 /usr/local/bin/rawio -a -p 16 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 8465.7 530 11011.5 672 2655.3 165 2278.7 139=09 iteration: 2 /usr/local/bin/rawio -a -p 16 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 8515.9 526 11641.4 711 2659.1 165 2326.8 142=09 iteration: 3 /usr/local/bin/rawio -a -p 16 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 8512.9 526 11324.0 691 2649.8 164 2342.4 143=09 iteration: 4 /usr/local/bin/rawio -a -p 16 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 8508.5 529 12994.2 793 2633.5 165 2251.1 137=09 iteration: 5 /usr/local/bin/rawio -a -p 16 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 8491.2 524 11597.3 708 2676.7 165 2217.6 135=09 thread count: 32 iteration: 1 /usr/local/bin/rawio -a -p 32 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 10834.8 673 12423.7 758 3192.5 197 2631.3 161=09 iteration: 2 /usr/local/bin/rawio -a -p 32 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 10814.6 672 11783.7 719 3204.2 198 2683.2 164=09 iteration: 3 /usr/local/bin/rawio -a -p 32 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 10662.3 661 11380.3 695 3213.3 199 2700.3 165=09 iteration: 4 /usr/local/bin/rawio -a -p 32 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 10911.5 672 13063.7 797 3222.6 198 2764.2 169=09 iteration: 5 /usr/local/bin/rawio -a -p 32 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 10774.9 669 12069.5 737 3193.8 198 2695.5 165=09 thread count: 64 iteration: 1 /usr/local/bin/rawio -a -p 64 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 10701.1 664 12647.8 772 3520.2 218 3119.9 190=09 iteration: 2 /usr/local/bin/rawio -a -p 64 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 12823.8 804 13050.4 797 3553.7 222 2932.2 179=09 iteration: 3 /usr/local/bin/rawio -a -p 64 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 13159.5 808 13024.3 795 3544.7 219 3030.8 185=09 iteration: 4 /usr/local/bin/rawio -a -p 64 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 12826.2 806 13288.9 811 3559.8 219 2961.7 181=09 iteration: 5 /usr/local/bin/rawio -a -p 64 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 13208.1 810 13099.8 800 3537.0 218 2984.4 182=09 thread count: 128 iteration: 1 /usr/local/bin/rawio -a -p 128 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 12603.9 782 13729.4 838 3764.5 232 3309.8 202=09 iteration: 2 /usr/local/bin/rawio -a -p 128 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 14885.3 922 13161.7 803 3755.7 233 3093.7 189=09 iteration: 3 /usr/local/bin/rawio -a -p 128 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 15113.8 930 13645.2 833 3769.7 234 3132.0 191=09 iteration: 4 /usr/local/bin/rawio -a -p 128 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 15020.5 931 13957.9 852 3734.1 230 3245.9 198=09 iteration: 5 /usr/local/bin/rawio -a -p 128 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.raid5_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 15108.7 932 13625.6 832 3725.9 231 3271.0 200=09 ------=_NextPart_000_0020_01C019E6.87FC5F50 Content-Type: application/octet-stream; name="results.striped_256k" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="results.striped_256k" drive ds1 device /dev/da2s1e drive ds2 device /dev/da3s1e drive ds3 device /dev/da4s1e drive ds4 device /dev/da5s1e drive ds5 device /dev/da6s1e volume datasilo plex org striped 256k sd drive ds1 length 0 sd drive ds2 length 0 sd drive ds3 length 0 sd drive ds4 length 0 sd drive ds5 length 0 thread count: 8 iteration: 1 /usr/local/bin/rawio -a -p 8 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 6390.3 398 12525.9 765 11486.2 709 17525.1 1070=09 iteration: 2 /usr/local/bin/rawio -a -p 8 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 6406.0 397 13403.7 818 11352.0 704 19254.4 1175=09 iteration: 3 /usr/local/bin/rawio -a -p 8 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 6416.1 396 12477.0 762 11317.9 701 19957.5 1218=09 iteration: 4 /usr/local/bin/rawio -a -p 8 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 6336.2 395 13510.4 825 11398.0 712 16984.6 1037=09 iteration: 5 /usr/local/bin/rawio -a -p 8 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 6395.0 397 14695.2 897 11242.2 695 17789.3 1086=09 thread count: 16 iteration: 1 /usr/local/bin/rawio -a -p 16 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 8583.2 528 14691.3 897 12095.3 751 15936.6 973=09 iteration: 2 /usr/local/bin/rawio -a -p 16 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 8483.9 528 17405.1 1062 12155.7 751 17489.5 1067=09 iteration: 3 /usr/local/bin/rawio -a -p 16 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 8464.9 529 13179.0 804 12323.6 758 15778.4 963=09 iteration: 4 /usr/local/bin/rawio -a -p 16 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 8512.8 529 13463.2 822 11975.2 749 16453.0 1004=09 iteration: 5 /usr/local/bin/rawio -a -p 16 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 8538.6 528 11751.9 717 12190.5 753 16207.7 989=09 thread count: 32 iteration: 1 /usr/local/bin/rawio -a -p 32 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 10840.5 675 13837.8 845 12867.1 794 13874.6 847=09 iteration: 2 /usr/local/bin/rawio -a -p 32 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 10777.9 674 13235.4 808 12839.7 795 14323.2 874=09 iteration: 3 /usr/local/bin/rawio -a -p 32 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 10833.1 670 12338.4 753 12664.9 784 14247.6 870=09 iteration: 4 /usr/local/bin/rawio -a -p 32 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 10864.1 672 14107.9 861 12731.8 796 13082.1 798=09 iteration: 5 /usr/local/bin/rawio -a -p 32 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 10763.6 669 12767.5 779 12825.2 789 13962.4 852=09 thread count: 64 iteration: 1 /usr/local/bin/rawio -a -p 64 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 13065.9 811 14175.3 865 13225.3 819 13499.8 824=09 iteration: 2 /usr/local/bin/rawio -a -p 64 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 13008.7 808 13541.8 827 13124.0 815 13897.3 848=09 iteration: 3 /usr/local/bin/rawio -a -p 64 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 13027.4 806 13905.5 849 13228.0 819 13059.2 797=09 iteration: 4 /usr/local/bin/rawio -a -p 64 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 13009.2 806 13178.1 804 13375.2 825 12659.1 773=09 iteration: 5 /usr/local/bin/rawio -a -p 64 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 13044.8 806 14340.9 875 13194.8 822 13023.6 795=09 thread count: 128 iteration: 1 /usr/local/bin/rawio -a -p 128 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 14997.5 933 13956.7 852 13929.4 861 13398.0 818=09 iteration: 2 /usr/local/bin/rawio -a -p 128 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 15107.8 934 13503.2 824 13307.1 823 13348.3 815=09 iteration: 3 /usr/local/bin/rawio -a -p 128 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 15065.6 928 13760.7 840 13671.6 845 13036.2 796=09 iteration: 4 /usr/local/bin/rawio -a -p 128 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 14941.1 934 13605.9 830 13664.8 846 13226.9 807=09 iteration: 5 /usr/local/bin/rawio -a -p 128 /dev/vinum/datasilo 2>&1 >> = /root/jfitz/vinum_test/results/results.striped_256k Random read Sequential read Random write Sequential write ID K/sec /sec K/sec /sec K/sec /sec K/sec /sec datasilo 15056.1 938 14277.5 871 13713.0 852 13347.9 815=09 ------=_NextPart_000_0020_01C019E6.87FC5F50 Content-Type: application/octet-stream; name="results.singledrive" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="results.singledrive" cheetah_t160_r8_i1 2236.4 584 1918.4 468 1805.0 472 1529.8 = 373=09 cheetah_t160_r8_i2 2447.2 636 1685.0 411 1831.3 475 1601.6 = 391=09 cheetah_t160_r8_i3 2434.9 627 1959.9 478 1855.5 481 1144.1 = 279=09 cheetah_t160_r16_i1 4739.1 596 3524.7 430 3552.6 447 = 2671.2 326=09 cheetah_t160_r16_i2 4681.8 592 3129.7 382 3563.9 450 = 3013.2 368=09 cheetah_t160_r16_i3 4688.7 591 3324.1 406 3639.9 461 = 2302.7 281=09 cheetah_t160_r32_i1 8240.8 510 6441.9 393 6654.2 414 = 3880.5 237=09 cheetah_t160_r32_i2 8137.0 502 5559.4 339 6823.8 423 = 4266.7 260=09 cheetah_t160_r32_i3 8084.8 498 5019.9 306 6652.8 413 = 4370.4 267=09 cheetah_t160_r64_i1 12267.7 379 10174.2 310 7545.1 234 = 6981.5 213=09 cheetah_t160_r64_i2 12636.1 389 9837.3 300 7918.0 243 = 6534.6 199=09 cheetah_t160_r64_i3 12677.9 391 9039.1 276 7172.4 223 = 7290.3 222=09 cheetah_t160_r128_i1 13950.4 215 10764.7 164 8284.2 127 = 9786.3 149=09 cheetah_t160_r128_i2 14440.9 221 20792.2 317 8255.5 126 = 10198.0 156=09 cheetah_t160_r128_i3 14298.3 219 20128.1 307 8199.2 126 = 9537.2 146=09 cheetah_t160_r256_i1 6037.6 85 19785.9 151 4352.6 56 = 9517.7 73=09 cheetah_t160_r256_i2 5169.6 68 19207.9 147 3794.4 54 = 9542.0 73=09 cheetah_t160_r256_i3 6391.0 88 19794.5 151 4035.2 56 = 9639.4 74=09 ------=_NextPart_000_0020_01C019E6.87FC5F50-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 9 5:52:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from guardian.hermes.si (guardian.hermes.si [193.77.5.150]) by hub.freebsd.org (Postfix) with ESMTP id 664DE37B422 for ; Sat, 9 Sep 2000 05:52:08 -0700 (PDT) Received: from hermes.si (primus.hermes.si [193.77.5.98]) by guardian.hermes.si (8.9.3/8.9.3) with ESMTP id OAA17744 for ; Sat, 9 Sep 2000 14:52:04 +0200 (METDST) Received: (from uucp@localhost) by hermes.si (8.9.3/8.9.3) id OAA10250 for ; Sat, 9 Sep 2000 14:52:02 +0200 Received: from lamu.hermes.si(10.17.1.230) by primus.hermes.si via smap (V2.1) id xma010002; Sat, 9 Sep 00 14:51:28 +0200 Received: (from mitja@localhost) by lamu.hermes.si (8.9.3/8.9.3) id OAA25888 for freebsd-hackers@freebsd.org; Sat, 9 Sep 2000 14:51:18 +0200 (CEST) Date: Sat, 9 Sep 2000 14:51:18 +0200 From: Mitja Horvat To: freebsd-hackers@freebsd.org Subject: Re: makecontext & friends ? Message-ID: <20000909145118.A25823@lamu.hermes.si> References: <20000908161542.A87619@engelschall.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000908161542.A87619@engelschall.com>; from rse@engelschall.com on Fri, Sep 08, 2000 at 04:15:42PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > Sure, it can. See my GNU Portable Threads under > http://www.gnu.org/software/pth/. We have a port under devel/pth, > too. It bases its user-land threads on ucontext(3) if available or on > setjmp(3)'s jmp_buf, etc. All without any assembler things. For details > read my USENIX paper under http://www.gnu.org/software/pth/rse-pmt.ps. > I read your paper and it describes the very same technique I was planning to implement, but the trick with sigaltstack() seems very ugly to me. That's why I poked around Solaris' man pages and found ucontext(3) functions. Anyway since you already have done all the work, it's pointless for me to reinvent the wheel. Besides this, GNU Pth is certainly more tested than my solution would ever be. Well, next time I should check for GNU stuff before I plan doing something. > If you need maximum portability, then GNU Pth certainly is an option for > you. I will definitely use it. Thank you for this great software... ! Regards, Mitja To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 9 6: 4:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from guardian.hermes.si (guardian.hermes.si [193.77.5.150]) by hub.freebsd.org (Postfix) with ESMTP id E615C37B422 for ; Sat, 9 Sep 2000 06:04:37 -0700 (PDT) Received: from hermes.si (primus.hermes.si [193.77.5.98]) by guardian.hermes.si (8.9.3/8.9.3) with ESMTP id PAA17921 for ; Sat, 9 Sep 2000 15:04:34 +0200 (METDST) Received: (from uucp@localhost) by hermes.si (8.9.3/8.9.3) id PAA28752 for ; Sat, 9 Sep 2000 15:04:32 +0200 Received: from lamu.hermes.si(10.17.1.230) by primus.hermes.si via smap (V2.1) id xma025351; Sat, 9 Sep 00 15:03:14 +0200 Received: (from mitja@localhost) by lamu.hermes.si (8.9.3/8.9.3) id PAA26046 for freebsd-hackers@freebsd.org; Sat, 9 Sep 2000 15:03:05 +0200 (CEST) Date: Sat, 9 Sep 2000 15:03:05 +0200 From: Mitja Horvat To: freebsd-hackers@freebsd.org Subject: Re: makecontext() & friends ? Message-ID: <20000909150305.A26019@lamu.hermes.si> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Dan, > I have implemented {make,get,set,swap}context as library routines > for FreeBSD. They're gathering dust somewhere and need a bit of > polishing. If you give me some time I can dust them off and > send them to you. I would really appreciate if I could get my hands on this code. Could you please specify a link, or if you prefer you can send the tarball as an attachment to mitja@hermes.si. Thank you very much for your help... Mitja To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 9 11:32:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id 162F237B422 for ; Sat, 9 Sep 2000 11:32:45 -0700 (PDT) Received: (qmail 15475 invoked by uid 66); 9 Sep 2000 18:41:38 -0000 Received: from en by slarti with UUCP; Sat Sep 9 18:41:38 2000 -0000 Received: by en1.engelschall.com (Sendmail 8.11.0+) for freebsd-hackers@freebsd.org id e89IW3N43484; Sat, 9 Sep 2000 20:32:03 +0200 (CEST) Date: Sat, 9 Sep 2000 20:31:54 +0200 From: "Ralf S. Engelschall" To: freebsd-hackers@freebsd.org Subject: Re: makecontext & friends ? Message-ID: <20000909203154.A42704@engelschall.com> Reply-To: rse@engelschall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Engelschall, Germany. X-Web-Homepage: http://www.engelschall.com/ X-PGP-Public-Key: https://www.engelschall.com/ho/rse/pgprse.asc X-PGP-Fingerprint: 00 C9 21 8E D1 AB 70 37 DD 67 A2 3A 0A 6F 8D A5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000909145118.A25823@lamu.hermes.si> you wrote: >> Sure, it can. See my GNU Portable Threads under >> http://www.gnu.org/software/pth/. We have a port under devel/pth, >> too. It bases its user-land threads on ucontext(3) if available or on >> setjmp(3)'s jmp_buf, etc. All without any assembler things. For details >> read my USENIX paper under http://www.gnu.org/software/pth/rse-pmt.ps. >> > I read your paper and it describes the very same technique I was planning > to implement, but the trick with sigaltstack() seems very ugly to me. > [...] Keep in mind that GNU Pth's Autoconf mechanism automatically selects ucontext(3) if available and only uses the sigaltstack(2) trick if no other possibilities exist. As the paper describes in detail, the "ugly trick" is just a _fallback_ approach. That's one reason why I want makecontext(3) on FreeBSD - that we no longer have to use the (15x slower) trick on FreeBSD and instead can directly use a (faster) user-land context mechanism for thread creation and dispatching (although for dispatching the sigjmp_buf approach is usually slightly faster than ucontext because ucontext is a superset of sigjmp_buf). Yours, Ralf S. Engelschall rse@engelschall.com www.engelschall.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 9 12:41:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 4E2EC37B42C for ; Sat, 9 Sep 2000 12:41:21 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13XdNq-0000IT-00; Fri, 08 Sep 2000 23:40:58 -0600 Message-ID: <39B9CD6A.7D290AB1@softweyr.com> Date: Fri, 08 Sep 2000 23:40:58 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Len Conrad Cc: freebsd-hackers@freebsd.org Subject: Re: Token Ring ?? References: <4.3.2.7.2.20000906145953.00d07900@mail.Go2France.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Len Conrad wrote: > > We deal lot with AS/400 customers with TRN systems. I see 4.1 release > still doesn't have a TRN card supported. > > Anybody got any ideas how to support TRN in FreeBSD? With an ethernet<->token ring switch? -- "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 Sep 9 12:43: 8 2000 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 15DA937B422; Sat, 9 Sep 2000 12:43:01 -0700 (PDT) Received: from db.wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with ESMTP id MAA12100; Sat, 9 Sep 2000 12:30:55 -0700 (PDT) (envelope-from dbutter@db.wireless.net) Message-ID: <39BA92BF.D0632472@db.wireless.net> Date: Sat, 09 Sep 2000 12:42:55 -0700 From: Devin Butterfield X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Cc: freebsd-stable@FreeBSD.ORG, buaas@wireless.net Subject: Panics from trying to open dev after kldunload Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I'm working on a device driver for FreeBSD for a VoIP telephony card and I stumbled upon a serious problem. If I "kldunload" my driver and subsequently try to open the device, the kernel panics. I found that the vn device suffers from this same bug. For example: Before kldload vn: [root@dbm]# echo -n>/dev/vn0 su: /dev/vn0: Device not configured [root@dbm]# This of course is the expected behavior. We then can do this... [root@dbm]# kldload vn [root@dbm]# echo -n>/dev/vn0 [root@dbm]# Again, expected behavior... But if we then do this... [root@dbm]# kldunload vn [root@dbm]# echo -n>/dev/vn0 we get an instant panic. It seems that there is already a pr open for this (kern/18270) which includes a patch to correctly cleanup after "kldunload". Is this the correct fix for this...why hasn't this been committed?? -- 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 Sep 9 12:43:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 5DD7037B443 for ; Sat, 9 Sep 2000 12:43:11 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13Xe8R-0000Jx-00; Sat, 09 Sep 2000 00:29:07 -0600 Message-ID: <39B9D8B3.4B6F1229@softweyr.com> Date: Sat, 09 Sep 2000 00:29:07 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jeroen C. van Gelderen" Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: FYI: RSA Donated to the public domain References: <200009061312.HAA68224@harmony.village.org> <200009061317.HAA68280@harmony.village.org> <39B658C0.CD9A2E37@vangelderen.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jeroen C. van Gelderen" wrote: > > Warner Losh wrote: > > > > In message <200009061312.HAA68224@harmony.village.org> Warner Losh writes: > > : RSA Security Releases RSA Encryption Algorithm into Public Domain > > > > Note that other information at the site says that RSAREF isn't > > released into the public domain. Its use is still governed by > > copyright law, so we'll have to use the international version of > > RSAREF if we want to get RSA into -current. > > RSAREF was only neccessary whilst the patent was > enforced. Now that RSA is released[1] we can use > the OpenSSL RSA implementation which is better. > > [1] The press release talk about RSADSI "waiving its > rights to enforce the RSA patent for any development > activities" > > This is very cunning as the patent never actually > covered development. Instead it covers usage and > sales of products incorporating RSA, both of which > are not explicitly allowed for in the press release. > Better be careful, better get written approval! No, it explicity said they were placing the RSA algorithm "in the public domain." That has some very specific legal meanings, which boil down to "you can do whatever you want with it, but you can't sue us over it because it's not ours anymore, it's everyones." -- "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 Sep 9 12:43:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 173D137B422 for ; Sat, 9 Sep 2000 12:43:13 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13XeBe-0000K6-00; Sat, 09 Sep 2000 00:32:26 -0600 Message-ID: <39B9D97A.B640E572@softweyr.com> Date: Sat, 09 Sep 2000 00:32:26 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Token Ring ?? References: <4.3.2.7.2.20000906145953.00d07900@mail.Go2France.com> <4.3.2.7.2.20000906145953.00d07900@mail.Go2France.com> <4.3.2.7.2.20000906170138.02870f00@mail.Go2France.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Len Conrad wrote: > > >If I am not mistaking Token Ring _is_ supported in FreeBSD. > > Stealthy support it is, then, as I cannot find it here: > > http://www.freebsd.org/releases/4.1R/notes.html UTSL: src/sys/dev/isa/if_tr{,ibm,tcm}_isa.c -- "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 Sep 9 13:33:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 538) id EFC3337B423; Sat, 9 Sep 2000 13:33:31 -0700 (PDT) To: hackers@FreeBSD.ORG From: Majordomo@FreeBSD.ORG Subject: Majordomo results: unsubscribe freebsd-hackers user reecetl Reply-To: Majordomo@FreeBSD.ORG Message-Id: <20000909203331.EFC3337B423@hub.freebsd.org> Date: Sat, 9 Sep 2000 13:33:31 -0700 (PDT) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -- >>>> unsubscribe freebsd-hackers user reecetl@marforlant.usmc.mil **** The address you supplied, user reecetl@marforlant.usmc.mil **** does not seem to be a legal Internet address. You may have supplied **** your full name instead of your address, or you may have included your **** name along with your address in a manner that does not comply with **** Internet standards for addresses. **** It is also possible that you are using a mailer that wraps long lines **** and the end of your request ended up on the following line. If the **** latter is true, try using backslashes to split long lines. (Split the **** line between words, then put a backslash at the end of all but the **** last line.) **** unsubscribe: invalid address 'user reecetl@marforlant.usmc.mil' >>>> >>>> >>>> freebsd-hackers-digest Saturday, September 9 2000 Volume 04 : Number 943 **** Command 'freebsd-hackers-digest' not recognized. >>>> >>>> >>>> >>>> In this issue: **** Command 'in' not recognized. >>>> Vinum RAID-5 performance problem **** Command 'vinum' not recognized. >>>> Re: How to stop problems from printf **** Command 're:' not recognized. >>>> Re: How to stop problems from printf **** Command 're:' not recognized. >>>> Re: md5 in boot loader **** Command 're:' not recognized. >>>> Re: Creating a list of newbus devices. **** Command 're:' not recognized. >>>> Re: Vinum RAID-5 performance problem **** Command 're:' not recognized. >>>> Re: Shared Memory Issues **** Command 're:' not recognized. >>>> Re: makecontext & friends ? **** Command 're:' not recognized. >>>> Re: Vinum RAID-5 performance problem **** Command 're:' not recognized. >>>> RE: Vinum RAID-5 performance problem **** Command 're:' not recognized. >>>> Re: makecontext & friends ? **** Command 're:' not recognized. >>>> Re: makecontext() & friends ? **** Command 're:' not recognized. >>>> Re: makecontext & friends ? **** Command 're:' not recognized. >>>> Re: Token Ring ?? **** Command 're:' not recognized. >>>> >>>> ---------------------------------------------------------------------- END OF COMMANDS **** Help for Majordomo@FreeBSD.ORG: This help message is being sent to you from the Majordomo mailing list management system at Majordomo@FreeBSD.ORG. This is version 1.94.4 of Majordomo. If you're familiar with mail servers, an advanced user's summary of Majordomo's commands appears at the end of this message. Majordomo is an automated system which allows users to subscribe and unsubscribe to mailing lists, and to retrieve files from list archives. You can interact with the Majordomo software by sending it commands in the body of mail messages addressed to "Majordomo@FreeBSD.ORG". Please do not put your commands on the subject line; Majordomo does not process commands in the subject line. You may put multiple Majordomo commands in the same mail message. Put each command on a line by itself. If you use a "signature block" at the end of your mail, Majordomo may mistakenly believe each line of your message is a command; you will then receive spurious error messages. To keep this from happening, either put a line starting with a hyphen ("-") before your signature, or put a line with just the word end on it in the same place. This will stop the Majordomo software from processing your signature as bad commands. Here are some of the things you can do using Majordomo: I. FINDING OUT WHICH LISTS ARE ON THIS SYSTEM To get a list of publicly-available mailing lists on this system, put the following line in the body of your mail message to Majordomo@FreeBSD.ORG: lists Each line will contain the name of a mailing list and a brief description of the list. To get more information about a particular list, use the "info" command, supplying the name of the list. For example, if the name of the list about which you wish information is "demo-list", you would put the line info demo-list in the body of the mail message. II. SUBSCRIBING TO A LIST Once you've determined that you wish to subscribe to one or more lists on this system, you can send commands to Majordomo to have it add you to the list, so you can begin receiving mailings. To receive list mail at the address from which you're sending your mail, simply say "subscribe" followed by the list's name: subscribe demo-list If for some reason you wish to have the mailings go to a different address (a friend's address, a specific other system on which you have an account, or an address which is more correct than the one that automatically appears in the "From:" header on the mail you send), you would add that address to the command. For instance, if you're sending a request from your work account, but wish to receive "demo-list" mail at your personal account (for which we will use "jqpublic@my-isp.com" as an example), you'd put the line subscribe demo-list jqpublic@my-isp.com in the mail message body. Based on configuration decisions made by the list owners, you may be added to the mailing list automatically. You may also receive notification that an authorization key is required for subscription. Another message will be sent to the address to be subscribed (which may or may not be the same as yours) containing the key, and directing the user to send a command found in that message back to Majordomo@FreeBSD.ORG. (This can be a bit of extra hassle, but it helps keep you from being swamped in extra email by someone who forged requests from your address.) You may also get a message that your subscription is being forwarded to the list owner for approval; some lists have waiting lists, or policies about who may subscribe. If your request is forwarded for approval, the list owner should contact you soon after your request. Upon subscribing, you should receive an introductory message, containing list policies and features. Save this message for future reference; it will also contain exact directions for unsubscribing. If you lose the intro mail and would like another copy of the policies, send this message to Majordomo@FreeBSD.ORG: intro demo-list (substituting, of course, the real name of your list for "demo-list"). III. UNSUBSCRIBING FROM MAILING LISTS Your original intro message contains the exact command which should be used to remove your address from the list. However, in most cases, you may simply send the command "unsubscribe" followed by the list name: unsubscribe demo-list (This command may fail if your provider has changed the way your address is shown in your mail.) To remove an address other than the one from which you're sending the request, give that address in the command: unsubscribe demo-list jqpublic@my-isp.com In either of these cases, you can tell Majordomo@FreeBSD.ORG to remove the address in question from all lists on this server by using "*" in place of the list name: unsubscribe * unsubscribe * jqpublic@my-isp.com IV. FINDING THE LISTS TO WHICH AN ADDRESS IS SUBSCRIBED To find the lists to which your address is subscribed, send this command in the body of a mail message to Majordomo@FreeBSD.ORG: which You can look for other addresses, or parts of an address, by specifying the text for which Majordomo should search. For instance, to find which users at my-isp.com are subscribed to which lists, you might send the command which my-isp.com Note that many list owners completely or fully disable the "which" command, considering it a privacy violation. V. FINDING OUT WHO'S SUBSCRIBED TO A LIST To get a list of the addresses on a particular list, you may use the "who" command, followed by the name of the list: who demo-list Note that many list owners allow only a list's subscribers to use the "who" command, or disable it completely, believing it to be a privacy violation. VI. RETRIEVING FILES FROM A LIST'S ARCHIVES Many list owners keep archives of files associated with a list. These may include: - back issues of the list - help files, user profiles, and other documents associated with the list - daily, monthly, or yearly archives for the list To find out if a list has any files associated with it, use the "index" command: index demo-list If you see files in which you're interested, you may retrieve them by using the "get" command and specifying the list name and archive filename. For instance, to retrieve the files called "profile.form" (presumably a form to fill out with your profile) and "demo-list.9611" (presumably the messages posted to the list in November 1996), you would put the lines get demo-list profile.form get demo-list demo-list.9611 in your mail to Majordomo@FreeBSD.ORG. VII. GETTING MORE HELP To contact a human site manager, send mail to postmaster@FreeBSD.ORG. To get another copy of this help message, send mail to Majordomo@FreeBSD.ORG with a line saying help in the message body. VIII. COMMAND SUMMARY FOR ADVANCED USERS In the description below items contained in []'s are optional. When providing the item, do not include the []'s around it. Items in angle brackets, such as
, are meta-symbols that should be replaced by appropriate text without the angle brackets. It understands the following commands: subscribe [
] Subscribe yourself (or
if specified) to the named . unsubscribe [
] Unsubscribe yourself (or
if specified) from the named . "unsubscribe *" will remove you (or
) from all lists. This _may not_ work if you have subscribed using multiple addresses. get Get a file related to . index Return an index of files you can "get" for . which [
] Find out which lists you (or
if specified) are on. who Find out who is on the named . info Retrieve the general introductory information for the named . intro Retrieve the introductory message sent to new users. Non-subscribers may not be able to retrieve this. lists Show the lists served by this Majordomo server. help Retrieve this message. end Stop processing commands (useful if your mailer adds a signature). Commands should be sent in the body of an email message to "Majordomo@FreeBSD.ORG". Multiple commands can be processed provided each occurs on a separate line. Commands in the "Subject:" line are NOT processed. If you have any questions or problems, please contact "Majordomo-Owner@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 Sep 9 13:33:45 2000 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 D376737B440 for ; Sat, 9 Sep 2000 13:33:39 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id QAA67430; Sat, 9 Sep 2000 16:33:30 -0400 (EDT) Date: Sat, 9 Sep 2000 16:33:30 -0400 (EDT) From: "Matthew N. Dodd" To: Wes Peters Cc: Len Conrad , freebsd-hackers@FreeBSD.ORG Subject: Re: Token Ring ?? In-Reply-To: <39B9D97A.B640E572@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 9 Sep 2000, Wes Peters wrote: > UTSL: src/sys/dev/isa/if_tr{,ibm,tcm}_isa.c That would be the NetBSD source tree. :) -- | 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 Sat Sep 9 13:36:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from plan9.hert.org (plan9.hert.org [195.3.2.198]) by hub.freebsd.org (Postfix) with ESMTP id F000D37B424 for ; Sat, 9 Sep 2000 13:36:47 -0700 (PDT) Received: from localhost (awr@localhost) by plan9.hert.org (8.9.3/8.9.1) with ESMTP id WAA24609 for ; Sat, 9 Sep 2000 22:35:57 +0200 (CEST) Date: Sat, 9 Sep 2000 22:35:56 +0200 (CEST) From: awr To: freebsd-hackers@freebsd.org Subject: Regarding kldunload / open /dev/ panic Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Also, shouldn't /usr/src/sys/dev/vn/vn.c use make_dev() and destroy_dev() calls instead of cdevsw_add()?? Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 9 20:23:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id A4EC237B422 for ; Sat, 9 Sep 2000 20:23:41 -0700 (PDT) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id XAA85776; Sat, 9 Sep 2000 23:23:43 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Sat, 9 Sep 2000 23:23:43 -0400 (EDT) From: Adam To: Stephen Hocking Cc: hackers@FreeBSD.ORG Subject: Re: What's the best PCMCIA Ethernet card? In-Reply-To: <200009070500.e87506G44740@bloop.craftncomp.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 Hi, I'd just like to say that I dont think non cardbus cards are capable of doing more than 10bt speeds even if it talks 100bt. I have not met one that did and I assume it is a limit of the pcmcia design. Just warning you not to waste your money on one if you get near 10bt speeds already. On Thu, 7 Sep 2000, Stephen Hocking wrote: >Preferably 10/100. This old Megahertz CC10BT doesn't seem to be terribly quick. > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 9 20:25:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id AC8DC37B42C for ; Sat, 9 Sep 2000 20:25:17 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13Xxs4-0000bA-00; Sat, 09 Sep 2000 21:33:32 -0600 Message-ID: <39BB010C.6DA26A06@softweyr.com> Date: Sat, 09 Sep 2000 21:33:32 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Matthew N. Dodd" Cc: Len Conrad , freebsd-hackers@FreeBSD.ORG Subject: Re: Token Ring ?? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > > On Sat, 9 Sep 2000, Wes Peters wrote: > > UTSL: src/sys/dev/isa/if_tr{,ibm,tcm}_isa.c > > That would be the NetBSD source tree. :) Oops. Now I see why that window was green instead of purple. Make that /sys/contrib/dev/oltr/* -- "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 Sep 9 20:49:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.linkline.com (smtp1.linkline.com [192.216.128.16]) by hub.freebsd.org (Postfix) with ESMTP id 44F6F37B424 for ; Sat, 9 Sep 2000 20:49:41 -0700 (PDT) Received: from mail.linkline.com (mail.linkline.com [192.216.128.2]) by smtp1.linkline.com (Postfix) with ESMTP id 33856163673; Thu, 7 Sep 2000 09:21:13 -0700 (PDT) Received: from linkline.com [207.16.24.11] by mail.linkline.com with ESMTP (SMTPD32-6.04) id A08A5EF00EA; Thu, 07 Sep 2000 09:21:30 -0700 Message-ID: <39B7C08B.5841BA62@linkline.com> Date: Thu, 07 Sep 2000 09:21:31 -0700 From: Lance Rocker X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: John Toon Cc: freebsd-hackers@freebsd.org Subject: Re: Shared Memory Issues References: <39B4BD1D.676139D4@btinternet.com> <20000905230110.A9425@host.cer.ntnu.edu.tw> <39B58ABD.1B215190@btinternet.com> Content-Type: multipart/mixed; boundary="------------EAF22AEA197976EC1D2DCA73" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------EAF22AEA197976EC1D2DCA73 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, I too had problems with running out of shared mem segments, so I wrote my first ever perl script that does something useful for me. I've attached it to this email and I'll paste it in below too, for convenience. I noticed that many (most?) of the shared mem segments in use, when I was running out of them, didn't actually have any processes attached to them. This perl script just goes through, finds those non-attached shared mem segments, and deletes them. I've found running it periodically works great for me, you may even want to put it in your crontab and let it run once a day, just as a little proactive housekeeping. For the record, here are the kernel options I use with this kernel: options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options SHMALL=16384 options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAXPGS=8192 options SHMMIN=128 options SHMMNI=128 options SHMSEG=96 I think that last one makes the biggest difference, and is the one you may want to make as large as possible, though 96 works fine for my 64MB of ram. This is a 4.0-release kernel, and I use XFree86 4.0 with Enlightenment as my window manager. John Toon wrote: > > Clive Lin wrote: > > > > Hm... long time ago I asked google about those SHM* and > > I thought SHMSEG may be the key point. Because SHMSEG stands for > > maximum number of shared segments per process. > > Fantastic! You're absolutely correct. Everything is now working > perfectly. My mistake had been to think that the system was running out > of actual shared memory pages, but successive increases of the maximum > pages had no effect. The actual problem, as you've rightly pointed out, > was that each process was running out of shared memory segments... > > > About the SYSV options, I have small notes about them. Though, I couldn't > > make sure they are 100% correct. It just works, and I have no more interests > > to dig more :-> > > > > SHMALL max shared mem system wide (in pages). > > SHMMAX max shared memory segment size (bytes). > > SHMMIN min shared memory segment size (bytes). > > SHMMNI max num of shared segments system wide. > > SHMSEG maximum number of shared segments per process. > > > > Regards, > > Clive > > Just as a side note, are there any commands available that will inform > me how many shared memory pages are currently being used by the running > system? yes, ipcs and ipcrm are the ones my perl script uses. Check out the manpage for each of them. . . I like to run "ipcs -mbop" to get a lot of info about used shared mem segments. -Lance Okay, here's my shmfree script, make sure you set the executable bit. I keep it in ~/bin . . . #!/usr/bin/perl -w $lines=0; $ignored=0; $deleted=0; # IPCS is used to display info about SYSV IPC memory stuff. See ipcs(1) open INPUT, "ipcs -mbop | grep $ENV{USER} |"; while( ) { $lines++; @output = split; print "a shmid is $output[1], "; print "nattach is $output[6]"; if ($output[6] == 0) { system 'ipcrm', '-m', $output[1]; # See ipcrm(1) $deleted++; print " <--- Deleted\n"; } else { print "\n"; $ignored++; } } print "Total shared mem segments: $lines, ignored: $ignored, deleted: $deleted\n"; --------------EAF22AEA197976EC1D2DCA73 Content-Type: text/plain; charset=us-ascii; name="shmfree" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="shmfree" #!/usr/bin/perl -w $lines=0; $ignored=0; $deleted=0; # IPCS is used to display info about SYSV IPC memory stuff. See ipcs(1) open INPUT, "ipcs -mbop | grep $ENV{USER} |"; while( ) { $lines++; @output = split; print "a shmid is $output[1], "; print "nattach is $output[6]"; if ($output[6] == 0) { system 'ipcrm', '-m', $output[1]; # See ipcrm(1) $deleted++; print " <--- Deleted\n"; } else { print "\n"; $ignored++; } } print "Total shared mem segments: $lines, ignored: $ignored, deleted: $deleted\n"; --------------EAF22AEA197976EC1D2DCA73-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 9 22:41: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 413DD37B423 for ; Sat, 9 Sep 2000 22:41:06 -0700 (PDT) Received: from rac1.wam.umd.edu (IDENT:root@rac1.wam.umd.edu [128.8.10.141]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id BAA24205; Sun, 10 Sep 2000 01:40:26 -0400 (EDT) Received: from rac1.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id BAA16051; Sun, 10 Sep 2000 01:40:26 -0400 (EDT) Received: from localhost (culverk@localhost) by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id BAA16047; Sun, 10 Sep 2000 01:40:26 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Sun, 10 Sep 2000 01:40:25 -0400 (EDT) From: Kenneth Wayne Culver To: Adam Cc: Stephen Hocking , hackers@FreeBSD.ORG Subject: Re: What's the best PCMCIA Ethernet card? 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've seen cardbus cards do almost a full 100 mbit, but regular pcmcia cards can't do much at all. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sat, 9 Sep 2000, Adam wrote: > Hi, I'd just like to say that I dont think non cardbus cards are capable > of doing more than 10bt speeds even if it talks 100bt. I have not met one > that did and I assume it is a limit of the pcmcia design. Just warning > you not to waste your money on one if you get near 10bt speeds already. > > On Thu, 7 Sep 2000, Stephen Hocking wrote: > > >Preferably 10/100. This old Megahertz CC10BT doesn't seem to be terribly quick. > > > > > > 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 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 9 23:12:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cecov.masternet.it (cecov.masternet.it [194.184.65.7]) by hub.freebsd.org (Postfix) with ESMTP id 2892137B422 for ; Sat, 9 Sep 2000 23:12:44 -0700 (PDT) Received: from suzy.scotty.masternet.it (modem03.masternet.it [194.184.65.63]) by cecov.masternet.it (8.9.3/8.9.3) with ESMTP id HAA23306 for ; Sun, 10 Sep 2000 07:59:55 +0200 (CEST) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.3.2.7.2.20000910075331.023fb5d0@194.184.65.7> X-Sender: gmarco@194.184.65.7 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 10 Sep 2000 08:11:23 +0200 To: freebsd-hackers@FreeBSD.ORG From: Gianmarco Giovannelli Subject: Re: Token Ring ?? I am using, but ... In-Reply-To: <39BB010C.6DA26A06@softweyr.com> References: 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 Token ring is supported and works quite well in FreeBSD. I am using a couple of card on a box to connect an entire network to the Internet (about 200 boxes). I have only a problem, or at least it seems to me a problem :-) I posted the following message to token-ring and questions mailing lists and directly to the author of the driver without having received any answer. So I post it here because I see someone that perhaps can answer (surely) to this :-) --- begin old message --- I have installed a FreeBSD 4.1-STABLE box with two olicom token ring cards. Everything seems to works fine except for the fact that one of these card has a lot of errors. Aug 9 19:00:47 freebsd /kernel: oltr0: receive error 3 Aug 9 19:01:22 freebsd last message repeated 7 times Aug 9 19:03:23 freebsd last message repeated 480 times Aug 9 19:13:28 freebsd last message repeated 7496 times Aug 9 19:23:29 freebsd last message repeated 7019 times Aug 9 19:33:30 freebsd last message repeated 3714 times Aug 9 19:43:32 freebsd last message repeated 38062 times Aug 9 19:48:07 freebsd last message repeated 5112 times What does this error (error 3) means ? Performance seems not be affected but it is quite annoying because it fills up every system logs. Is possible to correct it ? Is it harmless ? This is a piece of the boot message: Jul 29 19:36:47 freebsd /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Jul 29 19:36:47 freebsd /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jul 29 19:36:47 freebsd /kernel: The Regents of the University of California. All rights reserved. Jul 29 19:36:47 freebsd /kernel: FreeBSD 4.1-RC #0: Tue Jul 25 23:43:13 CEST 2000 Jul 29 19:36:47 freebsd /kernel: gmarco@freebsd.consiag.it:/usr/src/sys/compile/FREEBSD Jul 29 19:36:47 freebsd /kernel: Timecounter "i8254" frequency 1193182 Hz Jul 29 19:36:47 freebsd /kernel: Timecounter "TSC" frequency 166194007 Hz Jul 29 19:36:47 freebsd /kernel: CPU: Pentium/P54C (166.19-MHz 586-class CPU) Jul 29 19:36:47 freebsd /kernel: Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Jul 29 19:36:47 freebsd /kernel: Features=0x1bf Jul 29 19:36:47 freebsd /kernel: real memory = 134217728 (131072K bytes) Jul 29 19:36:47 freebsd /kernel: avail memory = 127803392 (124808K bytes) Jul 29 19:36:47 freebsd /kernel: Preloaded elf kernel "kernel" at 0xc02b6000. Jul 29 19:36:47 freebsd /kernel: Intel Pentium detected, installing workaround for F00F bug Jul 29 19:36:47 freebsd /kernel: md0: Malloc disk Jul 29 19:36:47 freebsd /kernel: npx0: on motherboard Jul 29 19:36:47 freebsd /kernel: npx0: INT 16 interface Jul 29 19:36:47 freebsd /kernel: pcib0: on motherboard Jul 29 19:36:47 freebsd /kernel: pci0: on pcib0 Jul 29 19:36:47 freebsd /kernel: isab0: at device 1.0 on pci0 Jul 29 19:36:47 freebsd /kernel: isa0: on isab0 Jul 29 19:36:47 freebsd /kernel: pci0: at 1.1 Jul 29 19:36:47 freebsd /kernel: pci0: at 1.2 irq 15 Jul 29 19:36:47 freebsd /kernel: ahc0: port 0x4000-0x40ff mem 0x80000000-0x80000fff irq 14 at device 6.0 on pci0 Jul 29 19:36:47 freebsd /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Jul 29 19:36:47 freebsd /kernel: oltr0: port 0x4440-0x447f irq 11 at device 7.0 on pci0 Jul 29 19:36:47 freebsd /kernel: oltr0: enabling bus master mode Jul 29 19:36:47 freebsd /kernel: oltr0: MAC address 00:00:83:2b:63:db Jul 29 19:36:47 freebsd /kernel: oltr0: adapter self-test complete (status=0) Jul 29 19:36:47 freebsd /kernel: pci0: at 8.0 Jul 29 19:36:47 freebsd /kernel: oltr1: port 0x4400-0x443f irq 10 at device 11.0 on pci0 Jul 29 19:36:47 freebsd /kernel: oltr1: enabling bus master mode Jul 29 19:36:47 freebsd /kernel: oltr1: MAC address 00:00:83:2b:63:df Jul 29 19:36:47 freebsd /kernel: oltr1: adapter self-test complete (status=0) Jul 29 19:36:47 freebsd /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Jul 29 19:36:47 freebsd /kernel: fdc0: FIFO enabled, 8 bytes threshold Jul 29 19:36:47 freebsd /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Jul 29 19:36:47 freebsd /kernel: atkbdc0: at port 0x60,0x64 on isa0 Jul 29 19:36:47 freebsd /kernel: atkbd0: irq 1 on atkbdc0 Jul 29 19:36:47 freebsd /kernel: psm0: irq 12 on atkbdc0 Jul 29 19:36:47 freebsd /kernel: psm0: model Generic PS/2 mouse, device ID 0 Jul 29 19:36:47 freebsd /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Jul 29 19:36:47 freebsd /kernel: sc0: on isa0 Jul 29 19:36:48 freebsd /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Jul 29 19:36:48 freebsd /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Jul 29 19:36:48 freebsd /kernel: sio0: type 16550A Jul 29 19:36:48 freebsd /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Jul 29 19:36:48 freebsd /kernel: sio1: type 16550A Jul 29 19:36:48 freebsd /kernel: ppc0: at port 0x278-0x27f irq 7 on isa0 Jul 29 19:36:48 freebsd /kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode Jul 29 19:36:48 freebsd /kernel: lpt0: on ppbus0 Jul 29 19:36:48 freebsd /kernel: lpt0: Interrupt-driven port Jul 29 19:36:48 freebsd /kernel: IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, unlimited logging Jul 29 19:36:48 freebsd /kernel: Waiting 3 seconds for SCSI devices to settle Jul 29 19:36:48 freebsd /kernel: Mounting root from ufs:/dev/da0s1a Jul 29 19:36:48 freebsd /kernel: cd0 at ahc0 bus 0 target 3 lun 0 Jul 29 19:36:48 freebsd /kernel: cd0: Removable CD-ROM SCSI-2 device Jul 29 19:36:48 freebsd /kernel: cd0: 5.000MB/s transfers (5.000MHz, offset 15) Jul 29 19:36:48 freebsd /kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present Jul 29 19:36:48 freebsd /kernel: da1 at ahc0 bus 0 target 5 lun 0 Jul 29 19:36:48 freebsd /kernel: da1: Fixed Direct Access SCSI-2 device Jul 29 19:36:48 freebsd /kernel: da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled Jul 29 19:36:48 freebsd /kernel: da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) Jul 29 19:36:48 freebsd /kernel: da0 at ahc0 bus 0 target 0 lun 0 Jul 29 19:36:48 freebsd /kernel: da0: Fixed Direct Access SCSI-2 device Jul 29 19:36:48 freebsd /kernel: da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled Jul 29 19:36:48 freebsd /kernel: da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) Jul 29 19:36:48 freebsd /kernel: oltr0: ring insert (16 Mbps - TXI) Jul 29 19:36:48 freebsd /kernel: oltr1: ring insert (16 Mbps - TKP) The interesting thing is that the two cards use different (automatic) configured setting (TXI, TKP). Oltr1 never experiences errors so what does it means ? May this be the problem ? And if yes how I can configure it ? man oltr seems not to exist anymore in my 4.1-STABLE . Here are more informations: freebsd:/home/gmarco# ifconfig -a oltr0: flags=143 mtu 1500 inet 172.16.16.239 netmask 0xfffff000 broadcast 172.16.31.255 lladdr 00:00:83:2b:63:db media: UTP/16Mbit () supported media: UTP/16Mbit UTP/4Mbit oltr1: flags=143 mtu 1500 inet 213.26.243.210 netmask 0xffffffe0 broadcast 213.26.243.223 lladdr 00:00:83:2b:63:df media: UTP/16Mbit () supported media: UTP/16Mbit UTP/4Mbit lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 freebsd:/home/gmarco# uname -a FreeBSD freebsd.consiag.it 4.1-RC FreeBSD 4.1-RC #0: Tue Jul 25 23:43:13 CEST 2000 gmarco@freebsd.consiag.it:/usr/src/sys/compile/FREEBSD i386 freebsd:/home/gmarco# Thanks to everyone for attention. Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message